
44
Routing Information Protocol (RIP)
The Routing Information Protocol (RIP) tracks distances or hop counts to nearby routers when establishing network connections
and is based on a distance-vector algorithm.
RIP is based on a distance-vector algorithm; it tracks distances or hop counts to nearby routers when establishing network
connections.
RIP protocol standards are listed in the
chapter.
Protocol Overview
RIP is the oldest interior gateway protocol.
There are two versions of RIP: RIP version 1 (RIPv1) and RIP version 2 (RIPv2). These versions are documented in RFCs 1058 and
2453.
RIPv1
RIPv1 learns where nodes in a network are located by automatically constructing a routing data table.
The routing table is established after RIP sends out one or more broadcast signals to all adjacent nodes in a network. Hop counts of
these signals are tracked and entered into the routing table, which defines where nodes in the network are located.
The information that is used to update the routing table is sent as either a request or response message. In RIPv1, automatic updates
to the routing table are performed as either one-time requests or periodic responses (every 30 seconds). RIP transports its
responses or requests by means of user datagram protocol (UDP) over port 520.
RIP must receive regular routing updates to maintain a correct routing table. Response messages containing a router’s full routing
table are transmitted every 30 seconds. If a router does not send an update within a certain amount of time, the hop count to that
route is changed to unreachable (a route hop metric of 16 hops). Another timer sets the amount of time before the unreachable
routes are removed from the routing table.
This first RIP version does not support variable length subnet mask (VLSM) or classless inter-domain routing (CIDR) and is not
widely used.
RIPv2
RIPv2 adds support for subnet fields in the RIP routing updates, thus qualifying it as a classless routing protocol.
The RIPv2 message format includes entries for route tags, subnet masks, and next hop addresses. Another enhancement included in
RIPv2 is multicasting for route updates on IP multicast address 224.0.0.9.
Implementation Information
Dell Networking OS supports both versions of RIP and allows you to configure one version globally and the other version on
interfaces or both versions on the interfaces.
The following table lists the defaults for RIP in Dell Networking OS.
710
Routing Information Protocol (RIP)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...