Network Discovery with Split Horizon

10.1.1.0/24
.1

RTA

10.1.2.0/24
.1

.2

s0

s0

e0

RTB

10.1.3.0/24
.1
s1

.2
s0

RTC

10.1.4.0/24
.1

.2

s1

s0

RTD

.1

10.1.5.0/24

e0

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0

Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
-----------------------10.1.2.0/24 1 10.1.1.1

Routing Update
Next-hop
Net.
Hops Address
10.1.2.0/24 1 10.1.3.1
-----------------------10.1.3.0/24 1 10.1.2.2

Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.4.1
-----------------------10.1.4.0/24 1 10.1.3.2

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0
10.1.3.0/24 1 10.1.2.2

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1
10.1.1.0/24 1 10.1.2.1
10.1.4.0/24 1 10.1.3.2

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1
10.1.2.0/24 1 10.1.3.1
10.1.5.0/24 1 10.1.4.2

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0
10.1.3.0/24 1 10.1.4.1

Routing Update
Next-hop
Net.
Hops Address
10.1.4.0/24 1 10.1.4.2
-----------------------10.1.5.0/24 1 10.1.4.2

Answer Do your routing tables look like these?

Now What do the next round of routing updates look like? Show the
routes which are sent (propagated) and those that are not sent
because of split horizon.

Network Discovery with Split Horizon

10.1.1.0/24
.1
e0

RTA

10.1.2.0/24
.1

.2

s0

s0

RTB

10.1.3.0/24
.1
s1

.2
s0

RTC

10.1.4.0/24
.1

.2

s1

s0

RTD

.1

10.1.5.0/24

e0

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0
10.1.3.0/24 1 10.1.2.2

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1
10.1.1.0/24 1 10.1.2.1
10.1.4.0/24 1 10.1.3.2

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1
10.1.2.0/24 1 10.1.3.1
10.1.5.0/24 1 10.1.4.2

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0
10.1.3.0/24 1 10.1.4.1

Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.4.1
10.1.2.0/24 2 10.1.4.1
-----------------------10.1.4.0/24 1 10.1.3.2
10.1.5.0/24 2 10.1.3.2

Routing Update
Next-hop
Net.
Hops Address
X10.1.4.0/24 1 10.1.4.2
X10.1.3.0/24 2 10.1.4.2
-----------------------10.1.5.0/24 1 10.1.4.2

Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
-----------------------10.1.2.0/24 1 10.1.1.1 X
10.1.3.0/24 2 10.1.1.1 X

Routing Update
Next-hop
Net.
Hops Address
10.1.2.0/24 1 10.1.3.1
10.1.1.0/24 2 10.1.3.1
-----------------------10.1.3.0/24 1 10.1.2.2
10.1.4.0/24 2 10.1.2.2

Answer Do your routing updates look like these?

Again, omission of the red/blue arrow means split horizon is in affect.
For example, RTB is not sending the route 10.1.1.0/24 to RTA to tell RTA it can
get to 10.1.1./24 in 2 hops via RTB. - This would make sense!
Split horizon - router never sends out information on an interface that it learned
from that interface

Now What do the routing tables look like?

Network Discovery with Split Horizon

10.1.1.0/24
.1

RTA

e0

10.1.2.0/24
.1

.2

s0

s0

RTB

10.1.3.0/24
.1
s1

.2
s0

RTC

10.1.4.0/24
.1

.2

s1

s0

RTD

.1

10.1.5.0/24

e0

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0
10.1.3.0/24 1 10.1.2.2

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1
10.1.1.0/24 1 10.1.2.1
10.1.4.0/24 1 10.1.3.2

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1
10.1.2.0/24 1 10.1.3.1
10.1.5.0/24 1 10.1.4.2

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0
10.1.3.0/24 1 10.1.4.1

Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.4.1
10.1.2.0/24 2 10.1.4.1
-----------------------10.1.4.0/24 1 10.1.3.2
10.1.5.0/24 2 10.1.3.2

Routing Update
Next-hop
Net.
Hops Address
X10.1.4.0/24 1 10.1.4.2
X10.1.3.0/24 2 10.1.4.2
-----------------------10.1.5.0/24 1 10.1.4.2

Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
-----------------------10.1.2.0/24 1 10.1.1.1 X
10.1.3.0/24 2 10.1.1.1 X

