7.4. Configuring RIP with CLI
This section provides information on configuring RIP using the command line interface.
Topics in this section include:
7.5. RIP Configuration Overview
7.5.1. Preconfiguration Requirements
Before RIP can be implemented, the following entities should be configured:
- policy statements must be defined in the config>router>policy-options context
7.5.2. 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 level
- group level
- neighbor level
Commands and parameters configured at the global level are inherited by the group and neighbor level, although parameters configured at the neighbor level take precedence over global and group configurations and group level takes precedence over global level.
7.6. Basic RIP Configuration
This section provides information on configuring RIP and configuration examples of common configuration tasks. For a router to accept RIP updates, you must define at least one group and one neighbor in the config>router>rip context. 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.
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. The command that is most specific to the neighboring router takes precedence; for example, neighbor settings have precedence over RIP group-level or global-level settings.
The minimum RIP parameters that must be configured in the config>router>rip context are:
- group
- neighbor
The following is an example of a basic RIP configuration.
7.7. 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 of the hierarchical RIP commands can be used at different levels. The most specific value is used. For example, a RIP group-specific command takes precedence over a global RIP command, and a neighbor-specific command takes precedence over group-specific and global-specific RIP commands.
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
7.7.1. 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, refer to the 7705 SAR Router 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:
7.7.2. 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, refer to the 7705 SAR Router Configuration Guide, “Configuring Route Policies With CLI”.
The following example displays commands to configure a policy statement. Use the commit command to save the changes.
7.8. Configuring RIP Parameters
Use the CLI syntax below to configure global-level, group-level, and neighbor-level parameters:
7.8.1. 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 global RIP configuration command usage:
7.8.2. 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 group configuration command usage:
7.8.3. 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 neighbor configuration command usage:
7.9. RIP Configuration Management Tasks
Examples are provided for the following RIP configuration management tasks:
7.9.1. Modifying RIP Parameters
When RIP parameters are modified, added, or removed, the changes are applied immediately. For the complete list of CLI commands, refer to Configuring RIP Parameters.
The following example displays the updated parameters:
7.9.2. 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.
If you try to delete the group without shutting it down first, the following message appears:
7.9.3. 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.
If you try to delete the neighbor before it is shut down, the following message appears: