Troubleshooting: OSPF Neighbor Down in SGSN9810

[复制链接]
selim.hasan   钻石会员    发表于 2014-9-21 20:04:21   最新回复:2018-05-30 13:46:58

Description

This alarm is generated and cleared in the following scenarios:

·         This alarm is generated when the Open Shortest Path First (OSPF) neighboring status changes from a state higher than Way_2 to Way_2 or a lower state. This alarm is cleared when the OSPF neighboring status changes back toFull.

·         If the network type is broadcast or non-broadcast multiple access (NBMA), this alarm is generated when the neighboring status between the designated router (DR) others changes from Way_2 to a lower state, and is cleared when the DR other neighboring status changes back to Way_2.

·         This alarm is generated when there is no OSPF neighbor whose status is Full on the OSPF interface, and both Nbr Route ID and Nbr Interface address are 255.255.255.255. This alarm is cleared when there is an OSPF neighbor whose status is Full.

·         An OSPF router ID uniquely identifies an OSPF neighbor down alarm. When there is an OSPF neighbor down alarm in USN, another OSPF neighbor down alarm with the same OSPF router ID triggered at this time will be treated as a duplicate alarm and it will not be reported.

Impact on the System

·         If this alarm is triggered by the OSPF neighbor, routes passing through this neighbor are deleted, affecting services transmitted on these routes.

·         If this alarm is triggered by OSPF interface faults, route learning is disabled on the OSPF interface, affecting services transmitted on these routes.

Possible Causes

·         The link or port is faulty.

·         The configurations on the local and peer ends are inconsistent.

·         Packets are lost because the traffic threshold is exceeded.

Procedure

1.     Check whether Nbr Route ID and Nbr Interface address in the alarm are both 255.255.255.255.

·         Yes: Go to 2.

·         No: Go to 7.

2.     Check whether there is another ALM-11914 OSPF Neighbor Down alarm. If yes, view the alarm information to check whether Subrack No.Slot No.Interface TypePort No. and Subinterface No. are identical with those of this alarm, and whether the values of Nbr Route ID and Nbr Interface address are valid IP addresses.

·         Yes: Go to 3.

·         No: Go to 4.

3.     View the handling suggestions of ALM-11914 OSPF Neighbor Down. Try to clear the alarm generated by the OSPF neighbor of the local OSPF interface, and check whether this alarm is cleared.

·         Yes: No further action is required.

·         No: Go to 4.

4.     Contact the customer and check whether configurations of the local interface have been modified or new configurations have been added.

·         Yes: Go to 5.

·         No: Go to 26.

5.     Check whether the corresponding configuration of the peer device is modified.

·         Yes: Go to 26.

·         No: Go to 6.

6.     Add or modify the corresponding configuration of the peer end, and check whether this alarm is cleared.

·         Yes: No further action is required.

·         No: Go to 26.

7.     Run In the MML interface of the CGP, run the commandLST OPTLOG to obtain the operation logs, and check whether there are entries related to RST OSPFPRCSS when this alarm is generated.

·         Yes: This alarm will be cleared automatically, and no further action is required.

·         No: Go to 8.

8.     Check whether there is an ALM-1023 Board Port Fault alarm for the port generating this alarm.

·         Yes: Go to 9.

·         No: Go to 11.

9.     View the handling suggestions of ALM-1023 Board Port Fault, and rectify the port faults.

10.  Check whether this alarm persists.

·         Yes: Go to 11.

·         No: No further action is required.

11.  Run In the MML interface of the USN9810, run the commandDSP IFIP to check whether the local interface IP address exists.

·         Yes: Go to 13.

·         No: Go to 12.

12.  Run In the MML interface of the USN9810, run the commandADD IFIP to add a local IP address, and check whether this alarm persists.

·         Yes: Go to 13.

·         No: No further action is required.

13.  Run In the MML interface of the USN9810, run the commandPING to check whether the link from the usn9810 to the peer device is normal.

·         Yes: Go to 14.

·         No: Go to 27.

14.  Check whether there is an ALM-11935 Process CPU Overload alarm.

·         Yes: Go to 15.

·         No: Go to 17.

15.  View the handling suggestions of ALM-11935 Process CPU Overload, and rectify the faults.

16.  Check whether this alarm persists.

·         Yes: Go to 17.

·         No: No further action is required.

17.  Run In the MML interface of the USN9810, run the commandDSP BFDSESSION to check whether the relevant OSPF process has initiated a BFD session and whether the status of the BFD session is Down.

·         Yes: Go to 18.

·         No: Go to 20.

18.  Check the BFD session configurations bound with the OSPF process on the local and peer ends, and rectify the BFD session faults.

19.  Check whether this alarm persists.

·         Yes: Go to 20.

·         No: No further action is required.

20.  Run In the MML interface of the USN9810, run the commandDSP OSPF with Protocol type set to NW, and check whether the OSPF interface information exists.

·         Yes: Go to 22.

·         No: Go to 21.

21.  Run In the MML interface of the USN9810, run the commandADD OSPFNW to add an OSPF interface, and check whether this alarm persists.

·         Yes: Go to 22.

·         No: No further action is required.

22.  Run In the MML interface of the USN9810, run the commandDSP OSPF with Protocol type set to INTERFACE, to check the interface status. If the interface status is DRBackupDRDR Other, or P To P, the interface operates properly.

·         Yes: Go to 23.

·         No: Go to 26.

23.  Run In the MML interface of the USN9810, run the commandDSP OSPF with Protocol type set to PEERINFO to check whether the DR and BDR neighboring status of the interface is Full.

·         Yes: Go to 24.

·         No: Go to 26.

24.  Run In the MML interface of the USN9810, run the commandDSP OSPF with Protocol type set to PEERINFO to check whether neighboring records exist, the neighboring status is Way_2, and the DR address and BDR address are displayed in the command output.

·         Yes: Go to 25.

·         No: Go to 26.

25.  Right-click the alarm record and select Manually Clear Alarm, and run In the MML interface of the USN9810, run the commandCLR OSPFALMFLG to clear the alarm flag.


After ALM-11914 OSPF Neighbor Down is manually cleared, run CLR OSPFALMFLG to clear the alarm flag, so that the alarm will not be reported after the EPU/EPUB/ESU switchover.

26.  Instruct the engineers of the peer device to check whether all the following conditions are met:

·         The IP address of the peer device is in the same network segment as the IP address of the local device.

·         The MTU, OSPF area, OSPF NW, and authentication type of the interface are the same as those of the local device.

·         The OSPF router ID is unique within the area.

·         The priority of the interface is proper.

·         Yes: Go to 28.

·         No: Go to 27.

27.  Instruct the engineers of the peer device to restore the link to the peer device or modify corresponding configurations, and then check whether this alarm persists.

·         Yes: Go to 28.

    • No: No further action is required.
  1. Contact Huawei technical support.


本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?注册

x
跳转到指定楼层
mehedi_hassan   银牌会员    发表于 2014-9-26 18:21:12

good document. its helpful
ahleemon   白金会员    发表于 2014-9-27 23:38:25

very good
user_2837311   钻石会员    发表于 2018-5-30 13:46:58

useful document, thanks
Have a nice day
快速回复 返回顶部