The Routing Information Protocol (RIP) port

Revised for CPX 4.7.0.
Configuration of the RIP port
Statistics of the RIP port

RIP External Routes filter table


The RIP port is used within the Abilis CPX to implement the homonym routing protocols RIP1 and RIP2 for TCP/IP networks.

The Routing Information Protocol (RIP) gets information about IP networks routing and particularly it uses the Connection-Less transport service provided by the UDP protocol.

RIP1 and RIP2 protocols are based on periodic information extraction from IP Routings table and sending those informations to the neighbour systems.

Sent information consists of:

The "distance" or metric is estimated by RIP as the number of hops; a path to a destination on a network is a series of hops, through routers. If, for example, a destination network has metric equal to 3, it means it is reachable transiting through 3 networks.

The longest distance allowed by the protocol is 15 hops: a network, far more than 15 hops, is considered unreachable.

Configuration of the RIP port top

The RIP port is labelled within the Abilis CPX with the acronym "RIP" and it is provided with the parameters described in this section.

Here is an example on how to show the RIP parameters. Shown values are examples.

[13:25:49] ABILIS_CPX: D P PO:RIP

PO:903 - Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------
RIP    ------------------------------------------------------------------------
       lowpo:902   ACT:YES  locport:520  fifo:15  max-routes:500    SH:PR   
       AUT:NO      PWD:                  UT:30    LT:180   GT:120   ASBR:YES    
       - ASBR section ---------------------------------------------------------
       LOCAL:YES           STATIC:YES           OSPF:NO   
       LOCAL-METRIC:*      STATIC-METRIC:*      OSPF-METRIC:*   
       DEF-METRIC:1         

The parameters reported in the "ASBR section" are displayed only if the ASBR: parameter is set to "YES".

To activate changes made on the parameters displayed by low case characters, it is needed to restart the system; on the contrary for activating changes made on upper case parameters it is enough to execute the initialization command INIT PO:.

The "Not Saved (SAVE CONF)" message is displayed every time the port configuration is modified but not saved with the SAVE CONF command.

The "Not Refreshed (INIT)" message is displayed every time the port configuration is modified but not refreshed with the INIT PO: command.

Detail of the RIP port parameters


LOWPO: Identifier of the Abilis CPX lower level port
NONE 1 - 999, NONE

It sets the Abilis CPX lower level port. It can only be an UDP port.

Value "NONE" isolates the RIP port.


ACT: Routing functionalities activation
NO NO, YES

It activates the routing functionalities above mentioned. If the parameter is set to "NO", even if the RIP port is configured and active, it won't carry out any functionality within the system.


locport: Identifier of the IP local port used
520 520

It sets the local IP port used by the RIP port.

The IP number assigned by default to the RIP service is 520.

The parameter has got only an informative value, it cannot be modified.


fifo: Size of the receiving FIFO
15 1 - 50

It sets the number of buffers available in the FIFO for receiving from the RIP port. Once the FIFO is full, the RIP port won't be able to receive datagram any more. The datagrams sent to it will be discarded by the UDP lower level port.


max-routes: Maximum number of routing that the RIP table can store.
500 500 - 10000

If the table will be full, no more routings can be added and an informative message will be shown in the System Log.


SH: Selection of routing update mode
PR NO, YES, PR

This parameter set the routing update mode used by the RIP port.

Value Meaning
NO Update information sent by the RIP ports on the net will include all the IP routings stored in the IP routing table
YES Update information sent by the RIP ports on the net will only include those routings not obtained from the interface where the information are sent to. This updating procedure is referred as Split Horizon.
PR Routings should not be included in the update information, however they are sent as well but their metric is set to 16 hops. This updating procedure is referred as Split Horizon and Poison Reverse


AUT: Selection of the authentication functionality
NO NO, STD, MD5

This parameter set the authentication functionality of information received and forwarded by the RIP port.

Value Meaning
NO NO authentication is applied on the information exchanged by the Abilis CPX with other routers
STD Authentication algorithm includes sending update messages of the password as it is set in the parameter PWD:
MD5 The algorithm MD5 is used for authenticating the update messages (requested by the RFC1321) jointly with the password set in the parameter PWD:


PWD: Authentication password
none from 0 up to 16 ASCII characters [33..126]

The parameter set the password used for the authentication function.

It is possible to use from 0 up to 16 ASCII characters in the range [33..126], spaces are not allowed. No differences between low and high case characters are made

Once it is configured, the password is saved on disk encrypted.

To delete the access password do not set the value of the parameter: "S P PO:xxx PWD:", where "xxx" stands for the RIP port identifier.


UT: Time interval between two consecutive generations of update messages
30 10 - 600 (in seconds)

It sets the time interval that the RIP port has to wait, before generating the next update message of routing information to be forwarded to other routers.


LT: Route Life Time
180 30 - 1800 (in seconds)

This parameter set the time interval during which an IP routing is considered valid, even if no update has been received. When this interval elapses the routing becomes invalid and the RIP will delete it only after GT: seconds in order to allow the network other routers to be updated.


GT: Garbage Collection Period
120 10 - 1800 (in seconds)

It sets how long the IP invalid routings have to be stored in the IP routing table. When this time interval elapses the IP routing is deleted.


ASBR: Defines this router as Autonomous System Boundary Router (ASBR).
YES YES, NO

ASBR router locates in point where RIP AS connects with other AS that does not use RIP routing protocol. ASBR router can redistribute routes between different AS.
Usually this parameter will set to YES, because only in this case RIP can import external routing. In fact, in case that ASBR is set to NO, RIP table will be filled only by routings obtained by other RIP routers in the network.


LOCAL: ASBR LOCAL activation
YES YES, NO

It enables/disables the use of LOCAL (connected) routes present in the routes table of IPRTR for redistribution into RIP.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".


STATIC: ASBR STATIC activation
YES YES, NO

It enables/disables the use of STATIC routes present in the routes table of IPRTR for redistribution into RIP.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".


OSPF: ASBR OSPF activation
NO YES, NO

It enables/disables the use of OSPF routes present in the routes table of IPRTR for redistribution into RIP.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".


LOCAL-METRIC: ASBR LOCAL metric
* 0 - 16, *

It sets the default metric value that will be used for redistribution routes, of LOCAL type, imported from the IPRTR route table into RIP.

The value "*" stands for "use default", i.e. indicates to use the DEF-METRIC: parameter value.

For specific routes this value may be overriden by a "not-*" value in the External routes.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".


STATIC-METRIC: ASBR STATIC metric
* 0 - 16, *

It sets the default metric value that will be used for redistribution routes, of STATIC type, imported from the IPRTR route table into RIP.

The value "*" stands for "use default", i.e. indicates to use the DEF-METRIC: parameter value.

For specific routes this value may be overriden by a "not-*" value in the External routes.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".


OSPF-METRIC: ASBR OSPF metric
* 0 - 16, *

It sets the default metric value that will be used for redistribution routes, of OSPF type, imported from the IPRTR route table into RIP.

The value "*" stands for "use default", i.e. indicates to use the DEF-METRIC: parameter value.

For specific routes this value may be overriden by a "not-*" value in the External routes.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".


DEF-METRIC: ASBR DEFAULT metric
1 0 - 16

It sets the default metric value that will be used for redistribution routes, of any type, imported from the IPRTR route table into RIP.
Used when a "protocol specific" value does not override it, i.e.:

For specific routes this value may also be overriden by a "not-*" value in the External routes.

This parameter is diaplyed and can be set only when ASBR: parameter is set to "YES".

Statistics of the RIP port top

Here it is a sample of the D S command execution to check the state and statistics of the RIP port.

[14:43:54] ABILIS_CPX: D S PO:RIP

PO:903 ------------------------------------------------------------------------
RIP    STATE:INACTIVE
       ------------------------------------------------------------------------
       RIP ROUTINGS TABLE Diagnostics
       -----------|---State---|-Current%--|--Current--|---Peak----|----Max----|
       ROUTINGS   |NORMAL     |          0|          0|          0|        500|
       ------------------------------------------------------------------------
       CHANGES:0             QUERIES:0   
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       FRM-V1     |          0|          0|FRM-V2     |          0|          1|
       BAD-VER    |          0|           |BAD-CMD    |          0|           |
       BAD-ROUT   |          0|           |LOST       |           |          0|
       ------------------------------------------------------------------------

The RIP ports also have extended statistics that can be displayed by the execution of the command D SE:

PO:903 ------------------------------------------------------------------------
RIP    --- Cleared 000:20:06:10 ago, on 17/03/2004 at 20:11:35 ----------------
       CHANGES:0             QUERIES:0   
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       FRM-V1     |          0|          0|FRM-V2     |          0|          1|
       BAD-VER    |          0|           |BAD-ROUT   |          0|           |
       REQ-UPD    |          0|          1|RESP-UPD   |           |          0|
       NORM-UPD   |           |          0|FLASH-UPD  |           |          0|
       REQ-CMD    |          0|          1|RESP-CMD   |          0|          0|
       OTHER-CMD  |          0|          0|BAD-CMD    |          0|           |
       LOST       |           |          0|
       ------------------------------------------------------------------------

The information "Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS", referred by the extended statistics, shows the elapsed time from the last reset of the statistics (by the format "days:hours:minutes:seconds") and date/time of its execution (by the format "day/month/year" and "hours:minutes:seconds").

Details of the state fields and statistics of the RIP port


STATE: Current state of the RIP port
INACTIVE, READY, DOWN, ERR

It shows the current state of the RIP port driver.

Driver States Description Values shown in:
System Log Events Log Display LCD
RIP INACTIVE The configuration parameter ACT: is set to "NO". As consequence the driver is active, but not working. By setting its value to "YES" and executing the command INIT PO:the driver will be effectively activated.     IN
READY The configuration parameter ACT: is set to "YES" and driver is successfully connected to the UDP port. It is ready to work.     RD
DOWN The configuration parameter ACT: is set to "YES" but the driver is not connected to the UDP port or the parameter LOWPO: is set to NONE.     DN
ERR Software error. Contact Abilis CPX assistance.     NA


