
Configuring Global BGP Parameters
308628-15.0 Rev 00
3-29
Configuring BGP Message Logging
By default, the router logs only a few event messages generated by BGP. To
troubleshoot a problem, you can configure the router to log BGP event messages
for the entire router or for a specific peer-to-peer session by specifying:
• Local and remote addresses of a peer-to-peer session or sessions
• Message severity level: fault, warning, information, trace, debug, or all levels
• BGP message type: open, keepalive, update, or notification
When you are not troubleshooting a problem, configure BGP message logging to
limit the number of debug messages that BGP generates and logs. If you allow
BGP to log all debug messages, the debug messages will overrun and overwrite
the log file.
Using the BCC
To configure BGP event message logging, go to the debug-control prompt (for
example,
box; ip; /jointfilesconvert/97454/bgp; debug-control
or
box; ip; /jointfilesconvert/97454/bgp; peer/2.2.2.2/2.2.2.4;
debug-control
) and enter:
log-message-type {debug
|
info
|
warning
|
fault
|
trace
|
all-levels}
log-packet-type {disabled
|
open
|
update
|
notification
|
keepalive}
To disable event message logging, set the
log-packet-type
parameter to
disabled
(the default value).
Note:
For more information about event messages, see the BayRS event
message database at http://www25.nortelnetworks.com/library/tpubs/events.
(You also can access the event message database from the BayRS
documentation CD.)
Comentários a estes Manuais