sikandar ccnp notes

[email protected] [email protected]

91 - 9985048840

Page 1 of 182

CCNP ROUTE 642-902

Chapter 1: Planning for Complex Networks Chapter 2: EIGRP Chapter 3: OSPF Chapter 4: Optimizing Routing Chapter 5: Path Control Chapter 6: BGP and Internet Connectivity Chapter 7: Branch Office Connectivity Chapter 8: Mobile Worker Connectivity Chapter 9: IPv6 Introduction Understanding Routing Protocols Cisco routers support multiple routing protocols, but the ROUTE exam covers only EIGRP, OSPF, and BGP Static Routing Manually configured by Administrator Administrative distance is 0 or 1 Destination network should be known Routing based on next hop IP address or exit interface Secure and fast Static Default Route Static default route will be used for unknown destination or for all destination. It is used for Internet It is last preferred route in routing table. It can be also used on Stub router Dynamic Routing Protocol Dynamic routing protocols, exchange routing information with the neighbors and build the routing table automatically Administrator need to advertise only the directly connected networks Any changes in the network topology are automatically updated Types of Dynamic Routing Protocol Distance Vector Protocol Link-State Protocol Advance or Hybrid Protocol


91 - 9985048840

Page 2 of 182

Distance Vector Protocol

Link State Protocol

Hybrid Protocol

Works with Bellman Ford algorithm Periodic updates Classful routing protocol Full Routing tables are exchanged Updates are through broadcast Example: RIP 1, , IGRP

Works with Dijkstra algorithm Link state updates Classless routing protocol Missing routes are exchanged Updates are through multicast Example : OSPF, IS-IS

Works with DUAL algorithm Link state updates Classless routing protocol Missing routes are exchanged Updates are through multicast Example : EIGRP Also called as Advance Distance vector Protocol

Administrative distance: It is the trustworthiness of the routing information. Lesser the Administrative distance, higher the preference.

Routing Protocols and Their Default Administrative Distance

Information Source AD Connected 0 Static 1 External BGP (Border Gateway Protocol) 20 Internal EIGRP (Enhanced IGRP) 90 IGRP (Internet Gateway Routing Protocol) 100 OSPF (Open Shortest Path First) 110 IS-IS (Intermediate System to Intermediate System) 115 RIP (Routing Information Protocol) 120 ODR (On Demand Routing) 160 External EIGRP 170 Internal BGP 200 Unknown 255 Building the Routing Table The router builds a routing table by ruling out invalid routes and considering the remaining advertisements. The procedure is 1. For each route received, verify the next hop. If invalid, discard the route. 2. If multiple identical, valid routes are received by a routing protocol, choose the lowest metric.


91 - 9985048840

Page 3 of 182

3. Routes are identical if they advertise the same prefix and mask, so 192.168.0.0/16 and 92.168.0.0/24 are separate paths and are each placed into the routing table. 4. If more than one specific valid route is advertised by different routing protocols, choose the path with the lowest AD. Comparison of Routing Protocols

SUBNETTING FLSM All the subnet have same subnet mask VLSM All subnet have different subnet mask

Classfull Routing Protocol Routing protocol which doesnt carry subnet mask in Routing updates. Eg. RIP, IGRP. Classless Routing Protocol Routing Protocols which carry subnet mask information in routing update Eg. RIPv2, EIGRP, OSPF, ISIS, BGPv4 SUMMARIZATION/CIDR/SUPERNETTING

It is the process of combining smaller networks in to single large sub network (Combining the contagious address into one and send to neighbor.) It helps in reducing the size of routing table.

Advantages Minimizing the routing table. Less use of resources like memory, processor, bandwidth. Two Type of Summarization Auto summary Manual summary

Auto Summary


91 - 9985048840

Page 4 of 182

Summarizes to a default class full boundary A /8 B /16 C /24

Class full routing protocol does auto summary by default and it cant be turn off Routing protocol like RIPv2, EIGRP, BGPv4 support auto summary Routing protocol like OSPF and ISIS doesnt support auto summary

Disadvantages of Auto-summary: Can create Problems if the network is in discontiguous Subnets. Not always applicable

To enable or disable auto summary Router(config-router)# [no] auto-summary

Manual summary Administrator manually configures Summarization It is supported by all classless routing protocols

Example of Manual summary : Example 1 Summarize the following addresses 10.1.0.0/24 10.1.2.0/24 10.1.3.0/24 10.1.4.0/24 10.1.5.0/24 10.1.6.0/24 Steps for calculating Manual summary : 1) WRITE THE BINARY OF FIRST and the last number 2) Divide between the common and un-common ( 0 0 or 1- 1 are common) 3) Convert right side values of the first number in to zeros ( change in to decimal) 4) count the left side bits (to find the / value) some examples for method of converting to binary

128 64 32 16 8 4 2 1 6 0 0 0 0 0 1 1 0 25 0 0 0 1 1 0 0 1


91 - 9985048840

Page 5 of 182

29 0 0 0 1 1 1 0 1 1 0 0 0 0 0 0 0 1 10.1.0.0/24 written as 10. 1. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10.1.6.0/24 written as 10. 1. 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 3) Convert right side values of the first number in to zeros ( change in to decimal) 10. 1. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Change in to decimal the above answer 10.1.0.0 count the left side bits (to find the / value) 10. 1. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 bits 8 bits 5 bits 10.1.0.0 /21 So the summarization address is 10.1.0.0 /21 EXAMPLE 2 Summarize the following addresses 172.16.25.0/24 172.16.26.0/24


91 - 9985048840

Page 6 of 182

172.16.27.0/24 172.16.28.0/24 172.16.29.0/24 WRITE THE BINARY OF FIRST and the last number Divide between the common and un-common Convert right side values of the first number in to zeros ( change in to decimal) count the left side bits (for / value)

172.16.25.0/24 172.16. 0 0 0 1 1 0 0 1 00000000 172.16.29.0/24 172.16. 0 0 0 1 1 1 0 1 00000000 Convert right side values of the first number in to zeros ( change in to decimal)

172.16. 0 0 0 1 1 0 0 0 00000000 count the left side bits (for / value)

172.16.24.0/21 ====================================================================== Planning a Routing Implementation It is critical to take a structured approach to planning a routing implementation and to document thoroughly once you are done. Taking an ad-hoc approach could lead to network instability, suboptimal routing, or scalability problems. Four commonly used models include

Cisco Lifestyle Services: Uses the PPDIOO model (Prepare, Plan, Design, Implement, Operate, and Optimize.) Network engineers at the CCNP level are involved with the implementation planning during the Design phase, and the Implementation itself during the Implement phase. IT Infrastructure Library (ITIL): Emphasizes business requirements and processes as they relate to IT. Implementation and implementation planning are part of its best practices. Fault, Configuration, Accounting, Performance, and Security (FCAPS): Has five network management categories. Implementation and implementation planning are under the Configuration management category. Telecommunications Management Network (TMN): Based on the FCAPS model. Implementation and implementation planning are one of its building blocks. Each approach includes identifying requirements, creating an implementation plan, implementing the changes, verifying your work, and then documenting it.


91 - 9985048840

Page 7 of 182

Creating an Implementation Plan To create an implementation plan you need to know what the network looks like now, and what it should look like when you are done. This involves gathering information about the current network parameters such as IP addressing, physical connectivity, routing configuration, and equipment. Compare the current state to what is required. Be sure to include any site-specific requirements and any dependencies on the existing network. An implementation plan includes most of the following, some of which might be site-specific: 1. A checklist of tasks to be done 2. Tools and resources needed 3. The schedule of work, coordinated with all needed resources 4. Device configurations 5. Verification processes and tests Creating Implementation Documentation Documentation should be kept up-to-date, accurate, and accessible. It includes network information, tools and resources used, implementation tasks, verification methods, device configurations, performance measurements, and possibly screen shots or pictures.


91 - 9985048840

Page 8 of 182

HOW TO INSTALL AND USE GNS3 Install GNS3 Copy IOS images to a specific folder Set the path

For PRO DIR For IMAGES

o

TEST THE DYNAMIPS


91 - 9985048840

Page 9 of 182

Set the path of theIOS images to be used


91 - 9985048840

Page 10 of 182

yo Design the topology and add the specific cards on the module required for connections. Configure the routers to add the specific modules ( and cards required) for connections to be made.


91 - 9985048840

Page 11 of 182


91 - 9985048840

Page 12 of 182

Design the topology

Start the devices


91 - 9985048840

Page 13 of 182