ROUTINGS - State Current state of the RIP routing table
NORMAL, WARNING, DANGER, OVERFLOW

Indicates the current state of the RIP routing table. Depending on the number of routings present into table, possible routing table states are:

States Description
NORMALUsed routings are less than 60%.
WARNING Used routings went over 60%.
A DANGER_IN message will be written in the System Log. To go back to normal, routings must decrease to 55%.
DANGER Used routings went over 80%.
To go back to warning, routings must decrease to 75%. A DANGER_OUT message will be written in the System Log.
OVERFLOW routings used reached 100%.
An OVERFLOW message will be written in the System Log.


ROUTINGS - Current% Current routing percentage
0 - 100

Indicates the current PERCENTAGE of routings present into routing table.


ROUTINGS - Current Current routing number
0 - MAX-ROUTES

Indicates the current NUMBER of routings present into routing table.


ROUTINGS - Peak Maximum routing peak
0 - MAX-ROUTES

Indicates the maximum number of routings reached from start-up into table.


ROUTINGS - Max Maximum number of routings present into table
MAX-ROUTES

This information indicate the MAX-ROUTES parameter present into RIP port.


CHANGES: Number of changes of the IP routing table
0 - 4.294.967.295

The counter CHANGES shows the number of changes made by the RIP on the IP routing table.


QUERIES: Number of responses sent to the queries received from other routers
0 - 4.294.967.295

It shows the number of responses sent by the RIP port to the queries received from other routers.


FRM-V1 Number of RIP version 1 messages sent/received
0 - 4.294.967.295

The counter FRM-V1 (INPUT) shows the number of RIP version 1 messages received. The counter FRM-V1 (OUTPUT) shows the number of RIP version 1 messages sent.


FRM-V2 Number of RIP version 2 messages sent/received
0 - 4.294.967.295

The counter FRM-V2 (INPUT) shows the number of RIP version 2 messages received. The counter FRM-V2 (OUTPUT) shows the number of RIP version 2 messages sent.


BAD-VER Overall number of messages received with a bad RIP version
0 - 4.294.967.295

The counter BAD-VER (INPUT) is incremented every time the RIP port receives a datagram whose RIP protocol version is bad.


BAD-CMD Overall number of messages received with a bad RIP command
0 - 4.294.967.295

The counter BAD-CMD (INPUT) is incremented every time the RIP port receives a message with a bad command.


BAD-ROUT Overall number of messages received with a bad routing
0 - 4.294.967.295

The counter BAD-ROUT (INPUT) shows the number of routing received by the RIP port whose IP network address or IP gateway address is not valid. They will be discarded.

The not valid addresses are LOOPBACK, BROADCAST, MULTICAST and all those address higher than the C class addresses.


LOST Overall number of messages lost during transmission
0 - 4.294.967.295

The counter LOST (OUTPUT) is incremented every time a sent datagram is lost.


REQ-UPD Number of update request received/sent
0 - 4.294.967.295

The counter REQ-UDP (INPUT) is incremented every time the RIP port receives an update request. The counter REQ-UDP (OUTPUT) is incremented every time the RIP port sends an update request.


RESP-UPD Number of responses (sent/received) to the update request
0 - 4.294.967.295

The counter RESP-UDP (INPUT) is incremented every time the RIP port receives a response to an update request. The counter RESP-UDP (OUTPUT) is incremented every time the RIP port sends a response to an update request.


NORM-UPD Number of "NORMAL" update messages sent/received
0 - 4.294.967.295

The counter NORM-UDP (INPUT) is incremented every time the RIP port receives a "NORMAL" update message. The counter NORM-UDP (OUTPUT) is incremented every time the RIP port sends a "NORMAL" update message.


FLASH-UPD Number of "FLASH" update messages sent/received
0 - 4.294.967.295

The counter NORM-UDP (INPUT) is incremented every time the RIP port receives a "FLASH" update message. The counter RESP-UDP (OUTPUT) is incremented every time the RIP port sends a "FLASH" update message.


REQ-CMD Number of datagrams with a REQUEST command sent/received
0 - 4.294.967.295

The counter REQ-CMD (INPUT) is incremented every time the RIP port receives a REQUEST command. The counter REQ-CMD (OUTPUT) is incremented every time the RIP port sends a REQUEST command.


RESP-CMD Number of datagrams with a RESPONSE command sent/received
0 - 4.294.967.295

The counter RESP-CMD (INPUT) is incremented every time the RIP port receives a RESPONSE command. The counter RESP-CMD (OUTPUT) is incremented every time the RIP port sends a RESPONSE command.


OTHER-CMD Number of datagrams sent/received with a command different from REQUEST or RESPONSE
0 - 4.294.967.295

The counter OTHER-CMD (INPUT and OUTPUT) shows the number of command frames (received/sent) different from REQUEST and RESPONSE.

printPrint this page