BSCI30 NIL Lab Guide PDF

BSCI
Building Scalable
Cisco Internetworks
Version 3.0

NIL Lab Guide

Copyright 2006, Cisco Systems, Inc. All rights reserved.
Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone
numbers, and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offices.
Argentina Australia Austria Belgium Brazil Bulgaria Canada Chile China PRC
Colombia Costa Rica Croatia Czech Republic Denmark Dubai, UAE Finland France
Germany Greece Hong Kong SAR Hungary India Indonesia Ireland Israel Italy Japan
Korea Luxembourg Malaysia Mexico The Netherlands New Zealand Norway Peru
Philippines Poland Portugal Puerto Rico Romania Russia Saudi Arabia Scotland
Singapore Slovakia Slovenia South Africa Spain Sweden Switzerland Taiwan Thailand
Turkey Ukraine United Kingdom United States Venezuela Vietnam Zimbabwe
Copyright 2006 Cisco Systems, Inc. All rights reserved. CCIP, CCSP, the Cisco Powered
Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are
trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick
Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP,
CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS
logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the
Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet
Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX,
MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing,
Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm,
SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other
countries.
All other trademarks mentioned in this document or Website are the property of their respective
owners. The use of the word partner does not imply a partnership relationship between Cisco and any
other company. (0401R)

Copyright 2006, NIL Data Communications Table of Contents I
Table of Contents
Configuring and Tuning EIGRP 1
Objective 1
Command List 3
Detailed Instructions 4
Lab Topology 12
Addressing and Routing 13
Configuring and Tuning EIGRP Lab Solutions 15
Lab Solution 15
Configuring and Examining OSPF in a Single Area 17
Objective 17
Command List 19
Lab Topology 30
Configuring and Examining OSPF in a Single Area Lab Solutions 33
Lab Solution 33
Configuring OSPF for Frame Relay Environment 37
Objective 37
Command List 39
Lab Topology 51
Configuring OSPF for Frame Relay Environment Lab Solutions 55
Lab Solution 55
Configuring a Multi-Area OSPF Network 57
Objective 57
Command List 59
Lab Topology 80
Configuring a Multi-Area OSPF Network Lab Solutions 83
Lab Solution 83
Configuring Integrated IS-IS in Multiple Areas 87
Objective 87
Command List 89
Lab Topology 97
Configuring Integrated IS-IS in Multiple Areas Lab Solutions 101
Lab Solution 101
Configuring Route Redistribution 105
Objective 105
Command List 107
Lab Topology 117
Configuring Route Redistribution Lab Solutions 121
Lab Solution 121
Configuring BGP 123
II Building Scalable Cisco Internetworks (BSCI) v3.0 Copyright 2006, NIL Data Communications
Objective 123
Command List 125
Lab Topology 138
Configuring BGP Lab Solutions 141
Lab Solution 141
Scaling BGP 143
Objective 143
Command List 145
Lab Topology 154
Scaling BGP Lab Solutions 159
Lab Solution 159
Configuring Multicast Routing 161
Objective 161
Command List 162
Lab Topology 172
Configuring Multicast Routing Lab Solutions 175
Lab Solution 175
Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel 177
Objective 177
Command List 179
Lab Topology 192
Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel Lab Solutions 195
Lab Solution 195

BSCI
Configuring and Tuning
EIGRP
Objective
In this exercise, you will configure EIGRP routing in your network by enabling EIGRP on all
WAN links (Frame Relay sub-interfaces) and all LAN links within your network as shown in the
following figure.

Figure 1: Basic EIGRP deployment
After configuring basic EIGRP routing, you will examine the established EIGRP adjacencies, the
EIGRP topology table and observe the IP routing tables. The changes in the network are
propagated through the entire network, which can result in frequent routing table recalculations.
To improve the stability, convergence speed and to reduce the routing overhead in your network
you will configure manual summarization towards the core routers. Next, you will influence
EIGRP path selection by changing delay on certain links. Finally you will deploy EIGRP stub
feature and advertise default route via EIGRP to internal routers to further improve stability of
the network.
2 Configuring and Tuning EIGRP Copyright 2006, NIL Data Communications

Figure 2: EIGRP with enhancements
In this laboratory exercise, you will complete these tasks:
Configure your routers with EIGRP routing protocol.
Explore the EIGRP query traffic.
Configure route summarization using EIGRP.
Announce a default route via EIGRP routing protocol.
Configure the EIGRP stub feature to limit the scope of the EIGRP queries.
Note Please refer to the Topology section for more details on physical connectivity and to the
Addressing section for detailed IP addressing information.
Copyright 2006, NIL Data Communications Configuring and Tuning EIGRP 3
Command List
Use the following commands to complete this exercise:
Command Task
bandwidth value Configures bandwidth in kbps on a certain interface.
debug ip eigrp Enables debugging of EIGRP.
delay value Configures delay in tens of microseconds on a certain
interface.
eigrp stub Configures a router to be an EIGRP stub router.
ip summary-address eigrp AS
network mask
Configures an EIGRP per interface summary route
(with the default Administrative Distance of 5).
network network {wildcard} Enables EIGRP on interfaces belonging to a specified
network.
no auto-summary Disables the EIGRP automatic summarization on
classful network boundaries
no shutdown Enables the interface.
router eigrp as-number Starts an EIGRP routing process with the given AS
number.
show ip eigrp neighbors {detail} Lists EIGRP neighbors and relevant information on
EIGRP neighbor adjacencies.
show ip eigrp topology [prefix]
[mask]
Displays EIGRP topology table (whole, or only per
prefix/mask).
show ip protocols Displays the information about configured IP
protocols.
show ip route {network mask} Displays the IP routing table information (whole, or
only for specific network).
Shutdown Disables the interface.
undebug all Turns off all debugging.
Table 1: Configuration and monitoring commands used in the Configuring and
Tuning EIGRP Lab exercise
Detailed Instructions
Task 1: Configuring Basic EIGRP
In this task, you will enable EIGRP in your network and examine the EIGRP query packets.
Step 1 Enable EIGRP routing protocol on R1, R2, R3 and R4 routers on all interfaces. Use the EIGRP
AS number 1.
Step 2 Disable the auto summarization on all routers.
Step 3 Set the bandwidth of all serial interfaces on routers R1, R2, R3 and R4 to 64 kbps.
Note The routers in different lab pods may support only Ethernet or only FastEthernet interfaces. As
all printouts in the lab were taken on routers with FastEthernet interfaces, the default
bandwidth and the default delay on Ethernet interfaces were changed to FastEthernet
interface default values for compatibility reasons.
Verification
Step 4 Verify the configuration of your routers using the show ip protocols command. Assure that the
correct AS number is configured and that the routers are exchanging routing updates with all
neighbors. The command also reveals whether automatic summarization is enabled, the current
values of K weights, and administrative distance of internal and external EIGRP routes. The
exemplary printouts show the EIGRP information on R1 and R3 routers.
R1#show ip protocols
Routing Protocol is "eigrp 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 1
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.31.0.0
Routing Information Sources:
Gateway Distance Last Update
(this router) 90 00:01:41
10.1.1.3 90 00:00:42
10.1.0.2 90 00:00:41
172.31.1.3 90 00:00:41
Distance: internal 90 external 170
Printout 1: EIGRP protocol information on R1 router
R3#show ip protocols
Routing Protocol is "eigrp 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 1
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
Routing Information Sources:
Gateway Distance Last Update
10.1.1.1 90 00:01:43
10.1.3.4 90 00:01:43
Distance: internal 90 external 170
Printout 2: EIGRP protocol information on R3 router
Step 5 Verify the establishment of EIGRP neighbor relations by using the show ip eigrp neighbors
command on all routers. The output also shows through which interfaces the router has
established EIGRP neighbor relations and the time that has elapsed since the individual EIGRP
adjacency was established.
R2#show ip eigrp neighbors
IP-EIGRP neighbors for process 1
H Address Interface Hold Uptime SRTT RTO Q Seq
Type
(sec) (ms) Cnt Num
2 172.31.1.3 Se0/0.2 158 00:03:56 973 5000 0 6
1 10.1.2.4 Fa0/0 11 00:04:08 3 200 0 6
0 10.1.0.1 Se0/0.1 13 00:04:39 556 3336 0 9
Printout 3: EIGRP adjacencies on R2 router
Note The order of listed EIGRP neighbors depends on the time of adjacency establishment. The
most recent neighbor is on top (see Uptime column).
Step 6 Examine the routing table on R2 and R4 routers. Since auto summarization has been turned off
and EIGRP is a classless routing protocol, routers learn of each subnet in your network.
R2#show ip route
...

Gateway of last resort is not set

172.31.0.0 255.255.255.0 is subnetted, 1 subnets
C 172.31.1.0 is directly connected, Serial0/0.2
D 10.1.3.0 [90/40514560] via 10.1.2.4, 00:11:41, FastEthernet0/0
C 10.1.2.0 is directly connected, FastEthernet0/0
D 10.1.1.0 [90/40514560] via 10.1.0.1, 00:11:41, Serial0/0.1
D 10.254.0.0 [90/41024000] via 172.31.1.3, 00:11:41, Serial0/0.2
Printout 4: Routing table on R2 router
R4#show ip route
...


D 10.1.1.0 [90/40514560] via 10.1.3.3, 00:19:59, Serial0/0.1
Step 7 Telnet to the BBR1 router and examine the content of the routing and topology table. BBR1
knows about each and every subnet in your network. Since EIGRP supports equal-cost load
sharing by default, you should see that the networks 10.1.3.0/24 and 10.1.0.0/24 are accessible
via two equal-cost next-hops. The output should be similar to the printout below.
BBR1#show ip route
...


D 10.1.3.0 [90/41026560] via 172.31.1.1, 00:21:11, Serial0/0.2
[90/41026560] via 172.31.1.2, 00:21:11, Serial0/0.2
D 10.1.2.0 [90/40514560] via 172.31.1.2, 00:21:11, Serial0/0.2
D 10.1.1.0 [90/40514560] via 172.31.1.1, 00:21:11, Serial0/0.2
D 10.1.0.0 [90/41024000] via 172.31.1.1, 00:21:11, Serial0/0.2
[90/41024000] via 172.31.1.2, 00:21:12, Serial0/0.2
Printout 6: Routing table on BBR1 router
BBR1#show ip eigrp topology
IP-EIGRP Topology Table for AS(1)/ID(10.254.0.1)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

P 10.1.3.0 255.255.255.0, 2 successors, FD is 41026560
via 172.31.1.2 (41026560/40514560), Serial0/0.2
via 172.31.1.1 (41026560/40514560), Serial0/0.2
via 172.31.1.2 (40514560/28160), Serial0/0.2
via 172.31.1.1 (40514560/28160), Serial0/0.2
via 172.31.1.2 (41024000/40512000), Serial0/0.2
via 172.31.1.1 (41024000/40512000), Serial0/0.2
via Connected, Serial0/0.2
via Connected, Serial0/0.1
BBR1#
Printout 7: EIGRP topology table on BBR1 router
The EIGRP topology table entry for the network 10.1.0.0/24 on BBR1 router shows the vector
metric related with the destination.
BBR1#show ip eigrp topology 10.1.0.0 255.255.255.0
IP-EIGRP (AS 1): Topology entry for 10.1.0.0 255.255.255.0
State is Passive, Query origin flag is 1, 2 Successor(s), FD is
41024000
Routing Descriptor Blocks:
172.31.1.2 (Serial0/0.2), from 172.31.1.2, Send flag is 0x0
Composite metric is (41024000/40512000), Route is Internal
Vector metric:
Minimum bandwidth is 64 Kbit
Total delay is 40000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Vector metric:
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Printout 8: EIGRP topology table information for the 10.1.0.0/24 network on
BBR1 router
Step 8 Use the debug ip eigrp command to monitor EIGRP queries on R4 internal router. Shut down
the S0/0.1 interface on R2 router and observe EIGRP queries sent to R4 router. R2 queries for the
network 10.1.0.0/24 R4 and informs R4 that it cannot reach that network (metric 4294967295
signifies that the network is no longer reachable via R2). R4 queries R3 about that network and
gets reply that the network is accessible via R3. R4 responds to R2 that the network 10.1.0.0/24 is
reachable and R2 updates its routing table with the information about 10.1.0.0/24 network.
R4#debug ip eigrp
IP-EIGRP Route Events debugging is on
R4#
07:50:04: IP-EIGRP: Processing incoming QUERY packet
07:50:04: IP-EIGRP: Int 10.1.0.0 255.255.255.0 M 4294967295 - 0
4294967295 SM 4294967295 - 0 4294967295
(received query packet from R2 for lost networks 10.1.1.0/24 and
10.1.0.0/24)
07:50:04: IP-EIGRP: Int 10.1.1.0 255.255.255.0 M 4294967295 - 40000000
4294967295 SM 4294967295 - 40000000 4294967295
07:50:04: IP-EIGRP: 10.1.0.0 255.255.255.0 - do advertise out Serial0/0.1
07:50:04: IP-EIGRP: Int 10.1.0.0 255.255.255.0 metric 4294967295 - 0
4294967295 (R4 has no Feasible Successor for 10.1.0.0, sends QUERY to R3)
07:50:04: IP-EIGRP: Processing incoming REPLY packet
07:50:04: IP-EIGRP: Int 10.1.0.0 255.255.255.0 M 41026560 - 40000000
1026560 SM 40514560 - 40000000 514560
(Received REPLY from R3 with valid information)
07:50:04: IP-EIGRP: 10.1.0.0 255.255.255.0 routing table not updated
07:50:04: IP-EIGRP: 10.1.0.0 255.255.255.0 routing table not updated
1026560
07:50:05: IP-EIGRP: 10.1.1.0 255.255.255.0 - do advertise out
FastEthernet0/0
514560
07:50:05: IP-EIGRP: 10.1.0.0 255.255.255.0 - do advertise out
FastEthernet0/0 (advertising update on 10.1.0.0 network to R2, based on
reply from R3)
1026560
Printout 9: EIGRP debug output on R4 router
Note The text in italics is a comment added to the output to aid the output explanation and will not
be present in your output.
R2#show ip route
...


D 10.254.0.0 [90/41024000] via 172.31.1.3, 00:04:27, Serial0/0.2
Step 9 Disable the debugging of the EIGRP operation on R4 router and re-enable the connection
between R1 and R2 edge routers.
Task 2: Influence EIGRP Path Selection
In this task, you will influence EIGRP path selection by changing the delay value on certain
interfaces.
Step 10 Increase the delay of S0/0.1 interface on R1 router to 25000 s, thus making the routes reachable
over this interface appear with a worse metric.
Note In Cisco IOS, the delay is configured in tens of microseconds. The default delay for serial
interfaces in Cisco IOS is 20000 s.
Verification
Step 11 Telnet to the BBR1 router and examine the content of the routing table. Remember that prior to
changing the delay value, two routes for the network 10.1.0.0/24 existed. Now the BBR1 router
has installed only the route through R2 router for the network 10.1.0.0/24.
BBR1#show ip route
...


D 10.1.3.0 [90/41026560] via 172.31.1.2, 00:03:58, Serial0/0.2
[90/41026560] via 172.31.1.1, 00:03:58, Serial0/0.2
D 10.1.2.0 [90/40514560] via 172.31.1.2, 00:01:26, Serial0/0.2
D 10.1.1.0 [90/40514560] via 172.31.1.1, 00:03:58, Serial0/0.2
D 10.1.0.0 [90/41024000] via 172.31.1.2, 00:01:36, Serial0/0.2
Step 12 Now check the EIGRP topology table content for the network 10.1.0.0/24 on BBR1 router. The
BBR1 has information about two possible paths to network 10.1.0.0/24. One is through R1 and
the other through R2 router. The lowest cost path is through R2 router, which is a successor.
Notice that the advertised distance through R1 router is less than the feasible distance of
10.1.0.0/24, which makes R1 a feasible successor.
State is Passive, Query origin flag is 1, 2 Successor(s), FD is
41024000
Vector metric:
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Vector metric:
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Printout 12: EIGRP topology table on BBR1 router
Task 3: Improve EIGRP Core Scalability
In this task, you will configure the EIGRP manual route summarization. Summarization
improves convergence speed and network stability by controlling the scope of queries and
minimizing the amount of routing update traffic and the size of the routing table.
Step 13 Configure manual summarization on R1 and R2 edge routers. Summarize the internal networks
towards the core into a single 10.1.0.0/16 network.
Verification
Step 14 Telnet to BBR1 router and re-examine the routing and topology tables. BBR1 router no longer
has knowledge about 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24 and 10.1.3.0/24 subnets. Instead, only
summary route 10.1.0.0/16 is known and thus the routing and topology tables are smaller due to
summarization. Notice that there are two equal-cost paths to 10.1.0.0/16 network, so BBR1 will
perform load sharing for all 10.1.0.0/16 subnets.
BBR1#show ip route
...


10.0.0.0 255.0.0.0 is variably subnetted, 2 subnets, 2 masks
D 10.1.0.0 255.255.0.0
[90/2172416] via 172.31.1.1, 00:01:20, Serial0/0.2
[90/2172416] via 172.31.1.2, 00:01:20, Serial0/0.2
C 10.254.0.0 255.255.255.0 is directly connected, Serial0/0.1
BBR1#
State is Passive, Query origin flag is 1, 2 Successor(s), FD is 2172416
Vector metric:
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Vector metric:
Load is 1/255
Minimum MTU is 1500
Hop count is 1
Printout 14: EIGRP topology table information for 10.1.0.0/16 network on BBR1
router
Step 15 Check the routing table of R1 and R2 routers. The propagation of a summary route results in an
unconditional attraction of the traffic for all the subnets from the summary, even if a particular
subnet does not exist anymore. To avoid black holing the traffic or even creating routing loops,
EIGRP installs a summary route connected to the Null0 interface on R1 and R2 routers. So, in
case a router receives packets destined for a subnet that does not exist, such packets are routed to
the Null0 interface, in other words, they are dropped.
R2#show ip route 10.1.0.0 255.255.0.0
Routing entry for 10.1.0.0 255.255.0.0
Known via "eigrp 1", distance 5, metric 28160, type internal
Redistributing via eigrp 1
* directly connected, via Null0
Route metric is 28160, traffic share count is 1
Total delay is 100 microseconds, minimum bandwidth is 100000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 0
Task 4: Configure EIGRP Stub
Your job now is to limit the query traffic from edge routers to internal routers. You will
accomplish that by deploying the EIGRP stub feature, which improves convergence speed and
network stability and helps avoiding stuck in active (SIA) situations, where EIGRP is unable to
resolve routes for long periods.
Step 16 Configure R3 and R4 internal routers as EIGRP stubs.
Verification
Step 17 Examine the detailed EIGRP neighbor information with the show ip eigrp neighbors detail
command on R1 and R2 router. R1 router recognizes R3 router as an EIGRP stub and R2 router
recognizes R4 router as an EIGRP stub.
R1#show ip eigrp neighbors detail
Type
(sec) (ms) Cnt Num
2 10.1.1.3 Fa0/0 12 00:00:16 403 2418 0 66
Version 12.2/1.2, Retrans: 0, Retries: 0
Stub Peer Advertising ( CONNECTED SUMMARY ) Routes
0 172.31.1.3 Se0/0.2 162 00:07:02 46 2280 0 53
1 10.1.0.2 Se0/0.1 14 00:24:04 36 2280 0 212
Printout 16: Detailed EIGRP neighbor information on R1 router
R2#show ip eigrp neighbors detail
Type
(sec) (ms) Cnt Num
1 10.1.2.4 Fa0/0 11 00:01:25 3 200 0 131
Stub Peer Advertising ( CONNECTED SUMMARY ) Routes
0 172.31.1.3 Se0/0.2 161 00:06:53 40 2280 0 52
2 10.1.0.1 Se0/0.1 11 00:24:50 38 2280 0 152
Printout 17: Detailed EIGRP neighbor information on R2 router
Step 18 To examine the benefits of EIGRP stub, enable EIGRP debugging on R4 router with the debug
ip eigrp command. Shut down the S0/0.1 link between R1 and R2 routers. Notice that no queries
are now being sent to the R4 internal router.
R4#debug ip eigrp
IP-EIGRP Route Events debugging is on
R4#
Printout 18: EIGRP debugging output on R4 router
Step 19 Disable the debugging of EIGRP operation on R4 router and re-enable the connection between
R1 and R2 edge routers.
Task 5: Configuring the EIGRP Default Route
To further improve the stability and convergence speed, you will minimize the update traffic sent
to internal routers and minimize their routing tables. To achieve that, you will announce only a
default route via EIGRP and filter all specific routes to internal routers
Step 20 Announce only a default route from R1 and R2 edge routers to R3 and R4 internal routers by
using manual summarization.
Verification
Step 21 Check the routing table of R3 and R4 routers. The routers have now learned only a default route
from edge routers and connected routes from the other internal router. The more specific routes
from edge routers have been filtered out by the summarization.
R3#show ip route
...

Gateway of last resort is 10.1.1.1 to network 0.0.0.0

D 10.1.2.0 [90/40514560] via 10.1.3.4, 00:45:30, Serial0/0.1
D* 0.0.0.0 0.0.0.0 [90/30720] via 10.1.1.1, 00:39:02, FastEthernet0/0
Review Questions
What is the default administrative distance for EIGRP?
__________________________________________________________________
What kind of load balancing does EIGRP support?
__________________________________________________________________
Which parameters does EIGRP use by default to calculate route metric?
__________________________________________________________________
What can be deployed to improve EIGRP scalability?
__________________________________________________________________
Lab Topology
Routers in your lab are connected according to the setup in the following figure. The light-gray
routers (BBR1 and BBR3) in the figure are accessible via telnet only.

Figure 3: Lab Topology
The routers have different roles as detailed in the following table:
Router name Router role in the laboratory
BBR1, BBR3 Core routers
R1, R2 Edge routers
R3, R4 Internal routers
Table 2: Roles of routers in topology
The routers are connected with Ethernet and Frame Relay links the first serial interface of each
router is connected to a Frame Relay switch, which is simulated by a router (not included in the
picture) that is pre-configured and is not accessible during the lab. The DLCI values for
individual sub-interface Frame Relay connections are given in the following table:
Source router DLCI IP address Destination router DLCI IP address
BBR1 236 172.31.1.3 R1 263 172.31.1.1
BBR1 331 172.31.1.3 R2 313 172.31.1.2
BBR1 130 10.254.0.1 BBR3 103 10.254.0.3
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
Table 3: Frame Relay DLCI values
Addressing and Routing
This section contains information on IP addressing ranges and EIGRP routing used in the remote
lab.
Note IP addressing and core routing have been pre-configured to allow you to focus exclusively on
the objectives of the exercise.
IP Addressing Scheme
The addressing of lab exercise routers uses the following IP allocation scheme:
Parameter Value
WAN subnet between core and edge routers 172.31.1.0/24
Core network 10.254.0.0/24
LAN subnet between R1 and R3 10.1.1.0/24
R1 to R2 point-to-point connection 10.1.0.0/24
Table 4: Network address space
The actual addresses used on WAN and LAN links configured on the Lab exercise routers are
displayed in the following figure:

Figure 4: Addressing of Lab exercise routers
Note The address shown in a callout pointing to a router interface is the IP address configured on
that interface.
Existing EIGRP Routing
EIGRP is used as the routing protocol between core BBR1 router and R1, R2 edge routers. The
existing EIGRP routing configuration on BBR1 is shown below:
interface Serial 0/0.2 multipoint
bandwidth 64
no ip split-horizon eigrp 1
!
router eigrp 1
network 10.254.0.0 0.0.0.255
network 172.31.0.0
no auto-summary
Printout 20: EIGRP routing on BBR1 router
Copyright 2006, NIL Data Communications Configuring and Tuning EIGRP Lab Solutions 15
BSCI
Configuring and Tuning
EIGRP
Lab Solutions
Lab Solution
Task 1: Configuring Basic EIGRP
The following commands need to be entered on R1and R2 routers:
interface Serial0/0.1 point-to-point
bandwidth 64
!
interface Serial0/0.2 multipoint
bandwidth 64
!
router eigrp 1
network 10.0.0.0
network 172.31.1.0
no auto-summary
Configuration 1: EIGRP configuration on R1 and R2 routers
bandwidth 64
!
router eigrp 1
network 10.0.0.0
no auto-summary
Configuration 2: EIGRP configuration on R3 and R4 routers
16 Configuring and Tuning EIGRP Lab Solutions Copyright 2006, NIL Data Communications
Task 2: Influence EIGRP Path Selection
The following commands need to be entered on R1 router:
delay 2500
Configuration 3: Delay adjustment on R1 router
Task 3: Improve EIGRP Core Scalability
The following commands need to be entered on R1 and R2 routers:
ip summary-address eigrp 1 10.1.0.0 255.255.0.0
Configuration 4: EIGRP summarization on R1 and R2 routers
Task 4: Configuring EIGRP Stub
router eigrp 1
eigrp stub
Configuration 5: EIGRP stub configuration on R3 and R4 routers
Task 5: Configuring the EIGRP Default Route
interface FastEthernet0/0
ip summary-address eigrp 1 0.0.0.0 0.0.0.0
Configuration 6: EIGRP default route origination on R1 and R2 routers
Answers to Review Questions
Q1: What is the default administrative distance for EIGRP?
A1: EIGRP uses two values for administrative distance. Internal routes have administrative 90,
external routes have administrative distance 170.
Q2: What kind of load balancing does EIGRP support?
A2: EIGRP supports equal-cost load balancing by default and non-equal-cost load balancing.
Q3: Which parameters does EIGRP use by default to calculate route metric?
A3: Bandwidth and delay.
Q4: What can be deployed to improve EIGRP scalability?
A4: EIGRP summarization and EIGRP stub feature.
Copyright 2006, NIL Data Communications Configuring and Examining OSPF in a Single Area 17
BSCI
Configuring and Examining
OSPF in a Single Area
Objective
In this exercise, you will deploy OSPF routing in your network by enabling OSPF on all WAN
links (Frame Relay sub-interfaces) and all LAN links within your network as shown in the
following figure.

Figure 5: Basic OSPF deployment
You will improve the stability of OSPF operation by configuring loopback interfaces and OSPF
router IDs. After configuring basic OSPF routing, you will examine the established OSPF
adjacencies and IP routing tables and check the operation of OSPF.
Then you will reconfigure OSPF on LAN links to influence OSPF operation and Designated
Router (DR) election and observe the election process. Next you will fine tune the OSPF costs so
that the link between R3 and R4 routers will be used only in case of a R1 to R2 link failure.
18 Configuring and Examining OSPF in a Single Area Copyright 2006, NIL Data Communications

Figure 6: Influencing the primary/backup configuration
Configure your routers with OSPF routing protocol and stable OSPF router IDs.
Explore OSPF packet types.
Influence OSPF DR and BDR election on LAN.
Influence OSPF route selection by changing OSPF link cost.
Command List
Command Task
clear ip ospf process Resets the OSPF process.
debug ip ospf events Shows OSPF process operation.
ip address ip-address ip-network-
mask
Specify the IP address on an interface.
ip ospf cost value Changes the OSPF link cost.
ip ospf priority value Changes the OSPF router priority to value.
network ip-address wildcard area
area-number
Specifies the interfaces on which to run OSPF, and
their areas.
ping destination Performs ping to a destination address.
router ospf process-ID Enables OSPF with a process ID of process-ID.
router-id value Configures OSPF router ID.
show ip ospf Displays general information about the OSPF routing
process.
show ip ospf interface Displays OSPF-specific information about an
interface.
show ip ospf neighbor Display information about OSPF neighbors.
show ip route Display the IP routing table.
traceroute destination Performs traceroute to a destination address.
undebug all Turn off debugging.
Table 5: Configuration and monitoring commands used in the Configuring and
Examining OSPF in a Single Area Lab exercise
Task 1: Configuring Single Area OSPF
In this task, you will enable OSPF routing protocol in your network and examine the OSPF
operation.
Step 22 Enable OSPF with the process ID 1 on all interfaces on R3 and R4 routers. Place all interfaces in
OSPF Area 0. To avoid problems in later tasks, use a network statement for 10.1.0.0 network
rather than the entire 10.0.0.0 network.
Step 23 Enable OSPF with the process ID 1 also on all interfaces on R1 and R2 routers. Place all
interfaces in OSPF Area 0. To avoid problems in later tasks, use a network statement for 10.1.0.0
network rather than the entire 10.0.0.0 network.
Note Enabling OSPF on an interface can be done by using the network router configuration
command or the ip ospf process-id area area-id interface configuration command available
since IOS 12.3(11)T.
Verification
Step 24 Verify that you have full connectivity within your network using the ping command. Make sure
that you can ping all the other routers within your network.
Step 25 Examine the routing table of your routers. Since you have only one OSPF area, you will see only
intra-area (O) OSPF routes. Using the show ip route command, you should see the outputs
similar to the following printouts:
R1#show ip route
...


O 10.1.3.0 [110/1563] via 10.1.1.3, 00:02:15, FastEthernet0/0
O 10.1.2.0 [110/1563] via 10.1.0.2, 00:02:15, Serial0/0.1
R3#show ip route
...


