Job Management Partner 1/Integrated Management - Event Gateway for Network Node Manager i Description, User's Guide and Reference

4.1.4 Definition example (sample file)

This subsection describes a definition example of an NNMi incident forwarding filter definition file based on using the sample file.

Shown below are the contents of the sample file. Note that line numbers are added for explanation purposes.
    #All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.
    #Licensed Material of Hitachi, Ltd.
1   forward-condition
2   filter
3   #An incident whose severity level is MINOR or higher
4   SEVERITY_UK RANGE MINOR CRITICAL
5   end-filter
6   mapping
7   message $FORMATTED_MESSAGE$
8   severity CRITICAL to Alert
9   severity MAJOR to Critical
10  severity MINOR to  Warning
11  severity WARNING to Notice
12  severity NORMAL to Information
13  #Addition of Notes to JP1 event extended attributes
14  attribute NNMI_NOTES
15  end-mapping
16  end-forward-condition
Filter condition block (lines 2 to 5)

Those NNMi incidents whose severity (SEVERITY_UK) is in the range from MINOR to CRITICAL are to be converted into JP1 events.

Mapping block (lines 6 to 15)

Message mapping (line 7)
Defines that messages in the NNMi incidents are to be mapped as is into messages in the JP1 events.

Severity mapping (lines 8 to 12)
Defines severity mapping between NNMi incidents and JP1 events.

Extended attribute mapping (line 14)
Defines that Notes (NNMI_NOTES) are to be mapped as an extended attribute.

[Contents][Back][Next]

[Trademarks]