< Home

ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

Description

ISIS/3/REJECT_ADJ:OID [oid] IS-IS failed to establish the adjacency with its peer. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFragment=[opaque], ifName=[string], hwIsisAdjChangeReason=[integer], hwIsisAdjChangeSubReason=[integer])

The local switch received a Hello packet sent by the adjacent switch, but cannot establish the IS-IS neighbor relationship with the adjacent switch.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.13

Minor

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel
Indicates the IS-IS level:

  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduFragment

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

hwIsisAdjChangeReason
Indicates the main cause of the change in the neighbor relationship:

  • 1: peer hold timer expiration

  • 2: physical interface change

  • 3: protocol reason

  • 4: BFD session getting down

  • 5: configuration change

  • 6: reason of peer router

  • 7: other reason

  • 8: alarm cleared

hwIsisAdjChangeSubReason
Indicates details about the cause of the change in the neighbor relationship:

  • 1: status of peer relation getting up

  • 2: peer deleted

  • 3: interface deleted

  • 4: interface silence

  • 5: invalid hello packets received

  • 6: authentication failed

  • 7: system ID conflict

  • 8: maximum area address number mismatch

  • 9: different L1 area addresses

  • 10: hello packet receiving failure

  • 11: interface going Down

  • 12: protocol mismatch

  • 13: adjacency deleted for space

  • 14: BFD session going down

  • 15: level change

  • 16: P2P negotiations change

  • 17: peer reset

  • 18: interface type change

  • 19: IS-IS reset

  • 20: undo network

  • 21: undo isis

  • 22: level mismatch

  • 23: no local MAC address in the received Hello packet

  • 24: three-way adjacency not up

  • 25: topology mismatch

  • 26: circuit ID mismatch

  • 27: Down three-way adjacency state

  • 28: other errors

  • 29: optional checksum TLV check failed

Impact on the System

The neighbor relationship cannot be established.

Possible Causes

1. The system ID or virtual system ID of the local switch is the same as the system ID of the neighbor.

2. The authentication mode or the authentication password configured for the interface on the local switch was inconsistent with that configured on the neighbor. As a result, the authentication of the Hello packet failed.

3. The Level-1 area address of the IS-IS neighbor was inconsistent with the Level-1 area address of the local switch.

4. The local interface received a Hello packet whose level is inconsistent with the local switch level.

5. In a broadcast network, the local interface received a Hello packet sent by the adjacent interface whose IP address is on a different network segment.

6. In a P2P network, because the isis peer-ip-ignore is not configured, the local interface received a Hello packet sent by the adjacent interface whose IP address is on a different network segment.

Procedure

  1. Check the IfName field in the trap to identify the interface that receives packets.

    • If the interface is a broadcast interface, go to Step 2.

    • If the interface is a P2P interface, go to Step 7.

  2. Check the PduFragment field in the trap, and then identify the source switch according to the consecutive six bytes beginning with the tenth byte, which indicates the system ID of the source switch. Run the display this command in the views of interfaces on the two ends of the link and in the IS-IS process view to check whether the IS-IS levels and interface levels on both ends of the link are consistent.

    • If so, go to Step 6.

    • If not, go to Step 3.

  3. Run the isis circuit-level command in the interface view to change the IS-IS levels and interface levels on both ends of the link to be consistent. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 4.

  4. Run the isis circuit-leveldisplay ip interface command to check whether the IP address of the interface on the source switch is on the same network segment as the IP address of the local interface.

    • If so, go to Step 8.

    • If not, go to Step 5.

  5. Run the ip address command in the interface views of the source switch and local switch to configure IP addresses of interfaces on both ends to belong to the same network segment. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 8.

  6. Run the display this command in the interface views of the source switch and local switch to check whether the isis peer-ip-ignore command is run.

    • If so, go to Step 10.

    • If not, go to Step 7.

  7. Run the isis peer-ip-ignore or ip address command in the interface views of the source switch and local switch to configure IP addresses of interfaces on both ends to belong to the same network segment. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 10.

  8. Check whether the Level-1 area addresses on both ends of the link are the same.

    • If so, go to Step 10.

    • If not, go to Step 9.

  9. Run the network-entity command in the IS-IS view to configure a new area address to ensure that the Level-1 area addresses on both ends are the same. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 10.

  10. Run the display current-configuration command to check whether the system ID of the source switch is the same as the system ID or virtual system ID of the local switch.

    • If so, go to Step 11.

    • If not, go to Step 12.

  11. Run the network-entity command to change the system ID or virtual system ID on one switch to ensure that the system IDs or virtual system IDs on both ends are different. Then, check whether the trap is cleared.

    • If so, go to Step 14.

    • If not, go to Step 12.

  12. Check IS-IS authentication modes and authentication passwords of interfaces on both ends are the same.

    • If so, go to Step 14.

    • If not, go to Step 13.

  13. Run the isis authentication-mode command in the views of interface on both ends to change the authentication mode and authentication password to ensure that IS-IS authentication modes and authentication passwords of interfaces on both ends are consistent. Alternatively, run the undo isis authentication-mode command in the views of interface on both ends to disable IS-IS authentication (disabling IS-IS authentication degrades the system security). Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 14.

  14. Collect the trap information, log information, and configuration, and then contact technical support personnel.
  15. End.

Related Information

None

Parent Topic: ISIS
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >