Ethernet Card Software Feature and Configuration Guide For the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 Cisco IOS Release 12.2 (29a) sv CTC and Documentation Release 7.2 Last Updated: January 2009 Corporate 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 xxvii Revision History xxvii Document Objectives xxviii Audience xxviii Document Organization xxviii Related Documentation xxx Document Conventions xxxi Obtaining Optical Networking Information xxxvi Where to Find Safety and Warning Information xxxvii Cisco Optical Networking Product Documentation CD-ROM Obtaining Documentation and Submitting a Service Request CHAPTER 1 ML-Series Card Overview CHAPTER 2 CTC Operations xxxvii 1-1 ML-Series Card Description ML-Se
Contents ML-Series IOS CLI Console Port 3-4 RJ-11 to RJ-45 Console Cable Adapter 3-5 Connecting a PC or Terminal to the Console Port 3-5 Startup Configuration File 3-7 Manually Creating a Startup Configuration File Through the Serial Console Port Passwords 3-8 Configuring the Management Port 3-8 Configuring the Hostname 3-9 CTC and the Startup Configuration File 3-9 Loading a Cisco IOS Startup Configuration File Through CTC 3-10 Database Restore of the Startup Configuration File 3-11 Multiple Microcode I
Contents Framing Mode, Encapsulation, and CRC Support 5-4 Configuring POS Interface Framing Mode 5-4 Configuring POS Interface Encapsulation Type 5-4 Configuring POS Interface CRC Size in HDLC Framing 5-5 Setting the MTU Size 5-5 Configuring Keep Alive Messages 5-6 SONET/SDH Alarms 5-6 Configuring SONET/SDH Alarms 5-7 Configuring SONET/SDH Delay Triggers 5-7 Configuring SONET/SDH Alarms 5-7 C2 Byte and Scrambling 5-8 Third-Party POS Interfaces C2 Byte and Scrambling Values 5-9 Configuring SPE Scrambling 5-
Contents Spanning-Tree Interface States 7-5 Blocking State 7-6 Listening State 7-7 Learning State 7-7 Forwarding State 7-7 Disabled State 7-7 Spanning-Tree Address Management 7-8 STP and IEEE 802.
Contents CHAPTER 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding IEEE 802.1Q Tunneling 9-1 9-1 Configuring IEEE 802.1Q Tunneling 9-4 IEEE 802.1Q Tunneling and Compatibility with Other Features Configuring an IEEE 802.1Q Tunneling Port 9-4 IEEE 802.
Contents Configuring OSPF 11-9 OSPF Interface Parameters 11-13 OSPF Area Parameters 11-14 Other OSPF Behavior Parameters 11-16 Change LSA Group Pacing 11-18 Loopback Interface 11-19 Monitoring OSPF 11-19 Configuring EIGRP 11-20 EIGRP Router Mode Commands 11-22 EIGRP Interface Mode Commands 11-23 Configure EIGRP Route Authentication 11-25 Monitoring and Maintaining EIGRP 11-26 Border Gateway Protocol and Classless Interdomain Routing Configuring BGP 11-27 Verifying the BGP Configuration 11-28 Configuring IS
Contents Priority Mechanism in IP and Ethernet 14-2 IP Precedence and Differentiated Services Code Point Ethernet CoS 14-3 14-2 ML-Series QoS 14-4 Classification 14-4 Policing 14-5 Marking and Discarding with a Policer 14-5 Queuing 14-6 Scheduling 14-6 Control Packets and L2 Tunneled Protocols 14-8 Egress Priority Marking 14-8 Ingress Priority Marking 14-8 QinQ Implementation 14-8 Flow Control Pause and QoS 14-9 QoS on Cisco Proprietary RPR 14-10 Configuring QoS 14-12 Creating a Traffic Class 14-12 Cre
Contents Configuring CoS-Based Packet Statistics Understanding IP SLA 14-31 IP SLA on the ML-Series 14-32 IP SLA Restrictions on the ML-Series CHAPTER 15 14-29 14-32 Configuring the Switching Database Manager Understanding the SDM 15-1 15-1 Understanding SDM Regions 15-1 Configuring SDM 15-2 Configuring SDM Regions 15-2 Configuring Access Control List Size in TCAM Monitoring and Verifying SDM CHAPTER 16 Configuring Access Control Lists Understanding ACLs 15-3 15-3 16-1 16-1 ML-Series ACL
Contents CTC Circuit Configuration Example for Cisco Proprietary RPR 17-8 Configuring Cisco Proprietary RPR Characteristics and the SPR Interface on the ML-Series Card 17-12 Assigning the ML-Series Card POS Ports to the SPR Interface 17-14 Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces 17-15 Cisco Proprietary RPR Cisco IOS Configuration Example 17-16 Verifying Ethernet Connectivity Between Cisco Proprietary RPR Ethernet Access Ports 17-18 CRC threshold configuration and detection 1
Contents EoMPLS Configuration on PE-CLE SPR Interface 18-8 Bridge Group Configuration on MPLS Cloud-facing Port Setting the Priority of Packets with the EXP 18-9 EoMPLS Configuration Example 18-8 18-9 Monitoring and Verifying EoMPLS 18-12 Understanding MPLS-TE 18-13 RSVP on the ML-Series Card 18-13 Ethernet FCS Preservation 18-13 Configuring MPLS-TE 18-14 Configuring an ML-Series Card for Tunnels Support 18-14 Configuring an Interface to Support RSVP-Based Tunnel Signalling and IGP Flooding Configurin
Contents Configuring RADIUS Authorization for User Privileged Access and Network Services 19-15 Starting RADIUS Accounting 19-16 Configuring a nas-ip-address in the RADIUS Packet 19-16 Configuring Settings for All RADIUS Servers 19-17 Configuring the ML-Series Card to Use Vendor-Specific RADIUS Attributes 19-18 Configuring the ML-Series Card for Vendor-Proprietary RADIUS Server Communication 19-19 Displaying the RADIUS Configuration 19-20 CHAPTER 20 POS on ONS Ethernet Cards POS Overview 20-1 20-1 PO
Contents SONET/GFP Suppression of CRC-ALARM Clearing of CRC-ALARM 21-7 Unwrap Synchronization 21-8 Unidirectional Errors 21-8 Bidirectional Errors 21-10 21-7 Configuring the ML-Series Card CRC Error Threshold 21-13 Clearing the CRC-ALARM Wrap with the Clear CRC Error Command 21-14 Configuring ML-Series Card RMON for CRC Errors 21-15 Configuration Guidelines for CRC Thresholds on the ML-Series Card 21-15 Accessing CRC Errors Through SNMP 21-15 Configuring an SNMP Trap for the CRC Error Threshold Using C
Contents G1K-4 and G1000-4 Comparison 23-2 G-Series Example 23-3 IEEE 802.3z Flow Control and Frame Buffering 23-3 Gigabit EtherChannel/IEEE 802.
Contents CHAPTER 24 CE-100T-8 Ethernet Operation CE-100T-8 Overview 24-1 24-1 CE-100T-8 Ethernet Features 24-2 Autonegotiation, Flow Control, and Frame Buffering 24-2 Ethernet Link Integrity Support 24-3 Administrative and Service States with Soak Time for Ethernet and SONET/SDH Ports IEEE 802.
Contents Role of SONET/SDH Circuits 26-2 RPR-IEEE Framing Process 26-3 CTM and RPR-IEEE 26-6 Configuring RPR-IEEE Characteristics 26-6 Configuring the Attribute Discovery Timer 26-7 Configuring the Reporting of SONET Alarms 26-7 Configuring BER Threshold Values 26-8 Configuring RPR-IEEE Protection 26-8 Configuring the Hold-off Timer 26-9 Configuring Jumbo Frames 26-10 Configuring Forced or Manual Switching 26-11 Configuring Protection Timers 26-12 Configuring the Wait-to-Restore Timer 26-13 Configuring a S
Contents Characteristics of RI on the ML-Series Card RI Configuration Example 26-39 APPENDIX A Command Reference APPENDIX B Unsupported CLI Commands 26-38 A-1 B-1 Unsupported Privileged Exec Commands B-1 Unsupported Global Configuration Commands B-1 Unsupported POS Interface Configuration Commands B-3 Unsupported POS Interface Configuration Commands (Cisco Proprietary RPR Virtual Interface) Unsupported IEEE 802.
F I G U R E S Figure 3-1 CTC IOS Window Figure 3-2 CTC Node View Showing IP Address and Slot Number Figure 3-3 Console Cable Adapter Figure 3-4 Connecting to the Console Port Figure 5-1 ML-Series Card to ML-Series Card POS Configuration Figure 5-2 ML-Series Card to Cisco 12000 Series Gigabit Switch Router (GSR) POS Configuration Figure 5-3 ML-Series Card to G-Series Card POS Configuration Figure 5-4 ML-Series Card to ONS 15310 CE-100T-8 Card Configuration Figure 6-1 Bridging Example Figur
Figures Figure 14-7 ML-Series VoIP Example Figure 14-8 ML-Series Policing Example Figure 14-9 ML-Series CoS Example Figure 14-10 QoS not Configured on Egress Figure 17-1 Cisco Proprietary RPR Packet Handling Operations Figure 17-2 Cisco proprietary RPR Ring Wrapping Figure 17-3 Cisco Proprietary RPR Frame for ML-Series Card Figure 17-4 Cisco Proprietary RPR Frame Fields Figure 17-5 Three Node Cisco Proprietary RPR 17-9 Figure 17-6 CTC Card View for ML-Series Card 17-10 Figure 17-7 CT
Figures Figure 21-3 Unwrapped Cisco proprietary RPR with Unidirectional Excessive CRC Errors Figure 21-4 Wrapped Cisco proprietary RPR with Bidirectional Excessive CRC Errors Figure 21-5 First Stage of Unwrapped Cisco proprietary RPR with Bidirectional Excessive CRC Errors Figure 21-6 Second Stage of Unwrapped Cisco proprietary RPR with Bidirectional Excessive CRC Errors Figure 22-1 SNMP on the ML-Series Card Example Figure 22-2 SNMP Network Figure 23-1 Data Traffic on a G-Series Point-to-Poin
Figures Figure 25-3 End-to-End Ethernet Link Integrity Support Figure 26-1 Dual-Ring Structure Figure 26-2 RPR-IEEE Data Frames Figure 26-3 Topology and Protection Control Frame Formats Figure 26-4 Fairness Frame Format Figure 26-5 Each RPR-IEEE Node Responding to a Protection Event by Steering Figure 26-6 Three Node RPR-IEEE Example Figure 26-7 RPR-IEEE Bridge Group Figure 26-8 RPR RI 25-4 26-3 26-4 26-5 26-6 26-9 26-32 26-33 26-38 Ethernet Card Software Feature and Configuration G
T A B L E S Table 2-1 ML-Series POS and Ethernet Statistics Fields and Buttons Table 2-2 CTC Display of Ethernet Port Provisioning Status Table 2-3 CTC Display of POS Port Provisioning Status Table 3-1 RJ-11 to RJ-45 Pin Mapping Table 3-2 Microcode Image Feature Comparison Table 3-3 Cisco IOS Command Modes Table 5-1 SONET STS Circuit Capacity in Line Rate Mbps Table 5-2 VCAT Circuit Sizes Supported by ML100T-12, ML100X-8, and ML1000-2 Cards Table 5-3 Supported Encapsulation, Framing, and C
Tables Table 12-1 Commands for Monitoring and Verifying IRB Table 12-2 show interfaces irb Field Descriptions Table 13-1 Commands for Monitoring and Verifying VRF Lite Table 14-1 Traffic Class Commands 14-12 Table 14-2 Traffic Policy Commands 14-14 Table 14-3 CoS Commit Command Table 14-4 Commands for QoS Status Table 14-5 CoS Multicast Priority Queuing Command Table 14-6 Packet Statistics on ML-Series Card Interfaces Table 14-7 CoS-Based Packet Statistics Command Table 14-8 Commands
Tables Table 23-6 Protection for E-Series Circuit Configurations Table 24-1 IP ToS Priority Queue Mappings Table 24-2 CoS Priority Queue Mappings Table 24-3 Supported SONET Circuit Sizes of CE-100T-8 on ONS 15454 Table 24-4 CE-100T-8 Supported SDH Circuit Sizes of CE-100T-8 on ONS 15454 SDH Table 24-5 Minimum SONET Circuit Sizes for Ethernet Speeds Table 24-6 SDH Circuit Sizes and Ethernet Services Table 24-7 CCAT High-Order Circuit Size Combinations for SONET Table 24-8 CCAT High-Order Ci
Tables Ethernet Card Software Feature and Configuration Guide, R7.
About this Guide Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
About this Guide Date Notes July 2008 Updated section “Flow Control Pause and QoS” of the Ingress Priority Marking Topic in Chapter 14, Configuring Quality of Service. January 2009 Added the following sections in Chapter 14, Configuring Quality of Service: • QoS not Configured on Egress • ML-Series Egress Bandwidth Example • Added a new bullet point in the “IP SLA Restrictions on the ML-Series” section.
About this Guide • Chapter 6, “Configuring Bridges,” provides bridging examples and procedures for the ML-Series card. • Chapter 7, “Configuring STP and RSTP,” provides spanning tree and rapid spanning tree examples and procedures for the ML-Series card. • Chapter 8, “Configuring VLANs,” provides VLAN examples and procedures for the ML-Series card. • Chapter 9, “Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling,” provides tunneling examples and procedures for the ML-Series card.
About this Guide • Appendix C, “Using Technical Support,” instructs the user on using the Cisco Technical Assistance Center (Cisco TAC) for ML-Series card problems. Related Documentation Use the Ethernet Card Software Feature and Configuration Guide, R7.2 in conjunction with the following general ONS 15454 or ONS 15454 SDH system publications: • Cisco ONS 15454 Procedure Guide Provides procedures to install, turn up, provision, and maintain a Cisco ONS 15454 node and network.
About this Guide The ML-Series card employs the Cisco IOS Modular QoS CLI (MQC). For more information on general MQC configuration, refer to the following Cisco IOS documents: • Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 • Cisco IOS Quality of Service Solutions Command Reference, Release 12.2 The ML-Series card employs Cisco IOS 12.2. For more general information on Cisco IOS 12.2, refer to the extensive Cisco IOS documentation at: • http://www.cisco.
About this Guide Warning IMPORTANT SAFETY INSTRUCTIONS This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.
About this Guide Avvertenza IMPORTANTI ISTRUZIONI SULLA SICUREZZA Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti.
About this Guide Ethernet Card Software Feature and Configuration Guide, R7.
About this Guide Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA Este símbolo de aviso significa perigo. Você se encontra em uma situação em que há risco de lesões corporais. Antes de trabalhar com qualquer equipamento, esteja ciente dos riscos que envolvem os circuitos elétricos e familiarize-se com as práticas padrão de prevenção de acidentes. Use o número da declaração fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham o dispositivo.
About this Guide Obtaining Optical Networking Information This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section. Ethernet Card Software Feature and Configuration Guide, R7.
About this Guide Where to Find Safety and Warning Information For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation.
About this Guide Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 1 ML-Series Card Overview This chapter provides an overview of the ML1000-2, ML100T-12, and ML100X-8 cards for the ONS 15454 (SONET) and ONS 15454 SDH. It lists Ethernet and SONET/SDH capabilities and Cisco IOS and Cisco Transport Controller (CTC) software features, with brief descriptions of selected features.
Chapter 1 ML-Series Card Overview ML-Series Feature List ML-Series Feature List The ML100T-12, ML100X-8, and ML1000-2 cards have the following features: • Layer 1 data features: – 10/100BASE-TX half-duplex and full-duplex data transmission – 100BASE-FX full-duplex data transmission with Auto-MDIX (ML100X-8) – 1000BASE-SX, 1000BASE-LX full-duplex data transmission – IEEE 802.3z (Gigabit Ethernet) and IEEE 802.
Chapter 1 ML-Series Card Overview ML-Series Feature List • RPR-IEEE service qualities supported: – Per-service-quality flow-control protocols regulate traffic introduced by clients. – Class A allocated or guaranteed bandwidth has low circumference-independent jitter. – Class B allocated or guaranteed bandwidth has bounded circumference-dependent jitter. This class allows for transmissions of excess information rate (EIR) bandwidths (with class C properties). – Class C provides best-effort services.
Chapter 1 ML-Series Card Overview ML-Series Feature List • Cisco Proprietary RPR: – Ethernet frame check sequence (FCS) preservation for customers – Cyclic redundancy check (CRC) error alarm generation – FCS detection and threshold configuration – Shortest path determination – Keep alives • Fast EtherChannel (FEC) features (ML100T-12): – Bundling of up to four Fast Ethernet ports – Load sharing based on source and destination IP addresses of unicast packets – Load sharing for bridge traffic based on MAC
Chapter 1 ML-Series Card Overview ML-Series Feature List – Intermediate System-to-Intermediate System (IS-IS) Protocol – Routing Information Protocol (RIP and RIP II) – Enhanced Interior Gateway Routing Protocol (EIGRP) – Open Shortest Path First (OSPF) Protocol – Protocol Independent Multicast (PIM)—Sparse, sparse-dense, and dense modes – Secondary addressing – Static routes – Local proxy ARP – Border Gateway Protocol (BGP) – Classless interdomain routing (CIDR) • Quality of service (QoS) features: – Mul
Chapter 1 ML-Series Card Overview ML-Series Feature List – Transaction Language 1 (TL1) • System features: – Automatic field programmable gate array (FPGA) Upgrade – Network Equipment Building Systems 3 (NEBS3) compliant – Multiple microcode images • CTC features: – Framing Mode Provisioning – Standard STS/STM and VCAT circuit provisioning for POS virtual ports – SONET/SDH alarm reporting for path alarms and other ML-Series card specific alarms, including RPR-WRAP – Raw port statistics – Standard inven
C H A P T E R 2 CTC Operations This chapter covers Cisco Transport Controller (CTC) operations of the ML-Series card. All operations described in the chapter take place at the card-level view of CTC. CTC shows provisioning information and statistics for both the Ethernet and packet-over-SONET/SDH (POS) ports of the ML-Series card. For the ML-Series cards, CTC manages SONET/SDH alarms and provisions STS/STM circuits in the same manner as other ONS 15454 SONET/SDH traffic cards.
Chapter 2 CTC Operations Displaying ML-Series Ethernet Ports Provisioning Information on CTC Table 2-1 ML-Series POS and Ethernet Statistics Fields and Buttons Button Description Refresh Manually refreshes the statistics. Baseline Resets the software counters (in that particular CTC client only) temporarily to zero without affecting the actual statistics on the card. From that point on, only counters displaying the change from the temporary baseline are displayed by this CTC client.
Chapter 2 CTC Operations Displaying ML-Series POS Ports Provisioning Information on CTC Table 2-2 CTC Display of Ethernet Port Provisioning Status (continued) Column Description ML1000-2 Flow Control Flow control mode negotiated with peer Asymmetrical, Symmetrical device. These values are displayed but Symmetrical or or None not configureable in CTC. None Symmetrical or None Optics Small form-factor pluggable (SFP) physical media type.
Chapter 2 CTC Operations Provisioning Card Mode Note The port name field configured in CTC and the port name configured in Cisco IOS are independent of each other. The name for the same port under Cisco IOS and CTC does not match, unless the same name is used to configure the port name in both CTC and Cisco IOS. Provisioning Card Mode The card mode provisioning window shows the mode currently configured on the ML-Series card and allows the user to change it to either HDLC, GFP-F, or 802.17 RPR.
Chapter 2 CTC Operations Provisioning SONET/SDH Circuits Caution Do not attempt to use current FPGA images with an earlier CTC software release. Provisioning SONET/SDH Circuits CTC provisions and edits STS/STM level circuits for the two virtual SONET/SDH ports of the ML-Series card in the same manner as it provisions other ONS 15454 SONET/SDH OC-N cards. The ONS 15454 ML-Series card supports both contiguous concatenation (CCAT) and virtual concatenation (VCAT) circuits.
Chapter 2 CTC Operations J1 Path Trace Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 3 Initial Configuration This chapter describes the initial configuration of the ML-Series card and contains the following major sections: • Hardware Installation, page 3-1 • Cisco IOS on the ML-Series Card, page 3-2 • Startup Configuration File, page 3-7 • Multiple Microcode Images, page 3-11 • Changing the Working Microcode Image, page 3-12 • Cisco IOS Command Modes, page 3-13 • Using the Command Modes, page 3-15 Hardware Installation This section lists hardware installation t
Chapter 3 Initial Configuration Cisco IOS on the ML-Series Card Cisco IOS on the ML-Series Card The Cisco IOS software image used by the ML-Series card is not permanently stored on the ML-Series card but in the flash memory of the TCC2/TCC2P card. During a hard reset, when a card is physically removed and reinserted or power is otherwise lost to the card, the Cisco IOS software image is downloaded from the flash memory of the TCC2/TCC2P to the memory cache of the ML-Series card.
Chapter 3 Initial Configuration Telnetting to the Node IP Address and Slot Number Figure 3-1 CTC IOS Window Telnetting to the Node IP Address and Slot Number Users can telnet to the Cisco IOS CLI using the IP address and the slot number of the ONS 15454 SONET/SDH plus 2000. Note A Cisco IOS startup configuration file must be loaded and the ML-Series card must be installed and initialized prior to telnetting to the IP address and slot number plus 2000.
Chapter 3 Initial Configuration Telnetting to a Management Port Figure 3-2 CTC Node View Showing IP Address and Slot Number 131940 Node IP address Step 3 Use the IP address and the total of the slot number plus 2000 as the Telnet address in your preferred communication program. For example, for an IP address of 10.92.18.124 and Slot 13, you would enter or telnet 10.92.18.124 2013.
Chapter 3 Initial Configuration ML-Series IOS CLI Console Port RJ-11 to RJ-45 Console Cable Adapter Due to space limitations on the ML-Series card faceplate, the console port is an RJ-11 modular jack instead of the more common RJ-45 modular jack. Cisco supplies an RJ-11 to RJ-45 console cable adapter (P/N 15454-CONSOLE-02) with each ML-Series card. After connecting the adapter, the console port functions like the standard Cisco RJ-45 console port. Figure 3-3 shows the RJ-11 to RJ-45 console cable adapter.
Chapter 3 Initial Configuration ML-Series IOS CLI Console Port Step 3 Insert the RJ-11 modular plug end of the supplied console cable adapter into the RJ-11 serial console port, labeled CONSOLE, on the ML-Series card faceplate. Figure 3-4 shows the ML1000-2 faceplate with console port. For the ML100T-12 and ML100X-8, the console port is at the bottom of the card faceplate.
Chapter 3 Initial Configuration Startup Configuration File Startup Configuration File The ML-Series card needs a startup configuration file in order to configure itself beyond the default configuration when the card is reset. If no startup configuration file exists in the TCC2/TCC2P flash memory, then the card boots up to a default configuration.
Chapter 3 Initial Configuration Manually Creating a Startup Configuration File Through the Serial Console Port Passwords There are two types of passwords that you can configure for an ML-Series card: an enable password and an enable secret password. For maximum security, make the enable password different from the enable secret password. • Enable password—The enable password is a non-encrypted password. It can contain any number of uppercase and lowercase alphanumeric characters.
Chapter 3 Initial Configuration CTC and the Startup Configuration File Command Purpose Step 7 Router(config-if)# no shutdown Enables the interface. Step 8 Router(config-if)# exit Router(config)# Returns to global configuration mode. Step 9 Router(config)# line vty line-number Router(config-line)# Activates line configuration mode for virtual terminal connections. Commands entered in this mode control the operation of Telnet sessions to the ML-Series card.
Chapter 3 Initial Configuration CTC and the Startup Configuration File If the ML-Series card is booted up prior to the loading of the Cisco IOS startup configuration file into TCC2/TCC2P card flash, then the ML-Series card must be reset to use the Cisco IOS startup configuration file or the user can issue the command copy start run at the Cisco IOS CLI to configure the ML-Series card to use the Cisco IOS startup configuration file.
Chapter 3 Initial Configuration Multiple Microcode Images Note A standard ONS 15454 SONET/SDH database restore reinstalls the Cisco IOS startup config file on the TCC2/TCC2P, but does not implement the Cisco IOS startup config on the ML-Series. See the “Database Restore of the Startup Configuration File” section on page 3-11 for additional information. Database Restore of the Startup Configuration File The ONS 15454 SONET/SDH includes a database restoration feature.
Chapter 3 Initial Configuration Changing the Working Microcode Image Caution Configuring topology discovery or shortest path load balancing on an ML-Series card with the SW-RPR microcode image disables support for Cisco Proprietary RPR DRPRI. Table 3-2 Microcode Image Feature Comparison Features Base Enhanced EoMPLS SW-RPR 802.
Chapter 3 Initial Configuration Cisco IOS Command Modes Step 1 Command Purpose Router(config)# microcode {base | enhanced | fail system-reload | mpls | spr} Configures the ML-Series card with the selected microcode image: base—(Default) Enables base features only. Base features include Multicast routing and IP fragmentation. enhanced—Enables ERMS, enhanced packet statistics, and enhanced DRPRI. Disables multicast routing and IP fragmentation.
Chapter 3 Initial Configuration Cisco IOS Command Modes Table 3-3 describes the most commonly used modes, how to enter the modes, and the resulting system prompts. The system prompt helps you identify which mode you are in and, therefore, which commands are available to you. Note Table 3-3 When a process makes unusually heavy demands on the CPU of the ML-Series card, it may impair CPU response time and cause a CPUHOG error message to appear on the console.
Chapter 3 Initial Configuration Using the Command Modes commands, such as show commands, which show the current configuration status, and clear commands, which clear counters or interfaces. The EXEC commands are not saved across reboots of the ML-Series card. The configuration modes allow you to make changes to the running configuration. If you later save the configuration, these commands are stored across ML-Series card reboots. You must start in global configuration mode.
Chapter 3 Initial Configuration Getting Help Tip If you are having trouble entering a command, check the system prompt, and enter the question mark (?) for a list of available commands. You might be in the wrong command mode or using incorrect syntax. You can press Ctrl-Z or type end in any mode to immediately return to privileged EXEC (enable) mode, instead of entering exit, which returns you to the previous mode. Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 4 Configuring Interfaces This chapter describes basic interface configuration for the ML-Series card to help you get your ML-Series card up and running. Advanced packet-over-SONET/SDH (POS) interface configuration is covered in Chapter 5, “Configuring POS.” For more information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication.
Chapter 4 Configuring Interfaces MAC Addresses MAC Addresses Every port or device that connects to an Ethernet network needs a MAC address. Other devices in the network use MAC addresses to locate specific ports in the network and to create and update routing tables and data structures. To find MAC addresses for a device, use the show interfaces command, as follows: Router# sh interfaces fastEthernet 0 FastEthernet0 is up, line protocol is up Hardware is epif_port, address is 0005.9a39.6634 (bia 0005.9a39.
Chapter 4 Configuring Interfaces Basic Interface Configuration Basic Interface Configuration The following general configuration instructions apply to all interfaces. Before you configure interfaces, develop a plan for a bridge or routed network. To configure an interface, do the following: Step 1 Enter the configure EXEC command at the privileged EXEC prompt to enter global configuration mode.
Chapter 4 Configuring Interfaces Basic Fast Ethernet, Gigabit Ethernet, and POS Interface Configuration Basic Fast Ethernet, Gigabit Ethernet, and POS Interface Configuration ML-Series cards support Fast Ethernet, Gigabit Ethernet, and POS interfaces. This section provides some examples of configurations for all interface types.
Chapter 4 Configuring Interfaces Configuring the Fast Ethernet Interfaces for the ML100X-8 Step 5 Command Purpose Router(config-if)# flowcontrol send {on | off | desired} (Optional) Sets the send flow control value for an interface. Flow control works only with port-level policing. ML-Series card Fast Ethernet port flow control is IEEE 802.3x compliant.
Chapter 4 Configuring Interfaces Configuring the Gigabit Ethernet Interface for the ML1000-2 Step 3 Command Purpose Router(config-if)# flowcontrol send {on | off | desired} (Optional) Sets the send flow control value for an interface. Flow control works only with port-level policing. ML-Series card Fast Ethernet port flow control is IEEE 802.3x compliant.
Chapter 4 Configuring Interfaces Configuring Gigabit Ethernet Remote Failure Indication (RFI) Command Purpose Step 6 Router(config)# end Returns to privileged EXEC mode. Step 7 Router# copy running-config startup-config (Optional) Saves configuration changes to TCC2/TCC2P flash database. Example 4-2 shows how to do an initial configuration of a Gigabit Ethernet interface with autonegotiation and an IP address.
Chapter 4 Configuring Interfaces Monitoring and Verifying Gigabit Ethernet Remote Failure Indication (RFI) Router# copy running-config startup-config Monitoring and Verifying Gigabit Ethernet Remote Failure Indication (RFI) After RFI is configured, you can verify that RFI is enabled by using the global command show running configuration. Example 4-4 shows the output from this command, and the “rfi auto” line under each of the Gigabit Ethernet port’s output signifies RFI is enabled on these ports.
Chapter 4 Configuring Interfaces Monitoring and Verifying Gigabit Ethernet Remote Failure Indication (RFI) ! interface GigabitEthernet1 no ip address rfi auto Example 4-5 show controller Command Output for RFI on near-end card with no faults detected Near_End# show controller gigabit ethernet 0 IF Name: GigabitEthernet0 Port Status UP Port rxLosState Signal present Remote Fault Indication 00 (no error) Local Fault Indication 00 (no error) Port 0 Gmac Loopback false SFP EEPROM information ---------------
Chapter 4 Configuring Interfaces Configuring the POS Interfaces (ML100T-12, ML100X-8 and ML1000-2) pkts_error_giants pkts_good_runts pkts_error_runts pkts_ucast pkts_mcast pkts_bcast Rx Sync Loss Overruns FCS_errors GMAC drop count Symbol error Rx Pause frames 0 0 0 0 5485 0 0 0 0 0 0 0 MAC Transmit Counters 5d00h: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down 5d00h: %ETHERCHAN-5-MEMREMOVED: GigabitEthernet0 taken out of port-channel1 5d00h: %LINEPROTO-5-UPDOWN: Line protocol on Inter
Chapter 4 Configuring Interfaces CRC Threshold Configuration To configure the IP address, bridge group, or encapsulation for the POS interface, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface pos number Activates interface configuration mode to configure the POS interface. Step 2 Router(config-if)# {ip address ip-address subnet-mask | bridge-group bridge-group-number} Sets the IP address and subnet mask.
Chapter 4 Configuring Interfaces Monitoring Operations on the Fast Ethernet and Gigabit Ethernet Interfaces Command Purpose Step 3 Router(config)#int pos0 Router(config-if)#trigger crc-error delay Sets the number of consecutive minutes for which excessive CRC errors should be seen to raise an excessive CRC indication. The valid values are from 3 minutes to 10 minutes. Default is 10minutes.
Chapter 4 Configuring Interfaces Monitoring Operations on the Fast Ethernet and Gigabit Ethernet Interfaces Enter the show controller command to display information about the Fast Ethernet controller chip. Example 4-9 shows the output from the show controller command, which shows statistics including initialization block information.
Chapter 4 Configuring Interfaces Monitoring Operations on the Fast Ethernet and Gigabit Ethernet Interfaces Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 5 Configuring POS This chapter describes advanced packet-over-SONET/SDH (POS) interface configuration for the ML-Series card. Basic POS interface configuration is included in Chapter 4, “Configuring Interfaces.” For more information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication. POS operation on ONS Ethernet cards, including the ML-Series card, is described in Chapter 20, “POS on ONS Ethernet Cards.
Chapter 5 Configuring POS VCAT Both SONET and SDH have a hierarchy of signaling speeds. Multiple lower level signals can be multiplexed together to form higher level signals. For example, three STS-1 signals can be multiplexed together to form a STS-3 signal, and four STM-1 signals can be multiplexed together to form a STM-4 signal. SONET circuit sizes are defined as STS-n, where n is a multiple of 51.84 Mbps and n is equal to or greater than 1.
Chapter 5 Configuring POS SW-LCAS Table 5-2 VCAT Circuit Sizes Supported by ML100T-12, ML100X-8, and ML1000-2 Cards SONET VCAT Circuit Size SDH VCAT Circuit Size STS-1-2v VC-3-2v STS-3c-2v VC-4-2v STS-12c-2v VC-4-4c-2v For step-by-step instructions on configuring an ML-Series card SONET VCAT circuit, refer to the “Create Circuits and VT Tunnels” chapter of the Cisco ONS 15454 Procedure Guide.
Chapter 5 Configuring POS Framing Mode, Encapsulation, and CRC Support Framing Mode, Encapsulation, and CRC Support The ML-Series cards on the ONS 15454 and ONS 15454 SDH support two modes of the POS framing mechanism, GFP-F framing and HDLC framing (default). The framing mode, encapsulation, and CRC size on source and destination POS ports must match for a POS circuit to function properly.
Chapter 5 Configuring POS Framing Mode, Encapsulation, and CRC Support Step 3 Command Purpose Router(config-if)# encapsulation type Sets the encapsulation type. Valid values are: • hdlc—Cisco HDLC • lex—(default) LAN extension, special encapsulation for use with Cisco ONS Ethernet line cards. When the lex keyword is used with GFP-F framing it is standard Mapped Ethernet over GFP-F according to ITU-T G.7041.
Chapter 5 Configuring POS SONET/SDH Alarms Command Purpose Step 3 Router(config-if)# end Returns to the privileged EXEC mode. Step 4 Router# copy running-config startup-config (Optional) Saves configuration changes to NVRAM. Table 5-4 shows the default MTU sizes.
Chapter 5 Configuring POS SONET/SDH Alarms CTC/TL1Alarms has sophisticated SONET/SDH alarm reporting capabilities. As a card in the ONS node, the Configuring SONET/SDH ML-Series card reports alarms to CTC/TL-1 like any other ONS card. On the ONS 15454 SONET, the ML-Series card reports alarms inthe thereporting Alarms of panel of CTC.
Chapter 5 Configuring POS C2 Byte and Scrambling To configure path alarms as triggers and specify a delay, perform the following steps beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface pos number Enters interface configuration mode and specifies the POS interface to configure.
Chapter 5 Configuring POS Monitoring and Verifying POS Table 5-5 C2 Byte and Scrambling Default Values (continued) Signal Label SONET/SDH Payload Contents 0x16 Cisco HDLC or PPP/BCP with scrambling 0x1B GFP-F Third-Party POS Interfaces C2 Byte and Scrambling Values If a Cisco POS interface fails to come up when connected to a third-party device, confirm the scrambling and cyclic redundancy check (CRC) settings as well as the advertised value in the C2 byte.
Chapter 5 Configuring POS Monitoring and Verifying POS Concatenation: CCAT Alarms reportable to CLI: PAIS PLOP PUNEQ PTIM PPLM ENCAP PRDI PPDI BER_SF_B3 BER_SD_B3 VCAT_OOU_TPT LOM SQM Link state change defects: PAIS PLOP PUNEQ PTIM PPLM ENCAP PRDI PPDI BER_SF_B3 Link state change time : 200 (msec) *************** Path *************** Circuit state: IS PAIS = 0 PLOP = 0 PRDI = 0 PTIM = 0 PPLM = 0 PUNEQ = 0 PPDI = 0 PTIU = 0 BER_SF_B3 = 0 BER_SD_B3 = 0 BIP(B3) = 0 REI = 0 NEWPTR = 0 PSE = 0 NSE = 0 ENCAP = 0
Chapter 5 Configuring POS POS Configuration Examples Received 0 broadcasts (0 IP multicast) 0 runts, 0 giants, 0 throttles 0 parity 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 applique, 0 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions POS Configuration Examples The following sec
Chapter 5 Configuring POS ML-Series Card to Cisco 12000 GSR-Series Router log-adjacency-changes network 192.168.1.0 0.0.0.255 area 0 network 192.168.2.0 0.0.0.255 area 0 Example 5-4 shows the commands associated with the configuration of ML Series B. Example 5-4 ML-Series Card B Configuration hostname ML_Series_B ! interface FastEthernet0 ip address 192.168.3.1 255.255.255.0 ! interface POS0 ip address 192.168.2.2 255.255.255.0 crc 32 pos flag c2 1 ! router ospf 1 log-adjacency-changes network 192.168.
Chapter 5 Configuring POS ML-Series Card to G-Series Card crc 32 ! router ospf 1 log-adjacency-changes network 192.168.1.0 0.0.0.255 area 0 network 192.168.2.0 0.0.0.255 area 0 Example 5-6 shows the commands associated with the configuration of the GSR-12000. Example 5-6 GSR-12000 Configuration hostname GSR ! interface FastEthernet1/0 ip address 192.168.3.1 255.255.255.0 ! interface POS2/0 ip address 192.168.2.2 255.255.255.
Chapter 5 Configuring POS ML-Series Card to ONS 15310 ML-100T-8 Card Figure 5-3 ML-Series Card to G-Series Card POS Configuration ONS 15454 with ML100T-12 ONS 15454 with G-Series ML_Series_A pos 0 192.168.2.1 SONET/SDH fast ethernet 0 192.168.1.1 83125 Ethernet Example 5-7 shows the commands associated with the configuration of ML-Series card A. Example 5-7 ML-Series Card A Configuration hostname ML_Series_A ! interface FastEthernet0 ip address 192.168.1.1 255.255.255.
Chapter 5 Configuring POS ML-Series Card to ONS 15310 ML-100T-8 Card Example 5-8 shows the commands associated with the configuration of ML-Series card A. Example 5-8 ML-Series Card A Configuration hostname ML_Series_A ! interface FastEthernet0 ip address 192.168.1.1 255.255.255.0 ! interface POS0 ip address 192.168.2.1 255.255.255.0 crc 32 ! router ospf 1 log-adjacency-changes network 192.168.1.0 0.0.0.255 area 0 network 192.168.2.0 0.0.0.
Chapter 5 Configuring POS ML-Series Card to ONS 15310 ML-100T-8 Card Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 6 Configuring Bridges This chapter describes how to configure bridging for the ML-Series card. For more information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication.
Chapter 6 Configuring Bridges Configuring Basic Bridging Spanning tree is not mandatory for an ML-Series card bridge group. But if it is configured, a separate spanning-tree process runs for each configured bridge group. A bridge group establishes a spanning tree based on the bridge protocol data units (BPDUs) it receives on only its member interfaces.
Chapter 6 Configuring Bridges Monitoring and Verifying Basic Bridging Figure 6-1 Bridging Example ONS 15454 with ML100T-12 ONS 15454 with ML100T-12 ML_Series_B ML_Series_A pos 0 pos 0 SONET/SDH fast ethernet 0 78972 fast ethernet 0 Example 6-1 Router A Configuration bridge 1 protocol ieee ! ! interface FastEthernet0 no ip address bridge-group 1 ! interface POS0 no ip address crc 32 bridge-group 1 pos flag c2 1 Example 6-2 Router B Configuration bridge 1 protocol ieee ! ! interface FastEtherne
Chapter 6 Configuring Bridges Monitoring and Verifying Basic Bridging Command Purpose Step 1 Router# clear bridge bridge-group-number Removes any learned entries from the forwarding database of a particular bridge group, clears the transmit, and receives counts for any statically configured forwarding entries. Step 2 Router# show bridge {bridge-group-number | interface-address} Displays classes of entries in the bridge forwarding database.
Chapter 6 Configuring Bridges Transparent Bridging Modes of Operation Hello Time Bridge ID 2 sec Max Age 20 sec Forward Delay 15 sec Priority 32769 (priority 32768 sys-id-ext 1) Address 0005.9a39.6634 Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Aging Time 300 Interface ---------------Fa0 PO0 Role ---Desg Desg Sts --FWD FWD Cost --------19 9 Prio.Nbr -------128.3 128.
Chapter 6 Configuring Bridges No IP Routing Mode • All the interfaces and subinterface belonging to the same bridge-group need consistent configuration with regard to IP addresses. Either all of the bridge group’s interfaces should be configured with IP addresses or none of the bridge group’s interfaces should be configured with IP addresses. Example 6-4 shows ML-Series card interfaces configured in a bridge group with no IP addresses.
Chapter 6 Configuring Bridges Bridge CRB Mode • An input interface or subinterface configured with only an IP address discards all packets, except packets with the destination MAC and IP address of the input interface, which are processed by Cisco IOS. This is not a valid configuration. • An input interface or subinterface configured with both an IP address and a bridge group bridges all packets, except packets sent to the input interface MAC address.
Chapter 6 Configuring Bridges Bridge IRB Mode Example 6-8 shows ML-Series card interfaces configured with IP addresses and multiple bridge groups. Example 6-8 bridge bridge bridge bridge IP Addresses and Multiple Bridge Group crb 1 proto rstp 1 route ip 2 proto rstp int f0 ip address 10.10.10.2 255.255.255.0 bridge-group 1 int pos 0 ip address 20.20.20.2 255.255.255.
Chapter 6 Configuring Bridges Bridge IRB Mode Example 6-9 Bridge irb with Routing and Bridging Enabled bridge irb bridge 1 proto rstp bridge 1 route ip int f0 bridge-group 1 int pos 0 bridge-group 1 int bvi 1 ip address 10.10.10.1 255.255.255.0 Example 6-10 shows ML-Series card interfaces configured with both an IP address and a bridge-group. IP routing is enabled and IP bridging is disabled.
Chapter 6 Configuring Bridges Bridge IRB Mode Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 7 Configuring STP and RSTP This chapter describes the IEEE 802.1D Spanning Tree Protocol (STP) and the ML-Series implementation of the IEEE 802.1W Rapid Spanning Tree Protocol (RSTP). It also explains how to configure STP and RSTP on the ML-Series card. This chapter consists of these sections: • STP Features, page 7-1 • RSTP, page 7-9 • Interoperability with IEEE 802.
Chapter 7 Configuring STP and RSTP STP Overview STP Overview STP is a Layer 2 link management protocol that provides path redundancy while preventing loops in the network. For a Layer 2 Ethernet network to function properly, only one active path can exist between any two stations. Spanning-tree operation is transparent to end stations, which cannot detect whether they are connected to a single LAN segment or a switched LAN of multiple segments.
Chapter 7 Configuring STP and RSTP Election of the Root Switch When a switch receives a configuration BPDU that contains superior information (lower bridge ID, lower path cost, etc.), it stores the information for that port. If this BPDU is received on the root port of the switch, the switch also forwards it with an updated message to all attached LANs for which it is the designated switch.
Chapter 7 Configuring STP and RSTP Bridge ID, Switch Priority, and Extended System ID Bridge ID, Switch Priority, and Extended System ID The IEEE 802.1D standard requires that each switch has an unique bridge identifier (bridge ID), which determines the selection of the root switch. Because each VLAN is considered as a different logical bridge with PVST+, the same switch must have as many different bridge IDs as VLANs configured on it.
Chapter 7 Configuring STP and RSTP Spanning-Tree Interface States Figure 7-1 Spanning-Tree Topology ONS 15454 with ML100T-12 DP A DP ONS 15454 with ML100T-12 D DP RP DP DP DP B ONS 15454 with ML100T-12 RP DP C ONS 15454 with ML100T-12 83803 RP RP = root port DP = designated port When the spanning-tree topology is calculated based on default parameters, the path between source and destination end stations in a switched network might not be ideal.
Chapter 7 Configuring STP and RSTP Spanning-Tree Interface States Figure 7-2 illustrates how an interface moves through the states. Figure 7-2 Spanning-Tree Interface States Power-on initialization Blocking state Listening state Disabled state Forwarding state 43569 Learning state When you power up the switch, STP is enabled by default, and every interface in the switch, VLAN, or network goes through the blocking state and the transitory states of listening and learning.
Chapter 7 Configuring STP and RSTP Spanning-Tree Interface States 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 determines that the interface should participate in frame forwarding.
Chapter 7 Configuring STP and RSTP Spanning-Tree Address Management 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. The ML-Series card switches supported BPDUs (0x0180C2000000 and 01000CCCCCCD) when they are being tunneled via the protocol tunneling feature. STP and IEEE 802.
Chapter 7 Configuring STP and RSTP Accelerated Aging to Retain Connectivity Accelerated Aging to Retain Connectivity The default for aging dynamic addresses is 5 minutes, which is the default setting of the bridge bridge-group-number aging-time global configuration command. However, a spanning-tree reconfiguration can cause many station locations to change.
Chapter 7 Configuring STP and RSTP Rapid Convergence • Root port—Provides the best path (lowest cost) when the switch forwards packets to the root switch. • Designated port—Connects to the designated switch, which incurs the lowest path cost when forwarding packets from that LAN to the root switch. The port through which the designated switch is attached to the LAN is called the designated port. • Alternate port—Offers an alternate path toward the root switch to that provided by the current root port.
Chapter 7 Configuring STP and RSTP Rapid Convergence • 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 7 Configuring STP and RSTP Synchronization of Port Roles Figure 7-4 Proposal and Agreement Handshaking for Rapid Convergence ONS 15454 with ML100T-12 Proposal Switch A ONS 15454 with ML100T-12 Switch B Root F DP Agreement Switch A ONS 15454 with ML100T-12 F RP Switch B F DP Switch A Proposal Switch B Root F DP Switch A ONS 15454 with ML100T-12 F F RP DP Switch B DP = designated port RP = root port F = forwarding ONS 15454 with ML100T-12 Switch B Agreement ONS 15454 with ML100T-12
Chapter 7 Configuring STP and RSTP Bridge Protocol Data Unit Format and Processing Figure 7-5 Sequence of Events During Rapid Convergence 4. Agreement 1. Proposal 5. Forward Edge port 8. Agreement 3. Block 11. Forward 6. Proposal 7. Proposal Root port Designated port 10. Agreement 74008 2. Block 9. Forward Bridge Protocol Data Unit Format and Processing The RSTP BPDU format is the same as the IEEE 802.1D BPDU format except that the protocol version is set to 2.
Chapter 7 Configuring STP and RSTP Topology Changes The RSTP does not have a separate topology change notification (TCN) BPDU. It uses the topology change (TC) flag to show the topology changes. However, for interoperability with IEEE 802.1D switches, the RSTP switch processes and generates TCN BPDUs. The learning and forwarding flags are set according to the state of the sending port. Processing Superior BPDU Information If a port receives superior root information (lower bridge ID, lower path cost, etc.
Chapter 7 Configuring STP and RSTP Interoperability with IEEE 802.1D STP • Protocol migration—For backward compatibility with IEEE 802.1D switches, RSTP selectively sends IEEE 802.1D configuration BPDUs and TCN BPDUs on a per-port basis. When a port is initialized, the timer is started (which specifies the minimum time during which RSTP BPDUs are sent), and RSTP BPDUs are sent. While this timer is active, the switch processes all BPDUs received on that port and ignores the protocol type.
Chapter 7 Configuring STP and RSTP Default STP and RSTP Configuration Default STP and RSTP Configuration Table 7-5 shows the default STP and RSTP configuration. Table 7-5 Default STP and RSTP Configuration Feature Default Setting Enable state Up to 255 spanning-tree instances can be enabled.
Chapter 7 Configuring STP and RSTP Configuring the Root Switch Beginning in privileged EXEC mode, follow these steps to disable STP or RSTP on a per-VLAN basis: Command Purpose Step 1 Router# configure terminal Enters the global configuration mode. Step 2 Router(config)# interface interface-id Enters the interface configuration mode. Step 3 Router(config-if)# bridge-group bridge-group-number spanning disabled Disables STP or RSTP on a per-interface basis.
Chapter 7 Configuring STP and RSTP Configuring the Path Cost Step 3 Command Purpose Router(config-if)# bridge-group bridge-group-number priority-value Configures the port priority for an interface that is an access port. For the priority-value, the range is 0 to 255; the default is 128 in increments of 16. The lower the number, the higher the priority. Step 4 Return to privileged EXEC mode.
Chapter 7 Configuring STP and RSTP Configuring the Switch Priority of a Bridge Group Configuring the Switch Priority of a Bridge Group You can configure the switch priority and make it more likely that the switch will be chosen as the root switch. Beginning in privileged EXEC mode, follow these steps to configure the switch priority of a bridge group: Command Purpose Step 1 Router# configure terminal Enters the global configuration mode.
Chapter 7 Configuring STP and RSTP Configuring the Forwarding-Delay Time for a Bridge Group Configuring the Forwarding-Delay Time for a Bridge Group Beginning in privileged EXEC mode, follow these steps to configure the forwarding-delay time for a bridge group: Command Purpose Step 1 Router# configure terminal Enters global configuration mode. Step 2 Router(config)# bridge bridge-group-number forward-time seconds Configures the forward time of a VLAN.
Chapter 7 Configuring STP and RSTP Verifying and Monitoring STP and RSTP Status Table 7-6 Note Commands for Displaying Spanning-Tree Status (continued) Command Purpose ML_Series# show spanning-tree interface interface-id Displays STP or RSTP information for the specified interface. ML_Series# show spanning-tree summary [totals] Displays a summary of port states or displays the total lines of the STP or RSTP state section.
Chapter 7 Configuring STP and RSTP Verifying and Monitoring STP and RSTP Status Port 20 (POS0) of Bridge group 1 is forwarding Port path cost 3, Port priority 128, Port Identifier 128.20. Designated root has priority 32769, address 0005.9a39.6634 Designated bridge has priority 32769, address 0005.9a39.6634 Designated port id is 128.
C H A P T E R 8 Configuring VLANs This chapter describes VLAN configurations for the ML-Series card. It describes how to configure IEEE 802.1Q VLAN encapsulation. For more information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication. This chapter contains the following major sections: Note • Understanding VLANs, page 8-1 • Configuring IEEE 802.1Q VLAN Encapsulation, page 8-2 • IEEE 802.
Chapter 8 Configuring VLANs Configuring IEEE 802.1Q VLAN Encapsulation ML-Series switching supports up to 900 VLAN subinterfaces per card (for example, 200 VLANs on four interfaces uses 800 VLAN subinterfaces). A maximum of 255 logical VLANs can be bridged per card (limited by the number of bridge-groups). Each VLAN subinterface can be configured for any VLAN ID in the full 1 to 4095 range. Figure 8-1 shows a network topology in which two VLANs span two ONS 15454s with ML-Series cards.
Chapter 8 Configuring VLANs IEEE 802.1Q VLAN Configuration Command Purpose Step 5 Router(config-subif)# encap dot1q vlan-number Sets the encapsulation on the VLAN to IEEE 802.1Q. Step 6 Router(config-subif)# bridge-group bridge-group-number Assigns a network interface to a bridge group. Step 7 Router(config-subif)# end Returns to privileged EXEC mode. Step 8 Router# copy running-config startup-config (Optional) Saves your configuration changes to NVRAM.
Chapter 8 Configuring VLANs IEEE 802.1Q VLAN Configuration Figure 8-2 Bridging IEEE 802.1Q VLANs ONS 15454 with ML100T-12 ONS 15454 with ML100T-12 Router_B Router_A POS 0 POS 0 SONET/SDH Native VLAN 1 Fast Ethernet 0.1 802.1.Q Fast Ethernet 0.2 Fast Ethernet 0.4 802.1.Q Fast Ethernet 0.2 Fast Ethernet 0.4 Switch Switch VLAN 4 VLAN 2 Host station Host station VLAN 4 VLAN 2 Fast Ethernet 0.3 VLAN 3 Host station Fast Ethernet 0.
Chapter 8 Configuring VLANs Monitoring and Verifying VLAN Operation pos flag c2 1 ! interface POS0.1 encapsulation dot1Q bridge-group 1 ! interface POS0.2 encapsulation dot1Q bridge-group 2 ! interface POS0.3 encapsulation dot1Q bridge-group 3 ! interface POS0.4 encapsulation dot1Q bridge-group 4 1 native 2 3 4 Monitoring and Verifying VLAN Operation After the VLANs are configured on the ML-Series card, you can monitor their operation by entering the privileged EXEC command show vlans vlan-id.
Chapter 8 Configuring VLANs Monitoring and Verifying VLAN Operation Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Virtual private networks (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 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding IEEE 802.1Q Tunneling Figure 9-1 IEEE 802.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding IEEE 802.1Q Tunneling Normal, IEEE 802.1Q, and IEEE 802.1Q-Tunneled Ethernet Packet Formats Source address Destination Length/ address EtherType DA SA Len/Etype DA SA Etype DA SA Etype Frame Check Sequence Data Tag Tag FCS Len/Etype Etype Tag Original Ethernet frame Data Len/Etype FCS IEE 802.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring IEEE 802.1Q Tunneling Configuring IEEE 802.1Q Tunneling This section includes the following information about configuring IEEE 802.1Q tunneling: Note • IEEE 802.1Q Tunneling and Compatibility with Other Features, page 9-4 • Configuring an IEEE 802.1Q Tunneling Port, page 9-4 • IEEE 802.1Q Example, page 9-5 By default, IEEE 802.1Q tunneling is not configured on the ML-Series. IEEE 802.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling IEEE 802.1Q Example Command Purpose Step 4 Router(config-if)# bridge-group number Assigns the tunnel port to a bridge-group. All traffic from the port (tagged and untagged) will be switched based on this bridge-group. Other members of the bridge-group should be VLAN subinterfaces on a provider trunk interface. Step 5 Router(config-if)# mode dot1q-tunnel Sets the interface as an IEEE 802.1Q tunnel port.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding VLAN-Transparent and VLAN-Specific Services ! interface POS0.2 encapsulation dot1Q 40 bridge-group 40 Example 9-2 Router B Configuration bridge 30 protocol ieee bridge 40 protocol ieee ! ! interface FastEthernet0 no ip routing no ip address mode dot1q-tunnel bridge-group 30 ! interface FastEthernet1 no ip address mode dot1q-tunnel bridge-group 40 ! interface POS0 no ip address crc 32 pos flag c2 1 ! interface POS0.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling VLAN-Transparent and VLAN-Specific Services Configuration Example Note VLAN-transparent service is also referred to as Ethernet Wire Service (EWS). VLAN-specific service is also referred to as QinQ tunneling trunk UNI in Metro Ethernet terminology. A VLAN-specific service on a subinterface coexists with the VLAN-transparent service, often IEEE 802.1Q tunneling, on a physical interface.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling VLAN-Transparent and VLAN-Specific Services Configuration Example bridge 30 protocol ieee ! ! interface GigabitEthernet0 no ip address no ip route-cache mode dot1q-tunnel bridge-group 10 bridge-group 10 spanning-disabled ! interface GigabitEthernet0.3 encapsulation dot1Q 30 no ip route-cache bridge-group 30 ! interface POS0 no ip address no ip route-cache crc 32 ! interface POS0.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Understanding Layer 2 Protocol Tunneling interface POS1 no ip address crc 32 ! interface POS1.1 encapsulation dot1Q 10 bridge-group 10 ! interface POS1.3 encapsulation dot1Q 30 bridge-group 30 Example 9-5 applies to ML-Series card C.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling • CDP discovers and shows information about the other Cisco devices connected through the service-provider network. • VTP provides consistent VLAN configuration throughout the customer network, propagating through the service provider to all switches. Layer 2 protocol tunneling can be used independently or to enhance IEEE 802.1Q tunneling. If protocol tunneling is not enabled on IEEE 802.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Layer 2 Protocol Tunneling Configuration Guidelines Table 9-2 Default Layer 2 Protocol Tunneling Configuration Feature Default Setting Layer 2 protocol tunneling Disabled for CDP, STP, and VTP. Class of service (CoS) value If a CoS value is configured on the interface for data packets, that value is the default used for Layer 2 PDUs. If none is configured, there is no default.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Configuring Layer 2 Tunneling Per-VLAN Command Purpose Step 1 Router# configuration terminal Enters global configuration mode. Step 2 Router(config)# bridge bridge-group-number protocol type Creates a bridge group number and specifies a protocol. Step 3 Router(config)# l2protocol-tunnel cos cos-value Associates a CoS value with the Layer 2 tunneling port. Valid numbers for a cos-value range from 0 to 7.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Monitoring and Verifying Tunneling Status Table 9-3 Commands for Monitoring and Maintaining Tunneling Command Purpose show dot1q-tunnel Displays IEEE 802.1Q tunnel ports on the switch. show dot1q-tunnel interface interface-id Verifies if a specific interface is a tunnel port. show l2protocol-tunnel Displays information about Layer 2 protocol tunneling ports. show vlan dot1q tag native Displays IEEE 802.
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling Monitoring and Verifying Tunneling Status Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 10 Configuring Link Aggregation This chapter describes how to configure link aggregation for the ML-Series cards, both EtherChannel and packet-over-SONET/SDH (POS) channel. For additional information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication.
Chapter 10 Configuring Link Aggregation Configuring EtherChannel Each ML100T-12 supports up to six FECs and one POS channel. Each ML100X-8 supports up to four FECs and one POS channel. A maximum of four Fast Ethernet ports can bundle into one Fast Ethernet Channel (FEC) and provide bandwidth scalability up to 400-Mbps full-duplex Fast Ethernet. Each ML1000-2 supports up to two port channels, including the POS channel.
Chapter 10 Configuring Link Aggregation EtherChannel Configuration Example For information on other configuration tasks for the EtherChannel, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.
Chapter 10 Configuring Link Aggregation Configuring POS Channel bridge-group 1 hold-queue 150 in ! interface FastEthernet 0 no ip address channel-group 1 ! interface FastEthernet 1 no ip address channel-group 1 ! interface POS 0 no ip routing no ip address crc 32 bridge-group 1 pos flag c2 1 Example 10-2 Switch B Configuration hostname Switch B ! bridge 1 protocol ieee ! interface Port-channel 1 no ip routing no ip address bridge-group 1 hold-queue 150 in ! interface FastEthernet 0 no ip address channel-g
Chapter 10 Configuring Link Aggregation POS Channel Configuration Example To create a POS channel interface, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface port-channel channel-number Creates the POS channel interface. You can configure one POS channel on the ML-Series card.
Chapter 10 Configuring Link Aggregation POS Channel Configuration Example Figure 10-2 POS Channel Example ML_Series A port-channel 1 bridge-group 1 ML_Series B pos 0 bridge-group 1 pos 0 SONET STS-N pos 1 bridge-group 1 port-channel 1 bridge-group 1 pos 1 bridge-group 1 83447 bridge-group 1 Example 10-3 Switch A Configuration bridge irb bridge 1 protocol ieee ! ! interface Port-channel1 no ip address no keepalive bridge-group 1 ! interface FastEthernet0 no ip address bridge-group 1 ! interface P
Chapter 10 Configuring Link Aggregation Understanding Encapsulation over EtherChannel or POS Channel pos flag c2 1 ! interface POS1 no ip address channel-group 1 crc 32 pos flag c2 1 Understanding Encapsulation over EtherChannel or POS Channel When configuring encapsulation over FEC, GEC, or POS, be sure to configure IEEE 802.1Q on the port-channel interface, not its member ports. However, certain attributes of port channel, such as duplex mode, need to be configured at the member port levels.
Chapter 10 Configuring Link Aggregation Encapsulation over EtherChannel Example Figure 10-3 Encapsulation over EtherChannel Example ONS 15454 with ML100T-12 Switch_A ONS 15454 with ML100T-12 Switch_B POS 0 Fast Ethernet 0 802.1Q Trunking VLANs 1 & 2 POS 0 Fast Ethernet 0 802.
Chapter 10 Configuring Link Aggregation Monitoring and Verifying EtherChannel and POS encapsulation dot1Q 2 bridge-group 2 Example 10-6 Switch B Configuration hostname Switch B ! bridge irb bridge 1 protocol ieee bridge 2 protocol ieee ! interface Port-channel1 no ip address hold-queue 150 in ! interface Port-channel1.1 encapsulation dot1Q 1 native bridge-group 1 ! interface Port-channel1.
Chapter 10 Configuring Link Aggregation Monitoring and Verifying EtherChannel and POS Encapsulation ARPA, loopback not set Keepalive set (10 sec) Unknown duplex, Unknown Speed ARP type: ARPA, ARP Timeout 04:00:00 No.
C H A P T E R 11 Configuring Networking Protocols This chapter describes how to configure the ML-Series card for supported IP routing protocols. It is intended to provide enough information for a network administrator to get the protocols up and running. However, this section does not provide in-depth configuration detail for each protocol. For detailed information, refer to the Cisco IOS IP and IP Routing Configuration Guide and the Cisco IOS IP and IP Routing Command Reference publications.
Chapter 11 Configuring Networking Protocols RIP RIP To configure the Routing Information Protocol (RIP), perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# router rip Enters router configuration mode, defines RIP as the routing protocol, and starts the RIP routing process.
Chapter 11 Configuring Networking Protocols BGP Step 1 Command Purpose Router(config)# router ospf process-ID Defines OSPF as the IP routing protocol. The process ID identifies a unique OSPF router process. This number is internal to the ML-Series card only; the process ID here does not have to match the process IDs on other routers. Step 2 Step 3 Router(config-router)# network net-address wildcard-mask area area-ID Router(config-router)# end Assigns an interface to a specific area.
Chapter 11 Configuring Networking Protocols Configuring IP Routing Command Purpose Step 1 Router# configure terminal Enters global configuration mode. Step 2 Router(config)# ip routing Enables IP routing (default). Step 3 Router(config)# router ip-routing-protocol Specifies an IP routing protocol. This step might include other commands, such as specifying the networks to route with the network (RIP) router configuration command.
Chapter 11 Configuring Networking Protocols Configuring RIP Using RIP, the switch sends routing information updates (advertisements) every 30 seconds. If a router does not receive an update from another router for 180 seconds or more, it marks the routes served by that router as unusable. If there is still no update after 240 seconds, the router removes all routing table entries for the nonupdating router. RIP uses hop counts to rate the value of different routes.
Chapter 11 Configuring Networking Protocols Configuring RIP Command Purpose Step 1 Router# configure terminal Enters global configuration mode. Step 2 Router(config)# ip routing Enables IP routing. (Required only if IP routing is disabled.) Step 3 Router(config)# router rip Enables a RIP routing process, and enters router configuration mode. Step 4 Router(config-router)# network network-number Associates a network with a RIP routing process. You can specify multiple network commands.
Chapter 11 Configuring Networking Protocols Configuring RIP Command Purpose Step 13 Router# show ip protocols Verifies your entries. Step 14 Router# copy running-config startup-config (Optional) Saves your entries in the configuration file. To turn off the RIP routing process, use the no router rip global configuration command. To display the parameters and current state of the active routing protocol process, use the show ip protocols privileged EXEC command (Example 11-2).
Chapter 11 Configuring Networking Protocols Configuring RIP Beginning in privileged EXEC mode, follow this procedure to configure RIP authentication on an interface: Command Purpose Step 1 Router# configure terminal Enters global configuration mode. Step 2 Router(config)# interface interface-id Enters interface configuration mode, and specifies the interface to configure. Step 3 Router(config-if)# ip rip authentication key-chain name-of-chain Enables RIP authentication.
Chapter 11 Configuring Networking Protocols Configuring OSPF Command Purpose Step 4 Router(config-if)# ip summary-address rip ip-address ip-network-mask Configures the IP address to be summarized and the IP network mask. Step 5 Router(config-if)# no ip split horizon Disables split horizon on the interface. Step 6 Router(config-if)# end Returns to privileged EXEC mode. Step 7 Router# show ip interface interface-id Verifies your entries.
Chapter 11 Configuring Networking Protocols Configuring OSPF Table 11-2 Default OSPF Configuration Feature Default Setting Interface parameters Cost: No default cost predefined. Retransmit interval: 5 seconds. Transmit delay: 1 second. Priority: 1. Hello interval: 10 seconds. Dead interval: 4 times the hello interval. No authentication. No password specified. MD5 authentication disabled. Area Authentication type: 0 (no authentication). Default cost: 1. Range: Disabled. Stub: No stub area defined.
Chapter 11 Configuring Networking Protocols Configuring OSPF Table 11-2 Default OSPF Configuration (continued) Feature Default Setting Timers shortest path first (spf) spf delay: 5 seconds. spf-holdtime: 10 seconds. Virtual link No area ID or router ID defined. Hello interval: 10 seconds. Retransmit interval: 5 seconds. Transmit delay: 1 second. Dead interval: 40 seconds. Authentication key: No key predefined. MD5: No key predefined.
Chapter 11 Configuring Networking Protocols Configuring OSPF Beginning in privileged EXEC mode, follow this procedure to enable OSPF: Command Purpose Step 1 Router# configure terminal Enters global configuration mode. Step 2 Router(config)# router ospf process-id Enables OSPF routing, and enters router configuration mode. The process ID is an internally used identification parameter that is locally assigned and can be any positive integer. Each OSPF routing process has a unique value.
Chapter 11 Configuring Networking Protocols Configuring OSPF OSPF Interface Parameters You can use the ip ospf interface configuration commands to modify interface-specific OSPF parameters. You are not required to modify any of these parameters, but some interface parameters (hello interval, dead interval, and authentication key) must be consistent across all routers in an attached network. If you modify these parameters, be sure all routers in the network have compatible values.
Chapter 11 Configuring Networking Protocols Configuring OSPF Command Purpose Step 11 Router(config-if)# ip ospf database-filter all out (Optional) Blocks flooding of OSPF LSA packets to the interface. By default, OSPF floods new LSAs over all interfaces in the same area, except the interface on which the LSA arrives. Step 12 Router(config-if)# end Returns to privileged EXEC mode. Step 13 Router# show ip ospf interface [interface-name] Displays OSPF-related interface information.
Chapter 11 Configuring Networking Protocols Configuring OSPF Route summarization is the consolidation of advertised addresses into a single summary route to be advertised by other areas. If network numbers are contiguous, you can use the area range router configuration command to configure the ABR to advertise a summary route that covers all networks in the range. Note The OSPF area router configuration commands are all optional.
Chapter 11 Configuring Networking Protocols Configuring OSPF Example 11-7 show ip ospf database and show ip ospf Privileged EXEC Command Ouputs Router# show ip ospf database OSPF Router with ID (192.168.3.1) (Process ID 1) Router Link States (Area 0) Link ID 192.168.2.1 192.168.3.1 ADV Router 192.168.2.1 192.168.3.1 Age 428 428 Seq# Checksum Link count 0x80000003 0x004AB8 2 0x80000003 0x006499 2 Net Link States (Area 0) Link ID 192.168.2.2 ADV Router 192.168.3.
Chapter 11 Configuring Networking Protocols Configuring OSPF • Domain Name Server (DNS) names for use in all OSPF show privileged EXEC command displays make it easier to identify a router than displaying it by router ID or neighbor ID. • Default metrics—OSPF calculates the OSPF metric for an interface according to the bandwidth of the interface.
Chapter 11 Configuring Networking Protocols Configuring OSPF Command Purpose Step 9 Router(config)# passive-interface type number (Optional) Suppresses the sending of hello packets through the specified interface. Step 10 Router(config)# timers spf spf-delay spf-holdtime (Optional) Configures route calculation timers. • spf-delay—Enter an integer from 0 to 65535. The default is 5 seconds; 0 means no delay. • spf-holdtime—Enter an integer from 0 to 65535.
Chapter 11 Configuring Networking Protocols Configuring OSPF Loopback Interface OSPF uses the highest IP address configured on the interfaces as its router ID. If this interface is down or removed, the OSPF process must recalculate a new router ID and resend all its routing information out of its interfaces. If a loopback interface is configured with an IP address, OSPF uses this IP address as its router ID, even if other interfaces have higher IP addresses.
Chapter 11 Configuring Networking Protocols Configuring EIGRP Configuring EIGRP Enhanced IGRP (EIGRP) is a Cisco proprietary enhanced version of the Interior Gateway Routing Protocol (IGRP). Enhanced IGRP uses the same distance vector algorithm and distance information as IGRP; however, the convergence properties and the operating efficiency of Enhanced IGRP are significantly improved.
Chapter 11 Configuring Networking Protocols Configuring EIGRP least-cost path to a destination that is guaranteed not to be part of a routing loop. When there are no feasible successors, but there are neighbors advertising the destination, a recomputation must occur. This is the process whereby a new successor is determined. The amount of time it takes to recompute the route affects the convergence time. Recomputation is processor-intensive; it is advantageous to avoid recomputation if it is not necessary.
Chapter 11 Configuring Networking Protocols Configuring EIGRP Table 11-4 Default EIGRP Configuration (continued) Feature Default Setting Metric weights tos: 0 k1 and k3: 1 k2, k4, and k5: 0 Network None specified. Offset-list Disabled. Router EIGRP Disabled. Set metric No metric set in the route map. Traffic-share Distributed proportionately to the ratios of the metrics. Variance 1 (equal-cost load balancing).
Chapter 11 Configuring Networking Protocols Configuring EIGRP Command Purpose Step 6 Router(config)# offset list [{access-list-number | name}] out } offset [type-number] Step 7 Router(config)# no auto-summary (Optional) Disables automatic summarization of subnet routes into network-level routes. Step 8 Router(config)# ip summary-address eigrp autonomous-system-number address-mask (Optional) Configures a summary aggregate. Step 9 Router(config)# end Returns to privileged EXEC mode.
Chapter 11 Configuring Networking Protocols Configuring EIGRP Command Purpose Step 1 Router# configure terminal Enters global configuration mode. Step 2 Router(config)# interface interface-id Enters interface configuration mode, and specifies the Layer 3 interface to configure. Step 3 Router(config)# ip bandwidth-percent eigrp autonomous-system-number percent (Optional) Configures the maximum percentage of bandwidth that can be used by EIGRP on an interface. The default is 50 percent.
Chapter 11 Configuring Networking Protocols Configure EIGRP Route Authentication Configure EIGRP Route Authentication EIGRP route authentication provides MD5 authentication of routing updates from the EIGRP routing protocol to prevent the introduction of unauthorized or false routing messages from unapproved sources. Beginning in privileged EXEC mode, follow these steps to enable authentication: Command Purpose Step 1 Router# configure terminal Enters global configuration mode.
Chapter 11 Configuring Networking Protocols Configure EIGRP Route Authentication Monitoring and Maintaining EIGRP You can delete neighbors from the neighbor table. You can also display various EIGRP routing statistics. Table 11-5 lists the privileged EXEC commands for deleting neighbors and displaying statistics. For explanations of fields in the resulting display, refer to the Cisco IOS IP and IP Routing Command Reference publication.
Chapter 11 Configuring Networking Protocols Border Gateway Protocol and Classless Interdomain Routing P 192.168.1.0/24, 1 successors, FD is 30720 via 192.168.2.1 (30720/28160), POS0 P 192.168.2.0/24, 1 successors, FD is 10752 via Connected, POS0 P 192.168.3.
Chapter 11 Configuring Networking Protocols Border Gateway Protocol and Classless Interdomain Routing Router(config)# router Router(config-router)# Router(config-router)# Router(config-router)# bgp 30 network 192.168.1.1 neighbor 192.168.2.1 end For more information about configuring BGP routing, refer to the “Configuring BGP” chapter in the Cisco IOS IP and IP Routing Configuration Guide. Verifying the BGP Configuration Table 11-6 lists some common EXEC commands used to view the BGP configuration.
Chapter 11 Configuring Networking Protocols Configuring IS-IS Prefix advertised 2, suppressed 0, withdrawn 0 Number of NLRIs in the update sent: max 2, min 0 Connections established 1; dropped 0 Last reset never Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local host: 192.168.2.2, Local port: 179 Foreign host: 192.168.2.
Chapter 11 Configuring Networking Protocols Verifying the IS-IS Configuration Command Purpose Step 1 Router(config)# router isis [tag] Defines IS-IS as the IP routing protocol. Step 2 Router(config-router)# net network-entity-title Configures network entity titles (NETs) for the routing process; you can specify a name for a NET as well as an address. Step 3 Router(config-router)# interface interface-type interface-id Enters interface configuration mode.
Chapter 11 Configuring Networking Protocols Configuring Static Routes Address Summarization: None Maximum path: 4 Routing for Networks: FastEthernet0 POS0 Routing Information Sources: Gateway Distance 192.168.2.1 115 Distance: (default is 115) Last Update 00:06:48 Router# show isis database IS-IS Level-1 Link State Database: LSPID LSP Seq Num LSP Checksum Router_A.00-00 0x00000003 0xA72F Router_A.02-00 0x00000001 0xA293 Router.
Chapter 11 Configuring Networking Protocols Monitoring Static Routes Example 11-19 show ip route Privileged EXEC Command Output (with a Static Route Configured) Router# show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
Chapter 11 Configuring Networking Protocols Monitoring and Maintaining the IP Network C C S* 192.168.2.0/24 is directly connected, POS0 192.168.3.0/24 is directly connected, FastEthernet0 0.0.0.0/0 [1/0] via 192.168.2.1 Monitoring and Maintaining the IP Network You can remove all contents of a particular cache, table, or database. You can also display specific statistics. Use the privileged EXEC commands in Table 11-9 to clear routes or display status.
Chapter 11 Configuring Networking Protocols Configuring IP Multicast Routing PIM dense mode assumes that the downstream networks want to receive the datagrams forwarded to them. The ML-Series card forwards all packets on all outgoing interfaces until pruning and truncating occur. Interfaces that have PIM dense mode enabled receive the multicast data stream until it times out.
Chapter 11 Configuring Networking Protocols Monitoring and Verifying IP Multicast Operation Monitoring and Verifying IP Multicast Operation After IP multicast routing is configured, you can monitor and verify its operation by performing the commands listed in Table 11-10, from privileged EXEC mode. Table 11-10 IP Multicast Routing Show Commands Command Purpose Router# show ip mroute Shows the complete multicast routing table and the combined statistics of packets processed.
Chapter 11 Configuring Networking Protocols Monitoring and Verifying IP Multicast Operation Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 12 Configuring IRB This chapter describes how to configure integrated routing and bridging (IRB) for the ML-Series card. For more information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication.
Chapter 12 Configuring IRB Configuring IRB • The default routing/bridging behavior in a bridge group (when IRB is enabled) is to bridge all packets. Make sure that you explicitly configure routing on the BVI for IP traffic. • Packets of unroutable protocols such as local-area transport (LAT) are always bridged. You cannot disable bridging for the unroutable traffic. • Protocol attributes should not be configured on the bridged interfaces when you are using IRB to bridge and route a given protocol.
Chapter 12 Configuring IRB IRB Configuration Example To enable and configure IRB and BVI, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# bridge irb Enables IRB. Allows bridging of traffic. Step 2 Router(config)# interface bvi bridge-group Configures the BVI by assigning the number of the corresponding bridge group to the BVI. Each bridge group can have only one corresponding BVI.
Chapter 12 Configuring IRB Monitoring and Verifying IRB ! interface POS0 no ip address crc 32 bridge-group 1 pos flag c2 1 ! interface POS1 no ip address crc 32 bridge-group 1 pos flag c2 1 ! interface BVI1 ip address 192.168.1.1 255.255.255.0 ! router ospf 1 log-adjacency-changes network 192.168.1.0 0.0.0.255 area 0 network 192.168.2.0 0.0.0.255 area 0 Example 12-2 Configuring Router B bridge irb bridge 1 protocol ieee bridge 1 route ip ! ! interface FastEthernet0 ip address 192.168.3.1 255.255.255.
Chapter 12 Configuring IRB Monitoring and Verifying IRB Table 12-1 Commands for Monitoring and Verifying IRB Command Purpose Router# show interfaces bvi bvi-interface-number Shows BVI information, such as the BVI MAC address and processing statistics. The bvi-interface-number is the number of the bridge group assigned to the BVI interface.
Chapter 12 Configuring IRB Monitoring and Verifying IRB Routed protocols on POS0: ip Bridged protocols on POS0: clns ip Software MAC address filter on POS0 Hash Len Address Matches 0x00: 0 ffff.ffff.ffff 9 0x58: 0 0100.5e00.0006 0 0x5B: 0 0100.5e00.0005 1313 0x61: 0 0011.2130.b340 38 0x61: 1 0011.2130.b340 0 0x65: 0 0011.2130.b344 0 0xC0: 0 0100.0ccc.cccc 224 0xC2: 0 0180.c200.0000 0 POS1 SPR1 Bridged protocols on SPR1: clns ip Software MAC address filter on SPR1 Hash Len Address Matches 0x00: 0 ffff.ffff.
C H A P T E R 13 Configuring VRF Lite This chapter describes how to configure VPN Routing and Forwarding Lite (VRF Lite) for the ML-Series cards. For additional information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication.
Chapter 13 Configuring VRF Lite Configuring VRF Lite Configuring VRF Lite Perform the following procedure to configure VRF Lite: Command Purpose Step 1 Router(config)# ip vrf vrf-name Enters VRF configuration mode and assigns a VRF name. Step 2 Router(config-vrf)# rd route-distinguisher Creates a VPN route distinguisher (RD). An RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN.
Chapter 13 Configuring VRF Lite VRF Lite Configuration Example VRF Lite Configuration Example Figure 13-1 shows an example of a VRF Lite configuration. The configurations for Router A and Router B are provided in Example 13-2 and Example 13-3 on page 13-4, respectively. The associated routing tables are shown in Example 13-4 on page 13-6 through Example 13-9 on page 13-7.
Chapter 13 Configuring VRF Lite VRF Lite Configuration Example bridge-group 2 ! interface FastEthernet1 no ip address ! interface FastEthernet1.1 encapsulation dot1Q 3 ip vrf forwarding customer_b ip address 192.168.2.1 255.255.255.0 bridge-group 3 ! interface POS0 no ip address crc 32 no cdp enable pos flag c2 1 ! interface POS0.1 encapsulation dot1Q 1 native ip address 192.168.50.1 255.255.255.0 bridge-group 1 ! interface POS0.2 encapsulation dot1Q 2 ip vrf forwarding customer_a ip address 192.168.100.
Chapter 13 Configuring VRF Lite VRF Lite Configuration Example ! bridge 1 protocol ieee bridge 2 protocol ieee bridge 3 protocol ieee ! ! interface FastEthernet0 no ip address ! interface FastEthernet0.1 encapsulation dot1Q 2 ip vrf forwarding customer_a ip address 192.168.4.1 255.255.255.0 bridge-group 2 ! interface FastEthernet1 no ip address ! interface FastEthernet1.1 encapsulation dot1Q 3 ip vrf forwarding customer_b ip address 192.168.5.1 255.255.255.
Chapter 13 Configuring VRF Lite VRF Lite Configuration Example Example 13-4 Router_A Global Routing Table Router_A# sh ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route,
Chapter 13 Configuring VRF Lite Monitoring and Verifying VRF Lite Gateway of last resort is not set C 192.168.50.0/24 is directly connected, POS0.
Chapter 13 Configuring VRF Lite Monitoring and Verifying VRF Lite Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 14 Configuring Quality of Service This chapter describes the quality of service (QoS) features built into your ML-Series card and how to map QoS scheduling at both the system and interface levels.
Chapter 14 Configuring Quality of Service Priority Mechanism in IP and Ethernet the ML-Series card to provide different levels of treatment to the different services. The different levels are defined through the service elements of bandwidth, including loss and delay. A service-level agreement (SLA) is a guaranteed level of these service elements. The QoS mechanism has three basic steps.
Chapter 14 Configuring Quality of Service Ethernet CoS Figure 14-1 IP Precedence and DSCP 0 Bits 1 DS-Field 2 3 4 5 DSCP 6 Bits 7 CU Class Selector Codepoints 0 1 Precedence 2 3 4 5 Type of Service DTR-Bits Currently Unused RFC 1122 6 7 MBZ Must be zero RFC 1349 Bits (0-2): IP-Precedence Defined 111 (Network Control) 110 (Internetwork Control) 101 (CRITIC/ECP) 100 (Flash Override) 011 (Flash) 101 (Immediate) 001 (Priority) 000 (Routine) Bits (3-6): Type of Service Defined 0
Chapter 14 Configuring Quality of Service ML-Series QoS ML-Series QoS The ML-Series QoS classifies each packet in the network based on its input interface, bridge group (VLAN), Ethernet CoS, IP precedence, IP DSCP, or Cisco proprietary resilient packet ring RPR-CoS. After they are classified into class flows, further QoS functions can be applied to each packet as it traverses the card. Figure 14-3 illustrates the ML-Series QoS flow.
Chapter 14 Configuring Quality of Service Policing Policing Dual leaky bucket policer is a process where the first bucket (CIR bucket) is filled with tokens at a known rate (CIR), which is a parameter that can be configured by the operator. Figure 14-4 illustrates the dual leaky bucket policer model. The tokens fill the bucket up to a maximum level, which is the amount of burstable committed (BC) traffic on the policer.
Chapter 14 Configuring Quality of Service Queuing In some cases, it might be desirable to discard all traffic of a specific ingress class. This can be accomplished by using a police command of the following form with the class: police 96000 conform-action drop exceed-action drop. If a marked packet has a provider-supplied Q-tag inserted before transmission, the marking only affects the provider Q-tag. If a Q-tag is received, it is re-marked.
Chapter 14 Configuring Quality of Service Scheduling WDRR extends the quantum idea from the DRR to provide weighted throughput for each queue. Different queues have different weights, and the quantum assigned to each queue in its round is proportional to the relative weight of the queue among all the queues serviced by that scheduler. Weights are assigned to each queue as a result of the service provisioning process.
Chapter 14 Configuring Quality of Service Control Packets and L2 Tunneled Protocols Control Packets and L2 Tunneled Protocols The control packets originated by the ML-Series card have a higher priority than data packets. The external Layer 2 and Layer 3 control packets are handled as data packets and assigned to broadcast queues.
Chapter 14 Configuring Quality of Service Ingress Priority Marking Using the QinQ feature, service providers can use a single VLAN to support customers with multiple VLANs. QinQ preserves customer VLAN IDs and segregates traffic from different customers within the service-provider infrastructure, even when traffic from different customers originally shared the same VLAN ID. The QinQ also expands VLAN space by using a VLAN-in-VLAN hierarchy and tagging the tagged packets.
Chapter 14 Configuring Quality of Service QoS on Cisco Proprietary RPR Note QoS and policing are not supported on the ML-Series card interface when link aggregation is used. Note Egress shaping is not supported on the ML-Series cards. QoS on Cisco Proprietary RPR For VLAN bridging over Cisco proprietary RPR , all ML-Series cards on the ring must be configured with the base Cisco proprietary RPR and Cisco proprietary RPR QoS configuration.
Chapter 14 Configuring Quality of Service QoS on Cisco Proprietary RPR Caution "Match cos 0" should not be included in the definition of any class-map, because non-VLAN-tagged Ethernet packets are always treated as CoS 0 on input from Ethernet. Using “match cos 0” might incorrectly match all traffic coming from Ethernet.
Chapter 14 Configuring Quality of Service Configuring QoS Configuring QoS This section describes the tasks for configuring the ML-Series card QoS functions using the MQC. The ML-Series card does not support the full set of MQC functionality.
Chapter 14 Configuring Quality of Service Creating a Traffic Policy Table 14-1 Traffic Class Commands (continued) Command Purpose Router(config-cmap)# match cos cos-number Specifies the CoS value against whose contents packets are checked to determine if they belong to the class. Router(config-cmap)# match input-interface interface-name Specifies the name of the input interface used as a match criterion against which packets are checked to determine if they belong to the class.
Chapter 14 Configuring Quality of Service Creating a Traffic Policy Table 14-2 Traffic Policy Commands Command Purpose Router (config)# policy-map policy-name Specifies the name of the traffic policy to configure. Names can be a maximum of 40 alphanumeric characters. Router (config-pmap)# class class-map-name Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy.
Chapter 14 Configuring Quality of Service Creating a Traffic Policy Table 14-2 Traffic Policy Commands (continued) Command Purpose Router (config-pmap-c)# police cir-rate-bps normal-burst-byte [max-burst-byte] [pir pir-rate-bps] [conform-action {set-cos-transmit | transmit | drop}] [exceed-action {set-cos-transmit | drop}] [violate-action {set-cos-transmit | drop}] Defines a policer for the currently selected class when the policy map is applied to input.
Chapter 14 Configuring Quality of Service Attaching a Traffic Policy to an Interface Table 14-2 Traffic Policy Commands (continued) Command Purpose Router (config-pmap-c)# priority kbps Specifies low latency queuing for the currently selected class. This command can only be applied to an output. When the policy-map is applied to an output, an output queue with strict priority is created for this class. The only valid rate choice is in kilobits per second.
Chapter 14 Configuring Quality of Service Configuring CoS-Based QoS Use the no form of the command to detach a traffic policy from an interface. The service-policy command syntax is as follows: service-policy {input | output} policy-map-name no service-policy {input | output} policy-map-name To attach a traffic policy to an interface, use the following commands in global configuration mode, as needed: Step 1 Enters interface configuration mode, and specifies the interface to apply the policy map.
Chapter 14 Configuring Quality of Service QoS Configuration Examples Table 14-4 Commands for QoS Status Command Purpose Router# show class-map name Displays the traffic class information of the user-specified traffic class. Router# show policy-map Displays all configured traffic policies. Router# show policy-map name Displays the user-specified policy map. Router# show policy-map interface interface Displays configurations of all input and output policies attached to an interface.
Chapter 14 Configuring Quality of Service Traffic Classes Defined Example Traffic Classes Defined Example Example 14-5 shows how to create a class map called class1 that matches incoming traffic entering interface fastethernet0. Example 14-5 Class Interface Command Examples Router(config)# class-map class1 Router(config-cmap)# match input-interface fastethernet0 Example 14-6 shows how to create a class map called class2 that matches incoming traffic with IP-precedence values of 5, 6, and 7.
Chapter 14 Configuring Quality of Service class-map match-any and class-map match-all Commands Example class-map match-any and class-map match-all Commands Example This section illustrates the difference between the class-map match-any command and the class-map match-all command. The match-any and match-all options determine how packets are evaluated when multiple match criteria exist.
Chapter 14 Configuring Quality of Service ML-Series VoIP Example Match input-interface SPR1 Match cos 1 ML-Series VoIP Example Figure 14-7 shows an example of ML-Series QoS configured for VoIP. The associated commands are provided in Example 14-12. Figure 14-7 ML-Series VoIP Example ONS 15454 with ML100T-12 Router_A VoIP Traffic Fast Ethernet 0 POS 0 SONET/SDH General Data Traffic During periods of congestion, the ML-Series card services all VoIP traffic before servicing any general data traffic.
Chapter 14 Configuring Quality of Service ML-Series CoS-Based QoS Example Figure 14-8 ML-Series Policing Example ONS 15454 with ML100T-12 Router_a Fast Ethernet 0 POS 0 Policer on Fast Ethernet 0 allows 1,000,000 bps of traffic with an IP ToS value of 0. Excess traffic with an IP ToS value of 0 is dropped.
Chapter 14 Configuring Quality of Service ML-Series CoS-Based QoS Example Figure 14-9 ML-Series CoS Example ML-Series Card B POS 1 POS 0 POS 1 POS 0 RPR POS 1 POS 0 ML-Series Card C Customer Access Point = STS circuit created on CTC 96501 ML-Series Card A Customer Access Point Example 14-14 shows the code used to configure ML-Series card A in Figure 14-9.
Chapter 14 Configuring Quality of Service Understanding Multicast QoS and Priority Multicast Queuing Understanding Multicast QoS and Priority Multicast Queuing ML-Series card QoS supports the creation of two priority classes for multicast traffic in addition to the default multiclass traffic class. Creating a multicast priority queuing class of traffic configures the ML-Series card to recognize an existing CoS value in ingressing multicast traffic for priority treatment.
Chapter 14 Configuring Quality of Service Multicast Priority Queuing QoS Restrictions When bandwidth is allocated to multicast priority queuing but no output policy map is applied, the default multicast congestion bandwidth is a minimum of 10 percent of the bandwidth not allocated to multicast priority queuing. When an output policy-map is applied to an interface, default multicast and default unicast share the minimum bandwidth assigned to the default class.
Chapter 14 Configuring Quality of Service Configuring Multicast Priority Queuing QoS Table 14-5 CoS Multicast Priority Queuing Command Command Purpose Router (config)# [no] cos priority-mcast cos-value {bandwidth-kbps | mbps bandwidth-mbps | percent percent} Creates a priority class of multicast traffic based on a multicast CoS value and specifies a minimum bandwidth guarantee to a traffic class in periods of congestion.
Chapter 14 Configuring Quality of Service QoS not Configured on Egress QoS not Configured on Egress The QoS bandwidth allocation of multicast and broadcast traffic is handled separately from unicast traffic. On each interface, the aggregate multicast and broadcast traffic are given a fixed bandwidth commit of 10% of the interface bandwidth. This is the optimum bandwidth that can be provided for traffic exceeding 10% of the interface bandwidth.
Chapter 14 Configuring Quality of Service ML-Series Egress Bandwidth Example For example, if 18x bandwidth is available after servicing priority unicast traffic (CoS 5), then the remaining bandwidth will be allocated as follows: Unicast traffic with CoS 2 : 2x Unicast traffic with CoS 7: 6x Unicast default (without CoS 2, CoS 5, CoS 7): 9x All multicast/broadcast (any CoS value): 1x Example 14-17 QoS with Priority and Bandwidth Configured without Priority Multicast ! class-map match-all customer_voice matc
Chapter 14 Configuring Quality of Service Understanding CoS-Based Packet Statistics policy-map policy_egress_bandwidth class customer_core_traffic bandwidth 1000 class customer_voice priority 1000 class customer_data bandwidth 3000 class class-default bandwidth 5000 ! ! interface POS0 no ip address crc 32 service-policy output policy_egress_bandwidth ! Understanding CoS-Based Packet Statistics Enhanced performance monitoring displays per-CoS packet statistics on the ML-Series card interfaces when CoS acco
Chapter 14 Configuring Quality of Service Configuring CoS-Based Packet Statistics Note For IEEE 802.1Q (QinQ) enabled interfaces, CoS accounting is based only on the CoS value of the outer metro tag imposed by the service provider. The CoS value inside the packet sent by the customer network is not considered for CoS accounting. For information on the enhanced microcode image, see the “Multiple Microcode Images” section on page 3-11.
Chapter 14 Configuring Quality of Service Understanding IP SLA Cos Cos Cos Cos Cos 3: 4: 5: 6: 10 7: 640 Router# show interface gigabitethernet 0 cos GigabitEthernet0 Stats by Internal-Cos Input: Packets Bytes Cos 0: 123 3564 Cos 1: Cos 2: 3 211 Cos 3: Cos 4: Cos 5: Cos 6: Cos 7: Output: Packets Bytes Cos 0: 1234567890 1234567890 Cos 1: 3 200 Cos 2: Cos 3: Cos 4: Cos 5: Cos 6: 1 64 Cos 7: Output: Drop-pkts Drop-bytes Cos 0: 1234567890 1234567890 Cos 1: Cos 2: Cos 3: Cos 4: Cos 5: 1 64 Cos 6: 10 640 Cos
Chapter 14 Configuring Quality of Service IP SLA on the ML-Series Depending on the specific IP SLAs operation, statistics of delay, packet loss, jitter, packet sequence, connectivity, path, server response time, and download time are monitored within the Cisco device and stored in both CLI and SNMP MIBs.
Chapter 14 Configuring Quality of Service IP SLA Restrictions on the ML-Series • The average Round Trip Time (RTT) measured on an ML-Series IP SLA feature is more than the actual data path latency. In the ML-Series cards, IP SLA is implemented in the software. The IP SLA messages are processed in the CPU of the ML-Series card. The latency time measured includes the network latency and CPU processing time.
Chapter 14 Configuring Quality of Service IP SLA Restrictions on the ML-Series Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 15 Configuring the Switching Database Manager This chapter describes the switching database manager (SDM) features built into the ML-Series card and contains the following major sections: • Understanding the SDM, page 15-1 • Understanding SDM Regions, page 15-1 • Configuring SDM, page 15-2 • Monitoring and Verifying SDM, page 15-3 Understanding the SDM ML-Series cards use the forwarding engine and ternary content-addressable memory (TCAM) to implement high-speed forwarding.
Chapter 15 Configuring the Switching Database Manager Configuring SDM • Weighted-exact-match region—The weighted-exact-match region consists of exact-match-entries with an assigned weight or priority. For example, with QoS, multiple exact match entries might exist, but some have priority over others. The weight is used to select one entry when multiple entries match. Table 15-1 lists default partitioning for each application region.
Chapter 15 Configuring the Switching Database Manager Configuring Access Control List Size in TCAM Configuring Access Control List Size in TCAM The default maximum size of the ACL is 300 64-bit entries. You can enter the sdm access-list command to change the maximum ACL database size, as shown in Table 15-2. Table 15-2 Partitioning the TCAM Size for ACLs Task Command sdm access-list number-entries Sets the name of the application region for which you want to configure the size.
Chapter 15 Configuring the Switching Database Manager Monitoring and Verifying SDM Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 16 Configuring Access Control Lists This chapter describes the access control list (ACL) features built into the ML-Series card. This chapter contains the following major sections: • Understanding ACLs, page 16-1 • ML-Series ACL Support, page 16-1 • Modifying ACL TCAM Size, page 16-5 Understanding ACLs ACLs provide network control and security, allowing you to filter packet flow into or out of ML-Series interfaces.
Chapter 16 Configuring Access Control Lists IP ACLs • ACL logging is supported only for packets going to the CPU, not for switched packets. • IP standard ACLs applied to bridged egress interfaces are not supported in the data-plane. When bridging, ACLs are only supported on ingress. IP ACLs The following ACL styles for IP are supported: Note • Standard IP ACLs: These use source addresses for matching operations.
Chapter 16 Configuring Access Control Lists Creating IP ACLs Creating IP ACLs The following sections describe how to create numbered standard, extended, and named standard IP ACLs: • Creating Numbered Standard and Extended IP ACLs, page 16-3 • Creating Named Standard IP ACLs, page 16-4 • Creating Named Extended IP ACLs (Control Plane Only), page 16-4 • Applying the ACL to an Interface, page 16-4 Creating Numbered Standard and Extended IP ACLs Table 16-1 lists the global configuration commands used
Chapter 16 Configuring Access Control Lists Creating IP ACLs Creating Named Standard IP ACLs To create a named standard IP ACL, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# ip access-list standard name Defines a standard IP ACL using an alphabetic name. Step 2 Router(config-std-nac1)# deny {source [source-wildcard] | any} In access-list configuration mode, specifies one or more conditions as permitted or denied.
Chapter 16 Configuring Access Control Lists Modifying ACL TCAM Size Table 16-2 Applying ACL to Interface Command Purpose ip access-group {access-list-number | name} {in | out} Controls access to an interface. Modifying ACL TCAM Size You can change the TCAM size by entering the sdm access-list command. For more information on ACL TCAM sizes, see the “Configuring Access Control List Size in TCAM” section on page 15-3. Example 16-1 provides an example of modifying and verifying ACLs.
Chapter 16 Configuring Access Control Lists Modifying ACL TCAM Size Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 17 Configuring Cisco Proprietary Resilient Packet Ring Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Understanding Cisco Proprietary RPR Understanding Cisco Proprietary RPR Cisco proprietary RPR is a MAC protocol operating at the Layer 2 level. It is well suited for transporting Ethernet over a SONET/SDH ring topology and it enables multiple ML-Series cards to become one functional network segment or shared packet ring (SPR). Cisco proprietary RPR overcomes the limitations of earlier schemes, such as IEEE 802.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Ring Wrapping Figure 17-1 Cisco Proprietary RPR Packet Handling Operations Strip Pass through Bridge 90649 ML-Series RPR Ring Wrapping Cisco proprietary RPR initiates ring wraps in the event of a fiber cut, node failure, node restoration, new node insertion, deletion of the circuit on POS port of SPR, SPR keepalive failure or other traffic problem.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Ring Wrapping Figure 17-2 Cisco proprietary RPR Ring Wrapping Ring Wrap Fiber Cut ML-Series RPR 90650 Ring Wrap In case of a ring failure, the ML-Series cards connected to the failed section of the Cisco proprietary RPR detect the failure through the SONET/SDH path alarms. When any ML-Series card receives this path-AIS signal, it wraps the POS interface that received the signal.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR Framing Process Cisco Proprietary RPR Framing Process Cisco proprietary RPR on the ML-Series card uses a proprietary RPR frame and high-level data link control (HDLC) or GFP-F framing. It attaches the Cisco proprietary RPR frame header to each Ethernet frame and encapsulates the Cisco proprietary RPR frame into the SONET/SDH payload for transport over the SONET/SDH topology.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring MAC Address and VLAN Support Figure 17-4 Cisco Proprietary RPR Frame Fields 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Protocol (RPR V1) Destination ID Destination Station Source ID Source Station PRI W B D D E Wrap Station V TTL D D RSVD Type W S 134982 Payload (Ethernet Frame) Table 17-1 Definitions of RPR Frame Fields Field Definition Destination Station An eight-bit field specifying the MAC address of a specific ML-Series car
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR QoS The ML-Series card still has an architectural maximum limit of 255 VLANs/bridge-groups per ML-Series card. But because the ML-Series card only needs to maintain the MAC address of directly connected devices, a greater total number of connected devices are allowed on a Cisco proprietary RPR network.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Connecting the ML-Series Cards with Point-to-Point STS/STM Circuits Note Transaction Language One (TL1) can be used to provision the required SONET/SDH point-to-point circuits instead of CTC. Connecting the ML-Series Cards with Point-to-Point STS/STM Circuits You connect the ML-Series cards through point-to-point STS/STM circuits.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Configuring CTC Circuits for Cisco Proprietary RPR Figure 17-5 Three Node Cisco Proprietary RPR SPR Station-ID 1 POS 1 POS 0 POS 1 POS 0 SPR 1 SPR Station-ID 2 SPR Station-ID 3 POS 1 POS 0 = STS circuit created on CTC The three-node Cisco proprietary RPR in Figure 17-5 is used for all of the examples in the consecutive procedures. Combining the examples will give you an end-to-end example of creating a Cisco proprietary RPR.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Configuring CTC Circuits for Cisco Proprietary RPR Figure 17-6 CTC Card View for ML-Series Card Step 2 Click the Circuits > Create tabs. The first page of the Circuit Creation wizard appears (Figure 17-7). Figure 17-7 CTC Circuit Creation Wizard Step 3 In the Circuit Type list, select STS. Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Configuring CTC Circuits for Cisco Proprietary RPR Step 4 Click Next. The Circuit Attributes page appears. Step 5 Type a circuit name in the Name field. Step 6 Select the relevant size of the circuit from the Size drop-down list, and the appropriate state from the State list. Step 7 Verify that the signal degrade (SD) threshold is either set to 1E-6 (default) or in the 1E-6 to 1E-9 range in the SD threshold field. Note Step 8 a.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Configuring Cisco Proprietary RPR Characteristics and the SPR Interface on the ML-Series Card Step 20 Build the third circuit between POS 0 on Node 3 and POS 1 on Node 1. Use the same procedure described in Steps 1 through 18, but substitute Node 3 for Node 1 and Node 1 for Node 2. Now all of the POS ports in all three nodes are connected by STS point-to-point circuits in an east-to-west pattern, as shown in Figure 17-5 on page 17-9.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Configuring Cisco Proprietary RPR Characteristics and the SPR Interface on the ML-Series Card Cisco proprietary RPR needs to be provisioned on each ML-Series card that is in the Cisco proprietary RPR.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Assigning the ML-Series Card POS Ports to the SPR Interface Assigning the ML-Series Card POS Ports to the SPR Interface Caution The SPR interface is the routed interface. Do not enable Layer 3 addresses or assign bridge groups on the POS interfaces assigned to the SPR interface.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces Command Purpose Step 7 Router(config-if)# interface pos 1 Enters the interface configuration mode to configure the second POS interface that you want to assign to the SPR. Step 8 Router(config-if)# encapsulation lex Sets POS interface encapsulation as LEX (default). Cisco proprietary RPR on the ML-Series card requires LEX encapsulation.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR Cisco IOS Configuration Example Figure 17-8 Cisco proprietary RPR Bridge Group ML-Series Card Ethernet Port 0 POS 0 Bridge Group Ethernet Port 1 SPR (RPR) Interface 134983 POS 1 Caution All Layer 2 network redundant links (loops) in the connecting network, except the Cisco proprietary RPR topology, must be removed for correct operation. Or if loops exist, you must configure STP/RSTP.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR Cisco IOS Configuration Example bridge-group 10 bridge-group 10 spanning-disabled hold-queue 150 in interface GigabitEthernet0 no ip address bridge-group 10 bridge-group 10 spanning-disabled interface GigabitEthernet1 no ip address shutdown interface POS0 no ip address carrier-delay msec 0 spr-intf-id 1 crc 32 interface POS1 no ip address carrier-delay msec 0 spr-intf-id 1 crc 32 ! Example 17-2 SPR Station-ID 2 Configurat
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Verifying Ethernet Connectivity Between Cisco Proprietary RPR Ethernet Access Ports interface SPR1 no ip address no keepalive spr station-id 3 bridge-group 10 bridge-group 10 spanning-disabled hold-queue 150 in interface GigabitEthernet0 no ip address bridge-group 10 bridge-group 10 spanning-disabled interface GigabitEthernet1 no ip address shutdown interface POS0 no ip address spr-intf-id 1 crc 32 interface POS1 no ip address spr-intf-id 1 crc
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Add an ML-Series Card into a Cisco Proprietary RPR MTU 1500 bytes, BW 290304 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation: Cisco-EoS-LEX, loopback not set Keepalive not set DTR is pulsed for 27482 seconds on reset, Restart-Delay is 65 secs ARP type: ARPA, ARP Timeout 04:00:00 No.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Add an ML-Series Card into a Cisco Proprietary RPR Figure 17-9 shows the existing two-node Cisco proprietary RPR with the single STS circuit and span that will be deleted. Figure 17-10 shows the Cisco proprietary RPR after the third node is added with the two new STS circuits and spans that will be added.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Add an ML-Series Card into a Cisco Proprietary RPR Figure 17-10 Three Node Cisco Proprietary RPR After the Addition Adjacent Node 1 POS 1 POS 0 POS 1 New Node POS 1 SPR 1 Adjacent Node 2 POS 0 = STS circuit created on CTC 145250 POS 0 To add an ML-Series card to the Cisco proprietary RPR, you need to complete several general actions: • Force away any existing non-ML-Series card circuits, such as DS-1, that use the span that will be
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Adding an ML-Series Card into a Cisco Proprietary RPR Caution • Test Ethernet connectivity between the access ports on the new ML-Series card with a test set to validate the newly created three-node Cisco proprietary RPR. • Monitor Ethernet traffic and existing routing protocols for at least an hour after the node insertion. The specific steps in the following procedure are for the topology in the example.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Adding an ML-Series Card into a Cisco Proprietary RPR Step 13 Use a test set to verify that Ethernet connectivity still exists between the Ethernet access ports on Adjacent Node 1 and Adjacent Node 2. Note The SPR interface and the Ethernet interfaces on the ML-Series card must be in a bridge group in order for Cisco proprietary RPR traffic to bridge the Cisco proprietary RPR.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Delete an ML-Series Card from a Cisco Proprietary RPR Step 22 Complete the following Cisco IOS configuration on the Adjacent Node 2 ML-Series card, beginning in global configuration mode: a. Router(config)# interface pos interface-number Enters interface configuration mode for the POS port at one endpoint of the second newly created circuit. b. Router(config-if)# no shutdown Enables the port.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Delete an ML-Series Card from a Cisco Proprietary RPR Figure 17-11 Three Node Cisco Proprietary RPR Before the Deletion Adjacent Node 1 POS 1 POS 0 POS 1 POS 0 Delete Node SPR 1 Adjacent Node 2 POS 0 = STS circuit created on CTC Figure 17-12 145251 POS 1 Two Node Cisco Proprietary RPR After the Deletion Adjacent Node 1 POS 0 POS 1 SPR 1 Deleted Node POS 1 POS 0 Adjacent Node 2 = STS circuit created on CTC 145253 This STS cir
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Deleting an ML-Series Card from a Cisco Proprietary RPR Caution • Force away any existing non-ML-Series card circuits, such as DS-1, that use the spans that will be deleted. • Shut down the POS ports on the adjacent ML-Series cards for the STS circuits that will be deleted to initiate the Cisco proprietary RPR wrap.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Deleting an ML-Series Card from a Cisco Proprietary RPR a. Router(config)# interface pos interface-number Enters interface configuration mode for the POS port at the end of the circuit directly connected to the Delete Node. b. Router(config-if)# shutdown Closes the interface. Step 5 Log into Adjacent Node 1 with CTC. Step 6 Double-click the ML-Series card in Adjacent Node 1. The card view appears. Step 7 Click the Circuits tab.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Understanding Cisco Proprietary RPR Link Fault Propagation Step 23 If the ML-Series card in the new node is to be deleted in CTC and physically removed, do so now. Refer to the “Install Cards and Fiber-Optic Cable” chapter of the Cisco ONS 15454 Procedure Guide or the “Install Cards and Fiber-Optic Cable” chapter of the Cisco ONS 15454 SDH Procedure Guide for procedures for installing cards in ONS nodes.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring LFP Sequence Figure 17-13 Cisco Proprietary RPR Link Fault Propagation Example Hub Router Original Link-fault ML-Series Card Master Interface ML-Series RPR ML-Series Card Slave Interface Access Switches and Routers 131696 Propagated Link-faults LFP Sequence LFP updates are done through a Cisco discovery packet (CDP) packet extension. The update is sent periodically and immediately after the master interface goes into a link-down state.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Propagation Delays • Disabling LFP on the master interface. Link faults only propagate from master to slave. Normal slave link faults are not propagated. Cisco proprietary RPR wrapping and unwrapping has no effect on LFP. Propagation Delays Propagation delay includes the carrier-delay time on the slave interface. The carrier-delay time is configurable and has a default of 200 ms.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring LFP Configuration Requirements To enable and configure the LFP slave link, perform the following procedure on an ML-Series card in the Cisco proprietary RPR other than the ML-Series card configured for the master link. Begin in global configuration mode: Command Purpose Step 1 Router# interface {gigabit ethernet | fastethernet} number Activates interface configuration mode to configure the Gigabit Ethernet or Fast Ethernet interface.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR Keep Alive Example 17-6 Monitor and Verify LFP Router# show link-fault Link Fault Propagation Configuration: ------------------------------------LFP Config Mode : LFP_SLAVE LFP Master State : LFP_STATUS_DOWN Interfaces configured for LFP: FastEthernet0 (down) Cisco Proprietary RPR Keep Alive The keep alive mechanism for Cisco proprietary RPR POS interfaces sends keep-alive packets onto SPR links connecting adjacent nodes.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Monitoring and Verifying Cisco Proprietary RPR Keep Alives To enable and configure the Cisco proprietary RPR keep alives, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router# interface pos 0 Activates interface configuration mode to configure the POS interface. Step 2 Router(config-if)# spr keepalive Enables Cisco proprietary RPR keep alives on the POS interface.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR Shortest Path Hardware is POS-SPR, address is 0005.9a3b.c140 (bia 0000.0000.0000) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation: Cisco-EoS-LEX, loopback not set Keepalive not set Unknown duplex, Unknown Speed, unknown media type ARP type: ARPA, ARP Timeout 04:00:00 SPR Wrapped information: POS0 : SONET POS1 : SONET KEEPALIVE No.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Cisco Proprietary RPR Shortest Path Shortest and Longest Path RPR P0 RPR P0 P1 P0 E0 P1 P0 E0 E0 E0 E1 A E1 A C C B A B B (shortest path) A 151792 Figure 17-14 B (longest path) By always using the shortest path, traffic between two nodes can achieve the lowest possible latency. This is especially important for delay-sensitive traffic such as voice-over-IP (VoIP) or video broadcast TV.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Configuring Shortest Path and Topology Discovery Configuring Shortest Path and Topology Discovery To enable and configure shortest path and topology discovery, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router# interface spr1 Activates interface configuration mode to configure the POS interface.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring Understanding Redundant Interconnect Understanding Redundant Interconnect Ring interconnect (RI) is a mechanism to interconnect RPRs, both RPR-IEEE and Cisco proprietary RPR, for protection from failure. It does this through redundant pairs of back-to-back Gigabit Ethernet connections that bridge RPR networks. One connection is the active node and the other is the standby node.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring RI for SW RPR Configuration Example • Provides card-level redundancy when connected to a switch running EtherChannel Caution When connecting to a switch running EtherChannel, you must configure spr ri foreign on the primary and secondary ML-Series cards. Caution SW RPR RI requires communication over the topology between the ML-Series cards.
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring RI for SW RPR Configuration Example spr ri mode primary peer 1 spr ri foreign no shutdown Example 17-13 Secondary ML-Series Card Configuration with Connection to Switch interface spr1 no ip address spr topology discovery spr ri mode primary peer 1 spr ri foriegn no shutdown Example 17-14 > Status of Redundant Interconnect can be found using sh ons spr ri ml1000-140#sh ons spr ri Redundant Interconnect Data Mode: primary State: initialization
Chapter 17 Configuring Cisco Proprietary Resilient Packet Ring RI for SW RPR Configuration Example Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 18 Configuring Ethernet over MPLS This chapter describes how to configure Ethernet over Multiprotocol Label Switching (EoMPLS) on the ML-Series card. This chapter includes the following major sections: • Understanding EoMPLS, page 18-1 • Configuring EoMPLS, page 18-4 • EoMPLS Configuration Example, page 18-9 • Monitoring and Verifying EoMPLS, page 18-12 Understanding EoMPLS EoMPLS provides a tunneling mechanism for Ethernet traffic through an MPLS-enabled Layer 3 core.
Chapter 18 Configuring Ethernet over MPLS Understanding EoMPLS EoMPLS Service Provider Network GSR 12000 MPLS Cloud-facing Core MPLS Interface RPR GSR 12000 MPLS Cloud-facing Interface RPR CE CE PE-CLE PE-CLE 96983 Figure 18-1 Implementing EoMPLS on a service provider network requires ML-Series card interfaces to play three major roles. The ML-Series card interface roles must be configured on both sides of the EoMPLS point-to-point service crossing the MPLS core.
Chapter 18 Configuring Ethernet over MPLS EoMPLS Support EoMPLS Support EoMPLS on the ML-Series card has the following characteristics: • EoMPLS is only supported on FastEthernet and GigabitEthernet interfaces or subinterfaces. • MPLS tag switching is only supported on SPR interfaces. • Class of service (CoS) values are mapped to the experimental (EXP) bits in the MPLS label, either statically or by using the IEEE 802.1p bits (default).
Chapter 18 Configuring Ethernet over MPLS Configuring EoMPLS By default, the ML-Series card does not map the IEEE 802.1P bits in the VLAN tag header to the MPLS EXP bits. The MPLS EXP bits are set to a value of 0. There is no straight copy between Layer 2 CoS and MPLS EXP, but the user can use the set mpls experimental action to set the MPLS EXP bit values based on a match to 802.1p bits. This mapping occurs at the entry point, the ingress of the network.
Chapter 18 Configuring Ethernet over MPLS EoMPLS Configuration Guidelines • EoMPLS Configuration on PE-CLE SPR Interface, page 18-8 (Required) • Bridge Group Configuration on MPLS Cloud-facing Port, page 18-8 (Required) • Setting the Priority of Packets with the EXP, page 18-9 EoMPLS Configuration Guidelines These are the guidelines for configuring EoMPLS: • Loopback addresses are used to specify the peer ML-Series card’s IP address. • LDP configuration is required.
Chapter 18 Configuring Ethernet over MPLS VC Type 5 Configuration on PE-CLE Port Step 7 Command Purpose Router(config-subif)# mpls l2transport route destination vc-id By entering the mpls l2transport route or the xconnect interface configuration command on a dot1Q VLAN sub-interface for VLAN-based EoMPLS, you can configure an EoMPLS tunnel to forward traffic based on the customer VLAN.
Chapter 18 Configuring Ethernet over MPLS VC Type 5 Configuration on PE-CLE Port Step 1 Command Purpose Router(config)# mpls label protocol ldp Specifies LDP as the label distribution protocol. LDP must be specified. The ML-Series card does not operate EoMPLS with the default TDP as the label distribution protocol. Step 2 Router(config)# interface loopback0 Enters loopback interface configuration mode. Step 3 Router(config-if)# ip address ip-address 255.255.255.
Chapter 18 Configuring Ethernet over MPLS EoMPLS Configuration on PE-CLE SPR Interface EoMPLS Configuration on PE-CLE SPR Interface To enable the RPR to act as an access ring for the MPLS cloud, you must provision the SPR interface on the same ML-Series card that hosts the EoMPLS PE-CLE FastEthernet or GigabitEthernet interfaces. Interface SPR 1 on card A and card C plays this role in Figure 18-2 on page 18-10.
Chapter 18 Configuring Ethernet over MPLS Setting the Priority of Packets with the EXP Command Purpose Step 6 Router(config-if)# bridge-group bridge-group-number Assigns the network interface to a bridge group. Step 7 Router(config-if)# end Returns to privileged EXEC mode. Step 8 Router# copy running-config startup-config (Optional) Saves your entries in the configuration file.
Chapter 18 Configuring Ethernet over MPLS EoMPLS Configuration Example EoMPLS Configuration Example ML-Series Card B GSR 12000 GigE 0 GigE 0.1 VC Type 4 1 5 gE e Gi Typ VC GSR 12000 Core MPLS ML-Series Card D GigE 0 RPR RPR SPR 1 SPR 1 ML-Series Card A ML-Series Card C GigE 0.1 VC Type 4 VC GigE Ty 1 pe 5 96982 Figure 18-2 Example 18-1 ML-Series Card A Configuration microcode mpls ip subnet-zero no ip domain-lookup ! mpls label protocol ldp ! interface Loopback0 ip address 10.10.10.10 255.
Chapter 18 Configuring Ethernet over MPLS EoMPLS Configuration Example no ip address spr-intf-id 1 crc 32 router ospf 1 log-adjacency-changes network 1.1.1.0 0.0.0.255 area 0 network 10.10.10.0 0.0.0.
Chapter 18 Configuring Ethernet over MPLS Monitoring and Verifying EoMPLS no ip address spr-intf-id 1 crc 32 ! router ospf 1 log-adjacency-changes network 1.1.1.0 0.0.0.255 area 0 network 10.10.10.0 0.0.0.
Chapter 18 Configuring Ethernet over MPLS Understanding MPLS-TE Understanding MPLS-TE MPLS traffic is normally routed to the least cost path as calculated by OSPF or another IGP routing protocol. This routing gives little or no consideration to varying bandwidth demands or link loads. MPLS traffic engineering (MPLS-TE) overcomes this by mapping traffic flows to paths that take bandwidth demands into account.
Chapter 18 Configuring Ethernet over MPLS Configuring MPLS-TE Ethernet FCS preservation is off by default on the ML-Series card. Configure Ethernet FCS preservation at the interface or sub-interface configuration level with the [no] fcs-preservation-on command. To operate correctly, both ends of the EoMPLS tunnel need to be configured for FCS preservation.
Chapter 18 Configuring Ethernet over MPLS Configuring OSPF and Refresh Reduction for MPLS-TE Note A VC type 4 requires one POS interface to be configured for MPLS-TE tunnel and the other POS interface configured for the 802.1Q tunnel. Command Purpose Step 1 Router(config-if)# mpls traffic-eng tunnels Enables MPLS-TE tunnels on an RPR (SPR) interface or on a POS interface.
Chapter 18 Configuring Ethernet over MPLS MPLS-TE Configuration Example Command Purpose Step 1 Router(config)# interface tunnel Configures an interface type and enters interface configuration mode. Step 2 Router(config)# ip unnumbered loopback0 Gives the tunnel interface an IP address. An MPLS-TE tunnel interface should be unnumbered because it represents a unidirectional link. Step 3 Router(config-if)# tunnel destination A.B.C.D Specifies the destination for a tunnel.
Chapter 18 Configuring Ethernet over MPLS MPLS-TE Configuration Example no mpls traffic-eng auto-bw timers frequency 0 ! ! ! interface Loopback0 ip address 222.222.222.222 255.255.255.255 ! interface Tunnel0 ip unnumbered Loopback0 tunnel destination 212.212.212.212 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng path-option 1 explicit identifier 1 ! interface Tunnel1 ip unnumbered Loopback0 tunnel destination 212.212.212.
Chapter 18 Configuring Ethernet over MPLS Monitoring and Verifying MPLS-TE and IP RSVP ! ip explicit-path identifier 1 enable next-address 2.1.1.1 next-address 192.168.3.2 next-address 192.168.3.1 next-address 2.2.1.1 next-address 2.2.1.2 next-address 212.212.212.212 ! ip explicit-path identifier 2 enable next-address 170.170.170.171 next-address 192.168.3.2 next-address 192.168.3.1 next-address 2.2.1.1 next-address 2.2.1.2 next-address 212.212.212.
Chapter 18 Configuring Ethernet over MPLS RPRW Alarm Table 18-3 Commands for Monitoring and Verifying MPLS-TE (continued) Command Purpose show mpls traffic-eng link-management igp-neighbors Displays IGP neighbors. show mpls traffic-eng link-management interfaces Displays interface resource and configuration information. show mpls traffic-eng link-management summary Displays a summary of link management information including link counts.
Chapter 18 Configuring Ethernet over MPLS RPRW Alarm Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 19 Configuring Security for the ML-Series Card This chapter describes the security features of the ML-Series card.
Chapter 19 Configuring Security for the ML-Series Card Disabling the Console Port on the ML-Series Card Disabling the Console Port on the ML-Series Card There are several ways to access the Cisco IOS running on the ML-Series card, including a direct connection to the console port, which is the RJ-11 serial port on the front of the card. Users can increase security by disabling this direct connection, which is enabled by default.
Chapter 19 Configuring Security for the ML-Series Card Configuring SSH SSH has two applications, an SSH server and SSH client. The ML-Series card only supports the SSH server and does not support the SSH client. The SSH server in Cisco IOS software works with publicly and commercially available SSH clients. The SSH server enables a connection into the ML-Series card, similar to an inbound Telnet connection, but with stronger security. Before SSH, security was limited to the native security in Telnet.
Chapter 19 Configuring Security for the ML-Series Card Configuring SSH Command Purpose Step 1 Router #configure terminal Enter global configuration mode. Step 2 Router (config)# hostname hostname Configure a hostname for your ML-Series card. Step 3 Router (config)# ip domain-name domain_name Configure a host domain for your ML-Series card.
Chapter 19 Configuring Security for the ML-Series Card Displaying the SSH Configuration and Status Command Purpose Step 1 Router # configure terminal Enter global configuration mode. Step 2 Router (config)# ip ssh version [1 | 2] (Optional) Configure the ML-Series card to run SSH Version 1 or SSH Version 2. • 1—Configure the ML-Series card to run SSH Version 1. • 2—Configure the ML-Series card to run SSH Version 2.
Chapter 19 Configuring Security for the ML-Series Card RADIUS on the ML-Series Card For more information about these commands, see the “Secure Shell Commands” section in the “Other Security Features” chapter of the Cisco IOS Security Command Reference, Cisco IOS Release 12.2, at this URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_r/fothercr.htm. RADIUS on the ML-Series Card RADIUS is a distributed client/server system that secures networks against unauthorized access.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Relay Mode Configuring RADIUS Relay Mode This feature is turned on with CTC or TL1. To enable RADIUS Relay Mode through CTC, go to the card-level view of the ML-Series card, check the Enable RADIUS Relay box and click Apply. The user must be logged in at the Superuser level to complete this task. To enable it using TL1, refer to the Cisco ONS SONET TL1 Command Guide.
Chapter 19 Configuring Security for the ML-Series Card Understanding RADIUS Understanding RADIUS When a user attempts to log in and authenticate to an ML-Series card with access controlled by a RADIUS server, these events occur: 1. The user is prompted to enter a username and password. 2. The username and encrypted password are sent over the network to the RADIUS server. 3. The user receives one of these responses from the RADIUS server: a. ACCEPT—The user is authenticated. b.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Default RADIUS Configuration RADIUS and AAA are disabled by default. To prevent a lapse in security, you cannot configure RADIUS through a network management application. When enabled, RADIUS can authenticate users accessing the ML-Series card through the Cisco IOS CLI.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Command Purpose Step 1 Router # configure terminal Enter global configuration mode. Step 2 Router (config)# aaa new-model Enable AAA. Step 3 Router (config)# radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number] [timeout seconds] [retransmit retries] [key string] Specify the IP address or hostname of the remote RADIUS server host.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS This example shows how to configure host1 as the RADIUS server and to use the default ports for both authentication and accounting: Switch(config)# radius-server host host1 Note You also need to configure some settings on the RADIUS server. These settings include the IP address of the switch and the key string to be shared by both the server and the switch. For more information, see the RADIUS server documentation.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Step 3 Command Purpose Router (config)# aaa authentication login { default | list-name} method1 [method2...] Create a login authentication method list. • To create a default list that is used when a named list is not specified in the login authentication command, use the default keyword followed by the methods that are to be used in default situations. The default method list is automatically applied to all ports.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Step 5 Command Purpose Router (config-line)# login authentication {default | list-name} Apply the authentication list to a line or set of lines. • If you specify default, use the default list created with the aaa authentication login command. • For list-name, specify the list created with the aaa authentication login command. Step 6 Router (config)# end Return to privileged EXEC mode.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Step 3 Command Purpose Router (config)# radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number] [timeout seconds] [retransmit retries] [key string] Specify the IP address or hostname of the remote RADIUS server host. • (Optional) For auth-port port-number, specify the UDP destination port for authentication requests.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS To remove the specified RADIUS server, use the no radius-server host hostname | ip-address global configuration command. To remove a server group from the configuration list, use the no aaa group server radius group-name global configuration command. To remove the IP address of a RADIUS server, use the no server ip-address server group configuration command.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Command Purpose Step 1 Router# configure terminal Enter global configuration mode. Step 2 Router (config)# aaa authorization network radius Configure the ML-Series card for user RADIUS authorization for all network-related service requests. Step 3 Router (config)# aaa authorization exec radius Configure the ML-Series card for user RADIUS authorization if the user has privileged EXEC access.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Identifying the specific ML-Series card that sent the request to the server can be useful in debugging from the server. The nas-ip-address is primarily used for validation of the RADIUS authorization and accounting requests. If this value is not configured, the nas-ip-address is filled in by the normal Cisco IOS mechanism using the value configured by the ip radius-source command.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS Step 5 Command Purpose Router (config)# radius-server deadtime minutes Specify the number of minutes to mark as "dead" any RADIUS servers that fail to respond to authentication requests. A RADIUS server marked as "dead" is skipped by additional authentication requests for the specified number of minutes. This allows trying the next configured server without having to wait for the request to time out before.
Chapter 19 Configuring Security for the ML-Series Card Configuring RADIUS cisco-avpair= “ip:outacl#2=deny ip 10.10.10.10 0.0.255.255 any” Other vendors have their own unique vendor-IDs, options, and associated VSAs. For more information about vendor-IDs and VSAs, see RFC 2138, “Remote Authentication Dial-In User Service (RADIUS).
Chapter 19 Configuring Security for the ML-Series Card Displaying the RADIUS Configuration Step 3 Command Purpose Router (config)# radius-server key string Specify the shared secret text string used between the ML-Series card and the vendor-proprietary RADIUS server. The ML-Series card and the RADIUS server use this text string to encrypt passwords and exchange responses. Note The key is a text string that must match the encryption key used on the RADIUS server.
C H A P T E R 20 POS on ONS Ethernet Cards This chapter describes packet-over-SONET/SDH (POS) and its implementation on ONS Ethernet cards.
Chapter 20 POS on ONS Ethernet Cards POS Interoperability Ethernet to POS Process on ONS Node POS Framing and Encapsulation SONET/SDH circuit Ethernet riding in multiplexed STS (VC) circuit onto Optical Card Optical card port transmits SONET/SDH signal containing data frame across SONET/SDH network Ethernet SONET/SDH POS virtual ports Ethernet ports Optical ports XC Card Ethernet Card Optical Card 115431 Figure 20-1 ONS Node ONS Ethernet cards all use POS.
Chapter 20 POS on ONS Ethernet Cards POS Interoperability The CRC size option does not need to match on the two endpoints when using GFP-F framing mode. All Ethernet cards do not interoperate or support all the POS port characteristic options. The following two tables list the interoperable Ethernet cards and characteristics. Table 20-1 lists this information for cards supporting and configured with high-level data link control (HDLC) framing mode.
Chapter 20 POS on ONS Ethernet Cards POS Encapsulation Types Table 20-2 ONS SONET/SDH Ethernet Card Interoperability under GFP-F Framing with Encapsulation Type ML-Series (ONS 15454) ML-Series (ONS 15310) CE-Series (All Platforms) LEX (CRC 32) LEX (CRC 32) LEX (CRC 32) Cisco HDLC (CRC 32) ML-Series PPP/BCP (CRC 32) (ONS 15454 SONET/SDH) IEEE 802.
Chapter 20 POS on ONS Ethernet Cards LEX Figure 20-2 RPR Data Frames Extended Data Frame Basic Data Frame 1 TTL to Dest 1 Base Control 6 MAC da 6 MAC sa 1 TTL Base 1 Extended Control 2 hec 2 Protocol Type n Service Data Unit 4 FCS Header Payload 1 TTL to Dest 1 Base Control 6 MAC da 6 MAC sa 1 TTL Base 1 Extended Control 2 hec 6 Extended DA 6 Extended SA 2 Protocol Type n Service Data Unit 4 FCS Header Payload 151965 Trailer Trailer LEX The Cisco EoS LEX
Chapter 20 POS on ONS Ethernet Cards PPP/BCP PPP/BCP The PPP encapsulation is a standard implementation of RFC 2615 (PPP-over-SONET/SDH), and provides a standard implementation of RFC 3518 (BCP) to provide the transmission of 802.1Q tagged and untagged Ethernet frames over SONET. Figure 20-4 illustrates BCP.
Chapter 20 POS on ONS Ethernet Cards E-Series Proprietary E-Series Proprietary The E-Series uses a proprietary HDLC-like encapsulation that is incompatible with LEX, Cisco HDLC, or PPP/BCP. This proprietary encapsulation prevents the E-Series from interoperating with other ONS Ethernet cards. In Release 5.0 and later, the ONS 15327 E-Series card, E10/100-4, supports LEX encapsulation with a 16-bit CRC as well as the original proprietary E-Series encapsulation.
Chapter 20 POS on ONS Ethernet Cards ONS 15327 E-10/100-4 Framing and Encapsulation Options ONS 15327 E-10/100-4 Framing and Encapsulation Options For Software Release 5.0 and later, the E-10/100-4 card on the ONS 15327, configured in port-mapped mode, offers the choice of configuring LEX or the original proprietary E-Series encapsulation. When configured for LEX encapsulation, the ONS 15327 E-Series card interoperates with ML-Series cards.
Chapter 20 POS on ONS Ethernet Cards G-Series Encapsulation and Framing Figure 20-8 ONS 15454 and ONS 15454 SDH E-Series Encapsulation and Framing Options Proprietary E-Series Encapsulation Flag Address Control Protocol Payload FCS Transport Overhead SONET/SDH Payload Envelope 115447 HDLC Framing SONET/SDH Frame G-Series Encapsulation and Framing The G-Series cards are supported on the ONS 15454, ONS 15454 SDH, and ONS 15327 platforms. They support LEX encapsulation and HDLC framing.
Chapter 20 POS on ONS Ethernet Cards ONS 15454, ONS 15454 SDH, ONS 15310-CL, and and ONS 15310-MA CE-Series Cards Encapsulation and Framing ONS 15454, ONS 15454 SDH, ONS 15310-CL, and and ONS 15310-MA CE-Series Cards Encapsulation and Framing CE-100T-8 cards are available for the ONS 15454, ONS 15454 SDH, ONS 15310-CL, and ONS 15310-MA platforms. CE-1000-4 cards are available for the ONS 15454 and ONS 15454 SDH platforms. They support HDLC Framing and GFP-F framing.
Chapter 20 POS on ONS Ethernet Cards Ethernet Clocking Versus SONET/SDH Clocking Figure 20-11 ML-Series Card Framing and Encapsulation Options GFP-F Frame Types Cisco HDLC LEX PPP BCP GFP-Cisco HDLC GFP-Mapped Ethernet (LEX) GFP-PPP GFP-BCP Encapsulation Address Control Protocol HDLC Framing Mode Transport Overhead Core Header Payload FCS or Payload Header Payload FCS GFP-F Framing Mode SONET/SDH Payload Envelope 115448 Flag SONET/SDH Frame Ethernet Clocking Versus SONET/SDH Clockin
Chapter 20 POS on ONS Ethernet Cards Ethernet Clocking Versus SONET/SDH Clocking Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 21 Configuring RMON This chapter describes how to configure remote network monitoring (RMON) on the ML-Series card for the ONS 15454 SONET/SDH. RMON is a standard monitoring specification that defines a set of statistics and functions that can be exchanged between RMON-compliant console systems and network probes. RMON provides you with comprehensive network-fault diagnosis, planning, and performance-tuning information.
Chapter 21 Configuring RMON Configuring RMON Figure 21-1 Remote Monitoring Example Network management station with generic RMON console application RMON alarms and events configured. SNMP configured. Workstations Workstations 145951 RMON history and statistic collection enabled.
Chapter 21 Configuring RMON Configuring RMON Alarms and Events Beginning in privileged EXEC mode, follow these steps to enable RMON alarms and events. This procedure is required. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 rmon event number [description string] [log] [owner string] Add an event in the RMON event table that is [trap community] associated with an RMON event number.
Chapter 21 Configuring RMON Configuring RMON Alarms and Events To disable an alarm, use the no rmon alarm number global configuration command on each alarm you configured. You cannot disable all the alarms that you configured by not specifying a specific number. You must disable each alarm separately. To disable an event, use the no rmon event number global configuration command. To learn more about alarms and events and how they interact with each other, see RFC 1757.
Chapter 21 Configuring RMON Collecting Group History Statistics on an Interface Collecting Group History Statistics on an Interface You must first configure RMON alarms and events to display collection information. Beginning in privileged EXEC mode, follow these steps to collect group history statistics on an interface. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode.
Chapter 21 Configuring RMON Collecting Group Ethernet Statistics on an Interface Collecting Group Ethernet Statistics on an Interface Beginning in privileged EXEC mode, follow these steps to collect group Ethernet statistics on an interface. This procedure is optional. Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 interface interface-id Specify the interface on which to collect statistics, and enter interface configuration mode.
Chapter 21 Configuring RMON Threshold and Triggered Actions The user can also configure the CRC-ALARM to trigger a link state down on the port and to wrap an Cisco proprietary RPR . By default, the CRC-ALARM is disabled. When the alarm is configured, the link down and wrap actions are still disabled by default. This feature is also supported on the ML-Series card Ethernet ports.
Chapter 21 Configuring RMON Unwrap Synchronization Before doing a manual clear, the user needs to determine the root cause of a CRC-ALARM and correct it. After that, the user has several alternative methods to manually clear the alarm: • Through the Cisco IOS CLI, enter the clear crc alarm interface interface-type interface-number command at the EXEC level. • Through the Cisco IOS CLI, do an administrative shutdown on the linked ports and then a no shutdown to enable the ports.
Chapter 21 Configuring RMON Unwrap Synchronization Figure 21-2 Wrapped Cisco proprietary RPR with Unidirectional Excessive CRC Errors Node B Figure 21-3illustrates the unwrap sequence for Figure 21-2. The traffic hit for the unwrap is dependent on the soak time required to declare PDI cleared on node D. Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 21 Configuring RMON Unwrap Synchronization Figure 21-3 Unwrapped Cisco proprietary RPR with Unidirectional Excessive CRC Errors Node B N d C Bidirectional Errors Figure 21-4 shows a Cisco proprietary RPR wrapped by excessive bidirectional CRC errors, both ports are reporting CRC-ALARMs. The figure captions further explain the process. Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 21 Configuring RMON Unwrap Synchronization Figure 21-4 Wrapped Cisco proprietary RPR with Bidirectional Excessive CRC Errors Node B Node C Figure 21-5 illustrates the first part of the unwrap sequence for Figure 21-4. This occurs after the unwrap command is configured on node E. For unwrap in this bidirectional scenario, the user must configure the command on the POS ports at both ends of the link. Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 21 Configuring RMON Unwrap Synchronization Figure 21-5 First Stage of Unwrapped Cisco proprietary RPR with Bidirectional Excessive CRC Errors Node B Node C User issues unwrap command. Node E has not unwrapped POS port 1 after the first CRC-ALARM clear command. Since node D continues to send PDI to node E, node E will raise the TPTFAIL alarm once the CRC-ALARM is cleared. At this point, the Cisco proprietary RPR is in a state similar to the unidirectional failure.
Chapter 21 Configuring RMON Configuring the ML-Series Card CRC Error Threshold Figure 21-6 Second Stage of Unwrapped Cisco proprietary RPR with Bidirectional Excessive CRC Errors Node B Node C Configuring the ML-Series Card CRC Error Threshold Beginning in privileged EXEC mode, follow these steps to configure the ML-Series card CRC error threshold: Command Purpose Step 1 ML_Series# configure terminal Enter global configuration mode.
Chapter 21 Configuring RMON Clearing the CRC-ALARM Wrap with the Clear CRC Error Command Step 3 Command Purpose ML_Series (config-if)# [no] trigger crc threshold [threshold-value] Sets an fcs error level as a percentage of bandwidth to trip the SONET/SDH CRC-ALARM. Valid values are: • 2—10e-2 or 1% traffic (1 CRC error in100 packets) • 3—10e-3 or 0.1% traffic (1 CRC error in 1000 packets) (default) • 4—10e-4 or 0.
Chapter 21 Configuring RMON Configuring ML-Series Card RMON for CRC Errors Beginning in privileged EXEC mode, follow these steps to clear the ML-Series card CRC-ALARM: Step 1 Command Purpose ML_Series # clear crc alarm interface interface-type interface-number Clears the SONET/SDH CRC-ALARM and allows the Cisco proprietary RPR to unwrap when conditions are met.
Chapter 21 Configuring RMON Configuring an SNMP Trap for the CRC Error Threshold Using Cisco IOS Configuring an SNMP Trap for the CRC Error Threshold Using Cisco IOS The ML-Series card supports RMON trap functionality in Cisco IOS. You must use the Cisco IOS CLI to configure RMON to monitor ifInErrors and generate a trap to an NMS when a threshold is crossed.
Chapter 21 Configuring RMON Configuring an SNMP Trap for the CRC Error Threshold Using Cisco IOS Step 3 Command Purpose rmon alarm number ifInErrors.ifIndex-number interval {absolute | delta} rising-threshold value [event-number] falling-threshold value [event-number] [owner string] Set an alarm on the MIB object. • For number, specify the alarm number. The range is 1 to 65535. • The ifIndex-number variable is the ifIndex number of an ML-Series card interface in decimal form.
Chapter 21 Configuring RMON Determining the ifIndex Number for an ML-Series Card 2005-03-22 16:25:38 ptlm9-454e56-97.cisco.com [10.92.56.97]: SNMPv2-MIB:sysUpTime.0 = Wrong Type (should be Timeticks): 43026500 SNMPv2-MIB:snmpTrapOID.0 = OID: RMON-MIB:risingAlarm RFC1271-MIB:alarmIndex.9 = 9 RFC1271-MIB:alarmVariable.9 = OID: IF-MIB:ifInErrors.983043 RFC1271-MIB:alarmSampleType.9 = deltaValue(2) RFC1271-MIB:alarmValue.9 = 1002 RFC1271-MIB:alarmRisingThreshold.9 = 1000 SNMPv2-SMI:snmpModules.18.1.3.
Chapter 21 Configuring RMON Manually Checking CRC Errors on the ML-Series Card Table 21-1 ML100T-12 FastEthernet Interfaces Port Numbers for the Interfaces of ML-Series Cards ML100T-12 POS Interfaces FE 7 = Port 7 ML100X-8 FastEthernet Interfaces ML100X-8 POS Interfaces ML1000-2 Gigabit Ethernet Interfaces ML1000-2 POS Interfaces FE 7 = Port 7 FE 8 = Port 8 FE 9 = Port 9 FE 10 = Port 10 FE 11 = Port 11 The slot and port are combined to form the ifIndex using the following formula: ifIndex = (slot
Chapter 21 Configuring RMON Displaying RMON Status ML_Series(config)# show interface pos 0 POS0 is up, line protocol is up Hardware is Packet/Ethernet over Sonet, address is 0005.9a39.713e (bia 0005.9a39.
Chapter 21 Configuring RMON Displaying RMON Status Event 10 is active, owned by config Description is Event firing causes log and trap to community slot15, last event fired at 0y3w2d,00:32:39, Current uptime 0y3w6d,03:03:12 Current log entries: index uptime description 1 0y3w2d,00:32:39 Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 21 Configuring RMON Displaying RMON Status Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 22 Configuring SNMP This chapter describes how to configure the ML-Series card for operating with Simple Network Management Protocol (SNMP). Note For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2.
Chapter 22 Configuring SNMP SNMP on the ML-Series Card • Using SNMP to Access MIB Variables, page 22-4 • Supported MIBs, page 22-5 • SNMP Notifications, page 22-5 SNMP on the ML-Series Card SNMP operates in two different ways on the ONS 15454 SONET/SDH ML-Series card. One way is to communicate directly. This is also how SNMP operates on a small Catalyst switch, using direct communication, Cisco IOS, and the data plane.
Chapter 22 Configuring SNMP SNMP Versions SNMP Versions Both the ML-Series card and the ONS 15454 SONET/SDH nodes support SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c), defined as: • SNMPv1—The Simple Network Management Protocol, a full Internet standard, defined in RFC 1157.
Chapter 22 Configuring SNMP SNMP Agent Functions SNMP Agent Functions The SNMP agent responds to SNMP manager requests as follows: • Get a MIB variable—The SNMP agent begins this function in response to a request from the NMS. The agent retrieves the value of the requested MIB variable and responds to the NMS with that value. • Set a MIB variable—The SNMP agent begins this function in response to a message from the NMS.
Chapter 22 Configuring SNMP Supported MIBs Supported MIBs The complete list of supported MIBs for the ML-Series card is found in the MIBsREADME.txt file on the ONS Software CD for your release. This software CD also includes the needed MIB modules and information on loading MIBs. You can also locate and download MIBs for Cisco platforms, Cisco IOS releases, and feature sets, using the Cisco MIB Locator found at the following URL: http://www.cisco.
Chapter 22 Configuring SNMP Configuring SNMP Configuring SNMP This section describes how to configure SNMP on your ML-Series card.
Chapter 22 Configuring SNMP Disabling the SNMP Agent • An SNMP engine ID is a name for the local or remote SNMP engine. Disabling the SNMP Agent Beginning in privileged EXEC mode, follow these steps to disable the SNMP agent: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 no snmp-server Disable the SNMP agent operation. Step 3 end Return to privileged EXEC mode. Step 4 show running-config Verify your entries.
Chapter 22 Configuring SNMP Configuring Community Strings Beginning in privileged EXEC mode, follow these steps to configure a community string on the ML-Series card: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 snmp-server community string [view view-name] [ro | rw] [access-list-number] Configure the community string.
Chapter 22 Configuring SNMP Configuring SNMP Groups and Users This example shows how to assign the string comaccess to SNMP, to allow read-only access, and to specify that IP access list 4 can use the community string to gain access to the ML-Series card SNMP agent: ML_Series(config)# snmp-server community comaccess ro 4 Configuring SNMP Groups and Users You can specify an identification name (engine ID) for the local or remote SNMP server engine on the ML-Series card.
Chapter 22 Configuring SNMP Configuring SNMP Notifications Step 4 Command Purpose snmp-server user username groupname [remote host [udp-port port]] {v1 | v2c [access access-list]} Configure a new user to an SNMP group. • The username is the name of the user on the host that connects to the agent. • The groupname is the name of the group with which the user is associated.
Chapter 22 Configuring SNMP Configuring SNMP Notifications Beginning in privileged EXEC mode, follow these steps to configure the ML-Series card to send traps or inform requests to a host: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 snmp-server engineID remote ip-address engineid-string Specify the IP address and engine ID for the remote host.
Chapter 22 Configuring SNMP Setting the Agent Contact and Location Information Command Purpose Step 6 snmp-server trap-source interface-id (Optional) Specify the source interface, which provides the IP address for the trap message. This command also sets the source IP address for inform requests. Step 7 snmp-server queue-length length (Optional) Establish how many trap messages each trap host can hold (message queue length.) The range is 1 to 1000; the default is 10.
Chapter 22 Configuring SNMP Limiting TFTP Servers Used Through SNMP Limiting TFTP Servers Used Through SNMP Beginning in privileged EXEC mode, follow these steps to limit the TFTP servers used for saving and loading configuration files through SNMP to the servers specified in an access list: Command Purpose Step 1 configure terminal Enter global configuration mode.
Chapter 22 Configuring SNMP Displaying SNMP Status This example shows how to allow read-only access for all objects to members of access list 4 that use the comaccess community string. No other SNMP managers have access to any objects. SNMP authentication failure traps are sent by SNMPv2c to the host cisco.com using the community string “public.” ML_Series(config)# snmp-server community comaccess ro 4 ML_Series(config)# snmp-server enable traps snmp authentication ML_Series(config)# snmp-server host cisco.
C H A P T E R 23 E-Series and G-Series Ethernet Operation Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 23 E-Series and G-Series Ethernet Operation G1K-4 and G1000-4 Comparison • High availability (HA), including hitless (< 50 ms) performance with software upgrades and all types of SONET/SDH equipment protection switches • Hitless reprovisioning • Support of Gigabit Ethernet traffic at full line rate • Full TL1-based provisioning capability • Serviceability options including enhanced port states, terminal and facility loopback, and J1 path trace • SONET/SDH-style alarm support • Ethernet
Chapter 23 E-Series and G-Series Ethernet Operation G-Series Example Software R4.0 and later identifies G1K-4 cards at physical installation. Software R3.4 and earlier identifies both G1000-4 and G1K-4 cards as G1000-4 cards at physical installation. G-Series Example Figure 23-1 shows a G-Series application. In this example, data traffic from the Gigabit Ethernet port of a high-end router travels across the ONS node’s point-to-point circuit to the Gigabit Ethernet port of another high-end router.
Chapter 23 E-Series and G-Series Ethernet Operation Gigabit EtherChannel/IEEE 802.3ad Link Aggregation When both autonegotiation and flow control are enabled, the G-Series card proposes symmetrical flow control to the attached Ethernet device. Flow control may be used or not depending on the result of the autonegotiation. If autonegotiation is enabled but flow control is disabled, then the G-Series proposes no flow control during the autonegotiation.
Chapter 23 E-Series and G-Series Ethernet Operation Ethernet Link Integrity Support Although the G-Series cards do not actively run GEC, they support the end-to-end GEC functionality of attached Ethernet devices. If two Ethernet devices running GEC connect through G-Series cards to an ONS network, the ONS SONET/SDH side network is transparent to the EtherChannel devices. The EtherChannel devices operate as if they are directly connected to each other.
Chapter 23 E-Series and G-Series Ethernet Operation Administrative and Service States with Soak Time for Ethernet and SONET/SDH Ports Administrative and Service States with Soak Time for Ethernet and SONET/SDH Ports The G-Series card supports the administrative and service states for the Ethernet ports and the SONET/SDH circuit.
Chapter 23 E-Series and G-Series Ethernet Operation G-Series Manual Cross-Connects On the ONS 15454 and ONS 15327, provisionable SONET circuit sizes are STS 1, STS 3c, STS 6c, STS 9c, STS 12c, STS 24c, and STS 48c. On the ONS 15454 SDH, provisionable SDH circuits are VC4, VC4-2c, VC4-3c, VC4-4c, VC4-8c, and VC4-16c. Each Ethernet port maps to a unique STS/VC circuit on the G-Series card.
Chapter 23 E-Series and G-Series Ethernet Operation G-Series Gigabit Ethernet Transponder Mode Figure 23-5 G-Series Manual Cross-Connects Non-ONS Network ONS Node SONET/SDH Ethernet 47093 ONS Node G-Series Gigabit Ethernet Transponder Mode The ONS 15454 and ONS 15454 SDH G-Series cards can be configured as transponders. ONS 15327 G-Series cards cannot be configured as transponders.
Chapter 23 E-Series and G-Series Ethernet Operation G-Series Gigabit Ethernet Transponder Mode A G-Series card configured as a transponder operates quite differently than a G-Series card configured for SONET/SDH. In SONET/SDH configurations, the G-Series card receives and transmits Gigabit Ethernet traffic out the Ethernet ports and GBICs on the front of the card. This Ethernet traffic is multiplexed on and off the SONET/SDH network through the cross-connect card and the optical card (Figure 23-7).
Chapter 23 E-Series and G-Series Ethernet Operation Two-Port Bidirectional Transponder Mode A G-Series card can be configured either for transponder mode or as the SONET/SDH default. When any port is provisioned in transponder mode, the card is in transponder mode and no SONET/SDH circuits can be configured until every port on the card goes back to SONET/SDH mode. To provision G-Series ports for transponder mode, refer to the Cisco ONS 15454 Procedure Guide or the Cisco ONS 15454 SDH Procedure Guide.
Chapter 23 E-Series and G-Series Ethernet Operation Two-Port Unidirectional Transponder Mode Gigabit Ethernet Ports Figure 23-9 One-Port Bidirectional Transponder Mode xWDM Lambda 1 xWDM Lambda 2 xWDM Lambda 3 xWDM Lambda 4 Ethernet TDM G-Series Card Cross-Connect Card Optical Card GBIC Standard SX, LX, ZX Tx Port Rx Port GBIC CWDM or DWDM Tx Port Rx Port Note: This configuration can be used when the client terminal's optical signal is single-mode, 1310 nm, 1550 nm, or 15xx.xx nm.
Chapter 23 E-Series and G-Series Ethernet Operation G-Series Transponder Mode Characteristics Gigabit Ethernet Ports Figure 23-10 Two-Port Unidirectional Transponder X xWDM Lambda 1 X X xWDM Lambda 2 X Ethernet TDM G-Series Card Cross-Connect Card Optical Card ONS Node Tx Port Rx Port GBIC CWDM or DWDM Tx Port Rx Port Note: This configuration must be used when the client terminal's optical signal is multimode, 850 nm.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Application Note In normal SONET/SDH mode, the G-Series cards supports an end-to-end link integrity function. This function causes an Ethernet or SONET/SDH failure to disable and turn the transmitting laser off in the corresponding mapped Ethernet port. In transponder mode, the loss of signal on an Ethernet port has no impact on the transmit signal of the corresponding mapped port.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Modes E-Series Multicard EtherSwitch Group Multicard EtherSwitch group provisions two or more Ethernet cards to act as a single Layer 2 switch. Figure 23-11 illustrates a multicard EtherSwitch configuration.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Modes Figure 23-12 Single-Card EtherSwitch Configuration Ethernet card 1 Ethernet card 2 Router Router VLAN A ONS Node ONS Node VLAN B Ethernet card 3 Router 45132 Ethernet card 4 Router Port-Mapped (Linear Mapper) Port-mapped mode, also referred to as linear mapper, configures the E-Series card to map a specific E-Series Ethernet port to one of the card’s specific STS/VC circuits (Figure 23-13).
Chapter 23 E-Series and G-Series Ethernet Operation E-Series IEEE 802.3z Flow Control Port-mapped mode also allows the creation of STS/VC circuits between any two E-Series cards, including the E100T-G, E1000-2-G, and the E10/100-4 (the ONS 15327 E-Series card). Port-mapped mode does not allow ONS 15454 E-Series cards to connect to the ML-Series or G-Series cards, but does allow an ONS 15327 E10/100-4 card provisioned with LEX encapsulation to connect to the ML-Series or G-Series cards.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series VLAN Support For the E100T-G or E10/100-4 (operating in any mode) and the E1000-2-G (operating port-mapped mode), flow control matches the sending and receiving device throughput to that of the bandwidth of the STS circuit. This same concept applies to the ONS 15454, ONS 15454 SDH and ONS 15327. For example, a router might transmit to the Gigabit Ethernet port on the E-Series in port-mapped mode.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Q-Tagging (IEEE 802.1Q) Figure 23-14 Edit Circuit Dialog Box Featuring Available VLANs E-Series Q-Tagging (IEEE 802.1Q) E-Series cards in single-card and multicard mode support IEEE 802.1Q. IEEE 802.1Q allows the same physical port to host multiple IEEE 802.1Q VLANs. Each IEEE 802.1Q VLAN represents a different logical network. E-Series cards in port-mapped mode transport IEEE 802.1Q tags (Q-tags), but do not remove or add these tags.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Q-Tagging (IEEE 802.1Q) Figure 23-15 Q-tag Moving Through VLAN Data Flow Q-tag The receiving ONS node removes the Q-tag and forwards the frame to the specific VLAN. Example 1. The ONS node uses a Q-tag internally to deliver the frame to a specific VLAN. Q-tag Example 2. The ONS node receives a frame with a Q-tag and passes it on. No tag Q-tag Q-tag The receiving ONS node receives a frame with a Q-tag and passes it on.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Priority Queuing (IEEE 802.1Q) E-Series Priority Queuing (IEEE 802.1Q) Networks without priority queuing handle all packets on a first-in-first-out (FIFO) basis. Priority queuing reduces the impact of network congestion by mapping Ethernet traffic to different priority levels. The E-Series card supports priority queuing. The E-Series card maps the eight priorities specified in IEEE 802.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Spanning Tree (IEEE 802.1D) Note IEEE 802.1Q was formerly known as IEEE 802.1P. Note E-Series cards in port-mapped mode and G-Series cards do not support priority queing (IEEE 802.1Q). E-Series Spanning Tree (IEEE 802.1D) The E-Series operates IEEE 802.1D Spanning Tree Protocol (STP). The E-Series card supports common STPs on a per-circuit basis up to a total of eight STP instances. It does not support per-VLAN STP.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Spanning Tree (IEEE 802.1D) Figure 23-18 Spanning Tree Map on Circuit Window Note Green represents forwarding spans and purple represents blocked (protect) spans. If you have a packet ring configuration, at least one span should be purple. Caution Multiple circuits with STP protection enabled will incur blocking if the circuits traverse a common card and use the same VLAN. Note E-Series port-mapped mode does not support STP (IEEE 802.1D).
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Circuit Configurations Table 23-4 Spanning Tree Parameters Parameter Description BridgeID ONS node unique identifier that transmits the configuration bridge protocol data unit (BPDU); the bridge ID is a combination of the bridge priority and the ONS node MAC address. TopoAge Amount of time in seconds since the last topology change. TopoChanges Number of times the STP topology has been changed since the node booted up.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Circuit Protection E-Series Circuit Protection Different combinations of E-Series circuit configurations and SONET/SDH network topologies offer different levels of E-Series circuit protection. Table 23-6 details the available protection.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Shared Packet Ring Ethernet Circuits Figure 23-20 Single-Card EtherSwitch or Port-Mapped Point-to-Point Circuit 192.168.1.25 255.255.255.0 VLAN test Slot 4 Note ONS 15454 2 ONS 15454 3 192.168.1.50 255.255.255.0 VLAN test Slot 15 32161 ONS 15454 1 A port-mapped, point-to-point circuit cannot join an E-Series port-based VLAN, but can transport external VLANs.
Chapter 23 E-Series and G-Series Ethernet Operation E-Series Hub-and-Spoke Ethernet Circuit Provisioning E-Series Hub-and-Spoke Ethernet Circuit Provisioning The hub-and-spoke configuration connects point-to-point circuits (the spokes) to an aggregation point (the hub). In many cases, the hub links to a high-speed connection and the spokes are Ethernet cards. Figure 23-22 illustrates a hub-and-spoke ring. Your network architecture might differ from the example.
Chapter 23 E-Series and G-Series Ethernet Operation Remote Monitoring Specification Alarm Thresholds interval. For example, if a threshold is set at 1000 collisions and 1001 collisions occur during the 15-minute interval, an event triggers. CTC allows you to provision these thresholds for Ethernet statistics. For Ethernet RMON alarm threshold procedures, refer to the Cisco ONS 15454 Troubleshooting Guide, Cisco ONS 15454 Troubleshooting Guide or Cisco ONS 15327 Troubleshooting Guide.
Chapter 23 E-Series and G-Series Ethernet Operation Remote Monitoring Specification Alarm Thresholds Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 24 CE-100T-8 Ethernet Operation This chapter describes the operation of the CE-100T-8 (Carrier Ethernet) card supported on the ONS 15454 and ONS 15454 SDH. A CE-100T-8 card installed in an ONS 15454 SONET is restricted to SONET operation, and a CE-100T-8 card installed in an ONS 15454 SDH is restricted to SDH operation. Another version of the CE-100T-8 card is supported on the ONS 15310-CL. Provisioning is done through Cisco Transport Controller (CTC) or Transaction Language One (TL1).
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 Ethernet Features The CE-100T-8 card carries any Layer 3 protocol that can be encapsulated and transported over Ethernet, such as IP or IPX. The Ethernet frame from the data network is transmitted on the Ethernet cable into the standard RJ-45 port on a CE-100T-8 card. The CE-100T-8 card transparently maps Ethernet frames into the SONET/SDH payload using packet-over-SONET/SDH (POS) encapsulation.
Chapter 24 CE-100T-8 Ethernet Operation Ethernet Link Integrity Support To prevent over-subscription, buffer memory is available for each port. When the buffer memory on the Ethernet port nears capacity, the CE-100T-8 uses IEEE 802.3x flow control to transmit a pause frame to the attached Ethernet device. Flow control and autonegotiation frames are local to the Fast Ethernet interfaces and the attached Ethernet devices. These frames do not continue through the POS ports.
Chapter 24 CE-100T-8 Ethernet Operation Administrative and Service States with Soak Time for Ethernet and SONET/SDH Ports Note Some network devices can be configured to ignore a loss of carrier condition. If a device configured to ignore a loss of carrier condition attaches to a CE-100T-8 card at one end, alternative techniques (such as use of Layer 2 or Layer 3 keep-alive messages) are required to route traffic around failures.
Chapter 24 CE-100T-8 Ethernet Operation IEEE 802.1Q CoS and IP ToS Queuing IEEE 802.1Q CoS and IP ToS Queuing The CE-100T-8 references IEEE 802.1Q class of service (CoS) thresholds and IP type of service (ToS) (IP Differentiated Services Code Point [DSCP]) thresholds for priority queueing. CoS and ToS thresholds for the CE-100T-8 are provisioned on a per port level.
Chapter 24 CE-100T-8 Ethernet Operation RMON and SNMP Support Table 24-2 CoS Priority Queue Mappings (continued) CoS Setting in CTC CoS Values Sent to Priority Queue 4 5, 6, 7 3 4, 5, 6, 7 2 3, 4, 5, 6, 7 1 2, 3, 4, 5, 6, 7 0 1, 2, 3, 4, 5, 6, 7 Ethernet frames without VLAN tagging use ToS-based priority queueing if both ToS and CoS priority queueing is active on the card.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 SONET/SDH Circuits and Features CE-100T-8 SONET/SDH Circuits and Features The CE-100T-8 has eight POS ports, numbered one through eight, which can be managed with CTC or TL1. Each POS port is statically mapped to a matching Ethernet port. By clicking the card-level Provisioning > POS Ports tab, the user can configure the Administrative State, Framing Type, and Encapsulation Type.
Chapter 24 CE-100T-8 Ethernet Operation Available Circuit Sizes and Combinations Table 24-6 SDH Circuit Sizes and Ethernet Services Ethernet Wire Speed CCAT VC-3 VCAT VC-12 VCAT 1 Line Rate 100BASE-T VC-4 VC-3-3v, VC-3-2v Sub Rate 100BASE-T VC-3 VC-3-1v VC-12-xv (x=1-49) Line Rate 10BBASE-T VC-3 VC-3-1v VC-12-5v Sub Rate 10BASE-T Not applicable VC-12-xv (x=1-4) Not applicable VC-12-xv (x=50-63) 1. VC-3-2v provides a total transport capacity of 98 Mbps.
Chapter 24 CE-100T-8 Ethernet Operation Available Circuit Sizes and Combinations Table 24-9 VCAT High-Order Circuit Combinations for STS-1-3v and STS-1-2v SONET (continued) Number of STS-1-3v Circuits Maximum Number of STS-1-2v Circuits 3 1 4 None Table 24-10 shows VC-3-3v and VC-3-2v circuit size combinations available for the CE-100T-8 on the ONS 15454 SDH.
Chapter 24 CE-100T-8 Ethernet Operation Available Circuit Sizes and Combinations Table 24-11 CE-100T-8 Illustrative Service Densities for SONET (continued) Service Combination STS-3c or STS-1-3v STS-1-2v STS-1 VT1.5-xV Number of Active Service 14 1 1 1 5 (x=1–28) 8 15 1 0 7 0 8 16 1 0 3 4 (x=1–42) 8 17 1 0 0 7 (x=1–42) 8 18 0 4 4 0 8 19 0 3 3 2 (x=1–42) 8 20 0 0 8 0 8 21 0 0 4 4 (x=1–42) 8 22 0 0 0 8 (x=1–42) 8 1.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 Pools Table 24-12 CE-100T-8 Sample Service Densities for SDH (continued) Service Combination VC-4 or VC-3-3v VC-3-2v VC-3 VC-12-xv 19 0 3 3 1 (x=1–32) plus 1 (x=1–31) 8 20 0 0 8 0 8 21 0 0 4 2 (x=1–32) plus 2 (x=1–31) 8 22 0 0 0 4 (x=1–32) plus 4 (x=1–31) 8 2 Number of Active Service These service combinations require creating the VC-12-xv circuit before you create the VC-3 circuits.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 Pools Figure 24-4 CE-100T-8 Allocation Tab for SDH Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 Pools Figure 24-5 CE-100T-8 STS/VT Allocation Tab Both Port 6 and Port 7 belong to Pool 1 CE-100T-8 Pool Allocation Example This information can be useful in freeing up the bandwidth required for provisioning a circuit if there is not enough existing capacity in any one pool for provisioning the desired circuit.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 VCAT Characteristics CE-100T-8 Pool Provisioning Rules All VCAT circuit members must be from the same pool. One of the four memory pools is reserved for the low-order VCAT circuits if sufficient bandwidth exists to support the high-order circuits in the remaining three pools. The high-order CCAT circuits use all the available capacity from a single memory pool before beginning to use the capacity of a new pool.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 Loopback, J1 Path Trace, and SONET/SDH Alarms CE-100T-8 Loopback, J1 Path Trace, and SONET/SDH Alarms The CE-100T-8 card supports terminal and facility loopbacks. It also reports SONET/SDH alarms and transmits and monitors the J1 Path Trace byte in the same manner as OC-N cards.
Chapter 24 CE-100T-8 Ethernet Operation CE-100T-8 Loopback, J1 Path Trace, and SONET/SDH Alarms Ethernet Card Software Feature and Configuration Guide, R7.
C H A P T E R 25 CE-1000-4 Ethernet Operation Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 25 CE-1000-4 Ethernet Operation CE-1000-4 Ethernet Features Figure 25-1 CE-1000-4 Point-to-Point Circuit ONS Node Point-to-Point Circuit ONS Node Ethernet 115781 Ethernet The CE-1000-4 cards allow you to provision and manage an Ethernet private line service like a traditional SONET/SDH line. The CE-1000-4 card provides carrier-grade Ethernet private line services and high-availability transport.
Chapter 25 CE-1000-4 Ethernet Operation Autonegotiation and Frame Buffering Note Many Ethernet attributes are also available through the network element (NE) defaults feature. For more information on NE defaults, refer to the "Network Element Defaults" appendix in the Cisco ONS 15454 Reference Manual or the Cisco ONS 15454 SDH Reference Manual. Autonegotiation and Frame Buffering On the CE-1000-4 card, Ethernet link autonegotiation is on by default.
Chapter 25 CE-1000-4 Ethernet Operation Flow Control Threshold Provisioning In pass-through mode, transmit flow control frames are not generated by the Ethernet port interfaces, and received flow control frames pass through transparently. Pass-through mode supports end-to-end flow control between clients using Ethernet over SONET/SDH transport.
Chapter 25 CE-1000-4 Ethernet Operation Administrative and Service States with Soak Time for Ethernet and SONET/SDH Ports Administrative and Service States with Soak Time for Ethernet and SONET/SDH Ports The CE-1000-4 card supports the administrative and service states for the Ethernet ports and the SONET/SDH circuit.
Chapter 25 CE-1000-4 Ethernet Operation Statistics and Counters Statistics and Counters The CE-1000-4 has a full range of Ethernet and POS statistics information under the Performance > Ether Ports tabs or the Performance > POS Ports tabs. CE-1000-4 SONET/SDH Circuits and Features The CE-1000-4 card has four POS ports, numbered one through four, which can be managed with CTC or TL1. Each POS port is statistically mapped to a matching Ethernet port.
Chapter 25 CE-1000-4 Ethernet Operation CE-1000-4 POS Encapsulation, Framing, and CRC • Add or remove cross-connect circuits from VCGs • Automatically remove errored members from the group Adding or removing members from the VCG is service-affecting. Adding or removing cross-connect circuits is not service-affecting, if the asociated members are not in the group The CE-1000-4 card also supports fixed (pure or non-flexible) VCGs.
Chapter 25 CE-1000-4 Ethernet Operation CE-1000-4 Loopback, J1 Path Trace, and SONET/SDH Alarms The user can provision framing on the CE-1000-4 as either the default frame-mapped generic framing procedure framing (GFP-F) or high-level data link control (HDLC) framing. With GFP-F framing, the user can also configure a 32-bit CRC (default) or no CRC (none). When LEX is used over GFP-F it is standard Mapped Ethernet over GFP-F according to ITU-T G.7041. HDLC framing provides a set 32-bit CRC.
C H A P T E R 26 Configuring IEEE 802.17b Resilient Packet Ring Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RPR-IEEE Features on the ML-Series Card Note Throughout this book, Cisco proprietary RPR is referred to as Cisco proprietary RPR, and IEEE 802.17b-based RPR is referred to as RPR-IEEE. This chapter covers RPR-IEEE. Chapter 17, “Configuring Cisco Proprietary Resilient Packet Ring” covers Cisco Proprietary RPR.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RPR-IEEE Framing Process An RPR-IEEE is made up of dual counter-rotating rings (ringlets), one for clockwise or west data traffic and one for counter-clockwise or east data traffic. The ringlets are identified as Ringlet 0 and Ringlet 1 in Figure 26-1. The west ringlet traffic is transmitted out the west interface and received by the east interface. The east ringlet traffic is transmitted out the east interface and received by the west interface.
Chapter 26 Configuring IEEE 802.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RPR-IEEE Framing Process Figure 26-3 illustrates the RPR-IEEE topology and protection control frame. Topology and protection (TP) frames are usually sent to the broadcast address.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring CTM and RPR-IEEE Figure 26-4 Fairness Frame Format 1 TTL 1 Base Control 6 SA Compact 2 Fairness Header 2 Fair Rate 4 FCS Header Trailer 151966 Payload For comparison of RPR-IEEE frames and Cisco proprietary RPR frames, see the “Cisco Proprietary RPR Framing Process” section on page 17-5 for Cisco proprietary RPR framing information.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring the Attribute Discovery Timer – Configuring Fairness Weights, page 26-19 – Configuring RPR-IEEE Service Classes Using the Modular QoS CLI, page 26-19 Configuring the Attribute Discovery Timer Because station attributes are communicated separately from topology and protection packets, there is a separate timer to control the frequency at which these packets are sent.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring BER Threshold Values To configure the reporting of SONET/SDH alarms on the Cisco IOS CLI, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring the Hold-off Timer Figure 26-5 Each RPR-IEEE Node Responding to a Protection Event by Steering Ringlet 1 (east) steering fiber break steering steering steering 151970 Ringlet 0 (west) You can modify many of the RPR-IEEE protection characteristics with the procedures in the following sections.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring Jumbo Frames To enable and configure the hold-off timer, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface. Step 2 Router(config-if)# rpr-ieee protection sonet holdoff-timer time [east | west] Specifies the delay before a protection response is sent.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring Forced or Manual Switching To enable and configure Jumbo frames, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring Protection Timers To enable and configure forced or manual switching, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring the Wait-to-Restore Timer To enable and configure the protection timers, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring a Span Shutdown Configuring a Span Shutdown The rpr-ieee shutdown command performs the same task as the rpr-ieee protection request forced-switch command. To cause a forced switch on the span of the interface, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring Triggers for CRC Errors To enable and configure the keepalives, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring Triggers for CRC Errors To enable and configure the triggers for CRC errors, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface rpr-ieee 0 Activates interface configuration mode to configure the RPR-IEEE interface.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring QoS on RPR-IEEE Command Purpose Step 5 Router(config)# no shut Enables the RPR-IEEE interface and changes the mode from the default passthrough. Step 6 Router(config)# end Returns to privileged EXEC mode. Step 7 Router# copy running-config startup-config (Optional) Saves configuration changes to the TCC2/TCC2P flash database.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring ClassC ClassC This is the lowest traffic priority. Class C cannot allocate any ring bandwidth guarantees MQC -IEEE RPR CLI Characteristics • IEEE-RPR classes are applicable to both front end and RPR-IEEE interfaces. • A MQC class in a policy map can be mapped to one of the RPR classes using "set rpr-ieee service class". By default the MQC class maps to IEEE-RPR class C.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring Fairness Weights Command Purpose Step 4 Router(config)# end Returns to privileged EXEC mode. Step 5 Router# copy running-config startup-config (Optional) Saves configuration changes to the TCC2/TCC2P flash database. Configuring Fairness Weights RPR-IEEE has a configurable fairness system, used to control congestion on each ringlet.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring RPR-IEEE Service Classes Using the Modular QoS CLI • Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at this URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122mindx/l22index.htm • Cisco IOS Quality of Service Solutions Command Reference, Release 12.2 at this URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_r/index.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuration Example for RPR-IEEE QoS Command Purpose Step 7 Router(config)# exit Exits class mode. Step 8 Router(config)# no shut Enables the RPR-IEEE interface and changes the mode from the default passthrough. Step 9 Router(config)# end Returns to privileged EXEC mode. Step 10 Router# copy running-config startup-config (Optional) Saves configuration changes to the TCC2/TCC2P flash database.
Chapter 26 Configuring IEEE 802.
Chapter 26 Configuring IEEE 802.
Chapter 26 Configuring IEEE 802.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Verifying and Monitoring RPR-IEEE Local Congestion: Congested? No Head? No Local Fair Rate: Approximate Bandwidth: 0 Kbps 0 normalized bytes per aging interval 0 bytes per ageCoef aging interval Downstream Congestion: Congested? No Tail? No Received Source Address: 0000.0000.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Verifying and Monitoring RPR-IEEE Example 26-6 show rpr-ieee topology detail Output Note The ip address field in the output of show rpr-ieee topology detail is populated only by the IP address that is applied to the rpr 0 main interface. It is not populated by the IP address of any of the sub-interfaces. router# show rpr-ieee topology detail 802.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Verifying and Monitoring RPR-IEEE ringlet0: NO ringlet1: NO Preferred protection mode: STEERING Jumbo preference: NOT SET (ring doesn't supports JUMBOS) Measured LRTT: 0 Sequence Number: 3 ATD INFO: Station Name: ML100X-491 A0 reserved Bandwidth: ringlet0: 0 mbpsringlet1: 0 mbps SAS enabled: YES Weight: ringlet0: 1ringlet1: 1 Secondary Mac Addresses: MAC 1: 0000.0000.0000 (UNUSED) MAC 2: 0000.0000.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Verifying and Monitoring RPR-IEEE Topology entry at Index 4 on ringlet 0: Station MAC address: 0013.1991.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Verifying and Monitoring RPR-IEEE ATD INFO: Station Name: ML100T-482 A0 reserved Bandwidth: ringlet0: 0 mbpsringlet1: 0 mbps SAS enabled: YES Weight: ringlet0: 1ringlet1: 1 Secondary Mac Addresses: MAC 1: 0000.0000.0000 (UNUSED) MAC 2: 0000.0000.0000 (UNUSED) ======================================================================= Topology entry at Index 2 on ringlet 1: Station MAC address: 0005.9a39.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuring RPR-IEEE End-to-End Advertised Protection requests: ringlet0: IDLEringlet1: IDLE Active Edges: ringlet0: NO ringlet1: NO Preferred protection mode: STEERING Jumbo preference: NOT SET (ring doesn't supports JUMBOS) Measured LRTT: 0 Sequence Number: 3 ATD INFO: Station Name: ML100X-491 A0 reserved Bandwidth: ringlet0: 0 mbpsringlet1: 0 mbps SAS enabled: YES Weight: ringlet0: 1ringlet1: 1 Secondary Mac Addresses: MAC 1: 0000.0000.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Provisioning Card Mode Caution Note High-level data link control (HDLC) framing is not supported. You can use TL-1 to provision the required SONET/SDH point-to-point circuits instead of CTC. Provisioning Card Mode The first task in creating an end-to-end RPR-IEEE is to set the CTC card mode to 802.17. For more information on this task, see the “Provisioning Card Mode” section on page 2-4.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Creating the RPR-IEEE Interface and Bridge Group Example of Connecting the ML-Series Cards with Point-to-Point STS/STM Circuits The three-node RPR-IEEE in Figure 26-6 shows an example of the point-to-point circuits needed.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Creating the RPR-IEEE Interface and Bridge Group Caution 6. Enable the rpr-ieee interface. 7. Set the encapsulation on the Ethernet interface. 8. Create rpr-ieee subinterfaces and assign them to the bridge group. A duplicate MAC address on the RPR-IEEE can cause network problems. Understanding the RPR-IEEE Interface When the card mode is changed to IEEE 802.17, the physical rpr-ieee interface is automatically created.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Creating the RPR-IEEE Interface and Bridge Group To enable the rpr-ieee interface and create the bridge group, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 Router(config)# bridge irb Enables the Cisco IOS software to both route and bridge a given protocol on separate interfaces within a single ML-Series card.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuration Examples for Cisco IOS CLI Portion of End-to-End RPR-IEEE Configuration Examples for Cisco IOS CLI Portion of End-to-End RPR-IEEE The following examples show RPR-IEEE configurations. Example 26-7 is a simple configuration. It does the minimum needed to bridge the ML-Series card’s Ethernet ports and the ML-Series card’s RPR-IEEE and leaves the RPR-IEEE characteristics at default.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Configuration Examples for Cisco IOS CLI Portion of End-to-End RPR-IEEE Example 26-8 Configuration Example for a Complex RPR-IEEE version 12.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring Verifying RPR-IEEE End-to-End Ethernet Connectivity bridge-group 12 bridge-group 12 spanning-disabled ! interface RPR-IEEE0.22 encapsulation dot1Q 22 no snmp trap bridge-group 22 bridge-group 22 spanning-disabled ! interface RPR-IEEE0.800 encapsulation dot1Q 800 ip address 8.1.1.1 255.255.255.
Chapter 26 Configuring IEEE 802.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RI Configuration Example Caution RPR-IEEE RI requires communication over the topology between the ML-Series cards. Traffic loss can occur if there is not enough communication and more than one span is down on a ring, for any reason. Caution If the primary ML-Series card goes to standby because the interconnect interface goes down, then the ring interface is placed admininistratively down (admin down).
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RI Configuration Example Router#show interface rpr-ieee 0 RPR-IEEE0 is up, line protocol is up Hardware is RPR-IEEE Channelized SONET, address is 0019.076c.7f72 (bia 0019.076c.7f72) The MAC address of the secondary peer is 0019.076c.7f72. The configuration would now appear as rpr-ieee ri mode 0019.076c.7f72.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RI Configuration Example Spans Provisioned : true Topology: stable Ring if: up Interconnect if: down Secondary IC mode: link-up, Ucode mode: Standby Interconnect interface 0: name: GigabitEthernet0 state: not up member port channel: false Interconnect interface 1: name: GigabitEthernet1 state: not up member port channel: false Monitored if: interconnect WTR-timer:60 Adjusted:65 Ethernet Card Software Feature and Configuration Guide, R7.
Chapter 26 Configuring IEEE 802.17b Resilient Packet Ring RI Configuration Example Ethernet Card Software Feature and Configuration Guide, R7.
A A P P E N D I X Command Reference Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration.
Appendix A Command Reference [no] bridge bridge-group-number protocol {drpri-rstp | ieee | rstp} [no] bridge bridge-group-number protocol {drpri-rstp | ieee | rstp} To define the protocol employed by a bridge group, use the bridge protocol global configuration command. If no protocol will be employed by the bridge group, this command is not needed. To remove a protocol from the bridge group, use the no form of this command with the appropriate keywords and arguments.
Appendix A Command Reference [no] clock auto [no] clock auto Use the clock auto command to determine whether the system clock parameters are configured automatically from the TCC2/TCC2P card. When enabled, both daylight savings time and time zone are automatically configured, and the system clock is periodically synchronized to the TCC2/TCC2P card. Use the no form of the command to disable this feature. Syntax Description This command has no arguments or keywords.
Appendix A Command Reference interface spr 1 interface spr 1 Use this command to create a shared packet ring (SPR) interface on an ML-Series card for a resilient packet ring (RPR) in Cisco proprietary RPR mode. If the interface has already been created, this command enters spr interface configuration mode. The only valid spr interface number is 1.
Appendix A Command Reference [no] ip radius nas-ip-address {hostname | ip-address} [no] ip radius nas-ip-address {hostname | ip-address} The ML-Series card allows the user to configure a separate nas-ip-address for each ML-Series card. This allows the Remote Authentication Dial In User Services (RADIUS) server to distinguish among individual ML-Series card in the same ONS node. If there is only one ML-Series card in the ONS node, this command does not provide any advantage.
Appendix A Command Reference microcode fail system-reload microcode fail system-reload In the event of a microcode failure, use this command to configure the ML-Series card to save information to the flash memory and then reboot. The information is saved for use by the Cisco Technical Assistance Center (Cisco TAC). To contact TAC, see the Obtaining Technical Assistance, page xxxiv. Defaults N/A Command Modes Global configuration Usage Guidelines This command and feature is specific to ML-Series card.
Appendix A Command Reference [no] pos pdi holdoff time [no] pos pdi holdoff time Use this command to specify the time, in milliseconds, to hold off sending the path defect indication (PDI) to the far end when a virtual concatenation (VCAT) member circuit is added to the virtual concatenation group (VCG). Use the no form of the command to use the default value. Syntax Description Parameter Description time Delay time in milliseconds, 100 to 1,000 Defaults The default value is 100 milliseconds.
Appendix A Command Reference [no] pos report alarm [no] pos report alarm Use this command to specify which alarms/signals are logged to the console. This command has no effect on whether alarms are reported to the TCC2/TCC2P and CTC. These conditions are soaked and cleared per Telcordia GR-253. Use the no form of the command to disable reporting of a specific alarm/signal. Syntax Description Parameter Description alarm The SONET/SDH alarm that is logged to the console.
Appendix A Command Reference [no] pos trigger defects condition [no] pos trigger defects condition Use this command to specify which conditions cause the associated POS link state to change. Use the no form of the command to disable triggering on a specific condition. Syntax Description Parameter Description condition The SONET/SDH condition that causes the link state change.
Appendix A Command Reference [no] pos scramble-spe [no] pos scramble-spe Use this command to enable scrambling. Syntax Description This command has no arguments or keywords. Defaults The default value depends on the encapsulation. Encapsulation Scrambling LEX pos scramble-spe PPP/HDLC no pos scramble-spe Command Modes Interface configuration mode (POS only) Usage Guidelines This value is normally configured to match the setting on the peer PTE.
Appendix A Command Reference rpr-ieee atd-timer value rpr-ieee atd-timer value Use this command to configure the attribute discovery (ATD) timer, which controls the frequency of ATD packet transmissions on the IEEE 802.17b based RPR interface. Syntax Description Parameter Description value Value expressed in seconds. Range is 1 through 10. Defaults Default is 1 second. Command Modes IEEE 802.17b based RPR interface configuration Usage Guidelines The ATD timer value is very rarely changed.
Appendix A Command Reference rpr-ieee fairness weight value rpr-ieee fairness weight value Use this command to configure the fairness weight of an IEEE 802.17b based RPR station. Syntax Description Parameter Description value Number, expressed as an exponent of two. Range is 0 through 7. Defaults The default is 0. Command Modes IEEE 802.
Appendix A Command Reference [no] rpr-ieee ri foreign [no] rpr-ieee ri foreign Use this command to control the secondary card laser states and the interface wait to restore (WTR) timer when changing from secondary mode to primary. Foreign mode indicates that the secondary card’s transmit laser(s) are turned off while in standby mode. In turn, the secondary card’s partner card does not send traffic through the ring redundant interconnect (RI) interface.
Appendix A Command Reference rpr-ieee keepalive-timer interval [east | west] rpr-ieee keepalive-timer interval [east | west] Use this command to configure the keepalive timer configuration on a specific IEEE 802.17b based RPR span (east or west). Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic. interval Timer interval expressed in milliseconds.
Appendix A Command Reference [no] rpr-ieee protection pref jumbo [no] rpr-ieee protection pref jumbo Use this command to set the IEEE 802.17b based RPR station MTU preference to jumbo Ethernet frames. If all stations on the ring select jumbo preference, the ring MTU is 9,000 bytes; otherwise, it is 1,500 bytes. Use the no form of this command to select normal MTU preference. Syntax Description This command has no arguments or keywords.
Appendix A Command Reference [no] rpr-ieee protection request forced-switch {east | west} [no] rpr-ieee protection request forced-switch {east | west} Use this command to trigger a forced-switch protection event on the specified IEEE 802.17b-based RPR span. Use the no form of this command to clear the switch. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic.
Appendix A Command Reference [no] rpr-ieee protection request manual-switch {east | west} [no] rpr-ieee protection request manual-switch {east | west} Use this command to trigger a manual-switch protection event on the specified IEEE 802.17b based RPR span. Use the no form of this command to deactivate the switch. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic.
Appendix A Command Reference rpr-ieee protection sonet holdoff-timer interval {east | west} rpr-ieee protection sonet holdoff-timer interval {east | west} Use this command to configure the SONET hold-off timer for a protection event on the specified IEEE 802.17b based RPR span. Use the no form of this command to turn off the SONET holdoff timer. Note Syntax Description This command replaces the pos vcat defect {delayed | immediate} command.
Appendix A Command Reference rpr-ieee protection timer fast rate {east | west} rpr-ieee protection timer fast rate {east | west} Use this command to configure the fast protection timer value for the specified IEEE 802.17b based RPR span. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic. rate The rate, expressed in milliseconds, at which the fast protection timer sends a protection message.
Appendix A Command Reference rpr-ieee protection timer slow rate {east | west} rpr-ieee protection timer slow rate {east | west} Use this command to configure the slow protection timer value on the specified IEEE 802.17b based RPR span. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic. rate The rate, expressed in milliseconds, at which the slow protection timer sends a protection message.
Appendix A Command Reference rpr-ieee protection wtr-timer {interval | never} rpr-ieee protection wtr-timer {interval | never} Use this command to configure the amount of time that an IEEE 802.17b based RPR span stays in wait-to-restore (WTR) state before normal service is restored on a span. The never argument configures an RPR-IEEE span WTR timer to disallow the WTR function.
Appendix A Command Reference rpr-ieee flag c2 value rpr-ieee flag c2 value Use this command to specify the SONET C2 byte path overhead values for both IEEE 802.17b based RPR spans. Syntax Description Parameter Description value The bytes that the path signal uses to flag the IEEE 802.17b based RPR interface for faults. The numeric value range is 0 to 255, and the default is 0 (0x1b) for generic framing procedure (GFP) encapsulation. Defaults The default is 0x1B, which indicates GFP encapsulation.
Appendix A Command Reference rpr-ieee pdi holdoff time interval rpr-ieee pdi holdoff time interval Use this command to configure the interval that occurs before a path defect indication (PDI) is raised on an IEEE 802.17b based RPR span. Syntax Description Parameter Description interval The period, expressed in milliseconds. The range is 100 to 1,000 milliseconds. Defaults The default is 100 milliseconds. Command Modes IEEE 802.
Appendix A Command Reference [no] rpr-ieee report alarm [no] rpr-ieee report alarm Use this command to specify which IEEE 802.17b based RPR alarms or signals are logged to the console. Use the no form of the command to disable a particular type of notification. Syntax Description Parameter Description alarm The SONET/SDH object that is logged to the console.
Appendix A Command Reference [no] rpr-ieee ri {primary | secondary} peer peer-MAC-address [no] rpr-ieee ri {primary | secondary} peer peer-MAC-address Use this command to set the mode for the IEEE 802.17b based RPR interface and the peer address, or disables the feature. Use the no form to disable the feature. Syntax Description Parameter Description primary Single traffic queue mode. secondary Dual traffic queue mode. peer-MAC-address The MAC of the alternate station.
Appendix A Command Reference [no] rpr-ieee ri {primary | secondary} delay interval [no] rpr-ieee ri {primary | secondary} delay interval Use this command to change the soak time for a primary card in active mode. Use the no form of this command to set the timer to default. Syntax Description Parameter Description primary Single traffic queue mode. secondary Dual traffic queue mode. interval Interval that the active mode timer waits before switching to the secondary card.
Appendix A Command Reference [no] rpr-ieee shutdown {east | west} [no] rpr-ieee shutdown {east | west} This command is similar to a rpr-ieee protection request forced-switch {east | west} command on the span. This command is essentially no different in function; it is an easier way to do the same thing. Syntax Description Parameter Description east Specifies a shutdown on the east span of the interface. west Specifies a shutdown on the west span of the interface. Defaults Default is no shutdown.
Appendix A Command Reference rpr-ieee tx-traffic rate-limit high rate [east | west] rpr-ieee tx-traffic rate-limit high rate [east | west] Use this command to limit the rate at which Class A1 traffic is transmitted only on a specific (east or west) span. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic.
Appendix A Command Reference rpr-ieee tx-traffic rate-limit medium rate [east | west] rpr-ieee tx-traffic rate-limit medium rate [east | west] Use this command to limit the rate that Class B-CIR traffic is transmitted on a specific (east or west) span. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic.
Appendix A Command Reference rpr-ieee tx-traffic rate-limit reserved rate [east | west] rpr-ieee tx-traffic rate-limit reserved rate [east | west] Use this command to limit the transmission rate of Class A0 reserved traffic on a specific (east or west) span. Syntax Description Parameter Description east Pertains to configuration for eastbound span traffic. west Pertains to configuration for westbound span traffic.
Appendix A Command Reference [no] rpr-ieee tx-traffic strict [no] rpr-ieee tx-traffic strict Use this command to configure either all or none of the traffic added by the node to have the strict order (SO) bit set on or off in the IEEE 802.17b-based RPR header. Syntax Description This command has no arguments or keywords. Defaults The default is off. Command Modes IEEE 802.17b based RPR interface configuration Usage Guidelines By default, the SO bit is turned off. You can turn it on in the IEEE 802.
Appendix A Command Reference show controller pos interface-number [detail] show controller pos interface-number [detail] Use this command to display the status of the POS controller. Use the detail argument to obtain additional SONET and POS information for the interface.
Appendix A Command Reference show controller pos interface-number [detail] Remote hostname : Remote interface: Remote IP addr : B3 BER thresholds: SFBER = 1e-4, SDBER = 1e-7 5 total input packets, 73842 post-HDLC bytes 0 input short packets, 73842 pre-HDLC bytes 0 input long packets , 0 input runt packets 67 input CRCerror packets , 0 input drop packets 0 input abort packets 0 input packets dropped by ucode 0 total output packets, 0 0 output post-HDLC bytes output pre-HDLC bytes Carrier delay is 200 msec
Appendix A Command Reference show controller pos interface-number [detail] Remote interface: Remote IP addr : B3 BER thresholds: SFBER = 1e-4, SDBER = 1e-7 *************** Member 2 *************** ESM State: IS VCG Member State: VCG_MEMBER_NORMAL PAIS = 0 PLOP = 0 PPLM = 0 PUNEQ = 0 BER_SF_B3 = 0 BER_SD_B3 = 0 NEWPTR = 0 PSE = 0 PRDI PPDI BIP(B3) NSE = = = = 0 0 15 0 PTIM = 0 PTIU = 0 REI = 35 Active Alarms : None Demoted Alarms: None Active Defects: None Alarms reportable to CLI: PAIS PLOP PUNEQ PTIM
Appendix A Command Reference show controller rpr-ieee interface-number [detail] show controller rpr-ieee interface-number [detail] Use this command to display the status of the IEEE 802.17b based RPR controller. Use the detail argument to obtain additional SONET and RPR-IEEE information for the interface. Syntax Description Parameter Description interface-number Number of the IEEE 802.17b based RPR interface (0–1) detail Greater detail per interface.
Appendix A Command Reference show controller rpr-ieee interface-number [detail] NEWPTR = 3 PSE = 0 NSE = 0 ENCAP = 0 OOU-TPT = 1 LOM = 1 SQM = 1 OOG = 0 Active Alarms : None Demoted Alarms: None Active Defects: None DOS FPGA channel number : 0 Starting STS (0 based) : 0 VT ID (if any) (0 based) : 255 Circuit size : STS1 RDI Mode : 1 bit C2 (tx / rx) : 0x1B / 0x1B Framing : SONET Path Trace Mode : off Transmit String : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Appendix A Command Reference show controller rpr-ieee interface-number [detail] BIP Sum:0, setTh:0, clrTh:0, BurstMap:0x0000, BurstTh:0 Counts: Over threshold:TRUE, Bursty:FALSE, Clear higher:FALSE, Set level:TRUE *************** Member 1 *************** ESM State: IS VCG Member State: VCG_MEMBER_NORMAL PAIS = 0 PLOP = 0 PRDI = 0 PTIM = PPLM = 0 PUNEQ = 1 PPDI = 0 PTIU = BER_SF_B3 = 0 BER_SD_B3 = 0 BIP(B3) = 22 REI = NEWPTR = 3 PSE = 0 NSE = 0 ENCAP = OOU-TPT = 1 LOM = 1 SQM = 1 OOG = Active Alarms : None
Appendix A Command Reference show controller rpr-ieee interface-number [detail] Over threshold:FALSE, Bursty:TRUE, Clear higher:TRUE, Set level:FALSE BER 1e-8: BIP Sum:0, setTh:399, clrTh:89, BurstMap:0x03FF, BurstTh:25 Counts:0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Over threshold:FALSE, Bursty:TRUE, Clear higher:TRUE, Set level:FALSE BER 1e-9: BIP Sum:0, setTh:399, clrTh:89, BurstMap:0x03FF, BurstTh:25 Counts:0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Over threshold:FALSE, Bursty:TRUE, Clear higher:TRUE, Set level:FALSE BER 1e-
Appendix A Command Reference show controller rpr-ieee interface-number [detail] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Received String : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Appendix A Command Reference show controller rpr-ieee interface-number [detail] C2 (tx / rx) : 0x1B / 0x1B Framing : SONET Path Trace Mode : off Transmit String : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Expected String : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Appendix A Command Reference show controller rpr-ieee interface-number [detail] Related Commands show interface rpr-ieee Ethernet Card Software Feature and Configuration Guide, R7.
Appendix A Command Reference show interface pos interface-number show interface pos interface-number Use this command to display the status of the POS. Syntax Description Parameter Description interface-number Number of the POS interface (0–1) Defaults N/A Command Modes Privileged executive Usage Guidelines This command can be used to help diagnose and isolate POS or SONET/SDH problems. In this command, interface can be shortened to int.
Appendix A Command Reference show interface pos interface-number Related Commands show controller pos clear counters Ethernet Card Software Feature and Configuration Guide, R7.
Appendix A Command Reference show interface rpr-ieee interface-number show interface rpr-ieee interface-number Use this command to display the status of chosen IEEE 802.17b based RPR interface. Syntax Description Parameter Description interface-number Number of the IEEE 802.17b based RPR interface (0–1) Defaults N/A Command Modes Privileged executive Usage Guidelines This command can be used to help diagnose and isolate IEEE 802.17b based RPR interface or SONET/SDH problems.
Appendix A Command Reference show interface rpr-ieee interface-number 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Related Commands show int pos show int spr Ethernet Card Software Feature and Configuration Guide, R7.
Appendix A Command Reference show ons alarm show ons alarm Use this command to display all the active alarms on the ML-Series card running the Cisco IOS CLI session. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines This command can be used to help diagnose and isolate card problems.
Appendix A Command Reference show ons alarm Related Commands show controller pos show ons alarm defect show ons alarm failure Ethernet Card Software Feature and Configuration Guide, R7.
Appendix A Command Reference show ons alarm defect eqpt show ons alarm defect eqpt Use this command to display the equipment-layer defects. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active defects for the equipment layer and the possible set of defects that can be set.
Appendix A Command Reference show ons alarm defect port show ons alarm defect port Use this command to display the port-layer defects. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active defects for the link layer and the possible set of defects that can be set. Note that the TPTFAIL defect can only occur on the POS ports and the CARLOSS defect can only occur on the Ethernet ports.
Appendix A Command Reference show ons alarm defect pos interface-number show ons alarm defect pos interface-number Use this command to display the link-layer defects. Syntax Description Parameter Description interface-number Number of the interface (0–1) Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active defects for the POS layer and the possible set of defects that can be set.
Appendix A Command Reference show ons alarm defect rpr [interface-number] show ons alarm defect rpr [interface-number] Use this command to display the interface defects on the layer. Syntax Description Parameter Description interface-number Number of the interface (0–1) Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active defects for the IEEE 802.17b based RPR and the possible set of defects that can be set.
Appendix A Command Reference show ons alarm failure eqpt show ons alarm failure eqpt Use this command to display the equipment-layer failures. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the active failures for the equipment layer. If an EQPT alarm is present, the board fail defect that was the source of the alarm is displayed.
Appendix A Command Reference show ons alarm failure port show ons alarm failure port Use this command to display the port-layer failures. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active failures for the link layer.
Appendix A Command Reference show ons alarm failure pos interface-number show ons alarm failure pos interface-number Use this command to display the link-layer failures. Syntax Description Parameter Description interface-number Number of the interface (0–1) Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active failures for a specific interface at the POS layer.
Appendix A Command Reference show ons alarm failure rpr [interface-number] show ons alarm failure rpr [interface-number] Use this command to display failures on a specific IEEE 802.17b based RPR interface. Syntax Description Parameter Description interface-number Number of the interface (0–1) Defaults N/A Command Modes Privileged executive Usage Guidelines This command displays the set of active failures for a specific IEEE 802.17b based RPR interface.
Appendix A Command Reference show rpr-ieee counters show rpr-ieee counters Use this command to display the various packet/byte counters for each span of the IEEE 802.17b based RPR interface. For definitions of ML-Series card statistics, refer to the “Performance Monitoring” chapter in the Cisco ONS 15454 SONET and DWDM Troubleshooting Guide or the Cisco ONS 15454 SDH Troubleshooting Guide. Syntax Description This command has no arguments or keywords. Defaults Defaults can vary by each counter.
Appendix A Command Reference show rpr-ieee counters Unicast Low Priority Unicast Med EIR Priority Unicast Med CIR Priority Unicast High Priority Multicast Low Priority Multicast Med EIR Priority Multicast Med CIR Priority Multicast High Priority Broadcast 18701060600 0 0 0 233345 456173838 48446005 192647108 0 2954767575274 0 0 0 38183383 72075466404 7654468790 30438243064 N/A Total Transmit Unicast Low Priority Unicast Med EIR Priority Unicast Med CIR Priority Unicast High Priority Multicast Low Priori
Appendix A Command Reference show rpr-ieee counters Unicast High Priority Multicast Low Priority Multicast Med EIR Priority Multicast Med CIR Priority Multicast High Priority Broadcast 3693986118 42456 39498185 8936134 17565790 0 583445203252 9288351 6240713230 1411909172 2775394820 N/A Total Receive Unicast Low Priority Unicast Med EIR Priority Unicast Med CIR Priority Unicast High Priority Multicast Low Priority Multicast Med EIR Priority Multicast Med CIR Priority Multicast High Priority Packets 776
Appendix A Command Reference show rpr-ieee counters 0 framer runts, 0 framer giants, 0 framer aborts, 0 mac runts, 0 mac giants, 3 mac ttl strips, 0 non_we drop, 0 ltb_strict drop, 0 htb_strict drop 0 scff errors, 0 bad addr frames, 0 self sourced frames Related Commands show int rpr-ieee interface-number Ethernet Card Software Feature and Configuration Guide, R7.
Appendix A Command Reference show rpr-ieee failure rpr-ieee interface-number show rpr-ieee failure rpr-ieee interface-number Use this command to display all inputs used to determine the failure state of each span on the IEEE 802.17b-based RPR interface. Syntax Description Parameter Description interface-number IEEE 802.17b based RPR interface number. No space is included between rpr-iee and the interface number (for example, rpr-ieee0).
Appendix A Command Reference show rpr-ieee fairness detail show rpr-ieee fairness detail Use this command to display the state information of the fairness state machine for each span of the IEEE 802.17b based RPR interface. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines This command can be used for troubleshooting traffic issues related to fairness weighting or bandwidth usage.
Appendix A Command Reference show rpr-ieee fairness detail TTL to Congestion: 255 Total Hops Tx: 4 Advertised Fair Rate: Approximate Bandwidth: FULL RATE 65535 normalized bytes per aging interval 8191 bytes per aging interval Eastbound Tx (Ringlet 0) Weighted Fairness: Local Weight: 0 (1) Single-Choke Fairness Status: Local Congestion: Congested? No Head? No Local Fair Rate: Approximate Bandwidth: 0 Kbps 0 normalized bytes per aging interval 0 bytes per ageCoef aging interval Downstream Congestion: Congest
Appendix A Command Reference show rpr-ieee fairness history show rpr-ieee fairness history Use this command to retrievs performance monitoring information about local and downstream IEEE 802.17b based RPR congestion history over a period of up to 24 hours. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines Use this command to determine whether the local IEEE 802.
Appendix A Command Reference show rpr-ieee fairness history 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 01:01:45:0 00:46:45:0 00:31:45:0 00:16:45:0 00:01:45:0 23:46:45:0 23:31:45:0 23:16:45:0 23:01:45:0 22:46:45:0 22:31:45:0 22:16:45:0 22:01:45:0 21:46:45:0 21:31:45:0 21:16:45:0 21:01:45:0 20:46:45:0 20:31:45:0 20:16:45:0 20:01:45:0 19:46:45:0 19:31:45:0 19:16:45:0 19:
Appendix A Command Reference show rpr-ieee fairness history 69 09:01:45:0 / 2250000 68 08:46:45:0 / 2250000 67 08:31:45:0 / 2250000 Downstream Congestion: No.
Appendix A Command Reference show rpr-ieee fairness history 8 17:46:45 : 0 / 2250000 7 17:31:45 : 0 / 2250000 6 17:16:45 : 0 / 2250000 5 17:01:45 : 0 / 2250000 4 16:46:45 : 0 / 2250000 3 16:31:45 : 0 / 2250000 2 16:16:45 : 0 / 2250000 1 16:01:45 : 0 / 2250000 96 15:46:45 : 0 / 2250000 95 15:31:45 : 0 / 2250000 94 15:16:45 : 0 / 2250000 93 15:01:45 : 0 / 2250000 92 14:46:45 : 0 / 2250000 91 14:31:45 : 0 / 2250000 90 14:16:45 : 0 / 2250000 89 14:01:45 : 0 / 2250000 88 13:46:45 : 0 / 2250000 87 13:31:45 : 0 /
Appendix A Command Reference show rpr-ieee fairness history 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 02:46:45 : 02:31:45 : 02:16:45 : 02:01:45 : 01:46:45 : 01:31:45 : 01:16:45 : 01:01:45 : 00:46:45 : 00:31:45 : 00:16:45 : 00:01:45 : 23:46:45 : 23:31:45 : 23:16:45 : 23:01:45 : 22:46:45 : 22:31:45 : 22:16:45 : 22:01:45 : 21:46:45 : 21:31:45 : 21:16:45 : 21:01:45 : 20:
Appendix A Command Reference show rpr-ieee fairness history 76 75 74 73 72 71 70 69 68 67 10:46:45 10:31:45 10:16:45 10:01:45 09:46:45 09:31:45 09:16:45 09:01:45 08:46:45 08:31:45 : : : : : : : : : : 0 0 0 0 0 0 0 0 0 0 / / / / / / / / / / 2250000 2250000 2250000 2250000 2250070 2250000 2250000 2250000 2250000 2250000 Downstream Congestion: No.
Appendix A Command Reference show rpr-ieee fairness history 16 19:46:45 : 15 19:31:45 : 14 19:16:45 : 13 19:01:45 : 12 18:46:45 : 11 18:31:45 : 10 18:16:45 : 9 18:01:45 : 8 17:46:45 : 7 17:31:45 : 6 17:16:45 : 5 17:01:45 : 4 16:46:45 : 3 16:31:45 : 2 16:16:45 : 1 16:01:45 : 96 15:46:45 : 95 15:31:45 : 94 15:16:45 : 93 15:01:45 : 92 14:46:45 : 91 14:31:45 : 90 14:16:45 : 89 14:01:45 : 88 13:46:45 : 87 13:31:45 : 86 13:16:45 : 85 13:01:45 : 84 12:46:45 : 83 12:31:45 : 82 12:16:45 : 81 12:01:45 : 80 11:46:45
Appendix A Command Reference show rpr-ieee protection show rpr-ieee protection Use this command to display the protection state of the local station, along with brief overview of the station’s neighbors, timer configuration, and self-detected failures that might contribute to the current state. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines Use this command to show the current protection status on the ring.
Appendix A Command Reference show rpr-ieee rate detail show rpr-ieee rate detail Use this command to display the configured rate limits for each service class of traffic. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged executive Usage Guidelines Use this command to show the configured rates for Class A1, B-EIR, B-CIR, and reserved traffic.
Appendix A Command Reference show rpr-ieee topology detail show rpr-ieee topology detail Use this command to display topology information gathered by the station from the protection and ATD messages received on either span of an IEEE 802.17b based RPR ring. Syntax Description This command has no arguments or keywords.
Appendix A Command Reference show rpr-ieee topology detail Weight: ringlet0: 1ringlet1: 1 Secondary Mac Addresses: MAC 1: 0000.0000.0000 (UNUSED) MAC 2: 0000.0000.0000 (UNUSED) ======================================================================= Topology Map for Outer ringlet ======================================================================= ======================================================================= Topology entry at Index 1 on ringlet 0: Station MAC address: 000b.fcff.
Appendix A Command Reference show rpr-ieee topology detail ringlet0: IDLEringlet1: IDLE Active Edges: ringlet0: NO ringlet1: NO Preferred protection mode: STEERING Jumbo preference: NOT SET (ring doesn't supports JUMBOS) Measured LRTT: 0 Sequence Number: 3 ATD INFO: Station Name: ML1000-492 A0 reserved Bandwidth: ringlet0: 0 mbpsringlet1: 0 mbps SAS enabled: YES Weight: ringlet0: 1ringlet1: 1 Secondary Mac Addresses: MAC 1: 0000.0000.0000 (UNUSED) MAC 2: 0000.0000.
Appendix A Command Reference show rpr-ieee topology detail MAC 2: 0000.0000.0000 (UNUSED) ======================================================================= Topology Map for Inner ringlet ======================================================================= ======================================================================= Topology entry at Index 1 on ringlet 1: Station MAC address: 0013.1991.
Appendix A Command Reference show rpr-ieee topology detail Measured LRTT: 0 Sequence Number: 3 ATD INFO: Station Name: ML1000-491 A0 reserved Bandwidth: ringlet0: 0 mbpsringlet1: 0 mbps SAS enabled: YES Weight: ringlet0: 1ringlet1: 1 Secondary Mac Addresses: MAC 1: 0000.0000.0000 (UNUSED) MAC 2: 0000.0000.0000 (UNUSED) ======================================================================= Topology entry at Index 4 on ringlet 1: Station MAC address: 000b.fcff.
Appendix A Command Reference show rpr-ieee topology detail Related Commands None Ethernet Card Software Feature and Configuration Guide, R7.
Appendix A Command Reference [no] shutdown [no] shutdown Use this command to place a POS or IEEE 802.17b based RPR interface in pass-through mode. This command has no arguments or keywords. Use the no form of this command to reverse the shutdown. Defaults The default is not shut down. Command Modes POS or IEEE 802.
Appendix A Command Reference spr-intf-id shared-packet-ring-number spr-intf-id shared-packet-ring-number Use this command to assign the POS interface to the SPR interface. Syntax Description Parameter Description shared-packet-ring-number The only valid shared-packet-ring-number (SPR number) is 1. Defaults N/A Command Modes POS interface configuration Usage Guidelines • The SPR number must be 1, which is the same SPR number assigned to the SPR interface.
Appendix A Command Reference [no] spr load-balance {auto | port-based} [no] spr load-balance {auto | port-based} Use this command to specify the Cisco proprietary RPR load-balancing scheme for unicast packets. Syntax Description Parameter Description auto The default auto option balances the load based on the MAC addresses or source and destination addresses of the IP packet. port-based The port-based load balancing option maps even ports to the POS 0 interface and odd ports to the POS 1 interface.
Appendix A Command Reference spr station-id station-id-number spr station-id station-id-number Use this command to configure a station ID. Syntax Description Parameter Description station-id-number The user must configure a different number for each SPR interface that attaches to the Cisco proprietary RPR. Valid station ID numbers range from 1 to 254.
Appendix A Command Reference spr wrap {immediate | delayed} spr wrap {immediate | delayed} Use this command to set the Cisco proprietary RPR wrap mode to either wrap traffic the instant it detects a link state change or to wrap traffic after the carrier delay, which gives the SONET protection time to register the defect and declare the link down. Syntax Description Parameter Description immediate Wraps Cisco proprietary RPR traffic the instant it detects a link state change.
Appendix A Command Reference [no] xconnect [destination] [vc-id] [encapsulation mpls] [no] xconnect [destination] [vc-id] [encapsulation mpls] Use this command at customer-edge (CE) or service provider-edge customer-located equipment (PE-CLE) ingress and egress Ethernet ports, or at dot1Q VLAN subinterfaces with a destination and virtual connection identifier (VC ID) to route Layer 2 packets over a specified point-to-point VC by using Ethernet over multiprotocol label switching (EoMPLS).
Appendix A Command Reference [no] xconnect [destination] [vc-id] [encapsulation mpls] At the PE1 interface: Switch(config)# interface vlan 3 Switch(config-if)# xconnect 20.0.0.1 123 encapsulation mpls At the PE2 interface: Switch(config)# interface vlan 4 Switch(config-if)# xconnect 10.0.0.1 123 encapsulation mpls Related Commands show mpls l2transport route Ethernet Card Software Feature and Configuration Guide, R7.
B A P P E N D I X Unsupported CLI Commands This appendix lists some of the command-line interface (CLI) commands that are not supported in this release, either because they are not tested, or because of hardware limitations. These unsupported commands are displayed when you enter the question mark (?) at the CLI prompt. This is not a complete list. Unsupported commands are listed by command mode.
Appendix B Unsupported CLI Commands Unsupported Global Configuration Commands bridge domain bridge lat-service-filtering bridge protocol dec bridge protocol ibm bridge protocol vlan-bridge chat-script class-map match access-group class-map match class-map class-map match destination-address class-map match mpls class-map match protocol class-map match qos-group class-map match source-address clns define dialer dialer-list downward-compatible-config file ip access-list log-upda
Appendix B Unsupported CLI Commands Unsupported POS Interface Configuration Commands queue-list router iso-igrp router mobile service compress-config service disable-ip-fast-frag service exec-callback service nagle service old-slip-prompts service pad service slave-log set privilege level subscriber-policy Unsupported POS Interface Configuration Commands access-expression autodetect bridge-group x circuit-group bridge-group x input-* bridge-group x lat-compression bridge-group x output-* bridge-group x su
Appendix B Unsupported CLI Commands Unsupported POS Interface Configuration Commands (Cisco Proprietary RPR Virtual Interface) iso-igrp loopback multilink-group netbios pos flag c2 pos mode gfp pos scramble-spe pos trigger delay pos vcat defect pos vcat resequence priority-group pulse-time random-detect rate-limit serial service-policy history source timeout transmit-interface tx-ring-limit Unsupported POS Interface Configuration Commands (Cisco Proprietary RPR Virtual Interface) shu
Appendix B Unsupported CLI Commands Unsupported FastEthernet or GigabitEthernet Interface Configuration Commands rpr-ieee count rpr-ieee fairness active-weights-detect rpr-ieee fairness mode aggressive rpr-ieee fairness mode conservative rpr-ieee fairness multi-choke rpr-ieee framing rpr-ieee loopback rpr-ieee protection pref wrap rpr-ieee protection sonet threshold sd-ber rpr-ieee protection sonet threshold sf-ber rpr-ieee trigger defects rpr-ieee tx-traffic idle l
Appendix B Unsupported CLI Commands Unsupported Port-Channel Interface Configuration Commands rate-limit service-policy history timeout transmit-interface tx-ring-limit Unsupported Port-Channel Interface Configuration Commands access-expression carrier-delay cdp clns custom-queue-list duplex down-when-looped encapsulation fair-queue flowcontrol full-duplex half-duplex hold-queue iso-igrp keepalive max-reserved-bandwidth multilink-group negotiation netbios ppp priority-group rate-limit random-detect timeou
Appendix B Unsupported CLI Commands Unsupported BVI Interface Configuration Commands Unsupported BVI Interface Configuration Commands access-expression carrier-delay cdp clns flowcontrol hold-queue iso-igrp keepalive l2protocol-tunnel load-interval max-reserved-bandwidth mode multilink-group netbios ntp mtu rate-limit timeout transmit-interface tx-ring-limit Ethernet Card Software Feature and Configuration Guide, R7.
Appendix B Unsupported CLI Commands Unsupported BVI Interface Configuration Commands Ethernet Card Software Feature and Configuration Guide, R7.
C A P P E N D I X Using Technical Support This appendix describes how to resolve problems with your ML-Series card.
Appendix C Using Technical Support Getting the Data from Your ML-Series Card • Node equipment and configuration; including type of cross-connect cards, ML-Series cards’ slot numbers, OC-N cards, and TCC2/TCC2P cards. To assist you in gathering this required data, the show tech-support EXEC command has been added in Cisco IOS Release 11.1(4) and later.
Appendix C Using Technical Support Providing Data to Your Technical Support Representative • Note UNIX workstation—At the UNIX prompt, enter the command script filename, then use Telnet to connect to the ML-Series card. The UNIX script command captures all screen output to the specified filename. To stop capturing output and close the file, enter the end-of-file character (typically Ctrl-D) for your UNIX system.
Appendix C Using Technical Support Providing Data to Your Technical Support Representative Ethernet Card Software Feature and Configuration Guide, R7.
I N D EX routing protocol defaults Numerics advertisements RIP 802.17 RPR card mode 2-4 11-32 11-5 aging time, accelerated for STP 802.1D. See STP alarms 802.1Q. See IEEE 802.1Q alarms, RMON 7-9, 7-20 5-6 21-3 area border routers. See ABRs ASBRs A 11-9 attributes, RADIUS abbreviating commands ABRs vendor-proprietary 3-15 vendor-specific 11-9 access control lists.
Index feature list oversubscription 1-2 monitoring and verifying overview 6-3 transparent 25-1 POS ports bridge CRB mode bvi command SW-LCAS 6-5 no IP routing mode overview statistics and counters 6-8 IP routing mode 25-6 RMON and SNMP support 6-7 bridge IRB mode 25-3 25-6 25-6 VCAT characteristics 6-6 25-6 CE-100T-8 6-5 capacity restrictions 12-3 BVIs Ethernet features configuring 12-3 flow control description 12-1 frame buffering displaying information about routing
Index clear bridge command clear vlan command no rpr-ieee protection pref jumbo 6-4 no rpr-ieee protection request forced-switch east A-16 8-5 clear vlan statistics command clocking tolerances 6-4 no rpr-ieee protection request forced-switch west A-16 20-11 commands access-list bridge irb no rpr-ieee protection request manual-switch east A-17 22-8 bridge-group 4-4, 4-5, 4-6, 4-11, 6-2, 18-8 no rpr-ieee protection request manual-switch west A-17 12-3 bridge priority no rpr-ieee report 6-2
Index rpr-ieee protection request forced-switch east A-16 show ons alarm defect port A-49 rpr-ieee protection request forced-switch west A-16 show ons alarm defect pos A-50 rpr-ieee protection request manual-switch east A-17 show ons alarm defect rpr A-51 rpr-ieee protection request manual-switch west rpr-ieee protection sonet holdoff-timer east A-18 rpr-ieee protection sonet holdoff-timer west rpr-ieee protection timer fast east A-17 A-18 A-19 show ons alarm failure eqpt A-52 show ons
Index snmp-server user spr-intf-id cos commit command 22-10 CRC A-79 spr load-balance auto spr station-id checking manually monitoring A-82 community strings overview POS statistics 22-6 configuration mode 22-12 D database restore 3-14 3-14 EIGRP 11-21 Layer 2 protocol tunneling EtherChannel encapsulation 10-7 3-9 OSPF RADIUS RIP interface, overview RMON 4-1 11-1 ISL over FEC 11-33 STP 10-7 management port 19-9 11-5 SNMP IP multicast 21-2 22-6 7-16 Default Multicast Qo
Index priority queuing E 23-20 proprietary encapsulation Egress priority marking 14-8 Q-tagging EIGRP 20-7 23-18 RMON alarm thresholds authentication 11-25 shared packed ring 23-25 components 11-20 single-card EtherSwitch configuring 11-22 spanning tree (STP) default configuration definition 11-21 11-20 interface parameters, configuring monitoring C-3 autonegotiation 3-8 clocking 5-4 10-7 8-2 Enhanced IGRP.
Index framing mode 5-4 I IEEE G 9-4 IEEE 802.1D. See STP IEEE 802.
Index IRB M BVIs 12-1 configuration considerations 12-1 MAC addresses 4-2 configuring 12-2 management options, SNMP description 12-1 management ports displaying information about monitoring and verifying IS, AINS 12-5 See also console ports configuring 12-4 25-5 3-8 match any command 14-12 match cos command 14-13 match ip dscp command J 22-1 14-13 match ip precedence command J1 bytes Media Access Control addresses.
Index Multicast QoS PC, connecting to switch 14-24 3-5 per-VLAN Spanning Tree+ 7-8 PIM N configuring neighbor discovery/recovery, EIGRP network element default 11-33 to 11-34 11-34 pin mappings for RJ-11 to RJ-45 port-channel command network management port channels 21-1 SNMP 11-33 to 11-34 rendezvous point 24-2, 25-3 networking protocols, IP multicast routing RMON modes 11-20 11-34 port IDs 22-1 10-1 10-1 4-2 not-so-stubby areas.
Index split horizon R 11-8 summary addresses RADIUS RJ-11 to RJ-45 console cable adapter attributes RJ-45 connector, console port vendor-proprietary vendor-specific 19-19 19-18 19-16 authentication authorization displaying status 19-15 communication, per-server multiple UDP ports default configuration 21-2 21-20 Monitoring CRC errors 19-17 overview 19-9 21-15 21-1 statistics 19-9 collecting group Ethernet 19-9 collecting group history 19-13 rmon alarm command displaying the conf
Index example configuring 17-29 monitoring and verifying understanding size 17-28 MAC address and VLAN support monitoring and verifying QoS 15-1 and customer VLANs 9-2 and IEEE 802.
Index configuring overview snmp-server trap-timeout command 22-7 snmp-server user command 22-4 configuration examples 22-13 configuration guidelines 22-6 default configuration groups hosts SNMPv2C soft-reset source 22-6 informs and trap keyword described 22-10 overview 11-34 SSH, configuring 19-3 22-13 3-9 11-31 RMON group Ethernet 21-6 RMON group history 21-5 SNMP input and output 22-1, 22-4 statistics, OSPF 22-14 trap manager, configuring 3-11 statistics 22-3 system cont
Index forwarding terminals 7-6, 7-7 learning 7-7 connecting to switch 3-5 listening 7-7 logging router output C-2 overview 7-5 terminal-emulation software Layer 2 protocol tunneling ternary content addressable memory. See TCAM 9-9 limitations with IEEE 802.
Index V VC4/VC LO allocation 24-11 VCAT characteristics fixed VCGs 25-6 25-6, 25-7 flexible VCGs 25-6 VCAT group (VCG) 25-6 VCs, assigning interfaces A-83 verifying IP multicast operation VLAN operation 11-35 8-5 virtual concatenation.SeeVCAT virtual LANs. See VLANs VLANs aging dynamic addresses 7-9 configuring IEEE 802.1Q 8-2 customer numbering in service-provider networks 9-3 number per system 8-1 STP and IEEE 802.