Network Discovery

In this article we will discuss Network Discovery, will make brief discussion on Network Discovery, In last article we discuss about Cold Start – Distance Vector.

After initial boot up and discovery, the routing table is updated with all directly connected networks and the interfaces those networks reside on.

If a routing protocol is configured, the next step is for the router to begin exchanging routing updates to learn about any remote routes.

The router sends an update packet out all interfaces that are enabled on the router. The update contains the information in the routing table, which currently is all directly connected networks.

At the same time, the router also receives and processes similar updates from other connected routers. Upon receiving an update, the router checks it for new network information. Any networks that are not currently listed in the routing table are added.

Refer to the figure for a topology setup between three routers, R1, R2, and R3 with RIPv2 enabled. Based on this topology, below is a listing of the different updates that R1, R2, and R3 send and receive during initial convergence.

R1:

  • Sends an update about network 10.1.0.0 out the Serial0/0/0 interface
  • Sends an update about network 10.2.0.0 out the FastEthernet0/0 interface
  • Receives an update from R2 about network 10.3.0.0 and increments the hop count by 1
  • Stores network 10.3.0.0 in the routing table with a metric of 1

R2:

  • Sends an update about network 10.3.0.0 out the Serial 0/0/0 interface
  • Sends an update about network 10.2.0.0 out the Serial 0/0/1 interface
  • Receives an update from R1 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 1
  • Receives an update from R3 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 1

R3:

  • Sends an update about network 10.4.0.0 out the Serial 0/0/1 interface
  • Sends an update about network 10.3.0.0 out the FastEthernet0/0
  • Receives an update from R2 about network 10.2.0.0 and increments the hop count by 1
  • Stores network 10.2.0.0 in the routing table with a metric of 1

After this first round of update exchanges, each router knows about the connected networks of their directly connected neighbors. However, did you notice that R1 does not yet know about 10.4.0.0 and that R3 does not yet know about 10.1.0.0? Full knowledge and a converged network do not take place until there is another exchange of routing information.

Add a Comment

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