![]() | Note: RIP commands are only supported on 7210 SAS-Mxp. |
This command creates a text description stored in the configuration file for a configuration context.
The no form of this command removes any description string from the context.
This command administratively disables an entity. Shutting down an entity does not change, reset, or remove any configuration settings or statistics. Many objects must be shut down before they may be deleted.
The shutdown command administratively shuts down an entity. Administratively shutting down an entity changes the operational state of the entity to down and the operational state of any entities contained within the administratively down entity.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system generated configuration files.
The no form of this command puts an entity into the administratively enabled state.
This command enables the context to configure the RIP protocol instance.
When a RIP instance is created, the protocol is enabled by default. To start or suspend execution of the RIP protocol without affecting the configuration, use the [no] shutdown command.
The no form of this command deletes the RIP protocol instance removing all associated configuration parameters.
no rip
This command sets the authentication password that is passed between RIP neighbors.
The authentication type and authentication key must match exactly for the RIP message to be considered authentic and processed.
The no form of this command removes the authentication password from the configuration and disables authentication.
no authentication-key
This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.
This command sets the type of authentication that is used between RIP neighbors.
The type and password must match exactly for the RIP message to be considered authentic and processed.
The no form of this command removes the authentication type from the configuration and effectively disables authentication.
no authentication-type
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.
This command can be set at all RIP 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 check-zero), the setting from the less specific level is inherited by the lower level.
The no form of this command removes the check-zero command from the configuration.
This command specifies the export route policies used to determine which routes are exported to RIP.
If no export policy is specified, non-RIP routes are not exported from the routing table manager to RIP. RIP-learned routes are exported to RIP neighbors.
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 overrides the previous command. A maximum of five policy names can be specified.
The no form of this command removes all policies from the configuration.
no export
The specified names must already be defined.
This command configures the maximum number of routes (prefixes) that can be exported into RIP from the route table.
The no form of this command removes the parameters from the configuration.
no export-limit
This command enables the context to configure a RIP group of neighbor interfaces.
RIP groups are a way of logically associating RIP neighbor interfaces to facilitate a common configuration for RIP interfaces.
The no form of this command deletes the RIP neighbor interface group. Deleting the group also removes the RIP configuration of all the neighbor interfaces currently assigned to this group.
no group
This command configures import route policies to determine which routes are accepted from RIP neighbors. If no import policy is specified, RIP accepts all routes from configured RIP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.
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 import commands are issued, the last command entered overrides the previous command. A maximum of five policy names can be specified.
The no form of this command removes all policies from the configuration.
no import
The specified names must already be defined.
This command configures the maximum number of routes per RIP update message.
The no form of this command reverts to the default value.
message-size 25
This command configures the metric added to routes received from a RIP neighbor.
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 this command reverts to the default value.
metric-in 1
This command configures the metric assigned to routes exported into RIP and advertised to RIP neighbors.
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 this command reverts to the default value.
metric-out 1
This command enables the context for configuring a RIP neighbor interface.
By default, interfaces are not activated in an interior gateway protocol, such as RIP, unless explicitly configured.
The no form of this command deletes the RIP interface configuration for this interface. The shutdown command in the config>router>rip>group>neighbor context can be used to disable an interface without removing the configuration for the interface.
no neighbor
If the IP interface name does not exist or does not have an IP address configured, an error message is returned.
This command configures the preference for RIP routes.
A route can be learned by the router from different protocols, in which case the costs (metrics) are not comparable. When this occurs the preference is used to decide which route is used.
Different protocols should not be configured with the same preference, if this occurs the tiebreaker is made according to the default preference table defined in Table 25. If multiple routes are learned with an identical preference using the same protocol, the lowest cost route is used.
If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, the decision of which route to use is determined by the configuration of the ecmp command in the config>router context.
The no form of this command reverts to the default value.
preference 100
Route Type | Preference | Configurable |
Direct attached | 0 | No |
Static routes | 5 | Yes |
OSPF internal | 10 | Yes |
IS-IS level 1 internal | 15 | Yes |
IS-IS level 2 internal | 18 | Yes |
RIP | 100 | Yes |
OSPF external | 150 | Yes |
IS-IS level 1 external | 160 | Yes |
IS-IS level 2 external | 165 | Yes |
This command configures the types of RIP updates that are accepted and processed.
If both or version-2 is specified, the RIP instance listens for and accepts packets sent to the broadcast and multicast (224.0.0.9) addresses.
If version-1 is specified, the router only listens for and accept packets sent to the broadcast address.
This control can be issued at the global, group, or interface level. The default behavior is to accept and process both RIPv1 and RIPv2 messages.
The no form of this command reverts to the default value.
receive both
This command specifies the type of RIP messages sent to RIP neighbors.
If version-1 is specified, the router need only listen for and accept packets sent to the broadcast address.
This control can be issued at the global, group, or interface level.
The no form of this command reverts to the default value.
send broadcast
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 specific 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. This allows the routes to be readvertised on interfaces other than the interface that learned the route, with the advertised metric equaling an increment of the metric-in value.
This configuration parameter can be set at the following 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 this command disables split horizon, which allows the lower level to inherit the setting from an upper level.
split-horizon enable
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. When the flush timer expires, the route is removed from the RIP database.
The no form of this command reverts to the default values.
timers 30 180 120
This command displays the routes in the RIP database.
The following output is an example of RIP database information, and Table 26 describes the output fields.
Label | Description |
Destination | Displays the RIP destination for the route |
Peer | Displays the router ID of the peer router |
Interface | Displays the IP address of the interface |
Metric | Displays the hop count to rate the value of different hops |
TTL | Displays how many seconds the specific route remains in the routing table. When an entry reaches 0, it is removed from the routing table. |
Valid | No — the route is not valid Yes — the route is valid |
This command displays RIP group information.
The following outputs are examples of RIP group information, and the corresponding tables describe the output fields.
Label | Description |
Group | Displays the RIP group name |
Adm | Down — the RIP group is administratively down Up — the RIP group is administratively up |
Opr | Down — the RIP group is operationally down Up — the RIP group is operationally up |
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 (that is, 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 are not 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 | Displays the metric value added to routes received from a RIP neighbor |
Label | Description |
Description | Displays the RIP group description. No Description Available indicates no description is configured. |
Admin State | Indicates whether the RIP group interface is administratively up or down |
Oper State | Indicates whether the RIP group 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 are accepted None — specifies that RIP updates are not 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 | Displays the metric value added to routes received from a RIP neighbor |
Metric Out | Displays 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 | Displays the maximum number of routes per RIP update message |
Preference | Displays the preference of RIP routes from the neighbor |
Auth. Type | Specifies the authentication type |
Update Timer | Displays the current setting of the RIP update timer value expressed in seconds |
Timeout Timer | Displays the current RIP timeout timer value expressed in seconds |
Flush Timer | Displays the number of seconds after a route has been declared invalid that it is flushed from the route database |
Export Policies | Displays the export route policy that is used to determine routes advertised to all peers |
Import Policies | Displays the import route policy that is used to determine which routes are accepted from RIP neighbors |
This command displays RIP neighbor interface information.
The following outputs are examples of RIP neighbor information, and the corresponding tables describe the output fields.
Label | Description |
Neighbor | Displays the RIP neighbor interface name |
Adm | Down — RIP neighbor interface is administratively down Up — RIP neighbor interface is administratively up |
Opr | Down — RIP neighbor interface is operationally down Up — RIP neighbor interface is operationally up |
Primary IP | Displays 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 (that is, 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 are accepted None — Specifies that RIP updates are not 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 | Displays the metric added to routes received from a RIP neighbor |
Label | Description |
Neighbor | Displays the RIP neighbor name |
Description | Displays the RIP neighbor description. No Description Available indicates no description is configured. |
Primary IP | Displays the RIP neighbor interface primary IP address |
Group | Displays the RIP group name of the neighbor interface |
Admin State | Down — RIP neighbor interface is administratively down Up — RIP neighbor interface is administratively up |
Oper State | Down — RIP neighbor interface is operationally down Up — RIP neighbor interface is operationally up |
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 (that is, 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 are accepted None — Specifies that RIP updates are not 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 | Displays the metric value added to routes received from a RIP neighbor |
Metric Out | Displays the value added to routes exported into RIP and advertised to RIP neighbors |
Split Horizon | Disabled — split horizon disabled for the neighbor Enabled — split horizon and poison reverse enabled for the neighbor |
Check Zero | Disabled — checking of the mandatory zero fields in the RIPv1 and RIPv2 specifications are not checked allowing receipt of RIP messages even if mandatory zero fields are non-zero for the neighbor Enabled — checking of the mandatory zero fields in the RIPv1 and RIPv2 specifications and rejecting non-compliant RIP messages is enabled for the neighbor |
Message Size | Displays the maximum number of routes per RIP update message |
Preference | Displays the preference of RIP routes from the neighbor |
Auth. Type | Specifies the authentication type |
Update Timer | Displays the current setting of the RIP update timer value expressed in seconds |
Timeout Timer | Displays the current RIP timeout timer value expressed in seconds |
Export Policies | Displays the export route policy that is used to determine routes advertised to all peers |
Import Policies | Displays the import route policy that is used to determine which routes are accepted from RIP neighbors |
This command displays RIP peer information.
The following output is an example of RIP peer information, and Table 31 describes the output fields.
Label | Description |
Peer IP Addr | Displays the IP address of the peer router |
Interface Name | Displays the peer interface name |
Version | Displays the version of RIP running on the peer |
Last Update | Displays the number of days since the last update |
No. of Peers | Displays the number of RIP peers |
This command displays interface level statistics for the RIP protocol.
If no IP address or interface name is specified, all configured RIP interfaces are displayed.
If an IP address or interface name is specified, only data regarding the specified RIP interface is displayed.
The following output is an example of RIP statistics information, and Table 32 describes the output fields.
Label | Description |
Learned Routes | Displays the number of RIP-learned routes that were exported to RIP neighbors |
Timed Out Routes | Displays the number of routes that have been timed out |
Current Memory | Displays the amount of memory used by this RIP router instance |
Maximum Memory | Displays the amount of memory allocated for this RIP router instance |
Interface | Displays the name of each interface configured in RIP and associated RIP statistics. |
Primary IP | Displays the interface IP address |
Update Timer | Displays the current setting of the RIP update timer value expressed in seconds |
Timeout Timer | Displays the current RIP timeout timer value expressed in seconds |
Flush Timer | Displays the number of seconds after a route has been declared invalid that it is flushed from the route database |
Updates Sent | Total — total number of RIP updates that were sent Last 5 Min — number of RIP updates that were sent in the last 5 minutes Last 1 Min — number of RIP updates that were sent in the last 1 minute |
Triggered Updates | Total — total number of triggered updates sent. These updates are sent before the entire RIP routing table is sent Last 5 Min — number of triggered updates that were sent in the last 5 minutes Last 1 Min — number of triggered updates that were sent in the last 1 minute |
Bad Packets Received | Total — total number of RIP updates received on this interface that were discarded as invalid Last 5 Min — number of RIP updates received on this interface that were discarded as invalid in the last 5 minutes Last 1 Min — number of RIP updates received on this interface that were discarded as invalid in the last 1 minute |
RIPv1 Updates Received | Total — total number of RIPv1 updates received Last 5 Min — number of RIPv1 updates received in the last 5 minutes Last 1 Min — number of RIPv1 updates received in the last 1 minute |
RIPv1 Updates Ignored | Total — total number of RIPv1 updates ignored Last 5 Min — number of RIPv1 updates ignored in the last 5 minutes Last 1 Min — number of RIPv1 updates ignored in the last 1 minute |
RIPv1 Bad Routes | Total — total number of bad routes received from the peer Last 5 Min — number of bad routes received from the peer in the last 5 minutes Last 1 Min — number of bad routes received from the peer in the last minute |
RIPv1 Requests Received | Total — total number of times the router received RIPv1 route requests from other routers Last 5 Min — number of times the router received RIPv1 route requests from other routers in the last 5 minutes Last 1 Min — The number of times the router received RIPv1 route requests from other routers in the last 1 minute |
RIPv1 Requests Ignored | Total — total number of times the router ignored RIPv1 route requests from other routers Last 5 Min — number of times the router ignored RIPv1 route requests from other routers in the last 5 minutes Last 1 Min — number of times the router ignored RIPv1 route requests from other routers in the last 1 minute |
RIPv2 Updates Received | Total — total number of RIPv2 updates received Last 5 Min — number of RIPv2 updates received in the last 5 minutes Last 1 Min — number of RIPv2 updates received in the last minute |
RIPv2 Updates Ignored | Total — total number of RIPv2 updates ignored Last 5 Min — number of RIPv2 updates ignored in the last 5 minutes Last 1 Min — number of RIPv2 updates ignored in the last minute |
RIPv2 Bad Routes | Total — total number of RIPv2 bad routes received from the peer Last 5 Min — number of RIPv2 bad routes received from the peer in the last 5 minutes Last 1 Min — number of RIPv2 bad routes received from the peer in the last minute |
RIPv2 Requests Received | Total — total number of times the router received RIPv2 route requests from other routers Last 5 Min — number of times the router received RIPv2 route requests from other routers in the last 5 minutes Last 1 Min — number of times the router received RIPv2 route requests from other routers in the last minute |
RIPv2 Requests Ignored | Total — total number of times the router ignored RIPv2 route requests from other routers Last 5 Min — number of times the router ignored RIPv2 route requests from other routers in the last 5 minutes Last 1 Min — number of times the router ignored RIPv2 route requests from other routers in the last minute |
Authentication Errors | Total — total number of authentication errors to secure table updates Last 5 Min — number of authentication errors to secure table updates in the last 5 minutes Last 1 Min — number of authentication errors to secure table updates in the last minute |
This command clears all routes in the RIP database.
This command re-evaluates all effective export policies.
This command clears statistics for RIP neighbors.
This command enables debugging for RIP authentication.
This command enables debugging for RIP errors.
This command enables debugging for RIP events.
This command enables debugging for RIP hold downs.
This command enables debugging for RIP packets.
This command enables debugging for RIP requests.
This command enables debugging for RIP trigger updates.
This command enables debugging for RIP updates.