Filter
Top Products
Troubleshooting IP Routing BGP Troubleshooting
OmniSwitch Troubleshooting Guide September 2005 page 12-27
tOspf-: ospfNbrStateMachine: (10.40.110.3) Change! PREV LOADING; EVENT LOAD-
DONE; NEXT FULL.
(Loading of the LSAs done, spf calculations being done and the routes are getting loaded in the route
table. The state moves to Full with the neighbor.)
tOspf-: ospfAreaTimer:3356 ospfBuildRouterLsa(area 0.0.0.5, flags 0x5).
[curTime = 7410s]
tOspf-: ospfBuildRouterLsa: Built Router LSA: Area 5 Seq 0x80000003 numLinks 1
Age 0
tOspf-: ospfNbrStateMachine: NBR 10.40.110.3; EVENT HELLORX; STATE FULL.
tOspf-: ospfNbrStateMachine: NBR 10.40.110.3; EVENT 2WAYRX; STATE FULL.
tOspf-: ospfNbrStateMachine: NBR 10.40.110.3; EVENT HELLORX; STATE FULL.
Other debug-types may be enabled as per need. The output of this command is verbose so care should be
taken before enabling the debug types.
For further troubleshooting the problem contact tech support.
BGP Troubleshooting
Be sure that the BGP neighbor Operational State is 'established'. The BGP neighbor 'maximum-prefix'
default is 5000. This value may be increased to 65000, which is the limitation of the NI routing table; a
total of 64K route entries. The maximum number of BGP routes will be a subset of this number, depend-
ing on how many other routes exist (RIP, OSPF, etc.). The number of BGP routes can be learn, depends
on the system memory resources.
When the Operation State is idle or active, increasing the maximum-prefix may resolve the issue.
The following commands are used to troubleshoot BGP failures:
show ip bgp neighbors
show ip bgp routes
show ip bgp statistics
show ip bgp aggregate-address
show ip bgp path
show ip bgp network
-> show ip bgp neighbors
Legends: Nbr = Neighbor
As = Autonomous System
Nbr address As Admin state Oper state BGP Id Up/Down
---------------+-----+-----------+------------+---------------+-----------
152.23.1.9 227 enabled established 20.23.24.20 17h:00m:17s
152.23.1.10 227 enabled established 20.23.24.17 19h:21m:18s