H3C Technologies H3C SR8800 - Manual (Page 43)

27
• Update response (Type-10)—Contains the routes requested by the neighbor.
• Update Acknowledge (Type-11)—Acknowledges received update responses.
TRIP retransmission mechanism
• If a router receives no update responses within a specified interval after sending an update request,
it sends the request again. If the router still receives no update response after the upper limit for
sending requests is reached, it considers the neighbor unreachable.
• If a router receives no update acknowledge within a specified interval after sending an update
response, it sends the update response again. If the router still receives no update acknowledge
after the upper limit for sending update responses is reached, it considers the neighbor
unreachable.
Supported RIP features
The current implementation supports the following RIP features:
• RIPv1 and RIPv2.
• RIP support for multi-VPN-instance.
RIP can serve as the IGP running between CE and PE on an MPLS L3VPN network. For related
information, see MPLS Configuration Guide.
• TRIP
• RIP FRR
• 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, and 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
RIP configuration task list
Complete the following tasks to configure RIP:
Task Remarks
Configuring RIP basic functions Required