O 10.1.2.0 [110/1563] via 10.1.3.4, 00:02:46, Serial0/0.1
O 10.1.0.0 [110/1563] via 10.1.1.1, 00:02:46, FastEthernet0/0
Step 26 Check OSPF router IDs on your routers using the show ip ospf command. The router ID is the
highest loopback IP address or the highest active IP address on the router. The command also
reveals the OSPF areas that the router participates in and the number of interfaces in a certain
area.
R2#show ip ospf
Routing Process "ospf 1" with ID 10.1.2.2
Supports only single TOS(TOS0) routes
Supports opaque LSA
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
External flood list length 0
Area BACKBONE(0)
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm executed 3 times
Area ranges are
Number of LSA 6. Checksum Sum 0x2FF92
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
Printout 23: OSPF process information on R2 router
Use the following table to write down OSPF router IDs of your routers.
Router Router ID
R1
R2
R3
R4
Table 1: Router IDs
Step 27 Check the established OSPF adjacencies on the R1 router with the show ip ospf neighbor
command. The neighbors states of R3 and R2 routers should be FULL and the R3 router should
be the DR router on the Ethernet connection between R1 and R3 routers.
R1#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address
Interface
10.1.2.2 1 FULL/ - 00:00:37 10.1.0.2
Serial0/0.1
10.1.3.3 1 FULL/DR 00:00:36 10.1.1.3
FastEthernet0/0
Printout 24: OSPF adjacency information on R1 router
Task 2: Configuring Stable OSPF Router ID
You must change Router IDs on your routers to achieve more stable OSPF operation. You will
achieve that by configuring loopback interfaces on some routers and OSPF router IDs on other
routers.
Step 28 Configure IP address 10.200.200.13/32 on loopback0 interface on R3 router.
Step 29 Configure IP address 10.200.200.14/32 on loopback0 interface on R4 router.
Step 30 Configure OSPF router ID 10.0.0.11 on R1 router.
Step 31 Configure OSPF router ID 10.0.0.12 on R2 router.
Note The ability to manually set the OSPF router ID was introduced in Cisco IOS Release 12.0(1)T.
Verification
Step 32 Check again the OSPF router IDs of all your routers and compare the values with the values from
the previous task.
Notice that router IDs have not changed. This is a stability feature of a Cisco IOS. If router ID
changed, the link-state advertisements (LSAs) would be invalid and the routers would have to re-
converge.
To change the router IDs on routers R3 and R4, where you configured loopback addresses, you
would have to reload the router or disable and then re-enable the OSPF process.
To change the router IDs on routers R1 and R2, where you configured them manually, you
would have to reset the OSPF process as explained in the following steps.
R2#show ip ospf
Supports opaque LSA
Area BACKBONE(0)
Area ranges are
Number of LSA 6. Checksum Sum 0x2FF92
Flood list length 0
Printout 25: Unchanged router ID on R2 router
Step 33 Save the OSPF configuration on R3 and R4 routers to a text file and disable the OSPF on both
routers using the no router ospf 1 command. Use the saved OSPF configuration and apply the
configuration back to your routers. Check the router IDs of R3 and R4 routers. Notice that router
IDs have changed and are now set to the IP address of a loopback0 interface.
R3#show ip ospf
Supports opaque LSA
Area BACKBONE(0)
Area ranges are
Number of LSA 4. Checksum Sum 0x15ABD
Flood list length 1
Printout 26: New router ID on R3 router
Step 34 Reset the OSPF process with the clear ip ospf process command on R1 and R2 routers and then
check the router IDs. The router IDs have changed to the manually configured values.
R1#show ip ospf
Supports opaque LSA
Area BACKBONE(0)
Area ranges are
Number of LSA 9. Checksum Sum 0x38A27
Flood list length 4
Printout 27: New router ID on R1 router
Step 35 Verify that OSPF adjacencies are in FULL state on all your routers.
Task 3: Understanding OSPF Packet Types
In this task, you will observe the creation of OSPF adjacency and packets that are exchanged
upon neighbor relationship being established.
Verification
Step 36 Shut down the Fe0/0 interface on R1 router.
Step 37 Enable the debugging of OSPF events on R1 router with the debug ip ospf events command to
examine OSPF packet types.
Step 38 Reset the OSPF process with the clear ip ospf process command and observe how R1
establishes OSPF adjacency with R2 router via S0/0.1 interface. The routers start exchanging
OSPF hello packets and reach the 2-WAY OSPF state when they become aware of each other.
Next they have to agree on who will lead the exchange of DBD packets this is called the
EXSTART state. In this case, the R2 router is a master since it has a higher router ID and R1
router is a slave. Afterwards they trade the DBD packets and synchronize their view of the OSPF
area in the EXCHANGE state. The end of the OSPF adjacency establishment process is indicated
with routers being in the OSPF FULL state.
R1#clear ip ospf process
Reset ALL OSPF processes? [no]: yes
R1#
10:24:24: OSPF: Flushing External Links
10:24:24: OSPF: Flushing Opaque AS Links
10:24:24: OSPF: Flushing Link states in area 0
10:24:24: OSPF: Interface Serial0/0.1 going Down
10:24:24: %OSPF-5-ADJCHG: Process 1, Nbr 10.0.0.12 on Serial0/0.1 from
FULL to DOWN, Neighbor Down: Interface down or detached
10:24:24: OSPF: Interface Serial0/0.1 going Up
10:24:24: OSPF: i_up : interface is down
10:24:24: OSPF: Rcv hello from 10.0.0.12 area 0 from Serial0/0.1 10.1.0.2
10:24:24: OSPF: 2 Way Communication to 10.0.0.12 on Serial0/0.1, state
2WAY
10:24:24: OSPF: Send DBD to 10.0.0.12 on Serial0/0.1 seq 0xF80 opt 0x42
flag 0x7 len 32
10:24:24: OSPF: End of hello processing
10:24:24: OSPF: Rcv DBD from 10.0.0.12 on Serial0/0.1 seq 0x1260 opt 0x42
flag 0x7 len 32 mtu 1500 state EXSTART
10:24:24: OSPF: NBR Negotiation Done. We are the SLAVE
10:24:24: OSPF: Send DBD to 10.0.0.12 on Serial0/0.1 seq 0x1260 opt 0x42
flag 0x0 len 32
flag 0x3 len 132 mtu 1500 state EXCHANGE
flag 0x0 len 32
10:24:24: OSPF: Database request to 10.0.0.12
10:24:24: OSPF: sent LS REQ packet to 10.1.0.2, length 60
flag 0x1 len 32 mtu 1500 state EXCHANGE
10:24:24: OSPF: Exchange Done with 10.0.0.12 on Serial0/0.1
flag 0x0 len 32
10:24:24: OSPF: Synchronized with 10.0.0.12 on Serial0/0.1, state FULL
10:24:24: %OSPF-5-ADJCHG: Process 1, Nbr 10.0.0.12 on Serial0/0.1 from
LOADING to FULL, Loading Done
Printout 28: R1 to R2 OSPF adjacencies establishment on R1 router
Step 39 Shut down the S0/0.1 interface and re-enable the Fe0/0 on R1 router.
Step 40 Reset the OSPF process with the clear ip ospf process command and observe how R1
establishes OSPF adjacency with R3 router via Fe0/0 interface. The establishment of OSPF
adjacency is very similar to the previous case. The difference is that routers here elect OSPF DR
and BDR router, since they peer over a broadcast network.
R1#clear ip ospf process
Reset ALL OSPF processes? [no]: yes
R1#
10:38:31: OSPF: Flushing External Links
10:38:31: OSPF: Flushing Opaque AS Links
10:38:31: OSPF: Flushing Link states in area 0
10:38:31: OSPF: Interface FastEthernet0/0 going Down
10:38:31: OSPF: Neighbor change Event on interface FastEthernet0/0
10:38:31: OSPF: DR/BDR election on FastEthernet0/0
10:38:31: OSPF: Elect BDR 0.0.0.0
10:38:31: OSPF: Elect DR 10.200.200.13
10:38:31: OSPF: Elect BDR 0.0.0.0
10:38:31: OSPF: Elect DR 10.200.200.13
10:38:31: DR: 10.200.200.13 (Id) BDR: none
10:38:31: %OSPF-5-ADJCHG: Process 1, Nbr 10.200.200.13 on FastEthernet0/0
from FULL to DOWN, Neighbor Down: Interface down or detached
10:38:31: OSPF: Elect BDR 0.0.0.0
10:38:31: OSPF: Elect DR 0.0.0.0
10:38:31: DR: none BDR: none
10:38:31: OSPF: Remember old DR 10.200.200.13 (id)
10:38:31: OSPF: i_up : interface is down
10:38:31: OSPF: Interface FastEthernet0/0 going Up
10:38:36: OSPF: Rcv hello from 10.200.200.13 area 0 from FastEthernet0/0
10.1.1.3
10:38:36: OSPF: 2 Way Communication to 10.200.200.13 on FastEthernet0/0,
state 2WAY
10:38:36: OSPF: Backup seen Event before WAIT timer on FastEthernet0/0
10:38:36: OSPF: Elect BDR 10.0.0.11
10:38:36: OSPF: Elect DR 10.200.200.13
10:38:36: OSPF: Elect BDR 10.0.0.11
10:38:36: OSPF: Elect DR 10.200.200.13
10:38:36: DR: 10.200.200.13 (Id) BDR: 10.0.0.11 (Id)
10:38:36: OSPF: Send DBD to 10.200.200.13 on FastEthernet0/0 seq 0x253A
opt 0x42 flag 0x7 len 32
10:38:36: OSPF: Rcv DBD from 10.200.200.13 on FastEthernet0/0 seq 0x103E
opt 0x42 flag 0x7 len 32 mtu 1500 state EXSTART
10:38:36: OSPF: NBR Negotiation Done. We are the SLAVE
10:38:36: OSPF: Send DBD to 10.200.200.13 on FastEthernet0/0 seq 0x103E
10:38:36: OSPF: Rcv DBD from 10.200.200.13 on FastEthernet0/0 seq 0x103F
opt 0x42 flag 0x3 len 112 mtu 1500 state EXCHANGE
10:38:36: OSPF: Send DBD to 10.200.200.13 on FastEthernet0/0 seq 0x103F
10:38:36: OSPF: Rcv DBD from 10.200.200.13 on FastEthernet0/0 seq 0x1040
opt 0x42 flag 0x1 len 32 mtu 1500 state EXCHANGE
10:38:36: OSPF: Exchange Done with 10.200.200.13 on FastEthernet0/0
10:38:36: OSPF: Send DBD to 10.200.200.13 on FastEthernet0/0 seq 0x1040
10:38:36: OSPF: Synchronized with 10.200.200.13 on FastEthernet0/0, state
FULL
from LOADING to FULL, Loading Done
10.1.1.3
10:38:46: OSPF: Elect BDR 10.0.0.11
10:38:46: OSPF: Elect DR 10.200.200.13
10:38:46: DR: 10.200.200.13 (Id) BDR: 10.0.0.11 (Id)
Printout 29: R1 to R2 OSPF adjacencies establishment on R1 router
Step 41 Disable the debugging of OSPF events on R1 router and re-enable S0/0.1.
Task 4: Understanding OSPF DR and BDR Elections
Now you will influence the election of DR and BDR routers on LAN by manually configuring
the OSPF priority on proper interfaces.
Step 42 First check the default OSPF priority and current DR on LAN network between R2 and R4
routers with the show ip ospf interface command on R4 router. R4 router is the OSPF DR and
its default OSPF priority is 1:
R4#show ip ospf interface FastEthernet 0/0
FastEthernet0/0 is up, line protocol is up
Internet Address 10.1.2.4 255.255.255.0, Area 0
Process ID 1, Router ID 10.200.200.14, Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 10.200.200.14, Interface address 10.1.2.4
Backup Designated router (ID) 10.0.0.12, Interface address 10.1.2.2
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:02
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.0.0.12 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
R4#
Printout 30: OSPF information for interface Fe0/0 on R4 router
Step 43 Influence the election of DR by setting the OSPF priority to 0 on R4 router LAN interface.
Setting OSPF priority to 0 removes the router from the election process.
Verification
Step 44 Disable the Fe0/0 interface on R2 and R4 routers and S0/0.1 interface on R4 router. Enable the
debugging of OSPF events on R4 router with debug ip ospf events command to examine OSPF
DR election process.
Step 45 Enable the Fe0/0 interfaces on R2 and R4 routers and observe the election process. Since R4
router has OSPF priority set to 0, R2 router is the only candidate for the role of the DR. Notice
that DR is elected, while BDR is not elected since there is no other candidate router present on
the LAN network. The debug output should resemble the following printout.
11:07:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface
FastEthernet0/0, changed state to up
11:07:57: OSPF: Interface FastEthernet0/0 going Up
10.1.2.2
11:08:03: OSPF: 2 Way Communication to 10.0.0.12 on FastEthernet0/0,
state 2WAY
10.1.2.2
10.1.2.2
10.1.2.2
11:08:33: OSPF: Backup seen Event before WAIT timer on FastEthernet0/0
11:08:33: OSPF: Elect BDR 0.0.0.0
11:08:33: OSPF: Elect DR 10.0.0.12
11:08:33: DR: 10.0.0.12 (Id) BDR: none
11:08:33: OSPF: Send DBD to 10.0.0.12 on FastEthernet0/0 seq 0x1891 opt
0x42 flag 0x7 len 32
11:08:33: OSPF: Rcv DBD from 10.0.0.12 on FastEthernet0/0 seq 0x1891 opt
0x42 flag 0x2 len 132 mtu 1500 state EXSTART
11:08:33: OSPF: NBR Negotiation Done. We are the MASTER
11:08:33: OSPF: Send DBD to 10.0.0.12 on FastEthernet0/0 seq 0x1892 opt
0x42 flag 0x3 len 132
0x42 flag 0x0 len 32 mtu 1500 state EXCHANGE
11:08:33: OSPF: Send DBD to 10.0.0.12
R4(config-if)#on FastEthernet0/0 seq 0x1893 opt 0x42 flag 0x1 len 32
0x42 flag 0x0 len 32 mtu 1500 state EXCHANGE
11:08:33: OSPF: Exchange Done with 10.0.0.12 on FastEthernet0/0
11:08:33: OSPF: Synchronized with 10.0.0.12 on FastEthernet0/0, state
FULL
from LOADING to FULL, Loading Done
Printout 31: DR election process
Step 46 Verify the results of the election process by examining the OSPF interface information on R4
router. Notice that no router was elected for the BDR role.
R4#show ip ospf interface FastEthernet 0/0
Transmit Delay is 1 sec, State DROTHER, Priority 0
No backup designated router on this network
Next 0x0(0)/0x0(0)
Adjacent with neighbor 10.0.0.12 (Designated Router)
R4#
Printout 32: OSPF information for Fe0/0 interface on R4 router
Step 47 Disable the debugging of OSPF events on R4 router and re-enable Fe0/0 and S0/0.1 interfaces.
Task 5: Configuring OSPF Cost
The connection between R1 and R2 routers should be used as a primary connection for the traffic
between the two LANs. The connection between R3 and R4 routers for the traffic between the
LANs should only be used in case of a primary connection failure. To achieve that you will
change the OSPF cost to appropriate value.
Step 48 First check the cost and next-hop to reach 10.1.2.0/24 network on R3 router. The network is
reachable through S0/0.1 with the cost of 1563, where 1562 is the cost of serial connection to R4
and 1 is the initial cost of the directly connected LAN network.
R3#show ip route 10.1.2.0 255.255.255.0
Known via "ospf 1", distance 110, metric 1563, type intra area
Last update from 10.1.3.4 on Serial0/0.1, 00:04:56 ago
* 10.1.3.4, from 10.0.0.12, 00:04:56 ago, via Serial0/0.1
Printout 33: Routing information for 10.1.2.0 /24 network on R3
Step 49 Check the cost and next-hop to reach 10.1.1.0/24 network on R4 router. The result is the same as
on R3 router. The network is reachable through S0/0.1 with the cost of 1563, where 1562 is the
cost of serial connection to R3 and 1 is the initial cost of the directly connected LAN network.
R4#show ip route 10.1.1.0 255.255.255.0
Last update from 10.1.3.3 on Serial0/0.1, 00:03:55 ago
* 10.1.3.3, from 10.200.200.13, 00:03:55 ago, via Serial0/0.1
Printout 34: Routing information for 10.1.1.0/24 network on R4
Step 50 Increase the OSPF cost of S0/0.1 interface on R3 and R4 routers to 2000.
Verification
Step 51 Perform traceroute from R3 router to 10.1.2.4. You will see that traffic is taking the path
through the primary connection between the two LANs.
R3#traceroute 10.1.2.4

Type escape sequence to abort.
Tracing the route to 10.1.2.4

1 10.1.1.1 0 msec 0 msec 4 msec
2 10.1.0.2 28 msec 28 msec 28 msec
3 10.1.2.4 28 msec * 28 msec
Printout 35: Traceroute to 10.1.2.4 from R3
Step 52 Examine the routing information for the 10.1.2.0/24 network on R3 router and for the 10.1.1.0/24
network on R4 router. The networks are no longer accessible via backup connection.
R3#show ip route 10.1.2.0 255.255.255.0
Last update from 10.1.1.1 on FastEthernet0/0, 00:56:30 ago
* 10.1.1.1, from 10.0.0.12, 00:56:30 ago, via FastEthernet0/0
R4#show ip route 10.1.1.0 255.255.255.0
Last update from 10.1.2.2 on FastEthernet0/0, 00:57:46 ago
* 10.1.2.2, from 10.200.200.13, 00:57:46 ago, via FastEthernet0/0
Review Questions
What is the default administrative distance for OSPF?
__________________________________________________________________
What is the OSPF metric based on?
__________________________________________________________________
Does OSPF support load balancing by default?
__________________________________________________________________
What is the default OSPF router priority used in DR/BDR election?
__________________________________________________________________
Lab Topology
Routers in your lab are connected according to the setup in the following figure.

R1, R2 Edge routers
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
This section contains information on IP addressing ranges used in the remote lab.
Note IP addressing, except loopback addresses, has been pre-configured to allow you to focus
exclusively on the objectives of the exercise.
Parameter Value
R1 to R2 point-to-point connection subnet 10.1.0.0/24
R3 loopback interface 10.200.200.13/32

Note The addresses shown in a box overlaying the router are the loopback addresses configured on
the router. The address shown in a callout pointing to a router interface is the IP address
configured on that interface.


Copyright 2006, NIL Data Communications Configuring and Examining OSPF in a Single Area Lab Solutions 33
BSCI
Configuring and Examining
OSPF in a Single Area
Lab Solutions
Lab Solution
Task 1: Configuring Single Area OSPF
The following commands need to be entered on R1, R2, R3 and R4 routers:
router ospf 1
network 10.1.0.0 0.0.255.255 area 0
Configuration 7: OSPF configuration on R1, R2, R3 and R4 routers
The following table lists the OSPF router IDs on R1, R2, R3 and R4 routers.
Router Router ID
R1 10.1.1.1
R2 10.1.2.2
R3 10.1.3.3
R4 10.1.3.4
Table 9: Router IDs
Task 2: Configuring Stable OSPF Router ID
router ospf 1
router-id 10.0.0.11
Configuration 8: OSPF router ID configuration on R1 router
34 Configuring and Examining OSPF in a Single Area Lab Solutions Copyright 2006, NIL Data Communications
router ospf 1
router-id 10.0.0.12
Configuration 9: OSPF router ID configuration on R2 router
interface Loopback0
ip address 10.200.200.13 255.255.255.255
!
no router ospf 1
!
router ospf 1
network 10.1.0.0 0.0.255.255 area 0
Configuration 10: Loopback configuration on R3 router
interface Loopback0
ip address 10.200.200.14 255.255.255.255
!
no router ospf 1
!
router ospf 1
network 10.1.0.0 0.0.255.255 area 0
Configuration 11: Loopback configuration on R4 router
Task 4: Understanding OSPF DR and BDR Elections
ip ospf priority 0
Configuration 12: OSPF priority adjustment on R4 router
Task 5: Configuring OSPF Cost
ip ospf cost 2000
Configuration 13: OSPF link cost adjustment on R3 and R4 routers
Answers to Review Questions
Q1: What is the default administrative distance for OSPF?
A1: The default OSPF administrative distance is 110.
Q2: What is the OSPF metric based on?
A2: OSPF uses cost for metric. By default, cost is calculated as the inverse value of bandwidth in
bits per second, multiplied by 10
8
.
Q3: What kind of load balancing does OSPF support?
Copyright 2006, NIL Data Communications Configuring and Examining OSPF in a Single Area Lab Solutions 35
A3: OSPF supports only equal-cost load balancing.
Q4: What is the default OSPF router priority used in DR/BDR election?
A4: Default OSPF router priority is 1.

36 Configuring and Examining OSPF in a Single Area Lab Solutions Copyright 2006, NIL Data Communications

Copyright 2006, NIL Data Communications Configuring OSPF for Frame Relay Environment 37
BSCI
Configuring OSPF for Frame
Relay Environment
Objective
In this exercise, you will configure a multi-area OSPF network and focus on an OSPF operation
in a Frame Relay environment. You will configure different OSPF Non-Broadcast Multiple
Access (NBMA) types of operation through the lab exercise and inspect OSPF behavior within
the network.
Configure and examine OSPF non-backbone area over Frame Relay point-to-point and
Ethernet interfaces.
Configure and examine OSPF backbone area over Frame Relay using the NBMA OSPF
network type.
Configure and examine OSPF backbone area over Frame Relay using the point-to-multipoint
OSPF network type.
The following figure shows the logical topology used for this lab.
38 Configuring OSPF for Frame Relay Environment Copyright 2006, NIL Data Communications

Figure 9: Configuring OSPF for Frame Relay Environment Lab exercise logical
topology
Command List
Command Task
ip ospf network {broadcast | non-broadcast
| {point-to-multipoint [non-broadcast]}}
Configures the OSPF network type to a type
other than the default for a given media.
ip ospf priority value Changes the OSPF router priority to value.
neighbor ip-address Configures OSPF routers interconnecting to
non-broadcast networks
network ip-address wildcard area area-
number
Specifies the interfaces on which to run
OSPF, and their areas.
router ospf process-ID Enables OSPF with a process ID of process-
ID.
show ip ospf adatabase Displays the content of OSPF database.
interface.
show ip ospf neighbor Displays information about OSPF neighbors.
show ip route Displays the IP routing table.
Table 10: Configuration and monitoring commands used in the Configuring
OSPF for Frame Relay Environment Lab exercise
Task 1: Configuring Non-Backbone OSPF Area
Step 1 Start the OSPF with the process ID 1 at R3 and R4 routers and place all active interfaces in the
OSPF area 1.
Step 2 Start the OSPF with the process ID 1 at R1 and R2 routers also and place only S0/0.1 and Fe0/0
interfaces in the OSPF area 1.
all printouts in the lab were taken on routers with Ethernet interfaces, the default bandwidth
and the default delay on Ethernet interfaces were changed to FastEthernet interface default
values for compatibility reasons.
Verification
Step 3 Begin the verification by checking that you have full connectivity within the OSPF area 1 using
the ping command. Make sure that you can ping all interfaces within OSPF area 1.
Step 4 Examine the OSPF interface information at R3 router with the show ip ospf interface command
for interfaces S0/0.1 and Fe0/0. Focus on network type, hello and dead interval fields. The
default OSPF network type for any point-to-point interface including Frame Relay point-to-point
subinterfaces is point-to-point. On broadcast media the default OSPF network type is broadcast.
R3#show ip ospf interface
Loopback0 is up, line protocol is up
Process ID 1, Router ID 10.200.200.13, Network Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serial0/0.1 is up, line protocol is up
Process ID 1, Router ID 10.200.200.13, Network Type POINT_TO_POINT,
Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT,
Next 0x0(0)/0x0(0)
Adjacent with neighbor 10.200.200.14
Ethernet0/0 is up, line protocol is up
Backup Designated router (ID) 10.200.200.11, Interface address 10.1.1.1
Next 0x0(0)/0x0(0)
Printout 38: OSPF interface information on R3 router
Step 5 Take a look at the OSPF neighbor relationships at R3 router. The OSPF operation over OSPF
point-to-point network type does not require DR and BDR routers as with broadcast network
type.

Interface
10.200.200.14 1 FULL/ - 00:00:36 10.1.3.4
Serial0/0.1
10.200.200.11 1 FULL/BDR 00:00:30 10.1.1.1
Ethernet0/0
Printout 39: OSPF neighbors on R3 router
Step 6 Examine routing tables of R1, R2, R3 and R4 routers. You should see that routing table is
populated with the OSPF learned routes as in the exemplary output from R3 router shown below.
R3#show ip route
...


O 10.200.200.14 255.255.255.255
[110/65] via 10.1.3.4, 00:04:25, Serial0/0.1
C 10.200.200.13 255.255.255.255 is directly connected, Loopback0
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.3.4, 00:04:25,
Serial0/0.1
C 10.1.1.0 255.255.255.0 is directly connected, Ethernet0/0
O 10.1.0.0 255.255.255.0 [110/65] via 10.1.1.1, 00:04:25,
Ethernet0/0
Task 2: Using NBMA OSPF Network Type over Frame Relay
Step 7 Enable OSPF with the process ID 1 at BBR1 core router and place all interfaces in the OSPF area
0.
Step 8 Place the S0/0.2 and Loopback0 interfaces in the OSPF area 0 at R1 and R2 routers.
Verification
Step 9 Check the S0/0.2 OSPF interface information at R1, R2 and BBR1 routers with the show ip ospf
interface command.
Note After enabling OSPF on BBR1 interfaces, wait for two minutes before issuing the show ip
ospf interface command on the BBR. This is the value of the Wait timer used for DR/BDR
election on an OSPF interface. After Wait timer expiration, the router proclaims itself as the
DR over that interface.
Pay special attention to network type, hello and dead interval, state and priority. The routers are
connected via Frame Relay point-to-multipoint subinterfaces with the OSPF NMBA network
type, which is a default for such interfaces. Notice that OSPF interface state on all three routers is
indicating that each router is DR on that segment, but no OSPF adjacency was formed through
the interface.
BBR1#show ip ospf interface serial 0/0.2
Process ID 1, Router ID 172.31.1.3, Network Type NON_BROADCAST, Cost:
1562
Next 0x0(0)/0x0(0)
Printout 41: S0/0.2 interface OSPF information on BBR1 router
Step 10 Now examine the OSPF neighbor table at BBR1 router. The router has established the adjacency
only with BBR3 router. You wont see OSPF adjacencies formed with R1 or R2 routers because
the OSPF neighbors are not discovered over interfaces with OSPF NMBA network type.
BBR1#show ip ospf neighbor

Interface
10.254.0.3 1 FULL/ - 00:00:33 10.254.0.3
Serial0/0.1
Printout 42: OSPF neighbor table on BBR1 router
Step 11 The OSPF database at BBR1 router is almost empty at the moment except for a two Type-1
LSAs also known as Router LSAs. Type-1 LSAs describe the routers BBR1 and BBR3 in area 0
and the state of their connected links. Check the OSPF database content with show ip ospf
database command.
BBR1#show ip ospf database

OSPF Router with ID (172.31.1.3) (Process ID 1)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link
count
10.254.0.3 10.254.0.3 535 0x80000004 0x574D 2
172.31.1.3 172.31.1.3 530 0x80000003 0x20C6 3
Printout 43: OSPF database on BBR1 router
Step 12 The consequence of an almost empty OSPF database on BBR1 is the routing table with no OSPF
learned routes. This can be verified with the show ip route command.
BBR1#show ip route
...


Task 3: Configuring OSPF Neighbor relationship and DR
Router for NBMA Network Type
The OSPF NBMA network type (called Non-broadcast in Cisco IOS) requires the manual
configuration of neighbors as well as election of DR and BDR routers. If a Frame Relay network
is fully meshed, the neighbors can be configured on all routers or at least on DR and BDR
routers. In a hub and spoke topology only a hub router has a full connectivity to the spoke
routers. As a consequence only a hub router can play the DR role and it is enough to configure
neighbors on hub router only.
Step 13 Set the OSPF priority on S0/0.2 interfaces to 0 at R1 and R2 routers. The priority value of 0
prevents the routers from starting the election process for the DR and BDR role.
Step 14 Configure R1 and R2 as OSPF neighbors at BBR1 router.
Verification
Step 15 The first verification step is checking the status of S0/0.2 OSPF interface at R1, R2 and BBR1
routers with show ip ospf interface command. Because of the priority set at R1 and R2 routers,
the BBR1 became the DR. The printouts show the OSPF interface information for interfaces
S0/0.2 on routers BBR1, R1 and R2.
Process ID 1, Router ID 172.31.1.3, Network Type NON_BROADCAST, Cost:
1562
Next 0x0(0)/0x0(0)
Printout 45: S0/0.2 interface OSPF information on BBR1 router
R1#show ip ospf interface serial 0/0.2
Process ID 1, Router ID 10.200.200.11, Network Type NON_BROADCAST,
Cost: 64
Flush timer for old DR LSA due in 00:00:54
Next 0x0(0)/0x0(0)
Printout 46: S0/0.2 interface OSPF information on R1 router
R2#show ip ospf interface serial 0/0.2
Process ID 1, Router ID 10.200.200.12, Network Type NON_BROADCAST,
Cost: 64
Flush timer for old DR LSA due in 00:00:33
Next 0x0(0)/0x0(0)
Printout 47: S0/0.2 interface OSPF information on R2 router
Step 16 Verify the state of OSPF adjacencies with show ip ospf neighbor command. The BBR1 router
has now formed the OSPF adjacency with R1 and R2 routers.

Interface
10.200.200.12 0 FULL/DROTHER 00:01:37 172.31.1.2
Serial0/0.2
10.200.200.11 0 FULL/DROTHER 00:01:55 172.31.1.1
Serial0/0.2
10.254.0.3 1 FULL/ - 00:00:31 10.254.0.3
Serial0/0.1
Printout 48: OSPF neighbors on BBR1 router

Interface
172.31.1.3 1 FULL/DR 00:01:45 172.31.1.3
Serial0/0.2
10.200.200.12 1 FULL/ - 00:00:35 10.1.0.2
Serial0/0.1
10.200.200.13 1 FULL/DR 00:00:34 10.1.1.3
Ethernet0/0