Calculate the IDLE PC value to reduce the CPU utilization o ( prefered values will be seen as asterisk *****

Console the routers


91 - 9985048840

Page 14 of 182

Assign the basic configurations according to the lab setup ( you will find in coming pages) Save configs ( WRITE command)


91 - 9985048840

Page 15 of 182

Export the configs to a folder :

FILE SAVE the topology for future labs Once the topology designed and configured with the basic configs , saved in can be used in the future labs all relating to CCNP RS module in the coming sections. The entire labs in the every topic is done mostly based on the same topology


91 - 9985048840

Page 16 of 182

LAB DEFAULT SETUP DIAGRAM :

BASIC CONFIGS ACCORDING TO THE LAB REQUIREMENT

R1 enable conf t hostname R1 no ip domain-lookup int fa0/0 ip add 10.1.1.1 255.0.0.0 no shut no keepalive int s1/0 ip add 1.1.1.1 255.0.0.0 no sh


91 - 9985048840

Page 17 of 182

int s1/1 ip add 4.4.4.2 255.0.0.0 no sh int loop 0 ip add 11.0.0.1 255.255.255.0 int loop 1 ip add 11.0.1.1 255.255.255.0 int loop 2 ip add 11.0.2.1 255.255.255.0 int loop 3 ip add 11.0.3.1 255.255.255.0 do write =============================================== R2 enable conf t hostname R2 no ip domain-lookup int fa0/0 ip add 20.1.1.1 255.0.0.0 no shut no keepalive int s1/0 ip add 1.1.1.2 255.0.0.0 no sh int s1/1 ip add 2.2.2.1 255.0.0.0 no sh int loop 0 ip add 12.0.0.1 255.255.255.0 int loop 1 ip add 12.0.1.1 255.255.255.0 int loop 2


91 - 9985048840

Page 18 of 182

ip add 12.0.2.1 255.255.255.0 int loop 3 ip add 12.0.3.1 255.255.255.0 do write ================================= R3 enable conf t hostname R3 no ip domain-lookup int fa0/0 ip add 30.1.1.1 255.0.0.0 no shut no keepalive exit int s1/0 ip add 2.2.2.2 255.0.0.0 no sh exit int s1/1 ip add 3.3.3.1 255.0.0.0 no sh exit int loop 0 ip add 13.0.0.1 255.255.255.0 int loop 1 ip add 13.0.1.1 255.255.255.0 int loop 2 ip add 13.0.2.1 255.255.255.0 int loop 3 ip add 13.0.3.1 255.255.255.0 do write =============================================


91 - 9985048840

Page 19 of 182

R4 enable conf t hostname R4 no ip domain-lookup int fa0/0 ip add 40.1.1.1 255.0.0.0 no shut no keepalive int s1/0 ip add 3.3.3.2 255.0.0.0 no sh exit int s1/1 ip add 4.4.4.1 255.0.0.0 no sh int loop 0 ip add 14.0.0.1 255.255.255.0 int loop 1 ip add 14.0.1.1 255.255.255.0 int loop 2 ip add 14.0.2.1 255.255.255.0 int loop 3 ip add 14.0.3.1 255.255.255.0 do write ==============================================


91 - 9985048840

Page 20 of 182

EIGRP Enhanced Interior Gateway Routing Protocol (EIGRP) The following are some features of EIGRP: Cisco proprietary advanced distance vector classless routing protocol. Fast convergence. Support for VLSM. Partial updates conserve network bandwidth. Support for IP, AppleTalk, and IPX. Runs directly over IP, using protocol number 88. Support for all Layer 2 (data link layer) protocols and topologies. Sophisticated metric that supports load-balancing across unequal-cost paths . Use of multicast (and unicast where appropriate) instead of broadcasts. Support for authentication. uses a complex metric based on bandwidth and delay Manual summarization at any interface. Uses multicast 224.0.0.10.

EIGRPs function is controlled by four key technologies: 1. Neighbor discovery and maintenance: Periodic hello messages 2. The Reliable Transport Protocol (RTP): Controls sending, tracking, and acknowledging EIGRP messages 3. Diffusing Update Algorithm (DUAL): Determines the best loop-free route 4. Protocol-independent modules (PDM): Modules are plug-ins for IP, IPX, and AppleTalk versions of EIGRP EIGRP uses three tables:

The neighbor table is built from EIGRP hellos and used for reliable delivery. The topology table contains EIGRP routing information for best paths and loop-free alternatives. EIGRP places best routes from its topology table into the common routing table.

Packet Types EIGRP uses five packet types Hello: Identifies neighbors and serves as a keep alive mechanism Update: Reliably sends route information Query: Reliably requests specific route information Reply: Reliably responds to a query ACK: Acknowledgment

Neighbor Discovery and Route Exchange When EIGRP first starts, it uses hellos to build a neighbor table. Neighbors are directly attached routers that have a matching AS number and k values. (The timers dont have to agree.) The process of neighbor discovery and route exchange between two EIGRP routers is as follows:


91 - 9985048840

Page 21 of 182

Step 1. Router A sends out a hello. Step 2. Router B sends back a hello and an update. The update contains routing information. Step 3. Router A acknowledges the update. Step 4. Router A sends its update. Step 5. Router B acknowledges. Initial Route Discovery

When two routers are EIGRP neighbors, they use hellos between them as keepalives. Additional route information is sent only if a route is lost or a new route is discovered. A neighbor is considered lost if no hello is received within three hello periods (called the hold time). The default hello/hold timers are as follows: 5 seconds/15 seconds for multipoint circuits with bandwidth greater than T1 and for point-to-point media 60 seconds/180 seconds for multipoint circuits with bandwidth less than or equal to T1

EIGRP METRIC CALCULATION

EIGRP Metric = [K1 * BW + ((K2 * BW) / (256 load)) + K3 * delay]


91 - 9985048840

Page 22 of 182

Formula with default K values (K1 = 1, K2 = 0, K3 = 1, K4 = 0, K5 = 0) EIGRP Metric BW= (107/lowest Bandwidth in kbps)*256 Delay= (sum of total delay/10)*256 By default, EIGRP metric: Metric = bandwidth (slowest link) + delay (sum of delays)

A --B --C -- D Least bandwidth 64 kbps Total delay 6,000 A --X --Y --Z --D Least bandwidth 256 kbps Total delay 8,000 Delay is the sum of all the delays of the links along the paths:

Delay = [delay in tens of microseconds] x 256 Bandwidth is the lowest bandwidth of the links along the paths:

Bandwidth = [10,000,000 / (bandwidth in kbps)] x 256 DUAL Terminology

Selects lowest-cost, loop-free paths to each destination AD = cost between the next-hop router and the destination FD = cost from local router = AD of next-hop router + cost between the local router and the next-hop router Lowest-cost = lowest FD (Current) successor = next-hop router with lowest-cost, loop free path Feasible successor = backup router with loop-free path

AD of feasible successor must be less than FD of current successor route Feasible Successor= Second best AD < FD of Successor

Planning an EIGRP Implementation When planning an EIGRP implementation, gather the following information:

Current network setup and future requirements: Document the IP addressing used and the network topology, including links types, bandwidth, and utilization. A good IP addressing design allows summarization at various points in the network.


91 - 9985048840

Page 23 of 182

Network design: Although EIGRP does not require a hierarchical network design, it can perform more efficiently within that type of network. Plans for EIGRP scaling options: These would include summarization, stub areas, and changes in interface metrics to improve bandwidth utilization. Your final implementation plan needs to include detailed parameters such as the exact topology, IP networks to be advertised, EIGRP AS number, lists of routers to run EIGRP, and any nondefault metrics to be used. It needs to list implementation tasks for each router in the network. Finally it needs to provide verification tasks for each router such as verifying neighbors, IP routing tables, EIGRP topology tables, and network connectivity

DUAL Stuck In Active After the router has chosen a path to a network, it is passive for that route. If a successor path is lost and no feasible successor is identified, the router sends out queries on all interfaces in an attempt to identify an alternate path. It is active for that route. No successor can be chosen until the router receives a reply to all queries. If a reply is missing for 3 minutes, the router becomes stuck in active (SIA). In that case, it resets the neighbor relationship with the neighbor that did not reply. Three common causes for SIA routes are CPU or memory usage is so high on the neighbor that it cannot process the query or reply. The link between the routers drops packets. Enough packets get through to maintain the neighbor relationship, but some queries or replies are dropped. Unidirectional link, so the router never receives packets from its neighbor.

To enable EIGRP as the IP routing protocol Router(config)# router EIGRP

Identifies attached networks participating in EIGRP.

Router(config-router)#network network-id [wildcard-mask] Defining the interfaces bandwidth for the purposes of sending routing update traffic

Router(config) # interface serial 0/0 Router(config-if)# bandwidth Configuring EIGRP for IP


91 - 9985048840

Page 24 of 182

Using the Wildcard Mask in EIGRP

Verifying EIGRP

R1#show ip EIGRP neighbors R1#show ip route EIGRP R1#show ip protocols R1#show ip EIGRP interfaces

EIGRP Route Summarization: Automatic


91 - 9985048840

Page 25 of 182

Purpose: Smaller routing tables, smaller updates Automatic summarization:

On major network boundaries, subnetworks are summarized to a single classful (major) network. Automatic summarization occurs by default.

EIGRP Route Summarization: Manual Manual summarization has the following characteristics:

Summarization is configurable on a per-interface basis in any router within a network. When summarization is configured on an interface, the router immediately creates a route pointing to null0. When the last specific route of the summary goes away, the summary is deleted. The minimum metric of the specific routes is used as the metric of the summary route.

Turns off automatic summarization for the EIGRP process Router(config-router)#no auto-summary To Creates a summary address that this interface will generate. Router(config-if)# ip summary-address EIGRP Manually Summarizing EIGRP Routes


91 - 9985048840

Page 26 of 182

EIGRP Load Balancing Routes with lowest equal metric are installed in the routing table (equal-cost load balancing) There can be up to sixteen entries in the routing table for the same destination: The number of entries is configurable The default is four EIGRP Unequal-Cost Load Balancing Allows the router to include routes with a metric smaller than the multiplier value times the metric of successor

Variance is configured for unequal cost load balancing Variance is the multiplier to FD of successor Default is 1(equal cost load balancing) Router(config-router)# variance


91 - 9985048840

Page 27 of 182

Router E chooses router C to get to network Z, because it has lowest FD of 20. With a variance of 2, router E chooses router B to get to network Z (20 + 10 = 30) < [2 * (FD) = 40]. Router D is never considered to get to network Z (because 25 > 20).

EIGRP BANDWIDTH UTILIZATION EIGRP uses up to 50% of bandwidth by default; this bandwidth utilization can be changed -The command to change the percentage of bandwidth used by EIGRP is Router(config-if)#ip bandwidth-percent EIGRP CONFIGURING THE IP DEFAULT-NETWORK COMMAND FOR EIGRP

CONFIGURING EIGRP AUTHENTICATION


91 - 9985048840

Page 28 of 182

Many routing protocols support authentication such that a router authenticates the source of each routing update packet that it receives. Simple password authentication is supported by:

IS-IS OSPF RIPv2

MD5 authentication is supported by: OSPF RIPv2 BGP EIGRP

Simple Password vs. MD5 Authentication Simple password authentication:

Router sends packet and key. Neighbor checks whether key matches its key. Process not secure.

MD5 authentication: Configure a key (password) and key ID; router generates a message digest, or hash, of the key, key ID and message. Message digest is sent with packet; key is not sent. Process OS secure.

EIGRP MD5 Authentication EIGRP supports MD5 authentication. Router generates and checks every EIGRP packet. Router authenticates the source of each routing update packet that it receives. Configure a key (password) and key ID; each participating neighbor must have same key configured. Router generates a message digest, or hash, of the key, key ID, and message. EIGRP allows keys to be managed using key chains. Specify key ID (number), key, and lifetime of key. First valid activated key, in order of key numbers, is used.

To implement EIGRP authentication, first create a plan:

Look at the current configuration to determine the AS number and interfaces where it will be configured. Decide the authentication type. (For EIGRP this must be MD5.) Decide the key strings, and how many keys will be used. Optionally decide the key lifetimes.

To configure the router for EIGRP authentication, follow these steps: Step 1. Configure a key chain to group the keys. Step 2. Configure one or more keys within that key chain. The router checks all inbound packets against the list of keys and uses the first valid one it finds. Step 3. Configure the password or authentication string for that key. Repeat Steps 2 and 3 to add more keys if desired.


91 - 9985048840

Page 29 of 182

Step 4. Optionally configure a lifetime for the keys within that key chain. If you do this, be sure that the time is synchronized between the two routers. Step 5. Enable authentication and assign a key chain to an interface. Step 6. Designate MD5 as the type of authentication. To Enters configuration mode for the keychain

Router(config)# key chain < name-of-chain> Identifies key and enters configuration mode for the keyid

Router(config-keychain)# key Identifies key string (password)

Router(config-keychain-key)# key-string To Specifies MD5 authentication for EIGRP packets

Router(config-if)# ip authentication mode EIGRP md5 Enables authentication of EIGRP packets using key in the keychain

Router(config-if)#ip authentication key-chain EIGRP < AS no > Verifying MD5 Authentication R1#show ip EIGRP neighbors R1#debug EIGRP packets R1#show key chain Example: Configuring EIGRP Authentication Router(config)# key chain RTR_Auth Router(config-keychain)# key 1 Router(config-keychain-key)# key-string mykey Router(config-keychain-key)# send-lifetime 10:15:00 300 Router(config-keychain-key)# accept-lifetime 10:00:00 10:05:00 ! Router(config)# interface s1/0 Router(config-if)# ip authentication mode EIGRP 10 md5 Router(config-if)# ip authentication key-chain EIGRP 10 RTR_Auth Verifying MD5 Authentication R1#show ip EIGRP neighbors R1#debug EIGRP packets R1#show key chain

Customizing the EIGRP Configuration EIGRP Scalability Four factors influence EIGRPs scalability:


91 - 9985048840

Page 30 of 182

1. The number of routes that must be exchanged 2. The number of routers that must know of a topology change 3. The number of alternate routes to a network 4. The number of hops from one end of the network to the other (topology depth)

To improve scalability, summarize routes when possible, try to have a network depth of no more than seven hops, and limit the scope of EIGRP queries. EIGRP Stub

Stub routing is one way to limit queries. A stub router is one that is connected to no more than two neighbors and should never be a transit router. The EIGRP stub routing feature improves network stability, reduces resource utilization, and simplifies remote router (spoke) configuration. Stub routing is commonly used in a hub-and-spoke topology. A stub router sends a special peer information packet to all neighboring routers to report its status as a stub router. A neighbor that receives a packet informing it of the stub status does not query the stub router for any routes.

Configuring EIGRP Stub Router(config-router)# EIGRP stub [receive-only|connected|static|summary]

receive-only: Prevents the stub from sending any type of route. connected: Permits stub to send connected routes (may still need to redistribute). static: Permits stub to send static routes (must still redistribute). summary: Permits stub to send summary routes. Default is connected and summary.

Active Process Enhancement


91 - 9985048840

Page 31 of 182

The Active Process Enhancement enables routers to use SIA-Queries and SIA-Replies to prevent the loss of a neighbor unnecessarily during SIA conditions. A router sends its neighbor a SIA-Query after no reply to a normal query. If the neighbor responds with a SIA-Reply, the router does not terminate the neighbor relationship after 3 minutes, because it knows the neighbor is available. Graceful Shutdown Graceful shutdown is another feature that speeds network convergence. Whenever the EIGRP process is shut down, the router sends a goodbye message to its neighbors. Ironically, the goodbye message is sent in a hello packet. The neighbors can then immediately recalculate any paths that used the router as the next hop, rather than waiting for the hold timer to expire. Passive Interface The passive-interface command prevents either routing updates or hello messages from being sent out an interface. RIP does not send updates when it enabled; EIGRP and OSPF do not send hellos, and thus they dont discover neighbors or form an adjacency out that interface. To disable the protocol on one interface, use the routing protocol configuration command passive-interface interface. To turn off the protocol on all interfaces, use passive-interface default. You can then use no passive-interface interface for the ones that should run the protocol, as shown here: Router(config)# router EIGRP 7 Router(config-router)# passive-interface default Router(config-router)# no passive-interface s1/0 Unicast Neighbors EIGRP usually uses a multicast to IP address 224.0.0.10 for its messages. You can configure it to use a unicast address instead with the routing protocol configuration command neighbor ip-address. The IP address must be in the same subnet as one of the routers own interfaces.


91 - 9985048840

Page 32 of 182

Summary

EIGRP capabilities include fast convergence and support for VLSM, partial updates, and multiple network layer protocols. EIGRP key technologies are neighbor discovery/recovery, RTP, DUAL finite-state machine, and PDMs. EIGRP uses three tables: neighbor table, topology table, and routing table. The routing table contains the best route to each destination, called the successor route. A feasible successor route is a backup route to a destination; it is kept in the topology table. EIGRP uses the same metric components as IGRP: delay, bandwidth, reliability, load, and MTU. By default, EIGRP metric equals bandwidth (slowest link) plus delay (sum of delays). EIGRP metrics are backward-compatible with IGRP; the EIGRP-equivalent metric is the IGRP metric multiplied by 256. The configuration commands for basic EIGRP include:

router EIGRP autonomous-system network network-number [wildcard-mask] bandwidth kilobits

The optional wildcard-mask parameter in the network command is an inverse mask used to determine how to interpret the network-number parameter. A wildcard bit of 0 is a match and of 1 is dont care. Create and advertise a default route in an EIGRP AS with the ip default-network network-number command. Use the show ip EIGRP neighbors command to verify that the router recognizes its neighbors. Use the show ip route EIGRP command to verify that the router recognizes routes from its neighbors. Use the show ip protocols, show ip EIGRP interfaces, show ip EIGRP neighbors, show ip EIGRP topology, and show ip EIGRP traffic commands to verify EIGRP operations. EIGRP performs automatic network-boundary summarization, but administrators can disable automatic summarization and perform manual route summarization on an interface-by-interface basis. Summarizing routes creates smaller routing tables. Use the no auto-summary command to disable automatic summarization. Use the ip summary-address EIGRP command to create a summary address. EIGRP performs equal-cost load balancing by default for up to four paths (up to six paths can be supported). Use the variance command to configure unequal-cost load balancing. EIGRP uses up to 50 percent of the bandwidth of an interface by default. Because of the inherent differences in the operational characteristics of WAN links, this default may not be the best option for all WAN links. Use the ip bandwidth-percent EIGRP command to configure EIGRP bandwidth use across WAN links. There are two types of router authentication: simple password and MD5. When EIGRP authentication is configured, the router generates and checks every EIGRP packet and authenticates the source of each routing update packet that it receives. EIGRP supports MD5 authentication.


91 - 9985048840

Page 33 of 182

To configure MD5 authentication, use the ip authentication mode EIGRP and ip authentication key-chain interface commands. The key chain must also be configured, starting with the key chain command. Use debug EIGRP packets to verify and troubleshoot MD5 authentication. Factors that affect network scalability include these:

Amount of information exchanged between neighbors Number of routers Depth of the topology Number of alternate paths through the network

When a route is lost and no feasible successor is available, queries are sent to all neighboring routers on all interfaces. The EIGRP stub command is used to enable the stub routing feature, which improves network stability, reduces resource utilization, and simplifies stub router configuration. After a route goes active and the query sequence is initiated, it can only come out of the active state and move to passive state when it receives a reply for every generated query. If the router does not receive a reply to all the outstanding queries within 3 minutes (the default time), the route goes to the SIA state. The active process enhancement feature enables an EIGRP router to monitor the progression of the search for a successor route so that neighbor relationships are not reset unnecessarily. With graceful shutdown, a goodbye message is broadcast when an EIGRP routing process is shut down, to inform adjacent peers about the impending topology change. Features such as stub routing, active process enhancement, and graceful shutdown help improve network stability and performance.

For successful neighbor relationship there are few attributes must match between EIGRP enabled routers.

1. AS number must match. 2. Authentication password must match 3. K values must match 4. MTU & network / subnet mask must match.

EIGRP Authentication support only MD5

EIGRP neighbors Steps for Troubleshooting EIGRP 1) connectivity (ping , IP , MASK ,) 2) advertisements 3) mismatch of any of the a. AS NO


