32.3. RIP diagnostics and statistics

32.3.1. RIP diagnostics

To display the diagnostics of the RIP resource the following commands are used:

d d rip / d de rip

Shows diagnostic information, such as the state of the resource, the state of the RIP routing table, the current percentage of routings present into the routing table, the current number of routings present into the routing table, the maximum number of routings reached from start-up into the table, the MAX-ROUTES parameter present into RIP resource.

[18:06:40] ABILIS_CPX:d d rip

RES:Rip -----------------------------------------------------------------------
       Routing_Information_Protocol
       STATE:READY
       ------------------------------------------------------------------------
       RIP ROUTINGs TABLE Diagnostics
       -----------|---State---|-Current%--|--Current--|---Peak----|----Max----|
       ROUTINGS   |NORMAL     |         52|        260|        263|        500|

32.3.2. RIP statistics

To display the statistics of the RIP resource the following commands are used:

d s rip

Shows statistic information, such as the number of RIP version 1 and version 2 messages sent/received, the overall number of messages received with a bad RIP version/command, the overall number of messages received with a bad routing and the overall number of messages lost during transmission.

d se rip

Shows statistic information in an extended format: the information listed for d s rip command are shown along with the number of update request received/sent, the number of responses (sent/received) to the update request, the number of NORMAL/FLASH update messages sent/received, the number of datagrams with a REQUEST/RESPONSE command and the number of datagrams sent/received with a command different from REQUEST or RESPONSE sent/received.

[18:06:40] ABILIS_CPX:d s rip

RES:Rip -----------------------------------------------------------------------
       Routing_Information_Protocol                                            
       --- Cleared 145 days 07:12:54 ago, on 03/05/2017 at 08:14:01 -----------
       CHANGES:0             QUERIES:0         
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       FRM-V1     |        146|          0|FRM-V2     |     430386|     441144|
       BAD-VER    |          0|           |BAD-CMD    |          0|           |
       BAD-ROUT   |          0|           |LOST       |           |          0|
[18:06:40] ABILIS_CPX:d se rip

RES:Rip -----------------------------------------------------------------------
       Routing_Information_Protocol                                            
       --- Cleared 145 days 07:13:01 ago, on 03/05/2017 at 08:14:02 -----------
       CHANGES:0             QUERIES:0         
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       FRM-V1     |        146|          0|FRM-V2     |     430386|     441145|
       BAD-VER    |          0|           |BAD-ROUT   |          0|           |
       REQ-UPD    |         39|         27|RESP-UPD   |           |         52|
       NORM-UPD   |           |     439027|FLASH-UPD  |           |       2039|
       REQ-CMD    |        322|         27|RESP-CMD   |     430210|     441118|
       OTHER-CMD  |          0|          0|BAD-CMD    |          0|           |
       LOST       |           |          0|
       ------------------------------------------------------------------------

With reference to the shown interval of time («Cleared 145 days 07:13:01 ago») these counters show the number of:

FRM-V1Incoming/outgoing frames Version 1.
FRM-V2Incoming/outgoing frames Version 2.
BAD-VERBad version received.
BAD-ROUTBad routing received.
REQ-UPDIncoming/outgoing Update frames.
RESP-UPDOutgoing Response Update frames.
NORM-UPDOutgoing Normal Update frames.
FLASH-UPDOutgoing Flash Update frames.
REQ-CMDRequest command.
RESP-CMDResponse command.
OTHER-CMDOther commands.
BAD-CMDBad command.
LOSTFrame lost during sending phase.