Chapter 2 Static Routing Part 1

CIS 82 Routing Protocols and Concepts Rick Graziani Cabrillo College graziani@cabrillo.edu Last Updated: 2/22/2009

CIS 82 Online students, before we begin: Download: Packet Tracer File: http://netacad.cabrillo.edu/curriculum/graziani/cis82/labs-e2/e2-1-52.pkt Print out this topology

Note
My web site is www.cabrillo.edu/~rgraziani. For access to these PowerPoint presentations and other materials, please email me at graziani@cabrillo.edu. See Notes section of PowerPoint for additional information.

For further information

This presentation is an overview of what is covered in the curriculum/book. For further explanation and details, please read the chapter/curriculum. Book: Routing Protocols and Concepts By Rick Graziani and Allan Johnson ISBN: 1-58713-206-0 ISBN-13: 978-58713206-3

Topics
Routers and the Network Role of the Router Introducing the Topology Examining the Connections of the Router Router Configuration Review Examining Router Interfaces Configuring an Ethernet Interface Verifying Ethernet Addresses Configuring a Serial Interfaces Examining Serial Interfaces Exploring Directly Connected Networks Verifying Changes to the Routing Table Devices on Directly Connected Networks Static Routes - Next-Hop Addresses ip route command Configuring Static Routes Routing Table Principles Resolving to an Exit Interface with a Recursive Lookup Static Routes - Exit Interfaces Configuring a Static Route with an Exit Interfaces Static Routes and Point-to-Point Networks Modifying Static Routes Verifying the Static Route Configuration Static Routes - Ethernet Interface Summary and Default Static Routes Summary Static Routes Default Static Routes

Routers and the Network

Role of the Router Introducing the Topology Examining the Connection on the Router

Role of the Router

What is the best path to 192.168.2.0/2 4 network?

Routers are primarily responsible for interconnecting networks by: Determining the best path Forwarding packets

Introducing the Topology

172.16.1.0/24

.1

172.16.2.0/24 172.16.3.0/24 .1 .1

.2

.2

192.168.1.0/24 .1 .1 192.168.2.0/24

Examining the Connections

Smart Serial Older Serial

Unlike most user PCs, a router will have multiple network interfaces. These interfaces can include a variety of connectors.

Serial Connectors

10

Serial Connectors

DCE Cable

DTE Cable
Router is typically a DTE device. The DTE cable is connected to the serial interface on the router to a CSU/DSU device (DCE).

11

Serial Connectors
DTE DCE

DTE

DTE

Labs we will use serial DTE/DCE cables (no CSU/DSU). Real World Router connected to CSU/DSU using a DTE cable.

12

Ethernet Connectors

When do you use a straight-through cable? Unlike devices Switch-to-router Hub-to-router Switch-to-PC/server Hub-to-PC/server

When do you use a crossover cable? Like devices Switch-to-switch PC/server-to-PC/server Switch-to-hub Hub-to-hub Router-to-router Router-to-PC/server

13

Router Configuration Review

Examining Router Interfaces Configuring an Ethernet Interface Verifying Ethernet Addresses Configuring a Serial Interfaces Examining Serial Interfaces
Note: This section is for review purposes only and will not be discussed in the lecture (except for Slide 29). Please see Week 1 Lab: 1.5.2 Basic Router Configuration (Cabrillo Version) for a complete introduction/review of Cisco IOS.

Examining Router Interfaces

R1# 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, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route Gateway of last resort is not set R1#

show ip route command is used to display the routing table. Initially, the routing table is empty if no interfaces have been configured. Note: Static routes and dynamic routes cannot be added to the routing table until the appropriate local interfaces, also known as the exit interfaces, have been configured on the router. (later)
15

Interfaces and their Statuses

R1# show interfaces FastEthernet0/0 is administratively down, line protocol is down Hardware is AmdFE, address is 000c.3010.9260 (bia 000c.3010.9260) <output omitted> Serial0/0/0 is administratively down, line protocol is down <output omitted>

16

Interfaces and their Statuses

R1# show ip interface brief Interface IP-Address OK? FastEthernet0/0 unassigned YES Serial0/0 unassigned YES FastEthernet0/1 unassigned YES Serial0/1 unassigned YES R1# Method manual unset unset unset Status administratively administratively administratively administratively Protocol down down down down down down down down

Used to see a portion of the interface information in a condensed format Note: Great command for checking interfaces before starting a lab!

17

Interfaces and their Statuses

R1# show running-config <output omitted> interface FastEthernet0/0 mac-address 000c.3010.9260 no ip address duplex auto speed auto shutdown ! interface FastEthernet0/1 mac-address 000c.3010.9261 no ip address duplex auto speed auto shutdown <output omitted>

show running-config command displays current configuration file another way to verify the configuration of an interface

18

Configuring an Ethernet Interface

R1(config)# interface fastethernet 0/0 R1(config-if)# ip address 172.16.3.1 255.255.255.0 R1(config-if)# no shutdown
*Mar 1 01:16:08.212: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up *Mar 1 01:16:09.214: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up

changed state to up message indicates that, physically, the connection is good. interface is properly connected to a switch or a hub. receiving a carrier signal from another device (switch, hub, PC, or another router). changed state to up message indicates that the data link layer is operational. LAN interfaces, typically no data link parameter changes. WAN interfaces in a lab environment require clocking on one side of the link
19

Unsolicited Messages from IOS

R1(config)# int fa0/0 R1(config-if)# ip address 172.16.3.1 255.255.255.0 R1(config-if)# no shutdown R1(config-if)# descri *Mar 1 01:16:08.212: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up *Mar 1 01:16:09.214: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upption R1(config-if)# The IOS often sends unsolicited messages Does not affect the command Can cause you to lose your place when typing.

20

Unsolicited Messages from IOS

R1(config)# line console 0 R1(config-line)# logging synchronous R1(config-if)# descri *Mar 1 01:28:04.242: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up *Mar 1 01:28:05.243: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up R1(config-if)# description

To keep the unsolicited output separate from your input, enter line configuration mode for the console port and add the logging synchronous

21

Reading the Routing Table

R1# show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M mobile, B - BGP <output omitted> Gateway of last resort is not set 172.16.0.0/24 is subnetted, 1 subnets 172.16.3.0 is directly connected, FastEthernet0/0

The interface was configured with the 172.16.3.1/24 IP address, which makes it a member of the 172.16.3.0/24 network. C = directly connected

