ISIS/3/ISIS_REJECTED_ADJACENCY
Message
ISIS/3/ISIS_REJECTED_ADJACENCY: IS-IS failed to establish the adjacency with its peer. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])
Description
The local received Hello packets sent from the neighboring but failed to establish IS-IS neighbor relationships with it.
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
[isisSysInstance] |
ID of an IS-IS process |
[isisSysLevelIndex] |
IS-IS level |
[isisCircIndex] |
Circuit index of an interface |
[isisCircIfIndex] |
Circuit IfIndex of an interface |
[isisPduFragment] |
64-byte PDU header |
[ifIndex] |
IfIndex of an interface |
[IfName] |
Interface name |
Possible Causes
Cause 1: The system ID or virtual system ID on the local was identical to that on the neighboring .
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
- 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.
- Check the isisPduFragment field, and then identify
the source 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.
- 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.
- Run the display ip interface command to check whether
the IP addresses of the source interface and the local interface
are on the same network segment.
If so, go to Step 8.
If not, go to Step 5.
- Run the ip address command respectively in the source 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.
- Run the display this command respectively in the source
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.
- Run the isis peer-ip-ignore or ip address command
respectively in the source 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.
- 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.
- 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.
- Run the display current-configuration command to check whether the system ID of the source is
the same as the system ID or virtual system ID on the local .
If so, go to Step 11.
If not, go to Step 12.
- Exercise caution when running the undo network-entity command. Change the system ID or virtual system ID of one 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.
- 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.
- 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.
- Contact technical support personnel technical support personnel.
- End.