91 - 9985048840

Page 34 of 182

b. K- values c. Authentication Sh ip EIGRP neighbors Sh ip protocols Sh run Sh run int fa0/0 Debug eigrp packets


91 - 9985048840

Page 35 of 182

LAB -1 EIGRP SUMMARIZATION

TASK 1.1 Basic ADVERTISEMENTS R1 Conf t router EIGRP `100 network 10.0.00.0 network 1.0.0.0 R2 router EIGRP 100 network 20.0.0.0 network 2.0.0.0 network 1.0.0.0 exit R3 router EIGRP 100 net 30.0.0.0 net 2.0.0.0


91 - 9985048840

Page 36 of 182

net 13.0.0.0 exit R-1#sh ip route C 1.0.0.0/8 is directly connected, Serial1/0 D 2 0.0/8 [90/2681856] via 1.1.1.2, 00:02:33, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:02:33, Serial1/0 C 10.0.0.0/8 is directly connected, FastEthernet0/0 11.0.0.0/24 is subnetted, 4 subnets C 11.0.3.0 is directly connected, Loopback3 C 11.0.2.0 is directly connected, Loopback2 C 11.0.1.0 is directly connected, Loopback1 C 11.0.0.0 is directly connected, Loopback0 D 13.0.0.0/8 [90/2809856] via 1.1.1.2, 00:02:06, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:02:12, Serial1/0 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:03:28, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:03:28, Serial1/0 D 13.0.0.0/8 [90/2809856] via 1.1.1.2, 00:02:59, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:03:05, Serial1/0 Same way you can verify on R2 . R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:03:28, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:03:28, Serial1/0 D 13.0.0.0/8 [90/2809856] via 1.1.1.2, 00:02:59, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:03:05, Serial1/0 13.0.0.0 network is auto summarized. By default ( as EIGRP, RIPV2 and BGP do auto summary by default ) TASK 1.2 disable auto-summary on all routers R-X(config)#router EIGRP 100 R-X(config-router)#no auto-summary


91 - 9985048840

Page 37 of 182

R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:06:09, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:06:09, Serial1/0 13.0.0.0/24 is subnetted, 4 subnets D 13.0.1.0 [90/2809856] via 1.1.1.2, 00:00:13, Serial1/0 D 13.0.0.0 [90/2809856] via 1.1.1.2, 00:00:13, Serial1/0 D 13.0.3.0 [90/2809856] via 1.1.1.2, 00:00:13, Serial1/0 D 13.0.2.0 [90/2809856] via 1.1.1.2, 00:00:13, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:05:46, Serial1/0 Al l the routes gets advertised individually TASK -1. 3 Here the requirement is that I want R3 to perform manual summarization of above networks as (13.0.00.0/22 after calculation) when it sends to R2 R3 int s1/0 ip summary-address EIGRP 100 13.0.0.0 255.255.252.0 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:10:19, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:10:19, Serial1/0 13.0.0.0/22 is subnetted, 1 subnets D 13.0.0.0 [90/2809856] via 1.1.1.2, 00:00:22, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:09:56, Serial1/0 Task 1.4 1) Advertise the loopbacks of R2 and R1 in EIGRP 100 2) Configure manual summarization when they send those routes to other routers R1 router EIGRP 100 net 11.0.0.0 no au no auto-summary exit R2


91 - 9985048840

Page 38 of 182

router EIGRP 100 network 12.0.0.0 no auto-summary exit R-3#sh ip route EIGRP D 1.0.0.0/8 [90/2681856] via 2.2.2.1, 00:13:33, Serial1/0 D 20.0.0.0/8 [90/2172416] via 2.2.2.1, 00:13:33, Serial1/0 D 10.0.0.0/8 [90/2684416] via 2.2.2.1, 00:13:33, Serial1/0 11.0.0.0/24 is subnetted, 4 subnets D 11.0.3.0 [90/2809856] via 2.2.2.1, 00:00:56, Serial1/0 D 11.0.2.0 [90/2809856] via 2.2.2.1, 00:00:56, Serial1/0 D 11.0.1.0 [90/2809856] via 2.2.2.1, 00:00:56, Serial1/0 D 11.0.0.0 [90/2809856] via 2.2.2.1, 00:00:56, Serial1/0 12.0.0.0/24 is subnetted, 4 subnets D 12.0.0.0 [90/2297856] via 2.2.2.1, 00:01:25, Serial1/0 D 12.0.1.0 [90/2297856] via 2.2.2.1, 00:01:25, Serial1/0 D 12.0.2.0 [90/2297856] via 2.2.2.1, 00:01:25, Serial1/0 D 12.0.3.0 [90/2297856] via 2.2.2.1, 00:01:25, Serial1/0 13.0.0.0/8 is variably subnetted, 5 subnets, 2 masks D 13.0.0.0/22 is a summary, 00:03:59, Null0 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:14:21, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:14:21, Serial1/0 12.0.0.0/24 is subnetted, 4 subnets D 12.0.0.0 [90/2297856] via 1.1.1.2, 00:01:50, Serial1/0 D 12.0.1.0 [90/2297856] via 1.1.1.2, 00:01:50, Serial1/0 D 12.0.2.0 [90/2297856] via 1.1.1.2, 00:01:50, Serial1/0 D 12.0.3.0 [90/2297856] via 1.1.1.2, 00:01:50, Serial1/0 13.0.0.0/22 is subnetted, 1 subnets D 13.0.0.0 [90/2809856] via 1.1.1.2, 00:04:24, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:13:58, Serial1/0 Task 1.5 Configure manual summarization when they send those routes to other routers R1 ( applying manual Summarization) int s1/0 ip summary-address EIGRP 100 11.0.0.0 255.255.252.0 exit


91 - 9985048840

Page 39 of 182

R-2#sh ip route EIGRP D 10.0.0.0/8 [90/2172416] via 1.1.1.1, 00:16:07, Serial1/0 11.0.0.0/22 is subnetted, 1 subnets D 11.0.0.0 [90/2297856] via 1.1.1.1, 00:00:29, Serial1/0 13.0.0.0/22 is subnetted, 1 subnets D 13.0.0.0 [90/2297856] via 2.2.2.2, 00:06:10, Serial1/1 D 30.0.0.0/8 [90/2172416] via 2.2.2.2, 00:15:44, Serial1/1 R2 ( applying manual Summarization) int s1/0 ip summary-address EIGRP 100 12.0.0.0 255.255.252.0 int s1/1 ip summary-address EIGRP 100 12.0.0.0 255.255.252.0 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:17:26, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:17:26, Serial1/0 11.0.0.0/8 is variably subnetted, 5 subnets, 2 masks D 11.0.0.0/22 is a summary, 00:01:49, Null0 12.0.0.0/22 is subnetted, 1 subnets D 12.0.0.0 [90/2297856] via 1.1.1.2, 00:00:41, Serial1/0 13.0.0.0/22 is subnetted, 1 subnets D 13.0.0.0 [90/2809856] via 1.1.1.2, 00:07:29, Serial1/0 D 30.0.0.0/8 [90/2684416] via 1.1.1.2, 00:17:03, Serial1/0 R-3#sh ip route EIGRP D 1.0.0.0/8 [90/2681856] via 2.2.2.1, 00:17:18, Serial1/0 D 20.0.0.0/8 [90/2172416] via 2.2.2.1, 00:17:18, Serial1/0 D 10.0.0.0/8 [90/2684416] via 2.2.2.1, 00:17:18, Serial1/0 11.0.0.0/22 is subnetted, 1 subnets D 11.0.0.0 [90/2809856] via 2.2.2.1, 00:02:04, Serial1/0 12.0.0.0/22 is subnetted, 1 subnets D 12.0.0.0 [90/2297856] via 2.2.2.1, 00:00:51, Serial1/0 13.0.0.0/8 is variably subnetted, 5 subnets, 2 masks D 13.0.0.0/22 is a summary, 00:07:44, Null0


91 - 9985048840

Page 40 of 182

Lab- 2 DEFAULT ROUTE IN EIGRP

1) BASIC ADV

R1 router EIGRP 100 no auto-summary net 10.0.0.0 net 1.0.0.0 exit R2 En Conf t router EIGRP 100 no auto-summary net 20.0.0.0 net 1.0.0.0 net 2.0.0.0 exit R3 router EIGRP 100 no auto-summary


91 - 9985048840

Page 41 of 182

net 2.0.0.0 exit note : 30.1.1.1 and all 13.0.0.0 network loopbacks act as internet routes in our example R-2#sh ip EIGRP neighbors IP-EIGRP neighbors for process 100 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 1 2.2.2.2 Se1/1 14 00:00:19 54 324 0 3 0 1.1.1.1 Se1/0 14 00:00:31 39 351 0 3

2) Configure a Default route on R2 (head office )to reach internet routes R-2(config)#ip route 0.0.0.0 0.0.0.0 2.2.2.2 R-2#sh ip route C 1.0.0.0/8 is directly connected, Serial1/0 C 2.0.0.0/8 is directly connected, Serial1/1 C 20.0.0.0/8 is directly connected, FastEthernet0/0 D 10.0.0.0/8 [90/2172416] via 1.1.1.1, 00:01:51, Serial1/0 12.0.0.0/24 is subnetted, 4 subnets C 12.0.0.0 is directly connected, Loopback0 C 12.0.1.0 is directly connected, Loopback1 C 12.0.2.0 is directly connected, Loopback2 C 12.0.3.0 is directly connected, Loopback3 S* 0.0.0.0/0 [1/0] via 2.2.2.2 R-2#ping 13.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 13.0.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 8/22/36 ms R-2#ping 30.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 30.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 20/31/52 ms


91 - 9985048840

Page 42 of 182

(R2)Head office can reach internet but the branch office cannot as there is no default route configured for internet in Branch office ( R1) . R-1#ping 13.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 13.0.0.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) No routes for 13.0.0.0 in the routing table R-1#sh ip route Gateway of last resort is not set C 1.0.0.0/8 is directly connected, Serial1/0 D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:02:51, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:02:51, Serial1/0 C 10.0.0.0/8 is directly connected, FastEthernet0/0 11.0.0.0/24 is subnetted, 4 subnets C 11.0.3.0 is directly connected, Loopback3 C 11.0.2.0 is directly connected, Loopback2 C 11.0.1.0 is directly connected, Loopback1 C 11.0.0.0 is directly connected, Loopback0 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:05:26, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:05:26, Serial1/0

3) In order to Provide internet access to branch offices (R1 ) to reach internet routes through head office we need to advertise the 2.0.0.0 network in EIGRP updates with the command R-2#conf t R-2(config)#ip default-network 2.0.0.0 R-1#sh ip route EIGRP

D* 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:00:22, Serial1/0 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:06:06, Serial1/0 R-1#ping 13.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 13.0.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 20/50/92 ms


91 - 9985048840

Page 43 of 182

R-1#ping 30.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 30.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 16/48/84 ms RIP default routing in RIPv2

R1 and R2 basic advertisements R2 ( head office ) configure a default route R1 router rip ver 2 net 10.0.0.0 net 1.0.0.0 no auto-summary exit

R2 router rip


91 - 9985048840

Page 44 of 182

ver 2 net 20.0.0.0 net 1.0.0.0 no auto-summary exit ip route 0.0.0.0 0.00.0.0 2.2.2.2 R2#sh ip route C 1.0.0.0/8 is directly connected, Serial0/0 C 2.0.0.0/8 is directly connected, Serial0/1 C 20.0.0.0/8 is directly connected, FastEthernet0/0 R 10.0.0.0/8 [120/1] via 1.1.1.1, 00:00:03, Serial0/0 12.0.0.0/24 is subnetted, 4 subnets C 12.0.0.0 is directly connected, Loopback0 C 12.0.1.0 is directly connected, Loopback1 C 12.0.2.0 is directly connected, Loopback2 C 12.0.3.0 is directly connected, Loopback3 S* 0.0.0.0/0 [1/0] via 2.2.2.2 R1#sh ip route C 1.0.0.0/8 is directly connected, Serial0/0 R 20.0.0.0/8 [120/1] via 1.1.1.2, 00:00:09, Serial0/0 C 10.0.0.0/8 is directly connected, FastEthernet0/0 11.0.0.0/24 is subnetted, 4 subnets C 11.0.3.0 is directly connected, Loopback3 C 11.0.2.0 is directly connected, Loopback2 C 11.0.1.0 is directly connected, Loopback1 C 11.0.0.0 is directly connected, Loopback0 Here we need to advertise the default route to all branch offices in the RIP so that they can access internet through head office R2 router rip default-information originate R1#sh ip route C 1.0.0.0/8 is directly connected, Serial0/0


91 - 9985048840

Page 45 of 182

R 20.0.0.0/8 [120/1] via 1.1.1.2, 00:00:06, Serial0/0 C 10.0.0.0/8 is directly connected, FastEthernet0/0 11.0.0.0/24 is subnetted, 4 subnets C 11.0.3.0 is directly connected, Loopback3 C 11.0.2.0 is directly connected, Loopback2 C 11.0.1.0 is directly connected, Loopback1 C 11.0.0.0 is directly connected, Loopback0 R* 0.0.0.0/0 [120/1] via 1.1.1.2, 00:00:06, Serial0/0 R1#ping 13.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 13.0.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/98/292 ms R1#traceroute 13.0.0.1 Type escape sequence to abort. Tracing the route to 13.0.0.1 1 1.1.1.2 68 msec 152 msec 4 msec 2 2.2.2.2 128 msec * 92 msec


91 - 9985048840

Page 46 of 182

DEFAULT ROUTE IN OSPF

Task : 1 Basic advertisements according to diagram R1 Router ospf 1 Network 1.0.0.0 0.255.255.255 area 0 Network 10.0.0.0 0.255.255.255 area 0 R2 Router ospf 1 Network 1.0.0.0 0.255.255.255 area 0 Network 20.0.0.0 0.255.255.255 area 0 Network 2.0.0.0 0.255.255.255 area 0 R3 Router ospf 1 Network 2.0.0.0 0.255.255.255 area 0


91 - 9985048840

Page 47 of 182

Task 2 Configure a Default route on R2 (head office )to reach internet routes

R2 ( head office) conf t ip route 0.0.0.0 0.0.0.0 2.2.2.2 Task 3 Advertise the default to all the other routers in OSPF R2 ( head office) router ospf 1 default-information originate


91 - 9985048840

Page 48 of 182

EIGRP Load balancing -------------------- When a router learns a same route from different neighbors with the same metric it install both the routes in the routing table and does load balancing, this is called equal cost load balancing. Note:- It does equal cost load balancing automatically. whereas unequal cost is not automatic. For unequal cost load balancing we need to enable "variance" ------------------------------------------------------

Lab : EIGRP LOAD BALANCING

TASK - 1


91 - 9985048840

Page 49 of 182

Basic advertisements On All routers

R1 En Conf t router EIGRP 100 no auto-summary net 10.0.0.0 net 1.0.0.0 net 4.0.0.0 exit R2 En Conf t router EIGRP 100 no auto-summary net 20.0.0.0 net 1.0.0.0 net 2.0.0.0 exit R3 En Conf t router EIGRP 100 no auto-summary net 30.0.0.0 net 2.0.0.0 net 3.0.0.0 exit R4 En Conf t router EIGRP 100 no auto-summary net 40.0.0.0 net 3.0.0.0 net 4.0.0.0 exit R-1#sh ip EIGRP neighbors


91 - 9985048840

Page 50 of 182

IP-EIGRP neighbors for process 100 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 1 4.4.4.1 Se1/1 12 00:00:11 77 462 0 9 0 1.1.1.2 Se1/0 12 00:00:11 62 372 0 11 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/2681856] via 1.1.1.2, 00:00:36, Serial1/0 D 3.0.0.0/8 [90/2681856] via 4.4.4.1, 00:00:36, Serial1/1 D 20.0.0.0/8 [90/2172416] via 1.1.1.2, 00:00:36, Serial1/0 D 40.0.0.0/8 [90/2172416] via 4.4.4.1, 00:00:36, Serial1/1 D 30.0.0.0/8 [90/2684416] via 4.4.4.1, 00:00:36, Serial1/1 [90/2684416] via 1.1.1.2, 00:00:36, Serial1/0 Both routes are in the routing table means it is using both the routes to send any packet to 30.1.1.1 (R3) R-1#sh ip EIGRP topology IP-EIGRP Topology Table for AS(100)/ID(11.0.3.1) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status P 1.0.0.0/8, 1 successors, FD is 2169856 via Connected, Serial1/0 P 2.0.0.0/8, 1 successors, FD is 2681856 via 1.1.1.2 (2681856/2169856), Serial1/0 P 3.0.0.0/8, 1 successors, FD is 2681856 via 4.4.4.1 (2681856/2169856), Serial1/1 P 4.0.0.0/8, 1 successors, FD is 2169856 via Connected, Serial1/1 P 10.0.0.0/8, 1 successors, FD is 28160 via Connected, FastEthernet0/0 P 20.0.0.0/8, 1 successors, FD is 2172416 via 1.1.1.2 (2172416/28160), Serial1/0 P 30.0.0.0/8, 2 successors, FD is 2684416 via 1.1.1.2 (2684416/2172416), Serial1/0 via 4.4.4.1 (2684416/2172416), Serial1/1 P 40.0.0.0/8, 1 successors, FD is 2172416 via 4.4.4.1 (2172416/28160), Serial1/1 R-1#sh interfaces s1/0 Serial1/0 is up, line protocol is up Hardware is M4T Internet address is 1.1.1.1/8


91 - 9985048840

Page 51 of 182

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 by default EIGRP do equal cost load balancing R-1#traceroute 30.1.1.1 Type escape sequence to abort. Tracing the route to 30.1.1.1 1 4.4.4.1 52 msec 1.1.1.2 24 msec 4.4.4.1 36 msec 2 2.2.2.2 76 msec 3.3.3.1 56 msec Task -2 : change the BW to 1000 Kbps on any of the R1 interface R-1(config)#int s1/0 R-1(config-if)#bandwidth ? Bandwidth in kilobits R-1(config-if)#bandwidth 1000 R-1#sh ip route EIGRP D 2.0.0.0/8 [90/3193856] via 4.4.4.1, 00:00:28, Serial1/1 D 3.0.0.0/8 [90/2681856] via 4.4.4.1, 00:00:28, Serial1/1 D 20.0.0.0/8 [90/3074560] via 1.1.1.2, 00:00:28, Serial1/0 D 40.0.0.0/8 [90/2172416] via 4.4.4.1, 00:08:11, Serial1/1 D 30.0.0.0/8 [90/2684416] via 4.4.4.1, 00:00:28, Serial1/1 R-1#sh ip EIGRP topology IP-EIGRP Topology Table for AS(100)/ID(11.0.3.1) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status P 1.0.0.0/8, 1 successors, FD is 3072000 via Connected, Serial1/0 P 2.0.0.0/8, 1 successors, FD is 3193856 via 4.4.4.1 (3193856/2681856), Serial1/1 via 1.1.1.2 (3584000/2169856), Serial1/0 P 3.0.0.0/8, 1 successors, FD is 2681856 via 4.4.4.1 (2681856/2169856), Serial1/1 P 4.0.0.0/8, 1 successors, FD is 2169856 via Connected, Serial1/1


91 - 9985048840

Page 52 of 182

P 10.0.0.0/8, 1 successors, FD is 28160 via Connected, FastEthernet0/0 P 20.0.0.0/8, 1 successors, FD is 2172416 via 1.1.1.2 (3074560/28160), Serial1/0 P 30.0.0.0/8, 1 successors, FD is 2684416 via 4.4.4.1 (2684416/2172416), Serial1/1 via 1.1.1.2 (3586560/2172416), Serial1/0 P 40.0.0.0/8, 1 successors, FD is 2172416 via 4.4.4.1 (2172416/28160), Serial1/1 EIGRP also supports unequal cost load balancing. But it has to be done manually using variance. Variance is a multiplier value (1 128) The routes which can go for load balancing should satisfy the condition cost of successor X variance > cost of the other routes to be used for load balancing cost ofsuccessor via 4.4.4.1 (2684416/2172416), Serial1/1 cost of second routes to be used for load balancing via 1.1.1.2 (3586560/2172416), Serial1/0 select the variance value cost of successor X variance > cost of the other routes to be used for loadbalancing 2684416 X ------- > 3586560 The variance to be used here is 2 to satisfy the condition R-1(config)#router EIGRP 100 R-1(config-router)#variance 2 R-1#sh ip protocols Routing Protocol is "EIGRP 100" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Default networks flagged in outgoing updates Default networks accepted from incoming updates EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0 EIGRP maximum hopcount 100 EIGRP maximum metric variance 2 Redistributing: EIGRP 100


91 - 9985048840

Page 53 of 182

R-1#sh ip route EIGRP D 2.0.0.0/8 [90/3193856] via 4.4.4.1, 00:00:56, Serial1/1 [90/3584000] via 1.1.1.2, 00:00:56, Serial1/0 D 3.0.0.0/8 [90/2681856] via 4.4.4.1, 00:00:56, Serial1/1 D 20.0.0.0/8 [90/3196416] via 4.4.4.1, 00:00:56, Serial1/1 [90/3074560] via 1.1.1.2, 00:00:56, Serial1/0 D 40.0.0.0/8 [90/2172416] via 4.4.4.1, 00:00:56, Serial1/1 D 30.0.0.0/8 [90/2684416] via 4.4.4.1, 00:00:56, Serial1/1 [90/3586560] via 1.1.1.2, 00:00:56, Serial1/0 Note : IT WILL DO load balancing for all the routes which satisfy the condition R-1#traceroute 30.1.1.1 Type escape sequence to abort. Tracing the route to 30.1.1.1 1 4.4.4.1 40 msec 1.1.1.2 20 msec 4.4.4.1 52 msec 2 2.2.2.2 32 msec 3.3.3.1 60 msec


91 - 9985048840

Page 54 of 182


91 - 9985048840

Page 55 of 182

OSPF OSPF Features

Open standard (IETF) SPF or Dijkstra algorithm Link-state routing protocol Classless Supports FLSM, VLSM, CIDR and Manual summary Incremental / triggered updates Updates are sent as multicast (224.0.0.5 & 224.0.0.6) Metric = Cost (cost = 108/bandwidth in bps) Administrative distance = 110 Load balancing via 4 equal cost paths by default (unequal cost load balancing not supported) Auto Neighbor discovery Hierarchical network design Sends periodic updates, known as link-state refresh, for every 30 minutes Maintains similar database on all the routers within an area

Router ID is used to identify each router Router ID

Highest IP address on Active Physical Interface More preference is given to logical interface (if configured) Highest preference is for Router ID command

Configuring Router ID Router(config-router)#router-id

Link-State Data Structures Neighbor Table


91 - 9985048840

Page 56 of 182

Also known as the adjacency database Contains list of directly connected routers (neighbors) Database Table Typically referred to as LSDB ( link state database) Contains information about all the possible routes to the networks with in the area Routing Table Contains list of best paths to each destination OSPF SEVEN STAGE PROCESS

1) Establishing Bidirectional Communication

2) Discovering the Network Routes


91 - 9985048840

Page 57 of 182

3) Adding the Link-State Entries

Link-State Data Structure: Network Hierarchy Link-state routing can have hierarchical network This two-level hierarchy consists of the following: Transit area (backbone or area 0) Regular areas (nonbackbone areas)


91 - 9985048840

Page 58 of 182

Issue of Maintaining of large OSPF network

OSPF Multi Area

OSPF Database


91 - 9985048840

Page 59 of 182

OSPF Metric calculation OSPF metric is not defined in standards. Every vendor uses different formula to calculate metric OSPF Metric in Cisco = Cost= 108/ Bandwidth in bps Ex: Serial link64 Kbpscost 1562 1544 Kbps cost 64 2000 Kbps cost 48 Ethernet10 Mbpscost 10 FastEthernet100 Mbps cost 1 Gigabit Ethernet(1000 Mbps) cost 1 OSPF Packet Type 1. Hello 2. Database Description 3. Link State Request 4. Link State Update 5. Link State Ack OSPF Packet Header Format


91 - 9985048840

Page 60 of 182

OSPF Neighbor relationship


91 - 9985048840

Page 61 of 182

LS Data Structures: LSA Operation

OSPF Network Types

Adjacency Behavior for a Point-to-Point Link

A point-to-point link is a single pair of routers. Serial line configured with PPP or HDLC protocol. No DR or BDR election is required OSPF auto detects this type of link.


91 - 9985048840

Page 62 of 182

Broadcast Multi Access Topology like Ethernet and Token Ring is BMA. DR and BDR Election is required. OSPF detects this type of link automatically


91 - 9985048840

Page 63 of 182

Designated Router &Backup Designated Router The router having highest priority is DR The router with second-highest priority is BDR The default priority value is 1 In the case of a tie, router with highest router ID is DR second highest router ID becomes the BDR If router priority is 0 it cannot become the DR or BDR Router which is not a DR or BDR is called as DROTHER DR & BDR election is not preemptive

DR/BDR Elections Neighbors DR/BDR DROTHER Full DROTHER DR/BDR Full DROTHER DROTHER 2 Way

Updates DROTHER DR/BDR 224.0.0.6 DR DROTHER 224.0.0.5


91 - 9985048840

Page 64 of 182

NBMA Links like Frame relay, ATM and X.25. OSPF considers NBMA as other broadcast media. NBMA is not always full-mesh DR BDR election depends on type of connection

NBMA Types


91 - 9985048840

Page 65 of 182

Type of OSPF Routers

OSPF Summarization Benefit Of Route Summarization Minimizes number of routing table entries Localizes the impact of a topology change Reduces LSA 3 and 5 flooding and saves CPU resources Before Route Summarization


91 - 9985048840

Page 66 of 182

After Route Summarization

Types Of LSA


91 - 9985048840

Page 67 of 182

LSA Type 1: Router LSA

generated by the internal router One Router LSA (type 1) for every router in an area Includes list of directly attached links Identified by the router ID of the originating router Floods within its area only; does not cross the ABR "O" routes in the routing table

LSA Type 2: Network LSA

One Network (type 2) LSA for each transit broadcast or NBMA network in an area (happens in broadcast networks ) Includes Network ID, subnet mask and list of attached routers on that transit link Advertised by the DR of the transit network (DR --> other ( LSA2)) Floods within its area only; does not cross ABR "O" routes


91 - 9985048840

Page 68 of 182

LSA Type 3: Summary LSA

sending updates from one area to another area( 0 IA routes in the routing table) contains network ID and subnet mask Advertised by the ABR of originating area Regenerated by subsequent ABRs to flood throughout the autonomous system. By default, routes are not summarized and there is one type 3 LSA for every subnet

LSA Type 4: Summary LSA

ASBR Summary (type 4) LSAs are used to advertise Router ID of ASBR to all routers in other areas present in autonomous system They are generated by the ABR of the originating area They are regenerated by all subsequent ABRs to flood throughout the autonomous system Type 4 LSAs contain only the router ID of the ASBR


91 - 9985048840

Page 69 of 182

LSA Type 5: External LSA

External (type 5) LSAs are used to advertise networks learned from other autonomous systems(ASBR external routes (redistributed routes) in to the OSPF) Type 5 LSAs are advertised and owned by the originating ASBR (generated by the ASBR) Type 5 LSAs flood throughout the autonomous system The advertising router ID (ASBR) is unchanged throughout the autonomous system Type 4 LSA is needed to identify ASBR By default, routes are not summarized by ASBR oE1 / oE2 routes

LSA- 6

o used in multicast routing (MOSPF routing protocol) Multicast LSA (Cisco routers dont support )

Types of Routes


91 - 9985048840

Page 70 of 182

E2 --- will not add the individual metric ( it remains same metric for al l the routers ) Default for external routes E1 ---- will add the individual metric ( it changes as move from router to router ) R4(config-router)#redistribute rip subnets metric 250 me R4(config-router)#redistribute rip subnets metric 250 metric-type ? 1 Set OSPF External Type 1 metrics 2 Set OSPF External Type 2 metrics Default Routes in OSPF OSPF can send Default Route in update A default route is sent as an external LSA type (O*E2) Static Default Route needs to be defined in Originating router Router(config)#iproute0.0.0.00.0.0.0 Router(config-router)#default-informationoriginate


91 - 9985048840

Page 71 of 182

OSPF Special Area

Stub and Totally Stubby Area Rules

There should not be an ASBR in the area The area should not be Area 0 No virtual links must pass through the area There should be a single ABR (recommended)

Using Stub Areas External LSAs are stopped ( E1 and E2 routes) Default route is advertised into stub area by the ABR All routers in stub area must be configured as stub


91 - 9985048840

Page 72 of 182

Stub Area Configuration Configuring Stub command on all router in the area Router(config-router)#areastub Using Totally Stubby Areas

External LSAs are stopped ( E1 and E2) Summary LSAs are stopped ( OIA routes ) Routing table is reduced to a minimum All routers in stub area must be configured as stub ABR of stub area must be configured as totally stubby This is a Cisco proprietary feature

Totally Stubby Configuration Configuring all routers of Totally Stubby Area Router(config-router)#area stub Configuring Area Border Router of Totally Stubby AreaRouter


91 - 9985048840

Page 73 of 182

(config-router)#area stubno-summary Not-So-Stubby Areas

NSSA breaks stub area rules ASBR is allowed in NSSA Special LSA type 7 defined, sent by ASBR ABR converts LSA type 7 to LSA type 5 ABR does not send default route into NSSA by default NSSA is an RFC addendum

NSSA Area Configuration Configuring NSSA command on all router in the area Router(config-router)#areanssa Totally Not-So-Stubby Areas Totally NSSA Does not accepts summary and external LSAs By default, Default Route is advertised by ABR of Totally NSSA

Totally NSSA Area Configuration Configuring NSSA command on all router in the area Router(config-router)#areanssa Configuring NSSA command on ABR router in the area Router(config-router)#areanssano-summary


91 - 9985048840

Page 74 of 182

OSPF Virtual Link Virtual links are used to connect a discontiguous area to area 0 A logical connection is built between routers Virtual links are recommended for backup or temporary connections

Configuring Virtual Links Router(config-router)#areavirtual-link


91 - 9985048840

Page 75 of 182

LAB -2.1 BASIC OSPF IMPLEMENTATION IN MULTIPLE AREAS

TASK -1 OSPF BASIC ADVERTISEMENTS R1 router ospf 1 network 10.0.0.0 0.255.255.255 area 10 network 1.0.0.0 0.255.255.255 area 10 end R2 router ospf 1 network 2.0.0.0 0.255.255.255 area 0 network 20.0.0.0 0.255.255.255 area 0 network 1.0.0.0 0.255.255.255 area 10


91 - 9985048840

Page 76 of 182

R2(config-router)# *Mar 1 00:04:22.903: %OSPF-5-ADJCHG: Process 1, Nbr 11.0.3.1 on Serial0/0 from LOADING to FULL, Loading Done R3 router ospf 1 network 30.0.0.0 0.255.255.255 area 0 network 2.0.0.0 0.255.255.255 area 0 network 3.0.0.0 0.255.255.255 area 20 *Mar 1 00:06:18.079: %OSPF-5-ADJCHG: Process 1, Nbr 12.0.3.1 on Serial0/0 from LOADING to FULL, Loading Done R4 router ospf 1 network 40.0.0.0 0.255.255.255 area 20 network 3.0.0.0 0.255.255.255 area 20 end R1#sh ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 12.0.3.1 0 FULL/ - 00:00:31 1.1.1.2 Serial0/0 R1#sh ip protocols Routing Protocol is "ospf 1" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Router ID 11.0.3.1 Number of areas in this router is 1. 1 normal 0 stub 0 nssa Maximum path: 4 Routing for Networks: 1.0.0.0 0.255.255.255 area 10 10.0.0.0 0.255.255.255 area 10 Router ID ( here it takes the highest IP of loopback interface )


91 - 9985048840

Page 77 of 182

R2#sh ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 13.0.3.1 0 FULL/ - 00:00:30 2.2.2.2 Serial0/1 11.0.3.1 0 FULL/ - 00:00:33 1.1.1.1 Serial0/0 R3#sh ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 12.0.3.1 0 FULL/ - 00:00:35 2.2.2.1 Serial0/0 14.0.3.1 0 FULL/ - 00:00:33 3.3.3.2 Serial0/1 R2#sh ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 13.0.3.1 0 FULL/ - 00:00:30 2.2.2.2 Serial0/1 11.0.3.1 0 FULL/ - 00:00:33 1.1.1.1 Serial0/0 R2#sh ip ospf database OSPF Router with ID (12.0.3.1) (Process ID 1) Router Link States (Area 0) Link ID ADV Router Age Seq# Checksum Link count 12.0.3.1 12.0.3.1 321 0x80000004 0x00EC4B 3 13.0.3.1 13.0.3.1 315 0x80000004 0x00C06B 3 Summary Net Link States (Area 0) Link ID ADV Router Age Seq# Checksum 1.0.0.0 12.0.3.1 429 0x80000001 0x007774 3.0.0.0 13.0.3.1 311 0x80000001 0x005494 10.0.0.0 12.0.3.1 419 0x80000001 0x006672 40.0.0.0 13.0.3.1 226 0x80000001 0x00D5E3 Router Link States (Area 10) Link ID ADV Router Age Seq# Checksum Link count 11.0.3.1 11.0.3.1 433 0x80000003 0x003813 3 12.0.3.1 12.0.3.1 427 0x80000002 0x00BDAF 2 Summary Net Link States (Area 10) Link ID ADV Router Age Seq# Checksum


91 - 9985048840

Page 78 of 182

2.0.0.0 12.0.3.1 434 0x80000001 0x006A80 3.0.0.0 12.0.3.1 310 0x80000001 0x00DFC9 20.0.0.0 12.0.3.1 437 0x80000001 0x0061AD 30.0.0.0 12.0.3.1 320 0x80000001 0x006163 40.0.0.0 12.0.3.1 228 0x80000001 0x006119 R1#sh ip ospf database OSPF Router with ID (11.0.3.1) (Process ID 1) Router Link States (Area 10) Link ID ADV Router Age Seq# Checksum Link count 11.0.3.1 11.0.3.1 505 0x80000003 0x003813 3 12.0.3.1 12.0.3.1 504 0x80000002 0x00BDAF 2 Summary Net Link States (Area 10) Link ID ADV Router Age Seq# Checksum 2.0.0.0 12.0.3.1 508 0x80000001 0x006A80 3.0.0.0 12.0.3.1 384 0x80000001 0x00DFC9 20.0.0.0 12.0.3.1 508 0x80000001 0x0061AD 30.0.0.0 12.0.3.1 393 0x80000001 0x006163 40.0.0.0 12.0.3.1 302 0x80000001 0x006119 R1#sh ip protocols Routing Protocol is "ospf 1" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Router ID 11.0.3.1 Number of areas in this router is 1. 1 normal 0 stub 0 nssa Maximum path: 4 Routing for Networks: 1.0.0.0 0.255.255.255 area 10 10.0.0.0 0.255.255.255 area 10 TASK - 2 Router ID ( it takes the highest IP of loopback interface if configured ) But its preferable to manually configure Router-ID. Lets say Here I want to change the Router-id (manually)


91 - 9985048840

Page 79 of 182

R1(config)#router ospf 1 R1(config-router)#router-id 11.1.1.1 Reload or use "clear ip ospf process" command, for this to take effect R1 already have the router id and it already established so u need to re enale the neighbor ship R1#clear ip ospf process Reset ALL OSPF processes? [no]: yes R1#sh ip protocols Routing Protocol is "ospf 1" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Router ID 11.1.1.1 Task 3 Change the Router-ID of as R2 22.2.2.2 R3 33.3.3.3 R4 44.4.4.4


91 - 9985048840

Page 80 of 182

REDISTRIBUTION

Task 1 Basic adv According to Diagram R1 router rip ver 2 network 11.0.0.0 no auto-summary exit router EIGRP 100 network 1.0.0.0 network 10.0.0.0 no auto-summary exit R2 router EIGRP 100 network 1.0.0.0 no auto-summary


91 - 9985048840

Page 81 of 182

exit router ospf 1 network 20.0.0.0 0.255.255.255 area 0 network 2.0.0.0 0.255.255.255 area 0 exit R3 router ospf 1 network 2.0.0.0 0.255.255.255 area 0 network 30.0.0.0 0.255.255.255 area 0 exit router rip ver 2 net 3.0.0.0 no auto-summary exit R4 router rip ver 2 network 3.0.0.0 network 40.0.0.0 no auto-summary exit router EIGRP 100 network 14.0.0.0 no auto-summary exit R2#sh ip route Gateway of last resort is not set C 1.0.0.0/8 is directly connected, Serial0/0 C 2.0.0.0/8 is directly connected, Serial0/1 C 20.0.0.0/8 is directly connected, FastEthernet0/0 D 10.0.0.0/8 [90/2195456] via 1.1.1.1, 00:03:08, Serial0/0 12.0.0.0/24 is subnetted, 4 subnets C 12.0.0.0 is directly connected, Loopback0 C 12.0.1.0 is directly connected, Loopback1 C 12.0.2.0 is directly connected, Loopback2


91 - 9985048840

Page 82 of 182

C 12.0.3.0 is directly connected, Loopback3 O 30.0.0.0/8 [110/74] via 2.2.2.2, 00:01:40, Serial0/1 R3#sh ip route C 2.0.0.0/8 is directly connected, Serial0/0 C 3.0.0.0/8 is directly connected, Serial0/1 O 20.0.0.0/8 [110/74] via 2.2.2.1, 00:02:53, Serial0/0 R 40.0.0.0/8 [120/1] via 3.3.3.2, 00:00:23, Serial0/1 13.0.0.0/24 is subnetted, 4 subnets C 13.0.1.0 is directly connected, Loopback1 C 13.0.0.0 is directly connected, Loopback0 C 13.0.3.0 is directly connected, Loopback3 C 13.0.2.0 is directly connected, Loopback2 C 30.0.0.0/8 is directly connected, FastEthernet0/0 R4#sh ip route Gateway of last resort is not set C 3.0.0.0/8 is directly connected, Serial1/0 C 4.0.0.0/8 is directly connected, Serial1/1 C 40.0.0.0/8 is directly connected, FastEthernet0/0 14.0.0.0/24 is subnetted, 4 subnets C 14.0.2.0 is directly connected, Loopback2 C 14.0.3.0 is directly connected, Loopback3 C 14.0.0.0 is directly connected, Loopback0 C 14.0.1.0 is directly connected, Loopback1 From the above outputs we can see that the router only learns the routes from coming from the same protocols So In order to the routes between different protocols we need to redistribution. Redistribution is the process of translating the routes from one protocol to another protocol There are some rules need to follow which doing redistribution:

The router where redistribution is done should be running both protocols on at least one interface You may also need to change the metric according to protocol in which you do redistribution

Task 2 Redistributing RIP in to EIGRP R1(config)#router EIGRP 100


91 - 9985048840

Page 83 of 182

R1(config-router)#re R1(config-router)#redistribute rip ? metric Metric for redistributed routes route-map Route map reference R1(config-router)#redistribute rip metric ? Bandwidth metric in Kbits per second R1(config-router)#redistribute rip metric 1000 ? EIGRP delay metric, in 10 microsecond units R1(config-router)#redistribute rip metric 1000 20000 ? EIGRP reliability metric where 255 is 100% reliable R1(config-router)#redistribute rip metric 1000 20000 255 ? EIGRP Effective bandwidth metric (Loading) where 255 is 100% loaded R1(config-router)#redistribute rip metric 1000 20000 255 1 ? EIGRP MTU of the path R1(config-router)#redistribute rip metric 1000 20000 255 1 1500 Note: Recommended to use the metric values near to defaults . R2#sh ip route Gateway of last resort is not set C 1.0.0.0/8 is directly connected, Serial0/0 C 2.0.0.0/8 is directly connected, Serial0/1 C 20.0.0.0/8 is directly connected, FastEthernet0/0 D 10.0.0.0/8 [90/2195456] via 1.1.1.1, 00:10:23, Serial0/0 11.0.0.0/24 is subnetted, 4 subnets D EX 11.0.3.0 [170/8192000] via 1.1.1.1, 00:02:26, Serial0/0 D EX 11.0.2.0 [170/8192000] via 1.1.1.1, 00:02:26, Serial0/0 D EX 11.0.1.0 [170/8192000] via 1.1.1.1, 00:02:26, Serial0/0 D EX 11.0.0.0 [170/8192000] via 1.1.1.1, 00:02:26, Serial0/0 12.0.0.0/24 is subnetted, 4 subnets C 12.0.0.0 is directly connected, Loopback0 C 12.0.1.0 is directly connected, Loopback1 C 12.0.2.0 is directly connected, Loopback2 C 12.0.3.0 is directly connected, Loopback3

30.0.0.0/8 [110/74] via 2.2.2.2, 00:08:56, Serial0/1


91 - 9985048840

Page 84 of 182

DEx EIGRP ( external routes) AD value = 170 D EIGRP routes AD value = 90 Here u can see the routes from RIP gets redistributed in EIGRP on R1 and they area learned on R2 as EIGRP external routes task 3 EIGRP into OSPF R2 R2(config)#router ospf 1 R2(config-router)#redistribute EIGRP 100 % Only classful networks will be redistributed R2(config-router)#redistribute EIGRP 100 ? metric Metric for redistributed routes metric-type OSPF/IS-IS exterior metric type for redistributed routes route-map Route map reference subnets Consider subnets for redistribution into OSPF tag Set tag for routes redistributed into OSPF R2(config-router)#redistribute EIGRP 100 subnets R3#sh ip route O E2 1.0.0.0/8 [110/20] via 2.2.2.1, 00:02:42, Serial0/0 C 2.0.0.0/8 is directly connected, Serial0/0 C 3.0.0.0/8 is directly connected, Serial0/1 O 20.0.0.0/8 [110/74] via 2.2.2.1, 00:16:57, Serial0/0 R 40.0.0.0/8 [120/1] via 3.3.3.2, 00:00:07, Serial0/1 O E2 10.0.0.0/8 [110/20] via 2.2.2.1, 00:02:42, Serial0/0 11.0.0.0/24 is subnetted, 4 subnets O E2 11.0.3.0 [110/20] via 2.2.2.1, 00:01:24, Serial0/0 O E2 11.0.2.0 [110/20] via 2.2.2.1, 00:01:24, Serial0/0 O E2 11.0.1.0 [110/20] via 2.2.2.1, 00:01:24, Serial0/0 O E2 11.0.0.0 [110/20] via 2.2.2.1, 00:01:24, Serial0/0 13.0.0.0/24 is subnetted, 4 subnets C 13.0.1.0 is directly connected, Loopback1 C 13.0.0.0 is directly connected, Loopback0 C 13.0.3.0 is directly connected, Loopback3 C 13.0.2.0 is directly connected, Loopback2 C 30.0.0.0/8 is directly connected, FastEthernet0/0 By default ospf uses default metric of 20 for external routes (redistributed routes in to ospf)


91 - 9985048840

Page 85 of 182

If u want to use other than default metric R2(config-router)#redistribute EIGRP 100 subnets metric 1000 R3#sh ip route Gateway of last resort is not set O E2 1.0.0.0/8 [110/1000] via 2.2.2.1, 00:00:03, Serial0/0 C 2.0.0.0/8 is directly connected, Serial0/0 C 3.0.0.0/8 is directly connected, Serial0/1 O 20.0.0.0/8 [110/74] via 2.2.2.1, 00:17:44, Serial0/0 R 40.0.0.0/8 [120/1] via 3.3.3.2, 00:00:27, Serial0/1 O E2 10.0.0.0/8 [110/1000] via 2.2.2.1, 00:00:03, Serial0/0 11.0.0.0/24 is subnetted, 4 subnets O E2 11.0.3.0 [110/1000] via 2.2.2.1, 00:00:03, Serial0/0 O E2 11.0.2.0 [110/1000] via 2.2.2.1, 00:00:03, Serial0/0 O E2 11.0.1.0 [110/1000] via 2.2.2.1, 00:00:03, Serial0/0 O E2 11.0.0.0 [110/1000] via 2.2.2.1, 00:00:03, Serial0/0 13.0.0.0/24 is subnetted, 4 subnets C 13.0.1.0 is directly connected, Loopback1 C 13.0.0.0 is directly connected, Loopback0 C 13.0.3.0 is directly connected, Loopback3 C 13.0.2.0 is directly connected, Loopback2 C 30.0.0.0/8 is directly connected, FastEthernet0/0 Task 4 OSPF IN TO RIP R4 # s how ip route C 3.0.0.0/8 is directly connected, Serial0/0 C 4.0.0.0/8 is directly connected, Serial0/1 C 40.0.0.0/8 is directly connected, FastEthernet0/0 14.0.0.0/24 is subnetted, 4 subnets C 14.0.2.0 is directly connected, Loopback2 C 14.0.3.0 is directly connected, Loopback3 C 14.0.0.0 is directly connected, Loopback0 C 14.0.1.0 is directly connected, Loopback1 No routes being learned here as different protocols are used R3


91 - 9985048840

Page 86 of 182

router rip redistribute ospf 1 metric 5 R4#sh ip route R 1.0.0.0/8 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 R 2.0.0.0/8 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 C 3.0.0.0/8 is directly connected, Serial0/0 C 4.0.0.0/8 is directly connected, Serial0/1 R 20.0.0.0/8 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 C 40.0.0.0/8 is directly connected, FastEthernet0/0 R 10.0.0.0/8 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 11.0.0.0/24 is subnetted, 4 subnets R 11.0.3.0 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 R 11.0.2.0 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 R 11.0.1.0 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 R 11.0.0.0 [120/5] via 3.3.3.1, 00:00:00, Serial0/0 14.0.0.0/24 is subnetted, 4 subnets C 14.0.2.0 is directly connected, Loopback2 C 14.0.3.0 is directly connected, Loopback3 C 14.0.0.0 is directly connected, Loopback0 C 14.0.1.0 is directly connected, Loopback1 R 30.0.0.0/8 [120/5] via 3.3.3.1, 00:00:05, Serial0/0 TASK 5 Check for routes from R4 coming on R1 or not R1#sh ip route Gateway of last resort is not set C 1.0.0.0/8 is directly connected, Serial0/0 C 4.0.0.0/8 is directly connected, Serial0/1 C 10.0.0.0/8 is directly connected, FastEthernet0/0 11.0.0.0/24 is subnetted, 4 subnets C 11.0.3.0 is directly connected, Loopback3 C 11.0.2.0 is directly connected, Loopback2 C 11.0.1.0 is directly connected, Loopback1 C 11.0.0.0 is directly connected, Loopback0 No routes coming from R4 because the redistribution has to be done mutual ( both sides)


91 - 9985048840

Page 87 of 182

Task 6 Redistributing EIGRP in to RIP R4 router rip redistribute EIGRP 100 metric 10 R3#sh ip route O E2 1.0.0.0/8 [110/1000] via 2.2.2.1, 00:08:46, Serial0/0 C 2.0.0.0/8 is directly connected, Serial0/0 C 3.0.0.0/8 is directly connected, Serial0/1 O 20.0.0.0/8 [110/74] via 2.2.2.1, 00:26:27, Serial0/0 R 40.0.0.0/8 [120/1] via 3.3.3.2, 00:00:25, Serial0/1 O E2 10.0.0.0/8 [110/1000] via 2.2.2.1, 00:08:46, Serial0/0 11.0.0.0/24 is subnetted, 4 subnets O E2 11.0.3.0 [110/1000] via 2.2.2.1, 00:08:46, Serial0/0 O E2 11.0.2.0 [110/1000] via 2.2.2.1, 00:08:46, Serial0/0 O E2 11.0.1.0 [110/1000] via 2.2.2.1, 00:08:46, Serial0/0 O E2 11.0.0.0 [110/1000] via 2.2.2.1, 00:08:46, Serial0/0 13.0.0.0/24 is subnetted, 4 subnets C 13.0.1.0 is directly connected, Loopback1 C 13.0.0.0 is directly connected, Loopback0 C 13.0.3.0 is directly connected, Loopback3 C 13.0.2.0 is directly connected, Loopback2 14.0.0.0/24 is subnetted, 4 subnets R 14.0.2.0 [120/10] via 3.3.3.2, 00:00:00, Serial0/1 R 14.0.3.0 [120/10] via 3.3.3.2, 00:00:00, Serial0/1 R 14.0.0.0 [120/10] via 3.3.3.2, 00:00:00, Serial0/1 R 14.0.1.0 [120/10] via 3.3.3.2, 00:00:00, Serial0/1 C 30.0.0.0/8 is directly connected, FastEthernet0/0 Task 7 Redistributing RIP in to OSPF R3 router ospf 1 redistribute rip subnets metric 2500 R2#sh ip route Gateway of last resort is not set C 1.0.0.0/8 is directly connected, Serial0/0


91 - 9985048840

Page 88 of 182

C 2.0.0.0/8 is directly connected, Serial0/1 O E2 3.0.0.0/8 [110/2500] via 2.2.2.2, 00:00:07, Serial0/1 C 20.0.0.0/8 is directly connected, FastEthernet0/0 O E2 40.0.0.0/8 [110/2500] via 2.2.2.2, 00:00:07, Serial0/1 D 10.0.0.0/8 [90/2195456] via 1.1.1.1, 00:28:48, Serial0/0 11.0.0.0/24 is subnetted, 4 subnets D EX 11.0.3.0 [170/8192000] via 1.1.1.1, 00:20:51, Serial0/0 D EX 11.0.2.0 [170/8192000] via 1.1.1.1, 00:20:51, Serial0/0 D EX 11.0.1.0 [170/8192000] via 1.1.1.1, 00:20:51, Serial0/0 D EX 11.0.0.0 [170/8192000] via 1.1.1.1, 00:20:51, Serial0/0 12.0.0.0/24 is subnetted, 4 subnets C 12.0.0.0 is directly connected, Loopback0 C 12.0.1.0 is directly connected, Loopback1 C 12.0.2.0 is directly connected, Loopback2 C 12.0.3.0 is directly connected, Loopback3 14.0.0.0/24 is subnetted, 4 subnets O E2 14.0.2.0 [110/2500] via 2.2.2.2, 00:00:09, Serial0/1 O E2 14.0.3.0 [110/2500] via 2.2.2.2, 00:00:09, Serial0/1 O E2 14.0.0.0 [110/2500] via 2.2.2.2, 00:00:09, Serial0/1 O E2 14.0.1.0 [110/2500] via 2.2.2.2, 00:00:09, Serial0/1 O 30.0.0.0/8 [110/74] via 2.2.2.2, 00:27:21, Serial0/1 Task 8 REDISTRIBUTING OSPF IN TO EIGRP R2 router EIGRP 100 redistribute ospf 1 metric 1544 2000 255 1 1500 R1#sh ip route C 1.0.0.0/8 is directly connected, Serial0/0 D EX 2.0.0.0/8 [170/2681856] via 1.1.1.2, 00:00:17, Serial0/0 D EX 3.0.0.0/8 [170/2681856] via 1.1.1.2, 00:00:17, Serial0/0 C 4.0.0.0/8 is directly connected, Serial0/1 D EX 20.0.0.0/8 [170/2681856] via 1.1.1.2, 00:00:17, Serial0/0 D EX 40.0.0.0/8 [170/2681856] via 1.1.1.2, 00:00:17, Serial0/0 C 10.0.0.0/8 is directly connected, FastEthernet0/0 11.0.0.0/24 is subnetted, 4 subnets C 11.0.3.0 is directly connected, Loopback3 C 11.0.2.0 is directly connected, Loopback2 C 11.0.1.0 is directly connected, Loopback1 C 11.0.0.0 is directly connected, Loopback0 14.0.0.0/24 is subnetted, 4 subnets D EX 14.0.2.0 [170/2681856] via 1.1.1.2, 00:00:18, Serial0/0 D EX 14.0.3.0 [170/2681856] via 1.1.1.2, 00:00:18, Serial0/0


91 - 9985048840

Page 89 of 182

D EX 14.0.0.0 [170/2681856] via 1.1.1.2, 00:00:18, Serial0/0 D EX 14.0.

sikandar ccnp notes

Documents