Enabling split horizon
The split horizon function disables an interface from sending routes received from the interface to prevent
routing loops between adjacent routers.
Follow these steps to enable split horizon:
To do...
Enter system view
Enter interface view
Enable split horizon
Enabling poison reverse
The poison reverse function allows an interface to advertise the routes received from it, but the metric of
these routes is set to 16, making them unreachable. This can avoid routing loops between neighbors.
Follow these steps to enable poison reverse:
To do...
Enter system view
Enter interface view
Enable poison reverse
Configuring the maximum number of load balanced routes
This task allows you to implement load balancing over multiple equal-cost RIP routes.
Follow these steps to configure the maximum number of load balanced routes:
To do...
Enter system view
Enter RIP view
Configure the maximum number of
load balanced routes
Enabling zero field check on incoming RIPv1 messages
Some fields in the RIPv1 message must be zero. These fields are called "zero fields." You can enable zero
field check on received RIPv1 messages. If such a field contains a non-zero value, the RIPv1 message will
not be processed. If you are certain that all messages are trustworthy, then disable zero field check to
save CPU resources.
This feature does not apply to RIPv2 packets, because they have no zero fields.
Follow these steps to enable zero field check on incoming RIPv1 messages:
Use the command...
system-view
interface interface-type
interface-number
rip split-horizon
Use the command...
system-view
interface interface-type
interface-number
rip poison-reverse
Use the command...
system-view
rip [ process-id ] [ vpn-instance
vpn-instance-name ]
maximum load-balancing number
32
Remarks
—
—
Optional
Enabled by default
Remarks
—
—
Required
Disabled by default
Remarks
––
––
Optional
8 by default