1 - Sproute 1.0 - Lab Guide

SPROUlE I

Deploying CiscoService ProviderNetwork RoutingVersion 1.0

Lab Guide

Text Part Number: 97-3149-01

Americas HeadquartersCisco Systems, Inc.San Jose, CA

Asia Pacific HeadquartersCisco Systems (USA) Pte. Ltd.Singapore

Europe HeadquartersCisco Systems International BV Amsterdam,The Netherlands

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at www.cisco.com/goJoffices.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to thisURL: WI.VI.V.cisco.com/goltrademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply apartnership relationship between Cisco and any other company. (111 OR)

DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED "AS IS." CISCO MAKES AND YOU RECEIVE NO WARRANTIESIN CONNECTION WITH THE CONTENT PROVIDED HEREUNDER, EXPRESS, IMPLIED, STATUTORY OR IN ANY OTHERPROVISION OF THIS CONTENT OR COMMUNICATION BETWEEN CISCO AND YOU. CISCO SPECIFICALLY DISCLAIMS ALLIMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR APARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. This learning productrnay contain early release content, and while Cisco believes it to be accurate, it falls subject to the disclairner above.

Lab Guide 2012 Cisco and/or its affiliates. All rights reserved.

Table of ContentsVolume 2

Lab Guide

OverviewOutline

Job AidsPod Access InformationDevice InformationIP AddressingNET Addressing

Lab 2-1: Implement OSPF RoutingActivity ObjectiveVisual ObjectiveOSPF AreasRequired ResourcesCommand ListTask 1: Enable OSPF on the RoutersTask 2: Influence OSPF DR and BDR ElectionTask 3: Influence OSPF Route Selection by Changing OSPF Link CostTask 4: Configure OSPF AuthenticationTask 5: Configure OSPF Virtual Links

Lab 2-2: Implement OSPF Special Area TypesActivity ObjectiveVisual ObjectiveOSPF AreasRequired ResourcesCommand ListTask 1: Enable OSPF SummarizationTask 2: Configure OSPF Stub Area

Lab 3-1: Implement Integrated IS-IS RoutingActivity ObjectiveVisual ObjectiveNET AddressingRequired ResourcesCommand ListTask 1: Enable Integrated IS-IS on the RoutersTask 2: IS-IS Route SummarizationTask 3: Enable IPv6 IS-IS Routing

Lab 4-1: Implement Basic BGP RoutingActivity ObjectiveVisual ObjectiveNET AddressingRequired ResourcesCommand ListTask 1: Configure External BGPTask 2: Configure Internal BGP

Lab 5-1: Implement Route RedistributionActivity ObjectiveVisual ObjectiveRequired ResourcesCommand ListTask 1: Redistribute Between OSPF and IS-ISTask 2: Prevent Potential Routing LoopsTask 3: Modify Administrative DistanceTask 4: One-way redistribution

1

1122246777889

112323252631313132323335364141414242434547485151515252535657595959606163666972

Lab 5-2: Influence BGP Route SelectionActivity ObjectiveVisual ObjectiveRequired ResourcesCommand ListTask 0: Set Second Link Between CE and PETask 1: Configure BGP Weight and Local PreferenceTask 2: Configure BGP Multi-Exit-DiscriminatorTask 3: Configure BGP Community

Answer KeyLab 2-1 Answer Key: Implement OSPF RoutingLab 2-2 Answer Key: Implement OSPF Special Area TypesLab 3-1 Answer Key: Implement Integrated IS-IS RoutingLab 4-1 Answer Key: Implement Basic BGP RoutingLab 5-1 Answer Key: Implement Route RedistributionLab 5-2 Answer Key: Influence BGP Route Selection

Deploying Cisco Service Provider Network Routing (SPROUTE) v1.0

7474747576787980828787939598

100103

2012 Cisco Systems, Inc.

SPROUTEI

Lab Guide

OverviewThis guide presents the instructions and other information concerning the lab activities for thiscourse. You can find the solutions in the lab activity Answer Key.

OutlineThis guide includes these activities:

Job Aids

Lab 2-1: Implement OSPF Routing

Lab 2-2: Implement OSPF Special Area Types

Lab 3-1: Implement Integrated IS-IS Routing

Lab 4-1: Implement Basic BGP Routing

Lab 5-1: Implement Route Redistribution

Lab 5-2: Influence BGP Route Selection

Appendix A: Tear-Out

Job AidsThese job aids are available to help you complete lab activities.

Pod Access InformationInstructor will provide you with the team and pod numbers, as well as other team and podaccess information. Write down the information in the table for future reference.

Parameter Default value Value

Team number z =1 - 4Pod number x =1,3,5,7

or

y =2, 4, 6, 8Remote lab SSH access IP address 128.107.245.9

Remote lab SSH access username instr

Remote lab SSH access password testMe

Pod PE (Cisco lOS XR) router username root

Pod PE (Cisco lOS XR) router password 1ron Man

Pod CE, SW and PE privileged level password cisco

Device InformationThis lab topology consists of four (4) teams and eight (8) pods. Two students will work in onepod and two pods will work in one team. Each pod has one switch and two routers. Two podsshare one additional switch. All teams share same core routers (P 1 and P2).

The CE routers in both pods are running Cisco lOS Software. The first pod within a team (pods1,3,5, or 7) will work on the PE router running Cisco IOS XR Software, and the second podwithin the same team (pods 2, 4, 6, or 8) will work on the PE router running Cisco IOS XESoftware.

Devices in the lab are connected with Fast Ethernet and Gigabit Ethernet connections and twoteams have a redundant POS connection, as shown in the following topology:

2 Deploying Cisco Service Provider Network Routing (SPROUTE) v1.0 2012 Cisco Systems, Inc.

Team 1

SW3 Pod 3 CE3

II" ----." /

I I , '"

~:::;I

SW7 Pod 7 CE7

II" ---." /I I " '"

Team 2

PEBPE6

SW5Pod 5

, ;~ I I, "'''' I I

CE5

CE6 Pod 6 SW6

~, I I

","'SW12'~ I I

w---CE2 Pod 2 SW2

, I I/SW56" I I---- '

CE1 Pod 1 SW1.---", ;~/I I, "'''' I I

I:==:C

Team 3 Team 4C2012Ci'"""8rd'oritstrflili*'".A1lrigi'ts......".......

Device Roles and Loopback IP Addresses

Device Name Device Role LoO IPv4 Address LoO IPv6 Address

CEx Cisco 2900 pod router 10.x.10.1/32 2001 :db8:1 O:x: 10:: 1/128

CEy 10.y.10.1/32 2001 :db8:1 0:y:1 0:: 1/128

PEx Cisco ASR 9000 or Cisco 10.x.1.1/32 2001 :db8:1 O:x: 1:: 1/128

PEy ASR 1000 pod router 10.y.1.1/32 2001 :db8:10:y:1 ::1/128

SWx Cisco ME340x pod switch 10.x.0.1/32 2001 :db8:1 O:x:O:: 1/128

SWy 10.y.0.1 /32 2001 :db8:1 0:y:0::1/128

SWxy Cisco ME340x pod switch 10.xy.0.1 /32 2001 :db8:1 0:xy:0::1 /128shared inside a team

P1 Cisco ASR 9000 core router 10.0.1.1/32 2001 :db8:1 0:0:1 ::1/128

P2 Cisco ASR 9000 core router 10.0.2.1/32 2001 :db8:1 0:0:2::1/128

The following figure illustrates the interface identification used in this lab setup.

2012 Cisco Systems, Inc. Lab Guide 3

Teamz

CEx Podx SWx PEx

P1

P2

Connections toPE(y+2)

GiOIOIOIO

FaO/2

FaO/2

FaO/1

FaO/1

/ I IFaO/2} 1'1' I' I I

I' 'FaO/24I IFaO/21 I' I' I I

1', I' FaO/211

IFaO/221'. FaO/22

GiOIO

GiOIO

---Gi

- - - Fa........... OC3 pos

Legend:

,GiO/1 , , , ,

FaO/~

FaO/2 I' ' '~\.aO/23 FaO/21 1 IFaO/22I' SWxy " I I

1'1' Fa0/24' ~ -fa0/23 I I

I' " I IGiO/1 I' FaO/24 "

GiOIOIO

CEy Pod Y SWy PE~osol2li"

L.=:====:::::::::================::r:":'::'"poso;~~:~:::'':OSO/21O.,.,

C2012Ci:OC08rd'oritstrflili*'".A1lrigi'ts......".......

IP AddressingThe following figure illustrates the IP addressing scheme used in this lab setup.

Teamz

P2192.168.10y.0/24

I

:~

:/

p

SWy

.,I' "

SWxy "

""""

" .~

1'1"10.xy.0.1 1'1'

1'1'1'1'

1'1'1'1'

192.168.1Oy.0/24

Pod x SWx192.168.10x.0/24 192.168.10x.0/24

- - - - - - - - - - P1

CEy

Legend: ---Gi

- - - Fa........... OC3 pos-3 Loopback

z = 1,2,3,4x = 1,3,5,7Y= 2,4,6,8w = 1 (for teams 1 and 2)

2 (for teams 3 and 4)

Connections toPE(y+2)

The following figure illustrates the management IP addresses used in this lab setup.


Team 1

CE1 Pod 1 SW1

10.10.10.14 - -110.$0.11 I- ""'"iFit:~iT'", ;~/I I

" "'''' I I10.10.10.13

/ ~, I I

//SW12"~ I I

10.10.10.15 -110.~.12 ~ - ....,..".~~'+\CE2 Pod 2 SW2

CE5 Pod 5 SW5

10.10.10.30 - -110~.27 I - ""'"iF.;:;~FrI", ;~ I I

