25
• RIP configurations made in interface view before enabling RIP take effect after RIP is enabled.
• RIP runs only on the interfaces residing on the specified networks. Specify the network after
enabling RIP to validate RIP on a specific interface.
• You can enable RIP on all interfaces using the command network 0.0.0.0.
• If a physical interface is attached to multiple networks, you cannot advertise these networks in
different RIP processes.
To enable RIP:
Ste
Command
Remarks
1. Enter system view.
system-view N/A
2. Enable a RIP process and
enter RIP view.
rip [ process-id ] [ vpn-instance
vpn-instance-name ]
Disabled by default.
3. Enable RIP on the interface
attached to the specified
network.
network network-address Disabled by default.
Configuring the interface behavior
Ste
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter RIP view.
rip [ process-id ] [ vpn-instance
vpn-instance-name ]
N/A
3. Disable an interface from
sending routing updates.
silent-interface { interface-type
interface-number | all }
Optional.
By default, all interfaces can send
routing updates.
The disabled interface can still
receive updates.
4. Return to system view.
quit N/A
5. Enter interface view.
interface interface-type
interface-number
N/A
6. Enable the interface to receive
RIP messages.
rip input
Optional.
Enabled by default.
7. Enable the interface to send
RIP messages.
rip output
Optional.
Enabled by default.
Configuring a RIP version
You can configure a RIP version in RIP view or interface view under the following conditions.
• If neither global nor interface RIP version is configured, the interface sends RIPv1 broadcasts and
can receive the following packets: RIPv1 broadcast, RIPv1 unicast, RIPv2 broadcast, RIPv2 multicast,
and RIPv2 unicast.
• If an interface has no RIP version configured, it uses the global RIP version; otherwise it uses the RIP
version configured on it.