SLG BOOK ASR9KE v4.0.1 PDF

Cisco ASR 9000
Aggregation
Services Router
Series Essentials
Student Lab Guide
Version 4.0.1
Before You Begin
Conventions
This lab guide uses the following conventions:
boldface Commands and keywords are in boldface.
Example: Type show running config
Example: Use the name command.
brackets ([ ]) Indicates optional element. You can choose one of
the options.
Example: (config-if)# frame-relay lmi-type
{ansi|cisco|q933a}
italics font Arguments for which you supply values are in

italics.
Example: Open file ip tcp window-size bytes
angle brackets In contexts that do not allow italics, arguments are
(<>) enclosed in angle brackets [<>] Do not type the
brackets when entering the command.
Example: If the command syntax is ping
<ip_address>, you enter ping 192.32.10.12
string A non-quoted set of characters. Do not use

quotations marks around the characters, or the
string will include the quotations marks.
Example: (config)# hostname MyRouter
separator (>) Shows the menu path.

Example: Dialup > Backup Circuits identifies
the Backup Circuits option in the Dialup menu.
vertical line Indicates that you enter only one of the parts of the
(|) command. The vertical line separates choices. Do
not type the vertical line when entering the
command.
Example: If the command syntax is show ipv4
route|arp, you enter either show route or show
arp, but not both.
2011 Cisco Systems, Inc. Version 4.0.1 v

Contents
Before You Begin ................................................................................................................... v!
Overview ................................................................................................................................ 1!
Acronyms ............................................................................................................................... 2!
Accessing the Lab .................................................................................................................. 3!
Owner SDR Topology ............................................................................................................ 4!
CE Topology ........................................................................................................................... 5!
Addressing Tables ................................................................................................................. 6!
Accessing the Lab Tear out .............................................................................................. 10!
Owner SDR Topology Tear Out ....................................................................................... 11!
CE Topology Tear Out..................................................................................................... 12!
Configuration Examples ..................................................................................................... 13!
Lab 1 ................................................................................................................. 11!

Overview ............................................................................................................................ 11!
Lab References .................................................................................................................. 12!
Part 1 ! Hardware Environment ..................................................................................... 13!
Part 2 ! Initial Configuration .......................................................................................... 16!
Summary ......................................................................................................................... 110!
Lab 2 ................................................................................................................. 21!

Overview ............................................................................................................................ 21!
Lab References .................................................................................................................. 22!
Software Installation ........................................................................................................ 23!
Summary ........................................................................................................................... 29!
Lab 3 ................................................................................................................. 31!

Overview ............................................................................................................................ 31!
Lab References .................................................................................................................. 32!
Part 1 ! Commit and Rollback ......................................................................................... 33!
Part 2 ! Redundancy and Switchover ............................................................................. 36!
Part 3 ! Process Restartability ........................................................................................ 38!
Summary ......................................................................................................................... 310!
Lab 4 ................................................................................................................. 41!
vi Version 4.0.1 ASR 9000 Series Essentils

Overview ............................................................................................................................ 41!
Lab Reference .................................................................................................................... 42!
Part 1 Create a User Security Policy ........................................................................... 43!
Summary ........................................................................................................................... 47!
Lab 5 ................................................................................................................. 51!

Overview ............................................................................................................................ 51!
Lab Reference .................................................................................................................... 52!
Configuring IS-IS .............................................................................................................. 53!
Summary ........................................................................................................................... 56!
Lab 6 ................................................................................................................. 61!

Overview ............................................................................................................................ 61!
Lab Reference .................................................................................................................... 62!
Configuring OSPF ............................................................................................................. 63!
Summary ........................................................................................................................... 64!
Lab 7 ................................................................................................................. 71!

Overview ............................................................................................................................ 71!
Lab Reference .................................................................................................................... 72!
Configuring iBGP .............................................................................................................. 73!
Summary ........................................................................................................................... 75!
Lab 8 ................................................................................................................. 81!

Overview ............................................................................................................................ 81!
Lab Reference .................................................................................................................... 82!
Original Route Map ........................................................................................................... 83!
Part 1 ! Converting a Route Map .................................................................................... 85!
Part 2 ! Lab Resolution .................................................................................................... 88!
Summary ......................................................................................................................... 812!
Lab 9 ................................................................................................................. 91!

Overview ............................................................................................................................ 91!
Lab Reference .................................................................................................................... 92!
Configuring IPv4 Multicast Routing ................................................................................ 93!
Summary ........................................................................................................................... 94!
Lab 10 ............................................................................................................. 101!

Overview .......................................................................................................................... 101!
Lab References ................................................................................................................ 103!
2011 Cisco Systems, Inc. Version 4.0.1 vii

Part 1 Configuring MPLS LDP ................................................................................... 104!
Part 2 Configuring Dynamic Traffic Engineering Tunnels ....................................... 108!
Summary ....................................................................................................................... 1014!
Lab 11 ............................................................................................................. 111!

Overview .......................................................................................................................... 111!
Lab References ................................................................................................................ 113!
Configuring a Layer 3 VPN ............................................................................................ 114!
Summary ....................................................................................................................... 1111!
Lab 12 ............................................................................................................. 121!

Overview .......................................................................................................................... 121!
Lab References ................................................................................................................ 123!
Part 1 ! Link Bundles .................................................................................................... 124!
Local E-Line with EFPs .................................................................................................. 127!
Summary ....................................................................................................................... 1211!
Lab 13 ............................................................................................................. 131!

Overview .......................................................................................................................... 131!
Lab References ................................................................................................................ 133!
Part 1 ! Link Bundles .................................................................................................... 134!
Part 2 ! EoMPLS E-Line ................................................................................................ 137!
Part 3 ! EoMPLS with PW Backup ............................................................................. 1310!
Summary ....................................................................................................................... 1314!
Lab 14 ............................................................................................................. 141!

Overview .......................................................................................................................... 141!
Lab References ................................................................................................................ 143!
Part 1!Multipoint Local E-LAN .................................................................................... 144!
Summary ......................................................................................................................... 147!
Lab 15 ............................................................................................................. 151!

Overview .......................................................................................................................... 151!
Lab References ................................................................................................................ 153!
Part 1!Multipoint VPLS E-LAN .................................................................................... 154!
Part 2!Configuring VPLS with BGP-Autodiscovery .................................................... 157!
Summary ....................................................................................................................... 1512!
Lab 16 ............................................................................................................. 161!

Overview .......................................................................................................................... 161!
viii Version 4.0.1 ASR 9000 Series Essentils

Part 1! Local E-LAN with E-OAM on an Access Link ................................................. 163!
Part 2 ! VPLS E-LAN with CFM ................................................................................... 167!
Summary ....................................................................................................................... 1610!
Lab 17 ............................................................................................................. 171!

Overview .......................................................................................................................... 171!
Lab References ................................................................................................................ 173!
Part 1!Configuring IGMP Snooping Profiles ................................................................ 174!
Summary ......................................................................................................................... 176!
2011 Cisco Systems, Inc. Version 4.0.1 ix

This page intentionally left blank
x Version 4.0.1 ASR 9000 Series Essentils

Lab Aids
Overview
Description
This section of the lab guide is to be used as a reference when performing
the lab exercises.
There are three complete and separate lab networks. Two are located in
Boxborough, Massachusetts, Building 1. Students access either the
BXB01NIX4 School or the BXB01NIX5 School remotely through an
instructor-provided virtual private network VPN client device. There is
one lab in Research Triangle Park, North Carolina. Students access the
RTPNIX3 School remotely through a Secure Sockets Layer VPN (SSL
VPN) or through an instructor-provided VPN client device. Your instructor
will provide you the connectivity details to whichever of these three labs
your class is assigned this week.
The lab aids given here are meant to supplement the material provided in
the student guide and instructor presentation.
2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids -1

Lab Aids
Acronyms
The following acronyms may be used in the lab writeups. Additional
acronym definitions are provided at the end of this section.
Operation Administration and

ACL Access Control List OAM
Maintenance
ARP Address Resolution Protocol OSPF Open Shortest Path First
AS Autonomous System P Provider core router
ASR Aggregation Services Router PE Provider edge router
AC Attachment Circuit PIE Package Installation Envelope
BGP Border Gateway Protocol PIM Protocol Independent Multicast
Broadband Remote Access
BRAS PW Pseudowire
Server
Broadband Network
BNG QoS Quality of Service
Gateway
BD Bridge-domain RIB Routing Information Base
RP Rendezvous Point for PIM
CE Customer edge router RP Route Processor
BG Bridge-group RPL Routing Policy Language
EGP Exterior Gateway Protocol RSVP Resource Reservation Protocol
EFP Ethernet Flow Point TE Traffic Engineering
EoMPLS Ethernet over MPLS TFTP Trivial File Transfer Protocol
GMPLS Generalized MPLS VFI Virtual Forwarding Instance
H-VPLS Hierarchical VPLS VPN Virtual Private Network
Internet Group Management
IGMP
Protocol
IGP Interior Gateway Protocol VPLS Virtual Private LAN Service
Intermediate System-to-
IS-IS VRF VPN routing and forwarding
Intermediate System
IP Internet Protocol XC Cross-connect
Layer 3 Virtual Private
L3VPN
Network
LDP Label Distribution Protocol
MD5 Message Digest 5
Multiprotocol Label
MPLS
Switching
MST- Multiple Spanning Tree-
AG Access Gateway
NSF Nonstop Forwarding
NTP Network Time Protocol
Lab Aids - 2 Version 4.0.1 Cisco ASR 9000 Series Essentials

Accessing the Lab
Accessing the Lab

Laptops
Public
VPN VPN
Network
Client
Private Lab Network
Network
Terminal Se rv er
P PE
CE
Console connections
NOTE: each router has a menu
selection assigned for each RP
WEB Ser ve r
TFTP Serve r
OutofBand Management Netw ork

172.21.116.0/24
OutofBand Mgmt LAN supports: Telnet, TFTP, HTTP

TELNET to devices with thes e addre ss es
Device Mgmt Address Device Mgmt Address Device Mgmt Address

PE1 RSP0 172.21.116.10 PE5 RSP0 172.21.116.50 TERMINAL SERVER
RSP1 172.21.116.11 PE, P 172.21.116.7
RSP1 172.21.116.51
TERMINAL SERVER
VIP 172.21.116.12 VIP 172.21.116.52 CE 172.21.116.5
PE2 RSP0 172.21.116.20 PE6 RSP0 172.21.116.60 DEFAULT GATEWAY 172.21.116.1
RSP1 172.21.116.21 RSP1 172.21.116.61 TFTP SERVER 172.21.116.8
VIP 172.21.116.22 VIP 172.21.116.62
Device Mgmt Address Device Mgmt Address

PE3 RSP0 172.21.116.30 P1 RP0 172.21.116.110
RSP1 172.21.116.31 RP1 172.21.116.111
VIP 172.21.116.32 P2 RP0 172.21.116.120
PE4 RSP0 172.21.116.40 RP1 172.21.116.121
RSP1 172.21.116.41
VIP 172.21.116.42 Username = cisco
Password = lab
2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids - 3

Lab Aids
Owner SDR Topology

Pod 1 MgmtEth 0/RSP0/CPU0/0 MgmtEth 0/RSP0/CPU0/0 Pod 4
MgmtEth 0/0/CPU0/0
MgmtEth 0/RSP1/CPU0/0 MgmtEth 0/RSP1/CPU0/0
MgmtEth 0/1/CPU0/0
GE 0/2/0/ GE 2/0 1
1 GE 3/0 GE 0/2/0/
PE1 2 PE4
0/
G
GE 3/1
GE 2/1 P1 2/
E
0/
0/
MgmtEth 0/RSP0/CPU0/0 GE MgmtEth 0/RSP0/CPU0/0

2/
2/2 3/2 E
0/
G
GE
2

/2/0/1 GE 0
GE 4/0
GE 4/1
GE 0 /2/0/1
GE 2
Pod 2 PE2 0/2
0/2
/0/ PE5 Pod 5
/0/
2 GE
1 GE Pod 6
Pod 3
/ 2 /0/ 0/2
0 /0/
GE 1
PE3 GE
0/2/
0/2
GE 4/1
0/2
/0/2 PE6
GE 4/0
G
0
GE
3/
E
MgmtEth 0/RSP1/CPU0/0 2/ 1 MgmtEth 0/RSP1/CPU0/0

3/
E
2/
G
0
GE GE
2/2 3/2
GE
P2
MgmtEth 0/0/CPU0/0
MgmtEth 0/1/CPU0/0
MgmtEth RSP 0 17 2.21. 116. 10 MgmtEth RSP 0 17 2.21. 116. 40

MgmtEth RP 0 17 2.21.1 16.1 10
MgmtEth RP 1 17 2.21.1 16.1 11
10.1.1.1 .1 .4 10.4.4.4
192.168.111 10.11. 11.1 1 192.168.114
Pod 1
PE1 .11 .11 PE4 Pod 4
.1 .4
.11 .11
P1 192.168.115
192.168.112 .11 .11
Pod 2 10.2.2.2 .2 .5
Pod 5
10.5.5.5
.11 .11
PE2 192.168.113 192.168.116 PE5
.2 192.168.21 .5
Pod 3 192.168.12 10.6.6.6 Pod 6
10.3.3.3 .3 .6
192.168.121 192.168.124
PE3 .3
.12
.6
PE6
MgmtEth RSP 0 17 2.21. 116. 30 192.168.122 192.168.125 MgmtEth RSP 0 17 2.21. 116. 60
.12
MgmtEth RSP 1 17 2.21. 116. 31 .12 .12 .12 .12 MgmtEth RSP 1 17 2.21. 116. 61
192.168.123 192.168.126
.12 .12
10.12. 12.1 2
P2
MgmtEth RP 0 17 2.21.1 16.1 20
MgmtEth RP 1 17 2.21.1 16.1 21

CE Topology
CE Topology
MgmtEth RP 0 17 2.21.1 16.9 1 MgmtEth RP 0 17 2.21.1 16.9 4
CE1 P1 CE4
Pod 1 PE1 PE4 Pod 4
Pod 2 IP/MPLS Pod 5

CE2 Core CE5
PE5
MgmtEth RP 0 17 2.21.1 16. 9 2 PE2 MgmtEth RP 0 17 2.21.1 16.9 5
Pod 3 P2 Pod 6
CE3 PE6 CE6
PE3
Cisco ME3400 CEs
PE-CE physical connections are illustrated in each

lab module
Group to CE and PE Mapping Key
Group # PEa PEb PEc CEa CEb CEc
1 1 2 3 1 2 3
2 2 3 1 2 3 1
3 3 1 2 3 1 2
4 4 5 6 4 5 6
5 5 6 4 5 6 4
6 6 4 5 6 4 5
Use this table in conjunction with the lab diagrams to identify which PE
and CE devices your group will configure.

Lab Aids
Addressing Tables
Management Ethernet:
RSP0 MGMTETH RSP1 MGMTETH IP VIRTUAL

ROUTER
IP ADDRESS IP ADDRESS ADDRESS
P1 172.21.116.110/24 172.21.116.111/24 172.21.116.112/24
P2 172.21.116.120/24 172.21.116.121/24 172.21.116.122/24
PE1 172.21.116.10/24 172.21.116.11/24 172.21.116.12/24
PE2 172.21.116.20/24 172.21.116.21/24 172.21.116.22/24
PE3 172.21.116.30/24 172.21.116.31/24 172.21.116.32/24
PE4 172.21.116.40/24 172.21.116.41/24 172.21.116.42/24
PE5 172.21.116.50/24 172.21.116.51/24 172.21.116.52/24
PE6 172.21.116.60/24 172.21.116.61/24 172.21.116.62/24
ROUTER GE0 IP ADDRESS

CE1 172.21.116.91/24
CE2 172.21.116.92/24
CE3 172.21.116.93/24
CE4 172.21.116.94/24
CE5 172.21.116.95/24
CE6 172.21.116.96/24
Loopback:
LOOPBACK 0
ROUTER
IP ADDRESS
P1 10.11.11.11/32
P2 10.12.12.12/32
PE1 10.1.1.1/32
PE2 10.2.2.2/32
PE3 10.3.3.3/32
PE4 10.4.4.4/32
PE5 10.5.5.5/32
PE6 10.6.6.6/32

Addressing Tables
Gigabit Ethernet:
ROUTER INTERFACE IP ADDRESS

P1 GIGABITETHERNET 2/0 192.168.111.11/24
GIGABITETHERNET 2/1 192.168.112.11/24
P2 GIGABITETHERNET 2/0 192.168.121.12/24

Lab Aids
PE1 GIGABITETHERNET 0/2/0/1 192.168.111.1/24

GIGABITETHERNET 0/2/0/2 192.168.121.1/24

Addressing Tables
IS-IS NET (NSAP):
ROUTER NET (NSAP}
P1 49.0001.0000.0000.0011.00
P2 49.0001.0000.0000.0012.00
PE1 49.0001.0000.0000.0001.00
PE2 49.0001.0000.0000.0002.00
PE3 49.0001.0000.0000.0003.00
PE4 49.0001.0000.0000.0004.00
PE5 49.0001.0000.0000.0005.00
PE6 49.0001.0000.0000.0006.00

Lab Aids
Accessing the Lab Tear out

TEAR-OUT
Laptops
Public
VPN VPN
Network
Client
Private Lab Network
Network
Terminal Se rv er
P PE
CE
Console connections
NOTE: each router has a menu
selection assigned for each RP
WEB Ser ve r
TFTP Serve r
OutofBand Management Netw ork

172.21.116.0/24
OutofBand Mgmt LAN supports: Telnet, TFTP, HTTP

TELNET to devices with thes e addre ss es
Device Mgmt Address Device Mgmt Address Device Mgmt Address

PE1 RSP0 172.21.116.10 PE5 RSP0 172.21.116.50 TERMINAL SERVER
RSP1 172.21.116.11 PE, P 172.21.116.7
RSP1 172.21.116.51
TERMINAL SERVER
VIP 172.21.116.12 VIP 172.21.116.52 CE 172.21.116.5
PE2 RSP0 172.21.116.20 PE6 RSP0 172.21.116.60 DEFAULT GATEWAY 172.21.116.1
RSP1 172.21.116.21 RSP1 172.21.116.61 TFTP SERVER 172.21.116.8
VIP 172.21.116.22 VIP 172.21.116.62
Device Mgmt Address Device Mgmt Address

PE3 RSP0 172.21.116.30 P1 RP0 172.21.116.110
RSP1 172.21.116.31 RP1 172.21.116.111
VIP 172.21.116.32 P2 RP0 172.21.116.120
PE4 RSP0 172.21.116.40 RP1 172.21.116.121
RSP1 172.21.116.41
VIP 172.21.116.42 Username = cisco
Password = lab

Owner SDR Topology Tear Out
Owner SDR Topology Tear Out

TEAR-OUT
Pod 1 MgmtEth 0/RSP0/CPU0/0 MgmtEth 0/RSP0/CPU0/0 Pod 4
MgmtEth 0/0/CPU0/0
MgmtEth 0/1/CPU0/0
GE 0/2/0/ GE 2/0 1
1 GE 3/0 GE 0/2/0/
PE1 2 PE4
0/
G
GE 3/1
GE 2/1 P1 2/
E
0/
0/

2/
2/2 3/2 E
0/
G
GE
2

/2/0/1 GE 0
GE 4/0
GE 4/1
GE 0 /2/0/1
GE 2
Pod 2 PE2 0/2
0/2
/0/ PE5 Pod 5
/0/
2 GE
Pod 3 0/1 GE Pod 6
2 / 0/2
0/ /0/
GE 1
PE3 GE
0/2/
0/2 0/2
/0/2 PE6
GE 4/1
GE 4/0
G
0
GE
3/
E
MgmtEth 0/RSP1/CPU0/0 2/ 1 MgmtEth 0/RSP1/CPU0/0

3/
E
2/
G
0
GE GE
2/2 /2
G E3
P2
MgmtEth 0/0/CPU0/0
MgmtEth 0/1/CPU0/0

