Specifying A Rip Neighbor; Configuring Rip-To-Mib Binding - 3Com 4510G Configuration Manual

In plain text authentication, the authentication information is sent with the RIP message, which
however cannot meet high security needs.
Follow these steps to configure RIPv2 message authentication:
To do...
Enter system view
Enter interface view
Configure RIPv2
authentication
This task does not apply to RIPv1 because RIPv1 does not support authentication. Although you can
specify authentication modes for RIPv1 in interface view, the configuration does not take effect.

Specifying a RIP Neighbor

Usually, RIP sends messages to broadcast or multicast addresses. On non broadcast or multicast links,
you need to manually specify RIP neighbors. If a specified neighbor is not directly connected, you must
disable source address check on incoming updates.
Follow these steps to specify a RIP neighbor:
To do...
Enter system view
Enter RIP view
Specify a RIP neighbor
Disable source address check
on incoming RIP updates
You need not use the peer ip-address command when the neighbor is directly connected;
otherwise the neighbor may receive both the unicast and multicast (or broadcast) of the same
routing information.
If a specified neighbor is not directly connected, you need to disable source address check on
incoming updates.

Configuring RIP-to-MIB Binding

This task allows you to enable a specific RIP process to receive SNMP requests.
Use the command...
system-view
interface interface-type interface-number
rip authentication-mode { md5 { rfc2082
key-string key-id | rfc2453 key-string } | simple
password }
Use the command...
system-view
rip [ process-id ]
peer ip-address
undo validate-source-address
3-14
Remarks
––
––
Required
Remarks
––
––
Required
Required
Not disabled by default