Interface
172.31.1.3 1 FULL/DR 00:01:38 172.31.1.3
Serial0/0.2
10.200.200.11 1 FULL/ - 00:00:38 10.1.0.1
Serial0/0.1
10.200.200.14 1 FULL/BDR 00:00:34 10.1.2.4
Ethernet0/0
Step 17 The OSPF database now contains a lot more information than before: Four Type-1 LSAs
describing R1, R2, BBR1 and BBR3 routers, one Type-2 LSA generated by the DR router
describing the multi-access Frame Relay network with attached routers, and several Type-3
LSAs generated by the ABR routers R1 and R2, describing the networks from the area 1.Check
the OSPF database content with show ip ospf database command.



count
10.200.200.11 10.200.200.11 35 0x80000003 0xBC91 2
10.200.200.12 10.200.200.12 23 0x80000003 0xD079 2
10.254.0.3 10.254.0.3 1265 0x80000004 0x574D 2
172.31.1.3 172.31.1.3 576 0x80000004 0x45CE 3

Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum
172.31.1.3 172.31.1.3 576 0x80000001 0xEA8D

Summary Net Link States (Area 0)

10.1.0.0 10.200.200.11 1252 0x80000001 0x1D2E
10.1.0.0 10.200.200.12 1240 0x80000001 0x1733
10.1.1.0 10.200.200.11 1252 0x80000001 0x99EF
10.1.1.0 10.200.200.12 1240 0x80000001 0x1632
10.1.2.0 10.200.200.11 1252 0x80000001 0x1137
10.1.2.0 10.200.200.12 1242 0x80000001 0x88FE
10.1.3.0 10.200.200.11 1253 0x80000001 0x641
10.1.3.0 10.200.200.12 1242 0x80000001 0xFF46
10.200.200.13 10.200.200.11 1253 0x80000001 0x2EBD
10.200.200.13 10.200.200.12 1242 0x80000001 0xAAFF
10.200.200.14 10.200.200.11 1253 0x80000001 0xA604
10.200.200.14 10.200.200.12 1242 0x80000001 0x1ECB
Step 18 The routing table on BBR1 router is now populated with OSPF learned routes. The output should
be similar to the following printout.
BBR1#show ip route
...


O 10.200.200.11 255.255.255.255
[110/1563] via 172.31.1.1, 00:00:54, Serial0/0.2
O IA 10.200.200.14 255.255.255.255
[110/1564] via 172.31.1.2, 00:00:54, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1563] via 172.31.1.2, 00:00:54, Serial0/0.2
O IA 10.200.200.13 255.255.255.255
[110/1564] via 172.31.1.1, 00:00:56, Serial0/0.2
O IA 10.1.3.0 255.255.255.0
[110/1627] via 172.31.1.1, 00:00:56, Serial0/0.2
[110/1627] via 172.31.1.2, 00:00:56, Serial0/0.2
O IA 10.1.2.0 255.255.255.0
[110/1563] via 172.31.1.2, 00:00:56, Serial0/0.2
O IA 10.1.1.0 255.255.255.0
[110/1563] via 172.31.1.1, 00:00:56, Serial0/0.2
O IA 10.1.0.0 255.255.255.0
[110/1626] via 172.31.1.1, 00:00:56, Serial0/0.2
[110/1626] via 172.31.1.2, 00:00:56, Serial0/0.2
Step 19 It looks like the OSPF NMBA network type is working for the hub and spoke topology. But the
pings from R1 to loopback on R2 and from R2 to loopback on R1 do not succeed.
R1#ping 10.200.200.12

Sending 5, 100-byte ICMP Echos to 10.200.200.12, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Printout 53: Ping from R1 router to R2 routers loopback interface.
R2#ping 10.200.200.11

.....
Printout 54: Ping from R2 router to R1 routers loopback interface.
Step 20 Checking the routing table with the show ip route command on R1 and R2 routers reveals the
reason. The routing table contains the route to the remote loopback with the next hop set to the
S0/0.2 interfaces IP address of the remote router. But that next-hop is not accessible since R1
cannot reach R2 over S0/0.2 interface and vice versa. This is because R1 has no frame-relay
mapping for the IP address of this next-hop, therefore layer 2 encapsulation will fail. The
conclusion is that a full mesh is required, in other words, direct connectivity between R1 and R2
routers should be available, because the loopback network appears to be one hop away.
R1#show ip route
...


O 10.200.200.14 255.255.255.255
[110/66] via 10.1.1.3, 00:25:04, Ethernet0/0
[110/66] via 10.1.0.2, 00:25:04, Serial0/0.1
O 10.200.200.12 255.255.255.255
[110/65] via 172.31.1.2, 00:04:52, Serial0/0.2
O 10.200.200.13 255.255.255.255
[110/2] via 10.1.1.3, 00:25:05, Ethernet0/0
O 10.1.3.0 255.255.255.0 [110/65] via 10.1.1.3, 00:25:05,
Ethernet0/0
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.0.2, 00:25:05,
Serial0/0.1
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.1.3, 00:04:54, Serial0/0.2
Printout 55: IP routing table output on R1 router
R2#show ip route
...


O 10.200.200.11 255.255.255.255
[110/65] via 172.31.1.1, 00:06:49, Serial0/0.2
O 10.200.200.14 255.255.255.255
[110/2] via 10.1.2.4, 00:27:01, Ethernet0/0
O 10.200.200.13 255.255.255.255
[110/66] via 10.1.2.4, 00:27:02, Ethernet0/0
[110/66] via 10.1.0.1, 00:27:02, Serial0/0.1
O 10.1.3.0 255.255.255.0 [110/65] via 10.1.2.4, 00:27:02,
Ethernet0/0
O 10.1.1.0 255.255.255.0 [110/65] via 10.1.0.1, 00:27:02,
Serial0/0.1
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.1.3, 00:06:50, Serial0/0.2
Printout 56: IP routing table output on R2 router
Task 4: Using Point-to-Multipoint OSPF Network Type over
Frame Relay
You have seen that the OSPF NBMA network type is not suitable for a partially meshed
topology. You will now use the OSPF point-to-multipoint representation.
Step 21 First, remove the manually configured OSPF neighbors at BBR1 router.
Step 22 Configure OSPF point-to-multipoint network type on S0/0.2 interfaces at R1, R2 and BBR1
routers.
Verification
Step 23 Start verification by inspecting the OSPF adjacencies on R1, R2 and BBR1 routers using the
show ip ospf neighbor command. The OSPF point-to-multipoint mode operates similar to OSPF
point-to-point mode. The DR and BDR routers are not required and the adjacencies are
established between the neighbors.

Interface
10.200.200.11 0 FULL/ - 00:01:44 172.31.1.1
Serial0/0.2
10.200.200.12 0 FULL/ - 00:01:52 172.31.1.2
Serial0/0.2
10.254.0.3 1 FULL/ - 00:00:33 10.254.0.3
Serial0/0.1

Interface
172.31.1.3 1 FULL/ - 00:01:58 172.31.1.3
Serial0/0.2
10.200.200.12 1 FULL/ - 00:00:37 10.1.0.2
Serial0/0.1
10.200.200.13 1 FULL/DR 00:00:35 10.1.1.3
Ethernet0/0

Interface
172.31.1.3 1 FULL/ - 00:01:56 172.31.1.3
Serial0/0.2
10.200.200.11 1 FULL/ - 00:00:34 10.1.0.1
Serial0/0.1
10.200.200.14 1 FULL/BDR 00:00:30 10.1.2.4
Ethernet0/0
Step 24 Now check the status of S0/0.2 OSPF interface on BBR1 router with show ip ospf interface. The
OSPF network type should be set to point-to-multipoint.
Process ID 1, Router ID 172.31.1.3, Network Type POINT_TO_MULTIPOINT,
Cost: 1562
Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT,
Next 0x0(0)/0x0(0)
Step 25 The OSPF database for Area0 does not contain the Type-2 LSA describing the multi-access
Frame Relay network with attached routers any more since OSPF treats the network as a
collection of point-to-point links. Check the OSPF database content with show ip ospf database
command.



count
10.200.200.11 10.200.200.11 611 0x80000005 0x56A 3
10.200.200.12 10.200.200.12 612 0x80000005 0x3B2F 3
10.254.0.3 10.254.0.3 436 0x80000005 0x554E 2
172.31.1.3 172.31.1.3 611 0x8000000A 0x575B 5


10.1.0.0 10.200.200.11 548 0x80000002 0x1B2F
10.1.0.0 10.200.200.12 417 0x80000002 0x1534
10.1.1.0 10.200.200.11 548 0x80000002 0x97F0
10.1.1.0 10.200.200.12 417 0x80000002 0x1433
10.1.2.0 10.200.200.11 548 0x80000002 0xF38
10.1.2.0 10.200.200.12 417 0x80000002 0x86FF
10.1.3.0 10.200.200.11 548 0x80000002 0x442
10.1.3.0 10.200.200.12 419 0x80000002 0xFD47
10.200.200.13 10.200.200.11 549 0x80000002 0x2CBE
10.200.200.13 10.200.200.12 419 0x80000002 0xA801
10.200.200.14 10.200.200.11 550 0x80000002 0xA405
10.200.200.14 10.200.200.12 419 0x80000002 0x1CCC
Step 26 As a result, the routing table now contains host routes for each OSPF neighbor on the
172.31.1.0/24 network. The R1 and R2 can now reach each others loopback interfaces since the
next hop address is now reachable, which you can verify using the show ip route, ping and
traceroute commands. The printouts show the content of routing tables on router BBR1, R1 and
R2 and successful ping test issued from R1 and R2 routers.
BBR1#show ip route
...


O 172.31.1.2 255.255.255.255
[110/1562] via 172.31.1.2, 00:10:47, Serial0/0.2
O 172.31.1.1 255.255.255.255
[110/1562] via 172.31.1.1, 00:10:47, Serial0/0.2
O 10.200.200.11 255.255.255.255
[110/1563] via 172.31.1.1, 00:10:47, Serial0/0.2
O IA 10.200.200.14 255.255.255.255
[110/1564] via 172.31.1.2, 00:10:48, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1563] via 172.31.1.2, 00:10:48, Serial0/0.2
O IA 10.200.200.13 255.255.255.255
[110/1564] via 172.31.1.1, 00:10:48, Serial0/0.2
O IA 10.1.3.0 255.255.255.0
[110/1627] via 172.31.1.1, 00:10:48, Serial0/0.2
[110/1627] via 172.31.1.2, 00:10:48, Serial0/0.2
O IA 10.1.2.0 255.255.255.0
[110/1563] via 172.31.1.2, 00:10:48, Serial0/0.2
O IA 10.1.1.0 255.255.255.0
[110/1563] via 172.31.1.1, 00:10:48, Serial0/0.2
O IA 10.1.0.0 255.255.255.0
[110/1626] via 172.31.1.1, 00:10:48, Serial0/0.2
[110/1626] via 172.31.1.2, 00:10:48, Serial0/0.2
R1#show ip route
...


O 172.31.1.2 255.255.255.255
[110/1626] via 172.31.1.3, 00:16:14, Serial0/0.2
O 172.31.1.3 255.255.255.255
[110/64] via 172.31.1.3, 00:16:14, Serial0/0.2
O 10.200.200.14 255.255.255.255
[110/66] via 10.1.1.3, 00:45:27, Ethernet0/0
[110/66] via 10.1.0.2, 00:45:27, Serial0/0.1
O 10.200.200.12 255.255.255.255
[110/1627] via 172.31.1.3, 00:16:15, Serial0/0.2
O 10.200.200.13 255.255.255.255
[110/2] via 10.1.1.3, 00:45:28, Ethernet0/0
O 10.1.3.0 255.255.255.0 [110/65] via 10.1.1.3, 00:45:28,
Ethernet0/0
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.0.2, 00:45:28,
Serial0/0.1
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.1.3, 00:16:16, Serial0/0.2
R2#show ip route
...


O 172.31.1.3 255.255.255.255
[110/64] via 172.31.1.3, 00:17:55, Serial0/0.2
O 172.31.1.1 255.255.255.255
[110/1626] via 172.31.1.3, 00:17:55, Serial0/0.2
O 10.200.200.11 255.255.255.255
[110/1627] via 172.31.1.3, 00:17:55, Serial0/0.2
O 10.200.200.14 255.255.255.255
[110/2] via 10.1.2.4, 00:47:05, Ethernet0/0
O 10.200.200.13 255.255.255.255
[110/66] via 10.1.2.4, 00:47:05, Ethernet0/0
[110/66] via 10.1.0.1, 00:47:05, Serial0/0.1
O 10.1.3.0 255.255.255.0 [110/65] via 10.1.2.4, 00:47:05,
Ethernet0/0
O 10.1.1.0 255.255.255.0 [110/65] via 10.1.0.1, 00:47:05,
Serial0/0.1
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.1.3, 00:17:56, Serial0/0.2
R2#
R1#ping 10.200.200.12

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/116/124
ms


1 172.31.1.3 32 msec 28 msec 28 msec
2 172.31.1.2 56 msec * 56 msec
R1#
Printout 65: Ping and traceroute from R1 to R2 loopback
R2#ping 10.200.200.11

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/116/124
ms


1 172.31.1.3 32 msec 28 msec 28 msec
2 172.31.1.1 57 msec * 61 msec
Printout 66: Ping and traceroute from R2 to R1 loopback

Lab Topology
router (BBR3) in the figure is accessible via telnet only.

R1, R2 Edge routers
router is connected to a Frame Relay switch. The DLCI values for individual sub-interface Frame
Relay connections are given in the following table:
BBR1 236 172.31.1.3 R1 263 172.31.1.1
BBR1 331 172.31.1.3 R2 313 172.31.1.2
BBR1 130 10.254.0.1 BBR3 103 10.254.0.3
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
This section contains information on IP addressing ranges and routing used in the remote lab.
Parameter Value
The actual addresses used on WAN and LAN links configured on the lab exercise routers are

Existing OSPF Routing
OSPF routing protocol is used as a core routing protocol. The existing OSPF routing
configuration on BBR3 router is shown below:
router ospf 1
network 10.254.0.0 0.0.0.255 area 0
Printout 67: OSPF routing on BBR3 router


Copyright 2006, NIL Data Communications Configuring OSPF for Frame Relay Environment Lab Solutions 55
BSCI
Configuring OSPF for Frame
Relay Environment
Lab Solutions
Lab Solution
Task 1: Configuring Non- Backbone OSPF Area
router ospf 1
network 10.0.0.0 0.255.255.255 area 1
Configuration 14: OSPF configuration on R3 and R4 routers
router ospf 1
network 10.1.0.0 0.0.255.255 area 1
Task 2: Using NBMA OSPF Network Type over Frame Relay
The following commands need to be entered on BBR1 router:
router ospf 1
network 10.254.0.0 0.0.0.255 area 0
network 172.31.1.0 0.0.0.255 area 0
Configuration 16: OSPF configuration on BBR1 router
56 Configuring OSPF for Frame Relay Environment Lab Solutions Copyright 2006, NIL Data Communications
router ospf 1
network 10.200.200.0 0.0.0.255 area 0
network 172.31.1.0 0.0.0.255 area 0
Task 3: Configuring OSPF Neighborship and DR Router for
NBMA Network Type
ip ospf priority 0
Configuration 18: OSPF priority adjustment on R1 and R2 routers
router ospf 1
neighbor 172.31.1.1
neighbor 172.31.1.2
Configuration 19: OSPF neighbor configuration on BBR1 router
Task 4: Using Point-to-Multipoint OSPF Network Type over
Frame Relay
ip ospf network point-to-multipoint
!
router ospf 1
no neighbor 172.31.1.1
no neighbor 172.31.1.2
Configuration 20: OSPF point-to-multipoint operation configuration on BBR1
router
Configuration 21: OSPF point-to-multipoint operation configuration on R1 and
R2 routers

Copyright 2006, NIL Data Communications Configuring a Multi-Area OSPF Network 57
BSCI
Configuring a Multi-Area
OSPF Network
Objective
In this exercise, you will configure large-scale OSPF routing by enabling OSPF on all WAN
(Frame Relay sub-interfaces) and LAN links. You will configure multiple OSPF areas first and
examine the established OSPF adjacencies and IP routing tables.
The OSPF non-backbone area contains some links that are unstable. To reduce the routing
overhead related to the unreliable links, you will configure OSPF route summarization on Area
Border Routers (ABR).
Since the routers within OSPF non-backbone areas are low on memory and cannot be replaced,
you will configure the OSPF non-backbone area to be stub. After examining IP routing tables,
you realize that you need only a default route injected into the OSPF non-backbone area, and so
the OSPF stub area will be converted into a totally stubby OSPF area. Since two ABR routers
exist, both will be injecting a default route. You will influence the cost of injected default routes
to prefer one ABR as an exit from the non-backbone area.
Finally, the OSPF non-backbone areas, which have no direct connection to OSPF backbone area,
will be configured. You will use OSPF virtual links to connect those OSPF areas to the OSPF
backbone area
Configure OSPF backbone and non-backbone areas over Frame Relay and Ethernet
interfaces.
Summarize the subnets in non-backbone OSPF area.
Reconfigure the non-backbone OSPF area to be a stub area.
Reconfigure the non-backbone OSPF area to be a totally stubby area.
Adjust the cost of injected default route on ABR router.
Configure OSPF virtual links to support OSPF areas not directly connected to area 0.
The following figure shows the logical topology used for this lab.
58 Configuring a Multi-Area OSPF Network Copyright 2006, NIL Data Communications

Figure 12: Configuring Multiarea OSPF Network Lab exercise logical topology
Command List
Command Task
area area-id default-cost cost Specifies a cost for the default summary
route sent into a stub area.
area area-number range IP-address mask Summarize address.
area area-number stub [no-summary] Configures an area as a stub or totally stubby
area.
area area-number virtual-link OSPF-router-
ID
Creates an OSPF virtual link.
ip ospf cost value Changes the OSPF link cost.
ip ospf network {broadcast | non-broadcast
| {point-to-multipoint [non-broadcast]}}
Configures the OSPF network type to a type
other than the default for a given media.
network ip-address wildcard area area-
number
Specifies the interfaces on which to run
OSPF, and their areas.
router ospf process-ID Enables OSPF with a process ID of process-
ID.
show ip ospf Display general information about the OSPF
routing process.
show ip ospf database
[router|network|summary|external]
Displays the content of OSPF database.
interface.
show ip ospf virtual-links Show the OSPF virtual-links status.
Multiarea OSPF Network Lab exercise
Task 1: Configuring Multiple OSPF Areas
Step 1 Start the OSPF with the process ID 1 at R3 and R4 routers and place S0/0.1 and Fe0/0 interfaces
in the OSPF area 1.
Step 2 Start the OSPF with the process ID 1 at R1 and R2 routers also. Place S0/0.1 and Fe0/0 interfaces
in the OSPF area 1 and S0/0.2 and loopback interfaces in OSPF area 0. Use OSPF point-to-
multipoint network type on multipoint Frame Relay interfaces.
Step 3 Start the OSPF with the process ID 1 at BBR1 router and place all WAN interfaces into OSPF
area 0. Use OSPF point-to-multipoint operation mode for Frame Relay multipoint interfaces.
Verification
Step 4 Verify that you have full connectivity in your network by using the ping command. For example,
try to ping other routers from R3 router.
Step 5 Examine the OSPF database on BBR1 router with the show ip ospf database command. The
router is an internal backbone router. The OSPF database is populated with Type-1, Type-3, and
Type-5 LSAs. There are no multi-access networks in the area so there are no Type-2 LSAs.



count
10.200.200.11 10.200.200.11 57 0x80000007 0x3D30 3
10.200.200.12 10.200.200.12 47 0x80000007 0x3731 3
172.31.1.3 172.31.1.3 52 0x80000005 0x7B50 5
172.31.22.22 172.31.22.22 85 0x80000005 0x20A9 2


10.1.0.0 10.200.200.11 62 0x80000003 0x1930
10.1.0.0 10.200.200.12 53 0x80000003 0x1335
10.1.1.0 10.200.200.11 62 0x80000003 0x95F1
10.1.1.0 10.200.200.12 53 0x80000003 0x1234
10.1.2.0 10.200.200.11 162 0x80000004 0xB3A
10.1.2.0 10.200.200.12 164 0x80000003 0x8401
10.1.3.0 10.200.200.11 62 0x80000003 0x243
10.1.3.0 10.200.200.12 54 0x80000003 0xFB48

Type-5 AS External Link States

Link ID ADV Router Age Seq# Checksum Tag
10.97.97.0 172.31.22.22 668 0x80000001 0x7B60 0
172.31.22.0 172.31.22.22 668 0x80000001 0x9036 0
Step 6 Check router LSAs on BBR1 router with the show ip ospf database router command. Type-1
LSAs describe the routers and their view of the connected links and neighbors in the area 0. The
link state ID in this case equals the router ID. For example, the BBR1 router with the router ID of
10.200.200.11 sees the loopback as a stub network and S0/0.2 interface as a stubnetwork and
link to another router (remember that OSPF point-to multipoint network representation is used
on that interface).
BBR1#show ip ospf database router



Routing Bit Set on this LSA
LS age: 178
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 10.200.200.11
Advertising Router: 10.200.200.11
LS Seq Number: 80000007
Checksum: 0x3D30
Length: 60
Area Border Router
Number of Links: 3

Link connected to: a Stub Network
(Link ID) Network/subnet number: 10.200.200.11
(Link Data) Network Mask: 255.255.255.255
Number of TOS metrics: 0
TOS 0 Metrics: 1

Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 172.31.1.3
(Link Data) Router Interface address: 172.31.1.1
TOS 0 Metrics: 64

TOS 0 Metrics: 0

LS age: 170
Link State ID: 10.200.200.12
Checksum: 0x3731
Length: 60
Area Border Router
Number of Links: 3

TOS 0 Metrics: 64

TOS 0 Metrics: 0

TOS 0 Metrics: 1


LS age: 176
Link State ID: 172.31.1.3
Checksum: 0x7B50
Length: 84
Number of Links: 5

TOS 0 Metrics: 1562

TOS 0 Metrics: 1562

TOS 0 Metrics: 0

TOS 0 Metrics: 64

TOS 0 Metrics: 64

LS age: 211
Link State ID: 172.31.22.22
Checksum: 0x20A9
Length: 48
AS Boundary Router
Number of Links: 2

TOS 0 Metrics: 64

TOS 0 Metrics: 64
Printout 69: Type-1 LSAs in OSPF database on BBR1 router
Step 7 Check summary LSAs on BBR1 router with the show ip ospf database summary command.
Type-3 LSAs include information about networks from area 1. Since there are two ABR routers,
eight Type-3 LSAs are present, 2 for each network from area 1. For example, network
10.1.0.0/24 is described with two LSAs, one advertised by the R1 router and the other advertised
by the R2 router.
BBR1#show ip ospf database summary



LS age: 894
Options: (No TOS-capability, DC, Upward)
LS Type: Summary Links(Network)
Link State ID: 10.1.0.0 (summary Network Number)
Checksum: 0x1930
Length: 28
Network Mask: 255.255.255.0
TOS: 0 Metric: 64

LS age: 885
Checksum: 0x1335
Length: 28
TOS: 0 Metric: 64

LS age: 895
Checksum: 0x95F1
Length: 28
TOS: 0 Metric: 1

LS age: 888
Checksum: 0x1234
Length: 28
TOS: 0 Metric: 65

LS age: 998
Checksum: 0xB3A
Length: 28
TOS: 0 Metric: 65

LS age: 1000
Checksum: 0x8401
Length: 28
TOS: 0 Metric: 1

LS age: 899
Checksum: 0x243
Length: 28
TOS: 0 Metric: 65

LS age: 890
Checksum: 0xFB48
Length: 28
TOS: 0 Metric: 65
Printout 70: Type-3 LSA in OSPF database on BBR1 router
Step 8 Examine Type-5 LSAs using the show ip ospf database external command on BBR1 router.
The Type-5 LSAs provide information about external networks, which are redistributed into
OSPF on BBR3 Autonomous System Boundary Router (ASBR). You should see two Type-5
LSAs describing networks 10.97.97.0/24 and 172.31.22.0/24.
BBR1#show ip ospf database external



LS age: 1870
LS Type: AS External Link
Link State ID: 10.97.97.0 (External Network Number )
Checksum: 0x7B60
Length: 36
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 0.0.0.0
External Route Tag: 0

LS age: 1870
Checksum: 0x8E37
Length: 36
TOS: 0
Metric: 20
Printout 71: Type-5 LSAs in OSPF database on BBR1 router
Step 9 The IP routing table on BBR1 router is populated with the result of SPF calculation. The intra-
area (O) routes are from the area 0. The inter-area (O IA) routes provide information about WAN
and LAN networks from OSPF area 1 and the external (O E2) routes are networks redistributed
on BBR3 router.
BBR1#show ip route
...


O E2 172.31.22.0 255.255.255.0
[110/20] via 10.254.0.3, 00:24:31, Serial0/0.1
O 172.31.1.2 255.255.255.255
[110/1562] via 172.31.1.2, 00:24:31, Serial0/0.2
O 172.31.1.1 255.255.255.255
[110/1562] via 172.31.1.1, 00:24:31, Serial0/0.2
O 10.200.200.11 255.255.255.255
[110/1563] via 172.31.1.1, 00:24:32, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1563] via 172.31.1.2, 00:24:32, Serial0/0.2
O IA 10.1.3.0 255.255.255.0
[110/1627] via 172.31.1.1, 00:24:32, Serial0/0.2
[110/1627] via 172.31.1.2, 00:24:32, Serial0/0.2
O IA 10.1.2.0 255.255.255.0
[110/1563] via 172.31.1.2, 00:24:32, Serial0/0.2
O IA 10.1.1.0 255.255.255.0
[110/1563] via 172.31.1.1, 00:24:32, Serial0/0.2
O E2 10.97.97.0 255.255.255.0
[110/20] via 10.254.0.3, 00:24:32, Serial0/0.1
O IA 10.1.0.0 255.255.255.0
[110/1626] via 172.31.1.1, 00:24:32, Serial0/0.2
[110/1626] via 172.31.1.2, 00:24:32, Serial0/0.2
Step 10 Now examine the OSPF database and IP routing table on R1 router. The R1 router is an Area-
Border Router (ABR) and has separate database information for OSPF area 0 and OSPF area 1.
R1#show ip ospf database



count
10.200.200.11 10.200.200.11 1573 0x80000007 0x3D30 3
10.200.200.12 10.200.200.12 1565 0x80000007 0x3731 3
172.31.1.3 172.31.1.3 1570 0x80000005 0x7B50 5
172.31.22.22 172.31.22.22 1603 0x80000005 0x20A9 2


10.1.0.0 10.200.200.11 1578 0x80000003 0x1930
10.1.0.0 10.200.200.12 1571 0x80000003 0x1335
10.1.1.0 10.200.200.11 1578 0x80000003 0x95F1
10.1.1.0 10.200.200.12 1571 0x80000003 0x1234
10.1.2.0 10.200.200.11 1679 0x80000004 0xB3A
10.1.2.0 10.200.200.12 1682 0x80000003 0x8401
10.1.3.0 10.200.200.11 1578 0x80000003 0x243
10.1.3.0 10.200.200.12 1572 0x80000003 0xFB48


count
10.200.200.11 10.200.200.11 1699 0x80000006 0x97CE 3
10.200.200.12 10.200.200.12 1695 0x80000003 0x2043 3
10.200.200.13 10.200.200.13 1737 0x80000003 0x5DFC 3
10.200.200.14 10.200.200.14 1699 0x80000003 0xDF74 3


10.1.1.3 10.200.200.13 1738 0x80000001 0x3EF4
10.1.2.4 10.200.200.14 1699 0x80000001 0x3BF2


10.200.200.11 10.200.200.11 1710 0x80000001 0x38B6
10.200.200.11 10.200.200.12 1557 0x80000001 0xEF9D
10.200.200.12 10.200.200.11 1555 0x80000001 0xEBA1
10.200.200.12 10.200.200.12 1691 0x80000001 0x28C4
10.254.0.0 10.200.200.11 1565 0x80000001 0xB755
10.254.0.0 10.200.200.12 1558 0x80000001 0xB15A
172.31.1.1 10.200.200.11 1722 0x80000001 0xD9EE
172.31.1.1 10.200.200.12 1558 0x80000001 0x91D5
172.31.1.2 10.200.200.11 1556 0x80000001 0x8DD9
172.31.1.2 10.200.200.12 1692 0x80000001 0xC9FC
172.31.1.3 10.200.200.11 1566 0x80000001 0x483E
172.31.1.3 10.200.200.12 1558 0x80000001 0x4243

Summary ASB Link States (Area 1)

172.31.22.22 10.200.200.11 1566 0x80000001 0x1607
172.31.22.22 10.200.200.12 1558 0x80000001 0x100C


10.97.97.0 172.31.22.22 194 0x80000002 0x7961 0
172.31.22.0 172.31.22.22 194 0x80000002 0x8E37 0
Printout 73: OSPF database on R1 router
Note You can also see a new LSA type here Type-4 or summary ASBR link state.
Step 11 In the area 1 OSPF database two new LSA types are present compared to the OSPF area 0
database. The Type-2 LSAs, which describe two LAN networks in the area and can be inspected
with the show ip ospf database network command and Type-4 LSAs that describe BBR3 ASBR
router from OSPF area 0 and can be inspected with the show ip ospf database asbr-summary
command.
R1#show ip ospf database network



LS age: 1552
LS Type: Network Links
Link State ID: 10.1.1.3 (address of Designated Router)
Checksum: 0x3CF5
Length: 32
Attached Router: 10.200.200.13

LS age: 1477
LS Type: Network Links
Link State ID: 10.1.2.4 (address of Designated Router)
Checksum: 0x39F3
Length: 32
Printout 74: Type-2 LSAs in OSPF database on R1 router
R1#show ip ospf database asbr-summary



LS age: 498
LS Type: Summary Links(AS Boundary Router)
Link State ID: 172.31.22.22 (AS Boundary Router address)
Checksum: 0x1607
Length: 28
TOS: 0 Metric: 128

