Cisco Systems Network Card Cisco ONS 15310 MA User Manual
Cisco ONS 15310-CL,  
Cisco ONS 15310-MA, and  
Cisco ONS 15310-MA SDH Ethernet Card  
Software Feature and Configuration Guide  
Cisco IOS Release 12.2(29)SVE0, 12.2(33)STE0  
CTC and Documentation Release 9.1 and Release 9.2  
August 2012  
Americas Headquarters  
Cisco Systems, Inc.  
170 West Tasman Drive  
San Jose, CA 95134-1706  
USA  
http://www.cisco.com  
Tel: 408 526-4000  
800 553-NETS (6387)  
Fax: 408 527-0883  
Text Part Number: 78-19415-01  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C O N T E N T S  
Preface xvii  
Revision History xvii  
Document Objectives xviii  
Audience xviii  
Related Documentation xviii  
Document Conventions xix  
Obtaining Optical Networking Information xxv  
Where to Find Safety and Warning Information xxv  
Cisco Optical Networking Product Documentation CD-ROM xxv  
Obtaining Documentation and Submitting a Service Request xxv  
CHAPTER  
1
Overview of the ML-Series Card 1-1  
ML-Series Card Description 1-1  
ML-Series Feature List 1-2  
Key ML-Series Features 1-4  
Cisco IOS 1-4  
GFP-F Framing 1-4  
Link Aggregation (FEC and POS) 1-5  
RMON 1-5  
RPR 1-5  
SNMP 1-5  
TL1 1-6  
CHAPTER  
2
CTC Operations on the ML-Series Card 2-1  
Displaying ML-Series POS Statistics in CTC 2-1  
Displaying ML-Series Ethernet Statistics in CTC 2-2  
Displaying ML-Series Ethernet Ports Provisioning Information on CTC 2-2  
Displaying ML-Series POS Ports Provisioning Information on CTC 2-3  
Displaying SONET Alarms 2-4  
Displaying J1 Path Trace 2-4  
Provisioning SONET Circuits 2-4  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
iii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
CHAPTER  
3
Initial Configuration of the ML-Series Card 3-1  
Hardware Installation 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 3-6  
Passwords 3-6  
Configuring the Management Port 3-6  
Configuring the Hostname 3-7  
Loading a Cisco IOS Startup Configuration File Through CTC 3-8  
Database Restore of the Startup Configuration File 3-9  
Cisco IOS Command Modes 3-9  
Using the Command Modes 3-11  
Exit 3-11  
Getting Help 3-11  
CHAPTER  
4
5
Configuring Bridging on the ML-Series Card 4-1  
Understanding Bridging 4-1  
Configuring Bridging 4-2  
Monitoring and Verifying Bridging 4-3  
CHAPTER  
Configuring Interfaces on the ML-Series Card 5-1  
General Interface Guidelines 5-1  
MAC Addresses 5-1  
Interface Port ID 5-2  
Basic Interface Configuration 5-3  
Basic Fast Ethernet and POS Interface Configuration 5-4  
Configuring the Fast Ethernet Interfaces 5-4  
Configuring the POS Interfaces 5-5  
Monitoring Operations on the Fast Ethernet Interfaces 5-6  
CHAPTER  
6
Configuring POS on the ML-Series Card 6-1  
Understanding POS on the ML-Series Card 6-1  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
iv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Available Circuit Sizes and Combinations 6-1  
LCAS Support 6-2  
J1 Path Trace, and SONET Alarms 6-2  
Framing Mode, Encapsulation, Scrambling, MTU and CRC Support 6-3  
Configuring the POS Interface 6-4  
Configuring POS Interface Framing Mode 6-4  
Configuring POS Interface Encapsulation Type Under GFP-F Framing 6-5  
SONET Alarms 6-6  
Configuring SONET Alarms 6-7  
Configuring SONET Delay Triggers 6-7  
Monitoring and Verifying POS 6-8  
CHAPTER  
7
Configuring STP and RSTP on the ML-Series Card 7-1  
STP Features 7-1  
STP Overview 7-2  
Supported STP Instances 7-2  
Bridge Protocol Data Units 7-2  
Election of the Root Switch 7-3  
Bridge ID, Switch Priority, and Extended System ID 7-4  
Spanning-Tree Timers 7-4  
Creating the Spanning-Tree Topology 7-5  
Spanning-Tree Interface States 7-5  
Blocking State 7-6  
Listening State 7-7  
Learning State 7-7  
Forwarding State 7-7  
Disabled State 7-7  
Spanning-Tree Address Management 7-8  
STP and IEEE 802.1Q Trunks 7-8  
Spanning Tree and Redundant Connectivity 7-8  
Accelerated Aging to Retain Connectivity 7-9  
RSTP Features 7-9  
Supported RSTP Instances 7-9  
Port Roles and the Active Topology 7-10  
Rapid Convergence 7-11  
Synchronization of Port Roles 7-12  
Bridge Protocol Data Unit Format and Processing 7-13  
Processing Superior BPDU Information 7-14  
Processing Inferior BPDU Information 7-14  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
v
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Topology Changes 7-14  
Interoperability with IEEE 802.1D STP 7-15  
Configuring STP and RSTP Features 7-15  
Default STP and RSTP Configuration 7-16  
Disabling STP and RSTP 7-16  
Configuring the Root Switch 7-17  
Configuring the Port Priority 7-17  
Configuring the Path Cost 7-18  
Configuring the Switch Priority of a Bridge Group 7-18  
Configuring the Hello Time 7-19  
Configuring the Forwarding-Delay Time for a Bridge Group 7-20  
Configuring the Maximum-Aging Time for a Bridge Group 7-20  
Verifying and Monitoring STP and RSTP Status 7-20  
CHAPTER  
8
Configuring VLANs on the ML-Series Card 8-1  
Understanding VLANs 8-1  
Configuring IEEE 802.1Q VLAN Encapsulation 8-2  
IEEE 802.1Q VLAN Configuration 8-3  
Monitoring and Verifying VLAN Operation 8-5  
CHAPTER  
9
Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card 9-1  
Understanding IEEE 802.1Q Tunneling 9-1  
Configuring IEEE 802.1Q Tunneling 9-4  
IEEE 802.1Q Tunneling and Compatibility with Other Features 9-4  
Configuring an IEEE 802.1Q Tunneling Port 9-4  
IEEE 802.1Q Example 9-5  
Understanding VLAN-Transparent and VLAN-Specific Services 9-6  
VLAN-Transparent and VLAN-Specific Services Configuration Example 9-7  
Understanding Layer 2 Protocol Tunneling 9-9  
Configuring Layer 2 Protocol Tunneling 9-9  
Default Layer 2 Protocol Tunneling Configuration 9-10  
Layer 2 Protocol Tunneling Configuration Guidelines 9-10  
Configuring Layer 2 Tunneling on a Port 9-11  
Configuring Layer 2 Tunneling Per-VLAN 9-12  
Monitoring and Verifying Tunneling Status 9-12  
CHAPTER 10  
Configuring Link Aggregation on the ML-Series Card 10-1  
Understanding Link Aggregation 10-1  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
vi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Configuring Link Aggregation 10-2  
Configuring Fast EtherChannel 10-2  
EtherChannel Configuration Example 10-3  
Configuring POS Channel 10-4  
POS Channel Configuration Example 10-5  
Understanding Encapsulation over FEC or POS Channel 10-6  
Configuring Encapsulation over EtherChannel or POS Channel 10-6  
Encapsulation over EtherChannel Example 10-7  
Monitoring and Verifying EtherChannel and POS 10-8  
CHAPTER 11  
Configuring IRB on the ML-Series Card 11-1  
Understanding Integrated Routing and Bridging 11-1  
Configuring IRB 11-2  
IRB Configuration Example 11-3  
Monitoring and Verifying IRB 11-4  
CHAPTER 12  
Configuring Quality of Service on the ML-Series Card 12-1  
Understanding QoS 12-2  
Priority Mechanism in IP and Ethernet 12-2  
IP Precedence and Differentiated Services Code Point 12-2  
Ethernet CoS 12-3  
ML-Series QoS 12-4  
Classification 12-4  
Policing 12-5  
Marking and Discarding with a Policer 12-5  
Queuing 12-6  
Scheduling 12-6  
Control Packets and L2 Tunneled Protocols 12-7  
Egress Priority Marking 12-8  
Ingress Priority Marking 12-8  
QinQ Implementation 12-8  
Flow Control Pause and QoS 12-9  
QoS on RPR 12-9  
Configuring QoS 12-10  
Creating a Traffic Class 12-10  
Creating a Traffic Policy 12-11  
Attaching a Traffic Policy to an Interface 12-15  
Configuring CoS-Based QoS 12-16  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
vii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Monitoring and Verifying QoS Configuration 12-16  
QoS Configuration Examples 12-17  
Traffic Classes Defined Example 12-18  
Traffic Policy Created Example 12-18  
class-map match-any and class-map match-all Commands Example 12-19  
match spr1 Interface Example 12-19  
ML-Series VoIP Example 12-20  
ML-Series Policing Example 12-20  
ML-Series CoS-Based QoS Example 12-21  
Understanding Multicast QoS and Multicast Priority Queuing 12-23  
Default Multicast QoS 12-23  
Multicast Priority Queuing QoS Restrictions 12-24  
Configuring Multicast Priority Queuing QoS 12-24  
QoS not Configured on Egress 12-26  
ML-Series Egress Bandwidth Example 12-26  
Case 1: QoS with Priority and Bandwidth Configured Without Priority Multicast 12-26  
Case 2: QoS with Priority and Bandwidth Configured with Priority Multicast 12-27  
Understanding CoS-Based Packet Statistics 12-28  
Configuring CoS-Based Packet Statistics 12-29  
Understanding IP SLA 12-30  
IP SLA on the ML-Series 12-31  
IP SLA Restrictions on the ML-Series 12-31  
CHAPTER 13  
Configuring the Switching Database Manager on the ML-Series Card 13-1  
Understanding the SDM 13-1  
Understanding SDM Regions 13-2  
Configuring SDM 13-2  
Configuring SDM Regions 13-3  
Configuring Access Control List Size in TCAM 13-3  
Monitoring and Verifying SDM 13-3  
CHAPTER 14  
Configuring Access Control Lists on the ML-Series Card 14-1  
Understanding ACLs 14-1  
ML-Series ACL Support 14-1  
IP ACLs 14-2  
Named IP ACLs 14-2  
User Guidelines 14-2  
Creating IP ACLs 14-3  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
viii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Creating Numbered Standard and Extended IP ACLs 14-3  
Creating Named Standard IP ACLs 14-4  
Creating Named Extended IP ACLs (Control Plane Only) 14-4  
Applying the ACL to an Interface 14-4  
Modifying ACL TCAM Size 14-5  
CHAPTER 15  
Configuring Resilient Packet Ring on the ML-Series Card 15-1  
Understanding RPR 15-1  
Role of SONET Circuits 15-2  
Packet Handling Operations 15-2  
Ring Wrapping 15-3  
RPR Framing Process 15-4  
MAC Address and VLAN Support 15-6  
RPR QoS 15-6  
CTM and RPR 15-6  
Configuring RPR 15-6  
Connecting the ML-Series Cards with Point-to-Point STS Circuits 15-7  
Configuring CTC Circuits for RPR 15-7  
CTC Circuit Configuration Example for RPR 15-7  
Configuring RPR Characteristics and the SPR Interface on the ML-Series Card 15-9  
Assigning the ML-Series Card POS Ports to the SPR Interface 15-11  
Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces 15-13  
RPR Cisco IOS Configuration Example 15-14  
Verifying Ethernet Connectivity Between RPR Ethernet Access Ports 15-15  
CRC Threshold Configuration and Detection 15-15  
Monitoring and Verifying RPR 15-16  
Add an ML-Series Card into an RPR 15-17  
Adding an ML-Series Card into an RPR 15-19  
Delete an ML-Series Card from an RPR 15-21  
Deleting an ML-Series Card from an RPR 15-23  
Cisco Proprietary RPR KeepAlive 15-25  
Configuring Cisco Proprietary RPR KeepAlive 15-25  
Monitoring Cisco Propretary RPR KeepAlive 15-25  
Cisco Proprietary RPR Shortest Path 15-25  
Configuring Shortest Path and Topology Discovery 15-25  
Monitoring and Verifying Shortest Path and Topolgy Discovery 15-25  
Redundant Interconnect 15-25  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
ix  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
CHAPTER 16  
Configuring Security for the ML-Series Card 16-1  
Understanding Security 16-1  
Disabling the Console Port on the ML-Series Card 16-2  
Secure Login on the ML-Series Card 16-2  
Secure Shell on the ML-Series Card 16-2  
Understanding SSH 16-2  
Configuring SSH 16-3  
Configuration Guidelines 16-3  
Setting Up the ML-Series Card to Run SSH 16-3  
Configuring the SSH Server 16-5  
Displaying the SSH Configuration and Status 16-5  
RADIUS on the ML-Series Card 16-6  
RADIUS Relay Mode 16-6  
Configuring RADIUS Relay Mode 16-7  
RADIUS Stand Alone Mode 16-7  
Understanding RADIUS 16-8  
Configuring RADIUS 16-8  
Default RADIUS Configuration 16-9  
Identifying the RADIUS Server Host 16-9  
Configuring AAA Login Authentication 16-11  
Defining AAA Server Groups 16-13  
Configuring RADIUS Authorization for User Privileged Access and Network Services 16-15  
Starting RADIUS Accounting 16-16  
Configuring a nas-ip-address in the RADIUS Packet 16-17  
Configuring Settings for All RADIUS Servers 16-17  
Configuring the ML-Series Card to Use Vendor-Specific RADIUS Attributes 16-18  
Configuring the ML-Series Card for Vendor-Proprietary RADIUS Server Communication 16-19  
Displaying the RADIUS Configuration 16-20  
CHAPTER 17  
CE-Series Ethernet Cards 17-1  
CE-100T-8 Ethernet Card 17-1  
CE-100T-8 Overview 17-2  
CE-100T-8 Ethernet Features 17-2  
Autonegotiation, Flow Control, and Frame Buffering 17-2  
Ethernet Link Integrity Support 17-3  
Enhanced State Model for Ethernet and SONET Ports 17-4  
IEEE 802.1Q CoS and IP ToS Queuing 17-5  
RMON and SNMP Support 17-6  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
x
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Statistics and Counters 17-6  
CE-100T-8 SONET Circuits and Features 17-7  
Available Circuit Sizes and Combinations 17-7  
CE-100T-8 STS/VT Allocation Tab 17-8  
CE-100T-8 VCAT Characteristics 17-10  
CE-100T-8 POS Encapsulation, Framing, and CRC 17-10  
CE-100T-8 Loopback, J1 Path Trace, and SONET Alarms 17-11  
CE-MR-6 Ethernet Card 17-12  
CE-MR-6 Overview 17-12  
CE-MR-6 Ethernet Features 17-13  
Autonegotiation, Flow Control, and Frame Buffering 17-13  
Ethernet Link Integrity Support 17-14  
Ethernet Drop and Continue Circuit 17-15  
Administrative and Service States with Soak Time for Ethernet and SONET Ports 17-16  
IEEE 802.1Q CoS and IP ToS Queuing 17-17  
RMON and SNMP Support 17-19  
Statistics and Counters 17-20  
Supported Cross-connects 17-20  
CE-MR-6 Circuits and Features 17-20  
Available Circuit Sizes and Combinations 17-20  
CE-MR-6 Pool Allocation 17-23  
CE-MR-6 VCAT Characteristics 17-23  
CE-MR-6 POS Encapsulation, Framing, and CRC 17-24  
CE-MR-6 Loopback, J1 Path Trace, and SONET Alarms 17-24  
APPENDIX  
APPENDIX  
A
B
Command Reference for the ML-Series Card A-1  
Unsupported CLI Commands for the ML-Series Card B-1  
Unsupported Privileged Exec Commands B-1  
Unsupported Global Configuration Commands B-1  
Unsupported POS Interface Configuration Commands B-3  
Unsupported FastEthernet Interface Configuration Commands B-4  
Unsupported Port-Channel Interface Configuration Commands B-5  
Unsupported BVI Interface Configuration Commands B-6  
APPENDIX  
C
Using Technical Support C-1  
Gathering Information About Your Internetwork C-1  
Getting the Data from Your ML-Series Card C-2  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Contents  
Providing Data to Your Technical Support Representative C-3  
INDEX  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
T A B L E S  
Table 2-1  
Table 2-2  
Table 3-1  
Table 3-2  
Table 6-1  
Table 6-2  
Table 7-1  
Table 7-2  
Table 7-3  
Table 7-4  
Table 7-5  
Table 7-6  
Table 9-1  
Table 9-2  
Table 9-3  
Table 11-1  
Table 11-2  
Table 12-1  
Table 12-2  
Table 12-3  
Table 12-4  
Table 12-5  
Table 12-6  
Table 12-7  
Table 12-8  
Table 13-1  
Table 13-2  
Table 14-1  
Table 14-2  
Table 15-1  
ML-Series POS Statistics Fields and Buttons 2-1  
ML-Series Ethernet Statistics Fields and Buttons 2-2  
RJ-11 to RJ-45 Pin Mapping 3-4  
Cisco IOS Command Modes 3-10  
ML-Series Card Supported Circuit Sizes and Sizes Required for Ethernet Wire Speeds 6-2  
ML-Series Card Encapsulation, Framing, and CRC Sizes 6-3  
Switch Priority Value and Extended System ID 7-4  
Spanning-Tree Timers 7-4  
Port State Comparison 7-10  
RSTP BPDU Flags 7-13  
Default STP and RSTP Configuration 7-16  
Commands for Displaying Spanning-Tree Status 7-21  
VLAN-Transparent Service Versus VLAN-Specific Services 9-6  
Default Layer 2 Protocol Tunneling Configuration 9-10  
Commands for Monitoring and Maintaining Tunneling 9-12  
Commands for Monitoring and Verifying IRB 11-5  
show interfaces irb Field Descriptions 11-6  
Traffic Class Commands 12-11  
Traffic Policy Commands 12-12  
CoS Commit Command 12-16  
Commands for QoS Status 12-16  
CoS Multicast Priority Queuing Command 12-25  
Packet Statistics on ML-Series Card Interfaces 12-28  
CoS-Based Packet Statistics Command 12-29  
Commands for CoS-Based Packet Statistics 12-29  
Default Partitioning by Application Region 13-2  
Partitioning the TCAM Size for ACLs 13-3  
Commands for Numbered Standard and Extended IP ACLs 14-3  
Applying ACL to Interface 14-5  
Definitions of RPR Frame Fields 15-5  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xiii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Tables  
Table 16-1  
Table 17-1  
Table 17-2  
Table 17-3  
Table 17-4  
Table 17-5  
Table 17-6  
Table 17-7  
Table 17-8  
Table 17-9  
Table 17-10  
Table 17-11  
Table 17-12  
Commands for Displaying the SSH Server Configuration and Status 16-5  
IP ToS Priority Queue Mappings 17-5  
CoS Priority Queue Mappings 17-5  
CE-100T-8 Supported Circuit Sizes 17-7  
SONET Circuit Size Required for Ethernet Wire Speeds 17-7  
CCAT High Order Circuit Size Combinations 17-7  
VCAT High Order Circuit Size Combinations 17-8  
CE-100T-8 Maximum Service Densities 17-8  
IP ToS Priority Queue Mappings 17-18  
CoS Priority Queue Mappings 17-18  
Supported SONET Circuit Sizes of CE-MR-6 on ONS 15310 17-21  
Minimum SONET Circuit Sizes for Ethernet Speeds 17-21  
VCAT High-Order Circuit Combinations for STS on ONS 15310 (Slots 1, 2, 5, and 6) 17-22  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xiv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
F I G U R E S  
Figure 3-1  
Figure 3-2  
Figure 4-1  
Figure 7-1  
Figure 7-2  
Figure 7-3  
Figure 7-4  
Figure 7-5  
Figure 8-1  
Figure 8-2  
Figure 9-1  
Figure 9-2  
Figure 9-3  
Figure 10-1  
Figure 10-2  
Figure 10-3  
Figure 11-1  
Figure 12-1  
Figure 12-2  
Figure 12-3  
Figure 12-4  
Figure 12-5  
Figure 12-6  
Figure 12-7  
Figure 12-8  
Figure 12-9  
Figure 12-10  
Figure 15-1  
Figure 15-2  
Figure 15-3  
CTC Node View Showing IP Address 3-3  
Console Cable Adapter 3-4  
Bridging Example 4-3  
Spanning-Tree Topology 7-5  
Spanning-Tree Interface States 7-6  
Spanning Tree and Redundant Connectivity 7-8  
Proposal and Agreement Handshaking for Rapid Convergence 7-12  
Sequence of Events During Rapid Convergence 7-13  
VLANs Spanning Devices in a Network 8-2  
Bridging IEEE 802.1Q VLANs 8-4  
IEEE 802.1Q Tunnel Ports in a Service-Provider Network 9-2  
Normal, IEEE 802.1Q, and IEEE 802.1Q-Tunneled Ethernet Packet Formats 9-3  
ERMS Example 9-7  
Encapsulation over EtherChannel Example 10-3  
POS Channel Example 10-5  
Encapsulation over EtherChannel Example 10-7  
Configuring IRB 11-3  
IP Precedence and DSCP 12-3  
Ethernet Frame and the CoS Bit (IEEE 802.1p) 12-3  
ML-Series QoS Flow 12-4  
Dual Leaky Bucket Policer Model 12-5  
Queuing and Scheduling Model 12-7  
QinQ Implementation on the ML-Series Card 12-9  
ML-Series VoIP Example 12-20  
ML-Series Policing Example 12-21  
ML-Series CoS Example 12-22  
QoS not Configured on Egress 12-26  
RPR Packet Handling Operations 15-3  
RPR Ring Wrapping 15-4  
RPR Frame for ML-Series Card 15-5  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Figures  
Figure 15-4  
Figure 15-5  
Figure 15-6  
Figure 15-7  
Figure 15-8  
Figure 15-9  
Figure 15-10  
Figure 17-1  
Figure 17-2  
Figure 17-3  
Figure 17-4  
Figure 17-5  
Figure 17-6  
Figure 17-7  
Figure 17-8  
Figure 17-9  
Figure 17-10  
RPR Frame Fields 15-5  
Three-Node RPR Example 15-8  
RPR Bridge Group 15-13  
Two-Node RPR Before the Addition 15-17  
Three-Node RPR After the Addition 15-18  
Three-Node RPR Before the Deletion 15-21  
Two-Node RPR After the Deletion 15-22  
CE-100T-8 Point-to-Point Circuit 17-2  
Flow Control 17-3  
End-to-End Ethernet Link Integrity Support 17-4  
CE-100T-8 STS/VT Allocation Tab 17-9  
ONS CE-100T-8 Encapsulation and Framing Options 17-11  
CE-MR-6 Point-to-Point Circuit 17-12  
Flow Control 17-14  
End-to-End Ethernet Link Integrity Support 17-15  
Unidirectional Drop from a CE-MR-6 card on Node 1 to Nodes 2, 3, and 4 17-15  
Unidirectional Drop from CE-MR-6 Card A to CE-MR-6 Card B 17-16  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xvi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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. Cisco does not  
recommend using its path protection feature in any particular topological network configuration.  
This section provides the following information:  
•
•
•
•
•
•
•
Revision History  
Document Objectives  
Audience  
Related Documentation  
Document Conventions  
Obtaining Optical Networking Information  
Obtaining Documentation and Submitting a Service Request  
Revision History  
Date  
Notes  
May 2010  
•
•
Added this Revision History table.  
Updated the link integrity soak duration range as 200 ms to 10000 ms in the  
sub-section “Ethernet Link Integrity Support” of the section “CE-MR-6  
Ethernet Features” in the chapter “CE-Series Ethernet Cards”.  
October 2010  
Updated the “CE-MR-6 VCAT Characteristics” section in the “CE-Series Ethernet  
Cards” chapter.  
December 2010 Updated the “CE-MR-6 VCAT Characteristics” section in the “CE-Series Ethernet  
Cards” chapter.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xvii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Preface  
Date  
Notes  
January 2011  
•
•
•
Updated the “CE-100T-8 VCAT Characteristics” section in the “CE-Series  
Ethernet Cards” chapter.  
Updated the “CE-MR-6 VCAT Characteristics” section in the “CE-Series  
Ethernet Cards” chapter.  
August 2011  
Updated the following tables in the chapter “CE-Series Ethernet Cards”:  
–
–
–
Supported SONET Circuit Sizes of CE-MR-6 on ONS 15310  
Minimum SONET Circuit Sizes for Ethernet Speeds  
VCAT High-Order Circuit Combinations for STS on ONS 15310 (Slots 1,  
2, 5, and 6)  
•
Updated the section “CE-MR-6 Pool Allocation” in the chapter “CE-Series  
Ethernet Cards”.  
August 2012  
The full length book-PDF was generated.  
Document Objectives  
This guide covers the software features and operations of the ML-100T-8 and the CE-100T-8 Ethernet  
cards for the Cisco ONS 15310-CL and the Cisco ONS 15310-MA. It explains software features and  
configuration for Cisco IOS on the ML-Series card. It also explains software feature and configuration  
for Cisco Transport Controller (CTC) on the CE-100T-8 card. The CE-100T-8 card is also available as  
a card for the Cisco ONS 15454 and Cisco ONS 15454 SDH. This version of the card is described in the  
Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration  
Guide. Use this guide in conjunction with the appropriate publications listed in the Related  
Documentation section.  
Audience  
To use the ML-Series card chapters of this publication, you should be familiar with Cisco IOS and  
preferably have technical networking background and experience. To use the CE-100T-8 card chapter of  
this publication, you should be familiar with CTC and preferably have technical networking background  
and experience.  
Related Documentation  
Use the Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software  
Feature and Configuration Guide, R9.1 and R9.2 in conjunction with the following general  
ONS 15310-CL and ONS 15310-MA system publications:  
•
•
To install, turn up, provision, and maintain a Cisco ONS 15310-CL or Cisco ONS 15310-MA node  
and network, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide and  
Cisco ONS 15310-MA SDH Procedure Guide.  
For alarm clearing, general troubleshooting procedures, transient conditions, and error messages for  
a Cisco ONS 15310-CL and Cisco ONS 15310-MA card, node, or network, refer to the  
Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide and Cisco ONS 15310-MA  
SDH Troubleshooting Guide.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xviii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
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 and Cisco ONS 15310-MA SDH 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.2  
The ML-Series card employs Cisco IOS 12.2. For more general information on Cisco IOS 12.2, refer  
to the extensive Cisco IOS documentation at http://www.cisco.com.  
For an update on End-of-Life and End-of-Sale notices, refer to  
http://www.cisco.com/en/US/products/hw/optical/ps2001/prod_eol_notices_list.html.  
Document Conventions  
This publication uses the following conventions:  
Convention  
boldface  
italic  
Application  
Commands and keywords in body text.  
Command input that is supplied by the user.  
Keywords or arguments that appear within square brackets are optional.  
[
]
{ x | x | x }  
Ctrl  
A choice of keywords (represented by x) appears in braces separated by  
vertical bars. The user must select one.  
The control key. For example, where Ctrl + D is written, hold down the  
Control key while pressing the D key.  
screen font  
Examples of information displayed on the screen.  
boldface screen font  
Examples of information that the user must enter.  
<
>
Command parameters that must be replaced by module-specific codes.  
Note  
Means reader take note. Notes contain helpful suggestions or references to material not covered in the  
document.  
Caution  
Means reader be careful. In this situation, the user might do something that could result in equipment  
damage or loss of data.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xix  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
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. Statement 1071  
SAVE THESE INSTRUCTIONS  
Waarschuwing  
BELANGRIJKE VEILIGHEIDSINSTRUCTIES  
Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan  
veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij  
elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van de standaard  
praktijken om ongelukken te voorkomen. Gebruik het nummer van de verklaring onderaan de  
waarschuwing als u een vertaling van de waarschuwing die bij het apparaat wordt geleverd, wilt  
raadplegen.  
BEWAAR DEZE INSTRUCTIES  
Varoitus  
TÄRKEITÄ TURVALLISUUSOHJEITA  
Tämä varoitusmerkki merkitsee vaaraa. Tilanne voi aiheuttaa ruumiillisia vammoja. Ennen kuin  
käsittelet laitteistoa, huomioi sähköpiirien käsittelemiseen liittyvät riskit ja tutustu  
onnettomuuksien yleisiin ehkäisytapoihin. Turvallisuusvaroitusten käännökset löytyvät laitteen  
mukana toimitettujen käännettyjen turvallisuusvaroitusten joukosta varoitusten lopussa näkyvien  
lausuntonumeroiden avulla.  
SÄILYTÄ NÄMÄ OHJEET  
Attention  
IMPORTANTES INFORMATIONS DE SÉCURITÉ  
Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant  
entraîner des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez  
conscient des dangers liés aux circuits électriques et familiarisez-vous avec les procédures  
couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions des  
avertissements figurant dans les consignes de sécurité traduites qui accompagnent cet appareil,  
référez-vous au numéro de l'instruction situé à la fin de chaque avertissement.  
CONSERVEZ CES INFORMATIONS  
WICHTIGE SICHERHEITSHINWEISE  
Warnung  
Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu Verletzungen führen  
kann. Machen Sie sich vor der Arbeit mit Geräten mit den Gefahren elektrischer Schaltungen und  
den üblichen Verfahren zur Vorbeugung vor Unfällen vertraut. Suchen Sie mit der am Ende jeder  
Warnung angegebenen Anweisungsnummer nach der jeweiligen Übersetzung in den übersetzten  
Sicherheitshinweisen, die zusammen mit diesem Gerät ausgeliefert wurden.  
BEWAHREN SIE DIESE HINWEISE GUT AUF.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xx  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Preface  
Avvertenza  
Advarsel  
Aviso  
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.  
CONSERVARE QUESTE ISTRUZIONI  
VIKTIGE SIKKERHETSINSTRUKSJONER  
Dette advarselssymbolet betyr fare. Du er i en situasjon som kan føre til skade på person. Før du  
begynner å arbeide med noe av utstyret, må du være oppmerksom på farene forbundet med  
elektriske kretser, og kjenne til standardprosedyrer for å forhindre ulykker. Bruk nummeret i slutten  
av hver advarsel for å finne oversettelsen i de oversatte sikkerhetsadvarslene som fulgte med denne  
enheten.  
TA VARE PÅ DISSE INSTRUKSJONENE  
INSTRUÇÕES IMPORTANTES DE SEGURANÇA  
Este símbolo de aviso significa perigo. Você está em uma situação que poderá ser causadora de  
lesões corporais. Antes de iniciar a utilização de qualquer equipamento, tenha conhecimento dos  
perigos envolvidos no manuseio de circuitos elétricos e familiarize-se com as práticas habituais de  
prevenção de acidentes. Utilize o número da instrução fornecido ao final de cada aviso para  
localizar sua tradução nos avisos de segurança traduzidos que acompanham este dispositivo.  
GUARDE ESTAS INSTRUÇÕES  
¡Advertencia!  
INSTRUCCIONES IMPORTANTES DE SEGURIDAD  
Este símbolo de aviso indica peligro. Existe riesgo para su integridad física. Antes de manipular  
cualquier equipo, considere los riesgos de la corriente eléctrica y familiarícese con los  
procedimientos estándar de prevención de accidentes. Al final de cada advertencia encontrará el  
número que le ayudará a encontrar el texto traducido en el apartado de traducciones que acompaña  
a este dispositivo.  
GUARDE ESTAS INSTRUCCIONES  
VIKTIGA SÄKERHETSANVISNINGAR  
Varning!  
Denna varningssignal signalerar fara. Du befinner dig i en situation som kan leda till personskada.  
Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och  
känna till vanliga förfaranden för att förebygga olyckor. Använd det nummer som finns i slutet av  
varje varning för att hitta dess översättning i de översatta säkerhetsvarningar som medföljer denna  
anordning.  
SPARA DESSA ANVISNINGAR  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xxi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xxii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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.  
GUARDE ESTAS INSTRUÇÕES  
Advarsel  
VIGTIGE SIKKERHEDSANVISNINGER  
Dette advarselssymbol betyder fare. Du befinder dig i en situation med risiko for  
legemesbeskadigelse. Før du begynder arbejde på udstyr, skal du være opmærksom på de  
involverede risici, der er ved elektriske kredsløb, og du skal sætte dig ind i standardprocedurer til  
undgåelse af ulykker. Brug erklæringsnummeret efter hver advarsel for at finde oversættelsen i de  
oversatte advarsler, der fulgte med denne enhed.  
GEM DISSE ANVISNINGER  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xxiii  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Preface  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xxiv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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 and Submitting a Service Request 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. This publication describes the  
international agency compliance and safety information for the Cisco ONS 15454 system. It also  
includes translations of the safety warnings that appear in the ONS 15454 system documentation.  
Cisco Optical Networking Product Documentation CD-ROM  
Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is  
available in a CD-ROM package that ships with your product. The Optical Networking Product  
Documentation CD-ROM is updated periodically and may be more current than printed documentation.  
Obtaining Documentation and Submitting a Service Request  
For information on obtaining documentation, submitting a service request, and gathering additional  
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and  
revised Cisco technical documentation, at:  
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html  
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed  
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free  
service and Cisco currently supports RSS version 2.0.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xxv  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Preface  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
xxvi  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
1
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 and CE-MR-6 card  
the Cisco ONS 15310-MA is covered in Chapter 17, “CE-Series Ethernet Cards.” For Ethernet card  
specifications, refer to the Cisco ONS 15454 Reference Manual. For step-by-step Ethernet card circuit  
configuration, hard-reset, and soft-reset procedures, refer to the Cisco ONS 15454 Procedure Guide.  
Refer to the Cisco ONS SONET TL1 Command Guide for TL1 provisioning commands. For specific  
details on ONS 15310-CL Ethernet card interoperability with other ONS platforms, refer to the “POS on  
ONS Ethernet Cards” chapter of the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card  
Software Feature and Configuration Guide.  
This chapter contains the following major sections:  
•
•
•
ML-Series Card Description, page 1-1  
ML-Series Feature List, page 1-2  
Key ML-Series Features, page 1-4  
ML-Series Card Description  
The ML-Series card is a module in the Cisco ONS 15310-CL and the Cisco ONS 15310-MA. It is an  
independent Fast Ethernet switch with eight RJ-45 interfaces. The ML-Series card uses Cisco IOS  
Release 12.2(28)SV, and the Cisco IOS command-line interface (CLI) is the primary user interface for  
the ML-Series card. Most configuration for the card, such as Ethernet and packet-over-SONET (POS)  
port provisioning, bridging, VLAN, and Quality of Service (QoS), can be done only with the Cisco IOS  
CLI.  
However, CTC—the ONS 15310-CL graphical user interface (GUI)—and Transaction Language One  
(TL1) also support the ML-Series card. SONET circuits must be configured through CTC or TL1 and  
cannot be provisioned through Cisco IOS. CTC also offers ML-Series card status information, SONET  
alarm management, Cisco IOS Telnet session initialization, provisioning, inventory, and other standard  
functions.  
The ML-Series card features two virtual ports, which function in a manner similar to OC-N card ports.  
The SONET circuits are provisioned through CTC in the same manner as standard OC-N circuits.  
For detailed card specifications, refer to the Cisco ONS 15454 Reference Manual.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
1-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
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.3x compliant flow control  
SONET features:  
–
–
•
–
High-level data link control (HDLC) or frame-mapped generic framing procedure (GFP-F)  
framing mechanisms for POS  
–
GFP-F supports LEX (default), Cisco HDLC, and Point-to-Point Protocol/Bridging Control  
Protocol (PPP/BCP) encapsulation for POS  
–
–
–
HDLC framing supports LEX encapsulation only  
Two POS virtual ports  
Virtual concatenated (VCAT) circuits with Link Capacity Adjustment Scheme (LCAS) or  
without LCAS  
–
ONS 15310 ML-Series LCAS is compatible with ONS 15454 ML-Series SW-LCAS  
•
Layer 2 bridging features:  
–
–
–
–
–
–
–
–
–
–
Transparent bridging  
MAC address learning, aging, and switching by hardware  
Protocol tunneling  
Multiple Spanning Tree (MST) protocol tunneling  
255 active bridge group maximum  
8,000 MAC address maximum per card  
Integrated routing and bridging (IRB)  
IEEE 802.1P/Q-based VLAN trunking  
IEEE 802.1Q VLAN tunneling  
IEEE 802.1D Spanning Tree Protocol (STP) and IEEE 802.1W Rapid Spanning Tree Protocol  
(RSTP)  
–
–
–
IEEE 802.1D STP instance per bridge group  
Resilient packet ring (RPR)  
VLAN-transparent and VLAN-specific services (Ethernet Relay Multipoint Service [ERMS])  
•
Fast EtherChannel (FEC) features:  
–
–
–
–
–
–
Bundling of up to four Fast Ethernet ports  
Load sharing based on source and destination IP addresses of unicast packets  
Load sharing for bridge traffic based on MAC addresses  
IRB  
IEEE 802.1Q trunking  
Up to 4 active FEC port channels  
•
POS channel:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
1-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 1 Overview of the ML-Series Card  
ML-Series Feature List  
–
–
–
–
Bundling the two POS ports  
LEX encapsulation only  
IRB  
IEEE 802.1Q trunking  
•
Layer 3 static routing:  
–
–
–
–
–
–
–
Default routes  
IP unicast and multicast forwarding  
Reverse Path Forwarding (RPF) multicast (not RPF unicast)  
Load balancing among equal cost paths based on source and destination IP addresses  
Up to 350 IP routes per card  
Up to 350 IP hosts per card  
IRB routing mode support  
•
QoS features:  
–
–
–
–
–
–
Multicast priority queuing classes  
Service level agreements (SLAs) with 1-Mbps granularity  
Input policing  
Guaranteed bandwidth (weighted round-robin [WDRR] plus strict priority scheduling)  
Low latency queuing support for unicast voice over IP (VoIP)  
Class of service (CoS) based on Layer 2 priority, VLAN ID, Layer 3 Type of Service/DiffServ  
Code Point (TOS/DSCP), and port  
–
–
–
–
CoS-based packet statistics  
Up to 350 QoS entries per card  
Up to 350 policers per card  
IP SLA network monitoring using Cisco IP SLA (formerly Cisco Service Assurance Agent)  
•
Security features  
–
–
–
–
Cisco IOS login enhancements  
Secure Shell connection (SSH Version 2)  
Disabled console port  
Authentication, Authorization, and Accounting/Remote Authentication Dial-In User Service  
(AAA/RADIUS) stand alone mode  
–
AAA/RADIUS relay mode  
•
•
Additional protocols:  
–
–
–
Cisco Discovery Protocol (CDP) support on Ethernet ports  
Dynamic Host Configuration Protocol (DHCP) relay  
Hot Standby Router Protocol (HSRP) over 10/100 Ethernet, FEC and Bridge Group Virtual  
Interface (BVI)  
–
Internet Control Message Protocol (ICMP)  
Management features:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
1-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 1 Overview of the ML-Series Card  
Key ML-Series Features  
–
–
–
–
–
Cisco IOS Release 12.2(28)SV  
CTC  
Remote monitoring (RMON)  
Simple Network Management Protocol (SNMP)  
TL1  
•
•
System features:  
–
Network Equipment Building Systems 3 (NEBS3) compliant  
CTC features:  
–
Standard synchronous transport signal (STS) and VCAT circuit provisioning for POS virtual  
ports  
–
–
–
–
–
–
SONET alarm reporting for path alarms and other ML-Series card specific alarms  
Raw port statistics  
Standard inventory and card management functions  
J1 path trace  
Cisco IOS CLI Telnet sessions from CTC  
Cisco IOS startup configuration file management from CTC  
Key ML-Series Features  
This section describes selected key features and their implementation on the ML-Series cards.  
Cisco IOS  
Cisco IOS controls the data functions of the ML-Series cards. Users cannot update the ML-Series  
Cisco IOS image in the same manner as the Cisco IOS system image on a Cisco Catalyst Series. An  
ML-Series Cisco IOS image upgrade is available only as part of the Cisco ONS 15310-CL or the Cisco  
ONS 15310-MA software release and accomplished only through CTC or TL1. The image is not  
available for download or shipped separately.  
GFP-F Framing  
GFP defines a standard-based mapping of different types of services onto SONET/SDH. The ML-Series  
and CE-Series support frame-mapped GFP (GFP-F), which is the protocol data unit (PDU)-oriented  
client signal adaptation mode for GFP. GFP-F maps one variable length data packet onto one GFP  
packet.  
GFP is composed of common functions and payload specific functions. Common functions are those  
shared by all payloads. Payload-specific functions are different depending on the payload type. GFP is  
detailed in the ITU recommendation G.7041.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
1-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
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.  
Traffic flows map to individual ports based on MAC source address (SA)/destination address (DA) for  
bridged packets and IP SA/DA for routed packets. There is no support for policing or class-based packet  
priorities when link aggregation is configured.  
RMON  
The ML-Series card features RMON that allows network operators to monitor the health of the network  
with an NMS. ONG RMON is recommended for the ML-100T-8. The ONG RMON contains the  
statistics, history, alarms, and events MIB groups from the standard RMON MIB. The standard  
Cisco IOS RMON is also available. A user can access RMON threshold provisioning through TL1 or  
CTC. For more information on RMON, refer to the “SNMP Remote Monitoring” section in “SNMP”  
chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.  
RPR  
RPR is an emerging network architecture designed for metro fiber ring networks. This new MAC  
protocol is designed to overcome the limitations of STP, RSTP, and SONET in packet-based networks.  
RPR convergence times are comparable to SONET and much faster than STP or RSTP. RPR operates at  
the Layer 2 level and is compatible with Ethernet and protected or unprotected SONET circuits.  
SNMP  
The Cisco ONS 15310-CL, the Cisco ONS 15310-MA, and the ML-Series cards have SNMP agents and  
support SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c) sets and traps. The Cisco ONS  
15310-CL and the Cisco ONS 15310-MA accept, validate, and forward get/getNext/set requests to the  
ML-Series through a proxy agent. Responses from the ML-Series are relayed by the Cisco ONS  
15310-CL and the Cisco ONS 15310-MA to the requesting SNMP agents.  
The ML-Series card SNMP support includes:  
•
•
•
STP traps from Bridge-MIB (RFC 1493)  
Authentication traps from RFC 1157  
Export of QoS statistics through the CISCO-PORT-QOS-MIB extension  
For more information on how the ONS 15310-CL implements SNMP, refer to the “SNMP” chapter of  
the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual. For more information on  
specific MIBs, refer to the Cisco SNMP Object Navigator at http://www.cisco.com.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
1-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
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.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
1-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
C H 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. For the  
ML-Series cards, CTC manages SONET alarms and provisions STS circuits in the same manner as other  
Cisco ONS 15310-CL and Cisco ONS 15310-MA SONET traffic.  
Use CTC to load a Cisco IOS configuration file or to open a Cisco IOS command-line interface (CLI)  
session. See Chapter 3, “Initial Configuration of the ML-Series Card.”  
This chapter contains the following major sections:  
•
•
•
•
•
•
•
Displaying ML-Series POS Statistics in CTC, page 2-1  
Displaying ML-Series Ethernet Statistics in CTC, page 2-2  
Displaying ML-Series Ethernet Ports Provisioning Information on CTC, page 2-2  
Displaying ML-Series POS Ports Provisioning Information on CTC, page 2-3  
Displaying SONET Alarms, page 2-4  
Displaying J1 Path Trace, page 2-4  
Provisioning SONET Circuits, page 2-4  
Displaying ML-Series POS Statistics in CTC  
The POS statistics window lists POS port-level statistics. Display the CTC card view for the ML-Series  
card and click the Performance > POS Ports tabs to display the window.  
Table 2-1 describes the buttons in the POS Ports window.  
Table 2-1  
ML-Series POS Statistics Fields and Buttons  
Button  
Refresh  
Description  
Manually refreshes the statistics.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
2-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
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  
Description  
Button  
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.  
These new baselined counters are shown only as long as the user displays the  
Performance window. If the user navigates to another CTC window and comes back  
to the Performance window, the true actual statistics retained by the card are shown.  
Auto-Refresh  
Sets a time interval for the automatic refresh of statistics.  
Refer to the Cisco ONS 15454 Troubleshooting Guide for definitions of the SONET POS parameters.  
CTC displays a different set of parameters for high-level data link control (HDLC) and frame-mapped  
generic framing procedure (GFP-F) framing modes.  
Displaying ML-Series Ethernet Statistics in CTC  
The Ethernet statistics window lists Ethernet port-level statistics. It is similar in appearance to the POS  
statistics window with different statistic parameters. The ML-Series Ethernet ports are zero based.  
Display the CTC card view for the ML-Series card and click the Performance > Ether Ports tabs to  
display the window. Table 2-2 describes the buttons in the EtherPorts window.  
Table 2-2  
ML-Series Ethernet Statistics Fields and Buttons  
Button  
Refresh  
Baseline  
Description  
Queries the current values from the card and updates the CTC display.  
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.  
These new baselined counters appear as long as the user displays the Performance  
window. If the user navigates to another CTC window and comes back to the  
Performance window, the true actual statistics retained by the card are shown.  
Auto-Refresh  
Sets a time interval for the automatic refresh of statistics.  
Refer to the Cisco ONS 15454 Troubleshooting Guide for definitions of the Ethernet parameters. CTC  
displays a different set of parameters for HDLC and GFP-F framing modes.  
Displaying ML-Series Ethernet Ports Provisioning Information  
on CTC  
The Ethernet port provisioning window displays the provisioning status of the Ethernet ports. Click the  
Provisioning > Ether Ports tabs to display this window. For ML-Series cards, the user must configure  
ML-Series Ethernet ports and POS ports using the Cisco IOS CLI.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
2-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
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. The port name field configured in CTC and the port  
name configured in Cisco IOS are independent of each other, and will not match unless the same name  
is used to configure the port name in both CTC and Cisco IOS.  
The Provisioning > Ether Ports tab displays the following information:  
•
•
•
Port #—The fixed number identifier for the specific port.  
Port Name—Configurable 12-character alphanumeric identifier for the port.  
Admin State—Configured port state, which is administratively active or inactive. Possible values are  
UP and DOWN.  
•
•
PSAS—A check indicates alarm suppression is set on the port for the time designated in the Soak  
Time column.  
Soak Time—Desired soak time in hours and minutes. Use this column when you have checked PSAS  
to suppress alarms. Once the port detects a signal, the countdown begins for the designated soak  
time. Soak time hours can be set from 0 to 48. Soak time minutes can be set from 0 to 45 in 15 minute  
increments.  
•
Link State—Status between signaling points at port and attached device. Possible values are UP and  
DOWN.  
•
•
•
Operating Speed—ML-100T-8 possible values are Auto, 10Mbps, or 100Mbps.  
Operating Duplex—Setting of the port. ML-100T-8 possible values are Auto, Full, or Half.  
Flow Control—Negotiated flow control mode. ML-100T-8 possible values are None or  
Symmetrical.  
Note  
Auto indicates the port is set to autonegotiate capabilities with the attached link partner.  
Displaying ML-Series POS Ports Provisioning Information on  
CTC  
The POS ports provisioning window displays the provisioning status of the card’s POS ports. Click the  
Provisioning > POS Ports tabs to display this window. For ML-Series cards, the user must configure  
ML-Series Ethernet ports and POS ports using the Cisco IOS CLI.  
The following fields can be provisioned using CTC: Port Name, PSAS, and Soak Time. Click in 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. The port name field configured in CTC and the port  
name configured in Cisco IOS are independent of each other and will not match unless the same name  
is used to configure the port name in both CTC and Cisco IOS.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
2-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
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.  
•
•
PSAS—A check indicates alarm suppression is set on the port for the time designated in the Soak  
Time column.  
Soak Time—Desired soak time in hours and minutes. Use this column when you have checked PSAS  
to suppress alarms. Once the port detects a signal, the countdown begins for the designated soak  
time. Soak time hours can be set from 0 to 48. Soak time minutes can be set from 0 to 45 in 15 minute  
increments.  
•
MTU—The maximum transfer unit, which is the largest acceptable packet size for that port. This  
value cannot be configured on the Cisco ONS 15310-CL and the Cisco ONS 15310-MA ML-Series  
card.  
•
•
Link State—Status between signaling points at the port and an attached device. Possible values are  
UP and DOWN.  
Framing Type- HDLC or frame-mapped generic framing procedure (GFP-F) framing type shows the  
POS framing mechanism being employed on the port  
Displaying SONET Alarms  
To view SONET alarms on the ML-Series card, click the Alarms tab.  
CTC manages the ML-Series card SONET alarm behavior in the same manner as it manages alarm  
behavior for other Cisco ONS 15310-CL and the Cisco ONS 15310-MA SONET traffic. Click the  
Provisioning > Alarm Profiles tabs for the Ethernet and POS port alarm profile information. Refer to  
the Cisco ONS 15454 Troubleshooting Guide for detailed information.  
Displaying J1 Path Trace  
The J1 Path Trace is a repeated, fixed-length string comprised of 64 consecutive J1 bytes. You can use  
the string to monitor interruptions or changes to SONET circuit traffic. Click the Maintenance >  
Path Trace tabs for the J1 Path Trace information.  
For information on J1 Path Trace, refer to the Cisco ONS 15454 Troubleshooting Guide.  
Provisioning SONET Circuits  
CTC provisions and edits STS level circuits for the two POS ports of the ML-Series card in the same  
manner as it provisions other Cisco ONS 15310-CL and Cisco ONS 15310-MA SONET OC-N cards.  
The ONS 15310-CL ML-Series card supports both contiguous concatenation (CCAT) and virtual  
concatenation (VCAT) circuits. Refer to the “Create Circuits” chapter of the Cisco ONS 15454  
Procedure Guide to create SONET STS circuits.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
2-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
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, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
2-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 2 CTC Operations on the ML-Series Card  
Provisioning SONET Circuits  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
2-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H 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. Because the  
ONS 15310 card slots can be preprovisioned for an ML-Series line card, the following physical  
operations can be performed before or after the provisioning of the slot has taken place.  
1. Install the ML-Series card into the ONS 15310. For physical installation instructions, refer to the  
Cisco ONS 15454 Troubleshooting Guide.  
2. Connect the Ethernet cables to the ML-Series card.  
3. Connect the console terminal to the ML-Series card (optional).  
Note  
A NO-CONFIG condition is reported in CTC under the Alarms pane when an ML-Series card is inserted  
and no valid Cisco IOS startup configuration file exists. Loading or creating this file clears the condition.  
See the “Startup Configuration File” section on page 3-5 for information on loading or creating the file.  
Cisco IOS on the ML-Series Card  
The Cisco IOS software image used by the ML-Series card is not permanently stored on the ML-Series  
card but in the flash memory of the 15310-CL-CTX or CTX2500 card. During a hard reset, the Cisco IOS  
software image is downloaded from the flash memory of the 15310-CL-CTX or CTX2500 to the memory  
cache of the ML-Series card. The cached image is then decompressed and initialized for use by the  
ML-Series card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
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. Caching the Cisco IOS image provides  
a significant time savings when a soft reset is performed.  
To use CTC to reset the ML-Series card with a hard reset or soft reset, at the CTC card-level view or  
node-level view, right-click on the ML-Series card and click Hard-reset Card or Soft-reset Card. A  
hard reset also requires that the ML-Series card is in the out of service (OOS) state, which is set under  
the Inventory tab. Then click Yes at the confirmation dialog that appears. You can also initiate a hard  
reset by removing and reinserting the ML-Series card. You can initiate a soft reset through Cisco IOS  
with the privileged EXEC reboot command. For TL1 commands, refer to the Cisco ONS SONET TL1  
Command Guide.  
Caution  
A soft reset or a hard reset on the Cisco ONS 15310 ML-Series card is service-affecting.  
There are four ways to access the ML-Series card Cisco IOS configuration. The two out-of-band options  
are opening a Cisco IOS session on CTC and telnetting to the node IP Address and 2001. The  
two-in-band signalling options are telnetting to a configured management interface and directly  
connecting to the console port.  
Opening a Cisco IOS Session Using CTC  
Users can initiate a Cisco IOS CLI session for the ML-Series card using CTC. Click the IOS tab at the  
card-level CTC view, then click the Open IOS Command Line Interface (CLI) button. A window  
opens and a standard Cisco IOS CLI User EXEC command mode prompt appears.  
Note  
A Cisco IOS startup configuration file must be loaded and the ML-Series card must be installed and  
initialized prior to opening a Cisco IOS CLI session on CTC. See the “Startup Configuration File”  
section on page 3-5 for more information.  
Telnetting to the Node IP Address and Slot Number  
Users can telnet to the Cisco IOS CLI using the IP address and the port number (2000 plus the slot  
number).  
Note  
Note  
A Cisco IOS startup configuration file must be loaded and the ML-Series card must be installed and  
initialized prior to telnetting to the ML-Series card. See the “Startup Configuration File” section on  
page 3-5 for more information.  
If the ONS 15310 node is set up as a proxy server, where one ONS 15310 node in the ring acts as a  
gateway network element (GNE) for the other nodes in the ring, telnetting over the GNE firewall to the  
IP address and slot number of a non-GNE or end network element (ENE) requires the user’s Telnet client  
to be SOCKS v5 aware (RFC 1928). Configure the Telnet client to recognize the GNE as the SOCKS v5  
proxy for the Telnet session and to recognize the ENE as the host.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
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  
Node IP address  
Step 2  
Step 3  
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.124 on the ONS 15310-CL in the example, you would enter or telnet 10.92.18.124  
2001. The slot number is always 1 for the ONS 15310-CL.  
If you are telnetting into an ONS 15310-MA with an ML-Series card, use the IP address and the port  
number (2000 plus the slot number) as the Telnet address in your preferred communication program. For  
example, with an IP address of 10.92.18.125 on an ONS 15310-CL with an ML-Series card in slot 5, you  
would enter or telnet to 10.92.18.125 2005.  
Telnetting to a Management Port  
Users can access the ML-Series through a standard Cisco IOS management port in the same manner as  
other Cisco IOS platforms. For further details about configuring ports and lines for management access,  
refer to the Cisco IOS Configuration Fundamentals Configuration Guide.  
As a security measure, the vty lines used for Telnet access are not fully configured. In order to gain  
Telnet access to the ML-Series card, you must configure the vty lines via the serial console connection  
or preload a startup-configuration file that configures the vty lines. A port on the ML-Series must first  
be configured as the management port; see the “Configuring the Management Port” section on page 3-6  
or the “Loading a Cisco IOS Startup Configuration File Through CTC” section on page 3-8.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
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.  
RJ-11 to RJ-45 Console Cable Adapter  
Due to space limitations on the ML-Series card faceplate, the console port is an RJ-11 modular jack  
instead of the more common RJ-45 modular jack. Cisco supplies an RJ-11 to RJ-45 console cable adapter  
with each ML-Series card. After connecting the adapter, the console port functions like the standard  
Cisco RJ-45 console port. Figure 3-2 shows the RJ-11 to RJ-45 console cable adapter.  
Figure 3-2  
Console Cable Adapter  
Table 3-1 shows the mapping of the RJ-11 pins to the RJ-45 pins.  
Table 3-1 RJ-11 to RJ-45 Pin Mapping  
RJ-11 Pin RJ-45 Pin  
1
1
2
3
4
5
6
7
8
2
3
4
None  
5
None  
6
Connecting a PC or Terminal to the Console Port  
Use the supplied cable, an RJ-11 to RJ-45 console cable adapter, and a DB-9 adapter to connect a PC to  
the ML-Series console port.  
The PC must support VT100 terminal emulation. The terminal-emulation software—frequently a PC  
application such as HyperTerminal or Procomm Plus—makes communication between the ML-Series  
and your PC or terminal possible during the setup program.  
Step 1  
Configure the data rate and character format of the PC or terminal to match these console port default  
settings:  
•
9600 baud  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 3 Initial Configuration of the ML-Series Card  
Startup Configuration File  
•
•
•
8 data bits  
1 stop bit  
No parity  
Step 2  
Step 3  
Insert the RJ-45 connector of the supplied cable into the female end of the supplied console cable  
adapter.  
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.  
Step 4  
Step 5  
Attach the supplied RJ-45-to-DB-9 female DTE adapter to the nine-pin DB-9 serial port on the PC.  
Insert the other end of the supplied cable in the attached adapter.  
Startup Configuration File  
The ML-Series card needs a startup configuration file in order to configure itself beyond the default  
configuration when it resets. If no startup configuration file exists in the 15310-CL-CTX or the CTX  
2500 flash memory, then the card boots up to a default configuration. Users can manually set up the  
startup configuration file through the serial console port and the Cisco IOS CLI configuration mode or  
load a Cisco IOS supplied sample startup configuration file through CTC. A running configuration  
becomes a startup configuration file when saved with a copy running-config startup-config command.  
It is not possible to establish a Telnet connection to the ML-Series card until a startup configuration file  
is loaded onto the ML-Series card. Access is available through the console port.  
Caution  
Caution  
The copy running-config startup-config command saves a startup configuration file to the flash  
memory of the ML-Series card. This operation is confirmed by the appearance of the text “[OK]” in the  
Cisco IOS CLI session. The startup configuration file is also saved to the ONS node’s database  
restoration file after approximately 30 additional seconds.  
Accessing the read-only memory monitor mode (ROMMON) on the ML-Series card without the  
assistance of Cisco personnel is not recommended. This mode allows actions that can render the  
ML-Series card inoperable. The ML-Series card ROMMON is preconfigured to boot the correct  
Cisco IOS software image for the ML-Series card.  
Caution  
Note  
The maximum permitted size of the startup configuration file on the ONS 15310 ML-Series card is 96  
kilobytes.  
When the running configuration file is altered, a RUNCFG-SAVENEED condition appears in CTC. This  
condition is a reminder to enter a copy running-config startup-config command in the Cisco IOS CLI,  
or configuration changes will be lost when the ML-Series card reboots.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
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.  
During initialization the ML-Series card first checks for a locally, valid cached copy of Cisco IOS. It  
then either downloads the Cisco IOS software image from the 15310-CL-CTX or the CTX 2500 or  
proceeds directly to decompressing and initializing the image. Following Cisco IOS initialization the  
CLI prompt appears, at which time the user can enter the Cisco IOS CLI configuration mode and setup  
the basic ML-Series configuration.  
Passwords  
There are two types of passwords that you can configure for an ML-Series card: an enable password and  
an enable secret password. For maximum security, make the enable password different from the enable  
secret password.  
•
Enable password—The enable password is an unencrypted password. It can contain any number of  
uppercase and lowercase alphanumeric characters. Give the enable password only to users permitted  
to make configuration changes to the ML-Series card.  
•
Enable secret password—The enable secret password is a secure, encrypted password. By setting an  
encrypted password, you can prevent unauthorized configuration changes. On systems running  
Cisco IOS software, you must enter the enable secret password before you can access global  
configuration mode.  
An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric  
characters. The first character cannot be a number. Spaces are valid password characters. Leading  
spaces are ignored; trailing spaces are recognized.  
Passwords are configured in the “Configuring the Management Port” section on page 3-6.  
Configuring the Management Port  
Because there is no separate management port on ML-Series cards, any Fast Ethernet interface (0-7), or  
any POS interface (0-1) can be configured as a management port.  
You can remotely configure the ML-Series card through the management port, but first you must  
configure an IP address so that the ML-Series card is reachable or load a startup configuration file. You  
can manually configure the management port interface from the Cisco IOS CLI via the serial console  
connection.  
To configure Telnet for remote management access, perform the following procedure, beginning in user  
EXEC mode:  
Command  
Purpose  
Router> enable  
Step 1  
Step 2  
Activates user EXEC (or enable) mode.  
The # prompt indicates enable mode.  
Router# configure terminal  
Activates global configuration mode. You can abbreviate  
the command to config t. The Router(config)# prompt  
indicates that you are in global configuration mode.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 3 Initial Configuration of the ML-Series Card  
Startup Configuration File  
Command  
Purpose  
Router(config)# enable password  
password  
Step 3  
Step 4  
Sets the enable password. See the “Passwords” section  
on page 3-6.  
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.  
Router(config)# interface type number  
Router(config-if)#  
Step 5  
Step 6  
Activates interface configuration mode on the interface.  
Router(config-if)# ip address  
ip-address subnetmask  
Allows you to enter the IP address and IP subnet mask  
for the interface specified in Step 5.  
Router(config-if)# no shutdown  
Step 7  
Step 8  
Enables the interface.  
Router(config-if)# exit  
Router(config)#  
Returns to global configuration mode.  
Router(config)# line vty line-number  
Step 9  
Activates line configuration mode for virtual terminal  
connections. Commands entered in this mode control the  
operation of Telnet sessions to the ML-Series card.  
Router(config-line)# password password  
Step 10  
Step 11  
Allows you to enter a password for Telnet sessions.  
Returns to privileged EXEC mode.  
Router(config-line)# end  
Router#  
Router# copy running-config  
startup-config  
Step 12  
(Optional) Saves your configuration changes to  
NVRAM.  
After you have completed configuring remote management on the management port, you can use Telnet  
to remotely assign and verify configurations.  
Configuring the Hostname  
In addition to the system passwords and enable password, your initial configuration should include a  
hostname to easily identify your ML-Series card. To configure the hostname, perform the following task,  
beginning in enable mode:  
Command  
Purpose  
Router# configure terminal  
Step 1  
Step 2  
Activates global configuration mode.  
Router(config)# hostname name-string  
Allows you to enter a system name. In this example, we  
set the hostname to “Router.”  
Router(config)# end  
Step 3  
Step 4  
Returns to privileged EXEC mode.  
Router# copy running-config  
startup-config  
(Optional) Copies your configuration changes to  
NVRAM.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
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. Users can also create their own startup configuration file  
(see the “Manually Creating a Startup Configuration File Through the Serial Console Port” section on  
page 3-6).  
CTC can load a Cisco IOS startup configuration file into the 15310-CL-CTX or CTX 2500 card flash  
before the ML-Series card is physically installed in the slot. When installed, the ML-Series card  
downloads and applies the Cisco IOS software image and the preloaded Cisco IOS startup-configuration  
file. Preloading the startup configuration file allows an ML-Series card to immediately operate as a fully  
configured card when inserted into the ONS 15310.  
If the ML-Series card is booted up prior to the loading of the Cisco IOS startup configuration file into  
15310-CL-CTX or CTX 2500 card flash, then the ML-Series card must be reset to use the Cisco IOS  
startup configuration file or the user can issue the command copy start run at the Cisco IOS CLI to  
configure the ML-Series card to use the Cisco IOS startup configuration file.  
This procedure details the initial loading of a Cisco IOS Startup Configuration file through CTC.  
Step 1  
Step 2  
At the card-level view of the ML-Series card, click the IOS tab (Figure 3-1 on page 3-3).  
The CTC IOS window appears.  
Click the IOS startup config button.  
The config file dialog box appears.  
Step 3  
Step 4  
Click the Local -> CTX button.  
The sample Cisco IOS startup configuration file can be installed from either the ONS 15310 software  
CD or from a PC or network folder:  
•
To install the Cisco supplied startup config file from the ONS 15310 software CD, insert the CD into  
the CD drive of the PC or workstation. Using the CTC config file dialog box, navigate to the CD  
drive of the PC or workstation, and double-click the Basic-IOS-startup-config.txt file.  
•
To install the Cisco supplied config file from a PC or network folder, navigate to the folder  
containing the desired Cisco IOS startup config file and double-click the desired Cisco IOS startup  
config file.  
Step 5  
Step 6  
At the Are you sure? dialog box, click the Yes button.  
The Directory and Filename fields on the configuration file dialog update to reflect that the Cisco IOS  
startup config file is loaded onto the 15310-CL-CTX.  
Load the Cisco IOS startup config file from the 15310-CL-CTX to the ML-Series card:  
a. If the ML-Series card has already been installed, right-click on the ML-Series card at the node-level  
or card-level CTC view and select Soft-reset.  
After the reset, the ML-Series card runs under the newly loaded Cisco IOS startup configuration.  
b. If the ML-Series card is not yet installed, installing the ML-Series card into the slot loads and runs  
the newly loaded Cisco IOS startup configuration on the ML-Series card.  
Caution  
A soft reset or a hard reset on the ONS 15310 ML-Series card is service-affecting.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
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. An experienced Cisco IOS user can locate and troubleshoot the  
line in the startup configuration file that produced the parsing error by opening the Cisco IOS  
CLI and entering a copy start run command.  
Note  
A standard ONS 15310 database restore reinstalls the Cisco IOS startup config file, but does not  
implement the Cisco IOS startup config on the ML-Series. Complete Step 6 to load the  
Cisco IOS startup config file from the 15310-CL-CTX to the ML-Series card.  
Database Restore of the Startup Configuration File  
The ONS 15310-CL includes a database restoration feature. Restoring the database will reconfigure a  
node and the installed line cards to the saved provisioning, except for the ML-Series card. The  
ML-Series card does not automatically restore the startup configuration file saved in the database.  
A user can load the saved startup configuration file onto the ML-Series card in two ways. He can revert  
completely to the saved startup configuration and lose any additional provisioning in the unsaved  
running configuration, which is a restoration scheme similar to other ONS cards, or he can install the  
saved startup configuration file on top of the current running configuration, which is a merging  
restoration scheme used by many Cisco Catalyst devices.  
To revert completely to the startup configuration file saved in the restored database, the user needs to  
soft reset the ML-Series card. Right-click the ML-Series card in CTC and choose Soft-reset or use the  
Cisco IOS CLI reload command to reset the ML-Series card.  
To merge the saved startup configuration file with the running configuration, use the Cisco IOS CLI copy  
startup-config running-config command. This restoration scheme should only be used by experienced  
users with an understanding of the current running configuration and the Cisco IOS copy command. The  
copy startup-config running-config command will not reset the ML-Series card. The user also needs  
to use the Cisco IOS CLI copy running-config startup-config command to save the new merged  
running configuration to the startup configuration file.  
Cisco IOS Command Modes  
The Cisco IOS user interface has several different modes. The commands available to you depend on  
which mode you are in. To get a list of the commands available in a given mode, type a question mark  
(?) at the system prompt.  
Table 3-2 describes the most commonly used modes, how to enter the modes, and the resulting system  
prompts. The system prompt helps you identify which mode you are in and, therefore, which commands  
are available to you.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 3 Initial Configuration of the ML-Series Card  
Cisco IOS Command Modes  
Note  
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. Seeing this message as a result of card reset or other infrequent events  
should not be a cause for concern.  
Table 3-2  
Cisco IOS Command Modes  
Mode  
What You Use It For  
How to Access  
Prompt  
Router>  
User EXEC  
Connect to remote devices,  
change terminal settings on a  
temporary basis, perform basic  
tests, and display system  
information.  
Log in.  
Router#  
Privileged EXEC  
Set operating parameters. The  
From user EXEC mode, enter the  
(also called Enable  
mode)  
privileged command set includes enable command and the enable  
the commands in user EXEC  
mode, as well as the configure  
command. Use this command  
mode to access the other  
command modes.  
password.  
Router(config)#  
Global configuration  
Configure features that affect the From privileged EXEC mode,  
system as a whole.  
enter the configure terminal  
command.  
Router(config-if)#  
Interface configuration Enable features for a particular From global configuration mode,  
interface. Interface commands  
enable or modify the operation  
of a Fast Ethernet or POS port.  
enter the interface type number  
command.  
For example, enter  
interface fastethernet 0 for  
Fast Ethernet or interface pos 0  
for POS interfaces.  
Router(config-line)#  
Line configuration  
Configure the console port or vty From global configuration mode,  
line from the directly connected enter the line console 0  
console or the virtual terminal  
used with Telnet.  
command to configure the  
console port or the  
line vty line-number command  
to configure a vty line.  
When you start a session on the ML-Series card, you begin in user EXEC mode. Only a small subset of  
the commands are available in user EXEC mode. To have access to all commands, you must enter  
privileged EXEC mode, also called Enable mode. From privileged EXEC mode, you can type in any  
EXEC command or access global configuration mode. Most of the EXEC commands are single-use  
commands, such as show commands, which show the current configuration status, and clear commands,  
which clear counters or interfaces. The EXEC commands are not saved across reboots of the ML-Series  
card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                     
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.  
ROMMON mode is a separate mode used when the ML-Series card cannot boot properly. For example,  
your ML-Series card might enter ROM monitor mode if it does not find a valid system image when it is  
booting, or if its configuration file is corrupted at startup.  
Using the Command Modes  
The Cisco IOS command interpreter, called the EXEC, interprets and executes the commands you enter.  
You can abbreviate commands and keywords by entering just enough characters to make the command  
unique from other commands. For example, you can abbreviate the show command to sh and the  
configure terminal command to config t.  
Exit  
When you type exit, the ML-Series card backs out one level. In general, typing exit returns you to global  
configuration mode. Enter end to exit configuration mode completely and return to privileged EXEC  
mode.  
Getting Help  
In any command mode, you can get a list of available commands by entering a question mark (?).  
Router> ?  
To obtain a list of commands that begin with a particular character sequence, type in those characters  
followed immediately by the question mark (?). Do not include a space. This form of help is called word  
help, because it completes a word for you.  
Router# co?  
configure  
To list keywords or arguments, enter a question mark in place of a keyword or argument. Include a space  
before the question mark. This form of help is called command syntax help, because it reminds you  
which keywords or arguments are applicable based on the command, keywords, and arguments you have  
already entered.  
Router# configure ?  
memory  
Configure from NV memory  
network  
Configure from a TFTP network host  
overwrite-network Overwrite NV memory from TFTP network host  
terminal  
<cr>  
Configure from the terminal  
To redisplay a command you previously entered, press the Up Arrow key. You can continue to press the  
Up Arrow key to see more of the previously issued commands.  
Tip  
If you are having trouble entering a command, check the system prompt, and enter the question mark (?)  
for a list of available commands. You might be in the wrong command mode or using incorrect syntax.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
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, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
3-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
C H A P T E R  
4
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.  
This chapter includes the following major sections:  
•
•
•
Understanding Bridging, page 4-1  
Configuring Bridging, page 4-2  
Monitoring and Verifying Bridging, page 4-3  
Caution  
Cisco Inter-Switch Link (ISL) and Cisco Dynamic Trunking Protocol (DTP) are not supported by the  
ML-Series cards, but the ML-Series broadcast forwards these formats. Using ISL or DTP on connecting  
devices is not recommended. Some Cisco devices attempt to use ISL or DTP by default.  
Understanding Bridging  
The ML-Series card supports transparent bridging for Fast Ethernet, Fast EtherChannel (FEC),  
packet-over-SONET/SDH (POS) ports, and POS channel. It supports a maximum of 255 active bridge  
groups. Transparent bridging combines the speed and protocol transparency of a spanning-tree bridge,  
along with the functionality, reliability, and security of a router.  
To configure bridging, you must perform the following tasks in the modes indicated:  
•
In global configuration mode:  
–
–
Enable bridging of IP packets.  
(Optional) Select the type of Spanning Tree Protocol (STP).  
•
In interface configuration mode:  
–
Determine which interfaces belong to the same bridge group.  
The ML-Series card bridges all nonrouted traffic among the network interfaces comprising the  
bridge group. If spanning tree is enabled, the interfaces become part of the same spanning tree.  
Interfaces that do not participate in a bridge group cannot forward bridged traffic.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
4-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 4 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.  
Spanning tree is not mandatory for an ML-Series card bridge group, but if it is configured, a  
separate spanning-tree process runs for each configured bridge group. A bridge group  
establishes a spanning tree based on the bridge protocol data units (BPDUs) it receives on only  
its member interfaces.  
Configuring Bridging  
Beginning in global configuration mode, use the following steps to configure bridging:  
Command  
Purpose  
ML_Series(config)# no ip  
routing  
Step 1  
Step 2  
Enables bridging of IP packets. This command needs to be  
executed once per card, not once per bridge-group. This step is  
not done for IRB.  
ML_Series(config)# bridge  
bridge-group-number [protocol  
{drpi-rstp | rstp | ieee}]  
Assigns a bridge group number and defines the appropriate  
spanning-tree type:  
•
drpri-rstp is the protocol used to interconnect dual resilient  
packet ring (RPR) to protect from node failure. Do not  
configure this option on the ONS 15310-CL or  
ONS 15310-MA ML-Series.  
•
rstp is the IEEE 802.1W Rapid Spanning Tree.  
ieee is the IEEE 802.1D Spanning Tree Protocol.  
•
Note  
Spanning tree is not mandatory for an ML-Series card  
bridge group, but configuring spanning tree blocks  
network loops.  
ML_Series(config)# bridge  
bridge-group-number priority  
number  
Step 3  
(Optional) Assigns a specific priority to the bridge, to assist in  
the spanning-tree root definition. Lowering the priority of a  
bridge makes it more likely that the bridge is selected as the root.  
ML_Series(config)# interface  
type number  
Step 4  
Step 5  
Enters interface configuration mode to configure the interface of  
the ML-Series card.  
ML_Series(config-if)#  
bridge-group  
Assigns a network interface to a bridge group.  
bridge-group-number  
ML_Series(config-if)# no  
shutdown  
Step 6  
Changes the shutdown state to up and enables the interface.  
ML_Series(config-if)# end  
Step 7  
Step 8  
Returns to privileged EXEC mode.  
ML_Series# copy running-config  
startup-config  
(Optional) Saves your entries in the configuration file.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
4-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 4 Configuring Bridging on the ML-Series Card  
Monitoring and Verifying Bridging  
Figure 4-1 shows a bridging example. Example 4-1 shows the code used to configure ML-Series A.  
Example 4-2 shows the code used to configure ML-Series B.  
Figure 4-1  
Bridging Example  
ML_Series_A  
ML_Series_B  
pos 0  
pos 0  
SONET/SDH  
fast ethernet 0  
fast ethernet 0  
Example 4-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 4-2 ML_Series B Configuration  
bridge irb  
bridge 1 protocol ieee  
!
!
interface FastEthernet0  
no ip address  
bridge-group 1  
!
interface POS0  
no ip address  
bridge-group 1  
Monitoring and Verifying Bridging  
After you have set up the ML-Series card for bridging, you can monitor and verify its operation by  
performing the following procedure in privileged EXEC mode:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
4-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 4 Configuring Bridging on the ML-Series Card  
Monitoring and Verifying Bridging  
Command  
Purpose  
ML_Series# clear bridge  
bridge-group-number  
Step 1  
Step 2  
Removes any learned entries from the forwarding database of a  
particular bridge group, clears the transmit, and receives counts  
for any statically configured forwarding entries.  
ML_Series# show bridge  
{bridge-group-number|  
interface-address}  
Displays classes of entries in the bridge forwarding database.  
ML_Series# show bridge verbose  
Step 3  
Step 4  
Displays detailed information about configured bridge groups.  
Displays detailed information about spanning tree.  
ML_Series# show spanning-tree  
[bridge-group-number][brief]  
•
bridge-group-number restricts the spanning tree information  
to specific bridge groups.  
•
brief displays summary information about spanning tree.  
Example 4-3 shows examples of monitoring and verifying bridging.  
Example 4-3 Monitoring and Verifying Bridging  
ML_Series# show bridge 1  
Total of 1260 station blocks, 310 free  
Codes: P - permanent, S - self  
Bridge Group 1:  
Maximum dynamic entries allowed: 1000  
Current dynamic entry count: 1  
Address  
Action  
Interface  
0000.0001.3100  
forward  
FastEthernet0  
ML_Series# show spanning-tree 1  
Bridge group 1 is executing the rstp compatible Spanning Tree protocol  
Bridge Identifier has priority 32768, sysid 1, address 000b.fcfa.339e  
Configured hello time 2, max age 20, forward delay 15  
We are the root of the spanning tree  
Topology change flag not set, detected flag not set  
Number of topology changes 1 last change occurred 1w1d ago  
from POS0.1  
Times: hold 1, topology change 35, notification 2  
hello 2, max age 20, forward delay 15  
Timers: hello 0, topology change 0, notification 0, aging 300  
Port 3 (FastEthernet0) of Bridge group 1 is designated disabled  
Port path cost 19, Port priority 128, Port Identifier 128.3.  
Designated root has priority 32769, address 000b.fcfa.339e  
Designated bridge has priority 32769, address 000b.fcfa.339e  
Designated port id is 128.3, designated path cost 0  
Timers: message age 0, forward delay 0, hold 0  
Number of transitions to forwarding state: 0  
Link type is point-to-point by default  
BPDU: sent 0, received 0  
Port 15 (POS0.1) of Bridge group 1 is designated down  
Port path cost 37, Port priority 128, Port Identifier 128.15.  
Designated root has priority 32769, address 000b.fcfa.339e  
Designated bridge has priority 32769, address 000b.fcfa.339e  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
4-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 4 Configuring Bridging on the ML-Series Card  
Monitoring and Verifying Bridging  
Designated port id is 128.15, designated path cost 0  
Timers: message age 0, forward delay 0, hold 0  
Number of transitions to forwarding state: 1  
Link type is point-to-point by default  
BPDU: sent 370832, received 4  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
4-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 4 Configuring Bridging on the ML-Series Card  
Monitoring and Verifying Bridging  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
4-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
5
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 6, “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.  
This chapter contains the following major sections:  
•
•
•
•
General Interface Guidelines, page 5-1  
Basic Interface Configuration, page 5-3  
Basic Fast Ethernet and POS Interface Configuration, page 5-4  
Monitoring Operations on the Fast Ethernet Interfaces, page 5-6  
General Interface Guidelines  
The main function of the ML-Series card is to relay packets from one data link to another. Consequently,  
you must configure the characteristics of the interfaces, which receive and send packets. Interface  
characteristics include, but are not limited to, IP address, address of the port, data encapsulation method,  
and media type.  
Many features are enabled on a per-interface basis. Interface configuration mode contains commands  
that modify the interface operation (for example, of an Ethernet port). When you enter the interface  
command, you must specify the interface type and number.  
The following general guidelines apply to all physical and virtual interface configuration processes:  
•
All interfaces have a name that is composed of an interface type (word) and a Port ID (number). For  
example, Fast Ethernet 2.  
•
•
Configure each interface with a bridge-group or IP address and IP subnet mask.  
VLANs are supported through the use of subinterfaces. The subinterface is a logical interface  
configured separately from the associated physical interface.  
•
Each physical interface, including the internal POS interfaces, has an assigned MAC address.  
MAC Addresses  
Every port or device that connects to an Ethernet network needs a MAC address. Other devices in the  
network use MAC addresses to locate specific ports in the network and to create and update routing  
tables and data structures.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 5 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.339e)  
Description: 100 mbps full duplex q-in-q tunnel  
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,  
reliability 255/255, txload 18/255, rxload 200/255  
Encapsulation ARPA, loopback not set  
Keepalive set (10 sec)  
Full-duplex, 100Mb/s, 100BaseTX  
ARP type: ARPA, ARP Timeout 04:00:00  
Last input 00:00:00, output 00:00:00, output hang never  
Last clearing of "show interface" counters never  
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: weighted fair  
Output queue: 0/1000/64/0 (size/max total/threshold/drops)  
Conversations 0/0/256 (active/max active/max total)  
Reserved Conversations 0/0 (allocated/max allocated)  
Available Bandwidth 75000 kilobits/sec  
30 second input rate 78525000 bits/sec, 144348 packets/sec  
30 second output rate 7363000 bits/sec, 13537 packets/sec  
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 carrier, 0 no carrier  
0 output buffer failures, 0 output buffers swapped out  
Interface Port ID  
The interface port ID designates the physical location of the interface within the ML-Series card. It is  
the name that you use to identify the interface you are configuring. The system software uses interface  
port IDs to control activity within the ML-Series card and to display status information. Interface port  
IDs are not used by other devices in the network; they are specific to the individual ML-Series card and  
its internal components and software.  
The ML-100T-8 port IDs for the eight Fast Ethernet interfaces are Fast Ethernet 0 through 7. The  
ML-Series card features two POS ports. The ML-Series port IDs for the two POS interfaces are POS 0  
and 1. You can use user-defined abbreviations such as f0 through f7 to configure the eight Fast Ethernet  
interfaces, and POS0 and POS1 to configure the two POS ports.  
You can use Cisco IOS show commands to display information about any or all the interfaces of the  
ML-Series card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 5 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.  
The key word your-password is the password set up by the user in the initial configuration of the  
ML-Series card.  
ML_Series> enable  
Password:<your-password>  
ML_Series# configure terminal  
ML_Series(config)#  
Step 2  
Step 3  
Enter the interface command, followed by the interface type (for example, fastethernet or pos) and its  
interface port ID (see the “Interface Port ID” section on page 5-2).  
For example, to configure a Fast Ethernet port, enter this command:  
ML_Series(config)# interface fastethernet number  
Follow each interface command with the interface configuration commands required for your particular  
interface.  
The commands you enter define the protocols and applications that will run on the interface. The  
ML-Series card collects and applies commands to the interface command until you enter another  
interface command or a command that is not an interface configuration command. You can also enter  
end to return to privileged EXEC mode.  
Step 4  
Check the status of the configured interface by entering the EXEC show interface command.  
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.339e)  
Description: 100 mbps full duplex q-in-q tunnel  
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,  
reliability 255/255, txload 18/255, rxload 200/255  
Encapsulation ARPA, loopback not set  
Keepalive set (10 sec)  
Full-duplex, 100Mb/s, 100BaseTX  
ARP type: ARPA, ARP Timeout 04:00:00  
Last input 00:00:00, output 00:00:00, output hang never  
Last clearing of "show interface" counters never  
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: weighted fair  
Output queue: 0/1000/64/0 (size/max total/threshold/drops)  
Conversations 0/0/256 (active/max active/max total)  
Reserved Conversations 0/0 (allocated/max allocated)  
Available Bandwidth 75000 kilobits/sec  
30 second input rate 78525000 bits/sec, 144348 packets/sec  
30 second output rate 7363000 bits/sec, 13537 packets/sec  
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  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 5 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.  
To configure an IP address or bridge-group number on a Fast Ethernet or POS interface, perform the  
following procedure, beginning in global configuration mode:  
Command  
Purpose  
ML_Series(config)# interface type number  
Step 1  
Step 2  
Activates interface configuration mode to  
configure either the Fast Ethernet interface or the  
POS interface.  
ML_Series(config-if)# {ip address  
ip-address subnet-mask | bridge-group  
bridge-group-number}  
Sets the IP address and IP subnet mask to be  
assigned to the interface.  
or  
Assigns a network interface to a bridge group.  
ML_Series(config-if)# no shutdown  
ML_Series(config)# end  
Step 3  
Enables the interface by preventing it from  
shutting down.  
Step 4  
Step 5  
Returns to privileged EXEC mode.  
ML_Series# copy running-config  
startup-config  
(Optional) Saves configuration changes to flash  
database.  
Configuring the Fast Ethernet Interfaces  
To configure the IP address or bridge-group number, autonegotiation, and flow control on a Fast Ethernet  
interface, perform the following procedure, beginning in global configuration mode:  
Command  
Purpose  
ML_Series(config)# interface fastethernet  
number  
Step 1  
Step 2  
Activates interface configuration mode to  
configure the Fast Ethernet interface.  
ML_Series(config-if)# {ip address  
ip-address subnet-mask | bridge-group  
bridge-group-number}  
Sets the IP address and IP subnet mask to be  
assigned to the interface.  
or  
Assigns a network interface to a bridge group.  
ML_Series(config-if)# [no] speed {10 | 100  
| auto}  
Step 3  
Configures the transmission speed for 10 or  
100 Mbps. If you set the speed or duplex for auto,  
you enable autonegotiation on the system—the  
ML-Series card matches the speed and duplex  
mode of the partner node.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 5 Configuring Interfaces on the ML-Series Card  
Basic Fast Ethernet and POS Interface Configuration  
Command  
Purpose  
ML_Series(config-if)# [no] duplex {full  
half auto}  
|
Step 4  
Step 5  
Sets full duplex, half duplex, or autonegotiate  
mode.  
|
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.  
ML_Series(config-if)# no shutdown  
ML_Series(config)# end  
Step 6  
Enables the interface by preventing it from  
shutting down.  
Step 7  
Step 8  
Returns to privileged EXEC mode.  
ML_Series# copy running-config  
startup-config  
(Optional) Saves your configuration changes to  
the flash database.  
Example 5-1 shows how to do the initial configuration of a Fast Ethernet interface with an IP address,  
autonegotiated speed, and autonegotiated duplex.  
Example 5-1 Initial Configuration of a Fast Ethernet Interface  
ML_Series(config)# interface fastethernet 1  
ML_Series(config-if)# ip address 10.1.2.4 255.0.0.0  
ML_Series(config-if)# speed auto  
ML_Series(config-if)# duplex auto  
ML_Series(config-if)# no shutdown  
ML_Series(config-if)# end  
ML_Series# copy running-config startup-config  
Configuring the POS Interfaces  
Encapsulation changes on POS ports are allowed only when the interface is in a manual shutdown  
(ADMIN_DOWN). For advanced POS interface configuration, see Chapter 6, “Configuring POS on the  
ML-Series Card.”  
Note  
The initial state of the ONS 15310-CL and ONS 15310-MA ML-Series card POS port is inactive. A POS  
interface command of no shutdown is required to carry traffic on the SONET circuit.  
To configure the IP address, bridge group, or encapsulation for the POS interface, perform the following  
procedure, beginning in global configuration mode:  
Command  
Purpose  
ML_Series(config)# interface pos number  
Step 1  
Step 2  
Activates interface configuration mode to  
configure the POS interface.  
ML_Series(config-if)# {ip address  
ip-address subnet-mask | bridge-group  
bridge-group-number}  
Sets the IP address and subnet mask.  
or  
Assigns a network interface to a bridge group.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 5 Configuring Interfaces on the ML-Series Card  
Monitoring Operations on the Fast Ethernet Interfaces  
Command  
Purpose  
ML_Series(config-if)# shutdown  
Step 3  
Step 4  
Manually shuts down the interface. Encapsulation  
changes on POS ports are allowed only when the  
interface is shut down (ADMIN_DOWN).  
ML_Series(config-if)# encapsulation type  
Sets the encapsulation type. Valid values are:  
•
hdlc—Cisco high-level data link control  
(HDLC)  
•
lex—(Default) LAN extension, special  
encapsulation for use with Cisco ONS  
Ethernet line cards  
•
ppp—Point-to-Point Protocol  
Note  
Under GFP-F framing, the  
ONS 15310-CL and ONS 15310-MA  
ML-Series card is restricted to LEX  
encapsulation.  
ML_Series(config-if)# no shutdown  
ML_Series(config)# end  
Step 5  
Step 6  
Step 7  
Restarts the shutdown interface.  
Returns to privileged EXEC mode.  
ML_Series# copy running-config  
startup-config  
(Optional) Saves configuration changes to  
NVRAM.  
Monitoring Operations on the Fast Ethernet Interfaces  
To verify the settings after you have configured the interfaces, enter the show interface command. For  
additional information on monitoring the operations on POS interfaces, see the “Configuring POS on the  
ML-Series Card” chapter.  
Example 5-2 shows the output from the show interface command, which displays the status of the  
interface including port speed and duplex operation.  
Example 5-2 show interface Command Output  
ML_Series# show interface fastethernet 0  
FastEthernet0 is up, line protocol is up  
Hardware is epif_port, address is 000b.fcfa.339e (bia 000b.fcfa.339e)  
Description: 100 mbps full duplex q-in-q tunnel  
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,  
reliability 255/255, txload 18/255, rxload 200/255  
Encapsulation ARPA, loopback not set  
Keepalive set (10 sec)  
Full-duplex, 100Mb/s, 100BaseTX  
ARP type: ARPA, ARP Timeout 04:00:00  
Last input 00:00:00, output 00:00:00, output hang never  
Last clearing of "show interface" counters never  
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: weighted fair  
Output queue: 0/1000/64/0 (size/max total/threshold/drops)  
Conversations 0/0/256 (active/max active/max total)  
Reserved Conversations 0/0 (allocated/max allocated)  
Available Bandwidth 75000 kilobits/sec  
30 second input rate 78525000 bits/sec, 144348 packets/sec  
30 second output rate 7363000 bits/sec, 13537 packets/sec  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 5 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 carrier, 0 no carrier  
0 output buffer failures, 0 output buffers swapped out  
Enter the show controller command to display information about the Fast Ethernet controller chip.  
Example 5-3 shows the output from the show controller command, which shows statistics, including  
information about initialization block information and raw MAC counters.  
Example 5-3 show controller Command Output  
ML_Series# show controller fastethernet 0  
IF Name: FastEthernet0  
Port Status UP  
Send Flow Control  
: Disabled  
Receive Flow Control : Enabled  
MAC registers  
CMCR : 0x00000433 (Tx Enabled, Rx Enabled)  
CMPR : 0x150B0A82 (Long Frame Enabled)  
FCR : 0x00008007  
MII registers:  
Control Register  
Status Register  
(0x0): 0x100 (Auto negotation disabled)  
(0x1): 0x780D (Link status Up)  
PHY Identification Register 1 (0x2): 0x40  
PHY Identification Register 2 (0x3): 0x61D4  
Auto Neg. Advertisement Reg  
(0x4): 0x461 (Speed 10, Duplex Full)  
Auto Neg. Partner Ability Reg (0x5): 0x0  
Auto Neg. Expansion Register (0x6): 0x4  
(Speed 10, Duplex Half)  
100Base-X Aux Control Reg  
(0x10): 0x0  
100Base-X Aux Status Register(0x11): 0x0  
100Base-X Rcv Error Counter (0x12): 0x0  
100Base-X False Carr. Counter(0x13): 0x400  
100Base-X Disconnect Counter (0x14): 0x200  
Aux Control/Status Register (0x18): 0x31  
Aux Status Summary Register (0x19): 0x5  
Interrupt Register  
(0x1A): 0xC000  
10Base-T Aux Err & Gen Status(0x1C): 0x3021  
Aux Mode Register  
Aux Multi-phy Register  
(0x1D): 0x0  
(0x1E): 0x0  
Counters :  
MAC receive conters:  
Bytes  
749876721  
pkt64  
2394  
pkts64to127  
49002  
21291  
11308  
40175  
24947  
54893  
11319  
0
pkts128to255  
pkts256to511  
pkts512to1023  
pkts1024to1518  
pkts1519to1530  
pkts_good_giants  
pkts_error_giants  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 5 Configuring Interfaces on the ML-Series Card  
Monitoring Operations on the Fast Ethernet Interfaces  
pkts_good_runts  
pkts_error_runts  
pkts_ucast  
0
5
26976  
pkts_mcast  
57281  
pkts_bcast  
align_errors  
FCS_errors  
0
1
5
0
Overruns  
MAC Transmit Counters  
Bytes  
pkts64  
pkts65to127  
pkts128to255  
pkts256to511  
pkts512to1023  
pkts1024to1518  
pkts1519to1530  
pkts_ucast  
1657084026  
23344  
48188  
12358  
38550  
24897  
11305  
62760  
17250  
23108  
11  
pkts_mcast  
pkts_bcast  
pkts_fcs_err  
pkts_giants  
pkts_underruns  
pkts_one_collision  
0
0
0
0
pkts_multiple_collisions 0  
pkts_excessive_collision 0  
Ucode drops  
2053079661  
Enter the show run interface [type number] command to display information about the configuration of  
the Fast Ethernet interface. The command is useful when there are multiple interfaces and you want to  
look at the configuration of a specific interface.  
Example 5-4 shows output from the show run interface [type number] command, which includes  
information about the IP or lack of IP address and the state of the interface.  
Example 5-4 show run interface Command Output  
daytona# show run interface fastethernet 1  
Building configuration...  
Current configuration : 222 bytes  
!
interface FastEthernet1  
no ip address  
duplex full  
speed 10  
mode dot1q-tunnel  
l2protocol-tunnel cdp  
l2protocol-tunnel stp  
l2protocol-tunnel vtp  
no cdp enable  
bridge-group 2  
bridge-group 2 spanning-disabled  
end  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
5-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
C H A P T E R  
6
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 5, “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.  
This chapter contains the following major sections:  
•
•
•
Understanding POS on the ML-Series Card, page 6-1  
Configuring the POS Interface, page 6-4  
Monitoring and Verifying POS, page 6-8  
Understanding POS on the ML-Series Card  
Ethernet frames and IP data packets need to be framed and encapsulated into SONET frames for  
transport across the SONET network. This framing and encapsulation process is known as POS and is  
carried out by the ML-Series card.  
The ML-Series card treats all the standard Ethernet ports on the front of the card and the two POS ports  
as switch ports. Under Cisco IOS, the POS port is an interface similar to the other Ethernet interfaces on  
the ML-Series card. Many standard Cisco IOS features, such as IEEE 802.1 Q VLAN configuration, are  
configured on the POS interface in the same manner as on a standard Ethernet interface. Other features  
and configurations are done strictly on the POS interface. The configuration of features limited to POS  
ports is shown in this chapter.  
Available Circuit Sizes and Combinations  
Each POS port terminates an independent contiguous SONET concatenation (CCAT) or virtual SONET  
concatenation (VCAT). The SONET circuit is created for these ports through Cisco Transport Controller  
(CTC) or Transaction Language One (TL1) in the same manner as a SONET circuit is created for a  
non-Ethernet line card. Table 6-1shows the circuit sizes available for the ML-Series card on the  
ONS 15310-CL and ONS 15310-MA, and the circuit sizes required for Ethernet wire speeds.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 6 Configuring POS on the ML-Series Card  
Understanding POS on the ML-Series Card  
Table 6-1  
ML-Series Card Supported Circuit Sizes and Sizes Required for Ethernet Wire Speeds  
Ethernet Wire Speed CCAT High Order  
VCAT High Order  
STS-1-1v  
STS-1-2v1  
10 Mbps  
STS-1  
—
100 Mbps  
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. The VCAT  
differential delay is the relative arrival time measurement between members of a virtual concatenation  
group (VCG).  
Note  
Note  
The initial state of the ONS 15310-CL and ONS 15310-MA ML-Series card POS port is inactive. A POS  
interface command of no shutdown is required to carry traffic on the SONET circuit.  
ML-Series card POS interfaces normally send an alarm for signal label mismatch failure in the ONS  
15454 STS path overhead (PDI-P) to the far end when the POS link goes down or when RPR wraps.  
ML-Series card POS interfaces do not send PDI-P to the far-end when PDI-P is detected, when a remote  
defection indication alarm (RDI-P) is being sent to the far end, or when the only defects detected are  
generic framing procedure (GFP)-loss of frame delineation (LFD), GFP client signal fail (CSF), virtual  
concatenation (VCAT)-loss of multiframe (LOM), or VCAT-loss of sequence (SQM).  
LCAS Support  
The ML-100T-8 card and the CE-100T-8 card (both the ONS 15310-CL/ONS 15310-MA version and the  
ONS 15454 SONET/SDH version) have hardware-based support for the ITU-T G.7042 standard link  
capacity adjustment scheme (LCAS). This allows the user to dynamically resize a high-order or  
low-order VCAT circuit through CTC or TL1 without affecting other members of the VCG (errorless).  
ML-100T-8 LCAS support is high order only and is limited to a two-member VCG.  
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 terminating on an ONS 15454 SONET ML-Series card.  
J1 Path Trace, and SONET Alarms  
The ML-100T-8 card also reports SONET alarms and transmits and monitors the J1 path trace byte in  
the same manner as OC-N cards. Support for path termination functions includes:  
•
•
•
•
H1 and H2 concatenation indication  
Bit interleaved parity 3 (BIP-3) generation  
G1 path status indication  
C2 path signal label read/write  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 6 Configuring POS on the ML-Series Card  
Understanding POS on the ML-Series Card  
•
•
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 framing procedure (GFP-F) framing. Supported  
encapsulation and cyclic redundancy check (CRC) sizes for the framing types are detailed in Table 6-2.  
Table 6-2  
ML-Series Card Encapsulation, Framing, and CRC Sizes  
GFP-F Framing  
LEX (default)1  
Cisco HDLC  
PPP/BCP  
HDLC Framing  
Encapsulations  
LEX (default)  
CRC Sizes  
32-bit (default)  
32-bit (default)  
None (FCS disabled)  
1. RPR requires LEX encapsulation in either framing mode.  
LEX is the common term for Cisco-EoS-LEX, which is a proprietary Cisco Ethernet-over-SONET  
encapsulation. This encapsulation is available on most ONS Ethernet cards. When the ML-Series card  
is configured for GFP-F framing, the LEX encapsulation is in accordance with ITU-T G.7041 as  
standard mapped Ethernet over GFP. Under GFP-F framing, the Cisco IOS CLI also uses this lex  
keyword to represent standard mapped Ethernet over GFP-F.  
LEX encapsulation is the required and default encapsulation for RPR on the ML-Series card. The  
maximum transmission unit (MTU) size is not configurable and is set at a 1500-byte maximum (standard  
Ethernet MTU). In addition, the ML-Series card supports baby giant frames in which the standard  
Ethernet frame is augmented by IEEE 802.1 Q tags or Multiprotocol Label Switching (MPLS) tags. It  
does not support full Jumbo frames.  
The ML-Series card supports GFP null mode. GFP-F client-management frames (CMFs) are counted and  
discarded.  
The ML-100T-8 card is interoperable with the ONS 15310-CL and ONS 15310-MA CE-100T-8 card and  
several other ONS Ethernet cards. For specific details on the ONS 15310-CL and ONS 15310-MA  
CE-100T-8 card’s encapsulation, framing, and CRC, see Chapter 17, “CE-Series Ethernet Cards.” For  
specific details on interoperability with other ONS system Ethernet cards, including framing mode,  
encapsulation, and CRC, refer to the “POS on ONS Ethernet Cards” chapter of the Cisco ONS 15454  
and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 6 Configuring POS on the ML-Series Card  
Configuring the POS Interface  
Configuring the POS Interface  
The user can configure framing mode, encapsulation, and Cisco IOS SONET alarm reporting parameters  
through Cisco IOS.  
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. ML-Series card POS interfaces do not send PDI-P to the far end when PDI-P is detected, when  
RDI-P is being sent to the far end, or when the only defects detected are GFP LFD, GFP CSF,  
VCAT LOM, or VCAT SQM.  
Configuring POS Interface Framing Mode  
You can configure framing mode on an ML-100T-8 card through Cisco IOS. You cannot configure  
framing mode through CTC on the ML-100T-8 card.  
Framing mode can be changed on a port by port basis. The user does not need to delete the existing  
circuits or reboot the ML-100T-8 card. On the ONS 15454 or ONS 15454 SDH ML-Series cards, the  
circuits must be deleted and the card must reboot for the framing mode to change.  
To configure framing mode for the ML-Series card, perform the following steps, beginning in global  
configuration mode:  
Command  
Purpose  
Router(config)# interface pos number  
Step 1  
Step 2  
Activates interface configuration mode to  
configure the POS interface.  
Router(config-if)# shutdown  
Manually shuts down the interface. Encapsulation  
and framing mode changes on POS ports are  
allowed only when the interface is shut down  
(ADMIN_DOWN).  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 6 Configuring POS on the ML-Series Card  
Configuring the POS Interface  
Command  
Purpose  
Router(config-if)# [no] pos mode gfp  
[fcs-disabled]  
Step 3  
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.  
•
GFP (default)—The ML-Series card supports  
the frame mapped version of generic framing  
procedure (GFP-F).  
GFP-F with a 32-bit CRC, also referred to as  
frame check sequence (FCS), is enabled by  
default. The optional FCS-disabled keyword  
disables the GFP-F 32-bit FCS.  
The FCS-disabled keyword is not available when  
setting the framing mode to Cisco HDLC.  
Note  
CRC-under-HDLC framing is restricted to  
a 32-bit size and cannot be disabled.  
Note  
The GFP-F FCS is compliant with ITU-T  
G.7041/Y.1303  
Router(config-if)# no shutdown  
Router(config)# end  
Step 4  
Step 5  
Step 6  
Restarts the shutdown interface.  
Returns to privileged EXEC mode.  
Router# copy running-config startup-config  
(Optional) Saves configuration changes to  
NVRAM.  
Configuring POS Interface Encapsulation Type Under GFP-F Framing  
To configure the encapsulation type for a ML-Series card, perform the following steps beginning in  
global configuration mode:  
Command  
Purpose  
Router(config)# interface pos number  
Step 1  
Step 2  
Activates interface configuration mode to  
configure the POS interface.  
Router(config-if)# shutdown  
Manually shuts down the interface. Encapsulation  
and framing mode changes on POS ports are  
allowed only when the interface is shut down  
(ADMIN_DOWN).  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 6 Configuring POS on the ML-Series Card  
Configuring the POS Interface  
Command  
Purpose  
Sets the encapsulation type. Valid values are:  
Router(config-if)# encapsulation type  
Step 3  
•
•
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.  
Router(config-if)# no shutdown  
Router(config)# end  
Step 4  
Step 5  
Step 6  
Restarts the shutdown interface.  
Returns to privileged EXEC mode.  
Router# copy running-config startup-config  
(Optional) Saves configuration changes to  
NVRAM.  
SONET Alarms  
The ML-Series cards report SONET alarms under Cisco IOS, CTC, and TL1. A number of path alarms  
are reported in the Cisco IOS console. Configuring Cisco IOS console alarm reporting has no effect on  
CTC and TL1 alarm reporting. The “Configuring SONET Alarms” section on page 6-7 procedure  
specifies the alarms reported to the Cisco IOS console.  
CTC and TL1 have sophisticated SONET alarm reporting capabilities. The ML-Series card reports  
Telcordia GR-253 SONET alarms on the Alarms tab of CTC, and in TL1-like other ONS system line  
cards. For more information about alarms and alarm definitions, refer to the “Alarm Troubleshooting”  
chapter of the Cisco ONS 15454 Troubleshooting Guide.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 6 Configuring POS on the ML-Series Card  
Configuring the POS Interface  
Configuring SONET Alarms  
All SONET alarms are logged on the Cisco IOS CLI by default. But to provision or disable the reporting  
of SONET alarms on the Cisco IOS CLI, perform the following steps beginning in global configuration  
mode:  
Command  
Purpose  
Router(config)# interface pos  
number  
Step 1  
Step 2  
Enters interface configuration mode and specifies the POS  
interface to configure.  
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.  
The alarms are as follows:  
•
•
•
•
•
•
•
•
•
•
•
all—All alarms/signals  
encap—Path encapsulation mismatch  
pais—Path alarm indication signal  
plop—Path loss of pointer  
ppdi—Path payload defect indication  
pplm—Payload label, C2 mismatch  
prdi—Path remote defect indication  
ptim—Path trace identifier mismatch  
puneq—Path label equivalent to zero  
sd-ber-b3—PBIP BER in excess of SD threshold  
sf-ber-b3—PBIP BER in excess of SF threshold  
Router(config-if)# end  
Step 3  
Step 4  
Returns to the privileged EXEC mode.  
Router# copy running-config  
startup-config  
(Optional) Saves configuration changes to NVRAM.  
To determine which alarms are reported on the POS interface and to display the bit error rate (BER)  
thresholds, use the show controllers pos command, as described in the “Monitoring and Verifying POS”  
section on page 6-8.  
Configuring SONET Delay Triggers  
You can set path alarms listed as triggers to bring down the line protocol of the POS interface. When you  
configure the path alarms as triggers, you can also specify a delay for the triggers using the pos trigger  
delay command. You can set the delay from 200 to 2000 ms. If you do not specify a time interval, the  
default delay is set to 200 ms.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 6 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  
Router(config)# interface pos  
number  
Step 1  
Step 2  
Enters interface configuration mode and specifies the POS  
interface to configure.  
Router(config-if)# pos trigger  
defect {all | ber_sf_b3 | encap  
| pais | plop | ppdi | pplm |  
prdi | ptim | puneq}  
Configures certain path defects as triggers to bring down the  
POS interface. The configurable triggers are as follows:  
•
•
all—All link down alarm failures  
ber_sd_b3—PBIP BER in excess of SD threshold  
failure  
•
•
ber_sf_b3—PBIP BER in excess of SD threshold failure  
(default)  
encap—Path Signal Label Encapsulation Mismatch  
failure (default)  
•
•
•
•
•
•
•
pais—Path Alarm Indication Signal failure (default)  
plop—Path Loss of Pointer failure (default)  
ppdi—Path Payload Defect Indication failure (default)  
pplm—Payload label mismatch path (default)  
prdi—Path Remote Defect Indication failure (default)  
ptim—Path Trace Indicator Mismatch failure (default)  
puneq—Path Label Equivalent to Zero failure (default)  
Router(config-if)# pos trigger  
delaymillisecond  
Step 3  
Sets waiting period before the line protocol of the interface  
goes down. Delay can be set from 200 to 2000 ms. If no time  
intervals are specified, the default delay is set to 200 ms.  
Router(config-if)# end  
Step 4  
Step 5  
Returns to the privileged EXEC mode.  
Router# copy running-config  
startup-config  
(Optional) Saves configuration changes to NVRAM.  
Monitoring and Verifying POS  
Showing the outputs framing mode and concatenation information with the show controller pos [0 | 1]  
command (Example 6-1).  
Example 6-1 Showing Framing Mode and Concatenation Information with the show controller pos  
[0 | 1] Command  
ML_Series# show controller pos0  
Interface POS0  
Hardware is Packet Over SONET  
Framing Mode: HDLC  
Concatenation: CCAT  
*************** GFP ***************  
Active Alarms : None  
Active Alarms : None  
LDF  
= 0  
CSF  
= 0  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 6 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 packets congestion drops  
56733042489 input good packets (POS MAC rx)  
4073785395967 input good octets (POS MAC rx)  
56701415757 total output packets, 4059987309747 post-encap bytes  
Carrier delay is 200 msec  
Showing scrambling with the show interface pos [0 | 1] command (Example 6-2).  
Example 6-2 Showing Scrambling with the show interface pos [0 | 1] Command  
ML_Series# show interface pos 0  
POS0 is up, line protocol is down  
Hardware is Packet Over SONET, address is 000b.fcfa.33b0 (bia 000b.fcfa.33b0)  
MTU 1500 bytes, BW 48384 Kbit, DLY 100 usec,  
reliability 255/255, txload 1/255, rxload 1/255  
Encapsulation: Cisco-EoS-LEX, loopback not set  
Keepalive set (10 sec)  
Scramble enabled  
ARP type: ARPA, ARP Timeout 04:00:00  
Last input 22:46:51, output never, output hang never  
Last clearing of "show interface" counters 1w5d  
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: fifo  
Output queue: 0/40 (size/max)  
5 minute input rate 0 bits/sec, 0 packets/sec  
5 minute output rate 0 bits/sec, 0 packets/sec  
777 packets input, 298426 bytes  
Received 0 broadcasts (0 IP multicast)  
0 runts, 0 giants, 0 throttles  
0 parity  
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored  
0 input packets with dribble condition detected  
769 packets output, 296834 bytes, 0 underruns  
0 output errors, 0 applique, 1 interface resets  
0 babbles, 0 late collision, 0 deferred  
0 lost carrier, 0 no carrier  
0 output buffer failures, 0 output buffers swapped out  
0 carrier transitions  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 6 Configuring POS on the ML-Series Card  
Monitoring and Verifying POS  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
6-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
7
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 7-1  
RSTP Features, page 7-9  
Interoperability with IEEE 802.1D STP, page 7-15  
Configuring STP and RSTP Features, page 7-15  
Verifying and Monitoring STP and RSTP Status, page 7-20  
STP Features  
These sections describe how the spanning-tree features work:  
•
•
•
•
•
•
•
•
•
•
•
•
STP Overview, page 7-2  
Supported STP Instances, page 7-2  
Bridge Protocol Data Units, page 7-2  
Election of the Root Switch, page 7-3  
Bridge ID, Switch Priority, and Extended System ID, page 7-4  
Spanning-Tree Timers, page 7-4  
Creating the Spanning-Tree Topology, page 7-5  
Spanning-Tree Interface States, page 7-5  
Spanning-Tree Address Management, page 7-8  
STP and IEEE 802.1Q Trunks, page 7-8  
Spanning Tree and Redundant Connectivity, page 7-8  
Accelerated Aging to Retain Connectivity, page 7-9  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 7 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.  
When you create fault-tolerant internetworks, you must have a loop-free path between all nodes in a  
network. The spanning-tree algorithm calculates the best loop-free path throughout a switched Layer 2  
network. Switches send and receive spanning-tree frames, called bridge protocol data units (BPDUs), at  
regular intervals. The switches do not forward these frames, but use the frames to construct a loop-free  
path.  
Multiple active paths among end stations cause loops in the network. If a loop exists in the network, end  
stations might receive duplicate messages. Switches might also learn end-station MAC addresses on  
multiple Layer 2 interfaces. These conditions result in an unstable network.  
Spanning tree defines a tree with a root switch and a loop-free path from the root to all switches in the  
Layer 2 network. Spanning tree forces redundant data paths into a standby (blocked) state. If a network  
segment in the spanning tree fails and a redundant path exists, the spanning-tree algorithm recalculates  
the spanning-tree topology and activates the standby path.  
When two interfaces on a switch are part of a loop, the spanning-tree port priority and path cost settings  
determine which interface is put in the forwarding state and which is put in the blocking state. The port  
priority value represents the location of an interface in the network topology and how well it is located  
to pass traffic. The path cost value represents media speed.  
Supported STP Instances  
The ML-Series card supports the per-VLAN spanning tree (PVST+) and a maximum of  
255 spanning-tree instances.  
Caution  
At more than 100 STP instances the STP instances may flap and may result in MAC entries flushed, and  
MAC entries learned again and again. This will cause flooding in the network. So it is recommended to  
keep the STP instances to be less than 100, to keep system from being unstable.  
Bridge Protocol Data Units  
The stable, active, spanning-tree topology of a switched network is determined by these elements:  
•
•
•
Unique bridge ID (switch priority and MAC address) associated with each VLAN on each switch  
Spanning-tree path cost to the root switch  
Port identifier (port priority and MAC address) associated with each Layer 2 interface  
When the switches in a network are powered up, each functions as the root switch. Each switch sends a  
configuration BPDU through all of its ports. The BPDUs communicate and compute the spanning-tree  
topology. Each configuration BPDU contains this information:  
•
•
•
Unique bridge ID of the switch that the sending switch identifies as the root switch  
Spanning-tree path cost to the root  
Bridge ID of the sending switch  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 7 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. If this BPDU is received on the root port of  
the switch, the switch also forwards it with an updated message to all attached LANs for which it is the  
designated switch.  
If a switch receives a configuration BPDU that contains inferior information to that currently stored for  
that port, it discards the BPDU. If the switch is a designated switch for the LAN from which the inferior  
BPDU was received, it sends that LAN a BPDU containing the up-to-date information stored for that  
port. In this way, inferior information is discarded, and superior information is propagated on the  
network.  
A BPDU exchange results in these actions:  
•
•
One switch in the network is elected as the root switch.  
A root port is selected for each switch (except the root switch). This port provides the best path  
(lowest cost) when the switch forwards packets to the root switch.  
•
•
The shortest distance to the root switch is calculated for each switch based on the path cost.  
A designated switch for each LAN segment is selected. The designated switch incurs the lowest path  
cost when forwarding packets from that LAN to the root switch. The port through which the  
designated switch is attached to the LAN is called the designated port.  
•
•
Interfaces included in the spanning-tree instance are selected. Root ports and designated ports are  
put in the forwarding state.  
All interfaces not included in the spanning tree are blocked.  
Election of the Root Switch  
All switches in the Layer 2 network participating in the spanning tree gather information about other  
switches in the network through an exchange of BPDU data messages. This exchange of messages results  
in these actions:  
•
•
•
Election of a unique root switch for each spanning-tree instance  
Election of a designated switch for every switched LAN segment  
Removal of loops in the switched network by blocking Layer 2 interfaces connected to redundant  
links  
For each VLAN, the switch with the highest switch priority (the lowest numerical priority value) is  
elected as the root switch. If all switches are configured with the default priority (32768), the switch with  
the lowest MAC address in the VLAN becomes the root switch. The switch priority value occupies the  
most significant bits of the bridge ID.  
When you change the switch priority value, you change the probability that the switch will be elected as  
the root switch. Configuring a higher value decreases the probability; a lower value increases the  
probability.  
The root switch is the logical center of the spanning-tree topology in a switched network. All paths that  
are not needed to reach the root switch from anywhere in the switched network are placed in the  
spanning-tree blocking mode.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 7 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.1D standard requires that each switch has an unique bridge identifier (bridge ID), which  
determines the selection of the root switch. Because each VLAN is considered as a different  
logical bridge with PVST+, the same switch must have as many different bridge IDs as VLANs  
configured on it. Each VLAN on the switch has a unique 8-byte bridge ID; the two most-significant bytes  
are used for the switch priority, and the remaining six bytes are derived from the switch MAC address.  
The ML-Series card supports the IEEE 802.1T spanning-tree extensions, and some of the bits previously  
used for the switch priority are now used as the bridge ID. The result is that fewer MAC addresses are  
reserved for the switch, and a larger range of VLAN IDs can be supported, all while maintaining the  
uniqueness of the bridge ID. As shown in Table 7-1, the two bytes previously used for the switch priority  
are reallocated into a 4-bit priority value and a 12-bit extended system ID value equal to the bridge ID.  
In earlier releases, the switch priority is a 16-bit value.  
Table 7-1  
Switch Priority Value and Extended System ID  
Switch Priority Value  
Bit 16 Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1  
32768 16384 8192 4096 2048 1024 512 256 128 64 32 16  
Extended System ID (Set Equal to the Bridge ID)  
8
4
2
1
Spanning tree uses the extended system ID, the switch priority, and the allocated spanning-tree MAC  
address to make the bridge ID unique for each VLAN.  
Spanning-Tree Timers  
Table 7-2 describes the timers that affect the entire spanning-tree performance.  
Table 7-2  
Spanning-Tree Timers  
Variable  
Description  
Hello timer  
When this timer expires, the interface sends out a Hello message to the  
neighboring nodes.  
Forward-delay timer  
Maximum-age timer  
Determines how long each of the listening and learning states last before the  
interface begins forwarding.  
Determines the amount of time the switch stores protocol information  
received on an interface.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
STP Features  
Creating the Spanning-Tree Topology  
In Figure 7-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. By  
increasing the priority (lowering the numerical value) of the ideal switch so that it becomes the root  
switch, you force a spanning-tree recalculation to form a new topology with the ideal switch as the root.  
Figure 7-1  
Spanning-Tree Topology  
ML-Series  
ML-Series  
DP  
DP  
A
D
DP  
RP DP DP  
DP  
RP  
DP  
RP  
B
C
ML-Series  
ML-Series  
RP = root port  
DP = designated port  
When the spanning-tree topology is calculated based on default parameters, the path between source and  
destination end stations in a switched network might not be ideal. For instance, connecting higher-speed  
links to an interface that has a higher number than the root port can cause a root-port change. The goal  
is to make the fastest link the root port.  
Spanning-Tree Interface States  
Propagation delays can occur when protocol information passes through a switched LAN. As a result,  
topology changes can take place at different times and at different places in a switched network. When  
an interface transitions directly from nonparticipation in the spanning-tree topology to the forwarding  
state, it can create temporary data loops. Interfaces must wait for new topology information to propagate  
through the switched LAN before starting to forward frames. They must allow the frame lifetime to  
expire for forwarded frames that have used the old topology.  
Each Layer 2 interface on a switch using spanning tree exists in one of these states:  
•
•
Blocking—The interface does not participate in frame forwarding.  
Listening—The first transitional state after the blocking state when the spanning tree determines  
that the interface should participate in frame forwarding.  
•
•
•
Learning—The interface prepares to participate in frame forwarding.  
Forwarding—The interface forwards frames.  
Disabled—The interface is not participating in spanning tree because of a shutdown port, no link on  
the port, or no spanning-tree instance running on the port.  
An interface moves through these states:  
1. From initialization to blocking  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 7 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 7-2 illustrates how an interface moves through the states.  
Figure 7-2  
Spanning-Tree Interface States  
Power-on  
initialization  
Blocking  
state  
Listening  
state  
Disabled  
state  
Learning  
state  
Forwarding  
state  
When you power up the switch, STP is enabled by default, and every interface in the switch, VLAN, or  
network goes through the blocking state and the transitory states of listening and learning. Spanning tree  
stabilizes each interface at the forwarding or blocking state.  
When the spanning-tree algorithm places a Layer 2 interface in the forwarding state, this process occurs:  
1. The interface is in the listening state while spanning tree waits for protocol information to transition  
the interface to the blocking state.  
2. While spanning tree waits for the forward-delay timer to expire, it moves the interface to the  
learning state and resets the forward-delay timer.  
3. In the learning state, the interface continues to block frame forwarding as the switch learns  
end-station location information for the forwarding database.  
4. When the forward-delay timer expires, spanning tree moves the interface to the forwarding state,  
where both learning and frame forwarding are enabled.  
Blocking State  
A Layer 2 interface in the blocking state does not participate in frame forwarding. After initialization, a  
BPDU is sent to each interface in the switch. A switch initially functions as the root until it exchanges  
BPDUs with other switches. This exchange establishes which switch in the network is the root or root  
switch. If there is only one switch in the network, no exchange occurs, the forward-delay timer expires,  
and the interfaces move to the listening state. An interface always enters the blocking state after switch  
initialization.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
STP Features  
An interface in the blocking state performs as follows:  
•
•
•
•
Discards frames received on the port  
Discards frames switched from another interface for forwarding  
Does not learn addresses  
Receives BPDUs  
Listening State  
Learning State  
Forwarding State  
Disabled 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.  
An interface in the listening state performs as follows:  
•
•
•
•
Discards frames received on the port  
Discards frames switched from another interface for forwarding  
Does not learn addresses  
Receives BPDUs  
A Layer 2 interface in the learning state prepares to participate in frame forwarding. The interface enters  
the learning state from the listening state.  
An interface in the learning state performs as follows:  
•
•
•
•
Discards frames received on the port  
Discards frames switched from another interface for forwarding  
Learns addresses  
Receives BPDUs  
A Layer 2 interface in the forwarding state forwards frames. The interface enters the forwarding state  
from the learning state.  
An interface in the forwarding state performs as follows:  
•
•
•
•
Receives and forwards frames received on the port  
Forwards frames switched from another port  
Learns addresses  
Receives BPDUs  
A Layer 2 interface in the disabled state does not participate in frame forwarding or in the spanning tree.  
An interface in the disabled state is nonoperational.  
A disabled interface performs as follows:  
•
Forwards frames switched from another interface for forwarding  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
STP Features  
•
•
Learns addresses  
Does not receive BPDUs  
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.1Q Trunks  
When you connect a Cisco switch to a non-Cisco device through an IEEE 802.1Q trunk, the Cisco switch  
uses PVST+ to provide spanning-tree interoperability. PVST+ is automatically enabled on IEEE 802.1Q  
trunks after users assign a protocol to a bridge group. The external spanning-tree behavior on access  
ports and Inter-Switch Link (ISL) trunk ports is not affected by PVST+.  
For more information on IEEE 802.1Q trunks, see Chapter 8, “Configuring VLANs on the ML-Series  
Card.”  
Spanning Tree and Redundant Connectivity  
You can create a redundant backbone with spanning tree by connecting two switch interfaces to another  
device or to two different devices. Spanning tree automatically disables one interface but enables it if  
the other one fails, as shown in Figure 7-3. If one link is high speed and the other is low speed, the  
low-speed link is always disabled. If the speeds are the same, the port priority and port ID are added  
together, and spanning tree disables the link with the lowest value.  
Figure 7-3  
Spanning Tree and Redundant Connectivity  
ML-Series  
ONS 15454  
with ML100T-12  
ML-Series  
Active link  
Blocked link  
Workstations  
You can also create redundant links between switches by using EtherChannel groups. For more  
information, see Chapter 10, “Configuring Link Aggregation on the ML-Series Card.”  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                     
Chapter 7 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. Because these stations could be unreachable  
for 5 minutes or more during a reconfiguration, the address-aging time is accelerated so that station  
addresses can be dropped from the address table and then relearned.  
Because each VLAN is a separate spanning-tree instance, the switch accelerates aging on a per-VLAN  
basis. A spanning-tree reconfiguration on one VLAN can cause the dynamic addresses learned on that  
VLAN to be subject to accelerated aging. Dynamic addresses on other VLANs can be unaffected and  
remain subject to the aging interval entered for the switch.  
RSTP Features  
RSTP provides rapid convergence of the spanning tree. It improves the fault tolerance of the network  
because a failure in one instance (forwarding path) does not affect other instances (forwarding paths).  
The most common initial deployment of RSTP is in the backbone and distribution layers of a Layer 2  
switched network; this deployment provides the highly available network required in a service-provider  
environment.  
RSTP improves the operation of the spanning tree while maintaining backward compatibility with  
equipment that is based on the (original) IEEE 802.1D spanning tree.  
RSTP takes advantage of point-to-point wiring and provides rapid convergence of the spanning tree.  
Reconfiguration of the spanning tree can occur in less than 2 second (in contrast to 50 seconds with the  
default settings in the IEEE 802.1D spanning tree), which is critical for networks carrying  
delay-sensitive traffic such as voice and video.  
These sections describe how RSTP works:  
•
•
•
•
•
•
Supported RSTP Instances, page 7-9  
Port Roles and the Active Topology, page 7-10  
Rapid Convergence, page 7-11  
Synchronization of Port Roles, page 7-12  
Bridge Protocol Data Unit Format and Processing, page 7-13  
Topology Changes, page 7-14  
Supported RSTP Instances  
The ML Series supports per-VLAN rapid spanning tree (PVRST) and a maximum of 255 rapid  
spanning-tree instances.  
Caution  
At more than 100 RSTP instances the RSTP instances may flap and may result in MAC entries flushed,  
and MAC entries learned again and again. This will cause flooding in the network. So it is recommended  
to keep the RSTP instances to be less than 100, to keep system from being unstable.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 7 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 7-3. Then the RSTP assigns one of these port roles to individual ports:  
•
•
Root port—Provides the best path (lowest cost) when the switch forwards packets to the root switch.  
Designated port—Connects to the designated switch, which incurs the lowest path cost when  
forwarding packets from that LAN to the root switch. The port through which the designated switch  
is attached to the LAN is called the designated port.  
•
•
Alternate port—Offers an alternate path toward the root switch to that provided by the current root  
port.  
Backup port—Acts as a backup for the path provided by a designated port toward the leaves of the  
spanning tree. A backup port can exist only when two ports are connected together in a loopback by  
a point-to-point link or when a switch has two or more connections to a shared LAN segment.  
•
Disabled port—Has no role within the operation of the spanning tree.  
A port with the root or a designated port role is included in the active topology. A port with the alternate  
or backup port role is excluded from the active topology.  
In a stable topology with consistent port roles throughout the network, the RSTP ensures that every root  
port and designated port immediately transition to the forwarding state while all alternate and backup  
ports are always in the discarding state (equivalent to blocking in IEEE 802.1D). The port state controls  
the operation of the forwarding and learning processes. Table 7-3 provides a comparison of  
IEEE 802.1D and RSTP port states.  
Table 7-3  
Port State Comparison  
Is Port Included in the  
Active Topology?  
Operational Status  
Enabled  
STP Port State  
Blocking  
RSTP Port State  
Discarding  
Discarding  
Learning  
No  
No  
Yes  
Yes  
No  
Enabled  
Listening  
Learning  
Enabled  
Enabled  
Forwarding  
Disabled  
Forwarding  
Discarding  
Disabled  
Caution  
STP edge ports are bridge ports that do not need STP enabled, where loop protection is not needed out  
of that port or an STP neighbor does not exist out of that port. For RSTP, it is important to disable STP  
on edge ports, which are typically front-side Ethernet ports, using the command bridge  
bridge-group-number spanning-disabled on the appropriate interface. If RSTP is not disabled on edge  
ports, convergence times will be excessive for packets traversing those ports.  
Note  
To be consistent with Cisco STP implementations, Table 7-3 describes the port state as blocking instead  
of discarding. Designated ports start in the listening state.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 7 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.  
•
Point-to-point links—If you connect a port to another port through a point-to-point link and the local  
port becomes a designated port, it negotiates a rapid transition with the other port by using the  
proposal-agreement handshake to ensure a loop-free topology.  
As shown in Figure 7-4, Switch A is connected to Switch B through a point-to-point link, and all of the  
ports are in the blocking state. Assume that the priority of Switch A is a smaller numerical value than  
the priority of Switch B. Switch A sends a proposal message (a configuration BPDU with the proposal  
flag set) to Switch B, proposing itself as the designated switch.  
After receiving the proposal message, Switch B selects as its new root port the port from which the  
proposal message was received, forces all non-edge ports to the blocking state, and sends an agreement  
message (a BPDU with the agreement flag set) through its new root port.  
After receiving an agreement message from Switch B, Switch A also immediately transitions its  
designated port to the forwarding state. No loops in the network are formed because Switch B blocked  
all of its non-edge ports and because there is a point-to-point link between Switches A and B.  
When Switch C is connected to Switch B, a similar set of handshaking messages are exchanged. Switch  
C selects the port connected to Switch B as its root port, and both ends immediately transition to the  
forwarding state. With each iteration of this handshaking process, one more switch joins the active  
topology. As the network converges, this proposal-agreement handshaking progresses from the root  
toward the leaves of the spanning tree.  
The switch determines the link type from the port duplex mode: a full-duplex port is considered to have  
a point-to-point connection; a half-duplex port is considered to have a shared connection.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
RSTP Features  
Figure 7-4  
Proposal and Agreement Handshaking for Rapid Convergence  
ML-Series  
ML-Series  
Proposal  
Switch A  
Root  
Switch B  
ML-Series  
Agreement  
F
F
DP  
RP  
Switch A  
Root  
Switch B  
ML-Series  
ML-Series  
Proposal  
F
F
DP  
RP  
Switch A  
Root  
Switch B  
Switch B  
ML-Series  
ML-Series  
Agreement  
F
F
F
F
DP  
RP  
DP  
RP  
Switch A  
Switch B  
Switch B  
DP = designated port  
RP = root port  
F = forwarding  
Synchronization of Port Roles  
When the switch receives a proposal message on one of its ports and that port is selected as the new root  
port, the RSTP forces all other ports to synchronize with the new root information. The switch is  
synchronized with superior root information received on the root port if all other ports are synchronized.  
If a designated port is in the forwarding state, it transitions to the blocking state when the RSTP forces  
it to synchronize with new root information. In general, when the RSTP forces a port to synchronize with  
root information and the port does not satisfy any of the above conditions, its port state is set to blocking.  
After ensuring all of the ports are synchronized, the switch sends an agreement message to the designated  
switch corresponding to its root port. When the switches connected by a point-to-point link are in agreement  
about their port roles, the RSTP immediately transitions the port states to forwarding. The sequence of events  
is shown in Figure 7-5.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
RSTP Features  
Figure 7-5  
Sequence of Events During Rapid Convergence  
4. Agreement  
5. Forward  
1. Proposal  
Edge port  
2. Block  
9. Forward  
3. Block  
11. Forward  
8. Agreement  
6. Proposal  
7. Proposal  
10. Agreement  
Root port  
Designated port  
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. A new Length field is set to zero, which means that no version 1 protocol information is  
present. Table 7-4 shows the RSTP flag fields.  
Table 7-4  
RSTP BPDU Flags  
Bit  
0
Function  
Topology change (TC)  
1
Proposal  
Port role:  
2–3:  
00  
01  
10  
11  
4
Unknown  
Alternate port  
Root port  
Designated port  
Learning  
5
Forwarding  
6
Agreement  
7
Topology change acknowledgement  
The sending switch sets the proposal flag in the RSTP BPDU to propose itself as the designated switch  
on that LAN. The port role in the proposal message is always set to the designated port.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 7 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.  
The learning and forwarding flags are set according to the state of the sending port.  
Processing Superior BPDU Information  
If a port receives superior root information (lower bridge ID, lower path cost, etc.) than currently stored  
for the port, the RSTP triggers a reconfiguration. If the port is proposed and is selected as the new root  
port, RSTP forces all the other ports to synchronize.  
If the BPDU received is an RSTP BPDU with the proposal flag set, the switch sends an agreement  
message after all of the other ports are synchronized. If the BPDU is an IEEE 802.1D BPDU, the switch  
does not set the proposal flag and starts the forward-delay timer for the port. The new root port requires  
twice the forward-delay time to transition to the forwarding state.  
If the superior information received on the port causes the port to become a backup or alternate port,  
RSTP sets the port to the blocking state but does not send the agreement message. The designated port  
continues sending BPDUs with the proposal flag set until the forward-delay timer expires, at which time  
the port transitions to the forwarding state.  
Processing Inferior BPDU Information  
If a designated port receives an inferior BPDU (higher bridge ID, higher path cost, etc.) than currently  
stored for the port with a designated port role, it immediately replies with its own information.  
Topology Changes  
This section describes the differences between the RSTP and the IEEE 802.1D in handling spanning-tree  
topology changes.  
•
Detection—Unlike IEEE 802.1D, in which any transition between the blocking and the forwarding  
state causes a topology change, only transitions from the blocking to the forwarding state cause a  
topology change with RSTP. (Only an increase in connectivity is considered a topology change.)  
State changes on an edge port do not cause a topology change. When an RSTP switch detects a  
topology change, it flushes the learned information on all of its non-edge ports.  
•
•
Notification—Unlike IEEE 802.1D, which uses TCN BPDUs, the RSTP does not use them.  
However, for IEEE 802.1D interoperability, an RSTP switch processes and generates TCN BPDUs.  
Acknowledgement—When an RSTP switch receives a TCN message on a designated port from an  
IEEE 802.1D switch, it replies with an IEEE 802.1D configuration BPDU with the topology change  
acknowledgement bit set. However, if the timer (the same as the topology-change timer in  
IEEE 802.1D) is active on a root port connected to an IEEE 802.1D switch and a configuration  
BPDU with the topology change acknowledgement bit set is received, the timer is reset.  
This behavior is only required to support IEEE 802.1D switches. The RSTP BPDUs never have the  
topology change acknowledgement bit set.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 7 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.  
Protocol migration—For backward compatibility with IEEE 802.1D switches, RSTP selectively  
sends IEEE 802.1D configuration BPDUs and TCN BPDUs on a per-port basis.  
When a port is initialized, the timer is started (which specifies the minimum time during which  
RSTP BPDUs are sent), and RSTP BPDUs are sent. While this timer is active, the switch processes  
all BPDUs received on that port and ignores the protocol type.  
If the switch receives an IEEE 802.1D BPDU after the port’s migration-delay timer has expired, it  
assumes that it is connected to an IEEE 802.1D switch and starts using only IEEE 802.1D BPDUs.  
However, if the RSTP switch is using IEEE 802.1D BPDUs on a port and receives an RSTP BPDU  
after the timer has expired, it restarts the timer and starts using RSTP BPDUs on that port.  
Interoperability with IEEE 802.1D STP  
A switch running RSTP supports a built-in protocol migration mechanism that enables it to interoperate  
with legacy IEEE 802.1D switches. If this switch receives a legacy IEEE 802.1D configuration BPDU  
(a BPDU with the protocol version set to 0), it sends only IEEE 802.1D BPDUs on that port.  
However, the switch does not automatically revert to the RSTP mode if it no longer receives  
IEEE 802.1D BPDUs because it cannot determine whether the legacy switch has been removed from the  
link unless the legacy switch is the designated switch. Also, a switch might continue to assign a boundary  
role to a port when the switch to which this switch is connected has joined the region.  
Configuring STP and RSTP Features  
These sections describe how to configure spanning-tree features:  
•
•
•
•
•
•
•
•
•
Default STP and RSTP Configuration, page 7-16  
Disabling STP and RSTP, page 7-16  
Configuring the Root Switch, page 7-17  
Configuring the Port Priority, page 7-17  
Configuring the Path Cost, page 7-18  
Configuring the Switch Priority of a Bridge Group, page 7-18  
Configuring the Hello Time, page 7-19  
Configuring the Forwarding-Delay Time for a Bridge Group, page 7-20  
Configuring the Maximum-Aging Time for a Bridge Group, page 7-20  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
Configuring STP and RSTP Features  
Default STP and RSTP Configuration  
Table 7-5 shows the default STP and RSTP configuration.  
Table 7-5  
Default STP and RSTP Configuration  
Feature  
Default Setting  
Enable state  
Up to 255 spanning-tree instances  
can be enabled.  
Switch priority  
32768 + Bridge ID  
Spanning-tree port priority (configurable on a per-interface  
basis—used on interfaces configured as Layer 2 access ports)  
128  
Spanning-tree port cost (configurable on a per-interface basis) 100 Mbps: 19  
10 Mbps: 100  
STS-1: 37  
Hello time  
2 seconds  
15 seconds  
20 seconds  
Forward-delay time  
Maximum-aging time  
Disabling STP and RSTP  
STP is enabled by default on the native VLAN 1 and on all newly created VLANs up to the specified  
spanning-tree limit of 255. Disable STP only if you are sure there are no loops in the network topology.  
Caution  
STP edge ports are bridge ports that do not need STP enabled—where loop protection is not needed out  
of that port or an STP neighbor does not exist out of that port. For RSTP, it is important to disable STP  
on edge ports, which are typically front-side Ethernet ports, using the command bridge  
bridge-group-number spanning-disabled on the appropriate interface. If RSTP is not disabled on edge  
ports, convergence times will be excessive for packets traversing those ports.  
Caution  
When STP is disabled and loops are present in the topology, excessive traffic and indefinite packet  
duplication can drastically reduce network performance.  
Beginning in privileged EXEC mode, follow these steps to disable STP or RSTP on a per-VLAN basis:  
Command  
Purpose  
ML_Series# configure terminal  
Step 1  
Step 2  
Step 3  
Enters the global configuration mode.  
Enters the interface configuration mode.  
Disables STP or RSTP on a per-interface basis.  
ML_Series(config)# interface interface-id  
ML_Series(config-if)# bridge-group  
bridge-group-number spanning disabled  
ML_Series(config-if)# end  
Step 4  
Returns to privileged EXEC mode.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 7 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. For each VLAN, the switch with the lowest bridge ID becomes the root switch for that VLAN.  
Note  
If your network consists of switches that both do and do not support the extended system ID, it is unlikely  
that the switch with the extended system ID support will become the root switch. The extended system  
ID increases the switch priority value every time the bridge ID is greater than the priority of the  
connected switches that are running older software.  
Configuring the Port Priority  
If a loop occurs, spanning tree uses the port priority when selecting an interface to put into the  
forwarding state. You can assign higher priority values (lower numerical values) to interfaces that you  
want selected first, and lower priority values (higher numerical values) that you want selected last. If all  
interfaces have the same priority value, spanning tree puts the interface with the lowest interface number  
in the forwarding state and blocks the other interfaces.  
Beginning in privileged EXEC mode, follow these steps to configure the port priority of an interface:  
Command  
Purpose  
ML_Series# configure terminal  
Step 1  
Step 2  
Enters the global configuration mode.  
ML_Series(config)# interface  
interface-id  
Enters the interface configuration mode, and specifies an  
interface to configure.  
Valid interfaces include physical interfaces and  
port-channel logical interfaces (port-channel  
port-channel-number).  
ML_Series(config-if)# bridge-group  
bridge-group-number priority-value  
Step 3  
Step 4  
Configures the port priority for an interface that is an  
access port.  
For the priority-value, the range is 0 to 255; the default is  
128 in increments of 16. The lower the number, the higher  
the priority.  
ML_Series(config-if)# end  
Return to privileged EXEC mode.  
To return the interface to its default setting, use the no bridge-group id bridge-group-number  
priority-value command.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 7 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. If all interfaces have the same cost value, spanning tree puts the interface with the  
lowest interface number in the forwarding state and blocks the other interfaces.  
Beginning in privileged EXEC mode, follow these steps to configure the cost of an interface:  
Command  
Purpose  
ML_Series# configure terminal  
Step 1  
Step 2  
Enters the global configuration mode.  
ML_Series(config)# interface  
interface-id  
Enters the interface configuration mode and specifies an  
interface to configure.  
Valid interfaces include physical interfaces and port-channel  
logical interfaces (port-channel port-channel-number).  
ML_Series(config-if)#  
bridge-group  
Step 3  
Configures the cost for an interface that is an access port.  
If a loop occurs, spanning tree uses the path cost when selecting  
an interface to place into the forwarding state. A lower path cost  
represents higher-speed transmission.  
bridge-group-number path-cost  
cost  
For cost, the range is 0 to 65535; the default value is derived  
from the media speed of the interface.  
ML_Series(config-if)# end  
Step 4  
Note  
Returns to the privileged EXEC mode.  
The show spanning-tree interface interface-id privileged EXEC command displays information only  
for ports that are in a link-up operative state. Otherwise, you can use the show running-config privileged  
EXEC command to confirm the configuration.  
To return the interface to its default setting, use the no bridge-group bridge-group-number path-cost  
cost command.  
Configuring the Switch Priority of a Bridge Group  
You can configure the switch priority and make it more likely that the switch will be chosen as the root  
switch.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 7 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  
ML_Series# configure terminal  
Step 1  
Step 2  
Enters the global configuration mode.  
Configures the switch priority of a bridge group.  
ML_Series(config)# bridge  
bridge-group-number priority  
priority-number  
For priority, the range is 0 to 61440 in increments of 4096; the  
default is 32768. The lower the number, the more likely the switch  
will be chosen as the root switch.  
The value entered is rounded to the lower multiple of 4096. The  
actual number is computed by adding this number to the bridge  
group number.  
ML_Series(config)# end  
Step 3  
Return to the privileged EXEC mode.  
To return the switch to its default setting, use the no bridge bridge-group-number priority  
priority-number command.  
Configuring the Hello Time  
Change the hello time to configure the interval between the generation of configuration messages by the  
root switch.  
Beginning in privileged EXEC mode, follow these steps to configure the hello time of a bridge group:  
Command  
Purpose  
ML_Series# configure terminal  
Step 1  
Step 2  
Enters global configuration mode.  
ML_Series(config)# bridge  
bridge-group-number hello-time  
seconds  
Configures the hello time of a bridge group. The hello time is  
the interval between the generation of configuration  
messages by the root switch. These messages mean that the  
switch is alive.  
For seconds, the range is 1 to 10; the default is 2.  
ML_Series(config)# end  
Step 3  
Returns to privileged EXEC mode.  
To return the switch to its default setting, use the no bridge bridge-group-number hello-time seconds  
command. The number for seconds should be the same number as configured in the original command.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 7 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  
ML_Series# configure  
terminal  
Step 1  
Step 2  
Enters global configuration mode.  
ML_Series(config)# bridge  
bridge-group-number  
forward-time seconds  
Configures the forward time of a VLAN. The forward delay is the  
number of seconds a port waits before changing from its  
spanning-tree learning and listening states to the forwarding state.  
For seconds, the range is 4 to 200; the default is 15.  
ML_Series(config)# end  
Step 3  
Returns to privileged EXEC mode.  
To return the switch to its default setting, use the no bridge bridge-group-number forward-time seconds  
command. The number for seconds should be the same number as configured in the original command.  
Configuring the Maximum-Aging Time for a Bridge Group  
Beginning in privileged EXEC mode, follow these steps to configure the maximum-aging time for a  
bridge group:  
Command  
Purpose  
ML_Series# configure  
terminal  
Step 1  
Step 2  
Enters global configuration mode.  
ML_Series(config)# bridge  
bridge-group-number max-age  
seconds  
Configures the maximum-aging time of a bridge group. The  
maximum-aging time is the number of seconds a switch waits  
without receiving spanning-tree configuration messages before  
attempting a reconfiguration.  
For seconds, the range is 6 to 200; the default is 20.  
ML_Series(config)# end  
Step 3  
Returns to privileged EXEC mode.  
To return the switch to its default setting, use the no bridge bridge-group-number max-age seconds  
command. The number for seconds should be the same number as configured in the original command.  
Verifying and Monitoring STP and RSTP Status  
To display the STP or RSTP status, use one or more of the privileged EXEC commands in Table 7-6.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
Chapter 7 Configuring STP and RSTP on the ML-Series Card  
Verifying and Monitoring STP and RSTP Status  
Table 7-6  
Commands for Displaying Spanning-Tree Status  
Purpose  
Command  
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.  
ML_Series# show spanning-tree  
summary[totals]  
Displays a summary of port states or displays the total lines of  
the STP or RSTP state section.  
Note  
The show spanning-tree interface interface-id privileged EXEC command displays information only  
if the port is in a link-up operative state. Otherwise, you can use the show running-config interface  
privileged EXEC command to confirm the configuration.  
Examples of the show spanning-tree privileged EXEC commands are shown here:  
Example 7-1 show spanning-tree Commands  
ML_Series# show spanning-tree brief  
Bridge group 1 is executing the rstp compatible Spanning Tree protocol  
Bridge Identifier has priority 32768, sysid 1, address 000b.fcfa.339e  
Configured hello time 2, max age 20, forward delay 15  
We are the root of the spanning tree  
Topology change flag not set, detected flag not set  
Number of topology changes 1 last change occurred 1w1d ago  
from POS0.1  
Times: hold 1, topology change 35, notification 2  
hello 2, max age 20, forward delay 15  
Timers: hello 0, topology change 0, notification 0, aging 300  
Port 3 (FastEthernet0) of Bridge group 1 is designated disabled  
Port path cost 19, Port priority 128, Port Identifier 128.3.  
Designated root has priority 32769, address 000b.fcfa.339e  
Designated bridge has priority 32769, address 000b.fcfa.339e  
Designated port id is 128.3, designated path cost 0  
Timers: message age 0, forward delay 0, hold 0  
Number of transitions to forwarding state: 0  
Link type is point-to-point by default  
BPDU: sent 0, received 0  
ML_Series# show spanning-tree interface fastethernet 0  
Port 3 (FastEthernet0) of Bridge group 1 is designated disabled  
Port path cost 19, Port priority 128, Port Identifier 128.3.  
Designated root has priority 32769, address 000b.fcfa.339e  
Designated bridge has priority 32769, address 000b.fcfa.339e  
Designated port id is 128.3, designated path cost 0  
Timers: message age 0, forward delay 0, hold 0  
Number of transitions to forwarding state: 0  
Link type is point-to-point by default  
BPDU: sent 0, received 0  
ML_Series# show spanning-tree summary totals  
Switch is in pvst mode  
Root bridge for: Bridge group 1-Bridge group 8  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 7 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 16  
8
0
0
0
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
7-22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
C H A P T E R  
8
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:  
•
•
•
•
Understanding VLANs, page 8-1  
Configuring IEEE 802.1Q VLAN Encapsulation, page 8-2  
IEEE 802.1Q VLAN Configuration, page 8-3  
Monitoring and Verifying VLAN Operation, page 8-5  
Note  
Configuring VLANs is optional. Complete general interface configurations before proceeding with  
configuring VLANs as an optional step.  
Understanding VLANs  
VLANs enable network managers to group users logically rather than by physical location. A VLAN is  
an emulation of a standard LAN that allows secure intragroup data transfer and communication to occur  
without the traditional restraints placed on the network. It can also be considered a broadcast domain  
that is set up within a switch. With VLANs, switches can support more than one subnet (or VLAN) on  
each switch and give routers and switches the opportunity to support multiple subnets on a single  
physical link. A group of devices that belong to the same VLAN, but are part of different LAN segments,  
are configured to communicate as if they were part of the same LAN segment.  
VLANs enable efficient traffic separation and provide excellent bandwidth utilization. VLANs also  
alleviate scaling issues by logically segmenting the physical LAN structure into different subnetworks  
so that packets are switched only between ports within the same VLAN. This can be very useful for  
security, broadcast containment, and accounting.  
ML-Series software supports port-based VLANs and VLAN trunk ports, which are ports that carry the  
traffic of multiple VLANs. Each frame transmitted on a trunk link is tagged as belonging to only one  
VLAN.  
ML-Series software supports VLAN frame encapsulation through the IEEE 802.1Q standard. The  
Cisco Inter-Switch Link (ISL) VLAN frame encapsulation is not supported. ISL frames are broadcast at  
Layer 2 or dropped at Layer 3.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
8-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Chapter 8 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 8-1 shows a network topology in  
which two VLANs span two ONS 15310-CLs with ML-Series cards.  
Figure 8-1  
VLANs Spanning Devices in a Network  
Host station Host station  
VLAN 10  
VLAN 10  
Fast Ethernet 1  
Fast Ethernet 4  
POS 0.10 VLAN 10  
POS 0. 2  
ML-Series  
ML-Series  
VLAN 2  
Fast Ethernet 2  
Fast Ethernet 3  
VLAN 2  
VLAN 2  
Host station  
Host station  
Configuring IEEE 802.1Q VLAN Encapsulation  
You can configure IEEE 802.1Q VLAN encapsulation on either type of ML-Series card interfaces,  
Ethernet or Packet over SONET/SDH (POS). VLAN encapsulation is not supported on POS interfaces  
configured with HDLC encapsulation.  
The native VLAN is always VLAN ID 1 on ML-Series cards. Frames on the native VLAN are normally  
transmitted and received untagged. On an trunk port, all frames from VLANs other than the native  
VLAN are transmitted and received tagged.  
To configure VLANs using IEEE 802.1Q VLAN encapsulation, perform the following procedure,  
beginning in global configuration mode:  
Command  
Purpose  
ML_Series(config)# bridge  
bridge-group-number protocol type  
Step 1  
Step 2  
Step 3  
Step 4  
Step 5  
Assigns a bridge group (VLAN) number and  
define the appropriate spanning tree type.  
ML_Series(config)# interface type number  
Enters interface configuration mode to configure  
the interface.  
ML_Series(config)# interface type  
number.subinterface-number  
Enters subinterface configuration mode to  
configure the subinterface.  
ML_Series(config-subif)# encap dot1q  
vlan-id  
Sets the encapsulation format on the VLAN to  
IEEE 802.1Q.  
ML_Series(config-subif)# bridge-group  
bridge-group-number  
Assigns a network interface to a bridge group.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
8-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 8 Configuring VLANs on the ML-Series Card  
IEEE 802.1Q VLAN Configuration  
Command  
Purpose  
ML_Series(config-subif)# end  
Step 6  
Step 7  
Returns to privileged EXEC mode.  
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. For example, a bridge-group can connect from a VLAN ID subinterface  
to a subinterface with a different VLAN ID, and then frames entering with one VLAN ID can be changed  
to exit with a different VLAN ID. This is know as VLAN translation.  
Note  
Note  
IP routing is enabled by default. To enable bridging, enter the no ip routing or bridge IRB command.  
Native VLAN frames transmitted on the interface are normally untagged. All untagged frames received  
on the interface are associated with the native VLAN, which is always VLAN 1. Use the command  
encapsulation dot1q 1 native.  
IEEE 802.1Q VLAN Configuration  
The VLAN configuration example for the ML-Series card shown in Figure 8-2 depicts the following  
VLANs:  
•
•
•
•
Fast Ethernet subinterface 0.1 is in the IEEE 802.1Q native VLAN 1.  
Fast Ethernet subinterface 0.2 is in the IEEE 802.1Q VLAN 2.  
Fast Ethernet subinterface 0.3 is in the IEEE 802.1Q VLAN 3.  
Fast Ethernet subinterface 0.4 is in the IEEE 802.1Q VLAN 4.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
8-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 8 Configuring VLANs on the ML-Series Card  
IEEE 802.1Q VLAN Configuration  
Figure 8-2  
Bridging IEEE 802.1Q VLANs  
ML-Series  
Router_A  
ML-Series  
Router_B  
POS 0  
POS 0  
SONET/SDH  
Native VLAN 1  
Fast Ethernet 0.1  
Native VLAN 1  
802.1.Q  
802.1.Q  
Fast Ethernet 0.1  
Fast Ethernet 0.2  
Fast Ethernet 0.2  
Fast Ethernet 0.4  
Fast Ethernet 0.4  
Switch  
Switch  
VLAN 4  
VLAN 2  
VLAN 4  
VLAN 2  
Fast Ethernet 0.3  
Host station  
Host station  
Host station  
Host station  
Fast Ethernet 0.3  
VLAN 3  
VLAN 3  
Host station  
Host station  
Example 8-1 shows how to configure VLANs for IEEE 802.1Q VLAN encapsulation. Use this  
configuration for both ML_Series A and ML_Series B.  
Example 8-1 Configure VLANs for IEEE 8021Q VLAN Encapsulation  
no ip routing  
bridge 1 protocol ieee  
bridge 2 protocol ieee  
bridge 3 protocol ieee  
bridge 4 protocol ieee  
!
!
interface FastEthernet0  
!
interface FastEthernet0.1  
encapsulation dot1Q 1 native  
bridge-group 1  
!
interface FastEthernet0.2  
encapsulation dot1Q 2  
bridge-group 2  
!
interface FastEthernet0.3  
encapsulation dot1Q 3  
bridge-group 3  
!
interface FastEthernet0.4  
encapsulation dot1Q 4  
bridge-group 4  
!
interface POS0  
!
interface POS0.1  
encapsulation dot1Q 1 native  
bridge-group 1  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
8-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 8 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 8-2). This command displays information  
on all configured VLANs or on a specific VLAN (by VLAN ID number).  
Example 8-2 Output for show vlans Command  
ML-Series# show vlans 1  
Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)  
vLAN Trunk Interface:  
POS0.1  
This is configured as native Vlan for the following interface(s) :  
POS0  
Protocols Configured:  
Bridging  
Address:  
Bridge Group 1  
Received:  
0
Transmitted:  
0
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
8-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 8 Configuring VLANs on the ML-Series Card  
Monitoring and Verifying VLAN Operation  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
8-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
9
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. Tunneling is a feature designed for service providers who carry traffic of multiple  
customers across their networks and are required to maintain the VLAN and Layer 2 protocol  
configurations of each customer without impacting the traffic of other customers. The ML-Series cards  
support IEEE 802.1Q tunneling (QinQ) and Layer 2 protocol tunneling.  
This chapter contains the following sections:  
•
•
•
•
•
•
Understanding IEEE 802.1Q Tunneling, page 9-1  
Configuring IEEE 802.1Q Tunneling, page 9-4  
Understanding VLAN-Transparent and VLAN-Specific Services, page 9-6  
VLAN-Transparent and VLAN-Specific Services Configuration Example, page 9-7  
Understanding Layer 2 Protocol Tunneling, page 9-9  
Configuring Layer 2 Protocol Tunneling, page 9-9  
Understanding IEEE 802.1Q Tunneling  
Business customers of service providers often have specific requirements for VLAN IDs and the number  
of VLANs to be supported. The VLAN ranges required by different customers in the same  
service-provider network might overlap, and traffic of customers through the infrastructure might be  
mixed. Assigning a unique range of VLAN IDs to each customer would restrict customer configurations  
and could easily exceed the IEEE 802.1Q specification VLAN limit of 4096.  
Using the IEEE 802.1Q tunneling (QinQ) feature, service providers can use a single VLAN to support  
customers who have multiple VLANs. Customer VLAN IDs are preserved and traffic from different  
customers is segregated within the service-provider infrastructure even when they appear to be on the  
same VLAN. The IEEE 802.1Q tunneling expands VLAN space by using a VLAN-in-VLAN hierarchy  
and tagging the tagged packets. A port configured to support IEEE 802.1Q tunneling is called a tunnel  
port. When you configure tunneling, you assign a tunnel port to a VLAN that is dedicated to tunneling.  
Each customer requires a separate VLAN, but that VLAN supports all of the customer’s VLANs.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                       
Chapter 9 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. You assign the tunnel port  
interface to an access VLAN ID unique to each customer (Figure 9-1).  
Figure 9-1  
IEEE 802.1Q Tunnel Ports in a Service-Provider Network  
Customer A  
VLANs 1 to 100  
Customer A  
VLANs 1 to 100  
Fast Ethernet 0  
Fast Ethernet 0  
ML-Series  
Switch_A  
ML-Series  
Switch_B  
Tunnel port  
VLAN 30  
Tunnel port  
VLAN 30  
POS  
0
POS  
0
SONET STS-N  
Tunnel port  
VLAN 40  
Tunnel port  
VLAN 40  
Fast Ethernet 1  
Fast Ethernet 1  
Customer B  
VLANs 1 to 200  
Customer B  
VLANs 1 to 200  
Trunk  
Asymmetric link  
Packets coming from the customer trunk port into the tunnel port on the ML-Series card are normally  
IEEE 802.1Q-tagged with an appropriate VLAN ID. The tagged packets remain intact inside the  
ML-Series card and, when they exit the trunk port into the service provider network, are encapsulated  
with another layer of an IEEE 802.1Q tag (called the metro tag) that contains the VLAN ID unique to  
the customer. The original IEEE 802.1Q tag from the customer is preserved in the encapsulated packet.  
Therefore, packets entering the service-provider infrastructure are double-tagged, with the outer tag  
containing the customer’s access VLAN ID, and the inner VLAN ID being the VLAN of the incoming  
traffic.  
When the double-tagged packet enters another trunk port in a service provider ML-Series card, the outer  
tag is stripped as the packet is processed inside the switch. When the packet exits another trunk port on  
the same core switch, the same metro tag is again added to the packet. Figure 9-2 shows the structure of  
the double-tagged packet.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card  
Understanding IEEE 802.1Q Tunneling  
Figure 9-2  
Normal, IEEE 802.1Q, and IEEE 802.1Q-Tunneled Ethernet Packet Formats  
Source  
address  
Destination  
Length/  
EtherType  
Frame Check  
Sequence  
address  
Original Ethernet frame  
DA  
SA  
SA  
SA  
Len/Etype  
Data  
FCS  
IEE 802.1Q frame from  
customer network  
DA  
DA  
Etype  
Tag  
Len/Etype  
Data  
FCS  
Etype  
Tag  
Etype  
Tag  
Len/Etype  
Data  
FCS  
Double-tagged  
frame in service  
provider  
infrastructure  
When the packet enters the trunk port of the service-provider egress switch, the outer tag is again  
stripped as the packet is processed internally on the switch. However, the metro tag is not added when it  
is sent out the tunnel port on the edge switch into the customer network, and the packet is sent as a normal  
IEEE 802.1Q-tagged frame to preserve the original VLAN numbers in the customer network.  
In Figure 9-1 on page 9-2, Customer A was assigned VLAN 30, and Customer B was assigned  
VLAN 40. Packets entering the ML-Series card tunnel ports with IEEE 802.1Q tags are double-tagged  
when they enter the service-provider network, with the outer tag containing VLAN ID 30 or 40,  
appropriately, and the inner tag containing the original VLAN number, for example, VLAN 100. Even  
if both Customers A and B have VLAN 100 in their networks, the traffic remains segregated within the  
service-provider network because the outer tag is different. With IEEE 802.1Q tunneling, each customer  
controls its own VLAN numbering space, which is independent of the VLAN numbering space used by  
other customers and the VLAN numbering space used by the service-provider network.  
At the outbound tunnel port, the original VLAN numbers on the customer’s network are recovered. If  
the traffic coming from a customer network is not tagged (native VLAN frames), these packets are  
bridged or routed as if they were normal packets, and the metro tag is added (as a single-level tag) when  
they exit toward the service provider network.  
If the native VLAN (VLAN 1) is used in the service provider network as a metro tag, this tag must always  
be added to the customer traffic, even though the native VLAN ID is not normally added to transmitted  
frames. If the VLAN 1 metro tag is not added on frames entering the service provider network, then the  
customer VLAN tag appears to be the metro tag, with disastrous results. The global configuration vlan  
dot1q tag native command must be used to prevent this by forcing a tag to be added to VLAN 1.  
Avoiding the use of VLAN 1 as a metro tag transporting customer traffic is recommended to reduce the  
risk of misconfiguration. A best practice is to use VLAN 1 as a private management VLAN in the service  
provider network.  
The IEEE 802.1Q class of service (COS) priority field on the added metro tag is set to zero by default,  
but can be modified by input or output policy maps.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 9 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:  
•
•
•
IEEE 802.1Q Tunneling and Compatibility with Other Features, page 9-4  
Configuring an IEEE 802.1Q Tunneling Port, page 9-4  
IEEE 802.1Q Example, page 9-5  
Note  
By default, IEEE 802.1Q tunneling is not configured on the ML-Series.  
IEEE 802.1Q Tunneling and Compatibility with Other Features  
Although IEEE 802.1Q tunneling works well for Layer 2 packet switching, there are incompatibilities  
with some Layer 2 features and with Layer 3 switching:  
•
•
•
A tunnel port cannot be a routed port.  
Tunnel ports do not support IP access control lists (ACLs).  
Layer 3 quality of service (QoS) ACLs and other QoS features related to Layer 3 information are  
not supported on tunnel ports. MAC-based QoS is supported on tunnel ports.  
•
•
•
EtherChannel port groups are compatible with tunnel ports as long as the IEEE 802.1Q  
configuration is consistent within an EtherChannel port group.  
Port Aggregation Protocol (PAgP) and Unidirectional Link Detection (UDLD) Protocol are not  
supported on IEEE 802.1Q tunnel ports.  
Dynamic Trunking Protocol (DTP) is not compatible with IEEE 802.1Q tunneling because you must  
manually configure asymmetric links with tunnel ports and trunk ports.  
•
•
Loopback detection is supported on IEEE 802.1Q tunnel ports.  
When a port is configured as an IEEE 802.1Q tunnel port, spanning tree bridge protocol data unit  
(BPDU) filtering is automatically disabled on the interface.  
Configuring an IEEE 802.1Q Tunneling Port  
Beginning in privileged EXEC mode, follow these steps to configure a port as an IEEE 802.1Q tunnel  
port:  
Command  
Purpose  
ML_Series# configure terminal  
Step 1  
Step 2  
Enters global configuration mode.  
Creates a bridge number and specifies a protocol.  
ML_Series(config)# bridge  
bridge-numberprotocol bridge-protocol  
ML_Series(config)# interface  
fastethernet number  
Step 3  
Enters the interface configuration mode and the interface to be  
configured as a tunnel port. This should be the edge port in the  
service-provider network that connects to the customer switch. Valid  
interfaces include physical interfaces and port-channel logical  
interfaces.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 9 Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card  
Configuring IEEE 802.1Q Tunneling  
Command  
Purpose  
ML_Series(config-if)# bridge-group  
vlan-number  
Step 4  
Step 5  
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.  
ML_Series(config-if)# mode  
dot1q-tunnel  
Sets the interface as an IEEE 802.1Q tunnel port to enable QinQ.  
ML_Series(config)# end  
Step 6  
Step 7  
Step 8  
Returns to privileged EXEC mode.  
ML_Series# show dot1q-tunnel  
Displays the tunnel ports on the switch.  
(Optional) Saves your entries in the configuration file.  
ML_Series# copy running-config  
startup-config  
Note  
Note  
The VLAN ID (VID) range of 2 to 4095 is recommended for IEEE 802.1Q tunneling on the ML-Series  
card.  
If VID 1 is required to be used as a metro tag, use the VLAN dot1Q tag native global configuration  
command.  
Use the no mode dot1q-tunnel interface configuration command to remove the IEEE 802.1Q tunnel  
from the interface.  
IEEE 802.1Q Example  
The following examples show how to configure the example in Figure 9-1 on page 9-2. Example 9-1  
applies to ML_Series A, and Example 9-2 applies to ML_Series B.  
Example 9-1 ML_Series A 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.2  
encapsulation dot1Q 40  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 9 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 9-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.2  
encapsulation dot1Q 40  
bridge-group 40  
Understanding VLAN-Transparent and VLAN-Specific Services  
The ML-Series card supports combining VLAN-transparent services and one or more VLAN-specific  
services on the same port. All of these VLAN-transparent and VLAN-specific services can be  
point-to-point or multipoint-to-multipoint.  
This allows a service provider to combine a VLAN-transparent service, such as IEEE 802.1Q tunneling  
(QinQ), with VLAN-specific services, such as bridging specific VLANs, on the same customer port. For  
example, one customer VLAN can connect to Internet access and the other customer VLANs can be  
tunneled over a single provider VLAN to another customer site, all over a single port at each site.  
Table 9-1 outlines the differences between VLAN-transparent and VLAN-specific services.  
Table 9-1  
VLAN-Transparent Service Versus VLAN-Specific Services  
VLAN-Transparent Services  
Bridging only  
VLAN-Specific Services  
Bridging or routing  
One service per port  
Up to 254 VLAN-specific services per port  
Applies only to specified VLANs  
Applies indiscriminately to all VLANs on the  
physical interface  
Note  
VLAN-transparent service is also referred to as Ethernet Wire Service (EWS). VLAN-specific service  
is also referred to as QinQ tunneling trunk UNI in Metro Ethernet terminology.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 9 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.1Q tunneling, configure this VLAN-transparent service in the normal manner (see the  
“Configuring IEEE 802.1Q Tunneling” section on page 9-4).  
A VLAN-specific service can be any service normally applicable to a VLAN. To configure an ERMS  
VLAN-specific service, configure the service in the normal manner.  
VLAN-Transparent and VLAN-Specific Services Configuration  
Example  
In this example, the Fast Ethernet interface 0 on both the ML-Series card A and ML-Series card C are  
the trunk ports in an IEEE 802.1Q tunnel, which is a VLAN-transparent service. VLAN 10 is used for  
the VLAN-transparent service, which would normally transport all customer VLANs on the  
ML-Series card A’s Fast Ethernet interface 0. All unspecified VLANs and VLAN 1 would also be  
tunneled across VLAN 10.  
VLAN 30 is prevented from entering the VLAN-transparent service and is instead forwarded on a  
specific-VLAN service, bridging Fast Ethernet interface 0 on ML-Series card A and Fast Ethernet  
interface 0 on ML-Series card B. Figure 9-3 is a reference for Example 9-3, Example 9-4 on page 9-8,  
and Example 9-5 on page 9-8.  
Figure 9-3  
ERMS Example  
802.1Q Tunnel on VLAN 10  
802.1Q Tunnel on VLAN 10  
Fast Ethernet Interface 0  
ML-Series Card C  
Fast Ethernet Interface 0  
ML-Series Card A  
VLANs 0-29 and 31-4095  
VLAN 30  
VLANs 0-29 and 31-4095  
ML-Series Card B  
VLAN 30  
Example 9-3 applies to ML-Series card A.  
Example 9-3 ML-Series Card A Configuration  
hostname ML-A  
no ip routing  
bridge 10 protocol rstp  
bridge 30 protocol ieee  
!
!
interface FastEthernet0  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 9 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 9-4 applies to ML-Series card B.  
Example 9-4 ML-Series Card B Configuration  
hostname ML-B  
!
bridge 10 protocol rstp  
bridge 30 protocol ieee  
!
!
interface FastEthernet0  
!
interface FastEthernet0.3  
encapsulation dot1Q 30  
bridge-group 30  
!
interface FastEthernet1  
shutdown  
!
interface POS0.1  
encapsulation dot1Q 10  
bridge-group 10  
!
interface POS0.3  
encapsulation dot1Q 30  
bridge-group 30  
!
interface POS1.1  
encapsulation dot1Q 10  
bridge-group 10  
!
interface POS1.3  
encapsulation dot1Q 30  
bridge-group 30  
Example 9-5 applies to ML-Series card C.  
Example 9-5 ML-Series Card C Configuration  
hostname ML-C  
bridge 10 protocol rstp  
!
!
interface FastEthernet0  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 9 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.1  
encapsulation dot1Q 10  
no ip route-cache  
bridge-group 10  
Understanding Layer 2 Protocol Tunneling  
Customers at different sites connected across a service-provider network need to run various Layer 2  
protocols to scale their topology to include all remote sites, as well as the local sites. Spanning Tree  
Protocol (STP) must run properly, and every VLAN should build a proper spanning tree that includes the  
local site and all remote sites across the service-provider infrastructure. Cisco Discovery Protocol (CDP)  
must discover neighboring Cisco devices from local and remote sites. VLAN Trunking Protocol (VTP)  
must provide consistent VLAN configuration throughout all sites in the customer network.  
When protocol tunneling is enabled, edge switches on the inbound side of the service-provider  
infrastructure encapsulate Layer 2 protocol packets with a special MAC address and send them across  
the service-provider network. Core switches in the network do not process these packets, but forward  
them as normal packets. CDP, STP, or VTP Layer 2 protocol data units (PDUs) cross the  
service-provider infrastructure and are delivered to customer switches on the outbound side of the  
service-provider network. Identical packets are received by all customer ports on the same VLANs with  
the following results:  
•
•
•
Users on each of a customer’s sites are able to properly run STP and every VLAN can build a correct  
spanning tree based on parameters from all sites and not just from the local site.  
CDP discovers and shows information about the other Cisco devices connected through the  
service-provider network.  
VTP provides consistent VLAN configuration throughout the customer network, propagating  
through the service provider to all switches.  
Layer 2 protocol tunneling can be used independently or to enhance IEEE 802.1Q tunneling. If protocol  
tunneling is not enabled on IEEE 802.1Q tunneling ports or on specific VLANs, remote switches at the  
receiving end of the service-provider network do not receive the PDUs and cannot properly run STP,  
CDP, and VTP. When protocol tunneling is enabled, Layer 2 protocols within each customer’s network  
are totally separate from those running within the service-provider network. Customer switches on  
different sites that send traffic through the service-provider network with IEEE 802.1Q tunneling  
achieve complete knowledge of the customer’s VLAN. If IEEE 802.1Q tunneling is not used, you can  
still enable Layer 2 protocol tunneling by connecting to the customer switch through access ports and  
enabling tunneling on the service-provider access port.  
Configuring Layer 2 Protocol Tunneling  
Layer 2 protocol tunneling (by protocol) is enabled on the tunnel ports or on specific tunnel VLANs that  
are connected to the customer by the edge switches of the service-provider network. ML-Series card  
tunnel ports are connected to customer IEEE 802.1Q trunk ports. The ML-Series card supports Layer 2  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 9 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.  
When the Layer 2 PDUs that entered the inbound ML-Series switch through the tunnel port exit the  
switch through the trunk port into the service-provider network, the switch overwrites the customer  
PDU-destination MAC address with a well-known Cisco proprietary multicast address  
(01-00-0c-cd-cd-d0). If IEEE 802.1Q tunneling is enabled, packets are also double-tagged; the outer tag  
is the customer metro tag and the inner tag is the customer VLAN tag. The core switches ignore the inner  
tags and forward the packet to all trunk ports in the same metro VLAN. The ML-Series switches on the  
outbound side restore the proper Layer 2 protocol and MAC address information and forward the  
packets. Therefore, the Layer 2 PDUs are kept intact and delivered across the service-provider  
infrastructure to the other side of the customer network.  
This section contains the following information about configuring Layer 2 protocol tunneling:  
•
•
•
•
•
Default Layer 2 Protocol Tunneling Configuration, page 9-10  
Layer 2 Protocol Tunneling Configuration Guidelines, page 9-10  
Configuring Layer 2 Tunneling on a Port, page 9-11  
Configuring Layer 2 Tunneling Per-VLAN, page 9-12  
Monitoring and Verifying Tunneling Status, page 9-12  
Default Layer 2 Protocol Tunneling Configuration  
Table 9-2 shows the default Layer 2 protocol tunneling configuration.  
Table 9-2  
Default Layer 2 Protocol Tunneling Configuration  
Feature  
Default Setting  
Layer 2 protocol tunneling  
Class of service (CoS) value  
Disabled for CDP, STP, and VTP.  
If a CoS value is configured on the interface for data  
packets, that value is the default used for Layer 2 PDUs. If  
none is configured, there is no default. This allows existing  
CoS values to be maintained, unless the user configures  
otherwise.  
Layer 2 Protocol Tunneling Configuration Guidelines  
These are some configuration guidelines and operating characteristics of Layer 2 protocol tunneling:  
•
The ML-Series card supports Per-VLAN Protocol Tunneling (PVPT), which allows protocol  
tunneling to be configured and run on a specific subinterface (VLAN). PVPT configuration is done  
at the subinterface level.  
•
•
PVPT should be configured on VLANs that carry multi-session transport (MST) BPDUs on the  
connected devices.  
The ML-Series card supports tunneling of CDP and STP (including MSTP and VTP protocols).  
Protocol tunneling is disabled by default but can be enabled for the individual protocols on  
IEEE 802.1Q tunnel ports or on specific VLANs.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 9 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.1Q  
configuration is configured within an EtherChannel port group.  
If an encapsulated PDU (with the proprietary destination MAC address) is received from a tunnel  
port or access port with Layer 2 tunneling enabled, the tunnel port is shut down to prevent loops.  
Only decapsulated PDUs are forwarded to the customer network. The spanning tree instance running  
on the service-provider network does not forward BPDUs to tunnel ports. No CDP packets are  
forwarded from tunnel ports.  
•
•
Because tunneled PDUs (especially STP BPDUs) must be delivered to all remote sites for the  
customer virtual network to operate properly, you can give PDUs higher priority within the  
service-provider network than data packets received from the same tunnel port. By default, the  
PDUs use the same CoS value as data packets.  
Protocol tunneling has to be configured symmetrically at both the ingress and egress point. For  
example, if you configure the entry point to tunnel STP, CDP, and VTP, then you must configure the  
egress point in the same way.  
Configuring Layer 2 Tunneling on a Port  
Beginning in privileged EXEC mode, follow these steps to configure a port as a Layer 2 tunnel port:  
Command  
Purpose  
ML_Series# configuration terminal  
Step 1  
Step 2  
Enters global configuration mode.  
Creates a bridge group number and specifies a protocol.  
ML_Series(config)# bridge  
bridge-group-numberprotocol type  
ML_Series(config)# l2protocol-tunnel cos  
cos-value  
Step 3  
Step 4  
Step 5  
Associates a CoS value with the Layer 2 tunneling port. Valid numbers  
for cos-value range from 0 to 7.  
ML_Series(config)# interface type number  
Enters interface configuration mode for the interface to be configured  
as a tunnel port.  
ML_Series(config-if)# bridge-group  
bridge-group-number  
Assigns a bridge group to the interface.  
ML_Series(config-if)# mode dot1q tunnel  
Step 6  
Step 7  
Sets the interface as an IEEE 802.1Q tunnel VLAN.  
ML_Series(config-if)# l2protocol-tunnel  
{all | cdp | stp | vtp}  
Sets the interface as a Layer 2 protocol tunnel port and enables all  
three protocols or specifically enables CDP, STP, or VTP. These  
protocols are off by default.  
ML_Series(config-if)# end  
Step 8  
Step 9  
Step 10  
Returns to privileged EXEC mode.  
ML_Series# show dot1q-tunnel  
Displays the tunnel ports on the switch.  
(Optional) Saves your entries in the configuration file.  
ML_Series# copy running-config  
startup-config  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 9 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  
ML_Series# configuration terminal  
Step 1  
Step 2  
Enters global configuration mode.  
Creates a bridge group number and specifies a protocol.  
ML_Series(config)# bridge  
bridge-group-numberprotocol type  
ML_Series(config)# l2protocol-tunnel  
cos cos-value  
Step 3  
Step 4  
Associates a CoS value with the Layer 2 tunneling VLAN. Valid  
numbers for cos-value range from 0 to 7.  
ML_Series(config)# interface type  
number.subinterface-number  
Enters subinterface configuration mode and the subinterface to be  
configured as a tunnel VLAN.  
ML_Series(config-subif)# encapsulation  
dot1q bridge-group-number  
Step 5  
Step 6  
Sets the subinterface as an IEEE 802.1Q tunnel VLAN.  
ML_Series(config-subif)# bridge-group  
bridge-group-number  
Specifies the default VLAN, which is used if the subinterface stops  
trunking. This VLAN ID is specific to the particular customer.  
ML_Series(config-subif)# end  
Step 7  
Step 8  
Returns to privileged EXEC mode.  
ML_Series# copy running-config  
startup-config  
(Optional) Saves your entries in the configuration file.  
Monitoring and Verifying Tunneling Status  
Table 9-3 shows the privileged EXEC commands for monitoring and maintaining IEEE 802.1Q and  
Layer 2 protocol tunneling.  
Table 9-3  
Commands for Monitoring and Maintaining Tunneling  
Command  
Purpose  
show dot1q-tunnel  
Displays IEEE 802.1Q tunnel ports on the switch.  
Verifies if a specific interface is a tunnel port.  
show dot1q-tunnel interface interface-id  
show l2protocol-tunnel  
Displays information about Layer 2 protocol  
tunneling ports.  
show vlan dot1q tag native  
Displays IEEE 802.1Q tunnel information.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
9-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
C H A P T E R  
10  
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.  
This chapter contains the following major sections:  
•
•
•
•
Understanding Link Aggregation, page 10-1  
Configuring Link Aggregation, page 10-2  
Understanding Encapsulation over FEC or POS Channel, page 10-6  
Monitoring and Verifying EtherChannel and POS, page 10-8  
Understanding Link Aggregation  
The ML-Series card offers both EtherChannel and POS channel. Traditionally EtherChannel is a  
trunking technology that groups together multiple full-duplex IEEE 802.3 Ethernet interfaces to provide  
fault-tolerant high-speed links between switches, routers, and servers. EtherChannel forms a single  
higher bandwidth routing or bridging endpoint and was designed primarily for host-to-switch  
connectivity. The ML-Series card extends this link aggregation technology to bridged POS interfaces.  
POS channel is only supported with LEX encapsulation.  
Link aggregation provides the following benefits:  
•
•
•
Logical aggregation of bandwidth  
Load balancing  
Fault tolerance  
Port channel is a term for both POS channel and EtherChannel. The port channel interface is treated as  
a single logical interface although it consists of multiple interfaces. Each port channel interfaces consists  
of one type of interface, either Fast Ethernet or POS. You must perform all port channel configurations  
on the port channel (EtherChannel or POS channel) interface rather than on the individual member  
Ethernet or POS interfaces. You can create the port channel interface by entering the interface  
port-channel interface configuration command.  
Port channel connections are fully compatible with IEEE 802.1Q trunking and routing technologies.  
IEEE 802.1Q trunking can carry multiple VLANs across a port channel.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 10 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  
Caution  
The EtherChannel interface is the Layer 2/Layer 3 interface. Do not enable Layer 3 addresses on the  
physical interfaces. Do not assign bridge groups on the physical interfaces because doing so creates  
loops.  
Before a physical interface is removed from an EtherChannel (port channel) interface, the physical  
interface must be disabled. To disable a physical interface, use the shutdown command in interface  
configuration mode.  
Note  
Note  
Note  
Link aggregation across multiple ML-Series cards is not supported.  
Policing is not supported on port channel interfaces.  
The ML-Series does not support the routing of Subnetwork Access Protocol (SNAP) or Inter-Switch  
Link (ISL) encapsulated frames.  
Configuring Link Aggregation  
You can configure an FEC or POS channel by creating an EtherChannel interface (port channel) and  
optionally assigning a network IP address.  
Configuring Fast EtherChannel  
All interfaces that are members of an FEC should have the same link parameters, such as duplex and  
speed.  
To create an EtherChannel interface, perform the following procedure, beginning in global configuration  
mode:  
Command  
Purpose  
Router(config)# interface port-channel  
channel-number  
Step 1  
Step 2  
Creates the EtherChannel interface.  
Router(config-if)# ip address ip-address  
subnet-mask  
(Optional) Assigns an IP address and subnet mask  
to the EtherChannel interface.  
Router(config-if)# end  
Step 3  
Step 4  
Exits to privileged EXEC mode.  
Router# copy running-config startup-config  
(Optional) Saves configuration changes to  
NVRAM.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 10 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.  
To assign Ethernet interfaces to the EtherChannel, perform the following procedure, beginning in global  
configuration mode:  
Command  
Purpose  
Router(config)# interface fastethernet  
number  
Step 1  
Step 2  
Enters one of the interface configuration modes to  
configure the Fast Ethernet interface that you want  
to assign to the EtherChannel.  
Router(config-if)# channel-group  
channel-number  
Assigns the Fast Ethernet interface to the  
EtherChannel. The channel number must be the  
same channel number you assigned to the  
EtherChannel interface.  
Router(config-if)# end  
Step 3  
Step 4  
Exits to privileged EXEC mode.  
Router# copy running-config startup-config  
(Optional) Saves configuration changes to  
NVRAM.  
EtherChannel Configuration Example  
Figure 10-1 shows an example of encapsulation over EtherChannel. The associated commands are  
provided in Example 10-1 and Example 10-2.  
Figure 10-1  
Encapsulation over EtherChannel Example  
ML-Series  
Switch_A  
ML-Series  
Switch_B  
POS 0  
SONET STS-N  
POS 0  
bridge-group 1  
bridge-group 1  
Fast Ethernet 1  
Fast Ethernet 1  
Fast Ethernet 0  
Fast Ethernet 0  
Port Channel  
bridge-group 1  
Port-Channel  
bridge-group 1  
Example 10-1 ML_Series A Configuration  
hostname Switch A  
no ip routing  
!
bridge 1 protocol ieee  
!
interface Port-channel 1  
bridge-group 1  
hold-queue 150 in  
!
interface FastEthernet 0  
channel-group 1  
!
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 10 Configuring Link Aggregation on the ML-Series Card  
Configuring Link Aggregation  
interface FastEthernet 1  
channel-group 1  
!
interface POS 0  
bridge-group 1  
Example 10-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 creating a POS channel interface (port channel) and optionally  
assigning an IP address. All POS interfaces that are members of a POS channel should have the same  
port properties and be on the same ML-Series card.  
Note  
POS channel is only supported with G-Series card compatible (LEX) encapsulation.  
To create a POS channel interface, perform the following procedure, beginning in global configuration  
mode:  
Command  
Purpose  
Router(config)# interface port-channel  
channel-number  
Step 1  
Step 2  
Creates the POS channel interface. You can  
configure one POS channel on the ML-Series card.  
Router(config-if)# ip address ip-address  
subnet-mask  
Assigns an IP address and subnet mask to the POS  
channel interface (required only for the Layer 3  
POS channel).  
Router(config-if)# end  
Step 3  
Step 4  
Exits to privileged EXEC mode.  
Router# copy running-config startup-config  
(Optional) Saves configuration changes to  
NVRAM.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 10 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.  
To assign POS interfaces to the POS channel, perform the following procedure, beginning in global  
configuration mode:  
Command  
Purpose  
Router(config)# interface pos number  
Step 1  
Step 2  
Enters the interface configuration mode to  
configure the POS interface that you want to  
assign to the POS channel.  
Router(config-if)# channel-group  
channel-number  
Assigns the POS interface to the POS channel. The  
channel number must be the same channel number  
that you assigned to the POS channel interface.  
Router(config-if)# end  
Step 3  
Step 4  
Exits to privileged EXEC mode.  
Router# copy running-config startup-config  
(Optional) Saves the configuration changes to  
NVRAM.  
POS Channel Configuration Example  
Figure 10-2 shows an example of POS channel configuration. The associated code for ML_Series A is  
provided in Example 10-3 and for ML_Series B in Example 10-4.  
Figure 10-2  
POS Channel Example  
ML_Series A  
ML_Series B  
pos 0  
pos 0  
port-channel 1  
bridge-group 1  
port-channel 1  
bridge-group 1  
bridge-group 1  
pos 1  
bridge-group 1  
pos 1  
SONET STS-N  
bridge-group 1  
bridge-group 1  
Example 10-3 ML_Series A Configuration  
no ip routing  
bridge 1 protocol ieee  
!
!
interface Port-channel1  
no ip address  
bridge-group 1  
!
interface FastEthernet0  
no ip address  
bridge-group 1  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 10 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 10-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 FEC or POS, be sure to configure IEEE 802.1Q on the  
port-channel interface, not its member ports. However, certain attributes of port channel, such as duplex  
mode, need to be configured at the member port levels. Also make sure that you do not apply  
protocol-level configuration (such as an IP address or a bridge group assignment) to the member  
interfaces. All protocol-level configuration should be on the port channel or on its subinterface. You  
must configure IEEE 802.1Q encapsulation on the partner system of the EtherChannel as well.  
Configuring Encapsulation over EtherChannel or POS Channel  
To configure encapsulation over the FEC or POS channel, perform the following procedure, beginning  
in global configuration mode:  
Command  
Purpose  
Router(config)# interface port-channel  
channel-number.subinterface-number  
Step 1  
Step 2  
Step 3  
Configures the subinterface on the created port  
channel.  
Router(config-subif)# encapsulation dot1q  
vlan-id  
Assigns the IEEE 802.1Q encapsulation to the  
subinterface.  
Router(config-subif)# bridge-group  
bridge-group-number  
Assigns the subinterface to a bridge group.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 10 Configuring Link Aggregation on the ML-Series Card  
Understanding Encapsulation over FEC or POS Channel  
Command  
Purpose  
Exits to privileged EXEC mode.  
Router(config-subif)# end  
Step 4  
Note  
Optionally, you can remain in interface  
configuration mode and enable other  
supported interface commands to meet  
your requirements.  
Router# copy running-config startup-config  
Step 5  
(Optional) Saves the configuration changes to  
NVRAM.  
Encapsulation over EtherChannel Example  
Figure 10-3 shows an example of encapsulation over EtherChannel. The associated code for  
ML_Series A is provided in Example 10-5 and for ML_Series B in Example 10-6.  
Figure 10-3  
Encapsulation over EtherChannel Example  
ML-Series  
Switch_A  
ML-Series  
Switch_B  
POS 0  
SONET STS-1  
POS 0  
Fast Ethernet 1  
Fast Ethernet 0  
Fast Ethernet 0  
802.1Q Trunking  
VLANs 1 & 2  
Fast Ethernet 1  
802.1Q Trunking  
VLANs 1 & 2  
This encapsulation over EtherChannel example shows how to set up two ONS 15310-CL nodes or  
ONS 15310-MA nodes with ML-Series cards to interoperate with two switches that also support  
IEEE 802.1Q encapsulation over EtherChannel. To set up this example, use the configurations in the  
following sections for both Switch A and Switch B.  
Example 10-5 ML_Series A Configuration  
hostname ML_Series_A  
!
bridge irb  
bridge 1 protocol ieee  
bridge 2 protocol ieee  
!
interface Port-channel1  
hold-queue 150 in  
!
interface Port-channel1.1  
encapsulation dot1Q 1 native  
bridge-group 1  
!
interface Port-channel1.2  
encapsulation dot1Q 2  
bridge-group 2  
!
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 10 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.2  
encapsulation dot1Q 2  
bridge-group 2  
Example 10-6 ML_Series B Configuration  
hostname ML_Series_B  
!
bridge irb  
bridge 1 protocol ieee  
bridge 2 protocol ieee  
!
interface Port-channel1  
hold-queue 150 in  
!
interface Port-channel1.1  
encapsulation dot1Q 1 native  
bridge-group 1  
!
interface Port-channel1.2  
encapsulation dot1Q 2  
bridge-group 2  
!
interface FastEthernet0  
channel-group 1  
!
interface FastEthernet1  
channel-group 1  
!
interface POS0  
!
interface POS0.1  
encapsulation dot1Q 1 native  
bridge-group 1  
!
interface POS0.2  
encapsulation dot1Q 2  
bridge-group 2  
!
Monitoring and Verifying EtherChannel and POS  
After FEC or POS is configured, you can monitor its status using the show interfaces port-channel  
command.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 10 Configuring Link Aggregation on the ML-Series Card  
Monitoring and Verifying EtherChannel and POS  
Example 10-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.22/25  
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,  
reliability 255/255, txload 1/255, rxload 1/255  
Encapsulation ARPA, loopback not set  
Keepalive set (10 sec)  
ARP type: ARPA, ARP Timeout 04:00:00  
No. of active members in this channel: 0  
Last input never, output never, output hang never  
Last clearing of "show interface" counters never  
Input queue: 0/300/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: fifo  
Output queue: 0/0 (size/max)  
5 minute input rate 0 bits/sec, 0 packets/sec  
5 minute output rate 0 bits/sec, 0 packets/sec  
0 packets input, 0 bytes  
Received 0 broadcasts (0 IP multicast)  
0 runts, 0 giants, 0 throttles  
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored  
0 watchdog, 0 multicast  
0 input packets with dribble condition detected  
0 packets output, 0 bytes, 0 underruns  
0 output errors, 0 collisions, 0 interface resets  
0 babbles, 0 late collision, 0 deferred  
0 lost carrier, 0 no carrier  
0 output buffer failures, 0 output buffers swapped out  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 10 Configuring Link Aggregation on the ML-Series Card  
Monitoring and Verifying EtherChannel and POS  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
10-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
11  
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.  
This chapter includes the following major sections:  
•
•
•
•
Understanding Integrated Routing and Bridging, page 11-1  
Configuring IRB, page 11-2  
IRB Configuration Example, page 11-3  
Monitoring and Verifying IRB, page 11-4  
Caution  
Cisco Inter-Switch Link (ISL) and Cisco Dynamic Trunking Protocol (DTP) are not supported by the  
ML-Series, but the ML-Series broadcast forwards these formats. Using ISL or DTP on connecting  
devices is not recommended. Some Cisco devices attempt to use ISL or DTP by default.  
Understanding Integrated Routing and Bridging  
Your network might require you to bridge local traffic within several segments and have hosts on the  
bridged segments reach the hosts or ML-Series card on routed networks. For example, if you are  
migrating bridged topologies into routed topologies, you might want to start by connecting some of the  
bridged segments to the routed networks.  
Using the integrated routing and bridging (IRB) feature, you can route a given protocol between routed  
interfaces and bridge groups within a single ML-Series card. Specifically, local or unroutable traffic is  
bridged among the bridged interfaces in the same bridge group, while routable traffic is routed to other  
routed interfaces or bridge groups.  
Because bridging is in the data link layer and routing is in the network layer, they have different protocol  
configuration models. With IP, for example, bridge group interfaces belong to the same network and have  
a collective IP network address. In contrast, each routed interface represents a distinct network and has  
its own IP network address. It uses the concept of a Bridge Group Virtual Interface (BVI) to enable these  
interfaces to exchange packets for a given protocol.  
A BVI is a virtual interface within the ML-Series card that acts like a normal routed interface. A BVI  
does not support bridging but actually represents the corresponding bridge group to routed interfaces  
within the ML-Series card. It also gives the user an IP management interface for the bridge group. The  
interface number is the link between the BVI and the bridge group.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
11-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 11 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.  
Protocol attributes should not be configured on the bridged interfaces when you are using IRB to  
bridge and route a given protocol. You can configure protocol attributes on the BVI, but you cannot  
configure bridging attributes on the BVI.  
•
•
A bridge links several network segments into one large, flat network. To bridge a packet coming  
from a routed interface among bridged interfaces, the bridge group should be represented by one  
interface.  
All ports in a BVI group must have matching maximum transmission unit (MTU) settings.  
Configuring IRB  
The process of configuring integrated routing and bridging consists of the following tasks:  
1. Configure bridge groups and routed interfaces.  
a. Enable bridging.  
b. Assign interfaces to the bridge groups.  
c. Configure the routing.  
2. Enable IRB.  
3. Configure the BVI.  
a. Enable the BVI to accept routed packets.  
b. Enable routing on the BVI.  
4. Configure IP addresses on the routed interfaces.  
5. Verify the IRB configuration.  
When you configure the BVI and enable routing on it, packets that come in on a routed interface destined  
for a host on a segment that is in a bridge group are routed to the BVI and forwarded to the bridging  
engine. From the bridging engine, the packet exits through a bridged interface. Similarly, packets that  
come in on a bridged interface but are destined for a host on a routed interface go first to the BVI. The  
BVI forwards the packets to the routing engine that sends them out on the routed interface.  
To configure a bridge group and an interface in the bridge group, perform the following procedure,  
beginning in global configuration mode:  
Command  
Purpose  
ML_Series(config)# bridge bridge-group  
protocol {ieee | rstp}  
Step 1  
Defines one or more bridge groups.  
ML_Series(config)# interface type number  
Step 2  
Step 3  
Enters interface configuration mode.  
ML_Series(config-if)# bridge-group  
bridge-group  
Assigns the interface to the specified bridge  
group.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
11-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 11 Configuring IRB on the ML-Series Card  
IRB Configuration Example  
Command  
Purpose  
ML_Series(config-if)# ip address  
ip-address ip-address-subnet-mask  
Step 4  
Step 5  
Configures IP addresses on routed interfaces.  
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  
ML_Series(config)# bridge irb  
Step 1  
Step 2  
Enables IRB. Allows bridging of traffic.  
ML_Series(config)# interface bvi  
bridge-group  
Configures the BVI by assigning the number of the  
corresponding bridge group to the BVI. Each bridge  
group can have only one corresponding BVI.  
ML_Series(config-if)# ip address  
ip-address ip-address-subnet-mask  
Step 3  
Configures IP addresses on routed interfaces.  
ML_Series(config-if)# exit  
Step 4  
Step 5  
Exits the interface configuration mode.  
ML_Series(config)# bridge bridge-group  
route protocol  
Enables a BVI to accept and route routable packets  
received from its corresponding bridge group.  
Enter this command for each protocol that you want  
the BVI to route from its corresponding bridge  
group to other routed interfaces.  
ML_Series(config)# end  
Step 6  
Step 7  
Returns to the privileged EXEC mode.  
ML_Series# copy running-config  
startup-config  
(Optional) Saves your configuration changes to  
NVRAM.  
IRB Configuration Example  
Figure 11-1 shows an example of IRB configuration. Example 11-1 shows the configuration code for  
ML_Series A, and Example 11-2 shows the configuration code for ML_Series B.  
Figure 11-1  
Configuring IRB  
ML-Series  
BVI 1 192.168.1.1/24  
ML-Series  
BVI 1 192.168.1.2/24  
Router_A  
Router_B  
pos 0  
pos 0  
bridge 1  
bridge 1  
SONET/SDH  
pos 1  
pos 1  
bridge 1  
bridge 1  
fast ethernet 0  
fast ethernet 0  
192.168.3.1/24  
192.168.2.1/24  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
11-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 11 Configuring IRB on the ML-Series Card  
Monitoring and Verifying IRB  
Example 11-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.255 area 0  
Example 11-2 Configuring ML_Series B  
bridge irb  
bridge 1 protocol ieee  
bridge 1 route ip  
!
!
interface FastEthernet0  
ip address 192.168.3.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.2 255.255.255.0  
!
router ospf 1  
log-adjacency-changes  
network 192.168.1.0 0.0.0.255 area 0  
network 192.168.3.0 0.0.0.255 area 0  
Monitoring and Verifying IRB  
Table 11-1 shows the privileged EXEC commands for monitoring and verifying IRB.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
11-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 11 Configuring IRB on the ML-Series Card  
Monitoring and Verifying IRB  
Table 11-1  
Commands for Monitoring and Verifying IRB  
Purpose  
Command  
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.  
Router# show interfaces [type-number] irb  
Shows BVI information for the following:  
•
Protocols that this bridged interface can route to  
the other routed interface (if this packet is  
routable).  
•
Protocols that this bridged interface bridges  
The following is sample output from the show interfaces bvi (Example 11-3) and show interfaces irb  
commands (Example 11-4):  
Example 11-3 show interfaces bvi  
Router# show interfaces bvi 22  
BVI22 is down, line protocol is down  
Hardware is BVI, address is 0012.0101.362c (bia 0000.0000.0000)  
Internet address is 192.192.192.194/24  
MTU 1500 bytes, BW 100000 Kbit, DLY 5000 usec,  
reliability 255/255, txload 1/255, rxload 1/255  
Encapsulation: ARPA, loopback not set  
ARP type: ARPA, ARP Timeout 04:00:00  
Last input never, output never, output hang never  
Last clearing of "show interface" counters never  
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: fifo  
Output queue: 0/0 (size/max)  
5 minute input rate 0 bits/sec, 0 packets/sec  
5 minute output rate 0 bits/sec, 0 packets/sec  
0 packets input, 0 bytes, 0 no buffer  
Received 0 broadcasts (0 IP multicast)  
0 runts, 0 giants, 0 throttles  
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort  
0 packets output, 0 bytes, 0 underruns  
0 output errors, 0 collisions, 0 interface resets  
0 output buffer failures, 0 output buffers swapped out  
Example 11-4 show interfaces irb  
Router# show interfaces irb  
BVI 22  
pkts_error_giants  
0
Hash Len  
Address  
Matches Act  
Type  
pkts_error_runts  
0x00: 0 ffff.ffff.ffff  
pkts_mcast  
0x2B: 0 0012.0101.362a  
align_errors  
0 RCV Physical broadcast  
00 no  
0
0 RCV Interface MAC addressfailures, 0 out  
0 RCV CDPcarrier transitions  
0xC0: 0 0100.0ccc.cccc  
Overruns  
Bridged protocols on POS0:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
11-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 11 Configuring IRB on the ML-Series Card  
Monitoring and Verifying IRB  
clns  
Software MAC address filter on POS0  
Hash Len Address Matches Act  
ip  
Type  
0x00: 0 ffff.ffff.ffff  
0x25: 0 0012.0101.3624  
0x29: 0 0012.0101.3628  
0xC0: 0 0100.0ccc.cccc  
0xC2: 0 0180.c200.0000  
0 RCV Physical broadcast  
0 RCV Interface MAC address  
0 RCV Interface MAC address  
0 RCV CDP  
0 RCV IEEE spanning tree  
POS1  
Bridged protocols on POS1:  
clns ip  
Software MAC address filter on POS1  
Hash Len Address Matches Act  
Type  
0x00: 0 ffff.ffff.ffff  
0x24: 0 0012.0101.3625  
0x29: 0 0012.0101.3628  
0xC0: 0 0100.0ccc.cccc  
0xC2: 0 0180.c200.0000  
0 RCV Physical broadcast  
0 RCV Interface MAC address  
0 RCV Interface MAC address  
0 RCV CDP  
0 RCV IEEE spanning tree  
Table 11-2 describes significant fields shown in the display.  
Table 11-2  
show interfaces irb Field Descriptions  
Field  
Description  
Routed protocols on…  
List of the routed protocols configured for the speci-  
fied interface.  
Bridged protocols on…  
List of the bridged protocols configured for the speci-  
fied interface.  
Software MAC address filter on…  
Table of software MAC address filter information for  
the specified interface.  
Hash  
Len  
Hash key/relative position in the keyed list for this  
MAC-address entry.  
Length of this entry to the beginning element of this  
hash chain.  
Address  
Matches  
Canonical (Ethernet ordered) MAC address.  
Number of received packets matched to this MAC  
address.  
Routed protocols on…  
Bridged protocols on…  
List of the routed protocols configured for the speci-  
fied interface.  
List of the bridged protocols configured for the speci-  
fied interface.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
11-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
C H A P T E R  
12  
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.  
This chapter contains the following major sections:  
•
•
•
•
•
•
•
•
•
•
•
•
•
Understanding QoS, page 12-2  
ML-Series QoS, page 12-4  
QoS on RPR, page 12-9  
Configuring QoS, page 12-10  
Monitoring and Verifying QoS Configuration, page 12-16  
QoS Configuration Examples, page 12-17  
Understanding Multicast QoS and Multicast Priority Queuing, page 12-23  
Configuring Multicast Priority Queuing QoS, page 12-24  
QoS not Configured on Egress, page 12-26  
ML-Series Egress Bandwidth Example, page 12-26  
Understanding CoS-Based Packet Statistics, page 12-28  
Configuring CoS-Based Packet Statistics, page 12-29  
Understanding IP SLA, page 12-30  
The ML-Series card employs the Cisco IOS Modular QoS Command-line Interface (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 at this URL:  
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122mindx/l22index.htm  
•
Cisco IOS Quality of Service Solutions Command Reference, Release 12.2 at this URL:  
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_r/index.htm  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 12 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. To support service-level agreements  
(SLAs), this dynamic allocation must accommodate the service elements of bandwidth, including loss  
and delay. The characteristics of these service elements make up QoS.  
The QoS mechanism has three basic steps. It classifies types of traffic, specifies what action to take  
against a type of traffic, and specifies where the action should take place.  
Priority Mechanism in IP and Ethernet  
For any QoS service to be applied to data, there must be a way to mark or identify an IP packet or an  
Ethernet frame. When identified, a specific priority can be assigned to each individual IP packet or  
Ethernet frame. The IP Precedence or the IP Differentiated Services Code Point (DSCP) field prioritizes  
the IP packets, and the Ethernet class of service (IEEE 802.1p defined class of service [CoS]) is used for  
the Ethernet frames. IP precedence and Ethernet CoS are further described in the following sections.  
IP Precedence and Differentiated Services Code Point  
IP precedence uses the three precedence bits in the IPv4 header’s ToS (type of service) field to specify  
class of service for each IP packet (RFC 1122). The most significant three bits of the IPv4 ToS field  
provide up to eight distinct classes, of which six are used for classifying services and the remaining two  
are reserved. On the edge of the network, the IP precedence is assigned by the client device or the  
ML Series, so that each subsequent network element can provide services based on the determined  
policy or the SLA.  
IP DSCP uses the six bits in the IPv4 header to specify class of service for each IP packet (RFC 2474).  
Figure 12-1 illustrates IP precedence and DSCP. The DSCP field classifies packets into any of the  
64 possible classes. On the network edge, the IP DSCP is assigned by the client device or the ML Series,  
so that each subsequent network element can provide services based on the determined policy or the  
SLA.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Understanding QoS  
Figure 12-1  
IP Precedence and DSCP  
Bits  
0
1
2
3
4
5
6
7
Bits  
0
1
2
3
4
5
6
7
DS-Field  
DSCP  
CU  
Precedence Type of Service  
MBZ  
Class Selector  
Codepoints  
Currently  
Unused  
DTR-Bits  
Must  
be  
zero  
RFC 1122  
RFC 1349  
Differentiated Services Code Point  
AFC 2474  
Bits (0-2): IP-Precedence Defined  
111 (Network Control)  
110 (Internetwork Control)  
101 (CRITIC/ECP)  
100 (Flash Override)  
011 (Flash)  
Bits (3-6): Type of Service Defined  
0000 (all normal)  
1000 (minimize delay)  
0100 (maximize throughput)  
0010 (maximize reliability)  
0001 (minimize monetary cost)  
101 (Immediate)  
001 (Priority)  
000 (Routine)  
Ethernet CoS  
Ethernet CoS refers to three bits within a four byte IEEE 802.1Q (VLAN) header used to indicate the  
priority of the Ethernet frame as it passes through a switched network. The CoS bits in the IEEE 802.1Q  
header are commonly referred to as the IEEE 802.1p bits. There are three CoS bits that provide eight  
classes, matching the number delivered by IP precedence. In many real-world networks, a packet might  
traverse both Layer 2 and Layer 3 domains. To maintain QoS across the network, the IP ToS can be  
mapped to the Ethernet CoS and vice versa, for example, in linear or one-to-one mapping, because each  
mechanism supports eight classes. Similarly, a set of DSCP values (64 classes) can be mapped into each  
of the eight individual Ethernet CoS values. Figure 12-2 is an IEEE 802.1Q Ethernet frame, which  
consists of a 2-byte Ethertype and a 2-byte tag (IEEE 802.1Q Tag) on the Ethernet protocol header.  
Figure 12-2  
Ethernet Frame and the CoS Bit (IEEE 802.1p)  
6
6
2
2
2
Destination Address  
Source Address  
Type=8100  
IEEE 802.1p  
(3 bits)  
Tag Control Information  
Type/Length  
CoS  
CFI  
VLAN ID  
MAC DATA  
IEEE 802.1Q Tag  
PAD  
FCS  
4
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 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 12-3 illustrates the ML-Series QoS flow.  
Figure 12-3  
ML-Series QoS Flow  
QoS Actions at Ingress  
Policing & Marking  
QoS Actions at Egress  
Classification  
Classification  
Queueing & Scheduleing  
Policing provided by the ML-Series card ensures that attached equipment does not submit more than a  
predefined amount of bandwidth (Rate Limiting) into the network. The policing feature can be used to  
enforce the committed information rate (CIR) and the peak information rate (PIR) available to a  
customer at an interface. Policing also helps characterize the statistical nature of the information allowed  
into the network so that traffic engineering can more effectively ensure that the amount of committed  
bandwidth is available on the network, and the peak bandwidth is over-subscribed with an appropriate  
ratio. The policing action is applied per classification.  
Priority marking can set the Ethernet IEEE 802.1p CoS bits or RPR-CoS bits as they exit the ML-Series  
card. The marking feature operates on the outer IEEE 802.1p tag, and provides a mechanism for tagging  
packets at the ingress of a QinQ packet. The subsequent network elements can provide QoS based only  
on this service-provider-created QoS indicator.  
Per-class flow queuing enables fair access to excess network bandwidth, allows allocation of bandwidth  
to support SLAs, and ensures that applications with high network resource requirements are adequately  
served. Buffers are allocated to queues dynamically from a shared resource pool. The allocation process  
incorporates the instantaneous system load as well as the allocated bandwidth to each queue to optimize  
buffer allocation. Congestion management on the ML-Series is performed through a tail drop mechanism  
along with discard eligibility on the egress scheduler.  
The ML-Series uses a Weighted Deficit Round Robin (WDRR) scheduling process to provide fair access  
to excess bandwidth as well as guaranteed throughput to each class flow.  
Admission control is a process that is invoked each time that service is configured on the ML-Series card  
to ensure that QoS resources are not overcommitted. In particular, admission control ensures that no  
configurations are accepted when the sum of committed bandwidths on an interface exceeds the total  
bandwidth on the interface.  
Classification  
Classification can be based on any single packet classification criteria or a combination (logical AND  
and OR). Classification of packets is configured using the Modular CLI class-map command. For traffic  
transiting the RPR, only the input interface and/or the RPR-CoS can be used as classification criteria.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 12 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 12-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. The nonconforming packets of the first bucket are the  
overflow packets, which are passed to the second leaky bucket (the PIR bucket). The second leaky bucket  
is filled with these tokens at a known rate (PIR), which is a parameter that can be configured by the  
operator. The tokens fill the PIR bucket up to a maximum level (BP), which is the amount of peak  
burstable traffic on the policer. The nonconform packets of the second bucket are the overflow packets,  
which can be dropped or marked according to the policer definition.  
On the dual leaky bucket policer, the packets conforming to the CIR are conform packets, the packets  
not conforming to CIR but conforming to PIR are exceed packets, and the packets not conforming to  
either the PIR or CIR are violate packets.  
Figure 12-4  
Dual Leaky Bucket Policer Model  
Tokens  
Bc  
OverflowTokens  
OverflowTokens  
Bp  
No  
No  
Size<Tc  
Size>=Tc+Tp  
Size>=Tc+Tp  
Yes  
Yes  
Yes  
Conform  
Exceed  
Violate  
Remark  
Set DE bit  
Transmit  
Drop  
Queued  
Packets  
Ingress  
Packets  
Marking and Discarding with a Policer  
On the ML-Series card’s policer, the conform packets can be transmitted or marked and transmitted. The  
exceed packets can be transmitted, marked and transmitted, or dropped. The violating packets can be  
transmitted, marked and transmitted, or dropped. The primary application of the dual-rate or three-color  
policer is to mark the conform packets with CoS bit 2l, mark the exceed packet with CoS bit 1, and  
discard the violated packets so all the subsequent network devices can implement the proper QoS  
treatment per frame/packet basis based on these priority marking without knowledge of each SLA.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 12 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. If a marked packet is transported over the RPR  
ring, the marking also affects the RPR-CoS bit.  
If a Q-tag is inserted (QinQ), the marking affects the added Q-tag. If the ingress packet contains a Q-tag  
and is transparently switched, the existing Q-tag is marked. In case of a packet without any Q-tag, the  
marking does not have any significance.  
The local scheduler treats all nonconforming packets as discard eligible regardless of their CoS setting  
or the global cos commit definition. For RPR implementation, the discard eligible (DE) packets are  
marked using the DE bit on the RPR header. The discard eligibility based on the CoS commit or the  
policing action is local to the ML-Series card scheduler, but it is global for the RPR ring.  
Queuing  
ML-Series card queuing uses a shared buffer pool to allocate memory dynamically to different traffic  
queues. The ML-100T-8 has 1.5 MB of packet buffer memory.  
Each queue has an upper limit on the allocated number of buffers based on the class bandwidth  
assignment of the queue and the number of queues configured. This upper limit is typically 30 percent  
to 50 percent of the shared buffer capacity. Dynamic buffer allocation to each queue can be reduced  
based on the number of queues needing extra buffering. The dynamic allocation mechanism provides  
fairness in proportion to service commitments as well as optimization of system throughput over a range  
of system traffic loads.  
The Low Latency Queue (LLQ) is defined by setting the weight to infinity or committing 100 percent  
bandwidth. When a LLQ is defined, a policer should also be defined on the ingress for that specific class  
to limit the maximum bandwidth consumed by the LLQ; otherwise there is a potential risk of LLQ  
occupying the whole bandwidth and starving the other unicast queues.  
The ML-Series includes support for 400 user-definable queues, which are assigned per the classification  
and bandwidth allocation definition. The classification used for scheduling classifies the frames/packet  
after the policing action, so if the policer is used to mark or change the CoS bits of the ingress  
frames/packet, the new values are applicable for the classification of traffic for queuing and scheduling.  
The ML-Series provides buffering for 4000 packets.  
Scheduling  
Scheduling is provided by a series of schedulers that perform a WDRR as well as priority scheduling  
mechanisms from the queued traffic associated with each egress port.  
Though ordinary round robin servicing of queues can be done in constant time, unfairness occurs when  
different queues use different packet sizes. Deficit Round Robin (DRR) scheduling solves this problem.  
If a queue was not able to send a packet in its previous round because its packet size was too large, the  
remainder from the previous amount of credits that the queue got in each previous round (quantum) is  
added to the quantum for the next round.  
WDRR extends the quantum idea from the DRR to provide weighted throughput for each queue.  
Different queues have different weights, and the quantum assigned to each queue in its round is  
proportional to the relative weight of the queue among all the queues serviced by that scheduler.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 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 12-5 illustrates the ML-Series card’s queuing and scheduling.  
Figure 12-5  
Queuing and Scheduling Model  
Queues assigned by  
"Priority" Command for  
associated Classification  
for Scheduling  
Weighted  
Deficit  
Round  
Robin  
Low Latency Queues  
Unicast Queues  
Queues assigned by  
"Bandwith" Command for  
associated Classification  
for Scheduling  
Weighted  
Deficit  
Round  
Robin  
Weighted  
Deficit  
Round  
Robin  
Weighted  
Deficit  
Round  
Robin  
Queues automatically  
assigned  
Multi/Broadcast Queues  
The weighting structure allows traffic to be scheduled at 1/2048 of the port rate. This equates to  
approximately 49 kbps for traffic exiting a FastEthernet port.  
The unicast queues are created as the output service policy implementation on the egress ports. Each  
unicast queue is assigned with a committed bandwidth and the weight of the queue is determined by the  
normalization of committed bandwidth of all defined unicast queues for that port. The traffic beyond the  
committed bandwidth on any queue is treated by the scheduler according to the relative weight of the  
queue.  
The LLQ is created as the output service policy implementation on the egress ports. Each LLQ is  
assigned with a committed bandwidth of 100 percent and is served with lower latency. To limit the  
bandwidth usage by the LLQ, a strict policer needs to be implemented on the ingress for the LLQ traffic  
classes.  
The DE allows some packets to be treated as committed and some as discard-eligible on the scheduler.  
For the Ethernet frames, the CoS (IEEE 802.1p) bits are used to identify committed and discard eligible  
packets, where the RPR-CoS and the DE bits are used for RPR traffic. When congestion occurs and a  
queue begins to fill, the DE packets hit a lower tail-drop threshold than the committed packets.  
Committed packets are not dropped until the total committed load exceeds the interface output. The  
tail-drop thresholds adjust dynamically in the card to maximize use of the shared buffer pool while  
guaranteeing fairness under all conditions.  
Control Packets and L2 Tunneled Protocols  
The control packets originated by the ML-Series card have a higher priority than data packets. The  
external Layer 2 and Layer 3 control packets are handled as data packets and assigned to broadcast  
queues. Bridge protocol data unit (BPDU) prioritization in the ML-Series card gives Layer 2-tunneled  
BPDU sent out the multicast/broadcast queue a higher discard value and therefore a higher priority than  
than other packets in the multicast/broadcast queue. The Ethernet CoS (IEEE 802.1p) for  
Layer 2-tunneled protocols can be assigned by the ML-Series card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 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. When used with the QinQ feature, priority marking allows the user traffic (inner  
Q-tag) to traverse the network transparently, while providing a means for the network to internally signal  
QoS treatment at Layer 2.  
Priority marking follows the classification process, and therefore any of the classification criteria  
identified earlier can be used as the basis to set the outgoing IEEE 802.1p CoS field. For example, a  
specific CoS value can be mapped to a specific bridge group.  
Priority marking is configured using the MQC set-cos command. If packets would otherwise leave the  
card without an IEEE 802.1Q tag, then the set-cos command has no effect on that packet. If an  
IEEE 802.1Q tag is inserted in the packet (either a normal tag or a QinQ tag), the inserted tag has the  
set-cos priority. If an IEEE 802.1Q tag is present on packet ingress and retained on packet egress, the  
priority of that tag is modified. If the ingress interface is an QinQ access port and the set-cos policy-map  
classifies based on ingress tag priority, this classifies based on the user priority. This is a way to allow  
the user-tag priority to determine the SP tag priority. When a packet does not match any set-cos  
policy-map, the priority of any preserved tag is unchanged and the priority of any inserted IEEE 802.1Q  
tag is set to 0.  
The set-cos command on the output service policy is only applied to unicast traffic. Priority marking for  
multicast/broadcast traffic can only be achieved by the set-cos action of the policing process on the input  
service policy.  
Ingress Priority Marking  
Ingress priority marking can be done for all input packets of a port, for all input packets matching a  
classification, or based on a measured rate. Marking of all packets of an input class can also be done with  
a policing command of the form police 96000 conform-action set-cos-transmit exceed-action  
set-cos-transmit. Using this command with a policy map that contains only the “class-default” will  
mark all ingress packets to the value. Rate based priority marking is discussed in the “Marking and  
Discarding with a Policer” section on page 12-5.  
QinQ Implementation  
The hierarchical VLAN or IEEE 802.1Q tunneling feature enables the service provider to transparently  
carry the customer VLANs coming from any specific port (UNI) and transport them over the service  
provider network. This feature is also known as QinQ, which is performed by adding an additional  
IEEE 802.1Q tag on every customer frame.  
Using the QinQ feature, service providers can use a single VLAN to support customers with multiple  
VLANs. QinQ preserves customer VLAN IDs and segregates traffic from different customers within the  
service-provider infrastructure, even when traffic from different customers originally shared the same  
VLAN ID. The QinQ also expands VLAN space by using a VLAN-in-VLAN hierarchy and tagging the  
tagged packets. When the service provider (SP) tag is added, the QinQ network typically loses any  
visibility to the IP header or the customer Ethernet IEEE 802.1Q tag on the QinQ encapsulated frames.  
On the ML-Series cards, the QinQ access ports (IEEE 802.1Q tunnel ports or QinQ UNI ports) have  
visibility to the customer CoS and the IP precedence or IP DSCP values; therefore, the SP tag can be  
assigned with proper CoS bit, which would reflect the customer IP precedence, IP DSCP, or CoS bits. In  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 12 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 12-6 illustrates the QinQ implementation on the ML-Series card.  
Figure 12-6  
QinQ Implementation on the ML-Series Card  
6
6
2
2
2
2
2
Destination Address  
Source Address  
Type=8100  
SP CoS bit  
(3 bits)  
IEEE 802.1p  
Tag Control Information  
Type=8100  
CoS  
CFI  
(3 bits)  
VLAN ID  
Tag Control Information  
Type/Length  
CoS  
CFI  
Service Provider Tag  
QinQ Tag  
VLAN ID  
MAC DATA  
Customer VLAN Tag  
IEEE 802.1Q Tag  
PAD  
FCS  
4
The ML-Series cards can be used as the IEEE 802.1Q tunneling device for the QinQ network and also  
provide the option to copy the customer frame’s CoS bit into the CoS bit of the added QinQ tag. This  
allows the service provider QinQ network to be fully aware of the necessary QoS treatment for each  
individual customer frame.  
Flow Control Pause and QoS  
If flow control and port-based policing are both enabled for an interface, flow control handles the  
bandwidth. If the policer gets noncompliant flow, then the policer drops or demarks the packets using  
the policer definition of the interface.  
Note  
Note  
QoS and policing are not supported on the ML-Series card interface when link aggregation is used.  
Egress shaping is not supported on the ML-Series cards.  
QoS on RPR  
For VLAN bridging over RPR, all ML-Series cards on the ring must be configured with the base RPR  
and RPR QoS configuration. SLA and bridging configurations are only needed at customer RPR access  
points, where IEEE 802.1Q VLAN CoS is copied to the RPR CoS. This IEEE 802.1Q VLAN CoS  
copying can be overwritten with a set-cos action command. The CoS commit rule applies at the RPR  
ring ingress. Transit RPR ring traffic is classified on CoS only.  
If the packet does not have a VLAN header, the RPR CoS for non-VLAN traffic is set using the following  
rules:  
1. The default CoS is 0.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 12 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.  
Configuring QoS  
This section describes the tasks for configuring the ML-Series card QoS functions using the MQC. The  
ML-Series card does not support the full set of MQC functionality.  
To configure and enable class-based QoS features, perform the procedures described in the following  
sections:  
•
•
•
•
Creating a Traffic Class, page 12-10  
Creating a Traffic Policy, page 12-11  
Attaching a Traffic Policy to an Interface, page 12-15  
Configuring CoS-Based QoS, page 12-16  
For QoS configuration examples, see the “QoS Configuration Examples” section on page 12-17.  
Creating a Traffic Class  
The class-map global configuration command is used to create a traffic class. The syntax of the  
class-map command is as follows:  
class-map [match-any | match-all] class-map-name  
no class-map [match-any | match-all] class-map-name  
The match-all and match-any options need to be specified only if more than one match criterion is  
configured in the traffic class. The class-map match-all command is used when all of the match criteria  
in the traffic class must be met for a packet to match the specified traffic class. The class-map  
match-any command is used when only one of the match criterion in the traffic class must be met for a  
packet to match the specified traffic class. If neither the match-all nor match-any keyword is specified,  
the traffic class behaves in a manner consistent with class-map match-all command.  
To create a traffic class containing match criteria, use the class-map global configuration command to  
specify the traffic class name, and then use the match commands in Table 12-1, as needed.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Configuring QoS  
Table 12-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. The command matches either  
all or any of the criteria, as controlled by the match-all and  
match-any subcommands of the class-map command.  
Note  
The ML-100T-8 supports a maximum of 126 user-defined  
class maps, plus one default class map named  
“class-default”. The ML-Series card on the ONS 15454  
SONET/SDH supports a maximum of 254 user-defined  
class maps, plus one default class map named  
“class-default”.  
ML_Series(config)# class-map match-all  
class-map-name  
Specifies that all match criteria must be met for traffic entering the  
traffic class to be classified as part of the traffic class.  
ML_Series(config)# class-map match-any  
class-map-name  
Specifies that one of the match criteria must be met for traffic  
entering the traffic class to be classified as part of the traffic class.  
ML_Series(config-cmap)# match any  
Specifies that all packets will be matched.  
ML_Series(config-cmap)# match bridge-group  
bridge-group-number  
Specifies the bridge-group-number against whose contents packets  
are checked to determine if they belong to the class.  
ML_Series(config-cmap)# match coscos-number  
Specifies the CoS value against whose contents packets are checked  
to determine if they belong to the class.  
ML_Series(config-cmap)# match input-interface  
interface-name  
Specifies the name of the input interface used as a match criterion  
against which packets are checked to determine if they belong to the  
class.  
The shared packet ring (SPR) interface used in RPR (SPR1) is a  
valid interface-name for the ML-Series card. For more information  
on the SPR interface, see Chapter 15, “Configuring Resilient Packet  
Ring on the ML-Series Card.”  
The input-interface choice is not valid when applied to the INPUT  
of an interface (redundant).  
ML_Series(config-cmap)# match ip dscp  
ip-dscp-value  
Specifies up to eight DSCP values used as match criteria. The value  
of each service code point is from 0 to 63.  
ML_Series (config-cmap)# match ip precedence  
ip-precedence-value  
Specifies up to eight IP precedence values used as match criteria.  
Creating a Traffic Policy  
To configure a traffic policy, use the policy-map global configuration command to specify the traffic  
policy name, and use the following configuration commands to associate a traffic class, which was  
configured with the class-map command and one or more QoS features. The traffic class is associated  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Chapter 12 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.  
When the bandwidth or priority action is used on any class in a policy map, then there must be a class,  
defined by the match-any command, that has a bandwidth or priority action in that policy map. This is  
to ensure that all traffic can be classified into a default class that has some assigned bandwidth. A  
minimum bandwidth can be assigned if the class is not expected to be used or if no reserved bandwidth  
is desired for default traffic.  
The QoS policies that can be applied in the traffic policy in policy-map class configuration mode are  
detailed in the following example.  
The syntax of the policy-map command is:  
policy-map policy-name  
no policy-map policy-name  
The syntax of the class command is:  
class class-map-name  
no class class-map-name  
All traffic that fails to meet the matching criteria belongs to the default traffic class. The default traffic  
class can be configured by the user, but cannot be deleted.  
To create a traffic policy, use the commands in Table 12-2 as needed.  
Table 12-2  
Command  
Traffic Policy Commands  
Purpose  
ML_Series (config)# policy-map policy-name  
Specifies the name of the traffic policy to configure. Names can be a  
maximum of 40 alphanumeric characters.  
ML_Series (config-pmap)# class  
class-map-name  
Specifies the name of a predefined traffic class, which was configured with  
the class-map command, used to classify traffic to the traffic policy.  
ML_Series (config-pmap)# class  
class-default  
Specifies the default class to be created as part of the traffic policy.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Configuring QoS  
Table 12-2  
Traffic Policy Commands (continued)  
Purpose  
Command  
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.  
Valid choices for the ML-Series cards are:  
•
•
Rate in kilobits per second  
Percent of total available bandwidth (1 to 100)  
If multiple classes and bandwidth actions are specified in a single policy  
map, they must use the same choice in specifying bandwidth (kilobits or  
percent).  
Note  
When using the bandwidth command, excess traffic (beyond the  
configured commit) is allocated any available bandwidth in  
proportion to the relative bandwidth commitment of its traffic  
class compared to other traffic classes. Excess traffic from two  
classes with equal commits has equal access to available  
bandwidth. Excess traffic from a class with a minimum commit  
might receive only a minimum share of available bandwidth  
compared to excess bandwidth from a class with a high commit.  
Note  
The true configurable bandwidth in kilobits per second is per port  
and depends on how the ML-Series card is configured. The show  
interface command shows the maximum bandwidth of a port (for  
example, BW 100000 Kbit). The sum of all bandwidth and priority  
actions applied to the interface, plus the cos priority-mcast  
bandwidth, is not allowed to exceed the maximum bandwidth of  
the port.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Configuring QoS  
Table 12-2  
Command  
Traffic Policy Commands (continued)  
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. Policing is supported only on ingress, not on egress.  
•
•
•
•
•
For cir-rate-bps, specify the average committed information rate (cir)  
in bits per second (bps). The range is 96000 to 800000000.  
For normal-burst-byte, specify the cir burst size in bytes. The range is  
8000 to 64000.  
(Optional) For maximum-burst-byte, specify the peak information rate  
(pir) burst in bytes. The range is 8000 to 64000.  
(Optional) For pir-rate-bps, specify the average pir traffic rate in bps  
where the range is 96000 to 800000000.  
(Optional) Conform action options are:  
–
–
–
Set a CoS priority value and transmit  
Transmit packet (default)  
Drop packet  
•
•
(Optional) Exceed action options are:  
–
–
Set a CoS value and transmit  
Drop packet (default)  
(Optional) The violate action is only valid if pir is configured. Violate  
action options are:  
–
–
Set a CoS value and transmit  
Drop packet (default)  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Configuring QoS  
Table 12-2  
Traffic Policy Commands (continued)  
Purpose  
Command  
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.  
Note  
This priority command does not apply to the default class.  
Note  
When using the priority action, the traffic in that class is given a  
100 percent CIR, regardless of the rate entered as the priority rate.  
To ensure that other bandwidth commitments are met for the  
interface, a policer must be configured on the input of all interfaces  
that might deliver traffic to this output class, limiting the peak rate  
to the priority rate entered.  
Note  
The true configurable bandwidth in kilobits per second is per port  
and depends on how the ML-Series card is configured. The show  
interface command shows the maximum bandwidth of a port (for  
example, BW 100000 Kbit). The sum of all bandwidth and priority  
actions applied to the interface, plus the cos priority-mcast  
bandwidth, is not allowed to exceed the maximum bandwidth of  
the port.  
ML_Series (config-pmap-c)# set cos  
cos-value  
Specifies a CoS value or values to associate with the packet. The number  
is in the range from 0 to 7.  
This command can only be used in a policy-map applied to an output. It  
specifies the VLAN CoS priority to set for the outbound packets in the  
currently selected class. If QinQ is used, the top-level VLAN tag is  
marked. If outbound packets have no VLAN tag, the action has no effect.  
This action is applied to the packet after any set-cos action done by a  
policer, and therefore overrides the CoS set by a policer action.  
If a packet is marked by the policer and forwarded out through an interface  
that also has a set-cos action assigned for the traffic class, the value  
specified by the police action takes precedence in setting the IEEE 802.1p  
CoS field.  
This command also sets the CoS value in the RPR header for packets  
exiting the ML-Series on the RPR interface.  
Attaching a Traffic Policy to an Interface  
Use the service-policy interface configuration command to attach a traffic policy to an interface and to  
specify the direction in which the policy should be applied (either on packets coming into the interface  
or packets leaving the interface). Only one traffic policy can be applied to an interface in a given  
direction.  
Use the no form of the command to detach a traffic policy from an interface. The service-policy  
command syntax is as follows:  
service-policy {input | output} policy-map-name  
no service-policy {input | output} policy-map-name  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 12 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:  
Command  
Purpose  
ML_Series(config)# interface  
interface-id  
Enters interface configuration mode, and specifies the  
interface to apply the policy map.  
Step 1  
Valid interfaces are limited to physical Ethernet and  
packet-over-SONET (POS) interfaces.  
Note  
Policy maps cannot be applied to SPR interfaces,  
subinterfaces, port channel interfaces, or Bridge  
Group Virtual Interfaces (BVIs).  
ML_Series(config-if)# service-policy  
output policy-map-name  
Step 2  
Step 3  
Specifies the name of the traffic policy to be attached to the  
output direction of an interface. The traffic policy evaluates  
all traffic leaving that interface.  
ML_Series(config-if)# service-policy  
input policy-map-name  
Specifies the name of the traffic policy to be attached to the  
input direction of an interface. The traffic policy evaluates  
all traffic entering that interface.  
Configuring CoS-Based QoS  
The global cos commit cos-value command allows the ML-Series card to base the QoS treatment for a  
packet coming in on a network interface on the attached CoS value, rather than on a per-customer-queue  
policer.  
CoS-based QoS is applied with a single global cos commit cos-value command, as shown in Table 12-3:  
Table 12-3  
CoS Commit Command  
Command  
Purpose  
ML_Series(config)# cos-commit  
cos-value  
Labels packets that come in with a CoS equal to or higher than  
the cos-value as CIR and packets with a lower CoS as DE.  
Monitoring and Verifying QoS Configuration  
After configuring QoS on the ML-Series card, the configuration of class maps and policy maps can be  
viewed through a variety of show commands. To display the information relating to a traffic class or  
traffic policy, use one of the following commands in EXEC mode, as needed. Table 12-4 describes the  
commands that are related to QoS status.  
Table 12-4  
Commands for QoS Status  
Command  
Purpose  
ML_Series# show class-map name  
Displays the traffic class information of the user-specified  
traffic class.  
ML_Series# show policy-map  
Displays all configured traffic policies.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                       
Chapter 12 Configuring Quality of Service on the ML-Series Card  
QoS Configuration Examples  
Table 12-4  
Commands for QoS Status (continued)  
Purpose  
Command  
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 12-1 shows examples of the QoS commands.  
Example 12-1 QoS Status Command Examples  
ML_Series# show class-map  
Class Map match-any class-default (id 0)  
Match any  
Class Map match-all policer (id 2)  
Match ip precedence 0  
ML_Series# show policy-map  
Policy Map police_f0  
class policer  
police 1000000 10000 conform-action transmit exceed-action drop  
ML_Series# show policy-map interface  
FastEthernet0  
service-policy input: police_f0  
class-map: policer (match-all)  
0 packets, 0 bytes  
5 minute offered rate 0 bps, drop rate 0 bps  
match: ip precedence 0  
class-map: class-default (match-any)  
0 packets, 0 bytes  
5 minute offered rate 0 bps, drop rate 0 bps  
match: any  
0 packets, 0 bytes  
5 minute rate 0 bps  
QoS Configuration Examples  
This section provides the specific command and network configuration examples:  
•
•
•
•
•
•
•
Traffic Classes Defined Example  
Traffic Policy Created Example  
class-map match-any and class-map match-all Commands Example  
match spr1 Interface Example  
ML-Series VoIP Example  
ML-Series Policing Example  
ML-Series CoS-Based QoS Example  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 Configuring Quality of Service on the ML-Series Card  
QoS Configuration Examples  
Traffic Classes Defined Example  
Example 12-2 shows how to create a class map called class1 that matches incoming traffic entering  
interface fastethernet0.  
Example 12-2 Class Interface Command Example  
ML_Series(config)# class-map class1  
ML_Series(config-cmap)# match input-interface fastethernet0  
Example 12-3 shows how to create a class map called class2 that matches incoming traffic with  
IP-precedence values of 5, 6, and 7.  
Example 12-3 Class IP-Precedence Command Example  
ML_Series(config)# class-map match-any class2  
ML_Series(config-cmap)# match ip precedence 5 6 7  
Note  
If a class-map contains a match rule that specifies multiple values, such as 5 6 7 in this example, then  
the class-map must be match-any, not the default match-all. Without the match-any class-map, an error  
message is printed and the class is ignored. The supported commands that allow multiple values are  
match cos, match ip precedence, and match ip dscp.  
Example 12-4 shows how to create a class map called class3 that matches incoming traffic based on  
bridge group 1.  
Example 12-4 Class Map Bridge Group Command Example  
ML_Series(config)# class-map class3  
ML_Series(config-cmap)# match bridge-group 1  
Traffic Policy Created Example  
In Example 12-5, a traffic policy called policy1 is defined to contain policy specifications, including a  
bandwidth allocation request for the default class and two additional classes—class1 and class2. The  
match criteria for these classes were defined in the traffic classes (see the “Creating a Traffic Class”  
section on page 12-10).  
Example 12-5 Traffic Policy Created Example  
ML_Series(config)# policy-map policy1  
ML_Series(config-pmap)# class class-default  
ML_Series(config-pmap-c)# bandwidth 1000  
ML_Series(config-pmap)# exit  
ML_Series(config-pmap)# class class1  
ML_Series(config-pmap-c)# bandwidth 3000  
ML_Series(config-pmap)# exit  
ML_Series(config-pmap)# class class2  
ML_Series(config-pmap-c)# bandwidth 2000  
ML_Series(config-pmap)# exit  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 12 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. Packets must either meet all of the match criteria (match-all) or one of the  
match criteria (match-any) in order to be considered a member of the traffic class.  
Example 12-6 shows a traffic class configured with the class-map match-all command.  
Example 12-6 Class Map Match All Command Example  
ML_Series(config)# class-map match-all cisco1  
ML_Series(config-cmap)# match cos 1  
ML_Series(config-cmap)# match bridge-group 10  
If a packet arrives with a traffic class called cisco1 configured on the interface, the packet is evaluated  
to determine if it matches the cos 1 and bridge group 10. If both of these match criteria are met, the  
packet matches traffic class cisco1.  
In a traffic class called cisco2, the match criteria are evaluated consecutively until a successful match  
criterion is located. The packet is first evaluated to the determine whether cos 1 can be used as a match  
criterion. If cos 1 can be used as a match criterion, the packet is matched to traffic class cisco2. If cos 1  
is not a successful match criterion, then bridge-group 10 is evaluated as a match criterion. Each matching  
criterion is evaluated to see if the packet matches that criterion. When a successful match occurs, the  
packet is classified as a member of traffic class cisco2. If the packet matches none of the specified  
criteria, the packet is classified as a member of the traffic class.  
Note that the class-map match-all command requires that all of the match criteria must be met in order  
for the packet to be considered a member of the specified traffic class (a logical AND operator). In the  
example, cos 1 AND bridge group 10 have to be successful match criteria. However, only one match  
criterion must be met for the packet in the class-map match-any command to be classified as a member  
of the traffic class (a logical OR operator).  
Example 12-7 shows a traffic class configured with the class-map match-any command. In the example,  
cos 1 OR bridge group 10 OR ip dscp 5 has to be successful match criteria.  
Example 12-7 Class Map Match Any Command Example  
ML_Series(config)# class-map match-any cisco2  
ML_Series(config-cmap)# match cos 1  
ML_Series(config-cmap)# match bridge-group 10  
ML_Series(config-cmap)# match ip dscp 5  
match spr1 Interface Example  
In Example 12-8, the SPR interface is specified as a parameter to the match input-interface CLI when  
defining a class-map.  
Example 12-8 Class Map SPR Interface Command Example  
ML_Series(config)# class-map spr1-cos1  
ML_Series(config-cmap)# match input-interface spr1  
ML_Series(config-cmap)# match cos 1  
ML_Series(config-cmap)# end  
ML_Series# sh class-map spr1-cos1  
Class Map match-all spr1-cos1 (id 3)  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 12 Configuring Quality of Service on the ML-Series Card  
QoS Configuration Examples  
Match input-interface SPR1  
Match cos 1  
ML-Series VoIP Example  
Figure 12-7 shows an example of ML-Series voice-over- IP (VoIP). The associated commands are  
provided in Example 12-9.  
Figure 12-7  
ML-Series VoIP Example  
ML-Series  
Router_A  
VoIP Traffic  
Fast Ethernet 0  
POS 0  
SONET/SDH  
STS-1 circuit  
General Data Traffic  
During periods of congestion, the ML-Series card services  
all VoIP traffic before servicing any general data traffic.  
Example 12-9 ML-Series VoIP Commands  
Router(config)# class-map match-all voip  
Router(config-cmap)# match ip precedence 5  
Router(config-cmap)# exit  
Router(config)# class-map match-any default  
Router(config-cmap)# match any  
Router(config-cmap)# exit  
Router(config)# policy-map pos0  
Router(config-pmap)# class default  
Router(config-pmap-c)# bandwidth  
Router(config-pmap-c)# class voip  
1000  
Router(config-pmap-c)# priority 1000  
Router(config-pmap-c)# interface FastEthernet0  
Router(config-if)# ip address 1.1.1.1 255.255.255.0  
Router(config-if)# interface POS0  
Router(config-if)# ip address 2.1.1.1 255.255.255.0  
Router(config-if)# service-policy output pos0  
Router(config-if)# crc 32  
Router(config-if)# no cdp enable  
ML-Series Policing Example  
Figure 12-8 shows an example of ML-Series policing. The example shows how to configure a policer  
that restricts traffic with an IP precedence of 0 to 1,000,000 bps. The associated code is provided in  
Example 12-10.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 12 Configuring Quality of Service on the ML-Series Card  
QoS Configuration Examples  
Figure 12-8  
ML-Series Policing Example  
ML-Series  
Router_a  
Fast Ethernet 0  
POS 0  
SONET/SDH  
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.  
Example 12-10 ML-Series Policing Commands  
Router(config)# class-map match-all policer  
Router(config-cmap)# match ip precedence 0  
Router(config-cmap)# exit  
Router(config)# policy-map police_f0  
Router(config-pmap)# class policer  
Router(config-pmap-c)# police 1000000 10000 conform-action transmit exceed-action drop  
Router(config-pmap-c)# interface FastEthernet0  
Router(config-if)# service-policy input police_f0  
ML-Series CoS-Based QoS Example  
Figure 12-9 shows an example of ML-Series CoS-based QoS. The associated code is provided in the  
examples that follow the figure. The CoS example assumes that the ML-Series cards are configured into  
an RPR and that the ML-Series card POS ports are linked by point-to-point SONET circuits. ML-Series  
Card A and ML-Series Card C are customer access points. ML-Series Card B is not a customer access  
point. For more information on configuring RPR, see Chapter 15, “Configuring Resilient Packet Ring  
on the ML-Series Card.”  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 Configuring Quality of Service on the ML-Series Card  
QoS Configuration Examples  
Figure 12-9  
ML-Series CoS Example  
ML-Series Card B  
POS 1  
POS 0  
POS 1  
POS 0  
POS 1  
RPR  
ML-Series Card A  
Customer Access Point  
ML-Series Card C  
POS 0 Customer Access Point  
= STS circuit created on CTC  
Example 12-11 shows the code used to configure ML-Series Card A in Figure 12-9.  
Example 12-11 ML-Series Card A Configuration (Customer Access Point)  
ML_Series_A(config)# cos commit 2  
ML_Series_A(config)# policy-map Fast5_in  
ML_Series_A(config-pmap)# class class-default  
ML_Series_A(config-pmap-c)# police 5000 8000 8000 pir 10000 conform-action  
set-cos-transmit 2 exceed-action set-cos-transmit 1 violate-action drop  
Example 12-12 shows the code used to configure ML-Series Card B in Figure 12-9.  
Example 12-12 ML-Series Card B Configuration (Not a Customer Access Point)  
ML_Series_B(config)# cos commit 2  
Example 12-13 shows the code used to configure ML-Series Card C in Figure 12-9.  
Example 12-13 ML-Series Card C Configuration (Customer Access Point)  
ML_Series_B(config)# cos commit 2  
ML_Series_B(config)# policy-map Fast5_in  
ML_Series_B(config-pmap)# class class-default  
ML_Series_B(config-pmap-c)# police 5000 8000 8000 pir 10000 conform-action  
set-cos-transmit 2 exceed-action set-cos-transmit 1 violate-action drop  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 12 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.  
The multicast priority queuing CoS match is based on the “internal” CoS value of each packet. This value  
is normally the same as the egress CoS value (after policer marking if enabled) but differs in two cases.  
The “internal” CoS value is not the same as the egress value when dot1q-tunneling is used. With  
dot1q-tunneling, the internal CoS value is always the value of the outer tag CoS, both when entering the  
dot1q tunnel and leaving the dot1q tunnel. The “internal” CoS value is also not the same as the egress  
value if a packet is transported over a VLAN, and the VLAN tag is removed on egress to send the packet  
untagged. In this case, the internal CoS is the CoS of the removed tag (including ingress policing and  
marking if enabled).  
The cos priority-mcast command does not modify the CoS of the multicast packets but only the  
bandwidth allocation for the multicast priority queuing class. The command guarantees a minimum  
amount of bandwidth and is queued separately from the default multicast/broadcast queue.  
Creating a multicast priority queuing class allows for special handling of certain types of multiclass  
traffic. This is especially valuable for multicast video distribution and service provider multicast traffic.  
For example, a service provider might want to guarantee the protection of their own multicast  
management traffic. To do this, they could create a multicast priority queuing class on the ML-Series  
card for the CoS value of the multicast management traffic and guarantee its minimum bandwidth. For  
multicast video distribution, a multicast priority queuing class on the ML-Series card for the CoS value  
of the multicast video traffic enables networks to efficiently manage multicast video bandwidth demands  
on a network shared with VoIP and other Ethernet services.  
Note  
Note  
Multicast priority queuing traffic uses port-based load-balancing over RPR and EtherChannel. Default  
multicast traffic is load-balanced over RPR, but not over EtherChannel.  
Multicast priority queuing bandwidth should not be oversubscribed for sustained periods with traffic  
from multiple sources. This can result in reduced multicast priority queuing throughput.  
Default Multicast QoS  
Default multicast traffic is any multicast traffic (including flooded traffic) that is not classified as  
multicast priority queuing. The default multicast class also includes broadcast data traffic, control traffic,  
L2 protocol tunneling, and flooding traffic of the unknown MAC during MAC learning.  
With no QoS configured (no multicast priority queuing and no output policy map) on the ML-Series  
card, the default multicast bandwidth is a 10 percent minimum of the total bandwidth.  
When bandwidth is allocated to multicast priority queuing but no output policy map is applied, the  
default multicast congestion bandwidth is a minimum of 10 percent of the bandwidth that is not allocated  
to multicast priority queuing.  
When an output policy-map is applied to an interface, default multicast and default unicast share the  
minimum bandwidth assigned to the default class. This default class is also known as the match-any  
class. The minimum bandwidth of default multicast is 10 percent of the total default class bandwidth.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-23  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 12 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. The rate of traffic can be reduced for all ports on  
the ML-Series card when this feature is configured. Default multicast traffic uses bandwidth only  
on the ports where it egresses, not globally like multicast priority queuing.  
•
•
•
Multicast priority queuing QoS is supported only for Layer 2 bridging.  
The ML-Series card supports a maximum of two multicast priority queuing classes.  
Unlike the rest of the ML-Series card QoS, multicast priority queuing QoS is not part of the  
Cisco IOS MQC.  
•
Priority-mcast bandwidth allocation is per port.  
Configuring Multicast Priority Queuing QoS  
To configure a priority class for multicast traffic, use the global configuration cos priority-mcast  
command defined in Table 12-5.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-24  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Configuring Multicast Priority Queuing QoS  
Table 12-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.  
cos-value specifies the CoS value of multicast packets which  
will be given the bandwidth allocation. Matches only a single  
CoS of traffic (not a range). Supported CoS range is 0 to 7.  
A minimum bandwidth guarantee can be specified in kbps, in  
mbps, or by a percentage of the overall available bandwidth.  
Valid choices for the ML-Series card are:  
•
•
•
Rate in kilobits per second  
Rate in megabits per second  
Percent of total available port bandwidth (1 to 100)  
Reentering the command with the same cos-value but a  
different bandwidth rate will modify the bandwidth of the  
existing class.  
Reentering the command with a different cos-value creates a  
separate multicast priority queuing class with a maximum of  
two multicast priority queuing classes.  
The no form of this command removes the multicast priority  
queuing class.  
Note  
The true configurable bandwidth in kilobits or megabits  
per second is per port and depends on how the  
ML-Series card is configured. The show interface  
command shows the maximum bandwidth of a port (for  
example, BW 100000 Kbit). The sum of all bandwidth  
and priority actions applied to the interface, plus the cos  
priority-mcast bandwidth, is not allowed to exceed the  
maximum bandwidth of the port.  
Note  
Attempting to configure a priority-mcast bandwidth  
that exceeds the true configurable bandwidth on any  
port will cause the priority-mcast configuration change  
to fail, and the multicast priority queuing bandwidth  
guarantee will not be changed.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-25  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 12 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.  
Figure 12-10  
QoS not Configured on Egress  
Traffic at Egress  
without QoS  
False  
Unicast Traffic?  
Multicast/Broadcast  
True  
service up to 90%  
interface BW and  
best effort service  
for exceeding traffic  
False  
If rate < 10%  
interface BW  
Best Effort  
Service  
True  
Guaranteed  
Service  
ML-Series Egress Bandwidth Example  
This section explains with examples the utilization of bandwidth across different queues with or without  
Priority Multicast.  
Case 1: QoS with Priority and Bandwidth Configured Without Priority Multicast  
Strict Priority Queue is always serviced first. The remaining interface bandwidth is utilized to service  
other configured traffic.  
In the following example, after servicing unicast customer_voicetraffic, the remaining interface  
bandwidth is utilized for other WRR queues such as customer_core_traffic, customer_data, and  
class-defaultin the ratio of 1:3:5.  
At any given time, the sum of the bandwidth assigned cannot exceed the interface bandwidth (in kbps).  
The bandwidth share allocated to class-default will be utilized by default unicast traffic (in this  
example, unicast traffic with CoS values other than 2, 5, 7) and all multicast/broadcast traffic (all CoS  
values). The default unicast and all multicast/broadcast traffic will be serviced in the ratio of 9:1.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-26  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 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 12-14 QoS with Priority and Bandwidth Configured without Priority Multicast  
!
class-map match-all customer_voice  
match cos 5  
class-map match-all customer_data  
match cos 7  
class-map match-all customer_core_traffic  
match cos 2  
!
!
policy-map policy_egress_bandwidth  
class customer_core_traffic  
bandwidth  
1000  
class customer_voice  
priority 1000  
class customer_data  
bandwidth  
class class-default  
bandwidth 5000  
3000  
!
!
interface POS0  
no ip address  
crc 32  
service-policy output policy_egress_bandwidth  
!
Case 2: QoS with Priority and Bandwidth Configured with Priority Multicast  
In this case, only multicast traffic of CoS 3 is allocated a guaranteed bandwidth. This multicast traffic  
will now participate in the queue along with other WRR queues. After servicing the customer_voice  
traffic, the remaining interface bandwidth is utilized for WRR queues, such as customer_core_traffic,  
customer_data, class-default, and multicast CoS 3 traffic in the ratio of 1:3:5:2.  
At any given time, the sum of the bandwidth assigned cannot exceed the interface bandwidth (in kbps).  
Example 12-15 QoS with Priority and Bandwidth configured with Priority Multicast  
cos priority-mcast 3 2000  
!
class-map match-all customer_voice  
match cos 5  
class-map match-all customer_data  
match cos 7  
class-map match-all customer_core_traffic  
match cos 2  
!
!
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-27  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 12 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  
class class-default  
bandwidth 5000  
3000  
!
!
interface POS0  
no ip address  
crc 32  
service-policy output policy_egress_bandwidth  
!
Understanding 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.  
Enhanced performance monitoring displays per-CoS packet statistics on the ML-Series card interfaces  
when CoS accounting is enabled. CoS-based traffic utilization is displayed at the Fast Ethernet interface  
or subinterface (VLAN) level, or at the POS interface level. It is not displayed at the POS subinterface  
level. RPR statistics are not available at the SPR interface level, but statistics are available for the  
individual POS ports that make up the SPR interface. EtherChannel (port-channel) and BVI statistics are  
available only at the member port level. Table 12-6 shows the types of statistics available at specific  
interfaces.  
Table 12-6  
Packet Statistics on ML-Series Card Interfaces  
Fast Ethernet  
Interface  
Fast Ethernet  
Subinterface (VLAN) Interface Subinterface  
POS  
POS  
Statistics Collected  
Input—Packets and Bytes Yes  
Output—Packets and Bytes Yes  
Yes  
Yes  
No  
No  
No  
Yes  
No  
No  
No  
Drop Count—Packets and Yes  
Bytes1  
1. Drop counts only include discards caused by output congestion and are counted at the output interface.  
CoS-based packet statistics are available through the Cisco IOS command-line interface (CLI) and  
Simple Network Management Protocol (SNMP), using an extension of the CISCO-PORT-QOS MIB.  
They are not available through Cisco Transport Controller (CTC).  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-28  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 12 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.  
To enable CoS-based packet statistics on an interface, use the interface configuration level command  
defined in Table 12-7.  
Table 12-7  
CoS-Based Packet Statistics Command  
Command  
Purpose  
ML_Series(config-if)# cos  
accounting  
Enables CoS-based packet statistics to be recorded at the specific  
interface and for all the subinterfaces of that interface. This  
command is supported only in interface configuration mode and not  
subinterface configuration mode.  
The no form of the command disables the statistics.  
After configuring CoS-based packet statistics on the ML-Series card, the statistics can be viewed  
through a variety of show commands. To display this information, use one of the commands in  
Table 12-8 in EXEC mode.  
Table 12-8  
Commands for CoS-Based Packet Statistics  
Command  
Purpose  
ML_Series# show interface type number  
cos  
Displays the CoS-based packet statistics available for  
an interface.  
ML_Series# show interface type  
number.subinterface-number cos  
Displays the CoS-based packet statistics available for  
a FastEthernet subinterface. POS subinterfaces are not  
eligible.  
Example 12-16 shows examples of these commands.  
Example 12-16 Commands for CoS-Based Packet Statistics Examples  
ML_Series# show interface fastethernet 0.5 cos  
FastEthernet0.5  
Stats by Internal-Cos  
Input: Packets  
Cos 0: 31  
Cos 1:  
Bytes  
2000  
Cos 2: 5  
Cos 3:  
400  
Cos 4:  
Cos 5:  
Cos 6:  
Cos 7:  
Output: Packets  
Bytes  
Cos 0: 1234567890 1234567890  
Cos 1: 31  
Cos 2:  
2000  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-29  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 12 Configuring Quality of Service on the ML-Series Card  
Understanding IP SLA  
Cos 3:  
Cos 4:  
Cos 5:  
Cos 6: 10  
Cos 7:  
640  
ML_Series# show interface fastethernet 0 cos  
FastEthernet0  
Stats by Internal-Cos  
Input: Packets  
Cos 0: 123  
Cos 1:  
Bytes  
3564  
Cos 2: 3  
Cos 3:  
211  
Cos 4:  
Cos 5:  
Cos 6:  
Cos 7:  
Output: Packets  
Bytes  
Cos 0: 1234567890 1234567890  
Cos 1: 3  
Cos 2:  
200  
Cos 3:  
Cos 4:  
Cos 5:  
Cos 6: 1  
Cos 7:  
64  
Output: Drop-pkts  
Drop-bytes  
Cos 0: 1234567890 1234567890  
Cos 1:  
Cos 2:  
Cos 3:  
Cos 4:  
Cos 5: 1  
Cos 6: 10  
Cos 7:  
64  
640  
ML_Series# show interface pos0 cos  
POS0  
Stats by Internal-Cos  
Output: Drop-pkts  
Cos 0: 12  
Cos 1: 31  
Cos 2:  
Drop-bytes  
1234  
2000  
Cos 3:  
Cos 4:  
Cos 5:  
Cos 6: 10  
Cos 7:  
640  
Understanding IP SLA  
Cisco IP SLA, formerly known as the Cisco Service Assurance Agent, is a Cisco IOS feature to assure  
IP service levels. Using IP SLA, service provider customers can measure and provide service level  
agreements, and enterprise customers can verify service levels, verify outsourced service level  
agreements, and understand network performance for new or existing IP services and applications. IP  
SLAs use unique service level assurance metrics and methodology to provide highly accurate, precise  
service level assurance measurements.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-30  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 12 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. The packets have configurable IP and application layer options  
such as source and destination IP address, User Datagram Protocol (UDP)/TCP port numbers, a type of  
service (ToS) byte (including Differentiated Services Code Point [DSCP] and IP Prefix bits), Virtual  
Private Network (VPN) routing/forwarding instance (VRF), and URL web address.  
IP SLAs uses generated traffic to measure network performance between two networking devices such  
as routers. IP SLAs starts when the IP SLAs device sends a generated packet to the destination device.  
After the destination device receives the packet, and depending on the type of IP SLAs operation, the  
device will respond with time-stamp information for the source to make the calculation on performance  
metrics. An IP SLAs operation is a network measurement to a destination in the network from the source  
device using a specific protocol such as UDP for the operation.  
Because IP SLA is accessible using SNMP, it also can be used in performance monitoring applications  
for network management systems (NMSs) such as CiscoWorks2000 (CiscoWorks Blue) and the  
Internetwork Performance Monitor (IPM). IP SLA notifications also can be enabled through Systems  
Network Architecture (SNA) network management vector transport (NMVT) for applications such as  
NetView.  
For general IP SLA information, refer to the Cisco IOS IP Service Level Agreements technology page  
at http://www.cisco.com/warp/public/732/Tech/nmp/ipsla. For information on configuring the Cisco IP  
SLA feature, see the “Network Monitoring Using Cisco Service Assurance Agent” chapter of the Cisco  
IOS Configuration Fundamentals Configuration Guide, Release 12.2. at:  
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter0918  
6a008030c773.html.  
IP SLA on the ML-Series  
The ML-Series card has a complete IP SLA Cisco IOS subsystem and offers all the normal features and  
functions available in Cisco IOS Release 12.2S. It uses the standard IP SLA Cisco IOS CLI commands.  
The SNMP support will be equivalent to the support provided in the IP SLA subsystem 12.2(S), which  
is the rttMon MIB.  
IP SLA Restrictions on the ML-Series  
The ML-Series card supports only features in the Cisco IOS 12.2S branch. It does not support functions  
available in future Cisco IOS versions, such as the IP SLA accuracy feature or the enhanced Cisco IOS  
CLI support with updated IP SLA nomenclature.  
Other restrictions are:  
•
Setting the CoS bits is supported, but set CoS bits are not honored when leaving or entering the CPU  
when the sender or responder is an ONS 15454, ONS 15454 SDH, ONS 15310-CL, or ONS  
15310-MA platform. Set CoS bits are honored in intermediate ONS nodes.  
•
•
On RPR, the direction of the data flow for the IP SLA packet might differ from the direction of  
customer traffic.  
The system clock on the ML-Series card synchronizes with the clock on the TCC2/TCC2P card. Any  
NTP server synchronization is done with the TCC2/TCC2P card clock and not with the ML-Series  
card clock.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-31  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 12 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. For very accurate IP SLA measurements, it is  
recommended that a Cisco Router or Switch be used as an external probe or responder to measure  
the RTT of the ML-Series cards in a network.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
12-32  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
13  
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 13-1  
Understanding SDM Regions, page 13-2  
Configuring SDM, page 13-2  
Monitoring and Verifying SDM, page 13-3  
Understanding the SDM  
The ONS 15310-CL and ONS 15310-MA ML-Series card features high-speed forwarding. The  
ML-Series card does Layer 2 MAC address lookups through a hash table. Quality of service (QoS)  
classifier lookup are done in software and all other lookups are supported by the main policy engine. The  
ONS 15310-CL and ONS 15310-MA ML-Series card does not use external ternary content-addressable  
memory (TCAM) like the ONS 15454 ML-Series card.  
The SDM is the software subsystem that manages the switching information. It organizes the switching  
information into application-specific regions and configures the size of these application regions. SDM  
enables exact-match and longest-match address searches, which result in high-speed forwarding.  
A location index is associated with each packet forwarded and conveyed to the forwarding engine. The  
forwarding engine uses this location index to derive information associated with each forwarded packet.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
13-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 13 Configuring the Switching Database Manager on the ML-Series Card  
Understanding SDM Regions  
Understanding SDM Regions  
SDM partitions multiple application-specific regions and interacts with the individual application  
control layers to store switching information. The regions share the total available space. SDM consists  
of the following types of regions:  
•
Exact-match region—The exact-match region consists of entries for multiple application regions  
such as IP adjacencies.  
•
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.  
•
Weighted-exact-match region—The weighted-exact-match region consists of exact-match-entries  
with an assigned weight or priority. For example, with QoS, multiple exact match entries might  
exist, but some have priority over others. The weight is used to select one entry when multiple  
entries match.  
Table 13-1 lists default partitioning for each application region.  
Table 13-1 Default Partitioning by Application Region  
Application Region Lookup Type Key Size Default Size  
IP Adjacency  
IP Prefix  
Exact-match  
64 bits  
64 bits  
64 bits  
64 bits  
64 bits  
64 bits  
64 bits  
300 (shared)  
300 (shared)  
300 (shared)  
300 (shared)  
300 (shared)  
8192  
Longest-match  
QoS Classifiers  
IP VRF Prefix  
IP Multicast  
MAC Addr  
Weighted exact-match  
Longest prefix match  
Longest prefix match  
Longest prefix match  
Weighted exact match  
Access List  
300 (shared)  
Configuring SDM  
This section describes SDM region size and access control list (ACL) size configuration. The commands  
described in this section are unique to the switching software. Configuration changes take place  
immediately on the ML-100T-8 card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
13-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 13 Configuring the Switching Database Manager on the ML-Series Card  
Monitoring and Verifying SDM  
Configuring SDM Regions  
To configure SDM maximum size for each application region, perform the following procedure,  
beginning in global configuration mode:  
Command  
Purpose  
ML_Series(config)# sdm size  
region-name number-of-entries  
Step 1  
Step 2  
Configures the maximum number of entries for an SDM  
region.  
ML_Series(config)# end  
Exits to privileged EXEC mode.  
An example of this is shown in Example 13-1.  
Example 13-1 Limiting the IP-Prefix Region to 2K Entries  
ML_Series # configure terminal  
ML_Series(config)# sdm size ip-prefix 200  
ML_Series(config)# end  
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 13-2.  
Table 13-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. You can enter the size as an absolute number  
of entries.  
An example of this is shown in Example 13-2.  
Example 13-2 Configuring Entries for the ACL Region in TCAM  
ML_Series# configure terminal  
ML_Series(config)# sdm access-list 100  
ML_Series(config)# end  
Monitoring and Verifying SDM  
To display the number of available TCAM entries, enter the show sdm size command from global  
configuration mode:  
ML_Series # show sdm size  
Active Switching Database Region Maximum Sizes :  
IP Adjacency  
IP Prefix  
QoS Classifiers  
IP VRF Prefix  
IP Multicast  
: 300  
: 300  
: 300  
: 300  
: 300  
64-bit entries  
64-bit entries  
64-bit entries  
64-bit entries  
64-bit entries  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
13-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                         
Chapter 13 Configuring the Switching Database Manager on the ML-Series Card  
Monitoring and Verifying SDM  
MAC Addr  
Access List  
: 8192  
: 300  
64-bit entries  
64-bit entries  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
13-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
14  
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 14-1  
ML-Series ACL Support, page 14-1  
Modifying ACL TCAM Size, page 14-5  
Understanding ACLs  
ACLs provide network control and security, allowing you to filter packet flow into or out of ML-Series  
interfaces. ACLs, which are sometimes called filters, allow you to restrict network use by certain users  
or devices. ACLs are created for each protocol and are applied on the interface for either inbound or  
outbound traffic. ACLs do not apply to outbound control plane traffic. Only one ACL filter can be  
applied per direction per subinterface.  
When creating ACLs, you define criteria to apply to each packet processed by the ML-Series card; the  
ML-Series card decides whether to forward or block the packet based on whether or not the packet  
matches the criteria in your list. Packets that do not match any criteria in your list are automatically  
blocked by the implicit “deny all traffic” criteria statement at the end of every ACL.  
ML-Series ACL Support  
Both control-plane and data-plane ACLs are supported on the ML-Series card:  
•
Control-plane ACLs: ACLs used to filter control data that is processed by the CPU of the ML-Series  
card (for example, distribution of routing information, Internet Group Membership Protocol (IGMP)  
joins, and so on).  
•
Data-plane ACLs: ACLs used to filter user data being routed or bridged through the ML Series in  
hardware (for example, denying access to a host, and so on). These ACLs are applied to an interface  
in the input or output direction using the ip access-group command.  
The following apply when using data-plane ACLs on the ML-Series card:  
•
•
ACLs are supported on all interface types, including bridged interfaces.  
Reflexive and dynamic ACLs are not supported on the ML-Series card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
14-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 14 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.  
IP ACLs  
The following ACL styles for IP are supported:  
•
•
Standard IP ACLs: These use source addresses for matching operations.  
Extended IP ACLs: (Control plane only) These use source and destination addresses for matching  
operations and optional protocol type and port numbers for finer granularity of control.  
•
Named ACLs: These use source addresses for matching operations.  
Note  
By default, the end of the ACL contains an implicit deny statement for everything if it did not find a  
match before reaching the end. With standard ACLs, if you omit the mask from an associated IP host  
address ACL specification, 0.0.0.0 is assumed to be the mask.  
After creating an ACL, you must apply it to an interface, as shown in the “Applying the ACL to an  
Interface” section on page 14-4.  
Named IP ACLs  
You can identify IP ACLs with a name, but it must be an alphanumeric string. Named IP ACLs allow  
you to configure more IP ACLs in a router than if you used numbered ACLs. If you identify your ACL  
with an alphabetic rather than a numeric string, the mode and command syntax are slightly different.  
Consider the following before configuring named ACLs:  
•
•
A standard ACL and an extended ACL cannot have the same name.  
Numbered ACLs are also available, as described in the “Creating Numbered Standard and Extended  
IP ACLs” section on page 14-3.  
User Guidelines  
Keep the following in mind when you configure IP network access control:  
•
•
•
•
•
You can program ACL entries into Ternary Content Addressable Memory (TCAM).  
You do not have to enter a deny everything statement at the end of your ACL; it is implicit.  
You can enter ACL entries in any order without any performance impact.  
For every eight TCAM entries, the ML-Series card uses one entry for TCAM management purposes.  
Do not set up conditions that result in packets getting lost. This situation can happen when a device  
or interface is configured to advertise services on a network that has ACLs that deny these packets.  
•
IP ACLs are not supported for double-tagged (QinQ) packets. They will, however, be applied to IP  
packets entering on a QinQ access port.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
14-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 14 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 14-3  
Creating Named Standard IP ACLs, page 14-4  
Creating Named Extended IP ACLs (Control Plane Only), page 14-4  
Applying the ACL to an Interface, page 14-4  
Creating Numbered Standard and Extended IP ACLs  
Table 14-1 lists the global configuration commands used to create numbered standard and extended IP  
ACLs.  
Table 14-1  
Commands for Numbered Standard and Extended IP ACLs  
Command  
Purpose  
ML_Series(config)#access-list  
access-list-number  
{deny | permit} source [source-wildcard]  
Defines a standard IP ACL using a source address  
and wildcard.  
ML_Series(config)#access-list  
access-list-number {deny | permit}  
any  
Defines a standard IP ACL using an abbreviation  
for the source and source mask of 0.0.0.0  
255.255.255.255.  
ML_Series(config)# access-list  
access-list-number {deny | permit} protocol  
source source-wildcard destination  
destination-wildcard [precedence  
precedence] [tos tos]  
Defines an extended IP ACL number and the  
access conditions.  
ML_Series(config)# access-list  
access-list-number {deny | permit} protocol  
any any  
Defines an extended IP ACL using an  
abbreviation for a source and source wildcard of  
0.0.0.0 255.255.255.255, and an abbreviation for  
a destination and destination wildcard of 0.0.0.0  
255.255.255.255.  
ML_Series(config)# access-list  
access-list-number {deny | permit} protocol  
host source host destination  
Defines an extended IP ACL using an  
abbreviation for a source and source wildcard of  
source 0.0.0.0, and an abbreviation for a  
destination and destination wildcard of  
destination 0.0.0.0.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
14-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 14 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  
ML_Series(config)# ip access-list  
standard name  
Step 1  
Step 2  
Defines a standard IP ACL using an alphabetic  
name.  
ML_Series(config-std-nac1)# {deny |  
permit} {source [source-wildcard] | any}  
In access-list configuration mode, specifies one or  
more conditions as permitted or denied. This  
determines whether the packet is passed or dropped.  
ML_Series(config)# exit  
Step 3  
Exits access-list configuration mode.  
Creating Named Extended IP ACLs (Control Plane Only)  
To create a named extended IP ACL, perform the following procedure, beginning in global configuration  
mode:  
Command  
Purpose  
ML_Series(config)# ip access-list extended  
name  
Step 1  
Step 2  
Defines an extended IP ACL using an alphabetic  
name.  
ML_Series(config-ext-nacl)# {deny | permit}  
protocol source source-wildcard destination  
destination-wildcard [precedence  
precedence] [tos tos]  
In access-list configuration mode, specifies the  
conditions allowed or denied.  
Or:  
Defines an extended IP ACL using an abbreviation  
for a source and source wildcard of 0.0.0.0  
255.255.255.255, and an abbreviation for a  
destination and destination wildcard of 0.0.0.0  
255.255.255.255.  
or  
{deny | permit} protocol any any  
or  
{deny | permit} protocol host source host  
destination  
Or:  
Defines an extended IP ACL using an abbreviation  
for a source and source wildcard of source 0.0.0.0,  
and an abbreviation for a destination and  
destination wildcard of destination 0.0.0.0.  
Applying the ACL to an Interface  
After you create an ACL, you can apply it to one or more interfaces. ACLs can be applied on either the  
inbound or the outbound direction of an interface. When controlling access to an interface, you can use  
a name or number. If a standard ACL is applied, the ML-Series card compares the source IP address with  
the ACL. To apply an ACL to one or more interfaces, use the command in Table 14-2.  
Note  
IP standard ACLs applied to the ingress of a Bridge Group Virtual Interface (BVI) will be applied to all  
bridged IP traffic in the associated bridge-group, in addition to the BVI ingress traffic.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
14-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 14 Configuring Access Control Lists on the ML-Series Card  
Modifying ACL TCAM Size  
Table 14-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 13-3.  
Example 14-1 provides an example of modifying and verifying ACLs.  
Note  
To increase the ACL TCAM size, you must decrease another region’s TCAM size, such as IP,  
IP multicast, or L2 switching.  
Caution  
You need to increase the TCAM size if you see the following error message:  
Warning:Programming TCAM entries failed  
Please remove last ACL command to re-activate ACL operation.  
!<ACL number or name> <IP or IPX> <INPUT_ACL or OUTPUT_ACL> from TCAM group for !<interface>  
Please see the documentation to see if TCAM space can be  
increased on this platform to alleviate the problem.  
Example 14-1 Monitor and Verify ACLs  
ML_Series# show ip access-lists 1  
Standard IP access list 1  
permit 192.168.1.1  
permit 192.168.1.2  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
14-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 14 Configuring Access Control Lists on the ML-Series Card  
Modifying ACL TCAM Size  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
14-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
15  
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. Cisco does not  
recommend using its path protection feature in any particular topological network configuration.  
This chapter describes how to configure resilient packet ring (RPR) for the ML-Series card.  
This chapter contains the following major sections:  
•
•
•
•
•
•
•
•
•
•
•
•
Understanding RPR, page 15-1  
Configuring RPR, page 15-6  
Monitoring and Verifying RPR, page 15-16  
Add an ML-Series Card into an RPR, page 15-17  
Delete an ML-Series Card from an RPR, page 15-21  
Cisco Proprietary RPR KeepAlive, page 15-25  
Configuring Cisco Proprietary RPR KeepAlive, page 15-25  
Monitoring Cisco Propretary RPR KeepAlive, page 15-25  
Cisco Proprietary RPR Shortest Path, page 15-25|  
Configuring Shortest Path and Topology Discovery, page 15-25  
Monitoring and Verifying Shortest Path and Topolgy Discovery, page 15-25  
Redundant Interconnect, page 15-25  
Understanding RPR  
RPR is a new MAC protocol operating at the Layer 2 level. It is well suited for transporting Ethernet  
over a SONET ring topology and enables multiple ML-Series cards to become one functional network  
segment or shared packet ring (SPR). RPR overcomes the limitations of earlier schemes, such as IEEE  
802.1D Spanning Tree Protocol (STP), IEEE 802.1W Rapid Spanning Tree Protocol (RSTP), and  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 15 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.  
The point-to-point STS circuits are configured on the ONS node and are transported over the ONS node’s  
SONET topology with either protected or unprotected circuits.  
On circuits unprotected by the SONET mechanism, RPR provides resiliency without using the capacity  
of the redundant protection path that a SONET protected circuit would require. This frees this capacity  
for additional traffic. RPR also utilizes the bandwidth of the entire ring and does not block segments like  
STP or RSTP.  
Packet Handling Operations  
When an ML-Series card is configured with RPR and is made part of an SPR, the ML-Series card  
assumes a ring topology. If a packet is not destined for network devices bridged through the Ethernet  
ports of a specific ML-Series card, the ML-Series card simply continues to forward this transit traffic  
along the SONET circuit, relying on the circular path of the ring architecture to guarantee that the packet  
will eventually arrive at the destination. This eliminates the need to queue and process the packet flowing  
through the nondestination ML-Series card. From a Layer 2 or Layer 3 perspective, the entire RPR looks  
like one shared network segment.  
An ML-Series card configured with RPR has three basic packet-handling operations: bridge,  
pass-through, and strip. Figure 15-1 illustrates these operations. Bridging connects and passes packets  
between the Ethernet ports on the ML-Series and the packet-over-SONET (POS) ports used for the  
SONET circuit circling the ring. Pass-through lets the packets continue through the ML-Series card and  
along the ring, and stripping takes the packet off the ring and discards it.  
The RPR protocol, using the transmitted packet's header information, allows the interfaces to quickly  
determine the operation that needs to be applied to the packet. It also uses both the source and destination  
addresses of a packet to choose a ring direction. Flow-based load sharing helps ensure that all packets  
populated with equal source- and destination-address pairs will be sent in the same direction, and arrive  
at their destination in the correct order. Ring direction also enables the use of spatial reuse to increase  
overall ring aggregate bandwidth. Unicast packets are destination stripped. Destination stripping  
provides the ability to have simultaneous flows of traffic between different parts of an RPR. Traffic can  
be concurrently transmitted bidirectionally between adjacent nodes. It can also can span multiple nodes,  
effectively reusing the same ring bandwidth. Multicast packets are source stripped.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Understanding RPR  
Figure 15-1  
RPR Packet Handling Operations  
Strip  
Bridge  
ML-Series RPR  
Pass through  
Ring Wrapping  
RPR initiates ring wraps in the event of a fiber cut, node failure, node restoration, new node insertion,  
or other traffic problem. This protection mechanism redirects traffic to the original destination by  
sending it in the opposite direction around the ring after a link state change or after receiving SONET  
path level alarms. Ring wrapping on the ML-Series card allows convergence times of less than 50 ms.  
RPR convergence times are comparable to SONET and much faster than STP or RSTP.  
RPR on the ML-Series card survives both unidirectional and bidirectional transmission failures within  
the ring. Unlike STP or RSTP, RPR restoration is scalable. Increasing the number of ML-Series cards in  
a ring does not increase the convergence time.  
Ring wraps occur within 50 msec after the failure condition with the default spr wrap immediate  
configured. If spr wrap delay is configured, the wrap is delayed until the POS interface goes link-down.  
The link goes down after the time specified with the CLI pos trigger delay <msec>. If the circuits are  
VCAT then the Cisco IOS CLI command pos vcat defect delayed also needs to be configured. The delay  
helps ensure that when RPR is configured with SONET bandwidth protection, this Layer 1 protection  
has a chance to take effect before the Layer 2 RPR protection. If the interface goes down without a  
SONET error, then the carrier delay also take effect. Figure 15-2 illustrates ring wrapping.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Understanding RPR  
Figure 15-2  
RPR Ring Wrapping  
Ring Wrap  
Fiber Cut  
ML-Series RPR  
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.  
Note  
Note  
Note  
If the POS interfaces on the ML100T-8 cards on either 15310MA or 15310CL receives the  
SF-P condition, then the SPR ring does not wrap.  
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.  
ML-Series card POS interfaces normally send an alarm for signal label mismatch failure in the STS path  
overhead (PDI-P) to the far end when the POS link goes down or when RPR wraps. ML-Series card POS  
interfaces do not send PDI-P to the far-end when PDI-P is detected, when a remote defection indication  
alarm (RDI-P) is being sent to the far end, or when the only defects detected are generic framing  
procedure (GFP)-loss of frame delineation (LFD), GFP client signal fail (CSF), virtual concatenation  
(VCAT)-loss of multiframe (LOM), or VCAT-loss of sequence (SQM).  
RPR Framing Process  
The ML-Series card uses a proprietary RPR frame and HDLC or GFP-F framing. It attaches the RPR  
frame header to each Ethernet frame and encapsulates the RPR frame into the SONET payload for  
transport over the SONET topology. The RPR header is removed at the egress ML-Series card.  
Figure 15-3 illustrates the RPR frame.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Understanding RPR  
Figure 15-3  
RPR Frame for ML-Series Card  
1 byte 1 byte 1 byte  
Flag Add Control Protocol  
0x7E 0x0F 0x00 0x0042  
2 bytes  
68-1522 bytes  
RPR Payload  
2-4 bytes 1 byte  
CRC  
Flag  
0x7F  
4 byte  
4 bytes  
60-1514 bytes  
Ethernet Payload  
RPR Address RPR Control  
7 byte 1 byte 6 bytes 6 bytes 6 bytes 46-1500 bytes 4 bytes  
Preamble SFD DA SA Ln/Type Data/Pad FCS  
The RPR framing and header includes a number of fields, including four bytes for source and destination  
station information and another four bytes for RPR control and quality of service (QoS). Figure 15-4  
illustrates the RPR frame format. Table 15-1 defines the most important fields.  
Figure 15-4  
RPR Frame Fields  
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0  
Protocol (RPR V1)  
Destination ID  
Source ID  
Destination Station  
Source Station  
D
E
PRI W B  
D
TTL  
D D  
W S  
Wrap Station  
V
RSVD Type  
Payload (Ethernet Frame)  
Table 15-1  
Definitions of RPR Frame Fields  
Destination Station  
An eight-bit field specifying the MAC address of a specific ML-Series card in  
the RPR as the destination. It has two well-known addresses, 0xff for Multicast  
DA-MAC and 0x00 for Unknown DA-MAC.  
Source Station  
An eight-bit field specifying the MAC address of a specific ML-Series card in  
the RPR as the source.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
Table 15-1  
Definitions of RPR Frame Fields  
PRI  
DE  
A three-bit QoS class of service (CoS) field that establishes RPR priority.  
A one-bit field for the discard eligible flag.  
TTL  
Type  
A nine-bit field for the frame’s time to live.  
A field indicating whether the packet is data or control.  
MAC Address and VLAN Support  
RPR increases the total number of MAC addresses supported because the MAC IDs of packets that pass  
through an ML-Series card are not recorded by that ML-Series card. The ML-Series card only records  
the MAC IDs of the packets that are bridged or stripped by that ML-Series card. This allows a greater  
number of MAC addresses in the collective address tables of the RPR.  
VLANs on RPR require less interface configuration than VLANs on STP and RSTP, which require  
configuration on all the POS interfaces in the ring. RPR VLANs only require configuration on SPR  
interfaces that bridge or strip packets for that VLAN.  
The ML-Series card still has an architectural maximum limit of 255 VLAN/bridge-group per ML-Series  
card. But because the ML-Series card only needs to maintain the MAC address of directly connected  
devices, a greater total number of connected devices are allowed on an RPR network.  
RPR QoS  
The ML-Series card’s RPR relies on the QoS features of the ML-Series card for efficient bandwidth  
utilization with service level agreement (SLA) support. ML-Series card QoS mechanisms apply to all  
SONET traffic on the ML-Series card, whether passed-through, bridged, or stripped. For detailed RPR  
QoS information see the QoS on RPR section of Chapter 15, “Configuring Resilient Packet Ring on the  
ML-Series Card.”  
CTM and RPR  
The Cisco Transport Manager (CTM) is an element management system (EMS) designed to integrate  
into an overall network management system (NMS) and interface with other higher level management  
tools. CTM supports RPR provisioning on ML-Series cards. For more information, refer to the  
Cisco Transport Manager User Guide.  
Configuring RPR  
You need to use both CTC and Cisco IOS to configure RPR for the ML-Series card. CTC is the graphical  
user interface (GUI) that serves as the enhanced craft tool for specific ONS node operations, including  
the provisioning of the point-to-point SONET circuits required for RPR. Cisco IOS is used to configure  
RPR on the ML-Series card and its interfaces.  
Successfully creating an RPR requires several consecutive procedures:  
1. Connecting the ML-Series Cards with Point-to-Point STS Circuits, page 15-7 (CTC or TL1)  
2. Configuring CTC Circuits for RPR, page 15-7 (CTC or TL1)  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
3. Configuring RPR Characteristics and the SPR Interface on the ML-Series Card, page 15-9  
(Cisco IOS)  
4. Assigning the ML-Series Card POS Ports to the SPR Interface, page 15-11 (Cisco IOS)  
5. Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces, page 15-13 (Cisco IOS)  
6. Verifying Ethernet Connectivity Between RPR Ethernet Access Ports, page 15-15 (Cisco IOS)  
7. CRC Threshold Configuration and Detection, page 15-15  
Note  
Transaction Language One (TL1) can be used to provision the required SONET point-to-point circuits  
instead of CTC.  
Connecting the ML-Series Cards with Point-to-Point STS Circuits  
You connect the ML-Series cards in an RPR through point-to-point STS circuits. These circuits use the  
SONET network and are provisioned using CTC in the normal manner for provisioning optical circuits.  
Configuring CTC Circuits for RPR  
These are the guidelines for configuring the CTC circuits required by RPR:  
•
Leave all CTC Circuit Creation Wizard options at their default settings, except Fully Protected  
Path in the Circuit Routing Preferences dialog box. Fully Protected Path provides SONET  
protection and should be unchecked. RPR normally provides the Layer 2 protection for SPR circuits.  
•
Check Using Required Nodes and Spans to route automatically in the Circuit Routing Preferences  
dialog box. If the source and destination nodes are adjacent on the ring, exclude all nodes except the  
source and destination in the Circuit Routing Preferences dialog box. This forces the circuit to be  
routed directly between source and destination and preserves STS circuits, which would be  
consumed if the circuit routed through other nodes in the ring. If there is a node or nodes that do not  
contain an ML-Series card between the two nodes containing ML-Series cards, include this node or  
nodes in the included nodes area in the Circuit Routing Preference dialog box, along with the source  
and destination nodes.  
•
•
Keep in mind that ML-Series card STS circuits do not support unrelated circuit creation options,  
such as the following check box titles in CTC, unidirectional traffic, creating cross-connects only  
(TL1-like), interdomain (unified control plane [UCP]), protected drops, subnetwork connection  
protection (SCNP), or path protectionpath selectors.  
A best practice is to configure SONET circuits in an east-to-west or west-to-east configuration, from  
Port 0 (east) to Port 1 (west) or Port 1 (east) to Port 0 (west), around the SONET ring. Do not  
configure Port 0 to Port 0 or Port 1 to Port 1. The east-to-west or west-to-east setup is also required  
in order for the CTM network management software to recognize the ML-Series configuration as an  
SPR.  
Detailed CTC circuit procedures are available in the “Create Circuits and VT Tunnels” chapter of the  
Cisco ONS 15454 Procedure Guide.  
CTC Circuit Configuration Example for RPR  
Figure 15-5 illustrates an example of a three-node RPR.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
Figure 15-5  
Three-Node RPR Example  
SPR Station-ID 1  
POS 1  
POS 0  
POS 1  
POS 0  
POS 1  
SPR 1  
SPR Station-ID 2  
POS 0  
SPR Station-ID 3  
= STS circuit created on CTC  
The three-node RPR in Figure 15-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.  
Caution  
The specific steps in the following procedure are for the topology shown in the example. Your own  
specific steps will vary according to your network. Do not attempt this procedure without obtaining a  
detailed plan or method of procedure from an experienced network architect.  
To configure the circuits, you need to create three circuits in CTC:  
•
•
•
Create a circuit from Node 1, POS Port 0 to Node 2, POS Port 1.  
Create a circuit from Node 2, POS Port 0 to Node 3, POS Port 1.  
Create a circuit from Node 3, POS Port 0 to Node 1, POS Port 1.  
Step 1  
Step 2  
In CTC, log into Node 1 and navigate to the CTC card view for the ML-Series card that will be in the  
RPR.  
Click the Circuits > Create tabs.  
The first page of the Circuit Creation wizard appears.  
In the Circuit Type list, select STS.  
Click Next.  
Step 3  
Step 4  
The Circuit Attributes page appears.  
Type a circuit name in the Name field.  
Step 5  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
Step 6  
Step 7  
Select the relevant size of the circuit from the Size drop-down list, and the appropriate state from the  
State list.  
Click Next.  
The Source page appears.  
Step 8  
Step 9  
Select Node 1 as the source node from the node drop-down list.  
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.  
Step 11 Select Node 2 as the destination node from the Node drop-down list.  
Step 12 Select the ML-Series card from the Slot drop-down list, and choose 1 (POS) from the Port drop-down  
list.  
Step 13 Click Next.  
The Circuit Routing Preferences page appears.  
Step 14 Uncheck the Fully Protected Path check box.  
Step 15 Click Next.  
The Circuit Constraints for Automatic Routing page appears.  
Step 16 Click the Node 1 icon to select it and click Next.  
The Route Review/Edit page appears.  
Step 17 Click Finish.  
You have now completed the initial circuit for the RPR.  
Note  
A TPTFAIL alarm might appear on CTC when the circuit is created. This alarm will disappear after the  
POS ports are enabled during the “Assigning the ML-Series Card POS Ports to the SPR Interface”  
procedure on page 15-11.  
Step 18 Build the second circuit between POS 0 on Node 2 and POS 1 on Node 3. Use the same procedure  
described in Steps 1 through 17, but substitute Node 2 for Node 1 and Node 3 for Node 2.  
Step 19 Build the third circuit between POS 0 on Node 3 and POS 1 on Node 1. Use the same procedure  
described in Steps 1 through 17, but substitute Node 3 for Node 1 and Node 1 for Node 2.  
Now all of the POS ports in all three nodes are connected by STS point-to-point circuits in an  
east-to-west pattern, as shown in Figure 15-5 on page 15-8.  
Step 20 The CTC circuit process is complete.  
Configuring RPR Characteristics and the SPR Interface on the ML-Series Card  
You configure RPR on the ML-Series cards by creating an SPR interface using the Cisco IOS  
command-line interface (CLI). The SPR interface is a virtual interface for the SPR. An ML-Series card  
supports a single SPR interface with a single MAC address. It provides all the normal attributes of a  
Cisco IOS virtual interface, such as support for default routes.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 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. An  
SPR interface is considered a trunk port, and like all trunk ports, subinterfaces must be configured for  
the SPR interface for it to join a bridge group.  
The physical POS interfaces on the ML-Series card are the only members eligible for the SPR interface.  
One POS port is associated with the SONET circuit heading east around the ring from the node, and the  
other POS port is associated with the circuit heading west. When the SPR interface is used and the POS  
ports are associated, RPR encapsulation is used on the SONET payload.  
Caution  
In configuring an SPR, if one ML-Series card is not configured with an SPR interface, but valid STS  
circuits connect this ML-Series card to the other ML-Series cards in the SPR, no traffic will flow  
between the properly configured ML-Series cards in the SPR, and no alarms will indicate this condition.  
Cisco recommends that you configure all of the ML-Series cards in an SPR before sending traffic.  
Caution  
Note  
Do not use native VLANs for carrying traffic with RPR.  
RPR on the ML-Series card is only supported with the default LEX encapsulation, a special  
CISCO-EOS-LEX encapsulation for use with Cisco ONS Ethernet line cards.  
RPR needs to be provisioned on each ML-Series card that is in the RPR. To provision RPR, perform the  
following procedure, beginning in global configuration mode:  
Command  
Purpose  
Router(config)# bridge irb  
Step 1  
Step 2  
Step 3  
Step 4  
Enables the Cisco IOS software to both route and bridge  
a given protocol on separate interfaces within a single  
ML-Series card.  
Router(config)# interface spr 1  
Creates the SPR interface on the ML-Series card or  
enters the SPR interface configuration mode. The only  
valid SPR number is 1.  
Router(config-if)# spr station-id  
station-ID-number  
Configures a station ID. 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.  
Router(config-if)# spr wrap  
{ immediate | delayed }  
(Optional) Sets the RPR ring wrap mode to either wrap  
traffic the instant it detects a SONET path alarm or to  
wrap traffic after the delay, which gives the SONET  
protection time to register the defect and declare the link  
down. Use immediate if RPR is running over  
unprotected SONET circuits. Use delayed for  
bidirectional line switched rings (BLSR), path  
protection, multiplex section-shared protection ring  
(MS-SPRing), or SNCP protected circuits.  
The default setting is immediate.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
Command  
Purpose  
Router(config-if)# carrier-delay msec  
milliseconds  
Step 5  
(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.  
Router(config-if)# [no] spr  
load-balance{ auto | port-based }  
Step 6  
(Optional) Specifies the RPR load-balancing scheme for  
unicast packets. The port-based load balancing option  
maps even ports to the POS 0 interface and odd ports to  
the POS 1 interface. The default auto option balances the  
load based on the MAC addresses or source and  
destination addresses of the IP packet.  
Router(config-if)# end  
Step 7  
Exits to privileged EXEC mode.  
Router# copy running-config  
startup-config  
Step 8  
(Optional) Saves configuration changes to NVRAM.  
Assigning the ML-Series Card POS Ports to the SPR Interface  
Caution  
The SPR interface is the routed interface. Do not enable Layer 3 addresses or assign bridge groups on  
the POS interfaces assigned to the SPR interface.  
Caution  
When traffic coming in on an SPR interface needs to be policed, the same input service policy needs to  
be applied to both POS ports that are part of the SPR interface.  
The POS ports require LEX encapsulation to be used in RPR. The first step of RPR configuration is to  
set the encapsulation of POS 0 and POS 1 ports to LEX.  
Each of the ML-Series card’s two POS ports must also be assigned to the SPR interface. To configure  
LEX encapsulation and assign the POS interfaces on the ML-Series card to the SPR, perform the  
following procedure, beginning in global configuration mode:  
Command  
Purpose  
Router(config)# interface pos 0  
Step 1  
Step 2  
Step 3 (  
Enters the interface configuration mode to configure the  
first POS interface that you want to assign to the SPR.  
Router(config-if)# encapsulation lex  
Sets POS interface encapsulation as LEX (default). RPR  
on the ML-Series card requires LEX encapsulation.  
Router(config-if)# spr-intf-id  
shared-packet-ring-number  
Assigns the POS interface to the SPR interface. The  
shared packet ring number must be 1, which is the only  
shared packet ring number that you can assign to the SPR  
interface.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
Command  
Purpose  
Router(config-if)# carrier-delay msec  
milliseconds  
Step 4  
(Optional) Sets the carrier delay time. The default setting  
is 200 msec, which is optimum for SONET protected  
circuits.  
Note  
The default unit of time for setting the carrier  
delay is seconds. The msec command resets the  
time unit to milliseconds.  
Router(config-if)# pos trigger defect  
ber_sd-b3  
Step 5  
(Optional) Configures a trigger to bring down the POS  
interface when the SONET bit error rate exceeds the  
threshold set for the signal degrade alarm. Bringing the  
POS interface down initiates the RPR wrap.  
This command is recommended for all RPR POS  
interfaces, since excessive SONET bit errors can cause  
packet loss on RPR traffic.  
Note  
This command should not be used when a Cisco  
ONS 15310 is part of the ring. It may cause  
inconsistent RPR wrapping.  
Router(config-if)# no shutdown  
Step 6  
Step 7  
Enables the POS port.  
Router(config-if)# interface pos 1  
Enters the interface configuration mode to configure the  
second POS interface that you want to assign to the SPR.  
Router(config-if)# encapsulation lex  
Step 8  
Step 9  
Sets POS interface encapsulation as LEX (default). RPR  
on the ML-Series card requires LEX encapsulation.  
Router(config-if)# spr-intf-id  
shared-packet-ring-number  
Assigns the POS interface to the SPR interface. The  
shared packet ring number must be 1 (the same shared  
packet ring number that you assigned in Step 3), which is  
the only shared packet ring number that you can assign  
to the SPR interface.  
Router(config-if)# carrier-delay msec  
milliseconds  
Step 10  
Step 11  
(Optional) Sets the carrier delay time. The default setting  
is 200 milliseconds, which is optimum for SONET  
protected circuits.  
Router(config-if)# pos trigger defect  
ber_sd-b3  
(Optional) Configures a trigger to bring down the POS  
interface when the SONET bit error rate exceeds the  
threshold set for the signal degrade alarm. Bringing the  
POS interface down initiates the RPR wrap.  
This command is recommended for all RPR POS  
interfaces since excessive SONET bit errors can cause  
packet loss on RPR traffic.  
Router(config-if)# no shutdown  
Router(config-if)# end  
Step 12  
Step 13  
Step 14  
Enables the POS port.  
Exits to privileged EXEC mode.  
Router# copy running-config  
startup-config  
(Optional) Saves the configuration changes to NVRAM.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 15 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. The ML-Series card will not forward any  
traffic by default, including untagged or VLAN 1 tagged packets.  
For any RPR traffic to be bridged on an ML-Series card, a bridge group needs to be created for that  
traffic. Bridge groups maintain the bridging and forwarding between the interfaces on the ML-Series  
card and are locally significant. Interfaces not participating in a bridge group cannot forward bridged  
traffic.  
To create a bridge group for RPR, you determine which Ethernet interfaces need to be in the same bridge  
group, create the bridge group, and associate these interfaces with the bridge group. Then associate the  
SPR interface with the same bridge group to provide transport across the RPR infrastructure.  
Figure 15-6 illustrates a bridge group spanning the ML-Series card interfaces, including the SPR virtual  
interface of RPR.  
Figure 15-6  
RPR Bridge Group  
ML-Series Card  
Ethernet  
Port 0  
POS 0  
POS 1  
SPR (RPR)  
Interface  
Bridge Group  
Ethernet  
Port 1  
Caution  
All Layer 2 network redundant links (loops) in the connecting network, except the RPR topology, must  
be removed for correct RPR operation. Or if loops exist, you must configure STP/RSTP.  
To configure the needed interfaces, perform the following procedure, beginning in global configuration  
mode:  
Command  
Purpose  
Router(config)# interface type number  
Step 1  
Enters interface configuration mode for the Ethernet  
interface joining the bridge group.  
Router(config-if)# no shutdown  
Step 2  
Step 3  
Enables the interface.  
Router(config-if)# bridge-group  
bridge-group-number  
Creates the specified bridge group and assigns the bridge  
group to the interface. Creating the bridge from the  
interface configuration disables STP or RSTP  
(spanning-disabled), which is recommended for RPR.  
Router(config)# interface spr1  
Step 4  
Step 5  
Enters interface configuration mode for the SPR  
Router(config-subif)# bridge-group  
bridge-group-number  
Associates the SPR interface to the specified bridge  
group.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Configuring RPR  
RPR Cisco IOS Configuration Example  
Figure 15-5 on page 15-8 shows a complete example of an RPR Cisco IOS configuration. The associated  
Cisco IOS code is provided in Examples 15-1, 15-2, and 15-3. The configuration assumes that ML-Series  
card POS ports are already linked by point-to-point SONET circuits configured through CTC.  
Example 15-1 SPR Station-ID 1 Configuration  
bridge irb  
interface SPR1  
no ip address  
no keepalive  
spr station-id 1  
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  
no ip address  
carrier-delay msec 0  
spr-intf-id 1  
crc 32  
interface POS1  
no ip address  
carrier-delay msec 0  
spr-intf-id 1  
crc 32  
!
Example 15-2 SPR Station-ID 2 Configuration  
bridge irb  
interface SPR1  
no ip address  
no keepalive  
spr station-id 2  
bridge-group 10  
bridge-group 10 spanning-disabled  
interface FastEthernet0  
no ip address  
bridge-group 10  
bridge-group 10 spanning-disabled  
interface FastEthernet1  
no ip address  
shutdown  
interface POS0  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 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 15-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  
no ip address  
spr-intf-id 1  
crc 32  
interface POS1  
no ip address  
spr-intf-id 1  
crc 32  
!
Verifying Ethernet Connectivity Between RPR Ethernet Access Ports  
After successfully completing the procedures to provision an RPR, you can test Ethernet connectivity  
between the Ethernet access ports on the separate ML-Series cards using your standard Ethernet  
connectivity testing.  
CRC Threshold Configuration and Detection  
You can configure a span shutdown when the ML-Series card receives CRC errors at a rate that exceeds  
the configured threshold and configured soak time. For this functionality to work in an SPR ring, make  
the configurations on the POS members of SPR interface specified in CRC Threshold Configuration,  
page 4-11.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 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 15-4) or the show run interface spr 1 command (Example 15-5).  
Example 15-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.0000)  
MTU 1500 bytes, BW 290304 Kbit, DLY 100 usec,  
reliability 255/255, txload 1/255, rxload 1/255  
Encapsulation: Cisco-EoS-LEX, loopback not set  
Keepalive not set  
DTR is pulsed for 27482 seconds on reset, Restart-Delay is 65 secs  
ARP type: ARPA, ARP Timeout 04:00:00  
No. of active members in this SPR interface: 2  
Member 0 : POS1  
Member 1 : POS0  
Last input 00:00:38, output never, output hang never  
Last clearing of "show interface" counters never  
Input queue: 0/150/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: fifo  
Output queue: 0/80 (size/max)  
5 minute input rate 0 bits/sec, 0 packets/sec  
5 minute output rate 0 bits/sec, 0 packets/sec  
37385 packets input, 20993313 bytes  
Received 0 broadcasts (0 IP multicast)  
0 runts, 0 giants, 0 throttles  
0 parity  
2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored  
0 input packets with dribble condition detected  
37454 packets output, 13183808 bytes, 0 underruns  
0 output errors, 0 applique, 4 interface resets  
0 babbles, 0 late collision, 0 deferred  
0 lost carrier, 0 no carrier  
0 output buffer failures, 0 output buffers swapped out  
0 carrier transitions  
Example 15-5 Example of show run interface spr 1 Output  
ML-Series# show run interface spr 1  
Building configuration...  
Current configuration : 141 bytes  
interface SPR1  
no ip address  
no keepalive  
spr station-id 2  
bridge-group 10  
bridge-group 10 spanning-disabled  
hold-queue 150 in  
end  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 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. You can also  
add an ML-Series card to a node that is already part of the SONET topology.  
The following example has a two-node RPR with two STS circuits connecting the ML-Series cards. One  
circuit will be deleted. The RPR will wrap traffic on the remaining circuit with as little as a one ping  
loss. The third node and ML-Series card are then added in, and the spans and circuits for this card are  
created.  
Figure 15-7 shows the existing two-node RPR with the single STS circuit and span that will be deleted.  
Figure 15-7  
Two-Node RPR Before the Addition  
Adjacent  
Node 1  
POS 0  
POS 1  
SPR 1  
POS 1  
New Node  
POS 0  
Adjacent  
Node 2  
This STS circuit  
will be deleted.  
= STS circuit created on CTC  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Add an ML-Series Card into an RPR  
Figure 15-8 shows the RPR after the third node is added with the two new STS circuits and spans that  
will be added.  
Figure 15-8  
Three-Node RPR After the Addition  
Adjacent Node 1  
POS 1  
POS 0  
POS 1  
POS 0  
POS 0  
New Node  
SPR 1  
Adjacent Node 2  
POS 1  
= STS circuit created on CTC  
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.  
Shut down the POS ports on the adjacent ML-Series cards for the STS circuit that will be deleted to  
initiate the RPR wrap.  
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 STS circuit that will be replaced by the new circuits. (In Figure 15-7, this is the circuit  
between Adjacent Node 2, POS 0 and Adjacent Node 1, POS 1.)  
•
•
Insert the new node into the ring topology if the node is not already part of the topology.  
Install the ML-Series card and load your initial configuration file or otherwise do an initial  
configuration of the ML-Series card.  
•
•
Ensure the new node is configured with RPR before its POS ports are manually enabled or enabled  
through the configuration file.  
Create an STS circuit from one of the POS ports of an existing adjacent ML-Series card to a POS  
port on the new ML-Series card. (In Figure 15-8, this is the circuit between Adjacent Node 2,  
POS Port 0 and New Node, POS Port 1.)  
•
Create a second STS circuit from one of the POS ports of the other existing adjacent ML-Series card  
to the remaining POS port on the new ML-Series card. (In Figure 15-8, this is the circuit between  
New Node, POS Port 0 and Adjacent Node 1, POS Port 1.)  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Add an ML-Series Card into an RPR  
•
•
•
•
Configure the new ML-Series card to join the RPR and enable the POS ports, if the initial  
configuration file did not already do this.  
Enable the POS ports on the existing adjacent ML-Series cards that connect to the new ML-Series  
card. (In Figure 15-8, these are Adjacent Node 1, POS Port 1 and Adjacent Node 2, POS Port 0.)  
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.  
Caution  
The specific steps in the following procedure are for the topology in the example. Your own steps will  
vary according to your network design. Do not attempt this procedure without obtaining a detailed plan  
or method of procedure from an experienced network architect.  
Adding an ML-Series Card into an RPR  
To add an ML-Series card to the RPR in the example, complete the following procedure:  
Step 1  
Step 2  
Start a Cisco IOS CLI session for the ML-Series card in the first adjacent node. This is Adjacent Node  
1 in Figure 15-7.  
Complete the following Cisco IOS configuration on the ML-Series card in the first adjacent node,  
beginning in global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at one  
endpoint of the circuit to be deleted.  
Router(config-if)# shutdown  
Closes the interface, which initiates the RPR wrap.  
Step 3  
Step 4  
Start a Cisco IOS CLI session for the ML-Series card in Adjacent Node 2, as shown in Figure 15-7.  
Complete the following Cisco IOS configuration on the Adjacent Node 2 ML-Series card, beginning in  
global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at one  
endpoint of the circuit to be deleted.  
Router(config-if)# shutdown  
Closes the interface.  
Step 5  
Step 6  
In CTC, log into Adjacent Node 1.  
Double-click the ML-Series card in Adjacent Node 1.  
The card view appears.  
Step 7  
Step 8  
Step 9  
Click the Circuits tab.  
Click the Circuits subtab.  
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 circuit to be deleted.  
The circuit entry is in node-name/card-slot/port-number format, such as Node-1/s12(ML100T)/pPOS-0.  
Step 10 Click the circuit entry to highlight it.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Add an ML-Series Card into an RPR  
Step 11 Click Delete.  
A confirmation dialog box appears.  
Step 12 Click Yes.  
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. Refer  
to the “Add and Remove Nodes” chapter of the Cisco ONS 15454 Procedure Guide.  
Step 15 If the ML-Series card in the new node is not already installed, install the card in the node. Refer to the  
“Install the Cisco ONS 15310-CL” or “Install the Cisco ONS 15310-MA” chapters of the  
Cisco ONS 15454 Procedure Guide.  
Step 16 Upload the initial startup configuration file for the new ML-Series card. If you do not have a prepared  
startup configuration file, manually create a startup configuration file.  
Caution  
Ensure the new node is configured with RPR before its POS ports are manually enabled or enabled  
through the configuration file.  
Step 17 Build an STS circuit with a circuit state of In Service (IS) from the available POS port on  
Adjacent Node 1 to the New Node, as shown in Figure 15-8. On the New Node, use the POS port with  
the interface-number that does not match the interface-number of the available POS port on  
Adjacent Node 1. For example, POS Port 0 on Adjacent Node 1would connect to POS Port 1 on the  
New Node.  
For detailed steps for building the circuit, see the “Configuring CTC Circuits for RPR” section on  
page 15-7.  
Note  
A best practice is to configure SONET circuits in an east-to-west or west-to-east configuration,  
from Port 0 (east) to Port 1 (west) or Port 1 (east) to Port 0 (west), around the SONET ring.  
Step 18 Build an STS circuit with a circuit state of IS from the available POS port on Adjacent Node 2 to the  
remaining POS port on the New Node, as shown in Figure 15-8.  
Step 19 Start or resume a Cisco IOS CLI session for the ML-Series card in Adjacent Node 1, as shown in  
Figure 15-7.  
Step 20 Complete the following Cisco IOS configuration, beginning in global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at one  
endpoint of the first newly created circuit.  
Router(config-if)# no shutdown  
Enables the port.  
Step 21 Start a Cisco IOS CLI session for the ML-Series card in Adjacent Node 2, as shown in Figure 15-7.  
Step 22 Complete the following Cisco IOS configuration on the Adjacent Node 2 ML-Series card, beginning in  
global configuration mode:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Delete an ML-Series Card from an RPR  
Router(config)# interface pos  
interface-number  
a.  
Enters interface configuration mode for the POS port at one  
endpoint of the second newly created circuit.  
Router(config-if)# no shutdown  
b.  
Enables the port.  
Step 23 Use a test set to verify that Ethernet connectivity exists on the RPR.  
Step 24 Monitor Ethernet traffic and routing tables for at least one hour after the node insertion.  
Stop. You have completed this procedure.  
Delete an ML-Series Card from an RPR  
An existing RPR might need an ML-Series card deleted. This can be done without taking down data  
traffic due to the RPR wrapping capability and ring architecture.  
The following example has a three-node RPR with three STS circuits connecting the ML-Series cards.  
Two circuits will be deleted. The RPR will wrap traffic on the remaining circuit with as little as a one  
ping loss. The third node and ML-Series card are then deleted and a new STS circuit is created between  
the two remaining cards.  
Figure 15-9 shows the existing three-node RPR with all three STS circuits and spans. Figure 15-10  
shows the RPR after the third node, circuits, and spans are deleted and the new STS circuit and span are  
added.  
Figure 15-9  
Three-Node RPR Before the Deletion  
Adjacent Node 1  
POS 1  
POS 0  
POS 1  
POS 0  
POS 0  
SPR 1  
Delete Node  
Adjacent Node 2  
POS 1  
= STS circuit created on CTC  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Delete an ML-Series Card from an RPR  
Figure 15-10  
Two-Node RPR After the Deletion  
Adjacent  
Node 1  
POS 0  
POS 1  
SPR 1  
POS 1  
Deleted Node  
POS 0  
Adjacent  
Node 2  
This STS circuit  
was created after the deletion.  
= STS circuit created on CTC  
To delete an ML-Series card from 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 spans that will be  
deleted.  
Shut down the POS ports on the adjacent ML-Series cards for the STS circuits that will be deleted  
to initiate the RPR wrap.  
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 15-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.)  
•
•
•
Remove the Delete Node from the ring topology if desired.  
Physically remove the delete ML-Series card from the node if desired.  
Create an STS circuit from the available POS port of one of the remaining adjacent ML-Series cards  
to the available POS port on the other remaining adjacent ML-Series card. (In Figure 15-10, this is  
the circuit between Adjacent Node 2, POS Port 0 and Adjacent Node 1, POS Port 1.)  
•
•
•
Enable the POS ports on the existing adjacent ML-Series cards.(In Figure 15-10, this is the  
Adjacent Node 2, POS Port 0 and the Adjacent Node 1, POS Port 1.)  
Test Ethernet connectivity between the access ports on the adjacent ML-Series card with a test set  
to validate the two-node RPR.  
Monitor Ethernet traffic and existing routing protocols for at least an hour after the node deletion.  
Caution  
The specific steps in the following procedure are for the topology in the example. Your own steps will  
vary according to your network design. Do not attempt this procedure without obtaining a detailed plan  
or method of procedure from an experienced network architect.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Delete an ML-Series Card from an RPR  
Deleting an ML-Series Card from an RPR  
To delete an ML-Series card from an RPR, complete the following procedure:  
Step 1  
Step 2  
Start a Cisco IOS CLI session for the ML-Series card on the first adjacent node. This is Adjacent Node  
1 in Figure 15-9.  
Complete the following Cisco IOS configuration on the ML-Series card in the first adjacent node,  
beginning in global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at the  
end of the circuit directly connected to the Delete Node.  
Router(config-if)# shutdown  
Closes the interface, which initiates the RPR wrap.  
Step 3  
Step 4  
Start a Cisco IOS CLI session for the ML-Series card in Adjacent Node 2, as shown in Figure 15-9.  
Complete the following Cisco IOS configuration on the Adjacent Node 2 ML-Series card, beginning in  
global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at the  
end of the circuit directly connected to the Delete Node.  
Router(config-if)# shutdown  
Closes the interface.  
Step 5  
Step 6  
Log into Adjacent Node 1 with CTC.  
Double-click the ML-Series card in Adjacent Node 1.  
The card view appears.  
Step 7  
Step 8  
Step 9  
Click the Circuits tab.  
Click the Circuits subtab.  
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.  
Step 10 Click the circuit entry to highlight it.  
Step 11 Click Delete.  
A confirmation dialog box appears.  
Step 12 Click Yes.  
Step 13 Verify that Ethernet connectivity still exists between the Ethernet access ports on Adjacent Node 1 and  
Adjacent Node 2 by using a test set.  
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 Log into Adjacent Node 2 with CTC.  
Step 15 Double-click the ML-Series card in Adjacent Node 2.  
The card view appears.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-23  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Delete an ML-Series Card from an RPR  
Step 16 Click the Circuits tab.  
Step 17 Click the Circuits subtab.  
Step 18 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 second circuit to be deleted.  
The circuit entry is in node-name/card-slot/port-number format, such as Node-1/s12(ML100T)/pPOS-0.  
Step 19 Click the circuit entry to highlight it.  
Step 20 Click Delete.  
The confirmation dialog box appears.  
Step 21 Click Yes.  
Step 22 If the new node will no longer be an active node in the SONET ring topology, delete the node from the  
ring. Refer to the “Add and Remove Nodes” chapter of the Cisco ONS 15454 Procedure Guide.  
Step 23 If the ML-Series card in the new node is to be deleted in CTC and physically removed, do so now. Refer  
to the “Install the Cisco ONS 15310-CL” or “Install the Cisco ONS 15310-MA” chapters of the  
Cisco ONS 15454 Procedure Guide.  
Step 24 Build an STS circuit with a circuit state of IS from the available POS port on Adjacent Node 1 to the  
available POS port on Adjacent Node 2, as shown in Figure 15-10. For detailed steps on building the  
circuit, see “Configuring CTC Circuits for RPR” section on page 15-7.  
Note  
A best practice is to configure SONET circuits in an east-to-west or west-to-east configuration,  
from Port 0 (east) to Port 1 (west) or Port 1 (east) to Port 0 (west), around the SONET ring.  
Step 25 Start or resume a Cisco IOS CLI session for the ML-Series card in Adjacent Node 1.  
Step 26 Complete the following Cisco IOS configuration for the ML-Series card in Adjacent Node 1, beginning  
in global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at one  
endpoint of the first newly created circuit.  
Router(config-if)# no  
shutdown  
Enables the port.  
Step 27 Start a Cisco IOS CLI session for the ML-Series card in Adjacent Node 2.  
Step 28 Complete the following Cisco IOS configuration on the Adjacent Node 2 ML-Series card, beginning in  
global configuration mode:  
Router(config)# interface pos  
interface-number  
a.  
b.  
Enters interface configuration mode for the POS port at one  
endpoint of the second newly created circuit.  
Router(config-if)# no  
shutdown  
Enables the port.  
Step 29 Use a test set to verify that Ethernet connectivity exists on the RPR.  
Step 30 Monitor Ethernet traffic and routing tables for at least one hour after the node deletion.  
Stop. You have completed this procedure.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-24  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Cisco Proprietary RPR KeepAlive  
Cisco Proprietary RPR KeepAlive  
Please see Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide, Chapter 17.  
Configuring Cisco Proprietary RPR KeepAlive  
Please see Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide, Chapter 17.  
Monitoring Cisco Propretary RPR KeepAlive  
Please see Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide, Chapter 17.  
Cisco Proprietary RPR Shortest Path  
Please see Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide, Chapter 17.  
Configuring Shortest Path and Topology Discovery  
Please see Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide, Chapter 17.  
Monitoring and Verifying Shortest Path and Topolgy Discovery  
Please see Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide, Chapter 17.  
Redundant Interconnect  
Redundant Interconnect is supported only on Cisco ONS 15454 platform.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-25  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Chapter 15 Configuring Resilient Packet Ring on the ML-Series Card  
Redundant Interconnect  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
15-26  
Download from Www.Somanuals.com. All Manuals Search And Download.  
C H A P T E R  
16  
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 16-1  
Disabling the Console Port on the ML-Series Card, page 16-2  
Secure Login on the ML-Series Card, page 16-2  
Secure Shell on the ML-Series Card, page 16-2  
RADIUS on the ML-Series Card, page 16-6  
RADIUS Relay Mode, page 16-6  
RADIUS Stand Alone Mode, page 16-7  
Understanding Security  
The ML-Series card includes several security features. Some of these features operate independently  
from the ONS node where the ML-Series card is installed. Others are configured using the Cisco  
Transport Controller (CTC) or Transaction Language One (TL1).  
Security features configured with Cisco IOS include:  
•
•
•
Cisco IOS login enhancements  
Secure Shell (SSH) connection  
authentication, authorization, and accounting/Remote Authentication Dial-In User Service  
(AAA/RADIUS) stand alone mode  
•
Cisco IOS basic password (For information on basic Cisco IOS password configuration, see the  
“Passwords” section on page 3-6.)  
Security features configured with CTC or TL1 include:  
•
•
disabled console port  
AAA/RADIUS relay mode  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 16 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. This prevents console port input  
without preventing any console port output, such as Cisco IOS error messages.  
You can disable console port access through CTC or TL1. To disable it with CTC, at the card-level view  
of the ML-Series card, click under the IOS tab and uncheck the Enable Console Port Access box and  
click Apply. The user must be logged in at the Superuser level to complete this task.  
To disable it using TL1, refer to the Cisco ONS SONET TL1 Command Guide.  
Secure Login on the ML-Series Card  
The ML-Series card supports the Cisco IOS login enhancements integrated into Cisco IOS  
Release 12.2(25)S and introduced in Cisco IOS Release 12.3(4)T. The enhancements allow users to  
better secure the ML-Series card when creating a virtual connection, such as Telnet, Secure Shell, or  
HTTP. The secure login feature records successful and failed login attempts for vty sessions (audit trail)  
on the ML-Series card. These features are configured using the Cisco IOS command-line interface (CLI.)  
For more information, including step-by-step configuration examples, refer to the Cisco IOS Release  
12.2(25)S feature guide module Cisco IOS Login Enhancements at  
http://www.cisco.com/en/US/products/sw/iosswrel/ps1838/products_feature_guides_list.html.  
Secure Shell on the ML-Series Card  
This section describes how to configure the SSH feature and contains this information:  
•
•
•
Understanding SSH, page 16-2  
Configuring SSH, page 16-3  
Displaying the SSH Configuration and Status, page 16-5  
For other SSH configuration examples, see the “SSH Configuration Examples” section in the  
“Configuring Secure Shell” chapter of the Cisco IOS Security Configuration Guide, Cisco IOS  
Release 12.2, at this URL:  
http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html  
Note  
For complete syntax and usage information for the commands used in this section, see the command  
reference for Cisco IOS Release 12.2 at the URL:  
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configuration_g  
uides_list.html  
Understanding SSH  
The ML-Series card supports SSH, both version 1 (SSHv1) and version 2 (SSHv2). SSHv2 offers  
security improvements over SSHv1 and is the default choice on the ML-Series card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
Chapter 16 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. Before SSH, security was limited to the native security in Telnet. SSH  
improves on this by allowing the use of Cisco IOS software authentication.  
The ONS node also supports SSH. When SSH is enabled on the ONS node, you use SSH to connect to  
the ML-Series card for Cisco IOS CLI sessions.  
Note  
Telnet access to the ML-Series card is not automatically disabled when SSH is enabled. The user can  
disable Telnet access with the vty line configuration command transport input ssh  
.
Configuring SSH  
This section has configuration information:  
•
•
•
Configuration Guidelines, page 16-3  
Setting Up the ML-Series Card to Run SSH, page 16-3 (required)  
Configuring the SSH Server, page 16-5 (required)  
Configuration Guidelines  
Follow these guidelines when configuring the ML-Series card as an SSH server:  
•
•
•
The new model of AAA and a AAA login method must be enabled. If not previously enabled,  
complete the “Configuring AAA Login Authentication” section on page 16-11.  
A Rivest, Shamir, and Adelman (RSA) key pair generated by a SSHv1 server can be used by an  
SSHv2 server, and the reverse.  
If you get CLI error messages after entering the crypto key generate rsa global configuration  
command, an RSA key pair has not been generated. Reconfigure the hostname and domain, and then  
enter the crypto key generate rsa command. For more information, see the “Setting Up the  
ML-Series Card to Run SSH” section on page 16-3.  
•
•
When generating the RSA key pair, the message No host name specifiedmight appear. If it does,  
you must configure a hostname by using the hostname global configuration command.  
When generating the RSA key pair, the message No domain specifiedmight appear. If it does, you  
must configure an IP domain name by using the ip domain-name global configuration command.  
Setting Up the ML-Series Card to Run SSH  
Follow these steps to set up your ML-Series card to run as an SSH server:  
1. Configure a hostname and IP domain name for the ML-Series card.  
2. Generate an RSA key pair for the ML-Series card, which automatically enables SSH.  
3. Configure user authentication for local or remote access. This step is required.  
Beginning in privileged EXEC mode, follow these steps to configure a hostname and an IP domain name  
and to generate an RSA key pair.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 16 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  
Step 3  
Router (config)# hostname hostname  
Configure a hostname for your ML-Series card.  
Configure a host domain for your ML-Series card.  
Router (config)# ip domain-name  
domain_name  
Step 4  
Step 5  
Router (config)# crypto key generate  
rsa  
Enable the SSH server for local and remote authentication on the  
ML-Series card and generate an RSA key pair.  
When you generate RSA keys, you are prompted to enter a modulus  
length. The default modulus length is 512 bits. A longer modulus length  
might be more secure, but it takes longer to generate and to use.  
Router (config)# ip ssh timeout seconds Specify the timeout value in seconds; the default is 120 seconds. The  
range is 0 to 120 seconds. This parameter applies to the SSH negotiation  
phase. After the connection is established, the ML-Series card uses the  
default timeout values of the CLI-based sessions.  
By default, up to five simultaneous, encrypted SSH connections for  
multiple CLI-based sessions over the network are available (session 0  
to session 4). After the execution shell starts, the CLI-based session  
timeout value returns to the default of 10 minutes.  
Step 6  
Router (config)# ip ssh  
authentication-retries number  
Specify the number of times that a client can reauthenticate to the  
server. The default is 3; the range is 0 to 5.  
Step 7  
Step 8  
Router (config)# end  
Router # show ip ssh  
or  
Return to privileged EXEC mode.  
Displays the version and configuration information for your SSH  
server.  
Router # show ssh  
Displays the status of the SSH server on the ML-Series card.  
Step 9  
Router # show crypto key mypubkey rsa Displays the generated RSA key pair associated with this ML-Series  
card.  
Step 10  
Router # copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
To delete the RSA key pair, use the crypto key zeroize rsa global configuration command. After the  
RSA key pair is deleted, the SSH server is automatically disabled.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 16 Configuring Security for the ML-Series Card  
Secure Shell on the ML-Series Card  
Configuring the SSH Server  
Beginning in privileged EXEC mode, follow these steps to configure the SSH server:  
Command  
Purpose  
Step 1  
Step 2  
Router # configure terminal  
Enter global configuration mode.  
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.  
If you do not enter this command or do not specify a keyword, the SSH  
server selects the latest SSH version supported by the SSH client. For  
example, if the SSH client supports SSHv1 and SSHv2, the SSH server  
selects SSHv2.  
Step 3  
Router (config)# ip ssh timeout  
seconds  
Specify the timeout value in seconds; the default is 120 seconds. The  
range is 0 to 120 seconds. This parameter applies to the SSH negotiation  
phase. After the connection is established, the ML-Series card uses the  
default timeout values of the CLI-based sessions.  
By default, up to five simultaneous, encrypted SSH connections for  
multiple CLI-based sessions over the network are available (session 0 to  
session 4). After the execution shell starts, the CLI-based session timeout  
value returns to the default of 10 minutes.  
Step 4  
Router (config)# ip ssh  
authentication-retries number  
Specify the number of times that a client can reauthenticate to the server.  
The default is 3; the range is 0 to 5.  
Step 5  
Step 6  
Router (config)# end  
Router # show ip ssh  
or  
Return to privileged EXEC mode.  
Show the version and configuration information for your SSH server.  
Router # show ssh  
Show the status of the SSH server connections on the ML-Series card.  
(Optional) Save your entries in the configuration file.  
Step 7  
Router # copy running-config  
startup-config  
To return to the default SSH control parameters, use the no ip ssh {timeout | authentication-retries}  
global configuration command.  
Displaying the SSH Configuration and Status  
To display the SSH server configuration and status, use one or more of the privileged EXEC commands  
in Table 16-1.  
Table 16-1  
Commands for Displaying the SSH Server Configuration and Status  
Command  
show ip ssh  
show ssh  
Purpose  
Shows the version and configuration information for the SSH server.  
Shows the status of the SSH server.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS on the ML-Series Card  
For more information about these commands, see the “Secure Shell Commands” section in the “Other  
Security Features” chapter of the Cisco IOS Security Command Reference, Cisco IOS Release 12.2, at  
this URL:  
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_r/fothercr.htm.  
RADIUS on the ML-Series Card  
RADIUS is a distributed client/server system that secures networks against unauthorized access. Clients  
send authentication requests to a central RADIUS server, which contains all user authentication and  
network service access information. The RADIUS host is normally a multiuser system running RADIUS  
server software from Cisco or another software provider.  
Many Cisco products offer RADIUS support, including the ONS 15454, ONS 15454 SDH,  
ONS 15310-CL, ONS 15310-MA, and ONS 15600. The ML-Series card also supports RADIUS.  
The ML-Series card can operate either in RADIUS relay mode or in RADIUS stand alone mode  
(default). In either mode, the RADIUS messages from the ML-Series card are passed to a RADIUS  
server that is on the data communications network (DCN) used to manage the ONS node.  
RADIUS Relay Mode  
In RADIUS relay mode, RADIUS on the ML-Series card is configured by CTC or TL1 and uses the  
AAA/RADIUS features of the ONS node, which contains the ML-Series card. There is no interaction  
between RADIUS relay mode and RADIUS standalone mode. For information on ONS node security,  
refer to the “Security” chapter of the ONS node’s reference manual.  
An ML-Series card operating in RADIUS relay mode does need to be specified as a client in the  
RADIUS server entries. The RADIUS server uses the client entry for the ONS node as a proxy for the  
ML-Series card.  
Enabling relay mode disables the Cisco IOS CLI commands used to configure AAA/RADIUS. The user  
can still use the Cisco IOS CLI commands not related to AAA/RADIUS.  
In relay mode, the ML-Series card shows a RADIUS server host with an IP address that is really the  
internal IP address of the active timing, communications, and control card (XTC). When the ML-Series  
card actually sends RADIUS packets to this internal address, the XTC converts the RADIUS packet  
destination into the real IP address of the RADIUS server. In stand alone mode, the ML-Series card  
shows the true IP addresses of the RADIUS servers.  
When in relay mode with multiple RADIUS server hosts, the ML-Series card IOS CLI show run output  
also shows the internal IP address of the active XTC card. But since the single IP address now represents  
multiple hosts, different port numbers are paired with the IP address to distinguish the individual hosts.  
These ports are from 1860 to 1869, one for each authentication server host configured, and from 1870  
to 1879, one for each accounting server host configured.  
The single IP address will not match the host IP addresses shown in CTC, which uses the true addresses  
of the RADIUS server hosts. These same true IP addresses appear in the ML-Series card IOS CLI show  
run output, when the ML-Series card is in stand alone mode.  
Note  
A user can configure up to 10 servers for either authentication or accounting application, and one server  
host can perform both authentication and accounting applications.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 16 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.  
Caution  
Caution  
Switching the ML-Series card into RADIUS relay mode erases any configuration in the Cisco IOS  
configuration file related to AAA/RADIUS. The cleared AAA/RADIUS configuration is not restored to  
the Cisco IOS configuration file when the ML-Series card is put back into stand alone mode.  
Do not use the Cisco IOS command copy running-config startup-config while the ML-Series card is in  
relay mode. This command will save a Cisco IOS configuration file with RADIUS relay enabled. On a  
reboot, the ML-Series card would come up in RADIUS relay mode, even when the Enable RADIUS  
Relay box on the CTC is not checked. If this situation arises, the user should check the Enable RADIUS  
Relay box and click Apply and then uncheck the Enable RADIUS Relay box and click Apply. Doing this  
will set the ML-Series card in stand alone mode and clear RADIUS relay from the ML-Series card  
configuration.  
RADIUS Stand Alone Mode  
In stand alone mode, RADIUS on the ML-Series card is configured with the Cisco IOS CLI in the same  
general manner as RADIUS on a Cisco Catalyst switch.  
This section describes how to enable and configure RADIUS in the stand alone mode on the ML-Series  
card. RADIUS in stand alone mode is facilitated through AAA and enabled through AAA commands.  
Note  
Note  
For the remainder of the chapter, RADIUS refers to the Cisco IOS RADIUS available when the  
ML-Series card is in stand alone mode. It does not refer to RADIUS relay mode.  
For complete syntax and usage information for the commands used in this section, see the Cisco IOS  
Security Command Reference, Release 12.2.  
These sections contain this configuration information:  
•
•
•
•
Understanding RADIUS, page 16-8  
RADIUS Stand Alone Mode, page 16-7  
Configuring RADIUS, page 16-8  
Displaying the RADIUS Configuration, page 16-20  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 16 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. REJECT—The user is either not authenticated and is prompted to reenter the username and  
password, or access is denied.  
The ACCEPT and REJECT responses are bundled with additional data that is used for privileged EXEC  
or network authorization. Users must first successfully complete RADIUS authentication before  
proceeding to RADIUS authorization if it is enabled. The additional data included with the ACCEPT and  
REJECT packets includes these items:  
•
•
Telnet, SSH, rlogin, or privileged EXEC services  
Connection parameters, including the host or client IP address, access list, and user timeouts  
Configuring RADIUS  
This section describes how to configure your ML-Series card to support RADIUS. At a minimum, you  
must identify the host or hosts that run the RADIUS server software and define the method lists for  
RADIUS authentication. You must also apply the method list to the interface on which you want  
authentication to occur. For the ML-Series card, this is the vty ports. You can optionally define method  
lists for RADIUS authorization and accounting.  
You should have access to and should configure a RADIUS server before configuring RADIUS features  
on your ML-Series card.  
These sections contain this configuration information:  
•
•
•
•
•
Default RADIUS Configuration, page 16-9  
Identifying the RADIUS Server Host, page 16-9 (required)  
Configuring AAA Login Authentication, page 16-11 (required)  
Defining AAA Server Groups, page 16-13 (optional)  
Configuring RADIUS Authorization for User Privileged Access and Network Services, page 16-15  
(optional)  
•
•
•
•
•
Starting RADIUS Accounting, page 16-16 (optional)  
Configuring a nas-ip-address in the RADIUS Packet, page 16-17 (optional)  
Configuring Settings for All RADIUS Servers, page 16-17 (optional)  
Configuring the ML-Series Card to Use Vendor-Specific RADIUS Attributes, page 16-18 (optional)  
Configuring the ML-Series Card for Vendor-Proprietary RADIUS Server Communication,  
page 16-19 (optional)  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 16 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.  
Identifying the RADIUS Server Host  
ML-Series-card-to-RADIUS-server communication involves several components:  
•
•
•
•
•
•
Hostname or IP address  
Authentication destination port  
Accounting destination port  
Key string  
Timeout period  
Retransmission value  
You identify RADIUS security servers by their hostname or IP address, their hostname and specific UDP  
port numbers, or their IP address and specific UDP port numbers. The combination of the IP address and  
the UDP port number creates a unique identifier, allowing different ports to be individually defined as  
RADIUS hosts providing a specific AAA service. This unique identifier enables RADIUS requests to be  
sent to multiple UDP ports on a server at the same IP address.  
If two different host entries on the same RADIUS server are configured for the same service—for  
example, accounting—the second host entry configured acts as a fail-over backup to the first one. Using  
this example, if the first host entry fails to provide accounting services, the ML-Series card tries the  
second host entry configured on the same device for accounting services.  
To configure RADIUS to use the AAA security commands, you must specify the host running the  
RADIUS server daemon and a secret text (key) string that it shares with the ML-Series card. A RADIUS  
server, the ONS node, and the ML-Series card use a shared secret text string to encrypt passwords and  
exchange responses. The system ensures that the ML-Series cards' shared secret matches the shared  
secret in the ONS node.  
Note  
Note  
If you configure both global and per-server functions (timeout, retransmission, and key commands) on  
the switch, the per-server timer, retransmission, and key value commands override global timer,  
retransmission, and key value commands. For information on configuring these settings on all RADIUS  
servers, see the “Configuring Settings for All RADIUS Servers” section on page 16-17.  
Retransmission and timeout period values can be configured on the ML-Series card in stand alone mode.  
These values cannot be configured on the ML-Series card in relay mode.  
You can configure the ML-Series card to use AAA server groups to group existing server hosts for  
authentication. For more information, see the “Defining AAA Server Groups” section on page 16-13.  
Beginning in privileged EXEC mode, follow these steps to configure per-server RADIUS server  
communication. This procedure is required.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
Command  
Purpose  
Step 1  
Router # configure terminal  
Enter global configuration mode.  
Step 2  
Step 3  
Router (config)# aaa new-model  
Enable AAA.  
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.  
(Optional) For acct-port port-number, specify the UDP destination  
port for accounting requests.  
(Optional) For timeout seconds, specify the time interval that the  
switch waits for the RADIUS server to reply before resending. The  
range is 1 to 1000. This setting overrides the radius-server timeout  
global configuration command setting. If no timeout is set with the  
radius-server host command, the setting of the radius-server  
timeout command is used.  
•
(Optional) For retransmit retries, specify the number of times a  
RADIUS request is resent to a server if that server is not responding  
or responding slowly. The range is 1 to 1000. If no retransmit value is  
set with the radius-server host command, the setting of the  
radius-server retransmit global configuration command is used.  
•
(Optional) For key string, specify the authentication and encryption  
key used between the switch and the RADIUS daemon running on the  
RADIUS server.  
Note  
The key is a text string that must match the encryption key used  
on the RADIUS server. Always configure the key as the last item  
in the radius-server host command. Leading spaces are ignored,  
but spaces within and at the end of the key are used. If you use  
spaces in your key, do not enclose the key in quotation marks  
unless the quotation marks are part of the key.  
To configure the switch to recognize more than one host entry associated  
with a single IP address, enter this command as many times as necessary,  
making sure that each UDP port number is different. The switch software  
searches for hosts in the order in which you specify them. Set the timeout,  
retransmit, and encryption key values to use with the specific RADIUS  
host.  
Step 4  
Step 5  
Step 6  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your entries.  
Router# show running-config  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
To remove the specified RADIUS server, use the no radius-server host hostname | ip-address global  
configuration command.  
This example shows how to configure one RADIUS server to be used for authentication and another to  
be used for accounting:  
Switch(config)# radius-server host 172.29.36.49 auth-port 1612 key rad1  
Switch(config)# radius-server host 172.20.36.50 acct-port 1618 key rad2  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 16 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.  
Configuring AAA Login Authentication  
To configure AAA authentication, you define a named list of authentication methods and then apply that  
list to various ports. The method list defines the types of authentication to be performed and the sequence  
in which they are performed; it must be applied to a specific port before any of the defined authentication  
methods are performed. The only exception is the default method list, which is named default. The  
default method list is automatically applied to all ports except those that have a named method list  
explicitly defined.  
A method list describes the sequence and authentication methods to be queried to authenticate a user.  
You can designate one or more security protocols to be used for authentication, thus ensuring a backup  
system for authentication in case the initial method fails. The software uses the first method listed to  
authenticate users; if that method fails to respond, the software selects the next authentication method in  
the method list. This process continues until there is successful communication with a listed  
authentication method or until all defined methods are exhausted. If authentication fails at any point in  
this cycle—meaning that the security server or local username database responds by denying the user  
access—the authentication process stops, and no other authentication methods are attempted.  
For additional information on AAA login, refer to the “Authentication, Authorization, and Accounting  
(AAA)” chapter of the Cisco IOS Security Configuration Guide, Release 12.2 at:  
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configuration_g  
uides_list.html  
Beginning in privileged EXEC mode, follow these steps to configure login authentication. This  
procedure is required.  
Command  
Purpose  
Step 1  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Enable AAA.  
Router (config)# aaa new-model  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
Command  
Purpose  
Create a login authentication method list.  
Step 3  
Router (config)# aaa authentication  
login {default | list-name} method1  
[method2...]  
•
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.  
•
•
For list-name, specify a character string to name the list you are  
creating.  
For method1..., specify the actual method the authentication  
algorithm tries. The additional methods of authentication are used  
only if the previous method returns an error, not if it fails.  
Select one of these methods:  
–
enable—Use the enable password for authentication. Before you  
can use this authentication method, you must define an enable  
password by using the enable password global configuration  
command.  
–
group radius—Use RADIUS authentication. Before you can use  
this authentication method, you must configure the RADIUS  
server. For more information, see the “Identifying the RADIUS  
Server Host” section on page 16-9.  
–
–
–
line—Use the line password for authentication. Before you can  
use this authentication method, you must define a line password.  
Use the password password line configuration command.  
local—Use the local username database for authentication. You  
must enter username information in the database. Use the  
username name password global configuration command.  
local-case—Use a case-sensitive local username database for  
authentication. You must enter username information in the  
database by using the username password global configuration  
command.  
–
none—Do not use any authentication for login.  
Step 4  
Router (config)# line [console | tty |  
Enter line configuration mode, and configure the lines to which you want  
vty] line-number [ending-line-number] to apply the authentication list.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
Command  
Purpose  
Apply the authentication list to a line or set of lines.  
Step 5  
Router (config-line)# login  
authentication {default | list-name}  
•
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  
Step 7  
Step 8  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your entries.  
Router# show running-config  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
To disable AAA, use the no aaa new-model global configuration command. To disable AAA  
authentication, use the no aaa authentication login {default | list-name} method1 [method2...] global  
configuration command. To either disable RADIUS authentication for logins or to return to the default  
value, use the no login authentication {default | list-name} line configuration command.  
Defining AAA Server Groups  
You can configure the ML-Series card to use AAA server groups to group existing server hosts for  
authentication. You select a subset of the configured server hosts and use them for a particular service.  
The server group is used with a global server-host list, which lists the IP addresses of the selected server  
hosts.  
Server groups also can include multiple host entries for the same server if each entry has a unique  
identifier (the combination of the IP address and UDP port number), allowing different ports to be  
individually defined as RADIUS hosts providing a specific AAA service. If you configure two different  
host entries on the same RADIUS server for the same service (for example, accounting), the second  
configured host entry acts as a fail-over backup to the first one.  
You use the server group server configuration command to associate a particular server with a defined  
group server. You can either identify the server by its IP address or identify multiple host instances or  
entries by using the optional auth-port and acct-port keywords.  
Beginning in privileged EXEC mode, follow these steps to define the AAA server group and associate a  
particular RADIUS server with it:  
Command  
Purpose  
Step 1  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Enable AAA.  
Router (config)# aaa new-model  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
Command  
Purpose  
Specify the IP address or hostname of the remote RADIUS server host.  
Step 3  
Router (config)# radius-server host  
{hostname | ip-address} [auth-port  
port-number] [acct-port port-number]  
[timeout seconds] [retransmit retries]  
[key string]  
•
•
•
(Optional) For auth-port port-number, specify the UDP destination  
port for authentication requests.  
(Optional) For acct-port port-number, specify the UDP destination  
port for accounting requests.  
(Optional) For timeout seconds, specify the time interval that the  
switch waits for the RADIUS server to reply before resending. The  
range is 1 to 1000. This setting overrides the radius-server timeout  
global configuration command setting. If no timeout is set with the  
radius-server host command, the setting of the radius-server  
timeout command is used.  
•
(Optional) For retransmit retries, specify the number of times a  
RADIUS request is resent to a server if that server is not responding  
or responding slowly. The range is 1 to 1000. If no retransmit value is  
set with the radius-server host command, the setting of the  
radius-server retransmit global configuration command is used.  
•
(Optional) For key string, specify the authentication and encryption  
key used between the switch and the RADIUS daemon running on the  
RADIUS server.  
Note  
The key is a text string that must match the encryption key used  
on the RADIUS server. Always configure the key as the last item  
in the radius-server host command. Leading spaces are ignored,  
but spaces within and at the end of the key are used. If you use  
spaces in your key, do not enclose the key in quotation marks  
unless the quotation marks are part of the key.  
To configure the switch to recognize more than one host entry associated  
with a single IP address, enter this command as many times as necessary,  
making sure that each UDP port number is different. The switch software  
searches for hosts in the order in which you specify them. Set the timeout,  
retransmit, and encryption key values to use with the specific RADIUS  
host.  
Step 4  
Step 5  
Router (config)# aaa group server  
radius group-name  
Define the AAA server-group with a group name.  
This command puts the ML-Series card in a server group configuration  
mode.  
Router (config-sg-radius)# server  
ip-address  
Associate a particular RADIUS server with the defined server group.  
Repeat this step for each RADIUS server in the AAA server group.  
Each server in the group must be previously defined in Step 2.  
Return to privileged EXEC mode.  
Step 6  
Step 7  
Step 8  
Router (config-sg-radius)# end  
Router # show running-config  
Verify your entries.  
Router # copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
Step 9  
Enable RADIUS login authentication. See the “Configuring AAA Login  
Authentication” section on page 16-11.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 16 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.  
In this example, the ML-Series card is configured to recognize two different RADIUS group servers  
(group1 and group2). Group1 has two different host entries on the same RADIUS server configured for  
the same services. The second host entry acts as a fail-over backup to the first entry.  
Switch(config)# radius-server host 172.20.0.1 auth-port 1000 acct-port 1001  
Switch(config)# radius-server host 172.10.0.1 auth-port 1645 acct-port 1646  
Switch(config)# aaa new-model  
Switch(config)# aaa group server radius group1  
Switch(config-sg-radius)# server 172.20.0.1 auth-port 1000 acct-port 1001  
Switch(config-sg-radius)# exit  
Switch(config)# aaa group server radius group2  
Switch(config-sg-radius)# server 172.20.0.1 auth-port 2000 acct-port 2001  
Switch(config-sg-radius)# exit  
Configuring RADIUS Authorization for User Privileged Access and Network Services  
AAA authorization limits the services available to a user. When AAA authorization is enabled, the  
ML-Series card uses information retrieved from the user’s profile, which is in the local user database or  
on the security server, to configure the user’s session. The user is granted access to a requested service  
only if the information in the user profile allows it.  
There is no support for setting the privilege level on the ML-Series card or using the priv-lvl command.  
A user authenticating with a RADIUS server will only access the ML-Series card with a privilege level  
of 1, which is the default login privilege level. Because of this, a priv-lvl configured on the RADIUS  
server should have the priv-lvl of 0 or 1. Once a user is authenticated and gains access to the ML-Series  
card, they can use the enable password to gain privileged EXEC authorization and become a super user  
with a privilege level of 15, which is the default privilege level of enable mode.  
This example of an ML-Series card user record is from the output of the RADIUS server and shows the  
privilege level:  
CISCO15 Auth-Type := Local, User-Password == "otbu+1"  
Service-Type = Login,  
Session-Timeout = 100000,  
Cisco-AVPair = "shell:priv-lvl=1"  
You can use the aaa authorization global configuration command with the radius keyword to set  
parameters that restrict a user’s network access to privileged EXEC mode.  
The aaa authorization exec radius local command sets these authorization parameters:  
•
Use RADIUS for privileged EXEC access authorization if authentication was performed by using  
RADIUS.  
•
Use the local database if authentication was not performed by using RADIUS.  
Note  
Authorization is bypassed for authenticated users who log in through the CLI even if authorization has  
been configured.  
Beginning in privileged EXEC mode, follow these steps to specify RADIUS authorization for privileged  
EXEC access and network services:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 16 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.  
The exec keyword might return user profile information (such as  
autocommand information).  
Step 4  
Step 5  
Step 6  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your entries.  
Router# show running-config  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
To disable authorization, use the no aaa authorization {network | exec} method1 global configuration  
command.  
Starting RADIUS Accounting  
The AAA accounting feature tracks the services that users are accessing and the amount of network  
resources that they are consuming. When AAA accounting is enabled, the ML-Series card reports user  
activity to the RADIUS security server in the form of accounting records. Each accounting record  
contains accounting attribute-value (AV) pairs and is stored on the security server. This data can then be  
analyzed for network management, client billing, or auditing.  
Beginning in privileged EXEC mode, follow these steps to enable RADIUS accounting for each  
Cisco IOS privilege level and for network services:  
Command  
Purpose  
Step 1  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Router (config)# aaa accounting  
network start-stop radius  
Enable RADIUS accounting for all network-related service requests.  
Step 3  
Router (config)# aaa accounting exec  
start-stop radius  
Enable RADIUS accounting to send a start-record accounting notice at  
the beginning of a privileged EXEC process and a stop-record at the end.  
Step 4  
Step 5  
Step 6  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your entries.  
Router# show running-config  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
To disable accounting, use the no aaa accounting {network | exec} start-stop method1... global  
configuration command.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 16 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.  
Identifying the specific ML-Series card that sent the request to the server can be useful in debugging  
from the server. The nas-ip-address is primarily used for validation of the RADIUS authorization and  
accounting requests.  
If this value is not configured, the nas-ip-address is filled in by the normal Cisco IOS mechanism using  
the value configured by the ip radius-source command. If no value is specified then the best IP address  
routable to the server is used. If no routable address is available, the IP address of the server is used.  
Beginning in privileged EXEC mode, follow these steps to configure the nas-ip-address:  
Command  
Purpose  
Step 1  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Router (config)# [no] ip radius  
nas-ip-address {hostname |  
ip-address}  
Specify the IP address or hostname of the attribute 4 (nas-ip-address) in the  
radius packet.  
If there is only one ML-Series card in the ONS node, this command does  
not provide any advantage. The public IP address of the ONS node serves  
as the nas-ip-address in the RADIUS packet sent to the server.  
Step 3  
Step 4  
Step 5  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your settings.  
Router# show running-config  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
Configuring Settings for All RADIUS Servers  
Beginning in privileged EXEC mode, follow these steps to configure global communication settings  
between the ML-Series card and all RADIUS servers:  
Command  
Purpose  
Step 1  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Router (config)# radius-server key  
string  
Specify the shared secret text string used between the ML-Series card and  
all RADIUS servers.  
Note  
The key is a text string that must match the encryption key used on  
the RADIUS server. Leading spaces are ignored, but spaces within  
and at the end of the key are used. If you use spaces in your key, do  
not enclose the key in quotation marks unless the quotation marks  
are part of the key.  
Step 3  
Step 4  
Router (config)# radius-server  
retransmit retries  
Specify the number of times the ML-Series card sends each RADIUS  
request to the server before giving up. The default is 3; the range 1 to 1000.  
Router (config)# radius-server  
timeout seconds  
Specify the number of seconds a ML-Series card waits for a reply to a  
RADIUS request before resending the request. The default is 5 seconds; the  
range is 1 to 1000.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
Command  
Purpose  
Step 5  
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. If all RADIUS servers are  
marked as "dead," the skipping will not take place.  
The default is 0; the range is 1 to 1440 minutes.  
Return to privileged EXEC mode.  
Step 6  
Step 7  
Step 8  
Router (config)# end  
Router# show running-config  
Verify your settings.  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
To return to the default setting for the retransmit, timeout, and deadtime, use the no forms of these  
commands.  
Configuring the ML-Series Card to Use Vendor-Specific RADIUS Attributes  
The Internet Engineering Task Force (IETF) draft standard specifies a method for communicating  
vendor-specific information between the ML-Series card and the RADIUS server by using the  
vendor-specific attribute (attribute 26). Vendor-specific attributes (VSAs) allow vendors to support their  
own extended attributes that are not suitable for general use. The Cisco RADIUS implementation  
supports one vendor-specific option by using the format recommended in the specification. Cisco’s  
vendor-ID is 9, and the supported option has vendor-type 1, which is named cisco-avpair. The value is  
a string with this format:  
protocol : attribute sep value *  
Protocol is a value of the Cisco protocol attribute for a particular type of authorization. Attribute and  
value are an appropriate attribute-value (AV) pair defined in the Cisco Terminal Access Controller  
Access Control System Plus (TACACS+) specification, and sep is the character = for mandatory  
attributes and the character * for optional attributes. The full set of features available for TACACS+  
authorization can then be used for RADIUS.  
For example, this AV pair activates Cisco’s multiple named ip address pools feature during IP  
authorization (during point-to-point protocol [PPP] internet protocol control protocol (IPCP) address  
assignment):  
cisco-avpair= ”ip:addr-pool=first“  
This example shows how to specify an authorized VLAN in the RADIUS server database:  
cisco-avpair= ”tunnel-type(#64)=VLAN(13)”  
cisco-avpair= ”tunnel-medium-type(#65)=802 media(6)”  
cisco-avpair= ”tunnel-private-group-ID(#81)=vlanid”  
This example shows how to apply an input access control list (ACL) in ASCII format to an interface for  
the duration of this connection:  
cisco-avpair= “ip:inacl#1=deny ip 10.10.10.10 0.0.255.255 20.20.20.20 255.255.0.0”  
cisco-avpair= “ip:inacl#2=deny ip 10.10.10.10 0.0.255.255 any”  
cisco-avpair= “mac:inacl#3=deny any any decnet-iv”  
This example shows how to apply an output ACL in ASCII format to an interface for the duration of this  
connection:  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
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).”  
Beginning in privileged EXEC mode, follow these steps to configure the ML-Series card to recognize  
and use VSAs:  
Command  
Purpose  
Step 1  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Router (config)# radius-server vsa  
send [accounting | authentication]  
Enable the ML-Series card to recognize and use VSAs as defined by  
RADIUS IETF attribute 26.  
•
(Optional) Use the accounting keyword to limit the set of recognized  
vendor-specific attributes to only accounting attributes.  
•
(Optional) Use the authentication keyword to limit the set of  
recognized vendor-specific attributes to only authentication attributes.  
If you enter this command without keywords, both accounting and  
authentication vendor-specific attributes are used.  
The AAA server includes the authorization level in the VSA response  
message for the ML-Series card.  
Step 3  
Step 4  
Step 5  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your settings.  
Router# show running-config  
Router# copy running-config  
startup-config  
(Optional) Save your entries in the configuration file.  
For a complete list of RADIUS attributes or more information about vendor-specific attribute 26, see the  
“RADIUS Attributes” appendix in the Cisco IOS Security Configuration Guide, Release 12.2.  
Configuring the ML-Series Card for Vendor-Proprietary RADIUS Server Communication  
Although an IETF draft standard for RADIUS specifies a method for communicating vendor-proprietary  
information between the ML-Series card and the RADIUS server, some vendors have extended the  
RADIUS attribute set in a unique way. Cisco IOS software supports a subset of vendor-proprietary  
RADIUS attributes.  
As mentioned earlier, to configure RADIUS (whether vendor-proprietary or IETF draft-compliant), you  
must specify the host running the RADIUS server daemon and the secret text string it shares with the  
ML-Series card. You specify the RADIUS host and secret text string by using the radius-server global  
configuration commands.  
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  
Step 2  
Router# configure terminal  
Enter global configuration mode.  
Router (config)# radius-server host {hostname |  
ip-address} non-standard  
Specify the IP address or hostname of the remote  
RADIUS server host and identify that it is using a  
vendor-proprietary implementation of RADIUS.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 16 Configuring Security for the ML-Series Card  
RADIUS Stand Alone Mode  
Command  
Purpose  
Step 3  
Router (config)# radius-server key string  
Specify the shared secret text string used between the  
ML-Series card and the vendor-proprietary RADIUS  
server. The ML-Series card and the RADIUS server  
use this text string to encrypt passwords and  
exchange responses.  
Note  
The key is a text string that must match the  
encryption key used on the RADIUS server.  
Leading spaces are ignored, but spaces within  
and at the end of the key are used. If you use  
spaces in your key, do not enclose the key in  
quotation marks unless the quotation marks  
are part of the key.  
Step 4  
Step 5  
Step 6  
Router (config)# end  
Return to privileged EXEC mode.  
Verify your settings.  
Router# show running-config  
Router# copy running-config startup-config  
(Optional) Save your entries in the configuration file.  
To delete the vendor-proprietary RADIUS host, use the no radius-server host {hostname | ip-address}  
non-standard global configuration command. To disable the key, use the no radius-server key global  
configuration command.  
This example shows how to specify a vendor-proprietary RADIUS host and to use a secret key of rad124  
between the ML-Series card and the server:  
Switch(config)# radius-server host 172.20.30.15 nonstandard  
Switch(config)# radius-server key rad124  
Displaying the RADIUS Configuration  
To display the RADIUS configuration, use the show running-config privileged EXEC command.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
16-20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
C H A P T E R  
17  
CE-Series Ethernet Cards  
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) and the CE-MR-6 card supported on the  
Cisco ONS 15310-MA (15310-CE-MR-6). 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. For step-by-step  
Ethernet card circuit configuration procedures and hard-reset and soft-reset procedures, refer to the  
Cisco ONS 15454 Procedure Guide. For TL1 provisioning commands, refer to the Cisco ONS SONET  
TL1 Command Guide. For specific details on ONS 15310-CL and ONS 15310-MA Ethernet card  
interoperability with other ONS platforms, refer to the “POS on ONS Ethernet Cards” chapter of the  
Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration  
Guide.  
Chapter topics include:  
•
•
CE-100T-8 Ethernet Card, page 17-1  
CE-MR-6 Ethernet Card, page 17-12  
CE-100T-8 Ethernet Card  
This section describes the operation of the CE-100T-8 (Carrier Ethernet) card supported on the  
ONS 15310-CL and ONS 15310-MA.  
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 15310-CL and Cisco ONS 15310-MA Reference  
Manual. For step-by-step Ethernet card circuit configuration procedures, refer to the  
Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide. For TL1 provisioning commands,  
refer to the Cisco ONS SONET TL1 Command Guide.  
Section topics include:  
•
•
•
CE-100T-8 Overview, page 17-2  
CE-100T-8 Ethernet Features, page 17-2  
CE-100T-8 SONET Circuits and Features, page 17-7  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
CE-100T-8 Overview  
The CE-100T-8 is a Layer 1 mapper card with eight 10/100 Ethernet ports. It maps each port to a unique  
SONET circuit in a point-to-point configuration. Figure 17-1 illustrates a sample CE-100T-8  
application. In this example, data traffic from the Fast Ethernet port of a switch travels across the  
point-to-point circuit to the Fast Ethernet port of another switch.  
Figure 17-1  
CE-100T-8 Point-to-Point Circuit  
ONS 15310-CL  
ONS 15310-CL  
Ethernet  
Ethernet  
Point-to-Point Circuit  
The CE-100T-8 cards allow you to provision and manage an Ethernet private line service like a  
traditional SONET line. CE-100T-8 card applications include providing Ethernet private line services  
and high-availability transport. It supports ITU-T G.707 and Telcordia GR-253 based standards for  
SONET.  
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. The console port on the CE-100T-8 card is not functional.  
The CE-100T-8 cards forward valid Ethernet frames unmodified over the SONET network. Information  
in the headers is not affected by the encapsulation and transport. For example, included IEEE 802.1Q  
information will travel through the process unaffected.  
The ONS 15454 CE-100T-8 and the ONS 15310 CE-100T-8 support maximum Ethernet frame sizes of  
1600 bytes including the CRC. The MTU size is not configureable and is set at a 1500 byte maximum  
(standard Ethernet MTU). Baby giant frames in which the standard Ethernet frame is augmented by  
IEEE 802.1 Q tags or MPLS tags are also supported. Full Jumbo frames (9000 byte maximum) are not  
supported.  
The CE-100T-8 cards discard certain types of erroneous Ethernet frames rather than transport them over  
SONET. Erroneous Ethernet frames include corrupted frames with cyclic redundancy check (CRC)  
errors and undersized frames that do not conform to the minimum 64-byte length Ethernet standard.  
Note  
Many Ethernet attributes are also available through the network element default feature. For more  
information on NE defaults, refer to the “Network Element Defaults” appendix in the Cisco ONS 15454  
Reference Manual.  
Autonegotiation, Flow Control, and Frame Buffering  
On the CE-100T-8 card, Ethernet link auto negotiation is on by default when the speed or duplex of the  
port is set to auto. The user can also set the link speed, duplex, selective auto negotiation, and flow  
control manually under the card-level Provisioning tab of CTC.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
The CE-100T-8 card supports selective auto negotiation on the Ethernet ports. If selective auto  
negotiation is enabled, the port attempts to auto negotiate only to a specific speed and duplex. The link  
will come up if both the speed and duplex of the attached auto negotiating device matches that of the  
port. You cannot enable selective auto negotiation if either the speed or duplex of the port is set to auto.  
The CE-100T-8 card supports IEEE 802.3x flow control and frame buffering to reduce data traffic  
congestion. Flow control is on by default.  
To prevent over-subscription, buffer memory is available for each port. When the buffer memory on the  
Ethernet port nears capacity, the CE-100T-8 card uses IEEE 802.3x flow control to transmit a pause  
frame to the attached Ethernet device. Flow control and auto negotiation frames are local to the Fast  
Ethernet interfaces and the attached Ethernet devices. These frames do not continue through the POS  
ports.  
The CE-100T-8 card has symmetric flow control and proposes symmetric flow control when auto  
negotiating flow control with attached Ethernet devices. Symmetric flow control allows the CE-100T-8  
cards to respond to pause frames sent from external devices and to send pause frames to external devices.  
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.  
Figure 17-2  
Flow Control  
ONS 15310-CL  
ONS 15310-CL  
STS-N  
Ethernet  
Ethernet  
SONET  
Pause Frames  
Pause Frames  
This flow-control mechanism matches the sending and receiving device throughput to that of the  
bandwidth of the STS circuit. For example, a router might transmit to the Ethernet port on the CE-100T-8  
card. This particular data rate might occasionally exceed 51.84 Mbps, but the SONET circuit assigned  
to the CE-100T-8 port might be only STS-1 (51.84 Mbps). In this example, the CE-100T-8 sends out a  
pause frame and requests that the router delay its transmission for a certain period of time. With flow  
control and a substantial per-port buffering capability, a private line service provisioned at less than full  
line rate capacity (STS-1) is efficient because frame loss can be controlled to a large extent.  
Ethernet Link Integrity Support  
The CE-100T-8 supports end-to-end Ethernet link integrity (Figure 17-3). This capability is integral to  
providing an Ethernet private line service and correct operation of Layer 2 and Layer 3 protocols on the  
attached Ethernet devices.  
End-to-end Ethernet link integrity means that if any part of the end-to-end path fails, the entire path fails.  
It disables the Ethernet port on the CE-100T-8 card if the remote Ethernet port is unable to transmit over  
the SONET network or if the remote Ethernet port is disabled.  
Failure of the entire path is ensured by turning off the transmit pair at each end of the path. The attached  
Ethernet devices recognize the disabled transmit pair as a loss of carrier and consequently an inactive  
link or link fail.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
Figure 17-3  
End-to-End Ethernet Link Integrity Support  
Ethernet port  
Ethernet port  
ONS 310  
ONS 310  
STS-N  
Rx  
Tx  
Rx  
Tx  
SONET  
Note  
Some network devices can be configured to ignore a loss of carrier condition. If a device configured to  
ignore a loss of carrier condition attaches to a CE-100T-8 card at one end, alternative techniques (such  
as use of Layer 2 or Layer 3 keep-alive messages) are required to route traffic around failures. The  
response time of such alternate techniques is typically much longer than techniques that use link state as  
indications of an error condition.  
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. IS,AINS initially puts the port in the Out-of-Service and Autonomous,  
Automatic In-Service (OOS-AU,AINS) state. In this service state, alarm reporting is suppressed, but  
traffic is carried. After the soak period passes, the port changes to In-Service and Normal (IS-NR).  
Raised fault conditions, whether their alarms are reported or not, can be retrieved on the CTC Conditions  
tab or by using the TL1 RTRV-COND command.  
Two Ethernet port alarms/conditions, CARLOSS and TPTFAIL, can prevent the port from going into  
service. This occurs even though alarms are suppressed when a CE-100T-8 circuit is provisioned with  
the Ethernet ports set to the IS,AINS state, because the CE-100T-8 link integrity function is active and  
ensures that the links at both ends are not enabled until all SONET and Ethernet errors along the path  
are cleared. As long as the link integrity function keeps the end-to-end path down, both ports will have  
at least one of the two conditions needed to suppress the AINS-to-IS transition. Therefore, the ports will  
remain in the AINS state with alarms suppressed.  
ESM also applies to the SONET circuits of the CE-100T-8 card. If the SONET circuit is set up in  
IS,AINS state and the Ethernet error occurs before the circuit transitions to IS, then link integrity will  
also prevent the circuit transition to the IS state until the Ethernet port errors are cleared at both ends.  
The service state will be OOS-AU,AINS as long as the administrative state is IS,AINS. When there are  
no Ethernet or SONET errors, link integrity enables the Ethernet port at each end. Simultaneously, the  
AINS countdown begins as normal. If no additional conditions occur during the time period, each port  
transitions to the IS-NR state. During the AINS countdown, the soak time remaining is available in CTC  
and TL1. The AINS soaking logic restarts from the beginning if a condition appears again during the  
soak period.  
A SONET circuit provisioned in the IS,AINS state remains in the initial Out-of-Service (OOS) state until  
the Ethernet ports on each end of the circuit transition to the IS-NR state. The SONET circuit transports  
Ethernet traffic and counts statistics when link integrity turns on the Ethernet port, regardless of whether  
this AINS-to-IS transition is complete.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
IEEE 802.1Q CoS and IP ToS Queuing  
The CE-100T-8 references IEEE 802.1Q class of service (CoS) thresholds and IP type of service (ToS)  
(IP Differentiated Services Code Point [DSCP]) thresholds for priority queueing. CoS and ToS thresholds  
for the CE-100T-8 are provisioned on a per port level. This allows the user to provide priority treatment  
based on open standard quality of service (QoS) schemes already existing in the data network attached  
to the CE-100T-8. The QoS treatment is applied to both Ethernet and POS ports.  
Any packet or frame with a priority greater than the set threshold is treated as priority traffic. This  
priority traffic is sent to the priority queue instead of the normal queue. When buffering occurs, packets  
on the priority queue preempt packets on the normal queue. This results in lower latency for the priority  
traffic, which is often latency-sensitive traffic, such as VoIP.  
Because these priorities are placed on separate queues, the priority queuing feature should not be used  
to separate rate-based CIR/EIR marked traffic (sometimes done at a Metro Ethernet service provider  
edge). This could result in out-of-order packet delivery for packets of the same application, which would  
cause performance issues with some applications.  
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. This results in all traffic being treated with equal priority by default.  
Table 17-3 shows which values are mapped to the priority queue for sample IP ToS settings. (ToS  
settings span the full 0 to 255 range, but only selected settings are shown.)  
Table 17-1  
IP ToS Priority Queue Mappings  
ToS Setting in CTC ToS Values Sent to Priority Queue  
255 (default)  
None  
250  
150  
100  
50  
251–255  
151–255  
101–255  
51–255  
1–255  
0
For a CoS-tagged frame, the CE-100T-8 can map the eight priorities specified in CoS to priority or best  
effort. The user can configure a different CoS on CTC at the card-level view under the Provisioning >  
Ether Ports tabs. Any CoS 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 CoS is set to 7, which is the highest CoS  
value. This results in all traffic being treated with equal priority by default.  
Table 17-2 shows which values are mapped to the priority queue for CoS settings.  
Table 17-2  
CoS Priority Queue Mappings  
CoS Setting in CTC CoS Values Sent to Priority Queue  
7 (default)  
none  
7
6
5
6, 7  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
Table 17-2  
CoS Priority Queue Mappings (continued)  
CoS Setting in CTC CoS Values Sent to Priority Queue  
4
3
2
1
0
5, 6, 7  
4, 5, 6, 7  
3, 4, 5, 6, 7  
2, 3, 4, 5, 6, 7  
1, 2, 3, 4, 5, 6, 7  
Ethernet frames without VLAN tagging use ToS-based priority queueing if both ToS and CoS priority  
queueing is active on the card. The CE-100T-8 card’s ToS setting must be lower than 255 (default) and  
the CoS setting lower than 7 (default) for CoS and ToS priority queueing to be active. A ToS setting of  
255 (default) disables ToS priority queueing, so in this case the CoS setting would be used.  
Ethernet frames with VLAN tagging use CoS-based priority queueing if both ToS and CoS are active on  
the card. The ToS setting is ignored. CoS based priority queueing is disabled if the CoS setting is the 7  
(default), so in this case the ToS setting would be used.  
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  
Note  
Priority queuing has no effect when flow control is enabled (default) on the CE-100T-8. Under flow  
control a 6 kilobyte single-priority first in first out (FIFO) buffer fills, then a PAUSE frame is sent. This  
results in the packet ordering priority becoming the responsibility of the external device, which is  
buffering as a result of receiving the PAUSE flow-control frames.  
Priority queuing has no effect when the CE-100T-8 is provisioned with STS-3C circuits. The STS-3c  
circuit has more data capacity than Fast Ethernet, so CE-100T-8 buffering is not needed. Priority queuing  
only takes effect when buffering occurs.  
RMON and SNMP Support  
The CE-100T-8 card features remote monitoring (RMON) that allows network operators to monitor the  
health of the network with a network management system (NMS). The CE-100T-8 uses the ONG RMON.  
The ONG RMON contains the statistics, history, alarms, and events MIB groups from the standard  
RMON MIB, as well as Simple Network Management Protocol (SNMP). A user can access RMON  
threshold provisioning through TL1 or CTC. For RMON threshold provisioning with CTC, refer to the  
Cisco ONS 15454 Procedure Guide and the Cisco ONS 15454 Troubleshooting Guide. For TL1  
information, refer to the Cisco ONS SONET TL1 Command Guide.  
Statistics and Counters  
The CE-100T-8 has a full range of Ethernet and POS statistics under Performance > Ether Ports or  
Performance > POS Ports. These are detailed in the “Performance Monitoring” chapter of the  
Cisco ONS 15454 Reference Manual.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
CE-100T-8 SONET Circuits and Features  
The CE-100T-8 has eight POS ports, numbered one through eight, which are exposed to management  
with CTC or TL1. Each POS port is statically mapped to a matching Ethernet port. By clicking the  
card-level Provisioning tab > POS Ports tab, the user can configure the Administrative State, Framing  
Type, and Encapsulation Type. By clicking the card-level Performance tab > POS Ports tab, the user can  
view the statistics, utilization, and history for the POS ports.  
Available Circuit Sizes and Combinations  
Each POS port terminates an independent contiguous SONET concatenation (CCAT) or virtual SONET  
concatenation (VCAT). The SONET circuit is created for these ports through CTC or TL1 in the same  
manner as a SONET circuit for a non-Ethernet line card. Table 17-3 shows the circuit sizes available for  
the CE-100T-8 on the ONS 15310-CL and ONS 15310-MA.  
Table 17-3  
CE-100T-8 Supported Circuit Sizes  
CCAT High Order  
STS-1  
VCAT High Order  
STS-1-1v  
VCAT Low Order  
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. A VCAT circuit is also restricted in this manner. Table 17-3 shows the minimum  
SONET circuit sizes required for 10 Mbps and 100 Mbps wire speed service.  
Table 17-4  
SONET Circuit Size Required for Ethernet Wire Speeds  
Ethernet Wire Speed CCAT High Order  
Line Rate 100BaseT STS-3c  
Sub Rate 100BaseT STS-1  
VCAT High Order  
VCAT Low Order  
STS-1-3v, STS-1-2v* Not applicable  
STS-1-1v  
VT1.5-xV (x=1-64)  
VT1.5-7V  
Line Rate 10BaseT  
Sub Rate 10BaseT  
STS-1  
Not applicable  
Not applicable  
Not applicable  
VT1.5-xV (x=1-6)  
*STS-1-2v provides a total transport capacity of 98 Mbps.  
The number of available circuits and total combined bandwidth for the CE-100T-8 depends on the  
combination of circuit sizes configured. Table 17-5 shows the circuit size combinations available for  
CE-100T-8 CCAT high-order circuits on the ONS 15310-CL and ONS 15310-MA. Table 17-6 shows the  
circuit size combinations available for CE-100T-8 VCAT high-order circuits on the ONS 15310-CL and  
ONS 15310-MA.  
Table 17-5  
CCAT High Order Circuit Size Combinations  
Number of STS-3c Circuits  
Maximum Number of STS-1 Circuits  
None  
6
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
Table 17-5  
CCAT High Order Circuit Size Combinations  
Number of STS-3c Circuits  
Maximum Number of STS-1 Circuits  
1
2
3
None  
Table 17-6  
VCAT High Order Circuit Size Combinations  
Number of STS-1-3v Circuits Maximum Number of STS-1-2v Circuits  
None  
2
1
2
1
None  
The CE-100T-8 supports up to eight low order VCAT circuits. The available circuit sizes are VT1.5-nv,  
where n ranges from 1 to 64. The total number of VT members cannot exceed 168 VT1.5s with each of  
the two pools on the card supporting 84 VT1.5s. The user can create a maximum of two circuits at the  
largest low order VCAT circuit size, VT1.5-64v.  
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-1-3v  
STS-3c or  
Number of Active  
Service  
STS-1-2v  
STS-1  
VT1.5-xV (x=1-7)  
1
2
1
1
1
0
0
0
0
0
0
0
1
0
0
2
1
1
0
0
0
0
1
3
0
2
1
0
6
3
0
0
2
2
0
3
3
0
4
4
7(x=1-12)*  
0
8*  
4
5
6
6(x=1-14)  
7(x=1-12)*  
0
8
7
8*  
6
8
9
5(x=1-16)  
8 (x=1-21)  
8
10  
8
* This LO-VCAT Circuit combination is achievable if the first circuit created on the card is an LO VCAT circuit. If the first circuit  
created on the card is HO-VCAT or CCAT STS circuits, then a maximum of six LO-VCAT circuits can be added on the card.  
CE-100T-8 STS/VT Allocation Tab  
The CE-100T-8 has two pools, each with a maximum capacity of three STSs. At the CTC card-level view  
under the Maintenance tab, the STS/VT Allocation tab displays how the provisioned circuits populate  
the two pools. This information can be useful in freeing up the bandwidth required for provisioning a  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
circuit, if there is not enough existing capacity on any one pool for provisioning the desired circuit. The  
user can look at the distribution of the existing circuits among the two pools and decide which circuits  
to delete in order to free up space for the desired circuit.  
Figure 17-4  
CE-100T-8 STS/VT Allocation Tab  
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. If the bandwidth is available  
but scattered among the pools, the circuit cannot be provisioned.  
Looking at the POS Port Map table, the user can determine which circuits belong to which pools. The  
Pool and Port columns in Figure 17-4 show that the circuit on port 5 is drawn from Pool 2, and no other  
circuits are drawn from Pool 2. Deleting this one circuit will free up an STS-3c or STS-1-3v worth of  
bandwidth from a single pool.  
The POS Port table has a row for each port with three columns (Figure 17-4). They show the port  
number, the circuit size and type, and the pool it is drawn from. The Pool Utilization table has two  
columns and shows the pool number, the type of circuits on that pool, how much of the pool’s capacity  
is being used, and whether additional capacity is available.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
CE-100T-8 VCAT Characteristics  
The ML-100T-8 card and the CE-100T-8 card (both the version for the ONS 15310-CL and  
ONS 15310-MA and the version for the ONS 15454 SONET/SDH) have hardware-based support for the  
ITU-T G.7042 standard link capacity adjustment scheme (LCAS). This allows the user to dynamically  
resize a high order or low order VCAT circuit through CTC or TL1 without affecting other members of  
the VCG (errorless). ML-100T-8 LCAS support is high order only and is limited to a two member VCG.  
To enable end-to-end connectivity in a VCAT circuit that traverses through a third-party network, you  
must create a server trail between the ports. For more details, refer to the “Create Circuits and VT  
Tunnels” chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide.  
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 SW-LCAS is not supported on CE-100T-8 cards for interoperation with the CE-MR-10, CE-MR-6,  
and ML-MR-10 cards.  
The CE-100T-8 card allows independent routing and protection preferences for each member of a VCAT  
circuit. The user can also control the amount of VCAT circuit capacity that is fully protected, unprotected  
or if the circuit is on a bidirectional line switched ring (BLSR), uses protection channel access (PCA).  
Alarms are supported on a per-member as well as per virtual concatenation group (VCG) basis.  
Note  
The maximum tolerable VCAT differential delay for the CE-100T-8 is 48 milliseconds. The VCAT  
differential delay is the relative arrival time measurement between members of a virtual concatenation  
group (VCG).  
On ML-100T-8 and CE-100T-8 cards, members of a HW-LCAS circuit must be moved to the OOS,OOG  
(locked, outOfGroup) state before you delete them.  
A traffic hit is seen under the following conditions:  
•
•
•
•
A hard reset of the card containing the trunk port.  
Trunk port moved to OOS,DSBLD(locked,disabled) state.  
Trunk fiber pull.  
Deletion of members of the HW-LCAS circuit in IG (In Group) state.  
CE-100T-8 POS Encapsulation, Framing, and CRC  
The CE-100T-8 uses Cisco EoS LEX (LEX). LEX is the primary encapsulation of ONS Ethernet cards.  
In this encapsulation the protocol field is set to the values specified in Internet Engineering Task Force  
(IETF) Request For Comments (RFC) 1841. The user can provision GPF-F framing (default) or  
high-level data link control (HDLC) framing. With GFP-F framing, the user can also configure a 32-bit  
CRC (the default) or no CRC (none). With GFP-F framing, the user can also configure a 32-bit CRC (the  
default) or no CRC (none). On CTC go to CE card view and click the Provisioning >pos ports tab, to see  
the various parameters that can be configured on the POS ports, see Displaying ML-Series Ethernet  
Statistics in CTC, page 2-2. Various parameters like, admin state, service state, framing type, CRC,  
MTU and soak time for a port can be configured when LEX is used over GFP-F it is standard Mapped  
Ethernet over GFP-F according to ITU-T G.7041. HDLC framing provides a set 32-bit CRC.  
Figure 17-5 illustrates CE-100T-8 framing and encapsulation.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 17 CE-Series Ethernet Cards  
CE-100T-8 Ethernet Card  
Figure 17-5  
ONS CE-100T-8 Encapsulation and Framing Options  
GFP-F Frame Types  
GFP-Mapped  
Ethernet (LEX)  
LEX  
Encapsulation  
Core  
Header  
Payload  
Header  
Flag Address Control Protocol Payload FCS  
HDLC Framing Mode  
Payload  
FCS  
or  
GFP-F Framing Mode  
Transport Overhead  
SONET/SDH Payload Envelope  
SONET/SDH Frame  
The CE-100T-8 card supports GFP-F null mode. GFP-F CMFs are counted and discarded.  
The CE-100T-8 card is interoperable with the ML-100T-8 card and several other ONS Ethernet cards.  
For specific details on ONS Ethernet card interoperability, refer to the “POS on ONS Ethernet Cards”  
chapter of the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and  
Configuration Guide.  
CE-100T-8 Loopback, J1 Path Trace, and SONET Alarms  
The CE-100T-8 card supports terminal and facility loopbacks when in the Out of Service, Maintenance  
state (OOS, MT). It also reports SONET alarms and transmits and monitors the J1 Path Trace byte in the  
same manner as OC-N cards. Support for path termination functions includes:  
•
•
•
•
•
•
H1 and H2 concatenation indication  
C2 signal label  
Bit interleaved parity 3 (BIP-3) generation  
G1 path status indication  
C2 path signal label read/write  
Path level alarms and conditions, including loss of pointer, unequipped, payload mismatch, alarm  
indication signal (AIS) detection, and remote defect indication (RDI)  
•
•
•
•
J1 path trace for high order paths  
J2 path trace for low order paths  
J2 path trace for low order VCAT circuits at the member level  
Extended signal label for the low order paths  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
CE-MR-6 Ethernet Card  
This section describes the operation of the CE-MR-6 card supported on the ONS 15310-MA. The  
CE-MR-6 card installed in ONS 15310-MA is restricted to SONET operations.  
Provisioning is done through Cisco Transport Controller (CTC) or Transaction Language One (TL1).  
Configurations through Cisco IOS terminal are not supported on the CE-MR-6 card.  
For Ethernet card specifications, refer to the Cisco ONS 15310 Reference Manual. For step-by-step  
Ethernet card circuit configuration procedures, refer to the Cisco ONS 15310 Procedure Guide. Refer to  
the Cisco ONS SONET TL1 Command Guide for TL1 provisioning commands.  
This section include the following topics:  
•
•
•
CE-MR-6 Overview, page 17-12  
CE-MR-6 Ethernet Features, page 17-13  
CE-MR-6 Circuits and Features, page 17-20  
CE-MR-6 Overview  
CE-MR-6 card is a 5 Gbps data module for use in the Cisco ONS 15310-MA. It provides support for L1  
packet mapping functions (Ethernet to SONET). The 10/100/1000 Mbps Ethernet-encapsulated traffic is  
mapped to SONET circuits. Each circuit has three main attributes:  
•
•
•
Low order or high order  
Contiguous concatenation (CCAT) or virtual concatenation (VCAT)  
Generic framing procedure (GFP), LEX, high-level data link control (HDLC), or  
PPP (point-to-point protocol) based framing.  
The CE-MR-6 cards support LCAS that allows hitless dynamic adjustment of SONET link bandwidth.  
The CE-MR-6 is a Layer 1 (Ethernet Private Line) and Layer 1+ (Virtual Private Wire Services) mapper  
card with six IEEE 802 compliant 10/100/1000 Mbps Ethernet ports that provide 1:1 mapping of  
Ethernet ports to circuits. It maps each port to a unique SONET circuit in a point-to-point configuration.  
Figure 17-6 illustrates a sample CE-MR-6 application. In this example, data traffic from the Fast  
Ethernet port of a switch travels across the point-to-point circuit to the Fast Ethernet port of another  
switch.  
Figure 17-6  
CE-MR-6 Point-to-Point Circuit  
ONS Node  
ONS Node  
Ethernet  
Ethernet  
Point-to-Point Circuit  
The CE-MR-6 card allows you to provision and manage an Ethernet private line service like a traditional  
SONET line. CE-MR-6 card applications include providing carrier-grade Ethernet private line services  
and high-availability transport.  
The CE-MR-6 card carries any Layer 3 protocol that can be encapsulated and transported over Ethernet,  
such as IP or IPX. The Ethernet frame from the data network is transmitted on the Ethernet cable into  
the 10/100/1000 Mbps Ethernet ports on a CE-MR-6 card. The CE-MR-6 card transparently maps  
Ethernet frames into the SONET payload using packet-over-SONET/SDH (POS) encapsulation. The  
POS circuit, with its encapsulated Ethernet inside, is then multiplexed onto an optical card like any other  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
SONET synchronous transport signal (STS). When the payload reaches the destination node, the process  
is reversed and the data is transmitted from the 10/100/1000 Mbps Ethernet ports in the destination  
CE-MR-6 card onto the Ethernet cable and data network. The POS process is covered in detail in  
Chapter 6, “Configuring POS on the ML-Series Card.”  
The CE-MR-6 card supports ITU-T G.707-based standards. It allows a soft reset, which is errorless in  
most cases. During the soft reset, if there is a provisioning change, or if the firmware is replaced during  
a software upgrade process, the reset is equivalent to a hard reset. For more information on a soft reset  
of a CE-MR-6 card using Cisco Transport Controller (CTC), refer to the  
Cisco ONS 15310 Procedure Guide.  
CE-MR-6 Ethernet Features  
The Ethernet interface of the CE-MR-6 card comprises six front-end Small Form-factor Pluggable (SFP)  
slots. For each slot, the interface speed and media type is determined by the installed SFP module. The  
SFP slots support 10 Mbps, 100 Mbps, and 1000 Mbps (Gigabit Ethernet) operation. The SFP modules  
supporting the intended rate can be copper (10/100/1000 Mbps) or optical (100/1000 Mbps). SFP  
modules are offered as separate orderable products for flexibility. For SFP details, refer to the  
Cisco ONS 15310 Reference Manual or Installing the GBIC, SFP, SFP+, XFP, CXP, and CFP Optical  
Modules in Cisco ONS Platforms. Ethernet Ports 1 through 6 each map to a POS port with a  
corresponding number. The console port on the CE-MR-6 card is not functional.  
The CE-MR-6 card forwards valid Ethernet frames without modifying it over the SONET network.  
Information in the headers is not affected by encapsulation and transport. IEEE 802.1Q information  
travels through the process unaffected.  
The CE-MR-6 supports jumbo frames with MTU sizes of 64 to 9600 bytes.  
The CE-MR-6 card discards certain types of erroneous Ethernet frames rather than transport them over  
SONET. Erroneous Ethernet frames include corrupted frames with CRC errors and undersized frames  
that do not conform to the minimum 64-byte length, or oversized frames greater than 9600 bytes Ethernet  
standard.  
Note  
Many Ethernet attributes are also available through the network element (NE) defaults feature. For more  
information on NE defaults, refer to the “Network Element Defaults” appendix in the Cisco ONS 15310  
Reference Manual.  
Autonegotiation, Flow Control, and Frame Buffering  
On the CE-MR-6 card, Ethernet link auto negotiation is on by default when the duplex or speed of the  
port is set to auto. The user can also set the link speed, duplex, selective auto negotiation, and flow  
control manually under the card-level Provisioning tab in CTC.  
The CE-MR-6 card supports selective auto negotiation on the Ethernet ports. If selective auto  
negotiation is enabled, the port attempts to auto negotiate only to a specific speed and duplex. The link  
will come up if both the speed and duplex of the attached auto negotiating device matches that of the  
port. You cannot enable selective auto negotiation if either the speed or duplex of the port is set to auto.  
The CE-MR-6 card supports IEEE 802.3x flow control and frame buffering to reduce data traffic  
congestion. Flow control is on by default.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
To prevent over-subscription, buffer memory is available for each port. When the buffer memory on the  
Ethernet port nears capacity, the CE-MR-6 card uses IEEE 802.3x flow control to transmit a pause frame  
to the attached Ethernet device. Flow control and auto negotiation frames are local to the Ethernet (10  
Mbps), Fast Ethernet (100 Mbps), Gigabit Ethernet (1000 Mbps) interfaces and attached Ethernet  
devices. These frames do not continue through the POS ports.  
The CE-MR-6 card has asymmetric flow control and proposes asymmetric flow control when auto  
negotiating flow control with attached Ethernet devices.  
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-7 illustrates pause  
frames being sent and received by CE-MR-6 cards and attached switches.  
Figure 17-7  
Flow Control  
ONS Node  
ONS Node  
STS-N  
Ethernet  
Ethernet  
SONET  
Pause Frames  
Pause Frames  
This flow-control mechanism matches the sending and receiving device throughput the bandwidth of the  
STS circuit. For example, a router might transmit to the Ethernet port on the CE-MR-6 card. This  
particular data rate might occasionally exceed 51.84 Mbps, but the SONET circuit assigned to the  
CE-MR-6 port might be only STS-1 (51.84 Mbps). Under this condition, the CE-MR-6 sends out a pause  
frame and requests that the router delay its transmission for a certain period of time. With flow control  
and a substantial per-port buffering capability, a private line service provisioned at less than full line rate  
capacity (STS-1) is efficient because frame loss is controlled to a large extent.  
Ethernet Link Integrity Support  
The CE-MR-6 supports end-to-end Ethernet link integrity (Figure 17-8). This capability is integral to  
providing an Ethernet private line service and correct operation of Layer 2 and Layer 3 protocols on the  
attached Ethernet devices. Link integrity is implemented so that the Ethernet over SONET connection  
behaves more like an Ethernet cable from the viewpoint of the attached Ethernet devices.  
End-to-end Ethernet link integrity means that if any part of the end-to-end path fails, the entire path fails.  
It disables the Ethernet port transmitter on the CE-MR-6 card when the remote Ethernet port does not  
have a receive signal or when the SONET near end or far-end failure is detected. The failure of the entire  
path is ensured by turning off the transmit pair at each end of the path. If any part of the end-to-end path  
fails, the CE-MR-6 card soaks the defect for a fixed duration of 200 ms. The attached Ethernet devices  
recognize the disabled transmit pair as a loss of carrier and consequently an inactive link or link failure.  
The transport fail alarm is raised when the port transmitter is disabled. Link integrity supports a double  
fault, that is, when both the Ethernet ports do not receive a signal.  
Note  
Only bidirectional link integrity is supported on the CE-MR-6 card.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
Figure 17-8  
End-to-End Ethernet Link Integrity Support  
Ethernet port  
Ethernet port  
ONS Node  
ONS Node  
STS-N  
Rx  
Tx  
Rx  
Tx  
SONET  
Note  
Some network devices can be configured to ignore a loss of carrier condition. If a device configured to  
ignore a loss of carrier condition attaches to a CE-MR-6 card at one end, alternative techniques (such as  
use of Layer 2 or Layer 3 keep-alive messages) are required to route traffic around failures. The response  
time of such alternate techniques is typically much longer than techniques that use link state as  
indications of an error condition.  
In certain network configurations, the restoration time, for example, after a protection switch can be  
more than 200 ms. Such disruptions necessitate the link integrity to be initiated at an interval greater than  
200 ms. To allow link integrity to be initiated at an interval greater than 200 ms, set the link integrity  
timer in the range between 200 and 10000 ms, in multiples of 100 ms.  
Note  
The accuracy of the Link Integrity timer is less on CE-MR-6 card compared to the G1000 or CE-1000  
cards. The accuracy of Link Integrity timer is within 200 ms for the CE-MR-6 card.  
Ethernet Drop and Continue Circuit  
The CE-MR-6 card supports Ethernet drop and continue in CCAT circuits. Ethernet drop and continue  
(unidirectional) circuits have multiple destinations for use in broadcast circuit schemes. In broadcast  
scenarios, one source transmits traffic to multiple destinations, but traffic is not returned to the source.  
Figure 17-9  
Unidirectional Drop from a CE-MR-6 card on Node 1 to Nodes 2, 3, and 4  
Node 1  
ONS 15310  
CE-MR-6  
(source)  
Unidirectional  
circuit  
Unidirectional  
Unidirecttional  
Unidirectional  
Drop  
Drop  
Drop  
CE-MR-6  
CE-MR-6  
CE-MR-6  
Node 2  
ONS 15310  
Node 3  
ONS 15310  
Node 4  
ONS 15310  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
This circuit is supported only on CCAT circuit sizes of STS-48c, STS-24c, STS-12c, STS-9c, STS-6c,  
STS-3c, and STS-1 (ANSI) or VC3, VC4, VC4-2c, VC4-3c, VC4-4c, VC4-8c, and VC4-16c (ETSI). The  
creation of Ethernet drop and continue (unidirectional) circuits is supported on protected (path  
protected/SNCP and 1+1 protection) schemes and unprotected circuits with multiple drop points.  
Note  
The Ethernet drop and continue feature is supported on all cross-connect cards except XC and XCVT.  
The ONS 15310 configuration determines the maximum drop points supported—multiple drops on ports  
of the same card or different cards in the chassis. Figure 17-10 shows unidirectional drop from POS0  
port on CE-MR-6 A to ports POS0, POS1, POS2, POS3 of the CE-MR-6 B.  
Figure 17-10  
Unidirectional Drop from CE-MR-6 Card A to CE-MR-6 Card B  
Node 1  
ONS 15310  
CE-MR-6 Card A  
CE-MR-6 Card B  
(source)  
POS0  
port  
Unidirectional  
circuit  
POS0  
port  
POS1  
port  
POS2  
port  
POS3  
port  
Drop  
Drop  
Drop  
Drop  
Unidirectional Unidirectional Unidirectional Unidirectional  
The Ethernet drop and continue feature supports unidirectional link integrity and performance  
management.  
Alarms are monitored in the forward direction for the Ethernet drop and continue circuits and suppressed  
in the reverse direction, that is, STS alarms will not be detected at the source port. These unidirectional  
circuits are configured through CTC and TL1. To create an Ethernet drop and continue circuit, see  
“Chapter 6, Create Circuits and VT Tunnels” of the Cisco ONS 15310-CL and Cisco ONS 15310-MA  
Procedure Guide. For TL1 provisioning commands, refer to the Cisco ONS SONET TL1 Command  
Guide. For information on Alarms, see “Chapter 2, Alarm Troubleshooting” of the Cisco ONS 15310-CL  
and Cisco ONS 15310-MA Troubleshooting Guide.  
Administrative and Service States with Soak Time for Ethernet and SONET Ports  
The CE-MR-6 card can be managed by TL1, SNMP, CTC or CTM. The card supports the administrative  
and service states for the Ethernet ports and the SONET circuit. For more information about card and  
circuit service states, refer to the “Administrative and Service States” appendix in the  
Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
The Ethernet ports can be set to the Enhanced State Model (ESM) service states including the In-Service,  
Automatic In-Service (IS, AINS) administrative state. IS, AINS initially puts the port in the  
Out-of-Service and Autonomous, Automatic In-Service (OOS-AU, AINS) state. In this service state,  
alarm reporting is suppressed, but traffic is carried and loopbacks are allowed. After the soak period  
passes, the port changes to In-Service and Normal (IS-NR). Raised fault conditions, whether their alarms  
are reported or not, can be retrieved from the CTC Conditions tab or by using the TL1 RTRV-COND  
command.  
Two Ethernet port alarms/conditions, CARLOSS and TPTFAIL, can prevent the port from going into  
service. This occurs even though alarms are suppressed when a CE-MR-6 circuit is provisioned with the  
Ethernet ports set to the IS,AINS state, because the CE-MR-6 link integrity function is active and ensures  
that the links at both ends are not enabled until all SONET and Ethernet errors along the path are cleared.  
As long as the link integrity function keeps the end-to-end path down, both ports will have at least one  
of the two conditions needed to suppress the AINS-to-IS transition. Therefore, the ports will remain in  
the AINS state with alarms suppressed.  
ESM also applies to the SONET circuits of the CE-MR-6 card. If the SONET circuit is set up in IS,AINS  
state and the Ethernet error occurs before the circuit transitions to IS, then link integrity will also prevent  
the circuit transition to the IS state until the Ethernet port errors are cleared at both ends. The service  
state will be OOS-AU,AINS as long as the administrative state is IS,AINS. When there are no Ethernet  
or SONET errors, link integrity enables the Ethernet port at each end. Simultaneously, the AINS  
countdown begins as normal. If no additional conditions occur during the time period, each port  
transitions to the IS-NR state. During the AINS countdown, the soak time remaining is available in CTC  
and TL1. The AINS soaking logic restarts from the beginning if a condition appears again during the  
soak period.  
A SONET circuit provisioned in the IS,AINS state remains in the initial Out-of-Service (OOS) state until  
the Ethernet ports on each end of the circuit transition to the IS-NR state. The SONET circuit transports  
Ethernet traffic and counts statistics when link integrity turns on the Ethernet port, regardless of whether  
this AINS-to-IS transition is complete.  
IEEE 802.1Q CoS and IP ToS Queuing  
The CE-MR-6 references IEEE 802.1Q class of service (CoS) thresholds and IP type of service (ToS)  
(IP Differentiated Services Code Point [DSCP]) thresholds for priority queueing. CoS and ToS  
thresholds for the CE-MR-6 are provisioned on a per port level. This allows the user to provide priority  
treatment based on open standard quality of service (QOS) schemes already existing in the data network  
attached to the CE-MR-6. The QOS treatment is applied to both Ethernet and POS ports.  
Any packet or frame with a priority greater than the set threshold is treated as priority traffic. This  
priority traffic is sent to the priority queue instead of the normal queue. When buffering occurs, packets  
on the priority queue preempt packets on the normal queue. This results in lower latency for the priority  
traffic, which is often latency-sensitive traffic such as voice-over-IP (VoIP).  
Because these priorities are placed on separate queues, the priority queuing feature should not be used  
to separate rate-based CIR/EIR marked traffic (sometimes done at a Metro Ethernet service provider  
end). This could result in out-of-order packet delivery for packets of the same application, which would  
cause performance issues with some applications.  
For an IP ToS-tagged packet, the CE-MR-6 can map any of the 256 priorities specified in IP ToS to  
priority or best effort. The user can configure a different ToS in 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. This results in all traffic being treated with equal priority by default.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
Table 17-8 shows which values are mapped to the priority queue for sample IP ToS settings.  
(ToS settings span the full 0 to 255 range, but only selected settings are shown in Table 17-8.)  
Table 17-8  
IP ToS Priority Queue Mappings  
ToS Setting in CTC ToS Values Sent to Priority Queue  
255 (default)  
None  
250  
150  
100  
50  
251–255  
151–255  
101–255  
51–255  
1–255  
0
For a CoS-tagged frame, the CE-MR-6 can map the eight priorities specified in CoS to priority or best  
effort. The user can configure a different CoS in CTC at the card-level view under the Provisioning >  
Ether Ports tabs. Any CoS 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 CoS is set to 7, which is the highest CoS  
value. This results in all traffic being treated with equal priority by default.  
Table 17-9 shows values that are mapped to the priority queue for CoS settings.  
Table 17-9  
CoS Priority Queue Mappings  
CoS Setting in CTC CoS Values Sent to Priority Queue  
7 (default)  
None  
6
5
4
3
2
1
0
7
6, 7  
5, 6, 7  
4, 5, 6, 7  
3, 4, 5, 6, 7  
2, 3, 4, 5, 6, 7  
1, 2, 3, 4, 5, 6, 7  
Ethernet frames without VLAN tagging use ToS-based priority queueing if both ToS and CoS priority  
queueing is active on the card. The CE-MR-6 card’s ToS setting must be lower than 255 (default) and  
the CoS setting lower than 7 (default) for CoS and ToS priority queueing to be active. A ToS setting of  
255 (default) disables ToS priority queueing, so in this case the CoS setting would be used.  
Ethernet frames with VLAN tagging use CoS-based priority queueing if both ToS and CoS are active on  
the card. The ToS setting is ignored. CoS based priority queueing is disabled if the CoS setting is  
7 (default), so in this case the ToS setting would be used.  
If the CE-MR-6 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. If data is not tagged with  
a ToS value or a CoS value before it enters the CE-MR-6 card, it also gets sent to the default normal  
traffic queue.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
Note  
Note  
Priority queuing has no effect when flow control is enabled (default) on the CE-MR-6. When flow  
control is enabled, a 6KB, single-priority, first-in first-out (FIFO) buffer fills, then a PAUSE frame is  
sent. This results in the packet ordering priority becoming the responsibility of the external device,  
which is buffering as a result of receiving the PAUSE flow-control frames.  
Priority queuing takes effect only when there is congestion at the egress POS. For example, priority  
queuing has no effect when the CE-MR-6 card is provisioned with STS-3C circuits and the front-end is  
100 Mbps. The STS-3c circuit has more data capacity than Fast Ethernet, so CE-MR-6 buffering is not  
needed. Priority queuing only takes effect during buffering.  
RMON and SNMP Support  
The CE-MR-6 card features remote monitoring (RMON) that allows network operators to monitor the  
health of the network with a network management system (NMS). The CE-MR-6 card uses  
ONG RMON. ONG RMON contains statistics, history, alarms, and events MIB groups from the standard  
RMON MIB as well as Simple Network Management Protocol (SNMP). A user can access RMON  
threshold provisioning through TL1 or CTC. For RMON threshold provisioning with CTC, see the Cisco  
ONS 15310 Procedure Guide and the Cisco ONS 15310 Troubleshooting Guide.  
SNMP MIBs Supported  
The following SNMP MIBs are supported by the CE-MR-6 card:  
•
RFC2819 -MIB  
etherStatsOversizePkts  
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
etherStatsUndersizePkts  
etherStatsJabbers  
etherStatsCollisions  
etherStatsDropEvents  
etherStatsOctets.  
etherStatsBroadcastPkts.  
etherStatsMulticastPkts.  
etherStatsCRCAlignErrors.  
etherStatsFragments  
etherStatsPkts64Octets.  
etherStatsPkts65to127Octets  
etherStatsPkts128to255Octets  
etherStatsPkts256to511Octets  
etherStatsPkts512to1023Octets.  
etherStatsPkts1024to1518Octets.  
Rx Utilization  
Tx Utilization  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
•
RFC2233-MIB  
–
–
–
–
–
–
–
–
ifInUcastPkts  
ifOutUcastPkts  
ifInMulticastPkts  
ifInBroadcastPkts  
ifInDiscards  
ifInOctets  
ifOutOctets  
ifInErrors  
•
RFC2358-MIB  
–
–
–
dot3StatsFCSErrors  
dot3StatsSingleCollisionFrames  
dot3StatsFrameTooLong  
Statistics and Counters  
The CE-MR-6 has a full range of Ethernet and POS statistics information under Performance >  
Ether Ports or Performance > POS Ports.  
Supported Cross-connects  
There is no restriction on the number of CE-MR-6 cards that could be added in one chassis or the slot  
where the CE-MR-6 cards can be placed. CE-MR-6 card is supported with XC cards.  
CE-MR-6 Circuits and Features  
The CE-MR-6 card has 6 POS ports, numbered 1 through 6, which can be managed via CTC or TL1.  
Each POS port is statically mapped to a matching Ethernet port. By clicking the card-level  
Provisioning > POS Ports tab, the user can configure the Administrative State, and Encapsulation Type.  
By clicking the card-level Performance > POS Ports tab, the user can view the statistics, utilization, and  
history of the POS ports.  
Available Circuit Sizes and Combinations  
Each POS port terminates an independent CCAT or VCAT circuit. The circuit is created for these ports  
through CTC or TL1 in the same manner as a circuit for a non-Ethernet line card.  
Note  
If a CE-MR-6 card with a 1 Gbps SFP is installed and cross connected to another card that supports only  
10 or 100 Mbps, (for example, CE-100T-8 cards in the ONS 15310-MA) packet loss may occur if the  
SONET circuit between the two cards is more than 100 Mbps. In the CE-100T-8 example, a STS-1-2v  
circuit is errorless; however, if a STS-1-3v is used there will be a packet loss in the CE-MR-6 to  
CE-100T-8 direction.  
Table 17-10 show the circuit sizes available for CE-MR-6 on ONS 15310.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
Table 17-10  
Supported SONET Circuit Sizes of CE-MR-6 on ONS 15310  
CCAT  
VCAT High Order  
VCAT Low Order  
STS-1  
STS-1-nv (n=1 to 21)  
(Release 9.0) VT1.5-nv (n=1 to 64)  
(Release 9.1 and later) VT1.5-nv (n=1 to 63)  
STS-3c  
STS-6c  
STS-9c  
STS-12c  
STS-24c  
STS-48c  
STS-3C-nv (n=1 to 7)  
Table 17-11 shows the minimum SONET circuit sizes required for wire speed service delivery.  
Table 17-11  
Minimum SONET Circuit Sizes for Ethernet Speeds  
VCAT High Order  
STS-1-nv(n=1 to 21)  
Ethernet Wire Speed  
CCAT High Order  
VCAT Low Order  
Line Rate 1000 Mbps  
STS-48c or  
STS-24c  
STS-1-21v or  
STS-3-7v  
Not applicable  
Sub Rate 1000 Mbps  
STS-12c, STS-9c, STS-1-1v to  
(Release 9.0)  
STS-6c, STS-3c,  
and STS-1  
STS-1-20v  
VT1.5-xv (x=1-64)  
(Release 9.1 and later)  
VT1.5-xv (x=1-63)  
Line Rate 100 Mbps  
STS-3c  
STS-1-3v or  
STS-1-2v1  
(Release 9.0)  
VT1.5-xv (x=56-64)  
(Release 9.1 and later)  
VT1.5-xv (x=56-63)  
Sub Rate 100 Mbps  
Line Rate 10 Mbps  
Sub Rate 10 Mbps  
STS-1  
STS-1-1v  
VT1.5-xv (x=1-55)  
VT1.5-7v  
STS-1  
Not applicable  
Not applicable  
Not applicable  
VT1.5-xv (x=1-6)  
1. STS-1-2v provides a total transport capacity of 98 Mbps.  
Table 17-12 shows VCAT high-order circuit size combinations available for CE-MR-6 on ONS 15310  
for slots 1, 2, 5, and 6.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
Table 17-12  
VCAT High-Order Circuit Combinations for STS on ONS 15310 (Slots 1, 2, 5, and 6)  
STS Circuit Combinations  
VT Circuits  
Any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, STS-48c, or STS-nv  
circuits up to a maximum of 10 circuits or maximum of:  
No VTs  
•
•
•
CCAT—48 STSs  
STS-1 VCAT—47 STSs  
STS-3c VCAT—45 STSs  
Any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c circuits up to a maximum 1 VT1.5-48v circuit  
of 9 circuits or maximum of:  
•
•
•
CCAT—46 STSs  
STS-1 VCAT—45 STSs  
STS-3c VCAT—39 STSs  
Any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c circuits up to a maximum (Release 9.0)  
of 9 circuits or maximum of: 1 VT1.5-64v circuit  
•
•
•
CCAT—44 STSs  
(Release 9.1 and later)  
1 VT1.5-63v circuit  
STS-1 VCAT—43 STSs  
STS-3c VCAT—33 STSs  
Any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c circuits up to a  
maximum of 8 circuits or maximum of:  
2 VT1.5-48v circuits  
•
•
•
CCAT—44 STSs  
STS-1 VCAT—43 STSs  
STS-3c VCAT—33 STSs  
Any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c circuits up to a maximum (Release 9.0)  
of 8 circuits or maximum of: 2 VT1.5-64v circuits  
•
•
•
CCAT—42 STSs  
(Release 9.1 and later)  
2 VT1.5-63v circuits  
STS-1 VCAT—41 STSs  
STS-3c VCAT—27 STSs  
Any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c circuits up to a maximum 3 VT1.5-48v circuits  
of 7 circuits or maximum of:  
•
•
•
CCAT—42 STSs  
STS-1 VCAT—41 STSs  
STS-3c VCAT—27 STSs  
Note  
You can replace STSs for VTs at the following rates:  
Add 48 VT 1.5s at the cost of two STS-1s. If all the high order (HO) circuits are VCAT, one additional  
STS-1 is lost. Alternatively, you can add 48 VT 1.5s at the cost of two STS-3cs. If all the HO circuits  
are VCAT, one additional STS-3c is lost.  
In some cases, circuits can be added by reducing the circuits for other concatenation rates.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
CE-MR-6 Pool Allocation  
Note  
CE-MR Pool allocation can be set for ONS 15310-MA only and can be provisioned only when the card  
is in automatic provisioning mode.  
CE-MR-6 has the following characteristics:  
One pool can support only one circuit (from any front port), and must be a STS-48c circuit only. Two  
pools of 24 STSs each can be independently allocated.  
•
•
Ports 1-4 assigned to pool 1; ports 5-6 to pool 2.  
Each pool can support only one circuit type at a time. The circuit types are:  
–
–
–
–
–
–
–
1 STS-24c  
Up to 2 STS-12cs  
Up to 2 STS-9cs  
Up to 4 STS-6cs  
Up to 4 CCATs/ VCATs made up of STS-1s  
Up to 4 CCATs/VCATs made up of STS-3cs  
Number of members available for VCAT is subject to the total limit of 24 STSs in pool 1 and  
23 STSs (or 21 STSs in case of STS-3C/VC4) in pool 2 (per VCG limit 21 STSs)  
•
•
In addition, Pool1 can also support low order circuits (but not pool2)  
VT1.5 based VCATs are subject to a total limit of 144 VT1.5s  
(For Release 9.0, per VCG limit is 64. For Release 9.1 and later, per VCG limit is 63.)  
•
•
The 1 pool versus 2 pool operation is decided dynamically by the first circuit provisioned.  
If two pool exists, then the mode of each pool is decided dynamically by the circuit types  
provisioned.  
CE-MR-6 VCAT Characteristics  
The CE-MR-6 card has hardware-based support for the ITU-T G.7042 standard LCAS. This allows the  
user to dynamically resize a high order or low order VCAT circuit through CTC or TL1 without affecting  
other members of the virtual concatenation group (VCG) (errorless).  
The ONS 15310 ML100X-8 card has a software-based LCAS (SW-LCAS) scheme. Software LCAS is  
supported on CE-MR-6 cards for interoperation with these cards.  
The SW-LCAS is not supported on CE-MR-6 cards for interoperation with the CE-100T-8 and  
ML-MR-10 cards.  
Note  
Note  
The CE-MR-6 card does not support interoperation between the LCAS and non-LCAS circuits.  
The CE-MR-6 card allows independent routing and protection preferences for each member of a VCAT  
circuit. Alarms are supported on a per-member as well as per-VCG basis.  
A differential delay of 135 ms is supported for high order circuits and low order circuits.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-23  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
On the CE-MR-6 card, members of a HW-LCAS circuit must be moved to the OOS,OOG (locked,  
outOfGroup) state before:  
•
•
•
•
Creating or deleting HW-LCAS circuits.  
Adding or deleting HW-LCAS circuit members.  
Changing the state to OOS,DSBLD.  
Changing the state from OOS,DSBLD to any other state.  
A traffic hit is seen under the following conditions:  
•
•
•
•
A hard reset of the card containing the trunk port.  
Trunk port moved to OOS,DSBLD(locked,disabled) state.  
Trunk fiber pull.  
Deletion of members of the HW-LCAS circuit in IG (In Group) state.  
Note  
CE-MR-6 cards display symmetric bandwidth behavior when an AIS, UNEQ, LOP, SF, SD, PLM,  
ENCAP, OOF, or PDI alarm is raised at the near-end member of the HW-LCAS circuit. The  
LCAS-SINK-DNU alarm and the RDI condition are raised at the far-end member of the circuit. The  
LCAS-SINK-DNU alarm changes the member state to outOfGroup (OOG) and hence, the traffic goes  
down in both directions. For more information about alarms, refer to the “Alarm Troubleshooting”  
chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide or the  
Cisco ONS 15310-MA SDH Troubleshooting Guide.  
Caution  
Packet losses might occur when an optical fiber is reinserted or when a defect is cleared on members of  
the HW-LCAS split fiber routed circuits.  
CE-MR-6 POS Encapsulation, Framing, and CRC  
The CE-MR-6 card uses Cisco EoS LEX (LEX). LEX is the primary encapsulation of ONS Ethernet  
cards. In this encapsulation, the protocol field is set to the values specified in Internet Engineering Task  
Force (IETF) Request For Comments (RFC) 1841. The user can provision frame-mapped generic  
framing procedure (GFP-F) framing (default) or HDLC framing. With GFP-F framing, the user can also  
configure a 32-bit CRC (the default) or no CRC (none). When LEX is used over GFP-F it is standard  
Mapped Ethernet over GFP-F according to ITU-T G.7041. HDLC framing provides a set 32-bit CRC.  
For more details about the interoperability of ONS Ethernet cards, including information on  
encapsulation, framing, and CRC, see the Chapter 6, “Configuring POS on the ML-Series Card.”  
The CE-MR-6 card supports GFP-F null mode. GFP-F CMFs are counted and discarded.  
CE-MR-6 Loopback, J1 Path Trace, and SONET Alarms  
The CE-MR-6 card supports terminal and facility loopbacks. It also reports SONET alarms and transmits  
and monitors the J1 Path Trace byte in the same manner as OC-N cards. Support for path termination  
functions includes:  
•
•
•
H1 and H2 concatenation indication  
C2 signal label  
Bit interleaved parity 3 (BIP-3) generation  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-24  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
•
•
•
G1 path status indication  
C2 path signal label read/write  
Path level alarms and conditions, including loss of pointer (LOP), unequipped, payload mismatch,  
alarm indication signal (AIS) detection, and remote defect indication (RDI)  
•
•
•
J1 path trace for high-order CCAT paths  
J2 path trace for low-order VCAT circuits at the member level  
Extended signal label for the low-order paths  
Terminal and Facility Loopback on LCAS Circuits In Split Fibre Routing  
The following section lists guidelines to follow when the CE-MR-6 card includes a split fiber routing in  
a terminal and facility loopback on SW-LCAS circuits:  
Note  
Make sure that you follow the guidelines and tasks listed in the following section. Not doing so will  
result in traffic going down on members passing through optical spans that do not have loopbacks.  
•
•
•
SW-LCAS circuit members must have J1 path trace set to manual.  
Transmit and receive traces must be unique.  
SW-LCAS circuits on CE-MR-6 must allow our of group (OOG) members on Trace Identifier  
Mismatch - Path (TIM-P).  
•
•
For members on split fiber routes, facility loopback must select the AIS option in CTC.  
Traffic hit is expected when loopback is applied. This is due to asynchronous detection of VCAT  
defects and TIM-P detection on the other end of the circuit. This is acceptable since loopbacks are  
intrusive and affect traffic.  
However, place members of an HW-LCAS circuit traversing an optical interface under maintenance in  
OOS,OOG (locked, outOfGroup) state before applying terminal/facility loopbacks.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-25  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Chapter 17 CE-Series Ethernet Cards  
CE-MR-6 Ethernet Card  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
17-26  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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. Cisco does not  
recommend using its path protection feature in any particular topological network configuration.  
This appendix provides a command reference for those Cisco IOS commands or those aspects of  
Cisco IOS commands that are unique to ML-Series cards. For information about the standard Cisco IOS  
Release 12.2 commands, refer to the Cisco IOS documentation set available at  
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
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.  
Syntax Description  
Parameter  
Description  
drpri-rstp  
The protocol that enables the Dual Resilient Packet Ring Interconnect  
(DRPRI) feature of the ONS 15454 ML-Series cards. Do not configure an  
ONS 15310-CL or ONS 15310-MA ML-Series card with this option.  
ieee  
IEEE 802.1D Spanning Tree Protocol (RSTP).  
rstp  
IEEE 802.1W Rapid Spanning Tree Protocol (STP).  
The identifying number of the bridge group being assigned a protocol.  
bridge-group-number  
Defaults  
N/A  
Command Modes  
Usage Guidelines  
Global configuration  
The ONS 15310-CL or ONS 15310-MA ML-Series card implement RSTP or STP. DRPRI is not  
available.  
Examples  
The following example assigns STP to the bridge group with the bridge group number of 100.  
Router(config)# bridge 100 protocol ieee  
Related Commands  
bridge-group  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
The clear command can also be executed from CTC by means of a button, or from TL1 using a command  
on the interface. The CTC clearing function allows you to choose between clearing front-end or  
back-end interfaces. Cisco IOS and TL1 interface clear commands do not have this ability.  
Syntax Description  
Defaults  
This command has no arguments or keywords.  
The default is for PM counters not to be cleared.  
Privileged exec  
Command Modes  
Usage Guidelines  
Examples  
This command is applicable to the ML100T-8 card on the ONS 15310-CL and ONS 15310-MA.  
Router# clear counters  
Clear "show interface" counters on all interfaces [confirm]  
Router#  
Related Commands  
show interface  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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  
Defaults  
This command has no arguments or keywords.  
The default setting is clock auto.  
Global configuration  
Command Modes  
Usage Guidelines  
The no form of the command is required before any manual configuration of daylight savings time, time  
zone, or clock. The no form of the command is required if Network Time Protocol (NTP) is configured  
in Cisco IOS. The ONS 15310-CL and ONS 15310-MA are also configured through Cisco Transport  
Controller (CTC) to use an NTP or Simple Network Time Protocol (SNTP) server to set the date and  
time of the node.  
Examples  
ML_Series(config)# no clock auto  
Related Commands  
clock summertime  
clock timezone  
clock set  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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  
Usage Guidelines  
Global configuration  
The command allows the user to create a virtual interface for the RPR/SPR. Commands such as  
spr wrap or spr station-id can then be applied to the RPR through SPR configuration command mode.  
Examples  
The following example creates the shared packet ring interface:  
ML_Series(config)# interface spr 1  
Related Commands  
spr-intf-id  
spr station-id  
spr wrap  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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).  
Note  
The GFP-F FCS is compliant with ITU-T G.7041/Y.1303.  
Defaults  
The default framing mode is GFP-F with a 32-bit frame check sequence (FCS) enabled.  
Syntax Description  
The optional fcs-disabled keyword disables the GFP-F FCS. The no form of the command sets the  
framing mode to Cisco HDLC. The fcs-disabled keyword is not available when setting the framing mode  
to Cisco HDLC.  
Command Modes  
Usage Guidelines  
Examples  
Interface configuration mode (Packet-over-SONET [POS] only)  
This command can be used only when the ML-Series card’s POS interface is in shutdown mode. The  
peer path terminating element (PTE) needs to be in the same framing mode as the POS interface.  
ML_Series(config) # int pos0  
ML_Series(config-if) # shutdown  
ML_Series(config-if) # pos mode gfp fcs-disable  
ML_Series(config-if) # no shutdown  
Related Commands  
shutdown  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
Interface configuration mode (POS only)  
Command Modes  
Usage Guidelines  
This value is normally configured to match the setting on the peer PTE. The time granularity for this  
command is 1 millisecond.  
Examples  
Gateway(config)# int pos0  
Gateway(config-if)# pos pdi holdoff 500  
Related Commands  
pos trigger defects  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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. The alarms are as  
follows:  
all—All link down alarm failures  
ber_sd_b3—PBIP BER in excess of SD threshold failure  
ber_sf_b3—PBIP BER in excess of SF threshold failure  
encap—Path signal label encapsulation mismatch failure  
pais—Path alarm indication signal failure  
plop—Path loss of pointer failure  
ppdi—Path payload defect indication failure  
pplm—Payload label mismatch path  
prdi—Path remote defect indication failure  
ptim—Path trace indicator mismatch failure  
puneq—Path label equivalent to zero failure  
Defaults  
The default is to report all alarms.  
Command Modes  
Usage Guidelines  
Examples  
Interface configuration mode (POS only)  
This value is normally configured to match the setting on the peer PTE.  
Gateway(config)# int pos0  
Gateway(config-if)# pos report all  
Gateway(config-if)# pos flag c2 1  
03:16:51: %SONET-4-ALARM: POS0: PPLM  
Gateway(config-if)# pos flag c2 0x16  
03:17:34: %SONET-4-ALARM: POS0: PPLM cleared  
Related Commands  
pos trigger defects  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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. The  
conditions are as follows:  
all—All link down alarm failures (default)  
ber_sd_b3—PBIP BER in excess of SD threshold failure  
ber_sf_b3—PBIP BER in excess of SF threshold failure  
encap—Path signal label encapsulation mismatch failure  
pais—Path alarm indication signal failure  
plop—Path loss of pointer failure  
ppdi—Path payload defect indication failure  
pplm—Payload label mismatch path  
prdi—Path remote defect indication failure  
ptim—Path trace indicator mismatch failure  
puneq—Path label equivalent to zero failure  
Defaults  
The default is to report all conditions except ber_sd_b3. For a list of all conditions, see the list in the  
above description.  
Command Modes  
Usage Guidelines  
Examples  
Interface configuration mode (POS only)  
This value is normally configured to match the setting on the peer PTE.  
Gateway(config)# int pos0  
Gateway(config-if)# pos trigger defects all  
Related Commands  
pos trigger delay  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
Interface configuration mode (POS only)  
Command Modes  
Usage Guidelines  
This value is normally configured to match the setting on the peer PTE. The time granularity for this  
command is 50 milliseconds.  
Examples  
Gateway(config)# int pos0  
Gateway(config-if)# pos trigger delay 500  
Related Commands  
pos trigger defects  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
Parameter  
immediate  
delayed  
Description  
Syntax Description  
Handles a defect state change the instant it is detected.  
Handles the defect after the time specified by the command pos trigger delay. If  
delay is configured and the circuit is on RPR, then the RPR defect processing  
will also be delayed by the delay time.  
Defaults  
The default setting is immediate.  
POS interface configuration  
Command Modes  
Usage Guidelines  
Immediate should be used if the VCAT circuit uses unprotected SONET circuits. Delayed should be run  
if the VCAT circuit uses SONET protected circuits, such as apath protection.  
Examples  
The following example sets an ML-Series card to delayed:  
ML_Series(config)# interface pos 1  
ML_Series(config-if)# pos vcat defect delayed  
Related Commands  
interface spr 1  
spr wrap  
interface pos 1  
pos trigger delay  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
Syntax Description  
Parameter  
Description  
interface-number  
Number of the POS interface (0–1)  
Defaults  
N/A  
Command Modes  
Usage Guidelines  
Examples  
Privileged EXEC  
This command can be used to help diagnose and isolate POS or SONET problems.  
The following example displays the ML-Series controller information for interface pos 0.  
ML_Series# show controller pos 0  
Interface POS0  
Hardware is Packet Over SONET  
Framing Mode: HDLC  
Concatenation: CCAT  
Alarms reportable to CLI: AIS-P LOP-P UNEQ-P TIM-P PLM-P ENCAP-MISMATCH RDI-P PDI-P SF-P  
SD-P  
Link state change defects: AIS LOP UNEQ TIM PLM ENCAP RDI PDI  
Link state change time  
: 200 (msec)  
*************** Path ***************  
Circuit Type: STS-1  
Physical Channel Number: 0  
Circuit ESM State: IS  
STS Index 0  
Active Alarms: None  
B3 BER thresholds:  
SFBER = 1e-4,  
Path Trace Info.  
Channel 0  
SDBER = 1e-7  
Received String Format : 64 Byte  
Transmit String Format : 64 Byte  
Provisioned Trace Mode : off  
Prov'd  
State  
: false  
: w4xcon  
TIU-P  
: FALSE  
TIM-P : FALSE  
MatchCnt: 0 MisMatchCnt: 0  
Rec Flag : false  
Exp Flag : false Xmt Enab : true  
2398983617 total input packets, 1913918056382 post-decap bytes  
0 input short packets  
67757 input CRCerror packets , 0 input drop packets  
63584 rx HDLC addr mismatchs , 63599 rx HDLC ctrl mismatchs  
63630 rx HDLC sapi mismatchs , 63599 rx HDLC ctrl mismatchs  
289 rx HDLC destuff errors , 68048 rx HDLC invalid frames  
0 input abort packets  
2093 input packets dropped by ucode  
0 input packets congestion events  
2398847783 input good packets (POS MAC tx)  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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  
Usage Guidelines  
Examples  
Privileged EXEC  
This command can be used to help diagnose and isolate POS or SONET problems.  
The following example displays the ML-Series interface information for interface pos 0.  
ML_Series# show interfaces pos0  
POS0 is up, line protocol is up  
Hardware is Packet Over SONET, address is 000c.9a9a.9a9a (bia 000c.9a9a.9a9a)  
MTU 1500 bytes, BW 48384 Kbit, DLY 100 usec,  
reliability 255/255, txload 157/255, rxload 157/255  
Encapsulation: Cisco-EoS-LEX, loopback not set  
Keepalive set (10 sec)  
Scramble enabled  
ARP type: ARPA, ARP Timeout 04:00:00  
Last input 00:00:00, output never, output hang never  
Last clearing of "show interface" counters 5d22h  
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0  
Queueing strategy: fifo  
Output queue: 0/40 (size/max)  
5 minute input rate 29797000 bits/sec, 4673 packets/sec  
5 minute output rate 29841000 bits/sec, 4670 packets/sec  
2399801434 packets input, 3309269642 bytes  
Received 799619391 broadcasts (0 IP multicast)  
0 runts, 0 giants, 0 throttles  
0 parity  
135834 input errors, 67757 CRC, 0 frame, 0 overrun, 0 ignored  
0 input packets with dribble condition detected  
2398705102 packets output, 1211912638 bytes, 0 underruns  
0 output errors, 0 applique, 0 interface resets  
0 babbles, 0 late collision, 0 deferred  
0 lost carrier, 0 no carrier  
0 output buffer failures, 0 output buffers swapped out  
0 carrier transitions  
Related Commands  
show controller pos  
clear counters  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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  
Defaults  
This command has no arguments or keywords.  
N/A  
Command Modes  
Usage Guidelines  
Examples  
Privileged EXEC  
This command can be used to help diagnose and isolate card problems.  
ML_Series# show ons alarm  
Equipment Alarms  
Active: CONTBUS-IO-A CTNEQPT-PBWORK  
Port Alarms  
POS0 Active: None  
POS1 Active: None  
FastEthernet0 Active: None  
FastEthernet1 Active: None  
FastEthernet2 Active: None  
FastEthernet3 Active: None  
FastEthernet4 Active: None  
FastEthernet5 Active: None  
FastEthernet6 Active: None  
FastEthernet7 Active: None  
FastEthernet8 Active: None  
FastEthernet9 Active: None  
FastEthernet10 Active: None  
FastEthernet11 Active: None  
POS0  
Active Alarms : None  
Demoted Alarms: None  
POS1 VCG State: VCG_NORMAL  
VCAT Group  
Active Alarms : None  
Demoted Alarms: None  
Member 0  
Active Alarms : None  
Demoted Alarms: None  
Member 1  
Active Alarms : None  
Demoted Alarms: None  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-16  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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  
port  
Specifies hardware-related.  
Specifies the physical interface level. Optional port-number specifies a particular  
physical interface.  
sts  
vcg  
vt  
Specifies the SONET circuit level. Optional sts-number specifies a particular SONET  
circuit.  
Specifies the VCAT circuit group level. Optional vcg-number specifies a particular VCAT  
group.  
Not valid.  
Defaults  
Displays all defects  
Privileged EXEC  
Command Modes  
Usage Guidelines  
This command displays the set of active defects for the specified layer and the possible set of defects  
that can be set.  
Examples  
The following example shows the command and output for the ML-Series alarm defect information at  
the equipment level.  
ML_Series# show ons alarm defect eqpt  
Equipment Defects  
Active: RUNCFG-SAVENEED  
Reportable to SC/CLI: CONTBUS-IO-A CONTBUS-IO-B CTNEQPT-PBWORK CTNEQPT-PBPROT EQPT  
RUNCFG-SAVENEED ERROR-CONFIG HIGH-TEMP PROVISION-ERROR  
Port Defects  
POS0  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
POS1  
........  
Note  
The output example is abbreviated because of length.  
The following example shows the command and output for the ML-Series alarm defect information at  
the port level.  
ML-Series# show ons alarm defect port  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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 SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
POS1  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet0  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet1  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet2  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet3  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet4  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet5  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet6  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
FastEthernet7  
Active: None  
Reportable to SC: CARLOSS TPTFAIL GFP-LFD GFP-CSF GFP-UPI LPBK-TERMINAL LPBK-FACILITY  
The following example shows the command and output for the ML-Series alarm defect information at  
the synchronous transport signal (STS) level.  
ML_Series# show ons alarm defect sts  
STS Defects  
STS 0  
Active: None  
STS 1  
Active: None  
STS 2  
Active: None  
STS 3  
Active: None  
STS 4  
Active: None  
STS 5  
Active: None  
Related Commands  
show controller pos  
show ons alarm failures  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-18  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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.  
Parameter Description  
Syntax Description  
eqpt  
Specifies hardware-related.  
port  
Specifies the physical interface level. Optional port-number specifies a particular  
physical interface.  
sts  
vcg  
vt  
Specifies the SONET circuit level. Optional sts-number specifies a particular SONET  
circuit.  
Specifies the VCAT circuit group level. Optional vcg-number specifies a particular VCAT  
group.  
Not valid.  
Defaults  
N/A  
Command Modes  
Usage Guidelines  
Privileged EXEC  
This command displays the set of active failures for the specified layer and the possible set of failures  
that can be set.  
Examples  
The following example shows the command and output for the ML-Series alarm failure information at  
the equipment level.  
ML_Series# show ons alarm failure eqpt  
Equipment Alarms  
Active: RUNCFG-SAVENEED  
The following example shows the command and output for the ML-Series alarm failure information at  
the port level.  
ML-Series# show ons alarm failure port  
Port Alarms  
POS0 Active: None  
POS1 Active: None  
FastEthernet0 Active: None  
FastEthernet1 Active: None  
FastEthernet2 Active: None  
FastEthernet3 Active: None  
FastEthernet4 Active: None  
FastEthernet5 Active: None  
FastEthernet6 Active: None  
FastEthernet7 Active: None  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
ML_Series# show ons alarm failure sts  
STS Defects  
STS 0  
Active: None  
STS 1  
Active: None  
STS 2  
Active: None  
STS 3  
Active: None  
STS 4  
Active: None  
STS 5  
Active: None  
Related Commands  
show ons alarm defect  
show interface  
show controller pos  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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  
The only valid shared-packet-ring-number (SPR number) is 1.  
shared-packet-ring-number  
Defaults  
N/A  
Command Modes  
Usage Guidelines  
POS interface configuration  
•
•
•
The SPR number must be 1, which is the same SPR number assigned to the SPR interface.  
The members of the SPR interface must be POS interfaces.  
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  
port-channel, you then configure the SPR interfaces instead of the POS interface.  
Examples  
The following example assigns an ML-Series card POS interface to an SPR interface with a  
shared-packet-ring-number of 1:  
ML_Series(config)# interface pos 0  
ML_Series(config-if)# spr-intf-id 1  
Related Commands  
interface spr 1  
spr station-id  
spr wrap  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
port-based  
The port-based load balancing option maps unicast packets from even  
ports to the POS 0 interface and odd ports to the POS 1 interface.  
Defaults  
The default setting is auto.  
SPR interface configuration  
Command Modes  
Examples  
The following example configures an SPR interface to use port-based load balancing:  
ML_Series(config)# interface spr 1  
ML_Series(config-if)# spr load-balance port-based  
Related Commands  
interface spr 1  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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.  
Defaults  
N/A  
Command Modes  
Usage Guidelines  
SPR interface configuration  
The different ML-Series cards attached to the RPR all have the same interface type and number, spr1.  
The station ID helps to differentiate the SPR interfaces.  
Examples  
The following example sets an ML-Series card SPR station ID to 100:  
ML_Series(config)# interface spr 1  
ML_Series(config-if)# spr station-id 100  
Related Commands  
interface spr 1  
spr-intf-id  
spr wrap  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-23  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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  
immediate  
delayed  
Description  
Wraps RPR traffic the instant it detects a link state change.  
Wraps RPR traffic after the carrier delay time expires.  
Defaults  
The default setting is immediate.  
SPR interface configuration  
Command Modes  
Usage Guidelines  
Immediate should be used if RPR is running over unprotected SONET circuits. Delayed should be run  
for SONET protected circuits (bidirectional line switched ring [BLSR] or path protection.  
Examples  
The following example sets an ML-Series card to delayed:  
ML_Series(config)# interface spr 1  
ML_Series(config-if)# spr wrap delayed  
Related Commands  
interface spr 1  
spr-intf-id  
spr station-id  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
A-24  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
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.  
Unsupported Privileged Exec Commands  
clear ip accounting  
show controller pos pm  
show controller pos [variable] pm  
show ip accounting  
show ip cache  
show ip tcp header-compression  
show ip mcache  
show ip mpacket  
show ons alarm defect vt  
show ons alarm failure vt  
Unsupported Global Configuration Commands  
access-list aaa <1100-1199>  
access-list aaa <200-299>  
access-list aaa <700-799>  
async-bootp  
boot  
bridge <num> acquire  
bridge <num> address  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
B-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Appendix B Unsupported CLI Commands for the ML-Series Card  
Unsupported Global Configuration Commands  
bridge cmf  
bridge <num> bitswap-layer3-addresses  
bridge <num> circuit-group  
bridge <num> domain  
bridge <num> lat-service-filtering  
bridge <num> protocol dec  
bridge <num> protocol ibm  
bridge <num> protocol vlan-bridge  
chat-script  
class-map match access-group  
class-map match class-map  
class-map match destination-address  
class-map match mpls  
class-map match protocol  
class-map match qos-group  
class-map match source-address  
clns  
define  
dialer  
dialer-list  
downward-compatible-config  
file  
ip access-list log-update  
ip access-list logging  
ip address-pool  
ip alias  
ip bootp  
ip gdp  
ip local  
ip radius nas-ip-address (Command distinguishes multiple ONS 15454 SONET/SDH ML-Series cards.)  
ip reflexive-list  
ip security  
ip source-route  
ip tcp  
ipc  
map-class  
map-list  
multilink  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
B-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
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-group x lat-compression  
bridge-group x output-*  
bridge-group x subscriber-loop-control  
clock  
clns  
crc 32 (CRC is 32-bit size by default and cannot be configured on the ONS 15310-CL and  
ONS 15310-MA ML-Series card.)  
custom-queue-list  
down-when-looped  
fair-queue  
flowcontrol  
full-duplex  
half-duplex  
hold-queue  
ip accounting  
ip broadcast-address  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
B-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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  
custom-queue-list  
fair-queue  
hold-queue  
ip accounting  
ip broadcast-address  
ip load-sharing per-packet  
ip route-cache  
ip security  
ip tcp  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
B-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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  
hold-queue  
iso-igrp  
keepalive  
max-reserved-bandwidth  
multilink-group  
negotiation  
netbios  
ppp  
priority-group  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
B-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
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, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
B-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
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 network prior to calling.  
Note  
When you have a problem that you cannot resolve, contact the Cisco Technical Assistance Center (TAC).  
See the “Obtaining Documentation and Submitting a Service Request” section on page xxv as needed.  
Gathering Information About Your Internetwork  
Before gathering any specific data, compile a list of all symptoms that users have reported on the  
internetwork (such as connections dropping or slow host response).  
The next step is to gather specific information. Typical information needed to troubleshoot  
internetworking problems falls into two general categories: information required for any situation; and  
information specific to the topology, technology, or protocol.  
Information that is always required by technical support engineers includes the following:  
•
•
Network topology map for the data network and the SONET topology and provisioning.  
List of hosts and servers: Include the host and server type, number on network, and a description of  
the host operating systems that are implemented.  
•
•
•
Configuration listing of all switch routers and switches involved.  
Complete specifications of all switch routers and switches involved.  
Version numbers of software (obtained with the show version command) and flash code (obtained  
with the show controllers command) on all relevant switch routers and switches.  
•
•
•
List of network layer protocols, versions, and vendors.  
List of alarms and conditions on all nodes in the SONET/SDH topology.  
Node equipment and configuration.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
C-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
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.  
The show tech-support command outputs the equivalent of the show version, show running-config,  
show controllers, show stacks, show interfaces, show buffers, show process memory, and show  
process EXEC commands.  
The specific information requirements that might be needed by technical support vary depending on the  
situation. They include the following:  
•
Output from the following general show commands:  
show interfaces  
show controllers  
show processes {cpu | mem}  
show buffer  
show mem summary  
•
Output from the following protocol-specific show commands:  
show protocol route  
show protocol traffic  
show protocol interfaces  
show protocol arp  
•
•
•
•
•
Output from provisioning show commands  
Output from relevant debug privileged EXEC commands  
Output from protocol-specific ping and trace diagnostic tests, as appropriate  
Network analyzer traces, as appropriate  
Core dumps obtained using the exception dump command, or using the write core command if the  
system is operational, as appropriate  
Getting the Data from Your ML-Series Card  
When obtaining the information from your ML-Series card, you must tailor your method to the system  
that you are using to retrieve the information. Following are some hints for different platforms:  
•
PC and Macintosh—Connect a PC or Macintosh to the console port of the ML-Series card and log  
all output to a disk file (using a terminal emulation program). The exact procedure varies depending  
on the communication package used with the system.  
•
Terminal connected to the console port or remote terminal—The only way to get information with  
a terminal connected to the console port or with a remote terminal is to attach a printer to the AUX  
port on the terminal (if one exists) and to force all screen output to go to the printer. Using a terminal  
is undesirable because there is no way to capture the data to a file.  
•
UNIX workstation—At the UNIX prompt, enter the command script filename, then use Telnet to  
connect to the ML-Series card. The UNIX script command captures all screen output to the  
specified filename. To stop capturing output and close the file, enter the end-of-file character  
(typically Ctrl-D) for your UNIX system.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
C-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
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.  
Providing Data to Your Technical Support Representative  
When submitting information to your technical support representative, electronic data is preferred.  
Electronic data significantly eases the transfer of information between technical support personnel and  
development staff. Common electronic formats include data sent through electronic mail and files sent  
using FTP.  
If you are submitting data to your technical support representative, use the following list (in order of  
most to least favorable) to determine the preferred method for submission:  
•
•
•
The preferred method of information submission is through FTP service over the Internet. If your  
environment supports FTP, you can place your file in the incoming directory on the host Cisco.com.  
The next best method is to send data by e-mail. Before using this method, be sure to contact your  
technical support representative, especially when transferring binary core dumps or other large files.  
Transfer through a PC-based communications protocol, such as Kermit, to upload files to  
Cisco.com. Again, be sure to contact your technical support representative before attempting any  
transfer.  
•
•
Transfer by disk or tape.  
The least favorable method is hard-copy transfer by fax or physical mail.  
Note  
If you use e-mail, do not use encoding methods such as binhex or zip. Only MIME-compliant mail  
should be used.  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
C-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Appendix C Using Technical Support  
Providing Data to Your Technical Support Representative  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
C-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
I N D E X  
POS ports to the SPR interface 15-11  
attaching traffic policies to an interface 12-15 to 12-16  
audit trail 16-2  
Numerics  
802.1D. See STP  
802.1Q. See IEEE 802.1Q  
authentication, RADUS. See RADIUS  
A
B
abbreviating commands 3-11  
access control list. See ACL  
accounting with RADIUS 16-16  
ACL  
bandwidth command traffic classes 12-13  
BPDU  
See also STP  
designated port, defined 7-3  
designated switch, defined 7-3  
inferior information 7-3, 7-14  
message exchange 7-2  
QoS prioritization 12-7  
root port, defined 7-3  
applying to an interface 14-4  
configuring for SDM in TCAM 13-3  
creating 14-3 to 14-5  
extended IP 14-3  
implementation guidelines 14-2  
modifying TCAM size 14-5  
monitoring 14-5  
RSTP format 7-13  
superior information 7-3, 7-14  
bridge group  
named extended IP 14-4  
named IP ACL 14-2  
creating for RPR 15-13  
defining protocol for A-2  
forwarding-delay time 7-20  
hello time 7-19  
named standard IP 14-4  
numbered standard 14-3  
overview 14-1  
verifying 14-5  
maximum-aging time 7-20  
QoS 12-4  
adapter cable 3-4  
adding an ML-100T-8 card to an RPR 15-17 to 15-21  
addresses  
routing 11-1  
switch priority 7-18  
aging for dynamic 7-9  
bridge-group command 4-2, 5-4, 5-5  
bridge-group virtual interface. See BVIs  
bridge irb command 11-3  
bridge priority command 4-2  
bridge protocol command 4-2  
bridge protocol drpri-rstp bridge command A-2  
multicast, STP address management 7-8  
aging time, accelerated for STP 7-9, 7-20  
applying an ACL to an interface 14-4  
assigning  
POS interface to SPR interface A-21  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
Index  
bridging  
SNMP support 17-6  
configuring 4-2 to 4-3  
SONET alarms 17-11  
examples 4-3  
SONET circuits and features 17-7  
statistics 17-6  
feature list 1-2  
monitoring 4-3 to 4-5  
overview 4-1  
STS/VT allocation tab 17-8  
VCAT characteristics 17-10  
verifying 4-3 to 4-5  
CE-MR-6  
BVIs  
Ethernet Features 17-13  
Ethernet features 17-12  
configuring 11-3  
description 11-1  
flow control 17-13  
displaying information about 11-5  
routing enabled on 11-2  
frame buffering 17-13  
IEEE 802.1Q 17-17  
link integrity 17-14  
Overview 17-12  
C
overview 17-12  
priority queuing (ToS and CoS) 17-17  
statistics and counters 17-20  
CE-MR-6 card 17-17  
cable, RJ-11 to RJ-45 adapter 3-4  
CDP, Layer 2 protocol tunneling 9-9  
CE-100T-8  
RMON support 17-19  
overview 17-1  
SNMP support 17-19  
CE-100T-8 card  
channel-group command 10-3, 10-5  
circuit  
capacity restrictions 17-8  
counters 17-6  
Ethernet drop and continue 17-15  
Cisco IOS  
Enhanced State Model (ESM) 17-4  
Ethernet features 17-2  
flow control 17-2  
accessing through Telnet 3-2 to 3-3  
backing out one level 3-11  
Cisco IP SLA, ML-Series cards 12-31  
Cisco IP SLA, ML-Series restrictions 12-31  
Cisco IP SLA, overview 12-30  
Cisco Service Assurance Agent 12-30  
command modes 3-9 to 3-12  
commands A-1 to A-24  
frame buffering 17-2  
IEEE 802.1Q 17-5  
IS,AINS 17-4  
J1 path trace 17-11  
LCAS support 6-2  
link integrity 17-3  
loopback 17-11  
enable command mode 3-10  
exit command 3-11  
MTU size 17-2  
NE defaults 17-2  
global configuration command mode 3-10  
interface configuration command mode 3-10  
line configuration command mode 3-10  
listing commands 3-11  
overview 17-1  
POS encapsulation, framing, and CTC 17-10  
priority queuing (ToS and CoS) 17-5  
resetting 17-1  
login enhancements 16-2  
RMON support 17-6  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-2  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
opening a session from CTC 3-2  
privileged EXEC command mode 3-10  
RPR configuration example 15-14  
security features 16-1  
match ip dscp 12-11  
match ip precedence 12-11  
pos mode gfp A-6  
pos pdi holdoff A-7  
software basics 3-9  
pos report 6-7, A-8  
software image 3-1  
pos trigger defects A-9  
pos trigger delay 6-8, A-10  
SDM access-list 13-3  
service-policy 12-15  
service-policy input 12-16  
service-policy output 12-16  
set cos 12-15  
startup configuration file 3-8  
upgrading image 1-4  
user EXEC command mode 3-10  
using the command modes 3-11  
Cisco Service Assurance Agent. See Cisco IOS, Cisco  
Service Assurance Agent  
class-map match-all command example 12-19  
class-map match-any command example 12-19  
clear bridge command 4-4  
clear vlan statistics command 4-4  
clock auto command A-4  
commands  
show bridge 4-4  
show controller pos A-12  
show interface pos A-14  
show interfaces bvi 11-5  
show interfaces irb 11-5  
show interfaces port-channel 10-8  
show ons alarm A-15  
show ons alarm defect A-17  
show ons alarm failure A-19  
show policy-map 12-16  
show sdm size 13-3  
bandwidth 12-13  
bridge-group 4-2, 5-4, 5-5  
bridge irb 11-3  
bridge priority 4-2  
bridge protocol 4-2  
bridge protocol drpri-rstp A-2  
channel-group 10-3, 10-5  
clear bridge 4-4  
show tech-support C-2  
show vlan 8-5  
spr-intf-id A-21  
clear counters A-3  
spr load-balance A-22  
spr station-id A-23  
clear vlan statistics 4-4  
clock auto A-4  
spr wrap A-24  
cos-commit 12-16  
unsupported on the ML-Series card B-1 to B-6  
vcat defect A-11  
debug vlan packet 8-5  
hostname 3-7  
configuration command mode  
global 3-10  
interface bvi 11-3  
interface port-channel 10-1  
interface spr 1 A-5  
interface 3-10  
line 3-10  
line vty 3-7  
configuring  
listing 3-11  
ACL size in TCAM 13-3  
bridge group forwarding-delay time 7-20  
bridge group maximum-aging time 7-20  
match-any 12-11  
match cos 12-11  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-3  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
bridging 4-2 to 4-3  
SPR station ID A-23  
BVIs 11-3  
SSH 16-3  
CoS-based packet statistics 12-29  
CoS-based QoS 12-16  
STP 7-1 to 7-9, 7-15 to 7-20  
STP and RSTP, defaults 7-16  
STP hello time 7-19  
CTC circuits for RPR 15-7 to 15-9  
EtherChannel encapsulation 10-6 to 10-8  
Fast EtherChannel 10-2 to 10-4  
Fast Ethernet interfaces 5-4  
guidelines for physical and virtual interfaces 5-1  
host name 3-7  
STP path cost 7-18  
STP port policy 7-17  
STP port priority 7-17  
STP root switch 7-17  
STP switch priority 7-18  
VLAN as Layer 2 tunnel 9-12  
VLANs 8-1  
IEEE 802.1Q tunneling ports 9-4  
IEEE 802.1Q VLANs 8-3 to 8-5  
interface parameters 5-1  
VLAN-transparent and VLAN-specific services 9-7  
interfaces 5-3  
connecting  
IRB 11-2 to 11-4  
ML-100T-8 card in an RPR 15-7  
PC or terminal to console port 3-4  
ISL over FEC 10-6 to 10-8  
Layer 2 protocol tunneling 9-9 to 9-12  
link aggregation 10-1, 10-2 to 10-6  
management port 3-6  
console command mode. See line configuration command  
mode  
console port  
connecting to 3-4  
ML-100T-8 card security 16-1 to 16-20  
multicast QoS 12-24  
disabling 16-2  
CoS  
POS channel 10-4 to 10-6  
ML-Series CoS-based QoS example 12-21 to 12-22  
packet statistics. See CoS-based packet statistics  
QoS based on 12-16  
POS interface encapsulation 6-5  
POS interface framing mode 6-4  
POS interfaces 5-4, 5-5, 6-3, 6-4  
QoS 12-10 to 12-16  
CoS-based packet statistics  
configuring 12-29  
RADIUS 16-8 to 16-20  
enhanced performance monitoring 12-28  
overview 12-28  
RADIUS authorization 16-15  
RADIUS relay mode 16-7  
RADIUS server settings 16-17  
RADIUS stand alone mode 16-7  
RPR 15-6 to 15-15  
cos-commit command 12-16  
CRC  
CE-100T-8 card 17-10  
configuring for POS 6-4  
ML-100T-8 card 6-3  
creating  
RPR, example 15-7, 15-14  
RPR characteristics on ML-100T-8 cards 15-9 to 15-11  
RSTP 7-9 to 7-20  
ACLs 14-3 to 14-5  
SDM 13-2  
bridge group for RPR 15-13  
QoS traffic class 12-10  
QoS traffic policies 12-11 to 12-15  
SONET alarms 6-7  
SONET delay triggers 6-7  
SPR interface on ML-100T-8 cards 15-9 to 15-11  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-4  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
SPR interface on an RPR A-5  
startup configuration file 3-6  
STP topology 7-5  
SDM size 13-3  
SSH information 16-5  
STP and RSTP status 7-20 to 7-22  
VLANs 8-5  
CTC  
Cisco IOS on CTC 3-2  
documentation  
Ethernet port provisioning information 2-2  
Ethernet statistics 2-2  
conventions i-xix  
objectives i-xviii  
loading Cisco IOS startup configuration file  
through 3-8  
related to this book i-xviii  
double-tagged packets  
POS port provisioning information 2-3  
POS statistics 2-1  
IEEE 802.1Q tunneling 9-2  
Layer 2 protocol tunneling 9-10  
DSCP 12-2  
SONET alarms 2-4  
SONET circuit provisioning 2-4  
CTM and RPR 15-6  
dual leaky bucket policer model 12-5  
dynamic addresses. See addresses  
D
E
debug vlan packet command 8-5  
default multicast QoS 12-23  
defining AAA RADIUS server groups 16-13  
differentiated services code point. See DSCP  
disabling  
e-mail, technical support C-3  
enable command mode 3-10  
enabling  
passwords 3-6  
RSTP 7-17  
ML-Series card console port 16-2  
RSTP 7-16  
STP 7-17  
encapsulation  
STP 7-16  
and framing mode 6-3  
CE-100T-8 card 17-10  
configuring EtherChannels 10-6  
configuring for POS 6-4  
configuring for POS under GFP-F 6-5  
configuring IEEE 802.1Q VLANs 8-2  
discarding QoS packets with a policer 12-5  
displaying  
active alarms A-15  
alarms A-17, A-19  
BVI information 11-5  
J1 path trace 2-4  
configuring over FEC or POS channel 10-6 to 10-8  
ML-100T-8 card 6-3  
ML-Series Ethernet port provisioning  
information 2-2  
over EtherChannel, example 10-3, 10-7  
Enhanced State Model (ESM) 17-4  
enhanced state model (ESM) 17-17  
error messages, logging C-3  
ML-Series Ethernet statistics 2-2  
ML-Series POS port provisioning information 2-3  
ML-Series POS statistics 2-1  
POS controller status A-12  
EtherChannel  
POS interface status A-14  
configuration example 10-3  
RADIUS configuration 16-20  
configuring encapsulation over 10-6 to 10-8  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-5  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
encapsulation over, example 10-7  
monitoring 10-8  
G
GFP-F  
port channels supported 10-1  
verifying 10-8  
configuring POS interface encapsulation for 6-5  
framing 1-4  
Ethernet  
ML-100T-8 6-3  
assigning bridge group for RPR 15-13  
configuration tasks 5-4  
global configuration command mode 3-10  
CoS 12-3  
flow control on CE-Series 17-2  
frame buffering 17-2, 17-13  
link integrity 17-3  
H
hard reset on ML-Series card 3-1  
host name, configuring 3-7  
hostname command 3-7  
priority mechanisms for QoS 12-2  
Ethernet drop and continue circuit 17-15  
Ethernet Wire Service 9-6  
EWS 9-6  
I
extended system ID, STP 7-4  
IEEE 802.1D. See STP  
IEEE 802.1Q  
F
configuring tunneling 9-4  
configuring VLAN 8-3 to 8-5  
configuring VLAN encapsulation 8-2  
CoS and IP ToS queuing 17-5  
example 9-5  
Fast EtherChannel, configuring 10-2 to 10-4  
Fast Ethernet  
configuring autonegotiation 5-4  
configuring interfaces 5-4  
monitoring operations on 5-6 to 5-8  
FEC, configuring encapsulation over 10-6 to 10-8  
flow control 17-13  
monitoring tunneling 9-12  
tunneling, overview 9-1  
tunneling and compatibility with other features 9-4  
integrated routing and bridging. See IRB  
interface bvi command 11-3  
interface configuration command mode 3-10  
interface port-channel command 10-1  
interface port IDs 5-2  
framing  
See also framing mode  
CE-100T-8 card 17-10  
configuring for POS 6-4  
GFP-F 1-4  
ML-100T-8 card 6-3  
RPR 15-4 to 15-6  
interface spr 1 command A-5  
Inter-Switch Link protocol. See ISL  
IOS. See Cisco IOS  
framing mode  
See also framing  
IP  
configuring for POS 6-4  
on the ML-100T-8 card 6-3  
setting A-6  
access control list. See ACL  
precedence in QoS 12-2  
priority mechanisms for QoS 12-2  
SLA. See Cisco IOS, Cisco IP SLA  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-6  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
IRB  
ML-100T-8 card 1-5  
BVIs 11-1  
link integrity 17-14  
configuration considerations 11-2  
configuration example 11-3  
configuring 11-2 to 11-4  
description 11-1  
loading a startup configuration file 3-8  
logging command C-3  
logging router output C-2  
login authentication with RADIUS 16-11  
displaying information about 11-5  
monitoring 11-4  
M
verifying 11-4  
IS,AINS 17-4  
MAC address 5-1, 15-6  
management ports  
See also console ports  
J
configuring 3-6  
J1 path trace  
managing STP addresses 7-8  
marking QoS packets with a policer 12-5  
match-any command 12-11  
match cos command 12-11  
match ip dscp command 12-11  
match ip precedence command 12-11  
match spr1 command example 12-19  
CE-100T-8 card 17-11  
displaying 2-4  
ML-100T-8 card 6-2  
K
Media Access Control addresses. See MAC address  
message logging C-3  
Kermit protocol C-3  
metro tags 9-2  
L
ML-100T-8 card  
adding to an RPR 15-17 to 15-21  
assigning POS ports to the SPR interface 15-11  
Cisco IOS 1-4  
Layer 2 protocol tunneling  
and QoS 12-7  
configuring 9-9 to 9-12  
default configuration 9-10  
defined 9-9  
Cisco IOS software image 3-1  
Cisco IP SLA 12-31  
configuring ACL 14-1  
guidelines 9-10  
configuring IRB 11-1  
monitoring 9-12  
configuring link aggregation 10-1  
configuring QoS 12-1  
LCAS  
CE-100T-8 card support 6-2, 17-10  
ML-100T-8 card support 1-2, 6-2  
line configuration command mode 3-10  
line vty command 3-7  
link aggregation  
configuring SDM 13-1  
configuring security 16-1 to 16-20  
configuring VLANs 8-1  
creating a startup configuration file 3-6  
description 1-1  
configuring 10-1, 10-2 to 10-6  
disabling the console port 16-2  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-7  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
duplex setting 2-3  
encapsulation and framing 6-3  
Fast Ethernet port IDs 5-2  
feature list 1-2  
performance of CoS packet statistics 12-28  
POS 6-8 to 6-9  
QoS configuration 12-16 to 12-17  
RPR 15-16  
flow control mode 2-3  
GFP-F framing 1-4  
SDM 13-3  
STP and RSTP status 7-20 to 7-22  
tunneling 9-12  
hard reset 3-1  
Layer 2 feature list 1-2  
Layer 3 feature list 1-4  
LCAS support 6-2  
VLANs 8-5  
MQC. See QoS  
MTU size  
and LEX encapsulation 6-3  
link aggregation 1-5  
loading the startup configuration file 3-8  
maximum VCAT differential delay 6-2  
operating speed 2-3  
overview 1-1  
CE-100T-8 card 17-2  
ML-100T-8 card 6-3  
Multicast priority queuing 12-23  
multicast QoS  
RADIUS on 16-6  
configuring 12-24  
removing from an RPR 15-21 to 15-25  
resetting 1-1  
default traffic 12-23  
overview 12-23  
restoring the startup configuration file 3-9  
RMON 1-5  
priority queuing 12-23  
priority queuing restrictions 12-24  
RPR 1-5  
SNMP 1-5  
N
soft reset 3-2  
SONET alarms 6-6  
network element default 17-2, 17-13  
startup configuration file 3-5  
supported circuit sizes 6-2  
TL1 1-6  
O
tunneling 9-1  
opening a Cisco IOS session 3-2  
unsupported commands B-1 to B-6  
ML-Series card. See ML-100T-8 card  
modifying ACL TCAM size 14-5  
modular QoS CLI. See QoS  
monitoring  
P
packet statistics. See CoS-based packet statistics  
passwords, enabling 3-6  
ACLs 14-5  
PC, connecting to switch 3-4  
per-VLAN Spanning Tree+ 7-8  
pin mappings for RJ-11 to RJ-45 3-4  
policers  
bridging 4-3 to 4-5  
EtherChannel 10-8  
Fast Ethernet operations 5-6 to 5-8  
IRB 11-4  
defining 12-14  
J1 path trace 6-2  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-8  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
dual leaky bucket 12-5  
Q
marking and discarding QoS packets 12-5  
ML-Series example 12-20  
QinQ  
CoS accounting 12-28  
ports  
implementation 12-8  
overview 9-1  
channel interface 10-1  
configuring priority for STP 7-17  
interface port IDs 5-2  
tunnel. See tunnel ports  
VLAN trunk 8-1  
QoS  
and L2 protocol tunneling 12-7  
and RPR 15-6  
classification 12-4  
POS  
configuration examples 12-17 to 12-22  
configuring 12-10 to 12-16  
control packets 12-7  
assigning ports to the SPR interface 15-11, A-21  
CE-100T-8 card 17-10  
configuring 6-4  
CoS-based 12-16  
configuring channel 10-4 to 10-6  
configuring channel, example 10-5  
configuring encapsulation over 10-6  
configuring framing 6-4  
configuring interfaces 6-3  
description 6-1  
CoS-based example 12-21 to 12-22  
CoS-based packet statistics. See CoS-based packet  
statistics  
DSCP 12-2  
egress priority marking 12-8  
Ethernet 12-3  
displaying controller status A-12  
displaying the interface status A-14  
GFP-F framing 1-4  
flow control pause 12-9  
ingress priority marking 12-8  
IP precedence 12-2  
monitoring 6-8 to 6-9  
marking and discarding packets 12-5  
ML-Series flow 12-4  
SONET alarms 6-7, 6-8  
verifying 6-8 to 6-9  
monitoring 12-16 to 12-17  
multicast. See multicast QoS  
multicast priority queueing 12-23  
on RPR 12-9  
pos mode gfp fcs A-6  
pos pdi holdoff command A-7  
pos report command 6-7, A-8  
pos trigger defects command A-9  
pos trigger delay command 6-8, A-10  
pos vcat defect command A-11  
priority queuing 17-17  
overview 12-2  
policing. See policers  
priority mechanisms in IP and Ethernet 12-2  
queuing 12-6  
privileged EXEC command mode 3-10  
processing BPDUs 7-13  
scheduling 12-6  
traffic class. See traffic class  
traffic policy. See traffic policy  
verifying configuration 12-16 to 12-17  
provisioning  
displaying information about in CTC 2-2, 2-3  
SONET circuits 2-4  
queuing 17-17  
PVST+. See per-VLAN Spanning Tree+  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-9  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
bridge groups 11-1  
R
enabled on BVIs 11-2  
RADIUS  
AAA login authentication 16-11  
RPR  
adding an ML-Series card to 15-17 to 15-21  
and CTM 15-6  
authentication key 16-9  
configuring 16-8 to 16-20  
configuration example 15-7, 15-14  
configuring 15-6 to 15-15  
configuring authorization 16-15  
configuring multiple UDP ports 16-9  
configuring relay mode 16-7  
configuring server settings 16-17  
configuring stand alone mode 16-7  
default configuration 16-9  
defining AAA server groups 16-13  
displaying the configuration 16-20  
identifying the server host 16-9  
limiting the services to the user 16-15  
ML-100T-8 card 16-6  
configuring ML-100T-8 card  
characteristics 15-9 to 15-11  
creating a SPR interface on A-5  
deleting an ML-Series card from 15-21 to 15-25  
framing process 15-4 to 15-6  
MAC address and VLAN support 15-6  
ML-100T-8 card 1-5  
monitoring 15-16  
overview 15-1  
packet handling 15-2  
QoS on 12-9, 15-6  
nas-ip-address 16-17  
ring wrapping 15-3  
overview 16-8  
setting the wrap mode A-24  
SONET circuits in 15-2  
specifying the load-balancing scheme A-22  
verifying 15-16  
relay mode 16-6  
starting accounting 16-16  
tracking services accessed by users 16-16  
vendor-proprietary attributes 16-19  
vendor-specific attributes 16-18  
Rapid Spanning Tree Protocol. See RSTP  
redundant STP connectivity 7-8  
remote terminals, logging router output C-2  
removing an ML-Series card from an RPR 15-21 to 15-25  
resetting  
RSTP  
active topology, determining 7-10  
BPDU format 7-13  
BPDU processing 7-14  
configuring 7-9 to 7-20  
default configuration 7-16  
designated port, defined 7-10  
designated switch, defined 7-10  
disabling 7-16  
CE-100T-8 card 17-1  
ML-100T-8 card 1-1, 3-2  
resilient packet ring. See RPR  
restoring the startup configuration file 3-9  
RJ-11 to RJ-45 console cable adapter 3-4  
RMON  
displaying status 7-20 to 7-22  
enabling 7-17  
interoperability with IEEE 802.1D STP 7-15  
monitoring status 7-20 to 7-22  
overview 7-9  
CE-100T-8 card 17-6  
CE-MR-6 card 17-19  
port roles 7-10  
ML-100T-8 card 1-5  
port roles, synchronization of 7-12  
routing  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
proposal-agreement handshake process 7-11  
rapid convergence 7-11  
VCAT defect processing mode A-11  
show bridge command 4-4  
show controller pos command A-12  
show interface pos command A-14  
show interfaces bvi command 11-5  
show interfaces irb command 11-5  
show interfaces port-channel command 10-8  
show ons alarm command A-15  
show ons alarm defect command A-17  
show ons alarm failure command A-19  
show policy-map command 12-16  
show sdm size command 13-3  
show tech-support command C-2  
show vlan command 8-5  
root port, defined 7-10  
supported number of instances 7-9  
topology changes 7-14  
S
safety instructions i-xx  
scrambling 6-3  
script command C-2  
SDM  
configuring ACL size 13-3  
configuring autolearn 13-2  
configuring regions 13-3  
configuring size 13-2  
SLA. See Cisco IOS, Cisco IP SLA  
SNMP  
CE-100T-8 card 17-6  
monitoring 13-3  
CE-MR-6 card 17-19  
overview 13-1  
ML-100T-8 card 1-5  
regions 13-2  
soft-reset 17-13  
verifying 13-3  
soft reset on the ML-Series card 3-2  
SONET alarms  
sdm access-list command 13-3  
secure login, ML-Series card 16-2  
secure shell. See SSH  
CE-100T-8 card 17-11  
configuring 6-7  
security  
configuring delay triggers 6-7  
ML-100T-8 card support for 6-2  
reported by the ML-100T-8 card 6-6  
SONET circuits  
Cisco IOS features 16-1  
configuring for ML-100T-8 card 16-1 to 16-20  
overview 16-1  
selective autonegotiation 17-3, 17-13  
service-policy command, traffic policies 12-15  
service-policy input command 12-16  
service-policy output command 12-16  
service-provider networks  
and customer VLANs 9-2  
and IEEE 802.1Q tunneling 9-1  
Layer 2 protocols across 9-9  
set cos command 12-15  
setting  
CE-100T-8 card 17-7  
in RPR 15-2  
SONET ports, administrative and service states for the  
CE-MR-10 card 17-16  
SONET ports, Enhanced State Model 17-4  
Spanning Tree Protocol. See STP  
SPR interface  
assigning bridge group for RPR 15-13  
assigning POS A-21  
assigning POS ports to 15-11  
framing mode A-6  
configuring for RPR on ML-100T-8 card 15-9 to 15-11  
RPR wrap mode A-24  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
spr-intf-id command A-21  
spr load-balance command A-22  
spr station-id command A-23  
spr wrap command A-24  
SSH  
limitations with IEEE 802.1Q trunks 7-8  
listening state 7-7  
monitoring status 7-20 to 7-22  
MSTP protocol tunneling 9-10  
multicast addresses, affect of 7-8  
overview 7-2  
configuration guidelines 16-3  
configuring 16-3  
redundant connectivity 7-8  
root switch 7-3  
configuring server 16-5  
displaying configuration and status 16-5  
overview 16-2  
supported number of spanning-tree instances 7-2  
timers, described 7-4  
setting up the ML-100T-8 card for 16-3  
starting  
unexpected behavior during root switch 7-17  
verifying status 7-20 to 7-22  
support, technical. See technical support  
syslog server C-3  
ML-100T-8 card 3-5  
RADIUS accounting 16-16  
STP  
See also BPDU  
T
accelerated aging 7-9  
blocking state 7-6  
tagged packets, Layer 2 protocol 9-9  
TCAM  
configuring 7-1 to 7-9, 7-15 to 7-20  
configuring forward-delay time 7-20  
configuring hello time 7-19  
configuring maximum-aging time 7-20  
configuring path cost 7-18  
configuring port priority 7-17  
configuring switch priority 7-18  
configuring the root switch 7-17  
creating topology 7-5  
configuring ACL size in 13-3  
modifying size for ACL 14-5  
technical support  
FTP service C-3  
gathering data C-1  
logging router output C-2  
providing data C-3  
show tech-support command C-2  
telnetting to Cisco IOS 3-2 to 3-3  
terminals  
default configuration 7-16  
disabled state 7-7  
disabling 7-16  
connecting to switch 3-4  
logging router output C-2  
terminal-emulation software 3-4  
TL1 on the ML-100T-8 card 1-6  
traffic class  
displaying status 7-20 to 7-22  
enabling 7-17  
extended system ID 7-4  
forward-delay time 7-6  
forwarding state 7-7  
bandwidth command 12-13  
creating 12-10  
interface states 7-5 to 7-8  
interoperability with RSTP 7-15  
Layer 2 protocol tunneling 9-9  
learning state 7-7  
traffic policy  
attaching interfaces 12-15 to 12-16  
creating 12-11 to 12-15  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
example 12-18  
and RPR 15-6  
service-policy command 12-15  
configuring as Layer 2 tunnel 9-12  
configuring IEEE 802.1Q 8-2, 8-3 to 8-5  
trunk ports 8-1  
tunneling  
defined 9-1  
customer numbering in service-provider  
networks 9-3  
monitoring operation 8-5  
number per system 8-1  
overview 8-1  
IEEE 802.1Q 9-1  
Layer 2 protocol 9-9  
tunnel ports  
STP and IEEE 802.1Q trunks 7-8  
trunk ports 8-1  
described 9-1  
IEEE 802.1Q, configuring 9-4, 9-11, 9-12  
incompatibilities with other features 9-4  
verifying operation 8-5  
VLAN-transparent and VLAN-specific  
services 9-6 to 9-9  
VoIP, configuration example 12-20  
VTP Layer 2 protocol tunneling 9-9  
vty 3-3  
U
upgrading Cisco IOS image 1-4  
user EXEC command mode 3-10  
W
V
warnings, definition i-xx  
VCAT  
CE-100T-8 card characteristics 17-10  
setting processing mode A-11  
verifying  
ACLs 14-5  
bridging 4-3 to 4-5  
EtherChannel 10-8  
IRB 11-4  
POS 6-8 to 6-9  
QoS configuration 12-16 to 12-17  
RPR 15-16  
SDM 13-3  
STP and RSTP status 7-20 to 7-22  
tunneling status 9-12  
VLANs 8-5  
virtual LANs. See VLANs  
VLANs  
aging dynamic addresses 7-9  
and QoS 12-4  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
Cisco ONS 15310-CL, ONS 15310-MA, and ONS 15310-MA SDH Ethernet Card Software Feature and Configuration Guide, R9.1 and R9.2  
78-19415-01  
IN-14  
Download from Www.Somanuals.com. All Manuals Search And Download.  

Beko Washer wmp601w User Manual
Blackberry Cell Phone 8110 User Manual
Black Box Computer Hardware High Density Media Converter System II User Manual
Blaupunkt Stereo Amplifier GTA 250 User Manual
Bosch Appliances Washer Dryer WFL 2090 User Manual
Bostitch Nail Gun RN45B User Manual
Briggs Stratton Pressure Washer 01936 User Manual
Canon Film Camera A2E User Manual
Casio Radio LK120 User Manual
C Crane Portable Radio PR D4VW User Manual