Quality of Service

The Quality of Service feature is applied throughout the network to ensure that network traffic is prioritized according to required criteria and that the desired traffic receives preferential treatment. This chapter contains the following sections:

QoS General

Quality of Service (QoS) is a feature on the switch which prioritizes traffic resulting in a performance improvement for critical network traffic. QoS varies by switch, as the higher the level switch, the higher the network application layer it works with. The number of queues differ, as well as the kind of information used to prioritize.

QoS Properties

Quality of Service (QoS) prioritizes the traffic flow based on the type of traffic and can be applied to prioritize traffic for latency-sensitive applications (such as voice or video) and to control the impact of latency-insensitive traffic.

To configure QoS properties, follow these steps:

Procedure

Step 1

Click Quality of Service > General > QoS Properties.

Step 2

Set the QoS mode. The following options are available:

  • Disable—QoS is disabled on the device.

  • Basic—QoS is enabled on the device in Basic mode.

  • Advanced—QoS is enabled on the device in Advanced mode.
Step 3

Select Port/LAG and click GO to display/modify all ports/LAGs on the device and their CoS information.

The following fields are displayed for all ports/LAGs:

  • Interface—Type of interface.

  • Default CoS—Default VPT value for incoming packets that do not have a VLAN Tag. The default CoS is 0.

Step 4

Click Apply. The Running Configuration file is updated.

To set QoS on an interface, select it, and click Edit.

Step 5

Enter the parameters.

  • Interface—Select the port or LAG.

  • Default CoS—Select the default CoS (Class-of-Service) value to be assigned for incoming packets (that do not have a VLAN tag).
Step 6

Click Apply. The interface default CoS value is saved to Running Configuration file.

To restore the default CoS values, click Restore CoS Defaults.

Queue

The device supports 8 queues for each interface. Queue number eight is the highest priority queue. Queue number one is the lowest priority queue.

There are two ways of determining how traffic in queues is handled, Strict Priority and Weighted Round Robin (WRR).

  • Strict Priority—Egress traffic from the highest-priority queue is transmitted first. Traffic from the lower queues is processed only after the highest queue has been transmitted, thus providing the highest level of priority of traffic to the highest numbered queue.

  • Weighted Round Robin (WRR)—In WRR mode the number of packets sent from the queue is proportional to the weight of the queue (the higher the weight the more frames are sent). For example, if there are a maximum of four queues possible and all four queues are WRR and the default weights are used, queue 1 receives 1/15 of the bandwidth (assuming all queues are saturated and there’s congestion), queue 2 receives 2/15, queue 3 receives 4/15 and queue 4 receives 8 /15 of the bandwidth. The type of WRR algorithm used in the device isn’t the standard Deficit WRR (DWRR), but rather Shaped Deficit WRR (SDWRR).

The queuing modes can be selected in the Queue page. When the queuing mode is by strict priority, the priority sets the order in which queues are serviced, starting with the highest priority queue and going to the next lower queue when each queue is completed.

When the queuing mode is Weighted Round Robin, queues are serviced until their quota has been used up and then another queue is serviced. It’s also possible to assign some of the lower queues to WRR, while keeping some of the higher queues in strict priority. In this case traffic for the strict-priority queues is always sent before traffic from the WRR queues. Only after the strict-priority queues have been emptied is traffic from the WRR queues forwarded. (The relative portion from each WRR queue depends on its weight).

To select the priority method and enter WRR data, complete the following steps:

Procedure

Step 1

Click Quality of Service > General > Queue.

Step 2

Enter the parameters.

  • Queue—Displays the queue number.

  • Scheduling Method—Select one of the following options:

    • Strict Priority—Traffic scheduling for the selected queue and all higher queues is based strictly on the queue priority.

    • WRR—Traffic scheduling for the selected queue is based on WRR. The period time is divided between the WRR queues that aren’t empty, meaning they have descriptors to egress. This division happens only if the strict-priority queues are empty.

    • WRR Weight—If WRR is selected, enter the WRR weight assigned to the queue.

    • % of WRR Bandwidth—Displays the amount of bandwidth assigned to the queue. These values represent the percent of the WRR weight.
Step 3

Click Apply. The queues are configured, and the Running Configuration file is updated.

CoS/802.1p to a Queue

The CoS/802.1p to Queue page maps 802.1p priorities to egress queues. The CoS/802.1p to Queue Table determines the egress queues of the incoming packets based on the 802.1p priority in their VLAN Tags. For incoming untagged packets, the 802.1p priority is the default CoS/802.1p priority assigned to the ingress ports.

The following table describes the default mapping when there are 8 queues:

802.1p Values 
(0-7, 7 being the highest)

Queue (8 queues 1-8, 8 is the highest priority)

Notes

0

2

Background

1

1

Best Effort

2

3

Excellent Effort

3

4

Critical Application - LVS phone SIP

4

5

Video

5

6

Voice - Cisco IP phone default

6

7

Interwork Control
 LVS phone RTP

7

8

Network Control

By changing the CoS/802.1p to Queue mapping (CoS/802.1p to Queue) and the Queue schedule method and bandwidth allocation, it’s possible to achieve the desired quality of service in a network.

The CoS/802.1p to Queue mapping is applicable only if one of the following exists:

  • The device is in QoS Basic mode and CoS/802.1p trusted mode.

  • The device is in QoS Advanced mode and the packets belong to flows that are CoS/802.1p trusted.

To map CoS values to egress queues, follow these steps:

Procedure

Step 1

Click Quality of Service > General > CoS/802.1p to Queue.

Step 2

Enter the parameters.

  • 802.1p—Displays the 802.1p priority tag values to be assigned to an egress queue, where 0 is the lowest and 7 is the highest priority.

  • Output Queue—Select the egress queue to which the 802.1p priority is mapped. Either four or eight egress queues are supported, where Queue 4 or Queue 8 is the highest priority egress queue and Queue 1 is the lowest priority.

Step 3

For each 802.1p priority, select the Output Queue to which it is mapped.
Step 4

Click Apply, Cancel or Restore Defaults. 801.1p priority values to queues are mapped, and the Running Configuration file is updated, the changes that entered are canceled, or previously defined values are restored.

IP Precedence to a Queue

The IP Precedence to Queue page maps IP Precedence priorities to egress queues. The IP Precedence to Queue Table determines the egress queues of the incoming packets based on the IP Precedence priority.

The following table describes the default mapping when there are 8 queues:

IP Precedence Values (0-7,7 being the highest)

Queue (8 queues 1-8,8 is the highest priority)

Notes

0

1

Background

1

2

Best Effort

2

3

Excellent Effort
3

4

Critical Application - LVS phone SIP

4

5

Video

5

6

Voice - Cisco IP phone default

6

7

Interwork Control LVS phone RTP

7

8

Network Control

By changing the IP Precedence to Queue mapping (IP Precedence to Queue) and the Queue schedule method and bandwidth allocation, it’s possible to achieve the desired quality of service in a network.

The IP Precedence to Queue mapping is applicable to IP packets if:

  • The device is in QoS Basic mode and IP Precedence is the trusted mode.

  • The device is in QoS Advanced mode and the packets belongs to flows that are IP Precedence trusted.

To map IP Precedence values to egress queues, follow these steps:

Procedure

Step 1

Click Quality of Service > General > IP Precedence to Queue.

Step 2

Enter the parameters.

  • IP Precedence—Displays the IP Precedence priority values to be assigned to an egress queue, where 0 is the lowest and 7 is the highest priority.

  • Output Queue—Select the egress queue to which the IP Precedence priority is mapped.

Step 3

For each IP Precedence priority, select the Output Queue to which it is mapped.
Step 4

Click Apply, Cancel or Restore Defaults. IP Precedence priority values to queues are mapped, and the Running Configuration file is updated, the changes that entered are canceled, or previously defined values are restored.

DSCP to Queue

