ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

Trap Buffer Description

IS-IS failed to establish the adjacency with its peer. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The local device received Hello packets sent from the neighboring device but failed to establish IS-IS neighbor relationships with it.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Error
Mnemonic Code	ISIS_REJECTED_ADJACENCY
Trap OID	1.3.6.1.3.37.2.0.13
MIB	ISIS-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
isisSysInstance	ID of an IS-IS process.
isisSysLevelIndex	IS-IS level.
isisCircIndex	Circuit IfIndex of an interface.
isisCircIfIndex	Circuit IfIndex of an interface.
isisPduFragment	64-byte PDU header.
ifIndex	IfIndex of an interface.
IfName	Interface name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.3.37.1.1.1.1.1	isisSysInstance	isisSysInstance
1.3.6.1.3.37.1.2.1.1.1	isisSysLevelIndex	isisSysInstance isisSysLevelIndex
1.3.6.1.3.37.1.3.1.1.2	isisCircIfIndex	isisSysInstance isisCircIndex
1.3.6.1.3.37.1.10.1.1.2	isisPduFragment	isisSysInstance
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex

Impact on the System

The neighbor relationship cannot be established.

Possible Causes

Cause 1: The system ID or virtual system ID on the local device was identical to that on the neighboring device.

Cause 2: Hello packets failed the authentication because the authentication mode or password on the local interface was different from that on the neighboring interface.

Cause 3: IS-IS Level-1 area addresses were different on the two ends of the link.

Cause 4: The local interface received Hello packets whose Level mismatched that on the local interface.

Cause 5: On a broadcast network, the local interface received Hello packets from an interface that is not on the network segment where the local interface resides.

Cause 6: On a P2P network, when not configured with the isispeer-ip-ignore command, the local interface received Hello packets from an interface that is not on the network segment where the local interface resides.

Procedure

1. Check the IfName field value and determine the interface type.

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 isisPduFragment field, and then identify the source device based on its system ID (six consecutive bytes beginning with the 10th byte). 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 the two ends of the link are consistent.

If not, go to Step 3.
If so, go to Step 6.

3. Run the isis circuit-level command in the interface view to change the IS-IS levels and interface levels on the two ends of the link to be the same. Check whether the fault is rectified.

If so, go to Step 15.
If not, go to Step 4.

4. Run the display ip interface command to check whether the IP addresses of the source device interface and the local interface are on the same network segment.

If so, go to Step 8.
If not, go to Step 5.

5. Run the ip address command respectively in the source device interface view and the local interface view to configure the IP addresses of the two interfaces to be on the same network segment. Check whether the fault is rectified.

If so, go to Step 15.
If not, go to Step 8.

6. Run the display this command respectively in the source device interface view and the local interface view to check whether the isis peer-ip-ignore command is configured on the two interfaces.

If so, go to Step 10.
If not, go to Step 7.

7. Run the isis peer-ip-ignore or ip address command respectively in the source device interface view and the local interface view to configure the IP addresses of the two interfaces to be on the same network segment. Check whether the fault is rectified.

If so, go to Step 15.
If not, go to Step 10.

8. Check whether the Level-1 area addresses on the two 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, ensuring that Level-1 area addresses on the two ends of the link are the same. Check whether the fault is rectified.

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 device is the same as the system ID or virtual system ID on the local device.

If so, go to Step 11.
If not, go to Step 12.

11. Exercise caution when running the undo network-entity command. Change the system ID or virtual system ID of one device to ensure that the system IDs or virtual system IDs on both ends are different. Check whether the fault is rectified.

If so, go to Step 14.
If not, go to Step 12.

12. Check whether IS-IS authentication modes and authentication passwords configured on two ends are consistent.

If so, go to Step 14.
If not, go to Step 13.

13. Run the isis authentication-mode command respectively in the two interface views to change the authentication modes and passwords to be the same. Alternatively, run the undo isis authentication-mode command respectively in the two interface views to disable IS-IS authentication. Note that disabling IS-IS authentication degrades the system security. Check whether the fault is rectified.

If so, go to Step 15.
If not, go to Step 14.

14. Collect log information and configuration information, and then contact technical support personnel.

15. End.