Use these commands to configure RIP properties that apply to all interfaces configured for RIP:
set rip auto-summary {on | off} update-interval {<1-65535> | default} expire-interval {<1-65535> | default} |
Parameters
Parameter |
Description |
---|---|
|
Automatically aggregates and redistributes classful RIP Version 1 into RIP. This applies only to RIP Version 1. If the Auto summarization field option is unchecked, you must do the aggregation and redistribution manually by using route aggregation and route redistribution. Note - Take care when you set this parameter, as RIP has no protocol mechanism to detect misconfiguration.
|
|
The amount of time, in seconds, between regularly scheduled RIP updates. To prevent synchronization of periodic updates, RIP updates are actually sent at a time from the uniform distribution on the interval (0.5T, 1.5T) where T corresponds to the Update Interval value. Note - Take care when you set this parameter, as RIP has no protocol mechanism to detect misconfiguration. |
|
A value of 30 seconds. |
|
The amount of time, in seconds, that must pass without receiving an update for a given route before the route is considered to have timed out. This value should be 6 times the update interval in order to allow for the possibility that packets containing an update could be dropped by the network. |
|
A value of 180 seconds. |
Use these commands to configure RIP properties that apply to a RIP interface:
set rip interface <if_name> {off | on} version {1 | 2} on metric {<0-16> | default} accept-updates {on | off} send-updates {on | off} transport {multicast | broadcast} authtype none simple password md5 secret secret [cisco-compatibility] {on | off} virtual address {on | off} |
Parameters
Parameter |
Description |
|
Turn on or turn off RIP on the interface.
|
|
The version of RIP to run. If you specify version 2, the default is to send full version 2 packets on the RIP multicast address.
|
|
The RIP metric to be added to routes that are sent using the specified interface(s). The default is zero. This is used to make other routers prefer other sources of RIP routes over this router. |
|
A value of 0. |
|
Whether RIP packets from other routers using the interface are accepted or ignored. Ignoring an update may result in suboptimal routing.
|
|
Whether RIP packets should be sent via the interface. This causes the interface to be a passive RIP listener. |
|
The transport mechanism. Selecting Multicast specifies that RIP version 2 packets should be multicast on this interface. This is the default. Note - When you use RIP 2, always select multicast. We recommend that you do not operate RIP 1 and RIP 2 together. |
|
There is no authentication scheme for the interface to accept routing information from neighboring routers. This option applies to rip version 2 only. In general, routers on a given link must agree on the authentication configuration in order to form neighbor adjacencies. This is used to guarantee that routing information is accepted only from trusted routers. |
|
Implement a simple authentication scheme for the interface to accept routing information from neighboring routers. Enter the Simple Password, from 1 to 16 characters. Must contain alphanumeric characters only. This option applies to RIP version 2 only. |
|
Implement an authentication scheme that uses an MD5 algorithm for the interface to accept routing information from neighboring routers. Enter the password. |
|
Make RIP run only on the VRRP Virtual IP address associated with this interface. If this router is not a VRRP Master then RIP will not run if this option is selected. It will only run on the VRRP Master. Note - You must use Monitored Circuit mode when configuring VRRP to work with virtual IPs, and when configuring virtual IP support for any dynamic routing protocol, including RIP. For more information, see ICMP Router Discovery.
|
|
To ensure interoperability with Cisco routers running RIP MD5 authentication, enable Cisco Compatibility. By default, RIP MD5 is set to conform to the Check Point standard, and not for Cisco compatibility.
|