Configuring The Maximum Number Of Load Balanced Routes; Enabling Zero Field Check On Incoming Ripv1 Messages; Enabling Source Ip Address Check On Incoming Rip Updates - H3C LS-3100-52P-OVS-H3 Operation Manual

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

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 sure that all messages are trusty, you can disable zero field
check to save CPU resources.
This task does not apply to RIPv2 packets that have no zero fields.
Follow these steps to enable zero field check on incoming RIPv1 messages:
To do...
Enter system view
Enter RIP view
Enable zero field check on
received RIPv1 messages

Enabling Source IP Address Check on Incoming RIP Updates

You can enable source IP address check on incoming RIP updates.
For a message received, RIP compares the source IP address of the message with the IP address of
the interface. If they are not in the same network segment, RIP discards the message.
Follow these steps to enable source IP address check on incoming RIP updates:
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
Use the command...
system-view
rip [ process-id ] [ vpn-instance
vpn-instance-name ]
checkzero
1-13
Remarks
—
—
Required
Disabled by default
Remarks
––
––
Optional
4 by default
Remarks
––
––
Optional
Enabled by default