[no] rip
config>router
Commands in this context 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
authentication-key [authentication-key | hash-key] [hash | hash2]
no authentication-key
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the authentication key. Allowed values are any string up to 16 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
Specifies the hash key. The key can be any combination of ASCII characters up to 33 characters (encrypted). If spaces are used in the string, enclose the entire string 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.
Keyword to specify 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.
Keyword to specify 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 {none | password | message-digest | message-digest-20}
no authentication-type
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Keyword that explicitly disables authentication at a specific level (global, group, neighbor). If the command does not exist in the configuration, the parameter is inherited.
Keyword to enable simple password (plain text) authentication. If authentication is enabled and no authentication type is specified in the command, simple password authentication is enabled.
Keyword to configure 16-byte message digest for MD5 authentication. If this option is configured, at least one message-digest key must be configured.
Keyword to configure 20-byte message digest for MD5 authentication in accordance with RFC 2082, RIP-2 MD5 Authentication. If this option is configured, at least one message-digest key must be configured.
check-zero {enable | disable}
no check-zero
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
This command enables checking for zero values in fields specified to be zero by the RIPv1 and RIPv2 specifications.
This command enables checking of the mandatory zero fields in the RIPv1 and RIPv2 specifications and rejecting of non-compliant RIP messages.
This 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 this command from the configuration.
By default, check-zero is disabled at the global RIP instance level.
Keyword to reject RIP messages that do not have zero in the RIPv1 and RIPv2 mandatory fields.
Keyword to allow the receipt of RIP messages that do not have the mandatory zero fields reset.
export policy-name [policy-name… (up to 5 max)]
no export
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the export route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The specified names must already be defined.
export-limit number [log percentage]
no export-limit
config>router>rip
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
Specifies the maximum number of routes (prefixes) that can be exported into RIP from the route table.
Specifies the percentage of the export-limit, at which a warning log message and SNMP notification are sent.
[no] group group-name
config>router>rip
This command configures 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
Specifies the RIP group name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
import policy-name [policy-name…(up to 5 max)]
no import
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the import route policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The specified names must already be defined.
message-size max-num-of-routes
no message-size
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the maximum number of RIP routes per RIP update message, expressed as a decimal integer.
metric-in metric
no metric-in
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the value added to the metric of routes received from a RIP neighbor, expressed as a decimal integer.
metric-out metric
no metric-out
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the value added to the metric for routes exported into RIP and advertised to RIP neighbors, expressed as a decimal integer.
[no] neighbor ip-int-name
config>router>rip>group
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
Specifies the IP interface name. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. Interface names can be any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
If the IP interface name does not exist or does not have an IP address configured, an error message is returned.
preference preference
no preference
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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: Route preference defaults by route type . 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
Specifies the preference for RIP routes expressed as a decimal integer. The following table lists the defaults for different route types.
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 |
receive {both | none | version-1 | version-2}
no receive
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Keyword to specify that RIP updates in either version 1 or version 2 format are accepted.
Keyword to specify that RIP updates are not accepted.
Keyword to specify that RIP updates in version 1 format only are accepted.
Keyword to specify that RIP updates in version 2 format only are accepted.
send {broadcast | multicast | none | version-1}
no send
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Keyword that sends RIPv2 formatted messages to the broadcast address.
Keyword that sends RIPv2 formatted messages to the multicast address.
Keyword that specifies not to send any RIP messages (that is, silent listener).
Keyword that sends RIPv1 formatted messages to the broadcast address.
split-horizon {enable | disable}
no split-horizon
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Keyword to enable split horizon and poison reverse.
Keyword to disable split horizon, allowing routes to be readvertised on the same interface on which they were learned with the advertised metric incremented by the metric-in value.
timers update timeout flush
no timers
config>router>rip
config>router>rip>group
config>router>rip>group>neighbor
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
Specifies the RIP update timer value in seconds, expressed as a decimal integer.
Specifies the RIP timeout timer value in seconds, expressed as a decimal integer.
Specifies the RIP flush timer value in seconds, expressed as a decimal integer.