The DSCP (IP Differentiated Services Code Point) to Queue page maps DSCP values to egress queues. The DSCP to Queue Table determines the egress queues of the incoming IP packets based on their DSCP values. The original VPT (VLAN Priority Tag) of the packet is unchanged.

By simply changing the DSCP to Queue mapping and the Queue schedule method and bandwidth allocation, it’s possible to achieve the desired quality of services in a network.

The DSCP to Queue mapping is applicable to IP packets if:

  • The device is in QoS Basic mode and DSCP is the trusted mode.

  • The device is in QoS Advanced mode and the packets belongs to flows that are DSCP trusted.

Non-IP packets are always classified to the best-effort queue.

The following tables describe the default DSCP to queue mapping for an 8-queue system where 8 is highest:

DSCP

63

55

47

39

31

23

15

7

Queue

8

7

6

5

4

3

2

1

DSCP

62

54

46

38

30

22

14

6

Queue

8

7

6

5

4

3

2

1

DSCP

61

53

45

37

29

21

13

5

Queue

8

7

6

5

4

3

2

1

DSCP

60

52

44

36

28

20

12

4

Queue

8

7

6

5

4

3

2

1

DSCP

59

51

43

35

27

19

11

3

Queue

8

7

6

5

4

3

2

1

DSCP

58

50

42

34

26

18

10

2

Queue

8

7

6

5

4

3

2

1

DSCP

57

49

41

33

25

17

9

1

Queue

8

7

6

5

4

3

2

1

DSCP

56

48

40

32

24

16

8

0

Queue

8

7

6

5

4

3

2

1

To map DSCP to queues, follow these steps:

Procedure

Step 1

Click Quality of Service > General > DSCP to Queue.

The DSCP to Queue page contains Ingress DSCP. It displays the DSCP value in the incoming packet and its associated class.
Step 2

Select the Output Queue (traffic forwarding queue) to which the DSCP value is mapped.
Step 3

Click Apply. The Running Configuration file is updated. Click Restore Defaults to restore the default settings.

Queue to CoS_802_1p

Use the Queues to CoS/802.1p page to remark the CoS/802.1p priority for egress traffic from each queue.

To map queues to CoS values, follow these steps:

Procedure

Step 1

Click Quality of Service > General > Queues to CoS/802.1p.

Step 2

Enter the parameters.

  • Output Queue—Display the egress queue to which the 802.1p priority is mapped.

  • 802.1p—Select the 802.1p priority tag values to be remarked.
Step 3

For each output queue, select the CoS/802.1p priority to which egress traffic from the queue is remarked
Step 4

Click Apply, Cancel or Restore Defaults. Queues to 801.1p priority values are remarked, and the Running Configuration file is updated, the changes that entered are canceled, or previously defined values are restored.

Queue to IP Precedence

Use the Queues to IP Precedence page to remark the IP Precedence value for egress traffic from each queue.

To map queues to IP Precedence values, follow these steps:

Procedure

Step 1

Click Quality of Service > General > Queues to IP Precedence.

Step 2

Enter the parameters.

  • Output Queue—Display the egress queue to which the IP Precedence value is mapped.

  • IP Precedence—Select the IP Precedence values to be remarked.
Step 3

For each output queue, select the IP Precedence value to which egress traffic from the queue is remarked.
Step 4

Click Apply, Cancel or Restore Defaults. Queues to IP Precedence priority values are remarked, and the Running Configuration file is updated, the changes that entered are canceled, or previously defined values are restored.

Queue to DSCP

Use the Queues to DSCP page to remark the DSCP value for egress traffic from each queue.

To map queues to DSCP values, follow these steps:

Procedure

Step 1

Click Quality of Service > General > Queues to DSCP.

Step 2

Enter the parameters.

  • Output Queue—Display the egress queue to which the DSCP value is mapped.

  • DSCP—Select the DSCP values to be remarked.
Step 3

For each output queue, select the DSCP value to which egress traffic from the queue is remarked.
Step 4