R1 has an interface that belongs to this network The /24 subnet mask for this route is displayed in the line above the actual route.
22

Routers Usually Store Network Addresses

R1# show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M mobile, B - BGP <output omitted> Gateway of last resort is not set 172.16.0.0/24 is subnetted, 1 subnets C 172.16.3.0 is directly connected, FastEthernet0/0

Phone book analogy: Families not individuals with same number Occasionally, a host route is entered in the routing table; the host route represents an individual host IP address. The host route is listed with the devices host IP address and a /32 (255.255.255.255) subnet mask. The topic of host routes is discussed in another course.
23

Commands to Verify Interface Configuration

R1# show interfaces fastethernet 0/0 FastEthernet0/0 is up, line protocol is up Hardware is AmdFE, address is 000c.3010.9260 (bia 000c.3010.9260) Internet address is 172.16.3.1/24 <output omitted> R1# show ip interface brief Interface IP-Address OK? FastEthernet0/0 172.16.3.1 YES Serial0/0/0 unassigned YES FastEthernet0/1 unassigned YES Serial0/0/1 unassigned YES

Method manual unset unset unset

Status up administratively administratively administratively

Protocol up down down down down down down

R1# show running-config <output omitted> interface FastEthernet0/0 ip address 172.16.3.1 255.255.255.0 <output omitted> Note: no shutdown is not displayed.
24

Ethernet Interfaces Participate in ARP

R1# show interfaces fastethernet 0/0 FastEthernet0/0 is up, line protocol is up Hardware is AmdFE, address is 000c.3010.9260 (bia 000c.3010.9260) Internet address is 172.16.3.1/24 <output omitted>

A routers Ethernet interface participates in a LAN network just like any other device on that network. This means that these interfaces: Layer 2 MAC address ARP Cache Issue ARP Requests when needed Issue ARP Replies when required
25

Configuring a Serial Interface

R1(config)# interface serial 0/0/0 R1(config-if)# ip address 172.16.2.1 255.255.255.0 R1(config-if)# no shutdown R1# show interfaces serial 0/0/0 Serial0/0/0 is down, line protocol is down Hardware is PowerQUICC Serial Internet address is 172.16.2.1/24 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, <output omitted> The serial interface will be in the up state only after the other end of the serial link has also been properly configured.

26

Configuring a Serial Interface

R1(config)# interface serial 0/0/0 R1(config-if)# ip address 172.16.2.1 255.255.255.0 R1(config-if)# no shutdown R2(config)# interface serial 0/0/0 R2(config-if)# ip address 172.16.2.2 255.255.255.0 R2(config-if)# no shutdown Can be different

Must be hosts on same network

Both interfaces do NOT have to be the same (Serial 0/0/0). Both interfaces do have to be members of the same network Same 172.16.2.0/24 network. (The terms network and subnet can be used interchangeably in this case.)

27

Configuring a Serial Interface

R2# show interfaces serial 0/0/0 Serial0/0/0 is up, line protocol is down <output omitted> Need clock rate on DCE end

Physical link between R1 and R2 is up both ends configured correctly with: IP address/mask no shutdown command Line protocol is still down. Interface is not receiving a clock signal. clock rate command, on the router with the DCE cable.

28

Physically Connecting a WAN Interface

Typically, the router is the DTE device and is connected to a CSU/DSU, which is the DCE device. Serial interfaces require a clock signal to control the timing of the communications. In most environments, the service provider (a DCE device such as a CSU/DSU) will provide the clock. By default, Cisco routers are DTE devices
29

Configuring Serial Links in a Lab Environment

R1# show controllers serial 0/0/0 Interface Serial0/0/0 Hardware is PowerQUICC MPC860 DCE V.35, no clock <output omitted>

In a lab environment, one side of a connection must be considered a DCE and provide a clocking signal. Although Cisco serial interfaces are DTE devices by default, they can be configured as DCE devices.
30

Configuring Serial Links in a Lab Environment

R1(config)# interface serial 0/0/0 R1(config-if)# clock rate 64000 01:10:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up

Available clock rates, in bits per second, are 1200, 2400, 9600, 19200, 38400, 56000, 64000, 72000, 125000, 148000, 500000, 800000, 1000000, 1300000, 2000000, and 4000000. If DTE interface is configured with the clock rate command, IOS disregards it.

31

Verifying the Serial Interface Configuration

R1# show interfaces serial 0/0/0 Serial0/0/0 is up, line protocol is up Hardware is PowerQUICC Serial Internet address is 172.16.2.1/24 <output omitted> R1# show ip interface brief Interface IP-Address OK? Method FastEthernet0/0 172.16.3.1 YES manual Serial0/0/0 172.16.2.1 YES manual <output omitted>

Status Protocol up up up up

R1# ping 172.16.2.2 Sending 5, 100-byte ICMP Echos to 172.16.2.2, timeout is 2 seconds: <output omitted> !!!!! R1#

32

Verifying the Serial Interface Configuration

R1# show ip route <output omitted> Gateway of last resort is not set 172.16.0.0/24 is subnetted, 2 subnets C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0

172.16.2.0/24 serial network is now in the routing table for R1

33

Verifying the Serial Interface Configuration

R1# show running-config <output omitted> ! interface FastEthernet0/0 description R1 LAN ip address 172.16.3.1 255.255.255.0 ! interface Serial0/0/0 description Link to R2 ip address 172.16.2.1 255.255.255.0 clockrate 64000 ! <output omitted> R1#

Although the clock rate command is two words, IOS spells clockrate as a single word in the running configuration and startup configuration files.
34

Exploring Directly Connected Networks

Verifying Changes to the Routing Table Devices on Directly Connected Networks Cisco Discovery Protocol (CDP) Using CDP for Network Discovery

Introducing the Topology

36

OPTION: Follow along with Packet Tracer

Edit -> Preferences

IMPORTANT: It is more important that you watch and listen to what I am explaining than to follow along in Packet Tracer. You can always go back through these slides and follow along later.

Download: cis82-static-routes-student.pkt

37

R1s configuration (so far)

R1# show running-config ! hostname R1 ! interface FastEthernet0/0 ip address 172.16.3.1 255.255.255.0 ! interface Serial0/0/0 ip address 172.16.2.1 255.255.255.0 clock rate 64000 ! line con 0 exec-timeout 0 0 logging synchronous line vty 0 4 login

See previous slides for configuration commands.

38

R2s configuration (so far)

R2# show running ! hostname R2 ! interface FastEthernet0/0 no ip address shutdown ! interface Serial0/0/0 ip address 172.16.2.2 255.255.255.0 ! interface Serial0/0/1 no ip address shutdown ! line con 0 exec-timeout 0 0 logging synchronous line vty 0 4 login

See previous slides for configuration commands.

39

R3s configuration (so far)

R3# show run ! hostname R3 ! interface FastEthernet0/0 no ip address shutdown ! interface Serial0/0/1 no ip address shutdown ! line con 0 exec-timeout 0 0 logging synchronous line vty 0 4 login

See previous slides for configuration commands.

40

What interface have been configured and are up?

On each router do: show ip interface brief Which interfaces still need to be configured? Dont configure them yet!

41

Which interfaces have been configured and are up?

Use show ip interface brief
R1# show ip interface brief Interface IP-Address FastEthernet0/0 172.16.3.1 FastEthernet0/1 unassigned Serial0/0/0 172.16.2.1 Serial0/0/1 unassigned R2# show ip interface brief Interface IP-Address FastEthernet0/0 unassigned FastEthernet0/1 unassigned Serial0/0/0 172.16.2.2 Serial0/0/1 unassigned R3# show ip interface brief Interface IP-Address FastEthernet0/0 unassigned FastEthernet0/1 unassigned Serial0/0/0 unassigned Serial0/0/1 unassigned OK? YES YES YES YES OK? YES YES YES YES OK? YES YES YES YES Method manual manual manual manual Method manual manual manual manual Method manual manual manual manual

To be configured
Status Protocol up up administratively down down up up administratively down down Status Protocol administratively down down administratively down down up up administratively down down Status administratively administratively administratively administratively Protocol down down down down 42

down down down down

Examine the routing tables

R1# show ip route <output omitted> Gateway of last resort is not set 172.16.0.0/24 is subnetted, 2 subnets C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0

R2# show ip route <output omitted> Gateway of last resort is not set 172.16.0.0/24 is subnetted, 1 subnets C 172.16.2.0 is directly connected, Serial0/0/0
The routing table consists of a list of known networks. How does a router learn about networks? (3 ways) Directly connected, configured statically, and learned dynamically. How did R1 and R2 learn about their networks? Directly connected networks, when the interfaces were configured with an IP address, subnet mask and no shutdown. (clock rate for serial DCE)

43

Using debug ip routing

R2# debug ip routing IP routing debugging is on R2# conf t R2(config)# int fa0/0 R2(config-if)# ip address 172.16.1.1 255.255.255.0 R2(config-if)# no shutdown %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up RT: add 172.16.1.0/24 via 0.0.0.0, connected metric [0/0] RT: interface FastEthernet0/0 added to routing table

debug ip routing - displays any changes in the routing table. After no shutdown interface up and up debug: Network added to routing table
44

Do show ip route on R2
R2# show ip route <output omitted> Gateway of last resort is not set 172.16.0.0/24 is subnetted, 2 subnets C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0

Was there a change to the R2 routing table as a result of the interface being configured? Yes

45

Turn of debug
R2# undebug all All possible debugging has been turned off ! or ! R2# undebug ip routing IP routing debugging is off R2#

46

Do NOT do this, just watch

R2# debug ip routing IP routing debugging is on R2# config t Enter configuration commands, one per line. End with CNTL/Z. R2(config)# int fa0/0 R2(config-if)# shutdown %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down is_up: 0 state: 6 sub state: 1 line: 1 RT: interface FastEthernet0/0 removed from routing table RT: del 172.16.1.0/24 via 0.0.0.0, connected metric [0/0] RT: delete subnet route to 172.16.1.0/24 <some ouput omitted> R2(config-if)# no ip address R2(config-if)# end R2# undebug all All possible debugging has been turned off

The shutdown command is used to disable interfaces. Retains the IPaddress/mask configuration on the interface but shuts it down temporarily. To completely remove the configuration, enter no ip address

47

Assume we did not remove this interface

R2# show ip route Gateway of last resort is not set 172.16.0.0/24 is subnetted, 1 subnets C 172.16.2.0 is directly connected, Serial0/0/0 R2(config)# interface fastethernet 0/0 R2(config-if)# ip address 172.16.1.1 255.255.255.0 R2(config-if)# no shutdown As we continue, assume we did not remove the fa0/0 interface.

48

Note on debug command

R2# undebug all All possible debugging has been turned off The debug commands, especially the debug all command, should be used sparingly. Useful for troubleshooting CPU and memory intensive Use sparingly Disable them immediately when they are no longer needed.

49

Configure the rest of the interfaces for R2 and R3

R2(config)# interface serial 0/0/1 R2(config-if)# ip address 192.168.1.2 255.255.255.0 R2(config-if)# clock rate 64000 R2(config-if)# no shutdown

R3(config)# interface fastethernet 0/0 R3(config-if)# ip address 192.168.2.1 255.255.255.0 R3(config-if)# no shutdown R3(config-if)# exit R3(config)# interface serial 0/0/1 R3(config-if)# ip address 192.168.1.1 255.255.255.0 R3(config-if)# no shutdown

The rest of the configurations for Routers R2 and R3.

50

Verifying the configurations

R1# show ip interface brief Interface IP-Address OK? FastEthernet0/0 172.16.3.1 YES Serial0/0/0 172.16.2.1 YES FastEthernet0/1 unassigned YES Serial0/0/1 unassigned YES Method manual manual manual manual

How do you know if the interfaces are active?

Status Protocol up up up up administratively down down administratively down down

R2# show ip interface brief Interface IP-Address OK? Method Status Protocol FastEthernet0/0 172.16.1.1 YES manual up up Serial0/0/0 172.16.2.2 YES manual up up FastEthernet0/1 unassigned YES manual administratively down down Serial0/0/1 192.168.1.2 YES manual up up R3# show ip interface brief Interface IP-Address FastEthernet0/0 192.168.2.1 Serial0/0/0 unassigned FastEthernet0/1 unassigned Serial0/0/1 192.168.1.1

OK? YES YES YES YES

Method manual manual manual manual

Status Protocol up up administratively down down administratively down down up up

51

Verifying the new entries in the routing table

R1# show ip route 172.16.0.0/24 is subnetted, 2 subnets C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 R2# show ip route

How did these networks get into the routing table? When the interfaces were

C C C

172.16.0.0/24 is subnetted, 2 subnets configured with an IP address, 172.16.1.0 is directly connected, FastEthernet0/0 subnet mask, and no shutdown. 172.16.2.0 is directly connected, Serial0/0/0 (clock rate for DCE serial) 192.168.1.0/24 is directly connected, Serial0/0/1

R3# show ip route C C 192.168.1.0/24 is directly connected, Serial0/0/1 192.168.2.0/24 is directly connected, FastEthernet0/0
52

Verifying Configurations

Which networks can R1 communicate with? 172.16.3.0/24 and 172.16.2.0/24 Which networks can R2 communicate with? 172.16.1.0/24, 172.16.2.0/24, and 192.168.1.0/24 Which networks can R3 communicate with? 192.168.1.0/24 and 192.168.2.0/24
53

Try pinging remote networks from R2

R2# ping 172.16.3.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.3.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) R2# ping 192.168.2.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)

Why did these pings fail? R2 does not know about these networks. R2 does not have a match in its routing table for these IP addresses.

54

Pings from R2 to 172.16.3.1

R2# ping 172.16.3.1 ..... IP Packet 172.16.3.1
Destination IP Address

R2# show ip route 172.16.0.0/24 is subnetted, 2 subnets C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0/0 C 192.168.1.0/24 is directly connected, Serial0/0/1
This is how IOS looks for a match (more later): 172.16.3.1 matches 16 bits of 172.16.0.0 (more later) Does 172.16.3.1s 24 leftmost bits match the 172.16.1.0/24 network? No Does 172.16.3.1s 24 leftmost bits match the 172.16.2.0/24 network? No Does 172.16.3.1s 24 leftmost bits match the 192.168.1.0/24 network? No Packets (with pings) are dropped.

55

Looking at the bits

IP Packet 172.16.3.1
Destination IP Address

Match?

Only Only 1 bit 22matches bitsmatch match between between 172.16.3.1 172.16.3.1 and and 192.168.1.0 172.16.1.0 Only 23 bits between 172.16.3.1 and 172.16.1.0

56

Pings from R2 to 192.168.1.1

R2# ping 192.168.1.1 !!!!

IP Packet 192.168.1.1
Destination IP Address

Match?

R2# show ip route 172.16.0.0/24 is subnetted, 2 subnets C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0/0 C 192.168.1.0/24 is directly connected, Serial0/0/1

Why does this ping succeed? 24 bits match between 192.168.1.1 and 192.168.1.0.

57

R2# ping 192.168.1.1 !!!!

The exit interface for this route is Serial 0/0/1

R2# show ip route 172.16.0.0/24 is subnetted, 2 subnets C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0/0 C 192.168.1.0/24 is directly connected, Serial0/0/1 IP Packet HDLC Hdr 192.168.1.1
Destination IP Address

CRC

58

Static Routes with Next-Hop Addresses

ip route command Configuring Static Routes Routing Table Principles Resolving to an Exit Interface with a Recursive Lookup

Purpose and Command Syntax of the ip route I only have one way to Command
172.16.3.0/24 network, so I will use a static route.

I only have one way to rest of the world (Internet), so I will use a static route.

Static routes are commonly used when routing from a network to a stub network. A stub network is a network accessed by a single route. Dynamic routing protocol between R1 and R2 is a waste of resources.

60

ip route Command
The command for configuring a static route is ip route. The complete syntax for configuring a static route is: ip route prefix mask {ip-address | interface-type interface-number [ip-address]} [dhcp] [distance] [name next-hop-name] [permanent | track number] [tag tag]

61

ip route Command
Simpler version of the syntax: Router(config)# ip route network-address subnet-mask {ip-address | exit-interface} network-address: Destination network address of the remote network subnet-mask: Subnet mask of the remote network One or both of the following parameters must also be used: ip-address: Next-hop routers IP address. (Does not have to be next-hop.) exit-interface: Outgoing or exit interface

62

Configuring Static Routes

What are the remote networks that R1 does not know about? 172.16.1.0/124: The LAN on R2 192.168.1.0/24: The serial network between R2 and R3 192.168.2.0/24: The LAN on R3

63

Configure a static route with debug ip routing on

R1# debug ip routing R1# conf t R1(config)# ip route 172.16.1.0 255.255.255.0 172.16.2.2
00:20:15: RT: add 172.16.1.0/24 via 172.16.2.2, static metric [1/0]

R1# show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 R1# un all

The remote networks that R1 does not know about: 172.16.1.0/24: The LAN on R2 192.168.1.0/24: The serial network between R2 and R3 192.168.2.0/24: The LAN on R3
64

Looking at what we just did

R1(config)# ip route 172.16.1.0 255.255.255.0 172.16.2.2 Remote Network and Mask Next-hop IP address

The IP address is the actual next-hop routers IP address. This IP address is reachable from one of this routers directly connected networks.

65

Configure the other two static routes for R1 and verify with show ip route
R1(config)# ip route 192.168.1.0 255.255.255.0 172.16.2.2 R1(config)# ip route 192.168.2.0 255.255.255.0 172.16.2.2 R1(config)# end R1# show ip route 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 [1/0] via 172.16.2.2

We have just configured static routes on R1 to reach: 172.16.1.0/24: The LAN on R2 192.168.1.0/24: The serial network between R2 and R3 192.168.2.0/24: The LAN on R3 Why do all three static routes have the same next-hop IP address?
66

Looking at the static routes we just configured

R1(config)# ip route 172.16.1.0 255.255.255.0 172.16.2.2 R1(config)# ip route 192.168.1.0 255.255.255.0 172.16.2.2 R1(config)# ip route 192.168.2.0 255.255.255.0 172.16.2.2 R1# show ip route 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 [1/0] via 172.16.2.2

Because packets for all the remote networks must be forwarded to Router R2, the nexthop router 172.16.2.2. [1/0] 1 = Administrative Distance (later) 0 = Metric (always 0 later)

67

Verifying Static Routes

R1# show running-config <output omitted> ! ip route 172.16.1.0 255.255.255.0 172.16.2.2 ip route 192.168.1.0 255.255.255.0 172.16.2.2 ip route 192.168.2.0 255.255.255.0 172.16.2.2 ! <output omitted> R1# copy running-config startup-config

Now is a good time to save the configuration to NVRAM with the copy running-config startup-config command.

68

Alex Zinins Routing Table Principles

I know about my remote networks but it is not my responsibility if R2 and R3 know about their remote networks.

Principle 1: Every router makes its decision alone, based on the information it has in its own routing table. R1 makes forwarding decisions based solely on the information in the routing table. R1 does not consult the routing tables in any other routers. Making each router aware of remote networks is the responsibility of the network administrator.

69

Alex Zinins Routing Table Principles

Just because I know how to get to R3s LAN, 192.168.2.0/24 and I send that packet to R2, doesnt mean R2 knows how to get there.

???

Principle 2: The fact that one router has certain information in its routing table does not mean that other routers have the same information.
70

Alex Zinins Routing Table Principles

And if the packet for R3s LAN reaches 192.168.2.0/24, I dont know if R3 has a route back to 172.16.3.0/24 for any return traffic. ???

Principle 3: Routing information about a path from one network to another does not provide routing information about the reverse, or return, path.

71

Configure R2 and R3 Static Routes and verify using show ip route

R2(config)# ip route 172.16.3.0 255.255.255.0 172.16.2.1 R2(config)# ip route 192.168.2.0 255.255.255.0 192.168.1.1

R3(config)# ip route 172.16.1.0 255.255.255.0 192.168.1.2 R3(config)# ip route 172.16.2.0 255.255.255.0 192.168.1.2 R3(config)# ip route 172.16.3.0 255.255.255.0 192.168.1.2 Configure static routes for R2 to reach all remote networks. Which networks are they? 172.16.3.0 255.255.255.0 192.168.2.0 255.255.255.0 Configure static routes for R3 to reach all remote networks. Which networks are they? 172.16.1.0 255.255.255.0 172.16.2.0 255.255.255.0 172.16.3.0 255.255.255.0 Do you need to configure static routes for directly connected networks? No, the router learned about these when the interface was configured.

72

R1# show ip route <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 [1/0] via 172.16.2.2 R2# show ip route <output omitted> 172.16.0.0/24 is subnetted, 3 subnets C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0/0 S 172.16.3.0 [1/0] via 172.16.2.1 C 192.168.1.0/24 is directly connected, Serial0/0/1 S 192.168.2.0/24 [1/0] via 192.168.1.1 R3# show ip route <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 192.168.1.2 S 172.16.2.0 [1/0] via 192.168.1.2 S 172.16.3.0 [1/0] via 192.168.1.2 C 192.168.1.0/24 is directly connected, Serial0/0/1 C 192.168.2.0/24 is directly connected, FastEthernet0/0

73

Verify End-to-End Connectivity using ping

R1# ping 172.16.1.1 !!!!! Success rate is 100 percent = 28/28/32 ms R1# ping 192.168.1.1 !!!!! Success rate is 100 percent = 56/56/56 ms R1# ping 192.168.1.2 !!!!! Success rate is 100 percent = 28/29/32 ms R1# ping 192.168.2.1 !!!!! Success rate is 100 percent = 56/56/56 ms R1#

(5/5), round-trip min/avg/max

(5/5), round-trip min/avg/max

(5/5), round-trip min/avg/max

(5/5), round-trip min/avg/max

74

Resolving to an Exit Interface with a Recursive Route Lookup

IP Packet 192.168.1.1
Destination IP Address

2 1

R1# show ip route <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 Exit Interface C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 [1/0] via 172.16.2.2
Route resolvability - Before any packet is forwarded by a router, the routing table process must determine the exit interface to use to forward the packet. When the router has to perform multiple lookups in the routing table before forwarding a packet, it is performing a process known as a recursive route lookup.

75

Exit Interface Is Down (Dont do this)

R1# debug ip routing IP routing debugging is on R1# config t R1(config)# int s0/0/0 R1(config-if)# shutdown R1(config-if)# end RT: interface Serial0/0/0 removed from routing table Interface RT: del 172.16.2.0/24 via 0.0.0.0, connected metric [0/0] RT: delete subnet route to 172.16.2.0/24 RT: del 192.168.1.0 via 172.16.2.2, static metric [1/0] Static Route RT: delete network route to 192.168.1.0 RT: del 172.16.1.0/24 via 172.16.2.2, static metric [1/0] Static Route RT: delete subnet route to 172.16.1.0/24 Note: Packet Tracer R1# show ip route Output should include del <output omitted> 192.168.2.0 Gateway of last resort is not set 172.16.0.0/24 is subnetted, 1 subnets C 172.16.3.0 is directly connected, FastEthernet0/0

If an interface is down (removed from routing table), all three static routes that are resolved to that interface as the exit interface will be removed from the routing table. Cant have a route if the exit interface does not exist.

76

When the interface comes back up

The static routes are still in R1s running configuration. If the interface comes back up (is enabled again with no shutdown), the IOS routing table process will reinstall these static routes into the routing table. R1# show ip route Serial 0/0/0: no shutdown <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 [1/0] via 172.16.2.2 Directly connected network route is reinstalled in the routing table. Static routes using that exit interface are reinstalled in the routing table.

77

Static Routes with Exit Interfaces

Configuring a Static Route with an Exit Interfaces Static Routes and Point-to-Point Networks Modifying Static Routes Verifying the Static Route Configuration Static Routes - Ethernet Interface

Static Routes with Next-hop IP Addresses

Router(config)# ip route network-address subnet-mask {ip-address | exit-interface} Currently, R1s static route for the 192.168.2.0/24 network is configured with the nexthop IP address of 172.16.2.2. The exit-interface is resolved with a recursive lookup ip route 192.168.2.0 255.255.255.0 172.16.2.2

R1# show ip route Recursive Lookup <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 [1/0] via 172.16.2.2
79

Remove this current static route and configure it with an exit interface.
R1(config)# no ip route 192.168.2.0 255.255.255.0 172.16.2.2 R1(config)# ip route 192.168.2.0 255.255.255.0 serial 0/0/0 R1(config)# end R1# show ip route <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 is directly connected, Serial0/0/0

Delete this current static route. Configure same static route using an exit interface. The exit interface is the same one that the static route was resolved to when it used the next-hop IP address. Verify with show ip route Resolves the route to an exit interface in a single lookup, the same Serial 0/0/0 interface.

80

Important note
R1# show ip route <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 [1/0] via 172.16.2.2 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 [1/0] via 172.16.2.2 S 192.168.2.0/24 is directly connected, Serial0/0/0 The static route displays the route as directly connected. It is important to understand that this does not mean that this route is a directly connected network or a directly connected route. This route is still a static route. The next chapter examines the importance of this fact when it discusses administrative distances in the next chapter. You will learn that this type of static route still has an administrative distance of 1. For now, just note that this route is still a static route with an administrative distance of 1 and is not a directly connected network.

81

Static Routes and Point-to-Point Networks

Static routes that are configured with exit interfaces instead of next-hop IP addresses are ideal for most serial point-to-point networks. Point-to-point networks that use protocols such as HDLC and PPP
82

Modifying Static Routes (already did this)

<Done in previously> R1(config)# no ip route 192.168.2.0 255.255.255.0 172.16.2.2 R1(config)# ip route 192.168.2.0 255.255.255.0 serial 0/0/0

There is no way to modify an existing static route. The static route must be deleted and a new one configured.
83

Modifying Static Routes

R1(config)# R1(config)# R1(config)# R1(config)# R2(config)# R2(config)# R2(config)# R2(config)# R3(config)# R3(config)# R3(config)# R3(config)# R3(config)# R3(config)# no ip no ip no ip no ip no ip no ip no ip ip route 172.16.1.0 255.255.255.0 172.16.2.2 route 172.16.1.0 255.255.255.0 serial 0/0/0 ip route 192.168.1.0 255.255.255.0 172.16.2.2 route 192.168.1.0 255.255.255.0 serial 0/0/0 ip route 172.16.3.0 255.255.255.0 172.16.2.1 route 172.16.3.0 255.255.255.0 serial 0/0/0 ip route 192.168.2.0 255.255.255.0 192.168.1.1 route 192.168.2.0 255.255.255.0 serial 0/0/1 ip route 172.16.1.0 255.255.255.0 192.168.1.2 route 172.16.1.0 255.255.255.0 serial 0/0/1 ip route 172.16.2.0 255.255.255.0 192.168.1.2 route 172.16.2.0 255.255.255.0 serial 0/0/1 ip route 172.16.3.0 255.255.255.0 192.168.1.2 route 172.16.3.0 255.255.255.0 serial 0/0/1

Modifying the rest of the serial point-to-point static routes using exit interfaces. Delete the previous static routes

84

Verifying Static Route Changes

R1# show running-config <output omitted> ip route 172.16.1.0 255.255.255.0 Serial0/0/0 ip route 192.168.1.0 255.255.255.0 Serial0/0/0 ip route 192.168.2.0 255.255.255.0 Serial0/0/0 <output omitted> R2# show running-config <output omitted> ip route 172.16.3.0 255.255.255.0 Serial0/0/0 ip route 192.168.2.0 255.255.255.0 Serial0/0/1 <output omitted>

R3# show running-config <output omitted> ip route 172.16.1.0 255.255.255.0 Serial0/0/1 ip route 172.16.2.0 255.255.255.0 Serial0/0/1 ip route 172.16.3.0 255.255.255.0 Serial0/0/1 <output omitted>

85

R1# show ip route 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 is directly connected, Serial0/0/0 C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S 192.168.1.0/24 is directly connected, Serial0/0/0 S 192.168.2.0/24 is directly connected, Serial0/0/0 R2# show ip route 172.16.0.0/24 is subnetted, 3 subnets C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0/0 S 172.16.3.0 is directly connected, Serial0/0/0 C 192.168.1.0/24 is directly connected, Serial0/0/1 S 192.168.2.0/24 is directly connected, Serial0/0/1

Verifying Static Route Changes

R3# show ip route 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 is directly connected, Serial0/0/1 S 172.16.2.0 is directly connected, Serial0/0/1 S 172.16.3.0 is directly connected, Serial0/0/1 C 192.168.1.0/24 is directly connected, Serial0/0/1 C 192.168.2.0/24 is directly connected, FastEthernet0/0 86

Verifying Static Route Changes

R1# ping 192.168.2.1 Sending 5, 100-byte ICMP Echos to 172.16.3.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms R2# ping 172.16.3.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms R2# ping 192.168.2.1 Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms R3# ping 172.16.3.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms
87

Static Routes with Ethernet Interfaces

Modified topology
88

Sending an ARP Request

R1(config)# ip route 192.168.2.0 255.255.255.0 172.16.2.2

R2s abcd MAC? R1 checks ARP Cache for 172.16.2.2 matching MAC address. If does not exist, R1 sends ARP Request and R2 sends ARP Reply. R1 uses R2s MAC address for 172.16.2.2 as the destination MAC address for the packet.

192.168.2.10
172.16.2.2
ARP Reply ARP Request

ARP Cache IP Add <-> MAC Add abcd

89

172.16.2.2 <->

Static Routes and Ethernet Exit Interfaces

<Not recommended> R1(config)# ip route 192.168.2.0 255.255.255.0 fastethernet0/1

<Recommended> R1(config)# ip route 192.168.2.0 255.255.255.0 fastethernet0/1 172.16.2.2

R1# show ip route S 192.168.2.0/24 [1/0] via 172.16.2.2 FastEthernet0/1

Best not to use only an exit interface with Ethernet interfaces. Ethernet networks is a multiaccess network. Can be multiple next-hop addresses, multiple routers. Router will not have sufficient information to determine which device is the next-hop device. Use both the next-hop interface and the exit interface for Ethernet exit interfaces. Only a single route lookup now needed.

90

Summary and Default Static Routes

Summary Static Routes Default Static Routes

Summarizing Routes to Reduce the Size of the Routing Table

Summary route is a single route that can be used to represent multiple routes. Generally a set of contiguous networks (but do not have to be) Have the same exit interface or next-hop IP address. Example: 10.0.0.0/16, 10.1.0.0/16, 10.2.0.0/16, 10.3.0.0/16, 10.4.0.0/16, 10.5.0.0/16, all the way through 10.255.0.0/16 Can be represented by a single network address: 10.0.0.0/8. Creates smaller routing tables More efficient routing table lookup process more efficient. A single static route can be used to represent dozens, hundreds, or even thousands of routes. As of Feb 2010, there are more than 300,000 routes in the Internet core routers. Most of these are summarized routes.

92

Summarizing Routes to Reduce the Size of the Routing Table

R3: ip route 172.16.1.0 255.255.255.0 Serial0/0/1 ip route 172.16.2.0 255.255.255.0 Serial0/0/1 ip route 172.16.3.0 255.255.255.0 Serial0/0/1

All three routes are forwarding traffic out the same Serial 0/0/1 interface. Can be summarized to the single 172.16.0.0 255.255.252.0 Lets see how!

93

Calculating a Summary Route

Step 1. Write out the networks that you want to summarize in binary. Step 2. To find the subnet mask for summarization, start with the leftmost bit. Step 3. Work your way to the right, finding all the bits that match consecutively. ip route

172.16.0.0 255.255.252.0 serial0/0/1

Step 4. When you find a column of bits that do not match, stop. You are at the summary boundary. Step 5. Count the number of leftmost matching bits, which in our example is 22. This number becomes your subnet mask for the summarized route, /22 or 255.255.252.0. Step 6. To find the network address for summarization: Copy the matching 22 bits Add all 0 bits to the end to make 32 bits.
94

Configure a Summary Route

R3(config)# no ip route 172.16.1.0 255.255.255.0 serial0/0/1 R3(config)# no ip route 172.16.2.0 255.255.255.0 serial0/0/1 R3(config)# no ip route 172.16.3.0 255.255.255.0 serial0/0/1 R3(config)# ip route 172.16.0.0 255.255.252.0 serial0/0/1

Delete individual static routes. Configure single summary route.

95

Changes in Routing Table

R3# show ip route Before <output omitted> 172.16.0.0/24 is subnetted, 3 subnets S 172.16.1.0 is directly connected, Serial0/0/1 S 172.16.2.0 is directly connected, Serial0/0/1 S 172.16.3.0 is directly connected, Serial0/0/1 C 192.168.1.0/24 is directly connected, Serial0/0/1 C 192.168.2.0/24 is directly connected, FastEthernet0/0 R3# show ip route After Fewer routes <output omitted> mean faster 172.16.0.0/22 is subnetted, 1 subnets lookups! S 172.16.0.0 is directly connected, Serial0/0/1 C 192.168.1.0/24 is directly connected, Serial0/1 C 192.168.2.0/24 is directly connected, FastEthernet0/0

What do you expect to see? Any packet with a destination IP address belonging to the 172.16.1.0/24, 172.16.2.0/24, or 172.16.3.0/24 network matches this summarized route.

96

Verify the Summary Route

R3# ping 172.16.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, !!!!! Success rate is 100 percent (5/5), round-trip 28/29/32 ms R3# ping 172.16.2.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.2.1, !!!!! Success rate is 100 percent (5/5), round-trip 56/56/60 ms R3# ping 172.16.3.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.3.1, !!!!! Success rate is 100 percent (5/5), round-trip 56/56/60 ms R3# timeout is 2 seconds: min/avg/max =

timeout is 2 seconds: min/avg/max =

timeout is 2 seconds:
min/avg/max =

97

Default Static Route

I only have one way to rest of the world (Internet), so I will use a static default route.

A default route is used to represent all routes with zero or no bits matching. When there are no routes that have a more specific match, the default route will be a match. (more later) A default static route is a route that will match all packets.

98

Configuring a Default Static Route

Router(config)# ip route 0.0.0.0 0.0.0.0 [exit-interface | ip-address ]

0.0.0.0 0.0.0.0 network address and mask is called a quad-zero route.

99

Configuring a Default Static Route

ip route 172.16.1.0 255.255.255.0 serial 0/0/0 ip route 192.168.1.0 255.255.255.0 serial 0/0/0 ip route 192.168.2.0 255.255.255.0 serial 0/0/0

Stub network

R1 is a stub router and is connected only to R2. R1 doesnt need specific routing information to reach R3 networks. Currently R1 has three static routes. All three static routes have a(n): Exit interface Serial 0/0/0 Next-hop Router R2
100

Configuring a Default Static Route

R1(config)# no ip route 172.16.1.0 255.255.255.0 serial 0/0/0 R1(config)# no ip route 192.168.1.0 255.255.255.0 serial 0/0/0 R1(config)# no ip route 192.168.2.0 255.255.255.0 serial 0/0/0 R1(config)# ip route 0.0.0.0 0.0.0.0 serial 0/0/0

Delete individual static routes. Configure single default static route.

101

What will the routing table look like now?

R1# show ip route

Before

S C C S S

172.16.0.0/24 is subnetted, 3 subnets 172.16.1.0 is directly connected, Serial0/0/0 172.16.2.0 is directly connected, Serial0/0/0 172.16.3.0 is directly connected, FastEthernet0/0 192.168.1.0/24 is directly connected, Serial0/0/0 192.168.2.0/24 is directly connected, Serial0/0/0

R1# show ip route After <some codes omitted> * - candidate default, U - per-user static route, o - ODR

Gateway of last resort is 0.0.0.0 to network 0.0.0.0 172.16.0.0/24 is subnetted, 2 subnets C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S* 0.0.0.0/0 is directly connected, Serial0/0/0
102

Verifying a Default Static Route

R1# show ip route <some codes omitted> * - candidate default, U - per-user static route, o - ODR Gateway of last resort is 0.0.0.0 to network 0.0.0.0 172.16.0.0/24 is subnetted, 2 subnets C 172.16.2.0 is directly connected, Serial0/0/0 C 172.16.3.0 is directly connected, FastEthernet0/0 S* 0.0.0.0/0 is directly connected, Serial0/0/0

A /0 mask indicates that zero or no bits are needed to match. As long as a more specific match doesnt exist, the default static route will match all packets. Very common No need to store hundreds or thousands of routes to different networks.

103

Managing and Troubleshooting Static Routes

Static Routes and Packet Forwarding Troubleshooting a Missing Route Solving the Missing Route

Static Routes and Packet Forwarding

105

How How did did R1 R1 learn learn about about its directly this static connected route? networks?
R1(config)# ip route 0.0.0.0 0.0.0.0 serial 0/0/0 R1# show ip route Gateway of last resort is 0.0.0.0 to network 0.0.0.0

C C S*

172.16.0.0/24 172.16.2.0 172.16.3.0 0.0.0.0/0 is

is subnetted, 2 subnets No Match with Dest. IP Add is directly connected, Serial0/0/0 No Match with is directly connected, FastEthernet0/0 Dest. IP Add directly connected, Serial0/0/0 Matches Dest. IP Add
106

