RIP

This chapter provides information about configuring RIP on the 7705 SAR.

Topics in this chapter include:

RIP overview

Routing Information Protocol (RIP) is an interior gateway protocol (IGP) that uses a Bellman-Ford distance-vector algorithm to determine the best route to a destination, using hop count as the metric. In order for the protocol to provide complete information on routing, every router in the domain must participate in the protocol.

The 7705 SAR supports RIPv1 and RIPv2 on all IP network interfaces and on IES and VPRN access interfaces.

RIPv1, specified in RFC 1058, was written and implemented prior to the introduction of CIDR. The RIPv1 protocol does not send subnet mask information during routing updates; instead, it assumes the subnet mask information for non-local routes based on the class the route belongs to:

  • Class A – 8-bit mask

  • Class B – 16-bit mask

  • Class C – 24-bit mask

RIPv2, as defined in RFC 2453, was written after CIDR was developed and transmits subnet mask information with every route. Because of the support for CIDR routes and other enhancements in RIPv2 such as triggered updates, multicast advertisements, and authentication, most production networks use RIPv2. However, some older hosts and routers only support RIPv1, especially when RIP is used simply to advertise default routing information.

RIP, which is carried over the UDP protocol, updates its neighbors, and the neighbors update their neighbors, and so on. Each host that uses RIP has a routing process that sends and receives datagrams on UDP port number 520. Although the RIP mechanism is fairly simple, it requires a lot of convergence time in large networks and is prone to routing loops unless additional measures are taken.

Each RIP router advertises all RIP routes periodically via RIP updates. By default, each update can contain a maximum of 25 route advertisements. This limit is imposed by RIP specifications. RIP can be configured to send as many as 255 routes per update. RIPv1 and RIPv2 updates are formatted slightly differently. RIPv1 updates are sent to a broadcast address (255.255.255.255); RIPv2 updates can be sent either to a broadcast or multicast address (224.0.0.9).

A network address of 0.0.0.0 is considered a default route. A default route is used when it is not convenient to list every possible network in the RIP updates and when one or more closely connected gateways in the system are prepared to handle traffic to the networks that are not listed explicitly. These gateways create RIP entries for the address 0.0.0.0 as if it were a network to which they are connected.

RIP versions

You can specify the RIP version that will be sent to RIP neighbors and the version of RIP updates that will be accepted and processed. The 7705 SAR allows the following combinations:

  • send only RIPv1 or RIPv2 messages to either the broadcast or multicast address, or send no messages

    If the sending router’s RIP interface is configured to send to the broadcast address, the receiving router interface must be configured to allow directed broadcasts in the config>router>interface context (for network interfaces), in the config>service>ies>interface context (for IES interfaces), or in the config>service>vprn>interface context (for VPRN interfaces). The 7705 SAR sends RIPv2 formatted messages to the broadcast address by default.

  • receive only RIPv1 updates, receive only RIPv2 updates, receive both RIPv1 and RIPv2 updates, or receive no updates

    The 7705 SAR receives both RIPv1 and RIPv2 updates by default.

RIPv2 authentication

RIPv2 messages carry more information than RIPv1 messages, which permits the use of a simple authentication mechanism to secure table updates. The 7705 SAR RIPv2 implementation enables the use of a plaintext (simple) password or message digest (MD5) authentication.

Metrics

By default, RIP advertises all RIP routes to each peer every 30 s. RIP uses a hop count metric to determine the distance between the packet’s source and destination. The metric/cost value for a valid route is 1 through 15.

Each router along the path increments the hop count value by 1. When a router receives a routing update with new or different destination information, the metric increments by 1.

The maximum number of hops in a path is 15. The router treats any number over 15 as infinitely large. If a router receives a routing update with a metric of 15 that contains a new or modified entry, the route metric value increments to 16 and the destination is considered unreachable.

The 7705 SAR uses split horizon and split horizon with poison reverse to avoid looping routes propagating through the network. When split horizon is enabled, the local router does not readvertise routes learned from a neighbor back to the same neighbor. When split horizon with poison is enabled and the router receives an update over an interface, the router sets the route metric to 16 (infinity) and advertises the route back to the network where it is now considered unreachable.

Timers

RIP uses three timers to determine how often RIP updates are sent and how long routes are maintained:

  • update – times the interval between periodic routing updates

  • timeout – initialized when a route is established and any time an update message is received for the route. When this timer expires, the route is no longer valid. It is retained in the table for a short time so that neighbors can be notified that the route has been dropped.

  • flush – when the flush timer expires, the route is removed from the tables

Import and export policies

Routing policies control the content of the routing tables, the routes that are advertised, and the best route to take to reach a destination. Import route policies determine which routes are accepted from RIP neighbors. Export route policies determine which routes are exported from the route table to RIP.

There are no default import or export routing policies. Policies must be explicitly created and applied with RIP import or export commands.

RIP packet format

There can be 1 to 25 route entries. The RIP packet header format is displayed in RIP packet format. RIPv1 packet format and RIPv2 packet format display the RIPv1 and RIPv2 packet formats.

Figure 1. RIP packet format
Figure 2. RIPv1 packet format
Figure 3. RIPv2 packet format

RIP packets contain the following fields:

  • Command – indicates whether the packet is a request or a response message. A request message asks the responding system to send all or part of its routing table. The response message may be sent in response to a request, or it may be an unsolicited routing update generated by the sender.

  • Version – specifies the RIP version used and can be used to signal different, and potentially incompatible, versions

  • Must be zero – provides backward compatibility with pre-standard varieties of RIP. RIP messages with non-zero values in this field are rejected unless the check-zero command is disabled.

  • Address family identifier (AFI) – the type of address. RIP can carry routing information for several different protocols. Each entry in this field has an AFI to indicate the type of address being specified. The IP AFI is 2.

  • IP Address – the IP address for the packet

  • Metric – specifies the number of hops to the destination

  • Next hop – the IP address of the next router along the path to the destination. This field appears only in RIPv2 packets.

  • Subnet mask – the subnet mask for the entry. If this field is 0, no subnet mask has been specified for the entry. This field appears only in RIPv2 packets.

RIP hierarchical levels

The minimum RIP configuration must define one group and one neighbor. The parameters configured at the RIP global level are inherited by the group and neighbor levels. Parameters can be modified and overridden on a level-specific basis. The RIP command hierarchy consists of three levels:

  • global

  • group

  • neighbor

Hierarchical RIP commands can be modified on different levels. The most specific value is used. A RIP group-specific command takes precedence over a global RIP command. A neighbor-specific command takes precedence over a global RIP or group-specific RIP command.

RIP configuration process overview

The following figure displays the process to configure RIP parameters.

