336
Configuring split horizon
Split horizon disables RIPng from sending routes through the interface where the routes were
learned to prevent routing loops between neighbors.
As a best practice, enable split horizon to prevent routing loops in normal cases.
To configure split horizon:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter interface view.
interface
interface-type
interface-number
N/A
3. Enable split horizon.
ripng split-horizon
By default, split horizon is
enabled.
Configuring poison reverse
Poison reverse enables a route learned from an interface to be advertised through the interface.
However, the metric of the route is set to 16, which means the route is unreachable.
To configure poison reverse:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter interface view.
interface
interface-type
interface-number
N/A
3. Enable poison reverse.
ripng poison-reverse
By default, poison reverse is
disabled.
Configuring zero field check on RIPng packets
Some fields in the RIPng packet header must be zero. These fields are called zero fields. You can
enable zero field check on incoming RIPng packets. If a zero field of a packet contains a non-zero
value, RIPng does not process the packets. If you are certain that all packets are trustworthy, disable
the zero field check to save CPU resources.
To configure RIPng zero field check:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter RIPng view.
ripng
[ process-id ]
[
vpn-instance
vpn-instance-name ]
N/A
3. Enable the zero field check
on incoming RIPng packets.
checkzero
By default, this feature is enabled.
Configuring the maximum number of ECMP routes
Step Command Remarks
1. Enter system view.
system-view
N/A