Configuring RIP with CLI
This section provides information to configure Routing Information Protocol (RIP) using the command line interface.
Topics in this section include:
RIP and RIPng Configuration Overview
Preconfiguration Requirements
Configure the following entities before beginning the RIP configuration:
- (Optional) Policy statements should be defined in the config>router>policy-options context.
RIP Hierarchy
RIP is configured in the config>router>rip context. RIP is not enabled by default. Three hierarchical levels are included in RIP configurations:
- Global
- Group
- Neighbor
Commands and parameters configured on the global level are inherited by the group and neighbor levels although parameters configured on the group and neighbor levels take precedence over global configurations.
Basic RIP Configuration
This section provides information to configure RIP and examples of common configuration tasks. For a router to accept RIP updates, in the config>router>rip context, you must define at least one group and one neighbor. A router will ignore updates received from routers on interfaces not configured for RIP. Configuring other RIP commands and parameters are optional.
By default, the local router imports all routes from this neighbor and does not advertise routes. The router receives both RIPv1 and RIPv2 update messages with 25 to 255 route entries per message.
The RIP configuration commands have three primary configuration levels: rip for global configurations, group group-name for RIP group configurations, and neighbor ip-int-name for RIP neighbor configurations. Within the different levels, the configuration commands are identical. For the repeated commands, the command that is most specific to the neighboring router is in effect; that is, neighbor settings have precedence over group settings which have precedence over RIP global settings.
The minimal RIP parameters that need to be configured in the config>router>rip context are:
- Group
- Neighbor
The following example displays a basic RIP configuration.
Common Configuration Tasks
This section provides a brief overview of the tasks that must be performed to configure RIP and provides the CLI commands.
Configure RIP hierarchically using the global level (applies to all peers), the group level (applies to all peers in peer-group), or the neighbor level (only applies to the specified interface). 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.
Many of the hierarchical RIP commands can be used on different levels. The most specific value is used. That is, a RIP group-specific command takes precedence over a global RIP command. A neighbor-specific statement takes precedence over a global RIP or group-specific command.
All RIP instances must be explicitly created on each device. Once created, RIP is administratively enabled.
To configure RIP, perform the following tasks:
- 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 like an IP address, port, Link Aggregation Group (LAG), or the system. For more information about configuring interfaces, refer to the Interface Configuration Guide.
To configure a network interface:
The following example displays router interface configuration command usage:
The following example displays the IP configuration output showing the interface information.
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.
This section only provides brief instructions to configure route policies. For more details, refer to the Route Policy Overview chapter.
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 the RIP global, group, and neighbor import and export commands.
Use the following CLI syntax to enter the edit mode:
The following example displays some commands to configure a policy statement. Policy option commands are configured in the config>router context. Use the commit command to save the changes.
Configuring RIP Parameters
Use the CLI syntax displayed below for:
Configuring Global-Level Parameters
After the RIP protocol instance is created, the no shutdown command is not required because RIP is administratively enabled upon creation. 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. |
Use the following CLI syntax to configure global-level RIP parameters.
The following example displays global RIP configuration command usage:
The following example displays the RIP group configuration:
Configuring Group-Level Parameters
A group is a collection of related RIP peers. 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 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. Use the following CLI syntax to configure a group.
The following example displays group configuration command usage:
The following example displays the RIP group configuration:
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.
Use the following CLI syntax to add a neighbor to a group and define options that override the same group-level command value.
The following example displays neighbor configuration command usage:
The following example displays the neighbor configured in group “headquarters”.
RIP Configuration Management Tasks
Examples are provided for the following RIP configuration management tasks:
Modifying RIP Parameters
Modify, add or remove RIP parameters in the CLI. The changes are applied immediately. For the complete list of CLI commands, refer to Configuring RIP Parameters.
The following example displays the updated parameters:
Deleting a Group
A group must be shut down before it can be deleted.
Use the following CLI syntax to shut down and then delete a group.
Deleting the group without first shutting it down causes the following message to appear:
Deleting a Neighbor
The neighbor must be shut down before it can be deleted.
Use the following CLI syntax to delete a neighbor.
Deleting the neighbor without first shutting it down causes the following message to appear: