ISIS/5/IS_ADJ_CHANGE

Message

ISIS/5/IS_ADJ_CHANGE: ISIS-INFO: ISIS adjacency state changed. (IfName=[IfName], AdjLevel=[AdjLevel], NbrSysId=[NbrSysId], AdjState=[AdjState], AddressFamily=[AddressFamily], Reason=[Reason], LastSendHelloTime=[LastSendHelloTime], LastRecvHelloTime=[LastRecvHelloTime], CpuUsage=[CpuUsage]%)

Description

The status of the neighbor changed.

Parameters

Parameter Name	Parameter Meaning
IfName	Name of a corresponding interface on a neighbor.
AdjLevel	Level of the neighbor whose status changes.
NbrSysId	ID of an LSP.
AdjState	Former status of a neighbor: 1: Down. 2: Init. 3: Up.
AddressFamily	Address family of a neighbor.
Reason	Cause of the neighbor status change.
LastSendHelloTime	Time when the Hello packet was last sent.
LastRecvHelloTime	Time when the Hello packet was last received.
CpuUsage	CPU usage.

Possible Causes

1. The hold timer of the IS-IS neighbor expired.(The neighbor HoldTimer expires.)

2. The physical interface went Down.(The interface is Down.)

3. Protocols are incorrectly configured.(protocol cause).

4. BFD detected that the neighbor went Down.(BFD detects that the neighbor is Down.)

5. The IS-IS configuration changed.(configuration change).

6. The problem is caused by the remote device.(The peer device is faulty.)

Cause 100: The alarm was cleared.(The alarm is cleared.)

Procedure

Check whether the adjacency HoldTimer expired.

1. Run the ping command to check whether two link ends are properly connected.

If the ping succeeds, go to Step 2.
If the ping fails, go to Step 4.

2. Run the display this in the IS-IS view and in the interface view of the remote end to check whether IS-IS is correctly configured.

If IS-IS is correctly configured, go to Step 3.
If IS-IS is not correctly configured, go to Step 5.

3. Run the display cpu-usage command to check whether the CPU usage is too high.

If the CPU usage is too high, go to Step 5.
If the CPU usage is normal, go to Step 6.

4. Run the display this command in the interface view to check whether the link between two ends is correctly configured. If the link is configured incorrectly, correct the configurations. Then run the display isis peer command to check whether the status of the IS-IS neighbor relationship between two ends is Up.

If IS-IS neighbor relationship status is Down, go to Step 5.
If IS-IS neighbor relationship status is Up, no action is required.

5. Run the display current-configuration command in the system view to check configurations of two ends. If the two ends are incorrectly configured, correct the configurations.Then run the display isis peer command to check whether the status of the IS-IS neighbor relationship between two ends is Up.

If IS-IS neighbor relationship status is Down, go to Step 6.
If IS-IS neighbor relationship status is Up, no action is required.

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

Check whether the physical interface went Down.

1. Run the display isis interface command or the display interface brief command to check whether interface status is Down.

If interface status remains Down, go to Step 2.
If interface status is Up, go to Step 3.

2. Change configurations and then check whether interface status changes to Up.

If interface status is Up, go to Step 3.
If interface status remains Down, go to Step 4.

3. Run the display isis peer command to check whether IS-IS neighbor relationship status is Up.

If IS-IS neighbor relationship status is Down, go to Step 4.
If IS-IS neighbor relationship status is Up, no action is required.

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

Check whether the CPU usage was too high due to a protocol problem.

1. Run the display memory-usage command to check whether the CPU usage is too high.

If the CPU usage is normal, go to Step 2.
If the CPU usage is too high, no action is required.

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

Check whether the neighbor went Down.

1. Run the ping command to check whether two link ends are properly connected.

If the ping succeeds, go to Step 3.
If the ping fails, go to Step 2.

2. Run the display this command in the interface view to check whether the link between two ends is correctly configured. - If the link is configured incorrectly, correct the configurations. Then run the display isis peer command to check whether the status of the IS-IS neighbor relationship between two ends is Up.

If IS-IS neighbor relationship status is Down, go to Step 3.
If IS-IS neighbor relationship status is Up, no action is required.

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

Check whether configurations changed.

1. Check whether some recently changed configurations affect the establishment of the IS-IS neighbor relationship.

If there are some configurations affecting the establishment of the IS-IS neighbor relationship, go to Step 2.
If there is no configuration affecting the establishment of the IS-IS neighbor relationship, go to Step 4.

2. Check whether changed configurations meet users' requirements.

If the changed configurations meet users' requirements, no action is required.
If the changed configurations do not meet users' requirements, go to Step3.

3. Restore the original configurations and then check whether IS-IS neighbor relationship status is Up.

If IS-IS neighbor relationship status is Down, go to Step 4.
If IS-IS neighbor relationship status is Up, no action is required.

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

Check whether the peer router was incorrectly configured or the neighbor relationship was not established.

1. Check whether the remote end is configured correctly.

If the configuration of the remote end is incorrect, go to Step 2.
If the configuration of the remote end is correct, go to Step 3.

2. Correct the configuration of the remote end and then check whether IS-IS neighbor relationship status is Up.

If IS-IS neighbor relationship status is Down, go to Step 3.
If IS-IS neighbor relationship status is Up, no action is required.

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