MgmtEth RP 0 17 2.21.1 16.1 10
MgmtEth RP 1 17 2.21.1 16.1 11
10.1.1.1 .1 .4 10.4.4.4
192.168.111 10.11. 11.1 1 192.168.114
Pod 1
PE1 .11 .11 PE4 Pod 4
.1 .4
.11 .11
P1 192.168.115
192.168.112 .11 .11
Pod 2 10.2.2.2 .2 .5
Pod 5
10.5.5.5
.11 .11
PE2 192.168.113 192.168.116 PE5
.2 192.168.21 .5
Pod 3 192.168.12 10.6.6.6 Pod 6
10.3.3.3 .3 .6
192.168.121 192.168.124
PE3 .3
.12
.6
PE6
MgmtEth RSP 0 17 2.21. 116. 30 192.168.122 192.168.125 MgmtEth RSP 0 17 2.21. 116. 60
.12
MgmtEth RSP 1 17 2.21. 116. 31 .12 .12 .12 .12 MgmtEth RSP 1 17 2.21. 116. 61
192.168.123 192.168.126
.12 .12
10.12. 12.1 2
P2
MgmtEth RP 0 17 2.21.1 16.1 20
MgmtEth RP 1 17 2.21.1 16.1 21

Lab Aids
CE Topology Tear Out

TEAR-OUT
CE1 P1 CE4
Pod 1 PE1 PE4 Pod 4
Pod 2 IP/MPLS Pod 5

CE2 Core CE5
PE5
MgmtEth RP 0 17 2.21.1 16. 9 2 PE2 MgmtEth RP 0 17 2.21.1 16.9 5
Pod 3 P2 Pod 6
CE3 PE6 CE6
PE3
Cisco ME3400 CEs
PE-CE physical connections are illustrated in each

lab module
Group to CE and PE Mapping Key
Group # PEa PEb PEc CEa CEb CEc
1 1 2 3 1 2 3
2 2 3 1 2 3 1
3 3 1 2 3 1 2
4 4 5 6 4 5 6
5 5 6 4 5 6 4
6 6 4 5 6 4 5
Use this table in conjunction with the lab diagrams to identify which PE
and CE devices your group will configure.

Configuration Examples
Configuration Examples
Base Router Configuration PE1_BASE
line console
exec-timeout 600 0
session-timeout 600
!
line default
exec-timeout 600 0
session-timeout 600
!
interface MgmtEth0/RSP0/CPU0/0
shutdown
shutdown
!
end
Initial Router Configuration PE1_INIT
hostname PE1
logging console informational
logging disabled
telnet vrf default ipv4 server max-servers 20
domain ipv4 host pe2 172.21.116.22
line console
exec-timeout 600 0
session-timeout 600
!
line default
exec-timeout 600 0
session-timeout 600
!
ipv4 virtual address 172.21.116.12 255.255.255.0
interface Loopback0
ipv4 address 10.1.1.1 255.255.255.255
!
ipv4 address 172.21.116.10 255.255.255.0

Lab Aids
!
shutdown
!
ipv4 address 172.21.116.11 255.255.255.0
!
shutdown
!
interface GigabitEthernet0/2/0/0
shutdown
!
ipv4 address 192.168.111.1 255.255.255.0
!
ipv4 address 192.168.121.1 255.255.255.0
!
router static
address-family ipv4 unicast
0.0.0.0/0 172.21.116.1
!
!
end

Cisco ASR 9000 Essentials Acronyms
!10 Gigabit Small Form Factor Pluggable Module (XFP)

!2-rate, 3-color (2R3C)
!Active Network Abstraction (ANA)
!Admin down (AD)
!Aggregation Services Routers (ASR)
!Alarm Cutoff (ACO)
!Application Programming Interfaces (APIs)
!Applications signal to the network that they require special QoS (IntServ)
!Asynchronous Transfer Mode (ATM)
!Attachment Circuit (AC)
!Attachment Circuits ( ACs)
!Base Station Controller (BSC)
!Bidirectional Forwarding Detection (BFD)
!Bidirectional PIM (Bidir-PIM)
!Bridge Domains (BDs)
!Bridge-Domain (BD)
!Broadband Network Gateway (BNG)
!Broadband Network Gateway (BNG)
!Broadband Remote Access Server (BRAS) PPPOATM
!Building Integrated Timing Supply ports (BITS)
!Call Admission Controls (CAC)
!Carrier Ethernet network (CEN)
!Circuit-Terminating Equipment (DCE)
!CiscoWorks QoS Policy Manager (QPM)
!Class of Service (CoS)
!Class-Based Weighted Fair Queueing (CBWFQ)
!Class-Based Weighted Fair Queuing (CBWFQ)
!Compact Flash (CF)
!Connected (CO)
2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids -15
Lab Aids
!Connectivity Fault Management (CFM)

!Connectivity Fault Management (CFM) 802.1ag
!Connectivity Verification (CV)
!Continuity Check Message (CCM)
!Continuity Check Protocol (CCP)
!Controller Area Network Bus (CANbus)
!cross-connects (xconnect)
!Customer Edge (CE)
!Customer VLAN (C-Vlan)
!Data Terminal Equipment (DTE)
!Deep Packet Inspection (DPI) Dual low-latency queues to enable both voice
and video services
!Deficit Weighted Round Robin (DWRR)
!Designated Shelf Controller (DSC)
!Differentiated Services Code Point (DSCP)
!DOWN MEP Outward-facing MEPs
!Dynamic Host Configuration Protocol (DHCP)
!End-to-End (E2E)
!Enterprise Resource Planning (ERP)
!Ethernet Access Domains (EAD)
!Ethernet Edge Hierarchical VPLS (EE-H-VPLS) QinQ tunnels
!Ethernet Flow Points (EFPs)
!Ethernet in the First Mile (EFM) 802.3ah Ethernet link OAM
!Ethernet Local Management Interface (E-LMI) MEF 16
!Ethernet Multipoint Service (EMS)
!Ethernet Out of band Communication (EoBC)
!Ethernet over MPLS (EoMPLS)
!Ethernet relay multipoint service (ERMS)
!Ethernet Relay Service (ERS)
!Ethernet to the home (ETTH)

!Ethernet Virtual Circuits (EVCs) / connections
!Ethernet Virtual Connection Service (EVCS)
!Ethernet Virtual Private Line (EVPL)
!Ethernet Wire Service (EWS)
!European Telecommunications Standards Institute (ETSI)
!Fabric Group ID (FGID)
!Fabric Port of Exit (FPOE)
!Fast Reroute (FRR)
!Field Programmable Gate Array (FPGA)
!Field-Replaceable Units (FRUs)
!First Customer Shipped (FCS)
!First Customer Shipped (FCS)
!Forwarding Equivalence Class (FEC)
!Hard Disk Drive (HDD)
!Hierarchical VPLS (H-VPLS)
!High Speed Internet (HSI)
!Hitless Software Upgrades (HSUs)
!Hot Standby Router Protocol (HSRP)
!In-Service Software Upgrade (ISSU)
!Internet Group Management Protocol (IGMP)
!Internet Group Management Protocol Versions 2 and 3 (IGMPv2/v3)
!Intra-Ethernet Access Domains (EAD)
!Label Edge Router (LER)
!Label Mapping Message (LMM)
!Layer 2 Control Protocol (L2CP)
!Layer 2 forwarding information base (L2FIB)
!Layer 2 Forwarding Information Base (L2FIB)
!Layer 2 Routing Information Base (L2RIB)

Lab Aids
!Link Aggregation (LAG)

!Link Aggregation Control Protocol (LACP)
!Link-Trace Message (LTM)
!Link-Trace Protocol (LTP)
!Link-Trace Reply (LTR)
!Local Up (LU)
!Loopback message (LBM)
!Loopback reply (LBR)
!Low-Latency Queueing (LLQ)
!Low-Latency Queuing (LLQ)
!Maintenance Association Identification (MAID)
!Maintenance Association/Service (MA)
!Maintenance Domain (MD)
!Maintenance Endpoint (MEP)
!Maintenance Intermediate Point (MIP)
!Maintenance Level (ML)
!Maintenance Points (MP)
!Mean Time To Recovery (MTTR)
!Metro Ethernet Forum (MEF)
!Metro Ethernet forum (MEF)
!Minimum Disruption Restart (MDR)
!Mobile Radio Access Network (RAN)
!Modular QoS CLI (MQC)
!Modular QoS Command-Line Interface (MQC)
!MPLS Edge Hierarchical VPLS (ME-H-VPLS) PWE3 Pseudo Wires
(EoMPLS)
!Multicast Forwarding Information Based (MFIB)
!Multicast Group ID (MGID)
!Multicast Group ID (MGID)
!Multicast Source Discovery Protocol (MSDP)

!Multiple Spanning Tree (MST)
!Multiple Spanning Tree (MST)
!Multiple Spanning Tree Protocol (MSTP)
!Multi-Point (MP)
!Multipoint-to-multipoint EVC (E-LAN)
!Multi-Protocol (MP)
!Multi-Protocol Label Switching (MPLS)
!Multi-Service Edge (MSE)
!Network Operations Center (NOC)
!Network Processor (NP-3c) Forwarding Engine
!Network Processor Unit (NPU)
!Network to Network Interface (NNI)
!Network-Based Application Recognition (NBAR)
!Network-Provider Edge (N-PE)
!Next-Generation Network (NGN)
!No QoS is applied to packets (Best-Effort)
!Node Point (NP)
!Non-Stop Forwarding (NSF)
!Non-Stop-Routing (NSR)
!Operating Expenses (OpEx)
!Operations Administration & Maintenance (OAM)
!Organizational Unique Identifier (OUI)
!Outgoing Interface Lists (OLIST)
!Packet Switched Network (PSN)
!Passive Optical Network (PON)
!Per-Hop Behaviors (PHB)
!PIM Source Specific Mode (PIM-SSM)
!Point of Load (POL)
!Point-to-point EVC (E-Line)
!Port Aggregation Protocol (PAgP)

Lab Aids
!Prefix Independent Convergence (PIC)

!Protocol Independent Multicast (PIM)
!Protocol Independent Multicast sparse mode (PIM-SM)
!Provider Edge (PE)
!Provider Edge (PE)
!Provider Edge aggregation (PE-agg)
!Pseudowire Header (PH)
!Pseudo-Wires (PWs)
!Remote Up (RU)
!Rendezvous Point (RP)
!Resource Reservation Protocol (RSVP)
!Reverse Layer 2 Gateway Protocol (R-L2GP)
!Rooted-multipoint EVC (E-Tree)
!Route-Switch Processor (RSP or RP)
!Routing Policy Language (RPL)
!Secure Domain Router (SDR)
!Service Provider VLAN (S-Vlan)
!Service-Level Agreements (SLAs)
!Single Mode Fiber (SMF)
!Source Specific Multicast (SSM)
!Sparse Mode (SM)
!Split-Horizon Group (SHG)
!Stateful Switch-Over (SSO)
!Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)
!Targeted Label Distribution Protocol (T-LDP)
!Technical Report (TR) eg. TR 101 which is DSL Form
!The network recognizes classes that require special QoS (DiffServ)
!Topology Change Notification (TCN)
!Traffic Engineering/Fast Reroute (TE-FRR)
!Transparent LAN Service (TLS)

!Tunnel Header (TH)
!Type of Service (ToS)
!Type, Length, Value (TLV)
!Unicast Reverse Path Forwarding (URPF)
!Unknown Unicast Flood Blocking (UUFB)
!UNRESOLVED (UR)
!UP MEP Inward-facing MEPs which can send CCM
!User to Network Interface (UNI)
!User-Network Interface (UNI)
!User-Provider Edge (U-PE)
!Virtual Circuit Connection Verification (VCCV)
!Virtual Circuit Connectivity Verification (VCCV)
!Virtual Forwarding Instance (VFI)
!Virtual Output Queue (VOQ) Scheduler = Arbiter=VOQ
!Virtual Private LAN Services (VPLS)
!Virtual Private Wire Services (VPWS)
!Virtual Router Redundancy Protocol (VRRP)
!Virtual Switch Instance (VSI)
!Virtual Switch Interface (VSI)
!Virtual Switching Instance (VSI)
!Weighted Fair Queueing (WFQ)
!Weighted Random Early Detection (WRED)
!Weighted Random Early Detection (WRED)

Lab 1
Hardware Discovery and Initial Configuration
Overview
Description
This exercise has two goals: (1) to familiarize you with the remote lab
hardware, and (2) to introduce the Cisco IOS XR configuration commands
used to do a basic configuration of your router. You will log in to your
router for the first time and use Cisco IOS XR commands to view the
hardware environment. You will establish the basic connectivity and
addressing necessary to create the lab network for the remainder of the
course.
Objectives
After completing this lab, you will be able to:
Display your routers hardware status and software version
information
Display RSP redundancy
Set routers date and time

Verify your routers running configuration
Enable and configure your Management Ethernet, virtual IP, and
loopback interfaces
Enable and configure all interfaces on your router

Configure IP addresses on all your routers interfaces
Test connectivity to neighbor routers in the lab
2011 Cisco Systems, Inc. Version 4.0.1 Lab 11

Hardware Discovery and Initial Configuration Lab 1
Lab References
Command list
In this laboratory exercise, refer to this list if you need command
assistance. Other commands not listed here may be needed to accomplish
the lab objectives.
address-family show clock

clock set show diag
commit show environment
config show ipv4 interface
domain ipv4 host show inventory
end show led
exit show platform
interface show process
ipv4 address show redundancy
ipv4 virtual address show route
logging console show running-config
no shut show version
router static
Lab 12 Version 4.0.1 Cisco ASR 9000 Series Essentials

Lab 1 Part 1 ! Hardware Environment
Part 1 ! Hardware Environment

The Cisco IOS XR commands in the following steps display necessary and
helpful information.
1. To connect to your assigned router, open a telnet terminal window to
the IP address of the Terminal Server shown in the Lab Aids, log in to
the terminal server and select your routers RSP0:
2. If not prompted by the router, press the Enter key to solicit a prompt.
Then log in to your router using the information in the Lab Aids.
If you do not receive a response from RSP0 or receive a message
indicating it is not the active RSP, disconnect and restart the terminal
server connection. Select RSP1 of your assigned router and notify your
instructor!
3. Display the hardware installed in your router by issuing the show
platform command and record your findings:
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
Verify that the GigabitEthernet hardware slot number(s) for your
router match the labs Owner SDR Topology in the Lab Aids, the
STATE is IOS XR RUN, and the CONFIG STATE is
PWR,NSHUT,MON. If not, notify your instructor.
4. Access administration EXEC mode and reenter the show platform
command. What additional information is displayed now?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
5. Exit administration EXEC mode.

6. Display and record the redundancy status of the RPs.

Node in Active role _______________________________________________
Partner node ____________________________________________________
Partner node role ________________________________________________
Standby node status _____________________________________________
! What command did you use? ___________________________________
! What other information is shown? ______________________________ .
If your nodes redundancy state does not look similar to the example
shown below, notify your instructor.
RP/0/RSP0/CPU0:PE1# show redundancy
Node 0/RSP0/CPU0 is in ACTIVE role
Partner node (0/RSP1/CPU0) is in STANDBY role
Standby node in 0/RSP1/CPU0 is ready
Standby node in 0/RSP1/CPU0 is NSR-ready
7. Display and review the detailed hardware information for all nodes
(locations) on the router, using the show diag command.
8. Display the hardware inventory, using the show inventory command.
9. Display the LED information for all slots.
! What message does your active RSP LED show? _________________

Lab 1 Part 1 ! Hardware Environment
10. Display the routers environmental information using the show

environment command.
! What type of environmental information is shown?
_____________________________________________________________
_____________________________________________________________

Part 2 ! Initial Configuration

In this section of the lab you will set up basic connectivity and addressing
necessary to connect the routers and be able to access the router remotely.
1. Display the running configuration and compare it with the Base Router
Configuration example in the Lab Aids. If it is not similar, notify your
instructor.
2. Check and set the current date and time.
! What command did you use to show and set the clock?
_____________________________________________________________
3. Using the tables provided in the Lab Aids, record youre Management
Ethernet and virtual IP addresses.
MgmtEth for RSP0 ______________________________________________
MgmtEth for RSP1 ______________________________________________
Virtual IP _______________________________________________________
4. Verify your router host name from the Lab Aids.
5. Configure the IP addresses for your Management Ethernet interfaces
and the virtual IP address.
! What command or commands did you use for your Management
Ethernet interfaces?
_____________________________________________________________
_____________________________________________________________
! What command did you use for the virtual IP address?
_____________________________________________________________
6. Management Ethernet interfaces are in a shutdown state by default;
you must perform a no shutdown command and commit the changes,
to enable them.
7. Remaining in global configuration mode, verify that the state of each
newly configured interface is up and that all interfaces are reachable.
! What command or commands did you use to display the state of
your interfaces?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_________________________ Note _________________________

Lab 1 Part 2 ! Initial Configuration
The virtual IP address is visible only in the routing table and ARP
cache.
______________________________________________________________
8. Using the Initial Router Configuration example in the Lab Aids,
configure and commit the domain names for each of the other routers
in the lab network. Use names with the form Px or PEx, where x is
the router number, and map the name to that routers virtual IP
address.
9. Ping your other routers domain names to make sure that they are all
up and working. If not working, investigate the cause with the affected
neighbor and fix it before continuing.
10. Configure each of the GigE interfaces with the appropriate IPv4
address information from the GigE Addressing tables found in the Lab
Aids.
! What commands did you use?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________

11. Verify that the GigE interfaces come up.

Did the interfaces come up? _____________________________________
! What command or commands did you use to verify the interfaces
activated?
_____________________________________________________________
_____________________________________________________________
If the interfaces do not come up ensure that both of you have issued a
no shutdown on each interface and committed the changes.
12. Ping your neighbors GigE interfaces to make sure that they are all up
and working. If not working, investigate the cause with the affected
neighbor and fix the problem before continuing.
__________________________ CAUTION _______________________
Do not continue until all required interfaces have come up.
__________________________________________________________________
13. Configure your Loopback0 interface with the IP address listed in the
Lab Aids.
! What command or commands did you use?
_____________________________________________________________
_____________________________________________________________
14. Configure a static default route to the default gateway listed in the Lab
Aids and commit the configuration.
! What commands did you use?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
Verify that your IP routing table contains routes to all the directly
connected GigE and MgmtEth networks, virtual IP and loopback
addresses, and static destinations.
15. Verify that you can successfully ping the default gateway and TFTP
server (refer to the Lab Aids for the address). If not, notify the
instructor.
16. In IOS XR all processes are off by default, including Telnet
functionality. Configure twenty telnet sessions by issuing the following
commands in configuration mode:
yty-pool default 0 99
telnet ipv4 server max-servers 20

Lab 1 Part 2 ! Initial Configuration
17. Enable logging output to the console to show all messages except
debugging messages.
! What command did you use?
_____________________________________________________________
17. Review the complete configuration (use the show running-config
command) and compare it with the Initial Router Configuration
example in the Lab Aids. Resolve any discrepancies before completing
the lab.
18. Verify that you can connect to your assigned router by opening a
browser window to the Web Server address shown in the Lab Aids.
Select your routers RP0 icon on the Web page and a telnet window will
open for a console session. Inform your instructor if this does not
happen.

Summary
Hardware Discovery and Initial Configuration and Initial Configuration
In this lab you learned to:
Display your routers hardware status and software version
information
Display RSP redundancy
Set routers date and time

Verify your routers running configuration
Enable and configure your Management Ethernet, virtual IP, and
loopback interfaces
Enable and configure all interfaces on your router
Configure IP addresses on all your routers interfaces
Test connectivity to neighbor routers in the lab
This completes the lab.

