H3C Technologies H3C S12500 Series Switches - Manual (Page 48)

32
Configuring the maximum number of ECMP routes
Perform this task to implement load sharing over ECMP routes.
To configure the maximum number of ECMP routes:
Step 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. Configure the
maximum number of
ECMP routes.
maximum load-balancing
number
Optional.
By default, the maximum number of ECMP
routes is 32.
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 a zero field contains a non-zero value, the RIPv1 message is
not processed. If you are certain that all messages are trustworthy, disable zero field check to save CPU
resources.
This feature does not apply to RIPv2 packets, because they have no zero fields.
To enable zero field check on incoming RIPv1 messages:
Step 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. Enable zero field check on
received RIPv1 messages. Checkzero Optional.
Enabled by default.
Enabling source IP address check on incoming RIP updates
You can enable source IP address check on incoming RIP updates.
For a message received on an Ethernet interface, 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.
For a message received on a serial interface, RIP checks whether the source address of the message is the
IP address of the peer interface. If not, RIP discards the message.
IMPORTANT:
Disable the source IP address check feature if the RIP neighbor is not directly connected.
To enable source IP address check on incoming RIP updates: