Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide Cisco IOS Release 12.2(28)SV CTC and Documentation Release 8.5 June 2009 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S Preface i Revision History i Document Objectives Audience ii ii Related Documentation ii Document Conventions iii Obtaining Optical Networking Information ix Where to Find Safety and Warning Information ix Cisco Optical Networking Product Documentation CD-ROM ix Obtaining Documentation, Obtaining Support, and Security Guidelines CHAPTER 1 Overview of the ML-Series Card ML-Series Card Description ML-Series Feature List 1-1 1-1 1-2 Key ML-Series Features 1-4 Cisco IOS 1-4
Contents CHAPTER 3 Initial Configuration of the ML-Series Card Hardware Installation 3-1 3-1 Cisco IOS on the ML-Series Card 3-1 Opening a Cisco IOS Session Using CTC 3-2 Telnetting to the Node IP Address and Slot Number 3-2 Telnetting to a Management Port 3-3 ML-Series IOS CLI Console Port 3-4 RJ-11 to RJ-45 Console Cable Adapter 3-4 Connecting a PC or Terminal to the Console Port 3-4 Startup Configuration File 3-5 Manually Creating a Startup Configuration File Through the Serial Console Port Passwor
Contents Configuring POS Interface Framing Mode 5-4 Configuring POS Interface Encapsulation Type Under GFP-F Framing SONET Alarms 5-6 Configuring SONET Alarms 5-6 Configuring SONET Delay Triggers 5-7 Monitoring and Verifying POS CHAPTER 6 5-5 5-8 Configuring STP and RSTP on the ML-Series Card 6-1 STP Features 6-1 STP Overview 6-2 Supported STP Instances 6-2 Bridge Protocol Data Units 6-2 Election of the Root Switch 6-3 Bridge ID, Switch Priority, and Extended System ID Spanning-Tree Timers 6-4 Creat
Contents Configuring the Root Switch 6-17 Configuring the Port Priority 6-17 Configuring the Path Cost 6-18 Configuring the Switch Priority of a Bridge Group 6-18 Configuring the Hello Time 6-19 Configuring the Forwarding-Delay Time for a Bridge Group 6-20 Configuring the Maximum-Aging Time for a Bridge Group 6-20 Verifying and Monitoring STP and RSTP Status CHAPTER 7 Configuring VLANs on the ML-Series Card Understanding VLANs 7-1 7-1 Configuring IEEE 802.1Q VLAN Encapsulation IEEE 802.
Contents Understanding Encapsulation over FEC or POS Channel 9-6 Configuring Encapsulation over EtherChannel or POS Channel Encapsulation over EtherChannel Example 9-7 9-6 Monitoring and Verifying EtherChannel and POS 9-8 Load Balancing on the ML-Series cards 9-9 CHAPTER 10 Configuring IRB on the ML-Series Card 10-1 Understanding Integrated Routing and Bridging Configuring IRB 10-2 IRB Configuration Example Monitoring and Verifying IRB CHAPTER 11 10-1 10-3 10-4 Configuring Quality of Service
Contents class-map match-any and class-map match-all Commands Example match spr1 Interface Example 11-19 ML-Series VoIP Example 11-20 ML-Series Policing Example 11-20 ML-Series CoS-Based QoS Example 11-21 Understanding Multicast QoS and Multicast Priority Queuing Default Multicast QoS 11-23 Multicast Priority Queuing QoS Restrictions 11-24 Configuring Multicast Priority Queuing QoS QoS not Configured on Egress 11-19 11-23 11-24 11-26 ML-Series Egress Bandwidth Example 11-26 Case 1: QoS with Priority a
Contents Modifying ACL TCAM Size CHAPTER 14 13-5 Configuring Resilient Packet Ring on the ML-Series Card 14-1 Understanding RPR 14-1 Role of SONET Circuits 14-2 Packet Handling Operations 14-2 Ring Wrapping 14-3 RPR Framing Process 14-4 MAC Address and VLAN Support 14-6 RPR QoS 14-6 CTM and RPR 14-6 Configuring RPR 14-6 Connecting the ML-Series Cards with Point-to-Point STS Circuits 14-7 Configuring CTC Circuits for RPR 14-7 CTC Circuit Configuration Example for RPR 14-7 Configuring RPR Characteristi
Contents Secure Shell on the ML-Series Card 15-2 Understanding SSH 15-2 Configuring SSH 15-3 Configuration Guidelines 15-3 Setting Up the ML-Series Card to Run SSH 15-3 Configuring the SSH Server 15-4 Displaying the SSH Configuration and Status 15-5 RADIUS on the ML-Series Card 15-6 RADIUS Relay Mode 15-6 Configuring RADIUS Relay Mode 15-7 RADIUS Stand Alone Mode 15-7 Understanding RADIUS 15-8 Configuring RADIUS 15-8 Default RADIUS Configuration 15-9 Identifying the RADIUS Server Host 15-9 Configuring
Contents CE-100T-8 SONET Circuits and Features 17-6 Available Circuit Sizes and Combinations 17-6 CE-100T-8 STS/VT Allocation Tab 17-8 CE-100T-8 VCAT Characteristics 17-9 CE-100T-8 POS Encapsulation, Framing, and CRC 17-10 CE-100T-8 Loopback, J1 Path Trace, and SONET Alarms 17-11 APPENDIX A Command Reference for the ML-Series Card APPENDIX B Unsupported CLI Commands for the ML-Series Card Unsupported Privileged Exec Commands A-1 B-1 Unsupported Global Configuration Commands B-1 Unsupported POS I
Contents Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
F I G U R E S Figure 3-1 CTC Node View Showing IP Address Figure 3-2 Console Cable Adapter Figure 6-1 Spanning-Tree Topology Figure 6-2 Spanning-Tree Interface States Figure 6-3 Spanning Tree and Redundant Connectivity Figure 6-4 Proposal and Agreement Handshaking for Rapid Convergence Figure 6-5 Sequence of Events During Rapid Convergence Figure 7-1 VLANs Spanning Devices in a Network Figure 7-2 Bridging IEEE 802.1Q VLANs Figure 8-1 IEEE 802.
Figures Figure 14-5 Three-Node RPR Example Figure 14-6 RPR Bridge Group Figure 14-7 Two-Node RPR Before the Addition 14-17 Figure 14-8 Three-Node RPR After the Addition 14-18 Figure 14-9 Three-Node RPR Before the Deletion Figure 14-10 Two-Node RPR After the Deletion Figure 16-1 Bridging Example Figure 17-1 CE-100T-8 Point-to-Point Circuit Figure 17-2 Flow Control Figure 17-3 End-to-End Ethernet Link Integrity Support Figure 17-4 CE-100T-8 STS/VT Allocation Tab Figure 17-5 ONS CE-10
T A B L E S Table 2-1 ML-Series POS Statistics Fields and Buttons Table 2-2 ML-Series Ethernet Statistics Fields and Buttons Table 3-1 RJ-11 to RJ-45 Pin Mapping 3-4 Table 3-2 Cisco IOS Command Modes 3-10 Table 5-1 ML-Series Card Supported Circuit Sizes and Sizes Required for Ethernet Wire Speeds Table 5-2 ML-Series Card Encapsulation, Framing, and CRC Sizes Table 6-1 Switch Priority Value and Extended System ID Table 6-2 Spanning-Tree Timers 6-4 Table 6-3 Port State Comparison 6-10 T
Tables Table 12-2 Partitioning the TCAM Size for ACLs Table 13-1 Commands for Numbered Standard and Extended IP ACLs Table 13-2 Applying ACL to Interface Table 14-1 Definitions of RPR Frame Fields Table 15-1 Commands for Displaying the SSH Server Configuration and Status Table 17-1 IP ToS Priority Queue Mappings Table 17-2 CoS Priority Queue Mappings Table 17-3 CE-100T-8 Supported Circuit Sizes Table 17-4 SONET Circuit Size Required for Ethernet Wire Speeds Table 17-5 CCAT High Order Cir
Preface 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.
Preface Date Notes January 2009 Added the following sections in Chapter 11, Configuring Quality of Service on the ML-Series Card: • QoS not Configured on Egress • ML-Series Egress Bandwidth Example • Added a new bullet point in the “IP SLA Restrcitions on the ML-Series” section. • Added Tables 9-1 and 9-2 and updated Table 4 in the “Load Balancing on ML-Series Cards” section of Chapter 9, Configuring Link Aggregation on the ML-Series Cards.
Preface • For detailed reference information about Cisco ONS 15310-CL or Cisco ONS 15310-MA cards, nodes, and networks, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. 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.
Preface 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.
Preface 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. Utilizzare il numero di istruzione presente alla fine di ciascuna avvertenza per individuare le traduzioni delle avvertenze riportate in questo documento.
Preface Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
Preface 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.
Preface Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
Preface 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, Obtaining Support, and Security Guidelines section. 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.
Preface Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 1 o Overview of the ML-Series Card This chapter provides an overview of the ML-100T-8 card for Cisco ONS 15310-CL and the Cisco ONS 15310-MA. It lists Ethernet and SONET capabilities and Cisco IOS and Cisco Transport Controller (CTC) software features, with brief descriptions of selected features. The CE-100T-8 card for the Cisco ONS 15310-CL and the Cisco ONS 15310-MA is covered in Chapter 17, “CE-100T-8 Ethernet Operation.
Chapter 1 Overview of the ML-Series Card ML-Series Feature List ML-Series Feature List The ML-100T-8 has the following features: • Layer 1 data features: – 10/100BASE-TX half-duplex and full-duplex data transmission – IEEE 802.
Chapter 1 Overview of the ML-Series Card ML-Series Feature List – Bundling the two POS ports – LEX encapsulation only – IRB – IEEE 802.
Chapter 1 Overview of the ML-Series Card Key ML-Series Features – Cisco IOS Release 12.
Chapter 1 Overview of the ML-Series Card Key ML-Series Features Link Aggregation (FEC and POS) The ML-Series offers Fast EtherChannel and POS channel link aggregation. Link aggregation groups multiple ports into a larger logical port and provides resiliency during the failure of any individual ports. The ML-Series supports a maximum of four Ethernet ports in Fast EtherChannel, and two SONET virtual ports in POS channel. POS channel is only supported with LEX encapsulation.
Chapter 1 Overview of the ML-Series Card Key ML-Series Features TL1 TL1 on the ML-Series cards can be used for card inventory, fault and alarm management, card provisioning, and retrieval of status information for both data and SONET ports. TL1 can also be used to provision SONET STS circuits and transfer a Cisco IOS startup configuration file to the card memory. For specific TL1 commands and general TL1 information, refer to the Cisco ONS SONET TL1 Command Guide.
CH A P T E R 2 CTC Operations on the ML-Series Card This chapter covers Cisco Transport Controller (CTC) operation 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 (POS) ports of the ML-Series card.
Chapter 2 CTC Operations on the ML-Series Card Displaying ML-Series Ethernet Statistics in CTC Table 2-1 ML-Series POS Statistics Fields and Buttons Button Description 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 on the ML-Series Card Displaying ML-Series POS Ports Provisioning Information on CTC The following fields can be provisioned using CTC: Port Name, Pre-Service Alarm Suppression (PSAS), and Soak Time. Click the Port Name field to assign a name to the port. For more information on provisioning these fields, refer to the “Change Card Settings” chapter in the Cisco ONS 15454 Procedure Guide. Note The port name can also be configured in Cisco IOS.
Chapter 2 CTC Operations on the ML-Series Card Displaying SONET Alarms The Provisioning > POS Ports tab displays the following information: • Port #—Fixed number identifier for the specific port. • Port Name—Configurable 12-character alphanumeric identifier for the port. • Admin State—Configured administrative port state, which is active or inactive. Possible values are UP and DOWN. For the UP value to appear, a POS port must be both administratively active and have a SONET/SDH circuit provisioned.
Chapter 2 CTC Operations on the ML-Series Card Provisioning SONET Circuits Note The initial state of the ML-Series card POS port is inactive. A Cisco IOS POS interface command of no shutdown is required to carry traffic on the SONET circuit. Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
Chapter 2 CTC Operations on the ML-Series Card Provisioning SONET Circuits Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 3 Initial Configuration of the ML-Series Card 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-1 • Startup Configuration File, page 3-5 • Cisco IOS Command Modes, page 3-9 • Using the Command Modes, page 3-11 Hardware Installation This section lists hardware installation tasks, including booting up the ML-Series card.
Chapter 3 Initial Configuration of the ML-Series Card Cisco IOS on the ML-Series Card During a soft reset, which reloads or warm restarts the ML-Series card, the ML-Series card checks the cache for a Cisco IOS image. If a valid and current Cisco IOS image exists, the ML-Series card decompresses and initializes the image. If the image does not exist, the ML-Series requests a new copy of the Cisco IOS image from the 15310-CL-CTX or CTX2500.
Chapter 3 Initial Configuration of the ML-Series Card Cisco IOS on the ML-Series Card Step 1 Obtain the node IP address from the IP Addr field shown at the CTC node view (Figure 3-1). Figure 3-1 CTC Node View Showing IP Address 134411 Node IP address Step 2 If you are telnetting into an ONS 15310-CL with an ML-Series card, use the IP address and the port number 2001 as the Telnet address in your preferred communication program. For example with the IP address of 10.92.18.
Chapter 3 Initial Configuration of the ML-Series Card Cisco IOS on the ML-Series Card ML-Series IOS CLI Console Port The ML-Series card has an RJ-11 serial console port on the card faceplate labeled Console. It enables communication from the serial port of a PC or workstation running terminal emulation software to the Cisco IOS CLI on a specific ML-Series card.
Chapter 3 Initial Configuration of the ML-Series Card Startup Configuration File • 8 data bits • 1 stop bit • No parity Step 2 Insert the RJ-45 connector of the supplied cable into the female end of the supplied console cable adapter. 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.
Chapter 3 Initial Configuration of the ML-Series Card Startup Configuration File Manually Creating a Startup Configuration File Through the Serial Console Port Configuration through the serial console port is familiar to those who have worked with other products using Cisco IOS. At the end of the configuration procedure, the copy running-config startup-config command saves a startup configuration file. The serial console port gives the user visibility to the entire booting process of the ML-Series card.
Chapter 3 Initial Configuration of the ML-Series Card Startup Configuration File Command Purpose Step 3 Router(config)# enable password password Sets the enable password. See the “Passwords” section on page 3-6. Step 4 Router(config)# enable secret password Allows you to enter an enable secret password. See the “Passwords” section on page 3-6. A user must enter the enable secret password to gain access to global configuration mode.
Chapter 3 Initial Configuration of the ML-Series Card Startup Configuration File Loading a Cisco IOS Startup Configuration File Through CTC CTC allows a user to load the startup configuration file required by the ML-Series card. A Cisco-supplied sample Cisco IOS startup configuration file, named Basic-IOS-startup-config.txt, is available on the Cisco ONS 15310 software CD. CISCO15 is the Cisco IOS CLI default line password and the enable password for this configuration.
Chapter 3 Initial Configuration of the ML-Series Card Cisco IOS Command Modes Note If there is a parsing error when the Cisco IOS startup configuration file is downloaded and parsed at initialization, an ERROR-CONFIG alarm is reported and appears under the CTC alarms tab or in TL1. No other Cisco IOS error messages regarding the parsing of text are reported to the CTC or in TL1.
Chapter 3 Initial Configuration of the ML-Series Card Cisco IOS Command Modes Note Table 3-2 When a process makes unusually heavy demands on the CPU of the ML-Series card, it might impair CPU response time and cause a CPUHOG error message to appear on the console. This message indicates which process used a large number of CPU cycles, such as the updating of the routing table with a large number of routes due to an event.
Chapter 3 Initial Configuration of the ML-Series Card Using the Command Modes 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. From global configuration mode, you can enter interface configuration mode, subinterface configuration mode, and a variety of protocol-specific modes.
Chapter 3 Initial Configuration of the ML-Series Card Using the Command Modes 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. Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 4 Configuring Interfaces on the ML-Series Card 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 (POS) interface configuration is covered in Chapter 5, “Configuring POS on 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 4 Configuring Interfaces on the ML-Series Card General Interface Guidelines To find MAC addresses for a device, use the show interfaces command, as follows: ML_Series# show interfaces fastethernet 0 FastEthernet0 is up, line protocol is up Hardware is epif_port, address is 000b.fcfa.339e (bia 000b.fcfa.
Chapter 4 Configuring Interfaces on the ML-Series Card 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 on the ML-Series Card Basic Fast Ethernet and POS Interface Configuration 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Basic Fast Ethernet and POS Interface Configuration ML-Series cards support Fast Ethernet and POS interfaces. This section provides some examples of configurations for all interface types.
Chapter 4 Configuring Interfaces on the ML-Series Card Basic Fast Ethernet and POS Interface Configuration Command Purpose | Step 4 ML_Series(config-if)# [no] duplex {full half | auto} Step 5 ML_Series(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 on the ML-Series Card Monitoring Operations on the Fast Ethernet Interfaces Command Purpose Step 3 ML_Series(config-if)# shutdown Manually shuts down the interface. Encapsulation changes on POS ports are allowed only when the interface is shut down (ADMIN_DOWN). Step 4 ML_Series(config-if)# encapsulation type Sets the encapsulation type.
Chapter 4 Configuring Interfaces on the ML-Series Card Monitoring Operations on the Fast Ethernet Interfaces 4095063706 packets input, 3885007012 bytes Received 0 broadcasts (0 IP multicast) 2 runts, 0 giants, 0 throttles 4 input errors, 0 CRC, 0 frame, 1 overrun, 0 ignored 0 watchdog, 0 multicast 0 input packets with dribble condition detected 1463732665 packets output, 749573412 bytes, 0 underruns 131072 output errors, 131072 collisions, 0 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost
Chapter 4 Configuring Interfaces on the ML-Series Card Monitoring Operations on the Fast Ethernet Interfaces pkts_good_runts pkts_error_runts pkts_ucast pkts_mcast pkts_bcast align_errors FCS_errors Overruns 0 5 26976 57281 0 1 5 0 MAC Transmit Counters Bytes pkts64 pkts65to127 pkts128to255 pkts256to511 pkts512to1023 pkts1024to1518 pkts1519to1530 pkts_ucast pkts_mcast pkts_bcast pkts_fcs_err pkts_giants pkts_underruns pkts_one_collision pkts_multiple_collisions pkts_excessive_collision Ucode drops 165
CH A P T E R 5 Configuring POS on the ML-Series Card This chapter describes advanced packet-over-SONET (POS) interface configuration for the ML-Series card. Basic POS interface configuration is included in Chapter 4, “Configuring Interfaces on 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 5 Configuring POS on the ML-Series Card Understanding POS on the ML-Series Card Table 5-1 ML-Series Card Supported Circuit Sizes and Sizes Required for Ethernet Wire Speeds Ethernet Wire Speed CCAT High Order VCAT High Order 10 Mbps STS-1 STS-1-1v 100 Mbps — STS-1-2v 1 1. STS-1-2v provides a total transport capacity of 98 Mbps Caution The maximum tolerable VCAT differential delay for the ML-100T-8 is 48 milliseconds.
Chapter 5 Configuring POS on the ML-Series Card Configuring the POS Interface • Path-level alarms and conditions, including loss of pointer (LOP), unequipped (UNEQ-P), payload mismatch (PLM-P), alarm indication signal (AIS) detection, and remote defect indication (RDI) • J1 path trace for high-order paths Framing Mode, Encapsulation, Scrambling, MTU and CRC Support The ML-Series card on the ONS 15310-CL and ONS 15310-MA supports high-level data link control (HDLC) framing and frame-mapped generic fram
Chapter 5 Configuring POS on the ML-Series Card Configuring the POS Interface Scrambling on the ONS 15310-CL and ONS 15310-MA ML-Series card is on by default and is not configurable. The C2 byte is not configurable. CRC-under-HDLC framing is restricted to 32-bit and is not configurable. CRC-under-GFP-F is restricted to 32-bit, but can be enabled (default) and disabled. Note ML-Series card POS interfaces normally send PDI-P to the far end when the POS link goes down or RPR wraps.
Chapter 5 Configuring POS on the ML-Series Card Configuring the POS Interface Step 3 Command Purpose Router(config-if)# [no] pos mode gfp [fcs-disabled] Sets the framing mode employed by the ONS Ethernet card for framing and encapsulating data packets onto the SONET transport layer. Valid framing modes are: • HDLC—A common mechanism employed in framing data packets for SONET. HDLC is not a keyword choice in the command. The no form of the command sets the framing mode to Cisco HDLC.
Chapter 5 Configuring POS on the ML-Series Card Configuring the POS Interface Step 3 Command Purpose Router(config-if)# encapsulation type Sets the encapsulation type. Valid values are: • hdlc—Cisco HDLC • lex—(default) LAN extension (Cisco-EoS-LEX), special encapsulation for use with Cisco ONS Ethernet line cards • ppp—Point-to-Point Protocol Note Under HDLC framing, the ONS 15310-CL and ONS 15310-MA ML-Series card is restricted to LEX encapsulation.
Chapter 5 Configuring POS on the ML-Series Card Configuring the POS Interface Command Purpose Step 1 Router(config)# interface pos number Enters interface configuration mode and specifies the POS interface to configure. Step 2 Router(config-if)# pos report {all | encap | pais | plop | ppdi | pplm | prdi | ptim | puneq | sd-ber-b3 | sf-ber-b3} Permits console logging of selected SONET alarms. Use the no form of the command to disable reporting of a specific alarm.
Chapter 5 Configuring POS on the ML-Series Card Monitoring and Verifying POS 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 on the ML-Series Card Monitoring and Verifying POS CCAT/VCAT info not available yet! 56517448726 total input packets, 4059987309747 post-encap bytes 0 input short packets, ?? pre-encap bytes 283 input CRCerror packets , 0 input drop packets 564 rx HDLC addr mismatchs , 564 rx HDLC ctrl mismatchs 564 rx HDLC sapi mismatchs , 564 rx HDLC ctrl mismatchs 0 rx HDLC destuff errors , 564 rx HDLC invalid frames 0 input abort packets 5049814101 input packets dropped by ucode 0 input packe
Chapter 5 Configuring POS on the ML-Series Card Monitoring and Verifying POS Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 6 Configuring STP and RSTP on the ML-Series Card 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 6-1 • RSTP Features, page 6-9 • Interoperability with IEEE 802.
Chapter 6 Configuring STP and RSTP on the ML-Series Card STP Features 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 6 Configuring STP and RSTP on the ML-Series Card STP Features • Message age • Identifier of the sending interface • Values for the hello, forward delay, and max-age protocol timers 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.
Chapter 6 Configuring STP and RSTP on the ML-Series Card STP Features BPDUs contain information about the sending switch and its ports, including switch and MAC addresses, switch priority, port priority, and path cost. Spanning tree uses this information to elect the root switch and root port for the switched network and the root port and designated port for each switched segment. Bridge ID, Switch Priority, and Extended System ID The IEEE 802.
Chapter 6 Configuring STP and RSTP on the ML-Series Card STP Features Creating the Spanning-Tree Topology In Figure 6-1, Switch A is elected as the root switch because the switch priority of all the switches is set to the default (32768) and Switch A has the lowest MAC address. However, because of traffic patterns, number of forwarding interfaces, or link types, Switch A might not be the ideal root switch.
Chapter 6 Configuring STP and RSTP on the ML-Series Card STP Features 2. From blocking to listening or to disabled 3. From listening to learning or to disabled 4. From learning to forwarding or to disabled 5. From forwarding to disabled Figure 6-2 illustrates how an interface moves through the states.
Chapter 6 Configuring STP and RSTP on the ML-Series Card STP Features • Discards frames switched from another interface for forwarding • Does not learn addresses • Receives BPDUs Listening State The listening state is the first state a Layer 2 interface enters after the blocking state. The interface enters this state when the spanning tree determines that the interface should participate in frame forwarding.
Chapter 6 Configuring STP and RSTP on the ML-Series Card STP Features 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 6 Configuring STP and RSTP on the ML-Series Card RSTP Features 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 6 Configuring STP and RSTP on the ML-Series Card RSTP Features Port Roles and the Active Topology The RSTP provides rapid convergence of the spanning tree by assigning port roles and by determining the active topology. The RSTP builds upon the IEEE 802.1D STP to select the switch with the highest switch priority (lowest numerical priority value) as the root switch as described in the “Election of the Root Switch” section on page 6-3.
Chapter 6 Configuring STP and RSTP on the ML-Series Card RSTP Features Rapid Convergence The RSTP provides for rapid recovery of connectivity following the failure of switch, a switch port, or a LAN. It provides rapid convergence for new root ports, and ports connected through point-to-point links as follows: • 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.
Chapter 6 Configuring STP and RSTP on the ML-Series Card RSTP Features Figure 6-4 Proposal and Agreement Handshaking for Rapid Convergence ML-Series ML-Series Proposal Switch B Switch A Root F DP Agreement ML-Series F RP Switch B ML-Series Root F DP F RP ML-Series Proposal Switch B Switch A Switch B ML-Series Root F DP Switch A DP = designated port RP = root port F = forwarding F RP F DP Switch B Agreement ML-Series F RP Switch B 124086 Switch A Synchronization of Port Roles When
Chapter 6 Configuring STP and RSTP on the ML-Series Card RSTP Features Figure 6-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 6 Configuring STP and RSTP on the ML-Series Card RSTP Features The sending switch sets the agreement flag in the RSTP BPDU to accept the previous proposal. The port role in the agreement message is always set to the root port. 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.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Interoperability with IEEE 802.1D STP • Propagation—When an RSTP switch receives a TC message from another switch through a designated or root port, it propagates the topology change to all of its non-edge, edge, designated ports, and root port (excluding the port on which it is received). The switch starts the TC-while timer for all such ports and flushes the information learned on them.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Configuring STP and RSTP Features Default STP and RSTP Configuration Table 6-5 shows the default STP and RSTP configuration. Table 6-5 Default STP and RSTP Configuration Feature Default Setting Enable state Up to 255 spanning-tree instances can be enabled.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Configuring STP and RSTP Features To reenable STP, use the no bridge-group bridge-group-number spanning disabled interface-level configuration command. Configuring the Root Switch The switch maintains a separate spanning-tree instance for each active VLAN configured on it. A bridge ID, consisting of the switch priority and the switch MAC address, is associated with each instance.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Configuring STP and RSTP Features Configuring the Path Cost The spanning-tree path cost default value is derived from the media speed of an interface. If a loop occurs, spanning tree uses cost when selecting an interface to put in the forwarding state. You can assign lower cost values to interfaces that you want selected first and higher cost values to interfaces that you want selected last.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Configuring STP and RSTP Features Beginning in privileged EXEC mode, follow these steps to configure the switch priority of a bridge group: Command Purpose Step 1 ML_Series# configure terminal Enters the global configuration mode. Step 2 ML_Series(config)# bridge bridge-group-number priority priority-number Configures the switch priority of a bridge group. For priority, the range is 0 to 61440 in increments of 4096; the default is 32768.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Verifying and Monitoring STP and RSTP Status 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 ML_Series# configure terminal Enters global configuration mode. Step 2 ML_Series(config)# bridge bridge-group-number forward-time seconds Configures the forward time of a VLAN.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Verifying and Monitoring STP and RSTP Status Table 6-6 Note Commands for Displaying Spanning-Tree Status Command Purpose ML_Series# show spanning-tree Displays detailed STP or RSTP information. ML_Series# show spanning-tree brief Displays brief summary of STP or RSTP information. ML_Series# show spanning-tree interface interface-id Displays STP or RSTP information for the specified interface.
Chapter 6 Configuring STP and RSTP on the ML-Series Card Verifying and Monitoring STP and RSTP Status Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------8 bridges 8 0 0 0 16 Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 7 Configuring VLANs on the ML-Series Card 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 7-1 • Configuring IEEE 802.1Q VLAN Encapsulation, page 7-2 • IEEE 802.
Chapter 7 Configuring VLANs on the ML-Series Card Configuring IEEE 802.1Q VLAN Encapsulation ML-Series switching supports up to 254 VLAN subinterfaces per interface. 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 7-1 shows a network topology in which two VLANs span two ONS 15310-CLs with ML-Series cards.
Chapter 7 Configuring VLANs on the ML-Series Card IEEE 802.1Q VLAN Configuration Command Purpose Step 6 ML_Series(config-subif)# end Returns to privileged EXEC mode. Step 7 ML_Series# copy running-config startup-config (Optional) Saves your configuration changes to NVRAM. Note In a bridge group on the ML-Series card, the VLAN ID does not have to be uniform across interfaces that belong to that bridge group.
Chapter 7 Configuring VLANs on the ML-Series Card IEEE 802.1Q VLAN Configuration Figure 7-2 Bridging IEEE 802.1Q VLANs ML-Series Router_B ML-Series 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 Fast Ethernet 0.2 Fast Ethernet 0.4 Switch Switch VLAN 2 VLAN 4 Host station Host station VLAN 4 VLAN 2 Fast Ethernet 0.3 VLAN 3 Host station Fast Ethernet 0.
Chapter 7 Configuring VLANs on the ML-Series Card Monitoring and Verifying VLAN Operation ! interface POS0.2 encapsulation dot1Q 2 bridge-group 2 ! interface POS0.3 encapsulation dot1Q 3 bridge-group 3 ! interface POS0.4 encapsulation dot1Q 4 bridge-group 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] (Example 7-2).
Chapter 7 Configuring VLANs on the ML-Series Card Monitoring and Verifying VLAN Operation Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card 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 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Understanding IEEE 802.1Q Tunneling Customer traffic tagged in the normal way with appropriate VLAN IDs comes from an IEEE 802.1Q trunk port on the customer device and into a tunnel port on the ML-Series card. The link between the customer device and the ML-Series card is an asymmetric link because one end is configured as an IEEE 802.1Q trunk port and the other end is configured as a tunnel port.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card 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 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card 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 8-4 • Configuring an IEEE 802.1Q Tunneling Port, page 8-4 • IEEE 802.1Q Example, page 8-5 By default, IEEE 802.1Q tunneling is not configured on the ML-Series. IEEE 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Configuring IEEE 802.1Q Tunneling Command Purpose Step 4 ML_Series(config-if)# bridge-group vlan-number Assigns the tunnel port to a VLAN. 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.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Understanding VLAN-Transparent and VLAN-Specific Services bridge-group 40 Example 8-2 ML_Series B Configuration no ip routing bridge 30 protocol ieee bridge 40 protocol ieee ! ! interface FastEthernet0 no ip routing mode dot1q-tunnel bridge-group 30 ! interface FastEthernet1 mode dot1q-tunnel bridge-group 40 ! interface POS0 ! interface POS0.1 encapsulation dot1Q 30 bridge-group 30 ! interface POS0.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card VLAN-Transparent and VLAN-Specific Services Configuration Example A VLAN-specific service on a subinterface coexists with the VLAN-transparent service, often IEEE 802.1Q tunneling, on a physical interface. VLANs configured for a VLAN-transparent service and a VLAN-specific service follow the VLAN-specific service configuration. If you need to configure IEEE 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card VLAN-Transparent and VLAN-Specific Services Configuration Example mode dot1q-tunnel bridge-group 10 bridge-group 10 spanning-disabled ! interface FastEthernet0.3 encapsulation dot1Q 30 bridge-group 30 ! interface POS0 ! interface POS0.1 encapsulation dot1Q 10 bridge-group 10 ! interface POS0.3 encapsulation dot1Q 30 bridge-group 30 Example 8-4 applies to ML-Series card B.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Understanding Layer 2 Protocol Tunneling no ip address no ip route-cache mode dot1q-tunnel bridge-group 10 bridge-group 10 spanning-disabled ! interface POS0.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Configuring Layer 2 Protocol Tunneling protocol tunneling for CDP, STP, and VTP at the interface and subinterface level. Multiple STP (MSTP) tunneling support is achieved through subinterface protocol tunneling. The ML-Series cards connected to the customer switch perform the tunneling process.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Configuring Layer 2 Protocol Tunneling • Tunneling is not supported on trunk ports. If you enter the l2protocol-tunnel interface configuration command on a trunk port, the command is accepted, but Layer 2 tunneling does not take effect unless you change the port to a tunnel port. • EtherChannel port groups are compatible with tunnel ports as long as the IEEE 802.
Chapter 8 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card Configuring Layer 2 Protocol Tunneling Configuring Layer 2 Tunneling Per-VLAN Beginning in privileged EXEC mode, follow these steps to configure a VLAN as a Layer 2 tunnel VLAN: Command Purpose Step 1 ML_Series# configuration terminal Enters global configuration mode. Step 2 ML_Series(config)# bridge bridge-group-number protocol type Creates a bridge group number and specifies a protocol.
CH A P T E R 9 Configuring Link Aggregation on the ML-Series Card This chapter describes how to configure link aggregation for the ML-Series cards, both EtherChannel and packet-over-SONET (POS) channel. For additional information about the Cisco IOS commands used in this chapter, refer to the Cisco IOS Command Reference publication.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Configuring Link Aggregation Each ML100-FX supports up to four FECs plus an additional POS channel, a port channel made up of the two POS ports. 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. Caution The EtherChannel interface is the Layer 2/Layer 3 interface. Do not enable Layer 3 addresses on the physical interfaces.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Configuring Link Aggregation For information on other configuration tasks for the EtherChannel, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Configuring Link Aggregation interface FastEthernet 1 channel-group 1 ! interface POS 0 bridge-group 1 Example 9-2 ML_Series B Configuration hostname Switch B no ip routing ! bridge 1 protocol ieee ! interface Port-channel 1 bridge-group 1 hold-queue 150 in ! interface FastEthernet 0 channel-group 1 ! interface FastEthernet 1 channel-group 1 ! interface POS 0 bridge-group 1 ! Configuring POS Channel You can configure a POS channel by creati
Chapter 9 Configuring Link Aggregation on the ML-Series Card Configuring Link Aggregation Caution The POS channel interface is the routed interface. Do not enable Layer 3 addresses on any physical interfaces. Do not assign bridge groups on any physical interfaces because doing so creates loops.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Understanding Encapsulation over FEC or POS Channel ! interface POS0 channel-group 1 ! interface POS1 channel-group 1 Example 9-4 ML_Series B Configuration bridge irb bridge 1 protocol ieee ! ! interface Port-channel1 bridge-group 1 ! interface FastEthernet0 bridge-group 1 ! interface POS0 channel-group 1 ! interface POS1 no ip address channel-group 1 Understanding Encapsulation over FEC or POS Channel When configuring encapsulation over FE
Chapter 9 Configuring Link Aggregation on the ML-Series Card Understanding Encapsulation over FEC or POS Channel Step 4 Command Purpose Router(config-subif)# end Exits to privileged EXEC mode. Note Step 5 Router# copy running-config startup-config Optionally, you can remain in interface configuration mode and enable other supported interface commands to meet your requirements. (Optional) Saves the configuration changes to NVRAM.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Monitoring and Verifying EtherChannel and POS interface FastEthernet0 channel-group 1 ! interface FastEthernet1 channel-group 1 ! interface POS0 ! interface POS0.1 encapsulation dot1Q 1 native bridge-group 1 ! interface POS0.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Monitoring and Verifying EtherChannel and POS Example 9-7 show interfaces port-channel Command ML_Series# show int port-channel 9 Port-channel9 is down, line protocol is down Hardware is FEChannel, address is 0000.0000.0000 (bia 0000.0000.0000) Internet address is 192.26.24.
Chapter 9 Configuring Link Aggregation on the ML-Series Card Monitoring and Verifying EtherChannel and POS Table 9-1 MAC Based- 2- Port Channel Interface Second Least Significant bit of the MAC-DA Second Least Significant bit of the MAC-SA XOR Result Used Member Interface for the Frame Forwarding to the EtherChannel and/or Port Channel 1 0 1 Port 2 1 1 0 Port 1 Table 9-2 IP Based- 2- Port Channel Interface Second Least Significant bit of the IP-DA Second Least Significant bit of the IP-S
Chapter 9 Configuring Link Aggregation on the ML-Series Card Monitoring and Verifying EtherChannel and POS Table 9-3 MAC Based - 4-Port Channel Interface Used Member Interface for the Frame Forwarding to the EtherChannel and/or Port Channel Third Least Significant bit of the MAC-DA Third Least Significant bit of the MAC-SA Second Least Significant bit of the MAC-DA Second Least Significant bit of the MAC-SA XOR Result 0 0 1 0 01 Second 0 0 1 1 00 First 0 1 0 0 10 Third 0 1 0 1
Chapter 9 Configuring Link Aggregation on the ML-Series Card Monitoring and Verifying EtherChannel and POS Table 9-4 IP Based - 4-Port Channel Interface Used Member Interface for the Frame Forwarding to the EtherChannel and/or Port Channel Third Least Significant bit of the IP-DA Third Least Significant bit of the IP-SA Second Least Significant bit of the IP-DA Second Least Significant bit of the IP-SA XOR Result 0 1 1 0 11 Fourth 0 1 1 1 10 Second 1 0 0 0 10 Second 1 0 0 1
CH A P T E R 10 Configuring IRB on the ML-Series Card 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 10 Configuring IRB on the ML-Series Card Configuring IRB Before configuring IRB, consider the following: • 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.
Chapter 10 Configuring IRB on the ML-Series Card IRB Configuration Example Command Purpose Step 4 ML_Series(config-if)# ip address ip-address ip-address-subnet-mask Configures IP addresses on routed interfaces. Step 5 ML_Series(config-if)# end Returns to privileged EXEC mode. To enable and configure IRB and BVI, perform the following procedure, beginning in global configuration mode: Command Purpose Step 1 ML_Series(config)# bridge irb Enables IRB. Allows bridging of traffic.
Chapter 10 Configuring IRB on the ML-Series Card Monitoring and Verifying IRB Example 10-1 Configuring ML_Series A bridge irb bridge 1 protocol ieee bridge 1 route ip ! ! interface FastEthernet0 ip address 192.168.2.1 255.255.255.0 ! interface POS0 no ip address bridge-group 1 ! interface POS1 no ip address bridge-group 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.
Chapter 10 Configuring IRB on the ML-Series Card Monitoring and Verifying IRB Table 10-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 10 Configuring IRB on the ML-Series Card Monitoring and Verifying IRB clns ip Software MAC address filter on POS0 Hash Len Address Matches 0x00: 0 ffff.ffff.ffff 0 0x25: 0 0012.0101.3624 0 0x29: 0 0012.0101.3628 0 0xC0: 0 0100.0ccc.cccc 0 0xC2: 0 0180.c200.0000 0 POS1 Bridged protocols on POS1: clns ip Software MAC address filter on POS1 Hash Len Address Matches 0x00: 0 ffff.ffff.ffff 0 0x24: 0 0012.0101.3625 0 0x29: 0 0012.0101.3628 0 0xC0: 0 0100.0ccc.cccc 0 0xC2: 0 0180.c200.
CH A P T E R 11 Configuring Quality of Service on the ML-Series Card This chapter describes the Quality of Service (QoS) features built into your ML-Series card. It also describes how to map QoS scheduling at both the system and interface levels.
Chapter 11 Configuring Quality of Service on the ML-Series Card Understanding QoS Understanding QoS The ML-Series card multiplexes multiple IP/Ethernet services onto the SONET circuit and dynamically allocates transmission bandwidth to data services based on data service requirements. This allows the network to operate at a significantly higher level of utilization.
Chapter 11 Configuring Quality of Service on the ML-Series Card Understanding QoS Figure 11-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
Chapter 11 Configuring Quality of Service on the ML-Series Card 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 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 11-3 illustrates the ML-Series QoS flow.
Chapter 11 Configuring Quality of Service on the ML-Series Card ML-Series QoS 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 11-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 11 Configuring Quality of Service on the ML-Series Card ML-Series QoS 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 11 Configuring Quality of Service on the ML-Series Card ML-Series QoS Weights are assigned to each queue as a result of the service provisioning process. When coupled with policing and policy mapping provisioning, these weights and the WDRR scheduling process ensure that QoS commitments are provided to each service flow. Figure 11-5 illustrates the ML-Series card’s queuing and scheduling.
Chapter 11 Configuring Quality of Service on the ML-Series Card ML-Series QoS Egress Priority Marking Egress priority marking allows the operator to assign the IEEE 802.1p CoS bits of packets that exit the card. This marking allows the operator to use the CoS bits as a mechanism for signaling to downstream nodes the QoS treatment that the packet should be given. This feature operates on the outer-most IEEE 802.1p CoS field.
Chapter 11 Configuring Quality of Service on the ML-Series Card QoS on RPR the QinQ network, the QoS is then implemented based on the IEEE 802.1p bit of the SP tag. The ML-Series cards do not have visibility into the customer CoS, IP precedence, or DSCP values after the packet is double-tagged (because it is beyond the entry point of the QinQ service). Figure 11-6 illustrates the QinQ implementation on the ML-Series card.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring QoS 2. If the packet comes in with an assigned CoS, the assigned CoS replaces the default. If an IP packet originates locally, the IP precedence setting replaces the CoS setting. 3. The input policy map has a set-cos action. 4. The output policy map has a set-cos action (except for broadcast or multicast packets). The RPR header contains a CoS value and DE indicator. The RPR DE is set for noncommitted traffic.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring QoS Table 11-1 Traffic Class Commands Command Purpose ML_Series(config)# class-map class-map-name Specifies the user-defined name of the traffic class. Names can be a maximum of 40 alphanumeric characters. If match-all or match-any is not specified, traffic must match all the match criteria to be classified as part of the traffic class. There is no default-match criteria. Multiple match criteria are supported.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring QoS with the traffic policy when the class command is used. The class command must be issued after entering policy-map configuration mode. After entering the class command, you are automatically in policy-map class configuration mode, which is where the QoS policies for the traffic policy are defined.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring QoS Table 11-2 Traffic Policy Commands (continued) Command Purpose ML_Series (config-pmap-c)# bandwidth {bandwidth-kbps | percent percent} Specifies a minimum bandwidth guarantee to a traffic class in periods of congestion. A minimum bandwidth guarantee can be specified in kbps or by a percentage of the overall available bandwidth.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring QoS Table 11-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 11 Configuring Quality of Service on the ML-Series Card Configuring QoS Table 11-2 Traffic Policy Commands (continued) Command Purpose ML_Series (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 11 Configuring Quality of Service on the ML-Series Card Monitoring and Verifying QoS Configuration To attach a traffic policy to an interface, perform the following procedure in global configuration mode: Step 1 Command Purpose ML_Series(config)# interface interface-id Enters interface configuration mode, and specifies the interface to apply the policy map. Valid interfaces are limited to physical Ethernet and packet-over-SONET (POS) interfaces.
Chapter 11 Configuring Quality of Service on the ML-Series Card QoS Configuration Examples Table 11-4 Commands for QoS Status (continued) Command Purpose ML_Series# show policy-map name Displays the user-specified policy map. ML_Series# show policy-map interface interface Displays configurations of all input and output policies attached to an interface. Statistics displayed with this command are unsupported and show zero. Example 11-1 shows examples of the QoS commands.
Chapter 11 Configuring Quality of Service on the ML-Series Card QoS Configuration Examples Traffic Classes Defined Example Example 11-2 shows how to create a class map called class1 that matches incoming traffic entering interface fastethernet0.
Chapter 11 Configuring Quality of Service on the ML-Series Card QoS Configuration Examples 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 11 Configuring Quality of Service on the ML-Series Card QoS Configuration Examples Match input-interface SPR1 Match cos 1 ML-Series VoIP Example Figure 11-7 shows an example of ML-Series voice-over- IP (VoIP). The associated commands are provided in Example 11-9. Figure 11-7 ML-Series VoIP Example ML-Series Router_A VoIP Traffic Fast Ethernet 0 POS 0 SONET/SDH During periods of congestion, the ML-Series card services all VoIP traffic before servicing any general data traffic.
Chapter 11 Configuring Quality of Service on the ML-Series Card QoS Configuration Examples Figure 11-8 ML-Series Policing Example ML-Series 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 11 Configuring Quality of Service on the ML-Series Card QoS Configuration Examples Figure 11-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 124097 ML-Series Card A Customer Access Point Example 11-11 shows the code used to configure ML-Series Card A in Figure 11-9.
Chapter 11 Configuring Quality of Service on the ML-Series Card Understanding Multicast QoS and Multicast Priority Queuing Understanding Multicast QoS and Multicast Priority 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 11 Configuring Quality of Service on the ML-Series Card Configuring Multicast Priority Queuing QoS Multicast Priority Queuing QoS Restrictions The following restrictions apply to multicast priority queuing QoS: • The bandwidth allocation and utilization configured for multicast priority queuing traffic is global and applies to all the ports on the ML-Series card, both POS and Fast Ethernet, regardless of whether these ports carry multicast priority queuing traffic.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring Multicast Priority Queuing QoS Table 11-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 11 Configuring Quality of Service on the ML-Series Card 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 11 Configuring Quality of Service on the ML-Series Card 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 11-14 QoS with Priority and Bandwidth Configured without Priority Multicast ! class-map match-
Chapter 11 Configuring Quality of Service on the ML-Series Card 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 Note For IEEE 802.
Chapter 11 Configuring Quality of Service on the ML-Series Card Configuring CoS-Based Packet Statistics 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.
Chapter 11 Configuring Quality of Service on the ML-Series Card Understanding IP SLA Cos Cos Cos Cos Cos 3: 4: 5: 6: 10 7: ML_Series# show interface FastEthernet0 Stats by Internal-Cos Input: Packets Cos 0: 123 Cos 1: Cos 2: 3 Cos 3: Cos 4: Cos 5: Cos 6: Cos 7: Output: Packets Cos 0: 1234567890 Cos 1: 3 Cos 2: Cos 3: Cos 4: Cos 5: Cos 6: 1 Cos 7: Output: Drop-pkts Cos 0: 1234567890 Cos 1: Cos 2: Cos 3: Cos 4: Cos 5: 1 Cos 6: 10 Cos 7: 640 fastethernet 0 cos Bytes 3564 211 Bytes 1234567890 200 64 D
Chapter 11 Configuring Quality of Service on the ML-Series Card Understanding IP SLA 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 11 Configuring Quality of Service on the ML-Series Card Understanding IP SLA • 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.
CH A P T E R 12 Configuring the Switching Database Manager on the ML-Series Card 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 12-1 • Understanding SDM Regions, page 12-1 • Configuring SDM, page 12-2 • Monitoring and Verifying SDM, page 12-3 Understanding the SDM The ONS 15310-CL and ONS 15310-MA ML-Series card features high-speed forwarding.
Chapter 12 Configuring the Switching Database Manager on the ML-Series Card Configuring SDM • Longest-match region—Each longest-match region consists of multiple buckets or groups of Layer 3 address entries organized in decreasing order by mask length. All entries within a bucket share the same mask value and key size. The buckets can change their size dynamically by borrowing address entries from neighboring buckets. Although the size of the whole application region is fixed, you can reconfigure it.
Chapter 12 Configuring the Switching Database Manager on the ML-Series Card Monitoring and Verifying SDM 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 12-2. Table 12-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 12 Configuring the Switching Database Manager on the ML-Series Card Monitoring and Verifying SDM Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 13 Configuring Access Control Lists on the ML-Series Card This chapter describes the access control list (ACL) features built into the ML-Series card and contains the following major sections: • Understanding ACLs, page 13-1 • ML-Series ACL Support, page 13-1 • Modifying ACL TCAM Size, page 13-5 Understanding ACLs ACLs provide network control and security, allowing you to filter packet flow into or out of ML-Series interfaces.
Chapter 13 Configuring Access Control Lists on the ML-Series Card ML-Series ACL Support • Access violations accounting is not supported on the ML-Series card. • 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.
Chapter 13 Configuring Access Control Lists on the ML-Series Card ML-Series ACL Support 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 13-3 • Creating Named Standard IP ACLs, page 13-4 • Creating Named Extended IP ACLs (Control Plane Only), page 13-4 • Applying the ACL to an Interface, page 13-4 Creating Numbered Standard and Extended IP ACLs Table 13-1 lists the global
Chapter 13 Configuring Access Control Lists on the ML-Series Card ML-Series ACL Support 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 ML_Series(config)# ip access-list standard name Defines a standard IP ACL using an alphabetic name.
Chapter 13 Configuring Access Control Lists on the ML-Series Card Modifying ACL TCAM Size Table 13-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 12-3.
Chapter 13 Configuring Access Control Lists on the ML-Series Card Modifying ACL TCAM Size Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 14 Configuring Resilient Packet Ring on the ML-Series Card 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 14 Configuring Resilient Packet Ring on the ML-Series Card Understanding RPR SONET, when used in this role. Although the IEEE 802.17 draft was used as reference for the Cisco ML-Series RPR implementation, the current ML-Series card RPR protocol does not comply with all clauses of IEEE 802.17. Role of SONET Circuits The ML-Series cards in an SPR must connect directly or indirectly through point-to-point STS circuits.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Understanding RPR Figure 14-1 RPR Packet Handling Operations Strip Pass through Bridge 124098 ML-Series RPR Ring Wrapping RPR initiates ring wraps in the event of a fiber cut, node failure, node restoration, new node insertion, or other traffic problem.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Understanding RPR Figure 14-2 RPR Ring Wrapping Ring Wrap Fiber Cut ML-Series RPR 124099 Ring Wrap In case of a ring failure, the ML-Series cards connected to the failed section of the RPR detect the failure through the SONET path alarms. When any ML-Series card receives this path-AIS signal, it wraps the POS interface that received the signal.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Understanding RPR 1 byte 1 byte RPR Frame for ML-Series Card 1 byte 2 bytes 68-1522 bytes RPR Payload Flag Add Control Protocol 0x7E 0x0F 0x00 0x0042 2-4 bytes 1 byte CRC Flag 0x7F 4 byte 4 bytes 60-1514 bytes RPR Address RPR Control 7 byte Ethernet Payload 1 byte 6 bytes 6 bytes 6 bytes Preamble SFD DA SA Ln/Type 46-1500 bytes 4 bytes Data/Pad FCS 134984 Figure 14-3 The RPR framing and header includes a num
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR Table 14-1 Definitions of RPR Frame Fields PRI A three-bit QoS class of service (CoS) field that establishes RPR priority. DE A one-bit field for the discard eligible flag. TTL A nine-bit field for the frame’s time to live. Type A field indicating whether the packet is data or control.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR Note 3. Configuring RPR Characteristics and the SPR Interface on the ML-Series Card, page 14-9 (Cisco IOS) 4. Assigning the ML-Series Card POS Ports to the SPR Interface, page 14-11 (Cisco IOS) 5. Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces, page 14-13 (Cisco IOS) 6. Verifying Ethernet Connectivity Between RPR Ethernet Access Ports, page 14-15 (Cisco IOS) 7.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR Figure 14-5 Three-Node RPR Example SPR Station-ID 1 POS 1 POS 0 POS 1 POS 0 SPR 1 SPR Station-ID 2 SPR Station-ID 3 POS 0 = STS circuit created on CTC 124100 POS 1 The three-node RPR in Figure 14-5 is used for all of the examples in the consecutive RPR procedures. Combining the examples will give you an end-to-end example of creating an RPR. It is assumed that the SONET node and its network is already active.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR 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 Click Next. The Source page appears. Step 8 Select Node 1 as the source node from the node drop-down list. Step 9 Select the ML-Series card from the Slot drop-down list, and choose 0 (POS) from the Port drop-down list. Step 10 Click Next. The Destination page appears.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR An SPR interface is configured similarly to a EtherChannel (port-channel) interface. Instead of using the channel-group command to define the members, you use the spr-intf-id command. Like the port-channel interface, you configure the virtual SPR interface instead of the physical POS interface.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR Step 5 Command Purpose Router(config-if)# carrier-delay msec milliseconds (Optional) Sets the carrier delay time. The default setting is 200 milliseconds, which is optimum for SONET protected circuits. Note If the carrier delay time is changed from the default, the new carrier delay time must be configured on all the ML-Series card interfaces.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR Step 4 Command Purpose Router(config-if)# carrier-delay msec milliseconds (Optional) Sets the carrier delay time. The default setting is 200 msec, which is optimum for SONET protected circuits. Note Step 5 Router(config-if)# pos trigger defect ber_sd-b3 The default unit of time for setting the carrier delay is seconds. The msec command resets the time unit to milliseconds.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces The default behavior of the ML-Series cards is that no traffic is bridged over the RPR even with the interfaces enabled. This is in contrast to many Layer 2 switches, including the Cisco Catalyst 6500 and the Cisco Catalyst 7600, which forward VLAN 1 by default.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR RPR Cisco IOS Configuration Example Figure 14-5 on page 14-8 shows a complete example of an RPR Cisco IOS configuration. The associated Cisco IOS code is provided in Examples 14-1, 14-2, and 14-3. The configuration assumes that ML-Series card POS ports are already linked by point-to-point SONET circuits configured through CTC.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Configuring RPR no ip address shutdown spr-intf-id 1 crc 32 interface POS1 no ip address spr-intf-id 1 crc 32 Example 14-3 SPR Station-ID 3 Configuration bridge irb interface SPR1 no ip address no keepalive spr station-id 3 bridge-group 10 bridge-group 10 spanning-disabled hold-queue 150 in interface FastEthernet0 no ip address bridge-group 10 bridge-group 10 spanning-disabled interface FastEthernet1 no ip address shutdown interface POS0
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Monitoring and Verifying RPR Monitoring and Verifying RPR After RPR is configured, you can monitor its status using the show interface spr 1 command (Example 14-4) or the show run interface spr 1 command (Example 14-5). Example 14-4 Example of show interface spr 1 Output ML-Series# show interfaces spr 1 SPR1 is up, line protocol is up Hardware is POS-SPR, address is 0005.9a39.77f8 (bia 0000.0000.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Add an ML-Series Card into an RPR Add an ML-Series Card into an RPR An existing RPR might need an ML-Series card added. This can be done without taking down data traffic due to the RPR wrapping capability and ring architecture. You can add the ML-Series card in concert with the addition of the node containing the card into the underlying SONET architecture.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Add an ML-Series Card into an RPR Figure 14-8 Three-Node 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 145991 POS 0 To add an ML-Series card to the 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 deleted.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Add an ML-Series Card into an 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 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. Your own steps will vary according to your network design.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Add an ML-Series Card into an 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 RPR traffic to bridge the RPR. Step 14 If the new node is not already an active node in the SONET ring topology, add the node to the ring.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Delete an ML-Series Card from an 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 14 Configuring Resilient Packet Ring on the ML-Series Card Delete an ML-Series Card from an RPR Figure 14-9 Three-Node 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 14-10 145994 POS 1 Two-Node RPR After the Deletion Adjacent Node 1 POS 0 POS 1 SPR 1 POS 1 POS 0 This STS circuit was created after the deletion.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Delete an ML-Series Card from an RPR Caution • Test Ethernet connectivity between the access ports on the existing adjacent ML-Series cards with a test set to ensure that the RPR wrapped successfully. • Delete the two STS circuits that will be replaced by the new circuits. (In Figure 14-9, this is the circuit between the Delete Node and one Adjacent Node, and the circuit between the Delete Node and the other Adjacent Node.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Delete an ML-Series Card from an RPR The card view appears. Step 7 Click the Circuits tab. Step 8 Click the Circuits subtab. Step 9 Identify the appropriate STS circuit by looking under the source column and destination column for the circuit entry that matches the POS ports at the endpoints of the first circuit to be deleted. The circuit entry is in node-name/card-slot/port-number format, such as Node-1/s12(ML100T)/pPOS-0.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Cisco Proprietary RPR KeepAlive Step 26 Complete the following Cisco IOS configuration for the ML-Series card in Adjacent Node 1, 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 first newly created circuit. b. Router(config-if)# no shutdown Enables the port.
Chapter 14 Configuring Resilient Packet Ring on the ML-Series Card Redundant Interconnect Monitoring and Verifying Shortest Path andTopolgy Discovery Please seeCisco ONS 15454 Ether Guide Chapter 17 Redundant Interconnect Redundant Interconnect is only supported on 454 platforms Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
CH A P T E R 15 Configuring Security for the ML-Series Card This chapter describes the security features of the ML-Series card and includes the following major sections: • Understanding Security, page 15-1 • Disabling the Console Port on the ML-Series Card, page 15-2 • Secure Login on the ML-Series Card, page 15-2 • Secure Shell on the ML-Series Card, page 15-2 • RADIUS on the ML-Series Card, page 15-6 • RADIUS Relay Mode, page 15-6 • RADIUS Stand Alone Mode, page 15-7 Understanding Security
Chapter 15 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 15 Configuring Security for the ML-Series Card Secure Shell on the ML-Series Card 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.
Chapter 15 Configuring Security for the ML-Series Card Secure Shell on the ML-Series Card 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 15 Configuring Security for the ML-Series Card Secure Shell on the ML-Series Card 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 15 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.
Chapter 15 Configuring Security for the ML-Series Card RADIUS Stand Alone 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode Configuring a nas-ip-address in the RADIUS Packet The ML-Series card in RADIUS relay mode allows the user to configure a separate nas-ip-address for each ML-Series card. In RADIUS standalone mode, this command is hidden in the Cisco IOS CLI. This allows the RADIUS server to distinguish among individual ML-Series card in the same ONS node.
Chapter 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode This example shows how to apply an output ACL in ASCII format to an interface for the duration of this connection: 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 15 Configuring Security for the ML-Series Card RADIUS Stand Alone Mode Beginning in privileged EXEC mode, follow these steps to specify a vendor-proprietary RADIUS server host and a shared secret text string: Command Purpose Step 1 Router# configure terminal Enter global configuration mode.
CH A P T E R 16 Configuring Bridging on the ML-Series Card This chapter describes how to configure bridging for the ML-Series card. Bridging is one of the simplest configurations of the ML-Series card. Other alternatives exist to simple bridging, such as Integrated Routing and Bridging (IRB). The user should consult the chapter detailing their desired type of configuration.
Chapter 16 Configuring Bridging on the ML-Series Card Configuring Bridging If the destination address of the packet is known in the bridge table, the packet is forwarded on a single interface in the bridge group. If the packet’s destination is unknown in the bridge table, the packet is flooded on all forwarding interfaces in the bridge group. The bridge places source addresses in the bridge table as it learns them during the process of bridging.
Chapter 16 Configuring Bridging on the ML-Series Card Monitoring and Verifying Bridging Figure 16-1 Bridging Example ML_Series_B ML_Series_A pos 0 pos 0 SONET/SDH fast ethernet 0 124411 fast ethernet 0 Example 16-1 ML_Series A Configuration bridge irb bridge 1 protocol ieee ! ! interface FastEthernet0 no ip address bridge-group 1 ! interface POS0 no ip address bridge-group 1 Example 16-2 ML_Series B Configuration bridge irb bridge 1 protocol ieee ! ! interface FastEthernet0 no ip address bridge-gro
Chapter 16 Configuring Bridging on the ML-Series Card Monitoring and Verifying Bridging Command Purpose Step 3 ML_Series# show bridge verbose Displays detailed information about configured bridge groups. Step 4 ML_Series# show spanning-tree [bridge-group-number][brief] Displays detailed information about spanning tree. • bridge-group-number restricts the spanning tree information to specific bridge groups. • brief displays summary information about spanning tree.
CH A P T E R 17 CE-100T-8 Ethernet Operation This chapter describes the operation of the CE-100T-8 (Carrier Ethernet) card supported on the Cisco ONS 15310-CL and ONS 15310-MA (15310-CE-100T-8). A CE-100T-8 card is also supported on the ONS 15454 (15454-CE-100T-8). Provisioning is done through Cisco Transport Controller (CTC) or Transaction Language One (TL1). Cisco IOS is not supported on the CE-100T-8 card. For Ethernet card specifications, refer to the Cisco ONS 15454 Reference Manual.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 Ethernet Features The CE-100T-8 offers full TL1-based provisioning capability. Refer to the Cisco ONS SONET TL1 Command Guide for CE-100T-8 TL1 provisioning commands. CE-100T-8 Ethernet Features The CE-100T-8 card has eight front-end Ethernet ports which use standard RJ-45 connectors for 10BASE-T Ethernet/100BASE-TX Ethernet media. Ethernet Ports 1 through 8 each map to a POS port with a corresponding number.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 Ethernet Features The pause frame instructs the source to stop sending packets for a specific period of time. The sending station waits the requested amount of time before sending more data. Figure 17-2 illustrates pause frames being sent and received by CE-100T-8 cards and attached switches.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 Ethernet Features Enhanced State Model for Ethernet and SONET Ports The CE-100T-8 supports the Enhanced State Model (ESM) for the Ethernet ports, as well as for the SONET circuit. For more information about the ESM, refer to the “Administrative and Service States” appendix in the Cisco ONS 15454 Reference Manual. The Ethernet ports can be set to the ESM service states including the In-Service, Automatic In-Service (IS,AINS) administrative state.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 Ethernet Features For an IP ToS-tagged packet, the CE-100T-8 can map any of the 256 priorities specified in IP ToS to priority or best effort. The user can configure a different ToS on CTC at the card-level view under the Provisioning > Ether Ports tabs. Any ToS class higher than the class specified in CTC is mapped to the priority queue, which is the queue geared towards low latency. By default, the ToS is set to 255, which is the highest ToS value.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features If the CE-100T-8 card’s ToS setting is 255 (default) and the CoS setting is 7 (default), priority queueing is not active on the card, and data gets sent to the default normal traffic queue. Also if data is not tagged with a ToS value or a CoS value before it enters the CE-100T-8 card, it gets sent to the default normal traffic queue. Note Priority queuing has no effect when flow control is enabled (default) on the CE-100T-8.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features Table 17-3 CE-100T-8 Supported Circuit Sizes CCAT High Order VCAT High Order VCAT Low Order STS-1 STS-1-1v VT1.5-nV (n= 1 to 64) STS-3c STS-1-2v STS-1-3v A single circuit provides a maximum of 100 Mbps of throughput, even when an STS-3c circuit, which has a bandwidth equivalent of 155 Mbps, is provisioned. This is due to the hardware restriction of the Fast Ethernet port.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features A user can combine CCAT high order, VCAT high order, and VCAT low order circuits in any way as long as there is a maximum of eight circuits and the mapper chip bandwidth restrictions are observed. The following table details the maximum density service combinations. Table 17-7 CE-100T-8 Maximum Service Densities Service Combination STS-3c or STS-1-3v STS-1-2v STS-1 VT1.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features CE-100T-8 STS/VT Allocation Tab 124894 Figure 17-4 Port 5 belongs to Pool 2 For example if a user needs to provision an STS-3c or STS-1-3v on the CE-100T-8 card shown in Figure 17-4, an STS-3c or STS-1-3v worth of bandwidth is not available from either of the two pools. The user needs to delete circuits from the same pool to free up bandwidth.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features The ONS 15454 SONET/SDH ML-Series card has a software-based LCAS (SW-LCAS) scheme. This scheme is also supported by both the ML-100T-8 card and both versions of the CE-100T-8, but only for circuits with the other end terminating on an ONS 15454 SONET/SDH ML-Series card. The CE-100T-8 card allows independent routing and protection preferences for each member of a VCAT circuit.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features Figure 17-5 ONS CE-100T-8 Encapsulation and Framing Options GFP-F Frame Types Address Control Protocol Core Header Payload FCS HDLC Framing Mode or Transport Overhead Payload Header Payload FCS GFP-F Framing Mode SONET/SDH Payload Envelope 115444 Flag GFP-Mapped Ethernet (LEX) Encapsulation LEX SONET/SDH Frame The CE-100T-8 card supports GFP-F null mode. GFP-F CMFs are counted and discarded.
Chapter 17 CE-100T-8 Ethernet Operation CE-100T-8 SONET Circuits and Features Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
A P P E N D I X A Command Reference for the ML-Series Card 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 for the ML-Series Card [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 for the ML-Series Card clear counters clear counters Use the clear counters command to simultaneously clear Ethernet interface performance monitoring (PM) counters in Cisco Transport Controller (CTC), Transaction Language One (TL1), and the Cisco IOS CLI. Using Cisco IOS, you can clear counters on a per-interface basis for any except the 802.13 IEEE RPR interface; in that instance, you can only clear all counters for both spans.
Appendix A Command Reference for the ML-Series Card [no] clock auto [no] clock auto Use the clock auto command to determine whether the system clock parameters are configured automatically from the node’s timing. When enabled, both daylight savings time and time zone are automatically configured, and the system clock is periodically synchronized to the node’s timing. Use the no form of the command to disable this feature. Syntax Description This command has no arguments or keywords.
Appendix A Command Reference for the ML-Series Card 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). If the interface has already been created, this command enters spr interface configuration mode. The only valid spr interface number is 1. Defaults N/A Command Modes Global configuration Usage Guidelines The command allows the user to create a virtual interface for the RPR/SPR.
Appendix A Command Reference for the ML-Series Card [no] pos mode gfp [fcs-disabled] [no] pos mode gfp [fcs-disabled] Sets the framing mode employed by the ONS Ethernet card for framing and encapsulating data packets onto the SONET transport layer. Valid framing modes are: • HDLC—(High-level data link control) A common mechanism employed in framing data packets for SONET/SDH. • GFP (default)—The ML-Series card supports the frame mapped version of generic framing procedure (GFP-F).
Appendix A Command Reference for the ML-Series Card [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 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 1000 Defaults The default value is 100 milliseconds.
Appendix A Command Reference for the ML-Series Card [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 for the ML-Series Card [non] pos trigger defects condition [non] pos trigger defects condition Use this command to specify which conditions cause the associated POS link state to change. These conditions are soaked/cleared using the delay specified in the pos trigger delay command. 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 for the ML-Series Card [no] pos trigger delay time [no] pos trigger delay time Use this command to specify which conditions cause the associated POS link state to change. The conditions specified in the pos trigger defects command are soaked/cleared using this delay. Use the no form of the command to use the default value. Syntax Description Parameter Description time delay time in milliseconds, 200 to 2000 Defaults The default value is 200 milliseconds.
Appendix A Command Reference for the ML-Series Card [no] pos vcat defect {immediate | delayed} [no] pos vcat defect {immediate | delayed} Sets the virtual concatenated (VCAT) defect processing mode to either handle a defect state change the instant it is detected or wait for the time specified by pos trigger delay. Use the no form of the command to use the default value. Syntax Description Parameter Description immediate Handles a defect state change the instant it is detected.
Appendix A Command Reference for the ML-Series Card show controller pos interface-number [details] show controller pos interface-number [details] Use this command to display the status of the POS controller. Use the details argument to obtain certain additional information.
Appendix A Command Reference for the ML-Series Card show controller pos interface-number [details] 1913918056382 input good octets (POS MAC tx) 2397888202 total output packets, 1913918056382 pre-encap bytes Carrier delay is 200 msec Related Commands show interface pos clear counters Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
Appendix A Command Reference for the ML-Series Card show interface pos interface-number show interface pos interface-number Use this command to display the status of the POS interface. Syntax Description Parameter Description interface-number Number of the POS interface (0–1) Defaults N/A Command Modes Privileged EXEC Usage Guidelines This command can be used to help diagnose and isolate POS or SONET problems.
Appendix A Command Reference for the ML-Series Card show ons alarm show ons alarm Use this command to display all the active alarms on the card. Syntax Description This command has no arguments or keywords. Defaults N/A Command Modes Privileged EXEC Usage Guidelines This command can be used to help diagnose and isolate card problems.
Appendix A Command Reference for the ML-Series Card show ons alarm Related Commands show controller pos show ons alarm defects show ons alarm failures Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
Appendix A Command Reference for the ML-Series Card show ons alarm defect {[eqpt | port [port-number] | sts [sts-number] | vcg [vcg-number] | vt]} show ons alarm defect {[eqpt | port [port-number] | sts [sts-number] | vcg [vcg-number] | vt]} This command displays all defects for the ML-Series card with no keyword (default) or defects for the level specified by the keyword. Syntax Description Parameter Description eqpt Specifies hardware-related. port Specifies the physical interface level.
Appendix A Command Reference for the ML-Series Card show ons alarm defect {[eqpt | port [port-number] | sts [sts-number] | vcg [vcg-number] | vt]} Port Defects POS0 Active: None Reportable to POS1 Active: None Reportable to FastEthernet0 Active: None Reportable to FastEthernet1 Active: None Reportable to FastEthernet2 Active: None Reportable to FastEthernet3 Active: None Reportable to FastEthernet4 Active: None Reportable to FastEthernet5 Active: None Reportable to FastEthernet6 Active: None Reportable t
Appendix A Command Reference for the ML-Series Card show ons alarm failure {[eqpt | port [port-number] | sts [sts-number] | vcg [vcg-number] | vt]} show ons alarm failure {[eqpt | port [port-number] | sts [sts-number] | vcg [vcg-number] | vt]} This command displays all failures for the ML-Series card with no keyword (default) or failures for the level specified by the keyword. Syntax Description Parameter Description eqpt Specifies hardware-related. port Specifies the physical interface level.
Appendix A Command Reference for the ML-Series Card show ons alarm failure {[eqpt | port [port-number] | sts [sts-number] | vcg [vcg-number] | vt]} The following example shows the command and output for the ML-Series alarm failure information at the STS level.
Appendix A Command Reference for the ML-Series Card spr-intf-id shared-packet-ring-number spr-intf-id shared-packet-ring-number Assigns 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 Examples • The SPR number must be 1, which is the same SPR number assigned to the SPR interface.
Appendix A Command Reference for the ML-Series Card [no] spr load-balance { auto | port-based } [no] spr load-balance { auto | port-based } Specifies the 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 the source and destination addresses of the IP packet.
Appendix A Command Reference for the ML-Series Card spr station-id station-id-number spr station-id station-id-number Configures 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 RPR. Valid station ID numbers range from 1 to 254.
Appendix A Command Reference for the ML-Series Card spr wrap { immediate | delayed } spr wrap { immediate | delayed } Sets the 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 RPR traffic the instant it detects a link state change.
A P P E N D I X B Unsupported CLI Commands for the ML-Series Card This appendix lists some of the command-line interface (CLI) commands that are not supported in this release, either because they were 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 for the ML-Series Card Unsupported Global Configuration Commands bridge cmf bridge bitswap-layer3-addresses bridge circuit-group 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
Appendix B Unsupported CLI Commands for the ML-Series Card Unsupported POS Interface Configuration Commands netbios partition policy-map class queue-limit priority-list 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 subscriber-policy Unsupported POS Interface Configuration Commands access-expression autodetect bridge-group x circuit-group bridge-group x input-* bridge-
Appendix B Unsupported CLI Commands for the ML-Series Card Unsupported FastEthernet Interface Configuration Commands ip load-sharing per-packet ip route-cache ip security ip tcp ip verify iso-igrp loopback multilink-group netbios pos flag c2 pos scramble-spe pos vcat resequence priority-group pulse-time random-detect rate-limit rmon scramble serial service-policy history source timeout transmit-interface tx-ring-limit Unsupported FastEthernet Interface Configuration Commands access-expression clns custo
Appendix B Unsupported CLI Commands for the ML-Series Card Unsupported Port-Channel Interface Configuration Commands ip verify iso-igrp keepalive loopback max-reserved-bandwidth multilink-group netbios priority-group random-detect 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 h
Appendix B Unsupported CLI Commands for the ML-Series Card Unsupported BVI Interface Configuration Commands rate-limit random-detect timeout tx-ring-limit 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 Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and
A P P E N D I X C Using Technical Support This appendix describes how to resolve problems with your ML-Series card and contains the following sections: • Gathering Information About Your Internetwork, page C-1 • Getting the Data from Your ML-Series Card, page C-2 • Providing Data to Your Technical Support Representative, page C-3 To help resolve these problems, use the “Gathering Information About Your Internetwork” section on page C-1 as a guideline for gathering relevant information about your net
Appendix C Using Technical Support Getting the Data from Your ML-Series Card 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. This command provides general information about the switch router that you can provide to your technical support representative when you are reporting a problem.
Appendix C Using Technical Support Providing Data to Your Technical Support Representative Note To get your system to automatically log specific error messages or operational information to a UNIX syslog server, enter the logging internet-address command. For more information about using the logging command and setting up a syslog server, refer to the Cisco IOS configuration guides and command references.
Appendix C Using Technical Support Providing Data to Your Technical Support Representative Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
I N D EX POS ports to the SPR interface Numerics 14-11 attaching traffic policies to an interface 802.1D. See STP audit trail 802.1Q. See IEEE 802.1Q authentication, RADUS.
Index bridging SONET circuits and features configuring statistics 16-2 to 16-3 examples 17-6 STS/VT allocation tab 16-3 feature list 1-2 monitoring 16-3 to 16-4 17-8 VCAT characteristics overview 16-1 verifying 16-3 to 16-4 17-6 17-9 channel-group command 9-3, 9-5 Cisco IOS accessing through Telnet BVIs backing out one level 3-2 to 3-3 3-11 configuring 10-3 Cisco IP SLA, ML-Series cards description 10-1 Cisco IP SLA, ML-Series restrictions displaying information about rout
Index bandwidth show ons alarm 11-13 bridge-group bridge irb 4-4, 4-5, 16-2 10-3 bridge priority bridge protocol drpri-rstp clear bridge 16-3 A-22 A-23 A-24 global 10-3 A-11 3-10 interface 9-1 line A-5 3-10 3-10 configuring 3-7 ACL size in TCAM 3-11 12-3 match-any 11-11 bridge group forwarding-delay time match cos 11-11 bridge group maximum-aging time match ip dscp bridging 11-11 match ip precedence pos mode gfp BVIs 11-11 pos trigger defects 14-7 to 14-9 EtherChann
Index management port console port 3-6 ML-100T-8 card security multicast QoS 11-24 POS channel 9-4 to 9-6 connecting to 15-1 to 15-20 disabling 3-4 15-2 CoS POS interface encapsulation 5-5 ML-Series CoS-based QoS example POS interface framing mode 5-4 packet statistics.
Index default multicast QoS enable command mode 11-23 defining AAA RADIUS server groups enabling 15-13 differentiated services code point.
Index Fast Ethernet configuring VLAN encapsulation configuring autonegotiation configuring interfaces CoS and IP ToS queuing 4-4 example 4-4 monitoring operations on FEC, configuring encapsulation over 8-12 tunneling, overview 9-6 to 9-8 framing 17-4 8-5 monitoring tunneling 4-6 to 4-8 7-2 8-1 tunneling and compatibility with other features See also framing mode integrated routing and bridging.
Index Media Access Control addresses.
Index RPR 1-5 SNMP N 1-5 soft reset network element default 3-2 SONET alarms 5-6 startup configuration file supported circuit sizes TL1 17-2 3-5 O 5-2 opening a Cisco IOS session 1-6 tunneling 8-1 unsupported commands B-1 to B-6 P ML-Series card. See ML-100T-8 card modifying ACL TCAM size 13-5 packet statistics. See CoS-based packet statistics modular QoS CLI.
Index monitoring marking and discarding packets 5-8 to 5-9 SONET alarms verifying ML-Series flow 5-6, 5-8 monitoring 5-8 to 5-9 pos mode gfp fcs 11-4 11-16 to 11-17 multicast. See multicast QoS A-6 pos pdi holdoff command pos report command multicast priority queueing A-7 on RPR 5-7, A-8 pos trigger defects command pos trigger delay command pos vcat defect command 11-23 11-9 overview A-9 11-2 policing.
Index Rapid Spanning Tree Protocol. See RSTP BPDU format redundant STP connectivity BPDU processing 6-8 remote terminals, logging router output configuring C-2 removing an ML-Series card from an RPR 6-13 6-14 6-9 to 6-20 default configuration 14-21 to 14-26 resetting 6-16 designated port, defined 6-10 CE-100T-8 card 17-1 designated switch, defined ML-100T-8 card 1-1, 3-2 disabling resilient packet ring.
Index configuring for ML-100T-8 card overview 15-1 to 15-20 SONET circuits CE-100T-8 card 15-1 selective autonegotiation in RPR 17-2 service-policy command, traffic policies service-policy input command 11-15 SONET ports, Enhanced State Model assigning bridge group for RPR and customer VLANs assigning POS 8-2 and IEEE 802.
Index disabling 6-16 displaying status enabling 6-20 to 6-22 connecting to switch 3-4 logging router output C-2 terminal-emulation software 6-17 extended system ID 6-4 TL1 on the ML-100T-8 card forward-delay time 6-6 traffic class forwarding state bandwidth command 6-7 interface states creating 6-5 to 6-7 interoperability with RSTP 6-15 Layer 2 protocol tunneling 8-9 learning state listening state 6-8 11-18 11-15 7-1 defined 6-8 8-1 8-1 Layer 2 protocol 6-8 8-9 tunnel po
Index QoS configuration RPR 14-16 SDM 12-3 11-16 to 11-17 STP and RSTP status tunneling status VLANs 6-20 to 6-22 8-12 7-5 virtual LANs. See VLANs VLANs aging dynamic addresses and QoS 11-4 and RPR 14-6 6-9 configuring as Layer 2 tunnel configuring IEEE 802.1Q 8-12 7-2, 7-3 to 7-5 customer numbering in service-provider networks 8-3 monitoring operation number per system overview 7-5 7-1 7-1 STP and IEEE 802.
Index Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.
