No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R010C00SPC200, 300, and 500 Self-Service Integration Guide 10

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Real-Time Alarm Traps

Real-Time Alarm Traps

Trap Description

When an alarm is generated for an NE or eSight, the SNMP NBI sends a real-time alarm trap to the upper-layer NMS.

Triggering Condition

The SNMP NBI sends a real-time alarm trap to the upper-layer OSS when an alarm is generated for an NE or eSight.

Trap Definition

Name

OID

Type

Description

iMAPNorthboundFaultAlarmReportNotificationType

1.3.6.1.4.1.2011.2.15.2.4.3.3.0.1

Trap/Inform

Report real-time alarms.

Field List

eSight provides real-time alarm trap fields, covering different SNMP versions used to interconnect with the upper-layer NMS.

The default data types of the fields listed in Table 4-11 comply with SNMPv1.

  • The data types complying with SNMPv2c and SNMPv3 are not described if they are the same as those complying with SNMPv1.
  • Different data types are provided in parentheses.
  • x represents 1.3.6.1.4.1.2011.2.15.2.4.3.3. For example, x.1 means 1.3.6.1.4.1.2011.2.15.2.4.3.3.1.
  • In this table, the OID fields are described in the ascending order. Interconnection requests are processed based on the sequence of the fields actually reported in the trap.
Table 4-11 iMAPNorthboundFaultAlarmReportNotificationType fields

Name

OID

Type

Description

iMAPNorthboundAlarmCSN

x.1

OCTET STRING

Indicates the alarm sequence number that uniquely identifies an alarm.

Example: 2000143

iMAPNorthboundAlarmCategory

x.2

OCTET STRING

Indicates the alarm type. The options are as follows:

  • 1: fault alarm
  • 2: cleared alarm
  • 3: event alarm
  • 4: acknowledged alarm
  • 5: unacknowledged alarm
  • 9: change alarm

Example: 1

iMAPNorthboundAlarmOccurTime

x.3

OCTET STRING

Indicates the alarm occurrence time.

The following two formats are supported:

  • 1: yyyy-mm-dd hh:MM:ss %TZ [%DST]
  • 2: yyyy-mm-dd hh:MM:ss

Example: 2016-11-22 00:35:00

iMAPNorthboundAlarmMOName

x.4

OCTET STRING

Indicates the device name.

Example: MyDevice 10.137.63.119

iMAPNorthboundAlarmProductID

x.5

INTEGER

Identifies the product series.

  • 6: alarm generated on eSight
  • 5: alarm reported by a device

Example: 5

iMAPNorthboundAlarmNEType

x.6

OCTET STRING

Identifies the device type.

Example: RH2288H V3

iMAPNorthboundAlarmNEDevID

x.7

OCTET STRING

Indicates the unique device ID.

Example: NE=34603236

iMAPNorthboundAlarmDevCsn

x.8

OCTET STRING

Indicates the SN of the device that generates an alarm. Each NE has a unique SN, for example, 550142.

iMAPNorthboundAlarmID

x.9

INTEGER (Integer32)

Indicates the alarm ID that distinguishes between alarm types for devices of the same type.

Example: 1100138

iMAPNorthboundAlarmType

x.10

INTEGER (Integer32)

Indicates the alarm type.

By default, the eSight specifications are used. The options are as follows:

  • 1: power system
  • 2: environmental system
  • 3: signaling system
  • 4: trunk system
  • 5: hardware system
  • 6: software system
  • 7: running system
  • 8: communications system
  • 9: QoS
  • 10: processing error
  • 11: OMC
  • 12: integrity violation
  • 13: operational violation
  • 14: physical violation
  • 15: security service or mechanism violation
  • 16: time domain violation
NOTE:

For the following common alarms on eSight (with alarm types ranging 11 to 21), the alarm type is uniformly set to 11 (OMC) for report.

11: ATTRIBUT_VALUE_CHANGE

12: OBJECT_CREATION

13: OBJECT_DELETION

14: RELATIONSHIP_CHANGE

15: STATE_CHANG

16: ROUTE_CHANGE

17: PROTECTION_SWITCH

18: TCA

19: FILE_TRANSFER_STATUS

20: BACKUP_STATUS

21: HEARTBEAT

If omsCompatibility under <MIB2 name="MIB2"> in the <Installation directory>/AppBase/run/etc/nbi/snmp/snmpagent.xml file is set to 1, the OMS specifications are used. The options are as follows:

  • 1: communications alarm
  • 2: equipment alarm
  • 3: processing error alarm
  • 4: QoS alarm
  • 5: environmental alarm
  • 6: integrity violation
  • 7: operational violation
  • 8: physical violation
  • 9: security service or mechanism violation
  • 10: time domain violation
  • 11: attribute value change
  • 12: object creation
  • 13: object deletion
  • 14: relationship change
  • 15: state change
  • 16: route change
  • 17: protection switch
  • 18: TCA
  • 19: file transfer status
  • 20: backup status
  • 21: heartbeat

Example: 2

iMAPNorthboundAlarmLevel

x.11

INTEGER

Indicates the alarm severity. The options are as follows:

1: critical

2: major

3: minor

4: suggestion

5: indeterminate

6: cleared

Example: 1

iMAPNorthboundAlarmRestore

x.12

INTEGER

Indicates whether the alarm is cleared.

  • 1: The alarm is cleared.
  • 2: The alarm is not cleared.
NOTE:

An event does not need to be cleared, and the value 0 is reported.

Example: 2

iMAPNorthboundAlarmConfirm

x.13

INTEGER

Indicates whether the alarm is acknowledged.

  • 1: The alarm is acknowledged.
  • 2: The alarm is not acknowledged.
NOTE:

An event does not need to be acknowledged, and the value 0 is reported.

Example: 2

iMAPNorthboundAlarmAckTime

x.14

OCTET STRING

Indicates the time when the alarm is acknowledged. If the alarm is not acknowledged, the value is a string of 0 character.

The following two formats are supported:

  • 1: yyyy-mm-dd hh:MM:ss %TZ [%DST]
  • 2: yyyy-mm-dd hh:MM:ss

Example: ""

iMAPNorthboundAlarmRestoreTime

x.15

OCTET STRING

Indicates the time when an alarm is cleared.

Example: ""

iMAPNorthboundAlarmOperator

x.16

OCTET STRING

Indicates the user who acknowledges the alarm.

Example: ""

IMAPNorthboundAlarmParas1

x.17

INTEGER

Indicates the alarm group ID.

Example: 278413609

NOTE:

The value of this field is 0 when events are reported.

iMAPNorthboundAlarmExtendInfo

x.27

OCTET STRIN

Indicates the alarm location information.

Example: Address=10.137.63.227, Protocol=SNMP, Port=161

iMAPNorthboundAlarmProbablecause

x.28

OCTET STRING

Indicates the alarm cause.

Example: Registration failure of the trap IP address with the device

iMAPNorthboundAlarmProposedrepairactions

x.29

OCTET STRING

Indicates the suggestion for rectifying the fault that generates the alarm.

Example: Check the SNMP parameters of the device.

iMAPNorthboundAlarmSpecificproblems

x.30

OCTET STRING

Indicates the detailed alarm cause.

Example:

Possible causes:

The number of trap IP addresses registered on the device reached the upper limit.

iMAPNorthboundAlarmClearOperator

x.46

OCTET STRING

Indicates the user who clears the alarm.

Example: ""

iMAPNorthboundAlarmObjectInstanceType

x.47

OCTET STRING

Indicates the alarm object instance type. If the alarm is generated by a component in a device, set this parameter to the resources type of the component, for example, Interface.

Example: RH2288H V3

iMAPNorthboundAlarmClearCategory

x.48

OCTET STRING

Indicates the alarm clearance type.

By default, the eSight specifications are used. The value is an integer and the options are as follows:

  • 1: alarms that can be automatically cleared.
  • 2: alarms that cannot be automatically cleared.
NOTE:

An event does not need to be cleared, and the value 0 is reported.

If omsCompatibility under <MIB2 name="MIB2"> in the <Installation directory>/AppBase/run/etc/nbi/snmp/snmpagent.xml file is set to 1, the OMS specifications are used. The options are as follows:

  • ADAC: Automatically Detected and Automatically Cleared
  • ADMC: Automatically Detected and Manually Cleared

Example: 1

iMAPNorthboundAlarmClearType

x.49

OCTET STRING

Indicates the alarm clearance type.

  • 0: not cleared
  • 1: normally clear
  • 2: cleared by resetting
  • 3: manually cleared
  • 4: cleared by configuration
  • 5: cleared by co-relation
NOTE:

If an alarm is not cleared, the value 0 is reported.

Example: 0

iMAPNorthboundAlarmServiceAffectFlag

x.50

OCTET STRING

Indicates whether the alarm affects operations. The options are as follows:

  • 1: affected
  • 2: not affected
  • 3: unknown
    NOTE:

    For an event, the value 0 is reported.

Example: 2

iMAPNorthboundAlarmAdditionalInfo

x.51

OCTET STRING

Indicates the additional information.

Example:

Recommended actions:

Contact your service provider to clear the alarm. Failed to register a trap IP address with the device. The target IP address is (10.137.67.83) and the target port is (162).

IMAPNorthboundAlarmExtendProductItem5

x.35

OCTET STRING

Indicates the MODN value of the reported alarm. This is an extended field.

Example: NE=34603236

NOTE:

This parameter is valid only in the following scenarios:

  • Local HA system software (SUSE Linux + MySQL + OMMHA)
  • Local HA system software (EulerOS + GaussDB + OMMHA)

IMAPNorthboundAlarmExtendProductItem6

x.36

OCTET STRING

Indicates the name of the NE that reports an alarm. This is an extended field.

Example: MyDevice 10.137.63.119

NOTE:

This parameter is valid only in the following scenarios:

  • Local HA system software (SUSE Linux + MySQL + OMMHA)
  • Local HA system software (EulerOS + GaussDB + OMMHA)

IMAPNorthboundAlarmExtendProductItem1

x.31

OCTET STRING

Indicates the IP address of the alarm NE.

NOTE:

This field is not supported by default. The extended field NEIP needs to be added to the <Installation directory>/Appbase/etc/nbi/snmp/snmpagent.xml file. It is recommended that the operation be performed by Huawei engineers.

<MIB2 name="MIB2">
    <Mib name="Mib">
        <param name="VBn+1">NEIP</param>
    </Mib>
</MIB2>

In the information, n indicates the maximum VB sequence number in the configuration file. For example, if n is 30, set this parameter to VB31.

Translation
Download
Updated: 2019-10-30

Document ID: EDOC1100044386

Views: 17826

Downloads: 87

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next