Static Routing
Download
Report
Transcript Static Routing
Static Routing
Routing Protocols and
Concepts – Chapter 2
Version 4.0
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
1
Objectives
Define the general role a router plays in networks.
Describe the directly connected networks, different
router interfaces.
Examine directly connected networks in the routing
table and use the CDP protocol.
Describe static routes with exit interfaces.
Describe summary and default route.
Examine how packets get forwarded when using
static routes.
Identify how to manage and troubleshoot static
routes.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
2
General Role of the Router
Functions of a Router
– Best Path Selections
– Forwarding packets to destination
Introducing the Topology
– 3 1800 series routers connected via WAN links
– Each router connected to a LAN represented by a switch and a PC
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
3
General Role of the Router
Connections of a Router for WAN
– A router has a DB-60 port that can support 5 different cabling standards
Connections of a Router for Ethernet
– 2 types of connectors can be used: Straight through and Cross-over
•
Straight through used to connect:
– Switch-to-Router, Switch-to-PC, Router-to-Server, Hub-to-PC, Hub-to-Server
•
Cross-over used to connect:
– Switch-to-Switch, PC-to-PC, Switch-to-Hub, Hub-to-Hub, Router-to-Router
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
4
Interfaces
Configuring an Ethernet interface
– By default all serial and Ethernet interfaces are down
– To enable an interface use the No Shutdown command
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
5
Interfaces
Verifying Ethernet interface
– Show interfaces for fastEthernet 0/0 – command used to show
status of fast Ethernet port
– Show ip interface brief
– Show running-config
Ethernet interfaces participate in ARP
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
6
Interfaces
Configuring a Serial interface
– Enter interface configuration mode
– Enter in the ip address and subnet mask
– Enter in the no shutdown command
Example:
– R1(config)#interface serial 0/0
– R1(config-if)#ip address 172.16.2.1 255.255.255.0
– R1(config-if)#no shutdown
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
7
Interfaces
Examining Router Interfaces
– Physically connecting a WAN Interface.
– A WAN Physical Layer connection has sides:
• Data Circuit-terminating Equipment (DCE) – This is the
service provider. CSU/DSU is a DCE device.
• Data Terminal Equipment (DTE) – Typically the router is
the DTE device.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
8
Interfaces
Configuring serial links in a lab environment
– One side of a serial connection must be considered a DCE.
– This requires placing a clocking signal – use the clock rate
command.
– Example:
• R1(config)#interface serial 0/0
• R1(config-if)#clockrate 64000
– Serial Interfaces require a clock signal to control the timing of
the communcations.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
9
Routing Table and CDP Protocol
Purpose of the debug ip routing command
– Allows you to view changes that the router performs when
adding or removing routes.
– Example:
• R2#debug ip routing
• IP routing debugging is on
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
10
Routing Table and CDP Protocol
To configure an Ethernet interface
– Example:
• R2(config)#interface fastethernet 0/0
• R2(config-if)#ip address 172.16.1.1 255.255.255.0
• R2(config-if)#no shutdown
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
11
Routing Table and CDP Protocol
When a router only has its interfaces configured & no
other routing protocols are configured then:
– The routing table contains only the directly connected networks
– Only devices on the directly connected networks are reachable
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
12
Routing Table and CDP Protocol
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
13
Routing Table and CDP Protocol
Checking each
route in turn
– The ping
command is
used to check
end to end
connectivity
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
14
Routing Table and CDP Protocol
Purpose of CDP
– A layer 2 cisco proprietary tool used to gather information
about other directly connected Cisco devices.
Concept of neighbors
– 2 types of neighbors:
• Layer 3 neighbors
• Layer 2 neighbors
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
15
Routing Table and CDP Protocol
CDP show commands
– Show cdp neighbors command
• Displays the following information:
– Neighbor device ID
– Local interface
– Holdtime value, in seconds
– Neighbor device capability code
– Neighbor hardware platform
– Neighbor remote port ID
– Show cdp neighbors detail command
• Useful in determining if an IP address configuration error
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
16
Routing Table and CDP Protocol
CDP provides the following information
about each CDP neighbor device:
•Device identifiers - For example, the
configured host name of a switch
•Address list - Up to one Network layer
address for each protocol supported
•Port identifier - The name of the local and
remote port-in the form of an ASCII
character string such as ethernet0
•Capabilities list - For example, whether
this device is a router or a switch
•Platform - The hardware platform of the
device; for example, a Cisco 7200 series
router
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
17
Static Routes with Exit Interfaces
Purpose of a static route
– A manually configured route used when routing from a network
to a stub network
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
18
Static Routes with Exit Interfaces
IP route command
– To configure a static route use the following command: ip route
– Example:
• Router(config)# ip route network-address subnet-mask {ipaddress | exit-interface }
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
19
Static Routes with Exit Interfaces
Static route syntax
– ip route - Static route command
– 172.16.1.0 – Destination network address
– 255.255.255.0 - Subnet mask of destination network
– 172.16.2.2 - Serial 0/0/0 interface IP address on R2, which is
the "next-hop" to this network
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
20
Static Routes with Exit Interfaces
Configuring routes to 2 or more remote networks
– Use the following commands for R1
• 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
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
21
Static Routes with Exit Interfaces
Resolving to an Exit Interface
– Recursive route lookup - Occurs when the router has to perform
multiple lookups in the routing table before forwarding a packet.
A static route that forwards all packets to the next-hop IP address
goes through the following process (reclusive route lookup).
• The router first must match static route’s destination IP
address with the Next hop address.
• The next hop address is then matched to an exit interface.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
22
Static Routes with Exit Interfaces
Configuring a Static route with an Exit Interface
– Static routes configured with an exit interface are more efficient
because the routing
– The routing table can resolve the exit interface in a single
search instead of 2 searches
– Example of syntax require to configure a static route with an
exit interface
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
23
Static Routes with Exit Interfaces
Modifying Static routes
– Existing static routes cannot be modified. The old static route
must be deleted by placing no in front of the ip route
– Example:
• no ip route 192.168.2.0 255.255.255.0 172.16.2.2
– A new static route must be rewritten in the configuration
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
24
Static Routes with Exit Interfaces
Ethernet interfaces and ARP
– If a static route is configured on an Ethernet link and
packet is sent to the next-hop router then…
• The destination MAC address will be the address of the
next hop’s Ethernet interface
• This is found by the router consulting the ARP table
• If an entry isn’t found then an ARP request will be sent out
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
25
Summary and Default Route
Summarizing routes reduces the size of the routing table.
Route summarization is the process of combining a number of
static routes into a single static route.
Multiple static routes
can be summarized into
a single static route if:
•The destination
networks can be
summarized into a
single network address,
and
•The multiple static
routes all use the same
exit-interface or nexthop IP address
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
26
Summary and Default Route
Configuring a summary route
– Step 1: Delete the current static route
– Step 2: Configure the summary static route
– Step 3: Verify the new static route
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
27
Summary and Default Route
Default Static Route
– This is a route that will match all packets. Stub routers that
have a number of static routes all exiting the same interface
are good candidates for a default route.
• Like route summarization this will help reduce the size of
the routing table.
Configuring a default static route
– Similar to configuring a static route. Except that destination IP
address and subnet mask are all zeros.
– Example:
• Router(config)#ip route 0.0.0.0 0.0.0.0 [exit-interface | ipaddress ].
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
28
Static Routes and Packet Forwarding
Troubleshooting a Missing Route
Tools that can be used to isolate routing problems
include:
– Ping - tests end to end connectivity
– Traceroute - used to discover all of the hops (routers) along the
path between 2 points
– Show IP route - used to display routing table & ascertain
forwarding process
– Show ip interface brief - used to show status of router
interfaces
– Show cdp neighbors detail - used to gather configuration
information about directly connected neighbors
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
29
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
30