Figure 4. RIP configuration and implementation flow

Configuration notes

The following guidelines and caveats apply to RIP configuration:

  • Before RIP neighbor parameters can be configured, router interfaces must be configured.

  • RIP must be explicitly created for each router interface. There are no default RIP instances on a 7705 SAR router.

RIP configuration overview

Preconfiguration requirements

Before RIP can be implemented, the following entities must be configured:

  • policy statements must be defined in the config>router>policy-options context

Basic RIP configuration

RIP is configured in the config>router>rip context for network interfaces and IES access interfaces. RIP is configured in the config>service>vprn>rip context for VPRN interfaces when RIP is used as a PE-to-CE routing protocol for VPRN service. For information about configuring RIP under VPRN, see the 7705 SAR Services Guide, ‟Configuring RIP for VPRN”.

RIP configuration commands have three primary configuration levels: rip for global configurations, group group-name for RIP groups, and neighbor ip-int-name for RIP neighbor configurations. Within the different levels, the configuration commands are identical.

Commands and parameters configured at the global level are inherited by the group and neighbor level; however, the command that is most specific to the neighboring router takes precedence. Parameters configured at the neighbor level have precedence over group and global configurations and parameters configured at the group level have precedence over global configurations.

The minimum RIP parameters that must be configured in the config>router>rip context are:

  • group

  • neighbor

For a router to accept RIP updates, at least one group and one neighbor must be defined. A 7705 SAR router ignores RIP updates received from routers on interfaces not configured for RIP. Configuring other RIP commands and parameters is optional.

By default, the local router imports all routes from its neighbor and does not advertise routes. The router receives both RIPv1 and RIPv2 update messages with 25 to 255 route entries per message.

The following is an example of a basic RIP configuration.

ALU-A>config>router>rip# info
----------------------------------------------
        group "RIP-ALU-A"
               neighbor "to-ALU-4"
               exit
        exit
----------------------------------------------
ALU-A>config>router>rip#

Common configuration tasks

This section provides a brief overview of the tasks that must be performed to configure RIP and provides the CLI commands.

RIP is configured hierarchically; the global level applies to all peers, the group level applies to all peers in the group, and the neighbor level only applies to a specified peer. By default, group members inherit the group’s configuration parameters, although a parameter can be modified on a per-member basis without affecting the group-level parameters.

All RIP instances must be explicitly created on each 7705 SAR. Once created, RIP is administratively enabled.

To configure RIP, perform the following tasks in order:

  • configure interfaces

  • configure policy statements (optional)

  • enable RIP

  • configure group parameters

  • configure neighbor parameters

Configuring interfaces

The following command sequences create a logical IP interface. The logical interface can associate attributes such as an IP address, port, link aggregation group (LAG), or the system. For more information about configuring interfaces, see the 7705 SAR Router Configuration Guide.

To configure a network interface:

CLI syntax:
config>router
    interface ip-int-name
        address {ip-addr/mask-length | ip-addr/netmask}
        allow-directed-broadcasts
        port port-name
Example:
config>router# interface ‟to-ALU-4”
config>router>if# address 10.10.12.1/8
config>router>if# port 1/1/1
config>router>if# exit

The following example displays the configuration output:

ALU-3>config>router# info
----------------------------------------------
#echo ‟IP Configuration”
#------------------------------------------
    interface "system"
        address 192.0.2.0/24
    exit
    interface "to-ALU-4"
        address 10.10.12.1/8
        port 1/1/1
    exit
#------------------------------------------
ALU-3>config>router#

The following command sequences create an IES (access) interface that will be added to RIP in the config>router>rip context. For more information about IES interfaces, see the 7705 SAR Services Guide, ‟Internet Enhanced Service”.

To configure an IES interface:

CLI syntax:
config>service
    ies service-id [customer customer-id] [create] [vpn vpn-id]
        interface ip-int-name [create]
            address {ip-addr/mask | ip-addr/netmask}
            allow-directed-broadcasts
            sap sap-id [create]
Example:
config>service# ies 4 customer 1 create
config>service>ies# interface ‟rip_interface” create
config>service>ies>if$ address 172.16.1.1/12
config>service>ies>if$ allow-directed-broadcasts
config>service>ies>if$ sap 1/1/4 create

The following example displays the configuration output:

*A:Sar18 Dut-B>config>service>ies# info
----------------------------------------------
            interface "rip_interface" create
                address 172.16.1.1/12
                allow-directed-broadcasts
                sap 1/1/4 create
                exit
            exit
            no shutdown
----------------------------------------------
*A:Sar18 Dut-B>config>service>ies#

Configuring a route policy

The import route policy command allows you to filter routes being imported by the local router from its neighbors. If no match is found, the local router does not import any routes.

The export route policy command allows you to determine which routes are exported from the route table to RIP. By default, RIP does not export routes it has learned to its neighbors. If no export policy is specified, non-RIP routes will not be exported from the routing table manager to RIP.

If multiple policy names are specified, the policies are evaluated in the order they are specified. The first policy that matches is applied. If multiple export commands are issued, the last command entered will override the previous command. A maximum of five policy names can be specified.

To enter the mode to create or edit route policies, you must enter the begin keyword at the config>router>policy-options prompt. Other editing commands include:

  • the commit command, saves and enables changes made to route policies during a session

  • the abort command, discards changes that have been made to route policies during a session

Use the following CLI syntax to configure a policy to use for RIP global, group, and neighbor import and export commands. This section provides brief instructions to configure route policies. For more details and the complete list of policy options commands, see the 7705 SAR Router Configuration Guide, ‟Configuring Route Policies With CLI”.

CLI syntax:
config>router>policy-options
    begin
    commit
    abort
    policy-statement name
        description text
        default-action {accept | next-entry | next-policy | reject}
        entry entry-id
            description text
            action {accept | next-entry | next-policy | reject}
            from
                protocol {bgp | direct | ospf | ospf3 | rip | isis | static | aggregate | bgp-vpn | igmp | mld | pim | ldp}
            to
                protocol {bgp | direct | ospf | ospf3 | rip | isis | static | aggregate | bgp-vpn | igmp | mld | pim | ldp}

The following example displays commands to configure a policy statement. Use the commit command to save the changes.

Example:
config>router>policy-options# begin
policy-options# policy-statement‟RIP-policy”
policy-options>policy-statement$ description "this is a
test RIP policy”
policy-options>policy-statement>default# entry 1
policy-options>policy-statement>entry$ action accept
policy-options>policy-statement>entry# exit
policy-options>policy-statement# default-action reject
policy-options>policy-statement# exit
policy-options# commit

ALU-A>config>router>policy-options# info
----------------------------------------------
    policy-statement "RIP-policy"
    description "this is a test RIP policy"
    entry 1
    action accept
    exit
    exit
    default-action reject
    exit
----------------------------------------------
ALU-A>config>router>policy-options>policy-statement#

Configuring RIP parameters

Use the CLI syntax below to configure global-level, group-level, and neighbor-level parameters:

CLI syntax:
config>router
    rip
        authentication-key {authentication-key | hash-key} [hash | hash2]
        authentication-type {none | password | message-digest | message-digest-20}
        check-zero {enable | disable}
        description description-string
        export policy-name [policy-name ...up to 5 max]
        group group-name
            authentication-key {authentication-key | hash-key} [hash | hash2]
            authentication-type {none | password | message-digest | message-digest-20}
            check-zero {enable | disable}
            description description-string
            export policy-name [policy-name ...up to 5 max]]
            import policy-name [policy-name ...up to 5 max]]
            message-size max-num-of-routes
            metric-in metric
            metric-out metric
            neighbor ip-int-name
                authentication-key {authentication-key | hash-key} [hash|hash2]
                authentication-type {none | password | message-digest | message-digest-20}
                check-zero {enable | disable}
                description description-string
                export policy-name [policy-name ...up to 5 max]]
                import policy-name [policy-name ...up to 5 max]]
                message-size max-num-of-routes
                metric-in metric
                metric-out metric
                preference preference
                receive receive-type
                send send-type
                no shutdown
                split-horizon {enable | disable}
                timers update timeout flush
            preference preference
            receive receive-type
            send send-type
            no shutdown
            split-horizon {enable|disable}
            timers update timeout flush
        import policy-name [policy-name ...up to 5 max]
        message-size max-num-of-routes
        metric-in metric
        metric-out metric
        preference preference
        receive receive-type
        send send-type
        no shutdown
        split-horizon {enable | disable}
        timers update timeout flush

Configuring global-level parameters

Once the RIP protocol instance is created, it is administratively enabled automatically; the no shutdown command is not required. To enable RIP on a router, at least one group and one neighbor must be configured. There are no default groups or neighbors. Each group and neighbor must be explicitly configured.

Note: Careful planning is essential to implement commands that can affect the behavior of global, group, and neighbor levels. Because the RIP commands are hierarchical, analyze the values that can disable features on a particular level.

The following example displays a global RIP configuration:

Example:
config>router# rip
config>router>rip# authentication-type password
config>router>rip# authentication-key test123
config>router>rip# receive both
config>router>rip# split-horizon enable
config>router>rip# timers 300 600 600
config>router>rip>group# exit

ALU-A>config>router>rip# info
----------------------------------------------
            authentication-type simple
            authentication-key "ac1865lvz1d" hash
            timers 300 600 600
----------------------------------------------

Configuring group-level parameters

A group is a collection of related RIP peers (neighbors). The group name should be a descriptive name for the group. Follow your group, name, and ID naming conventions for consistency and to help when troubleshooting faults.

All parameters configured for a peer group are applied to the group and are inherited by each peer (neighbor), but a group parameter can be overridden on a specific neighbor-level basis.

The following example displays a group configuration:

Example:
config>router# rip
config>router>rip# group headquarters
config>router>rip>group$ description "Base HQ"
config>router>rip>group# no shutdown

ALA-A>config>router>rip# info
----------------------------------------------
            authentication-type simple
            authentication-key "ac1865lvz1d" hash
            timers 300 600 600
            group "headquarters"
                description "Base HQ"
            exit
----------------------------------------------
ALA-A>config>router>rip#

Configuring neighbor-level parameters

After you create a group name and assign options, add neighbor interfaces within the same group. All parameters configured for the peer group level are applied to each neighbor, but a group parameter can be overridden on a specific neighbor basis.

The following example displays a neighbor configuration:

Example:
config>router# rip
config>router>rip# group headquarters
config>router>rip>group# neighbor ferguson-274
config>router>rip>group>neighbor$ preference 255
config>router>rip>group>neighbor# send both
config>router>rip>group>neighbor# split-horizon enable
config>router>rip>group>neighbor# message-size 255

ALU-A>config>router>rip>group>neighbor# info
----------------------------------------------
                    message-size 255
                    preference 255
                    split-horizon enable
                    no timers
----------------------------------------------
ALU-A>config>router>rip>group>neighbor#

RIP configuration management tasks

Examples are provided for the following RIP configuration management tasks:

Modifying RIP parameters

When RIP parameters are modified, added, or removed, the changes are applied immediately. For the complete list of CLI commands, see Configuring RIP parameters.

CLI syntax:
config>router# rip
    group group-name
    . . .
        neighbor ip-int-name
    . . .
Example:
config>router>rip# group "headquarters"
config>router>rip>group# neighbor "ferguson-274"
config>router>rip>group>neighbor# import RIPpolicy
config>router>rip>group>neighbor# message-size 150

The following example displays the updated parameters:

ALU-A>config>router>rip# info
----------------------------------------------
authentication-type simple
authentication-key "ac1865lvz1d" hash
timers 300 600 600
group "headquarters"
description "Mt. View"
neighbor "ferguson-274"
import "RIPpolicy"
message-size 150
preference 255
split-horizon enable
no timers
exit
exit
----------------------------------------------
ALU-A>config>router>rip#

Deleting a RIP group

A RIP group must be shut down first in order to delete it.

Use the following CLI syntax to shut down and then delete a RIP group.

CLI syntax:
config>router# rip
    group group-name
        shutdown
        exit
    no group group-name
Example:
config>router> rip
config>router>rip# group ‟RIP-ALU-3”
config>router>rip>group# shutdown
config>router>rip>group# exit
config>router>rip# no group ‟RIP-ALU-3”

If you try to delete the group without shutting it down first, the following message appears:

INFO: RIP #1204 group should be administratively down -
virtual router index 1,group 
RIP-ALA-4

Deleting a RIP neighbor

A RIP neighbor must be shut down first in order to delete it.

Use the following CLI syntax to shut down and then delete a RIP neighbor.

CLI syntax:
config>router# rip
    group group-name
        neighbor ip-int-name
            shutdown
            exit
        no neighbor ip-int-name
Example:
config>router# rip
config>router>rip# group ‟RIP-ALU-4”
config>router>rip>group# neighbor ‟to-ALU-3”
config>router>rip>group>neighbor# shutdown
config>router>rip>group>neighbor# exit
config>router>rip>group# no neighbor ‟to-ALU-3”

If you try to delete the neighbor before it is shut down, the following message appears:

INFO: RIP #1101 neighbor should be administratively down - virtual router index

RIP command reference

Command hierarchies

Configuration commands

Global RIP commands 
config
    - router [router-name]
        - [no] rip
            - authentication-key {authentication-key | hash-key} [hash | hash2]
            - no authentication-key 
            - authentication-type {none | password | message-digest | message-digest-20}
            - no authentication-type
            - check-zero {enable | disable}
            - no check-zero
            - description string
            - no description
            - export policy-name [policy-name…(up to 5 max)]
            - no export
            - export-limit number [log percentage]
            - no export-limit
            - [no] group group-name
            - import policy-name [policy-name…(up to 5 max)]
            - no import
            - message-size max-num-of-routes
            - no message-size
            - metric-in metric
            - no metric-in
            - metric-out metric
            - no metric-out
            - preference preference
            - no preference
            - receive receive-type
            - no receive
            - send send-type
            - no send
            - [no] shutdown
            - split-horizon {enable | disable}
            - no split-horizon
            - timers update timeout flush
            - no timers
Group RIP commands 
config
    - router [router-name]
        - [no] rip
            - [no] group group-name
                    - authentication-key {authentication-key | hash-key} [hash | hash2]
                    - no authentication-key 
                    - authentication-type {none | password | message-digest | 
message-digest-20}
                    - no authentication-type
                    - check-zero {enable | disable}
                    - no check-zero
                    - description string
                    - no description
                    - export policy-name [policy-name…(up to 5 max)]
                    - no export
                    - import policy-name [policy-name…(up to 5 max)]
                    - no import
                    - message-size max-num-of-routes
                    - no message-size
                    - metric-in metric
                    - no metric-in
                    - metric-out metric
                    - no metric-out
                    - [no] neighbor ip-int-name 
                    - preference preference
                    - no preference
                    - receive receive-type
                    - no receive
                    - send send-type
                    - no send
                    - [no] shutdown
                    - split-horizon {enable | disable}
                    - no split-horizon
                    - timers update timeout flush
                    - no timers
Neighbor RIP commands 
config 
    - router [router-name]
        - [no] rip
            - [no] group group-name
                - [no] neighbor ip-int-name
                    - authentication-key {authentication-key | hash-key} [hash | hash2]
                    - no authentication-key 
                    - authentication-type {none | password | message-digest | 
message-digest-20}
                    - no authentication-type
                    - check-zero {enable | disable}
                    - no check-zero
                    - description string
                    - no description
                    - export policy-name [policy-name…(up to 5 max)]
                    - no export
                    - import policy-name [policy-name…(up to 5 max)]
                    - no import
                    - message-size max-num-of-routes
                    - no message-size
                    - metric-in metric
                    - no metric-in
                    - metric-out metric
                    - no metric-out
                    - preference preference
                    - no preference
                    - receive receive-type
                    - no receive
                    - send send-type
                    - no send
                    - [no] shutdown
                    - split-horizon {enable | disable}
                    - no split-horizon
                    - timers update timeout flush
                    - no timers

Show commands

show
    - router [router-instance]
        - rip
            - database [ip-prefix [/mask] [longer] [peer ip-address] [detail]
            - group [name] [detail]
            - neighbor [ip-int-name | ip-address] [detail] [advertised-routes]
            - peer [interface-name]
            - statistics [ip-int-name | ip-address]

Clear commands

clear
    - router
        - rip
            - database 
            - statistics [neighbor ip-int-name | ip-address]

Monitor commands

monitor
    - router
        - rip
            - neighbor neighbor [neighbor...[(up to 5 max)] [interval seconds] [repeat repeat] [absolute | rate]

Debug commands

debug
    - router
        - rip
            - [no] auth [neighbor ip-int-name | ip-address]
            - [no] error [neighbor ip-int-name | ip-address]
            - [no] events [neighbor ip-int-name | ip-address]
            - [no] holddown [neighbor ip-int-name | ip-address]
            - [no] packets [neighbor ip-int-name | ip-address]
            - [no] request [neighbor ip-int-name | ip-address]
            - [no] trigger [neighbor ip-int-name | ip-address]
            - [no] updates [neighbor ip-int-name | ip-address]
Note: Unless specified otherwise, all hierarchical RIP commands can be modified on different levels. The most specific value is used. A RIP group-specific command takes precedence over a global RIP command. A neighbor-specific command takes precedence over a global RIP or group-specific RIP command.

Command descriptions

Configuration commands

Generic commands
description
Syntax

description description-string

no description

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command creates a text description stored in the configuration file for a configuration context.

The no form of the command removes the description string from the context.

Default

no description is associated with the configuration context

Parameters
description-string

the description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed within double quotes.

shutdown
Syntax

[no] shutdown

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

The no form of this command administratively enables an entity.

Unlike other commands and parameters where the default state is not indicated in the configuration file, the shutdown and no shutdown states are always indicated in system-generated configuration files.

Default administrative states for services and service entities are described below in Special Cases.

Special cases
RIP global

the RIP protocol is created in the no shutdown state

RIP group

RIP groups are created in the no shutdown state

RIP neighbor

RIP neighbors/peers are created in the no shutdown state

RIP commands
rip
Syntax

[no] rip

Context

config>router

Description

This command creates the RIP protocol instance and RIP configuration context. RIP is administratively enabled upon creation. To start or suspend execution of the RIP protocol without affecting the configuration, use the [no] shutdown command.

The no form of the command deletes the RIP protocol instance and removes all configuration parameters for the RIP instance.

Default

no rip

authentication-key
Syntax

authentication-key {authentication-key | hash-key} [hash | hash2]

no authentication-key

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures the RIPv2 authentication key.

Authentication is performed between neighboring routers before setting up the RIP session by verifying the password. Authentication is performed using the MD5 message-based digest.

The authentication key can be any combination of ASCII characters up to 255 characters long. The hash-key can be any combination of ASCII characters up to 342 characters long.

The no form of the command removes the authentication password from the configuration and disables authentication.

Default

no authentication-key

Parameters
authentication-key

the authentication key. The key can be any combination of ASCII characters up to 255 characters in length (unencrypted). If spaces are used in the string, the entire string must be enclosed in quotation marks (‟ ”).

hash-key

the hash key. The key can be any combination of ASCII characters up to 342 characters in length (encrypted). If spaces are used in the string, the entire string must be enclosed in quotation marks (‟ ‟). This is useful when a user must configure the parameter, but for security purposes, the actual unencrypted key value is not provided.

hash

specifies that the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted form in the configuration file with the hash parameter specified.

hash2

specifies that the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less-encrypted hash form is assumed.

authentication-type
Syntax

authentication-type {none | password | message-digest | message-digest-20}

no authentication-type

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command sets the type of authentication to be used between RIP neighbors. Authentication type can be specified regardless of the configured send and receive parameters, but will only apply to RIPv2 packets.

The type and password must match exactly for the RIP message to be considered authentic and processed.

The no form of the command removes the authentication type from the configuration and disables authentication.

Default

no authentication-type

Parameters
none

explicitly disables authentication at a given level (global, group, neighbor). If the command does not exist in the configuration, the parameter is inherited from a higher level.

password

enables simple password (plaintext) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.

message-digest

configures 16-byte message digest for MD5 authentication. If this option is configured, then at least one message-digest key must be configured.

message-digest-20

configures 20-byte message digest for MD5 authentication in accordance with RFC 2082, RIP-2 MD5 Authentication. If this option is configured, then at least one message-digest key must be configured.

check-zero
Syntax

check-zero {enable | disable}

no check-zero

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command enables checking for zero values in fields specified to be zero by the RIPv1 and RIPv2 specifications.

The check-zero enable command enables checking of the mandatory zero fields in the RIPv1 and RIPv2 specifications and rejecting of non-compliant RIP messages.

The check-zero disable command disables this check and allows the receipt of RIP messages even if the mandatory zero fields are non-zero.

The check-zero command can be enabled at all three RIP levels. The most specific value is used. If no check-zero value is set (no check-zero), the setting from the less-specific level is inherited by the lower level.

The no form of the command disables check-zero on the configuration.

Default

disabled at the RIP global level

Parameters
enable

configures the router to reject RIP messages that do not have zero in the mandatory fields

disable

configures the router to accept RIP messages that do not have zero in the mandatory fields

export
Syntax

export policy-name [policy-name…(up to 5 max)]

no export

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command specifies the export route policy used to determine which routes are advertised to peers. Route policies are configured in the config>router>policy-options context. See the section on ‟Route Policy” in the 7705 SAR Router Configuration Guide.

When multiple policy names are specified, the policies are evaluated in the order in which they are specified. A maximum of five (5) policy names can be configured. The first policy that matches is applied.

When multiple export commands are issued, the last command entered overrides the previous command.

By default, when no export policies are specified, RIP routes are advertised and non-RIP routes are not advertised.

The no form of the command removes the policy association with the RIP instance. To remove association of all policies, use the no export command without arguments.

Default

no export

Parameters
policy-name

the route policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed within double quotes.

export-limit
Syntax

export-limit number [log percentage]

no export-limit

Context

config>router>rip

Description

This command configures the maximum number of routes (prefixes) that can be exported into RIP from the route table. Export-limit can be configured only on the global level.

The no form of the command removes the parameters from the configuration.

Default

no export-limit

Parameters
number

specifies the maximum number of routes (prefixes) that can be exported into RIP from the route table

Values

1 to 4294967295

percentage

specifies the percentage of the export-limit at which a warning log message and SNMP notification would be sent

Values

1 to 100

group
Syntax

[no] group group-name

Context

config>router>rip

Description

This command enables the context for configuring a RIP group of neighbor interfaces.

RIP groups logically associate RIP neighbor interfaces to facilitate a common configuration for RIP interfaces.

The no form of the command deletes the RIP neighbor interface group. Deleting the group also removes the RIP configuration from all of the neighbor interfaces currently assigned to the group.

Parameters
group-name

the RIP group name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed within double quotes.

import
Syntax

import policy-name [policy-name…(up to 5 max)]

no import

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command specifies the import route policy to be used to determine which routes are accepted from peers. Route policies are configured in the config>router>policy-options context. See the section on ‟Route Policy” in the 7705 SAR Router Configuration Guide.

When multiple policy names are specified, the policies are evaluated in the order in which they are specified. A maximum of five (5) policy names can be specified. The first policy that matches is applied.

When multiple import commands are issued, the last command entered will override the previous command.

When an import policy is not specified, RIP routes are accepted by default.

The no form of the command removes the policy association with the RIP instance. To remove association of all policies, use no import without arguments.

Default

no import

Parameters
policy-name

the route policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (such as #, $, or spaces), the entire string must be enclosed within double quotes.

message-size
Syntax

message-size max-num-of-routes

no message-size

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures the maximum number of routes per RIP update message.

By default, each update can contain a maximum of 25 route advertisements. This limit is imposed by RIP specifications. RIP can be configured to send as many as 255 routes per update.

The no form of the command reverts to the default value.

Default

25

Parameters
max-num-of-routes

the maximum number of RIP routes per RIP update message, expressed as a decimal integer

Values

25 to 255

metric-in
Syntax

metric-in metric

no metric-in

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures the metric added to routes received from a RIP neighbor. The specified metric value is added to the hop count and shortens the maximum distance of the route.

When applying an export policy to a RIP configuration, the policy overrides the metric values determined through calculations involving the metric-in and metric-out values.

The no form of the command reverts to the default value.

Default

1

Parameters
metric

the value added to the metric of routes received from a RIP neighbor, expressed as a decimal integer

Values

1 to 16

metric-out
Syntax

metric-out metric

no metric-out

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures the metric assigned to routes exported into RIP and advertised to RIP neighbors. The specified metric value is added to the hop count and shortens the maximum distance of the route.

When applying an export policy to a RIP configuration, the policy overrides the metric values determined through calculations involving the metric-in and metric-out values.

The no form of the command reverts to the default value.

Default

1

Parameters
metric

the value added to the metric for routes exported into RIP and advertised to RIP neighbors, expressed as a decimal integer

Values

1 to 16

neighbor
Syntax

[no] neighbor ip-int-name

Context

config>router>rip>group

Description

This command enables the context for configuring a RIP neighbor interface.

By default, interfaces are not activated unless explicitly configured.

The no form of the command deletes the RIP interface configuration for this interface. The shutdown command in the config>router>rip>group group-name>neighbor context can be used to disable an interface without removing the configuration for the interface.

Default

No RIP interfaces are defined by default.

Parameters
ip-int-name

the IP interface name. Interface names must already be defined under the config>router>interface or config>service>ies>interface context.

preference
Syntax

preference preference

no preference

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures the route preference for routes learned from the configured peers.

The lower the preference, the higher the chance of the route being the active route. The 7705 SAR assigns the highest default preference to RIP routes as compared to routes that are direct, static, or learned via MPLS or OSPF.

Default

170

Parameters
preference

the route preference, expressed as a decimal integer

Values

1 to 255

receive
Syntax

receive receive-type

no receive

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures the type of RIP updates that will be accepted and processed.

If you specify version-2 or both, the RIP instance listens for and accepts packets sent to the broadcast (255.255.255.255) and multicast (224.0.0.9) addresses.

If version-1 is specified, the router only listens for and accepts packets sent to the broadcast address.

The default behavior is to accept and process both RIPv1 and RIPv2 messages.

The no form of the command reverts to the default value.

Default

both

Parameters
receive-type

configures the type of RIP updates that will be accepted and processed

Values

receiver-type values are both, none, version-1, and version-2, where:

both

specifies that RIP updates in either version 1 or version 2 format will be accepted

none

specifies that RIP updates will not be accepted

version-1

specifies that RIP updates in version 1 format only will be accepted

version-2

specifies that RIP updates in version 2 format only will be accepted
send
Syntax

send send-type

no send

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command specifies the type of RIP messages sent to RIP neighbors.

If broadcast or version-1 is specified, the router only listens for and accepts packets sent to the broadcast address.

The no form of the command reverts to the default value.

Default

broadcast

Parameters
send-type

configures the type of RIP messages that will be sent to RIP neighbors

Values

send-type values are broadcast, multicast, none, and version-1, where:

broadcast

sends RIPv2 formatted messages to the broadcast address

multicast

sends RIPv2 formatted messages to the multicast address

none

does not to send any RIP messages (silent listener)

version-1

sends RIPv1 formatted messages to the broadcast address
split-horizon
Syntax

split-horizon {enable | disable}

no split-horizon

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command enables the use of split-horizon.

RIP uses split-horizon with poison-reverse to avoid looping routes propagating through the network. Split-horizon with poison reverse means that routes learned from a neighbor through a given interface are advertised in updates out of the same interface but with a metric of 16 (infinity).

The split-horizon disable command enables split horizon without poison reverse. With split horizon enabled, the local router does not readvertise routes learned from a neighbor back to the neighbor.

This configuration parameter can be set at three levels: global level (applies to all groups and neighbor interfaces), group level (applies to all neighbor interfaces in the group) or neighbor level (only applies to the specified neighbor interface). The most specific value is used. In particular if no value is set (no split-horizon), the setting from the less specific level is inherited by the lower level.

The no form of the command disables split horizon.

Default

enable

Parameters
enable

enables split horizon and poison reverse

disable

disables poison reverse but leaves split horizon enabled

timers
Syntax

timers update timeout flush

no timers

Context

config>router>rip

config>router>rip>group

config>router>rip>group>neighbor

Description

This command configures values for the update, timeout, and flush RIP timers.

The RIP update timer determines how often RIP updates are sent.

If the route is not updated by the time the RIP timeout timer expires, the route is declared invalid but is maintained in the RIP database.

The RIP flush timer determines how long a route is maintained in the RIP database after it has been declared invalid. Once the flush timer expires, the route is removed from the RIP database.

The no form of the command reverts to the default values.

Parameters
update

the RIP update timer value, in seconds, expressed as a decimal integer

Values

1 to 600

Default

30

timeout

the RIP timeout value, in seconds, expressed as a decimal integer

Values

1 to 1200

Default

180

flush

the RIP flush timer value, in seconds, expressed as a decimal integer

Values

1 to 1200

Default

120

Show commands

Note: The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration.
database
Syntax

database [ip-prefix [/mask] [longer]] [peer ip-address] [detail]

Context

show>router>rip

Description

This command displays the routes in the RIP database.

Parameters
ip-prefix

the IP prefix for the IP match criterion, in dotted-decimal notation

/mask

the subnet mask length, expressed as a decimal integer

longer

displays routes matching the ip-prefix/mask and routes with longer masks

ip-address

specifies a targeted RIP peer

detail

displays detailed information about the RIP database entries

Output

The following output is an example of RIP database information, and RIP database field descriptions describes the fields.

Output example 
A:ALU-A# show router rip database
===============================================================================
RIP Route Database
===============================================================================
Destination       Peer          NextHop             Metric   Tag     TL   Valid
-------------------------------------------------------------------------------
10.0.0.10/32     10.1.7.15     10.0.0.0             2        0       163  No
10.0.0.10/32     10.1.8.14     10.0.0.0             2        0       179  No
10.0.0.14/32     10.1.8.14     10.0.0.0             1        0       179  Yes
10.0.6.0/24      10.1.7.15     10.0.0.0             11       8194    163  No
10.0.6.0/24      10.1.8.14     10.0.0.0             11       8194    179  No
10.0.7.0/24      10.1.7.15     10.0.0.0             11       8194    163  No
10.1.5.0/24      10.1.7.15     10.0.0.0             2        0       151  Yes
10.1.5.0/24      10.1.8.14     10.0.0.0             1        0       167  No
10.100.17.16/30  10.1.7.15     10.0.0.0             2        0       151  No
10.100.17.16/30  10.1.8.14     10.0.0.0             2        0       167  No
-------------------------------------------------------------------------------
No. of Routes: 10
===============================================================================
A:ALU-A#
Table 1. RIP database field descriptions

Label

Description

Destination

The RIP destination for the route

Peer

The router ID of the peer router

NextHop

The IP address of the next hop

Metric

The hop count to rate the value of different hops

Tag

The value to distinguish between internal routes (learned by RIP) and external routes (learned from other protocols)

TL

Displays how many seconds the specific route will remain in the routing table. When an entry reaches 0, it is removed from the routing table.

Valid

Yes – the route is valid

No – the route is not valid
group
Syntax

group [name] [detail]

Context

show>router>rip

Description

This command displays group information for a RIP peer group. This command can be entered with or without parameters.

When this command is entered without a group name, information for all peer groups is displayed.

When the command is issued with a specific group name, information for that specific peer group is displayed.

The Admin and Oper state fields display the RIP group’s operational state. Valid states are:

  • Up – RIP global process is configured and running

  • Down – RIP global process is administratively shut down and not running

  • Disabled – RIP global process is operationally disabled. The process must be restarted by the operator.

Parameters
name

displays information for the RIP group specified

detail

displays detailed information

Output

The following output is an example of RIP group and detailed RIP group information, and RIP group field descriptions describes the fields.

Output example 
A:ALU-A# show router rip group rip-group
===============================================================================
RIP Groups
===============================================================================
Interface                                Adm   Opr      Send    Recv     Metric
                                                        Mode     Mode    In
-------------------------------------------------------------------------------
rip-group                                Up    Down     BCast   Both     1
===============================================================================
A:ALU-A#

*A:ALU-2>show>router>rip# group rip-group detail
===============================================================================
RIP Group  (detail)
===============================================================================
-------------------------------------------------------------------------------
Group  : ‟rip_group”
-------------------------------------------------------------------------------
Description      : No Description Available
Admin State      : Up                     Oper State   : Down
Send Mode        : Broadcast              Receive Mode : Both
Metric In        : 1                      Metric Out   : 1
Split Horizon    : Enabled                Check Zero   : Disabled
Message Size     : 25                     Preference   : 100
Auth. Type       : None                   Update Timer : 30
Timeout Timer    : 180                    Flush Timer  : 120
Export Policies  : None
Import Policies  : None
===============================================================================
-------------------------------------------------------------------------------
Peer Groups : 1
===============================================================================
*A:ALU-2>show>router>rip#
Table 2. RIP group field descriptions

Label

Description

Group

The RIP group name

Interface

The interface name

Adm

Indicates whether the RIP neighbor interface is administratively up or down

Opr

Indicates whether the RIP neighbor interface is operationally up or down

Send Mode

Bcast – specifies that RIPv2 formatted messages are sent to the broadcast address

Mcast – specifies that RIPv2 formatted messages are sent to the multicast address

None – specifies that no RIP messages are sent (silent listener)

RIPv1 – specifies that RIPv1 formatted messages are sent to the broadcast address

Recv Mode

Both – specifies that RIP updates in either version 1 or version 2 format will be accepted

None – specifies that RIP updates will not be accepted

RIPv1 – specifies that RIP updates in version 1 format only are accepted

RIPv2 – specifies that RIP updates in version 2 format only are accepted

Metric In

The metric added to routes received from a RIP neighbor
neighbor
Syntax

neighbor [ip-int-name | ip-address] [detail] [advertised-routes]

Context

show>router>rip

Description

This command displays RIP neighbor information. This command can be entered with or without any parameters.

When this command is issued without any parameters, information for all RIP neighbors displays.

Parameters
ip-int-name | ip-address

displays information for the specified IP interface

Values

ipv4-address:        a.b.c.d (host bits must be 0)

detail

displays detailed RIP neighbor information

advertised-routes

displays the routes advertised to RIP neighbors. If no neighbors are specified, then all routes advertised to all neighbors are displayed. If a neighbor is specified, then only routes advertised to that neighbor are displayed.

Output

The following outputs are examples of RIP neighbor information:

Output example - RIP neighbor (standard and advertised routes) 
A:ALU-A# show router rip neighbor
===============================================================================
RIP Neighbors
===============================================================================
Interface                       Adm   Opr   Primary IP       Send   Recv   Metric
                                                             Mode   Mode   In
-------------------------------------------------------------------------------
router-2/1                      Up    Up    10.0.3.12        None   Both   1
router-2/2                      Up    Up    10.0.5.12        BCast  Both   1
router-2/3                      Up    Up    10.0.6.12        BCast  Both   1
router-2/5                      Up    Up    10.0.9.12        BCast  Both   1
router-2/6                      Up    Up    10.0.17.12       None   Both   1
router-2/7                      Up    Up    10.0.16.12       None   Both   1
===============================================================================
A:ALU-A#
Table 3. RIP neighbor field descriptions

Label

Description

Interface

The RIP neighbor name or IP address

Adm

Indicates whether the RIP neighbor interface is administratively up or down

Opr

Indicates whether the RIP neighbor interface is operationally up or down

Primary IP

The primary IP address of the RIP neighbor interface

Send Mode

Bcast – specifies that RIPv2 formatted messages are sent to the broadcast address

Mcast – specifies that RIPv2 formatted messages are sent to the multicast address

None – specifies that no RIP messages are sent (silent listener)

RIPv1 – specifies that RIPv1 formatted messages are sent to the broadcast address

Recv Mode

Both – specifies that RIP updates in either version 1 or version 2 format will be accepted

None – specifies that RIP updates will not be accepted

RIPv1 – specifies that RIP updates in version 1 format only are accepted

RIPv2 – specifies that RIP updates in version 2 format only are accepted

Metric In

The metric added to routes received from a RIP neighbor
Output example - RIP neighbor (detailed) 
A:ALU-A# show router rip neighbor detail
===============================================================================
RIP Neighbors (Detail)
===============================================================================
-------------------------------------------------------------------------------
Neighbor "router-2/7"
-------------------------------------------------------------------------------
Description   : No Description Available
Primary IP    : 10.0.16.12            Group : seven
Admin State   : Up                    Oper State : Up
Send Mode     : None                  Receive Mode : Both
Metric In     : 1                     Metric Out : 1
Split Horizon : Enabled               Check Zero : Disabled
Message Size  : 25                    Preference : 100
Auth. Type    : None                  Update Timer : 3
Timeout Timer : 6                     Flush Timer : 6
Export Policies:
   Rip2Rip
   direct2Rip
   bgp2Rip
Import Policies:
   None
===============================================================================
A:ALU-A#
Table 4. RIP neighbor (detailed) field descriptions

Label

Description

Neighbor

The RIP neighbor name or IP address

Description

The RIP neighbor description. No Description Available indicates no description is configured.

Primary IP

The RIP neighbor interface primary IP address

Group

The RIP group name of the neighbor interface

Admin State

Indicates whether the RIP neighbor interface is administratively up or down

Oper State

Indicates whether the RIP neighbor interface is operationally up or down

Send Mode

Bcast – specifies that RIPv2 formatted messages are sent to the broadcast address

Mcast – specifies that RIPv2 formatted messages are sent to the multicast address

None – specifies that no RIP messages are sent (silent listener)

RIPv1 – specifies that RIPv1 formatted messages are sent to the broadcast address

Receive Mode

Both – specifies that RIP updates in either version 1 or version 2 format will be accepted\

None – specifies that RIP updates will not be accepted

RIPv1 – specifies that RIP updates in version 1 format only are accepted

RIPv2 – specifies that RIP updates in version 2 format only are accepted

Metric In

The metric value added to routes received from a RIP neighbor

Metric Out

The value added to routes exported into RIP and advertised to RIP neighbors

Split Horizon

Indicates whether split horizon and poison reverse is Enabled or Disabled for the RIP neighbor

Check Zero

Disabled – the mandatory zero fields in RIP packets are not checked, allowing receipt of RIP messages even if mandatory zero fields are non-zero for the neighbor

Enabled – mandatory zero fields in RIP packets are checked and non-compliant RIP messages are rejected

Message Size

The maximum number of routes per RIP update message

Preference

The preference of RIP routes from the neighbor

Auth. Type

Specifies the authentication type

Update Timer

The current setting of the RIP update timer value expressed in seconds

Timeout Timer

The current RIP timeout timer value expressed in seconds

Flush Timer

The number of seconds after a route has been declared invalid that it is flushed from the route database

Export Policies

The export route policy that is used to determine routes advertised to all peers

Import Policies

The import route policy that is used to determine which routes are accepted from RIP neighbors
peer
Syntax

peer [interface-name]

Context

show>router>rip

Description

This command displays RIP peer information.

Parameters
interface-name

displays peer information for peers on the specified IP interface

Output

The following output is an example of RIP peer information, and RIP peer field descriptions describes the fields.

Output example 
A:ALU-A# show router rip peers
===============================================================================
RIP Peers
===============================================================================
Peer IP Addr     Interface Name                       Version     Last Update
-------------------------------------------------------------------------------
10.0.5.13        router-2/2                           RIPv2       0
10.0.6.16        router-2/3                           RIPv2       2
10.0.9.14        router-2/5                           RIPv2       8
10.0.10.15       router-2/4                           RIPv2       0
-------------------------------------------------------------------------------
No. of Peers: 4
===============================================================================
A:ALU-A#
Table 5. RIP peer field descriptions

Label

Description

Peer IP Addr

The IP address of the peer router

Interface Name

The peer interface name

Version

The version of RIP running on the peer

Last Update

The number of days since the last update

No. of Peers

The number of RIP peers
statistics
Syntax

statistics [ip-int-name | ip-address]

Context

show>router>rip

Description

This command displays interface level statistics for the RIP protocol.

If no IP address or interface name is specified, then all configured RIP interfaces are displayed.

If an IP address or interface name is specified, then only data about the specified RIP interface is displayed.

Parameters
ip-addr | ip-int-name

displays statistics for the specified IP interface

Output

The following output is an example of RIP statistics information, and RIP statistics field descriptions describes the fields.

Output example 
A:ALU-A# show router rip statistics
===============================================================================
RIP Statistics
===============================================================================
Learned Routes   : 0               Timed Out Routes : 0
Current Memory   : 120624          Maximum Memory : 262144
-------------------------------------------------------------------------------
Interface "to-web"
-------------------------------------------------------------------------------
Primary IP       : 10.1.1.3        Update Timer : 30
Timeout Timer    : 180             Flush Timer : 120
Counter                    Total           Last 5 Min         Last 1 Min
-------------------------------------------------------------------------------
Updates Sent               0               0                  0
Triggered Updates          0               0                  0
Bad Packets Received       0               0                  0
RIPv1 Updates Received     0               0                  0
RIPv1 Updates Ignored      0               0                  0
RIPv1 Bad Routes           0               0                  0
RIPv1 Requests Received    0               0                  0
RIPv1 Requests Ignored     0               0                  0
RIPv2 Updates Received     0               0                  0
RIPv2 Updates Ignored      0               0                  0
RIPv2 Bad Routes           0               0                  0
RIPv2 Requests Received    0               0                  0
RIPv2 Requests Ignored     0               0                  0
Authentication Errors      0               0                  0
===============================================================================
A:ALU-A#
Table 6. RIP statistics field descriptions

Label

Description

Learned Routes

The number of RIP learned routes that were exported to RIP neighbors

Timed Out Routes

The number of routes that have timed out

Current Memory

The amount of memory used by the RIP router instance

Maximum Memory

The amount of memory allocated for the RIP router instance

Interface

Displays the name of each interface configured in RIP and its associated RIP statistics

Primary IP

The interface IP address

Update Timer

The current setting of the RIP update timer value expressed in seconds

Timeout Timer

The current RIP timeout timer value expressed in seconds

Flush Timer

The number of seconds before a route that has been declared invalid is removed from the route database

Total

The total number of each corresponding RIP statistic collected

Last 5 Min

The number of each corresponding RIP statistic collected in the last 5 minutes

Last 1 Min

The number of each corresponding RIP statistic that was collected in the last minute

Updates Sent

The total number of RIP updates that have been sent

Triggered Updates

The number of triggered updates that have been sent. Triggered updates are sent before the RIP routing table is sent.

Bad Packets Received

The number of RIP updates received on this interface that were discarded as invalid

RIPv1 Updates Received

The number of RIPv1 updates received

RIPv1 Updates Ignored

The number of RIPv1 updates ignored

RIPv1 Bad Routes

The number of bad RIPv1 routes received from the peer

RIPv1 Requests Received

The number of RIPv1 requests received from other routers

RIPv1 Requests Ignored

The number of times the router ignored a RIPv1 route request from other routers

RIPv2 Updates Received

The number of RIPv2 updates received

RIPv2 Updates Ignored

The number of RIPv2 updates ignored

RIPv2 Bad Routes

The number of bad RIPv2 routes received from the peer

RIPv2 Requests Received

The number of RIPv2 requests received from other routers

RIPv2 Requests Ignored

The number of times the router ignored a RIPv2 route request from other routers

Authentication Errors

The number of authentication errors that occurred while attempting to secure table updates

Clear commands

database
Syntax

database

Context

clear>router>rip

Description

This command deletes all routes in the RIP database.

statistics
Syntax

statistics [neighbor ip-int-name | ip-address]

Context

clear>router>rip

Description

This command clears RIP neighbor statistics. You can clear statistics for a specific RIP interface or for all RIP interfaces.

Default

none

Parameters
ip-int-name | ip-address

clears the statistics for the specified RIP interface

Monitor commands

neighbor
Syntax

neighbor neighbor [neighbor...(up to 5 max)] [interval seconds] [repeat repeat] [absolute | rate]

Context

monitor>router>rip

Description

This command displays statistical RIP neighbor information at the configured interval until the configured count is reached.

The first screen displays the current statistics related to the specified RIP neighbors. The subsequent statistical information listed for each interval is displayed as a delta to the previous display. When the keyword rate is specified, the rate-per-second for each statistic is displayed instead of the delta.

Monitor commands are similar to show commands but only statistical information displays. Monitor commands display the selected statistics according to the configured number of times at the interval specified.

Parameters
neighbor

the name of the IP interface or the IP address of the neighbor

Values

ip-int-name | ip-address

seconds

configures the interval for each display, in seconds

Values

3 to 60

Default

10

repeat

configures how many times the command is repeated

Values

1 to 999

Default

10

absolute

displays raw statistics, without processing. No calculations are performed on the delta or rate statistics.

rate

displays rate-per-second for each statistic instead of the delta

Debug commands

auth
Syntax

[no] auth [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP authentication at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

error
Syntax

[no] error [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP errors at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

events
Syntax

[no] events [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP events at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

holddown
Syntax

[no] holddown [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP hold-downs at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

packets
Syntax

[no] packets [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP packets at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

request
Syntax

[no] request [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP requests at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

trigger
Syntax

[no] trigger [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP triggers at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor

updates
Syntax

[no] updates [neighbor ip-int-name | ip-address]

Context

debug>router>rip

Description

This command enables debugging for RIP updates at either the global level or neighbor level.

Parameters
ip-int-name | ip-address

the interface name or IP address of the neighbor