Using Bgp Debugging Commands - Avaya 8800 Troubleshooting Manual

Software troubleshooting tool configuration using CLI
assert <true=1|false=2>
bstrap <true=1|false=2>
group <ipaddress>
hello <true=1|false=2>
info
joinprune <true=1|
false=2>
pimdbglog <true=1|
false=2>
pimdbgtrace <true=1|
false=2>
rcv <true=1|false=2>
register <true=1|
false=2>
regstop <true=1|
false=2>
rp-adv <true=1|false=2>
send <true=1|false=2>
source <ipaddress>

Using BGP debugging commands

Use global and peer debug commands to display specific debug messages for your global and
peers BGP configuration, including the BGP neighbors.
You can use these commands to troubleshoot your BGP configuration.
Procedure steps
1. Display specific debug messages for your global BGP configuration using the
144 Troubleshooting
Variable
following command:
Comments? infodev@avaya.com
Value
Displays the assert debug traces.
Displays bootstrap debug traces.
Displays debug traces from a specific group IP
address.
Displays hello debug traces.
Displays the current PIM debug trace flag settings on
the switch.
Displays join/prune debug traces.
Enables or disables whether the switch logs debug
traces.
Enables or disables PIM debug traces.
Displays trace messages received by the switch.
Displays register debug traces.
Displays register stop debug traces.
Displays RP advertisement debug traces.
Displays trace messages forwarded by the switch.
Displays debug traces from a specific source IP
address.
July 2013