Troubleshooting ospfv3 configuration, No ospfv3 neighbor relationship established, Symptom – H3C Technologies H3C S10500 Series Switches User Manual
Page 323: Analysis, Process steps, Incorrect routing information
308
*Nov 5 11:37:43:062 2009 SwitchA RM/6/RMDEBUG: OSPFv3 OSPFv3-BFD: Message Type delete
session, Connect Type direct-connect, Src IP Address FE80::20F:FF:FE00:1202, Dst IP
Address FE80::20F:FF:FE00:1200.
# Display the BFD information of Switch A. You can see that Switch A has removed its neighbor
relationship with Switch B and therefore no information is output.
# Display routes to 2001:4::0/64 on Switch A, and you can see that Switch A communicates with Switch
B through Switch C.
Routing Table :
Summary Count : 1
Destination : 2001:4:: PrefixLength : 64
NextHop : 2001:2::2 Preference : 10
IpPrecedence : QosLcId :
RelayNextHop : :: Tag : 0H
Neighbor : :: ProcessID : 0
Interface : Vlan-interface11 Protocol : OSPFv3
State : Invalid Adv Cost : 2
Tunnel ID : 0x0 Label : NULL
Age : 4610sec
Troubleshooting OSPFv3 configuration
No OSPFv3 neighbor relationship established
Symptom
No OSPF neighbor relationship can be established.
Analysis
If the physical link and lower protocol function properly, check OSPF parameters configured on interfaces.
The two neighboring interfaces must have the same parameters, such as the area ID, network segment
and mask, and network type. If the network type is broadcast, at least one interface must have a DR
priority higher than 0.
Process steps
1.
Display neighbor information using the display ospfv3 peer command.
2.
Display OSPFv3 interface information using the display ospfv3 interface command.
3.
Ping the neighbor router’s IP address to check connectivity.
4.
Check OSPF timers. The dead interval on an interface must be at least four times the hello interval.
5.
On a broadcast network, at least one interface must have a DR priority higher than 0.
Incorrect routing information
Symptom
OSPFv3 cannot find routes to other areas.