OcNOS-RON : Troubleshooting Guide : Layer 3 Routing : OSPFv3
OSPFv3
This section contains steps to resolve OSPFv3 issues.
Neighborship Formation
 
Symptom/Cause
Solution
OSPF not enabled on the interface or the corresponding interface is down
Use network command to enable OSPFv3 on a particular network address. Do no shutdown on the corresponding interface. Use these commands:
 
show ipv6 ospf interface
show ipv6 ospf
show running-config ospfv3
show ipv6 ospf neighbor
show ipv6 ospf neighbor detail
Hello packet attribute mismatch i.e. interface hello interval or dead interval mismatch
Use these commands to find the output/mismatch:
 
show running-config ospfv3
show ipv6 ospf interface
debug ipv6 ospf nfsm
debug ipv6 ospf packet hello detail
OSPF option field mismatch i.e. Ospf External Routing Capability mismatch due to stub area mismatch
Configure the same stubby-area. Use these commands:
 
debug ipv6 ospf packet hello
show ipv6 ospf
show running-config ospfv3
OSPF gets stuck in two-way state when there is no DR/BDR elected i.e. both routers configuration with priority 0
One router should be configured with a priority other than 0. Use these commands:
 
show ipv6 ospf neighbor
show running-config ospfv3
OSPF can get stuck in Exstart/Exchange state when the maximum transmission unit (MTU) does not match
Use these commands:
 
show ipv6 ospf interface
show running-config ospfv3
show ipv6 ospf neighbor
OSPF network type mismatch can cause timers (hello-interval) mismatch
Use these commands:
 
show ipv6 ospf interface
debug ipv6 ospf packet hello
show running-config ospfv3
OSPF same router-id and loopback address
Use these commands:
 
show ipv6 ospf
show running-config ospv3
show ipv6 ospf interface
Ospf area mismatch for virtual-link
Use these commands:
 
show running-config ospfv3
show ipv6 ospf virtual-link
OSPF virtual-link router-id mismatch cause virtual-link down.
Use these commands:
 
show running-config ospfv3
show ipv6 ospf virtual-link
show ipv6 ospf interface
show ipv6 ospf neighbor
OSPF vlink Global remote address is NULL causing virtual-link adjacency down.
Use these commands:
 
show ipv6 ospf interface
show ipv6 ospf virtual-link
OSPF not enabled on the interface or the corresponding interface is down causing vlink down.
Use these commands:
 
show ipv6 ospf
show running-config ospfv3
show ipv6 ospf virtual-link
show ipv6 ospf interface
Last modified date: 06/16/2023