CCNA Dis3 - Chapter 5 - Routing With A Distance Vector Protocol - PPT (Compatibility Mode)

Chapter 5 Routing witch a Distance Vector Protocol
CCNA Discovery 4.0
Intruduction
Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com
Intruduction
Intruduction
Intruduction
Objectives
Managing Enterprise Networks

Enterprise Networks
Enterprise Networks

Routers forward traffic and prevent broadcasts from clogging the main channels to crucial services. Enterprise networks provide a high level of reliability and services. To ensure this, network professionals: Design networks to provide redundant links to use in case a primary data path fails. Deploy Quality of Service (QoS) to ensure critical data receives priority treatment. Use packet filtering to deny certain types of packets, maximize available bandwidth, and protect the network from attacks.
Enterprise Topologies

Choosing the right physical topology allows a company to expand its networked services without losing reliability and efficiency. Star Topology A star topology provides centralized control of the network. Extended Star
Partial Mesh Full Mesh
Static and Dynamic Routing

Typically, both static and dynamic routes are employed in an enterprise network Static routing addresses specific network needs Depending on the physical topology, a static route can be used to control the traffic flow. Limiting traffic to a single point of entrance/exit creates a stub network.

Static routing provides forwarding services without the overhead associated with most dynamic routing protocols. Static routing provides more security than dynamic routing, because no routing updates are required.
Configuring Static Route
Router(config)#ip route [network-address] [subnet mask] [address of next hop OR exit interface]
Summary route

A floating static route has a higher administrative distance than the route learned from a dynamic routing protocol. For that reason, a floating static route does not display in the routing table To create a floating static route, add an administrative distance value to the end of the ip route command: Router(config)#ip route 192.168.4.0 255.255.255.0 192.168.9.1 200 .
Default Route

The final default route, located on the border router, sends the traffic to the ISP. This route identifies the last stop within the enterprise as the Gateway of Last Resort for packets that cannot be matched.
Distance Vector Routing Protocols
Dynamic routing protocols are classified into two major categories: distance vector protocols and link-state protocols.
Routers running distance vector routing protocols share network information with directly connected neighbors. Distance vector protocols calculate the best route based on the distance from a router to a network. An example of a metric used is hop count, which is the number of routers, or hops, between the router and the destination.
Distance Vector Routing Protocols
Routing Information Protocol (RIP)

RIPv1 does not send subnet mask information in its routing updates and, therefore, does not support VLSM and CIDR. By default, RIPv1 broadcasts its routing updates to all connected routers every 30 seconds. RIPv1 does not support Discontigous network
RIPv2 is a classless routing protocol that supports VLSM and CIDR.
RIPv2 also has the ability to turn off automatic summarization of routes.
RIPv2 shares many of the features found in RIPv1, such as:
Hop-count metric 15-hop maximum TTL equals 16 hops Default 30-second update interval Route poisoning, poison reverse, split horizon, and holddowns to avoid loops Updates using UDP port 520 Administrative distance of 120 Message header containing up to 25 routes without authentication

When a router starts up, each RIP-configured interface sends out a request message. RIP-enabled neighbors send a response message that includes known network entries.

By default, RIPv2 sends and receives only version 2 updates. By default, RIPv1 sends version 1 updates, but receives both versions 1 and 2. So RIPv1 and v2 are not compatible so.next slide.
Compatibility with RIP v1

NewYork interface fastethernet0/0 ip address 192.168.50.129 255.255.255.192 ip rip send version 1 ip rip receive version 1 interface fastethernet0/1 ip address 172.25.150.193 255.255.255.240 ip rip send version 1 2 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
30
RIPv2
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.
Hc vin mng Bach Khoa - Website: www.bkacad.com
Activity
Configuring RIPv2
The basic RIP configuration consists of three commands: Router(config)#router rip Enables the routing protocol Router(config)#version 2 Specifies the version Router(config-router)#network [network address] Identify each directly connected network that should be advertised by RIP
Configuring RIPv2
Propagating a default Routes in RIPv2
Two steps to propagate default route into RIPv2: Create default route in propagator. Implement default-information originate in router mode.
Internet
10.0.0.0/8
.1 .25 .1 e0 207.0.0.0/16 207.1.0.0/16 207.2.0.0/16 207.3.0.0/16 etc.
ISP router rip redistribute static network 10.0.0.0 network 192.168.4.0 version 2 no auto-summary default-information originate ip route 207.0.0.0 255.0.0.0 null0 ip route 0.0.0.0 0.0.0.0 10.0.0.2 etherenet0
static route to 207.0.0.0/8
ISP
s0 s1 .21
192.168.4.24/30
192.168.4.20/30 172.30.200.32/28
Lo2
.26
s0
s0
.22
Lo1
172.30.200.16/28
172.30.2.0/24
Lo0 .1 SantaCruz1 .1 e0
SantaCruz2
.1 e0
Lo0 .1
172.30.110.0/24
172.30.1.0/24
172.30.100.0/24
34
Authentication
Whatever the reason, it is good practice to authenticate routing information transmitted between routers. RIPv2, EIGRP, OSPF, IS-IS, and BGP can be configured to authenticate routing information. This practice ensures routers will only accept routing information from other routers that have been configured with the same password or authentication information. Note: Authentication does not encrypt the routing table.
Hc vin mng Bach Khoa - Website: www.bkacad.com 35
Configuring authentication
Router(config)#key chain Romeo Router(config-keychain)#key 1 Router(config-keychain-key)#key-string Juliet The password must be the same on both routers (Juliet), but the name of the key (Romeo) can be different. Router(config)#interface fastethernet 0/0 Router(config-if)#ip rip authentication key-chain Romeo Router(config-if)#ip rip authentication mode md5 If the command ip rip authentication mode md5 is not added, the interface will use the default clear text authentication. Although clear text authentication may be necessary to communicate with some RIP v2 implementations, for security concerns use the more secure MD5 authentication whenever possible.
RIPv2 redistribution
Planning Redistribution
Locate the boundary router between two routing processes. Determine which routing process is the core or backbone process Determine which routing process is the edge or migration process Select a method for injecting the required edge protocol routes into the core.
Configuring Redistribution into RIP
Use this command to redistribute routes into RIP: Router(config-router)# redistribute protocol [process-id] [match route-type] [metric metric-value] [route-map map-tag]
RtrA(config)# router rip RtrA(config-router)# redistribute ospf ? <1-65535> Process ID
RtrA(config-router)# redistribute ospf 1 ? match metric route-map Redistribution of OSPF routes Metric for redistributed routes Route map reference
Default metric is infinity.

<cr>
38
The redistribute command parameters for RIP

Parameter Description
Source protocol from which routes are being redistributed. This value is an AS number. For OSPF, this value is an OSPF process ID. (Optional) Command parameter used for redistributing OSPF routes into another routing protocol. For OSPF, the criterion by which OSPF routes are redistributed into other routing domains. (Optional) Parameter used to specify the RIP seed metric for the redistributed route. When you are redistributing into RIP, this value is not specified and no value is specified using the default-metric router configuration command, then the default metric is 0, which is interpreted as infinity, and routes will not be redistributed. The metric for RIP is the hop count. (Optional) Identifier of a configured route map to be interrogated to filter the importation of routes from this source routing protocol to the current routing protocol.
39
protocol process-id
match route-type
metric metric-value
route-map map-tag
Problem with RIP
Unlike RIPv1, with RIPv2 the automatic summarization feature can be disabled. Router(config-router)#no auto-summary
40
Problem with RIP

qThe passive-interface command, issued in interface mode, disables routing updates on specified interfaces. qRouter(config-router)#passive-interfaceinterface-type interfacenumber
41
Problem with RIP

Routing Loop
42
Problem with RIP

Count to Infinity
43
Problem with RIP
Routing loops negatively affect network performance. RIP contains several features designed to combat this impact.: Poisoned reverse Split horizon Holddown timer Triggered updates
44
Problem with RIP
Split Horizon Split horizon dictates that a router receiving routing information on an interface cannot send an update about that same network back out the same interface.
45
Problem with RIP
Holddown timer The holddown timer refuses to accept route updates with a higher metric to the same destination network for a period after a route goes down
46
Verification and Troubleshooting Commands
There are several ways to verify and troubleshoot RIPv2. Many of the same commands used for RIPv2 can be used to verify and troubleshoot other routing protocols. It is always best to begin with the basics: 1. Make sure all of the links (interfaces) are up and operational. 2. Check the cabling. 3. Check to make sure you have the correct IP address and subnet mask on each interface. 4. Remove any unnecessary configuration commands that are no longer necessary or have been replaced by other commands.
Router#show ip route C C R R C C R C R R 172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks 172.30.200.32/28 is directly connected, Loopback2 172.30.200.16/28 is directly connected, Loopback1 172.30.2.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0 172.30.1.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0 172.30.100.0/24 is directly connected, Ethernet0 172.30.110.0/24 is directly connected, Loopback0 192.168.4.0/30 is subnetted, 2 subnets 192.168.4.24 [120/1] via 192.168.4.21, 00:00:21, Serial0 192.168.4.20 is directly connected, Serial0 10.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0 207.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0
Supernet, classless routing protcols will route supernets (CIDR)

49
50
51

Router(config)# line console 0 Router(config-line)# logging synchronous Router#debug ip rip RIP protocol debugging is on Router#01:23:34: RIP: received v2 update from 192.168.4.22 on Serial1 01:23:34: 172.30.100.0/24 -> 0.0.0.0 in 1 hops 01:23:34: 172.30.110.0/24 -> 0.0.0.0 in 1 hops Includes mask Router# 01:23:38: RIP: received v2 update from 192.168.4.26 on Serial0 01:23:38: 172.30.2.0/24 -> 0.0.0.0 in 1 hops 01:23:38: 172.30.1.0/24 -> 0.0.0.0 in 1 hops multicast Router# 01:24:31: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.0.1) 01:24:31: 172.30.2.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 172.30.1.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 172.30.100.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 172.30.110.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 192.168.4.24/30 -> 0.0.0.0, metric 1, tag 0 01:24:31: 192.168.4.20/30 -> 0.0.0.0, metric 1, tag 0 <text omitted>
53
54

Router# show ip rip database 172.19.0.0/16 auto-summary 172.19.64.0/24 directly connected, Ethernet0 172.19.65.0/24 [1] via 172.19.70.36, 00:00:17, Serial1 [2] via 172.19.67.38, 00:00:25, Serial0 172.19.67.0/24 directly connected, Serial0 172.19.67.38/32 directly connected, Serial0 172.19.70.0/24 directly connected, Serial1 172.19.86.0/24[1] via 172.19.67.38, 00:00:25, Serial0 [1] via 172.19.70.36, 00:00:17, Serial1
The show ip rip database command to check summary address entries in the RIP database. These entries will appear in the database if there are only relevant child or specific routes being summarized. When the last child route for a summary address becomes invalid, the summary address is also removed from the routing table.
Common RIPv2 issues
The network statement does two things: It enables the routing protocol to send and receive updates on any local interfaces that belong to that network. It includes that network in its routing updates to its neighboring routers.
Limitations of RIP
Additionally, the RIP limitation of 15 hops can mark distant networks as unreachable.
Routing using the EIGRP protocol
Enhanced Interior Gateway Routing Protocol (EIGRP)
Cisco developed EIGRP as a proprietary distance vector routing protocol.
The two main goals of EIGRP are to provide a loop-free routing environment and rapid convergence. The metric used is a composite metric that primarily considers bandwidth and delay. The Diffusing Update Algorithm (DUAL) used by EIGRP guarantees loop-free operation while it calculates routes.
EIGRP is a good choice for complex enterprise networks that are composed primarily of Cisco routers. Its maximum hop count of 224 supports large networks. EIGRP does not send complete tables in its updates. EIGRP multicasts partial updates about specific changes to only those routers that need the information, not to all routers in the area. Instead of sending periodic routing updates, EIGRP sends small hello packets to maintain knowledge of its neighbors.
Activity
EIGRP Terminology and Tables
Neighbor table
Neighbor table The neighbor table lists information about directly connected neighbor routers. If a hello packet is not received within the hold time, the timer expires and DUAL recalculates the topology.
Topology Table The topology table lists all routes learned from each EIGRP neighbor.
The Diffusing Update Algorithm (DUAL) is used to prevent looping: Successor. Feasible Distance (FD). Feasible Successor (FS). Reported Distance (RD) or Advertised Distance (AD). Feasible Condition or Feasibility Condition (FC).
DUAL Concepts
Successor is a neighboring router that is used for packet forwarding and is the least-cost route to the destination network. Feasible distance The lowest calculated metric along a path to a destination network.
DUAL Concepts
Feasible Successor This is a loop free backup route to same destination as successor route.
67
DUAL Concepts
Reported distance (RD) The metric that a router reports to a neighbor about its own cost to that network. The reported distance or advertised distance is simply an EIGRP neighbor's feasible distance to the same destination network. Feasibility Condition (FC) Met when a neighbors RD is less than the local routers FD to the same destination network.
68
Routing table The routing table displays only the best paths called the successor routes. EIGRP displays information about routes in two ways: The routing table designates routes learned through EIGRP with a D. EIGRP tags dynamic or static routes learned from other routing protocols or from outside the EIGRP network as D EX or external, because they did not originate from EIGRP routers within the same AS.
Routing table R3s Routing table
Activity
EIGRP Neighbors and Adjacencies
Before EIGRP can exchange packets between routers, it must first discover its neighbors. EIGRP routers use hello packets to discover neighbors and establish adjacencies with neighbor routers. By default, hello packets are multicast every 5 seconds on links greater than a T1 and every 60 seconds on T1 or slower links. On IP networks, the multicast address is 224.0.0.10. The hello packet contains information about the router interfaces and the interface addresses. The hold time is the period that EIGRP waits to receive a hello packet.
The hold time is three times the duration of the hello interval. When the hold time expires and EIGRP declares the route as down, DUAL re-evaluates the topology and refreshes the routing table.
When a neighbor adjacency is established, EIGRP uses various types of packets to exchange and update routing table information.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7

Cisco designed lReliable Transport Protoco (RTP) as a proprietary Layer 4 protocol. Each Network Layer protocol works through a Protocol Dependent Module, or PDM,
Activity
EIGRP Metrics and Convergence
EIGRP uses a composite metric value to determine the best path to a destination. Bandwidth Delay Reliability Load Maximum Transmission Unit (MTU) is another value included in routing updates, but is not a routing metric.
EIGRP Composite Metric & the K Values EIGRP uses the following values in its composite metric Bandwidth, delay, reliability, and load. The composite metric used by EIGRP: Formula used has values K1 K5. K1 & K3 = 1. All other K values = 0.
Use the show ip protocols command to verify the K values
87

Use the show interfaces command to view metrics EIGRP Metrics Bandwidth EIGRP
uses a static bandwidth to calculate metric. Most serial interfaces use a default bandwidth value of 1.544Mbps (T1). Modifying the bandwidth value does not change the actual bandwidth of the link.
88

Delay Delay is the defined as the measure of time it takes for a packet to traverse a route It is a static value based on link type to which interface is connected.
89
EIGRP Metric Calculation
Reliability (not a default EIGRP metric) A measure of the likelihood that a link will fail. Measure dynamically & expressed as a fraction of 255 the higher the fraction the better the reliability. Load (not a default EIGRP metric) A number that reflects how much traffic is using a link. Number is determined dynamically and is expressed as a fraction of 255. The lower the fraction the less the load on the link because it indicates less load on the link.

Using the Bandwidth Command Modifying the interface bandwidth Use the bandwidth command Command: Router(config-if)#bandwidth kilobits Use the interface command no bandwidth to restore the default value. Verifying bandwidth Use the show interface command Note bandwidth command does not change the links physical bandwidth.
The EIGRP topology table uses metrics to maintain values for feasible distance (FD) and advertised distance (AD) , or reported distance (RD).
Activity
Activity
Activity
Configuring EIGRP
Configuring EIGRP
Add eigrp log-neighbor-changes command to view changes in neighbor adjacencies. This feature helps the administrator monitor the stability of the EIGRP network.
Configuring EIGRP
EIGRP authentication requires the use of a pre-shared key.
Configuring EIGRP
EIGRP Route Summarization
Like RIP, EIGRP automatically summarizes subnetted networks on the classful boundary. EIGRP installs a Null0 summary route in the routing table for each parent route. The Null0 interface indicates that this is not an actual path, but a summary for advertising purposes. Use the no auto-summary command to disable the default summarization.

Manual summarization provides a more precise control of EIGRP routes. A manually summarized route appears in the routing table as an EIGRP route sourced from a logical, not physical, interface: D 192.168.0.0/22 is a summary, Null0
Verifying EIGRP Operation
debug eigrp packet
displays transmission and receipt of all EIGRP packets
debug eigrp fsm
displays feasible successor activity to determine whether routes are discovered, installed, or deleted by EIGRP
Issues and Limitation of EIGRP
Does not work in a multi-vendor environment because it is a Cisco proprietary protocol Works best with a flat network design Must share the same autonomous system among routers and cannot be subdivided into groups. Can create very large routing tables, which requires large update packets and large amounts of bandwidth. Uses more memory and processor power than RIP Works inefficiently when left on the default settings Requires administrators with advanced technical knowledge of the protocol and the network
Summary
Static route Dynamic routing RIP version 1 & 2 EIGRP protocol

CCNA Dis3 - Chapter 5 - Routing With A Distance Vector Protocol - PPT (Compatibility Mode)

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CCNA Dis3 - Chapter 5 - Routing With A Distance Vector Protocol - PPT (Compatibility Mode)

Hochgeladen von

Copyright:

Verfügbare Formate

Chapter 5 Routing witch a Distance Vector Protocol

CCNA Discovery 4.0

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Managing Enterprise Networks

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Partial Mesh Full Mesh

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Static and Dynamic Routing

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Static and Dynamic Routing

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Static and Dynamic Routing

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Static and Dynamic Routing

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Configuring Static Route

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Configuring Static Route

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Configuring Static Route

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Configuring Static Route

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Configuring Static Route

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Distance Vector Routing Protocols

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Distance Vector Routing Protocols

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Routing Information Protocol (RIP)

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Routing Information Protocol (RIP)

RIPv2 is a classless routing protocol that supports VLSM and CIDR.

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Routing Information Protocol (RIP)

RIPv2 shares many of the features found in RIPv1, such as:

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Routing Information Protocol (RIP)

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Routing Information Protocol (RIP)

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Compatibility with RIP v1

Hc vin mng Bach Khoa - Website: www.bkacad.com

Routing Information Protocol (RIP)

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Hc vin cng ngh thng tin Bach Khoa - Website: www.bkacad.com

Propagating a default Routes in RIPv2

static route to 207.0.0.0/8

Hc vin mng Bach Khoa - Website: www.bkacad.com

Configuring Redistribution into RIP

Default metric is infinity.

The redistribute command parameters for RIP

Problem with RIP