Escolar Documentos
Profissional Documentos
Cultura Documentos
Justinian Anatory
Overview
FAQs
FAQs Network Discovery
Q: How often does initial network discovery happen?
A: Only when the network comes 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.
Triggered Updates
Routers do not have to wait for the periodic update to hear about
changes in the network 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.
Department of Computer and systems Engineering
Triggered Updates
Triggered Updates
Routing Loops
Distance vector routing protocols are simple in their implementation 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
Department of Computer and systems Engineering
Network 1 Fails
Router E sends an update to Router A.
Router A stops routing packets to network 1.
But Routers B, C, and D continue to do so because they have not yet been
informed about the failure.
Router A sends out its update.
Routers B and D stop routing to network1, (via Router A).
However, Router C is still not updated.
To router C, network 1 is still reachable via router B.
Department of Computer and systems Engineering
Defining a Maximum
10
Split Horizon
The effect of split horizon is that a router will send out different routing
messages on different interfaces. In effect a router never sends out
information on an interface that it learned from that interface.
11
Split Horizon
12
RTA
10.1.2.0/24
.1
.2
s0
s0
RTB
10.1.3.0/24
.1
e0
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
e0
Initial
routing
tables
13
10.1.1.0/24
.1
10.1.2.0/24
RTA
.1
.2
s0
s0
e0
RTB
10.1.3.0/24
.1
e0
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
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 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
Routing Update
Next-hop
Net.
Hops Address
10.1.2.0/24 1 10.1.2.2
10.1.3.0/24 1 10.1.2.2
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
Initial
routing
tables
10.1.2.0/24
network is
included because
split horizon has
been disabled
New
routing
tables
14
10.1.1.0/24
.1
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
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
10.1.3.0/24 2 10.1.1.1
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
Previous
routing
tables
Networks in red
were included
because split
horizon has been
disabled
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 2
10.1.2.1
10.1.1.0/24 1
10.1.2.1
New
routing
tables
15
10.1.1.0/24
.1
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
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
10.1.3.0/24 2 10.1.1.1
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
Previous
routing
tables
Networks in red
were included
because split
horizon has been
disabled
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 2
10.1.2.1
10.1.1.0/24 1
10.1.2.1
New
routing
tables
16
10.1.1.0/24
.1
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 2
10.1.2.1
10.1.1.0/24 1
10.1.2.1
Routing Update
Next-hop
Net.
Hops Address
10.1.2.0/24 1 10.1.2.2
10.1.3.0/24 3 10.1.2.2
10.1.1.0/24 2 10.1.2.2
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 3
10.1.2.2
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 2
10.1.2.1
10.1.1.0/24 1
10.1.2.1
Previous
routing
tables
Networks in red
were included
because split
horizon has been
disabled
New
routing
tables
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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 16 10.1.2.2
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 16 10.1.2.1
10.1.1.0/24 1
10.1.2.1
18
10.1.1.0/24
.1
Split
Horizon
Enabled
10.1.2.0/24
RTA
.1
.2
s0
s0
e0
RTB
10.1.3.0/24
.1
e0
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
e0
Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
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
Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
Previous
routing
tables
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.2.2
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
New
routing
tables
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.2.2
19
10.1.1.0/24
.1
RTA
10.1.2.0/24
.1
.2
s0
s0
e0
RTB
10.1.3.0/24
.1
e0
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
e0
Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
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
Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1 10.1.1.1
Previous
routing
tables
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.2.2
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
New
routing
tables
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1 10.1.2.2
20
10.1.1.0/24
.1
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops
Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 (down) e0
10.1.1.0/24 1
10.1.2.1
Previous
routing
tables
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 16 10.1.2.2
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 (down) 10.1.2.2
Routing Table
Net.
Hops
Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 (down) e0
10.1.1.0/24 1
10.1.2.1
New
routing
tables
21
10.1.1.0/24
.1
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops
Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 (down) e0
10.1.1.0/24 1
10.1.2.1
Previous
routing
tables
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 16 10.1.2.2
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 (down) 10.1.2.2
Routing Table
Net.
Hops
Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 (down) e0
10.1.1.0/24 1
10.1.2.1
New
routing
tables
22
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1
10.1.1.1
10.1.2.0/24 16 10.1.2.1
10.1.3.0/24 16 10.1.2.1
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1
10.1.2.2
10.1.2.0/24 16 10.1.2.2
10.1.1.0/24 16 10.1.2.2
Poisoned
routes in red.
Routing tables
remain the
same.
Many vendor implementations of distance vector routing protocols like Ciscos RIP and
IGRP apply a special kind of split horizon, called split horizon with poison reverse.
Split horizon with poison reverse means that, instead of not advertising routes to the
source, routes are advertised back to the source with a metric of 16, which will make the
source router ignore the route. It is perceived that explicitly telling a router to ignore a
route is better than not telling it about the route in the first place. (Lewis, Cisco TCP/IP
Routing)
One drawback is that routing update packet sizes will be increased when using Poison
Reverse, since they now include these routes.
Department of Computer and systems Engineering
23
RTA
e0
10.1.2.0/24
.1
.2
s0
s0
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
Routing Update
Next-hop
Net.
Hops Address
10.1.1.0/24 1
10.1.1.1
10.1.2.0/24 16 10.1.2.1
10.1.3.0/24 16 10.1.2.1
RTB
10.1.3.0/24
.1
e0
Routing Table
Net.
Hops Ex-Int
10.1.2.0/24 0
s0
10.1.3.0/24 0
e0
10.1.1.0/24 1
10.1.2.1
Routing Update
Next-hop
Net.
Hops Address
10.1.3.0/24 1
10.1.2.2
10.1.2.0/24 16 10.1.2.2
10.1.1.0/24 16 10.1.2.2
Poisoned
routes in red.
24
Route poisoning
25
26
Curriculum
A count to infinity problem can be avoided by using holddown timers.
When a router receives an update from a neighbor indicating that a
previously accessible network is now inaccessible, the router marks
the route as inaccessible and starts a hold-down timer.
27
28
29
If at any time before the hold-down timer expires an update arrives from a
different neighboring router with a poorer metric than originally recorded for the
network the update is ignored and the hold-down timer continues.
Ignoring an update with a poorer metric when a hold-down is in effect allows
more time for the knowledge of a disruptive change to propagate through the
entire network.
30
31
Packet forwarding
Even though routing tables remain constant and routers do not accept
potentially bad updates, an interesting question is whether or not routers
should continue use the existing routes that are in holddown state for
forwarding packets?
In practice, routes in the holddown state are used for packet forwarding. In
the worst case, packets are forwarded toward the router that was previously
connected to the destination network, which drops them. In the best case, they
are forwarded along a potentially suboptimal but valid path. (Zinin, Cisco IP
Routing)
Department of Computer and systems Engineering
32
15 16
4-bit
Header
Length
8-bit Type Of
Service
(TOS)
16-bit Identification
8 bit Time To Live
TTL
31
8-bit Protocol
15 16
4-bit
Header
Length
8-bit Type Of
Service
(TOS)
16-bit Identification
8 bit Time To Live
TTL
31
8-bit Protocol
When a packet is first generated a value is entered into the TTL field.
Originally, the TTL field was the number of seconds, but this was difficult to implement
and rarely supported.
Now, the TTL is now set to a specific value which is then decremented by each router.
Department of Computer and systems Engineering
15 16
4-bit
Header
Length
8-bit Type Of
Service
(TOS)
16-bit Identification
8 bit Time To Live
TTL
31
8-bit Protocol
If the router decrements the TTL field to 0, it will then drop the packet (unless the packet
is destined specifically for the router,Data
I.e. ping, telnet, etc.).
Common operating system TTL values are:
UNIX: 255
Linux: 64 or 255 depending upon vendor and version
Microsoft Windows 95: 32
Other Microsoft Windows operating systems: 128
http://www.switch.ch/docs/ttl_default.html
TTL Overview - Disclaimer:
The following list is a best effort overview of some widely used TCP/IP stacks. The
information was provided by vendors and many helpful system administrators. We would
like to thank all these contributors for their precious help ! SWITCH cannot, however,
take any responsibility that the provided information is correct. Furthermore, SWITCH
cannot be made liable for any damage that may arise by the use of this information.
+--------------------+-------+---------+---------+
| OS Version
|"safe" | tcp_ttl | udp_ttl |
+--------------------+-------+---------+---------+
AIX
n
60
30
DEC Pathworks V5
n
30
30
FreeBSD 2.1R
y
64
64
HP/UX
9.0x
n
30
30
HP/UX
10.01
y
64
64
Irix 5.3
y
60
60
Irix 6.x
y
60
60
Linux
y
64
64
MacOS/MacTCP 2.0.x
y
60
60
OS/2 TCP/IP 3.0
y
64
64
OSF/1 V3.2A
n
60
30
Solaris 2.x
y
255
255
SunOS 4.1.3/4.1.4
y
60
60
Ultrix V4.1/V4.2A
n
60
30
VMS/Multinet
y
64
64
VMS/TCPware
y
60
64
VMS/Wollongong 1.1.1.1
n
128
30
VMS/UCX (latest rel.)
y
128
128
MS WfW
n
32
32
MS Windows 95
n
32
32
MS Windows NT 3.51
n
32
32
MS Windows NT 4.0
y
128
128
Department of Computer and systems Engineering
15 16
4-bit
Header
Length
8-bit Type Of
Service
(TOS)
16-bit Identification
8 bit Time To Live
TTL
31
8-bit Protocol
The idea behind the TTL field is that IP packets can not travel around the
Internet forever, from router to router.
Eventually, the packets TTL which reach 0 and be dropped by the router, even
if there is a routing loop somewhere in the network.
Configuring RIP
Configuring RIP
Triggered Extensions
10
Triggered Extensions
interface serial 0
ip rip triggered
11
Triggered Extensions
interface serial 0
ip rip triggered
12
IP Packet
Header
UDP
Segment
Header
RIP
Message
RIP Message
Data Link Frame
IP Source Address
Hops (metric)
Department of Computer and systems Engineering
13
Data Link
Frame
Header
IP Packet
Header
UDP
Segment
Header
RIP
Message
0
7 8
15 16
23 24
Command = 1 or 2
Version = 1
Must be zero
Address family identifier (2 = IP)
Must be zero
IP Address (Network Address)
Must be zero
Must be zero
Metric (Hops)
31
14
All the extensions to the original protocol are carried in the unused
fields.
The Address Family Identifier (AFI) field is set to two for IP. The only
exception is a request for a full routing table of a router or host, in
which case it will be set to zero.
15
The Route Tag field provides a way to differentiate between internal and
external routes.
External routes are those that have been redistributed into the RIP v2.
The Next Hop field contains the IP address of the next hop listed in the IP
Address field.
Metric indicates how many internetwork hops, between 1 and 15 for a valid
route, or 16 for an unreachable route.
16
Configuring RIP
RIP must be enabled and the networks specified. The remaining tasks are
optional. Among these optional tasks are:
Applying offsets to routing metrics (Not commonly used)
Adjusting timers
Specifying a RIP version (RIPv1 or RIPv2)
Enabling RIP authentication
Configuring route summarization on an interface
Verifying IP route summarization
Disabling automatic route summarization (RIPv2)
Running IGRP and RIP concurrently (Usually, redistributing, not concurrently.)
Disabling the validation of source IP addresses
Enabling or disabling split horizon
Connecting RIP to a WAN
Department of Computer and systems Engineering
17
ip classless command
R
C
C
C
S
S
S*
Parent Route
Created automatically whenever there is a route with a mask greater
than the classful mask.
For non-VLSM routes, contains the mask of the child routes.
Child Routes
Routes with masks greater than the default classful mask.
Department of Computer and systems Engineering
Lookup what?
RouterB#show ip route
R
C
C
C
S
S
S*
R
C
C
C
S
S
S*
DA = 172.16.4.1
Router(config)# no ip classless
With classful routing behavior, if the child routes are checked but
there are no matches, the routing lookup process ends and the Packet
is dropped. (The packets get in, but they cant get out!)
Supernet and default routes are not checked.
Default with IOS 11.2 and prior
Department of Computer and systems Engineering
R
C
C
C
S
S
S*
DA = 172.16.4.1
Router(config)# ip classless
With classless routing behavior, if the child routes are checked but
there are no matches, the routing lookup process continues with other
routes in the routing table, including supernet and default routes.
8 bits of 172.0.0.0/8 do match, so this route is used!
Default with IOS 11.3 and later
Department of Computer and systems Engineering
23
24
25
For RIP and IGRP, the passive interface command stops the router from
sending updates to a particular neighbor, but the router continues to
listen and use routing updates from that neighbor.
Also used when there are no routers on that interface, such as stub
LANs.
Router(config-router)# passive-interface interface
26
27
28
interface fastethernet0/1
ip address 172.25.150.193 255.255.255.240
ip rip send version 1 2
Interface FastEthernet0/0 is
configured to send and receive
RIP v1 updates.
FastEthernet0/1 is configured
to send both version 1 and 2
updates.
FastEthernet0/2 has no special
configuration and therefore
sends and receives version 2
by default.
interface fastethernet0/2
ip address 172.25.150.225 225.255.255.240
router rip
version 2
network 172.25.0.0
network 192.168.50.0
29
30
31
32
33
34
35
Fast Switching
Per Destination Load Balancing
Router(config-if)# ip route-cache
ping 10.0.0.2
ping 10.0.0.1
36
Fast Switching
Per Destination Load Balancing
Router(config-if)# ip route-cache
ping 10.0.0.2
ping 10.0.0.1
Fast Switching
1. Router switches first packet to a particular destination, a routing table lookup
is performed and an exit interface is selected.
2. The necessary data-link information to frame the packet for the selected
interface is retrieved including any ARP cache information.
3. The route and data-link information is stored in fast switching cache.
4. The router uses the cache to look up subsequent packets.
5. All other packets to the same destination are immediately switched out the
same interface without the router performing another routing table lookup,
including any recursive lookups. (Also no ARP cache lookup).
Department of Computer and systems Engineering
37
Process Switching
Per Packet Load Balancing
Router(config-if)#no ip route-cache
ping 10.0.0.2
ping 10.0.0.1
Process Switching
Given equal cost paths, per packet load sharing means that one packet to a
destination is sent over one link, the next packet to the same destination is
sent over the next link, and so on.
If the paths are unequal cost, the load balancing may be one packet over the
higher-cost link for every three packets over the lower-cost link, or similar
ratio.
With process switching, for every packet, the router performs a route table
lookup and selects an interface, and looks up the data-link information.
To enable distributed or process switching:
Router(config-if)# no ip route-cache
Department of Computer and systems Engineering
38
Which one?
Fast Switching
ping 10.0.0.2
ping 10.0.0.1
Router(config-if)# ip route-cache
Process Switching
ping 10.0.0.2
ping 10.0.0.1
Router(config-if)#no ip route-cache
39
d=10.0.0.1 (Serial0/0),
d=10.0.0.1 (Serial0/1),
d=10.0.0.1 (Serial0/0),
d=10.0.0.1 (Serial0/1),
40
41
42
172.16.0.0/16
router rip
network 192.168.14.0
ip route 172.16.0.0 255.255.0.0 bri0/1 130
Floating static routes are static routes which are used as backup
routes.
They are only injected into the routing table when a route with a lower
administrative distance (dynamic or another static route) goes down.
Should the route with the lower administrative distance come back up
then the floating static route is removed from the routing table.
43
Redistribute Static
172.16.0.0/16
RIP
RouterA
ip route 172.16.0.0 255.255.0.0 eth 0
Router rip
redistribute static
network .
44
45
46
Baypointe#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Baypointe(config)#router rip
Baypointe(config-router)#network 192.168.4.0
Baypointe(config-router)#network 192.168.5.0
SanJose1#configure terminal
Enter configuration commands, one per line.
SanJose1(config)#router rip
SanJose1(config-router)#network 192.168.2.0
SanJose1(config-router)#network 192.168.3.0
SanJose1(config-router)#network 192.168.4.0
Department of Computer and systems Engineering
47
48
49
50
SanJose2
01:30:45: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.1.1)
01:30:45:
network 192.168.4.0, metric 2
01:30:45:
network 192.168.5.0, metric 3
01:30:45:
network 192.168.2.0, metric 1
01:30:45:
network 192.168.3.0, metric 2
01:30:45: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.2.1)
01:30:45:
network 192.168.1.0, metric 1
SanJose2#
01:30:50: RIP: received v1 update from 192.168.2.2 on Serial0
01:30:50:
192.168.4.0 in 1 hops
01:30:50:
192.168.5.0 in 2 hops
01:30:50:
192.168.3.0 in 1 hops
SanJose2#
SanJose2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
Gateway of last resort is not set
R
192.168.4.0/24
R
192.168.5.0/24
C
192.168.1.0/24
C
192.168.2.0/24
R
192.168.3.0/24
SanJose2#
[120/1] via
[120/2] via
is directly
is directly
[120/1] via
51
SanJose1
01:33:05:
01:33:05:
SanJose1#
01:33:07:
01:33:07:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
01:33:08:
SanJose1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
Gateway of last resort is not set
C
192.168.4.0/24 is directly connected, Serial1
R
192.168.5.0/24 [120/1] via 192.168.4.1, 00:00:12, Serial1
R
192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:10, Serial0
C
192.168.2.0/24 is directly connected, Serial0
C
192.168.3.0/24 is directly connected, Ethernet0
Department of Computer and systems Engineering
52
Baypointe
01:34:53: RIP:
01:34:53:
01:34:53:
01:34:53:
01:34:53:
01:34:53: RIP:
01:34:53:
Baypointe#
01:34:56: RIP:
01:34:56:
01:34:56:
01:34:56:
sending
network
network
network
network
sending
network
v1 update to
192.168.4.0,
192.168.1.0,
192.168.2.0,
192.168.3.0,
v1 update to
192.168.5.0,
received v1
192.168.1.0
192.168.2.0
192.168.3.0
Baypointe#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
Gateway of last resort is not set
C
C
R
R
R
192.168.4.0/24
192.168.5.0/24
192.168.1.0/24
192.168.2.0/24
192.168.3.0/24
is directly
is directly
[120/2] via
[120/1] via
[120/1] via
connected, Serial0
connected, Ethernet0
192.168.4.2, 00:00:23, Serial0
192.168.4.2, 00:00:23, Serial0
192.168.4.2, 00:00:23, Serial0
53
54
SanJose1
hostname SanJose1
interface ethernet 0
ip add 172.30.3.1 255.255.255.0
interface serial 0
ip add 172.30.2.2 255.255.255.0
interface serial 1
ip add 192.168.4.9 255.255.255.252
Baypointe
hostname Baypointe
interface ethernet 0
ip add 192.168.5.1 255.255.255.0
interface serial 0
ip add 192.168.4.10 255.255.255.252
55
56
57
Notice we only used a single network statement for SanJose2, which includes both interfaces, on different
subnets, of the 172.30.0.0 major network.
SanJose1#configure terminal
Enter configuration commands, one per line.
SanJose1(config)#router rip
SanJose1(config-router)#network 172.30.0.0
SanJose1(config-router)#network 192.168.4.0
Again, notice that we only used a single network statement for SanJose1, which includes both interfaces, on
different subnets, of the 172.30.0.0 major network.
Baypointe#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Baypointe(config)#router rip
Baypointe(config-router)#network 192.168.4.0
Baypointe(config-router)#network 192.168.5.0
58
59
Step 2 Viewing the debug ip rip output and the routing tables
SanJose2
SanJose2# debug ip rip
00:14:10: RIP: received v1 update from 172.30.2.2 on Serial0
00:14:10:
172.30.3.0 in 1 hops
00:14:10:
192.168.4.0 in 1 hops
00:14:10:
192.168.5.0 in 2 hops
SanJose2#
00:14:29: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.30.1.1)
00:14:29:
subnet 172.30.2.0, metric 1
00:14:29:
subnet 172.30.3.0, metric 2
00:14:29:
network 192.168.4.0, metric 2
00:14:29:
network 192.168.5.0, metric 3
00:14:29: RIP: sending v1 update to 255.255.255.255 via Serial0 (172.30.2.1)
00:14:29:
subnet 172.30.1.0, metric 1
SanJose2#
00:14:39: RIP: received v1 update from 172.30.2.2 on Serial0
00:14:39:
172.30.3.0 in 1 hops
00:14:39:
192.168.4.0 in 1 hops
00:14:39:
192.168.5.0 in 2 hops
SanJose2# undebug all
SanJose2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
Gateway of last resort is not set
172.30.0.0/24 is subnetted, 3 subnets
C
172.30.2.0 is directly connected, Serial0
R
172.30.3.0 [120/1] via 172.30.2.2, 00:00:08, Serial0
C
172.30.1.0 is directly connected, Ethernet0
R
192.168.4.0/24 [120/1] via 172.30.2.2, 00:00:08, Serial0
R
192.168.5.0/24 [120/2] via 172.30.2.2, 00:00:08, Serial0
Department of Computer and systems Engineering
60
61
SanJose1
SanJose1#debug ip rip
RIP protocol debugging is on
SanJose1#
00:17:52: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.30.3.1)
00:17:52:
subnet 172.30.2.0, metric 1
00:17:52:
subnet 172.30.1.0, metric 2
00:17:52:
network 192.168.4.0, metric 1
00:17:52:
network 192.168.5.0, metric 2
00:17:52: RIP: sending v1 update to 255.255.255.255 via Serial0 (172.30.2.2)
00:17:52:
subnet 172.30.3.0, metric 1
00:17:52:
network 192.168.4.0, metric 1
00:17:52:
network 192.168.5.0, metric 2
00:17:52: RIP: sending v1 update to 255.255.255.255 via Serial1 (192.168.4.9)
00:17:52:
network 172.30.0.0, metric 1
SanJose1#
00:18:10: RIP: received v1 update from 172.30.2.1 on Serial0
00:18:10:
172.30.1.0 in 1 hops
SanJose1#
00:18:12: RIP: received v1 update from 192.168.4.10 on Serial1
00:18:12:
192.168.5.0 in 1 hops
SanJose1# undebug all
SanJose1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
Gateway of last resort is not set
172.30.0.0/24 is subnetted, 3 subnets
C
172.30.2.0 is directly connected, Serial0
C
172.30.3.0 is directly connected, Ethernet0
R
172.30.1.0 [120/1] via 172.30.2.1, 00:00:14, Serial0
192.168.4.0/30 is subnetted, 1 subnets
C
192.168.4.8 is directly connected, Serial1
R
192.168.5.0/24 [120/1] via 192.168.4.10, 00:00:10, Serial1
Department of Computer and systems Engineering
62
63
SanJose1#debug ip rip
RIP protocol debugging is on
SanJose1#
00:17:52: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.30.3.1)
00:17:52:
subnet 172.30.2.0, metric 1
00:17:52:
subnet 172.30.1.0, metric 2
00:17:52:
network 192.168.4.0, metric 1
00:17:52:
network 192.168.5.0, metric 2
00:17:52: RIP: sending v1 update to 255.255.255.255 via Serial0 (172.30.2.2)
00:17:52:
subnet 172.30.3.0, metric 1
00:17:52:
network 192.168.4.0, metric 1
00:17:52:
network 192.168.5.0, metric 2
00:17:52: RIP: sending v1 update to 255.255.255.255 via Serial1 (192.168.4.9)
00:17:52:
network 172.30.0.0, metric 1
SanJose1#
00:18:10: RIP: received v1 update from 172.30.2.1 on Serial0
00:18:10:
172.30.1.0 in 1 hops
SanJose1#
00:18:12: RIP: received v1 update from 192.168.4.10 on Serial1
00:18:12:
192.168.5.0 in 1 hops
SanJose1# undebug all
SanJose1#show ip route
Codes: <omitted>
Gateway of last resort is not set
172.30.0.0/24 is subnetted, 3 subnets
C
172.30.2.0 is directly connected, Serial0
C
172.30.3.0 is directly connected, Ethernet0
R
172.30.1.0 [120/1] via 172.30.2.1, 00:00:14, Serial0
192.168.4.0/30 is subnetted, 1 subnets
C
192.168.4.8 is directly connected, Serial1
R
192.168.5.0/24 [120/1] via 192.168.4.10, 00:00:10, Serial1
Department of Computer and systems Engineering
64
Compare that to the same information for the 172.30.0.0 network being sent out
Serial 0 & Ethernet 0:
Notice that the 172.30.0.0 subnets are being summarized to their classful
network address of 172.30.0.0 when sent out Serial 1 to Baypointe.
RIP automatically summarizes RIP updates between classful networks.
Because the 172.30.0.0 update is being sent out an interface (Serial 1) on a
different classful network (192.168.4.0), RIP sends out only a single update for
the entire classful network instead of all of the different subnets. This is similar
to what we did with summarizing several static routes into a single static route.
A router like SanJose1, which has an interface in more than one classful
network is sometimes called a boundary router in RIP. Boundary routers
automatically summarize RIP subnets from one classful network to the other.
65
66
Baypointe
Baypointe#debug ip rip
RIP protocol debugging is on
Baypointe#
00:20:09: RIP: received v1 update from 192.168.4.9 on Serial0
00:20:09:
172.30.0.0 in 1 hops
Baypointe#
00:20:24: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.5.1)
00:20:24:
network 172.30.0.0, metric 2
00:20:24:
network 192.168.4.0, metric 1
00:20:24: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.4.10)
00:20:24:
network 192.168.5.0, metric 1
Baypointe#
Baypointe#undebug all
Baypointe#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
Gateway of last resort is not set
R
C
C
67
Also, the subnet mask scheme could be changed (i.e. to /27) on the 172.30.0.0
network without affecting Baypointes routing table or the RIP update sent to
Baypointe by SanJose1.
Department of Computer and systems Engineering
68
69
70
71
Notice that we are only including the 172.30.0.0 interfaces, networks, for SanJose1.
We will not be exchanging RIP updates with Baypointe via the 192.168.4.0/30
network.
72
73
Step 3 - Configuring the static route on Baypointe for the 172.30.0.0/16 network
Since Baypointe and SanJose1 are not exchanging RIP updates, we need to configure a static
route on Baypointe for the 172.30.0.0/16 network. This will send all 172.30.0.0/16 traffic,
packets with destination IP addresses of 172.30.x.x, to SanJose1.
Baypointe(config)# ip route 172.30.0.0 255.255.0.0 serial 0
Once again, notice, since the exit interface is a point-to-point serial interface we chose to use
the exit-interface instead of a intermediate-address (next-hop-ip address), saving the
router from having to do a recursive lookup. However, using an intermediate-address
(next-hop-ip-address) would have worked also.
74
SanJose1
SanJose1#debug ip rip
RIP protocol debugging is on
SanJose1#
02:09:10: RIP: received v1 update from 172.30.2.1 on Serial0
02:09:10:
172.30.1.0 in 1 hops
SanJose1#
02:09:29: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.30.3.1)
02:09:29:
subnet 172.30.2.0, metric 1
02:09:29:
subnet 172.30.1.0, metric 2
02:09:29:
default, metric 1
02:09:29: RIP: sending v1 update to 255.255.255.255 via Serial0 (172.30.2.2)
02:09:29:
subnet 172.30.3.0, metric 1
02:09:29:
default, metric 1
SanJose1#
SanJose1#undebug all
SanJose1#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
C
C
R
C
S*
75
76
SanJose2
SanJose2#debug ip rip
RIP protocol debugging is on
SanJose2#
02:07:06: RIP: received v1 update from 172.30.2.2 on Serial0
02:07:06:
172.30.3.0 in 1 hops
02:07:07:
0.0.0.0 in 1 hops
SanJose2#
02:07:23: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.30.1.1)
02:07:23:
subnet 172.30.2.0, metric 1
02:07:23:
subnet 172.30.3.0, metric 2
02:07:23:
default, metric 2
02:07:23: RIP: sending v1 update to 255.255.255.255 via Serial0 (172.30.2.1)
02:07:23:
subnet 172.30.1.0, metric 1
SanJose2#
SanJose2#undebug all
SanJose2#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
<omitted>
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
Gateway of last resort is 172.30.2.2 to network 0.0.0.0
172.30.0.0/24 is subnetted, 3 subnets
C
172.30.2.0 is directly connected, Serial0
R
172.30.3.0 [120/1] via 172.30.2.2, 00:00:22, Serial0
C
172.30.1.0 is directly connected, Ethernet0
R*
0.0.0.0/0 [120/1] via 172.30.2.2, 00:00:22, Serial0
77
78
Baypointe
No RIP messages, as we are not running RIP.
Baypointe#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
Gateway of last resort is not set
S
C
C
Reflections
Notice that RIP is not being used on Baypointe. The only routes that are
not directly-connected is the static route.
79
Be sure to understand this command. We will examine it again when we take a closer look at RIPv1,
RIPv2 and IGRP. Take a look at the items in bold and make sure you understand them.
Department of Computer and systems Engineering
80
81
From
82
If you wish to see what is happening in the routers routing table process, you can use
the debug ip routing command:
SanJose2#debug ip routing
IP routing debugging is on
SanJose2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
SanJose2(config)#router rip
SanJose2(config-router)#network 172.30.0.0
SanJose2(config-router)#
00:15:03: RT: add 172.30.3.0/24 via 172.30.2.2, rip metric [120/1]
00:15:03: RT: add 0.0.0.0/0 via 172.30.2.2, rip metric [120/1]
00:15:03: RT: default path is now 0.0.0.0 via 172.30.2.2
00:15:03: RT: new default network 0.0.0.0
Department of Computer and systems Engineering
83