Adv Router is not-reachable
LS age: 499
LS Type: Summary Links(AS Boundary Router)
Link State ID: 172.31.22.22 (AS Boundary Router address)
Checksum: 0x100C
Length: 28
TOS: 0 Metric: 128
Printout 75: Type-4 LSAs in OSPF database on R1 router
Step 12 Since R1 is an ABR router and there are only OSPF area 0 and area 1, the routing table does not
hold any inter-area (O IA) routes.
R1#show ip route
...


O E2 172.31.22.0 255.255.255.0
[110/20] via 172.31.1.3, 00:09:10, Serial0/0.2
O 172.31.1.2 255.255.255.255
[110/1626] via 172.31.1.3, 00:09:20, Serial0/0.2
O 172.31.1.3 255.255.255.255
[110/64] via 172.31.1.3, 00:09:20, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1627] via 172.31.1.3, 00:09:21, Serial0/0.2
O 10.1.3.0 255.255.255.0
[110/65] via 10.1.1.3, 00:26:12, FastEthernet0/0
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.0.2, 00:26:13,
Serial0/0.1
O E2 10.97.97.0 255.255.255.0
[110/20] via 172.31.1.3, 00:09:11, Serial0/0.2
C 10.1.1.0 255.255.255.0 is directly connected, FastEthernet0/0
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.1.3, 00:09:21, Serial0/0.2
Step 13 The routing table on R3 router contains intra-area (O) routes from OSPF area 1, inter-area (O IA)
routes from OSPF backbone area and external (O E2) routes that are redistributed into OSPF at
BBR3 router. The OSPF database holds the information for area 1 only and is populated with all
previously mentioned LSA types.
R3#show ip route
...


O E2 172.31.22.0 255.255.255.0
O IA 172.31.1.2 255.255.255.255
[110/65] via 10.1.3.4, 00:25:23, Serial0/0.1
O IA 172.31.1.3 255.255.255.255
O IA 172.31.1.1 255.255.255.255
O IA 10.200.200.11 255.255.255.255
O IA 10.200.200.12 255.255.255.255
[110/66] via 10.1.3.4, 00:25:24, Serial0/0.1
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.3.4, 00:26:38,
Serial0/0.1
O E2 10.97.97.0 255.255.255.0
O 10.1.0.0 255.255.255.0
O IA 10.254.0.0 255.255.255.0



count
10.200.200.11 10.200.200.11 679 0x80000008 0x93D0 3
10.200.200.12 10.200.200.12 560 0x80000005 0x1C45 3
10.200.200.13 10.200.200.13 758 0x80000005 0x59FE 3
10.200.200.14 10.200.200.14 654 0x80000005 0xDB76 3


10.1.1.3 10.200.200.13 758 0x80000003 0x3AF6
10.1.2.4 10.200.200.14 654 0x80000003 0x37F4


10.200.200.11 10.200.200.11 679 0x80000003 0x34B8
10.200.200.11 10.200.200.12 560 0x80000003 0xEB9F
10.200.200.12 10.200.200.11 430 0x80000003 0xE7A3
10.200.200.12 10.200.200.12 560 0x80000003 0x24C6
10.254.0.0 10.200.200.11 680 0x80000003 0xB357
10.254.0.0 10.200.200.12 561 0x80000003 0xAD5C
172.31.1.1 10.200.200.11 680 0x80000003 0xD5F0
172.31.1.1 10.200.200.12 561 0x80000003 0x8DD7
172.31.1.2 10.200.200.11 431 0x80000003 0x89DB
172.31.1.2 10.200.200.12 561 0x80000003 0xC5FE
172.31.1.3 10.200.200.11 680 0x80000003 0x4440
172.31.1.3 10.200.200.12 561 0x80000003 0x3E45


172.31.22.22 10.200.200.11 680 0x80000003 0x1209
172.31.22.22 10.200.200.12 561 0x80000003 0xC0E


10.97.97.0 172.31.22.22 1124 0x80000003 0x7762 0
172.31.22.0 172.31.22.22 1125 0x80000003 0x8C38 0
R3#
Task 2: OSPF Area Route Summarization
Step 14 Enable summarization of 10.1.x.0/24 subnets from OSPF area 1 into one summarized route
10.1.0.0/16 at R1and R2 ABR routers.
Verification
Step 15 First examine the OSPF database on BBR1 router. The database is smaller, since it holds only
two type-3 LSAs now, one from R1 and the other from R2 ABR router.



count
10.200.200.11 10.200.200.11 390 0x80000009 0x3932 3
10.200.200.12 10.200.200.12 270 0x80000009 0x3333 3
172.31.1.3 172.31.1.3 181 0x80000007 0x7752 5
172.31.22.22 172.31.22.22 319 0x80000007 0x1CAB 2


10.1.0.0 10.200.200.11 390 0x80000006 0x9AEA
10.1.0.0 10.200.200.12 270 0x80000006 0x94EF


10.97.97.0 172.31.22.22 832 0x80000003 0x7762 0
172.31.22.0 172.31.22.22 832 0x80000003 0x8C38 0
BBR1#
Step 16 The routing table on BBR1 router has only one inter-area (O IA) route now, the 10.1.0.0/16
summary route instead of more specific 10.1.x.0/24 subnets from area 1. The summary route is
reachable through two equal cost paths (through R1 and R2).
BBR1#show ip route
...


O E2 172.31.22.0 255.255.255.0
[110/20] via 10.254.0.3, 01:01:40, Serial0/0.1
O 172.31.1.2 255.255.255.255
[110/1562] via 172.31.1.2, 01:01:40, Serial0/0.2
O 172.31.1.1 255.255.255.255
[110/1562] via 172.31.1.1, 01:01:40, Serial0/0.2
O 10.200.200.11 255.255.255.255
[110/1563] via 172.31.1.1, 01:01:41, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1563] via 172.31.1.2, 01:01:41, Serial0/0.2
O E2 10.97.97.0 255.255.255.0
[110/20] via 10.254.0.3, 01:01:41, Serial0/0.1
O IA 10.1.0.0 255.255.0.0 [110/1563] via 172.31.1.1, 00:00:23,
Serial0/0.2
[110/1563] via 172.31.1.2, 00:00:23,
Serial0/0.2
Step 17 Check the routing table on R1 and R2 ABR routers also. Since routers are performing
summarization, the summary route to Null0 interface is installed to the routing table to prevent
black hole routing.
R1#show ip route
...


O E2 172.31.22.0 255.255.255.0
[110/20] via 172.31.1.3, 00:01:29, Serial0/0.2
O 172.31.1.2 255.255.255.255
[110/1626] via 172.31.1.3, 00:01:29, Serial0/0.2
O 172.31.1.3 255.255.255.255
[110/64] via 172.31.1.3, 00:01:29, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1627] via 172.31.1.3, 00:01:30, Serial0/0.2
O 10.1.3.0 255.255.255.0 [110/65] via 10.1.1.3, 00:01:30,
Ethernet0/0
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.0.2, 00:01:30,
Serial0/0.1
O E2 10.97.97.0 255.255.255.0
[110/20] via 172.31.1.3, 00:01:30, Serial0/0.2
O 10.1.0.0 255.255.0.0 is a summary, 00:01:30, Null0
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.1.3, 00:01:30, Serial0/0.2
Task 3: Configuring OSPF Stub Area
Step 18 Configure the OSPF area 1 to be a stub area to minimize the size of the OSPF databases on R3
and R4 routers.
Verification
Step 19 Examine the routing table at R3 and R4 routers. The inter-area (O IA) routes are still in the
routing table, whereas the external routes (O E2) are not present any more. Instead of external
routes the R1 and R2 ABR routers have generated a default route, so that internal routers can still
reach external networks.
R3#show ip route
...


O IA 172.31.1.2 [110/65] via 10.1.1.1, 00:00:19, FastEthernet0/0
[110/65] via 10.1.3.4, 00:00:19, Serial0/0.1
O IA 10.200.200.11 255.255.255.255
O IA 10.200.200.12 255.255.255.255
[110/66] via 10.1.3.4, 00:00:21, Serial0/0.1
O 10.1.2.0 255.255.255.0 [110/65] via 10.1.3.4, 00:00:21,
Serial0/0.1
O 10.1.0.0 255.255.255.0
O IA 10.254.0.0 255.255.255.0
O*IA 0.0.0.0 0.0.0.0 [110/2] via 10.1.1.1, 00:00:21, FastEthernet0/0
Step 20 Similar information is acquired by inspecting the OSPF database. Type-5 LSAs are no longer
present, they are blocked by the ABR routers; instead two Type-3 LSAs describing a default
route generated by ABR routers are present.



count
10.200.200.11 10.200.200.11 175 0x8000000B 0xABB7 3
10.200.200.12 10.200.200.12 174 0x80000008 0x342C 3
10.200.200.13 10.200.200.13 169 0x80000008 0x71E5 3
10.200.200.14 10.200.200.14 167 0x80000008 0xF35D 3


10.1.1.3 10.200.200.13 174 0x80000005 0x54DC
10.1.2.4 10.200.200.14 171 0x80000005 0x51DA


0.0.0.0 10.200.200.11 198 0x80000001 0x5146
0.0.0.0 10.200.200.12 192 0x80000001 0x4B4B
10.200.200.11 10.200.200.11 198 0x80000004 0x509D
10.200.200.11 10.200.200.12 192 0x80000004 0x884
10.200.200.12 10.200.200.11 199 0x80000004 0x488
10.200.200.12 10.200.200.12 193 0x80000004 0x40AB
10.254.0.0 10.200.200.11 199 0x80000004 0xCF3C
10.254.0.0 10.200.200.12 193 0x80000004 0xC941
172.31.1.1 10.200.200.11 199 0x80000004 0xF1D5
172.31.1.1 10.200.200.12 193 0x80000004 0xA9BC
172.31.1.2 10.200.200.11 199 0x80000004 0xA5C0
172.31.1.2 10.200.200.12 193 0x80000004 0xE1E3
172.31.1.3 10.200.200.11 199 0x80000004 0x6025
172.31.1.3 10.200.200.12 193 0x80000004 0x5A2A
Step 21 Verify the number and types of OSPF areas on your area border routers (ABR) R1 and R2 as
well as on your internal routers R3 and R4 with the show ip ospf command.
R1#show ip ospf
Supports opaque LSA
It is an area border router
Number of external LSA 2. Checksum Sum 0x10B96
Area BACKBONE(0)
Area ranges are
Number of LSA 6. Checksum Sum 0x24CFB
Flood list length 0
Area 1
It is a stub area
generates stub default route with cost 1
Area ranges are
10.1.0.0 255.255.0.0 Active(1) Advertise
Router LSA rebuild timer due in 00:02:38
Number of LSA 20. Checksum Sum 0xA805B
Flood list length 0
Printout 17: OSPF properties on R1 router
R3#show ip ospf
Supports opaque LSA
Area 1
It is a stub area
Area ranges are
Number of LSA 20. Checksum Sum 0xA5D51
Flood list length 0
Printout 18: OSPF properties on R1 router
Task 4: Configuring OSPF Totally Stubby Area
Step 22 Configure the OSPF area 1 to be a totally stubby area to further minimize the size of the OSPF
databases on R3 and R4 routers.
Verification
Step 23 Re-examine the routing table at R3 and R4 routers. The inter-area (O IA) routes have disappeared
from the routing table. There are only intra-area (O) routes and a default route towards the
closest ABR router.
R3#show ip route
...


O 10.1.2.0 255.255.255.0 [110/65] via 10.1.3.4, 00:00:16,
Serial0/0.1
O 10.1.0.0 255.255.255.0
Step 24 Check the OSPF database on R3 and R4 routers. There are only two Type-3 LSAs generated by
the ABR routers describing the default route. All other Type-3 LSAs have been blocked by the
ABR routers.



count
10.200.200.11 10.200.200.11 702 0x8000000E 0xA5BA 3
10.200.200.12 10.200.200.12 703 0x8000000A 0x302E 3
10.200.200.13 10.200.200.13 707 0x8000000A 0x6DE7 3
10.200.200.14 10.200.200.14 922 0x80000008 0xF35D 3


10.1.1.3 10.200.200.13 707 0x80000007 0x50DE
10.1.2.4 10.200.200.14 926 0x80000005 0x51DA


0.0.0.0 10.200.200.11 711 0x80000002 0x4F47
0.0.0.0 10.200.200.12 708 0x80000002 0x494C
Task 5: Optimizing Default Routing for Area 1
Step 25 Set the OSPF area 1 default cost at R2 ABR router to 100, to prefer R1 as the exit from the area
1.
Step 26 The R4 internal router has two equal cost paths towards R1 ABR router one through R3 and the
other through R2, both with the cost of 66. To prevent R4 from installing two default routes set
the OSPF cost of R1 to R2 link to 100.
Verification
Step 27 Verify the routing table on R3 and R4 routers. You should see that the default way out of the area
on R4 router is no longer through R2. Using show ip route command you should see the outputs
similar to the following printouts:
R3#show ip route
...


O 10.1.2.0 255.255.255.0 [110/65] via 10.1.3.4, 00:15:08,
Serial0/0.1
O 10.1.0.0 255.255.255.0
R4# show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route


O 10.1.1.0 255.255.255.0 [110/65] via 10.1.3.3, 00:15:31,
Serial0/0.1
O 10.1.0.0 255.255.255.0
O*IA 0.0.0.0 0.0.0.0 [110/66] via 10.1.3.3, 00:15:32, Serial0/0.1
Step 28 Perform traceroute from R4 to 10.254.0.3 to verify that the traffic leaving OSPF area 1, is
taking the path through R1 router.


1 10.1.3.3 28 msec 28 msec 28 msec
2 10.1.1.1 28 msec 28 msec 32 msec
3 172.31.1.3 80 msec 100 msec 40 msec
4 10.254.0.3 80 msec * 80 msec
Printout 23: Traceroute from R4 to 10.254.0.3
Task 6: Configuring OSPF Virtual Link
You have to configure OSPF areas 11 and 12, which are not directly connected to the area 0.
Since OSPF assumes that all non-backbone areas have at least one interface in area 0 you have to
deploy OSPF virtual-links to solve the problem.
Step 29 Remove the OSPF totally stubby area configuration from all area 1 routers.
Note Make sure you removed all area stub commands from your area 1 routers before continuing
with the configuration.
Step 30 At R3 router, place the loopback interface into the OSPF area 11.
Step 31 Determine the OSPF router ID of routers R1 and R3 and create the OSPF virtual link to support
the OSPF area 11.
Step 32 At R4 router, place the loopback interface into the OSPF area 12.
Step 33 Determine the OSPF router ID of routers R2 and R4 and create the OSPF virtual link to support
the OSPF area 12.
Verification
Step 34 Verify the virtual link status at R1 and R3 routers using the show ip ospf virtual-links
command. The outputs should be similar to the printouts below:
R1#show ip ospf virtual-links
Virtual Link OSPF_VL0 to router 10.200.200.13 is up
Run as demand circuit
DoNotAge LSA allowed.
Transit area 1, via interface FastEthernet0/0, Cost of using 1
Adjacency State FULL (Hello suppressed)
Index 2/4, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Printout 24: OSPF virtual-links status on R1 router
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Step 35 Now verify that virtual link between R2 and R4 is also functional. The outputs should be similar
to the printouts below:
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Step 36 Check the OSPF configuration with the show ip ospf command on R3 and R4 routers. OSPF
treats the virtual link as if there were an interface connected to area 0. Note that both routers
belong to 3 OSPF areas; backbone area and two non-backbone areas
R3#show ip ospf
Supports opaque LSA
It is an area border router
Number of external LSA 2. Checksum Sum 0x1039A
Area BACKBONE(0)
Area ranges are
Number of LSA 18. Checksum Sum 0x7CF9A
Flood list length 0
Area 1
Area ranges are
Number of LSA 44. Checksum Sum 0x15CD3A
Flood list length 0
Area 11
Area ranges are
Number of LSA 14. Checksum Sum 0x7BC02
Flood list length 0
Printout 28: OSPF information on R3 router
Step 37 Verify the connectivity to 10.200.200.13 and 10.200.200.14 from R1 router with traceroute
command.


1 10.1.1.3 0 msec * 0 msec
The path to 10.200.200.14 is through BBR1 router, since R1 does not have direct connection to
R2 router.


1 172.31.1.3 28 msec 32 msec 28 msec
2 172.31.1.2 64 msec 56 msec 56 msec
3 10.1.2.4 56 msec * 52 msec
Step 38 Examine the routing table on BBR1 router with the show ip route command. You should see R3
and R4 loopback networks as an interarea (O IA) routes present in the routing table. Notice also
that 10.1.x.0/24 networks are present in the routing table inspite of summarization on R1 and R2
routers. The reason is that R3 and R4 routers have become ABR routers, so summarization
should be configured there too.
BBR1#show ip route
...


O E2 172.31.22.0 255.255.255.0
[110/20] via 10.254.0.3, 00:24:56, Serial0/0.1
O 172.31.1.2 255.255.255.255
[110/1562] via 172.31.1.2, 00:24:56, Serial0/0.2
O 172.31.1.1 255.255.255.255
[110/1562] via 172.31.1.1, 00:24:56, Serial0/0.2
O 10.200.200.11 255.255.255.255
[110/1563] via 172.31.1.1, 00:24:57, Serial0/0.2
O IA 10.200.200.14 255.255.255.255
[110/1564] via 172.31.1.2, 00:24:57, Serial0/0.2
O 10.200.200.12 255.255.255.255
[110/1563] via 172.31.1.2, 00:24:57, Serial0/0.2
O IA 10.200.200.13 255.255.255.255
[110/1564] via 172.31.1.1, 00:24:57, Serial0/0.2
O IA 10.1.3.0 255.255.255.0
[110/1627] via 172.31.1.2, 00:24:57, Serial0/0.2
[110/1627] via 172.31.1.1, 00:24:57, Serial0/0.2
O IA 10.1.2.0 255.255.255.0
[110/1564] via 172.31.1.2, 00:24:57, Serial0/0.2
O IA 10.1.1.0 255.255.255.0
[110/1564] via 172.31.1.1, 00:24:57, Serial0/0.2
O E2 10.97.97.0 255.255.255.0
[110/20] via 10.254.0.3, 00:24:57, Serial0/0.1
O IA 10.1.0.0 255.255.255.0
[110/1664] via 172.31.1.2, 00:24:57, Serial0/0.2
[110/1664] via 172.31.1.1, 00:24:57, Serial0/0.2
O IA 10.1.0.0 255.255.0.0 [110/1563] via 172.31.1.1, 00:24:58,
Serial0/0.2
[110/1563] via 172.31.1.2, 00:24:58,
Serial0/0.2
Step 39 Verify the OSPF database on routers R3 and R4 with the show ip ospf database command to see
the DNA (Do Not Age) bit for LSAs flooded over a demand circuit like a virtual link.



count
10.200.200.11 10.200.200.11 1 (DNA) 0x80000004 0x6345 4
10.200.200.12 10.200.200.12 3 (DNA) 0x80000005 0xE0BE 4
10.200.200.13 10.200.200.13 214 0x80000002 0x4BDC 1
10.200.200.14 10.200.200.14 8 (DNA) 0x80000004 0x5CC4 1
172.31.1.3 172.31.1.3 973 (DNA) 0x80000004 0x9BF0 5
172.31.22.22 172.31.22.22 986 (DNA) 0x80000003 0x24A7 2


10.1.0.0 10.200.200.11 965 (DNA) 0x80000002 0xA2E6
10.1.0.0 10.200.200.12 955 (DNA) 0x80000002 0x9CEB
10.1.0.0 10.200.200.13 201 0x80000003 0x172F
10.1.0.0 10.200.200.14 7 (DNA) 0x80000001 0x1532
10.1.1.0 10.200.200.13 206 0x80000003 0x89FB
10.1.1.0 10.200.200.14 13 (DNA) 0x80000002 0x83D
10.1.2.0 10.200.200.13 173 0x80000004 0xFE44
10.1.2.0 10.200.200.14 7 (DNA) 0x80000001 0x7C09
10.1.3.0 10.200.200.13 226 0x80000001 0xEF56
10.1.3.0 10.200.200.14 7 (DNA) 0x80000001 0xE95B
10.200.200.13 10.200.200.13 216 0x80000001 0x18D2
10.200.200.14 10.200.200.14 4 (DNA) 0x80000001 0x8E0



count
10.200.200.11 10.200.200.11 10 (DNA) 0x80000004 0x6345 4
10.200.200.12 10.200.200.12 5 (DNA) 0x80000005 0xE0BE 4
10.200.200.13 10.200.200.13 8 (DNA) 0x80000002 0x4BDC 1
10.200.200.14 10.200.200.14 796 0x80000004 0x5CC4 1
172.31.1.3 172.31.1.3 992 (DNA) 0x80000004 0x9BF0 5
172.31.22.22 172.31.22.22 1005 (DNA) 0x80000003 0x24A7 2


10.1.0.0 10.200.200.11 985 (DNA) 0x80000002 0xA2E6
10.1.0.0 10.200.200.12 972 (DNA) 0x80000002 0x9CEB
10.1.0.0 10.200.200.13 4 (DNA) 0x80000003 0x172F
10.1.0.0 10.200.200.14 827 0x80000001 0x1532
10.1.1.0 10.200.200.13 4 (DNA) 0x80000003 0x89FB
10.1.1.0 10.200.200.14 808 0x80000002 0x83D
10.1.2.0 10.200.200.13 4 (DNA) 0x80000004 0xFE44
10.1.2.0 10.200.200.14 828 0x80000001 0x7C09
10.1.3.0 10.200.200.13 10 (DNA) 0x80000001 0xEF56
10.1.3.0 10.200.200.14 829 0x80000001 0xE95B
10.200.200.13 10.200.200.13 4 (DNA) 0x80000001 0x18D2
10.200.200.14 10.200.200.14 819 0x80000001 0x8E0
Lab Topology
router (BBR3) in the figure is accessible via telnet only.

R1, R2 Edge routers
BBR1 236 172.31.1.3 R1 263 172.31.1.1
BBR1 331 172.31.1.3 R2 313 172.31.1.2
BBR1 130 10.254.0.1 BBR3 103 10.254.0.3
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
This section contains information on IP addressing ranges and OSPF routing used in the remote
lab.
Parameter Value
BBR3 loopback interfaces 10.97.97.0/24, 172.31.22.0/24

OSPF routing protocol is used as a core routing protocol. The existing OSPF routing
configuration on BBR3 router is shown below:
router ospf 1
redistribute connected subnets route-map CONN
network 10.254.0.0 0.0.0.255 area 0
!
!
access-list 10 permit 10.97.97.0 0.0.0.255
route-map CONN permit 10
match ip address 10
Copyright 2006, NIL Data Communications Configuring a Multi-Area OSPF Network Lab Solutions 83
BSCI
Configuring a Multi-Area
OSPF Network
Lab Solutions
Lab Solution
Task 1: Configuring Multiple OSPF Areas
!
router ospf 1
network 10.1.0.0 0.0.255.255 area 1
network 10.200.200.0 0.0.0.255 area 0
network 172.31.1.0 0.0.0.255 area 0
router ospf 1
network 10.1.0.0 0.0.255.255 area 1
!
router ospf 1
network 10.254.0.0 0.0.0.255 area 0
network 172.31.1.0 0.0.0.255 area 0
Configuration 24: OSPF configuration on BBR1 router
84 Configuring a Multi-Area OSPF Network Lab Solutions Copyright 2006, NIL Data Communications
Task 2: OSPF Area Route Summarization
router ospf 1
area 1 range 10.1.0.0 255.255.0.0
Configuration 25: OSPF summarization on R1 and R2 routers
Task 3: Configuring OSPF Stub Area
router ospf 1
area 1 stub
Configuration 26: OSPF stub area configuration on R1, R2, R3 and R4 routers
Task 4: Configuring OSPF Totally Stubby Area
router ospf 1
area 1 stub no-summary
Configuration 27: OSPF totally stubby area configuration on R1 and R2 routers
Task 5: Optimizing Default Routing for Area 1
ip ospf cost 100
Configuration 28: OSPF link cost adjustment on R1 router
ip ospf cost 100
!
router ospf 1
area 1 default-cost 100
Configuration 29: OSPF link and default cost adjustment on R2 router
Task 6: Configuring OSPF Virtual Link
router ospf 1
no area 1 stub
area 1 virtual-link 10.200.200.13
Configuration 30: OSPF virtual link configuration on R1 router
Copyright 2006, NIL Data Communications Configuring a Multi-Area OSPF Network Lab Solutions 85
router ospf 1
no area 1 stub
router ospf 1
no area 1 stub
network 10.200.200.13 0.0.0.0 area 11
router ospf 1
no area 1 stub
network 10.200.200.14 0.0.0.0 area 12

86 Configuring a Multi-Area OSPF Network Lab Solutions Copyright 2006, NIL Data Communications

Copyright 2006, NIL Data Communications Configuring Integrated IS-IS in Multiple Areas 87
BSCI
Configuring Integrated IS-IS
in Multiple Areas
Objective
In this exercise, you will configure multi-area IS-IS routing by enabling IS-IS on all WAN
(Frame Relay sub-interfaces) and LAN links. You will then examine the established IS-IS
adjacencies and IP routing tables.

Figure 15: Configuring IS-IS in multiple areas
To reduce the routing overhead, you will change the IS-IS router types on the routers that are
evidently only level-1 IS-IS routers and eliminate redundant hello propagation by changing the
default IS-IS circuit type on L1L2 routers.

Figure 16: IS-IS router types
88 Configuring Integrated IS-IS in Multiple Areas Copyright 2006, NIL Data Communications
Since the network is large, you will limit the possible routing overhead related to unstable links
by configuring IS-IS route summarization.

Figure 17: IS-IS summarization
Configure the R1, R2, R3 and R4 routers to be in a specific IS-IS area.
Enable IS-IS on the proper interfaces on R1, R2, R3 and R4 routers.
Configure the R3 and R4 routers to be a L1 IS-IS router.
Configure the R1 and R2 routers to perform route summarization.
Verify proper L1 IS-IS adjacencies establishment between R1, R3 and R2, R4 routers.
Verify proper L2 IS-IS adjacencies establishment between the R1 and R2 routers.
Verify proper network connectivity.
Command List
Command Task
ip router isis [process-ID] Enables IS-IS on the interface.
isis circuit-type level1|level2|level-1-
2
Changes the interfaces IS-IS circuit type.
is-type level-1-only | level-2-only |
level-1-2
Configures the router as a level-1 or level-2 or level-
1 and level-2 IS-IS router.
net NET Configures the Network Entity Title (NET).
passive-interface interface-type
interface-number
Prevents establishing of IS-IS adjacencies over the
interface.
router isis [process-ID] Enables IS-IS.
show clns interface interface Displays ConnectionLess Network Service (CLNS)
interface status and configuration.
show clns is-neighbors Displays the IS-IS neighbor table.
show isis topology Displays a list of all connected routers in all areas.
summary-address IP-address mask Configures route summarization.
Integrated IS-IS in Multiple Areas Lab exercise
Task 1: Enable Integrated IS-IS
In this task, you will enable the Integrated IS-IS in your network and examine formed
adjacencies.
Step 1 Configure IS-IS with 49.0011 area ID on R1 and R3 routers. For the IS-IS routers NET, refer to
the Addressing section.
Step 2 Configure IS-IS with 49.0012 area ID on R2 and R4 routers. For the IS-IS routers NET, refer to
the Addressing section.
Step 3 Enable IS-IS on S0/0.1 and Fe0/0 and Loopback0 interfaces on R1, R2, R3 and R4 routers.
Verification
Step 4 Examine the CLNS interface status and configuration for interfaces of R1 router with the show
clns interface command. By default, the router acts as L1/L2 IS-IS router. R1 router thus forms
two L2 adjacencies (one with R3 in the same area and one with R2 in a different area) and one
L1 adjacency (only with the R3 router, which is in the same area). The printouts show the CLNS
interface information for interfaces S0/0.1, Fe0/0 and Loopback0 on R1 router.
R1#show clns interface Serial 0/0.1
Checksums enabled, MTU 1500, Encapsulation FRAME-RELAY
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching enabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 0 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x0, local circuit ID 0x100
Level-1 Metric: 10, Priority: 64, Circuit ID: R2.00
Number of active level-1 adjacencies: 0
Next IS-IS Hello in 5 seconds
R1#show clns interface FastEthernet 0/0
Checksums enabled, MTU 1497, Encapsulation SAP
CLNS fast switching enabled
Next IS-IS LAN Level-1 Hello in 565 milliseconds
Next IS-IS LAN Level-2 Hello in 2 seconds
R1#show clns interface loopback 0
Loopback0 is up, line protocol is up
Checksums enabled, MTU 1514, Encapsulation LOOPBACK
CLNS fast switching disabled
Next IS-IS LAN Level-1 Hello in 2 seconds
Next IS-IS LAN Level-2 Hello in 621 milliseconds
Printout 85: S0/0.1, Loopback0 and Fe0/0 CLNS interface information on R1
Step 5 Check the established IS-IS adjacencies and IS-IS topology database on all your routers with the
show clns is-neighbors command. As already mentioned, the routers act as L1/L2 IS-IS routers
by default. As a result each router forms L1 and L2 adjacency with the router from the same
area, and L2 adjacency with the router from another area.
R1#show clns is-neighbors

System Id Interface State Type Priority Circuit Id
Format
R2 Se0/0.1 Up L2 0 00 Phase
V
R3 Fa0/0 Up L1L2 64/64 R1.01 Phase
V
Printout 86: IS-IS neighbors on R1 router

Format
V
R4 Fa0/0 Up L1L2 64/64 R4.02 Phase
V

Format
R1 Fa0/0 Up L1L2 64/64 R1.01 Phase
V
V

