[Trouble shooting]ISIS neighbor status is abnormal

Hi, community,

Today, let's solve the problem that IS-IS neighbor relationships cannot be established. If you have any suggestions or comments, please let me know.

1. Check the connectivity between devices and run the ping command to check whether the unicast link is normal.

2. Check whether the IS-IS configuration (level configuration, area address, and authentication) on each device is correct.

3. Check whether IS-IS is enabled on the interface of the device.

4. Check the cost of the device.

5. Run the display isis interface command to check the network status of the device interface.

6. Check whether packets are discarded on the interface. If packets are discarded, IS-IS packets are discarded.

7. Check the MTU of the device interface to check whether packet loss is caused by large packets.

8. Check the CPU statistics of the device to determine whether CPU packet loss occurs.

9. Run the display isis statistics packet interface command to check whether Hello packets contain the MAC address of the interface.

10. Check whether IS-IS error packets exist.

11. Check whether the IS-IS LSDB can receive the LSDB from the peer end. (The lsdb database status is normal.)

12. Check whether the logbuffer and trapbuffer logs contain IS-IS alarms. ( Sorry, because ensp cannot view logs, so use other images)

13. Check whether alarms related to IP address conflict exist in the logbuffer and trapbuffer logs.     

14. Check the tlv field if the device is connected to a non-Huawei device.

You can use display isis lsdb verbose commands to view the tlv

15. Check the version. If the version is EOS, upgrade the version in time.

Thank you! We’re looking forward to having you as a member!