[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Monitoring RIP
Two sets of commands enable you to monitor RIP
operation on your router: the debug and the show commands. Both sets
of commands provide information about your router’s RIP state
and configuration.
The task you are performing with each of these
monitoring commands is basically the same for each command; that is,
you are requesting information. The results of this request may vary.
For instance, the debug commands provide information about problems
with the network or the router, whereas the show commands provide
information about the actual state and configuration of your router.
debug Commands
The debug commands provide information about the following
RIP items:
- General events, such as creating a RIP process or removing
RIP from an interface
- Routing events, such as when two RIP routers exchange
routes
debug ip rip
- Use to display information about selected RIP events.
This command has many keywords that allow you to specify a variety
of RIP events.
- You can set the level of severity for the events you want
displayed; specify the desired descriptive term or a corresponding
number (0–7).
- You can set the verbosity of the messages you want displayed:
low, medium, high.
- Example
- host1#debug ip rip events
- Use the no version to cancel
the display of any information about the designated variable.
- See debug ip rip
undebug ip rip
- Use to cancel the display of information about a selected
event.
- The same RIP variables can be designated as in the debug
ip rip command.
- Example
- host1#undebug ip rip events
- There is no no version.
- See undebug ip rip
show Commands
Use the show commands to monitor the following
types of RIP information:
- Configuration
- IP-related information
- Global counters
- Counters for a specified network
- Statistics
You can set a statistics baseline for RIP interfaces
by using the baseline ip rip command.
You can specify a VRF instance for the show ip rip commands. You can use the output filtering
feature of the show command to include
or exclude lines of output based on a text string you specify. See Command-Line Interface in the JUNOSe System Basics Configuration Guide,
for details.
baseline ip rip
- Use to set a statistics baseline for RIP interfaces.
- The router implements the baseline by reading and storing
the statistics at the time the baseline is set and then subtracting
this baseline whenever baseline-relative statistics are retrieved.
- Use the optional delta keyword
with the show ip rip statistics command
to specify that baselined statistics are to be shown.
- Example
- host1#baseline ip rip
- There is no no version.
- See baseline ip rip
show ip rip
- Use to display RIP information.
- Specify vrf vrfName to limit the display to a specific VRF.
- Use the ifconfig keyword to
display address and interface configuration information instead of
the default operational data.
- Field descriptions
- Router Information Protocol Fields
- Router Administrative State—Displays the RIP state.
Enable means the router is allowed to send and receive updates. Disable
means that RIP might be configured but it is not allowed to run yet.
- System version RIP1—RIP versions allowed for sending
and receiving RIP updates. The router version is currently set to
RIP1, which sends RIPv1 but will receive RIPv1 or RIPv2. If it is
set to RIP2, it will send and receive RIPv2 only. The default is configured
for RIP1.
- Incoming filters—Access list applied to incoming
route updates
- Outgoing filters—Access list applied to outgoing
route updates
- Global route map—Route map that specifies all RIP
interfaces on the router
- Default metric—Value for redistributed routes. The
default is 1. This global value is superseded by metrics applied to
a RIP interface.
- Distance—Value added to RIP routes added to the
IP routing table. The default is 120.
- Number of route changes—Number of times the router
has been told to route changes by its peers
- Number of route queries—Number of times the router
has received route requests from other routers
- Update interval—Current setting of the update timer
(in seconds)
- Invalid interval—Current setting of the invalid
timer (in seconds)
- Hold down time—Current setting of the hold-down
timer (in seconds)
- Flush interval—Current setting of the flush timer
(in seconds)
- Route Type—Whether RIP routes are available only
for unicast forwarding, only for multicast reverse path forwarding
checks, or for both
- Max Ecmp Paths—Number of parallel routes that RIP
can support
- Default-Information originate always—Ability (enabled
or disabled) of RIP to advertise a default route (0.0.0.0/0) if the
default route exists in the IP routing table
- Triggered Updates—Ability (enabled or disabled)
of RIP to send triggered updates
- Purge Routes on Interface Down Event—Ability (enabled
or disabled) of RIP to purge the routing table for interfaces that
were brought down by some event
- Send More Specific Routes—Ability (enabled or disabled)
of RIP to send a less-specific route in preference to a more-specific
route if the less-specific route has a metric
- Debounce Time—Debounce time for interfaces brought
down by some event
- Default-Information originate—Ability (enabled or
disabled) of RIP to advertise a default route (0.0.0.0/0) if the default
route exists in the IP routing table
- route-map—Name of the route map specified for RIP
- Summary Address—Route that RIP summarizes
- Network—IP address of a network on which RIP is
running
- Netmask—Network mask applied to the network address
- Neighbor—Configured neighbor information
- Address Operational Data
- Unnumbered status—Status of the unnumbered interface
- Received bad packet—Number of bad packets received
- Received bad routes—Number of bad routes received
- Triggered updates sent—Number of triggered updates
sent; triggered updates are sent before the entire RIP routing table
is sent; triggered by events such as adding a new RIP route or redistribution
- Received updates—Number of updates received
- Numbered status—Status of the numbered interface
from which this interface obtains its configuration
- Send version—Version of RIP used for sending updates
- Receive version—Version of RIP accepted in received
updates
- Authentication mode—Password or MD5 authentication,
or none
- Default metric—Metric value applied to the RIP interface.
The default
is 1.
- BFD minimum receive interval(msec)—Configured minimum
interval requested between BFD control packets sent by the remote
RIP peer; used with RIP peers to negotiate a detection interval for
BFD session failure. The default is 300 milliseconds.
- BFD minimum transmit interval(msec)—Configured minimum
interval between BFD control packets sent by the local RIP peer; used
with RIP peers to negotiate a detection interval for BFD session failure.
The default is 300 milliseconds.
- BFD multiplier—Multiplied by the negotiated BFD
minimum receive interval to determine the interval between packets
permitted before the BFD session is declared down. Also, the number
of BFD control packets that the RIP local peer can miss before the
BFD session is declared down. The default is 3.
- Passive Interface—Whether or not the interface is
passive, thereby restricting the interface to unicast RIP messages
- Passive Interface—Whether or not the interface is
passive, thereby restricting the interface to unicast RIP messages
- Access-list applied to outgoing route—Name of the
access list applied to outgoing routes
- Access-list applied to incoming route—Name of the
access list applied to incoming routes
- Route-map applied to outgoing route—Name of the
route map applied to outgoing routes
- Example 1
host1#show ip rip
Routing Information Protocol
Router Administrative State = enable
System version RIP2: send = 2, receive = 2
No filter is applied to outgoing route update for all interfaces
No filter is applied to incoming route update for all interfaces
No global route map
No table map
Default metric = 1
Distance = 120
Number of route changes = 3
Number of route queries = 0
Update interval = 30 (secs)
Invalid interval = 180 (secs)
Hold down time = 120 (secs)
Flush interval = 300 (secs)
Route Type = both unicast and multicast
Max Ecmp Paths = 4
Default-Information originate always = enabled
Triggered Updates = enabled
Purge Routes on Interface Down Event = enabled
Send More Specific Routes = enabled
Debounce Time = 10
Default-Information originate : disabled
route-map : none
Summary Address: None
Network netmask
Neighbor
No Configured Neighbors
*** Address Operational Data ***
Unnumbered, Rip is up, ATM2/1.18
Dynamic creation and inherits configuration from loopback1
Received bad packet = 0
Received bad routes = 0
Triggered updates sent = 0
Received updates = 9
1.1.1.1, Rip is up, loopback1
Send version = 2
Receive version = 2
Authentication mode = none
Default metric = 1
Passive Interface = No
Access-list applied to outgoing route = none
Access-list applied to incoming route = none
Route-map applied to outgoing route = none
Copy configuration to dynamic interfaces
Received bad packet = 0
Received bad routes = 0
Triggered updates sent = 0
Received updates = 0
- Example 2
host1#show ip rip ifconfig
Routing Information Protocol
Router Administrative State = enable
System version RIP2: send = 2, receive = 2
No filter is applied to outgoing route update for all interfaces
No filter is applied to incoming route update for all interfaces
No global route map
No table map
Default metric = 1
Distance = 120
Number of route changes = 17
Number of route queries = 2
Update interval = 30 (secs)
Invalid interval = 180 (secs)
Hold down time = 120 (secs)
Flush interval = 300 (secs)
Route Type = both unicast and multicast
Max Ecmp Paths = 4
Default-Information originate always = enabled
Triggered Updates = enabled
Purge Routes on Interface Down Event = enabled
Send More Specific Routes = enabled
Debounce Time = 10
Default-Information originate : disabled
route-map : none
Summary Address: None
Network netmask
Neighbor
No Configured Neighbors
*** Interface Configuration Data***
loopback1
Send version = def
Receive version = def
Authentication mode = none
Default metric = default
Passive Interface = No
Access-list applied to outgoing route = none
Access-list applied to incoming route = none
Route-map applied to outgoing route = none
Copy configuration to dynamic interfaces
*** Address Configuration Data ***
Unnumbered, Rip is up, ATM2/1.18
Dynamic creation and inherits configuration from loopback1
Received bad packet = 0
Received bad routes = 0
Triggered updates sent = 0
Received updates = 3
1.1.1.1, Rip is up, loopback1
Send version = def
Receive version = def
Authentication mode = none
Default metric = default
Passive Interface = No
Access-list applied to outgoing route = none
Access-list applied to incoming route = none
Route-map applied to outgoing route = none
Received bad packet = 0
Received bad routes = 0
Triggered updates sent = 0
Received updates = 0
- Example 3—Interface configuration data excerpt showing
BFD information.
host1#show ip rip ifconfig
*** Interface Configuration Data***
FastEthernet1/0
Send version = def
Receive version = def
Authentication mode = none
Default metric = default
BFD minimum receive interval(msec) = 400
BFD minimum transmit interval(msec)= 500
BFD multiplier = 2
Passive Interface = No
Access-list applied to outgoing route = none
Access-list applied to incoming route = none
Route-map applied to outgoing route = none...
- See show ip rip
show ip rip brief
show ip rip database
show ip rip network
show ip rip peer
- Use to display limited information about each RIP neighbor.
- Specify vrf vrfName to limit the display to a specific VRF.
- Field descriptions
- Time since last update received—Time in seconds
since an update was received from this peer
- Peer version—Version of IS-IS running on the peer
- Bad packets received—Number of bad packets received
from the peer
- Bad routes received—Number of bad routes received
from the peer
- BFD—State of the BFD session with the peer, Up or
Down
- Example
host1#show ip rip peer
192.168.1.102
Time since last update received = 24
Peer version = 1
Bad packet received = 0
Bad routes received = 0
BFD Up
192.168.1.151
Time since last update received = 24
Peer version = 1
Bad packet received = 0
Bad routes received = 0
BFD Down
192.168.1.250
Time since last update received = 7
Peer version = 2
Bad packet received = 0
Bad routes received = 0
BFD Up
- See show ip rip peer
show ip rip statistics
- Use to display global and session statistics counters
for RIP. If you specify an IP address, statistics for that interface
are displayed in addition to the global RIP statistics.
- Specify vrf vrfName to limit the display to a specific VRF.
- Use the optional delta keyword
to specify that baselined statistics are to be shown. You must use
the baseline ip rip command to set a baseline.
- Field descriptions
- Number of route changes—Number of times the router
has been told to route changes by its peers
- Number of route queries—Number of times the router
has received route requests from other routers
- Received bad packets—Number of bad packets received
from the peer
- Received bad routes—Number of bad routes received
from the peer
- Triggered updates sent—Number of triggered updates
sent; triggered updates are sent before the entire RIP routing table
is sent; triggered by events such as adding a new RIP route or redistribution
- Received updates—Number of updates received
- Example 1
host1#show ip rip statistics
Number of route changes = 23
Number of route queries = 0
- Example 2
host1#show ip rip statistics 10.2.1.32
Number of route changes = 901
Number of route queries = 0
fastEthernet 0/0, 10.2.1.32
Received bad packet = 0
Received bad routes = 0
Triggered updates sent = 2
Received updates = 41
- See show ip rip statistics
show ip rip summary-address
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]