Format
R2 Fa0/0 Up L1L2 64/64 R4.02 Phase
V
V
Step 6 Now examine the routing table of R1 router. The routing table holds L2 routes for the R2 and R4
loopbacks and LAN network from IS-IS area 49.0012, as well as L1 routes for the R3 loopback
and network from the S0/0.1 interface of R3 router. Notice that the IS-IS default administrative
distance is 115 and that 10.200.200.14/32 is accessible via 2 equal-cost paths.
R1#show ip route
...


i L2 10.200.200.14 255.255.255.255 [115/30] via 10.1.0.2, Serial0/0.1
[115/30] via 10.1.1.3,
FastEthernet0/0
i L2 10.200.200.12 255.255.255.255 [115/20] via 10.1.0.2, Serial0/0.1
i L1 10.200.200.13 255.255.255.255 [115/20] via 10.1.1.3,
FastEthernet0/0
i L1 10.1.3.0 255.255.255.0 [115/20] via 10.1.1.3, FastEthernet0/0
i L2 10.1.2.0 255.255.255.0 [115/20] via 10.1.0.2, Serial0/0.1
Step 7 The R3 router has L1 routes for the R1 loopback and network from the S0/0.1 interface of R1
router as well as L2 routes for the R2 and R4 loopbacks and LAN network from IS-IS area
49.0012 in its routing table. The 10.200.200.12/32 is accessible via two equal-cost paths.
R3#show ip route
...


i L1 10.200.200.11 255.255.255.255 [115/20] via 10.1.1.1,
FastEthernet0/0
i L2 10.200.200.14 255.255.255.255 [115/20] via 10.1.3.4, Serial0/0.1
i L2 10.200.200.12 255.255.255.255 [115/30] via 10.1.1.1,
FastEthernet0/0
[115/30] via 10.1.3.4, Serial0/0.1
i L2 10.1.2.0 255.255.255.0 [115/20] via 10.1.3.4, Serial0/0.1
Task 2: Changing the IS-IS Router Type
In this task, you will change the default IS-IS router type.
Step 8 Configure R3 and R4 routers to be IS-IS L1 only routers and make S0/0.1 passive interfaces to
eliminate unwanted hellos.
Verification
Step 9 Examine the established IS-IS adjacencies and routing table on R4 router using the show clns is-
neighbors and show ip route commands. R4 does not form L1 IS-IS adjacency with R3 over the
S0/0.1 interface since R3 is in a different IS-IS area. The only IS-IS adjacency that is formed by
R4 is the L1 IS-IS adjacency with the R2 router.

Format
R2 Fa0/0 Up L1 64 R4.02 Phase
V
Examining the IS-IS topology with the show isis topology command reveals the same
information.
R4#show isis topology

IS-IS paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
R2 10 R2 Fa0/0
0002.4b79.a880
R4 --
Printout 93: IS-IS topology as seen by R4 router
The routing table of the R4 router now holds only L1 routes. The default route is injected by the
area 49.0012 L2 router the R2 router.
R4#show ip route
...


i L1 10.200.200.12 255.255.255.255 [115/20] via 10.1.2.2,
FastEthernet0/0
i*L1 0.0.0.0 0.0.0.0 [115/10] via 10.1.2.2, FastEthernet0/0
Step 10 Check the established IS-IS adjacencies and the routing table also on the R3 router. The router
forms a L1 IS-IS adjacency only with R1 router, which is in the same area. As it was the case
with R4, the R3 routing table holds only L1 routes. The default route is injected by the area
49.0011 L2 router, the R1 router.

Format
V
R3#show ip route
...


i L1 10.200.200.11 255.255.255.255 [115/20] via 10.1.1.1,
FastEthernet0/0
Step 11 Perform extended traceroute from R3 to R4 loopback interface. All communication between the
areas goes through the L2 backbone that R1 and R2 routers are part of. The result of the
command should be similar to the following printout.
R3#traceroute
Protocol [ip]:
Target IP address: 10.200.200.14
Source address: 10.200.200.13
Numeric display [n]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Port Number [33434]:
Loose, Strict, Record, Timestamp, Verbose[none]:

1 10.1.1.1 4 msec 0 msec 4 msec
2 10.1.0.2 28 msec 28 msec 28 msec
3 10.1.2.4 28 msec * 28 msec
Printout 97: Traceroute from R3 to R4 loopback interface
Task 3: Changing the IS-IS Circuit Type
In this task, you will eliminate the unwanted hellos on certain interfaces by changing the default
IS-IS circuit type.
Step 12 Change the default IS-IS circuit type of Fe0/0 interfaces on R1 and R2 routers to L1 only to
eliminate the unwanted L2 hellos.
Step 13 Change the default IS-IS circuit type of S0/0.1 interfaces on R1 and R2 routers to L2 only to
eliminate the unwanted L1 hellos.
Verification
Step 14 Verify that R1 and R2 have formed only L1 adjacency over the Fe0/0 interface and L2 adjacency
over the S0/0.1 interface. Using the show clns is-neighbors command, you should get a printout
similar to the one below.

Format
V
V
Printout 98: IS-IS adjacencies on R1 router
R2#show isis topology

R2 --
R4 10 R4 Fa0/0
0002.4b87.c400

R1 10 R1 Se0/0.1 DLCI 732
R2 --
R3 **
R4 **
R2#
Printout 99: IS-IS topology on R2 router
Step 15 Look at the routing table of R1 router. Since R3 and R4 are only L1 routers, the 10.200.200.14/32
is available via single path only.
R1#show ip route
...


i L2 10.200.200.14 255.255.255.255 [115/30] via 10.1.0.2, Serial0/0.1
i L2 10.200.200.12 255.255.255.255 [115/20] via 10.1.0.2, Serial0/0.1
i L1 10.200.200.13 255.255.255.255 [115/20] via 10.1.1.3,
FastEthernet0/0
i L2 10.1.2.0 255.255.255.0 [115/20] via 10.1.0.2, Serial0/0.1
Step 16 Check the routing tables of R3 and R4 routers. The routers are L1 only routers, so the routing
table no longer holds information about 10.1.0.0/24 network, since this is now part of L2
backbone only.
R3#show ip route
...


i L1 10.200.200.11 255.255.255.255 [115/20] via 10.1.1.1,
FastEthernet0/0
R4#show ip route
...


i L1 10.200.200.12 255.255.255.255 [115/20] via 10.1.2.2,
FastEthernet0/0
Task 4: Configuring Route Summarization
Step 17 Configure the R1 router to perform route summarization and summarize 10.1.0.0/24 and
10.1.1.0/24 networks to 10.1.0.0/23.
Step 18 Configure the R2 router to perform route summarization and summarize 10.1.2.0/24 and
10.1.3.0/24 networks to 10.1.2.0/23.
Verification
Step 19 Verify the presence of summary routes in routing tables of R1 and R2 routers. Notice that each
router also installs a summary route to Null0 interface for the configured summary network in
order to avoid black hole routing.
R1#show ip route
...


i L2 10.200.200.14 255.255.255.255 [115/30] via 10.1.0.2, Serial0/0.1
i L2 10.200.200.12 255.255.255.255 [115/20] via 10.1.0.2, Serial0/0.1
i L1 10.200.200.13 255.255.255.255 [115/20] via 10.1.1.3,
FastEthernet0/0
i L2 10.1.2.0 255.255.254.0 [115/20] via 10.1.0.2, Serial0/0.1
i su 10.1.0.0 255.255.254.0 [115/10] via 0.0.0.0, Null0
R1#
R2#show ip route
...


i L2 10.200.200.11 255.255.255.255 [115/20] via 10.1.0.1, Serial0/0.1
i L1 10.200.200.14 255.255.255.255 [115/20] via 10.1.2.4,
FastEthernet0/0
i L2 10.200.200.13 255.255.255.255 [115/30] via 10.1.0.1, Serial0/0.1
i su 10.1.2.0 255.255.254.0 [115/10] via 0.0.0.0, Null0
i L2 10.1.0.0 255.255.254.0 [115/20] via 10.1.0.1, Serial0/0.1
Lab Topology

R1, R2 Edge routers
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
This section contains information on IP addressing ranges and IS-IS routing used in the remote
lab.
Note IP addressing has been pre-configured to allow you to focus exclusively on the objectives of
the exercise.
Parameter Value

IS-IS Routing
The IS-IS routing uses the following NET allocation scheme:
Parameter Value
R1 49.0011.1111.1111.1111.00
R2 49.0012.2222.2222.2222.00
R3 49.0011.3333.3333.3333.00
R4 49.0012.4444.4444.4444.00
Table 22: NET addresses


Copyright 2006, NIL Data Communications Configuring Integrated IS-IS in Multiple Areas Lab Solutions 101
BSCI
Configuring Integrated IS-IS
in Multiple Areas
Lab Solutions
Lab Solution
Task 1: Configuring Integrated IS-IS in Multiple Areas
interface Loopback0
ip router isis
!
ip router isis
!
ip router isis
!
router isis
net 49.0011.1111.1111.1111.00
Configuration 34: IS-IS configuration on R1 router
interface Loopback0
ip router isis
!
ip router isis
!
ip router isis
!
router isis
net 49.0012.2222.2222.2222.00
102 Configuring Integrated IS-IS in Multiple Areas Lab Solutions Copyright 2006, NIL Data Communications
interface Loopback0
ip router isis
!
ip router isis
!
ip router isis
!
router isis
net 49.0011.3333.3333.3333.00
interface Loopback0
ip router isis
!
ip router isis
!
ip router isis
!
router isis
net 49.0012.4444.4444.4444.00
Task 2: Changing the IS-IS Router Type
router isis
passive-interface Serial0/0.1
is-type level-1
Configuration 38: IS-IS configuration adjustment on R3 and R4 routers
Task 3: Changing the IS-IS Circuit Type
isis circuit-type level-1
!
isis circuit-type level-2-only
Configuration 39: IS-IS circuit type adjustment on R1 and R2 routers
Task 4: Configuring Route Summarization
router isis
summary-address 10.1.0.0 255.255.254.0
Configuration 40: IS-IS summarization on R1 router
Copyright 2006, NIL Data Communications Configuring Integrated IS-IS in Multiple Areas Lab Solutions 103
router isis
summary-address 10.1.2.0 255.255.254.0
Configuration 41: IS-IS summarization on R2 router

104 Configuring Integrated IS-IS in Multiple Areas Lab Solutions Copyright 2006, NIL Data Communications

Copyright 2006, NIL Data Communications Configuring Route Redistribution 105
BSCI
Configuring Route
Redistribution
Objective
Your network is using OSPF routing protocol in the backbone to achieve superior scalability and
fast re-routing in case of link failures. The network edge is equipped with less powerful routers
and slower adaptation to changes is sufficient so RIPv2 routing protocol is deployed there. You
will have to enable connectivity between two routing domains by configuring route redistribution
from RIPv2 to OSPF and injecting a default route into RIPv2 routing domain.

Figure 20: Redistribution from RIP to OSPF
Later you realize that some networks from RIPv2 routing domain do not need to be accessible
from the OSPF routing domain. To limit the number of routes that are redistributed from RIPv2
to OSPF, you will enhance route redistribution with route filtering.
106 Configuring Route Redistribution Copyright 2006, NIL Data Communications

Figure 21: Redistribution with route filtering
Configure Open Shortest Path First (OSPF) between the R1, R2 and BBR2 routers.
Configure Routing Information Protocol Version 2 (RIPv2) between the R1, R2, R3 and R4
routers.
Configure route redistribution at the R1 and R2 routers.
Configure route redistribution with filtering at the R1 and R2 routers.
Verify connectivity within the network.
Command List
Command Task
access-list number permit|deny IP-
address
Creates standard access list to permit/deny traffic.
distribute-list access-list out rip Enables filtering when redistributing from RIP.
match metric value Matches the metric value in a route-map.
network ip-address Specifies the interfaces that are included in RIP.
network ip-address wildcard area
area-number
Specifies the interfaces on which OSPF is run, and
their areas.
redistribute rip [metric metric]
[subnets] [route-map route-map]
Redistributes RIP to OSPF.
route-map map-name permit|deny
sequence-number
Creates a route map.
router ospf process-ID Enables OSPF with a process ID of process-ID.
router rip Enables RIP.
set metric value Sets the metric to a specified value in a route-map.
show ip ospf database external Displays the information about networks redistributed
into OSPF.
show ip route rip Displays the RIP routes if IP routing table.
version 2 Enables RIP Version 2.
Route Redistribution Lab exercise
Task 1: Configuring OSPF and RIPv2
In this task, you will configure OSPF routing protocol on edge routers R1 and R2 towards BBR2
and RIPv2 routing protocol between R1, R2, R3 and R4 routers.
Step 1 Enable OSPF routing protocol with the process ID 1 between R1, R2 and BBR2 routers on S0/0.3
interfaces. Place them in OSPF Area 0 and set the OSPF network type of the interface to point-
to-multipoint.
Step 2 Enable RIPv2 routing protocol on R1, R2, R3 and R4 routers. Include all interfaces except S0/0.3
on R1 and R2 routers in RIPv2 and disable automatic summarization.
Verification
Step 3 Use the ping command to verify that you have connectivity between R1, R2, R3 and R4 routers
and also between R1, R2 and BBR2 and BBR3 routers.
Step 4 Verify that R1 and R2 have formed OSPF adjacencies with BBR2 and examine the routing tables
of R1 and R2 routers. The routers have learned both OSPF and RIPv2 routes. Notice that the
highest RIP hop count is 2. The printouts show the OSPF neighbor information and routing
tables content on R1 and R2 routers

Interface
172.31.11.4 1 FULL/ - 00:01:31 172.31.11.4
Serial0/0.3

Interface
172.31.11.4 1 FULL/ - 00:01:46 172.31.11.4
Serial0/0.3
R1#show ip route
...


O 172.31.11.2 255.255.255.255
[110/1626] via 172.31.11.4, 00:02:11, Serial0/0.3
O 172.31.11.4 255.255.255.255
[110/64] via 172.31.11.4, 00:02:11, Serial0/0.3
R 10.200.200.14 255.255.255.255
[120/2] via 10.1.0.2, 00:00:23, Serial0/0.1
[120/2] via 10.1.1.3, 00:00:04, Ethernet0/0
R 10.200.200.12 255.255.255.255
[120/1] via 10.1.0.2, 00:00:23, Serial0/0.1
R 10.200.200.13 255.255.255.255
[120/1] via 10.1.1.3, 00:00:04, Ethernet0/0
R 10.1.3.0 255.255.255.0 [120/1] via 10.1.1.3, 00:00:04,
Ethernet0/0
R 10.1.2.0 255.255.255.0 [120/1] via 10.1.0.2, 00:00:24,
Serial0/0.1
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.11.4, 00:02:12, Serial0/0.3
R2#show ip route
...


O 172.31.11.1 255.255.255.255
[110/1626] via 172.31.11.4, 00:04:19, Serial0/0.3
O 172.31.11.4 255.255.255.255
[110/64] via 172.31.11.4, 00:04:19, Serial0/0.3
R 10.200.200.11 255.255.255.255
[120/1] via 10.1.0.1, 00:00:26, Serial0/0.1
R 10.200.200.14 255.255.255.255
[120/1] via 10.1.2.4, 00:00:09, Ethernet0/0
R 10.200.200.13 255.255.255.255
[120/2] via 10.1.0.1, 00:00:00, Serial0/0.1
[120/2] via 10.1.2.4, 00:00:09, Ethernet0/0
R 10.1.3.0 255.255.255.0 [120/1] via 10.1.2.4, 00:00:09,
Ethernet0/0
R 10.1.1.0 255.255.255.0 [120/1] via 10.1.0.1, 00:00:00,
Serial0/0.1
O 10.254.0.0 255.255.255.0
[110/128] via 172.31.11.4, 00:04:20, Serial0/0.3
Step 5 Telnet to BBR2 router and examine the routing table to verify that only routes from OSPF
routing domain are present.
BBR2#show ip route
...


O 172.31.11.1 255.255.255.255
[110/1562] via 172.31.11.1, 00:02:33, Serial0/0.3
O 172.31.11.2 255.255.255.255
[110/1562] via 172.31.11.2, 00:02:33, Serial0/0.3
Task 2: Configuring Basic Redistribution
In this task, you will configure one-way RIPv2 to OSPF redistribution and announce a default
route into a RIPv2 routing domain.
Step 6 Configure a static default route on R1 and R2 routers pointing to the IP address of BBR2 routers
S0/0.3 interface and announce a default route into the RIPv2 routing domain.
Step 7 Redistribute RIPv2 routes into OSPF on R1 and R2 edge routers without specifying a metric
value.
Verification
Step 8 Examine the routing tables of R3 and R4 routers. The default route should be present in their
routing tables. On R3 the route should point to R1 router and on R4 router the route should point
to R2 router.
Note RIP is slow in convergence. To force the convergence you should use the clear ip route *
command.
R3#show ip route
...


R 10.200.200.11 255.255.255.255
[120/1] via 10.1.1.1, 00:00:17, Ethernet0/0
R 10.200.200.14 255.255.255.255
[120/1] via 10.1.3.4, 00:00:21, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/2] via 10.1.3.4, 00:00:21, Serial0/0.1
R 10.1.2.0 255.255.255.0 [120/1] via 10.1.3.4, 00:00:23,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.1.1, 00:00:18,
Ethernet0/0
R* 0.0.0.0 0.0.0.0 [120/1] via 10.1.1.1, 00:00:18, Ethernet0/0
R4#show ip route
...


R 10.200.200.11 255.255.255.255
[120/2] via 10.1.3.3, 00:00:10, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/1] via 10.1.2.2, 00:00:21, Ethernet0/0
R 10.200.200.13 255.255.255.255
[120/1] via 10.1.3.3, 00:00:10, Serial0/0.1
R 10.1.1.0 255.255.255.0 [120/1] via 10.1.3.3, 00:00:11,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.2.2, 00:00:22,
Ethernet0/0
R* 0.0.0.0 0.0.0.0 [120/1] via 10.1.2.2, 00:00:22, Ethernet0/0
Step 9 Verify the presence of redistributed routes in the OSPF database on R1 router with the show ip
ospf database external command. All redistributed routes are described with Type-5 LSAs and
have the initial metric set to 20.
R1#show ip ospf database external



LS age: 24
Checksum: 0xF8F5
Length: 36
TOS: 0
Metric: 20

LS age: 41
Checksum: 0xF2FA
Length: 36
TOS: 0
Metric: 20

LS age: 25
Checksum: 0xEDFF
Length: 36
TOS: 0
Metric: 20

LS age: 43
Checksum: 0xDC0F
Length: 36
TOS: 0
Metric: 20

LS age: 43
Checksum: 0xD119
Length: 36
TOS: 0
Metric: 20
...remaining output omitted....
Printout 112: OSPF database information on R1 router for the redistributed
routes
Step 10 Telnet to BBR2 router and verify the redistribution of RIPv2 routes by examining the routing
table with the show ip route command. RIPv2 redistributed routes are present in the routing
table as OSPF E2 routes with the cost of 20, which is the default metric type when redistributing
into OSPF without explicitly specifying the metric type and value.
BBR2#show ip route
...


O 172.31.11.1 255.255.255.255
[110/1562] via 172.31.11.1, 00:03:16, Serial0/0.3
O 172.31.11.2 255.255.255.255
[110/1562] via 172.31.11.2, 00:03:16, Serial0/0.3
O E2 10.200.200.11 255.255.255.255
[110/20] via 172.31.11.1, 00:00:02, Serial0/0.3
O E2 10.200.200.14 255.255.255.255
[110/20] via 172.31.11.2, 00:00:08, Serial0/0.3
O E2 10.200.200.12 255.255.255.255
[110/20] via 172.31.11.2, 00:00:08, Serial0/0.3
O E2 10.200.200.13 255.255.255.255
[110/20] via 172.31.11.2, 00:00:09, Serial0/0.3
O E2 10.1.3.0 255.255.255.0 [110/20] via 172.31.11.2, 00:00:09,
Serial0/0.3
O E2 10.1.2.0 255.255.255.0 [110/20] via 172.31.11.2, 00:00:09,
Serial0/0.3
O E2 10.1.1.0 255.255.255.0 [110/20] via 172.31.11.1, 00:00:04,
Serial0/0.3
O E2 10.1.0.0 255.255.255.0 [110/20] via 172.31.11.2, 00:00:05,
Serial0/0.3
[110/20] via 172.31.11.1, 00:00:05,
Serial0/0.3
Step 11 Use the ping command to verify that you have connectivity between RIPv2 and OSPF routing
domains.
Task 3: Adjusting Administrative Distance to Eliminate
Suboptimal Routing
Due to redistribution a suboptimal routing occurs on edge R1 and R2 routers as a consequence of
OSPF having better administrative distance than RIPfor example, the route for 10.1.2.0/24 on
R1 and the route for 10.1.1.0/24 on R2 appear as OSPF routes. Therefore, you will adjust
administrative distance for the RIP routes on the edge routers to make them more attractive than
the routes for the same networks redistributed into OSPF.
Step 12 Create an access list on edge routers R1 and R2 that will match 10.1.0.0/16 and 10.200.200.0/24
subnets.
Step 13 Adjust the administrative distance to 125 for the access list-matched subnets on edge R1 and R2
routers.
Verification
Step 14 Examine the routing tables of R1 and R2 routers. The routes originated within the RIP domain
should now appear as RIP routes in the routing tables.
R1#show ip route rip
R 10.200.200.14 255.255.255.255
[120/2] via 10.1.1.3, 00:00:07, Ethernet0/0
[120/2] via 10.1.0.2, 00:00:22, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/1] via 10.1.0.2, 00:00:22, Serial0/0.1
R 10.200.200.13 255.255.255.255
[120/1] via 10.1.1.3, 00:00:07, Ethernet0/0
R 10.1.3.0 255.255.255.0 [120/1] via 10.1.1.3, 00:00:07,
Ethernet0/0
R 10.1.2.0 255.255.255.0 [120/1] via 10.1.0.2, 00:00:22,
Serial0/0.1
R2#show ip route rip
R 10.200.200.11 255.255.255.255
[120/1] via 10.1.0.1, 00:00:15, Serial0/0.1
R 10.200.200.14 255.255.255.255
R 10.200.200.13 255.255.255.255
[120/2] via 10.1.0.1, 00:00:15, Serial0/0.1
R 10.1.3.0 255.255.255.0 [120/1] via 10.1.2.4, 00:00:23,
FastEthernet0/0
R 10.1.1.0 255.255.255.0 [120/1] via 10.1.0.1, 00:00:15,
Serial0/0.1
Task 4: Filtering Routing Updates
The information about loopback addresses should not be redistributed into OSPF routing
domain. To achieve that you will configure filtering upon redistribution.
Step 15 Create an access list that matches loopback addresses of R1, R2, R3 and R4 routers.
Step 16 Use the created access list and configure filters, which will prevent redistribution of R1, R2, R3
and R4 routers loopback networks into the OSPF routing domain.
Verification
Step 17 Telnet to BBR2 router and examine the routing table. As desired, the R1, R2, R3 and R4
loopback addresses are no longer present in the routing table and are thus not accessible from the
BBR2 router any more.
BBR2#show ip route
...


O 172.31.11.1 255.255.255.255
[110/1562] via 172.31.11.1, 00:08:32, Serial0/0.3
O 172.31.11.2 255.255.255.255
[110/1562] via 172.31.11.2, 00:08:32, Serial0/0.3
O E2 10.1.3.0 [110/20] via 172.31.11.2, 00:05:22, Serial0/0.3
O E2 10.1.2.0 [110/20] via 172.31.11.2, 00:05:22, Serial0/0.3
O E2 10.1.1.0 [110/20] via 172.31.11.1, 00:05:19, Serial0/0.3
O E2 10.1.0.0 [110/20] via 172.31.11.2, 00:05:19, Serial0/0.3
[110/20] via 172.31.11.1, 00:05:19, Serial0/0.3
Task 5: Tuning Redistribution with Route Maps
All redistributed routes from RIPv2 have the same cost in OSPF routing domain. You will adjust
that by changing the default OSPF redistribution behavior.
Step 18 Create a route map on R1 and R2 routers to alter the OSPF cost of redistributed routes. Match the
RIP routes with hop count 1 and set the OSPF cost to 1000. Match all other RIP routes (in this
case, only the directly connected networks, since loopback networks are filtered upon
redistribution) and set the OSPF cost to 500.
Step 19 Reconfigure the redistribution from RIPv2 to OSPF on R1 and R2 routers by using the
configured route map.
Verification
Step 20 Examine the OSPF database information for the redistributed routes on R1 router with the show
ip ospf database external command. The initial cost for the redistributed networks is now
changed according to the routing policy. The output should be similar to the following printout.
R1#show ip ospf database external



LS age: 330
Checksum: 0xC843
Length: 36
TOS: 0
Metric: 500

LS age: 345
Checksum: 0xC248
Length: 36
TOS: 0
Metric: 500

LS age: 331
Checksum: 0xBD4D
Length: 36
TOS: 0
Metric: 500

LS age: 346
Checksum: 0xAC5C
Length: 36
TOS: 0
Metric: 500

LS age: 333
Checksum: 0x41D1
Length: 36
TOS: 0
Metric: 1000
...remaining output omitted....
Printout 117: OSPF database information on R1 router for the redistributed
routes
Step 21 Telnet to BBR2 router and examine the routers routing table. Since RIP routes are redistributed
as OSPF E2 routes, the cost is not changed throughout the OSPF domain, but equals the cost set
with route map upon redistribution.
BBR2#show ip route
...


O 172.31.11.1 255.255.255.255
[110/1562] via 172.31.11.1, 00:43:38, Serial0/0.3
O 172.31.11.2 255.255.255.255
[110/1562] via 172.31.11.2, 00:43:38, Serial0/0.3
O E2 10.1.3.0 [110/1000] via 172.31.11.1, 00:04:51, Serial0/0.3
[110/1000] via 172.31.11.2, 00:04:51, Serial0/0.3
O E2 10.1.2.0 [110/500] via 172.31.11.2, 00:05:03, Serial0/0.3
O E2 10.1.1.0 [110/500] via 172.31.11.1, 00:04:52, Serial0/0.3
O E2 10.1.0.0 [110/500] via 172.31.11.1, 00:04:52, Serial0/0.3
[110/500] via 172.31.11.2, 00:04:52, Serial0/0.3
Lab Topology
routers (BBR2 and BBR3) are accessible via telnet only.

BBR2, BBR3 Backbone routers
R1, R2 Edge routers
BBR2 212 172.31.11.4 R1 221 172.31.11.1
BBR2 211 172.31.11.4 R2 211 172.31.11.2
BBR2 120 10.254.0.2 BBR3 102 10.254.0.3
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4

Note IP addressing and backbone routing have been pre-configured to allow you to focus
Parameter Value
WAN subnet between backbone and edge routers 172.31.11.0/24
Backbone subnet 10.254.0.0/24

OSPF routing protocol is used as a backbone routing protocol. The existing OSPF routing
configuration on BBR2and BBR3 routers is shown below:
!
router ospf 1
network 10.254.0.0 0.0.0.255 area 0
network 172.31.11.0 0.0.0.255 area 0
router ospf 1
network 10.254.0.0 0.0.0.255 area 0


Copyright 2006, NIL Data Communications Configuring Route Redistribution Lab Solutions 121
BSCI
Configuring Route
Redistribution
Lab Solutions
Lab Solution
Task 1: Configuring OSPF and RIP
interface serial 0/0.3 multipoint
!
router ospf 1
network 172.31.11.0 0.0.0.255 area 0
!
router rip
version 2
network 10.0.0.0
no auto-summary
Configuration 42: OSPF and RIP configuration on R1 and R2 routers
router rip
version 2
network 10.0.0.0
no auto-summary
Configuration 43: RIP configuration on R3 and R4 routers

122 Configuring Route Redistribution Lab Solutions Copyright 2006, NIL Data Communications
Task 2: Configuring Basic Redistribution
router ospf 1
redistribute rip subnets
!
router rip
default-information originate
!
ip route 0.0.0.0 0.0.0.0 172.31.11.4
Configuration 44: RIP redistribution and default route origination on R1 and R2
routers
Task 3: Adjusting Administrative Distance to Eliminate
Suboptimal Routing
router ospf 1
distance 125 0.0.0.0 255.255.255.255 33
!
Configuration 45: Adjusting AD on R1 and R2 routers
Task 4: Filtering Routing Updates
router ospf 1
distribute-list 10 out rip
!
access-list 10 deny 10.200.200.0 0.0.0.255
access-list 10 permit any
Configuration 46: Route filtering on R1 and R2 routers
Task 5: Tuning Redistribution with Route Maps
router ospf 1
redistribute rip subnets route-map CONVERT
!
route-map CONVERT permit 10
match metric 1
set metric 1000
!
route-map CONVERT permit 20
set metric 500
Configuration 47: Route filtering with route maps on R1 and R2 routers

Copyright 2006, NIL Data Communications Configuring BGP 123
BSCI
Configuring BGP
Objective
In this exercise you will configure Border Gateway Protocol (BGP) routing in your network.
First you will configure external BGP (EBGP) on WAN connections towards two different ISPs
and internal BGP (IBGP) between your edge routers. Afterwards you will examine the
established adjacencies, the content of a BGP table, and the IP routing table.

Figure 24: Basic BGP deployment
Then you will change the IBGP configuration by deploying full mesh IBGP in your network and
examining the newly established BGP adjacencies and the IP routing table.
To allow the internal routers to install the IBGP learned routes in their routing table, you will
enable the edge routes to propagate themselves as next-hop for BGP learned routes and disable
the synchronization between BGP and IGP routing protocols, and then re-examine the BGP and
IP routing tables.
124 Configuring BGP Copyright 2006, NIL Data Communications

