Protocols And Standards; Configuring Rip Basic Functions; Configuration Prerequisites; Configuration Procedure - 3Com S7906E Configuration Manual

RFC 1723 only defines plain text authentication. For information about MD5 authentication, refer to
RFC 2453 "RIP Version 2".
With RIPv1, you can configure the authentication mode in interface view. However, the
configuration will not take effect because RIPv1 does not support authentication.

Supported RIP Features

The current implementation supports the following RIP features.
RIPv1 and RIPv2
RIP multi-instance.
RIP can serve as the IGP running between CE and PE on a BGP/MPLS VPN network. For related
information, refer to MPLS L3VPN Configuration in the MPLS Volume.
BFD
RIP periodically sends route update requests to neighbors. If no route update response for a route is
received within the specified interval, RIP considers the route unreachable. This mechanism cannot
detect link faults quickly. After BFD is configured for RIP, when BFD detects a broken link, RIP can
quickly age out the unreachable route, thus avoiding interference to other services.

Protocols and Standards

RFC 1058: Routing Information Protocol
RFC 1723: RIP Version 2 - Carrying Additional Information
RFC 1721: RIP Version 2 Protocol Analysis
RFC 1722: RIP Version 2 Protocol Applicability Statement
RFC 1724: RIP Version 2 MIB Extension
RFC 2082: RIPv2 MD5 Authentication
RFC 2091: Triggered Extensions to RIP to Support Demand Circuits
RFC 2453: RIP Version 2

Configuring RIP Basic Functions

Configuration Prerequisites

Before configuring RIP basic functions, complete the following tasks.
Configure the link layer protocol.
Configure an IP address on each interface, and make sure all adjacent routers are reachable to
each other.

Configuration Procedure

Enabling RIP and a RIP interface
Follow these steps to enable RIP:
1-5