Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide Cisco IOS Release 15.1(3)MR October 2012 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.
CONTENTS About This Guide xix Document Revision History Objectives Audience xix xx xx Organization xx Conventions xxi Related Documentation xxii Obtaining Documentation, Obtaining Support, and Security Guidelines CHAPTER 1 Cisco MWR 2941 Router Overview 1-1 Introduction 1-1 RAN Transport Solutions 1-2 MLPPP Optimization Features 1-2 Distributed IPHC Offload 1-2 Distributed Multilink Point-to-Point Protocol (dMLPPP) Offload Intelligent Cell Site IP Services 1-3 Cell Site Points-of-Presence 1-
Contents Configuring the Hostname and Password 3-7 Verifying the Hostname and Password 3-8 CHAPTER 4 Configuring Gigabit Ethernet Interfaces Configuring the Interface Properties 4-1 Setting the Speed and Duplex Mode 4-2 Enabling the Interface 4-3 Creating Backup Switch Interfaces CHAPTER 5 4-1 Configuring Layer 2 Interfaces 5-1 Configuring a Range of Interfaces Defining a Range Macro 4-4 5-1 5-2 Configuring Layer 2 Optional Interface Features 5-2 Interface Speed and Duplex Configuration
Contents Displaying VLANs 7-11 Configuring VLAN Trunks 7-12 Trunking Overview 7-12 IEEE 802.
Contents CHAPTER Configuring STP 9 9-1 Understanding Spanning-Tree Features 9-1 STP Overview 9-2 Spanning-Tree Topology and BPDUs 9-2 Bridge ID, Switch Priority, and Extended System ID 9-3 Spanning-Tree Interface States 9-4 Blocking State 9-5 Listening State 9-6 Learning State 9-6 Forwarding State 9-6 Disabled State 9-6 How a Switch or Port Becomes the Root Switch or Root Port 9-7 Spanning Tree and Redundant Connectivity 9-7 Spanning-Tree Address Management 9-8 Accelerated Aging to Retain Connectivity
Contents IST, CIST, and CST 10-2 Operations Within an MST Region 10-3 Operations Between MST Regions 10-3 IEEE 802.1s Terminology 10-5 Hop Count 10-5 Boundary Ports 10-6 IEEE 802.1s Implementation 10-6 Port Role Naming Change 10-6 Interoperation Between Legacy and Standard Switches Detecting Unidirectional Link Failure 10-7 Interoperability with IEEE 802.
Contents Understanding Port Fast 11-1 Understanding BPDU Guard 11-2 Understanding BPDU Filtering 11-3 Understanding Root Guard 11-3 Understanding Loop Guard 11-4 Configuring Optional Spanning-Tree Features 11-5 Default Optional Spanning-Tree Configuration 11-5 Optional Spanning-Tree Configuration Guidelines 11-5 Enabling Port Fast 11-5 Enabling BPDU Guard 11-6 Enabling BPDU Filtering 11-7 Enabling Root Guard 11-8 Enabling Loop Guard 11-9 Displaying the Spanning-Tree Status CHAPTER 12 Managing the MAC Ad
Contents Selecting a Tunnel Load-Balancing Algorithm for Cisco Express Forwarding Traffic 13-8 Selecting an Include-Ports Layer 4 Load-Balancing Algorithm for Cisco Express Forwarding Traffic 13-9 Configuration Examples for Configuring a Load-Balancing Scheme for Cisco Express Forwarding Traffic 13-11 Selecting a Cisco Express Forwarding Load-Balancing Algorithm: Example 13-11 Selecting a Tunnel Load-Balancing Algorithm for Cisco Express Forwarding Traffic: Example 13-11 Selecting an Include-Ports Layer 4
Contents SNMP Traps and Fault Alarms 15-5 Configuration Error List 15-6 CFM Version Interoperability 15-6 IP SLAs Support for CFM 15-6 Configuring Ethernet CFM 15-7 Default Ethernet CFM Configuration 15-7 Ethernet CFM Configuration Guidelines 15-7 Configuring the CFM Domain 15-8 Configuring Ethernet CFM Crosscheck 15-11 Configuring Static Remote MEP 15-12 Configuring a Port MEP 15-14 Configuring SNMP Traps 15-15 Configuring Fault Alarms 15-16 Configuring IP SLAs CFM Operation 15-17 Manually Configuring an
Contents OAM Messages 15-34 Setting Up and Configuring Ethernet OAM 15-34 Default Ethernet OAM Configuration 15-34 Ethernet OAM Configuration Guidelines 15-35 Enabling Ethernet OAM on an Interface 15-35 Enabling Ethernet OAM Remote Loopback 15-36 Configuring Ethernet OAM Link Monitoring 15-36 Configuring Ethernet OAM Remote Failure Indications Configuring Ethernet OAM Templates 15-40 Displaying Ethernet OAM Protocol Information Enabling Ethernet Loopback Understanding E-LMI 15-43 15-43 15-46 Configur
Contents Hybrid Clocking 16-3 Pseudowire-Based Clocking 16-3 Synchronous Ethernet 16-3 Synchronous Ethernet ESMC and SSM 16-3 Configuring Clocking and Timing 16-4 Configuring PTP Clocking 16-4 Configuring Global PTP Settings 16-5 Configuring the PTP Interface Settings 16-5 Configure the Global Network Clock 16-9 Configuring PTP Input and Output 16-9 Configuring PTP Redundancy 16-10 Configuring Pseudowire-Based Clocking with Adaptive Clock Recovery Configuring In-Band Master Mode 16-13 Configuring In-Band
Contents Related Documents Standards 17-9 MIBs 17-9 RFCs 17-9 CHAPTER 18 17-9 Configuring MLPPP Backhaul 18-1 Configuring the Card Type 18-1 Configuring E1 Controllers 18-2 Configuring T1 Controllers 18-4 Configuring ATM IMA 18-6 Configuring T1 and E1 Local Switching 18-7 Configuration Examples for T1 and E1 Local Switching 18-8 Configuring a Multilink Backhaul Interface 18-10 Creating a Multilink Bundle 18-10 Configuring PFC and ACFC 18-11 Enabling Multilink and Identifying the Multilink Interface 18-
Contents Configuring IPv6 BFD on an SVI Interface 22-5 Configuring IPv6 BGP on the Cisco MWR 2941 22-7 Configuring BFD for IS-IS 22-8 Configuring BFD for IS-IS on a Single Interface 22-9 Configuring BFD for IS-IS for All Interfaces 22-9 Configuring BFD for Static Routes 22-10 Configuration Examples for BFD 22-11 OSPF with BFD 22-11 BGP with BFD 22-14 IPv6 BFD with IPv6 BGP 22-17 IS-IS with BFD 22-17 CHAPTER 23 Configuring Pseudowire 23-1 Understanding Pseudowire 23-1 Structure-Agnostic TDM over Packet
Contents CHAPTER 24 Configuring MPLS VPNs 24-1 Understanding MPLS VPNs Configuring MPLS VPNs 24-1 24-2 Sample MPLS VPN Configuration CHAPTER 25 Configuring Quality of Service 24-2 25-1 Understanding Quality of Service Traffic Classification 25-2 Traffic Marking 25-2 Traffic Queuing 25-2 Traffic Shaping 25-2 25-1 Configuring Quality of Service 25-2 QoS Limitations 25-3 General QoS Limitations 25-3 Statistics Limitations 25-3 Propagation Limitations 25-4 Classification Limitations 25-5 Marking
Contents Configuring Class-Based Traffic Shaping in a Primary-Level (Parent) Policy Map Configuring the Secondary-Level (Child) Policy Map 25-25 Configuring Ethernet Trusted Mode 25-26 Sample Quality of Service Configurations Switchport Priority 25-26 Classification and Marking 25-27 MPLS Bit Marking 25-28 Priority Queuing 25-28 CHAPTER 26 Configuring Link Noise Monitor Usage Notes CHAPTER 27 25-26 26-1 26-2 Configuring Cisco Discovery Protocol Understanding CDP 27-1 27-1 Configuring CDP 27-2 D
Contents Using Cisco Mobile Wireless Transport Manager (MWTM) 29-2 Configuring SNMP Support 29-3 Enabling Remote Network Management 29-8 Show Commands for Monitoring the Cisco MWR 2941 Router 29-9 Configuring Cisco Networking Services (CNS) 29-11 Process Overview 29-12 Configuring a DHCP Server 29-13 Configuring a TFTP Server 29-13 Configuring the Cisco Configuration Engine 29-14 Verifying the Configuration 29-14 Zero Touch Deployment Sample Configuration 29-14 INDEX Cisco MWR 2941 Mobile Wireless Edge Ro
Contents Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
About This Guide This section describes the objectives, audience, organization, and conventions of this software configuration guide.
About This Guide Objectives This guide explains how to configure software features on the Cisco MWR 2941-DC and MWR 2941-DC-A routers. Unless otherwise stated, features described in this guide apply to both the Cisco MWR 2941-DC and the Cisco MWR 2941-DC-A. Audience This publication is for the person responsible for configuring the router.
About This Guide Chapter Title Description Chapter 12 Managing the MAC Address Table Describes how to manage the MAC address table Chapter 13 Configuring Cisco Express Forwarding Describes how to configure Cisco Express Forwarding Chapter 14 Configuring Resilient Ethernet Describes how to configure Resilient Ethernet Protocol Protocol Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Describes how to configure carrier Ethernet features including Ethernet OAM, CFM, and E–LMI Chapter 16 Conf
About This Guide Convention Description screen font Examples of information displayed on the screen. boldface screen Examples of information the user enters. font < > Nonprinting characters, for example passwords, appear in angle brackets. [ ] Default responses to system prompts appear in square brackets. Note Timesaver Tip Caution Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual. Means the described action saves time.
About This Guide Obtaining Documentation, Obtaining Support, and Security Guidelines For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Cisco MWR 2941 Mobile Wireless Edge Router Release 3.
About This Guide Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 1 Cisco MWR 2941 Router Overview The Cisco MWR 2941 Mobile Wireless Router is cell-site access platforms 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 MWR 2941 Router Overview Introduction The traffic generated by a BTS/Node B is transported to the corresponding BSC/RNC across a network, referred to as the backhaul network, which is often a hub-and-spoke topology with hundreds of BTS/Node Bs connected to a BSC/RNC by point-to-point time division multiplexing (TDM) trunks. These TDM trunks may be leased-line T1/E1s or their logical equivalents, such as microwave links or satellite channels.
Chapter 1 Cisco MWR 2941 Router Overview Introduction Distributed Multilink Point-to-Point Protocol (dMLPPP) Offload Distributed Multilink Point-to-Point Protocol (dMLPPP) allows you to combine T1 or E1 connections into a bundle that has the combined bandwidth of all of the connections in the bundle, providing improved capacity and CPU utilization over MLPPP.
Chapter 1 Cisco MWR 2941 Router Overview Introduction Cell Site Points-of-Presence The cell site becomes a physical Point-of-Presence (POP) from which to offer hotspot services, or voice and wired ISP services, to nearby enterprises and residences. Because many cell sites are located in and around downtown areas, hotels, airports, and convention centers, they make attractive sites for co-locating public wireless LAN (PWLAN) access points and other wireless data overlays.
CH A P T E R 2 Cisco IOS Software Basics This chapter describes the basics of using the Cisco IOS software. Review this information before you configure the router using the command-line interface (CLI).
Chapter 2 Cisco IOS Software Basics Understanding Command Modes Understanding Command Modes The Cisco IOS user interface is used in various command modes. Each command mode permits you to configure different components on your router. The commands available at any given time depend on which command mode you are in. Entering a question mark (?) at a prompt displays a list of commands available for that command mode. The following table lists the most common command modes.
Chapter 2 Cisco IOS Software Basics Undoing a Command or Feature Undoing a Command or Feature If you want to undo a command that you entered or if you want to disable a feature, enter the keyword no before most commands; for example, no ip routing. 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.
Chapter 2 Cisco IOS Software Basics Saving Configuration Changes Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
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.
Chapter 3 First-Time Configuration Understanding the Cisco MWR 2941 Router Interface Numbering Figure 3-1 Cisco MWR 2941 Router Port Numbers HWIC 0 ports 1/0, 1/1, 1/2, 1/3 HWIC 1 ports 2/0, 2/1, 2/2, 2/3 16 T1/E1 ports top row 0/1, 0/3, 0/5, 0/7, 0/9, 0/11, 0/13, 0/15 bottom row 0/0, 0/2, 0/4, 0/6, 0/8, 0/10, 0/12, 0/14 4 GE ports 0/2, 0/3, 0/4, 0/5 (RJ45 100/1000 Ethernet) 252031 Console/ Auxiliary port 2 GE ports 0/0, 0/1 (SFP 1000BT) 2 Mini-coax connectors 10MHZ and 1PPS BITS/SYNC port Slot
Chapter 3 First-Time Configuration Setup Mode • Logical interface numbering for the built-in T1/E1 ports runs from 0/0 through 0/15. Interfaces are hardwired; therefore, port 0 is always logical interface 0/0, port 1 is always logical interface 0/1, and so on. Built-in T1/E1 ports are numbered bottom to top, left to right (bottom row numbered 0-2-4-6-8-10-12-14, top row numbered 1-3-5-7-9-11-13-15).
Chapter 3 First-Time Configuration Setup Mode Note If you make a mistake while using the setup command facility, you can exit the facility and run it again. Press Ctrl-C, and type setup at the enable mode prompt ( 1900#). Configuring Global Parameters Use the following procedure to configure global parameters. Step 1 Caution Power on the router. Messages appear in the terminal emulation program window. Do not press any keys on the keyboard until the messages stop.
Chapter 3 First-Time Configuration Setup Mode subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013. cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706 Cisco IOS Software, 2900 Software (MWR2900-IPRAN-M), Experimental Version 12.
Chapter 3 First-Time Configuration Setup Mode The enable password is used when you do not specify an enable secret password, with some older software versions, and some boot images. Enter enable password: ciscoenable Step 6 To prevent unauthenticated access to the router through ports other than the console port, enter the virtual terminal password. The virtual terminal password is used to protect access to the router over a network interface.
Chapter 3 First-Time Configuration Verifying the Cisco IOS Software Version [0] Go to the IOS command prompt without saving this config. [1] Return back to the setup without saving this config. [2] Save this configuration to nvram and exit. Enter your selection [2]: 2 Building configuration... [OK] Use the enabled mode 'configure' command to modify this configuration.
Chapter 3 First-Time Configuration Configuring the Hostname and Password When the prompt changes to Router, you have entered enable mode. Step 2 Enter global configuration mode. 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.
CH A P T E R 4 Configuring Gigabit Ethernet Interfaces To configure the Gigabit Ethernet (GE) interface on the Cisco MWR 2941, complete the following tasks: • Configuring the Interface Properties, page 4-1 • Setting the Speed and Duplex Mode, page 4-2 • Enabling the Interface, page 4-3 • Creating Backup Switch Interfaces, page 4-4 Configuring the Interface Properties Perform a basic Gigabit Ethernet IP Address configuration by specifying the port adapter and aligning an IP address and subnet mask
Chapter 4 Configuring Gigabit Ethernet Interfaces Setting the Speed and Duplex Mode Command Step 3 Purpose interface gigabitethernet slot/port Specify the port adapter type and the location of the interface to be configured. The slot is always 0 and the port is the number of the port. Example: Router(config)# interface gigabitethernet 0/1 Step 4 switchport mode { access | trunk} Specify the interface mode.
Chapter 4 Configuring Gigabit Ethernet Interfaces Enabling the Interface When you configure an interface speed and duplex mode, follow these guidelines: • If both ends of the line support autonegotiation, use the default autonegotiation settings. • When autonegotiation is turned on for either speed or duplex mode, it autonegotiates both speed and the duplex mode.
Chapter 4 Configuring Gigabit Ethernet Interfaces Creating Backup Switch Interfaces Creating Backup Switch Interfaces You can use the following command to create a backup switch interface: Command Step 1 Purpose Create a backup switch interface. switchport backup interface interface_name preemption [forced | bandwidth | off] delay [time] Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 5 Configuring Layer 2 Interfaces The Cisco MWR 2941 has an onboard layer 2 Gigabit Ethernet switch and supports HWICs with layer 2 interfaces.To configure the layer 2 interfaces on the Cisco MWR 2941, complete the following tasks: • Configuring a Range of Interfaces, page 5-1 • Defining a Range Macro, page 5-2 • Configuring Layer 2 Optional Interface Features, page 5-2 Configuring a Range of Interfaces The interface range command allows you to configure multiple interfaces at once.
Chapter 5 Configuring Layer 2 Interfaces Defining a Range Macro Defining a Range Macro A range macro allows you to create a name that defines a range of interfaces on the Cisco MWR 2941. Follow these steps to configure an interface range macro. Step 1 Command Purpose enable Enter enable mode. Example: Router> enable Router# Step 2 configure terminal Enter configuration mode.
Chapter 5 Configuring Layer 2 Interfaces Configuring Layer 2 Optional Interface Features Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the interface during the reconfiguration. Configuring the Interface Speed Follow these steps to configure the speed of a layer 2 interface. Step 1 Command Purpose enable Enter enable mode. Example: Router> enable Router# Step 2 configure terminal Enter configuration mode.
Chapter 5 Configuring Layer 2 Interfaces Configuring Layer 2 Optional Interface Features Step 3 Command Purpose interface interface slot/port Enter configuration for the interface that you want to modify. Example: Router(config)# interface fastethernet 1/0 Step 4 duplex [auto | full | half] Use the duplex command to set the interface to send traffic at full duplex, half duplex, or to autonegotiate its duplex setting.
Chapter 5 Configuring Layer 2 Interfaces Configuring Layer 2 Optional Interface Features Configuring a Layer 2 Interface as a Layer 2 Trunk Follow these steps to configure an interface as a Layer 2 trunk. Step 1 Command Purpose enable Enter enable mode. Example: Router> enable Router# Step 2 configure terminal Enter configuration mode. Example: Router# configure terminal Router(config)# Step 3 interface interface slot/port Enter configuration for the interface that you want to modify.
Chapter 5 Configuring Layer 2 Interfaces Configuring Layer 2 Optional Interface Features Step 8 Command Purpose no shutdown Activate the interface. Example: Router(config-if)# no shutdown Step 9 end Exit configuration mode. Example: You can use the show running-configuration command to verify the layer 2 trunk configuration. Router(config-if)# end Router# Configuring a Layer 2 Interface as Layer 2 Access Follow these steps to configure a Fast Ethernet interface as Layer 2 access.
Chapter 5 Configuring Layer 2 Interfaces Configuring Layer 2 Optional Interface Features Step 7 Command Purpose no shutdown Activate the interface. Example: Router(config-if)# no shutdown Step 8 end Exit configuration mode. Example: Router(config-if)# end Router# Note You can use the show running-config interface command and the show interfaces command to verify layer 2 access configuration. Cisco MWR 2941 Mobile Wireless Edge Router Release 3.
Chapter 5 Configuring Layer 2 Interfaces Configuring Layer 2 Optional Interface Features Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 6 Configuring HWIC-D-9ESW Interfaces This chapter provides instructions for configuring interfaces on the HWIC-D-9ESW card. Follow these steps to configure a pair of ports on two different switch modules as stacking partners. 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 6 Step 7 Command or Action Purpose interface gigabitethernet partner-interface-id Specifies the partner-interface, and enters interface configuration mode. • Example: Step 8 Configuring HWIC-D-9ESW Interfaces Enter the partner interface number. When you configure the FastEthernet port as a stacking partner, the corresponding GigabitEthernet interface is automatically configured as a stacking partner.
CH A P T E R 7 Configuring VLANs This chapter describes how to configure normal-range VLANs (VLAN IDs 1 to 1005) and extended-range VLANs (VLAN IDs 1006 to 4094) on the Cisco MWR 2941 router. It includes information about VLAN membership modes, VLAN configuration modes, and VLAN trunks. Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.
Chapter 7 Configuring VLANs Understanding VLANs Figure 7-1 shows an example of VLANs segmented into logically defined networks. Figure 7-1 VLANs as Logically Defined Networks Engineering VLAN Marketing VLAN Accounting VLAN Cisco router Floor 3 Gigabit Ethernet Floor 2 90571 Floor 1 VLANs are often associated with IP subnetworks. For example, all the end stations in a particular IP subnet belong to the same VLAN.
Chapter 7 Configuring VLANs Understanding VLANs The router supports Per VLAN Spanning Tree Plus (PVST+) with a maximum of 128 spanning-tree instances. One spanning-tree instance is allowed per VLAN. Note The router does not support Rapid PVST+. Note Network node interfaces (NNIs) support STP by default. Enhanced network interfaces (ENIs) can be configured to support STP. User-network interfaces (UNIs) do not support STP and by default are always in a forwarding state.
Chapter 7 Configuring VLANs Understanding VLANs • Note VLAN number to use when translating from one VLAN type to another This chapter does not provide configuration details for most of these parameters. For complete information on the commands and parameters that control VLAN configuration, see the command reference for this release.
Chapter 7 Configuring VLANs Creating and Modifying VLANs Creating and Modifying VLANs You use VLAN configuration mode, accessed by entering the vlan global configuration command to create VLANs and to modify some parameters. You use the interface configuration mode to define the port membership mode and to add and remove ports from VLANs. The results of these commands are written to the running-configuration file, and you can display the file by entering the show running-config privileged EXEC command.
Chapter 7 Configuring VLANs Creating and Modifying VLANs Table 7-2 Ethernet VLAN Defaults and Ranges (continued) Parameter Default Range VLAN state active active, suspend UNI-ENI VLAN UNI-ENI isolated VLAN 2–1001, 1006–4094 VLAN 1 is always a UNI-ENI isolated VLAN. VLAN Configuration Guidelines Follow these guidelines when creating and modifying VLANs in your network: • The router supports 1005 VLANs. • Normal-range Ethernet VLANs are identified with a number between 1 and 1001.
Chapter 7 Configuring VLANs Creating and Modifying VLANs – If necessary, you can shut down the routed port assigned to the internal VLAN, which frees up the internal VLAN, and then create the extended-range VLAN and re-enable the port, which then uses another VLAN as its internal VLAN. See the “Creating an Extended-Range VLAN with an Internal VLAN ID” section on page 7-9.
Chapter 7 Configuring VLANs Creating and Modifying VLANs Command Purpose Step 4 mtu mtu-size (Optional) Change the MTU size. Step 5 end Return to privileged EXEC mode. Step 6 show vlan {name vlan-name | id vlan-id} Verify your entries. The name option is valid only for VLAN IDs 1 to 1005. Step 7 copy running-config startup config (Optional) Save the configuration in the switch startup configuration file. To delete a VLAN, use the no vlan vlan-id global configuration command.
Chapter 7 Configuring VLANs Creating and Modifying VLANs Command Purpose Step 5 switchport access vlan vlan-id Assign the port to a VLAN. Valid VLAN IDs are 1 to 4094. Step 6 end Return to privileged EXEC mode. Step 7 show running-config interface interface-id Verify the VLAN membership mode of the interface. Step 8 show interfaces interface-id switchport Verify your entries in the Administrative Mode and the Access Mode VLAN fields of the display.
Chapter 7 Configuring VLANs Configuring VLAN Trunking Protocol Configuring VLAN Trunking Protocol This section describes how to configure the VLAN Trunking Protocol (VTP) on an EtherSwitch HWIC, and contains the following tasks: • Configuring a VTP Server • Configuring a VTP Client • Disabling VTP Configuring a VTP Server When a router is in VTP server mode, you can change the VLAN configuration and have it propagate throughout the network.
Chapter 7 Configuring VLANs Displaying VLANs Command Purpose Step 1 enable Enter enable mode. Step 2 configure terminal Enter configuration mode. Step 3 vtp mode transparent Set the router in VTP transparent mode. Step 4 exit Exit configuration mode. Note You can use the show vtp status command to verify the VTP status of the router. Displaying VLANs Use the show vlan privileged EXEC command to display a list of all VLANs on the router, including extended-range VLANs.
Chapter 7 Configuring VLANs Configuring VLAN Trunks Configuring VLAN Trunks • Trunking Overview, page 7-12 • Default Layer 2 Ethernet Interface VLAN Configuration, page 7-13 • Configuring an Ethernet Interface as a Trunk Port, page 7-13 • Configuring Trunk Ports for Load Sharing, page 7-16 Trunking Overview A trunk is a point-to-point link between one or more Ethernet switch interfaces and another networking device such as a router or a switch.
Chapter 7 Configuring VLANs Configuring VLAN Trunks is maintained by Cisco switches separated by a cloud of non-Cisco IEEE 802.1Q switches. The non-Cisco IEEE 802.1Q cloud separating the Cisco switches is treated as a single trunk link between the switches. • If the native VLAN on one end of the trunk is different from the native VLAN on the other end, spanning-tree loops might result. Make sure that the native VLAN for an IEEE 802.1Q trunk is the same on both ends of the trunk link.
Chapter 7 Configuring VLANs Configuring VLAN Trunks Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify the port to be configured for trunking, and enter interface configuration mode. Step 3 no shutdown Enable the port, if necessary. By default, UNIs and ENIs are disabled, and NNIs are enabled. Step 4 switchport mode trunk Configure the interface as a Layer 2 trunk.
Chapter 7 Configuring VLANs Configuring VLAN Trunks If a trunk port with VLAN 1 disabled is converted to a nontrunk port, it is added to the access VLAN. If the access VLAN is set to 1, the port is added to VLAN 1, regardless of the switchport trunk allowed setting. The same is true for any VLAN that has been disabled on the port. A trunk port can become a member of a VLAN if the VLAN is enabled and if the VLAN is in the allowed list for the port.
Chapter 7 Configuring VLANs Configuring VLAN Trunks Beginning in privileged EXEC mode, follow these steps to configure the native VLAN on an IEEE 802.1Q trunk: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Define the interface that is configured as the IEEE 802.1Q trunk, and enter interface configuration mode. Step 3 no shutdown Enable the port, if necessary. By default, UNIs and ENIs are disabled and NNIs are enabled.
Chapter 7 Configuring VLANs Configuring VLAN Trunks • VLANs 8 through 10 retain the default port priority of 128 on Trunk 2. In this way, Trunk 1 carries traffic for VLANs 8 through 10, and Trunk 2 carries traffic for VLANs 3 through 6. If the active trunk fails, the trunk with the lower priority takes over and carries the traffic for all of the VLANs. No duplication of traffic occurs over any trunk port.
Chapter 7 Configuring VLANs Configuring VLAN Trunks Load Sharing Using STP Path Cost You can configure parallel trunks to share VLAN traffic by setting different path costs on a trunk and associating the path costs with different sets of VLANs, blocking different ports for different VLANs. The VLANs keep the traffic separate and maintain redundancy in the event of a lost link. In Figure 7-3, Trunk ports 1 and 2 are configured as 100Base-T ports.
Chapter 7 Configuring VLANs Configuring VLAN Trunks Command Purpose Step 13 exit Return to global configuration mode. Step 14 interface fastethernet0/2 Enter interface configuration mode for Trunk port 2. Step 15 spanning-tree vlan 8-10 cost 30 Set the spanning-tree path cost to 30 for VLANs 2 through 4. Step 16 exit Return to global configuration mode.
Chapter 7 Configuring VLANs Configuring VLAN Trunks Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling VPNs provide enterprise-scale connectivity on a shared infrastructure, often Ethernet-based, with the same security, prioritization, reliability, and manageability requirements of private networks.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding 802.1Q Tunneling the same VLAN. Using 802.1Q tunneling expands VLAN space by using a VLAN-in-VLAN hierarchy and retagging the tagged packets. A port configured to support 802.1Q tunneling is called a tunnel port. When you configure tunneling, you assign a tunnel port to a VLAN ID that is dedicated to tunneling.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding 802.1Q Tunneling Remove the Layer 2 protocol configuration from a trunk port because incoming encapsulated packets change that trunk port to error disabled. The outgoing encapsulated VTP (CDP and STP) packets are dropped on that trunk. Figure 8-2 Original (Normal), 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring 802.1Q Tunneling headers. The packets are encapsulated with the metro tag VLAN ID (set to the access VLAN of the tunnel port) when they are sent through the service-provider network on an 802.1Q trunk port. The priority field on the metro tag is set to match the CoS field of the inner tag (or customer tag) by default. Configuring 802.1Q Tunneling • Default 802.1Q Tunneling Configuration, page 8-4 • 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring 802.1Q Tunneling These are some ways to solve this problem: • Note Use ISL trunks between core switches in the service-provider network. Although customer interfaces connected to edge switches must be 802.1Q trunks, we recommend using ISL trunks for connecting switches in the core layer. The Cisco MWR 2941 router does not support ISL trunks.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring 802.1Q Tunneling 802.1Q Tunneling and Other Features Although 802.1Q tunneling works well for Layer 2 packet switching, there are incompatibilities between some Layer 2 features and Layer 3 switching. Routing on VLANs with 802.1Q Tunnel Ports IP routing is not supported on a VLAN that includes 802.1Q tunnel ports. Packets received from a tunnel port are forwarded based only on Layer 2 information.
Chapter 8 Configuring IEEE 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding VLAN Mapping • Traditional 802.1Q tunneling (QinQ)—Performs all-to-one bundling of C-VLAN IDs to a single S-VLAN ID for the port. The S-VLAN is added to the incoming unmodified C-VLAN. You can configure the port as an 802.1Q tunnel port for traditional QinQ, or you can configure selective QinQ for a more flexible implementation. Mapping takes place at ingress and egress of the port.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring VLAN Mapping Configuring VLAN Mapping • Default VLAN Mapping Configuration, page 8-9 • VLAN Mapping Configuration Guidelines, page 8-9 • Configuring VLAN Mapping, page 8-9 Default VLAN Mapping Configuration By default, no VLAN mapping is configured. VLAN Mapping Configuration Guidelines • The Cisco MWR 2941 uses 802.1Q tunnel ports for both traditional and selective QinQ. VLAN mapping is only supported on 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring VLAN Mapping Command Purpose Step 6 show running-config interface type number Verify the configuration. Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file. This example shows how to bundle all traffic on the port to leave the router with the S-VLAN ID of 100.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding Layer 2 Protocol Tunneling Router(config-if)# exit Understanding Layer 2 Protocol Tunneling Customers at different sites connected across a service-provider network need to use various Layer 2 protocols to scale their topologies to include all remote sites, as well as the local sites.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding Layer 2 Protocol Tunneling Figure 8-5 Layer 2 Protocol Tunneling Customer X Site 1 VLANs 1ot 100 Figure 8-6 Layer 2 Network Topology without Proper Convergence 101821 Customer X virtual network VLANs 1 to 100 Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling You can enable Layer 2 protocol tunneling (by protocol) on the ports that are connected to the customer in the edge switches of the service-provider network. The service-provider edge switches connected to the customer switch perform the tunneling process. Edge-switch tunnel ports are connected to customer 802.1Q trunk ports.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling Table 8-1 Default Layer 2 Ethernet Interface VLAN Configuration (continued) Feature Default Setting Drop threshold None set. CoS value If a CoS value is configured on the interface, that value is used to set the BPDU CoS value for Layer 2 protocol tunneling. If no CoS value is configured at the interface level, the default value for CoS marking of L2 protocol tunneling BPDUs is 5.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling Beginning in privileged EXEC mode, follow these steps to configure a port for Layer 2 protocol tunneling: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Enter interface configuration mode, and enter the interface to be configured as a tunnel port.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Monitoring and Maintaining Tunneling and Mapping Status Use the no l2protocol-tunnel [cdp | stp | vtp] interface configuration command to disable protocol tunneling for one of the Layer 2 protocols or for all three. Use the no l2protocol-tunnel shutdown-threshold [cdp | stp | vtp] and the no l2protocol-tunnel drop-threshold [cdp | stp | vtp] commands to return the shutdown and drop thresholds to the default settings.
CH A P T E R 9 Configuring STP This chapter describes how to configure the Spanning Tree Protocol (STP) on port-based VLANs on the Cisco MWR 2941 router. The router can use the per-VLAN spanning-tree plus (PVST+) protocol based on the IEEE 802.1D standard and Cisco proprietary extensions, or the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol based on the IEEE 802.1w standard. On the Cisco MWR 2941 router, STP is enabled by default on network node interfaces (NNIs).
Chapter 9 Configuring STP Understanding Spanning-Tree Features • Spanning-Tree Interoperability and Backward Compatibility, page 9-10 • STP and IEEE 802.1Q Trunks, page 9-10 For configuration information, see the “Configuring Spanning-Tree Features” section on page 9-10. For information about optional spanning-tree features, see Chapter 11, “Configuring Optional Spanning-Tree Features.
Chapter 9 Configuring STP Understanding Spanning-Tree Features When the switches in a network are powered up, each functions as the root switch. Each switch sends a configuration BPDU through all of its ports, or on the Cisco MWR 2941 router, only through the ports. The BPDUs communicate and compute the spanning-tree topology.
Chapter 9 Configuring STP Understanding Spanning-Tree Features The switch supports the IEEE 802.1t spanning-tree extensions, and some of the bits previously used for the switch priority are now used as the VLAN identifier. The result is that fewer MAC addresses are reserved for the switch, and a larger range of VLAN IDs can be supported, all while maintaining the uniqueness of the bridge ID.
Chapter 9 Configuring STP Understanding Spanning-Tree Features Figure 9-1 illustrates how an interface moves through the states.
Chapter 9 Configuring STP Understanding Spanning-Tree Features • Does not learn addresses • Receives BPDUs Listening State The listening state is the first state a Layer 2 interface enters after the blocking state. The interface enters this state when the spanning tree decides that the interface should participate in frame forwarding.
Chapter 9 Configuring STP Understanding Spanning-Tree Features How a Switch or Port Becomes the Root Switch or Root Port If all switches in a network are enabled with default spanning-tree settings, the switch with the lowest MAC address becomes the root switch. In Figure 9-2, Switch A is elected as the root switch because the switch priority of all the switches is set to the default (32768) and Switch A has the lowest MAC address.
Chapter 9 Configuring STP Understanding Spanning-Tree Features Spanning Tree and Redundant Connectivity Active link Blocked link Workstations 101226 Figure 9-3 Spanning-Tree Address Management IEEE 802.1D specifies 17 multicast addresses, ranging from 0x00180C2000000 to 0x0180C2000010, to be used by different bridge protocols. These addresses are static addresses that cannot be removed.
Chapter 9 Configuring STP Understanding Spanning-Tree Features Spanning-Tree Modes and Protocols The switch NNIs and ENIs with STP enabled support these spanning-tree modes and protocols: • PVST+—This spanning-tree mode is based on the IEEE 802.1D standard and Cisco proprietary extensions. It is the default spanning-tree mode used on most Ethernet port-based VLANs. The PVST+ runs on each VLAN on the switch up to the maximum supported, ensuring that each has a loop-free path through the network.
Chapter 9 Configuring STP Configuring Spanning-Tree Features Supported Spanning-Tree Instances In PVST+ mode, the switch supports up to 128 spanning-tree instances. In MSTP mode, the switch supports up to 65 MST instances. You can map up to 255 VLANs to a particular MST instance. Spanning-Tree Interoperability and Backward Compatibility Table 9-2 lists the interoperability and compatibility among the supported spanning-tree modes in a network.
Chapter 9 Configuring STP Configuring Spanning-Tree Features • Configuring Port Priority, page 9-16 (optional) • Configuring Path Cost, page 9-18 (optional) • Configuring the Switch Priority of a VLAN, page 9-19 (optional) • Configuring Spanning-Tree Timers, page 9-20 (optional) Default Spanning-Tree Configuration Table 9-3 shows the default spanning-tree configuration. Table 9-3 Default Spanning-Tree Configuration Feature Default Setting Enable state Enabled on NNIs in VLAN 1.
Chapter 9 Configuring STP Configuring Spanning-Tree Features If 255 instances of spanning tree are already in use, you can disable spanning tree on STP ports in one of the VLANs and then enable it on the VLAN where you want it to run. Use the no spanning-tree vlan vlan-id global configuration command to disable spanning tree on a specific VLAN, and use the spanning-tree vlan vlan-id global configuration command to enable spanning tree on the desired VLAN.
Chapter 9 Configuring STP Configuring Spanning-Tree Features Step 4 Command Purpose spanning-tree Enable spanning tree on the interface. The interface will belong to the switch spanning tree instance along with NNIs in the VLAN. Note This command is visible only on ENIs. Step 5 end Return to privileged EXEC mode. Step 6 show spanning-tree interface interface-id Verify your entries. Step 7 copy running-config startup-config (Optional) Save your entries in the configuration file.
Chapter 9 Configuring STP Configuring Spanning-Tree Features Step 7 Command Purpose show spanning-tree summary Verify your entries. and show spanning-tree interface interface-id Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file. To return to the default setting, use the no spanning-tree mode global configuration command. To return the port to its default spanning-tree mode setting, use the no spanning-tree link-type interface configuration command.
Chapter 9 Configuring STP Configuring Spanning-Tree Features If any root switch for the specified VLAN has a switch priority lower than 24576, the switch sets its own priority for the specified VLAN to 4096 less than the lowest switch priority. (4096 is the value of the least-significant bit of a 4-bit switch priority value as shown in Table 9-1 on page 9-4.) Note The spanning-tree vlan vlan-id root global configuration command fails if the value necessary to be the root switch is less than 1.
Chapter 9 Configuring STP Configuring Spanning-Tree Features To return to the default setting, use the no spanning-tree vlan vlan-id root global configuration command. Configuring a Secondary Root Switch When you configure a device as the secondary root, the switch priority is modified from the default value (32768) to 28672. The switch is then likely to become the root switch for the specified VLAN if the primary root switch fails.
Chapter 9 Configuring STP Configuring Spanning-Tree Features Beginning in privileged EXEC mode, follow these steps to configure the port priority of a spanning-tree port. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify an interface to configure, and enter interface configuration mode.
Chapter 9 Configuring STP Configuring Spanning-Tree Features Configuring Path Cost The spanning-tree path cost default value is derived from the media speed of an interface (port running spanning tree). If a loop occurs, spanning tree uses cost when selecting an interface to put in the forwarding state. You can assign lower cost values to interfaces that you want selected first and higher cost values that you want selected last.
Chapter 9 Configuring STP Configuring Spanning-Tree Features To return to the default setting, use the no spanning-tree [vlan vlan-id] cost interface configuration command. For information on how to configure load sharing on trunk ports by using spanning-tree path costs, see the “Configuring Trunk Ports for Load Sharing” section on page 7-16. Configuring the Switch Priority of a VLAN You can configure the switch priority and make it more likely that the router will be chosen as the root switch.
Chapter 9 Configuring STP Configuring Spanning-Tree Features Configuring Spanning-Tree Timers Table 9-4 describes the timers that affect the entire spanning-tree performance. Table 9-4 Spanning-Tree Timers Variable Description Hello timer Controls how often the router broadcasts hello messages to other switches. Forward-delay timer Controls how long each of the listening and learning states last before the STP port begins forwarding.
Chapter 9 Configuring STP Configuring Spanning-Tree Features To return to the default setting, use the no spanning-tree vlan vlan-id hello-time global configuration command. Configuring the Forwarding-Delay Time for a VLAN Beginning in privileged EXEC mode, follow these steps to configure the forwarding-delay time for a VLAN. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode.
Chapter 9 Configuring STP Displaying the Spanning-Tree Status Command Purpose Step 4 show spanning-tree vlan vlan-id Verify your entries. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. To return to the default setting, use the no spanning-tree vlan vlan-id max-age global configuration command.
CH A P T E R 10 Configuring MSTP This chapter describes how to configure the Cisco implementation of the IEEE 802.1s Multiple STP (MSTP) on the Cisco MWR 2941 router. On the Cisco MWR 2941 router, user network interfaces (UNIs) do not participate in STP and immediately forward traffic when they are brought up. STP is enabled by default on network node interfaces (NNIs), and can be also be enabled on enhanced network interfaces (ENIs). If STP is not enabled on an ENI, the interface always forwards traffic.
Chapter 10 Configuring MSTP Understanding MSTP • Configuring MSTP Features, page 10-13 • Displaying the MST Configuration and Status, page 10-26 Understanding MSTP MSTP, which uses RSTP for rapid convergence, enables VLANs to be grouped into a spanning-tree instance, with each instance having a spanning-tree topology independent of other spanning-tree instances.
Chapter 10 Configuring MSTP Understanding MSTP The IST is the only spanning-tree instance that sends and receives BPDUs; all of the other spanning-tree instance information is contained in M-records, which are encapsulated within MSTP BPDUs. Because the MSTP BPDU carries information for all instances, the number of BPDUs that need to be processed by a switch to support multiple spanning-tree instances is significantly reduced.
Chapter 10 Configuring MSTP Understanding MSTP The IST connects all the MSTP switches in the region and appears as a subtree in the CST that encompasses the entire switched domain, with the root of the subtree being the IST master. The MST region appears as a virtual switch to adjacent STP switches and MST regions. Figure 10-1 shows a network with three MST regions and a legacy IEEE 802.1D switch (D). The IST master for region 1 (A) is also the CST root.
Chapter 10 Configuring MSTP Understanding MSTP IEEE 802.1s Terminology Some MST naming conventions used in Cisco’s prestandard implementation have been changed to identify some internal or regional parameters. These parameters are significant only within an MST region, as opposed to external parameters that are relevant to the whole network.
Chapter 10 Configuring MSTP Understanding MSTP Boundary Ports In the Cisco prestandard implementation, a boundary port connects an MST region to a single spanning-tree region running RSTP, to a single spanning-tree region running PVST+ or to another MST region with a different MST configuration. A boundary port also connects to a LAN, the designated switch of which is either a single spanning-tree switch or a switch with a different MST configuration.
Chapter 10 Configuring MSTP Understanding MSTP Interoperation Between Legacy and Standard Switches Because automatic detection of prestandard switches can fail, you can use an interface configuration command to identify prestandard ports. A region cannot be formed between a standard and a prestandard switch, but they can interoperate by using the CIST. Only the capability of load balancing over different instances is lost in that particular case.
Chapter 10 Configuring MSTP Understanding RSTP Figure 10-3 illustrates a unidirectional link failure that typically creates a bridging loop. Switch A is the root switch, and its BPDUs are lost on the link leading to switch B. RSTP and MST BPDUs include the role and state of the sending port. With this information, switch A can detect that switch B does not react to the superior BPDUs it sends and that switch B is the designated, not root switch.
Chapter 10 Configuring MSTP Understanding RSTP Port Roles and the Active Topology The RSTP provides rapid convergence of the spanning tree by assigning port roles and by learning the active topology. The RSTP builds upon the IEEE 802.1D STP to select the switch with the highest switch priority (lowest numerical priority value) as the root switch as described in the “Spanning-Tree Topology and BPDUs” section on page 9-2. Then the RSTP assigns one of these port roles to individual ports.
Chapter 10 Configuring MSTP Understanding RSTP • Root ports—If the RSTP selects a new root port, it blocks the old root port and immediately transitions the new root port to the forwarding state. • Point-to-point links—If you connect a port to another port through a point-to-point link and the local port becomes a designated port, it negotiates a rapid transition with the other port by using the proposal-agreement handshake to ensure a loop-free topology.
Chapter 10 Configuring MSTP Understanding RSTP Synchronization of Port Roles When the switch receives a proposal message on one of its ports and that port is selected as the new root port, the RSTP forces all other ports to synchronize with the new root information. The switch is synchronized with superior root information received on the root port if all other ports are synchronized. An individual port on the switch is synchronized if • That port is in the blocking state.
Chapter 10 Configuring MSTP Understanding RSTP Table 10-3 RSTP BPDU Flags Bit Function 0 Topology change (TC) 1 Proposal 2–3: Port role: 00 Unknown 01 Alternate port 10 Root port 11 Designated port 4 Learning 5 Forwarding 6 Agreement 7 Topology change acknowledgement (TCA) The sending switch sets the proposal flag in the RSTP BPDU to propose itself as the designated switch on that LAN. The port role in the proposal message is always set to the designated port.
Chapter 10 Configuring MSTP Configuring MSTP Features Topology Changes This section describes the differences between the RSTP and the IEEE 802.1D in handling spanning-tree topology changes. • Detection—Unlike IEEE 802.1D in which any transition between the blocking and the forwarding state causes a topology change, only transitions from the blocking to the forwarding state cause a topology change with RSTP (only an increase in connectivity is considered a topology change).
Chapter 10 Configuring MSTP Configuring MSTP Features • Configuring the Forwarding-Delay Time, page 10-23 (optional) • Configuring the Maximum-Aging Time, page 10-23 (optional) • Configuring the Maximum-Hop Count, page 10-24 (optional) • Specifying the Link Type to Ensure Rapid Transitions, page 10-24 (optional) • Designating the Neighbor Type, page 10-25 (optional) • Restarting the Protocol Migration Process, page 10-25 (optional) Default MSTP Configuration Table 10-4 shows the default MSTP
Chapter 10 Configuring MSTP Configuring MSTP Features • PVST+ and MSTP are supported, but only one version can be active at any time. (For example, all VLANs run PVST+ or all VLANs run MSTP.) For more information, see the “Spanning-Tree Interoperability and Backward Compatibility” section on page 9-10. For information on the recommended trunk port configuration, see the “Interaction with Other Features” section on page 7-13.
Chapter 10 Configuring MSTP Configuring MSTP Features Command Purpose Step 4 name name Specify the configuration name. The name string has a maximum length of 32 characters and is case sensitive. Step 5 revision version Specify the configuration revision number. The range is 0 to 65535. Step 6 show pending Verify your configuration by displaying the pending configuration. Step 7 exit Apply all changes, and return to global configuration mode. Step 8 spanning-tree mode mst Enable MSTP.
Chapter 10 Configuring MSTP Configuring MSTP Features To configure the router to become the root switch, use the spanning-tree mst instance-id root global configuration command to modify the switch priority from the default value (32768) to a significantly lower value so that the switch becomes the root switch for the specified spanning-tree instance. When you enter this command, the switch checks the switch priorities of the root switches.
Chapter 10 Configuring MSTP Configuring MSTP Features Use the diameter keyword, which is available only for MST instance 0, to specify the Layer 2 network diameter (that is, the maximum number of switch hops between any two end stations in the Layer 2 network). When you specify the network diameter, the switch automatically sets an optimal hello time, forward-delay time, and maximum-age time for a network of that diameter, which can significantly reduce the convergence time.
Chapter 10 Configuring MSTP Configuring MSTP Features Beginning in privileged EXEC mode, follow these steps to configure a switch as the secondary root switch. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 spanning-tree mst instance-id root secondary [diameter net-diameter [hello-time seconds]] Configure a switch as the secondary root switch.
Chapter 10 Configuring MSTP Configuring MSTP Features Beginning in privileged EXEC mode, follow these steps to configure the MSTP port priority of an interface. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify an interface to configure, and enter interface configuration mode. Valid interfaces include physical NNIs or ENIs with spanning tree enabled, VLANs, and NNIs. The VLAN ID range is 1 to 4094.
Chapter 10 Configuring MSTP Configuring MSTP Features Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify an interface to configure, and enter interface configuration mode. Valid interfaces include physical NNIs or ENIs with spanning tree enabled, VLANs, and NNIs. The VLAN ID range is 1 to 4094. The port-channel range is 1 to 48.
Chapter 10 Configuring MSTP Configuring MSTP Features Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 spanning-tree mst instance-id priority priority Configure the switch priority. • For instance-id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is 0 to 4094. • For priority, the range is 0 to 61440 in increments of 4096; the default is 32768.
Chapter 10 Configuring MSTP Configuring MSTP Features To return the router to its default setting, use the no spanning-tree mst hello-time global configuration command. Configuring the Forwarding-Delay Time Beginning in privileged EXEC mode, follow these steps to configure the forwarding-delay time for all MST instances. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode.
Chapter 10 Configuring MSTP Configuring MSTP Features Configuring the Maximum-Hop Count Beginning in privileged EXEC mode, follow these steps to configure the maximum-hop count for all MST instances. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 spanning-tree mst max-hops hop-count Specify the number of hops in a region before the BPDU is discarded, and the information held for a port is aged.
Chapter 10 Configuring MSTP Configuring MSTP Features To return the port to its default setting, use the no spanning-tree link-type interface configuration command. Designating the Neighbor Type A topology could contain both prestandard and IEEE 802.1s standard compliant devices. By default, ports can automatically detect prestandard devices, but they can still receive both standard and prestandard BPDUs. When there is a mismatch between a device and its neighbor, only the CIST runs on the interface.
Chapter 10 Configuring MSTP Displaying the MST Configuration and Status Displaying the MST Configuration and Status To display the spanning-tree status, use one or more of the privileged EXEC commands in Table 10-5: Table 10-5 Commands for Displaying MST Status Command Purpose show spanning-tree mst configuration Displays the MST region configuration. show spanning-tree mst configuration digest Displays the MD5 digest included in the current MSTCI.
CH A P T E R 11 Configuring Optional Spanning-Tree Features This chapter describes how to configure optional spanning-tree features on the Cisco MWR 2941router. You can configure all of these features when your router is running per-VLAN spanning-tree plus (PVST+). You can configure only the noted features when your router is running the Multiple Spanning Tree Protocol (MSTP) protocol. On the Cisco MWR 2941 router, STP is enabled by default on network node interfaces (NNIs).
Chapter 11 Configuring Optional Spanning-Tree Features Understanding Optional Spanning-Tree Features You can use Port Fast on STP ports connected to a single workstation or server, as shown in Figure 11-1, to allow those devices to immediately connect to the network, rather than waiting for the spanning tree to converge. STP ports connected to a single workstation or server should not receive bridge protocol data units (BPDUs).
Chapter 11 Configuring Optional Spanning-Tree Features Understanding Optional Spanning-Tree Features Fast-enabled STP ports do not receive BPDUs. Receiving a BPDU on a Port Fast-enabled port signals an invalid configuration, such as the connection of an unauthorized device, and the BPDU guard feature puts the interface in the error-disabled state.
Chapter 11 Configuring Optional Spanning-Tree Features Understanding Optional Spanning-Tree Features If the router is operating in multiple spanning-tree (MST) mode, root guard forces the interface to be a designated port. If a boundary port is blocked in an internal spanning-tree (IST) instance because of root guard, the interface also is blocked in all MST instances. A boundary port is an interface that connects to a LAN, the designated switch of which is either an 802.
Chapter 11 Configuring Optional Spanning-Tree Features Configuring Optional Spanning-Tree Features Configuring Optional Spanning-Tree Features • Default Optional Spanning-Tree Configuration, page 11-5 • Optional Spanning-Tree Configuration Guidelines, page 11-5 • Enabling Port Fast, page 11-5 (optional) • Enabling BPDU Guard, page 11-6 (optional) • Enabling BPDU Filtering, page 11-7 (optional) • Enabling Root Guard, page 11-8 (optional) • Enabling Loop Guard, page 11-9 (optional) Default Opt
Chapter 11 Configuring Optional Spanning-Tree Features Configuring Optional Spanning-Tree Features Beginning in privileged EXEC mode, follow these steps to enable Port Fast. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify an STP interface to configure, and enter interface configuration mode.
Chapter 11 Configuring Optional Spanning-Tree Features Configuring Optional Spanning-Tree Features Caution Configure Port Fast only on STP ports that connect to end stations; otherwise, an accidental topology loop could cause a data packet loop and disrupt switch and network operation. You also can use the spanning-tree bpduguard enable interface configuration command to enable BPDU guard on any STP port without also enabling the Port Fast feature.
Chapter 11 Configuring Optional Spanning-Tree Features Configuring Optional Spanning-Tree Features You can also use the spanning-tree bpdufilter enable interface configuration command to enable BPDU filtering on any STP port without also enabling the Port Fast feature. This command prevents the STP port from sending or receiving BPDUs. Caution Enabling BPDU filtering on an STP port is the same as disabling spanning tree on it and can result in spanning-tree loops.
Chapter 11 Configuring Optional Spanning-Tree Features Configuring Optional Spanning-Tree Features Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify an interface to configure, and enter interface configuration mode. Step 3 spanning-tree guard root Enable root guard on the STP port. By default, root guard is disabled on all interfaces. Step 4 end Return to privileged EXEC mode. Step 5 show running-config Verify your entries.
Chapter 11 Configuring Optional Spanning-Tree Features Displaying the Spanning-Tree Status Displaying the Spanning-Tree Status To display the spanning-tree status, use one or more of the privileged EXEC commands in Table 11-2: Table 11-2 Commands for Displaying the Spanning-Tree Status Command Purpose show spanning-tree active Displays spanning-tree information on active interfaces only. show spanning-tree detail Displays a detailed summary of interface information.
CH A P T E R 12 Managing the MAC Address Table The MAC address table contains address information that the switch uses to forward traffic between ports. All MAC addresses in the address table are associated with one or more ports. The address table includes these types of addresses: • Dynamic address: a source MAC address that the switch learns and then ages when it is not in use. • Static address: a manually entered unicast address that does not age and that is not lost when the switch resets.
Chapter 12 Managing the MAC Address Table Displaying Address Table Entries • You cannot disable MAC address learning on a VLAN that is used internally by the router. If the VLAN ID that you enter is an internal VLAN, the switch generates an error message and rejects the command. To view internal VLANs in use, enter the show vlan internal usage privileged EXEC command. • If you disable MAC address learning on a VLAN that includes a secure port, MAC address learning is not disabled on that port.
Chapter 12 Managing the MAC Address Table Displaying Address Table Entries Table 12-1 Commands for Displaying the MAC Address Table (continued) Command Description show mac address-table count Displays the number of addresses present in all VLANs or the specified VLAN. show mac address-table dynamic Displays only dynamic MAC address table entries. show mac address-table interface Displays the MAC address table information for the specified interface.
Chapter 12 Managing the MAC Address Table Displaying Address Table Entries Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 13 Configuring Cisco Express Forwarding This module contains information about Cisco Express Forwarding and describes the required and optional tasks for configuring a load-balancing scheme for Cisco Express Forwarding traffic. Load-balancing allows you to optimize resources by distributing traffic over multiple paths. Cisco Express Forwarding is an advanced Layer 3 IP switching technology.
Chapter 13 Configuring Cisco Express Forwarding Information About Cisco Express Forwarding • Note Scalability—Cisco Express Forwarding offers full switching capacity at each line card when distributed Cisco Express Forwarding mode is active. Distributed Cisco Express Forwarding is a distributed switching mechanism that scales linearly with the number of interface cards and the bandwidth installed in the router. Distributed Cisco Express Forwarding is not currently supported on the Cisco MWR 2941.
Chapter 13 Configuring Cisco Express Forwarding Information About Cisco Express Forwarding • Frame Relay • High-Level Data Link Control (HDLC) • PPP • Spatial Reuse Protocol (SRP) • TokenRing • Tunnels Main Components of Cisco Express Forwarding Operation Information conventionally stored in a route cache is stored in several data structures for Cisco Express Forwarding switching. The data structures provide optimized lookup for efficient packet forwarding.
Chapter 13 Configuring Cisco Express Forwarding Information About Cisco Express Forwarding Cisco Express Forwarding Adjacency Tables Overview A node is said to be adjacent to another node if the node can be reached with a single hop across a link layer (Layer 2). Cisco Express Forwarding stores forwarding information (outbound interface and MAC header rewrite) for adjacent nodes in a data structure called the adjacency table.
Chapter 13 Configuring Cisco Express Forwarding Information About Cisco Express Forwarding Table 13-1 Adjacency Types That Require Special Handling (continued) Packets of This Adjacency Type Receive This Processing Discard adjacency The router discards the packets. Drop adjacency The router drops the packets. Unresolved Adjacency When a link-layer header is prepended to a packet, the FIB requires the prepended header to point to an adjacency corresponding to the next hop.
Chapter 13 Configuring Cisco Express Forwarding Configuring Cisco Express Forwarding Central Cisco Express Forwarding Mode Operation Cisco 7500 series router running CEF Route Processor Routing table Interface card E1 E2 Adjacency table FIB table Interface card E1 Interface card E2 E1 S6783 Figure 13-2 E2 Cisco Catalyst switches Workgroup LAN Workgroup LAN Workgroup LAN Configuring Cisco Express Forwarding Cisco Express Forwarding load balancing is based on a combination of source and de
Chapter 13 Configuring Cisco Express Forwarding Configuring Cisco Express Forwarding Supported Features Cisco IOS Release 15.
Chapter 13 Configuring Cisco Express Forwarding Configuring Cisco Express Forwarding Enabling or Disabling Cisco Express Forwarding Per-Destination Load Balancing Perform this task to enable or disable Cisco Express Forwarding per-destination load balancing. Note The Cisco MWR 2941 router does not support per-packet load balancing. Cisco Express Forwarding per-destination load balancing is enabled by default on the Cisco MWR 2941; therefore no configuration is required to use this feature.
Chapter 13 Configuring Cisco Express Forwarding Configuring Cisco Express Forwarding Step 3 Command or Action Purpose ip cef load-sharing algorithm {universal [id] include-ports {source [id] | [destination] [id] | source [id] destination [id]}} Selects a Cisco Express Forwarding load-balancing algorithm. • The universal keyword sets the load-balancing algorithm to one that uses a source and destination and an ID hash.
Chapter 13 Configuring Cisco Express Forwarding Configuring Cisco Express Forwarding Restrictions The Layer 4 load-balancing algorithm applies to software switched packets. For platforms that switch traffic using a hardware forwarding engine, the hardware load-balancing decision might be different from the software load-balancing decision for the same traffic stream. You might want to override the configured algorithm. Step 1 Command or Action Purpose enable Enables privileged EXEC mode.
Chapter 13 Configuring Cisco Express Forwarding Configuration Examples for Configuring a Load-Balancing Scheme for Cisco Express Forwarding Traffic Configuration Examples for Configuring a Load-Balancing Scheme for Cisco Express Forwarding Traffic This section provides the following examples for configuring a load-balancing scheme for Cisco Express Forwarding traffic. Selecting a Cisco Express Forwarding Load-Balancing Algorithm: Example The router is set to perform universal load balancing by default.
Chapter 13 Configuration Examples for Configuring a Load-Balancing Scheme for Cisco Express Forwarding Traffic Configuring Cisco Express Forwarding Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 14 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 14 Configuring Resilient Ethernet Protocol Understanding Resilient Ethernet Protocol Figure 14-1 REP Open Segments E1 Edge port Blocked port Link failure E2 E1 E2 201888 E1 The segment shown in Figure 14-1 is an open segment; there is no connectivity between the two edge ports. The REP segment cannot cause a bridging loop, and you can safely connect the segment edges to any network.
Chapter 14 Configuring Resilient Ethernet Protocol Understanding Resilient Ethernet Protocol You can construct almost any type of network based on REP segments. REP also supports VLAN load-balancing, controlled by the primary edge port but occurring at any port in the segment. In access ring topologies, the neighboring switch might not support REP, as shown in Figure 14-3. In this case, you can configure the non-REP facing ports (E1 and E2) as edge no-neighbor ports.
Chapter 14 Configuring Resilient Ethernet Protocol Understanding Resilient Ethernet Protocol A segment port does not become operational if: • No neighbor has the same segment ID. • More than one neighbor has the same segment ID. • The neighbor does not acknowledge the local port as a peer. Each port creates an adjacency with its immediate neighbor. After the neighbor adjacencies are created, the ports negotiate to determine one blocked port for the segment, the alternate port.
Chapter 14 Configuring Resilient Ethernet Protocol Understanding Resilient Ethernet Protocol (downstream position from the primary edge port) or a negative offset number (downstream position from the secondary edge port). If E2 became the primary edge port, its offset number would then be 1, and E1 would be -1. • By entering the preferred keyword to select the port that you previously configured as the preferred alternate port with the rep segment segment-id preferred interface configuration command.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) Note Do not configure VLAN load balancing on an interface that carries Ethernet over multiprotocol label switching (EoMPLS) traffic. VLAN load balancing across the REP ring might prevent forwarding some of the EoMPLS traffic. Spanning Tree Interaction REP does not interact with STP or with the Flex Link feature, but can coexist with both.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) • Default REP Configuration, page 14-7 • REP Configuration Guidelines, page 14-7 • Configuring the REP Administrative VLAN, page 14-8 • Configuring REP Interfaces, page 14-10 • Setting Manual Preemption for VLAN Load Balancing, page 14-13 • Configuring SNMP Traps for REP, page 14-14 • Monitoring REP, page 14-15 Default REP Configuration REP is disabled on all interfaces.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) – If only one port on a switch is configured in a segment, the port should be an edge port. – If two ports on a switch belong to the same segment, they must be both edge ports, both regular segment ports, or one regular port and one edge no-neighbor port. An edge port and regular segment port on a switch cannot belong to the same segment.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) Beginning in privileged EXEC mode, follow these steps to configure the REP administrative VLAN: Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 rep admin vlan vlan-id Configures a REP administrative VLAN.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) Configuring REP Interfaces For REP operation, you need to enable it on each segment interface and to identify the segment ID. This step is required and must be done before other REP configuration. You must also configure a primary and secondary edge port on each segment. All other steps are optional.
Chapter 14 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 optional keywords are available. • Enter edge to configure the port as an edge port.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) Step 8 Command Purpose rep block port {id port-id | neighbor-offset | preferred} vlan {vlan-list | all} (Optional) Configures VLAN load balancing on the primary edge port, identifies the REP alternate port in one of three ways, and configures the VLANs to be blocked on the alternate port. Example: • Enter the id port-id to identify the alternate port by port ID.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) Command Purpose Step 13 show rep topology [segment segment-id] Indicates which port in the segment is the primary edge port.
Chapter 14 Configuring Resilient Ethernet Protocol Configuring Resilient Ethernet Protocol (REP) Beginning in privileged EXEC mode, follow these steps on the switch that has the segment primary edge port to manually trigger VLAN load balancing on a segment: 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 14 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 Note Step 4 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 14 Configuring Resilient Ethernet Protocol Configuration Examples for REP Configuration Examples for REP • Configuring the REP Administrative VLAN: Example, page 14-16 • Configuring a REP Interface: Example, page 14-16 • Setting the Preemption for VLAN Load Balancing: Example, page 14-17 • Configuring SNMP Traps for REP: Example, page 14-17 • Monitoring the REP Configuration: Example, page 14-17 • Sample MWR 2941 Topology: Example, page 14-18 Configuring the REP Administrative VLAN: E
Chapter 14 Configuring Resilient Ethernet Protocol Configuration Examples for REP 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 5 Setting the Preemption for VLAN Load Balancing: Example The following is an example of setting the preemption for VLAN load balancing on a REP segment.
Chapter 14 Configuring Resilient Ethernet Protocol Configuration Examples for REP 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 Sample MWR 2941 Topology: Example The following configuration example shows two Cisco MWR 2941 routers and two Cisco 7600 series routers using a REP ring. Note This section provides partial configurations intended to demonstrate a specific feature.
Chapter 14 Configuring Resilient Ethernet Protocol Configuration Examples for REP rep segment 1 ! interface GigabitEthernet0/1 switchport trunk allowed vlan 1,2 switchport mode trunk rep segment 1 ! interface Vlan1 ip address 172.18.44.239 255.255.255.0 no ptp enable ! interface Vlan2 ip address 1.1.1.2 255.255.255.
Chapter 14 Configuring Resilient Ethernet Protocol Configuration Examples for REP 7600_2 interface Port-channel69 switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 1,2 switchport mode trunk ! interface GigabitEthernet5/2 switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 1,2 switchport mode trunk rep segment 1 edge ! interface GigabitEthernet7/25 switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 1,2 switchport mode trunk c
CH A P T E R 15 Configuring Ethernet OAM, CFM, and E-LMI 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 MWR 2941 router supports IEEE 802.1ag Connectivity Fault Management (CFM), Ethernet Local Management Interface (E-LMI), and IEEE 802.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Ethernet CFM • Understanding E-LMI, page 15-46 • Configuring E-LMI, page 15-46 • Displaying E-LMI Information, page 15-49 • Enabling Ethernet OAM, page 15-49 • Understanding Microwave 1+1 Hot Standby Protocol, page 15-50 • Configuring Microwave 1+1 Hot Standby Protocol, page 15-52 • Configuration Examples, page 15-55 Understanding Ethernet CFM Ethernet CFM is an end-to-end per-service-instance (per VLAN) Ethernet layer OAM pr
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Ethernet CFM Figure 15-1 CFM Maintenance Domains Service Provider Domain Level 6 Operator Domains Operator 1 CE 1 PE 1 Operator 2 PE 3 PE 4 PE 2 MEP MIP MIP CE 2 MEP Level 6 Level 6 MEP MIP MIP MEP Level 4 MIP MEP 157281 MIP Level 3 Figure 15-2 Allowed Domain Relationships Scenario A: Touching Domains OK Scenario B: Nested Domains OK Scenario C: Intersecting Domains Not Allowed 157282 MEP Maintenance Associatio
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Ethernet CFM Note CFM draft 1 referred to inward and outward-facing MEPs. CFM draft 8.1 refers to up and down MEPs, respectively. This document uses the CFM 8.1 terminology for direction. CFM draft 1 supported only up MEPs on a per-port or per-VLAN basis. CFM 802.1ag supports up and down per-VLAN MEPs, as well as port MEPs, which are untagged down MEPs that are not associated with a VLAN.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Ethernet CFM CFM Messages CFM uses standard Ethernet frames distinguished by EtherType or (for multicast messages) by MAC address. All CFM messages are confined to a maintenance domain and to a service-provider VLAN (S-VLAN).
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Ethernet CFM Configuration Error List CFM configuration errors in CFM 802.1ag can be misconfigurations or extra configuration commands detected during MEP configuration. They can be caused by overlapping maintenance associations.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM You can manually configure individual Ethernet ping or jitter operations. You can also configure an IP SLAs automatic Ethernet operation that queries the CFM database for all MEPs in a given maintenance domain and VLAN. The operation then automatically creates individual Ethernet ping or jitter operations based on the discovered MEPs.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM – Trunk ports configured as MEPs must belong to allowed VLANs – Access ports configured as MEPs must belong to the native VLAN. • CFM is not supported on 802.1Q tunnel interfaces. • You cannot configure CFM on an EoMPLS port. • A REP port or FlexLink port can also be a service (VLAN) MEP or MIP, but it cannot be a port MEP. • CFM is supported on ports running STP.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Step 7 Step 8 Command Purpose id {mac-address domain_number | dns name | null} (Optional) Assign a maintenance domain identifier. service {ma-name | ma-number | vpn-id vpn} {vlan vlan-id [direction down] | port} • mac-address domain_number—Enter the MAC address and a domain number. The number can be from 0 to 65535. • dns name—Enter a DNS name string. The name can be a maximum of 43 characters.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Step 14 Command Purpose mip auto-create [lower-mep-only | none] (Optional) Configure auto creation of MIPs for the service. • lower-mep-only—Create a MIP only if there is a MEP for the service in another domain at the next lower active level. • none —No MIP auto-create. Step 15 exit Return to ethernet-cfm configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Command Purpose Step 26 show ethernet cfm errors [configuration] (Optional) Display the configuration error list. Step 27 copy running-config startup-config (Optional) Save your entries in the configuration file. Use the no versions of the commands to remove the configuration or return to the default configurations.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Step 7 Command Purpose ethernet cfm mep crosscheck {enable | disable} domain domain-name {vlan {vlan-id | any} | port} Enable or disable CFM crosscheck for one or more VLANs or a port MEP in the domain. • domain domain-name—Specify the name of the created domain.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Command Step 3 Purpose service {ma-name | ma-num | vlan-id vlan-id | vpn-id Define a customer service maintenance association name vpn-id} [port | vlan vlan-id [direction down]] or number or a VPN ID to be associated with the domain, and a VLAN ID or peer MEP, and enter ethernet-cfm-service configuration mode. • ma-name—a string of no more than 100 characters that identifies the MAID. • ma-number—a value from 0 to 65535.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM 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.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Step 12 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 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Configuring Fault Alarms Beginning in privileged EXEC mode, follow these steps to configure Ethernet CFM fault alarms. Note that you can configure fault alarms in either global configuration mode or Ethernet CFM interface MEP mode. In case of conflict, the interface MEP mode configuration takes precedence. Command Purpose Step 1 configure terminal Enter global configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Command Purpose Step 8 ethernet cfm alarm notification {all | error-xcon | (Optional) Enable Ethernet CFM fault alarm notification mac-remote-error-xcon | none | remote-error-xcon for the specified defects on the interface. | xcon} Note The Ethernet CFM interface MEP alarm configuration takes precedence over the global configuration.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Manually Configuring an IP SLAs CFM Probe or Jitter Operation Beginning in privileged EXEC mode, follow these steps to manually configure an IP SLAs Ethernet echo (ping) or jitter operation: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 ip sla operation-number Create an IP SLAs operation, and enter IP SLAs configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Command Purpose Step 12 exit Return to global configuration mode. Step 13 ip sla schedule operation-number [ageout seconds] [life {forever | seconds}] [recurring] [start-time {hh:mm {:ss} [month day | day month] | pending | now | after hh:mm:ss}] Schedule the time parameters for the IP SLAs operation. • operation-number—Enter the IP SLAs operation number.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Ethernet CFM Step 3 Command Purpose type echo domain domain-name vlan vlan-id [exclude-mpids mp-ids] Configure the automatic Ethernet operation to create echo (ping) or jitter operation and enter IP SLAs Ethernet echo configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding TWAMP Step 11 Command Purpose ip sla schedule operation-number [ageout seconds] [life {forever | seconds}] [recurring] [start-time {hh:mm {:ss} [month day | day month] | pending | now | after hh:mm:ss}] Schedule the time parameters for the IP SLAs operation. • operation-number—Enter the IP SLAs operation number.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring TWAMP Figure 15-3 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 15-4 Although each entity is separate, the protocol allows for logical merging of the roles on a single device.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring TWAMP Configuring the TWAMP Server The TWAMP server and reflector functionality are configured on the same device. Note The switch does not support the TWAMP sender and client roles. Beginning in privileged EXEC mode, follow these steps to configure the TWAMP server: Command Purpose Step 1 configure terminal Enter global configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding CFM ITU-T Y.1731 Fault Management Command Purpose Step 3 timeout seconds (Optional) Set the maximum time, in seconds, the session can be inactive before the session ends. The range is 1–604800 seconds. The default is 900 seconds. Step 4 end Return to privileged EXEC mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding CFM ITU-T Y.1731 Fault Management • Defect conditions: – Loss of continuity (LOC): the MEP stopped receiving CCM frames from a peer MEP – Mismerge: the MEP received a CCM frame with a correct maintenance level (matching the MEP level) but an incorrect maintenance ID. – Unexpected MEP: the MEP received a CCM frame with the correct maintenance level (matching the MEP’s level) and correct maintenance ID, but an unexpected MEP ID.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding CFM ITU-T Y.1731 Fault Management Ethernet Remote Defect Indication When Ethernet OAM continuity check (ETH-CC) transmission is enabled, the Ethernet Remote Defect Indication (ETH-RDI) function uses a bit in the CFM CC message to communicate defect conditions to the MEP peers. For ETH-RDI functionality, you must configure the MEP MEG level, the ETH-CC transmission period, and the ETH-CC frame priority.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Y.1731 Fault Management When a MEP receives a valid LBM frame, it generates an LB reply frame and sends it to the requested MEP after a random delay in the range of 0 to 1 second. The validity of the frame is determined on its having the correct MEG level. When a MEP sends a multicast LBM frame and receives an LB reply frame within 5 seconds, the LB reply frame is valid. Configuring Y.1731 Fault Management To configure Y.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Y.1731 Fault Management Step 7 Command Purpose service {ma-name | ma-number | vpn-id vpn} {vlan vlan-id [direction down] | port} Define a customer service maintenance association (MA) 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.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Managing and Displaying Ethernet CFM Information This is an example of the output from the show ethernet cfm smep command when Ethernet AIS has been enabled: Router# show ethernet cfm smep SMEP Settings: -------------Interface: GigabitEthernet1/0/3 LCK-Status: Enabled LCK Period: 60000 (ms) Level to transmit LCK: Default AIS-Status: Enabled AIS Period: 60000 (ms) Level to transmit AIS: Default Defect Condition: AIS Using Multicast Ethernet Loopback You
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Managing and Displaying Ethernet CFM Information Table 15-2 Displaying CFM Information (continued) Command Purpose show ethernet cfm maintenance-points remote Displays information about a remote maintenance point domains or levels or [crosscheck | detail | domain | static] details in the CFM database. show ethernet cfm mpdb Displays information about entries in the MIP continuity-check database.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding the Ethernet OAM Protocol MIP Settings: ------------Local MIPs: * = MIP Manually Configured -----------------------------------------------------------------------------Level Port MacAddress SrvcInst Type Id -----------------------------------------------------------------------------*5 Gi0/3 0021.d7ef.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding the Ethernet OAM Protocol – The control block provides the interface between the OAM client and other OAM sublayer internal blocks. – The multiplexer manages frames from the MAC client, the control block, and the parser and passes OAM PDUs from the control block and loopback frames from the parser to the subordinate layer.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding the Ethernet OAM Protocol • Error Frame (error frames per second)—The number of frame errors detected during a specified period exceeded a threshold. • Error Frame Period (error frames per n frames)—The number of frame errors within the last n frames has exceeded a threshold.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM OAM Messages Ethernet OAM messages or OAM PDUs are standard length, untagged Ethernet frames within the normal frame length bounds of 64 to 1518 bytes. The maximum OAM PDU frame size exchanged between two peers is negotiated during the discovery phase. OAM PDUs always have the destination address of slow protocols (0180.c200.0002) and an Ethertype of 8809.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Ethernet OAM Configuration Guidelines Follow these guidelines when configuring Ethernet OAM: • The router does not support monitoring of egress frames sent with cyclic redundancy code (CDC) errors. The ethernet oam link-monitor transmit crc interface-configuration or template-configuration commands are visible but are not supported on the router. The commands are accepted, but are not applied to an interface.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Enabling Ethernet OAM Remote Loopback You must 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.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Step 3 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 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM 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 Repeat this step to configure both high and low thresholds.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Step 9 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.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Configuring Ethernet OAM Remote Failure Indications You can configure an error-disable action to occur on an interface if one of the high thresholds is exceeded, if the remote link goes down, if the remote device is rebooted, or if the remote device disables Ethernet OAM on the interface.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Beginning in privileged EXEC mode, follow these steps to configure an Ethernet OAM template and to associate it with an interface: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 template template-name Create a template, and enter template configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Setting Up and Configuring Ethernet OAM Command Step 5 Step 6 Step 7 Purpose ethernet oam link-monitor frame {threshold {high (Optional) Configure high and low thresholds for error {high-frames | none} | low {low-frames}} | window frames that trigger an error-frame link event. milliseconds} • Enter threshold high high-frames to set a high threshold in number of frames. The range is 1 to 65535. You must enter a high threshold.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Displaying Ethernet OAM Protocol Information Command Purpose Step 8 ethernet oam link-monitor high threshold action error-disable-interface (Optional) Configure the router to put an interface in an error disabled state when a high threshold for an error is exceeded. Step 9 exit Return to global configuration mode. Step 10 interface interface-id Define an Ethernet OAM interface, and enter interface configuration mode.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Enabling Ethernet Loopback Per-port facility loopback puts the port into a loopback state where the link is up, but the line protocol is down for regular traffic. The switch loops back all received traffic. When you configure per-port, per-VLAN loopback by entering the vlan vlan-list keywords, the other VLANs on the port continue to switch traffic normally, allowing nondisruptive loopback testing.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Enabling Ethernet Loopback • Port loopback shares hardware resources with the VLAN mapping feature. If not enough TCAM resources are available because of VLAN-mapping configuration, when you attempt to configure loopback, you receive an error message, and the configuration is not allowed.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding E-LMI To disable Ethernet terminal configuration, enter the no ethernet loopback interface configuration command. For more information about Ethernet loopback commands, see the Cisco MWR 2941 Mobile Wireless Edge Router IOS Command Reference, Release 15.1(1)MR. Understanding E-LMI Ethernet Local Management Interface (E-LMI) is a protocol between the customer-edge (CE) device and the provider-edge (PE) device.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring E-LMI • Customer-Edge Device Configuration, page 15-48 Default E-LMI Configuration Ethernet LMI is globally disabled by default. When enabled, the router is in provider-edge (PE) mode by default. When you globally enable E-LMI by entering the ethernet lmi global global configuration command, it is automatically enabled on all interfaces. You can also enable or disable E-LMI per interface to override the global configuration.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring E-LMI Step 6 Command Purpose ethernet lmi {n391 value | n393 value | t391 value| t392 value} Configure E-LMI parameters for the UNI. The keywords have these meanings: • n391 value—Set the event counter on the customer equipment. The counter polls the status of the UNI and all Ethernet virtual connections (EVCs). The range is from 1 to 65000; the default is 360. • n393 value—Set the event counter for the metro Ethernet network.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Displaying E-LMI Information For E-LMI to work, any VLANs used on the PE device must also be created on the CE device. Create a VLAN by entering the vlan vlan-id global configuration command on the CE device, where the vlan-ids match those on the PE device and configure these VLANs as allowed VLANs by entering the switchport trunk allowed vlan vlan-ids interface configuration command.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Microwave 1+1 Hot Standby Protocol Command Step 3 Purpose ethernet oam [max-rate oampdus | min-rate Enable Ethernet OAM on the interface seconds | mode {active | passive} | timeout seconds] • (Optional) Enter max-rate oampdus to set the maximum rate (per second) to send OAM PDUs. The range is 1 to 10 PDUs per second; the default is 10. • (Optional) Enter min-rate seconds to set the minimum rate in seconds.The range is 1 to 10 seconds.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Understanding Microwave 1+1 Hot Standby Protocol Figure 15-6 shows a sample physical topology for HSBY using two ODUs (active and standby) and one IDU. Figure 15-6 HSBY Link Protection Physical Topology ODU 1 (Active) ODU 2 (Standby) 208861 IDU In this topology, the IDU is connected to an active and a standby ODU. While only the active ODU handles data traffic, both ODUs process CFM and management traffic at all times.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Microwave 1+1 Hot Standby Protocol • CFM traffic between the IDU and the ODU 2 • CFM traffic between ODU 1 and ODU 2. This traffic passes through IDU. • Data traffic between the WAN and ODU 1. This traffic passes through the IDU. Figure 15-7 provides a logical view of the maintenance associations used in this HSBY topology.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Microwave 1+1 Hot Standby Protocol ODU Configuration Values HSBY protocol specifies that some values on the ODU are configurable while others utilize fixed values. Table 15-6 summarizes the permitted values for an ODU using HSBY protocol.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuring Microwave 1+1 Hot Standby Protocol Command Purpose Step 4 link-protection group group-number pccm vlan vlan-id Specifies a link protection group for ODU 1. Step 5 interface gigabitethernet slot/port Enters configuration for the interface connected to ODU 2 Step 6 ethernet cfm mep domain domain-name mpid mpid Defines a CFM MEP domain for ODU 2.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuration Examples Command Purpose Step 24 show link-protection [detail [group group-number]] (Optional) Displays the status of configured link protection groups. Step 25 show link-protection statistics [interface interface-name slot/port] (Optional) Displays the counters for each link protection port.
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuration Examples Router(config-if-srv)# exit Customer-edge device 2 (CE2) configuration: Router# config t Router(config)# interface gigabitethernet1/0/1 Router(config-if)# switchport trunk allowed vlan 10 Router(config-if)# switchport mode trunk Router(config-if)# ethernet oam remote-loopback supported Router(config-if)# ethernet oam Router(config-if)# exit These are examples of the output showing provider-edge switch port status of the configur
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuration Examples ethernet cfm ieee ethernet cfm global ethernet cfm traceroute cache ethernet cfm traceroute cache size 112 ethernet cfm domain CISCO_7 service L7 vlan 700 continuity-check ! ethernet cfm domain CISCO_ENG service ce28 vlan 600 continuity-check ! ethernet cfm domain CISCO_5 service L5 vlan 1 continuity-check ! ethernet lmi global ! interface GigabitEthernet0/2 switchport access vlan 600 shutdown ethernet cfm mip vlan 600 ethernet cfm
Chapter 15 Configuring Ethernet OAM, CFM, and E-LMI Configuration Examples continuity-check interval 10ms ! interface GigabitEthernet0/3 ethernet cfm mep domain LPG1 mpid 1 vlan 10 link-protection group 12 ! interface GigabitEthernet0/4 ethernet cfm mep domain LPG2 mpid 1 vlan 11 link-protection group 12 ! Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 16 Configuring Clocking and Timing Clock synchronization is important for a variety of applications, including synchronization of radio cell towers. While legacy TDM protocols incorporate timing features, packet-switched networks such as Ethernet do not natively include these features. The Cisco MWR 2941 supports legacy TDM technologies while supporting a variety of technologies that distribute clocking information over packet-switched networks.
Chapter 16 Configuring Clocking and Timing Network Clocking Overview Precision Timing Protocol (PTP) The Cisco MWR 2941 supports the Precision Time Protocol (PTP) as defined by the IEEE 1588-2008 standard. PTP provides for accurate time synchronization on over packet-switched networks. Nodes within a PTP network can act in one of the following roles: • Grandmaster—A device on the network physically attached to the primary time source.
Chapter 16 Configuring Clocking and Timing Network Clocking Overview When configured as a multicast PTP router, the Cisco MWR 2941 selects the best path toward a Rendezvous Point (RP) using the active routing protocol, sends a Cisco Protocol Independent Multicast (PIM) join message to the RP, and forwards PTP multicast messages to the PTP client. The Cisco MWR 2941 also supports PIM forwarding. For instructions on how to configure PTP redundancy using multicast, see Configuring PTP Redundancy, page 16-10.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Configuring Clocking and Timing The Cisco MWR 2941 supports the following network clocking types: Note • Precision Time Protocol (PTP)—Clocking and clock recovery based on the IEEE 1588-2008 standard; allows the Cisco MWR 2941 router to receive clocking from another PTP-enabled device or provide clocking to a PTP-enabled device. To configure PTP clocking, see Configuring PTP Clocking.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Configuring Global PTP Settings Enter the following commands to configure the global PTP settings: 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 mode ordinary Specifies the PTP mode; you can configure ordinary or boundary clock mode.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Table 16-1 PTP Interface Commands Command Purpose ptp announce Sets interval and timeout values for PTP announcement packets. ptp boundary Sets the interface in boundary clock mode; you can specify the interface to use multicast or unicast negotiation.. ptp clock-destination Specifies the IP address of a clock destination. This command applies only when the router is in PTP master unicast mode.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Router(config-if)# Router(config-if)# Router(config-if)# Router(config-if)# Router(config-if)# • ptp ptp ptp ptp ptp announce interval 0 sync interval -6 delay-req interval -4 slave multicast enable PTP multicast slave mode (with hybrid clocking)—Sets the Cisco MWR 2941 to receive phase from a PTP master device in multicast mode while using clock frequency obtained from the synchronous Ethernet port.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing • PTP unicast slave mode—Sets the Cisco MWR 2941 to receive clocking from a single PTP master device. Router(config)# interface Vlan2 Router(config-if)# ip address 192.168.52.38 255.255.255.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Enabling PTP on Multiple VLANs You can enable PTP on up to three VLANs at a time. The following restrictions apply: • All PTP-enabled VLANs must use PTP master or PTP slave; you cannot configure PTP master and PTP slave VLANs at the same time. • All PTP-enabled VLANs must use multicast or unicast, but not both.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing • To configure output clocking using the 10Mhz timing port, use the ptp output command to specify 10Mhz, 2.048Mhz, or 1.544Mhz output. Use this command when the router is in PTP slave mode. Router(config)# ptp output 2.048M • To configure the router to send time of day messages using the 1PPS port, use the ptp 1pps command.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Command Purpose Step 4 Router(config)# interface vlan 100 Router(config-if)# description PTP client interface Router(config-if)# ip address 10.1.1.1 255.255.255.252 Enter these commands to configure a VLAN for the PTP client. Step 5 Router(config-if)# ip pim sparse-dense-mode Enables Protocol Independent Multicast (PIM) on the VLAN interface. You can specify the interface to use sparse, dense, or sparse-dense mode.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Command Purpose Step 12 Router(config)# interface gigabitethernet 0/1 Router(config-if)# description physical interface to PTP multicast source Router(config-if)# switchport trunk allowed vlan 1,2,402,1002-1005 Router(config-if)# switchport mode trunk Configures the second gigabit Ethernet interface connected to the multicast PTP clock source.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Configuring In-Band Master Mode Use the following steps to configure in-band master mode. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 The following example shows how to configure SAToP.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Configuring In-Band Slave Mode Use the following steps to configure in-band slave mode. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 The following example shows how to configure SAToP.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Command Purpose Step 9 Router(config)# network-clock-select 1 PACKET-TIMING Router(config)# network-clock-select hold-timeout 900 Configures the network clock: Step 10 exit Exits configuration mode. Example: Router(config)# exit Router# Configuring Out-of-Band Slave Mode Use the following steps to configure out-of-band slave mode.
Chapter 16 Configuring Clocking and Timing Configuring Clocking and Timing Command Purpose Step 8 Router(config)# network-clock-select 1 PACKET-TIMING Router(config)# network-clock-select hold-timeout 900 Configures the network clock. Step 9 exit Exits configuration mode. Example: Router(config)# exit Router# Configuring Synchronous Ethernet The following sections describe how to configure synchronous Ethernet timing on the Cisco MWR 2941.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations • show platform hardware rtm—Displays the current status of the TOP module For more information about these commands, see the Cisco MWR 2941 Mobile Wireless Edge Router IOS Command Reference, Release 15.0(1)MR. Clocking Sample Configurations The following sections show a sample configurations for PTP. For more information about how to configure PTP, see Chapter 16, “Configuring Clocking and Timing.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations ! ipran-mib snmp-access outOfBand archive log config hidekeys ! ! controller E1 0/0 clock source internal cem-group 0 unframed description TDM Shorthaul for SAToP PW ! controller E1 0/1 framing NO-CRC4 clock source internal cem-group 0 timeslots 1-31 description TDM Shorthaul for CESoPSN PW ! controller E1 0/2 clock source internal ! controller E1 0/3 clock source internal ! controller E1 0/4 clock source line ! controller E1 0/5 c
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations clock source internal ! controller BITS applique E1 ! ! pseudowire-class My_MPLS encapsulation mpls sequencing both ! ! interface Loopback0 ip address 10.1.1.22 255.255.255.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations encapsulation aal0 xconnect 10.10.10.36 5237 encapsulation mpls ! pvc 1/38 l2transport encapsulation aal0 xconnect 10.10.10.36 5238 encapsulation mpls ! pvc 1/39 l2transport encapsulation aal0 xconnect 10.10.10.36 5239 encapsulation mpls ! ! interface Vlan1 no ip address shutdown no ptp enable ! interface Vlan3 description 7600/2941 MPLS Backhaul VLAN ip address 192.22.2.2 255.255.255.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations ip forward-protocol nd ip route 0.0.0.0 0.0.0.0 172.18.75.1 ip route 10.1.1.201 255.255.255.255 10.100.11.1 ip route 10.1.1.202 255.255.255.255 10.100.12.1 ! ! ip http server ip pim rp-address 10.2.1.1 5 override ! access-list 5 permit 224.0.1.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations end ! interface GigabitEthernet0/0 switchport access vlan 10 ! interface GigabitEthernet0/1 switchport access vlan 5 ! interface Vlan5 ip address 5.5.5.2 255.255.255.0 ip router isis ip pim sparse-mode no ptp enable ! interface Vlan10 ip address 10.10.10.2 255.255.255.0 ip router isis ip pim sparse-mode no ptp enable ! router isis net 49.0001.1720.1600.3003.00 passive-interface Loopback0 ! ip pim rp-address 6.6.6.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations PTP Boundary Clock The following configurations show how to use PTP boundary clock: Note This section provides partial configurations intended to demonstrate a specific feature. Boundary Node ptp ptp ptp ptp mode boundary priority1 128 priority2 128 domain 1 interface Vlan1 ip address 192.168.1.2 255.255.255.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations Unicast Boundary Clock ptp ptp ptp ptp mode boundary priority1 128 priority2 128 domain 1 interface Vlan1 ip address 192.168.1.2 255.255.255.0 ptp announce interval 3 ptp announce timeout 2 ptp sync interval -4 ptp delay-req interval -4 ptp boundary unicast-negotiation ptp clock-source 192.168.1.1 ptp enable interface Vlan2 ip address 172.18.52.38 255.255.255.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations ptp enable MWR B ptp ptp ptp ptp mode ordinary priority1 128 priority2 128 domain 0 Vlan $vlan2 interface Vlan $vlan2 ip address 192.168.20.1 255.255.255.0 ptp announce interval 0 ptp announce timeout 10 ptp sync interval -6 ptp delay-req interval -4 ptp master unicast ptp clock-destination 192.168.20.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations PTP Hybrid Mode The following section shows a sample PTP configuration that uses hybrid mode. For more information about how to configure PTP hybrid mode, see “Hybrid Clocking” section on page 16-3. Note This section provides a partial configuration intended to demonstrate a specific feature. ptp ptp ptp ptp mode ordinary priority1 128 priority2 128 domain 1 interface Vlan1 ip address 192.168.1.2 255.255.255.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations PTP Input Timing The following sample configuration sets the router as a PTP master clock with input timing enabled using the 10Mhz timing port. Note This section only applies to the Cisco MWR 2941-DC-A router; the Cisco MWR-DC router does not have the timing ports used in this example. Note This section provides a partial configuration intended to demonstrate a specific feature.
Chapter 16 Configuring Clocking and Timing Clocking Sample Configurations interface GigabitEthernet 0/0 switchport access vlan 1588 interface vlan 1588 ip address 192.168.15.88 255.255.255.0 ip igmp join-group 224.0.1.129 ptp sync interval -6 ptp delay-req interval -4 ptp slave multicast ptp enable network-clock-select hold-timeout 1000 network-clock-select 1 PACKET-TIMING enable 10M Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 17 Configuring Synchronous Ethernet ESMC and SSM With Ethernet equipment gradually replacing Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) equipment in service-provider networks, frequency synchronization is required to provide high-quality clock synchronization over Ethernet ports. Synchronous Ethernet (SyncE) provides the required synchronization at the physical level.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM Restrictions for Synchronous Ethernet (SyncE): ESMC and SSM Restrictions for Synchronous Ethernet (SyncE): ESMC and SSM • To use the network-clock synchronization ssm option command, the following conditions are required: – No input source is in the configuration. – No network clock quality level is in the configuration. – No network clock source quality source is set under any synchronous Ethernet interface.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM How to Configure Synchronous Ethernet (SyncE): ESMC and SSM slow protocol; the ITU-T OUI, a specific ITU-T subtype; an ESMC-specific header; a flag field; and a type, length, value (TLV) structure. The use of flags and TLVs improves the management of SyncE links and the associated timing change. How to Configure Synchronous Ethernet (SyncE): ESMC and SSM Perform this task to configure SyncE using ESMC and SSM.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM How to Configure Synchronous Ethernet (SyncE): ESMC and SSM Step 8 Command or Action Purpose exit Exits controller configuration mode and returns to configuration mode.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM How to Configure Synchronous Ethernet (SyncE): ESMC and SSM Step 17 Command or Action Purpose network-clock-select hold-timeout {timeout | infinite} (Optional) Specifies how long the router waits before reevaluating the network clock entry. Example: Router(config)# network-clock-select hold-timeout 2000 Step 18 esmc process Enables the ESMC process.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM Configuration Examples for Synchronous Ethernet (SyncE): ESMC and SSM Step 26 Command or Action Purpose network-clock wait-to-restore seconds (Optional) Configures wait-to-restore timer for the SyncE interface. Example: Router(config-if)# network-clock wait-to-restore 70 Step 27 Exits interface configuration mode and returns to privileged EXEC mode.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM Configuration Examples for Synchronous Ethernet (SyncE): ESMC and SSM QL Receive: QL-SSU-B ESMC Information rate : 1 packet/second ESMC Expiry: 5 second The following examples shows how to view the network clock synchronization details: Router# show network-clock synchronization detail Automatic selection process : Enable Equipment Clock : 2048 (EEC-Option1) Clock Mode : QL-Enable ESMC : Disabled SSM Option : 1 T0 : Internal Hold-off (global) : 300
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM Configuration Examples for Synchronous Ethernet (SyncE): ESMC and SSM QL Transmit Configured: Hold-off: 300 Wait-to-restore: 300 Lock Out: FALSE Signal Fail: FALSE Alarms: FALSE Slot Disabled: FALSE Dont Use: FALSE Configured Priority: 2 Force Switch: FALSE Manual Switch: FALSE Manual Switch In progress: FALSE Holdoff_cfg: FALSE Wtr_cfg: FALSE Reason for alarm flag: 0 Msw in progress: FALSE Intf_sig_nv: 0 Hold off Timer: Stopped Wait to restore Tim
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM Additional References Additional References Related Documents Related Topic Document Title SyncE configuration commands Cisco IOS Interface and Hardware Component Command Reference Standards Standard Title ITU-T G.8262 Timing characteristics of synchronous Ethernet equipment slave clock (EEC) ITU-T G.8264 Timing distribution through Packet Networks ITU-T G.
Chapter 17 Configuring Synchronous Ethernet ESMC and SSM Additional References Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 18 Configuring MLPPP Backhaul To configure an MLPPP backhaul, complete the following tasks: • Configuring the Card Type, page 18-1 • Configuring E1 Controllers, page 18-2 • Configuring T1 Controllers, page 18-4 • Configuring ATM IMA, page 18-6 • Configuring T1 and E1 Local Switching, page 18-7 • Configuring a Multilink Backhaul Interface, page 18-10 Configuring the Card Type Perform a basic card type configuration by enabling the router, enabling an interface, and specifying the c
Chapter 18 Step 3 Configuring MLPPP Backhaul 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 1 • slot—Slot number of the interface. • subslot—VWIC slot number. The example shows how to configure a T1/E HWIC in the first HWIC slot as an E1 card. When the command is used for the first time, the configuration takes effect immediately.
Chapter 18 Step 3 Configuring MLPPP Backhaul Command Purpose controller e1 slot/port Specifies the controller that you want to configure. Controller E1 0/0 maps to the T1/E1 HWIC card in HWIC slot 0. Example: The example shows how to specify the E1 controller as the first port of the T1/E1 HWIC card in slot 0. Router(config)# controller e1 0/0 Router(config-controller)# Step 4 framing {crc4 | no-crc4} Specifies the framing type.
Chapter 18 Step 8 Configuring MLPPP Backhaul Command Purpose Router(config-controller)# channel-group channel-no timeslots timeslot-list speed {64} Specifies the channel-group and time slots to be mapped. After you configure a channel-group, the serial interface is automatically created. The syntax is: Example: Router(config-controller)# channel-group 0 timeslots 1-31 speed 64 • channel-no—ID number to identify the channel group. The valid range is from 0–30.
Chapter 18 Configuring MLPPP Backhaul Note In the following procedure, press the Return key after each step unless otherwise noted. At any time, you can exit the privileged level and return to the user level by entering disable at the Router# prompt. To configure the T1 interfaces, follow these steps in the global configuration mode: Step 1 Command Purpose enable Enables privileged EXEC mode. Enter your password if prompted.
Chapter 18 Configuring MLPPP Backhaul Command Purpose Step 11 Router(config-if)# encapsulation ppp Enters the following command to configure PPP encapsulation. Step 12 Router(config-if)# keepalive [period [retries]] Enables keepalive packets on the interface and specify the number of times that keepalive packets will be sent without a response the interface is brought down: Step 13 exit Exits configuration mode.
Chapter 18 Step 9 Configuring MLPPP Backhaul Command Purpose interface ATMslot/IMA Specify the slot location and port of IMA interface group. Example: Router(config-if)# interface atm0/ima0 • slot—The slot location of the ATM IMA port adapter. • group-number—The group number of the IMA group. The example specifies the slot number as 0 and the group number as 0. Note To explicitly configure the IMA group ID for the IMA interface, you may use the optional ima group-id command.
Chapter 18 Configuring MLPPP Backhaul Follow these steps to configure T1 and E1 local switching Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 controller {t1 | e1} slot/port Enter T1 or E1 controller configuration mode. Step 3 tdm-group tdm-group-no timeslot timeslot-list Specify the TDM group and timeslots for which you want to enable local switching.
Chapter 18 Configuring MLPPP Backhaul Non-Channelized Local Switching controller E1 0/0 tdm-group 0 timeslots 1-31 controller E1 0/1 tdm-group 0 timeslots 1-31 connect st1 E1 0/0 0 E1 0/1 0 Channelized Local Switching controller E1 0/0 tdm-group 0 timeslots 1-10 tdm-group 1 timeslots 11-20 controller E1 0/1 tdm-group 0 timeslots 1-10 tdm-group 1 timeslots 11-20 connect st1 E1 0/0 0 E1 0/1 0 connect st2 E1 0/0 1 E1 0/1 1 Channelized Local Switching on Multiple Channels controller E1 0/0 tdm-group 0 times
Chapter 18 Configuring MLPPP Backhaul Configuring a Multilink Backhaul Interface A multilink interface is a virtual interface that represents a multilink PPP bundle. The multilink interface coordinates the configuration of the bundled link, and presents a single object for the aggregate links. However, the individual PPP links that are aggregated must also be configured.
Chapter 18 Step 4 Configuring MLPPP Backhaul Command Purpose Router(config-if)# ip address address [subnet mask] Assigns an IP address to the multilink interface. Example: Step 5 • address— IP address. • subnet mask—Network mask of IP address. Router(config-if)# ip address 10.10.10.2 255.255.255.0 The example configures an IP address and subnet mask. exit Exits configuration mode.
Chapter 18 Step 4 Configuring MLPPP Backhaul Command Purpose Router(config-if)# ppp pfc remote {apply | reject | ignore} Specifies how the router manages the PFC option in configuration requests received from a remote peer. The syntax is as follows: • apply—Specifies that PFC options are accepted and ACFC may be performed on frames sent to the remote peer. • reject—Specifies that PFC options are explicitly ignored.
Chapter 18 Step 4 Configuring MLPPP Backhaul 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: • apply—ACFC options are accepted and ACFC may be performed on frames sent to the remote peer. • reject—ACFC options are explicitly ignored. • ignore—ACFC options are accepted, but ACFC is not performed on frames sent to the remote peer.
Chapter 18 Step 5 Command Purpose Router(config-if)# keepalive [period [retries]] Enables keepalive packets on the interface and specifies the number of times the keepalive packets are sent without a response before the router disables the interface. The syntax is as follows: Example: • period—(Optional) Integer value in seconds greater than 0. The default is 10.
Chapter 18 Configuring MLPPP Backhaul Enabling Real-Time Transport Protocol (RTP) Header Compression On a Multilink Inteface To enable RTP header compression, follow these steps while in the interface configuration mode: Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode.
Chapter 18 Configuring MLPPP Backhaul dIPHC Usage Notes • The Cisco MWR 2941 supports dIPHC for UDP traffic only. • The Cisco MWR 2941 supports up to 300 IPHC sessions over 3 multilinks . • The Cisco MWR 2941 supports only the IEFT format of IPHC. • The Cisco MWR 2941 supports dIPHC only for UDP traffic. • After enabling dIPHC on an interface, ensure that you “flap” the interface by using the shutdown and no shutdown commands in interface configuration mode for the configuration to take effect.
Chapter 18 Step 11 Configuring MLPPP Backhaul Command Purpose exit Exits interface configuration mode. Example: Router(config-if)# exit Router(config)# Step 12 exit Exits global configuration mode. Example: Router(config)# exit Router# Step 13 show ip rtp header-compression multilink Displays Real-Time Transport Protocol (RTP) header compression statistics on the multilink interface.
Chapter 18 Configuring MLPPP Backhaul Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 19 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.0S. Note The Cisco MWR 2941 does not necessarily support all of the commands listed in the Release 15.0S documentation. Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
Chapter 19 Configuring Multiprotocol Label Switching Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 20 Configuring IPv6 The Cisco MWR 2941 routr provides support for a subset of the IPv6 features supported in Cisco IOS Release 15.1(1)S. The following sections describe the IPv6 features supported on the Cisco MWR 2941. • Supported IPv6 Features, page 20-1 • Supported IPv6 Commands, page 20-2 • Sample IPv6 Configurations, page 20-4 Supported IPv6 Features Table 1 summarizes the supported IPv6 features in Release 15.0(1)MR.
Chapter 20 Configuring IPv6 Supported IPv6 Commands IPv6 Limitations For information about IPv6 limitations Release Notes for Cisco MWR 2941-DC Mobile Wireless Edge Router, Release 15.1(1)MR . Supported IPv6 Commands Table 2 summarizes the supported commands in Release 15.0(1)MR. For more information about these commands, refer to the Cisco IOS IPv6 Command Reference.
Chapter 20 Configuring IPv6 Supported IPv6 Commands Table 2 Supported IPv6 Commands ipv6 address autoconfig neighbor translate-update show ipv6 ospf interface ipv6 address ipv6 unicast-routing show ipv6 ospf neighbor ipv6 address eui-64 neighbor update-source ipv6 address link-local network (BGP and multiprotocol BGP) show ipv6 ospf request-list ipv6 cef network (IPv6) show ipv6 ospf retransmission-list ipv6 cef accounting passive-interface (IPv6) show ipv6 ospf statistics ipv6 dhcp dat
Chapter 20 Configuring IPv6 Sample IPv6 Configurations Table 2 Supported IPv6 Commands ipv6 ospf dead-interval show cef timers throttle spf ipv6 ospf demand-circuit show cef interface traceroute ipv6 ospf encryption show cef table vrf definition ipv6 ospf flood-reduction show clns neighbors vrf forwarding Sample IPv6 Configurations The following sections provide sample configurations for IPv6.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations • Example: Associating an IPv6 Static Route with a BFDv6 Neighbor • Example: Displaying OSPF Interface Information about BFD • Example: IPv6 VPN Configuration Using IPv4 Next Hop Example: Specifying an IPv6 Static BFDv6 Neighbor The following example specifies a fully configured IPv6 static BFDv6 neighbor. The interface is Ethernet 0/0 and the neighbor address is 2001::1.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations neighbor 192.168.2.10 send-community extended exit-address-family By default, the next hop advertised will be the IPv6 VPN address: [0:0]::FFFF:192.168.2.10 Note that it is a 192-bit address in the format of [RD]::FFFF:IPv4-address. When the BGP IPv6 VPN peers share a common subnet, the MP_REACH_NLRI attribute contains a link-local address next hop in addition to the global address next hop.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations ipv6 address autoconfig For more information about how to configure DHCP, refer to Implementing DHCP for IPv6. IS-IS The following example shows how to configure IS-IS routing for IPv6 traffic. interface Vlan306 mtu 4470 ip address 10.36.1.1 255.255.255.0 no ptp enable ipv6 address 2001:DB8:1::1/64 ipv6 enable ipv6 router isis isis-600-1 mpls ip bfd interval 150 min_rx 50 multiplier 3 ! router isis isis-600-1 net net 2001:DB8.0000.0000.0003.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations neighbor 10.0.4.4 send-label exit-address-family ! For more information about how to configure IPv6 over MPLS, refer to Implementing IPv6 over MPLS. IPv6 VPN over MPLS The following example shows how to configure an IPv6 VPN over MPLS (6VPE).
Chapter 20 Configuring IPv6 Sample IPv6 Configurations neighbor 10.10.4.4 send-community both exit-address-family ! address-family ipv6 vrf B redistribute connected redistribute static exit-address-family ! address-family ipv6 vrf C neighbor 2001:DB8:100:1:: remote-as 104 neighbor 2001:DB8:100:1:: activate exit-address-family For more information about how to configure IPv6 VPN over MPLS, see Implementing IPv6 VPN over MPLS.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations match protocol ipv6 match dscp af33, af13 class-map match-all ipv6_hsps match protocol ipv6 match dscp af12 policy-map input-policy class ipv6_llq set cos 5 set qos-group 5 class ipv6_prem set qos-group 4 set cos 4 class ipv6_hsps set cos 3 set qos-group 3 interface GigabitEthernet0/4 switchport access vlan 1000 switchport mode access service-policy input input-policy Applying Ingress QoS to IPv4 Traffic The following example classifies IPv4 traffic
Chapter 20 Configuring IPv6 Sample IPv6 Configurations Applying Egress QoS to IPv4 and IPv6 Traffic The following example performs the following QoS functions: • Matches all IPv4 and IPv6 traffic based on QoS group • Applies egress queuing based on QoS group • Applies egress shaping to all traffic class-map match-all match qos-group 0 class-map match-all match qos-group 1 class-map match-all match qos-group 2 class-map match-all match qos-group 3 q0 q1 q2 q3 policy-map child_policy_egress class q3
Chapter 20 Configuring IPv6 Sample IPv6 Configurations Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
Chapter 20 Configuring IPv6 Sample IPv6 Configurations Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 21 Configuring Routing Protocols In addition to static routing, the Cisco MWR 2941 supports the following routing protocols: Note • OSPF—An Interior Gateway Protocol (IGP) designed expressly 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.
Chapter 21 Configuring Routing Protocols Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 22 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 22 Configuring Bidirectional Forwarding Detection Configuring BFD Configuring BFD for OSPF This section describes how to configure BFD on the Cisco MWR 2941. Configuring BFD for OSPF on One or More Interfaces Follow these steps to configure BFD for Open Shortest Path First (OSPF) on a single interface. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Configuring BFD for OSPF on All Interfaces Follow these steps to configure BFD for OSPF on all interfaces. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode. Example: Router# configure terminal Step 3 Router(config)# router ospf 100 Creates a configuration for an OSPF process.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Step 4 Command Purpose neighbor ip-address fall-over bfd Enables support for BFD failover. Example: Router(config-router)# neighbor ip-address fall-over bfd Step 5 end Returns the router to privileged EXEC mode.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Step 3 Command Purpose ipv6 cef Enables Cisco Express Forwarding for IPv6. Example: Router(config)# ipv6 cef Step 4 Exits configuration mode and enters privileged EXEC mode. end Example: Router(config-router)# end Router# Configuring IPv6 BFD on an SVI Interface To configure IPv6 BFD on an SVI interface, complete the following steps: Step 1 Command Purpose configure terminal Enters global configuration mode.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Step 7 Command Purpose interface interface Specifies an interface to configure. Example: Router(config)# interface vlan10 Step 8 ipv6 enable Enables IPv6 support on the interface. Example: Router(config-if)# ipv6 enable Step 9 ipv6 address ipv6-address / prefix-length Configures an IPv6 address on the interface.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Configuring IPv6 BGP on the Cisco MWR 2941 To configure IPv6 BGP on the Cisco MWR 2941, complete the following steps: Step 16 Command Purpose configure terminal Enters global configuration mode. Example: Router# configure terminal Step 17 router bgp as-tag Enters router configuration mode for the specified routing process.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Step 24 Command Purpose redistribute connected Redistributes routes from one routing domain into another routing domain. The connected keyword refers to routes that are established automatically by virtue of having enabled IP on an interface. Example: Router(config-router-af)# redistribute connected Step 25 neighbor ipv6-address activate Enables the exchange of information with a Border Gateway Protocol (BGP) neighbor.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Configuring BFD for IS-IS on a Single Interface Follow these steps to configure BFD for IS-IS on a single interface. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted. Example: Router> enable Step 2 configure terminal Enters global configuration mode.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuring BFD Command Purpose Step 6 Router(config-router)# exit Router(config)# Exits the interface. Step 7 Router(config)# interface vlan1 Router(config-if) ip router isis [tag] Router(config-if)# isis bfd 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: Step 8 exit a. Use the interface command to enter interface configuration mode.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD Command Purpose Step 6 Router(config-if)# ip route static bfd Serial 2/0 10.201.201.2 Specifies a static route BFD neighbor. Step 7 exit Exits configuration mode. Example: Router(config)# exit Router# 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.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD archive log config hidekeys ! controller T1 0/0 mode atm clock source line ! controller T1 0/1 clock source line cem-group 0 timeslots 1-31 ! controller T1 0/2 clock source internal ! controller T1 0/3 clock source internal ! controller T1 0/4 clock source internal ! controller T1 0/5 clock source internal ! controller T1 0/6 clock source internal ! controller T1 0/7 clock source internal ! controller T1 0/8 clock so
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD ! interface GigabitEthernet0/1 ! interface GigabitEthernet0/2 switchport access vlan 10 ! interface GigabitEthernet0/3 ! interface GigabitEthernet0/4 ! interface GigabitEthernet0/5 ! interface ATM0/0 no ip address scrambling-payload atm pvp 1 l2transport xconnect 10.10.10.2 10001 encapsulation mpls no atm ilmi-keepalive pvc 0/20 l2transport vc-hold-queue 80 encapsulation aal0 xconnect 10.10.10.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD mpls ip ! router ospf 100 router-id 88.88.88.150 log-adjacency-changes timers throttle spf 50 50 1000 timers throttle lsa all 0 25 10000 timers lsa arrival 0 timers pacing flood 20 timers pacing retransmission 30 redistribute static subnets network 88.88.88.150 0.0.0.0 area 0 network 172.22.41.0 0.0.0.255 area 0 network 172.22.42.0 0.0.0.255 area 0 bfd all-interfaces ! ip default-gateway 192.168.52.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD ip source-route ! ! ip cef no ip domain lookup ip host tftp 64.102.116.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD clock source internal ! controller BITS applique E1 ! interface Loopback0 ip address 20.20.20.20 255.255.255.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD ! interface Vlan4 (connected to 7600) ip address 11.1.1.2 255.255.255.0 no ptp enable bfd interval 50 min_rx 50 multiplier 3 ! interface Vlan10 ip address 192.168.40.61 255.255.255.128 no ptp enable mpls ip ! interface Vlan100 ip address 12.1.1.2 255.255.255.0 no ptp enable mpls bgp forwarding mpls ip bfd interval 50 min_rx 50 multiplier 3 ! interface Vlan200 ip address 12.1.2.2 255.255.255.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD ! card type t1 0 0 logging buffered 1000000 no logging console ! no aaa new-model ip source-route ! ! ip cef no ip domain lookup ip host tftp 64.102.116.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD clock source internal ! controller T1 0/14 clock source internal ! controller T1 0/15 clock source internal ! controller BITS applique E1 ! interface Loopback0 ip address 20.20.20.20 255.255.255.
Chapter 22 Configuring Bidirectional Forwarding Detection Configuration Examples for BFD interface ATM0/1 no ip address scrambling-payload no atm ilmi-keepalive pvc 0/100 l2transport ! ! interface Vlan4 ip address 11.1.1.2 255.255.255.0 ip router isis test_ip_isis no ptp enable isis bfd ! interface Vlan10 ip address 192.168.40.61 255.255.255.128 no ptp enable mpls ip ! interface Vlan100 ip address 12.1.1.2 255.255.255.
CH A P T E R 23 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.
Chapter 23 Configuring Pseudowire Understanding Pseudowire • Structure-Agnostic TDM over Packet, page 23-2 • Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network, page 23-2 • Transportation of Service Using ATM over MPLS, page 23-2 • Transportation of Service Using Ethernet over MPLS, page 23-3 Structure-Agnostic TDM over Packet SAToP encapsulates TDM bit-streams (T1, E1, T3, E3) as PWs over PSNs.
Chapter 23 Configuring Pseudowire Configuring Pseudowire The Cisco MWR 2941 also supports cell packing and PVC mapping for ATM over MPLS pseudowires. Note Release 15.1(1)MR does not support ATM over MPLS N-to-1 Cell Mode or 1-to-1 Cell Mode. For more information about how to configure ATM over MPLS, see Configuring Transportation of Service Using ATM over MPLS. For sample ATM over MPLS configurations, see Configuration Examples for Pseudowire.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Using Pseudowire Classes A pseudowire class allows you to create a single configuration template for multiple pseudowire connections. You can apply pseudowire classes to all pseudowire types. Follow these steps to configure a pseudowire class: 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 23 Configuring Pseudowire Configuring Pseudowire Using CEM Classes A CEM class allows you to create a single configuration template for multiple CEM pseudowires. Follow these steps to configure a CEM class: Note Step 1 You cannot apply a CEM class to other pseudowire types such as ATM over MPLS. 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 Configuring Pseudowire Configuring Pseudowire Configuring a Backup Peer A backup peer provides a redundant pseudowire (PW) connection in the case that the primary PW loses connection; if the primary PW goes down, the Cisco MWR 2941 diverts traffic to the backup PW. Follow these steps to configure a backup peer. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Configuring Structure-Agnostic TDM over Packet (SAToP) Follow these steps to configure SAToP on the Cisco MWR 2941: 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)# controller [T1|E1] 0/4 Router(config-controller)# Configures the T1 or E1 interface.
Chapter 23 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 Router(config)# controller [e1|t1] 0/0 Router(config-controller)# Enters configuration mode for the E1 or T1 controller.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Configuring a CESoPSN Pseudowire with UDP Encapsulation Follow these steps to configure a CESoPSN pseudowire with UDP encapsulation: 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)# pseudowire-class udpClass Creates a new pseudowire class.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Command Purpose Step 15 Router(config-if-cem)# exit Router(config)# Exits the CEM interface. Step 16 exit Exits configuration mode. Example: Router(config)# exit Router# Configuring Transportation of Service Using ATM over MPLS ATM over MPLS pseudowires allow you to encapsulate and transport ATM traffic across an MPLS network. This service allows you to deliver ATM services over an existing MPLS network.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Step 6 Command Purpose Router(config-controller)# ima-group 0 scrambling-payload If you want to configure an ATM IMA backhaul, use the ima-group command to assign the interface to an IMA group. For a T1 connection, use the no-scrambling-payload to disable ATM-IMA cell payload scrambling; for an E1 connection, use the scrambling-payload parameter to enable ATM-IMA cell payload scrambling.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Step 3 Command Purpose Router(config-controller)# interface ATMslot/IMAgroup-number Specifies the slot location and port of IMA interface group. The syntax is as follows: Example: Router(config-controller)# interface atm0/ima0 Router(config-if)# • slot—The slot location of the ATM IMA port adapter. • group-number—The group number of the IMA group. The example specifies the slot number as 0 and the group number as 0.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Note When creating IP routes for a pseudowire configuration, build a route from the xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route 30.30.30.2 255.255.255.255 1.2.3.4. Configuring N-to-1 VCC Cell Transport Pseudowire An N-to-1 VCC cell transport pseudowire maps one or more ATM virtual channel connections (VCCs) to a single pseudowire. Follow these steps to configure an N-to-1 pseudowire.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Configuring N-to-1 VPC Cell Transport An N-to-1 VPC cell transport pseudowire maps one or more ATM virtual path connections (VPCs) to a single pseudowire. While the configuration is similar to one-to-one VPC cell mode, this transport method uses the N-to-1 VPC Pseudowire protocol and format defined in RFCs 4717 and 4446. Follow these steps to configure an N-to-1 VPC pseudowire. Note Step 1 Release 15.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Command Purpose Step 4 Router(config-if)# pvc 0/12 l2transport Router(cfg-if-atm-l2trans-pvc)# Configures a PVC and specify a VCI/VPI. Step 5 Router(cfg-if-atm-l2trans-pvc)# encapsulation aal5 Sets the PVC encapsulation type to AAL5. Note You must use AAL5 encapsulation for this transport type. Step 6 Router(cfg-if-atm-l2trans-pvc)# xconnect 25.25.25.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Optional Configurations You can apply the following optional configurations to a pseudowire link. Configuring Cell Packing Cell packing allows you to improve the efficiency of ATM-to-MPLS conversion by packing multiple ATM cells into a single MPLS packet. Follow these steps to configure cell packing. Step 1 Command Purpose enable Enables privileged EXEC mode. • Enter your password if prompted.
Chapter 23 Configuring Pseudowire Configuring Pseudowire Configuring Transportation of Service Using Ethernet over MPLS Ethernet over MPLS PWs allow you to transport Ethernet traffic over an existing MPLS network. For an overview of Ethernet over MPLS pseudowires, see Transportation of Service Using Ethernet over MPLS, page 23-3. Configuring VLAN Mode An Ethernet over MPLS pseudowire in VLAN mode creates a connection based on an existing VLAN ID on the Cisco MWR 2941.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire Note For more information about configuring VLANs on the Cisco MWR 2941, see the “Configuring VLANs” section on page 7-1. Configuration Examples for Pseudowire The following sections contain full configuration examples for pseudowire connections.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ! controller E1 0/1 clock source internal cem-group 20 unframed ! controller E1 0/2 clock source internal cem-group 12 unframed ! controller E1 0/3 clock source internal cem-group 30 unframed ! controller E1 0/4 clock source internal cem-group 8 unframed ! controller E1 0/5 clock source internal cem-group 25 unframed ! controller E1 1/0 mode atm clock source internal ! controller E1 1/1 mode atm clock source internal ! controller E1 1
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire no ip address cem 12 xconnect 50.0.0.2 3 encapsulation mpls ! ! interface CEM0/3 no ip address cem 30 xconnect 50.0.0.2 4 encapsulation mpls ! interface CEM0/4 no ip address cem 8 xconnect 50.0.0.2 5 encapsulation mpls ! ! interface CEM0/5 no ip address cem 25 xconnect 50.0.0.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire xconnect 50.0.0.2 12 encapsulation mpls pvc 0/10 l2transport encapsulation aal0 ! pvc 0/11 l2transport encapsulation aal0 ! pvc 0/12 l2transport encapsulation aal0 ! pvc 0/13 l2transport encapsulation aal0 ! ! interface ATM1/0.3 point-to-point pvc 0/16 l2transport encapsulation aal0 xconnect 50.0.0.2 14 encapsulation mpls ! ! interface ATM1/0.4 point-to-point pvc 0/17 l2transport encapsulation aal0 xconnect 50.0.0.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire interface ATM1/2 no ip address scrambling-payload ima-group 0 no ilmi-keepalive ! ip route 50.0.0.2 255.255.255.255 20.0.0.2 ! ip http server no ip http secure-server ! ! mpls ldp router-id Loopback50 force ! ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! network-clock-select 1 BITS ! end MWR_2 version 12.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ! controller E1 1/0 mode atm clock source internal ! controller E1 1/1 mode atm clock source internal ! controller E1 1/2 mode atm clock source internal ! controller E1 1/3 clock source internal ! pseudowire-class mpls encapsulation mpls preferred-path peer 50.0.0.1 ! ! interface Loopback50 ip address 50.0.0.2 255.255.255.255 ! interface CEM0/0 no ip address cem 1 xconnect 50.0.0.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire xconnect 50.0.0.1 4 encapsulation mpls ! ! interface CEM0/4 no ip address cem 8 xconnect 50.0.0.1 5 encapsulation mpls ! ! interface CEM0/5 no ip address cem 25 xconnect 50.0.0.1 6 encapsulation mpls ! ! interface ATM1/0 ip address 1.1.1.2 255.0.0.0 load-interval 30 scrambling-payload mcpt-timers 1000 5000 10000 no ilmi-keepalive pvc 0/5 l2transport encapsulation aal0 cell-packing 25 mcpt-timer 3 xconnect 50.0.0.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire encapsulation aal0 ! ! interface ATM1/0.3 point-to-point pvc 0/16 l2transport encapsulation aal0 xconnect 50.0.0.1 14 encapsulation mpls ! ! interface ATM1/0.4 point-to-point pvc 0/17 l2transport encapsulation aal0 xconnect 50.0.0.1 15 pw-class mpls one-to-one ! ! interface ATM1/0.6 multipoint pvc 0/26 l2transport xconnect 50.0.0.1 16 pw-class mpls ! pvc 0/27 l2transport encapsulation aal0 cell-packing 18 mcpt-timer 3 xconnect 50.0.0.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ! ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 exec-timeout 0 0 login ! network-clock-select 1 BITS ! end PWE3 Redundancy Configuration The following example shows a PWE3 Redundancy configuration (Figure 23-3). Figure 23-3 PWE3 Redundancy Configuration TDM (Primary) ATM Ethernet BTS/Node B GigabitEthernet0/1 9.9.9.6/24 MWR_1 GigabitEthernet0/1 ATM (Primary) ATM (Backup) 9.9.9.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire controller E1 1/1 ! controller E1 1/2 ! controller E1 1/3 clock source internal ! interface CEM0/0 cem 0 xconnect 2.2.2.2 1 encapsulation mpls backup peer 2.2.2.2 2 backup delay 20 20 ! interface ATM1/0 no ip address scrambling-payload no ilmi-keepalive pvc 0/1 l2transport encapsulation aal0 xconnect 2.2.2.2 3 encapsulation mpls backup peer 2.2.2.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire exec-timeout 0 0 logging synchronous line aux 0 line vty 0 4 exec-timeout 0 0 password mypassword login ! exception data-corruption buffer truncate ! end MWR_2 ! version 12.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire interface CEM0/0 cem 0 xconnect 1.1.1.1 1 encapsulation mpls ! ! Backup interface CEM0/1 cem 0 xconnect 1.1.1.1 2 encapsulation mpls ! ! Primary interface ATM1/0 no ip address scrambling-payload no ilmi-keepalive pvc 0/1 l2transport encapsulation aal0 xconnect 1.1.1.1 3 encapsulation mpls ! ! Backup interface ATM1/3 no ip address scrambling-payload no ilmi-keepalive pvc 0/1 l2transport encapsulation aal0 xconnect 1.1.1.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ! ! mpls ldp router-id Loopback1 force ! control-plane ! no call rsvp-sync ! ! ! line con 0 exec-timeout 0 0 logging synchronous line aux 0 line vty 0 4 exec-timeout 0 0 password mypassword login ! exception data-corruption buffer truncate ! end TDM over MPLS Configuration Figure 23-4 shows a TDM over MPLS configuration. The configuration uses both SAToP and CESoPSN for E1 and T1. TDM over MPLS Configuration 30.30.30.2 30.30.30.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ip cef ! controller E1 0/0 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 ! controller E1 1/0 clock source internal ! controller E1 1/1 ! inter
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire login line aux 0 password xxx login no exec line vty 0 4 password xxx login ! network-clock-select 1 BITS end MWR_B ! version 12.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire interface GigabitEthernet0/1 ip address 50.50.50.2 255.255.255.0 mpls ip ! 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 ! ! no ip classless ip route 30.30.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire 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 You cannot use the vrf interface as a tunnel source to establish the PW. You must use only the interface which is present in the global routing table.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire boot-start-marker boot-end-marker ! card type e1 0 0 card type e1 0 1 logging buffered 4096 enable password mypassword ! ! ip cef ! ! no ip domain lookup ! ! controller E1 0/0 mode atm clock source internal ! controller E1 0/1 mode atm clock source internal ! controller E1 0/2 mode atm clock source internal ! controller E1 0/3 mode atm clock source internal ! controller E1 0/4 ! controller E1 0/5 ! controller E1 1/0 ! controller E1 1/
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ! interface ATM0/1 no ip address load-interval 30 scrambling-payload mcpt-timers 1000 2000 3000 no ilmi-keepalive pvc 0/10 ! pvc 0/100 l2transport encapsulation aal5 xconnect 99.99.99.99 1100 encapsulation mpls ! pvc 0/101 l2transport encapsulation aal0 cell-packing 28 mcpt-timer 3 xconnect 99.99.99.99 1101 encapsulation mpls ! pvc 0/102 l2transport encapsulation aal0 cell-packing 28 mcpt-timer 3 xconnect 99.99.99.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire ! ! ip http server no ip http secure-server ! ! mpls ldp router-id Loopback0 ! ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 exec-timeout 0 0 privilege level 15 password mypassword login ! network-clock-select 1 E1 1/0 ! end MWR_B ! version 12.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire mpls experimental 5 ! ! interface Loopback0 ip address 99.99.99.99 255.255.255.255 ! interface ATM0/0 no ip address scrambling-payload mcpt-timers 1000 2000 3000 no ilmi-keepalive cell-packing 28 mcpt-timer 3 xconnect 88.88.88.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire interface GigabitEthernet0/1 ip address 2.2.2.3 255.255.255.0 duplex auto speed auto mpls ip ! interface ATM0/2 no ip address scrambling-payload ima-group 0 no ilmi-keepalive ! interface ATM0/3 no ip address scrambling-payload ima-group 0 no ilmi-keepalive ! ip route 88.88.88.88 255.255.255.255 2.2.2.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire service timestamps log datetime msec no service password-encryption ! hostname mwr_A ! boot-start-marker boot-end-marker ! card type e1 0 0 card type e1 0 1 logging buffered 4096 enable password mypassword ! no aaa new-model ! network-clock-select 1 E1 0/0 mmi polling-interval 60 no mmi auto-configure no mmi pvc mmi snmp-timeout 180 ip cef ! no ip domain lookup ip domain name cisco.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire xconnect 2.2.2.2 10 encapsulation mpls ! ip route 2.2.2.2 255.255.255.255 20.20.20.2 ! no ip http server no ip http secure-server ! ! mpls ldp router-id Loopback0 ! ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 exec-timeout 0 0 password mypassword login ! end MWR_B ! version 12.
Chapter 23 Configuring Pseudowire Configuration Examples for Pseudowire mode aim 1 ! controller E1 0/3 mode aim 1 ! controller E1 0/4 ! controller E1 0/5 ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 ! interface GigabitEthernet0/4 switchport trunk allowed vlan 1,2,20,1002-1005 switchport mode trunk ! interface GigabitEthernet0/5 switchport trunk allowed vlan 1,2,40,1002-1005 switchport mode trunk ! interface Vlan20 ip address 20.20.20.2 255.255.255.
CH A P T E R 24 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 24 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.0S. Sample MPLS VPN Configuration The following section shows a sample configuration for Layer 3 Virtual Private Network (VPN).
Chapter 24 Configuring MPLS VPNs Sample MPLS VPN Configuration redistribute bgp 101 metric-type 1 subnets network 192.168.0.0 0.0.255.255 area 0 network 192.169.0.0 0.0.255.255 area 0 ! ----------------------MP-BGP with 2 VRF customers --------------------------------router bgp 101 bgp router-id 100.1.1.1 bgp log-neighbor-changes neighbor 100.1.1.2 remote-as 101 neighbor 100.1.1.2 update-source Loopback1 ! address-family ipv4 redistribute connected neighbor 100.1.1.
Chapter 24 Configuring MPLS VPNs Sample MPLS VPN Configuration vrf forwarding customer_a ip address 192.169.3.2 255.255.255.0 ! interface GigabitEthernet0/5 switchport access vlan 99 load-interval 30 duplex full ! interface Vlan99 vrf forwarding customer_b ip address 192.169.3.2 255.255.255.0 ! Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 25 Configuring Quality of Service QoS refers to the ability of a network to provide improved service to selected network traffic over various underlying technologies including Frame Relay, ATM, Ethernet and 802.1 networks, SONET, and IP-routed networks.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Traffic Classification Classifying network traffic allows you to organize packets into traffic classes based on whether the traffic matches specific criteria. Classifying network traffic is the foundation for enabling many QoS features on your network. For instructions on how to configure traffic classification, see Configuring Classification.
Chapter 25 Configuring Quality of Service Configuring Quality of Service • Configuring Ethernet Trusted Mode, page 25-26 QoS Limitations The Cisco MWR 2941 offers different QoS support according to the physical interface and traffic type. The following sections describe the limitations for each QoS capability on the Cisco MWR 2941.
Chapter 25 Configuring Quality of Service Configuring Quality of Service • The show policy-map command displays inaccurate output for QoS counters due to ingress counter limitations on the router. The command displays a summary of QoS activity on the MWR 2941 that is limited as follows: – The number of packets displayed below the Class-map name includes the number of packets matched and marked on the router. – The Packets marked number for each QoS value always displays as 0.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Classification Limitations Table 25-1 summarizes the values that you can use to classify traffic based on interface type. The values are parameters that you can use with the match command.
Chapter 25 Configuring Quality of Service Configuring Quality of Service – Ingress VLAN classification is not supported on switchport interfaces configured as dot1q tunnels using the switchport mode dot1q-tunnel command. We recommend that you configure classification based on CoS, Exp bit, or DSCP. • The following limitations apply to output Gigabit Ethernet interface QoS policies: – Class maps only support matching based on qos-group. This limitation does not apply to the class-default class map.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Congestion Management Limitations The congestion management limitations for the Cisco MWR 2941 are described in the following sections: • Queuing Limitations • Rate Limiting Limitations Queuing Limitations The Cisco MWR 2941 uses CBFQ for congestion management. Table 25-3 summarizes the queuing commands that you can apply when using CBFQ according to interface type.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Table 25-4 QoS Rate Limiting Limitations by Interface Policing with GigabitEthernet HWIC-9ESW MLPPP HWIC-1GE-SFP HWIC-ADSL HWIC-SHDSL Ingress Egress Ingress Egress Ingress Egress Ingress Egress Ingress Egress Ingress Egress One rate One rate and two actions Two rates and two actions Two rates and three actions Shaping Limitations Table 25-5 summarizes the values that you can use to mark traffic based on interface typ
Chapter 25 Configuring Quality of Service Configuring Quality of Service • For traffic passing between other interfaces, the output queue is determined based on the CS fields (top three bits) of the IP DSCP bits; these bits are copied to the CoS bits, which are mapped 1:1 to the QoS group value.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Note This is a partial configuration intended to demonstrate the QoS feature. To view other QoS sample configurations see Sample Quality of Service Configurations. Configuring Classification Classifying network traffic allows you to organize packets into traffic classes based on whether the traffic matches specific criteria. Classifying network traffic is the foundation for enabling many QoS features on your network.
Chapter 25 Configuring Quality of Service Configuring Quality of Service 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)# policy-map policy1 Router(config-pmap)# Defines a new policy map and enter policy map configuration mode.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 4 Router(config-if)# service-policy output policy1 Attaches the policy map to an interface. The input and output parameters specify the direction in which router applies the policy map. Step 5 exit Exits configuration mode. Example: Router(config)# exit Router# Note You can use the show policy map interface command to verify your configuration.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Creating a Class Map for Marking Network Traffic Class maps allow you to define classes of network traffic to apply QoS features to each class. Follow these steps to define a traffic class to mark network traffic. 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 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 4 Router(config-pmap)# class class1 Router(config-pmap-c)# Specifies the traffic class for which you want to create a policy and enter policy map class configuration mode. You can also use the class-default parameter to define a default class. Step 5 set cos set dscp set qos-group Defines a QoS treatment type; use one of the set commands listed in Table 6. Step 6 exit Exits configuration mode.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 4 Router(config-if)# service-policy input policy1 Attaches the policy map to an interface. The input and output parameters specify the direction in which router applies the policy map. Step 5 exit Exits configuration mode. Example: Router(config)# exit Router# Note You can use the show policy map interface command to verify your configuration.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 10 Router(cfg-if-atm-l2trans-pvc)# xconnect 10.10.10.1 121 pw-class MPLS_3 Creates a pseudowire. Use the pw-class keyword to use the configuration defined in the pseudowire class. Step 11 exit Exits configuration mode. Example: Router(config)# exit Router# For more information about configuring marking, see the Quality of Service Solutions Configuration Guide, Cisco IOS Release 15.0S.
Chapter 25 Configuring Quality of Service Configuring Quality of Service • While QoS is enabled on the SVI interface, the Cisco MWR 2941 supports only DSCP-to-CoS remarking on the SVI interface. • Because the Cisco MWR 2941 supports DSCP-to-CoS mapping via an SVI interface, operators must manage route paths to ensure that all incoming traffic from a multilink interface is forwarded to a VLAN on which the remarking occurs on the egress side of the VLAN interface.
Chapter 25 Configuring Quality of Service Configuring Quality of Service The following configuration example configures a table map with the name “DCSP-to-CoS-marking,” in which specific DSCP values are mapped to specific COS values.
Chapter 25 Configuring Quality of Service Configuring Quality of Service The following configuration example configures a policy map with the name “qos-marking” and associates the “DSCP-to-COS-marking” table map to the class.
Chapter 25 Configuring Quality of Service Configuring Quality of Service The following configuration example configures an SVI interface with the name “Vlan999” and attaches a policy map named “qos-marking” to its output interface. Additionally, the SVI interface is added to the list of VLANs allowed on the trunk. Router(config)# interface Vlan999 Router(config-if)# ip address 200.200.200.1 255.255.255.
Chapter 25 Configuring Quality of Service Configuring Quality of Service interface Vlan999 description for XYZ ip address 200.200.200.1 255.255.255.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose show interface gigaport port-num Displays the statistics of Gigabit interface. show platform hardware winpath cef ipv4 adj-ip-address Platform command for viewing the statistics. Note Operators can only view DSCP-to-COS remarking in a neighbor router (or Traffic Generator) that is connected to the Cisco MWR 2941 over the SVI interface.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 6 Router(config-pmap-c)# bandwidth percent 30 Use the bandwidth command to specify the bandwidth available to the traffic class within the policy map. You can specify the bandwidth in kbps or by a percentage of bandwidth. Step 7 exit Exit configuration mode.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 9 Router(config-pmap)# exit Router(config)# Exits the policy map configuration. Step 10 Router(config)# interface atm0/ima0 Enters configuration for the interface to which you want to apply the policy map. Step 11 Router(config-if)# service-policy output policy1 Applies the service policy to the interface. Step 12 exit Exits configuration mode.
Chapter 25 Configuring Quality of Service Configuring Quality of Service Command Purpose Step 6 Router(config-pmap-c)# service-policy policy-map Attaches the policy map to the class map. Step 7 exit Exits configuration mode. Example: Router(config)# exit Router# Note You can use the show policy-map command to verify your configuration. For more information about configuring shaping, see the Quality of Service Solutions Configuration Guide, Cisco IOS Release 15.0S.
Chapter 25 Configuring Quality of Service Sample Quality of Service Configurations For more information about configuring shaping, see the Quality of Service Solutions Configuration Guide, Cisco IOS Release 15.0S. Note The Cisco MWR 2941 does not support all of the commands described in the IOS Release 15.0S documentation. Configuring Ethernet Trusted Mode The Cisco MWR 2941 supports trusted and non-trusted mode for switch ports.
Chapter 25 Configuring Quality of Service Sample Quality of Service Configurations ! regardless of current priority values.
Chapter 25 Configuring Quality of Service Sample Quality of Service Configurations ! ! Note 4: the hierarchical output policy handles WRR and shaping policy-map QOS-child class group6 priority percent 5 class group5 bandwidth percent 20 class group4 bandwidth percent 20 class group3 bandwidth percent 20 class group1 bandwidth percent 20 policy-map output-policy class class-default shape average 38000000 service-policy QOS-child ! Interface GigabitEthernet 0/0 service-policy input input-policy Interface G
Chapter 25 Configuring Quality of Service Sample Quality of Service Configurations ip address 50.50.50.49 255.255.255.
Chapter 25 Configuring Quality of Service Sample Quality of Service Configurations Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 26 Configuring Link Noise Monitor Noise on T1 and E1 links that span between the BTS and central office can affect voice quality for mobile users to the point where it becomes unacceptable. To monitor the quality of individual links in a multilink bundle, you can configure the Link Noise Monitor (LNM) on your Cisco MWR 2941 router. The LNM detects, alerts, and removes noisy links from a bundle based on user-defined thresholds and durations.
Chapter 26 Configuring Link Noise Monitor Usage Notes • lcv value—Threshold (in bit errors per second) that when exceeded for the configured duration when the set keyword has been specified, creates a condition (warning or link removal), or when fallen below for the configured duration when the clear keyword has been specified, clears the condition. For T1 links: – Valid range is 5 to 1544. – For Link Warning monitoring, the default is 15. – For Link Removal monitoring, the default is 154.
Chapter 26 Configuring Link Noise Monitor Usage Notes • If the span command is issued without either the set or clear keywords specified, set is the default. • The set and clear keywords can only be specified if the threshold and/or duration has been specified. • If the PCV threshold is not configured (using the pcv keyword and value), the threshold is calculated using Gaussian probability distribution that is representative of most noise environments.
Chapter 26 Configuring Link Noise Monitor Usage Notes Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 27 Configuring Cisco Discovery Protocol This chapter describes how to configure Cisco Discovery Protocol (CDP) on the Cisco MWR 2941 router. Note For complete syntax and usage information for the commands used in this chapter, see the Cisco MWR 2941 Mobile Wireless Edge Router IOS Command Reference, Release 15.0(1)MR and the Configuration Fundamentals Configuration Guide, Cisco IOS Release 15.0S.
Chapter 27 Configuring Cisco Discovery Protocol Configuring CDP For a router and connected endpoint devices running Cisco Medianet • CDP identifies connected endpoints that communicate directly with the router. • To prevent duplicate reports of neighboring devices, only one wired switch reports the location information. • The wired switch and the endpoints both send and receive location information. For information, go to http://www.cisco.
Chapter 27 Configuring Cisco Discovery Protocol Configuring CDP Command Purpose Step 1 configure terminal Enters global configuration mode. Step 2 cdp timer seconds (Optional) Sets the transmission frequency of CDP updates in seconds. The range is from 5–254; the default is 60 seconds. Step 3 cdp holdtime seconds (Optional) Specifies the amount of time a receiving device should hold the information sent by your device before discarding it.
Chapter 27 Configuring Cisco Discovery Protocol Configuring CDP Beginning in privileged EXEC mode, follow these steps to globally enable CDP when it has been disabled: Command Purpose Step 1 configure terminal Enters global configuration mode. Step 2 cdp run Enables CDP after disabling it. Step 3 end Returns to privileged EXEC mode.
Chapter 27 Configuring Cisco Discovery Protocol Monitoring and Maintaining CDP This example shows how to change a UNI to an ENI and enable CDP on the port. Router# configure terminal Router(config)# interface fastethernet0/1 Router(config-if)# cdp enable Router(config-if)# end Monitoring and Maintaining CDP To monitor and maintain CDP on your device, perform one or more of these tasks, beginning in privileged EXEC mode: Command Description clear cdp counters Resets the traffic counters to zero.
Chapter 27 Configuring Cisco Discovery Protocol Monitoring and Maintaining CDP Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
CH A P T E R 28 Configuring Traffic Storm Control This chapter describes how to configure traffic storm control on the Cisco MWR 2941.
Chapter 28 Configuring Traffic Storm Control Guidelines and Limitations Note • If you enable unicast traffic storm control, and unicast traffic exceeds the level within a 1-second traffic storm control interval, traffic storm control drops all traffic (broadcast, multicast, and unicast) on the interface until the end of the traffic storm control interval.
Chapter 28 Configuring Traffic Storm Control Configuring Traffic Storm Control Support on the MWR 2941 Configuring Traffic Storm Control Support on the MWR 2941 The Cisco MWR 2941 supports traffic storm control filters using bandwidth level and packets per second (PPS).
Chapter 28 Configuring Traffic Storm Control Configuring Traffic Storm Control Support on the MWR 2941 Step 5 Command Purpose storm-control action {shutdown | trap} Specifies the action taken when a storm occurs on a port, where: Example: Router(config-if)# storm-control action shutdown • shutdown—Disables the port during a storm. • trap—Sends an SNMP trap. The default action is to filter traffic. Step 6 Exits interface configuration mode.
Chapter 28 Configuring Traffic Storm Control Configuring Traffic Storm Control Support on the MWR 2941 Step 4 Command Purpose storm-control {{broadcast | multicast | unicast} level pps number} Enables broadcast, multicast, or unicast storm control on a port, where: • broadcast—Enables broadcast storm control on the port. • multicast—Enables multicast storm control on the port. • unicast—Enables unicast storm control on the port. • level pps rate—Specifies the rate of PPS.
Chapter 28 Configuring Traffic Storm Control Monitoring and Maintaining Storm Control Step 3 Command Purpose errdisable recovery interval seconds Specifies the time, in seconds, to recover from a specified error-disable cause. The range is from 30 to 86400. The default interval is 300. Example: Router(config-if)# errdisable recovery interval 30 Step 4 Exits interface configuration mode.
CH A P T E R 29 Monitoring and Managing the Cisco MWR 2941 Router The Cisco MWR 2941 supports a variety of network management features, including Mobile Wireless Transport Manager (MTWM), Cisco Active Network Abstraction (ANA), SNMP, and Cisco Networking Services (CNS). The following sections describe the network management features on the Cisco MWR 2941.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features the physical elements. Its virtual nature provides customers with a strong and reliable platform for service activation, service assurance and network management. For more information about ANA, see http://www.cisco.com/en/US/products/ps6776/tsd_products_support_series_home.html.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features • Inventory • OSS Integration • Security • Client/Server Architecture • Multiple OS Support The Cisco MWTM integrates with any SNMP-based monitoring system, such as Cisco Info Center products. In addition, the Cisco MWTM collects a large amount of performance data that can be exported or directly accessed from the database. This data can then be used by performance reporting applications.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features 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 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Step 5 Command Purpose Router(config)# snmp-server enable traps [notification-type] [notification-option] Enables the router to send SNMP traps or notifications. Use the no form of this command to disable SNMP notifications.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Step 6 Command Purpose Router(config)# snmp-server enable traps ipran Enables SNMP traps for all IP-RAN notifications. Note Besides enabling SNMP traps for all IP-RAN notifications, you can also enable traps for IP-RAN GSM alarms, UMTS alarms, and general information about the backhaul utilization.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features 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—Enable SNMP AAA Server traps. – atm—Enable SNMP atm Server traps. – ccme—Enable SNMP ccme traps. – cnpd—Enable NBAR Protocol Discovery traps. – config—Enable SNMP config traps.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Command Purpose – pppoe—Enable SNMP pppoe traps. – pw—Enable SNMP PW traps. – rsvp—Enable RSVP flow change traps. – snmp—Enable SNMP traps. – srst—Enable SNMP srst traps. – syslog—Enable SNMP syslog traps. – tty—Enable TCP connection traps. – voice—Enable SNMP voice traps. – vrrp—Enable SNMP vrrp traps. – vtp—Enable SNMP VTP traps. – xgcp—Enable XGCP protocol traps.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Step 6 Command Purpose Router(config)# snmp-server host hostname [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}] community-string [udp-port port] [notification-type] Specifies the recipient of a Simple Network Management Protocol (SNMP) notification operation. The hostname is the name assigned to the Cisco Info Center workstation with the ip host command in Step 3.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Command Purpose show controllers t1 Information about cable length, framing, firmware, and errors associated with the T1. With the Cisco MWR 2941 router, this command also shows the status of the relays on the VWIC. show dsl interface atm Displays information specific to the asymmetric digital subscriber line (ADSL) for a specified ATM interface.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Command Purpose show policy-map interface Statistics and the configurations of the input and output policies that are attached to an interface. show ppp multilink MLP and multilink bundle information. show ppp multilink interface number Multilink information for the specified interface. show protocols Protocols configured for the router and the individual interfaces.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features TFTP/DHCP Server MWR 2941-DC Router WAN CNS-CE Server 252924 MWR 2941-DC Router Customer premises Note These devices must be connected through onboard Ethernet interfaces. CNS connections over Ethernet HWICs and non-Ethernet interfaces are not supported. The following sections describe how to configure CNS on the Cisco MWR 2941.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features 8. The CNS-CE server sends a configuration template to the Cisco MWR 2941 9. Successful event 10. Publish success event Image Download The following events take place when a CNS-enabled Cisco MWR 2941 downloads a new image. 1. The CNS-CE server requests inventory (disk/flash info) from the Cisco MWR 2941-DC 2. The Cisco MWR 2941-DC sends an inventory 3.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features ! end For more information about the commands used in this configuration, see the Cisco MWR 2941 Mobile Wireless Edge Router IOS Command Reference, Release 15.0(1)MR. Cisco Configuration Engine Installation & Configuration Guide at http://www.cisco.com/en/US/products/sw/netmgtsw/ps4617/tsd_products_support_series_home.html.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features • debug cns all Zero Touch Deployment Sample Configuration The following configuration example sets the Cisco MWR 2941 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 2941 ! cns trusted-server all-agents 30.30.1.20 cns event 30.30.1.
Chapter 29 Monitoring and Managing the Cisco MWR 2941 Router Configuring Network Management Features Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.
INDEX Cisco MWR 2941-DC router A monitoring and managing ATM port 4-6 port numbering attachment circuits 1-3 4-46 3-2 show commands for monitoring 4-48 autodiscovery 4-46 slot numbering auxiliary port 3-2 understanding interface numbering 3-2 3-1 Cisco Pseudowire Emulation Edge-to-Edge See PWE3 B Cisco pseudowire emulation edge-to-edge See PWE3 base station controller clocking See BSC base station controller (BSC) clocking example (figure) 4-6 clock signal base transceiver statio
Index interface atm ima A-29 hostname ip local interface A-30 IP address 4-2 4-4 ip rtp header-compression A-32 multilink interface ip tcp header-compression A-35 password keepalive load-interval A-59 D A-57 3-3 data bearer traffic show atm cell-packing show cem circuit show connection show controller A-81 duplex mode, setting E A-86 A-88 E1 controllers show mpls l2transport vc A-100 enable mode A-102 2-2, 4-46 event monitoring 4-46 A-114 snmp-server enable traps ipran F
Index mode 4-5 speed 4-5 N Network-Clock-Participate global parameters configuring network-clock-select 3-3 A-53 A-53 P H help, Cisco IOS password 2-1 3-5 configuring hostname configuring verifying verifying 4-2 4-2 4-3 point-of-presence 4-3 See POP POP I cell site POP intelligent cell site IP services 1-5 interface configuring E1 4-23 GE, configuring multilink 4-4 port numbering Cisco MWR 2941-DC router ptp announce 2-1 verifying version 4-1 IP address configuring 4-4
Index switchport backup interface R A-120 synchronized network operation RAN, using the Cisco MWR 2941-DC router recovered-clock slave 1-1 A-78 T RNC in a RAN 4-6 1-1 transmit clock S 4-6 U SAToP 1-3 undo feature saving configuration changes security serial port 2-3, 4-45 Cisco IOS 2-2 4-46 4-6 set network-clocks V A-80 setup command facility 3-3 show atm cell-packing A-81 verifying show commands for monitoring the Cisco MWR 2941-DC router 4-48 show controller show interface
