Triggered Updates Routers do not have to wait for the periodic update to hear about changes in the network

k topology. Improvements to the distance-vector algorithm is typically made in distance-vector routing protocols, like RIP, to include triggered updates. Even with triggered updates, large distance vector networks can suffer from long convergence times in some situations.

Triggered updates: (continued) Triggered updates are sent whenever a router sees a topology change or a change in routing information (from another router). The router does not have to wait for the period timer, but can send them immediately. Triggered updates do not need to include the entire routing table but only the modified route(s).

Triggered updates: (continued) Triggered updates must still be sent to adjacent routers, from router to router, like other routing updates. Most distance-vector routing protocols limit the frequency of triggered updates so that a flapping link does not put an unnecessary load on the network. (RIP: random 1 to 5 seconds) Typically, triggered updates can be triggered by:
Interface transition to the up or down state A route has entered or exited an unreachable (down) state (later) A new route is installed in the routing table

Routing Loops

Distance vector routing protocols are simple in their implementaton and configuration, but this comes at a price. Pure distance vector routing protocols suffer from possible routing loops. Routing loops can cause major network problems, from packets getting lost (blackholed) in your network, to bringing down your entire network. Several remedies to have been added to distance-vector algorithms to help prevent routing loops including: Split horizon Hold-down timers Defining a maximum metric

Routing Loops (continued)

What can cause routing loops? Routing loops can occur when there are: Incorrect or inconsistent routing updates due to slow convergence after a topology change. (Example coming up next.) Incorrect or incomplete routing information (see presentation on Discard Routes) Static routes incorrectly configured with an intermediate address which does not become resolved in the routing table. (see presentation on Static Routes Additional Information)