From Page no.

216 to onward are under correction

process. If you find any mistake or you have any
suggestion, plz contact me at

[email protected]
[email protected]
 CCNP (BSCI 642-901)

ROUTING
LAB MANUAL

Ver 1.11

Prepared and verified by:

MUHAMMAD SHAKEEL ASHRAF

0092-300-4772177
[email protected]

Under kind supervision of:

SIR HAROON AHMAD MALIK

CORVIT SYSTEMS/SOLUTIONS
GULBERG, LAHORE, PAKISTAN
 TABLE OF CONTENTS
COURSE OUTLINE............................................................1
RIP (LAB #1)..............................................................2
RIP (LAB #2) - ROUTES WITH DIFFERENT PATHS................................4
REDISTRIBUTION (LAB #1)...................................................6
REDISTRIBUTION (LAB #2)...................................................8
RUNNING TWO PROTOCOLS AT THE SAME ROUTER.................................12
HOW TO SET DELAY & BANDWIDTH VALUE?......................................14
SETTING DELAY AND BANDWIDTH VALUE......................................14
CHECKING DELAY AND BANDWIDTH VALUE.....................................15
CALCULATING METRIC VALUE OF EIGRP........................................16
HOW TO VERIFYING EIGRP METRIC VALUE?.....................................18
MANIPULATING METRIC IN CASE OF IGRP......................................19
CALCULATING METRIC VALUE OF IGRP.........................................19
VLSM (Variable Length Subnet Mask).......................................20
IPv6.....................................................................23
INTRODUCTION...........................................................23
IPv6 HEADER FORMAT.....................................................23
IPv6 SAMPLE IP ADDRESS.................................................23
UNICAST IPv6 ADDRESSES.................................................24
OSPF (Open Shortest Path First)..........................................29
BACKGROUND.............................................................29
ROUTING HIERARCHY......................................................29
SPF ALGORITHM..........................................................30
PACKET FORMAT..........................................................31
ADDITIONAL OSPF FEATURES...............................................32
ADVANTAGES OF OSPF.....................................................32
DISADVANTAGES OF OSPF..................................................32
WILD CARD MASK OF ACL & OSPF.............................................33
UNDERSTANDING WILD CARD MASK - LAB.......................................37
ROUTER-ID................................................................43
CONFIGURING ROUTER-ID..................................................44
DR, BDR & DR-OTHER.......................................................44
PRIORITY NUMBER..........................................................44
HOW ELECTION TAKE PLACE?.................................................44
AUTONOMOUS SYSTEM........................................................45
ROUTER TYPES.............................................................50
INTERNAL ROUTER (IR)...................................................50
BACKBONE INTERNAL ROUTER (BR)..........................................50
AREA BORDER ROUTER (ABR)...............................................50
AUTONOMOUS SYSTEM BORDER ROUTER (ASBR).................................50
LINK STATE ADVERTISEMENT.................................................52
Type 1 - Router LSA....................................................52
Type 2 - Network LSA...................................................52
Type 3 - Summary LSA...................................................52
Type 4 - ASBR-Summary LSA..............................................52
Type 5 - External LSA..................................................52
Type 6 - Group Membership LSA..........................................52
Type 7.................................................................52
Type 8 - a link-local only LSA.........................................52
Type 9 - a link-local "opaque" LSA.....................................52
Type 10 - an area-local "opaque" LSA...................................52
Type 11 - an "opaque" LSA..............................................53
FRAME RELAY (HUB-N-SPOKE TOPOLOGY).......................................55
(USING DYNAMIC MAPPING / INVERSE ARP)..................................55
(USING STATIC MAPPING – RECOMMENDED)...................................58
POINT-TO-MULTIPOINT SUB-INTERFACE WITH STATIC MAPPING..................60
POINT-TO-POINT SUB-INTERFACE WITH STATIC MAPPING.......................63
BEHAVIOR OF OSFF WITH FRAME RELAY......................................67
OSPF STATES..............................................................69
DOWN STATE.............................................................69
INIT OR ONE WAY STATE..................................................69
TWO WAY STATE..........................................................69
EXSTART (MASTER/SLAVE).................................................70
EXCHANGE (LSA REQUEST).................................................71
LOADING................................................................71
FULL...................................................................71
ROUTES...................................................................72
STATIC ROUTES..........................................................72
DYNAMIC ROUTES.........................................................72
ROUTES - LAB...........................................................73
VIRTUAL LINKS............................................................77
AUTHENTICATION IN OSPF...................................................83
ROUTE SUMMARIZATION......................................................85
STUB AREA................................................................86
TOTALLY STUB AREA........................................................90
NOT-SO-STUBBY AREA (NSSA)................................................91
CHANGING METRIC VALUE OF STATIC ROUTES...................................97
CHANGING METRIC TYPE OF STATIC ROUTES....................................98
CHANGING METRIC VALUE & TYPE (USING SINGLE LINE COMMAND)................98
ROUTE MAPS..............................................................103
LAB #1................................................................103
LAB #2 STATIC ROUTES+OSPF DIFFERENT AREAS+ROUTE MAPS.................110
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS.................................117
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS.................................132
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS.................................145
EIGRP (ENHANCED INTERIOR GATEWAY PROTOCOL)..............................161
MANUAL SUMMARIZATION OF STATIC ROUTES IN EIGRP........................163
ENABLING AUTO-SUMMARIZATION...........................................165
PERFORMING AUTHENTICATION IN EIGRP....................................166
EIGRP - LOAD BALANCING..................................................168
UN-EQUAL LOAD BALANCING BY CHANGING BANDWIDTH.........................173
VARIANCE..............................................................174
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS.................................175
OSPF FILTERATION........................................................189
IS-IS (INTERMEDIATE SYSTEM-TO-INTERMEDIATE SYSTEM)......................193
CLNS..................................................................193
INTEGRATED OR DUAL IS-IS..............................................194
IS-IS OPERATIONS......................................................194
IS-IS DATA-FLOW DIAGRAM...............................................194
AREAS AND THE ROUTING DOMAIN..........................................195
BACKBONE..............................................................196
AREAS.................................................................196
LEVEL-1 ROUTER........................................................197
LEVEL-2 ROUTER........................................................198
LEVEL-1 / LEVEL-2 ROUTER..............................................198
NSAP ADDRESSES........................................................199
METRICS...............................................................200
DEFAULT METRIC........................................................200
EXTENDED METRIC.......................................................201
IS-IS (LAB #1)..........................................................202
IS-IS (LAB #2)..........................................................208
 1

COURSE OUTLINE

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 2

LECTURE NO. 2
26 Nov 2008
RIP (LAB #1)

Figure-2a
(Note: Lab results are produced using Packet Tracer 5.0 Simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface serial 1/1

A(config-if)# ip address 3.0.0.2 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.2 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 3

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.50.1 255.255.255.0
C(config-if)# no shutdown

RUNNING RIP ON ROUTER-A, B & C

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 3.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router rip

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0
B(config-router)# network 200.100.100.0

C(config)# router rip

C(config-router)# network 2.0.0.0
C(config-router)# network 3.0.0.0
C(config-router)# network 200.100.50.0

ROUTING TABLE OF ROUTER-A

A# show ip route

NOTE: Routing table of Router-A has been completely converged and

network 2.0.0.0 has been reached on Router-A using three
different paths.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 4

RIP (LAB #2) - ROUTES WITH DIFFERENT PATHS

Figure-2b
(Note: Lab results are produced using Packet Tracer 5.0 Simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface serial 1/1

A(config-if)# ip address 3.0.0.2 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 5

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

RUNNING RIP ON ROUTER-A, B & C

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 3.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router rip

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0
B(config-router)# network 200.100.100.0

C(config)# router rip

C(config-router)# network 2.0.0.0
C(config-router)# network 3.0.0.0
C(config-router)# network 200.100.150.0

ROUTING TABLE OF ROUTER-A

A# show ip route

NOTE: Routing table of Router-A has been completely converged and

network 2.0.0.0 has been reached on Router-A using two
different paths.

SHUTTING DOWN INTERFACE SERIAL 1/0 OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# shutdown

A# show ip route

NOTE: Network 2.0.0.0 has been reached on Router-A using only one
path.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 6

REDISTRIBUTION (LAB #1)

When different protocols are running on a router, the convergence could not be done
because the different protocols cannot talk to each other. Therefore to perform the
convergence, we use redistribution method.

Figure-2c
(Note: Lab results are produced using Boson Simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 0/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 1/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 0/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface fastethernet 1/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A & B

A# show ip route

B# show ip route

A# show ip protocol (Run these command to make sure that there

B# show ip protocol is no routing protocol running at these
routers)

RUNNING RIP ON ROUTER-A, & B

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router rip

B(config-router)# network 1.0.0.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 7

RUNNING IGRP ON ROUTER-B

B(config)# router igrp 222
B(config-router)# network 200.100.100.0

ROUTING TABLE OF ROUTER-A

(AFTER RUNNING RIP)

A# show ip route

ROUTING TABLE OF ROUTER-B

(AFTER RUNNING IGRP & RIP)

B# show ip route

NOTE: Routing Table of Router-B has been completed (in other words
convergence on Router-B has been done) but Routing Table of
Router-A is still incomplete. To do the needful, we'll perform
redistribution.

PERFORMING REDISTRIBUTION ON ROUTER-B

B(config)# router rip
B(config-router)# redistribute igrp 1
B(config-router)# default-metric 5 * Default-metric should be =<15
* If you are using Boson Simulator
for this lab, apply following
command:
B(config-router)# default 5

ROUTING TABLE OF ROUTER-A

(AFTER PERFORMING REDISTRIBUTION ON ROUTER-B)

A# show ip route

NOTE-1: Routing Table of Router-A has been completed (in other

words convergence on Router-A has been done).

NOTE-2: When a protocol (e.g. IGRP) enters into a different

protocol (e.g. RIP), it adopts the same language of the
routing protocol into which it is entering, e.g in the
above case IGRP (network 200.100.100.0) has changed its
language from IGRP to RIP and also has changed its
metric value i.e. 5

RIP [100/1] (in case of RIP, 1 is called hop count)

IGRP (100/5] (in case of IGRP, 5 is called metric)

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 8

REDISTRIBUTION (LAB #2)

Figure-2d
(Note: Lab results are produced using Packet Tracer 5.0 Simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface serial 1/1

A(config-if)# ip address 3.0.0.2 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 9

C(config)# interface serial 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A, B & C

(BEFORE RUNNING ANY PROTOCOL)

A# show ip route

B# show ip route

C# show ip route

RUNNING RIP ON ROUTER-A, B & C

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 3.0.0.0

B(config)# router rip

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0

C(config)# router rip

C(config-router)# network 2.0.0.0
C(config-router)# network 3.0.0.0

ROUTING TABLE OF ROUTER-A, B & C

(AFTER RUNNING RIP ON ROUTER-A, B & C)

A# show ip route

B# show ip route

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 10

RUNNING IGRP ON ROUTER-A, B & C

A(config)# router igrp 1
A(config-router)# network 200.100.50.0

B(config)# router igrp 1

B(config-router)# network 200.100.100.0

C(config)# router igrp 1

C(config-router)# network 200.100.150.0

ROUTING TABLE OF ROUTER-A

(AFTER RUNNING IGRP ON ROUTER-A, B & C)

A# show ip route

B# show ip route

C# show ip route

NOTE: After running IGRP on Router-A, B & C, we have found there is

no change in routing table of Router-A, network 200.100.100.0
and network 200.100.150.0 is not found on Router-A. Therefore,
we'll perform re-distribution method at all routers.

PERFORMING REDISTRIBUTION ON ROUTER-A, B & C

A(config)# router rip
A(config-router)# redistribute igrp 1
A(config-router)# default-metric 10

B(config)# router rip

B(config-router)# redistribute igrp 1
B(config-router)# default-metric 10

C(config)# router rip

C(config-router)# redistribute igrp 1
C(config-router)# default-metric 10

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 11

ROUTING TABLE OF ROUTER-A

(AFTER PERFORMING REDISTRIBUTION ON ROUTER-A,B & C)

A# show ip route

B# show ip route

C# show ip route

NOTE: Routing tables of Router-A, B & C have been completed.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 12

LECTURE NO. 3
28 Nov 2008
RUNNING TWO PROTOCOLS AT THE SAME ROUTER
If two protocols are running at the same time, the protocol with lesser
Administrative Distance shall have priority.

Figure-3a
(Note: Lab results are produced using Boson Simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# clock rate 64000
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# clock rate 64000
B(config-if)# no shutdown

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 13

ROUTING TABLE OF ROUTER-A, B & C

(BEFORE RUNNING RIP ON ROUTER-A, B & C)

A# show ip route

B# show ip route

C# show ip route

RUNNING RIP ON ROUTER-A, B & C

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router rip

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0
B(config-router)# network 200.100.100.0

C(config)# router rip

C(config-router)# network 2.0.0.0
C(config-router)# network 200.100.50.0

ROUTING TABLE OF ROUTER-A, B & C

(AFTER RUNNING RIP ON ROUTER-A, B & C)

A# show ip route

B# show ip route

C# show ip route

RUNNING IGRP ON ROUTER-B & C

B(config)# router igrp 100
B(config-router)# network 2.0.0.0

C(config)# router igrp 100

C(config-router)# network 2.0.0.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 14

ROUTING TABLE OF ROUTER-A, B & C

(AFTER RUNNING IGRP ON ROUTER-B & C)

A# show ip route

NOTE: Network 200.100.150.0 is not found on Router-A.

B# show ip route

NOTE: Administrative distance value of RIP is 120 and IGRP is 100,

therefore network 200.100.150.0 has reached on Router-B as {I}
with an administrative distance value of 100 and metric value
of 651.

C# show ip route

PERFORMING REDISTRIBUTION ON ROUTER-B

B(config)# router rip
B(config-router)# redistribute igrp 100
B(config-router)# default-metric 7

ROUTING TABLE OF ROUTER-A

(AFTER PERFORMING REDISTRIBUTION ON ROUTER-B)

A# show ip route

NOTE: Network 200.100.150.0 has been reached on Router-A.

HOW TO SET DELAY & BANDWIDTH VALUE?

SETTING DELAY AND BANDWIDTH VALUE

A(config)# interface serial 1/0
A(config-if)# delay 1000

NOTE: If you set any value for delay, it will be displayed with one
extra zero.

A(config-if)# bandwidth 500

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 15

CHECKING DELAY AND BANDWIDTH VALUE

A# show interface serial 1/0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 16

CALCULATING METRIC VALUE OF EIGRP

FORMULA = [ (107 ÷ Bandwidth Minimum )+ (Total Delay ÷ 10) ] x 256

Figure-3b
(Note: Lab results are produced using Packet Tracer 5.0 Simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface serial 1/1

A(config-if)# ip address 3.0.0.2 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 17

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

RUNNING EGRP ON ROUTER-A, B & C

A(config)# router eigrp 200
A(config-router)# network 1.0.0.0
A(config-router)# network 2.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router eigrp 200

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0
B(config-router)# network 200.100.100.0

C(config)# router eigrp 200

C(config-router)# network 2.0.0.0
C(config-router)# network 3.0.0.0
C(config-router)# network 200.100.150.0

ROUTING TABLE OF ROUTER-A, B & C

(AFTER RUNNING EIGRP ON ROUTER-A, B & C)

A# show ip route

B# show ip route

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 18

SETTING DELAY AND BANDWIDTH VALUE ON ROUTER-A & B

A(config)# interface serial 1/0
A(config-if)# delay 1000
A(config-if)# bandwidth 500

B(config)# interface serial 1/1

B(config-if)# delay 500
B(config-if)# bandwidth 256

A# show interface serial 1/0

B# show interface serial 1/1

A# show ip route

HOW TO VERIFYING EIGRP METRIC VALUE?

= [ (107 ÷ Bandwidth Minimum )+ (Total Delay ÷ 10) ] x 256

= [(10000000÷Bandwidth-1 Bandwidth on S1/1 of Router-A is minimum)+((Delay-1+Delay-2) ÷ 10)]x256

= [ (10000000 ÷ 256) + ( (10000 + 15000) ÷ 10) ] x 256

= [ 39062 + (25000 ÷ 10) ] x 256

= [ 39062 + 2500 ] x 256

= 41562 x 256

= 10639872 (This is the EIGRP Metric Value of network 2.0.0.0 on Router-A)

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 19

MANIPULATING METRIC IN CASE OF IGRP

A(config)# Router IGRP 50

A(config-router)# metric weights 0 1 0 0 0 0

TOS K1 K2 K3 K4 K5

TOS = Type of Service

K1 = Bandwidth
K2 = Reliability
K3 = Delay
K4 = Loading
K5 = MTU

A# show ip protocol

CALCULATING METRIC VALUE OF IGRP

FORMULA: = [ (107 ÷ Bandwidth Minimum )+ (Total Delay ÷ 10) ]

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 20

LECTURE NO. 4
01 Dec 2008
VLSM (Variable Length Subnet Mask)

Figura-4a

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 21

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 22

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 23

LECTURE NO. 5
04 Dec 2008
IPv6
INTRODUCTION: IP version 6 (IPv6) is a new version of the Internet Protocol,
designed as the successor to IP version 4 (IPv4). The changes from IPv4 to IPv6
fall primarily into the following categories:

ƒ EXPANDED ADDRESSING CAPABILITIES

IPv6 increases the IP address size from 32 bits to 128 bits, to support more
levels of addressing hierarchy, a much greater number of addressable nodes,
and simpler auto-configuration of addresses. The scalability of multicast
routing is improved by adding a "scope" field to multicast addresses. And a
new type of address called an "anycast address" is defined, used to send a
packet to any one of a group of nodes.

ƒ HEADER FORMAT SIMPLIFICATION

Some IPv4 header fields have been dropped or made optional, to reduce the
common-case processing cost of packet handling and to limit the bandwidth
cost of the IPv6 header.

ƒ IMPROVED SUPPORT FOR EXTENSIONS AND OPTIONS

Changes in the way IP header options are encoded allows for more efficient
forwarding, less stringent limits on the length of options, and greater
flexibility for introducing new options in the future.

ƒ FLOW LABELING CAPABILITY

A new capability is added to enable the labeling of packets belonging to
particular traffic "flows" for which the sender requests special handling,
such as non-default quality of service or "real-time" service.

ƒ AUTHENTICATION AND PRIVACY CAPABILITIES

Extensions to support authentication, data integrity, and (optional) data
confidentiality are specified for IPv6.

IPv6 HEADER FORMAT:

Version Traffic Class Flow Label
Payload Length Next Header Hop Limit

Source Address

Destination Header

IPv6 SAMPLE IP ADDRESS:

2003 : 0000 : 0000 : 012a :: 0000 : 0000 : 0000 : 000e

Here in above example, each number is a hexadecimal number and each

number is equals to 4 binary numbers. Therefore one IPv6 address
consists of 128 binary numbers.

HOW TO MAKE IPV6 SHORT?

2003 : 0000 : 0000 : 012a :: 0000 : 0000 : 0000 : 000e

2003 : 0 : 0 : 12a :: 0 : 0 : 0 : e
2003 : 0 : 0 : 12a :: e

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 24

UNICAST IPv6 ADDRESSES

A unicast address identifies a single interface within the scope of the type of
unicast address. With the appropriate unicast routing topology, packets addressed
to a unicast address are delivered to a single interface. The following types of
addresses are unicast IPv6 addresses:

• Aggregatable global unicast addresses

• Link-local addresses
• Site-local addresses
• Special addresses
• Compatibility addresses
• NSAP addresses

AGGREGATABLE GLOBAL UNICAST ADDRESSES

Aggregatable global unicast addresses, identified by the Format Prefix (FP) of 001,
are equivalent to public IPv4 addresses. They are globally routable and reachable
on the IPv6 Internet. Aggregatable global unicast addresses are also known as
global addresses.

As the name implies, aggregatable global unicast addresses are designed to be

aggregated or summarized to produce an efficient routing infrastructure. Unlike the
current IPv4-based Internet, which has a mixture of both flat and hierarchical
routing, the IPv6-based Internet has been designed from its foundation to support
efficient, hierarchical addressing and routing. The scope, the region of the IPv6
internetwork over which the address is unique, of an aggregatable global unicast
address is the entire IPv6 Internet.

The fields in the aggregatable global unicast address are described as follows:

• TLA ID
The TLA ID field indicates the Top Level Aggregation Identifier (TLA ID) for
the address. The size of this field is 13 bits. The TLA identifies the
highest level in the routing hierarchy. TLAs are administered by IANA and
allocated to local Internet registries that, in turn, allocate individual
TLA IDs to large, global Internet service providers (ISPs). A 13-bit field
allows up to 8,192 different TLA IDs. Routers in the highest level of the
IPv6 Internet routing hierarchy (called default-free routers) do not have a
default route--only routes with 16-bit prefixes that correspond to the
allocated TLAs.

• Res
The Res field is reserved for future use in expanding the size of either the
TLA ID or the NLA ID. The size of this field is 8 bits.

• NLA ID
The NLA ID field indicates the Next Level Aggregation Identifier (NLA ) for
the address. The NLA ID is used to identify a specific customer site. The
size of this field is 24 bits. The NLA ID allows an ISP to create multiple
levels of addressing hierarchy to organize addressing and routing and to
identify sites. The structure of the ISP's network is not visible to the
default-free routers.

• SLA ID
The SLA ID field indicates the Site Level Aggregation Identifier (SLA ID)
for the address. The SLA ID is used by an individual organization to
identify subnets within its site. The size of this field is 16 bits. The
organization can use these 16 bits within its site to create 65,536 subnets
or multiple levels of addressing hierarchy and an efficient routing
infrastructure. With 16 bits of subnetting flexibility, an aggregatable
global unicast prefix assigned to an organization is equivalent to that
organization being allocated an IPv4 Class A network ID (assuming that the

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 25

last octet is used for identifying nodes on subnets). The structure of the
customer's network is not visible to the ISP.

• Interface ID
The Interface ID field indicates the interface of a node on a specific
subnet. The size of this field is 64 bits.

The following illustration shows how the fields within the aggregatable global
unicast address create a three-level topological structure.

The public topology is the collection of larger and smaller ISPs that provide
access to the IPv6 Internet. The site topology is the collection of subnets within
an organization's site. The interface identifier identifies a specific interface on
a subnet within an organization's site. For more information about aggregatable
global unicast addresses, see RFC 2374, "An IPv6 Aggregatable Global Unicast
Address Format."

LOCAL-USE UNICAST ADDRESSES

There are two types of local-use unicast addresses:

1. Link-local addresses, which are used between on-link neighbors and for
Neighbor Discovery processes.
2. Site-local addresses, which are used between nodes that communicate with
other nodes in the same site.

LINK-LOCAL ADDRESSES
Link-local addresses, identified by the FP of 1111 1110 10, are used by nodes when
communicating with neighboring nodes on the same link. For example, on a single
link IPv6 network with no router, link-local addresses are used to communicate
between hosts on the link. Link-local addresses are equivalent to Automatic Private
IP Addressing (APIPA) IPv4 addresses (using the 169.254.0.0/16 prefix). The scope
of a link-local address is the local link. A link-local address is required for
Neighbor Discovery processes and is always automatically configured, even in the
absence of all other unicast addresses. For more information about the address
autoconfiguration process for link-local addresses.

Link-local addresses always begin with FE80. With the 64-bit interface identifier,
the prefix for link-local addresses is always FE80::/64. An IPv6 router never
forwards link-local traffic beyond the link.

SITE-LOCAL ADDRESSES
Site-local addresses, identified by the FP of 1111 1110 11, are equivalent to the
IPv4 private address space (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16). For
example, private intranets that do not have a direct, routed connection to the IPv6
Internet can use site-local addresses without conflicting with aggregatable global
unicast addresses. Site-local addresses are not reachable from other sites, and
routers must not forward site-local traffic outside of the site. Site-local
addresses can be used in addition to aggregatable global unicast addresses. The
scope of a site-local address is the site (the organization internetwork).
Unlike link-local addresses, site-local addresses are not automatically configured
and must be assigned either through stateless or stateful address configuration
processes. For more information.

The first 48-bits are always fixed for site-local addresses, beginning with
FEC0::/48. After the 48 fixed bits is a 16-bit subnet identifier (Subnet ID field)
that provides 16 bits with which you can create subnets within your organization.
With 16 bits, you can have up to 65,536 subnets in a flat subnet structure, or you
can subdivide the high-order bits of the Subnet ID field to create a hierarchical
and aggregatable routing infrastructure. After the Subnet ID field is a 64-bit
Interface ID field that identifies a specific interface on a subnet.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 26

The aggregatable global unicast address and site-local address share the same
structure beyond the first 48 bits of the address. In aggregatable global unicast
addresses, the SLA ID identifies the subnet within an organization. For site-local
addresses, the Subnet ID performs the same function. Because of this, you can
assign a specific subnet number to identify a subnet that is used for both site-
local and aggregatable global unicast addresses.

SPECIAL ADDRESSES
The following are special IPv6 addresses:

• Unspecified address
The unspecified address (0:0:0:0:0:0:0:0 or ::) is used only to indicate the
absence of an address. It is equivalent to the IPv4 unspecified address of
0.0.0.0. The unspecified address is typically used as a source address for
packets that are attempting to verify the uniqueness of a tentative address.
The unspecified address is never assigned to an interface or used as a
destination address.

• Loopback address
The loopback address (0:0:0:0:0:0:0:1 or ::1) is used to identify a loopback
interface, enabling a node to send packets to itself. It is equivalent to
the IPv4 loopback address of 127.0.0.1. Packets addressed to the loopback
address are never sent on a link or forwarded by an IPv6 router.

COMPATIBILITY ADDRESSES
To aid in the migration from IPv4 to IPv6 and facilitate the coexistence of both
types of hosts, the following addresses are defined:

• IPv4-compatible address
The IPv4-compatible address, 0:0:0:0:0:0:w.x.y.z or ::w.x.y.z (where w.x.y.z
is the dotted decimal representation of a public IPv4 address), is used by
dual-stack nodes that are communicating with IPv6 over an IPv4
infrastructure. Dual-stack nodes are nodes with both IPv4 and IPv6
protocols. When the IPv4-compatible address is used as an IPv6 destination,
IPv6 traffic is automatically encapsulated with an IPv4 header and sent to
the destination by using the IPv4 infrastructure.

• IPv4-mapped address
The IPv4-mapped address, 0:0:0:0:0:FFFF:w.x.y.z or ::FFFF:w.x.y.z, is used
to represent an IPv4-only node to an IPv6 node. It is used only for internal
representation. The IPv4-mapped address is never used as a source or
destination address for an IPv6 packet. The IPv6 protocol does not support
the use of IPv4-mapped addresses.

• 6to4 address
The 6to4 address is used for communicating between two nodes running both
IPv4 and IPv6 over the Internet. The 6to4 address is formed by combining the
prefix 2002::/16 with the 32 bits of the public IPv4 address of the node,
forming a 48-bit prefix. For example, for the IPv4 address of 131.107.0.1,
the 6to4 address prefix is 2002:836B:1::/48. For more information about
6to4.

NSAP ADDRESSES
To provide a means for mapping Network Service Access Point (NSAP) addresses to
IPv6 addresses, NSAP addresses use the FP of 0000001 and map the last 121 bits of
the IPv6 address to an NSAP address. For more information about the four types of
NSAP address mappings, see RFC 1888, "OSI NSAPs and IPv6."

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 27

LECTURE NO. 6
06 Dec 2008
IPv6
ENABLING IPv6 ADDRESS
B(config)# ipv6 unicast-routing
B(config)# Interface FastEthernet 0/0
B(config-if)# ipv6 enable

BEFORE ASSIGNING IPV6 ADDRESS ON FASTETHERNET 0/0

B# show ipv6 interface f0/0

ASSIGNING IPV6 ADDRESS ON FASTETHERNET 0/0

B(config)# interface fastethernet 0/0
B(config)# ipv6 address 2001:0:0:3::1/64
B(config-if)# exit
B(config)# exit

AFTER ASSIGNING IPV6 ADDRESS ON FASTETHERNET 0/0

B# show ipv6 interface fastethernet 0/0

ASSIGNING IPV6 ADDRESS AT FASTETHERNET 0/0

(USING LINK LOCAL ADDRESS)

B(config)# interface fastethernet 0/0

B(config-if)# no ipv6 address
B(config-if)# ipv6 address 2001:0:0::/64 eui-64
B(config-if)# exit
B(config)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 28

B# show ipv6 interface fastethernet 0/0

HOW TO CHECK MAC ADDRESS:

B# show interface fastethernet 0/0

HOW MAC ADDRESS CONVERTS INTO LINK LOCAL ADDRESS ?

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 29

LECTURE NO. 7
17 Dec 2008
OSPF (Open Shortest Path First)

BACKGROUND
Open Shortest Path First (OSPF) is a routing protocol developed for Internet
Protocol (IP) networks by the Interior Gateway Protocol (IGP) working group of the
Internet Engineering Task Force (IETF). The working group was formed in 1988 to
design an IGP based on the Shortest Path First (SPF) algorithm for use in the
Internet. Similar to the Interior Gateway Routing Protocol (IGRP), OSPF was created
because in the mid-1980s, the Routing Information Protocol (RIP) was increasingly
incapable of serving large, heterogeneous internetworks. This chapter examines the
OSPF routing environment, underlying routing algorithm, and general protocol
components.

OSPF was derived from several research efforts, including Bolt, Beranek, and
Newman's (BBN's) SPF algorithm developed in 1978 for the ARPANET (a landmark
packet-switching network developed in the early 1970s by BBN), Dr. Radia Perlman's
research on fault-tolerant broadcasting of routing information (1988), BBN's work
on area routing (1986), and an early version of OSI's Intermediate System-to-
Intermediate System (IS-IS) routing protocol.

OSPF has two primary characteristics. The first is that the protocol is open, which
means that its specification is in the public domain. The OSPF specification is
published as Request For Comments (RFC) 1247. The second principal characteristic
is that OSPF is based on the SPF algorithm, which sometimes is referred to as the
Dijkstra algorithm, named for the person credited with its creation.
OSPF is a link-state routing protocol that calls for the sending of link-state
advertisements (LSAs) to all other routers within the same hierarchical area.
Information on attached interfaces, metrics used, and other variables is included
in OSPF LSAs. As OSPF routers accumulate link-state information, they use the SPF
algorithm to calculate the shortest path to each node.

As a link-state routing protocol, OSPF contrasts with RIP and IGRP, which are
distance-vector routing protocols. Routers running the distance-vector algorithm
send all or a portion of their routing tables in routing-update messages to their
neighbors.

ROUTING HIERARCHY
Unlike RIP, OSPF can operate within a hierarchy. The largest entity within the
hierarchy is the autonomous system (AS), which is a collection of networks under a
common administration that share a common routing strategy. OSPF is an intra-AS
(interior gateway) routing protocol, although it is capable of receiving routes
from and sending routes to other ASs.

An AS can be divided into a number of areas, which are groups of contiguous

networks and attached hosts. Routers with multiple interfaces can participate in
multiple areas. These routers, which are called Area Border Routers, maintain
separate topological databases for each area.
A topological database is essentially an overall picture of networks in
relationship to routers. The topological database contains the collection of LSAs
received from all routers in the same area. Because routers within the same area
share the same information, they have identical topological databases.

The term domain sometimes is used to describe a portion of the network in which all
routers have identical topological databases. Domain is frequently used
interchangeably with AS.
An area's topology is invisible to entities outside the area. By keeping area
topologies separate, OSPF passes less routing traffic than it would if the AS were
not partitioned.

Area partitioning creates two different types of OSPF routing, depending on whether
the source and the destination are in the same or different areas. Intra-area

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 30

routing occurs when the source and destination are in the same area; interarea
routing occurs when they are in different areas.
An OSPF backbone is responsible for distributing routing information between areas.
It consists of all Area Border Routers, networks not wholly contained in any area,
and their attached routers. Below figure shows an example of an internetwork with
several areas.

In the figure, routers 4, 5, 6, 10, 11, and 12 make up the backbone. If Host H1 in
Area 3 wants to send a packet to Host H2 in Area 2, the packet is sent to Router
13, which forwards the packet to Router 12, which sends the packet to Router 11.
Router 11 then forwards the packet along the backbone to Area Border Router 10,
which sends the packet through two intra-area routers (Router 9 and Router 7) to be
forwarded to Host H2.

The backbone itself is an OSPF area, so all backbone routers use the same
procedures and algorithms to maintain routing information within the backbone that
any area router would. The backbone topology is invisible to all intra-area
routers, as are individual area topologies to the backbone.
Areas can be defined in such a way that the backbone is not contiguous. In this
case, backbone connectivity must be restored through virtual links. Virtual links
are configured between any backbone routers that share a link to a nonbackbone area
and function as if they were direct links.

An OSPF AS Consists of Multiple

Areas Linked by Routers

AS border routers running OSPF learn about exterior routes through exterior gateway
protocols (EGPs), such as Exterior Gateway Protocol (EGP) or Border Gateway
Protocol (BGP), or through configuration information. For more information about
these protocols, see Chapter 39, "Border Gateway Protocol."

SPF ALGORITHM
The Shortest Path First (SPF) routing algorithm is the basis for OSPF operations.
When an SPF router is powered up, it initializes its routing-protocol data
structures and then waits for indications from lower-layer protocols that its
interfaces are functional.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 31

After a router is assured that its interfaces are functioning, it uses the OSPF
Hello protocol to acquire neighbors, which are routers with interfaces to a common
network. The router sends hello packets to its neighbors and receives their hello
packets. In addition to helping acquire neighbors, hello packets also act as
keepalives to let routers know that other routers are still functional.

On multiaccess networks (networks supporting more than two routers), the Hello
protocol elects a designated router and a backup designated router. Among other
things, the designated router is responsible for generating LSAs for the entire
multiaccess network. Designated routers allow a reduction in network traffic and in
the size of the topological database.

When the link-state databases of two neighboring routers are synchronized, the
routers are said to be adjacent. On multiaccess networks, the designated router
determines which routers should become adjacent. Topological databases are
synchronized between pairs of adjacent routers. Adjacencies control the
distribution of routing-protocol packets, which are sent and received only on
adjacencies.

Each router periodically sends an LSA to provide information on a router's

adjacencies or to inform others when a router's state changes. By comparing
established adjacencies to link states, failed routers can be detected quickly, and
the network's topology can be altered appropriately. From the topological database
generated from LSAs, each router calculates a shortest-path tree, with itself as
root. The shortest-path tree, in turn, yields a routing table.

PACKET FORMAT
All OSPF packets begin with a 24-byte header, as illustrated in figure (on next
page).
In below figure OSPF Packets Consist of Nine Fields:

The following descriptions summarize the header fields illustrated in above figure.

• Version number—Identifies the OSPF version used.

• Type—Identifies the OSPF packet type as one of the following:
ƒ Hello—Establishes and maintains neighbor relationships.
ƒ Database description Describes the contents of the topological database.
These messages are exchanged when an adjacency is initialized.
ƒ Link-state request Requests pieces of the topological database from
neighbor routers. These messages are exchanged after a router discovers
(by examining database-description packets) that parts of its topological
database are outdated.
ƒ Link-state update Responds to a link-state request packet. These messages
also are used for the regular dispersal of LSAs. Several LSAs can be
included within a single link-state update packet.
ƒ Link-state acknowledgment Acknowledges link-state update packets.

• Packet length Specifies the packet length, including the OSPF header, in bytes.
• Router ID Identifies the source of the packet.
• Area ID Identifies the area to which the packet belongs. All OSPF packets are
associated with a single area.
• Checksum—Checks the entire packet contents for any damage suffered in transit.
• Authentication type Contains the authentication type. All OSPF protocol
exchanges are authenticated. The authentication type is configurable on per-area
basis.
• Authentication Contains authentication information.
• Data Contains encapsulated upper-layer information.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 32

ADDITIONAL OSPF FEATURES

Additional OSPF features include equal-cost, multipath routing, and routing based
on upper-layer type-of-service (TOS) requests. TOS-based routing supports those
upper-layer protocols that can specify particular types of service. An application,
for example, might specify that certain data is urgent. If OSPF has high-priority
links at its disposal, these can be used to transport the urgent datagram.

OSPF supports one or more metrics. If only one metric is used, it is considered to
be arbitrary, and TOS is not supported. If more than one metric is used, TOS is
optionally supported through the use of a separate metric (and, therefore, a
separate routing table) for each of the eight combinations created by the three IP
TOS bits (the delay, throughput, and reliability bits). For example, if the IP TOS
bits specify low delay, low throughput, and high reliability, OSPF calculates
routes to all destinations based on this TOS designation.

IP subnet masks are included with each advertised destination, enabling variable-
length subnet masks. With variable-length subnet masks, an IP network can be broken
into many subnets of various sizes. This provides network administrators with extra
network-configuration flexibility.

ADVANTAGES OF OSPF
1. Changes in an OSPF network are propagated quickly.
2. OSPF is heirarchical, using area 0 as the top as the heirarchy.
3. OSPF is a Link State Algorithm.
4. OSPF supports Variable Length Subnet Masks (VLSM).
5. OSPF uses multicasting within areas.
6. After initialization, OSPF only sends updates on routing table sections
which have changed, it does not send the entire routing table.
7. Using areas, OSPF networks can be logically segmented to decrease the size
of routing tables. Table size can be further reduced by using route
summarization.
8. OSPF is an open standard, not related to any particular vendor.

DISADVANTAGES OF OSPF
1. OSPF is very processor intensive.
2. OSPF maintains multiple copies of routing information, increasing the amount
of memory needed.
3. Using areas, OSPF can be logically segmented (this can be a good thing and a
bad thing).
4. OSPF is not as easy to learn as some other protocols.
5. In the case where an entire network is running OSPF, and one link within it
is "bouncing" every few seconds, OSPF updates would dominate the network by
informing every other router every time the link changed state.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 33

WILD CARD MASK OF ACL & OSPF

A wildcard mask is a sequence of numbers that streamlines packet routing within the
subnets of a proprietary network. A subnet can be a geographically defined local
area network (LAN).

Alternatively, a subnet may define security boundaries, departmental boundaries,

multicast zones or hardware security parameters. The use of a mask saves a router
the task of having to handle an entire IP address because the router deals only
with the digits selected by the mask. Wildcard masks are commonly used with Open
Shortest Path First (OSPF) router protocols and in access control lists for Cisco
routers.

Once a packet has arrived at an organization's main gateway with its network
number, that packet is routed to its ultimate destination using a subnet number.
The wildcard mask is usually a string of binary digits shown over the subnet
number, telling the router which parts of the subnet number to look at. A binary
"0" over a particular digit in the subnet number says "Pay attention to this
digit." A "1" says "Ignore this digit." In a wildcard mask, all the binary "0"s in
a conventional subnet mask are replaced by "1"s and all the "1"s are replaced by
"0"s.

wildcard mask is basically a mask of bits that indicates which parts of an IP

address can assume any value. In the Cisco IOS, they are used in several places,
for example:

• To indicate the size of a network or subnet for some routing protocols, such
as OSPF.
• To indicate what IP addresses should be permitted or denied in access
control lists (ACLs).

9 Wildcard mask is very different from subnet mask.

9 The values for subnet mask can be 128,192,224,240,248,252,254 and 255.
9 On the other hand, wild card mask values are: 127,63,31,15,7,3,1 and 0.
9 The tip out here is that simply subtract subnet mask value from 255.
9 In ACLS and OSPF network statements, we use wild card mask, 127 will be:
011111111 which means match the first bit and ignore the other 7.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 34

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 35

ASSIGNMENT
Calculate WCM of Odd and Even Numbers (saperately), for a subnet starting from
19 2.168.1.0 to 192.168.1.31.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 36

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 37

UNDERSTANDING WILD CARD MASK - LAB

Figure-7a
(Note: Lab results are produced using GNS3 Simulator)

Question #1 Using access list, deny below mentioned static routes, so that they
cannot reach on Router-A:

192.2.4.0
192.2.5.0
192.2.6.0
192.2.7.0

Question #2 Using access list, deny below mentioned odd static routes on Router-A:

192.2.1.0
192.2.3.0
192.2.5.0
192.2.7.0

Question #3 Using access list, deny static routes 192.2.0.0 and permit static
routes (mentioned below) for Router-A:

192.2.1.0
192.2.2.0
192.2.3.0
192.2.4.0
192.2.5.0
192.2.6.0
192.2.7.0

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.1.1.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 38

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/1
B(config-if)# ip address 1.1.1.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A & B

A# show ip route

B# show ip route

RUNNING RIP ON ROUTER-A, & B

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router rip

B(config-router)# network 1.0.0.0
B(config-router)# network 200.100.100.0

ROUTING TABLE OF ROUTER-A & B

(AFTER RUNNING RIP)

A# show ip route

B# show ip route

DEFINING 8 STATIC ROUTES ON ROUTER-B

B(config)# ip route 192.2.0.0 255.255.255.0 null 0
B(config)# ip route 192.2.1.0 255.255.255.0 null 0
B(config)# ip route 192.2.2.0 255.255.255.0 null 0
B(config)# ip route 192.2.3.0 255.255.255.0 null 0
B(config)# ip route 192.2.4.0 255.255.255.0 null 0
B(config)# ip route 192.2.5.0 255.255.255.0 null 0
B(config)# ip route 192.2.6.0 255.255.255.0 null 0
B(config)# ip route 192.2.7.0 255.255.255.0 null 0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 39

REDISTRIBUTION OF STATIC ROUTES INTO RIP

B(config)# router rip
B(config-router)# redistribute static
B(config-router)# default-metric 1

ROUTING TABLE OF ROUTER-A AND B

(AFTER APPLYING REDISTRIBUTION)

B# show ip route

A# show ip route

NOTE: Static routes of router-b have reached on Router-A.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 40

SOLUTION OF QUESTION NO. 1

DEFINING ACCESS-LIST ON ROUTER-A

A(config)# access-list 60 deny 192.2.4.0 0.0.3.0
A(config)# access-list 60 permit any

APPLYING ACCESS-LIST ON ROUTER-A

A(config)# router rip
A(config-router)# distribute-list 60 in serial 1/0

ROUTING TABLE OF ROUTER-A

(AFTER APPLYING ACCESS-LIST AT SERIAL 1/0 INTERFACE OF ROUTER-A)
A# show ip route

NOTE: After applying access-list 60 on Router-A, you’ll notice that

static routes 192.2.4.0 to 192.2.7.0 are still reaching on
Router-A. Actually dead timer for these routes (00:00:34)
indicates that these routes have been blocked and these blocked
routes will be disappeared from the routing table, after you
apply following command on Router-A (which is used to clear the
routing table.

A# clear ip route *

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 41

A# show ip route

SOLUTION OF QUESTION NO. 2

REMOVING ACCESS-LIST FROM ROUTER-A

A(config)# no access-list 60
A(config)# router rip
A(config-router)# no distribute-list 60 in serial 1/0

A# show ip route

DEFINING ACCESS-LIST ON ROUTER-A

A(config)# access-list 44 deny 192.2.1.0 0.0.6.0
A(config)# access-list 44 permit any

APPLYING ACCESS-LIST ON ROUTER-A

A(config)# router rip
A(config-router)# distribute-list 44 in serial 1/0

ROUTING TABLE OF ROUTER-A

(AFTER APPLYING ACCESS-LIST AT SERIAL 1/0 INTERFACE OF ROUTER-A)

A# clear ip route *

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 42

A# show ip route

NOTE: After applying access-list 44 on Router-A, static routes

192.2.1.0 192.2.3.0 192.2.5.0 192.2.7.0 have been blocked.

SOLUTION OF QUESTION NO. 3

REMOVING ACCESS-LIST FROM ROUTER-A

A(config)# no access-list 44
A(config)# router rip
A(config-router)# no distribute-list 44 in serial 1/0

DEFINING ACCESS-LIST ON ROUTER-A

A(config)# access-list 88 deny host 192.2.0.0
A(config)# access-list 88 permit 192.2.0.0 0.0.7.0

NOTE: If you notice that, in the above line, we have denied 192.1.0.0
but in the next line, we have permitted 192.1.0.0.

Why we have permitted 192.1.0.0 in the next line?

Ans. We can only calculate wild card mask for a single ip,
subnet or network. According to question no. 3, we have
to deny 192.2.0.0 and permit ip 192.2.1.0 to 192.2.7.0

192.2.1.0 to 192.2.7.0 is not a complete subnet The

range of this subnet starts from 192.2.0.0 to 192.2.7.0.
To complete this subnet, we have added 192.2.0.0 ip in
this range and consequently, wild card mask for this
subnet comes to 0.0.7.0.

Now, if we permit subnet 192.2.0.0 to 192.2.7.0, it will

not permit 192.2.0.0 ip, because this ip is already
denied in the previous line, but it will permit ips
192.2.1.0 to 192.2.7.0.

APPLYING ACCESS-LIST ON ROUTER-A

A(config)# router rip
A(config-router)# distribute-list 88 in serial 1/0

ROUTING TABLE OF ROUTER-A

(AFTER APPLYING ACCESS-LIST AT SERIAL 1/0 INTERFACE OF ROUTER-A)

A# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 43

ROUTER-ID
a. If there is no concept of virtual/logical interfaces, then the highest IP
address (amongst the IP addresses on a router interfaces) becomes Router-ID.

b. If there is one virtual/logical interface (e.g. loopback) on a router, then it

becomes Router-ID (even if it has the smaller IP address amongst the IP
addresses on the same router).

c. If there are multiple virtual/logical interfaces on a router, then the highest

IP address (amongst the virtual/logical IP addresses on the same router) becomes
Router-ID.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 44

LECTURE NO. 8
19 Dec 2008
ROUTER-ID

CONFIGURING ROUTER-ID
(HARD CODED METHOD)

A(config)# router ospf 120

A(config-router)# router-id 2.0.0.1

DR, BDR & DR-OTHER

Under one Autonomous System, we can have multiple areas and under each area, we can
have multiple networks and each/every multi network (e.g. Ethernet/LAN) can have
its own DR (Designated Router), BDR (Backup Designated Router) and DR-Other
(Designated Router Other), provided.

If we run OSPF debug, we'll see following multicast addresses:-

224.0.0.5
224.0.0.6

And, if we run RIP debug, we'll see 255.255.255.255 broadcast address.

PRIORITY NUMBER
PRI No. is used to when election process for DR, BDR & DR-Other starts. In case of
OSPF, PRI No. of all CISCO routers is same i.e. 1 (one).

HOW ELECTION TAKE PLACE?

In the election process, the router having maximum PRI No. becomes DR. The router
having 2nd maximum PRI No. becomes BDR and all remaining routers becomes DR-Other.
If PRI No. of routers in a network is same, then the election shall take place on
the basis of Router-ID.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 45

AUTONOMOUS SYSTEM
A network with the same routing policies is called Autonomous System.

Figure-8a

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 46

In this figure, router having

PRI No. 15 has become DR on
its Fast-Ethernet 1/0
interface. Router having PRI
No. 13 has become BDR on its
Fast-Ethernet 1/0 interface.
All other routers have become
DR-Other on their Fast-
Ethernet 1/0 interfaces.
Figure-8b

In this figure, all the

routers have the same PRI No.
i.e. 11 on their Fast-Ethernet
1/0 interfaces, therefore,
router having Router-ID
20.0.0.1 has become DR on its
Fast-Ethernet 1/0 interface.
Router having Router-ID
16.0.0.1 has become BDR on its
Fast-Ethernet 1/0 interface.
All other routers have become
DR-Other on their Fast-
Ethernet 1/0 interfaces.
Figutr-8c

If there is only one router,

it becomes DR.

Figure-8d

Now, if you add a new router,

it becomes BDR, even if it has
the greater PRI No. than the
PRI No. of DR.

Figure-8e

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 47

In this figure, you'll notice

that DR has smaller PRI No.
than BDR and DR-Other. You'll
also notice that DR-Other has
greater PRI No. than BDR.

To reset election, apply

following command
Figure-8f
A# clear ip ospf process

After applying above command,

you'll notice that DR has
swapped with DR-Other.

Figure-8g

Figure-8h

In this example,
let's suppose
the network was
running fine and
after some time
DR gets down.

Figure-8i

Now BDR becomes

DR and election
process between
DR-Others is
held for the
selection of BDR
and DR-Other.
Router having
PRI No. 10
becomes BDR and
Router with PRI
No. 4 becomes
DR-Other.
Figure-8j

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 48

Let's suppose,
after some time
old DR gets
stable. In this
situation it'll
become DR-Other,
even its PRI No.
is greater than
other routers.
Figure-8k

Figure-8l

Figure-8m

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 49

Figure-8n

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 50

LECTURE NO. 9
22 Dec 2008
ROUTER TYPES

INTERNAL ROUTER (IR)

A router having all its interfaces in the same area is called Internal Router.

BACKBONE INTERNAL ROUTER (BR)

A router having all its interfaces in area zero is called Backbone Router.

AREA BORDER ROUTER (ABR)

A router which connects and communicates area-0 with another area is called Area
Border Router.

AUTONOMOUS SYSTEM BORDER ROUTER (ASBR)

A router which connects and communicates two different autonomous systems is called
Autonomous System Border Router.

------------------------------------

Source: http://en.wikipedia.org/wiki/Open_Shortest_Path_First#OSPF_router_types

AREA BORDER ROUTER (ABR) An ABR is a router that connects one or more OSPF
areas to the main backbone network. It is
considered a member of all areas it is connected
to. An ABR keeps multiple copies of the link-state
database in memory, one for each area to which
that router is connected.

AUTONOMOUS SYSTEM BORDER ROUTER (ASBR) An ASBR is a router that is connected to

more than one AS and that exchanges routing
information with routers in other ASs. ASBRs
typically also run a non-IGP routing protocol
(e.g., BGP), or use static routes, or both. An
ASBR is used to distribute routes received from
other ASs throughout its own AS.

INTERNAL ROUTER (IR) An IR is a router that only has OSPF neighbor

relationships with interfaces in the same area.

BACKBONE ROUTER (BR) These are routers that are part of the OSPF
backbone. By definition, this includes all area
border routers, since those routers pass routing
information between areas. However, a backbone
router may also be a router that connects only to
other backbone (or area border) routers, and is
therefore not part of any area (other than Area
0).

NOTE THAT: An area border router is always a backbone router, but a

backbone router is not necessarily an area border
router.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 51

Figure-9a

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 52

LINK STATE ADVERTISEMENT

Source: Wikipedia

The Link-state advertisement (LSA) is a basic communication means of the OSPF

routing protocol for IP. It communicates the router's local routing topology to all
other local routers in the same OSPF area. OSPF is designed for scalability, so
some LSAs are not flooded out on all interfaces, but only on those that belong to
the appropriate area. In this way detailed information can be kept localized, while
summary information is flooded to the rest of the network.

The LSA types, defined in OSPF, are as follows:

Type 1 - Router LSA - the router lists the links to other routers or networks
in the same area, together with the metric. Type 1 LSAs are flooded across their
own area only. The link-state ID of type 1 LSA is the originating router ID.

Type 2 - Network LSA - the designated router on a broadcast segment (e.g.

Ethernet) lists which routers are joined together by the segment. Type 2 LSAs
are flooded across their own area only. The link-state ID of the type 2 LSA is
the IP interface address of the DR.

Type 3 - Summary LSA - an Area Border Router (ABR) takes information it has
learned on one of its attached areas and it can summarize it (but not by
default) before sending it out on other areas it is connected to. This
summarization helps provide scalability by removing detailed topology
information for other areas, because their routing information is summarized
into just an address prefix and metric. The summarization process can also be
configured to remove a lot of detailed address prefixes and replace them with a
single summary prefix, also helping scalability. The link-state ID is the
destination network number for type 3 LSAs.

Type 4 - ASBR-Summary LSA - this is needed because Type 5 External LSAs are
flooded to all areas and the detailed next-hop information may not be available
in those other areas. This is solved by an Area Border Router flooding the
information for the router (i.e. the Autonomous System Border Router) where the
type 5 originated. The link-state ID is the router ID of the described ASBR for
type 4 LSAs. This LSA describes the location of ASBR.

Type 5 - External LSA - these LSAs contain information imported into OSPF from
other routing processes. They are flooded to all areas (except stub areas). For
"External Type 1" LSAs routing decisions are made by adding the OSPF metric to
get to the ASBR and the external metric from there on, while for "External Type
2" LSAs only the external metric is used. The link-state ID of the type 5 LSA is
the external network number. This LSA describes the network information ASBR.

Type 6 - Group Membership LSA - this was defined for Multicast extensions to
OSPF (MOSPF), a multicast routing protocol which is not in general use.

Type 7 - Routers in a Not-so-stubby-area (NSSA) do not receive external LSAs

from Area Border Routers, but are allowed to send external routing information
for redistribution. They use type 7 LSAs to tell the ABRs about these external
routes, which the Area Border Router then translates to type 5 external LSAs and
floods as normal to the rest of the OSPF network.

Type 8 - a link-local only LSA for the IPv6 version of OSPF, which is known
as OSPFv3. A type 8 LSA is used to give information about link-local addresses
and a list of IPv6 addresses on the link. Type 8 is a specialized LSA that is
used in internetworking OSPF and Border Gateway Protocol (BGP).

Type 9 - a link-local "opaque" LSA (defined by RFC2370) in OSPFv2 and the

Intra-Area-Prefix LSA in OSPFv3. It is the OSPFv3 LSA that contains prefixes for
stub and transit networks in the link-state ID.

Type 10 - an area-local "opaque" LSA as defined by RFC2370. Opaque LSAs

contain information which should be flooded by other routers even if the router
is not able to understand the extended information itself. Typically type 10

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 53

LSAs are used for traffic engineering extensions to OSPF, flooding extra
information about links beyond just their metric, such as link bandwidth and
color.

Type 11 - an "opaque" LSA defined by RFC2370, which is flooded everywhere

except stub areas. This is the opaque equivalent of the type 5 external LSA.

The opaque LSAs, types 9, 10, and 11, are designated for upgrades to OSPF for
application-specific purposes. For example, OSPF-TE has traffic engineering
extensions to be used by RSVP-TE in Multiprotocol Label Switching (MPLS). Opaque
LSAs are used to flood link color and bandwidth information. Standard LSDB flooding
mechanisms are used for distribution of opaque LSAs. Each of the three types has a
different flooding scope.

For all types of LSAs, there are 20-byte LSA headers. One of the fields of the LSA
header is the link-state ID.

Each router link is defined as one of four types: type 1, 2, 3, or 4. The LSA
includes a link ID field that identifies, by the network number and mask, the
object that this link connects to.

Depending on the type, the link ID has different meanings.

Link
Description Link ID
type
point-to-point connection to another
1 neighboring router ID
router
IP address of Designated
2 connection to a transit network
Router
3 connection to a stub network IP network/subnet number
4 virtual link neighboring router ID

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 54

Source:
http://www.informit.com/library/content.aspx?b=CCIE_Practical_Studies_I&seqNum=132

The word LSA has been mentioned quite a bit. LSAs are what OSPF uses to build the
OSPF database. OSPF floods specific LSA types to specific portions of the OSPF
domain as dictated by the area and router type mentioned previously. LSA are
classified by type, and each type serves a specific purpose, as described in the
following list:

• Router LSA (Type 1)— This LSA contains information about a router and the
links that it has in an area. LSA type 1s are flooded only in that area. The
LSA also tells whether the router is a stub or ASBR, or whether it has one
end of a virtual link. OSPF represents these routes in the forwarding table
with an O.

• Network LSA (Type 2)— This LSA is used for transit networks within an area.
It describes the set of routers attached to a network. LSA Type 2s are not
flooded outside an area. OSPF represents these routes in the forwarding
table with an O.

• Summary LSAs for ABRs (Type 3)— These LSAs advertise internal networks to
routers in other areas, called OSPF interarea routes. The LSA might contain
a summary network or a single network. ABRs are the only router type that
generates this LSA type. OSPF represents these routes in the forwarding
table with an O IA.

• Summary LSA for ASBRs (Type 4)— These LSAs are used to advertise the
location of an ASBR. Routers searching for a path to an external network use
LSA Type 4 to determine the best next hop. OSPF represents these routes in
the forwarding table with an O IA. This LSA type is hard to remember, so you
can think of it as the "how do I get out here LSA."

• Autonomous system external LSAs (Type 5)— Type 5 LSAs are used to advertise
routes redistributed into OSPF. These routes are called OSPF external
routes, and they are flooded throughout the entire OSPF autonomous system,
except for stub, totally stubby, and NSSA areas. OSPF represents these
routes in the forwarding table with an O E1 or O E2, depending on the route.

• NSSA external LSA (Type 7)— This type of LSA is generated for the external
routes redistributed into a not-so-stubby area. They are flooded throughout
the NSSA area. When they hit an ABR, the ABR advertises them as Type 5 LSAs
into Area 0. Type 7 LSAs never leave the NSSA area. OSPF represents these
routes in the forwarding table with an O N1 or O N2, depending on how the
route was redistributed.

Table 12-2 summarizes the LSAs that are allowed in each area.

Table 12-2. LSA Types Allowed in Each Area

Area Type LSA 1 and 2 LSA 3 and 4 LSA 5 LSA 7

Backbone area (Area 0) Yes Yes Yes No
Stub area Yes Yes No No
Totally stubby area Yes No No No
Not-so-stubby area Yes Yes No Yes
Nonbackbone, nonstub area Yes Yes Yes No

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 55

LECTURE NO. 10
24 Dec 2008
FRAME RELAY (HUB-N-SPOKE TOPOLOGY)
(USING DYNAMIC MAPPING / INVERSE ARP)

Figure-10a
(Note: Lab results are produced using GNS3 simulator)

CONFIGURATION ON FRAME RELAY SWITCH

(SERVICE PROVIDER SIDE)
FRS(config)# frame-relay switching

NOTE: Here we are using a router instead of a frame relay

switch; therefore, the above command is used to convert
a router into a frame relay switch.

SERIAL1/0 INTERFACE

FRS(config)# interface serial 1/0

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay intf-type dce Serial interface of FRS
FRS(config-if)# frame-relay lmi-type ansi
FRS(config-if)# frame-relay route 102 interface serial 1/1 201
FRS(config-if)# frame-relay route 103 interface serial 1/2 301
FRS(config-if)# exit
Serial interface of FRS

SERIAL1/1 INTERFACE

FRS(config)# interface serial 1/1

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay lmi-type ansi Serial interface of FRS
FRS(config-if)# frame-relay intf-type dce
FRS(config-if)# frame-relay route 201 interface serial 1/0 102
FRS(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 56

SERIAL1/2 INTERFACE

FRS(config)# interface serial 1/2

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay lmi-type ansi Serial interface of FRS
FRS(config-if)# frame-relay intf-type dce
FRS(config-if)# frame-relay route 301 interface serial 1/0 103
FRS(config-if)# exit

CONFIGURATION OF R1 ROUTER (CLIENT SIDE)

R1(config)# interface serial 1/0
R1(config-if)# no shutdown
R1(config-if)# ip address 1.1.1.1 255.0.0.0
R1(config-if)# encapsulation frame-relay
R1(config-if)# frame-relay lmi-type ansi
R1(config-if)# exit

CONFIGURATION OF R2 ROUTER (CLIENT SIDE)

R2(config)# interface serial 1/1
R2(config-if)# no shutdown
R2(config-if)# ip address 1.1.1.2 255.0.0.0
R2(config-if)# encapsulation frame-relay
R2(config-if)# frame-relay lmi-type ansi
R2(config-if)# exit

CONFIGURATION OF R3 ROUTER (CLIENT SIDE)

R3(config)# interface serial 1/2
R3(config-if)# no shutdown
R3(config-if)# ip address 1.1.1.3 255.0.0.0
R3(config-if)# encapsulation frame-relay
R3(config-if)# frame-relay lmi-type ansi
R3(config-if)# exit

CHECKING FRAME-RELAY MAPPING

R1# show frame-relay map

R2# show frame-relay map

R3# show frame-relay map

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 57

R1# show frame-relay lmi interface serial 1/0

R1# ping 1.1.1.3

R1# ping 1.1.1.2

R1# show frame-relay pvc

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 58

FRAME RELAY
(USING STATIC MAPPING – RECOMMENDED)

CONFIGURATION ON FRAME RELAY SWITCH

(SERVICE PROVIDER SIDE)
Frame-relay switch configuration is same as defined above in dynamic method.

CONFIGURATION ON R1 ROUTER (CLIENT SIDE)

R1(config)# interface serial 1/0
R1(config-if)# no shutdown
R1(config-if)# encapsulation frame-relay
R1(config-if)# frame-relay lmi-type ansi
R1(config-if)# no frame-relay inverse-arp
R1(config-if)# ip address 1.1.1.1 255.0.0.0
R1(config-if)# frame-relay map ip 1.1.1.2 102
R1(config-if)# frame-relay map ip 1.1.1.3 103
R1(config-if)# exit

CONFIGURATION OF R2 ROUTER (CLIENT SIDE)

R2(config)# interface serial 1/1
R2(config-if)# no shutdown
R2(config-if)# encapsulation frame-relay
R2(config-if)# frame-relay lmi-type ansi
R2(config-if)# no frame-relay inverse-arp
R2(config-if)# ip address 1.1.1.2 255.0.0.0
R2(config-if)# frame-relay map ip 1.1.1.1 201
R2(config-if)# exit

CONFIGURATION OF R3 ROUTER (CLIENT SIDE)

R3(config)# interface serial 1/2
R3(config-if)# no shutdown
R3(config-if)# encapsulation frame-relay
R3(config-if)# frame-relay lmi-type ansi
R3(config-if)# no frame-relay inverse-arp
R3(config-if)# ip address 1.1.1.3 255.0.0.0
R3(config-if)# frame-relay map ip 1.1.1.1 301
R3(config-if)# exit

CHECKING FRAME-RELAY MAPPING

R1# show frame-relay map

R2# show frame-relay map

R3# show frame-relay map

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 59

R1# show frame-relay lmi interface serial 1/0

R1# ping 1.1.1.3

R1# ping 1.1.1.2

R1# show frame-relay pvc

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 60

FRAME RELAY
(SUB-INTERFACES)

POINT-TO-MULTIPOINT SUB-INTERFACE WITH STATIC MAPPING

Figure-10b
(Note: Lab results are produced using GNS3 simulator)

CONFIGURATION ON FRAME RELAY SWITCH

(SERVICE PROVIDER SIDE)
FRS(config)# frame-relay switching

NOTE: Here, we are using a router instead of a frame relay

switch; therefore, the above command is used to convert
a router into a frame relay switch.

SERIAL1/0 INTERFACE

FRS(config)# interface serial 1/0

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay intf-type dce Serial interface of FRS
FRS(config-if)# frame-relay lmi-type ansi
FRS(config-if)# frame-relay route 102 interface serial 1/1 201
FRS(config-if)# frame-relay route 103 interface serial 1/2 301
FRS(config-if)# exit
Serial interface of FRS

SERIAL1/1 INTERFACE

FRS(config)# interface serial 1/1

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay lmi-type ansi Serial interface of FRS
FRS(config-if)# frame-relay intf-type dce
FRS(config-if)# frame-relay route 201 interface serial 1/0 102
FRS(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 61

SERIAL1/2 INTERFACE

FRS(config)# interface serial 1/2

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay lmi-type ansi Serial interface of FRS
FRS(config-if)# frame-relay intf-type dce
FRS(config-if)# frame-relay route 301 interface serial 1/0 103
FRS(config-if)# exit

CONFIGURATION ON R1 ROUTER (CLIENT SIDE)

R1(config)# interface serial 1/0
R1(config-if)# no shutdown
R1(config-if)# no ip address
R1(config-if)# encapsulation frame-relay
R1(config-if)# frame-relay lmi-type ansi
R1(config-if)# no frame-relay inverse-arp
R1(config-if)# exit

R1(config)# interface serial 1/0.123 multipoint

R1(config-subif)# ip address 1.1.1.1 255.0.0.0
R1(config-subif)# no shutdown
R1(config-subif)# frame-relay map ip 1.1.1.2 102
R1(config-subif)# frame-relay map ip 1.1.1.3 103
R1(config-subif)# no frame-relay inverse-arp
R1(config-subif)# exit
R1(config)#

CONFIGURATION OF R2 ROUTER (CLIENT SIDE)

R2(config)# interface serial 1/1
R2(config-if)# no shutdown
R2(config-if)# encapsulation frame-relay
R2(config-if)# frame-relay lmi-type ansi
R2(config-if)# no frame-relay inverse-arp
R2(config-if)# ip address 1.1.1.2 255.0.0.0
R2(config-if)# frame-relay map ip 1.1.1.1 201
R2(config-if)# exit
R2(config)#

CONFIGURATION OF R3 ROUTER (CLIENT SIDE)

R3(config)# interface serial 1/2
R3(config-if)# no shutdown
R3(config-if)# encapsulation frame-relay
R3(config-if)# frame-relay lmi-type ansi
R3(config-if)# no frame-relay inverse-arp
R3(config-if)# ip address 2.1.1.2 255.0.0.0
R3(config-if)# frame-relay map ip 1.1.1.1 301
R3(config-if)# exit

CHECKING FRAME-RELAY MAPPING

R1# show frame-relay map

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 62

R2# show frame-relay map

R3# show frame-relay map

R1# show frame-relay lmi interface serial 1/0

R1# ping 1.1.1.2

R1# ping 1.1.1.3

R1# show frame-relay pvc

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 63

POINT-TO-POINT SUB-INTERFACE WITH STATIC MAPPING

Figure-10c
(Note: Lab results are produced using GNS3 simulator)

CONFIGURATION ON FRAME RELAY SWITCH

(SERVICE PROVIDER SIDE)
FRS(config)# frame-relay switching

NOTE: Here, we are using a router instead of a frame relay

switch; therefore, the above command is used to convert
a router into a frame relay switch.

SERIAL1/0 INTERFACE

FRS(config)# interface serial 1/0

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay intf-type dce Serial interface of FRS
FRS(config-if)# frame-relay lmi-type ansi
FRS(config-if)# frame-relay route 102 interface serial 1/2 201
FRS(config-if)# frame-relay route 103 interface serial 1/3 301
FRS(config-if)# exit
Serial interface of FRS

SERIAL1/1 INTERFACE

FRS(config)# interface serial 1/2

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay lmi-type ansi Serial interface of FRS
FRS(config-if)# frame-relay intf-type dce
FRS(config-if)# frame-relay route 201 interface serial 1/0 102
FRS(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 64

SERIAL1/2 INTERFACE

FRS(config)# interface serial 1/3

FRS(config-if)# no ip address
FRS(config-if)# no shutdown
FRS(config-if)# clock rate 56000
FRS(config-if)# encapsulation frame-relay
FRS(config-if)# frame-relay lmi-type ansi Serial interface of FRS
FRS(config-if)# frame-relay intf-type dce
FRS(config-if)# frame-relay route 301 interface serial 1/0 103
FRS(config-if)# exit

CONFIGURATION ON R1 ROUTER (CLIENT SIDE)

R1(config)# interface serial 1/0
R1(config-if)# no shutdown
R1(config-if)# no ip address
R1(config-if)# clock rate 56000
R1(config-if)# encapsulation frame-relay
R1(config-if)# frame-relay lmi-type ansi
R1(config-if)# no frame-relay inverse-arp
R1(config-if)# exit

R1(config)# interface serial 1/0.12 point-to-point

R1(config-subif)# ip address 1.1.1.1 255.0.0.0
R1(config-subif)# no shutdown
R1(config-subif)# no frame-relay inverse-arp
R1(config-subif)# frame-relay interface-dlci 102
R1(config-fr-dlci)# exit
R1(config-subif)# exit
R1(config)#

R1(config)# interface serial 1/0.13 point-to-point

R1(config-subif)# ip address 2.1.1.1 255.0.0.0
R1(config-subif)# no shutdown
R1(config-subif)# no frame-relay inverse-arp
R1(config-subif)# frame-relay interface-dlci 103
R1(config-fr-dlci)# exit
R1(config-subif)# exit
R1(config)#

CONFIGURATION OF R2 ROUTER (CLIENT SIDE)

R2(config)# interface serial 1/2
R2(config-if)# no shutdown
R2(config-if)# encapsulation frame-relay
R2(config-if)# frame-relay lmi-type ansi
R2(config-if)# no frame-relay inverse-arp
R2(config-if)# ip address 1.1.1.2 255.0.0.0
R2(config-if)# frame-relay interface-dlci 201
R2(config-fr-dlci)# exit
R2(config-if)# exit
R2(config)#

CONFIGURATION OF R3 ROUTER (CLIENT SIDE)

R3(config)# interface serial 1/3
R3(config-if)# no shutdown
R3(config-if)# encapsulation frame-relay
R3(config-if)# frame-relay lmi-type ansi
R3(config-if)# no frame-relay inverse-arp
R3(config-if)# ip address 2.1.1.2 255.0.0.0
R3(config-if)# frame-relay interface-dlci 301
R3(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 65

ROUTING TABLE OF ROUTER-R1, R2 & R3

(BEFORE RUNNING RIP)

R1# show ip route

R2# show ip route

R3# show ip route

RUNNING RIP ON ROUTER-R1

R1(config)# router rip
R1(config-router)# network 1.0.0.0
R1(config-router)# network 2.0.0.0
R1(config-router)# exit
R1(config)#

RUNNING RIP ON ROUTER-R2

R2(config)# router rip
R2(config-router)# network 1.0.0.0
R2(config-router)# exit
R2(config)#

RUNNING RIP ON ROUTER-R3

R3(config)# router rip
R3(config-router)# network 2.0.0.0
R3(config-router)# exit
R3(config)#

ROUTING TABLE OF ROUTER-R1, R2 & R3

(AFTER RUNNING RIP)

R1# show ip route

R2# show ip route

R3# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 66

CHECKING FRAME-RELAY MAPPING

R1# show frame-relay map

R2# show frame-relay map

R3# show frame-relay map

VERFYING FRAME-RELAY NETWORK USING PING COMMAND

R2# ping 1.1.1.1

R2# ping 2.1.1.1

R2# ping 2.1.1.2

R3# ping 2.1.1.1

R3# ping 1.1.1.1

R3# ping 1.1.1.2

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 67

LECTURE NO. 11
BEHAVIOR OF OSFF WITH FRAME RELAY

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 68

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 69

LECTURE NO. 12
29 Dec 2008
OSPF STATES
OSPF neighbors go through states before they can begin exchanging LSAs. You can
examine the state of an OSPF neighbor with the help of following command:-

A# show ip ospf neighbor

DOWN STATE
This state occurs when configuration is mismatched on both sides e.g. If STUB is
configured on one side only. STUB is one of the fields in HELLO packet. HELLO
packet contains following information/fields:-

ƒ The Router-ID of the originating router.

ƒ The Area-ID of the originating router intrface.
ƒ The address mask of the originating interface.
ƒ Authentication type and authentication information for the originating
interface.
ƒ The Hello Interval of the originating interface.
ƒ The Router Dead Interval of the originating interface.
ƒ The router priority.
ƒ The Designated Router (DR) and Backup Designated Router (BDR)
information.
ƒ Five flags for options.
ƒ The Router-ID of the originating router's neighbors.

This is the initial state of the neighbor, which also indicates that no hellos
were heard from this neighbor within the last dead time interval. For details,
please see Stub Area Lab (Lecture-15).

INIT OR ONE WAY STATE

One router (A) sent Hello packet to other router (B) and the information is
matched on the other router (B). In response other router (B) sent
acknowledgment, but it is in the pipeline.

This state indicates that a router has seen its own Ruter-ID in the neighbor
field of the HELLO packet that it received from the neighbor. It also means that
bidirectional conversation was established and that DR and BDR election can
occur.

TWO WAY STATE

Router-A sent HELLO Packet and Router-B sent acknowledgment, afterthat, Router-B
sent Hello packet and Router-A sent acknowledgment in response. Then neighbor
table is completed and DR/BDR Election process begins.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 70

Figure-12a

When an OSPF interface first becomes active, it begins to send hello

packets. When two routers receive each other's hello, they place the
neighbor in INIT STATUS. When a neighbor is in init status, it places its
own Router-ID into the hello packet. When a router receives one of the new
hellos with the Router-ID of its neighbor, it places the neighbor in a new
state of 2-WAY. The 2-Way state ensures that here is a two-way communication
between the routers. The routers must be in this state before they can
negotiate a DR/BDR and exchange LSAs.

After the routers have achieved the 2-Way state, OSPF enters into its final
states:

EXSTART (MASTER/SLAVE)
A simple meaning of this state is "who will initialize the communication first".
At this state, another election for the selection of Master and Slave Router
begins. The neighbor with the highest IP address becomes the Master and other
becomes the Slave, to exchange LSA.

Figure-12b

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 71

EXCHANGE (LSA REQUEST)

The router sends its database description packets to neighbors in the exchange
state. The database description packets describe the entire link state database.
The link-state database is synchronized after this phase. After synchronization,
the router enters one of two final states.

Every network in the routing table of a router has a correspinding sequence

number. At this state, a router sends the sequence numbers to the neighbor
router. In response, as acknowledgment, the neighbor router also sends its
sequence numbers.

Figure-12c
LOADING
The router also sends link state request packets to all neighbors that are in
the loading state. The loading phase requests that more recent LSAs be sent. At
this state the database table is completed.

Figure-12d
FULL
At this state, SPF algorithm is applied and best path is calculated. Neighbors
in this state are fully adjacent and routing table of neighbors are completed.

A# show ip ospf adj

A# show ip ospf neighbor

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 72

LECTURE NO. 13
31 Dec 2008
ROUTES

Every router must have a route to know where to send traffic. I compare this to the
post office's predetermined ways to route your postal mail to its destination. When
a router receives a packet from the LAN or the WAN, it must know the "next hop"
where it needs to deliver that packet. That next hop is the IP address of the
destination router. The router learns the next hop for packets by one of two
methods:

STATIC ROUTES
Static routing is not really a protocol, simply the process of manually entering
routes into the routing table via a configuration file that is loaded when the
routing device starts up. As an alternative, these routes can be entered by a
network administrator who configures the routes. Since these routes don't change
after they are configured (unless a human changes them) they are called 'static'
routes.

Static routing is the simplest form of routing, but it is a manual process and
does not work well when the routing information has to be changed frequently or
needs to be configured on a large number of routing devices (routers). Static
routing also does not handle outages or down connections well because any route
that is configured manually must be reconfigured manually to fix or repair any
lost connectivity.

ADVANTAGES OF STATIC ROUTES:

ƒ Easy to configure
ƒ No routing protocol overhead

DISADVANTAGES OF STATIC ROUTES:

ƒ Network changes require manual reconfiguration

ƒ Network outages cannot be automatically routed around

DYNAMIC ROUTES
Dynamic routing protocols are software applications that dynamically discover
network destinations and how to get to them.

A router will 'learn' routes to all directly connected networks first. It will
then learn routes from other routers that run the same routing protocol. The
router will then sort through it's list of routes and select one or more 'best'
routes for each network destination it knows or has learned.

Dynamic protocols will then distribute this 'best route' information to other
routers running the same routing protocol, thereby extending the information on
what networks exist and can be reached. This gives dynamic routing protocols the
ability to adapt to logical network topology changes, equipment failures or
network outages 'on the fly'

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 73

ROUTES - LAB

Figure-13a
(Note: Lab results are produced using Packet Tracer 5.0 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 74

RUNNING OSPF ON ROUTER-A, B & C

A(config)# router ospf 100
A(config-router)# network 1.0.0.0 0.255.255.255 area 0
A(config-router)# network 200.100.50.0 0.0.0.255 area 0

B(config)# router ospf 100

B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 2.0.0.0 0.255.255.255 area 1
B(config-router)# network 200.100.100.0 0.0.0.255 area 0

C(config)# router ospf 100

C(config-router)# network 2.0.0.0 0.255.255.255 area 1
C(config-router)# network 200.100.150.0 0.0.0.255 area 1

ROUTING TABLE OF ROUTER-A

(AFTER RUNNING OSPF)

A# show ip route

CHECKING, WHICH ROUTER IS ABR/ASBR?

A# show ip ospf

NOTE: Its not an area border router.

C# show ip ospf

NOTE: Its not an area border router.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 75

B# show ip ospf

CREATING 4 STATIC ROUTES ON ROUTER-C

C(config)# ip route 192.1.17.0 255.255.255.0 null 0
C(config)# ip route 192.1.18.0 255.255.255.0 null 0
C(config)# ip route 192.1.19.0 255.255.255.0 null 0
C(config)# ip route 192.1.20.0 255.255.255.0 null 0

PERFORMING REDISTRIBUTION FOR STATIC ROUTES

C(config)# router ospf 100
C(config-router)# redistribute static subnets

NOTE: The above command shall redistribute all static routes

including subnetted routes.

ROUTING TABLE OF ROUTER-A & C

(AFTER DEFINING STATIC ROUTES AND PERFORMING REDISTRIBUTION)

A# show ip route

NOTE: Static routes of Router-C have been reached as OE2 (external

routes) on Router-A

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 76

CREATING 4 STATIC ROUTES ON ROUTER-B

B(config)# ip route 192.1.65.0 255.255.255.0 null 0
B(config)# ip route 192.1.66.0 255.255.255.0 null 0
B(config)# ip route 192.1.67.0 255.255.255.0 null 0
B(config)# ip route 192.1.68.0 255.255.255.0 null 0

PERFORMING REDISTRIBUTION FOR STATIC ROUTES

B(config)# router ospf 100
B(config-router)# redistribute static subnets

ROUTING TABLE OF ROUTER-A, B & C

(AFTER DEFINING STATIC ROUTES AND PERFORMING REDISTRIBUTION)

A# show ip route

B# show ip route

C# show ip route

NOTE: Static routes of Router-B have been reached as OE2 (external

routes) on Router-B & C.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 77

LECTURE NO. 14
02 Jan 2009
VIRTUAL LINKS
All areas in an Open Shortest Path First (OSPF) autonomous system must be
physically connected to the backbone area (Area 0). In some cases, where this is
not possible, you can use a virtual link to connect to the backbone through a non-
backbone area. You can also use virtual links to connect two parts of a partitioned
backbone through a non-backbone area. The area through which you configure the
virtual link, known as a transit area, must have full routing information. The
transit area cannot be a stub area.

Figure - 14a
(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

A(config)# interface loopback 0

A(config-if)# ip address 11.1.1.1 255.0.0.0

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

B(config)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.0.0.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 78

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

C(config)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.0.0.0

RUNNING OSPF ON ROUTER-A, B & C

A(config)# router ospf 125
A(config-router)# network 200.100.50.0 0.0.0.255 area 0
A(config-router)# network 1.0.0.0 0.255.255.255 area 1

B(config)# router ospf 125

B(config-router)# network 1.0.0.0 0.255.255.255 area 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 2

C(config)# router ospf 125

C(config-router)# network 200.100.150.0 0.0.0.255 area 3
C(config-router)# network 2.0.0.0 0.255.255.255 area 2

NOTE: Do not run OSPF on network 200.100.100.0

HARD COADING ROUTER-IDS OF ROUTER-A, B & C

A(config)# router ospf 125
A(config-router)# router-id 11.1.1.1

B(config)# router ospf 125

B(config-router)# router-id 22.2.2.2

C(config)# router ospf 125

C(config-router)# router-id 33.3.3.3

ROUTING TABLE OF ROUTER-A, B & C

(AFTER RUNNING OSPF)

A# show ip route

B# show ip route

C# show ip route

NOTE: Routing table of Router-A, B & C is not converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 79

WHICH ROUTER IS ABR/ASBR?

(BEFORE CREATING VIRTUAL LINKS)

A# show ip ospf

It is an ABR

B# show ip ospf

It is not an ABR/ASBR

C# show ip ospf

It is not an ABR/ASBR

CREATING VIRTUAL LINK BETWEEN ROUTER-A AND B

Figure-14b
(Area-0 will virtually cover Area-1 and will get access to Router-B)

CONDITIONS:

a. One router must be part of Area-0.

b. There should be a common area.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 80

According to figure-14a:

ROUTER AREA
A Area-0 + Area-1
B Area-1 + Area-2
C Area-2 + Area-3

According to above table:

ROUTER AREA-0 Common Area

A+B Yes Yes (Area-1)
A+C Yes No
B+C No Yes (Area-2)

NOTE: According to above information, we notice that Router-A and

Router-B meet both conditions. Therefore, we can create a
VIRTUAL LINK between Router-A and B.

A(config)# router ospf 125

A(config-router)# area 1 virtual-link 22.2.2.2 Router ID of Router-B

B(config)# router ospf 125

B(config-router)# area 1 virtual-link 11.1.1.1 Router ID of Router-A

NOTE: After creating virtual-link, you'll notice following:

ƒ Network 200.100.50.0 has changed its status from OIA to O on

Router-B.
ƒ Network 2.0.0.0 has been reached on Router-A.
ƒ Router-B has become ABR.

B# show ip route

A# show ip route

B# show ip ospf

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 81

CREATING VIRTUAL LINK BETWEEN ROUTER-B AND C

Figure-14c
(Area-0 will virtually cover Area-2 and will get access to Router-C)

CONDITIONS:

a. One router must be part of Area-0.

b. There should be a common area.

In figure-14b:

ROUTER AREA
B Area-0 + Area-2
C Area-2 + Area-3

According to above table:

ROUTER AREA-0 Common Area

B+C Yes Yes (Area-2)

NOTE: According to above information, we notice thon Router-B and

Router-C meets both conditions. Therefore, we can create a
VIRTUAL LINK between Router-B and Router-C.

B(config)# router ospf 125

B(config-router)# area 2 virtual-link 33.3.3.3 Router ID of Router-C

C(config)# router ospf 125

C(config-router)# area 2 virtual-link 22.2.2.2 Router ID of Router-B

NOTE: After creating virtual-link, you'll notice following:

ƒ Network 200.100.150.0 has been reached on Router-A and

Router-B.
ƒ Network 200.100.50.0 and Network 1.0.0.0 has been reached on
Router-C.
ƒ Routing tables of Router-A, B & C have been converged.
Network 200.100.100.0 has not participated in this activity,
so it is not included in the routing tables of Router-A, B &
C.
ƒ All Routers including Router-C have become ABR.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 82

A# show ip route

B# show ip route

C# show ip route

C# show ip ospf

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 83

AUTHENTICATION IN OSPF

Figure-14d
(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/1
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/1
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

RUNNING OSPF ON ROUTER-A, & B

A(config)# router ospf 100
A(config-router)# network 1.0.0.0 0.255.255.255 area 0
A(config-router)# network 200.100.50.0 0.0.0.255 area 1

B(config)# router ospf 100

B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 2

ROUTING TABLE OF ROUTER-A & B

(AFTER RUNNING OSPF)

A# show ip route

B# show ip route

A# show ip ospf neighbor

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 84

PERFORMING AUTHENTICATION OF AREA 0 ON ROUTER-A

A(config)# router ospf 100
A(config-router)# area 0 authentication
A(config-router)# exit
A(config)# interface serial 1/1
A(config-router)# ip ospf authentication-key hello
A(config-router)#

A# show ip ospf neighbor

NOTE: After performing authentication on Router-A, you’ll notice that

neighbor relationship of 1.0.0.1 with 1.0.0.2 has been
demolished.

A# show ip route

B# show ip route

PERFORMING AUTHENTICATION OF AREA 0 ON ROUTER-B

B(config)# router ospf 100
B(config-router)# area 0 authentication
B(config-router)# exit
B(config)# interface serial 1/1
B(config-router)# ip ospf authentication-key hello
B(config-router)#

A# show ip ospf neighbor

A# show ip route

B# show ip route

NOTE: After performing authentication on Router-B, you’ll notice that

neighbor relationship of 1.0.0.1 with 1.0.0.2 has been formed
and routing tables of Router-A & Router-B have been converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 85

LECTURE NO. 15
05 Jan 2009
ROUTE SUMMARIZATION

With route summarization, or aggregation, in a hierarchical routing infrastructure,

one route in a routing table represents many routes. A routing table entry for the
highest level (the network) is also the route used for subnets and sub-subnets. In
contrast, in a flat routing infrastructure, the routing table on every router in
the network contains an entry for each network segment. When you use flat routing,
the network IDs have no network/subnet structure and cannot be summarized. RIP-
based Internet Packet Exchange (IPX) internetworks use flat network addressing and
have a flat routing infrastructure.

Using route summarization, you can contain topology changes occurring in one area
of the network within that area. Route summarization simplifies routing tables and
reduces the exchange of routing information, but it requires more planning than
does a flat routing infrastructure.
To support route summarization, your IP addressing scheme must meet the following
requirements:

• Classless routing protocols (those including subnet mask or prefix length

information along with the IP address) must be used.
• All IP addresses used in route summarization must share identical high-order
bits.
• The length of the prefix can be any number of bits up to 32 (for IPv4).

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 86

STUB AREA
No external routes are advertised into a stub area, nor will they generate external
LSA type 5s. A backbone area will advertise a single default route to a stub area
or a network summary LSA for the destination 0.0.0.0. Some other restrictions on
stub areas apply:

ƒ Virtual links cannot be configured across stub areas.

ƒ Adjacencies will not be established with any other router not configured
as a stub, except for the Area Border Router.
ƒ No router within a stub area can be an ASBR because no external routes or
LSA Type 5 can be advertised out of a stub area. In short, stub areas
cannot perform redistribution.
ƒ LSA Types 4 and 5 (OE2) are blocked into the area. Only LSA Types 1, 2,
and 3 are flooded into the area.

Figure-15a
(Note: Lab results are produced using Packet Tracer 5.0 & GNS3 simulators)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 87

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

RUNNING OSPF ON ROUTER-A, B AND C

A(config)# router ospf 222
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# network 200.100.50.0 0.0.0.255 area 1

B(config)# router ospf 222

B(config-router)# network 1.0.0.0 0.255.255.255 area 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 1

C(config)# router ospf 222

C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 200.100.150.0 0.0.0.255 area 2

NOTE: Routing tables of Router-A, B & C have been converged.

ROUTING TABLE OF ROUTER-A, B AND C

A# show ip route

B# show ip route

C# show ip route

WHICH ROUTER IS ABR AND ASBR?

A# show ip ospf

NOTE: This router is not an ABR and nor ASBR.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 88

B# show ip ospf

C# show ip ospf

DEFINING 4 STATIC ROUTES ON ROUTER-C

C(config)# ip route 192.1.65.0 255.255.255.0 null 0
C(config)# ip route 192.1.66.0 255.255.255.0 null 0
C(config)# ip route 192.1.67.0 255.255.255.0 null 0
C(config)# ip route 192.1.68.0 255.255.255.0 null 0

PERFORMING REDISTRIBUTION ON ROUTER-C

C(config)# router ospf 222
C(config-router)# redistribute static subnets

C# show ip ospf

NOTE: After redistributing static routes of Router-C into OSPF, we

notice that Router-C has becomes ABR+ASBR.

ROUTING TABLE OF ROUTER-A, B AND C

(AFTER PERFORMING REDISTRIBUTION ON ROUTER-C)

A# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 89

B# show ip route

C# show ip route

NOTE: Static routes of Router-C have been reached on Router-B and

Router-C.

CONFIGURING STUB AREA ON ROUTER-B

B(config)# router ospf 222
B(config-router)# area 1 stub

B# show ip ospf neighbor

NOTE: Due to the configuration of stub area on one side only, the
configuration have been mismatched, causes the router to go on
down state. Please also see DOWN STATE in Lecture No. 12.

A# show ip route

B# debug ip ospf events

B# debug ip ospf hello

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 90

CONFIGURING STUB AREA ON ROUTER-A

A(config)# router ospf 222

A(config-router)# area 1 stub

VERIFYING STUB AREA

A# show ip route

NOTE: A default route is injected, instead of external routes

(OE2).

B# show ip ospf neighbor

NOTE: After configuring stub on both sides, we notice that the

OSPF state of neighbor 200.100.50.1 has changed to FULL.

REMOVING STUB AREA FROM ROUTER-A & B

A(config)# router ospf 222
A(config-router)# no area 1 stub
A(config-router)# exit

B(config)# router ospf 222

B(config-router)# no area 1 stub
B(config-router)# exit

TOTALLY STUB AREA

Neither external nor internal routes are advertised into this area. LSA types 3, 4,
and 5 (OIA & OE2) are blocked into the area, except for a single default route
advertised as a LSA type 3. The router will use the default route to reach any
destination outside the area. In this type, there is no need to configure totally
stub on all routers. Just configure it on ABR.

CREATING TOTALLY STUB AREA ON ROUTER-B (ABR)

B(config)# router ospf 222
B(config-router)# area 1 stub no-summary

NOTE: LSAs which are generated by ABR are called Summary-LSA,

therefore, in above command, NO-SUMMARY represents summary LSA,
i.e LSA-3/4.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 91

A# show ip route

NOTE: LSAs 3, 4 & 5 (OIA & OE2) have been blocked.

HOW TO REMOVE TOTALLY SUB AREA?

B(config)# router ospf 222
B(config-router)# no area 1 stub no-summary
B(config-router)# no area 1 stub

NOTE: The above command only removes NO-SUMMARY

portion from this command. AREA 1 STUB
portion of above command converts Area 1
into STUB on Router-B and it causes
mismatch of information between Router-A
and Router-B. Therefore, when you apply
show ip ospf neighbor command on Router-B,
it cannot find its neighbor 200.100.50.1.

To resolve the issue, apply this command

and after applying both commands, check
running-config to verify that stub and no-
summary commands have been removed.

NOT-SO-STUBBY AREA (NSSA)

Sometimes, it is necessary to redistribute another routing protocol, such as RIP,
into a stub area. Because this violates the definition of stub area, a new area
type was needed. To remedy this, RFC 1587 defines not-so-stubby areas (NSSA). An
NSSA allows external routes to be advertised into the OSPF domain while retaining
the other characteristics of a stub area. When external routes are redistributed
into a router in an NSSA area, the router originates LSA Type 7s to advertise the
new external destination(s) to routers within the NSSA area. The LSA Type 7s are
converted to LSA Type 5 when flooded into Area 0 by the ABR. No LSA type 5s will
exist in the NSSA area. All routers in the area must be configured NSSA.

Figure-15b
(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 92

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

RUNNING OSPF ON ROUTER-A, B AND C

A(config)# router ospf 222
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# network 200.100.50.0 0.0.0.255 area 1

B(config)# router ospf 222

B(config-router)# network 1.0.0.0 0.255.255.255 area 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 1

C(config)# router ospf 222

C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 200.100.150.0 0.0.0.255 area 2

NOTE: Routing tables of Router-A, B & C have been converged.

DEFINING 4 STATIC ROUTES ON ROUTER-C

C(config)# ip route 192.1.65.0 255.255.255.0 null 0
C(config)# ip route 192.1.66.0 255.255.255.0 null 0
C(config)# ip route 192.1.67.0 255.255.255.0 null 0
C(config)# ip route 192.1.68.0 255.255.255.0 null 0

PERFORMING REDISTRIBUTION ON ROUTER-C

C(config)# router ospf 222
C(config-router)# redistribute static subnets

CREATING STATIC ROUTES ON ROUTER-A

A(config)# ip route 192.1.17.0 255.255.255.0 null 0
A(config)# ip route 192.1.18.0 255.255.255.0 null 0
A(config)# ip route 192.1.19.0 255.255.255.0 null 0
A(config)# ip route 192.1.20.0 255.255.255.0 null 0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 93

PERFORMING REDISTRIBUTION ON ROUTER-A

A(config)# router ospf 222
A(config-router)# redistribute static subnets

ROUTING TABLE OF ROUTER-A, B AND C

(AFTER CREATING STATIC ROUTES AND PERFORMING REDISTRIBUTION)

A# show ip route

B# show ip route

C# show ip route

CREATING NSSA ON AREA 1

A(config)# router ospf 222
A(config-router)# area 1 nssa

B(config)# router ospf 222

B(config-router)# area 1 nssa

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 94

ROUTING TABLE OF ROUTER-A, B AND C

(AFTER CREATING NSSA ON ROUTER-A)

A# show ip route

B# show ip route

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 95

LECTURE NO. 16
09 Jan 2009
METRIC, METRIC TYPE, ROUTE SUMMARIZATION
& ROUTER-ID

Figure-16a
(Note: Lab results are produced using Packet Tracer 5.0 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 96

ROUTING TABLE OF ROUTER-A, B & C

A# show ip route

B# show ip route

C# show ip route

RUNNING OSPF ON ROUTER-A, B AND C

A(config)# router ospf 222
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# network 200.100.50.0 0.0.0.255 area 1

B(config)# router ospf 222

B(config-router)# network 1.0.0.0 0.255.255.255 area 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 1

C(config)# router ospf 222

C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 200.100.150.0 0.0.0.255 area 2

ROUTING TABLE OF ROUTER-A, B AND C

A# show ip route

B# show ip route

C# show ip route

NOTE: Routing tables of Router-A, B & C have been converged.

DEFINING 4 STATIC ROUTES ON ROUTER-C

C(config)# ip route 192.1.65.0 255.255.255.0 null 0
C(config)# ip route 192.1.66.0 255.255.255.0 null 0
C(config)# ip route 192.1.67.0 255.255.255.0 null 0
C(config)# ip route 192.1.68.0 255.255.255.0 null 0

PERFORMING REDISTRIBUTION ON ROUTER-C

C(config)# router ospf 222
C(config-router)# redistribute static subnets

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 97

ROUTING TABLE OF ROUTER-A, B AND C

(AFTER PERFORMING REDISTRIBUTION ON ROUTER-C)

A# show ip route

B# show ip route

C# show ip route

NOTE: Static routes of Router-C have been reached as OE2 (External

Routes) on Router-A & B.

CHANGING METRIC VALUE OF STATIC ROUTES

C(config)# router ospf 222
C(config-router)# redistribute static metric 333

ROUTING TABLE OF ROUTER-A & B

(AFTER CHANING METRIC VALUE OF STATIC ROUTES)

A# show ip route

B# show ip route

NOTE: Metric value of static routes have been changed..

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 98

CHANGING METRIC TYPE OF STATIC ROUTES

C(config)# router ospf 222
C(config-router)# redistribute static subnets metric-type type-1

ROUTING TABLE OF ROUTER-A, and B

(AFTER CHANING METRIC VALUE)

A# show ip route

B# show ip route

CHANGING METRIC VALUE & TYPE

(USING SINGLE LINE COMMAND)

C(config)# router ospf 222

C(config-router)# redistribute static subnets metric 200 metric-type type-1

A# show ip route

NOTE: Cost of every link adds in the metric value of metric type-1
(OE-1). In this case, cost of serial link between Router-A and
B (cost=64) and between Router-B and C (cost=64) has been added
in the metric value.

B# show ip route

NOTE: In this case, cost of serial link between Router-A and B

(cost=64) has been added in the metric value.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 99

C(config)# router ospf 222

C(config-router)# redistribute static subnets metric 200 metric-type type-2

A# show ip route

B# show ip route

NOTE: Metric value of metric type-2 (OE-2) remains same/fix. It does

not carry the cost of links.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 100

ROUTE SUMMARIZATION

C(config)# router ospf 222

C(config-router)# summary-address 192.1.64.0 255.255.248.0

NOTE: 255.255.248.0 is subnet mask of 192.1.64.0/21 while

192.1.64.0/21 is the matching address of 192.1.65.0/24,
192.1.66.0/24, 192.1.67.0/24 and 192.1.68.0/24. For detail, see
below example.

NOTE: Route-summarization is a similar concept of supernatting and

the above command is normally used on ASBR.

ROUTING TABLE OF ROUTER-A

A# show ip route

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 101

ROUTER-ID
CHECKING ROUTER IDS
A# show ip ospf interface

B# show ip ospf interface

C# show ip ospf interface

CREATING LOOPBACK INTERFACE TO BECOME ROUTER-ID

A(config)# interface loopback 1
A(config-if)# ip address 11.1.1.1 255.0.0.0

CHECKING WHETHER ROUTER-ID HAS CHANGED OR NOT?

A# show ip ospf interface

NOTE: Router-ID has not changed.

RESETTING OSPF PROCESS

A# clear ip ospf process

A# show ip ospf interface

NOTE: Router-ID has still not changed.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 102

REMOVING OSPF FROM ROUTER-A

A(config)# no router ospf 222

RUNNING NEW OSPF ON ROUTER-A

A(config)# router ospf 222
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# network 200.100.50.0 0.0.0.255 area 1

CHECKING WHETHER ROUTER ID HAS CHANGED OR NOT

A# show ip ospf interface

NOTE: Router-ID has been changed.

ADVERTISING LOOPBACK (ROUTER-ID)

A(config)# router ospf 222
A(config-router)# network 11.1.1.1 0.0.0.0 area 1

ROUTING TABLE OF ROUTER-A, B & C

(AFTER ADVERTISING ROUTER-ID)

A# show ip route

B# show ip route

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 103

LECTURE NO. 17
12 Jan 2009
ROUTE MAPS
Route maps are used to control and modify routing information that is exchanged
between routing domains. Route maps consist of a list of match and set
configuration commands. The match commands specify match criteria for incoming
routes and the set commands specify the action taken if the match criteria are met.

Figure-17a

Route maps are used to define the conditions for redistributing routes from one
protocol to another, and within the BGP protocol (BGP peer to BGP peer).

LAB #1

Figure-17b
(Note: Lab results are produced using GNS3 simulator)

EXAMPLE #1

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface ethernet 2/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 104

RUNNING OSPF ON ROUTER-A AND B

A(config)# router ospf 222
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# network 200.100.50.0 0.0.0.255 area 3

B(config)# router ospf 222

B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 1

CREATING 15 STATIC ROUTES ON ROUTER-A

A(config)# ip route 192.1.1.0 255.255.255.0 null 0
A(config)# ip route 192.1.2.0 255.255.255.0 null 0
A(config)# ip route 192.1.3.0 255.255.255.0 null 0
A(config)# ip route 192.1.4.0 255.255.255.0 null 0
A(config)# ip route 192.1.5.0 255.255.255.0 null 0
A(config)# ip route 192.1.6.0 255.255.255.0 null 0
A(config)# ip route 192.1.7.0 255.255.255.0 null 0
A(config)# ip route 192.1.8.0 255.255.255.0 null 0
A(config)# ip route 192.1.9.0 255.255.255.0 null 0
A(config)# ip route 192.1.10.0 255.255.255.0 null 0
A(config)# ip route 192.1.11.0 255.255.255.0 null 0
A(config)# ip route 192.1.12.0 255.255.255.0 null 0
A(config)# ip route 192.1.13.0 255.255.255.0 null 0
A(config)# ip route 192.1.14.0 255.255.255.0 null 0
A(config)# ip route 192.1.15.0 255.255.255.0 null 0

DEFINING ACCESS LIST

(FOR ODD NUMBERS)
A(config)# access-list 5 permit 192.1.1.0 0.0.0.255
A(config)# access-list 5 permit 192.1.3.0 0.0.0.255
A(config)# access-list 5 permit 192.1.5.0 0.0.0.255
A(config)# access-list 5 permit 192.1.7.0 0.0.0.255
A(config)# access-list 5 permit 192.1.9.0 0.0.0.255
A(config)# access-list 5 permit 192.1.11.0 0.0.0.255
A(config)# access-list 5 permit 192.1.13.0 0.0.0.255
A(config)# access-list 5 permit 192.1.15.0 0.0.0.255

(FOR EVEN NUMBERS)

A(config)# access-list 6 permit 192.1.2.0 0.0.0.255
A(config)# access-list 6 permit 192.1.4.0 0.0.0.255
A(config)# access-list 6 permit 192.1.6.0 0.0.0.255
A(config)# access-list 6 permit 192.1.8.0 0.0.0.255
A(config)# access-list 6 permit 192.1.10.0 0.0.0.255
A(config)# access-list 6 permit 192.1.12.0 0.0.0.255
A(config)# access-list 6 permit 192.1.14.0 0.0.0.255

VIEWING/VERIFYING ACCESS LIST

A# show access-list

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 105

DEFINING ROUTE MAP FOR CHANGING METRIC-TYPE

(ROUTE-MAP FOR ODD NUMBERS)

A(config)# route-map pakistan permit 10

A(config-route-map)# match ip address 5
A(config-route-map)# set metric-type type-1

NOTE: pakistan= route-map name

10 = route map line number
5 = odd numbers access-list number
type-1 = OSPF type OE-1

(ROUTE-MAP FOR EVEN NUMBERS)

A(config)# route-map pakistan permit 11

A(config-route-map)# match ip address 6
A(config-route-map)# set metric-type type-2

HERE: pakistan= route-map name

11 = route map line number
6 = even numbers access-list number
type-2 = OSPF type OE-2

REDISTRIBUTION WITH ROUTE MAP

A(config)# router ospf 222
A(config-router)# redistribute static subnets route-map pakistan

ROUTING TABLE OF ROUTER-A AND B

A# show ip route

B# show ip route

NOTE: Odd number static routes of Router-A have been reached on

Router-B as OE1 and even number static routes have been reached
at as OE2.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 106

EXAMPLE #2
BASIC CONFIGURATION OF ROUTER-A, B &C
Same as in Example #1 (Lab No. 1).

RUNNING OSPF ON ROUTER-A AND B:

Same as in Example #1 (Lab No. 1).

CREATING 15 STATIC ROUTES ON ROUTER-A

Same as in Example #1 (Lab No. 1).

CALCULATING WILD CARD MASK

WCM for Odd Numbers WCM for Even Numbers

NOTE: Please note that in step no. 1 and step no. 2, wild card mask
(0.0.14.0) for odd and even numbers is same.

DEFINING ACCESS LIST USING WILD CARD MASK

(FOR ODD AND EVEN NUMBERS)

A(config)# access-list 5 permit 192.1.1.0 0.0.14.0

A(config)# access-list 6 permit 192.1.1.0 0.0.14.0

VIEWING ACCESS LIST

A# show access-list

DEFINING ROUTE MAP FOR CHANGING METRIC VALUE

(ROUTE-MAP FOR ODD NUMBERS)

A(config)# route-map lahore permit 15

A(config-route-map)# match ip address 5
A(config-route-map)# set metric 333

NOTE: lahore = route-map name

15 = route map line number
5 = odd numbers access-list number
333 = OSPF metric value

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 107

(ROUTE-MAP FOR EVEN NUMBERS)

A(config)# route-map lahore permit 16

A(config-route-map)# match ip address 6
A(config-route-map)# set metric 444

NOTE: lahore = route-map name

16 = route map line number
6 = odd numbers access-list number
444 = OSPF metric value

REDISTRIBUTION WITH ROUTE MAP

A(config)# router ospf 222
A(config-router)# redistribute static subnets route-map lahore

ROUTING TABLE OF ROUTER-A AND B

B# show ip route

NOTE: Metric value of odd number static routes has been changed to 333
and metric value of even number static routes has been changed
to 444.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 108

EXAMPLE #3
In this example we'll create 16 static routes on Router-A.

BASIC CONFIGURATION OF ROUTER-A, B & C

Same as in Example #1 & 2 (Lab No. 1).

RUNNING OSPF ON ROUTER-A AND B:

Same as in Example #1 & 2 (Lab No. 1).

CREATING 16 STATIC ROUTES ON ROUTER-A

A(config)# ip route 192.1.1.0 255.255.255.0 null 0
A(config)# ip route 192.1.2.0 255.255.255.0 null 0
A(config)# ip route 192.1.3.0 255.255.255.0 null 0
A(config)# ip route 192.1.4.0 255.255.255.0 null 0
A(config)# ip route 192.1.5.0 255.255.255.0 null 0
A(config)# ip route 192.1.6.0 255.255.255.0 null 0
A(config)# ip route 192.1.7.0 255.255.255.0 null 0
A(config)# ip route 192.1.8.0 255.255.255.0 null 0
A(config)# ip route 192.1.9.0 255.255.255.0 null 0
A(config)# ip route 192.1.10.0 255.255.255.0 null 0
A(config)# ip route 192.1.11.0 255.255.255.0 null 0
A(config)# ip route 192.1.12.0 255.255.255.0 null 0
A(config)# ip route 192.1.13.0 255.255.255.0 null 0
A(config)# ip route 192.1.14.0 255.255.255.0 null 0
A(config)# ip route 192.1.15.0 255.255.255.0 null 0
A(config)# ip route 192.1.16.0 255.255.255.0 null 0

CALCULATING WILD CARD MASK OF ODD NUMBERS

Same as in Example #2 (Lab No. 1).

CALCULATING WILD CARD MASK OF EVEN NUMBERS

Same as in Example #2 (Lab No. 1).

DEFINING ACCESS LIST USING WILD CARD MASK

(FOR ODD AND EVEN NUMBERS EXCLUDING STATIC ROUTE 16)

A(config)# access-list 5 permit 192.1.1.0 0.0.14.0

A(config)# access-list 6 permit 192.1.1.0 0.0.14.0

VIEWING ACCESS LIST

A# show access-list

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 109

DEFINING ROUTE MAP

(ROUTE-MAP FOR ODD NUMBERS)

A(config)# route-map shakeel permit 100

A(config-route-map)# match ip address 5
A(config-route-map)# set metric-type type-1

NOTE: shakeel= route-map name

100 = route map line number
5 = odd numbers access-list number
type-1 = OSPF metric type OE1

PERFORMING REDISTRIBUTION
A(config)# router ospf 222
A(config-router)# redistribute static subnets route-map shakeel

ROUTING TABLE OF ROUTE-B

B# show ip route

DEFINING ROUTE MAP

A(config)# route-map shakeel permit 101

NOTE: shakeel= route-map name

101 = route map line number

NOTE: Here, if you apply match and set command for even numbers,
Static Route 192.1.16.0 shall not reach on Router-B. Therefore,
there is no need of applying match and set command. It'll
automatically set OSPF Metric Type OE-2 of remaining static
routes (all even numbers including 192.1.16.0).

ROUTING TABLE OF ROUTE-B

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 110

LAB #2
STATIC ROUTES+OSPF DIFFERENT AREAS+ROUTE MAPS

Figure-17c
(Note: Lab results are produced using Packet GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface serial 1/1

A(config-if)# ip address 3.0.0.2 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 6 4000

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 111

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# no shutdown

C(config)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

CREATING LOOPBACK INTERFACES ON ROUTER-A, B & C

A(config)# interface loopback 0
A(config-if)# ip address 11.1.1.1 255.0.0.0

B(config)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.0.0.0

C(config)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.0.0.0

RUNNING OSPF ON ROUTER-A B AND C

A(config)# router ospf 5
A(config-router)# network 1.0.0.0 0.255.255.255 area 0
A(config-router)# network 3.0.0.0 0.255.255.255 area 0
A(config-router)# network 200.100.50.0 0.0.0.255 area 3
A(config-router)# network 11.1.1.1 0.0.0.0 area 0

B(config)# router ospf 5

B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 1
B(config-router)# network 22.2.2.2 0.0.0.0 area 0

C(config)# router ospf 5

C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 3.0.0.0 0.255.255.255 area 0
C(config-router)# network 200.100.150.0 0.0.0.255 area 2
C(config-router)# network 33.3.3.3 0.0.0.0 area 0

CONFIGURING ROUTER-IDS OF ROUTER-A B AND C

(HARD CODED METHOD)

A(config)# router ospf 5

A(config-router)# router-id 11.1.1.1

B(config)# router ospf 5

B(config-router)# router-id 22.2.2.2

C(config)# router ospf 5

C(config-router)# router-id 33.3.3.3

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 112

ROUTING TABLE OF ROUTER-A B AND C

A# show ip route

B# show ip route

C# show ip route

NOTE: Routing tables of Router-A, B & C have been completely

converged.

CREATING 4 STATIC ROUTES ON ROUTER-C

C(config)# ip route 192.168.17.0 255.255.255.0 null 0
C(config)# ip route 192.168.18.0 255.255.255.0 null 0
C(config)# ip route 192.168.19.0 255.255.255.0 null 0
C(config)# ip route 192.168.20.0 255.255.255.0 null 0

REDISTRIBUTION OF STATIC ROUTES INTO OSPS 5

C(config)# router ospf 5
C(config-router)# redistribute static subnets metric 100

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 113

ROUTING TABLE OF ROUTER-A B AND C

(AFTER PERFORMING REDISTRIBUTION OF STATIC ROUTES INTO OSPF)

A# show ip route

B# show ip route

C# show ip route

PERFORMING ROUTE SUMMARIZATION OF STATIC ROUTES

C(config)# router ospf 5
C(config-router)# summary-address 192.168.16.0 255.255.248.0

NOTE: 255.255.248.0 is subnet mask of 192.168.16.0/21 while

192.168.16.0/21 is the matching address of 192.168.17.0/24,
192.168.18.0/24, 192.168.19.0/24 and 192.168.20.0/24. For
detail, see below example.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 114

ROUTING TABLE OF ROUTER-A & B

(AFTER PERFORMING ROUTE SUMMARIZATION OF STATIC ROUTES)

A# show ip route

B# show ip route

REMOVING ROUTE SUMMARIZATION OF STATIC ROUTES

C(config)# router ospf 5
C(config-router)# no summary-address 192.168.16.0 255.255.248.0

DEFINING ACCESS LIST

C(config)# access-list 5 permit 192.168.17.0 0.0.0.255
C(config)# access-list 5 permit 192.168.18.0 0.0.0.255

C(config)# access-list 6 permit 192.168.19.0 0.0.0.255

C(config)# access-list 6 permit 192.168.20.0 0.0.0.255

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 115

DEFINING ROUTE MAP FOR CHANGING METRIC TYPE

(ROUTE-MAP FOR ROUTE NUMBERS 192.168.17.0 & 192.168.18.0)

C(config)# route-map lahore permit 11

C(config-route-map)# match ip address 5
C(config-route-map)# set metric-type type-2

NOTE: lahore = route-map name

11 = route map line number
5 = access-list number
type-2 = OSPF metric-type OE2

(ROUTE-MAP FOR ROUTE NUMBERS 192.168.19.0 & 192.168.20.0)

C(config)# route-map lahore permit 12

C(config-route-map)# match ip address 6
C(config-route-map)# set metric-type type-1

NOTE: lahore = route-map name

12 = route map line number
6 = odd numbers access-list number
type-1 = OSPF metric-type OE1

REDISTRIBUTION WITH ROUTE MAP

C(config)# router ospf 5
C(config-router)# redistribute static subnets route-map lahore

ROUTING TABLE OF ROUTER-A AND B

A# show ip route

B# show ip route

NOTE: Static routes 192.168.19.0 and 192.168.20.0 have been reached

at Router-A & B as OE1 and static routes 192.168.17.0 and
192.168.18.0 have been reached at Router-A & B as OE2 and

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 116

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 117

LECTURE NO. 18 & 19

14/16 JAN 2009
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS

Figure-18a
(Note: Lab results are produced using GNS3 simulator)

Question NO. 1 Set Router-IDs as given below:

Router-A 11.1.1.1
Router-B 22.2.2.2
Router-C 33.3.3.3
Router-D 44.4.4.4

Question NO. 2 Configure Routing Protocols as shown in Figure-18a.

Question NO. 3 Advertise Router-IDs (as mentioned in Question-1) in the

appropriate routing protocols.

Question NO. 4 Define 16 static routes on Router-D, starting from 192.1.32.0 .

Question NO. 5 Perform convergence of routing protocols so that you can ping
each and every IP address, available in the topology. Perform
clock-wise redistribution (if required).

Question NO. 6 Try to configure Area-1 as a stub area.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 118

Question NO. 7 Redistribute static routes of Router-D. Remember that odd

number routes must redistribute as OE-2 and even number routes
must redistribute as OE-1.

Question NO. 8 Define following 3 static routes on Router-B, redistribute

these routes in OSPF and perform route summarization.

192.1.97.0
192.1.98.0
192.1.99.0

Question NO. 9 Increase administrative distance value of IGRP-111, so that

network 200.100.200.0 can reach on Router-B as OSPF.

Question NO. 10 Perform authentication for Area-1.

SOLUTION

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface s 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface s 1/1

A(config-if)# ip address 4.0.0.2 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface f 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown
A(config-if)# exit

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface s 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface s 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface f 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown
B(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 119

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface s 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface s 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface f 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown
C(config-if)# exit

BASIC CONFIGURATION OF ROUTER-D

D(config)# interface s 1/0
D(config-if)# ip address 3.0.0.2 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface s 1/1

D(config-if)# ip address 4.0.0.1 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface f 0/0

D(config-if)# ip address 200.100.200.1 255.255.255.0
D(config-if)# no shutdown
D(config-if)# exit

ROUTING TABLE OF ROUTE-A, B, C & D

A# show ip route

B# show ip route

C# show ip route

D# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 120

ANSWER NO. 1

CREATING LOOPBACK INTERFACE ON ROUTER-A, B, C & D

(FOR SETTING UP ROUTER-ID)

A(config)# interface loopback 0

A(config-if)# ip address 11.1.1.1 255.255.255.255

B(config)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.255.255.255

C(config)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.255.255.255

D(config)# interface loopback 0

D(config-if)# ip address 44.4.4.4 255.255.255.255

NOTE: PLEASE ALSO SEE ANSWER NO. 2 & 3

ANSWER NO. 2 & 3

CONFIGURING ROUTING PROTOCOLS AND SETTING + ADVERTISING
ROUTER-ID
A(config)# router rip
A(config-router)# network 200.100.50.0
A(config-router)# exit
A(config)# router ospf 444
A(config-router)# router-id 11.1.1.1 Part of Question No. 1
A(config-router)# network 11.1.1.1 0.0.0.0 area 1 Part of Question No. 3
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# network 4.0.0.0 0.255.255.255 area 1

B(config)# router igrp 222

B(config-router)# network 2.0.0.0
B(config-router)# exit
B(config)# router ospf 444
B(config-router)# router-id 22.2.2.2 Part of Question No. 1
B(config-router)# network 22.2.2.2 0.0.0.0 area 0 Part of Question No. 3
B(config-router)# network 1.0.0.0 0.255.255.255 area 1
B(config-router)# network 200.100.100.0 0.0.0.255 area 0

C(config)# router igrp 222

C(config-router)# network 2.0.0.0
C(config-router)# network 3.0.0.0
C(config-router)# exit
C(config)# router ospf 555
C(config-router)# router-id 33.3.3.3 Part of Question No. 1
C(config-router)# network 33.3.3.3 0.0.0.0 area 0 Part of Question No. 3
C(config-router)# network 200.100.150.0 0.0.0.255 area 0

D(config)# router igrp 222

D(config-router)# network 3.0.0.0
D(config-router)# exit
D(config)# router ospf 444
D(config-router)# router-id 44.4.4.4 Part of Question No. 1
D(config-router)# network 44.4.4.4 0.0.0.0 area 2 Part of Question No. 3
D(config-router)# network 4.0.0.0 0.255.255.255 area 1
D(config-router)# network 200.100.200.0 0.0.0.255 area 2

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 121

VERIFYING ROUTER-IDS
A# show ip ospf interface

B# show ip ospf interface

C# show ip ospf interface

D# show ip ospf interface

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

MISSING NETWORKS ON ROUTER-A:

2.0.0.0 3.0.0.0
33.0.0.0 44.0.0.0
200.100.150.0 200.100.200.0

B# show ip route

MISSING NETWORKS ON ROUTER-B:

33.0.0.0 44.0.0.0
200.100.50.0 200.100.150.0
200.100.200.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 122

C# show ip route

MISSING NETWORKS ON ROUTER-C:

1.0.0.0 4.0.0.0
11.0.0.0 22.0.0.0
44.0.0.0 200.100.50.0
200.100.100.0 200.100.200.0

D# show ip route

MISSING NETWORKS ON ROUTER-D:

33.0.0.0 200.100.50.0
200.100.150.0

ANSWER NO. 4
DEFINING 16 STATIC ROUTES ON ROUTER-D
D(config)# ip route 192.1.32.0 255.255.255.0 null 0
D(config)# ip route 192.1.33.0 255.255.255.0 null 0
D(config)# ip route 192.1.34.0 255.255.255.0 null 0
D(config)# ip route 192.1.35.0 255.255.255.0 null 0
D(config)# ip route 192.1.36.0 255.255.255.0 null 0
D(config)# ip route 192.1.37.0 255.255.255.0 null 0
D(config)# ip route 192.1.38.0 255.255.255.0 null 0
D(config)# ip route 192.1.39.0 255.255.255.0 null 0
D(config)# ip route 192.1.40.0 255.255.255.0 null 0
D(config)# ip route 192.1.41.0 255.255.255.0 null 0
D(config)# ip route 192.1.42.0 255.255.255.0 null 0
D(config)# ip route 192.1.43.0 255.255.255.0 null 0
D(config)# ip route 192.1.44.0 255.255.255.0 null 0
D(config)# ip route 192.1.45.0 255.255.255.0 null 0
D(config)# ip route 192.1.46.0 255.255.255.0 null 0
D(config)# ip route 192.1.47.0 255.255.255.0 null 0

ANSWER NO. 5
CREATING VIRTUAL LINK BETWEEN ROUTER-B & D
B(config)# router ospf 444
B(config-router)# area 1 virtual-link 44.4.4.4

D(config)# router ospf 444

D(config-router)# area 1 virtual-link 22.2.2.2

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 123

B# show ip route

NOTE: Network 200.100.200.0 has been reached on Router-B as OIA.

MISSING NETWORKS ON ROUTER-B:

33.0.0.0 200.100.50.0
200.100.150.0

PERFORMING REDISTRIBUTION OF RIP INTO OSPF 444

A(config)# router ospf 444
A(config-router)# redistribute rip subnets

B# show ip route

NOTE: Network 200.100.50.0 has been reached on Router-B as OE2.

MISSING NETWORKS ON ROUTER-B:

33.0.0.0
200.100.150.0

D# show ip route

NOTE: Network 200.100.50.0 has been reached on Router-D as OE-2.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 124

C# show ip route

MISSING NETWORKS ON ROUTER-C:

1.0.0.0 4.0.0.0
11.0.0.0 22.0.0.0
44.0.0.0 200.100.50.0
200.100.100.0 200.100.200.0

PERFORMING REDISTRIBUTION OF OSPF 444 INTO IGRP 222

D(config)# router igrp 222
D(config-router)# redistribute ospf 444
D(config-router)# default-metric 1 1 1 1 1

C# show ip route

NOTE: Routing Table of Router-C has been completed/converged.

REDISTRIBUTION OF OSPF 555 INTO IGRP 222

C(config)# router igrp 222
C(config-router)# redistribute ospf 555
C(config-router)# default-metric 1 1 1 1 1

B# show ip route

NOTE: Network 200.100.150.0 has been reached on Router-B as I and

Routing Table of Router-B has also been completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 125

D# show ip route

NOTE: Network 200.100.150.0 has been reached on Router-D as I and

Routing Table of Router-D has also been completed/converged.

A# show ip route

MISSING NETWORKS ON ROUTER-A:

2.0.0.0 33.0.0.0
3.0.0.0 200.100.150.0

REDISTRIBUTION OF IGRP 222 INTO OSPF 444

B(config)# router ospf 444
B(config-router)# redistribute eigrp 222 subnets

A# show ip route

NOTE: Network 200.100.150.0 has been reached on Router-A as OE-2 and

Routing Table of Router-A has been completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 126

ANSWER NO. 6
CREATING STUB AREA
B(config)# router ospf 444
B(config-router)# area 1 stub

D(config)# router ospf 444

D(config-router)# area 1 stub

NOTE: It is not possible to create a stub on backbone area or on a

virtual link.

ANSWER NO. 7

CREATING ACCESS-LIST
D(config)# aaccess-list 70 permit 192.1.32.0 0.0.14.0
D(config)# aaccess-list 71 permit 192.1.33.0 0.0.14.0

WCM for Odd Numbers WCM for Even Numbers

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 127

CREATING ROUTE-MAP
D(config)# route-map shakeel permit 10
D(config-map)# match ip address 70
D(config-map)# set metric-type type-1
D(config-map)# exit
D(config)# route-map shakeel permit 11
D(config-map)# match ip address 71
D(config-map)# set metric-type type-2
D(config-map)# exit

REDISTRIBUTING STATIC ROUTES OF ROUTER-D USING ROUTE-MAP

D(config)# router ospf 444
D(config-router)# redistribute static subnets route-map shakeel

B# show ip route

NOTE: Static routes of Router-D have been redistributed as OE1 & OE2.

ANSWER NO. 8
CREATING 3 STATIC ROUTES ON ROUTER-B
B(config)# ip route 192.1.97.0 255.255.255.0 null 0
B(config)# ip route 192.1.98.0 255.255.255.0 null 0
B(config)# ip route 192.1.99.0 255.255.255.0 null 0

REDISTRIBUTING STATIC ROUTES IN OSPF 444

B(config)# router ospf 444
B(config-router)# redistribute static subnets

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 128

D# show ip route

C# show ip route

NOTE: Static routes of Router-B have been redistributed.

ROUTE-SUMMARIZATION OF STATIC ROUTES OF ROUTER-B

B(config)# router ospf 444

B(config-router)# summary-address 192.1.96.0 255.255.252.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 129

D# show ip route

C# show ip route

NOTE: You’ll not be unable to see summary address 192.1.96.0/22 on

Router-C, because there is no subnet field in header of RIP &
IGRP.

ANSWER NO. 10
PERFORMING AUTHENTICATION ON OSPF 444 AREA-1 – ROUTER-A
A(config)# router ospf 444
A(config-router)# area 1 authentication
A(config-router)# exit
A(config)# interface serial 1/0
password
A(config-if)# ip ospf authentication-key hello
A(config-router)# exit
A(config)# interface serial 1/1
A(config-if)# ip ospf authentication-key hello

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 130

PERFORMING AUTHENTICATION ON OSPF 444 AREA-1 – ROUTER-B

B(config)# router ospf 444
B(config-router)# area 1 authentication
B(config-router)# exit
B(config)# interface serial 1/0
B(config-if)# ip ospf authentication-key hello

PERFORMING AUTHENTICATION ON OSPF 444 AREA-1 – ROUTER-D

D(config)# router ospf 444
D(config-router)# area 1 authentication
D(config-router)# exit
D(config)# interface serial 1/1
D(config-if)# ip ospf authentication-key hello

ANSWER TO QUESTION NO. 9

ADMINISTRATIVE DISTANCE VALUES
Default
Route Source Distance
Values
Connected interface 0
Static route 1
Enhanced Interior Gateway Routing
5
Protocol (EIGRP) summary route
External Border Gateway Protocol
20
(BGP)
Internal EIGRP 90
IGRP 100
OSPF 110
Intermediate System-to-
115
Intermediate System (IS-IS)
Routing Information Protocol
120
(RIP)
Exterior Gateway Protocol (EGP) 140
On Demand Routing (ODR) 160
External EIGRP 170
Internal BGP 200
Unknown* 255

NOTE: Network 200.100.200.0 has two paths available to reach on

Router-B. One is through OSPF and the other is through IGRP.
Currently, it is reaching on Router-B using IGRP path because
IGRP has the lower administrative distance value than OSPF.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 131

INCREASING ADMINISTRATIVE DISTANCE OF IGRP

Following commands shall be used to forcefully increase the administrative distance
value of IGRP, so that network 200.100.200.0 shall reach on Router-B as OSPF.

B(config)# router igrp 222

B(config-router)# distance 150
B(config-router)# end
B# clear ip route *

C(config)# router igrp 222

C(config-router)# distance 150
C(config-router)# end
C# clear ip route *

D(config)# router igrp 222

D(config-router)# distance 150
D(config-router)# end
D# clear ip route *

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 132

LECTURE NO. 20
19 Jan 2009
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS

Figure-20a
(Note: Lab results are produced using GNS3 simulator)

Question NO. 1 Set Router-IDs as per following detail:

Router-A 11.1.1.1 For OSPF 444

Router-B 22.2.2.2 For OSPF 444
Router-C 33.3.3.3 For EIGRP 222
Router-D 44.4.4.4 For OSPF 444

Question NO. 2 Configure Routing Protocols as shown in Figure-20a.

Question NO. 3 Advertise Router-IDs (as mentioned in Question-1) in the

appropriate routing protocols.

Question NO. 4 Define 16 static routes on Router-D, starting from 192.1.32.0 .

Question NO. 5 Perform convergence of routing protocols so that you can ping
each and every IP address, available in the topology. Perform
clock-wise redistribution (if required).

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 133

Question NO. 6 Redistribute static routes of Router-D. Remember that odd

number routes must redistribute as OE-2 and even number routes
must redistribute as OE-1.

Question NO. 7 Define following 3 static routes on Router-B, redistribute

these routes in OSPF and perform route summarization.

192.1.97.0
192.1.98.0
192.1.99.0

Question NO. 9 Perform authentication on OSPF-444 Area-2

In this lecture, we'll notice followings:

Area Authentication
Behavior between EIGRP and IGRP
Behavior between OSPF444 and OSPF-555

SOLUTION
BASIC CONFIGURATION OF ROUTER-A
A(config)# interface s 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface s 1/1

A(config-if)# ip address 4.0.0.2 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface f 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown
A(config-if)# exit

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface s 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface s 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface f 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown
B(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 134

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface s 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface s 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface f 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown
C(config-if)# exit

BASIC CONFIGURATION OF ROUTER-D

D(config)# interface s 1/0
D(config-if)# ip address 3.0.0.2 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface s 1/1

D(config-if)# ip address 4.0.0.1 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface f 0/0

D(config-if)# ip address 200.100.200.1 255.255.255.0
D(config-if)# no shutdown
D(config-if)# exit

ROUTING TABLE OF ROUTE-A, B, C & D

A# show ip route

B# show ip route

C# show ip route

D# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 135

ANSWER NO. 1

CREATING LOOPBACK INTERFACE ON ROUTER-A, B, C & D

(FOR SETTING UP ROUTER-ID)

A(config)# interface loopback 0

A(config-if)# ip address 11.1.1.1 255.255.255.255

B(config)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.255.255.255

C(config)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.255.255.255

D(config)# interface loopback 0

D(config-if)# ip address 44.4.4.4 255.255.255.255

NOTE: PLEASE ALSO SEE ANSWER NO. 2 & 3

ANSWER NO. 2 & 3

CONFIGURING ROUTING PROTOCOLS AND SETTING + ADVERTISING

ROUTER-ID
A(config)# router ospf 444
A(config-router)# router-id 11.1.1.1 Part of Question No. 1
A(config-router)# network 11.1.1.1 0.0.0.0 area 0 Part of Question No. 3
A(config-router)# network 1.0.0.0 0.255.255.255 area 0
A(config-router)# network 4.0.0.0 0.255.255.255 area 2
A(config-router)# exit
A(config)# router ospf 555
A(config-router)# network 200.100.50.0 0.0.0.255 area 5

NOTE: Here, we need 2 Router-IDs, one for OSPF 444 and other for OSPF
555. We have set 11.1.1.1 IP as Router-ID of OSPF 444 on
Router-A. For OSPF 555, the highest IP address i.e.
200.100.50.1 of Router-A will automatically become Router-ID.

B(config)# router ospf 444

B(config-router)# router-id 22.2.2.2 Part of Question No. 1
B(config-router)# network 22.2.2.2 0.0.0.0 area 1 Part of Question No. 3
B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 1
B(config-router)# exit
B(config)# router eigrp 222
B(config-router)# network 2.0.0.0

C(config)# router eigrp 222

C(config-router)# eigrp router-id 33.3.3.3 Part of Question No. 1
C(config-router)# network 33.3.3.3 0.0.0.0 Part of Question No. 3
C(config-router)# network 3.0.0.0
C(config-router)# network 2.0.0.0
C(config-router)# exit
C(config)# router igrp 222
C(config-router)# network 200.100.150.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 136

D(config)# router ospf 444

D(config-router)# router-id 44.4.4.4 Part of Question No. 1
D(config-router)# network 44.4.4.4 0.0.0.0 area 2 Part of Question No. 3
D(config-router)# network 4.0.0.0 0.255.255.255 area 2
D(config-router)# network 200.100.200.0 0.0.0.255 area 3
D(config-router)# exit
D(config)# router eigrp 222
D(config-router)# network 3.0.0.0
D(config-router)# exit

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

MISSING NETWORKS ON ROUTER-A:

2.0.0.0
3.0.0.0
33.0.0.0
44.0.0.0
200.100.150.0
200.100.200.0

B# show ip route

MISSING NETWORKS ON ROUTER-B:

44.0.0.0
200.100.50.0
200.100.200.0

C# show ip route

MISSING NETWORKS ON ROUTER-C:

1.0.0.0
4.0.0.0
11.0.0.0
22.0.0.0
44.0.0.0
200.100.50.0
200.100.100.0
200.100.200.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 137

D# show ip route

MISSING NETWORK ON ROUTER-D:

200.100.50.0

ANSWER NO. 4
DEFINING 16 STATIC ROUTES ON ROUTER-D
D(config)# ip route 192.1.32.0 255.255.255.0 null 0
D(config)# ip route 192.1.33.0 255.255.255.0 null 0
D(config)# ip route 192.1.34.0 255.255.255.0 null 0
D(config)# ip route 192.1.35.0 255.255.255.0 null 0
D(config)# ip route 192.1.36.0 255.255.255.0 null 0
D(config)# ip route 192.1.37.0 255.255.255.0 null 0
D(config)# ip route 192.1.38.0 255.255.255.0 null 0
D(config)# ip route 192.1.39.0 255.255.255.0 null 0
D(config)# ip route 192.1.40.0 255.255.255.0 null 0
D(config)# ip route 192.1.41.0 255.255.255.0 null 0
D(config)# ip route 192.1.42.0 255.255.255.0 null 0
D(config)# ip route 192.1.43.0 255.255.255.0 null 0
D(config)# ip route 192.1.44.0 255.255.255.0 null 0
D(config)# ip route 192.1.45.0 255.255.255.0 null 0
D(config)# ip route 192.1.46.0 255.255.255.0 null 0
D(config)# ip route 192.1.47.0 255.255.255.0 null 0

ANSWER NO. 5
CREATING VIRTUAL LINK BETWEEN ROUTER-A & D
A(config)# router ospf 444
A(config-router)# area 2 virtual-link 44.4.4.4

D(config)# router ospf 444

D(config-router)# area 2 virtual-link 11.1.1.1

B# show ip route

MISSING NETWORK ON ROUTER-B:

200.100.50.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 138

PERFORMING REDISTRIBUTION OF OSPF 555 INTO OSPF 444

A(config)# router ospf 444
A(config-router)# redistribute ospf 555 subnets

B# show ip route

NOTE: Network 200.100.50.0 has been reached on Router-B as OE-2 and

routing table of Router-B has been completed/converged.

D# show ip route

NOTE: Network 200.100.50.0 has been reached on Router-D as OE-2 and

Routing Table of Router-D is completed/converged.

C# show ip route

NOTE: Routing table of Router-C is not completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 139

PERFORMING REDISTRIBUTION OF OSPF 444 INTO EIGRP 222

D(config)# router eigrp 222
D(config-router)# redistribute ospf 444
D(config-router)# default-metric 1 1 1 1 1

C# show ip route

NOTE: Routing Table of Router-C has been completed/converged.

A# show ip route

MISSING NETWORKS ON ROUTER-A:

2.0.0.0
3.0.0.0
33.0.0.0
200.100.150.0

REDISTRIBUTION OF EIGRP 222 INTO OSPF 444

B(config)# router ospf 444
B(config-router)# redistribute eigrp 222 subnets

A# show ip route

NOTE: Routing Table of Router-A has been completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 140

USING PING COMMAND

ANSWER NO. 6
CREATING ACCESS-LIST

D(config)# access-list 70 permit 192.1.32.0 0.0.14.0

D(config)# access-list 71 permit 192.1.33.0 0.0.14.0

WCM for Odd Numbers WCM for Even Numbers

CREATING ROUTE-MAP
D(config)# route-map shakeel permit 10
D(config-route-map)# match ip address 70
D(config-route-map)# set metric-type type-1
D(config-route-map)# exit
D(config)# route-map shakeel permit 11
D(config-route-map)# match ip address 71
D(config-route-map)# set metric-type type-2
D(config-route-map)# exit

REDISTRIBUTING ROUTE-MAP
D(config)# router ospf 444
D(config-router)# redistribute static subnets route-map shakeel

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 141

B# show ip route

NOTE: Static routes of Router-D have been redistributed as OE2 and

OE1.

ANSWER NO. 8
CREATING 3 STATIC ROUTES ON ROUTER-B
B(config)# ip route 192.1.97.0 255.255.255.0 null 0
B(config)# ip route 192.1.98.0 255.255.255.0 null 0
B(config)# ip route 192.1.99.0 255.255.255.0 null 0

REDISTRIBUTING STATIC ROUTES IN OSPF

B(config)# router ospf 444
B(config-router)# redistribute static subnets

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 142

B# show ip route

C# show ip route

NOTE: Static routes of Router-B have been redistributed.

ROUTE-SUMMARIZATION OF STATIC ROUTES OF ROUTER-B

B(config)# router ospf 444

B(config-router)# summary-address 192.1.96.0 255.255.252.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 143

D# show ip route

C# show ip route

ANSWER NO. 9
PERFORMING AUTHENTICATION ON OSPF 444 AREA 2 – ROUTER B
A(config)# router ospf 444
A(config-router)# area 2 authentication
A(config-router)# exit
A(config)# interface serial 1/1
A(config-if)# ip ospf authentication-key cisco password

D# show ip ospf neighbor

D#

NOTE: Neighbor 11.1.1.1 is not found. To see neighbor, we need to

perform authentication on other end of OSPF-444 Area-2 (i.e.
Serial 1/1 of Router-D).

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 144

PERFORMING AUTHENTICATION ON OSPF 444 AREA 2 – ROUTER D

D(config)# router ospf 444
D(config-router)# area 2 authentication
D(config-router)# exit
D(config)# interface serial 1/1
D(config-if)# ip ospf authentication-key cisco password

AFTER AUTHENTICATION
A# show ip ospf neighbor

D# show ip ospf neighbor

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 145

COMPLEMENTARY LECTURE NO. 1

28 May 2009
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS

(Note: Lab results are produced using GNS3 simulator)

Question NO. 1 Set Router-IDs as per following detail:

Router-A 11.1.1.1 For OSPF 11

Router-B 22.2.2.2 For OSPF 11
Router-C 33.3.3.3 For OSPF 22
Router-D 44.4.4.4 For OSPF 11

Question NO. 2 Configure Routing Protocols as shown in above figure.

Question NO. 3 Advertise Router-IDs (as mentioned in Question-1) in the

appropriate routing protocols.

Question NO. 4 Perform convergence of routing protocols so that you can ping
each and every IP address, available in the topology. Perform
anti-clock-wise redistribution (if required).

Question NO. 5 Increase administrative distance of IGRP so that network

3.0.0.0 can reach on Router-A as OSPF external route.

Question NO. 6 Define 4 static routes on Router-A, starting from 192.168.17.0

to 192.168.20.0 .

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 146

Question NO. 7 Redistribute static routes of Router-A. Remember that odd

number routes must redistribute as OE-1 and even number routes
must redistribute as OE-2.

Question NO. 8 Try to configure OSPF 11 Area 1 as stub area.

SOLUTION
BASIC CONFIGURATION OF ROUTER-A
A(config)# interface s 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface s 1/1

A(config-if)# ip address 4.0.0.2 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface f 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown
A(config-if)# exit

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface s 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface s 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface f 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown
B(config-if)# exit

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface s 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface s 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface f 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown
C(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 147

BASIC CONFIGURATION OF ROUTER-D

D(config)# interface s 1/0
D(config-if)# ip address 3.0.0.2 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface s 1/1

D(config-if)# ip address 4.0.0.1 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface f 0/0

D(config-if)# ip address 200.100.200.1 255.255.255.0
D(config-if)# no shutdown
D(config-if)# exit

ROUTING TABLE OF ROUTE-A, B, C & D

A# show ip route

B# show ip route

C# show ip route

D# show ip route

ANSWER NO. 1
CREATING LOOPBACK INTERFACE ON ROUTER-A, B, C & D
(FOR SETTING UP ROUTER-ID)

A(config)# interface loopback 0

A(config-if)# ip address 11.1.1.1 255.255.255.255

B(config)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.255.255.255

C(config)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.255.255.255

D(config)# interface loopback 0

D(config-if)# ip address 44.4.4.4 255.255.255.255

NOTE: For remaining configuration, please also see Answer No. 2 & 3

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 148

ANSWER NO. 2 & 3

CONFIGURING ROUTING PROTOCOLS AND SETTING + ADVERTISING
ROUTER-ID
A(config)# router ospf 11
A(config-router)# router-id 11.1.1.1 Part of Question No. 1
A(config-router)# network 11.1.1.1 0.0.0.0 area 1 Part of Question No. 3
A(config-router)# network 4.0.0.0 0.255.255.255 area 2
A(config-router)# network 1.0.0.0 0.255.255.255 area 1
A(config-router)# exit
A(config)# router ospf 22
A(config-router)# network 200.100.50.0 0.0.0.255 area 1

NOTE: Here, we need 2 Router-IDs, one for OSPF 11 and other for OSPF
22. We have set 11.1.1.1 IP as Router-ID of OSPF 11 on
Router-A. For OSPF 22, the highest IP address i.e. 200.100.50.1
of Router-A will automatically become Router-ID.

B(config)# router ospf 11

B(config-router)# router-id 22.2.2.2 Part of Question No. 1
B(config-router)# network 22.2.2.2 0.0.0.0 area 0 Part of Question No. 3
B(config-router)# network 1.0.0.0 0.255.255.255 area 1
B(config-router)# network 200.100.100.0 0.0.0.255 area 0
B(config-router)# exit
B(config)# router igrp 1
B(config-router)# network 2.0.0.0

C(config)# router ospf 22

C(config-router)# router-id 33.3.3.3 Part of Question No. 1
C(config-router)# network 33.3.3.3 0.0.0.0 area 2 Part of Question No. 3
C(config-router)# network 200.100.150.0 0.0.0.255 area 2
C(config-router)# exit
C(config)# router igrp 1
C(config-router)# network 2.0.0.0
C(config-router)# network 3.0.0.0

D(config)# router ospf 11

D(config-router)# router-id 44.4.4.4 Part of Question No. 1
D(config-router)# network 44.4.4.4 0.0.0.0 area 2 Part of Question No. 3
D(config-router)# network 4.0.0.0 0.255.255.255 area 2
D(config-router)# exit
D(config)# router igrp 1
D(config-router)# network 3.0.0.0
D(config-router)# exit

D(config)# router rip

D(config-router)# network 200.100.200.0
D(config-router)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 149

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

MISSING NETWORKS ON ROUTER-A:

2.0.0.0 3.0.0.0
33.0.0.0 44.0.0.0
200.100.150.0 200.100.200.0

B# show ip route

MISSING NETWORKS ON ROUTER-B:

4.0.0.0 44.0.0.0
33.0.0.0 200.100.50.0
200.100.200.0 200.100.150.0

C# show ip route

MISSING NETWORKS ON ROUTER-C:

1.0.0.0 4.0.0.0
11.0.0.0 22.0.0.0
44.0.0.0 200.100.50.0
200.100.100.0 200.100.200.0

D# show ip route

MISSING NETWORK ON ROUTER-D:

1.0.0.0 11.1.1.1
22.2.2.2 33.3.3.3
200.100.50.0 200.100.100.0
200.100.150.0

CREATING VIRTUAL LINK BETWEEN ROUTER-A & B

A(config)# router ospf 11
A(config-router)# area 1 virtual-link 22.2.2.2

B(config)# router ospf 11

B(config-router)# area 1 virtual-link 11.1.1.1

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 150

ANSWER NO. 4
REDISTRIBUTION OF OSPF 22 INTO OSPF 11 – ROUTER A
A(config)# router ospf 11
A(config-router)# redistribute ospf 22 subnets metric 10

REDISTRIBUTION OF OSPF 11 INTO IGRP 1 – ROUTER B

B(config)# router IGRP 1
B(config-router)# redistribute ospf 11 metric 1 1 1 1 1

REDISTRIBUTION OF OSPF 22 INTO IGRP 1 – ROUTER C

C(config)# router IGRP 1
C(config-router)# redistribute ospf 22 metric 1 1 1 1 1

REDISTRIBUTION OF IGRP 1 INTO OSPF 11 – ROUTER D

D(config)# router ospf 11
D(config-router)# redistribute igrp 1 subnets metric 20

REDISTRIBUTION OF RIP INTO OSPF 11 – ROUTER D

D(config)# router ospf 11
D(config-router)# redistribute rip subnets metric 15

REDISTRIBUTION OF IGRP INTO RIP – ROUTER D

D(config)# router rip
D(config-router)# redistribute igrp 1 metric 5

ROUTING TABLES OF ROUTER-A, B C & D

A# show ip route

NOTE: Routing Table of Router-A has been completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 151

B# show ip route

NOTE: Routing Table of Router-B has been completed/converged.

C# show ip route

NOTE: Routing Table of Router-C has been completed/converged.

D# show ip route

NOTE: Routing Table of Router-D has been completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 152

USING PING COMMAND

ANSWER NO. 5

B# traceroute 3.0.0.2

NOTE: The path to 3.0.0.2 from Router-B is

Router-B Æ Router-C Æ Router-D

B# show ip route

NOTE: Network 3.0.0.0 is reaching as I on Router-B.

INCREASING ADMINISTRATIVE DISTANCE OF IGRP 1

B(config)# router igrp 1
B(config-router)# distance 150
B(config-router)# end
B# clear ip route *

C(config)# router igrp 1

C(config-router)# distance 150
C(config-router)# end
C# clear ip route *

D(config)# router igrp 1

D(config-router)# distance 150
D(config-router)# end
D# clear ip route *

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 153

B# traceroute 3.0.0.2

NOTE: After changing administrative distance of IGRP to 150, the path

to 3.0.0.2 from Router-B is:
Router-B Æ Router-A Æ Router-D

B# show ip route

NOTE: After changing administrative distance of IGRP to 150, network

3.0.0.0 is reaching as OE2 on Router-B.

ANSWER NO. 6
DEFINING 4 STATIC ROUTES ON ROUTER-A
A(config)# ip route 192.1.16.0 255.255.255.0 null 0
A(config)# ip route 192.1.17.0 255.255.255.0 null 0
A(config)# ip route 192.1.18.0 255.255.255.0 null 0
A(config)# ip route 192.1.19.0 255.255.255.0 null 0

ANSWER NO. 7
CREATING ACCESS-LIST
A(config)# access-list 12 permit 192.1.16.0 0.0.2.0
A(config)# access-list 13 permit 192.1.17.0 0.0.2.0

WCM for Odd Numbers WCM for Even Numbers

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 154

CREATING ROUTE-MAP
A(config)# route-map shakeel permit 5
A(config-route-map)# match ip address 12
A(config-route-map)# set metric-type type-2
A(config-route-map)# exit
A(config)# route-map shakeel permit 6
A(config-route-map)# match ip address 13
A(config-route-map)# set metric-type type-1
A(config-route-map)# exit

REDISTRIBUTING STATIC ROUTES USING ROUTE-MAP

A(config)# router ospf 11
A(config-router)# redistribute static subnets route-map shakeel

B# show ip route

NOTE: Static routes of Router-A have been redistributed as OE2 and

OE1.

ANSWER NO. 8
CREATING STUB AREA
A(config)# router ospf 11
A(config-router)# area 1 stub

B(config)# router ospf 444

B(config-router)# area 1 stub

NOTE: It is not possible to create a stub on backbone area or on a

virtual link.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 155

RUNNING CONFIGURATION OF ROUTER-A

!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname A
!
!
ip subnet-zero
ip cef
!
!
!
call rsvp-sync
!
!
!
!
!
!
!
!
interface Loopback0
ip address 11.1.1.1 255.255.255.255
!
interface FastEthernet0/0
ip address 200.100.50.1 255.255.255.0
no keepalive
duplex half
!
interface Serial1/0
ip address 1.0.0.1 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/1
ip address 4.0.0.2 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 11
router-id 11.1.1.1
log-adjacency-changes
area 1 virtual-link 22.2.2.2
redistribute static subnets route-map shakeel
redistribute ospf 22 metric 5 subnets
network 1.0.0.0 0.255.255.255 area 1
network 4.0.0.0 0.255.255.255 area 2
network 11.1.1.1 0.0.0.0 area 1
!
router ospf 22
log-adjacency-changes
network 200.100.50.0 0.0.0.255 area 1
!

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 156

ip classless
ip route 192.1.16.0 255.255.255.0 Null0
ip route 192.1.17.0 255.255.255.0 Null0
ip route 192.1.18.0 255.255.255.0 Null0
ip route 192.1.19.0 255.255.255.0 Null0
no ip http server
!
access-list 12 permit 192.1.16.0 0.0.2.0
access-list 13 permit 192.1.17.0 0.0.2.0
route-map shakeel permit 5
match ip address 12
set metric-type type-2
!
route-map shakeel permit 6
match ip address 13
set metric-type type-1
!
!
dial-peer cor custom
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
line aux 0
line vty 0 4
login
!
end

RUNNING CONFIGURATION OF ROUTER-B

!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname B
!
!
ip subnet-zero
ip cef
!
!
!
call rsvp-sync
!
!
!
!
!
interface Loopback0
ip address 22.2.2.2 255.255.255.255
!
interface FastEthernet0/0
ip address 200.100.100.1 255.255.255.0
no keepalive
duplex half
!
interface Serial1/0
ip address 1.0.0.2 255.0.0.0
serial restart-delay 0
clockrate 64000

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 157

!
interface Serial1/1
ip address 2.0.0.1 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 11
router-id 22.2.2.2
log-adjacency-changes
area 1 virtual-link 11.1.1.1
network 1.0.0.0 0.255.255.255 area 1
network 22.2.2.2 0.0.0.0 area 0
network 200.100.100.0 0.0.0.255 area 0
!
router igrp 1
redistribute ospf 11 metric 1 1 1 1 1
network 2.0.0.0
distance 150
!
ip classless
no ip http server
!
!
dial-peer cor custom
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
line aux 0
line vty 0 4
login
!
end

RUNNING CONFIGURATION OF ROUTER-C

!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname C
!
!
ip subnet-zero
ip cef
!
!
!
call rsvp-sync
!

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 158

!
!
!
!
!
!
interface Loopback0
ip address 33.3.3.3 255.255.255.255
!
interface FastEthernet0/0
ip address 200.100.150.1 255.255.255.0
no keepalive
duplex half
!
interface Serial1/0
ip address 3.0.0.1 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/1
ip address 2.0.0.2 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 22
router-id 33.3.3.3
log-adjacency-changes
network 33.3.3.3 0.0.0.0 area 2
network 200.100.150.0 0.0.0.255 area 2
!
router igrp 1
redistribute ospf 22 metric 1 1 1 1 1
network 2.0.0.0
network 3.0.0.0
distance 150
!
ip classless
no ip http server
!
!
dial-peer cor custom
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
line aux 0
line vty 0 4
login
!
end

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 159

RUNNING CONFIGURATION OF ROUTER-D

!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname D
!
!
ip subnet-zero
ip cef
!
!
!
call rsvp-sync
!
!
!
!
!
!
!
!
interface Loopback0
ip address 44.4.4.4 255.255.255.255
!
interface FastEthernet0/0
ip address 200.100.200.1 255.255.255.0
no keepalive
duplex half
!
interface Serial1/0
ip address 3.0.0.2 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/1
ip address 4.0.0.1 255.0.0.0
serial restart-delay 0
clockrate 64000
!
interface Serial1/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 11
router-id 44.4.4.4
log-adjacency-changes
redistribute igrp 1 metric 20 subnets
redistribute rip metric 15 subnets
network 4.0.0.0 0.255.255.255 area 2
network 44.4.4.4 0.0.0.0 area 2
!
router rip
redistribute igrp 1 metric 5
network 200.100.200.0
!

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 160

router igrp 1
redistribute rip
network 3.0.0.0
distance 150
!
ip classless
no ip http server
!
!
dial-peer cor custom
!
!
!
!
gatekeeper
shutdown
!
!
line con 0
line aux 0
line vty 0 4
login
!
end

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 161

LECTURE NO. 21
21 Jan 2009
EIGRP (ENHANCED INTERIOR GATEWAY PROTOCOL)
(HYBRID ROUTING PROTOCOL)
(DISTANCE VECTOR)
(LINK STATE)
ƒ In EIGRP, summarization is by default enabled as "auto summarization", which is
a BGP feature and it is not using for redistributed routes. Auto-summarization
can only be applied on the networks which are advertised in EIGRP.

ƒ EIGRP can run on any routed protocol.

Routed Protocols = IP, IPX

Routing Protocols = RIP, IGRP, OSPF

ƒ EIGRP Multicast Address = 224 . 0 . 0 . 10

ƒ In OSPF, summary-address command is performed at A(config-router)# router mode,

but in EIGRP this command can be performed at A(config-if)# interface mode.

Figure-21a
(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# clock rate 64000
B(config-if)# no shutdown

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# clock rate 64000
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 162

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface ethernet 2/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A, B & C

(BEFORE RUNNING PROTOCOLS)

A# show ip route

B# show ip route

C# show ip route

CONFIGURING PROTOCOLS ON ROUTER-A, B & C

A(config)# router igrp 11
A(config-router)# network 1.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router igrp 11

B(config-router)# network 1.0.0.0
B(config-router)# exit
B(config)# router eigrp 11
B(config-router)# network 2.0.0.0
B(config-router)# no auto-summary

C(config)# router eigrp 11

C(config-router)# network 2.0.0.0
C(config-router)# network 200.100.150.0
C(config-router)# no auto-summary

ROUTING TABLE OF ROUTER-A, B & C

(AFTER RUNNING PROTOCOLS)

A# show ip route

B# show ip route

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 163

DEFINING 4 STATIC ROUTES ON ROUTER-C

C(config)# ip route 192.1.17.0 255.255.255.0 null 0
C(config)# ip route 192.1.18.0 255.255.255.0 null 0
C(config)# ip route 192.1.19.0 255.255.255.0 null 0
C(config)# ip route 192.1.20.0 255.255.255.0 null 0

REDISTRIBUTION OF STATIC ROUTES INTO EIGRP 11

C(config)# router eigrp 11
C(config-router)# redistribute static metric 1 1 1 1 1

ROUTING TABLE OF ROUTER-A, B & C

(AFTER REDISTRIBUTION OF STATIC ROUTES INTO EIGRP 11)

A# show ip route

B# show ip route

NOTE: Static routes of Router-C have been redistribute. Auto summary

of static routes is not found on Router-A & B, therefore, we'll
perform manual summarization of static routes.

C# show ip route

MANUAL SUMMARIZATION OF STATIC ROUTES IN EIGRP

C(config)# interface serial 1/1
C(config-if)# ip summary-address eigrp 11 192.1.16.0 255.255.248.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 164

ROUTING TABLE OF ROUTER-A & B

(AFTER PERFORMING MANUAL SUMMARIZATION OF STATIC ROUTES)

A# clear ip route *
A# show ip route

NOTE: Summary address of static routes of Router-C cannot be seen on

Router-A, because Router-A is running IGRP and we know that
there is no subnet field in the header of IGRP & RIP.

B# show ip route

Manual summary address of static routes

C# show ip route

Manual summary address of static routes

DEFINING 3 LOOPBACK INTERFACES ON ROUTER-C

C(config)# interface loopback 0
C(config-if)# ip address 192.1.1.33 255.255.255.224
C(config-if)# exit

C(config-if)# interface loopback 1

C(config-if)# ip address 192.1.1.65 255.255.255.224
C(config-if)# exit

C(config-if)# interface loopback 2

C(config-if)# ip address 192.1.1.97 255.255.255.224

NOTE: Here, we have assigned IP addresses to loopback interfaces,

using 3 bit subnetting of Class-C network 192.1.1.0

ADVERTISING LOOPBACK INTERFACES INTO EIGRP 11

METHOD-1 (using wild card mask for a single IP)
C(config)# router eigrp 11
C(config-router)# network 192.1.1.33 0.0.0.0

METHOD-2 (using wild card mask for a subnet)

C(config)# router eigrp 11
C(config-router)# network 192.1.1.32 0.0.0.31

METHOD-3 (for a network)

C(config)# router eigrp 11
C(config-router)# network 192.1.1.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 165

ROUTING TABLE OF ROUTER-A & B

A# show ip route

Network-ID of loopback addresses

B# show ip route

Manual summary address of static routes

Since we have disabled auto-summarization feature on Router-C,

therefore, we can see individual loopback addresses on
Router-B.

ENABLING AUTO-SUMMARIZATION
C(config)# router eigrp 11
C(config-router)# auto-summary

ROUTING TABLE OF ROUTER-A & B

(AFTER ENABLING AUTO-SUMMARIZATION)

A# show ip route

Network-ID of loopback addresses

NOTE: Summary address 192.1.16.0/21 of static routes of Router-C

cannot be seen on Router-A, because Router-A is running IGRP
and there is no summary-address field in the header of RIP &
IGRP.

B# show ip route

Manual summary address of static routes

Network-ID of loopback addresses

NOTE: Remember that auto-summary features is only for those

network/routes, which are advertised in EIGRP, not for those
which are redistributed in EIGRP. That’s why, we performed
manual summary of static routes on Router-C. If you remove this
command from the serial interface 1/1 of Router-C, you will not
be able to see auto-summary of static routes on Router-B.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 166

PERFORMING AUTHENTICATION IN EIGRP

B# show ip eigrp topology

NOTE: show ip eigrp topology command is equals to show ip ospf

database

BEFORE PERFORMING AUTHENTICATION ON ROUTER-B

B# show ip eigrp neighbor

PERFORMING AUTHENTICATION ON ROUTER-B

B(config)# key chain lahore Key chain name
B(config-keychain)# key 100 Key chain number
B(config-keychain-key)# key-string pakistan password
B(config-keychain-key)# exit
B(config-keychain)# exit
B(config)# interface serial 1/1
B(config-if)# ip authentication key-chain eigrp 11 lahore

B(config-if)# ip authentication mode eigrp 11 md5

AFTER PERFORMING AUTHENTICATION ON ROUTER-B

B# show ip eigrp neighbor

NOTE: Neighbor can not be seen until we perform authentication on the

other end (i.e. Serial 1/1 of Router-C).

PERFORMING AUTHENTICATION ON ROUTER-C

C(config)# key chain lahore Key chain name
C(config-keychain)# key 100 Key chain number
C(config-keychain-key)# key-string pakistan password
C(config-keychain-key)# exit
C(config-keychain)# exit
C(config)# interface serial 1/1
C(config-if)# ip authentication key-chain eigrp 11 lahore
C(config-if)# ip authentication mode eigrp 11 md5

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 167

AFTER PERFORMING AUTHENTICATION ON ROUTER-C

B# show ip eigrp neighbor

NOTE: Now we can see neighbor 2.0.0.2

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 168

COMPLEMENTARY LECTURE NO. 2

02 Jun 2009
EIGRP - LOAD BALANCING

(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.1.1.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown

A(config)# interface serial 1/2

A(config-if)# ip address 2.1.1.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown

A(config)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/1
B(config-if)# ip address 1.1.1.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/3

B(config-if)# ip address 2.1.1.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 169

ROUTING TABLE OF ROUTER-A & B

A# show ip route

B# show ip route

CONFIGURING PROTOCOLS ON ROUTER-A & B

A(config)# router eigrp 1
A(config-router)# network 1.0.0.0
A(config-router)# network 2.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router eigrp 1

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0
B(config-router)# network 200.100.100.0

ROUTING TABLE OF ROUTER-A & B

(AFTER RUNNING PROTOCOLS)

A# show ip route

B# show ip route

DEFINING 3 LOOPBACK INTERFACES ON ROUTER-B

B(config)# interface loopback 0
B(config-if)# ip address 192.1.1.33 255.255.255.224
B(config-if)# exit

B(config-if)# interface loopback 1

B(config-if)# ip address 192.1.1.65 255.255.255.224
B(config-if)# exit

B(config-if)# interface loopback 2

B(config-if)# ip address 192.1.1.97 255.255.255.224
B(config-if)# exit

NOTE: Here, we have assigned IP addresses to loopback interfaces,

using 3 bit subnetting of Class-C network 192.1.1.0

REDISTRIBUTING & ADVERTISING LOOPBACK INTERFACES IN EIGRP

B(config)# router eigrp 1
B(config-router)# network 192.1.1.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 170

ROUTING TABLE OF ROUTER-A & B

A# show ip route

Auto-summary address of loopback addresses

B# show ip route

Auto-summary address of loopback addresses

DISABLING AUTO-SUMMARIZATION
B(config)# router eigrp 1
B(config-router)# no auto-summary

ROUTING TABLE OF ROUTER-A & B

(AFTER DISABLING AUTO-SUMMARY FEATURE)

A# show ip route

B# show ip route

NOTE: After disabling auto-summary feature, auto-summary address is

disappeared from the routing table of Router-A & B.

ENABLING AUTO-SUMMARIZATION
B(config)# router eigrp 1
B(config-router)# auto-summary

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 171

DEFINING 4 STATIC ROUTES ON ROUTER-B

B(config)# ip route 192.1.17.0 255.255.255.0 null 0
B(config)# ip route 192.1.18.0 255.255.255.0 null 0
B(config)# ip route 192.1.19.0 255.255.255.0 null 0
B(config)# ip route 192.1.20.0 255.255.255.0 null 0

REDISTRIBUTION OF STATIC ROUTES INTO EIGRP 1

B(config)# router eigrp 1
B(config-router)# redistribute static metric 1 1 1 1 1

ROUTING TABLE OF ROUTER-A, & B

(AFTER REDISTRIBUTION OF STATIC ROUTES INTO EIGRP)

A# show ip route

B# show ip route

NOTE: Static routes of Router-B have been redistribute. Auto summary

of static routes is not found on Router-A & B, therefore, we'll
perform manual summarization of static routes.

MANUAL SUMMARIZATION OF STATIC ROUTES IN EIGRP

(FOR SERIAL 1/1 INTERFACE)

B(config)# interface serial 1/1

B(config-if)# ip summary-address eigrp 1 192.1.16.0 255.255.248.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 172

ROUTING TABLE OF ROUTER-A

(AFTER PERFORMING MANUAL SUMMARIZATION OF STATIC ROUTES)

A# show ip route

Manual summary address of static routes

NOTE: Manual summary address of static routes of Router-B is coming

via 1.1.1.2 and individual static routes are coming via
2.1.1.2.

MANUAL SUMMARIZATION OF STATIC ROUTES IN EIGRP

(FOR SERIAL 1/3 INTERFACE)

B(config)# interface serial 1/3

B(config-if)# ip summary-address eigrp 1 192.1.16.0 255.255.248.0

ROUTING TABLE OF ROUTER-A & B

A# show ip route

Manual summary address of static routes

Auto-summary address of loopback addresses

A# show interface serial 1/0

A# show interface serial 1/2

NOTE: Bandwidth is same on both interfaces.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 173

UN-EQUAL LOAD BALANCING BY CHANGING BANDWIDTH

A(config)# interface serial 1/2
A(config-if)# bandwidth 128
A(config-if)# exit

A# show interface serial 1/2

ROUTING TABLE OF ROUTER-A & B

(AFTER CHANGING BANDWIDTH ON SERIAL INTERFACES OF ROUTER-A)

A# show ip route

NOTE: Network 200.100.100.0 and auto-summary address 192.1.1.0 of

loopback interfaces were reaching on Router-A using two
different paths. Now, after changing bandwidth on serial 1/2
interface of Router-A, these routes are using only the path
with maximum bandwith (which is 1544 Kbit on serial 1/0
interface of Router-A).

A# show ip eigrp topology

NOTE: Routing table of Router-A only displays best path of network

200.100.100.0 and 192.1.1.0 but show ip eigrp topology command
displays both paths of these networks. If you are desirous to
see boths paths of these routes in the routing table of
Router-A, see varience:

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 174

VARIANCE
Variance is the technique through which we can see / show multiple paths of a
route.

CALCULATION OF VARIANCE
Network 200.100.100.0 = Max. Feasible Distance ÷ Min. Feasible Distance
= 20514560 ÷ 2172416
= 9.4432
= 10 round figure

A(config)# router eigrp 1

A(config-router)# variance 10
A(config-router)# end
A# clear ip eigrp neighbors

B(config)# router eigrp 1

B(config-router)# variance 10
B(config-router)# end
B# clear ip eigrp neighbors

A# show ip eigrp neighbors

NOTE: Routing table of Router-A displays both un-equal paths of the

networks 200.100.100.0 & 192.1.1.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 175

LECTURE NO. 22
23 Jan 2009
LAB - TOPOLOGY WITH DIFFERENT PROTOCOLS

Figure-22a
(Note: Lab results are produced using GNS3 simulator)

QUESTIONS

Question NO. 1 Configure Routing Protocols.

Question NO. 2 Set Router IDs as per following detail:

11.1.1.1 - For Router-A

22.2.2.2 - For Router-B
33.3.3.3 - For Router-C
44.4.4.4 - For Router-D

Advertise these Router-IDs in the appropriate routing

protocols.

Question NO. 3 Define Static Routes on Router-A, starting from 192.1.32.0 to

192.1.47.0.

Question NO. 4 Perform convergence.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 176

Question NO. 5 Perform anti-clockwise redistribution (if required).

Question NO. 6 Redistribute static routes in OSPF-555.

Question NO. 7 Try to block odd routes, which are coming from Route-A.

Question NO. 8 Perform MD5 authentication for EIGRP-222.

Question NO. 9 Define 4 loopback interfaces on Router-C and assign IP to these

loopback interfaces using 4 bit subnetting of Class-C network.

Question NO. 10 Advertise these loopback IDs in EIGRP-222 or EIGRP-111 and try
to disable auto-summary feature.

Question NO. 11 Define following 8 static routes on Router-B:

192.2.0.0/24
192.2.1.0/24
192.2.2.0/24
192.2.3.0/24
192.2.4.0/24
192.2.5.0/24
192.2.6.0/24
192.2.7.0/24

Question NO. 12 Redistribute static routes (mentioned in Question No. 11) in

EIGRP-222.

Question NO. 13 Using single line ACL, filter 1st four static routes (mentioned
in Question No. 11), so that they will not reach on Router-C.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 177

SOLUTION

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface serial 1/1

A(config-if)# ip address 4.0.0.2 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown
A(config-if)# exit

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# exit

B(config)# interface ethernet 2/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown
B(config-if)# exit

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/0
C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface serial 1/1

C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# clock rate 64000
C(config-if)# no shutdown
C(config-if)# exit

C(config)# interface ethernet 2/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown
C(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 178

BASIC CONFIGURATION OF ROUTER-D

D(config)# interface serial 1/0
D(config-if)# ip address 3.0.0.2 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface serial 1/1

D(config-if)# ip address 4.0.0.1 255.0.0.0
D(config-if)# no shutdown
D(config-if)# exit

D(config)# interface ethernet 2/0

D(config-if)# ip address 200.100.200.1 255.255.255.0
D(config-if)# no shutdown
D(config-if)# exit

ROUTING TABLE OF ROUTE-A, B, C AND D

A# show ip route

B# show ip route

C# show ip route

D# show ip route

ANSWER NO. 4
CREATING LOOPBACK INTERFACE ON ROUTER-A, B, C & D
(FOR SETTING UP ROUTER-ID)

A(config)# interface loopback 0

A(config-if)# ip address 11.1.1.1 255.255.255.255

B(config-if)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.255.255.255

C(config-if)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.255.255.255

D(config-if)# interface loopback 0

D(config-if)# ip address 44.4.4.4 255.255.255.255

NOTE: PLEASE ALSO SEE ANSWER NO. 2 & 3

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 179

ANSWER NO. 2 & 3

CONFIGURING ROUTING PROTOCOLS AND SETTING + ADVERTISING
ROUTER-ID
A(config)# router ospf 444
A(config-router)# router-id 11.1.1.1 Part of Question No. 1
A(config-router)# network 11.1.1.1 0.0.0.0 area 0 Part of Question No. 3
A(config-router)# network 4.0.0.0 0.255.255.255 area 1
A(config-router)# network 200.100.50.0 0.0.0.255 area 0
A(config-router)# exit
A(config)# router ospf 555
A(config-router)# network 1.0.0.0 0.255.255.255 area 4

NOTE: Here we need 2 Router-IDs, one for OSPF 444 and other for OSPF
555. We have set 11.1.1.1 IP as Router-ID for OSPF 444 on
Router-A.

For OSPF 555, the highest IP address i.e. 200.100.50.1 on

Router-A will automatically become Router-ID.

B(config)# router eigrp 222

B(config-router)# eigrp router-id 22.2.2.2 Part of Question No. 1
B(config-router)# network 22.2.2.2 0.0.0.0 Part of Question No. 3
B(config-router)# network 2.0.0.0
B(config-router)# exit
B(co7nfig)# router ospf 555
B(config-router)# network 1.0.0.0 0.255.255.255 area 4
B(config-router)# network 200.100.100.0 0.0.0.255 area 0

C(config)# router eigrp 222

C(config-router)# eigrp router-id 33.3.3.3 Part of Question No. 1
C(config-router)# network 33.3.3.3 0.0.0.0 Part of Question No. 3
C(config-router)# network 2.0.0.0
C(config-router)# exit
C(config)# router igrp 111
C(config-router)# network 200.100.150.0
C(config-router)# exit
C(config)# router eigrp 111
C(config-router)# network 3.0.0.0

D(config)# router ospf 444

D(config-router)# router-id 44.4.4.4 Part of Question No. 1
D(config-router)# network 44.4.4.4 0.0.0.0 area 2 Part of Question No. 3
D(config-router)# network 4.0.0.0 0.255.255.255 area 1
D(config-router)# network 200.100.200.0 0.0.0.255 area 2
D(config-router)# exit
D(config)# router eigrp 111
D(config-router)# network 3.0.0.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 180

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

MISSING NETWORKS ON ROUTER-A:

2.0.0.0 22.0.0.0
3.0.0.0 33.0.0.0
200.100.150.0 44.0.0.0
200.100.200.0

B# show ip route

MISSING NETWORKS ON ROUTER-B:

3.0.0.0 11.0.0.0
4.0.0.0 44.0.0.0
200.100.50.0 200.100.150.0
200.100.200.0

C# show ip route

MISSING NETWORKS ON ROUTER-C:

1.0.0.0 11.0.0.0
4.0.0.0 44.0.0.0
200.100.50.0 200.100.100.0
200.100.200.0

D# show ip route

MISSING NETWORKS ON ROUTER-D:

1.0.0.0 22.0.0.0
2.0.0.0 33.0.0.0
200.100.100.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 181

ANSWER NO. 4
DEFINING 16 STATIC ROUTES ON ROUTER-A
A(config)# ip route 192.1.32.0 255.255.255.0 null 0
A(config)# ip route 192.1.33.0 255.255.255.0 null 0
A(config)# ip route 192.1.34.0 255.255.255.0 null 0
A(config)# ip route 192.1.35.0 255.255.255.0 null 0
A(config)# ip route 192.1.36.0 255.255.255.0 null 0
A(config)# ip route 192.1.37.0 255.255.255.0 null 0
A(config)# ip route 192.1.38.0 255.255.255.0 null 0
A(config)# ip route 192.1.39.0 255.255.255.0 null 0
A(config)# ip route 192.1.40.0 255.255.255.0 null 0
A(config)# ip route 192.1.41.0 255.255.255.0 null 0
A(config)# ip route 192.1.42.0 255.255.255.0 null 0
A(config)# ip route 192.1.43.0 255.255.255.0 null 0
A(config)# ip route 192.1.44.0 255.255.255.0 null 0
A(config)# ip route 192.1.45.0 255.255.255.0 null 0
A(config)# ip route 192.1.46.0 255.255.255.0 null 0
A(config)# ip route 192.1.47.0 255.255.255.0 null 0

ANSWER NO. 5
CREATING VIRTUAL LINK BETWEEN ROUTER-A & D
A(config)# router ospf 444
A(config-router)# area 1 virtual-link 44.4.4.4

D(config)# router ospf 444

D(config-router)# area 1 virtual-link 11.1.1.1

A# show ip route

NOTE: Network 200.100.200.0 has been reached on Router-A as OIA.

PERFORMING REDISTRIBUTION OF OSPF 444 INTO OSPF 555

ON ROUTER-A (ANTI-CLOCKWISE)

A(config)# router ospf 555

A(config-router)# redistribute ospf 444 subnets

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 182

B# show ip route

NOTE: Following networks have been reached on Router-B:

4.0.0.0 11.0.0.0
44.0.0.0 200.100.50.0

C# show ip route

D# show ip route

NOTE: There is no change in the routing tables of Router-C & D.

PERFORMING REDISTRIBUTION OF OSPF 555 INTO EIGRP 222

ON ROUTER-B (ANTI-CLOCKWISE)

B(config)# router eigrp 222

B(config-router)# redistribute ospf 555
B(config-router)# default-metric 1 1 1 1 1

C# show ip route

NOTE: Routing Table of Router-C has been completed/converged.

PERFORMING REDISTRIBUTION OF EIGRP222 INTO IGRP 111

ON ROUTER-C (ANTI-CLOCKWISE)

C(config)# router eigrp 111

C(config-router)# redistribute eigrp 222 metric 1 1 1 1 1

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 183

D# show ip route

NOTE: Routing Table of Router-D has also been completed/converged.

PERFORMING REDISTRIBUTION OF EIGRP111 INTO OSPF 444

ON ROUTER-D (ANTI-CLOCKWISE)

D(config)# router ospf 444

D(config-router)# redistribute eigrp 111 subnets

A# show ip route

NOTE: Routing Table of Router-A has been completed/converged.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 184

B# show ip route

NOTE: Routing Table of Router-B has also been completed.

VERIFYING BY USING PING COMMAND

ANSWER NO. 6
REDISTRIBUTION OF STATIC ROUTES IN OSPF 555 (ON Router-A)
A(config)# router ospf 555
A(config-router)# redistribute static subnets metric 20

ANSWER NO. 7
CREATING ACCESS-LIST
B(config)# access-list 11 deny 192.1.33.0 0.0.14.0
B(config)# access-list 11 permit any

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 185

APPLYING DISTRIBUTE-LIST COMMAND

(FOR FILTERING RECORDS)

B(config)# router ospf 555

B(config-router)# distribute-list 11 in serial 1/0

ROUTING TABLE OF ROUTER-B

B# show ip route

NOTE: Odd Routes have been blocked on Router-B

ANSWER NO. 8
BEFORE PERFORMING AUTHENTICATION
B# show ip eigrp neighbors

C# show ip eigrp neighbors

PERFORMING AUTHENTICATION ON ROUTER-B

B(config)# key chain lahore Key chain name
B(config-keychain)# key 100 Key chain number
B(config-keychain-key)# key-string pakistan password
B(config-keychain-key)# exit
B(config-keychain)# exit
B(config)# interface serial 1/1
B(config-if)# ip authentication key-chain eigrp 222 lahore
B(config-if)# ip authentication mode eigrp 222 md5

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 186

AFTER PERFORMING AUTHENTICATION ON ROUTER-B

B# show ip eigrp neighbor

NOTE: Neighbor can not be seen until we perform authentication on the

other end (i.e. Serial 1/1 of Router-C).

PERFORMING AUTHENTICATION ON ROUTER-C

C(config)# key chain lahore Key chain name
C(config-keychain)# key 100 Key chain number
C(config-keychain-key)# key-string pakistan password
C(config-keychain-key)# exit
C(config-keychain)# exit
C(config)# interface serial 1/1
C(config-if)# ip authentication key-chain eigrp 222 lahore
C(config-if)# ip authentication mode eigrp 222 md5

AFTER PERFORMING AUTHENTICATION ON ROUTER-C

B# show ip eigrp neighbors

C# show ip eigrp neighbors

NOTE: Now we can see neighbor.

ANSWER NO. 9
CREATING 4 LOOPBACK INTERFACES ON ROUTER-C
AND ASSIGNING IPs USING 4 BIT SUBNETTED ADDRESSES OF CLASS-C Network

C(config)# interface loopback 1

C(config-if)# ip address 211.211.211.193 255.255.255.240
C(config-if)# exit
C(config)# interface loopback 2
C(config-if)# ip address 211.211.211.209 255.255.255.240
C(config-if)# exit
C(config)# interface loopback 3
C(config-if)# ip address 211.211.211.225 255.255.255.240
C(config-if)# exit
C(config)# interface loopback 4
C(config-if)# ip address 211.211.211.241 255.255.255.240

ANSWER NO. 10
ADVERTISING LOOPBACK INTERFACES IN EIGRP 222
C(config)# router eigrp 222
C(config-router)# no auto-summary
C(config-router)# network 211.211.211.193 0.0.0.0
C(config-router)# network 211.211.211.209 0.0.0.0
C(config-router)# network 211.211.211.225 0.0.0.0
C(config-router)# network 211.211.211.241 0.0.0.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 187

ROUTING TABLE OF ROUTER-B

(WITHOUT AUTO-SUMMARY)

B# show ip route

ENABLING AUTO-SUMMARY
C(config)# router eigrp 222
C(config-router)# auto-summary

ROUTING TABLE OF ROUTER-B

(WITH AUTO-SUMMARY)

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 188

ANSWER NO. 11 & 12

CREATING 8 STATIC ROUTES ON ROUTER-B
B(config)# ip route 192.2.0.0 255.255.255.0 null 0
B(config)# ip route 192.2.1.0 255.255.255.0 null 0
B(config)# ip route 192.2.2.0 255.255.255.0 null 0
B(config)# ip route 192.2.3.0 255.255.255.0 null 0
B(config)# ip route 192.2.4.0 255.255.255.0 null 0
B(config)# ip route 192.2.5.0 255.255.255.0 null 0
B(config)# ip route 192.2.6.0 255.255.255.0 null 0
B(config)# ip route 192.2.7.0 255.255.255.0 null 0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 189

LECTURE NO. 23
26 Jan 2009
OSPF FILTERATION

Figure-23a
(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION ON ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown
A(config-if)# clock rate 64000

A(config)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION ON ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface ethernet 2/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

RUNNING OSPF-1 ON ROUTER-A

A(config)# router ospf 1
A(config-router)# network 1.0.0.0 0.255.255.255 area 0
A(config-router)# network 200.100.50.0 0.0.0.255 area 0

RUNNING OSPF-1 ON ROUTER-B

B(config)# router ospf 1
B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 190

ROUTING TABLE OF ROUTER-A & B

A# show ip route

B# show ip route

CREATING 16 STATIC ROUTES ON ROUTER-A

A(config)# ip route 192.1.0.0 255.255.255.0 null 0
A(config)# ip route 192.1.1.0 255.255.255.0 null 0
A(config)# ip route 192.1.2.0 255.255.255.0 null 0
A(config)# ip route 192.1.3.0 255.255.255.0 null 0
A(config)# ip route 192.1.4.0 255.255.255.0 null 0
A(config)# ip route 192.1.5.0 255.255.255.0 null 0
A(config)# ip route 192.1.6.0 255.255.255.0 null 0
A(config)# ip route 192.1.7.0 255.255.255.0 null 0
A(config)# ip route 192.1.8.0 255.255.255.0 null 0
A(config)# ip route 192.1.9.0 255.255.255.0 null 0
A(config)# ip route 192.1.10.0 255.255.255.0 null 0
A(config)# ip route 192.1.11.0 255.255.255.0 null 0
A(config)# ip route 192.1.12.0 255.255.255.0 null 0
A(config)# ip route 192.1.13.0 255.255.255.0 null 0
A(config)# ip route 192.1.14.0 255.255.255.0 null 0
A(config)# ip route 192.1.15.0 255.255.255.0 null 0

REDISTRIBUTION OF STATIC ROUTES INTO OSPF-1

A(config)# router ospf 1
A(config-router)# redistribute static subnets metric 20

ROUTING TABLE OF ROUTER-A & B

A# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 191

B# show ip route

FILTRATION METHOD #1 - (ROUTER-B)

PREPARING ACCESS-LIST FOR ODD NUMBERS STATIC ROUTES
B(config)# access-list 7 deny 192.1.1.0 0.0.14.0
B(config)# access-list 7 permit any

APPLYING FILTRATION USING ACCESS-LIST (INSIDE DIRECTION)

B(config)# router ospf 1
B(config)# distribute-list 7 in serial 1/0

Note: Here, we are applying filtration for static routes (which are
coming to Router-B) through its serial 1/0 interface.

B# show ip route

FILTRATION METHOD #2 - (ROUTER-A)

PREPARING ACCESS-LIST FOR ODD NUMBERS STATIC ROUTES
A(config)# access-list 7 deny 192.1.1.0 0.0.14.0
A(config)# access-list 7 permit any

APPLYING FILTRATION USING ACCESS-LIST (Outside Direction)

A(config)# router ospf 1
A(config-router)# distribute-list 7 out serial 1/0

NOTE: In OSPF, it is not possible to apply distribute-list command

onto a router from which the traffic is originating, e.g.
Router-A is generating static routes traffic, which we want to
block.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 192

FILTRATION FOR RIP & EIGRP

In OSPF, it is not possible to apply distribute-list command onto a router from
which the traffic is originating, but in RIP & EIGRP, it is possible to apply
distribute-list command on "IN" interface of a router which is receiving traffic
(e.g. Router-B) or on OUT interface of a router which is generating traffic (e.g.
Router-A).

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 193

LECTURE NO. 24
29 Jan 2009
IS-IS (INTERMEDIATE SYSTEM-TO-INTERMEDIATE SYSTEM)
In recent years, the IS-IS routing protocol has become increasingly popular, with
widespread usage among Service Providers. It is a link state protocol, which
enables very fast convergence with large scalability. It is also a very flexible
protocol and has been extended to incorporate leading edge features such as MPLS
Traffic Engineering.

The IS-IS routing protocol is a link-state protocol, as opposed to distance-vector

protocols such as Interior Gateway Routing Protocol (IGRP) and Routing Information
Protocol (RIP). Link-state offers several advantages over distance-vector
protocols. It is faster converging, supports much larger internetworks, and is less
susceptible to routing loops. Features of IS-IS include:

• Hierarchical routing
• Classless behavior
• Rapid flooding of new information
• Fast Convergence
• Very scalable
• Flexible timer tuning
• Cisco IOS implementation of multi-area routing
• Cisco IOS implementation of route-leaking
• Cisco IOS implementation of overload-bit

Intermediate System-to-Intermediate System (IS-IS) Protocol is an intradomain Open

System Interconnection (OSI) dynamic routing protocol specified in International
Organization for Standardization (ISO) 10589. The protocol is designed to operate
in OSI Connectionless Network Service (CLNS). Data is carried using the protocol
specified in ISO 8473.

A two-level hierarchy is used to support large routing domains. A large domain may
be administratively divided into areas. Each system resides in exactly one area.1
Routing within an area is referred to as Level 1 routing. A Level 1 IS keeps track
of the routing within its own area. Routing between areas is referred to as Level 2
routing. A Level 2 Intermediate System (IS) keeps track of the paths to destination
areas. For a packet destined for another area, a Level 1 IS sends the packet to the
nearest Level 2 IS in its own area, regardless of what the destination area is.
Then the packet travels via Level 2 routing to the destination area, where it may
travel via Level 1 routing to the destination. It should be noted that selecting an
exit from an area based on Level 1 routing to the closest Level 2 IS might result
in suboptimal routing.2

On broadcast multiaccess media (LAN), a Designated Intermediate System (DIS) is

elected and will conduct the flooding over the media. The DIS is analogous to the
designated router in Open Shortest Path First (OSPF) Protocol, even though the
details including election process and adjacencies within a multiaccess media
differ significantly.The DIS is elected by priority. The highest priority becomes
the DIS. This is configurable on an interface basis. In the case of a tie, the
router with the highest SNPA (MAC) address will become the DIS.

CLNS
OSI CLNS is a network layer service similar to bare IP service. A CLNS entity
communicates over Connectionless Network Protocol (CLNP) with its peer CLNS entity.

In the OSI architecture there are "systems": Routers are ISs, and hosts are End
Systems (ESs).
ESs themselves have no routing information; they discover ISs (routers) by
listening to Intermediate System Hellos (ISHs) and sending traffic to any random
router. ESs send End System Hellos (ESHs); they do not choose a designated router
to handle all traffic, and optimal routing is accomplished via redirects.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 194

ISs discover ESs by listening to ESHs, and ISs send ISHs to ESs.

There is no Address Resolution Protocol (ARP), Internet Control Message Protocol

(ICMP) or Interdomain Routing Protocol (IDRP) for CLNS, but End System-to-
Intermediate System (ES-IS) Protocol provides the same kind of reporting functions
for ISs and ESs. The ES-IS Protocol is defined in ISO 9542.

IS-IS is an Interior Gateway Protocol (IGP) for routing OSI. IS-IS packets are not
encapsulated in CLNS or IP but are encapsulated directly in the data-link layer.
The IS-IS protocol family is OSI, and values such as 0xFE and 0xFEFE are used by
the data-link protocol to identify the Layer 3 protocol as OSI.

INTEGRATED OR DUAL IS-IS

The IS-IS Routing Protocol may be used as an IGP to support IP as well as OSI. This
allows a single routing protocol to be used to support pure IP environments, pure
OSI environments, and dual environments. Integrated IS-IS is deployed extensively
in an IP-only environment in the top-tier Internet service provider (ISP) networks.
The IS-IS working group of the Internet Engineering Task Force (IETF) developed the
specification for Integrated IS-IS (RFC 1195).

Two primary methods are available for routing protocols to support dual OSI and IP
routers. One method, known as "Ships in the Night," makes use of completely
independent routing protocols for each of the two protocol suites. This
specification presents an alternative approach, which makes use of a single
integrated protocol for interior routing (that is, for calculating routes within a
routing domain) for both protocol suites.

By supporting both IP and OSI traffic, this integrated protocol design supports
traffic to IP hosts, OSI end systems, and dual end systems. The IS-IS Protocol can
be used to support pure-IP environments, pure-OSI environments, and dual
environments. IS-IS allows the interconnection of dual (IP and OSI) routing domains
with other dual domains, with IP-only domains, and with OSI-only domains.

IS-IS OPERATIONS
From a high level, IS-IS operates as follows:

• Routers running IS-IS will send hello packets out all IS-IS-enabled
interfaces to discover neighbors and establish adjacencies.
• Routers sharing a common data link will become IS-IS neighbors if their
hello packets contain information that meets the criteria for forming an
adjacency. The criteria differ slightly depending on the type of media being
used (p2p or broadcast). The main criteria are matching authentication, IS-
type and MTU size).
• Routers may build a link-state packet (LSP) based upon their local
interfaces that are configured for IS-IS and prefixes learned from other
adjacent routers.
• Generally, routers flood LSPs to all adjacent neighbors except the neighbor
from which they received the same LSP. However, there are different forms of
flooding and also a number of scenarios in which the flooding operation may
differ.
• All routers will construct their link-state database from these LSPs.
• A shortest-path tree (SPT) is calculated by each IS, and from this SPT the
routing table is built.

IS-IS DATA-FLOW DIAGRAM

In IS-IS, routers may have adjacencies with other routers on point-to-point links.
In a LAN environment, routers report their adjacencies to a Designated Intermediate
System (DIS), which generates an additional LSP, commonly known as the pseudonode
LSP. The DIS is responsible for conducting flooding over the LAN and also for
maintaining synchronization.
The flow of information within the IS-IS routing function is represented by the
IS-IS data-flow diagram (Figure-24a), which consists of four processes and a
Routing Information Base (RIB). The RIB consists of the link-state database and the

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 195

forwarding database. The four processes in the IS-IS data-flow diagram are:
receive, update, decision, and forward.

Figure-24a IS-IS Data-Flow Diagram

The receive process is the entry point for all data, including user data, error
reports, routing information, and control packets. It passes user data and error
reports to the forward process and passes routing information and control packets
(hellos, LSPs, and sequence number packets) to the update process.

The update process generates local link information that is flooded to adjacent
routers; in addition, the update process receives, processes, and forwards link
information received from adjacent routers. This process manages the Level 1 and
Level 2 link-state databases and floods Level 1 and Level 2 LSPs throughout an
area.

Each LSP that resides in the link-state database has a remaining lifetime, a
checksum, and a sequence number.

The LSP remaining lifetime counts down from 1200 seconds (20 minutes) to 0. The LSP
originator must periodically refresh its LSPs to prevent the remaining lifetime
from reaching 0. The refresh interval is 15 minutes, with a random jitter of up to
25 percent. If the remaining lifetime reaches 0, the expired LSP will be kept in
the database for an additional 60 seconds (known as ZeroAgeLifetime) before it is
purged.

If a router receives an LSP with an incorrect checksum, the router will cause a
purge of the LSP by setting the remaining lifetime value to 0, removing the body
and reflooding it. This triggers the LSP originator to send a new LSP. This
behavior is different from that of OSPF, where only the originating router can
purge an LSP. IS-IS can be configured so that LSPs with incorrect checksums are not
purged, but the router that originated the LSP will not know that the LSP was not
received.

The decision process runs shortest-path-first (SPF) algorithm on the link-state

database, and creates the forwarding database. It computes next-hop information and
computes sets of equal-cost paths, creating an adjacency set that is used for load
balancing. On a Cisco router, IS-IS supports load balancing over and up to six
equal-cost paths.
The forward process gets its input from the receive process and uses the forwarding
database to forward data packets toward their destination. It also redirects load
sharing and generates error reports.

AREAS AND THE ROUTING DOMAIN

An IS-IS routing domain is similar to a BGP autonomous system. A routing domain is
a collection of areas under an administration that implements routing policies
within the domain.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 196

BACKBONE
IS-IS does not have a backbone area like the OSPF area 0. The IS-IS backbone is a
contiguous collection of Level 2-capable routers, each of which can be in a
different area (Figure-24b).

Figure-24b IS-IS Backbone

AREAS
With IS-IS, an individual router is in only one area, and the border between areas
is on the link that connects two routers that are in different areas (Figure-24c).
This is in contrast to OSPF, in which the area borders are within the Area Border
Routers (ABRs) (Figure-24d). The reason for this difference is that an IS-IS router
generally has one network service access point (NSAP) address, and an IP router
generally has multiple IP addresses.

Figure-24c OSPF Areas: Area Borders are within Routers

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 197

Figure-24d IS-IS Areas: Area Borders are on links between Routers

IS-IS has a two-level hierarchy. Contiguous Level 2-capable routers form the
backbone. Both Level 2 and Level 1 routers live in areas. Routers can be Level 1
(L1), Level 2 (L2), or both (L1/L2). Within Cisco IOS® Software, the default
configuration is both Level 1 and Level 2 at the same time which allows an IS-IS
network to run with minimal configuration in a plug-and-play fashion. Level 2-
capable routers connect all areas within a routing domain. Level 2 routers
advertise their own area addresses (NSAP) to the other Level 2 routers in the
backbone. All Level 1 routers and hosts in an area must have an NSAP with the same
area address.

LEVEL-1 ROUTER
A Level 1 router knows the topology only of its own area and has Level 1 or
Level1/Level2 neighbors in this area. It has a Level 1 link-state database with all
the information for intra-area routing. It uses the closest Level 2-capable router
in its own area to send packets out of the area, a scenario that may result in
suboptimal routing.

Figure-24e provides an example of sub-optimal routing: The cost on all links is 10.
Router A (L1) in Area X will send all traffic destined for outside Area X to Router
B (L1/L2) because Router B is the closest L1/L2 neighbor. Router B is directly
connected to Area Y. Router C, also L1/L2, is in Area X and is directly connected
to Area Z. Router A will send packets destined for Area Z to Router B, and because
Router B, Router E, and Router C are backbone routers, Router B will send this
packet to Router C through Router E for delivery into Area Z. The more optimal path
would be for Router A to send the packet directly to Router C through Router D.

Figure-24e Example of Sub-optimal Routing

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 198

This mechanism is used to inform the Level 1 router about the closest Level 2-
capable router:

A Level 1/Level 2 router that is attached to another area will set the "attached
bit" in its Level 1 LSP; all the Level 1 ISs in an area will get a copy of this LSP
and know where to forward packets to destinations outside the area. If the routers
are running Integrated IS-IS, a default IP route will automatically be installed in
the Level 1 routers pointing toward the nearest Level 1/Level 2 router that
originally set the attached bit in its Level 1 LSP. A Level 1/Level 2 router that
is not attached to another area can also detect that a Level 2-only neighbor is
attached to another area and set the "attached bit" on behalf of this Level 2-only
neighbor.

If there is more than one point to exit the area (multiple Level 2-capable
routers), the closest Level 1/Level 2 router is selected based on the cost. If
there are two equal cost paths then the traffic may load balance over the two
paths.

LEVEL-2 ROUTER
A Level 2 router may have neighbors in the same or in different areas, and it has a
Level 2 link-state database with all information for inter-area routing. Level 2
routers know about other areas but will not have Level 1 information from its own
area. In the OSI world, a router must know the topology of its own area; so a Level
2 router should not be configured when only OSI traffic is being routed. If the
traffic in an area is IP-only, all the routers can be configured as Level 2.

LEVEL-1 / LEVEL-2 ROUTER

A Level 1/Level 2 router may have neighbors in any area. It has two link-state
databases: a Level 1 link-state database for intra-area routing and a Level 2 link-
state database for inter-area routing. A Level 1/Level 2 router runs two SPFs and
may require more memory and processing as a result.

A Level 1/Level 2 router running Integrated IS-IS will leak all the IP subnets from
Level 1 into Level 2; these subnets can be summarized where this is desirable.

When designing a network (see Figure-24f), care should be taken to choose the
correct setting, Level 1, Level 2, or Level 1/Level 2. When IS-IS is configured on
a Cisco router, the default setting is Level 1/Level 2.

All IS-IS areas are "stub" areas, although with Cisco IOS Software Release 12.0T,
it has become possible to leak Level 2 routes into Level 1, creating a sort of IS-
IS not-so-stubby area.

Figure-24f A simple network running IS-IS as a routing protocol

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 199

NSAP ADDRESSES
NSAP is the network-layer address for CLNS packets. An NSAP describes an attachment
to a particular service at the network layer of a node, similar to the combination
of IP destination address and IP protocol number in an IP packet. NSAP encoding and
format are specified by ISO 8348/Ad2.

ISO 8348/Ad2 uses the concept of hierarchical addressing domains. The global domain
is the highest level. This global domain is subdivided into sub-domains, and each
sub-domain is associated with an addressing authority that has a unique plan for
constructing NSAP addresses.

An NSAP address (Figure-24g) has two major parts: the initial domain part (IDP) and
the domain specific part (DSP) (Figure 7). The IDP consists of a 1-byte authority
and format identifier (AFI) and a variable-length initial domain identifier (IDI),
and the DSP is a string of digits identifying a particular transport implementation
of a specified AFI authority. Everything to the left of the system ID can be
thought of as the area address of a network node.

Figure-24g The NSAP address

A network entity title (NET) is an NSAP with an n-selector of zero. All router NETs
have an n-selector of zero, implying the network layer of the IS itself (0 means no
transport layer). For this reason, the NSAP of a router is always referred to as a
NET. The NSEL (NSAP selector) is like a TCP port number: It indicates the transport
layer.

Routers are identified with NETs of 8 to 20 bytes. ISO/IEC 10589 distinguishes only
three fields in the NSAP address format: a variable-length area address beginning
with a single octet, a system ID, and a 1-byte n-selector. Cisco implements a fixed
length of 6 bytes for the system ID, which is like the OSPF router ID.

The LSP identifier is derived from the system ID (along with the pseudonode ID and
LSP number). Each IS is usually configured with one NET and in one area; each
system ID within an area must be unique.

The big difference between NSAP style addressing and IP style addressing is that,
in general, there will be a single NSAP address for the entire router, whereas with
IP there will be one IP address per interface. All ISs and ESs in a routing domain
must have system IDs of the same length. All routers in an area must have the same
area address. All Level 2 routers must have a unique system ID domain-wide, and all
Level 1 routers must have a unique system ID area-wide. All ESs in an area will
form an adjacency with a Level 1 router on a shared media segment if they share the
same area address. If multiple NETs are configured on the same router, they must
all have the same system ID.

There are several techniques for creating unique system IDs:

• Start numbering 1, 2, 3, 4, and so on.

• Use Media Access Control (MAC) addresses.
• Convert and use the loopback IP address:
192.168.11.1 --> 192.168.011.001--> 1921.6801.1001.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 200

The practice of using a modified loopback IP address as the system ID may now be
considered outdated because of the dynamic hostname feature. This feature uses a
new Type Length Value (TLV 137) to map the router's hostname to the system ID.

Three NSAP formats are illustrated in Figure-24g. The first is a simple 8-octet
area ID/system ID format. The second is an OSI NSAP format, and the third is a
Government OSI Profile (GOSIP) NSAP format.

Figure-24h Three NSAP Formats

If an official prefix is not required, you can use AFI 49, which denotes private
address space, like IP address space for private Internets as defined in RFC 1918.

The AFI has a binary value between 0 and 99; this value specifies the IDI format
and the DSP syntax. The DSP is in binary format, and the IDP is in decimal. ISO
recognizes seven top-level network addressing authorities; each authority has its
own addressing format represented by the IDI format field.

Cisco technology supports all NSAP formats that are defined by ISO 8348/Ad2.

It is possible to configure multiple NETs on a router, but no router is ever in

more than one area. Configuring multiple NETs causes the areas to merge into a
common area, leaking the Level 1 databases into each other. The only reasons to
have multiple NETs are for splitting, merging, or renumbering areas; this method
should only be used in periods of transition. Cisco Systems limits the number of
configurable NETs to three per router.

METRICS
The original IS-IS specification defines four different types of metrics. Cost,
being the default metric, is supported by all routers. Delay, expense, and error
are optional metrics. The delay metric measures transit delay, the expense metric
measures the monetary cost of link utilization, and the error metric measures the
residual error probability associated with a link.

The Cisco implementation uses cost only. If the optional metrics were implemented,
there would be a link-state database for each metric and SPF would be run for each
link-state database.

DEFAULT METRIC
While some routing protocols calculate the link metric automatically based on
bandwidth (OSPF) or bandwidth/delay (Enhanced Interior Gateway Routing Protocol
[EIGRP]), there is no automatic calculation for IS-IS. Using old-style metrics, an
interface cost is between 1 and 63 (6 bit metric value). All links use the metric

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 201

of 10 by default. The total cost to a destination is the sum of the costs on all
outgoing interfaces along a particular path from the source to the destination, and
the least-cost paths are preferred.

The total path metric was limited to 1023 (the sum of all link metrics along a path
between the calculating router and any other node or prefix). This small metric
value proved insufficient for large networks and provided too little granularity
for new features such as Traffic Engineering and other applications, especially
with high bandwidth links. Wide metrics are also required if route-leaking is used.

EXTENDED METRIC
Cisco IOS Software addresses this issue with the support of a 24-bit metric field,
the so-called "wide metric". Using the new metric style, link metrics now have a
maximum value of 16777215 (224-1) with a total path metric of 4261412864 (254 x
224).

Deploying IS-IS in the IP network with wide metrics is recommended to enable finer
granularity and to support future applications such as Traffic Engineering.

Running different metric styles within one network poses one serious problem: Link-
state protocols calculate loop-free routes because all routers (within one area)
calculate their routing table based on the same link-state database. This principle
is violated if some routers look at old-style (narrow), and some at new-style
(wider) TLVs. However, if the same interface cost is used for both the old- and
new-style metrics, then the SPF will compute a loop-free topology.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 202

LECTURE NO. 25
31 Jan 2009
IS-IS (LAB #1)

Figure-25a

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config-if)# interface fastethernet 0/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config-if)# interface fastethernet 0/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.0.0.1 255.0.0.0
C(config-if)# no shutdown

C(config-if)# interface fastethernet 0/0

C(config-if)# ip address 200.100.150.1 255.255.255.0
C(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 203

BASIC CONFIGURATION OF ROUTER-D

D(config)# interface serial 1/0
D(config-if)# ip address 3.0.0.2 255.0.0.0
D(config-if)# no shutdown
D(config-if)# clock rate 64000

D(config-if)# interface fastethernet 0/0

D(config-if)# ip address 200.100.200.1 255.255.255.0
D(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

B# show ip route

C# show ip route

D# show ip route

SETTING NET ADDRESS ON ROUTER-A,B,C & D

A(config)# router isis
A(config-router)# net 47.0001.0000.0000.000a.00

Area-ID System-ID Selector-Byte

B(config)# router isis

B(config-router)# net 47.0001.0000.0000.000b.00

C(config)# router isis

C(config-router)# net 47.0002.0000.0000.000c.00

D(config)# router isis

D(config-router)# net 47.0002.0000.0000.000d.00

ENABLING IS-IS ON ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip router isis

A(config)# interface fastethernet 0/0

A(config-if)# ip router isis

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 204

ENABLING IS-IS ON ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip router isis

B(config)# interface serial 1/1

B(config-if)# ip router isis

B(config)# interface fastethernet 0/0

B(config-if)# ip router isis

ENABLING IS-IS ON ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip router isis

C(config)# interface serial 1/0

C(config-if)# ip router isis

C(config)# interface fastethernet 0/0

C(config-if)# ip router isis

ENABLING IS-IS ON ROUTER-D

D(config)# interface serial 1/0
D(config-if)# ip router isis

D(config)# interface fastethernet 0/0

D(config-if)# ip router isis

VERIFICATION
B# show clns is-neighbor

B# show isis neighbor

B# show isis database

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 205

B# show clns interface

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 206

C# show ip route

D# show ip route

NOTE: Default metric of IS-IS is 10

CHANGING CIRCUIT-TYPE OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# isis circuit-type level-1

B(config)# interface serial 1/1

B(config-if)# isis circuit-type level-2

CHANGING CIRCUIT-TYPE OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# isis circuit-type level-2

C(config)# interface serial 1/0

C(config-if)# isis circuit-type level-1

CHANGING CIRCUIT-TYPE OF ROUTER-A

(FOR COMPLETE ROUTER)

A(config)# router isis

A(config-if)# is-type level-1

NOTE: Since all interfaces of Router-A are in Level-1, so we can

apply this command, which will convert all interfaces of
Router-A into Level-1.

CHANGING CIRCUIT-TYPE OF ROUTER-D

(FOR COMPLETE ROUTER)

D(config)# router isis

D(config-if)# is-type level-1

NOTE: Since all interfaces of Router-D are in Level-1, so we can

apply this command, which will convert all interfaces of
Router-D into Level-1.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 207

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

B# show ip route

C# show ip route

D# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 208

COMPLEMENTARY LECTURE NO. 3

06 Jun 2009
IS-IS (LAB #2)

(Note: Lab results are produced using GNS3 simulator)

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.1.1.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown

A(config)# interface serial 1/1

A(config-if)# ip address 3.1.1.2 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown

A(config-if)# interface loopback 0

A(config-if)# ip address 11.1.1.1 255.0.0.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/1
B(config-if)# ip address 1.1.1.2 255.0.0.0
B(config-if)# no shutdown

B(config)# interface serial 1/0

B(config-if)# ip address 2.1.1.1 255.0.0.0
B(config-if)# clock rate 64000
B(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 209

B(config-if)# interface loopback 0

B(config-if)# ip address 22.2.2.2 255.0.0.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.1.1.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.1.1.1 255.0.0.0
C(config-if)# no shutdown

C(config-if)# interface loopback 0

C(config-if)# ip address 33.3.3.3 255.0.0.0
C(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A, B, C & D

A# show ip route

B# show ip route

C# show ip route

ISIS CONFIGURATION OF ROUTER-A

A(config)# router isis
A(config-router)# net 49.2007.0000.0000.0001.00

Network Entity Title Area-ID System-ID Network Selector-Byte (NSEL)

A(config-router)# exit

A(config)# interface serial 1/0

A(config-if)# ip router isis
A(config-if)# isis circuit-type level-1
A(config-if)# exit

A(config)# interface serial 1/1

A(config-if)# ip router isis
A(config-if)# isis circuit-type level-2
A(config-if)# exit

A(config)# interface loopback 0

A(config-if)# ip router isis
A(config-if)# exit

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 210

ISIS CONFIGURATION OF ROUTER-B

B(config)# router isis
B(config-router)# net 49.2007.0000.0000.0002.00
B(config-router)# exit

B(config)# interface serial 1/1

B(config-if)# ip router isis
B(config-if)# isis circuit-type level-1
B(config-if)# exit

B(config)# interface serial 1/0

B(config-if)# ip router isis
B(config-if)# isis circuit-type level-2
B(config-if)# exit

B(config)# interface loopback 0

B(config-if)# ip router isis
B(config-if)# exit

ISIS CONFIGURATION OF ROUTER-C

C(config)# router isis
C(config-router)# net 49.3007.0000.0000.0003.00
C(config-router)# exit

C(config)# interface serial 1/1

C(config-if)# ip router isis
C(config-if)# isis circuit-type level-2
C(config-if)# exit

C(config)# interface serial 1/0

C(config-if)# ip router isis
C(config-if)# isis circuit-type level-2
C(config-if)# exit

C(config)# interface loopback 0

C(config-if)# ip router isis
C(config-if)# exit

VERIFICATION
C# show isis neighbor

C# show isis database

C# show isis hostname

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 211

C# show isis topology

C# show clns is-neighbor

C# show clns interface

C# show clns cache

C# show clns neighbors

C# show clns route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 212

C# show clns protocol

ROUTING TABLE OF ROUTER-A, B & C

A# show ip route

B# show ip route

C# show ip route

NOTE: Default metric of IS-IS is 10

EFFECT OF CHANGING METRIC VALUE OF INTERFACE LOOPBACK 0

OF ROUTER-A
A(config)# interface loopback 0
A(config-if)# isis metric 50 level-2

C# show ip route

NOTE: We have set the metric value 50 of loopback interface 0 on

Router-A for ISIS Level-2. Currently, it is reaching on
Router-C with a metric value of 30. Let’s see, why it is
reaching on Router-C with a metric value of 30.

i. Default metric of loopback interface 0 (network

11.0.0.0.) on Router-A is 10 (in ISIS
environment).

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 213

ii. There are two paths for network 11.0.0.0 to reach

on Router-C:

a. A Æ C

b. A Æ B Æ C.

iii. When it goes through Level-2 (A Æ C) for

approaching to Router-C, it adds 50 in its metric
value, which comes to a total of 60.

iv. When it goes through Level-1 (A Æ B) for

approaching to Router-B, it adds 10 in its metric
value, which comes to a total of 20 and again when
it goes through Level-2 (B Æ C) for approaching
to Router-C, it adds 10 in its metric value, which
comes to a total of 30.

v. Since, 30 it a lower metric value than 60,

therefore, it goes through A Æ B Æ C and
approaches to Router-C with metric 30

SHUTTING DOWN INTERFACE SERIAL 1/0 OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# shutdown

C# show ip route

NOTE: After shutting down interface serial 1/0 of Router-A, there is

only one path available for network 11.0.0.0 to reach on
Router-C, which is A Æ C.

Default metric of loopback interface 0 - 10

on Router-A (in ISIS environment)

Metric value for the Level-2 (A Æ C) - 50

Therefore, it is reaching on Router-C with a metric value of

60.

REMOVING ABOVE CONFIGURATION FROM INTERFACE SERIAL 1/0

AND LOOPBACK 0 OF ROUTER-A
A(config)# interface serial 1/0
A(config-if)# no shutdown
A(config-if)# exit

A(config)# interface loopback 0

A(config-if)# no isis metric 50 level-2

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 214

HOW TO REDISTRIBUTE STATIC ROUTE INTO ISIS

A(config)# ip route 192.1.17.0 255.255.255.0 null 0

A(config)# router isis

A(config-router)# redistribute static metric 10 level 2

C# show ip route

NOTE: Static router of Router-A has been redistributed reached on

Router-C with metric 20, using the path A Æ C.

ROUTE LEAKING
Let’s see, what happens, when the interface serial 1/1 of Router-A (L2 to L2 link)
or interface serial 1/0 of Router-B (L2 to L2 link) goes to down state.

A# show ip route

A(config)# interface serial 1/1

A(config-if)# shutdown

A# show ip route

NOTE: Level-2 routes 2.0.0.0 & 3.0.0.0 are not found on Router-A but
a default route 0.0.0.0 is injected.

A(config)# interface serial 1/1

A(config-if)# no shutdown
A(config-if)# exit

A# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 215

Following configuration is strongly recommended, if there is any possibility that

any link could go to down state.

CREATING ACCESS-LIST AND REDISTRIBUTING ISIS LEVEL-2 INTO

LEVEL-1 (ROUTER-A)
A(config)# access-list 101 permit ip any any
A(config)# router isis
A(config-router)# redistribute isis ip level-2 into level-1 distribute-list 101

CREATING ACCESS-LIST AND REDISTRIBUTING ISIS LEVEL-2 INTO

LEVEL-1 (ROUTER-A)
B(config)# access-list 101 permit ip any any
B(config)# router isis
B(config-router)# redistribute isis ip level-2 into level-1 distribute-list 101

VERIFICATION
A# show ip route

A(config)# interface serial 1/1

A(config-if)# shutdown

A# show ip route

NOTE: After shutting down interface serial 1/1 of Router-A, Level-2

routes 2.0.0.0 & 33.0.0.0 are reaching on Router-A Level-1
path.

HOW TO REMOVE DEFAULT ROUTE FROM THE ROUTING TABLE OF

ROUTER-A
A# show isis database

NOTE: In order to flush out default route 0.0.0.0 from the routing
table of Router-A, we have to set the value of ATTACHMENT-BIT
to zero.

To do the needful, apply the configuration on next page.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 216

ROUTER-A
A(config)# clns filter-set shakeel deny 49.3007 shakeel = label name
A(config)# route-map haroon permit 10 haroon = label name

A(config-route-map)# match clns address shakeel

A(config-route-map)# exit

A(config)# router isis

A(config-router)# set-attached-bit route-map haroon

ROUTER-B
B# show isis database

B(config)# clns filter-set lahore deny 49.3007 lahore = label name

B(config)# route-map pakistan permit 11 pakistan = label name

B(config-route-map)# match clns address lahore

B(config-route-map)# exit

B(config)# router isis

B(config-router)# set-attached-bit route-map pakistan

VERIFICATION
A# show ip route

NOTE: Default route 0.0.0.0 has been flush out from the routing table
of Router-A.

A# show isis database

B# show isis database

NOTE: The value ATTACHMENT-BIT has been set to zero on Router-A & B.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 217

LECTURE NO. 26
03 Feb 2009
MULTICASTING
http://tools.ietf.org/id/draft-ietf-mboned-intro-multicast-01.txt

INTRODUCTION TO MULTICAST:
There are three fundamental types of IPv4
addresses: unicast, broadcast, and multicast. A
unicast address is used to transmit a packet to a
single destination. A broadcast address is used
to send a datagram to an entire subnetwork. A
multicast address is designed to enable the
delivery of datagrams to a set of hosts that have
been configured as members of a multicast group
across various subnetworks.

Multicasting is not connection-oriented. A

multicast datagram is delivered to
destination group members with the same
"best-effort" reliability as a standard
unicast IP datagram. This means that
multicast datagrams are not guaranteed to
reach all members of a group, nor to
arrive in the same order in which they
were transmitted.

The only difference between a multicast IP

packet and a unicast IP packet is the
presence of a 'group address' in the
Destination Address field of the IP
header. Instead of a Class A, B, or C IP
destination address, multicasting employs
a Class-D address format, which ranges
from 224.0.0.0 to 239.255.255.255.

MULTICAST GROUPS:
Individual hosts are free to join or leave a multicast group at any time.
There are no restrictions on the physical location or the number of members
in a multicast group. A host may be a member of more than one multicast
group at any given time and does not have to belong to a group to send
packets to members of a group.

GROUP MEMBERSHIP PROTOCOL:

A group membership protocol is employed by routers to learn about the
presence of group members on their directly attached subnetworks. When a
host joins a multicast group, it transmits a group membership protocol
message for the group(s) that it wishes to receive, and sets its IP process
and network interface card to receive frames addressed to the multicast
group. This receiver-initiated join process has excellent scaling
properties since, as the multicast group increases in size, it becomes ever

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 218

more likely that a new group member will be able to locate a nearby branch
of the multicast delivery tree.

THE INTERNET's MULTICAST BACKBONE (MBone):

The Internet Multicast Backbone (MBone) is an interconnected set of
subnetworks and routers that support the delivery of IP multicast traffic.
The goal of the MBone is to construct a semipermanent IP multicast testbed
to enable the deployment of multicast applications without waiting for the
ubiquitous deployment of multicast-capable routers in the Internet.

The MBone has grown from 40 subnets in four different countries in 1992, to
more than 3400 subnets in over 25 countries by March 1997. With new
multicast applications and multicast-based services appearing, it seems
likely that the use of multicast technology in the Internet will keep
growing at an ever-increasing rate.

The MBone is a virtual network that is layered on top of sections of the

physical Internet. It is composed of islands of multicast routing
capability connected to other islands by virtual point-to-point links
called "tunnels." The tunnels allow multicast traffic to pass through the
non-multicast-capable parts of the Internet. Tunneled IP multicast packets
are encapsulated as IP-over-IP (i.e., the protocol number is set to 4) so
they look like normal unicast packets to intervening routers. The
encapsulation is added on entry to a tunnel and stripped off on exit from a
tunnel. This set of multicast routers, their directly-connected
subnetworks, and the interconnecting tunnels comprise the MBone.

Since the MBone and the Internet have different topologies, multicast
routers execute a separate routing protocol to decide how to forward
multicast packets. The majority of the MBone routers currently use the
Distance Vector Multicast Routing Protocol (DVMRP), although some portions
of the MBone execute either Multicast OSPF (MOSPF) or the Protocol-
Independent Multicast (PIM) routing protocols. The operation of each of
these protocols is discussed later in this paper.

INTERNET GROUP MANAGEMENT PROTOCOL (IGMP):

The Internet Group Management Protocol (IGMP) runs between hosts and their
immediately-neighboring multicast routers. The mechanisms of the protocol
allow a host to inform its local router that it wishes to receive
transmissions addressed to a specific multicast group. Also, routers
periodically query the LAN to determine if any group members are still
active. If there is more than one IP multicast router on the LAN, one of
the routers is elected "querier" and assumes the responsibility of querying
the LAN for the presence of any group members.

Based on the group membership information learned from the IGMP, a router
is able to determine which (if any) multicast traffic needs to be forwarded
to each of its "leaf" subnetworks. Multicast routers use this information,
in conjunction with a multicast routing protocol, to support IP
multicasting across the Internet.

Distance Vector Multicast Routing Protocol (DVMRP):

The Distance Vector Multicast Routing Protocol (DVMRP) is a distance-
vector routing protocol designed to support the forwarding of multicast
datagrams through an internetwork. DVMRP constructs source-based multicast
delivery trees using the Reverse Path Multicasting (RPM) algorithm.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 219

Originally, the entire MBone ran only DVMRP. Today, over half of the MBone
routers still run some version of DVMRP.

DVMRP was first defined in RFC-1075. The original specification was derived
from the Routing Information Protocol (RIP) and employed the Truncated
Reverse Path Broadcasting (TRPB) technique. The major difference between
RIP and DVMRP is that RIP calculates the next-hop toward a destination,
while DVMRP computes the previous-hop back toward a source. Since mrouted
3.0, DVMRP has employed the Reverse Path Multicasting (RPM) algorithm.
Thus, the latest implementations of DVMRP are quite different from the
original RFC specification in many regards. There is an active effort
within the IETF Inter-Domain Multicast Routing (IDMR) working group to
specify DVMRP version 3 in a standard form.

Multicast Extensions to OSPF (MOSPF):

Version 2 of the Open Shortest Path First (OSPF) routing protocol is
defined in RFC-1583. OSPF is an Interior Gateway Protocol (IGP) that
distributes unicast topology information among routers belonging to a
single OSPF "Autonomous System." OSPF is based on link-state algorithms
which permit rapid route calculation with a minimum of routing protocol
traffic. In addition to efficient route calculation, OSPF is an open
standard that supports hierarchical routing, load balancing, and the import
of external routing information.

The Multicast Extensions to OSPF (MOSPF) are defined in RFC-1584. MOSPF

routers maintain a current image of the network topology through the
unicast OSPF link-state routing protocol. The multicast extensions to OSPF
are built on top of OSPF Version 2 so that a multicast routing capability
can be incrementally introduced into an OSPF Version 2 routing domain.
Routers running MOSPF will interoperate with non-MOSPF routers when
forwarding unicast IP data traffic. MOSPF does not support tunnels.

Protocol-Independent Multicast (PIM):

The Protocol Independent Multicast (PIM) routing protocols have been
developed by the Inter-Domain Multicast Routing (IDMR) working group of the
IETF. The objective of the IDMR working group is to develop one—or possibly
more than one--standards-track multicast routing protocol(s) that can
provide scaleable multicast routing across the Internet.

PIM is actually two protocols: PIM - Dense Mode (PIM-DM) and PIM - Sparse
Mode (PIM-SM). In the remainder of this introduction, any references to
"PIM" apply equally well to either of the two protocols... there is no
intention to imply that there is only one PIM protocol. While PIM-DM and
PIM-SM share part of their names, and they do have related control
messages, they are actually two completely independent protocols.

PIM receives its name because it is not dependent on the mechanisms

provided by any particular unicast routing protocol. However, any
implementation supporting PIM requires the presence of a unicast routing
protocol to provide routing table information and to adapt to topology
changes.

PIM makes a clear distinction between a multicast routing protocol that is

designed for dense environments and one that is designed for sparse
environments. Dense-mode refers to a protocol that is designed to operate
in an environment where group members are relatively densely packed and
bandwidth is plentiful. Sparse-mode refers to a protocol that is optimized
for environments where group members are distributed across many regions of
the Internet and bandwidth is not necessarily widely available. It is

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 220

important to note that sparse-mode does not imply that the group has a few
members, just that they are widely dispersed across the Internet.

The designers of PIM-SM argue that DVMRP and MOSPF were developed for
environments where group members are densely distributed, and bandwidth is
relatively plentiful. They emphasize that when group members and senders
are sparsely distributed across a wide area, DVMRP and MOSPF do not provide
the most efficient multicast delivery service. The DVMRP periodically
sends multicast packets over many links that do not lead to group members,
while MOSPF can send group membership information over links that do not
lead to senders or receivers.

PIM - Dense Mode (PIM-DM):

While the PIM architecture was driven by the need to provide scaleable
sparse-mode delivery trees, PIM also defines a new dense-mode protocol
instead of relying on existing dense-mode protocols such as DVMRP and
MOSPF. It is envisioned that PIM-DM would be deployed in resource rich
environments, such as a campus LAN where group membership is relatively
dense and bandwidth is likely to be readily available. PIM-DM's control
messages are similar to PIM-SM's by design.

PIM - Dense Mode (PIM-DM) is similar to DVMRP in that it employs the

Reverse Path Multicasting (RPM) algorithm. However, there are several
important differences between PIM-DM and DVMRP:

• To find routes back to sources, PIM-DM relies on the presence

of an existing unicast routing table. PIM-DM is independent of
the mechanisms of any specific unicast routing protocol. In
contrast, DVMRP contains an integrated routing protocol that
makes use of its own RIP-like exchanges to build its own unicast
routing table (so a router may orient itself with respect to
active source(s)). MOSPF augments the information in the OSPF
link state database, thus MOSPF must run in conjunction with
OSPF.

• Unlike the DVMRP which calculates a set of child interfaces for

each (source, group) pair, PIM-DM simply forwards multicast
traffic on all downstream interfaces until explicit prune
messages are received. PIM-DM is willing to accept packet
duplication to eliminate routing protocol dependencies and to
avoid the overhead inherent in determining the parent/child
relationships.

For those cases where group members suddenly appear on a pruned branch of
the delivery tree, PIM-DM, like DVMRP, employs graft messages to re-attach
the previously pruned branch to the delivery tree.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 221

Figure-26a

"SPARSE MODE" ROUTING PROTOCOLS:

The most recent additions to the set of multicast routing protocols are
called "sparse mode" protocols. They are designed from a different
perspective than the "dense mode" protocols that we have already examined.
Often, they are not data-driven, in the sense that forwarding state is set
up in advance, and they trade off using bandwidth liberally (which is a
valid thing to do in a campus LAN environment) for other techniques that
are much more suited to scaling over large WANs, where bandwidth is scarce
and expensive.

These emerging routing protocols include:

• Protocol Independent Multicast - Sparse Mode (PIM-SM), and

• Core-Based Trees (CBT).

While these routing protocols are designed to operate efficiently over a

wide area network where bandwidth is scarce and group members may be quite
sparsely distributed, this is not to imply that they are only suitable for
small groups. Sparse doesn't mean small, rather it is meant to convey that
the groups are widely dispersed, and thus it is wasteful to (for instance)
flood their data periodically across the entire internetwork.

Protocol-Independent Multicast - Sparse Mode (PIM-SM):

As described previously, PIM also defines a "dense-mode" or source-based
tree variant. Again, the two protocols are quite unique, and other than
control messages, they have very little in common. Note that while PIM
integrates control message processing and data packet forwarding among PIM-
Sparse and -Dense Modes, PIM-SM and PIM-DM must run in separate regions.
All groups in a region are either sparse-mode or dense-mode.

PIM-Sparse Mode (PIM-SM) has been developed to provide a multicast routing

protocol that provides efficient communication between members of sparsely
distributed groups--the type of groups that are likely to be common in
wide-area internetworks. PIM's designers observed that several hosts

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 222

wishing to participate in a multicast conference do not justify flooding

the entire internetwork periodically with the group's multicast traffic.

Noting today's existing MBone scaling problems, and extrapolating to a

future of ubiquitous multicast (overlaid with perhaps thousands of small,
widely dispersed groups), it is not hard to imagine that existing multicast
routing protocols will experience scaling problems. To eliminate these
potential scaling issues, PIM-SM is designed to limit multicast traffic so
that only those routers interested in receiving traffic for a particular
group "see" it. PIM-SM differs from existing dense-mode protocols in two
key ways:

• Routers with adjacent or downstream members are required to

explicitly join a sparse mode delivery tree by transmitting join
messages. If a router does not join the pre-defined delivery tree,
it will not receive multicast traffic addressed to the group.
In contrast, dense-mode protocols assume downstream group
membership and forward multicast traffic on downstream links until
explicit prune messages are received. Thus, the default forwarding
action of dense-mode routing protocols is to forward all traffic,
while the default action of a sparse-mode protocol is to block
traffic unless it has been explicitly requested.

• PIM-SM evolved from the Core-Based Trees (CBT) approach in that

it employs the concept of a "core" (or rendezvous point (RP) in
PIM-SM terminology) where receivers "meet" sources.

Figure-26b

When joining a group, each receiver uses IGMP to notify its directly-
attached router, which in turn joins the multicast delivery tree by sending

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 223

an explicit PIM-Join message hop-by-hop toward the group's RP. A source

uses the RP to announce its presence, and act as a conduit to members that
have joined the group. This model requires sparse-mode routers to maintain
a bit of state (the RP-set for the sparse-mode region) prior to the arrival
of data. In contrast, because dense-mode protocols are data-driven, they
do not store any state for a group until the arrival of its first data
packet.

There is only one RP-set per sparse-mode domain, not per group. Moreover,
the creator of a group is not involved in RP selection. Also, there is no
such concept as a "primary" RP. Each group has precisely one RP at any
given time. In the event of the failure of an RP, a new RP-set is
distributed which does not include the failed RP.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 224

LECTURE NO. 27
07 Feb 2009
MULTICASTING
BASIC CONFIGURATION OF ROUTER-A
A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# no shutdown

A(config-if)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.0.0.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.0.0.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config-if)# interface ethernet 2/0

B(config-if)# ip address 200.100.100.1 255.0.0.0
B(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.0.0.2 255.0.0.0
C(config-if)# no shutdown

C(config-if)# interface ethernet 2/0

C(config-if)# ip address 200.100.150.1 255.0.0.0
C(config-if)# no shutdown

ROUTING TABLE OF ROUTER-A, B & C

A# show ip route

B# show ip route

C# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 225

RUNNING RIP ON ROUTER-A, B & C

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 200.100.50.0

B(config)# router rip

B(config-router)# network 1.0.0.0
B(config-router)# network 2.0.0.0
B(config-router)# network 200.100.100.0

C(config)# router rip

C(config-router)# network 2.0.0.0
C(config-router)# network 200.100.150.0

DENSE-MODE

Figure-27a

Step-1. ENABLING MULTICASTING ON ROUTER-A,B,& C

A(config)# ip multicast-routing

B(config)# ip multicast-routing

C(config)# ip multicast-routing

Step-2. JOINING GROUP

C(config)# interface ethernet 2/0
C(config-if)# ip igmp join-group 225.1.1.1

NOTE: Here, we are not using a computer to join a

group, but we are going to join a group
225.1.1.1 using Ethernet interface of
Router-C.

Step-3. USING PING COMMAND ON ROUTER-A

NOTE: This command will automatically convert

Router-A into Server.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 226

Step-4. RUNNING DENSE-MODE ON ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip pim dense-mode

A(config)# interface ethernet 2/0

A(config-if)# ip pim dense-mode

Step-5. RUNNING DENSE-MODE ON ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip pim dense-mode

B(config)# interface serial 1/1

B(config-if)# ip pim dense-mode

B(config)# interface ethernet 2/0

B(config-if)# ip pim dense-mode

Step-6. RUNNING DENSE-MODE ON ROUTER-C

C(config)# interface serial 1/0
C(config-if)# ip pim dense-mode

C(config)# interface ethernet 2/0

C(config-if)# ip pim dense-mode

Step-7. VERIFYING NEIGHBOR

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 227

SPARSE-MODE (STATIC-RP)

Figure-27b

NOTE: Use the same basic and RIP configuration as mentioned above.

Step-1. Same as mentioned in DENSE-MODE.

Step-2. Same as mentioned in DENSE-MODE.

Step-3. Same as mentioned in DENSE-MODE.

Step-4. CREATING LOOPBACK INTERFACE ON ROUTER-B

B(config)# interface loopback 0
B(config-if)# ip address 22.2.2.2 255.0.0.0

Step-5. RUNNING RIP AT LOOPBACK INTERFACE-0 of Router-B

B(config)# router rip
B(config-router)# network 22.0.0.0

Step-6. RUNNING SPARSE-MODE ON ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip pim sparse-mode

A(config)# interface ethernet 2/0

A(config-if)# ip pim sparse-mode

Step-7. RUNNING SPARSE-MODE ON ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip pim sparse-mode

B(config)# interface serial 1/1

B(config-if)# ip pim sparse-mode

B(config)# interface ethernet 2/0

B(config-if)# ip pim sparse-mode

B(config)# interface loopback 0

B(config-if)# ip pim sparse-mode

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 228

Step-8. RUNNING SPARSE-MODE ON ROUTER-C

C(config)# interface serial 1/0
C(config-if)# ip pim sparse-mode

C(config)# interface ethernet 2/0

C(config-if)# ip pim sparse-mode

Step-9. SETTING RP-ADDRESS ON ROUTER-A, B & C

A(config)# ip pim rp-address 22.2.2.2

B(config)# ip pim rp-address 22.2.2.2

C(config)# ip pim rp-address 22.2.2.2

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 229

SPARSE-MODE (AUTO-RP)

Figure-27c

NOTE: Use the same basic and RIP configuration as mentioned above.

Step-1. Same as mentioned in SPARSE-MODE.

Step-2. Same as mentioned in SPARSE-MODE.

Step-3. Same as mentioned in SPARSE-MODE.

Step-4. Same as mentioned in SPARSE-MODE.

Step-5. Same as mentioned in SPARSE-MODE.

Step-6. CREATING LOOPBACK INTERFACE ON ROUTER-C

C(config)# interface loopback 0
C(config-if)# ip address 33.3.3.3 255.0.0.0

Step-7. RUNNING RIP AT LOOPBACK INTERFACE-0 of Router-C

C(config)# router rip
C(config-router)# network 33.3.3.3

Step-8. RUNNING SPARSE-DENSE-MODE ON ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip pim sparse-dense-mode

A(config)# interface thernet 2/0

A(config-if)# ip pim sparse-dense-mode

Step-9. RUNNING SPARSE-DENSE-MODE ON ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip pim sparse-dense-mode

B(config)# interface serial 1/1

B(config-if)# ip pim sparse-dense-mode
B(config)# interface thernet 2/0
B(config-if)# ip pim sparse-dense-mode

B(config)# interface loopback 0

B(config-if)# ip pim sparse-dense-mode

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 230

Step-10. RUNNING SPARSE-MODE ON ROUTER-C

C(config)# interface serial 1/0
C(config-if)# ip pim sparse-dense-mode

C(config)# interface thernet 2/0

C(config-if)# ip pim sparse-dense-mode

C(config)# interface loopback 0

C(config-if)# ip pim sparse-dense-mode

Step-11. SETTING RP-ANNOUNCE ON ROUTER-B

B(config)# ip pim send-rp-announce Loopback 0 scope 15

Step-11. SETTING RP-DISCOVERY ON ROUTER-C

C(config)# ip pim send-rp-discovery Loopback 0 scope 15

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 231

LECTURE NO. 28
09 Feb 2009
BGP (BORDER GATWAY PROTOCOL)
BGP is a Policy Based Routing Protocol and works on Port No. 179 of TCP.

Figure-28a

Source: www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/bgp.htm

INTRODUCTION
The Border Gateway Protocol (BGP) is an interautonomous system routing protocol. An
autonomous system is a network or group of networks under a common administration
and with common routing policies. BGP is used to exchange routing information for
the Internet and is the protocol used between Internet service providers (ISP).
Customer networks, such as universities and corporations, usually employ an
Interior Gateway Protocol (IGP) such as RIP or OSPF for the exchange of routing
information within their networks. Customers connect to ISPs, and ISPs use BGP to
exchange customer and ISP routes. When BGP is used between autonomous systems (AS),
the protocol is referred to as External BGP (EBGP). If a service provider is using
BGP to exchange routes within an AS, then the protocol is referred to as Interior
BGP (IBGP). Figure 28-b illustrates this distinction.

Figure 28-b (External and Interior BGP)

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 232

BGP is a very robust and scalable routing protocol, as evidenced by the fact that
BGP is the routing protocol employed on the Internet. At the time of this writing,
the Internet BGP routing tables number more than 90,000 routes. To achieve
scalability at this level, BGP uses many route parameters, called attributes, to
define routing policies and maintain a stable routing environment.

In addition to BGP attributes, classless interdomain routing (CIDR) is used by BGP

to reduce the size of the Internet routing tables. For example, assume that an ISP
owns the IP address block 195.10.x.x from the traditional Class C address space.
This block consists of 256 Class C address blocks, 195.10.0.x through 195.10.255.x.
Assume that the ISP assigns a Class C block to each of its customers. Without CIDR,
the ISP would advertise 256 Class C address blocks to its BGP peers. With CIDR, BGP
can supernet the address space and advertise one block, 195.10.x.x. This block is
the same size as a traditional Class B address block. The class distinctions are
rendered obsolete by CIDR, allowing a significant reduction in the BGP routing
tables.

BGP neighbors exchange full routing information when the TCP connection between
neighbors is first established. When changes to the routing table are detected, the
BGP routers send to their neighbors only those routes that have changed. BGP
routers do not send periodic routing updates, and BGP routing updates advertise
only the optimal path to a destination network.

BGP PATH SELECTION

BGP could possibly receive multiple advertisements for the same route from multiple
sources. BGP selects only one path as the best path. When the path is selected, BGP
puts the selected path in the IP routing table and propagates the path to its
neighbors. BGP uses the following criteria, in the order presented, to select a
path for a destination:

• If the path specifies a next hop that is inaccessible, drop the update.
• Prefer the path with the largest weight.
• If the weights are the same, prefer the path with the largest local
preference.
• If the local preferences are the same, prefer the path that was originated
by BGP running on this router.
• If no route was originated, prefer the route that has the shortest AS_path.
• If all paths have the same AS_path length, prefer the path with the lowest
origin type (where IGP is lower than EGP, and EGP is lower than incomplete).
• If the origin codes are the same, prefer the path with the lowest MED
attribute.
• If the paths have the same MED, prefer the external path over the internal
path.
• If the paths are still the same, prefer the path through the closest IGP
neighbor.
• Prefer the path with the lowest IP address, as specified by the BGP router
ID.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 233

Figure-28c

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.0.0.1 255.0.0.0
A(config-if)# clock rate 64000
A(config-if)# no shutdown

A(config-if)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.255.255.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/1
B(config-if)# ip address 1.0.0.2 255.0.0.0
B(config-if)# no shutdown

B(config-if)# interface ethernet 2/0

B(config-if)# ip address 200.100.100.1 255.255.255.0
B(config-if)# no shutdown

RUNNING RIP ON ROUTER-A

A(config)# router rip
A(config-router)# network 1.0.0.0
A(config-router)# network 200.100.50.0

RUNNING OSPF ON ROUTER-B

B(config)# router ospf 1
B(config-router)# network 1.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 0

ROUTING TABLE OF ROUTER-A & B

A# show ip route

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 234

RUNNING BGP ON ROUTER-A

A(config)# router bgp 10 (10 = Autonomus System)
A(config-router)# neighbor 1.0.0.2 remote-as 20
A(config-router)# network 200.100.50.0

RUNNING BGP ON ROUTER-B

B(config)# router bgp 20 (20 = Autonomus System)
B(config-router)# neighbor 1.0.0.1 remote-as 10
B(config-router)# network 200.100.50.0

ROUTING TABLE OF ROUTER-A & B

A# show ip route

B# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 235

LECTURE NO. 29
11 Feb 2009
BGP

Figure-29a
(Note: Lab results are produced using GNS3 simulator)

A# show ip route

B# show ip route

C# show ip route

D# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 236

RUNNING RIP ON ROUTER-A

A(config)# router rip
A(config-router)# network 200.100.50.0
A(config-router)# network 1.0.0.0

RUNNING EBGP ON ROUTER-A

A(config)# router bgp 10
A(config-router)# neighbor 1.1.1.2 remote-as 20
A(config-router)# network 200.100.50.0

RUNNING EBGP ON ROUTER-B

B(config)# router bgp 20
B(config-router)# neighbor 1.1.1.1 remote-as 10

B# show ip bgp

B# show ip route

B# ping 200.100.50.0

RUNNING OSPF ON ROUTER-B

B(config)# router ospf 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 200.100.100.0 0.0.0.255 area 0

RUNNING OSPF ON ROUTER-C

C(config)# router ospf 1
C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 200.100.150.0 0.0.0.255 area 0

B# show ip route

C# show ip route

NOTE: Network 200.100.50.0 has not reached

on Router-C. Therefore, we'll
perform redistribution on Router-B.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 237

REDISTRIBUTION OF BGP 20 INTO OSPF 1

B(config)# router ospf 1
B(config-router)# redistribute bgp 20 subnets

C# show ip route

NOTE: Network 200.100.50.0 has been

reached on Router-C.

C# ping 200.100.50.1

WHY NOT PING?

REASON: When you try to ping 200.100.50.1 from Router-C, source address is
2.1.1.2 and destination is 200.100.50.1.

When REPLY from Router-A wants to reach back on Router-C, then the
destination address 200.100.50.1 converts into source address and
source address 2.1.1.2 converts into destination address and it could
not find network 2.0.0.0 in the routing table of Router-A.

A# show ip route

To resolve the above issue, we have following three methods:

METHOD #1 (DEFINING STATIC ROUTE ON ROUTER-A)

A(config)# ip route 2.0.0.0 255.0.0.0 1.1.1.2 (where 1.1.1.2 = next hop)

A# show ip route

C# ping 200.100.50.0

METHOD #2 (ADVERTISING 2.0.0.0 INTO BGP ON ROUTER-B)

B(config)# router bgp 20
B(config-router)# network 2.0.0.0

A# show ip bgp

A# show ip route

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 238

NOTE: Network 2.0.0.0 still exists as

static route on Router-A. To prefer
it using BGP, we'll increase
administrative distance of static
route.

A(config)# ip route 2.0.0.0 255.0.0.0 1.1.1.2 50

(where 50 = administrative dist.)

A# show ip route

NOTE: Now the network 2.0.0.0 can be seen

as EBGP (administrative distance =
20) on Router-A.

(RUNNING IBGP BETWEEN ROUTER-A & C)

a. REMOVING STATIC ROUTE FROM ROUTER-A

A(config)# no ip route 2.0.0.0 255.0.0.0 1.1.1.2

b. REMOVING REDISTRIBUTION FROM ROUTER-B

B(config)# router ospf 1

B(config-router)# no redistribute bgp 20 subnets
B(config-router)# no redistribute bgp 20

c. DE-ADVERTISING NETWORK 2.0.0.0 IN BGP

B(config)# router bgp 20

B(config-router)# no network 2.0.0.0

d. RUNNING IBGP IN BETWEEN ROUTERS-B & C

B(config)# router bgp 20

B(config-router)# neighbor 2.1.1.2 remote-as 20

C(config)# router bgp 20

C(config-router)# neighbor 2.1.1.1 remote-as 20

C# show ip route

NOTE: Network 200.100.50.0 has been

disappeared.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 239

C# show ip bgp

NOTE: In the above result, you'll find that even the network
200.100.50.0 exists in the bgp table, but you'll find
there is no > sign, which means that now 200.100.50.0
is not the best entry due to incorrect next hop address,
therefore it has been disappeared from the routing table
of Router-C.

To resolve the above issue, we have following two methods:

a. MANUAL METHOD:
B(config)# router bgp 20
B(config-router)# neighbor 2.1.1.2 next-hop-self
B(config-router)# exit
B(config)# exit

B# clear ip bgp *

B# show ip bgp

C# show ip bgp

NOTE: > Sign still not found, it means that it is still not
best entry, but the next hop 2.1.1.1 has been corrected.
To resolve this issue, apply following command:

C(config)# router bgp 20

C(config-router)# no synchronization (use to avoid black hole)
C(config)# exit

C# clear ip bgp *

C# show ip bgp

C# show ip route

NOTE: Network 200.100.50.0 has been reached as IBGP

(administrative distance = 200) on Router-C.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 240

b. DYNAMIC METHOD:
B(config)# router bgp 20
B(config-router)# no neighbor 2.1.1.2 next-hop-self
B(config-router)# exit
B(config)# exit

B# clear ip bgp *

C# show ip bgp

NOTE: > Sign has been disappeared.

C# show ip route

NOTE: Network 200.100.50.0 has also

been disappeared.

Always use following sequence:

Router bgp x
No synchronization
Router ospf x
Network x.x.x.x x.x.x.x area x

Advertise network 1.0.0.0 in OSPF 1, so that it can reach on Router-C as OSPF.

B(config)# router ospf 1

B(config-router)# network 1.0.0.0 0.255.255.255 area 0

C# show ip route

NOTE: Network 1.0.0.0 has been reached as "O" on Router-C.

When running IBGP, create full

mesh, even the devices are
directly connected or not.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 241

LECTURE NO. 30
13 Feb 2009
BGP

Figure-30a

RUNNING RIP ON ROUTER-A

A(config)# router rip
A(config-router)# network 200.100.50.0
A(config-router)# network 1.0.0.0

RUNNING EBGP ON ROUTER-A

A(config)# router bgp 10
A(config-router)# no synchronization
A(config-router)# neighbor 1.1.1.2 remote-as 20
A(config-router)# neighbor 4.1.1.1 remote-as 20
A(config-router)# network 200.100.50.0

RUNNING EBGP ON ROUTER-B

B(config)# router bgp 20
B(config-router)# no synchronization
B(config-router)# neighbor 1.1.1.1 remote-as 10

RUNNING EBGP ON ROUTER-D

D(config)# router bgp 20
D(config-router)# no synchronization
D(config-router)# neighbor 4.1.1.2 remote-as 10

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 242

RUNNING OSPF ON ROUTER-B

B(config)# router ospf 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 1.0.0.0 0.255.255.255 area 0

RUNNING OSPF ON ROUTER-C

C(config)# router ospf 1
C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 3.0.0.0 0.255.255.255 area 0

RUNNING OSPF ON ROUTER-D

D(config)# router ospf 1
D(config-router)# network 3.0.0.0 0.255.255.255 area 0
D(config-router)# network 4.0.0.0 0.255.255.255 area 0

RUNNING IBGP ON ROUTER-B

B(config)# router bgp 20
B(config-router)# no synchronization
B(config-router)# neighbor 4.1.1.1 remote-as 20
B(config-router)# neighbor 2.1.1.2 remote-as 20

RUNNING IBGP ON ROUTER-C

C(config)# router bgp 20
C(config-router)# no synchronization
C(config-router)# neighbor 2.1.1.1 remote-as 20
C(config-router)# neighbor 3.1.1.2 remote-as 20

RUNNING IBGP ON ROUTER-D

D(config)# router bgp 20
D(config-router)# no synchronization
D(config-router)# neighbor 3.1.1.1 remote-as 20
D(config-router)# neighbor 2.1.1.1 remote-as 20

B# show ip bgp

B# show ip route

B# ping 200.100.50.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 243

D# show ip bgp

D# show ip route

C# show ip bgp

C# show ip route

A# show ip bgp

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 244

LECTURE NO. 31
16 Feb 2009
BGP ATTRIBUTES
Routes learned via BGP have associated properties that are used to determine the
best route to a destination when multiple paths exist to a particular destination.
These properties are referred to as BGP attributes, and an understanding of how BGP
attributes influence route selection is required for the design of robust networks.
This section describes the attributes that BGP uses in the route selection process:

• Weight
• Local preference
• Multi-exit discriminator
• Origin
• AS path
• Next hop
• Community

C# show ip bgp

attributes

WEIGHT ATTRIBUTE
Weight is a Cisco-defined attribute that is local to a router. The weight attribute
is not advertised to neighboring routers. If the router learns about more than one
route to the same destination, the route with the highest weight will be preferred.
The route with the highest weight will be installed in the IP routing table.

LAB
CHANGING WEIGHT ATTRIBUTE OF SERIAL 1/0 - ROUTER-C?

C(config)# router bgp 20

C(config-router)# neighbor 3.1.1.2 weight 333
C# clear ip bgp *

BEFORE CHANGING WEIGHT ATTRIBUTE

C# show ip bgp

AFTER CHANGING WEIGHT ATTRIBUTE

C# show ip bgp

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 245

CHANGING WEIGHT ATTRIBUTE OF SERIAL 1/1 OF ROUTER-C

C(config)# router bgp 20

C(config-router)# neighbor 2.1.1.1 weight 333
C# clear ip bgp *

C# show ip bgp

NOTE: Here, we have configured same value of weight attribute at both interfaces
of Router-C. In this case, decision would take place using Router-ID
attribute. Router having smaller value of Router-ID shall be preferred. Here
Router-ID of Router-D is 200.100.200.1 and Router-ID of Router-B is
200.100.100.1. Therefore, Router-B has been preferred. You can check Router-
ID of a neighbor by using following command:

C# show ip bgp neighbor

LOCAL PREFERENCE ATTRIBUTE

The local preference attribute is used to prefer an exit point from the local
autonomous system (AS). Unlike the weight attribute, the local preference attribute
is propagated throughout the local AS. If there are multiple exit points from the
AS, the local preference attribute is used to select the exit point for a specific
route.

LAB
CHANGING VALUE OF LOCAL PREFERENCE ATTRIBUTE ON ROUTER-C

D(config)# router bgp 20

D(config-router)# bgp default local-preference 420
D# clear ip bgp *

BEFORE CHANGING VALUE OF LOCAL PREFERENCE ATTRIBUTE ON ROUTER-D

C# show ip bgp

AFTER CHANGING VALUE OF LOCAL PREFERENCE ATTRIBUTE ON ROUTER-D

C# show ip bgp

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 246

LECTURE NO. 32
18 Feb 2009
BGP ATTRIBUTES
MULTI-EXIT DISCRIMINATOR ATTRIBUTE
The multi-exit discriminator (MED) or metric attribute is used as a suggestion to
an external AS regarding the preferred route into the AS that is advertising the
metric.

The term suggestion is used because the external AS that is receiving the MEDs may
be using other BGP attributes for route selection. MEDs are advertised throughout
the local AS. Router having smaller value of metric shall be preferred.

LAB
A(config)# access-list 31 permit 200.100.50.0 0.0.0.255
A(config)# route-map shakeel permit 11
A(config-route-map)# match ip address 31
A(config-route-map)# set metric 50
A(config-route-map)# exit
A(config)# route-map nabeel permit 11
A(config-route-map)# match ip address 31
A(config-route-map)# set metric 100
A(config-route-map)# exit
A(config)#
A(config)# router bgp 10
A(config-router)# neighbor 4.1.1.1 route-map shakeel out
A(config-router)# neighbor 1.1.1.2 route-map nabeel out

B# show ip bgp

C# show ip bgp

D# show ip bgp

ORIGIN
The origin attribute indicates how BGP learned about a particular route. The origin
attribute is used for route selection. The origin attribute can have one of three
possible values:

• IGP—The route is interior to the originating AS. This value is set when
the network router configuration command is used to inject the route into
BGP.
• EGP—The route is learned via the Exterior Border Gateway Protocol (EBGP).
• Incomplete—The origin of the route is unknown or learned in some other
way. An origin of incomplete occurs when a route is redistributed into
BGP.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 247

LAB-1 (SUMMARY & ORIGIN ATTRIBUTE)

REMOVING ACCESS-LIST AND ROUTE-MAP

A(config)# no access-list 31 permit 200.100.50.0 0.0.0.255

A(config)# no route-map shakeel permit 11
A(config)# no route-map nabeel permit 12
A(config)# router bgp 10
A(config-router)# no neighbor 4.1.1.1 route-map shakeel out
A(config-router)# no neighbor 1.1.1.2 route-map nabeel out

DEFINING 4 STATIC ROUTES ON ROUTER-A

A(config)# ip route 192.1.17.0 255.255.255.0 null 0

A(config)# ip route 192.1.18.0 255.255.255.0 null 0
A(config)# ip route 192.1.19.0 255.255.255.0 null 0
A(config)# ip route 192.1.20.0 255.255.255.0 null 0

REDISTRIBUTION OF STATIC ROUTES INTO BGP 10 – ROUTER-A

A(config)# router bgp 10

A(config-router)# redistribute static

C# show ip bgp

Origin Attribute
Precedence of I
Is more than ?

CREATING SUMMARY OF STATIC ROUTES

A(config)# router bgp 10

A(config-router)# aggregate-address 192.1.16.0 255.255.218.0 summary-only

C# show ip bgp

Summary Address of Static Routes

REMOVING SUMMARY OF STATIC ROUTES

A(config)# router bgp 10

A(config-router)# no aggregate-address 192.1.16.0 255.255.218.0 summary-only
A(config-router)# no aggregate-address 192.1.16.0 255.255.218.0

CREATING SUMMARY OF STATIC ROUTES - (WITHOUT SUMMARY-ONLY COMMAND)

A(config)# router bgp 10

A(config-router)# aggregate-address 192.1.16.0 255.255.218.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 248

C# show ip bgp

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 249

LAB-2

Figure-32b
(Note: Lab results are produced using GNS3 simulator)

CREATING ACCESS-LIST ON ROUTER-A

A(config)# access-list 81 permit 200.100.50.0 0.0.0.255

A(config)# access-list 81 permit 192.1.17.0 0.0.0.255
A(config)# access-list 81 permit 192.1.18.0 0.0.0.255

A(config)# access-list 82 permit 192.1.19.0 0.0.0.255

A(config)# access-list 82 permit 192.1.20.0 0.0.0.255

CREATING ROUTE-MAP (AD) ON ROUTER-A

A(config)# route-map AD permit 10

A(config-route-map)# match ip address 81
A(config-route-map)# set metric 50
A(config-route-map)# exit

A(config)# route-map AD permit 20

A(config-route-map)# match ip address 82
A(config-route-map)# set metric 120

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 250

CREATING ROUTE-MAP (AB) ON ROUTER-A

A(config)# route-map AB permit 10

A(config-route-map)# match ip address 82
A(config-route-map)# set metric 60
A(config-route-map)# exit

A(config)# route-map AB permit 20

A(config-route-map)# match ip address 81
A(config-route-map)# set metric 100

APPLYING ROUTE-MAP (AD & AB) ON ROUTER-A

A(config)# router bgp 10

A(config-router)# neighbor 4.1.1.1 route-map AD out
A(config-router)# neighbor 1.1.1.2 route-map AB out

A# clear ip bgp *

B# show ip bgp

C# show ip bgp

D# show ip bgp

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 251

LECTURE NO. 33
19 Feb 2009
BGP ATTRIBUTES
AS_PATH ATTRIBUTE
When a route advertisement passes through an autonomous system, the AS number is
added to an ordered list of AS numbers that the route advertisement has traversed.

Figure-33a

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 252

LAB

DEFINING 5 STATIC ROUTES AT ROUTE-A

A(config)# ip route 192.1.17.0 255.255.255.0 null 0

A(config)# ip route 192.1.18.0 255.255.255.0 null 0
A(config)# ip route 192.1.19.0 255.255.255.0 null 0
A(config)# ip route 192.1.20.0 255.255.255.0 null 0

REDISTRIBUTING STATIC ROUTES INTO BGP 10 – ROUTER-A

A(config)# router bgp 10

A(config-router)# redistribute static

CREATING ACCESS-LIST ON ROUTER-A

A(config)# access-list 51 permit 200.100.50.0 0.0.0.255

A(config)# access-list 51 permit 192.1.17.0 0.0.0.255
A(config)# access-list 51 permit 192.1.18.0 0.0.0.255

A(config)# access-list 52 permit 192.1.19.0 0.0.0.255

A(config)# access-list 52 permit 192.1.20.0 0.0.0.255

CREATING ROUTE-MAP (AD) ON ROUTER-A

A(config)# route-map AD permit 10

A(config-route-map)# match ip address 51
A(config-route-map)# set as-path prepend 33

A(config)# route-map AD permit 20

A(config-route-map)# match ip address 52
A(config-route-map)# set as-path prepend 88 99

CREATING ROUTE-MAP (AB) ON ROUTER-A

A(config)# route-map AB permit 10

A(config-route-map)# match ip address 51
A(config-route-map)# set as-path prepend 44 55

A(config)# route-map AB permit 20

A(config-route-map)# match ip address 52
A(config-route-map)# set as-path prepend 66

APPLYING ROUTE-MAP (AD & AB) ON ROUTER-A

A(config)# router-bgp 10
A(config-router)# neighbor 4.1.1.1 route-map AD out
A(config-router)# neighbor 1.1.1.2 route-map AB out

A# clear ip bgp *

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 253

B# show ip bgp

C# show ip bgp

D# show ip bgp

DEFINING ONE MORE STATIC ROUTE AT ROUTE-A

A(config)# ip route 192.1.21.0 255.255.255.0 null 0

CREATING ROUTE-MAP FOR NEW STATIC ROUTE - ROUTE-A

A(config)# route-map AD permit 30

A(config-route-map)# exit
A(config)# route-map AB permit 30

A# clear ip bgp *

C# show ip bgp

CHANGING METRIC VALUE OF 192.1.21.0 SO THAT IT CAN USE 4.1.1.2 AS BEST PATH

A(config)# access-list 53 permit 192.1.21.0 0.0.0.255

A(config)# route-map AD permit 25

A(config-route-map)# match ip address 53
A(config-route-map)# set metric 100

A(config)# route-map AB permit 25

A(config-route-map)# match ip address 53
A(config-route-map)# set metric 200

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 254

A# clear ip bgp *

C# show ip bgp

AS-PATH FILTERATION LAB

(USING ABOVE LAB)

_99$ = Routes having as-path value ends with 99

^10_ = Routes having as-path value starts with 10

_88_ = Routes having as-path value 88, either at start or at end or in

middle

. * = Routes having any value of as-path

D(config)# ip as-path access-list 5 deny _99$

D(config)# ip as-path access-list 5 permit . *

D(config)# router bgp 20

D(config-router)# neighbor 4.1.1.2 filter-list 5 in

D# clear ip bgp *

D# show ip bgp

EXTERNAL BGP (E) > INTERNAL BGP (I)

If value of local preference is equal at all ABRs, then the decision would take
place using E>I attribute. Router having maximum value of LOCAL PREFERENCE
attribute shall be preferred. Normally, we apply this attribute at ABR.

ROUTER-ID
The neighbor having small Router-ID shall be preferred.

HOW TO CHANGE ROUTER-ID IN BGP?

C(config)# router bgp 20

C(config-router)# bgp router-id 200.100.20.0

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 255

NEXT-HOP ATTRIBUTE
The EBGP next-hop attribute is the IP address that is used to reach the advertising
router. For EBGP peers, the next-hop address is the IP address of the connection
between the peers. For IBGP, the EBGP next-hop address is carried into the local AS

COMMUNITY ATTRIBUTE
The community attribute provides a way of grouping destinations, called
communities, to which routing decisions (such as acceptance, preference, and
redistribution) can be applied. Route maps are used to set the community attribute.
Predefined community attributes are listed here:

• no-export—Do not advertise this route to EBGP peers.

• no-advertise—Do not advertise this route to any peer.
• internet—Advertise this route to the Internet community; all routers in the
network belong to it.

Figure 30-G illustrates the no-export community. AS 1 advertises 200.100.100.0 to

AS 2 with the community attribute no-export. AS 2 will propagate the route
throughout AS 2 but will not send this route to AS 3 or any other external AS.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 256

LECTURE NO. 34
20 Feb 2009
ROUTE REFLECTOR / CONFEDERATION
SCALABILITY PROBLEMS WITH IBGP FULL MESH
ƒ When your network have grown and a full mesh isn't feasible
ƒ n*(n-1)/2 where n = the number of iBGP speaking routers
ƒ If we have 200 routers in our network that would give us 19900 BGP sessions

SOLUTIONS
ƒ Route Reflectors
ƒ Confederations

WHAT ARE BGP ROUTE REFLECTORS?

Using standard Internal Border Gateway Protocol (IBGP) configurations, all BGP
systems within an Autonomous

System (AS) must peer with all other BGP systems, forming a full-mesh
configuration. This presents scaling concerns, as all external information must be
propagated/distributed to all BGP systems within the AS, resulting in far more
information being shared between the IBGP peers then is necessary. BGP Route
Reflectors (RR) provides a mechanism for both minimizing the number of update
messages transmitted within the AS, and reducing the amount of data that is
propagated in each message. The deployment of BGP Route Reflectors leads to much
higher levels of network scalability.

Figure-C (An Example of IBGP Full Mesh)

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 257

A ROUTE REFLECTOR REFLECTS IBGP ROUTING INFORMATION

♦ From clients to iBGP peers and other clients

♦ From iBGP peers to clients
♦ Never from iBGP peers to iBGP peers (as before)
♦ Should not change the attributes

ƒ NEXT_HOP
ƒ AS_PATH
ƒ LOCAL_PREF
ƒ MED

CONFEDERATIONS

♦ Another way of solving iBGP full mesh.

♦ The idea behind confederations is to take one large AS and divide it into
several smaller ones

ƒ Non-members of the confederation see one AS, members of the confederation

are divided into sub-AS's
ƒ One IGP must usually be run in the whole confederation to support
connectivity
ƒ LOCAL-PREF and NEXTHOP is preserved through the confederation

MECHANISM

♦ Two new segments of the AS_PATH are added (apart from AS_SEQUENCE and AS_SET):

ƒ AS-CONFED-SET
ƒ AS-CONFED-SEQUENCE

♦ BGP speakers add sub-AS numbers to these within the confederation.

SUB AS NUMBERS

♦ AS confederation identifier = the external AS number

♦ AS member number = the confederation sub-AS number
♦ Design considerations: When configuring confederations use private AS numbers
(64512 – 65535):

ƒ Some implementations of confederations have been known to leak

ƒ The member sub-AS numbers to it's eBGP peers

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 258

ƒ What happens if you use public AS numbers that belonged to someone else?

ANNOUNCING RULES

♦ IBGP (within a sub_AS) behaves as normal

♦ BGP peering between sub-ASs (sometimes called eiBGP):

ƒ Prepend the sub-AS (AS member #) to the AS_PATH

♦ When a BGP update is leaving the confederation

ƒ Remove the prepended sub-AS information from the AS-PATH.

♦ Differences between eBGP and eiBGP

ƒ LOCAL-PREF is preserved through the confederation

ƒ NEXT-HOP is also preserved

♦ You have to know if you should speak eiBGP or eBGP to your neighbor:

ƒ Share AS confederation identifier -> eiBGP

SUB-HIERARCHIES

♦ You cannot make sub-hierarchies using confederations

♦ You can use route reflection within a sub_AS

ƒ And even sub-route reflector hierarchies.

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 259

ROUTE-REFLECTOR - LAB

Figure-34a

BASIC CONFIGURATION OF ROUTER-A

A(config)# interface serial 1/0
A(config-if)# ip address 1.1.1.1 255.0.0.0
A(config-if)# no shutdown

A(config-if)# interface ethernet 2/0

A(config-if)# ip address 200.100.50.1 255.0.0.0
A(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-B

B(config)# interface serial 1/0
B(config-if)# ip address 1.1.1.2 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

B(config)# interface serial 1/1

B(config-if)# ip address 2.1.1.1 255.0.0.0
B(config-if)# no shutdown
B(config-if)# clock rate 64000

BASIC CONFIGURATION OF ROUTER-C

C(config)# interface serial 1/1
C(config-if)# ip address 2.1.1.2 255.0.0.0
C(config-if)# no shutdown

C(config)# interface serial 1/0

C(config-if)# ip address 3.1.1.1 255.0.0.0
C(config-if)# no shutdown

BASIC CONFIGURATION OF ROUTER-D

D(config)# interface serial 1/1
D(config-if)# ip address 3.1.1.2 255.0.0.0
D(config-if)# no shutdown

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 260

RUNNING EBGP ON ROUTER-A

A(config)# router bgp 10
A(config-router)# no synchronization
A(config-router)# neighbor 1.1.1.2 remote-as 20
A(config-router)# network 200.100.50.0

RUNNING EBGP ON ROUTER-B

B(config)# router bgp 20
B(config-router)# no synchronization
B(config-router)# neighbor 1.1.1.1 remote-as 10

RUNNING OSPF ON ROUTER-B

B(config)# router ospf 1
B(config-router)# network 2.0.0.0 0.255.255.255 area 0
B(config-router)# network 1.0.0.0 0.255.255.255 area 0

RUNNING OSPF ON ROUTER-C

C(config)# router ospf 1
C(config-router)# network 2.0.0.0 0.255.255.255 area 0
C(config-router)# network 3.0.0.0 0.255.255.255 area 0

RUNNING OSPF ON ROUTER-D

C(config)# router ospf 1
C(config-router)# network 3.0.0.0 0.255.255.255 area 0

RUNNING IBGP ON ROUTER-B

B(config)# router bgp 20
B(config-router)# no synchronization
B(config-router)# neighbor 1.1.1.1 remote-as 20
B(config-router)# neighbor 2.1.1.2 remote-as 20

RUNNING IBGP ON ROUTER-C

C(config)# router bgp 20
C(config-router)# no synchronization
C(config-router)# neighbor 2.1.1.1 remote-as 20
C(config-router)# neighbor 3.1.1.2 remote-as 20

RUNNING IBGP ON ROUTER-D

D(config)# router bgp 20
D(config-router)# no synchronization
D(config-router)# neighbor 3.1.1.1 remote-as 20

B# show ip bgp

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF

 261

C# show ip bgp

D# show ip bgp

NOTE: Network/Route 200.100.50.0 not found

on Router-D.

APPLYING ROUTE-REFLECTOR ON ROUTER-C

C(config)# router bgp 20
C(config-router)# neighbor 2.1.1.1 route-reflector-client
C(config-router)# neighbor 3.1.1.2 route-reflector-client

C# clear ip bgp *

D# show ip bgp

AUTHENTICATION IN BGP

AUTHENTICATION ON ROUTER-A
A(config)# router bgp 10
A(config-router)# neighbor 1.1.1.2 password shakeel

AUTHENTICATION ON ROUTER-B
B(config)# router bgp 20
B(config-router)# neighbor 1.1.1.1 password shakeel

NOTE: Use same password on both sides (I used shakeel

as a password).

CCNP ROUTING – LAB MANUAL BY: MUHAMMAD SHAKEEL ASHRAF