Configuring Zero Field Check On Ripng Packets; Configuring The Maximum Number Of Ecmp Routes; Applying Ipsec Policies For Ripng - HPE 5800 Series Configuration Manual

Step
Enable the poison reverse
3.
function.

Configuring zero field check on RIPng packets

Some fields in the RIPng packet must be zero, which are called "zero fields." With zero field check on
RIPng packets enabled, if such a field contains a non-zero value, the entire RIPng packet is
discarded. If you are sure that all packets are reliable, disable the zero field check to reduce the CPU
processing time.
To configure RIPng zero field check:
Step
Enter system view.
1.
Enter RIPng view.
2.
Enable the zero field check.
3.

Configuring the maximum number of ECMP routes

Step
Enter system view.
1.
Enter RIPng view.
2.
Configure the maximum
3.
number of ECMP routes for
load balancing.

Applying IPsec policies for RIPng

To protect routing information and defend attacks, RIPng supports using an IPsec policy to
authenticate protocol packets.
Outbound RIPng packets carry the Security Parameter Index (SPI) defined in the relevant IPsec
policy. A device uses the SPI carried in a received packet to match against the configured IPsec
policy. If they match, the device accepts the packet. Otherwise, it discards the packet and does not
establish a neighbor relationship with the sending device.
You can configure an IPsec policy for a RIPng process or interface. The IPsec policy configured for a
process applies to all packets in the process. The IPsec policy configured on an interface applies to
packets on the interface. If an interface and its process each have an IPsec policy configured, the
interface uses its own IPsec policy.
Configuration prerequisites
Before you apply an IPsec policy to RIPng, complete following tasks:
Command
ripng poison-reverse
Command
system-view
ripng [ process-id ]
[ vpn-instance
vpn-instance-name ]
checkzero
Command
system-view
ripng [ process-id ] [ vpn-instance
vpn-instance-name ]
maximum load-balancing
number
258
Remarks
Disabled by default.
Remarks
N/A
N/A
Optional.
Enabled by default.
Remarks
N/A
N/A
Optional.
By default, the maximum number
of ECMP routes for load
balancing is 16.