Click Apply, Cancel or Restore Defaults. Queues to DSCP priority values are remarked, and the Running Configuration file is updated, the changes that entered are canceled, or previously defined values are restored.

Remark Interface

Use the Remark Interface Settings page to remark the CoS/802.1p priority, IP precedence, and DSCP value for egress traffic on a port. The CoS/802.1p priority and IP or the CoS/802.1p priority and DSCP value can be remarked simultaneously, but the DSCP value and IP cannot be remarked simultaneously

To remark egress traffic on an interface:

Procedure

Step 1

Click Quality of Service > General > Remark Interface Settings.

Step 2

Select an interface type (Port or LAG), and click Go.

Step 3

Select a Port/LAG, and click Edit.

Step 4

Enter the parameters.

  • Interface—Select the port or LAG to be defined.

  • Remark CoS—Check Enable to remark the CoS/802.1p priority for egress traffic on this port or LAG.

  • Remark IP Precedence—Check Enable to remark the IP precedence for egress traffic on this port or LAG.

  • Remark DSCP—Check Enable to remark the DSCP value for egress traffic on this port or LAG.
Step 5

Click Apply. The Running Configuration is updated

Bandwidth

The Bandwidth page displays bandwidth information for each interface. To view the bandwidth information, complete the following steps:

Procedure

Step 1

Click Quality of Service > General > Bandwidth.

The fields in this page are described in the Edit page below, except for the following fields:

  • Ingress Rate Limit:

    • Status—Displays whether Ingress Rate Limit is enabled.

    • Rate Limit (KBits/sec)—Displays the ingress rate limit for the port.

    • %—Displays the ingress rate limit for the port divided by the total port bandwidth.

  • Egress Shaping Rates:

    • Status—Displays whether Egress Shaping Rates is enabled.

    • CIR (KBits/sec)—Displays the maximum bandwidth for the egress interface.
Step 2

Select an interface, and click Edit.

Step 3

Select the Port interface.
Step 4

Enter the fields for the selected interface:

Option Description

Ingress Rate Limit

Select to enable the ingress rate limit, which is defined in the field below. (Not relevant for LAGs).

Ingress Rate Limit (Kbits per sec)

Enter the maximum amount of bandwidth allowed on the interface. (Not relevant for LAGs).

Egress Shaping Rate

Select to enable egress shaping on the interface.

Committed Information Rate (CIR)

Enter the maximum bandwidth for the egress interface.
Step 5

Click Apply. The bandwidth settings are written to the Running Configuration file.

Egress Shaping per Queue

In addition to limiting transmission rate per port, which is done in the Bandwidth page, the device can limit the transmission rate of selected egressing frames on a per-queue per-port basis. Egress rate limiting is performed by shaping the output load.

The device limits all frames except for management frames. Any frames that aren’t limited are ignored in the rate calculations, meaning that their size isn’t included in the limit total.

To configure the egress shaping per queue, complete the following steps:

Procedure

Step 1

Click Quality of Service > General > Egress Shaping per Queue.

The Egress Shaping Per Queue page displays the rate limit (CIR) for each queue.
Step 2

Select an interface type (Port), and click Go.

Step 3

Select a Port, and click Edit.

This page enables shaping the egress for up to eight queues on each interface.
Step 4

Select the Interface.
Step 5

For each queue that is required, enter the following fields:

  • Enable Shaping—Select to enable egress shaping on this queue.

  • Committed Information Rate (CIR)—Enter the maximum rate (CIR) in Kbits per second (Kbps). CIR is the average maximum amount of data that can be sent.

Step 6

Click Apply. The bandwidth settings are written to the Running Configuration file.

VLAN Ingress Rate Limit

Rate limiting per VLAN, performed in the VLAN Ingress Rate Limit page, enables traffic limiting on VLANs. When VLAN ingress rate limiting is configured, it limits aggregate traffic from all the ports on the device.

The following constraints apply to rate limiting per VLAN:

  • It has lower precedence than any other traffic policing defined in the system. For example, if a packet is subject to QoS rate limits but is also subject to VLAN rate limiting, and the rate limits conflict, the QoS rate limits take precedence.

