User manual
Table Of Contents
- Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide
- Contents
- Preface
- Overview of the ML-Series Card
- CTC Operations on the ML-Series Card
- Initial Configuration of the ML-Series Card
- Configuring Interfaces on the ML-Series Card
- Configuring POS on the ML-Series Card
- Configuring STP and RSTP on the ML-Series Card
- STP Features
- STP Overview
- Supported STP Instances
- Bridge Protocol Data Units
- Election of the Root Switch
- Bridge ID, Switch Priority, and Extended System ID
- Spanning-Tree Timers
- Creating the Spanning-Tree Topology
- Spanning-Tree Interface States
- Spanning-Tree Address Management
- STP and IEEE 802.1Q Trunks
- Spanning Tree and Redundant Connectivity
- Accelerated Aging to Retain Connectivity
- RSTP Features
- Interoperability with IEEE 802.1D STP
- Configuring STP and RSTP Features
- Default STP and RSTP Configuration
- Disabling STP and RSTP
- Configuring the Root Switch
- Configuring the Port Priority
- Configuring the Path Cost
- Configuring the Switch Priority of a Bridge Group
- Configuring the Hello Time
- Configuring the Forwarding-Delay Time for a Bridge Group
- Configuring the Maximum-Aging Time for a Bridge Group
- Verifying and Monitoring STP and RSTP Status
- STP Features
- Configuring VLANs on the ML-Series Card
- Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling on the ML-Series Card
- Configuring Link Aggregation on the ML-Series Card
- Configuring IRB on the ML-Series Card
- Configuring Quality of Service on the ML-Series Card
- Understanding QoS
- ML-Series QoS
- QoS on RPR
- Configuring QoS
- Monitoring and Verifying QoS Configuration
- QoS Configuration Examples
- Understanding Multicast QoS and Multicast Priority Queuing
- Configuring Multicast Priority Queuing QoS
- QoS not Configured on Egress
- ML-Series Egress Bandwidth Example
- Understanding CoS-Based Packet Statistics
- Configuring CoS-Based Packet Statistics
- Understanding IP SLA
- Configuring the Switching Database Manager on the ML-Series Card
- Configuring Access Control Lists on the ML-Series Card
- Configuring Resilient Packet Ring on the ML-Series Card
- Understanding RPR
- Configuring RPR
- Connecting the ML-Series Cards with Point-to-Point STS Circuits
- Configuring CTC Circuits for RPR
- Configuring RPR Characteristics and the SPR Interface on the ML-Series Card
- Assigning the ML-Series Card POS Ports to the SPR Interface
- Creating the Bridge Group and Assigning the Ethernet and SPR Interfaces
- RPR Cisco IOS Configuration Example
- Verifying Ethernet Connectivity Between RPR Ethernet Access Ports
- CRC Threshold Configuration and Detection
- Monitoring and Verifying RPR
- Add an ML-Series Card into an RPR
- Delete an ML-Series Card from an RPR
- Cisco Proprietary RPR KeepAlive
- Cisco Proprietary RPR Shortest Path
- Redundant Interconnect
- Configuring Security for the ML-Series Card
- Understanding Security
- Disabling the Console Port on the ML-Series Card
- Secure Login on the ML-Series Card
- Secure Shell on the ML-Series Card
- RADIUS on the ML-Series Card
- RADIUS Relay Mode
- RADIUS Stand Alone Mode
- Understanding RADIUS
- Configuring RADIUS
- Default RADIUS Configuration
- Identifying the RADIUS Server Host
- Configuring AAA Login Authentication
- Defining AAA Server Groups
- Configuring RADIUS Authorization for User Privileged Access and Network Services
- Starting RADIUS Accounting
- Configuring a nas-ip-address in the RADIUS Packet
- Configuring Settings for All RADIUS Servers
- Configuring the ML-Series Card to Use Vendor-Specific RADIUS Attributes
- Configuring the ML-Series Card for Vendor-Proprietary RADIUS Server Communication
- Displaying the RADIUS Configuration
- Configuring Bridging on the ML-Series Card
- CE-100T-8 Ethernet Operation
- Command Reference for the ML-Series Card
- [no] bridge bridge-group-number protocol {drpri-rstp | ieee | rstp}
- clear counters
- [no] clock auto
- interface spr 1
- [no] pos mode gfp [fcs-disabled]
- [no] pos pdi holdoff time
- [no] pos report alarm
- [non] pos trigger defects condition
- [no] pos trigger delay time
- [no] pos vcat defect {immediate | delayed}
- show controller pos interface-number [details]
- show interface pos interface-number
- show ons alarm
- show ons alarm defect {[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]}
- spr-intf-id shared-packet-ring-number
- [no] spr load-balance { auto | port-based }
- spr station-id station-id-number
- spr wrap { immediate | delayed }
- Unsupported CLI Commands for the ML-Series Card
- Using Technical Support
- Index
11-19
Cisco ONS 15310-CL and Cisco ONS 15310-MA Ethernet Card Software Feature and Configuration Guide R8.5
78-18133-01
Chapter 11 Configuring Quality of Service on the ML-Series Card
QoS Configuration Examples
class-map match-any and class-map match-all Commands Example
This section illustrates the difference between the class-map match-any command and the class-map
match-all command. The match-any and match-all options determine how packets are evaluated when
multiple match criteria exist. 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 11-6 shows a traffic class configured with the class-map match-all command.
Example 11-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 11-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 11-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 11-8, the SPR interface is specified as a parameter to the match input-interface CLI when
defining a class-map.
Example 11-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)