" "'''' I I

C2012Ci'"""8rd'oritstrflili*'".A1lrigi'ts......".......

Team 2

SW3 Pod 3 CE3

t":;';f~~ - -t 10$19 1- 10.10.10.22I I '~, /I I " '"

Team 4

Note Replace the x or y with your pod number to get the IP addresses within your pod (x is for

odd number pods 1, 3, 5, and 7; y is for even number pods 2, 4, 6, and 8). Replace the xy

(where x < y) with numbers of the pods within the same team (for example, 12, 34, 56, or

78) to get IP addresses on the link between those pods.

Pod IP Addressing

Device Interface IPv4 Address IPv6 Address

CEx GiO/O 192.168.1 Ox.x1 /24 2001 :db8:192:168:1 Ox::x1/80

CEy GiO/O 192.168.10y.y1/24 2001 :db8:192:168:1 Oy::y1 /80

P1 192.168.x1.1/24 2001 :db8:192:168:x1:: 1/80

192.168.y1.1/24 2001 :db8:192:168:y1 ::1/80

P2 192.168.x2.2/24 2001 :db8:192:168:x2::2/80

192.168.y2.2/24 2001 :db8:192:168:y2::2/80

PE2 POSO/2/0 192.168.211.20/24 2001 :db8:192:168:211 ::20/80

POSO/2/1 192.168.212.20/24 2001 :db8:192:168:212::20/80

PE4 POSO/2/0 192.168.211.40/24 2001 :db8:192:168:211 ::40/80

POSO/2/1 192.168.212.40/24 2001 :db8:192:168:212::40/80

PE6 POSO/2/0 192.168.221.60/24 2001 :db8:192:168:221 ::60/80

POSO/2/1 192.168.222.60/24 2001 :db8:192:168:222::60/80

PE8 POSO/2/0 192.168.221.80/24 2001 :db8:192:168:221 ::80/80

POSO/2/1 192.168.222.80/24 2001 :db8:192:168:222::80/80

PEx GiO/O/O/O 192.168.10x.xO/24 2001 :db8:192:168:1 Ox::xO/80

GiO/0/0/1 192.168.1 xy.xO/24 2001 :db8:192:168:1 xy::xO/80


Device Interface IPv4 Address IPv6 Address

GiO/0/0/2 192.168.x1.xO/24 2001 :db8:192:168:x1 ::xO/80

GiO/0/0/3 192.168.x2.xO/24 2001 :db8:192:168:x2::xO/80

PEy GiO/O/O 192.168.10y.yO/24 2001 :db8:192:168:1 Oy::yO/80

GiO/0/1 192.168.1 xy.yO/24 2001 :db8:192:168:1 xy::yO/80

GiO/0/2 192.168.y1.yO/24 2001 :db8:192:168:y1 ::yO/80

GiO/0/3 192.168.y2.yO/24 2001 :db8:192:168:y2::yO/80

Core IP Addressing

Device Device IP Address Peer Peer IP Address

P1 192.168.1.1/24 P2 192.168.1.2/24

2001 :db8:192:168:1:: 1/80 2001 :db8:192:168:1 ::2/80

192.168.2.1/24 192.168.2.2/24

2001 :db8:192:168:2:: 1/80 2001 :db8:192:168:2::2/80

NET AddressingThis subtopic includes table with NET addresses used in the lab activities.

Pod and Backbone NET Addresses

Replace the x or y with your pod number to get the NET addresses for routers.

Router NET address

P1 49.0000.0100.0000.1001.00

P2 49.0000.0100.0000.2001.00

CEx 49.000x.0100.0x01.0001.00

CEy 49.000y.0100.0y01.0001.00

PEx 49.000x.0 100.OxOO.1 00 1.00

PEy 49.000y.0100.0yOO.1001.00


Lab 2-1: Implement OSPF RoutingComplete this lab activity to practice what you learned in the related module.

Activity ObjectiveIn this lab activity, you will configure OSPF routing by enabling OSPF Area 0 to run in thebackbone and other nonbackbone areas to run in your pod.

Note Students from two different pods are working in team. The CE routers in both pods are

running Cisco lOS Software. The first pod in the team will work on the PE router running

Cisco lOS XR Software and the second pod in the same team will work on the PE router

running Cisco lOS XE Software. Students in the same team should coordinate their lab

activity.

In the lab activity, you will work on different Cisco routers running Cisco lOS (c2900), CiscoIOS XE (asrlOOl), and Cisco lOS XR (asr9k) Software. After completing this activity, you willbe able to meet these objectives:

Configure routers with OSPFv2 and OSPFv3 routing protocols and stable OSPF router IDs

Influence OSPF DR and BDR election on a LAN

Influence OSPF route selection by changing the OSPF link cost

Configure OSPF authentication

Configure OSPF virtual links to support OSPF areas not directly connected to Area 0

Visual ObjectiveThe figure illustrates what you will accomplish in this activity.

OSPFAreay

OSPF Area 1y

miitJliltM11fij

Teamz

Pody

Pod x OSPF Area 1xGiO/o- -- -- -- -- - -- -- -- -- -- -D~~=~

I OSPF Link Cost I

OSPFAreayOO


OSPF AreasThis section includes a table with OSPF areas used in the lab. Replace the x or y with your podnumber to get the OSPF areas used in the lab.

Link OSPF area

P1 - P2

P1 and P2 LoopbackO

PEx- P1, PEy- P1 0

PEx - P2, PEy - P2

PEx - PEy

PEx LoopbackO, PEy LoopbackO x, y

CEx - PEx, CEy - PEy1x, 1y

CEx LoopbackO, CEy LoopbackO

CEx Loopback1x (1x.O.O.1/24), CEy xOO, yOOLoopback1y (1y.O.O.1/24)

Required ResourcesThese are the resources and equipment that are required to complete this activity:

A PC with access to the Internet

An SSH client installed on the PC


Command ListThe table describes the commands that are used in this lab activity.

Cisco 10SIIOS XE Commands

Command Description

[no] shutdown Enables or disables interface

area area virtual-link IP-address (Router) Enables OSPF virtual link

clear ip ospf process Clears OSPF processes on the router

configure terminal Enters configuration mode

interface interface Enters interface configuration mode

ip ospf authentication message-digest Enables OSPF MD5 authentication on the interface

ip ospf cost cost Sets OSPF link cost on the interface

ip ospf message-digest-key key-ID md5 Sets OSPF MD5 key on the interfacekey

ip ospf priority priority Sets OSPF interface priority for DR and BDRelection

iplipv6 address ip_address subneLmask Sets an IPv4 or IPv6 address and the subnet maskon the interface

ipv6 enable Enables IPv6 support on the interface

ipv6 ospf process-id area area Enables OSPFv3 routing on the interface

ipv6 unicast-routing Globally enables IPv6 unicast routing

network prefix wildcard_mask area area (Router) Enables OSPF routing on the network andplaces network into OSPF area

ping desL/P source source_IP Verifies connectivity between source IP anddestination IP

router ospf process-id Enables OSPFv2 proccess on the router

router-id IP-address (Router) Sets OSPF router 10

show ip interface brief Displays interface status and IPv4 addressesconfigured

show ip ospf Displays information related to the OSPF routingprotocol running on the router

show ip ospf interface Displays OSPF interface information

show ip ospf virtual-links Displays OSPF virtual link information

show iplipv6 ospf database Displays the content of the OSPF database

show iplipv6 ospf neighbors Displays OSPF neighbor information

show iplipv6 protocols Displays IPv4 or IPv6 protocols running on therouter

show iplipv6 route Displays the current routes in the routing table

show running-config Displays running configuration


Cisco IDS XR Commands

Command Description

[no] shutdown Enables or disables interface

area area (Router) Creates OSPF area on the router

authentication message-digest (Router) Enables OSPF MD5 authentication on theinterface

clear ospf process Clears OSPF processes on the router

commit Commits changes to the running configuration


cost cost (Router) Sets OSPF link cost on the interface

interface interface (Global) Enters interface configuration mode

interface interface (Router) Defines the interfaces on which the OSPFprotocol runs

ipv41ipv6 address ip_addressAen Sets the IPv4 or IPv6 address for an interface andthe subnet mask using the prefix length format

ipv6 enable Enables IPv6 support on the interface

message-digest-key key-ID md5 key (Router) Sets OSPF MD5 key on the interface

ping desL/P source [source_/p] Verifies connectivity between source IP anddestination IP (IPv4 and IPv6)

priority priority (Router) Sets OSPF interface priority for DR andBDR election

router ospflospfv3 process-IO Creates a OSPFv2 or OSPFv3 process

router-id IP-address (Router) Sets OSPF router 10.

show ipv4 interface brief Displays interface status and IPv4 addressesconfigured

show ospf Displays information related to the OSPF routingprotocol running on the router

show ospf interface Displays OSPF interface information

show ospflospfv3 database Displays the content of the OSPF database

show ospflospfv3 neighbors Displays OSPF neighbor information

show protocols Displays protocols running on the router

show route Displays the current routes in the routing table

show running-config Displays running configuration

traceroute IP-address Traces IP address

virtual-link IP-address (Router) Enables OSPF virtual link


Step 1

Task 1: Enable OSPF on the RoutersIn this task, you will enable OSPF version 2 and OSPF version 3 routing protocols and you willconfigure stable OSPF router IDs.

Activity Procedure

Complete these steps to prepare the initial configuration for routers in your pod.

On the CE router, enable GiOIO and LoO interfaces and configure IP addresses. Onthe PE router enable GiOIOIOIO, GiOIOIOII, GiOIOIO/2, GiOIOIO/3, and LoopbackOinterfaces and configure IP addresses. Find correct IP addresses in the visualobjective figure.

On the CE router, there should be first Gigabit Ethernet and Loopback interfaces up andrunning with assigned IP addresses.

CE1#show ip interface brief I include GigabitEthernetOjOILoopbackOGigabitEthernetO/O 192.168.101.11 YES manual upLoopbackO 10.1.10.1 YES manual up

On the PE router, there should be four Gigabit Ethernet and Loopback interfaces up andrunning with assigned IP addresses.

upup

RP/0/RSPO/CPUO:PE1#showThu Jun 8 00:08:39.335LoopbackOMgmtEthO/RSPO/CPUO/OGigabitEthernetO/O/O/OGigabitEthernetO/0/0/1GigabitEthernetO/0/0/2GigabitEthernetO/0/0/3

ipv4 interface briefUTC

10.1.1.110.10.10.17192.168.101.10192.168.112.10192.168.11.10192.168.12.10

include Up

upUpUpUpUpUp

UpUpUpUpUpUp

Step 2 You should be able to successfully test IP connectivity between CE and PE routersin your pod, between PE routers in your team, and between the PE router in yourteam and core routers P I and P2.

Successful ping from PE to CE router:

RP/0/RSPO/CPUO:PE1#ping 192.168.101.11Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.101.11, timeout is 2 seconds:!!!! !

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

Successful ping between PE routers in your team:



Successful ping between PE router in your team and core routers P I and P2:


Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 msRP/0/RSPO/CPUO:PE1#ping 192.168.12.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.12.2, timeout is 2 seconds:!!!! !Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms


In the following steps, you will configure basic OSPF routing in your team routers:

Step 3

Step 4

Step 5

Determine OSPF area for every link in your team. Use visual objective and OSPFAreas sections to complete this step:

Link (Interface) OSPF Area

PEx (GiO/O/O/2) - P1

PEx (GiO/O/O/3) - P2

PEx (GiO/O/O/1) - PEy (GiO/O/O/1)

PEx (GiO/O/O/O) - CEx (GiO/O)

PEx (LoopbackO)

CEx (LoopbackO)

On the CE and PE routers in your pod, enable OSPF routing and assign interfaces tothe areas determined in the previous step. Use OSPF process ID 1.

You should be able to successfully test IP connectivity between CE routers in yourteam.

Successful ping from CE router in your pod and CE router in neighbor pod (same team).

CE1#ping 10.2.10.1

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.2.10.1, timeout is 2 seconds:!!!! !Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

Step 6 Verify what router ID is assigned to the OSPF routing process on CE and PErouters. Find out what OSPF router IDs are assigned in the neighbor pod (sameteam).

The OSPF router ID on the CE and PE routers:

CE1#show ip ospf I include IDRouting Process "ospf 1" with ID 10.1.10.1

RP/0/RSPO/CPUO:PE1#show ospf I include IDRouting Process "ospf 1" with ID 10.1.1.1

Write the results into the following table:

Router OSPF Router 10

PEx (pod)

CEx (pod)

PEy (neighbor pod)

CEy (neighbor pod)

Step 7

Step 8

On the CE and PE routers in your pod, set OSPF router IDs to the IP addressesxO.xO.xO.xO (for CEx) and x.x.x.x (for PEx) or yO.yO.yO.yO (for CEy) and y.y.y.y(for PEy), where x or y is your pod number. Make sure that the new OSPF routerIDs will take effect.

On the CE and PE routers in your pod, enable IPv6 routing. On the CE router,enable IPv6 on GiOIO and LaO interfaces and configure IPv6 address on the LaOinterface only. On the PE router, enable IPv6 on GiO/oIOIO, GiO/OIOIl, GiOIOIO/2,GiO/oIO/3, and LaO interfaces and configure IP address on the LaO interface only.Find correct IPv6 addresses in the visual objective figure.


Step 9 On the CE and PE routers in your pod, enable OSPF version 3 routing and assigninterfaces to the areas as used for OSPF version 2.

Last Update00:07:1200:13:14

Activity Verification

You have completed this task when you attain these results:

On the CE router in your pod, verify IP protocols running, OSPF neighbors, and the OSPFdatabase. There should be one OSPF neighbor. The OSPF database should show LSAsfrom Area lx, where x is your pod number. Outputs should be similar to the following:

CE1#show ip protocols*** IP Routing is NSF aware ***

Routing Protocol is "ospf 1"Outgoing update filter list for all interfaces is not setIncoming update filter list for all interfaces is not setRouter ID 10.10.10.10Number of areas in this router is 1. 1 normal 0 stub 0 nssaMaximum path: 4Routing for Networks:

10.1.10.1 0.0.0.0 area 11192.168.101.11 0.0.0.0 area 11

Routing Information Sources:Gateway Distance1.1.1.1 11010.1.1.1 110

Distance: (default is 110)

CE1#show ip ospf neighbor

Neighbor ID Pri State1.1.1.1 1 FULL/BDRCE1#show ip ospf database

Dead Time00:00:38

Address192.168.101.10

InterfaceGiO/O

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

Router Link States (Area 11)

Link ID1.1.1.110.10.10.10

ADV Router1.1.1.110.10.10.10

Age558550

Seq# Checksum Link countOx80000003 OxOOOB6A 1Ox80000003 Ox0008FD 2

Net Link States (Area 11)

Link ID192.168.101.11

ADV Router10.10.10.10

Age550

Seq# ChecksumOx80000001 Ox007E8D

Summary Net Link States (Area 11)

Link ID10.0.1.110.0.2.110.1.1.110.2.1.110.2.10.1192.168.1. 0192.168.2.0192.168.11.0192.168.12.0192.168.21.0192.168.22.0192.168.31.0192.168.32.0192.168.41.0192.168.42.0192.168.51.0192.168.52.0


ADV Router1.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.1

Age558558559482447558558559558559559559559559560560560

Seq#Ox80000002Ox80000002Ox80000002Ox80000005Ox80000001Ox80000002Ox80000002Ox80000002Ox80000005Ox80000002Ox80000002Ox80000002Ox80000002Ox80000002Ox80000002Ox80000002Ox80000002

ChecksumOxOOE544OxOODA4EOxOOCF5AOxOOC75DOx0076A8OxOOCOOBOxOOB515Ox00487AOx003787OxOOE3D3OxOOD8DDOx007538Ox006A42Ox00079COxOOFBA6Ox009801Ox008DOB

Lab Guide 13

192.168.61.0 1.1.1.1 560 Ox80000002 Ox002A65192.168.62.0 1.1.1.1 560 Ox80000002 Ox001F6F192.168.71.0 1.1.1.1 560 Ox80000002 OxOOBBC9192.168.72.0 1.1.1.1 560 Ox80000002 OxOOBOD3192.168.81.0 1.1.1.1 560 Ox80000002 Ox004D2E192.168.82.0 1.1.1.1 560 Ox80000002 Ox004238192.168.102.0 1.1.1.1 448 Ox80000001 Ox0067FF192.168.112.0 1.1.1.1 493 Ox80000006 OxOOE474

On the PE router in your pod, verify IP protocols running, OSPF neighbors, and the OSPFdatabase. There should be four OSPF neighbors. The OSPF database should show LSAsfrom areas 0, x, and lx, where "x" is your pod number. Outputs should be similar to thefollowing:

RP/0/RSPO/CPUO:PE1#show protocolsRouting Protocol OSPF 1

Router Id: 1.1.1.1Distance: 110Non-Stop Forwarding: DisabledRedistribution:

NoneArea 0

GigabitEthernetO/0/0/1GigabitEthernetO/0/0/2GigabitEthernetO/0/0/3

Area 1LoopbackO

Area 11GigabitEthernetO/O/O/O

% EIGRP: EIGRP not configured

RP/0/RSPO/CPUO:PE1#show ospf neighbor* Indicates MADJ interface

Neighbors for OSPF 1

Neighbor ID Pri State2.2.2.2 1 FULL/BDR

Neighbor is up for 00:56:160.0.0.1 1 FULL/DR



Neighbor is up for 00:57:33

Total neighbor count: 4RP/0/RSPO/CPUO:PE1#show ospf database

Dead Time00:00:37

00:00:34

00:00:33

00:00:38

Address192.168.112.20

192.168.11.1

192.168.12.2

192.168.101.11

InterfaceGiO/0/0/1

GiO/0/0/2

GiO/0/0/3

GiO/O/O/O



Link ID ADV Router Age Seq# Checksum Link count0.0.0.1 0.0.0.1 559 Ox80000c12 Ox00756a 70.0.0.2 0.0.0.2 561 Ox80000cOc OxOOa364 81.1.1.1 1.1.1.1 562 Ox80000008 Ox00321e 32.2.2.2 2.2.2.2 557 Ox80000003 Ox00679f 33.3.3.3 3.3.3.3 617 Ox8000000a Ox006493 44.4.4.4 4.4.4.4 613 Ox80000002 OxOOce78 25.5.5.5 5.5.5.5 856 Ox80000004 OxOOObf8 310.7.1.1 10.7.1.1 1137 Ox800003cc OxOObb21 310.7.10.1 10.7.10.1 1795 Ox800003cO OxOOca09 210.8.10.1 10.8.10.1 696 Ox800005ce OxOOc2e6 210.100.100.100 10.100.100.100 670 Ox800003d3 Ox003516 330.30.30.30 30.30.30.30 4 (DNA) Ox80000002 OxOOa49d 1



Link ID ADV Router Age Seq# Checksum192.168.2.2 0.0.0.2 581 Ox80000b7e OxOOc17d192.168.11.1 0.0.0.1 592 Ox80000005 Ox009822192.168.12.2 0.0.0.2 599 Ox80000005 Ox00872f192.168.21.1 0.0.0.1 559 Ox80000003 Ox00604e192.168.22.2 0.0.0.2 561 Ox80000003 Ox004f5b192.168.31.1 0.0.0.1 1863 Ox80000006 Ox001e7f192.168.32.2 0.0.0.2 1847 Ox80000006 OxOOOd8c192.168.51.1 0.0.0.1 617 Ox80000004 OxOOa9d9192.168.52.2 0.0.0.2 842 Ox80000004 Ox0098e6192.168.71.70 10.7.1.1 1137 Ox800003bd OxOOe477192.168.82.80 10.100.100.100 670 Ox800003bb Ox0025da192.168.107.70 10.7.1.1 619 Ox80000395 OxOOa4aO192.168.108.81 10.8.10.1 696 Ox800003b8 Ox005d89192.168.112.10 1.1.1.1 562 Ox80000001 Ox001d29192.168.134.30 3.3.3.3 617 Ox80000003 OxOOc938


Link ID ADV Router Age Seq# Checksum10.1.1.1 1.1.1.1 595 Ox80000002 OxOOcf5a10.1.10.1 1.1.1.1 573 Ox80000001 Ox0078a810.2.1.1 2.2.2.2 558 Ox80000001 OxOOa77e10.2.10.1 2.2.2.2 519 Ox80000001 Ox004ecd10.3.1.1 3.3.3.3 1723 Ox80000003 Ox0079a510.3.10.1 3.3.3.3 892 Ox80000003 Ox0020f410.3.10.1 30.30.30.30 85 (DNA) Ox80000002 OxOOeabf10.4.1.1 4.4.4.4 608 Ox80000001 Ox0053c810.4.10.1 4.4.4.4 491 Ox80000001 OxOOf91810.5.10.1 5.5.5.5 608 Ox80000002 OxOOcd3e13.0.0.1 30.30.30.30 95 (DNA) Ox80000001 Ox00585d192.168.101. 0 1.1.1.1 573 Ox80000005 Ox006005192.168.102.0 2.2.2.2 558 Ox80000001 Ox003f25192.168.103.0 3.3.3.3 1562 Ox80000005 OxOOOe4d192.168.103.0 30.30.30.30 85 (DNA) Ox80000002 OxOOe60b192.168.104.0 4.4.4.4 491 Ox80000001 OxOOec6d192.168.105.0 5.5.5.5 608 Ox80000006 OxOOb996

Type-10 Opaque Link Area Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Opaque ID1.0.0.0 0.0.0.1 353 Ox800000e1 OxOOe55e 01.0.0.0 0.0.0.2 580 Ox800000e1 OxOOe859 01.0.0.0 10.7.1.1 619 Ox800000e1 Ox0084a6 01.0.0.0 10.100.100.100 671 Ox800000e1 Ox009570 01.0.0.4 10.100.100.100 670 Ox800000e6 Ox002a15 41.0.0.8 0.0.0.1 353 Ox800000e6 OxOOcdf9 81.0.0.9 10.7.1.1 1644 Ox800000e6 Ox005016 91.0.0.11 0.0.0.2 580 Ox800000e8 Ox006619 111.0.0.12 0.0.0.1 353 Ox800000e8 Ox004c2b 121.0.0.19 0.0.0.2 580 Ox800000e6 OxOOb94d 19


Link ID ADV Router Age Seq# Checksum Link count1.1.1.1 1.1.1.1 599 Ox80000001 OxOO1309 1


Link ID10.0.1.110.0.2.110.1.10.110.2.1.110.2.10.110.3.1.1


ADV Router1.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.1

Age589594573557518589

Seq#Ox80000002Ox80000001Ox80000001Ox80000001Ox80000001Ox80000002

ChecksumOxOOe544OxOOdc4dOx0078a8OxOOcf59Ox0076a8OxOOcb5a

Lab Guide 15

10.3.10.110.4.1.110.4.10.110.5.10.110.7.1.110.7.10.110.8.1.110.8.10.113.0.0.1192.168.2.0192.168.11.0192.168.12.0192.168.21.0192.168.22.0192.168.31.0192.168.32.0192.168.41.0192.168.42.0192.168.51.0192.168.52.0192.168.71.0192.168.82.0192.168.101. 0192.168.102.0192.168.103.0192.168.104.0192.168.105.0192.168.107.0192.168.108.0192.168.112.0192.168.134.0192.168.156.0

1.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.1

589589488589589589594594589594599599561594589589589594589589589594573557589488589589594567589589

Ox80000002 Ox0072a9Ox80000002 OxOOc95aOx80000001 Ox0072a8Ox80000002 Ox005abfOx80000002 OxOOf523Ox80000002 Ox009c72Ox80000001 OxOOeb2dOx80000001 Ox00927cOx80000002 OxOOdd48Ox80000001 OxOOc109Ox80000001 Ox004a79Ox80000001 Ox003f83Ox80000004 OxOOdfd5Ox80000001 OxOOdadcOx80000002 Ox007538Ox80000002 Ox007437Ox80000002 Ox001b86Ox80000001 OxOOfda5Ox80000002 Ox009801Ox80000002 Ox0097ffOx80000002 Ox001666Ox80000001 Ox00ged3Ox80000001 Ox006801Ox80000001 Ox0067ffOx80000002 Ox0064ffOx80000001 Ox0065fdOx80000002 Ox004e14Ox80000002 Ox0092c4Ox80000001 Ox0089cdOx80000003 OxOOea71Ox80000002 OxOOOe37Ox80000002 Ox001b14


Link ID1.1.1.110.10.10.10

ADV Router1.1.1.110.10.10.10

Age595574

Seq# Checksum Link countOx80000003 OxOOOb6a 1Ox80000003 Ox0008fd 2


Link ID192.168.101.11

ADV Router10.10.10.10

Age574

Seq# ChecksumOx80000001 Ox007e8d


Link ID10.0.1.110.0.2.110.1.1.110.2.1.110.2.10.110.3.1.110.3.10.110.4.1.110.4.10.110.5.10.110.7.1.110.7.10.110.8.1.110.8.10.113.0.0.1192.168.2.0192.168.11.0192.168.12.0192.168.21.0192.168.22.0192.168.31.0

ADV Router1.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.1

Age589594594557518589589589488589589589594594589594594594561594589

Seq#Ox80000002Ox80000003Ox80000002Ox80000006Ox80000001Ox80000002Ox80000002Ox80000002Ox80000001Ox80000002Ox80000003Ox80000002Ox80000003Ox80000003Ox80000002Ox80000002Ox80000004Ox80000004Ox80000006Ox80000003Ox80000002

ChecksumOxOOe544OxOOd84fOxOOcf5aOxOOc55eOx0076a8OxOOcb5aOx0072a9OxOOc95aOx0072a8Ox005abfOx00f324Ox009c72OxOOe72fOx008e7eOxOOdd48OxOObfOaOx00447cOx003986OxOOdbd7OxOOd6deOx007538


0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA

0 IA

192.168.32.0 1.1.1.1 589 Ox80000002 Ox007437192.168.41.0 1.1.1.1 589 Ox80000002 Ox001b86192.168.42.0 1.1.1.1 594 Ox80000003 OxOOf9a7192.168.51.0 1.1.1.1 589 Ox80000002 Ox009801192.168.52.0 1.1.1.1 589 Ox80000002 Ox0097ff192.168.71.0 1.1.1.1 589 Ox80000002 OxOO1666192.168.82.0 1.1.1.1 594 Ox80000003 Ox009ad5192.168.102.0 1.1.1.1 557 Ox80000001 Ox0067ff192.168.103.0 1.1.1.1 589 Ox80000002 Ox0064ff192.168.104.0 1.1.1.1 488 Ox80000001 Ox0065fd192.168.105.0 1.1.1.1 589 Ox80000002 Ox004e14192.168.107.0 1.1.1.1 589 Ox80000002 Ox0092c4192.168.108.0 1.1.1.1 594 Ox80000003 Ox0085cf192.168.112.0 1.1.1.1 567 Ox80000007 OxOOe275192.168.134.0 1.1.1.1 589 Ox80000002 OxOOOe37192.168.156.0 1.1.1.1 589 Ox80000002 Ox001b14

On the CE and PE routers, verify that OSPF routes are present in the IP routing table.Output on the CE router should be similar to the following:

CE1#show ip route ospfCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, 0 - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2ia - IS-IS inter area, * - candidate default, U - per-user static routeo - ODR, P - periodic downloaded static route, + - replicated route

Gateway of last resort is not set

10.0.0.0/32 is subnetted, 6 subnets10.0.1.1 [110/3] via 192.168.101.10, 00:04:52, GigabitEthernetO/O10.0.2.1 [110/3] via 192.168.101.10, 00:04:52, GigabitEthernetO/O10.1.1.1 [110/2] via 192.168.101.10, 00:04:52, GigabitEthernetO/O10.2.1.1 [110/3] via 192.168.101.10, 00:04:52, GigabitEthernetO/O10.2.10.1 [110/4] via 192.168.101.10, 00:04:52, GigabitEthernetO/O

192.168.1.0/24 [110/3] via 192.168.101.10, 00:04:52, GigabitEthernetO/O192.168.2.0/24 [110/3] via 192.168.101.10, 00:04:53, GigabitEthernetO/O192.168.11.0/24 [110/2] via 192.168.101.10, 00:04:53, GigabitEthernetO/O192.168.12.0/24 [110/2] via 192.168.101.10, 00:04:53, GigabitEthernetO/O192.168.21.0/24 [110/3] via 192.168.101.10, 00:04:53, GigabitEthernetO/O192.168.22.0/24 [110/3] via 192.168.101.10, 00:04:53, GigabitEthernetO/O192.168.31.0/24 [110/3] via 192.168.101.10, 00:04:53, GigabitEthernetO/O192.168.32.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.41.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.42.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.51.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.52.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.61.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.62.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.71.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.72.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.81.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.82.0/24 [110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.102.0/24

[110/3] via 192.168.101.10, 00:04:55, GigabitEthernetO/O192.168.112.0/24

[110/2] via 192.168.101.10, 00:04:56, GigabitEthernetO/O

Output on the PE router should be similar to the following:

RP/0/RSPO/CPUO:PE1#show route ospfThu Jun 8 02:19:25.000 UTC

o 10.0.1.1/32 [110/2] via 192.168.11.1, 01:01:08, GigabitEthernetO/0/0/2o 10.0.2.1/32 [110/2] via 192.168.12.2, 01:01:08, GigabitEthernetO/0/0/3o 10.1.10.1/32 [110/2] via 192.168.101.11, 01:01:01, GigabitEthernetO/O/O/O


o IA 10.2.1.1/32 [110/2] via 192.168.112.20, 00:59:51, GigabitEthernetO/0/0/1o IA 10.2.10.1/32 [110/3] via 192.168.112.20, 00:59:16, GigabitEthernetO/0/0/1o 192.168.1.0/24 [110/2] via 192.168.11.1, 01:01:08, GigabitEthernetO/0/0/2o 192.168.2.0/24 [110/2] via 192.168.11.1, 01:01:08, GigabitEthernetO/0/0/2o 192.168.21.0/24 [110/2] via 192.168.11.1, 00:59:53,GigabitEthernetO/0/0/2

[110/2] via 192.168.112.20, 00:59:53,GigabitEthernetO/0/0/1o 192.168.22.0/24 [110/2] via 192.168.12.2, 00:59:48,GigabitEthernetO/0/0/3

[110/2] via 192.168.112.20, 00:59:48,GigabitEthernetO/0/0/1o 192.168.31.0/24 [110/2] via 192.168.11.1, 01:01:08,GigabitEthernetO/0/0/2o 192.168.32.0/24 [110/2] via 192.168.12.2, 01:01:08,GigabitEthernetO/0/0/3o 192.168.41.0/24 [110/2] via 192.168.11.1, 01:01:08,GigabitEthernetO/0/0/2o 192.168.42.0/24 [110/2] via 192.168.12.2, 01:01:08,GigabitEthernetO/0/0/3o 192.168.51.0/24 [110/2] via 192.168.11.1, 01:01:08,GigabitEthernetO/0/0/2o 192.168.52.0/24 [110/2] via 192.168.12.2, 01:01:08,GigabitEthernetO/0/0/3o 192.168.61.0/24 [110/2] via 192.168.11.1, 01:01:08,GigabitEthernetO/0/0/2o 192.168.62.0/24 [110/2] via 192.168.12.2, 01:01:08,GigabitEthernetO/0/0/3o 192.168.71.0/24 [110/2] via 192.168.11.1, 01:01:08,GigabitEthernetO/0/0/2o 192.168.72.0/24 [110/2] via 192.168.12.2, 01:01:08,GigabitEthernetO/0/0/3o 192.168.81.0/24 [110/2] via 192.168.11.1, 01:01:08,GigabitEthernetO/0/0/2o 192.168.82.0/24 [110/2] via 192.168.12.2, 01:01:08,GigabitEthernetO/0/0/3o IA 192.168.102.0/24 [110/2] via 192.168.112.20, 00:59:16,GigabitEthernetO/0/0/1

Verify IPv4 connectivity between CE routers in your team. A ping from CE router in yourpod to the CE router in the other pod (same team) should be successful.

CE1#ping 10.2.10.1 (IP address of the CE2 router LoO interface)

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.2.10.1, timeout is 2 seconds:!!!! !Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

On the CE router in your pod, verify that these IPv6 protocols are running: OSPFv3neighbors and OSPFv3 database. There should be one OSPFv3 neighbor. The OSPFv3database should show LSAs from Area 1x, where "x" is your pod number. Outputs shouldbe similar to the following:

CE1#show ipv6 protocolsIPv6 Routing Protocol is "connected"IPv6 Routing Protocol is "ND"IPv6 Routing Protocol is "ospf 1"

Interfaces (Area 11) :LoopbackOGigabitEthernetO/O

Redistribution:None

CE1#show ipv6 ospf neighbor

Neighbor ID10.1.1.1

Pri1

StateFULL/BDR

Dead Time00:00:31

Interface ID7

InterfaceGiO/O


CE1#show ipv6 ospf database

OSPFv3 Router with ID (11.0.0.1) (Process ID 1)


ADV Router10.1.1.111.0.0.1

Age621619

Seq#Ox80000002Ox80000002

Fragment IDoo

Link count1

1

BitsBNone


ADV Router11.0.0.1

Age619

Seq#Ox80000001

Link ID2

Rtr count2

Inter Area Prefix Link States (Area 11)

ADV Router Age Seq# Prefix10.1.1.1 1228 Ox80000001 2001:DB8:10:0:1: :1/12810.1.1.1 1228 Ox80000001 2001:DB8:10:0:2: :1/12810.1.1.1 1228 Ox80000001 2001:DB8:10:1:1: :1/12810.1.1.1 987 Ox80000002 2001:DB8:10:2:1: :1/12810.1.1.1 723 Ox80000001 2001:DB8:10:2:10: :1/128

Link (Type- 8) Link States (Area 11)

ADV Router Age Seq# Link ID Interface10.1.1.1 1239 Ox80000001 7 GiO/O11.0.0.1 1293 Ox80000001 2 GiO/O

Intra Area Prefix Link States (Area 11)

ADV Router Age Seq# Link ID Ref-lstype Ref-LSID11.0.0.1 1315 Ox80000001 0 Ox2001 0

On the PE router in your pod, verify that these IPv6 protocols are running: OSPFv3neighbors and OSPFv3 database. There should be four OSPFv3 neighbors. The OSPFv3database should show LSAs from areas 0, x, and lx, where "x" is your pod number.Outputs should be similar to the following:

RP/0/RSPO/CPUO:PE1#show protocols ipv6% EIGRP: EIGRP not configuredRouting Protocol OSPFv3 1

Router Id: 10.1.1.1Distance: 110Graceful Restart: DisabledRedistribution:

NoneArea 0

GigabitEthernetO/0/0/3GigabitEthernetO/0/0/2GigabitEthernetO/0/0/1

Area 1LoopbackO

Area 11GigabitEthernetO/O/O/O

RP/0/RSPO/CPUO:PE1#show ospfv3 neighborNeighbors for OSPFv3 1

Neighbor ID Pri State10.1.10.1 1 FULL/DRGigabitEthernetO/O/O/O

Neighbor is up for 00:10:2110.2.1.1 1 FULL/DRGigabitEthernetO/0/0/1



Dead Time Interface ID Interface00:00:36 7

00:00:37 8

00:00:33 9

Lab Guide 19


Neighbor is up for 00:10:21

00:00:33 10

Total neighbor count: 4RP/0/RSPO/CPUO:PE1#show ospfv3 database



ADV Router Age Seq# Fragment ID Link count Bits10.0.1.1 625 Ox80000b87 0 5 None10.0.2.1 103 Ox80000b9c 0 7 None10.1.1.1 589 Ox80000003 0 3 B10.2.1.1 590 Ox80000003 0 3 B10.3.1.1 117 Ox80000004 0 3 B10.4.1.1 103 Ox80000003 0 2 B10.5.1.1 1815 Ox80000002 0 2 B10.100.100.100 933 Ox800003c8 0 1 None


ADV Router Age Seq# Link ID Rtr count10.0.1.1 642 Ox80000001 9 210.0.1.1 1114 Ox80000002 10 210.0.1.1 1820 Ox80000001 11 210.0.1.1 625 Ox80000001 13 210.0.2.1 927 Ox80000b7b 11 2RP/0/RSPO/CPUO:PE1(config-ospfv3-ar-if)#do show ospfv3 databaseTue Nov 15 19:20:01.918 UTC



ADV Router10.0.1.110.0.2.110.1.1.110.2.1.110.3.1.110.4.1.110.5.1.110.100.100.100

Age1048526101210135405262291356

Seq#Ox80000b87Ox80000b9cOx80000003Ox80000003Ox80000004Ox80000003Ox80000003Ox800003c8

Fragment IDoooooooo

Link count5

73

33

221

BitsNoneNoneBB

BB

BNone


ADV Router10.0.1.110.0.1.110.0.1.110.0.1.110.0.2.110.0.2.110.0.2.110.0.2.110.0.2.110.0.2.110.2.1.110.3.1.110.100.100.100

Age106515372931048135010691600361104852610135401356

Seq#Ox80000001Ox80000002Ox80000002Ox80000001Ox80000b7bOx80000001Ox80000002Ox80000002Ox80000001Ox80000001Ox80000001Ox80000001Ox800003be

Link ID91011131112131416179811

Rtr2222222222222

count


ADV Router10.1.1.110.1.1.1

Age10591023

Seq# PrefixOx80000001 2001:db8:10:1:1: :1/128Ox80000001 2001: db8: 10: 1: 10: : 1/128


10.2.1.110.2.1.110.3.1.110.3.1.110.4.1.110.4.1.110.4.1.110.4.1.110.5.1.110.5.1.1

1044100815451545536536466456229229

Ox80000001 2001:db8:10:2:1: :1/128Ox80000001 2001: db8: 10: 2: 10: : 1/128Ox80000002 2001:db8:10:3:1: :1/128Ox80000002 2001: db8: 10: 3: 10: : 1/128Ox80000002 2001:db8:10:4:1: :1/128Ox80000002 2001: db8: 192: 168: 104: : /80Ox80000001 2001: db8: 10: 4: 10: : 1/128Ox80000001 2001: db8: 192: 168: : /64Ox80000002 2001:db8:10:5:1: :1/128Ox80000002 2001: db8: 10: 5: 10: : 1/128

Link (Type-8) Link States (Area 0)

ADV Router10.1.1.110.2.1.110.0.1.110.1.1.110.0.2.110.1.1.1

Age1069105453410696021069

Seq#Ox80000001Ox80000001Ox80000002Ox80000001Ox80000002Ox80000001

Link ID899

91210

InterfaceGiO/0/0/1GiO/0/0/1GiO/0/0/2GiO/0/0/2GiO/0/0/3GiO/0/0/3


ADV Router Age Seq# Link ID Ref-lstype Ref-LSID10.0.1.1 793 Ox80000b84 0 Ox2001 010.0.2.1 1600 Ox80000ba3 0 Ox2001 010.0.2.1 526 Ox80000001 17408 Ox2002 1710.3.1.1 540 Ox80000001 8192 Ox2002 810.100.100.100 1356 Ox800003be 11264 Ox2002 11


ADV Router10.1.1.1

Age1069

Seq# Fragment IDOx80000001 0

Link counto

BitsB


ADV Router10.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.1

Age1059105910591059105910591059100810231007533523523523464454

Seq#Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000002Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001

Prefix2001:db8:192:168:82: :/802001:db8:10:0:1: :1/1282001:db8:10:0:2: :1/1282001:db8:10:5:10: :1/1282001:db8:10:5:1: :1/1282001:db8:10:3:10: :1/1282001:db8:10:3:1: :1/1282001:db8:10:2:1: :1/1282001:db8:10:1:10: :1/1282001:db8:10:2:10: :1/1282001:db8:192:168:134: :/802001:db8:192:168:41: :/802001:db8:10:4:1: :1/1282001:db8:192:168:104: :/802001:db8:10:4:10: :1/1282001:db8:192:168: :/64


ADV Router10.1.1.1

Age1069

Seq# Link IDOx80000001 0

Ref-lstypeOx2001

Ref-LSIDo


ADV Router10.1.1.110.1.10.1

Age10301031

Seq# Fragment IDOx80000002 0Ox80000002 0

Link count1

1

BitsB

None



Lab Guide 21

ADV Router10.1.10.1

Age1031


Rtr count2


ADV Router10.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.110.1.1.1

Age1059105910591059105910591059105910081007533523523523464454

Seq#Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000002Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001Ox80000001

Prefix2001:db8:192:168:82: :/802001:db8:10:0:1: :1/1282001:db8:10:0:2: :1/1282001:db8:10:1:1: :1/1282001:db8:10:5:10: :1/1282001:db8:10:5:1: :1/1282001:db8:10:3:10: :1/1282001:db8:10:3:1: :1/1282001:db8:10:2:1: :1/1282001:db8:10:2:10: :1/1282001:db8:192:168:134: :/802001:db8:192:168:41: :/802001:db8:10:4:1: :1/1282001:db8:192:168:104: :/802001:db8:10:4:10: :1/1282001:db8:192:168: :/64

Link (Type-8) Link States (Area 11)

ADV Router10.1.1.110.1.10.1

Age10691080

Seq# Link IDOx80000001 7Ox80000001 2

InterfaceGiO/O/O/OGiO/O/O/O


ADV Router10.1.10.1

Age1081


Ref-lstypeOx2001

Ref-LSIDo

On the CE and PE routers, verify that OSPFv3 routes are present in the IPv6 routing table.Output on the CE router should be similar to the following:

CE1#show ipv6 route ospfIPv6 Routing Table - default - 7 entriesCodes: C - Connected, L - Local, S - Static, U - Per-user Static route

B - BGP, R - RIP, 11 - ISIS L1, 12 - ISIS L2IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP externalND - Neighbor Discoveryo - OSPF Intra, 01 - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2

01 2001:DB8:10:0:1: :1/128 [110/2]via FE80: :4255:39FF:FE2E:C420, GigabitEthernetO/O





Output on the PE router should be similar to the following:

RP/0/RSPO/CPUO:PE1#show route ipv6 ospfo 2001:db8:10:0:1: :1/128

[110/1] via fe80: :4255:39ff:fe2e:d822, 00:26:58, GigabitEthernetO/0/0/2o 2001:db8:10:0:2: :1/128

[110/1] via fe80: :4255:39ff:fe2f:42da, 00:26:58, GigabitEthernetO/0/0/3o 2001:db8:10:1:10: :1/128

[110/1] via fe80: :eab7:48ff:fe2c:a180, 00:16:45, GigabitEthernetO/O/O/Oo IA 2001:db8:10:2:1: :1/128

[110/1] via fe80: :eab7:48ff:fefb:5801, 00:22:57, GigabitEthernetO/0/0/1o IA 2001:db8:10:2:10: :1/128


[110/2] via fe80: :eab7:48ff:fefb:5801, 00:18:32, GigabitEthernetO/0/0/1

Verify IPv6 connectivity between CE routers in your team. A ping from the CE router inyour pod to the CE router in the other pod (same team) should be successful.

CE1#ping 2001:DB8:10:2:10::1 (IPv6 address of the CE2 router LoO interface)

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 2001:DB8:10:2:10: :1, timeout is 2 seconds:!!!! !


Task 2: Influence OSPF DR and BDR ElectionIn this task, you will influence OSPF DR and BDR election on the LAN. On the LAN segmentbetween CE and PE routers, only the PE router will become DR-the CE router will neverbecome DR nor BDR. On the LAN segments between the PE router and the core routers, youwill influence DR and BDR election by changing the OSPF priority.

Activity Procedure

Complete these steps:

Step 1 On the CE router GiOIO interface, change the OSPF priority to the value that enablesthe PE router GiOIOIOIO interface to be DR.

Step 2 On the PE router GiOlOlO/2 and GiOlOlO/3 interfaces, change the OSPF priority to thevalue one higher than default.



On the PE router in your pod, verify the state of the GiOIOIO/o interface. The state should beDR.

RP/0/RSPO/CPUO:PE1#show ospf interface GigabitEthernet 0/0/0/0 I include StateTransmit Delay is 1 sec, State DR, Priority 1, MTU 1500, MaxPktSz 1500

On the PE router in your pod, verify the priority that the GiOlO/o/2 and GiOlOlO/3 interfaceshave. The priority should be 2.

RP/0/RSPO/CPUO:PE1#show ospf interface GigabitEthernet 0/0/0/2 I include StateTransmit Delay is 1 sec, State BDR, Priority 2, MTU 1500, MaxPktSz 1500

RP/0/RSPO/CPUO:PE1#show ospf interface GigabitEthernet 0/0/0/3 I include StateTransmit Delay is 1 sec, State BDR, Priority 2, MTU 1500, MaxPktSz 1500

If the state on the GiO/oIO/2 and GiO/O/O/3 interfaces is not DR, it should change when thecurrent DR will go down.

Task 3: Influence OSPF Route Selection by Changing OSPFLink Cost

In this task, you will change the OSPF link cost to influence the OSPF route selection. TheOSPF configured on the PE router in your pod selects the best route to the neighbor pod (sameteam) via a link that directly connects both pods. You will change the OSPF cost on the link tothe value that will make OSPF select the path via core devices.

Activity Procedure


Step 1 On the PE router, verify the route that is selected for prefixes from the neighbor pod.The OSPF selects a direct link between pods and does not use backbone routers.


RP/0/RSPO/CPUO:PE1#show route 10.2.1.1Routing entry for 10.2.1.1/32

Known via "ospf I", distance 110, metric 2, type inter areaInstalled Jun 8 01:19:33.142 for 01:51:13Routing Descriptor Blocks

192.168.112.20, from 2.2.2.2, via GigabitEthernetO/0/0/1Route metric is 2

No advertising protos.RP/0/RSPO/CPUO:PE1#show route 10.2.10.1Routing entry for 10.2.10.1/32

Known via "ospf I", distance 110, metric 3, type inter areaInstalled Jun 8 01:20:08.609 for 01:50:55Routing Descriptor Blocks


No advertising protos.

Step 2

Step 3

On the PE (Cisco lOS XR) router, change the OSPF link cost on the GiO/O/O/3 (toP2) to 3. On the PE (Cisco lOS XE) router, change the OSPF link cost on theGiO/O/2 (to PI) to 3.

On the PE routers in your team, change the OSPF link cost on the direct linkbetween pods to 10.



The PE router in your pod selects the best path to the prefixes in the neighbor pod via corerouters. The routing table on the PE (Cisco lOS XR) router shows the best path via the PIcore router:

RP/0/RSPO/CPUO:PE1#show route 10.2.1.1Routing entry for 10.2.1.1/32

Known via "ospf I", distance 110, metric 5, type inter areaInstalled Nov 15 19:43:15.469 for 00:01:47Routing Descriptor Blocks



No advertising protos.RP/0/RSPO/CPUO:PE1#show route 10.2.10.1Routing entry for 10.2.10.1/32

Known via "ospf I", distance 110, metric 6, type inter areaInstalled Nov 15 19:43:15.469 for 00:02:04Routing Descriptor Blocks



No advertising protos.

The routing table on the PE (Cisco lOS XE) router shows the best path via the P2 core router:

PE2#show ip route 10.1.1.1Routing entry for 10.1.1.1/32

Known via "ospf I", distance 110, metric 5, type inter areaLast update from 192.168.22.2 on GigabitEthernetO/0/3, 00:01:49 agoRouting Descriptor Blocks:

192.168.22.2, from 1.1.1.1, 00:01:49 ago, via GigabitEthernetO/0/3Route metric is 5, traffic share count is 1

* 192.168.21.1, from 1.1.1.1, 00:01:49 ago, via GigabitEthernetO/0/2Route metric is 5, traffic share count is 1

PE2#show ip route 10.1.10.1Routing entry for 10.1.10.1/32

Known via "ospf I", distance 110, metric 6, type inter area


Last update from 192.168.22.2 on GigabitEthernetO/0/3, 00:02:06 agoRouting Descriptor Blocks:

192.168.22.2, from 1.1.1.1, 00:02:06 ago, via GigabitEthernetO/0/3Route metric is 6, traffic share count is 1

* 192.168.21.1, from 1.1.1.1, 00:02:06 ago, via GigabitEthernetO/0/2Route metric is 6, traffic share count is 1

Trace between PE routers in your team shows the core routers in the path. Output on the PE(Cisco lOS XR) router should be similar to the following:

RP/0/RSPO/CPUO:PE1#traceroute 10.2.1.1Type escape sequence to abort.Tracing the route to 10.2.1.1

1 192.168.12.2 2 msec192.168.11.1 1 msec192.168.12.2 0 msec

2 192.168.21.20 0 msec192.168.22.20 0 msec *

Output on the PE (Cisco lOS XE) router should be similar to the following:

PE2#traceroute 10.1.1.1

Type escape sequence to abort.Tracing the route to 10.1.1.1VRF info: (vrf in name/id, vrf out name/id)

1 192.168.21.1 1 msec192.168.22.2 1 msec192.168.21.1 1 msec

2 192.168.12.10 40 msec192.168.11.10 1 msec192.168.12.10 1 msec

Task 4: Configure OSPF AuthenticationIn this task, you will configure OSPF authentication between routers in your pod.

Activity Procedure


Step 1 On the CE and PE routers, enable OSPF MD5 authentication. Use key number "1"and key string "cisco".



On the PE router in your pod, verify that OSPF neighbor to the CE router is up. Outputfrom the PE (Cisco lOS XR) router should be similar to the following:

RP/0/RSPO/CPUO:PE1#show ospf neighbor 10.10.10.10 I include StateNeighbor priority is 0, State is FULL, 6 state changes

Output from the PE (Cisco lOS XE) router should be similar to the following:

PE2#show ip ospf neighbor 20.20.20.20 I include StateNeighbor priority is 1, State is FULL, 6 state changes

On the PE router in your pod, verify that OSPF MD5 authentication is used on the interfacetoward the CE router. Output from the PE (Cisco lOS XR) router should be similar to thefollowing:

RP/0/RSPO/CPUO:PE1#show ospf interface GigabitEthernet 0/0/0/0GigabitEthernetO/O/O/O is up, line protocol is up

Internet Address 192.168.101.10/24, Area 11


Process ID 1, Router ID 1.1.1.1, Network Type BROADCAST, Cost: 1Transmit Delay is 1 sec, State DR, Priority 1, MTU 1500, MaxPktSz 1500Designated Router (ID) 1.1.1.1, Interface address 192.168.101.10No backup designated router on this networkTimer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

Hello due in 00:00:08Index 1/5, flood queue length 0Next 0(0)/0(0)Last flood scan length is 12, maximum is 27Last flood scan time is 0 msec, maximum is 0 msecLS Ack List: current length 0, high water mark 33Neighbor Count is 1, Adjacent neighbor count is 1

Adjacent with neighbor 10.10.10.10Suppress hello for 0 neighbor(s)Message digest authentication enabled

Youngest key id is 1Multi-area interface Count is 0

Output from the PE (Cisco lOS XE) router should be similar to the following:

PE2#show ip ospf interface GigabitEthernet 0/0/0GigabitEthernetO/O/O is up, line protocol is up

Internet Address 192.168.102.20/24, Area 12, Attached via Network StatementProcess ID 1, Router ID 2.2.2.2, Network Type BROADCAST, Cost: 1Topology-MTID Cost Disabled Shutdown Topology Name

o 1 no no BaseTransmit Delay is 1 sec, State BDR, Priority 1Designated Router (ID) 20.20.20.20, Interface address 192.168.102.21Backup Designated router (ID) 2.2.2.2, Interface address 192.168.102.20Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

oob-resync timeout 40Hello due in 00:00:05

Supports Link-local Signaling (LLS)Cisco NSF helper support enabledIETF NSF helper support enabledIndex 1/4, flood queue length 0Next OxO(O)/OxO(O)Last flood scan length is 14, maximum is 26Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1

Adjacent with neighbor 20.20.20.20 (Designated Router)Suppress hello for 0 neighbor(s)Message digest authentication enabled

Youngest key id is 1

Task 5: Configure OSPF Virtual LinksIn this task, you will configure an OSPF virtual link to connect the nonbackbone area to thebackbone area. For the purpose of this task, you will introduce another network on the CErouter and place this network into the OSPF nonbackbone area. To reach the newly introducednetwork, you will enable the OSPF virtual link between CE and PE routers.

Activity Procedure


Step 1

Step 2

Step 3

On the CE router, enable the Loopbacklx or Loopbackly interface and assign the IPaddress Ix.O.O.1/24 or ly.O.O.1/24, where x or y is your pod number.

On the CE router, include Loopbacklx or Loopbackly into the OSPF area xOO oryOO.

Configure the OSPF virtual link between CE and PE routers.




On the CE router in your pod, verify that the OSPF virtual link is running and OSPFadjacency is up on the virtual link.

InterfaceOSPF VL2GiO/O

Topology NameBase

Address192.168.101.10192.168.101.1000:00:31

Dead Time

CE1#show ip ospf virtual-linksVirtual Link OSPF VL2 to router 1.1.1.1 is up

Run as demand circuitDoNotAge LSA allowed.Transit area 11, via interface GigabitEthernetO/O

Topology-MTID Cost Disabled Shutdown01= =

Transmit Delay is 1 sec, State POINT_TO POINT,Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

Hello due in 00:00:00Adjacency State FULL (Hello suppressed)Index 1/2, retransmission queue length 0, number of retransmission 0First OxO(O)/OxO(O) Next OxO(O)/OxO(O)Last retransmission scan length is 0, maximum is 0Last retransmission scan time is 0 msec, maximum is 0 msec

CE1#show ip ospf neighborNeighbor ID Pri State1.1.1.1 0 FULL/1.1.1.1 1 FULL/DR

On the CE router in your pod, verify that the OSPF database has LSAs from Area O.

CE1#show ip ospf database



Link ID ADV Router Age Seq# Checksum Link count0.0.0.1 0.0.0.1 224 (DNA) Ox80000C15 OxOOF389 90.0.0.2 0.0.0.2 1141 (DNA) Ox80000COD OxOOA165 81.1.1.1 1.1.1.1 1 (DNA) Ox8000000C OxOO1717 42.2.2.2 2.2.2.2 2 (DNA) Ox80000007 Ox00862B 43.3.3.3 3.3.3.3 31 (DNA) Ox80000013 OxOOAA2F 44.4.4.4 4.4.4.4 31 (DNA) Ox80000007 OxOOB6DC 35.5.5.5 5.5.5.5 150 (DNA) Ox80000007 OxOOFBF9 310.7.1.1 10.7.1.1 1721 (DNA) Ox800003CD OxOOB922 310.7.10.1 10.7.10.1 383 (DNA) Ox800003C2 OxOOC60B 210.8.10.1 10.8.10.1 1263 (DNA) Ox800005CF OxOOCOE7 210.10.10.10 10.10.10.10 87 Ox80000002 Ox0023DD 110.100.100.100 10.100.100.100 1242 (DNA) Ox800003D4 Ox003317 320.20.20.20 20.20.20.20 3 (DNA) Ox80000002 OxOOE3BD 130.30.30.30 30.30.30.30 4 (DNA) Ox80000006 Ox009CA1 1


Link ID ADV Router Age Seq# Checksum192.168.2.2 0.0.0.2 1141 (DNA) Ox80000B7F OxOOBF7E192.168.11.1 0.0.0.1 1205 (DNA) Ox80000006 OxOO9623192.168.12.2 0.0.0.2 1141 (DNA) Ox80000006 Ox008530192.168.21.1 0.0.0.1 1205 (DNA) Ox80000004 Ox005E4F192.168.22.2 0.0.0.2 1141 (DNA) Ox80000004 Ox004D5C192.168.31.1 0.0.0.1 450 (DNA) Ox80000008 Ox001A81192.168.32.2 0.0.0.2 395 (DNA) Ox80000008 OxOO098E192.168.51.1 0.0.0.1 1205 (DNA) Ox80000005 OxOOA7DA192.168.52.2 0.0.0.2 1405 (DNA) Ox80000005 OxOO96E7192.168.71. 70 10.7.1.1 1721 (DNA) Ox800003BE OxOOE278192.168.82.80 10.100.100.100 1242 (DNA) Ox800003BC Ox0023DB192.168.107.70 10.7.1.1 1213 (DNA) Ox80000396 OxOOA2A1192.168.108.81 10.8.10.1 1263 (DNA) Ox800003B9 Ox005B8A192.168.112.10 1.1.1.1 1342 (DNA) Ox80000002 Ox001B2A192.168.134.40 4.4.4.4 31 (DNA) Ox80000001 Ox003BBA



Link ID10.1.1.110.1.10.110.1.10.110.2.1.110.2.10.110.2.10.110.3.1.110.3.10.110.3.10.110.4.1.110.4.10.110.5.10.110.5.10.111.0.0.112.0.0.113.0.0.1192.168.101. 0192.168.101. 0192.168.102.0192.168.102.0192.168.103.0192.168.103.0192.168.104.0192.168.105.0192.168.105.0

ADV Router1.1.1.11.1.1.110.10.10.102.2.2.22.2.2.220.20.20.203.3.3.33.3.3.330.30.30.304.4.4.44.4.4.45.5.5.550.50.50.5010.10.10.1020.20.20.2030.30.30.301.1.1.110.10.10.102.2.2.220.20.20.203.3.3.330.30.30.304.4.4.45.5.5.550.50.50.50

Age13421342113128312839296

5986140111397864114996603114128395986113911624

(DNA)(DNA)

(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)

(DNA)(DNA)(DNA)

(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)

Seq#Ox80000003Ox80000002Ox80000002Ox80000002Ox80000002Ox80000001Ox80000005Ox80000004Ox80000002Ox80000002Ox80000002Ox80000003Ox80000001Ox80000002Ox80000001Ox80000001Ox80000008Ox80000002Ox80000002Ox80000001Ox80000006Ox80000002Ox80000002Ox80000007Ox80000001

ChecksumOxOOCD5BOx0076A9Ox005D9FOxOOA57FOx004CCEOx0026AEOx0075A7Ox001EF5OxOOEABFOx0051C9OxOOF719OxOOCB3FOx007ADEOxOOCA3COx00924COx00585DOx005A08Ox0057ECOx003D26Ox0021FAOxOOOC4EOxOOE60BOxOOEA6EOxOOB797Ox007828

Type-10 Opaque Link Area Link States (Area 0)

Link ID1.0.0.01.0.0.01.0.0.01.0.0.01.0.0.41.0.0.81.0.0.91.0.0.111.0.0.121.0.0.19

ADV Router0.0.0.10.0.0.210.7.1.110.100.100.10010.100.100.1000.0.0.110.7.1.10.0.0.20.0.0.10.0.0.2

Age952114112131242124295220611419521141

(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)(DNA)

Seq#Ox800000E2Ox800000E2Ox800000E2Ox800000E2Ox800000E7Ox800000E7Ox800000E8Ox800000E9Ox800000E9Ox800000E7

Checksum Opaque IDOxOOE35F 0OxOOE65A 0Ox0082A7 0Ox009371 0Ox002816 4OxOOCBFA 8Ox004C18 9Ox00641A 11Ox004A2C 12OxOOB74E 19


Link ID1.1.1.110.10.10.10

ADV Router1.1.1.110.10.10.10

Age887110

Seq# Checksum Link countOx80000005 OxOOFC77 1Ox80000008 OxOOF606 2


Link ID192.168.101.10

ADV Router1.1.1.1

Age887

Seq# ChecksumOx80000001 Ox002809


Link ID10.0.1.110.0.2.110.1.1.110.2.1.110.2.10.110.3.1.110.3.10.110.4.1.110.4.10.110.5.10.110.7.1.110.7.10.110.8.1.1

ADV Router1.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.11.1.1.1

Age14537291453729729145417414014089514541454730

Seq#Ox80000003Ox80000006Ox80000003Ox80000008Ox80000003Ox80000003Ox80000001Ox80000001Ox80000001Ox80000003Ox80000004Ox80000003Ox80000006

ChecksumOxOOE345OxOOE63COxOOCD5BOxOODF3FOx009089OxOOC95BOx0074A8Ox0026F5OxOOCC45Ox0058COOxOOF125Ox009A73OxOOF51C


10.8.10.1 1.1.1.1 730 Ox80000006 Ox009C6B11.0.0.1 1.1.1.1 112 Ox80000001 OxOOE54511.0.0.1 10.10.10.10 127 Ox80000001 OxOOCC3B12.0.0.1 1.1.1.1 97 Ox80000001 OxOOO12513.0.0.1 1.1.1.1 168 Ox80000001 OxOODF47192.168.2.0 1.1.1.1 1454 Ox80000003 OxOOBDOB192.168.11.0 1.1.1.1 1454 Ox80000005 Ox00427D192.168.12.0 1.1.1.1 760 Ox80000006 Ox004972192.168.21.0 1.1.1.1 751 Ox80000008 OxOOEBC3192.168.22.0 1.1.1.1 731 Ox80000005 OxOOE6CA192.168.31.0 1.1.1.1 1455 Ox80000003 Ox007339192.168.32.0 1.1.1.1 558 Ox80000004 Ox008423192.168.41.0 1.1.1.1 1455 Ox80000003 OxOO1987192.168.42.0 1.1.1.1 731 Ox80000006 OxOO0894192.168.51.0 1.1.1.1 1455 Ox80000003 OxOO9602192.168.52.0 1.1.1.1 761 Ox80000004 OxOOA7EB192.168.61.0 1.1.1.1 337 Ox80000001 Ox00404E192.168.71.0 1.1.1.1 1455 Ox80000003 OxOO1467192.168.82.0 1.1.1.1 731 Ox80000006 OxOOA8C2192.168.102.0 1.1.1.1 731 Ox80000003 Ox0081EO192.168.103.0 1.1.1.1 219 Ox80000001 Ox0066FE192.168.104.0 1.1.1.1 142 Ox80000001 OxOOBF9A192.168.105.0 1.1.1.1 1455 Ox80000003 Ox004C15192.168.107.0 1.1.1.1 1456 Ox80000003 Ox0090C5192.168.108.0 1.1.1.1 732 Ox80000006 Ox0093BC192.168.112.0 1.1.1.1 695 Ox8000000A Ox003715192.168.134.0 1.1.1.1 141 Ox80000005 Ox0062D6192.168.156.0 1.1.1.1 192 Ox80000005 Ox006FB3


Link ID ADV Router Age Seq# Checksum Link count10.10.10.10 10.10.10.10 129 Ox80000002 Ox00587B 1


Link ID ADV Router Age Seq# Checksum10.0.1.1 10.10.10.10 110 Ox80000001 OxOOE22310.0.2.1 10.10.10.10 110 Ox80000001 OxOOEB1710.1.1.1 10.10.10.10 110 Ox80000001 OxOOCC3910.1.10.1 10.10.10.10 130 Ox80000001 Ox005F9E10.2.1.1 10.10.10.10 110 Ox80000001 OxOOE81810.2.10.1 10.10.10.10 110 Ox80000001 Ox008F6710.3.1.1 10.10.10.10 110 Ox80000001 OxOOC83910.3.10.1 10.10.10.10 110 Ox80000001 Ox006F8810.4.1.1 10.10.10.10 110 Ox80000001 Ox0021D510.4.10.1 10.10.10.10 110 Ox80000001 OxOOC72510.5.10.1 10.10.10.10 110 Ox80000001 Ox00579E10.7.1.1 10.10.10.10 110 Ox80000001 OxOOF20210.7.10.1 10.10.10.10 110 Ox80000001 Ox00995110.8.1.1 10.10.10.10 110 Ox80000001 OxOOFAF610.8.10.1 10.10.10.10 111 Ox80000001 OxOOA14612.0.0.1 10.10.10.10 95 Ox80000001 OxOOFB0513.0.0.1 10.10.10.10 111 Ox80000001 OxOODA27192.168.2.0 10.10.10.10 111 Ox80000001 OxOOBCE8192.168.11.0 10.10.10.10 111 Ox80000001 Ox004559192.168.12.0 10.10.10.10 111 Ox80000001 Ox004E4D192.168.21.0 10.10.10.10 111 Ox80000001 OxOOF49C192.168.22.0 10.10.10.10 112 Ox80000001 OxOOE9A6192.168.31.0 10.10.10.10 112 Ox80000001 Ox007217192.168.32.0 10.10.10.10 112 Ox80000001 Ox0085FF192.168.41.0 10.10.10.10 112 Ox80000001 OxOO1865192.168.42.0 10.10.10.10 112 Ox80000001 OxOOOD6F192.168.51.0 10.10.10.10 112 Ox80000001 Ox0095DF192.168.52.0 10.10.10.10 112 Ox80000001 OxOOA8C8192.168.61.0 10.10.10.10 112 Ox80000001 Ox003B2E192.168.71.0 10.10.10.10 112 Ox80000001 OxOO1345192.168.82.0 10.10.10.10 112 Ox80000001 OxOOAD9D


~

192.168.101. 0 10.10.10.10 132 Ox80000001 Ox0059EB192.168.102.0 10.10.10.10 112 Ox80000001 Ox0080BE192.168.103.0 10.10.10.10 112 Ox80000001 Ox0061DE192.168.104.0 10.10.10.10 112 Ox80000001 OxOOBA7A192.168.105.0 10.10.10.10 112 Ox80000001 Ox004BF2192.168.107.0 10.10.10.10 112 Ox80000001 Ox008FA3192.168.108.0 10.10.10.10 113 Ox80000001 Ox009897192.168.112.0 10.10.10.10 114 Ox80000001 Ox0044EB192.168.134.0 10.10.10.10 114 Ox80000001 Ox0065B2192.168.156.0 10.10.10.10 114 Ox80000001 Ox00728F

Verify IP connectivity from the PE router in your pod to the newly enabled Loopback IPaddress on the CE router in your pod.

RP/0/RSPO/CPUO:PE1#ping 11.0.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 11.0.0.1, timeout is 2 seconds:!!!! !Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms


Lab 2-2: Implement OSPF Special Area TypesComplete this lab activity to practice what you learned in the related module.

Activity ObjectiveIn this lab activity, you will configure OSPF summarization. You will configure thenonbackbone OSPF area to be a stub and totally stubby area. You will also adjust the cost ofthe injected default route on an ABR router.

Note Students from two different pods are working in team. The CE routers in both pods are

running Cisco lOS Software. The first pod in the team will work on the PE router running

Cisco lOS XR Software and the second pod in the same team will work on the PE router

running Cisco lOS XE Software. Students in the same team should coordinate their lab

activity.

In the lab activity, you will work on different Cisco routers running Cisco lOS (c2900), CiscolOS XE (asrlOOI), and Cisco lOS XR (asr9k) Software. After completing this activity, you willbe able to meet these objectives:

Summarize the subnets in the nonbackbone OSPF area

Configure the nonbackbone OSPF area to be a stub area

Configure the nonbackbone OSPF area to be a totally stubby area

Adjust the cost of the injected default route on an ABR router

Configure the nonbackbone OSPF area to be a totally NSSA

Visual ObjectiveThe figure illustrates what you will accomplish in this activity.

Teamz

C2012Ci'"""8rd'oritstrffili*'".A1lrigi'ts......".......


OSPFAreay

Lab Guide 31

OSPF AreasThis section includes a table with OSPF areas used in the lab. Replace the x or y with your podnumber to get the OSPF areas used in the lab.

Link OSPF area

P1 - P2

P1 and P2 LoopbackO

PEx- P1, PEy- P1 0

PEx - P2, PEy - P2

PEx - PEy

PEx LoopbackO, PEy LoopbackO x, y

CEx - PEx, CEy - PEy1x, 1y

CEx LoopbackO, CEy LoopbackO

CEx Loopback1x (1x.O.O.1/24), CEy xOO, yOOLoopback1y (1y.O.O.1/24)

Required ResourcesThese are the resources and equipment that are required to complete this activity:

A PC with access to the Internet

An SSH client installed on the PC


Command ListThe table describes the commands that are used in this lab activity.

Cisco 10SIIOS XE Commands

Command Description

[no] area area virtual-link IP-address (Router) Enables or disables OSPF virtual link

[no] network prefix wildcard_mask area (Router) Enables or disables OSPF routing on thearea network

area area default-cost cost (Router) Changes cost of the default route sent byABR into stub area

area area range prefix subnet-mask (Router) Summarizes prefixes from nonbackboneOSPF area to the backbone OSPF area

area area stublnssa [no-summary] (Router) Changes nonbackbone OSPF area intostub area or NSSA. Use the no-summary keywordto create totally stubby area or totally NSSA


match interface interface (Route-map) Creates a statement to match interfacein the route map

ping desC/P source [source_lp] Verifies connectivity between source IP anddestination IP

redistribute connected [subnets] [route- (Router) Redistributes connected routes into OSPF.map route-map] Use the keyword subnets to include subnets into

redistribution. Use the route-map keyword toredistribute with conditions

route-map name permitldeny Creates route-map sentence and enters route-mapconfiguration mode

router ospf process-id Enables OSPF proccess on the router

show ip ospf database Displays the content of the OSPF database

show ip route Displays the current routes in the routing table

summary-address prefix subnet-mask (Router) Summarizes external OSPF prefixes intoOSPF domain

Cisco IDS XR Commands

Command Description

[no] virtual-link IP-address (Router) Enables or disables OSPF virtual link

area area (Router) Creates OSPF area on the router

commit Commits changes to the running configuration


default-cost cost (Router) Changes cost of the default route sent byABR into stub area

ping desL/P source [source_lp] Verifies connectivity between source IP anddestination IP

range prefix/subnet-mask (Router) Summarizes prefixes from nonbackboneOSPF area to the backbone OSPF area

router ospf process-IO Creates an OSPF process


show ospf database

show route

stublnssa [no-summary]

Displays the content of the OSPF database

Displays the current routes in the routing table

(Router) Changes nonbackbone OSPF area intostub area or NSSA. Use the no-summary keywordto create totally stubby area or totally NSSA


Step 2

Step 1

Task 1: Enable OSPF SummarizationIn this task, you will enable OSPF summarization.

Activity Procedure


On the CE and PE routers, remove the OSPF virtual link configured in the previouslab activity, and, on the CE router, remove Loopbacklx or Loopbackly from theOSPF process.

On the CE router, redistribute Loopbacklx into the OSPF process. You will see thatthe external route appears in the PE router routing table.

On the PE router, you will see two OSPF routes from the CE router: LoopbackO andLoopbacklx or Loopbackly, where x or y is your pod number. The CE router LoopbackOnetwork is shown as intra-area OSPF route and Loopbacklx or Loopbackly network is shownas external OSPF route.

RP/0/RSPO/CPUO:PE1#show route ospfo 10.0.1.1/32 [110/2] via 192.168.11.1, 5d21h, GigabitEthernetO/0/0/2o 10.0.2.1/32 [110/3] via 192.168.11.1, 5d18h, GigabitEthernetO/0/0/2o 10.1.10.1/32 [110/2] via 192.168.101.11, 5d17h, GigabitEthernetO/O/O/Oo IA 10.2.1.1/32 [110/4] via 192.168.11.1, 5d18h, GigabitEthernetO/0/0/2o IA 10.2.10.1/32 [110/5] via 192.168.11.1, 00:13:38, GigabitEthernetO/0/0/2o E2 11.0.0.0/24 [110/20] via 192.168.101.11, 00:06:36, GigabitEthernetO/O/O/Oo E2 12.0.0.0/24 [110/20] via 192.168.11.1, 00:04:44, GigabitEthernetO/0/0/2< text omitted>

Step 3

Step 4

On the PE router, summarize the intra-area OSPF (CE LoopbackO interfacenetwork) route to the subnet mask 24.

On the CE router, summarize the external OSPF (CE Loopbacklx or Loopbacklyinterface network) route to the subnet mask 8.



On the PE router in your pod, verify the routing table. You will still see the intra-areaOSPF route from the CE router with subnet mask 32, because the PE router is ABR in thearea Ix or ly (x or y is your pod number). Additionally, you will see a route pointing to theNullO interface. The external OSPF route is shown with subnet mask 8. Outputs should besimilar to the following, taken from the PEl router:

RP/0/RSPO/CPUO:PE1#show route ospfo 10.0.1.1/32 [110/2] via 192.168.11.1, 5d21h, GigabitEthernetO/0/0/2o 10.0.2.1/32 [110/3] via 192.168.11.1, 5d18h, GigabitEthernetO/0/0/2o IA 10.1.10.0/24 [254/0] via 0.0.0.0, 00:02:26, NullOo 10.1.10.1/32 [110/2] via 192.168.101.11, 5d17h, GigabitEthernetO/O/O/Oo IA 10.2.1.1/32 [110/4] via 192.168.11.1, 5d18h, GigabitEthernetO/0/0/2o IA 10.2.10.0/24 [110/5] via 192.168.11.1, 00:02:31, GigabitEthernetO/0/0/2o E2 11.0.0.0/8 [110/20] via 192.168.101.11, 00:04:36, GigabitEthernetO/O/O/Oo E2 12.0.0.0/8 [110/20] via 192.168.11.1, 00:04:05, GigabitEthernetO/0/0/2< text omitted>

On the CE router in your pod, verify the routing table. You should see the CE routerLoopback interfaces networks from the neighbor pod (same team). The subnet mask of theLoopbackO is 24 and the subnet mask of the Loopback ly or Loopback Ix is 8 (y or x is theneighbor pod number). Outputs should be similar to the following:

CE1#show ip route ospfCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP


o IAo IAo IAo IAo IA



10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks10.0.1.1/32 [110/3] via 192.168.101.10, 00:25:08, GigabitEthernetO/O10.0.2.1/32 [110/4] via 192.168.101.10, 00:25:08, GigabitEthernetO/O10.1.1.1/32 [110/2] via 192.168.101.10, 00:25:08, GigabitEthernetO/O10.2.1.1/32 [110/5] via 192.168.101.10, 00:25:08, GigabitEthernetO/O10.2.10.0/24 [110/6] via 192.168.101.10, 00:09:43, GigabitEthernetO/O

11.0.0.0/8 is variably subnetted, 3 subnets, 3 maskso 11.0.0.0/8 is a summary, 00:11:48, NullOo E2 12.0.0.0/8 [110/20] via 192.168.101.10, 00:11:11, GigabitEthernetO/O< text omitted>

Task 2: Configure OSPF Stub AreaIn this task, you will configure the nonbackbone OSPF area to be a stub and totally stubby area.You will also adjust the cost of the injected default route on an ABR router. To get full IPreachability to the external routes, you will enable NSSA.

Activity Procedure


Step 1 On the CE router, examine the IP routing table, and you should see intra-area,interarea, and external OSPF routes. Output should be similar to the following, takenfrom the CEI router:

CE1#show ip routeCodes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP



0 IA0 IA0 IAC0 IA0 IA

0

CL0 E20 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA

10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks10.0.1.1/32 [110/3] via 192.168.101.10, 01:04:29, GigabitEthernetO/O10.0.2.1/32 [110/4] via 192.168.101.10, 01:04:29, GigabitEthernetO/O10.1.1.1/32 [110/2] via 192.168.101.10, 01:04:29, GigabitEthernetO/O10.1.10.1/32 is directly connected, LoopbackO10.2.1.1/32 [110/5] via 192.168.101.10, 01:04:29, GigabitEthernetO/O10.2.10.0/24 [110/6] via 192.168.101.10, 00:49:04, GigabitEthernetO/O

11.0.0.0/8 is variably subnetted, 3 subnets, 3 masks11.0.0.0/8 is a summary, 00:51:10, NullO11.0.0.0/24 is directly connected, Loopback1111.0.0.1/32 is directly connected, Loopback11

12.0.0.0/8 [110/20] via 192.168.101.10, 00:50:33, GigabitEthernetO/O192.168.1.0/24 [110/3] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.2.0/24 [110/4] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.11.0/24 [110/2] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.12.0/24 [110/4] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.21.0/24 [110/5] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.22.0/24 [110/4] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.31.0/24 [110/3] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.32.0/24 [110/6] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.41.0/24 [110/5] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.42.0/24 [110/4] via 192.168.101.10, 01:04:30, GigabitEthernetO/O


0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA

CL0 IA

0 IA

Step 2

Step 3

192.168.51.0/24 [110/3] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.52.0/24 [110/6] via 192.168.101.10, 01:04:30, GigabitEthernetO/O192.168.61.0/24 [110/5] via 192.168.101.10, 01:04:31, GigabitEthernetO/O192.168.62.0/24 [110/4] via 192.168.101.10, 01:04:31, GigabitEthernetO/O192.168.71.0/24 [110/3] via 192.168.101.10, 01:04:31, GigabitEthernetO/O192.168.72.0/24 [110/6] via 192.168.101.10, 01:04:31, GigabitEthernetO/O192.168.81.0/24 [110/5] via 192.168.101.10, 01:04:31, GigabitEthernetO/O192.168.82.0/24 [110/4] via 192.168.101.10, 01:04:31, GigabitEthernetO/O192.168.101.0/24 is variably subnetted, 2 subnets, 2 masks

192.168.101.0/24 is directly connected, GigabitEthernetO/O192.168.101.11/32 is directly connected, GigabitEthernetO/O

192.168.102.0/24[110/5] via 192.168.101.10, 01:04:32, GigabitEthernetO/O

192.168.112.0/24[110/11] via 192.168.101.10, 01:04:32, GigabitEthernetO/O

Configure an OSPF area between the CE and PE routers in your pod to be stub.

On the CE router, examine the IP routing table, and you should see intra-area andinterarea OSPF routes. There are no external OSPF routes in the routing table;instead, you should see a default route. Outputs should be similar to the following,taken from the CE1 router:



Gateway of last resort is 192.168.101.10 to network 0.0.0.0

O*IA

0 IA0 IA0 IAC0 IA0 IA

0

CL0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA0 IA

CL

0.0.0.0/0 [110/2] via 192.168.101.10, 00:00:02, GigabitEthernetO/O10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks

10.0.1.1/32 [110/3] via 192.168.101.10, 00:00:02, GigabitEthernetO/O10.0.2.1/32 [110/4] via 192.168.101.10, 00:00:02, GigabitEthernetO/O10.1.1.1/32 [110/2] via 192.168.101.10, 00:00:02, GigabitEthernetO/O10.1.10.1/32 is directly connected, LoopbackO10.2.1.1/32 [110/5] via 192.168.101.10, 00:00:02, GigabitEthernetO/O10.2.10.0/24 [110/6] via 192.168.101.10, 00:00:02, GigabitEthernetO/O

11.0.0.0/8 is variably subnetted, 3 subnets, 3 masks11.0.0.0/8 is a summary, 00:56:00, NullO11.0.0.0/24 is directly connected, Loopback1111.0.0.1/32 is directly connected, Loopback11

192.168.1.0/24 [110/3] via 192.168.101.10, 00:00:02, GigabitEthernetO/O192.168.2.0/24 [110/4] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.11.0/24 [110/2] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.12.0/24 [110/4] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.21.0/24 [110/5] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.22.0/24 [110/4] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.31.0/24 [110/3] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.32.0/24 [110/6] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.41.0/24 [110/5] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.42.0/24 [110/4] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.51.0/24 [110/3] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.52.0/24 [110/6] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.61.0/24 [110/5] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.62.0/24 [110/4] via 192.168.101.10, 00:00:04, GigabitEthernetO/O192.168.71.0/24 [110/3] via 192.168.101.10, 00:00:05, GigabitEthernetO/O192.168.72.0/24 [110/6] via 192.168.101.10, 00:00:05, GigabitEthernetO/O192.168.81.0/24 [110/5] via 192.168.101.10, 00:00:05, GigabitEthernetO/O192.168.82.0/24 [110/4] via 192.168.101.10, 00:00:05, GigabitEthernetO/O192.168.101.0/24 is variably subnetted, 2 subnets, 2 masks

192.168.101.0/24 is directly connected, GigabitEthernetO/O192.168.101.11/32 is directly connected, GigabitEthernetO/O


Step 8

o IA 192.168.102.0/24[110/5] via 192.168.101.10, 00:00:05, GigabitEthernetO/O

o IA 192.168.112.0/24[110/11] via 192.168.101.10, 00:00:05, GigabitEthernetO/O

Step 4 Configure an OSPF area between the CE and PE routers in your pod to be totallystubby.

Step 5 On the CE router, examine the IP routing table, and you should see only intra-areaOSPF routes. There are no interarea or external OSPF routes in the routing table;instead, you should see a default route. Output should be similar to the following,taken from the CEI router:



Gateway of last resort is 192.168.101.10 to network 0.0.0.0

O*IA 0.0.0.0/0 [110/2] via 192.168.101.10, 00:01:11, GigabitEthernetO/O10.0.0.0/32 is subnetted, 1 subnets

C 10.1.10.1 is directly connected, LoopbackO11.0.0.0/8 is variably subnetted, 3 subnets, 3 masks

o 11.0.0.0/8 is a summary, 01:01:45, NullOC 11.0.0.0/24 is directly connected, Loopback11L 11.0.0.1/32 is directly connected, Loopback11

192.168.101.0/24 is variably subnetted, 2 subnets, 2 masksC 192.168.101.0/24 is directly connected, GigabitEthernetO/OL 192.168.101.11/32 is directly connected, GigabitEthernetO/O

Step 6 On the PE router, adjust the OSPF cost of injected default route to 10.

Step 7 Examine the OSPF database on the CE router. There should be a summary LSA thatincludes a default route with metric 10. Output should be similar to the following,taken from the CE1 router:

CE1#show ip ospf database summary 0.0.0.0



Routing Bit Set on this LSA in topology Base with MTID 0LS age: 615Options: (No TOS-capability, DC, Upward)LS Type: Summary Links (Network)Link State ID: 0.0.0.0 (summary Network Number)Advertising Router: 1.1.1.1LS Seq Number: 80000003Checksum: OxE945Length: 28Network Mask: /0

MTID: 0 Metric: 10

Examine the OSPF default route metric on the CE router. The metric of the defaultroute is 11. Outputs should be similar to the following, taken from the CEI router:

CE1#show ip route 0.0.0.0Routing entry for 0.0.0.0/0, supernet

Known via "ospf 1", distance 110, metric 11, candidate default path, typeinter area

Last update from 192.168.101.10 on GigabitEthernetO/O, 00:11:56 ago


Routing Descriptor Blocks:* 192.168.101.10, from 1.1.1.1, 00:11:56 ago, via GigabitEthernetO/O

Route metric is 11, traffic share count is 1

Step 9 Because the OSPF area between the CE and PE routers is configured as stub, there isno IP reachability to the Loopbacklx or Loopbackly (x or y is your pod number).The stub area does not support an ASBR router inside the area. To get IPreachability, change the stub area into a totally NSSA. A totally NSSA allows anASBR router inside the area.



On the PE router in your pod, verify the OSPF database. There should be type 7 LSA,originated by the CE router. Type 7 LSA describes the CE Loopbacklx or Loopbacklynetwork

1 - Sproute 1.0 - Lab Guide

Documents

ospf summarizationtask

ospf authenticationtask

cisco logo

cisco website

influence ospf dr

list of cisco trademarks

influence ospf route

ospf link costtask