To define the VLAN ingress rate limit, complete the following steps:

Procedure

Step 1

Click Quality of Service > General > VLAN Ingress Rate Limit.

This page displays the VLAN Ingress Rate Limit Table.
Step 2

Click Add.

Step 3

Enter the parameters.

  • VLAN ID—Select a VLAN.

  • Committed Information Rate (CIR)—Enter the average maximum amount of data that can be accepted into the VLAN in Kilobits per second.

Step 4

Click Apply. The VLAN rate limit is added, and the Running Configuration file is updated.

VLAN Port Ingress Rate Limit

Rate limiting per VLAN port, performed on the VLAN Port Ingress Rate Limit page, enables traffic limiting on the ports that are bound to a specific VLAN. When VLAN port ingress rate limiting is configured, it limits aggregate traffic from the specified ports on the switch.

The following constraints apply to rate limiting per VLAN:

  • It has lower precedence than any other traffic policing defined in the system. For example, if a packet is subject to QoS rate limits but is also subject to VLAN port rate limiting, and the rate limits conflict, the QoS rate limits take precedence.

To define the VLAN Port ingress rate limit, complete the following steps:

Procedure

Step 1

Click Quality of Service > General > VLAN Port Ingress Rate Limit.

Step 2

Click Add.

Step 3

Enter the parameters:

  • VLAN ID—Select a VLAN

  • Committed Information Rate (CIR)—Enter the average maximum amount of data that can be accepted into the VLAN in Kilobits per second

  • Interface — Enter an interface or a range of interfaces. The interfaces must be bound to the selected VLAN.
Step 4

Click Apply. The VLAN Port rate limit is added, and the Running Configuration file is updated

TCP Congestion Avoidance

The TCP Congestion Avoidance page enables activating a TCP congestion avoidance algorithm. The algorithm breaks up or avoids TCP global synchronization in a congested node, where the congestion is due to various sources sending packets with the same byte count.

To configure TCP congestion avoidance complete the following steps:

Procedure

Step 1

Click Quality of Service > General > TCP Congestion Avoidance.

Step 2

Click Enable to enable TCP congestion avoidance, and click Apply.

QoS Basic Mode

In QoS Basic mode, a specific domain in the network can be defined as trusted. Within that domain, packets are marked with 802.1p priority and/or DSCP to signal the type of service they require. Nodes within the domain use these fields to assign the packet to a specific output queue. The initial packet classification and marking of these fields is done in the ingress of the trusted domain.

QoS Global Settings

The Global Settings page contains information for enabling Trust on the device (see the Trust Mode field below). This configuration is active when the QoS mode is Basic mode. Packets entering a QoS domain are classified at the edge of the QoS domain.

To define the Trust configuration, complete the following steps:

Procedure

Step 1

Click Quality of Service > QoS Basic Mode > Global Settings.

Step 2

Select the Trust Mode while the device is either in Basic or Advanced mode. If a packet CoS level and DSCP tag are mapped to separate queues, the Trust mode determines the queue to which the packet is assigned:

  • CoS/802.1p—Traffic is mapped to queues based on the VPT field in the VLAN tag, or based on the per-port default CoS/802.1p value (if there’s no VLAN tag on the incoming packet), the actual mapping of the VPT to queue can be configured in the mapping CoS/802.1p to Queue page.

  • DSCP—All IP traffic is mapped to queues based on the DSCP field in the IP header. The actual mapping of the DSCP to queue can be configured in the DSCP to Queue page. If traffic isn’t IP traffic, it’s mapped to the best effort queue.

  • CoS/802.1p-DSCP—Either CoS/802.1p or DSCP whichever has been set.
Step 3

Click Apply. The Running Configuration file is updated with the new DSCP values. Click Restore Defaults to go back to the default settings.

QoS Interface Settings