Figure 25: Full-mesh IBGP deployment
Configure EBGP between R1 and R2 routers and the BBR1 and BBR2 routers.
Configure the IBGP between R1 and R2 routers.
Configure full mesh IBGP between R1, R2, R3 and R4 routers.
Configure, during the configuration of full mesh IBGP:
-Next-hop-self
-Disabling synchronization
Verify connectivity to the BBR1 and BBR2 router.
Verify BGP operation.
Command List
Command Task
clear ip bgp * Resets all BGP information.
neighbor IP-address next-hop-self Allows modification of the next-hop router to
itself.
neighbor IP-address remote-as as-number Establishes a BGP neighbor relationship.
neighbor IP-address update-source
Loopback0
Specifies a source address for a BGP
session.
network IP-address [mask mask] Specifies the network to be advertised.
no synchronization Turns off the synchronization between BGP
and the IGP.
router bgp as-number Enables BGP with the autonomous system
(AS).
show ip bgp Shows BGP information.
show ip bgp neighbors Shows detail BGP neighbor status.
show ip bgp summary Shows summary BGP neighbor status.
Table 27: Configuration and monitoring commands used in the Configuring BGP
Lab exercise
Task 1: Configuring EBGP and IBGP
Step 1 Configure EBGP at R1 and R2 routers using AS number 65001. Establish the EBGP neighbor
relations with BBR1 (IP address 172.31.1.3) in AS 64998 and with BBR2 (IP address
172.31.11.4) in AS 64999.
Step 2 Configure IBGP between R1 and R2 routers. Use the IP addresses configured on S0/0.1
interfaces.
Step 3 Advertise 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24 and 10.1.3.0/24 networks to the AS 64998 and
AS 64999. Remember that the major network 10.0.0.0 is sub netted, so you will have to specify
the mask to announce the subnets and that the networks listed in the network statement must
match the networks in routing table exactly.
Verification
Step 4 At R1 and R2 routers, examine the BGP neighbor status using the show ip bgp summary
command. There are two EBGP neighbors and one IBGP neighbor. The BGP neighbor state
shows the number of prefixes learned from BGP neighbors.
R1#show ip bgp summary
BGP router identifier 10.200.200.11, local AS number 65001
BGP table version is 8, main routing table version 8
7 network entries and 17 paths using 1291 bytes of memory
12 BGP path attribute entries using 720 bytes of memory
4 BGP AS-PATH entries using 96 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP activity 14/15 prefixes, 35/18 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
10.1.0.2 4 65001 31 30 8 0 0 00:03:17
7
172.31.1.3 4 64998 21 22 8 0 0 00:03:11
3
172.31.11.4 4 64999 23 25 8 0 0 00:02:31
3
Printout 121: BGP neighbor status on R1 router

State/PfxRcd
10.1.0.1 4 65001 30 31 8 0 0 00:03:43
7
172.31.1.3 4 64998 22 25 8 0 0 00:03:42
3
172.31.11.4 4 64999 23 23 8 0 0 00:03:22
3
Verify the detailed BGP neighbor status of the BBR1 router (172.31.1.3) with the show ip bgp
neighbor command on the R1 router. The current BGP version is 4, state is established, and you
can also see the time elapsed since the adjacency is up. The output should be similar to the
printout below:
R1#show ip bgp neighbors 172.31.1.3
BGP neighbor is 172.31.1.3, remote AS 64998, external link
BGP version 4, remote router ID 172.31.1.3
BGP state = Established, up for 00:06:47
Last read 00:00:40, hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
Route refresh: advertised and received(new)
Address family IPv4 Unicast: advertised and received
Received 21 messages, 0 notifications, 0 in queue
Sent 22 messages, 0 notifications, 0 in queue
Route refresh request: received 0, sent 0
Default minimum time between advertisement runs is 30 seconds

For address family: IPv4 Unicast
BGP table version 8, neighbor version 8
Index 1, Offset 0, Mask 0x2
3 accepted prefixes consume 108 bytes
Prefix advertised 10, suppressed 0, withdrawn 0
Number of NLRIs in the update sent: max 2, min 0

Connections established 2; dropped 1
Last reset 00:07:30, due to Peer closed the session
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 172.31.1.1, Local port: 179
Foreign host: 172.31.1.3, Foreign port: 11015

Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)

Event Timers (current time is 0x18EA01E):
Timer Starts Wakeups Next
Retrans 6 0 0x0
TimeWait 0 0 0x0
AckHold 6 3 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0

iss: 1749460413 snduna: 1749460704 sndnxt: 1749460704 sndwnd:
16094
irs: 2505370990 rcvnxt: 2505371271 rcvwnd: 16104 delrcvwnd:
280

SRTT: 165 ms, RTTO: 1172 ms, RTV: 1007 ms, KRTT: 0 ms
minRTT: 32 ms, maxRTT: 300 ms, ACK hold: 200 ms
Flags: passive open, retransmission timeout, nagle, gen tcbs

Datagrams (max data segment is 1460 bytes):
Rcvd: 12 (out of order: 0), with data: 6, total data bytes: 280
Sent: 9 (retransmit: 0, fastretransmit: 0), with data: 5, total data
bytes: 290
Printout 123: Detailed BGP neighbor status on R1 router
Step 5 Examine the BGP table and IP routing table on R1 and R2 routers using the show ip bgp and
show ip route commands. The BGP table is populated with seven different prefixes. Networks
10.1.x.0/24 are locally originated and learned from the IBGP neighbor. The remote networks are
received from the BBR1 and BBR2 routers and the other edge router.
Step 6 Notice that weight for locally originated routes is set to 32768, which makes locally originated
routes best. The MED attribute (metric) for local networks, such as 10.1.x.0/24 networks, is set
according to the RIP metric. The printouts show the content of BGP and routing tables on R1 and
R2 routers.
R1#show ip bgp
BGP table version is 8, local router ID is 10.200.200.11
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
* i10.1.0.0/24 10.1.0.2 0 100 0 i
*> 0.0.0.0 0 32768 i
* i10.1.1.0/24 10.1.2.4 2 100 0 i
*> 0.0.0.0 0 32768 i
* i10.1.2.0/24 10.1.0.2 0 100 0 i
*> 0.0.0.0 2 32768 i
* i10.1.3.0/24 10.1.2.4 1 100 0 i
*> 0.0.0.0 1 32768 i
* 10.254.0.0/24 172.31.11.4 0 64999 64998
i
* i 172.31.1.3 0 100 0 64998 i
*> 172.31.1.3 0 0 64998 i
* 172.31.1.0/24 172.31.11.4 0 64999 64998
i
* i 172.31.1.3 0 100 0 64998 i
*> 172.31.1.3 0 0 64998 i
* 172.31.11.0/24 172.31.1.3 0 64998 64999
i
* i 172.31.11.4 0 100 0 64999 i
*> 172.31.11.4 0 0 64999 i
Printout 124: BGP information on R1 router
R1#show ip route
...


R 10.200.200.14 255.255.255.255
R 10.200.200.12 255.255.255.255
R 10.200.200.13 255.255.255.255
R 10.1.3.0 255.255.255.0 [120/1] via 10.1.1.3, 00:00:07,
FastEthernet0/0
R 10.1.2.0 255.255.255.0 [120/2] via 10.1.1.3, 00:00:07,
FastEthernet0/0
B 10.254.0.0 255.255.255.0 [20/0] via 172.31.1.3, 00:23:49
R2#show ip bgp
internal

* i10.1.0.0/24 10.1.0.1 0 100 0 i
*> 0.0.0.0 0 32768 i
* i10.1.1.0/24 10.1.0.1 0 100 0 i
*> 0.0.0.0 2 32768 i
* i10.1.2.0/24 10.1.1.3 2 100 0 i
*> 0.0.0.0 0 32768 i
* i10.1.3.0/24 10.1.1.3 1 100 0 i
*> 0.0.0.0 1 32768 i
* 10.254.0.0/24 172.31.11.4 0 64999 64998
i
* i 172.31.1.3 0 100 0 64998 i
*> 172.31.1.3 0 0 64998 i
* 172.31.1.0/24 172.31.11.4 0 64999 64998
i
* i 172.31.1.3 0 100 0 64998 i
*> 172.31.1.3 0 0 64998 i
* 172.31.11.0/24 172.31.1.3 0 64998 64999
i
* i 172.31.11.4 0 100 0 64999 i
*> 172.31.11.4 0 0 64999 i
Printout 126: BGP information on R2 router
R2#show ip route
...


R 10.200.200.11 255.255.255.255
R 10.200.200.14 255.255.255.255
R 10.200.200.13 255.255.255.255
R 10.1.3.0 255.255.255.0 [120/1] via 10.1.2.4, 00:00:06,
FastEthernet0/0
R 10.1.1.0 255.255.255.0 [120/2] via 10.1.2.4, 00:00:06,
FastEthernet0/0
B 10.254.0.0 255.255.255.0 [20/0] via 172.31.1.3, 00:26:43
Step 7 Telnet to the BBR1 router and examine the BGP table and BGP neighbor information. Except
from locally originated routes, all other routes are received from three different BGP neighbors.
The criteria for the best routes consists of the shortest AS path, origin type (IGP preferred over
Incomplete), then the lowest MED attribute and finally the oldest route.
Step 8 For example, to reach the 10.1.0.0/24 network, three possible next hops exist. The 10.254.0.2
next hop with the longest AS path is obviously the worst one. The 172.31.1.1 is preferred over
172.31.1.2 because BBR1 learned about 10.1.0.0/24 from 172.31.1.1 first (the BGP adjacency
was established with R1 prior to R2). The printouts show the content of BGP and routing table on
BBR1 router.
Note If the BGP adjacency on your BBR1 router were established first with R2 router, the R2 router
would be chosen as the next hop.
BBR1#show ip bgp
internal

* 10.1.0.0/24 10.254.0.2 0 64999 65001
i
* 172.31.1.2 0 0 65001 i
*> 172.31.1.1 0 0 65001 i
* 10.1.1.0/24 10.254.0.2 0 64999 65001
i
* 172.31.1.2 2 0 65001 i
*> 172.31.1.1 0 0 65001 i
* 10.1.2.0/24 10.254.0.2 0 64999 65001
i
*> 172.31.1.2 0 0 65001 i
* 172.31.1.1 2 0 65001 i
* 10.1.3.0/24 10.254.0.2 0 64999 65001
i
* 172.31.1.2 1 0 65001 i
*> 172.31.1.1 1 0 65001 i
*> 10.254.0.0/24 0.0.0.0 0 32768 i
*> 172.31.1.0/24 0.0.0.0 0 32768 i
* 172.31.11.0/24 172.31.1.2 0 65001 64999
i
* 172.31.1.1 0 65001 64999
i
*> 10.254.0.2 0 0 64999 i
Printout 128: BGP table on BBR1 router
BBR1#show ip bgp summary

State/PfxRcd
10.254.0.2 4 64999 128 131 13 0 0 00:42:41
5
172.31.1.1 4 65001 130 126 13 0 0 00:42:42
5
172.31.1.2 4 65001 131 127 13 0 0 00:42:45
5
Printout 129: BGP neighbors on BBR1 router
Step 9 Now examine the routing table at the BBR1 router. The networks learned via BGP from R1 and
R2 routers are present in the IP routing table with the next hop set to the best next hop
determined by the BGP.
BBR1#show ip route
...


B 172.31.11.0 [20/0] via 10.254.0.2, 00:54:56
B 10.1.3.0 [20/1] via 172.31.1.1, 00:41:05
B 10.1.2.0 [20/0] via 172.31.1.2, 00:54:59
B 10.1.1.0 [20/0] via 172.31.1.1, 00:54:59
B 10.1.0.0 [20/0] via 172.31.1.1, 00:54:59
Step 10 Verify the connectivity to BBR3 router (10.254.0.3) from R1 and R2 edge routers and R3 and R4
internal routers by using the ping command. Since there is no redistribution from BGP to RIP on
R1 and R2 edge routers, the internal routers do not know about networks 172.31.1.0/24,
172.31.11.0/24 and 10.254.0.0/24, and pings from R3 and R4 are not successful.
Task 2: Configuring Full-Mesh IBGP
Step 11 Configure R1, R2, R3 and R4 routers to provide full-mesh of IBGP sessions. There should be a
total of six IBGP sessions including the existing IBGP session between the R1 and R2 router. To
configure IBGP sessions between edge and internal routers and between internal routers, use the
IP addresses configured on loopback interfaces.
Step 12 Advertise 10.200.200.13/32 prefix into the IBGP at R3 router.
Step 13 Advertise 10.200.200.14/32 prefix into the IBGP at R4 router.
Verification
Step 14 Verify the establishment of IBGP sessions by inspecting the BGP neighbor relationships at R1,
R2, R3 and R4 routers. The edge routers R1 and R2 should have three IBGP sessions and two
EBGP sessions. The internal routers R3 and R4 should have three IBGP sessions. The printouts
show the BGP neighbor information on routers R1, R2, R3 and R4,
Note It may take a minute or so for the changes to appear.

State/PfxRcd
10.1.0.2 4 65001 31 30 10 0 0 00:17:11
7
10.200.200.13 4 65001 4 8 10 0 0 00:01:59
1
10.200.200.14 4 65001 4 8 10 0 0 00:01:30
1
172.31.1.3 4 64998 22 24 10 0 0 00:17:05
3
172.31.11.4 4 64999 23 27 10 0 0 00:16:24
3

State/PfxRcd
10.1.0.1 4 65001 30 31 10 0 0 00:17:30
7
10.200.200.13 4 65001 4 8 10 0 0 00:02:12
1
10.200.200.14 4 65001 4 8 10 0 0 00:01:48
1
172.31.1.3 4 64998 23 27 10 0 0 00:17:30
3
172.31.11.4 4 64999 25 25 10 0 0 00:17:10
3

State/PfxRcd
10.200.200.11 4 65001 8 4 7 0 0 00:02:42
5
10.200.200.12 4 65001 8 4 7 0 0 00:02:35
7
10.200.200.14 4 65001 7 7 7 0 0 00:02:27
1

State/PfxRcd
10.200.200.11 4 65001 8 4 7 0 0 00:02:30
7
10.200.200.12 4 65001 8 4 7 0 0 00:02:29
5
10.200.200.13 4 65001 7 7 7 0 0 00:02:44
1
Step 15 Examine the IP routing table of internal routers R3 and R4. Notice that 10.254.0.0/24,
172.31.1.0/24 and 172.31.11.0/24 learned via IBGP are not present in the routing table. The
printouts show the routing table content on router R3 and R4.
R3#show ip route
...


R 10.200.200.11 255.255.255.255
[120/1] via 10.1.1.1, 00:00:00, Ethernet0/0
R 10.200.200.14 255.255.255.255
[120/1] via 10.1.3.4, 00:00:03, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/2] via 10.1.3.4, 00:00:03, Serial0/0.1
R 10.1.2.0 255.255.255.0 [120/1] via 10.1.3.4, 00:00:04,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.1.1, 00:00:01,
Ethernet0/0
R4#show ip route
...


R 10.200.200.11 255.255.255.255
[120/2] via 10.1.3.3, 00:00:11, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/1] via 10.1.2.2, 00:00:19, Ethernet0/0
R 10.200.200.13 255.255.255.255
[120/1] via 10.1.3.3, 00:00:11, Serial0/0.1
R 10.1.1.0 255.255.255.0 [120/1] via 10.1.3.3, 00:00:12,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.2.2, 00:00:21,
Ethernet0/0
Step 16 Now check the BGP table on the R3 and R4 router. The next hop to reach 10.254.0.0/24,
172.31.1.0/24 networks is 172.31.1.3 on both routers. The next hop to reach the 172.31.11.0/24
network is 172.31.11.4 on both routers. However, the internal routers do not know how to reach
these next hops, and the routes are therefore not installed into the routing table. The printouts
show the BGP table content on routers R3 and R4.
R3#show ip bgp
internal

* i10.1.0.0/24 10.200.200.12 0 100 0 i
*>i 10.200.200.11 0 100 0 i
* i10.1.1.0/24 10.1.2.4 2 100 0 i
*>i 10.200.200.11 0 100 0 i
*>i10.1.2.0/24 10.200.200.12 0 100 0 i
*>i10.1.3.0/24 10.1.2.4 1 100 0 i
*> 10.200.200.13/32 0.0.0.0 0 32768 i
*>i10.200.200.14/32 10.200.200.14 0 100 0 i
* i10.254.0.0/24 172.31.1.3 0 100 0 64998 i
* i 172.31.1.3 0 100 0 64998 i
* i172.31.1.0/24 172.31.1.3 0 100 0 64998 i
* i 172.31.1.3 0 100 0 64998 i
* i172.31.11.0/24 172.31.11.4 0 100 0 64999 i
* i 172.31.11.4 0 100 0 64999 i
Printout 137: BGP table on R3 router
R4#show ip bgp
internal

*>i10.1.0.0/24 10.200.200.12 0 100 0 i
* i 10.200.200.11 0 100 0 i
*>i10.1.1.0/24 10.200.200.11 0 100 0 i
*>i10.1.2.0/24 10.200.200.12 0 100 0 i
* i 10.1.1.3 2 100 0 i
*>i10.1.3.0/24 10.1.1.3 1 100 0 i
*>i10.200.200.13/32 10.200.200.13 0 100 0 i
*> 10.200.200.14/32 0.0.0.0 0 32768 i
* i10.254.0.0/24 172.31.1.3 0 100 0 64998 i
* i 172.31.1.3 0 100 0 64998 i
* i172.31.1.0/24 172.31.1.3 0 100 0 64998 i
* i 172.31.1.3 0 100 0 64998 i
* i172.31.11.0/24 172.31.11.4 0 100 0 64999 i
* i 172.31.11.4 0 100 0 64999 i
Task 3: Changing the Next Hop Information
Step 17 Change the BGP next hop processing at R1 and R2 routers and set it up so that they announce
themselves as the next hop for BGP prefixes advertised to internal routers.
Verification
Step 18 At R3 and R4 router, verify that the next hop is changed for BGP learned prefixes from R1 and
R2 edge routers. However, external networks are still not in the routing table since the BGP
synchronization rule prevents BGP from installing them in the routing table. The rule ensures
that the routers within the AS contain synchronized IGP and BGP information for all BGP-
advertised prefixes before they can route traffic to those prefixes. Since there is no need for
redistribution from BGP into the IGP due to the full mesh of IBGP sessions, the synchronization
never occurs in this exercise. The printouts show the content of BGP and routing tables on
routers R3 and R4.
R3#show ip bgp
internal

* i10.1.0.0/24 10.200.200.12 0 100 0 i
*>i 10.200.200.11 0 100 0 i
* i10.1.1.0/24 10.200.200.12 2 100 0 i
*>i 10.200.200.11 0 100 0 i
* i10.1.2.0/24 10.200.200.11 2 100 0 i
*>i 10.200.200.12 0 100 0 i
*>i10.1.3.0/24 10.200.200.11 1 100 0 i
* i 10.200.200.12 1 100 0 i
*> 10.200.200.13/32 0.0.0.0 0 32768 i
*>i10.200.200.14/32 10.200.200.14 0 100 0 i
* i10.254.0.0/24 10.200.200.12 0 100 0 64998 i
* i 10.200.200.11 0 100 0 64998 i
* i172.31.1.0/24 10.200.200.12 0 100 0 64998 i
* i 10.200.200.11 0 100 0 64998 i
* i172.31.11.0/24 10.200.200.12 0 100 0 64999 i
* i 10.200.200.11 0 100 0 64999 i
R4#show ip bgp
internal

*>i10.1.0.0/24 10.200.200.12 0 100 0 i
* i 10.200.200.11 0 100 0 i
* i10.1.1.0/24 10.200.200.12 2 100 0 i
*>i 10.200.200.11 0 100 0 i
*>i10.1.2.0/24 10.200.200.12 0 100 0 i
* i 10.200.200.11 2 100 0 i
*>i10.1.3.0/24 10.200.200.12 1 100 0 i
* i 10.200.200.11 1 100 0 i
*>i10.200.200.13/32 10.200.200.13 0 100 0 i
*> 10.200.200.14/32 0.0.0.0 0 32768 i
* i10.254.0.0/24 10.200.200.12 0 100 0 64998 i
* i 10.200.200.11 0 100 0 64998 i
* i172.31.1.0/24 10.200.200.12 0 100 0 64998 i
* i 10.200.200.11 0 100 0 64998 i
* i172.31.11.0/24 10.200.200.12 0 100 0 64999 i
* i 10.200.200.11 0 100 0 64999 i
R3#show ip route
...


R 10.200.200.11 255.255.255.255
[120/1] via 10.1.1.1, 00:00:23, Ethernet0/0
R 10.200.200.14 255.255.255.255
[120/1] via 10.1.3.4, 00:00:24, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/2] via 10.1.3.4, 00:00:24, Serial0/0.1
R 10.1.2.0 255.255.255.0 [120/1] via 10.1.3.4, 00:00:25,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.1.1, 00:00:24,
Ethernet0/0
R4#show ip route
...


R 10.200.200.11 255.255.255.255
[120/2] via 10.1.3.3, 00:00:05, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/1] via 10.1.2.2, 00:00:08, Ethernet0/0
R 10.200.200.13 255.255.255.255
[120/1] via 10.1.3.3, 00:00:05, Serial0/0.1
R 10.1.1.0 255.255.255.0 [120/1] via 10.1.3.3, 00:00:06,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.2.2, 00:00:09,
Ethernet0/0
Task 4: Disabling the Synchronization
Step 19 Disable the BGP synchronization on edge and internal routers. The synchronization can be
turned off since full-mesh IBGP is deployed.
Verification
Step 20 Examine both the BGP and the routing table at R3 and R4 routers. External networks
10.254.0.0/24, 172.31.1.0/24 and 172.31.11.0/24 are now present in the routing table. Both R3
and R4 receive two instances of the same prefixes over two IBGP sessions to the edge R1 and R2
routers. The IBGP path through the nearest next hop, as determined by the IGP (RIPv2), is
selected as the best by BGP, since all other BGP path attributes are equal. Consequently, the next
hop for those prefixes in the routing table is set to that same nearest next hop. On the R3 router,
this is 10.200.200.11 and on the R4 router, this is 10.200.200.12. The printouts show the content
of BGP and routing tables on routers R3 and R4.
R3#show ip bgp
internal

* i10.1.0.0/24 10.200.200.12 0 100 0 i
*>i 10.200.200.11 0 100 0 i
* i10.1.1.0/24 10.200.200.12 2 100 0 i
*>i 10.200.200.11 0 100 0 i
* i10.1.2.0/24 10.200.200.11 2 100 0 i
*>i 10.200.200.12 0 100 0 i
*>i10.1.3.0/24 10.200.200.11 1 100 0 i
* i 10.200.200.12 1 100 0 i
*> 10.200.200.13/32 0.0.0.0 0 32768 i
*>i10.200.200.14/32 10.200.200.14 0 100 0 i
* i10.254.0.0/24 10.200.200.12 0 100 0 64998 i
*>i 10.200.200.11 0 100 0 64998 i
* i172.31.1.0/24 10.200.200.12 0 100 0 64998 i
*>i 10.200.200.11 0 100 0 64998 i
* i172.31.11.0/24 10.200.200.12 0 100 0 64999 i
*>i 10.200.200.11 0 100 0 64999 i
R3#show ip route
...


B 172.31.1.0 [200/0] via 10.200.200.11, 00:01:51
B 172.31.11.0 [200/0] via 10.200.200.11, 00:01:51
R 10.200.200.11 255.255.255.255
[120/1] via 10.1.1.1, 00:00:13, Ethernet0/0
R 10.200.200.14 255.255.255.255
[120/1] via 10.1.3.4, 00:00:13, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/2] via 10.1.3.4, 00:00:14, Serial0/0.1
R 10.1.2.0 255.255.255.0 [120/1] via 10.1.3.4, 00:00:14,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.1.1, 00:00:15,
Ethernet0/0
B 10.254.0.0 255.255.255.0 [200/0] via 10.200.200.11, 00:01:52

R4#show ip bgp
internal

*>i10.1.0.0/24 10.200.200.12 0 100 0 i
* i 10.200.200.11 0 100 0 i
* i10.1.1.0/24 10.200.200.12 2 100 0 i
*>i 10.200.200.11 0 100 0 i
*>i10.1.2.0/24 10.200.200.12 0 100 0 i
* i 10.200.200.11 2 100 0 i
*>i10.1.3.0/24 10.200.200.12 1 100 0 i
* i 10.200.200.11 1 100 0 i
*>i10.200.200.13/32 10.200.200.13 0 100 0 i
*> 10.200.200.14/32 0.0.0.0 0 32768 i
*>i10.254.0.0/24 10.200.200.12 0 100 0 64998 i
* i 10.200.200.11 0 100 0 64998 i
*>i172.31.1.0/24 10.200.200.12 0 100 0 64998 i
* i 10.200.200.11 0 100 0 64998 i
*>i172.31.11.0/24 10.200.200.12 0 100 0 64999 i
* i 10.200.200.11 0 100 0 64999 i
R4#show ip route
...


B 172.31.1.0 [200/0] via 10.200.200.12, 00:07:55
B 172.31.11.0 [200/0] via 10.200.200.12, 00:07:55
R 10.200.200.11 255.255.255.255
[120/2] via 10.1.3.3, 00:00:01, Serial0/0.1
R 10.200.200.12 255.255.255.255
[120/1] via 10.1.2.2, 00:00:03, Ethernet0/0
R 10.200.200.13 255.255.255.255
[120/1] via 10.1.3.3, 00:00:02, Serial0/0.1
R 10.1.1.0 255.255.255.0 [120/1] via 10.1.3.3, 00:00:02,
Serial0/0.1
R 10.1.0.0 255.255.255.0 [120/1] via 10.1.2.2, 00:00:04,
Ethernet0/0
B 10.254.0.0 255.255.255.0 [200/0] via 10.200.200.12, 00:07:56
Step 21 Check that you have connectivity from internal routers to the 10.254.0.0/24 network with the
ping command.

Lab Topology
routers (BBR1, BBR2 and BBR3) in the figure are accessible via telnet only.

BBR1, BBR2, BBR3 Routers that are part of external routing domains
R1, R2 Edge routers
BBR1 236 172.31.1.3 R1 263 172.31.1.1
BBR1 331 172.31.1.3 R2 313 172.31.1.2
BBR2 212 172.31.11.4 R1 221 172.31.11.1
BBR2 211 172.31.11.4 R2 211 172.31.11.2
BBR3 103 10.254.0.3 R1 130 10.254.0.1
BBR3 102 10.254.0.3 R2 120 10.254.0.2
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
Note IP addressing and routing have been pre-configured to allow you to focus exclusively on the
objectives of the exercise.
Parameter Value
WAN subnet between BBR1 and R1, R2 edge routers 172.31.1.0/24
Eternal WAN subnet 10.254.0.0/24

Existing BGP and RIP Routing
BGP routing protocol is used as a routing protocol between BBR1, BBR2 and R1, R2 edge
routers. The existing BGP routing configuration on BBR1 and BBR2 routers is shown below:
router bgp 64998
bgp log-neighbor-changes
network 10.254.0.0 mask 255.255.255.0
network 172.31.1.0 mask 255.255.255.0
neighbor 10.254.0.2 remote-as 64999
Printout 147: BGP routing on BBR1 router
router bgp 64999
network 172.31.11.0 mask 255.255.255.0
RIP routing protocol is used as an IGP routing protocol between R1, R3, R2, R4 and R3, R4
routers. RIP is disabled between R1 and R2 routers and the default route is injected into the RIP
routing domain. The existing RIP routing configuration is shown below:
router rip
version 2
no auto-summary
passive-interface serial 0/0.1
network 10.0.0.0
Printout 149: RIP routing on R1 and R2 routers
router rip
version 2
no auto-summary
network 10.0.0.0
Printout 150: RIP routing on R3 and R4 routers

Copyright 2006, NIL Data Communications Configuring BGP Lab Solutions 141
BSCI
Configuring BGP
Lab Solutions
Lab Solution
Task 1: Configuring EBGP and IBGP
router bgp 65001
network 10.1.0.0 mask 255.255.255.0
network 10.1.1.0 mask 255.255.255.0
network 10.1.2.0 mask 255.255.255.0
network 10.1.3.0 mask 255.255.255.0
Configuration 48: BGP configuration on R1 router
router bgp 65001
network 10.1.0.0 mask 255.255.255.0
network 10.1.1.0 mask 255.255.255.0
network 10.1.2.0 mask 255.255.255.0
network 10.1.3.0 mask 255.255.255.0
Configuration 49: BGP configuration on R2 router
142 Configuring BGP Lab Solutions Copyright 2006, NIL Data Communications
Task 2: Configuring Full-Mesh IBGP
router bgp 65001
neighbor 10.200.200.13 update-source Loopback0
Configuration 50: Full-mesh IBGP configuration on R1 and R2 routers
router bgp 65001
network 10.200.200.13 mask 255.255.255.255
Configuration 51: Full-mesh IBGP configuration on R3 router
router bgp 65001
network 10.200.200.14 mask 255.255.255.255
Configuration 52: Full-mesh IBGP configuration on R4 router
Task 3: Changing the Next Hop Information
router bgp 65001
neighbor 10.200.200.13 next-hop-self
Configuration 53: BGP next hop processing adjustment on R1 and R2 routers
Task 4: Disabling the Synchronization
router bgp 65001
no synchronization
Configuration 54: BGP synchronization configuration on R1, R2, R3 and R4
routers

Copyright 2006, NIL Data Communications Scaling BGP 143
BSCI
Scaling BGP
Objective
Your companys every day operation heavily relies on e-commerce applications. The corporate
network is therefore connected to two different ISPs, and the connections terminate at two
different edge routers. The ISPs have asked you to minimize the number of prefixes that you
announce so you will optimize BGP operation using route aggregation on your edge routers and
investigate the BGP path selection process.

Figure 28: BGP route aggregation
Then you decide to implement a routing policy for the outgoing traffic to a certain network by
adjusting the local preference. At the same time you also influence the path selection for
incoming traffic to your AS by manipulating the MED attribute.
144 Scaling BGP Copyright 2006, NIL Data Communications