Routing Update
Next-hop
Net.
Hops Address
10.1.2.0/24 1 10.1.3.1
10.1.1.0/24 2 10.1.3.1
-----------------------10.1.3.0/24 1 10.1.2.2
10.1.4.0/24 2 10.1.2.2

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0
10.1.3.0/24 1 10.1.2.2
10.1.4.0/24 2 10.1.2.2

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1
10.1.1.0/24 1 10.1.2.1
10.1.4.0/24 1 10.1.3.2
10.1.5.0/24 2 10.1.3.2

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1
10.1.2.0/24 1 10.1.3.1
10.1.5.0/24 1 10.1.4.2
10.1.1.0/24 2 10.1.3.1

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0
10.1.3.0/24 1 10.1.4.1
10.1.2.0/24 2 10.1.4.1

Answer Do your routing tables look like these? Convergence?

Note: Newest routing table entries are at the bottom of the routing tables in these
diagrams.

Now What do the next round of routing updates look like and the routing
tables? (Well finish this up )

Network Discovery with Split Horizon

10.1.1.0/24
.1
e0

RTA

10.1.2.0/24

RTB

.1

.2

s0

s0

10.1.3.0/24
.1
s1

.2
s0

RTC

10.1.4.0/24
.1

.2

s1

s0

RTD

.1

10.1.5.0/24

e0

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0
10.1.3.0/24 1 10.1.2.2
10.1.4.0/24 2 10.1.2.2

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1
10.1.1.0/24 1 10.1.2.1
10.1.4.0/24 1 10.1.3.2
10.1.5.0/24 2 10.1.3.2

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1
10.1.2.0/24 1 10.1.3.1
10.1.5.0/24 1 10.1.4.2
10.1.1.0/24 2 10.1.3.1

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0
10.1.3.0/24 1 10.1.4.1
10.1.2.0/24 2 10.1.4.1

Routing Update
Next-hop
Net.
Hops Address
10.1.2.0/24 1 10.1.3.1
10.1.1.0/24 2 10.1.3.1
-----------------------10.1.3.0/24 1 10.1.2.2
10.1.4.0/24 2 10.1.2.2
10.1.5.0/24 3 10.1.2.2

Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.4.1
10.1.2.0/24 2 10.1.4.1
10.1.1.0/24 3 10.1.4.1
-----------------------10.1.4.0/24 1 10.1.3.2
10.1.5.0/24 2 10.1.3.2

Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
-----------------------10.1.2.0/24 1 10.1.1.1 X
10.1.3.0/24 2 10.1.1.1 X
10.1.4.0/24 3 10.1.1.1 X

Routing Update
Next-hop
Net.
Hops Address
X10.1.4.0/24 1 10.1.4.2
X10.1.3.0/24 2 10.1.4.2
X10.1.2.0/24 3 10.1.4.2
-----------------------10.1.5.0/24 1 10.1.4.2

Routing Table

Routing Table

Routing Table

Routing Table

Net.
Hops Ex-Int
10.1.1.0/24 0
e0
10.1.2.0/24 0
s0
10.1.3.0/24 1 10.1.2.2
10.1.4.0/24 2 10.1.2.2
10.1.5.0/24 3 10.1.2.2

Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
s1
10.1.1.0/24 1 10.1.2.1
10.1.4.0/24 1 10.1.3.2
10.1.5.0/24 2 10.1.3.2

Net.
Hops Ex-Int
10.1.3.0/24 0
s0
10.1.4.0/24 0
s1
10.1.2.0/24 1 10.1.3.1
10.1.5.0/24 1 10.1.4.2
10.1.1.0/24 2 10.1.3.1

Net.
Hops Ex-Int
10.1.4.0/24 0
s0
10.1.5.0/24 0
e0
10.1.3.0/24 1 10.1.4.1
10.1.2.0/24 2 10.1.4.1
10.1.1.0/24 3 10.1.4.1

Answer Do your routing tables look like these?

Convergence? YES!

Good Job!

FAQs Network Discovery

Q: How often does initial network discovery happen?
A: Only when the network first comes up.
Q: Do routers share routing table information after network discovery?
A: Yes, distance-vector routing protocols share their entire routing tables
periodically (with or without split horizon enabled). Distance vector
routing protocols on Cisco routers by default use split horizon with
poison reverse (discussed in the next section). Depending upon the
distance-vector routing protocol, the frequency of the updates will
happen for RIP every 30 seconds, IPX RIP every 60 seconds, and IGRP
every 90 seconds.

Q: What happens when there is a change in the topology, link goes down,
new network is added, new router, is added, etc.?
A: Lets take a look.