Cisco WS-X6416-GE-MT - Interface Module - Expansion Manual de usuario Pagina 37

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 51
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 36
White Paper
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 37 of 51
Cisco Catalyst OS Cisco IOS Software
set qos map 1p1q4t rx 2 1 cos 5
set qos map 1p2q2t tx 1 1 cos 0,1
set qos map 1p2q2t tx 3 1 cos 5
interface gigabitethernet 3/1
rcv-queue cos-map 2 1 5
wrr-queue cos-map 1 1 0 1
priority-queue cos-map 1 5
Queue Sizes
The total amount of buffer per port is a fixed quantity. However, the allocation of that packet buffer
per queue can be configured on most Ethernet ports. Specifically, the transmit buffer allocation
can be changed on the classic Fast Ethernet, any Gigabit Ethernet, and any 10 Gigabit Ethernet
line card. The receive buffer allocation is configurable on the fabric-enabled Fast Ethernet ports
(6548, 6524 line cards) and on the 10 Gigabit Ethernet ports (6501, 6502 line cards).
Cisco Catalyst OS Cisco IOS Software
set qos txq-ratio 1p2q2t 10 90
set qos rxq-ratio 1p1q0t 10 90
interface gigabitethernet 3/1
wrr-queue queue-limit 10 90
interface fastethernet 4/1
rcv-queue queue-limit 10 90
WRR Scheduling
The Weighted Round Robin (WRR) scheduling mechanism is used to prioritize traffic as it exits an
egress port. The prioritization is based on the relative weighting of each of the participating
queues, so that traffic in a higher priority queue will be serviced before traffic in a low priority
queue. The WRR scheduling feature is supported on the transmit queues for all Ethernet line
cards. An example (for Gigabit Ethernet ports) is shown below. As with the CoS-to-queue
mapping, the WRR scheduling is configured on a per-ASIC basis.
Cisco Catalyst OS Cisco IOS Software
set qos wrr 1p2q2t 30 70 interface gigabitethernet 3/1
wrr-queue bandwidth 30 70
Configuring QoS Policies
The configuration of QoS policies differs significantly between Cisco IOS Software and the Cisco
Catalyst OS. For the Cisco Catalyst OS, a QoS ACL statement is used to configure all match and
action parameters for marking and policing. Cisco IOS Software QoS supports classification,
marking, and policing using the Modular QoS CLI (MQC) syntax.
A Cisco IOS Software policy uses traffic classes (with the class-map statement) to identify
interesting traffic. These traffic classes can be defined for different types of traffic flows; for
example, a user could have a different class for IP traffic, IPX traffic, and MAC traffic. Each traffic
class uses Cisco IOS Software based ACLs and/or class match statements to identify traffic. The
policy-map includes the desired action for the matched traffic (mark, police, trust, etc). The policy
defined by a policy-map is mapped to an interface using the service-policy command.
Examples of both are included below.
Trust with an ACL
As an alternative to setting the trust state for all traffic on a port (as described above), a QoS policy
can be created to trust traffic that matches a specific QoS ACL. This functionality is available in
both the Cisco Catalyst OS and Cisco IOS Software. As such, it is a straightforward example of the
configuration differences between the Cisco Catalyst OS QoS ACL syntax and the Cisco IOS
Vista de pagina 36
1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 50 51

Comentarios a estos manuales

Sin comentarios