Figure 29: BGP routing policy
Configure BGP aggregation towards AS 64999 and AS 64998.
Change the BGP local preference to adjust routing policy for certain outgoing traffic.
Change the MED attribute to manipulate path selection into your AS.
Verify the configured routing policy and Border Gateway Protocol (BGP) operation.
Command List
Command Task
access-list number permit|deny IP-address Creates a standard access list to
permit/deny traffic.
aggregate-address IP-address mask
summary-only
Allows only the summarized route to be
advertised.
clear ip bgp Restarts the BGP session with your BGP
neighbor.
clear ip bgp neighbor soft in|out Performs BGP soft reconfiguration with a
BGP neighbor.
match ip address access-list Matches the IP address in a route-map.
neighbor neighbor route-map name {in|out} Applies a route map to incoming or
outgoing routing updates.
route-map map-name permit|deny
sequence-number
Creates a route map.
router bgp as-number Enables BGP with the autonomous system
(AS).
set local-preference num Sets the local preference attribute within a
route-map.
set metric num Sets the metric attribute within a route-map.
show ip bgp Shows BGP information.
show ip bgp network/prefix longer-prefixes Displays route and more specific routes in
BGP table.
show ip bgp summary Shows summary BGP neighbor status.
Table 31: Configuration and monitoring commands used in the Scaling BGP Lab
exercise
Task 1: Configuring BGP Route Summarization and Examining
BGP Path Selection Process
Step 1 Configure BGP route summarization at R1 and R2 edge routers and summarize all but loopback
networks to 10.1.0.0/16. Advertise only loopback and summary networks to the neighboring AS
numbers.
Verification
Step 2 Inspect the BGP information about 10.1.x.0/24 networks at R1 and R2 routers with the show ip
bgp 10.1.0.0/16 longer-prefixes command. Notice that 10.1.x.0/24 prefixes are suppressed and
the 10.1.0.0/16 summary is present in the BGP table.
R1#show ip bgp 10.1.0.0/16 longer-prefixes
internal

s> 10.1.0.0/24 0.0.0.0 0 32768 i
*> 10.1.0.0/16 0.0.0.0 32768 i
* i 10.1.0.2 100 0 i
s> 10.1.1.0/24 0.0.0.0 0 32768 i
s> 10.1.2.0/24 0.0.0.0 2 32768 i
s> 10.1.3.0/24 0.0.0.0 1 32768 i
Printout 151: 10.1.0.0/16 prefix BGP information on R1 router
internal

s> 10.1.0.0/24 0.0.0.0 0 32768 i
* i10.1.0.0/16 10.1.0.1 100 0 i
*> 0.0.0.0 32768 i
s> 10.1.1.0/24 0.0.0.0 2 32768 i
s> 10.1.2.0/24 0.0.0.0 0 32768 i
s> 10.1.3.0/24 0.0.0.0 1 32768 i
Printout 152: 10.1.0.0/16 prefix BGP information on R2 router
Step 3 Telnet to BBR1 and BBR2 routers to inspect the BGP and routing table. Routers do not have
information about more specific 10.1.0.0/16 subnets, since that information is suppressed at edge
routers by the aggregate-address command. Since there are two routes with the same AS path
length for the network 10.1.0.0/16, the oldest one is chosen and put into the routing table. The
printouts below show the content of the BGP and routing tables on routers BBR1 and BBR2
routers.
Note The best route to 10.1.0.0/16 on BBR1 router in the next two printouts is through 172.31.1.1
(R1). In your case, the best route could be through 172.31.1.2 (R2), depending on the route
age.
BBR1#show ip bgp
internal

* 10.1.0.0/16 10.254.0.2 0 64999 65001
i
* 172.31.1.2 0 65001 i
*> 172.31.1.1 0 65001 i
* 10.97.97.0/24 10.254.0.3 0 64999 64997
i
*> 10.254.0.3 0 0 64997 i
* 10.200.200.13/32 10.254.0.2 0 64999 65001
i
* 172.31.1.2 0 65001 i
*> 172.31.1.1 0 65001 i
* 10.200.200.14/32 10.254.0.2 0 64999 65001
i
* 172.31.1.2 0 65001 i
*> 172.31.1.1 0 65001 i
* 10.254.0.0/24 10.254.0.3 0 64999 64997
i
*> 10.254.0.3 0 0 64997 i
*> 172.31.1.0/24 0.0.0.0 0 32768 i
*> 172.31.2.0/24 0.0.0.0 0 32768 i
*> 172.31.11.0/24 10.254.0.2 0 0 64999 i
*> 172.31.22.0/24 10.254.0.2 0 0 64999 i
BBR1#show ip route
...


B 172.31.22.0 [20/0] via 10.254.0.2, 00:04:58
C 172.31.2.0 is directly connected, Loopback0
B 172.31.11.0 [20/0] via 10.254.0.2, 00:04:58
B 10.200.200.14 255.255.255.255 [20/0] via 172.31.1.1, 00:04:58
B 10.200.200.13 255.255.255.255 [20/0] via 172.31.1.1, 00:04:58
B 10.97.97.0 255.255.255.0 [20/0] via 10.254.0.3, 00:05:00
B 10.1.0.0 255.255.0.0 [20/0] via 172.31.1.1, 00:05:00
Note The best route to 10.1.0.0/16 on BBR2 router in the next two printouts is through 172.31.11.1
(R1). In your case, the best route could be through 172.31.11.2 (R2), depending of the route
age.
BBR2#show ip bgp
internal

* 10.1.0.0/16 172.31.11.2 0 65001 i
* 10.254.0.1 0 64998 65001
i
*> 172.31.11.1 0 65001 i
* 10.97.97.0/24 10.254.0.3 0 64998 64997
i
*> 10.254.0.3 0 0 64997 i
* 10.200.200.13/32 10.254.0.1 0 64998 65001
i
* 172.31.11.2 0 65001 i
*> 172.31.11.1 0 65001 i
* 10.200.200.14/32 10.254.0.1 0 64998 65001
i
* 172.31.11.2 0 65001 i
*> 172.31.11.1 0 65001 i
* 10.254.0.0/24 10.254.0.3 0 64998 64997
i
*> 10.254.0.3 0 0 64997 i
*> 172.31.1.0/24 10.254.0.1 0 0 64998 i
*> 172.31.2.0/24 10.254.0.1 0 0 64998 i
*> 172.31.11.0/24 0.0.0.0 0 32768 i
*> 172.31.22.0/24 0.0.0.0 0 32768 i
BBR2#show ip route
...


C 172.31.22.0 is directly connected, Loopback0
B 172.31.2.0 [20/0] via 10.254.0.1, 00:05:17
B 172.31.1.0 [20/0] via 10.254.0.1, 00:05:17
B 10.200.200.14 255.255.255.255 [20/0] via 172.31.11.1, 00:05:47
B 10.200.200.13 255.255.255.255 [20/0] via 172.31.11.1, 00:05:47
B 10.97.97.0 255.255.255.0 [20/0] via 10.254.0.3, 00:05:49
B 10.1.0.0 255.255.0.0 [20/0] via 172.31.11.1, 00:05:48
Step 4 Verify that you have the connectivity with ping from BBR1 and BBR2 routers to 10.1.3.3 and
10.1.3.4.
Step 5 Now examine the BGP information for 172.31.2.0/24 and 172.31.22.0/24 networks on R1 and R2
routers with the show ip bgp 172.31.2.0/24 longer-prefixes and the show ip bgp 172.31.22.0/24
longer prefixes commands. The information about those networks is received from EBGP
neighbors in AS 64998 and AS 64999 and from the IBGP neighbor. Both routers selected the
path to the 172.31.2.0/24 network through BBR1 and to the 172.31.22.0/24 network through
BBR2 according to the shortest AS path criteria. The printouts show the information about
prefixes 172.31.2.0/24 and 172.31.22.0/24 on routers R1 and R2.
internal

* 172.31.2.0/24 172.31.11.4 0 64999 64998
i
* i 172.31.1.3 0 100 0 64998 i
*> 172.31.1.3 0 0 64998 i

internal

* i172.31.22.0/24 172.31.11.4 0 100 0 64999 i
* 172.31.1.3 0 64998 64999
i
*> 172.31.11.4 0 0 64999 i
Printout 157: BGP information for 172.31.2.0/24 and 172.31.22.0/24 networks on
R1 router
internal

* 172.31.2.0/24 172.31.11.4 0 64999 64998
i
*> 172.31.1.3 0 0 64998 i
* i 172.31.1.3 0 100 0 64998 i

internal

* i172.31.22.0/24 172.31.11.4 0 100 0 64999 i
* 172.31.1.3 0 64998 64999
i
*> 172.31.11.4 0 0 64999 i
R2 router
Task 2: Using Local Preference with Route Maps for BGP Path
Manipulation
Your company has established a policy requiring that all traffic exiting your AS, bound for the
remote networks 172.31.2.0/24 and 172.31.22.0/24, should take the path through AS 64999.
Step 6 On R1 and R2 edge routers, configure a route map to set the local preference to 300 for the
networks 172.31.2.0/24 and 172.31.22.0/24. Create an access list to match those networks.
Step 7 Apply the configured route map to the incoming updates from the BBR2 router on R1 and R2
edge routers.
Verification
Step 8 Check the BGP information for 172.31.2.0/24 and 172.31.22.0/24 networks at the R1 and R2
edge routers. Notice that the local preference has not changed. The printouts show the
information about prefixes 172.31.2.0/24 and 172.31.22.0/24 on routers R1 and R2.
internal

* 172.31.2.0/24 172.31.11.4 0 64999 64998
i
* i 172.31.1.3 0 100 0 64998 i
*> 172.31.1.3 0 0 64998 i

internal

* i172.31.22.0/24 172.31.11.4 0 100 0 64999 i
* 172.31.1.3 0 64998 64999
i
*> 172.31.11.4 0 0 64999 i
R1 router
internal

* 172.31.2.0/24 172.31.11.4 0 64999 64998
i
*> 172.31.1.3 0 0 64998 i
* i 172.31.1.3 0 100 0 64998 i

internal

* i172.31.22.0/24 172.31.11.4 0 100 0 64999 i
* 172.31.1.3 0 64998 64999
i
*> 172.31.11.4 0 0 64999 i
R2 router
Step 9 When a BGP policy is changed, it is not automatically applied to the routes already in the BGP
table. To apply the changed policy, you have to either reset the BGP relationship with the BBR2,
or convince the router to apply the policy to existing routes without resetting the relationship by
using the BGP route refresh functionality. Use route refresh to apply the policy to the routes
learned from the BBR2 router with the clear ip bgp 172.31.11.4 soft in command on both edge
routers, and re-examine the BGP information for 172.31.2.0/24 and 172.31.22.0/24 networks.
The printouts show the information about prefixes 172.31.2.0/24 and 172.31.22.0/24 on routers
R1 and R2.
internal

* i172.31.2.0/24 172.31.11.4 300 0 64999 64998
i
*> 172.31.11.4 300 0 64999 64998
i
* 172.31.1.3 0 0 64998 i

internal

* i172.31.22.0/24 172.31.11.4 0 300 0 64999 i
* 172.31.1.3 0 64998 64999
i
*> 172.31.11.4 0 300 0 64999 i
R1 router
internal

*> 172.31.2.0/24 172.31.11.4 300 0 64999 64998
i
* 172.31.1.3 0 0 64998 i
* i 172.31.11.4 300 0 64999 64998
i

internal

* i172.31.22.0/24 172.31.11.4 0 300 0 64999 i
* 172.31.1.3 0 64998 64999
i
*> 172.31.11.4 0 300 0 64999 i
R2 router
The local preference is now changed and the path through AS 64999 is preferred to reach
networks 172.31.2.0/24 and 172.31.22.0/24.
Step 10 Verify the path of the traffic to 172.31.2.2 and 172.31.22.22 from R3 router with the traceroute
command.


1 10.1.1.1 0 msec 0 msec 4 msec
2 172.31.11.4 [AS 64999] 28 msec 28 msec 28 msec
3 10.254.0.1 [AS 64997] 40 msec * 36 msec



1 10.1.1.1 0 msec 4 msec 0 msec
2 172.31.11.4 [AS 64999] 28 msec * 28 msec
Printout 163: Traceroute from R3 to 172.31.2.2 and 173.31.22.22
Step 11 Telnet to BBR1 and BBR2 routers and examine the BGP information for the 10.1.0.0/16 prefix
with the show ip bgp 10.1.0.0/16 longer-prefixes command. Each router has multiple ways into
your network, the direct path through your edge routers or the path through the other AS and
then to the edge routers. The selection of the best path is based on the oldest EBGP path criteria.
Note In the printout below, the routers have chosen the path through the R1 router into the AS. In
your case, the preferred way into the AS could be the R2 router.
BBR1#show ip bgp 10.1.0.0/16 longer-prefixes
internal

* 10.1.0.0/16 10.254.0.2 0 64999 65001
i
* 172.31.1.2 0 65001 i
*> 172.31.1.1 0 65001 i
Printout 164: BGP information for 10.1.0.0/16 prefix on BBR1 router
internal

* 10.1.0.0/16 172.31.11.2 0 65001 i
* 10.254.0.1 0 64998 65001
i
*> 172.31.11.1 0 65001 i
Printout 165: BGP information for 10.1.0.0/16 prefix on BBR2 router
Task 3: Using MED with Route Maps for BGP Path Manipulation
You want to assure that the traffic destined to your networks summarized by the 10.1.0.0/16
prefix from the AS 64998 enters the AS through the R1 edge router and from the AS 64999
through the R2 edge router. To meet the required policy, the paths through R1 must appear
unattractive to BBR2, and paths through R2 must appear unattractive to BBR1 router. You will
achieve that by adjusting the MED attribute.
Step 12 Configure a route map at the R1 router to set the MED to 200 for the 10.1.0.0/16 summary
prefix. Apply the route map to the updates sent to the BBR2 router.
Step 13 Configure a route map at the R2 router to set the MED to 200 for the 10.1.0.0/16 summary
prefix. Apply the route map to the updates sent to the BBR1 router.
Verification
Step 14 Perform the soft reconfiguration for the BBR1 BGP neighbor at the R2 edge router to apply the
configured policy with the clear ip bgp 172.31.1.3 soft out command.
Step 15 Perform the soft reconfiguration for the BBR2 BGP neighbor at the R1 edge router to apply the
configured policy with the clear ip bgp 172.31.11.4 soft out command.
Step 16 Telnet to the BBR1 router and examine the BGP information for 10.1.0.0/16 prefix with show ip
bgp 10.1.0.0/16 longer-prefixes command. Notice that the MED value has changed to 200 for
the 10.1.0.0/16 prefix received from the R2 edge router, which makes R1 preferred over R2.
internal

* 10.1.0.0/16 10.254.0.2 0 64999 65001
i
* 172.31.1.2 200 0 65001 i
*> 172.31.1.1 0 65001 i
R1 router
Step 17 Telnet to the BBR2 router and examine the BGP information for 10.1.0.0/16 prefix with the
show ip bgp 10.1.0.0/16 longer-prefixes command. The MED value has changed to 200 for the
10.1.0.0/16 prefix received from the R1 edge router, which makes the path through R2 better.
internal

*> 10.1.0.0/16 172.31.11.2 0 65001 i
* 10.254.0.1 0 64998 65001
i
* 172.31.11.1 200 0 65001 i
R2 router
Lab Topology
routers (BBR1, BBR2 and BBR3) in the figure are accessible via telnet only.

BBR1, BBR2, BBR3 Routers that are part of an external routing domains
R1, R2 Edge routers
BBR1 236 172.31.1.3 R1 263 172.31.1.1
BBR1 331 172.31.1.3 R2 313 172.31.1.2
BBR2 212 172.31.11.4 R1 221 172.31.11.1
BBR2 211 172.31.11.4 R2 211 172.31.11.2
BBR3 103 10.254.0.3 R1 130 10.254.0.1
BBR3 102 10.254.0.3 R2 120 10.254.0.2
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
Note IP addressing and BGP routing have been pre-configured to allow you to focus exclusively on
Parameter Value
External WAN subnet 10.254.0.0/24
BBR1 loopback interface 172.31.2.0/24

Existing BGP and RIP Routing
BGP routing protocol is used as routing protocol between 64997, 64998, 64999 and 65001 AS
numbers as shown in the following figure.

Figure 32: Existing BGP routing
BBR3 is configured with AS path filter to prevent the AS 64997 from becoming the transit AS.
Similarly, R1 and R2 routers are configured with AS path filters to prevent the AS 65001 from
becoming the transit AS. The transit AS filtering in this lab exercise is used to ensure consistent
printouts on your lab routers.
RIP routing protocol is used as an IGP routing protocol between R1, R3, R2, R4 and R3, R4
routers. RIP is disabled between R1 and R2 routers.
The existing routing configuration on BBR1, BBR2, BBR3, R1, R2, R3 and R4 routers is shown
below:
router bgp 64998
network 172.31.1.0 mask 255.255.255.0
network 172.31.2.0 mask 255.255.255.0
router bgp 64999
network 172.31.11.0 mask 255.255.255.0
network 172.31.22.0 mask 255.255.255.0
router bgp 64997
network 10.97.97.0 mask 255.255.255.0
network 10.254.0.0 mask 255.255.255.0
neighbor 10.254.0.1 route-map TRANSIT out
!
ip as-path access-list 1 permit ^$
!
route-map TRANSIT permit 10
match as-path 1
router rip
version 2
no auto-summary
network 10.0.0.0
!
router bgp 65001
no synchronization
network 10.1.0.0 mask 255.255.255.0
network 10.1.1.0 mask 255.255.255.0
network 10.1.2.0 mask 255.255.255.0
network 10.1.3.0 mask 255.255.255.0
!
!
match as-path 1
Printout 171: RIP and BGP routing on R1 router
router rip
version 2
no auto-summary
network 10.0.0.0
!
router bgp 65001
no synchronization
network 10.1.0.0 mask 255.255.255.0
network 10.1.1.0 mask 255.255.255.0
network 10.1.2.0 mask 255.255.255.0
network 10.1.3.0 mask 255.255.255.0
!
!
match as-path 1
router rip
version 2
no auto-summary
network 10.0.0.0
!
router bgp 65001
no synchronization
network 10.200.200.13 mask 255.255.255.255
router rip
version 2
no auto-summary
network 10.0.0.0
!
router bgp 65001
no synchronization
network 10.200.200.14 mask 255.255.255.255

Copyright 2006, NIL Data Communications Scaling BGP Lab Solutions 159
BSCI
Scaling BGP
Lab Solutions
Lab Solution
Task 1: Configuring BGP Route Summarization and Examining
BGP Path Selection Process
router bgp 65001
aggregate-address 10.1.0.0 255.255.0.0 summary-only
Configuration 55: BGP route summarization on R1 and R2 routers
Task 2: Using Local Preference with Route Maps for BGP Path
Manipulation
router bgp 65001
neighbor 172.31.11.4 route-map SET_PREF in
!
!
route-map SET_PREF permit 10
match ip address 10
set local-preference 300
!
route-map SET_PREF permit 20
Configuration 56: BGP local preference configuration on R1 and R2 routers

160 Scaling BGP Lab Solutions Copyright 2006, NIL Data Communications
Task 3: Using MED with Route Maps for BGP Path Manipulation
router bgp 65001
neighbor 172.31.11.4 route-map SET_MED_HI out
!
!
route-map SET_MED_HI permit 10
match ip address 11
set metric 200
!
Configuration 57: BGP MED configuration on R1 router
router bgp 65001
neighbor 172.31.1.3 route-map SET_MED_HI out
!
!
match ip address 11
set metric 200
!
Configuration 58: BGP MED configuration on R2 router

Copyright 2006, NIL Data Communications Configuring Multicast Routing 161
BSCI
Configuring Multicast Routing
Objective
In this exercise, you will implement multicast routing by enabling the PIM Sparse-Dense mode
on selected interfaces. You will observe the PIM operation and enable a router to join a multicast
group by configuring IGMP and finally configure the auto Rendezvous Point (RP) and mapping
agent on the selected router:
Configure and examine the IP Multicast and PIM Sparse-Dense mode over Frame Relay
point-to-point and Ethernet interfaces
Configure and examine the IGMP on a selected router
Configure and examine the auto-RP and mapping agent functionality for certain multicast
groups
Figure 33 shows the logical topology used for this lab.

Figure 33: Configuring Multicast Routing Lab exercise logical topology
162 Configuring Multicast Routing Copyright 2006, NIL Data Communications
Command List
Command Task
access-list number permit ip-address Configures an access list permiting specified
IP address or network.
ip igmp join-group group Configures router to join the specified
multicast group on a selected interface
router becomes receiver for that multicast
group traffic.
ip multicast-routing Globally enables multicast routing.
ip pim send-rp-announce interface scope
ttl-scope group-list list
Configures router to send announcements of
beeing a candidate RP for the multicast
groups specified by the access list using the
specified interface as a source and limited to
the TTL scope.
ip pim send-rp-discovery interface scope
ttl-scope
Configures a router to be a mapping agent
using the specified source interface limited to
TTL scope.
ip pim sparse-dense-mode Enables PIM sparse-dense mode per
interface.
show ip igmp groups Displays the multicast groups with receivers
that are directly connected to the router and
that were learned through Internet Group
Management Protocol (IGMP).
show ip igmp interface Displays the multicast-related information
about an interface.
show ip mroute Displays the content of the IP multicast
routing table.
show ip pim interface Displays information about interfaces
configured for PIM.
show ip pim neighbor Lists the discovered PIM neighbors.
show ip pim rp Displays the active rendezvous points (RPs)
that are cached with associated multicast
routing entries.
show ip pim rp mapping Displays the detailed information about active
RPs that are cached with associated
multicast routing entries.
Multicast Routing Lab exercise
Task 1: Enabling IP Multicast and PIM Sparse-Dense Mode
Step 1 Enable IP multicast routing on routers R1, R2, R3, and R4.
Step 2 Enable PIM Sparse-Dense mode on Frame Relay subinterfaces, Ethernet and Loopback
interfaces on routers R1, R2, R3, and R4.
Note The routers in different lab pods may support only Ethernet or only FastEthernet interfaces.
The printouts in the lab guide and your lab exercise might though differ.
Verification
Step 3 Begin the verification by checking the PIM enabled interfaces on R1, R2, R3, and R4 routers.
Note that by default PIM version 2 is used and that you can also see the number of PIM
neighbors, PIM mode, and Designated Router (DR) for each PIM enabled interface.
R1#show ip pim interface

Address Interface Ver/ Nbr Query DR DR
Mode Count Intvl Prior
10.1.1.1 FastEthernet0/0 v2/SD 1 30 1
10.1.1.3
10.1.0.1 Serial0/0.1 v2/SD 1 30 1 0.0.0.0
172.31.1.1 Serial0/0.2 v2/SD 0 30 1 0.0.0.0
10.200.200.11 Loopback0 v2/SD 0 30 1
10.200.200.11
Printout 175: PIM interface information on R1 router

10.1.2.4
10.1.0.2 Serial0/0.1 v2/SD 1 30 1
0.0.0.0
10.200.200.12 Loopback0 v2/SD 0 30 1
10.200.200.12

10.1.1.3
10.1.3.3 Serial0/0.1 v2/SD 1 30 1
0.0.0.0
10.200.200.13 Loopback0 v2/SD 0 30 1
10.200.200.13

10.1.2.4
10.1.3.4 Serial0/0.1 v2/SD 1 30 1
0.0.0.0
10.200.200.14 Loopback0 v2/SD 0 30 1
10.200.200.14
Step 4 Next, examine the established PIM neighborship on routers R1, R2, R3, and R4. Each router
should have formed the PIM neighorship with neighboring router except over Loopback
interfaces. Also, R1 did not establish neighborship over Serial0/0.2 since there is no device with
PIM configured.
R1#show ip pim neighbor
PIM Neighbor Table
Neighbor Interface Uptime/Expires Ver DR
Address
Prio/Mode
10.1.1.3 FastEthernet0/0 00:15:24/00:01:22 v2 1 / DR
B S
10.1.0.2 Serial0/0.1 00:16:11/00:01:34 v2 1 / B
S
Printout 179: PIM neighborship information on R1 router
PIM Neighbor Table
Address
Prio/Mode
10.1.2.4 FastEthernet0/0 00:18:32/00:01:43 v2 1 / DR
B S
10.1.0.1 Serial0/0.1 00:20:34/00:01:40 v2 1 / B
S
PIM Neighbor Table
Address
Prio/Mode
10.1.1.1 FastEthernet0/0 00:20:13/00:01:31 v2 1 / B
S
10.1.3.4 Serial0/0.1 00:19:00/00:01:16 v2 1 / B
S
PIM Neighbor Table
Address
Prio/Mode
10.1.2.2 FastEthernet0/0 00:19:19/00:01:26 v2 1 / B
S
10.1.3.3 Serial0/0.1 00:19:18/00:01:26 v2 1 / B
S
Step 5 Take a look at the multicast routing table on routers R1, R2, R3, and R4. You should notice a
single (*, G) entry only for 224.0.1.40. The 224.0.1.40 is a RP discovery group to which all PIM
enabled routers automatically join to receive all group-to-RP mapping information, which is
distributed by the RP mapping agent. The output on your routers should be similar to the
following output taken from router R1.
R1#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP
Advertisement,
U - URD, I - Received Source Specific Host Report
Outgoing interface flags: H - Hardware switched
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.0.1.40), 00:12:00/00:00:00, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.1, Forward/Sparse-Dense, 00:12:00/00:00:00
FastEthernet0/0, Forward/Sparse-Dense, 00:12:00/00:00:00
Printout 183: Multicast routing table on R1 router
Step 6 Try pinging 224.1.1.1 and 224.2.2.2 from BBR1 router. The ping should not succeed since there
are no receivers for those groups in your network.
BBR1#ping 224.1.1.1

.
BBR1#ping 224.2.2.2

.
Printout 184: Ping 224.1.1.1 and 224.2.2.2 from BBR1 router
Step 7 Examine the multicast routing table on R1 router immediately after pinging from BBR1 router.
Notice that the (*, G) and (S, G) entries for the 224.1.1.1 and 224.2.2.2 appear and later age out
after the expiration time (3 minutes). Mind that since no RP is configured in the network the PIM
dense mode is used for the 224.1.1.1 and 224.2.2.2 groups.
R1#show ip mroute
Connected,
Advertisement,

(*, 224.0.1.40), 00:45:00/00:00:00, RP 0.0.0.0, flags: DCL

(*, 224.1.1.1), 00:00:40/00:02:59, RP 0.0.0.0, flags: D

(172.31.1.3, 224.1.1.1), 00:00:41/00:02:18, flags: PT
Incoming interface: Serial0/0.2, RPF nbr 0.0.0.0
FastEthernet0/0, Prune/Sparse-Dense, 00:00:35/00:02:24
Serial0/0.1, Prune/Sparse-Dense, 00:00:36/00:02:23

(*, 224.2.2.2), 00:00:36/00:02:59, RP 0.0.0.0, flags: D

(172.31.1.3, 224.2.2.2), 00:00:36/00:02:23, flags: PT
Task 2: Configuring IGMP
Step 8 Configure IGMP on the Fa0/0 interface of router R4 to join the multicast groups 224.1.1.1 and
224.2.2.2.
Verification
Step 9 Examine the IGMP group and interface information on router R4. You should notice in the
IGMP group membership information that apart from 224.1.1.1 and 224.2.2.2 groups also the
224.0.1.40 is present. In the IGMP interface information, you should notice that by default IGMP
version 2 is enabled and that router R4 joined the multicast groups on Fa0/0 interface.
R4#show ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last
Reporter
224.0.1.40 FastEthernet0/0 00:59:00 00:02:30 10.1.2.2
224.0.1.40 Loopback0 00:59:08 00:02:20
10.200.200.14
224.1.1.1 FastEthernet0/0 00:08:52 00:02:30 10.1.2.4
224.2.2.2 FastEthernet0/0 00:08:46 00:02:25 10.1.2.4
Printout 186: IGMP group information on router R4
R4#show ip igmp interface
Internet address is 10.1.2.4 255.255.255.0
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 5 joins, 2 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 10.1.2.4 (this system)
IGMP querying router is 10.1.2.2
Multicast groups joined (number of users):
224.1.1.1(1) 224.2.2.2(1)
Serial0/0 is up, line protocol is up
Internet protocol processing disabled
Internet address is 10.1.3.4 255.255.255.0
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 0 joins, 0 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
IGMP querying router is 0.0.0.0 (this system)
No multicast groups joined
<... part of output omitted ...>
Printout 187: IGMP interface information on R4 router
Step 10 Try pinging 224.1.1.1 and 224.2.2.2 from BBR1 router again. The ping should now succeed since
the R4 router is configured as IGMP receiver for groups 224.1.1.1 and 224.2.2.2.
BBR1#ping 224.1.1.1


Reply to request 0 from 10.1.3.4, 228 ms
BBR1#ping 224.2.2.2


Reply to request 0 from 10.1.3.4, 212 ms
Printout 188: Ping 224.1.1.1 and 224.2.2.2 from BBR1 router
Task 3: Deploying Auto-RP Functionality
Step 11 Configure router R1 to announce itself as being available to be the RP for group 224.1.1.1 only.
Router R1 should use Loopback interface for that purpose and should limit the scope to 3.
Step 12 Next, configure router R1 to send RP-to-group mappings for other routers to dynamically
discover the RPthe router R1 should be the RP mapping agent, and should use Loopback
interface and limit the scope to 3 for that purpose.
Verification
Step 13 Examine the multicast routing table on R1 router. Notice the new (*, G) and (S, G) entries for the
224.0.1.39 group. The 224.0.1.39 group is RP announce group to which RP mapping agents join
to receive the candidate RPs periodic multicast advertisments. In the lab exercise, the router R1
(thus the (10.200.200.11, 224.0.1.39) entry) periodically announces itself to be the candidate RP
for the group 224.1.1.1. Since R1 is also the mapping agent, R1 also advertises to other PIM
routers the availability of RP.
Notice also that for the 224.1.1.1 the PIM sparse mode is used now since the RP is known.
R1#show ip mroute
Connected,
Advertisement,