The Interface Settings page enables configuring QoS on each port of the device, as follows:

  • QoS State Disabled on an Interface—All inbound traffic on the port is mapped to the best effort queue and no classification/prioritization takes place.

  • QoS State of the Port is Enabled—Port prioritize traffic on ingress is based on the system-wide configured trusted mode, which is either CoS/802.1p trusted mode or DSCP trusted mode.

To enter QoS settings per interface, complete the following steps:

Procedure

Step 1

Click Quality of Service > QoS Basic Mode > Interface Settings.

Step 2

Use the filter to select the Interface Type (Port or Lag) and click Go to display the current settings. QoS State displays whether QoS is enabled on the interface

Step 3

Select an interface, and click Edit.

Step 4

Select the Port or LAG interface.
Step 5

Click to enable or disable QoS State for this interface.
Step 6

Click Apply. The Running Configuration file is updated.

QoS Advanced Mode

Frames that match an ACL and permitted entrance are implicitly labeled with the name of the ACL that permitted their entrance. Advanced mode QoS actions can then be applied to these flows.

In QoS advanced mode, the device uses policies to support per flow QoS. A policy and its components have the following characteristics and relationships:

  • A policy contains one or more class maps.

  • A class map defines a flow with one or more associating ACLs. Packets that match only ACL rules (ACE) in a class map with Permit (forward) action are considered belonging to the same flow, and are subjected to the same quality of services. Thus, a policy contains one or more flows, each with a user defined QoS.

  • The QoS of a class map (flow) is enforced by the associating policer. There are two type of policers, single policer and aggregate policer. Each policer is configured with a QoS specification. A single policer applies the QoS to a single class map, and thus to a single flow, based on the policer QoS specification. An aggregate policer applies the QoS to one or more class maps, and thus one or more flows. An aggregate policer can support class maps from different policies.

  • Per flow QoS are applied to flows by binding the policies to the desired ports. A policy and its class maps can be bound to one or more ports, but each port is bound with at most one policy.

Global Settings

The Global Settings page contains information for enabling Trust on the device. Packets entering a QoS domain are classified at the edge of the QoS domain.

To define the Trust configuration:

Procedure

Step 1

Click Quality of Service > QoS Advanced Mode > Global Settings.

Step 2

Select the Trust Mode while the device is in Advanced mode. If a packet CoS level and DSCP tag are mapped to separate queues, the Trust mode determines the queue to which the packet is assigned:

  • CoS/802.1p—Traffic is mapped to queues based on the VPT field in the VLAN tag, or based on the per-port default CoS/802.1p value (if there’s no VLAN tag on the incoming packet), the actual mapping of the VPT to queue can be configured in the mapping CoS/802.1p to Queue page.

  • DSCP—All IP traffic is mapped to queues based on the DSCP field in the IP header. The actual mapping of the DSCP to queue can be configured in the DSCP to Queue page. If traffic isn’t IP traffic, it’s mapped to the best effort queue.

  • CoS/802.1p-DSCP—Select to use Trust CoS mode for non-IP traffic and Trust DSCP for IP traffic.
Step 3

Select the default Advanced mode QoS trust mode (either trusted or untrusted) for interfaces in the Default Mode Status field. This provides basic QoS functionality on Advanced QoS, so that you can trust CoS/DSCP on Advanced QoS by default (without having to create a policy).

Step 4

In QoS Advanced Mode, when the Default Mode Status is set to Not Trusted, the default CoS values configured on the interface is ignored and all the traffic goes to queue 1. See the Quality of Service > QoS Advanced Mode > Global Settings page for details.

Step 5

If you have a policy on an interface then the Default Mode is irrelevant, the action is according to the policy configuration and unmatched traffic is dropped.

Class Mapping

A Class Map defines a traffic flow with ACLs (Access Control Lists) defined on it. A MAC ACL, IP ACL, and IPv6 ACL can be combined into a class map. Class maps are configured to match packet criteria on a match-all or match-any basis. They are matched to packets on a first-fit basis, meaning that the action associated with the first-matched class map is the action performed by the system. Packets that match the same class map are considered to belong to the same flow.


Note

