1-11
Cisco ASA Series CLI Configuration Guide
Chapter 1 Configuring RIP
Monitoring RIP
Monitoring RIP
We recommend that you only use the debug commands to troubleshoot specific problems or during
troubleshooting sessions with the Cisco TAC.
Debugging output is assigned high priority in the CPU process and can render the ASA unusable. It is
best to use debug commands during periods of lower network traffic and fewer users. Debugging during
these periods decreases the likelihood that increased debug command processing overhead will affect
performance. For examples and descriptions of the command output, see the command reference.
To monitor or debug various RIP routing statistics, enter one of the following commands:
Configuration Example for RIP
The following example shows how to enable and configure RIP with various optional processes:
hostname(config)# router rip 2
hostname(config-router)# default-information originate
hostname(config-router)# version [1]
hostname(config-router)# network 225.25.25.225
hostname(config-router)# passive-interface [default]
hostname(config-router)# redistribute connected [metric bandwidth delay reliability
loading mtu] [route-map map_name]
Command Purpose
Monitoring RIP Routing
show rip database
Display the contents of the RIP routing database.
show running-config router
rip
Displays the RIP commands.
show route cluster
Displays additional route synchronization details for clustering.
Debugging RIP
debug rip events
Displays RIP processing events.
debug rip database
Displays RIP database events.
debug route cluster
Enables RIB table replication trace messages to determine if the
RIB is correctly synchronized to the slave units in clustering.
To Next Page
Loading...
Need help?
General