Periodic Vs Triggered Update
Duration: 4 min
This video lesson is available to enrolled students.
AI Summary
An AI-generated summary of this video lecture.
The lecture focuses on the operational mechanics of Distance Vector Routing protocols, specifically addressing the timing and triggers for exchanging routing information between nodes. The instructor explains that a node sends its partial routing table, which contains only two columns (destination and distance), to all its immediate neighbors. This transmission occurs in two distinct scenarios: periodically and when a change is detected. The first scenario is the "Periodic Update," where a node sends its routing table at regular intervals, typically every 30 seconds, though the exact period depends on the specific protocol being used. The second scenario is the "Triggered Update," which is an immediate response to a change in the routing table. The instructor elaborates on the conditions that trigger this update, such as receiving a table from a neighbor that causes a change in the local table or detecting a failure in a neighboring link, which results in the distance changing to infinity. Throughout the explanation, the instructor draws a diagram on the slide to visualize a central node connected to its neighbors and a destination node, illustrating the flow of information and distance metrics.
Chapters
0:00 – 2:00 00:00-02:00
The instructor begins by posing the question of when a node sends its partial routing table to its immediate neighbors. He clarifies that the table is sent both periodically and whenever there is a change in the table. He then defines "Periodic Update," stating that a node sends its routing table, normally every 30 seconds, in a periodic update. He emphasizes that the period depends on the protocol that is using distance vector routing. To illustrate the concept, he starts drawing a diagram on the slide, sketching a central node with arrows pointing outwards to represent its neighbors. He explains that the table sent is a partial routing table containing only two columns.
2:00 – 4:29 02:00-04:29
The instructor moves on to define "Triggered Update," explaining that a node sends its two-column routing table to its neighbors anytime there is a change in its routing table. He lists the specific changes that can result in this update. First, a node receives a table from a neighbor, resulting in changes in its own table after updating. Second, a node detects some failure in the neighboring links which results in a distance change to infinity. As he explains these points, he continues to draw on the diagram, adding a circle to represent a destination node and writing "D" and "100" near a link to illustrate distance and cost metrics. He uses hand gestures to emphasize the flow of information and the concept of detecting failures.
The lecture provides a clear distinction between periodic and triggered updates in distance vector routing. Periodic updates maintain network stability through regular, scheduled exchanges of routing information, typically every 30 seconds, ensuring that all nodes have a baseline view of the network. In contrast, triggered updates offer a mechanism for rapid convergence by immediately propagating changes, such as link failures or metric adjustments, to neighbors. This dual approach ensures that the network remains consistent while also reacting quickly to topology changes, preventing routing loops and ensuring efficient data transmission across the network.