© Copyright IBM Corp. 2011
211
Chapter 18. Routing Information Protocol
In a routed environment, routers communicate with one another to keep track of
available routes. Routers can learn about available routes dynamically using the
Routing Information Protocol (RIP). IBM Networking OS software supports RIP
version 1 (RIPv1) and RIP version 2 (RIPv2) for exchanging TCP/IPv4 route
information with other routers.
Note:
IBM N/OS 6.8 does not support IPv6 for RIP.
Distance Vector Protocol
RIP is known as a distance vector protocol. The vector is the network number
and next hop, and the distance is the metric associated with the network number.
RIP identifies network reachability based on metric, and metric is defined as hop
count. One hop is considered to be the distance from one switch to the next, which
typically is 1.
When a switch receives a routing update that contains a new or changed destination
network entry, the switch adds 1 to the metric value indicated in the update and
enters the network in the routing table. The IPv4 address of the sender is used as
the next hop.
Stability
RIP includes a number of other stability features that are common to many routing
protocols. For example, RIP implements the split horizon and hold-down
mechanisms to prevent incorrect routing information from being propagated.
RIP prevents routing loops from continuing indefinitely by implementing a limit on
the number of hops allowed in a path from the source to a destination. The
maximum number of hops in a path is 15. The network destination network is
considered unreachable if increasing the metric value by 1 causes the metric to be
16 (that is infinity). This limits the maximum diameter of a RIP network to less than
16 hops.
RIP is often used in stub networks and in small autonomous systems that do not
have many redundant paths.
Routing Updates
RIP sends routing-update messages at regular intervals and when the network
topology changes. Each router “advertises” routing information by sending a routing
information update every 30 seconds. If a router doesn’t receive an update from
another router for 180 seconds, those routes provided by that router are declared
invalid. The routes are removed from the routing table, but they remain in the RIP
routes table. After another 120 seconds without receiving an update for those
routes, the routes are removed from respective regular updates.
When a router receives a routing update that includes changes to an entry, it
updates its routing table to reflect the new route. The metric value for the path is
increased by 1, and the sender is indicated as the next hop. RIP routers maintain
only the best route (the route with the lowest metric value) to a destination.
For more information, see the Configuration section, Routing Information Protocol
Configuration in the
IBM Networking OS Command Reference
.
Summary of Contents for RackSwitch G8000
Page 1: ...RackSwitch G8000 Application Guide...
Page 2: ......
Page 3: ...RackSwitch G8000 Application Guide...
Page 16: ...16 RackSwitch G8000 Application Guide...
Page 22: ...20 RackSwitch G8000 Application Guide...
Page 23: ...Copyright IBM Corp 2011 21 Part 1 Getting Started...
Page 24: ...22 RackSwitch G8000 Application Guide...
Page 54: ...52 RackSwitch G8000 Application Guide...
Page 55: ...Copyright IBM Corp 2011 53 Part 2 Securing the Switch...
Page 56: ...54 RackSwitch G8000 Application Guide...
Page 92: ...90 RackSwitch G8000 Application Guide...
Page 94: ...92 RackSwitch G8000 Application Guide...
Page 144: ...142 RackSwitch G8000 Application Guide...
Page 145: ...Copyright IBM Corp 2011 143 Part 4 Advanced Switch ing Features...
Page 146: ...144 RackSwitch G8000 Application Guide...
Page 148: ...146 RackSwitch G8000 Application Guide...
Page 182: ...180 RackSwitch G8000 Application Guide...
Page 184: ...182 RackSwitch G8000 Application Guide...
Page 212: ...210 RackSwitch G8000 Application Guide...
Page 258: ...256 RackSwitch G8000 Application Guide...
Page 286: ...284 RackSwitch G8000 Application Guide...
Page 294: ...292 RackSwitch G8000 Application Guide...
Page 298: ...296 RackSwitch G8000 Application Guide...
Page 310: ...308 RackSwitch G8000 Application Guide...
Page 311: ...Copyright IBM Corp 2011 309 Part 7 Network Management...
Page 312: ...310 RackSwitch G8000 Application Guide...
Page 320: ...318 RackSwitch G8000 Application Guide...
Page 332: ...330 RackSwitch G8000 Application Guide...
Page 334: ...332 RackSwitch G8000 Application Guide...
Page 345: ...Copyright IBM Corp 2011 343 Part 9 Appendices...
Page 346: ...344 RackSwitch G8000 Application Guide...
Page 357: ...Copyright IBM Corp 2011 Appendix C Notices 355 Taiwan Class A compliance statement...