Exchanging the Routing Information

In this article we will discuss Exchanging the Routing Information, will make brief discussion on Exchanging the Routing Information, In last article we discuss about Network Discovery.

At this point the routers have knowledge about their own directly connected networks and about the connected networks of their immediate neighbors.

Continuing the journey toward convergence, the routers exchange the next round of periodic updates. Each router again checks the updates for new information.

Refer to the figure for a topology setup between three routers, R1, R2, and R3. After initial discovery is complete, each router continues the convergence process by sending and receiving the following updates.

R1:

  • Sends an update about network 10.1.0.0 out the Serial 0/0/0 interface
  • Sends an update about networks 10.2.0.0 and 10.3.0.0 out the FastEthernet0/0 interface
  • Receives an update from R2 about network 10.4.0.0 and increments the hop count by 1
  • Stores network 10.4.0.0 in the routing table with a metric of 2
  • Same update from R2 contains information about network 10.3.0.0 with a metric of 1. There is no change; therefore, the routing information remains the same

R2:

  • Sends an update about networks 10.3.0.0 and 10.4.0.0 out of Serial 0/0/0 interface
  • Sends an update about networks 10.1.0.0 and 10.2.0.0 out of Serial 0/0/1 interface
  • Receives an update from R1 about network 10.1.0.0. There is no change; therefore, the routing information remains the same
  • Receives an update from R3 about network 10.4.0.0. There is no change; therefore, the routing information remains the same

R3:

  • Sends an update about network 10.4.0.0 out the Serial 0/0/1 interface
  • Sends an update about networks 10.2.0.0 and 10.3.0.0 out the FastEthernet0/0 interface
  • Receives an update from R2 about network 10.1.0.0 and increments the hop count by 1
  • Stores network 10.1.0.0 in the routing table with a metric of 2
  • Same update from R2 contains information about network 10.2.0.0 with a metric of 1. There is no change; therefore, the routing information remains the same

Distance vector routing protocols typically implement a routing loop prevention technique known as split horizon. Split horizon prevents information from being sent out the same interface from which it was received. For example, R2 does not send an update containing the network 10.1.0.0 out of Serial 0/0/0, because R2 learned about network 10.1.0.0 through Serial 0/0/0.

After routers within a network have converged, the router can then use the information within the routing table to determine the best path to reach a destination. Different routing protocols have different ways of calculating the best path.

Add a Comment

Your email address will not be published. Required fields are marked *