ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.13 hwIsisAdjacencyChangeClear

Description

ISIS/2/ADJ_CHANGE_CLEAR:OID [oid] The isisAdjacencyChange alarm was cleared. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofInterface=[integer], circuit=[integer], ifIndex=[integer], circuitIfIndex=[integer], lspID=[string], adjState=[integer], ifName=[string], hwIsisAdjChangeReason=[integer], hwIsisAdjChangeSubReason=[integer])

The IS-IS neighbor status change alarm is cleared.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.24.2.4.13

Major

equipmentAlarm(5)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

ID of an IS-IS instance

sysInstanceofLevel

Instance level

sysLevel
IS-IS level:

  • 1: Level-1

  • 2: Level-2

sysInstanceofInterface

Interface that belongs to an IS-IS process

circuit

Link ID

ifIndex

Interface index

circuitIfIndex

Interface index

lspID

LSP ID

adjState
Neighbor status:

  • 1: Down

  • 2: Initializing

  • 3: Up

  • 4: Failed

  • 5: Cleared

ifName

Name of an interface

hwIsisAdjChangeReason
Possible causes of the neighbor status change:

  • 1: The hold timer expired.

  • 2: The status of the physical interface changed.

  • 3: It is a protocol-related cause.

  • 4. The BFD session went Down.

  • 5: A configuration was changed.

  • 6. It is a neighbor-related cause.

  • 7. Other causes.

  • 8. The alarm was cleared.

  • 100: The neighbor was cleared.

hwIsisAdjChangeSubReason
Detailed causes of the neighbor status change:

  • 1: An adjacency relationship was established.

  • 2. The adjacency relationship was deleted.

  • 3: An interface was deleted.

  • 4: The interface was suppressed.

  • 5: An invalid Hello packet was received.

  • 6: Authentication failed.

  • 7: A system ID conflict occurred.

  • 8: The maximum number of area addresses in the received Hello packet was different from the local one.

  • 9: The area address of the neighbor was different from the local area address.

  • 10: No Hello packet was received.

  • 11: The interface went Down.

  • 12: Protocols did not match.

  • 13: The neighbor was deleted.

  • 14. The BFD session went Down.

  • 15: The level was changed.

  • 16: The P2P negotiation configuration was changed.

  • 17. The neighbor was reset.

  • 18: The interface type was changed.

  • 19: IS-IS was reset.

  • 20: The NET configuration was deleted.

  • 21: IS-IS was disabled.

  • 2. Levels did not match.

  • 23: The received Hello packet did not carry the local MAC address.

  • 24: Three-way handshake failed.

  • 25: Topologies did not match.

  • 26: Interface IDs did not match.

  • 27: The three-way handshake status was Down.

  • 28: Unknown errors occurred.

  • 29: Optional checksum check failed.

Impact on the System

The system will not be affected.

Possible Causes

The interface instance was deleted.

Procedure

  1. This trap is informational only, and no action is required.

Related Information

None

Parent topic: ISIS
Copyright © Huawei Technologies Co., Ltd.