35
Step Command Remarks
3. Configure RIPv2
authentication.
rip authentication-mode
{
md5
{
rfc2082
{
cipher
cipher-string
|
plain
plain-string
}
key-id |
rfc2453
{
cipher
cipher-string
|
plain
plain-string
} } |
simple
{
cipher
cipher-string
|
plain
plain-string
}
}
By default, RIPv2
authentication is not
configured.
Specifying a RIP neighbor
Typically RIP messages are sent in broadcast or multicast. To enable RIP on a link that does not
support broadcast or multicast, you must manually specify RIP neighbors.
Follow these guidelines when you specify a RIP neighbor:
• Do not use the peer ip-address command when the neighbor is directly connected. Otherwise,
the neighbor might receive both unicast and multicast (or broadcast) messages of the same
routing information.
• If the specified neighbor is not directly connected, disable source address check on incoming
updates.
To specify a RIP neighbor:
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. Specify a RIP neighbor.
peer
ip-address
By default, RIP does not
unicast updates to any
peer.
4. Disable source IP
address check on
inbound RIP updates
undo validate-source-address
By default, source IP
address check on inbound
RIP updates is enabled.
Configuring RIP network management
You can use network management software to manage the RIP process to which MIB is bound.
To configure RIP network management:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Bind MIB to a RIP
process.
rip mib-binding
process-id
By default, MIB is bound to the
RIP process with the smallest
process ID.
Configuring the RIP packet sending rate
Perform this task to specify the interval for sending RIP packets and the maximum number of RIP
packets that can be sent at each interval. This feature can avoid excessive RIP packets from
affecting system performance and consuming too much bandwidth.
To configure the RIP packet sending rate:
To Next Page
Loading...
Need help?
General