RIP Dynamic Routing
Routing Information Protocol (RIP) is a protocol which allows routers within a network to exchange routes of which they are aware approximately every 30 seconds. Through this process, each router becomes adds routes in the network to its routing table.
Each router to router link is called a 'hop' and routes of up to 15 hops are created in the routing tables. When more than one route to a destination exists, the route with the lowest metric (number of hops) is added to the routing table.
When an existing route becomes unavailable, after 5 minutes it is marked as requiring 'infinite' (16 hops). It is then advertised as such to other routers for the next few updates before being removed from the routing table. The IP Office also uses 'split horizon' and 'poison reverse'.
RIP is a simple method for automatic route sharing and updating within small homogeneous networks. It allows alternate routes to be advertised when an existing route fails. Within a large network the exchange of routing information every 30 seconds can create excessive traffic. In addition the routing table held by each IP Office is limited to 100 routes (including static and internal routes).
RIP is supported with IP Office system's from Level 2.0 upwards. The normal default is for RIP to be disabled. It can be enabled on LAN1, LAN2 and individual services.
-
Listen Only (Passive):
The IP Office listens to RIP1 and RIP2 messages and uses these to update its routing table. However the IP Office does not respond.
-
RIP1:
The IP Office listens to RIP1 and RIP2 messages. It advertises its own routes in a RIP1 sub-network broadcast.
-
RIP2 Broadcast (RIP1 Compatibility):
The IP Office listens to RIP1 and RIP2 messages. It advertises its own routes in a RIP2 sub-network broadcast. This method is compatible with RIP1 routers.
-
RIP2 Multicast:
The IP Office listens to RIP1 and RIP2 messages. It advertises its own routes to the RIP2 multicast address (249.0.0.0). This method is not compatible with RIP1 routers.
Broadcast and multicast routes (those with addresses such as 255.255.255.255 and 224.0.0.0) are not included in RIP broadcasts. Static routes (those in the IP Route table) take precedence over a RIP route when the two routes have the same metric.
|