How How did did R2 R2 learn learn about about its directly these static connected routes? networks?
R2(config)# ip route 172.16.3.0 255.255.255.0 serial 0/0/0 R2(config)# ip route 192.168.2.0 255.255.255.0 serial 0/0/1

R2# show ip route 172.16.0.0/24 is subnetted, 3 subnets No Match C 172.16.1.0 is directly connected, FastEthernet0/0 C 172.16.2.0 is directly connected, Serial0/0/0 No Match S 172.16.3.0 is directly connected, Serial0/0/0 No Match C 192.168.1.0/24 is directly connected, Serial0/0/1 No Match S 192.168.2.0/24 is directly connected, Serial0/0/1 Match!
107

How How did did R3 R3 learn learn about about its directly these static connected routes? networks?
R3(config)# ip route 172.16.0.0 255.255.252.0 serial0/0/1 R3# show ip route 172.16.0.0/22 is subnetted, 1 subnets 172.16.0.0 is directly connected, Serial0/0/1 No Match 192.168.1.0/24 is directly connected, Serial0/1 No Match 192.168.2.0/24 is directly connected, FastEthernet0/0 Match!

S C C

108

Troubleshooting a Missing Route

When end-to-end connectivity is a problem, begin by making sure that you can ping your own interface and other devices on your own directly connected networks. When this has been verified, begin testing connectivity to remote networks and from other devices. Networks are subject to many different forces that can cause their status to change quite often: Interface failure Dropped connection by a service provider Oversaturation of links Incorrect configuration entered by an administrator. Tools: ping traceroute show ip route show ip interface brief

109

Troubleshooting Static Routes

Download: cis82-static-routes-troubleshooting.pkt Determine why the PCs cannot ping each other and fix the problem.
110

Troubleshooting Techniques

Make sure all interfaces are up and up What command will help you determine this? R1# show ip interface brief What are some of the reasons an interface may be down? Didnt issue the no shutdown command Missing clock rate command on Serial DCE interface.

Missing or incorrect cable No connection to other end device: Ethernet: No switch or hub attached Serial: Other end not connected or configured Both ends of serial interface must be configured correctly to be up

111

Troubleshooting Techniques

Can you ping addresses on directly connected networks (next-hop addresses)? Can you ping other interfaces on the next-hop router? Can you ping the next-hop interface? If unsuccessful: Make sure each router on the path to that network have the remote network in its routing table. Make sure each router on the path to that network have a return route back to this router.

112

Alex Zinins Routing Table Principles

I know about my remote networks but it is not my responsibility if R2 and R3 know about their remote networks.

Principle 1: Every router makes its decision alone, based on the information it has in its own routing table. R1 makes forwarding decisions based solely on the information in the routing table. R1 does not consult the routing tables in any other routers. Making each router aware of remote networks is the responsibility of the network administrator.

113

Alex Zinins Routing Table Principles

Just because I know how to get to R3s LAN, 192.168.2.0/24 and I send that packet to R2, doesnt mean R2 knows how to get there.

???

Principle 2: The fact that one router has certain information in its routing table does not mean that other routers have the same information.
114

Alex Zinins Routing Table Principles

And if the packet for R3s LAN reaches 192.168.2.0/24, I dont know if R3 has a route back to 172.16.3.0/24 for any return traffic. ???

Principle 3: Routing information about a path from one network to another does not provide routing information about the reverse, or return, path.

115

Cisco Discovery Protocol (CDP)

Download: cis82-static-routing-cdp.pkt CDP does not have anything specifically to do with static routing, but it is covered in this chapter.
116

Cisco Discovery Protocol (CDP)

Cisco Discovery Protocol (CDP) Network-monitoring and troubleshooting tool. Get information about directly connected Cisco devices. Cisco proprietary.

117

CDP Advertisements

By default, each Cisco device sends periodic messages to directly connected Cisco devices. CDP advertisements. Information gathered from other devices can assist you: Troubleshooting Network discovery tool

118

Layer 2 Neighbors

CDP operates at Layer 2 only. Therefore, CDP neighbors are Cisco devices that are directly connected physically and share the same data link. R1 and S1 are CDP neighbors R1 and R2 are CDP neighbors R2 and S2 are CDP neighbors R2 and R3 are CDP neighbors R3 and S3 are CDP neighbors

119

CDP Operation
R3# show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone Device ID Local Intrfce Holdtme Capability Platform Port ID Switch Fas 0/0 135 S 2950 Fas 0/1 R2 Ser 0/0/1 135 R C1841 Ser 0/0/1 R3#

What is the Device ID? Hostname

What is the Capability? S=Switch R= Router What is the Platform? Model Number

120

Try it on R1
R1# show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone Device ID Local Intrfce Holdtme Capability Platform Port ID Switch Fas 0/0 153 S 2950 Fas 0/1 R2 Ser 0/0/0 153 R C1841 Ser 0/0/0 R1#

121

Try it on R2
R2# show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone Device ID Local Intrfce Holdtme Capability Platform Port ID Switch Fas 0/0 176 S 2950 Fas 0/1 R3 Ser 0/0/1 176 R C1841 Ser 0/0/1 R1 Ser 0/0/0 176 R C1841 Ser 0/0/0 R2#

122

Try it with the detail option

R3# show cdp neighbors detail Device ID: Switch Entry address(es): Platform: cisco 2950, Capabilities: Switch Interface: FastEthernet0/0, Port ID (outgoing port): FastEthernet0/1 <output omitted> Duplex: full --------------------------Device ID: R2 Entry address(es): IP address : 192.168.1.2 IP Address of remote router Platform: cisco C1841, Capabilities: Router Interface: Serial0/0/1, Port ID (outgoing port): Serial0/0/1 Holdtime: 122 Version : Cisco IOS Software, 1841 Software (C1841-ADVIPSERVICESK9-M), Version 12.4(15)T1, RELEASE SOFTWARE (fc2) <output omitted> 123

Disabling CDP
Router(config)# no cdp run or Router(config-if)# no cdp enable CDP can be a security risk. To disable CDP globally, for the entire device, use this command: Router(config)# no cdp run To stop CDP advertisements on a particular interface: Router(config-if)# no cdp enable

124

Chapter 2 Static Routing

CIS 82 Routing Protocols and Concepts Rick Graziani Cabrillo College graziani@cabrillo.edu