(*, 224.0.1.39), 00:11:52/00:00:00, RP 0.0.0.0, flags: DCL
Loopback0, Forward/Sparse-Dense, 00:11:37/00:00:00

(10.200.200.11, 224.0.1.39), 00:11:52/00:02:36, flags: CLT
Incoming interface: Loopback0, RPF nbr 0.0.0.0

(*, 224.0.1.40), 02:20:55/00:00:00, RP 0.0.0.0, flags: DCL

(10.200.200.11, 224.0.1.40), 00:10:54/00:02:32, flags: CLT

(*, 224.1.1.1), 00:10:54/00:02:30, RP 10.200.200.11, flags: S
Step 14 Also, check the multicast routing tables on R2, R3, and R4 routers. Just like on R1 router, you
should notice the (*, G) and (S, G) for the group 224.0.1.39 with R1 being the source
(10.200.200.11). On R2 and R4 routers you should also see the entry for the 224.2.2.2 group
since the receiver for the group is located in the connected Ethernet segment.
R2#show ip mroute
Connected,
Advertisement,

(*, 224.0.1.39), 00:19:05/00:02:59, RP 0.0.0.0, flags: D

(10.200.200.11, 224.0.1.39), 00:00:05/00:02:54, flags: PT

(*, 224.0.1.40), 01:45:38/00:00:00, RP 0.0.0.0, flags: DCL

(10.200.200.11, 224.0.1.40), 00:18:07/00:02:48, flags: CLT

(*, 224.1.1.1), 00:45:32/00:02:25, RP 10.200.200.11, flags: SJP
Outgoing interface list: Null

(*, 224.2.2.2), 00:45:27/00:02:33, RP 0.0.0.0, flags: DC
R3#show ip mroute
Connected,
Advertisement,

(*, 224.0.1.39), 00:19:56/00:02:59, RP 0.0.0.0, flags: DC

(10.200.200.11, 224.0.1.39), 00:00:57/00:02:02, flags: PCT
Incoming interface: FastEthernet0/0, RPF nbr 10.1.1.1

(*, 224.0.1.40), 02:28:48/00:00:00, RP 0.0.0.0, flags: DCL

(10.200.200.11, 224.0.1.40), 00:18:58/00:03:26, flags: CLT

(*, 224.1.1.1), 00:18:58/00:03:26, RP 10.200.200.11, flags: S
R4#show ip mroute
Connected,
Advertisement,

(*, 224.0.1.39), 00:20:33/00:02:59, RP 0.0.0.0, flags: D

(10.200.200.11, 224.0.1.39), 00:01:33/00:01:26, flags: PT

(*, 224.0.1.40), 01:47:11/00:00:00, RP 0.0.0.0, flags: DCL

(10.200.200.11, 224.0.1.40), 00:19:35/00:02:19, flags: CLT
FastEthernet0/0, Forward/Sparse-Dense, 00:03:40/now

(*, 224.1.1.1), 00:47:01/00:00:00, RP 10.200.200.11, flags: SJCL

(*, 224.2.2.2), 00:46:55/00:00:00, RP 0.0.0.0, flags: DCL
Step 15 Examine the RP information on R1, R2, R3, and R4 routers. You should see that R1 being the
mapping agent is announcing itself with the Loopback IP address. On routers R2, R3, and R4 you
should see that they learned that R1 is the RP for the group 224.1.1.1.
R1#show ip pim rp
Group: 224.1.1.1, RP: 10.200.200.11, v2, v1, next RP-reachable in
00:00:45
Printout 193: PIM RP information on R1 router
R1#show ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent (Loopback0)

Group(s) 224.1.1.1/32
RP 10.200.200.11 (?), v2v1
Info source: 10.200.200.11 (?), elected via Auto-RP
Uptime: 00:31:20, expires: 00:02:37
Printout 194: Detailed PIM RP information on R1 router
R2#show ip pim rp
Group: 224.1.1.1, RP: 10.200.200.11, v2, v1, uptime 00:21:03, expires
00:04:26
Printout 195: PIM RP information on R2 router (should be similar on R3 and R4
routers)
R4#show ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.1.1.1/32
RP 10.200.200.11 (?), v2v1
Info source: 10.200.200.11 (?), elected via Auto-RP
Uptime: 00:32:31, expires: 00:02:10
Printout 196: Detailed PIM RP information on R4 router (should be similar on R2
and R3 routers)
Step 16 Issue another ping to 224.1.1.1 from BBR1 router and re-examine the multicast routing table on
R1 router. The ping should succeed and in the R1s multicast routing table a new (S, G) entry
should appear where S equals to 172.31.1.3 and G equals to 224.1.1.1.
R1#show ip mroute
Connected,
Advertisement,

(*, 224.0.1.39), 00:36:08/00:00:00, RP 0.0.0.0, flags: DCL

(10.200.200.11, 224.0.1.39), 00:36:08/00:03:21, flags: CLT

(*, 224.0.1.40), 02:45:10/00:00:00, RP 0.0.0.0, flags: DCL

(10.200.200.11, 224.0.1.40), 00:35:09/00:03:05, flags: CLT

(*, 224.1.1.1), 00:35:09/00:03:04, RP 10.200.200.11, flags: S

(172.31.1.3, 224.1.1.1), 00:01:09/00:01:50, flags: T
Lab Topology

BBR1 Core router
R1, R2 Edge routers
The routers are connected with Ethernet and Frame Relay linksthe first serial interface of each
BBR1 236 172.31.1.3 R1 263 172.31.1.1
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
Parameter Value

Figure 35: Addressing of lab exercise routers
Existing EIGRP Routing
EIGRP routing protocol is used as a routing protocol. The existing EIGRP routing configuration
on routers is shown below:
router eigrp 1
network 172.31.0.0
no auto-summary
!
ip route 0.0.0.0 0.0.0.0 172.31.1.1
Printout 198: EIGRP and default routing on BBR1 router
router eigrp 1
network 172.31.0.0
network 10.0.0.0
no auto-summary
Printout 199: EIGRP routing on R1 router
router eigrp 1
network 10.0.0.0
no auto-summary
Printout 200: EIGRP routing on R2, R3 and R4 routers

Copyright 2006, NIL Data Communications Configuring Multicast Routing Lab Solutions 175
BSCI
Configuring Multicast Routing
Lab Solutions
Lab Solution
Task 1: Enabling IP Multicast and PIM Sparse-Dense Mode
ip multicast-routing
!
interface Loopback0
ip pim sparse-dense-mode
!
!
!
Configuration 59: IP Multicast and PIM Sparse-Dense configuration on R1 router
!
interface Loopback0
!
!
Configuration 60: IP Multicast and PIM Sparse-Dense configuration on R2 router

176 Configuring Multicast Routing Lab Solutions Copyright 2006, NIL Data Communications
!
interface Loopback0
!
!
Configuration 61: IP Multicast and PIM Sparse-Dense configuration on R3 and
R4 routers
Task 2: Configuring IGMP
ip igmp join-group 224.1.1.1
ip igmp join-group 224.2.2.2
Configuration 62: IGMP configuration on R4 router
Task 3: Deploying Auto-RP Functionality
ip pim send-rp-announce Loopback0 scope 3 group-list 1
ip pim send-rp-discovery Loopback0 scope 3
!
access-list 1 permit 224.1.1.1
Configuration 63: PIM RP and mapping agent configuration on R1 router

Copyright 2006, NIL Data Communications Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel 177

BSCI
Configuring IPv6 Addressing,
OSPFv3 Routing, and IPv6
Tunnel
Objective
In this exercise you will deploy IPv6 in your network. First, you will enable IPv6 processing on
your routers and assign the IPv6 addresses. Next, you will implement OSPFv3 routing in your
IPv6 domain to interconnect the IPv6 LAN segments and to provide end-to-end connectivity.

Figure 36: OSPFv3 deployment
Finally, you will enhance your IPv6 network by providing the additional connectivity via IPv4
network using the IPv6 tunnel. You will include the IPv6 tunnel into the OSPFv3.
178 Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel Copyright 2006, NIL Data Communications

Figure 37: Implementing IPv6 tunnel
Enable IPv6 functionality on your routers
Assign IPv6 addresses to the specified interfaces
Deploy OSPFv3 routing in the IPv6 network
Implement IPv6 tunnel over IPv4 network
Explore IPv6 routing and verify the connectivity in the IPv6 network
Command List
Command Task
bandwidth bw Sets the bandwidth in kbps on a selected interface.
clear counters interface Clears counters on the specified interface.
interface interface-ID Creates the specified interface (for example,
Tunnel0).
ipv6 address ipv6-prefix eui-64 Configures an IPv6 address on an interface with the
lower 64 bits of the address derived from the
interface ID.
ipv6 cef Enables IPv6 CEF switching on a router.
ipv6 ospf process-ID area area-ID Enables OSPFv3 process with the specified process
ID and in the specified OSPFv3 area on a selected
interface.
ipv6 router ospf process-ID Configures OSPFv3 process globally with the
specified process-ID and enters the OSPFv3
process configuration mode.
ipv6 unicast-routing Enables the IPv6 unicast routing on a router.
router-id ip-address Sets the router-ID for the OSPF process under the
OSPF configuration mode.
show cdp neighbors interface detail Shows the detailed CDP information for the neighbor
via the selected interface, which also includes one
network address per network layer protocol.
show ipv6 interface Displays the IPv6 interface information.
show ipv6 interface brief Displays the IPv6 interface information in a brief
form.
show ipv6 ospf interface Displays the IPv6 OSPF interface information.
show ipv6 ospf neighbor Displays the IPv6 OSPF neighbor list and
information.
show ipv6 route Displays the IPv6 routing table.
tunnel destination ip-address Sets the tunnel destination IPv4 address.
tunnel mode ipv6ip Sets the tunnel mode to IPv6 manual tunnel.
tunnel source interface/ip-address Sets the tunnel source interface or IPv4 address.
Table 2: Configuration and monitoring commands used in the Configuring IPv6
Addressing, OSPFv3 Routing, and IPv6 Tunnel Lab exercise
Task 1: Configuring IPv6 Addressing
In this task, you will enable IPv6 and configure IPv6 addressing using IPv6 global addresses.
Step 1 Enable IPv6 unicast routing and IPv6 CEF switching on routers R1, R2, R3, and R4.
Step 2 Configure IPv6 addresses on the Ethernet segment between R1 and R3 routers. Use the
2001:0410:0001:13::/64 for the IPv6 prefix. The lower 64 bits of the IPv6 address should be
derived from the interface ID.
Step 3 Configure IPv6 addresses on the Frame Relay segment between R1 and R2 routers. Use the
Step 4 Configure IPv6 addresses on the Ethernet segment between R2 and R4 routers. Use the
Note The routers in different lab pods may support only Ethernet or only FastEthernet interfaces.
Therefore the printouts in your lab exercise may differ from the printouts present in this lab
exercise guide.

Note The IPv6 global and link-local address in your lab exercise might differ from the IPv6
addresses shown in the printouts since the interface ID part of the addresses differ.
Verification
Step 5 Verify the IPv6 addressing configuration by examining the IPv6 interface information on routers
R1, R2, R3, and R4. You can see the IPv6 global unicast address as well as IPv6 link-local
address assigned per segment.
R1#show ipv6 interface
IPv6 is enabled, link-local address is FE80::206:53FF:FEBA:F640
Description: Link to R3
Global unicast address(es):
2001:410:1:13:206:53FF:FEBA:F640, subnet is 2001:410:1:13::/64
Joined group address(es):
FF02::1
FF02::2
FF02::1:FFBA:F640
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
Hosts use stateless autoconfig for addresses.
FF02::1
FF02::2
FF02::1:FFBA:F640
MTU is 1500 bytes
Printout 201: IPv6 interface information on R1 router
IPv6 is enabled, link-local address is FE80::206:53FF:FE03:9C40
2001:410:1:24:206:53FF:FE03:9C40, subnet is 2001:410:1:24::/64
FF02::1
FF02::2
FF02::1:FF03:9C40
MTU is 1500 bytes
IPv6 is enabled, link-local address is FE80::206:53FF:FE03:9C40
2001:410:1:12:206:53FF:FE03:9C40, subnet is 2001:410:1:12::/64
FF02::1
FF02::2
FF02::1:FF03:9C40
MTU is 1500 bytes
FF02::1
FF02::2
FF02::1:FFBA:F700
MTU is 1500 bytes
IPv6 is enabled, link-local address is FE80::206:53FF:FEC7:D100
2001:410:1:24:206:53FF:FEC7:D100, subnet is 2001:410:1:24::/64
FF02::1
FF02::2
FF02::1:FFC7:D100
MTU is 1500 bytes
Step 6 Test the IPv6 connectivity between neighboring routers using the ping command. To make this
verification part easier obtain the complete IPv6 addresses of all the routers in the network and
write them into Table 39.
Router Interface IPv6 address
R1 S0/0.1
R2 S0/0.1
R2 Fe0/0
R3 S0/0.1
R4 S0/0.1
R4 Fe0/0
Table 39: IPv6 addresses
You can use the show cdp neighbor detail command to obtain the IPv6 addresses of the
neighbors or show ipv6 interface brief command to obtain the IPv6 addresses on a selected
router.
R1#show ipv6 interface brief
FastEthernet0/0 [up/up]
FE80::206:53FF:FEBA:F640
2001:410:1:13:206:53FF:FEBA:F640
FastEthernet0/0.727 [up/up]
unassigned
Serial0/0 [up/up]
unassigned
Serial0/0.1 [up/up]
FE80::206:53FF:FEBA:F640
2001:410:1:12:206:53FF:FEBA:F640
<...rest of the output omitted...>
Printout 205: IPv6 interface list on R1 router
Step 7 For example, in the detailed CDP information on router R1 for the Serial0/0.1 interface you can
see the global IPv6 addresses derived from the assigned IPv6 global prefix and interface ID, and
the link-local IPv6 address derived from the FE80::/64 prefix and interface ID.
R1#show cdp neighbors serial 0/0.1 detail
-------------------------
Device ID: R2
Entry address(es):
IP address: 10.1.0.2
IPv6 address: FE80::206:53FF:FE03:9C40 (link-local)
IPv6 address: 2001:410:1:12:206:53FF:FE03:9C40 (global unicast)
Platform: cisco 2621, Capabilities: Router Switch
Interface: Serial0/0.1, Port ID (outgoing port): Serial0/0.1
Holdtime : 130 sec
<...rest of the output omitted...>
Printout 206: CDP detailed neighbor information on R1 router
Notice that pinging to not directly connected prefixes does not succeed because there is no IPv6
enabled routing protocol currently deployed.
R1#ping ipv6 2001:410:1:13:206:53FF:FEBA:F700

Sending 5, 100-byte ICMP Echos to 2001:410:1:13:206:53FF:FEBA:F700,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

!!!!!
R1#ping ipv6 2001:410:1:24:206:53FF:FE03:9C40

Sending 5, 100-byte ICMP Echos to 2001:410:1:24:206:53FF:FE03:9C40,
.....
Printout 207: IPv6 ping from R1 to R3 Fe0/0, R2 S0/0.1, and R2 Fe0/0

.....

!!!!!
R2#ping ipv6 2001:410:1:24:206:53FF:FEC7:D100

Sending 5, 100-byte ICMP Echos to 2001:410:1:24:206:53FF:FEC7:D100,
!!!!!
Printout 208: IPv6 ping from R2 to R1 Fe0/0, R1 S0/0.1, and R4 Fe0/0
Step 8 Examine the IPv6 routing table on R1 router. You should notice:
IPv6 prefixes denoted with C, which are connected global IPv6 networks
IPv6 addresses denoted with L, which are local per interface assigned IPv6 addresses
FE80::/10 prefix pointing to null interface, which is used for automatically assigned link-
local IPv6 addresses
FF00::/8 pointing to null interface, which is used for IPv6 multicast addresses
R1#show ipv6 route
IPv6 Routing Table - 6 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext
2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
C 2001:410:1:12::/64 [0/0]
via ::, Serial0/0.1
L 2001:410:1:12:206:53FF:FEBA:F640/128 [0/0]
via ::, Serial0/0.1
C 2001:410:1:13::/64 [0/0]
via ::, FastEthernet0/0
L 2001:410:1:13:206:53FF:FEBA:F640/128 [0/0]
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Printout 209: IPv6 routing table on R1
Task 2: Configuring OSPFv3 Single Area Routing
In this task you will configure OSPFv3 routing in the IPv6 network to enable end-to-end
connectivity in the IPv6 network network.
Step 9 Enable OSPFv3 globally on each router in the network. Set the OSPF router ID and use the
Loopback0 interface for that purpose.
Step 10 Configure OSPFv3 in Area 0 on each router in the network on the interfaces configured with
IPv6 addresses. Use 1 for the process ID.
Verification
Step 11 Examine the OSPFv3 interface information on routers to confirm that OSPFv3 is enabled on
proper interfaces. You can see the OSPFv3 network type, which is the same as in OSPFv2. The
output also show you the number of OSPFv3 neighbours via certain interface and the
neighboring routers router ID. On the Ethernet segmentthe BROADCAST network type
you can also see the elected DR and BDR for that segment along with their link-local addresses.
R1#show ipv6 ospf interface
Link Local Address FE80::206:53FF:FEBA:F640, Interface ID 13
Area 0, Process ID 1, Instance ID 0, Router ID 10.200.200.11
Network Type POINT_TO_POINT, Cost: 1562
Index 1/2/2, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Link Local Address FE80::206:53FF:FEBA:F640, Interface ID 3
Network Type BROADCAST, Cost: 1
Designated Router (ID) 10.200.200.11, local address
FE80::206:53FF:FEBA:F640
Backup Designated router (ID) 10.200.200.13, local address
FE80::206:53FF:FEBA:F700
Next 0x0(0)/0x0(0)/0x0(0)
Printout 210: OSPFv3 interface information on R1
R2#show ipv6 ospf interface
Link Local Address FE80::206:53FF:FE03:9C40, Interface ID 8
Network Type POINT_TO_POINT, Cost: 1562
Next 0x0(0)/0x0(0)/0x0(0)
Link Local Address FE80::206:53FF:FE03:9C40, Interface ID 3
Network Type BROADCAST, Cost: 1
Designated Router (ID) 10.200.200.12, local address
FE80::206:53FF:FE03:9C40
Backup Designated router (ID) 10.200.200.14, local address
FE80::206:53FF:FEC7:D100
Next 0x0(0)/0x0(0)/0x0(0)
Printout 211: OSPFv3 interface information on R2
Step 12 Verify the formation of OSPFv3 neighborship and examine the DR/BDR election on the
Ethernet segments. The information provided with this output among other shows you the
neighboring routers router ID, state in which this neighborship is, and the interface through
which the neighborship is formed.
R1#show ipv6 ospf neighbor

Neighbor ID Pri State Dead Time Interface ID
Interface
10.200.200.12 1 FULL/ - 00:00:32 8
Serial0/0.1
10.200.200.13 1 FULL/BDR 00:00:34 3
FastEthernet0/0
Printout 212: OSPFv3 neighbor information on R1 router

Interface
10.200.200.11 1 FULL/ - 00:00:37 13
Serial0/0.1
10.200.200.14 1 FULL/BDR 00:00:34 3
FastEthernet0/0

Interface
10.200.200.11 1 FULL/DR 00:00:30 3
FastEthernet0/0

Interface
10.200.200.12 1 FULL/DR 00:00:37 3
FastEthernet0/0
Step 13 Check the IPv6 routing table to verify that IPv6 routing information has been exchanged between
the routers participating in the OSPFv3 domain. You should see new routesOSPFv3 intra-area
routes denoted with Oin the routing table. The next hop for those routes is the link-local IPv6
address of the neighbor.
R1#show ipv6 route
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext
2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
C 2001:410:1:12::/64 [0/0]
via ::, Serial0/0.1
L 2001:410:1:12:206:53FF:FEBA:F640/128 [0/0]
via ::, Serial0/0.1
C 2001:410:1:13::/64 [0/0]
L 2001:410:1:13:206:53FF:FEBA:F640/128 [0/0]
O 2001:410:1:24::/64 [110/1563]
via FE80::206:53FF:FE03:9C40, Serial0/0.1
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Printout 216: IPv6 routing table on R1 router
R2#show ipv6 route
<... part of the output omitted ...>
C 2001:410:1:12::/64 [0/0]
via ::, Serial0/0.1
L 2001:410:1:12:206:53FF:FE03:9C40/128 [0/0]
via ::, Serial0/0.1
O 2001:410:1:13::/64 [110/1563]
via FE80::206:53FF:FEBA:F640, Serial0/0.1
C 2001:410:1:24::/64 [0/0]
L 2001:410:1:24:206:53FF:FE03:9C40/128 [0/0]
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
R3#show ipv6 route
O 2001:410:1:12::/64 [110/1563]
via FE80::206:53FF:FEBA:F640, FastEthernet0/0
C 2001:410:1:13::/64 [0/0]
L 2001:410:1:13:206:53FF:FEBA:F700/128 [0/0]
O 2001:410:1:24::/64 [110/1564]
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
R4#show ipv6 route
O 2001:410:1:12::/64 [110/1563]
via FE80::206:53FF:FE03:9C40, FastEthernet0/0
O 2001:410:1:13::/64 [110/1564]
C 2001:410:1:24::/64 [0/0]
L 2001:410:1:24:206:53FF:FEC7:D100/128 [0/0]
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Step 14 Verify that you have end-to-end connectivity in your IPv6 network using the ping and
traceroute commands. Use the IPv6 address table (Table 39) from Task 1.
R4#ping 2001:410:1:13:206:53FF:FEBA:F640

!!!!!

R4#ping 2001:410:1:12:206:53FF:FEBA:F640

!!!!!
Printout 220: Ping from R4 to R1 Fe0/0 and R1 S0/0.1
R4#traceroute 2001:410:1:13:206:53FF:FEBA:F640

Tracing the route to 2001:410:1:13:206:53FF:FEBA:F640

1 2001:410:1:24:206:53FF:FE03:9C40 0 msec 0 msec 4 msec
2 2001:410:1:12:206:53FF:FEBA:F640 44 msec 44 msec 44 msec

R4#traceroute 2001:410:1:12:206:53FF:FEBA:F640

Tracing the route to 2001:410:1:12:206:53FF:FEBA:F640

1 2001:410:1:24:206:53FF:FE03:9C40 4 msec 0 msec 4 msec
2 2001:410:1:12:206:53FF:FEBA:F640 44 msec 44 msec 44 msec
Printout 221: Traceroute from R4 to R1 Fe0/0 and R1 S0/0.1
Task 3: Configuring IPv6 Tunnel
You will provide an additional path for the IPv6 network via IPv4 network by implementing
IPv6 tunnel.
Step 15 Create an IPv6 tunnel between R3 and R4 routers. Use the Serial0/0.1 interfaces for tunnel source
and destination. Assign 2001:410:1:a::3/64 IPv6 address to R3 tunnel interface and
2001:401:1:a::4/64 IPv6 address to R4 tunnel interface.
Step 16 Include the newly configured tunnel interface into the OSPFv3 routing domain by enabling the
OSPFv3 on the tunnel interface. Set the bandwidth of the tunnel to 1024 to make tunnel
preferable compared to Frame Relay connection between R1 and R2.
Verification
Step 17 Verify the tunnel interface configuration by examining the tunnel information.
R3#show interfaces tunnel 0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
MTU 1514 bytes, BW 1024 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 10.1.3.3 (Serial0/0.1), destination 10.1.3.4
Tunnel protocol/transport IPv6/IP, key disabled, sequencing disabled
Tunnel TTL 255
Checksumming of packets disabled, fast tunneling enabled
Last input 00:00:02, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
32 packets input, 4056 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
41 packets output, 4260 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
R3#show ipv6 interface tunnel 0
IPv6 is enabled, link-local address is FE80::A01:303
2001:410:1:A::3, subnet is 2001:410:1:A::/64
FF02::1
FF02::2
FF02::5
FF02::1:FF00:3
FF02::1:FF01:303
MTU is 1480 bytes
Printout 222: IPv6 tunnel interface information on R3 router
Hardware is Tunnel
Keepalive not set
Tunnel TTL 255
Last clearing of "show interface" counters never
R4#show ipv6 interface tunnel 0
IPv6 is enabled, link-local address is FE80::A01:304
2001:410:1:A::3, subnet is 2001:410:1:A::/64 [DUPLICATE]
FF02::1
FF02::2
FF02::5
FF02::1:FF00:3
FF02::1:FF01:304
MTU is 1480 bytes
Printout 223: IPv6 tunnel interface information on R4 router
Step 18 Examine the IPv6 routing table on R3 and R4 routers. You should notice that the path to the
distant Ethernet segment is now available via IPv6 tunnel interface.
R3#show ipv6 route
C 2001:410:1:A::/64 [0/0]
via ::, Tunnel0
L 2001:410:1:A::3/128 [0/0]
via ::, Tunnel0
O 2001:410:1:12::/64 [110/1563]
C 2001:410:1:13::/64 [0/0]
L 2001:410:1:13:206:53FF:FEBA:F700/128 [0/0]
O 2001:410:1:24::/64 [110/98]
via FE80::A01:304, Tunnel0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
R4#show ipv6 route
C 2001:410:1:A::/64 [0/0]
via ::, Tunnel0
O 2001:410:1:12::/64 [110/1563]
O 2001:410:1:13::/64 [110/98]
via FE80::A01:303, Tunnel0
C 2001:410:1:24::/64 [0/0]
L 2001:410:1:24:206:53FF:FEC7:D100/128 [0/0]
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Step 19 Verify that you have end-to-end connectivity in your IPv6 network using the ping command. To
make this verification part easier use the table with IPv6 addresses (Table 39) from Task 1. To
ensure that traffic is passing via tunnel interface clear the tunnel interface counters prior to
issuing the ping commands.
R3#clear counters tunnel 0
Clear "show interface" counters on this interface [confirm]
R3#show interfaces tun 0
02:39:46: %CLEAR-5-COUNTERS: Clear counter on interface Tunnel0 by
console

Hardware is Tunnel
Keepalive not set
Tunnel TTL 255
Last clearing of "show interface" counters 00:00:01

R3#ping 2001:410:1:24:206:53FF:FEC7:D100

Sending 5, 100-byte ICMP Echos to 2001:410:1:24:206:53FF:FEC7:D100,
!!!!!

Hardware is Tunnel
Keepalive not set
Tunnel TTL 255
Last clearing of "show interface" counters 00:00:07
Printout 226: Connection verification from R3 to R4 Fe0/0
Lab Topology

R1, R2 Edge routers
The routers are connected with Ethernet and Frame Relay linksthe first serial interface of each
R1 723 10.1.0.1 R2 732 10.1.0.2
R3 714 10.1.3.3 R4 741 10.1.3.4
Note The routers have additional (Fast)Ethernet subinterface, which is used solely for downloading
the IOS image upon boot. Do not change configuration of that subinterface on any router.
This section contains information on IP addressing ranges used in the remote lab.
Note IP addressing, except loopback addresses, has been pre-configured to allow you to focus
Parameter Value

Figure 39: Addressing of lab exercise routers


Copyright 2006, NIL Data Communications Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel Lab Solutions 195
BSCI
Configuring IPv6 Addressing,
OSPFv3 Routing, and IPv6
Tunnel Lab Solutions
Lab Solution
Task 1: Configuring IPv6 Addressing
ipv6 unicast-routing
ipv6 cef
!
ipv6 address 2001:410:1:13::/64 eui-64
!
ipv6 address 2001:410:1:12::/64 eui-64
Configuration 64: IPv6 configuration on R1 router
ipv6 cef
!
ipv6 address 2001:410:1:24::/64 eui-64
!
ipv6 address 2001:410:1:12::/64 eui-64
ipv6 cef
!
ipv6 address 2001:410:1:13::/64 eui-64
196 Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel Lab Solutions Copyright 2006, NIL Data Communications
ipv6 cef
!
ipv6 address 2001:410:1:24::/64 eui-64
Task 2: Configuring OSPFv3 Single Area Routing
ipv6 ospf 1 area 0
!
ipv6 ospf 1 area 0
!
ipv6 router ospf 1
router-id 10.200.200.11
Configuration 68: OSPFv3 configuration on R1 router
ipv6 ospf 1 area 0
!
ipv6 ospf 1 area 0
!
ipv6 router ospf 1
router-id 10.200.200.12
ipv6 ospf 1 area 0
!
ipv6 router ospf 1
router-id 10.200.200.13
ipv6 ospf 1 area 0
!
ipv6 router ospf 1
router-id 10.200.200.14
Copyright 2006, NIL Data Communications Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel Lab Solutions 197
Task 3: Configuring IPv6 Tunnel
interface Tunnel0
bandwidth 1024
ipv6 address 2001:410:1:A::3/64
ipv6 ospf 1 area 0
tunnel source Serial0/0.1
tunnel destination 10.1.3.4
tunnel mode ipv6ip
Configuration 72: IPv6 tunnel configuration on R3 router
interface Tunnel0
bandwidth 1024
ipv6 address 2001:410:1:A::3/64
ipv6 ospf 1 area 0
tunnel source Serial0/0.1
tunnel destination 10.1.3.3
tunnel mode ipv6ip
Configuration 73: IPv6 tunnel configuration on R4 router

198 Configuring IPv6 Addressing, OSPFv3 Routing, and IPv6 Tunnel Lab Solutions Copyright 2006, NIL Data Communications

BSCI30 NIL Lab Guide PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BSCI30 NIL Lab Guide PDF

Загружено:

Авторское право:

Доступные форматы

BSCI

Вам также может понравиться