Mypower
S4100
Troubleshooting
Maipu Confidential & Proprietary Information
Page
93
of
124
10.
The opposite
interface is passive
interface (the
possibility is low)
How to find out the cause:
Use the show ip ospf neighbor command and no neighbors are
found for a long time.
Open the debug ip ospf packet hello. If the opposite hello
packets cannot be received, check whether the opposite
interface is configured to be passive interface.
Solution: remove the configuration of the passive interface.
Note: the possibility of the problem is low
11.
The router IDs of the
two OSPF negotiation
parties are duplicated
How to find out the cause:
Use the show ip ospf neighbor command and no neighbors are
found for a long time.
Open the debug ip ospf packet hello to print the following error
information: OSPF RECV Area 0.0.0.0 172.160.3.4 ->
224.0.0.5: HELLO: Router Id collision; it indicates that the router
IDs of the two parties are duplicated.
Solution:
Configure new router-ID. The command is router-id A.B.C.D.
After the configuration, use the clear ip ospf process command
to enable the configuration.
12.
The OSPF neighbor is
in the INIT status
How to find out the cause:
The OSPF uses a multicast address 224.0.0.5 to send and
receive hello packets. If the packets define an access list at an
interface and enable OSPF, the multicast address must be
allowed in the access list. Otherwise, the status may remain
INIT. The problem occurs only when one end stops OSPF. If the
two ends stop the OSPF, run the show ip ospf neighbor
command and an empty table is returned.
Run the show ip ospf neighbor command to check that the
neighbor interface is in the INIT status.
Open the debug ip ospf packet hello. Find that the interface can
receive the opposite hello packets and send its own hello
packets. At the opposite end, run the debug ip ospf packet hello
to check whether the multicast hello packets are received.
Solution:
Check whether the relevant ACL is applied at the interface.
Remove the ACL from the interface.
13.
The OSPF neighbor is
in the Attempt status
How to find out the cause:
The problem is only effective in the NBMA network that defined
neighbor statement. The Attempt status means that a routing
device attempts to send hello packets to the neighbor but
receives no response from the neighbor. The Attempt status is
not a problem for it is a common status that the routing device
should pass in the NBMA mode. If a routing device keeps the
status for a long time, it indicates a fault.
Run the show ip ospf neighbor command to find that when the
status is Attempt for a long time, the neighbor is N/A.
Solution:
Run the show run router ospf to check the neighbor statement.
If it is incorrect, change the value to the right one.
Check whether the link is connected and whether the ping
neighbor address is available.
Check the ACL configuration, if it is incorrect, remove the ACL
filtering.
14.
The OSPF neighbor is
in the two-way status
How to find out the cause:
Run the show ip ospf neighbor command to check that the
neighbor interface is in the Two-way status.
Open the debug ip ospf packet hello detail to find that the
RtrPriority fields of hello packets sent and received at the
interface are 0.
Solution:
Configure the interface or a neighbor interface priority to non-
