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-7
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
ML-Series QoS
Weights are assigned to each queue as a result of the service provisioning process. When coupled with
policing and policy mapping provisioning, these weights and the WDRR scheduling process ensure that
QoS commitments are provided to each service flow.
Figure 11-5 illustrates the ML-Series card’s queuing and scheduling.
Figure 11-5 Queuing and Scheduling Model
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.
96502
Low Latency Queues
Weighted
Deficit
Round
Robin
Unicast Queues
Weighted
Deficit
Round
Robin
Weighted
Deficit
Round
Robin
Multi/Broadcast Queues
Weighted
Deficit
Round
Robin
Queues assigned by
"Priority" Command for
associated Classification
for Scheduling
Queues assigned by
"Bandwith" Command for
associated Classification
for Scheduling
Queues automatically
assigned