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).
Alarm Management Interfaces

Alarm Management Interfaces

Reporting Real-Time Alarm Traps

The SNMP NBI of the eSight reports real-time alarm traps to the third-party system so that the third-party system can obtain NE alarm information in a timely manner.

Real-time alarm traps cover fault alarms, clear alarms, event alarms, acknowledged alarms, unacknowledged alarms, and change alarms.

The third-party system can receive real-time alarm traps after the trap IP address, port, and protocol version are configured on the third-party system. For the definition of a real-time alarm trap, see Real-Time Alarm Traps.

Synchronizing Alarms

Function

SNMP is a UDP-based protocol, which is unreliable and may cause alarms to get lost during transmission. The third-party system can synchronize alarms periodically to ensure alarm data consistency with the eSight, or stop alarm synchronization.

When alarm synchronization is triggered, the SNMP NBI sends a trap to the third-party system, indicating the start of alarm synchronization.

When the synchronization is complete or the third-party system stops the synchronization, the SNMP NBI sends a trap to the third-party system, indicating the end of alarm synchronization.

For details on the trap indicating the start of alarm synchronization, see Alarm Query Start Trap.

For details on the trap indicating the alarm synchronization results, see Alarm Query Trap.

For details on the trap indicating the end of alarm synchronization, see Alarm Query End Trap.

The third-party system is not allowed to start another alarm synchronization before the current synchronization is complete.

MIB Definition

The MIB OID is 1.3.6.1.4.1.2011.2.15.2.4.1.5.

The complete path is as follows:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).products(2).hwNetManagement(15).iMAPNorthbound(2).iMAPNorthboundFault(4).iMAPNorthboundFaultQuery(1).iMAPNorthboundAlarmQuery(5)

Node Name

Data Type

Maximum Access Rights

Description

iMAPNorthboundAlarmQuery

OCTET STRING

read-write

Query active alarms.

Setting Method

  • Starting alarm synchronization

    The third-party system sets iMAPNorthboundAlarmQuery to 1 to start alarm synchronization.

  • Stopping alarm synchronization

    The third-party system sets iMAPNorthboundAlarmQuery to 0 to stop alarm synchronization.

Acknowledging Alarms

Function

The third-party system acknowledges alarms reported from the eSight by alarm sequence number.

After being acknowledged, the alarm becomes an acknowledged alarm. If reporting acknowledged alarms is set as a filter criterion, the SNMP NBI will reports acknowledged alarms to the third-party system.

  • After an alarm is acknowledged using the SNMP NBI, Acknowledged by on the eSight client is displayed as SNMP Agent User.
  • Alarms with invalid or unavailable alarm sequence numbers or historical alarms cannot be acknowledged. When the problem occurs, the SNMP NBI returns an error message to the third-party system.

MIB Definition

The MIB OID is 1.3.6.1.4.1.2011.2.15.2.4.4.1.

The complete path is as follows:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).products(2).hwNetManagement(15).iMAPNorthbound(2).iMAPNorthboundFault(4).iMAPNorthboundFaultAcknowledge(4).iMAPNorthboundAlarmAcknowledge(1)

Node Name

Data Type

Maximum Access Rights

Description

iMAPNorthboundAlarmAcknowledge

OCTET STRING

read-write

Acknowledge alarms by alarm sequence number.

Setting Method

The third-party system sets the MIB value to acknowledge active alarms on the eSight.

The format is as follows: alarm sequence number,alarm sequence number,...

Alarm sequence numbers are separated by commas (,).

Unacknolwedging Alarms

Function

The third-party system unacknowledges alarms reported from the eSight by alarm sequence number.

After being unacknowledged, the alarm becomes an unacknowledged alarm. If reporting unacknowledged alarms is set as a filter criterion, the SNMP NBI will report unacknowledged alarms to the third-party system.

  • After an alarm is acknowledged using the SNMP NBI, Acknowledged by on the eSight client is displayed as SNMP Agent User.
  • Alarms with invalid or unavailable alarm sequence numbers or historical alarms cannot be unacknowledged. If this problem occurs, the SNMP NBI returns an error message to the third-party system.

MIB Definition

The MIB OID is 1.3.6.1.4.1.2011.2.15.2.4.5.1.

The complete path is as follows:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).products(2).hwNetManagement(15).iMAPNorthbound(2).iMAPNorthboundFault(4).iMAPNorthboundFaultUnAcknowledge(5).iMAPNorthboundAlarmUnAcknowledge(1)

Node Name

Data Type

Maximum Access Rights

Description

iMAPNorthboundAlarmUnAcknowledge

OCTET STRING

read-write

Unacknowledge alarms by alarm sequence number.

Setting Method

The third-party system sets the MIB value to unacknowledge active alarms on the eSight.

The format is as follows: alarm sequence number,alarm sequence number...

Alarm sequence numbers are separated by commas (,).

Clearing Alarms

Function

The third-party system clears alarms reported from the eSight by alarm sequence number.

After being cleared, the alarm becomes a clear alarm. If reporting clear alarms is set as a filter criterion, the SNMP NBI will report clear alarms to the third-party system.

  • After an alarm is cleared using the SNMP NBI, Cleared by on the eSight client is displayed as SNMP Agent User.
  • Alarms with invalid or unavailable alarm sequence numbers or historical alarms cannot be cleared. If this problem occurs, the SNMP NBI returns an error message to the third-party system.

MIB Definition

The MIB OID is 1.3.6.1.4.1.2011.2.15.2.4.6.1.

The complete path is as follows:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).huawei(2011).products(2).hwNetManagement(15).iMAPNorthbound(2).iMAPNorthboundFault(4).iMAPNorthboundFaultClear(4).iMAPNorthboundAlarmClear(1)

Node Name

Data Type

Maximum Access Rights

Description

iMAPNorthboundAlarmClear

OCTET STRING

read-write

Clear alarms by alarm sequence number.

Setting Method

The third-party system sets the MIB value to clear active alarms on the eSight.

The format is as follows: alarm sequence number,alarm sequence number,....

Alarm sequence numbers are separated by commas (,).

Translation
Download
Updated: 2019-10-30

Document ID: EDOC1100044386

Views: 15216

Downloads: 83

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