!
monitor event-trace rlc all enable
!
ip subnet-zero
no ip icmp rate-limit unreachable
ip cef table hardware resource-failure action punt
no ip domain-lookup
ip multicast-routing distributed
mpls label protocol ldp
mpls ldp graceful-restart
mpls traffic-eng tunnels
mpls traffic-eng logging tunnel path change
mpls oam
echo revision 3
tag-switching tdp discovery hello interval 15
tag-switching tdp discovery hello holdtime 30
!
controller E1 0/0
shutdown
!
controller T1 0/1
shutdown
!
interface Loopback0
ip address 10.11.11.11 255.255.255.255
no ip directed-broadcast
ip pim sparse-mode
ip router isis lab
no ip route-cache

Lab 1 Summary
no ip mroute-cache
!
interface GigabitEthernet2/0
description *PE1*
ip address 192.168.111.11 255.255.255.0
ip pim dense-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE2*
ip address 192.168.112.11 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
!
description *PE3*
ip address 192.168.113.11 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE4*
ip address 192.168.114.11 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE5*
ip address 192.168.115.11 255.255.255.0
ip pim dense-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE6*
ip address 192.168.116.11 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *P2*
ip address 192.168.21.11 255.255.255.0
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *P2*
ip address 192.168.12.11 255.255.255.0
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
no ip address
shutdown
no negotiation auto
!
interface Ethernet0
description *Mgmt LAN*
ip address 172.21.116.110 255.255.255.0
no ip route-cache
no ip mroute-cache
!
interface Ethernet1
no ip address
no ip route-cache
no ip mroute-cache
shutdown
!
interface Ethernet2
no ip address
Lab 1 Summary
no ip route-cache
no ip mroute-cache
shutdown
!
router ospf 1
router-id 10.11.11.11
log-adjacency-changes
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0
network 10.0.0.0 0.255.255.255 area 0
network 192.168.111.0 0.0.0.255 area 0
network 192.168.112.0 0.0.0.255 area 0
network 192.168.113.0 0.0.0.255 area 0
network 192.168.114.0 0.0.0.255 area 0
network 192.168.115.0 0.0.0.255 area 0
network 192.168.116.0 0.0.0.255 area 0
network 192.168.0.0 0.0.255.255 area 0
distance 116
!
router isis lab
net 49.0001.0000.0000.0011.00
is-type level-1
metric-style wide
nsf ietf
mpls traffic-eng level-1
!
router bgp 65000
bgp router-id 10.11.11.11
bgp log-neighbor-changes
neighbor 10.1.1.1 remote-as 65000
neighbor 10.12.12.12 update-source Loopback0
!
address-family ipv4
neighbor 10.1.1.1 activate
no auto-summary
no synchronization
network 10.11.11.11 mask 255.255.255.255
exit-address-family
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.21.116.1
!
ip pim send-rp-announce Loopback0 scope 3
ip pim send-rp-discovery Loopback0 scope 3

!
!
!
tag-switching tdp router-id Loopback0
control-plane
!
!
line con 0
session-timeout 1200
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
password lab
login
line vty 5 50
exec-timeout 0 0
password lab
login
!
exception warmstart 60 5
no cns aaa enable
end
upgrade fpd auto

version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service internal
service download-fl
!
hostname P2
!
boot-start-marker
boot system disk0:c12kprp-p-mz.120-32.SY3
boot bootldr bootflash:c12kprp-boot-mz.120-32.S3.bin
boot-end-marker
!
!
redundancy
mode rpr
no logging console
enable password lab
!
monitor event-trace rlc all enable
!
!
!
ip subnet-zero
Lab 1 Summary
no ip icmp rate-limit unreachable

ip cef table hardware resource-failure action punt
no ip domain-lookup
mpls label protocol ldp
mpls ldp graceful-restart
mpls traffic-eng logging tunnel path change
mpls oam
echo revision 3
tag-switching tdp discovery hello interval 15
tag-switching tdp discovery hello holdtime 30
!
controller E1 0/0
shutdown
!
controller T1 0/1
shutdown
!
!
interface Loopback0
ip address 10.12.12.12 255.255.255.255
ip pim sparse-mode
ip router isis lab
no ip route-cache
no ip mroute-cache
!
description *PE1*
ip address 192.168.121.12 255.255.255.0
ip pim dense-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE2*
ip address 192.168.122.12 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE3*
ip address 192.168.123.12 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE4*
ip address 192.168.124.12 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE5*
ip address 192.168.125.12 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *PE6*
ip address 192.168.126.12 255.255.255.0
ip pim sparse-mode
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *P1*
ip address 192.168.12.12 255.255.255.0
ip router isis lab
no negotiation auto
tag-switching ip
ip rsvp bandwidth
!
description *P1*
ip address 192.168.21.12 255.255.255.0
ip router isis lab
no negotiation auto
tag-switching ip
Lab 1 Summary
ip rsvp bandwidth
!
no ip address
shutdown
no negotiation auto
!
interface Ethernet0
description *Mgmt LAN*
ip address 172.21.116.120 255.255.255.0
no ip route-cache
no ip mroute-cache
!
interface Ethernet1
no ip address
no ip route-cache
no ip mroute-cache
shutdown
!
interface Ethernet2
no ip address
no ip route-cache
no ip mroute-cache
shutdown
!
!
router ospf 1
router-id 10.12.12.12
log-adjacency-changes
mpls traffic-eng area 0
network 10.0.0.0 0.255.255.255 area 0
network 192.168.121.0 0.0.0.255 area 0
network 192.168.122.0 0.0.0.255 area 0
network 192.168.123.0 0.0.0.255 area 0
network 192.168.124.0 0.0.0.255 area 0
network 192.168.125.0 0.0.0.255 area 0
network 192.168.126.0 0.0.0.255 area 0
network 192.168.0.0 0.0.255.255 area 0
distance 116
!
router isis lab
net 49.0001.0000.0000.0012.00
is-type level-1
metric-style wide
nsf ietf
mpls traffic-eng level-1
!
router bgp 65000
bgp router-id 10.12.12.12
bgp log-neighbor-changes

neighbor 10.11.11.11 update-source Loopback0
!
address-family ipv4
no auto-summary
no synchronization
network 10.12.12.12 mask 255.255.255.255
exit-address-family
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.21.116.1
!
ip pim send-rp-announce Loopback0 scope 3
ip pim send-rp-discovery Loopback0 scope 3
!
!
!
tag-switching tdp router-id Loopback0
control-plane
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
password lab
login
line vty 5 50
exec-timeout 0 0
password lab
login
!
exception warmstart 60 5
no cns aaa enable
end
!

Lab 1 Summary
This page was intentionally left blank.

Lab 2
Cisco IOS XR Software Installation
Overview
Description
The goal of this lab exercise is for you to use Cisco IOS XR software installation
commands to add, activate, deactivate, and remove various types of software
packages. You will review and verify the results.
Objectives
Perform an installation of a new software packages to add additional
features
Activate and deactivate additional software packages

Test to ensure that software packages are correctly installed and functioning

Cisco IOS XR Software Installation Lab 2
Lab References
Command List
In this lab exercise, refer to this list if you need command assistance.
clock set show clock
dir disk0: show install active
install activate show install commit
install add show install inactive
install commit show install log
install deactivate show install pie-info
install remove show install requests
install rollback show install rollback
show platform
show version
Software Packages
Cisco XR 12000 files on TFTP server Cisco ASR 9000 files on TFTP server
Manageability c12k-mgbl.pie-4.0.1 Multicast asr9k-mcast-p.pie-4.0.1

MPLS c12k-mpls.pie-4.0.1 MPLS asr9k-mpls-p.pie-4.0.1
Documentation c12k-doc.pie-4.0.1 Documentation asr9k-doc-p.pie-4.0.1
Diagnostics c12k-diags.pie-4.0.1 Manageability asr9k-mgbl-p.pie-4.0.1
Cisco CRS-1 files on TFTP server
Manageability hfr-mgbl-p.pie-4.0.1
MPLS hfr-mpls-p.pie-4.0.1
Documentation hfr-doc.pie-4.0.1
Diagnostics hfr-diags-p.pie-4.0.1

Lab 2 Software Installation
Software Installation
Pre-installation checks
1. Check the version of Cisco IOS XR software running on your router.
! Which command did you use? _________________________________
! What is the boot disk? ________________________________________
2. Check the date and time on your router.
! Which command did you use? _________________________________
3. Set the time to match the current date and local time.
! Which command did you use?
_____________________________________________________________
Adding Feature Packages using the One-step Method

