Enabling poison reverse – H3C Technologies H3C SR8800 User Manual

Page 52

Advertising
background image

36

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.
To enable 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.

rip poison-reverse

Disabled by default

Configuring the maximum number of load balanced routes

This task allows you to implement load balancing over multiple equal-cost RIP routes.
To configure the maximum number of load balanced 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 load balanced

routes.

maximum load-balancing number

Optional

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, disable zero field check to save CPU

resources.
This feature does not apply to RIPv2 packets that 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.

Advertising