Professional Documents
Culture Documents
Authored By:
Khawar Butt
CCIE # 12353 Comprehensive Coverage of the CCNP
(R/S, Security, SP, Voice) BSCI Blueprint
Netmetric Solutions
http://www.netmetric-solutions.com
Authored By:
Netmetric Solutions
http://www.netmetric-solutions.com
Definition
Variable-Length Subnet Mask(VLSM): provides the ability to have more than one subnet
mask within your major network. It also allows you to further subnet your already subnetted
networks. Requires Classless Routing Protocols.
Advantages
Efficient Use of IP addresses: Without VLSMs, networks would have to use the same subnet
mask throughout the network. But all your networks don’t have the same number of hosts.
For example: You have 2 LAN connected via a Serial Point-to-point connection. Each LAN has
50 Hosts on it. When you assign the subnet mask, it has to be consistent across your network. So
you end up assign a sub-network address to the WAN connection with 62 hosts, whereas you
only need 2.
Greater Capability for Route Summarization: Route Summarization is covered in detail, later
on in this module.
25 Hosts
25 Hosts
25 Hosts
25 Hosts
In this example, we want to connect the Main Site to the Branch Offices. If we used a fixed
length subnet mask, we would need 4 networks for the LANs and 3 Networks for WANs, a total
of 7 networks. Let us say we have a Class C address of 200.200.200.0 assigned to us. If we need
7 networks, we have to borrow 4 bits, giving us 14 networks. But it will only give us 14 hosts per
network. In order to get around this problem, we will use VLSMs.
In VLSMs, we can get away with borrowing only 3 bits. 3 bits give us 6 usable networks with
30 hosts per network. We will use the first 4 networks for our LAN based networks, and subnet
the fifth one further to give us additional networks with less hosts on each for our WAN
connections. Our WAN connections only require 2 hosts per network and we need 3 Networks.
Decimal Binary
Subnet :200.200.200.10100000 (200.200.200.160)
Mask : 255.255.255.11100000 (255.255.255.224)
We only need 2 hosts per WAN connection. We will borrow a further 3 bits from this
network, leaving only 2 bits for hosts on each network.
So you can choose any 3 of the above network addresses for the WAN connections.
200. 200.200.32/ 27
200. 200.200.164/30
25 Hosts
25 Hosts 200. 200.200.168/30
200. 200.200.64/ 27
25 Hosts
200. 200.200.96/ 27
200. 200.200.172/30
Exercise 1
25 Hosts
5 Hosts
25 Hosts
5 Hosts
5 Hosts
Definition
Route Summarization: reduces the number of routes that a router must maintain because it
represents a series of network numbers in a single summary address.
Advantages
Routing Table
150. 50. 33. 0/24 150. 50. 33. 0/24
150. 50. 34. 0/24
150. 50. 35. 0/24
Let us say that we the following networks connected to a Router named LA:
150.50.64.0/24
150.50.65.0/24
150.50.66.0/24
150.50.67.0/24
150.50.68.0/24
150.50.69.0/24
150.50.70.0/24
150.50.71.0/24
LA is connected to another router SD. LA wants to minimize the number of entries it sends to
SD.
150.50.01000000.00000000 (150.50.64.0)
150.50.01000001.00000000 (150.50.65.0)
150.50.01000010.00000000 (150.50.66.0)
150.50.01000011.00000000 (150.50.67.0)
150.50.01000100.00000000 (150.50.68.0)
150.50.01000101.00000000 (150.50.69.0)
150.50.01000110.00000000 (150.50.70.0)
150.50.01000111.00000000 (150.50.71.0)
Starting from High order bits towards low order bits (Left to Right), look at the bits that are
common and draw a line.
150.50.01000000.00000000 (150.50.64.0)
150.50.01000001.00000000 (150.50.65.0)
150.50.01000010.00000000 (150.50.66.0)
150.50.01000011.00000000 (150.50.67.0)
150.50.01000100.00000000 (150.50.68.0)
150.50.01000101.00000000 (150.50.69.0)
150.50.01000110.00000000 (150.50.70.0)
150.50.01000111.00000000 (150.50.71.0)
The summarized address will be address you get from the common high order bits.
150.50.01000000.00000000 (150.50.64.0).
Your Subnet mask will the number of common bits, which is 16 + 16 + 5 = 21
Exercise 1
131.107.1.192/28 131.107.1.208/28
LA SF
131.107.1.64/28 131.107.1.80/28
OC 131.107.1.128/28
131.107.1.144/28
131.107.1.160/28
131.107.1.96/28 131.107.1.176/28
SD
131.107.1.112/28
Exercise 2
131.107.1.128/28 131.107.1.144/28
LA SF
131.107.1.176/28 131.107.1.160/28
131.107.1.64/28
OC 131.107.1.80/28
131.107.1.96/28
131.107.1.112/28
131.107.1.192/28
SD 131.107.1.208/28
131.107.1.48/28
Authored By:
Khawar Butt
CCIE # 12353 Module 2 - RIP Ver 1 Labs
(R/S, Security, SP, Voice)
Netmetric Solutions
http://www.netmetric-solutions.com
Copyrights Netmetric Solutions 2006-2010
Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com
Page 11 of 207
Lab 1 – Basic RIP Configuration
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
R1 Configuration
R2 Configuration
On R1
router#conf t
router(config)#hostname R1
R1(config)#Router RIP
R1(config-router)#no auto-summary
R1 (config-router)#net 1.0.0.0
R1 (config-router)#net 192.1.12.0
On R2
Router#conf t
On Both Routers
Objective: Looking at the operation of RIP v1. You will take a look at the
Broadcast classfull updates. You will also take a look at the effect of Passive-
Interface command and the effect of turning off Split Horizon.
On Both Routers
Interesting Facts
On R1
R1(config)#int loopback 0
R1(config-if)#shut
When a route goes down, the router does not wait for Periodic Update. It
sends a Triggered update with a Poisoned route with a metric of 16
Notice R2 also sends an immediate Triggered Update back, indicating
that you can’t reach 10.0.0.0 cannot be reached through it.
On R1
R1(config)#int loopback 0
R1(config-if)#no shut
On Both Routers
Rx(Config)#int s 0/0
Rx(Config-if)#no ip split-horizon
Interesting Facts
• The router is advertising all routes. Even the ones that it learned from
the same router. The reason it does make it to the routing table is
because the Router has a better metric to the route.
Passive Interfaces
On Both Routers
Rx(config)#router rip
Rx(config-router)#passive interface Loopback 0
Interesting Facts
The router stops advertising from the Loopback interface. The command
is useful for cutting down unnecessary broadcast over an interface that
only has hosts on it and no router.
Objective: Turn Spilt-Horizon back on. You would like to send Unicast updates
between R1 and R2 instead of Broadcast updates.
On Both Routers
Rx(Config)#int s 0/0
Rx(Config-if)#ip split-horizon
On R1
R1(config)#Router rip
R1(config-router)#passive interface S 0/0
R1(config-router)#neighbor 192.1.12.2
On R2
R2(config)#Router rip
R2(config-router)#passive interface S 0/0
R2(config-router)#neighbor 192.1.12.1
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
S 0/0 (.3) L0 3.3.3.3/8
L0 4.4.4.4/8
R4 R3
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
Objective: R1 is acting as the ISP and R2 is the Edge Router for a company
that is running RIP internally between R2, R3 and R4. R1 will have static
routes towards all the company networks. R2 will have a default route pointing
towards R1.
On R1
R1#conf t
R1(config)#ip route 2.0.0.0 255.0.0.0 192.1.12.2
R1(config)#ip route 3.0.0.0 255.0.0.0 192.1.12.2
R1(config)#ip route 4.0.0.0 255.0.0.0 192.1.12.2
R1(config)#ip route 192.1.23.0 255.255.255.0 192.1.12.2
R1(config)#ip route 192.1.34.0 255.255.255.0 192.1.12.2
On R2
R2#conf t
R2(config)# ip route 0.0.0.0 0.0.0.0 192.1.12.1
R2(config)#Router RIP
R2(config-router)#no auto-summary
R2(config-router)#net 2.0.0.0
R2(config-router)#net 192.1.12.0
R2(config-router)#net 192.1.23.0
On R3
R3#conf t
R3(config)#Router RIP
R3(config-router)#no auto-summary
R3(config-router)#net 3.0.0.0
R3(config-router)#net 192.1.23.0
R3(config-router)#net 192.1.34.0
On R4
R4#conf t
On R3 and R4
• Type Show IP route. Do you see an entry learned through RIP that has
a *?
• By default, RIP will advertise the default route to other RIP enabled
routers.
• Enter Debug IP RIP and view the routing table entries going from R2 to
R3 and R4.
On R2
On R3 and R4
Type Show IP route. Do you see an entry learned through RIP that has a
*?
Enter Debug IP RIP and view the routing table entries going from R2 to R3
and R4.
Authored By:
Khawar Butt
CCIE # 12353 Module 3 - RIP Ver 2 Labs
(R/S, Security, SP, Voice)
Netmetric Solutions
http://www.netmetric-solutions.com
R1 S 0/0(.1) 192.1.12.0/2 R2
S 0/0 (.2)
L0 1.1.1.1/8 L0 2.2.2.2/8
R1 Configuration
R2 Configuration
On R1
router#conf t
router(config)#hostname R1
R1(config)#Router RIP
R1(config-router)#no auto-summary
R1(config-router)#version 2
R1 (config-router)#net 1.0.0.0
R1 (config-router)#net 192.1.12.0
On R2
Router#conf t
router(config)#hostname R2
R2(config)#Router RIP
On Both Routers
Objective: Looking at the operation of RIP v2. You will take a look at the
Multicast classless updates.
On Both Routers
Interesting Facts
• Update is a V2 Update
• Includes the Subnet Mask
• The destination address.
R1 S 0/0(.1) 192.1.12.0/2 R2
S 0/0 (.2)
L0 1.1.1.1/8 L0 2.2.2.2/8
E 0/0 (.2)
192.1.23.0/2
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/2
S 0/0 (.3)
L0 4.4.4.4/8 L0 3.3.3.3/8
R4 R3
R1 Configuration
R2 Configuration
R3 Configuration
Objective: R3 does not support RIP v2. Configure R1, R2 and R4 with RIP v2.
Configure R3 with RIP V1. Allow R2 and R4 to exchange routes with R3.
On R1
R1#conf t
R1(config)#Router RIP
R1(config-router)#no auto-summary
R1(config-router)#version 2
R1(config-router)#net 192.1.12.0
R1(config-router)#net 1.0.0.0
On R2
R2#conf t
R2(config)#Router RIP
R2(config-router)#no auto-summary
R2(config-router)#version 2
R2(config-router)#net 192.1.12.0
R2(config-router)#net 192.1.23.0
R2(config-router)#net 2.0.0.0
R2(config-router)#Interface E 0/0
R2(config-if)#ip rip send v1
R2(config-if)#ip rip receive v1
On R3
R3#conf t
R3(config)#Router RIP
R3(config-router)#no auto-summary
R3(config-router)#version 1
R3(config-router)#net 192.1.23.0
R3(config-router)#net 192.1.34.0
R3(config-router)#net 3.0.0.0
On R4
On R2
R1
(Requires no change)
R2
R2(config)#interface E 0/0
R2(config-if)#no ip rip send version 1
R2(config-if)#no ip rip receive version 1
R3
R3(config)#Router RIP
R3(config-router)#version 2
R4
R4(config)#interface S 0/0
R4(config-if)#no ip rip send version 1
R4(config-if)#no ip rip receive version 1
R1
R1(config)#key chain KC-1
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string CISCO
R1(config-keychain-key)#exit
R2
R3
R4
R1
R1#config t
R1(config)#int S 0/0
R1(config-if)#ip rip authentication mode md5
R2
R2#config t
R2(config)#int S 0/0
R2(config-if)#ip rip authentication mode md5
R2(config-if)#int E 0/0
R2(config-if)# ip rip authentication mode md5
R3
R3#config t
R3(config)#int E 0/0
R3(config-if)#ip rip authentication mode md5
R3(config)#int S 0/0
R3(config-if)#ip rip authentication mode md5
R4
R4#config t
R4(config)#int S 0/0
R4(config-if)#ip rip authentication mode md5
• Can you see the authentication happening and if so, can you see the
actual password?
Authored By:
Netmetric Solutions
http://www.netmetric-solutions.com
Features
• Security: With IOS version 11.3 or better, EIGRP can authenticate using
only MD5, the reason EIGRP does not support clear text is because,
• Multiple Network Layer Protocol Support: EIGRP can support IP, IPX,
and AppleTalk, whereas the other routing protocols support only one
routed protocol. EIGRP will also perform auto-redistribution with NLSP,
IPXRIP, RTMP. EIGRP supports incremental SAP and RIP updates, 224
HOPS, and it uses bandwidth + delay which is far more better than just
Ticks and Hops used by IPXRIP. For RTMP it supports event driven
updates, but it must run in a clientless networks(WAN), and also a better
metric calculation.
• Unequal and Equal Cost Path Load-Balancing: This feature will enable
the administrators to distribute traffic flow in the network. By default
EIGRP will use up to 4 paths and this can be increased to 6.
• OSI and EIGRP: Like all TCP/IP routing protocols EIGRP relies in IP to
deliver the packets, EIGRP maps to the transport layer of OSI and uses
protocol number 88.
• 100% Loop Free: EIGRP uses DUAL to attain fast convergence while
maintaining a totally loop free topology at every instance.
R-B
S 0/0 10.2.1.2/30
S 0/0 10.1.1.1/30
R-C
R-A
S 0/1 10.3.1.2/30
S 0/1 10.4.1.1/30
R-D
In the above diagram, the minute the Ethernet port on R-A comes
active, it notifies R-B, and R-D with its own vector metric, R-D, and
R-B will adjust these values based on the parameters of their
interface to R-A, and then they will advertise that cost to R-C.
EIGRP uses the same formula as IGRP to calculate its composite
metric, with one difference and that is EIGRP scales the metric
component by 256 to achieve a finer metric granularity. This
metric is calculated using Bandwidth, Delay, Reliability, Load, and
MTU. The formula that it uses is as follows:
You can view the detailed vector and composite metric of a single
EIGRP route from the topology table with the following command:
Metric = [107/Bandwidth(min))+(Delay(Sum)]/10)]*256
• To find out the value of bandwidth and the delay associated to a given
interface, “ sh interface < the interface type > x “ where x is the
interface number.
• Neighbor table: Each Eigrp router has a neighbor table that has a list of
adjacent routers. Neighbor relationships ensure a bi-directional
communication between each of the directly connected neighbor.
• Routing Table: Eigrp uses the best path to a given destination (the
Successor/s) from the topology table and places it into the routing table.
• Upstream: This router is further away from the destination than the
local router. This router will use the local router to get to the destination.
• Hello: Used for neighbor discovery process. Hello packets are sent as
multicasts, and they use unreliable delivery meaning that they do not
need an ACK, as long as these packets are received the routers can
determine that the neighbor is up.
Authored By:
Khawar Butt
CCIE # 12353 Module 4 - EIGRP Labs
(R/S, Security, SP, Voice)
Lab 1 – Configur
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
Netmetric Solutions
Copyrights Netmetric Solutions 2006-2010
Website: http://www.netmetric-solutions.com;
http://www.netmetric-solutions.com Email: khawarb@khawarb.com
Page 40 of 207
R1 Configuration
R2 Configuration
On R1
R1(config)#Router eigrp 12
R1 (config-router)#net 1.0.0.0
R1 (config-router)#net 192.1.12.0
On R2
R2(config)#Router eigrp 12
R2 (config-router)#net 2.0.0.0
R2 (config-router)#net 192.1.12.0
• Type SH IP ROUTE
• See how the Hello # are changing and updates are not.
• Note the Values in the output. See how the queries number increased
On Both Routers
R1(config)#int S 0/0
R1(config-if)#ip hello-interval eigrp 12 20
R1(config-if)#ip hold-time eigrp 12 60
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
S 0/0 (.3) L0 3.3.3.3/8
L0 4.4.4.4/8
R4 R3
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
On R1
R1(config)#Router eigrp 1
R1(config-router)#net 1.0.0.0
R1(config-router)#net 192.1.12.0
On R2
R2(config)#Router eigrp 1
R2(config-router)#net 2.0.0.0
R2(config-router)#net 192.1.12.0
R2(config-router)#net 192.1.23.0
On R3
R3(config)#Router eigrp 1
R3(config-router)#net 3.0.0.0
R3(config-router)#net 192.1.23.0
R3(config-router)#net 192.1.34.0
On R4
R4(config)#Router eigrp 1
R4(config-router)#net 4.0.0.0
R4(config-router)#net 192.1.34.0
• Type SH IP ROUTE
On R1 and R2
• Type SH IP ROUTE
Rx(config)#Router eigrp 1
Rx(config-router)#Passive-interface S 0/0
• With RIP, the passive-interface command RIP doesn’t send updates but
continue to receive routes.
On R1
R1(config)#Router eigrp 1
R1(config-router)#Neighbor 192.1.12.2
On R2
R2(config)#Router eigrp 1
R2(config-router)#Neighbor 192.1.12.1
On R1 and R2
• Type SH IP ROUTE
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
E 0/0 (.2)
E 0/0 (.1)
192.1.23.0/24
192.1.14.0/24
E 0/0 (.3)
E 0/0 (.4)
L0 4.4.4.4/8 L0 3.3.3.3/8
S 0/0(.4)
S 0/0 (.3)
192.1.34.0/24
R4 R3
Objective: Configure the Ethernet link between R1 and R4. Configure the
Variance command to support unequal cost load balancing. This lab shows you
the Feasible Condition come into play.
R1 Configuration
R4 Configuration
On R1
R1(config)#Router eigrp 1
R1(config-router)#net 192.1.14.0
On R4
R4(config)#Router eigrp 1
R4(config-router)#net 192.1.14.0
On R1
R1(config)#Interface S 0/0
R1(config-if)#bandwidth 128
R1(config-if)#Interface E 0/0
R1(config-if)#bandwidth 64
R1(config-if)#delay 2000
On R2
R2(config)#Interface E 0/0
R2(config-if)#bandwidth 512
R2(config-if)#delay 2000
R2(config-if)#Interface S 0/0
R2(config-if)#bandwidth 128
R3(config)#Interface E 0/0
R3(config-if)#bandwidth 512
R3(config-if)#delay 2000
R3(config-if)#Interface S 0/0
R3(config-if)#bandwidth 256
On R4
R4(config)#Interface E 0/0
R4(config-if)#bandwidth 64
R4(config-if)#delay 2000
R4(config-if)#Interface S 0/0
R4(config-if)#bandwidth 256
• Note you have 2 ways to get to the diagonally opposite loopback networks
On All Routers
Rx(config)#Router EIGRP 1
Rx(config-router)#Variance xx
On All Routers
• Type SH IP ROUTE.
• If not, Why?
L0 10.1.4.0 – R2 L0 10.1.8.0 –
R1 S 0/0(.1) 192.1.12.0/24 L3 10.1.11.0/24
L3 10.1.7.0/24 S 0/0 (.2)
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
L0 10.1.16.0 – S 0/0(.4) 192.1.34.0/24
L3 10.1.19.0/24 S 0/0 (.3)
L0 10.1.12.0 –
R4 R3 L3 10.1.15.0/24
Group B
R1 Configuration
R3 Configuration
R4 Configuration
R1 on Both Groups
R1(config)#Router eigrp 1
R1(config-router)#net 10.0.0.0
R1(config-router)#net 192.X.12.0
R1(config-router)#no auto-summary
R2 on Both Groups
R2(config)#Router eigrp 1
R2(config-router)#net 10.0.0.0
R2(config-router)#net 192.X.12.0
R2(config-router)#net 192.X.23.0
R3 on Both Groups
R3(config)#Router eigrp 1
R3(config-router)#net 10.0.0.0
R3(config-router)#net 192.X.23.0
R3(config-router)#net 192.X.34.0
R3(config-router)#no auto-summary
R4 on Both Groups
R4(config)#Router eigrp 1
R4(config-router)#net 10.0.0.0
R4(config-router)#net 192.X.34.0
R4(config-router)#no auto-summary
• Get together with your group and figure out a summarization for the
Border router (Router connecting to the backbone).
• Write it down
• Router(config)#int E 0/1
• Type SH IP ROUTE
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
S 0/0 (.3) L0 3.3.3.3/8
L0 4.4.4.4/8
R4 R3
R1 Configuration
R2 Configuration
R3 Configuration
Objective: R1 is acting as the ISP and R2 is the Edge Router for a company
that is running EIGRP internally between R2, R3 and R4. R1 will have static
routes towards all the company networks. R2 will have a default route pointing
towards R1. R2 should inject the default route into R3 and R4.
On R1
On R2
On R3
R3(config)#Router EIGRP 1
R3(config-router)#no auto-summary
R3(config-router)#net 3.0.0.0
R3(config-router)#net 192.1.23.0
R3(config-router)#net 192.1.34.0
On R4
R4(config)#Router EIGRP 1
R4(config-router)#no auto-summary
R4(config-router)#net 4.0.0.0
R4(config-router)#net 192.1.34.0
On R2
• Does it work?
On R3 and R4
• Does it work?
• Type SH IP ROUTE
• Do you have any routes to the 1.1.1.1 or any Default gateway set?
On R2
R2(config)#router eigrp 1
R2(config-router)#redistribute static metric 10000 1000 255 1 1500
On R3 and R4
• Type SH IP ROUTE
Objective: This lab is based on the previous lab. R2 will have a default route
pointing towards R1. R2 should inject the default route into R3 and R4 using
the Summary address command instead of Route Redistribution.
On R2
R1(config)#router eigrp 1
R1(config-router)#no redistribute static metric 10000 1000 255 1 1500
On R3 and R4
• Does it work?
• Type SH IP ROUTE
On R2
R2(config)#int E 0/0
R2(config-if)#ip summary-address eigrp 1 0.0.0.0 0.0.0.0
On R3 and R4
• Type Ping 4.4.4.4
R1 192.1.12.0/24 R2
L0 1.1.1.1/8 S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L1 11.11.11.11/8
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
S 0/0 (.3) L0 3.3.3.3/8
L0 4.4.4.4/8
R4 R3
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
Objective: Inject the 1.0.0.0 and 11.0.0.0 networks into EIGRP without using
the Network command.
On R1
R1(config)#Router EIGRP 1
R1(config-router)#no auto-summary
R1(config-router)#network 192.1.12.0
On R2
R2(config)#Router EIGRP 1
R2(config-router)#no auto-summary
R2(config-router)#net 2.0.0.0
R2(config-router)#net 192.1.12.0
R2(config-router)#net 192.1.23.0
On R3
R3(config)#Router EIGRP 1
R3(config-router)#no auto-summary
R3(config-router)#net 3.0.0.0
R3(config-router)#net 192.1.23.0
R3(config-router)#net 192.1.34.0
On R4
R4#conf t
R4(config)#Router EIGRP 1
R4(config-router)#no auto-summary
On R1
R1(config)#router eigrp 1
R1(config-router)#redistribute connected
On R2, R3 and R4
• Type SH IP ROUTE
Remove eigrp 1 from R1. Remove network 192.1.12.0 and 2.0.0.0 from
EIGRP 1 on R2. Run EIGRP 11 between R1 and R2. Advertise the
Loopbacks on both the Routers in EIGRP 11.
On R1
On R2
R2(config)#router eigrp 1
R2(config-router)#no net 2.0.0.0
R2(config-router)#no net 192.1.12.0
R2(config-router)#Router eigrp 11
R2(config-router)#net 192.1.12.0
R2(config-router)#net 2.0.0.0
On R1, R3 and R4
• Type SH IP ROUTE
On R2
R2(config)#router eigrp 1
R2(config-router)#redistribute eigrp 11
On R1, R2 and R4
• Type SH IP ROUTE
Objective: Performing Redistribution between RIP and EIGRP Run RIP between
R1 and R2. Run EIGRP in AS 1 between R2, R3 and R4.
On R1
On R2
On R1, R3 and R4
• Type SH IP ROUTE
On R3
R3(config)#router eigrp 1
R3(config-router)#redistribute rip metric 10000 1000 255 1 1500
R3(config-router)#router rip
• Type SH IP ROUTE
Objective: This lab builds on the configuration of the previous labs. We will
add some new routes on R1 and R4 and inject them into the appropriate
protocols. We will filter certain routes from getting redistributed into the other
routing protocol
R1
R4
On R1
R1(config)#interface Loopback 11
R1(config-if)#ip address 11.0.0.1 255.0.0.0
R1(config-if)#interface Loopback 12
R1(config-if)#ip address 12.0.0.1 255.0.0.0
R1(config)#interface Loopback 13
R1(config-if)#ip address 13.0.0.1 255.0.0.0
R1(config)#interface Loopback 14
R1(config-if)#ip address 14.0.0.1 255.0.0.0
R1(config-if)#router rip
R1(config-router)#net 11.0.0.0
R1(config-router)#net 12.0.0.0
R1(config-router)#net 13.0.0.0
On R4
R4(config)#interface Loopback 15
R4(config-if)#ip address 15.0.0.1 255.0.0.0
R4(config-if)#interface Loopback 16
R4(config-if)#ip address 16.0.0.1 255.0.0.0
R4(config)#interface Loopback 17
R4(config-if)#ip address 17.0.0.1 255.0.0.0
R4(config)#interface Loopback 18
R4(config-if)#ip address 18.0.0.1 255.0.0.0
R4(config-if)#Router eigrp 1
R4(config-router)#net 15.0.0.0
R4(config-router)#net 16.0.0.0
R4(config-router)#net 17.0.0.0
R4(config-router)#net 18.0.0.0
On R1, R3 and R4
• Type SH IP ROUTE
On R2
On R3 and R4
• Type SH IP ROUTE
On R1
• Type SH IP ROUTE
Objective: R1 and R2 will not be running any routing protocol between them.
R1 will use a default route pointing towards R2. R2 will create static routes for
the R1 networks. You would like to inject some of these static routes into the
already running EIGRP instance between R2, R3 and R4.
On R1
On R2
On R2
• Type SH IP ROUTE
• Verify that you see all the static routes except the 11.0.0.0 and 14.0.0.0
networks
Objective: Use MD5 to authenticate the Routers that are running EIGRP
On R2
On R3
On R4
On R2
R2(config)#int E 0/0
R2(config-if)#ip authentication key-chain eigrp 1 KC-1
R2(config-if)#ip authentication mode eigrp 1 md5
On R3
R3(config)#int E 0/0
R3(config-if)#ip authentication key-chain eigrp 1 trinet
R3(config-if)#ip authentication mode eigrp 1 md5
R3(config-if)#int S 0/0
R3(config-if)#ip authentication key-chain eigrp 1 trinet
R3(config-if)#ip authentication mode eigrp 1 md5
R4(config)#int S 0/0
R4(config-if)#ip authentication key-chain eigrp 1 trinet
R4(config-if)#ip authentication mode eigrp 1 md5
On R2, R3 and R4
• Type Debug
eigrp packet
• Notice the
authentication is md5
Authored By:
Khawar Butt
CCIE # 12353 Module 5 - OSPF
(R/S, Security, SP, Voice)
Open Shortest P
History
• OSPF Version 1
was specified in
RFC 1131 in
1988. This
protocol was
finalized in
1989.
• OSPF Version 2
(Current
version). The
most recent
Netmetric Solutions
Copyrights Netmetric Solutions 2006-2010
Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com
http://www.netmetric-solutions.com
Page 74 of 207
specifications are specified in RFC 2328.
OSPF Features
Areas
Router Types
Link State: The status of a link between two routers, that is, a router’s
interface and its relationship to its neighboring routers. The link states are
advertised to other routers in a special packet called link-state advertisements
(LSA).
Router ID:
• A 32-bit number assigned to each OSPF enabled router.
• It’s used to uniquely identify a router within an Autonomous System.
• Its calculated at boot time
• It’s the highest Loopback address on a Router. If there is no loopback
configured, it will be the highest configured address on the router.
Broadcast Networks
For the Election process to function properly, the following conditions must
exist:
Point-to-point Networks
• Large Routing Table: Each router would need to maintain at least one
entry per network, and if we have provided redundancy to some of the
links, then more entries will be found in the routing table.
• If one of the areas is having a flapping link, it will not have an effect on
the other areas, because the traffic will always be restricted to that area
If you summarization is performed on the ABR.
Benefits
• Routers
• LSAs
• Areas
• Virtual-Links
1. LSA Type 1:
2. LSA Type 2:
3. LSA Type 3:
4. LSA Type 4:
5. LSA Type 5:
6. LSA Type 6:
7. LSA Type 7:
3. Stub Area:
5. Not-So-Stubby:
Authored By:
Khawar Butt
CCIE # 12353 Module 5 - OSPF Labs
(R/S, Security, SP, Voice)
Lab 1 – OSPF
Netmetric Solutions
Copyrights Netmetric Solutions 2006-2010
Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com
http://www.netmetric-solutions.com
Page 90 of 207
R1 R2
L0 1.1.1.1/8 L0 2.2.2.2/8
L0 192.1.100.0/24
R3
R4
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
On R1
R1(config)#Router ospf 1
R1 (config-router)#net 1.0.0.0 0.255.255.255 area 0
R1 (config-router)#net 192.1.100.0 0.0.0.255 area 0
On R2
R2(config)#Router ospf 1
R2 (config-router)#net 2.0.0.0 0.255.255.255 area 0
R2 (config-router)#net 192.1.100.0 0.0.0.255 area 0
On R3
R3(config)#Router ospf 1
R3 (config-router)#net 3.0.0.0 0.255.255.255 area 0
R3 (config-router)#net 192.1.100.0 0.0.0.255 area 0
On R4
R4(config)#Router ospf 1
R4 (config-router)#net 4.0.0.0 0.255.255.255 area 0
R4 (config-router)#net 192.1.100.0 0.0.0.255 area 0
State:
Init State First Hello is sent
2-Way Neighbor discovered, but adjacency not built
Exstart Neighbor’s form a Master/Slave Relationship. Based on the
Highest IP address. Initial sequence number established
Exchange The router’s exchange Database Description packets to tell
each other about the routes it knows about. A request list is
created.
Format:
Displays all the Network LSA’s received by your router. Send out by the DR.
Includes the following information:
o DR Address
o All the attached routers of the area
Interface Cost
FDDI/Fast Ethernet 1
Loopback 1
HSSI 2
16 M Token Ring 6
Ethernet 10
4 M Token Ring 25
Serial 64
Command Explanation
IP OSPF COST [Value] Changes the default cost of an
Interface
IP OSPF Hello-Interval [Value] Change the Hello-interval
IP OSPF Dead-Interval [Value] Changes the Dead-interval
IP OSPF Priority [Value] Changes the Priority. Used in forcing
one of the router’s to be the DR or
BDR
auto-cost reference-bandwidth Used when you have a Gigabit
Ethernet connection and 108 does not
work correctly.
Debug IP OSPF Packet Shows all packets for OSPF
Debug IP OSPF Adj Displays the Hello packets and DR and
BDR Election
On R1
R1(config)#Int E 0/0
R1(config-if)#IP OSPF priority 100
R1(config-if)#shut
On R2
R2(config)#Int E 0/0
R2(config-if)#IP OSPF priority 50
R2(config-if)#shut
On R3
R3(config)#Int E 0/0
R3(config-if)#IP OSPF priority 0
R3(config-if)#shut
On R4
R4(config)#Int E 0/0
R4(config-if)#IP OSPF priority 0
R4(config-if)#shut
• Use Up arrow key and Enter to keep on repeating the commands and see
the state of the routers going from Init to Full. Also note the Roles of the
Routers
• Type SH IP OSPF INT E 0/0 to see the DR and BDR for the Network.
• Type U ALL
On RI and R2
Rx(config)#Int E 0/0
Rx(config-if)#IP OSPF authentication-key Cisco
Rx(config-if)#IP OSPF authentication
On All Routers
• Type SH IP Route
• Notice R1 and R2 talk to each other and R3 and R4 only see the directly
connected networks
ON R3 and R4
Rx(config)#Int E 0/0
Rx(config-if)#IP OSPF authentication-key Cisco
• Type U ALL
On All Routers
Rx(config)#Int E 0/0
Rx(config-if)#IP OSPF message-digest-key 1 md5 ccnp
Rx(config-if)#IP OSPF authentication message-digest
On All Routers
• Type SH IP Route
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
R1 Configuration
R2 Configuration
On R1
R1(config)#Router ospf 1
R1 (config-router)#net 1.0.0.0 0.255.255.255 area 0
R1 (config-router)#net 192.1.12.0 0.0.0.255 area 0
On R2
R2(config)#Router ospf 1
R2 (config-router)#net 2.0.0.0 0.255.255.255 area 0
R2 (config-router)#net 192.1.12.0 0.0.0.255 area 0
• Type SH IP ROUTE
• No Type 2 LSA (Network LSA’s) are displayed. Type 2 LSA’s are only
displayed for Broadcast Multi-access(BMA) or Non-Broadcast Multi-
access Networks(NBMA).
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
S 0/0 (.3) L0 3.3.3.3/8
L0 4.4.4.4/8
R4 R3
R1 Configuration
R2 Configuration
R3 Configuration
Objective: Configuring OSPF with P-2-P and Ethernet networks. You also take
a look at the LSA Database
On R1
R1(config)#Router ospf 1
R1(config-router)#net 1.0.0.0 0.255.255.255 area 0
R1(config-router)#net 192.1.12.0 0.0.0.255 area 0
On R2
R2(config)#Router ospf 1
R2(config-router)#net 2.0.0.0 0.255.255.255 area 0
R2(config-router)#net 192.1.12.0 0.0.0.255 area 0
R2(config-router)#net 192.1.23.0 0.0.0.255 area 0
On R3
R3(config)#Router ospf 1
R3(config-router)#net 3.0.0.0 0.255.255.255 area 0
R3(config-router)#net 192.1.23.0 0.0.0.255 area 0
R3(config-router)#net 192.1.34.0 0.0.0.255 area 0
On R4
R4(config)#Router ospf 1
R4(config-router)#net 4.0.0.0 0.255.255.255 area 0
R4(config-router)#net 192.1.34.0 0.0.0.255 area 0
• Type SH IP ROUTE
• How many Neighbors do you see and What are their States and
Designations
(Builds on Lab 6)
Objective: Performing Mutual Redistribution between RIP and OSPF. Run RIP
between R1 and R2. Run OSPF between R2, R3 and R4.
On R1
On R2
R2(config)#Router rip
R2(config-router)#net 2.0.0.0
R2(config-router)#net 192.1.12.0
R2(config-router)#router ospf 1
R2(config-router)#no net 192.1.12.0 0.0.0.255 area 0
R2(config-router)#no net 2.0.0.0 0.255.255.255 area 0
On All Router’s
• Type SH IP ROUTE
On R2
R2(config)#router rip
R2(config-router)#redistribute ospf 1 metric 2
On All Router’s
Redistribute RIP into OSPF and OSPF into RIP Using E1 routes
On R2
R2(config)#router ospf 1
R2(config-router)#no redistribute rip metric 10
R2(config-router)#redistribute rip metric 10 metric-type 1
On All Router’s
(Builds on Lab 7)
On R1
On R2
On All Router’s
• Type SH IP ROUTE
On R2
R2(config)#router eigrp 1
R2(config-router)#redistribute ospf 1 metric 1544 2000 255 1 1500
R2(config-router)#router ospf 1
On All Router’s
On R1
On R2
On All Router’s
• Type SH IP ROUTE
On R2
R2(config-router)#router ospf 1
R2(config-router)#redistribute static metric-type 1 subnets
On All Router’s
• Type SH IP ROUTE on R3 and R4. Do you see another Type of Route?
• Ping 1.1.1.1 from R3 and R4. Can you ping?
On R2
R2(config)#int loo 5
R2(config-if)#ip addr 5.5.5.5 255.0.0.0
R2(config-if)#int loo 6
R2(config-if)#ip addr 6.6.6.6 255.0.0.0
R2(config-if)#int loo 7
R2(config-if)#ip addr 7.7.7.7 255.0.0.0
On All Router’s
• Type SH IP ROUTE
On R2
On R2
On All Router’s
• Type SH IP ROUTE
• Do you see a 0.0.0.0 route in the routing table of R3 and R4. Is the
Gateway of Last resort set?
R3
R2
Frame-Relay
On R1
R1(config)#int S 0/0
R1(config-if)#ip address 192.1.123.1 255.255.255.0
R1(config-if)#encapsulation frame-relay
R1(config-if)#frame-relay map ip 192.1.123.2 102 broadcast
R1(config-if)#frame-relay map ip 192.1.123.3 103 broadcast
R1(config-if)#no shut
R1(config-if)#int loopback 0
R1(config-if)#ip address 1.1.1.1 255.0.0.0
R1(config)#Router ospf 1
R1(config-router)#net 1.1.1.1 0.0.0.0 area 0
R1(config-router)#net 192.1.123.0 0.0.0.255 area 0
On R2
R2(config)#int S 0/0
R2(config-if)#ip address 192.1.123.2 255.255.255.0
R2(config-if)#encapsulation frame-relay
R2(config-if)#frame-relay map ip 192.1.123.1 201 broadcast
R2(config-if)#frame-relay map ip 192.1.123.3 201
R2(config-if)#no shut
R2(config-if)#int loopback 0
R2(config-if)#ip address 2.2.2.2 255.0.0.0
R2(config)#Router ospf 1
R2(config-router)#net 2.2.2.2 0.0.0.0 area 0
R2(config-router)#net 192.1.123.0 0.0.0.255 area 0
On R3
R3(config)#int S 0/0
R3(config-if)#ip address 192.1.123.3 255.255.255.0
R3(config-if)#encapsulation frame-relay
R3(config-if)#frame-relay map ip 192.1.123.1 301 broadcast
R3(config-if)#frame-relay map ip 192.1.123.2 301
R3(config-if)#no shut
R3(config-if)#int loopback 0
On All Routers
Type SH IP ROUTE
What type of network is it? Does it send the OSPF routing packets?
On R2 and R3
Rx(config)#int S 0/0
Rx(config-if)#shut
Rx(config-if)# IP OSPF Network broadcast
Rx(config-if)# IP OSPF priority 0
Rx(config-if)#no shut
On R1
R1(config)#int S 0/0
R1(config-if)#shut
R1(config-if)# IP OSPF Network broadcast
Rx(config-if)#no shut
• Type SH IP ROUTE
Objective: Configure OSPF to run over a NBMA network by using the Neighbor
command
On All Routers
Rx(config)#int S 0/0
Rx(config-if)#sh
Rx(config-if)# NO IP OSPF network broadcast
Rx(config-if)#no shut
On All Routers
• Type SH IP ROUTE
On R1
R1(config)#router ospf 1
R1(config-router)#neighbor 192.1.123.2
R1(config-router)#neighbor 192.1.123.3
R2(config)#router ospf 1
R2(config-router)#neighbor 192.1.123.1
On R3
R3(config)#router ospf 1
R3(config-router)#neighbor 192.1.123.1
On All Routers
• Type SH IP ROUTE
On R1
R1(config)#router ospf 1
R1(config-router)#no neighbor 192.1.123.2
R1(config-router)#no neighbor 192.1.123.3
On R2
R2(config)#router ospf 1
R2(config-router)#no neighbor 192.1.123.1
On R3
R3(config)#router ospf 1
R3(config-router)#no neighbor 192.1.123.1
On All Routers
• Type SH IP ROUTE
On R1
R1(config)#int S 0/0
R1(config-if)#sh
R1(config-if)#IP ospf network point-to-multipoint
R1(config-if)#no shut
On R2 and R3
Rx(config)#int S 0/0
Rx(config-if)#sh
Rx(config-if)#IP ospf network point-to-multipoint
Rx(config-if)#no IP ospf priority 0
Rx(config-if)#no shut
On All Routers
• Type SH IP ROUTE
L0 1.1.0.0 – R1 192.1.12.0/24 R2
S 0/0(.1) L0 2.1.0.0 –
L3 1.1.3.0/24 S 0/0 (.2) L3 2.1.3.0/24
Area 10
E 0/0 (.2)
192.1.23.0/24
Area 0
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24 L0 3.1.0.0 –
L0 4.1.0.0 – S 0/0 (.3)
L3 4.1.3.0/24 L3 3.1.3.0/24
R4 Area 100 R3
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
On R1
R1(config)#Router ospf 1
R1(config-router)#net 1.1.0 0.0.255.255 area 10
R1(config-router)#net 192.1.12 0.0.0.255 area 10
On R2
R2(config)#Router ospf 1
R2(config-router)#net 2.1.0.0 0.0.255.255 area 10
R2(config-router)#net 192.1.12.0.0 0.0.0.255 area 10
R2(config-router)#net 192.1.23.0.0 0.0.0.255 area 0
On R3
R3(config)#Router ospf 1
R3(config-router)#net 192.1.23.0 0.0.0.255 area 0
R3(config-router)#net 192.1.34.0 0.0.0.255 area 100
On R4
R4(config)#Router ospf 1
R4(config-router)#net 4.1.0.0 0.0.255.255 area 100
R4(config-router)#net 192.1.34.0 0.0.0.255 area 100
On All Routers
Objective: Perform Route summarization such that all the Loopbacks from
Area 10 and Area 100 are summarized
On R2
R2(config)#router ospf 1
R2(config-router)# area 10 range 1.1.0.0 255.255.252.0
R2(config-router)# area 10 range 2.1.0.0 255.255.252.0
On R3
R3(config)#router ospf 1
R3(config-router)# area 100 range 3.1.0.0 255.255.252.0
R3(config-router)# area 100 range 4.1.0.0 255.255.252.0
On All Routers
• Type SH IP ROUTE
• Does your routing table have all the entries to all the networks outside
your area?
L0 1.1.0.0 – R1 192.1.12.0/24 R2
S 0/0(.1) L0 2.1.0.0 –
L1 1.1.1.0/24 S 0/0 (.2) L1 2.1.1.0/24
192.1.23.0/24
Area 0
E 0/0 (.3)
R4 Area 100 R3
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
On R1
R1(config)#Router ospf 1
R1(config-router)#net 192.1.12 0.0.0.255 area 10
R1(config-router)#net 1.1.0.0 0.0.255.255 area 10
On R2
R2(config)#Router ospf 1
R2(config-router)#net 192.1.12.0.0 0.0.0.255 area 10
R2(config-router)#net 192.1.23.0.0 0.0.0.255 area 0
R2(config-router)#redistribute connected subnets
On R3
R3(config)#Router ospf 1
R3(config-router)#net 192.1.23.0 0.0.0.255 area 0
R3(config-router)#net 192.1.34.0 0.0.0.255 area 100
R3(config-router)# redistribute connected subnets
On R4
R4(config)#Router ospf 1
R4(config-router)#net 4.1.0.0 0.0.255.255 area 100
R4(config-router)#net 192.1.34.0 0.0.0.255 area 100
• Do you see the external Routes (2.1.0.0, 2.1.1.0, 3.1.0.0 and 3.1.1.0)?
On R1 and R2
Rx(config)#router ospf 1
Rx(config-router)#area 10 stub
On R3 and R4
Rx(config)#router ospf 1
Rx(config-router)#area 100 stub
On R1 and R4
• Do you see the external Routes (2.1.0.0, 2.1.1.0, 3.1.0.0 and 3.1.1.0)?
• What type of routes do you not see in the routing table of a stub area?
Objective: Configure Area 10 and 100 as Totally Stubby area’s by also blocking
the Inter-Area routes from propagating into it.
On R1 and R4
On R2
R2(config)#router ospf 1
R2(config-router)#area 10 stub no-summary
On R3
R3(config)#router ospf 1
R3(config-router)#area 10 stub no-summary
On R1 and R4
• What type of routes do you not see in the routing table of a Totally stub
area?
R1 192.1.12.0/24 R2
L0 1.1.1.1/24 S 0/0(.1) L0 2.2.2.2/24
S 0/0 (.2)
RIP
E 0/0 (.2)
192.1.23.0/24
Area 10
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
L0 4.4.4.4/24 S 0/0 (.3) L0 3.3.3.3/24
R4 Area 0 R3
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
On R1
R1(config)#Router rip
R1(config-router)#version 2
R1(config-router)#net 1.0.0.0
R1(config-router)#net 192.1.12.0
On R2
R2(config)#Router rip
R2(config-router)#no auto-summary
R2(config-router)#net 2.0.0.0
R2(config-router)#net 192.1.12.0
R2(config-router)#redistribute ospf 1 metric 1
R2(config-router)#Router ospf 1
R2(config-router)#net 192.1.23.2 0.0.0.0 area 1
R2(config-router)#redistribute rip subnets
R3(config)#Router ospf 1
R3(config-router)#net 192.1.23.3 0.0.0.0 area 1
R3(config-router)#net 3.3.3.3 0.0.0.0 area 0
R3(config-router)#net 192.1.34.3 0.0.0.0 area 0
On R4
R4(config)#Router ospf 1
R4(config-router)#net 192.1.34.4 0.0.0.0 area 0
R4(config-router)#redistribute connected subnets
On R3
• Type SH IP ROUTE
• Do you see External Routes from the ABR (R3) and from ASBR(R2)?
Configure Area 10 as a NSSA area. This will stop the ABR from
injecting the external routes from the backbone into Area 10.
Area 10 external routes should will be injected in a Type 7
routes in Area 10 and then converted back into Type when
send into the Backbone area.
On R3 and R2
Rx(config)#router ospf 1
Rx(config-router)#area 10 nssa
On R4
• Type SH IP ROUTE
On R3
On R2
• Do you still see the 4.0.0.0 network? What type of route is it?
• What does the ABR do with the N routes (LSA Type 7)?
On R3
• Do you see the RIP routes (1.0.0.0, 192.1.12.0) in the routing table?
On R4
R3(config)#Router ospf 1
R3(config-router)#area 10 nssa default-information-originate
On R4
• Type SH IP ROUTE
On R4
• Type SH IP ROUTE
• What if you want to cut your Routing table by blocking the Inter-area
routes from getting injected into Area 10.
On R3
R3(config)#Router ospf 1
R3(config-router)#area 10 nssa no-summary
On R4
• Type SH IP ROUTE
L0 1.1.0.0 – R1 192.1.12.0/24 R2
S 0/0(.1) L0 2.1.0.0 –
L1 1.1.1.0/24 S 0/0 (.2) L1 2.1.1.0/24
192.1.23.0/24
Area 10
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24 L0 3.1.0.0 –
L0 4.1.0.0 – S 0/0 (.3)
L1 4.1.1.0/24 L1 3.1.1.0/24
R4 Area 100 R3
R1 Configuration
R2 Configuration
R3 Configuration
On R1
R1(config)#Router ospf 1
R1(config-router)#net 1.1.1.1 0.0.0.0 area 0
R1(config-router)#net 192.1.12.1 0.0.0.0 area 0
On R2
R2(config)#Router ospf 1
R2(config-router)#router-id 2.2.2.2
R2(config-router)#net 192.1.12.2 0.0.0.0 area 0
R2(config-router)#net 2.2.2.2 0.0.0.0 area 10
R2(config-router)#net 192.1.23.2 0.0.0.255 area 10
On R3
R3(config)#Router ospf 1
R3(config-router)#router-id 3.3.3.3
R3(config-router)#net 192.1.23.3 0.0.0.0 area 10
R3(config-router)#net 3.3.3.3 0.0.0.0 area 10
R3(config-router)#net 192.1.34.3 0.0.0.0 area 100
On R4
R4(config)#Router ospf 1
R4(config-router)#net 192.1.34.4 0.0.0.0 area 100
R4(config-router)#net 4.4.4.4 0.0.0.0 area 100
On R4
• Type SH IP ROUTE.
On R2
R2(config)#router ospf 1
R2(config-router)#area 10 virtual-link 3.3.3.3
On R3
R3(config)#router ospf 1
R3(config-router)#area 10 virtual-link 2.2.2.2
On R4
Type SH IP ROUTE
Authored By:
Khawar Butt
CCIE # 12353 Module 6 – BGP
(R/S, Security, SP, Voice)
Border Gatew
FEATURES
Inter-domain routing
protocol also known
as EGP
Latest version is 4
Defined in RFC
1771
Autonomous system
is a set of routers
under a single
technical
administration, using
an IGP & common
metrics to route
packets within the
INTERNAL BGP
When BGP neighbors belong to the same AS
Neighbors do not have to be directly connected but need to be able to reach each other.
EXTERNAL BGP
BGP neighbors belong to different AS and should be able to reach each other.
Neighbors should be directly connected
Used to connect different Autonomous Systems to each other.
BGP METRICS
Known as Path Attributes
Four Categories of Path Attributes
Well-Known Mandatory
Well-Known Discretionary
Optional Tranistive
Optional Non-Transitive
OPTIONAL ATTRIBUTES
Recognized by some implementation’s
Recognized optional attributes are propagated based on their meaning
Optional Transitive Attributes: If not recognized, are marked as partial &
propagated to other neighbors
Optional Non-Transitive Attributes: Discard if not recognized
OPTIONAL TRANSITIVE
Aggregator: Indicates the AS # and IP address of the Router that performed the
Aggregation,
Community: Indicates the community that the route belongs to. Helps in route-selection
policy and filtering traffic. They allow to filter incoming and outgoing routes. They allow
routers to make decisions based on the Community a route belongs to.
Router BGP 100 (Where 100 is the Autonomous system on this router)
Neighbor 192.1.1.1 remote-as 200) (The IP address of your BGP Peer and its AS #. If the AS
number is the same as your AS #, it indicates that the BGP
Routers are IBGP Peer’s or Neighbors
Network 1.0.0.0 (What networks to advertise)
Route Reflectors
BGP Split Horizon: Routes learned via IBGP are never propagated to other IBGP Peers.
Required to avoid Routing Loops.
In order to let IBGP routers to propagate routes within an Autonomous System it requires a
Full Mesh Topology or Use Route Reflectors.
Full Mesh topology result in many BGP sessions being created. This may result in a
significant amount of increased traffic which is not feasible for slow WAN Links.
Route Reflectors modify BGP Spilt Horizon by allowing the router configured as the route
reflector to propagate routes learned by IBGP to other IBGP Peers.
Prefix List
Configuration
Authored By:
Netmetric Solutions
http://www.netmetric-solutions.com
R1 192.1.12.0/24 R2 L0 2.2.2.2/8
L0 1.1.1.1/8 S 0/0(.1)
S 0/0 (.2)
L1 11.1.0.1/16 L1 12.1.0.1/16
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
S 0/0(.4) 192.1.34.0/24
L0 4.4.4.4/8 S 0/0 (.3) L0 3.3.3.3/8
L1 14.1.0.1/16 L1 13.1.0.1/16
R4 R3
BGP Layout
AS 1 AS 2
R2
R1
R4
R3
AS 4 AS 3
R2 Configuration
R3 Configuration
R4 Configuration
On R1
R1(config)#Router bgp 1
R1(config-router)#no auto-summary
On R2
R2(config)#Router bgp 2
R2(config-router)#no auto-summary
R2(config-router)#no sync
R2(config-router)#bgp router-id 22.22.22.22
R2(config-router)#network 2.0.0.0
R2(config-router)#network 12.1.0.0 mask 255.255.0.0
R2(config-router)#neighbor 192.1.12.1 remote-as 1
On R2
R2(config)#Router bgp 2
R2(config-router)#neighbor 192.1.23.3 remote-as 3
On R3
R3(config)#Router bgp 3
R3(config-router)#no auto-summary
R3(config-router)#no sync
R3(config-router)#bgp router-id 33.33.33.33
R3(config-router)#network 13.1.0.0 mask 255.255.0.0
R3(config-router)#neighbor 192.1.23.2 remote-as 2
On R4
Objective: Configure BGP Authentication using MD5 between all the BGP
peers.
On R1
R1(config)#Router bgp 1
R1(config-router)#neighbor 192.1.12.2 password cisco-12
On R2
R2(config)#Router bgp 2
R2(config-router)#neighbor 192.1.12.1 password cisco-12
On R2
R2(config)#Router bgp 2
R2(config-router)#neighbor 192.1.23.3 password cisco-23
On R3
R3(config)#Router bgp 3
R3(config-router)#neighbor 192.1.23.2 password cisco-23
On R3
R3(config)#Router bgp 3
R3(config-router)#neighbor 4.4.4.4 password cisco-34
Objective: Disable BGP from the previous lab and Re-configure it based on the
new topology. Configure Route Reflector to overcome the BGP split-horizon
issue.
BGP Layout
R3
AS 234
AS 1
R3
R1 R2 R4
Disable BGP on all 4 routers. Also, delete the static routes for
network 4.0.0.0 on R3 and network 3.0.0.0 on R4.
On R1
On R2
On R3
On R1
R1(config)#router bgp 1
R1(config-router)#no auto-summary
R1(config-router)#no sync
R1(config-router)#bgp router-id 11.11.11.11
R1(config-router)#network 1.0.0.0
R1(config-router)#network 11.1.0.0 mask 255.255.0.0
R1(config-router)#neighbor 192.1.12.2 remote-as 234
On R2
On R2
R2(config)#Router RIP
R2(config-router)#no auto-summary
R2(config-router)#version 2
R2(config-router)#network 192.1.23.0
R3(config)#Router RIP
R3(config-router)#no auto-summary
R3(config-router)#version 2
R3(config-router)#network 192.1.23.0
R3(config-router)#network 192.1.34.0
On R4
R4(config)#Router RIP
R4(config-router)#no auto-summary
R4(config-router)#version 2
R4(config-router)#network 192.1.34.0
On R2
On R3
Loopback 1 – 192.2.1.1/24
Loopback 2 – 192.2.2.1/24
Loopback 3 – 192.2.3.1/24
Loopback 4 – 192.2.4.1/24
Loopback 5 – 192.2.5.1/24
Loopback 6 – 192.2.6.1/24
Loopback 7 – 192.2.7.1/24
Loopback 8 – 192.2.8.1/24
On R2
R2(config)#interface Loopback 1
R2(config-if)# ip address 192.2.1.1 255.255.255.0
R2(config-if)#interface Loopback 2
R2(config-if)# ip address 192.2.2.1 255.255.255.0
R2(config-if)#interface Loopback 3
R2(config-if)# ip address 192.2.3.1 255.255.255.0
R2(config-if)#interface Loopback 4
R2(config-if)# ip address 192.2.4.1 255.255.255.0
R2(config-if)#interface Loopback 5
R2(config-if)# ip address 192.2.5.1 255.255.255.0
R2(config-if)#interface Loopback 6
R2(config-if)# ip address 192.2.6.1 255.255.255.0
R2(config-if)#interface Loopback 7
R2(config-if)# ip address 192.2.7.1 255.255.255.0
R2(config-if)#interface Loopback 8
R2(config-if)# ip address 192.2.8.1 255.255.255.0
On R2
On R2
On R4
(Builds on R4)
Loopback 1 – 150.3.16.1/20
Loopback 2 – 150.3.36.1/22
Loopback 3 – 150.3.40.1/22
Loopback 4 – 150.3.50.1/23
Loopback 5 – 150.3.65.1/24
Loopback 6 – 150.13.0.1/16
Loopback 7 – 150.14.64.1/18
On R3
R3(config)#interface Loopback 1
R3(config-if)# ip address 150.3.16.1 255.255.240.0
R3(config-if)#interface Loopback 2
R3(config-if)# ip address 150.3.36.1 255.255.252.0
R3(config-if)#interface Loopback 3
R3(config-if)# ip address 150.3.40.1 255.255.252.0
R3(config-if)#interface Loopback 4
R3(config-if)# ip address 150.3.50.1 255.255.254.0
R3(config-if)#interface Loopback 5
R3(config-if)# ip address 150.3.65.1 255.255.255.0
R3(config-if)#interface Loopback 6
R3(config-if)# ip address 150.13.0.1 255.255.0.0
R3(config-if)#interface Loopback 7
R3(config-if)# ip address 150.14.64.1 255.255.192.0
On R3
On R2
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
E 0/0 (.2)
E 0/0 (.1)
192.1.23.0/24
192.1.14.0/24
E 0/0 (.3)
E 0/0 (.4)
L0 4.4.4.4/8 L0 3.3.3.3/8
S 0/0(.4)
S 0/0 (.3)
192.1.34.0/24
R4 R3
BGP Layout
R2
AS 1
AS 234
R3
R1
R4
R2 Configuration
R3 Configuration
R4 Configuration
Objective: Configure BGP in 2 AS’s (1 and 234). Use MED to control incoming
traffic into AS 234.
On R2
R2(config)#Router RIP
R2(config-router)#Version 2
R2(config-router)#No auto-summary
R2(config-router)#Network 192.1.23.0
R3(config)#Router RIP
R3(config-router)#Version 2
R3(config-router)#No auto-summary
R3(config-router)#Network 192.1.23.0
R3(config-router)#Network 192.1.34.0
On R4
R4(config)#Router RIP
R4(config-router)#Version 2
R4(config-router)#No auto-summary
R4(config-router)#Network 192.1.34.0
On R1
R1(config)#Router BGP 1
R1(config-router)#No auto-summary
R1(config-router)#No sync
R1(config-router)#Network 1.0.0.0
R1(config-router)#Neighbor 192.1.12.2 remote-as 234
R1(config-router)#Neighbor 192.1.14.4 remote-as 234
On R2
On R3
On R2
On R2
Objective: Controlling outgoing traffic on the local router without affecting the
rest of the AS.
Configure R4 such that all traffic destined for network 1.0.0.0 should go
directly to R1 instead of going thru R2 as it has a higher Local Preference for
the AS.
On R4
Authored By:
Khawar Butt
CCIE # 12353 Module 7 -Additional Topics
(R/S, Security, SP, Voice)
Additio
• Allows a
Cisco Router
to Assign IP
Configuration
information
Command Syntax:
Router(config)#IP dhcp
pool pool name
Router(dhcp-
config)#network
Netmetric Solutions
Copyrights Netmetric Solutions 2006-2010
Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com
http://www.netmetric-solutions.com
Page 164 of 207
network address /Prefix mask
Router(dhcp-config)#default-router Router’s Address
Router(dhcp-config)#netbios-name-server Name Server Address
Router(dhcp-config)#netbios-node-type Node-type
Router(dhcp-config)#dns-server Dns Server Address
Router(dhcp-config)#lease Days hours minutes
Helper Addresses
• If a client needs to reach a server and does not know the server’s
address the client uses a broadcast to find the server’s address. By
default, a router will drop the broadcast packet. Helper addresses
allow connectivity by forwarding these broadcasts as unicast packets
Server Locations
Command Syntax:
IP helper-address Address
Route Maps
• Route maps can be used for both Redistribution and for Policy Routing.
• You have Addresses and Inverse Masks in Access Lists whereas you have
Match Statements in a Route Map.
• Like an Access List, there is an “Implicit deny any” at the end of a route
map.
• Unlike Access Lists Route Maps can be edited without reentering the
whole Access Lists.
Command Syntax:
Policy Routing
Authored By:
Khawar Butt
CCIE # 12353
(R/S, Security, SP, Voice) Module 7 -Additional Topics
Labs
Netmetric Solutions
Copyrights Netmetric Solutions 2006-2010
http://www.netmetric-solutions.com
Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com
Page 168 of 207
Lab 1 – IP Helper Addresses
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2)
E 0/0(.1) E 0/0(.1)
192.1.11.0/24 192.1.22.0/24
Objective:
R1 Basic Configuration
R1(config)#int S 0/0
R1(config-if)#ip addr 192.1.12.1 255.255.255.0
R1(config-if)#clock rate 128000
R1(config-if)#no shut
R1(config-if)#exit
R1(config)#int E 0/0
R1(config-if)#ip addr 192.1.11.1 255.255.255.0
R1(config-if)#no shut
R1(config-if)#exit
R1(config-if)#Router RIP
R1(config-router)#version 2
R2 Basic Configuration
R2(config)#int S 0/0
R2(config-if)#ip addr 192.1.12.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#int E 0/0
R2(config-if)#ip addr 192.1.22.1 255.255.255.0
R2(config-if)#no shut
R2(config-if)#Router RIP
R2(config-router)#version 2
R2(config-router)#no auto-summary
R2(config-router)#network 192.1.12.0
R2(config-router)#network 192.1.22.0
R1 DHCP Configuration
Objective:
Also, configure R1 as a DHCP Server for the 192.1.22.0/24 network. The pool
should start giving addresses from 192.1.22.11 – 192.1.22.254. It should
assign 192.1.22.1 as the default gateway and 192.1.22.5 as the DNS Server.
Use a lease time of 3 and a half days. Make sure R2 forwards the DHCP
requests to R1 DHCP.
R1 DHCP Configuration
PC Configuration
• Check the Addresses against the addresses assigned by the IOS DHCP
Server.
• Make sure the addresses are not from the excluded range
R1 R2
S 0/0(.1) 192.1.12.0/24
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
S 0/1(.1)
192.1.112.0/24 S 0/1 (.2) E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
L0 3.3.3.3/8
R3
R1 Configuration
R2 Configuration
R3 Configuration
On R1
R1#conf t
R1(config)#Router eigrp 1
R1(config-router)#net 1.0.0.0
R1(config-router)#net 192.1.12.0
R1(config-router)#net 192.1.112.0
On R2
R2#conf t
R2(config)#Router eigrp 1
R2(config-router)#net 2.0.0.0
R2(config-router)#net 192.1.12.0
R2(config-router)#net 192.1.112.0
R2(config-router)#net 192.1.23.0
On R3
R3#conf t
R3(config)#Router eigrp 1
R3(config-router)#net 3.0.0.0
R3(config-router)#net 192.1.23.0
On R2
On R2
Type Debug ip packet (Look for the interface used to send the packet to
1.1.1.1 when R3 sends the ping).
On R3
• Notice all traffic from R3 with a source address of 3.3.3.3 goes through S
0/0.
R1 R2
L0 10.0.0.1/8 S 0/0(.1) 192.1.12.0/24
S 0/0 (.2) L0 2.2.2.2/8
E 0/0 (.2)
192.1.23.0/24
E 0/0 (.3)
L0 192.168.1.0/24
R3
R1 Configuration
R2 Configuration
R3 Configuration
On R1
On R3
On R1
R1(config)#interface Tunnel13
R1(config-if)#ip address 172.16.0.1 255.255.0.0
R1(config-if)#tunnel source 192.1.12.1
R1(config-if)#tunnel destination 192.1.23.3
R1(config-if)#tunnel key 1234
On R3
R3(config)#interface Tunnel13
R3(config-if)#ip address 172.16.0.3 255.255.0.0
R3(config-if)#tunnel source 192.1.23.3
R3(config-if)#tunnel destination 192.1.12.1
R3(config-if)#tunnel key 1234
On R1
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#network 10.0.0.0
R1(config-router)#network 172.16.0.0
R1(config-router)#no auto-summary
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#network 192.168.1.0
R3(config-router)#network 172.16.0.0
R3(config-router)#no auto-summary
On R1 and R3
• Type Show IP route. Do you see the private networks from each other.
Objective: Configure NAT and PAT on R1 and R3 to route traffic from the
private networks to the Internet (R2 – 2.2.2.2).
On R2
On R1
On R1
On R1
On R2
On R3
On R3
R1 R2
Lo 0 E 0/0 E 0/0 Lo 0
2000:192:1:12::/64 S 0/0.1
Frame 2000:192:1:23::/64
S 0/0.1
2000:192:1:34::/64
Lo 0 E 0/0 E 0/0 Lo 0
R4 R3
Objective: Configure IPv6 on the Routers. Run RIPng to route between the
networks.
• R1 – 2001:1:1:12::1 /64
• R2 – 2001:1:1:12::2 /64
• R3 – 2001:1:1:34::3 /64
• R4 – 2001:1:1:34::4 /64
On R1
R1(config)#ipv6 unicast-routing
R1(config)#Interface E 0/0
R1(config-if)#ipv6 address 2001:1:1:12::1/64
R1(config-if)#no shut
On R2
R2(config)#ipv6 unicast-routing
R2(config)#Interface E 0/0
On R3
R3(config)#ipv6 unicast-routing
R3(config)#Interface E 0/0
R3(config-if)#ipv6 address 2001:1:1:34::3/64
R3(config-if)#no shut
On R4
R4(config)#ipv6 unicast-routing
R4(config)#Interface E 0/0
R4(config-if)#ipv6 address 2001:1:1:34::4/64
R4(config-if)#no shut
• R1 – Loopback0 – 2001:1:1:1::/64
• R2 – Loopback0 – 2001:2:2:2::/64
• R3 – Loopback0 – 2001:3:3:3::/64
• R4 – Loopback0 – 2001:4:4:4::/64
On R1
R1(config)#Interface Loopback 0
R1(config-if)#ipv6 address 2001:1:1:1::/64 eui-64
On R2
R2(config)#Interface Loopback 0
R2(config-if)#ipv6 address 2001:2:2:2::/64 eui-64
On R3
R3(config)#Interface Loopback 0
R3(config-if)#ipv6 address 2001:3:3:3::/64 eui-64
On R4
R4(config)#Interface Loopback 0
• R2 – 2001:1:1:23::2/64
• R3 – 2001:1:1:23::3/64
Ensure that the routers can ping each other’s serial interface.
Also allow R2 and R3 to ping their own IP addresses. Use a sun-
interface on R2 and R3 for the Frame relay configuration.
On R2
R2(config)#Interface S 0/0
R2(config-if)#encap frame-relay
R2(config-if)#no shut
R2(config-if)#interface S 0/0.1 point-to-point
R2(config-subif)#ipv6 address 2001:1:1:23::2/64
R2(config-subif)#frame-relay interface-dlci 203
On R3
R3(config)#Interface S 0/0
R3(config-if)#encap frame-relay
R3(config-if)#no shut
R3(config-if)#interface S 0/0.1 point-to-point
R3(config-subif)#ipv6 address 2001:1:1:23::3/64
R3(config-subif)#frame-relay interface-dlci 302
R1 – E 0/0, Loopback 0
R2 – E 0/0, Loopback 0, S 0/0.1
R3 – E 0/0, Loopback 0, S 0/0.1
R4 – E 0/0, Loopback 0
On R1
R1(config)#Interface Loopback0
R1(config-if)#ipv6 rip 1234 enable
On R2
R2(config)#Interface Loopback0
R2(config-if)#ipv6 rip 1234 enable
R2(config-if)#Interface E 0/0
R2(config-if)#ipv6 rip 1234 enable
R2(config-if)#Interface S 0/0.1
R2(config-if)#ipv6 rip 1234 enable
On R3
R3(config)#Interface Loopback0
R3(config-if)#ipv6 rip 1234 enable
R3(config-if)#Interface E 0/0
R3(config-if)#ipv6 rip 1234 enable
R3(config-if)#Interface S 0/0.1
R3(config-if)#ipv6 rip 1234 enable
On R4
R4(config)#Interface Loopback0
R4(config-if)#ipv6 rip 1234 enable
R4(config-if)#Interface E 0/0
R4(config-if)#ipv6 rip 1234 enable
On All Routers
• Type Show IPv6 Route rip. Do you see all the IPv6 routes learned thru
RIPng?
On R1
R1(config)#Interface Loopback 0
R1(config-if)#No ipv6 rip 1234 enable
R1(config-if)#Interface E 0/0
R1(config-if)#No ipv6 rip 1234 enable
On R2
R2(config)#Interface Loopback 0
R2(config-if)#No ipv6 rip 1234 enable
R2(config-if)#Interface E 0/0
R2(config-if)#No ipv6 rip 1234 enable
R2(config-if)#Interface S 0/0.1
R2(config-if)#No ipv6 rip 1234 enable
On R3
R3(config)#Interface Loopback 0
R3(config-if)#No ipv6 rip 1234 enable
R3(config-if)#Interface E 0/0
R3(config-if)#No ipv6 rip 1234 enable
R3(config-if)#Interface S 0/0.1
R3(config-if)#No ipv6 rip 1234 enable
On R4
R4(config)#Interface Loopback 0
R4(config-if)#No ipv6 rip 1234 enable
R4(config-if)#Interface E 0/0
R4(config-if)#No ipv6 rip 1234 enable
On R2
On R3
On R4
On R1
R1(config)#interface Loopback 0
R1(config-if)# ip ospf network point-to-point
On R2
R2(config)#interface Loopback 0
R2(config-if)# ip ospf network point-to-point
On R3
R3(config)#interface Loopback 0
R3(config-if)# ip ospf network point-to-point
On R4
R4(config)#interface Loopback 0
R4(config-if)# ip ospf network point-to-point
On All Routers
• Type Show IPv6 Route ospf. Do you see all the IPv6 routes learned thru
OSPFv3?
R1 R2
Lo 0 E 0/0 E 0/0 Lo 0
2000:1:1:12::/64 S 0/0
Frame 192.1.23.0/24
S 0/0
2000:1:1:34::/64
Lo 0 E 0/0 E 0/0 Lo 0
R4 R3
Objective: IPv6 is running between R1-R2 and between R3-R4. IPv4 is running
between R2-R3. You need to connect the 2 IPv6 networks over a IPv4 network
using a Tunnel.
• R1 – 2001:1:1:12::1 /64
• R2 – 2001:1:1:12::2 /64
• R3 – 2001:1:1:34::3 /64
• R4 – 2001:1:1:34::4 /64
On R1
R1(config)#ipv6 unicast-routing
R1(config)#Interface E 0/0
R1(config-if)#ipv6 address 2001:1:1:12::1/64
R1(config-if)#no shut
On R2
On R3
R3(config)#ipv6 unicast-routing
R3(config)#Interface E 0/0
R3(config-if)#ipv6 address 2001:1:1:34::3/64
R3(config-if)#no shut
On R4
R4(config)#ipv6 unicast-routing
R4(config)#Interface E 0/0
R4(config-if)#ipv6 address 2001:1:1:34::4/64
R4(config-if)#no shut
• R1 – Loopback0 – 2001:1:1:1::1/64
• R2 – Loopback0 – 2001:2:2:2::2/64
• R3 – Loopback0 – 2001:3:3:3::3/64
• R4 – Loopback0 – 2001:4:4:4::4/64
On R1
R1(config)#Interface Loopback 0
R1(config-if)#ipv6 address 2001:1:1:1::1/64
On R2
R2(config)#Interface Loopback 0
R2(config-if)#ipv6 address 2001:2:2:2::2/64
On R3
R3(config)#Interface Loopback 0
R3(config-if)#ipv6 address 2001:3:3:3::3/64
On R4
R1 – E 0/0, Loopback 0
R2 – E 0/0, Loopback 0
R3 – E 0/0, Loopback 0
R4 – E 0/0, Loopback 0
On R1
R1(config)#Interface Loopback0
R1(config-if)#ipv6 rip 1234 enable
R1(config-if)#Interface E 0/0
R1(config-if)#ipv6 rip 1234 enable
On R2
R2(config)#Interface Loopback0
R2(config-if)#ipv6 rip 1234 enable
R2(config-if)#Interface E 0/0
R2(config-if)#ipv6 rip 1234 enable
On R3
R3(config)#Interface Loopback0
R3(config-if)#ipv6 rip 1234 enable
R3(config-if)#Interface E 0/0
R3(config-if)#ipv6 rip 1234 enable
On R4
R4(config)#Interface Loopback0
R4(config-if)#ipv6 rip 1234 enable
R4(config-if)#Interface E 0/0
R4(config-if)#ipv6 rip 1234 enable
On R3
R3(config)#Interface S 0/0
R3(config-if)#ip address 192.1.23.3 255.255.255.0
R3(config-if)#encap frame-relay
R3(config-if)#frame-relay map ip 192.1.23.2 302
R3(config-if)#no shut
On R2
R2(config)#Interface Tunnel 23
R2(config-if)#ipv6 address 2001:23:23:23::2/64
R2(config-if)#tunnel source S 0/0
R2(config-if)# tunnel destination 192.1.23.3
R2(config-if)#ipv6 rip 1234 enable
R2(config-if)#tunnel mode IPv6IP
On R3
R3(config)#Interface Tunnel 23
R3(config-if)#ipv6 address 2001:23:23:23::3/64
R3(config-if)#tunnel source S 0/0
R3(config-if)# tunnel destination 192.1.23.2
R3(config-if)#ipv6 rip 1234 enable
R3(config-if)#tunnel mode IPv6IP
On All Routers
• Type Show IPv6 Route rip. Do you see all the IPv6 routes learned thru
RIPng?
R1
R2
R4
Frame-Relay
R3
On R1
R1(config)#IPv6 unicast-routing
R1(config)#Interface S0/0
R1(config-if)#Encapsulation frame-relay
R1(config-if)#No frame-relay inverse
R1(config-if)#No shut
R1(config-if)#Int S0/0.14 point-to-point
R1(config-subif)#Ipv6 address 2001:192:1:14::1/64
R1(config-subif)#Frame-relay interface-dlci 104
On R4
R4(config)#IPv6 unicast-routing
R4(config)#Interface S0/0
R4(config-if)#Encapsulation frame-relay
R4(config-if)#No frame-relay inverse
R4(config-if)#Ipv6 address 2001:192:1:14::4/64
R4(config-if)#Frame-relay map ipv6 2001:192:1:14::1 401 broadcast
R4(config-if)#No shut
On R1
R1(config)#Int S0/0.123 multipoint
R1(config-subif)#Ipv6 address 2001:192:1:123::1/64
R1(config-subif)#Frame-relay map ipv6 2001:192:1:123::2 102 broad
R1(config-subif)#Frame-relay map ipv6 2001:192:1:123::3 103 broad
On R2
R2(config)#IPv6 unicast-routing
R2(config)#Interface S0/0
R2(config-if)#Encapsulation frame-relay
R2(config-if)#No frame-relay inverse
R2(config-if)#Ipv6 address 2001:192:1:123::2/64
R2(config-if)#Frame-relay map ipv6 2001:192:1:123::1 201 broadcast
R2(config-if)#Frame-relay map ipv6 2001:192:1:123::3 201
R2(config-if)#No shut
On R3
R3(config)#IPv6 unicast-routing
R3(config)#Interface S0/0
R3(config-if)#Encapsulation frame-relay
R3(config-if)#No frame-relay inverse
R3(config-if)#Ipv6 address 2001:192:1:123::3/64
R3(config-if)#Frame-relay map ipv6 2001:192:1:123::1 301 broadcast
R3(config-if)#Frame-relay map ipv6 2001:192:1:123::2 301
R3(config-if)#No shut
On R1
(Find the Link-Local Address for R2 and R3 by using Show IPv6 int brief
on R2 and R3 respectively. This is required for OSPFv3 Neighbor
relationship to be established)
On R2
(Find the Link-Local Address for R1 by using Show IPv6 int brief on R1.
This is required for OSPFv3 Neighbor relationship to be established)
On R3
On R4
On R1
R1(config)#interface Loopback 0
R1(config-if)# ip ospf network point-to-point
On R2
R2(config)#interface Loopback 0
R2(config-if)# ip ospf network point-to-point
On R3
R3(config)#interface Loopback 0
R3(config-if)# ip ospf network point-to-point
On R4
R4(config)#interface Loopback 0
R4(config-if)# ip ospf network point-to-point
• Type Show IPv6 Route ospf. Do you see all the IPv6 routes learned thru
OSPFv3?
Authored By:
Khawar Butt
CCIE # 12353 Module 8 - IS-IS
(R/S, Security, SP, Voice)
Netmetric Solutions
Copyrights Netmetric Solutions 2006-2010
http://www.netmetric-solutions.com
Website: http://www.netmetric-solutions.com; Email: khawarb@khawarb.com
Page 198 of 207
IS-IS Overview
IS – IS COMMANDS
• IS – IS : Intermediate system – to – intermediate system protocol is a
part of open systems interconnect (OSI) suite of protocols.
• The OSI suite uses CLNS (connection less network service) to provide
connectionless delivery of data and the actual layer 3 protocol is CLNP
(connectionless network protocol).
• IS – IS uses CLNS addresses to identify the routers and to build the
link-state database.
• IS – IS supports Ethernet & frame-relay.
• IS – IS supports important characteristics of OSPF and EIGRP as it
supports VLSM and converges quickly.
• Integrated IS – IS (dual IS – IS) offers support for IP and OSI protocols.
• IS – IS is found in large ISP’s and in some networks that support OSI
protocols because of scalability, convergence, and stability.
• Router is referred to as intermediate-system, thus allowing routers to
communicate with other routers.
• IS – IS serves as IGP for the CLNS.
• IS – IS is a link state routing protocol.
• Uses Dijkstra’s SPF algorithm, has faster convergence.
• Uses hellos to establish adjacencies and LSP’s to exchange link-state
information.
• Efficient use of bandwidth, memory, and processor.
• IS – IS supports two routing protocols:
o Level – 1 builds topology of system ID’s in local area and routes
within local area using lowest cost path.
o Level – 2 exchanges prefix information between areas. Routes
traffic to area using lowest cost path.
• Level – 1 routes learn about paths within the area.
• Level – 2 routes learn about paths between areas.
• Level 1 – 2 routes learn about paths both within and between areas.
• The path of connected level – 2 and level 1 – 2 routes is called the
backbone.
• Default narrow metrics are limited to 6-bit interface and 10-bit path
metric.
• IS – IS interfaces have default metric as 10.
• ES – IS protocol permits ES’s & IS’s to discover one another.
Area Design:
• In IS – IS the area borders lie on links.
• Each IS – IS router belongs to exactly one area.
• IS – IS is more flexible when extending the backbone.
o Area address
o AFI set to 49
o Area ID
o System ID
o NSEL – always set to 0 for a router.
o Eg: 49.0001.0000.0012.3456.00
Link is the path between 2 neighbor IS’s and is defined as being up when
communication is possible between the two neighbors SNPA’s.
IS – IS Routing levels:
Area address is used to route between areas system ID is used to route within
an area.
Authored By:
Netmetric Solutions
http://www.netmetric-solutions.com
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
R1 Configuration
R2 Configuration
On R1
R1(config)#Router isis
R1(config-router)#net 49.0001.0000.0000.0001.00
R1(config-router)#is-type level-1
R1(config-router)#interface S0/0
R1(config-if)#ip router isis
R1(config-if)#isis circuit-type level-1
R1(config-router)#interface Loopback 0
R1(config-if)#ip router isis
R1(config-if)#isis circuit-type level-1
On R2
R1(config)#Router isis
R1(config-router)#net 49.0001.0000.0000.0002.00
• On R1, Type Show ip route. The output displays that network 2.0.0.0 is
the route from level 1 as indicated by the “iL1” tag
R1
Routing Table
Routing Table
• On R1, Type Show isis topology. This command displays the level 1
topology table, which shows the least cost IS – IS paths to the IS’s.
R1 192.1.12.0/24 R2
S 0/0(.1)
S 0/0 (.2) L0 2.2.2.2/8
L0 1.1.1.1/8
R1 Configuration
R2 Configuration
On R1
R1(config)#Router isis
R1(config-router)#net 49.0001.0000.0000.0001.00
R1(config-router)#is-type level-1
R1(config-router)#interface S0/0
R1(config-if)#ip router isis
R1(config-if)#isis circuit-type level-1-2
R1(config-router)#interface Loopback 0
R1(config-if)#ip router isis
R1(config-if)#isis circuit-type level-1
R1(config)#Router isis
R1(config-router)#net 49.0002.0000.0000.0002.00
R1(config-router)#is-type level-1
R1(config-router)#interface S0/0
R1(config-if)#ip router isis
R1(config-if)#isis circuit-type level-1-2
R1(config-router)#interface Loopback 0
R1(config-if)#ip router isis
R1(config-if)#isis circuit-type level-1
• On R1, Type Show ip route. The output displays that network 2.0.0.0 is
the route from level 1 as indicated by the “iL2” tag
R1
Routing Table
Routing Table
On R1
• On R2, Type Show ip route. The output displays that network the new
loopbacks networks are level 2 routes as indicated by the “iL2” tag
R2
Routing Table
On R1
R1(config)#router isis
R1(config-if)#summary-address 150.1.4.0 255.255.252.0 level-2
• On R2, Type Show ip route. The output displays that network the
summarized address for the new loopbacks.
R2
Routing Table