Defining class maps doesn’t have any effect on QoS; it’s an interim step, enabling the class maps to be used later.

If more complex sets of rules are needed, several class maps can be grouped into a supergroup called a policy.

In the same class map, a MAC ACL can’t be used with an IPv6 ACE that has a Destination IPv6 address as a filtering condition.

The Class Mapping page shows the list of defined class maps and the ACLs comprising each, and enables you to add/delete class maps.

To define a Class Map, complete the following steps:

Procedure

Step 1

Click Quality of Service > QoS Advanced Mode > Class Mapping.

For each class map, the ACLs defined on it are displayed along with the relationship between them. Up to three ACLs can be displayed along with their Match, which is Or. This indicates the relationship between the ACLs. The Class Map is then the result of the three ACLs combined with Or.

Step 2

Click Add.

A new class map is added by selecting one or two ACLs and giving the class map a name. If a class map has two ACLs, you can specify that a frame must match both ACLs, or that it must match either one or both of the ACLs selected.

Step 3

Enter the parameters.

  • Class Map Name—Enter the name of a new class map.

  • Match ACL Type—The criteria that a packet must match in order to be considered to belong to the flow defined in the class map. The options are:

    • IP—A packet must match either of the IP-based ACLs in the class map.

    • MAC—A packet must match the MAC-based ACL in the class map.

    • IP or MAC—A packet must match either the IP-based ACL or the MAC-based ACL in the class map.

  • IP—Select the IPv4 based ACL or the IPv6 based ACL for the class map.

  • MAC—Select the MAC-based ACL for the class map.

  • Preferred ACL—Select whether packets are first matched to an IP or MAC.
Step 4

Click Apply. The Running Configuration file is updated.

Aggregate Policer

You can measure the rate of traffic that matches a predefined set of rules. To enforce limits, use ACLs in one or more class maps to match the desired traffic, and use a policer to apply the QoS on the matching traffic.

A policer is configured with a QoS specification. There are two kinds of policers:

  • Single (Regular) Policer—A single policer applies the QoS to a single class map, and to a single flow based on the policer's QoS specification. When a class map using single policer is bound to multiple ports, each port has its own instance of single policer. Thus, each applying the QoS on the class map (flow) at ports that are otherwise independent of each other. A single policer is created in the Policy Table page.

  • Aggregate Policer—An aggregate policer applies the QoS to one or more class maps, and one or more flows. An aggregation policer can support class maps from different policies. An aggregate policer applies QoS to all its flows in aggregation regardless of policies and ports. An aggregate policer is created in the Aggregate Policer page.

    An aggregate policer is defined if the policer is to be shared with more than one class. Policers on a port can’t be shared with other policers in another device.

Each policer is defined with its own QoS specification with a combination of the following parameters:

  • A maximum allowed rate, called a Committed Information Rate (CIR), measured in Kbps.

  • An action to be applied to frames that are over the limits (called out-of-profile traffic), where such frames can be passed as is, dropped, or passed, for all subsequent handling within the device.

  • Configures traffic policing on the basis of the specified rates and optional actions Enter the CIR and these optional values and actions

Assigning a policer to a class map is done when a class map is added to a policy. If the policer is an aggregate policer, you must create it using the Aggregate Policer page.

To define an aggregate policer, complete the following steps:

Procedure

Step 1

Click Quality of Service > QoS Advanced Mode > Aggregate Policer.

This page displays the existing aggregate policers.
Step 2

Click Add.

Step 3

Enter the parameters.

  • Aggregate Policer Name—Enter the name of the Aggregate Policer.

  • Ingress Committed Information Rate (CIR)—Enter the maximum bandwidth allowed in bits per second. See the description of this in the Bandwidth.

  • Exceed Action—Select the action to be performed on incoming packets that exceed the CIR. Possible values are:

    • Drop—Packets exceeding the defined CIR value are dropped.
Step 4

Click Apply. The Running Configuration file is updated.

Policy Table