In this part of the lab, you will add four software packages called package
installation envelope (PIEs). Each PIE will be installed and activated in Admin
EXEC mode using the one-step method.
_____________________________ Note _________________________
The PIE files are located on the TFTP server (172.21.116.8) under the folder
/4.0.1/ (ex. tftp://172.21.116.8/4.0.1/asr9k-mcast-p.pie-4.0.1).
The following approach adds and activates individual PIEs using a single
command. You have the option to add and/or activate multiple PIEs
simultaneously or individually, as desired.
__________________________________________________________________
Enter global configuration mode and attempt to enter multicast-routing
command.
! Were you able to enter the multicast-routing command?
_____________________________________________________________
1. Enter Admin EXEC mode.
__________________________ Note _________________________
The following install [add | activate | commit | pie-info] commands
will be executed only from the owner SDR ADMIN EXEC mode.
______________________________________________________________
2. View and verify the detail information on the Multicast PIE file located on
the TFTP server.

_____________________________________________________________
_____________________________________________________________
_______________________________________________________________
Hint: Dont forget the TFTP server address and file path (if necessary).
Note the cards supported by the software packages.
3. Install and activate the Multicast package from the TFTP server using one
command.
_____________________________________________________________ .
_____________________________________________________________
______________________________________________________________
4. After the installation add step above is complete, reenter global
configuration mode and determine if you can now enter the multicast-
router command.
! Were you able to enter the multicast-routing command now?____
! Why? ________________________________________________________
5. Use the show install log reverse command to display information logged
about the installation activation. x is the request (transaction) ID assigned
to the command.
6. Now add and activate the MPLS and Documentation PIEs from Admin
EXEC mode.
! What command did you use to install and activate the MPLS PIE?
_____________________________________________________________

7. While this package installation is running, enter the show install requests
command.
! What does this command tell you about your installation request?
_____________________________________________________________
_____________________________________________________________
8. Allow the process to finish and then enter the show install active and
show install committed commands.
! Identify the differences you observe.
_____________________________________________________________
_____________________________________________________________
Notice that the active software list now contains the three PIEs you just
added and activated, but the committed software list does not. If the entire
system reloaded right now (say, due to a complete power failure), the router
would come up without the software features you loaded, because they were
not committed. Therefore, after any software package installation, test to see
if the system is behaving properly and then commit the new software.
9. Now that you have verified that the Multicast, MPLS, and Documentation
packages are installed and working correctly, commit the installation so that
it will activate on any subsequent router reload.

10. Now install and activate the Manageability PIE from Admin EXEC mode.
_____________________________________________________________
11. Allow the process to finish and then enter the show install active and
show install committed commands.
! Identify the differences you observe.
_____________________________________________________________
_____________________________________________________________
12. Now that you have verified that the Multicast, MPLS, Documentation and
Manageability PIEs are installed and working correctly, commit the
installation so that it will activate on any subsequent router reload.
Deactivating Feature Packages

In this part of the lab you will deactivate the optional Manageability feature
package on the router.
____________________________ Note _________________________
The Manageability PIE adds CORBA agent, XML Parser, and HTTP server
features that are not used in this course.
__________________________________________________________________
1. From administrative EXEC mode, deactivate the Manageabilty package.
_____________________________________________________________
! How would you verify that the package is deactivated?
_____________________________________________________________
! Are the Manageability package files gone? ______________________
! How do you check? ____________________________________________

Enter the command to remove the Manageability package.

! What is the command? ________________________________________
_____________________________________________________________
! Did this command work? ______________________________________
The system does not allow the removal of the Manageabilty package at this
point, even though it is deactivated because it is still part of the committed
software.
2. Enter the show install committed command.
Notice that the Manageability package is still listed as committed (meaning
that it will become active the next time the router boots) even though it is
not currently active.
3. Issue the install commit command.
! Are the files gone now? ________________________________________
4. Test the removal of the Manageability package but DO NOT REMOVE THE
PACKAGE!
! What command(s) did you use?
_____________________________________________________________
! Read the messages carefully. Will it be possible to roll back the
Manageability package if you execute an install remove command?
_____________________________________________________________
If not, why not? ______________________________________________

Challenge Questions
! At which stage does the software certification check occur, during the
add or activate step? _________________________________________
! At which stage does API compatibility check occur, during the add or
activate step? ________________________________________________
! If there were a package that was disruptive (it impacted forwarding for
example), at what stage would this occur, during the add or activate
step? _________________________________________________________
! When removing a package, why is it necessary to enter the install
commit command after deactivating the package?
_____________________________________________________________
! If you wanted to return to the last committed state of the installed
software, what two methods could you use?
_____________________________________________________________
_____________________________________________________________

Lab 2 Summary
Summary
Cisco IOS XR Software Installation
In this lab, you learned to:
Perform an installation of a new software package to add additional features

Activate and deactivate additional software packages
Test to ensure that software packages are correctly installed and functioning

Lab 3
Cisco IOS XR Operations
Overview
Description
The goal of this exercise is to familiarize you with various operational
features unique to Cisco IOS XR software. You will commit configuration
changes and roll them back. You will configure RSP redundancy and force
a switchover. You will stop and restart processes and make observations
about all these tasks.
Objectives
Commit configurations using available options
Read the configuration history and rollback logs

Perform a configuration rollback that restores an old configuration
Configure redundancy and perform a switchover
Observe processes checkpointed on secondary RSP
Stop processes and observe continued software operation
Restart processes independent of other router functions

Cisco IOS XR Operations Lab 3
Lab References
Command List
In this laboratory exercise, you will use the following commands. Refer to
this list if you need command assistance. Other commands not listed here
may be needed to accomplish the lab configurations.
commit [best-effort] show clock
clock set show config history
config show config

dir show config rollback changes
process restart show config running

process shutdown show interface pos*
redundancy switchover show memory summary
rollback configuration show process
show process failover

show redundancy
show running-config

Lab 3 Part 1 ! Commit and Rollback
Part 1 ! Commit and Rollback

In this scenario, you are asked to make some configuration changes to the
router and then view and save them. Presuming the configuration changes
have been successful, you must then locate the old configuration and
restore it using the rollback feature.
Make and Test Configuration Changes

In this task, you will make and test the configuration changes. You will
look at the target, merged, and running configurations to make sure that
the changes have taken place.
1. Log in to your owner SDR and display the running configuration.
What command did you use? ______________________________________
2. Check the state (interface and line protocol) of your GigE interfaces.
Are your GigE interfaces up? _____________________________________
3. Display the router date and time.
Which command did you use? _____________________________________
Record the date and time kept by the router. _______________________
4. Configure interface GigabitEthernet0/2/0/1 with a description that
reads Core connection to P1.
5. Configure interface GigabitEthernet0/2/0/2 with a description that
reads Core connection to P2.
6. Check the target configuration.
What command did you use?
_____________________________________________________________
7. Check to see what the complete new configuration would look like.
What command did you use? (hint: merge)
_____________________________________________________________

8. Commit the configuration by using the command that tests and

activates only the valid target configuration statements, and rejects
configuration statements that are not valid.
What is a possible consequence of this type of commit? ______________
_____________________________________________________________
9. Change the router host name to your name and verify the target
configuration while still in configuration mode. Press Ctrl-Z to exit.
Does this give you the option to commit the target configuration?
_____________________________________________________________
If you did not save the routers host name change, proceed anyway.
Review and Verify Configurations

In the second part of this exercise, you look at the just-completed
configuration changes and verify that you can restore an old configuration
using the rollback feature. Finally, you verify that the old configuration
works.
1. Check to see if the router has recorded the configuration change in the
configuration history.
2. Look at the configuration changes made in the last configuration
session.
_____________________________________________________________
Does it list the user who made the changes? ________________________

Lab 3 Part 1 ! Commit and Rollback
3. Check to see if there is a rollback point that allows you to roll back the
to the last committed configuration.
_____________________________________________________________
View your current running configuration.
4. Roll back the configuration changes made in the last commit operation.
_____________________________________________________________
5. Verify that the configuration changes have been rolled back by looking
at your running configuration and the rollback logs.
Have the configuration changes made earlier, been removed?
_____________________________________________________________
6. Check the configuration history log and the rollback points.
Is there a rollback point that would allow you to now change back to
the configuration you just performed a rollback from? _______________
What is that rollback point? _______________________________________
___________________________ CAUTION _______________________

Use the show interface command to verify that the interface
description are in place for subsequent labs.
__________________________________________________________________

Part 2 ! Redundancy and Switchover

At the end of the bootup process, one of the RSPs is primary and provides
overall chassis control and management. The other RSP stays in standby
mode until a switchover is initiated.
Verify RP Status
1. Connect to your PE via the console port using the Terminal Server.
2. Confirm that there are two paired RSPs installed in the owner SDR.
Which command did you use? _____________________________________
Which RSP is the primary? ________________________________________
3. Use the show version command to confirm that the configuration
register for both RSPs has a value of either 0x2 or 0x2102. If the value
is NEITHER, notify your instructor!
4. Using the redundancy state display, answer the following questions:
What is the role of the partner node? ______________________________
What is the status of the standby RSP? ____________________________
How many RSP switchovers have occurred since the router was last
booted? _________________________________________________________
5. Check to see if the two RSPs in your system have the same amount of
memory.
Which command did you use?
_____________________________________________________________
Test RP Switchover
To test RSP switchover and evaluate its effect on process operation, you
will view the switchover from the console and immediately check to see the
status of the process.
1. Open a second terminal server session and connect to the standby RSP.
2. Place the active and standby terminal server sessions side by side to
observe the process.

Lab 3 Part 2 ! Redundancy and Switchover
3. From the active RSP, perform a switchover to the standby RSP.

4. Observe the RSP switchover process from the logging output to the
console of the standby (new active) RSP.
! What was the final failover elapsed time?
_____________________________________________________________
_____________________________ Note _________________________
The time it takes is a reflection of how long it takes for all services on
the RSP to become available. The previous active RSP will reload and
assume a standby role however will not go ready until the
configuration file system is synced.
__________________________________________________________________
5. When the switchover process has finished, log in and use the show
redundancy and show led commands.
Record the slot number of the new active RSP.______________________
6. Use the show process failover command to see process failover
information.
At the bottom of the output screen, record the Last process started:
time. ____________________________________________________________
How many Total processes were restarted? _______________________

Part 3 ! Process Restartability

This exercise illustrates how Cisco IOS XR software processes function in
strict isolation from one another, shielding other processes from individual
process failures. We are simply demonstrating that processes can be shut
down while other processes continue to operate. However, the routers
overall operation may be affected.
____________________________ Note _________________________
If you are telneted to either the management Ethernet or virtual IP
address, your session will be lost when you accomplish the following
steps. Re-establish a terminal session on the console before proceeding.
__________________________________________________________________
1. Enter administration EXEC mode.
2. Display process information for the ipv4_static process.
* What command did you use? ______________________________
* Record the following information pertaining to the IPv4 static route
process.
Job Id: _____________________________
PID: _______________________________
Instance #: _________________________
Respawn count: _____________________
Last started: _______________________
Process state: _______________________
_______________________ Note _________________________
The job ID is used to keep track of processes and does not
change after a process is restarted or the router is reset. It can
also be used to start/restart/stop processes.
___________________________________________________________
3. Stop the ipv4_static process.
* What command did you use? ___________________________________
_____________________ CAUTION _______________________
The shutdown command causes the equivalent of a
process crash. Shutting down random processes can
seriously impact router functionality.
___________________________________________________________
4. Start the ipv4_static process.

Lab 3 Part 3 ! Process Restartability
5. Display the process information for the IPv4 static route process and
record the following values:
Job ID: ____________________________
PID: _______________________________
Instance #: _________________________
Respawn count: ____________________
Last started: _______________________
Process state: ______________________
If a process was stopped by a software failure, what command could you
use to restart the process?
_____________________________________________________________
6. Display the process information for the IPv4 static route process and
record the following values:
Job ID: ____________________________
PID: _______________________________
Instance #: _________________________
Respawn count: ____________________
Last started: _______________________
Process state: ______________________
Has the respawn count changed? _________________________________
_______________________ Note _________________________
A process frequently restarting may indicate a problem that is
impacting router operation.
___________________________________________________________
7. Restore the RSPs to their original primary/standby relationship by
performing another switchover.
8. Terminate your secondary console connection.

Summary
Cisco IOS XR Operations
Commit configurations with the available options

Read the configuration history and rollback logs
Perform a configuration rollback that restores an old configuration
Configure redundancy and perform a switchover
Observe processes checkpointed on secondary RSP
Stop processes and observe continued software operation
Restart processes independent of other router functions

Lab 4
Cisco IOS XR Security
Overview
Description
The goal of this exercise is to familiarize you with the Cisco IOS XR
commands used to configure user authentication and access control.
Objectives
After completing this lab, you will be able to do the following:
Create customized task groups
Create customized user groups
Add users for authentication
Assign users to user group

Cisco IOS XR Security Lab 4
Lab Reference
Command List
For this laboratory exercise, refer to this list if you need command
the lab configurations.
group show aaa taskgroup
inherit show aaa userdb
password show aaa usergroup

task show config merge
taskgroup show aaa task supported

usergroup show user tasks
username

Lab 4 Part 1 Create a User Security Policy
Part 1 Create a User Security Policy

In this section of the lab exercise, you will create a user security policy to
allow certain users to perform router administration and Interior Gateway
Protocol (IGP) configuration commands. You will create another set of
users to perform Exterior Gateway Protocol (EGP) configuration
commands.
Configure Task Groups

1. Review the task IDs supported in Cisco IOS XR software, using the
show aaa task supported command.
2. Create a task group called igpadmin.
! List the command you used to create the task group.
_____________________________________________________________
3. Now that you are in task group configuration submode, assign write
(with implied read) access rights for both Open Shortest Path First
(OSPF) and Intermediate System-to-Intermediate System (IS-IS).
! List the commands used to add OSPF and IS-IS configuration
rights.
_____________________________________________________________
_____________________________________________________________
4. While still in task group configuration submode, add write access
rights to configure a routing process (hint: rib). This is mandatory to
configure routing protocols in Cisco IOS XR software.
! List the command used to add router configuration rights.
_____________________________________________________________
5. Exit from task group configuration submode and create a second task
group called routeadmin.
6. Add Border Gateway Protocol (BGP) configuration rights to the task
group just created.

7. Allow this task group to inherit the rights of the igpadmin group.
! List the command used to inherit rights from the other task group.
_____________________________________________________________
! Do you need to specifically add the rib rights to this task group?
Why?
_____________________________________________________________
_____________________________________________________________
Configure User Groups

The next tasks are to create user groups that match the security policy
(task groups) that you have just added on your router.
1. Exit from task group configuration submode and create a user group
called igp_admin.
! What command did you use to create the user group?
_____________________________________________________________
2. Add the igpadmin task group to this user group.
! What command did you use to add the task group?
_____________________________________________________________
3. Exit from user group configuration submode and create another user
group called route_admin.
4. Add the routeadmin task group to this user group.
Configure Users
The next task is to create the users which will log in to Cisco IOS XR
software and be authenticated as part of the security policy.
1. Exit from user group configuration submode and create a user using
your first name.
! What command did you use to create the user?
_____________________________________________________________

Lab 4 Part 1 Create a User Security Policy
2. Assign this user to the igp_admin user group.

! What command did you use to assign the user?
_____________________________________________________________
3. Create a password for this user. Pick any password you want.
! What command did you use to assign the password?
_____________________________________________________________
4. Exit from user configuration submode and create another user, using
your last name, and assign a password for it.
5. Assign this user to the route_admin user group.
6. Commit this configuration, if you have not already done so, and return
to EXEC mode.
Verify Your Configuration

Check the configuration and make sure that the task groups and user
groups created have the proper permissions and tasks assigned to them.
1. Verify the task group configuration.
! What command did you use to display the task groups?
_____________________________________________________________
2. Verify the user group configuration.
_____________________________________________________________
3. Verify the users and the groups to which they belong.
_____________________________________________________________
! How many users have been assigned to each group?
_____________________________________________________________

4. Examine the task permissions assigned to each user.

! Which user has more task permissions, your current login or
another user? ________________________________________________
_____________________________________________________________
! What command did you use to display your current task

permissions?
_____________________________________________________________
! What command could you use to determine the group and
permissions for a specific user? ________________________________
_____________________________________________________________
_____________________________________________________________

Lab 4 Summary
Summary
Cisco Cisco IOS XR Security
Create customized task groups

Create customized user groups
Add users for authentication
Assign users to user group

Lab 5
IS-IS Routing Configuration
Overview
Description
The goal of this exercise is to familiarize students with the Cisco IOS XR
commands used to configure routing protocols. It is necessary to already
have a good working knowledge of IS-IS to be able to successfully configure
and operate the protocol.
Objectives
Configure IS-IS operation
Verify IS-IS operation

IS-IS Routing Configuration Lab 5
Lab Reference
Command List
In this lab exercise, you will refer to this list for command assistance.
Additional commands, not listed here, may also be needed to complete the
lab configurations.
address-family ipv4 unicast show isis
interface show isis interface
is-type show isis neighbors

net
metric-style
nsf ietf
passive
router isis

Lab 5 Configuring IS-IS
Configuring IS-IS
You are going to configure IS-IS only on the PEa router assigned to your
group. Review the Group to PE/CE Mapping Key table provided in the
lab aids. Only the core-facing GigE interfaces on the PEa router will be
configured by your group. The P routers are already configured with IS-IS.
1. View the status of all your GigE interfaces:
show interfaces Gig* brief
All GigE interfaces connecting to neighboring P routers and the line
protocol should be up. If they are not, inform your instructor and work
with the affected neighbors to get the links up.
2. Locate your routers NSAP in the Lab Aids (Lab Aids page 9).
! What is your routers NSAP? __________________________________
3. Configure your router as an IS-IS router.
! What command did you use to enter the ISIS configuration?
____________________________________________________________
4. Configure your router as a Level 1 router.
! What command did you use to accomplish this?
____________________________________________________________
5. Set your routers NET using the NSAP recorded above.
! What is the command to accomplish this?
____________________________________________________________
6. Configure IS-IS to use wide metrics to support MPLS operation.
! What two commands did you use to accomplish this?
____________________________________________________________
____________________________________________________________
7. Without exiting configuration mode, commit the configuration.

8. View the status of IS-IS.

! What command did you use to view the configuration? ___________
_____________________________________________________________
! Which topologies are supported? _______________________________
! Why? ________________________________________________________
9. Configure IS-IS for IPv4 unicast routing on each of the GigE interfaces
that connects to a P router.
DO NOT ENABLE IS-IS ON YOUR MANAGEMENT ETHERNET
(MgmtEth) INTERFACES.
! In what configuration context (hint: check the prompt) do you
configure IPv4 unicast? _______________________________________
! What commands did you use to configure the interface for IPv4
unicast?
_____________________________________________________________
_____________________________________________________________
10. Show the uncommitted configuration and check it for accuracy.
11. Without exiting configuration mode, commit the configuration.
12. View the status of IS-IS again.
! Is that GigE interface listed as active? __________________________
! Which topologies are supported? _______________________________
! Will IS-IS advertise IPv4 routes? ______________________________
13. Configure IS-IS for all remaining GigE interfaces that connect to P
routers.
14. Check the neighbor adjacencies on each of your IS-IS interfaces to
make sure that they are all up.

Lab 5 Configuring IS-IS
15. Configure your loopback interface for IPv4 unicast routing and set it
passive.
! What commands did you use to configure the loopback interface?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
16. Verify your IS-IS interfaces.
17. Enable NSF (IETF version) for IS-IS and check the state of NSF to
make sure that it is working.
! In what configuration context do you configure NSF?
____________________________________________________________
! What command did you use to configure NSF?
_____________________________________________________________
18. Verify that all your neighbors can be seen again.

Summary
IS-IS Routing Configuration
Configure and verify IS-IS operation

Lab 6
OSPF Routing Configuration
Overview
Description
The goal of this exercise is to familiarize students with the Cisco IOS XR
commands used to configure routing protocols. It is necessary to already
have a good working knowledge of OSPF to be able to successfully
configure and operate the protocol.
Objectives
Configure OSPF operation
Verify OSPF operation

OSPF Routing Configuration Lab 6
Lab Reference
Command List
lab configurations.
area show ospf interface
interface show ospf neighbor
passive
nsf ietf
router ospf

Lab 6 Configuring OSPF
Configuring OSPF
You are going to configure OSPF only on the PEa router assigned to your
configured by your group. The P routers are already configured with
OSPF.
Assume that all PE and P routers are in the backbone (area 0).
1. Configure the OSPF routing protocol on your groups PEa router.
List the command used. __________________________________________
2. Enable in area 0 all GigE interfaces connecting to other P routers.
DO NOT ENABLE OSPF ON YOUR MANAGEMENT ETHERNET
(MgmtEth) INTERFACES.
List the commands used.
_____________________________________________________________
_____________________________________________________________
3. Without leaving configuration mode, commit your configuration.
4. Check that all your OSPF interfaces are up and that you can see your
OSPF neighbors.
Is it compatible to run with any other Cisco router in the same
network? _____________________________________________________
5. Configure your loopback interface in the same area as passive.
What commands did you use to configure the loopback interface?
_____________________________________________________________
_____________________________________________________________
6. Enable NSF (IETF version) for OSPF.
7. Without leaving configuration mode, commit your configuration.

OSPF Routing Configuration Lab 6
Summary
OSPF Routing Configuration
Configure and verify OSPF operation

Lab 7
iBGP Routing Configuration
Overview
Description
The goal of this exercise is to familiarize you with the Cisco IOS XR
commands used to configure iBGP routing protocol. It is necessary to
already have a basic working knowledge of iBGP routing to be able to
successfully configure and operate the protocol.
Objectives
Configure iBGP operation
Verify iBGP operation

iBGP Routing Configuration Lab 7
Lab Reference
Command List
lab configuration and verification.
address-family show bgp neighbor
description show bgp summary
neighbor
neighbor-group
remote-as
router bgp
update-source
use

Lab 7 Configuring iBGP
Configuring iBGP
You are going to configure iBGP only on the PEa router assigned to your
configured by your group. The P routers are already configured with iBGP.
Assume that all PE and P routers are in the same autonomous system
(full-mesh iBGP).
1. Configure the BGP routing process in AS 65000 on your groups PEa
router.
! What command or commands did you use? _____________________
2. Configure the IPv4 unicast address family for BGP operation.
! What command did you use? __________________________________ _
3. Configure a neighbor group, called internal, with your routers local AS
number (65000) as the remote AS (for iBGP operation), your routers
Loopback0 address as the update source, and the IPv4 unicast address
family for the neighbor session.
! What commands did you use to configure the neighbor group?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
4. Set up peering relationships to each of the other P and PE routers
Loopback0 interface addresses using the neighbor group you just
configured and adding a description containing that routers identity
from the lab topology.
! What commands did you use to set up the peering relationships?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
! How many neighbors did you configure? ________________________

5. Check to be sure that your peers (neighbors) are up and that you can
see BGP messages being exchanged.
! What command did you use? __________________________________
6. If all your peers are not up, troubleshoot the problems with the affected
neighbors.

Lab 7 Summary
Summary
iBGP Routing Configuration
Configure and verify iBGP operation

This page intentionally left blank.

Lab 8
Building RPL Route Policies
Overview
Description
The goal of this exercise is to learn to build route policies using the Routing
Policy Language (RPL). You will accomplish this by converting a
traditional route map into RPL policy.
Objectives
Translate a route map using RPL
Nest conditionals to remove repetitive comparisons

Use inline sets to remove small named set references
Reuse common structures with parameterization

Building RPL Route Policies Lab 8
Lab Reference
Command List (RPL Statements)
In this laboratory exercise, you will refer to the following RPL statement
and command list for configuration assistance during the lab exercise.
apply if/then/else/elseif/endif
community-set prepend as-path
community matches prefix-set
destination in route policy
end-policy set community

end-set set local-preference
Lab 82 Version 4.0.1 Cisco ASR 9000 Essentials

Lab 8 Original Route Map
Original Route Map

ip prefix-list 101
10 permit 36.48.0.0/16 le 32
20 permit 45.48.0.0/19 le 32
30 permit 204.10.10.0/24
40 permit 205.11.1.0/24
ip prefix-list 102
10 permit 46.48.0.0/16 le 32
20 permit 35.48.0.0/19 le 32
30 permit 214.10.10.0/24
40 permit 215.11.1.0/24
ip community-list 1
10 permit 10:11
ip community-list 2
10 permit 10:12
ip community-list 3
10 permit 10:13
ip community-list 4
10 permit 10:14
Route Map for prefix-list 101

route-map sample1-translation-1 permit 10
match ip address prefix-list 101
match community 1
set community 12:34 additive
set as-path prepend 101
!
match community 2
set as-path prepend 101 101
!
match community 3
set as-path prepend 101 101 101
!
match community 4
set as-path prepend 101 101 101 101
!
set local-preference 222

Route Map for prefix-list 102

match community 1
set as-path prepend 102
match community 2
set as-path prepend 102 102

match community 3
set as-path prepend 102 102 102

match community 4
set as-path prepend 102 102 102 102


Lab 8 Part 1 ! Converting a Route Map
Part 1 ! Converting a Route Map

You have been given a Cisco IOS route map and associated lists. The route
map needs to be translated into a Cisco IOS XR RPL policy and optimized
for efficiency using parameterization and inline sets.
Task 1 - Simple Conversion

From the route map and lists, do a simple conversion using the RPL
language.
1. Use the prefix-set statement to convert the route map ip prefix list
entries. Keep the same numbering to reduce confusion.
! How many prefix sets do you have? _____________________________
Hint: Dont forget to use the end-set statement after each prefix list
conversion.
2. Take the route map ip community-list entries and convert them into
the RPL equivalent community-set statements. Dont forget to use the
end-set statement to close each statement.
! How many community sets do you have? ________________________
3. Take the route map for prefix-list 101 and convert it into the equivalent
RPL route policy. Start by using the route-policy statement to define
your routing policy name. Then build nested if/then and else-if
conditional blocks containing simple Boolean expressions to combine
match clauses and action statements for each set of clauses. Do not
attempt to consolidate the route map at this point.
Enter the first translated route map statement below:
________________________________________________________________
________________________________________________________________
________________________________________________________________
4. Repeat Step 3 for prefix-list 102 and enter the first translated route
map statement below:
________________________________________________________________
________________________________________________________________
________________________________________________________________

Task 2 - Reduce Comparisons

Reduce the operation comparisons and shorten the statements that are
part of the translated route policy.
1. Examine the first route policy you created in Task 1 for repetitive
comparisons.
! Is there any matching condition and action combination that
repeats in each conditional block of the route policy?
_____________________________________________________________
! What is the only route attribute that repeats AND changes in the
route policy? __________________________________________________
2. Now rewrite the first route policy such that the repetitive statements
occur only once.
! What conditional did you add to the policy to replace the repetitive
statements?
_____________________________________________________________
_____________________________________________________________
3. Examine the second route policy for repetitive comparisons and rewrite
it in a similar manner.
4. Examine the prefix sets you created in Task 1. Hint: Look for repetitive
patterns that can be isolated and removed.
! Did the prefix sets change in this task? _________________________
Task 3 - Consolidate Inline Sets

Edit the route policy statements to consolidate small named sets into inline
sets.
1. Note that the named community sets contain only one matching
element. Replace the references to the named community sets in the
route policy conditionals with their equivalent inline set definition.
2. Delete the named sets that are no longer needed.

Lab 8 Part 1 ! Converting a Route Map
Task 4 - Creating a parameterized policy

1. Examine your route policies and note that they modify the same
attributes.
! Record the common modified attributes:
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
! What is the only attribute whose value doesnt change between the
two policies?__________________________________________________
2. Because there are two common attributes that change between the
policies, create a parameterized policy with two parameters that can be
substituted for the attributes that change.
! Record the parameter names you will be using: __________________
3. Using the common attributes recorded in Step 1, create two
parameterized policies that can be reused for both route policies. Hint:
Create a prepending policy that does the as-path prepending and
another policy that sets the community tag and applies the
prepending policy.
4. Edit the two route policies you have written in the previous task,
replacing all the common statements by applying the second
parameterized policy.
! Record one of the policies:
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________

Part 2 ! Lab Resolution

Task 1 - Step 1
prefix-set ps101
36.48.0.0/16 le 32,
45.48.0.0/19 le 32,
204.10.10.0/24,
205.11.1.0/24
end-set
prefix-set ps102
46.48.0.0/16 le 32,
35.48.0.0/19 le 32,
214.10.10.0/24,
215.11.1.0/24
end-set
Task 1 - Step 2
community-set cs1
10:11
end-set
community-set cs2
10:12
end-set
community-set cs3
10:13
end-set
community-set cs4
10:14
end-set
Task 1 - Step 3
route-policy easy1
if destination in ps101 and community matches-any cs1 then
prepend as-path 101 1
set community (12:34) additive
elseif destination in ps101 and community matches-any cs2 then
elseif destination in ps101 then
endif
end-policy
Lab 8 Part 2 ! Lab Resolution
Task 1 - Step 4
route-policy easy2
if destination in ps102 and community matches-any cs1 then
elseif destination in ps102 then
endif
end-policy
Task 2
route-policy easy1 (the first route map)
if destination in ps101 then
if community matches-any cs1 then
elseif community matches-any cs2 then
else
endif
endif
end-policy
route-policy easy2(the second route map)

if community matches-any cs1 then
else
endif
endif

end-policy
Task 3
route-policy easy1
if community matches-any (10:11) then
elseif community matches-any (10:12) then
else
endif
endif
end-policy
route-policy easy2
else
endif
endif
end-policy
Task 4
route-policy do_prepend($prepend_as)
prepend as-path $prepend_as 1
else
endif
end-policy
route-policy parameterization($as,$tag)
set community (12:$tag) additive

Lab 8 Part 2 ! Lab Resolution
apply do_prepend ($as)

end-policy
route-policy easy1
apply parameterization(101,34)
endif
end-policy
route-policy easy2
apply parameterization(102,35)
endif
end-policy

Summary
Building RPL Route Policies
Translate a route map using RPL

Nest conditionals to remove repetitive comparisons
Use inline sets to remove small named set references
Reuse common structures with parameterization

Lab 9
IPv4 Multicast Configuration
Overview
Description
The goal of this exercise is to familiarize the students with the
Cisco IOS XR commands used to configure and operate IPv4 multicast
routing.
Objectives
Configure IPv4 multicast routing
Verify IPv4 multicast routing operation

IPv4 Multicast Configuration Lab 9
Lab Reference
Command List
lab configuration and verification.
interface all enable show mfib route
multicast-routing show pim group-map
router pim show pim interface
show igmp groups show pim neighbors

show igmp interfaces show pim summary
show igmp summary
show lfib route

Lab 9 Configuring IPv4 Multicast Routing
Configuring IPv4 Multicast Routing

In this lab you will enable IPv4 multicast routing on your router and set up
a basic configuration for PIM.
1. What is the name of the task ID needed to configure multicast routing?
(Hint: You should be in global configuration mode.)
_____________________________________________________________
_____________________________________________________________
2. Check that you have the proper rights to configure and enable
multicast routing. Add any necessary rights.
How did you determine your rights? _____________________________
3. In configuration mode, enable multicast routing on your router.
What command did you use? _______________________________________________
Note how the command prompt changed.
4. Enable multicast routing on your GigE interfaces.
How many commands did you use to achieve this objective? __________
_____________________________________________________________
5. Check to make sure that multicast routing is now enabled on your
router.
What command or commands did you use to verify multicast routing?
_____________________________________________________________

IPv4 Multicast Configuration Lab 9
Summary
IP Multicast Configuration
Configure IPv4 multicast routing

Verify IPv4 multicast routing operation

Lab 10
Multiprotocol Label Switching (MPLS)
Overview
Description
This lab teaches you to configure MPLS Label Distribution Protocol (LDP)
and dynamic traffic engineering (TE) tunnels.
Objectives
Configure MPLS LDP
Configure MPLS dynamic TE tunnels
Verify the configuration and operation

Multiprotocol Label Switching (MPLS) Lab 10
Visual Objective
P routers are
preconfigured for
OSPF, IS-IS,
MPLS LDP iBGP, MPLS LDP,
enabled on all and MPLS-TE.
core-facing GigE P1
interfaces. PE1 PE4 No additional
configuration
Each group will should be
enable one PE required.
router. PE5
PE2
P2
PE3 PE6
IP/MPLS
Core
An IP/MPLS cloud is
established when all PE-P
neighbor relationships are
fully configured.

Lab 10 Lab References
Lab References
Command List
lab configurations.
MPLS LDP Commands
discovery show mpls
graceful restart show mpls label

interface show mpls ldp
mpls ldp show mpls forwarding
router-id show mpls bindings
RSVP Commands
bandwidth show rsvp interface
interface
rsvp
MPLS TE Dynamic Commands
autoroute announce show isis mpls
destination show mpls traffic-eng

interface tunnel-te show ospf mpls
ipv4 unnumbered
mpls traffic engineering
path-option
priority
signaled- bandwidth

Part 1 Configuring MPLS LDP

Overview
You are going to configure MPLS LDP only on the PEa router assigned to
your group. Review the Group to PE/CE Mapping Key table provided in
the lab aids. Only the core-facing GigE interfaces on the PEa router will
be configured by your group. The P routers are already configured with
MPLS LDP.
MPLS LDP Configuration
Router(config)# mpls ldp

Router(config-ldp)# router-id loopback 0
interface gigabitEthernet0/2/0/1
interfce gigabitEthernet0/2/0/2 IP/MPLS
PEa 0/2/0/1
PEa
PEa 0/2/0/2
Group PEa
mpls ldp
router-id loopback0
X
Task 1. Configuring LDP Discovery

Use the following steps to configure LDP discovery to locate neighbors:
1. Enter configuration mode on your groups PEa.
2. Enter MPLS LDP configuration submode.
3. Specify your router ID using your loopback interface.
_____________________________________________________________
Lab 10 Part 1 Configuring MPLS LDP
4. To support LDP, configure the GigE core interface between P and PE

routers.
_____________________________________________________________
5. (Optional) Specify how long your router will keep a discovered router
without receipt of subsequent hello messages. The default for this
parameter is 15 seconds. Set the discovery hello holdtime to 30 seconds.
What command did you use to change the discovery hello holdtime?
_____________________________________________________________
6. (Optional) Specify the interval your router will use between consecutive
hello messages. The default is 5 seconds. Change the time to 15
seconds.
What command did you use to change the consecutive hello setting?
_____________________________________________________________
7. Without exiting configuration mode, commit your configuration.
8. Verify your configuration using do show commands.
9. Turn on LDP NSF (hint: graceful-restart).
What command did you use to implement NSF for MPLS LDP?
__________________________________________________________
10. Commit the configuration and exit configuration mode.
Task 2. Verifying LDP Discovery Operations

1. Verify the running configuration by using show commands.
2. Are all of your LDP neighbors active and exchanging labels? If not,
troubleshoot your LDP configuration. Be sure to check with your
neighbors about the status of their configuration.
3. Use the show mpls ldp parameters and show mpls ldp graceful-
restart commands to determine the status of graceful-restart.
What does the show mpls ldp parameters command show for a
status of graceful-restart?
What does the show mpls ldp graceful-restart command show?
4. Display the current MPLS LDP discovery information using show

commands.
Which command or commands did you use? ____________________
_____________________________________________________________
_____________________________________________________________

Lab 10 Part 1 Configuring MPLS LDP
5. Display the current MPLS forwarding information using show

commands.
Which command or commands did you use? ____________________
_____________________________________________________________
6. Complete the following table with the label used to reach the loopback
address of the other routers in the network. Use the mpls show
commands to find the label information. Exclude your own router.
Destination
Local label Outgoing label
router
P1
P2
PE1
PE2
PE3
PE4
PE5
PE6
WAIT Please be sure all other groups have completed the LDP section
before proceeding.

Part 2 Configuring Dynamic Traffic Engineering Tunnels

The IP/MPLS core cloud is now operational. You will configure an
MPLS-TE tunnel between two routers (PEa and PEb) that are assigned to
your group. This is the first lab in which you will configure the PEb router.
Review the Group to PE/CE Mapping Key table provided in the lab aids.
Only the core-facing GigE interfaces on the PEa and PEb routers will be
configured by your group. The P routers are already configured to support
MPLS-TE.
You will configure dynamically-created (not statically-created) MPLS TE
tunnel paths.
Visual Objective
MPLS-TE Tunnel
interface (head)
PEa 0/2/0/1 IP/MPLS
P1
MPLS-TE
Tunnel path
traverses the
P router
P2 core.
PE1
PEb 0/2/0/2
MPLS-TE Tunnel
interface (tail)

Lab 10 Part 2 Configuring Dynamic Traffic Engineering Tunnels
MPLS-TE
MPLS Tunnel Lab
TE Tunnel Configuration Diagram
x = Group #
1. Configure the MPLS-TE infrastructure
2. Create the MPLS-TE Tunnel
router ospf lab interface (head and tail)
mpls traffic-eng router-id loopback0
area 0 interface tunnel-te ab
mpls traffic-eng ipv4 unnumbered Loopback 0
rsvp priority 0 0
signalled-bandwidth 1000
interface gigabitEthernet0/2/0/1 PEa 0/2/0/1 autoroute announce
bandwidth
mpls traffic-eng destination 10.b.b.b
interface gigabitEthernet0/2/0/1 path-option 1 dynamic
PE1 2. Create the

1. Configure the MPLS-TE infrastructure PEb 0/2/0/2 MPLS-TE Tunnel
interface (head
router ospf lab
mpls traffic-eng router-id loopback0 and tail)
area 0
mpls traffic-eng interface tunnel-te ba
rsvp ipv4 unnumbered Loopback 0
PE1 priority 0 0
bandwidth signalled-bandwidth 1000
mpls traffic-eng autoroute announce
interface gigabitEthernet0/2/0/2 destination 10.a.a.a
path-option 1 dynamic
Table 1. MPLS-TE Tunnel Lab Configuration

2011, Cisco Systems, Inc. All rights reserved. Version 3.9.1 Lab Aid Presentation
MPLS TE Tunnel Configuration in IOS XR
Group PEa PEb

router ospf lab router ospf lab
mpls traffic-eng router-id loopback0 mpls traffic-eng router-id loopback0
area 0 area 0
mpls traffic-eng mpls traffic-eng
rsvp rsvp
interface gigabitEthernet0/2/0/1 interface gigabitEthernet0/2/0/2
bandwidth bandwidth
mpls traffic-eng mpls traffic-eng
X
interface tunnel-te ab interface tunnel-te ba

ipv4 unnumbered Loopback 0 ipv4 unnumbered Loopback 0
priority 0 0 priority 0 0
signalled-bandwidth 1000 signalled-bandwidth 1000
autoroute announce autoroute announce
destination 10.b.b.b destination 10.a.a.a
path-option 1 dynamic path-option 1 dynamic

Configuring the MPLS-TE Infrastructure

Dynamic MPLS TE tunnels use the core IGP, LDP, and RSVP to set up
paths. The infrastructure configuration will be completed on routers PEa
and PEb that are assigned to your group. Refer to the Group to PE/CE
Mapping Key table in the Lab Aids.
Configuring the IGP Relationship
To build an association between your IGP and MPLS TE, you must set a
loopback interface address in the IGP. For this lab, we will use OSPF.
1. On your groups PEa, enter the OSPF routing protocol instance and set
the loopback interface as the MPLS-TE router ID. Check with your
neighbor to ensure this step was performed on your groupsPEb.
What command or commands did you use? ______________________
_____________________________________________________________
_____________________________________________________________
2. Set the MPLS-TE OSPF area in area 0.
What commands did you use? __________________________________
Configuring the RSVP Signaling
MPLS-TE uses RSVP signaling.

1. Enable RSVP signaling on both the gigabitEthernet 0/2/0/1 interface on
PEa and the gigabitEthernet 0/2/0/2 interface on PEb.
What command or commands did you use?
__________________________________________________________
2. Configure the default RSVP bandwidth for all your interfaces.
What command or commands did you use? ______________________
3. Without exiting configuration mode, commit the configuration and
verify the status of the RSVP interfaces.

Configuring the TE Interfaces
The routers must know what interfaces will participate in the MPLS traffic
engineering infrastructure.
4. Set both the gigabitEthernet 0/2/0/1 interface on PEa and the
gigabitEthernet 0/2/0/2 interface on PEb for MPLS TE.
__________________________________________________________
7. Commit your configuration.
8. Exit configuration mode.
Reviewing the MPLS-TE Infrastructure
1. Display and verify the MPLS-TE topology.

What command did you use? __________________________________
_____________________________________________________________
What bandwidth constraint model is in use? ____________________
Choose a single interface. What is the physical bandwidth
available? ________________________________________________
What is the maximum reservable bandwidth? __________________
Is this the bandwidth amount you configured? __________________
_____________________________________________________________
_____________________________________________________________
2. Display and review the MPLS-TE link management information.
What command shows this information? _______________________
_____________________________________________________________
What is your link label type? __________________________________

3. Display the IGP to-MPLS-TE relationship.

What command provides this information? ______________________
_____________________________________________________________
4. Display the MPLS and RSVP interfaces.
Configuring the MPLS-TE Tunnels

____________________________ Note _________________________
This configuration is completed on only two routers per group (PEa and
PEb). One MPLS-TE tunnel will be created in each direction to
complete a single, bidirectional tunnel.
__________________________________________________________________
Configure a MPLS TE tunnel between PEa and PEb by creating two tunnel
interfaces, one on each PE.
1. Create a tunnel interface to one of your neighbor routers.
2. Use your loopback address as the tunnel head.
3. Use the loopback address of the destination router as the tunnel tail.
4. Configure the tunnel with 1000 Kbps of bandwidth.
5. Use a dynamic path as the primary path.
6. Set the priority to the highest available level.
7. Advertise the tunnel availability to the IGP.
Repeat Steps 1 through 7 for each tunnel that you need to create.

Verification of Dynamic TE Configuration
Verification should be done on both PEa and PEb routers.

8. Verify that all tunnels are active.
What command or commands did you use? _____________________
__________________________________________________________
__________________________________________________________
9. Review the status of RSVP.
__________________________________________________________
10. When all tunnels are active, how many tunnel heads and tails do you
have in your router?
Heads
Tails
11. Enter show mpls and show mpls traffic-eng commands and observe
the labels. Review all the label information to confirm your tunnels are
properly configured.
12. Examine the OSPF interfaces.
Are your tunnels now listed as OSPF interfaces? ________________
13. Examine the IPv4 routes to the tunnel destination addresses.
What type of route are they? ___________________________________

Summary
Multiprotocol Label Switching (MPLS)
Configure MPLS LDP

Configure MPLS dynamic TE tunnels

Lab 10 Summary

Lab 11
Layer 3 Virtual Private Network
Overview
Description
This lab teaches you to configure a simple Layer 3 Virtual Private Network
(L3VPN) and the infrastructure required to support it.
Objectives
Configure an L3VPN
Configure an L3VPN infrastructure
Verify and test L3VPN configuration and operation

Layer 3 Virtual Private Network Lab 11
Visual Objective
L3VPN Lab Topology x = Group #

Interface PEa 0/2/0/
Loopback ab assigned to VRF VRF created
GROUP_ x 28 IP/MPLS
with route
10.255.ab.1 /24 targets
21
CEa
FE0/ 172.16.ab.2
172.16.ab.1
BGP
configured
for L3VPN
Loopback ba
172.16.ba.1
PEb 0/2/0/
10.255.ba.1 /24
172.16.ba.2
CEb
FE0/ 22
29 VRF created
with route
targets
Static routes configured
between CE and PE
Interface
assigned to VRF
Ping between CE L3 interfaces to GROUP_x
verify L3 connectivity

Lab References
Command list
lab configurations.
address-family vpnv4 unicast router static
vrf show bgp vrf
ipv4 address show int vrf

export route-target show route
import route-target show route vrf

rd show bgp vpnv4 unicast
redistribute ping vrf
traceroute speed 100
vrf

Configuring a Layer 3 VPN

Overview
In this lab your group will create a complete Layer 3 using the PEa and
PEb routers. NO configuration will occur on the P routers. No
configuration is required on the CEs.
Review the Group to PE/CE Mapping Key table provided in the lab aids
for your groups assignments. Use the illustrations and tables provided to
determine the configuration required on PEa and PEb.
____________________________ Note _________________________
Please take careful note of the interface numbers on each PE to prevent
configuration overlap between groups.
__________________________________________________________________
L3VPN Lab Configuration x = Group #

vrf GROUP_x
PEa 0/2/0/ address-family ipv4 unicast
import route-target 65000:x
28 IP/MPLS
export route-target 65000:x
21 interface gigabitEthernet0/2/0/28
CEa speed 100
FE0/ vrf GROUP_x
ipv4 address 172.16.ab.2 /24
CEa = ip route 172.16.ba.0/24 172.16.ab.2
ip route 10.255.ba.0/24 172.16.ab.2
router bgp 65000
address-family vpnv4 unicast
neighbor 10.b.b.b
address-family vpnv4 unicast
CEb vrf GROUP_x

FE0/ 22 rd 65000:x
29 address-family ipv4 unicast
redistribute static
redistribute connected
CEb = ip route 172.16.ab.0/24 172.16.ba.2
ip route 10.255.ab.0/24 172.16.ba.2 PEb 0/2/0/
router static
vrf GROUP_x
address-family ipv4 unicast
10.255.ab.0 /24 gigabitEthernet0/2/0/28

Lab 11 Configuring a Layer 3 VPN
Table 1. Layer 3 VPN Configuration on PEa and PEb
Table 1. L3VPN Configuration

Group PEa PEb
vrf GROUP_x vrf GROUP_x

address-family ipv4 unicast address-family ipv4 unicast
import route-target import route-target
65000:x 65000:x
export route-target export route-target
65000:x 65000:x

speed 100 speed 100
ipv4 address 172.16.ab.2 255.255.255.0 ipv4 address 172.16.ba.2 255.255.255.0
! !
router bgp 65000 router bgp 65000
X address-family vpnv4 unicast address-family vpnv4 unicast
neighbor 10.b.b.b neighbor 10.a.a.a
address-family vpnv4 unicast address-family vpnv4 unicast
rd 65000:x rd 65000:x
redistribute connected redistribute connected
redistribute static redistribute static
router static router static

10.255.ab.0/24 gigabitEthernet0/2/0/28 10.255.ba.0/24 gigabitEthernet0/2/0/29
Creating the VPN VRF

This section creates the specific VRF entry for your routers VPN
destination. Perform these steps on both PEa and PEb. Use the diagrams
and the Lab Aids to determine the PEa and PEb assignments for your
group.
1. In global configuration mode, create a VRF entry using your group
number (GROUP_x).
2. Set the address family for IPv4 unicast traffic.
What is the command to do this? __________________________________
_____________________________________________________________
3. Specific routes from your CEas VPN destination must be imported for
the VRF to use. Enter the command that will accomplish that on PEa,
keeping in mind that it must match the entry on PEb which connects to
CEb, the VPN partner.
What is the entry used by the destination PEa? ____________________

What command did you use to create the entry for the routes your VRF
needs to learn? _______________________________________________
4. Also, your PEa must send routes to the destination PEb. This entry will
be used by the partner to put your CEa routes into its VRF.
What value did you use? __________________________________________
5. Exit your VRF configuration.
Assigning the VRF to the Interface

The interface that supports the CE router using the VPN has the VRF
assigned to it. Perform these steps on both PEa and PEb.
1. The interface to which the VRF is going to be assigned must not have
an IP address assigned to it. Remove the IP address from the interface
that attaches to your CE router. Set the interface speed to 100
Mbps.
2. Assign the VRF to the interface using the same VRF name.
3. Reassign the IP address to the VRF on the interface.
Record the commands, in sequence, used to accomplish the above three
steps. ________________________________________________________
_____________________________________________________________
Configuring VPN Routing with the CE

The routing protocol between the PE and CE routers is static routing.
Perform the following steps on both the PEa and PEb routers.
1. Add a VRF to the static routing process.
2. Set the address family for IPv4 unicast traffic.
3. Add static routes for the destination CE addresses as indicated in the
illustration and table above.
Write the command or commands you used. ________________________
_____________________________________________________________
_____________________________________________________________

Configuring BGP for the VPN

The BGP routing protocol must be configured to establish a relationship
between itself and MPLS, so labels can be used to forward data with any
configured VPNs. BGP is also used to advertise VRF routes to other
partner PE routers. Perform the following steps on both PEa and PEb.
1. Add a statement to the existing BGP router definition that will create
the BGP-MPLS relationship.
What command did you use? _____________________________________
2. Using the same BGP router definition, add your VRF definition.
3. Routes associated with this VPN must be distinguishable from routes
in other VPNs that might be created. Set the distinguisher value to
65000:x.
What command did you use? _____________________________________
4. Set the address family for the VPN.
What command and value did you use? ____________________________
5. The routes that are assigned to the VPN must be advertised. These
routes are not BGP routes. Enter a command so that these routes will
be advertised to other BGP routers.
What commands and values did you use?
_____________________________________________________________
_____________________________________________________________
6. Add a statement to the PE neighbor configuration with which you have
a VPN relationship.
What command did you add and to which neighbor?
_____________________________________________________________
Verification of the L3VPN Configuration

1. Display the (default VRF) route table on the PEa.
Do you see routes from either of the CEs? _________________________
Why or why not?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
2. Display the VRF route information.
Do you see the addresses from your partner CEa router? ____________
Should you see them? ____________________________________________

If you think that you should see the addresses and you do not see them,
troubleshoot with students at VPN destination to resolve the problem.
3. Connect to your groups CEa router.
4. Display the route table on the CEa.
Do you see the routes from your partner CEb? ______________________
_____________________________________________________________
5. Connect to PEb. Display the BGP VRF information.
What is the next hop for the path to the networks at the destination
CEa? ________________________________________________________
6. From CEa, issue a ping to the addresses on your VPN destination CEb
router. Use the following diagrams to identify which Loopback
addresses to ping for your groups VRF
Were you successful? _____________________________________________
If you were not successful, troubleshoot with students at VPN
destination to resolve the problem.

L3VPN IP Addressing Groups 1-3

Group #1
172.16.12.1 172.16.12.2
10.255.12.1 21 28
22 29
10.255.13.1
172.16.13.1 Group #2 172.16.13.2
172.16.23.1 172.16.23.2
10.255.23.1
21 28
22 29
10.255.21.1 172.16.21.1 172.16.21.2
172.16.31.1 172.16.31.2
10.255.31.1
21 28
22 29
10.255.32.1 172.16.32.1 172.16.32.2 Group #3

L3VPN IP Addressing Groups 4-6

Group #4
172.16.45.1 172.16.45.2
10.255.45.1 21 28
22 29
10.255.46.1
172.16.46.1 Group #5 172.16.46.2
172.16.56.1 172.16.56.2
10.255.56.1
21 28
22 29
10.255.54.1 172.16.54.1 172.16.54.2
172.16.64.1 172.16.64.2
10.255.64.1
21 28
22 29
10.255.65.1 172.16.65.1 172.16.65.2 Group #6

Lab 11 Summary
Summary
Layer 3 Virtual Private Networks
Configure an L3VPN
Configure an L3VPN infrastructure

Lab 12
Local E-Line Service
Overview
Description
The goal of this exercise is to familiarize the student with various
Cisco IOS XR software commands used to implement point-to-point local
E-Line Carrier Ethernet services on a Cisco ASR 9000 Series Aggregation
Services Router.
There are two parts in this lab. In Part One, link bundles are configured
on the Cisco ASR 9000 Provider Edge (PE) devices. In Part Two Ethernet
Flow Points (EFPs) are built on the logical link bundle interfaces. A Layer
2 Virtual Private Network (L2VPN) crossconnect links the two EFPs, and
Layer 2 connectivity is verified between Cisco ME3400 Customer
Equipment (CE) devices by issuing ping commands between CE switch
virtual interfaces (SVIs).
Configuration is performed on the PE devices only. The CE and core (P)
devices are preconfigured. The figure below shows the objectives of this
lab.
Objectives
Configure link bundles with Cisco EtherChannel
Configure Ethernet Flow Points

Configure P2P local crossconnects
Verify point-to-point L2VPN operation

Local E-Line Service Lab 112
Visual Objective
Ping betw een CE SVIs to

verify L2VPN connectiv ity
x = Group #
Create link
bundles
Int vlan x0
192.168.x0.1 PEa 0/2/0/
CEa 1,2 3,4
Local xconnect
FE0/
20,21
Int vlan x0
192.168.x0.2 PE1
EFPs on Bundle
CEb sub-interfaces
13,14 Local E-Line
FE0/ L2VPN
Trunk ports on
Bundled interfaces

Lab References
Command List
the lab objectives. This list is meant to supplement the Student Guide
materials.
configure terminal
show interface
L2transport
encapsulation
rewrite
L2vpn
xconnect
bundle-ether
bundle id
speed 100
interface
show l2vpn xconnect
ping
commit

Part 1 ! Link Bundles

Overview
In this lab, you will create two Ethernet link bundles on a Cisco ASR 9000
PE. Refer to the Lab Aids to identify your group CE and PE assignments.
Each link bundle will have two physical ports assigned to it. You will
verify the state of the Ethernet interfaces, create link bundles, assign
Ethernet interfaces to the link bundles, and verify the state of the link
bundles. Refer to the following figures to identify the configurations for
you group. CEs are preconfigured and the Cisco IOS configuration shown
is in summarized form.
Link Bundle Configuration or Local E-Line

Bundle Lab Diagram for Local E-Line
IOS Bundle #1
x = Group #
interface fast-ethernet1 IOS XR Bundle #1
channel-group 1 mode on
interface fast-ethernet2 interface bundle-ether x00
channel-group 1 mode on commit
speed 100
PEa 0/2/0/ bundle id x00
CEa 1,2 3,4 interface gigabitEthernet0/2/0/4

speed 100
FE0/ bundle id x00
20,21
PE1
CEb
FE0/ IOS XR Bundle #2
13,14
interface bundle-ether x01
commit
IOS Bundle #2 interface gigabitEthernet0/2/0/20
speed 100
interface fast-ethernet13 bundle id x01
channel-group 5 mode on interface gigabitEthernet0/2/0/21
interface fast-ethernet14 speed 100
channel-group 5 mode on bundle id x01

Lab 12 Part 1 ! Link Bundles
Table 1. Bundle Configuration

Group PEa
int bundle-ethernet x00
commit
int gigE 0/2/0/3

speed100 Group CEa CEb
bundle id x00 int fastethernet 0/1 int fastethernet 0/13
int gigE 0/2/0/4 channel-group 1 mode on channel-group 5 mode on
X
speed 100 int fastethernet0/2 int fastethernet 0/14
bundle id x00 channel-group 1 mode on channel-group 5 mode on
X
int bundle-ethernet x01
commit
int gigE 0/2/0/20

speed 100
bundle id x01
int gigE 0/2/0/21
speed 100
bundle id x01
Task 1. Verify Gigabit Ethernet port state

The Cisco ASR 9000 PE is equipped with a 40-port Gigabit Ethernet card
in slot two (0/2/0/port number). This card is populated with 10/100
Ethernet interface adapters so the link operates at 100 Mbps. The CE
interfaces are also Fast Ethernet. Verify that the physical interfaces that
are configured with link bundles are in the UP state. Refer to the Lab Aids
for your group assignments. Always replace x with your Group
number.
1. Connect to your assigned PE router. In interface configuration mode,
check that the state of the physical interfaces that you will assign to a
bundle are in the UP state. The PE interface speed must be set to
match that of the CE device.
! Which PE interface command do you use to set the correct link
speed?
_____________________________________________________________
Task 2. Create link bundles and assign member interfaces.

1. Create the logical link bundle x00 using the assignments in Table 1.
Add a description to bundle interface x00 that reads Group x Local E-
Line, EoMPLS E-Line, Local E-LAN, L2 Multicast.
2. Assign two member interfaces to the link bundle.

! Which command did you use to create the logical link bundle
interface?
_____________________________________________________________
3. Create the second link bundle x01 and add a description that reads
Group x Local E-Line, Local E-LAN, L2 Multicast.
4. Assign two member interfaces to the link bundle.
! What command do you use to assign a physical (or member)
interface to a bundle?
_____________________________________________________________
5. Verify and commit the link bundle configuration.
! Which of the following actions did you perform?
a. Add bundle member to a link bundle in bundle interface
configuration mode.
b. Assign the bundle to an interface in physical or member interface
configuration mode.
_____________________________________________________________

Lab 12 Local E-Line with EFPs
Local E-Line with EFPs

Overview
In this part of the lab, you build a L2VPN service using the link bundles
you just created. EFPs are built on the bundle interfaces on a single PE.
The two local EFPs are then linked with a point-to-point crossconnect. The
bundle interfaces must be in the UP state before the EFPs or the
crossconnect comes UP. Once the L2VPN is UP, a ping between CEs
should be successful. Testing of tag translation operations is optional. The
figure below summarizes the configuration.
Local E-Line with EFPs Configuration

Local E-Line Lab Diagram
Trunk #1 x = Group #
1. EFP #1
switchport mode trunk
switchport trunk allowed vlan x0 interface bundle-Ether x00.1 l2transport
encap dot1q x0
Int vlan x0
SVI #1 192.168.x0.1
PEa 0/2/0/
CEa 1,2 3,4

FE0/
SVI #2 20,21
Int vlan x0 PE1
192.168.x0.2 3. xconnect
l2vpn
CEb 13,14 xconnect group AC2AC_x p2p LOCAL_ELINE
FE0/ interface bundle-Ether x00.1
interface bundle-Ether x01.1
Trunk #2
switchport mode trunk 2. EFP #2
switchport trunk allowed vlan x0 interface bundle-Ether x01.1 l2transport
encap dot1q x0

Table 2. Local E-Line Configuration

Table 2. Local E-Line Configuration
Group PEa
int bundle-ether x00.1 l2transport
encap dot1q x0
int bundle-ether x01.1 l2transport
X encap dot1q x0
L2vpn
xconnect group AC2AC_x
p2p LOCAL_ELINE
Group CEa CEb

int Vlan x0 int Vlan x0
192.168.x0.1 192.168.x0.2
X int port-channel 1 int port-channel 5
switchport mode trunk switchport mode trunk
switchport trunk allowed vlan x0 switchport trunk allowed vlan x0
Task 1. Verify Link Bundle state

EFPs are built on the link bundles created in Part 1 of this lab. Verify that
the bundle interfaces are configured with EFPs are in the UP state. Refer
to Table 2 for your Groups configuration.
1. Connect to your assigned router. Verify that the access Bundle-
Ethernet ports that are assigned to your Group are in the UP state. If
they are not, troubleshoot the link.
! What are the MAC addresses of each of the link bundles?
_____________________________________________________________
_____________________________________________________________
Task 2. Create Local EFPs

1. On bundle-Ethernet interface x00, create a subinterface EFP. Use the
parameters assigned to your Group in Table 2 to match on a single
VLAN x0 with no rewrite action. Add a description that reads Group x
Local E-Line.
2. Create a second EFP on bundle-Ethernet interface x01 with the same
configuration as the other EFP. Add a description that reads Group x
Local E-Line
3. Verify the configuration before committing it.
4. Commit the configuration.

Lab 12 Local E-Line with EFPs
5. Verify the state of the EFPs.

! What commands did you use to create the EFPs?
_____________________________________________________________
_____________________________________________________________
Are the EFPs in the UP state? What command did you use?
_____________________________________________________________
_____________________________________________________________
Task 3. Create a Local Crossconnect

1. Create an L2VPN with a crossconnect group name specified in Table 2.
2. Add the two newly created EFPs to the crossconnect group.
3. Verify the configuration before committing it.
5. Verify the state of the crossconnect.
6. Verify the P2P local E-Line configuration.
! What commands did you use to connect the EFPs?
_____________________________________________________________
_____________________________________________________________
! What is the state of each crossconnect segment?:
_____________________________________________________________
_____________________________________________________________
Task 4. Verify connectivity between the CE devices.

1. Connect to your CEa device and log into User Mode. The Password is
lab.
2. The CEs each have an array of Switch Virtual Interfaces (SVIs). An
SVI is a logical Layer 3 interface that is mapped to a single VLAN.
An SVI mapped to VLAN x0 has been preconfigured on both CEa and
CEb. Ping between these CE SVIs for your VLAN to test reachability.
Use the IP addresses assigned to your Group in Table 2. Use show
l2vpn xconnect detail, show interface and other show commands
to show traffic flow. A successful Ping completes this lab.
Task 4. (Optional) Configure VLAN Rewrite

1. You can test the behavior of VLAN rewrite operations on the EFP of
the Cisco ASR 9000. On interface bundle-ethernet x00 and interface
bundle-Ethernet x01, try implementing different rewrite actions (push,

pop, and translate). If a ping is unsuccessful, use show interface

commands to identify where the packets are dropped (check CE SVI
and trunk ports, and PE EFPs.).
2. Configure and test different egress filtering options either globally or
directly on the EFPs.

Lab 12 Summary
Summary
Local E-Line Service
Configure link bundles with Cisco EtherChannel

Configure Ethernet Flow Points
Configure P2P local crossconnects
Verify point-to-point L2VPN operation


Lab 13
EoMPLS Service
Overview
Description
The goal of this exercise is to familiarize the student with the various
Cisco IOS XR software commands used to implement a Point-to-point
EoMPLS E-Line Carrier Ethernet service across an IP and MPLS-enabled
Cisco ASR 9000 Series Aggregation Services network.
There are three parts to this lab. Part One involves link bundle creation.
Part Two involves EFP and pseudowire creation between two
Cisco ASR 9000 PEs. Part Three adds resiliency to the EoMPLS E-Line by
adding a backup pseudowire to the topology.
Configuration is performed on the PE devices only. The CE and P devices
are preconfigured. The diagram below illustrates the objectives of this lab.
Objectives
Configure EFP encapsulation, matching, and rewrite.
Configure P2P EoMPLS E-Line service.
Verify Layer 2 Ethernet service operation.
Configure pseudowire redundancy.
Verify redundancy and resiliency operation.

EoMPLS Service Lab 13
x = Group #
EoMPLS E-Line PEa 0/2/0/
L2VPN
Int vlan x1 3,4 IP/MPLS
192.168.x1.1
1,2
CEa
FE0/
EoMPLS
xconnect
Int vlan x1 PEb 0/2/0/
192.168.x1.2
CEb
FE0/
15,16
22,23
Trunk ports on
Bundled interfaces
EFPs on Bundle
Ping betw een CE SVIs to sub-interfaces

Lab References
Command List
materials.
show ospf
show mpls ldp
ping
L2transport
encapsulation
rewrite
L2vpn
xconnect
neighbor
backup
show interface
show l2vpn xconnect
pw-class
preferred-path

Part 1 ! Link Bundles

Overview
In this lab, you will create a new link bundle across which you will build an
EoMPLS pseudowire. The EoMPLS PW links EFPs on different PE
devices. First, you will create a link bundle on PEb. The link bundles
created on PEa will be reused by the EoMPLS E-Line.
Link Bundle Configuration for EoMPLS E-Line
x = Group #
Previously created
Bundle
Previously created PEa 0/2/0/
Bundle
3,4
CEa
1,2
PE1 IP/MPLS
FE0/
PEb 0/2/0/
CEb
FE0/
15,16
22,23
IOS Bundle #1 IOS XR Bundle #1

interface bundle-ether x02
interface fast-ethernet15
commit
channel-group 6 mode on
interface fast-ethernet16
channel-group 6 mode on bundle id x02
bundle id x02

Lab 13 Part 1 ! Link Bundles
Table 1. Link Bundle Configuration in IOS XR and IOS
Task 1. Verify IP/MPLS connectivity

Before MPLS-based Layer 2 services can be created, the necessary
IP/MPLS network foundation must be configured. Verify the existing IGP
and MPLS configuration using Cisco IOS XR show commands.
1. Connect to your assigned PEb router. Verify IGP connectivity with
your neighbor routers using the show ospf neighbors or show isis
neighbors command. Record your findings.
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
2. Verify MPLS connectivity with your neighbor routers using the show
mpls ldp and show mpls interfaces commands. Record your
findings.
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
3. Ping all the remote PE routers.

Task 2. Create a Link Bundle on PEb

Both EFPs that serve as endpoints to EoMPLS PW will be built on bundle-
interfaces. An additional link bundle must be created on PEb.
____________________________ Note _________________________
Make sure you are building your bundles on the PEb router assigned to
your group. Do not create any new bundles on PEa.
__________________________________________________________________
1. Connect to your assigned PEb router. In interface configuration mode,
check that the state of the physical interfaces that you will assign to a
bundle are in the UP state. The PE interface speed must be set to
match that of the CE device.
! Which PE interface command do you use to set the correct link
speed?
_____________________________________________________________
2. On PEb, create the logical link bundle x02 using the assignments in
Table 1. Add a description to bundle interface x02 that reads Group x,
EoMPLS E-Line.
3. Assign two member interfaces to link bundle.
4. Verify and commit the configuration.
! Which command did you use to create the logical link bundle
interface?
_____________________________________________________________

Lab 13 Part 2 ! EoMPLS E-Line
Part 2 ! EoMPLS E-Line

Overview
The EoMPLS PW links EFPs on different PE devices. Before the
pseudowire can be created, the IGP and MPLS network must be fully
configured. In this portion of the lab, verify the EoMPLS network
foundation and create a point-to-point EoMPLS or VPWS service.
EoMPLS E-Line Configuration
EoMPLS E-Line Lab Diagram

x = Group #
1. EFP #1
Trunk#1 interface bundle-Ethernet x00.2 l2transport
encap dot1q x1
switchport trunk allowed vlan add x1
2. xconnect #1
Int vlan x1 l2vpn
SVI#1 192.168.x1.1 xconnect group AC2PW_x
PEa 0/2/0/ p2p PEa_PEb_x_A
CEa 1,2 3,4 int bundle-Ethernet x00.2

neighbor 10.b.b.b pw-id x01
FE0/
SVI#2
Int vlan x1 PE1 4. xconnect #2
192.168.x1.2
PEb 0/2/0/ l2vpn
xconnect group AC2PW_x
CEb 15,16 p2p PEb_PEa_x_B
int bundle-Ethernet x02.1
FE0/ neighbor 10.a.a.a pw-id x01
22,23
Trunk#2 PE1 3. EFP#2
switchport trunk allowed vlan x1
interface bundle-Ethernet x02.1 l2transport
encap dot1q x1

Table 2. EoMPLS E-Line Configuration
Group PEa PEb

int bundle-eth x00.2 l2transport int bundle-eth x02.1 l2transport
encap dot1q x1 encap dot1q x1
L2vpn L2vpn
X xconnect group AC2PW_x xconnect group AC2PW_x
p2p PEa_PEb_x_a p2p PEb_PEa_x_b
int bundle-eth x00.2 int bundle-eth x02.1
neighbor 10.b.b.b pw-id x01 neighbor 10.a.a.a pw-id x01
Group CEa CEb

192.168.x1.1 192.168.x1.2
int port-channel 1 int port-channel 5
X
switchport mode switchport mode
trunk trunk
switchport trunk switchport trunk
allowed vlan add x1 allowed vlan add x1
Task 1. Create the EFPs

A P2P EoMPLS or E-Line service consists of two EFPs on different
platforms connected by an EoMPLS cross-connect. EFPs on PEa and PEb
will be connected by an EoMPLS pseudowire. Each group will create an
entire configuration including an EFP on their PE and on the far-end PE.
The neighbor commands use the format 10.a.a.a and 10.b.b.b. Replace
the values of a and b with those assigned to your Group in the CE/PE lab
aids (for example, for Group 5, a=5 and b= 6 so the neighbor command
10.a.a.a would be 10.5.5.5).
1. Create EFPs on PEa and PEb bundle interfaces with the parameters
listed in Table 2. Add a description on the PEa EFP: Group x EoMPLS
E-Line PW Backup and on the PEb EFP: Group x EoMPLS. Check
your EFP configuration before committing it.
2. Commit your configuration on both routers.
3. Verify the state of your EFPs.
Task 2. Create an EoMPLS Pseudowire Cross-connect

1. Create an EoMPLS cross-connect from PEa to PEb. Use the criteria
listed in Table 2.
! In which mode do you create the PW crossconnect?
_____________________________________________________________

Lab 13 Part 2 ! EoMPLS E-Line
! What is the state of the crossconnect at this point?

_____________________________________________________________
2. On PEb, create an EoMPLS cross-connect back to PEa. Use the
assignments listed in Table 2.
3. Verify and commit your configuration.
4. Verify the state of your EoMPLS cross-connects.
! What type of crossconnect segments have you created? What is
their state?
_____________________________________________________________
! What command will give you a list of different crossconnect types
and their current state?
_____________________________________________________________
Task 3. Test connectivity across the EoMPLS E-Line.

1. Log into CEa and CEb and use the ping command to test connectivity
across the EoMPLS E-Line.
! Must pseudowire identifiers on each end of the PW match?
_____________________________________________________________
! What pseudowire type is being used?
_____________________________________________________________
Task 4. (Optional) Configure an EoMPLS PW across an MPLS TE tunnel

Preferred Path.
Rebuild your pseudowires and configure them to use the MPLS TE tunnels
configured in the MPLS TE lab.
Guidelines for Tunnel configuration using the pw-class and preferred-
path command can be found in the Student Guide. Define your own name
for the pw-class.

Part 3 ! EoMPLS with PW Backup

Overview
Redundancy in the core portion of the network is critical to providing end-
to-end high availability of the Carrier Ethernet services. The core
pseudowires built thus far have no type of protection scheme which could
provide service protection in event of PE or CE failure. In this lab, you will
create backup PWs to add redundancy to the EoMPLS E-Line service.
Visual Objective
x = Group #
PEa 0/2/0/
Int vlan x1
192.168.x1.1
3,4
IP/MPLS
CEa FE0/ 1,2
Int vlan x1
192.168.x1.2 PEb 0/2/0/ Primary PW
CEb FE0/
15,16
22,23
Shut EFP parent interface to
force a PW switchover
Int vlan x1 PEc 0/2/0/ Backup PW
192.168.x1.3
CEc FE0/ 17
24
Ping between CEa and CEc SVIs to verify L2VPN connectivity Backup EFP sub-interface
after switchover on backup PE

Lab 13 Part 3 ! EoMPLS with PW Backup
EoMPLS with PW Backup Topology
x = Group #
Trunk#1
Int vlan x1 2. backup xconnect

SVI#1 192.168.x1.1 PEa 0/2/0/
l2vpn
1,2 3,4 p2p PEa_PEb_x_A
CEa FE0/ neighbor 10.b.b.b pw-id x01
backup neighbor 10.c.c.c pw-id x01
SVI#3
Int vlan x1
PEb 0/2/0/ 3. backup xconnect
192.168.x1.3
l2vpn
17 PEc 0/2/0/ p2p PEa_PEb_x_A_BACKUP
CEc FE0/ int gigabitEthernet0/2/0/24.1
neighbor 10.a.a.a pw-id x01
24
Trunk#3 PE1 1. EFP#3
switchport trunk allowed vlan x1 interface gigabitEthernet 0/2/0/24.1 l2transport
Table 1. EoMPLS E-Line with PW Backup encap dot1q x1
Configuration
Table 3. EoMPLS with PW Backup
Group PEa PEc

int bundle-eth x00.2 l2transport
int gigabitEthernet 0/2/0/24.1 l2transport
encap dot1q x1
encap dot1q x1
L2vpn
L2vpn
X xconnect group AC2PW_x
p2p PEa_PEb_x_a
p2p PEa_PEb_x_a_BACKUP
int bundle-eth x00.2
int gigabitEthernet 0/2/0/24.1
backup neighbor 10.c.c.c pw-id x01
Group CEc
int Vlan x1
192.168.x1.3
int fastethernet 0/17
X
switchport mode
trunk
switchport trunk
allowed vlan x1

Task 1. Create Backup EFPs.

1. On the Backup router PEc, create an EFP using the parameters
assigned to your Group in Table 3. Add a description that reads Group
x EoMPLS PW Backup.
2. Verify and commit the EFP configuration.
3. Verify the state of the EFP.
Task 2. Create a Backup PW from the Hub PE.

1. On PEa, in L2VPN configuration mode, identify the EoMPLS E-Line
crossconnect you created in the previous lab. Create a Backup PW
from PEc with the parameters specified in Table 3.
! Under what submode of L2VPN config mode do you configure a
Backup PW?
_____________________________________________________________
3. Issue the show l2vpn xconnect detail command. Check the state of
your crossconnect segments.
! What is the state of the backup PW? Explain the current state.
_____________________________________________________________
_____________________________________________________________
Task 3. Create a Backup PW from the Backup PE.

1. On PEc, in L2VPN configuration mode create a PW to PEa with the
parameters specified in Table 3.
! What is the state of the backup PW now? Is this correct?
_____________________________________________________________
! What is the state of the primary PW?
_____________________________________________________________
3. From CEa, ping the Backup CE (CEc SVI in VLAN x1).
! Was it successful? Why?
_____________________________________________________________
4. Force a switch from the Primary PW (PEa to PEb) to the Backup PW
(PEa to PEc) by entering a shutdown command on the EFP on PEb.

Lab 13 Part 3 ! EoMPLS with PW Backup
6. From CEa, ping the Backup CE (CEc SVI in VLAN x1).

! Was it successful? Why?
_____________________________________________________________
7. Enter the no shutdown command on the EFP on PEb.
! Did the Primary PW revert to active?
_____________________________________________________________
8. (Optional) Another way to perform a switchover is by using the l2vpn
switchover neighbor A.B.C.D pw-id X command on the active PW.

Summary
EoMPLS Service
Configure EFP encapsulation, matching, and rewrite.

Configure P2P EoMPLS E-Line service.
Verify Layer 2 Ethernet service operation.
Configure pseudowire redundancy.
Verify redundancy and resiliency operation.

Lab 14
Local Multipoint Layer 2 Service
Overview
Description
Cisco IOS XR commands used to implement local E-LAN Carrier Ethernet
services on a Cisco Aggregation Services Router 9000 (ASR 9000).
This lab involves EFP and bridge domain creation on a single ASR 9000
provider edge (PE) router. Configuration is performed on the PE devices
only. The CE and P devices are preconfigured. The diagram below
illustrates the objectives of this lab.
Objectives
Configure EFPs
Configure a multipoint bridge domain

Verify Local E-LAN service operation

Local Multipoint Layer 2 Service Lab 14
Visual Objective
x = Group #
Ping betw een CE SVIs to
Local E-LAN
L2VPN
Int vlan x2 Local bridge-
192.168.x2.1 PEa 0/2/0/ domain
CEa
1,2 3,4
FE0/ BD
20,21
Int vlan x2
192.168.x2.2 PE125
CEb 13,14 EFPs on Bundle sub-

FE0/ interfaces and non-
Int vlan x2 Bundled sub-interfaces
192.168.x2.3 Trunk ports on
Bundled interfaces
CEc
18
FE0/ Trunk ports on physical
interfaces

Lab References
Command List
materials.
configure t
interface
L2transport
encapsulation
rewrite
L2vpn
bridge group
bridge-domain
error-disable
show interface
show l2vpn bridge-domain
show l2vpn forwarding

Part 1!Multipoint Local E-LAN

Overview
Point-to-point Layer 2 Ethernet services provide connectivity between two
Ethernet flow points (EFPs). To provide local connectivity to more than
two EFPs, a bridge-domain must be created. In this portion of the lab, you
will create three local EFPs and you will connect them with a unique
bridge-domain. Two of the EFPs are built on existing bundle interfaces.
One EFP is built on a physical interface.
Local E-LAN Configuration

interface bundle-Ethernet x00.3 l2transport
switchport trunk allowed vlan add x2 encap dot1q x2
switchport trunk allowed vlan add x2 interface bundle-Ethernet x01.2 l2transport

encap dot1q x2
Int vlan x2
192.168.x2.1 PEa 0/2/0/
CEa
1,2 3,4
FE0/ BD
20,21
Int vlan x2
192.168.x2.2 PE125
l2vpn
CEb 13,14 bridge group BG_x bridge-domain BD_x
FE0/ interface bundle-Ethernet x00.3
interface bundle-Ethernet x01.2
Int vlan x2 interface gigabitEthernet 0/2/0/25.1
192.168.x2.3
CEc FE0/ 18 interface gigabitEthernet 0/2/0/25.1 l2transport

switchport mode trunk encap dot1q x2
switchport trunk allowed vlan x2

Lab 14 Part 1!Multipoint Local E-LAN
Table 1. Local E-LAN Configuration

Table 1. Local E-LAN Configuration
Group PEa
encap dot1q x2
encap dot1q x2
int gigabitEthernet 0/2/0/25.1 l2transport
encap dot1q x2
X
l2vpn
bridge group BG_x
bridge-domain BD_x
Group CEa CEb CEc

int Vlan x2
int Vlan x2
int Vlan x2 192.168.x2.3
192.168.x2.1
192.168.x2.2 int fastethernet 0/18
int port-channel 1
X int port-channel 5 switchport mode
switchport trunk allowed trunk
switchport trunk allowed vlan vlan add x2 switchport trunk
add x2
allowed vlan x2
Task 1. Create local EFPs.

1. On the customer-facing GE line card of your assigned router, create
three EFPs using the parameters assigned to your group in Table 1.
Add a description to the EFP that says Group x Local E-LAN.
2. Verify EFP configuration before committing.
! What is the state of the three EFPs you just created?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
Task 2. Create a bridge-domain and add local EFPs.

1. Create an L2VPN with a bridge group and bridge-domain, with the
2. Add the newly created, local EFPs to the bridge-domain.
3. Verify the bridge-domain configuration before committing.

! What is the state of the bridge-domain?

_____________________________________________________________
! What command did you use to retrieve this information?
_____________________________________________________________
Task 3. Test connectivity across the Local E-LAN.

1. Log into CEa, CEb, and CEc and use the Ping command between all
CEs to test connectivity across the Local E-LAN service.
! How many ACs are connected? What is their state?
_____________________________________________________________
Task 4. Check MAC learning within the Local E-LAN.

1. Log into PEa and issue the command to synchronize the RP MAC table
to that of the NPUs.
! What command did you issue?
_____________________________________________________________
! What MAC address was learned and on what port?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
! What command did you use to retrieve the MAC address table?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
! How old is that MAC address? When will it age out?
_____________________________________________________________

Lab 14 Summary
Summary
Local Multipoint Layer 2 Service
Configure EFPs
Configure a multipoint bridge domain
Verify Local E-LAN service operation


Lab 15
Virtual Private LAN Service
Overview
Description
The goal of this exercise is to familiarize the student with various Cisco
IOS XR commands used to implement Virtual Private LAN Service (VPLS)
E-LAN Carrier Ethernet service across an Internet Protocol and
multiprotocol label switching (IP/MPLS)-enabled Cisco ASR 9000 network.
There are two parts to this lab. Part One involves Ethernet flow point
(EFP), bridge-domain (BD) and pseudowire (PW) mesh creation across
three Cisco ASR 9000 provider edge (PE) routers, which establishes a
static VPLS. Part Two shows the benefits of VPLS creation using PW
autodiscovery.
Configuration is performed on the PE devices only. The customer edge
(CE) and core (P) devices are preconfigured. The figure on the following
page shows the objectives of this lab.
Objectives
Configure EFPs
Configure multipoint VPLS E-LAN service
Configure VPLS using PW autodiscovery

Verify VPLS service operation

Virtual Private LAN Service Lab 15
Visual Objective
Trunk ports on
non-Bundled PEa 0/2/0/
interfaces
Int vlan x3 5 IP/MPLS
192.168.x3.1 VSI
VPLS E-LAN
3 L2VPN
CEa
FE0/
EFPs on sub-
Int vlan x3 interfaces
Bridge-
192.168.x3.2
domains with
PEb 0/2/0/ VFIs (VPLS)
CEb
FE0/ 19
Int vlan x3 VSI

192.168.x3.3
26
CEc
FE0/ 20 PEc 0/2/0/
Ping between CE SVIs to VSI

27
verify L2VPN connectivity

Lab References
Command list
materials.
l2transport rd auto
l2vpn route-target
bridge group signaling-protocol bgp
bridge-domain ve-id
l2vfi
interface
neighbor
pw-id
show l2vpn bridge-domain
router bgp
address-family l2vpn vpls-vpws
vpn-id
autodiscovery bgp

Part 1!Multipoint VPLS E-LAN

Overview
VPLS is used to provide multipoint connectivity between two or more EFPs
on PEs in an MPLS cloud. EFPs are linked to a BD that is combined with
a VPLS virtual forwarding interface (VFI). In this portion of the lab, your
group will create EFPs and a BD on three different pods. These BDs are
connected by a VFI mesh, resulting in a multipoint VPLS E-LAN.
VPLS Configuration
interface gigabitEthernet 0/2/0/5.1 l2transport

encap dot1q x3
switchport trunk allowed vlan x3 PEa 0/2/0/
Int vlan x3 5 VSI
192.168.x3.1 l2vpn
bridge group BG_x0 bridge-domain BD_x0
3 interface gigabitEthernet 0/2/0/5.1
CEa vfi x0
FE0/
switchport mode trunk neighbor 10.b.b.b pw-id x02
switchport trunk allowed vlan x3 neighbor 10.c.c.c pw-id x02
interface gigabitEthernet 0/2/0/26.1 l2vpn
Int vlan x3 l2transport bridge group BG_x0 bridge-domain BD_x0
192.168.x3.2 encap dot1q x3 interface gigabitEthernet 0/2/0/26.1
vfi x0
CEb 19
neighbor 10.c.c.c pw-id x02
FE0/
Int vlan x3 VSI
192.168.x3.3
26 l2vpn
PEb 0/2/0/
bridge group BG_x0 bridge-domain BD_x0
interface gigabitEthernet 0/2/0/27.1
CEc vfi x0
FE0/ 20 PEc 0/2/0/ neighbor 10.a.a.a pw-id x02
switchport trunk allowed vlan x3 IP/MPLS
27 VSI
encap dot1q x3

Lab 15 Part 1!Multipoint VPLS E-LAN
Table 1. VPLS E-LAN Configuration

Table 1. VPLS E-LAN Configuration
Group PEa PEb PEc
int gigabitEthernet 0/2/0/5.1 int gigabitEthernet 0/2/0/26.1 int gigabitEthernet 0/2/0/27.1

l2transport l2transport l2transport
encap dot1q x3 encap dot1q x3 encap dot1q x3
l2vpn l2vpn l2vpn
bridge group BG_x0 bridge group BG_x0 bridge group BG_x0
X bridge-domain BD_x0 bridge-domain BD_x0 bridge-domain BD_x0
vfi x0 vfi x0 vfi x0
neighbor 10.b.b.b pw-id x02 neighbor 10.c.c.c pw-id x02 neighbor 10.a.a.a pw-id x02
neighbor 10.c.c.c pw-id x02 neighbor 10.a.a.apw-id x02 neighbor 10.b.b.b pw-id x02
Group CEa CEb PEc

int Vlan x3 int Vlan x3 int Vlan x3
192.168.x3.1 192.168.x3.2 192.168.x3.3
X int fastethernet 0/3 int fastethernet 0/19 int fastethernet 0/20
switchport mode trunk switchport mode trunk switchport mode trunk
switchport trunk allowed vlan x3 switchport trunk allowed vlan x3 switchport trunk allowed vlan x3
Task 1. Create EFPs on each PE.

1. On PEa, PEb, and PEc, create EFPs using the parameters assigned to
your group in Table 1.
2. Add a description to each EFP that reads Group x VPLS.
3. Verify and commit EFP configuration
4. Verify the state of the EFPs. If necessary, check the configuration of
the parent interfaces to ensure that the interface speed is set to 100
Mbps using the speed 100 command.
Task 2. Create a BD and add local EFPs.

1. Create an L2VPN with a bridge group and BD at each PE. Use the
2. Add the newly created, local EFPs to the BD, one per PE.
3. Verify and commit the BD configuration.
4. Verify the BD state.
! What MAC address(es) have been learned in the BD so far?
_____________________________________________________________

! What command were you prompted to enter before viewing the

MAC table?
_____________________________________________________________
! What type of L2VPN have you created so far?
_____________________________________________________________
Task 3. Create a Layer 2 VFI within the BD (VSI)

1. At each assigned PE, create a VFI and specify a PW mesh to the two
neighbors. You should create a total of six PWs between all of the
neighbors in your VPLS.
2. Verify the VSI before committing the configuration.
4. Verify the VPLS configuration.
! On PEa, how many ACs, VFIs, and PWs are connected? What is
their state?
_____________________________________________________________
Task 4. Test connectivity across the VPLS service.

1. Log into CEa, CEb, and CEc and use the ping command between all
CEs to test connectivity across the VPLS E-LAN service.
! What MAC address(es) have been learned?
_____________________________________________________________

Lab 15 Part 2!Configuring VPLS with BGP-Autodiscovery
Part 2!Configuring VPLS with BGP-Autodiscovery

Overview
Manual VPLS creation, PE addition, and PE deletion from an existing
VPLS require detailed configuration. Configuring VPLS with BGP
autodiscovery (BGP-AD) allows PEs to discover when they share L2VPN
instances. BGP also provides the signaling to automatically provision the
necessary PWs between PEs. In this portion of the lab, create a new VPLS
using BGP-AD.
Visual Objective
Trunk ports on
non-Bundled
interfaces PEa 0/2/0/
Int vlan x4 5 IP/MPLS
192.168.x4.1 VSI
3
CEa VPLS E-LAN
FE0/ with BGP Auto-
EFPs on sub-
Discovery of PW
Int vlan x4 interfaces
mesh
192.168.x4.2
PEb 0/2/0/
CEb
FE0/ 19
Int vlan x4 VSI

192.168.x4.3
26
CEc Bridge-
FE0/ PEc 0/2/0/ domains with
20
VFIs (VPLS)
Ping between CE SVIs to VSI

27
verify L2VPN connectivity

VPLS BGP-AD Configuration (CEs and EFPs)

switchport trunk allowed vlan add x4 PEa 0/2/0/
Int vlan x4 5 VSI
192.168.x4.1
3 encap dot1q x4
CEa
switchport modeFE0/
trunk
interface gigabitEthernet 0/2/0/26.2
Int vlan x4 l2transport
192.168.x4.2 encap dot1q x4
CEb 19
FE0/
Int vlan x4 VSI
192.168.x4.3
26
PEb 0/2/0/
CEc interface gigabitEthernet 0/2/0/27.2 l2transport

FE0/ 20 encap dot1q x4
switchport trunk allowed vlan add x4 IP/MPLS
27 VSI
PEc 0/2/0/
VPLS BGP-AD Configuration (PEs)
PEa 0/2/0/ router bgp 650 00

address-f amily l2 vpn vpls-vpws
neighbor 10.b.b.b
5 VSI address-fa mily l2vpn vpls-vpw s
neighbor 10.c.c.c
address-fa mily l2vpn vpls-vpw s
l2vpn
bridge group BG_x1 bridge-domain BD _x 1
router bgp 650 00 vfi x1
address-f amily l2 vpn vpls-vpws
vpn-id x00
neighbor 10.a.a.a autodiscovery bgp
address-fa mily l2vpn vpls-vpw s rd auto
neighbor 10.c.c.c route-target x.x.x.x: xxx
address-fa mily l2vpn vpls-vpw s
PEb 0/2/0/ signaling-protocol bgp
ve-id a
l2vpn
bridge group BG_x1 bridge-domain BD _x 1
int gigabitEthernet 0/2/0/26.2 router bgp 650 00
vfi x1 address-f amily l2 vpn vpls-vpws
VSI
vpn-id x00 neighbor 10.a.a.a
26 autodiscovery bgp address-fa mily l2vpn vpls-vpw s
rd auto neighbor 10.b.b.b
route-target x.x.x.x: xxx address-fa mily l2vpn vpls-vpw s
signaling-protocol bgp
ve-id b l2vpn
PEc 0/2/0/ bridge group BG_x1 bridge-domain BD _x 1
vfi x1
vpn-id x00
IP/MPLS autodiscovery bgp
rd auto
27 VSI route-target x.x.x.x: xxx
signaling-protocol bgp
ve-id c

Table 2. VPLS BPG-AD Configuration (PEs)
Group PEa PEb PEc

int gigabitEthernet 0/2/0/5.2 l2tr ansport int gigabitEthernet 0/2/0/26.2 l2t ranspo rt int gigabitEthernet 0/2/0/27.2 l2t ranspo rt
encap dot1q x4 encap dot1q x4 encap dot1q x4
router bgp 650 00 router bgp 650 00 router bgp 650 00

address-f amily l2 vpn vpls-vpws address-f amily l2 vpn vpls-vpws address-f amily l2 vpn vpls-vpws
neighbor 10.b.b.b neighbor 10.a.a.a neighbor 10.a.a.a
address-fa mily l2vpn vpls-vpw s address-fa mily l2vpn vpls-vpw s address-fa mily l2vpn vpls-vpw s
neighbor 10.c.c.c neighbor 10.c.c.c neighbor 10.b.b.b
address-fa mily l2vpn vpls-vpw s address-fa mily l2vpn vpls-vpw s address-fa mily l2vpn vpls-vpw s
X l2vpn l2vpn l2vpn

bridge group BG_x1 bridge-domain bridge group BG_x1 bridge-domain bridge group BG_x1 bridge-domain
BD _x1 BD _x1 BD _x1
vfi x1 vfi x1 vfi x1
vpn-id x00 vpn-id x00 vpn-id x00
autodiscovery bgp autodiscovery bgp autodiscovery bgp
rd auto rd auto rd auto
route-target x.x.x.x: xxx route-target x.x.x.x: xxx route-target x.x.x.x: xxx
signaling-protocol bgp signaling-protocol bgp signaling-protocol bgp
ve-id a ve-id b ve-id c
Table 3. VPLS BGP-AD Configuration (CEs)
Group CEa CEb PEc

int Vlan x4 int Vlan x4 int Vlan x4
192.168.x4.1 192.168.x4.2 192.168.x4.3
int fastethernet 0/3 int fastethernet 0/19 int fastethernet 0/20
X
switchport mode trunk switchport mode trunk switchport mode trunk
switchport trunk allowed vlan switchport trunk allowed vlan switchport trunk allowed vlan
add x4 add x4 add x4
Task 1. Create EFPs on each PE.

1. Create EFPs on PEa, PEb, and PEc using the parameters assigned to
your group in Table 2.
2. Add a description to each EFP that reads Group x VPLS BGP-AD.
3. Verify and commit EFP configuration.
4. Verify the state of the EFPs. If necessary, check the configuration of
the parent interfaces to ensure that the interface speed is set to 100
Mbps using the speed 100 command.
Task 2. Create a BD and add local EFPs.

1. Create an L2VPN with a bridge group and BD at each PE using the

2. Add the newly created, local EFPs to the BD, one per PE.
3. Verify and commit the BD configuration.
4. Verify the BD state.
! What MAC address(es) have been learned in the BD so far?
_____________________________________________________________
! What type of L2VPN have you created so far?
_____________________________________________________________
Task 3. Configure BGP for L2VPN

BGP-AD requires provisioning of the BGP autonomous system (AS) with
the proper AFI/SAFI settings as well as the configuration of BGP AD and
signaling parameters per L2 VFI.
1. On PEa and PEb only, enter router bgp configuration mode and
provision the PEs with the BGP AS parameters listed in Table 2.
2. On PEa only, create a VFI and specify the VFI to use BGP for
autodiscovery and signaling using the parameters listed for your group
in Table 2. Commit the configuration on PEa.
! On PEa, which PW neighbors are connected?
_____________________________________________________________
3. On PEb only, create a VFI and specify the VFI to use BGP for
in Table 2.
4. Verify and commit the configurations on PEa and PEb.
! On PEa, what PW neighbors are connected?
_____________________________________________________________
! On PEa, what VE-ID is being advertised by the neighbor?
_____________________________________________________________
! Did all pings work? If not, which CE did not respond? Why?
_____________________________________________________________
6. On PEc only, enter router bgp configuration mode and provision the
PE with the BGP AS parameters listed in Table 2.
7. On PEc only, create a VFI and specify the VFI to use BGP for
in Table 2.
8. Verify and commit the configurations on PEc.
! Did all pings work?
_____________________________________________________________

Summary
VPLS
Configure EFPs
Configure multipoint VPLS E-LAN service
Configure VPLS using PW autodiscovery
Verify VPLS service operation

Lab 16
Ethernet Operations, Administration, and
Maintenance
Overview
Description
The goal of this exercise is to familiarize the student with various Cisco
IOS XR commands used to implement link-based and service-based
Ethernet Operations, Administration, and Maintenance (OAM) protocols.
There are two parts to this lab. Part One adds IEEE 802.3ah or Ethernet-
Operations, Administration, and Maintenance (E-OAM) to a PE-to-CE
link. Part Two adds IEEE 802.3ag or Ethernet-Connectivity Fault
Management (CFM) to a VPLS service.
Configuration is performed on the PE devices only. The customer edge
(CE) and core (P) devices are preconfigured
Objectives
Configure link-based E-OAM

Test E-OAM operation
Configure service-based CFM
Test CFM operation

Ethernet Operations, Administration, and Maintenance Lab 16
Lab References
Command list
materials.
ethernet oam ethernet cfm
profile domain
remote-loopback level
ethernet oam service
error-disable continuity-check interval
ethernet oam loopback enable ethernet cfm mep
ethernet oam loopback disable mep-id
show ethernet oam discovery ping ethernet cfm
show ethernet oam statistics traceroute ethernet cfm
show ethernet oam

configuration
remote

Lab 16 Part 1! Local E-LAN with E-OAM on an Access Link
Part 1! Local E-LAN with E-OAM on an Access Link

Overview
In this lab, you will enable E-OAM on the physical port that links your
PEa router to the CEc. This link is part of the Local E-LAN configuration
created in a previos lab. CEc is preconfigured with E-OAM as shown in the
diagram below.
E-OAM on an Access Link Configuration
1. Create E-OAM profile x = Group #

ethernet oam profile EOAM_x
action
critical-event error-disable-interface
dying-gasp error-disable-interface
link-fault error-disable-interface
session-down error-disable-interface
remote-loopback
mib-retrieval
PEa 0/2/0/
CEc 18 25
FE0/
PE1 2. Apply to physical interface
interface gigabitEthernet 0/2/0/25

Peer#1
ethernet oam
ethernet oam remote-loopback supported
ethernet oam remote-failure link-fault action error-disable interface

Table 1. Local E-Line with E-OAM on Access Configuration
Group PEa
action
critical-event error-disable-interface
dying-gasp error-disable-interface
link-fault error-disable-interface
X session-down error-disable-interface
remote-loopback
mib-retrieval
int gigE 0/2/0/25

Group CEc
ethernet oam
X ethernet oam remote-loopback supported
ethernet oam remote-failure link-fault action error-disable interface
Task 1. Create an E-OAM profile in global configuration mode.

E-OAM features can be enabled two ways, directly using interface
configuration mode or with an E-OAM profile that can be applied to many
interfaces. In this lab, you will enable E-OAM by creating an E-OAM
profile in global configuration mode and applying it to a physical interface.
1. Create an Ethernet OAM profile on your PEa router using the
parameters listed in Table 1.
! What command do you use to view an Ethernet OAM profile?
_____________________________________________________________
! What features does this profile enable?
_____________________________________________________________
Task 2. Apply E-OAM profiles to physical ports.

1. Apply the E-OAM profiles you just created to the physical interfaces
assigned to your group in Table 1. Apply the profiles in interface
configuration mode.
2. Add a description to the physical interface that states Group x Local
E-LAN, E-OAM
3. Verify and commit the E-OAM configuration.

Lab 16 Part 1! Local E-LAN with E-OAM on an Access Link
Task 3. Verify E-OAM Operation.

1. Check the E-OAM session discovery information on PEa. Log into your
PEa device and use show commands to answer the following questions:
! What is the operational mode of the remote (CE) client?
_____________________________________________________________
! What is the operational state of the local (PE) client?
_____________________________________________________________
! What is the remote client (CE) MAC address?
_____________________________________________________________
! What command do you use to view what the E-OAM features that
are currently configured?
_____________________________________________________________
! What command do you used to view the local E-OAM event
counters?
_____________________________________________________________
2. Now check the E-OAM session discovery information on CEc. Log into
your CEc device and use show commands to answer the following
questions:
! What is the operational state of the local (CE) client?
_____________________________________________________________
! What command do you use to view which E-OAM features that are
currently configured? _________________________________________
! What command do you used to view the local E-OAM event
counters? ____________________________________________________
3. With E-OAM configuration verified on both sides, you will now test E-
OAM operation Connect to your CEc device via its Console connection
so that you can view log messages.
4. On PEa, shut down the interface on which you have just enabled E-
OAM.
! What related log messages do you see coming from CEc?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________

5. On PEa, enable (no shut) the interface you just shut down.
! Did the E-OAM session and the physical port come back UP?
_____________________________________________________________
Task 4. (Optional) Test E-OAM Loopback and MIB-Retrieval Operation.

1. You optionally force the CEc device to go into E-OAM Loopback mode
from the PEa device. Log into PEa and enter the command to force
CEc into E-OAM Loopback mode.
! What command did you enter?
_____________________________________________________________
! What is the Loopback Status of the E-OAM session on PEa?
_____________________________________________________________
! Can you ping the other CEs from CEc?
_____________________________________________________________
2. Enter the command to disable Loopback mode on PEa.
! What command did you enter?
_____________________________________________________________
Task 5. (Optional) Test E-OAM MIB-Retrieval Operation.
1. Enter the command to view CEcs E-OAM discovery information from
the perspective of PEa.
! What command did you receive?
_____________________________________________________________
! What message did you receive?
_____________________________________________________________
_____________________________________________________________
_____________________________________________________________
Although the Cisco ASR 9000 supports the MIB Retrieval feature,
the ME3400 CE device does not yet support this particular E-OAM
feature.

Lab 16 Part 2 ! VPLS E-LAN with CFM
Part 2 ! VPLS E-LAN with CFM

Overview
In this lab, you will create service-based operations, administration, and
management (OAM) using CFM. CFM provides end-to-end fault detection
and management between the EFPs of a service. In this lab, you create
three CFM maintenance endpoints (MEPs) on top of the VPLS E-LAN
service you manually created in a previous lab. Ethernet CFM pings and
traceroutes can then be tested between MEPs.
Visual Objective
CFM domain and

EFP MEP#1 service
Layer 2 Ping PEa 0/2/0/ configuration
and Trace
between CFM CEa FE0/ 5 VSI
MEPs
3 IP/MPLS
CFM domain and
CEb FE0/ service
configuration
19 PEb 0/2/0/
EFP MEP#2 CFM domain and

VSI
26 service
20 configuration
PEc 0/2/0/
CEc FE0/
VSI
27 Previously
configured
EFP MEP#3 VPLS

VPLS with CFM Configuration
ethernet cfm domain DOM_x level 3

int gigabitEthernet 0/2/0/5.1 L2transport service SER_x bridge group BG_x0 bridge-
ethernet cfm mep domain DOM_x service SER_x mep-id 1 domain BD_x0
continuity-check interval 10s
CEa FE0/ 5 VSI
3 IP/MPLS
PEa 0/2/0/
ethernet cfm domain DOM_x level 3
CEb FE0/ service SER_x bridge group BG_x0 bridge-
domain BD_x0
19 PEb 0/2/0/ continuity-check interval 10s
int gigabitEthernet 0/2/0/26.1 L2transport
ethernet cfm mep domain DOM_x service SER_x mep-id 2
VSI
26 ethernet cfm domain DOM_x level 3
20 service SER_x bridge group BGx0 bridge-
PEc 0/2/0/ domain BD_x0
continuity-check interval 10s
CEc FE0/
VSI
27
int gigabitEthernet 0/2/0/27.1 L2transport

ethernet cfm mep domain DOM_x service SER_x mep-id 3
Table 2. CFM Configuration in Cisco IOS XR
Table 2. VPLS with CFM Configuration

Group PEa PEb PEc
ethernet cfm ethernet cfm ethernet cfm

domain DOM_x level 3 domain DOM_x level 3 domain DOM_x level 3
service SER_x bridge group service SER_x bridge group service SER_x bridge group
BG_x0 bridge-domain BD_x0 BG_x0 bridge-domain BD_x0 BG_x0 bridge-domain BD_x0
continuity-check interval 10s continuity-check interval 10s continuity-check interval 10s
X
int gig 0/2/0/5.1 L2transport int gig 0/2/0/26.1 L2transport int gig 0/2/0/27.1 L2transport
ethernet cfm mep domain ethernet cfm mep domain ethernet cfm mep domain DOM_x
DOM_x service SER_x mep-id 1 DOM_x service SER_x mep-id 2 service SER_x mep-id 3
Task 1. Create a CFM domain in global configuration mode.CFM features are

established in global configuration mode and are applied per service.
Lab 16 Part 2 ! VPLS E-LAN with CFM
1. Enter Ethernet CFM configuration mode from global configuration

mode. Specify a domain name and a level, as assigned in Table 2.
2. Specify a Continuity Check Message interval of 10 seconds. If CCM is
not enabled, CFM peers are not visible and CFM loopback and
linktrace do not work.
Task 2. Enable CFM MEP on EFPs

1. Following the assignments in Table 2 for your group, enable CFM on
the existing VPLS E-LAN Layer 2 service by applying the CFM
configuration and MEPs to EFPs on all endpoints of the service (PEa,
PEb, and PEc).
2. Verify and commit your configuration.
! What MAC addresses are being used by your local MEP?
_____________________________________________________________
! What MAC addresses are being used by your remote MEPs?
_____________________________________________________________
! How many CCM messages have been dropped?
_____________________________________________________________
Task 3. Ping and Traceroute to EFPs at Layer 2 using CFM

1. Log into PEa and generate a Layer 2 Ethernet CFM Ping to all other
MEP endpoints.
! Are all other MEPs reachable?
_____________________________________________________________
2. Log into PEa and generate a Layer 2 Ethernet CFM Traceroute to all
other MEP endpoints.
! How many hops to MEP #1, MEP #2 and MEP #3?
_____________________________________________________________

Summary
Ethernet Operations, Administration, and Maintenance
Configure link-based E-OAM

Test E-OAM operation
Configure service-based CFM
Test CFM operation

Lab 17
Cisco ASR 9000 Layer 2 Multicast
Overview
Description
Cisco IOS XR commands used to implement Layer 2 multicast in
conjunction with a multipoint Carrier Ethernet service on a
Cisco ASR 9000 PE. Customer edge (CEs) devices are provisioned to
simulate multicast routers and hosts and their Layer 3 multicast traffic is
snooped by the Layer 2 Internet Group Management Protocol (IGMP)
Snooping-enabled bridge-domain (BD).
Configuration is performed on the provider edge (PE) devices only. The CE
and core (P) devices are preconfigured. The diagram on the following page
illustrates the objectives of this lab.
Objectives
Configure an IGMP Snooping profile.
Configure your existing multipoint Local E-LAN service with an IGMP
snooping profile.
Verify Layer 2 multicast configuration.
Verify IGMP Snooping action.

Cisco ASR 9000 Layer 2 Multicast Lab 17
Visual Objective
int vlan x2
ip pim dense-mode
Int vlan x2
192.168.x2.1 PEa 0/2/0/
CEa 1,2 3,4

FE0/
interface vlan x2 20,21 BD
Int vlan x2 ip igmp join-group 239.x0.x0.x0
192.168.x2.2 PE1
25
CEb 13,14 igmp snooping profile IGMPSN_x

FE0/ router-alert-check disable
interface vlan x2
Int vlan x2 ip igmp join-group 239.x0.x0.x0 l2vpn
192.168.x2.3 bridge group BG_x bridge-domain BD_x
igmp snooping profile IGMPSN_x
CEc FE0/ 18

Lab References
Command List
materials.
igmp snooping profile
l2vpn
bridge group
bridge-domain
show igmp snooping bridge-domain
show igmp snooping group
show igmp snooping port
show igmp snooping profile
show igmp snooping summary

Part 1!Configuring IGMP Snooping Profiles

IGMP snooping is enabled within a BD by attaching an IGMP snooping
profile. BD IGMP snooping attributes can be set in the BD and port-
specific IGMP snooping attributes can be set per port by attaching an
additional port profile.
IGMP Snooping Configuration

int vlan x2
ip pim dense-mode
ip igmp join-group 239.x0.x0.x0
Int vlan x2
192.168.x2.1 PEa 0/2/0/
CEa
1,2 3,4
FE0/ BD
interface vlan x2 20,21
Int vlan x2 ip igmp join-group 239.x0.x0.x0
192.168.x2.2 PE125
CEb 13,14 igmp snooping profile IGMPSN_x

FE0/ router-alert-check disable
interface vlan x2
Int vlan x2 ip igmp join-group 239.x0.x0.x0 l2vpn
192.168.x2.3 bridge group BG_x bridge-domain BD_x
CEc FE0/ 18
Table 1. IGMP Snooping Profiles

Table 1. IGMP Snooping Profiles
Group PEa
router-alert disable
l2vpn
X bridge group BG_x
bridge-domain BD_x
Group CEa CEb PEc

int Vlan x2
X ip pim dense-mode
ip igmp join-group 239.x0.x0.x0 ip igmp join-group 239.x0.x0.x0
ip igmp join-group 239.x0.x0.x0
Lab 17 Part 1!Configuring IGMP Snooping Profiles
Task 1. Create a BD IGMP snooping profile.

1. Create a BD-level IGMP snooping profile. Use the profile name and
attributes assigned to your group in Table 1.
2. Verify IGMP snooping profile settings.
! Will this IGMP Snooping profile apply to the ports in the BD?
_____________________________________________________________
4. On PEa, enter the show igmp snooping groups command.
! What output did you get? Why?
_____________________________________________________________
Task 2. Enable IGMP snooping and assign BD attributes.

Creation of the IGMP snooping BD and port-level profiles is the first step
in configuring IGMP snooping. The second step is to attach profiles to the
BD and specific ports as required. In this portion of the lab, you will
attach IGMP snooping profiles that will implement specific IGMP snooping
operation. Use the assignments for your group listed in Table 1.
1. Enter BD configuration mode on the PE assigned to your group.
2. Apply the IGMP snooping BD profile as assigned in Table 1.
4. Verify IGMP snooping profile settings.
5. Verify that the IGMP snooping process is active.
Task 3. View IGMP Snooping output.

Layer 2 multicast IGMP snooping is now enabled, and the IGMP snooping
process is running. Layer 2 multicast architecture will be learned from
multicast join or query packets ingress on the interfaces on which IGMP
Snooping is configured.
1. Enter show command to view the IGMP snooping group information.
! How many groups were learned by the BD?
_____________________________________________________________
! How many ports are active in the BD? __________________________
! How many Mrouter ports were learned by your groups BD?
_____________________________________________________________
! What is the IP address of the Querier?
_____________________________________________________________

Summary
Cisco ASR 9000 Layer 2 Multicast
Configure an IGMP Snooping profile.

Configure your existing multipoint Local E-LAN service with an IGMP
snooping profile.
Verify Layer 2 multicast configuration.

Verify IGMP Snooping action.

Part Number: ASR9KE

SLG BOOK ASR9KE v4.0.1 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SLG BOOK ASR9KE v4.0.1 PDF

Caricato da

Copyright:

Formati disponibili

Cisco ASR 9000

italics font Arguments for which you supply values are in

string A non-quoted set of characters. Do not use

separator (>) Shows the menu path.

2011 Cisco Systems, Inc. Version 4.0.1 v

Lab 1 ................................................................................................................. 11!

Lab 2 ................................................................................................................. 21!

Lab 3 ................................................................................................................. 31!

Lab 4 ................................................................................................................. 41!

vi Version 4.0.1 ASR 9000 Series Essentils

Lab 5 ................................................................................................................. 51!

Lab 6 ................................................................................................................. 61!

Lab 7 ................................................................................................................. 71!

Lab 8 ................................................................................................................. 81!

Lab 9 ................................................................................................................. 91!

Lab 10 ............................................................................................................. 101!

2011 Cisco Systems, Inc. Version 4.0.1 vii

Lab 11 ............................................................................................................. 111!

Lab 12 ............................................................................................................. 121!

Lab 13 ............................................................................................................. 131!

Lab 14 ............................................................................................................. 141!

Lab 15 ............................................................................................................. 151!

Lab 16 ............................................................................................................. 161!

viii Version 4.0.1 ASR 9000 Series Essentils

Lab 17 ............................................................................................................. 171!

2011 Cisco Systems, Inc. Version 4.0.1 ix

x Version 4.0.1 ASR 9000 Series Essentils

2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids -1

Operation Administration and

Lab Aids - 2 Version 4.0.1 Cisco ASR 9000 Series Essentials

Accessing the Lab

OutofBand Management Netw ork

OutofBand Mgmt LAN supports: Telnet, TFTP, HTTP

Device Mgmt Address Device Mgmt Address Device Mgmt Address

Device Mgmt Address Device Mgmt Address

2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids - 3

Owner SDR Topology

MgmtEth 0/RSP0/CPU0/0 GE MgmtEth 0/RSP0/CPU0/0

MgmtEth 0/RSP1/CPU0/0 MgmtEth 0/RSP1/CPU0/0

MgmtEth 0/RSP1/CPU0/0 2/ 1 MgmtEth 0/RSP1/CPU0/0

MgmtEth RSP 0 17 2.21. 116. 10 MgmtEth RSP 0 17 2.21. 116. 40

Lab Aids - 4 Version 4.0.1 Cisco ASR 9000 Series Essentials

MgmtEth RP 0 17 2.21.1 16.9 1 MgmtEth RP 0 17 2.21.1 16.9 4

Pod 2 IP/MPLS Pod 5

Cisco ME3400 CEs

PE-CE physical connections are illustrated in each

Group to CE and PE Mapping Key

Group # PEa PEb PEc CEa CEb CEc

2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids - 5

RSP0 MGMTETH RSP1 MGMTETH IP VIRTUAL

ROUTER GE0 IP ADDRESS

Lab Aids - 6 Version 4.0.1 Cisco ASR 9000 Series Essentials

ROUTER INTERFACE IP ADDRESS

2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids - 7

PE1 GIGABITETHERNET 0/2/0/1 192.168.111.1/24

Lab Aids - 8 Version 4.0.1 Cisco ASR 9000 Series Essentials

IS-IS NET (NSAP):

ROUTER NET (NSAP}

2011 Cisco Systems, Inc. Version 4.0.1 Lab Aids - 9

Accessing the Lab Tear out

OutofBand Management Netw ork

OutofBand Mgmt LAN supports: Telnet, TFTP, HTTP

Device Mgmt Address Device Mgmt Address Device Mgmt Address