Cisco ASR 901 Series Aggregation Services Router

Cisco ASR 901 Series Aggregation
Services Router Software Configuration
Guide
November 21, 2013
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-23826-09
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required
to correct the interference at their own expense.
The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not
installed in accordance with Cisco installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply
with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection
against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.
Modifying the equipment without Cisco written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices.
In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications
at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its
peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
• Turn the television or radio antenna until the interference stops.
• Move the equipment to one side or the other of the television or radio.
• Move the equipment farther away from the television or radio.
• Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits
controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
Copyright © 2011-2013, Cisco Systems, Inc.
All rights reserved. Printed in USA
C O N T E N T S
Document Revision History
Objectives
xxxvii
xlvii
Audience
xlvii
Organization
xlvii
Conventions
l
Related Documentation
li
Obtaining Documentation, Obtaining Support, and Security Guidelines
CHAPTER
1
Cisco ASR 901 Router Overview
Introduction
1-1
1-2
Features 1-2
Performance Features 1-2
Management Options 1-3
Manageability Features 1-3
Security Features 1-4
Quality of Service and Class of Service Features
Layer 3 Features 1-5
Layer 3 VPN Services 1-5
Monitoring Features 1-5
CHAPTER
2
Licensing
1-4
2-1
Finding Feature Information
Contents
li
2-1
2-1
Feature Overview
2-2
Licenses Supported on Cisco ASR 901 Router
License Types 2-4
Image Level License 2-4
Features Supported 2-4
Feature Based License 2-4
Port Based/Mode License
1588BC License 2-5
2-2
2-5
Port or Interface Behavior 2-5
Port Based License 2-6
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
iii
Contents
Example: When Port Based License is not Installed 2-6
Example: When Port Based License is Installed 2-6
10gigUpgrade License 2-7
Example: When 10gigUpgrade License is not Installed 2-7
Example: When 10gigUpgrade License is Installed 2-8
Flexi License 2-8
Example: When Flexi License is not Installed 2-8
Example: When Flexi License is Installed 2-9
1588BC License 2-9
Example: When 1588BC License is not Installed 2-9
Example: When 1588BC License is Installed 2-9
Removing the 1588BC License 2-10
Generating the License
2-11
Installing the License
2-11
Changing the License
2-12
Return Materials Authorization License Process
Example: RMA Process 2-13
Verifying the License
Where to Go Next
2-13
2-14
2-14
Additional References 2-15
Related Documents 2-15
Standards 2-15
MIBs 2-15
RFCs 2-15
Technical Assistance 2-16
Feature Information for Licensing
CHAPTER
3
First-Time Configuration
Contents
2-17
3-1
3-1
Setup Mode 3-1
Before Starting Your Router 3-1
Using Setup Mode 3-2
Configuring Global Parameters 3-2
Completing the Configuration 3-4
Verifying the Cisco IOS Software Version
3-5
Configuring the Hostname and Password 3-5
Verifying the Hostname and Password 3-6
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
iv
OL-23826-09
Contents
CHAPTER
4
Managing and Monitoring Network Management Features
Finding Feature Information
Contents
4-1
4-1
4-1
Network Management Features for the ASR 901 4-2
Cisco Active Network Abstraction (ANA) 4-2
SNMP MIB Support 4-2
Cisco Networking Services (CNS) 4-2
How to Configure Network Management Features on ASR 901 4-2
Configuring SNMP Support 4-3
Configuring Remote Network Management 4-8
Enabling Cisco Networking Services (CNS) and Zero-Touch Deployment
Zero-Touch Deployment 4-10
Image Download 4-11
Configuring a DHCP Server 4-12
Configuring a TFTP Server 4-13
Creating a Bootstrap Configuration 4-13
Enabling a TFTP Server on the Edge Router 4-14
Configuring the Cisco Configuration Engine 4-14
Configuration Examples 4-15
Example: Configuring SNMP Support 4-15
Example: Configuring Remote Network Management
Example: Configuring a DHCP Server 4-15
Example: Zero-touch Deployment 4-16
Where to Go Next
4-10
4-15
4-16
Additional References 4-16
Related Documents 4-16
Standards 4-16
MIBs 4-17
RFCs 4-17
Technical Assistance 4-17
Feature Information for Monitoring and Managing the ASR 901 Router
CHAPTER
5
Using the Command-Line Interface
Contents
4-18
5-1
5-1
Understanding Command Modes
Understanding the Help System
5-1
5-3
Understanding Abbreviated Commands
5-4
Understanding no and default Forms of Commands
5-4
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
v
Contents
Understanding CLI Error Messages
5-4
Using Command History 5-5
Changing the Command History Buffer Size 5-5
Recalling Commands 5-6
Disabling the Command History Feature 5-6
Using Editing Features 5-6
Enabling and Disabling Editing Features 5-6
Editing Commands through Keystrokes 5-7
Editing Command Lines that Wrap 5-8
Searching and Filtering Output of show and more Commands
5-9
Accessing the CLI 5-9
Accessing the CLI through a Console Connection or through Telnet
Saving Configuration Changes
CHAPTER
6
Software Upgrade
Contents
5-10
6-1
6-1
Selecting a Cisco IOS Image
6-1
Upgrading the Cisco IOS image
Auto Upgrading the MCU
6-1
6-4
Manually Upgrading the ROMMON
Auto Upgrade of ROMMON
CHAPTER
7
6-5
6-6
Configuring Gigabit Ethernet Interfaces
Contents
5-9
7-1
7-1
Configuring the Interface
7-1
Setting the Speed and Duplex Mode
Enabling the Interface
7-2
7-3
Modifying MTU Size on the Interface
Verifying the MTU Size 7-4
7-3
MAC Flap Control 7-5
Configuring MAC FLap Control
7-5
Configuring a Combo Port 7-6
Restrictions 7-6
Verifying the Media Type 7-8
CHAPTER
8
Configuring Ethernet Virtual Connections
Finding Feature Information
8-1
8-1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
vi
OL-23826-09
Contents
Contents
8-1
Supported EVC Features
8-2
Understanding EVC Features 8-3
Ethernet Virtual Connections 8-3
Service Instances and EFPs 8-3
Encapsulation 8-4
Bridge Domains 8-5
DHCP Client on Switch Virtual Interface
Split-Horizon 8-6
Rewrite Operations 8-6
8-6
Configuring EFPs 8-7
Default EVC Configuration 8-7
Configuration Guidelines 8-7
Creating Service Instances 8-8
Configuration Examples of Supported Features 8-10
Example: Configuring a Service Instance 8-10
Example: Encapsulation Using a VLAN Range 8-10
Example: Two Service Instances Joining the Same Bridge Domain
Example: Bridge Domains and VLAN Encapsulation 8-10
Example: Rewrite 8-11
Example: Split Horizon 8-11
Configuration Examples of Unsupported Features
Example: Filtering 8-12
Example: Overlapping Encapsulation 8-12
8-10
8-12
How to Configure EVC Default Encapsulation 8-13
Configuring EVC Default Encapsulation with Bridge-Domain 8-13
Configuring EVC Default Encapsulation with Xconnect 8-14
Verifying EVC Default Encapsulation with Bridge-Domain 8-15
Verifying EVC Default Encapsulation with Xconnect 8-16
Configuration Examples for EVC Default Encapsulation 8-16
Example: Configuring EVC Default Encapsulation with Bridge-Domain 8-16
Example: Configuring EVC Default Encapsulation with Xconnect 8-16
Configuring Other Features on EFPs 8-16
EFPs and EtherChannels 8-17
MAC Address Forwarding, Learning and Aging on EFPs 8-17
Disabling MAC Address Learning on an Interface or Bridge Domain
Configuring IEEE 802.1Q Tunneling using EFPs 8-20
802.1Q Tunneling (QinQ) 8-20
Restrictions 8-22
8-18
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
vii
Contents
Configuration Examples 8-22
Routed QinQ 8-23
Restrictions 8-23
Configuration Example 8-23
Bridge Domain Routing 8-24
Restrictions 8-24
Example: Configuring Bridge-Domain Routing 8-24
How to Configure DHCP Client on SVI 8-25
Configuring DHCP Client on SVI 8-25
Verifying DHCP Client on SVI 8-26
Configuration Example for DHCP Client on SVI 8-26
EFPs and Switchport MAC Addresses 8-27
EFPs and MSTP 8-27
Monitoring EVC
8-28
Sample Configuration with Switchport to EVC Mapping
Configuration Example 8-30
8-29
Additional References 8-32
Related Documents 8-32
Standards 8-32
MIBs 8-32
RFCs 8-32
Technical Assistance 8-32
Feature Information for Configuring Ethernet Virtual Connections
CHAPTER
9
Configuring EtherChannels
Contents
8-33
9-1
9-1
Understanding How EtherChannels Work 9-1
EtherChannel Feature Overview 9-1
Understanding How EtherChannels Are Configured 9-2
EtherChannel Configuration Overview 9-2
Understanding Manual EtherChannel Configuration 9-2
Understanding IEEE 802.3ad LACP EtherChannel Configuration
Understanding Port-Channel Interfaces 9-4
Understanding Load Balancing 9-4
EtherChannel Configuration Guidelines and Restrictions
Configuring Etherchannels 9-5
Configuring Channel Groups 9-5
Configuring the LACP System Priority and System ID
Configuring the LACP Transmit Rate 9-7
9-2
9-4
9-6
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
viii
OL-23826-09
Contents
Verifying the LACP Transmit Rate 9-8
Configuring EtherChannel Load Balancing 9-8
Modifying MTU Size on Port-Channel 9-9
Restrictions 9-9
Verifying the MTU Size on Port-Channel 9-9
EVC On Port-Channel 9-10
Restrictions for EVC EtherChannel 9-10
Configuring EVC on Port-Channel 9-11
Verifying the Configuration 9-11
Troubleshooting 9-12
CHAPTER
10
Configuring Ethernet OAM 10-1
Contents 10-1
Understanding Ethernet CFM 10-2
IP SLA Support for CFM 10-2
Configuring Ethernet CFM 10-2
Default Ethernet CFM Configuration 10-3
Ethernet CFM Configuration Restrictions and Guidelines 10-3
Configuring the CFM Domain 10-3
Configuring Multi-UNI CFM MEPs in the Same VPN 10-7
Configuring Ethernet CFM Crosscheck 10-12
Configuring Static Remote MEP 10-13
Configuring a Port MEP 10-14
Configuring SNMP Traps 10-15
Configuring IP SLA CFM Operation 10-16
Manually Configuring an IP SLA CFM Probe or Jitter Operation 10-16
Configuring CFM over EFP with Cross Connect 10-19
Configuring CFM over EFP Interface with Cross Connect 10-20
Configuring CFM over EFP Interface with Cross Connect—Port Channel-Based Cross Connect
Tunnel 10-22
Configuring CFM with EVC Default Encapsulation 10-24
Verifying CFM with EVC Default Encapsulation 10-25
Example: Configuring CFM with EVC Default Encapsulation 10-26
Configuring Y.1731 Fault Management 10-26
Default Y.1731 Configuration 10-26
Configuring ETH-AIS 10-27
Configuring ETH-LCK 10-28
Managing and Displaying Ethernet CFM Information 10-30
Understanding the Ethernet OAM Protocol 10-32
OAM Features 10-33
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
ix
Contents
Setting Up and Configuring Ethernet OAM 10-35
Default Ethernet OAM Configuration 10-36
Restrictions and Guidelines 10-36
Enabling Ethernet OAM on an Interface 10-36
Enabling Ethernet OAM Remote Loopback 10-38
Configuring Ethernet OAM Link Monitoring 10-38
Configuring Ethernet OAM Remote Failure Indications 10-41
Configuring Ethernet OAM Templates 10-42
Displaying Ethernet OAM Protocol Information 10-45
Verifying Ethernet OAM Configuration 10-46
Understanding E-LMI 10-48
Restrictions 10-49
Configuring E-LMI 10-49
Default E-LMI Configuration 10-49
Enabling E-LMI 10-50
Displaying E-LMI Information 10-51
Understanding Ethernet Loopback 10-51
Configuring Ethernet Loopback 10-51
Restrictions 10-52
Enabling Ethernet Loopback 10-52
Configuration Example 10-54
Configuring Y.1564 to Generate Ethernet Traffic 10-56
Configuring IP SLA for Traffic Generation 10-58
Configuration Examples 10-60
CHAPTER
11
ITU-T Y.1731 Performance Monitoring
Finding Feature Information
Contents
11-1
11-1
11-1
Prerequisites for ITU-T Y.1731 Performance Monitoring
Restrictions for ITU-T Y.1731 Performance Monitoring
11-1
11-2
Information About ITU-T Y.1731 Performance Monitoring 11-2
Frame Delay and Frame-Delay Variation 11-3
Frame Loss Ratio 11-4
On-Demand and Concurrent Operations 11-4
Supported interfaces 11-5
Benefits of ITU-T Y.1731 Performance Monitoring 11-5
How to Configure ITU-T Y.1731 Performance Monitoring 11-5
Configuring Two-Way Delay Measurement 11-6
Configuring Single-Ended Synthetic Loss Measurement 11-9
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
x
OL-23826-09
Contents
Scheduling IP SLAs Operations
Prerequisites 11-14
11-14
Verifying the Frame Delay and Synthetic Loss Measurement Configurations 11-15
Example: Verifying Sender MEP for a Two-Way Delay Measurement Operation 11-16
Example: Verifying Receiver MEP for a Two-Way Delay Measurement Operation 11-16
Example: Verifying Sender MEP for a Synthetic Loss Measurement Operation 11-17
Example: Verifying Ethernet CFM Performance Monitoring 11-17
Example: Verifying History for IP SLAs Operations 11-18
How to Configure IP SLAs Y.1731 On-Demand and Concurrent Operations 11-19
Configuring Direct On-Demand Operation on a Sender MEP 11-19
Prerequisites 11-19
Configuring Referenced On-Demand Operation on a Sender MEP 11-20
Prerequisites 11-20
Configuring IP SLAs Y.1731 Concurrent Operation on a Sender MEP 11-21
Configuration Examples for IP SLAs Y.1731 On-Demand Operations
Example: On-Demand Operation in Direct Mode 11-21
Example: On-Demand Operation in Referenced Mode 11-22
11-21
Additional References 11-23
Related Documents 11-23
Standards 11-23
MIBs 11-23
RFCs 11-23
Technical Assistance 11-24
Feature Information for ITU-T Y.1731 Performance Monitoring
CHAPTER
12
Configuring Resilient Ethernet Protocol
Contents
11-25
12-1
12-1
Understanding Resilient Ethernet Protocol (REP)
Overview 12-1
Restrictions 12-3
Link Integrity 12-4
Fast Convergence 12-4
VLAN Load Balancing (VLB) 12-4
REP Ports 12-6
12-1
Configuring Resilient Ethernet Protocol (REP) 12-7
Default REP Configuration 12-7
REP Configuration Guidelines 12-7
Configuring the REP Administrative VLAN 12-9
SUMMARY STEPS 12-9
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xi
Contents
DETAILED STEPS 12-9
Configuring REP Interfaces 12-10
SUMMARY STEPS 12-10
DETAILED STEPS 12-11
Configuring REP as Dual Edge No-Neighbor Port 12-15
SUMMARY STEPS 12-15
DETAILED STEPS 12-16
Cisco ASR 901 Dual Rep Edge No-Neighbor Topology Example
Setting up Manual Preemption for VLAN Load Balancing 12-20
SUMMARY STEPS 12-20
DETAILED STEPS 12-20
Configuring SNMP Traps for REP 12-21
SUMMARY STEPS 12-21
DETAILED STEPS 12-21
Monitoring REP 12-22
SUMMARY STEPS 12-22
DETAILED STEPS 12-23
Configuration Examples for REP 12-24
Configuring the REP Administrative VLAN: Example 12-24
Configuring a REP Interface: Example 12-24
Setting up the Preemption for VLAN Load Balancing: Example
Configuring SNMP Traps for REP: Example 12-25
Monitoring the REP Configuration: Example 12-25
Cisco ASR 901 Topology Example 12-26
CHAPTER
13
Configuring MST on EVC Bridge Domain
12-25
13-1
Contents 13-1
Overview of MST and STP 13-1
Overview of MST on EVC Bridge Domain 13-2
Restrictions and Guidelines 13-2
Configuring MST on EVC Bridge Domain 13-4
Configuration Example for MST on EVC Bridge Domain
Verification 13-6
Troubleshooting Tips 13-9
CHAPTER
14
Configuring Multiprotocol Label Switching
CHAPTER
15
Configuring EoMPLS
Contents
12-18
13-6
14-1
15-1
15-1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xii
OL-23826-09
Contents
Understanding EoMPLS
Restrictions 15-2
Configuring EoMPLS
15-1
15-2
EoMPLS Configuration Example
15-3
Configuring Pseudowire Redundancy
Configuration Commands 15-4
Port Based EoMPLS
CHAPTER
16
15-5
Configuring MPLS VPNs
Contents
16-1
16-1
Understanding MPLS VPNs
Configuring MPLS VPNs
16-1
16-2
Configuration Examples for MPLS VPN
CHAPTER
17
Configuring MPLS OAM
Contents
15-4
16-2
17-1
17-1
Understanding MPLS OAM 17-1
LSP Ping 17-1
LSP Traceroute 17-2
LSP Ping over Pseudowire 17-2
Configuring MPLS OAM 17-2
Using LSP Ping for LDP IPv4 FEC 17-3
Using LSP Traceroute for LDP IPv4 FEC 17-3
Using LSP Ping for Pseudowire 17-3
Using LSP Traceroute over Pseudowire 17-4
Displaying AToM VCCV capabilities 17-4
17-4
CHAPTER
CHAPTER
18
19
Configuring Routing Protocols 18-1
Changing Default Hashing Algorithm for ECMP
Configuring Bidirectional Forwarding Detection
Contents
18-1
19-1
19-1
Understanding BFD
19-1
Configuring BFD 19-1
BFD Configuration Guidelines and Restrictions 19-2
Configuring BFD for OSPF 19-2
Configuring BFD for OSPF on One of More Interfaces
19-2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xiii
Contents
Configuring BFD for OSPF on All Interfaces 19-3
Configuring BFD for BGP 19-4
Configuring BFD for IS-IS 19-4
Configuring BFD for IS-IS on a Single Interface 19-4
Configuring BFD for IS-IS for All Interfaces 19-5
Configuring BFD for Static Routes 19-6
Configuration Examples for BFD 19-7
BFD with OSPF on All Interfaces 19-7
BFD with OSPF on Individual Interfaces 19-7
BFD with BGP 19-8
BFD with IS-IS on All Interfaces 19-8
BFD with IS-IS on Individual Interfaces 19-8
BFD with Static Routes 19-9
CHAPTER
20
Configuring T1/E1 Controllers
Contents
20-1
20-1
Configuring the Card Type
20-1
Configuring E1 Controllers
20-2
Configuring T1 Controllers
20-4
Troubleshooting Controllers 20-5
Troubleshooting E1 Controllers
Troubleshooting T1 Controllers
CHAPTER
21
Configuring Pseudowire
20-6
21-1
Finding Feature Information
Contents
20-5
21-1
21-1
Understanding Pseudowires 21-2
Structure-Agnostic TDM over Packet 21-2
Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network
Transportation of Service Using Ethernet over MPLS 21-3
Limitations 21-3
Hot Standby Pseudowire Support for ATM/IMA
21-3
21-3
Configuring Pseudowire 21-4
Configuring Pseudowire Classes 21-4
Configuring CEM Classes 21-6
Configuring a Backup Peer 21-8
Configuring Structure-Agnostic TDM over Packet 21-9
Configuring a SAToP Pseudowire with UDP Encapsulation
21-11
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xiv
OL-23826-09
Contents
Configuring Circuit Emulation Service over Packet-Switched Network 21-14
Configuring a CESoPSN Pseudowire with UDP Encapsulation 21-15
QoS for CESoPSN over UDP and SAToP over UDP 21-18
Configuring Transportation of Service Using Ethernet over MPLS 21-18
Configuring L2VPN Pseudowire Redundancy 21-20
Example: Pseudowire Redundancy 21-22
Configuring Hot Standby Pseudowire Support for ATM/IMA 21-22
Configuring ATM/IMA Pseudowire Redundancy in PVC Mode
Configuring ATM/IMA Pseudowire Redundancy in PVP Mode
Configuring ATM/IMA Pseudowire Redundancy in Port Mode
Verifying Hot Standby Pseudowire Support for ATM/IMA
TDM Local Switching 21-27
Restrictions 21-28
Configuring TDM Local Switching on a T1/E1 Mode
DETAILED STEPS 21-28
Verifying Local Switching 21-29
Configuration Example for Local Switching
21-22
21-24
21-25
21-26
21-28
21-29
Configuration Examples of Hot Standby Pseudowire Support for ATM/IMA 21-30
Example: Configuring ATM/IMA Pseudowire Redundancy in PVC Mode 21-30
Example: Configuring ATM/IMA Pseudowire Redundancy in PVP Mode 21-30
Example: Configuring ATM/IMA Pseudowire Redundancy in Port Mode 21-31
Configuration Examples for Pseudowire 21-31
Example: TDM over MPLS Configuration-Example
Example: CESoPSN with UDP 21-34
Example: Ethernet over MPLS 21-35
21-31
Additional References 21-36
Related Documents 21-36
Standards 21-36
MIBs 21-36
RFCs 21-36
Technical Assistance 21-36
Feature Information for Configuring Pseudowire
CHAPTER
22
Configuring Clocking
Contents
Restrictions
21-37
22-1
22-1
22-1
Configuring Network Clock for Cisco ASR 901 Router 22-2
Configuring Network Clock in Global Configuration Mode
22-3
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xv
Contents
Configuring Network Clock in Interface Configuration Mode
Understanding SSM and ESMC 22-7
Synchronization Status Message 22-7
Ethernet Synchronization Messaging Channel 22-7
Clock Selection Algorithm 22-7
ESMC behavior for Port Channels 22-8
ESMC behavior for STP Blocked Ports 22-8
Configuring ESMC in Global Configuration Mode 22-8
Configuring ESMC in Interface Configuration Mode 22-9
Verifying ESMC Configuration 22-10
Managing Synchronization 22-11
Synchronization Example 22-12
Configuring Synchronous Ethernet for Copper Ports 22-13
Verifying the Synchronous Ethernet configuration 22-13
Troubleshooting Tips 22-16
Troubleshooting ESMC Configuration 22-17
22-6
Configuring PTP for the Cisco ASR 901 Router 22-18
Restrictions 22-18
Setting System Time to Current Time 22-19
Configuring PTP Ordinary Clock 22-19
Configuring Master Ordinary Clock 22-19
Configuring Slave Ordinary Clock 22-21
Configuring PTP in Unicast Mode 22-25
Configuring PTP in Unicast Negotiation Mode 22-25
PTP Boundary Clock 22-26
Configuring PTP Boundary Clock 22-27
Verifying PTP modes 22-29
Verifying PTP Configuration on the 1588V2 Slave 22-31
Verifying PTP Configuration on the 1588V2 Master 22-32
PTP Hybrid Clock 22-34
Configuring a Hybrid Ordinary Clock 22-34
Configuring a Hybrid Boundary Clock 22-37
Verifying Hybrid modes 22-38
SSM and PTP Interaction 22-39
ClockClass Mapping 22-40
Telecom Profiles 22-40
PTP Redundancy 22-40
Configuring Telecom Profile in Slave Ordinary Clock 22-41
Configuring Telecom Profile in Master Ordinary Clock 22-43
Verifying Telecom profile 22-44
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xvi
OL-23826-09
Contents
Setting the TimeProperties 22-46
ASR901 Negotiation Mechanism 22-46
Static Unicast Mode 22-46
Configuring ToD on 1588V2 Slave 22-47
Troubleshooting Tips 22-47
CHAPTER
23
Cisco IOS IP SLA
Contents
23-1
23-1
Configuring IPSLA Path Discovery 23-1
Example for IPSLA Path Discovery 23-3
Two-Way Active Measurement Protocol 23-5
Configuring TWAMP 23-6
Configuring the TWAMP Server 23-7
Configuring the TWAMP Reflector 23-8
Configuration Examples for TWAMP 23-8
Example: Configuring the Router as an IP SLA TWAMP server 23-9
Example: Configuring the Router as an IP SLA TWAMP Reflector 23-9
CHAPTER
24
Configuring QoS
24-1
Finding Feature Information
Contents
24-1
24-1
Understanding QoS 24-2
Modular QoS CLI 24-4
Input and Output Policies 24-5
Input Policy Maps 24-5
Output Policy Maps 24-6
Access Control Lists 24-6
Restrictions 24-6
Classification 24-7
Class Maps 24-8
The match Command 24-8
Classification Based on Layer 2 CoS 24-9
Classification Based on IP Precedence 24-9
Classification Based on IP DSCP 24-9
Classification Comparisons 24-10
Classification Based on QoS Groups 24-11
Classification Based on VLAN IDs 24-12
Table Maps 24-13
Policing 24-14
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xvii
Contents
Individual Policing 24-15
Unconditional Priority Policing 24-16
Egress Policing 24-17
Marking 24-18
Congestion Management and Scheduling 24-19
Traffic Shaping 24-19
Class-Based Weighted Fair Queuing 24-21
Priority Queuing 24-23
Ingress and Egress QoS Functions 24-24
Configuring Quality of Service (QoS) 24-25
QoS Limitations 24-25
General QoS Limitations 24-26
Statistics Limitations 24-26
Propagation Limitations 24-27
Classification Limitations 24-27
Marking Limitations 24-28
Congestion Management Limitations 24-29
ACL-based QoS Restrictions 24-30
Improving Feature Scalability 24-31
TCAM with QoS 24-31
QoS for MPLS/IP over MLPPP 24-31
QoS for CPU Generated Traffic 24-31
QoS Configuration Guidelines 24-32
Sample QoS Configuration 24-33
Configuring Classification 24-34
Creating a Class Map for Classifying Network Traffic 24-34
Creating a Policy Map for Applying a QoS Feature to Network Traffic
Attaching the Policy Map to an Interface 24-36
Attaching Policy Map to Cross Connect EVC 24-37
Configuring Marking 24-38
Creating a Class Map for Marking Network Traffic 24-39
Creating a Policy Map for Applying a QoS Feature to Network Traffic
Attaching the Policy Map to an Interface 24-40
Configuring MPLS Exp Bit Marking using a Pseudowire 24-41
Configuring Congestion Management 24-42
Configuring Low Latency Queueing (LLQ) 24-42
Configuring Multiple Priority Queueing 24-43
Configuration Examples 24-44
Configuring Class-Based Weighted Fair Queuing (CBFQ) 24-45
Weighted Random Early Detection (WRED) 24-46
24-35
24-39
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xviii
OL-23826-09
Contents
Configuring Shaping 24-47
Configuring Class-Based Traffic Shaping in a Primary-Level (Parent) Policy Map
Configuring the Secondary-Level (Child) Policy Map 24-48
Configuring Ethernet Trusted Mode 24-49
Creating IP Extended ACLs 24-49
Using Class Maps to Define a Traffic Class 24-50
Creating a Named Access List 24-52
Restrictions 24-52
What to do Next 24-53
TCAM with ACL 24-54
Verifying Named Access List 24-55
Configuration Example for Named Access List 24-56
QoS Treatment for Performance-Monitoring Protocols
Cisco IP-SLAs 24-62
QoS Treatment for IP-SLA Probes 24-62
Marking 24-62
Queuing 24-62
QoS Marking for CPU-Generated Traffic 24-62
QoS Queuing for CPU-Generated Traffic 24-63
24-47
24-62
Extending QoS for MLPPP 24-64
Configuring Class-map for Matching MPLS EXP Bits 24-64
Configuring Class-map for Matching IP DSCP Value 24-65
Configuring Class-map for Matching MPLS EXP Bits or IP DSCP Value 24-66
Configuring a Policy-map 24-67
Attaching the Policy-map to MLPPP Interface 24-70
Re-marking IP DSCP Values of CPU Generated Traffic 24-72
Re-marking MPLS EXP Values of CPU Generated Traffic 24-73
Configuring a Policy-map to Match on CS5 and EXP4 24-74
Attaching the Policy-map to Match on CS5 and EXP4 to MLPPP Interface 24-76
Configuration Examples for Extending QoS for MPLS over MLPPP 24-76
Configuring Class-map for Matching MPLS EXP Bits 24-76
Configuring Class-map for Matching IP DSCP Value 24-77
Configuring Class-map for Matching MPLS EXP Bits or IP DSCP Value 24-77
Configuring a Policy-map 24-77
Configuring a Policy-map to Match on CS5 and EXP 4 24-78
Attaching the Policy-map to MLPPP Interface 24-78
Verifying MPLS over MLPPP Configuration
Configuration Guidelines 24-80
Troubleshooting Tips
24-79
24-81
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xix
Contents
Additional References 24-87
Related Documents 24-87
Standards 24-87
MIBs 24-87
RFCs 24-87
Technical Assistance 24-87
Feature Information for Configuring QoS
CHAPTER
25
Configuring MLPPP
25-1
Finding Feature Information
Contents
25-1
25-1
Prerequisites
Restrictions
24-88
25-2
25-2
MLPPP Optimization Features 25-2
Distributed Multilink Point-to-Point Protocol Offload
Multiclass MLPPP 25-3
MPLS over MLPPP 25-3
MPLS Features Supported for MLPPP 25-4
MPLS over MLPPP on PE-to-CE Links 25-4
MPLS over MLPPP on Core Links 25-5
MPLS over MLPPP on CE to PE Links 25-5
25-2
Configuring MLPPP Backhaul 25-6
Configuring the Card Type, E1 and T1 Controllers 25-6
Configuring a Multilink Backhaul Interface 25-6
Creating a Multilink Bundle 25-6
Configuring MRRU 25-7
Configuring PFC and ACFC 25-8
Enabling Multilink and Identifying the Multilink Interface 25-11
Configuring a Serial Interface as a Member Link of a MLPPP Group
MLPPP Offload 25-13
Configuring Additional MLPPP Settings 25-14
Configuring MPLS over the MLPPP on a Serial Interface 25-14
Configuring MPLS over MLPPP for OSPF 25-16
Configuration Examples for MPLS over MLPPP 25-18
Verifying MPLS over MLPPP Configuration 25-19
25-12
Additional References 25-21
Related Documents 25-21
Standards 25-21
MIBs 25-21
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xx
OL-23826-09
Contents
RFCs 25-21
Technical Assistance
25-21
Feature Information for MLPPP
CHAPTER
26
Onboard Failure Logging
Contents
26-1
26-1
Understanding OBFL
Configuring OBFL
26-1
26-2
Verifying OBFL Configuration
CHAPTER
27
25-22
26-2
Hot Standby Router Protocol and Virtual Router Redundancy Protocol
Finding Feature Information
Contents
27-1
27-1
27-1
Information About HSRP and VRRP 27-2
Overview of HSRP and VRRP 27-2
Text Authentication 27-2
Preemption 27-2
How to Configure HSRP 27-3
Configuring HSRP 27-3
Restrictions 27-3
Configuration Examples for HSRP 27-5
Example: Configuring HSRP Active Router 27-5
Example: Configuring HSRP Backup Router 27-5
Example: HSRP Text Authentication 27-6
How to Configure VRRP 27-6
Configuring VRRP 27-6
Restrictions 27-6
Configuration Examples for VRRP 27-8
Example: Configuring a VRRP Master Router
Example: Configuring a VRRP Backup Router
Example: VRRP Text Authentication 27-9
Where to Go Next
27-8
27-8
27-9
Additional References 27-9
Related Documents 27-9
Standards 27-9
MIBs 27-10
RFCs 27-10
Technical Assistance 27-10
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxi
Contents
Feature Information for HSRP and VRRP
CHAPTER
28
27-11
Configuring Link Layer Discovery Protocol
Finding Feature Information
Contents
28-1
28-1
28-1
Restrictions for LLDP
Overview of LLDP
28-2
28-2
How to Configure LLDP 28-2
Configuring LLDP 28-2
Verifying LLDP 28-4
Configuration Example for LLDP 28-4
Example: Enabling LLDP Globally 28-4
Example: Configuring Hold Time 28-4
Example: Configuring Delay Time 28-5
Example: Configuring Intervals 28-5
Where to Go Next
28-6
Additional References 28-7
Related Documents 28-7
Standards 28-7
MIBs 28-7
RFCs 28-7
Technical Assistance 28-8
Feature Information for LLDP
CHAPTER
29
28-8
Configuring Multihop Bidirectional Forwarding Detection
Finding Feature Information
Contents
29-1
29-1
29-1
Restrictions for Multihop BFD
29-2
Information About Multihop BFD 29-2
Overview of Multihop BFD 29-2
How to Configure Multihop BFD 29-2
Configuring Multihop BFD Template 29-2
Configuring a Multihop BFD Map 29-4
Configuration Examples for Multihop BFD 29-4
Example : Configuring Multihop BFD 29-4
Where to Go Next
29-5
Additional References
29-6
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxii
OL-23826-09
Contents
Related Documents 29-6
Standards 29-6
MIBs 29-6
RFCs 29-6
Technical Assistance 29-7
Feature Information for Multihop BFD
CHAPTER
30
Bit Error Rate Testing
29-7
30-1
Finding Feature Information
30-1
Contents 30-1
Prerequisites 30-1
Restrictions 30-2
Feature Overview
30-2
How to Configure BERT 30-2
Performing BERT on a T1/E1 Line 30-3
Terminating BERT on a T1/E1 Controller 30-3
Verifying BERT on a T1/E1 Controller 30-4
Configuration Examples
30-5
Additional References 30-5
Related Documents 30-6
Standards 30-6
MIBs 30-6
RFCs 30-6
Technical Assistance 30-6
Feature Information for Bit Error Rate Testing
CHAPTER
31
30-6
Microwave ACM Signaling and EEM Integration
Finding Feature Information
Contents 31-1
Prerequisites
Feature Overview
Benefits
31-1
31-1
31-2
31-2
31-3
How to Configure Microwave ACM Signaling and EEM Integration 31-4
Configuring Connectivity Fault Management 31-4
Configuring EEP Applet Using CLIs 31-7
Prerequisites 31-7
Configuring Event Handler 31-9
Verifying Microwave Microwave ACM Signaling and EEM Integration Configuration
31-10
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxiii
Contents
Configuration Examples for Microwave ACM Signaling and EEM Integration
Example: Configuring CFM 31-11
Example: Configuring EEP Applet 31-11
Example: Configuring Event Handler 31-15
31-11
Additional References 31-16
Related Documents 31-16
Standards 31-16
MIBs 31-16
RFCs 31-16
Technical Assistance 31-16
Feature Information for Microwave ACM Signaling and EEM Integration
CHAPTER
32
IPv6 Support on the Cisco ASR 901 Router
Finding Feature Information
Contents
31-17
32-1
32-1
32-1
Prerequisites for IPv6 Support on the Cisco ASR 901 Router
Restrictions for IPv6 Support on the Cisco ASR 901 Router
Information About IPv6 Support on the Cisco ASR 901 Router
Benefits 32-3
Overview of IPv6 32-3
IPv6 Address Formats 32-3
IPv6 Addressing and Discovery 32-4
Static Configuration 32-4
Stateless Autoconfiguration 32-5
ICMPv6 32-5
IPv6 Duplicate Address Detection 32-6
IPv6 Neighbor Discovery 32-6
IPv4 and IPv6 Dual-Stack on an Interface 32-6
Routing Protocols 32-7
IS-IS Enhancements for IPv6 32-7
OSPFv3 for IPv6 32-7
Multiprotocol BGP Extensions for IPv6 32-7
Bidirectional Forwarding Detection for IPv6 32-7
QoS for IPv6 32-8
32-2
32-2
32-2
How to Configure IPv6 Support on the Cisco ASR 901 Router 32-8
Configuring IPv6 Addressing and Enabling IPv6 Routing 32-8
Configuring a Static IPv6 Route 32-10
Enabling Stateless Auto-Configuration 32-11
Implementing IPv6 on VLAN Interfaces 32-12
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxiv
OL-23826-09
Contents
Implementing IPv6 Addressing on Loopback Interfaces 32-13
Configuring ICMPv6 Rate Limiting 32-14
Configuring IPv6 Duplicate Address Detection 32-15
Configuring IPv6 Neighbor Discovery 32-16
Configuring IPv6 and IPv4 Dual-Stack on the Same VLAN 32-17
Prerequisites 32-17
Configuring OSPFv3 for IPv6 32-18
Configuring IS-IS for IPv6 32-19
Configuring Multiprotocol-BGP for IPv6 32-21
Configuring BFD for IPv6 32-22
Specifying a Static BFDv6 Neighbor 32-22
Associating an IPv6 Static Route with a BFDv6 Neighbor 32-23
Configuring BFDv6 and OSPFv3 32-25
Prerequisites 32-25
Configuring BFDv6 for BGP 32-26
Implementing QoS for IPv6 32-27
Verifying the Configuration of IPv6 Support on the Cisco ASR 901 Router
Verifying IPv6 Addressing Routing 32-27
Verifying a Static IPv6 Route 32-28
Verifying a Stateless Auto-Configuration 32-29
Verifying IPv6 Implementation on VLAN Interfaces 32-29
Verifying IPv6 Implementation on Loopback Interfaces 32-30
Verifying ICMPv6 Configuration 32-30
Verifying IPv6 Duplicate Address Detection Configuration 32-32
Verifying IPv6 Neighbor Discovery Configuration 32-33
Verifying IPv6 and IPv4 Dual-Stack Configuration 32-33
Verifying OSPFv3 for IPv6 Configuration 32-34
Verifying IS-IS for IPv6 Configuration 32-35
Verifying Multiprotocol-BGP for IPv6 Configuration 32-35
Verifying BFD for IPv6 Configuration 32-37
Verifying BFDv6 and OSPFv3 Configuration 32-38
Verifying BFDv6 for BGP Configuration 32-39
32-27
Configuration Examples for IPv6 Support on the Cisco ASR 901 Router 32-39
Example: IPv6 Addressing on VLAN Interfaces 32-40
Example: IPv6 Addressing on Loopback Interfaces 32-40
Example: Customizing ICMPv6 32-40
Example: Configuring IPv6 Duplicate Address Detection 32-40
Example: Configuring IPv6 Neighborhood Discovery 32-41
Example: Enabling IPv6 Stateless Address Autoconfiguration 32-41
Example: Configuring the IPv4 and IPv6 Dual-Stack 32-41
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxv
Contents
Example: Configuring IPv6 Static Routing 32-41
Example: Configuring BFD and Static Routing for IPv6 32-42
Example: Configuring OSPFv3 for IPv6 32-42
Example: Configuring BFD and OSPFv3 for IPv6 32-42
Example: Configuring IS-IS for IPv6 32-43
Example: Configuring Multiprotocol-BGP for IPv6 32-44
Example: Configuring BFD and Multiprotocol-BGP for IPv6 32-45
Troubleshooting Tips
Where to Go Next
32-46
32-46
Additional References 32-47
Related Documents 32-47
Standards 32-47
MIBs 32-47
RFCs 32-47
Technical Assistance 32-48
Feature Information for IPv6 Support on the Cisco ASR 901 Router
CHAPTER
33
Labeled BGP Support
32-49
33-1
Finding Feature Information
33-1
Contents 33-1
Prerequisites 33-2
Restrictions 33-2
Overview of Labeled BGP Support
33-2
How to Configure Labeled BGP Support 33-2
Configuration Example for Labeled Support
Verifying Labeled BGP Support 33-4
33-3
Additional References 33-7
Related Documents 33-7
Standards 33-7
MIBs 33-7
RFCs 33-7
Technical Assistance 33-7
Feature Information for Labeled BGP Support
CHAPTER
34
33-8
MPLS Traffic Engineering - Fast Reroute Link Protection
Finding Feature Information
Contents 34-1
Prerequisites
34-1
34-1
34-2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxvi
OL-23826-09
Contents
Restrictions
34-2
Feature Overview 34-2
BFD-triggered Fast Reroute
BFD 34-4
Fast Reroute 34-4
Link Protection 34-4
34-3
How to Configure Traffic Engineering - Fast Reroute Link Protection 34-4
Enabling MPLS TE-FRR on an SVI Interface 34-5
Enabling MPLS TE-FRR for EoMPLS on a Global Interface 34-5
Enabling MPLS TE-FRR for EoMPLS on an Interface 34-7
Enabling MPLS TE-FRR for IS-IS 34-9
Configuring Primary One-hop Auto-Tunnels 34-11
Configuring Backup Auto-Tunnels 34-13
Enabling Targeted LDP session over Primary one-hop Auto-Tunnels 34-14
Enabling BFD Triggered FRR on an SVI Interface 34-15
Enabling BFD Triggered FRR on a Router 34-16
Verification Examples 34-17
Verifying MPLS TE-FRR Configuration 34-17
Verifying Primary One-hop Auto-Tunnels 34-19
Verifying Backup Auto-Tunnels 34-19
Verifying BFD Triggered FRR Configuration 34-20
Configuration Examples 34-24
Example: Configuring MPLS TE-FRR 34-24
Example: Configuring Primary One-hop Auto-Tunnels
Example: Configuring Backup Auto-Tunnels 34-24
Example: Configuring BFD Triggered FRR 34-24
34-24
Additional References 34-25
Related Documents 34-25
Standards 34-25
MIBs 34-25
RFCs 34-25
Technical Assistance 34-26
Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection
CHAPTER
35
Layer 2 Control Protocol Peering, Forwarding, and Tunneling
Finding Feature Information
34-27
35-1
35-1
Contents 35-1
Prerequisites 35-1
Restrictions 35-2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxvii
Contents
Layer 2 Control Protocol Forwarding
Layer 2 Control Protocol Tunneling
35-2
35-2
How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling
Configuring Layer 2 Peering 35-4
Restrictions 35-4
Configuring Layer 2 Forwarding 35-5
Restrictions 35-5
Configuring Layer 2 Tunneling 35-7
Restrictions 35-7
Verifying Layer 2 Peering 35-9
Verifying Layer 2 Forwarding 35-9
Verifying Layer 2 Tunneling 35-9
35-3
Configuration Examples 35-10
Example: Configuring Layer 2 Peering 35-10
Example: Configuring Layer 2 Forwarding 35-10
Example: Configuring Layer 2 Tunneling 35-11
Additional References 35-13
Related Documents 35-14
Standards 35-14
MIBs 35-14
RFCs 35-14
Technical Assistance 35-14
Feature Information for Layer 2 Control Protocol Peering, Forwarding, and Tunneling
CHAPTER
36
Configuring Inverse Muliplexing over ATM
Finding Feature Information
35-15
36-1
36-1
Contents 36-1
Prerequisites 36-1
Restrictions 36-2
Feature Overview
36-2
How to Configure IMA
36-2
Configuring ATM IMA on T1/E1 Interface
36-3
Configuring ATM IMA over MPLS 36-4
Configuring the T1/E1 Controller 36-4
Configuring an ATM IMA Interface 36-5
Configuring ATM over MPLS Pseudowire Interface
Configuring a Port Mode Pseudowire 36-7
Configuring an N-to-1 VCC Cell Mode 36-7
36-6
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxviii
OL-23826-09
Contents
Configuring an N-to-1 vPC Cell Mode 36-8
ATM AAL5 SDU VCC Transport 36-9
Verifying IMA Configurations 36-10
How to Configure ATM Class of Service 36-11
Configuring Constant Bit Rate 36-11
Configuring Unspecified Bit Rate 36-12
Configuring Unspecified Bit Rate Plus 36-13
Configuring Variable Bit Rate for Real/Non-Real Time Traffic 36-14
Configuration Examples 36-15
Example: Creating an IMA Interface 36-15
Example: Configuring a Port Mode Pseudowire 36-15
Example: Configuring an N-to-1 VCC Cell Mode 36-16
Example: Configuring an N-to-1 VPC Cell Mode 36-16
Example: Configuring CBR 36-16
Example: Configuring UBR 36-16
Example: Configuring UBR Plus 36-17
Example: Configuring VBR for Real Time Traffic 36-17
Example: Configuring VBR for Non-Real Time Traffic 36-17
Configuring Marking MPLS Experimental Bits 36-17
Creating a Policy-map for PVP/PVC/ATM IMA Interface 36-17
Applying the Policy-map 36-18
Applying a Policy map on PVC and PVP 36-18
Applying a Policy map on ATM IMA Interface 36-20
Creating a Table-map 36-21
Creating a Policy-map for SVI Interface 36-22
Applying a Service Policy on SVI Interface 36-23
Additional References 36-25
Related Documents 36-25
Standards 36-25
MIBs 36-25
RFCs 36-25
Technical Assistance 36-25
Feature Information for Inverse Multiplexing over ATM
CHAPTER
37
IPv6 over MPLS: 6PE and 6VPE
Finding Feature Information
36-26
37-1
37-1
Contents 37-1
Prerequisites 37-2
Restrictions 37-2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxix
Contents
Feature Overview 37-2
Benefits of 6PE and 6VPE 37-3
IPv6 on Provider Edge Routers 37-3
IPv6 on VPN Provider Edge Routers 37-4
Components of MPLS-based 6VPE Network
Supported Features
37-5
Scalability Numbers
37-6
37-4
How to Configure IPv6 over MPLS: 6PE and 6VPE 37-6
Configuring 6PE 37-6
Configuring 6VPE 37-9
Setting up IPv6 Connectivity from PE to CE Routers 37-9
Setting up MP-BGP Peering to the Neighboring PE 37-10
Setting up MPLS/IPv4 Connectivity with LDP 37-12
Creating IPv6 VRFs on PE Routers 37-13
Verifying IPv6 over MPLS: 6PE and 6VPE Configuration 37-15
Configuration Examples 37-18
Example: Configuring 6PE 37-18
Example: Configuring 6VPE 37-19
Additional References 37-20
Related Documents 37-20
Standards 37-20
MIBs 37-20
RFCs 37-20
Technical Assistance 37-20
Feature Information for IPv6 over MPLS: 6PE and 6VPE
CHAPTER
38
Storm Control
37-21
38-1
Finding Feature Information
38-1
Contents 38-1
Prerequisites 38-2
Restrictions 38-2
Feature Overview
38-2
Configuring Storm Control 38-2
Verifying Storm Control 38-4
Configuring Error Disable Recovery 38-5
Monitoring Error Disable Recovery 38-6
Configuration Example for Storm Control
Troubleshooting Tips
38-7
38-7
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxx
OL-23826-09
Contents
Additional References 38-8
Related Documents 38-8
Standards 38-8
MIBs 38-8
RFCs 38-8
Technical Assistance 38-8
Feature Information for Storm Control
CHAPTER
39
38-9
Remote Loop-Free Alternate - Fast Reroute
Finding Feature Information
39-1
39-1
Contents 39-1
Prerequisites 39-2
Restrictions 39-2
Feature Overview 39-3
Benefits of Remote LFA-FRR 39-4
Avoiding Traffic Drops 39-4
Pseudowire Redundancy over FRR 39-4
Conditions for Switchover 39-5
How to Configure Remote Loop-Free Alternate - Fast Reroute 39-5
Configuring Remote LFA-FRR for IS-IS 39-6
Configuring Remote LFA-FRR for OSPF 39-9
Configuring Remote LFA-FRR for Ethernet and TDM Pseudowires 39-11
Configuring Remote LFA-FRR on a Global Interface 39-12
Configuring Remote LFA-FRR on a GigabitEthernet Interface 39-13
Configuring Remote LFA-FRR on an SVI Interface 39-14
Configuring Remote LFA-FRR on IS-IS 39-15
Configuring LFA-FRR for EoMPLS 39-19
Configuring LFA-FRR for ATM/IMA 39-21
Configuring LFA-FRR for CESoPSN 39-23
Configuring LFA-FRR for SAToP 39-25
Verification Examples for Remote LFA-FRR 39-27
Verifying Remote LFA-FRR Configuration 39-28
Verifying Remote LFA-FRR Configuration for EoMPLS on a GigabitEthernet Interface
Verifying Remote LFA-FRR Configuration for EoMPLS on an EVC Interface 39-32
Verifying Remote LFA-FRR Configuration on IS-IS 39-33
Verifying Remote LFA-FRR Configuration on ATM/IMA 39-33
Verifying Remote LFA-FRR Configuration on CESoPSN 39-34
Verifying Remote LFA-FRR Configuration on SAToP 39-35
Configuration Examples for Remote LFA-FRR
39-30
39-35
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxxi
Contents
Example: Configuring Remote LFA-FRR for IS-IS 39-36
Example: Configuring Remote LFA-FRR for OSPF 39-36
Example: Configuring Remote LFA-FRR Globally 39-36
Example: Configuring Remote LFA-FRR on a GigabitEthernet Interface 39-37
Example: Configuring Remote LFA-FRR on an SVI Interface 39-37
Example: Configuring EoMPLS Pseudowire Redundancy over FRR 39-37
Example: Configuring LFA-FRR on ATM/IMA 39-37
Example: Configuring LFA-FRR on CESoPSN 39-38
Example: Configuring LFA-FRR on SAToP 39-38
Additional References 39-39
Related Documents 39-39
Standards 39-39
MIBs 39-39
RFCs 39-39
Technical Assistance 39-39
Feature Information for Remote Loop-Free Alternate - Fast Reroute
CHAPTER
40
Digital Optical Monitoring
Finding Feature Information
Contents
39-40
40-1
40-1
40-1
Feature Overview
40-1
How to Enable Transceiver Monitoring
Restrictions 40-2
40-2
Examples 40-3
Example: Displaying Transceiver Information 40-3
Example: Displaying Detailed Transceiver Information 40-4
Example: Displaying List of Supported Transceivers 40-5
Example: Displaying Threshold Tables 40-6
Example: Displaying Threshold Violations 40-9
Example: Displaying Threshold Violations on a Specific Interface
Example: When Transceiver Monitoring is Disabled 40-9
Example: Displaying SPF Details 40-10
40-9
Additional References 40-12
Related Documents 40-12
Standards 40-12
MIBs 40-12
RFCs 40-12
Technical Assistance 40-12
Feature Information for Digital Optical Monitoring
40-13
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxxii
OL-23826-09
Contents
CHAPTER
41
IPv4 Multicast
41-1
Finding Feature Information
41-1
Contents 41-1
Prerequisites 41-2
Restrictions 41-2
Feature Overview 41-2
Supported Protocols 41-3
PIM SSM for IPv4 41-3
Source Specific Multicast 41-3
Protocol Independent Multicast 41-3
IGMP 41-4
IGMPv1 41-4
IGMPv2 41-4
IGMPv3 41-4
PIM SSM Mapping 41-5
Static SSM Mapping 41-5
Reverse Path Forwarding 41-5
Configuring IPv4 Multicast 41-6
Enabling IPv4 Multicast Routing 41-6
Configuring PIM SSM 41-7
Configuring PIM SSM Mapping 41-8
Verifying IPv4 Multicast Routing 41-9
Verifying PIM SSM 41-9
Verifying PIM SSM Mapping 41-10
Configuration Examples for IPv4 Multicast 41-11
Example: IPv4 Multicast Routing 41-12
Example: Configuring PIM SSM 41-12
Example: Configuring PIM SSM Mapping 41-12
Example: Configuring Rendezvous Point 41-13
Troubleshooting Tips
41-13
Additional References 41-14
Related Documents 41-14
Standards 41-14
MIBs 41-14
RFCs 41-14
Technical Assistance 41-15
Feature Information for IPv4 Multicast
41-16
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxxiii
Contents
CHAPTER
42
IPv6 Multicast
42-1
Finding Feature Information
42-1
Contents 42-1
Prerequisites 42-2
Restrictions 42-2
Feature Overview 42-2
IPv6 Multicast Groups 42-3
IPv6 Multicast Routing Implementation 42-3
Multicast Listener Discovery Protocol for IPv6 42-3
Protocol Independent Multicast 42-4
PIM Source Specific Multicast 42-5
Source Specific Multicast Mapping for IPv6 42-5
PIM-Sparse Mode 42-5
Rendezvous Point 42-6
Configuring IPv6 Multicast 42-6
Enabling IPv6 Multicast Routing 42-6
Disabling IPv6 Multicast Forwarding 42-7
Disabling MLD Device-Side Processing 42-8
Configuring MLD Protocol on an Interface 42-9
Configuring a Rendezvous Point 42-10
Configuring PIM SSM Options 42-11
Disabling PIM SSM Multicast on an Interface 42-12
Configuring IPv6 SSM Mapping 42-12
Verifying IPv6 Multicast 42-13
Configuration Examples for IPv6 Multicast 42-21
Example: Enabling IPv6 Multicast Routing 42-21
Example: Configuring IPv6 SSM Mapping 42-21
Example: Configuring Rendezvous Point 42-21
Troubleshooting Tips
42-21
Additional References 42-23
Related Documents 42-23
Standards 42-23
MIBs 42-23
RFCs 42-23
Technical Assistance 42-23
Feature Information for IPv6 Multicast
42-24
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxxiv
OL-23826-09
Contents
CHAPTER
43
Configuring Switched Port Analyzer
Finding Feature Information
Contents
43-1
43-1
43-1
SPAN Limitations and Configuration Guidelines
43-1
Understanding SPAN 43-2
Overview 43-2
SPAN Session 43-3
Source Interface 43-3
Destination Interface 43-4
Traffic Types 43-4
SPAN Traffic 43-4
Configuring SPAN 43-4
Creating a SPAN Session 43-4
SUMMARY STEPS 43-4
DETAILED STEPS 43-5
Removing Sources or Destination from a SPAN Session
SUMMARY STEPS 43-6
DETAILED STEPS 43-6
Configuration Examples for SPAN 43-6
Verifying Local SPAN 43-6
43-5
Additional References 43-8
Related Documents 43-8
Standards 43-8
MIBs 43-8
RFCs 43-8
Technical Assistance 43-8
Feature Information for Switched Port Analyzer
43-9
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
xxxv
Contents
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
xxxvi
OL-23826-09
About This Guide
This section describes the objectives, audience, organization, and conventions of this software
configuration guide. It contains the following sections:
•
Document Revision History, page xxxvii
•
Objectives, page xlvii
•
Audience, page xlvii
•
Organization, page xlvii
•
Conventions, page l
•
Related Documentation, page li
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page li
Document Revision History
The Document Revision History table records technical changes to this document.
Document
Number
Date
Change Summary
OL-23826-01 November 2011
Initial version of the document.
OL-23826-02 January 2012
Following are the updates specific to this release:
•
Cisco ASR 901 supports port based licensing. This type of
license is applicable to gigabit ethernet ports only. Ports 4 to
7 are enabled by default. For Copper and SFP ports, you need
to purchase separate licenses to enable them. For more
details see, Chapter 2, “Licensing”.
•
SL-A901-B license supports VRF-Lite. For more details see,
Chapter 2, “Licensing”.
•
The minimum time interval supported for BFD is 50 ms. For
more details, see Chapter 19, “Configuring Bidirectional
Forwarding Detection”.
•
Cisco ASR 901 supports MLPPP configuration. For more
details, see Chapter 25, “Configuring MLPPP”.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xxxvii
Chapter
Document
Number
Date
OL-23826-03 May 2012
Change Summary
•
Structure-Agnostic TDM over Packet (SAToP) is a
structure-agnostic protocol for transporting TDM using
pseudowires (PW). PW connections using SAToP are
supported.
•
SAToP pseudowire with UDP encapsulation is supported.
•
CESoPSN pseudowire with UDP encapsulation is supported.
•
QoS for CESoPSN over UDP and SAToP over UDP—IP
DSCP and IP Precedence via service-policy, and Type of
Service (ToS) settings are supported in pseudowire class.
•
L2VPN Pseudowire Redundancy feature:
– provides backup service for circuit emulation (CEM)
pseudowires.
– enables the network to detect failure, and reroute the
Layer 2 (L2) service to another endpoint that can
continue to provide the service.
– provides the ability to recover from a failure: either the
failure of the remote PE router, or of the link between
the PE and the CE routers.
•
T1 Local Switching—This feature allows switching of Layer
2 data between two CEM interfaces on the same router.
•
IEEE 1588-2008 (PTPv2) Ordinary Clock (OC) Master
Clock mode is supported.
•
G.781 QL-enabled mode is supported for synchronization
clock selection to avoid timing loops in the network.
•
ESMC—This feature dynamically distributes clock-quality
across synchronous ethernet links and enables selection of
the best clock in the network.
•
Onboard Failure Logging (OBFL)—OBFL provides a
mechanism to store hardware, software, and environment
related critical data in a non-volatile memory, such as flash
EPROM or EEPROM on routers. Stored OBFL data can be
retrieved in the event of a crash or failure.
•
MAC Flap control—A MAC flap occurs when a switch
receives packets from two different interfaces, with the same
source MAC address. When a MAC flap occurs, Cisco ASR
901 does Err-Disabling in one of the ports that has flapping.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-xxxviii
OL-23826-09
Chapter
Document
Number
Date
Change Summary
•
CFM over EFP Interface with cross connect— This feature
allows you to:
– Forward continuity check messages (CCM) towards the
core over cross connect pseudowires.
– Receive CFM messages from the core.
– Forward CFM messages to the access side (after
Continuity Check Database [CCDB] based on
maintenance point [MP] filtering rules).
•
IPSLA Path Discovery—The LSP path discovery (LPD)
feature allows the IP SLA MPLS LSP to automatically
discover all the active paths to the forwarding equivalence
class (FEC), and configure LSP ping and traceroute
operations across various paths between the provide edge
(PE) devices.
•
Routed QinQ—Pop 2 configuration is supported.
•
Port Based EoMPLS—Port mode allows a frame coming
into an interface to be packed into an MPLS packet and
transported over the MPLS backbone to an egress interface.
The entire ethernet frame without the preamble or FCS is
transported as a single packet.
•
Rommon and MCU upgrade—Upgradable MCU and
ROMMON is bundled with the IOS image. Once the IOS
image is upgraded, both the MCU and the ROMMON images
also get upgraded.
•
T1.403 remote loopback—Cisco ASR 901 accepts the
remote loopback (line and payload) initiated at the far end.
•
Layer3 VPN over REP/MST is supported.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xxxix
Chapter
Document
Number
Date
OL-23826-04 August 2012
Change Summary
Following are the updates specific to this release:
•
DHCP client on SVI—This feature allows you to configure
DHCP client on SVI interface.
•
HSRP/VRRP—This feature allows you to configure the Hot
Standby Router Protocol (HSRP) or Virtual Router
Redundancy Protocol (VRRP) protocol.
•
TWAMP Responder—This feature allows you to deploy
TWAMP in a simplified network architecture, with the
control-client and the session-sender on one device and the
server and the session-reflector on another device.
•
Dying Gasp—This feature allows you to send notifications
during power failure, link down, router reload and link
administratively down conditions.
•
Multihop BFD—This feature allows you to do subsecond
forwarding failure detection for a destination with more than
one hop and up to 255 hops.
•
Ethernet Loopback—This feature allows you to use per-port
and per VLAN Ethernet loopback to test connectivity at
initial startup, to test throughput, and to test quality of
service in both directions.
•
LLDP—This feature allows the network devices to advertise
information about themselves to other devices in the
network.
•
Bit Error Rate Testing—This feature allows you to test the
integrity of the physical layer. For more details, see Bit Error
Rate Testing.
•
IPv6 Support—This feature supports Long Term Evolution
(LTE) rollouts that provides high-bandwidth data connection
for mobile wireless devices. The Cisco ASR 901 router
supports IPv6 addressing on Switch Virtual Interface (SVI),
Loopback, and Ethernet interfaces. For more details, see
IPv6 Support on the Cisco ASR 901 Router.
•
Labeled BGP Support—This feature describes how to add
label mapping information to the Border Gateway Protocol
(BGP) message that is used to distribute the route on the
Cisco ASR 901 Series Aggregation Services Routers. For
more details, see Labeled BGP Support.
•
MPLS Traffic Engineering—This feature describes the Fast
Reroute (FRR) link protection and Bidirectional Forwarding
Detection (BFD)-triggered FRR feature of Multiprotocol
Label Switching (MPLS) traffic engineering (TE). The
MPLS TE is supported on the Cisco ASR 901 router to
enable only the FRR. The traffic engineering aspects of
MPLS TE is currently not supported. For more details, see
MPLS Traffic Engineering - Fast Reroute Link Protection.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-xl
OL-23826-09
Chapter
Document
Number
Date
Change Summary
OL-23826-05 October 2012
Following are the updates specific to this release:
•
IMA—This feature allows you to configure Inverse
Multiplexing over ATM (IMA).
•
TDM Local Switching—This feature allows you to
configure Time Division Multiplexing (TDM) local
switching on the T1 or E1 mode.
•
Licensing—This feature allows you to view the list of
licenses available for the Cisco ASR 901 router. The
10gigUpgrade and Gige4portflexi licenses are available
from Cisco IOS Release 15.2(2)SNH1 onwards.
•
EVC—The restrictions section of the Ethernet Virtual
Connections feature is updated.
•
L2PT—This feature allows tunneling of Ethernet protocol
frames across layer 2 switching domains.
•
ACL-based QoS—The Access Control List (ACL) based Qos
feature provides classification based on source and
destination. The current implementation of this feature
supports only named ACLs.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xli
Chapter
Document
Number
Date
OL-23826-06 February 2013
Change Summary
Following are the updates specific to this release:
•
IPv6 over MPLS—Enables the service providers running an
MPLS/IPv4 infrastructure to offer IPv6 services without any
major changes in the infrastructure, see IPv6 over MPLS: 6PE
and 6VPE, page 1 for more information.
•
Remote Loop-Free Alternate—provides local protection for
unicast traffic in pure IP and MPLS networks, see Remote
Loop-Free Alternate - Fast Reroute, page 1 for more
information.
•
MPLS over MLPPP —Allows you to use labeled switch paths
(LSPs) over MLPPP links, see Configuring MLPPP, page 1 for
more information.
•
Zero Touch Provisioning—Enables the ASR 901 router to auto
configure itself, download an updated image, connect to the
network, and start the operation as soon as it is cabled and
powered up, see Managing and Monitoring Network
Management Features, page 1 for more information.
•
Digital Optical Monitoring—Support for Digital Optical
Monitoring (DOM) for Gig Optics on ASR 901, see Digital
Optical Monitoring, page 1 for more information.
•
BC Licensing—Supports for Precision Time Protocol (PTP)
Boundary Clock (BC) is introduced on the ASR 901 routers.
ADVANCED TIMING(1588BC) license should be installed to
use the BC feature, see Licensing, page 1 for more information.
•
1588V2 Boundary Clock—Supports for Precision Time
Protocol (PTP) Boundary Clock (BC) is introduced on the
ASR 901 routers, see Configuring Clocking, page 1 for more
information.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-xlii
OL-23826-09
Chapter
Document
Number
Date
Change Summary
OL-23826-07 March 2013
•
Configuring Y.1564 to Generate Ethernet Traffic—Y.1564 is
an Ethernet service activation or performance test
methodology for turning up, installing, and troubleshooting
Ethernet-based services. This test methodology allows for
complete validation of Ethernet service-level agreements
(SLAs) in a single test. Using traffic generator performance
profile, you can create the traffic based on your
requirements. The network performance like throughput,
loss, and availability are analyzed using Layer 2 traffic with
various bandwidth profiles.
•
Ethernet Synthetic Loss Measurement in Y.1731—Allows to
measure the Frame Loss Ratio (FLR) in the network, that is,
the ratio of frames lost to frames sent, using synthetic
frames.
•
EVC Default Encapsulation for QinQ and
Xconnect—Supports EVC default encapsulation on the
Cisco ASR 901 router. This feature matches and forwards all
the ingress traffic on the port. The default service instance on
a port is configured using the encapsulation default
command.
•
Hot Standby Pseudowire Support for ATM and TDM Access
Circuits—Improves the availability of pseudowires by
detecting failures and handling them with minimal
disruption to the service. This feature allows the backup
pseudowire to be in a “hot standby” state, so that it can
immediately take over if the primary pseudowire fails.
•
Microwave ACM Signaling and EEM Integration—Enables
the microwave radio transceivers to report link bandwidth
information to an upstream Ethernet switch and take action
on the signal degradation to provide optimal bandwidth.
•
Multi-UNI CFM MEPs in the Same VPN—Services are
configured such that two or more bridge domains (BDs) are
used to achieve UNI isolation and backhauling towards
provider edge (PE) device. Local MEPs (with up direction)
need to be configured on the UNIs (with the associated BDs)
to monitor the service backhaul connection.
•
OSPFv3 MIBs—The OSPFV3-MIB is supported from Cisco
IOS Release 15.3(2)S onwards. This MIB module is for
OSPF version 3.
•
Remote Loop-Free Alternate - Fast Reroute for
EoMPLS—The Remote Loop-Free Alternate - Fast Reroute
for EoMPLS feature is introduced.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xliii
Chapter
Document
Number
Date
Change Summary
•
TCAM in Cisco ASR 901 Router—Effective with Cisco IOS
Release 15.3(2)S, the Ternary Content Addressable Memory
(TCAM) is allocated and deallocated dynamically, which
improves both feature scalability and the efficiency of usage
of TCAM.
•
Traffic Engineering - Fast Reroute for EoMPLS—The
Traffic Engineering - Fast Reroute for EoMPLS feature is
introduced.
•
Y.1731 Performance Monitoring—Provides standards-based
Ethernet performance monitoring as outlined in the ITU-T
Y-1731 specification and interpreted by the Metro Ethernet
Forum (MEF).
•
Combo Port Media Type Select—Starting with Cisco IOS
Release 15.3(2)S, the Cisco ASR 901 router supports
selection of combo ports as the media type. A combo port is
considered as a single interface with dual front ends (an
RJ-45 connector and an SFP module connector).
•
Configurable MTU on Physical Interface—Starting with
Cisco IOS Release 15.3(2)S, the Cisco ASR 901 router
supports modification of MTU size on physical interface.
•
Disabling MAC Address Learning on an Interface or Bridge
Domain—Starting with Cisco IOS Release 15.3(2)S, you
can control MAC address learning on an interface or VLAN
to manage the available MAC address table space by
controlling which interfaces or VLANs can learn MAC
addresses.
•
Layer 3 Ping in Customer EVC—Starting with Cisco IOS
Release 15.3(2)S, pop 2 configuration is supported on layer
2 and layer 3 operations. Additionally, it is supported on
GigabitEthernet and port channel interfaces.
•
Sub-second Link OAM Timers—Starting with Cisco IOS
Release 15.3(2)S, the Cisco ASR 901 router supports
sub-second OAM timers.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-xliv
OL-23826-09
Chapter
Document
Number
Date
OL-23826-08 July 2013
Change Summary
•
Autonomic Networking—Autonomic networking is
supported from Cisco IOS Release 15.3(2)S onwards. It
makes devices more intelligent and simplifies the interface
between the operator and Network Management System
(NMS) system, by providing a strong abstraction across the
network, distributed on each device. It also automatically
provides all relevant best practices, and keeps them up to
date, without the need for human intervention.
•
Storm Control—The Storm Control feature prevents traffic
on a LAN from being disrupted by a broadcast, multicast, or
unknown unicast storm on one of a port.
•
Egress Policing—Egress policing can be classified based on
QoS-groups, DSCP, and precedence value. For QoS-groups
to work at egress, you should map the traffic at ingress to a
specific QoS-group value.
•
MPLS Traffic Engineering (TE)—Fast Reroute (FRR) Link
Protection—Support for CESoPSN, SAToP, and ATM/IMA
was added from Cisco IOS Release 15.3(3)S onwards.
•
Multiaction Ingress Policer on EVC—Effective with Cisco
IOS Release 15.3(3)S, the Cisco ASR 901 supports policing
ingress traffic over the cross connect EVC, similar to bridge
domain service policy.
•
Y.1731 Performance Monitoring—Effective with Cisco IOS
Release 15.3(3)S, the Cisco ASR 901 router supports ITU-T
Y.1731 performance monitoring on the following interfaces:
– SLM support on the EVC cross connect
– SLM support on the Port-Channel EVC cross connect
– DMM and SLM support on the EVC BD for both the up
and down MEPs
– SLM support on the EVC cross connect for both the up
and down MEPs
•
RFC 3107 Labeled BGP Support for TDM Pseudowire—The
RFC 3105 labeled BGP is supported for TDM pseudowire
from Cisco IOS Release 15.3(3)S onwards.
•
Support for Digital Optical Monitoring (DOM) for 10 Gig
Optics—Effective with Cisco IOS Release 15.3(3)S, Cisco
ASR 901 supports DOM for both 1G and 10G SFPs.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xlv
Chapter
Document
Number
Date
OL-23826-09 November 2013
Change Summary
•
1588v2 Hybrid Clock—To improve the clock quality, you
can either improve the oscillator class or reduce the number
of hops between the master and the slave. In PTP hybrid
mode, the oscillator class is improved by using a physical
layer clock (sourced from a stratum-1 clock) instead of the
available internal oscillator. The PTP hybrid mode is
supported for ordinary clock (in slave mode only) and
boundary clock.
•
Dual REP Edge No-Neighbor—Effective with Cisco IOS
release 15.4.(1)S, you can configure the non-REP switch
facing ports on a single device as dual edge no-neighbor
ports. These ports inherit all properties of edge ports, and
overcome the limitation of not converging quickly during a
failure.
•
EoMPLS/TDM Pseudowire Redundancy over
FRR—Effective with Cisco IOS Release 15.4(1)S, support
was added for EoMPLS/TDM pseudowire redundancy over
FRR.
•
Ethernet loopback (NOSTG CLI and terminal loopback
)—Effective with Cisco IOS Release 15.4(1)S, the Cisco
ASR 901 supports internal loopback on Bridge-domain
EFPs.
•
IPv4 Multicast—Describes how to configure IP multicast in
an IPv4 network. IP multicast is an efficient way to use
network resources, especially for bandwidth-intensive
services such as audio and video.
•
IPv6 Multicast—Describes how to configure basic IP
multicast in an IPv6 network.
•
Extending QoS over MLPPP Interface—Effective with
Cisco IOS Release 15.4(1)S, the QoS functionality on the
MLPPP interface is extended to support:
– QoS for MPLS over MLPPP
– QoS for CPU generated traffic
•
Redundant PTP instances as per G.8265.1—PTP redundancy
is an implementation on different clock nodes by which the
PTP slave clock node interacts with multiple master ports
such as grand master, boundary clock nodes, and so on. A
new servo mode is defined under PTP to support high PDV
scenarios (when the PDVs exceed G.8261 standard profiles).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-xlvi
OL-23826-09
Chapter
Document
Number
Date
Change Summary
•
REP over LAG—Effective with Cisco IOS Release 15.4(1)S,
the Cisco ASR 901 supports REP over port-channel.
•
Switched Port Analyzer (SPAN)—Effective with Cisco IOS
Release 15.4(1)S, the Cisco ASR 901 supports Local SPAN.
Local SPAN supports a SPAN session entirely within one
switch. You can analyze network traffic passing through
ports or VLANs by using SPAN to send a copy of the traffic
to another port on the switch that has been connected to a
network analyzer or other monitoring or security devices.
SPAN copies (or mirrors) traffic received or sent (or both) on
source ports to a destination port for analysis.
•
Y.1564 over EVC CrossConnect—Effective with Cisco IOS
release 15.4.(01)S, traffic can be generated over cross
connect interface. Figure 10-3 shows the Traffic Generator
topology over cross connect describing the traffic flow in the
external and internal modes.
Objectives
This guide explains how to configure software features on the Cisco ASR 901-TDM version and
Cisco ASR 901-Ethernet version routers. Unless otherwise stated, the features described in this guide
apply to both the routers.
Audience
This guide is for the person responsible for configuring the router. This guide is intended for the
following audiences:
•
Customers with technical networking background and experience.
•
System administrators who are familiar with the fundamentals of router-based internetworking, but
who may not be familiar with Cisco IOS software.
•
System administrators who are responsible for installing and configuring internetworking
equipment, and who are familiar with Cisco IOS software.
Organization
The major sections of this software configuration guide are listed in the following table:
Chapter
Description
Chapter 1, “Cisco ASR 901
Router Overview”
Provides an overview of the Cisco ASR 901 router.
Chapter 2, “Licensing”
Describes the licensing aspects of the router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xlvii
Chapter
Chapter
Description
Chapter 3, “First-Time
Configuration”
Describes the first time configuration of the router.
Chapter 4, “Managing and
Monitoring Network
Management Features”
Describes how to monitor, manage and deploy a variety of network
management features.
Chapter 5, “Using the
Command-Line Interface”
Describes the CLI of the router.
Chapter 6, “Software
Upgrade”
Describes how to upgrade the Cisco IOS image on the router.
Chapter 7, “Configuring
Gigabit Ethernet Interfaces”
Describes how to configure gigabit ethernet interfaces on the router.
Chapter 8, “Configuring
Ethernet Virtual Connections”
Describes how to configure EVCs on the router.
Chapter 9, “Configuring
EtherChannels”
Describes how to configure EtherChannels on the router.
Chapter 10, “Configuring
Ethernet OAM”
Describes how to configure ethernet OAM on the router.
Chapter 11, “ITU-T Y.1731
Performance Monitoring”
Displays information on the ITU-T Y.1731 Performance Monitoring
for the Cisco ASR 901 Series Aggregation Services Router.
Chapter 12, “Configuring
Resilient Ethernet Protocol”
Describes how to configure REP on the router.
Chapter 13, “Configuring MST Describes how to configure MSTP on the router.
on EVC Bridge Domain”
Chapter 14, “Configuring
Multiprotocol Label
Switching”
Describes how to configure MPLS on the router.
Chapter 15, “Configuring
EoMPLS”
Describes how to configure EoMPLS on the router.
Chapter 16, “Configuring
MPLS VPNs”
Describes how to configure MPLS VPNs on the router.
Chapter 17, “Configuring
MPLS OAM”
Describes how to configure MPLS OAM on the router.
Chapter 18, “Configuring
Routing Protocols”
Describes how to configure the routing protocols on the router.
Chapter 19, “Configuring
Bidirectional Forwarding
Detection”
Describes how to configure BFD on the router.
Chapter 20, “Configuring
T1/E1 Controllers”
Describes how to configure T1/E1 controllers on the router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-xlviii
OL-23826-09
Chapter
Chapter
Description
Chapter 21, “Configuring
Pseudowire”
Describes how to configure pseudowire on the router.
Chapter 22, “Configuring
Clocking”
Describes how to configure clocking on the router.
Chapter 23, “Cisco IOS IP
SLA”
Describes the IPSLA aspects of the router.
Chapter 24, “Configuring
QoS”
Describes how to configure QoS on the router.
Chapter 25, “Configuring
MLPPP”
Describes how to configure MLPPP on the router.
Chapter 26, “Onboard Failure
Logging”
Describes how to configure OBFL on the router.
Chapter 27, “Hot Standby
Router Protocol and Virtual
Router Redundancy Protocol”
Describes how to configure HSRP and VSRP.
Chapter 28, “Configuring Link Describes how to configure LLDP.
Layer Discovery Protocol”
Chapter 29, “Configuring
Multihop Bidirectional
Forwarding Detection”
Describes how to configure multihop BFD
Chapter 30, “Bit Error Rate
Testing”
Describes how to configure Bit Error Rate testing.
Chapter 31, “Microwave ACM Describes how the Microwave Adaptive Code Modulation (ACM)
Signaling and EEM
Signaling and Embedded Event Manager (EEM) integration that
Integration”
enables the microwave radio transceivers to report link bandwidth
information to an upstream Ethernet switch and take action on the
signal degradation to provide optimal bandwidth.
Chapter 32, “IPv6 Support on
the Cisco ASR 901 Router”
Describes how to support Long Term Evolution (LTE) rollouts that
provides high-bandwidth data connection for mobile wireless
devices.
Chapter 33, “Labeled BGP
Support”
Describes how to add label mapping information to the Border
Gateway Protocol
Chapter 34, “MPLS Traffic
Engineering - Fast Reroute
Link Protection”
Describes how to add Fast Reroute (FRR) link protection and
Bidirectional Forwarding Detection (BFD)-triggered FRR feature of
Multiprotocol Label Switching (MPLS) traffic engineering (TE).
Chapter 35, “Layer 2 Control
Protocol Peering, Forwarding,
and Tunneling”
Describes how to configure Layer 2 (L2) Control Protocol Peering,
Forwarding, and Tunneling feature on the Cisco ASR 901 Series
Aggregation Services Routers.
Chapter 36, “Configuring
Inverse Muliplexing over
ATM”
Describes how to configure Inverse Multiplexing over ATM (IMA)
technology that is used to transport ATM traffic over a bundle of T1
or E1 cables, known as IMA group in the Cisco ASR 901 Series
Aggregation Services Routers.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-xlix
Chapter
Chapter
Description
Chapter 37, “IPv6 over MPLS: Describes how to implement IPv6 VPN Provider Edge Transport over
6PE and 6VPE”
MPLS (IPv6 on Provider Edge Routers [6PE] and IPv6 on ASR 901.
Chapter 38, “Storm Control”
Describes how to monitor the incoming broadcast, multicast, and
unknown unicast packets and prevent them from flooding the LAN
ports.
Chapter 39, “Remote
Loop-Free Alternate - Fast
Reroute”
Describes the Remote Loop-free Alternate (LFA) - Fast Reroute
(FRR) feature that uses a backup route, computed using dynamic
routing protocol during a node failure, to avoid traffic loss.
Chapter 40, “Digital Optical
Monitoring”
Provides information on the digital optical monitoring (DOM) feature
for the Cisco ASR 901 Series Aggregation Services Router.
Chapter 41, “Autonomic
Networking Infrastructure”
Describes how the Autonomic Networking Infrastructure feature
makes new and unconfigured devices securely reachable by an
operator or network management system.
Chapter 41, “IPv4 Multicast”
Describes how to configure IP multicast in an IPv4 network.
Chapter 42, “IPv6 Multicast”
Describes how to configure basic IP multicast in an IPv6 network.
Chapter 43, “Configuring
Switched Port Analyzer”
Describes how to configure a switched port analyzer (SPAN) on the
Cisco ASR 901 Router.
Conventions
This publication uses the following conventions to convey instructions and information.
Convention
Description
boldface font Commands and keywords.
italic font
Variables for which you supply values.
[
Keywords or arguments that appear within square brackets are optional.
]
{x | y | z}
A choice of required keywords appears in braces separated by vertical bars. You must
select one.
screen font
Examples of information displayed on the screen.
boldface
Examples of information the user enters.
screen font
Note
Timesaver
<
>
Nonprinting characters, for example passwords, appear in angle brackets.
[
]
Default responses to system prompts appear in square brackets.
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
manual.
Means the described action saves time.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-l
OL-23826-09
Chapter
Tip
Caution
Means the following information will help you solve a problem. The tips information might not be
troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Related Documentation
The following list includes documentation related to your product by implementation.
•
Cisco ASR 901 Series Aggregation Services Router Documents
– Cisco ASR 901 Series Aggregation Services Router Command Reference
– Cisco ASR 901 Series Aggregation Services Router Hardware Installation Guide
– Cisco Regulatory Compliance and Safety Information for Cisco ASR 901 Series Aggregation
Services Router
•
Release Notes
– Release Notes for Cisco ASR 901 Series Aggregation Services Router
To access the related documentation on Cisco.com, go to:
http://www.cisco.com/en/US/partner/products/ps12077/tsd_products_support_series_home.html
Note
To obtain the latest information, access the online documentation.
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
-li
Chapter
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
-lii
OL-23826-09
CH A P T E R
1
Cisco ASR 901 Router Overview
Cisco ASR 901 Mobile Wireless Router is a cell-site access platform specifically designed to aggregate
and transport mixed-generation radio access network (RAN) traffic. The router is used at the cell site
edge as a part of a 2G, 3G, or 4G radio access network (RAN). The Cisco ASR 901 is availabe in the
following models:
•
Cisco ASR 901-TDM version (A901-12C-FT-D, A901-4C-FT-D, A901-6CZ-FT-D,
A901-6CZ-FT-A)
•
Cisco ASR 901-Ethernet version (A901-12C-F-D, A901-4C-F-D, A901-6CZ-F-D, A901-6CZ-F-A)
The Cisco ASR 901 router helps enable a variety of RAN solutions by extending IP connectivity to
devices using Global System for Mobile Communications (GSM), General Packet Radio Service
(GPRS), Node Bs using HSPA or LTE, Base Transceiver Stations (BTSs) using Enhanced Data Rates for
GSM Evolution (EDGE), Code Division Multiple Access (CDMA), CDMA-2000, EVDO, or WiMAX,
and other cell-site equipment.
The Cisco ASR 901 router transparently and efficiently transports cell-site voice, data, and signaling
traffic over IP using traditional T1/E1 circuits, including leased line, microwave, and satellite. It also
supports alternative backhaul networks, including Carrier Ethernet and Ethernet in the First Mile (EFM).
The Cisco ASR 901 router also supports standards-based Internet Engineering Task Force (IETF)
Internet protocols over the RAN transport network, including those standardized at the Third-Generation
Partnership Project (3GPP) for IP RAN transport.
Custom designed for the cell site, the Cisco ASR 901 features a small form factor, extended operating
temperature, and cell-site DC input voltages.
The Cisco ASR 901 TDM version provides 12 Gigabit Ethernet ports, 16 T1/E1 ports and one
Management port. Whereas, the Cisco ASR 901 Ethernet version does not contain the 16 T1/E1 ports.
It has only 12 Gigabit Ethernet ports and one management port.
The Cisco ASR 901 router supports Ethernet Virtual Circuits (EVC) only. Metro-Ethernet Forum (MEF)
defines an Ethernet Virtual Connection as an association between two or more user network interfaces
identifying a point-to-point or multipoint-to-multipoint path within the service provider network. An
EVC is a conceptual service pipe within the service provider network.
For more information on EVCs, see Configuring Ethernet Virtual Connections, page 8-1.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
1-1
Chapter 1
Cisco ASR 901 Router Overview
Introduction
Introduction
A RAN is typically composed of thousands of BTSs or Node Bs, hundreds of base station controllers or
radio network controllers (BSCs or RNCs), and several mobile switching centers (MSCs). The BTS or
Node Bs and BSC or RNC are often separated by large geographic distances, with the BTSs or Node Bs
located in cell sites uniformly distributed throughout a region, and the BSCs, RNCs, and MSCs located
at suitably chosen Central Offices (CO) or mobile telephone switching offices (MTSO).
The traffic generated by a BTS or Node B is transported to the corresponding BSC or RNC across a
network, referred to as the backhaul network, which is often a hub-and-spoke topology with hundreds
of BTS or Node Bs connected to a BSC or RNC by point-to-point time division multiplexing (TDM)
trunks. These TDM trunks may be leased-line T1/E1s or their logical equivalents, such as microwave
links or satellite channels.
The Cisco ASR 901 has two different types of interfaces by default: network node interfaces (NNIs) to
connect to the service provider network and user network interfaces (UNIs) to connect to customer
networks. Some features are supported only on one of these port types. You can also configure enhanced
network interfaces (ENIs). An ENI is typically a user-network facing interface and has the same default
configuration and functionality as UNIs, but can be configured to support protocol control packets for
Cisco Discovery Protocol (CDP), Spanning-Tree Protocol (STP), EtherChannel Link Aggregation
Control Protocol (LACP).
Features
This section contains the following topics:
•
Performance Features, page 1-2
•
Management Options, page 1-3
•
Manageability Features, page 1-3
•
Security Features, page 1-4
•
Quality of Service and Class of Service Features, page 1-4
•
Layer 3 Features, page 1-5
•
Layer 3 VPN Services, page 1-5
•
Monitoring Features, page 1-5
Performance Features
•
Autosensing of port speed and autonegotiation of duplex mode on all ports for optimizing
bandwidth.
•
Automatic-medium-dependent interface crossover (auto-MDIX) capability on 100 and 100/1000
Mbps interfaces and on 100/1000 BASE-T/TX small form-factor pluggable (SFP) module interfaces
that enables the interface to automatically detect the required cable connection type
(straight-through or crossover) and to configure the connection appropriately.
•
EtherChannel for enhanced fault tolerance and for providing up to 8 Gbps (Gigabit EtherChannel)
or 800 Mbps (Fast EtherChannel) full duplex of bandwidth between switches, routers, and servers.
•
Link Aggregation Control Protocol (LACP) for automatic creation of EtherChannel links (supported
only on NNIs or ENIs).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
1-2
OL-23826-09
Chapter 1
Cisco ASR 901 Router Overview
Features
•
Forwarding of Layer 2 and Layer 3 packets at Gigabit line rate.
Management Options
•
CLI—You can access the CLI either by connecting your management station directly to the router
console port or by using Telnet from a remote management station. For more information about the
CLI, see Chapter 5, “Using the Command-Line Interface.”
•
Cisco Configuration Engine—The Cisco Configuration Engine is a network management device that
works with embedded Cisco IOS CNS Agents in the Cisco ASR 901 Series Aggregation Services
Router software. You can automate initial configurations and configuration updates by generating
router-specific configuration changes, sending them to the router, executing the configuration
change, and logging the results.
•
SNMP—SNMP management applications such as CiscoWorks2000 LAN Management Suite (LMS)
and HP OpenView. You can manage from an SNMP-compatible management station that is running
platforms such as HP OpenView or SunNet Manager.
For information about configuring SNMP, see
http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf014.html.
For the list of MIBs that Cisco ASR 901 router supports, see the Release Notes for Cisco ASR 901
router.
Manageability Features
•
Address Resolution Protocol (ARP) for identifying a router through its IP address and its
corresponding MAC address
•
Cisco Discovery Protocol (CDP) Versions 1 and 2 for network topology discovery and mapping
between the router and other Cisco devices on the network (supported on NNIs by default, can be
enabled on ENIs, not supported on UNIs)
•
Network Time Protocol (NTP) for providing a consistent time stamp to all routers from an external
source
•
Cisco IOS File System (IFS) for providing a single interface to all file systems that the Cisco ASR
901 Series Aggregation Services Router uses.
•
In-band management access for up to 5 simultaneous Telnet connections for multiple CLI-based
sessions over the network. Effective with Cisco IOS Release 15.3(2)S1, in-band management access
for up to 98 simultaneous Telnet connections for multiple CLI-based sessions over the network.
•
In-band management access for up to five simultaneous, encrypted Secure Shell (SSH) connections
for multiple CLI-based sessions over the network.
•
In-band management access through SNMP Versions 1 and 2c get and set requests.
•
Out-of-band management access through the router console port to a directly attached terminal or
to a remote terminal through a serial connection or a modem
•
User-defined command macros for creating custom router configurations for simplified deployment
across multiple routers
•
Support for metro Ethernet operation, administration, and maintenance (OAM) IEEE 802.1ag
Connectivity Fault Management (CFM), Ethernet Line Management Interface (E-LMI) on
customer-edge and provider-edge devices, and IEEE 802.3ah Ethernet OAM discovery, link
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
1-3
Chapter 1
Cisco ASR 901 Router Overview
Features
monitoring, remote fault detection, and remote loopback, and IEEE 802.3ah Ethernet OAM
discovery, link monitoring, remote fault detection, and remote loopback (requires the metro IP
access or metro access image)
•
Configuration replacement and rollback to replace the running configuration on a router with any
saved Cisco IOS configuration file
•
CPU utilization threshold logs.
Security Features
•
Password-protected access (read-only and read-write access) to management interfaces for
protection against unauthorized configuration changes
•
Configuration file security so that only authenticated and authorized users have access to the
configuration file, preventing users from accessing the configuration file by using the password
recovery process
•
Multilevel security for a choice of security level, notification, and resulting actions
•
Automatic control-plane protection to protect the CPU from accidental or malicious overload due to
Layer 2 control traffic on UNIs or ENIs
•
TACACS+, a proprietary feature for managing network security through a TACACS server
•
RADIUS for verifying the identity of, granting access to, and tracking the actions of remote users
through authentication, authorization, and accounting (AAA) services
•
Extended IP access control lists for defining security policies in the inbound direction on physical
ports.
•
Extended IP access control lists for defining security policies in the inbound and outbound direction
on SVIs.
Quality of Service and Class of Service Features
•
Configurable control-plane queue assignment to assign control plane traffic for CPU-generated
traffic to a specific egress queue.
•
Cisco modular quality of service (QoS) command-line (MQC) implementation
•
Classification based on IP precedence, Differentiated Services Code Point (DSCP), and IEEE
802.1p class of service (CoS) packet fields, or assigning a QoS label for output classification
•
Policing
– One-rate policing based on average rate and burst rate for a policer
– Two-color policing that allows different actions for packets that conform to or exceed the rate
– Aggregate policing for policers shared by multiple traffic classes
•
Table maps for mapping CoS, and IP precedence values
•
Queuing and Scheduling
– Class-based traffic shaping to specify a maximum permitted average rate for a traffic class
– Port shaping to specify the maximum permitted average rate for a port
– Class-based weighted queuing (CBWFQ) to control bandwidth to a traffic class
– Low-latency priority queuing to allow preferential treatment to certain traffic
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
1-4
OL-23826-09
Chapter 1
Cisco ASR 901 Router Overview
Features
•
Per-port, per-VLAN QoS to control traffic carried on a user-specified VLAN for a given interface.
Layer 3 Features
•
IP routing protocols for load balancing and for constructing scalable, routed backbones:
– OSPF
– BGP Version 4
– IS-IS dynamic routing
– BFD protocol Bidirectional Forwarding Detection (BFD) Protocol to detect forwarding-path
failures for OSPF, IS-IS, and BGP routing protocols
•
IP routing between VLANs (inter-VLAN routing) for full Layer 3 routing between two or more
VLANs, allowing each VLAN to maintain its own autonomous data-link domain
•
Static IP routing for manually building a routing table of network path information
•
Equal-cost routing for load balancing and redundancy
•
Internet Control Message Protocol (ICMP) and ICMP Router Discovery Protocol (IRDP) for using
router advertisement and router solicitation messages to discover the addresses of routers on directly
attached subnets
Layer 3 VPN Services
These features are available only when the Cisco ASR 901router is running the Advance Metro IP
services.
•
Multiple VPN routing/forwarding (multi-VRF) instances in customer edge devices (multi-VRF CE)
to allow service providers to support multiple virtual private networks (VPNs) and overlap IP
addresses between VPNs
•
MPLS VPN is supported.
Monitoring Features
•
Router LEDs that provide port- and router-level status
•
Syslog facility for logging system messages about authentication or authorization errors, resource
issues, and time-out events
•
Enhanced object tracking for HSRP clients (requires metro IP access image)
•
IP Service Level Agreements (IP SLAs) support to measure network performance by using active
traffic monitoring (requires metro IP access or metro access image)
•
IP SLAs EOT to use the output from IP SLAs tracking operations triggered by an action such as
latency, jitter, or packet loss for a standby router failover takeover (requires metro IP access or metro
access image)
•
EOT and IP SLAs EOT static route support to identify when a preconfigured static route or a DHCP
route goes down (requires metro IP access or metro access image)
•
Embedded event manager (EEM) for device and system management to monitor key system events
and then act on them though a policy (requires metro IP access or metro access image)
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
1-5
Chapter 1
Cisco ASR 901 Router Overview
Features
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
1-6
OL-23826-09
CH A P T E R
2
Licensing
This feature module describes the licensing aspects of the Cisco ASR 901 Series Aggregation Services
Router.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for Licensing” section on page 2-17.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Feature Overview, page 2-2
•
Licenses Supported on Cisco ASR 901 Router, page 2-2
•
License Types, page 2-4
•
Port or Interface Behavior, page 2-5
•
Generating the License, page 2-11
•
Installing the License, page 2-11
•
Changing the License, page 2-12
•
Return Materials Authorization License Process, page 2-13
•
Verifying the License, page 2-14
•
Where to Go Next, page 2-14
•
Additional References, page 2-15
•
Feature Information for Licensing, page 2-17
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-1
Chapter 2
Licensing
Feature Overview
Feature Overview
The Cisco ASR 901 router license is similar to any other software license in Cisco. It is tied to the
Unique Device Identifier (UDI) —where the license is integrated to the PID (Product Identifier) and SN
(Serial Number). A license generated for one router cannot be shared or installed in any other router.
Complete these steps to obtain the license file:
1.
Purchase the required Product Authorization Key (PAK).
2.
Get the UDI from the device.
3.
Enter the UDI and PAK in the Cisco’s licensing portal.
You will receive a license file through email.
4.
Install the licenses on the device. For more information on how to install the license, see Installing
the License, page 2-11.
In addition to using the router CLI, you can install the license using the Cisco License Manager (CLM)
or the Callhome interface.
Licenses Supported on Cisco ASR 901 Router
The following licenses are supported:
License
Description
Sl.No. Chassis PID
License PID
1
SL-A901-A
AdvancedMetroIP Image
Access
SL-A901-B
IPBase
A901-12C-FT-D
A901-12C-F-D
License Type (Image or Feature)
A901-4C-FT-D
A901-4C-F-D
A901-6CZ-FT-A
A901-6CZ-FT-D
A901-6CZ-F-A
A901-6CZ-F-D
2
A901-12C-F-D
Image (by default gets enabled)
A901-12C-FT-D
A901-4C-FT-D
A901-4C-F-D
A901-6CZ-FT-A
A901-6CZ-FT-D
A901-6CZ-F-A
A901-6CZ-F-D
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-2
OL-23826-09
Chapter 2
Licensing
Licenses Supported on Cisco ASR 901 Router
Sl.No. Chassis PID
License PID
3
FLS-A901-4S
A901-4C-FT-D
A901-4C-F-D
License
Description
License Type (Image or Feature)
Gige4SfpUpgrade Feature
FLS-A901-4S=
1
L-FLS-A901-4S=1
4
A901-4C-FT-D
A901-4C-F-D
Gige4CuUpgrade Feature
FLS-A901-4T
FLS-A901-4T=
1
L-FLS-A901-4T=1
5
A901-6CZ-FT-A
FLS-A901-2Z
10gigUpgrade
Feature
Gige4portflexi
Feature
1588BC
Feature
1
A901-6CZ-FT-D
FLS-A901-2Z=
A901-6CZ-F-A
L-FLS-A901-2Z=1
A901-6CZ-F-D
6
A901-6CZ-FT-A
FLS-A901-4
1
A901-6CZ-FT-D
FLS-A901-4=
A901-6CZ-F-A
L-FLS-A901-4=1
A901-6CZ-F-D
7
A901-12C-FT-D
SL-A901-T
A901-12C-F-D
A901-4C-FT-D
A901-4C-F-D
A901-6CZ-FT-A
A901-6CZ-FT-D
A901-6CZ-F-A
A901-6CZ-F-D
1 = variants are spares or represent the e-paper form.
The Cisco ASR 901 software uses the license description to resolve errors related to license availability.
You need to map the proper license PID as per the table above and purchase the licenses. The
Cisco ASR 901 router supports permanent licenses only.
You should install only a supported license for the proper chassis PID. You will get a “Not Supported”
message while trying to install a wrong license. However, license installation process will go through
and a confirmation message is displayed. When you run the show license command to display the details
of this license, the output shows license state as “NOT IN USE”, and you cannot make it “IN USE”.
The following is a sample confirmation message that is displayed on the router when you try to install a
wrong license.
Install FLS-A901-4S license on A901-6CZ-F-A (10g) boards,
10G-Router#license install flash:CAT1625U0EP_201307231358341640.lic
Installing licenses from "flash:CAT1625U0EP_201307231358341640.lic"
Installing...Feature:Gige4SfpUpgrade...Successful:Not Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were failed to install
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-3
Chapter 2
Licensing
License Types
License Types
Cisco ASR 901 router supports the following types of licenses:
•
Image Level License
•
Feature Based License
Image Level License
An Image level license corresponds to the level of the IOS image that comes up based on the licenses
present on the router. This license is enforced while booting and it uses a universal image. It activates
all the subsystems corresponding to the license that you purchased. Image based licenses (SL-A901-A
and SL-A901-B) need rebooting of the router.
Features Supported
In Cisco ASR 901, IPBase (SL-A901-B) and AdvancedMetroIPAccess (SL-A901-A) are permanent;
once installed they do not expire. Trial or temporary licenses are not supported on the Cisco ASR 901
router.
License
IPBase / SL-A901-B
Features
•
L2, EVC, 802.1Q, 802.1ad, QinQ, 802.3ah,
H-Qos, IPv4 static routes, routing protocols,
host connectivity, ACL, REP, VRF-Lite
•
E-OAM—CFM (BD, port level), IPSLA
(barring LSP)
•
Clocking—SyncE, 1588-OC Slave, 10M,
1PPS/ToD, G.781 Priority based Clock
Selection (no ESMC/SSM)
Note
AdvancedMetroIPAccess / SL-A901-A
Time-division multiplexing (TDM) is
unavailable.
•
All IPBase license features
•
MPLS—MPLS, L2VPN (EoMPLS), L3VPN,
MPLS OAM, PW redundancy
•
E-OAM—IPSLA(LSP)
•
TDM —IPoPPP/HDLC, QoS,
CESoPSNoMPLS, PPP/HDLCoMPLS, Clock
Recovery from TDM interfaces, Y.1731PM
Feature Based License
Feature based licenses are licenses used to activate individual features once the image level licenses are
used. Once the image level license is used and the appropriate subsystems are activated. Individual
feature licenses are used to activate individual features. These include:
•
Port based license
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-4
OL-23826-09
Chapter 2
Licensing
Port or Interface Behavior
Note
•
Port mode license
•
1588BC license
Copper (FLS-A901-4T), SFP (SL-A901-B), and 1588BC (SL-A901-T) licenses are feature-based
licenses. Once they are installed, the licenses become active and there is no need to reboot the router.
Port Based/Mode License
The following table lists the port number, type, and the required license for those ports:
Port Number
Port Type
Chassis PID
License Required
0-3
Copper
A901-4C-FT-D
FLS-A901-4T
A901-4C-F-D
4-7
Combo
No license is required. These ports
are enabled by default.
8-11
Small
A901-4C-FT-D
Form-Factor
A901-4C-F-D
Pluggable(SFP)
FLS-A901-4S
0-3 and 8-11
Copper and
Combo
FLS-A901-4
A901-6CZ-FT-A
A901-6CZ-FT-D
A901-6CZ-F-A
A901-6CZ-F-D
TenGig0/1,
TenGig0/2
SFP+
A901-6CZ-FT-A
FLS-A901-2Z
A901-6CZ-FT-D
A901-6CZ-F-A
A901-6CZ-F-D
By default, ports 4 to 7 are enabled on the router. When you purchase the copper or SFP port license, the
corresponding ports are only enabled. Copper and SFP port licenses can co-exist.
1588BC License
1588BC (SL-A901-T) license is a feature based license. This license does not need rebooting of the
router for activation. The following table lists the features supported
License
Features
1588BC / SL-A901-T
Clocking—1588V2 PTP boundary clock
Port or Interface Behavior
The following sections describe the port or interface behavior of the licenses:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-5
Chapter 2
Licensing
Port or Interface Behavior
•
Port Based License, page 2-6
•
10gigUpgrade License, page 2-7
•
Flexi License, page 2-8
•
1588BC License, page 2-9
Port Based License
When a port based license is not present, ports 4 to 7 are enabled. Ports 0 to 3, and ports 8 to 11 are
disabled. This is the expected behavior. Interfaces that are disabled are in the administrative down state.
Example: When Port Based License is not Installed
The following error message appears when the port based license is not installed and you use the
no shutdown command on the interface:
Router# show ip interface brief
Interface
IP-Address
GigabitEthernet0/0
unassigned
GigabitEthernet0/1
unassigned
GigabitEthernet0/2
unassigned
GigabitEthernet0/3
unassigned
GigabitEthernet0/4
unassigned
GigabitEthernet0/5
unassigned
GigabitEthernet0/6
unassigned
GigabitEthernet0/7
unassigned
GigabitEthernet0/8
unassigned
GigabitEthernet0/9
unassigned
GigabitEthernet0/10
unassigned
GigabitEthernet0/11
unassigned
FastEthernet0/0
unassigned
Vlan1
unassigned
Router#
OK?
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
Method
unset
unset
unset
unset
unset
unset
unset
unset
unset
unset
unset
unset
NVRAM
unset
Status
administratively
administratively
administratively
administratively
down
down
down
down
administratively
administratively
administratively
administratively
administratively
down
down
down
down
down
down
down
down
down
down
Protocol
down
down
down
down
down
down
down
down
down
down
down
down
down
down
Router(config-if)# interface gig 0/0
Router(config-if)# no shutdown
Router(config-if)#
*Oct 5 14:22:27.743: %LICENSE-1-REQUEST_FAILED: License request for feature fls-a901-4t
1.0 failed. UDI=MWR-3941:FHAK13101A1
Router# show interface gigabitEthernet 0/0
GigabitEthernet0/0 is administratively down, line protocol is down (disabled)
…….
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is force-up, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
LICENSE not available! Interface disabled
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Example: When Port Based License is Installed
The following example shows how to install the port based license:
Router# license install flash:FHAK13101A1_20110811190230024_fls-a901-4t.lic
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-6
OL-23826-09
Chapter 2
Licensing
Port or Interface Behavior
Installing licenses from "flash:FHAK13101A1_20110811190230024_fls-a901-4t.lic"
Installing...Feature:Fls-a901-4t...Successful:Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were failed to install
Router#*Oct 5 17:23:14.487: %LICENSE-6-INSTALL: Feature Fls-a901-4t 1.0 was installed in
this device. UDI=MWR-3941-TEST:FHAK13101A1; StoreIndex=2:Primary License Storage
Router(config)# interface gig 0/0
Router(config-if)# no shutdown
When the port based license is installed for copper or SFP ports, the corresponding ports are enabled.
Following is a sample output from the show ip interface command:
Router# show ip interface brief
Interface
IP-Address
GigabitEthernet0/0
unassigned
GigabitEthernet0/1
unassigned
GigabitEthernet0/2
unassigned
…..
Note
OK?
YES
YES
YES
Method
unset
unset
unset
Status
Protocol
up
up
administratively down down
administratively down down
Combo ports are either copper or SFP ports depending on the configuration specified in the media-type
command.
10gigUpgrade License
When you do not have the 10gigUpgrade license, the 10 Gigabit Ethernet ports are enabled in 1 Gigabit
Ethernet mode. Install the 10gigUpgrade license to enable new 10 Gigabit Ethernet ports in 10Gigabit
Ethernet mode. To enable 1 Gigabit Ethernet mode, 1 Gigabit Ethernet SFPs have to be used on both the
ends. There is no speed command to control the speed and this depends on the type of the SFP. The 10
Gigabit Ethernet ports does not support 100M speed. You can connect 10 Gigabit Ethernet SFP+ to 10
Gigabit Ethernet ports only.
Example: When 10gigUpgrade License is not Installed
The following error message appears when the 10gigUpgrade license is not installed and you use the
show interface command:
Router# show interface Ten0/1
TenGigabitEthernet0/1 is down, line protocol is down (notconnect)
Hardware is TenGigabit Ethernet, address is 2c54.2dd6.c10e (bia 2c54.2dd6.c10e)
MTU 9216 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Unknown, Unknown, media type is H10GB-CU3M
output flow-control is unsupported, input flow-control is unsupported
LICENSE not available or 1G SFP ( Interface in 1G mode )
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-7
Chapter 2
Licensing
Port or Interface Behavior
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Example: When 10gigUpgrade License is Installed
The following example shows how to install the 10gigUpgrade license:
Router# license install flash:10G-ac.lic
Installing licenses from "flash:10G-ac.lic"
Installing...Feature:10gigUpgrade...Successful:Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were failed to install
Following is a sample output from the show license command:
Router# show license
Index 1 Feature: AdvancedMetroIPAccess
Period left: Life time
License Type: Permanent
License State: Active, In Use
License Count: Non-Counted
License Priority: Medium
Index 2 Feature: IPBase
Index 3 Feature: Gige4portflexi
Index 4 Feature: 10gigUpgrade
Period left: Life time
License Type: Permanent
License State: Active, In Use
License Count: Non-Counted
License Priority: Medium
Flexi License
When a flexi license is not present, ports 4 to 7 are enabled. Ports 0 to 3, and ports 8 to 11 are disabled.
This is the expected behavior. Interfaces that are disabled are in the administrative down state.
FLS-A901-4 flexi license is a combination of copper and SFP ports. This license is not tied to any port
types. If you purchase a single FL-A901-4 license and install it, four ports are enabled and if you have
two licenses, all the eight ports are enabled. You can purchase and install two flexi licenses in a router.
Note
Flexi license is supported only on the Cisco ASR 901 10G router.
Example: When Flexi License is not Installed
The following error message appears when the flexi license is not installed and you use the
show ip interface command on the interface:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-8
OL-23826-09
Chapter 2
Licensing
Port or Interface Behavior
Router# show ip interface brief
Interface
IP-Address
GigabitEthernet0/0
unassigned
GigabitEthernet0/1
unassigned
GigabitEthernet0/2
unassigned
GigabitEthernet0/3
unassigned
GigabitEthernet0/4
unassigned
GigabitEthernet0/5
unassigned
GigabitEthernet0/6
unassigned
GigabitEthernet0/7
unassigned
GigabitEthernet0/8
unassigned
GigabitEthernet0/9
unassigned
GigabitEthernet0/10
unassigned
GigabitEthernet0/11
unassigned
FastEthernet0/0
unassigned
Vlan1
unassigned
OK?
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
Method
unset
unset
unset
unset
unset
unset
unset
unset
unset
unset
unset
unset
NVRAM
unset
Status
administratively
administratively
administratively
administratively
down
down
down
down
administratively
administratively
administratively
administratively
administratively
down
down
down
down
down
down
down
down
down
down
Protocol
down
down
down
down
down
down
down
down
down
down
down
down
down
down
Example: When Flexi License is Installed
Following is a sample output from the show license command:
Router# show license
Index 1 Feature: AdvancedMetroIPAccess
Period left: Life time
License Type: Permanent
License State: Active, In Use
License Count: Non-Counted
License Priority: Medium
Index 2 Feature: IPBase
Index 3 Feature: Gige4portflexi
1588BC License
When the SL-A901-T 1588BC license is not installed, the PTP boundary clock cannot be configured.
For more information on configuring the PTP boundary clock, see PTP Boundary Clock.
Example: When 1588BC License is not Installed
The following error message appears on configuring the PTP boundary clock, when the 1588BC license
is not installed:
Note
Though an error message appears on configuring the PTP boundary clock, the running-config file
accepts the PTP boundary clock configuration. This configuration can be saved. However, the PTP
boundary clock is not configured in the hardware, and is inactive.
Router(config)# ptp clock boundary domain 0
%ERROR: Boundary Clock needs a separate license. Please install license and reconfigure
PTP.
Router(config-ptp-clk)#
Example: When 1588BC License is Installed
The following example shows how to install the 1588BC license:
Router# license install flash:CAT1632U029_20121005013805577.lic
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-9
Chapter 2
Licensing
Port or Interface Behavior
Installing licenses from "flash:CAT1632U029_20121005013805577.lic"
Installing…Feature:1588BC…Successful:Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were failed to install
Following is a sample output from the show license command:
Note
When the 1588BC license is installed and PTP boundary clock is not configured, the license state is
displayed as Active, Not in Use. When the 1588BC license is installed and PTP boundary clock is
configured, the license state is displayed as Active, In Use.
Router#
Index 1
Index 2
Index 3
Index 4
Index 5
show license
Feature: AdvancedMetroIPAccess
Feature: IPBase
Feature: Gige4portflexi
Feature: 10gigUpgrade
Feature: 1588BC
Period left: Life time
License Type: Permanent
License State: Active, In Use
License Count: Non-Counted
License Priority: Medium
Removing the 1588BC License
If PTP boundary clock is configured, then the following error message appears when removing the
1588BC license:
Router# license clear 1588BC
Feature: 1588BC
License Type: Permanent
License State: Active, In Use
License Addition: Exclusive
License Count: Non-Counted
Comment:
Store Index: 2
Store Name: Primary License Storage
Are you sure you want to clear? (yes/[no]): yes
Handling Event, Unknown event type: 3
% Error: Could not delete in-use license
Complete the following steps to remove the 1588BC license.
Step 1
Use the no ptp clock command to remove the PTP boundary clock configuration.
Router(config-ptp-clk)# no ptp clock boundary domain 0
Step 2
Use the license clear command to remove the 1588BC license.
Router# license clear 1588BC
Feature: 1588BC
License Type: Permanent
License State: Active, Not in Use
License Addition: Exclusive
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-10
OL-23826-09
Chapter 2
Licensing
Generating the License
License Count: Non-Counted
Comment:
Store Index: 3
Store Name: Primary License Storage
Are you sure you want to clear? (yes/[no]): yes
Generating the License
Complete the following steps to generate the license:
Step 1
Use the show license udi command on the router
Step 2
Save the output.
The output contains the UDI with the Product Identifier (PID) and Serial Number (SN).
Step 3
Go to the SWIFT tool at https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet.
Step 4
Enter the PAK and UDI.
Step 5
Click Submit.
You will receive the license file through email.
Installing the License
Complete the following steps to install the license:
SUMMARY STEPS
1.
enable
2.
license install
3.
copy tftp: flash:
4.
show flash:
5.
license install license-file-name
6.
reload
7.
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-11
Chapter 2
Licensing
Changing the License
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
license install ?
Example:
(Optional) License can be installed either by placing
the license file in the tftp boot directory or by copying
the license to the flash: directory.
Router# license install ?
Step 3
copy tftp: flash:
Copies the license file to the flash: directory.
Example:
Router# copy tftp: flash:
Step 4
Displays the contents of the flash: directory.
show flash:
Example:
Router# show flash:
Step 5
license install license-file-name
Installs the license from the flash: directory.
Example:
Router# license install
FHK10LLL021_20110530015634482.lic
Step 6
Reboots the system to activate the new license.
reload
Note
Example:
Router# reload
The 1588BC license is activated after
installation. Rebooting the router is not
necessary.
Changing the License
Use the license boot level command in the global configuration mode, to change the license. Reboot the
system to activate the new license.
Note
If you do not install a license, the router starts with the lowest level license by default.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-12
OL-23826-09
Chapter 2
Licensing
Return Materials Authorization License Process
Return Materials Authorization License Process
A Return Materials Authorization (RMA) license transfer enables moving all the licenses from the failed
device to the replacement device. Complete the following steps to transfer the license to an RMA
equipment:
Step 1
Go to the license portal https://tools.cisco.com/SWIFT/Licensing/LicenseAdminServlet/getProducts
Step 2
Enter the old (failed box) UDI and the new (replacement box) UDI.
The portal sends the new license file for transferring to the new device.
For more information, see the RMA License Transfer Between a Failed and a Working Device section
in the Cisco IOS Software Activation Conceptual Overview Guide.
Alternatively, you can use the Cisco License Manager (CLM) for the RMA license transfer. For more
information, see http://www.cisco.com/en/US/products/ps7138/products_user_guide_list.html.
Example: RMA Process
Router# license install ?
flash:
Install from flash: file system
tftp:
Install from tftp: file system
Router# copy tftp: flash:
Address or name of remote host []? 10.105.33.135
Source filename []? /tftpboot/arulpri/FHK10LLL021_20110530015634482.lic
Destination filename [FHK10LLL021_20110530015634482.lic]?
Accessing tftp://10.105.33.135//tftpboot/arulpri/FHK10LLL021_20110530015634482.lic...
Erase flash: before copying? [confirm]
Erasing the flash filesystem will remove all files! Continue? [confirm]
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee...
Erased
Erase of flash: complete
Loading /tftpboot/arulpri/FHK10LLL021_20110530015634482.lic from 10.105.33.135 (via
FastEthernet0/0): !
[OK - 1237 bytes]
Verifying checksum... OK (0x7403)
1237 bytes copied in 0.132 secs (9371 bytes/sec)
Router# license install flash:FHK10LLL021_20110530015634482.lic
Installing licenses from "flash:FHK10LLL021_20110530015634482.lic"
Extension licenses are being installed in the device with
UDI "ASR901:FHK10LLL021" for the following features:
Feature Name: AdvancedMetroIPAccess
PLEASE READ THE FOLLOWING TERMS CAREFULLY. INSTALLING THE LICENSE OR
LICENSE KEY PROVIDED FOR ANY CISCO PRODUCT FEATURE OR USING SUCH
PRODUCT FEATURE CONSTITUTES YOUR FULL ACCEPTANCE OF THE FOLLOWING
TERMS. YOU MUST NOT PROCEED FURTHER IF YOU ARE NOT WILLING TO BE BOUND
BY ALL THE TERMS SET FORTH HEREIN.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-13
Chapter 2
Licensing
Verifying the License
You hereby acknowledge and agree that the product feature license
is terminable and that the product feature enabled by such license
may be shut down or terminated by Cisco after expiration of the
applicable term of the license (e.g., 30-day trial period). Cisco
reserves the right to terminate or shut down any such product feature
electronically or by any other means available. While alerts or such
messages may be provided, it is your sole responsibility to monitor
your terminable usage of any product feature enabled by the license
and to ensure that your systems and networks are prepared for the shut
down of the product feature. You acknowledge and agree that Cisco will
not have any liability whatsoever for any damages, including, but not
limited to, direct, indirect, special, or consequential damages related
to any product feature being shutdown or terminated. By clicking the
"accept" button or typing "yes" you are indicating you have read and
agree to be bound by all the terms provided herein.
ACCEPT? (yes/[no]):
yes
Installing...Feature:AdvancedMetroIPAccess...Successful:Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were success to install
Verifying the License
To verify the new license, use the show license command.
Router# show license
Index 1 Feature: AdvancedMetroIPAccess
Period left: Lifetime
License Type: Permanent
License State: Active, In Use
License Priority: High
License Count: 1/1/0 (Active/In-use/Violation)
Index 2 Feature:…..
Period left: 0 minute
0
second
Where to Go Next
For additional information on Licensing, see the documentation listed in the “Related Documents”
section on page 2-15.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-14
OL-23826-09
Chapter 2
Licensing
Additional References
Additional References
Related Documents
Related Topic
Document Title
Cisco IOS commands
Cisco IOS Master Commands List, All Releases
ASR 901 Command Reference
Cisco ASR 901 Series Aggregation Services Router Command
Reference
Cisco IOS Interface and Hardware Component
Commands
Cisco IOS Interface and Hardware Component Command Reference
Cisco Software Licensing Concepts
Cisco IOS Software Activation Conceptual Overview
Cisco ASR 901Software Configuration Guide
Cisco ASR 901 Series Aggregation Services Router Software
Configuration Guide
Standards
Standard
Title
None
—
MIBs
MIB
MIBs Link
None
To locate and download MIBs for selected platforms, Cisco software
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
No new or modified RFCs are supported by this
feature, and support for existing RFCs has not been
modified by this feature.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-15
Chapter 2
Licensing
Additional References
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/index.html
The Cisco Support and Documentation website
provides online resources to download documentation,
software, and tools. Use these resources to install and
configure the software and to troubleshoot and resolve
technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support and
Documentation website requires a Cisco.com user ID
and password.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-16
OL-23826-09
Chapter 2
Licensing
Feature Information for Licensing
Feature Information for Licensing
Table 2-1 lists the release history for this feature and provides links to specific configuration
information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 2-1
Table 2-1 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for Licensing
Feature Name
Releases
Licensing
15.2(2)SNH1 The following sections provide information about this
feature:
1588BC Licensing
15.2(2)SNI
Feature Information
•
Licenses Supported on Cisco ASR 901 Router
•
License Types
•
Port or Interface Behavior
•
Generating the License
•
Installing the License
•
Changing the License
•
Return Materials Authorization License Process
The following sections provide information about this
feature:
•
Licenses Supported on Cisco ASR 901 Router
•
License Types
•
Port or Interface Behavior
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
2-17
Chapter 2
Licensing
Feature Information for Licensing
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
2-18
OL-23826-09
CH A P T E R
3
First-Time Configuration
This chapter describes the actions to take before turning on your router for the first time.
Contents
Note
•
Setup Mode, page 3-1
•
Verifying the Cisco IOS Software Version, page 3-5
•
Configuring the Hostname and Password, page 3-5
To understand the router interface numbering, see the Cisco ASR 901 Series Aggregation Services
Router Hardware Installation Guide.
Setup Mode
The setup mode guides you through creating a basic router configuration. If you prefer to configure the
router manually or to configure a module or interface that is not included in setup mode, go to Using the
Command-Line Interface, page 5-1 to familiarize yourself with the command-line interface (CLI).
Before Starting Your Router
Complete the following steps before you power on your router and begin using the setup mode:
Step 1
Set up the hardware and connect the console and network cables as described in the “Connecting Cables”
section of the Cisco ASR 901 Series Aggregation Services Router Hardware Installation Guide.
Step 2
Configure your PC terminal emulation program for 9600 baud, 8 data bits, no parity, and 1 stop bit.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
3-1
Chapter 3
First-Time Configuration
Setup Mode
Using Setup Mode
The setup command facility appears in your PC terminal emulation program window. To create a basic
configuration for your router, perform the following:
•
Complete the steps in the “Configuring Global Parameters” section on page 3-2
•
Complete the steps in the “Completing the Configuration” section on page 3-4
Note
If you made a mistake while using the setup command facility, exit the facility and run it again.
Press Ctrl-C, and type setup at the enable mode prompt (1900#).
Configuring Global Parameters
Complete the following steps to configure global parameters.
Step 1
Caution
Power on the router. Messages appear in the terminal emulation program window.
Do not press any keys on the keyboard until the messages stop. Any keys that you press during this time
are interpreted as the first command entered after the messages stop, which might cause the router to
power off and start over. Wait a few minutes. The messages stop automatically.
The messages look similar to the following:
System Bootstrap, Version 15.1(2r)SNG, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2011 by cisco Systems, Inc.
Compiled Tue 25-Oct-11 12:09 by tinhuang
P2020 platform with 524288 Kbytes of main memory
program load complete, entry point: 0x2000000, size: 0x1d29954
Self decompressing the image :
##########################################################################################
##########################################################################################
##########################################################################################
##########################################################################################
##########################################################################################
##########################################################################################
################################### [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
3-2
OL-23826-09
Chapter 3
First-Time Configuration
Setup Mode
Cisco IOS Software, 901 Software (ASR901-UNIVERSALK9-M), Version 15.1(2)SNG, RELEASE
SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Tue 25-Oct-11 13:13 by prod_rel_team
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Cisco ASR901-E (P2020) processor (revision 1.0) with 393216K/131072K bytes of memory.
Processor board ID CAT1529U01P
P2020 CPU at 792MHz, E500v2 core, 512KB L2 Cache
1 FastEthernet interface
12 Gigabit Ethernet interfaces
1 terminal line
256K bytes of non-volatile configuration memory.
98304K bytes of processor board System flash (Read/Write)
65536K bytes of processor board RAM Disk (Read/Write)
--- System Configuration Dialog --Would you like to enter the initial configuration dialog? [yes/no]:
Note
Step 2
The messages vary, depending on the Cisco IOS software image and interface modules in your
router. This section is for reference only, and output might not match the messages on your
console.
To begin the initial configuration dialog, enter yes when the following message appears:
Would you like to enter the initial configuration dialog? [yes/no]:yes
Would you like to enter basic management setup? [yes/no]: yes
Configuring global parameters:
Step 3
Enter a hostname for the router (this example uses 901-1).
Configuring global parameters:
Enter host name [Router]: 901-1
Step 4
Enter an enable secret password. This password is encrypted (more secure) and cannot be seen when
viewing the configuration.
The enable secret is a password used to protect access to
privileged EXEC and configuration modes. This password, after
entered, becomes encrypted in the configuration.
Enter enable secret: ciscoenable
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
3-3
Chapter 3
First-Time Configuration
Setup Mode
Note
Step 5
When you enter the enable secret password, the password is visible as you type it. Once you
enter the password, it becomes encrypted in the configuration.
Enter an enable password that is different from the enable secret password. This password is not
encrypted (less secure) and can be seen when viewing the configuration.
The enable password is used when you do not specify an
enable secret password, with some older software versions, and
some boot images.
Enter enable password: ciscoenable
Step 6
To prevent unauthenticated access to the router through ports other than the console port, enter the virtual
terminal password.
The virtual terminal password is used to protect
access to the router over a network interface.
Enter virtual terminal password: ciscoterminal
Step 7
Respond to the following prompts as appropriate for your network:
Configure System Management? [yes/no]: no
Configure SNMP Network Management? [yes]:
Community string [public]: public
Step 8
The summary of interfaces appears. This list varies, depending on the network modules installed in your
router.
Step 9
Specify the interface to be used to connect to the network management system.
Step 10
Configure the specified interface as prompted.
Completing the Configuration
When you have provided all of the information prompted for by the setup command facility, the
configuration appears. Messages similar to the following appear:
The following configuration command script was created:
!
hostname 901-1
enable secret 5 $1$5fH0$Z6Pr5EgtR5iNJ2nBg3i6y1 enable password ciscoenable line vty 0 98
password ciscoenablesnmp-server community public !
no ip routing
!
interface GigabitEthernet0/1
shutdown
!
end
Complete the following steps to configure the router:
Step 1
The setup command facility displays the following prompt.
[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
3-4
OL-23826-09
Chapter 3
First-Time Configuration
Verifying the Cisco IOS Software Version
Enter your selection [2]: 2
Building configuration...
[OK]
Use the enabled mode 'configure' command to modify this configuration.
Press RETURN to get started!
If you answer:
Step 2
•
0—The configuration information that you entered is not saved, and you return to the router enable
prompt. To return to the system configuration dialog, enter setup.
•
1—The configuration is not saved, and you return to the EXEC prompt.
When the messages stop displaying in your window, press Return to view the command line prompt.
The 901-1> prompt appears indicating that you are at the CLI and you completed a basic router
configuration.
Note
The basic configuration is not a complete configuration.
Verifying the Cisco IOS Software Version
To verify the version of Cisco IOS software, use the show version command. The show version
command displays the configuration of the system hardware, the software version, the names and
sources of the configuration files, and the boot images.
Configuring the Hostname and Password
First configure the hostname and set an encrypted password. Configuring a hostname allows you to
distinguish multiple Cisco routers from each other. Setting an encrypted password allows you to prevent
unauthorized configuration changes.
Note
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
Complete the following steps to configure a hostname and to set an encrypted password:
Step 1
Enter enable mode.
Router> enable
The Password prompt appears. Enter your password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 2
Enter global configuration mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
3-5
Chapter 3
First-Time Configuration
Configuring the Hostname and Password
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
When the prompt changes to Router(config), you have entered global configuration mode.
Router(config)#
Step 3
Change the name of the router to a meaningful name. Substitute your hostname for Router.
Router(config)# hostname Router
Router(config)#
Step 4
Enter an enable secret password. This password provides access to privileged EXEC mode. When you
type enable at the EXEC prompt ( Router>), you must enter the enable secret password to access
configuration mode. Enter your secret password.
Router(config)# enable secret secret password
Step 5
Exit back to global configuration mode.
Router(config)# exit
Verifying the Hostname and Password
Complete the following steps to verify that you have correctly configured the hostname and password:
Step 1
Enter the show config command:
Router# show config
Using 1888 out of 126968 bytes
!
version XX.X
.
.
.
!
hostname Router
!
enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/
.
.
.
Step 2
Check the hostname and encrypted password, which appear near the top of the command output.
Step 3
Exit global configuration mode and attempt to re-enter it using the new enable password:
Router# exit
.
.Router con0 is now available
Press RETURN to get started.
Router> enable
Password: password
Router#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
3-6
OL-23826-09
CH A P T E R
4
Managing and Monitoring Network
Management Features
This feature module describes how to monitor, manage and deploy a variety of network management
features, including Cisco Active Network Abstraction (ANA), Simple Network Management Protocol
(SNMP) and Cisco Networking Services (CNS). The CNS software agent on the ASR 901 can
communicate with a Cisco Configuration Engine to allow the ASR 901 to be deployed in the field
without having to pre-stage it for configuration or image upgrade. The Zero-touch deployment capability
enables the ASR 901 router to auto configure itself, download an updated image, connect to the network,
and start the operation as soon as it is cabled and powered up.
For more information about the Cisco Configuration Engine, see
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps4617/qa_c67_598467.html
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for Monitoring and Managing the ASR 901 Router” section on
page 4-18.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Network Management Features for the ASR 901, page 4-2
•
How to Configure Network Management Features on ASR 901, page 4-2
•
Where to Go Next, page 4-16
•
Additional References, page 4-16
•
Feature Information for Monitoring and Managing the ASR 901 Router, page 4-18
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-1
Chapter 4
Managing and Monitoring Network Management Features
Network Management Features for the ASR 901
Network Management Features for the ASR 901
The following sections describe the network management features available on the ASR 901.
•
Cisco Active Network Abstraction (ANA)
•
SNMP MIB Support
•
Cisco Networking Services (CNS)
Cisco Active Network Abstraction (ANA)
Cisco ANA is a powerful, next-generation network resource management solution designed with a fully
distributed OSS mediation platform that abstracts the network, its topology and its capabilities from the
physical elements. Its virtual nature provides customers with a strong and reliable platform for service
activation, service assurance and network management. For more information about ANA, see
http://www.cisco.com/en/US/products/ps6776/tsd_products_support_series_home.html.
SNMP MIB Support
To view the current MIBs that the ASR 901 supports, see http://www.cisco.com/go/mibs.
Cisco Networking Services (CNS)
Cisco Networking Services (CNS) is a collection of services that can provide remote configuration of
Cisco IOS networking devices, remote execution of command-line interface (CLI) commands, and
image downloads by communicating with a Cisco Configuration Engine application running on a server.
CNS enables the zero-touch deployment for the ASR 901 router by automatically downloading its
configuration and upgrading its image if needed.
Note
The ASR 901 only supports CNS over motherboard Ethernet interfaces.
For more information about CNS configuration, see Enabling Cisco Networking Services (CNS) and
Zero-Touch Deployment.
How to Configure Network Management Features on ASR 901
This section contains the following procedures:
•
Configuring SNMP Support
•
Configuring Remote Network Management
•
Enabling Cisco Networking Services (CNS) and Zero-Touch Deployment
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-2
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Configuring SNMP Support
Use the following to configure SNMP support for
Note
•
Setting up the community access
•
Establishing a message queue for each trap host
•
Enabling the router to send SNMP trap messages
•
Enabling SNMP trap messages for alarms
•
Enabling trap messages for a specific environment.
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
Complete the following steps to configure SNMP:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server community string [view view-name] [ro | rw] [number]
4.
snmp-server queue-length length
5.
snmp-server enable traps [notification-type] [notification-option]
6.
snmp-server enable traps ipran
7.
snmp-server enable traps envmon
8.
snmp-server host host-address [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}]
community-string [udp-port port] [notification-type]
9.
end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-3
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Step 3
Command
Purpose
Router(config)# snmp-server
community string [view view-name]
[ro | rw] [number]
Sets up the community access string to permit access to SNMP. The no
form of this command removes the specified community string.
Example:
Router(config)# snmp-server
community xxxxx RO
Step 4
Router(config)# snmp-server
queue-length length
•
string—Community string is the password to access the SNMP
protocol.
•
view view-name—(Optional) Previously defined view. The view
defines the objects available to the community.
•
ro—(Optional) Specifies read-only access. Authorized management
stations are able only to retrieve MIB objects.
•
rw—(Optional) Specifies read-write access. Authorized management
stations are able to both retrieve and modify MIB objects.
•
number—(Optional) Specifies an access list of IP addresses allowed
to use the community string to gain access to the SNMP agent. Values
range from 1 to 99.
Establishes the message queue length for each trap host.
•
length—Specifies the number of trap events that can be held before
the queue must be emptied.
Example:
Router(config)# snmp-server
queue-length 100
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-4
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Step 5
Command
Purpose
Router(config)# snmp-server enable
traps [notification-type]
[notification-option]
Enables the router to send SNMP traps messages. Use the no form of this
command to disable SNMP notifications.
•
Example:
Router(config)# snmp-server enable
traps snmp linkdown linkup
coldstart warmstart
notification-type—snmp [authentication]—Enables RFC 1157
SNMP notifications. Note that use of the authentication keyword
produces the same effect as not using the authentication keyword.
Both the snmp-server enable traps snmp and snmp-server enable
traps snmp authentication forms of this command globally enable
(or, if using the no form, disable) the following SNMP traps:
– authentication failure
– linkup
– linkdown
– coldstart
– warmstart
•
notification-option—(Optional) atm pvc [interval seconds]
[fail-interval seconds]—The optional interval seconds
keyword/argument combination specifies the minimum period
between successive traps, in the range from 1 to 3600. Generation of
PVC traps is dampened by the notification interval to prevent trap
storms. No traps are sent until the interval lapses. The default interval
is 30.
The optional fail-interval seconds keyword/argument combination
specifies the minimum period for storing the failed time stamp, in the
range from 0 to 3600. The default fail-interval is 0.
•
envmon [voltage | shutdown | supply | fan | temperature]—When
the envmon keyword is used, you can enable a specific environmental
notification type, or accept all notification types from the
environmental monitor system. If no option is specified, all
environmental notifications are enabled. The option can be one or
more of the following keywords: voltage, shutdown, supply, fan,
and temperature.
•
isdn [call-information | isdn u-interface]—When the isdn keyword
is used, you can specify the call-information keyword to enable an
SNMP ISDN call information notification for the ISDN MIB
subsystem, or you can specify the isdnu-interface keyword to enable
an SNMP ISDN U interface notification for the ISDN U interface
MIB subsystem.
•
repeater [health | reset]—When the repeater keyword is used, you
can specify a repeater option. If no option is specified, all repeater
notifications are enabled. The option can be one or more of the
following keywords:
– health—Enables IETF Repeater Hub MIB (RFC 1516) health
notification.
– reset—Enables IETF Repeater Hub MIB (RFC 1516) reset
notification.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-5
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Step 6
Command
Purpose
Router(config)# snmp-server enable
traps ipran
Enables SNMP trap messages for all IP-RAN notifications.
Note
Example:
Router(config)# snmp-server enable
traps ipran
Step 7
Router(config)# snmp-server enable
traps envmon
Besides enabling SNMP trap messages for all IP-RAN
notifications, you can also enable the messages for IP-RAN GSM
alarms, UMTS alarms, and general information about the
backhaul utilization.
Enables SNMP trap messages for a specific environment.
Example:
Router(config)# snmp-server enable
traps envmon
Step 8
Router(config)# snmp-server host
host-address [traps | informs]
[version {1 | 2c | 3 [auth | noauth
| priv]}] community-string
[udp-port port] [notification-type]
Example:
Router(config)# snmp-server host
10.20.30.40 version 2c
Specifies the recipient of an SNMP trap messages. To remove the
specified host, use the no form of this command.
•
host-address—Name or Internet address of the host (the targeted
recipient).
•
traps—Sends SNMP trap messages to this host. This is the default.
•
informs—(Optional) Sends SNMP informs to this host.
•
version—(Optional) Version of the SNMP used to send the traps.
Version 3 is the most secure model because allows packet encryption
with the priv keyword. If you use the version keyword, one of the
following must be specified:
– 1—SNMP version 1. This option is not available with informs.
– 2c—SNMP version 2C.
– 3—SNMP version 3. The following three optional keywords can
follow the version 3 keyword:
–auth (Optional). Enables Message Digest 5 (MD5) and Secure
Hash Algorithm (SHA) packet authentication
–noauth (Default). The no authentication-no privileges security
level is the default if the auth | noauth | priv] keyword choice is
not specified.
–priv (Optional). Enables Data Encryption Standard (DES)
packet encryption.
•
community-string—Password-like community string sent with the
notification operation. Though you can set this string using the
snmp-server host command by itself, we recommend you define this
string using the snmp-server community command before using the
snmp-server host command.
•
udp-port port—UDP port of the host. The default value is 162.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-6
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Command
Purpose
•
notification-type—(Optional) Type of notification to be sent to the
host. If no type is specified, all notifications are sent. The notification
type can be one or more of the following keywords:
– aaa_server—Enables SNMP AAA Server traps.
– atm—Enables SNMP ATM Server traps.
– ccme—Enables SNMP CCME traps.
– cnpd—Enables NBAR Protocol Discovery traps.
– config—Enables SNMP config traps.
– config-copy—Enables SNMP config-copy traps.
– cpu—Allow cpu related traps.
– dial—Enables SNMP dial control traps.
– dnis—Enables SNMP DNIS traps.
– ds0-busyout—Enables ds0-busyout traps.
– ds1—Enables SNMP DS1 traps.
– ds1-loopback—Enables ds1-loopback traps.
– ds3—Enables SNMP DS3 traps.
– dsp—Enables SNMP dsp traps.
– eigrp—Enables SNMP EIGRP traps.
– entity—Enables SNMP entity traps.
– envmon—Enables SNMP environmental monitor traps.
– flash—Enables SNMP FLASH notifications.
– frame-relay—Enables SNMP frame-relay traps.
– hsrp—Enables SNMP HSRP traps.
– icsudsu—Enables SNMP ICSUDSU traps.
– ipmulticast—Enables SNMP ipmulticast traps.
– ipran—Enables IP-RAN Backhaul traps.
– ipsla—Enables SNMP IP SLA traps.
– isdn—Enables SNMP isdn traps.
– 12tun—Enables SNMP L2 tunnel protocol traps.
– mpls—Enables SNMP MPLS traps.
– msdp—Enables SNMP MSDP traps.
– mvpn—Enables Multicast Virtual Private Networks traps.
– ospf—Enables OSPF traps.
– pim—Enables SNMP PIM traps.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-7
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Command
Purpose
– pppoe—Enables SNMP pppoe traps.
– pw—Enables SNMP PW traps.
– rsvp—Enables RSVP flow change traps.
– snmp—Enables SNMP traps.
– srst—Enables SNMP srst traps.
– syslog—Enables SNMP syslog traps.
– tty—Enables TCP connection traps.
– voice—Enables SNMP voice traps.
– vrrp—Enables SNMP vrrp traps.
– vtp—Enables SNMP VTP traps.
– xgcp—Enables XGCP protocol traps.
Step 9
Exits global configuration mode.
end
Example:
Router(config)# end
Configuring Remote Network Management
Complete the following steps to configure remote network management of ASR 901:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip host host-name ip-address
4.
interface loopback number
5.
ip-address ip-address subnet-mask
6.
end
7.
snmp-server host hostname [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}]
community-string [udp-port port] [notification-type]
8.
snmp-server community public ro
9.
snmp-server community private rw
10. snmp-server enable traps
11. snmp-server trap-source loopback number
12. end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-8
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
ip host host-name ip-address
Example:
Router(config)# ip host om-work 10.0.0.1
Step 4
Assigns a host name to each of the network management
workstations, where hostname is the name assigned to the
Operations and Maintenance (O&M) workstation and
ip_address is the address of the network management
workstation.
Creates a loopback interface for O&M.
interface loopback number
Example:
Router(config-if)# interface loopback 5005
Step 5
Configures the interval at which packets are sent to refresh
the MAC cache when HSRP is running.
ip-address ip-address subnet-mask
Example:
Router(config-if)# ip-address 10.10.12.10 23
Step 6
Exits interface configuration mode.
end
Example:
Router(config-if)# end
Step 7
snmp-server host hostname [traps | informs]
[version {1 | 2c | 3 [auth | noauth | priv]}]
community-string [udp-port port]
[notification-type]
Specifies the recipient of a Simple Network Management
Protocol (SNMP) notification operation.
The hostname is the name assigned to the Cisco Info Center
workstation with the ip host command in Step 3.
Example:
Router(config-if)# snmp-server host snmp1
version 3 auth
Step 8
Specifies the public SNMP community name.
snmp-server community public ro
Example:
Router(config-if)# snmp-server community
snmppubliccom RO
Step 9
Specifies the private SNMP community name.
snmp-server community private rw
Example:
Router(config-if)# snmp-server community
snmpprivatecom RW
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-9
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Step 10
Command or Action
Purpose
snmp-server enable traps
Enables the transmission of SNMP traps messages.
Example:
Router(config-if)# snmp-server enable traps
Step 11
snmp-server trap-source loopback number
Example:
Specifies the loopback interface from which SNMP traps
messages originate, where number is the number of the
loopback interface you configured for the O&M in Step 4.
Router(config-if)# snmp-server trap-source
loopback 5005
Step 12
Exits global configuration mode.
end
Example:
Router(config-if)# end
Enabling Cisco Networking Services (CNS) and Zero-Touch Deployment
To enable CNS and Zero-Touch deployment, you need the following servers:
Note
•
A DHCP server (standalone or enabled on the carrier edge router)
•
A TFTP server (standalone or enabled on the carrier edge router)
•
A server running the Cisco Configuration Engine (formerly known as the CNS-CE server)
The ASR 901 only supports CNS over motherboard Ethernet interfaces.
This section contains the following procedures:
•
Zero-Touch Deployment, page 4-10
•
Configuring a DHCP Server, page 4-12
•
Configuring a TFTP Server, page 4-13
•
Configuring the Cisco Configuration Engine, page 4-14
Zero-Touch Deployment
Zero-touch deployment feature gives the router the ability to retrieve its configuration file from the
remote server during initial router deployment with no end-user intervention.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-10
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Figure 4-1
Zero-touch Deployment
DHCP Server
L3 Network
TFTP Server
DHCP Helper
Configuration
Engine
303311
Cisco ASR 901 router
with no configurations
The following steps provide an overview of events that take place during ASR 901 zero-touch
deployment.
Step 1
Connect the Cisco ASR 901 without any configurations to an upstream router.
Step 2
The ASR 901 auto-senses the management vlan of the upstream router for IP connectivity by listening
to the traffic it receives on the connected interface.
Step 3
The ASR 901 sends DHCP discover messages using the discovered VLAN tag. If the upstream router is
not using a management VLAN, untagged DHCP discover messages are sent.
Step 4
The DHCP server responds with a DHCP offer.
Step 5
The ASR 901 sends a DHCP request message to the DHCP server. The DHCP server then sends the
DHCP ACK message.
Note
Step 6 and 7 are used only when Option 43 is not configured.
Step 6
The ASR 901 requests network-config file via TFTP.
Step 7
The TFTP server sends the ASR 901 a network-config file.
Step 8
The ASR 901 sends an HTTP request to the CNS-CE server.
Step 9
The CNS-CE server sends a configuration template to the ASR 901.
Step 10
Publish success event.
Image Download
The following events take place when a CNS-enabled ASR 901 downloads a new image:
Step 1
The CNS-CE server requests inventory (disk/flash info) from the ASR 901-DC.
Step 2
The ASR 901-DC sends an inventory.
Step 3
The CNS-CE server sends an image location.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-11
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Step 4
The ASR 901-DC sends a TFTP image request.
Step 5
The ASR 901-DC downloads an image from the TFTP server.
Step 6
Refresh the CNS-CE server to check whether the image download is complete.
Step 7
Associate the .inv template in the CNS-CE server. Based on the boot variable, the ASR 901 reboots with
the copied image.
Step 8
The CNS-CE server reboots the ASR 901-DC router.
Configuring a DHCP Server
The Cisco ASR 901 requires a DHCP server for zero-touch deployment. Complete the following steps
to configure a Cisco router as a DHCP server.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip dhcp excluded-address dhcp-server-ip-address
4.
ip dhcp excluded-address ip-address subnet-mask
5.
ip dhcp pool pool-name
6.
network ip-address subnet-mask
7.
default-router ip-address
8.
option 43 ascii string or option 150 ascii string
9.
end
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ip dhcp excluded-address dhcp-server-ip-address
Specifies to exclude IP address of the DHCP server.
Example:
Router# ip dhcp excluded-address 30.30.1.6
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-12
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
Step 4
Command or Action
Purpose
ip dhcp excluded-address ip-address subnet-mask
Assigns IP addresses with an exception of 30.30.1.6, which
is the IP address of the DHCP server.
Example:
Router# ip dhcp excluded-address 30.30.1.20
30.30.1.255
Step 5
Specifies the DHCP pool name.
ip dhcp pool pool-name
Example:
Router# ip dhcp pabudhcp2
Step 6
Specifies the IP address and subnet mask of the network.
network ip-address subnet-mask
Example:
Router# network 160.100.100.0 255.255.255.252
Step 7
Specifies the IP address of the default router.
default-router ip-address
Example:
Router# default-router 30.30.1.6
Step 8
option 43 ascii string
or
option 150 ip <TFTP-server-ip-address>
Specifies Option 43 and a string value that has the CNS
details, serial number of the hardware, and the code for CE
IP address or Option 150 and the IP address of the TFTP
server.
Example:
For more information on Option 43, see
http://www.cisco.com/en/US/docs/ios-xml/ios/cns/configu
ration/15-mt/cns-dhcp.html#GUID-CA88C33A-D81B-41
D3-A1F4-F276DA11C8B5. ASR 901 supports only few
letter code options mentioned in this link.
Router# option 43 ascii 3A1D;A3;B161.100.100.2
Step 9
Exits configuration mode.
end
Example:
Router(config-if)# end
Configuring a TFTP Server
You need to set up a TFTP server to provide a bootstrap configuration to the ASR 901 routers when they
boot using option 150.
Creating a Bootstrap Configuration
Create or download a file with the initial bootstrap configuration on the TFTP server. An example of the
configuration file is shown below:
hostname test-router
!
cns trusted-server all-agents 30.30.1.20
cns event 30.30.1.20 11011 keepalive 60 3
cns config initial 30.30.1.20 80
cns config partial 30.30.1.20 80
cns id hostname
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-13
Chapter 4
Managing and Monitoring Network Management Features
How to Configure Network Management Features on ASR 901
cns id hostname event
cns id hostname image
!
end
Enabling a TFTP Server on the Edge Router
The Cisco ASR 901 requires a TFTP server for zero-touch deployment while using option 150. The
TFTP server is typically implemented on the carrier edge router. You can use the following global
configuration commands to enable a TFTP server on the edge router that can send the initial
configuration to the Cisco ASR 901 router.
tftp-server sup-bootflash:network-confg
Once the Cisco ASR 901 boots with this configuration, it can connect to the CNS-CE server.
Configuring the Cisco Configuration Engine
The Cisco Configuration Engine (formerly known as the Cisco CNS Configuration Engine) allows you
to remotely manage configurations and IOS software images on Cisco devices including the
Cisco ASR 901.
Once the Cisco ASR 901 downloads the bootstrap configuration and connects to the Cisco Configuration
Engine server, you can use the server to download a full configuration to the router. You can also use the
CNS-CE server to complete any of the following tasks:
•
Manage configuration templates—The CNS-CE server can store and manage configuration
templates.
•
Download a new image—You can use the CNS-CE server to load a new IOS image on a
Cisco ASR 901 router.
•
Loading a new config—You can use the CNS-CE server to load a new configuration file on a
Cisco ASR 901 router.
•
Enable identification—You can use a unique CNS agent ID to verify the identity of a host device
prior to communication with the CNS-CE server.
•
Enable authentication—You can configure the CNS-CE server to require a unique password from
the ASR 901 router as part of any communication handshake.
•
Enable encryption—You can enable Secure Socket Layer (SSL) encryption for the HTTP sessions
between the CNS agent devices (Cisco ASR 901 routers) and the CNS-CE server.
For instructions about how to use the CNS-CE server, see the Cisco Configuration Engine Installation
& Configuration Guide at
http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home.html.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-14
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
Configuration Examples
Configuration Examples
This section provides the following configuration examples:
•
Example: Configuring SNMP Support
•
Example: Configuring Remote Network Management
•
Example: Configuring a DHCP Server
•
Example: Zero-touch Deployment
Example: Configuring SNMP Support
!
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
!
community xxxxx RO
queue-length 100
enable traps snmp linkdown linkup coldstart warmstart
enable traps ipran
enable traps envmonsnmp-server host 10.20.30.40 version 2c
Example: Configuring Remote Network Management
cns trusted-server all-agents 30.30.1.20
cns event 30.30.1.20 11011 keepalive 60 3
cns config initial 30.30.1.20 80
cns config partial 30.30.1.20 80
cns id hostname
cns id hostname event
cns id hostname image
cns exec 80
logging buffered 20000
!
end
Example: Configuring a DHCP Server
ip dhcp excluded-address 30.30.1.6
ip dhcp excluded-address 30.30.1.20 30.30.1.255
!
ip dhcp pool asrdhcp
network 30.30.1.0 255.255.255.0
default-router 30.30.1.6
Option 43 ascii 3A1D;A3;B161.100.100.2
!
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-15
Chapter 4
Managing and Monitoring Network Management Features
Where to Go Next
Example: Zero-touch Deployment
The following configuration example sets the Cisco ASR 901 to boot using configurations stored on a
CNS–CE server with the IP address 30.30.1.20.
Note
This section provides partial configurations intended to demonstrate a specific feature.
hostname 901
!
cns trusted-server all-agents 30.30.1.20
cns event 30.30.1.20 11011 keepalive 60 3
cns config initial 30.30.1.20 80
cns config partial 30.30.1.20 80
cns id hostname
cns id hostname event
cns id hostname image
!
end
Where to Go Next
For additional information on monitoring and managing the ASR 901 router, see the documentation
listed in the “Related Documents” section on page 4-16.
Additional References
Related Documents
Related Topic
Document Title
Cisco IOS commands
Cisco IOS Master Commands List, All Releases
ASR 901 Command Reference
Cisco ASR 901 Series Aggregation Services Router Command
Reference
Cisco IOS Interface and Hardware Component
Commands
Cisco IOS Interface and Hardware Component Command Reference
Standards
Standard
Title
None
—
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-16
OL-23826-09
Chapter 4
Managing and Monitoring Network Management Features
Additional References
MIBs
MIB
MIBs Link
None
To locate and download MIBs for selected platforms, Cisco software
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
No new or modified RFCs are supported by this
feature, and support for existing RFCs has not been
modified by this feature.
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/index.html
The Cisco Support and Documentation website
provides online resources to download documentation,
software, and tools. Use these resources to install and
configure the software and to troubleshoot and resolve
technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support and
Documentation website requires a Cisco.com user ID
and password.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
4-17
Chapter 4
Managing and Monitoring Network Management Features
Feature Information for Monitoring and Managing the ASR 901 Router
Feature Information for Monitoring and Managing the ASR 901
Router
Table 1 lists the release history for this feature and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 1
Table 1 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for Monitoring and Managing the ASR 901 Router
Feature Name
Releases
Monitoring and Managing the ASR 901 Router 15.2(2)SNI
Feature Information
The following sections provide information about this
feature:
•
Network Management Features for the ASR 901
•
How to Configure Network Management Features on
ASR 901
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
4-18
OL-23826-09
CH A P T E R
5
Using the Command-Line Interface
This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure the
Cisco ASR 901 router.
Contents
•
Understanding Command Modes, page 5-1
•
Understanding the Help System, page 5-3
•
Understanding Abbreviated Commands, page 5-4
•
Understanding no and default Forms of Commands, page 5-4
•
Understanding CLI Error Messages, page 5-4
•
Using Command History, page 5-5
•
Using Editing Features, page 5-6
•
Searching and Filtering Output of show and more Commands, page 5-9
•
Accessing the CLI, page 5-9
•
Saving Configuration Changes, page 5-10
Understanding Command Modes
The Cisco IOS user interface is divided into different modes. The commands depend on which mode you
are currently in. Enter a question mark (?) at the system prompt to obtain a list of commands for each
command mode.
When you start a session on the router, you begin in the user mode, often called user EXEC mode. Only
a limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC
commands are one-time commands, such as show commands, which show the current configuration
status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved
when the router reboots.
To gain access to all the commands, enter privileged EXEC mode. You need to enter a password to enter
privileged EXEC mode. From this mode, you can enter any privileged EXEC command or enter global
configuration mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
5-1
Chapter 5
Using the Command-Line Interface
Understanding Command Modes
Using the configuration modes (global, interface, and line), you can make changes to the running
configuration. When you save the configuration, these commands are stored and used for router reboots.
To access the various configuration modes, you must start at global configuration mode. From global
configuration mode, you can enter interface configuration mode and line configuration mode.
Table 5-1 describes the main command modes, how to access each one, the prompt you see in that mode,
and how to exit the mode. The examples in the table use the hostname Router.
For more detailed information on the command modes, see the command reference guide for this release.
Table 5-1
Command Mode Summary
Command Mode
Access Method
Router Prompt
Displayed
User EXEC
Log in.
Router>
Exit Method
About This Mode
Use the logout
command.
Use this mode to:
•
Change terminal
settings.
•
Perform basic tests.
•
Display system
information.
Privileged EXEC
From user EXEC
mode, use the enable
command.
Router#
To go to user EXEC
mode, use the disable,
exit, or logout
command.
Use this mode to verify
commands that you have
entered. Use a password
to protect access to this
mode.
Global configuration
From the privileged
EXEC mode, use the
configure terminal
command.
Router (config)#
To go to privileged
EXEC mode, use the
exit or end command,
or press Ctrl-Z.
Use this mode to
configure parameters
that apply to the entire
router.
Interface configuration
From the global
configuration mode,
use the interface
command (with a
specific interface).
Router (config-if)#
To go to global
configuration mode,
use the exit command.
Use this mode to
configure parameters for
the Ethernet ports.
To return directly to
privileged EXEC mode,
press Ctrl-Z.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
5-2
OL-23826-09
Chapter 5
Using the Command-Line Interface
Understanding the Help System
Table 5-1
Command Mode Summary
Command Mode
Access Method
VLAN configuration
While in global
configuration mode,
enter the vlan
vlan-id command.
Router Prompt
Displayed
Router(config-vlan)
#
Exit Method
About This Mode
To go to global
configuration mode,
enter the exit
command.
Use this mode to
configure VLAN
parameters.
To return to privileged
EXEC mode, press
Ctrl-Z or use the end
command.
Line configuration
While in global
configuration mode,
specify a line by
using the line vty or
line console
command.
Router(config-line)
#
To go to global
configuration mode,
use the exit command.
Use this mode to
configure parameters for
the terminal line.
To return to privileged
EXEC mode, press
Ctrl-Z or enter end.
Understanding the Help System
Enter a question mark (?) at the system prompt to display a list of commands available for each command
mode. You can also obtain a list of associated keywords and arguments for any command, as shown in
Table 5-2.
Table 5-2
Help Summary
Command
Purpose
help
Obtain a brief description of the help system in any command mode.
abbreviated-command-entry?
Obtain a list of commands that begin with a particular character string.
For example:
Router# di?
dir disable disconnect
abbreviated-command-entry<Tab>
Complete a partial command name.
For example:
Router# sh conf<tab>
Router# show configuration
?
List all commands available for a particular command mode.
For example:
Router> ?
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
5-3
Chapter 5
Using the Command-Line Interface
Understanding Abbreviated Commands
Table 5-2
Help Summary (continued)
Command
Purpose
command ?
List the associated keywords for a command.
For example:
Router> show ?
command keyword ?
List the associated arguments for a keyword.
For example:
Router(config)# cdp holdtime ?
<10-255> Length of time (in sec) that receiver must keep this packet
Understanding Abbreviated Commands
You need to enter only enough characters for the router to recognize the command as unique.
This example shows how to use the show configuration privileged EXEC command in an abbreviated
form:
Router# show conf
Understanding no and default Forms of Commands
Almost every configuration command also has a no form. In general, use the no form to disable a feature
or function, or reverse the action of a command. For example, the no shutdown interface configuration
command reverses the shutdown of an interface. Use the command without the keyword no to re-enable
a disabled feature or to enable a feature that is disabled by default.
Configuration commands can also have a default form. The default form of a command returns the
command setting to its default. Most commands are disabled by default, so the default form is the same
as the no form. However, some commands are enabled by default and have variables set to certain default
values. In these cases, the default command enables the command and sets variables to their default
values.
Understanding CLI Error Messages
Table 5-3 lists some error messages that you might encounter while using the CLI to configure your
router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
5-4
OL-23826-09
Chapter 5
Using the Command-Line Interface
Using Command History
Table 5-3
Common CLI Error Messages
Error Message
Meaning
How to Get Help
% Ambiguous command:
"show con"
You did not enter enough characters
for your router to recognize the
command.
Re-enter the command followed by a question mark (?)
with a space between the command and the question
mark.
The possible keywords that you can enter with the
command appear.
You did not enter all the keywords or Re-enter the command followed by a question mark (?)
values required by this command.
with a space between the command and the question
mark.
% Incomplete command.
The possible keywords that you can enter with the
command appear.
% Invalid input detected
at ‘^’ marker.
You entered the command
incorrectly. The caret (^) marks the
point of the error.
Enter a question mark (?) to display all the commands
that are available in this command mode.
The possible keywords that you can enter with the
command appear.
Using Command History
The software provides a history or record of commands that you entered. The command history feature
is particularly useful for recalling long or complex commands or entries, including access lists. You can
customize this feature to suit your needs as described in these sections:
•
Changing the Command History Buffer Size, page 5-5 (optional)
•
Recalling Commands, page 5-6 (optional)
•
Disabling the Command History Feature, page 5-6 (optional)
Changing the Command History Buffer Size
By default, the router records ten command lines in its history buffer. You can alter this number for a
current terminal session or for all sessions on a particular line. These procedures are optional.
Beginning in privileged EXEC mode, enter this command to change the number of command lines that
the router records during the current terminal session:
Router# terminal history
[size number-of-lines]
The range is from 0 to 256.
Beginning in line configuration mode, enter this command to configure the number of command lines
the router records for all sessions on a particular line:
Router(config-line)# history
[size number-of-lines]
The range is from 0 to 256.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
5-5
Chapter 5
Using the Command-Line Interface
Using Editing Features
Recalling Commands
To recall commands from the history buffer, perform one of the actions listed in Table 5-4. These actions
are optional.
Table 5-4
Recalling Commands
Action1
Result
Press Ctrl-P or the up arrow key.
Recall commands in the history buffer, beginning with the most recent command.
Repeat the key sequence to recall successively older commands.
Press Ctrl-N or the down arrow key.
Return to more recent commands in the history buffer after recalling commands
with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively
more recent commands.
show history
While in privileged EXEC mode, list the last several commands that you just
entered. The number of commands that appear is controlled by the setting of the
terminal history global configuration command and the history line configuration
command.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Disabling the Command History Feature
The command history feature is automatically enabled. You can disable it for the current terminal session
or for the command line. These procedures are optional.
To disable the feature during the current terminal session, use the terminal no history privileged EXEC
command.
To disable command history for the line, use the no history line configuration command.
Using Editing Features
This section contains the following the editing features that can help you manipulate the command line.
•
Enabling and Disabling Editing Features, page 5-6 (optional)
•
Editing Commands through Keystrokes, page 5-7 (optional)
•
Editing Command Lines that Wrap, page 5-8 (optional)
Enabling and Disabling Editing Features
Although the enhanced editing mode is automatically enabled, you can disable it, re-enable it, or
configure a specific line to have enhanced editing. These procedures are optional.
To globally disable enhanced editing mode, enter this command in line configuration mode:
Router (config-line)# no editing
To re-enable the enhanced editing mode for the current terminal session, enter this command in
privileged EXEC mode:
Router# terminal editing
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
5-6
OL-23826-09
Chapter 5
Using the Command-Line Interface
Using Editing Features
To reconfigure a specific line to have enhanced editing mode, enter this command in line configuration
mode:
Router(config-line)# editing
Editing Commands through Keystrokes
Table 5-5 shows the keystrokes that you need to edit command lines. These keystrokes are optional.
Table 5-5
Editing Commands through Keystrokes
Capability
Keystroke1
Move around the command line to
make changes or corrections.
Press Ctrl-B, or press the Move the cursor back one character.
left arrow key.
Purpose
Press Ctrl-F, or press the
right arrow key.
Move the cursor forward one character.
Press Ctrl-A.
Move the cursor to the beginning of the command line.
Press Ctrl-E.
Move the cursor to the end of the command line.
Press Esc B.
Move the cursor back one word.
Press Esc F.
Move the cursor forward one word.
Press Ctrl-T.
Transpose the character to the left of the cursor with the
character located at the cursor.
Recall commands from the buffer and Press Ctrl-Y.
paste them in the command line. The
router provides a buffer with the last
ten items that you deleted.
Press Esc Y.
Recall the most recent entry in the buffer.
Recall the next buffer entry.
The buffer contains only the last 10 items that you have
deleted or cut. If you press Esc Y more than ten times, you
cycle to the first buffer entry.
Delete entries if you make a mistake Press the Delete or
or change your mind.
Backspace key.
Capitalize or lower the case or
capitalize a set of letters.
Erase the character to the left of the cursor.
Press Ctrl-D.
Delete the character at the cursor.
Press Ctrl-K.
Delete all characters from the cursor to the end of the
command line.
Press Ctrl-U or Ctrl-X.
Delete all characters from the cursor to the beginning of
the command line.
Press Ctrl-W.
Delete the word to the left of the cursor.
Press Esc D.
Delete from the cursor to the end of the word.
Press Esc C.
Capitalize at the cursor.
Press Esc L.
Change the word at the cursor to lowercase.
Press Esc U.
Capitalize letters from the cursor to the end of the word.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
5-7
Chapter 5
Using the Command-Line Interface
Using Editing Features
Table 5-5
Editing Commands through Keystrokes (continued)
Keystroke1
Capability
Purpose
Designate a particular keystroke as
Press Ctrl-V or Esc Q.
an executable command, perhaps as a
shortcut.
Scroll down a line or screen on
displays that are longer than the
terminal screen can display.
Note
Press the Return key.
Scroll down one line.
Press the Space bar.
Scroll down one screen.
Press Ctrl-L or Ctrl-R.
Redisplay the current command line.
The More prompt is used for
any output that has more
lines than can be displayed
on the terminal screen,
including show command
output. You can use the
Return and Space bar
keystrokes whenever you see
the More prompt.
Redisplay the current command line
if the router suddenly sends a
message to your screen.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Editing Command Lines that Wrap
You can use a wraparound feature for commands that extend beyond a single line on the screen. When
the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the
first ten characters of the line, but you can scroll back and check the syntax at the beginning of the
command. The keystroke actions are optional.
To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You
can also press Ctrl-A to immediately move to the beginning of the line.
Note
The arrow keys function only on ANSI-compatible terminals such as VT100s.
In this example, the access-list global configuration command entry extends beyond one line. When the
cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar
sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line,
the line is again shifted ten spaces to the left.
Router(config)#
Router(config)#
Router(config)#
Router(config)#
access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1
$ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25
$t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq
$108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45
After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key
to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been
scrolled to the right:
Router(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
5-8
OL-23826-09
Chapter 5
Using the Command-Line Interface
Searching and Filtering Output of show and more Commands
The software assumes you have a terminal screen that is 80 columns wide. If you have a width other than
that, use the terminal width privileged EXEC command to set the width of your terminal.
Use line wrapping with the command history feature to recall and modify previous complex command
entries. For information about recalling previous command entries, see the “Editing Commands through
Keystrokes” section on page 5-7.
Searching and Filtering Output of show and more Commands
You can search and filter the output for show and more commands. This is useful when you need to sort
through large amounts of output or if you want to exclude output that you do not need to see. Using these
commands is optional.
To use this functionality, use show or more command followed by the pipe character (|), one of the
keywords begin, include, or exclude, and an expression that you want to search for or filter out:
command | {begin | include | exclude} regular-expression
Expressions are case sensitive. For example, if you use exclude output command, the lines that contain
output are not displayed, but the lines that contain Output appear.
This example shows how to include in the output display only lines where the expression protocol
appears:
Router# show interfaces | include protocol
Vlan1 is up, line protocol is up
Vlan10 is up, line protocol is down
GigabitEthernet0/1 is up, line protocol is down
GigabitEthernet0/2 is up, line protocol is up
Accessing the CLI
You can access the CLI through a console connection, through Telnet, or by using the browser.
Accessing the CLI through a Console Connection or through Telnet
Before accessing the CLI, you must connect a terminal or PC to the router console port and power on
the router as described in the hardware installation guide that shipped with your router.
If your router is already configured, you can access the CLI through a local console connection or
through a remote Telnet session, but your router must first be configured for this type of access..
You can use one of these methods to establish a connection with the router:
•
Connect the router console port to a management station or dial-up modem. For information about
connecting to the console port, see the router hardware installation guide.
•
Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management
station. The router must have network connectivity with the Telnet or SSH client, and the router must
have an enable secret password configured.
The router supports up to 16 simultaneous Telnet sessions. Changes made by one Telnet user are
reflected in all other Telnet sessions.
The router supports up to five simultaneous secure SSH sessions.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
5-9
Chapter 5
Using the Command-Line Interface
Saving Configuration Changes
After you connect through the console port, through a Telnet session or through an SSH session, the
user EXEC prompt appears on the management station.
Saving Configuration Changes
To save your configuration changes to NVRAM, so that the changes are not lost during a system reload
or power outage, enter the copy running-config startup-config command. For example:
Router# copy running-config startup-config
Router# write memory
Building configuration...
It might take a few minutes to save the configuration to NVRAM. After the configuration has been saved,
the following message appears:
[OK]
Router#
For additional information about using the Cisco IOS Release 15.1SNG, see the guides listed at:
http://www.cisco.com/en/US/products/ps11280/tsd_products_support_series_home.html
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
5-10
OL-23826-09
CH A P T E R
6
Software Upgrade
This chapter explains how to upgrade the Cisco IOS image installed on the Cisco ASR 901 router.
Contents
•
Selecting a Cisco IOS Image
•
Upgrading the Cisco IOS image
•
Auto Upgrading the MCU
•
Manually Upgrading the ROMMON
•
Auto Upgrade of ROMMON
Selecting a Cisco IOS Image
When you select the Cisco IOS image for upgrade, consider the following:
•
Memory requirement—The router should have sufficient disk or flash memory to store the Cisco
IOS. The router should also have sufficient memory (DRAM) to run the Cisco IOS. The
recommended logging buffer in DRAM ranges from 8 kilobytes to 64 kilobytes. If the router does
not have sufficient memory (DRAM), the router will have boot problems when it boots through the
new Cisco IOS.
•
Interfaces and modules support—You must ensure that the new Cisco IOS supports all the interfaces
and modules in the router.
•
Software feature support—You must ensure that the new Cisco IOS supports the features used with
the old Cisco IOS.
Upgrading the Cisco IOS image
Complete the following steps to upgrade the Cisco IOS image:
Step 1
Download the Cisco IOS software image to the TFTP server.
Download the Cisco IOS software image onto your workstation or PC from the Download Software Area
(registered customers only).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
6-1
Chapter 6
Software Upgrade
Upgrading the Cisco IOS image
Step 2
Identify the file system to copy the image.
The file system type ‘flash’ or ‘disk’ is used to store the Cisco IOS image. The show file system
command lists the file systems available on the router. The file system should have sufficient space to
store the Cisco IOS image. You can use the show file system or the dir file_system command in order
to find the free space.
Router# show file system
File Systems:
Size(b)
Free(b)
Type Flags
262144
240157
nvram
opaque
opaque
opaque
opaque
network
opaque
*
100401148
39104096
flash
67108860
67108860
flash
network
network
network
network
opaque
Step 3
Prefixes
rw
nvram:
rw
system:
rw
tmpsys:
rw
null:
ro
tar:
rw
tftp:
wo
syslog:
rw
flash:
rw
ramdisk:
rw
rcp:
rw
ftp:
rw
http:
rw
scp:
ro
cns:
Prepare for the upgrade.
You should consider these items before you upgrade the Cisco IOS:
Step 4
•
Store both the old Cisco IOS and the new Cisco IOS, if the router has sufficient memory. You can
boot the router in the ROMMON mode and boot the old Cisco IOS, in case of boot failure with new
Cisco IOS. This method saves time if you want to roll back the Cisco IOS.
•
Backup the configuration from the router because some of the Cisco IOS releases add default
configurations. This newly added configuration may conflict with your current configuration.
Compare the configuration of the router after the Cisco IOS upgrade with the configuration backed
up before the upgrade. If there are differences in the configuration, you must ensure they do not
affect your requirements.
Verify that the TFTP server has IP connectivity to the router.
The TFTP server must have a network connection to the router and must be able to ping the IP address
of the router targeted for a TFTP software upgrade. In order to achieve this connection, the router
interface and the TFTP server must have an IP address in the same range or a default gateway configured.
Check the IP address of the TFTP server in order to verify this configuration.
Step 5
Copy the IOS Image from the TFTP server.
Before you copy the image, ensure that you have started the TFTP server software on your PC, and that
you have the file name mentioned in the TFTP server root directory. Cisco recommends that you keep a
backup of the router and access server configuration before you upgrade. The upgrade does not affect
the configuration, which is stored in nonvolatile RAM [NVRAM]. However, this situation might happen
if the right steps are not followed properly.
Router# copy tftp: flash:
Address or name of remote host []? 10.105.33.135
Source filename []? asr901-universalk9-mz.151-2.SNG
Destination filename [asr901-universalk9-mz.151-2.SNG]?
Accessing tftp://10.105.33.135/asr901-universalk9-mz.151-2.SNG...
Erase flash: before copying? [confirm]n
Loading asr901-universalk9-mz.151-2.SNG from 10.105.33.135 (via FastEthernet0/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 30551884 bytes]
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
6-2
OL-23826-09
Chapter 6
Software Upgrade
Upgrading the Cisco IOS image
Verifying checksum... OK (0xC7E6)
30551884 bytes copied in 199.636 secs (153038 bytes/sec)
Router#
Step 6
Verify the Cisco IOS image in the file system.
Router# dir flash:
Directory of flash:/
1
-rw-
30551884
<no date>
asr901-universalk9-mz.151-2.SNG
100401148 bytes total (69849200 bytes free)
Router#
Router#
verify flash:asr901-universalk9-mz.151-2.SNG
File system hash verification successful.
Step 7
Verify the Configuration Register.
Use the show version command to check the config-register value. The value is displayed in the last line
of the show version output. It should be set to 0x2102.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# config-register 0x2102
Router(config)#^Z
Step 8
Verify the Boot Variable
The router tries to boot with the first file in the Flash. If the first file is not the Cisco IOS Software image,
you need to configure a boot system statement in order to boot the specified image. If there is only one
file in Flash and it is the Cisco IOS Software image, this step is not necessary.
Router#show run | inc boot
boot-start-marker
boot system flash asr901-universalk9-mz.151-2.SNG.fc1
boot-end-marker
Router#
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#no boot system
Router(config)#boot system flash asr901-universalk9-mz.151-2.SNG
Router(config)#end
Router#
Router#show run | inc boot
boot-start-marker
boot system flash asr901-universalk9-mz.151-2.SNG
boot-end-marker
Router#
Step 9
Save the configuration and reload the router.
Router# write memory
Router# reload
Proceed with reload? [confirm]
Jul 24 20:17:07.787: %SYS-5-RELOAD: Reload requested by console. Reload Reason:
Reload Command.
Step 10
Verify the Cisco IOS upgrade.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
6-3
Chapter 6
Software Upgrade
Auto Upgrading the MCU
After the reload is complete, the router should run the desired Cisco IOS Software image. Use the show
version command in order to verify the Cisco IOS software.
Router# show version
Cisco IOS Software, 901 Software (ASR901-UNIVERSALK9-M), Version 15.1(2)SNG, RELEASE
SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 27-Oct-11 15:52 by prod_rel_team
ROM: System Bootstrap, Version 15.1(2r)SNG, RELEASE SOFTWARE (fc1)
ASR901 uptime is 4 minutes
System returned to ROM by reload at 13:11:07 UTC Wed Apr 19 2000
System image file is "tftp://10.105.33.135/rajuvenk/asr901-universalk9-mz.151-2.SNG.bin"
Last reload type: Normal Reload
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
License Level: AdvancedMetroIPAccess
License Type: Permanent
Next reload license Level: AdvancedMetroIPAccess
Cisco ASR901-E (P2020) processor (revision 1.0) with 393216K/131072K bytes of memory.
Processor board ID CAT1529U01P
P2020 CPU at 792MHz, E500v2 core, 512KB L2 Cache
1 FastEthernet interface
12 Gigabit Ethernet interfaces
1 terminal line
256K bytes of non-volatile configuration memory.
98304K bytes of processor board System flash (Read/Write)
65536K bytes of processor board RAM Disk (Read/Write)
Configuration register is 0x2102
Auto Upgrading the MCU
Upgradable MCU is bundled with the IOS image. You can upgrade the MCU using one of the following
ways:
•
MCU Auto upgrade can be enabled or disabled by setting the ROMMON variable
AUTO_UPGRADE_ROMMON to TRUE or FALSE:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
6-4
OL-23826-09
Chapter 6
Software Upgrade
Manually Upgrading the ROMMON
– From the ROMMON:
rommon> AUTO_UPGRADE_MCU=TRUE | FALSE
– From theIOS:
Router# upgrade mcu preference [enable | disable]
Once the MCU is upgraded, the router is not reloaded. Subsequent reload versions are compared; if
the versions are same, then the MCU is not upgraded.
•
If the AUTO_UPGRADE_ROMMON variable is set to FALSE, then the MCU can be upgraded as
follows:
Router# upgrade mcu file flash:image.hex
Manually Upgrading the ROMMON
Complete the following steps to manually upgrade the router ROMMON:
Step 1
Load the IOS image.
Step 2
Copy the upgradable ROMMON file ASR901_RM2.srec, to the flash memory.
Step 3
Upgrade the ROMMON using the following command:
Router# upgrade rom-monitor file flash:ASR901_RM2.srec
The router reloads and comes up with upgradable ROMMON.
Step 4
Check the status of the currently running ROMMON using any one of the following commands:
•
From the ROMMON:
rommon> showmon
•
From the IOS:
router> show rom-monitor
Note
While upgrade is in progress, if something goes wrong like power-off or power cycler removed,
or if the erase program is not done properly, you can reset the board. It falls back to the read-only
rommon.
After the ROMMON upgrade, if you need to fall back to either the read-only ROMMON, or the upgrade
ROMMON, use any one of the following commands:
•
From the IOS:
Router# upgrade rom-monitor preference readonly | upgrade
•
From the ROMMON:
rommon> rommon-pref readonly
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
6-5
Chapter 6
Software Upgrade
Auto Upgrade of ROMMON
Auto Upgrade of ROMMON
Upgradable rommon is bundled with the IOS image. You can do an auto upgrade of the ROMMON using
one of the following ways:
•
Rommon Auto upgrade can be enabled or disabled with by setting the rommon variable
AUTO_UPGRADE_ROMMON to TRUE or FALSE using the following commands:
– From the ROMMON:
rommon> AUTO_UPGRADE_ROMMON=TRUE | FALSE
– From the IOS:
Router# upgrade rom-monitor preference autoupgrade enable | disable
By default, the upgrade variable is set to be TRUE.
Once the ROMMON is upgraded, the IOS falls back to the ROMMON. Subsequent reload versions
are compared; if the version is the same, then the ROMMON will not be upgraded.
•
If the AUTO_UPGRADE_ROMMON variable is set to FALSE, use the following command in IOS,
to upgrade:
Router# upgrade rom-monitor internal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
6-6
OL-23826-09
CH A P T E R
7
Configuring Gigabit Ethernet Interfaces
This chapter explains how to configure the Gigabit Ethernet (GE) interface on the Cisco ASR 901 router.
Contents
•
Configuring the Interface, page 7-1
•
Setting the Speed and Duplex Mode, page 7-2
•
Enabling the Interface, page 7-3
•
Modifying MTU Size on the Interface, page 7-3
•
MAC Flap Control, page 7-5
•
Configuring a Combo Port, page 7-6
Configuring the Interface
To configure the GE interface, complete the following steps:
Note
Step 1
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
Command
Purpose
enable
Enters enable mode.
Example:
Router> enable
Router#
Step 2
configure terminal
Enters configuration mode.
Example:
Router# configure terminal
Router(config)#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
7-1
Chapter 7
Configuring Gigabit Ethernet Interfaces
Setting the Speed and Duplex Mode
Step 3
Command
Purpose
interface gigabitethernet slot/port
Specifies the port adapter type and the location of the interface to be
configured. The slot is always 0 and the port is the number of the port.
Example:
Router(config)# interface
gigabitethernet 0/1
Step 4
Enables Cisco Discovery Protocol on the router, use the cdp enable
command.
cdp enable
Example:
Router(config-if)# cdp enable
Step 5
end
Exits configuration mode.
Example:
Router(config-if)# end
Router#
Setting the Speed and Duplex Mode
The Gigabit Ethernet ports of the Cisco ASR 901 router can run in full or half- duplex mode—100 Mbps
or 1000 Mbps (1 Gbps). The Cisco ASR 901 router has an autonegotiation feature that allows the router
to negotiate the speed and duplex mode with the corresponding interface at the other end of the
connection.
Autonegotiation is the default setting for the speed and transmission mode.
When you configure an interface speed and duplex mode, follow these guidelines:
Note
Note
•
If both ends of the line support autonegotiation, use the default autonegotiation settings.
•
When autonegotiation is turned on, it autonegotiates both speed and the duplex mode.
•
If one interface supports autonegotiation, and the interface at the other end does not, configure the
duplex mode and speed on both interfaces. If you use the autonegotiation setting on the supported
side, the duplex mode setting is set at half-duplex.
•
For Giga Ethernet ports with copper cable, autonegotiation should always be enabled for operating
at 1000Mbps speed.
•
Auto-negotiation must be enabled for 1000M full duplex Gigabit Ethernet devices; otherwise
behavior is unpredictable.
Speed and duplex can be configured only on the following interfaces:
•
Copper gigabitethernet interfaces (0/0-3)
•
Combo gigabitethernet interface (0/4-7), when the media type is configured as RJ-45
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
7-2
OL-23826-09
Chapter 7
Configuring Gigabit Ethernet Interfaces
Enabling the Interface
To configure speed and duplex operation, complete these steps in the interface configuration mode:
Step 1
Command
Purpose
duplex [auto | half | full]
Specify the duplex operation.
Example:
Router(config-if)# duplex auto
Step 2
Specify the speed.
speed [auto | 1000 | 100]
Example:
Router(config-if)# speed auto
Enabling the Interface
To enable the interface, complete these steps:
Note
Step 1
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
Command
Purpose
interface gigabitethernet slot/port
Specify the port adapter type and the location of the interface to be
configured. The slot is always 0 and the port is the number of the port.
Example:
Router(config)# interface
gigabitethernet 0/1
Step 2
Enable the gigabit Ethernet interface using the no shutdown command.
no shutdown
Modifying MTU Size on the Interface
Complete the following steps to modify the MTU size on Gigabit Ethernet interface:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface gigabitethernet slot/port
4.
mtu bytes
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
7-3
Chapter 7
Configuring Gigabit Ethernet Interfaces
Modifying MTU Size on the Interface
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface gigabitethernet slot/port
Selects a Gigabit Ethernet interface and enters
interface configuration mode.
•
Example:
slot/port—Specifies the slot and port number.
Router(config)# interface gigabitethernet 0/1
Step 4
Configures the MTU size for Gigabit Ethernet
interface.
mtu bytes
•
Example:
Router(config-if)# mtu 6000
bytes—The range is from 1500 to 9216. The
default is 9216.
Note
To set the MTU size to its default value, use
the no mtu or default mtu command.
Verifying the MTU Size
To verify the MTU size, use the show interface gigabitethernet and show interface mtu commands.
Router# show interface gigabitethernet 0/1
GigabitEthernet0/1 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 4055.398d.bd05 (bia 4055.398d.bd05)
MTU 6000 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters 21:01:41
Input queue: 0/200/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
Router# show interface mtu
Port
Name
MTU
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
7-4
OL-23826-09
Chapter 7
Configuring Gigabit Ethernet Interfaces
MAC Flap Control
Gi0/0
Gi0/1
Gi0/2
Gi0/3
Gi0/4
Gi0/5
Gi0/6
Gi0/7
Gi0/8
Gi0/9
Gi0/10
Gi0/11
9216
6000
3000
9216
9216
9216
9216
9216
9216
9216
9216
9216
MAC Flap Control
A MAC flap occurs when a switch receives packets from two different interfaces, with the same source
MAC address. This happens when wrong configurations such as loops are introduced in networks. MAC
flapping can cause CPU hogs and software induced crashes, if preventive action is not taken.
The two main aspects of MAC flap control feature are:
•
Identification of MAC Flapping—Identified when MAC movement counter threshold is hit at
specified time intervals.
•
Preventive Action—Err-Disabling is done in one of the ports that has MAC flapping.
This feature is disabled by default and can be enabled or disabled through the CLI. You can
configure the maximum number of MAC movements that are allowed in a specified time interval,
beyond which the MAC movement is termed as flapping.
Once the port is err-disabled, it can be administratively brought up using the shut and no shut
commands.
Restrictions and Limitations
•
If MAC learning is done in tens of thousands, the CPU may slow down. This feature does not address
the slow down or CPU hog due to MAC learning.
•
When the router is learning tens of thousands of MACs, and there are a couple of genuine MAC
movements (not due to a loop), they are not tagged as MAC flapping since these are valid MAC
movements.
•
Average MAC Movement issue
For example, let us assume that MAC movement counter is configured for a maximum of 5 MAC
movements in 10 seconds.
If 2000 MACs have contributed for 4 MAC movements each in 10 seconds, the total number of AC
movements will be 8000. Since the individual MAC threshold is not hit in this case, the router does
not take any preventive action. However, this condition may not really occur in practice.
Configuring MAC FLap Control
Complete the following steps to configure MAC Flap control:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
7-5
Chapter 7
Configuring Gigabit Ethernet Interfaces
Configuring a Combo Port
Step 1
Command
Purpose
configure terminal
Enter global configuration mode.
Example:
Router# configure terminal
Step 2
mac-flap-ctrl on per-mac <mac-movement>
<time-interval>
Example:
Router(config)# mac-flap-ctrl on per-mac
20 10
Enable MAC flap control.
•
mac-movement—Maximum number of MAC movements
that are allowed in the specified time.
•
time-interval—Time interval that can elapse before the MAC
movements are tagged as flapping.
If values are not specified for the above parameters, the default
values are taken by the router. The default values for the counters
are five and ten; that is five movements in ten seconds.
The no form of the command disables this feature.
Configuring a Combo Port
A combo port is considered as a single interface with dual front ends (an RJ-45 connector and an SFP
module connector). The dual front ends of a combo port are non-redundant interfaces; the
Cisco ASR 901 router activates only one connector of the pair. Combo ports can be configured as copper
ports or small form-factor pluggable (SFP) module ports.
By default, the Cisco ASR 901 router selects the RJ-45 connector. However, you can use the media-type
command to manually select the media type. When the media type is auto-select, the router gives
preference to SFP module if both copper and fiber-optic signals are simultaneously detected.
Restrictions
•
When you configure SFP or RJ-45 media type, the non-configured media type is disabled even if
there is a connector installed on the interface and no connector on the configured media type.
•
When the media type is auto-select, the Cisco ASR 901 router configures both types with auto
negotiation of speed and duplex.
•
When the media type is auto-select, you cannot use 100M SFPs.
•
When the media type is auto-select, you cannot use the speed and duplex commands.
•
When the media type is auto-select, the Cisco ASR 901 router uses the following criteria to select
the type:
– If only one connector is installed, that interface is active and remains active until the media is
removed or the router is reloaded.
– If both media are installed in the combo port, the router gives preference to the SFP module
interface.
– If both media are installed in the combo port, when the SFP module interface is inactive, the
RJ-45 connector is selected. When the SFP module interface recovers and becomes active, the
RJ-45 connector is disabled and the router gives preference to the SFP module interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
7-6
OL-23826-09
Chapter 7
Configuring Gigabit Ethernet Interfaces
Configuring a Combo Port
– If both media are installed in the combo port, and the router is reloaded or the port is disabled
and then re-enabled through the shutdown and the no shutdown interface configuration
commands, the router gives preference to the SFP module interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface gigabitethernet slot/port
4.
media-type {auto-select | rj45 | sfp}
5.
end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
interface gigabitethernet slot/port
Selects a Gigabit Ethernet interface and enters
interface configuration mode.
•
Example:
slot/port—Specifies the slot and port number.
Router(config)# interface gigabitethernet 0/1
Step 4
media-type {auto-select | rj45 | sfp}
Configures the media type.
•
auto-select—Specifies dynamic selection of the
physical connection.
•
rj45—Specifies an RJ-45 physical connection.
•
sfp—Specifies an SFP physical connection for
fiber media.
Example:
Router(config-if)# media-type rj45
Step 5
end
Exits interface configuration mode and enters
privileged EXEC mode.
Example:
Router(config-if)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
7-7
Chapter 7
Configuring Gigabit Ethernet Interfaces
Configuring a Combo Port
Verifying the Media Type
To verify the media type, use the show interface gigabitethernet command.
Following is a sample output when the media type is RJ-45:
Router# show interface gigabitethernet 0/1
GigabitEthernet0/1 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 4055.398d.bd05 (bia 4055.398d.bd05)
MTU 9216 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
Following is a sample output when fiber-optic is selected as the physical connection:
Router# show interface gigabitethernet 0/7
GigabitEthernet0/7 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 4055.398d.bd0b (bia 4055.398d.bd0b)
MTU 9216 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is SX
output flow-control is unsupported, input flow-control is unsupported
Following is a sample output when the media type is auto-select and the interface is down:
Router# show interface gigabitethernet 0/7
GigabitEthernet0/7 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is 0000.0000.0000 (bia 0000.0000.0000)
MTU 9216 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is unknown
output flow-control is unsupported, input flow-control is unsupported
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
7-8
OL-23826-09
CH A P T E R
8
Configuring Ethernet Virtual Connections
Metro-Ethernet Forum (MEF) defines Ethernet Virtual Connection (EVC) as an association between two
or more user network interfaces that identifies a point-to-point or multipoint-to-multipoint path within
the service provider network. An EVC is a conceptual service pipe within the service provider network.
A bridge domain is a local broadcast domain that is VLAN-ID-agnostic. An ethernet flow point (EFP)
service instance is a logical interface that connects a bridge domain to a physical port or to an
EtherChannel group in a router.
An EVC broadcast domain is determined by a bridge domain and the EFPs connected to it. You can
connect multiple EFPs to the same bridge domain on the same physical interface, and each EFP can have
its own matching criteria and rewrite operation. An incoming frame is matched against EFP matching
criteria on the interface, learned on the matching EFP, and forwarded to one or more EFPs in the bridge
domain. If there are no matching EFPs, the frame is dropped.
You can use EFPs to configure VLAN translation. For example, if there are two EFPs egressing the same
interface, each EFP can have a different VLAN rewrite operation, which is more flexible than the
traditional switchport VLAN translation model.
Note
Cisco ASR 901 router does not support switch port configuration.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for Configuring Ethernet Virtual Connections” section on page 8-33.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Supported EVC Features, page 8-2
•
Understanding EVC Features, page 8-3
•
Configuring EFPs, page 8-7
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-1
Chapter 8
Configuring Ethernet Virtual Connections
Supported EVC Features
•
Configuration Examples of Supported Features, page 8-10
•
Configuration Examples of Unsupported Features, page 8-12
•
How to Configure EVC Default Encapsulation, page 8-13
•
Configuring Other Features on EFPs, page 8-16
•
Monitoring EVC, page 8-28
•
Sample Configuration with Switchport to EVC Mapping, page 8-29
Supported EVC Features
This section contains the following supported EVC features:
•
Service instance—create, delete, and modify EFP service instances on Ethernet interfaces.
•
Encapsulation—map traffic to EFPs based on:
– 802.1Q VLANs (a single VLAN or a list or range of VLANs)
– 802.1Q tunneling (QinQ) VLANs (a single outer VLAN and a list or range of inner VLANs)
– Double-tagged frames mapped to EVC based on C-tags (wildcard S-Tags)
– Cisco QinQ ethertype for S-tags
•
Bridge domains—configure EFPs as members of a bridge domain (up to 64 EFPs per bridge
domain).
•
DHCP client—retrieves the host information from the DHCP server.
•
Rewrite (VLAN translation)
– Pop symmetric only—the supported rewrite configuration implies egress pushing (adding a tag)
1.
pop 1 removes the outermost tag
2.
pop symmetric adds a tag on egress for a push operation
– QinQ with rewrite
– Ingress rewrite is not supported
•
EVC forwarding
•
MAC address learning and aging
•
EVCs on EtherChannels
•
Split horizon
•
EVC MAC address security
•
MSTP (MST on EVC bridge domain)
•
EFP statistics (packets and bytes)
•
QoS aware EVC/EFP per service instance
•
Pop 2 configuration supports layer 2 and layer 3 operations. Additionally, it supports
GigabitEthernet and port channel interfaces.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-2
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Understanding EVC Features
These Layer 2 port-based features can run with EVC configured on the port:
•
LACP
•
CDP
•
MSTP
Understanding EVC Features
This section contains the following topics:
•
Ethernet Virtual Connections, page 8-3
•
Service Instances and EFPs, page 8-3
•
Encapsulation, page 8-4
•
Bridge Domains, page 8-5
•
DHCP Client on Switch Virtual Interface
•
Configuring Other Features on EFPs, page 8-16
•
Rewrite Operations, page 8-6
Ethernet Virtual Connections
Use the ethernet evc evc-id global configuration command to create an EVC. The evc-id or name is a
text string from 1 to 100 bytes. Using this command moves the device into service configuration mode
(config-srv) where you configure all parameters that are common to an EVC.
In this mode you can use these commands:
•
default—Sets a command to its defaults
•
exit—Exits EVC configuration mode
•
no— Negates a command or sets its defaults
•
oam—Specifies the OAM Protocol
•
uni—Configures a count UNI under EVC
Service Instances and EFPs
Configuring a service instance on a Layer 2 port or EtherChannel creates an EFP on which you configure
EVC features. Each service instance has a unique number per interface, but you can use the same number
on different interfaces because service instances on different ports are not related.
If you defined an EVC by using the ethernet evc evc-id global configuration command, you can
associate the EVC with the service instance (optional). There is no default behavior for a service
instance. You can configure a service instance only on trunk ports with no allowed VLANs. Any other
configuration is not allowed. After you have configured a service instance on an interface, switchport
commands are not allowed on the interface. You can also configure a service instance on an
EtherChannel group.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-3
Chapter 8
Configuring Ethernet Virtual Connections
Understanding EVC Features
Use the service instance number ethernet [name] interface configuration command to create an EFP on
a Layer 2 interface or EtherChannel and to enter service instance configuration mode. You use service
instance configuration mode to configure all management and control date plane attributes and
parameters that apply to the service instance on a per-interface basis.
•
The service instance number is the EFP identifier, an integer from 1 to 8000.
•
The optional ethernet name is the name of a previously configured EVC. You do not need to enter
an EVC name, but you must enter ethernet. Different EFPs can share the same name when they
correspond to the same EVC. EFPs are tied to a global EVC through the common name.
When you enter service instance configuration mode, you can configure these options:
•
default—Sets a command to its defaults
•
description—Adds a service instance specific description
•
encapsulation—Configures Ethernet frame match criteria
•
ethernet—Configures Ethernet-lmi parameters
•
exit— Exits from service instance configuration mode
•
no—Negates a command or sets its defaults
•
service-policy —Attaches a policy-map to an EFP
•
shutdown—Takes the service instance out of service
Enter the [no] shutdown service-instance configuration mode to shut down or bring up a service
instance.
On a Layer 2 port with no service instance configured, multiple switchport commands are available
(access, backup, block, host, mode, and trunk). When one or more service instances are configured on
a Layer 2 port, no switchport commands are accepted on that interface.
Encapsulation
Encapsulation defines the matching criteria that maps a VLAN, a range of VLANs, Ethertype, or a
combination of these to a service instance. Configure encapsulation in the service instance configuration
mode. You must configure one encapsulation command per EFP (service instance).
Use the encapsulation command in service-instance configuration mode to set the encapsulation
criteria. Different types of encapsulations are dot1q, dot1ad, and untagged. Valid Ethertypes (type) are
IPv4, PPPOE-All, PPPOE-Discover, and PPPOE-Session.
Encapsulation classification options also include:
•
outer tag VLAN
•
inner tag VLAN
•
payload ethertype—any ethertype tag after the VLAN tag
After you enter an encapsulation method, these keyword options are available in service instance
configuration mode:
•
bridge-domain—Configures a bridge domain
•
rewrite—Configures Ethernet rewrite criteria
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-4
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Understanding EVC Features
Table 8-1
Supported Encapsulation Types
Command
Description
encapsulation dot1q vlan-id
[,vlan-id[-vlan-id]]
Defines the matching criteria to be used to map 802.1Q frames ingress on an interface to the
appropriate EFP. The options are a single VLAN, a range of VLANs, or lists of VLANs or
VLAN ranges. VLAN IDs are 1 to 4094.
•
Enter a single VLAN ID for an exact match of the outermost tag.
•
Enter a VLAN range for a ranged outermost match.
Note
encapsulation dot1q vlan-id
second-dot1q vlan-id
[,vlan-id[-vlan-id]]
VLAN IDs 4093, 4094, and 4095 are reserved for internal usage.
Double-tagged 802.1Q encapsulation. Matching criteria to be used to map QinQ frames
ingress on an interface to the appropriate EFP. The outer tag is unique and the inner tag can
be a single VLAN, a range of VLANs or lists of VLANs or VLAN ranges.
•
Enter a single VLAN ID in each instance for an exact match of the outermost two tags.
•
Enter a VLAN range for second-dot1q for an exact outermost tag and a ranged second
tag.
encapsulation dot1ad
vlan-id[,vlan-id[-vlain-id]]
[native]
Defines the matching criteria to be used in order to map single-tagged 802.1ad frames ingress
on an interface to the appropriate service instance. The criteria for this command are: single
VLAN, range of VLANs and lists of the previous two.
encapsulation untagged
Matching criteria to be used to map untagged (native) Ethernet frames entering an interface
to the appropriate EFP.
Only one EFP per port can have untagged encapsulation. However, a port that hosts EFP
matching untagged traffic can also host other EFPs that match tagged frames.
encapsulation default
Configures default encapsulation.
If a packet entering or leaving a port does not match any of the encapsulations on that port, the packet
is dropped, resulting in filtering on both ingress and egress. The encapsulation must match the packet on
the wire to determine filtering criteria. On the wire refers to packets ingressing the router before any
rewrites and to packets egressing the router after all rewrites.
Note
The router does not allow overlapping encapsulation configurations. See the “Configuration Examples
of Unsupported Features” section on page 8-12.
Bridge Domains
A service instance must be attached to a bridge domain. Flooding and communication behavior of a
bridge domain is similar to that of a VLAN domain. Bridge-domain membership is determined by which
service instances have joined it (based on encapsulation criteria), while VLAN domain membership is
determined by the VLAN tag in the packet.
Note
You must configure encapsulation before you can configure the bridge domain.
Use the bridge-domain bridge-id service-instance command in the configuration mode to bind the EFP
to a bridge domain instance. The bridge-id is the identifier for the bridge domain instance, a number
ranging from 1 to 4094.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-5
Chapter 8
Configuring Ethernet Virtual Connections
Understanding EVC Features
DHCP Client on Switch Virtual Interface
The DHCP client retrieves the host information from the DHCP server and configures the SVI interface
of the Cisco ASR 901 router. If the DHCP server is unable to provide the requested configuration
parameters from its database to the DHCP client, it forwards the request to one or more secondary DHCP
servers defined by the network administrator. DHCP helps you to dynamically assign reusable IP
addresses to clients.
Hosts are connected to secondary VLANs, and the DHCP server assigns them IP addresses from the
block of addresses assigned to the primary VLAN. When new devices are added, the DHCP server
assigns them the next available address from a large pool of subnet addresses. In Cisco ASR 901 router,
the DHCP client is supported only on SVI interfaces and for IPv4 addresses.
Split-Horizon
The split-horizon feature allows service instances in a bridge domain to join groups. Service instances
in the same bridge domain and split-horizon group cannot forward data between each other, but can
forward data between other service instances that are in the same bridge domain, but not in the same
split-horizon group.
Service instances do not have to be in a split-horizon group. If a service instance does not belong to a
group, it can send and receive from all ports within the bridge domain. A service instance cannot join
more than one split-horizon group.
Use the bridge-domain bridge-id split-horizon group group_id service-instance command in the
configuration mode to configure a split-horizon group. The group_id is a number from 0 to31. All
members of the bridge-domain configured with the same group_id are part of the same split-horizon
group. EFPs that are not configured with an explicit group_id do not belong to any group.
You can configure no more than 12 service instances per bridge domain. When a bridge domain contains
a service instance that is part of a split-horizon group, this decreases the number of service instances
allowed to be configured in that split-horizon group. The router supports up to 32 split-horizon groups
plus the default (no group).
If a service instance joins split-horizon group, it can have no more than 12 members in split horizon
group in the same bridge domain. We recommend that you add split horizon groups in numerical order
to maximize the number of service instances that can belong to a group.
Rewrite Operations
Use the rewrite command to modify packet VLAN tags. You can also use this command to emulate
traditional 802.1Q tagging, where packets enter a router on the native VLAN and VLAN tagging
properties are added on egress. You can also use the rewrite command to facilitate VLAN translation
and QinQ.
Use the rewrite ingress tag pop 1symmetric service-instance configuration mode command to specify
the encapsulation adjustment to be performed on the frame ingress to the EFP. Entering pop 1 pops
(removes) the outermost tag.
Note
The symmetric keyword is required to complete the rewrite configuration.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-6
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring EFPs
When you enter the symmetric keyword, the egress counterpart performs the inverse action and pushes
(adds) the encapsulation VLAN. You can use the symmetric keyword only with ingress rewrites and
only when single VLANs are configured in encapsulation. If you configure a list of VLANs or a VLAN
range or encapsulation default, the symmetric keyword is not accepted for rewrite operations.
The Cisco ASR 901router supports only the following rewrite command.
rewrite ingress tag pop 1 symmetric
rewrite ingress tag pop 2 symmetric
The router does not support rewrite commands for ingress push and translate in this release. However,
you can use the rewrite ingress tag pop symmetric command to achieve translation. Possible
translation combinations are 1-to-1, 1-to-2, and 2-to-1.
The Cisco ASR 901 Series Aggregation Services Router does not support egress rewrite operations
beyond the second VLAN that a packet carries into a router. See the “Configuring Other Features on
EFPs” section on page 8-16.
Configuring EFPs
This section contains the following topics:
•
Default EVC Configuration, page 8-7
•
Configuration Guidelines, page 8-7
•
Creating Service Instances, page 8-8
•
Configuration Examples of Supported Features, page 8-10
•
Configuration Examples of Unsupported Features, page 8-12
Default EVC Configuration
Cisco IOS Release 15.3(2)S introduces support for EVC default encapsulation on the Cisco ASR 901
routers. This feature matches and forwards all the ingress traffic on the port. The default service instance
on a port is configured using the encapsulation default command.
All traffic coming to the interface with default encapsulation is matched and forwarded. This includes
untagged, single tagged, and double tagged traffic. For example, when an untagged EFP is configured,
all the traffic except the untagged traffic matches the default EFP.
All Layer 2 features are supported on the default EVC.
Note
Before Cisco IOS Release 15.3(2)S, EFPs or service instances or bridge domains were not configured.
Configuration Guidelines
•
You can configure up to 4000 bridge domains on the Cisco ASR 901 router.
•
The number of bridge domains that you can configure depends on the license that is installed:
– The metro services licenses support 4000 bridge domains.
– The metro IP services licenses support 4000 bridge domains.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-7
Chapter 8
Configuring Ethernet Virtual Connections
Configuring EFPs
•
All licenses support a maximum of 16 EFPs per bridge domain.
•
You must configure encapsulation on a service instance before configuring bridge domain.
•
When you configure a bridge domain between 1 and 4094, IGMP snooping is automatically disabled
on the VLAN.
•
ISL trunk encapsulation is not supported.
•
When an EFP encapsulation is the default (matching or allowing all ingress frames), you cannot
configure any other encapsulation on an EFP on the same port and bridge-domain as the default
encapsulation. There can be only one default encapsulation per port.
•
The router does not support overlapping configurations on the same interface and same bridge
domain. If you have configured a VLAN range encapsulation, or encapsulation default on service
instance 1, you cannot configure any other encapsulations that also match previous encapsulations
in the same interface and bridge domain. See the “Configuration Examples of Unsupported
Features” section on page 8-12.
•
Default encapsulation is supported only on the physical interface and port channel interface.
•
The default encapsulation command is accepted only for untagged EFP.
•
If default encapsulation EVC is configured on the interface, only the untagged encapsulation is
accepted and all other encapsulation commands are rejected.
•
Default EFP under xconnect and untagged EFP under bridge-domain on the same interface is not
supported.
•
The rewrite command on encapsulation default EVC is rejected.
•
Supports encapsulation only on bridge-domain and Xconnect.
•
Supports only untagged EFPs on the port with default encapsulation.
•
Egress filtering is not supported. All unlearned traffic ingresses on the default encapsulation
interface is flooded to other interfaces that are part of the same bridge-domain.
•
Layer 3 routing is not supported. Layer 2 VPN is supported on the default encapsulation EFP.
•
QinQ configuration for Layer3 is not possible with pop1 rewrite. However pop2 configured routed
QinQ is supported.
•
Default xconnect MTU is 9216.
•
For interoperability with other routers for an xconnect session, ensure that the MTU on both PE
routers is same before the xconnect session is established.
•
MPLS is not supported over routed QinQ.
•
VLAN IDs 4093, 4094, and 4095 are reserved for internal usage.
Creating Service Instances
Complete the following steps to create an EFP service instance:
Note
The dot1q and dot1ad range configuration is not supported on the port channel interface on
Cisco IOS Release 15.2(2)SNI.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-8
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring EFPs
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Specify the interface, and enter interface configuration mode.
Valid interfaces are physical ports.
Step 3
service instance number ethernet [name]
Configure an EFP (service instance) and enter service instance
configuration) mode.
Step 4
Step 5
encapsulation {dot1q | dot1ad | untagged |
default}
bridge-domain bridge-id [split-horizon group
group-id]
•
The number is the EFP identifier, an integer from 1 to 4000.
•
(Optional) ethernet name is the name of a previously
configured EVC. You do not need to use an EVC name in a
service instance.
Configure encapsulation type for the service instance.
•
dot1q—Configure 802.1Q encapsulation. See Table 8-1 for
details about options for this keyword.
•
dot1ad—Configure 802.1ad encapsulation.
•
untagged—Map to untagged VLANs. Only one EFP per port
can have untagged encapsulation.
•
default—Configures default encapsulation.
Configure the bridge domain ID. The range is from 1 to 4094.
•
Note
Step 6
rewrite ingress tag pop 1 symmetric
(Optional) split-horizon group group-id—Configure a
split-horizon group. The group ID is from 0 to 31. EFPs in the
same bridge domain and split-horizon group cannot forward
traffic between each other, but can forward traffic between
other EFPs in the same bridge domain but not in the same
split-horizon group.
You must configure encapsulation before the
bridge-domain keyword is available.
(Optional) Specify that encapsulation modification to occur on
packets at ingress.
•
pop 1—Pop (remove) the outermost tag.
•
symmetric—Configure the packet to undergo the reverse of
the ingress action at egress. If a tag is popped at ingress, it is
pushed (added) at egress.
Note
Although the symmetric keyword appears to be optional,
you must enter it for rewrite to function correctly.
Step 7
end
Return to privileged EXEC mode.
Step 8
show ethernet service instance
Verify your entries.
show bridge-domain [n | split-horizon]
Step 9
copy running-config startup-config
Note
(Optional) Save your entries in the configuration file.
Use the no forms of the commands to remove the service instance, encapsulation type, or bridge domain
or to disable the rewrite operation.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-9
Chapter 8
Configuring Ethernet Virtual Connections
Configuration Examples of Supported Features
Configuration Examples of Supported Features
•
Example: Configuring a Service Instance
•
Example: Encapsulation Using a VLAN Range
•
Example: Two Service Instances Joining the Same Bridge Domain
•
Example: Bridge Domains and VLAN Encapsulation
•
Example: Rewrite
•
Example: Split Horizon
Example: Configuring a Service Instance
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 22 Ethernet [name]
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 10
Example: Encapsulation Using a VLAN Range
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 22 Ethernet
(config-if-srv)# encapsulation dot1q 22-44
(config-if-srv)# bridge-domain 10
Example: Two Service Instances Joining the Same Bridge Domain
In this example, service instance 1 on interfaces Gigabit Ethernet 0/1 and 0/2 can bridge between each
other.
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 10
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 10
Example: Bridge Domains and VLAN Encapsulation
Unlike VLANs, the bridge-domain number does not need to match the VLAN encapsulation number.
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 4000
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 4000
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-10
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuration Examples of Supported Features
However, when encapsulations do not match in the same bridge domain, traffic cannot be forwarded. In
this example, the service instances on Gigabit Ethernet 0/1 and 0/2 can not forward between each other,
since the encapsulations don’t match (filtering criteria). However, you can use the rewrite command to
allow communication between these two.
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 4000
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 99
(config-if-srv)# bridge-domain 4000
Example: Rewrite
In this example, a packet that matches the encapsulation will have one tag removed (popped off). The
symmetric keyword allows the reverse direction to have the inverse action: a packet that egresses out
this service instance will have the encapsulation (VLAN 10) added (pushed on).
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# rewrite ingress tag pop 1 symmetric
(config-if-srv)# bridge-domain 4000
Example: Split Horizon
In this example, service instances 1 and 2 cannot forward and receive packets from each other. Service
instance 3 can forward traffic to any service instance in bridge domain 4000 since it has not joined any
split-horizon groups.
Router
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# rewrite ingress pop 1 symmetric
(config-if-srv)# bridge-domain 4000 split-horizon group 1
(config-if-srv)# exit
Router
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 2 Ethernet
(config-if-srv)# encapsulation dot1q 99
(config-if-srv)# rewrite ingress pop 1 symmetric
(config-if-srv)# bridge-domain 4000 split-horizon group 1
(config-if-srv)# exit
Router
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/3
(config-if)# service instance 3 Ethernet
(config-if-srv)# encapsulation dot1q 99
(config-if-srv)# rewrite ingress pop 1 symmetric
(config-if-srv)# bridge-domain 4000
(config-if-srv)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-11
Chapter 8
Configuring Ethernet Virtual Connections
Configuration Examples of Unsupported Features
Configuration Examples of Unsupported Features
•
Example: Filtering
•
Example: Overlapping Encapsulation
Example: Filtering
In EVC switching, egress filtering is performed before the frame is sent on the egress EFP. Egress
filtering ensures that when a frame is sent, it conforms to the matching criteria of the service instance
applied on the ingress direction. EFP does not require egress filtering if the number of pops is the same
as the number of VLANs specified in the encapsulation command.
Note
Specifying the cos keyword in the encapsulation command is relevant only in the ingress direction. For
egress filtering, cos is ignored.
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 20
(config-if-srv)# bridge-domain 19
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 2 Ethernet
(config-if-srv)# encapsulation dot1q 30
(config-if-srv)# bridge-domain 19
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/3
(config-if)# service instance 3 Ethernet
(config-if-srv)# encapsulation dot1q 10 second-dot1q 20
(config-if-srv)# rewrite ingress pop 1 symmetric
(config-if-srv)# bridge-domain 19
If a packet with VLAN tag 10 or 20 is received on Gigabit Ethernet 0/3, the ingress logical port would
be service instance 3. For the frame to be forwarded on a service instance, the egress frame must match
the encapsulation defined on that service instance after the rewrite is done. Service instance 1 checks for
outermost VLAN 20; service instance 2 checks for VLAN 30. In this example, the frame with VLAN
tags 10 and 20 can be sent to service instance 1 but not to service instance 2.
Example: Overlapping Encapsulation
The router does not allow overlapping encapsulation. Overlapping encapsulation configuration occurs
when two EFPs are configured on the same port and the same bridge domain and the set of
encapsulations on one EFP is a subset of the encapsulations on the other EFP.
Service instance 2 configuration is rejected because service instance 1 encapsulation dot1q any is
superset of service instance 2 encapsulation dot1q 10.
Router
Router
Router
Router
Router
Router
Router
Router
(config)# interface gigabitethernet 0/1
(config-if)# service instance 1 ethernet
(config-if-srv)# encapsulation dot1q any
(config-if-srv)# bridge-domain 10
(config-if-srv)# exit
(config-if)# service instance 2 ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# bridge-domain 10
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-12
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
How to Configure EVC Default Encapsulation
How to Configure EVC Default Encapsulation
•
Configuring EVC Default Encapsulation with Bridge-Domain
•
Configuring EVC Default Encapsulation with Xconnect
•
Verifying EVC Default Encapsulation with Bridge-Domain
•
Verifying EVC Default Encapsulation with Xconnect
•
Configuration Examples for EVC Default Encapsulation
Configuring EVC Default Encapsulation with Bridge-Domain
Complete the following steps to configure EVC default encapsulation for a bridge-domain.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
service instance instance-id ethernet
5.
encapsulation default
6.
bridge-domain bridge-id
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Specifies an interface type and number, and enters interface
configuration mode.
interface type number
Example:
Router(config)# interface GigabitEthernet0/4
Step 4
service instance instance-id ethernet
Creates a service instance on an interface and defines the
matching criteria.
•
Example:
Router(config-if)# service instance 10 ethernet
instance-id—Integer that uniquely identifies a service
instance on an interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-13
Chapter 8
Configuring Ethernet Virtual Connections
How to Configure EVC Default Encapsulation
Step 5
Command or Action
Purpose
encapsulation default
Configures the default service instance.
Example:
Router(config-if-srv)# encapsulation default
Step 6
Binds the service instance to a bridge domain instance using
an identifier.
bridge-domain bridge-id
Example:
Router(config-if-srv)# bridge-domain 15
Configuring EVC Default Encapsulation with Xconnect
Complete the following steps to configure EVC default encapsulation for xconnect.
Note
When default encapsulation is configured on xconnect, the Cisco ASR 901 router does not support
untagged encapsulation on the bridge-domain of the same interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
service instance instance-id ethernet
5.
encapsulation default
6.
xconnect peer-ip-address vc-id encapsulation mpls
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-14
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
How to Configure EVC Default Encapsulation
Step 3
Command or Action
Purpose
interface type number
Specifies an interface type and number, and enters interface
configuration mode.
Example:
Router(config)# interface
GigabitEthernet0/4
Step 4
service instance instance-id ethernet
Creates a service instance on an interface and defines the
matching criteria.
•
Example:
Router(config-if)# service instance 10
ethernet
Step 5
instance-id—Integer that uniquely identifies a service
instance on an interface.
Configures the default service instance.
encapsulation default
Example:
Router(config-if)# encapsulation default
Step 6
Binds an attachment circuit to a pseudowire, and to configure an
Any Transport over MPLS (AToM) static pseudowire.
xconnect peer-ip-address vc-id
encapsulation mpls
•
peer-ip-address—IP address of the remote provider edge
(PE) peer. The remote router ID can be any IP address, as
long as it is reachable.
•
vc-id—The 32-bit identifier of the virtual circuit (VC)
between the PE routers.
•
encapsulation—Specifies the tunneling method to
encapsulate the data in the pseudowire.
•
mpls—Specifies MPLS as the tunneling method.
Example:
Router(config-if-srv)# xconnect 1.1.1.1 100
encapsulation mpls
Verifying EVC Default Encapsulation with Bridge-Domain
To verify the configuration of EVC default encapsulation with bridge-domain, use the show command
shown below.
Router# show running-config interface gigabitEthernet 0/9
Building configuration...
Current configuration : 210 bytes
!
interface GigabitEthernet0/9
no ip address
negotiation auto
service instance 1 ethernet
encapsulation default
bridge-domain 99
!
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-15
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Verifying EVC Default Encapsulation with Xconnect
To verify the configuration of EVC default encapsulation with xconnect, use the show command shown
below.
Router# show running-config interface gigabitEthernet 0/4
Building configuration...
Current configuration : 181 bytes
!
interface GigabitEthernet0/4
no ip address
negotiation auto
no keepalive
service instance 1 ethernet
encapsulation default
xconnect 2.2.2.2 100 encapsulation mpls
!
end
Configuration Examples for EVC Default Encapsulation
•
Example: Configuring EVC Default Encapsulation with Bridge-Domain
•
Example: Configuring EVC Default Encapsulation with Xconnect
Example: Configuring EVC Default Encapsulation with Bridge-Domain
!
interface GigabitEthernet0/9
service instance 1 ethernet
encapsulation default
bridge-domain 99
!
Example: Configuring EVC Default Encapsulation with Xconnect
!
interface GigabitEthernet0/4
service instance 10 ethernet
encapsulation default
xconnect 1.1.1.1 100 encapsulation mpls
!
Configuring Other Features on EFPs
This section contains the following topics:
•
EFPs and EtherChannels, page 8-17
•
MAC Address Forwarding, Learning and Aging on EFPs, page 8-17
•
Configuring IEEE 802.1Q Tunneling using EFPs, page 8-20
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-16
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
•
Bridge Domain Routing, page 8-24
•
How to Configure DHCP Client on SVI, page 8-25
•
EFPs and MSTP, page 8-27
EFPs and EtherChannels
You can configure EFP service instances on EtherChannel port channels, but EtherChannels are not
supported on ports configured with service instances. Load-balancing on port channels is based on the
MAC address or IP address of the traffic flow on the EtherChannel interface.
Configuration Example
This example configures a service instance on an EtherChannel port channel. Configuration on the ports
in the port channel are independent from the service instance configuration.
Router
Router
Router
Router
(config)# interface port-channel 4
(config-if)# service instance 2 ethernet
(config-if-srv)# encapsulation dot1q 20
(config-if-srv)# bridge-domain 2
MAC Address Forwarding, Learning and Aging on EFPs
•
Layer 2 forwarding is based on the bridge domain ID and the destination MAC address. The frame
is forwarded to an EFP if the binding between the bridge domain, destination MAC address, and EFP
is known. Otherwise, the frame is flooded to all the EFPs or ports in the bridge domain.
•
MAC address learning is based on bridge domain ID, source MAC addresses, and logical port
number. MAC addresses are managed per bridge domain when the incoming packet is examined and
matched against the EFPs configured on the interface. If there is no EFP configured, the bridge
domain ID equal to the outer-most VLAN tag is used as forwarding and learning look-up key. For
native VLAN frames, the bridge domain equal to the access VLAN configured in the interface is
used.
If there is no matching entry in the Layer 2 forwarding table for the ingress frame, the frame is
flooded to all the ports within the bridge domain. Flooding within the bridge domain occurs for
unknown unicast, and broadcast.
•
Dynamic addresses are addresses learned from the source MAC address when the frame enters the
router. All unknown source MAC addresses are sent to the CPU along with ingress logical port
number and bridge domain ID for learning. Once the MAC address is learned, the subsequent frame
with the destination MAC address is forwarded to the learned port. When a MAC address moves to
a different port, the Layer 2 forwarding entry is updated with the corresponding port.
•
Dynamic addresses are aged out if there is no frame from the host with the MAC address. If the
aged-out frame is received by the router, it is flooded to the EFPs in the bridge domain and the Layer
2 forwarding entry is created again. The default for aging dynamic addresses is 5 minutes.
You can configure dynamic address aging time by entering the mac address-table aging time [0 |
10-1000000]. The range is in seconds. An aging time of 0 means that the address aging is disabled.
•
MAC address movement is detected when the host router moves from one port to another. If a host
moves to another port or EFP, the learning lookup for the installed entry fails because the ingress
logical port number does not match and a new learning cache entry is created. The detection of MAC
address movement is disabled for static MAC addresses where the forwarding behavior is configured
by the user.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-17
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Disabling MAC Address Learning on an Interface or Bridge Domain
By default, MAC address learning is enabled on all interfaces and bridge domains or VLANs on the
router. You can control MAC address learning on an interface or VLAN to manage the available MAC
address table space by controlling which interfaces or VLANs can learn MAC addresses. When you
disable MAC address learning for a BD/VLAN or interface, the router that receives packet from any
source on the BD, VLAN or interface, the addresses are not learned. Since addresses are not learned, all
IP packets floods into the Layer 2 domain.
Prerequisites
You can disable MAC address learning on a single VLAN ID from 2 to 4092 (for example, no
mac-address-table learning vlan 10). If the MAC address learning is disabled for a VLAN or interface,
the already learnt addresses for that VLAN or interface are immediately removed from the MAC address
table. However, you cannot disable MAC learning for the reserved 4093, 4094, and 4095 VLAN IDs. If
the VLAN ID that you enter is a reserved VLAN, the switch generates an error message and rejects the
command.
•
We recommend that you disable MAC address learning only in VLANs with two ports. If you
disable MAC address learning on a VLAN with more than two ports, every packet entering the
switch is flooded in that VLAN domain.
•
You cannot disable MAC address learning on a VLAN that is used internally by the router. VLAN
ID 1 is used internally by the router. If the VLAN ID that you enter is an internal VLAN, the switch
generates an error message and rejects the command.
Restrictions
Complete the following steps to disable MAC address learning on a VLAN:
SUMMARY STEPS
1.
configure terminal
2.
no mac-address-table learning {vlan vlan-id | interface interface slot/port}
3.
end
4.
copy running-config startup-config
DETAILED STEPS
Step 1
Command or Action
Purpose
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 2
no mac-address-table learning {vlan vlan-id |
interface type slot/port}
Disable MAC address learning on an interface or on a
specified VLAN.
Example:
vlan vlan-id—Specifies the VLAN ID which ranges from 2
to 4094. It cannot be an internal VLAN or reserved VLAN.
Router(config)# no mac-address-table learning
vlan 10
interface type slot/port—Specifies the location of the
interface and its type.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-18
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Command or Action
Purpose
Step 3
end
Return to privileged EXEC mode.
Step 4
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To reenable MAC address learning, use the mac-address-table learning global configuration command.
The command causes the configuration to appear in the show running-config privileged EXEC
command display.
Configuration Examples
This example shows how to disable MAC address learning on VLAN 10:
Router(config)# no mac-address-table learning vlan 10
This example shows how to disable MAC-address learning for all modules on a specific routed interface:
Router(config)# no mac-address-table learning interface GigabitEthernet 0/5
Router(config)#
This example shows how to disable MAC address learning for port-channel interface:
Router(config)# no mac-address-table learning interface port-channel 1
Verification
The following are the examples of the outputs using the show commands.
Router# show mac-address-table
Mac Address Table
------------------------------------------Vlan
Mac Address
Type
Ports
------------------------20
2222.2222.2222
STATIC
Gi0/2
10
0000.0700.0a00
DYNAMIC
Gi0/9
10
0000.0700.0b00
DYNAMIC
Gi0/1
Total Mac Addresses for this criterion: 3
In the above example, the show mac-address-table command displays both the dynamically and
statically learned addresses.
Following is an example for show mac-address-table dynamic command which displays only
dynamically learned addresses.
Router# show mac-address-table dynamic
Mac Address Table
------------------------------------------Vlan
Mac Address
Type
Ports
------------------------10
0000.0700.0a00
DYNAMIC
Gi0/9
10
0000.0700.0b00
DYNAMIC
Gi0/1
Total Mac Addresses for this criterion: 2
Following is an example for show mac-address-table vlan 10 command which displays only the
addresses learned on a particular VLAN/BD.
Router# show mac-address-table vlan 10
Mac Address Table
-------------------------------------------
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-19
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Vlan
Mac Address
Type
Ports
------------------------10
0000.0700.0a00
DYNAMIC
Gi0/9
10
0000.0700.0b00
DYNAMIC
Gi0/1
Total Mac Addresses for this criterion: 2
Following is an example for show mac-address-table interface g0/9 command which displays only the
addresses learned on a particular VLAN/BD interface.
Router# show mac-address-table interface 0/9
Mac Address Table
------------------------------------------Vlan
Mac Address
Type
Ports
------------------------10
0000.0700.0a00
DYNAMIC
Gi0/9
Total Mac Addresses for this criterion: 1
Following is an example for show mac-address-table interface port-channel command which displays
only the addresses learned on a particular port-channel interface.
Router# show mac-address-table interface port-channel 1
Mac Address Table
------------------------------------------Vlan
Mac Address
Type
Ports
------------------------10
0000.0700.0b00
DYNAMIC
Po1
Total Mac Addresses for this criterion: 1
Configuring IEEE 802.1Q Tunneling using EFPs
Tunneling is a feature used by service providers whose networks carry traffic of multiple customers and
who are required to maintain the VLAN and Layer 2 protocol configurations of each customer without
impacting the traffic of other customers. The Cisco ASR 901 router uses EFPs to support QinQ and
Layer 2 protocol tunneling.
This section contains the following topics:
•
802.1Q Tunneling (QinQ), page 8-20
•
Routed QinQ, page 8-23
802.1Q Tunneling (QinQ)
Service provider customers often have specific requirements for VLAN IDs and the number of VLANs
to be supported. The VLAN ranges required by different customers in the same service-provider network
might overlap, and traffic of customers through the infrastructure might be mixed. Assigning a unique
range of VLAN IDs to each customer would restrict customer configurations and could easily exceed the
VLAN limit (4096) of the 802.1Q specification.
Using the EVCs, service providers can encapsulate packets that enter the service-provider network with
multiple customer VLAN IDs (C-VLANs) and a single 0x8100 Ethertype VLAN tag with a service
provider VLAN (S-VLAN). Within the service provider network, packets are switched based on the
S-VLAN. When the packets egress the service provider network onto the customer network, the
S-VLAN tag is decapsulated and the original customer packet is restored.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-20
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Figure 8-1 shows the tag structures of the double-tagged packets.
Original (Normal), 802.1Q, and Double-Tagged Ethernet Packet Formats
Source
address
Destination
Length/
address
EtherType
DA
SA
Len/Etype
DA
SA
Etype
DA
SA
Etype
Frame Check
Sequence
Data
Tag
Tag
FCS
Len/Etype
Etype
Tag
Original Ethernet frame
Data
Len/Etype
FCS
IEE 802.1Q frame from
customer network
Data
FCS
74072
Figure 8-1
Double-tagged
frame in service
provider
infrastructure
In Figure 8-2, Customer A is assigned VLAN 30, and Customer B is assigned VLAN 40. Packets
entering the edge routers with 802.1Q tags are double-tagged when they enter the service-provider
network, with the outer tag containing VLAN ID 30 or 40, appropriately, and the inner tag containing
the original VLAN number, for example, VLAN 100. Even if both Customers A and B have VLAN 100
in their networks, the traffic remains segregated within the service-provider network because the outer
tag is different. Each customer controls its own VLAN numbering space, which is independent of the
VLAN numbering space used by other customers and the VLAN numbering space used by the
service-provider network. At the outbound port, the original VLAN numbers on the customer's network
are recovered.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-21
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Figure 8-2
802.1Q Tunnel Ports in a Service-Provider Network
Customer A
VLANs 1 to 100
Customer A
VLANs 1 to 100
802.1Q
802.1Qt trunk
runkport
port
Se rvice
provider
Port with EFP
VLAN 30
Port with Ethernet
Flow Point (EFP)
VLAN 30
802.1Q
802.1Qt trunk
runkport
port
Port with EFP
VLAN 30
Trunk
ports
Trunk
ports
Port with EFP
VLAN 40
Port with EFP
VLAN 40
802.1Q
802.1Qt trunk
runkport
port
802.1Q t runk port
Customer B
VLANs 1 to 200
Trunk
Asymmet ric link
Customer B
VLANs 1 to 200
208640
802.1Q
802.1Q tt runk
runk port
port
You can use EFPs to configure 802.1Q tunneling in two ways:
Restrictions
•
Inner VLAN range filtering for QinQ traffic from Network-to-Network Interface (NNI) to
User-to-Network Interface (UNI) is not enforced if the range is more than 1000.
•
Egress VLAN range filtering for traffic coming from NNI to UNI, is not supported on UNI.
•
Single-tagged EVC with VLAN range is not supported on the port channel.
Configuration Examples
In this example, for Customer A, interface Gigabit Ethernet 0/1 is the customer-facing port, and Gigabit
Ethernet 0/2 is a trunk port facing the service provider network. For Customer B, Gigabit Ethernet 0/3
is the customer-facing port, and Gigabit Ethernet 0/4 is the trunk port facing the service provider
network.
Customer A
Router
Router
Router
Router
(config)# interface gigabitethernet0/1
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 1-100
(config-if-srv)# bridge-domain 500
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 2 Ethernet
(config-if-srv)# encapsulation dot1q 30 second-dot1q 1-100
(config-if-srv)# rewrite ingress pop 1 symmetric
(config-if-srv)# bridge-domain 500
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-22
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
For Customer A, service instance 1 on Gigabit Ethernet port 0/1 is configured with the VLAN
encapsulations used by the customer: C-VLANs 1–100. These are forwarded on bridge-domain 500. The
service provider facing port is configured with a service instance on the same bridge-domain and with
an encapsulation dot1q command matching the S-VLAN. The rewrite ingress pop 1 symmetric
command also implies a push of the configured encapsulation on egress packets. Therefore, the original
packets with VLAN tags between 1 and 100 are encapsulated with another S-VLAN (VLAN 30) tag
when exiting Gigabit Ethernet port 0/2.
Similarly, for double- tagged (S-VLAN = 30, C-VLAN = 1–100) packets coming from the provider
network, using the rewrite ingress pop 1 symmetric command enables the outer S-VLAN tag and
forwards the original C-VLAN tagged frame over bridge-domain 500 out to Gigabit Ethernet port 0/1.
Customer B
Router
Router
Router
Router
(config)# interface gigabitethernet0/3
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 1-200
(config-if-srv)# bridge-domain 500
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/4
(config-if)# service instance 2 Ethernet
(config-if-srv)# encapsulation dot1q 40 second-dot1q 1-200
(config-if-srv)# rewrite ingress pop 1 symmetric
(config-if-srv)# bridge-domain 500
Routed QinQ
Cisco ASR 901 router supports pop 2 configuration.
Restrictions
•
Pop 2 is not supported for MPLS, L2VPN, and MPLS VPN deployments.
•
ACL and QOS configurations for pop2 EVC scenarios are not supported.
Configuration Example
This section provides the following sample configuration examples for routed QinQ on the Cisco ASR
901 Router:
Example: User to Network Interface
Gig 0/1 (Connected to BTS)
interface GigabitEthernet0/1
service instance 1 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 100
int vlan 100
ip address 1.1.1.1 255.255.255.0
Example: Network to Network Interface/Core Router
interface GigabitEthernet0/2
service instance 2 ethernet
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-23
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
encapsulation dot1q 20 second-dot1q 30
rewrite ingress tag pop 2 symmetric
bridge-domain 101
int vlan 101
ip address 2.2.2.2 255.255.255.0
In the above example:
•
The traffic coming from the Base Transceiver Station (BTS) through the GigabitEthernet interface
0/1 has the VLAN tag 10, which is popped and hits the Switch Virtual Interface (SVI) 100.This gets
routed to SVI 101 depending on the destination address.
•
At the egress on the core interface, two tags (20 and 30) are pushed and sent out of GigabitEthernet
interface 0/2, for SVI 101.
•
The traffic coming from the core router through GigabitEthernet interface 0/2, is destined to the BTS
and has two tags (20,30); both tags get popped and hit SVI 101. This gets routed to SVI 100, which
sends the traffic out of GigabitEthernet interface 0/1 with VLAN 10.
•
GigabitEthernet interface 0/2 can have multiple service instances and the traffic egresses out of the
corresponding service instance depending on the SVI it gets routed to.
Bridge Domain Routing
The router supports IP routing for bridge domains, including Layer 3 and Layer 2 VPNs, using the SVI
model.
Restrictions
•
You must configure SVIs for bridge-domain routing.
•
The bridge domain must be in the range of 1 to 4094 to match the supported VLAN range.
•
There can be only one EFP in the bridge domain.
•
You cannot have any Layer 2 switchports in the VLAN (bridge domain) used for routing.
•
You can use bridge domain routing with only native packets.
•
MPLS is supported on EFP with SVI.
•
Scale limit for EFPs reduces if you use the second-dotlq command. Use the second-dotlq any
command to maintain this limit.
Example: Configuring Bridge-Domain Routing
This is an example of configuring bridge-domain routing with a single tag EFP:
Router
Router
Router
Router
Router
(config)# interface gigabitethernet0/2
(config-if)# service instance 1 Ethernet
(config-if-srv)# encapsulation dot1q 10
(config-if-srv)# rewrite ingress tag pop 1 symmetric
(config-if-srv)# bridge-domain 100
Router (config)# interface vlan 100
Router (config-if)# ip address 20.1.1.1 255.255.255.255
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-24
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
How to Configure DHCP Client on SVI
This section contains the following topics:
•
Configuring DHCP Client on SVI
•
Verifying DHCP Client on SVI
•
Configuration Example for DHCP Client on SVI
Configuring DHCP Client on SVI
To configure the DHCP client, the IP address, mask, broadcast address, and default gateway address of
the SVI are retrieved from the server.
Complete the following steps to configure the DHCP client on SVI.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface vlan vlan-id
4.
ip address dhcp
5.
interface type-number
6.
service instance instance-id ethernet encapsulation dotlq vlan-id
7.
rewrite ingress tag pop [1|2] symmetric
8.
bridge-domain bridge-id
9.
end
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface vlan vlan-id
Configures the VLAN interface and enters interface
configuration mode.
Example:
Router(config)# interface vlan 15
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-25
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
Step 4
Command or Action
Purpose
ip address dhcp
Specifies an IP address through DHCP.
Example:
Router(config-if)# ip address dhcp
Step 5
Specifies an interface type number.
interface type-number
Example:
Router(config-if)# interface GigabitEthernet0/7
Step 6
Creates a service instance on an interface and defines the
matching criteria to be used in order to map the ingress
dotlq frames to the appropriate service instance.
service instance instance-id ethernet
encapsulation dotlq vlan-id
Example:
•
instance-id—Integer that uniquely identifies a service
instance on an interface.
•
vlan-id—VLAN range is between 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
Router(config-if)# service instance 10 ethernet
encapsulation dotlq 15
Step 7
rewrite ingress tag pop [1|2] symmetric
Example:
Specifies the encapsulation adjustment to be performed on
the frame ingress to the EFP. The symmetric keyword is
required to complete the rewrite configuration.
Router(config-if)# rewrite ingress tag pop 1
symmetric
Step 8
Binds the service instance to a bridge domain instance using
an identifier.
bridge-domain bridge-id
Example:
Router(config-if)# bridge-domain 15
Verifying DHCP Client on SVI
To verify the configuration of DHCP client on SVI, use the show command described below.
Router# show ip-address interface brief | include vlan15
Interface
Vlan15
IP-Address
15.0.0.2
OK
YES
Method
DHCP
Status
up
Protocol
up
Configuration Example for DHCP Client on SVI
Router(config)# interface Vlan 15
Router(config-if)# ip address dhcp
Router(config-if)# interface GigabitEthernet0/7
Router(config-if)# negotiation auto
Router(config-if)# service instance 10 ethernet
Router(config-if-srv)# encapsulation dot1q 15
Router(config-if-srv)# rewrite ingress tag pop 1 symmetric
Router(config-if-srv)# bridge-domain 15
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-26
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Configuring Other Features on EFPs
EFPs and Switchport MAC Addresses
Because forwarding can occur between EFPs and switchports, MAC address movement can occur on
learned addresses. Addresses learned on EFPs will have the format of interface + EFP ID, for example
gigabitethernet 0/1 + EFP 1. When an address moves between a non-secured EFP and a switchport, the
behavior is similar to that of moving between switchports.
To see MAC address information for VLANs 1 to 4094, use the show mac address-table vlan privileged
EXEC command. For VLANs 4096 to 8000, use the show mac address-table bridge-domain privileged
EXEC command. All other show mac address-table commands also support bridge domains as well as
VLANs.
When an EFP property changes (bridge domain, rewrite, encapsulation, split-horizon, secured or
unsecured, or a state change), the old dynamic MAC addresses are removed from their existing tables.
This is to prevent old invalid entries from getting retained.
EFPs and MSTP
EFP bridge domains are supported by the Multiple Spanning Tree Protocol (MSTP). These restrictions
apply when running MSTP with bridge domains.
•
All incoming VLANs (outer-most or single) mapped to a bridge domain must belong to the same
MST instance or loops could occur.
•
For all EFPs that are mapped to the same MST instance, you must configure backup EFPs on every
redundant path to prevent loss of connectivity due to STP blocking a port.
•
When STP mode is PVST+ or PVRST, EFP information is not passed to the protocol. EVC only
supports only MSTP.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-27
Chapter 8
Configuring Ethernet Virtual Connections
Monitoring EVC
Monitoring EVC
Note
Table 8-2
Statistics are not available in the service instance command. To look at flow statistics, you need to
configure a class default policy on the service instance.
Supported show Commands
Command
Description
show ethernet service evc [id evc-id |
interface interface-id] [detail]
Displays information about all EVCs, or a specific EVC when you enter an EVC
ID, or all EVCs on an interface when you enter an interface ID. The detail
option provides additional information about the EVC.
show ethernet service instance [id
instance-id interface interface-id |
interface interface-id] {[detail] | [stats]}
Displays information about one or more service instance (EFPs). If you specify
an EFP ID and interface, only data pertaining to that particular EFP is displayed.
If you specify only an interface ID, data is displayed for all EFPs on the
interface.
show bridge-domain [n]
Displays all the members of the specified bridge-domain, if a bridge-domain
with the specified number exists.
If you do not enter n, the command displays all the members of all
bridge-domains in the system.
show bridge-domain n split-horizon
[group {group_id | all}]
Displays all the members of bridge-domain n that belong to split horizon group
0, when you do not specify a group group_id with this command.
If you specify a numerical group_id, this command displays all the members of
the specified group id.
When you enter group all, the command displays all members of any split
horizon group.
show ethernet service instance detail
This command displays detailed service instance information, including Layer
2 protocol information. This is an example of the output:
Router# show ethernet service instance detail
Service Instance ID: 1
Associated Interface: Ethernet0/0
Associated EVC:
L2protocol tunnel lacp
CE-Vlans:
State: Up
EFP Statistics:
Pkts In
Bytes In
Pkts Out Bytes Out
0
0
0
0
show mac address-table
This command displays dynamically learned or statically configured MAC
security addresses.
show mac address-table bridge-domain
bridge-domain id
This command displays MAC address table information for the specified bridge
domain.
show mac address-table count
bridge-domain bridge-domain id
This command displays the number of addresses present for the specified bridge
domain.
show mac address-table learning
bridge-domain bridge-domain id
This command displays the learning status for the specified bridge domain.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-28
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Sample Configuration with Switchport to EVC Mapping
Example
This is an example of output from the show ethernet service instance detail command:
Router# show ethernet service
instance id 1 interface gigabitEthernet 0/1 detail
Service Instance ID: 1
Associated Interface: GigabitEthernet0/13
Associated EVC: EVC_P2P_10
L2protocol drop
CE-Vlans:
Encapsulation: dot1q 10 vlan protocol type 0x8100
Interface Dot1q Tunnel Ethertype: 0x8100
State: Up
EFP Statistics:
Pkts In
Bytes In
Pkts Out Bytes Out
214
15408
97150
6994800
EFP Microblocks:
****************
Microblock type: Bridge-domain
Bridge-domain: 10
This is an example of output from the show ethernet service instance statistics command:
Router# show ethernet service instance id 1 interface gigabitEthernet 0/13 stats
Service Instance 1, Interface GigabitEthernet0/13
Pkts In
Bytes In
Pkts Out Bytes Out
214
15408
97150
6994800
This is an example of output from the show mac-address table count command:
Router# show mac address-table count bridge-domain 10
Mac Entries for BD
10:
--------------------------Dynamic Address Count : 20
Static Address Count : 0
Total Mac Addresses : 20
Sample Configuration with Switchport to EVC Mapping
This example illustrates EVC in a UNI layer, 802.1q tunnelling towards aggregation and QoS
classification with marking and policing at ingress port. A two level HQOS policy is applied on the
ingress.
In this example, all the switchport configurations of the ME3400/MWR2941 have been converted into
EVC based equivalent configuration for GigabitethErnet interface 0/0. This is the ingress port connected
to the nodes. So, instead of switchport access vlan there is an EVC configured using the service
instance command under the physical interface.
The GigabitethErnet interface 0/9 has the egress port configuration which has 802.1q tunnelling
configured. This port is connected to the aggregation device. This is the fundamental difference in
configuration between the Cisco ME34xx devices and the Cisco ASR 901 router. All configurations can
be modelled along this sample working configuration.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-29
Chapter 8
Configuring Ethernet Virtual Connections
Sample Configuration with Switchport to EVC Mapping
Configuration Example
class-map match-any CELL-TRFC
match vlan 2615 3615
!
policy-map INPUT-SUBMAP
class CELL-TRFC
police cir 60000000 bc 1875000
conform-action transmit
exceed-action drop
policy-map INPUT-TOPMAP
class class-default
police cir 90000000 conform-action transmit
service-policy INPUT-SUBMAP
policy-map INPUT-MAP
class class-default
police cir 60000000 bc 1875000
conform-action transmit
exceed-action drop
!
!
interface GigabitEthernet0/0
no negotiation auto
service instance 2615 ethernet
encapsulation dot1q 2615
service-policy input INPUT-TOPMAP
bridge-domain 2615
!
service instance 3615 ethernet
encapsulation dot1q 3615
service-policy input INPUT-MAP
bridge-domain 3615
!
!
interface GigabitEthernet0/1
no negotiation auto
!
interface GigabitEthernet0/2
no negotiation auto
!
interface GigabitEthernet0/3
no negotiation auto
!
interface GigabitEthernet0/4
no negotiation auto
!
interface GigabitEthernet0/5
no negotiation auto
!
interface GigabitEthernet0/6
no negotiation auto
!
interface GigabitEthernet0/7
no negotiation auto
!
interface GigabitEthernet0/8
no negotiation auto
!
interface GigabitEthernet0/9
no negotiation auto
service instance 2615 ethernet
encapsulation dot1q 100 second-dot1q 2615
exceed-action drop
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-30
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Sample Configuration with Switchport to EVC Mapping
rewrite ingress tag pop 1 symmetric
bridge-domain 2615
!
service instance 3615 ethernet
encapsulation dot1q 100 second-dot1q 3615
rewrite ingress tag pop 1 symmetric
bridge-domain 3615
!
!
interface GigabitEthernet0/10
no negotiation auto
!
interface GigabitEthernet0/11
no negotiation auto
!
interface ToP0/12
no negotiation auto
!
interface FastEthernet0/0
full-duplex
!
interface Vlan1
!
ip forward-protocol nd
!
!
no ip http server
!
logging esm config
!
!
!
control-plane
!
!
line con 0
line con 1
transport preferred lat pad telnet rlogin udptn mop ssh
transport output lat pad telnet rlogin udptn mop ssh
line vty 0 4
login
!
exception data-corruption buffer truncate
exception crashinfo buffersize 128
!
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-31
Chapter 8
Configuring Ethernet Virtual Connections
Additional References
Additional References
The following sections provide references related to Configuring EVC feature.
Related Documents
Related Topic
Document Title
Cisco IOS Commands
Cisco IOS Master Commands List, All Releases
ASR 901 Command Reference
Cisco ASR 901 Series Aggregation Services Router Command
Reference
Cisco IOS Interface and Hardware Component
Commands
Cisco IOS Interface and Hardware Component Command Reference
Standards
Standard
Title
None
—
MIBs
MIB
MIBs Link
None
To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
None
—
Technical Assistance
Description
Link
http://www.cisco.com/techsupport
The Cisco Technical Support website contains
thousands of pages of searchable technical content,
including links to products, technologies, solutions,
technical tips, and tools. Registered Cisco.com users
can log in from this page to access even more content.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-32
OL-23826-09
Chapter 8
Configuring Ethernet Virtual Connections
Feature Information for Configuring Ethernet Virtual Connections
Feature Information for Configuring Ethernet Virtual
Connections
Table 8-3 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 8-3
Table 8-3 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for Configuring Ethernet Virtual Connections
Feature Name
Releases
Feature Information
Configuring Ethernet Virtual Connections
15.2(2)SNH1
See the following links for more information about this
feature:
EVC Default Encapsulation
15.3(2)S
•
Supported EVC Features
•
Understanding EVC Features
•
Configuring EFPs
•
Configuring Other Features on EFPs
•
Monitoring EVC
•
Sample Configuration with Switchport to EVC
Mapping
See the following links for more information about this
feature:
•
Default EVC Configuration
•
How to Configure EVC Default Encapsulation
•
Configuring EVC Default Encapsulation with
Xconnect
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
8-33
Chapter 8
Configuring Ethernet Virtual Connections
Feature Information for Configuring Ethernet Virtual Connections
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
8-34
OL-23826-09
CH A P T E R
9
Configuring EtherChannels
This chapter describes how to configure EtherChannels on the Cisco ASR 901 router Layer 2 or Layer 3
LAN ports.
Contents
•
Understanding How EtherChannels Work, page 9-1
•
EtherChannel Configuration Guidelines and Restrictions, page 9-4
•
Configuring Etherchannels, page 9-5
•
EVC On Port-Channel, page 9-10
Understanding How EtherChannels Work
This section contains the following topics:
•
EtherChannel Feature Overview, page 9-1
•
Understanding How EtherChannels Are Configured, page 9-2
•
Understanding Port-Channel Interfaces, page 9-4
•
Understanding Load Balancing, page 9-4
EtherChannel Feature Overview
An EtherChannel bundles individual Ethernet links into a single logical link that provides the aggregate
bandwidth of up to eight physical links.
The Cisco ASR 901 router supports a maximum of eight EtherChannels with a maximum eight member
links in each EtherChannel.
You can form an EtherChannel with up to eight compatibly configured LAN ports in a Cisco ASR 901.
All LAN ports in each EtherChannel must be of the same speed and must all be configured as Layer 2
LAN ports.
Note
The network device to which a Cisco ASR 901 is connected may impose its own limits on the number
of ports in an EtherChannel.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
9-1
Chapter 9
Configuring EtherChannels
Understanding How EtherChannels Work
If a segment within an EtherChannel fails, traffic previously carried over the failed link switches to the
remaining segments within the EtherChannel. When a failure occurs, the EtherChannel feature sends a
trap that identifies the router, the EtherChannel, and the failed link. Inbound broadcast packets on one
segment in an EtherChannel are blocked from returning on any other segment of the EtherChannel.
Understanding How EtherChannels Are Configured
This section contains the following topics:
•
EtherChannel Configuration Overview, page 9-2
•
Understanding Manual EtherChannel Configuration, page 9-2
•
Understanding IEEE 802.3ad LACP EtherChannel Configuration, page 9-2
EtherChannel Configuration Overview
You can configure EtherChannels manually or use the Link Aggregation Control Protocol (LACP) to form
EtherChannels. The EtherChannel protocols allow ports with similar characteristics to form an
EtherChannel through dynamic negotiation with connected network devices. LACP is defined in IEEE
802.3ad.
Table 9-1 lists the user-configurable EtherChannel modes.
Table 9-1
EtherChannel Modes
Mode
Description
on
This is the mode that forces the LAN port to channel unconditionally. In the on mode, a
usable EtherChannel exists only when a LAN port group in the on mode is connected to
another LAN port group in the on mode. Because ports configured in the on mode do not
negotiate, there is no negotiation traffic between the ports. You cannot configure the on
mode with an EtherChannel protocol.
passive
(Default for LACP) LACP mode that places a port into a passive negotiating state, in which
the port responds to LACP packets it receives but does not initiate LACP negotiation.
active
LACP mode that places a port into an active negotiating state, in which the port initiates
negotiations with other ports by sending LACP packets.
Understanding Manual EtherChannel Configuration
Manually configured EtherChannel ports do not exchange EtherChannel protocol packets. A manually
configured EtherChannel forms only when you enter configure all ports in the EtherChannel compatibly.
Understanding IEEE 802.3ad LACP EtherChannel Configuration
LACP supports the automatic creation of EtherChannels by exchanging LACP packets between LAN
ports. LACP packets are exchanged only between ports in passive and active modes.
The protocol learns the capabilities of LAN port groups dynamically and informs the other LAN ports.
Once LACP identifies correctly matched Ethernet links, it facilitates grouping the links into an
EtherChannel. The EtherChannel is then added to the spanning tree as a single bridge port.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
9-2
OL-23826-09
Chapter 9
Configuring EtherChannels
Understanding How EtherChannels Work
Both the passive and active modes allow LACP to negotiate between LAN ports to determine if they can
form an EtherChannel, based on criteria such as port speed and trunking state. Layer 2 EtherChannels
also use VLAN numbers.
LAN ports can form an EtherChannel when they are in different LACP modes as long as the modes are
compatible. For example:
•
A LAN port in active mode can form an EtherChannel successfully with another LAN port that is
in active mode.
•
A LAN port in active mode can form an EtherChannel with another LAN port in passive mode.
•
A LAN port in passive mode cannot form an EtherChannel with another LAN port that is also in
passive mode, because neither port will initiate negotiation.
Table 9-2 provides a summary of these combinations.
Table 9-2
LACP EtherChannel Modes
Router A
Router B
Result
passive mode
passive mode
No EtherChannel group is created.
passive mode
active mode
EtherChannel group is created.
active mode
passive mode
EtherChannel group is created.
active mode
active mode
EtherChannel group is created.
LACP uses the following parameters:
•
LACP system priority—You must configure an LACP system priority on each router running LACP.
The system priority can be configured automatically or through the command line interface (CLI)
(see the “Configuring the LACP System Priority and System ID” section on page 9-6). LACP uses
the system priority with the router MAC address to form the system ID and also during negotiation
with other systems.
Note
•
LACP port priority—You must configure an LACP port priority on each port configured to use
LACP. The port priority can be configured automatically or through the CLI (see the “Configuring
Channel Groups” section on page 9-5). LACP uses the port priority with the port number to form
the port identifier. LACP uses the port priority to decide which ports should be put in standby mode
when there is a hardware limitation that prevents all compatible ports from aggregating.
Note
•
The LACP system ID is the combination of the LACP system priority value and the MAC
address of the router.
Port priority is only effective when it is configured on a device with an LACP system priority
higher than the peer.
LACP administrative key—LACP automatically configures an administrative key value equal to the
channel group identification number on each port configured to use LACP. The administrative key
defines the ability of a port to aggregate with other ports. A port’s ability to aggregate with other
ports is determined by these factors:
– Port physical characteristics, such as data rate, duplex capability, and point-to-point or shared
medium
– Configuration restrictions that you establish
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
9-3
Chapter 9
Configuring EtherChannels
EtherChannel Configuration Guidelines and Restrictions
On ports configured to use LACP, LACP tries to configure the maximum number of compatible ports in
an EtherChannel, up to the maximum allowed by the hardware (eight ports). If LACP cannot aggregate
all the ports that are compatible (for example, the remote system might have more restrictive hardware
limitations), then all the ports that cannot be actively included in the channel are put in hot standby state
and are used only if one of the channeled ports fails. You can configure an additional 8 standby ports
(total of 16 ports associated with the EtherChannel).
Understanding Port-Channel Interfaces
Each EtherChannel has a numbered port-channel interface. The configuration that you apply to the
port-channel interface affects all LAN ports assigned to the port-channel interface.
After you configure an EtherChannel, the configuration that you apply to the port-channel interface
affects the EtherChannel; the configuration that you apply to the LAN ports affects only the LAN port
to which you apply the configuration. To change the parameters of all ports in an EtherChannel, apply
the configuration commands to the port-channel interface, for example, Spanning Tree Protocol (STP)
commands or commands to configure a Layer 2 EtherChannel as a trunk.
Understanding Load Balancing
An EtherChannel balances the traffic load across the links in an EtherChannel by reducing part of the
binary pattern formed from the addresses in the frame to a numerical value that selects one of the links
in the channel.
EtherChannel load balancing can use MAC addresses or IP addresses. EtherChannel load balancing can
use either source or destination or both source and destination addresses or ports. The selected mode
applies to all EtherChannels configured on the router. EtherChannel load balancing can use MPLS Layer
2 information.
Use the option that provides the balance criteria with the greatest variety in your configuration. For
example, if the traffic on an EtherChannel is going only to a single MAC address and you use the
destination MAC address as the basis of EtherChannel load balancing, the EtherChannel always chooses
the same link in the EtherChannel; using source addresses or IP addresses might result in better load
balancing.
EtherChannel Configuration Guidelines and Restrictions
Note
When EtherChannel interfaces are configured improperly, they are disabled automatically to avoid
network loops and other problems.
•
The commands in this chapter can be used on all LAN ports in the Cisco ASR 901.
•
Configure all LAN ports in an EtherChannel to use the same EtherChannel protocol; you cannot run
two EtherChannel protocols in one EtherChannel.
•
Configure all LAN ports in an EtherChannel to operate at the same speed and in the same duplex
mode.
•
LACP does not support half-duplex. Half-duplex ports in an LACP EtherChannel are put in the
suspended state.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
9-4
OL-23826-09
Chapter 9
Configuring EtherChannels
Configuring Etherchannels
•
Enable all LAN ports in an EtherChannel. If you shut down a LAN port in an EtherChannel, it is
treated as a link failure and its traffic is moved to one of the remaining ports in the EtherChannel.
•
An EtherChannel will not form if one of the LAN ports is a Switched Port Analyzer (SPAN)
destination port.
•
For Layer 2 EtherChannels:
– Assign all LAN ports in the EtherChannel to the same VLAN or configure them as trunks.
– If you configure an EtherChannel from trunking LAN ports, verify that the trunking mode is the
same on all the trunks. LAN ports in an EtherChannel with different trunk modes can operate
unpredictably.
– An EtherChannel supports the same allowed range of VLANs on all the LAN ports in a trunking
Layer 2 EtherChannel. If the allowed range of VLANs is not the same, the LAN ports do not
form an EtherChannel.
– LAN ports with different STP port path costs can form an EtherChannel as long they are
compatibly configured with each other. If you set different STP port path costs, the LAN ports
are still compatible for the formation of an EtherChannel.
– An EtherChannel will not form if protocol filtering is set differently on the LAN ports.
•
You can configure a maximum of eight port-channel interfaces, numbered from 1 to 8.
•
After you configure an EtherChannel, the configuration that you apply to the port-channel interface
affects the EtherChannel. The configuration that you apply to the LAN ports affects only those LAN
ports to which you apply the configuration.
Configuring Etherchannels
This section contains the following topics:
Note
•
Configuring Channel Groups, page 9-5
•
Configuring the LACP System Priority and System ID, page 9-6
•
Configuring the LACP Transmit Rate, page 9-7
•
Configuring EtherChannel Load Balancing, page 9-8
•
Modifying MTU Size on Port-Channel, page 9-9
•
EVC On Port-Channel, page 9-10
Ensure that the LAN ports are configured correctly (see the “EtherChannel Configuration Guidelines and
Restrictions” section on page 9-4).
Configuring Channel Groups
Note
•
When configuring Layer 2 EtherChannels, configure the LAN ports with the channel-group
command as described in this section, which automatically creates the port-channel logical
interface. You cannot add Layer 2 LAN ports into a manually created port-channel interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
9-5
Chapter 9
Configuring EtherChannels
Configuring Etherchannels
•
To create port-channel interfaces for Layer 2 EtherChannels, the Layer 2 LAN ports must be
connected and functioning.
To configure channel groups, complete the following steps for each LAN port in interface configuration
mode:
Command
Purpose
Step 1
Router(config)# interface type slot/port
Selects a LAN port to configure.
Step 2
Router(config-if)# no ip address
Ensures that there is no IP address assigned to the LAN
port.
Step 3
Router(config-if)# channel-protocol lacp
(Optional) On the selected LAN port, restricts the
channel-group command to the EtherChannel protocol
configured with the channel-protocol command.
Step 4
Router(config-if)# channel-group number mode
{active | on | passive}
Configures the LAN port in a port-channel and specifies
the mode (see Table 9-1 on page 9-2). LACP supports the
active and passive modes.
Step 5
Router(config-if)# lacp port-priority
priority_value
(Optional for LACP) Valid values are 1 through 65535.
Higher numbers have lower priority. The default is 32768.
Step 6
Router(config-if)# end
Exits configuration mode.
Step 7
Router# show running-config interface type
slot/port
Router# show interfaces type slot/port
etherchannel
Verifies the configuration.
type—gigabitethernet.
Configuring the LACP System Priority and System ID
The LACP system ID is the combination of the LACP system priority value and the MAC address of the
router. To configure the LACP system priority and system ID, complete the following tasks:
Command
Purpose
Step 1
Router(config)# lacp system-priority
priority_value
(Optional for LACP) Valid values are 1 through 65535.
Higher numbers have lower priority. The default is 32768.
Step 2
Router(config)# end
Exits configuration mode.
Step 3
Router# show lacp sys-id
Verifies the configuration.
Configuration examples for LACP system priority
This example shows how to configure the LACP system priority:
Router# configure terminal
Router(config)# lacp system-priority 23456
Router(config)# end
This example shows how to verify the configuration:
Router# show lacp sys-id
23456,0050.3e8d.6400
The system priority is displayed first, followed by the MAC address of the router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
9-6
OL-23826-09
Chapter 9
Configuring EtherChannels
Configuring Etherchannels
Configuring the LACP Transmit Rate
To configure the rate at which Link Aggregation Control Protocol (LACP) control packets are
transmitted to an LACP-supported interface, complete the following tasks:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
lacp rate {fast | normal}
5.
end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface type number
Specifies an interface type and number, and enters interface
configuration mode.
Example:
Router(config)# interface
gigabitethernet 0/1
Step 4
lacp rate {fast | normal}
Example:
Configures the transmission rate of LACP control packets to an
LACP-supported interface.
•
fast—Specifies that LACP control packets are transmitted at
the fast rate, once every second.
•
normal—Specifies that LACP control packets are transmitted
at the normal rate, every 30 seconds after the link is bundled.
Router(config-if)# lacp rate fast
Step 5
end
Exits the interface configuration mode and enters the privileged
EXEC mode.
Example:
Router(config-if)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
9-7
Chapter 9
Configuring EtherChannels
Configuring Etherchannels
Verifying the LACP Transmit Rate
To verify the LACP control packet transmission rate, use the following show command:
Router# show lacp internal
Flags:
S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode
P - Device is in Passive mode
Channel group 5
Port
Gi0/1
Flags
FA
State
bndl
LACP port
Priority
32768
Admin
Key
0xA
Oper
Key
0xA
Port
Number
0x102
Port
State
0x7D
Configuring EtherChannel Load Balancing
To configure EtherChannel load balancing, complete the following steps:
Step 1
Command
Purpose
Router(config)# port-channel load-balance
{src-mac | dst-mac | src-dst-mac | src-ip |
dst-ip | src-dst-ip | src-port | dst-port |
src-dst-port}
Configures EtherChannel load balancing. The
load-balancing keywords indicate the following
information:
•
dst-ip—Destination IP addresses
•
dst-mac—Destination MAC addresses
•
dst-port—Destination Layer 4 port
•
src-dst-ip—Source and destination IP addresses
•
src-dst-mac—Source and destination MAC
addresses
•
src-dst-port—Source and destination Layer 4 port
•
src-ip—Source IP addresses
•
src-mac—Source MAC addresses
•
src-port—Source Layer 4 port
Step 2
Router(config)# end
Exits configuration mode.
Step 3
Router# show etherchannel load-balance
Verifies the configuration.
Configuration Examples
This example shows how to configure EtherChannel to use source and destination IP addresses:
Router# configure terminal
Router(config)# port-channel load-balance src-dst-ip
Router(config)# end
Router(config)#
This example shows how to verify the configuration:
Router# show etherchannel load-balance
Source XOR Destination IP address
Router#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
9-8
OL-23826-09
Chapter 9
Configuring EtherChannels
Configuring Etherchannels
Modifying MTU Size on Port-Channel
Complete the following steps to modify MTU size on the port-channel interface:
Restrictions
If the MTU size of a port-channel member link is different from the MTU size of the port-channel
interface, the member link is not bundled.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface port-channel number
4.
mtu bytes
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Selects a port-channel interface and enters interface
configuration mode.
interface port-channel number
•
Example:
Router(config)# interface port-channel 1
Step 4
number—Specifies the port-channel interface
number. The range is from 1 to 8.
Configures the MTU size for port-channel interface.
mtu bytes
•
Example:
Router(config-if)# mtu 4000
Note
bytes—The range is from 1500 to 9216. The
default is 9216.
To set the MTU size to its default value, use
the no mtu or default mtu command.
Verifying the MTU Size on Port-Channel
To verify the MTU size on port-channel interface, use the show interface port-channel command.
Router# show interface port-channel 1
Port-channel1 is up, line protocol is up (connected)
Hardware is EtherChannel, address is 4055.3989.4a15 (bia 4055.3989.4a15)
MTU 4000 bytes, BW 2000000 Kbit/sec, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 0/255
Encapsulation ARPA, loopback not set
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
9-9
Chapter 9
Configuring EtherChannels
EVC On Port-Channel
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
EVC On Port-Channel
An EtherChannel bundles individual Ethernet links into a single logical link that provides the aggregate
bandwidth of up to eight physical links.The EVC EtherChannel feature provides support for
EtherChannels on Ethernet Virtual Connection Services (EVCS) service instances.
The EVC EtherChannel feature supports MPBE, local connect, and xconnect service types.
Load balancing is accomplished on a Ethernet flow point (EFP) basis where a number of EFPs exclusively
pass traffic through member links. In a default load balancing, you have no control over how the EFPs
are grouped together, and sometimes the EFP grouping may not be ideal. To avoid this, use manual load
balancing to control the EFP grouping.
Restrictions for EVC EtherChannel
The following restrictions apply to EVC EtherChannel:
•
Bridge-domains, EVCs, and IP subinterfaces are allowed over the port-channel interface and the
main interface.
•
If you configure a physical port as part of a channel group, you cannot configure EVCs under that
physical port.
•
If port-channel is configured on an MPLS core, the encapsulation ID should be the same as the
bridge domain.
•
A physical port that is part of an EVC port-channel cannot have EVC configuration.
•
Statically configuring port-channel membership with LACP is not supported.
•
You can apply QoS policies under EVCs on a port-channel.
•
You cannot use the police percent commands on EVC port-channels in flat policy-maps or in parent
of HQoS policy-maps.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
9-10
OL-23826-09
Chapter 9
Configuring EtherChannels
EVC On Port-Channel
Configuring EVC on Port-Channel
To configure the EVC on port-channel, complete these steps in the interface configuration mode:
Step 1
Command
Purpose
interface port-channel number
Creates the port-channel interface.
Example:
Router(config)# interface port-channel
11
Step 2
Creates a service instance (an instantiation of an EVC)
on an interface and sets the device into the config-if-srv
submode.
[no] service instance id Ethernet
[service-name}
Example:
Router(config-if)# service instance 101
ethernet
Step 3
encapsulation {untagged|dot1q vlan-id
[second-dot1q vlan-id]}
Defines the matching criteria to be used in order to map
ingress dot1q frames on an interface to the appropriate
service instance.
Example:
Router(config-if-srv)# encapsulation
dot1q 13
Step 4
rewrite ingress tag
pop 1 symmetric
Specifies the tag manipulation that is to be performed
on the frame ingress to the service instance.
Example:
Router(config-if-srv)# rewrite ingress
tag pop 1 symmetric
Step 5
The bridge-domain command binds the service instance
to a bridge domain instance where bridge-id is the
identifier for the bridge domain instance.
[no] bridge-domain bridge-id
Example:
Router(config-if-srv)# bridge-domain 12
Verifying the Configuration
Use the following commands to verify the configuration:
Command
Purpose
Router# show ethernet service evc [id evc-id | interface
interface-id] [detail]
Displays information pertaining to a specific EVC if an EVC
ID is specified, or pertaining to all EVCs on an interface if an
interface is specified. The detailed option provides additional
information on the EVC.
Router# show ethernet service instance interface
port-channel number [summary]
Displays the summary of all the configured EVCs within the
interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
9-11
Chapter 9
Configuring EtherChannels
EVC On Port-Channel
Command
Purpose
Router# show ethernet service instance [id instance-id
interface interface-id | interface interface-id] [detail]
Displays information about one or more service instances. If a
service instance ID and interface are specified, only data
pertaining to that particular service instance is displayed. If
only an interface ID is specified, displays data for all service
instances s on the given interface.
Router# show mpls l2 transport vc detail
Displays detailed information related to the virtual connection
(VC).
Router# show mpls forwarding
Displays the contents of the Multiprotocol Label Switching
(MPLS) Label Forwarding Information Base (LFIB).
Note
Output should have the label entry l2ckt.
Router# show etherchannel summary
Displays view all EtherChannel groups states and ports.
Router# show policy-map interface service instance
Displays the policy-map information for a given service
instance.
Troubleshooting
Table 9-3
Troubleshooting Scenarios for EVC on a Port-Channel
Problem
Solution
Port data block issues in port-channel
Use the show ethernet service interface [interface-id]
[detail] command to view information on the port data. Share
the output with TAC for further investigation.
Issues with platform events or errors
Use the debug platform npc custom-ether client [event,
error] command to debug and trace platform issues. Share the
output with TAC for further investigation.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
9-12
OL-23826-09
CH A P T E R
10
Configuring Ethernet OAM
Ethernet Operations, Administration, and Maintenance (OAM) is a protocol for installing, monitoring,
and troubleshooting ethernet networks, to increase management capability within the context of the
overall Ethernet infrastructure.
The Cisco ASR 901 router supports:
•
IEEE 802.3ah Ethernet OAM discovery, link monitoring, remote fault detection, and remote
loopback.
•
IEEE 802.1ag Connectivity Fault Management (CFM)
•
Ethernet Local Management Interface (E-LMI)
•
IP Service Level Agreements (SLAs) for CFM
•
ITU-T Y.1731 fault management
This chapter provides information about configuring the Ethernet OAM, CFM and E-LMI and also
enabling Ethernet Loopback.
For complete command and configuration information for Ethernet OAM see the Cisco IOS Carrier
Ethernet Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/ios-xml/ios/cether/configuration/12-2sr/ce-12-2sr-book.html
Note
The Cisco ASR 901 router does not necessarily support all of the commands listed in the Cisco IOS
Carrier Ethernet documentation.
Note
Cisco ASR 901 does not support CFM pre-draft version.
Contents
•
Understanding Ethernet CFM, page 10-2
•
Configuring Ethernet CFM, page 10-2
•
Configuring CFM over EFP with Cross Connect, page 10-19
•
Configuring Y.1731 Fault Management, page 10-26
•
Managing and Displaying Ethernet CFM Information, page 10-30
•
Understanding the Ethernet OAM Protocol, page 10-32
•
Setting Up and Configuring Ethernet OAM, page 10-35
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-1
Chapter 10
•
Displaying Ethernet OAM Protocol Information, page 10-45
•
Understanding E-LMI, page 10-48
•
Configuring E-LMI, page 10-49
•
Displaying E-LMI Information, page 10-51
•
Configuring Ethernet Loopback, page 10-51
•
Configuring Y.1564 to Generate Ethernet Traffic, page 10-56
Configuring Ethernet OAM
Understanding Ethernet CFM
Ethernet CFM is an end-to-end per-service-instance (per VLAN) Ethernet layer OAM protocol that
includes proactive connectivity monitoring, fault verification, and fault isolation. End-to-end can be
provider-edge-to-provider-edge (PE-to-PE) device. Ethernet CFM, as specified by IEEE 802.1ag, is the
standard for Layer 2 ping, Layer 2 traceroute, and end-to-end connectivity check of the Ethernet
network.
For more information about ethernet CFM, see Ethernet Connectivity Fault Management.
IP SLA Support for CFM
The router supports CFM with IP Service Level Agreements (SLA), which provides the ability to gather
Ethernet layer network performance metrics. Available statistical measurements for the IP SLA CFM
operation include round-trip time, jitter (interpacket delay variance), and packet loss. You can schedule
multiple IP SLA operations and use Simple Network Management Protocol (SNMP) trap notifications
and syslog messages for proactive threshold violation monitoring.
IP SLA integration with CFM gathers Ethernet layer statistical measurements by sending and receiving
Ethernet data frames between CFM MEPs. Performance is measured between the source MEP and the
destination MEP. Unlike other IP SLA operations that provide performance metrics for only the IP layer,
IP SLA with CFM provides performance metrics for Layer 2.
You can manually configure individual Ethernet ping or jitter operations. You can also configure an IP
SLA automatic Ethernet operation that queries the CFM database for all MEPs in a given maintenance
domain and VLAN. The operation then automatically creates individual Ethernet ping or jitter
operations based on the discovered MEPs.
Because IP SLA is a Cisco proprietary feature, interoperability between CFM draft 1 and CFM 802.1ag
is handled automatically by the router.
For more information about IP SLA operation with CFM, see the IP SLAs for Metro-Ethernet feature
module at this URL:
http://www.cisco.com/en/US/docs/ios/12_2sr/12_2srb/feature/guide/sr_meth.html
Configuring Ethernet CFM
Configuring Ethernet CFM requires configuring the CFM domain. You can optionally configure and
enable other CFM features such as crosschecking, remote MEP, port MEPs, SNMP traps, and fault
alarms. Note that some of the configuration commands and procedures differ from those used in CFM
draft 1.
This section contains the following topics:
•
Default Ethernet CFM Configuration, page 10-3
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-2
OL-23826-09
Chapter 10
Configuring Ethernet OAM
•
Ethernet CFM Configuration Restrictions and Guidelines, page 10-3
•
Configuring the CFM Domain, page 10-3
•
Configuring Multi-UNI CFM MEPs in the Same VPN, page 10-7
•
Configuring Ethernet CFM Crosscheck, page 10-12
•
Configuring Static Remote MEP, page 10-13
•
Configuring a Port MEP, page 10-14
•
Configuring SNMP Traps, page 10-15
•
Configuring IP SLA CFM Operation, page 10-16
Default Ethernet CFM Configuration
•
CFM is globally disabled.
•
CFM is enabled on all interfaces when CFM is globally enabled.
•
A port can be configured as a flow point (MIP/MEP), a transparent port, or disabled (CFM disabled).
By default, ports are transparent ports until configured as MEP, MIP, or disabled.
•
There are no MEPs or MIPs configured.
•
When configuring a MEP, if you do not configure direction, the default is up (inward facing).
•
For Multi-UNI CFM MEPs (with up direction), port-based model for MAC address assignment is
used instead of bridge brain model.
Ethernet CFM Configuration Restrictions and Guidelines
•
You cannot configure CFM on VLAN interfaces.
•
CFM is configurable only under EVC and physical or port channel interfaces.
•
CFM is supported on ports running MSTP.
•
You must configure a port MEP at a lower level than any service (VLAN) MEPs on an interface.
Configuring the CFM Domain
Complete the following steps to configure the Ethernet CFM domain, configure a service to connect the
domain to a VLAN, or configure a port to act as a MEP. You can also enter the optional commands to
configure other parameters, such as continuity checks.
Note
You do not need to enter the ethernet cfm ieee global configuration command to configure the CFM
version as IEEE 802.1ag; the CFM version is always 802.1ag and the command is automatically
generated when you enable CFM.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet cfm global
Globally enable Ethernet CFM on the router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-3
Chapter 10
Step 3
Step 4
Configuring Ethernet OAM
Command
Purpose
ethernet cfm traceroute cache [size entries |
hold-time minutes]
(Optional) Configure the CFM traceroute cache. You can
set a maximum cache size or hold time.
ethernet cfm mip auto-create level level-id vlan
vlan-id
•
(Optional) For size, enter the cache size in number of
entry lines. The range is from 1 to 4095; the default is
100 lines.
•
(Optional) For hold-time, enter the maximum cache
hold time in minutes. The range is from 1 to 65535; the
default is 100 minutes.
(Optional) Configure the router to automatically create
MIPs for VLAN IDS that are not associated with specific
maintenance associations at the specified level. The level
range is 0 to 7.
Note
Configure MIP auto-creation only for VLANs that
MIPs should monitor. Configuring for all VLANs
can be CPU and memory-intensive.
Step 5
ethernet cfm mip filter
(Optional) Enable MIP filtering, which means that all CFM
frames at a lower level are dropped. The default is disabled.
Step 6
ethernet cfm domain domain-name level level-id
Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 7
id {mac-address domain_number | dns name | null}
(Optional) Assign a maintenance domain identifier.
Step 8
Step 9
service {ma-name | ma-number | vpn-id vpn} {vlan
vlan-id [direction down] | port}
continuity-check
•
mac-address domain_number—Enter the MAC
address and a domain number. The number can be from
0 to 65535.
•
dns name—Enter a DNS name string. The name can be
a maximum of 43 characters.
•
null—Assign no domain name.
Define a customer service maintenance association (MA)
name or number or VPN ID to be associated with the
domain, a VLAN ID or port MEP, and enter
ethernet-cfm-service configuration mode.
•
ma-name—a string of no more than 100 characters that
identifies the MAID.
•
ma-number—a value from 0 to 65535.
•
vpn-id vpn—enter a VPN ID as the ma-name.
•
vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
•
(Optional) direction down—specify the service
direction as down.
•
port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Enable sending and receiving of continuity check
messages.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-4
OL-23826-09
Chapter 10
Step 10
Configuring Ethernet OAM
Command
Purpose
continuity-check interval value
(Optional) Set the interval at which continuity check
messages are sent. The available values are 100 ms,
1 second, 10 seconds, 1 minute and 10 minutes. The default
is 10 seconds.
Note
Because faster CCM rates are more CPU-intensive,
we do not recommend configuring a large number
of MEPs running at 100 ms intervals.
Step 11
continuity-check loss-threshold threshold-value
(Optional) Set the number of continuity check messages to
be missed before declaring that an MEP is down. The range
is 2 to 255; the default is 3.
Step 12
maximum meps value
(Optional) Configure the maximum number of MEPs
allowed across the network. The range is from 1 to 65535.
The default is 100.
Step 13
sender-id {chassis | none}
(Optional) Include the sender ID TLVs, attributes
containing type, length, and values for neighbor devices.
Step 14
mip auto-create [lower-mep-only | none]
•
chassis—Send the chassis ID (host name).
•
none—Do not include information in the sender ID.
(Optional) Configure auto creation of MIPs for the service.
•
lower-mep-only—Create a MIP only if there is a MEP
for the service in another domain at the next lower
active level.
•
none —No MIP auto-create.
Step 15
exit
Return to ethernet-cfm configuration mode.
Step 16
mip auto-create [lower-mep-only]
(Optional) Configure auto creation of MIPs for the domain.
•
lower-mep-only—Create a MIP only if there is a MEP
for the service in another domain at the next lower
active level.
Step 17
mep archive-hold-time minutes
(Optional) Set the number of minutes that data from a
missing maintenance end point is kept before it is purged.
The range is 1 to 65535; the default is 100 minutes.
Step 18
exit
Return to global configuration mode.
Step 19
interface interface-id
Specify an interface to configure, and enter interface
configuration mode.
Step 20
service instance number ethernet name
Specify the service instance number and the name of the
EVC.
Step 21
cfm mip level level-id
(Optional) Configure a customer level or service-provider
level maintenance intermediate point (MIP) for the
interface. The MIP level range is 0 to 7.
Note
This step is not required if you have entered the
ethernet cfm mip auto-create global
configuration command or the mip auto-create
ethernet-cfm or ethernet-cfm-srv configuration
mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-5
Chapter 10
Step 22
Configuring Ethernet OAM
Command
Purpose
cfm mep domain domain-name mpid identifier
Configure maintenance end points for the domain, and
enter Ethernet cfm mep mode.
•
domain domain-name—Specify the name of the
created domain.
•
mpid identifier—Enter a maintenance end point
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
Step 23
cos value
(Optional) Specify the class of service (CoS) value to be
sent with the messages. The range is 0 to 7.
Step 24
end
Return to privileged EXEC mode.
Step 25
show ethernet cfm maintenance-points {local |
remote}
Verify the configuration.
Step 26
show ethernet cfm errors [configuration]
(Optional) Display the configuration error list.
Step 27
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Note
Use the no form of each command to remove the configuration or return to the default configurations.
Example for Basic CFM configuration
Router(config)# ethernet cfm ieee
Router(config)# ethernet cfm global
Router(config)# ethernet cfm domain abc level 3
Router(config-ecfm)# service test evc EVC1 vlan 5
Router(config-ecfm-srv)# continuity-check
Router(config-ecfm-srv)# exit
Router(config-ecfm)# exit
Router(config)# ethernet evc EVC1
Router(config)# interface gigabitethernet 0/1
Router(config-if)# service instance 1 ethernet EVC1
Router(config-if-srv)# encapsulation dot1q 5
Router(config-if-srv)# rewrite ingress tag pop 1 symmetric
Router(config-if-srv)# bridge domain 5
Router(config-if-srv)# cfm mep domain abc mpid 100
Router(config-if-ecfm-mep)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-6
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Configuring Multi-UNI CFM MEPs in the Same VPN
Effective with Cisco IOS Release 15.3(2)S, services are configured such that two or more bridge
domains (BDs) are used to achieve UNI isolation and backhauling towards provider edge (PE) device.
Local MEPs (with up direction) need to be configured on the UNIs (with the associated BDs) to monitor
the service backhaul connection. To achieve this, use the alias command to configure a CFM MA, MA2,
as an alias to another MA, MA1. As a result, MA1 behaves as though it is configured as MA2 on a
different Bridge Domain (BD) associated with it. MA1 and MA2 function as if they are part of the same
service, thus associating the same CFM MA to two different BDs and UNI isolation.
Figure 10-1 shows the configuring Mutli-NNI CFM in the same VPN.
Figure 10-1
Configuring Multi-NNI CFM in the Same VPN
Restrictions:
•
Two MAs can be configured such that MA2 connected with different BD will act as a proxy (alias)
for MA1 only for the MEPs which have the service direction as Up.
•
Y1731-PM is not supported with Multi-NNI CFM.
Complete these steps to configure Multi-UNI CFM MEPs in the same VPN.
SUMMARY STEPS
1.
configure terminal
2.
ethernet cfm global
3.
ethernet cfm domain domain-name level level-id
4.
service {ma-name | ma-number | vpn-id vpn} {vlan vlan-id [direction down] | port}
5.
continuity-check
6.
continuity-check interval value
7.
continuity-check loss-threshold threshold-value
8.
alias{alias-short-ma-name | icc icc-code meg-id | number ma-number | vlan-id vlan-id | vpn-id
vpn-id}
9.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-7
Chapter 10
Configuring Ethernet OAM
10. exit
11. interface interface-id
12. service instance number ethernet name
13. cfm mep domain domain-name mpid identifier
14. end
15. show ethernet cfm maintenance-points {local | remote}
16. show ethernet cfm errors [configuration]
17. copy running-config startup-config
DETAILED STEPS
Command
Purpose
Step 1
configure terminal
Enter global configuration mode. Enter your password if
prompted.
Step 2
ethernet cfm global
Globally enable Ethernet CFM on the router.
Example:
Router(config)# ethernet cfm global
Step 3
ethernet cfm domain domain-name level level-id
Example:
Define a CFM domain, set the domain level, and enter
ethernet-CFM configuration mode for the domain. The
maintenance level number range is 0 to 7.
Router(config)# ethernet cfm domain MD6 level 6
Step 4
service {ma-name | ma-number | vpn-id vpn} {vlan
vlan-id [direction down] | port}
Example:
Router(config-ecfm)# service MA6 evc evc30 vlan
30
Define a customer service maintenance association (MA)
name or number or VPN ID to be associated with the
domain, a VLAN ID or port MEP, and enter
ethernet-cfm-service configuration mode.
•
ma-name—a string of no more than 100 characters that
identifies the MAID.
•
ma-number—a value from 0 to 65535.
•
vpn-id vpn—enter a VPN ID as the ma-name.
•
vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
•
(Optional) direction down—specify the service
direction as down.
Note
•
Two MAs can be configured such that MA2
connected with different BD will act as a proxy
(alias) for MA1 only for the MEPs which have the
service direction as Up.
port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-8
OL-23826-09
Chapter 10
Step 5
Configuring Ethernet OAM
Command
Purpose
continuity-check
Enable sending and receiving of continuity check
messages.
Example:
Router(config-ecfm-srv)# continuity-check
Step 6
continuity-check interval value
Example:
Router(config-ecfm-srv)# continuity-check
interval 1s
Step 7
continuity-check loss-threshold threshold-value
Example:
(Optional) Set the interval at which continuity check
messages are sent. The available values are 100 ms,
1 second, 10 seconds, 1 minute and 10 minutes. The default
is 10 seconds.
Note
Because faster CCM rates are more CPU-intensive,
we do not recommend configuring a large number
of MEPs running at 100 ms intervals.
(Optional) Set the number of continuity check messages to
be missed before declaring that an MEP is down. The range
is 2 to 255; the default is 3.
Router(config-ecfm-srv)# continuity-check
loss-threshold 4
Step 8
alias{alias-short-ma-name | icc icc-code meg-id |
Define a customer alias maintenance association (MA)
number ma-number | vlan-id vlan-id | vpn-id vpn-id} name or number or VPN ID to be associated with the
domain, a VLAN ID or port MEP, and enter
ethernet-cfm-service configuration mode.
Example:
• alias-short-ma-name—a string of no more than 100
Router(config-ecfm-srv)# alias MA6
characters that identifies the MAID.
•
icc icc-code meg-id—specify the ITU Carrier Code
(ICC) (maximum: 6 characters) and Unique
Maintenance Entity Group (MEG) ID Code (UMC).
The maximum characters allowed is 12.
•
number ma-number—a value from 0 to 65535.
•
vlan-id vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
•
vpn-id vpn-id—enter a VPN ID as the ma-name.
Step 9
exit
Return to ethernet-CFM configuration mode.
Step 10
exit
Return to global configuration mode.
Step 11
interface interface-id
Specify an interface to configure, and enter interface
configuration mode.
Example:
Router(config)# interface gigabitethernet 0/4
Step 12
service instance number ethernet name
Specify the service instance number and the name of the
EVC.
Example:
Router(config-if)# service instance 30 ethernet
EVC30
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-9
Chapter 10
Step 13
Configuring Ethernet OAM
Command
Purpose
cfm mep domain domain-name mpid identifier
Configure maintenance end points for the domain, and
enter Ethernet cfm mep mode.
Example:
Router(config-if-srv)# cfm mep domain MD6 mpid
30
•
domain domain-name—Specify the name of the
created domain.
•
mpid identifier—Enter a maintenance end point
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
Step 14
end
Return to privileged EXEC mode.
Step 15
show ethernet cfm maintenance-points {local |
remote}
Verify the configuration.
Step 16
show ethernet cfm errors [configuration]
(Optional) Display the configuration error list.
Step 17
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Configuration Examples for Multi-UNI CFM MEPs
Example Configuration for Multi-UNI CFM MEPs in the same VPN
Router(config)# ethernet cfm ieee
Router(config)# ethernet cfm global
Router(config)# ethernet cfm domain MD6 level 6
Router(config-ecfm)# service MA6 evc evc30 vlan 30
Router(config-ecfm-srv)# continuity-check
Router(config-ecfm-srv)# continuity-check interval ls
Router(config-ecfm-srv)# service MA6_alias evc evc40 vlan 40
Router(config-ecfm-srv)# continuity-check
Router(config-ecfm-srv)# continuity-check interval ls
Router(config-ecfm-srv)# alias MA6
Router(config-ecfm-srv)# exit
Router(config-ecfm)# exit
Router(config)# ethernet evc EVC30
Router(config)# interface gigabitethernet 0/4
Router(config-if)# service instance 30 ethernet EVC30
Router(config-if-srv)# encapsulation dot1q 30
Router(config-if-srv)# bridge domain 30
Router(config-if-srv)# cfm mep domain MD6 mpid 30
Router(config-if-srv)# exit
Router(config-if)# exit
Router(config)# ethernet evc EVC40
Router(config)# interface gigabitethernet 0/5
Router(config-if)# service instance 30 ethernet EVC40
Router(config-if-srv)# encapsulation dot1q 30
Router(config-if-srv)# bridge domain 40
Router(config-if-srv)# cfm mep domain MD6 mpid 40
Router(config-if-srv)# exit
Router(config-if)# exit
Router(config)# interface gigabitethernet 0/6
Router(config-if)# service instance 30 ethernet
Router(config-if-srv)# encapsulation dot1q 100 second-dot1q 30
Router(config-if-srv)# rewrite ingress tag pop 1 symmetric
Router(config-if-srv)# bridge domain 30
Router(config-if-srv)# exit
Router(config-if)# exit
Router(config)# interface gigabitethernet 0/7
Router(config-if)# service instance 40 ethernet
Router(config-if-srv)# encapsulation dot1q 200 second-dot1q 30
Router(config-if-srv)# rewrite ingress tag pop 1 symmetric
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-10
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Router(config-if-srv)# bridge domain 40
Router(config-if-srv)# exit
Router(config-if)# exit
Verification
Use the following commands to verify a configuration:
•
Use the show ethernet cfm maintenance-point local command to verify the Multi-UNI CFMs over
EVC configuration. This command shows the basic configuration information for Multi-UNI CFM.
Router# show ethernet cfm maintenance-points local
Local MEPs:
-------------------------------------------------------------------------------MPID Domain Name
Lvl
MacAddress
Type CC
Ofld Domain Id
Dir
Port
Id
MA Name
SrvcInst
Source
EVC name
-------------------------------------------------------------------------------30
MD6
6
4055.3989.7868 BD-V Y
No
MD6
Up
Gi0/4
30
MA6
30
Static
evc30
40
MD6
6
4055.3989.7869 BD-V Y
No
MD6
Up
Gi0/5
40
MA6_alias (MA6)
40
Static
evc40
Total Local MEPs: 2
Local MIPs: None
•
Use the show ethernet cfm maintenance-point remote to verify the MEP configuration:
Router# show ethernet cfm maintenance-points remote
-------------------------------------------------------------------------------MPID Domain Name
MacAddress
IfSt PtSt
Lvl Domain ID
Ingress
RDI MA Name
Type Id
SrvcInst
EVC Name
Age
Local MEP Info
-------------------------------------------------------------------------------40
MD6
4055.3989.7869
Up
Up
6
MD6
Gi0/6
MA6
BD-V 30
30
evc30
0s
MPID: 30 Domain: MD6 MA: MA6
30
MD6
4055.3989.7868
Up
Up
6
MD6
Gi0/7
MA6_alias (MA6)
BD-V 40
40
evc40
1s
MPID: 40 Domain: MD6 MA: MA6_alias (MA6)
Total Remote MEPs: 2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-11
Chapter 10
Configuring Ethernet OAM
Configuring Ethernet CFM Crosscheck
Complete the following steps to configure Ethernet CFM crosscheck:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet cfm mep crosscheck start-delay delay
Configure the number of seconds that the device waits for
remote MEPs to come up before the crosscheck is started.
The range is 1 to 65535; the default is 30 seconds.
Step 3
ethernet cfm domain domain-name level level-id
Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 4
service {ma-name | ma-number | vpn-id vpn} {vlan
vlan-id}
Define a customer service maintenance association name
or number or VPN ID to be associated with the domain, and
a VLAN ID, and enter ethernet-cfm-service configuration
mode.
•
ma-name—a string of no more than 100 characters that
identifies the MAID.
•
ma-number—a value from 0 to 65535.
•
vpn-id vpn—enter a VPN ID as the ma-name.
•
vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
Step 5
mep mpid identifier
Define the MEP maintenance end point identifier in the
domain and service. The range is 1 to 8191
Step 6
end
Return to privileged EXEC mode.
Step 7
ethernet cfm mep crosscheck {enable | disable}
domain domain-name {vlan {vlan-id | any} | port}
Enable or disable CFM crosscheck for one or more VLANs
or a port MEP in the domain.
•
domain domain-name—Specify the name of the
created domain.
•
vlan {vlan-id | any}—Enter the service provider
VLAN ID or IDs as a VLAN-ID (1 to 4094), a range of
VLAN-IDs separated by a hyphen, or a series of
VLAN IDs separated by comma. Enter any for any
VLAN.
•
port—Identify a port MEP.
Step 8
show ethernet cfm maintenance-points remote
crosscheck
Verify the configuration.
Step 9
show ethernet cfm errors [configuration]
Enter this command after you enable CFM crosscheck to
display the results of the crosscheck operation. Enter the
configuration keyword to display the configuration error
list.
Step 10
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-12
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Note
Use the no form of each command to remove a configuration or to return to the default settings.
Configuring Static Remote MEP
Complete the following steps to configure Ethernet CFM static remote MEP:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet cfm domain domain-name level level-id
Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 3
service { short-ma-name | number MA-number |
vlan-id primary-vlan-id | vpn-id vpn-id } {vlan
vlan-id | port | evc evc-name }
Configure the maintenance association and set a
universally unique ID for a customer service instance (CSI)
or the maintenance association number value, primary
VLAN ID and VPN ID within a maintenance domain in
Ethernet connectivity fault management (CFM)
configuration mode.
Step 4
continuity-check
Enable sending and receiving of continuity check
messages.
Step 5
mep mpid identifier
Define the static remote maintenance end point identifier.
The range is 1 to 8191
Step 6
continuity-check static rmep
Enable checking of the incoming continuity check message
from a remote MEP that is configured in the MEP list.
Step 7
end
Return to privileged EXEC mode.
Step 8
show ethernet cfm maintenance-points remote
static
Verify the configuration.
Step 9
show ethernet cfm errors [configuration]
Enter this command after you enable CFM crosscheck to
display the results of the crosscheck operation. Enter the
configuration keyword to display the configuration error
list.
Step 10
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Note
Use the no form of each command to remove a configuration or to return to the default settings.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-13
Chapter 10
Configuring Ethernet OAM
Configuring a Port MEP
A port MEP is a down MEP that is not associated with a VLAN and that uses untagged frames to carry
CFM messages. You configure port MEPs on two connected interfaces. Port MEPs are always configured
at a lower domain level than native VLAN MEPs.
Complete the following steps to configure Ethernet CFM port MEPs:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet cfm domain domain-name level level-id
Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 3
service {ma-name | ma-number | vpn-id} port
Define a customer service maintenance association name
or number or VPN ID to be associated with the domain,
define a port MEP, and enter ethernet-cfm-service
configuration mode.
•
ma-name—a string of no more than 100 characters that
identifies the MAID.
•
ma-number—a value from 0 to 65535.
•
vpn-id vpn—enter a VPN ID as the ma-name.
Step 4
mep mpid identifier
Define the static remote maintenance end point identifier in
the domain and service. The range is 1 to 8191
Step 5
continuity-check
Enable sending and receiving of continuity check
messages.
Step 6
continuity-check interval value
(Optional) Set the interval at which continuity check
messages are sent. The available values are 100 ms,
1 second, 10 seconds, 1 minute and 10 minutes. The default
is 10 seconds.
Note
Because faster CCM rates are more CPU-intensive,
we do not recommend configuring a large number
of MEPs running at 100 ms intervals.
Step 7
continuity-check loss-threshold threshold-value
(Optional) Set the number of continuity check messages to
be missed before declaring that an MEP is down. The range
is 2 to 255; the default is 3.
Step 8
continuity-check static rmep
Enable checking of the incoming continuity check message
from a remote MEP that is configured in the MEP list.
Step 9
exit
Return to ethernet-cfm configuration mode.
Step 10
exit
Return to global configuration mode.
Step 11
interface interface-id
Identify the port MEP interface and enter interface
configuration mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-14
OL-23826-09
Chapter 10
Step 12
Configuring Ethernet OAM
Command
Purpose
ethernet cfm mep domain domain-name mpid
identifier port
Configure the interface as a port MEP for the domain.
•
domain domain-name—Specify the name of the
created domain.
•
mpid identifier—Enter a maintenance end point
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
Step 13
end
Return to privileged EXEC mode.
Step 14
show ethernet cfm maintenance-points remote
static
Verify the configuration.
Step 15
show ethernet cfm errors [configuration]
Enter this command after you enable CFM crosscheck to
display the results of the crosscheck operation. Enter the
configuration keyword to display the configuration error
list.
Step 16
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Note
Use the no form of each command to remove a configuration or to return to the default settings.
This is a sample configuration for a port MEP:
Router(config)# ethernet cfm domain abc level 3
Router(config-ecfm)# service PORTMEP port
Router(config-ecfm-srv)# mep mpid 222
Router(config-ecfm-srv)# continuity-check
Router(config-ecfm-srv)# continuity-check static rmep
Router(config-ecfm-srv)# exit
Router(config-ecfm)# exit
Router(config)# interface gigabitethernet 0/1
Router(config-if)# ethernet cfm mep domain abc mpid 111 port
Router(config-if)# end
Configuring SNMP Traps
To configure traps for Ethernet CFM, complete the following steps:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
snmp-server enable traps ethernet cfm cc [mep-up] (Optional) Enable Ethernet CFM continuity check traps.
[mep-down] [config] [loop] [cross-connect]
Step 3
snmp-server enable traps ethernet cfm crosscheck (Optional) Enable Ethernet CFM crosscheck traps.
[mep-unknown] [mep-missing] [service-up]
Step 4
end
Return to privileged EXEC mode.
Step 5
show running-config
Verify your entries.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-15
Chapter 10
Note
Configuring Ethernet OAM
Use the no form of each command to remove a configuration or to return to the default settings.
Configuring IP SLA CFM Operation
You can manually configure an individual IP SLA ethernet ping, or jitter echo operation, or you can
configure IP SLA ethernet operation with endpoint discovery. You can also configure multiple operation
scheduling. For accurate one-way delay statistics, the clocks on the endpoint switches must be
synchronized. You can configure the endpoint switches with Network Time Protocol (NTP) so that the
switches are synchronized to the same clock source.
For more information about configuring IP SLA ethernet operations, see the IP SLAs Configuration
Guide, Cisco IOS Release 15.0S. For detailed information about commands for IP SLAs, see the Cisco
IOS IP SLAs Command Reference.
Note
The Cisco ASR 901 does not necessarily support all of the commands listed in the Cisco IOS IP SLA
documentation.
This section includes these procedures:
•
Manually Configuring an IP SLA CFM Probe or Jitter Operation, page 10-16
•
Configuring an IP SLA Operation with Endpoint Discovery, page 10-18
Manually Configuring an IP SLA CFM Probe or Jitter Operation
To manually configure an IP SLA ethernet echo (ping) or jitter operation, complete the following steps:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip sla operation-number
Create an IP SLA operation, and enter IP SLA
configuration mode.
Step 3
ethernet echo mpid identifier domain domain-name Configure the IP SLA operation as an echo (ping) or jitter
operation, and enter IP SLA ethernet echo configuration
vlan vlan-id
mode.
or
ethernet jitter mpid identifier domain domain-name • Enter echo for a ping operation or jitter for a jitter
operation.
vlan vlan-id [interval interpacket-interval]
[num-frames number-of frames transmitted]
•
For mpid identifier, enter a maintenance endpoint
identifier. The identifier must be unique for each
VLAN (service instance). The range is 1 to 8191.
•
For domain domain-name, enter the CFM domain
name.
•
For vlan vlan-id, the VLAN range is from 1 to 4095.
•
(Optional—for jitter only) Enter the interval between
sending of jitter packets.
•
(Optional—for jitter only) Enter the num-frames and
the number of frames to be sent.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-16
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Command
Purpose
Step 4
cos cos-value
(Optional) Set a class of service value for the operation.
Step 5
frequency seconds
(Optional) Set the rate at which the IP SLA operation
repeats. The range is from 1 to 604800 seconds; the default
is 60 seconds.
Step 6
history history-parameter
(Optional) Specify parameters for gathering statistical
history information for the IP SLA operation.
Step 7
owner owner-id
(Optional) Configure the SNMP owner of the IP SLA
operation.
Step 8
request-data-size bytes
(Optional) Specify the protocol data size for an IP SLA
request packet. The range is from 0 to the maximum size
allowed by the protocol being used; the default is 66 bytes.
Step 9
tag text
(Optional) Create a user-specified identifier for an IP SLA
operation.
Step 10
threshold milliseconds
(Optional) Specify the upper threshold value in
milliseconds (ms0 for calculating network monitoring
statistics. The range is 0 to 2147483647; the default is
5000.
Step 11
timeout milliseconds
(Optional) Specify the amount of time in ms that the IP
SLA operation waits for a response from its request packet.
The range is 0 to 604800000; the default value is 5000.
Step 12
exit
Return to global configuration mode.
Step 13
ip sla schedule operation-number [ageout seconds]
[life {forever | seconds}] [recurring] [start-time
{hh:mm {:ss} [month day | day month] | pending |
now | after hh:mm:ss}]
Schedule the time parameters for the IP SLA operation.
•
operation-number—Enter the IP SLA operation
number.
•
(Optional) ageout seconds—Enter the number of
seconds to keep the operation in memory when it is not
actively collecting information. The range is 0 to
2073600 seconds. The default is 0 seconds.
•
(Optional) life—Set the operation to run indefinitely
(forever) or for a specific number of seconds. The
range is from 0 to 2147483647. The default is 3600
seconds (1 hour)
•
(Optional) recurring—Set the probe to be
automatically scheduled every day.
•
(Optional) start-time—Enter the time for the
operation to begin collecting information:
– To start at a specific time, enter the hour, minute,
second (in 24-hour notation), and day of the
month.
– Enter pending to select no information collection
until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to show that the operation
should start after the entered time has elapsed.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-17
Chapter 10
Configuring Ethernet OAM
Command
Purpose
Step 14
end
Return to privileged EXEC mode.
Step 15
show ip sla configuration [operation-number]
Show the configured IP SLA operation.
Step 16
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To remove an IP SLA operation, enter the no ip sla operation-number global configuration command.
Configuring an IP SLA Operation with Endpoint Discovery
To automatically discover the CFM endpoints for a domain and VLAN ID, using IP SLAs, complete the
steps given below. You can configure ping or jitter operations to the discovered endpoints.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ip sla ethernet-monitor operation-number
Begin configuration of an IP SLA automatic ethernet
operation, and enter IP SLA ethernet monitor configuration
mode.
Step 3
type echo domain domain-name vlan vlan-id
[exclude-mpids mp-ids]
Configure the automatic Ethernet operation to create echo
(ping) or jitter operation and enter IP SLA ethernet echo
configuration mode.
or
type jitter domain domain-name vlan vlan-id
[exclude-mpids mp-ids] [interval
interpacket-interval] [num-frames number-of frames
transmitted]
Step 4
cos cos-value
•
Enter type echo for a ping operation or type jitter for
a jitter operation.
•
For mpid identifier, enter a maintenance endpoint
identifier. The range is 1 to 8191.
•
For domain domain-name, enter the CFM domain
name.
•
For vlan vlan-id, the VLAN range is from 1 to 4095.
•
(Optional) Enter exclude-mpids mp-ids to exclude the
specified maintenance endpoint identifiers.
•
(Optional—for jitter only) Enter the interval between
sending of jitter packets.
•
(Optional—for jitter only) Enter the num-frames and
the number of frames to be sent.
(Optional) Set a class of service value for the operation.
Before configuring the cos parameter, you must globally
enable QoS by entering the mls qos global configuration
command.
Step 5
owner owner-id
(Optional) Configure the SNMP owner of the IP SLA
operation.
Step 6
request-data-size bytes
(Optional) Specify the protocol data size for an IP SLA
request packet. The range is from 0 to the maximum size
allowed by the protocol being used; the default is 66 bytes.
Step 7
tag text
(Optional) Create a user-specified identifier for an IP SLA
operation.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-18
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Command
Purpose
Step 8
threshold milliseconds
(Optional) Specify the upper threshold value in
milliseconds for calculating network monitoring statistics.
The range is 0 to 2147483647; the default is 5000.
Step 9
timeout milliseconds
(Optional) Specify the amount of time in milliseconds that
the IP SLA operation waits for a response from its request
packet. The range is 0 to 604800000; the default value is
5000.
Step 10
exit
Return to global configuration mode.
Step 11
ip sla schedule operation-number [ageout seconds]
[life {forever | seconds}] [recurring] [start-time
{hh:mm {:ss} [month day | day month] | pending |
now | after hh:mm:ss}]
Schedule the time parameters for the IP SLA operation.
•
operation-number—Enter the IP SLA operation
number.
•
(Optional) ageout seconds—Enter the number of
seconds to keep the operation in memory when it is not
actively collecting information. The range is 0 to
2073600 seconds. The default is 0 seconds.
•
(Optional) life—Set the operation to run indefinitely
(forever) or for a specific number of seconds. The
range is from 0 to 2147483647. The default is 3600
seconds (1 hour)
•
(Optional) recurring—Set the probe to be
automatically scheduled every day.
•
(Optional) start-time—Enter the time for the
operation to begin collecting information:
– To start at a specific time, enter the hour, minute,
second (in 24-hour notation), and day of the
month.
– Enter pending to select no information collection
until a start time is selected.
– Enter now to start the operation immediately.
– Enter after hh:mm:ss to show that the operation
should start after the entered time has elapsed.
Step 12
end
Return to privileged EXEC mode.
Step 13
show ip sla configuration [operation-number]
Show the configured IP SLA operation.
Step 14
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To remove an IP SLA operation, enter the no ip sla operation-number global configuration command.
Configuring CFM over EFP with Cross Connect
The CFM over EFP Interface with cross connect feature allows you to:
•
Forward continuity check messages (CCM) towards the core over cross connect pseudowires.
To know more about pseudowires, see
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-19
Chapter 10
Configuring Ethernet OAM
•
Receive CFM messages from the core.
•
Forward CFM messages to the access side (after Continuity Check Database [CCDB] based on
maintenance point [MP] filtering rules).
This section contains the following topics:
•
Configuring CFM over EFP Interface with Cross Connect, page 10-20
•
Configuring CFM over EFP Interface with Cross Connect—Port Channel-Based Cross Connect
Tunnel, page 10-22
Configuring CFM over EFP Interface with Cross Connect
To configure CFM over EFP Interface with cross connect, complete the following steps.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router# enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
pseudowire-class [pw-class-name]
Specifies the name of a Layer 2 pseudowire class and
enter pseudowire class configuration mode.
Example:
Router(config)# pseudowire-class
vlan-xconnect
Step 4
encapsulation mpls
Example:
Specifies that Multiprotocol Label Switching (MPLS) is
used as the data encapsulation method for tunneling
Layer 2 traffic over the pseudowire.
Router(config-if)# encapsulation mpls
Step 5
exit
Exits the pseudowire class configuration mode.
Example:
Router(config-if-srv)# exit
Step 6
interface gigabitethernet slot/port or
interface tengigabitethernet slot/port
Specifies the Gigabit Ethernet or the Ten Gigabit
Ethernet interface to configure.
Example:
Router(config-if-srv)# interface
Gi2/0/2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-20
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Step 7
Command
Purpose
service instance id ethernet [service-name]
Creates a service instance (an instantiation of an EVC)
on an interface and sets the device into the config-if-srv
submode.
Example:
Router(config-if-srv)# service instance 101 ethernet
Step 8
encapsulation untagged | dot1q vlan-id
| default
Example:
Router(config-if-srv)# encapsulation
dot1q 100
Configures the encapsulation. Defines the matching
criteria that maps the ingress dot1q or untagged frames
on an interface for the appropriate service instance.
Effective with Cisco IOS Release 15.3(2)S, default
encapsulation is supported.
Note
Step 9
xconnect peer-ip-address vc-id {encapsulation {l2tpv3 [manual] | mpls [manual]} | pw-class pw-class-name
}[pw-class pw-class-name] [sequencing
{transmit | receive | both}]
dot1q range and second-dot1q are not supported
for EFP Interface with Cross Connect.
Binds an attachment circuit to a pseudowire, and
configures an Any Transport over MPLS (AToM) static
pseudowire.
Example:
Router(config-if-srv)# xconnect
10.0.3.201 123 pw-class vlan-xconnect
Step 10
cfm mep domain domain-name [up | down]
mpid mpid-value [cos cos-value]
Configures a maintenance endpoint (MEP) for a domain.
Example:
Router(config-if-srv)# cfm mep down
mpid 100 domain Core
Step 11
Exits the interface configuration mode.
exit
Example:
Router(config-if-srv)# exit
Examples
This example shows how to configure CFM over EVC using cross connect.
ASR901(config)#ethernet cfm ieee
ASR901(config)#ethernet cfm global
ASR901(config)#ethernet cfm domain L5 level 5
ASR901(config-ecfm)# service s1 evc e711
ASR901(config-ecfm-srv)# continuity-check
ASR901(config-ecfm-srv)#exit
ASR901(config-ecfm)#exit
Example for untagged Encapsulation
ASR901(config)#int g0/1
ASR901(config-if)#service instance 711 ethernet e711
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-21
Chapter 10
Configuring Ethernet OAM
ASR901(config-if-srv)#encapsulation untagged
ASR901(config-if-srv)# xconnect 3.3.3.3 3 encapsulation mpls
ASR901(cfg-if-ether-vc-xconn)#
mtu 1500
ASR901(cfg-if-ether-vc-xconn)# cfm mep domain L5 mpid 511
Example for single tag Encapsulation
ASR901(config)#int g0/1
ASR901(config-if)#service instance 711 ethernet e711
ASR901(config-if-srv)# encapsulation dot1q 711
ASR901(config-if-srv)# xconnect 3.3.3.3 3 encapsulation mpls
ASR901(cfg-if-ether-vc-xconn)#
mtu 1500
ASR901(cfg-if-ether-vc-xconn)# cfm mep domain L5 mpid 511
Configuring CFM over EFP Interface with Cross Connect—Port Channel-Based Cross Connect
Tunnel
This section describes how to configure CFM over EFP Interface with Port Channel-Based cross connect
Tunnel.
Examples
This example shows how to configure CFM over EFP Interface with Port Channel-Based cross connect
Tunnel:
ASR901(config)#ethernet cfm ieee
ASR901(config)#ethernet cfm global
ASR901(config)#ethernet cfm domain L5 level 5
ASR901(config-ecfm)# service s1 evc e711
ASR901(config-ecfm-srv)# continuity-check
ASR901(config-ecfm-srv)#exit
ASR901(config-ecfm)#exit
ASR901(config)#interface GigabitEthernet0/1
ASR901(config-if)# negotiation auto
ASR901(config-if)# no keepalive
ASR901(config-if)# channel-group 1 mode on
ASR901(config-if)#exit
ASR901(config)#interface GigabitEthernet0/7
ASR901(config-if)# negotiation auto
ASR901(config-if)# channel-group 1 mode on
ASR901(config-if)#exit
ASR901(config)#int port-channel 1
ASR901(config-if)#service instance 711 ethernet e711
ASR901(config-if-srv)# encapsulation dot1q 711
ASR901(config-if-srv)# xconnect 3.3.3.3 3 encapsulation mpls
ASR901(cfg-if-ether-vc-xconn)#
mtu 1500
ASR901(cfg-if-ether-vc-xconn)# cfm mep domain L5 mpid 511
Verification
Use the following commands to verify a configuration:
•
Use the show ethernet cfm maintenance-point local commands to verify the CFM over EVC
configuration. This command shows the basic configuration information for CFM.
Router-30-PE1#show ethernet cfm maintenance-point local
Local MEPs:
-------------------------------------------------------------------------------MPID Domain Name
Lvl
MacAddress
Type CC
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-22
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Domain Id
Dir
Port
Id
MA Name
SrvcInst
EVC name
-------------------------------------------------------------------------------1
L6
6
000a.f393.56d0 XCON Y
L6
Down Gi0/2 N/A
bbb
1
bbb
3
L5
5
0007.8478.4410 XCON Y
L5
Up
Gi0/2 N/A
bbb
1
bbb
Total Local MEPs: 2
Local MIPs:
* = MIP Manually Configured
-------------------------------------------------------------------------------Level Port
MacAddress
SrvcInst
Type
Id
-------------------------------------------------------------------------------7
Gi0/2 0007.8478.4410 1
XCON
N/A
Total Local MIPs: 1
•
Use the show ethernet cfm maintenance-point remote to verify the MEP configuration:
Router-30-PE1#show ethernet cfm maintenance-point remote
-------------------------------------------------------------------------------MPID Domain Name
MacAddress
IfSt PtSt
Lvl Domain ID
Ingress
RDI MA Name
Type Id
SrvcInst
EVC Name
Age
-------------------------------------------------------------------------------4
L5
000a.f393.56d0
Up
Up
5
L5
Te2/0/0:(2.2.2.2, 1)
bbb
XCON N/A
1
bbb
9s
2
L6
000a.f393.56d0
Up
Up
6
L6
Te2/0/0:(2.2.2.2, 1)
bbb
XCON N/A
1
bbb
1s
Total Remote MEPs: 2
•
Use the show ethernet cfm mpdb command to verify the catalouge of CC with MIP in intermediate
routers.
PE2#show ethernet cfm mpdb
* = Can Ping/Traceroute to MEP
-------------------------------------------------------------------------------MPID Domain Name
MacAddress
Version
Lvl
Domain ID
Ingress
Expd MA Name
Type Id
SrvcInst
EVC Name
Age
-------------------------------------------------------------------------------600 * L6
0021.d8ca.d7d0
IEEE-CFM
6
L6
Te2/1:(2.2.2.2, 1)
s1
XCON N/A
1
1
2s
700
L7
001f.cab7.fd01
IEEE-CFM
7
L7
Te2/1:(2.2.2.2, 1)
s1
XCON N/A
1
1
3s
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-23
Chapter 10
Configuring Ethernet OAM
Total Remote MEPs: 2
•
Use show ethernet cfm error command to view the error report:
PE2#show ethernet cfm error
-------------------------------------------------------------------------------MPID Domain Id
Mac Address
Type
Id Lvl
MAName
Reason
Age
-------------------------------------------------------------------------------- L3
001d.45fe.ca81 BD-V
200 3
s2
Receive AIS
8s
PE2#
Configuring CFM with EVC Default Encapsulation
Complete the following steps to configure CFM with EVC default encapsulation:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
service instance instance-id ethernet evc-name
5.
encapsulation default
6.
bridge-domain bridge-id
7.
cfm encapsulation {dot1ad vlan-id | dot1q vlan-id} [dot1q vlan-id | second-dot1q vlan-id]
8.
cfm mep domain domain-name mpid mpid-value
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface type number
Specifies an interface type and number, and enters interface
configuration mode.
Example:
Router(config)# interface GigabitEthernet0/9
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-24
OL-23826-09
Chapter 10
Step 4
Configuring Ethernet OAM
Command or Action
Purpose
service instance instance-id ethernet evc-name
Creates a service instance on an interface and defines the
matching criteria.
Example:
•
instance-id—Integer that uniquely identifies a service
instance on an interface.
•
evc-name—String that associates an EVC to the service
instance. Maximum byte size is 100.
Router(config-if)# service instance 1 ethernet
evc100
Step 5
Configures the default service instance.
encapsulation default
Example:
Router(config-if-srv)# encapsulation default
Step 6
Binds the service instance to a bridge domain instance using
an identifier.
bridge-domain bridge-id
Example:
Router(config-if-srv)# bridge-domain 99
Step 7
cfm encapsulation {dot1ad vlan-id | dot1q
vlan-id} [dot1q vlan-id | second-dot1q vlan-id]
Configures connectivity fault management (CFM) Ethernet
frame encapsulation.
•
dot1ad—Indicates the 802.1ad provider bridges
encapsulation type.
•
dot1q—Supports the IEEE 802.1q standard for
encapsulation of traffic and specifies the outer dot1q
encapsulation tag.
•
second-dot1q—Specifies the inner dot1q
encapsulation tag. Valid option only when you first
select the outer dot1q encapsulation tag. When the
dot1ad encapsulation type is selected first, dot1q is a
valid option.
•
vlan-id—Integer from 1 to 4094 that specifies the
VLAN on which to send CFM frames.
Example:
Router(config-if-srv)# cfm encapsulation dot1q
75
Step 8
cfm mep domain domain-id mpid mpid-value
Configures a maintenance endpoint (MEP) for a domain.
•
domain-name—String from 1 to 154 characters that
identifies the domain name.
•
mpid—Indicates the maintenance point ID (MPID).
•
mpid-value—Integer from 1 to 8191 that identifies the
MPID.
Example:
Router(config-if-srv)# cfm mep domain md2 mpid
111
Verifying CFM with EVC Default Encapsulation
To verify the configuration of CFM with EVC default encapsulation, use the show command shown
below.
Router# show running-config interface gigabitEthernet 0/9
Building configuration...
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-25
Chapter 10
Configuring Ethernet OAM
Current configuration : 210 bytes
!
interface GigabitEthernet0/9
no ip address
negotiation auto
service instance 1 ethernet evc100
encapsulation default
bridge-domain 99
cfm mep domain md2 mpid 111
cfm encapsulation dot1q 75
!
end
Example: Configuring CFM with EVC Default Encapsulation
!
interface GigabitEthernet0/9
service instance 1 ethernet evc100
encapsulation default
bridge-domain 99
cfm encapsulation dot1q 75
cfm mep domain md2 mpid 111
!
Configuring Y.1731 Fault Management
The ITU-T Y.1731 feature provides new CFM functionality for fault and performance management for
service providers in large network. The router supports Ethernet Alarm Indication Signal (ETH-AIS) and
Ethernet Remote Defect Indication (ETH-RDI) functionality for fault detection, verification, and
isolation.
For more information on Y.1731 Fault Management, see
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_cfm-ieee_y1731.html
To configure Y.1731 fault management, you must enable CFM and configure MIPs on the participating
interfaces. AIS messages are generated only on interfaces with a configured MIP.
This section contains the following topics:
•
Default Y.1731 Configuration, page 10-26
•
Configuring ETH-AIS, page 10-27
•
Configuring ETH-LCK, page 10-28
Default Y.1731 Configuration
•
ETH-AIS is enabled by default when CFM is enabled.
•
When you configure ETH-AIS, you must configure CFM before ETH-AIS is operational.
•
ETH-RDI is set automatically when continuity check messages are enabled.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-26
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Configuring ETH-AIS
Complete the following steps to configure ETH- AIS on the router:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet cfm ais link-status global
Configure AIS-specific SMEP commands by entering
config-ais-link-cfm mode.
Step 3
level level-id
Configure the maintenance level for sending AIS frames
transmitted by the SMEP. The range is 0 to 7.
or
or
disable
Disable generation of ETH-AIS frames.
Step 4
period value
Configure the SMEP AIS transmission period interval.
Allowable values are 1 second or 60 seconds.
Step 5
exit
Return to global configuration mode.
Step 6
ethernet cfm domain domain-name level level-id
Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Step 7
service { short-ma-name | number MA-number |
vlan-id primary-vlan-id | vpn-id vpn-id } {vlan
vlan-id | port | evc evc-name }
Configure the maintenance association and set a
universally unique ID for a customer service instance (CSI)
or the maintenance association number value, primary
VLAN ID and VPN ID within a maintenance domain in
Ethernet connectivity fault management (CFM)
configuration mode.
Step 8
ais level level-id
(Optional) Configure the maintenance level for sending
AIS frames transmitted by the MEP. The range is 0 to 7.
Step 9
ais period value
(Optional) Configure the MEP AIS transmission period
interval. Allowable values are 1 second or 60 seconds.
Step 10
ais expiry-threshold value
(Optional) Set the expiring threshold for the MA as an
integer. The range is 2 to 255. The default is 3.5.
Step 11
no ais suppress-alarms
(Optional) Override the suppression of redundant alarms
when the MEP goes into an AIS defect condition after
receiving an AIS message.
Step 12
exit
Return to ethernet-cfm configuration mode.
Step 13
exit
Return to global configuration mode.
Step 14
interface interface-id
Specify an interface ID, and enter interface configuration
mode.
Step 15
[no] ethernet cfm ais link-status
Enable or disable sending AIS frames from the SMEP on
the interface.
Step 16
ethernet cfm ais link-status period value
Configure the ETH-AIS transmission period generated by
the SMEP on the interface. Allowable values are 1 second
or 60 seconds.
Step 17
ethernet cfm ais link-status level level-id
Configure the maintenance level for sending AIS frames
transmitted by the SMEP on the interface. The range is 0 to
7.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-27
Chapter 10
Configuring Ethernet OAM
Command
Purpose
Step 18
end
Return to privileged EXEC mode.
Step 19
show ethernet cfm smep [interface interface-id]
Verify the configuration.
Step 20
show ethernet cfm error
Display received ETH-AIS frames and other errors.
Step 21
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use the no form of this commands to return to the default configuration or to remove a configuration.
To disable the generation of ETH-AIS frames, enter the disable config-ais-link-cfm mode command.
This is an example of the output from the show ethernet cfm smep command when Ethernet AIS has
been enabled:
Router# show ethernet cfm smep
SMEP Settings:
-------------Interface: GigabitEthernet1/0/3
LCK-Status: Enabled
LCK Period: 60000 (ms)
Level to transmit LCK: Default
AIS-Status: Enabled
AIS Period: 60000 (ms)
Level to transmit AIS: Default
Defect Condition: AIS
Configuring ETH-LCK
Complete the following steps to configure ethernet locked signal on a switch:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet cfm lck link-status global
Execute SMEP LCK commands by entering
config-lck-link-cfm mode.
Step 3
level level-id
Configure the maintenance level for sending ETH-LCK
frames transmitted by the SMEP. The range is 0 to 7.
or
or
disable
Disable the generation of ETH-LCK frames.
Step 4
period value
Configure the SMEP ETH-LCK frame transmission period
interval. Allowable values are 1 second or 60 seconds.
Step 5
exit
Return to global configuration mode.
Step 6
ethernet cfm domain domain-name level level-id
Define a CFM domain, set the domain level, and enter
ethernet-cfm configuration mode for the domain. The
maintenance level number range is 0 to 7.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-28
OL-23826-09
Chapter 10
Step 7
Configuring Ethernet OAM
Command
Purpose
service {ma-name | ma-number | vpn-id vpn} {vlan
vlan-id [direction down] | port}
Define a customer service maintenance association name
or number to be associated with the domain, or a VLAN ID
or VPN-ID, and enter ethernet-cfm-service configuration
mode.
•
ma-name—a string of no more than 100 characters that
identifies the MAID.
•
ma-number—a value from 0 to 65535.
•
vpn-id—enter a VPN ID as the ma-name.
•
vlan vlan-id—VLAN range is from 1 to 4094. You
cannot use the same VLAN ID for more than one
domain at the same level.
•
(Optional) direction down—specify the service
direction as down.
•
port—Configure port MEP, a down MEP that is
untagged and not associated with a VLAN.
Step 8
lck level level-id
(Optional) Configure the maintenance level for sending
ETH-LCK frames sent by the MEP. The range is 0 to 7.
Step 9
lck period value
(Optional) Configure the MEP ETH-LCK frame
transmission period interval. Allowable values are 1 second
or 60 seconds.
Step 10
lck expiry-threshold value
(Optional) Set the expiring threshold for the MA. The
range is 2 to 255. The default is 3.5.
Step 11
exit
Return to ethernet-cfm configuration mode.
Step 12
exit
Return to global configuration mode.
Step 13
interface interface-id
Specify an interface ID, and enter interface configuration
mode.
Step 14
[no] ethernet cfm lck link-status
Enable or disable sending ETH-LCK frames from the
SMEP on the interface.
Step 15
ethernet cfm lck link-status period value
Configure the ETH-LCK transmission period generated by
the SMEP on the interface. Allowable values are 1 second
or 60 seconds.
Step 16
ethernet cfm lck link-status level level-id
Configure the maintenance level for sending ETH-LCK
frames sent by the SMEP on the interface. The range is 0 to
7.
Step 17
end
Return to privileged EXEC mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-29
Chapter 10
Step 18
Configuring Ethernet OAM
Command
Purpose
ethernet cfm lck start interface interface-id
direction {up | down} [drop l2-bpdu]
(Optional) Apply the LCK condition to an interface.
•
interface interface-id—Specify the interface to be put
in LCK condition.
•
direction inward—The LCK is in the direction toward
the relay; that is, within the switch.
•
direction outward—The LCK is in the direction of
the wire.
•
(Optional) drop l2-bpdu specifies that all Layer 2
BPDUs except CFM frames, all data frames, and all
Layer 3 control traffic are dropped for that MEP. If not
entered, only data frames and Layer 3 control frames
are dropped.
Step 19
show ethernet cfm smep [interface interface-id]
Verify the configuration.
Step 20
show ethernet cfm error
Display received ETH-LCK frames.
Step 21
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To remove the LCK condition from MEP, enter the ethernet cfm lck stop mpid local-mpid domain
domain-name vlan vlan-id privileged EXEC command. To put an interface out of LCK condition, enter
the ethernet cfm lck start interface interface-id direction {inward | outward} privileged EXEC
command.
This is an example of the output from the show ethernet cfm smep command when ethernet LCK has
been enabled:
Switch# show ethernet cfm smep
SMEP Settings:
-------------Interface: GigabitEthernet0/3
LCK-Status: Enabled
LCK Period: 60000 (ms)
Level to transmit LCK: Default
AIS-Status: Enabled
AIS Period: 60000 (ms)
Level to transmit AIS: Default
Defect Condition: AIS
Managing and Displaying Ethernet CFM Information
Use the following commands in the privileged EXEC mode to clear Ethernet CFM information.
Table 1
Clearing CFM Information
Command
Purpose
clear ethernet cfm ais domain domain-name
mpid id {vlan vlan-id | port}
Clear MEPs with matching domain and VLAN ID out of AIS defect
condition.
clear ethernet cfm ais link-status interface
interface-id
Clear a SMEP out of AIS defect condition.
clear ethernet cfm error
Clear all CFM error conditions, including AIS.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-30
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Use the commands in Table 10-2 in the privileged EXEC mode to display Ethernet CFM information.
Table 10-2
Displaying CFM Information
Command
Purpose
show ethernet cfm domain [brief]
Displays CFM domain information or brief domain information.
show ethernet cfm errors [configuration |
domain-id]
Displays CFM continuity check error conditions logged on a device since
it was last reset or the log was last cleared. When CFM crosscheck is
enabled, displays the results of the CFM crosscheck operation.
show ethernet cfm maintenance-points local
[detail | domain | interface | level | mep | mip]
Displays maintenance points configured on a device.
show ethernet cfm maintenance-points remote Displays information about a remote maintenance point domains or levels or
[crosscheck | detail | domain | static]
details in the CFM database.
show ethernet cfm mpdb
Displays information about entries in the MIP continuity-check database.
show ethernet cfm smep [interface
interface-id]
Displays Ethernet CFM SMEP information.
show ethernet cfm traceroute-cache
Displays the contents of the traceroute cache.
show platform cfm
Displays platform-independent CFM information.
This is an example of output from the show ethernet cfm domain brief command:
Router# show ethernet cfm domain brief
Domain Name
level5
level3
test
name
test1
lck
Index Level Services Archive(min)
1
5
1
100
2
3
1
100
3
3
3
100
4
3
1
100
5
2
1
100
6
1
1
100Total Services : 1
This is an example of output from the show ethernet cfm errors command:
Router# show ethernet cfm errors
-------------------------------------------------------------------------------MPID Domain Id
Mac Address
Type
Id Lvl
MAName
Reason
Age
-------------------------------------------------------------------------------6307 level3
0021.d7ee.fe80 Vlan
7
3
vlan7
Receive RDI
5s
This is an example of output from the show ethernet cfm maintenance-points local detail command:
Router# show ethernet cfm maintenance-points local detail
Local MEPs:
---------MPID: 7307
DomainName: level3
Level: 3
Direction: Up
Vlan: 7
Interface: Gi0/3
CC-Status: Enabled
CC Loss Threshold: 3
MAC: 0021.d7ef.0700
LCK-Status: Enabled
LCK Period: 60000(ms)
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-31
Chapter 10
Configuring Ethernet OAM
LCK Expiry Threshold: 3.5
Level to transmit LCK: Default
Defect Condition: No Defect
presentRDI: FALSE
AIS-Status: Enabled
AIS Period: 60000(ms)
AIS Expiry Threshold: 3.5
Level to transmit AIS: Default
Suppress Alarm configuration: Enabled
Suppressing Alarms: No
MIP Settings:
------------Local MIPs:
* = MIP Manually Configured
-----------------------------------------------------------------------------Level Port
MacAddress
SrvcInst
Type
Id
-----------------------------------------------------------------------------*5
Gi0/3
0021.d7ef.0700 N/A
Vlan
2,7
This is an example of output from the show ethernet cfm traceroute command:
Router# show ethernet cfm traceroute
Current Cache-size: 0 Hops
Max Cache-size: 100 Hops
Hold-time: 100 Minutes
Use the commands in Table 10-3 in the privileged EXEC mode to display IP SLA ethernet CFM
information.
Table 10-3
Displaying IP SLA CFM Information
Command
Purpose
show ip sla configuration [entry-number]
Displays configuration values including all defaults for all IP SLA
operations or a specific operation.
show ip sla ethernet-monitor configuration
[entry-number]
Displays the configuration of the IP SLA automatic ethernet operation.
show ip sla statistics [entry-number |
aggregated | details]
Display current or aggregated operational status and statistics.
Understanding the Ethernet OAM Protocol
The Ethernet OAM protocol for installing, monitoring, and troubleshooting Metro Ethernet networks
and Ethernet WANs relies on an optional sublayer in the data link layer of the OSI model. Normal link
operation does not require Ethernet OAM. You can implement Ethernet OAM on any full-duplex
point-to-point or emulated point-to-point Ethernet link for a network or part of a network (specified
interfaces).
OAM frames, called OAM protocol data units (OAM PDUs) use the slow protocol destination MAC
address 0180.c200.0002. They are intercepted by the MAC sublayer and cannot propagate beyond a
single hop within an Ethernet network. Ethernet OAM is a relatively slow protocol, with a maximum
transmission rate of 10 frames per second, resulting in minor impact to normal operations. However,
when you enable link monitoring, because the CPU must poll error counters frequently, the number of
required CPU cycles is proportional to the number of interfaces that must be polled.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-32
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Ethernet OAM has two major components:
•
The OAM client establishes and manages Ethernet OAM on a link and enables and configures the
OAM sublayer. During the OAM discovery phase, the OAM client monitors OAM PDUs received
from the remote peer and enables OAM functionality. After the discovery phase, it manages the rules
of response to OAM PDUs and the OAM remote loopback mode.
•
The OAM sublayer presents two standard IEEE 802.3 MAC service interfaces facing the superior
and inferior MAC sublayers. It provides a dedicated interface for the OAM client to pass OAM
control information and PDUs to and from the client. It includes these components:
– The control block provides the interface between the OAM client and other OAM sublayer
internal blocks.
– The multiplexer manages frames from the MAC client, the control block, and the parser and
passes OAM PDUs from the control block and loopback frames from the parser to the
subordinate layer.
– The parser classifies frames as OAM PDUs, MAC client frames, or loopback frames and sends
them to the appropriate entity: OAM PDUs to the control block, MAC client frames to the
superior sublayer, and loopback frames to the multiplexer.
Benefits of Ethernet OAM
Ethernet OAM provides the following benefits:
•
Competitive advantage for service providers
•
Standardized mechanism to monitor the health of a link and perform diagnostics
OAM Features
The following OAM features are defined by IEEE 802.3ah:
•
Discovery
•
Link Monitoring
•
Remote Failure Indication
•
Remote Loopback
Discovery
Discovery is the first phase of Ethernet OAM and it identifies the devices in the network and their OAM
capabilities. Discovery uses information OAM PDUs. During the discovery phase, the following
information is advertised within periodic information OAM PDUs:
•
OAM mode—Conveyed to the remote OAM entity. The mode can be either active or passive and can
be used to determine device functionality.
•
OAM configuration (capabilities)—Advertises the capabilities of the local OAM entity. With this
information a peer can determine what functions are supported and accessible; for example,
loopback capability.
•
OAM PDU configuration—Includes the maximum OAM PDU size for receipt and delivery. This
information along with the rate limiting of 10 frames per second can be used to limit the bandwidth
allocated to OAM traffic.
•
Platform identity—A combination of an organization unique identifier (OUI) and 32-bits of
vendor-specific information. OUI allocation, controlled by the IEEE, is typically the first three bytes
of a MAC address.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-33
Chapter 10
Configuring Ethernet OAM
Discovery includes an optional phase in which the local station can accept or reject the configuration of
the peer OAM entity. For example, a node may require that its partner support loopback capability to be
accepted into the management network. These policy decisions may be implemented as vendor-specific
extensions.
Link Monitoring
Link monitoring in Ethernet OAM detects and indicates link faults under a variety of conditions. Link
monitoring uses the event notification OAM PDU and sends events to the remote OAM entity when there
are problems detected on the link. The error events include the following:
•
Error Symbol Period (error symbols per second)—The number of symbol errors that occurred
during a specified period exceeded a threshold. These errors are coding symbol errors.
•
Error Frame (error frames per second)—The number of frame errors detected during a specified
period exceeded a threshold.
•
Error Frame Period (error frames per n frames)—The number of frame errors within the last n
frames has exceeded a threshold.
•
Error Frame Seconds Summary (error seconds per m seconds)—The number of error seconds
(1-second intervals with at least one frame error) within the last m seconds has exceeded a threshold.
Since IEEE 802.3ah OAM does not provide a guaranteed delivery of any OAM PDU, the event
notification OAM PDU may be sent multiple times to reduce the probability of a lost notification. A
sequence number is used to recognize duplicate events.
Remote Failure Indication
Faults in Ethernet connectivity that are caused by slowly deteriorating quality are difficult to detect.
Ethernet OAM provides a mechanism for an OAM entity to convey these failure conditions to its peer
via specific flags in the OAM PDU. The following failure conditions can be communicated:
•
Link Fault—Loss of signal is detected by the receiver; for instance, the peer's laser is
malfunctioning. A link fault is sent once per second in the information OAM PDU. Link fault applies
only when the physical sublayer is capable of independently transmitting and receiving signals.
•
Dying Gasp—This notification is sent for power failure, link down, router reload and link
administratively down conditions. This type of condition is vendor specific. A notification about the
condition may be sent immediately and continuously.
•
Critical Event—An unspecified critical event occurs. This type of event is vendor specific. A critical
event may be sent immediately and continuously.
Remote Loopback
An OAM entity can put its remote peer into loopback mode using the loopback control OAM PDU.
Loopback mode helps an administrator ensure the quality of links during installation or when
troubleshooting. In loopback mode, every frame received is transmitted back on the same port except for
OAM PDUs and pause frames. The periodic exchange of OAM PDUs must continue during the loopback
state to maintain the OAM session.
The loopback command is acknowledged by responding with an information OAM PDU with the
loopback state indicated in the state field. This acknowledgement allows an administrator, for example,
to estimate if a network segment can satisfy a service-level agreement. Acknowledgement makes it
possible to test delay, jitter, and throughput.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-34
OL-23826-09
Chapter 10
Configuring Ethernet OAM
When an interface is set to the remote loopback mode the interface no longer participates in any other
Layer 2 or Layer 3 protocols; for example Spanning Tree Protocol (STP) or Open Shortest Path First
(OSPF). The reason is that when two connected ports are in a loopback session, no frames other than the
OAM PDUs are sent to the CPU for software processing. The non-OAM PDU frames are either looped
back at the MAC level or discarded at the MAC level.
From a user's perspective, an interface in loopback mode is in a link-up state.
Cisco Vendor-Specific Extensions
Ethernet OAM allows vendors to extend the protocol by allowing them to create their own
type-length-value (TLV) fields.
OAM Messages
Ethernet OAM messages or OAM PDUs are standard length, untagged Ethernet frames within the normal
frame length bounds of 64 to 1518 bytes. The maximum OAM PDU frame size exchanged between two
peers is negotiated during the discovery phase.
OAM PDUs always have the destination address of slow protocols (0180.c200.0002) and an Ethertype
of 8809. OAM PDUs do not go beyond a single hop and have a hard-set maximum transmission rate of
10 OAM PDUs per second. Some OAM PDU types may be transmitted multiple times to increase the
likelihood that they will be successfully received on a deteriorating link.
Four types of OAM messages are supported:
•
Information OAM PDU—A variable-length OAM PDU that is used for discovery. This OAM PDU
includes local, remote, and organization-specific information.
•
Event notification OAM PDU—A variable-length OAM PDU that is used for link monitoring. This
type of OAM PDU may be transmitted multiple times to increase the chance of a successful receipt;
for example, in the case of high-bit errors. Event notification OAM PDUs also may include a time
stamp when generated.
•
Loopback control OAM PDU—An OAM PDU fixed at 64 bytes in length that is used to enable or
disable the remote loopback command.
•
Vendor-specific OAM PDU—A variable-length OAM PDU that allows the addition of
vendor-specific extensions to OAM.
For instructions on how to configure Ethernet Link OAM, see Setting Up and Configuring Ethernet
OAM, page 10-35.
Setting Up and Configuring Ethernet OAM
This section includes the following topics:
•
Default Ethernet OAM Configuration, page 10-36
•
Restrictions and Guidelines, page 10-36
•
Enabling Ethernet OAM on an Interface, page 10-36
•
Enabling Ethernet OAM Remote Loopback, page 10-38
•
Configuring Ethernet OAM Link Monitoring, page 10-38
•
Configuring Ethernet OAM Remote Failure Indications, page 10-41
•
Configuring Ethernet OAM Templates, page 10-42
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-35
Chapter 10
•
Displaying Ethernet OAM Protocol Information, page 10-45
•
Verifying Ethernet OAM Configuration, page 10-46
Configuring Ethernet OAM
Default Ethernet OAM Configuration
•
Ethernet OAM is disabled on all interfaces.
•
When Ethernet OAM is enabled on an interface, link monitoring is automatically turned on.
•
Remote loopback is disabled.
•
No Ethernet OAM templates are configured.
Restrictions and Guidelines
Follow these guidelines when configuring Ethernet OAM:
•
The router does not support monitoring of egress frames sent with cyclic redundancy code (CDC)
errors. The ethernet oam link-monitor transmit crc interface-configuration or
template-configuration commands are visible but are not supported on the router. The commands are
accepted, but are not applied to an interface.
•
For a remote failure indication, the router does not generate link fault or Critical Event OAM PDUs.
However, if these PDUs are received from a link partner, they are processed. The router supports
generating and receiving Dying Gasp OAM PDUs when Ethernet OAM is disabled, the interface is
shut down, the interface enters the error-disabled state, the router is reloading, or during power
failure.
•
Effective with Cisco IOS Release 15.3(2)S, the Cisco ASR 901 router supports sub-second OAM
timers.
•
The Cisco ASR 901 router supports up to two Ethernet OAM sessions with sub-second OAM timers.
•
Ethernet OAM sessions with sub-second OAM timers reduce the scalability for Ethernet CFM
sessions.
Enabling Ethernet OAM on an Interface
Complete the following steps to enable Ethernet OAM on an interface:
Command
Purpose
Step 1
configure terminal
Enters global configuration mode.
Step 2
interface interface-id
Defines an interface to configure as an Ethernet OAM
interface, and enters interface configuration mode.
Step 3
ethernet oam
Enables Ethernet OAM on the interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-36
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Command
Step 4
Purpose
ethernet oam [max-rate oampdus | min-rate seconds Configures the OAM parameters:
[ms] | mode {active | passive} | timeout seconds
• max-rate—(Optional) Configures the maximum
[ms] ]
number of OAM PDUs sent per second.
•
oampdus—The range is from 1 to 10.
•
min-rate—(Optional) Configures the minimum
transmission rate when one OAM PDU is sent per
second.
•
seconds—The range is as follows:
– 1 to 10 seconds
– 100 to 900 milliseconds (multiples of 100)
•
ms—Specifies the minimum transmission rate value in
milliseconds.
•
mode active—(Optional) Sets OAM client mode to
active.
•
mode passive—(Optional) Sets OAM client mode to
passive.
Note
When Ethernet OAM mode is enabled on two
interfaces passing traffic, at least one must be in the
active mode.
•
timeout—(Optional) Sets a time for OAM client
timeout.
•
seconds—The range is as follows:
– 2 to 30 seconds
– 500 to 1900 milliseconds (multiples of 100)
•
ms—Specifies the timeout value in milliseconds.
Step 5
end
Returns to privileged EXEC mode.
Step 6
show ethernet oam status [interface interface-id]
Verifies the configuration.
Step 7
copy running-config startup-config
(Optional) Saves your entries in the configuration file.
Use the no ethernet oam interface configuration command to disable Ethernet OAM on the interface.
Configuration Example
The following example shows how to configure an Ethernet OAM session with sub-second OAM timers
on an interface:
Router> enable
Router# configure terminal
Router(config)# interface gigabitethernet 0/1
Router(config-if)# ethernet oam
Router(config-if)# ethernet oam min-rate 100 ms
Router(config-if)# ethernet oam timeout 500 ms
Router(config-if)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-37
Chapter 10
Configuring Ethernet OAM
Enabling Ethernet OAM Remote Loopback
Enable Ethernet OAM remote loopback on an interface for the local OAM client to initiate OAM remote
loopback operations. Changing this setting causes the local OAM client to exchange configuration
information with its remote peer. Remote loopback is disabled by default.
Restrictions
•
Internet Group Management Protocol (IGMP) packets are not looped back.
•
If dynamic ARP inspection is enabled, ARP or reverse ARP packets are not looped or dropped.
Complete the following steps to enable Ethernet OAM remote loopback on an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Define an interface to configure as an EOM interface, and
enter interface configuration mode.
Step 3
ethernet oam remote-loopback {supported |
timeout seconds}
Enable Ethernet remote loopback on the interface or set a
loopback timeout period.
•
Enter supported to enable remote loopback.
•
Enter timeout seconds to set a remote loopback
timeout period. The range is from 1 to 10 seconds.
Step 4
end
Return to privileged EXEC mode.
Step 5
ethernet oam remote-loopback {start | stop}
{interface interface-id}
Turn on or turn off Ethernet OAM remote loopback on an
interface.
Step 6
show ethernet oam status [interface interface-id]
Verify the configuration.
Step 7
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use the no ethernet oam remote-loopback {supported | timeout} interface configuration command to
disable remote loopback support or remove the timeout setting.
Configuring Ethernet OAM Link Monitoring
You can configure high and low thresholds for link-monitoring features. If no high threshold is
configured, the default is none —no high threshold is set. If you do not set a low threshold, it defaults
to a value lower than the high threshold.
Complete the following steps to configure Ethernet OAM link monitoring on an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Define an interface, and enter interface configuration
mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-38
OL-23826-09
Chapter 10
Step 3
Configuring Ethernet OAM
Command
Purpose
ethernet oam link-monitor supported
Enable the interface to support link monitoring. This is the
default.
You need to enter this command only if it has been disabled
by previously entering the no ethernet oam link-monitor
supported command.
Step 4
ethernet oam link-monitor high-threshold action
{error-disable-interface | failover}
Use the ethernet oam link-monitor high-threshold
command to configure an error-disable function on the
Ethernet OAM interface when a high threshold for an error
is exceeded.
Note
Step 5
ethernet oam link-monitor symbol-period
{threshold {high {high symbols | none} | low
{low-symbols}} | window symbols}
Note
Step 6
Repeat this step to configure both high and
low thresholds.
Release 15.0(1)MR does not support the failover
keyword.
(Optional) Configure high and low thresholds for an
error-symbol period that trigger an error-symbol period
link event.
•
Enter threshold high high-symbols to set a high
threshold in number of symbols. The range is 1 to
65535. The default is none.
•
Enter threshold high none to disable the high
threshold if it was set. This is the default.
•
Enter threshold low low-symbols to set a low
threshold in number of symbols. The range is 0 to
65535. It must be lower than the high threshold.
•
Enter window symbols to set the window size (in
number of symbols) of the polling period. The range is
1 to 65535 symbols.
ethernet oam link-monitor frame {threshold {high (Optional) Configure high and low thresholds for error
{high-frames | none} | low {low-frames}} | window frames that trigger an error-frame link event.
milliseconds}
• Enter threshold high high-frames to set a high
threshold in number of frames. The range is 1 to
Note
Repeat this step to configure both high and
65535. The default is none.
low thresholds.
•
Enter threshold high none to disable the high
threshold if it was set. This is the default.
•
Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
•
Enter window milliseconds to set the a window and
period of time during which error frames are counted.
The range is 10 to 600 and represents the number of
milliseconds in multiples of 100. The default is 100.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-39
Chapter 10
Step 7
Command
Purpose
ethernet oam link-monitor frame-period
{threshold {high {high-frames | none} | low
{low-frames}} | window frames}
(Optional) Configure high and low thresholds for the
error-frame period that triggers an error-frame-period link
event.
Note
Step 8
Configuring Ethernet OAM
Repeat this step to configure both high and
low thresholds.
ethernet oam link-monitor frame-seconds
{threshold {high {high-frames | none} | low
{low-frames}} | window milliseconds}
Note
Repeat this step to configure both high and
low thresholds.
•
Enter threshold high high-frames to set a high
threshold in number of frames. The range is 1 to
65535. The default is none.
•
Enter threshold high none to disable the high
threshold if it was set. This is the default.
•
Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
•
Enter window frames to set the a polling window size
in number of frames. The range is 1 to 65535; each
value is a multiple of 10000 frames. The default is
1000.
(Optional) Configure high and low thresholds for the
frame-seconds error that triggers an error-frame-seconds
link event.
•
Enter threshold high high-frames to set a high error
frame-seconds threshold in number of seconds. The
range is 1 to 900. The default is none.
•
Enter threshold high none to disable the high
threshold if it was set. This is the default.
•
Enter threshold low low-frames to set a low threshold
in number of frames. The range is 1 to 900. The default
is 1.
•
Enter window frames to set the a polling window size
in number of milliseconds. The range is 100 to 9000;
each value is a multiple of 100 milliseconds. The
default is 1000.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-40
OL-23826-09
Chapter 10
Step 9
Configuring Ethernet OAM
Command
Purpose
ethernet oam link-monitor receive-crc {threshold
{high {high-frames | none} | low {low-frames}} |
window milliseconds}
(Optional) Configure thresholds for monitoring ingress
frames received with cyclic redundancy code (CRC) errors
for a period of time.
Note
Repeat this step to configure both high and
low thresholds.
•
Enter threshold high high-frames to set a high
threshold for the number of frames received with CRC
errors. The range is 1 to 65535 frames.
•
Enter threshold high none to disable the high
threshold.
•
Enter threshold low low-frames to set a low threshold
in number of frames. The range is 0 to 65535. The
default is 1.
•
Enter window milliseconds to set the a window and
period of time during which frames with CRC errors
are counted. The range is 10 to 1800 and represents the
number of milliseconds in multiples of 100. The
default is 100.
Step 10
ethernet oam link-monitor transmit-crc {threshold Use the ethernet oam link-monitor transmit-crc
{high {high-frames | none} | low low-frames} |
command to configure an Ethernet OAM interface to
window milliseconds} }
monitor egress frames with CRC errors for a period of
time.
Step 11
[no] ethernet link-monitor on
(Optional) Start or stop (when the no keyword is entered)
link-monitoring operations on the interface. Link
monitoring operations start automatically when support is
enabled.
Step 12
end
Return to privileged EXEC mode.
Step 13
show ethernet oam status [interface interface-id]
Verify the configuration.
Step 14
copy running-config startup-config
(Optional) Save your entries in the configuration file.
The ethernet oam link-monitor transmit-crc {threshold {high {high-frames | none} | low
{low-frames}} | window milliseconds} command is visible on the router and you are allowed to enter it,
but it is not supported. Use the no form of this commands to disable the configuration. Use the no form
of each command to disable the threshold setting.
Configuring Ethernet OAM Remote Failure Indications
You can configure an error-disable action to occur on an interface if one of the high thresholds is
exceeded, if the remote link goes down, if the remote device is rebooted, if the remote device disables
Ethernet OAM on the interface, or if the power failure occurs on the remote device .
Complete the following steps to enable Ethernet OAM remote-failure indication actions on an interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Define an interface, and enter interface configuration
mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-41
Chapter 10
Step 3
Configuring Ethernet OAM
Command
Purpose
ethernet oam remote-failure {critical-event |
dying-gasp | link-fault} action
error-disable-interface
Configure the Ethernet OAM remote-failure action on the
interface. You can configure disabling the interface for one
of these conditions:
•
Select critical-event to shut down the interface when
an unspecified critical event has occurred.
•
Select dying-gasp to shut down the interface when
Ethernet OAM is disabled or the interface enters the
error-disabled state.
•
Select link-fault to shut down the interface when the
receiver detects a loss of signal.
Step 4
end
Return to privileged EXEC mode.
Step 5
show ethernet oam status [interface interface-id]
Verify the configuration.
Step 6
copy running-config startup-config
(Optional) Save your entries in the configuration file.
The router does not generate Link Fault or Critical Event OAM PDUs. However, if these PDUs are
received from a link partner, they are processed. The router supports sending and receiving Dying Gasp
OAM PDUs when Ethernet OAM is disabled, the interface is shut down, the interface enters the
error-disabled state, or the router is reloading. It can respond to and generate Dying Gasp PDUs based
on loss of power. Use the no ethernet remote-failure {critical-event | dying-gasp | link-fault} action
command to disable the remote failure indication action.
Configuring Ethernet OAM Templates
You can create a template for configuring a common set of options on multiple Ethernet OAM interfaces.
The template can be configured to monitor frame errors, frame-period errors, frame-second errors,
received CRS errors, and symbol-period errors and thresholds. You can also set the template to put the
interface in error-disabled state if any high thresholds are exceeded. These steps are optional and can be
performed in any sequence or repeated to configure different options.
Complete the following steps to configure an Ethernet OAM template and to associate it with an
interface:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
template template-name
Create a template, and enter template configuration mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-42
OL-23826-09
Chapter 10
Step 3
Step 4
Step 5
Configuring Ethernet OAM
Command
Purpose
ethernet oam link-monitor receive-crc {threshold
{high {high-frames | none} | low {low-frames}} |
window milliseconds}
(Optional) Configure thresholds for monitoring ingress
frames received with cyclic redundancy code (CRC) errors
for a period of time.
ethernet oam link-monitor symbol-period
{threshold {high {high symbols | none} | low
{low-symbols}} | window symbols}
•
Enter the threshold high high-frames command to set
a high threshold for the number of frames received
with CRC errors. The range is 1 to 65535 frames.
•
Enter the threshold high none command to disable the
high threshold.
•
Enter the threshold low low-frames command to set a
low threshold in number of frames. The range is 0 to
65535. The default is 1.
•
Enter the window milliseconds command to set the a
window and period of time during which frames with
CRC errors are counted. The range is 10 to 1800 and
represents the number of milliseconds in multiples of
100. The default is 100.
(Optional) Configure high and low thresholds for an
error-symbol period that triggers an error-symbol period
link event.
•
Enter the threshold high high-symbols command to
set a high threshold in number of symbols. The range
is 1 to 65535.
•
Enter the threshold high none command to disable the
high threshold.
•
Enter the threshold low low-symbols command to set
a low threshold in number of symbols. The range is 0
to 65535. It must be lower than the high threshold.
•
Enter the window symbols command to set the window
size (in number of symbols) of the polling period. The
range is 1 to 65535 symbols.
ethernet oam link-monitor frame {threshold {high (Optional) Configure high and low thresholds for error
{high-frames | none} | low {low-frames}} | window frames that trigger an error-frame link event.
milliseconds}
• Enter the threshold high high-frames command to set
a high threshold in number of frames. The range is 1 to
65535. You must enter a high threshold.
•
Enter the threshold high none command to disable the
high threshold.
•
Enter the threshold low low-frames command to set a
low threshold in number of frames. The range is 0 to
65535. The default is 1.
•
Enter the window milliseconds command to set the a
window and period of time during which error frames
are counted. The range is 10 to 600 and represents the
number of milliseconds in a multiple of 100. The
default is 100.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-43
Chapter 10
Step 6
Step 7
Configuring Ethernet OAM
Command
Purpose
ethernet oam link-monitor frame-period
{threshold {high {high-frames | none} | low
{low-frames}} | window frames}
(Optional) Configure high and low thresholds for the
error-frame period that triggers an error-frame-period link
event.
ethernet oam link-monitor frame-seconds
{threshold {high {high-seconds | none} | low
{low-seconds}} | window milliseconds}
•
Enter the threshold high high-frames command to set
a high threshold in number of frames. The range is 1 to
65535. You must enter a high threshold.
•
Enter the threshold high none command to disable the
high threshold.
•
Enter the threshold low low-frames command to set a
low threshold in number of frames. The range is 0 to
65535. The default is 1.
•
Enter the window frames command to set the a polling
window size in number of frames. The range is 1 to
65535; each value is a multiple of 10000 frames. The
default is 1000.
(Optional) Configure frame-seconds high and low
thresholds for triggering an error-frame-seconds link event.
•
Enter the threshold high high-seconds command to
set a high threshold in number of seconds. The range is
1 to 900. You must enter a high threshold.
•
Enter the threshold high none command to disable the
high threshold.
•
Enter the threshold low low-frames command to set a
low threshold in number of frames. The range is 1 to
900. The default is 1.
•
Enter the window frames command to set the a polling
window size in number of frames. The range is 100 to
9000; each value is a multiple of 100 milliseconds. The
default is 1000.
Step 8
ethernet oam link-monitor high threshold action
error-disable-interface
(Optional) Configure the router to move an interface to the
error disabled state when a high threshold for an error is
exceeded.
Step 9
exit
Return to global configuration mode.
Step 10
interface interface-id
Define an Ethernet OAM interface, and enter interface
configuration mode.
Step 11
source-template template-name
Associate the template to apply the configured options to
the interface.
Step 12
end
Return to privileged EXEC mode.
Step 13
show ethernet oam status [interface interface-id]
Verify the configuration.
Step 14
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-44
OL-23826-09
Chapter 10
Configuring Ethernet OAM
The router does not support monitoring egress frames with CRC errors. The ethernet oam link-monitor
transmit-crc {threshold {high {high-frames | none} | low {low-frames}} | window milliseconds}
command is visible on the router and you can enter it, but it is not supported. Use the no form of each
command to remove the option from the template. Use the no source-template template-name to remove
the source template association.
Configuration Example
Router# configure terminal
Enter configuration commands, one per line.
End with CNTL/Z.
Router(config)# interface gigabitEthernet 0/8
Router(config-if)# ethernet oam
Router(config-if)# ethernet oam link-monitor symbol-period threshold high 299
Router(config-if)# ethernet oam link-monitor frame window 399
Router(config-if)# ethernet oam link-monitor frame-period threshold high 599
Router(config-if)# ethernet oam link-monitor frame-seconds window 699
Router(config-if)# ethernet oam link-monitor receive-crc window 99
Router(config-if)# ethernet oam link-monitor transmit-crc threshold low 199
Router(config-if)# ethernet oam link-monitor high-threshold action error-disable-interface
Router(config-if)# end
Router# show running-config interface gigabitethernet 0/8
Building configuration...
Current configuration : 478 bytes
!
interface GigabitEthernet0/8
no ip address
negotiation auto
ethernet oam link-monitor symbol-period threshold high 299
ethernet oam link-monitor frame window 399
ethernet oam link-monitor frame-period threshold high 599
ethernet oam link-monitor frame-seconds window 699
ethernet oam link-monitor receive-crc window 99
ethernet oam link-monitor transmit-crc threshold low 199
ethernet oam link-monitor high-threshold action error-disable-interface
ethernet oam
end
Displaying Ethernet OAM Protocol Information
Use these commands in the privileged EXEC to display the Ethernet OAM protocol information.
Table 10-4
Displaying Ethernet OAM Protocol Information
Command
Purpose
show ethernet oam discovery [interface interface-id] Displays discovery information for all Ethernet OAM interfaces or
the specified interface.
show ethernet oam statistics [interface interface-id] Displays detailed information about Ethernet OAM packets.
show ethernet oam status [interface interface-id]
Displays Ethernet OAM configuration for all interfaces or the
specified interface.
show ethernet oam summary
Displays active Ethernet OAM sessions on the router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-45
Chapter 10
Configuring Ethernet OAM
Verifying Ethernet OAM Configuration
Verifying an OAM Session
To verify an OAM session, use the show ethernet oam summary command.
In the following example, the local client interface is in session with a remote client with MAC address
442b.0348.bc60 and organizationally unique identifier (OUI) 00000C, which is the OUI for Cisco
Systems. The remote client is in active mode, and has established capabilities for link monitoring and
remote loopback for the OAM session.
Router# show ethernet oam summary
Symbols:
* - Master Loopback State, # - Slave Loopback State
& - Error Block State
Capability codes: L - Link Monitor, R - Remote Loopback
U - Unidirection, V - Variable Retrieval
Local
Interface
Gi0/8
MAC Address
Remote
OUI
Mode
442b.0348.bc60 00000C active
Capability
L R
Verifying OAM Discovery Status
To verify OAM Discovery status on the local client and remote peer, use the show ethernet oam
discovery command as shown in the following example:
Router# show ethernet oam discovery interface gigabitethernet 0/8
GigabitEthernet0/8
Local client
-----------Administrative configurations:
Mode:
active
Unidirection:
not supported
Link monitor:
supported (on)
Remote loopback:
not supported
MIB retrieval:
not supported
Mtu size:
1500
Operational status:
Port status:
Loopback status:
PDU revision:
operational
no loopback
0
Remote client
------------MAC address: 442b.0348.bc60
Vendor(oui): 00000C(cisco)
Administrative configurations:
PDU revision:
0
Mode:
active
Unidirection:
not supported
Link monitor:
supported
Remote loopback:
not supported
MIB retrieval:
not supported
Mtu size:
1500
Verifying Information OAMPDU and Fault Statistics
To verify statistics for information OAMPDUs and local and remote faults, use the show ethernet oam
statistics command as shown in the following example:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-46
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Router# show ethernet oam statistics interface gigabitethernet 0/8
GigabitEthernet0/8
Counters:
--------Information OAMPDU Tx
: 5549
Information OAMPDU Rx
: 5914
Unique Event Notification OAMPDU Tx
: 0
Unique Event Notification OAMPDU Rx
: 0
Duplicate Event Notification OAMPDU TX : 0
Duplicate Event Notification OAMPDU RX : 0
Loopback Control OAMPDU Tx
: 0
Loopback Control OAMPDU Rx
: 0
Variable Request OAMPDU Tx
: 0
Variable Request OAMPDU Rx
: 0
Variable Response OAMPDU Tx
: 0
Variable Response OAMPDU Rx
: 0
Cisco OAMPDU Tx
: 1
Cisco OAMPDU Rx
: 0
Unsupported OAMPDU Tx
: 0
Unsupported OAMPDU Rx
: 0
Frames Lost due to OAM
: 0
Local Faults:
------------0 Link Fault records
1 Dying Gasp records
Total dying gasps
Time stamp
: 1
: 23:27:13
0 Critical Event records
Remote Faults:
-------------0 Link Fault records
0 Dying Gasp records
0 Critical Event records
Local event logs:
----------------0 Errored Symbol Period records
0 Errored Frame records
0 Errored Frame Period records
0 Errored Frame Second records
Remote event logs:
-----------------0 Errored Symbol Period records
0 Errored Frame records
0 Errored Frame Period records
0 Errored Frame Second records
Verifying Link Monitoring Configuration and Status
To verify link monitoring configuration and status on the local client, use the show ethernet oam status
command. The Status field in the following example shows that link monitoring status is supported and
enabled (on).
Router# show ethernet oam status interface gigabitethernet 0/8
GigabitEthernet0/8
General
------Admin state:
enabled
Mode:
active
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-47
Chapter 10
Configuring Ethernet OAM
Understanding E-LMI
PDU max rate:
PDU min rate:
Link timeout:
High threshold action:
Link fault action:
Dying gasp action:
Critical event action:
10 packets per second
1 packet per 1000 ms
5000 ms
error disable interface
no action
no action
no action
Link Monitoring
--------------Status: supported (on)
Symbol Period Error
Window:
Low threshold:
High threshold:
100 x 1048576 symbols
1 error symbol(s)
299 error symbol(s)
Frame Error
Window:
Low threshold:
High threshold:
400 x 100 milliseconds
1 error frame(s)
none
Frame Period Error
Window:
Low threshold:
High threshold:
1000 x 10000 frames
1 error frame(s)
599 error frame(s)
Frame Seconds Error
Window:
Low threshold:
High threshold:
700 x 100 milliseconds
1 error second(s)
none
Verifying Status of the Remote OAM Client
To verify the status of a remote OAM client, use the show ethernet oam summary and show ethernet
oam status commands.
To verify the remote client mode and capabilities for the OAM session, use the show ethernet oam
summary command and observe the values in the Mode and Capability fields. The following example
shows that the local client (local interface Gi0/8) is connected to the remote client
Router# show ethernet oam summary
Symbols:
* - Master Loopback State, # - Slave Loopback State
& - Error Block State
Capability codes: L - Link Monitor, R - Remote Loopback
U - Unidirection, V - Variable Retrieval
Local
Interface
Gi0/8
MAC Address
Remote
OUI
Mode
442b.0348.bc60 00000C active
Capability
L R
Understanding E-LMI
Ethernet Local Management Interface (E-LMI) is a protocol between the customer-edge (CE) device and
the provider-edge (PE) device. It runs only on the PE-to-CE UNI link and notifies the CE device of
connectivity status and configuration parameters of Ethernet services available on the CE port. E-LMI
interoperates with an OAM protocol, such as CFM, that runs within the provider network to collect OAM
status. CFM runs at the provider maintenance level (UPE to UPE with inward-facing MEPs at the UNI).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-48
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding E-LMI
OAM manager, which streamlines interaction between any two OAM protocols, handles the interaction
between CFM and E-LMI. This interaction is unidirectional, running only from OAM manager to E-LMI
on the UPE side of the router. Information is exchanged either as a result of a request from E-LMI or
triggered by OAM when it received notification of a change from the OAM protocol. This type of
information is relayed:
•
EVC name and availability status
•
Remote UNI name and status
•
Remote UNI counts
You can configure Ethernet virtual connections (EVCs), service VLANs, UNI ids (for each CE-to-PE
link), and UNI count and attributes. You need to configure CFM to notify the OAM manager of any
change to the number of active UNIs and or the remote UNI ID for a given S-VLAN domain.
You can configure the router as a provider-edge device.
Restrictions
E-LMI is not supported for the service instances in which the pseudowire cross-connects are configured.
Configuring E-LMI
For E-LMI to work with CFM, you configure EVCs, EFPs, and E-LMI customer VLAN mapping. Most
of the configuration occurs on the PE device on the interfaces connected to the CE device. On the CE
device, you only need to enable E-LMI on the connecting interface. Note that you must configure some
OAM parameters, for example, EVC definitions, on PE devices on both sides of a metro network.
This section contains the following topics:
•
Default E-LMI Configuration, page 10-49
•
Enabling E-LMI, page 10-50
•
Displaying E-LMI Information, page 10-51
Default E-LMI Configuration
Ethernet LMI is globally disabled by default. When enabled, the router is in provider-edge (PE) mode
by default.
When you globally enable E-LMI by entering the ethernet lmi global global configuration command,
it is automatically enabled on all interfaces. You can also enable or disable E-LMI per interface to
override the global configuration. The E-LMI command that is given last is the command that has
precedence.
There are no EVCs, EFP service instances, or UNIs defined.
UNI bundling service is bundling with multiplexing.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-49
Chapter 10
Configuring Ethernet OAM
Understanding E-LMI
Enabling E-LMI
You can enable E-LMI globally or on an interface and you can configure the router as a PE device.
Beginning in privileged EXEC mode, follow these steps to enable for E-LMI on the router or on an
interface. Note that the order of the global and interface commands determines the configuration. The
command that is entered last has precedence.
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
ethernet lmi global
Globally enable E-LMI on all interfaces. By default, the
router is a PE device.
Step 3
interface interface-id
Define an interface to configure as an E-LMI interface, and
enter interface configuration mode.
Step 4
ethernet lmi interface
Configure Ethernet LMI on the interface. If E-LMI is
enabled globally, it is enabled on all interfaces unless you
disable it on specific interfaces. If E-LMI is disabled
globally, you can use this command to enable it on
specified interfaces.
Step 5
ethernet lmi {n391 value | n393 value | t391 value|
t392 value}
Configure E-LMI parameters for the UNI.
The keywords have these meanings:
•
n391 value—Set the event counter on the customer
equipment. The counter polls the status of the UNI and
all Ethernet virtual connections (EVCs). The range is
from 1 to 65000; the default is 360.
•
n393 value—Set the event counter for the metro
Ethernet network. The range is from 1 to 10; the
default is 4.
•
t391 value—Set the polling timer on the customer
equipment. A polling timer sends status enquiries and
when status messages are not received, records errors.
The range is from 5 to 30 seconds; the default is 10
seconds.
•
t392 value—Set the polling verification timer for the
metro Ethernet network or the timer to verify received
status inquiries. The range is from 5 to 30 seconds, or
enter 0 to disable the timer. The default is 15 seconds.
Note
The t392 keyword is not supported when the router
is in CE mode.
Step 6
end
Return to privileged EXEC mode.
Step 7
show ethernet lmi evc
Verify the configuration.
Step 8
copy running-config startup-config
(Optional) Save your entries in the configuration file.
Use the no ethernet lmi global configuration command to globally disable E-LMI. Use the no form of
the ethernet lmi interface configuration command with keywords to disable E-LMI on the interface or
to return the timers to the default settings.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-50
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Use the show ethernet lmi commands to display information that was sent to the CE from the status
request poll. Use the show ethernet service commands to show current status on the device.
Displaying E-LMI Information
Use the following commands in privileged EXEC mode to display E-LMI information.
Table 10-5
Displaying E-LMI Information
Command
Purpose
show ethernet lmi evc [detail evc-id [interface
interface-id] | map interface type number]
Displays details sent to the CE from the status request poll about the
E-LMI EVC.
show ethernet lmi parameters interface interface-id Displays Ethernet LMI interface parameters sent to the CE from the
status request poll.
show ethernet lmi statistics interface interface-id
Displays Ethernet LMI interface statistics sent to the CE from the
status request poll.
show ethernet lmi uni map interface [interface-id]
Displays information about the E-LMI UNI VLAN map sent to the CE
from the status request poll.
show ethernet service instance {detail | id
efp-identifier interface interface-id | interface
interface-id}
Displays information relevant to the specified Ethernet service
instances (EFPs).
Understanding Ethernet Loopback
The local aggregated Ethernet, Fast Ethernet, Tri-Rate Ethernet copper, and Gigabit Ethernet interfaces
connect to a remote system. The Loopback command is used to place the interface in loopback mode.
You can use per-port and per EFP Ethernet loopback to test connectivity at initial startup, to test
throughput, and to test quality of service in both directions. The RFC2544 for latency testing specifies
that the throughput must be measured by sending frames at increasing rate, representing the percentage
of frames received as graphs, and reporting the frames dropping rate. This rate is dependent on the frame
size. This throughput measurement at traffic generator requires the ethernet loopback support on the
responder.
Ethernet loopback can be achieved with External or Internal loopback. External loopback is the process
of looping frames coming from the port on the wire side. Internal loopback is the process of looping
frames coming from the port on the relay side.
Configuring Ethernet Loopback
This section contains the following topics:
•
Restrictions
•
Enabling Ethernet Loopback
•
Configuration Example
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-51
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Restrictions
•
Ethernet loopback is not supported on a routed port.
•
A single terminal session is initiated at a time over a cross connect or bridge domain.
•
The maximum total traffic that can be looped back across all sessions combined, is 1GB.
•
For an internal loopback over bridge domain, the traffic for loopback must have encapsulation that
matches the egress encapsulation. If there is a rewrite operation on the egress EFP, the traffic post
the operation must match the EFP encapsulation.
•
Dot1q tag-based filtering is not available on the Cisco ASR 901 router.
•
Internal Loopback over bridge domain cannot be initiated if SPAN is already active.
•
Internal Loopback over bridge domain cannot be initiated if Traffic generator is already active.
•
Loopback is not supported on Fast Ethernet interface.
•
External loopback is not supported on EFP with VLAN range.
•
Source and destination address specified in the EXEC command are the MAC fields. These
addresses are used for MAC swap. The source and destination MAC addresses cannot be identical
or multicast MAC addresses.
•
Source MAC address is mandatory.
•
External loopback is only supported over bridge domain.
•
Internal loopback is not supported over a port-channel interface
•
When Ethernet Loopback is enabled, the L2CP forward and L2CP tunnel protocols are not
functional on any ports.
•
Internal loopback over cross connect cannot be initiated if the Traffic Generator is already active.
Enabling Ethernet Loopback
Complete the following steps to configure Ethernet Loopback on the Cisco ASR 901 router:
SUMMARY STEPS
1.
configure terminal
2.
interface type number
3.
service instance instance-number ethernet
4.
encapsulation dotlq-number
5.
rewrite ingress tag pop 1 symmetric
6.
[bridge domain-number | xconnect peer-ip-address vc-id encapsulation mpls]
7.
ethernet loopback permit [external | internal]
8.
end
9.
ethernet loopback start local interface interface-name service instance instance-number
{external | internal} source mac-address source-mac-address [destination mac-address
destination-mac-address] [timeout {time-in-seconds | none}]
10. ethernet loopback stop local interface type number id session id
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-52
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Specifies an interface type and number to enter the interface
configuration mode.
interface type number
Example:
Router(config)# interface gigabitEthernet0/1
Step 4
service instance instance-number ethernet
Creates a service instance on an interface and enters service
instance configuration mode.
Example:
Router(config-if)# service instance 10 ethernet
Step 5
Defines the matching criteria to be used in order to map the
ingress dot1q frames on an interface to the appropriate
service instance.
encapsulation dotlq-number
Example:
Router(config-if-srv)# encapsulation dot1q 10
Step 6
rewrite ingress tag pop 1 symmetric
Example:
Router(config-if-srv)# rewrite ingress tag pop
1 symmetric
Step 7
Specifies the tag manipulation that is to be performed on the
frame ingress to the service instance. Perform Step 7 if you
want to configure ethernet loopback for a bridge-domain.
Go to Step 8 if you want to configure ethernet loopback for
cross connect.
Binds the service instance to a bridge domain. Perform this
step if you want to configure ethernet loopback for a
bridge-domain.
bridge domain-number
Example:
Router(config-if-srv)# bridge domain 10
Step 8
xconnect peer-ip-address vc-id encapsulation
mpls
Example:
Router(config-if-srv)# xconnect 1.1.1.1 100
encapsulation mpls
Binds an attachment circuit to a pseudowire, and to
configure an Any Transport over MPLS (AToM) static
pseudowire. Perform this step if you want to configure
ethernet loopback for cross connect.
•
peer-ip-address—IP address of the remote provider
edge (PE) peer. The remote router ID can be any IP
address, as long as it is reachable.
•
vc-id—The 32-bit identifier of the virtual circuit (VC)
between the PE routers.
•
encapsulation—Specifies the tunneling method to
encapsulate the data in the pseudowire.
•
mpls—Specifies MPLS as the tunneling method.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-53
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Step 9
Command or Action
Purpose
ethernet loopback permit external
Configures ethernet permit external loopback on an
interface. External loopback allows loopback of traffic from
the wire side. This command is supported under a service
instance and interface.
Example:
Router(config-if-srv)# ethernet loopback permit
external
Step 10
ethernet loopback permit internal
Example:
Router(config-if-srv)# ethernet loopback permit
internal
Step 11
Configures ethernet permit internal loopback on an
interface. Internal loopback allows loopback of traffic from
the relay side. This command is supported under a service
instance and interface.
Returns to privileged EXEC mode.
end
Example:
Router(config-if-srv)# end
Step 12
ethernet loopback start local interface type
number service instance instance-number {
external | internal } source mac-address source
mac-address [destination mac-address
destination-mac-address] [timeout
{time-in-seconds | none}]
Starts ethernet external or internal loopback process on the
service instance. Destination MAC address is an optional
field. If destination mac address is not provided, the
loopback interface MAC address is assigned to the source
MAC address after swapping.
•
(Optional) Use the timeout time-in-seconds command
to set a loopback timeout period. The range is from 1 to
90000 seconds (25 hours). The default value is 300
seconds.
•
(Optional) Use the timeout none command to set the
loopback to no time out.
Example:
Router# ethernet loopback start local interface
gigabitEthernet 0/1 service instance 10
external source mac-address 0123.4567.89ab
destination mac-address 255.255.255 timeout
9000
Step 13
ethernet loopback stop local interface type
number id session id
Stops ethernet loopback.
Example:
Router# ethernet loopback stop local interface
gigabitEthernet 0/1 id 3
Configuration Example
This example shows how to configure Ethernet External Loopback for a bridge-domain:
!
interface GigabitEthernet0/0
service instance 201 ethernet evc201
encapsulation dot1q 201
rewrite ingress tag pop 1 symmetric
bridge-domain 201
ethernet loopback permit external
ethernet loopback permit internal
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-54
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
ethernet loopback start local interface GigabitEthernet0/0 service instance 201
external source mac-address 5000.10a1.6ab8 destination mac-address 0000.0000.0202
timeout 9000
!
!
ethernet loopback stop local interface gigabitEthernet 0/0 id 1
!
This example shows how to configure Ethernet Internal Loopback for cross connect:
!
interface GigabitEthernet0/0
service instance 201 ethernet evc201
encapsulation dot1q 201
rewrite ingress tag pop 1 symmetric
xconnect 2.2.2.2 10 encapsulation mpls
ethernet loopback permit external
ethernet loopback permit internal
!
ethernet loopback start local interface GigabitEthernet0/0 service instance 201
internal source mac-address 5000.10a1.6ab8 destination mac-address 0000.0000.0202
timeout 9000
!
!
ethernet loopback stop local interface gigabitEthernet 0/0 id 1
!
This following is the example of the output from the show ethernet loopback command:
Router# show ethernet loopback active interface GigabitEthernet0/0 service instance 201
Loopback Session ID
: 1
Interface
: GigabitEthernet0/0
Service Instance
: 201
Direction
: Internal
Time out(sec)
: 300
Status
: on
Start time
: 12:06:35.300 IST Mon Sep 23 2013
Time left
: 00:03:28
Dot1q/Dot1ad(s)
: 201
Second-dot1q(s)
:
Source Mac Address
: 5000.10a1.6ab8
Destination Mac Address : 0000.0000.0202
Ether Type
: Any
Class of service
: Any
Llc-oui
: Any
Total Active Session(s): 1
Total Internal Session(s): 1
Total External Session(s): 0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-55
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Configuring Y.1564 to Generate Ethernet Traffic
Y.1564 is an Ethernet service activation or performance test methodology for turning up, installing, and
troubleshooting Ethernet-based services. This test methodology allows for complete validation of
Ethernet service-level agreements (SLAs) in a single test. Using traffic generator performance profile,
you can create the traffic based on your requirements. The network performance like throughput, loss,
and availability are analyzed using Layer 2 traffic with various bandwidth profiles. Availability is
inversely proportional to frame loss ratio.
Figure 10-2 shows the Traffic Generator topology over bridge domain describing the traffic flow in the
external and internal modes. The traffic is generated at the wire-side of network to network interface
(NNI) and is transmitted to the responder through the same interface for the external mode. The traffic
is generated at the user to network interface (UNI) and transmitted to the responder through NNI
respectively for the internal mode. External mode is used to measure the throughput and loss at the NNI
port where as internal mode is used to measure the throughput and loss at the UNI port. During traffic
generation, traffic at other ports is not impacted by the generated traffic and can continue to switch
network traffic.
Figure 10-2
Traffic Generator Topology over Bridge Domain
Effective with Cisco IOS release 15.4.(01)S, traffic can be generated over cross connect interface.
Figure 10-3 shows the Traffic Generator topology over cross connect describing the traffic flow in the
external and internal modes.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-56
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Figure 10-3
Traffic Generator Topology over cross connect
Internal Mode
Traffic generated from UNI port
UNI
Interface
Measurement
port - UNI
NNI
Interface
Carrier Ethernet
Ethernet
Loopback
Traffic generating Router
External Mode
NNI
Interface
Carrier Ethernet
Measurement
port - NNI
361413
Ethernet
Loopback
To generate traffic using Y.1564, complete the following tasks:
Note
•
Configure EVC on the interface path such that the Layer 2/L2VPN path should be complete between
transmitter and receiver.
•
Configure Traffic Generator on the transmitter.
•
Configure ethernet loopback on the receiver. For information on Ethernet loopback, see
Understanding Ethernet Loopback, page 10-51.
•
Start the IP SLA session.
Using traffic generator, a maximum traffic of 1GB is generated.
Restrictions
•
A single traffic session is generated.
•
Traffic generation will not be supported on VLAN interface.
•
One-way traffic generation and passive measurement features are not supported.
•
Payload signature verification is not supported.
•
The QoS functions like classification and policing are supported on the ingress EVC.
•
Internal mode traffic generation cannot be configured on port channel interfaces.
•
Maximum throughput rate is 1GB.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-57
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
•
SPAN and Traffic generator cannot be used simultaneously since both uses the mirror mechanism.
•
For Traffic generation over cross connect port-channel will not be supported for both internal and
external modes.
•
Ethernet loopback and Traffic generator cannot be used simultaneously.
•
After reload, the Traffic generator over cross connect should be rescheduled (stop and start).
•
After cross connect flaps, the Traffic generator over cross connect should be rescheduled (stop and
start).
Configuring IP SLA for Traffic Generation
Complete these steps to configure IP SLA for traffic generation.
SUMMARY STEPS
1.
configure terminal
2.
ip sla sla_id
3.
service-performance type ethernet dest-mac-addr destination mac-address interface type
number service instance number
4.
aggregation | default | description | duration | exit | frequency | measurement-type direction |
no | profile | signature
5.
default | exit | loss | no | throughput
6.
exit
7.
default | exit | inner-cos | inner-vlan | no | outer-cos | outer-vlan | packet-size | src-mac-addr
8.
exit
9.
direction {external | internal}
10. default | exit | no | rate-step
11. exit
DETAILED STEPS
Step 1
Command or Action
Purpose
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 2
ip sla sla_id
Specify the SLA ID to start the IP SLA session.
Example:
Router(config)# ip sla 100
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-58
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Step 3
Command or Action
Purpose
service-performance type ethernet dest-mac-addr
destination mac-address interface type number
service instance number
Specifies the service performance type as ethernet and the
destination MAC address in H.H.H format.
Example:
Router(config-ip-sla)# service-performance type
ethernet dest-mac-addr 0001.0001.0001 interface
gigabitEthernet0/10 service instance 10
Step 4
Step 5
Step 6
aggregation | default | description | duration
| exit | frequency | measurement-type direction
| no | profile | signature
Specifies an interface type and number which traffic
generator uses to send the packets. Also, specifies the
service instance number that is required to create a service
instance on an interface. The range is 1 to 4096.
Specify the type of service performance. The following are
the options:
•
aggregation—Represents the statistics aggregation.
Example:
•
default—Set a command to its defaults.
Router(config-ip-sla-service-performance)# prof
ile traffic direction external
•
description—Description of the operation.
•
duration—Sets the service performance duration
configuration.
•
frequency—Represents the scheduled frequency. The
options available are iteration and time. The range is 20
to 65535 seconds.
•
measurement-type direction—Specifies the statistics
to measure traffic. The options available are external or
internal; the default option is Internal. If you use this
option, go to Step 5.
•
profile—Specifies the service performance profile. If
you use the packet or traffic option, go to Step 7 or Step
9 respectively.
•
signature—Specifies the payload contents.
default | exit | loss | no | throughput
Specifies the measurement type based on which the service
performance is calculated. The following are the options:
Example:
•
default—Set a command to its defaults
Router(config-ip-sla-service-performance-measur
ement)# throughput
•
loss—Specifies the measurement such as frame loss.
•
throughput—Specifies the measurement such as
average rate of successful frame delivery.
exit
Exits the measurement mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-59
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
Step 7
Command or Action
Purpose
default | exit | inner-cos | inner-vlan | no |
outer-cos | outer-vlan | packet-size |
src-mac-addr
Specifies the packet type. The following are the options:
•
default—Set a command to its defaults
•
inner-cos—Specify the class of service (CoS) value for
the inner VLAN tag of the interface from which the
message will be sent.
•
inner-vlan—Specify the VLAN ID for the inner vlan
tag of the interface from which the message will be
sent.
•
outer-cos—Specify the CoS value which will be filled
in the outer VLAN tag of the packet.
•
outer-vlan—Specify the VLAN ID which will be filled
in the outer VLAN tag of the packet.
•
packet-size—Specify the packet size; the default size
is 64 bytes. The supported packet size are 64 bytes, 128
bytes, 256 bytes, 512 bytes, 1280 bytes, and 1518 bytes.
•
src-mac-addr—Specifies the source MAC address in
H.H.H format.
Example:
Router(config-ip-sla-service-performance-packet
)# src-mac-addr 4055.3989.7b56
Step 8
exit
Exits the packet mode.
Step 9
direction {external | internal}
Specifies the direction of the profile traffic. The options are
external and internal.
Example:
Router(config-ip-sla-service-performance)# prof
ile traffic direction external
Step 10
Specifies the traffic type. The following are the options:
default
or
exit
or
no
or
rate-step
•
default—Set a command to its defaults
•
rate-step—Specifies the transmission rate in kbps. The
rate-step range is from 1-1000000 (1 Kbps to 1Gbps).
Example:
Router(config-ip-sla-service-performance-traffi
c)# rate-step kbps 1000
Step 11
Exits the traffic mode.
exit
Configuration Examples
This section shows sample configuration examples for traffic generation on Cisco ASR 901 Router:
ip sla 10
service-performance type ethernet dest-mac-addr 0001.0001.0001 interface
TenGigabitEthernet0/0 service instance 30
measurement-type direction external
loss
throughput
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-60
OL-23826-09
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
profile packet
outer-vlan 30
packet-size 512
src-mac-addr d48c.b544.93dd
profile traffic direction external
rate-step kbps 1000
frequency time 35
Example: Two-Way Measurement
The following is a sample configuration for two-way measurement to measure throughput, loss, tx, rx,
txbytes, and rxbytes.
INTERNAL: (to test UNI scenario)
ip sla 2
service-performance type ethernet dest-mac-addr aaaa.bbbb.cccc interface
GigabitEthernet0/0 service instance 2
measurement-type direction internal
loss
throughput
profile packet
outer-vlan 10
packet-size 512
src-mac-addr d48c.b544.9600
profile traffic direction internal
rate-step kbps 1000 2000 3000
frequency time 95
EXTERNAL: (to test NNI scenario)
ip sla 2
service-performance type ethernet dest-mac-addr aaaa.bbbb.cccc interface
gigabitEthernet0/7 service instance 2
measurement-type direction external
loss
throughput
profile packet
outer-vlan 10
packet-size 512
src-mac-addr d48c.b544.9600
profile traffic direction external
rate-step kbps 1000 2000 3000
frequency time 95
Example: Traffic Generation Mode
The following is a sample configuration for traffic generation mode to measure tx and txbytes.
INTERNAL: (to test UNI scenario)
ip sla 2
service-performance type ethernet dest-mac-addr aaaa.bbbb.cccc interface
GigabitEthernet0/0 service instance 2
measurement-type direction internal
profile packet
outer-vlan 10
packet-size 512
src-mac-addr d48c.b544.9600
profile traffic direction internal
rate-step kbps 1000 2000 3000
frequency time 95
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
10-61
Chapter 10
Configuring Ethernet OAM
Understanding Ethernet Loopback
EXTERNAL: (to test NNI scenario)
ip sla 2
service-performance type ethernet dest-mac-addr aaaa.bbbb.cccc interface
GigabitEthernet0/7 service instance 2
measurement-type direction external
profile packet
outer-vlan 10
packet-size 512
src-mac-addr d48c.b544.9600
profile traffic direction external
rate-step kbps 1000 2000 3000
frequency time 95
The following is an example of the output from the show ip sla statistics command.
show ip sla statistics 10
IPSLAs Latest Operation Statistics
IPSLA operation id: 10
Type of operation: Ethernet Service Performance
Test mode: Traffic Generator
Steps Tested (kbps): 1000
Test duration: 30 seconds
Latest measurement:
Latest return code:
01:34:08.636 IST Wed Sep 25 2013
OK
Step 1 (1000 kbps):
Stats:
Tx Packets: 1425 Tx Bytes: 729600
Step Duration: 6 seconds
Note
Statistics are cumulative over a period of time and not specific to any particular time instance.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
10-62
OL-23826-09
CH A P T E R
11
ITU-T Y.1731 Performance Monitoring
This chapter provides information on the ITU-T Y.1731 Performance Monitoring for the
Cisco ASR 901 Series Aggregation Services Router.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for ITU-T Y.1731 Performance Monitoring” section on page 11-25.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Prerequisites for ITU-T Y.1731 Performance Monitoring, page 11-1
•
Restrictions for ITU-T Y.1731 Performance Monitoring, page 11-2
•
Information About ITU-T Y.1731 Performance Monitoring, page 11-2
•
How to Configure ITU-T Y.1731 Performance Monitoring, page 11-5
•
Verifying the Frame Delay and Synthetic Loss Measurement Configurations, page 11-15
•
How to Configure IP SLAs Y.1731 On-Demand and Concurrent Operations, page 11-19
•
Configuration Examples for IP SLAs Y.1731 On-Demand Operations, page 11-21
•
Additional References, page 11-23
•
Feature Information for ITU-T Y.1731 Performance Monitoring, page 11-25
Prerequisites for ITU-T Y.1731 Performance Monitoring
•
Configure and enable IEEE-compliant connectivity fault management (CFM) for Y.1731
performance monitoring to function.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-1
Chapter 11
ITU-T Y.1731 Performance Monitoring
Restrictions for ITU-T Y.1731 Performance Monitoring
Restrictions for ITU-T Y.1731 Performance Monitoring
•
The Cisco ASR 901 router does not support one-way delay measurement (1DM).
•
The Cisco ASR 901 router does not support Loss Measurement Message (LMM).
•
The Cisco ASR 901 router does not support Delay Measurement Message (DMM) on the cross
connect EVC.
•
The Cisco ASR 901 router does not support Synthetic Loss Measurement (SLM) on the port level
cross connect.
•
The Cisco ASR901 router does not support Multi-NNI CFM and SLM over the cross-connect EFP
simultaneously. However, you can enable Multi-NNI CFM or SLM over the cross-connect EFP
function in a node.
Information About ITU-T Y.1731 Performance Monitoring
When service providers sell connectivity services to a subscriber, a Service Level Agreement (SLA) is
reached between the buyer and seller of the service. The SLA defines the attributes offered by a provider
and serves as a legal obligation on the service provider. As the level of performance required by
subscribers rises, service providers need to monitor the performance parameters being offered. Various
standards, such as IEEE 802.1ag and ITU-T Y.1731, define the methods and frame formats used to
measure performance parameters.
ITU-T Y.1731 performance monitoring provides standards-based Ethernet performance monitoring as
outlined in the ITU-T Y-1731 specification and interpreted by the Metro Ethernet Forum (MEF). It
includes the measurement of Ethernet frame delay, frame delay variation, frame loss, and throughput.
To measure SLA parameters such as frame delay or frame delay variation, a small number of synthetic
frames are transmitted along with the service to the end point of the maintenance region, where the
Maintenance End Point (MEP) responds to the synthetic frame.
The following figure illustrates Maintenance Entities (ME) and MEP typically involved in a
point-to-point metro ethernet deployment for the Y.1731 standard.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-2
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
Information About ITU-T Y.1731 Performance Monitoring
Figure 11-1
A Point-to-Point Metro Ethernet Deployment with Typical Maintenance Entities and
Maintenance Points
Subscriber
Equipment
1
Subscriber
Equipment
Service Provider
Operator A NEs
2
3
Operator B NEs
4
5
6
7
8
Subscriber
MEG
Test MEG
EVC ME
Operator A
Operator B MEG
E-NNI ME
UNI ME
281942
UNI MEG
MEP (up orientation)
MEP (down orientation)
Logical path of SOAM PDUs
Frame Delay and Frame-Delay Variation
Ethernet frame Delay Measurement (ETH-DM) is used for on-demand Ethernet Operations,
Administration & Maintenance (OAM) to measure frame delay and frame-delay variation.
Ethernet frame delay and frame delay variation are measured by sending periodic frames with ETH-DM
information to the peer MEP in the same maintenance entity. Peer MEPs perform frame-delay and
frame-delay variation measurements through this periodic exchange during the diagnostic interval.
Ethernet frame delay measurement supports hardware-based timestamping in the ingress direction.
These are the two methods of delay measurement, as defined by the ITU-T Y.1731 standard, One-way
ETH-DM (1DM) and Two-way ETH-DM (2DM). However, the Cisco ASR 901 router supports only
Two-way ETH-DM.
Two-way Delay Measurement
Two-way frame delay and variation can be measured using DMM and Delay Measurement Reply (DMR)
frames.
In two-way delay measurements, the sender MEP transmits a frame containing ETH-DM request
information and TxTimeStampf, where TxTimeStampf is the timestamp of the time at which the DMM
is sent.
When the receiver MEP receives the frame, it records RxTimeStampf, where RxTimeStampf is the
timestamp of the time at which the frame with ETH-DM request information is received.
The receiver MEP responds with a frame containing ETH-DM reply information and TxTimeStampb,
where TxTimeStampb is the timestamp of the time at which the frame with ETH-DM reply information
is sent.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-3
Chapter 11
ITU-T Y.1731 Performance Monitoring
Information About ITU-T Y.1731 Performance Monitoring
When the sender MEP receives this frame, it records RxTimeStampb, where RxTimeStampb is the
timestamp of the time at which the frame containing ETH-DM reply information is received.
Two-way frame delay is calculated as:
Frame delay = (RxTimeStampb-TxTimeStampf)-(TxTimeStampb-RxTimeStampf)
Note
Discard the frame delay and frame-delay variation measurements when known network topology
changes occur or when continuity and availability faults occur.
For more information on ITU-T Y.1731 performance monitoring, see Configuring IP SLAs
Metro-Ethernet 3.0 (ITU-T Y.1731) Operations in the IP SLAs Configuration Guide.
Frame Loss Ratio
Ethernet Frame Loss Ratio (ETH-LM: FLR), also known as frame loss, measures the availability of
synthetic frames in the network. Availability is defined in terms of the ratio of frames lost to frames sent,
or Frame Loss Ratio (FLR).
Ethernet Synthetic Loss Measurement (ETH-SLM) is used to collect counter values applicable for
ingress and egress synthetic frames where the counters maintain a count of transmitted and received
synthetic frames between a pair of MEPs.
ETH-SLM transmits synthetic frames with ETH-SLM information to a peer MEP and similarly receives
synthetic frames with ETH-SLM information from the peer MEP. Each MEP performs frame loss
measurements, which contribute to unavailable time. A near-end frame loss refers to frame loss
associated with ingress data frames. A far-end frame loss refers to frame loss associated with egress data
frames. Both near-end and far-end frame loss measurements contribute to near-end severely errored
seconds and far-end severely errored seconds, which together contribute to unavailable time. ETH-SLM
is measured using SLM and SLR frames.
There are the two methods of frame loss measurement, defined by the ITU-T Y.1731 standard ETH-LM
and ETH-SLM. However, the Cisco ASR 901 router supports only single-ended ETH-SLM.
Single-ended ETH-SLM
Each MEP transmits frames with the ETH-SLM request information to its peer MEP and receives frames
with ETH-SLR reply information from its peer MEP to carry out synthetic loss measurements.
On-Demand and Concurrent Operations
On-demand IP SLAs SLM operations enable users without configuration access to perform real-time
troubleshooting of Ethernet services. There are two operational modes for on-demand operations: direct
mode that creates and runs an operation immediately and referenced mode that starts and runs a
previously configured operation.
•
In the direct mode, a single command can be used to create multiple pseudo operations for a range
of class of service (CoS) values to be run, in the background, immediately. A single command in
privileged EXEC mode can be used to specify frame size, interval, frequency, and duration for the
direct on-demand operation. Direct on-demand operations start and run immediately after the
command is issued.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-4
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
•
In the referenced mode, you can start one or more already-configured operations for different
destinations, or for the same destination, with different CoS values. Issuing the privileged EXEC
command creates a pseudo version of a proactive operation that starts and runs in the background,
even while the proactive operation is running.
•
After an on-demand operation is completed, statistical output is displayed on the console.
On-demand operation statistics are not stored and are not supported by the statistic history and
aggregation functions.
•
After an on-demand operation is completed, and the statistics handled, the direct and referenced
on-demand operation is deleted. The proactive operations are not deleted and continue to be
available to be run in referenced mode, again.
A concurrent operation consists of a group of operations, all configured with the same operation ID
number, that run concurrently. Concurrent operations are supported for a given EVC, CoS, and remote
MEP combination, or for multiple MEPs for a given multipoint EVC, for delay or loss measurements.
The Cisco ASR 901 router also supports burst mode for concurrent operations, one-way dual-ended,
single-ended delay and delay variation operations, and single-ended loss operations.
Supported interfaces
The ASR 901 router supports ITU-T Y.1731 performance monitoring on the following interfaces:
Note
•
DMM and SLM support on the EVC bridge domain (BD)
•
DMM and SLM support on the Port-Channel EVC BD
•
SLM support on the EVC cross connect
•
SLM support on the Port-Channel EVC cross connect
•
DMM and SLM support on the EVC BD for both the up and down MEPs
•
SLM support on the EVC cross connect for both the up and down MEPs
SLM and DMM can be configured for the same EVCs over CFM session. The combined number of CFM,
DMM, and SLM sessions must be within the scale limits, otherwise DMM/SLM probes might get
dropped resulting in a few incomplete measurements.
Benefits of ITU-T Y.1731 Performance Monitoring
Combined with IEEE-compliant CFM, Y.1731 performance monitoring provides a comprehensive fault
management and performance monitoring solution for service providers. This comprehensive solution
in turn lessens service providers' operating expenses, improves their SLAs, and simplifies their
operations.
How to Configure ITU-T Y.1731 Performance Monitoring
•
Configuring Two-Way Delay Measurement, page 11-6
•
Configuring Single-Ended Synthetic Loss Measurement, page 11-9
•
Scheduling IP SLAs Operations, page 11-14
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-5
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Configuring Two-Way Delay Measurement
Note
To display information about remote (target) MEPs on destination devices, use the show ethernet cfm
maintenance-points remote command.
Complete the following steps to configure two-way delay measurement.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip sla operation-number
4.
ethernet y1731 delay DMM domain domain-name {evc evc-id | vlan vlan-id} {mpid target-mp-id
| mac-address target-address} cos cos {source {mpid source-mp-id | mac-address
source-address}}
5.
aggregate interval seconds
6.
distribution {delay | delay-variation} {one-way | two-way} number-of-bins
boundary[,...,boundary]
7.
frame interval milliseconds
8.
frame offset offset-value
9.
frame size bytes
10. history interval intervals-stored
11. max-delay milliseconds
12. owner owner-id
13. end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ip sla operation-number
Example:
Router(config)# ip sla 10
Configures an IP SLA operation and enters IP SLA
configuration mode.
•
operation-number—Identifies the IP SLAs
operation you want to configure.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-6
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Step 4
Command
Purpose
ethernet y1731 delay DMM domain domain-name {evc
evc-id | vlan vlan-id} {mpid target-mp-id |
mac-address target-address} cos cos {source {mpid
source-mp-id | mac-address source-address}}
Configures two-way delay measurement and enters
IP SLA Y.1731 delay configuration mode.
Example:
•
DMM—Specifies that the frames sent are Delay
Measurement Message (DMM) synthetic frames.
•
domain domain-name—Specifies the name of
the Ethernet maintenance Operations,
Administration & Maintenance (OAM) domain.
•
evc evc-id—Specifies the EVC identification
name.
•
vlan vlan-id—Specifies the VLAN identification
number. The range is from 1 to 4096.
•
mpid target-mp-id—Specifies the maintenance
endpoint identification numbers of the MEP at
the destination. The range is from 1 to 8191.
•
mac-address target-address—Specifies the
MAC address of the MEP at the destination.
•
cos cos—Specifies, for this MEP, the class of
service (CoS) that will be sent in the Ethernet
message. The range is from 0 to 7.
•
source—Specifies the source MP ID or MAC
address.
•
mpid source-mp-id—Specifies the maintenance
endpoint identification numbers of the MEP
being configured. The range is from 1 to 8191.
•
mac-address source-address—Specifies the
MAC address of the MEP being configured.
Router(config-ip-sla)# ethernet y1731 delay DMM
domain xxx evc yyy mpid 101 cos 4 source mpid 100
Step 5
(Optional) Configures the length of time during
which the performance measurements are conducted
and the results stored.
aggregate interval seconds
Example:
Router(config-sla-y1731-delay)# aggregate interval
900
•
seconds—Specifies the length of time in seconds.
The range is from 1 to 65535. The default is 900.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-7
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Step 6
Command
Purpose
distribution {delay | delay-variation} {one-way |
two-way} number-of-bins boundary[,...,boundary]
(Optional) Specifies measurement type and
configures bins for statistics distributions kept.
•
delay—Specifies that the performance
measurement type is delay. This is the default
value, along with delay variation.
•
delay-variation—Specifies that the performance
measurement type is delay variation. This is the
default value, along with delay.
•
one-way—Specifies one-way measurement
values. This is the default for a dual-ended
operation.
•
two-way—Specifies two-way measurement
values. This is the default for a single-ended
operation.
•
number-of-bins—Specifies the number of bins
kept during an aggregate interval. The range is
from 1 to 10. The default is 10.
•
boundary [,...,boundary]—Lists upper
boundaries for bins in microseconds. Minimum
number of boundaries required is one. Maximum
allowed value for the uppermost boundary is -1
microsecond. Multiple values must be separated
by a comma (,). The default value is
5000,10000,15000,20000,25000,30000,35000,4
0000,45000, -1.
Example:
Router(config-sla-y1731-delay)# distribution
delay-variation two-way 5 5000, 10000,15000,20000,-1
Step 7
frame interval milliseconds
(Optional) Sets the gap between successive frames.
•
Example:
Router(config-sla-y1731-delay)# frame interval 100
Step 8
frame offset offset-value
Example:
(Optional) Sets a value for calculating delay variation
values.
•
Router(config-sla-y1731-delay)# frame offset 1
Step 9
frame size bytes
•
Router(config-sla-y1731-delay)# frame size 32
history interval intervals-stored
Example:
Router(config-sla-y1731-delay)# history interval 2
offset-value—The range is from 1 to 10. The
default is 1.
(Optional) Configures padding size for frames.
Example:
Step 10
milliseconds—Specifies the length of time in
milliseconds (ms) between successive synthetic
frames. The range is from 100 to 10000. The
default is 1000.
bytes—Specifies the padding size, in four-octet
increments, for the synthetic frames. The range is
from 64 to 384. The default is 64.
(Optional) Sets the number of statistics distributions
kept during the lifetime of an IP SLAs Ethernet
operation.
•
intervals-stored—Specifies the number of
statistics distributions. The range is from 1 to 10.
The default is 2.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-8
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Step 11
Command
Purpose
max-delay milliseconds
(Optional) Sets the amount of time an MEP waits for
a frame.
•
Example:
Router(config-sla-y1731-delay)# max-delay 5000
Step 12
(Optional) Configures the owner of an IP SLAs
operation.
owner owner-id
•
Example:
Router(config-sla-y1731-delay)# owner admin
Step 13
milliseconds—Specifies the maximum delay in
milliseconds (ms). The range is from 1 to 65535.
The default is 5000.
owner-id—Specifies the name of the SNMP
owner. The value is from 0 to 255 ASCII
characters.
Exits IP SLA Y.1731 delay configuration mode and
enters privileged EXEC mode.
end
Example:
Router(config-sla-y1731-delay)# end
What to Do Next
After configuring two-way delay measurement, see the Scheduling IP SLAs Operations, page 11-14 to
schedule the operation.
Configuring Single-Ended Synthetic Loss Measurement
Note
To display information about remote (target) MEPs on destination devices, use the show ethernet cfm
maintenance-points remote command.
Complete the following steps to configure a single-ended SLM.
Prerequisites
Class of Service (CoS)-level monitoring must be enabled on MEPs associated to the Ethernet frame loss
operation using the monitor loss counter command on the devices at both ends of the operation.
Note
Cisco IOS Y.1731 implementation allows monitoring of frame loss for frames on an EVC regardless of
the CoS value (any CoS or Aggregate CoS cases). See the "Configuration Examples for IP SLAs
Metro-Ethernet 3.0 (ITU-T Y.1731) Operations" section for configuration information.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
asr901-platf-multi-nni-cfm
4.
ip sla operation-number
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-9
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
5.
ethernet y1731 loss SLM domain domain-name {evc evc-id | vlan vlan-id} {mpid target-mp-id |
mac-address target-address} cos cos {source {mpid source-mp-id | mac-address
source-address}}
6.
aggregate interval seconds
7.
availability algorithm {sliding-window | static-window}
8.
frame consecutive value
9.
frame interval milliseconds
10. frame size bytes
11. history interval intervals-stored
12. owner owner-id
13. exit
14. exit
15. ip sla reaction-configuration operation-number [react {unavailableDS | unavailableSD |
loss-ratioDS | loss-ratioSD}] [threshold-type {average [number-of-measurements] | consecutive
[occurrences] | immediate}] [threshold-value upper-threshold lower-threshold]
16. ip sla logging traps
17. exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
[no] asr901-platf-multi-nni-cfm
Example:
Router# asr901-platf-multi-nni-cfm
Step 4
ip sla operation-number
Example:
Router(config)# ip sla 11
Enables Multi-NNI CFM configuration on the Cisco
ASR 901 router. The no form of this command
enables the SLM over cross connect EVC
configuration. The default option enables multi-NNI
CFM configuration.
Configures an IP SLA operation and enters IP SLA
configuration mode.
•
operation-number—Identifies the IP SLAs
operation you want to configure.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-10
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Step 5
Command
Purpose
ethernet y1731 loss SLM domain domain-name {evc
evc-id | vlan vlan-id} {mpid target-mp-id |
mac-address target-address} cos cos {source {mpid
source-mp-id | mac-address source-address}}
Configures a single-ended synthetic loss
measurement and enters IP SLA Y.1731 loss
configuration mode.
•
SLM—Specifies that the frames sent are
Synthetic Loss Measurement (SLM) frames.
•
domain domain-name—Specifies the name of
the Ethernet Connectivity Fault Management
(CFM) maintenance domain.
•
evc evc-id—Specifies the EVC identification
name.
•
vlan vlan-id—Specifies the VLAN identification
number. The range is from 1 to 4096.
•
mpid target-mp-id—Specifies the maintenance
endpoint identification numbers of the MEP at
the destination. The range is from 1 to 8191.
•
mac-address target-address—Specifies the
MAC address of the MEP at the destination.
•
cos cos—Specifies, for this MEP, the class of
service (CoS) that will be sent in the Ethernet
message. The range is from 0 to 7.
•
source—Specifies the source MP ID or MAC
address.
•
mpid source-mp-id—Specifies the maintenance
endpoint identification numbers of the MEP
being configured. The range is from 1 to 8191.
•
mac-address source-address—Specifies the
MAC address of the MEP being configured.
Example:
Router(config-ip-sla)# ethernet y1731 loss SLM
domain xxx evc yyy mpid 101 cos 4 source mpid 100
Step 6
(Optional) Configures the length of time during
which the performance measurements are conducted
and the results stored.
aggregate interval seconds
Example:
Router(config-sla-y1731-loss)# aggregate interval
900
Step 7
availability algorithm {sliding-window |
static-window}
Example:
Router(config-sla-y1731-loss)# availability
algorithm static-window
Step 8
•
seconds—Specifies the length of time in seconds.
The range is from 1 to 65535. The default is 900.
(Optional) Specifies availability algorithm used.
•
sliding-window—Specifies a sliding-window
control algorithm.
•
static-window—Specifies static-window control
algorithm.
(Optional) Specifies number of consecutive
measurements to be used to determine availability or
unavailability status.
frame consecutive value
Example:
Router(config-sla-y1731-loss)# frame consecutive 10
•
value—Specifies the number of consecutive
measurements. The range is from 1 to 10. The
default is 10.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-11
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Step 9
Command
Purpose
frame interval milliseconds
(Optional) Sets the gap between successive frames.
•
Example:
Router(config-sla-y1731-loss)# frame interval 100
Step 10
frame size bytes
(Optional) Configures padding size for frames.
•
Example:
Router(config-sla-y1731-loss)# frame size 32
Step 11
history interval intervals-stored
Example:
Router(config-sla-y1731-loss)# history interval 2
Step 12
owner owner-id
Example:
Router(config-sla-y1731-loss)# owner admin
Step 13
exit
milliseconds—Specifies the length of time in
milliseconds (ms) between successive synthetic
frames. The range is from 100 to 10000. The
default is 1000.
bytes—Specifies the padding size, in four-octet
increments, for the synthetic frames. The range is
from 64 to 384. The default is 64.
(Optional) Sets the number of statistics distributions
kept during the lifetime of an IP SLAs Ethernet
operation.
•
intervals-stored—Specifies the number of
statistics distributions. The range is from 1 to 10.
The default is 2.
(Optional) Configures the owner of an IP SLAs
operation.
•
owner-id—Specified the name of the SNMP
owner. The value is from 0 to 255 ASCII
characters.
Exits IP SLA Y.1731 loss configuration mode and
enters IP SLA configuration mode.
Example:
Router(config-sla-y1731-loss)# exit
Step 14
exit
Exits IP SLA configuration mode and enters global
configuration mode.
Example:
Router(config-ip-sla)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-12
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Step 15
Command
Purpose
ip sla reaction-configuration operation-number
[react {unavailableDS | unavailableSD | loss-ratioDS
| loss-ratioSD}] [threshold-type {average
[number-of-measurements] | consecutive [occurrences]
| immediate}] [threshold-value upper-threshold
lower-threshold]
(Optional) Configures proactive threshold
monitoring for frame loss measurements.
•
operation-number—Identifies the IP SLAs
operation for which reactions are to be
configured.
•
react—(Optional) Specifies the element to be
monitored for threshold violations.
•
unavailableDS—Specifies that a reaction should
occur if the percentage of destination-to-source
Frame Loss Ratio (FLR) violates the upper
threshold or lower threshold.
•
unavailableSD—Specifies that a reaction should
occur if the percentage of source-to-destination
FLR violates the upper threshold or lower
threshold.
•
loss-ratioDS—Specifies that a reaction should
occur if the one-way destination-to-source
loss-ratio violates the upper threshold or lower
threshold.
•
loss-ratioSD—Specifies that a reaction should
occur if the one way source-to-destination
loss-ratio violates the upper threshold or lower
threshold.
•
threshold-type average
[number-of-measurements]—(Optional) When
the average of a specified number of
measurements for the monitored element exceeds
the upper threshold or when the average of a
specified number of measurements for the
monitored element drops below the lower
threshold, perform the action defined by the
action-type keyword. The default number of 5
averaged measurements can be changed using the
number-of-measurements argument. The range is
from 1 to 16.
•
threshold-type consecutive
[occurrences]—(Optional) When a threshold
violation for the monitored element is met
consecutively for a specified number of times,
perform the action defined by the action-type
keyword.The default number of 5 consecutive
occurrences can be changed using the
occurrences argument. The range is from 1 to 16.
Example:
Router(config)# ip sla reaction-configuration 11
react unavailableDS
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-13
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure ITU-T Y.1731 Performance Monitoring
Command
Step 16
Purpose
ip sla logging traps
•
threshold-type immediate—(Optional) When a
threshold violation for the monitored element is
met, immediately perform the action defined by
the action-type keyword.
•
threshold-value upper-threshold
lower-threshold—(Optional) Specifies the
upper-threshold and lower-threshold values of
the applicable monitored elements.
(Optional) Enables IP SLAs syslog messages from
CISCO-RTTMON-MIB.
Example:
Router(config)# ip sla logging traps
Step 17
Exits global configuration mode and enters privileged
EXEC mode.
exit
Example:
Router(config)# exit
What to Do Next
After configuring this MEP, see the Scheduling IP SLAs Operations, page 11-14 to schedule the
operation.
Scheduling IP SLAs Operations
Complete the following steps to schedule an IP SLAs operation.
Prerequisites
•
All IP SLAs operations to be scheduled must be already configured.
•
The frequency of all operations scheduled in a multi-operation group must be the same.
•
List of one or more operation ID numbers to be added to a multi-operation group is limited to a
maximum of 125 characters, including commas (,).
1.
enable
2.
configure terminal
3.
Do one of the following:
SUMMARY STEPS
– ip sla schedule operation-number [life {forever | seconds}] [start-time {hh : mm[:ss] [month
day | day month] | pending | now | after hh : mm : ss}] [ageout seconds] [recurring]
– ip sla group schedule group-operation-number operation-id-numbers schedule-period
schedule-period-range [ageout seconds] [frequency group-operation-frequency] [life{forever
| seconds}] [start-time{hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]
4.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-14
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
Verifying the Frame Delay and Synthetic Loss Measurement Configurations
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Do one of the following:
•
•
ip sla schedule operation-number [life {forever
| seconds}] [start-time { hh : mm[: ss ] [month day
| day month ] | pending | now | after hh : mm :
ss}] [ageout seconds ] [recurring]
ip sla group schedule group-operation-number
operation-id-numbers schedule-period
schedule-period-range [ageout seconds]
[frequency group-operation-frequency]
[life{forever | seconds}] [start-time{hh:mm[ :ss ]
[ month day | day month] | pending | now | after
hh:mm:ss}]
Configures the scheduling parameters for an
individual IP SLAs operation.
Specifies an IP SLAs operation group number and the
range of operation numbers to be scheduled for a
multi-operation scheduler.
Example:
Router(config)# ip sla schedule 10 start-time now
life forever
Example:
Router(config)# ip sla group schedule 1 3,4,6-9
Step 4
Exits global configuration mode and enters privileged
EXEC mode.
exit
Example:
Router(config)# exit
Verifying the Frame Delay and Synthetic Loss Measurement
Configurations
•
Example: Verifying Sender MEP for a Two-Way Delay Measurement Operation, page 11-16
•
Example: Verifying Receiver MEP for a Two-Way Delay Measurement Operation, page 11-16
•
Example: Verifying Sender MEP for a Synthetic Loss Measurement Operation, page 11-17
•
Example: Verifying Ethernet CFM Performance Monitoring, page 11-17
•
Example: Verifying History for IP SLAs Operations, page 11-18
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-15
Chapter 11
ITU-T Y.1731 Performance Monitoring
Verifying the Frame Delay and Synthetic Loss Measurement Configurations
Example: Verifying Sender MEP for a Two-Way Delay Measurement Operation
The following sample output shows the configuration, including default values, of the sender MEP for a
two-way delay measurement operation:
Router# show ip sla configuration 10
IP SLAs Infrastructure Engine-III
Entry number: 10
Owner:
Tag:
Operation timeout (milliseconds): 5000
Ethernet Y1731 Delay Operation
Frame Type: DMM
Domain: xxx
Vlan: yyy
Target Mpid: 101
Source Mpid: 100
CoS: 4
Max Delay: 5000
Request size (Padding portion): 64
Frame Interval: 1000
Clock: Not In Sync
Threshold (milliseconds): 5000
.
.
.
Statistics Parameters
Aggregation Period: 900
Frame offset: 1
Distribution Delay Two-Way:
Number of Bins 10
Bin Boundaries: 5000,10000,15000,20000,25000,30000,35000,40000,45000,-1
Distribution Delay-Variation Two-Way:
Number of Bins 10
Bin Boundaries: 5000,10000,15000,20000,25000,30000,35000,40000,45000,-1
History
Number of intervals: 2
Example: Verifying Receiver MEP for a Two-Way Delay Measurement
Operation
The following sample output shows the configuration of the receiver MEP for a two-way delay
measurement operation:
Note
The Cisco ASR 901 router supports hardware-based timestamping. Enable the hardware-based
timestamping using the dmm responder hardware timestamp command on the receiver MEP.
Router-1# show running interface gigabitethernet0/0
interface GigabitEthernet0/0
no ip address
negotiation auto
service instance 1310 ethernet ssvc1310
encapsulation dot1q 1310
rewrite ingress tag pop 1 symmetric
bridge-domain 1310
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-16
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
Verifying the Frame Delay and Synthetic Loss Measurement Configurations
cfm mep domain sdmm mpid 1310
dmm responder hardware timestamp
Example: Verifying Sender MEP for a Synthetic Loss Measurement Operation
The following sample output shows the configuration, including default values, of the sender MEP for a
single-ended SLM operation with a start-time of now:
Router# show ip sla configuration 11
IP SLAs Infrastructure Engine-III
Entry number: 11
Owner:
Tag:
Operation timeout (milliseconds): 5000
Ethernet Y1731 Loss Operation
Frame Type: SLM
Domain: xxx
Vlan: 12
Target Mpid: 34
Source Mpid: 23
CoS: 4
Request size (Padding portion): 0
Frame Interval: 1000
Schedule:
Operation frequency (seconds): 60 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): ActiveThreshold (milliseconds): 5000
Statistics Parameters
Aggregation Period: 900
Frame consecutive: 10
Availability algorithm: static-window
History
Number of intervals: 2
Example: Verifying Ethernet CFM Performance Monitoring
To view the Ethernet CFM performance monitoring activities, use the show ethernet cfm pm command.
Router# show ethernet cfm pm session summary
Number of Configured Session : 4
Number of Active Session: 4
Number of Inactive Session: 0
Router# show ethernet cfm pm session detail 1
Session ID: 1
Sla Session ID: 2002
Level: 5
Service Type: BD-V
Service Id: 1000
Direction: Down
Source Mac: 4055.3989.736d
Destination Mac: 4055.3989.6c01
Session Version: 0
Session Operation: On-demand
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-17
Chapter 11
ITU-T Y.1731 Performance Monitoring
Verifying the Frame Delay and Synthetic Loss Measurement Configurations
Session Status: Active
MPID: 1000
Tx active: yes
Rx active: yes
RP monitor Tx active: yes
RP monitor Rx active: yes
Timeout timer: stopped
Last clearing of counters: *13:39:29.070 IST Mon Mar 18 2013
DMMs:
Transmitted: 0
DMRs:
Rcvd: 0
1DMs:
Transmitted: 0
Rcvd: 0
LMMs:
Transmitted: 0
LMRs:
Rcvd: 0
VSMs:
Transmitted: 0
VSRs:
Rcvd: 0
SLMs:
Transmitted: 517100
SLRs:
Rcvd: 517098
Example: Verifying History for IP SLAs Operations
To view the history collected for IP SLAs operations, use the show ip sla history command.
Note
The show ip sla history full command is not supported for the ITU-T Y.1731 operations.
Router# show ip sla history interval-statistics
Loss Statistics for Y1731 Operation 2001
Type of operation: Y1731 Loss Measurement
Latest operation start time: *13:48:39.055 IST Tue Mar 19 2013
Latest operation return code: OK
Distribution Statistics:
Interval 1
Start time: *13:48:39.055 IST Tue Mar 19 2013
End time: *13:48:59.055 IST Tue Mar 19 2013
Number of measurements initiated: 198
Number of measurements completed: 198
Flag: OK
Forward
Number of Observations 19
Available indicators: 19
Unavailable indicators: 0
Tx frame count: 190
Rx frame count: 190
Min/Avg/Max - (FLR % ): 0:9/000.00%/0:9
Cumulative - (FLR % ): 000.0000%
Timestamps forward:
Min - *13:48:58.084 IST Tue Mar 19 2013
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-18
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure IP SLAs Y.1731 On-Demand and Concurrent Operations
Max - *13:48:58.084 IST Tue Mar 19 2013
Backward
Number of Observations 19
Available indicators: 19
Unavailable indicators: 0
Tx frame count: 190
Rx frame count: 190
Min/Avg/Max - (FLR % ): 0:9/000.00%/0:9
Cumulative - (FLR % ): 000.0000%
Timestamps backward:
Min - *13:48:58.084 IST Tue Mar 19 2013
Max - *13:48:58.084 IST Tue Mar 19 2013
How to Configure IP SLAs Y.1731 On-Demand and Concurrent
Operations
•
Configuring Direct On-Demand Operation on a Sender MEP, page 11-19
•
Configuring Referenced On-Demand Operation on a Sender MEP, page 11-20
•
Configuring IP SLAs Y.1731 Concurrent Operation on a Sender MEP, page 11-21
Configuring Direct On-Demand Operation on a Sender MEP
Prerequisites
Class of Service (CoS)-level monitoring must be enabled on MEPs associated to the Ethernet frame loss
operation using the monitor loss counter command on the devices at both ends of the operation.
Note
Cisco IOS Y.1731 implementation allows monitoring of frame loss for frames on an EVC regardless of
the CoS value (any CoS or Aggregate CoS cases).
SUMMARY STEPS
1.
enable
2.
ip sla on-demand ethernet slm domain domain-name {evc evc-id | vlan vlan-id} {mpid
target-mp-id | mac-address target-address} cos cos {source {mpid source-mp-id | mac-address
source-address}} {continuous [interval milliseconds] | burst [interval milliseconds] [number
number-of-frames] [frequency seconds]} [size bytes] aggregation seconds {duration seconds |
max number-of-packets}
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-19
Chapter 11
ITU-T Y.1731 Performance Monitoring
How to Configure IP SLAs Y.1731 On-Demand and Concurrent Operations
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
ip sla on-demand ethernet slm domain domain-name
{evc evc-id | vlan vlan-id} {mpid target-mp-id |
mac-address target-address} cos cos { source { mpid
source-mp-id | mac-address source-address}}
{continuous [interval milliseconds] | burst [interval
milliseconds] [ number number-of-frames] [frequency
seconds]} [ size bytes] aggregation seconds {duration
seconds | max number-of-packets}
Creates and runs an on-demand operation in direct
mode.
Repeat this step for each on-demand operation to be
run.
Example:
Router# ip sla on-demand ethernet SLM domain xxx
vlan 12 mpid 34 cos 4 source mpid 23 continuous
aggregation 10 duration 60
Configuring Referenced On-Demand Operation on a Sender MEP
Prerequisites
Single-ended and concurrent Ethernet delay, or delay variation, and frame loss operations to be
referenced must be configured.
SUMMARY STEPS
1.
enable
2.
ip sla on-demand ethernet slm operation number {duration seconds | max number-of-packets}
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
{duration seconds | max number-of-packets}
Creates and runs a pseudo operation of the operation
being referenced, in the background.
Example:
Repeat this step for each on-demand operation to be
run.
ip sla on-demand ethernet slm operation number
Router# ip sla on-demand ethernet slm 11
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-20
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
Configuration Examples for IP SLAs Y.1731 On-Demand Operations
Configuring IP SLAs Y.1731 Concurrent Operation on a Sender MEP
To configure concurrent Ethernet delay, and delay variation, and frame loss operations, see the “How to
Configure ITU-T Y.1731 Performance Monitoring” section on page 11-5.
Configuration Examples for IP SLAs Y.1731 On-Demand
Operations
•
Example: On-Demand Operation in Direct Mode, page 11-21
•
Example: On-Demand Operation in Referenced Mode, page 11-22
Example: On-Demand Operation in Direct Mode
Router# ip sla on-demand ethernet slm domain md5 evc evc1000 mpid 1000 cos 1 source mpid
1001 continuous aggregation 30 duration 31
Loss Statistics for Y1731 Operation 3313031511
Type of operation: Y1731 Loss Measurement
Latest operation start time: *13:21:23.995 IST Tue Mar 19 2013
Latest operation return code: OK
Distribution Statistics:
Interval
Start time: *13:21:23.995 IST Tue Mar 19 2013
End time: *13:21:53.988 IST Tue Mar 19 2013
Number of measurements initiated: 30
Number of measurements completed: 30
Flag: OK
Forward
Number of Observations 3
Available indicators: 0
Unavailable indicators: 3
Tx frame count: 30
Rx frame count: 30
Min/Avg/Max - (FLR % ): 0:9/000.00%/0:9
Cumulative - (FLR % ): 000.0000%
Timestamps forward:
Min - *13:21:53.030 IST Tue Mar 19 2013
Max - *13:21:53.030 IST Tue Mar 19 2013
Backward
Number of Observations 3
Available indicators: 0
Unavailable indicators: 3
Tx frame count: 30
Rx frame count: 30
Min/Avg/Max - (FLR % ): 0:9/000.00%/0:9
Cumulative - (FLR % ): 000.0000%
Timestamps backward:
Min - *13:21:53.030 IST Tue Mar 19 2013
Max - *13:21:53.030 IST Tue Mar 19 2013
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-21
Chapter 11
ITU-T Y.1731 Performance Monitoring
Configuration Examples for IP SLAs Y.1731 On-Demand Operations
Example: On-Demand Operation in Referenced Mode
Router# configure terminal
Router(config)# ip sla 2002
Router(config-ip-sla)# ethernet y1731 loss SLM domain md5 evc evc1000 mpid 1001 cos 3
source mpid 1000
Router(config-sla-y1731-loss)# aggregate interval 30
Router(config-sla-y1731-loss)# end
Router# ip sla on-demand ethernet slm 2002 duration 31
Loss Statistics for Y1731 Operation 3313031511
Type of operation: Y1731 Loss Measurement
Latest operation start time: *13:21:23.995 IST Tue Mar 19 2013
Latest operation return code: OK
Distribution Statistics:
Interval
Start time: *13:21:23.995 IST Tue Mar 19 2013
End time: *13:21:53.988 IST Tue Mar 19 2013
Number of measurements initiated: 30
Number of measurements completed: 30
Flag: OK
Forward
Number of Observations 3
Available indicators: 0
Unavailable indicators: 3
Tx frame count: 30
Rx frame count: 30
Min/Avg/Max - (FLR % ): 0:9/000.00%/0:9
Cumulative - (FLR % ): 000.0000%
Timestamps forward:
Min - *13:21:53.030 IST Tue Mar 19 2013
Max - *13:21:53.030 IST Tue Mar 19 2013
Backward
Number of Observations 3
Available indicators: 0
Unavailable indicators: 3
Tx frame count: 30
Rx frame count: 30
Min/Avg/Max - (FLR % ): 0:9/000.00%/0:9
Cumulative - (FLR % ): 000.0000%
Timestamps backward:
Min - *13:21:53.030 IST Tue Mar 19 2013
Max - *13:21:53.030 IST Tue Mar 19 2013
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-22
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
Additional References
Additional References
The following sections provide references to ITU-T Y.1731 Performance Monitoring.
Related Documents
Related Topic
Document Title
Cisco IOS Commands
Cisco IOS Master Commands List, All Releases
Cisco IOS IP SLAs commands
Cisco IOS IP SLAs Command Reference
IEEE CFM
Configuring IEEE Standard-Compliant Ethernet CFM in a Service
Provider Network
Using OAM
Using Ethernet Operations, Administration, and Maintenance
IEEE CFM and Y.1731 commands
Cisco IOS Carrier Ethernet Command Reference
Standards
Standard
Title
IEEE 802.1ag
802.1ag - Connectivity Fault Management
ITU-T Y.1731
ITU-T Y.1731 OAM Mechanisms for Ethernet-Based Networks
MEF 17
Service OAM Requirements & Framework - Phase 1
MIBs
MIB
MIBs Link
CISCO-IPSLA-ETHERNET-MIB
To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
CISCO-RTTMON-MIB
http://www.cisco.com/go/mibs
RFCs
RFC
Title
None
—
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-23
Chapter 11
ITU-T Y.1731 Performance Monitoring
Additional References
Technical Assistance
Description
Link
http://www.cisco.com/cisco/web/support/index.html
The Cisco Technical Support website contains
thousands of pages of searchable technical content,
including links to products, technologies, solutions,
technical tips, and tools. Registered Cisco.com users
can log in from this page to access even more content.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-24
OL-23826-09
Chapter 11
ITU-T Y.1731 Performance Monitoring
Feature Information for ITU-T Y.1731 Performance Monitoring
Feature Information for ITU-T Y.1731 Performance Monitoring
Table 11-1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 11-1
Table 11-1 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for ITU-T Y.1731 Performance Monitoring
Feature Name
Releases
Feature Information
Y.1731 Performance Monitoring
15.3(2)S
This feature was introduced on the Cisco ASR 901 router.
The following sections provide information about this
feature:
Ethernet Synthetic Loss Measurement in
Y.1731
Y.1731 Performance Monitoring
15.3(2)S
•
Information About ITU-T Y.1731 Performance
Monitoring, page 11-2
•
How to Configure ITU-T Y.1731 Performance
Monitoring, page 11-5
•
Verifying the Frame Delay and Synthetic Loss
Measurement Configurations, page 11-15
This feature was introduced on the Cisco ASR 901 router.
The following sections provide information about this
feature:
15.3(3)S
•
Information About ITU-T Y.1731 Performance
Monitoring, page 11-2
•
Configuring Single-Ended Synthetic Loss
Measurement, page 11-9
•
Verifying the Frame Delay and Synthetic Loss
Measurement Configurations, page 11-15
The Cisco ASR 901 router supports ITU-T Y.1731
performance monitoring on the following interfaces:
–SLM support on the EVC cross connect
–SLM support on the Port-Channel EVC cross connect
–DMM and SLM support on the EVC BD for both the up
and down MEPs
–SLM support on the EVC cross connect for both the up and
down MEPs
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
11-25
Chapter 11
ITU-T Y.1731 Performance Monitoring
Feature Information for ITU-T Y.1731 Performance Monitoring
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
11-26
OL-23826-09
CH A P T E R
12
Configuring Resilient Ethernet Protocol
Resilient Ethernet Protocol (REP) is a Cisco proprietary protocol that provides an alternative to
Spanning Tree Protocol (STP) to control network loops, to respond to link failures, and to improve
convergence time. REP controls a group of ports connected in a segment, ensures that the segment does
not create any bridging loops, and responds to link failures within the segment. REP provides a basis for
constructing more complex networks and supports VLAN load balancing. Effective with Cisco IOS
Release 15.4(1)S, the Cisco ASR 901 supports REP over port-channel.
Contents
•
Understanding Resilient Ethernet Protocol (REP), page 12-1
•
Configuring Resilient Ethernet Protocol (REP), page 12-7
•
Configuration Examples for REP, page 12-24
Understanding Resilient Ethernet Protocol (REP)
This section contains the following topics:
•
Overview
•
Restrictions, page 12-3
•
Link Integrity
•
Fast Convergence
•
VLAN Load Balancing (VLB)
•
REP Ports
Overview
An REP segment is a chain of ports connected to each other and configured with a segment ID. Each
segment consists of standard (non-edge) segment ports and two user-configured edge ports. A switch can
have only two ports belonging to the same segment, and each segment port can have only one external
neighbor. A segment can go through a shared medium, but on any link, only two ports can belong to the
same segment. REP is supported only on Layer 2 trunk interfaces.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-1
Chapter 12
Configuring Resilient Ethernet Protocol
Understanding Resilient Ethernet Protocol (REP)
Figure 12-1 shows an example of a segment consisting of six ports spread across four switches. Ports E1
and E2 are configured as edge ports. When all ports are operational (as in the segment on the left), a
single port is blocked, shown by the diagonal line. When there is a network failure, as shown on the right
of the diagram, the blocked port returns to the forwarding state to minimize network disruption.
Figure 12-1
REP Open Segments
E1
Edge port
Blocked port
Link failure
E2
E1
E2
201888
E1
The segment shown in Figure 12-1 is an open segment; there is no connectivity between the two edge
ports. The REP segment cannot cause a bridging loop, and you can safely connect the segment edges to
any network. All hosts connected to switches inside the segment have two possible connections to the
rest of the network through the edge ports, but only one connection is accessible at any time. If a host
cannot access its usual gateway because of a failure, REP unblocks all ports to ensure that connectivity
is available through the other gateway.
The segment shown in Figure 12-2, with both edge ports located on the same switch, is a ring segment.
In this configuration, there is connectivity between the edge ports through the segment. With this
configuration, you can create a redundant connection between any two switches in the segment.
Figure 12-2
REP Ring Segment
E2
201889
E1
REP segments have these characteristics:
•
If all ports in the segment are operational, one port (referred to as the alternate port) is in the blocked
state for each VLAN.
•
If VLAN load balancing is configured, two ports in the segment control the blocked state of VLANs.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-2
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Understanding Resilient Ethernet Protocol (REP)
•
If one or more ports in a segment is not operational, causing a link failure, all ports forward traffic
on all VLANs to ensure connectivity.
•
In case of a link failure, the alternate ports are unblocked as quickly as possible. When the failed
link comes back up, a logically blocked port per VLAN is selected with minimal disruption to the
network.
You can construct almost any type of network based on REP segments. REP also supports VLAN
load-balancing, controlled by the primary edge port but occurring at any port in the segment.
In access ring topologies, the neighboring switch might not support REP, as shown in Figure 12-3. In
this case, you can configure the non-REP facing ports (E1 and E2) as edge no-neighbor ports. These
ports inherit all properties of edge ports, and you can configure them the same as any edge port, including
configuring them to send STP or REP topology change notices to the aggregation switch. In this case the
STP topology change notice (TCN) that is sent is a multiple spanning-tree (MST) STP message.
Figure 12-3
No-neighbor Topology
E1
REP not
supported
273792
E1 and E2 are configured
as edge no-neighbor ports
E2
REP ports
Restrictions
•
You must configure each segment port; an incorrect configuration can cause forwarding loops in the
networks.
•
REP can manage only a single failed port within the segment; multiple port failures within the REP
segment cause loss of network connectivity.
•
You should configure REP only in networks with redundancy. Configuring REP in a network
without redundancy causes loss of connectivity.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-3
Chapter 12
Configuring Resilient Ethernet Protocol
Understanding Resilient Ethernet Protocol (REP)
Link Integrity
REP does not use an end-to-end polling mechanism between edge ports to verify link integrity. It
implements local link failure detection. The REP Link Status Layer (LSL) detects its REP-aware
neighbor and establishes connectivity within the segment. All VLANs are blocked on an interface until
it detects the neighbor. After the neighbor is identified, REP determines which neighbor port should
become the alternate port and which ports should forward traffic.
Each port in a segment has a unique port ID. The port ID format is similar to that used by the spanning
tree algorithm: a port number (unique on the bridge), associated to a MAC address (unique in the
network). When a segment port is coming up, its LSL starts sending packets that include the segment ID
and the port ID. The port is declared operational after it performs a three-way handshake with a neighbor
in the same segment.
A segment port does not become operational if:
•
No neighbor has the same segment ID.
•
More than one neighbor has the same segment ID.
•
The neighbor does not acknowledge the local port as a peer.
Each port creates an adjacency with its immediate neighbor. After the neighbor adjacencies are created,
the ports negotiate to determine one blocked port for the segment, the alternate port. All other ports
become unblocked. By default, REP packets are sent to a BPDU class MAC address. The packets are
dropped by devices not running REP.
Fast Convergence
Because REP runs on a physical link basis and not a per-VLAN basis, only one hello message is required
for all VLANs, reducing the load on the protocol. We recommend that you create VLANs consistently
on all switches in a given segment and configure the same allowed VLANs on the REP trunk ports. To
avoid the delay introduced by relaying messages in software, REP also allows some packets to be
flooded to a regular multicast address. These messages operate at the hardware flood layer (HFL) and
are flooded to the whole network, not just the REP segment. Switches that do not belong to the segment
treat them as data traffic. You can control flooding of these messages by configuring a dedicated
administrative VLAN for the whole domain.
The estimated convergence recovery time on fiber interfaces is less than 200 ms for the local segment
with 200 VLANs configured. Convergence for VLAN load balancing is 300 ms or less.
VLAN Load Balancing (VLB)
One edge port in the REP segment acts as the primary edge port; the other as the secondary edge port.
The primary edge port always participates in VLAN load balancing in the segment. REP VLAN
balancing is achieved by blocking some VLANs at a configured alternate port and all other VLANs at
the primary edge port. When you configure VLAN load balancing, you can specify the alternate port in
one of three ways:
•
Enter the port ID of the interface. To identify the port ID of a port in the segment, use the show
interface rep detail interface configuration command for the port.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-4
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Understanding Resilient Ethernet Protocol (REP)
Note
Use rep platform vld segment command on every Cisco ASR 901 router participating in the REP
segment.
Enter the neighbor offset number of a port in the segment, which identifies the downstream neighbor
port of an edge port. The neighbor offset number range is –256 to +256; a value of 0 is invalid. The
primary edge port has an offset number of 1; positive numbers above 1 identify downstream
neighbors of the primary edge port. Negative numbers identify the secondary edge port (offset
number -1) and its downstream neighbors.
•
You configure offset numbers on the primary edge port by identifying the downstream position
from the primary (or secondary) edge port. Do not enter an offset value of 1 because that is the
offset number of the primary edge port.
Note
Figure 12-4 shows neighbor offset numbers for a segment where E1 is the primary edge port and E2
is the secondary edge port. The red numbers inside the ring are numbers offset from the primary
edge port; the black numbers outside the ring show the offset numbers from the secondary edge port.
Note that you can identify all ports (except the primary edge port) by either a positive offset number
(downstream position from the primary edge port) or a negative offset number (downstream position
from the secondary edge port). If E2 became the primary edge port, its offset number would then
be 1, and E1 would be -1.
•
By entering the preferred keyword to select the port that you previously configured as the preferred
alternate port with the rep segment segment-id preferred interface configuration command.
Figure 12-4
Neighbor Offset Numbers in a Segment
-1
-9 2
E1
1
E2
10
E1 = Primary edge port
E2 = Secondary edge port
9
-2
Offset numbers from the primary edge port
Offset numbers from the secondary edge
port (negative numbers)
8 -3
-8 3
7
-7
5
-6
6
-5
-4
201890
4
When the REP segment is complete, all VLANs are blocked. When you configure VLAN load balancing,
you must also configure triggers in one of two ways:
•
Manually trigger VLAN load balancing at any time by entering the rep preempt segment
segment-id privileged EXEC command on the router that has the primary edge port.
•
Configure a preempt delay time by entering the rep preempt delay seconds interface configuration
command. After a link failure and recovery, VLAN load balancing begins after the configured
preemption time period elapses. Note that the delay timer restarts if another port fails before the time
elapses.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-5
Chapter 12
Configuring Resilient Ethernet Protocol
Understanding Resilient Ethernet Protocol (REP)
Note
When VLAN load balancing is configured, it does not start working until triggered by either manual
intervention or a link failure and recovery.
When VLAN load balancing is triggered, the primary edge port sends a message to alert all interfaces in
the segment about the preemption. When the secondary port receives the message, it is reflected into the
network to notify the alternate port to block the set of VLANs specified in the message and to notify the
primary edge port to block the remaining VLANs.
You can also configure a particular port in the segment to block all VLANs. Only the primary edge port
initiates VLAN load balancing, which is not possible if the segment is not terminated by an edge port on
each end. The primary edge port determines the local VLAN load balancing configuration.
Reconfigure the primary edge port to reconfigure load balancing. When you change the load balancing
configuration, the primary edge port again waits for the rep preempt segment command or for the
configured preempt delay period after a port failure and recovery before executing the new
configuration. If you change an edge port to a regular segment port, the existing VLAN load balancing
status does not change. Configuring a new edge port might cause a new topology configuration.
Spanning Tree Interaction
REP does not interact with MSTP, but the two can coexist. A port that belongs to a segment is removed
from spanning tree control, and STP BPDUs are not accepted or sent from segment ports.
To migrate from an STP ring configuration to REP segment configuration, begin by configuring a single
port in the ring as part of the segment, and continue by configuring contiguous ports to minimize the
number of segments. Each segment always contains a blocked port, so multiple segments means multiple
blocked ports and a potential loss of connectivity. When the segment is configured in both directions to
the edge ports, you then configure the edge ports.
REP Ports
Ports in REP segments are in the Failed, Open, or Alternate states. The various states REP ports go
through are as follows:
•
A port configured as a regular segment port starts as a failed port.
•
After the neighbor adjacencies are determined, the port changes to alternate port state, blocking all
VLANs on the interface. Blocked port negotiations occur and when the segment settles, one blocked
port remains in the alternate role, and all other ports become open ports.
•
When a failure occurs in a link, all ports move to the open state. When the alternate port receives
the failure notification, it changes to the open state, forwarding all VLANs.
A regular segment port converted to an edge port, or an edge port converted to a regular segment port,
does not always result in a topology change. If you convert an edge port into a regular segment port,
VLAN load balancing is not implemented unless it has been configured. For VLAN load balancing, you
must configure two edge ports in the segment.
A segment port reconfigured as a spanning tree port restarts according to the spanning tree configuration.
By default, this is a designated blocking port. If PortFast is configured or if STP is disabled, the port
goes into the forwarding state.
For instructions on how to configure REP, see Configuring Resilient Ethernet Protocol (REP), page 12-7.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-6
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Configuring Resilient Ethernet Protocol (REP)
A segment is a collection of ports connected one to the other in a chain and configured with a segment
ID. To configure REP segments, you configure the REP administrative VLAN (or use the default
VLAN 1) and then add the ports to the segment using interface configuration mode. You should
configure a service instance with encapsulation corresponding to the REP admin VLAN and associate it
to arbitratory bridge domain.
Note
The explicit configuration of EFP gives you the flexibility to choose the bridge domain of your choice.
You should configure two edge ports in the segment, one as the primary edge port and the other, by
default, the secondary edge port. A segment has only one primary edge port. If you configure two ports
in a segment as the primary edge port, for example ports on different switches, the REP selects one to
serve as the segment primary edge port. You can also optionally configure where to send segment
topology change notices (STCNs) and VLAN load balancing messages.
This section contains the following topics:
•
Default REP Configuration, page 12-7
•
REP Configuration Guidelines, page 12-7
•
Configuring the REP Administrative VLAN, page 12-9
•
Configuring REP Interfaces, page 12-10
•
Configuring REP as Dual Edge No-Neighbor Port, page 12-15
•
Setting up Manual Preemption for VLAN Load Balancing, page 12-20
•
Configuring SNMP Traps for REP, page 12-21
•
Monitoring REP, page 12-22
Default REP Configuration
By default, REP is disabled on all interfaces. When enabled, the interface is a regular segment port,
unless it is configured as an edge port.
When REP is enabled, the sending of segment topology change notices (STCNs) is disabled, all VLANs
are blocked, and the administrative VLAN is VLAN 1.
When VLAN load balancing is enabled, the default is manual preemption with the delay timer disabled.
If VLAN load balancing is not configured, the default after manual preemption is to block all VLANs at
the primary edge port.
REP Configuration Guidelines
Follow these guidelines when configuring REP:
•
We recommend that you begin by configuring one port and then configure the contiguous ports to
minimize the number of segments and the number of blocked ports.
•
If more than two ports in a segment fail when no external neighbors are configured, one port goes
into a forwarding state for the data path to help maintain connectivity during configuration. In the
show rep interface command output, the Port Role for this port shows as Fail Logical Open; the
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-7
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Port Role for the other failed port shows as Fail No Ext Neighbor. When the external neighbors for
the failed ports are configured, the ports go through the alternate port state transitions and eventually
go to an open state or remain as the alternate port, based on the alternate port election mechanism.
•
REP ports must be Layer 2 ports.
•
Be careful when configuring REP through a Telnet connection. Since REP blocks all VLANs until
another REP interface sends a message to unblock the VLAN, you might lose connectivity to the
router if you enable REP in a Telnet session that accesses the router through the REP interface.
•
If you connect an STP network to the REP segment, be sure that the connection is at the segment
edge. An STP connection that is not at the edge could cause a bridging loop because STP does not
run on REP segments. All STP BPDUs are dropped at REP interfaces.
•
You must configure all ports in the segment with the same set of allowed VLANs, or a
misconfiguration occurs.
•
REP ports follow these rules:
– There is no limit to the number of REP ports on a switch; however, only two ports on a switch
can belong to the same REP segment.
– If only one port on a switch is configured in a segment, the port should be an edge port.
– If two ports on a switch belong to the same segment, they must be both edge ports, both regular
segment ports, or one regular port and one edge no-neighbor port. An edge port and regular
segment port on a switch cannot belong to the same segment.
– If two ports on a switch belong to the same segment and one is configured as an edge port and
one as a regular segment port (a misconfiguration), the edge port is treated as a regular segment
port.
•
REP interfaces come up and remain in a blocked state until notified that it is safe to unblock. You
need to be aware of this to avoid sudden connection losses.
•
You should configure service instance with encapsulation corresponding to the REP admin VLAN
and associate it to arbitratory Bridge Domain. This explicit configuration of EFP gives you the
flexibility to choose the bridge domain of your choice.
•
REP sends all LSL PDUs in untagged frames on the native VLAN. The BPA message sent to the
Cisco multicast address is sent on the administration VLAN, which is VLAN 1 by default.
•
You can configure how long a REP interface remains up without receiving a hello from a neighbor.
You can use the rep lsl-age-timer value interface configuration command to set the time from 120
ms to 10000 ms. The LSL hello timer is then set to the age-timer value divided by three. In normal
operation, three LSL hellos are sent before the age timer on the peer switch expires and searches for
hello messages.
•
You can configure how long a REP interface remains up without receiving a hello from a neighbor.
You can use the rep lsl-age-timer value interface configuration command to set the time from 120
ms to 10000 ms. The LSL hello timer is then set to the age-timer value divided by three. In normal
operation, three LSL hellos are sent before the age timer on the peer switch expires and searches for
hello messages.
•
REP ports cannot be configured as one of these port types:
– SPAN destination port
– Private VLAN
– Tunnel port
– Access port
•
There is a maximum of 128 REP segments per router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-8
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Configuring the REP Administrative VLAN
To avoid the delay introduced by relaying messages in software for link-failure or VLAN-blocking
notification during load balancing, REP floods packets at the hardware flood layer (HFL) to a regular
multicast address. These messages are flooded to the whole network, not just the REP segment. You can
control flooding of these messages by configuring an administrative VLAN for the whole domain.
Follow these guidelines when configuring the REP administrative VLAN:
•
If you do not configure an administrative VLAN, the default is VLAN 1.
•
There can be only one administrative VLAN on a router and on a segment. However, this is not
enforced by the software.
•
For VLB to work, rep platform vlb has to be configured on every Cisco ASR 901router
participating in the segment.
Complete the following steps to configure the REP administrative VLAN:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
rep admin vlan vlan-id
4.
end
5.
show interface [interface-id] rep [detail]
6.
copy running-config startup config
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
rep admin vlan vlan-id
Configures a REP administrative VLAN.
•
Example:
Specify the administrative VLAN. The range is
1–4094. The default is VLAN 1.
Router(config)# rep admin vlan 1
Step 4
end
Returns to privileged EXEC mode.
Example:
Router(config)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-9
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Step 5
Command
Purpose
show interface [interface-id] rep [detail]
Displays the REP configuration and status for a specified
interface.
•
Example:
Router# show interface gigabitethernet0/1 rep
detail
Step 6
copy running-config startup config
Enter the physical Layer 2 interface or port channel
(logical interface) and the optional detail keyword, if
desired.
(Optional) Saves your entries in the router startup
configuration file.
Example:
Router# copy running-config startup config
Configuring REP Interfaces
For REP operation, you need to enable it on each segment interface and identify the segment ID. This
step is required and must be done before other REP configuration. You must also configure a primary
and secondary edge port on each segment. All other steps are optional.
Complete these steps to enable and configure REP on an interface:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface interface-id
4.
service instance <instance-id> ethernet encap dot1q <admin-vlan> rewrite ingress tag pop 1
symmetric bridge-domain <bd-id>
5.
rep segment segment-id [edge [no-neighbor] [primary]] [preferred]
6.
rep lsl-retries number-of-retries
7.
rep stcn {interface interface-id | segment id-list | stp}
8.
rep platform vlb segment segment-id vlan {vlan-list|all}
9.
rep block port {id port-id | neighbor-offset | preferred} vlan {vlan-list | all}
10. rep preempt delay seconds
11. rep lsl-age-timer value
12. end
13. show interface [interface-id] rep [detail]
14. show rep topology [segment segment-id] [archive] [detail]
15. copy running-config startup config
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-10
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Specifies the interface, and enters interface configuration mode.
interface interface-id
•
Example:
Enter the physical Layer 2 interface or port channel ID. The
port-channel range is 1 to 8.
Router(config)# interface
gigabitethernet0/1
Router(config)# interface port-channel 1
Step 4
Configures ethernet virtual circuit for the administrative VLAN.
service instance <instance-id>
ethernet encap dot1q <admin-vlan>
rewrite ingress tag pop 1 symmetric
bridge-domain <bd-id>
Example:
Router(config-if)# service instance 1
ethernet encap dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-11
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Step 5
Command
Purpose
rep segment segment-id [edge [no-neighbor]
[primary]] [preferred]
Enables REP on the interface, and identifies a segment number. The
segment ID range is from 1 to 1024.
Note
Example:
Router(config-if)# rep segment 1 edge
preferred
These are the optional keywords:
•
Enter the edge keyword to configure the port as an edge port.
Entering edge without the primary keyword configures the
port as the secondary edge port. Each segment has only two
edge ports.
•
(Optional) Enter the no-neighbor keyword to configure a port
with no external REP neighbors as an edge port. The port
inherits all properties of edge ports, and you can configure them
the same as any edge port.
•
On an edge port, enter the primary keyword to configure the
port as the primary edge port, the port on which you can
configure VLAN load balancing.
Note
•
Note
Step 6
rep lsl-retries number-of-retries
You must configure two edge ports, including one primary
edge port for each segment.
Although each segment can have only one primary edge
port, if you configure edge ports on two different switches
and enter the primary keyword on both switches, the
configuration is allowed. However, REP selects only one of
these ports as the segment primary edge port. You can
identify the primary edge port for a segment by entering the
show rep topology privileged EXEC command.
Enter the preferred keyword to indicate that the port is the
preferred alternate port or the preferred port for VLAN load
balancing.
Configuring a port as preferred does not guarantee that it
becomes the alternate port; it merely gives it a slight edge
among equal contenders. The alternate port is usually a
previously failed port.
Use the rep lsl-retries command to configure the REP link status
layer (LSL) number of retries before the REP link is disabled.
Example:
Router(config-if)# rep lsl-retries 4
Step 7
rep stcn {interface interface-id |
segment id-list | stp}
(Optional) Configures the edge port to send segment topology
change notices (STCNs).
•
Enter interface interface-id to designate a physical Layer 2
interface or port channel to receive STCNs.
•
Enter segment id-list to identify one or more segments to
receive STCNs. The range is from 1–1024.
•
Enter stp to send STCNs to STP networks.
Example:
Router(config-if)# rep stcn segment 2-5
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-12
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Step 8
Command
Purpose
rep platform vlb segment segment-id vlan
{vlan-list|all}
(Optional) Configures the VLAN list which forms the VLB group.
This command should be issued on all Cisco ASR 901 routers
participating in VLB for a particular segment and should have a
matching VLAN list. This VLAN list should also match with the
rep block command issued on primary edge port.
Example:
Router(config)# rep platform vlb segment
1 vlan 100-200
Step 9
•
Enter vlan vlan-list to block a single VLAN or a range of
VLANs,
•
Enter vlan all to block all VLANs. This is the default
configuration.
(Optional) Configures VLAN load balancing on the primary edge
port, identifies the REP alternate port in one of three ways, and
configures the VLANs to be blocked on the alternate port.
rep block port {id port-id |
neighbor-offset | preferred} vlan
{vlan-list | all}
Example:
•
Enter the id port-id to identify the alternate port by port ID. The
port ID is automatically generated for each port in the segment.
You can view interface port IDs by entering the show interface
interface-id rep [detail] privileged EXEC command.
•
Enter a neighbor-offset number to identify the alternate port as
a downstream neighbor from an edge port. The range is from
–256 to 256, with negative numbers indicating the downstream
neighbor from the secondary edge port. A value of 0 is invalid.
Enter -1 to identify the secondary edge port as the alternate
port.
Router(config-if)# rep block port
0009001818D68700 vlan all
Note
•
Enter the preferred keyword to select the regular segment port
previously identified as the preferred alternate port for VLAN
load balancing.
•
Enter vlan vlan-list to block one VLAN or a range of VLANs.
•
Enter vlan all to block all VLANs.
Note
Step 10 rep preempt delay seconds
Example:
Router(config-if)# rep preempt delay 60
Example:
Router(config-if) rep lsl-age-timer 5000
Enter this command only on the REP primary edge port.
(Optional) Configures a preempt time delay. Use this command if
you want VLAN load balancing to automatically trigger after a link
failure and recovery. The time delay range is 15 to 300 seconds. The
default is manual preemption with no time delay.
Note
Step 11 rep lsl-age-timer value
Because you enter this command at the primary edge port
(offset number 1), you would never enter an offset value of
1 to identify an alternate port.
Use this command only on the REP primary edge port.
(Optional) Configure a time (in milliseconds) for which the REP
interface remains up without receiving a hello from a neighbor. The
range is from 120 to 10000 ms in 40-ms increments; the default is
5000 ms (5 seconds).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-13
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Command
Step 12 end
Purpose
Returns to privileged EXEC mode.
Example:
Router(config-if)# end
Step 13 show interface [interface-id] rep
Verifies the REP interface configuration.
[detail]
•
Enter the physical Layer 2 interface or port channel (logical
interface) and the optional detail keyword, if desired.
Example:
Router# show interface gigabitethernet0/1
rep detail
Step 14 show rep topology [segment segment-id]
Indicates which port in the segment is the primary edge port.
[archive] [detail]
Example:
Router# show rep topology segment 1
Step 15 copy running-config startup config
(Optional) Saves your entries in the router startup configuration
file.
Example:
Router# copy running-config startup
config
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-14
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Configuring REP as Dual Edge No-Neighbor Port
For REP operation, you need to enable it on each segment interface and identify the segment ID.
Effective with Cisco IOS release 15.4.(1)S, you can configure the non-REP switch facing ports on a
single device as dual edge no-neighbor ports. These ports inherit all properties of edge ports, and
overcome the limitation of not converging quickly during a failure.
Figure 12-5
Dual Edge No-neighbor Topology
REP not supported device
E1
E2
361412
REP not supported device
REP No-Neighbour Ports
In access ring topologies, the neighboring switch might not support REP, as shown in Figure 12-5. In
this case, you can configure the non-REP facing ports (E1 and E2) as edge no-neighbor ports. These
ports inherit all properties of edge ports, and you can configure them the same as any edge port, including
configuring them to send STP or REP topology change notices to the aggregation switch. In this case the
STP topology change notice (TCN) that is sent is a multiple spanning-tree (MST) STP message.
Complete these steps to enable and configure REP as dual edge no-neighbor port:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface interface-id
4.
rep segment segment-id edge no-neighbor [primary | preferred]
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-15
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-16
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Step 3
Command
Purpose
interface interface-id
Specifies the interface, and enters interface configuration mode.
•
Example:
Enter the physical Layer 2 interface or port channel ID. The
port-channel range is 1 to 8.
Router(config)# interface
gigabitethernet0/1
Router(config)# interface port-channel 1
Step 4
rep segment segment-id edge no-neighbor
[primary | preferred]
Enables REP on the interface, and identifies a segment number. The
segment ID range is from 1 to 1024.
Note
Example:
Router(config-if)# rep segment 1 edge
no-neighbor preferred
These are the optional keywords:
•
Enter the edge keyword to configure the port as an edge port.
Entering edge without the primary keyword configures the
port as the secondary edge port. Each segment has only two
edge ports.
•
Enter the no-neighbor keyword to configure a port with no
external REP neighbors as an edge port. The port inherits all
properties of edge ports, and you can configure them the same
as any edge port.
•
On an edge port, enter the primary keyword to configure the
port as the primary edge port, the port on which you can
configure VLAN load balancing.
Note
•
Note
Note
You must configure two edge ports, including one primary
edge port for each segment.
Although each segment can have only one primary edge
port, if you configure edge ports on two different switches
and enter the primary keyword on both switches, the
configuration is allowed. However, REP selects only one of
these ports as the segment primary edge port. You can
identify the primary edge port for a segment by entering the
show rep topology privileged EXEC command.
Enter the preferred keyword to indicate that the port is the
preferred alternate port or the preferred port for VLAN load
balancing.
Configuring a port as preferred does not guarantee that it
becomes the alternate port; it merely gives it a slight edge
among equal contenders. The alternate port is usually a
previously failed port.
For configuring REP LSL timer and VLB, see Configuring REP Interfaces, page 12-10.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-17
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Cisco ASR 901 Dual Rep Edge No-Neighbor Topology Example
The following configuration example shows a Cisco ASR 901 router running with Dual REP Edge
No-Neighbor and two Cisco 7600 series routers running as non-REP devices.
Note
This section provides partial configurations intended to demonstrate a specific feature.
ASR_1
interface GigabitEthernet0/0
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
rep segment 1 edge no-neighbor primary
!
interface GigabitEthernet0/1
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
rep segment 1 edge no-neighbor preferred
!
interface Vlan1
ip address 172.18.40.70 255.255.255.128
no ptp enable
!
interface Vlan2
ip address 1.1.1.1 255.255.255.0
no ptp enable
!
interface Vlan3
ip address 2.2.2.2 255.255.255.0
no ptp enable
!
interface Vlan3
ip address 4.4.4.2 255.255.255.0
no ptp enable
!
ip route 3.3.3.0 255.255.255.0 1.1.1.2
ip route 5.5.5.0 255.255.255.0 1.1.1.2
7600_1
interface Port-channel69
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-18
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
!
interface GigabitEthernet3/25
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface GigabitEthernet3/26
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface GigabitEthernet3/35
ip address 3.3.3.2 255.255.255.0
!
interface GigabitEthernet3/36
ip address 5.5.5.2 255.255.255.0
!
interface GigabitEthernet5/2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
!
interface Vlan1
no ip address
!
interface Vlan2
ip address 1.1.1.2 255.255.255.0
!
ip route 2.2.2.0 255.255.255.0 1.1.1.1
ip route 4.4.4.0 255.255.255.0 1.1.1.1
7600_2
interface Port-channel69
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
!
interface GigabitEthernet7/25
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface GigabitEthernet7/26
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-19
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
!
interface GigabitEthernet5/2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
!
interface Vlan1
no ip address
!
interface Vlan2
ip address 1.1.1.3 255.255.255.0
Setting up Manual Preemption for VLAN Load Balancing
If you do not enter the rep preempt delay seconds interface configuration command on the primary edge
port to configure a preemption time delay, the default is to manually trigger VLAN load balancing on
the segment. Be sure to complete all other segment configuration before manually preempting VLAN
load balancing. When you enter the rep preempt segment segment-id command, a confirmation
message appears before the command is executed because preemption can cause network disruption.
Note
Ethernet over Multiprotocol Label Switching (EoMPLS) is supported on the Cisco ASR 901 router for
Cisco IOS Release 15.2(2)SNG and later releases.
Complete these steps on the switch that has the segment primary edge port to manually trigger VLAN
load balancing on a segment:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
rep preempt segment segment-id
4.
end
5.
show rep topology
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-20
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Step 3
Command or Action
Purpose
rep preempt segment segment-id
Manually triggers VLAN load balancing on the segment.
•
Example:
Note
Router# rep preempt segment 1
Step 4
Enter the segment ID.
You will be asked to confirm the action before the
command is executed.
Returns to privileged EXEC mode.
end
Example:
Router(config)# end
Step 5
Views the REP topology information.
show rep topology
Example:
Router# show rep topology
Configuring SNMP Traps for REP
You can configure the switch to send REP-specific traps to notify the SNMP server of link operational
status changes and port role changes. Complete these steps to configure REP traps:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp mib rep trap-rate value
4.
end
5.
show running-config
6.
copy running-config startup config
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-21
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
Step 3
Command or Action
Purpose
snmp mib rep trap-rate value
Enables the router to send REP traps, and sets the number of
traps sent per second.
•
Example:
Router(config)# snmp mib rep trap-rate 500
Enter the number of traps sent per second. The range is
from 0 to 1000. The default is 0 (no limit imposed; a trap is
sent at every occurrence).
Note
Step 4
To remove the traps, enter the no snmp mib rep
trap-rate command.
Returns to privileged EXEC mode.
end
Example:
Router(config)# end
Step 5
show running-config
(Optional) Displays the running configuration, which you can
use to verify the REP trap configuration.
Example:
Router# show running-config
Step 6
copy running-config startup config
(Optional) Saves your entries in the router startup configuration
file.
Example:
Router# copy running-config startup config
Monitoring REP
Complete the following steps to monitor the REP configuration:
SUMMARY STEPS
1.
enable
2.
show interface [interface-id] rep [detail]
3.
show rep topology [segment segment-id] [archive] [detail]
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-22
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuring Resilient Ethernet Protocol (REP)
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
show interface [interface-id] rep [detail]
(Optional) Displays the REP configuration and status for
a specified interface.
•
Example:
Router# show interface gigabitethernet0/1 rep
detail
Step 3
show rep topology [segment segment-id] [archive]
[detail]
Example:
Router# show rep topology
Enter the physical Layer 2 interface or port channel
(logical interface) and the optional detail keyword,
if desired.
(Optional) Displays REP topology information for a
segment or for all segments, including the primary and
secondary edge ports in the segment.
•
Enter the optional keywords and arguments, as
desired.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-23
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
Configuration Examples for REP
This section contains the following examples:
•
Configuring the REP Administrative VLAN: Example, page 12-24
•
Configuring a REP Interface: Example, page 12-24
•
Setting up the Preemption for VLAN Load Balancing: Example, page 12-25
•
Configuring SNMP Traps for REP: Example, page 12-25
•
Monitoring the REP Configuration: Example, page 12-25
•
Cisco ASR 901 Topology Example, page 12-26
Configuring the REP Administrative VLAN: Example
This example shows how to configure the administrative VLAN as VLAN 100.
Router# configure terminal
Router(config)# rep admin vlan 100
Router(config-if)# end
Configuring a REP Interface: Example
This example shows how to configure an interface as the primary edge port for segment 1, to send
Spanning Tree Topology Changes Notification (STCNs) to segments 2 through 5, and to configure the
alternate port as the port with port ID 0009001818D68700 to block all VLANs after a preemption delay
of 60 seconds after a segment port failure and recovery.
Router# configure terminal
Router(config)# interface gigabitethernet0/1
Router(config-if)# rep segment 1 edge primary
Router(config-if)# rep stcn segment 2-5
Router(config-if)# rep block port 0009001818D68700 vlan all
Router(config-if)# rep preempt delay 60
Router (config-if)# rep lsl-age-timer 6000
Router(config-if)# end
This example shows how to configure the same configuration when the interface has no external REP
neighbor:
Router# configure terminal
Router(conf)# interface gigabitethernet0/1
Router(config-if)# rep segment 1 edge no-neighbor primary
Router(config-if)# rep stcn segment 2-5
Router(config-if)# rep block port 0009001818D68700 vlan all
Router(config-if)# rep preempt delay 60
Router(config-if)# rep lsl-age-timer 6000
Figure 6 shows how to configure the VLAN blocking configuration. The alternate port is the neighbor
with neighbor offset number 4. After manual preemption, VLANs 100 to 200 are blocked at this port and
all other VLANs are blocked at the primary edge port E1 (Gigabit Ethernet port 0/1).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-24
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
Router# configure terminal
Router(config)# interface gigabitethernet0/1
Router(config-if)# rep segment 1 edge primary
Router(config-if)# rep block port 4 vlan 100-200
Router(config-if)# end
Router(config)# rep platform vlb segment 1 vlan 100-200
Example of VLAN Blocking
Primary edge port E1
blocks all VLANs except
VLANs 100-200
E1
E2
4
Alternate port (offset 4)
blocks VLANs 100-200
201891
Figure 6
Setting up the Preemption for VLAN Load Balancing: Example
The following is an example of setting the preemption for VLAN load balancing on a REP segment.
Router>
Router#
Router#
Router#
enable
configure terminal
rep preempt segment 1
end
Configuring SNMP Traps for REP: Example
This example shows how to configure the router to send REP traps at a rate of 10 traps per second:
Router> enable
Router# configure terminal
Router(config)# snmp mib rep trap-rate 10
Router(config)# end
Monitoring the REP Configuration: Example
The following is sample output of the show interface rep detail command. Use the show interface rep
detail command on one of the REP interfaces to monitor and verify the REP configuration.
Router# show interface gigabitethernet0/1 rep detail
GigabitEthernet0/1 REP enabled
Segment-id: 2 (Edge)
PortID: 00010019E7144680
Preferred flag: No
Operational Link Status: TWO_WAY
Current Key: 0002001121A2D5800E4D
Port Role: Open
Blocked Vlan: <empty>
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-25
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
Admin-vlan: 100
Preempt Delay Timer: disabled
Load-balancing block port: none
Load-balancing block vlan: none
STCN Propagate to: none
LSL PDU rx: 3322, tx: 1722
HFL PDU rx: 32, tx: 5
BPA TLV rx: 16849, tx: 508
BPA (STCN, LSL) TLV rx: 0, tx: 0
BPA (STCN, HFL) TLV rx: 0, tx: 0
EPA-ELECTION TLV rx: 118, tx: 118
EPA-COMMAND TLV rx: 0, tx: 0
EPA-INFO TLV rx: 4214, tx: 4190
Cisco ASR 901 Topology Example
The following configuration example shows two Cisco ASR 901 routers and two Cisco 7600 series
routers using a REP ring.
Note
This section provides partial configurations intended to demonstrate a specific feature.
ASR_1
interface GigabitEthernet0/0
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
rep segment 1
!
interface GigabitEthernet0/1
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
rep segment 1
!
interface GigabitEthernet0/3
service instance 3 ethernet
encapsulation dot1q 3
rewrite ingress tag pop 1 symmetric
bridge-domain 3
!
interface GigabitEthernet0/4
service instance 4 ethernet
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-26
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
encapsulation dot1q 4
rewrite ingress tag pop 1 symmetric
bridge-domain 4
!
interface Vlan1
ip address 172.18.40.70 255.255.255.128
no ptp enable
!
interface Vlan2
ip address 1.1.1.1 255.255.255.0
no ptp enable
!
interface Vlan3
ip address 2.2.2.2 255.255.255.0
no ptp enable
!
interface Vlan3
ip address 4.4.4.2 255.255.255.0
no ptp enable
!
ip route 3.3.3.0 255.255.255.0 1.1.1.4
ip route 5.5.5.0 255.255.255.0 1.1.1.4
ASR_2
interface GigabitEthernet0/0
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
rep segment 1
interface GigabitEthernet0/1
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
rep segment 1
!
interface Vlan1
ip address 172.18.44.239 255.255.255.0
no ptp enable
!
interface Vlan2
ip address 1.1.1.2 255.255.255.0
no ptp enable
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-27
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
7600_1
interface Port-channel69
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
!
interface GigabitEthernet3/25
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface GigabitEthernet3/26
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface GigabitEthernet3/35
ip address 3.3.3.2 255.255.255.0
!
interface GigabitEthernet3/36
ip address 5.5.5.2 255.255.255.0
!
interface GigabitEthernet5/2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
rep segment 1 edge
interface Vlan1
no ip address
!
interface Vlan2
ip address 1.1.1.4 255.255.255.0
!
ip route 2.2.2.0 255.255.255.0 1.1.1.1
ip route 4.4.4.0 255.255.255.0 1.1.1.1
7600_2
interface Port-channel69
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
!
interface GigabitEthernet5/2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
rep segment 1 edge
!
interface GigabitEthernet7/25
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-28
OL-23826-09
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface GigabitEthernet7/26
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,2
switchport mode trunk
channel-group 69 mode on
!
interface Vlan1
no ip address
!
interface Vlan2
ip address 1.1.1.3 255.255.255.0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
12-29
Chapter 12
Configuring Resilient Ethernet Protocol
Configuration Examples for REP
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
12-30
OL-23826-09
CH A P T E R
13
Configuring MST on EVC Bridge Domain
This section describes how to configure MST on EVC Bridge Domain.
Contents
•
Overview of MST and STP, page 13-1
•
Overview of MST on EVC Bridge Domain, page 13-2
•
Restrictions and Guidelines, page 13-2
•
Configuring MST on EVC Bridge Domain, page 13-4
Overview of MST and STP
Spanning Tree Protocol (STP) is a Layer 2 link-management protocol that provides path redundancy
while preventing undesirable loops in the network. For a Layer 2 Ethernet network to function properly,
only one active path can exist between any two stations. STP operation is transparent to end stations,
which cannot detect whether they are connected to a single LAN segment or a switched LAN of multiple
segments.
MST maps multiple VLANs into a spanning tree instance, with each instance having a spanning tree
topology independent of other spanning tree instances. This architecture provides multiple forwarding
paths for data traffic, enables load balancing, and reduces the number of spanning tree instances required
to support a large number of VLANs. MST improves the fault tolerance of the network because a failure
in one instance (forwarding path) does not affect other instances (forwarding paths).
For routers to participate in MST instances, you must consistently configure the routers with the same
MST configuration information. A collection of interconnected routers that have the same MST
configuration comprises an MST region. For two or more routers to be in the same MST region, they
must have the same VLAN-to-instance mapping, the same configuration revision number, and the same
MST name.
The MST configuration controls the MST region to which each router belongs. The configuration
includes the name of the region, the revision number, and the MST VLAN-to-instance assignment map.
A region can have one or multiple members with the same MST configuration; each member must be
capable of processing RSTP bridge protocol data units (BPDUs). There is no limit to the number of MST
regions in a network, but each region can support up to 65 spanning tree instances. Instances can be
identified by any number in the range from 0 to 4094. You can assign a VLAN to only one spanning tree
instance at a time.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
13-1
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
Overview of MST on EVC Bridge Domain
The MST on EVC Bridge-Domain feature uses VLAN IDs for service-instance-to-MST-instance
mapping. EVC service instances with the same VLAN ID (the outer VLAN IDs in the QinQ case) as the
one in another MST instance will be mapped to that MST instance.
EVC service instances can have encapsulations with a single tag as well as double tags. In case of double
tag encapsulations, the outer VLAN ID shall be used for the MST instance mapping, and the inner VLAN
ID is ignored.
A single VLAN per EVC is needed for the mapping with the MST instance. The following service
instances without any VLAN ID or with multiple outer VLAN IDs are not supported:
•
Untagged (encapsulation untagged) is supported but there is no loop detection on the EVC
•
Priority-tagged (encapsulation priority-tagged)
•
Multiple outer tags (encapsulation dot1q 200 to 400 second-dot1q 300)
Restrictions and Guidelines
The following restrictions and guidelines apply to MST on EVC bridge domain:
•
Cisco IOS Release 15.1(2)SNG supports EVC port-channels.
•
With default configuration, Cisco ASR 901 does not run any spanning-tree protocol. Hence all the
ports participating in bridge domains are moved to forward state. To enable MSTP, issue
spanning-tree mode mstp command in the global configuration mode.
•
Main interface where the EFP is configured must be up and running with MSTP as the selected
Spanning Tree Mode (PVST and Rapid-PVST are not supported).
•
The SPT PortFast feature is not supported with EFPs.
•
The co-existence of REP and mLACP with MST on the same port is not supported.
•
Any action performed on VPORT (which represents a particular VLAN in a physical port) affects
the bridge domain and other services.
•
Supports 32 MSTs and one CIST (common and internal spanning tree).
•
Supports one MST region.
•
Scales to 4000 EFPs.
•
Untagged EVCs do not participate in MST loop detection.
•
Service instances without any VLAN ID in the encapsulation are not supported, because a unique
VLAN ID is required to map an EVC to an MST instance.
•
Supports EFPs with unambiguous outer VLAN tag (that is, no range, list on outer VLAN, neither
default nor untagged).
•
Removing dot1q encapsulation removes the EVC from MST.
•
Changing the VLAN (outer encapsulation VLAN of EVC) mapping to a different MST instance will
move the EVC port to the new MST instance.
•
Changing an EVC service instance to a VLAN that has not been defined in MST 1 will result in
mapping of EVC port to MST 0.
•
The peer router of the EVC port must also be running MST.
•
MST is supported only on EVC BD. EVCs without BD configuration will not participate in MST.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
13-2
OL-23826-09
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
•
When an MST is configured on the outer VLAN, you can configure any number of service instances
with the same outer VLAN as shown in the following configuration example.
nPE1#sh run int gi0/5
Building configuration...
Current configuration : 373 bytes
!
interface GigabitEthernet0/5
description connected to CE1
no ip address
service instance 100 ethernet
encapsulation dot1q 100 second-dot1q 1
bridge-domain 100
!
service instance 101 ethernet
encapsulation dot1q 100 second-dot1q 2
bridge-domain 101
!
service instance 102 ethernet
encapsulation dot1q 100 second-dot1q 120-140
bridge-domain 102
!
end
nPE1#sh run int gi0/6
Building configuration...
Current configuration : 373 bytes
!
interface GigabitEthernet0/6
description connected to CE1
no ip address
service instance 100 ethernet
encapsulation dot1q 100 second-dot1q 1
bridge-domain 100
!
service instance 101 ethernet
encapsulation dot1q 100 second-dot1q 2
bridge-domain 101
!
service instance 102 ethernet
encapsulation dot1q 100 second-dot1q 120-140
bridge-domain 102
!
end
nPE1#sh span vlan 100
MST0
Spanning tree enabled protocol mstp
Root ID
Priority
32768
Address
0018.742f.3b80
Cost
0
Port
2821 (GigabitEthernet12/5)
Hello Time
2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID
Priority
Address
Hello Time
32768 (priority 32768 sys-id-ext 0)
001a.303c.3400
2 sec Max Age 20 sec Forward Delay 15 sec
Interface
Role Sts Cost
Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
13-3
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
Gi12/5
Gi12/6
Root FWD 20000
Altn BLK 20000
128.2821 P2p
128.2822 P2p
nPE1#
Configuring MST on EVC Bridge Domain
Figure 13-1 shows an example of the untagged EVCs that do not participate in MST loop detection.
When you link your networks together as shown below, a loop is caused since MST is not running on
the untagged EVCs.
Figure 13-1
Untagged EVCs not participating in MST loop detection
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
13-4
OL-23826-09
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
Figure 13-2
MST with untagged EVCs without loop
Complete the following steps to configure MST on EVC bridge domain.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router# enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
interface gigabitethernet slot/port
Specifies the gigabit ethernet interface to configure.
•
slot/port—Specifies the location of the interface.
Example:
Router(config)# interface
gigabitethernet 0/1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
13-5
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
Step 4
Command
Purpose
[no] service instance id Ethernet
[service-name]
Creates a service instance (EVC instance) on an
interface and sets the device into the config-if-srv
submode.
Example:
Router(config-if)# service instance 101
ethernet
Step 5
encapsulation dot1q vlan-id
Example:
Defines the matching criteria to be used in order to map
ingress dot1q frames on an interface to the appropriate
service instance.
Router(config-if-srv)# encapsulation
dot1q 13
Step 6
[no] bridge-domain bridge-id
Example:
Binds the service instance to a bridge domain instance
where bridge-id is the identifier for the bridge domain
instance.
Router(config-if-srv)# bridge-domain 12
Configuration Example for MST on EVC Bridge Domain
In the following example, two interfaces participate in MST instance 0, the default instance to which all
VLANs are mapped:
Router# enable
Router# configure terminal
Router(config)# interface g0/1
Router(config-if)# service instance 1 ethernet
Router(config-if-srv)# encapsulation dot1q 2
Router(config-if-srv)# bridge-domain 100
Router(config-if-srv)# interface g0/3
Router(config-if)# service instance 1 ethernet
Router(config-if-srv)# encapsulation dot1q 2
Router(config-if-srv)# bridge-domain 100
Router(config-if-srv)# end
Verification
Use this command to verify the configuration:
Router# show spanning-tree vlan 2
MST0
Spanning tree enabled protocol mstp
Root ID
Priority
32768
Address
0009.e91a.bc40
This bridge is the root
Hello Time
2 sec Max Age 20 sec
Bridge ID
Priority
Address
Hello Time
Forward Delay 15 sec
32768 (priority 32768 sys-id-ext 0)
0009.e91a.bc40
2 sec Max Age 20 sec Forward Delay 15 sec
Interface
Role Sts Cost
Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------------Gi4/1
Desg FWD 20000
128.1537 P2p
Gi4/3
Back BLK 20000
128.1540 P2p
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
13-6
OL-23826-09
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
In this example, interface gi4/1 and interface gi4/3 are connected back-to-back. Each has a service
instance (EFP) attached to it. The EFP on both interfaces has an encapsulation VLAN ID of 2. Changing
the VLAN ID from 2 to 8 in the encapsulation directive for the EFP on interface gi4/1 stops the MSTP
from running in the MST instance to which the old VLAN is mapped and starts the MSTP in the MST
instance to which the new VLAN is mapped:
Router(config-if)# interface g4/1
Router(config-if)# service instance 1 ethernet
Router(config-if-srv)# encap dot1q 8
Router(config-if-srv)# end
Use this command to verify the configuration:
Router# show spanning-tree vlan 2
MST1
Spanning tree enabled protocol mstp
Root ID
Priority
32769
Address
0009.e91a.bc40
This bridge is the root
Hello Time
2 sec Max Age 20 sec
Bridge ID
Priority
Address
Hello Time
Forward Delay 15 sec
32769 (priority 32768 sys-id-ext 1)
0009.e91a.bc40
2 sec Max Age 20 sec Forward Delay 15 sec
Interface
Role Sts Cost
Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------------Gi4/3
Desg FWD 20000
128.1540 P2p
Router# show spanning-tree vlan 8
MST2
Spanning tree enabled protocol mstp
Root ID
Priority
32770
Address
0009.e91a.bc40
This bridge is the root
Hello Time
2 sec Max Age 20 sec
Bridge ID
Priority
Address
Hello Time
Forward Delay 15 sec
32770 (priority 32768 sys-id-ext 2)
0009.e91a.bc40
2 sec Max Age 20 sec Forward Delay 15 sec
Interface
Role Sts Cost
Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------------Gi4/1
Desg FWD 20000
128.1537 P2p
In this example, interface gi4/3 (with an EFP that has an outer encapsulation VLAN ID of 2 and a bridge
domain of 100) receives a new service:
Router# enable
Router# configure terminal
Router(config)# interface g4/3
Router((config-if)# service instance 2 ethernet
Router((config-if-srv)# encap dot1q 2 second-dot1q 100
Router((config-if-srv)# bridge-domain 200
Now there are two EFPs configured on interface gi4/3 and both of them have the same outer VLAN 2.
interface GigabitEthernet4/3
no ip address
service instance 1 ethernet
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
13-7
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
encapsulation dot1q 2
bridge-domain 100
!
service instance 2 ethernet
encapsulation dot1q 2 second-dot1q 100
bridge-domain 200
The preceding configuration does not affect the MSTP operation on the interface; there is no state change
for interface gi4/3 in the MST instance it belongs to.
Router# show spanning-tree mst 1
##### MST1
Bridge
Root
vlans mapped:
2
address 0009.e91a.bc40
this switch for MST1
priority
32769 (32768 sysid 1)
Interface
Role Sts Cost
Prio.Nbr Type
---------------- ---- --- --------- -------- -------------------------------Gi4/3
Desg FWD 20000
128.1540 P2p
This example shows MST on port channels:
Router# show spanning-tree mst 1
##### MST1 vlans mapped: 3
Bridge address 000a.f331.8e80 priority 32769 (32768 sysid 1)
Root address 0001.6441.68c0 priority 32769 (32768 sysid 1)
port Po5 cost 20000 rem hops 18
Interface Role Sts Cost Prio.Nbr Type
---------------- ---- --- --------- -------- -------------------------------Gi2/0/0 Desg FWD 20000 128.257 P2p
Po5 Root FWD 10000 128.3329 P2p
Po6 Altn BLK 10000 128.3330 P2p
Router# show spanning-tree vlan 3
MST1
Spanning tree enabled protocol mstp
Root ID Priority 32769
Address 0001.6441.68c0
Cost 20000
Port 3329 (Port-channel5)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 000a.f331.8e80
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------------Gi2/0/0 Desg FWD 20000 128.257 P2p
Po5 Root FWD 10000 128.3329 P2p
Po6 Altn BLK 10000 128.3330 P2p
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
13-8
OL-23826-09
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
Troubleshooting Tips
Table 13-1
Troubleshooting Scenarios
Problem
Solution
Multiple Spanning Tree Protocol (MSTP) incorrectly or
inconsistently formed due to misconfiguration and BPDU
loss
To avoid BPDU loss, re-configure these on the following
nodes:
•
Configuration name
•
Bridge revision
•
Provider-bridge mode
•
Instance to VLAN mapping
Determine if node A is sending BPDUs to node B. Use the
show spanning-tree mst interface gi1/1 service instance
command for each interface connecting the nodes. Only
designated ports relay periodic BPDUs.
MSTP correctly formed, but traffic flooding occurs
Intermittent BPDU loss occurs when the spanning tree appears
incorrectly in the show commands, but relays topology change
notifications. These notifications cause a MAC flush, forcing
traffic to flood until the MAC addresses are re-learned. Use the
debug spanning-tree mst packet full {received | sent}
command to debug topology change notifications.
Use the debug spanning-tree mst packet brief {received |
sent} command on both nodes to check for missing BPDUs.
Monitor the timestamps. A time gap greater than or equal to
six seconds causes topology change.
MSTP shows incorrect port state
When the spanning tree protocol (STP) attempts to change the
port state, it uses L2VPN. Check the value of the sent update.
If the value is Yes, then STP is awaiting an update from
L2VPN.
Packet forwarding does not match the MSTP state
Complete the following steps to verify and troubleshoot:
1.
Shut down redundant links, remove MSTP configuration,
and ensure that basic bridging works.
2.
Check the state of each port as calculated by MSTP, and
compare it with the packet counts transmitted and
received on ports and EFPs controlled by MSTP. Normal
data packets should be sent/received only on ports in the
forwarding (FWD) state. BPDUs should be sent/received
on all ports controlled by MSTP.
3.
Ensure that BPDUs are flowing and that root bridge
selection is correct and check the related scenarios.
4.
Use the show l2vpn bridge-domain detail command to
confirm the status of the members of the bridge domain.
Ensure that the relevant bridge domain members are
active.
5.
Check the forwarding state as programmed in hardware.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
13-9
Chapter 13
Configuring MST on EVC Bridge Domain
Contents
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
13-10
OL-23826-09
CH A P T E R
14
Configuring Multiprotocol Label Switching
Several technologies such as pseudowires utilize MPLS for packet transport. For more information about
how to configure MPLS, see the MPLS Configuration Guide, Cisco IOS Release 15.1S.
Note
The Cisco ASR 901 router does not necessarily support all of the commands listed in the
Release 15.1(2)S documentation.
Note
In Cisco ASR 901, mpls ip is configured on SVI only. The Cisco ASR 901 router supports only a
maximum of 60 MPLS enabled SVI interfaces.
Note
If port channel is configured on an MPLS core, the encapsulation ID should be the same as the bridge
domain.
Note
The maximum number of LDP labels supported in Cisco ASR 901 router is 4000.
Note
MPLS byte switched counters are not supported on Cisco ASR 901 router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
14-1
Chapter 14
Configuring Multiprotocol Label Switching
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
14-2
OL-23826-09
CH A P T E R
15
Configuring EoMPLS
The Cisco ASR 901 router supports EoMPLS, a subset of AToM that uses a tunneling mechanism to
carry Layer 2 Ethernet traffic. Ethernet Over MPLS (EoMPLS) encapsulates Ethernet frames in MPLS
packets and forwards them across the MPLS network.
Contents
•
Understanding EoMPLS, page 15-1
•
Configuring EoMPLS, page 15-2
•
EoMPLS Configuration Example, page 15-3
•
Configuring Pseudowire Redundancy, page 15-4
•
Port Based EoMPLS, page 15-5
Understanding EoMPLS
EoMPLS encapsulates ethernet frames in MPLS packets and forwards them across the MPLS network.
Each frame is transported as a single packet, and the PE routers connected to the backbone add and
remove labels as appropriate for packet encapsulation:
•
The ingress PE router receives an Ethernet frame and encapsulates the packet by removing the
preamble, the start of frame delimiter (SFD), and the frame check sequence (FCS). The rest of the
packet header is not changed.
•
The ingress PE router adds a point-to-point virtual connection (VC) label and a label switched path
(LSP) tunnel label for normal MPLS routing through the MPLS backbone.
•
The network core routers use the LSP tunnel label to move the packet through the MPLS backbone
and do not distinguish Ethernet traffic from any other types of packets in the MPLS backbone.
•
At the other end of the MPLS backbone, the egress PE router receives the packet and
de-encapsulates the packet by removing the LSP tunnel label if one is present. The PE router also
removes the VC label from the packet.
•
The PE router updates the header, if necessary, and sends the packet out the appropriate interface to
the destination switch.
The MPLS backbone uses the tunnel labels to transport the packet between the PE routers. The egress
PE router uses the VC label to select the outgoing interface for the Ethernet packet. EoMPLS tunnels are
unidirectional; for bidirectional EoMPLS, you need to configure one tunnel in each direction.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
15-1
Chapter 15
Configuring EoMPLS
Configuring EoMPLS
The point-to-point VC requires you to configure VC endpoints at the two PE routers. Only the PE routers
at the ingress and egress points of the MPLS backbone know about the VCs dedicated to transporting
Layer 2 traffic. Other routers do not have table entries for these VCs.
Restrictions
•
When configuring an EoMPLS pseudowire on Cisco ASR 901, you cannot configure an IP address
on the same interface as the pseudowire.
•
EoMPLS xconnect with VLAN range is not supported.
•
EoMPLS xconnect port with double tagged encapsulation is not supported.
•
When port channel is configured on MPLS core, the encapsulation ID should be equal to the bridge
domain.
•
The encapsulation dot1ad command is not supported.
Configuring EoMPLS
Complete the following steps to configure EoMPLS:
Step 1
Command
Purpose
interface interface-id
Specify the interface, and enter interface configuration mode.
Valid interfaces are physical ports.
Example:
Router(config)# int gig 0/1
Step 2
service instance number ethernet [name]
Configure a service instance and enter service instance
configuration) mode.
•
The number is the service instance identifier, an integer from
1 to 4000.
•
(Optional) ethernet name is the name of a previously
configured EVC. You do not need to use an EVC name in a
service instance.
Example:
Router(config-if)#service instance 101
ethernet
Step 3
encapsulation {dot1q | untagged}
Example:
Configure encapsulation type for the service instance.
•
dot1q—Configure 802.1Q encapsulation.
•
untagged—Map to untagged VLANs. Only one EFP per port
can have untagged encapsulation.
Router(config-if-srv)#encapsulation dot1q 51
Note
The dot1ad keyword is not supported for the
encapsulation command in EoMPLS.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
15-2
OL-23826-09
Chapter 15
Configuring EoMPLS
EoMPLS Configuration Example
Step 4
Command
Purpose
rewrite ingress tag pop 1 symmetric
Specify that encapsulation modification to occur on packets at
ingress.
Example:
•
pop 1—Pop (remove) the outermost tag.
Router(config-if-srv)#rewrite ingress tag pop
1 symmetric
•
symmetric—Configure the packet to undergo the reverse of
the ingress action at egress. If a tag is popped at ingress, it is
pushed (added) at egress.
Note
Step 5
xconnect ip address service-instance-number
encapsulation mpls
Although the symmetric keyword appears to be optional,
you must enter it for rewrite to function correctly.
Configure cross-connect pseudowire by specifying the IP address
of remote peer and the virtual circuit ID.
Example:
Router(config-if-srv)#xconnect 192.168.1.8
101 encapsulation mpls
EoMPLS Configuration Example
interface Loopback0
description for_mpls_ldp
ip address 99.99.99.99 255.255.255.255
!
interface GigabitEthernet0/10
description Core_facing
no negotiation auto
service instance 150 ethernet
encapsulation dot1q 150
rewrite ingress tag pop 1 symmetric
bridge-domain 150
!
interface GigabitEthernet0/11
description Core_facing
service instance 501 ethernet
encapsulation dot1q 501
rewrite ingress tag pop 1 symmetric
xconnect 111.0.1.1 501 encapsulation mpls
!
interface FastEthernet0/0
ip address 10.104.99.74 255.255.255.0
full-duplex
!
interface Vlan1
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
mpls ip
!
router ospf 7
network 99.99.99.99 0.0.0.0 area 0
network 150.0.0.0 0.0.0.255 area 0
!
no ip http server
ip route 10.0.0.0 255.0.0.0 10.104.99.1
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
15-3
Chapter 15
Configuring EoMPLS
Configuring Pseudowire Redundancy
logging esm config
!
mpls ldp router-id Loopback0 force
!
!
end
Configuring Pseudowire Redundancy
Pseudowire (PW) Redundancy enables you to configure a backup pseudowire in case the primary
pseudowire fails. When the primary pseudowire fails, the PE router can switch to the backup pseudowire.
Traffic can be switched back to the primary pseudowire after the path is operational again.
You can configure the network with redundant pseudowires and redundant network elements, as shown
in Figure 15-1.
Figure 15-1
Configuring Redundant Pseudowires
Configuration Commands
Complete the following steps to configure pseudowire redundancy:
Command
Purpose
Step 6
configure terminal
Enters global configuration mode.
Step 7
Router(config)# interface
GigabitEthernet0/2
Router(config-if)#
Specifies an interface to configure.
Step 8
Router(config-if)# service instance
101 ethernet
Configures a service instance and enters the service instance
configuration mode.
Step 9
Router(config-if-srv)#
encapsulation dot1q 101
Configures encapsulation type for the service instance.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
15-4
OL-23826-09
Chapter 15
Configuring EoMPLS
Port Based EoMPLS
Step 10
Command
Purpose
Router(config-if-srv)# rewrite
ingress tag pop 1 symmetric
Specifies the encapsulation modification to occur on packets at ingress as
follows:
•
pop 1—Pop (remove) the outermost tag.
•
symmetric—Configure the packet to undergo the reverse of the
ingress action at egress. If a tag is popped at ingress, it is pushed
(added) at egress.
Note
Although the symmetric keyword appears to be optional, you
must enter it for rewrite to function correctly.
Step 11
Router(config-if-srv)# xconnect
11.205.1.1 141 encapsulation mpls
Binds the VLAN attachment circuit to an Any Transport over MPLS
(AToM) pseudowire for EoMPLS.
Step 12
Router(cfg-if-ether-vc-xconn)#
backup peer 13.205.3.3 1141
Specifies a backup peer for redundancy.
Step 13
end
Returns to privileged EXEC mode.
Step 14
•
show mpls l2t vc id
•
show mpls l2t vc detail
•
show mpls infrastructure lfd
pseudowire internal
Use these commands to display pseudowire information.
Port Based EoMPLS
Port mode allows a frame coming into an interface to be packed into an MPLS packet and transported
over the MPLS backbone to an egress interface. The entire ethernet frame without the preamble or frame
check sequence (FCS) is transported as a single packet. To configure port mode, use the xconnect
command in the main interface mode and specify the destination address and the VC ID. The syntax and
semantics of the xconnect command are the same as for all other transport types. Each interface is
associated with one unique pseudowire VC label.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router> configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
15-5
Chapter 15
Configuring EoMPLS
Port Based EoMPLS
Step 3
Command
Purpose
interface GigabitEthernet slot/port
Specifies an interface to configure.
Example:
Router(config)# interface
GigabitEthernet 0/2
Router(config-if)#
Step 4
xconnect peer-router-id vcid
encapsulation mpls
Binds the attachment circuit to a pseudowire VC. The syntax for this
command is the same as for all other Layer 2 transports.
Example:
Router(config)# xconnect 10.0.0.1
123 encapsulation mpls
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
15-6
OL-23826-09
CH A P T E R
16
Configuring MPLS VPNs
A Virtual Private Network (VPN) is an IP-based network that delivers private network services over a
public infrastructure. VPNs allow you to create a set of sites that can communicate privately over the
Internet or other public or private networks.
Contents
•
Understanding MPLS VPNs
•
Configuring MPLS VPNs
•
Configuration Examples for MPLS VPN
Understanding MPLS VPNs
A conventional VPN consists of a full mesh of tunnels or permanent virtual circuits (PVCs) connecting
all of the sites within the VPN. This type of VPN requires changes to each edge device in the VPN in
order to add a new site. MPLS VPNs, also known as Layer 3 VPNs, are easier to manage and expand
than conventional VPNs because they use layer 3 communication protocols and are based on a peer
model. The peer model enables the service provider and customer to exchange Layer 3 routing
information, enabling service providers to relay data between customer sites without customer
involvement. The peer model also provides improved security of data transmission between VPN sites
because data is isolated between improves security between VPN sites.
The Cisco ASR 901 supports the following MPLS VPN types:
Note
•
Basic Layer 3 VPN—Provides a VPN private tunnel connection between customer edge (CE)
devices in the service provider network. The provider edge (PE) router uses Multiprotocol Border
Gateway Protocol (MP-BGP) to distribute VPN routes and MPLS Label Distribution Protocol (LDP)
to distribute Interior Gateway Protocol (IGP) labels to the next-hop PE router.
•
Multi-VRF CE—Multi-VRF CE extends limited PE functionality to a CE router in an MPLS-VPN
model. A CE router now has the ability to maintain separate VRF tables in order to extend the
privacy and security of an MPLS-VPN down to a branch office rather than just at the PE router node.
Cisco ASR 901 does not support VRF on TDM interfaces.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
16-1
Chapter 16
Configuring MPLS VPNs
Configuring MPLS VPNs
Configuring MPLS VPNs
Layer 3 VPNs allow you to establish VPNs in a routed environment, improving the flexibility and ease
of maintenance of VPNs. For instructions on how to configure layer 3 VPNs, see the
MPLS Configuration Guide, Cisco IOS Release 15.1S.
The following restrictions apply to MPLS VPNs:
•
When the port channel is on core, bridge ID must be equal to the encapsulation ID.
•
Equal Cost Multipath (ECMP) is not supported for swap cases.
Configuration Examples for MPLS VPN
This section contains the following sample configurations involving three routers:
•
PE1 Configuration, page 16-2
•
Provider Configuration, page 16-5
•
PE2 Configuration, page 16-6
PE1 Configuration
Current configuration : 3326 bytes
!
! Last configuration change at 20:37:37 UTC Thu Sep 29 2011
!
version 15.1
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
!card type command needed for slot/vwic-slot 0/0
no logging console
!
no aaa new-model
ip source-route
ip cef
!
ip vrf customer_2
rd 1:2
route-target export 1:2
route-target import 1:2
!
!
!
no ip domain lookup
no ipv6 cef
!
!
multilink bundle-name authenticated
!
!
!
spanning-tree mode pvst
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
16-2
OL-23826-09
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback2
no ip address
!
interface Loopback100
ip address 111.0.0.1 255.255.255.255
!
interface GigabitEthernet0/0
no negotiation auto
!
interface GigabitEthernet0/1
no negotiation auto
!
interface GigabitEthernet0/2
no negotiation auto
!
interface GigabitEthernet0/3
no negotiation auto
!
interface GigabitEthernet0/4
no negotiation auto
!
interface GigabitEthernet0/5
media-type sfp
no negotiation auto
cdp enable
service instance 2 ethernet
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
bridge-domain 2
!
!
interface GigabitEthernet0/6
no negotiation auto
service instance 10 ethernet
encapsulation dot1q 20
bridge-domain 120
!
!
interface GigabitEthernet0/7
load-interval 30
media-type sfp
no negotiation auto
cdp enable
service instance 300 ethernet
encapsulation dot1q 300
rewrite ingress tag pop 1 symmetric
bridge-domain 300
!
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
16-3
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
interface GigabitEthernet0/8
no negotiation auto
!
interface GigabitEthernet0/9
load-interval 30
no negotiation auto
service instance 10 ethernet
encapsulation dot1q 301
rewrite ingress tag pop 1 symmetric
bridge-domain 301
!
!
interface GigabitEthernet0/10
no negotiation auto
ethernet dot1ad nni
service instance 1 ethernet
encapsulation dot1ad 30
rewrite ingress tag pop 1 symmetric
!
!
interface GigabitEthernet0/11
no negotiation auto
!
interface ToP0/12
no negotiation auto
!
interface FastEthernet0/0
no ip address
full-duplex
!
interface Vlan1
!
interface Vlan2
ip vrf forwarding customer_2
ip address 2.2.1.1 255.255.255.0
!
interface Vlan300
ip address 1.0.0.1 255.255.255.0
mpls ip
!
interface Vlan301
ip address 11.0.0.1 255.255.255.0
mpls ip
!
router ospf 22
router-id 1.0.0.1
redistribute connected subnets
network 1.0.0.0 0.0.0.255 area 23
network 11.0.0.0 0.0.0.255 area 23
!
router bgp 1
bgp log-neighbor-changes
neighbor 111.0.1.1 remote-as 1
neighbor 111.0.1.1 update-source Loopback100
!
address-family ipv4
redistribute connected
neighbor 111.0.1.1 activate
neighbor 111.0.1.1 send-community both
exit-address-family
!
address-family vpnv4
neighbor 111.0.1.1 activate
neighbor 111.0.1.1 send-community both
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
16-4
OL-23826-09
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
exit-address-family
!
address-family ipv4 vrf cust
redistribute static
aggregate-address 190.0.0.0 255.0.0.0 summary-only
redistribute connected
neighbor 2.2.1.2 remote-as 100
neighbor 2.2.1.2 activate
exit-address-family
!
ip forward-protocol nd
!
!
no ip http server
!
logging esm config
cdp run
!
mpls ldp router-id Loopback100 force
!
!
control-plane
!
!
line con 0
line con 1
transport preferred lat pad telnet rlogin udptn mop ssh
transport output lat pad telnet rlogin udptn mop ssh
line vty 0 4
login
!
exception data-corruption buffer truncate
exception crashinfo buffersize 128
!
end
Provider Configuration
Router_1#show running-config interface gigabitEthernet 4/15
Building configuration...
Current configuration : 80 bytes
!
interface GigabitEthernet4/15
ip address 9.0.0.1 255.255.255.0
mpls ip
end
Router_1#show running-config interface gigabitEthernet 4/16
Building configuration...
Current configuration : 91 bytes
!
interface GigabitEthernet4/16
ip address 1.0.0.2 255.255.255.0
mpls ip
end
Router_1#
mpls ldp router-id Loopback2 force
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
16-5
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
Router_1#show running-config partition router bgp 1
Building configuration...
Current configuration : 664 bytes
!
Configuration of Partition - router bgp 1
!
!
!
router bgp 1
bgp log-neighbor-changes
neighbor 100.0.0.1 remote-as 1
neighbor 100.0.0.1 update-source Loopback2
neighbor 100.0.1.1 remote-as 1
neighbor 100.0.1.1 update-source Loopback2
!
address-family ipv4
no synchronization
neighbor 100.0.0.1 activate
neighbor 100.0.0.1 send-community both
neighbor 100.0.1.1 activate
neighbor 100.0.1.1 send-community both
no auto-summary
exit-address-family
!
address-family vpnv4
neighbor 100.0.0.1 activate
neighbor 100.0.0.1 send-community both
neighbor 100.0.1.1 activate
neighbor 100.0.1.1 send-community both
exit-address-family
!
!
end
Router_1#
Router_1#show running-config partition router ospf 1
Building configuration...
Current configuration : 197 bytes
!
Configuration of Partition - router ospf 1
!
!
!
router ospf 1
log-adjacency-changes
redistribute connected subnets
network 1.0.0.0 0.0.0.255 area 0
network 9.0.0.0 0.0.0.255 area 0
!
!
end
PE2 Configuration
Interface details
Router_3#show running-config interface gigabitEthernet 6/3
Building configuration...
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
16-6
OL-23826-09
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
Current configuration : 79 bytes
!
interface GigabitEthernet6/3
ip address 9.0.0.2 255.255.255.0
mpls ip
end
Router_3#show running-config interface gigabitEthernet 6/6
Building configuration...
Current configuration : 107 bytes
!
interface GigabitEthernet6/6
ip vrf forwarding customer_red
ip address 20.20.30.100 255.255.255.0
end
Router_3#show running-config interface gigabitEthernet 6/2
Building configuration...
Current configuration : 136 bytes
!
interface GigabitEthernet6/2
ip vrf forwarding customer_green
ip address 20.20.30.99 255.255.255.0
speed nonegotiate
mpls ip
end
Router_3#
OSPF and BGP details
Router_3#show running-config partition router bgp 1
Building configuration...
Current configuration : 1061 bytes
!
Configuration of Partition - router bgp 1
!
!
!
router bgp 1
bgp log-neighbor-changes
neighbor 35.35.35.35 remote-as 1
neighbor 35.35.35.35 update-source Loopback1
neighbor 100.0.0.1 remote-as 1
neighbor 100.0.0.1 update-source Loopback1
!
address-family ipv4
no synchronization
redistribute connected
neighbor 35.35.35.35 activate
neighbor 35.35.35.35 send-community both
neighbor 100.0.0.1 activate
neighbor 100.0.0.1 send-community both
no auto-summary
exit-address-family
!
address-family vpnv4
neighbor 35.35.35.35 activate
neighbor 35.35.35.35 send-community both
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
16-7
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
neighbor 100.0.0.1 activate
neighbor 100.0.0.1 send-community both
exit-address-family
!
address-family ipv4 vrf customer_green
redistribute static
aggregate-address 191.0.0.0 255.0.0.0 summary-only
no synchronization
redistribute connected
neighbor 20.20.30.199 remote-as 200
neighbor 20.20.30.199 activate
exit-address-family
!
address-family ipv4 vrf customer_red
redistribute static
aggregate-address 191.0.0.0 255.0.0.0 summary-only
no synchronization
redistribute connected
neighbor 20.20.30.200 remote-as 100
neighbor 20.20.30.200 activate
exit-address-family
!
!
end
Router_3#show running-config partition router ospf 1
Building configuration...
Current configuration : 220 bytes
!
Configuration of Partition - router ospf 1
!
!
!
router ospf 1
log-adjacency-changes
redistribute connected subnets
network 9.0.0.0 0.0.0.255 area 0
network 20.20.30.0 0.0.0.255 area 0
bfd all-interfaces
!
!
end
Router_3#
Loop Back details
Router_3#show interfaces Loopback 1
Loopback1 is up, line protocol is up
Hardware is Loopback
Internet address is 100.0.1.1/24
MTU 1514 bytes, BW 8000000 Kbit/sec, DLY 5000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation LOOPBACK, loopback not set
Keepalive set (10 sec)
Last input 20:14:17, output never, output hang never
Last clearing of "show interface" counters 22:18:00
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
16-8
OL-23826-09
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
21 packets output, 1464 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
Router_3#show run | i Loopback
interface Loopback1
interface Loopback60
neighbor 35.35.35.35 update-source Loopback1
neighbor 100.0.0.1 update-source Loopback1
mpls ldp router-id Loopback1 force
Router_3#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
16-9
Chapter 16
Configuring MPLS VPNs
Configuration Examples for MPLS VPN
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
16-10
OL-23826-09
CH A P T E R
17
Configuring MPLS OAM
This chapter describes how to configure multiprotocol label switching (MPLS) operations,
administration and maintenance (OAM) in the Cisco ASR 901 router.
Contents
•
Understanding MPLS OAM, page 17-1
•
Configuring MPLS OAM, page 17-2
Understanding MPLS OAM
MPLS OAM helps service providers monitor label-switched paths (LSPs) and quickly isolate MPLS
forwarding problems to assist with fault detection and troubleshooting in an MPLS network. The
Cisco ASR 901 router supports the following MPLS OAM features:
•
LSP Ping
•
LSP Traceroute
•
LSP Ping over Pseudowire
LSP Ping
MPLS LSP ping uses MPLS echo request and reply packets, similar to Internet Control Message
Protocol (ICMP) echo request and reply messages, to validate an LSP. ICMP echo request and reply
messages validate IP networks; MPLS OAM echo and reply messages validate MPLS LDP networks.
The LSP ping and trace functions use IPv4 UDP packets with UDP port number 3503. You can use
MPLS LSP ping to validate IPv4 LDP or Forwarding Equivalence Classes (FECs) by using the ping
mpls privileged EXEC command. The MPLS echo request packet is sent to a target router by using the
label stack associated with the FEC to be validated.
The source address of the LSP echo request is the IP address of the LDP router generating the LSP
request. The destination IP address is a 127.x.y.z/8 address, which prevents the IP packet from being
switched to its destination if the LSP is broken. The 127.0.0.x destination address range prevents the
OAM packets from exiting the egress provider-edge router, which keeps them from leaking from the
service-provider network to the customer network.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
17-1
Chapter 17
Configuring MPLS OAM
Configuring MPLS OAM
In response to an MPLS echo request, an MPLS echo reply is forwarded as an IP packet by using IP,
MPLS, or a combination of both. The source address of the MPLS echo-reply packet is an address
obtained from the router generating the echo reply. The destination address is the source address of the
router that originated the MPLS echo-request packet. The MPLS echo-reply destination port is the
echo-request source port.
LSP Traceroute
MPLS LSP traceroute also uses MPLS echo request and reply packets to validate an LSP. You can use
MPLS LSP traceroute to validate LDP IPv4 by using the trace mpls privileged EXEC command. The
traceroute time-to-live (TTL) settings force expiration of the TTL along an LSP. MPLS LSP traceroute
incrementally increases the TTL value in its MPLS echo requests (TTL = 1, 2, 3, 4) to discover the
downstream mapping of each successive hop. The transit router processing the MPLS echo request
returns an MPLS echo reply containing information about the transit hop in response to the TTL-expired
MPLS packet. The MPLS echo reply destination port is sent to the echo request source port.
LSP Ping over Pseudowire
The LSP Ping over Pseudowire is used for detecting faults in the data plane or forwarding path for
pseudowire services. The connectivity verification model for pseudowires consists of:
•
Advertising the VCCV capability
•
Verifying the data plane connectivity
Advertising the VCCV capability is done as part of MPLS Label Mapping message. This consists of
Control Channel (CC) type which is a bitmask that indicates the type of control channel that can be used
to verify connectivity. The Cisco ASR 901 router supports the following CC type:
•
Note
MPLS Router Alert Label (Type 2) : The control channel is created out of band and uses the router
alert label (RA).
The Cisco ASR 901 router does not support Control Channel Type 1 and 3.
Connectivity verification type defines a bitmask that indicates the types of CV packets and protocols that
can be sent on the specified control channel.
The LSP ping over pseudowire uses the same label stack as used by the pseudowire data path. Basically
it contains the virtual circuit (VC) label and tunnel labels.
Configuring MPLS OAM
This section contains the following topics:
•
Using LSP Ping for LDP IPv4 FEC, page 17-3
•
Using LSP Traceroute for LDP IPv4 FEC, page 17-3
•
Using LSP Ping for Pseudowire, page 17-3
•
Using LSP Traceroute over Pseudowire, page 17-4
•
Displaying AToM VCCV capabilities, page 17-4
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
17-2
OL-23826-09
Chapter 17
Configuring MPLS OAM
Configuring MPLS OAM
Note
On Cisco ASR 901, for a default MTU of 1500 bytes, IOS supports MPLS ping up to 1486 bytes. For
MPLS ping with size more than 1486 bytes to work in Cisco ASR 901, the MTU setting on the SVI has
to be adjusted to be more than 1500 bytes.
Using LSP Ping for LDP IPv4 FEC
When you enter the ping mpls privileged EXEC command to begin an LSP ping operation, the keyword
that follows specifies the Forwarding Equivalence Class (FEC) that is the target of the LSP ping to which
you want to verify connectivity.
Command
Purpose
ping mpls ipv4
destination-address
destination-mask
To verify LSP path from Cisco ASR 901 to remote peer. The
keywords have these meanings:
•
destination-address destination-mask—Specify the address and
network mask of the target FEC.
Using LSP Traceroute for LDP IPv4 FEC
The LSP traceroute originator sends incremental MPLS echo requests to discover the downstream
mapping of each successive hop. When the originating provider edge router receives the reply from the
intermediate router, it forms another MPLS echo request with the same target FEC and the time-to-live
is incremented by one.
Command
Purpose
traceroute mpls ipv4 destination-address To configure LSP IPv4 traceroute.
destination-mask
• destination-address destination-mask is the address
and network mask of the target FEC.
Using LSP Ping for Pseudowire
Use the ping mpls pseudowire command to verify the AToM pseudowire path.
Command
Purpose
ping mpls pseudowire ipv4-address vc_id
vc-id-value
To verify AToM pseudowire path from the ASR 901
router to remote peer.
•
ipv4-address is the ip address of the remote peer.
•
vc_id is the virtual circuit id.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
17-3
Chapter 17
Configuring MPLS OAM
Configuring MPLS OAM
Using LSP Traceroute over Pseudowire
Use the traceroute mpls pseudowire command to verify the pseudowire path and the next hop details
at the remote peer.
Command
Purpose
traceroute mpls pseudowire ipv4-address To verify AToM pseudowire path from the ASR 901
vc_id vc-id-value segment
router to remote peer and next hop details at remote peer.
•
ipv4-address is the ip address of the remote peer.
•
vc_id is the virtual circuit id.
Displaying AToM VCCV capabilities
Use the show mpls l2transport command to display the AToM VCCV capabilities.
Command
Purpose
show mpls l2transport binding vc_id
vc-id-value
To display AToM VCCV capabilities negotiated between
the peers.
•
vc_id is the virtual circuit id.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
17-4
OL-23826-09
CH A P T E R
18
Configuring Routing Protocols
In addition to static routing, the Cisco ASR 901 supports the following routing protocols:
•
OSPF—An Interior Gateway Protocol (IGP) designed for IP networks that supports IP subnetting
and tagging of externally derived routing information. OSPF also allows packet authentication and
uses IP multicast when sending and receiving packets. For more information on how to configure
OSPF, see the IP Routing: OSPF Configuration Guide, Cisco IOS Release 15.1S.
•
IS-IS—An Open System Interconnection (OSI) protocol that specifies how routers communicate
with routers in different domains. For more information on how to configure IS–IS, see the IP
Routing: ISIS Configuration Guide, Cisco IOS Release 15.1S.
•
BGP—An interdomain routing protocol designed to provide loop-free routing between separate
routing domains that contain independent routing policies (autonomous systems). For more
information on how to configure BGP, see the IP Routing: BGP Configuration Guide, Cisco IOS
Release 15.1S.
For information about Bidirectional Forwarding Detection (BFD) including sample routing
configurations with BFD, see Configuring BFD.
Note
Cisco ASR 901 router supports IP routing on SVI interfaces.
Note
Cisco ASR 901 router does not support IGP fast timers.
Note
The maximum number of prefixes supported in Cisco ASR 901 router is 12000.
Note
The maximum number of SVI's supported in Cisco ASR 901 router is 250.
Changing Default Hashing Algorithm for ECMP
The hashing algorithm for ECMP is changed from Cisco IOS Release 15.3(2)S onwards. You can use
the following commands to configure various types of ECMP hash configurations for improved load
distribution of IP traffic.
•
asr901-ecmp-hash-config global-type
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
18-1
Chapter 18
•
asr901-ecmp-hash-config ipv4-type
•
asr901-ecmp-hash-config ipv6-type
•
asr901-ecmp-hash-config mpls-to-ip
Configuring Routing Protocols
For detailed information on these commands, see the Cisco ASR 901 Series Aggregation Services Router
Command Reference guide at the following location:
http://www.cisco.com/en/US/docs/wireless/asr_901/Command/Reference/asr901_cmdref.html
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
18-2
OL-23826-09
CH A P T E R
19
Configuring Bidirectional Forwarding Detection
Bidirectional Forwarding Detection (BFD) provides a low-overhead, short-duration method of detecting
failures in the forwarding path between two adjacent routers, including the interfaces, data links, and
forwarding planes. BFD is a detection protocol that you enable at the interface and routing protocol
levels.
Contents
•
Understanding BFD, page 19-1
•
Configuring BFD, page 19-1
•
Configuration Examples for BFD, page 19-7
Understanding BFD
Cisco supports the BFD asynchronous mode, in which two routers exchange BFD control packets to
activate and maintain BFD neighbor sessions. To create a BFD session, you must configure BFD on both
systems (or BFD peers). After you enable BFD on the interface and the router level for the appropriate
routing protocols, a BFD session is created, BFD timers are negotiated, and the BFD peers begin to send
BFD control packets to each other at the negotiated interval.
Configuring BFD
This section contains the following topics:
•
BFD Configuration Guidelines and Restrictions, page 19-2
•
Configuring BFD for OSPF, page 19-2
•
Configuring BFD for BGP, page 19-4
•
Configuring BFD for IS-IS, page 19-4
•
Configuring BFD for Static Routes, page 19-6
For more information about BFD, refer to the IP Routing: BFD Configuration Guide, Cisco IOS Release
15.1S.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
19-1
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuring BFD
Note
Cisco ASR 901 supports BFD echo mode.
BFD Configuration Guidelines and Restrictions
•
The minimum time interval supported for BFD is 50 ms.
•
The maximum number of stable sessions supported for BFD with 50 ms interval is 4.
•
When you configure BFD and REP on Cisco ASR 901, REP protocol goes down.
•
After enabling BFD on an interface, if you configure an IPV4 static route with BFD routing through
this interface, and if the IPV4 BFD session does not get established, unconfigure BFD on the given
interface, and configure it again. The BFD session comes up.
•
When you move the BFD configuration saved in flash memory to the running configuration, BFD
session is re-established.
•
When BFD is configured on a port from which more than 70% of line rate data traffic is egressing,
there is a drop in control packets including BFD packets. To avoid BFD packet drop, you have to
configure QoS policies that give higher priority for both CPU generated BFD packets and BFD echo
reply packets.
Configuring BFD for OSPF
This section describes how to configure BFD on the Cisco ASR 901.
Configuring BFD for OSPF on One of More Interfaces
Complete these steps to configure BFD for OSPF on a single interface.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
Router(config)# interface vlan1
Router(config-if)#
Specifies an interface to configure.
Step 4
Router(config-if)# ip ospf bfd
Enables BFD for OSPF on the interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
19-2
OL-23826-09
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuring BFD
Command
Purpose
Step 5
Router(config-if)# bfd interval 50
min_rx 50 multiplier 3
Specifies the BFD session parameters.
Step 6
end
Exits configuration mode.
Example:
Router(config-if)# end
Router#
Note
You can also use the show bfd neighbors and show ip ospf commands to display troubleshooting
information about BFD and OSPF.
Configuring BFD for OSPF on All Interfaces
Complete these steps to configure BFD for OSPF on all interfaces.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
Router(config)# router ospf 100
Creates a configuration for an OSPF process.
Step 4
Router(config)# bfd all-interfaces
Enables BFD globally on all interfaces associated with the OSPF routing
process.
Step 5
exit
Exits configuration mode.
Example:
Router(config)# exit
Router#
Note
You can disable BFD on a single interface using the ip ospf bfd disable command when configuring the
relevant interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
19-3
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuring BFD
Configuring BFD for BGP
Complete these steps to configure BFD for BGP.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
Router(config)# router bgp as-tag
Specifies a BGP process and enter router configuration mode.
Step 4
Router(config)# neighbor ip-address
fall-over bfd
Enables support for BFD failover.
Step 5
exit
Exits configuration mode.
Example:
Router(config)# exit
Router#
Step 6
show bfd neighbors [details]
show ip bgp neighbor
Use the following commands to verify the BFD configuration:
•
show bfd neighbors [details] —Verifies that the BFD neighbor is
active and displays the routing protocols that BFD has registered.
•
show ip bgp neighbor—Displays information about BGP and TCP
connections to neighbors.
Configuring BFD for IS-IS
This section describes how to configure BFD for IS-IS routing.
Configuring BFD for IS-IS on a Single Interface
Complete these steps to configure BFD for IS-IS on a single interface.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
19-4
OL-23826-09
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuring BFD
Command
Purpose
Step 3
Router(config)# interface vlan1
Router(config-if)#
Enters interface configuration mode.
Step 4
Router(config-if) ip router isis
[tag]
Enables support for IPv4 routing on the interface.
Step 5
Router(config-if) isis bfd
Enables BFD on the interfaces.
Step 6
exit
Exits configuration mode.
Example:
Router(config)# exit
Router#
Note
You can use the show bfd neighbors and show clns interface commands to verify your configuration.
Configuring BFD for IS-IS for All Interfaces
Complete these steps to configure BFD for IS-IS on all interfaces.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
Router(config)# interface vlan1
Router(config-if)#
Enters interface configuration mode.
Step 4
Router(config-if) ip router isis
[tag]
Enables support for IPv4 routing on the interface.
Step 5
Router(config-router)# bfd
all-interfaces
Enables BFD globally on all interfaces associated with the IS-IS routing
process.
Step 6
Router(config-router)# exit
Router(config)#
Exits the interface.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
19-5
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuring BFD
Step 7
Step 8
Command
Purpose
Router(config)# interface vlan1
Router(config-if) ip router isis
[tag]
If you want to enable BFD on a per-interface basis for one or more
interfaces associated with the IS-IS routing process, complete the
following steps:
exit
a.
Use the interface command to enter interface configuration mode.
b.
Use the ip router isis command to enables support for IPv4 routing
on the interface.
Exit configuration mode.
Example:
Router(config)# exit
Router#
Note
You can use the show bfd neighbors and show clns interface commands to verify your configuration.
Configuring BFD for Static Routes
Complete these steps to configure BFD for static routes.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
Router(config)# interface vlan 150
Specifies an interface and enters interface configuration mode.
Step 4
Router(config-if)# ip address
10.201.201.1 255.255.255.0
Configures an IP address for the interface.
Step 5
Router(config-if)# bfd interval 50
min_rx 50 multiplier 3
Enables BFD on the interface.
Step 6
exit
Exits configuration mode.
Example:
Router(config-if)# exit
Router#(config)
Step 7
Router(config)# ip route static bfd
Vlan150 150.0.0.2
Specifies neighbors for the static routes in BFD.
Step 8
Router(config)# ip route 77.77.77.0
255.255.255.0 Vlan150
Specifies the exit interface for the static route in BFD.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
19-6
OL-23826-09
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuration Examples for BFD
Note
You can use the show ip static route command to verify your configuration.
Configuration Examples for BFD
The following section contains sample configurations for each routing protocol using BFD.
Note
This section provides partial configurations intended to demonstrate a specific feature.
•
BFD with OSPF on All Interfaces, page 19-7
•
BFD with OSPF on Individual Interfaces, page 19-7
•
BFD with BGP, page 19-8
•
BFD with IS-IS on All Interfaces, page 19-8
•
BFD with IS-IS on Individual Interfaces, page 19-8
•
BFD with Static Routes, page 19-9
BFD with OSPF on All Interfaces
interface GigabitEthernet0/10
description Core_facing
negotiation auto
service instance 150 ethernet
encapsulation untagged
bridge-domain 150
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
bfd interval 50 min_rx 50 multiplier 3
!
router ospf 7
network 99.99.99.99 0.0.0.0 area 0
network 150.0.0.0 0.0.0.255 area 0
bfd all-interfaces
BFD with OSPF on Individual Interfaces
interface GigabitEthernet0/10
description Core_facing
negotiation auto
service instance 150 ethernet
encapsulation untagged
bridge-domain 150
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
bfd interval 50 min_rx 50 multiplier 3
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
19-7
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuration Examples for BFD
ip ospf bfd
!
router ospf 7
network 99.99.99.99 0.0.0.0 area 0
network 150.0.0.0 0.0.0.255 area 0
BFD with BGP
interface GigabitEthernet0/10
description Core_facing
negotiation auto
service instance 150 ethernet
encapsulation untagged
bridge-domain 150
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
bfd interval 50 min_rx 50 multiplier 3
!
router bgp 1
bgp log-neighbor-changes
neighbor 150.0.0.2 remote-as 2
neighbor 150.0.0.2 fall-over bfd
BFD with IS-IS on All Interfaces
interface GigabitEthernet0/10
description Core_facing
negotiation auto
service instance 150 ethernet
encapsulation untagged
bridge-domain 150
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
bfd interval 50 min_rx 50 multiplier 3
!
router isis
net 49.0001.2222.2222.2222.00
bfd all-interfaces
!
BFD with IS-IS on Individual Interfaces
interface GigabitEthernet0/10
description Core_facing
negotiation auto
service instance 150 ethernet
encapsulation untagged
bridge-domain 150
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
19-8
OL-23826-09
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuration Examples for BFD
interface Vlan150
ip address 150.0.0.1 255.255.255.0
bfd interval 50 min_rx 50 multiplier 3
isis bfd
!
router isis
net 49.0001.2222.2222.2222.00
!
BFD with Static Routes
interface GigabitEthernet0/10
description Core_facing
negotiation auto
service instance 150 ethernet
encapsulation untagged
bridge-domain 150
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
bfd interval 50 min_rx 50 multiplier 3
!
ip route static bfd Vlan150 150.0.0.2
ip route 77.77.77.0 255.255.255.0 Vlan150 150.0.0.2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
19-9
Chapter 19
Configuring Bidirectional Forwarding Detection
Configuration Examples for BFD
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
19-10
OL-23826-09
CH A P T E R
20
Configuring T1/E1 Controllers
This chapter provides information about configuring the T1/E1 controllers on Cisco ASR 901 router.
Contents
•
Configuring the Card Type, page 20-1
•
Configuring E1 Controllers, page 20-2
•
Configuring T1 Controllers, page 20-4
•
Troubleshooting Controllers, page 20-5
Configuring the Card Type
Perform a basic card type configuration by enabling the router, enabling an interface, and specifying the
card type as described below. You might also need to enter other configuration commands, depending on
the requirements for your system configuration and the protocols you plan to route on the interface.
Note
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
To select and configure a card type, complete the following steps:
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
20-1
Chapter 20
Configuring T1/E1 Controllers
Configuring E1 Controllers
Step 3
Command
Purpose
card type {e1 | t1} slot subslot
Sets the card type. The command has the following syntax:
Example:
Router(config)# card type e1 0 0
•
slot—Slot number of the interface.
•
subslot—0.
When the command is used for the first time, the configuration takes
effect immediately. A subsequent change in the card type does not take
effect unless you enter the reload command or reboot the router.
Note
Step 4
exit
When you are using the card type command to change the
configuration of an installed card, you must first enter the no card
type {e1 | t1} slot subslot command. Then enter the card type {e1
| t1} slot subslot command for the new configuration information.
Exit configuration mode.
Example:
Router(config)# exit
Router#
Configuring E1 Controllers
Perform a basic E1 controller configuration by specifying the E1 controller, entering the clock source,
specifying the channel-group, configuring the serial interface, configuring PPP encapsulation, and
enabling keepalive packets. You might also need to enter other configuration commands, depending on
the requirements for your system configuration and the protocols you plan to route on the interface.
Note
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
To configure the E1 controllers, complete the following steps in the global configuration mode:
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
controller e1 slot/port
Specifies the controller that you want to configure.
Example:
Router(config)# controller e1 0/0
Router(config-controller)#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
20-2
OL-23826-09
Chapter 20
Configuring T1/E1 Controllers
Configuring E1 Controllers
Step 4
Command
Purpose
framing {crc4 | no-crc4}
Specifies the framing type.
Example:
Router(config-controller)# framing
crc4
Step 5
Specifies the line code format.
linecode hdb3
Example:
Router(config-controller)# linecode
hdb3
Step 6
Router(config-controller)#
channel-group channel-no timeslots
timeslot-list speed {64}
Example:
Router(config-controller)#
channel-group 0 timeslots 1-31
speed 64
Specifies the channel-group and time slots to be mapped. After you
configure a channel-group, the serial interface is automatically created.
The syntax is:
•
channel-no—ID number to identify the channel group. The valid
range is from 0–30.
•
timeslot-list—Timeslots (DS0s) to include in this channel-group. The
valid time slots are from 1–31.
•
speed {64}—The speed of the DS0.
The example configures the channel-group and time slots for the E1
controller:
Note
When you are using the channel-group channel-no timeslots
timeslot-list {64} command to change the configuration of an
installed card, you must enter the no channel-group channel-no
timeslots timeslot-list speed {64} command first. Then enter the
channel-group channel-no timeslots timeslot-list {64} command
for the new configuration information.
Step 7
Router(config-controller)# exit
Router(config)#
Exits controller configuration mode.
Step 8
interface serial slot/port:channel
Configures the serial interface. Specify the E1 slot, port number, and
channel-group.
Example:
When the prompt changes to Router(config-if), you have entered
interface configuration mode.
Router(config)# interface serial
0/0:1
Router(config-if)#
Step 9
encapsulation ppp
Note
To see a list of the configuration commands available to you, enter
? at the prompt or press the Help key while in the configuration
mode.
Specifies PPP encapsulation on the interface.
Example:
Router(config-if)# encapsulation
ppp
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
20-3
Chapter 20
Configuring T1/E1 Controllers
Configuring T1 Controllers
Step 10
Command
Purpose
keepalive [period [retries]]
Enables keepalive packets on the interface and specify the number of
times keepalive packets are sent without a response before the router
disables the interface.
Example:
Router(config-if)# keepalive
[period [retries]]
Step 11
Router(config-if)# end
Router#
Exits interface configuration mode.
Configuring T1 Controllers
Use the following steps to perform a basic T1 controller configuration: specifying the T1 controller,
specifying the framing type, specifying the line code form, specifying the channel-group and time slots
to be mapped, configuring the cable length, configuring the serial interface, configuring PPP
encapsulation, and enabling keepalive packets. You might also need to enter other configuration
commands, depending on the requirements for your system configuration and the protocols you plan to
route on the interface.
Note
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
To configure the T1 interfaces, complete the following steps in the global configuration mode:
Command
Purpose
Step 1
enable
Enables privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
Enters global configuration mode.
Step 3
controller t1 slot/subslot
Specifies the controller that you want to configure. The command has the
following syntax:
Example:
•
slot—Slot number of the interface. The slot number should be 0.
Router(config-controller)#
controller t1 0/0
•
subslot—Subslot number of the interface. The supported range for
subslot is 0 to 15.
Step 4
Router(config-controller)# framing
esf
Specifies the framing type.
Step 5
Router(config-controller)# linecode
b8zs
Specifies the line code format.
Step 6
Router(config-controller)#
channel-group 0 timeslots 1-24
speed 64
Specifies the channel-group and time slots to be mapped. After you
configure a channel-group, the serial interface is automatically created.
•
The default speed of the channel-group is 64.
•
The supported range for channel-group is 0 to 23.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
20-4
OL-23826-09
Chapter 20
Configuring T1/E1 Controllers
Troubleshooting Controllers
Command
Purpose
Step 7
Router(config-controller)#
cablelength {long [-15db | -22.5db
| -7.5db | 0db] short [110ft |
220ft | 330ft| 440ft | 550ft |
600ft]}
Configures the cable length.
Step 8
Router(config-controller)# exit
Exits controller configuration mode.
Step 9
Router(config)# interface serial
slot/port:channel
Configures the serial interface. Specify the T1 slot (always 0), port
number, and channel-group.
Step 10
Router(config-if)# encapsulation
ppp
Enters the following command to configure PPP encapsulation.
Step 11
Router(config-if)# keepalive
[period [retries]]
Enables keepalive packets on the interface and specify the number of
times that keepalive packets will be sent without a response the interface
is brought down:
Step 12
exit
Exits configuration mode.
Example:
Router(config)# exit
Router#
Troubleshooting Controllers
This line card supports local and network T1/E1 loopback modes, and remote T1 loopback modes for
testing, network fault isolation, and agency compliance. You can test T1/E1 lines in local and network
loopback modes. You can also test T1 lines in remote mode.
Note
The ASR901 supports activating or deactivating payload and line loopback modes using FDL in ESF
framing mode as defined in the T1.403 ANSI standard. The implementation confirms to ANSI
T1.403-1999, sections 9.4.2.1 and 9.4.2.2. The ASR901 only accepts remotely initiated loopback
requests and does not support initiation of FDL remote loopback requests.
Note
Bit-error-rate testing and loopbacks are used to resolve problems and test the quality of T1/E1 links.
Troubleshooting E1 Controllers
To troubleshoot the E1 line card, complete the following steps in the controller configuration mode:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
20-5
Chapter 20
Configuring T1/E1 Controllers
Troubleshooting Controllers
Step 1
Command
Purpose
enable
Enables privileged EXEC mode. Enter your password if prompted.
Example:
Router# enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
controller e1 slot/subslot
Example:
Router(config-controller)#
controller e1 0/0
Step 4
loopback {local | network {line|
payload}}
Sets the controller type. The command has the following syntax:
•
slot—Slot number of the interface.
•
subslot—0.
Sends the packets from a port in local loopback to the remote end.
•
local—Configures the line card to loop the transmitted traffic back to
the line card as E1 received traffic and transmits AIS to the remote
receiver.
•
network line—Configures the E1 line card to loop the received traffic
back to the remote device after passing them through the line
loopback mode of the framer. The framer does not re-clock or reframe
the incoming traffic.
•
network payload—Configures the E1 line card to loop the received
traffic back to the remote device after passing them through the
payload loopback mode of the framer. The framer re-clocks and
reframes the incoming traffic before sending it to the network.
Example:
Router(config-controller)# loopback
network line
Step 5
Exits controller configuration mode.
exit
Example:
Router(config-controller)# exit
Troubleshooting T1 Controllers
To troubleshoot the T1 line card, complete the following steps in the controller configuration mode:
Step 1
Command
Purpose
enable
Enables privileged EXEC mode. Enter your password if prompted.
Example:
Router# enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
20-6
OL-23826-09
Chapter 20
Configuring T1/E1 Controllers
Troubleshooting Controllers
Step 3
Command
Purpose
controller t1 slot/subslot
Sets the controller type. The command has the following syntax:
Example:
Router(config-controller)#
controller t1 0/0
Step 4
loopback {diagnostic | local {line|
payload}}
Example:
Router(config-controller)# loopback
local line
Step 5
exit
•
slot—Slot number of the interface.
•
subslot—0.
Sends the packets from a port in local loopback to the remote end.
•
diagnostic—Configures the line card to loop data from the transmit
path to the receiver path.
•
local line—Configures the T1 line card to loop the received traffic
back to the remote device after passing them through the line
loopback mode of the framer. The framer does not re-clock or reframe
the incoming traffic.
•
local payload—Configures the T1 line card to loop the received
traffic back to the remote device after passing them through the
payload loopback mode of the framer. The framer re-clocks and
reframes the incoming traffic before sending it to the network.
Exits controller configuration mode.
Example:
Router(config-controller)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
20-7
Chapter 20
Configuring T1/E1 Controllers
Troubleshooting Controllers
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
20-8
OL-23826-09
CH A P T E R
21
Configuring Pseudowire
Cisco Pseudowire Emulation Edge-to-Edge (PWE3) allows you to transport traffic using traditional
services such as E1/T1 over a packet-based backhaul technology such as MPLS or IP. A pseudowire
(PW) consists of a connection between two provider edge (PE) devices that connects two attachment
circuits (ACs), such as ATM VPIs/VCIs or E1/T1 links.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for Configuring Pseudowire” section on page 21-37.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Understanding Pseudowires, page 21-2
•
Hot Standby Pseudowire Support for ATM/IMA, page 21-3
•
Configuring Pseudowire, page 21-4
•
Configuring L2VPN Pseudowire Redundancy, page 21-20
•
Configuring Hot Standby Pseudowire Support for ATM/IMA, page 21-22
•
TDM Local Switching, page 21-27
•
Configuration Examples of Hot Standby Pseudowire Support for ATM/IMA, page 21-30
•
Configuration Examples for Pseudowire, page 21-31
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-1
Chapter 21
Configuring Pseudowire
Understanding Pseudowires
Figure 21-1
TDM
Cisco ASR 901 Router in a PWE3—Example
xconnect
xconnect
TDM
MPLS/IP
Emulated Circuit
284293
Pseudowire
Understanding Pseudowires
Pseudowires (PWs) manage encapsulation, timing, order, and other operations in order to make it
transparent to users; the PW tunnel appears as an unshared link or circuit of the emulated service.
There are limitations that impede some applications from utilizing a PW connection.
Cisco supports the following standards-based PWE types:
•
Structure-Agnostic TDM over Packet, page 21-2
•
Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network, page 21-3
•
Transportation of Service Using Ethernet over MPLS, page 21-3
Structure-Agnostic TDM over Packet
SAToP encapsulates TDM bit-streams (T1, E1, T3, E3) as PWs over PSNs. It disregards any structure
that may be imposed on streams, in particular the structure imposed by the standard TDM framing. The
protocol used for emulation of these services does not depend on the method in which attachment circuits
are delivered to the PEs. For example, a T1 attachment circuit is treated the same way for all delivery
methods, including: PE on copper, multiplex in a T3 circuit, mapped into a virtual tributary of a
SONET/SDH circuit, or carried over a network using unstructured Circuit Emulation Service (CES).
Termination of specific carrier layers used between the PE and circuit emulation (CE) is performed by
an appropriate network service provider (NSP).
For instructions on how to configure SAToP, see Configuring Structure-Agnostic TDM over Packet,
page 21-9.
For a sample SAToP configuration, see Configuration Examples for Pseudowire, page 21-31.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-2
OL-23826-09
Chapter 21
Configuring Pseudowire
Hot Standby Pseudowire Support for ATM/IMA
Structure-Aware TDM Circuit Emulation Service over Packet-Switched
Network
CESoPSN encapsulates structured (NxDS0) TDM signals as PWs over PSNs.
Emulation of NxDS0 circuits saves PSN bandwidth and supports DS0-level grooming and distributed
cross-connect applications. It also enhances resilience of CE devices due to the effects of loss of packets
in the PSN.
For instructions on how to configure CESoPSN, see Configuring Circuit Emulation Service over
Packet-Switched Network, page 21-14.
For a sample CESoPSN configuration, see Configuration Examples for Pseudowire, page 21-31.
Transportation of Service Using Ethernet over MPLS
Ethernet over MPLS (EoMPLS) PWs provide a tunneling mechanism for Ethernet traffic through an
MPLS-enabled Layer 3 core network. EoMPLS PWs encapsulate Ethernet protocol data units (PDUs)
inside MPLS packets and use label switching to forward them across an MPLS network. EoMPLS PWs
are an evolutionary technology that allows you to migrate packet networks from legacy networks while
providing transport for legacy applications. EoMPLS PWs also simplify provisioning, since the provider
edge equipment only requires Layer 2 connectivity to the connected customer edge (CE) equipment. The
Cisco ASR 901 implementation of EoMPLS PWs is compliant with the RFC 4447 and 4448 standards.
For instructions on how to create an EoMPLS PW, see Configuring Transportation of Service Using
Ethernet over MPLS.
Limitations
•
When configuring an EoMPLS pseudowire on the Cisco ASR 901, you cannot configure an IP
address on the same interface as the pseudowire.
•
Layer 2 Tunneling Protocol, version 2 and 3 (L2TPv2 and L2TPv3) is not supported on the
Cisco ASR 901 series routers.
Hot Standby Pseudowire Support for ATM/IMA
The Hot Standby Pseudowire Support for Inverse Multiplexing over ATM (IMA) feature improves the
availability of pseudowires by detecting failures and handling them with minimal disruption to the
service. This feature allows the backup pseudowire to be in a “hot standby” state, so that it can
immediately take over if the primary pseudowire fails.
A backup pseudowire is provisioned and corresponding entries are populated to hardware tables. When
the primary pseudowire goes down, the backup pseudowire is used to switch the packets.
This feature supports the following transport types:
•
ATM AAL5 in VC mode
•
ATM in VP mode
•
ATM in port mode
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-3
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Configuring Pseudowire
This section describes how to configure pseudowire on the Cisco ASR 901. The Cisco ASR 901
supports pseudowire connections using CESoPSN. The following sections describe how to configure
pseudowire connections on the Cisco ASR 901.
•
Configuring Pseudowire Classes, page 21-4
•
Configuring CEM Classes, page 21-6
•
Configuring a Backup Peer, page 21-8
•
Configuring Structure-Agnostic TDM over Packet, page 21-9
•
Configuring Circuit Emulation Service over Packet-Switched Network, page 21-14
•
QoS for CESoPSN over UDP and SAToP over UDP, page 21-18
•
Configuring Transportation of Service Using Ethernet over MPLS, page 21-18
For full descriptions of each command, see the Cisco ASR 901 Series Aggregation Services Router IOS
Command Reference.
For pseudowire configuration examples, see Configuration Examples for Pseudowire, page 21-31
Configuring Pseudowire Classes
A pseudowire class allows you to create a single configuration template for multiple pseudowire
connections. You can apply pseudowire classes to all pseudowire types.
Complete the following steps to configure a pseudowire class:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
pseudowire-class class-name
4.
encapsulation mpls
5.
interface cemslot/port
6.
cem group-number
7.
xconnect ip pw-class pseudowire-class
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-4
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
pseudowire-class class-name
Creates a new pseudowire class.
Example:
Router(config)# pseudowire-class
newclass
Step 4
encapsulation mpls
Sets an encapsulation type.
Example:
Router(config-pw-class)#
encapsulation mpls
Step 5
interface cemslot/port
Configures the pseudowire interface to use for the new pseudowire class.
This example shows a CESoPSN interface.
Example:
Router(config)# interface cem0/0
Step 6
cem group-number
Defines a CEM channel.
Example:
Router(config-if)# cem 0
Step 7
xconnect ip pw-class
pseudowire-class
Binds an attachment circuit to the CESoPSN interface to create a
CESoPSN pseudowire. Use the pw-class parameter to specify the
pseudowire class that the CESoPSN pseudowire interface uses.
Example:
Router(cfg-if-cem)# xconnect
1.1.1.1 40 pw-class myclass
Note
You cannot use the encapsulation mpls parameter with the pw-class parameter.
Note
The use of the xconnect command can vary depending on the type of pseudowire you configure.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-5
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Configuring CEM Classes
A CEM class allows you to create a single configuration template for multiple CEM pseudowires.
Note
•
Cisco IOS release 15.3(3)S automatically enables forward-alarm ais configuration (under the
config-controller configuration mode). To disable this configuration, use the no forward-alarm ais
command.
•
The forward-alarm ais configuration is applicable only for CESoP. It is not supported for SAToP.
•
You must run the no forward-alarm ais command before using CESoP with controllers in loopback
(either through loopback command under controller or by using a physical loopback jack).
•
Though the forward-alarm ais command (and its no form) was not supported in previous releases,
the Cisco ASR 901 router behaved as if this command was configured under the controller interface.
Complete the following steps to configure a CEM class:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
class cem cem-class-name
4.
payload-size size
5.
dejitter-buffer size
6.
idle-pattern size
7.
exit
8.
interface cem slot/port
9.
no ip address
10. cem group-number
11. cem class cem-class-name
12. xconnect ip-address encapsulation mpls
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-6
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 3
Command
Purpose
class cem cem-class-name
Creates a new CEM class
Example:
Router(config)# class cem
mycemclass
Step 4
payload-size size
Specifies the payload for the CEM class.
Example:
Router(config-cem-class)#
payload-size 512
Step 5
dejitter-buffer size
Specifies the dejitter buffer for the CEM class.
Example:
Router(config-cem-class)#
dejitter-buffer 10
Step 6
idle-pattern size
Specifies the idle-pattern for the CEM class.
Example:
Router(config-cem-class)#
idle-pattern 0x55
Step 7
exit
Returns to the config prompt.
Example:
Router(config-cem-class)# exit
Step 8
interface cem slot/port
Configure the CEM interface that you want to use for the new CEM class.
Note
Example:
The use of the xconnect command can vary depending on the type
of pseudowire you are configuring.
Router(config)# interface cem 0/0
Step 9
no ip address
Disables the IP address configuration for the physical layer interface.
Example:
Router(config-if)# no ip address
Step 10
cem group-number
Enters the CEM configuration mode.
Example:
Router(config-if)# cem 0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-7
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 11
Command
Purpose
cem class cem-class-name
Specifies the CEM class name.
Example:
Router(config-if-cem)# cem class
mycemclass
Step 12
xconnect ip-address encapsulation
mpls
Binds an attachment circuit to the CEM interface to create a pseudowire
Example:
Router(config-if-cem)# xconnect
10.10.10.10 200 encapsulation mpls
Configuring a Backup Peer
A backup peer provides a redundant pseudowire (PW) connection in the case that the primary PW loses
connection; if the primary PW goes down, the Cisco ASR 901 diverts traffic to the backup PW.
Complete the following steps to configure a backup peer:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface cemslot/port
4.
cem group-number
5.
xconnect peer-loopback-ip-address encapsulation mpls
6.
backup peer peer-router-ip-address vcid [pw-class pw-class-name]
7.
backup delay enable-delay [disable-delay | never]
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface cemslot/port
Configures the pseudowire interface to use for the new pseudowire class.
Example:
Router(config)# interface cem0/0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-8
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 4
Command
Purpose
cem group-number
Defines a CEM channel.
Example:
Router(config-if)# cem 0
Step 5
Binds an attachment circuit to the CEM interface to create a pseudowire.
xconnect peer-loopback-ip-address
encapsulation mpls
Example:
Router(config-if-cem)# xconnect
10.10.10.20 encapsulation mpls
Step 6
Defines the address and VC of the backup peer.
backup peer peer-router-ip-address
vcid [pw-class pw-class-name]
Example:
Router(config-if-cem-xconn)# backup
peer 10.10.10.12 10 344
Step 7
Specifies the delay before the router switches pseudowire traffic to the
backup peer VC.
backup delay enable-delay
[disable-delay | never]
Where:
Example:
Router(config-if-cem-xconn)# backup
delay 30 never
•
enable-delay—Time before the backup PW takes over for the primary
PW.
•
disable-delay—Time before the restored primary PW takes over for
the backup PW.
•
never—Disables switching from the backup PW to the primary PW.
Configuring Structure-Agnostic TDM over Packet
Complete the following steps to configure Structure-Agnostic TDM over Packet (SAToP) on the
Cisco ASR 901:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller {t1 | e1} slot/port
4.
cem-group group-number unframed
5.
interface CEMslot/port
6.
no ip address
7.
cem group-number
8.
xconnect ip-address encapsulation mpls
9.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-9
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
controller {t1|e1} slot/port
Configures the T1 or E1 interface.
Example:
Router(config)# controller t1 0/4
Step 4
cem-group group-number unframed
Example:
Assigns channels on the T1 or E1 circuit to the CEM channel. This
example uses the unframed parameter to assign all the T1 timeslots to the
CEM channel.
Router(config-if)# cem-group 4
unframed
Step 5
interface CEMslot/port
Configures the pseudowire interface to use for the new pseudowire class.
Example:
Router(config)# interface CEM0/4
Step 6
no ip address
Disables the IP address configuration for the physical layer interface.
Example:
Router(config)# no ip address
Step 7
cem group-number
Defines a CEM group.
Example:
Router(config-if)# cem 4
Step 8
xconnect ip-address encapsulation
mpls
Binds an attachment circuit to the CEM interface to create a pseudowire.
This example creates a pseudowire by binding the CEM circuit 304 to the
remote peer 30.30.2.304.
Example:
Router(config-if-cem)# xconnect
30.30.30.2 304 encapsulation mpls
Step 9
Exits configuration mode.
exit
Example:
Router(cfg-if-cem-xconn)# exit
Note
When creating IP routes for a pseudowire configuration, we recommend that you build a route from the
xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route
30.30.30.2 255.255.255.255 1.2.3.4.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-10
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Configuring a SAToP Pseudowire with UDP Encapsulation
Complete the following steps to configure a SAToP pseudowire with UDP encapsulation:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
pseudowire-class pseudowire-class-name
4.
encapsulation udp
5.
ip local interface loopback interface-number
6.
ip tos value value-number
7.
ip ttl number
8.
controller {e1 | t1} slot/port
9.
cem-group group-number unframed
10. exit
11. interface cem slot/port
12. no ip address
13. cem group-number
14. xconnect peer-router-id vcid {pseudowire-class name}
15. udp port local-udp-port remote remote-udp-port
16. exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
pseudowire-class
pseudowire-class-name
Creates a new pseudowire class.
Example:
Router(config)# pseudowire-class
udpClass
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-11
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 4
Command
Purpose
encapsulation udp
Specifies the UDP transport protocol.
Example:
Router(config-pw-class)#
encapsulation udp
Step 5
ip local interface loopback
interface-number
Configures the IP address of the provider edge (PE) router interface as the
source IP address for sending tunneled packets.
Example:
Router(config-pw-class)# ip local
interface Loopback 1
Step 6
ip tos value value-number
Specifies the type of service (ToS) level for IP traffic in the pseudowire.
Example:
Router(config-pw-class)# ip tos
value 100
Step 7
ip ttl number
Specifies a value for the time-to-live (TTL) byte in the IP headers of Layer
2 tunneled packets.
Example:
Router(config-pw-class)# ip ttl 100
Step 8
controller {e1|t1} slot/port
Enters E1/T1 controller configuration mode.
Example:
Router(config)# controller [e1|t1]
0/0
Step 9
cem-group group-number unframed
Example:
Assigns channels on the T1 or E1 circuit to the CEM channel. This
example uses the unframed parameter to assign all the T1 timeslots to the
CEM channel.
Router(config-controller)#
cem-group 4 unframed
Step 10
exit
Exits controller configuration.
Example:
Router(config-controller)# exit
Step 11
interface cem slot/port
Example:
Selects the CEM interface where the CEM circuit (group) is located
(where slot/subslot is the SPA slot and subslot and port is the SPA port
where the interface exists).
Router(config)# interface CEM0/4
Step 12
no ip address
Disables the IP address configuration for the physical layer interface.
Example:
Router(config)# no ip address
Step 13
cem group-number
Defines a CEM channel.
Example:
Router(config-if)# cem 4
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-12
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 14
Command
Purpose
xconnect peer-router-id vcid
{pseudowire-class name}
Binds an attachment circuit to the CEM interface to create a pseudowire.
This example creates a pseudowire by binding the CEM circuit 5 to the
remote peer 30.30.30.2.
Example:
Note
Router(config-if-cem)# xconnect
30.30.30.2 305 pw-class udpClass
Step 15
udp port local <local-udp-port>
remote <remote-udp-port>
When creating IP routes for a pseudowire configuration, we
recommend that you build a route from the cross-connect address
(LDP router-ID or loopback address) to the next hop IP address,
such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
Specifies a local and remote UDP port for the connection. Valid port
values for SAToP pseudowires using UDP are from 49152–57343.
Example:
Router(config-if-cem-xconn)# udp
port local 49150 remote 55000
Step 16
exit
Exits the CEM interface.
Example:
Router(config-if-cem-xconn)# exit
Step 17
exit
Exits the configuration mode.
Example:
Router(config-if)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-13
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Configuring Circuit Emulation Service over Packet-Switched Network
Complete the following steps to configure Circuit Emulation Service over Packet-Switched Network
(CESoPSN):
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller {e1 | t1} slot/port
4.
cem-group group-number timeslots timeslot
5.
exit
6.
interface CEMslot/port
7.
cem group-number
8.
xconnect ip-address encapsulation mpls
9.
exit
10. end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
controller {e1 | t1} slot/port
Enters configuration mode for an E1 or T1 controller.
Example:
Router(config)# controller [e1 |
t1] 0/0
Step 4
cem-group 5 timeslots timeslot
Example:
Router(config-controller)#
cem-group 5 timeslots 1-24
Step 5
exit
Assigns channels on the T1 or E1 circuit to the circuit emulation (CEM)
channel and specific timeslots to the CEM channel.
•
timeslot—The timeslot value for T1 interface is between 1 to 24 and
for E1 interface, its between 1 to 31.
Exits controller configuration.
Example:
Router(config-controller)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-14
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 6
Command
Purpose
interface CEMslot/port
Defines a CEM channel.
Example:
Router(config)# interface CEM0/5
Step 7
Defines a CEM channel.
cem group-number
Example:
Router(config-if-cem)# cem 5
Step 8
xconnect ip-address encapsulation
mpls
Binds an attachment circuit to the CEM interface to create a pseudowire.
This example creates a pseudowire by binding the CEM circuit 5 to the
remote peer 30.30.30.2.
Example:
Note
Router(config-if-cem)# xconnect
30.30.30.2 305 encapsulation mpls
Step 9
When creating IP routes for a pseudowire configuration, we
recommend that you build a route from the xconnect address
(LDP router-id or loopback address) to the next hop IP address,
such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
Exits the CEM interface.
exit
Example:
Router(config-if-cem-xconn)# exit
Step 10
Exits configuration mode.
end
Example:
Router(config-if-cem)# end
Configuring a CESoPSN Pseudowire with UDP Encapsulation
Complete the following steps to configure a CESoPSN pseudowire with UDP encapsulation:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
pseudowire-class pseudowire-class-name
4.
encapsulation udp
5.
ip local interface loopback interface-number
6.
ip tos value value-number
7.
ip ttl number
8.
exit
9.
controller {e1 | t1} slot/port
10. cem-group number timeslots number
11. exit
12. interface cem slot/port
13. no ip address
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-15
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
14. cem group-number
15. xconnect peer-router-id vcid {pseudowire-class name}
16. udp port local local_udp_port remote remote_udp_port
17. end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
pseudowire-class
pseudowire-class-name
Creates a new pseudowire class.
Example:
Router(config)# pseudowire-class
udpClass
Step 4
encapsulation udp
Specifies the UDP transport protocol.
Example:
Router(config-pw-class)#
encapsulation udp
Step 5
ip local interface loopback
interface-number
Configures the IP address of the provider edge (PE) router interface as the
source IP address for sending tunneled packets.
Example:
Router(config-pw-class)# ip local
interface loopback1
Step 6
ip tos value value-number
Specifies the type of service (ToS) level for IP traffic in the pseudowire.
Example:
Router(config-pw-class)# ip tos
value 100
Step 7
ip ttl number
Specifies a value for the time-to-live (TTL) byte in the IP headers of Layer
2 tunneled packets.
Example:
Router(config-pw-class)# ip ttl 100
Step 8
exit
Exits pseudowire-class configuration mode.
Example:
Router(config-pw-class)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-16
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
Step 9
Command
Purpose
controller {e1|t1} slot/port
Enters E1/T1 controller configuration mode.
Example:
Router(config)# controller e1 0/0
Step 10
cem-group number timeslots number
Example:
Assigns channels on the T1 or E1 circuit to the CEM channel. This
example uses the unframed parameter to assign all the T1 timeslots to the
CEM channel.
Router(config-controller)#
cem-group 5 timeslots 1-24
Step 11
exit
Exits controller configuration.
Example:
Router(config-controller)# exit
Step 12
interface cem slot/port
Example:
Selects the CEM interface where the CEM circuit (group) is located
(where slot/subslot is the SPA slot and subslot and port is the SPA port
where the interface exists).
Router(config)# interface CEM 0/5
Step 13
no ip address
Disables the IP address configuration for the physical layer interface.
Example:
Router(config)# no ip address
Step 14
cem group-number
Defines a CEM channel.
Example:
Router(config-if)# cem 5
Step 15
xconnect peer-router-id vcid
{pseudowire-class name}
Binds an attachment circuit to the CEM interface to create a pseudowire.
This example creates a pseudowire by binding the CEM circuit 5 to the
remote peer 30.30.30.2.
Example:
Note
Router(config-if-cem)# xconnect
30.30.30.2 305 pw-class udpClass
Step 16
udp port local local_udp_port
remote remote_udp_port
When creating IP routes for a pseudowire configuration, we
recommend that you build a route from the cross-connect address
(LDP router-ID or loopback address) to the next hop IP address,
such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
Specifies a local and remote UDP port for the connection. Valid port
values for CESoPSN pseudowires using UDP are from 49152–57343.
Example:
Router(config-if-cem-xconn)# udp
port local 49150 remote 55000
Step 17
end
Exits the configuration mode.
Example:
Router(config-if-cem)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-17
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
QoS for CESoPSN over UDP and SAToP over UDP
Cisco ASR 901 router supports IP DSCP and IP Precedence via service-policy and Type of Service (ToS)
setting in pseudowire-class.
The ToS setting in pseudowire-class is optional. If a quality of service (QoS) policy with DSCP and IP
Precedence value is applied on the cem circuit that has a ToS setting (via pseudowire-class), then the
DSCP IP Precedence setting at the service policy is applied. Hence, the service-policy overrides the Qos
configuration that is set through the pseudowire-class.
Example
Router(config)#pseudowire-class pw-udp
Router(config-pw-class)#ip tos value tos-value
Router(config)#policy-map
Router(config-pmap)#class
Router(config-pmap-c)#set
Router(config-pmap-c)#set
Router(config-pmap-c)#set
policy-Qos
class-default
ip precedence precedence-value
ip dscp dscp-value
qos-group qos-group-value
Router(config)#interface cem 0/0
Router(config-if)#cem 0
Router(config-if-cem)#service-policy input policy-Qos
Router(config-if-cem)#xconnect 180.0.0.201 29 pw-class pw-udp
Router(cfg-if-cem-xconn)#udp port local 49152 remote 49152
The set qos-group command is used to set the mpls experimental bit for the vc label, if no action on
egress is copied to the outer mpls label experimental bit.
Note
For details on configuring QoS in Cisco ASR 901, see Configuring QoS.
Configuring Transportation of Service Using Ethernet over MPLS
Ethernet over MPLS PWs allow you to transport Ethernet traffic over an existing MPLS network. For an
overview of Ethernet over MPLS pseudowires, see Transportation of Service Using Ethernet over MPLS,
page 21-3.
Complete the following steps to configure an Ethernet over MPLS pseudowire:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface GigabitEthernetslot/port
4.
service instance instance-number ethernet
5.
encapsulation dot1q encapsulation-type
6.
rewrite ingress tag pop 1 symmetric
7.
xconnect ip-address encapsulation mpls
8.
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-18
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Pseudowire
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Specifies an interface to configure.
interface GigabitEthernetslot/port
Example:
Router(config)# interface
GigabitEthernet0/2
Step 4
Configures a service instance and enters the service instance
configuration mode.
service instance instance-number
ethernet
Example:
Router(config-if)# service instance
101 ethernet
Step 5
Configures encapsulation type for the service instance.
encapsulation dot1q
encapsulation-type
Example:
Router(config-if-srv)#
encapsulation dot1q 101
Step 6
rewrite ingress tag pop 1 symmetric
Specifies the encapsulation modification to occur on packets at ingress as
follows:
Example:
•
pop 1—Pop (remove) the outermost tag.
Router(config-if-srv)# rewrite
ingress tag pop 1 symmetric
•
symmetric—Configure the packet to undergo the reverse of the
ingress action at egress. If a tag is popped at ingress, it is pushed
(added) at egress.
Note
Step 7
xconnect ip-address encapsulation
mpls
Although the symmetric keyword appears to be optional, you
must enter it for rewrite to function correctly.
Binds the VLAN attachment circuit to an Any Transport over MPLS
(AToM) pseudowire for EoMPLS.
Example:
Router(config-if-srv)# xconnect
11.205.1.1 141 encapsulation mpls
Step 8
end
Returns to privileged EXEC mode.
Example:
Router(config-if-srv)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-19
Chapter 21
Configuring Pseudowire
Configuring L2VPN Pseudowire Redundancy
Configuring L2VPN Pseudowire Redundancy
The Cisco ASR 901 router supports the L2VPN pseudowire redundancy feature that provides backup
service for circuit emulation (CEM) pseudowires. This feature enables the network to detect a failure,
and reroute the Layer 2 (L2) service to another endpoint that can continue to provide the service. This
feature also provides the ability to recover from a failure: either the failure of the remote PE router, or
of the link between the PE and the CE routers.
Configure pseudowire redundancy by configuring two pseudowires for the CEM interface: a primary
pseudowire and a backup (standby) pseudowire. If the primary pseudowire goes down, the router uses
the backup pseudowire in its place. When the primary pseudowire comes back up, the backup
pseudowire is brought down and the router resumes using the primary.
Figure 21-2 shows an example of pseudowire redundancy.
Figure 21-2
Pseudowire Redundancy
CE1
PE2
PE1
Redundant
attachment CE2
circuits
135058
Primary
pseudowire
Backup
pseudowire
Note
You must configure the backup pseudowire to connect to a different router than the primary pseudowire.
Complete the following steps to configure pseudowire redundancy on a CEM interface.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 1
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 2
controller {e1 | t1} slot/port
Selects an E1 or T1 controller.
Example:
Router(config)# controller t1 0/1
Step 3
[number] cem-group group-number
{unframed | timeslots timeslot}
Creates a CEM interface and assigns it a CEM group number.
Example:
Router(config-controller)#
cem-group 5 timeslots 30}
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-20
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring L2VPN Pseudowire Redundancy
Step 4
Command
Purpose
framing {sf | esf}
Selects the T1 framing type.
Example:
Router(config-controller)# framing
esf
Step 5
Exits the controller configuration mode.
exit
Example:
Router(config-controller)# exit
Step 6
Configures the pseudowire interface to use for the new pseudowire class.
interface cemslot/port
Example:
Router(config)# interface cem0/0
Step 7
Configures the pseudowire interface to use for the new pseudowire class.
cem group-number
Example:
Router(config-if)# cem 0
Step 8
Configures a pseudowire to transport TDM data from the CEM circuit
across the MPLS network.
xconnect peer-router-id vcid
{encapsulation mpls | pw-class
pw-class-name}
Example:
xconnect 10.10.10.11 344
encapsulation mpls
•
peer-router-id is the IP address of the remote PE peer router.
•
vcid is a 32-bit identifier to assign to the pseudowire. The same vcid
must be used for both ends of the pseudowire.
•
encapsulation mpls sets MPLS for tunneling mode.
•
pw-class-name specifies a pseudowire class that includes the
encapsulation mpls command.
The peer-router-id and vcid combination must be unique on the
Note
router.
Step 9
Specifies a redundant peer for the pseudowire VC.
backup peer peer-router-ip-address
vcid [pw-class pw-class-name]
Example:
Router(config-if-xcon)# backup peer
The pseudowire class name must match the name specified when you
created the pseudowire class, but you can use a different pw-class in the
backup peer command than the name used in the primary xconnect
command.
10.10.10.11 344 [pw-class pwclass1]
Step 10
backup delay enable-delay
{disable-delay | never}
•
enable delay—Specifies how long (in seconds) the backup
pseudowire VC should wait to take over, after the primary pseudowire
VC goes down. The range is 0 to 180.
Example:
•
disable delay—Specifies how long the primary pseudowire should
wait, after it becomes active to take over for the backup pseudowire
VC. The range is 0 to 180 seconds. If you specify the never keyword,
the primary pseudowire VC never takes over for the backup.
Router(config-if-xcon)# backup
delay 30 60
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-21
Chapter 21
Configuring Pseudowire
Configuring Hot Standby Pseudowire Support for ATM/IMA
Example: Pseudowire Redundancy
This example shows pseudowire redundancy configured for a CEM circuit (group). In the example, the
xconnect command configures a primary pseudowire for CEM group 0. The backup peer command
creates a redundant pseudowire for the group.
int cem 0/1
no ip address
cem 0
xconnect 10.10.10.1 1 encap mpls
backup peer 10.10.10.2 200
exit
Configuring Hot Standby Pseudowire Support for ATM/IMA
This section describes how to configure ATM/IMA pseudowire redundancy:
Note
•
Configuring ATM/IMA Pseudowire Redundancy in PVC Mode
•
Configuring ATM/IMA Pseudowire Redundancy in PVP Mode
•
Configuring ATM/IMA Pseudowire Redundancy in Port Mode
•
Verifying Hot Standby Pseudowire Support for ATM/IMA
Both the primary and backup pseudowires must be provisioned for the Hot Standby Pseudowire Support
feature to work.
Configuring ATM/IMA Pseudowire Redundancy in PVC Mode
Complete the following steps to configure pseudowire redundancy in permanent virtual circuit (PVC)
mode.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface interface-name
4.
pvc vpi/vci l2transport
5.
encapsulation { aal0 | aal5 }
6.
xconnect peer-ip-address vc-id encapsulation mpls
7.
backup peer peer-router-ip-addr vcid
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-22
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Hot Standby Pseudowire Support for ATM/IMA
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Selects the interface.
interface interface-name
•
interface-name—Name of the interface
Example:
Router(config)# interface ATM0/IMA1
Step 4
Step 5
Create or assigns a name to an ATM permanent virtual circuit (PVC), to
specify the encapsulation type on an ATM PVC.
pvc vpi/vci l2transport
Example:
•
vpi—ATM network virtual path identifier (VPI) for this PVC.
Router(config-if)# pvc 90/90
l2transport
•
vci—ATM network virtual channel identifier (VCI) for this PVC.
Configures the ATM adaptation layer ( AAL) and encapsulation type for
an ATM virtual circuit (VC), VC class , VC, bundle, or permanent virtual
circuit (PVC) range.
encapsulation { aal0 | aal5 }
Example:
Router(config-if)# encapsulation
aa10
Step 6
Binds an attachment circuit to a pseudowire.
xconnect peer-ip-address vc-id
encapsulation mpls
Example:
Router(config-if-srv)# xconnect
192.168.1.12 100 encapsulation mpls
Step 7
backup peer peer-router-ip-addr
vcid
Example:
Router(config-if-xconn)# backup
peer 170.0.0.201 200
•
peer-ip-address—IP address of the remote provider edge (PE) peer.
The remote router ID can be any IP address, as long as it is reachable.
•
vcid—32-bit identifier of the VC between the routers at each end of
the layer control channel.
•
encapsulation—Specifies the tunneling method to encapsulate the
data in the pseudowire.
Specifies a redundant peer for a pseudowire virtual circuit (VC).
•
peer-router-id—IP address of the remote peer router.
•
vcid—32-bit identifier of the VC between the routers at each end of
the layer control channel.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-23
Chapter 21
Configuring Pseudowire
Configuring Hot Standby Pseudowire Support for ATM/IMA
Configuring ATM/IMA Pseudowire Redundancy in PVP Mode
Complete the following steps to configure pseudowire redundancy in permanent virtual path (PVP)
mode.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface interface-name
4.
atm pvp vpi l2transport
5.
xconnect peer-ip-address vc-id encapsulation mpls
6.
backup peer peer-router-ip-addr vcid
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface interface-name
Selects the interface.
•
interface-name—Name of the interface
Example:
Router(config)# interface ATM0/IMA1
Step 4
atm pvp vpi l2transport
Example:
Creates a permanent virtual path (PVP) used to multiplex (or bundle) one
or more virtual circuits (VCs).
•
vpi—ATM network virtual path identifier (VPI) of the VC to
multiplex on the permanent virtual path.
•
l2transport—Specifies that the PVP is for the Any Transport over
MPLS (AToM) ATM cell relay feature or the ATM Cell Relay over
L2TPv3 feature.
Router(config-if)# atm pvp 90
l2transport
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-24
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuring Hot Standby Pseudowire Support for ATM/IMA
Step 5
Command
Purpose
xconnect peer-ip-address vc-id
encapsulation mpls
Binds an attachment circuit to a pseudowire, and to configure an Any
Transport over MPLS (AToM) static pseudowire.
•
peer-ip-address—IP address of the remote provider edge (PE) peer.
The remote router ID can be any IP address, as long as it is reachable.
•
vcid—32-bit identifier of the VC between the routers at each end of
the layer control channel.
•
encapsulation—Specifies the tunneling method to encapsulate the
data in the pseudowire.
Example:
Router(config-if)# xconnect
192.168.1.12 100 encapsulation mpls
Step 6
Specifies a redundant peer for a pseudowire virtual circuit (VC).
backup peer peer-router-ip-addr
vcid
Example:
•
peer-router-id—IP address of the remote peer router.
•
vcid—32-bit identifier of the VC between the routers at each end of
the layer control channel.
Router(config-if-xconn)# backup
peer 170.0.0.201 200
Configuring ATM/IMA Pseudowire Redundancy in Port Mode
Complete the following steps to configure pseudowire redundancy in port mode.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface interface-name
4.
xconnect peer-ip-address vc-id encapsulation mpls
5.
backup peer peer-router-ip-addr vcid
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Selects the interface.
interface interface-name
•
interface-name—Name of the interface
Example:
Router(config)# interface ATM0/IMA1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-25
Chapter 21
Configuring Pseudowire
Configuring Hot Standby Pseudowire Support for ATM/IMA
Step 4
Command
Purpose
xconnect peer-ip-address vc-id
encapsulation mpls
Binds an attachment circuit to a pseudowire, and to configure an Any
Transport over MPLS (AToM) static pseudowire.
•
peer-ip-address—IP address of the remote provider edge (PE) peer.
The remote router ID can be any IP address, as long as it is reachable.
•
vcid—32-bit identifier of the VC between the routers at each end of
the layer control channel.
•
encapsulation—Specifies the tunneling method to encapsulate the
data in the pseudowire.
Example:
Router(config-if)# xconnect
192.168.1.12 100 encapsulation mpls
Step 5
backup peer peer-router-ip-addr
vcid
Example:
Router(config-if-xconn)# backup
peer 170.0.0.201 200
Specifies a redundant peer for a pseudowire virtual circuit (VC).
•
peer-router-ip-addr—IP address of the remote peer router.
•
vcid—32-bit identifier of the VC between the routers at each end of
the layer control channel.
Verifying Hot Standby Pseudowire Support for ATM/IMA
To verify the configuration of Hot Standby Pseudowire Support for ATM/IMA, use the show commands
as shown in the following examples.
Router# show mpls l2transport vc 90
Local intf
------------AT0/IMA1
AT0/IMA1
Local circuit
-------------------------ATM VPC CELL 90
ATM VPC CELL 90
Dest address
--------------2.2.2.2
180.0.0.201
VC ID
---------90
90
Status
---------STANDBY
UP
Router# show mpls l2transport vc detail
ASR901-PE2#sh mpls l2 vc 90 deta
Local interface: AT0/IMA1 up, line protocol up, ATM VPC CELL 90 up
Destination address: 2.2.2.2, VC ID: 90, VC status: standby
Output interface: Vl500, imposed label stack {22 17}
Preferred path: not configured
Default path: active
Next hop: 150.1.1.201
Create time: 5d02h, last status change time: 2d17h
Last label FSM state change time: 5d02h
Signaling protocol: LDP, peer 2.2.2.2:0 up
Targeted Hello: 170.0.0.201(LDP Id) -> 2.2.2.2, LDP is UP
Graceful restart: not configured and not enabled
Non stop routing: not configured and not enabled
Status TLV support (local/remote)
: enabled/supported
LDP route watch
: enabled
Label/status state machine
: established, LrdRru
Last local dataplane
status rcvd: No fault
Last BFD dataplane
status rcvd: Not sent
Last BFD peer monitor status rcvd: No fault
Last local AC circuit status rcvd: DOWN(standby)
Last local AC circuit status sent: No fault
Last local PW i/f circ status rcvd: No fault
Last local LDP TLV
status sent: DOWN(standby)
Last remote LDP TLV
status rcvd: No fault
Last remote LDP ADJ
status rcvd: No fault
MPLS VC labels: local 17, remote 17
Group ID: local 0, remote 0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-26
OL-23826-09
Chapter 21
Configuring Pseudowire
TDM Local Switching
MTU: local n/a, remote n/a
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
Dataplane:
SSM segment/switch IDs: 28683/16387 (used), PWID: 4
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals:
receive 0, send 0
transit packet drops: receive 0, seq error 0, send 0
Local interface: AT0/IMA1 up, line protocol up, ATM VPC CELL 90 up
Destination address: 180.0.0.201, VC ID: 90, VC status: up
Output interface: Vl300, imposed label stack {21}
Preferred path: not configured
Default path: active
Next hop: 110.1.1.202
Create time: 5d02h, last status change time: 2d17h
Last label FSM state change time: 2d17h
Signaling protocol: LDP, peer 180.0.0.201:0 up
Targeted Hello: 170.0.0.201(LDP Id) -> 180.0.0.201, LDP is UP
Graceful restart: not configured and not enabled
Non stop routing: not configured and not enabled
Status TLV support (local/remote)
: enabled/supported
LDP route watch
: enabled
Label/status state machine
: established, LruRru
Last local dataplane
status rcvd: No fault
Last BFD dataplane
status rcvd: Not sent
Last BFD peer monitor status rcvd: No fault
Last local AC circuit status rcvd: No fault
Last local AC circuit status sent: No fault
Last local PW i/f circ status rcvd: No fault
Last local LDP TLV
status sent: No fault
Last remote LDP TLV
status rcvd: No fault
Last remote LDP ADJ
status rcvd: No fault
MPLS VC labels: local 16, remote 21
Group ID: local 0, remote 0
MTU: local n/a, remote n/a
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
Dataplane:
SSM segment/switch IDs: 4110/12290 (used), PWID: 3
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals:
receive 0, send 0
transit packet drops: receive 0, seq error 0, send 0
packet drops:
receive 0, send 0
TDM Local Switching
Time Division Multiplexing (TDM) Local Switching allows switching of layer 2 data between two CEM
interfaces on the same router.
Note
Effective with 15.2(2)SNH1 release, you can configure local switching on the T1 or E1 mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-27
Chapter 21
Configuring Pseudowire
TDM Local Switching
Restrictions
•
Auto-provisioning is not supported.
•
Out-of-band signaling is not supported.
•
Redundancy is not supported.
•
Interworking with other interface types other than CEM is not supported.
•
The same CEM circuit cannot be used for both local switching and cross-connect.
•
You cannot use CEM local switching between two CEM circuits on the same CEM interface.
•
Local switching is not supported in unframed mode.
•
Local switching with channelized CEM interface is not supported.
•
Modifications to payload size, dejitter buffer, idle pattern, and service policy CEM interface
parameters are not supported.
Configuring TDM Local Switching on a T1/E1 Mode
To configure local switching on a T1 or E1 mode, complete the following steps:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface cemslot/port
4.
connect name cemslot/port interface-name cemslot/port interface-name
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-28
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuration Example for Local Switching
Step 3
Command
Purpose
interface cemslot/port
Selects the CEM interface to configure the pseudowire.
Example:
Router(config)# interface cem0/3
Step 4
connect connection-name
cemslot/port interface-name
cemslot/port interface-name
Configures a local switching connection between the first and the second
CEM interfaces. The no form of this command unconfigures the
connection.
Example:
Router(config)# connect myconn
CEM0/0 0 CEM0/1 0
Verifying Local Switching
To verify local switching on a T1/E1 mode, use the show connection, show connection all, show
connection id or show connection name command.
Router# show connection
ID
Name
Segment 1
Segment 2
State
==========================================================================
1
myconn
CE0/0 CESP 0
CE0/1 CESP 0
Router# show connection all
ID
Name
Segment 1
Segment 2
UP
State
==========================================================================
1
2
myconn
myconn1
CE0/0 CESP 0
CE0/1 CESP 1
CE0/1 CESP 0
CE0/0 CESP 1
UP
UP
Router# show connection name myconn
Connection: 1 - myconn
Current State: UP
Segment 1: CEM0/0 CESoPSN Basic 0 up
Segment 2: CEM0/1 CESoPSN Basic 0 up
Router# show connection id 1
Connection: 1 - myconn
Current State: UP
Segment 1: CEM0/0 CESoPSN Basic 0 up
Segment 2: CEM0/1 CESoPSN Basic 0 up
Configuration Example for Local Switching
The following is a sample configuration of local switching:
!
controller T1 0/0
cem-group 0 timeslots 1-24
!
controller T1 0/1
cem-group 0 timeslots 1-24
!
!
interface CEM0/0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-29
Chapter 21
Configuring Pseudowire
Configuration Examples of Hot Standby Pseudowire Support for ATM/IMA
no ip address
cem 0
!
!
interface CEM0/1
no ip address
cem 0
!
!
connect myconn CEM0/0 0 CEM0/1 0
!
Configuration Examples of Hot Standby Pseudowire Support for
ATM/IMA
This section provides sample configuration examples of Hot Standby Pseudowire Support for ATM/IMA
on the Cisco ASR 901 router:
•
Example: Configuring ATM/IMA Pseudowire Redundancy in PVC Mode
•
Example: Configuring ATM/IMA Pseudowire Redundancy in PVP Mode
•
Example: Configuring ATM/IMA Pseudowire Redundancy in Port Mode
Example: Configuring ATM/IMA Pseudowire Redundancy in PVC Mode
The following is a sample configuration of ATM/IMA pseudowire redundancy in PVC mode.
!
interface ATM0/IMA1
pvc 90/90 l2transport
encapsulation aal0
xconnect 192.168.1.12 100 encapsulation mpls
backup peer 170.0.0.201 200
!
Example: Configuring ATM/IMA Pseudowire Redundancy in PVP Mode
The following is a sample configuration of ATM/IMA pseudowire redundancy in PVP mode.
!
interface ATM0/IMA1
atm pvp 90 l2transport
xconnect 192.168.1.12 100 encapsulation mpls
backup peer 170.0.0.201 200
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-30
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuration Examples for Pseudowire
Example: Configuring ATM/IMA Pseudowire Redundancy in Port Mode
The following is a sample configuration of ATM/IMA pseudowire redundancy in port mode.
!
interface ATM0/IMA1
xconnect 192.168.1.12 100 encapsulation mpls
backup peer 170.0.0.201 200
!
Configuration Examples for Pseudowire
This section contains the following examples:
•
Example: TDM over MPLS Configuration-Example, page 21-31
•
Example: CESoPSN with UDP, page 21-34
•
Example: Ethernet over MPLS, page 21-35
Example: TDM over MPLS Configuration-Example
Figure 21-3 shows a TDM over MPLS configuration. The configuration uses CESoPSN for E1.
TDM over MPLS Configuration
30.30.30.2
30.30.30.1
BSC
CEM 0/0 (clock )
CEM 0/1
CEM 0/4
CEM 0/5
ASR_A
CEM 0/0
CEM 0/1
CEM 0/4
CEM 0/5
GigabitEthernet 0/1 GigabitEthernet 0/1
50.50.50.2
50.50.50.1
E1-1/0
E1-1/0
ASR_B
300157
Figure 21-3
BTS
ASR_A
!
version 12.4
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
no service password-encryption
!
hostname asr_A
!
boot-start-marker
boot-end-marker
!
card type e1 0 0
enable password xxx
!
no aaa new-model
clock timezone est -5
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-31
Chapter 21
Configuring Pseudowire
Configuration Examples for Pseudowire
ip cef
!
controller E1 0/0
clock source internal
cem-group 0 timeslots 1-31
description E1 CESoPSN example
!
controller E1 0/1
clock source internal
cem-group 1 unframed
description E1 SATOP example
!
controller E1 0/4
clock source internal
cem-group 4 unframed
description E1 SATOP example
!
controller E1 0/5
clock source internal
cem-group 5 timeslots 1-24
description E1 CESoPSN example
!
interface Loopback0
ip address 30.30.30.1 255.255.255.255
!
interface GigabitEthernet0/1
no negotiation auto
service instance 2 ethernet
encapsulation untagged
bridge-domain 100
!
!
interface CEM0/0
no ip address
cem 0
xconnect 30.30.30.2 300 encapsulation
!
!
interface CEM0/1
no ip address
cem 1
xconnect 30.30.30.2 301 encapsulation
!
!
interface CEM0/4
no ip address
cem 4
xconnect 30.30.30.2 304 encapsulation
!
!
interface CEM0/5
no ip address
cem 5
xconnect 30.30.30.2 305 encapsulation
!
!
interface Vlan100
ip address 50.50.50.1 255.255.255.0
mpls ip
!
router ospf 1
network 50.50.50.0 0.0.0.255 area 0
network 30.30.30.1 0.0.0.0 area 0
!
mpls
mpls
mpls
mpls
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-32
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuration Examples for Pseudowire
no ip http server
no ip http secure-server
!
line con 0
password xxx
login
line aux 0
password xxx
login
no exec
line vty 0 4
password xxx
login
!
network-clock input-source 1 external 0/0/0
end
e1 crc4
ASR_B
!
version 12.4
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
no service password-encryption
!
hostname asr_B
!
boot-start-marker
boot-end-marker
!
card type e1 0 0
enable password xxx
!
no aaa new-model
clock timezone est -5
!
ip cef
!
controller E1 0/0
clock source internal
cem-group 0 timeslots 1-31
description E1 CESoPSN example
!
controller E1 0/1
clock source internal
cem-group 1 unframed
description E1 SATOP example
!
controller E1 0/4
clock source internal
cem-group 4 unframed
description T1 SATOP example
!
controller E1 0/5
clock source internal
cem-group 5 timeslots 1-24
description T1 CESoPSN example
!
interface Loopback0
ip address 30.30.30.2 255.255.255.255
!
interface GigabitEthernet0/1
no negotiation auto
service instance 2 ethernet
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-33
Chapter 21
Configuring Pseudowire
Configuration Examples for Pseudowire
encapsulation untagged
bridge-domain 100
!
!
interface CEM0/0
no ip address
cem 0
xconnect 30.30.30.1 300 encapsulation mpls
!
!
interface CEM0/1
no ip address
cem 1
xconnect 30.30.30.1 301 encapsulation mpls
!
!
interface CEM0/4
no ip address
cem 4
xconnect 30.30.30.1 304 encapsulation mpls
!
!
interface CEM0/5
no ip address
cem 5
xconnect 30.30.30.1 305 encapsulation mpls
!
!
interface Vlan100
ip address 50.50.50.2 255.255.255.0
mpls ip
!
router ospf 1
network 50.50.50.0 0.0.0.255 area 0
network 30.30.30.2 0.0.0.0 area 0
!
no ip http server
no ip http secure-server
!
line con 0
password xxx
login
line aux 0
password xxx
login
no exec
line vty 0 4
password xxx
login
!
network-clock input-source 1 controller e1 0/0
end
Example: CESoPSN with UDP
The following configuration uses CESoSPN with UDP encapsulation.
Note
This section provides a partial configuration intended to demonstrate a specific feature.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-34
OL-23826-09
Chapter 21
Configuring Pseudowire
Configuration Examples for Pseudowire
interface Loopback0
ip address 2.2.2.8 255.255.255.255
!
pseudowire-class udpClass
encapsulation udp
protocol none
ip local interface Loopback 0
!
controller E1 0/13
clock source internal
cem-group 0 timeslots 1-31
!
interface cem 0/13
cem 0
xconnect 2.2.2.9 200 pw-class udpClass
udp port local 50000 remote 55000
Example: Ethernet over MPLS
The following configuration example shows an Ethernet pseudowire (aka EoMPLS) configuration.
interface Loopback0
description for_mpls_ldp
ip address 99.99.99.99 255.255.255.255
!
interface GigabitEthernet0/10
description Core_facing
no negotiation auto
service instance 150 ethernet
encapsulation dot1q 150
rewrite ingress tag pop 1 symmetric
bridge-domain 150
!
interface GigabitEthernet0/11
description Core_facing
service instance 501 ethernet
encapsulation dot1q 501
rewrite ingress tag pop 1 symmetric
xconnect 111.0.1.1 501 encapsulation mpls
!
interface FastEthernet0/0
ip address 10.104.99.74 255.255.255.0
full-duplex
!
interface Vlan1
!
interface Vlan150
ip address 150.0.0.1 255.255.255.0
mpls ip
!
router ospf 7
network 99.99.99.99 0.0.0.0 area 0
network 150.0.0.0 0.0.0.255 area 0
!
no ip http server
ip route 10.0.0.0 255.0.0.0 10.104.99.1
!
logging esm config
!
mpls ldp router-id Loopback0 force
!
!end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-35
Chapter 21
Configuring Pseudowire
Additional References
Additional References
The following sections provide references related to inverse multiplexing over ATM.
Related Documents
Related Topic
Document Title
Cisco IOS Commands
Cisco IOS Master Commands List, All Releases
ASR 901 Command Reference
Cisco ASR 901 Series Aggregation Services Router Command
Reference
Cisco IOS Interface and Hardware Component
Commands
Cisco IOS Interface and Hardware Component Command Reference
Standards
Standard
Title
None
—
MIBs
MIB
MIBs Link
IMA-MIB
To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
None
—
Technical Assistance
Description
Link
http://www.cisco.com/techsupport
The Cisco Technical Support website contains
thousands of pages of searchable technical content,
including links to products, technologies, solutions,
technical tips, and tools. Registered Cisco.com users
can log in from this page to access even more content.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-36
OL-23826-09
Chapter 21
Configuring Pseudowire
Feature Information for Configuring Pseudowire
Feature Information for Configuring Pseudowire
Table 21-1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 21-1
Table 21-1 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for Configuring Pseudowire
Feature Name
Releases
Feature Information
Configuring Pseudowire
15.2(2)SNH1
See the following links for more information about this
feature:
•
Hot Standby Pseudowire Support for
ATM/IMA
15.3(2)S
TDM Local Switching
See the following links for more information about this
feature:
•
Hot Standby Pseudowire Support for ATM/IMA
•
Configuring Hot Standby Pseudowire Support for
ATM/IMA
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
21-37
Chapter 21
Configuring Pseudowire
Feature Information for Configuring Pseudowire
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
21-38
OL-23826-09
CH A P T E R
22
Configuring Clocking
This chapter provides information about configuring clocking on the Cisco ASR 901 Series Aggregation
Services Router.
Contents
•
Restrictions, page 22-1
•
Configuring Network Clock for Cisco ASR 901 Router, page 22-2
•
Configuring PTP for the Cisco ASR 901 Router, page 22-18
Restrictions
•
External interfaces like Building Integrated Timing Supply (BITS) and 1 Pulse Per Second (1PPS)
have only one port. These interfaces can be used as either an input interface or output interface at a
given time.
•
The line to external option is not supported for external Synchronization Supply Unit (SSU).
•
Time-of-Day (ToD) is not integrated to the router system time. ToD input or output reflects only the
PTP time, not the router system time.
•
Revertive and non-revertive modes work correctly only with two clock sources.
•
BITS cable length option is supported via platform timing bits line-build-out command.
•
There is no automatic recovery from out-of-resource (OOR) alarms. OOR alarms must be manually
cleared using clear platform timing oor-alarms command.
•
If copper Gigabit Ethernet port is selected as the input clock source, the link must be configured as
a IEEE 802.3 link-slave, using synce state slave command.
•
BITS reports loss of signal (LOS) only for Alarm Indication Signal (AIS), LOS, and loss of frame
(LOF) alarms.
•
The clock source line command does not support loop timing in T1/E1 controllers. However, the
clock can be recovered from T1/E1 lines and used to synchronize the system clock using the
network-clock input-source priority controller E1/T1 0/x command.
•
Adaptive clocking is not supported in Cisco ASR 901 router.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-1
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Configuring Network Clock for Cisco ASR 901 Router
Cisco ASR 901 router supports time, phase and frequency awareness through ethernet networks; it also
enables clock selection and translation between the various clock frequencies.
If Cisco ASR 901 interoperates with devices that do not support synchronization, synchronization
features can be disabled or partially enabled to maintain backward compatibility.
The network clock can be configured in global configuration mode and interface configuration mode:
•
Configuring Network Clock in Global Configuration Mode, page 22-3
•
Configuring Network Clock in Interface Configuration Mode, page 22-6
•
Understanding SSM and ESMC, page 22-7
•
Configuring ESMC in Global Configuration Mode, page 22-8
•
Configuring ESMC in Interface Configuration Mode, page 22-9
•
Managing Synchronization, page 22-11
•
Configuring Synchronous Ethernet for Copper Ports, page 22-13
•
Verifying the Synchronous Ethernet configuration, page 22-13
•
Troubleshooting Tips, page 22-16
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-2
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Configuring Network Clock in Global Configuration Mode
Complete the following steps to configure the network clock in global configuration mode:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
network-clock synchronization automatic
4.
network-clock eec {1 | 2}
5.
network-clock synchronization ssm option {1 | 2 {GEN1 | GEN2}}
6.
network-clock hold-off {0 | 50-10000} global
7.
network-clock external slot/card/port hold-off {0 | 50-10000}
8.
network-clock wait-to-restore 0-86400 global
9.
network-clock input-source priority {interface interface-name slot/port | top slot/port | {external
slot/card/port [t1 {sf | efs | d4} | e1 [crc4| fas| cas [crc4] | 2048k | 10m]}}
10. network-clock input-source priority controller [t1/e1] slot/port
11. network-clock revertive
12. network-clock output-source system priority {external slot/card/port [t1 {sf | efs | d4} | e1 [crc4|
fas| cas [crc4] | 2048k | 10m]}
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
network-clock synchronization
automatic
Enables G.781-based automatic clock selection process.
G.781 is the ITU-T Recommendation that specifies the
synchronization layer functions.
Example:
Router(config)# network-clock
synchronization automatic
Step 4
network-clock eec {1 | 2}
Example:
Router(config)# network-clock eec 1
Configures the clocking system hardware with the desired
parameters. These are the options:
•
For option 1, the default value is EEC-Option 1 (2048).
•
For option 2, the default value is EEC-Option 2 (1544).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-3
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Step 5
Command or Action
Purpose
network-clock synchronization ssm
option {1 | 2 {GEN1 | GEN2}}
Configures the router to work in a synchronized network
mode as described in G.781. The following are the options:
•
Option 1: refers to synchronization networks designed
for Europe (E1 framings are compatible with this
option).
•
Option 2: refers to synchronization networks designed
for the US (T1 framings are compatible with this
option).
The default option is 1 and while choosing option 2,
you need to specify the second generation message
(GEN2) or first generation message (GEN1).
Example:
Router(config)# network-clock
synchronization ssm option 2 GEN1
Note
Step 6
network-clock hold-off
50-10000} global
{0 |
Network-clock configurations that are not common
between options need to be configured again.
Configures general hold-off timer in milliseconds. The
default value is 300 milliseconds.
Note
Example:
Displays a warning message for values below 300
ms and above 1800 ms.
Router(config)# network-clock
hold-off 75 global
Step 7
network-clock external
slot/card/port hold-off
50-10000}
Overrides hold-off timer value for external interface.
{0 |
Note
Example:
Displays a warning message for values above 1800
ms, as waiting longer causes the clock to go into the
holdover mode.
Router(config)# network-clock
external 3/1/1 hold-off 300
Step 8
network-clock wait-to-restore
0-86400 global
Sets the value for the wait-to-restore timer globally.
The wait to restore time is configurable in the range of 0 to
86400 seconds. The default value is 300 seconds.
Example:
Router(config)# network-clock
external wait-to-restore 1000 global Caution
Ensure that you set the wait-to-restore values
above 50 seconds to avoid a timing flap.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-4
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Step 9
Command or Action
Purpose
network-clock input-source priority
{interface interface-name slot/port
| top slot/port | {external
slot/card/port [t1 { sf | efs | d4}
| e1 [crc4| fas| cas [crc4] | 2048k
| 10m]}}
Configures a clock source line interface, an external timing
input interface, GPS interface, or a packet-based timing
recovered clock as the input clock for the system and
defines its priority. Priority is a number between 1 and 250.
Example:
This command also configures the type of signal for an
external timing input interface. These signals are:
•
T1 with Standard Frame format or Extended Standard
Frame format.
•
E1 with or without CRC4
•
2 MHz signal
•
Default for Europe or Option I is e1 crc4 if the signal
type is not specified.
•
Default for North America or Option II is t1 esf if
signal type is not specified.
Router(config)# network-clock
input-source 1 interface top 0/12
Example for GPS interface
Router(config)# network-clock
input-source 1 external 0/0/0 10m
Note
Step 10
network-clock input-source priority
controller [t1/e1 ] slot/port
The no version of the command reverses the
command configuration, implying that the priority
has changed to undefined and the state machine is
informed.
Adds the clock recovered from the serial interfaces as one
of the nominated sources, for network-clock selection.
Example:
Router(config)# network-clock
input-source 10 controller e1 0/12
Step 11
network-clock revertive
Example:
Step 12
Specifies whether or not the clock source is revertive.
Clock sources with the same priority are always
non-revertive. The default value is non-revertive.
Router(config)# network-clock
revertive
In non-revertive switching, a switch to an alternate
reference is maintained even after the original reference
recovers from the failure that caused the switch. In
revertive switching, the clock switches back to the original
reference after that reference recovers from the failure,
independent of the condition of the alternate reference.
network-clock output-source system
priority {external slot/card/port
[t1 {sf | efs | d4 } | e1 [crc4 | fas|
cas [crc4] | 2048k | 10m]}
Allows transmitting the system clock to external timing
output interfaces.
Example:
Router(config)#network-clock
output-source system 55 external
0/0/0 t1 efs
This command provides station clock output as per G.781.
We recommend that you use the interface level command
instead of global commands. Global command should
preferably be used for interfaces that do not have an
interface sub mode. For more information on configuring
network clock in interface level mode, see Configuring
Network Clock in Interface Configuration Mode,
page 22-6.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-5
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Configuring Network Clock in Interface Configuration Mode
Complete the following steps to configure the network clock in interface configuration mode:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface
4.
synchronous mode
5.
network-clock hold-off {0 | 50-10000}
6.
network-clock wait-to-restore 0-86400
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface
Enters interface configuration mode.
Example:
Router(config)# interface
Step 4
synchronous mode
Configures the ethernet interface to synchronous mode.
Note
Example:
Router(config-if)# synchronous mode
Step 5
network-clock hold-off {0 |
50-10000}
This command is applicable to Synchronous
Ethernet capable interfaces. The default value is
asynchronous mode.
Configures hold-off timer for interface. The default value
is 300 milliseconds.
Note
Example:
Displays a warning for values below 300 ms and
above 1800 ms.
Router(config-if)#network-clock
hold-off 1000
Step 6
network-clock wait-to-restore
0-86400
Example:
Router(config-if)#network-clock
wait-to-restore 1000
Configures the wait-to-restore timer on the SyncE
interface.
Caution
Ensure that you set the wait-to-restore values
above 50 seconds to avoid timing flap.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-6
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Understanding SSM and ESMC
Network Clocking uses these mechanisms to exchange the quality level of the clock between the network
elements:
•
Synchronization Status Message, page 22-7
•
Ethernet Synchronization Messaging Channel, page 22-7
Synchronization Status Message
Network elements use Synchronization Status Messages (SSM) to inform the neighboring elements
about the Quality Level (QL) of the clock. The non-ethernet interfaces such as optical interfaces and
SONET/T1/E1 SPA framers use SSM. The key benefits of the SSM functionality are:
•
Prevents timing loops.
•
Provides fast recovery when a part of the network fails.
•
Ensures that a node derives timing from the most reliable clock source.
Ethernet Synchronization Messaging Channel
In order to maintain a logical communication channel in synchronous network connections, ethernet
relies on a channel called Ethernet Synchronization Messaging Channel (ESMC) based on IEEE 802.3
Organization Specific Slow Protocol standards. ESMC relays the SSM code that represents the quality
level of the Ethernet Equipment Clock (EEC) in a physical layer.
The ESMC packets are received only for those ports configured as clock sources and transmitted on all
the SyncE interfaces in the system. The received packets are processed by the clock selection algorithm
and are used to select the best clock. The Tx frame is generated based on the QL value of the selected
clock source and sent to all the enabled SyncE ports.
Clock Selection Algorithm
Clock selection algorithm selects the best available synchronization source from the nominated sources.
The clock selection algorithm has a non-revertive behavior among clock sources with same QL value
and always selects the signal with the best QL value. For clock option 1, the default is revertive and for
clock option 2, the default is non-revertive.
The clock selection process works in the QL enabled and QL disabled modes. When multiple selection
processes are present in a network element, all processes work in the same mode.
QL-enabled mode
In the QL-enabled mode, the following parameters contribute to the selection process:
•
Quality level
•
Signal fail via QL-FAILED
•
Priority
•
External commands.
If no external commands are active, the algorithm selects the reference (for clock selection) with the
highest quality level that does not experience a signal fail condition.
If multiple inputs have the same highest quality level, the input with the highest priority is selected.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-7
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
For multiple inputs having the same highest priority and quality level, the existing reference is
maintained (if it belongs to this group), otherwise an arbitrary reference from this group is selected.
QL-disabled mode
In the QL-disabled mode, the following parameters contribute to the selection process:
•
Signal failure
•
Priority
•
External commands
If no external commands are active, the algorithm selects the reference (for clock selection) with the
highest priority that does not experience a signal fail condition.
For multiple inputs having the same highest priority, the existing reference is maintained (if it belongs
to this group), otherwise an arbitrary reference from this group is selected.
ESMC behavior for Port Channels
ESMC is an Organization Specific Slow Protocol (OSSP) like LACP of port channel, sharing the same
slow protocol type, indicating it is in the same sub-layer as LACP. Hence, ESMC works on the link layer
on individual physical interfaces without any knowledge of the port channel. This is achieved by setting
the egress VLAN as the default VLAN (VLAN 1) and the interface as a physical interface while sending
out the packets from the CPU. So none of the service instance, port channel, or VLAN rules apply to the
packet passing through the switch ASIC.
ESMC behavior for STP Blocked Ports
ESMC works just above the MAC layer (below spanning tree protocol), and ignores spanning tree Port
status. So, ESMC is exchanged even when the port is in the blocked state (but not disabled state). This
is achieved by setting the egress VLAN as the default VLAN (VLAN 1) and the interface as a physical
interface while sending out packets from the CPU. So none of the service instance, port channel, or
VLAN port state, or rules apply to the packet passing through the switch ASIC.
Configuring ESMC in Global Configuration Mode
Complete the following steps to configure ESMC in global configuration mode:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
network-clock synchronization mode ql-enabled
4.
esmc process
5.
network-clock quality-level {tx | rx} value {interface interface-name slot/sub-slot/port | external
slot/sub-slot/port | gps slot/sub-slot | controller slot/sub-slot/port}
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-8
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
network-clock synchronization mode
ql-enabled
Example:
Router(config)# network-clock
synchronization mode ql-enabled
Step 4
Configures the automatic selection process QL-enabled
mode.
•
QL is disabled by default.
•
ql-enabled mode can be used only when the
synchronization interface is capable to send SSM.
Enables the ESMC process.
esmc process
Note
Example:
ESMC can be enabled globally or at the sync-E
interface level
Router(config)# esmc process
Step 5
network-clock quality-level {tx |
rx} value {interface interface-name
slot/sub-slot/port | external
slot/sub-slot/port | gps
slot/sub-slot | controller
slot/sub-slot/port}
Forces the QL value for line or external timing output.
Example:
Router(config)# network-clock
quality-level rx qL-pRC external
0/0/0 e1 crc4
Configuring ESMC in Interface Configuration Mode
Complete the following steps to configure ESMC in interface configuration mode:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface
4.
esmc mode {tx | rx}
5.
network-clock source quality-level value {tx | rx}
6.
esmc mode ql-disabled
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-9
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface
Enters interface configuration mode.
Example:
Router(config)# interface
Step 4
esmc mode {tx | rx}
Enables the ESMC process at the interface level. The no
form of the command disables the ESMC process.
Example:
Router(config-if)# esmc mode tx
Step 5
network-clock source quality-level
value {tx | rx}
Configures the QL value for ESMC on a gigabitethernet
port. The value is based on global interworking options:
•
If Option 1 is configured, the available values are
QL-PRC, QL-SSU-A, QL-SSU-B, QL-SEC, and
QL-DNU.
•
If Option 2 is configured with GEN 2, the available
values are QL-PRS, QL-STU, QL-ST2, QL-TNC,
QL-ST3, QL-SMC, QL-ST4, and QL-DUS.
•
If Option 2 is configured with GEN1, the available
values are QL-PRS, QL-STU, QL-ST2, QL-SMC,
QL-ST4, and QL-DUS
Example:
Router(config-if)# network-clock
source quality-level <value> tx
Step 6
esmc mode ql-disabled
Enables the QL-disabled mode.
Example:
Router(config-if)# esmc mode
ql-disabled
Note
By disabling Rx on an interface, any ESMC packet received on the interface shall be discarded. By
disabling Tx on an interface, ESMC packets will not be sent on the interface; any pending Switching
Message Delay timers (TSM) are also stopped.
Verifying ESMC Configuration
Use the following commands to verify ESMC configuration:
•
show esmc
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-10
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
•
show network-clock synchronization
Router#show esmc interface gigabitEthernet ?
<0-1> GigabitEthernet interface number
Router#show esmc interface gigabitEthernet 0/10
Interface: GigabitEthernet0/10
Administative configurations:
Mode: Synchronous
ESMC TX: Enable
ESMC RX: Enable
QL TX: QL RX: Operational status:
Port status: UP
QL Receive: QL-SEC
QL Transmit: QL-DNU
QL rx overrided: ESMC Information rate: 1 packet/second
ESMC Expiry: 5 second
Router# show network-clocks synchronization
Symbols:
En - Enable, Dis - Disable, Adis - Admin Disable
NA - Not Applicable
* - Synchronization source selected
# - Synchronization source force selected
& - Synchronization source manually switched
Automatic selection process : Enable
Equipment Clock : 2048 (EEC-Option1)
Clock Mode : QL-Disable
ESMC : Disabled
SSM Option : 1
T0 : GigabitEthernet0/4
Hold-off (global) : 300 ms
Wait-to-restore (global) : 300 sec
Tsm Delay : 180 ms
Revertive : No
Nominated Interfaces
Interface
Internal
To0/12
External 0/0/0
Gi0/1
*Gi0/4
SigType
NA
NA
10M
NA
NA
Mode/QL
NA/Dis
NA/En
NA/Dis
Sync/En
Sync/En
SigType
E1 CRC4
Input
Internal
Prio
251
1
2
20
21
QL_IN ESMC Tx
QL-SEC
NA
QL-FAILED NA
QL-FAILED NA
QL-FAILED QL-DNU
-
ESMC Rx
NA
NA
NA
-
T4 Out
External Interface
External 0/0/0
Prio
1
Squelch
FALSE
AIS
FALSE
Managing Synchronization
You can manage the synchronization using the following management commands:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-11
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Command
Purpose
network-clock switch force {interface
interface_name slot /port | external
slot/card/ port}
Forcefully selects a synchronization source irrespective
of whether the source is available and is within the
range.
Example:
Router(config)# network-clock switch
force interface GigabitEthernet 0/1 t1
network-clock switch manual {interface
interface_name slot /port | external
slot/card/ port}
Manually selects a synchronization source, provided the
source is available and is within the range.
Example:
Router(config)# network-clock switch
manual interface GigabitEthernet 0/1 t1
network-clock clear switch {t0 |
external slot/card/port [10m | 2m ]}
Clears the forced switch and manual switch commands.
Example:
Router(config)# network-clock clear
switch t0
Synchronization Example
Example 22-1 Configuration for QL-disabled mode clock selection
network-clock synchronization automatic
network-clock input-source 1 interface ToP0/12
network-clock input-source 2 External 0/0/0 10m
network-clock input-source 20 interface GigabitEthernet0/1
network-clock input-source 21 interface GigabitEthernet0/4
network-clock output-source system 1 External 0/0/0 e1 crc4
!
interface GigabitEthernet0/1
synchronous mode
synce state slave
!
interface GigabitEthernet0/4
negotiation auto
synchronous mode
synce state slave
end
Example 22-2 GPS Configuration
10MHz signal
network-clock input-source 1 External 0/0/0 10m
2M signal
network-clock input-source 1 External 0/0/0 2048K
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-12
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Configuring Synchronous Ethernet for Copper Ports
You can configure synchronization on the copper ports using the following commands:
:
Command
Purpose
Router(config-if)# synce state slave
Configures synchronous ethernet copper port as slave.
Router(config-if)# synce state master
Configures synchronous ethernet copper port as master.
Verifying the Synchronous Ethernet configuration
Use the show network-clock synchronization command to display the sample output.
Router# show network-clocks synchronization
Symbols:
En - Enable, Dis - Disable, Adis - Admin Disable
NA - Not Applicable
* - Synchronization source selected
# - Synchronization source force selected
& - Synchronization source manually switched
Automatic selection process : Enable
Equipment Clock : 2048 (EEC-Option1)
Clock Mode : QL-Disable
ESMC : Disabled
SSM Option : 1
T0 : GigabitEthernet0/4
Hold-off (global) : 300 ms
Wait-to-restore (global) : 300 sec
Tsm Delay : 180 ms
Revertive : No
Nominated Interfaces
Interface
Internal
To0/12
External 0/0/0
Gi0/1
*Gi0/4
SigType
NA
NA
10M
NA
NA
Mode/QL
NA/Dis
NA/En
NA/Dis
Sync/En
Sync/En
SigType
E1 CRC4
Input
Internal
Prio
251
1
2
20
21
QL_IN ESMC Tx
QL-SEC
NA
QL-FAILED NA
QL-FAILED NA
QL-FAILED QL-DNU
-
ESMC Rx
NA
NA
NA
-
T4 Out
External Interface
External 0/0/0
Prio
1
Squelch
FALSE
AIS
FALSE
Use the show network-clock synchronization detail command to display all details of network-clock
synchronization parameters at the global and interface levels.
Router# show network-clocks synchronization detail
Symbols:
En - Enable, Dis - Disable, Adis - Admin Disable
NA - Not Applicable
* - Synchronization source selected
# - Synchronization source force selected
& - Synchronization source manually switched
Automatic selection process : Enable
Equipment Clock : 2048 (EEC-Option1)
Clock Mode : QL-Disable
ESMC : Disabled
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-13
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
SSM Option : 1
T0 : External 0/0/0 10m
Hold-off (global) : 300 ms
Wait-to-restore (global) : 0 sec
Tsm Delay : 180 ms
Revertive : Yes
Force Switch: FALSE
Manual Switch: FALSE
Number of synchronization sources: 3
sm(netsync NETCLK_QL_DISABLE), running yes, state 2A
Last transition recorded: (begin)-> 2A (sf_change)-> 2A
Nominated Interfaces
Interface
Internal
To0/12
*External 0/0/0
Gi0/11
SigType
NA
NA
10M
NA
Mode/QL
NA/Dis
NA/En
NA/Dis
Sync/En
SigType
E1 CRC4
Input
Internal
Prio
251
3
1
2
QL_IN ESMC Tx
QL-SEC
NA
QL-SEC
NA
QL-SEC
NA
QL-DNU
-
ESMC Rx
NA
NA
NA
-
T4 Out
External Interface
External 0/0/0
Prio
1
Squelch
FALSE
AIS
FALSE
Interface:
--------------------------------------------Local Interface: Internal
Signal Type: NA
Mode: NA(Ql-disabled)
SSM Tx: DISABLED
SSM Rx: DISABLED
Priority: 251
QL Receive: QL-SEC
QL Receive Configured: QL Receive Overrided: QL Transmit: QL Transmit Configured: Hold-off: 0
Wait-to-restore: 0
Lock Out: FALSE
Signal Fail: FALSE
Alarms: FALSE
Slot Disabled: FALSE
SNMP input source index: 1
SNMP parent list index: 0
Local Interface: To0/12
Signal Type: NA
Mode: NA(Ql-disabled)
SSM Tx: DISABLED
SSM Rx: ENABLED
Priority: 3
QL Receive: QL-SEC
QL Receive Configured: QL Receive Overrided: QL Transmit: QL Transmit Configured: Hold-off: 300
Wait-to-restore: 0
Lock Out: FALSE
Signal Fail: FALSE
Alarms: FALSE
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-14
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Slot Disabled: FALSE
SNMP input source index: 2
SNMP parent list index: 0
Local Interface: External 0/0/0
Signal Type: 10M
Mode: NA(Ql-disabled)
SSM Tx: DISABLED
SSM Rx: DISABLED
Priority: 1
QL Receive: QL-SEC
QL Receive Configured: QL Receive Overrided: QL Transmit: QL Transmit Configured: Hold-off: 300
Wait-to-restore: 0
Lock Out: FALSE
Signal Fail: FALSE
Alarms: FALSE
Active Alarms : None
Slot Disabled: FALSE
SNMP input source index: 3
SNMP parent list index: 0
Local Interface: Gi0/11
Signal Type: NA
Mode: Synchronous(Ql-disabled)
ESMC Tx: ENABLED
ESMC Rx: ENABLED
Priority: 2
QL Receive: QL-DNU
QL Receive Configured: QL Receive Overrided: QL Transmit: QL Transmit Configured: Hold-off: 300
Wait-to-restore: 0
Lock Out: FALSE
Signal Fail: FALSE
Alarms: FALSE None
Slot Disabled: FALSE
SNMP input source index: 4
SNMP parent list index: 0
External 0/0/0 e1 crc4's Input:
Internal
Local Interface: Internal
Signal Type: NA
Mode: NA(Ql-disabled)
SSM Tx: DISABLED
SSM Rx: DISABLED
Priority: 1
QL Receive: QL-SEC
QL Receive Configured: QL Receive Overrided: QL Transmit: QL Transmit Configured: Hold-off: 300
Wait-to-restore: 0
Lock Out: FALSE
Signal Fail: FALSE
Alarms: FALSE
Slot Disabled: FALSE
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-15
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
SNMP input source index: 1
SNMP parent list index: 1
Troubleshooting Tips
Note
Before you troubleshoot, ensure that all the network clock synchronization configurations are complete.
Table 22-1 provides the troubleshooting scenarios encountered while configuring the synchronous
ethernet.
Table 22-1
Troubleshooting Scenarios for Synchronous Ethernet Configuration
Problem
Solution
Clock selection
•
Verify that there are no alarms on the interfaces. Use the show network-clock
synchronization detail RP command to confirm.
•
Use the show network-clock synchronization command to confirm if the system is in
revertive mode or non-revertive mode and verify the non-revertive configurations as
shown in this example:
Router# show network-clocks synchronization
Symbols:
En - Enable, Dis - Disable, Adis - Admin Disable
NA - Not Applicable
*
- Synchronization source selected
#
- Synchronization source force selected
&
- Synchronization source manually switched
Automatic selection process : Enable
Equipment Clock : 2048 (EEC-Option1)
Clock Mode : QL-Disable
ESMC : Disabled
SSM Option : 1
T0 : GigabitEthernet0/4
Hold-off (global) : 300 ms
Wait-to-restore (global) : 300 sec
Tsm Delay : 180 ms
Revertive : Yes<<<<If it is non revertive then it will show NO here.
The above example does not show the complete command output. For complete
command output, see the example in Verifying the Synchronous Ethernet
configuration.
Note
•
Reproduce the current issue and collect the logs using the debug network-clock
errors, debug network-clock event, and debug network-clock sm RP commands.
Warning
•
We suggest you do not use these debug commands without TAC supervision.
Contact Cisco technical support if the issue persists.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-16
OL-23826-09
Chapter 22
Configuring Clocking
Configuring Network Clock for Cisco ASR 901 Router
Problem
Solution
Incorrect quality level (QL)
values when you use the show
network-clock
synchronization detail
command.
•
Use the network clock synchronization SSM (option 1 | option 2) command to
confirm that there is no framing mismatch. Use the show run interface command to
validate the framing for a specific interface. For the SSM option 1 framing should be
an E1 and for SSM option 2, it should be a T1.
Error message
“%NETCLK-6-SRC_UPD:
Synchronization source 10m
0/0/0 status (Critical
Alarms(OOR)) is posted to all
selection process" is displayed.
•
Interfaces with alarms or OOR cannot be the part of selection process even if it has
higher quality level or priority. OOR should be cleared manually. OOR can be cleared
by platform command clear platform timing oor-alarms.
Troubleshooting ESMC Configuration
Use the following debug commands to troubleshoot the PTP configuration on the Cisco ASR 901 router:
Warning
We suggest you do not use these debug commands without TAC supervision.
Command
Purpose
debug esmc error
debug esmc event
debug esmc packet [interface
interface-name>]
debug esmc packet rx [interface
interface-name]
debug esmc packet tx [interface
interface-name]
Verify whether the ESMC packets are transmitted and
received with proper quality-level values.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-17
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Configuring PTP for the Cisco ASR 901 Router
Note
Before configuring PTP, you should set the system time to the current time. See Setting System Time to
Current Time section for configuration details.
This section contains the following topics:
•
Restrictions
•
Setting System Time to Current Time
•
Configuring PTP Ordinary Clock
•
Configuring PTP in Unicast Mode
•
Configuring PTP in Unicast Negotiation Mode
•
PTP Boundary Clock
•
Verifying PTP modes
•
Verifying PTP Configuration on the 1588V2 Slave
•
Verifying PTP Configuration on the 1588V2 Master
•
PTP Hybrid Clock
•
SSM and PTP Interaction
•
ClockClass Mapping
•
PTP Redundancy
•
Configuring ToD on 1588V2 Slave
•
Troubleshooting Tips
•
Only unicast direct and unicast negotiation modes are supported. Multicast mode is not supported.
•
PTP slave supports both single and two-step modes. PTP master supports only two-step mode.
•
VLAN 4093 is used for internal PTP communication; do not use VLAN 4093 in your network.
•
Loopback interface is used in Cisco ASR 901 router instead of ToP interface for configuring 1588
interface/IP address.
•
The 1pps output command is not supported on master ordinary clock.
•
Sync and Delay request rates should be above 32 pps. The optimum value is 64 pps.
•
Clock-ports start as master even when they are configured as slave-only. The initial or reset state of
the clock is master. Therefore, the master clock must have higher priority (priority1, priority2) for
the slave to accept the master.
Restrictions
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-18
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Setting System Time to Current Time
To set the system time to the current time before configuring PTP, complete the steps given below:
SUMMARY STEPS
1.
enable
2.
calendar set hh : mm : ss day month year
3.
clock read-calendar
4.
show clock
DETAILED STEPS
Command
Purpose
Router# calendar set hh : mm : ss day
month year
Sets the hardware clock.
Example:
Router# calendar set 09:00:00 6 Feb 2013
Router# clock read-calendar
•
hh : mm : ss—RCurrent time in hours (using
24-hour notation), minutes, and seconds.
•
day—Current day (by date) in the month.
•
month—Current month (by name).
•
year—Current year (no abbreviation).
Synchronizes the system clock with the calendar time.
Example:
Router# clock read-calendar
Verifies the clock setting.
Router# show clock
Example:
Router# show clock
Configuring PTP Ordinary Clock
The following sections describe how to configure a PTP ordinary clock.
•
Configuring Master Ordinary Clock, page 22-19
•
Configuring Slave Ordinary Clock, page 22-21
Configuring Master Ordinary Clock
Complete the following steps to configure the a master ordinary clock:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ptp clock ordinary domain domain
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-19
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
4.
priority1 priority-value
5.
priority2 priority-value
6.
clock-port port-name master
7.
transport ipv4 unicast interface interface-type interface-number
8.
clock-destination clock-ip-address
9.
sync interval interval
10. announce interval interval
11. end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ptp clock ordinary domain domain
Example:
Configures the PTP clock as an ordinary clock and enters
clock configuration mode.
•
Router(config)# ptp clock ordinary
domain 0
Step 4
priority1 priority-value
domain—The PTP clocking domain number. The
range is from 0 to 127.
(Optional) Sets the preference level for a clock.
•
Example:
priority-value—The range is from 0 to 255. The
default is 128.
Router(config-ptp-clk)# priority1 4
Step 5
priority2 priority-value
Example:
Router(config-ptp-clk)# priority2 8
(Optional) Sets a secondary preference level for a clock.
The priority2 value is considered only when the router is
unable to use priority1 and other clock attributes to select
a clock.
•
Step 6
clock-port port-name master
Example:
priority-value—The range is from 0 to 255. The
default is 128.
Sets the clock port to PTP master and enters clock port
configuration mode. In master mode, the port exchanges
timing packets with PTP slave devices.
Router(config-ptp-clk)# clock-port
Master master
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-20
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 7
Command
Purpose
transport ipv4 unicast interface
Sets port transport parameters.
interface-type interface-number
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
Example:
Router(config-ptp-port)# transport
ipv4 unicast interface loopback 0
Step 8
clock-destination clock-ip-address
Specifies the IP address of a clock destination when the
router is in PTP master mode.
Example:
Router(config-ptp-port)#
clock-destination 8.8.8.1
Step 9
sync interval interval
Example:
Router(config-ptp-port)# sync
interval -5
(Optional) Specifies the interval used to send PTP
synchronization messages. The intervals are set using log
base 2 values. The Cisco ASR 901 router supports the
following values:
•
-5—1 packet every 1/32 seconds, or 32 packets per
second.
•
-6—1 packet every 1/64 seconds, or 64 packets per
second.
The default is -6.
Step 10
announce interval interval
Example:
Router(config-ptp-port)# announce
interval 2
(Optional) Specifies the interval for PTP announce
messages. The intervals are set using log base 2 values, as
follows:
•
4—1 packet every 16 seconds
•
3—1 packet every 8 seconds
•
2—1 packet every 4 seconds
•
1—1 packet every 2 seconds
•
0—1 packet every second
The default is 1.
Step 11
Exits clock port configuration mode and enters privileged
EXEC mode.
end
Example:
Router(config-ptp-port)# end
Configuring Slave Ordinary Clock
Complete the following steps to configure a slave ordinary clock:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ptp clock ordinary domain domain
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-21
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
4.
clock-port port-name slave
5.
transport ipv4 unicast interface interface-type interface-number
6.
clock source source-address
7.
announce timeout value
8.
delay-req interval interval
9.
sync interval interval
10. end
Note
PTP redundancy is an implementation on different clock nodes by which the PTP slave clock node
interacts with multiple master ports such as grand master, boundary clock nodes, and so on. A new servo
mode is defined under PTP to support high PDV scenarios (when the PDVs exceed G.8261 standard
profiles). You should use the servo mode high-jitter command to enable this mode on the PTP slave. In
servo mode, convergence time would be longer than usual, as this mode is meant only for frequency
synchronization.
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ptp clock ordinary domain domain
Configures the PTP clock as an ordinary clock and enters
clock configuration mode.
Example:
Router(config)# ptp clock ordinary
domain 0
Step 4
clock-port port-name master
Example:
Sets the clock port to PTP slave mode and enters clock port
configuration mode. In slave mode, the port exchanges
timing packets with a PTP master clock.
Router(config-ptp-clk)# clock-port
Slave slave
Step 5
transport ipv4 unicast interface
interface-type interface-number
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
Example:
Router(config-ptp-port)# transport
ipv4 unicast interface loopback 0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-22
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 6
Command
Purpose
clock source source-address
Specifies the address of a PTP master clock.
Example:
Router(config-ptp-port)# clock
source 8.8.8.1
Step 7
announce timeout value
(Optional) Specifies the number of PTP announcement
intervals before the session times out.
•
Example:
value—The range is from 1 to 10. The default is 3.
Router(config-ptp-port)# announce
timeout 8
Step 8
delay-req interval interval
(Optional) Configures the minimum interval allowed
between PTP delay request messages.
Example:
The intervals are set using log base 2 values, as follows:
Router(config-ptp-port)# delay-req
interval 1
•
5—1 packet every 32 seconds
•
4—1 packet every 16 seconds
•
3—1 packet every 8 seconds
•
2—1 packet every 4 seconds
•
1—1 packet every 2 seconds
•
0—1 packet every second
•
-1—1 packet every 1/2 second, or 2 packets per second
•
-2—1 packet every 1/4 second, or 4 packets per second
•
-3—1 packet every 1/8 second, or 8 packets per second
•
-4—1 packet every 1/16 seconds, or 16 packets per
second.
•
-5—1 packet every 1/32 seconds, or 32 packets per
second.
•
-6—1 packet every 1/64 seconds, or 64 packets per
second.
•
-7—1 packet every 1/128 seconds, or 128 packets per
second.
The default is -6.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-23
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 9
Command
Purpose
sync interval interval
(Optional) Specifies the interval used to send PTP
synchronization messages. The intervals are set using log
base 2 values. The Cisco ASR 901 router supports the
following values:
Example:
Router(config-ptp-port)# sync
interval -5
•
-5—1 packet every 1/32 seconds, or 32 packets per
second.
•
-6—1 packet every 1/64 seconds, or 64 packets per
second.
The default is -6.
Step 10
end
Exits clock port configuration mode and enters privileged
EXEC mode.
Example:
Router(config-ptp-port)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-24
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Configuring PTP in Unicast Mode
In unicast mode, the slave port and the master port need to know each other’s IP address. Unicast mode
has one to one mapping between the slave and the master. One master can have just one slave and
vice-versa. Unicast mode is not a good option for scalability.
The command used for configuring Cisco ASR 901 on unicast mode is clock-port.
Command
Purpose
Router(config-ptp-clk)# clock-port
Configures Cisco ASR 901 on unicast mode. The
following options can be configured with this
command:
•
Port Name
•
Port Role
Before configuring Cisco ASR 901 on different modes, you need to configure the loopback address. The
following example shows the configuration of loopback address:
Note
This loopback address cannot be used for any protocol other than PTP.
Router(config)#int loopback
Router(config-if)#ip address 8.8.8.2 255.255.255.255
Router(config-if)#no sh
Router#sh run int loopback
Building configuration...
Current configuration : 72 bytes
!
interface loopback
ip address 8.8.8.2 255.255.255.255
end
!
Note
Ensure that this loopback interface is reachable (using ICMP ping) from remote locations, before
assigning the interface to PTP. Once the interface is assigned to PTP, it does not respond to ICMP pings.
The following example shows the configuration of Cisco ASR 901 on the unicast mode:
Router# configure terminal
Router(config)# ptp clock ordinary domain 0
Router(config-ptp-clk) clock-port SLAVE slave
Router(config-ptp-port)# transport ipv4 unicast interface loopback 10
Router(config-ptp-port)# clock-source 8.8.8.1
Configuring PTP in Unicast Negotiation Mode
In unicast negotiation mode, master port does not know the slave port at the outset. Slave port sends
negotiation TLV when active and master port figures out that there is some slave port for
synchronization. Unicast negotiation mode is a good option for scalability as one master has multiple
slaves.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-25
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
The command used for configuring Cisco ASR 901router on unicast negotiation mode is clock-port.
Command
Purpose
Router(config-ptp-clk)# clock-port
Configures Cisco ASR 901 router on unicast
negotiation mode. The following options can be
configured with this command:
•
Port Name
•
Port Role
The following example shows the configuration of Cisco ASR 901 router on the unicast negotiation
mode:
Router# configure terminal
Router(config)# ptp clock ordinary domain 0
Router(config-ptp-clk) clock-port SLAVE slave
Router(config-ptp-port)# transport ipv4 unicast interface loopback 23 negotiation
Router(config-ptp-port)# clock-source 8.8.8.1
Router(config)# ptp clock ordinary domain 0
Router(config-ptp-clk)# clock-port MASTER Master
Router(config-ptp-port)# transport ipv4 unicast interface loopback 23 negotiation
Router(config-ptp-port)# sync interval <>
Router (config-ptp-port)# announce interval <>
PTP Boundary Clock
A PTP boundary clock (BC) acts as a middle hop between a PTP master and PTP slave. It has multiple
ports which can act as a master or slave port as shown in Figure 22-1. A PTP boundary clock has one
slave port and one or more master ports. A slave port acts as a slave to a remote PTP master, while a
master port acts as a master to a remote PTP slave. A PTP boundary clock derives clock from a
master/grand master clock (by acting as a slave) and sends the derived clock to the slaves connected to
it (by acting as a master).
PTP boundary clock starts its own PTP session with a number of downstream slaves. The PTP boundary
clock mitigates the number of network hops and results in packet delay variations in the packet network
between the grand master and slave.
Figure 22-1
PTP Boundary Clock
PTP Slaves
PTP Boundary
S
M
PTP Master
M
S
M
S
M
S
303315
M - Master Port
S - Slave Port
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-26
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
The ASR 901 PTP boundary clock has the following capabilities:
•
Support for up to 20 clock ports.
•
Simultaneous support for static and negotiated clock ports.
•
Support for up to 36 slaves and 1 master.
Note
If all clock ports created in PTP boundary clock are static, Cisco ASR 901 supports only
1 master port and 19 slave ports. However, if one or more slave ports are configured in unicast
negotiation mode, Cisco ASR 901 can support up to 36 slaves.
•
Support for dynamic addition and deletion of clock ports. This capability is supported only on
boundary clock master ports.
•
Support for selecting boundary clock as the clock source.
Configuring PTP Boundary Clock
Complete the following steps to configure the PTP boundary clock.
Prerequisites
•
Note
Install the 1588BC license before configuring the PTP boundary clock. For more information on
installing the license, see “Installing the License” section on page 2-11.
If PTP boundary clock is configured before installing the 1588BC license, remove the boundary
clock configuration and reconfigure the boundary clock after the license installation.
•
Configure a different loopback address for each PTP master or slave port before configuring the PTP
boundary clock. For more information on configuring loopback address, see “Configuring PTP in
Unicast Mode” section on page 22-25.
•
The loopback address configured for PTP port can be used only for PTP functionality.
•
The loopback address configured for PTP port does not respond to pings.
•
A clock port once configured as master cannot change to slave dynamically, and vice versa.
•
PTP boundary clock can be configured for only one domain.
1.
enable
2.
configure terminal
3.
ptp clock boundary domain domain
4.
clock-port port-name slave
5.
transport ipv4 unicast interface interface-type interface-number [negotiation]
6.
clock source source-address
7.
clock-port port-name master
Restrictions
SUMMARY STEPS
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-27
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
8.
transport ipv4 unicast interface interface-type interface-number [negotiation]
9.
exit
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ptp clock boundary domain domain
Example:
Configures the PTP boundary clock and enters clock
configuration mode.
•
Router(config)# ptp clock boundary
domain 0
Step 4
clock-port port-name slave
Example:
domain—The PTP clocking domain number. Valid
values are from 0 to 127.
Sets the clock port to PTP slave mode and enters the clock
port configuration mode. In slave mode, the port exchanges
timing packets with a PTP master clock.
Router(config-ptp-clk)# clock-port
SLAVE slave
Step 5
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Example:
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
•
negotiation—(Optional) Enables dynamic discovery
of slave devices and their preferred format for sync
interval and announce interval messages.
Router(config-ptp-port)# transport
ipv4 unicast interface Loopback 0
negotiation
Step 6
clock source source-address
Specifies the address of a PTP master clock.
Example:
Router(config-ptp-port)# clock
source 133.133.133.133
Step 7
clock-port port-name master
Sets the clock port to PTP master mode. In master mode,
the port exchanges timing packets with PTP slave devices.
Example:
Note
Router(config-ptp-port)# clock-port
Master master
The master clock-port does not establish a clocking
session until the slave clock-port is phase aligned.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-28
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 8
Command or Action
Purpose
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Sets port transport parameters.
Example:
Router(config-ptp-port)# transport
ipv4 unicast interface Loopback 1
negotiation
Step 9
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
•
negotiation—(Optional) Enables dynamic discovery
of slave devices and their preferred format for sync
interval and announce interval messages.
Exits clock port configuration mode.
exit
Example:
Router(config-ptp-port)# exit
Verifying PTP modes
Ordinary Clock
Use the show ptp clock dataset current command to display the sample output.
Router#show ptp clock dataset current
CLOCK [Ordinary Clock, domain 0]
Steps Removed: 1
Offset From Master: 0
Use the show ptp clock dataset default command to display the sample output.
Router#show ptp clock dataset default
CLOCK [Ordinary Clock, domain 0]
Two Step Flag: No
Clock Identity: 0x0:A:8B:FF:FF:5C:A:80
Number Of Ports: 1
Priority1: 128
Priority2: 128
Domain Number: 0
Slave Only: Yes
Clock Quality:
Class: 13
Accuracy: Greater than 10s
Offset (log variance): 52592
Use the show ptp clock dataset parent domain command to display the sample output.
Router# show ptp clock dataset parent domain 0
CLOCK [Ordinary Clock, domain 0]
Parent Stats: No
Observed Parent Offset (log variance): 65535
Observed Parent Clock Phase Change Rate: 0
Grandmaster Clock:
Identity: 0x0:D0:4:FF:FF:B8:6C:0
Priority1: 128
Priority2: 128
Clock Quality:
Class: 13
Accuracy: Within 1s
Offset (log variance): 52592
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-29
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Use the show ptp clock dataset time-properties domain command to display the sample output.
Router# show ptp clock dataset time-properties domain 0
CLOCK [Ordinary Clock, domain 0]
Current UTC Offset Valid: TRUE
Current UTC Offset: 33
Leap 59: FALSE
Leap 61: FALSE
Time Traceable: TRUE
Frequency Traceable: TRUE
PTP Timescale: TRUE
Time Source: Internal Oscillator
Boundary Clock
Use the show ptp clock dataset current command to display the sample output.
Router# show ptp clock dataset current
CLOCK [Boundary Clock, domain 0]
Steps Removed: 0
Offset From Master: 0ns
Use the show ptp clock dataset default command to display the sample output.
Router# show ptp clock dataset default
CLOCK [Boundary Clock, domain 0]
Two Step Flag: No
Clock Identity: 0x0:0:0:FF:FE:0:23:45
Number Of Ports: 1
Priority1: 128
Priority2: 128
Domain Number: 0
Slave Only: Yes
Clock Quality:
Class: 248
Accuracy: Within 25us
Offset (log variance): 22272
Use the show ptp clock dataset parent domain command to display the sample output.
Router# show ptp clock dataset parent domain 0
CLOCK [Boundary Clock, domain 0]
Parent Stats: No
Observed Parent Offset (log variance): 0
Observed Parent Clock Phase Change Rate: 0
Grandmaster Clock:
Identity: 0x0:0:0:FF:FE:0:23:45
Priority1: 128
Priority2: 128
Clock Quality:
Class: 248
Accuracy: Within 25us
Offset (log variance): 22272
Use the show ptp clock dataset time-properties domain command to display the sample output.
Router# show ptp clock dataset time-properties domain 0
CLOCK [Boundary Clock, domain 0]
Current UTC Offset Valid: FALSE
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-30
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Current UTC Offset: 34
Leap 59: FALSE
Leap 61: FALSE
Time Traceable: FALSE
Frequency Traceable: FALSE
PTP Timescale: FALSE
Time Source: Internal Oscillator
Verifying PTP Configuration on the 1588V2 Slave
The following examples help you verify the PTP configuration on the1588V2 slave.
Note
The loopback interface assigned to PTP does not respond to ICMP pings. To check route availability,
either do it before assigning the interface to PTP, or remove PTP from the interface and then perform
ICMP ping. For removing PTP, use no transport ipv4 unicast interface loopback interface command.
Note
The bridge state indicates the extension of previously known state which can be ignored or considered
to be normal. The clock state can get into holdover from bridge state when the packet delay variation is
high on the received PTP packets or the PTP connection is lost. This holdover state indicates that the
clock cannot be recovered from PTP packets as the quality is poor.
Example 1
Router# show ptp clock runn dom 0
PTP Ordinary Clock [Domain 0]
State
Ports
Pkts sent
Pkts rcvd
ACQUIRING
1
5308
27185
PORT SUMMARY
Name
Tx Mode
Role
Transport
State
Sessions
SLAVE
unicast
slave
Lo10
-
1
SESSION INFORMATION
SLAVE [L010] [Sessions 1]
Peer addr
Pkts in
Pkts out
In Errs
Out Errs
3.3.3.3
27185
5308
0
0
Example 2
Router# show platform ptp state
flag = 2
FLL State
FLL Status Duration
Forward
Forward
Forward
Forward
Forward
Flow
Flow
Flow
Flow
Flow
: 2 (Fast Loop)
: 7049 (sec)
Weight
:
Transient-Free
:
Transient-Free
:
Transactions Used:
Oper. Min TDEV
:
0.0
900 (900 sec Window)
3600 (3600 sec Window)
23.0 (%)
4254.0 (nsec)
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-31
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Forward Mafie
: 38.0
Forward Flow Min Cluster Width: 7550.0 (nsec)
Forward Flow Mode Width
: 21400.0 (nsec)
Reverse
Reverse
Reverse
Reverse
Reverse
Reverse
Reverse
Reverse
Flow Weight
:
Flow Transient-Free
:
Flow Transient-Free
:
Flow Transactions Used:
Flow Oper. Min TDEV
:
Mafie
:
Flow Min Cluster Width:
Flow Mode Width
:
100.0
900 (900 sec Window)
3600 (3600 sec Window)
200.0 (%)
487.0 (nsec)
36.0
225.0 (nsec)
450.0 (nsec)
Frequency Correction
Phase Correction
: 257.0 (ppb)
: 0.0 (ppb)
Output TDEV Estimate
Output MDEV Estimate
: 1057.0 (nsec)
: 1.0 (ppb)
Residual Phase Error
Min. Roundtrip Delay
: 0.0 (nsec)
: 45.0 (nsec)
Sync Packet Rate
Delay Packet Rate
: 65 (pkts/sec)
: 65 (pkts/sec)
Forward IPDV % Below Threshold: 0.0
Forward Maximum IPDV
: 0.0 (usec)
Forward Interpacket Jitter
: 0.0 (usec)
Reverse IPDV % Below Threshold: 0.0
Reverse Maximum IPDV
: 0.0 (usec)
Reverse Interpacket Jitter
: 0.0 (usec)
Verifying PTP Configuration on the 1588V2 Master
A typical configuration on a 1588V2 master is:
ptp clock ordinary domain 0
tod 0/0 cisco
input 1pps 0/0
clock-port MASTER master
transport ipv4 unicast interface Lo20 negotiation
Use the show ptp clock running domain command to display the PTP clock configuration:
Router# show ptp clock running domain 0
PTP Ordinary Clock [Domain 0]
State
Ports
FREQ_LOCKED
1
Pkts sent
Pkts rcvd
1757273
599954
Transport
State
PORT SUMMARY
Name
Tx Mode
Role
o
unicast
master
Lo20
Master
Sessions
5
SESSION INFORMATION
o [Lo20] [Sessions 5]
Peer addr
Pkts in
Pkts out
In Errs
Out Errs
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-32
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
9.9.9.14
9.9.9.13
9.9.9.11
9.9.9.12
9.9.9.10
120208
120159
120148
119699
119511
344732
344608
343955
342863
342033
0
0
0
0
0
0
0
0
0
0
Use the show platform ptp stats command to display the PTP statistics:
Statistics for PTP clock 0
###############################
Number of ports : 1
Pkts Sent : 1811997
Pkts Rcvd : 619038
Pkts Discarded : 0
Statistics for PTP clock port 1
##################################
Pkts Sent : 1811997
Pkts Rcvd : 619038
Pkts Discarded : 0
Signals Rejected : 0
Statistics for peer 1
########################
IP addr : 9.9.9.14
Pkts Sent : 355660
Pkts Rcvd : 124008
Statistics for peer 2
########################
IP addr : 9.9.9.13
Pkts Sent : 355550
Pkts Rcvd : 123973
Statistics for peer 3
########################
IP addr : 9.9.9.11
Pkts Sent : 354904
Pkts Rcvd : 123972
Statistics for peer 4
########################
IP addr : 9.9.9.12
Pkts Sent : 353815
Pkts Rcvd : 123525
Statistics for peer 5
########################
IP addr : 9.9.9.10
Pkts Sent : 352973
Pkts Rcvd : 123326
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-33
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
PTP Hybrid Clock
To improve the clock quality, you can either improve the oscillator class or reduce the number of hops
between the master and the slave. In PTP hybrid mode, the oscillator class is improved by using a
physical layer clock (sourced from a stratum-1 clock) instead of the available internal oscillator. The
PTP hybrid mode is supported for ordinary clock (in slave mode only) and boundary clock.
Configuring a Hybrid Ordinary Clock
Complete the following steps to configure a hybrid clocking in ordinary slave clock mode:
Prerequisites
When configuring a hybrid clock, ensure that the frequency and phase sources are traceable to the same
master clock.
Restrictions
•
Hybrid mode is not supported when PTP ordinary clock is in the master mode.
•
Hybrid clock is not supported with ToP as network-clock. It needs a valid physical clock source, for
example, Sync-E/BITS/10M/TDM.
1.
enable
2.
configure terminal
3.
ptp clock ordinary domain domain [hybrid]
4.
clock-port port-name slave
5.
transport ipv4 unicast interface interface-type interface-number
6.
clock source source-address
7.
announce timeout value
8.
delay-req interval interval
9.
sync interval interval
SUMMARY STEPS
10. end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-34
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
ptp clock ordinary domain domain
hybrid
Configures the PTP clock as an ordinary clock and enters
clock configuration mode.
•
domain—The PTP clocking domain number. Valid
values are from 0 to 127.
•
hybrid—(Optional) Enables the PTP boundary clock
to work in hybrid mode. Enables the hybrid clock such
that the output of the clock is transmitted to the remote
slaves.
Example:
Router(config)# ptp clock ordinary
domain 0
Step 4
clock-port port-name slave
Example:
Sets the clock port to PTP slave mode and enters clock port
configuration mode. In slave mode, the port exchanges
timing packets with a PTP master clock.
Router(config-ptp-clk)# clock-port
Slave slave
Step 5
transport ipv4 unicast interface
interface-type interface-number
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
Example:
Router(config-ptp-port)# transport
ipv4 unicast interface loopback 0
Step 6
clock source source-address
Specifies the address of a PTP master clock.
Example:
Router(config-ptp-port)# clock
source 8.8.8.1
Step 7
announce timeout value
(Optional) Specifies the number of PTP announcement
intervals before the session times out.
•
Example:
value—The range is from 1 to 10. The default is 3.
Router(config-ptp-port)# announce
timeout 8
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-35
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 8
Command
Purpose
delay-req interval interval
(Optional) Configures the minimum interval allowed
between PTP delay request messages.
Example:
The intervals are set using log base 2 values, as follows:
Router(config-ptp-port)# delay-req
interval 1
•
5—1 packet every 32 seconds
•
4—1 packet every 16 seconds
•
3—1 packet every 8 seconds
•
2—1 packet every 4 seconds
•
1—1 packet every 2 seconds
•
0—1 packet every second
•
-1—1 packet every 1/2 second, or 2 packets per second
•
-2—1 packet every 1/4 second, or 4 packets per second
•
-3—1 packet every 1/8 second, or 8 packets per second
•
-4—1 packet every 1/16 seconds, or 16 packets per
second.
•
-5—1 packet every 1/32 seconds, or 32 packets per
second.
•
-6—1 packet every 1/64 seconds, or 64 packets per
second.
•
-7—1 packet every 1/128 seconds, or 128 packets per
second.
The default is -6.
Step 9
sync interval interval
Example:
Router(config-ptp-port)# sync
interval -5
(Optional) Specifies the interval used to send PTP
synchronization messages. The intervals are set using log
base 2 values. The Cisco ASR 901 router supports the
following values:
•
-5—1 packet every 1/32 seconds, or 32 packets per
second.
•
-6—1 packet every 1/64 seconds, or 64 packets per
second.
The default is -6.
Step 10
end
Exits clock port configuration mode and enters privileged
EXEC mode.
Example:
Router(config-ptp-port)# end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-36
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Configuring a Hybrid Boundary Clock
Complete the following steps to configure a hybrid clocking in PTP boundary clock mode.
Prerequisites
When configuring a hybrid clock, ensure that the frequency and phase sources are traceable to the same
master clock.
Restrictions
Hybrid clock is not supported with ToP as network-clock. It needs a valid physical clock source, for
example, Sync-E/BITS/10M/TDM.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ptp clock boundary domain domain [hybrid]
4.
clock-port port-name slave
5.
transport ipv4 unicast interface interface-type interface-number [negotiation]
6.
clock source source-address
7.
clock-port port-name master
8.
transport ipv4 unicast interface interface-type interface-number [negotiation]
9.
exit
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
ptp clock boundary domain domain
hybrid
Configures the PTP boundary clock and enters clock
configuration mode.
•
domain—The PTP clocking domain number. Valid
values are from 0 to 127.
•
hybrid—(Optional) Enables the PTP boundary clock
to work in hybrid mode. Enables the hybrid clock such
that the output of the clock is transmitted to the remote
slaves.
Example:
Router(config)# ptp clock boundary
domain 0 hybrid
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-37
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 4
Command or Action
Purpose
clock-port port-name slave
Sets the clock port to PTP slave mode and enters the clock
port configuration mode. In slave mode, the port exchanges
timing packets with a PTP master clock.
Example:
Router(config-ptp-clk)# clock-port
SLAVE slave
Step 5
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Example:
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
•
negotiation—(Optional) Enables dynamic discovery
of slave devices and their preferred format for sync
interval and announce interval messages.
Router(config-ptp-port)# transport
ipv4 unicast interface Loopback 0
negotiation
Step 6
clock source source-address
Specifies the address of a PTP master clock.
Example:
Router(config-ptp-port)# clock
source 133.133.133.133
Step 7
clock-port port-name master
Sets the clock port to PTP master mode. In master mode,
the port exchanges timing packets with PTP slave devices.
Example:
Note
Router(config-ptp-port)# clock-port
Master master
Step 8
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Example:
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
•
negotiation—(Optional) Enables dynamic discovery
of slave devices and their preferred format for sync
interval and announce interval messages.
Router(config-ptp-port)# transport
ipv4 unicast interface Loopback 1
negotiation
Step 9
exit
The master clock-port does not establish a clocking
session until the slave clock-port is phase aligned.
Exits clock port configuration mode.
Example:
Router(config-ptp-port)# exit
Note
The hybrid clock (HC) relies on an external clock source for frequency recovery while phase is recovered
through PTP. Once the HC reaches the normal or phase aligned state, and if the external frequency
channel is active and traceable to PRC, then the HC moves into the phase aligned state even when the
PTP link is down.
Verifying Hybrid modes
Use the show running-config | section ptp command to display the sample output.
Router# show running-config | section ptp
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-38
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
ptp clock ordinary domain 20 hybrid
time-properties gps timeScaleTRUE currentUtcOffsetValidTRUE leap59FALSE leap61FALSE 35
clock-port SLAVE slave
transport ipv4 unicast interface Lo17
clock source 17.17.1.1
Use the show ptp clock running domain command to display the sample output.
Router# show ptp clock running domain
PTP Ordinary Clock [Domain 20] [Hybrid]
State
Ports
Pkts sent
Pkts rcvd
Redundancy Mode
PHASE_ALIGNED
1
27132197
81606642
Track all
PORT SUMMARY
Name
Tx Mode
SLAVE unicast
Role
Transport
State
Sessions
PTP Master
Port Addr
slave
Lo17
Slave
1
17.17.1.1
Use the show platform ptp channel_status command to display the sample output after PTP is in
normal state.
Router#show platform ptp channel_status
Configured channels : 2
channel[0]: type=0, source=0, frequency=0, tod_index=0, freq_prio=5
time_enabled=y, freq_enabled=y, time_prio=1 freq_assumed_QL=0
time_assumed_ql=0, assumed_ql_enabled=n
channel[1]: type=6, source=17, frequency=0, tod_index=0, freq_prio=2
time_enabled=n, freq_enabled=y, time_prio=0 freq_assumed_QL=0
time_assumed_ql=0, assumed_ql_enabled=n
Channel 0:
Frequency
Time
--------------------------------------Status OK
OK
Weight
0
100
QL
9
9
--------------------------------------QL is not read externally.
Fault status: 00000000
Channel 1:
Frequency
Time
--------------------------------------Status OK
Disabled
Weight
100
0
QL
9
9
--------------------------------------QL is not read externally.
Fault status: 00000000
SSM and PTP Interaction
PTP carries clock quality in its datasets in the structure defined by the IEEE 1588 specification. The
Ordinary Clock (OC) master carries the Grand Master (GM) clock quality in its default dataset which is
sent to the downstream OC slaves and Boundary Clocks (BC). The OC slaves and BCs keep the GM
clock quality in their parent datasets.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-39
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
If the T0 clock in Cisco ASR 901 is driven by the clock recovered from the OC Slave (if ToP0/12 is
selected as clock-source), then the clock quality in the PTP parent dataset represents the quality of the
ToP0/12 input clock. This should be informed to the netsync process for proper clock selection. This is
done by translating clockClass data field in clock quality to QL-values expected by netsync.
On the other hand, if Cisco ASR 901 serves as the OC Master, then the GM clock is the clock providing
T0 clock to Cisco ASR 901 router. Hence, the T0 clock quality should be used by OC master to fill up
clockClass in the clock quality field, in its default dataset. For this, the T0 output QL-value should be
mapped to the clockClass value according to ITU-T Telecom Profile, and set in the default dataset of the
OC Master. This QL-value is then transmitted to the PTP slaves and BC downstream.
ClockClass Mapping
The Cisco ASR 901 router supports two methods of mapping PTP ClockClass to SSM/QL-value:
•
Telecom Profile based on ITU-T G.8265.1/Y.1365.1 PTP (Telecom) Profile for Frequency
Synchronization [2]
•
Default method of calculating clockClass based on IEEE 1588v2 PTP specification.
Telecom Profiles
The Telecom Profile specifies an alternative algorithm for selecting between different master clocks,
based on the quality level (QL) of master clocks and on a local priority given to each master clock.
Release 3.11 introduces support for telecom profiles using a new configuration method, which allow you
to configure a clock to use the G.8265.1 recommendations for establishing PTP sessions, determining
the best master clock, handling SSM, and mapping PTP classes.
PTP Redundancy
PTP redundancy is an implementation on different clock nodes by which the PTP slave clock node
achieves the following:
Note
•
Interact with multiple master ports such as grand master, boundary clock nodes, and so on.
•
Open PTP sessions.
•
Select the best master from the existing list of masters (referred to as the primary PTP master port
or primary clock source).
•
Switch to the next best master available in case the primary master fails, or the connectivity to the
primary master fails.
The Cisco ASR 901 Series Router supports unicast-based timing as specified in the 1588-2008 standard.
Hybrid mode is not supported with PTP 1588 redundancy.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-40
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Configuring Telecom Profile in Slave Ordinary Clock
Complete the following steps to configure the telecom profile in slave ordinary clock.
Prerequisites
•
When configuring the Telecom profile, ensure that the master and slave nodes have the same
network option configured.
•
Negotiation should be enabled for master and slave modes.
•
Cisco ASR 901 router must be enabled using the network-clock synchronization mode
QL-enabled command for both master and slave modes.
•
Telecom profile is not applicable for boundary clocks. It is only applicable for ordinary clocks.
•
Hybrid mode with OC-MASTER is not supported.
1.
enable
2.
configure terminal
3.
ptp clock ordinary domain domain [hybrid]
4.
clock-port port-name slave [profile g8265.1]
5.
transport ipv4 unicast interface interface-type interface-number [negotiation]
6.
clock source source-address [priority]
7.
clock source source-address [priority]
8.
clock source source-address [priority]
9.
clock source source-address [priority]
Restrictions
SUMMARY STEPS
10. end
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-41
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 3
Command
Purpose
ptp clock ordinary domain domain
Configures the PTP ordinary clock and enters clock
configuration mode.
Example:
•
Router(config)# ptp clock ordinary
domain 4
Step 4
clock-port port-name {master |
slave} [profile g8265.1]
Example:
Router(config-ptp-clk)# clock-port
Slave slave
Sets the clock port to PTP slave mode and enters clock port
configuration mode. In slave mode, the port exchanges
timing packets with a PTP master clock.
The profile keyword configures the clock to use the
G.8265.1 recommendations for establishing PTP sessions,
determining the best master clock, handling SSM, and
mapping PTP classes.
Note
Step 5
transport ipv4 unicast interface
interface-type interface-number
domain—The PTP clocking domain number. Valid
values are from 4 to 23.
Using a telecom profile requires that the clock have
a domain number of 4–23.
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
Example:
Router(config-ptp-port)# transport
ipv4 unicast interface loopback 0
Step 6
clock source source-address
[priority]
Specifies the address of a PTP master clock. You can
specify a priority value as follows:
•
No priority value—Assigns a priority value of 0, the
highest priority.
•
1—Assigns a priority value of 1.
•
2—Assigns a priority value of 2.
Example:
Router(config-ptp-port)# clock
source 8.8.8.1
Step 7
clock source source-address
[priority]
Specifies the address of an additional PTP master clock;
repeat this step for each additional master clock. You can
configure up to four master clocks.
Example:
Router(config-ptp-port)# clock
source 8.8.8.2 1
Step 8
clock source source-address
[priority]
Specifies the address of an additional PTP master clock;
repeat this step for each additional master clock. You can
configure up to four master clocks.
Example:
Router(config-ptp-port)# clock
source 8.8.8.3 2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-42
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Step 9
Command
Purpose
clock source source-address
[priority]
Specifies the address of an additional PTP master clock;
repeat this step for each additional master clock. You can
configure up to four master clocks.
Example:
Router(config-ptp-port)# clock
source 8.8.8.4 3
Step 10
Exits clock port configuration mode and enters privileged
EXEC mode.
end
Example:
Router(config-ptp-port)# end
Configuring Telecom Profile in Master Ordinary Clock
Complete the following steps to configure the telecom profile in the master ordinary clock.
Prerequisites
•
When configuring the telecom profile, ensure that the master and slave nodes have the same network
option configured.
•
Negotiation should be enabled for master and slave modes.
•
Cisco ASR 901 router must be enabled using the network-clock synchronization mode
QL-enabled command for both master and slave modes.
•
Telecom profile is not applicable for boundary clocks. It is only applicable for ordinary clocks.
•
Hybrid mode with OC-MASTER is not supported.
1.
enable
2.
configure terminal
3.
ptp clock ordinary domain domain
4.
clock-port port-name master [profile g8265.1]
5.
transport ipv4 unicast interface interface-type interface-number [negotiation]
6.
end
Restrictions
SUMMARY STEPS
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-43
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ptp clock ordinary domain domain
Example:
Configures the PTP ordinary clock and enters clock
configuration mode.
•
Router(config)# ptp clock ordinary
domain 4
Step 4
clock-port port-name {master |
slave} [profile g8265.1]
Example:
Router(config-ptp-clk)# clock-port
Master master profile g8265.1
domain—The PTP clocking domain number. Valid
values are from 4 to 23.
Sets the clock port to PTP master and enters clock port
configuration mode. In master mode, the port exchanges
timing packets with a PTP slave devices.
The profile keyword configures the clock to use the
G.8265.1 recommendations for establishing PTP sessions,
determining the best master clock, handling SSM, and
mapping PTP classes.
Using a telecom profile requires that the clock have
a domain number of 4–23.
Note
Step 5
transport ipv4 unicast interface
interface-type interface-number
Sets port transport parameters.
•
interface-type—The type of the interface.
•
interface-number—The number of the interface.
Example:
Router(config-ptp-port)# transport
ipv4 unicast interface loopback 0
Step 6
end
Exits clock port configuration mode and enters privileged
EXEC mode.
Example:
Router(config-ptp-port)# end
Verifying Telecom profile
Use the show ptp port running detail command to display the details of PTP masters configured for a
Telecom profile slave. The PTSF and Alarm fields indicate the alarm experienced by the SLAVE clock
for the MASTER clock.
Router#show ptp port running detail
PORT [slave] CURRENT PTP MASTER PORT
Protocol Address: 208.1.1.3
Clock Identity: 0xE4:D3:F1:FF:FE:FF:BC:E4
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-44
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
PORT [slave] PREVIOUS PTP MASTER PORT
Protocol Address: 208.1.1.1
Clock Identity: 0xE4:D3:F1:FF:FE:22:F2:C8
Reason:
PORT [slave] LIST OF PTP MASTER PORTS
LOCAL PRIORITY 0
Protocol Address: 208.1.1.1
Clock Identity: 0xE4:D3:F1:FF:FE:22:F2:C8
PTSF Status:
Alarm In Stream:
Clock Stream Id: 0
Priority1: 128
Priority2: 128
Class: 102
Accuracy: Unknown
Offset (log variance): 0
Steps Removed: 0
LOCAL PRIORITY 1
Protocol Address: 208.1.1.3
Clock Identity: 0xE4:D3:F1:FF:FE:FF:BC:E4
PTSF Status:
Alarm In Stream:
Clock Stream Id: 0
Priority1: 128
Priority2: 128
Class: 100
Accuracy: Unknown
Offset (log variance): 0
Steps Removed: 0
LOCAL PRIORITY 2
Protocol Address: 208.1.1.4
Clock Identity: 0x40:55:39:FF:FE:89:44:48
PTSF Status:
Alarm In Stream:
Clock Stream Id: 0
Priority1: 128
Priority2: 128
Class: 102
Accuracy: Unknown
Offset (log variance): 0
Steps Removed: 0
Use the show ptp clock running domain command to display the sample output.
Router#show ptp clock running domain 10
PTP Ordinary Clock [Domain 10]
State
Ports
Pkts sent
Pkts rcvd
Redundancy Mode
PHASE_ALIGNED
1
22459694
67364835
Track all
PORT SUMMARY
Name
Tx Mode
SLAVE unicast
Role
Transport
State
Sessions
PTP Master
Port Addr
slave
Lo40
Slave
1
4.4.4.3
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-45
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
SESSION INFORMATION
SLAVE [Lo40] [Sessions 1]
Peer addr
Pkts in
Pkts out
In Errs
Out Errs
4.4.4.3
60023902
20011138
0
0
Setting the TimeProperties
The timeProperties dataset members (except timeTraceable and frequencyTraceable) can be individually
set by using the time-properties command.
Caution
The time-properties command does not perform any input validation; use this command with caution.
The following is an example of the time-properties command:
Router(config-ptp-clk)# time-properties atomic-clock timeScaleTRUE
currentUtcOffsetValidTRUE leap59TRUE leap61FALSE 34
slave#show ptp clock dataset time-properties
CLOCK [Ordinary Clock, domain 0]
Current UTC Offset Valid: TRUE
Current UTC Offset: 34
Leap 59: TRUE
Leap 61: FALSE
Time Traceable: TRUE
Frequency Traceable: TRUE
PTP Timescale: TRUE
Time Source: Atomic
The values of Time Traceable and Frequency Traceable are determined dynamically.
ASR901 Negotiation Mechanism
The Cisco ASR 901 router supports a maximum of 36 slaves, when configured as a negotiated 1588V2
master. For a slave to successfully negotiate with the Cisco ASR 901 master, it should request sync and
announce packet rates that are not greater than the sync and announce rate that are currently set in the
master.
For example, if the sync interval on the master is -5 (32 packets/second), and if the slave tries to negotiate
a value of sync interval value of -6 (64 packets/second), the negotiation fails.
Static Unicast Mode
A clock destination can be added when the master is configured in the static unicast mode (by
configuring the transport without the negotiation flag). The master does not communicate with any other
slave, in this configuration.
Router(config-ptp-port)#clock destination 9.9.9.10
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-46
OL-23826-09
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Configuring ToD on 1588V2 Slave
Use the following commands configure ToD on the 1588V2 slave:
Command
Purpose
Router(config-ptp-clk)# tod
<slot>/ <subslot> <Cisco/ntp/ubx/nmea >
Configures ToD on 1588V2.
Router(config-ptp-clk)# 1pps-out <1
PPS offset in ns> <pulse width> <pulse
width unit>
Configures 1 PPS output parameters.
This example shows the ToD configuration on the 1588V2 slave:
Router# config terminal
Router(config)# ptp clock ordinary domain 0
Router(config-ptp-clk)# tod 0/0 cisco
Router(config-ptp-clk)# 1pps-out 0 2250 ns
Router(config-ptp-clk)# clock-port SLAVE slave
Router(config-ptp-port)# transport ipv4 unicast interface Lo10 negotiation
Router(config-ptp-port)# clock source 1.1.1.1
Router(config-ptp-port)# end
Troubleshooting Tips
Use the following debug commands to troubleshoot the PTP configuration on the Cisco ASR 901 router:
Warning
We suggest you do not use these debug commands without TAC supervision.
Command
Purpose
[no] debug platform ptp error
Enables debugging of internal errors.
The no form of the command disables debugging
internal errors.
[no] debug platform ptp event
Displays event messages.
The no form of the command disables displaying event
messages.
[no] debug platform ptp verbose
Displays verbose output.
The no form of the command disables displaying
verbose output.
[no] debug platform ptp all
Debugs for error, event and verbose.
The no form of the command disables all debugging.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
22-47
Chapter 22
Configuring Clocking
Configuring PTP for the Cisco ASR 901 Router
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
22-48
OL-23826-09
CH A P T E R
23
Cisco IOS IP SLA
The Cisco IOS IP Service Level Agreements (SLAs) is a core part of the Cisco IOS software portfolio,
which allows Cisco customers to analyze IP service levels for IP applications and services, to increase
productivity, to lower operational costs, and to reduce the frequency of network outages.
The Cisco IOS IP SLAs uses active traffic monitoring—the generation of traffic in a continuous, reliable,
and predictable manner—for measuring network performance. Using Cisco IOS IP SLA, service
provider customers can measure and provide SLAs, and enterprise customers can verify service levels,
verify out sourced SLAs, and understand network performance.
The Cisco IOS IP SLAs can perform network assessments, verify quality of service (QoS), ease the
deployment of new services, and assist administrators with network troubleshooting.
The Cisco IOS IP SLAs can be accessed using the Cisco IOS CLI or Simple Network Management
Protocol (SNMP) through the Cisco Round-Trip Time Monitor (RTTMON) and syslog Management
Information Bases (MIBs).
For detailed information on Cisco IOS IP SLA features, see IP SLAs Configuration Guide, Cisco IOS
Release 15.1S.
Note
Cisco IOS IP SLA for VoIP, ICMP Jitter, Gatekeeper and Data Link Switching Plus (DLSw+) features
are not supported in Cisco ASR 901 router.
Contents
•
Configuring IPSLA Path Discovery, page 23-1
•
Two-Way Active Measurement Protocol, page 23-5
•
Configuring TWAMP, page 23-6
Configuring IPSLA Path Discovery
The LSP path discovery (LPD) feature allows the IP SLA MPLS LSP to automatically discover all the
active paths to the forwarding equivalence class (FEC), and configure LSP ping and traceroute
operations across various paths between the provide edge (PE) devices.
Complete the following steps to configure IPSLA path discovery in a typical VPN setup for MPLS LPD
operation:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
23-1
Chapter 23
Cisco IOS IP SLA
Configuring IPSLA Path Discovery
SUMMARY STEPS
Step 1
1.
enable
2.
configure terminal
3.
mpls discovery vpn next-hop
4.
mpls discovery vpn interval seconds
5.
auto ip sla mpls-lsp-monitor operation-number
6.
type echo ipsla-vrf-all
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
mpls discovery vpn next-hop
(Optional) Enables the MPLS VPN next hop neighbor discovery process.
Note
Example:
This command is automatically enabled when the auto ip sla
mpls-lsp-monitor command is entered.
Router(config)# mpls discovery vpn
next-hop
Step 4
mpls discovery vpn interval seconds
Example:
(Optional) Specifies the time interval at which routing entries that are no
longer valid are removed from the next hop neighbor discovery database
of an MPLS VPN.
Router(config)# mpls discovery vpn
interval 120
Step 5
auto ip sla mpls-lsp-monitor
operation-number
Begins configuration for an LSP Health Monitor operation and enters auto
IP SLA MPLS configuration mode.
Example:
Router(config)# auto ip sla
mpls-lsp-monitor 1
Router(config-auto-ip-sla-mpls)#
Step 6
type echo ipsla-vrf-all
Example:
Router(config-auto-ip-sla-mpls)#
type echo ipsla-vrf-all
Router(config-auto-ip-sla-mpls-para
ms)#
Enters MPLS parameters configuration submode and allows the user to
configure the parameters for an IP SLAs LSP ping operation using the
LSP Health Monitor.
For details on the parameters, see Configuration Parameters, page 23-2.
Configuration Parameters
Router(config)#auto ip sla mpls-lsp-monitor 1
Router(config-auto-ip-sla-mpls)#?
Auto IP SLAs MPLS LSP Monitor entry configuration commands:
exit Exit IP SLAs MPLSLM configuration
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
23-2
OL-23826-09
Chapter 23
Cisco IOS IP SLA
Configuring IPSLA Path Discovery
type
Type of entry
Router(config-auto-ip-sla-mpls)#type ?
echo
Perform MPLS LSP Ping operation
pathEcho Perform MPLS LSP Trace operation
Router(config-auto-ip-sla-mpls)#type pathEcho ?
ipsla-vrf-all Configure IP SLAs MPLS LSP Monitor for all VPNs
vrf
vrf Name
Following parameters can be configured in the auto-ip-sla-mpls-params mode:
Router(config-auto-ip-sla-mpls)#type echo ipsla-vrf-all
Router(config-auto-ip-sla-mpls-params)#?
IP SLAs MPLSLM entry parameters configuration commands:
access-list
Apply Access-List
default
Set a command to its defaults
delete-scan-factor
Scan Factor for automatic deletion
exit
Exit IP SLAs MPLSLM configuration
exp
EXP value
force-explicit-null force an explicit null label to be added
lsp-selector
LocalHost address used to select the LSP
no
Negate a command or set its defaults
path-discover
IP SLAs LSP path discover configuration
reply-dscp-bits
DSCP bits in reply IP header
reply-mode
Reply for LSP echo request
request-data-size
Request data size
scan-interval
Scan Interval for automatic discovery in minutes
secondary-frequency Frequency to be used if there is any violation condition
happens
tag
User defined tag
threshold
Operation threshold in milliseconds
timeout
Timeout of an operation
ttl
Time to live
Following parameters can be configured in the auto-ip-sla-mpls-lpd-params mode:
Router(config-auto-ip-sla-mpls-params)#path-discover
Router(config-auto-ip-sla-mpls-lpd-params)#?
IP SLAs MPLS LSP Monitor LPD configuration commands:
default
Set a command to its defaults
exit
Exit IP SLAs MPLS LSP Monitor path discover
configuration
force-explicit-null
Force an explicit null label to be added
hours-of-statistics-kept Maximum number of statistics hour groups to capture
interval
Send interval between requests in msec
lsp-selector-base
Base 127/8 address to start the tree trace
maximum-sessions
Number of concurrent active tree trace requests
which can be submit at one time
no
Negate a command or set its defaults
scan-period
Time period for finishing tree trace discovery in
minutes
session-timeout
Timeout value for the tree trace request in seconds
timeout
Timeout for an MPLS Echo Request in seconds
Example for IPSLA Path Discovery
auto ip sla mpls-lsp-monitor 1
type echo ipsla-vrf-all
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
23-3
Chapter 23
Cisco IOS IP SLA
Configuring IPSLA Path Discovery
path-discover
auto ip sla mpls-lsp-monitor schedule 1 schedule-period 1 frequency 10 start-time now
This example shows the LPD parameter values configured:
auto ip sla mpls-lsp-monitor 2
type echo vrf vpn1
path-discover
force-explicit-null
hours-of-statistics-kept 1
scan-period 30
lsp-selector-base 127.0.0.7
session-timeout 20
timeout 100
interval 1000
auto ip sla mpls-lsp-monitor schedule 2 schedule-period 1 frequency 10 start-time now
Router#show ip sla mpls-lsp-monitor summary
Index
- MPLS LSP Monitor probe index
Destination
- Target IP address of the BGP next hop
Status
- LPD group status
LPD Group ID
- Unique index to identify the LPD group
Last Operation Time
- Last time an operation was attempted by
a particular probe in the LPD Group
Index
1
Destination
2.2.2.2
Status
up
LPD Group ID
100004
Last Operation Time
*20:08:01.481 UTC Tue Nov 14 2000
Router#show ip sla mpls-lsp-monitor neighbors
IP SLA MPLS LSP Monitor Database : 1
BGP Next hop 2.2.2.2 (Prefix: 2.2.2.2/32) OK Paths: 2
ProbeID: 100004 (pavan_1)
Router# show ip sla mpls-lsp-monitor lpd operational-state
Entry number: 100004
MPLSLM Entry Number: 1
Target FEC Type: LDP IPv4 prefix
Target Address: 2.2.2.2
Number of Statistic Hours Kept: 2
Last time LPD Stats were reset: *18:00:57.817 UTC Sat Nov 11 2000
Traps Type: 1
Latest Path Discovery Mode: initial complete
Latest Path Discovery Start Time: *20:04:26.473 UTC Tue Nov 14 2000
Latest Path Discovery Return Code: OK
Latest Path Discovery Completion Time(ms): 40
Number of Paths Discovered: 2
Path Information :
Path
Outgoing
Lsp
Link Conn Adj
NextHop
Index Interface Selector
Type Id
Addr
Addr
Status
1
Vl22
127.0.0.0
90
0
22.1.1.1
22.1.1.1
OK
2
Vl26
127.0.0.0
90
0
26.1.1.2
26.1.1.2
OK
Router# show ip sla
Entry Number : 1
Modification time
Operation Type
Vrf Name
Tag
EXP Value
Timeout(ms)
Downstream
Label Stack
29
21
mpls-lsp-monitor configuration
:
:
:
:
:
:
*20:19:08.233 UTC Tue Nov 14 2000
echo
ipsla-vrf-all
0
5000
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
23-4
OL-23826-09
Chapter 23
Cisco IOS IP SLA
Two-Way Active Measurement Protocol
Threshold(ms)
: 5000
Frequency(sec)
: 10
ScanInterval(min)
: 1
Delete Scan Factor : 1
Operations List
: 100006
Schedule Period(sec): 1
Request size
: 100
Start Time
: Start Time already passed
SNMP RowStatus
: Active
TTL value
: 255
Reply Mode
: ipv4
Reply Dscp Bits
:
Path Discover
: Enable
Maximum sessions
: 1
Session Timeout(seconds) : 120
Base LSP Selector
: 127.0.0.0
Echo Timeout(seconds)
: 5
Send Interval(msec)
: 1000
Label Shimming Mode
:
Number of Stats Hours
: 2
Scan Period(minutes)
: 1
[Wrap text] [Edit this enclosure]
Unit-test_IPSLA: Added 12/02/2011 00:05:01 by pacv
[Unwrap text] [Edit this enclosure]
Unit-test_IPSLA: Added 12/02/2011 00:05:01 by pacv
Two-Way Active Measurement Protocol
Two-Way Active Measurement Protocol (TWAMP) consists of two related protocols. Use the
TWAMP-Control protocol to start performance measurement sessions. You can deploy TWAMP in a
simplified network architecture, with the control-client and the session-sender on one device and the
server and the session-reflector on another device.
The Cisco IOS software TWAMP implementation supports a basic configuration. Figure 23-1 shows a
sample deployment.
Figure 23-2 shows the four logical entities that comprise the TWAMP architecture.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
23-5
Chapter 23
Cisco IOS IP SLA
Two-Way Active Measurement Protocol
Figure 23-1
TWAMP Deployment
Server and Reflector
TWAMP-enabled device
Control-client
and sender
251575
Client
Server and Reflector
TWAMP-enabled device
TWAMP Architecture
Session-Sender
TWAMP-Test
Session-Reflector
Vendorspecific
Control-Client
Vendorspecific
TWAMP-Ctrl
Server
251576
Figure 23-2
Although each entity is separate, the protocol allows for logical merging of the roles on a single device.
Configuring TWAMP
The TWAMP server and reflector functionality are configured on the same device. This section contains
the following topics:
•
Configuring the TWAMP Server, page 23-7
•
Configuring the TWAMP Reflector, page 23-8
•
Configuration Examples for TWAMP, page 23-8
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
23-6
OL-23826-09
Chapter 23
Cisco IOS IP SLA
Two-Way Active Measurement Protocol
Configuring the TWAMP Server
Complete the following steps to configure the TWAMP server:
SUMMARY STEPS
Step 1
1.
enable
2.
configure terminal
3.
ip sla server twamp
4.
port port-number
5.
timer inactivity seconds
6.
end
7.
copy running-config startup-config
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Configures the Cisco ASR 901 router as a TWAMP server, and enters
TWAMP configuration mode.
ip sla server twamp
Example:
Router(config)# ip sla server twamp
Step 4
port port-number
Example:
Router(config-twamp-srvr)# port
9000
Step 5
timer inactivity seconds
Example:
(Optional) Specifies the port number to be used by the TWAMP server to
listen for connection and control requests. The same port negotiates for the
port to which performance probes are sent. The configured port should not
be an IANA port or any port used by other applications. The default is port
862.
(Optional) Sets the maximum time, in seconds. The session can be inactive
before the session ends. The range is between 1 to 6000 seconds. The
default is 900 seconds.
Router(config-twamp-srvr)# timer
inactivity 300
Step 6
Return to privileged EXEC mode.
end
Example:
Router(config-twamp-srvr)# end
To disable the IP SLA TWAMP server, enter the no ip sla server twamp global configuration command.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
23-7
Chapter 23
Cisco IOS IP SLA
Two-Way Active Measurement Protocol
Configuring the TWAMP Reflector
The TWAMP server and reflector functionality are both configured on the same device.
Complete the following steps to configure the TWAMP reflector:
SUMMARY STEPS
Step 1
1.
enable
2.
configure terminal
3.
ip sla responder twamp
4.
timeout seconds
5.
end
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 1
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 2
ip sla server twamp
Configures the switch as a TWAMP responder, and enter TWAMP
configuration mode.
Example:
Router(config)# ip sla server twamp
Step 3
timer inactivity seconds
Example:
(Optional) Sets the maximum time, in seconds. The session can be inactive
before the session ends. The range is between 1 to 604800 seconds. The
default is 900 seconds.
Router(config-twamp-srvr)# timer
inactivity 300
Step 4
Return to privileged EXEC mode.
end
Example:
Router(config-twamp-srvr)# end
Configuration Examples for TWAMP
This section provides the following configuration examples:
•
Example: Configuring the Router as an IP SLA TWAMP server
•
Example: Configuring the Router as an IP SLA TWAMP Reflector
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
23-8
OL-23826-09
Chapter 23
Cisco IOS IP SLA
Two-Way Active Measurement Protocol
Example: Configuring the Router as an IP SLA TWAMP server
Router(config)# ip sla server twamp
Router(config-twamp-srvr)# port 9000
Router(config-twamp-srvr)# timer inactivity 300
Example: Configuring the Router as an IP SLA TWAMP Reflector
Router(config)# ip sla responder twamp
Router(config-twamp-srvr)# timeout 300
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
23-9
Chapter 23
Cisco IOS IP SLA
Two-Way Active Measurement Protocol
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
23-10
OL-23826-09
CH A P T E R
24
Configuring QoS
This chapter describes how to configure quality of service (QoS) by using the modular QoS CLI (MQC)
on the Cisco ASR 901 router. With QoS, you can provide preferential treatment to certain types of traffic
at the expense of others. When QoS is not configured, the router offers the best-effort service to each
packet, regardless of the packet contents or size. It sends the packets without any assurance of reliability,
delay bounds, or throughput. MQC provides a comprehensive hierarchical configuration framework for
prioritizing or limiting specific streams of traffic.
Note
IPv6 QoS is supported only from Cisco IOS Release 15.2(2)SNG onwards.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for Configuring QoS” section on page 24-88.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Understanding QoS, page 24-2
•
Configuring Quality of Service (QoS), page 24-25
•
QoS Treatment for Performance-Monitoring Protocols, page 24-62
•
Additional References, page 24-87
•
Feature Information for Configuring QoS, page 24-88
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-1
Chapter 24
Configuring QoS
Understanding QoS
Understanding QoS
Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority
and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an
equal chance of being dropped.
When you configure the QoS feature, you can select specific network traffic, prioritize it according to
its relative importance, and use traffic-management techniques to provide preferential treatment.
Implementing QoS in your network makes network performance more predictable and bandwidth
utilization more effective.
Figure 24-1 shows the MQC model.
Modular QoS CLI Model
Classification
Policing
Marking
Policer
Drops
Congestion
Avoidance
Congestion
Drops
Queuing
141149
Figure 24-1
Scheduling
Basic QoS includes these actions.
•
Packet classification organizes traffic on the basis of whether or not the traffic matches a specific
criteria. When a packet is received, the router identifies all key packet fields: class of service (CoS),
Differentiated Services Code Point (DSCP), or IP precedence. The router classifies the packet based
on this content or based on an access-control list lookup. For more information, see the
“Classification” section on page 24-7.
•
Packet policing determines whether a packet is in or out of profile by comparing the rate of the
incoming traffic to the configured policer. You can control the traffic flow for packets that conform
to or exceed the configured policer. You can configure a committed information rate (CIR) and peak
information rate (PIR) and set actions to perform on packets that conform to the CIR and PIR
(conform-action), packets that conform to the PIR, but not the CIR (exceed-action), and packets that
exceed the PIR value (violate-action). For more information, see the “Policing” section on
page 24-14.
•
Packet prioritization or marking evaluates the classification and policer information to determine the
action to take. All packets that belong to a classification can be remarked. When you configure a
policer, packets that meet or exceed the permitted bandwidth requirements (bits per second) can be
conditionally passed through, dropped, or reclassified. For more information, see the “Marking”
section on page 24-18.
•
Congestion management uses queuing and scheduling algorithms to queue and sort traffic that is
leaving a port. The router supports these scheduling and traffic-limiting features: class-based
weighted fair queuing (CBWFQ), class-based traffic shaping, port shaping, and class-based priority
queuing. You can provide guaranteed bandwidth to a particular class of traffic while still servicing
other traffic queues. For more information, see the “Congestion Management and Scheduling”
section on page 24-19.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-2
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Default QoS for Traffic from External Ethernet Ports
The Cisco ASR 901 router allows complete configuration of QoS via policy-maps for the external
ethernet ports. However, the default case when no policy-map is configured is described below:
By default, the qos-group (internal-priority) applied to every packet from an external port is zero.
In cases where Cisco ASR 901 router configuration causes fields to be generated that were not present
on the incoming packet, (for example, if a VLAN tag or an MPLS label is added by Cisco ASR 901 that
was not present on the incoming packet) the router uses the following default procedures to propagate
the priority from the received frame as described below:
a.
In the absence of a policy-map, when adding an 802.1Q VLAN outer tag (service tag) when a service
tag was not previously present, the priority value in outer tag is zero. The priority of the inner tag
(if present) is not modified from its original value.
b.
When adding an 802.1Q VLAN inner tag (customer tag), the default priority value for the inner tag
is zero.
c.
The default QoS-group, used for internal prioritization, output queuing and shaping, and for
propagating QoS information to MPLS EXP, is zero.
d.
For tunneling technologies, such as EoMPLS pseudowires and L3VPN, additional defaults are in
place to propagate QoS. These are described below:
Default QoS for Traffic from Internal Ports
The Cisco ASR 901 router does not allow policy maps to be applied to internal ports, such as the
Ethernet or PCI ports to the CPU, nor the Ethernet ports to the timing CPU or the Winpath.
Cisco ASR 901 router generally treats these internal ports as trusted. The Cisco ASR 901 Series
Aggregation Services Router defaults to propagate the priority from the received frame as described
below:
a.
By default, the QoS-group (internal-priority) applied to every packet from an internal port is equal
to the priority received in the 802.1Q VLAN tag received on that packet.
b.
If a packet is received on one of these internal interfaces which does not have a VLAN tag attached,
a VLAN tag is added internally, with the priority value copied from the ip-precedence field (in case
of IP packets), and zero (in case on non-ip packets).
c.
The default QoS-group, (internal priority) for internal queue assignment and for propagating QoS
information to MPLS EXP, is set equal to the priority of the outer VLAN tag (either the original or
the default value) on the received frame.
d.
For tunneling technologies, such as EoMPLS pseudowires and L3VPN, additional defaults are in
place to propagate QOS as follows:
– For MPLS based L3 VPN and for the EoMPLS (both VPWS and VPLS), upon imposition of the
first (bottom of stack) MPLS label, MPLS EXP values are equal to the value is specified in the
internal qos-group setting (internal priority).
– When adding additional MPLS label to an existing stack, the default MPLS EXP values are set
to match qos-group value.
This section contains the following topics:
•
Modular QoS CLI, page 24-4
•
Input and Output Policies, page 24-5
•
Classification, page 24-7
•
Table Maps, page 24-13
•
Policing, page 24-14
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-3
Chapter 24
Configuring QoS
Understanding QoS
•
Marking, page 24-18
•
Congestion Management and Scheduling, page 24-19
•
Configuring Quality of Service (QoS), page 24-25
Modular QoS CLI
Modular QoS CLI (MQC) allows users to create traffic policies and attach these policies to interfaces.
A traffic policy contains a traffic class and one or more QoS features. Use a traffic class to classify traffic,
and the QoS features in the traffic policy determine how to treat the classified traffic.
Complete the following steps to configure Modular QoS CLI:
Step 1
Define a traffic class.
Use the class-map [match-all | match-any] class-map-name global configuration command to define a
traffic class and to enter class-map configuration mode. A traffic class contains three elements: a name,
an instruction on how to evaluate the configured match commands (if more than one match command is
configured in the class map), and a series of match commands
•
Name the traffic class in the class-map command line to enter class-map configuration mode.
•
You can optionally include keywords to evaluate these match commands by entering class-map
match-any or class-map match-all. If you specify match-any, the traffic being evaluated must
match one of the specified criteria. If you specify match-all, the traffic being evaluated must match
all of the specified criteria. A match-all class map can contain only one match statement, but a
match-any class map can contain multiple match statements.
Note
•
Step 2
If you do not enter match-all or match-any, the default is to match all.
Use the match class-map configuration commands to specify criteria for classifying packets. If a
packet matches the specified criteria, that packet is considered a member of the class and is
forwarded according to the QoS specifications set in the traffic policy. Packets that fail to meet any
of the matching criteria are classified as members of the default traffic class.
Create a traffic policy to associate the traffic class with one or more QoS features.
Use the policy-map policy-map-name global configuration command to create a traffic policy and to
enter policy-map configuration mode. A traffic policy defines the QoS features to associate with the
specified traffic class. A traffic policy contains three elements: a name, a traffic class (specified with the
class policy-map configuration command), and the QoS policies configured in the class.
Note
•
Name the traffic policy in the policy-map command line to enter policy-map configuration mode.
•
In policy-map configuration mode, enter the name of the traffic class used to classify traffic to the
specified policy, and enter policy-map class configuration mode.
•
In policy-map class configuration mode, you can enter the QoS features to apply to the classified
traffic. These include using the set, police, or police aggregate commands for input policy maps or
the bandwidth, priority, or shape average commands for output policy maps.
A packet can match only one traffic class within a traffic policy. If a packet matches more than one traffic
class in the traffic policy, the first traffic class defined in the policy is used. To configure more than one
match criterion for packets, you can associate multiple traffic classes with a single traffic policy.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-4
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Step 3
Attach the traffic policy to an interface.
Use the service-policy interface configuration command to attach the policy map to an interface for
packets entering or leaving the interface. You must specify whether the traffic policy characteristics
should be applied to incoming or outgoing packets. For example, entering the service-policy output
class1 interface configuration command attaches all the characteristics of the traffic policy named class1
to the specified interface. All packets leaving the specified interface are evaluated according to the
criteria specified in the traffic policy named class1.
Note
If you enter the no policy-map configuration command or the no policy-map policy-map-name global
configuration command to delete a policy map that is attached to an interface, a warning message
appears that lists any interfaces from which the policy map is being detached. For example:
Warning: Detaching Policy test1 from Interface GigabitEthernet0/1
The policy map is then detached and deleted.
Input and Output Policies
Policy maps are either input policy maps or output policy maps, attached to packets as they enter or leave
the router by service policies applied to interfaces. Input policy maps perform policing and marking on
received traffic. Policed packets can be dropped or reduced in priority (marked down) if they exceed the
maximum permitted rates. Output policy maps perform scheduling and queuing on traffic as it leaves the
router.
Input policies and output policies have the same basic structure; the difference is in the characteristics
that they regulate. Figure 24-2 shows the relationship of input and output policies.
You can configure a maximum of 32 policy maps.
You can apply one input policy map and one output policy map to an interface.
Input and Output Policy Relationship
Apply
output
policy
Apply
input
policy
Ingress
port
Switching
and
forwarding
Egress
port
Apply
input
policy
Apply
output
policy
141150
Figure 24-2
Input Policy Maps
Input policy map classification criteria include matching a CoS, a DSCP, or an IP precedence value or
VLAN ID (for per-port, per-VLAN QoS). Input policy maps can have any of these actions:
•
Setting or marking a CoS, a DSCP, an IP precedence, or QoS group value
•
Individual policing
•
Aggregate policing
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-5
Chapter 24
Configuring QoS
Understanding QoS
Only input policies provide matching on VLAN IDs, and only output policies provide matching on QoS
groups. You can assign a QoS group number in an input policy and match it in the output policy. The
class class-default is used in a policy map for any traffic that does not explicitly match any other class
in the policy map. Input policy maps do not support queuing and scheduling keywords, such as
bandwidth, priority, and shape average.
An input policy map can have a maximum of 64 classes plus class-default. You can configure a
maximum of 64 classes in an input policy.
Output Policy Maps
Output policy map classification criteria include matching a CoS, a DSCP, an IP precedence, or a QoS
group value. Output policy maps support scheduling (of bandwidth, priority, and shape average)
Output policy maps do not support matching of access groups. You can use QoS groups as an alternative
by matching the appropriate access group in the input policy map and setting a QoS group. In the output
policy map, you can then match the QoS group. For more information, see the “Classification Based on
QoS Groups” section on page 24-11.
Output policies do not support policing (except in the case of priority with policing).
The class class-default is used in a policy map for any traffic that does not explicitly match any other
class in the policy map.
An output policy map attached to an egress port can match only the packets that have already been
matched by an input policy map attached to the ingress port for the packets. You can attach an output
policy map to any or all ports on the router. The router supports configuration and attachment of a unique
output policy map for each port. There are no limitations on the configurations of bandwidth, priority,
or shaping.
Access Control Lists
The Cisco IOS Release 15.2(2)SNH1 introduces support for access control list (ACL) based QoS on the
Cisco ASR 901 router. This feature provides classification based on source and destination IP. The
current implementation of this feature supports only named ACLs.
ACLs are an ordered set of filter rules. Each rule is a permit or a deny statement known as access control
entries (ACEs). They filter network traffic by forwarding or blocking routed packets at the interface of
the router. The router examines each packet to determine whether to forward or drop the packet based
on the criteria specified within the access list.
The permit and deny statements are not applicable when ACLs are used as part of ACL-based QoS. ACLs
are used only for traffic classification purposes as part of QoS.
Restrictions
•
Loopback feature should not be enabled when Layer 2 Control Protocol Forwarding is enabled.
•
Following IOS keywords are not supported on Cisco ASR 901 router—match-any, ip-options,
logging, icmp-type/code, igmp type, dynamic, reflective, evaluate.
•
Ingress PACL and RACL supports TCP/UDP port range; Egress ACL does not support port range.
•
Sharing access lists across interfaces is not supported.
•
ACL is not supported on Management port (FastEthernet) and serial interfaces.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-6
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
•
Devices in the management network (network connected to Fast Ethernet port) cannot be accessed
from any other port. If the default route is configured on Cisco ASR 901 to fast ethernet interface
(Fa0/0), all the routed packets will be dropped. However, this configuration could keep CPU busy
and affect overall convergence.
Classification
Classification distinguishes one kind of traffic from another by examining the fields in the packet header.
When a packet is received, the router examines the header and identifies all key packet fields. A packet
can be classified based on the DSCP, the CoS, or the IP precedence value in the packet, or by the VLAN
ID. Figure 24-3 shows the classification information carried in a Layer 2 or a Layer 3 IP packet header,
using six bits from the deprecated IP type of service (ToS) field to carry the classification information.
•
On ports configured as Layer 2 IEEE 802.1Q trunks, all traffic is in 802.1Q frames except for traffic
in the native VLAN. Layer 2 802.1Q frame headers have a 2-byte Tag Control Information field that
carries the CoS value, called the User Priority bits, in the three most-significant bits, and the VLAN
ID value in the 12 least-significant bits. Other frame types cannot carry Layer 2 CoS values.
Layer 2 CoS values range from 0 to 7.
•
Layer 3 IP packets can carry either an IP precedence value or a DSCP value. QoS supports the use
of either value because DSCP values are backward-compatible with IP precedence values.
IP precedence values range from 0 to 7. DSCP values range from 0 to 63.
•
Output remarking is based on the Layer 2 or Layer 3 marking type, marking value and packet type.
Figure 24-3
QoS Classification Layers in Frames and Packets
Layer 2 IEEE 802.1Q and IEEE 802.1p Frame
Preamble
Start frame
delimiter
DA
SA
TAG
2 Bytes
Type
PT
Data
FCS
3 bits used for CoS
(IEEE 802.1p user priority)
PRI
CFI
VLAN ID
Layer 3 IPv4 Packet
7
ToS
1 Byte
6
5
Len
ID
4
IP precedence
Offset
3
TTL
2
Proto
1
FCS
IP-SA
IP-DA
Data
0
Flow control
for DSCP
DSCP
Standard IPv4:
MSBs called IP precedence
141151
Version
length
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-7
Chapter 24
Configuring QoS
Understanding QoS
These sections contain additional information about classification:
•
“Class Maps” section on page 24-8
•
“The match Command” section on page 24-8
•
“Classification Based on Layer 2 CoS” section on page 24-9
•
“Classification Based on IP Precedence” section on page 24-9
•
“Classification Based on IP DSCP” section on page 24-9
•
“Classification Comparisons” section on page 24-10
•
“Classification Based on QoS Groups” section on page 24-11
•
“Classification Based on VLAN IDs” section on page 24-12
Class Maps
Use an MQC class map to name a specific traffic flow (or class) and to isolate it from all other traffic. A
class map defines the criteria used to match against a specific traffic flow to further classify it. If you
wish to classify more than one type of traffic, you can create another class map and use a different name.
When you use the class-map command with a class-map name, the router enters the class-map
configuration mode. In this mode, you define the match criterion for the traffic by using the match
class-map configuration command. After a packet is matched against the class-map criteria, it is acted
on by the associated action specified in a policy map.
You can match more than one criterion for classification. You can also create a class map that requires
that all matching criteria in the class map be in the packet header by using the class map match-all
class-map name global configuration command to enter class map configuration mode.
Note
You can configure only one match entry in a match-all class map.
You can use the class map match-any class-map name global configuration command to define a
classification with any of the listed criteria.
Note
If you do not enter match-all or match-any, the default is to match all. A match-all class map cannot
have more than one classification criterion (match statement). A class map with no match condition has
a default of match all.
The match Command
To configure the type of content used to classify packets, use the match class-map configuration
command to specify the classification criteria. If a packet matches the configured criteria, it belongs to
a specific class and is forwarded according to the specified policy. For example, you can use the match
class-map command with CoS, IP DSCP, and IP precedence values. These values are referred to as
markings on a packet.
•
For an input policy map, you cannot configure an IP classification (match ip dscp, match ip
precedence, match ip acl) and a non-IP classification (match cos or match mac acl) in the same
policy map or class map.
•
In an output policy map, no two class maps can have the same classification criteria, that is, the same
match qualifiers and values.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-8
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
This example shows how to create a class map example to define a class that matches any of the listed
criteria. In this example, if a packet is received with the DSCP equal to 32 or a 40, the packet is identified
(classified) by the class map.
Router(config)# class-map match-any example
Router(config-cmap)# match ip dscp 32
Router(config-cmap)# match ip dscp 40
Router(config-cmap)# exit
Classification Based on Layer 2 CoS
You can use the match command to classify Layer 2 traffic based on the CoS value, which ranges from
0 to 7.
Note
A match cos command is supported only on Layer 2 802.1Q trunk ports.
This example shows how to create a class map to match a CoS value of 5:
Router(config)# class-map premium
Router(config-cmap)# match cos 5
Router(config-cmap)# exit
Classification Based on IP Precedence
You can classify IPv4 traffic based on the packet IP precedence values, which range from 0 to 7.
This example shows how to create a class map to match an IP precedence value of 4:
Router(config)# class-map sample
Router(config-cmap)# match ip precedence 4
Router(config-cmap)# exit
Classification Based on IP DSCP
When you classify IPv4 traffic based on IP DSCP value, and enter the match ip dscp class-map
configuration command, you have several classification options to choose from:
•
Entering a specific DSCP value (0 to 63).
•
Using the Default service, which corresponds to an IP precedence and DSCP value of 0. The default
per-hop behavior (PHB) is usually best-effort service.
•
Using Assured Forwarding (AF) by entering the binary representation of the DSCP value. AF sets
the relative probability that a specific class of packets is forwarded when congestion occurs and the
traffic does not exceed the maximum permitted rate. AF per-hop behavior provides delivery of IP
packets in four different AF classes: AF11-13 (the highest), AF21-23, AF31-33, and AF41-43 (the
lowest). Each AF class could be allocated a specific amount of buffer space and drop probabilities,
specified by the binary form of the DSCP number. When congestion occurs, the drop precedence of
a packet determines the relative importance of the packet within the class. An AF41 provides the
best probability of a packet being forwarded from one end of the network to the other.
•
Entering Class Selector (CS) service values of 1 to 7, corresponding to IP precedence bits in the ToS
field of the packet.
•
Using Expedited Forwarding (EF) to specify a low-latency path. This corresponds to a DSCP value
of 46. EF services use priority queuing to preempt lower priority traffic classes.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-9
Chapter 24
Configuring QoS
Understanding QoS
This display shows the available classification options:
Router(config-cmap)# match ip dscp ?
<0-63>
Differentiated services codepoint value
af11
Match packets with AF11 dscp (001010)
af12
Match packets with AF12 dscp (001100)
af13
Match packets with AF13 dscp (001110)
af21
Match packets with AF21 dscp (010010)
af22
Match packets with AF22 dscp (010100)
af23
Match packets with AF23 dscp (010110)
af31
Match packets with AF31 dscp (011010)
af32
Match packets with AF32 dscp (011100)
af33
Match packets with AF33 dscp (011110)
af41
Match packets with AF41 dscp (100010)
af42
Match packets with AF42 dscp (100100)
af43
Match packets with AF43 dscp (100110)
cs1
Match packets with CS1(precedence 1) dscp
cs2
Match packets with CS2(precedence 2) dscp
cs3
Match packets with CS3(precedence 3) dscp
cs4
Match packets with CS4(precedence 4) dscp
cs5
Match packets with CS5(precedence 5) dscp
cs6
Match packets with CS6(precedence 6) dscp
cs7
Match packets with CS7(precedence 7) dscp
default Match packets with default dscp (000000)
ef
Match packets with EF dscp (101110)
Note
(001000)
(010000)
(011000)
(100000)
(101000)
(110000)
(111000)
For more information on DSCP prioritization, see RFC-2597 (AF per-hop behavior), RFC-2598 (EF), or
RFC-2475 (DSCP).
Classification Comparisons
Table 24-1 shows suggested IP DSCP, IP precedence, and CoS values for typical traffic types.
Table 24-1
Typical Traffic Classifications
DSCP
per-hop
DSCP
(decimal)
IP
Precedence
CoS
Voice-bearer—traffic in a priority queue or the queue with the
highest service weight and lowest drop priority.
EF
46
5
5
Voice control—signalling traffic, related to call setup, from a
voice gateway or a voice application server.
AF31
26
3
3
Video conferencing—in most networks, video conferencing
AF41
over IP has similar loss, delay, and delay variation requirements
as voice over IP traffic.
34
4
4
Streaming video—relatively high bandwidth applications with a AF13
high tolerance for loss, delay, and delay variation. Usually
considered more important than regular background
applications such as e-mail and web browsing.
14
1
1
18
20
22
2
2
2
2
2
2
Traffic Type
Mission critical date (gold data)—delay-sensitive applications
critical to the operation of an enterprise.
•
Level 1
•
Level 2
•
Level 3
AF21
AF22
AF23
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-10
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Table 24-1
Typical Traffic Classifications (continued)
Traffic Type
DSCP
per-hop
DSCP
(decimal)
IP
Precedence
CoS
AF11
AF12
AF13
10
12
14
1
1
1
1
1
1
Default
0
0
0
2
4
6
0
0
0
0
0
0
Less critical data (silver data)—noncritical, but relatively
important data.
•
Level 1
•
Level 2
•
Level 3
Best-effort data (bronze data)—other traffic, including all
noninteractive traffic, regardless of importance.
Less than best-effort data—noncritical, bandwidth-intensive
data traffic given the least preference. This is the first traffic type
to be dropped.
•
Level 1
•
Level 2
•
Level 3
Classification Based on QoS Groups
A QoS group is an internal label used by the router to identify packets as a members of a specific class.
The label is not part of the packet header and is restricted to the router that sets the label. QoS groups
provide a way to tag a packet for subsequent QoS action without explicitly marking (changing) the
packet.
A QoS group is identified at ingress and used at egress; it is assigned in an input policy to identify
packets in an output policy. See Figure 24-3. The QoS groups help aggregate different classes of input
traffic for a specific action in an output policy.
QoS Groups
1. Classify traffic
2. Set qos-group
Switching
functions
1. Match qos-group
2. Output policy
141152
Figure 24-4
You can use QoS groups to aggregate multiple input streams across input classes and policy maps for the
same QoS treatment on the egress port. Assign the same QoS group number in the input policy map to
all streams that require the same egress treatment, and match to the QoS group number in the output
policy map to specify the required queuing and scheduling actions.
You can also use QoS groups to identify traffic entering a particular interface if the traffic must be treated
differently at the output based on the input interface.
You can use QoS groups to configure per-port, per-VLAN QoS output policies on the egress interface
for bridged traffic on the VLAN. Assign a QoS group number to a VLAN on the ingress interface by
configuring a per-port, per-VLAN input policy. Then use the same QoS-group number for classification
at the egress. Because the VLAN of bridged traffic does not change during forwarding through the router,
the QoS-group number assigned to the ingress VLAN can be used on the egress interface to identify the
same VLAN.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-11
Chapter 24
Configuring QoS
Understanding QoS
You can independently assign QoS-group numbers at the ingress to any combination of interfaces,
VLANs, traffic flows, and aggregated traffic. To assign QoS-group numbers, configure a QoS group
marking in an input policy map, along with any other marking or policing actions required in the input
policy map for the same service class. This allows the input marking and policing functions to be
decoupled from the egress classification function if necessary because only the QoS group must be used
for egress classification.
This example identifies specific packets as part of QoS group 1 for later processing in an output policy:
Router(config)# policy-map in-gold-policy
Router(config-pmap)# class in-class1
Router(config-pmap-c)# set qos-group 1
Router(config-cmap-c)# exit
Router(config-cmap)# exit
Use the set qos-group command only in an input policy. The assigned QoS group identification is
subsequently used in an output policy with no mark or change to the packet. Use the match qos-group
in the output policy.
Note
You cannot configure match qos-group for an input policy map.
This example creates an output policy to match the QoS group created in the input policy map
in-gold-policy. Traffic internally tagged as qos-group 1 is identified and processed by the output policy.
Router(config)# class-map out-class1
Router(config-cmap)# match qos-group 1
Router(config-cmap)# exit
Classification Based on VLAN IDs
With classification based on VLAN IDs, you can apply QoS policies to frames carried on a
user-specified VLAN for a given interface. Per-VLAN classification is not required on access ports
because access ports carry traffic for a single VLAN.
The router supports two policy levels: a parent level and a child level. With the QoS parent-child
structure, you can reference a child policy in a parent policy to provide additional control of a specific
traffic type. For per-port, per-VLAN QoS, the parent-level class-default matches the VLAN; match
criteria is defined by the service instance encapsulation. You cannot configure multiple service classes
at the parent level to match different combinations of VLANs.
Note
A per-port, per-VLAN parent-level class map supports only class class-default; it should be configured
with single rate policer. A flat policy can have multiple classes with match vlan and any action.
Note
You can configure only class-default in the parent level of a per-port, per-VLAN hierarchical policy map.
In this example, the class maps in the child-level policy map specify matching criteria for voice, data,
and video traffic, and the child policy map sets the action for input policing each type of traffic. The
parent-level policy map specifies the VLANs to which the child policy maps are applied on the specified
port.
Router(config)# class-map match-any dscp-1 data
Router(config-cmap)# match ip dscp 1
Router(config-cmap)# exit
Router(config)# class-map match-any dscp-23 video
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-12
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Router(config-cmap)# match ip dscp 23
Router(config-cmap)# exit
Router(config)# class-map match-any dscp-63 voice
Router(config-cmap)# match ip dscp-63
Router(config-cmap)# exit
Router(config)# policy-map customer-1-ingress
Router(config-pmap)# class class-default
Router(config-pmap-c)# service-policy child_policy-1
Note
You can also enter the match criteria as match vlan 100 200 300 in the child-level policy-map.
Router(config)# policy-map child policy-1
Router(config-pmap)# class dscp-63 voice
Router(config-pmap-c)# police cir 10000000 bc 50000
Router(config-pmap-c)# conform-action set-cos-transmit 5
Router(config-pmap-c)# exceed-action drop
Router(config-pmap-c)# exit
Router(config-pmap)# class dscp-1 data
Router(config-pmap-c)# set cos 0
Router(config-pmap-c)# exit
Router(config-pmap)# class dscp-23 video
Router(config-pmap-c)# set cos 4
Router(config-pmap-c)# set ip precedence 4
Router(config-pmap-c)# exit
Router(config)# interface gigabitethernet0/1
Router(config-if)# service instance 100 ethernet
Router(config-if)# encapsulation dot1q 100
Router(config-if)# service-policy input customer-1-ingress
Router(config-if)# rewrite ingress tag pop 1 symmetric
Router(config-if)# bridge-domain 100
Table Maps
You can use table maps to manage a large number of traffic flows with a single command. You can
specify table maps in set commands and use them as mark-down mapping for the policers. You can also
use table maps to map an incoming QoS marking to a replacement marking without having to configure
a large number of explicit matches and sets. Table maps are used only in input policy maps.
Table maps can be used to:
•
Correlate specific CoS, DSCP, or IP precedence values to specific CoS, DSCP, or IP precedence
values
•
Mark down a CoS, DSCP, or IP precedence value
•
Assign defaults for unmapped values
This example creates a table to map specific CoS values to DSCP values. The unspecified values are all
mapped to a to-value of 0.
Router(config)# table-map cos-dscp-tablemap
Router(config-tablemap)# map from 5 to 46
Router(config-tablemap)# map from 6 to 56
Router(config-tablemap)# map from 7 to 57
Router(config-tablemap)# exit
The Cisco ASR 901 router supports a maximum of 32 unique table maps. You can enter up to 64
different map from–to entries in a table map. These table maps are supported on the router:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-13
Chapter 24
Configuring QoS
Understanding QoS
•
Cos to Qos-group
•
Qos-group to mpls experimental topmost
Table maps modify only one parameter (CoS, IP precedence, or DSCP, whichever is configured) and are
only effective when configured with a set command in a policy map.
Policing
After a packet is classified, you can use policing as shown in Figure 24-5 to regulate the class of traffic.
The policing function limits the amount of bandwidth available to a specific traffic flow or prevents a
traffic type from using excessive bandwidth and system resources. A policer identifies a packet as in or
out of profile by comparing the rate of the inbound traffic to the configuration profile of the policer and
traffic class. Packets that exceed the permitted average rate or burst rate are out of profile or
nonconforming. These packets are dropped or modified (marked for further processing), depending on
the policer configuration.
Policing is used primarily on receiving interfaces. You can attach a policy map with a policer only in an
input service policy. The only policing allowed in an output policy map is in priority classes. See the
“Unconditional Priority Policing” section on page 24-16.
Figure 24-5
Receive
Policing of Classified Packets
Packets that conform
to the committed
information rate (CIR)
Classify
Queuing,
scheduling,
and shaping
An exceed-action at this
point results in dropped
or reclassified packets.
Drop
141153
Packets that exceed
the CIR
This section contains the following topics:
•
Individual Policing, page 24-15
•
Unconditional Priority Policing, page 24-16
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-14
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Individual Policing
Individual policing applies only to input policy maps. In policy-map configuration mode, use the class
command followed by class-map name, and enter policy-map class configuration mode. Effective with
Cisco IOS Release 15.3(3)S, the Cisco ASR 901 supports policing ingress traffic over the cross connect
EVC, similar to bridge domain service policy.
Use the police policy-map class configuration command to define the policer, the committed rate
limitations of the traffic, committed burst size limitations of the traffic, and the action to take for a class
of traffic that is below the limits (conform-action) and above the limits (exceed-action). If you do not
specify burst size (bc), the system calculates an appropriate burst size value. The calculated value is
appropriate for most applications.
To make the policy map effective, attach it to a physical port by using the service-policy input interface
configuration command. Policing is done only on received traffic, so you can only attach a policer to an
input service policy.
Note
The QoS-group precedes the CoS value that is matched in the class-map, when the set qos-group
command is used along with MPLS experimental imposition.
Restrictions
•
Only byte counters are supported.
•
Only drop and pass counters are supported.
•
If an ingress cross connect policer is attached to a physical interface, an ingress cross connect policer
cannot be attached to EVC’s under the specific physical port.
•
Applying or removing the policy-map on a cross connect interface requires shutdown or no
shutdown on the interface.
•
User class based MPLS experimental imposition is supported only for user classes based on CoS
match.
•
Supports policy-map on 254 ingress cross connect interfaces only.
•
Dynamic modification of policy-maps (modifying a policy-map or class-map while it is attached to
an interface) is not supported for the policy-maps applied on cross connect.
Configuration Examples
The following is a sample configuration of basic policing for all traffic received with a CoS of 4. The
first value following the police command limits the average traffic rate to 10, 000,000 bits per second
(bps); the second value represents the additional burst size (10 kilobytes). The policy is assigned to
gigabitethernet port 1.
Router(config)# class-map video-class
Router(config-cmap)# match cos 4
Router(config-cmap)# exit
Router(config)# policy-map video-policy
Router(config-pmap)# class video-class
Router(config-pmap-c)# police 10000000 10000
Router(config-pmap-c-police)# exit
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet0/1
Router(config-if)# service-policy input video-policy
Router(config-if)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-15
Chapter 24
Configuring QoS
Understanding QoS
The following is a sample configuration of policing ingress traffic over cross connect EVC.
Router(config)# interface GigabitEthernet0/3
Router(config-if)# service instance 22 ethernet
Router(config-if-svr)# encapsulation dot1q 22
Router(config-if-svr)# rewrite ingress tag pop 1 symmetric
Router(config-if-svr)# xconnect 1.1.1.1 100 encapsulation mpls
Router(config-if-svr)# service-policy input policy1
Router(config-if-svr)# exit
You can use the conform-action and exceed-action policy-map class configuration commands or the
conform-action and exceed-action policy-map class police configuration commands to specify the
action to be taken when the packet conforms to or exceeds the specified traffic rate.
Conform actions are to send the packet without modifications, to set a new CoS, DSCP, or IP precedence
value, or to set a QoS group value for classification at the egress. Exceed actions are to drop the packet,
to send the packet without modification, to set a new CoS, DSCP, or IP precedence to a value, or to set
a QoS group value for classification at the egress.
You can configure each marking action by using explicit values, table maps, or a combination of both.
Table maps list specific traffic attributes and map (or convert) them to other attributes.
You can configure multiple conform and exceed actions simultaneously for each service class.
After you create a table map, configure a policy-map policer to use the table map.
Note
In Cisco ASR 901, the from–type action in the table map must be cos.
To configure multiple actions in a class, you can enter multiple conform or exceed action entries in
policy-map class police configuration mode, as in this example:
Router(config)# policy-map map1
Router(config-pmap)# class class1
Router(config-pmap-c)# police 100000 500000
Router(config-pmap-c-police)# conform-action set-cos-transmit 4
Router(config-pmap-c-police)# conform-action set-qos-transmit 4
Router(config-pmap-c-police)# exceed-action set-cos-transmit 2
Router(config-pmap-c-police)# exceed-action set-qos-transmit 2
Router(config-pmap-c-police)# exit
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Unconditional Priority Policing
Priority policing applies only to output policy maps. You can use the priority policy-map class
configuration command in an output policy map to designate a low-latency path, or class-based priority
queuing, for a specific traffic class. With strict priority queuing, the packets in the priority queue are
scheduled and sent until the queue is empty, at the expense of other queues. Excessive use of
high-priority queuing can create congestion for lower priority traffic.
To eliminate this congestion, you can use priority with implicit policer (priority policing) to reduce the
bandwidth used by the priority queue and allocate traffic rates on other queues. Priority with police is
the only form of policing supported in output policy maps.
Note
You cannot configure a policer committed burst size for an unconditional priority policer. Any
configured burst size is ignored.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-16
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
This example shows how to use the priority percent command to configure out-class1 as the priority
queue, with traffic going to the queue limited to 20,000,000 bps so that the priority queue never uses
more than that. Traffic above that rate is dropped. This allows other traffic queues to receive some port
bandwidth, in this case a minimum bandwidth guarantee of 50% and 20%. The class class-default queue
gets the remaining port bandwidth.
Router(config)# policy-map policy1
Router(config-pmap)# class out-class1
Router(config-pmap-c)# priority percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# class out-class2
Router(config-pmap-c)# bandwidth percent 50
Router(config-pmap-c)# exit
Router(config-pmap)# class out-class3
Router(config-pmap-c)# bandwidth percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet0/1
Router(config-if)# service-policy output policy1
Router(config-if)# exit
Egress Policing
Egress policing can be classified based on QoS-groups, DSCP, and precedence value. For QoS-groups
to work at egress, you should map the traffic at ingress to a specific QoS-group value.
Restrictions
•
Egress policing is supported only on the physical interface (policy-maps are applied only at port
level).
•
Egress policing on EVC is not supported.
•
Egress policing supports up to 64 policers.
•
Only byte counters are supported.
•
Only drop and pass counters are supported.
•
Policing and queuing are not supported together in a policy-map.
•
Hierarchical egress policing is not supported.
Configuration Example
This is an example for egress policing on a physical interface:
class-map match-all dscp1
match ip dscp 1
class-map match-all Q1
match qos-group 1
policy-map ingress
class dscp1
set qos-group 1
policy-map egress
class Q1
police cir 5000000
int gig 0/1
service-policy input ingress
int gig 0/0
service-policy output egress
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-17
Chapter 24
Configuring QoS
Understanding QoS
Marking
You can use packet marking in input policy maps to set or modify the attributes for traffic belonging to
a specific class. After network traffic is organized into classes, you use marking to identify certain traffic
types for unique handling. For example, you can change the CoS value in a class or set IP DSCP or IP
precedence values for a specific type of traffic. These new values are then used to determine how the
traffic should be treated. You can also use marking to assign traffic to a QoS group within the router.
Traffic marking is typically performed on a specific traffic type at the ingress port. The marking action
can cause the CoS, DSCP, or precedence bits to be rewritten or left unchanged, depending on the
configuration. This can increase or decrease the priority of a packet in accordance with the policy used
in the QoS domain so that other QoS functions can use the marking information to judge the relative and
absolute importance of the packet. The marking function can use information from the policing function
or directly from the classification function.
You can specify and mark traffic by using the set commands in a policy map for all supported QoS
markings (CoS, IP DSCP, IP precedence, and QoS groups). A set command unconditionally marks the
packets that match a specific class. You then attach the policy map to an interface as an input policy map.
You can also mark traffic by using the set command with table maps. Table maps list specific traffic
attributes and maps (or converts) them to another attribute. A table map establishes a to-from
relationship for the attribute and defines the change to be made.
You can simultaneously configure actions to modify DSCP, precedence, and COS markings in the packet
for the same service along with QoS group marking actions. You can use the QoS group number defined
in the marking action for egress classification.
Note
When you use a table map in an input policy map, the protocol type of the from-type action in the table
map must be the same as the protocol type of the associated classification. If the class map represents a
non-IP classification, the from-type action in the table map must be cos.
Note
Cisco ASR 901 transparently preserves the ECN bits while marking DSCP.
After you create a table map, configure a policy map to use the table map. See the “Congestion
Management and Scheduling” section on page 24-19. Figure 24-6 shows the steps for marking traffic.
Receive
Marking of Classified Traffic
Classify
Unconditionally
mark traffic for
reclassification
Queuing,
scheduling,
and shaping
157193
Figure 24-6
This example uses a policy map to remark a packet. The first marking (the set command) applies to the
QoS default class map that matches all traffic not matched by class AF31-AF33 and sets all traffic to an
IP DSCP value of 1. The second marking sets the traffic in classes AF31 to AF33 to an IP DSCP of 3.
Router(config)# policy-map Example
Router(config-pmap)# class class-default
Router(config-pmap-c)# set ip dscp 1
Router(config-pmap-c)# exit
Router(config-pmap)# class AF31-AF33
Router(config-pmap-c)# set ip dscp 3
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-18
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Router(config)# interface gigabitethernet0/1
Router(config-if)# service-policy input Example
Router(config-if)# exit
Congestion Management and Scheduling
Cisco Modular QoS CLI (MQC) provides several related mechanisms to control outgoing traffic flow.
They are implemented in output policy maps to control output traffic queues. The scheduling stage holds
packets until the appropriate time to send them to one of the four traffic queues. Queuing assigns a packet
to a particular queue based on the packet class. You can use different scheduling mechanisms to provide
a guaranteed bandwidth to a particular class of traffic while also serving other traffic in a fair way. You
can limit the maximum bandwidth that can be consumed by a particular class of traffic and ensure that
delay-sensitive traffic in a low latency queue is sent before traffic in other queues.
The Cisco ASR 901 router supports these scheduling mechanisms:
•
Traffic shaping
Use the shape average policy map class configuration command to specify that a class of traffic
should have a maximum permitted average rate. You specify the maximum rate in bits per second.
•
Class-based-weighted-fair-queuing (CBWFQ)
Use the bandwidth policy-map class configuration command to control the bandwidth allocated to
a specific class. Minimum bandwidth can be specified as percentage.
•
Priority queuing or class-based priority queuing
Use the priority policy-map class configuration command to specify the priority of a type of traffic
over other types of traffic. You can specify strict priority for the high-priority traffic and allocate any
excess bandwidth to other traffic queues, or specify priority with unconditional policing of
high-priority traffic and allocate the known remaining bandwidth among the other traffic queues.
– To configure strict priority, use only the priority policy-map class configuration command to
configure the priority queue. Use the bandwidth remaining percent policy-map class
configuration command for the other traffic classes to allocate the excess bandwidth in the
desired ratios.
– To configure priority with unconditional policing, configure the priority queue by using the
priority policy-map class configuration command and the police policy-map class
configuration command to unconditionally rate-limit the priority queue. In this case, you can
configure the other traffic classes with bandwidth or shape average, depending on
requirements.
These sections contain additional information about scheduling:
•
Traffic Shaping, page 24-19
•
Class-Based Weighted Fair Queuing, page 24-21
•
Priority Queuing, page 24-23
Traffic Shaping
Traffic shaping is a traffic-control mechanism similar to traffic policing. While traffic policing is used
in input policy maps, traffic shaping occurs as traffic leaves an interface. The router can apply
class-based shaping to classes of traffic leaving an interface and port shaping to all traffic leaving an
interface. Configuring a queue for traffic shaping sets the maximum bandwidth or peak information rate
(PIR) of the queue.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-19
Chapter 24
Configuring QoS
Understanding QoS
Note
Effective with Cisco IOS Release 15.2(2)SNI, the lower limit of the committed burst size (bc) is 1 ms.
Class-Based Shaping
Class-based shaping uses the shape average policy-map class configuration command to limit the rate
of data transmission as the number of bits per second to be used for the committed information rate for
a class of traffic. The router supports separate queues for three classes of traffic. The fourth queue is
always the default queue for class class-default, unclassified traffic.
Note
In the Cisco ASR 901 router, configuring traffic shaping automatically sets the minimum bandwidth
guarantee or committed information rate (CIR) of the queue to the same value as the PIR.
This example shows how to configure traffic shaping for outgoing traffic on a gigabitethernet port so that
outclass1, outclass2, and outclass3 get a maximum of 50, 20, and 10 Mbps, respectively, of the available
port bandwidth. The class class-default at a minimum gets the remaining bandwidth.
Router(config)# policy-map out-policy
Router(config-pmap)# class classout1
Router(config-pmap-c)# shape average 50000000
Router(config-pmap-c)# exit
Router(config-pmap)# class classout2
Router(config-pmap-c)# shape average 20000000
Router(config-pmap-c)# exit
Router(config-pmap)# class classout3
Router(config-pmap-c)# shape average 10000000
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet 0/1
Router(config-if)# service-policy output out-policy
Router(config-if)# exit
Port Shaping
To configure port shaping (a transmit port shaper), create a policy map that contains only a default class,
and use the shape average command to specify the maximum bandwidth for a port.
This example shows how to configure a policy map that shapes a port to 90 Mbps, allocated according
to the out-policy policy map configured in the previous example. The service-policy policy map class
command is used to create a child policy to the parent:
Router(config)# policy-map out-policy-parent
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 90000000
Router(config-pmap-c)# service-policy out-policy
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet0/1
Router(config-if)# service-policy output out-policy-parent
Router(config-if)# exit
Parent-Child Hierarchy
The router also supports parent policy levels and child policy levels for traffic shaping. The QoS
parent-child structure is used for specific purposes where a child policy is referenced in a parent policy
to provide additional control of a specific traffic type.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-20
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
The first policy level, the parent level, is used for port shaping, and you can specific only one class of
type class-default within the policy. This is an example of a parent-level policy map:
Router(config)# policy-map parent
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 50000000
Router(config-pmap-c)# exit
The second policy level, the child level, is used to control a specific traffic stream or class, as in this
example:
Router(config)# policy-map child
Router(config-pmap)# class class1
Router(config-pmap-c)# priority
Router(config-pmap-c)# exit
Note
The total of the minimum bandwidth guarantees (CIR) for each queue of the child policy cannot exceed
the total port-shape rate.
This is an example of a parent-child configuration:
Router(config)# policy-map parent
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 50000000
Router(config-pmap-c)# service-policy child
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet0/1
Router(config-if)# service-policy output parent
Router(config-if)# exit
Class-Based Weighted Fair Queuing
You can configure class-based weighted fair queuing (CBWFQ) to set the relative precedence of a queue
by allocating a portion of the total bandwidth that is available for the port. Use the bandwidth
policy-map class configuration command to set the output bandwidth for a class of traffic as a percentage
of total bandwidth, or a percentage of remaining bandwidth.
Note
When you configure bandwidth in a policy map, you must configure all rates in the same format. The
total of the minimum bandwidth guarantees (CIR) for each queue of the policy cannot exceed the total
speed of the parent.
•
Note
When you use the bandwidth policy-map class configuration command to configure a class of
traffic as a percentage of total bandwidth, it represents the minimum bandwidth guarantee (CIR) for
that traffic class. This means that the traffic class gets at least the bandwidth indicated by the
command, but is not limited to that bandwidth. Any excess bandwidth on the port is allocated to each
class in the same ratio in which the CIR rates are configured.
You cannot configure bandwidth as a percentage of total bandwidth when strict priority (priority
without police) is configured for another class in the output policy.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-21
Chapter 24
Configuring QoS
Understanding QoS
•
Note
Note
When you use the bandwidth policy-map class configuration command to configure a class of
traffic as a percentage of total bandwidth, it represents the portion of the excess bandwidth of the
port that is allocated to the class. This means that the class is allocated bandwidth only if there is
excess bandwidth on the port, and if there is no minimum bandwidth guarantee for this traffic class.
You can configure bandwidth as percentage of remaining bandwidth only when strict priority
(priority without police) is configured for another class in the output policy map.
You cannot configure bandwidth and traffic shaping (shape average) or priority queuing (priority) for
the same class in an output policy map.
This example shows how the classes outclass1, outclass2, and outclass3 and class-default get a
minimum of 40%, 20%, 10%, and 10% of the total bandwidth. Any excess bandwidth is divided among
the classes in the same proportion as rated in the CIR.
Router(config)# policy-map out-policy
Router(config-pmap)# class outclass1
Router(config-pmap-c)# bandwidth percent 40
Router(config-pmap-c)# exit
Router(config-pmap)# class outclass2
Router(config-pmap-c)# bandwidth percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# class outclass3
Router(config-pmap-c)# bandwidth percent 10
Router(config-pmap-c)# exit
Router(config-pmap)# class class-default
Router(config-pmap-c)# bandwidth percent 10
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet 0/1
Router(config-if)# service-policy output out-policy
Router(config-if)# exit
Note
When you configure CIR bandwidth for a class as a percentage of the total bandwidth, any excess
bandwidth remaining after servicing the CIR of all the classes in the policy map, is divided among the
classes in the same proportion as the CIR rates. If the CIR rate of a class is configured as 0, that class is
also not eligible for any excess bandwidth and as a result receives no bandwidth.
This example shows how to allocate the excess bandwidth among queues by configuring bandwidth for
a traffic class as a percentage of remaining bandwidth. The class outclass1 is given priority queue
treatment. The other classes are configured to get percentages of the excess bandwidth if any, after
servicing the priority queue; outclass2 is configured to get 20 percent, outclass3 to get 30 percent, and
the class class-default to get the remaining 50 percent.
Router(config)# policy-map out-policy
Router(config-pmap)# class outclass1
Router(config-pmap-c)# priority
Router(config-pmap-c)# exit
Router(config-pmap)# class outclass2
Router(config-pmap-c)# bandwidth remaining percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# class outclass3
Router(config-pmap-c)# bandwidth remaining percent 30
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-22
OL-23826-09
Chapter 24
Configuring QoS
Understanding QoS
Router(config)# interface gigabitethernet 0/1
Router(config-if)# service-policy output out-policy
Router(config-if)# exit
Priority Queuing
You can use the priority policy-map class configuration command to ensure that a particular class of
traffic is given preferential treatment. With strict priority queuing, the priority queue is constantly
serviced. All packets in the queue are scheduled and sent until the queue is empty. Priority queuing
allows traffic for the associated class to be sent before packets in other queues are sent.
Caution
Be careful when using the priority command. Excessive use of strict priority queuing might cause
congestion in other queues.
The router supports strict priority queuing or priority percent policy-map command.
•
Note
•
Note
Strict priority queuing (priority without police) assigns a traffic class to a low-latency queue to
ensure that packets in this class have the lowest possible latency. When this is configured, the
priority queue is continually serviced until it is empty, possibly at the expense of packets in other
queues.
You cannot configure priority without policing for a traffic class when traffic shaping or
CBWFQ are configured for another class in the same output policy map.
Use the priority percent policy-map command, or unconditional priority policing, to reduce the
bandwidth used by the priority queue. This is the only form of policing that is supported in output
policy maps. Using this combination of commands configures a maximum rate on the priority queue,
and you can use the bandwidth and shape average policy-map commands for other classes to
allocate traffic rates on other queues. From Cisco IOS Release 15.3(2)S, Cisco ASR 901 Router
allows configuration of multiple classes to serve based on priority.
When priority is configured in an output policy map without the priority command, you can
only configure the other queues for sharing by using the bandwidth remaining percent
policy-map command to allocate excess bandwidth.
Restrictions
•
You can associate the priority command with a single unique class for all attached output polices
on the router. From Cisco IOS Release 15.3(2)S, Cisco ASR 901 Router allows configuration of
multiple classes with “priority percent.”
•
You cannot configure priority and any other scheduling action (shape average or bandwidth) in the
same class.
•
You cannot configure priority queuing for the class-default of an output policy map.
This example shows how to configure the class out-class1 as a strict priority queue so that all packets in
that class are sent before any other class of traffic. Other traffic queues are configured so that out-class-2
gets 50 percent of the remaining bandwidth and out-class3 gets 20 percent of the remaining bandwidth.
The class class-default receives the remaining 30 percent with no guarantees.
Router(config)# policy-map policy1
Router(config-pmap)# class out-class1
Router(config-pmap-c)# priority
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-23
Chapter 24
Configuring QoS
Understanding QoS
Router(config-pmap-c)# exit
Router(config-pmap)# class out-class2
Router(config-pmap-c)# bandwidth remaining percent 50
Router(config-pmap-c)# exit
Router(config-pmap)# class out-class3
Router(config-pmap-c)# bandwidth remaining percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet 0/1
Router(config-if)# service-policy output policy1
Router(config-if)# exit
This example shows how to use the priority with percent commands to configure out-class1 as the
priority queue, with traffic going to the queue limited to 20000000 bps so that the priority queue will
never use more than that. Traffic above that rate is dropped. The other traffic queues are configured to
use 50 and 20 percent of the bandwidth that is left, as in the previous example.
Router(config)# policy-map policy1
Router(config-pmap)# class out-class1
Router(config-pmap-c)# priority percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# class out-class2
Router(config-pmap-c)# bandwidth percent 50
Router(config-pmap-c)# exit
Router(config-pmap)# class out-class3
Router(config-pmap-c)# bandwidth percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface gigabitethernet 0/1
Router(config-if)# service-policy output policy1
Router(config-if)# exit
The following example shows how to use the priority with percent commands to configure multiple
traffic classes:
Router(config)# policy-map pmap_bckbone
Router(config-pmap)# class VOICE_GRP
Router(config-pmap-c)# priority percent 50
Router(config-pmap-c)# exit
Router(config-pmap)# class CTRL_GRP
Router(config-pmap-c)# priority percent 5
Router(config-pmap-c)# exit
Router(config-pmap)# class E1_GRP
Router(config-pmap-c)# priority percent 55
Router(config-pmap-c)# exit
Router(config-pmap)# class class-default
Router(config-pmap-c)# bandwidth percent 10
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Ingress and Egress QoS Functions
This section lists the supported and unsupported qos functions for ingress and egress.
Ingress QoS Functions
In Cisco ASR 901 router:
•
Interfaces support ingress classification.
•
Ethernet interfaces support ingress policing.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-24
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
•
Ethernet interfaces support ingress marking.
•
Ethernet interfaces do not support Low-Latency Queuing (LLQ) (Ingress Priority) is not supported
on ingress
•
Ethernet interfaces do not support Queuing, Shaping and Scheduling on ingress.
Egress QoS Functions
In Cisco ASR 901 router:
•
Gigabit ethernet interfaces support egress classification.
•
Gigabit ethernet interfaces do not support egress policing. All policing must be done on ingress.
•
Gigabit ethernet interfaces support egress marking.
•
Gigabit ethernet interfaces support egress scheduling.
•
Interfaces support per interface and per qos-group shaping on egress ports.
•
Interfaces support Low Latency Queuing (LLQ) and Weighted Random Early Detection (WRED)
on egress.
Configuring Quality of Service (QoS)
The following sections describe how to configure the Quality of Service (QoS) features supported by the
Cisco ASR 901 router.
•
QoS Limitations
•
QoS Configuration Guidelines
•
Sample QoS Configuration
•
Configuring Classification
•
Configuring Marking
•
Configuring Congestion Management
•
Configuring Shaping
•
Configuring Ethernet Trusted Mode
•
Creating IP Extended ACLs
•
Using Class Maps to Define a Traffic Class
•
Creating a Named Access List
QoS Limitations
The Cisco ASR 901 offers different QoS support according to the physical interface and traffic type. The
following sections describe the limitations for each QoS capability on the Cisco ASR 901.
•
General QoS Limitations
•
Statistics Limitations
•
Propagation Limitations
•
Classification Limitations
•
Marking Limitations
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-25
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
•
Congestion Management Limitations
•
Shaping Limitations
•
ACL-based QoS Restrictions
General QoS Limitations
The following general QoS limitations apply to the Cisco ASR 901 router.
•
You can create a maximum of 256 class maps including the class-default class map.
•
You can create a maximum of 32 policy-maps.
The following limitations apply to QoS policies on HDLC, PPP, PPP interfaces:
•
Input PPP interfaces support only QoS marking policies.
•
You can create a maximum of eight match statements within a class map in a service policy applied
to a PPP interface.
•
You can create a maximum of eight classes within a policy-map that is applied to a PPP interface.
This number includes the default-class.
•
You can have only one priority class within a policy-map applied to a PPP interface.
•
The match-all keyword of the class-map command is not supported.
•
The following actions are not supported for Egress Policy:
– Bandwidth value
– Priority value
– Set of qosgroup (VLAN Priority)—This is relevant only for Layer 2 transport over MLPPP
interface.
•
Requires explicit configuration of class-default with bandwidth percent.
•
DSCP marking is not supported for class-default queue.
•
All the above restrictions are applicable to MPLS/IP over MLPPP, in addition to the following
specific restrictions.
The following limitations apply to QoS policies on MPLS/IP over MLPPP interfaces:
•
Cisco ASR 901 router supports the following features for MLPPP egress—DSCP marking priority,
eight bandwidth queues, link fragmentation, interleave, and queue limits.
•
Input policy is not supported.
•
EXP marking is not supported for class-default queue.
The following limitations apply to GigabitEthernet interfaces:
•
You can apply a maximum of 2 different service policies to GigabitEthernet interfaces
•
You can only use the class-default class for HQoS parent service policies applied to egress Gigabit
Ethernet interfaces.
Statistics Limitations
•
Input service policies on the GigabitEthernet interface support statistics in bytes.
•
PPP and MLPPP interfaces support QoS statistics in packets.
•
Output service policies on the Gigabit Ethernet interface support statistics in bytes.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-26
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
•
2R3C policer provides exceed and violate counters as a single counter.
Propagation Limitations
The Cisco ASR 901 has the following limitations when propagating QoS values between interfaces:
•
The following limitations apply when traffic ingresses through a GigabitEthernet interface and
egresses through a GigabitEthernet interface:
– When traffic is switched at layer 2, the QoS group is propagated through the router.
•
The following limitations apply when traffic ingresses through any other interface type
(host-generated, PPP) and egresses through the GigabitEthernet interface.
– The Precedence bit value is propagated to the CoS bit (for host-generated interface only).
– The CoS bit value is mapped 1:1 to the QoS group value.
See Sample QoS Configuration, page 24-33 for a sample QoS configuration that accounts for
propagation limitations on the Cisco ASR 901.
Classification Limitations
Table 24-2 summarizes the values that you can use to classify traffic based on interface type. The values
are parameters that you can use with the match command.
Table 24-2
QoS Classification Limitations by Interface
GigabitEthernet
PPP
Ingress
Egress
Ingress
Egress
all
X
X
any
X
X
X
X
X
X
X
X
X
X
ip dscp
X
X
X
X
ip precedence
X
X
Value
access-group
class-map
cos
destination-address
discard-class
dscp
flow pdp
frde
frdlci
ip rtp
mpls experimental
X
not
packet length
precedence
X
X
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-27
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Table 24-2
QoS Classification Limitations by Interface
GigabitEthernet
PPP
protocol
qos-group
X
source-address
vlan
X
X
The following limitations also apply when configuring classification on the Cisco ASR 901.
•
The following limitations apply to input Gigabit Ethernet interface QoS policies:
– You can use the match vlan command with a maximum of four VLANs.The match vlan
command is supported only for PORT, EVC, and pseudowire.
– You can use the match dcsp command with a maximum of four DSCP values.
– Cisco ASR 901 router first looks for IP DSCP and then the MPLS experimental imposition for
the mpls packets.
•
The following limitations apply to output Gigabit Ethernet interface QoS policies:
– Class maps with queuing action only support matching based on qos-group. This limitation does
not apply to the class-default class map.
– You cannot create two class maps that match based on the same qos-group value.
•
The following limitations apply to input PPP interfaces:
– You can create up to 8 matches in a class-map using DSCP or MPLS Exp values.
Marking Limitations
Table 24-3 summarizes the values that you can use to mark traffic based on interface type. The values
are parameters that you can use with the set command.
Table 24-3
QoS Marking Limitations by Interface
Value
GigabitEthernet
PPP
Ingress
Egress
Ingress
X
Egress
atm-clp
cos
X
discard-class
X
dscp
X
dscp-transmit
X
ip dscp
X
X
ip precedence
X
X
mpls experimental
mpls experimental imposition
mpls experimental topmost
qos-group
X
X
X
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-28
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Table 24-3
QoS Marking Limitations by Interface
GigabitEthernet
precedence
X
prec-transmit
X
qos-group
X
PPP
X
Congestion Management Limitations
The congestion management limitations for the Cisco ASR 901 are described in the following sections:
•
Queuing Limitations
•
Rate Limiting Limitations
Queuing Limitations
The Cisco ASR 901 uses Class-based fair weighted queuing (CBFQ) for congestion management.
Table 24-4 summarizes the queuing commands that you can apply when using CBFQ according to
interface type.
Table 24-4
QoS Queuing Limitations by Interface
Value
GigabitEthernet
PPP
Ingress
Ingress
Egress
Egress
bandwidth (kbps)
bandwidth percent
X
X
bandwidth remaining percent
X
X
X
X
X
X
compression header ip
drop
fair-queue
priority
priority (kbps)
priority (without queue-limit)
priority percent
queue-limit (cells)
queue-limit (packets)
X
random-detect discard-class-based
X
Rate Limiting Limitations
You can use rate limiting for congestion management on the Cisco ASR 901. Table 24-5 summarizes the
rate limiting parameters that you can use with the police command according to interface type. The table
uses the following terms:
•
Rate—A speed of network traffic such as a committed information rate (CIR) or peak information
rate (PIR).
•
Actions—A defined action when traffic exceeds a rate, such as conform-action, exceed-action, or
violate-action.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-29
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Table 24-5
QoS Rate Limiting Limitations by Interface
Policing with
GigabitEthernet
PPP
Ingress Egress
Ingress Egress
One rate
One rate and two
actions
X
Two rates and two
actions
Two rates and
three actions
X
Shaping Limitations
Table 24-6 summarizes the values that you can use to mark traffic based on interface type. The values
are parameters that you can use with the shape command.
Table 24-6
QoS Shaping Limitations by Interface
Value
GigabitEthernet
PPP
Ingress Egress
Ingress Egress
adaptive
average
X
fecn-adapt
max-buffers
peak
The following limitations also apply to QoS shaping on the Cisco ASR 901:
•
The following limitations apply to input Gigabit Ethernet interfaces:
– You cannot apply shaping to the class-default class unless you are using hierarchical policy
maps and applying shaping to the parent policy map.
– If you are using hierarchical policy maps, you can only apply the class-default class to the parent
policy map.
ACL-based QoS Restrictions
In addition to all the limitations applicable to current QoS configuration, the following restrictions are
applicable for ACL-based QoS.
•
IPv6 ACLs are not supported
•
ACL-based QoS is limited to source and destination IP addresses. Extended ACLs with extended
options like DSCP, fragments, option, precedence, time-range, ToS, and TTL are not supported.
•
MAC ACLs are not supported. Only IP ACLs are supported.
•
You can configure only named access lists in QoS; other ACL types are not supported.
•
Only source and destination IPv4 addresses are supported in the access-list definition.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-30
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
•
You can add only a maximum of 128 ACL match filters (including default deny ace) as part of class
or classes.
Improving Feature Scalability
Effective with Cisco IOS Release 15.3(2)S, Ternary Content Addressable Memory (TCAM) is allocated
and deallocated dynamically based on system configuration. This improves both feature scalability and
efficiency of usage of TCAM. 25 percent of this memory is reserved for Layer 2 and Layer 3 control
protocols and the remaining 75 percent is allocated dynamically based on the requirements. Layer 2 and
Layer 3 forwarding tables are independent of TCAM.
TCAM with QoS
The scalability of QoS will change depending on the features configured on the Cisco ASR 901 Router.
The following are the examples:
•
You can create a maximum of 768 TCAM rules.
•
You can create a maximum of 640 TCAM rules with remote loopback in Ethernet OAM (802.3ah),
Ethernet loopback, and DelayMeasurement configured.
•
You can create a maximum of 512 TCAM rules with remote loopback in Ethernet OAM (802.3ah),
Ethernet loopback, DelayMeasurement, and Router ACL configured.
For more information on troubleshooting scalability, see Troubleshooting Tips, page 24-81.
QoS for MPLS/IP over MLPPP
Effective with Cisco IOS Release 15.4(1)S, the extended QoS functionality is supported on the MLPPP
interface. The egress policy supports classification on the MLPS EXP bits.
The following actions are supported:
•
Bandwidth percent
•
Priority percent
•
Setting the MPLS EXP bits
•
Setting the queue limit.
QoS for CPU Generated Traffic
Effective with Cisco IOS Release 15.4(1)S, QoS is provided for CPU generated traffic. The classification
is based on DSCP (for packets going over IP adjacency) or EXP (for packets going over TAG
Adjacency).
QoS treatment is available for the following CPU generated traffic:
•
OSPF Packets
•
ICMP Packets
•
BGP Packets
•
LDP Packets
•
ISIS Frames
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-31
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
The QoS configuration for CPU generated traffic is the same as of QoS for MPLS over MLPPP. However,
you should use class-map to match on DSCP or EXP values of CPU generated traffic.
For example:
•
If the OSPF packets use DSCP CS6, the policy-map should use the class-map to match DSCP CS6.
•
BGP and LDP packets use either IP Adjacency or TAG Adjacency (depends on type of packets)
– Packets going over IP Adjacency use DSCP CS6
– Packets going over TAG Adjacency use EXP 6
Note
•
For ICMP packets (PING traffic), the default DSCP value is 0; you can specify TOS value while
sending the ping traffic.
•
If IS-IS packets do not have either DSCP or EXP; it is treated with the policy configuration of DSCP
CS6.
The show policy-map interface multilink bundle-number command shows the combined counters of
CPU generated traffic and data traffic, if both data traffic and CPU generated traffic flow in the same
class.
QoS Configuration Guidelines
•
You can configure QoS on physical ports and EFPs (only in ingress).
•
QoS can likely be configured on Port-channel.
•
Only table-map configuration is allowed on SVI interfaces.
•
On a port configured for QoS, all traffic received through the port is classified, policed, and marked
according to the input policy map attached to the port. On an EFP configured for QoS, traffic in all
VLANs received through the port is classified, policed, and marked according to the policy map
attached to the port. If a per-port, per-VLAN policy map is attached, traffic on the trunk port is
classified, policed, and marked for the VLANs specified in the class filter.
•
If you have EtherChannel ports configured on your router, you must configure QoS classification,
policing, mapping, and queuing on the individual physical ports that comprise the EtherChannel.
You must decide whether the QoS configuration should match on all ports in the EtherChannel.
•
Control traffic (such as spanning-tree bridge protocol data units [BPDUs] and routing update
packets) received by the router are subject to all ingress QoS processing.
•
You might lose data when you change queue settings; therefore, try to make changes when traffic is
at a minimum.
•
When you try to attach a new policy to an interface and this brings the number of policer instances
to more than 255, you receive an error message, and the configuration fails.
•
When you try to attach new policy to an interface and this brings the number of policer profiles to
more than 254, you receive an error message, and the configuration fails. A profile is a combination
of commit rate, peak rate, commit burst, and peak burst. You can attach one profile to multiple
instances, but if one of these characteristics differs, the policer is considered to have a new profile.
•
On all Cisco ASR 901 routers, you can specify 128 unique VLAN classification criteria within a
per-port, per-VLAN policy-map, across all ports on the router. Any policy attachment or change that
causes this limit to be exceeded fails with a VLAN label resources exceeded error message.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-32
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
•
On all Cisco ASR 901 routers, you can attach per-port and per-port, per-VLAN policy-maps across
all ports on the router until QoS classification resource limitations are reached. Any policy
attachment or change that causes this limit to be exceeded fails with a TCAM resources exceeded
error message.
Sample QoS Configuration
The following configuration demonstrates how to apply QoS given the hardware limitations. The
Cisco ASR 901 processes traffic between interfaces as follows:
•
For layer 2 traffic passing between the GigabitEthernet 0/2 interface and the GigabitEthernet 0/0
interface, the output queue is determined by the QoS Group assigned in the in-qos policy map.
•
For layer 3 traffic passing between GigabitEthernet 0/2 interface and the GigabitEthernet 0/0
interface, the output queue is determined based on the CoS value assigned in the in-qos policy map.
(the CoS value is mapped 1:1 to the QoS group value.)
•
For traffic passing between other interfaces, the output queue is determined based on the CS fields
(top three bits) of the IP DSCP bits; these bits are copied to the CoS bits, which are mapped 1:1 to
the QoS group value.
!
class-map match-all q0
match qos-group 0
class-map match-all q1
match qos-group 1
class-map match-all q2
match qos-group 2
class-map match-all q3
match qos-group 3
class-map match-all q4
match qos-group 4
class-map match-all q5
match qos-group 5
class-map match-all q6
match qos-group 6
class-map match-all q7
match qos-group 7
class-map match-any Voice
match dscp ef
class-map match-any Signaling
match dscp af41
class-map match-any HSDPA
match dscp af11 af12
class-map match-any TCAM1
!translates to 3 TCAM rules because each match in match-any uses one entry
match dscp af21
match cos 3
match mpls experimental topmost
class-map match-all TCAM2
!translates to 1 TCAM rules because all the match-all clauses together take only 1 entry
match dscp af21
match cos 3
match mpls experimental topmost 1
!
policy-map in-qos
class Voice
set cos 5
set qos-group 5
class control_plane
set cos 4
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-33
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
set qos-group 4
class HSDPA
set cos 1
set qos-group 1
!
policy-map out-child
class q5
priority percent 20
class q4
bandwidth remaining percent 20
class q1
bandwidth remaining percent 59
!
!
policy-map out-parent
class class-default
shape average 100000000
service-policy out-child
!
Note
This is a partial configuration intended to demonstrate the QoS feature.
Configuring Classification
Classifying network traffic allows you to organize packets into traffic classes based on whether the
traffic matches specific criteria. Classifying network traffic is the foundation for enabling many QoS
features on your network.
This section contains the following topics:
•
Creating a Class Map for Classifying Network Traffic, page 24-34
•
Creating a Policy Map for Applying a QoS Feature to Network Traffic, page 24-35
•
Attaching the Policy Map to an Interface, page 24-36
Creating a Class Map for Classifying Network Traffic
Class maps allow you to define classes of network traffic in order to apply QoS features to each class.
Complete the following steps to create a class map:
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Use the class-map command to define a new class map and enter class map configuration mode.
Router(config)# class-map class1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-34
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Step 5
Use the match command to specify the match criteria for the class map. You can define a variety of
match criteria including CoS, DSCP, MPLS Exp, or QoS group value.
Router(config-cmap)# match qos-group 7
Note
Step 6
Class-default queue matches packets with qos-group 0.
Exit configuration mode.
Router(config-cmap)# end
Router#
Creating a Policy Map for Applying a QoS Feature to Network Traffic
A policy map allows you to apply a QoS feature to network traffic based on the traffic classification.
Complete the following steps to create and configure a policy map that uses an existing class map.
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Use the policy-map command to define a new policy map and enter policy map configuration mode.
Router(config)# policy-map policy1
Router(config-pmap)#
Step 5
Use the class command to specify a traffic class to which the policy applies. This command enters
policy-map class configuration mode, which allows you to define the treatment for the traffic class.
Router(config-pmap)# class class1
Router(config-pmap-c)#
Use the bandwidth command to specify the bandwidth allocated for a traffic class attached to the policy
map. You can define the amount of bandwidth in kbps, a percentage of bandwidth, or an absolute amount
of bandwidth. This step is optional.
Note
GigabitEthernet interfaces only support bandwidth defined as a percentage or remaining percent.
Router(config-pmap-c)# bandwidth percent 50
Step 6
Exit configuration mode.
Router(config-cmap)# end
Router#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-35
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Note
You can use the show policy-map command to verify your configuration.
Attaching the Policy Map to an Interface
After you create the policy map, you must attach it to an interface. Policy maps can be attached to either
the input or output direction of the interface.
Complete these steps to attach the policy map to an interface:
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Specify the interface to which you want to apply the policy map.
Router(config)# interface gigabitEthernet0/1
Step 5
Use the service-policy command to attach the policy map to an interface. The input and output
parameters specify the direction in which router applies the policy map.
Router(config-if)# service-policy output policy1
Step 6
Exit configuration mode.
Router(config-cmap)# end
Router#
Note
You can use the show policy map interface command to verify your configuration.
For more information about configuring classification, see the Cisco IOS Quality of Service Solutions
Configuration Guide, Release 12.2SR.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-36
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Attaching Policy Map to Cross Connect EVC
After you create the policy map, you must attach it to cross connect EVC. Policy maps can be attached
only to ingress.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
service instance instance-id ethernet
5.
encapsulation dot1q vlan-id
6.
rewrite ingress tag pop 1 symmetric
7.
xconnect peer-ip-address vc-id encapsulation mpls
8.
service policy input policy name
9.
exit
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Specifies an interface type and number, and enters interface
configuration mode.
interface type number
Example:
Router(config)# interface
GigabitEthernet0/3
Step 4
service instance instance-id ethernet
Creates a service instance on an interface and defines the
matching criteria.
•
Example:
instance-id—Unique identifier of the instance.
Router(config-if)# service instance 22
ethernet
Step 5
encapsulation dot1q vlan-id
Example:
Router(config-if)# encapsulation dot1q 22
Defines the matching criteria to be used to map 802.1Q frames
ingress on an interface to the appropriate EFP. Enter a single
VLAN ID for an exact match of the outermost tag. VLAN IDs
are 1 to 4094.
Note
VLAN IDs 4093, 4094, and 4095 are reserved for
internal use.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-37
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Step 6
Command or Action
Purpose
rewrite ingress tag pop 1 symmetric
Specifies the encapsulation modification to occur on packets at
ingress.
Example:
•
pop 1—Pop (remove) the outermost tag.
Router(config-if-svr)# rewrite ingress tag
pop 1 symmetric
•
symmetric—Configure the packet to undergo the reverse of
the ingress action at egress. If a tag is popped at ingress, it
is pushed (added) at egress.
Although the symmetric keyword appears to be optional, you
must enter it for rewrite to function correctly.
Step 7
xconnect peer-ip-address vc-id
encapsulation mpls
Binds an attachment circuit to a pseudowire, and configures an
Any Transport over MPLS (AToM) static pseudowire.
•
peer-ip-address—IP address of the remote provider edge
(PE) peer. The remote router ID can be any IP address, as
long as it is reachable.
•
vc-id—The 32-bit identifier of the virtual circuit (VC)
between the PE routers.
•
encapsulation—Specifies the tunneling method to
encapsulate the data in the pseudowire.
•
mpls—Specifies MPLS as the tunneling method.
Example:
Router(config-if-srv)# xconnect 1.1.1.1 100
encapsulation mpls
Step 8
service policy input policy name
Attaches the policy map to an interface.
•
input—Specifies the direction in which the router applies
the policy map.
•
policy name—The name of the policy map.
Example:
Router(config-if-srv)# service-policy input
policy1
Step 9
Enters global configuration mode.
exit
Configuring Marking
Marking network traffic allows you to set or modify the attributes for packets in a defined traffic class.
You can use marking with traffic classification to configure variety of QoS features for your network.
The Cisco ASR 901 marking allows you to modify the following packet attributes:
•
Differentiated services code point (DSCP) value
•
Class of service (CoS) value
•
MPLS Exp bit value
•
Qos-group value (internal)
For instructions on how to configure marking for IP Precedence, DSCP, or CoS value, see the following
sections:
•
Creating a Class Map for Marking Network Traffic
•
Creating a Policy Map for Applying a QoS Feature to Network Traffic
•
Attaching the Policy Map to an Interface
For instructions on how to configure MPLS Exp bit marking, see:
•
Configuring MPLS Exp Bit Marking using a Pseudowire.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-38
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Creating a Class Map for Marking Network Traffic
Class maps allow you to define classes of network traffic in order to apply QoS features to each class.
Complete the following steps to define a traffic class to mark network traffic:
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Use the class-map command to define a new class map and enter class map configuration mode.
Router(config)# class-map class1
Step 5
Use the match command to specify the match criteria for the class map. You can define a variety of
match criteria including CoS, DSCP, MPLS Exp, or QoS group value.
Router(config-cmap)# match qos-group 7
Step 6
Exit configuration mode.
Router(config-cmap)# end
Router#
Creating a Policy Map for Applying a QoS Feature to Network Traffic
Policy maps allow you to apply the appropriate QoS feature to the network traffic based on the traffic
classification. The following sections describe how to create and configure a policy map to use a class
map or table map.
The following restrictions apply when applying a QoS feature to network traffic:
•
A policy map containing the set qos-group command can only be attached as an intput traffic policy.
•
A policy map containing the set cos command can only be attached as an input traffic policy.
Complete the following steps to create a policy map.
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-39
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Use the policy-map command to define a policy map and enter policy map configuration mode.
Router(config)# policy-map policy1
Router(config-pmap)#
Step 5
Use the class command to specify the traffic class for which you want to create a policy and enter policy
map class configuration mode. You can also use the class-default parameter to define a default class.
Router(config-pmap)# class class1
Router(config-pmap-c)#
Step 6
Use one of the set commands listed in Table 24-7 to define a QoS treatment type.
Table 24-7
Step 7
set Commands Summary
set Commands
Traffic Attributes
Network Layer
Protocol
set cos
Layer 2 CoS value of the
outgoing traffic
Layer 2
802.1q
set dscp
DSCP value in the ToS byte
Layer 3
IP
set qos-group
QoS group ID
Layer 3
IP, MPLS
Exit configuration mode.
Router(config-pmap)# end
Router#
Note
You can use the show policy-map or show policy-map policy-map class class-name commands to
verify your configuration.
Attaching the Policy Map to an Interface
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Specify the interface to which you want to apply the policy map.
Router(config)# interface gigabitEthernet0/1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-40
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Step 5
Use the service-policy command to attach the policy map to an interface. The input and output
parameters specify the direction in which router applies the policy map.
Router(config-if)# service-policy input policy1
Step 6
Exit configuration mode.
Router(config-cmap)# end
Router#
Note
You can use the show policy map interface command to verify your configuration.
Configuring MPLS Exp Bit Marking using a Pseudowire
You can also configure MPLS Exp bit marking within an EoMPLS pseudowire interface using the set
mpls experimental imposition command. MQC based policy configuration supersedes
pseudowire-class mode of configuring QoS marking. The MQC policy shall contain only class-default
with set action to achieve the same. Follow these steps to configure MPLS Exp bit marking using a
pseudowire interface.
Complete the following steps to apply a marking policy to a pseudowire:
Step 1
Enter the interface configuration mode.
Router(config)# interface gigabitethernet 0/0
Router(config-if)#
Step 2
Specify an EVC.
Router(config-if)# service instance 1 ethernet
Router(cfg-if-srv)#
Step 3
Specify an encapsulation type for the EVC.
Router(cfg-if-srv)# encapsulation dot1q 200
Step 4
Use the xconnect command with the service policy that uses the configuration defined in the pseudowire
class.
Router(cfg-if-srv)# xconnect 10.10.10.1 121
Router(cfg-if-srv)# service-policy in <mark-policy>
For more information about configuring marking, see the Cisco IOS Quality of Service Solutions
Configuration Guide, Release 12.2SR.
Note
The Cisco ASR 901 does not support all of the commands described in the IOS Release 12.2SR
documentation.
Configuration Example
This is a sample configuration example for applying a marking policy to a pseudowire.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-41
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
policy-map cos-6
class cos-6
police rate percent 5
conform-action transmit
exceed-action drop
set mpls experimental imposition 4
interface GigabitEthernet0/3
no ip address
load-interval 30
negotiation auto
service instance 22 ethernet
encapsulation dot1q 22
rewrite ingress tag pop 1 symmetric
service-policy input cos-6
xconnect 2.2.2.2 22 encapsulation mpls
Configuring Congestion Management
The following sections describe how to configure congestion management on the Cisco ASR 901.
•
Configuring Low Latency Queueing (LLQ)
•
Configuring Multiple Priority Queueing
•
Configuring Class-Based Weighted Fair Queuing (CBFQ)
•
Weighted Random Early Detection (WRED)
Configuring Low Latency Queueing (LLQ)
Low latency queuing allows you to define a percentage of bandwidth to allocate to an interface or PVC
as a percentage. You can define a percentage for priority or nonpriority traffic classes.
Complete the following steps to configure LLQ.
Step 1
Enter enable mode.
Router> enable
Step 2
Enter the password.
Password: password
When the prompt changes to Router, you have entered enable mode.
Step 3
Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Use the policy-map command to define a policy map.
Router(config)# policy-map policy1
Step 5
Use the class command to reference the class map that defines the traffic to which the policy map
applies.
Router(config-pmap)# class class1
Router(config-pmap-c)#
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-42
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Step 6
Use the priority command to specify the priority percentage allocated to the traffic class assigned to the
policy map. You can use the burst parameter to configures the network to accommodate temporary
bursts of traffic.
Router(config-pmap-c)# priority percent 10
Step 7
Use the bandwidth command to specify the bandwidth available to the traffic class within the policy map.
You can specify the bandwidth in kbps or by a percentage of bandwidth.
Router(config-pmap-c)# bandwidth percent 30
Step 8
Exit configuration mode.
Router(config-pmap-c)# end
Router#
Note
You can use the show policy-map, show policy-map policy-map class class-name, or show
policy-map interface commands to verify your configuration.
Configuring Multiple Priority Queueing
Multiple priority queuing allows you to configure more than one class with priority percentage. The
queue-number decides the ordering. The QoS group is serviced in the descending order starting with the
highest queue number. This guarantees each of the queues its allocated bandwidth. This configuration
has a higher latency on the lower priority queue like voice, due to servicing multiple traffic types on
priority.
Restrictions
There is no provision to configure the priority level for a traffic class.
Complete the following steps to configure multiple priority queueing.
SUMMARY STEPS
1.
configure terminal
2.
policy-map
3.
class
4.
priority percent
5.
bandwidth
6.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-43
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
DETAILED STEPS
Command
Purpose
Step 1
configure terminal
Enters global configuration mode. Enter your password if prompted.
Step 2
policy-map
Defines a new policy map and enters policy map configuration mode.
Example
Router(config)# policy-map policy1
Router(config-pmap)#
Step 3
class
Example
Router(config-pmap)# class class1
Router(config-pmap-c)#
Step 4
priority percent
Example
Router(config-pmap-c)# priority
percent 10
Step 5
bandwidth
Example
Router(config-pmap-c)# bandwidth
percent 50
Step 6
exit
Specifies a traffic class to which the policy applies. This command
enters policy-map class configuration mode, which allows you to define
the treatment for the traffic class.
Specifies the priority percentage allocated to the traffic class assigned
to the policy map.
(Optional) Specifies the bandwidth allocated for a traffic class attached
to the policy map. You can define the percentage of bandwidth, or an
absolute amount of bandwidth.
Returns to global configuration mode.
Configuration Examples
This section shows sample configuration examples for multiple priority queuing on Cisco ASR 901
Router:
policy-map pmap_bckbone
class VOICE_GRP
priority percent 50
class CTRL_GRP
priority percent 5
class E1_GRP
priority percent 35
class class-default
bandwidth percent 10
Note
You can use the show policy-map, show policy-map policy-map class class-name, or show
policy-map interface commands to verify your configuration.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-44
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Configuring Class-Based Weighted Fair Queuing (CBFQ)
The Cisco ASR 901 supports Class-Based Weighted Fair Queuing (CBWFQ) for congestion
management.
Complete the following steps to configure CBWFQ.
Step 1
A class map contains match criteria against which a packet is checked to determine if it belongs to the
class. You can use class maps to define criteria that are referenced in one or more policy maps. Complete
the following steps to configure a class map.
a.
Use the class-map command to create a class map.
Router(config)# class-map class1
Router(config-cmap)#
b.
Use the match command to specify the match criteria for the class map. You can define a variety of
match criteria including CoS, DSCP, MPLS Exp, or QoS group value.
Router(config-cmap)# match qos-group 7
c.
Use the exit command to exit class map configuration.
Router(config-cmap)# exit
Router(config)#
Step 2
Note
Complete the following steps to configure a policy map and attach it to an interface.
The Cisco ASR 901 does not support the queue-limit commands. Only random-detect
discard-class-based is supported on GigabitEthernet Interfaces.
a.
Use the policy-map command to define a policy map.
Router(config)# policy-map policy1
Router(config-pmap)#
b.
Use the class command to reference the class map that defines the traffic to which the policy map
applies.
Router(config-pmap)# class class1
Router(config-pmap-c)#
c.
Use the bandwidth command to specify the bandwidth allocated for the traffic class.
Router(config-pmap-c)# bandwidth percent 10
d.
Use the exit command to exit the policy map class configuration.
Router(config-pmap-c)# exit
Router(config-pmap)#
e.
Use the exit command to exit the policy map configuration.
Router(config-pmap)# exit
Router(config)#
f.
Enter configuration for the interface to which you want to apply the policy map.
Router(config)# interface atm0/ima0
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-45
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
g.
Use the service-policy command to apply the service policy to the interface.
Router(config-if)# service-policy output policy1
Weighted Random Early Detection (WRED)
Random Early Detection (RED) is a congestion avoidance mechanism that takes advantage of the
congestion control mechanism of TCP. By randomly dropping packets prior to periods of high
congestion, RED tells the packet source to decrease its transmission rate. WRED drops packets
selectively based on IP discard-class. Discard-class is assigned to packets at the ingress, as they enter
the network. WRED is useful on any output interface where you expect to have congestion. However,
WRED is usually used in the core routers of a network, rather than at the edge. WRED uses discard-class
to determine how it treats different types of traffic.
When a packet arrives, the following events occur:
Note
1.
The average queue size is calculated.
2.
If the average is less than the minimum queue threshold, the arriving packet is queued.
3.
If the average is between the minimum queue threshold for that type of traffic and the maximum
threshold for the interface, the packet is either dropped or queued, depending on the packet drop
probability for that type of traffic.
4.
If the average queue size is greater than the maximum threshold, the packet is dropped.
Cisco ASR 901 supports configuration of random-detect thresholds only in number-of-packets.
Complete the following steps to configure WRED:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode
Step 2
policy-map
Define a new policy map and enter policy map configuration mode.
Example
Router(config)# policy-map policy1
Router(config-pmap)#
Step 3
class
Example
Router(config-pmap)# class class1
Router(config-pmap-c)#
Step 4
bandwidth
Example
Router(config-pmap-c)# bandwidth
percent 50
Specify a traffic class to which the policy applies. This command enters
policy-map class configuration mode, which allows you to define the
treatment for the traffic class.
Specify the bandwidth allocated for a traffic class attached to the policy
map. You can define the percentage of bandwidth, or an absolute
amount of bandwidth.
This step is optional.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-46
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Step 5
Command
Purpose
[no] random-detect discard-class-based
Base WRED on the discard class value of a packet.
To disable this feature, use the no form of this command.
Step 6
[no] random-detect discard-class value
min-threshold max-threshold
mark-prob-denominator
Example
Router(config-pmap-c)# random-detect
discard-class 2 100 200 10
Configure WRED parameters for a discard-class value for a class policy
in a policy map.
•
Note
value—Discard class. Valid values are 0 to 2.
WRED counters are not supported for discard class 0.
•
min-threshold—Minimum threshold in number of packets. Valid
values are 1 to 4096. When the average queue length reaches the
minimum threshold, WRED randomly drops some packets with the
specified IP precedence.
•
max-threshold—Maximum threshold in number of packets. Valid
values are 1 to 4096. When the average queue length exceeds the
maximum threshold, WRED drops all packets with the specified IP
precedence.
Note
•
Max-threshold values configured above 1024 cannot be
reached.
mark-prob-denominator—Denominator for the fraction of packets
dropped when the average queue depth is at the maximum
threshold. For example, if the denominator is 512, 1 out of every
512 packets is dropped when the average queue is at the maximum
threshold. Valid values are 1 to 65535. The default is 10; 1 out of
every 10 packets is dropped at the maximum threshold.
To return the values to the default for the discard class, use the no form
of this command.
Configuring Shaping
The Cisco ASR 901 supports class-based traffic shaping. Follow these steps to configure class-based
traffic shaping.
Class-based traffic shaping is configured using a hierarchical policy map structure; you enable traffic
shaping on a primary level (parent) policy map and other QoS features such as queuing and policing on
a secondary level (child) policy map.
This section contains the following topics:
•
Configuring Class-Based Traffic Shaping in a Primary-Level (Parent) Policy Map
•
Configuring the Secondary-Level (Child) Policy Map
Configuring Class-Based Traffic Shaping in a Primary-Level (Parent) Policy Map
Follow these steps to configure a parent policy map for traffic shaping.
Step 1
Use the policy-map command to specify the policy map for which you want to configure shaping and
enter policy-map configuration mode.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-47
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Router(config)# policy-map output-policy
Step 2
Use the class command to specify the traffic class to which the policy map applies.
Router(config-pmap)# class class1
Router(config-pmap-c)#
Step 3
Use the shape command to define algorithm and rate used for traffic shaping.
Router(config-pmap-c)# shape average mean-rate burst-size
Step 4
Use the service-policy command to attach the policy map to the class map.
Router(config-pmap-c)# service-policy policy-map
Step 5
Exit configuration mode.
Router(config-pmap-c)# end
Router#
Note
You can use the show policy-map command to verify your configuration.
For more information about configuring shaping, see Regulating Packet Flow on a Per-Class
Basis---Using Class-Based Traffic Shaping.
Note
The Cisco ASR 901 does not support all of the commands described in the IOS Release 12.2SR
documentation.
Configuring the Secondary-Level (Child) Policy Map
Follow these steps to create a child policy map for traffic shaping.
Step 1
Use the policy-map command to specify the policy map for which you want to configure shaping and
enter policy-map configuration mode.
Router(config)# policy-map output-policy
Step 2
Use the class command to specify the traffic class to which the policy map applies.
Router(config-pmap)# class class1
Router(config-pmap-c)#
Step 3
Use the bandwidth command to specify the bandwidth allocated to the policy map. You can specify the
bandwidth in kbps, a relative percentage of bandwidth, or an absolute amount of bandwidth.
Router(config-pmap-c)# bandwidth percent 50
Step 4
Exit configuration mode.
Router(config-pmap-c)# end
Router#
For more information about configuring shaping, see Regulating Packet Flow on a Per-Class
Basis---Using Class-Based Traffic Shaping.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-48
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Note
The Cisco ASR 901 does not support all of the commands described in the IOS Release 12.2SR
documentation.
Configuring Ethernet Trusted Mode
The Cisco ASR 901 supports trusted and non-trusted mode for Gigabit ethernet ports. Gigabit ethernet
ports are set in non-trusted mode by default. Trust mode is configured through table-maps. Use the set
qos-group cos command to use default mapping.
Creating IP Extended ACLs
Complete the following steps to create an IP extended ACL for IP traffic:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
Create an IP extended ACL. Repeat the step as many times as necessary.
access-list access-list-number permit
protocol {source source-wildcard
• For access-list-number, enter the access list number. The range is
destination destination-wildcard}
100 to 199 and 2000 to 2699.
[precedence precedence] [tos tos] [dscp
• For protocol, enter the name or number of an IP protocol. Use the
dscp]
question mark (?) to see a list of available protocols. To match any
Internet protocol (including ICMP, TCP, and UDP), enter ip.
•
The source is the number of the network or host sending the packet.
•
The source-wildcard applies wildcard bits to the source.
•
The destination is the network or host number receiving the packet.
•
The destination-wildcard applies wildcard bits to the destination.
You can specify source, destination, and wildcards as:
or
ip access-list extended name
•
The 32-bit quantity in dotted-decimal format.
•
The keyword any for 0.0.0.0 255.255.255.255 (any host).
•
The keyword host for a single host 0.0.0.0.
Define an extended IPv4 access list using a name, and enter access-list
configuration mode. The name can be a number from 100 to 199.
In access-list configuration mode, enter permit protocol {source
source-wildcard destination destination-wildcard}.
Step 3
end
Return to privileged EXEC mode.
Step 4
show access-lists
Verify your entries.
Step 5
copy running-config startup-config
(Optional) Save your entries in the configuration file.
To delete an access list, use the no access-list access-list-number global configuration command.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-49
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
This example shows how to create an ACL that permits IP traffic from a source host at 10.1.1.1 to a
destination host at 10.1.1.2:
Router(config)# access-list 100 permit ip host 10.1.1.1 host 10.1.1.2
Using Class Maps to Define a Traffic Class
You use the class-map global configuration command to name and to isolate a specific traffic flow (or
class) from all other traffic. A class map defines the criteria to use to match against a specific traffic flow
to further classify it. Match statements can include criteria such as CoS value, DSCP value, IP
precedence values, or QoS group values, or VLAN IDs. You define match criterion with one or more
match statements entered in the class-map configuration mode.
Follow these guidelines when configuring class maps:
•
A match-all class map cannot have more than one classification criterion (one match statement), but
a match-any class map can contain multiple match statements.
•
The match cos and match vlan commands are supported only on Layer 2 802.1Q trunk ports.
•
You use a class map with the match vlan command in the parent policy in input hierarchical policy
maps for per-port, per-VLAN QoS on trunk ports. A policy is considered a parent policy map when
it has one or more of its classes associated with a child policy map. Each class within a parent policy
map is called a parent class. You can configure only the match vlan command in parent classes. You
cannot configure the match vlan command in classes within the child policy map.
•
You cannot configure match qos-group for an input policy map.
•
In an output policy map, no two class maps can have the same classification criteria; that is, the same
match qualifiers and values.
•
The maximum number of class maps supported on the Cisco ASR 901 router is 256.
Complete the following steps to create a class map and to define the match criterion to classify traffic:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
class-map [match-all | match-any]
class-map-name
Create a class map, and enter class-map configuration mode. By default, no
class maps are defined.
•
(Optional) Use the match-all keyword to perform a logical-AND of all
matching statements under this class map. All match criteria in the class
map must be matched.
•
(Optional) Use the match-any keyword to perform a logical-OR of all
matching statements under this class map. One or more match criteria
must be matched.
•
For class-map-name, specify the name of the class map.
If no matching statements are specified, the default is match-all.
Note
A match-all class map cannot have more than one classification
criterion (match statement).
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-50
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Command
Step 3
Purpose
match {cos cos-list | ip dscp dscp-list Define the match criterion to classify traffic. By default, no match criterion
| ip precedence ip-precedence-list |
is defined.
qos-group value | vlan vlan-list}
Only one match type per class map is supported.
•
For cos cos-list, enter a list of up to four CoS values in a single line to
match against incoming packets. Separate each value with a space. You
can enter multiple cos-list lines to match more than four CoS values. The
range is 0 to 7.
•
For ip dscp dscp-list, enter a list of up to eight IPv4 DSCP values to
match against incoming packets. Separate each value with a space. You
can enter multiple dscp-list lines to match more than eight DSCP values.
The numerical range is 0 to 63. You can also configure DSCP values in
other forms. See the “Classification Based on IP DSCP” section on
page 24-9.
•
For ip precedence ip-precedence-list, enter a list of up to four IPv4
precedence values to match against incoming packets. Separate each
value with a space. You can enter multiple ip-precedence-list lines to
match more than four precedence values. The range is 0 to 7.
•
For vlan vlan-list, specify a VLAN ID or a range of VLANs to be used
in a parent policy map for per-port, per-VLAN QoS on a trunk port. The
VLAN ID range is 1 to 4094.
•
For qos-group value, specify the QoS group number. The range is
0 to 7. Matching of QoS groups is supported only in output policy maps.
Step 4
end
Return to privileged EXEC mode.
Step 5
show class-map
Verify your entries.
Step 6
copy running-config startup-config (Optional) Save your entries in the configuration file.
This example shows how to create a class map called class2, which matches incoming traffic with DSCP
values of 10, 11, and 12.
Router(config)# class-map match-any class2
Router(config-cmap)# match ip dscp 10 11 12
Router(config-cmap)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-51
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Creating a Named Access List
To create a standard or extended named access list, perform the following tasks:
Restrictions
Extended ACLs with extended options like DSCP, fragments, option, precedence, time-range, ToS, and
TTL are not supported. Only ACLs with source and destination IP addresses are supported.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip access-list {standard | extended} name
4.
permit {source [source-wildcard] | any} log
5.
exit
6.
class-map class-map-name
7.
match access-group name access-group-name
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
ip access-list {standard | extended}
name
Example:
Router(config)# ip access-list
standard acl-std
or
Define a standard or extended IP access list using a name.
•
standard—Specifies a standard IP access list.
•
extended—Specifies an extended IP access list.
•
name—Name of the IP access list or object-group ACL. Names
cannot contain a space or quotation mark, and must begin with
an alphabetic character to prevent ambiguity with numbered
access lists.
Router(config)# ip access-list
extended acl-std
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-52
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Step 4
Command
Purpose
permit {source [source-wildcard] |
any} log
Enters access-list configuration mode, and specifies one or more
allowed or denied conditions. This determines whether the packet is
passed or dropped.
Example:
Router(config-std-nacl)# permit
10.10.10.10 255.255.255.0
Step 5
•
source—Number of the network or host from which the packet
is sent in a 32-bit quantity in four-part, dotted-decimal format.
•
source-wildcard—(Optional) Wildcard bits to be applied to the
source in four-part, dotted-decimal format. Place ones in the bit
positions you want to ignore.
•
any—Specifies any source or destination host as an
abbreviation for the source-addr or destination-addr value and
the source-wildcard, or destination-wildcard value of 0.0.0.0
255.255.255.255.
•
log—Causes an informational logging message about the
packet that matches the entry to be sent to the console. (The
level of messages logged to the console is controlled by the
logging console command.)
Enters global configuration mode.
exit
Example:
Router(config-std-nacl)# exit
Step 6
class-map class-map-name
Defines name for the class map and enters class-map config mode.
•
class-map-name—Name of the class map.
Example:
Router(config)# class-map
class-acl-std
Step 7
match access-group name
access-group-name
Defines a named ACL for the match criteria.
•
Example:
Router(config-cmap)# match
access-group name acl-std
access-group-name—Specifies a named ACL whose contents
are used as the match criteria against which packets are checked
to determine if they belong to the same class. The name can be
up to 40 alphanumeric characters.
What to do Next
After creating a standard access list using names, define a policy map and attach it to the interface. See
Creating a Policy Map for Applying a QoS Feature to Network Traffic, page 24-35 and Attaching the
Policy Map to an Interface, page 24-36 for more details.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-53
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
TCAM with ACL
The scalability of ACLs will change depending on the features configured on the Cisco ASR 901 Router.
With on-demand allocation, ACLs can be allocated up to a maximum of 1536 TCAM rules. For more
information on troubleshooting scalability, see Troubleshooting Tips, page 24-81.
Configuration Examples for ACL
The following is a sample output of the show ip access-lists tcam command.
Router# show ip access-lists tcam1
!consumes 1 TCAM entry per rule + a default rule.
!4 TCAM entries in this case]
Extended IP access list tcam1
10 permit ip host 1.1.1.12 any
20 deny ip host 2.2.2.11 any
30 permit ip host 1.1.1.13 any
Router#
Router# show run int gig 0/1
Building configuration...
Current configuration : 221 bytes
!
interface GigabitEthernet0/1
no ip address
ip access-group tcam1 in
negotiation auto
Router# show platform tcam detailed
Ingress
: 6/8 slices, 1536/2048 entries used
Pre-Ingress: 3/4 slices, 768/1024 entries used
Egress
: 0/4 slices, 0/512 entries used
Slice ID: 1
Stage: Pre-Ingress
Mode: Single
Entries used: 29/256
Slice allocated to: Layer-2 Classify and Assign Group
Slice ID: 4
Stage: Pre-Ingress
Mode: Double
Entries used: 11/128
Slice allocated to: L2CP
Slice ID: 2
Stage: Ingress
Mode: Double
Entries used: 27/128
Slice allocated to: L2 Post-Switch Processing Group
Slice ID: 5
Stage: Ingress
Mode: Single
Entries used: 4/256
Slice allocated to: Port ACLs
Slice ID: 7
Stage: Ingress
Mode: Double
Entries used: 10/128
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-54
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Slice allocated to: OAM, Ethernet loopback, Y.1731 DMM
Slice ID: 3
Stage: Ingress
Mode: Double
Entries used: 15/128
Slice allocated to: CESoPSN-UDP, CEF, Layer-3 Control Protocols
Slice ID: 8
Stage: Ingress
Mode: Double
Entries used: 220/256
Slice allocated to: Quality Of Service
Verifying Named Access List
To verify the standard or extended access list configuration, use the show access-lists command as given
below:
Router# show access-lists tes456
Extended IP access list tes456
10 permit ip host 10.1.1.1
20 permit ip host 10.1.1.1
30 permit ip host 10.1.1.1
40 permit ip host 10.1.1.1
50 permit ip host 10.1.1.1
60 permit ip host 10.1.1.1
70 permit ip host 10.1.1.1
80 permit ip host 10.1.1.1
90 permit ip host 10.1.1.1
!
!
!
192.168.1.0
192.168.2.0
192.168.3.0
192.168.4.0
192.168.5.0
192.168.6.0
192.168.7.0
192.168.8.0
192.168.9.0
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
To verify the ACL-based QoS classification, use the show policy-map command as given below:
Router# show policy-map interface gigabitethernet 0/0
GigabitEthernet0/0
Service-policy input: test
Class-map: test (match-any)
0 packets, 244224 bytes
5 minute offered rate 6000 bps, drop rate 0000 bps
Match: access-group name test
QoS Set
dscp af32
Packets marked 0
No marking statistics available for this class
Class-map: class-default (match-any)
0 packets, 239168 bytes
5 minute offered rate 6000 bps, drop rate 0000 bps
Match: any
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-55
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
Configuration Example for Named Access List
The following is the sample configuration of a named access list on the Cisco ASR 901 Router.
Note
In the following configuration, both the ACL and ACL-based QoS are exclusive of each other and are
not related to each other.
Router# show running-config
Building configuration...
Current configuration : 11906 bytes
!
! Last configuration change at 22:51:12 UTC Sun May 13 2001
!
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
!card type command needed for slot/vwic-slot 0/0
enable password lab
!
no aaa new-model
ip cef
!
!
!
!
no ipv6 cef
!
!
mpls label protocol ldp
multilink bundle-name authenticated
!
table-map sach
map from 0 to 0
map from 1 to 1
map from 2 to 2
map from 3 to 3
map from 4 to 3
map from 5 to 5
map from 6 to 6
map from 7 to 7
default copy
!
l3-over-l2 flush buffers
!
!
!
!
!
!
!
spanning-tree mode pvst
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-56
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
spanning-tree extend system-id
username lab password 0 lab
!
!
!
class-map match-any test
match access-group name test123
class-map match-all test456
match access-group name tes456
class-map match-any test1
match access-group name test123
!
policy-map test
class test456
class class-default
!
!
!
!
!
!
interface Loopback0
ip address 10.10.10.1 255.255.255.255
!
interface Port-channel1
no negotiation auto
!
interface Port-channel8
no negotiation auto
service-policy input test
service instance 2000 ethernet
encapsulation dot1q 2000
rewrite ingress tag pop 1 symmetric
bridge-domain 2000
!
!
interface GigabitEthernet0/0
no negotiation auto
service-policy input test
!
interface GigabitEthernet0/1
shutdown
no negotiation auto
!
interface GigabitEthernet0/2
negotiation auto
channel-group 8 mode active
!
interface GigabitEthernet0/3
no negotiation auto
!
interface GigabitEthernet0/4
negotiation auto
service instance 200 ethernet
encapsulation untagged
bridge-domain 200
!
!
interface GigabitEthernet0/5
negotiation auto
!
interface GigabitEthernet0/6
no negotiation auto
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-57
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
interface GigabitEthernet0/7
no negotiation auto
!
interface GigabitEthernet0/8
negotiation auto
channel-group 8 mode active
!
interface GigabitEthernet0/9
no negotiation auto
!
interface GigabitEthernet0/10
no negotiation auto
!
interface GigabitEthernet0/11
no negotiation auto
!
interface FastEthernet0/0
ip address 10.104.99.152 255.255.255.0
full-duplex
!
interface Vlan1
no ip address
!
interface Vlan108
ip address 11.11.11.1 255.255.255.0
mpls ip
!
interface Vlan200
ip address 10.1.1.2 255.255.255.0
mpls ip
!
interface Vlan2000
ip address 200.1.1.1 255.255.255.0
!
router ospf 1
router-id 10.10.10.1
network 10.10.10.1 0.0.0.0 area 0
network 200.1.1.0 0.0.0.255 area 0
!
router bgp 1
bgp router-id 10.10.10.1
bgp log-neighbor-changes
neighbor 10.1.1.1 remote-as 2
neighbor 10.10.10.50 remote-as 1
neighbor 10.10.10.50 update-source Loopback0
!
ip forward-protocol nd
!
!
no ip http server
ip route 0.0.0.0 0.0.0.0 10.104.99.1
!
ip access-list extended check
deny
ip any any
ip access-list extended tes456
permit ip host 10.1.1.1 192.168.1.0 0.0.0.255
permit ip host 10.1.1.1 192.168.2.0 0.0.0.255
permit ip host 10.1.1.1 192.168.3.0 0.0.0.255
permit ip host 10.1.1.1 192.168.4.0 0.0.0.255
permit ip host 10.1.1.1 192.168.5.0 0.0.0.255
permit ip host 10.1.1.1 192.168.6.0 0.0.0.255
permit ip host 10.1.1.1 192.168.7.0 0.0.0.255
permit ip host 10.1.1.1 192.168.8.0 0.0.0.255
permit ip host 10.1.1.1 192.168.9.0 0.0.0.255
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-58
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
permit
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
ip
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
host
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
10.1.1.1
192.168.10.0
192.168.11.0
192.168.12.0
192.168.13.0
192.168.14.0
192.168.15.0
192.168.16.0
192.168.17.0
192.168.18.0
192.168.19.0
192.168.20.0
192.168.21.0
192.168.22.0
192.168.23.0
192.168.24.0
192.168.25.0
192.168.26.0
192.168.27.0
192.168.28.0
192.168.29.0
192.168.30.0
192.168.31.0
192.168.32.0
192.168.33.0
192.168.34.0
192.168.35.0
192.168.36.0
192.168.37.0
192.168.38.0
192.168.40.0
192.168.41.0
192.168.42.0
192.168.43.0
192.168.44.0
192.168.45.0
192.168.46.0
192.168.47.0
192.168.48.0
192.168.49.0
192.168.50.0
192.168.51.0
192.168.52.0
192.168.53.0
192.168.54.0
192.168.55.0
192.168.56.0
192.168.57.0
192.168.58.0
192.168.59.0
192.168.60.0
192.168.61.0
192.168.62.0
192.168.63.0
192.168.64.0
192.168.65.0
192.168.66.0
192.168.67.0
192.168.68.0
192.168.69.0
192.168.70.0
192.168.71.0
192.168.72.0
192.168.73.0
192.168.74.0
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
0.0.0.255
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-59
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
permit ip host 10.1.1.1 192.168.75.0 0.0.0.255
ip access-list extended test123
remark 1
permit ip host 10.1.1.1 192.168.1.0 0.0.0.255
remark 2
permit ip host 10.1.1.1 192.168.2.0 0.0.0.255
remark 3
permit ip host 10.1.1.1 192.168.3.0 0.0.0.255
remark 4
permit ip host 10.1.1.1 192.168.4.0 0.0.0.255
remark 5
permit ip host 10.1.1.1 192.168.5.0 0.0.0.255
remark 6
permit ip host 10.1.1.1 192.168.6.0 0.0.0.255
remark 7
permit ip host 10.1.1.1 192.168.7.0 0.0.0.255
remark 8
permit ip host 10.1.1.1 192.168.8.0 0.0.0.255
remark 9
permit ip host 10.1.1.1 192.168.9.0 0.0.0.255
remark 10
permit ip host 10.1.1.1 192.168.10.0 0.0.0.255
remark 11
permit ip host 10.1.1.1 192.168.11.0 0.0.0.255
remark 12
permit ip host 10.1.1.1 192.168.12.0 0.0.0.255
remark 13
permit ip host 10.1.1.1 192.168.13.0 0.0.0.255
remark 14
permit ip host 10.1.1.1 192.168.14.0 0.0.0.255
remark 15
permit ip host 10.1.1.1 192.168.15.0 0.0.0.255
remark 16
permit ip host 10.1.1.1 192.168.16.0 0.0.0.255
remark 17
permit ip host 10.1.1.1 192.168.17.0 0.0.0.255
remark 18
permit ip host 10.1.1.1 192.168.18.0 0.0.0.255
remark 19
permit ip host 10.1.1.1 192.168.19.0 0.0.0.255
remark 20
permit ip host 10.1.1.1 192.168.20.0 0.0.0.255
remark 21
permit ip host 10.1.1.1 192.168.21.0 0.0.0.255
remark 22
permit ip host 10.1.1.1 192.168.22.0 0.0.0.255
remark 23
permit ip host 10.1.1.1 192.168.23.0 0.0.0.255
remark 24
permit ip host 10.1.1.1 192.168.24.0 0.0.0.255
remark 25
permit ip host 10.1.1.1 192.168.25.0 0.0.0.255
remark 26
permit ip host 10.1.1.1 192.168.26.0 0.0.0.255
remark 27
permit ip host 10.1.1.1 192.168.27.0 0.0.0.255
remark 28
permit ip host 10.1.1.1 192.168.28.0 0.0.0.255
remark 29
permit ip host 10.1.1.1 192.168.29.0 0.0.0.255
remark 30
permit ip host 10.1.1.1 192.168.30.0 0.0.0.255
remark 31
permit ip host 10.1.1.1 192.168.31.0 0.0.0.255
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-60
OL-23826-09
Chapter 24
Configuring QoS
Configuring Quality of Service (QoS)
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
remark
permit
32
ip
33
ip
34
ip
35
ip
36
ip
37
ip
38
ip
39
ip
40
ip
41
ip
42
ip
43
ip
44
ip
45
ip
46
ip
47
ip
48
ip
49
ip
50
ip
host 10.1.1.1 192.168.32.0 0.0.0.255
host 10.1.1.1 192.168.33.0 0.0.0.255
host 10.1.1.1 192.168.34.0 0.0.0.255
host 10.1.1.1 192.168.35.0 0.0.0.255
host 10.1.1.1 192.168.36.0 0.0.0.255
host 10.1.1.1 192.168.37.0 0.0.0.255
host 10.1.1.1 192.168.38.0 0.0.0.255
host 10.1.1.1 192.168.39.0 0.0.0.255
host 10.1.1.1 192.168.40.0 0.0.0.255
host 10.1.1.1 192.168.41.0 0.0.0.255
host 10.1.1.1 192.168.42.0 0.0.0.255
host 10.1.1.1 192.168.43.0 0.0.0.255
host 10.1.1.1 192.168.44.0 0.0.0.255
host 10.1.1.1 192.168.45.0 0.0.0.255
host 10.1.1.1 192.168.46.0 0.0.0.255
host 10.1.1.1 192.168.47.0 0.0.0.255
host 10.1.1.1 192.168.48.0 0.0.0.255
host 10.1.1.1 192.168.49.0 0.0.0.255
host 10.1.1.1 192.168.50.0 0.0.0.255
!
access-list 2600 permit ip any any
!
mpls ldp router-id Loopback0
!
!
control-plane
!
environment monitor
!
line con 0
line aux 0
transport preferred none
transport output lat pad telnet rlogin udptn ssh
line vty 0 4
exec-timeout 3 3
password lab
login
!
exception crashinfo buffersize 128
!
!
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-61
Chapter 24
Configuring QoS
QoS Treatment for Performance-Monitoring Protocols
QoS Treatment for Performance-Monitoring Protocols
This section contains the following topics:
•
Cisco IP-SLAs, page 24-62
•
QoS Treatment for IP-SLA Probes, page 24-62
•
QoS Marking for CPU-Generated Traffic, page 24-62
•
QoS Queuing for CPU-Generated Traffic, page 24-63
•
Configuration Guidelines, page 24-80
Cisco IP-SLAs
For information about Cisco IP service level agreements (IP-SLAs), see Understanding Cisco IOS IP
SLAs, page 3-2.
QoS Treatment for IP-SLA Probes
The QoS treatment for IP-SLA and TWAMP probes must exactly reflect the effects that occur to the
normal data traffic crossing the device.
The generating device should not change the probe markings. It should queue these probes based on the
configured queueing policies for normal traffic.
Marking
By default, the class of service (CoS) marking of CFM traffic (including IP SLAs using CFM probes) is
not changed. This feature cannot change this behavior.
By default, IP traffic marking (including IP SLA and TWAMP probes) is not changed. This feature can
change this behavior.
Queuing
The CFM traffic (including IP SLAs using CFM probes) is queued according to its CoS value and the
output policy map configured on the egress port, similar to normal traffic. This feature cannot change
this behavior.
IP traffic (including IP SLA and TWAMP probes) is queued according to the markings specified in the
cpu traffic qos global configuration command and the output policy map on the egress port. If this
command is not configured, all IP traffic is statically mapped to a queue on the egress port.
QoS Marking for CPU-Generated Traffic
You can use QoS marking to set or modify the attributes of traffic from the CPU. The QoS marking action
can cause the CoS, DSCP, or IP precedence bits in the packet to be rewritten or left unchanged. QoS uses
packet markings to identify certain traffic types and how to treat them on the local router and the
network.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-62
OL-23826-09
Chapter 24
Configuring QoS
QoS Treatment for Performance-Monitoring Protocols
You can also use marking to assign traffic to a QoS group within the router. This QoS group is an internal
label that does not modify the packet, but it can be used to identify the traffic type when configuring
egress queuing on the network port.
You can specify and mark traffic CPU-generated traffic by using these global configuration commands:
cpu traffic qos cos {cos_value | cos [table-map table-map-name] | dscp [table-map table-map-name] |
precedence [table-map table-map-name]}
You can mark a QoS group by configuring an explicit value or by using the table-map keyword. Table
maps list specific traffic attributes and map (or convert) them to another attribute. A table map
establishes a to-from relationship for the attribute and defines the change to be made:
•
Marking CoS by using the CoS, or the IP-DSCP, or the IP precedence of IP CPU-packets
•
Marking CoS by using the CoS of non-IP CPU-packets.
•
Marking IP DSCP by using the CoS, or the IP-DSCP, or the IP precedence of the CPU-packet
•
Marking IP precedence by using the CoS, or the IP-DSCP, or the IP precedence of the CPU-packet
You can configure either IP-DSCP or IP precedence marking.
You can also simultaneously configure marking actions to modify CoS, IP-DSCP or IP precedence, and
QoS group.
The cpu traffic qos command specifies the traffic to which it applies: all CPU traffic, only CPU IP
traffic, or only CPU non-IP traffic. All other traffic retains its QoS markings. This feature does not affect
CFM traffic (including Layer 2 IP SLA probes using CFM).
QoS Queuing for CPU-Generated Traffic
You can use the QoS markings established for the CPU-generated traffic by the cpu traffic qos global
configuration command as packet identifiers in the class-map of an output policy-map to map CPU
traffic to class-queues in the output policy-map on the egress port. You can then use output policy-maps
on the egress port to configure queuing and scheduling for traffic leaving the router from that port.
If you want to map all CPU-generated traffic to a single class in the output policy-maps without changing
the CoS, IP DSCP, or IP-precedence packet markings, you can use QoS groups for marking
CPU-generated traffic.
If you want to map all CPU-generated traffic to classes in the output policy maps based on the CoS
without changing the CoS packet markings, you can use the table map:
•
Configure CoS marking by using CoS as the map from value without a table map.
•
Configure CoS marking using CoS as the map from value with a table map, using only the default
and copy keywords.
For details about table maps, see the “Table Maps” section on page 24-13.
Using the cpu traffic qos global configuration command with table mapping, you can configure multiple
marking and queuing policies to work together or independently. You can queue native VLAN traffic
based on the CoS markings configured using the cpu traffic qos global configuration command.
The cpu traffic qos command specifies the traffic to which it applies: all CPU traffic, only CPU-IP
traffic, or only CPU non-IP traffic. All other traffic is statically mapped to a CPU-default queue on the
egress port. All CFM traffic (including Layer 2 IP SLA probes using CFM) is mapped to classes in the
output policy map, and queued based on their CoS value.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-63
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Extending QoS for MLPPP
•
Configuring Class-map for Matching MPLS EXP Bits, page 24-64
•
Configuring Class-map for Matching IP DSCP Value, page 24-65
•
Configuring Class-map for Matching MPLS EXP Bits or IP DSCP Value, page 24-66
•
Configuring a Policy-map, page 24-67
•
Attaching the Policy-map to MLPPP Interface, page 24-70
•
Re-marking IP DSCP Values of CPU Generated Traffic, page 24-72
•
Re-marking MPLS EXP Values of CPU Generated Traffic, page 24-73
•
Configuring a Policy-map to Match on CS5 and EXP4, page 24-74
•
Attaching the Policy-map to Match on CS5 and EXP4 to MLPPP Interface, page 24-76
Configuring Class-map for Matching MPLS EXP Bits
Complete the following steps to configure class-map for matching MPLS experimental bits.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
class-map match-any class-map-name
4.
match mpls experimental topmost number
5.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
class-map match-any class-map-name
Example:
Router(config)# class-map match-any
mplsexp
Creates a class map to be used for matching packets to a specified class
and to enter QoS class-map configuration mode:
•
class-map-name—Name of the class for the class map. The class
name is used for both the class map and to configure a policy for the
class in the policy map.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-64
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 4
Command
Purpose
match mpls experimental topmost
number
Matches the experimental (EXP) value in the topmost label header.
•
Example:
Note
Router(config-cmap)# match mpls
experimental topmost 5
Step 5
number—Multiprotocol Label Switching (MPLS) EXP field in the
topmost label header. Valid values are 0 to 7.
In this configuration packets with experimental bits of value 5 are
matched. Repeat this step to configure more values. If any one of
the values is matched, action pertaining to the class-map is
performed.
Exits class-map configuration mode.
exit
Example:
Router(config-cmap)# exit
Configuring Class-map for Matching IP DSCP Value
This classification is required for all the packets flowing without an MPLS header like normal IP packets
flowing through an MLPPP Interface.
Complete the following steps to configure class-map for matching IP DSCP Values.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
class-map match-any class-map-name
4.
match ip dscp [dscp-value...dscp-value]
5.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Creates a class map to be used for matching packets to a specified class
and to enter QoS class-map configuration mode:
class-map match-any class-map-name
•
Example:
Router(config)# class-map match-any
matchdscp
class-map-name—Name of the class for the class map. The class
name is used for both the class map and to configure a policy for the
class in the policy map.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-65
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 4
Command
Purpose
match ip dscp
[dscp-value...dscp-value]
Identify one or more differentiated service code point (DSCP), Assured
Forwarding (AF), and Class Selector (CS) values as a match criterion.
•
Example:
Router(config-cmap)# match ip dscp
af11
Step 5
Note
dscp-value—The DSCP value used to identify a DSCP value.
In this configuration packets with IP DSCP of value af11 are
matched. Repeat this step to configure more values. If any one of
the values is matched, action pertaining to the class-map is
performed.
Exits class-map configuration mode.
exit
Example:
Router(config-cmap)# exit
Configuring Class-map for Matching MPLS EXP Bits or IP DSCP Value
In this configuration, all MPLS packets flowing through the MLPPP Interface EXP value are matched
and all the IP Packets flowing through the MLPPP Interface IP DSCP value are matched.
Complete the following steps to configure class-map for matching MPLS EXP bits or IP DSCP Values.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
class-map match-any class-map-name
4.
match mpls experimental topmost number
5.
match ip dscp [dscp-value...dscp-value]
6.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-66
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 3
Command
Purpose
class-map match-any class-map-name
Creates a class map to be used for matching packets to a specified class
and to enter QoS class-map configuration mode:
•
Example:
Router(config)# class-map match-any
matchdscp
Step 4
class-map-name—Name of the class for the class map. The class
name is used for both the class map and to configure a policy for the
class in the policy map.
Matches the experimental (EXP) value in the topmost label header.
match mpls experimental topmost
number
•
number—Multiprotocol Label Switching (MPLS) EXP field in the
topmost label header. Valid values are 0 to 7.
Example:
Router(config-cmap)# match mpls
experimental topmost 5
Step 5
Identifies the DSCP values as a match criterion.
match ip dscp dscp-value
•
dscp-value—The DSCP value used to identify a DSCP.
Example:
Router(config-cmap)# match ip dscp
af11
Step 6
Exits class-map configuration mode.
exit
Example:
Router(config-cmap)# exit
Configuring a Policy-map
Complete the following steps to configure a policy-map.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
policy-map policy-map-name
4.
class class-name
5.
priority percent priority-percent -
6.
class class-name
7.
bandwidth percent bandwidth-percent
8.
class class-name
9.
set mpls experminetal topmost number
10. class class-name
11. set ip dscp dscp-value
12. class class-name
13. bandwidth percent bandwidth-percent
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-67
Chapter 24
Configuring QoS
Extending QoS for MLPPP
14. set mpls experminetal topmost number
15. set ip dscp value
16. queue-limit queue-limit-size packets
17. class class-default
18. bandwidth percent bandwidth-percent
19. exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
policy-map policy-map-name
Example:
Configures a policy map that can be attached to one or more interfaces and
enters QoS policy-map configuration mode.
•
policy-map-name—Name of the policy map.
Router(config)# policy-map
mplsomlpppqos
Step 4
class class-name
Specifies the name of the class whose policy you want to create.
•
Example:
Router(config-pmap)# class mplsexp
Step 5
priority percent percentage
class-name—Name of the class to be configured or whose policy is
to be modified. The class name is used for both the class map and to
configure a policy for the class in the policy map.
Configures priority to a class of traffic belonging to a policy map.
•
Example:
percentage—Total available bandwidth to be set aside for the priority
class.
Router(config-pmap-c)# priority
percent 10
Step 6
class class-name
Specifies the name of the class whose policy you want to create.
Example:
Router(config-pmap-c)# class
matchdscp
Step 7
bandwidth percent percentage
Configures the bandwidth allocated for a class belonging to a policy map.
•
Example:
Router(config-pmap-c)# bandwidth
percent 20
percentage—Specifies the percentage of guaranteed bandwidth based
on an absolute percent of available bandwidth to be set aside for the
priority class or on a relative percent of available bandwidth.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-68
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 8
Command
Purpose
class class-name
Specifies the name of the class whose policy you want to create.
Example:
Router(config-pmap-c)# class
mplsexpvalues
Step 9
set mpls experimental topmost
mpls-exp-value
Sets the MPLS EXP field value in the topmost label on an interface.
•
mpls-exp-value—Specifies the value used to set MPLS experimental
bits defined by the policy map.
Example:
Router(config-pmap-c)# set mpls
experimental topmost 4
Step 10
class class-name
Specifies the name of the class whose policy you want to create.
Example:
Router(config-pmap-c)# class
matchdscpvalues
Step 11
set dscp dscp-value
Example:
Marks a packet by setting the differentiated services code point (DSCP)
value in the type of service (ToS) byte.
•
dscp-value—The DSCP value used to identify a DSCP.
Router(config-pmap-c)# set dscp
af41
Step 12
class class-name
Specifies the name of the class whose policy you want to create.
Example:
Router(config-pmap-c)# class
mplsexp_or_dscp
Step 13
bandwidth percent percentage
Configures the bandwidth allocated for a class belonging to a policy map.
Example:
Router(config-pmap-c)# bandwidth
percent 20
Step 14
set mpls experimental topmost
mpls-exp-value
Sets the MPLS EXP field value in the topmost label on an interface.
Example:
Router(config-pmap-c)# set mpls
experimental topmost 1
Step 15
set dscp dscp-value
Marks a packet by setting the differentiated services code point (DSCP)
value in the type of service (ToS) byte.
Example:
Router(config-pmap-c)# set dscp
af11
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-69
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 16
Command
Purpose
queue queue-limit-size packets
Configures the queue limit (size) for a class in packets.
Example:
Step 17
•
number—The maximum size of the queue.
•
packets—Indicates that the unit of measure is packets.
Router(config-pmap-c)# queue-limit
80 packets
Note
end
Exits QoS policy-map class configuration mode.
To configure queue-limit, you should configure either priority
percent or bandwidth percent.
Example:
Router(config-pmap-c)# exit
Attaching the Policy-map to MLPPP Interface
Complete the following steps to attach the policy-map to an MLPPP interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface multilink group-number
4.
ip address address [subnet mask]
5.
load-interval interval
6.
mpls ip
7.
keepalive period
8.
ppp multilink
9.
ppp multilink group number
10. ppp multilink endpoint string char-string
11. service-policy output policy-map-name
12. exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-70
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Creates a multilink bundle and enters the interface configuration mode:
interface multilink
group-number
•
group-number—Number of the multilink bundle.
Example:
Router(config)# interface
multilink5
Step 4
Assigns an IP address to the multilink interface.
ip address
address [subnet mask]
Example:
•
address— IP address.
•
subnet mask—Network mask of IP address.
Router(config-if)# ip address
84.1.2.3 255.255.255.0
Step 5
Configures the length of time for which data is used to compute load
statistics.
load-interval interval
•
Example:
Router(config-if)# load-interval 30
Step 6
mpls ip
interval—Length of time for which data is used to compute load
statistics.
Enables MPLS forwarding of IPv4 packets along normally routed paths
for a particular interfaces.
Example:
Router(config-if)# mpls ip
Step 7
keepalive period
Example:
Router(config-if)# keepalive 1
Step 8
ppp multilink
Enables keepalive packets and specifies the number of times that the
router tries to send keepalive packets without a response before bringing
down the interface.
•
period—Time interval, in seconds, between messages sent by the
router to ensure that a network interface is alive.
Enables Multilink PPP (MLP) on an interface.
Example:
Router(config-if)# ppp multilink
Step 9
ppp multilink group group-number
Example:
Restricts a physical link to join only one designated multilink group
interface.
•
group-number—Multilink group number (a nonzero number).
Router(config-if)# ppp multilink
group 3
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-71
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 10
Command
Purpose
ppp multilink endpoint string
char-string
Configures the default endpoint discriminator the system uses when
negotiating the use of MLPPP with the peer.
•
char-string—Uses the supplied character string.
Example:
Router(config-if)# ppp multilink
endpoint string ML3
Step 11
service-policy output
policy-map-name
Attaches a policy map to an interface that will be used as the service
policy for the interface.
•
Example:
policy-map-name—The name of a service policy map (created using
the policy-map command) to be attached.
Router(config-if)# service-policy
output mplsomlpppqos
Step 12
Exits interface configuration mode.
exit
Example:
Router(config-if)# exit
Re-marking IP DSCP Values of CPU Generated Traffic
Complete the following steps to re-mark the IP DSCP values of the CPU generated traffic.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cpu traffic ppp set ip dscp cs5
4.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-72
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 3
Command
Purpose
cpu traffic ppp set ip dscp cs5
Re-marks the IP DSCP value to give the desired QoS treatment to CPU
generated traffic.
Example:
Router(config)# cpu traffic ppp set
ip dscp cs5
Step 4
Exits configuration mode.
exit
Example:
Router(config)# exit
Re-marking MPLS EXP Values of CPU Generated Traffic
Complete the following steps to re-mark the MPLS EXP values of the CPU generated traffic.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cpu traffic ppp set mpls experimental topmost number
4.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Re-marks Multiprotocol Label Switching (MPLS) experimental (EXP)
topmost value to give the desired QoS treatment to CPU generated traffic.
cpu traffic ppp set mpls
experimental topmost number
•
Example:
number—MPLS EXP field in the topmost label header. Valid values
are 0 to 7.
Router(config)# cpu traffic ppp set
mpls experimental topmost 4
Step 4
exit
Exits configuration mode.
Example:
Router(config)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-73
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Configuring a Policy-map to Match on CS5 and EXP4
Complete the following steps to configure a policy-map to match on CS5 and EXP4.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
class-map match-any class-map-name
4.
match ip dscp cs-value
5.
class-map match-any exp4
6.
match mpls experimental topmost number
7.
policy-map policy-map-name
8.
class class-name
9.
bandwidth percent bandwidth-percent
10. set ip dscp dscp-value
11. class class-name
12. bandwidth percent bandwidth-percent
13. set mpls experminetal topmost number
14. class class-name
15. bandwidth percent bandwidth-percent
16. exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
class-map match-any dscp cs-value
Example:
Configures a class map to be used for matching packets to a specified
class and enters QoS class-map configuration mode.
•
class-map-name—The name used for class map.
Router(config)# class-map match-any
dscpcs5
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-74
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 4
Command
Purpose
match ip dscp cs-value
Identify one or more differentiated service code point (DSCP) CS value
as a match criterion.
Example:
•
cs-value—The Class Selector(CS) value.
Router(config-cmap)# match ip dscp
cs5
Step 5
class-map match-any class-map-name
Creates a class map to be used for matching packets to a specified class.
•
class-map-name—Name of the class for the class map.
Example:
Router(config-cmap)# class-map
match-any exp4
Step 6
match mpls experimental topmost
number
Matches the experimental (EXP) value in the topmost label header.
•
number—Multiprotocol Label Switching (MPLS) EXP field in the
topmost label header. Valid values are 0 to 7.
Example:
Router(config-cmap)# match mpls
experimental topmost 4
Step 7
policy-map policy-map-name
Example:
Configures a policy map that can be attached to one or more interfaces and
enters QoS policy-map configuration mode.
•
policy-map-name—Name of the policy map.
Router(config-cmap)# policy-map
dscp_exp
Step 8
class class-name
Specifies the name of the class whose policy you want to create.
•
Example:
Router(config-pmap)# class dscpcs5
Step 9
bandwidth percent percentage
Configures the bandwidth allocated for a class belonging to a policy map.
•
Example:
Router(config-pmap-c)# bandwidth
percent 20
Step 10
set ip dscp cs-value
class-name—Name of the class to be configured or whose policy is
to be modified. The class name is used for both the class map and to
configure a policy for the class in the policy map.
percentage—Specifies the percentage of guaranteed bandwidth based
on an absolute percent of available bandwidth to be set aside for the
priority class or on a relative percent of available bandwidth.
Marks a packet by setting the differentiated services code point (DSCP)
value in the type of service (ToS) byte.
Example:
Router(config-pmap-c)# set ip dscp
cs6
Step 11
class class-name
Specifies the name of the class whose policy you want to create.
Example:
Router(config-pmap-c)# class exp4
Step 12
bandwidth percent percentage
Configures the bandwidth allocated for a class belonging to a policy map.
•
Example:
Router(config-pmap-c)# bandwidth
percent 20
percentage—Specifies the percentage of guaranteed bandwidth based
on an absolute percent of available bandwidth to be set aside for the
priority class or on a relative percent of available bandwidth.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-75
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Step 13
Command
Purpose
set mpls experimental topmost
mpls-exp-value
Sets the MPLS EXP field value in the topmost label on an interface.
•
mpls-exp-value—Specifies the value used to set MPLS experimental
bits defined by the policy map.
Example:
Router(config-pmap-c)# set mpls
experimental topmost 6
Step 14
class class-name
Specifies the name of the class whose policy you want to create.
Example:
Router(config-pmap-c)# class
class-default
Step 15
bandwidth percent percentage
Configures the bandwidth allocated for a class belonging to a policy map.
Example:
Router(config-pmap-c)# bandwidth
percent 20
Step 16
Exits QoS policy-map class configuration mode.
end
Example:
Router(config-pmap-c)# exit
Attaching the Policy-map to Match on CS5 and EXP4 to MLPPP Interface
See “Attaching the Policy-map to MLPPP Interface” section on page 24-78 for configuration steps.
Note
DSCP CS6 and EXP 6 are default values. If you configure the CPU generated traffic to these values using
CLI, you cannot see them in the output of the show running-configuration command.
Configuration Examples for Extending QoS for MPLS over MLPPP
•
Configuring Class-map for Matching MPLS EXP Bits, page 24-76
•
Configuring Class-map for Matching IP DSCP Value, page 24-77
•
Configuring Class-map for Matching MPLS EXP Bits or IP DSCP Value, page 24-77
•
Configuring a Policy-map, page 24-77
•
Attaching the Policy-map to MLPPP Interface, page 24-78
Configuring Class-map for Matching MPLS EXP Bits
The following example shows a configuration of class-map for matching MPLS EXP bits.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-76
OL-23826-09
Chapter 24
Configuring QoS
Extending QoS for MLPPP
Building configuration...
Current configuration : 101 bytes
!
class-map match-any mpls_exp5
match mpls experimental topmost 5
!
Configuring Class-map for Matching IP DSCP Value
The following example shows a configuration of class-map for matching IP DSCP value.
Building configuration...
Current configuration : 101 bytes
!
!
class-map match-any dscpaf11
match ip dscp af11
!
Configuring Class-map for Matching MPLS EXP Bits or IP DSCP Value
The following example shows a configuration of class-map for matching MPLS EXP Bits or IP DSCP
value.
Building configuration...
Current configuration : 101 bytes
!
!
class-map match-any mplsexp_or_cos
match mpls experimental topmost 4
match ip dscp af41
!
Configuring a Policy-map
The following example shows a configuration of a policy-map.
Building configuration...
Current configuration : 101 bytes
!
policy-map mplsomlpppqos
class mplsexp
priority percent 10
class mplsexpvalues
set mpls experimental topmost 4
class matchdscp
bandwidth percent 20
class matchdscpvalues
set dscp af41
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-77
Chapter 24
Configuring QoS
Extending QoS for MLPPP
class mplsexp_or_dscp
bandwidth percent 20
queue-limit 80 packets
set mpls experimental topmost 1
set dscp af11
!
Configuring a Policy-map to Match on CS5 and EXP 4
The following example shows a configuration of a policy-map.
Building configuration...
Current configuration : 101 bytes
!
class-map match-any dscpcs5
match ip dscp cs5
class-map match-any exp4
match mpls experimental topmost 4
policy-map dscp_exp
class dscpcs5
bandwidth percent 20
set ip dscp cs6
class exp4
bandwidth percent 20
set mpls experimental topmost 6
class class-default
bandwidth percent 20
!
Attaching the Policy-map to MLPPP Interface
The following example shows a configuration of attaching the policy-map to MLPPP interface.
Building configuration...
Current configuration : 101 bytes
!
!
interface Multilink3
ip address 84.1.2.3 255.255.255.0
load-interval 30
mpls ip
keepalive 1
ppp multilink
ppp multilink group 3
ppp multilink endpoint string ML3
service-policy output mplsomlpppqos
!
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-78
OL-23826-09
Chapter 24
Configuring QoS
Verifying MPLS over MLPPP Configuration
Verifying MPLS over MLPPP Configuration
To verify the configuration of MPLS over MLPPP, use the following commands as shown in the
examples below:
To verify the details of a class-map created for matching MPLS EXP bits, use the following command
as shown in the example below:
Router# show run class-map mpls_exp1
Building configuration...
Current configuration : 76 bytes
!
class-map match-any mpls_exp1
match mpls experimental topmost 1
!
end
To verify the details of a class-map created for matching IP DSCP values, use the following command
as shown in the example below:
Router# show run class-map dscpaf21
Building configuration...
Current configuration : 60 bytes
!
class-map match-any dscpaf21
match ip dscp af21
!
end
To verify the details of a policy-map, use the following command as shown in the example below:
Router# show run policy-map policy_match_dscpaf11
Building configuration...
Current configuration : 100 bytes
!
policy-map policy_match_dscpaf11
class dscpaf11
set ip dscp af22
priority percent 10
!
end
To verify the details of a policy-map attached to MLPPP interface, use the following command as shown
in the example below:
Router# show policy-map interface multilink3
Multilink3
Service-policy output: match_dscp_exp
Class-map: dscpcs4 (match-any)
0 packets, 0 bytes
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-79
Chapter 24
Configuring QoS
Verifying MPLS over MLPPP Configuration
30 second offered rate 0000 bps, drop rate 0000 bps
Match: ip dscp cs4 (32)
Queueing
queue limit 38 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 10% (153 kbps)
Class-map: dscpcs6 (match-any)
19 packets, 1889 bytes
30 second offered rate 0000 bps, drop rate 0000 bps
Match: ip dscp cs6 (48)
Queueing
queue limit 38 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 10% (153 kbps)
Configuration Guidelines
•
This feature must be configured globally for a router; it cannot be configured per-port or
per-protocol.
•
Enter each cpu traffic qos marking action on a separate line.
•
The cpu traffic qos cos global configuration command configures CoS marking for CPU-generated
traffic by using either a specific CoS value or a table map, but not both. A new configuration
overwrites the existing configuration.
•
The cpu traffic qos dscp global configuration command configures IP-DSCP marking for
CPU-generated IP traffic by using either a specific DSCP value or a table map, but not both. A new
configuration overwrites the existing configuration.
•
The cpu traffic qos precedence global configuration command configures IP-precedence marking
for CPU-generated IP traffic by using either a specific precedence value or a table map, but not both.
A new configuration overwrites the existing configuration.
•
The cpu traffic qos dscp and cpu traffic qos precedence global configuration commands are
mutually exclusive. A new configuration overwrites the existing configuration.
•
When the cpu traffic qos dscp global configuration command is configured with table maps, you
can configure only one map from value at a time—DSCP, precedence, or CoS. A new configuration
overwrites the existing configuration. Packets marked by this command can be classified and queued
by an output policy map based on the marked DSCP or precedence value.
•
When the cpu traffic qos precedence global configuration command is configured with table maps,
you can configure only one map from value at a time—DSCP, precedence, or CoS. A new
configuration overwrites the existing configuration. Packets marked by this command can be
classified and queued by an output policy map based on the marked precedence or DSCP value.
•
You cannot configure a map from value of both DSCP and precedence. A new configuration
overwrites the existing configuration.
•
When the cpu traffic qos cos global configuration command is configured with table maps, you can
configure two map from values at a time—CoS and either DSCP or precedence.
•
If the cpu traffic qos cos global configuration command is configured with only a map from value
of DSCP or precedence:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-80
OL-23826-09
Chapter 24
Configuring QoS
Troubleshooting Tips
– The CoS value of IP packets is mapped by using the DSCP (or precedence) value in the packet
and the configured table map. Packets can be classified and queued by an output policy map
based on the marked CoS value.
– The CoS value of non-IP packets remains unchanged.
•
If the cpu traffic qos cos global configuration command is configured with a map from value of
CoS:
– The CoS value of IP packets is mapped by using the CoS value in the packet and the configured
table map. Packets can be classified and queued by an output policy map based on the marked
CoS value.
– The CoS value of non-IP packets is mapped by using the CoS value in the packet and the
configured table map. Packets can be classified and queued by an output policy map based on
the marked CoS value.
•
If the cpu traffic qos cos global configuration command is configured with a map from value of
DSCP or precedence and CoS:
– The CoS value of IP packets is mapped by using the DSCP or precedence value in the packet
and the configured table map. Packets can be classified and queued by an output policy map
based on the marked CoS value.
– The CoS value of non-IP packets is mapped by using the CoS value in the packet and the
configured table map. Packets can be classified and queued by an output policy map based on
the marked CoS value.
Troubleshooting Tips
The on-demand TCAM resource allocation may fail due to the unavailability of resources for the
requested operation. In such scenarios, use the following troubleshooting tips:
1.
Run the show platform tcam detailed command to understand the current resource allocation.
2.
Use this information to find the features that are allocated resources.
3.
Unconfigure the features that are no longer required to free the resources.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-81
Chapter 24
Configuring QoS
Troubleshooting Tips
Figure 24-7 shows the troubleshooting feature scalability procedure.
Figure 24-7
Troubleshooting Feature Scalabitlity
The following TCAM commands are used for troubleshooting feature scalability.
Command
Purpose
show platform tcam summary
Shows the current occupancy of TCAM with summary of
the number of slices allocated or free.
show platform tcam detailed
Shows the current occupancy and includes per-slice
information such as number of entries used or free,
feature(s) using the slice, slice mode, and slice stage and ID.
This command helps to understand current resource
allocation and decide which feature(s) to unconfigure to
free resources.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-82
OL-23826-09
Chapter 24
Configuring QoS
Troubleshooting Tips
Command
Purpose
debug platform tcam error
Enables TCAM error printing.
By default, the error printing is turned on and the info
printing is turned off.
Enables TCAM info printing.
debug platform tcam info
Use the no form of the debug commands to disable TCAM error printing and TCAM info printing.
Warning
We suggest you do not use the debug commands without TAC supervision.
The following is a sample of the output from the show platform tcam summary command.
Router# show
Ingress
:
Pre-Ingress:
Egress
:
platform tcam summary
2/8 slices, 512/2048 entries used
3/4 slices, 768/1024 entries used
0/4 slices, 0/512 entries used
The following is a sample of the output from the show platform tcam detailed command.
Router# show platform tcam detailed
Ingress
: 2/8 slices, 512/2048 entries used
Pre-Ingress: 3/4 slices, 768/1024 entries used
Egress
: 0/4 slices, 0/512 entries used
Slice ID: 1
Stage: Pre-Ingress
Mode: Single
Entries used: 28/256
Slice allocated to: Layer-2 Classify and Assign Group
Slice ID: 4
Stage: Pre-Ingress
Mode: Double
Entries used: 10/128
Slice allocated to: L2CP
Slice ID: 2
Stage: Ingress
Mode: Double
Entries used: 29/128
Slice allocated to: L2 Post-Switch Processing Group
Slice ID: 3
Stage: Ingress
Mode: Single
Entries used: 13/256
Slice allocated to: CESoPSN-UDP, CEF, Layer-3 Control Protocols
Example: TCAM troubleshooting related error
In this example all the eight slices available at the Ingress stage have already been allocated. Also, the
slice allocated to QoS has no free entries. If we need to configure a few more QoS rules, the following
options are available:
1.
To unconfigure QoS rules that are no longer required and thereby freeing up the entries
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-83
Chapter 24
Configuring QoS
Troubleshooting Tips
2.
To free up a slice by unconfiguring features that are no longer required.
Router# show platform tcam detailed
Ingress
: 8/8 slices, 2048/2048 entries used [no free slices available]
Pre-Ingress: 3/4 slices, 768/1024 entries used
Egress
: 0/4 slices, 0/512 entries used
Slice ID: 1
Stage: Pre-Ingress
Mode: Single
Entries used: 29/256
Slice allocated to: Layer-2 Classify and Assign Group
Slice ID: 4
Stage: Pre-Ingress
Mode: Double
Entries used: 11/128
Slice allocated to: L2CP
Slice ID: 2
Stage: Ingress
Mode: Double
Entries used: 27/128
Slice allocated to: L2 Post-Switch Processing Group
Slice ID: 6
Stage: Ingress
Mode: Single
Entries used: 250/256
Slice allocated to: Port ACLs
Slice ID: 5
Stage: Ingress
Mode: Single
Entries used: 500/512
Slice allocated to: Router ACLs
Slice ID: 7
Stage: Ingress
Mode: Double
Entries used: 10/128
Slice allocated to: OAM, Ethernet loopback, Y.1731 DMM
Slice ID: 3
Stage: Ingress
Mode: Double
Entries used: 15/128
Slice allocated to: CESoPSN-UDP, CEF, Layer-3 Control Protocols
Slice ID: 8
Stage: Ingress
Mode: Double
Entries used: 256/256
[no free entries available]
Slice allocated to: Quality Of Service
Configuring a service-policy fails because of insufficient resources.
Router(config-if-srv)# service-policy input policy2
Router(config-if-srv)#
*Mar 6 18:41:14.771: %Error: Not enough hardware resources to program this policy-map
*Mar 6 18:41:14.771: %QOS-6-POLICY_INST_FAILED:
Service policy installation failed
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-84
OL-23826-09
Chapter 24
Configuring QoS
Troubleshooting Tips
Router(config-if-srv)#
In the above scenario, you can free up the TCAM rules by unconfiguring the service-policy that is no
longer required or free up a slice by unconfiguring a feature that is no longer required.
Router(config-if-srv)# no service-policy input policy1
Router(config-if-srv)# end
Router#
Router# show platform tcam detailed
Ingress
: 8/8 slices, 2048/2048 entries used
Pre-Ingress: 3/4 slices, 768/1024 entries used
Egress
: 0/4 slices, 0/512 entries used
Slice ID: 1
Stage: Pre-Ingress
Mode: Single
Entries used: 29/256
Slice allocated to: Layer-2 Classify and Assign Group
Slice ID: 4
Stage: Pre-Ingress
Mode: Double
Entries used: 11/128
Slice allocated to: L2CP
Slice ID: 2
Stage: Ingress
Mode: Double
Entries used: 27/128
Slice allocated to: L2 Post-Switch Processing Group
Slice ID: 6
Stage: Ingress
Mode: Single
Entries used: 250/256
Slice allocated to: Port ACLs
Slice ID: 5
Stage: Ingress
Mode: Single
Entries used: 500/512
Slice allocated to: Router ACLs
Slice ID: 7
Stage: Ingress
Mode: Double
Entries used: 10/128
Slice allocated to: OAM, Ethernet loopback, Y.1731 DMM
Slice ID: 3
Stage: Ingress
Mode: Double
Entries used: 15/128
Slice allocated to: CESoPSN-UDP, CEF, Layer-3 Control Protocols
Slice ID: 8
Stage: Ingress
Mode: Double
Entries used: 195/256
[after unconfiguring policy1]
Slice allocated to: Quality Of Service
We now have enough free entries to configure policy2.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-85
Chapter 24
Configuring QoS
Troubleshooting Tips
Router(config-if-srv)# service-policy input policy2
Router(config-if-srv)#
Router# show platform tcam detailed
Ingress
: 8/8 slices, 2048/2048 entries used
Pre-Ingress: 3/4 slices, 768/1024 entries used
Egress
: 0/4 slices, 0/512 entries used
Slice ID: 1
Stage: Pre-Ingress
Mode: Single
Entries used: 29/256
Slice allocated to: Layer-2 Classify and Assign Group
Slice ID: 4
Stage: Pre-Ingress
Mode: Double
Entries used: 11/128
Slice allocated to: L2CP
Slice ID: 2
Stage: Ingress
Mode: Double
Entries used: 27/128
Slice allocated to: L2 Post-Switch Processing Group
Slice ID: 6
Stage: Ingress
Mode: Single
Entries used: 250/256
Slice allocated to: Port ACLs
Slice ID: 5
Stage: Ingress
Mode: Single
Entries used: 500/512
Slice allocated to: Router ACLs
Slice ID: 7
Stage: Ingress
Mode: Double
Entries used: 10/128
Slice allocated to: OAM, Ethernet loopback, Y.1731 DMM
Slice ID: 3
Stage: Ingress
Mode: Double
Entries used: 15/128
Slice allocated to: CESoPSN-UDP, CEF, Layer-3 Control Protocols
Slice ID: 8
Stage: Ingress
Mode: Double
Entries used: 220/256 [after configuring policy2]
Slice allocated to: Quality Of Service
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-86
OL-23826-09
Chapter 24
Configuring QoS
Additional References
Additional References
The following sections provide references related to bit error rate testing.
Related Documents
Related Topic
Document Title
Cisco IOS Commands
Cisco IOS Master Commands List, All Releases
ASR 901 Command Reference
Cisco ASR 901 Series Aggregation Services Router Command
Reference
Cisco IOS MQC Commands
Cisco IOS Quality of Service Solutions Command Reference
Standards
Standard
Title
None
—
MIBs
MIB
MIBs Link
None
To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
None
—
Technical Assistance
Description
Link
http://www.cisco.com/techsupport
The Cisco Technical Support website contains
thousands of pages of searchable technical content,
including links to products, technologies, solutions,
technical tips, and tools. Registered Cisco.com users
can log in from this page to access even more content.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
24-87
Chapter 24
Configuring QoS
Feature Information for Configuring QoS
Feature Information for Configuring QoS
Table 24-8 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 24-8
Table 24-8 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for Configuring QoS
Feature Name
Releases
Feature Information
ACL-based QoS
15.2(2)SNH1
This feature was introduced.
Shaper Burst Commit Size Down to 1 ms
15.2(2)SNI
The following section provides information about this
feature:
•
Traffic Shaping
Egress Policing
15.3(3)S
Support for Egress Policing was introduced on the Cisco
ASR 901 routers.
Multiaction Ingress Policer on EVC
15.3(3)S
Support for Multiaction Ingress Policer on EVC was
introduced on the Cisco ASR 901 routers.
QoS for MPLS over MLPPP
15.4(1)S
This feature was introduced on the Cisco ASR 901 routers.
The following sections provide information about this
feature:
•
QoS for MPLS/IP over MLPPP, page 24-31
•
Extending QoS for MLPPP, page 24-64
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
24-88
OL-23826-09
CH A P T E R
25
Configuring MLPPP
The Multilink Point-to-Point (MLPPP) feature provides load balancing functionality over multiple WAN
links, while providing multivendor interoperability, packet fragmentation and proper sequencing, and
load calculation on both inbound and outbound traffic.
Note
To get information on the basic configuration of MLPPP, see
http://www.cisco.com/en/US/docs/ios/12_2/dial/configuration/guide/dafppp.html.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for MLPPP” section on page 25-22.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
This section contains the following topics:
•
Prerequisites, page 25-2
•
Restrictions, page 25-2
•
MLPPP Optimization Features, page 25-2
•
Configuring MLPPP Backhaul, page 25-6
•
Additional References, page 25-21
•
Feature Information for MLPPP, page 25-22
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-1
Chapter 25
Configuring MLPPP
Prerequisites
Prerequisites
•
Cisco IOS Release 15.2(2)SNI or a later release that supports the Multiprotocol Label Switching
(MPLS) over MLPPP feature must be installed previously on the Cisco ASR 901 Series Aggregation
Services Router.
•
Cisco Express Forwarding (CEF) or distributed Cisco Express Forwarding (dCEF) should be
enabled.
•
MPLS should enabled on PE and P routers.
•
Before enabling MPLS over MLPPP link, configure the following commands:
– mpls label protocol ldp
– mpls ip (configure this command over MLPPP link where IP address has been enabled)
Restrictions
•
TE-FRR/LFA FRR feature is not supported on the MLPPP interface.
•
Virtual Routing and Forwarding (VRF) configuration is not supported on the MLPPP interface.
•
You need to shut down and bring up the MLPP interface for the following conditions:
– On the fly fragmentation enable or disable
– On the fly changes to the fragment size
– Link fragmentation interleave
– Enabling multiclass
•
If the CPU command is modified when IS-IS is configured, you should remove and re-apply the
service-policy in MLPPP.
MLPPP Optimization Features
The Cisco ASR 901 supports several features that improve the performance of Multilink Point-to-Point
Protocol (MLPPP) connections and related applications such as IP over MLPPP. Some important
features are given below:
•
Distributed Multilink Point-to-Point Protocol Offload
•
Multiclass MLPPP
•
MPLS over MLPPP
Distributed Multilink Point-to-Point Protocol Offload
Distributed Multilink Point-to-Point Protocol (dMLPPP) allows you to combine T1 or E1 connections
into a bundle that has the combined bandwidth of all of the connections in the bundle, providing
improved capacity and CPU utilization over MLPPP. The dMLPPP offload feature improves the
performance for traffic in dMLPPP applications such as IP over MLPPP by shifting processing of this
traffic from the main CPU to the network processor.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-2
OL-23826-09
Chapter 25
Configuring MLPPP
MLPPP Optimization Features
The Cisco ASR 901 supports one serial links per T1/E1 connection and up to 16 MLPPP bundles. You
can use the fixed T1/E1 ports to create up to 16 MLPPP links.
The Cisco ASR 901 implementation of multilink (dMLPPP) uses interleaving to allow short,
delay-sensitive packets to be transmitted within a predictable amount of time. Interleaving allows the
Cisco ASR 901 to interrupt the transmission of delay-insensitive packets in order to transmit
delay-sensitive packets. You can also adjust the responsiveness of the Cisco ASR 901 to delay-sensitive
traffic by adjusting the maximum fragment size; this value determines the maximum delay that a
delay-sensitive packet can encounter while the Cisco ASR 901 transmits queued fragments of
delay-insensitive traffic.
Multiclass MLPPP
The Cisco ASR 901 implementation of dMLPPP also supports Multiclass MLPPP. Multiclass MLPPP is
an extension to MLPPP functionality that allows you to divide traffic passing over a multilink bundle
into several independently sequenced streams or classes. Each multiclass MLPPP class has a unique
sequence number, and the receiving network peer processes each stream independently. The multiclass
MLPPP standard is defined in RFC 2686.
The Cisco ASR 901 supports the following multiclass MLPPP classes:
•
Class 0- Data traffic that is subject to normal MLPPP fragmentation. Appropriate for
non-delay-sensitive traffic.
•
Class 1- Data traffic that can be interleaved but not fragmented. Appropriate for delay-sensitive
traffic such as voice.
Note
By default, Multiclass MLPPP is enabled with two classes. Maximum number of classes supported is
also two.
Note
The Cisco ASR 901 does not support some PPP and MLPPP options when the bundle is offloaded to the
network processor; you can retain these options by disabling MLPPP and IPHC offloading for a given
bundle. For more information, see “MLPPP Offload” section on page 25-13.
Note
The output for the show ppp multilink command for an offloaded MLPPP bundle differs from the output
for a non-offloaded bundle.
MPLS over MLPPP
The Multiprotocol Label Switching (MPLS) support over Multilink PPP feature allows you to use
labeled switch paths (LSPs) over MLPPP links. In a network with Ethernet and MLPPP connections, this
feature supports MPLS over MLPPP links in the edge (PE-to-CE) or in the MPLS core (PE-to-PE and
PE-to-P) or at the end of MPLS labeled path (CE-to-PE) as PE router.
Note
QoS is not supported for MPLS over MLPPP.
This section contains the following topics:
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-3
Chapter 25
Configuring MLPPP
MLPPP Optimization Features
•
MPLS Features Supported for MLPPP
•
MPLS over MLPPP on PE-to-CE Links
•
MPLS over MLPPP on Core Links
•
MPLS over MLPPP on CE to PE Links
MPLS Features Supported for MLPPP
The following features are supported.
•
MPLS Label imposition (LER)
•
MPLS Label switching (LSR)
•
MPLS VPN (L3VPN): User-Network Interface (UNI) on which virtual routing and forwarding
(VRF) is configured should be switch virtual interface (SVI) on Gigabit interfaces and
Network-to-Network Interface(NNI) can be MLPPP link
•
Routing Protocols – ISIS/OSPF/BGP on MLPPP
•
Label Distribution Protocol (LDP) as MPLS label protocol
•
Equal Cost Multipath (ECMP) support on MLPPP links for IP to Tag (LER cases)
MPLS over MLPPP on PE-to-CE Links
Figure 1 shows a typical MPLS network in which the PE router is responsible for label imposition (at
ingress) and disposition (at egress) of the MPLS traffic.
In this topology, MLPPP is deployed on the PE-to-CE links.
PE to CE Links
CE
CE
LDP
LDP
P
PE
P
LDP
PE
CE
CE
MLP interfaces handling
MPLS labeled packets
303378
Figure 1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-4
OL-23826-09
Chapter 25
Configuring MLPPP
MLPPP Optimization Features
MPLS over MLPPP on Core Links
Figure 2 shows a sample topology in which MPLS is deployed over MLPPP on PE-to-P and P-to-P links.
Enabling MPLS on MLPPP for PE-to-P links is similar to enabling MPLS on MLPPP for P-to-P links.
PE-to-P and P-to-P links
CE
CE
LDP
LDP
P
P
LDP
PE
PE
CE
CE
MLP interfaces handling
MPLS labeled packets
303379
Figure 2
MPLS over MLPPP on CE to PE Links
Figure 3 shows a sample topology in which MPLS is deployed over MLPPP between CE and PE links
with LDP.
Figure 3
CE to PE Links
LDP
LDP
P1
P2
LDP
MLP interfaces handling
MPLS labeled packets
303380
CSC-CE2
CSC-PE2 CSC-CE1
CSC-CE1 CSC-PE1
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-5
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Configuring MLPPP Backhaul
To configure an MLPPP backhaul, complete the following tasks:
•
Configuring the Card Type, E1 and T1 Controllers, page 25-6
•
Configuring a Multilink Backhaul Interface, page 25-6
Configuring the Card Type, E1 and T1 Controllers
For information on configuring the card type, E1 and T1 controllers, see Chapter 18, Configuring T1/E1
Controllers.
Configuring a Multilink Backhaul Interface
A multilink interface is a virtual interface that represents a multilink PPP bundle. The multilink interface
coordinates the configuration of the bundled link, and presents a single object for the aggregate links.
However, the individual PPP links that are aggregated must also be configured. Therefore, to enable
multilink PPP on multiple serial interfaces, you first need to set up the multilink interface, and then
configure each of the serial interfaces and add them to the same multilink interface.
Note
In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
The Cisco ASR 901 router can support up to 16 E1/T1 connections through the multilink interface,
ranging from 16 bundles of one E1/T1 each to a single bundle containing 16 E1/T1 bundles.
Complete the following tasks to configure a multilink backhaul interface.
•
Creating a Multilink Bundle, page 25-6
•
Configuring MRRU, page 25-7
•
Configuring PFC and ACFC, page 25-8
•
Enabling Multilink and Identifying the Multilink Interface, page 25-11
•
Configuring a Serial Interface as a Member Link of a MLPPP Group, page 25-12
Creating a Multilink Bundle
Complete the following steps to create a multilink bundle:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface multilink group-number
4.
ip address address [subnet mask]
5.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-6
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Router(config)# interface multilink
group-number
Creates a multilink bundle and enters the interface configuration mode:
•
The example creates a multilink bundle 5.
Example:
Step 4
Router(config)# interface
multilink5
To remove a multilink bundle, use the no form of this command.
Router(config-if)# ip address
address [subnet mask]
Assigns an IP address to the multilink interface.
Example:
Step 5
group-number—Number of the multilink bundle.
•
address— IP address.
•
subnet mask—Network mask of IP address.
Router(config-if)# ip address
10.10.10.2 255.255.255.0
The example configures an IP address and subnet mask.
Router(config-if)# exit
Exits configuration mode.
Example:
Router(config-if)# exit
Configuring MRRU
You should configure the local maximum received reconstructed unit (MRRU) of the multilink bundle
to a value greater than or equal to 1508 bytes(or equal to the maximum packet length expected on the
bundle at any point in time). The maximum MTU supported on the Cisco ASR 901 router is 1536, and
MTU drops occur when the packet length is more than 1536.
Complete the following steps to configure MRRU:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface multilink group-number
4.
ppp multilink mru local bytes
5.
end
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-7
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface multilink
multilink-bundle-number
Creates a multilink bundle and enters the multilink interface configuration
mode to configure the multilink bundle.
•
Example:
multilink-bundle-number—Number of the multilink bundle. The
range is from 1 to 65535.
Router(config)# interface multilink
1
Step 4
ppp multilink mrru local bytes
Example:
Router(config-if)# ppp multilink
mrru local 1536
Step 5
Configures the MRRU value negotiated on a Multilink PPP bundle.
•
local—Configures the local MRRU value.
•
bytes—MRRU value, in bytes. Valid value range is 128 to 16384.
Exits configuration mode.
exit
Example:
Router(config)# exit
Configuring PFC and ACFC
Protocol-Field-Compression (PFC) and Address-and-Control-Field-Compression (AFC) are PPP
compression methods defined in RFCs 1661 and 1662. PFC allows for compression of the PPP Protocol
field; ACFC allows for compression of the PPP Data Link Layer Address and Control fields.
Follow these steps to configure PFC and ACFC handling during PPP negotiation to be configured. By
default, PFC/ACFC handling is not enabled.
Note
The recommended PFC and ACFC handling in the Cisco ASR 901 router is: acfc local request, acfc
remote apply, pfc local request, and pfc remote apply.
Configuring PFC
Complete the following steps to configure PFC handling during PPP negotiation:
SUMMARY STEPS
1.
enable
2.
configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-8
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
3.
interface multilink group-number
4.
ppp pfc local {request | forbid}
5.
ppp pfc remote {apply | reject | ignore}
6.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Router(config)# interface multilink
group-number
Creates a multilink bundle and enters the interface configuration mode:
•
Example:
Step 4
group-number—Number of the multilink bundle.
The example creates a multilink bundle 5.
Router(config)# interface
multilink5
To remove a multilink bundle, use the no form of this command.
Router(config-if)# ppp pfc local
{request | forbid}
Configures how the router handles PFC in its outbound configuration
requests, use the ppp pfc local command. The syntax is as follows:
•
request—The PFC option is included in outbound configuration
requests.
•
forbid—The PFC option is not sent in outbound configuration
requests, and requests from a remote peer to add the PFC option are
not accepted.
Example:
Router(config-if)# ppp pfc local
request
The example shows how to create a method for the router to manage PFC.
Step 5
Router(config-if)# ppp pfc remote
{apply | reject | ignore}
Specifies how the router manages the PFC option in configuration
requests received from a remote peer. The syntax is as follows:
•
apply—Specifies that PFC options are accepted and PFC may be
performed on frames sent to the remote peer.
•
reject—Specifies that PFC options are explicitly ignored.
•
ignore—Specifies that PFC options are accepted, but PFC is not
performed on frames sent to the remote peer.
Example:
Router(config-if)# ppp pfc remote
apply
The example shows how to allow PFC options to be accepted.
Step 6
Router(config-if)# exit
Exits configuration mode.
Example:
Router(config)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-9
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Configuring ACFC
Complete the following steps to configure ACFC handling during PPP negotiation:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface multilink group-number
4.
ppp acfc local {request | forbid}
5.
ppp acfc remote {apply | reject | ignore}
6.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
Router(config)# interface multilink
group-number
Creates a multilink bundle and enter the interface configuration mode:
•
Example:
Step 4
group-number—Number of the multilink bundle.
The example creates a multilink bundle 5.
Router(config)# interface multilink
5
To remove a multilink bundle, use the no form of this command.
Router(config-if)# ppp acfc local
{request | forbid}
Specifies how the router handles ACFC in outbound configuration
requests. The syntax is as follows:
•
request—Specifies that the ACFC option is included in outbound
configuration requests.
•
forbid—Specifies that the ACFC option is not sent in outbound
configuration requests, and requests from a remote peer to add the
ACFC option are not accepted.
Example:
Router(config-if)# ppp acfc local
request
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-10
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Step 5
Command
Purpose
Router(config-if)# ppp acfc remote
{apply | reject | ignore}
Specifies how the router handles the ACFC option in configuration
requests received from a remote peer. The syntax is as follows:
Example:
Router(config-if)# ppp acfc remote
apply
•
apply—ACFC options are accepted and ACFC may be performed on
frames sent to the remote peer.
•
reject—ACFC options are explicitly ignored.
•
ignore—ACFC options are accepted, but ACFC is not performed on
frames sent to the remote peer.
The example allows ACFC options to be accepted.
Step 6
Router(config-if)# exit
Exit configuration mode.
Example:
Router(config)# exit
Enabling Multilink and Identifying the Multilink Interface
Complete the following steps to enable multilink and identify the multilink interface:
Note
If you modify parameters for an MLPPP bundle while it is active, the changes do not take effect until the
Cisco ASR 901 renegotiates the bundle connection.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface multilink group-number
4.
keepalive [period [retries]]
5.
exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-11
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Step 3
Command
Purpose
Router(config-if)# interface
multilink group-number
Creates the multilink group interface corresponding to the specified group
number. This command enables the following commands under the
interface multilink group number:
Example:
1.
ppp multilink
Router(config-if)# interface
multilink 5
2.
ppp multilink group group-number
where group-number is the Multilink group number.
The example restricts (identifies) the multilink interface that can be
negotiated to multilink interface 5.
Step 4
Router(config-if)# keepalive
[period [retries]]
Example:
Enables keepalive packets on the interface and specifies the number of
times the keepalive packets are sent without a response before the router
disables the interface. The syntax is as follows:
•
period—(Optional) Integer value in seconds greater than 0. The
default is 10. Using 0 disables the keepalive option.
•
retries—(Optional) Specifies the number of times that the device will
continue to send keepalive packets without response before bringing
the interface down. Integer value greater than 1 and less than 255. If
omitted, the value that was previously set is used; if no value was
specified previously, the default of 5 is used.
Router(config-if)# keepalive 1 5
Step 5
Router(config-if)# exit
Exits configuration mode.
Example:
Router(config)# exit
Configuring a Serial Interface as a Member Link of a MLPPP Group
Complete the following steps to configure a serial interface as a member link of a MLPPP group:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface serial slot/port: channel-group-number
4.
encapsulation ppp
5.
ppp multilink
6.
ppp multilink group group-number
7.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-12
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Router# configure terminal
Step 3
Router(config-if)# interface serial
slot/port:channel-group-number
Identifies and accesses the serial interface on the specified slot and port.
•
Example:
channel-group-number—ID number to identify the channel group.
The valid range is from 0–30 for E1 controllers and 0–23 for T1
controllers.
Router(config-if)# interface serial
0/5:5
Step 4
Enables PPP encapsulation on the serial interface.
Router(config-if)# encapsulation
ppp
Example:
Router(config-if)# encapsulation
ppp
Step 5
Enables multilink PPP on the serial interface.
Router(config-if)# ppp multilink
Example:
Router(config-if)# ppp multilink
Step 6
Configures the serial interface as a member link to the multilink interface
identified by the group-number.
Router(config-if)# ppp multilink
group group-number
•
Example:
Step 7
group-number—Multilink group number.
Router(config-if)# ppp multilink
group 5
The example identifies the multilink interface to which the serial interface
should be bound to as a member-link.
Router(config-if)# exit
Exits configuration mode.
Example:
Router(config)# exit
MLPPP Offload
By default, the Cisco ASR 901 router offloads processing for distributed MLPPP (dMLPPP) to the
network processor for improved performance. However, the Cisco ASR 901 does not support some
dMLPPP settings on offloaded bundles. The Cisco ASR 901 does not support the following options on
offloaded dMLPPP bundles:
•
ppp multilink idle-link
•
ppp multilink queue depth
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-13
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Note
•
ppp multilink fragment maximum
•
ppp multilink slippage
•
ppp timeout multilink lost-fragment
If you have a bundle that requires the use of these options, contact Cisco support for assistance.
Configuring Additional MLPPP Settings
You can perform a variety of other configurations on an MLPPP bundle, including the following:
Note
•
Modifying the maximum fragment size
•
Modifying fragmentation settings
•
Enabling or disabling fragmentation
•
Enabling or disabling interleaving
•
Configuring multiclass MLPPP
For more information about configuring MLPPP, see theDial Configuration Guide, Cisco IOS Release
15.0S.
Configuring MPLS over the MLPPP on a Serial Interface
Complete the following steps to configure MPLS over the MLPPP link on a serial interface:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface serial slot/port:time-slot
4.
no ip address
5.
encapsulation encapsulation-type
6.
ppp multilink
7.
ppp multilink group group-number
8.
exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-14
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface serial
slot/port:time-slot
Specifies a serial interface created on a channelized E1 or channelized T1
controller:
•
slot—Slot number where the channelized E1 or T1 controller is
located.
•
port—Port number where the channelized E1 or T1 controller is
located.
•
time-slot—For ISDN, the D channel time slot, which is the :23
channel for channelized T1 and the :15 channel for channelized E1.
PRI time slots are in the range from 0 to 23 for channelized T1 and in
the range from 0 to 30 for channelized E1.
Example:
Router(config-if)# interface
Serial0/0:0
Step 4
no ip address
Disabled IP address processing.
Example:
Router(config-if)# no ip address
Step 5
encapsulation encapsulation-type
Configures the encapsulation method used by the interface.
•
encapsulation-type—Encapsulation type.
Example:
Router(config-if)# encapsulation
ppp
Step 6
ppp multilink
Enables Multilink PPP on an interface .
Example:
Router(config-if)# ppp multilink
Step 7
ppp multilink group group-number
Example:
Restricts a physical link to join only one designated multilink group
interface.
•
group-number—Multilink-group number (a non-zero number).
Router(config-if)# ppp multilink
group 2
Step 8
exit
Exits interface configuration mode.
Example:
Router(config)# exit
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-15
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Configuring MPLS over MLPPP for OSPF
Complete the following steps to configure MPLS over the MLPPP link for OSPF:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface multilink group-number
4.
ip address address [subnet mask]
5.
ip ospf process-id area area-id
6.
ip ospf authentication null
7.
mpls ip
8.
no keepalive
9.
ppp pfc local request
10. ppp pfc remote apply
11. ppp multilink
12. ppp multilink group group-number
13. ppp multilink endpoint string char-string
14. exit
15. router ospf process-id [vrf vrf-name]
16. network ip-address wildcard-mask area area-id
17. exit
DETAILED STEPS
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
interface multilink group-number
Example:
Creates the multilink group interface corresponding to the specified group
number, and enters the interface configuration mode.
•
group-number—Multilink group number.
Router(config)# interface multilink
2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-16
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Step 4
Command
Purpose
ip address address [subnet mask]
Assigns an IP address to the multilink interface.
Example:
Router(config-if)# ip address
11.11.11.2 255.255.255.0
Step 5
ip ospf process-id area area-id
Example:
Router(config-if)# ip router isis
Step 6
ip ospf authentication null
•
address—IP address.
•
subnet mask—Network mask of IP address.
Enables OSPF on an interface.
•
process-id—A decimal value in the range from 1 to 65535.
•
area-id—A decimal value in the range from 0 to 4294967295, or an
IP address.
Specifies the authentication type for an interface.
•
Example:
null—No authentication is used. Useful for overriding password or
message-digest authentication if configured for an area.
Router(config-if)# ip ospf
authentication null
Step 7
mpls ip
Enables MPLS forwarding of IPv4 packets along normally routed paths
for a particular interface.
Example:
Router(config-if)# mpls ip
Step 8
no keepalive
Disables keepalive packets.
Example:
Router(config-if)# no keepalive
Step 9
ppp pfc local request
Configures protocol field compression (PFC) in configuration requests.
Example:
Router(config-if)# ppp pfc local
request
Step 10
ppp pfc remote apply
Configures how the PFC option in configuration requests is received from
a remote peer.
Example:
Router(config-if)# ppp pfc remote
apply
Step 11
ppp multilink
Enables Multilink PPP on an interface.
Example:
Router(config-if)# ppp multilink
Step 12
ppp multilink group group-number
Example:
Restricts a physical link to join only one designated multilink group
interface.
•
group-number—Multilink-group number (a nonzero number).
Router(config-if)# ppp multilink
group 2
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-17
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
Step 13
Command
Purpose
ppp multilink endpoint string
char-string
Restricts a physical link to join only one designated multilink group
interface.
•
char-string—Character string.
Example:
Router(config-if)# ppp multilink
endpoint string 22
Step 14
Exits interface configuration mode.
exit
Example:
Router(config)# exit
Step 15
router ospf process-id [vrf
vrf-name]
Configures an OSPF routing process and enters the router configuration
mode.
•
Example:
Router(config)# router ospf 1234
Step 16
network ip-address wildcard-mask
area area-id
Example:
Router(config-router)# network
6.6.6.6 0.0.0.0 area 2
Configures the interfaces on which OSPF runs and to define the area ID
for those interfaces.
•
ip-address—IP address.
•
wildcard-mask—IP-address-type mask that includes optional bits.
•
area-id—Area that is to be associated with the OSPF address range.
It can be specified as either a decimal value or as an IP address. If you
intend to associate areas with IP subnets, you can specify a subnet
address as the value of the area-id argument.
Note
Step 17
process-id— Internally used identification parameter for an OSPF
routing process. It is locally assigned and can be any positive integer.
A unique value is assigned for each OSPF routing process.
Repeat this step to configure different interfaces on which OSPF
runs, and to define the area ID for those interfaces.
Exits the router configuration mode.
exit
Example:
Router(config-router)# exit
Configuration Examples for MPLS over MLPPP
The following example shows a sample configuration of MPLS over MLPPP for OSPF.
Building configuration...
Current configuration : 234 bytes
!
interface Multilink2
ip address 11.11.11.2 255.255.255.0
ip ospf 1234 area 0
ip ospf authentication null
mpls ip
no keepalive
ppp pfc local request
ppp pfc remote apply
ppp multilink
ppp multilink group 2
ppp multilink endpoint string 22
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-18
OL-23826-09
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
router ospf 1234
network 6.6.6.6 0.0.0.0 area 2
network 11.11.11.0 0.0.0.255 area 0
network 12.12.12.0 0.0.0.255 area 2
The following example shows a sample configuration of MPLS over MLPPP for a Serial Interface.
Building configuration...
Current configuration : 101 bytes
!
interface Serial0/0:0
no ip address
encapsulation ppp
ppp multilink
ppp multilink group 2
Verifying MPLS over MLPPP Configuration
To verify the configuration of MPLS over MLPPP, use the following commands as shown in the
examples below:
Router# ping mpls ipv4 6.6.6.6/32
Sending 5, 100-byte MPLS Echos to 6.6.6.6/32,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/8 ms
Total Time Elapsed 40 ms
Router# show mpls ldp bindings 6.6.6.6 32
lib entry: 6.6.6.6/32, rev 8
local binding: label: 17
remote binding: lsr: 6.6.6.6:0, label: imp-null
Router# traceroute mpls ipv4 6.6.6.6/32
Tracing MPLS Label Switched Path to 6.6.6.6/32, timeout is 2 seconds
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-19
Chapter 25
Configuring MLPPP
Configuring MLPPP Backhaul
'R' - transit router, 'I' - unknown upstream index,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort.
0 11.11.11.1 MRU 1500 [Labels: implicit-null Exp: 0]
! 1 11.11.11.2 4 ms
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-20
OL-23826-09
Chapter 25
Configuring MLPPP
Additional References
Additional References
The following sections provide references related to MLPPP feature.
Related Documents
Related Topic
Document Title
Cisco IOS Commands
Cisco IOS Master Commands List, All Releases
ASR 901 Commands
Cisco ASR 901 Series Aggregation Services Router Command
Reference
Cisco IOS Dial Technologies Configuration Guide
Configuring Media-Independent PPP and Multilink PPP
MPLS over MLPPP
MPLS—Multilink PPP Support
Standards
Standard
Title
None
—
MIBs
MIB
MIBs Link
None
To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFC
Title
None
—
Technical Assistance
Description
Link
http://www.cisco.com/techsupport
The Cisco Technical Support website contains
thousands of pages of searchable technical content,
including links to products, technologies, solutions,
technical tips, and tools. Registered Cisco.com users
can log in from this page to access even more content.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
25-21
Chapter 25
Configuring MLPPP
Feature Information for MLPPP
Feature Information for MLPPP
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software
release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.
An account on Cisco.com is not required.
Note
Table 1
Table 1 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Feature Information for MLPPP
Feature Name
Releases
Feature Information
MPLS over MLPPP
15.2(2)SNI
This feature was introduced on the Cisco ASR 901 routers.
The following sections provide information about this
feature:
•
MPLS over MLPPP, page 25-3
•
Configuring MPLS over the MLPPP on a Serial
Interface, page 25-14
•
Configuring MPLS over MLPPP for OSPF, page 25-16
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
25-22
OL-23826-09
CH A P T E R
26
Onboard Failure Logging
Onboard Failure Logging (OBFL) captures and stores hardware failure and environmental information
into nonvolatile memory. OBFL permits improved accuracy in hardware troubleshooting and root cause
isolation analysis. Stored OBFL data can be retrieved in the event of a router crash or failure.
Contents
•
Understanding OBFL, page 26-1
•
Configuring OBFL, page 26-2
•
Verifying OBFL Configuration, page 26-2
Understanding OBFL
OBFL provides a mechanism to store hardware, software, and environment related critical data in a
non-volatile memory, such as flash EPROM or EEPROM on routers. The logging information is used by
the TAC team to troubleshoot and fix hardware issues.
OBFL collects data like temperatures and voltages. It stores the data in a dedicated area of the flash
memory of the router. This data is retrieved by TAC personnel to troubleshoot routers. It can also be
analyzed by back-end software to detect failure patterns, and possibly to recommend specific quality
improvements.
Retrieval of the OBFL message
If the hardware is defective and the system cannot boot up, any data in flash is inaccessible. In that case,
use any one of the following methods to recover OBFL data:
•
Read the flash through JTAG: this requires provisions in hardware design and back-end hardware
and software support tools.
•
Repair the system; boot it; use the OBFL CLI commands.
Recording OBFL Messages
Data is recorded in any of the following formats:
•
Continuous information that displays a snapshot of measurements.
•
Samples in a continuous file, and summary information about the data being collected.
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
26-1
Chapter 26
Onboard Failure Logging
Configuring OBFL
Configuring OBFL
Use the following commands to configure and verify OBFL:
Command
Purpose
Router(conf)# hw-module {all|slot|module}
{slotnumber/subslotnumber|modulenumber}
logging onboard
Enables OBFL on the specified hardware module.
The no form of the command disables OBFL.
Example:
Router(conf)# hw-module module 0 logging
onboard
Router> show logging onboard
{slot|module}
{slotnumber/subslotnumber|modulenumber}
[status]
Shows the status of OBFL logging.
Router(conf)# clear logging onboard
Clears OBFL logging.
OBFL is enabled by default in Cisco ASR 901.
Verifying OBFL Configuration
Example 1
Router# show logging onboard status
Devices registered with infra
Slot no.: 0 Subslot no.: 0, Device obfl0:
Application name clilog :
Path : obfl0:
CLI enable status : enabled
Platform enable status: enabled
Application name temperature :
Path : obfl0:
CLI enable status : enabled
Platform enable status: enabled
Example 2
Router # show logging onboard temperature ?
continuous Onboard logging continuous information
detail Onboard logging detailed information
end ending time and date
raw Onboard logging raw information
start starting time and date
status Onboard logging status information
summary Onboard logging summary information
Router# show logging onboard temperature continuous
-------------------------------------------------------------------------------TEMPERATURE CONTINUOUS INFORMATION
-------------------------------------------------------------------------------Sensor | ID |
-------------------------------------------------------------------------------System 1
--------------------------------------------
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
26-2
OL-23826-09
Chapter 26
Onboard Failure Logging
Verifying OBFL Configuration
Time Stamp |Sensor Temperature 0C
MM/DD/YYYY HH:MM:SS | 1
-------------------------------------------03/01/2000 00:06:02 37
03/01/2000 00:16:02 37
03/01/2000 00:05:57 36
Router# show logging onboard voltage continuous
-----------------------------------------------------------------------------------------------------------------VOLTAGE CONTINUOUS INFORMATION
-----------------------------------------------------------------------------------------------------------------Sensor | ID |
-----------------------------------------------------------------------------------------------------------------12.00VA 0
1.50V 1
1.25V 2
12.00VB 3
2.50V 4
1.05V 5
1.20V 6
1.80V 7
-----------------------------------------------------------------------------------------------------------------Time Stamp |Sensor Voltage
MM/DD/YYYY HH:MM:SS | 12.00VA 1.50V 1.25V 12.00VB 2.50V 1.05V 1.20V
1.80V
-----------------------------------------------------------------------------------------------------------------02/24/2000 21:41:58 11.764 1.176 1.176 7.843 2.352 0.784 1.176
1.568
02/24/2000 21:46:00 11.764 1.176 1.176 7.843 2.352 0.784 1.176
1.568
02/25/2000 14:29:53 11.764 1.176 1.176 7.843 2.352 0.784 1.176
1.568
02/25/2000 14:33:54 11.764 1.176 1.176 7.843 2.352 0.784 1.176
1.568
Router# sh logging onboard clilog summary
-------------------------------------------------------------------------------CLI LOGGING SUMMARY INFORMATION
-------------------------------------------------------------------------------COUNT COMMAND
-------------------------------------------------------------------------------1 clear logging onboard
2 hw-module module 0 logging onboard message level 1
1 hw-module module 0 logging onboard message level 2
5 hw-module module 0 logging onboard message level 3
2 no hw-module module 0 logging onboard message level
5 show logging onboard
2 show logging onboard clilog
2 show logging onboard clilog continuous
1 show logging onboard clilog summary
2 show logging onboard continuous
1 show logging onboard environment
9 show logging onboard message
9 show logging onboard message continuous
1 show logging onboard message summary
3 show logging onboard status
1 show logging onboard temperature
1 show logging onboard voltage
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
26-3
Chapter 26
Onboard Failure Logging
Verifying OBFL Configuration
1 test logging onboard error 3
1 test logging onboard error1 3
1 test logging onboard try 1
--------------------------------------------------------------------------------
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
26-4
OL-23826-09
CH A P T E R
27
Hot Standby Router Protocol and Virtual Router
Redundancy Protocol
This feature module describes the HOT Standby Router Protocol(HSRP) and Virtual Router Redundancy
Protocol(VRRP) features. The Hot Standby Router Protocol (HSRP) is a First Hop Redundancy Protocol
(FHRP) designed to allow transparent fail-over of the first-hop IP router. HSRP provides high network
availability by providing first-hop routing redundancy for IP hosts on Ethernet, Fiber Distributed Data
Interface (FDDI), Bridge-Group Virtual Interface (BVI), LAN Emulation (LANE), or Token Ring
networks configured with a default gateway IP address. HSRP is used in a group of routers for selecting
an active router and a standby router.
The Virtual Router Redundancy Protocol (VRRP) eliminates the single point of failure inherent in the
static default routed environment . VRRP is not an election protocol in itself; rather it specifies an
election protocol that dynamically assigns responsibility for a virtual router.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature
information and caveats, see the release notes for your platform and software release. To find information
about the features documented in this module, and to see a list of the releases in which each feature is
supported, see the “Feature Information for HSRP and VRRP” section on page 27-11.
Use Cisco Feature Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on
Cisco.com is not required.
Contents
•
Information About HSRP and VRRP, page 27-2
•
How to Configure HSRP, page 27-3
•
Configuration Examples for HSRP, page 27-5
•
How to Configure VRRP, page 27-6
•
Configuration Examples for VRRP, page 27-8
•
Where to Go Next
•
Additional References, page 27-9
Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide
OL-23826-09
27-1
Chapter 27
Hot Standby Router Protocol and Virtual Router Redundancy Protocol
Information About HSRP and VRRP
•
Feature Information for HSRP and VRRP, page 27-11
Information About HSRP and VRRP
•
Overview of HSRP and VRRP
•
Text Authentication
•
Preemption
Overview of HSRP and VRRP
HSRP provides network redundancy for IP networks, which helps maximum network uptime. By sharing
an IP address and a MAC (Layer 2)