The Policy Table Map page displays the list of advanced QoS policies defined in the system. The page also allows you to create and delete policies. Only those policies that are bound to an interface are active.

Each policy consists of:

  • One or more class maps of ACLs which define the traffic flows in the policy.

  • One or more aggregates that applies the QoS to the traffic flows in the policy.

After a policy has been added, class maps can be added by using the Policy Table page. To add a QoS policy, complete the following steps:

Procedure

Step 1

Click Quality of Service > QoS Advanced Mode > Policy Table.

This page displays the list of defined policies.
Step 2

Click Policy Class Map Table to display the Policy Class Maps page or click Add to open the Add Policy Table page.

Step 3

Enter the name of the new policy in the New Policy Name field.
Step 4

Click Apply. The QoS policy profile is added, and the Running Configuration file is updated.

Policy Class Maps

One or more class maps can be added to a policy. A class map defines the type of packets that are considered to belong to the same traffic flow.

To add a class map to a policy:

Procedure

Step 1

Click Quality of Service > QoS Advanced Mode > Policy Class Maps.

Step 2

Select a policy in the Filter, and click Go. All class maps in that policy are displayed.

Step 3

To add a new class map, click Add.

Step 4

Enter the following parameters.

Policy Name

Displays the policy to which the class map is being added.

Class Map Name

Select an existing class map to be associated with the policy. Class maps are created in the Class Mapping page.

Action Type

Select the action regarding the ingress CoS/802.1p and/or DSCP value of all the matching packets.

  • Use default trust mode—If this option is selected, use the default mode status in Global Trust mode. If the default mode status is “Not Trusted”, ignore the ingress CoS/802.1p and/or DSCP value and the matching packets are sent as best effort.

  • Always Trust—If this option is selected, the device trusts the matching packet based on the Global Trust mode (selected in the Global Settings page). It ignores the Default Mode status (selected in the Global Settings page).

  • Set—If this option is selected, use the value entered in the New Value box to determine the egress queue of the matching packets as follows:

    If the new value (0..7) is a CoS/802.1p priority, use the priority value and the CoS/802.1p to Queue Table to determine the egress queue of all the matching packets.

    If the new value (0..63) is a DSCP, use the new DSCP and the DSCP to Queue Table to determine the egress queue of the matching IP packets. Otherwise, use the new value (1..8) as the egress queue number for all the matching packets.

Police Type

Select the policer type for the policy. The options are:

  • None—No policy is used.

  • Single—The policer for the policy is a single policer.

  • Aggregate—The policer for the policy is an aggregate policer.
Step 5

If Police Type is Aggregate, select the Aggregate Policer.
Step 6

If Police Type is Single, enter the following QoS parameters:

Ingress Committed Information Rate (CIR)

Enter the CIR in Kbps. See a description of this in the Bandwidth page.

Exceed Action

Select the action assigned to incoming packets exceeding the CIR. The options are:

  • Drop—Packets exceeding the defined CIR value are dropped.
Step 7

Click Apply.

Policy Binding

The Policy Binding page shows which policy profile is bound and to which port. A policy can be bound to an interface as an ingress (input) policy. When a policy profile is bound to a specific port, it’s active on that port. Only one policy profile can be configured per port and per direction. However, a single policy can be bound to more than one port.

When a policy is bound to a port, it filters and applies QoS to traffic that belongs to the flows defined in the policy.

To edit a policy, it must first be removed (unbound) from all those ports to which it’s bound.


Note

It’s possible to either bind a port to a policy or to an ACL but both can’t be bound.

To define policy binding, complete the following steps:

Procedure

Step 1

Click Quality of Service > QoS Advanced Mode > Policy Binding.

Step 2

Select an Interface Type if required.
Step 3

Click Go. The policies for that interface are displayed.

Step 4

Click Edit.

Step 5

Select the following for the input policy/interface:

  • Input Policy Binding—Select to bind the input policy to the interface.

  • Policy Name—Select the input policy being bound.
Step 6

Click Apply. The QoS policy binding is defined, and the Running Configuration file is updated.