OmniSwitch OS6860/OS6900/OS10K Troubleshooting Guide Part No.032996-00 Rev.A
AOS Release 7.X and 8.X January 2015
Alcatel-Lucent Page 85 of 148
12. Troubleshooting OSPF
Checklist
Make sure that neighbors use the same MTU size
OSPF maximum packet size is hardcoded to 4 KB (to make sure that 8 KB out buffer is not fully used), but
OSPF can still negotiate greater MTU size.
Summary of the commands in this chapter is listed here:
____________________________________________________________________
show configuration snapshot ospf ip
show ip ospf
show ip ospf neighbor
show ip ospf interface
show ip ospf interface <interface>
show ip ospf area
show ip ospf ar
ea <are
a id>
show ip ospf lsdb
show vrf
____________________________________________________________________
12.1. Supported debug variables
areamaxintfs default is 200 interfaces per area
debug ip ospf set noloopback0 1
debug ip ospf set nostubloopback0 1
debug ip ospf set subsecond 1
debug ip ospf set bfdsubsecond 1
debug ip ospf set areamaxintfs <n>
OSPF 150ms link convergence made it in the GA build for 7.1.1.R01.
You have to enable it as follows:
debug ip ospf set subsecond 1
Further enhancement has been done to extend this feature in combination with BFD.
From Build 7.1.1.1673.R01 onwards (not sure if this is post-GA or not), if you need the same behavior (i.e.
sub-second reconvergence) on BFD events in OSPF, you can enable:
debug ip ospf set bfdsubsecond 1
12.2. Planned and unplanned Virtual Chassis takeover
This technical document explains how OSPF graceful restart (unplanned) feature can be used on AOS7 Virtual
Chassis to achieve sub-second convergence during Virtual Chassis takeover.
Overview on OSPF task in AOS7 VC
According to current AOS architecture, the control/management functions are performed by CMM and data
forwarding functions are performed by NI. OSPF task runs in control plane building the forwarding
information which will be used by the data plane for data forwarding. OSPF task functions in centralized mode
To Next Page
Loading...
