Configuring the interface behavior, Configuring a rip version – H3C Technologies H3C SecPath F1000-E User Manual

Page 378

Advertising
background image

353

Configuring the interface behavior

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.

Disable an or all interfaces from
sending routing updates (the

interfaces can still receive

updates).

silent-interface { interface-type
interface-number
| all }

Optional.
By default, all interfaces can
send routing updates.

4.

Return to system view.

quit

N/A

5.

Enter interface view.

interface interface-type
interface-number

N/A

6.

Enable the interface to receive
RIP messages.

rip input

Optional.
Enabled by default.

7.

Enable the interface to send RIP

messages.

rip output

Optional.
Enabled by default.

Configuring a RIP version

You can configure a RIP version in RIP or interface view.

If neither global nor interface RIP version is configured, the interface sends RIPv1 broadcasts and
can receive the following packets: RIPv1 broadcast, RIPv1 unicast, RIPv2 broadcast, RIPv2 multicast,

and RIPv2 unicast.

If an interface has no RIP version configured, it uses the global RIP version; otherwise it uses the RIP
version configured on it.

With RIPv1 configured, an interface sends RIPv1 broadcasts, and can receive RIPv1 broadcasts
and RIPv1 unicasts.

With RIPv2 configured, a multicast interface sends RIPv2 multicasts and can receive RIPv2 unicasts,
broadcasts, and multicasts.

With RIPv2 configured, a broadcast interface sends RIPv2 broadcasts and can receive RIPv1
unicasts, and broadcasts, and RIPv2 broadcasts, multicasts, and unicasts.

To configure a RIP version:

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

Advertising