General Bgp+ Troubleshooting; Enabling Trace And Debugging For Bgp+ Troubleshooting - Avaya 8800 Troubleshooting Manual

Unicast routing troubleshooting

General BGP+ troubleshooting

The following procedure describes additional general troubleshooting steps for BGP+.
1. First try to ping the network and see whether the network is reachable or not.
2. If the network is not reachable, then check for IGP neighbors. See whether any IGP
3. Check the topology to find any possible STP blocking states on the ports or non-
4. Also check for ARP entries of the next-hop (in case the next-hop is specified). If
5. Similarly, if Neighbor discovery for a particular IPv6 route fails, then that IPv6 route

Enabling trace and debugging for BGP+ troubleshooting

If the preceding sections do not resolve your issue, you can obtain additional BGP+ information
by using the following procedure.
1. Run the BGP trace command and see whether there is any error message in the
2. Enable debugging on BGP globally, as well as on the neighbor:
3. In addition to BGP trace and debug, you can also run RTM traces to see if the routes
366 Troubleshooting
is enabled, and whether IGP connections are established.
routable interfaces.
there is no ARP entry, then the route is not added to the route table.
is not installed in the RTM.
trace:
trace level 52 3
trace screen on
config ip bgp global-debug mask <value>
config ip bgp debug-screen on
config ip bgp neighbor <neighbor-ip> neighbor-debug mask
<value> (CLI)
global-debug mask <value>
debug-screen on
neighbor <neighbor-ip> neighbor-debug mask <value> (ACLI BGP
Router Configuration mode)
are being lost somewhere during the RTM processing.
trace level 45 3
Comments? infodev@avaya.com
July 2013