RSW RIP troubleshooting on X-series

book

Article ID: 168761

calendar_today

Updated On:

Products

CPM XOS

Issue/Introduction

There appear to be issues with the Routing Information Protocol (RIP) running on an X-Series VAP group.

The following high-level generic steps can be used to more closely identify the nature of the issues. Commands are followed by a brief description of the information provided in the output, with suggestions of areas to investigate, if relevant.

Resolution

  1. Gather the following information by running the relevant commands in the XOS CLI:
# show ap-vap-mapping
Identify the master VAP for the VAP group having issues

# show routing-protocol vap-group <name>
# show routing-protocol rip status
# show routing-protocol sync-circuit (
Optional for DBHA configurations)
Show the running status of the RSW protocols.
 
# show flow active verbose destination-port 520 protocol 17
# show flow active verbose source-port 520 protocol 17

RIP uses UDP/520 port for communication.
Identify if there are flow entries for the master VAP. If there are not, is there a pass-to-master rule in the VAP group configuration?
The Routing Information Protocol (RIP) version 2 group address 224.0.0.9 is used to send routing information to all RIP2-aware routers on a network segment.
  1. Enter ZebOS CLI for RIP:
# routing-protocol rip vap-group <name> vdname <vdname> configure
(The vdname specification is only required for VSX.)

# show ip protocols rip
Show the RIP process status.

# show ip rip  
Show RIP routes.

# show ip rip database
Show RIP route database content.

# show ip rip interface
Show RIP interface information.

Use the following steps to collect debugging data:
#show debugging rip
Verify the current RIP debug status.

# configure terminal
(config)# log file <path>

Store the debug output in a file.

(config)# debug rip <all | events | nsm | packet>
For a complete debug flags list, refer to RIP command reference guide.

To turn off debugging:
# configure terminal
(config)# no log file <path>
(config)# no debug all
  1. Return to the XOS CLI:
# configure routing-protocol rip vap-group <name> vdname <vdname> < stop | start | restart >
(The vdname specification is only required for VSX.)
Perform some action on a RIP instance: start/stop/restart
  1. Enter the NSM CLI and verify which routes you see there compared to the RIP CLI:
# routing-protocol-services vap-group <name> vdname <vdname> configure 
NSM is in charge of actual route installation/removal on the VAPs.

# show ip route database rip
# show ip route rip

Use the "show ip route database" command to list all the routes received by NSM.  When multiple entries are available for the same prefix, NSM uses an internal route selection mechanism based on protocol administrative distance and metric values to choose the best route. All best routes are entered into the FIB and can be viewed using the show ip route command. The routes added to the FIB are marked with an asterisk (*). When multiple routes are available for the same prefix, the best route is indicated with the ">" symbol. Unselected routes have neither the * nor the > symbol.
Use the "show ip route" command to list only routes that are selected by NSM and installed in the FIB.
  1. Enter the master VAP:
# un su
# rsh <master_vap>


# vsenv <VSID>
(Optional, for VSX)

# ip route (should show ECMP routes as well)
# ip route get
or
# ip route get <route>

Show all routes or just a particular route.

# ip route show cache
# ip route show cache <IP>
# ip -s route show cache <IP>

Show routing cache with statistics.

# ip route flush cache
Flush the cache.

# /crossbeam/bin/rsw-service-wrapper  nsm status
# /crossbeam/bin/rsw-service-wrapper -i <VSXID> nsm status

Get the NSM status. Use the second version of the command, specifying the VSXID for VSX.

# /crossbeam/bin/rsw-service-wrapper ripd status
# /crossbeam/bin/rsw-service-wrapper -i <VSXID> ripd status

Get RIP status. Use the second version of the command, specifying the VSXID for VSX.

# tcpdump -eni <IFname> udp port 520
Check to see if there is traffic on port 520/UDP.
  1. Back up the RSW configuration from CPM Unix prompt for review:
# tar czvf /var/tmp/rsw_conf.tgz  /tftpboot/<vapname>_?/crossbeam/etc/zebos/* 
 

Workaround

N/A