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.
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.
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-
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 Gener
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 Downlo
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
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 VL
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
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 CF
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 Configur
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 Confi
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 Exam
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 1
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 CHAPT
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 M
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 Synchr
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
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
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-Monitorin
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 MP
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 Configuri
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 Referen
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 Docume
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 Prerequisi
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 Ne
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 Te
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 sess
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
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
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 R
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
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 R
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-
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 Disabl
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
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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 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 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 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.
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).
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).
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.
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.
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.
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.
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.
Chapter 2 Licensing Licenses Supported on Cisco ASR 901 Router Sl.No.
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.
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.
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.
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.
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
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?
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
Chapter 6 Software Upgrade Auto Upgrade of ROMMON Auto Upgrade of ROMMON Upgradable rommon is bundled with the IOS image.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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—creat
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, pa
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.
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.
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.
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.
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.
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.
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 (conf
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 Statist
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 excee
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-proto
Chapter 8 Configuring Ethernet Virtual Connections Additional References Additional References The following sections provide references related to Configuring EVC feature.
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.
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.
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.
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.
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).
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.
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.
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.
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 Ether
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.
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)
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 OAMP
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 thresh
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
Chapter 11 ITU-T Y.1731 Performance Monitoring Information About ITU-T Y.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
Chapter 11 ITU-T Y.
Chapter 11 ITU-T Y.
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.
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.
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.
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.
Chapter 11 ITU-T Y.1731 Performance Monitoring Configuration Examples for IP SLAs Y.
Chapter 11 ITU-T Y.1731 Performance Monitoring Additional References Additional References The following sections provide references to ITU-T Y.1731 Performance Monitoring.
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.
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.
Chapter 11 ITU-T Y.1731 Performance Monitoring Feature Information for ITU-T Y.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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-grou
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.
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.
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).
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.
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-
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 Pre
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 configurat
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.
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
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.
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.
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.
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...
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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...
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
Chapter 21 Configuring Pseudowire Additional References Additional References The following sections provide references related to inverse multiplexing over ATM.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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
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.
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.
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/
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 / Configures ToD on 1588V2. Router(config-ptp-clk)# 1pps-out <1 PPS offset in ns> Configures 1 PPS output parameters.
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.
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.
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 MPLSL
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 • “Clas
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.
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 wit
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 pe
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Chapter 24 Configuring QoS Configuring Quality of Service (QoS) Slice allocated to: OAM, Ethernet loopback, Y.
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.
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.
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.
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 permi
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.
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.
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
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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...
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...
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...
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 o
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.
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.
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.
Chapter 24 Configuring QoS Troubleshooting Tips 2. To free up a slice by unconfiguring features that are no longer required.
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.
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:
Chapter 24 Configuring QoS Additional References Additional References The following sections provide references related to bit error rate testing.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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...
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.
Chapter 25 Configuring MLPPP Additional References Additional References The following sections provide references related to MLPPP feature.
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.
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.
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.
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 ------------------------------------------------------------------------------------
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.
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) address, two or more routers can act as a single virtual router.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol How to Configure HSRP The standby delay minimum reload interface configuration command delays HSRP groups from initializing for the specified time after the interface comes up. This command is different from the standby preempt delay interface configuration command, which enables HSRP preemption delay. You can disable the preemptive scheme by using the no vrrp preempt command.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol How to Configure HSRP 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 Configures an interface type and enters interface configuration mode.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol Configuration Examples for HSRP Step 9 Command or Action Purpose standby [group-number] track object-number [decrement priority-decrement] Configures HSRP to track an object and change the Hot Standby priority on the basis of the state of the object. Example: Router(config-if)# standby 1 track 100 decrement 20 Step 10 Returns to privileged EXEC mode.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol How to Configure VRRP Router# configure terminal Router(config)# interface Vlan10 Router(config-if)# ip address 10.10.10.22 255.255.255.0 Router(config-if)# standby 1 ip 10.10.10.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol How to Configure VRRP 7. vrrp [group-number] priority level 8. vrrp [group-number] authentication text string 9. vrrp [group-number] track object-number [decrement priority-decrement] 10. end 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.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol Configuration Examples for VRRP Step 9 Command or Action Purpose vrrp [group-number] track object-number [decrement priority-decrement] Configures VRRP to track an object and change the Hot Standby priority on the basis of the state of the object. Example: Router(config-if)# vrrp 2 track 1 decrement 20 Step 10 Returns to privileged EXEC mode.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol Where to Go Next Router# configure terminal Router(config)# interface Vlan10 Router(config-if)# ip address 10.10.10.26 255.255.255.0 Router(config-if)# vrrp 2 ip 10.10.10.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol 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.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol Feature Information for HSRP and VRRP Feature Information for HSRP and VRRP 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.
Chapter 27 Hot Standby Router Protocol and Virtual Router Redundancy Protocol Feature Information for HSRP and VRRP Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 27-12 OL-23826-09
CH A P T E R 28 Configuring Link Layer Discovery Protocol This feature module describes how to configure Link Layer Discovery Protocol (LLDP) on the Cisco ASR 901 Aggregation Series Router. The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over the data-link layer (Layer 2) on all Cisco-manufactured devices (routers, bridges, access servers, and switches).
Chapter 28 Configuring Link Layer Discovery Protocol Restrictions for LLDP Restrictions for LLDP The following are the restrictions for LLDP: • The memory available on a given end network device dictates the number of neighbor entries recorded. However, under most operating conditions, end devices such as printers, IP phones, workstations and so on, are typically operated in the receive mode only. • If Entity MIB are used for LLDP broadcast, such as to create a sender ID.
Chapter 28 Configuring Link Layer Discovery Protocol How to Configure LLDP 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 lldp run Enables LLDP globally on all the interfaces on the router. Example: Router(config)# lldp run or lldp holdtime seconds Specifies the hold time.
Chapter 28 Configuring Link Layer Discovery Protocol Configuration Example for LLDP Verifying LLDP To verify LLDP on the Cisco ASR 901 router, use the show command as shown in the following example.
Chapter 28 Configuring Link Layer Discovery Protocol Configuration Example for LLDP Example: Configuring Delay Time Router> enable Router# configure terminal Router(config)# lldp reinit 2 Router(config)# end Example: Configuring Intervals Router> enable Router# configure terminal Router(config)# lldp timer 75 Router(config)# end Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide OL-23826-09 28-5
Chapter 28 Configuring Link Layer Discovery Protocol Where to Go Next This is an example to enable an LLDP TLV on a supported interface: Router> enable Router# configure terminal Router(config)# interface ethernet 0/1 Router(config-if)# lldp tlv-select system-description Router(config-if)# end Where to Go Next For additional information on configuring LLDP, see the documentation listed in the “Related Documents” section on page 28-7.
Chapter 28 Configuring Link Layer Discovery Protocol 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 Standards Standard Title None — MIBs MIB MIBs Link None To locate and download MI
Chapter 28 Configuring Link Layer Discovery Protocol Feature Information for LLDP 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.
CH A P T E R 29 Configuring Multihop Bidirectional Forwarding Detection Cisco ASR 901 supports Bidirectional Forwarding Detection(BFD) on arbitrary paths, which can span multiple network hops. The multihop BFD feature provides subsecond forwarding failure detection for a destination with more than one hop and up to 255 hops. A multihop BFD session is set up between a unique source-destination address pair provided by the client. A session can be set up between two endpoints that have IP connectivity.
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection Restrictions for Multihop BFD Restrictions for Multihop BFD The following are the restrictions for multihop BFD: • BFD does not support echo mode. You can configure sessions for minimum timer interval. • The minimum guaranteed timer depends on the topology, scale, number of hops, and control plane processing. All the packets must reach the control plane since echo mode is not supported. • Supports IPv4 deployments only.
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection How to Configure Multihop BFD 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 bfd-template multi-hop template-name Creates a BFD multihop BFD template and enters BFD configuration mode.
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection Configuration Examples for Multihop BFD Configuring a Multihop BFD Map After configuring the interval timers and authentication in a template, you must configure a map to associate the template with unique source-destination address pairs for multihop BFD sessions. SUMMARY STEPS 1. enable 2. configure terminal 3. bfd mapipv4 vrf vrf-name destination-address/length source-address/length template-name 4.
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection Where to Go Next ! interface Fast Ethernet 0/1 ip address 172.16.10.1 255.255.255.0 bfd interval 50 min_rx 50 multiplier 3 ! interface Fast Ethernet 3/0.1 ip address 172.17.0.1 255.255.255.0 ! ! router bgp 40000 bgp log-neighbor-changes neighbor 172.16.10.2 remote-as 45000 neighbor 172.16.10.2 fall-over bfd ! address-family ipv4 neighbor 172.16.10.2 activate no auto-summary no synchronization network 172.18.0.0 mask 255.255.255.
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection 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 Standards Standard Title None — MIBs MIB MIBs Link None To locate
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection Feature Information for Multihop BFD 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.
Chapter 29 Configuring Multihop Bidirectional Forwarding Detection Feature Information for Multihop BFD Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 29-8 OL-23826-09
CH A P T E R 30 Bit Error Rate Testing This feature module describes how to configure a Bit Error Rate Test (BERT) and display the test results for channelized line cards in the Cisco ASR 901 Series Aggregation Services Routers. 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.
Chapter 30 Bit Error Rate Testing Feature Overview • To determine if the remote serial port returns the BERT pattern unchanged, you must manually enable network loopback at the remote serial port while you configure a BERT pattern to use in the test at specified time intervals on the local serial port. • BERT affects the functionality of any configured protocol on a controller on which it is initiated.
Chapter 30 Bit Error Rate Testing How to Configure BERT • Terminating BERT on a T1/E1 Controller, page 30-3 (Required) • Verifying BERT on a T1/E1 Controller, page 30-4 (Optional) Performing BERT on a T1/E1 Line To enable BERT pattern on a T1 or E1 controller, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller {t1 | e1} slot/port 4. bert pattern pattern interval time DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode.
Chapter 30 Bit Error Rate Testing How to Configure BERT 4. no bert pattern pattern interval time 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 {t1 | e1} slot/port Selects a T1 or E1 controller and enters controller configuration mode.
Chapter 30 Bit Error Rate Testing Configuration Examples Configuration Examples The following is a sample configuration of the BERT feature. Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#controller e1 0/9 Router(config-controller)#bert pattern 2^15 interval 1 Additional References The following sections provide references related to bit error rate testing.
Chapter 30 Bit Error Rate Testing Feature Information for 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 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
Chapter 30 Bit Error Rate Testing Feature Information for Bit Error Rate Testing 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.
Chapter 30 Bit Error Rate Testing Feature Information for Bit Error Rate Testing Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 30-8 OL-23826-09
CH A P T E R 31 Microwave ACM Signaling and EEM Integration This feature module describes the Microwave Adaptive Code Modulation (ACM) Signaling and Embedded Event Manager (EEM) integration, which 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. Finding Feature Information Your software release may not support all the features documented in this module.
Chapter 31 Microwave ACM Signaling and EEM Integration Feature Overview Prerequisites • The microwave transceiver in the network topology must support adaptive bandwidth modulation, and the microwave transceiver must support the Ethernet Connectivity Fault Management (CFM) extension for microwave devices as defined by Cisco. • In a heterogeneous ring topology, all devices connected directly to the microwave transceiver must support signal degradation (SD) functions.
Chapter 31 Microwave ACM Signaling and EEM Integration Feature Overview H-QoS Policy Adjustment H-QoS policy adjustment is the process of adjusting the egress H-QoS policy parameters on the IP/MPLS access node connected to the microwave link. This modifies the parent shaper rate to match the current bandwidth of the microwave link. It also adjusts the child class parameters to ensure correct priority and bandwidth-guaranteed traffic.
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration This section describes how to configure Microwave ACM Signaling and EEM Integration: • Configuring Connectivity Fault Management, page 31-4 (Required) • Configuring EEP Applet Using CLIs, page 31-7 (Required) • Configuring Event Handler, page 31-9 (Required) • Verifying Microwave Microwave ACM Signaling and EEM Integration
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration 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.
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration Step 8 Command Purpose exit Exits Ethernet EVC configuration mode and enters global configuration mode. Example: Router(config-evc)# exit Step 9 interface type number Specifies an interface type and number, and enters interface configuration mode.
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration Configuring EEP Applet Using CLIs To configure EEP applet, complete the following steps: Prerequisites Note • One switch virtual interface (SVI) or bridge domain is required per physical link. • One EEM script is required per physical link. The EEM script configures the metric on the microwave link and adjusts the QoS policy based on the Ethernet event parameters.
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration Step 4 Command Purpose event tag event-tag ethernet microwave clear-sd {interface type number} Specifies the event criteria for an EEM applet that is run by matching a Cisco IOS command-line interface (CLI). • tag—Specifies a tag using the event-tag argument that can be used with the trigger command to support multiple event statements within an applet.
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration Step 8 Command Purpose action action-id cli command cli-string Specifies the action of executing a Cisco IOS CLI command when an EEM applet is triggered. • action-id—Unique identifier that can be any string value. Actions are sorted and run in ascending alphanumeric key sequence using the label as the sort key.
Chapter 31 Microwave ACM Signaling and EEM Integration How to Configure Microwave ACM Signaling and EEM Integration Step 3 Command Purpose interface type number Specifies an interface type and number, and enters interface configuration mode. Example: Router(config)# interface vlan 40 Step 4 ethernet event microwave hold-off seconds Configures the settings of the Ethernet microwave event. • hold-off—Specifies the microwave bandwidth degradation hold-off time, in seconds.
Chapter 31 Microwave ACM Signaling and EEM Integration Configuration Examples for Microwave ACM Signaling and EEM Integration To display microwave bandwidth statistics of an interface, use the following show command.
Chapter 31 Microwave ACM Signaling and EEM Integration Configuration Examples for Microwave ACM Signaling and EEM Integration event tag event_cd ethernet microwave clear-sd interface GigabitEthernet0/10 event tag event_sd ethernet microwave sd interface GigabitEthernet0/10 threshold 1000 trigger correlate event event_cd or event event_sd ! Variable settings action 100 set olc "100" action 102 set dlc "1" action 104 set n "$_ring_nodes" action 106 set cb "$_ethernet_current_bw" action 108 set nb "$_ethern
Chapter 31 Microwave ACM Signaling and EEM Integration Configuration Examples for Microwave ACM Signaling and EEM Integration # action 233 action 234 syslog msg "233: cname: $cname" end ! Calculate bandwidth for each of the classes action 236 regexp "(priority|bandwidth) percent (.
Chapter 31 Microwave ACM Signaling and EEM Integration Configuration Examples for Microwave ACM Signaling and EEM Integration action 338 action 340 cli command "shape average $cb_bps" cli command "service-policy $s1$cpmap" ! Apply the QoS policy on a PHY interface action action action action 344 cli command "int $_ethernet_intf_name" 346 cli command "no service-policy output $pmap" 348 cli command "service-policy output $s1$pmap" 390 end ! End of the QoS part ! IGP metric block action action action
Chapter 31 Microwave ACM Signaling and EEM Integration Configuration Examples for Microwave ACM Signaling and EEM Integration Example: Configuring Event Handler The following is a sample configuration of Event Handler.
Chapter 31 Microwave ACM Signaling and EEM Integration Additional References Additional References The following sections provide references related to Microwave ACM Signaling and EEM Integration feature. Related Documents Related Topic Document Title Cisco IOS Commands Cisco IOS Master Commands List, All Releases Cisco ASR 901 Router Commands Cisco ASR 901 Series Aggregation Services Router Command Reference G.
Chapter 31 Microwave ACM Signaling and EEM Integration Feature Information for Microwave ACM Signaling and EEM Integration Feature Information for Microwave ACM Signaling and EEM Integration Table 31-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.
Chapter 31 Microwave ACM Signaling and EEM Integration Feature Information for Microwave ACM Signaling and EEM Integration Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 31-18 OL-23826-09
CH A P T E R 32 IPv6 Support on the Cisco ASR 901 Router This document provides implementation and command reference information for IPv6 features supported on the Cisco ASR 901 router. We strongly recommend that you read this entire document before reading other documents on IPv6 for Cisco IOS software. Detailed conceptual information about the features supported on the Cisco ASR 901 router, is documented outside of this feature in the Cisco IOS software documentation.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Prerequisites for IPv6 Support on the Cisco ASR 901 Router Prerequisites for IPv6 Support on the Cisco ASR 901 Router • Cisco IOS Release 15.2(2)SNG or a later IPv6-supporting release must be installed previously on the Cisco ASR 901 Series Aggregation Services Router.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Information About IPv6 Support on the Cisco ASR 901 Router Benefits IPv6 Support on the Cisco ASR 901 router provides the following benefits: • Supports state-less auto-configuration of IPv6 addresses.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Information About IPv6 Support on the Cisco ASR 901 Router Table 32-1 Compressed IPv6 Address Formats IPv6 Address Type Preferred Format Compressed Format Unicast 2001:0:0:0:DB8:800:200C:417A 2001::DB8:800:200C:417A Loopback 0:0:0:0:0:0:0:1 ::1 Unspecified 0:0:0:0:0:0:0:0 :: The loopback address listed in Table 32-1 are used by a node to send an IPv6 packet to itself.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Information About IPv6 Support on the Cisco ASR 901 Router provides more control over the network but it requires more work to maintain the table. The table must be updated every time routes are added or changed. Moreover, the static routes must be manually reconfigured if there is a change in the network topology. Static configuration provides security and resource efficiency.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Information About IPv6 Support on the Cisco ASR 901 Router IPv6 Duplicate Address Detection During the stateless autoconfiguration process, duplicate address detection (DAD) verifies the uniqueness of new unicast IPv6 addresses before the addresses are assigned to interfaces (the new addresses remain in a tentative state while duplicate address detection is performed). DAD is first performed first on the new link-local address.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Information About IPv6 Support on the Cisco ASR 901 Router Routing Protocols The Cisco ASR 901 router supports widely deployed routing protocols such as IS-IS, OSPFv3, and multiprotocol BGP. IS-IS Enhancements for IPv6 IS-IS in IPv6 functions the same as in IPv4 and offers many of the same benefits as IS-IS in IPv4. IPv6 enhancements to IS-IS allow IS-IS to advertise IPv6 prefixes in addition to IPv4 and OSI routes.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router QoS for IPv6 The Cisco ASR 901 router support of QoS features for IPv6 environments include ingress packet classification, policing, marking on Ethernet interfaces. It also supports egress packet classification, marking, scheduling, per interface and per qos-group shaping, Low Latency Queuing (LLQ), and weighted random early detection (WRED) on GigabitEthernet interfaces.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. ipv6 address ipv6-address/prefix-length {eui-64 | link-local | anycast} 5. ipv6 enable 6. exit 7. ipv6 unicast-routing 8. ipv6 cef DETAILED STEPS Step 1 Command or Action Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 6 Command or Action Purpose exit Exits interface configuration mode, and returns the router to global configuration mode. Example: Router(config-if)# exit Step 7 ipv6 unicast-routing Enables the forwarding of IPv6 unicast datagrams. Example: Router(config)# ipv6 unicast-routing Step 8 Enables Cisco Express Forwarding (CEF) globally on the router.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 3 Command or Action Purpose ipv6 route {ipv6-prefix / prefix-length ipv6-address | interface-type interface-number [ipv6-address]} [administrative-distance] [administrative-multicast-distance | unicast | multicast] [tag tag] Configures a static default IPv6 route.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the 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 type number Specifies an interface type and number, and places the router in interface configuration mode.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the 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 Specifies an interface type and number, and places the router in interface configuration mode.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the 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 type number Specifies an interface type and number, and places the router in interface configuration mode.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the 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 Configures the interval for IPv6 ICMP error messages.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 4 Command or Action Purpose ipv6 nd dad attempts value Configures the number of consecutive neighbor solicitation messages that are sent on an interface while duplicate address detection is performed on the unicast IPv6 addresses of the interface. Example: Router(config)ipv6 nd dad attempts 5 Configuring IPv6 Neighbor Discovery SUMMARY STEPS 1. enable 2. configure terminal 3.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 4 Command or Action Purpose ipv6 nd {advertisement-interval | autoconfig | cache | dad | managed-config-flag | na | ns-interval | nud | other-config-flag | prefix | ra | reachable-time | router-preference} Configures a Neighbor Discovery on a specified interface on the router. • advertisement-interval—Sends an advertisement interval option in router advertisements (RAs).
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the 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 type number Specifies an interface type and number, and places the router in interface configuration mode.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router 3. interface type number 4. ipv6 ospf process-id area area-id [instance instance-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.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the 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 router isis area-tag Example: Enables IS-IS for the specified IS-IS routing process, and enters router configuration mode.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 8 Command or Action Purpose ipv6 router isis area-name Enables the specified IPv6 IS-IS routing process on an interface. • Example: Router(config-if)# ipv6 router isis area2 area-name—Meaningful name for a routing process. If a name is not specified, a null name is assumed and the process is referenced with a null name.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 4 Command or Action Purpose no bgp default ipv-unicast Disables the IPv4 unicast address family for the BGP routing process specified in the previous step. Example: Router(config-router)# no bgp default ipv4-unicast Step 5 bgp router-id ip-address (Optional) Configures a fixed 32-bit router ID as the identifier of the local router running BGP.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 3 Command or Action Purpose ipv6 route static bfd [vrf vrf-name] interface-type interface-number ipv6-address [unassociated] Specifies static route IPv6 BFDv6 neighbors. Example: Router(config)# ipv6 route static bfd vlan 4000 2001::1 • vrf-name—(Optional) Name of the virtual routing and forwarding (VRF) instance by which static routes are specified. • interface-type—Interface type.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 3 Command or Action Purpose ipv6 route static bfd [vrf vrf-name] interface-ype interface-number ipv6-address [unassociated] Specifies static route IPv6 BFDv6 neighbors.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Configuring BFDv6 and OSPFv3 This section describes the procedures for configuring BFD support for OSPFv3, so that OSPFv3 is a registered protocol with BFD and will receive forwarding path detection failure messages from BFD.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 4 Command or Action Purpose bfd all-interfaces Enables BFD for all interfaces participating in the routing process Example: Router(config-rtr)# bfd all-interfaces Step 5 Enter this command twice to go to privileged EXEC mode. end Example: Router(config-rtr)# end Configuring BFDv6 for BGP SUMMARY STEPS 1. enable 2. configure terminal 3. router bgp as-tag 4.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Step 5 Command or Action Purpose exit Exits global configuration mode and enters privileged EXEC mode. Example: Router(config-router)# exit Implementing QoS for IPv6 The QoS implementation for IPv6 environment in the Cisco ASR router is the same as that of IPv4. For configuration information on Configuring QoS on the Cisco ASR 901 router, refer the following link: http://www.cisco.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Vlan40 is up, line protocol is up IPv6 is enabled, link-local address is FE80::4255:39FF:FE89:4831 No Virtual link-local address(es): Global unicast address(es): 2011:8:8:3::4, subnet is 2011:8:8:3::/64 Joined group address(es): FF02::1 FF02::2 FF02::5 FF02::6 FF02::1:FF00:4 FF02::1:FF89:4831 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled IC
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router L C L I1 22::22/128 [0/0] via Vlan111, receive 33::/64 [0/0] via Vlan111, directly connected 33::33/128 [0/0] via Vlan111, receive 454::/96 [115/20] via FE80::4255:39FF:FE89:3F71, Vlan2020 Verifying a Stateless Auto-Configuration To verify the autoconfigured IPv6 address and its state, use the show ipv6 interface command in privileged EXEC mode, as shown in the example.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds (using 30000) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds (using 30000) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router 0 group query, 0 group report, 0 group reduce 0 router solicit, 50 router advert, 0 redirects 8 neighbor solicit, 8 neighbor advert UDP statistics: Rcvd: 0 input, 0 checksum errors, 0 length errors 0 no port, 0 dropped Sent: 0 output TCP statistics: Rcvd: 0 input, 0 checksum errors Sent: 0 output, 0 retransmitted Verifying IPv6 Duplicate Address Detection Configuration To verify the IPv6 Duplica
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router ND reachable time is 30000 milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. Verifying IPv6 Neighbor Discovery Configuration To verify the IPv6 neighbor discovery configuration, use the show ipv6 neighbors command in privileged EXEC mode, as shown in the example.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Inbound access list is not set Outgoing access list is not set Internet protocol processing disabled GigabitEthernet0/2 is up, line protocol is up Inbound access list is not set Outgoing access list is not set Internet protocol processing disabled GigabitEthernet0/3 is up, line protocol is up Inbound access list is not set Outgoing access list is not set Internet protocol processing disabled Giga
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Router is not originating router-LSAs with maximum metric Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs 10000 msecs Maximum wait time between two consecutive SPFs 10000 msecs Minimum LSA interval 5 secs Minimum LSA arrival 1000 msecs LSA group pacing timer 240 secs Interface flood pacing timer 33 msecs Retransmission pacing timer 66 msecs Number of external L
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router FE80::21E:4AFF:FE97:5BB%Vlan160 4 6500 82 82 25 0 0 01:09:25 5 Router# show bgp ipv6 unicast neighbors 2001:101::2 BGP neighbor is 2001:101::2, remote AS 6500, external link Fall over configured for session BFD is configured. Using BFD to detect fast fallover BGP version 4, remote router ID 14.14.14.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router Refresh-In took 0 seconds Refresh activity: Refresh Start-of-RIB Refresh End-of-RIB Sent ---0 0 Rcvd ---1 1 Address tracking is disabled Connections established 1; dropped 0 Last reset never Transport(tcp) path-mtu-discovery is enabled Graceful-Restart is disabled Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Connection is ECN Disabled Mininum incoming TTL 0, Outgoing TTL 1 Lo
Chapter 32 IPv6 Support on the Cisco ASR 901 Router How to Configure IPv6 Support on the Cisco ASR 901 Router 2001:101::2 2001:103::2 2001:170::2 2001:180::2 2001:190::2 FE80::21E:4AFF:FE97:5BB CE1-2009# 12/11 3/2 8/7 11/10 4/3 13/12 Up Up Up Up Up Up Up Up Up Up Up Up Vl101 Vl103 Vl170 Vl180 Vl190 Vl160 Verifying BFDv6 and OSPFv3 Configuration To verify the BFDv6 and OSPFv3 configuration, use the show bfd neighbors or the show ipv6 ospf command in privileged EXEC mode, as shown in the examples.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router Verifying BFDv6 for BGP Configuration To verify the BFDv6 for BGP configuration, use the show bfd neighbors command in privileged EXEC mode, as shown in the example. Router# show bfd neighbors IPv4 Sessions NeighAddr 101.101.101.2 103.103.103.2 150.150.150.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router Example: IPv6 Addressing on VLAN Interfaces The following is a sample configuration of IPv6 addressing on VLAN interfaces. ! interface Vlan2020 ip address 4.5.6.7 255.255.255.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router Example: Configuring IPv6 Neighborhood Discovery The following is a sample configuration of IPv6 neighborhood discovery. ! interface Vlan111 no ip address ipv6 address 22::22/64 ipv6 address 33::33/64 ipv6 address autoconfig ipv6 nd autoconfig prefix !Neighborhood discovery information is given above.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router ipv6 enable ipv6 ospf 1 area 0 Example: Configuring BFD and Static Routing for IPv6 The following is a sample configuration of bidirectional forwarding detection and static routing for IPv6.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router ! ipv6 router ospf 1 router-id 1.1.1.1 interface vlan 4000 ipv6 add 2001::2/64 ipv6 ospf 1 area 0 ipv6 ospf bfd bfd interval 50 min_rx 50 multiplier 3 ! The following is a sample configuration of bidirectional forwarding detection support for OSPFv3 on all interfaces: ipv6 router ospf 1 router-id 1.1.1.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router Example: Configuring Multiprotocol-BGP for IPv6 The following is a sample configuration of multiprotocol-BGP for IPv6. Router-1 -------ipv6 unicast-routing !Enables forwarding of IPv6 packets.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Configuration Examples for IPv6 Support on the Cisco ASR 901 Router no bgp default ipv4-unicast bgp log-neighbor-changes neighbor 2010:AB8:0:2:C600:10FF:FE58:0 remote-as 1 ! address-family ipv6 neighbor 2010:AB8:0:2:C600:10FF:FE58:0 activate exit-address-family !i Example: Configuring BFD and Multiprotocol-BGP for IPv6 The following is a sample configuration of bidirectional forwarding detection and multiprotocol-BGP for IPv6.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Troubleshooting Tips Troubleshooting Tips Problems can occur in the IPv6 functionality due to misconfigurations. To enable IPv6 functionality, you should enable IPv6 configurations at several places. Some of the sample troubleshooting scenarios are provided below: Problem Solution IPv6 commands are not available. IPv6 is not enabled by default. Enable IPv6 functionality using ipv6 unicast-routing command.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Additional References Additional References Related Documents Related Topic Document Title Cisco IOS commands Cisco IOS Master Commands List, All Releases Cisco IOS Debug commands Cisco IOS Debug Command Reference Cisco IOS IPv6 commands Cisco IOS IPv6 Command Reference IPv6 Configuration document IPv6 Configuration Guide Configuration Examples and TechNotes IPv6 Configuration Examples and TechNotes Standards Standard Title None — MIBs MI
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Additional References RFC Title RFC 5308 Routing IPv6 with IS-IS RFC 5881 Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop) 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.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Feature Information for IPv6 Support on the Cisco ASR 901 Router Feature Information for IPv6 Support on the Cisco ASR 901 Router Table 32-2 lists the release history for this feature. Table 32-2 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.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Feature Information for IPv6 Support on the Cisco ASR 901 Router Table 32-2 Feature Information for IPv6 Support on the Cisco ASR 901 Router (continued) Feature Name Releases Feature Information IPv6 Neighbor Discovery 15.2(2)SNG The IPv6 neighbor discovery determines the link-layer address of a neighbor on the same network (local link), verify the reachability of a neighbor, and track neighboring routers.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Feature Information for IPv6 Support on the Cisco ASR 901 Router Table 32-2 Feature Information for IPv6 Support on the Cisco ASR 901 Router (continued) Feature Name Releases Feature Information OSPFv3 for IPv6 15.2(2)SNG OSPF is a link-state protocol. A link-state protocol makes its routing decisions based on the states of the links that connect source and destination machines.
Chapter 32 IPv6 Support on the Cisco ASR 901 Router Feature Information for IPv6 Support on the Cisco ASR 901 Router Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 32-52 OL-23826-09
CH A P T E R 33 Labeled BGP Support This feature module 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. 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.
Chapter 33 Labeled BGP Support Overview of Labeled BGP Support Prerequisites Cisco IOS Release 15.2(2)SNG or a later release that supports Labeled BGP must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. Restrictions • The Cisco ASR 901 router supports only the client functionality of RFC 3107 and not its area border router (ABR) functionality. • The Cisco ASR 901 router does not support two label-pop (Label pop is the process of removing label header).
Chapter 33 Labeled BGP Support How to Configure Labeled BGP Support 6. neighbor peer-group-name send-label 7. neighbor peer-group-name activate 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 Enters router configuration mode.
Chapter 33 Labeled BGP Support How to Configure Labeled BGP Support neighbor pan peer-group neighbor pan remote-as 1000 neighbor pan update-source Loopback0 neighbor 100.111.14.3 peer-group pan ! address-family ipv4 neighbor pan send-community neighbor pan send-label !The "send-label" option is used to associate a BGP label to the prefix. neighbor 100.111.14.3 activate exit-address-family ! address-family vpnv4 neighbor pan send-community extended neighbor 100.111.14.
Chapter 33 Labeled BGP Support How to Configure Labeled BGP Support 100.112.1.2/32 100.112.1.3/32 100.111.14.3 100.111.14.4 100.111.14.3 100.111.14.4 100.111.14.3 nolabel/nolabel nolabel/nolabel nolabel/nolabel nolabel/nolabel nolabel/nolabel Router# show ip bgp vpnv4 all label Network Next Hop Route Distinguisher: 236:236 154.154.236.4/30 100.154.1.1 100.154.1.1 154.154.236.8/30 100.154.1.1 100.154.1.1 154.154.236.12/30 100.154.1.1 100.154.1.1 154.154.236.16/30 100.154.1.1 100.154.1.1 154.154.236.
Chapter 33 Labeled BGP Support How to Configure Labeled BGP Support LFD: 113.22.12.0/24 0 local labels contains path extension list ifnums: (none) path 13E8A064, path list 13F49DC8, share 1/1, type recursive, for IPv4, flags must-be-labelled, recursive-via-host MPLS short path extensions: MOI flags = 0x0 label 51 recursive via 100.111.13.22[IPv4:Default] label 51, fib 141253D8, 1 terminal fib, v4:Default:100.111.13.
Chapter 33 Labeled BGP Support Additional References Additional References The following sections provide references related to Labeled BGP Support feature. Related Documents Related Topic Document Title Cisco IOS Commands Cisco IOS Master Commands List, All Releases Cisco ASR 901 Command Reference Cisco ASR 901 Series Aggregation Services Router Command Reference BGP Commands Cisco IOS IP Routing: BGP Command Reference Configuring BGP Cisco IOS IP Configuration Guide, Release 12.
Chapter 33 Labeled BGP Support Feature Information for Labeled BGP Support Feature Information for Labeled BGP Support Table 33-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.
CH A P T E R 34 MPLS Traffic Engineering - Fast Reroute Link Protection This feature module describes the Fast Reroute (FRR) link protection and Bidirectional Forwarding Detection (BFD)-triggered FRR feature of Multiprotocol Label Switching (MPLS) traffic engineering (TE). 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.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Feature Overview Prerequisites • Cisco IOS Release 15.2(2)SNG or a later release that supports the MPLS TE-FRR link protection feature must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. • You should enable the asr901-platf-frr command at the global configuration before using TE-FRR.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Feature Overview The MPLS TE-FRR feature is useful for time critical applications like voice calls that require minimal loss of data during link failures. This feature is used to overcome the issue of convergence speed experienced by the Interior Gateway Protocol (IGP) fast timers. Note The convergence numbers is the sum of detection time and re-programming time.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection BFD BFD is a detection protocol designed to provide fast forwarding link failure detection times for all media types, encapsulations, topologies, and routing protocols. In addition to fast forwarding link failure detection, BFD provides a consistent failure detection method for network administrators.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Enabling MPLS TE-FRR on an SVI Interface To enable MPLS TE-FRR on an SVI interface, perform the steps given below: SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. mpls traffic-eng tunnels DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection 6. pseudowire-class pw-class-name 7. encapsulation encapsulation-type 8. preferred-path {[interface] tunnel tunnel-number | peer host-ip-address} [disable-fallback] 9. exit 10. mpls label protocol ldp 11. mpls ldp igp sync holddown milliseconds DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Step 8 Command Purpose preferred-path {[interface] tunnel tunnel-number | peer host-ip-address} [disable-fallback] Specifies the MPLS TE tunnel that traffic uses. Example: Router(config-pw-class)# preferred-path interface Tunnel41 disable-fallback Step 9 • interface—Specifies the preferred path using an output interface.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection 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.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Step 7 Command Purpose rewrite ingress tag pop 1 symmetric Specifies the encapsulation adjustment to be performed on a frame ingressing a service instance. Example: Router(config-if-srv)# rewrite ingress tag pop 1 symmetric Step 8 Binds an attachment circuit to a pseudowire, and to configure an Any Transport over MPLS (AToM) static pseudowire.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection 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 isis Activates the IS-IS routing process for IP and puts the device into router configuration mode.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Step 10 Step 11 Command Purpose fast-reroute per-prefix level-2 all Configures an FRR path that redirects traffic to a remote LFA tunnel for level-2 packets. Example: • level-2—Enables per-prefix FRR of level 2 packets. Router(config-router)# fast-reroute per-prefix level-2 all • all—Enables FRR of all primary paths.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection 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 mpls traffic-eng auto-tunnel primary onehop Creates primary tunnels to all the next hops automatically.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Configuring Backup Auto-Tunnels To configure backup auto-tunnels, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. mpls traffic-eng auto-tunnel backup 4. mpls traffic-eng auto-tunnel backup nhop-only 5. mpls traffic-eng auto-tunnel backup tunnel-num [min num] [max num] 6.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Step 6 Command Purpose mpls traffic-eng auto-tunnel backup timers removal unused sec Configures how frequently a timer scans the backup autotunnels and remove tunnels that are not being used. • Example: sec—Configures (in seconds) the timer scan interval. The range is 0 to 604,800.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection 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 Configures the router to respond to requests for targeted Hello messages from all neighbors.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection How to Configure Traffic Engineering - Fast Reroute Link Protection Step 3 Command Purpose interface type number Specifies an interface type and number, and enters interface configuration mode. Example: Router(config)# interface vlan 40 Step 4 ip rsvp signalling hello bfd Enables BFD protocol on an interface for FRR link protection.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples Verification Examples • Verifying MPLS TE-FRR Configuration • Verifying Primary One-hop Auto-Tunnels • Verifying Backup Auto-Tunnels • Verifying BFD Triggered FRR Configuration Verifying MPLS TE-FRR Configuration To verify the MPLS TE-FRR configuration, use the show commands given below: Note • show mpls traffic-eng tunnels brief • show ip rsvp sender detail • show mpls traffic-eng fast-reroute database
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples 10.10.7.1/32, Flags:0x0 (No Local Protection) 10.10.4.1/32, Flags:0x9 (Local Prot Avail/to NNHOP) !Available to NNHOP 10.10.1.1/32, Flags:0x0 (No Local Protection) Traffic params - Rate: 10K bits/sec, Max. burst: 1K bytes Min Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytes Fast-Reroute Backup info: Inbound FRR: Not active Outbound FRR: No backup tunnel selected Path ID handle: 50000416.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples 172.18.1.1/32, Flags:0x1 (Local Prot Avail/to NHOP) Label subobject: Flags 0x1, C-Type 1, Label 18 172.19.1.1/32, Flags:0x0 (Local Prot Avail/In Use/Has BW/to NHOP) Label subobject: Flags 0x1, C-Type 1, Label 16 172.19.1.2/32, Flags:0x0 (No Local Protection) Label subobject: Flags 0x1, C-Type 1, Label 0 Resv ID handle: CD000404. Policy: Accepted.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples POS2/1 POS2/2 POS2/3 POS3/0 POS3/1 POS3/2 POS3/3 GigabitEthernet4/0 GigabitEthernet4/1 GigabitEthernet4/2 Loopback0 Tunnel0 Tunnel65436 Tunnel65437 Ethernet0 Ethernet1 10.0.0.49 10.0.0.45 10.0.0.57 10.0.0.18 10.0.0.33 unassigned unassigned 10.0.0.37 unassigned unassigned 10.0.3.1 10.0.3.1 10.0.3.1 10.0.3.1 10.3.38.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples Note • show ip rsvp hello bfd nbr detail • show ip rsvp hello bfd nbr summary For more information on the above show commands, see: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_path_protect/configuration/xe-3s/mp-te-bfd-frr.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples Tunnel500 Tun hd AT4/0.100:Untagg Tu501:20 ready Prefix item frr information: Prefix Tunnel In-label Out intf/label FRR intf/label Status 10.0.0.8/32 Tu500 18 AT4/0.100:Pop ta Tu501:20 ready 10.0.8.8/32 Tu500 19 AT4/0.100:Untagg Tu501:20 ready 10.8.9.0/24 Tu500 22 AT4/0.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Verification Examples RSVP Hello for Fast-Reroute/Reroute: Enabled Statistics: Disabled BFD for Fast-Reroute/Reroute: Enabled RSVP Hello for Graceful Restart: Disabled Use this command to display the interface configuration for Hello. Router# show ip rsvp interface detail Gi9/47: RSVP: Enabled Interface State: Up Bandwidth: Curr allocated: 0 bits/sec Max. allowed (total): 0 bits/sec Max. allowed (per flow): 0 bits/sec Max.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Configuration Examples Client FRR Neighbor 10.0.0.6 I/F Gi9/47 State LostCnt LSPs Up 0 1 Configuration Examples This section provides sample configuration examples for MPLS TE-FRR feature and BFD triggered TE/FRR feature on the Cisco ASR 901 Routers.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Additional References Additional References The following sections provide references related to MPLS Traffic Engineering - Fast Reroute Link Protection feature.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Additional References 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.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection Table 34-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.
Chapter 34 MPLS Traffic Engineering - Fast Reroute Link Protection Feature Information for MPLS Traffic Engineering - Fast Reroute Link Protection Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 34-28 OL-23826-09
CH A P T E R 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling This feature module describes how to configure Layer 2 (L2) Control Protocol Peering, Forwarding, and Tunneling feature on the Cisco ASR 901 Series Aggregation Services Routers. 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.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Layer 2 Control Protocol Forwarding Restrictions If you want to peer Operation, Administration, and Maintenance (OAM) packets when l2proto-forward tagged command is configured at the interface level, you should also configure the l2protocol peer lacp command. Layer 2 Control Protocol Forwarding The ASR 901 forwards Layer 2 Control Protocol (L2CP) packets between customer-edge (CE) devices.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling • Spanning Tree Protocol (STP)—including Multiservice Transport Platform (MSTP) and Per VLAN Spanning Tree (PVST) • Virtual Trunking Protocol (VTP) The ASR 901 router allows to tunnel layer 2 packets between CEs. The Cisco proprietary multicast address (01-00-0c-cd-cd-d0) is used while tunneling the packet over the NNI interfaces.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling Configuring Layer 2 Peering The ASR 901 router supports layer 2 peering functionality on a per Ethernet Flow Point (EFP) basis. It supports a maximum packet rate of 10 packets ps (per interface) for a protocol, and 100 packets ps for all protocols (on all interfaces).
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling 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 type and number and enters interface configuration mode.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling • If an interface is configured with layer 2 protocol forwarding, then L2CP packets on the interface are flooded on to the bridge domain. The flooding follows the translations specified in interface. 1. enable 2. configure terminal 3. interface type number 4. l2proto-forward tagged protocol 5. service instance id ethernet 6.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling Step 6 Command Purpose encapsulation untagged Defines the matching criteria to map untagged ingress Ethernet frames on an interface to the appropriate service instance. Example: Router(config-if-srv)# encapsulation untagged Step 7 Enables forwarding of untagged packets of specified protocol in a service instance.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling 4. service instance id ethernet 5. encapsulation encapsulation-type 6. l2protocol tunnel [protocol] 7. bridge-domain bridge-id 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.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling How to Configure Layer 2 Control Protocol Peering, Forwarding, and Tunneling Verifying Layer 2 Peering To verify the layer 2 protocol peering functionality, use the show ethernet service instance command as shown below.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Configuration Examples Associated Interface: GigabitEthernet0/4 Associated EVC: L2protocol tunnel CE-Vlans: Encapsulation: untagged Interface Dot1q Tunnel Ethertype: 0x8100 State: Up EFP Statistics: Pkts In Bytes In Pkts Out Bytes Out 0 0 0 0 EFP Microblocks: **************** Microblock type: Bridge-domain Bridge-domain: 9 Configuration Examples This section provides sample configuration examples for Layer 2 Control Protocol Peering,
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Configuration Examples negotiation auto ! service instance 9 ethernet encapsulation untagged l2protocol forward cdp bridge-domain 9 ! end The following is a sample configuration of layer 2 protocol forwarding of tagged Bridge Protocol Data Units (BPDUs) at the port-channel interface level.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Configuration Examples Note The configuration given below applies to only one router. Similar configuration has to be applied on two Cisco ASR 901 routers. Building configuration...
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Additional References ! ! interface GigabitEthernet0/6 negotiation auto service instance 20 ethernet encapsulation untagged l2protocol tunnel lldp bridge-domain 30 ! end Additional References The following sections provide references related to the Layer 2 Control Protocol Peering and Forwarding feature.
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Additional References 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 Interface and Hardware Component Commands Cisco IOS Interface and Hardware Component Command Reference Cisco IOS LAN Switching Commands Cisco IOS LAN Switching Command Reference Standards Standard Tit
Chapter 35 Layer 2 Control Protocol Peering, Forwarding, and Tunneling Feature Information for Layer 2 Control Protocol Peering, Forwarding, and Tunneling Feature Information for Layer 2 Control Protocol Peering, Forwarding, and Tunneling Table 35-2 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.
Chapter 35 Feature Information for Layer 2 Control Protocol Peering, Forwarding, and Tunneling Layer 2 Control Protocol Peering, Forwarding, and Tunneling Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 35-16 OL-23826-09
CH A P T E R 36 Configuring Inverse Muliplexing over ATM This feature module describes how to configure Inverse Multiplexing over ATM (IMA) to transport ATM traffic over a bundle of T1 or E1 cables. This feature enables the expansion of WAN bandwidth from T1 speeds, without DS3 or OC3 circuits. Finding Feature Information Your software release may not support all the features documented in this module.
Chapter 36 Configuring Inverse Muliplexing over ATM Feature Overview Restrictions The following features are not supported: • Native ATM interfaces • IP Routing • VPI or VCI rewrite • 1:1 and N:1 (where N > 1) VCC or VPP mode • up and down traps • ATM class of service (CBR, VBR-RT, VBR-nRT, UBR+, and UBR) for VPCs and port-mode • Transmission of AIS on VCCs and VPCs to the customer-edge s, when the pseudowire goes down.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA on T1/E1 Interface Configuring ATM IMA on T1/E1 Interface To configure the ATM IMA on an E1 or T1 interface, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. card type {t1 | e1} slot port 4. controller {t1 | e1} slot/port 5. ima-group ima-group-number 6. exit 7. interface ATMslot-number/IMAima-group-number 8. no ip address 9. atm bandwidth dynamic 10.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS Step 6 Command Purpose exit Exits the controller interface. Example: Router(config-controller)# exit Step 7 interface ATMslot/IMAgroup-number Example: Router(config-if)# interface ATM0/IMA0 Step 8 Specifies the slot location and port of IMA interface group. • slot—Specifies the slot location of the ATM IMA port adapter. • group-number—Specifies the group number of the IMA group.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS 5. clock source internal 6. ima-group group-number DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 Enters the global configuration mode. configure terminal Example: Router# configure terminal Step 3 Configures the IMA on an E1 or T1 interface.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS 7. no atm ilmi-keepalive DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters the global configuration mode. Example: Router# configure terminal Step 3 controller {t1 | e1} slot/port Selects a T1 or E1 controller and enters controller configuration mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS Configuring a Port Mode Pseudowire A port mode pseudowire allows you to map an entire ATM interface to a single pseudowire connection. To configure, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. interface ATMslot/IMAgroup-number 4. xconnect ip-address port-number encapsulation mpls DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS 5. encapsulation encapsulation-type 6. xconnect ip-address port-number encapsulation mpls one-to-one DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters the global configuration mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS 4. atm pvp VPI l2transport 5. xconnect ip-address port-number encapsulation mpls DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 Enters the global configuration mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring ATM IMA over MPLS DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters the global configuration mode. Example: Router# configure terminal Step 3 interface ATMslot/IMAgroup-number Example: Router(config)# interface ATM0/IMA0 Step 4 VPI/VCI l2transport Specifies the slot location and port of IMA interface group.
Chapter 36 Configuring Inverse Muliplexing over ATM How to Configure ATM Class of Service ImaGroupTestLink = None ImaGroupTestPattern = 0xFF ImaGroupConfLink = 2 ImaGroupActiveLink = 2 IMA Link Information: ID Link Link State - Ctlr/Chan/Prot Test Status Scrambling ---- -------------- ------------------------------ --------------- -----------0 T1 0/0 Up Up Up Up disabled Off 1 T1 0/1 Up Up Up Up disabled Off How to Configure ATM Class of Service This section describes how to configure ATM class of servic
Chapter 36 Configuring Inverse Muliplexing over ATM How to Configure ATM Class of Service Step 3 Command Purpose interface ATMslot/IMAgroup-number Configures an ATM interface and enters the interface configuration mode. Example: Router(config)# interface ATM1/IMA0 Step 4 pvc VPI/VCI l2transport Specifies the VPI and VCI of the PVC and configures the PVC in layer 2 transport mode. • Example: l2transport is an optional field.
Chapter 36 Configuring Inverse Muliplexing over ATM How to Configure ATM Class of Service Step 4 Command Purpose pvc VPI/VCI l2transport Specifies the VPI and VCI of the PVC and configures the PVC in layer 2 transport mode. • Example: l2transport is an optional field. Router(config-if)# pvc 100/12 l2transport Step 5 ubr rate Example: Router(config-if-atm-vc)# ubr 16000 Configures the UBR QoS class for an ATM permanent virtual circuit (PVC) and specifies the bandwidth.
Chapter 36 Configuring Inverse Muliplexing over ATM How to Configure ATM Class of Service Step 4 Command Purpose pvc VPI/VCI l2transport Specifies the VPI and VCI of the PVC and configures the PVC in layer 2 transport mode. • Example: l2transport is an optional field. Router(config-if)# pvc 100/12 l2transport Step 5 ubr+ pcr-rate mcr-rate Configures the UBR+ QoS class for an ATM permanent virtual circuit () and specifies the bandwidth. Example: • pcr-rate—Peak cell rate in Kbps.
Chapter 36 Configuring Inverse Muliplexing over ATM How to Configure ATM Class of Service Step 4 Command Purpose pvc VPI/VCI l2transport Specifies the VPI and VCI of the PVC and configures the PVC in layer 2 transport mode. • Example: l2transport is an optional field.
Chapter 36 Configuring Inverse Muliplexing over ATM How to Configure ATM Class of Service Example: Configuring an N-to-1 VCC Cell Mode The following is a sample configuration of N-to-1 VCC cell mode: ! interface ATM0/IMA0 no ip address atm mcpt-timers 500 600 700 no atm enable-ilmi-trap 100/100 l2transport cell-packing 10 mcpt-timer 2 encapsulation aal0 xconnect 25.25.25.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits Example: Configuring UBR Plus ! interface atm0/ima0 1/200 l2transport ubr+ 16000 2000 ! Example: Configuring VBR for Real Time Traffic ! interface atm0/ima0 1/200 l2transport vbr-rt 10000 5000 37 ! Example: Configuring VBR for Non-Real Time Traffic ! interface atm0/ima0 1/200 l2transport vbr-nrt 10000 5000 50 ! Configuring Marking MPLS Experimental Bits You can configure MPLS through the following procedures:
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters the global configuration mode. Example: Router# configure terminal Step 3 policy-map policy-map-name Specifies a name for the policy map.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits 8. service-policy input policy-map-name 9. xconnect ip-address port-number encapsulation mpls 10. atm pvp VPI l2transport 11. service-policy input policy-map-name 12. xconnect ip-address port-number encapsulation mpls DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 Enters the global configuration mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits Step 9 Command Purpose xconnect ip-address port-number encapsulation mpls Binds an attachment circuit to the ATM IMA PVC to create a pseudowire. Example: Router(config-if)# xconnect 25.25.25.25 125 encapsulation mpls Step 10 atm pvp VPI l2transport Specifies the VPI of the PVP and configures the PVP in layer 2 transport mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 Enters the global configuration mode. configure terminal Example: Router# configure terminal Step 3 Specifies the slot location and port of IMA interface group and configures the ATM interface.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits 4. map from from-value to to-value 5. default copy DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters the global configuration mode. Example: Router# configure terminal Step 3 table-map table-name Creates a table map with the specified name.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 Enters the global configuration mode. configure terminal Example: Router# configure terminal Step 3 Specifies the name of the existing policy map.
Chapter 36 Configuring Inverse Muliplexing over ATM Configuring Marking MPLS Experimental Bits DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters the global configuration mode. Example: Router# configure terminal Step 3 interface interface-type Specifies the interface type and enters the interface configuration mode.
Chapter 36 Configuring Inverse Muliplexing over ATM Additional References Additional References The following sections provide references related to inverse multiplexing over ATM.
Chapter 36 Configuring Inverse Muliplexing over ATM Feature Information for Inverse Multiplexing over ATM Feature Information for Inverse Multiplexing over ATM Table 36-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.
CH A P T E R 37 IPv6 over MPLS: 6PE and 6VPE This feature module describes how to implement IPv6 VPN Provider Edge Transport over MPLS (IPv6 on Provider Edge Routers [6PE] and IPv6 on VPN Provider Edge Routers [6VPE]) on the Cisco ASR 901 Series Aggregation Services Routers. 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.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Feature Overview Prerequisites • Cisco IOS Release 15.2(2)SNI or a later release that supports the IPv6 over MPLS: 6PE and 6VPE feature must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. • Multiprotocol Label Switching (MPLS) in provider backbone devices. • MPLS with Virtual Private Network (VPN) code in provider devices with VPN provider edge (PE) devices.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Feature Overview Benefits of 6PE and 6VPE 6PE and 6VPE offers the following benefits to service providers: • Minimal operational cost and risk—No impact on existing IPv4 and MPLS services. • Only provider edge routers require upgrade—A 6PE and 6VPE router can be an existing PE router or a new one dedicated to IPv6 traffic. • No impact on IPv6 customer edge (CE) routers—The ISP can connect to any CE router running Static, IGP or EGP.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Feature Overview Figure 37-1 illustrates a 6PE topology.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Supported Features In the MPLS-VPN model a VPN is defined as a collection of sites sharing a common routing table. A customer site is connected to the service provider network by one or more interfaces, where the service provider associates each interface with a VPN routing table–known as the VRF table. Figure 37-2 illustrates an MPLS VPN network. MPLS VPN Network 1. HTTP request to www.example.com 2. ASA decrypts packet; src address is now local address 209.165.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Scalability Numbers Scalability Numbers Table 37-1 shows the scalability numbers for the 6PE and 6VPE feature. Table 37-1 Scalability Numbers for 6PE and 6VPE Interface Numbers Number of VRFs 113 Number of VPNv6 prefixes per VRF About 40001 Number of VPNv6 prefixes About 400037-1 Number of global IPv6 prefixes About 400037-1 1. This number is limited by the MPLS label usage on the PE router.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE 9. neighbor {ip-address | ipv6-address | peer-group-name} remote-as as-number 10. neighbor {ip-address | ipv6-address | peer-group-name} update-source interface-type interface-number 11. address-family ipv6 12. neighbor {ip-address | ipv6-address | peer-group-name} activate 13. neighbor {ip-address | ipv6-address | peer-group-name} send-label 14.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Step 8 Command Purpose no bgp default ipv4-unicast Disables the default IPv4 unicast address family for peering session establishment. Example: Router(config-router)# no bgp default ipv4-unicast Step 9 neighbor {ip-address | ipv6-address | peer-group-name} remote-as as-number Example: Router(config-router)# neighbor 10.108.1.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Configuring 6VPE 6VPE requires setting up of IPv6 connectivity from PE to CE routers, MP-BGP peering to the neighboring PE and MPLS/IPv4 connectivity to the core network using supported routing protocols (like OSPF, IS-IS, EIGRP, Static) as done in 6PE. In addition, IPv6 VRFs have to be created on the PE routers and attached to the interfaces connecting to CE routers.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Step 4 Command Purpose address-family ipv6 [vrf vrf-name] Enters address family configuration mode for configuring routing sessions, such as BGP, that use standard IPv6 address prefixes. Example: • vrf—(Optional) Specifies all VRF instance tables or a specific VRF table for an IPv6 address. • vrf-name—(Optional) A specific VRF table for an IPv6 address.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE 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 Enters the number that identifies the autonomous system (AS) in which the router resides.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Setting up MPLS/IPv4 Connectivity with LDP To configure MPLS and IPv4 connectivity with LDP, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. interface interface 4. ip address ip-address 5. mpls ip 6. exit DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Creating IPv6 VRFs on PE Routers To configure IPv6 VRFs on the PE routers, complete the following tasks: • Configuring IPv6-only VRF • Configuring Dual-stack VRF Configuring IPv6-only VRF To configure IPv6-only VRF, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. vrf definition vrf-name 4. address-family ipv6 5.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Configuring Dual-stack VRF To configure dual-stack VRF, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. vrf definition vrf-name 4. address-family ipv4 5. exit-address-family 6. address-family ipv6 7. exit-address-family DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE Step 6 Command Purpose address-family ipv6 Enters address family configuration mode for configuring routing sessions that use standard IPv6 address prefixes. Example: Router(config-vrf)# address-family ipv6 Step 7 exit-address-family Exits address-family submode.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE B B B B B B B B B B B B B B B B B B O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2 ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 72::/64 [20/0] via 100::2 72:0:0:1::/64 [20/0] via 100::2 72:0:0:2::/64 [20/0] via 100::2 72:0:0:4::/64 [20/0] via 100::2 72:0:0:5::/64 [20/0] via 100::2 72:0:0:6::/64 [20/0] via 100::2 72:0:0:7::/64 [20/0] via 100::2 72:0:0:8::/64 [20/0] via 100::2 72:0:0:9::/64 [20/0] vi
Chapter 37 IPv6 over MPLS: 6PE and 6VPE How to Configure IPv6 over MPLS: 6PE and 6VPE To display IPv6 routing table information associated with a VPN routing and forwarding (VRF) instance, use the following show command.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Configuration Examples To display output information linking the MPLS label with prefixes, use the following show command. Router# show mpls forwarding-table Local tag 16 17 18 19 20 21 22 23 24 Outgoing tag or VC Aggregate Aggregate Aggregate Pop tag Pop tag Pop tag Aggregate Aggregate Aggregate Prefix or Tunnel Id IPv6 IPv6 IPv6 192.168.99.64/30 192.168.99.70/32 192.168.99.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Configuration Examples redistribute connected redistribute isis ipv6-cloud allocate-label all ! neighbor 34.4.3.3 remote-as 55400 address-family ipv4 unicast ! address-family ipv6 labeled-unicast Example: Configuring 6VPE The following is a sample configuration of 6VPE. vrf vpn1 address-family ipv6 unicast import route-target 200:2 ! export route-target 200:2 interface Loopback0 ipv4 address 10.0.0.1 255.255.255.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Additional References Additional References The following sections provide references related to Remote Loop-Free Alternate Fast Reroute feature.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Feature Information for IPv6 over MPLS: 6PE and 6VPE Feature Information for IPv6 over MPLS: 6PE and 6VPE Table 37-2 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.
Chapter 37 IPv6 over MPLS: 6PE and 6VPE Feature Information for IPv6 over MPLS: 6PE and 6VPE Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 37-22 OL-23826-09
CH A P T E R 38 Storm Control This feature module describes the Storm Control feature that helps to monitor the incoming broadcast, multicast, and unknown unicast packets and prevent them from flooding the LAN ports. 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.
Chapter 38 Storm Control Feature Overview Prerequisites • Cisco IOS Release 15.3(3)S or a later release that supports the Storm Control feature must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. • The storm-control command is not recommended on an interface that is part of a port channel. • Storm-control counters are not supported on port channel as the counters are based on physical ports. • Discarded counters are not displayed for port channel.
Chapter 38 Storm Control Configuring Storm Control SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. storm-control {action {shutdown | trap}| {broadcast | multicast | unicast} {level {level | bps bps-level | pps pps-level}} 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.
Chapter 38 Storm Control Configuring Storm Control Step 4 Step 5 Command Purpose storm-control {action {shutdown | trap}| {broadcast | multicast | unicast} {level {level | bps bps-level| pps pps-level}} Configures broadcast, multicast, or unknown unicast storm control. • action—Specifies the action to take when a storm occurs on a port. • shutdown—Disables the port during a storm. Example: • trap—Sends an SNMP trap.
Chapter 38 Storm Control Configuring Error Disable Recovery To verify the dropped counters, use the show command described in the following example. Router# show interface gigabitethernet 0/1 counters storm-control Port Gi0/1 UcastSupp UcastSuppDiscards McastSupp McastSuppDiscards BcastSupp BcastSuppDiscards %/ps %/ps %/ps 100.00% 0 20000p 1065163 100.00% 0 Configuring Error Disable Recovery The Cisco ASR 901 router supports error disable recovery for traffic storm control.
Chapter 38 Storm Control Configuring Error Disable Recovery Step 4 Command Purpose errdisable recovery interval seconds Configures the period to recover from a specified error-disable cause. • Example: Router(config)# errdisable recovery interval 30 Step 5 seconds—Specifies the time to recover from a specified error-disable cause. Exits global configuration mode and enters the privileged EXEC mode.
Chapter 38 Storm Control Configuration Example for Storm Control Configuration Example for Storm Control The following is a sample configuration of Storm Control feature on the Cisco ASR 901 router. ! interface GigabitEthernet0/1 no ip address negotiation auto storm-control broadcast level pps 200 storm-control multicast level pps 300 storm-control action trap end ! Troubleshooting Tips Use the following debug command to enable the debug feature to help in troubleshooting the storm control feature.
Chapter 38 Storm Control Additional References Additional References The following sections provide references related to Storm Control feature.
Chapter 38 Storm Control Feature Information for Storm Control Feature Information for Storm Control Table 38-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.
Chapter 38 Storm Control Feature Information for Storm Control Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 38-10 OL-23826-09
CH A P T E R 39 Remote Loop-Free Alternate - Fast Reroute This feature module 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. 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.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Contents Prerequisites • Cisco IOS Release 15.2(2)SNI or a later release that supports the Remote LFA-FRR feature must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. • You should enable the following commands at the global configuration mode before configuring the Remote LFA-FRR feature.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Feature Overview • The Border Gateway Protocol (BGP) Prefix-Independent Convergence (PIC) edge is not supported. Specifically, the bgp additional-paths install command is not supported. • If the network port is an LAG interface (etherchannel), you must use BFD over SVI to achieve FRR convergence numbers. • If the LAG interface is used either on access side or towards the core, you should shutdown the interface before removing it.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Feature Overview R1 and R7 CE nodes R6 - R5 - R4 R2 and R3 PE nodes (protected link) R2 - R4- R5 - R6 - R3 Fast Reroute Repair Path P nodes Benefits of Remote LFA-FRR • Simplifies operation with minimum configuration • Eliminates additional traffic engineering (TE) protocols. • Computes PQ node dynamically without any manual provisioning (PQ node is a member of both the extended P-space and the Q-space.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Figure 39-2 PW Pseudowire Redundancy Over FRR P1 P2 P3 P6 P5 P4 PE-3 PW-AC PW-SY Standby PW 361186 Active PW Conditions for Switchover • If the primary path to the peer node goes down for active VC, the FRR changes to backup and the VC remains active. • A VC switchover does not occur unless both primary and backup paths are down for active VC.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Configuring Remote LFA-FRR for IS-IS To configure Remote LFA-FRR for the IS-IS routing process, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. no negotiation auto 5. service instance id ethernet 6. encapsulation dot1q vlan-id 7. rewrite ingress tag pop 1 symmetric 8. bridge-domain bridge-domain-id 9.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 4 Command Purpose no negotiation auto Disables automatic negotiation. Example: Router(config-if)# no negotiation auto Step 5 Configures an Ethernet service instance on an interface. service instance id ethernet • Example: id—Integer that uniquely identifies a service instance on an interface. Router(config-if)# service instance 7 ethernet Step 6 Enables IEEE 802.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 13 Command Purpose isis network point-to-point Configures a network of two networking devices that use the integrated IS-IS routing protocol to function as a point-to-point link. Example: Router(config-if)# isis network point-to-point Step 14 exit Exits the interface configuration mode and enters the global configuration mode.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Configuring Remote LFA-FRR for OSPF To configure Remote LFA-FRR for the OSPF routing process, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. no negotiation auto 5. service instance id ethernet 6. encapsulation dot1q vlan-id 7. rewrite ingress tag pop 1 symmetric 8. bridge-domain bridge-domain-id 9.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 5 Command Purpose service instance id ethernet Configures an Ethernet service instance on an interface. • Example: id—Integer that uniquely identifies a service instance on an interface. Router(config-if)# service instance 7 ethernet Step 6 encapsulation dot1q vlan-id Example: Enables IEEE 802.1Q encapsulation of traffic on a specified interface in a VLAN.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 13 Step 14 Step 15 Command Purpose fast-reroute per-prefix {level-1 | level-2} {all | route-map route-map-name} Configures an FRR path that redirects traffic to a remote LFA tunnel for either level 1 or level 2 packets. • level-1—Enables per-prefix FRR of level 1 packets. Example: • level-2—Enables per-prefix FRR of level 2 packets.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Configuring Remote LFA-FRR on a Global Interface To configure Remote LFA-FRR on a global interface, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. mpls label protocol ldp 4. no l3-over-l2 flush buffers 5. asr901-platf-frr enable 6. mpls ldp discovery targeted-hello accept DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Configuring Remote LFA-FRR on a GigabitEthernet Interface To configure Remote LFA-FRR on a GigabitEthernet interface, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. no negotiation auto 5. service instance id ethernet 6. encapsulation dot1q vlan-id 7. rewrite ingress tag pop 1 symmetric 8.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 7 Step 8 Command Purpose rewrite ingress tag pop 1 symmetric Specifies the encapsulation adjustment to be performed on a frame ingressing a service instance. Example: • pop—Removes a tag from a packet. Router(config-if-srv)# rewrite ingress tag pop 1 symmetric • 1—Specifies the outermost tag for removal from a packet.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 4 Command Purpose ip address ip-address Specifies an IP address for the specified interface. Example: Router(config-if)# ip address 7.7.7.1 255.255.255.0 Step 5 Configures an IS-IS routing process for an IP on an interface.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 18. passive-interface interface-type interface-number 19. mpls ldp sync 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.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 9 Command Purpose max-lsp-lifetime seconds Configures the maximum link-state packets (LSPs) lifetime. • Example: seconds—Maximum LSP lifetime in seconds. The range is from 1 to 65535. Router(config-router)# max-lsp-lifetime 65535 Step 10 Sets the link-state packet (LSP) refresh interval.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 13 Command Purpose lsp-gen-interval [level-1 | level-2] lsp-max-wait [lsp-initial-wait lsp-second-wait] Customizes IS-IS throttling of LSP generation. Example: • level-1—(Optional) Apply intervals to Level-1 areas only. • level-2—(Optional) Apply intervals to Level-2 areas only.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 18 Command Purpose passive-interface interface-type interface-number Disables sending routing updates on an interface. • interface-type—Interface type. • interface-number—Interface number. Example: Router(config-router)# passive-interface Loopback0 Step 19 Enables MPLS LDP synchronization on interfaces for an IS-IS process.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 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.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 9 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.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 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 {t1 | e1} slot/port Selects a T1 or E1 controller and enters controller configuration mode.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 10 Command Purpose xconnect ip-address encapsulation mpls Binds an attachment circuit to a pseudowire, to configure an Any Transport over MPLS (AToM) static pseudowire. Example: • 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.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 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 {t1 | e1} slot/port Selects a T1 or E1 controller and enters controller configuration mode.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 9 Command Purpose no ip address Removes an IP address or disables IP processing. Example: Router(config-cem)# no ip address Step 10 Defines a CEM channel. cem group-number Example: Router(config-cem)# cem 0 Step 11 xconnect ip-address encapsulation mpls Example: Binds an attachment circuit to a pseudowire, to configure an Any Transport over MPLS (AToM) static pseudowire.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 10. no ip address 11. cem group-number 12. xconnect ip-address encapsulation mpls 13. backup peer peer-ip-address 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.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Step 9 Command Purpose interface CEM slot/port Defines a CEM channel. Example: Router(config)# interface CEM 0/0 Step 10 Removes an IP address or disables IP processing. no ip address Example: Router(config-if)# no ip address Step 11 Defines a CEM channel.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Verifying Remote LFA-FRR Configuration To verify the remote LFA-FRR configuration, use the show commands described in the following examples. To display information for an OSPF per-prefix LFA-FRR configuration, use the following show command. Router# show ip ospf fast-reroute remote-lfa tunnels OSPF Router with ID (1.1.1.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute nexthop 6.6.6.6 MPLS-Remote-Lfa6, repair, adjacency IP midchain out of MPLS-Remote-Lfa6 12CD7880 output chain: label [31|537] FRR Primary (0x11139020)
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute repair: attached-nexthop 6.6.6.6 MPLS-Remote-Lfa1 (12C55D24) path 12C55D24, path list 12C856E8, share 1/1, type attached nexthop, for IPv4, flags repair, repair-only nexthop 6.6.6.6 MPLS-Remote-Lfa1, repair, adjacency IP midchain out of MPLS-Remote-Lfa1 12D512C0 output chain: label [none|23] FRR Primary (0xA74F800)
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 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 loc
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute Verifying Remote LFA-FRR Configuration for EoMPLS on an EVC Interface To verify the remote LFA-FRR configuration for EoMPLS on an EVC interface, use the show commands described in the following examples. Router# show mpls l2transport vc 3001 detail Local interface: Gi0/0 up, line protocol up, Eth VLAN 200 up Interworking type is Ethernet Destination address: 3.3.3.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 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 16 Group ID:
Chapter 39 Remote Loop-Free Alternate - Fast Reroute How to Configure Remote Loop-Free Alternate - Fast Reroute 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 faul
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Configuration Examples for Remote LFA-FRR transit packet totals: receive 64465447, send 64465519 transit byte totals: receive 15987430856, send 15987448712 transit packet drops: receive 0, seq error 0, send 0 Verifying Remote LFA-FRR Configuration on SAToP To verify the remote LFA-FRR configuration on SAToP, use the show commands described in the following example.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Configuration Examples for Remote LFA-FRR • Example: Configuring LFA-FRR on ATM/IMA, page 39-37 • Example: Configuring LFA-FRR on CESoPSN, page 39-38 • Example: Configuring LFA-FRR on SAToP, page 39-38 Example: Configuring Remote LFA-FRR for IS-IS The following is a sample configuration of Remote LFA-FRR for IS-IS on all nodes.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Configuration Examples for Remote LFA-FRR mpls ldp discovery targeted-hello accept no l3-over-l2 flush buffers asr901-platf-frr enable ! Example: Configuring Remote LFA-FRR on a GigabitEthernet Interface The following is a sample configuration of Remote LFA-FRR on a GigabitEthernet Interface.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Configuration Examples for Remote LFA-FRR ima-group 2 ! interface ATM0/IMA1 no ip address no atm enable-ilmi-trap xconnect 2.2.2.2 90 encapsulation mpls backup peer 180.0.0.201 90 ! Example: Configuring LFA-FRR on CESoPSN The following is a sample configuration of LFA-FRR on CESoPSN, which also includes pseudowire redundancy.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Additional References Additional References The following sections provide references related to Remote Loop-Free Alternate - Fast Reroute feature.
Chapter 39 Remote Loop-Free Alternate - Fast Reroute Feature Information for Remote Loop-Free Alternate - Fast Reroute Feature Information for Remote Loop-Free Alternate - Fast Reroute Table 39-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.
CH A P T E R 40 Digital Optical Monitoring This feature module provides information on the digital optical monitoring (DOM) feature 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.
Chapter 40 Digital Optical Monitoring How to Enable Transceiver Monitoring The command line output for the real-time parameters is shown using the show interfaces transceiver command. To enable threshold notification in the transceiver via SNMP, use the snmp-server enable traps transceiver command. You can use the show controllers gig 0/x command to check whether SFP’s are DOM capable. This command displays the SFP details.
Chapter 40 Digital Optical Monitoring Examples Step 4 Command Purpose monitoring Enables monitoring of all optical transceivers. Example: Router(config-xcvr-type)# monitoring Step 5 (Optional) Specifies the time interval for monitoring optical transceivers. Valid range is 300 to 3600 seconds, and the default value is 600 seconds.
Chapter 40 Digital Optical Monitoring Examples Example: Displaying Detailed Transceiver Information This example shows how to display detailed transceiver information: Router# show interfaces transceiver detail mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable. ++ : high alarm, + : high warning, - : low warning, -- : low alarm. A2D readouts (if they differ), are reported in parentheses. The threshold values are calibrated.
Chapter 40 Digital Optical Monitoring Examples Example: Displaying List of Supported Transceivers This example shows how to display the list of supported DOM transceivers: Router# show interfaces transceiver supported-list Transceiver Type Cisco p/n min version supporting DOM -----------------------------------------DWDM GBIC DWDM SFP RX only WDM GBIC DWDM XENPAK DWDM X2 DWDM XFP CWDM GBIC CWDM X2 CWDM XFP XENPAK ZR X2 ZR XFP ZR Rx_only_WDM_XENPAK XENPAK_ER X2_ER XFP_ER XENPAK_LR X2_LR XFP_LR XENPAK_LW X2
Chapter 40 Digital Optical Monitoring Examples Example: Displaying Threshold Tables This example shows how to display the threshold tables for all transceivers on the ASR 901 router: Router# show interfaces transceiver threshold table Optical Tx Optical Rx Temp Laser Bias current ------------- ------------- ----------------DWDM GBIC Min1 Voltage --------- -0.50 -28.50 0 N/A 4.50 -0.30 3.29 3.50 -28.29 -6.69 6.00 5 60 70 N/A N/A N/A 4.75 5.25 5.50 -0.50 -28.50 0 N/A 3.00 Min2 -0.
Chapter 40 Digital Optical Monitoring Examples X2 ZR Min1 -0.50 -24.50 0 N/A N/A -0.80 4.30 4.50 -24.29 -6.69 4.00 5 60 70 N/A N/A N/A N/A N/A N/A -0.50 -24.50 0 N/A N/A Min2 -0.80 Max2 4.30 Max1 4.50 Rx_only_WDM_XENPAK Min1 N/A -24.29 -6.69 4.00 5 60 70 N/A N/A N/A N/A N/A N/A -24.50 0 N/A N/A Min2 Max2 Max1 XENPAK_ER Min1 N/A N/A N/A -24.29 -6.69 4.00 5 60 70 N/A N/A N/A N/A N/A N/A -5.00 -16.50 0 N/A N/A Min2 Max2 Max1 X2_ER Min1 -4.69 4.00 4.50 -15.80 -0.50 0.
Chapter 40 Digital Optical Monitoring Examples Max2 Max1 X2 SR Min1 0.50 1.00 0.50 1.00 60 70 N/A N/A N/A N/A -11.30 -13.89 -4 N/A N/A -7.30 -1.00 3.00 -9.89 -1.00 3.00 0 70 74 N/A N/A N/A N/A N/A N/A -10.30 -12.89 0 N/A N/A -7.30 -1.00 2.00 -9.89 -1.00 2.00 5 60 70 N/A N/A N/A N/A N/A N/A -4.00 -32.00 -4 84.00 3.00 0.00 5.00 8.00 -28.00 -7.00 -3.00 0 85 90 70.00 4.00 2.00 3.09 3.50 3.59 -10.00 -17.50 -5 N/A 3.00 -9.50 -4.00 -3.50 -17.00 0.00 0.
Chapter 40 Digital Optical Monitoring Examples Example: Displaying Threshold Violations This example shows how to display the threshold violations for all transceivers on a Cisco ASR 901 router: Router# show interfaces transceiver threshold violations Rx: Receive, Tx: Transmit.
Chapter 40 Digital Optical Monitoring Examples Gi0/10 Gi0/11 3.25 3.23 3.70 3.70 3.59 3.59 3.09 3.09 3.00 3.00 Port --------Gi0/10 Gi0/11 Current (milliamperes) ----------------533.9 391.1 High Alarm Threshold (mA) ---------N/A N/A High Warn Threshold (mA) --------N/A N/A Low Warn Threshold (mA) --------N/A N/A Low Alarm Threshold (mA) --------N/A N/A Port --------Gi0/10 Gi0/11 Optical Transmit Power (dBm) -----------------4.5 -5.5 High Alarm Threshold (dBm) ----------3.5 -3.
Chapter 40 Digital Optical Monitoring Examples br_nominal length_9km length_9m length_50m length_62_5m length_cu vendor_name vendor_oui vendor_pn vendor_rev cc_base options[0] options[1] br_max (%) br_min (%) vendor_sn date_code cc_ext DOM support (100MHz) (100m) (100m) (100m) (100m) (10m) 13 10 100 55 55 0 CISCO-SUMITOMO 0x00 00 5F SCP6G44-C1-BMH A 0x28 0x00000000 0x0000001A 0 0 SPC15240CP6 110612C8 (yymmddvv, v=vendor specific) 0x64 yes Cisco ASR 901 Series Aggregation Services Router Software Config
Chapter 40 Digital Optical Monitoring Additional References Additional References The following sections provide references to digital optical monitoring feature.
Chapter 40 Digital Optical Monitoring Feature Information for Digital Optical Monitoring Feature Information for Digital Optical Monitoring Table 40-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.
Chapter 40 Digital Optical Monitoring Feature Information for Digital Optical Monitoring Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 40-14 OL-23826-09
CH A P T E R 41 IPv4 Multicast This feature module 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. 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.
Chapter 41 IPv4 Multicast Feature Overview Prerequisites • Cisco IOS Release 15.4(1)S or a later release that supports the IPv4 Multicast feature must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. • Source Specific Multicast (SSM) mapping takes a group G join from a host and identifies this group with an application associated with one or more sources. The SSM mapping can support only one such application per group G.
Chapter 41 IPv4 Multicast Feature Overview Supported Protocols • Basic multicast routing • IGMP • PIMv4 SSM • PIMv4 SSM Mapping • PIM MIB • PIM Sparse mode • Static Rendezvous Point (RP) • Auto RP • Bootstrap router (BSR) PIM SSM for IPv4 PIM SSM is the routing protocol that supports the implementation of SSM and is derived from the PIM sparse mode (PIM-SM).
Chapter 41 IPv4 Multicast Feature Overview PIM SSM Address Range SSM can coexist with the Internet Standard Multicast (ISM) service by applying the SSM delivery model to a configured subset of the IP multicast group address range. The Cisco IOS software allows SSM configuration for an arbitrary subset of the IP multicast address range 224.0.0.0 through 239.255.255.255.
Chapter 41 IPv4 Multicast Feature Overview PIM SSM Mapping PIM SSM mapping supports SSM transition in cases where neither the URD nor IGMP v3lite is available, or when supporting SSM on the end system is not feasible. SSM mapping enables you to leverage SSM for video delivery to legacy set-top boxes (STBs) that do not support IGMPv3 or for applications that do not take advantage of the IGMPv3 host stack. URD and IGMPv3lite are applications used on receivers which do not have SSM support.
Chapter 41 IPv4 Multicast Configuring IPv4 Multicast Configuring IPv4 Multicast • Enabling IPv4 Multicast Routing, page 41-6 • Configuring PIM SSM, page 41-7 • Configuring PIM SSM Mapping, page 41-8 • Verifying IPv4 Multicast Routing, page 41-9 • Verifying PIM SSM, page 41-9 • Verifying PIM SSM Mapping, page 41-10 Enabling IPv4 Multicast Routing To configure IPv4 multicast on the Cisco ASR 901 series routers, complete the following steps: SUMMARY STEPS 1. enable 2. configure terminal 3.
Chapter 41 IPv4 Multicast Configuring IPv4 Multicast Step 4 Command Purpose asr901-platf-multicast enable Enables multicast on the Cisco ASR 901 series routers. Example: Router(config)# asr901-platf-multicast enable Step 5 Configures the address of a PIM RP for multicast groups. ip pim rp-address rp-address Example: Router(config)# ip pim rp-address 192.168.0.1 Step 6 Configures the interface type and enters interface configuration mode.
Chapter 41 IPv4 Multicast Configuring IPv4 Multicast 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 pim ssm [default | range access-list] Configures SSM service. The default keyword defines the SSM range access list.
Chapter 41 IPv4 Multicast Configuring IPv4 Multicast 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 Disables DNS-based SSM mapping. no ip igmp ssm-map query dns Example: Router(config)# no ip igmp ssm-map query dns Step 4 Enables SSM mapping for groups in the configured SSM range.
Chapter 41 IPv4 Multicast Configuring IPv4 Multicast 224.0.1.40 224.0.1.40 Vlan16 Vlan23 04:17:35 05:08:03 00:02:58 00:02:54 16.1.1.3 23.1.1.1 To display the contents of the IP multicast routing table, use the show command described in the following example.
Chapter 41 IPv4 Multicast Configuration Examples for IPv4 Multicast Database Source list : Static : 5.1.1.1 9.1.1.1 To display the multicast groups with receivers that are directly connected to the router and that were learned through IGMP, use the show command described in the following examples. • show ip igmp groups group-address Router# show ip igmp groups 232.1.1.1 IGMP Connected Group Membership Group Address Interface Accounted 232.1.1.
Chapter 41 IPv4 Multicast Configuration Examples for IPv4 Multicast Example: IPv4 Multicast Routing The following is a sample configuration of IPv4 Multicast routing feature on the Cisco ASR 901 router. ! Building configuration... Current configuration : 120 bytes ! ip multicast-routing asr901-platf-multicast enable ! interface Vlan5 asr901-multicast source ip address 22.1.1.2 255.255.255.
Chapter 41 IPv4 Multicast Troubleshooting Tips ! interface vlan10 description Sample IGMP Interface Configuration for SSM-Mapping Example ip address 10.20.1.2 255.0.0.0 ip pim sparse-mode ip igmp static-group 232.1.2.1 source ssm-map ip igmp version 3 ! . . . ! ip pim ssm default ! access-list 10 permit 232.1.2.10 access-list 11 permit 232.1.2.0 0.0.0.255 ! Example: Configuring Rendezvous Point For a sample configuration of RP, see the Configuring a Rendezvous Point guide at: http://www.cisco.
Chapter 41 IPv4 Multicast Additional References Additional References The following sections provide references related to IPv4 Multicast feature.
Chapter 41 IPv4 Multicast Additional References 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.
Chapter 41 IPv4 Multicast Feature Information for IPv4 Multicast Feature Information for IPv4 Multicast Table 41-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.
Chapter 41 IPv4 Multicast Feature Information for IPv4 Multicast Table 41-1 Feature Information for IPv4 Multicast Feature Name Releases Feature Information IGMP Version 2 15.4(1)S This feature was introduced on the Cisco ASR 901 routers. The following section provides information about this feature: • IGMPv2, page 41-4 Platform-Independent Cisco IOS Software Documentation See the “Customizing IGMP” chapter of the IP Multicast: IGMP Configuration Guide. IGMP Version 3 15.
Chapter 41 IPv4 Multicast Feature Information for IPv4 Multicast Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 41-18 OL-23826-09
CH A P T E R 42 IPv6 Multicast This feature module describes how to configure basic IP multicast in an IPv6 network. 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.
Chapter 42 IPv6 Multicast Feature Overview Prerequisites • Cisco IOS Release 15.4(1)S or a later release that supports the IPv6 Multicast feature must be installed previously on the Cisco ASR 901 Series Aggregation Services Router. • You must first enable IPv6 unicast routing on all interfaces of the device on which you want to enable IPv6 multicast routing. • PIM dense-mode is not supported. • Bidirectional PIM is not supported.
Chapter 42 IPv6 Multicast Feature Overview How active a multicast group is, its duration, and its membership can vary from group to group and from time to time. A group that has members may have no activity. IPv6 Multicast Groups An IPv6 address must be configured on an interface for the interface to forward IPv6 traffic. Configuring a site-local or global IPv6 address on an interface automatically configures a link-local address and activates IPv6 for that interface.
Chapter 42 IPv6 Multicast Feature Overview A set of queriers and hosts that receive multicast data streams from the same source is called a multicast group. Queriers and hosts use MLD reports to join and leave multicast groups and to begin receiving group traffic. MLD uses the Internet Control Message Protocol (ICMP) to carry its messages. All MLD messages are link-local with a hop limit of 1, and they all have the alert option set.
Chapter 42 IPv6 Multicast Feature Overview PIM Source Specific Multicast PIM SSM is the routing protocol that supports the implementation of SSM and is derived from PIM SM. However, unlike PIM SM where data from all multicast sources are sent when there is a PIM join, the SSM feature forwards datagram traffic to receivers from only those multicast sources that the receivers have explicitly joined, thus optimizing bandwidth utilization and denying unwanted Internet broadcast traffic.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Rendezvous Point A rendezvous point (RP) is required only in networks running Protocol Independent Multicast sparse mode (PIM-SM). The protocol is described in RFC 2362. For more information on RP, see the Configuring a Rendezvous Point guide at: http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers/rps.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast 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 ipv6 multicast-routing [vrf vrf-name] Example: Enables multicast routing on all IPv6-enabled interfaces and enables multicast forwarding for PIM and MLD on all enabled interfaces of the device.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Step 2 Command Purpose configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 Disables IPv6 multicast forwarding on the router. no ipv6 mfib Example: Router(config)# no ipv6 mfib Disabling MLD Device-Side Processing MLD is enabled on every interface when IPv6 multicast routing is configured. This procedure disables MLD router side processing on that interface.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Step 3 Command Purpose interface type number Specifies an interface type and number, and places the device in interface configuration mode. Example: Router(config)# interface GigabitEthernet 0/1 Step 4 Disables MLD device-side processing on a specified interface.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Step 4 Command Purpose ipv6 mld query-interval seconds Configures the frequency of MLD Host-Query packets transmitted. A designated router for a LAN is the only router that transmits queries. The default value is 60 seconds. Example: Router(config-if)# ipv6 mld query-interval 60 Step 5 ipv6 mld query-max-response-time seconds Specifies the maximum query response time advertised in the MLD queries. Default value is 10 seconds.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Configuring PIM SSM Options To configure PIM Source-Specific Multicast options, complete the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. ipv6 pim 4. interface type number 5. ipv6 pim hello-interval interval-in-seconds 6. ipv6 pim join-prune-interval interval-in-seconds DETAILED STEPS Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Disabling PIM SSM Multicast on an Interface To disable PIM SSM multicast on a specified interface, complete the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. interface type number 4. no ipv6 pim 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.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast 2. configure terminal 3. ipv6 mld [vrf vrf-name] ssm-map enable 4. ipv6 mld [vrf vrf-name] ssm-map static access-list source-address 5. no ipv6 mld [vrf vrf-name] ssm-map query dns 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.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast To display the MLD interface specific parameters, use the show command described in the following example.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast DR : not elected GigabitEthernet0/1 off 0 30 1 Address: :: DR : not elected GigabitEthernet0/2 off 0 30 1 Address: :: DR : not elected GigabitEthernet0/3 off 0 30 1 Address: :: DR : not elected GigabitEthernet0/4 off 0 30 1 Address: :: DR : not elected GigabitEthernet0/5 off 0 30 1 Address: :: DR : not elected GigabitEthernet0/6 off 0 30 1 Address: :: DR : not elected GigabitEthernet0/7 off 0 30 1 Address: :: DR : not elected Vlan1 off 0 30 1 Address: :
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Interface Nbr count Vlan300 Vlan100 Vlan10 Loopback0 0 0 1 0 Total Nbrs 1 To display the number of PIM neighbors discovered, use the show command described in the following example.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast SM SPT UP: 04:27:20 JP: Join(never) Flags: KAT(00:01:04) AA PA RA SR RPF: Vlan47,47::1:1:3* FastEthernet4/10 04:27:16 fwd Join(00:03:14) Tunnel0 04:27:17 fwd To display the count of the ranges, (*, G), (S, G) and (S, G) RPT routes in the pim topology tables, use the show command described in the following example. Router# show ipv6 pim topology route-count PIM No. No. No. No.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Tunnel1* Type : PIM Encap RP : 4::4 Source: 300::1 To display information about the PIM traffic counters, use the show command described in the following example.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast To display the MRIB table, use the show command described in the following example. All entries are created by various clients of MRIB, such as, MLD, PIM and MFIB. The flags on each entry or interface, serve as communication mechanism between various clients of MRIB.
Chapter 42 IPv6 Multicast Configuring IPv6 Multicast Forwarding: 9592618/0/182/0, Other: 0/0/0 Vlan47 Flags: A Tunnel0 Flags: F NS Pkts: 0/0 FastEthernet4/10 Flags: F NS Pkts: 0/9592618 To display the general MFIB configuration status and operational status, use the show command described in the following example.
Chapter 42 IPv6 Multicast Configuration Examples for IPv6 Multicast Configuration Examples for IPv6 Multicast • Example: Enabling IPv6 Multicast Routing, page 42-21 • Example: Configuring IPv6 SSM Mapping, page 42-21 • Example: Configuring Rendezvous Point, page 42-21 Example: Enabling IPv6 Multicast Routing The following is a sample configuration of IPv6 Multicast feature on the Cisco ASR 901 router.
Chapter 42 IPv6 Multicast Troubleshooting Tips Caution We suggest you do not use these debug commands without TAC supervision. Command Name Description [no] debug ipv6 mld Enables debugging MLD protocol activity. [no] debug ipv6 pim Enables debugging PIM protocol activity. [no] debug ipv6 pim neighbor Enables debugging for PIM Hello message processing. [no] debug ipv6 mrib route Enables debugging MRIB routing entry related activity.
Chapter 42 IPv6 Multicast Additional References Additional References The following sections provide references related to IPv6 Multicast feature.
Chapter 42 IPv6 Multicast Feature Information for IPv6 Multicast Feature Information for IPv6 Multicast Table 42-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.
Chapter 42 IPv6 Multicast Feature Information for IPv6 Multicast Table 42-1 Feature Information for IPv6 Multicast Feature Name Releases Feature Information IPv6 Multicast: Multicast Listener Discovery Protocol, Versions 1 and 2 15.4(1)S This feature was introduced on the Cisco ASR 901 routers.
Chapter 42 IPv6 Multicast Feature Information for IPv6 Multicast Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 42-26 OL-23826-09
CH A P T E R 43 Configuring Switched Port Analyzer This feature module describes how to configure a switched port analyzer (SPAN) on the Cisco ASR 901 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.
Chapter 43 Configuring Switched Port Analyzer Understanding SPAN • Ethernet loopback and Traffic generator are not supported when SPAN is enabled. For egress SPAN, the traffic is mirrored before egress xlate translation. • Egress SPAN is only supported for port and not supported for VLAN, EFP, or Port-Channel interfaces. • When you specify source interfaces and do not specify a traffic type [Transmit (Tx), Receive (Rx), or Both], both type is used by default.
Chapter 43 Configuring Switched Port Analyzer Understanding SPAN Figure 43-1 Example of Local SPAN Configuration 1 2 3 4 5 6 7 8 9 10 11 12 E6 E7 E5 E4 E3 E11 E8 E9 Port 5 traffic mirrored on port 10 E12 E10 E2 Network analyzer 361283 E1 SPAN does not affect the switching of network traffic that is received on source ports; a copy of the packets that are received by the source ports is still sent to the destination port.
Chapter 43 Configuring Switched Port Analyzer Configuring SPAN Destination Interface A destination interface (also called a monitoring interface) is a switched interface to which SPAN sends packets for analysis. You can have only one SPAN destination interface. A destination interface has these restrictions: • It needs to be a single physical port. • It cannot be used as an ingress interface. • When an interface is configured as a destination interface, it cannot be configured as a source interface.
Chapter 43 Configuring Switched Port Analyzer Configuring SPAN 4. source {interface interface_type slot/port} | {vlan vlan_ID} | {service instance id interface_type slot/port} [, | - | rx | tx | both] 5. destination {interface interface_type slot/port} 6. no shutdown 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.
Chapter 43 Configuring Switched Port Analyzer Configuring SPAN SUMMARY STEPS 1. enable 2. configure terminal 3. no monitor session session_number 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 monitor session session_number Clears existing SPAN configuration for a session.
Chapter 43 Configuring Switched Port Analyzer Configuring SPAN The following is sample output from the show monitor session all detail command.
Chapter 43 Configuring Switched Port Analyzer Additional References Additional References The following sections provide references to digital optical monitoring feature.
Chapter 43 Configuring Switched Port Analyzer Feature Information for Switched Port Analyzer Feature Information for Switched Port Analyzer Table 43-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.
Chapter 43 Configuring Switched Port Analyzer Feature Information for Switched Port Analyzer Cisco ASR 901 Series Aggregation Services Router Software Configuration Guide 43-10 OL-23826-09
I N D EX best-effort packet delivery Numerics 24-2 BGP 802.
Index IP SLAs with endpoint discovers manually configuring IP SLAs ping or jitter measuring network performance monitoring See CoS 10-18 10-2 10-16 class selectors, DSCP clearing Ethernet CFM 10-31, 10-32 port MEP, configuring 10-30 CLI 10-14 static RMEP, configuring 24-9 10-13 Y.
Index configuration guidelines CFM See DSCP 10-3 Ethernet OAM EVCs DSCP 10-36 assured forwarding 8-7 QoS, general classification 24-32 QoS class maps REP Differentiated Services Code Point 24-50 12-7 configuring 24-9 24-9 class selectors 24-9 default service 24-9 expedited forwarding controllers values E1 interface global parameters hostname password 7-2 3-2 3-5 IP address 24-7 duplex mode, setting 20-2 24-9 E 7-1 3-5 E1 controllers Configuring PFC and ACFC 25-8 conge
Index load balancing F configuring 9-8 understanding modes figure 9-4 Cisco ASR 901 router in a PWE3 9-2 port-channel interfaces TDM over MPLS configuration 9-4 show and more command output 9-6, 9-8 command example STP 9-8 5-9 3-1 frame distribution 1-2 understanding 5-9 filtering show and more command output first-time configuration 9-4 support for 21-31 filtering port-channel load-balance command 21-2 See EtherChannel load balancing 9-1 Ethernet flow point See EFP Ethernet
Index ICMP Router Discovery Protocol support for See IRDP IEEE 802.1ag 1-5 ITU-T Y.1731 See Y.1731 10-2 IEEE 802.3ad See LACP IEEE 802.
Index CLI 5-1 N overview 1-3 manual preemption, REP, configuring 12-20 neighbor offset numbers, REP 12-5 Network Time Protocol marking described See NTP 24-2, 24-14 no commands match command, QoS for classification guidelines NTP 24-4, 24-8 support for 24-50 matching classifications, QoS O See MSC modular QoS command-line interface OAM See MQC client monitoring 10-51 Ethernet CFM 10-31, 10-32 Ethernet OAM 10-45 Ethernet OAM protocol features 1-3 24-8 mobile switching center
Index verifying priority policing, described 3-6 passwords 24-16 priority queues for security described 1-4 performance features for QoS scheduling 1-2 per-port per VLAN policing ping, LSP commands ping mpls ipv4 command 24-19 priority with police 24-12 17-1 24-17 priority with unconditional policing, QoS 17-3 ping mpls pseudowire command 17-3 24-19 PWE3 example of Cisco ASR 901 router in a PWE3 (figure) 21-2 policers described 24-23 24-2 policing described 24-2 Q individual
Index input policy maps described R 24-5 IP packet classification RADIUS 24-7 Layer 2 packet classification 24-7 Layer 3 packet classification 24-7 marking, described match command overview 1-4 RAN, using the Cisco ASR 901 router See RADIUS 24-8 remote failure indications, Ethernet OAM remote loopback, Ethernet OAM 24-6 packet classification 10-38 administrative VLAN 24-2 12-9 packet marking 24-18 administrative VLAN, configuring packet policing 24-2 and MSTP parent-child hierar
Index Structure-agnostic TDM over Packet S 21-3 Structure-agnostic TDM over Packet (SaToP) saving configuration changes scheduling, QoS 5-10 SunNet Manager 24-19 21-3 1-3 system message logging secondary edge port, REP 12-4 syslog facility 1-5 Secure Shell See SSH security features T 1-4 service instance table maps configuration mode configuring 8-4 described 8-8 creating 8-3 defined 8-3 for QoS marking types of 8-4 24-13 support for service-policy command 1-4 Telnet attac
Index REP 12-4 triggering 12-6 Y Y.
