Configuring H-QoS for the Skylight element: GT

Overview

Service providers that deploy Ethernet business services can face significant challenges in maintaining efficient bandwidth usage and per-application Quality of Service (QoS), since companies typically use several business-critical applications over a single Ethernet connection. Each application may be subject to individual Service Level Agreements (SLAs), and application requirements for bandwidth, latency, delay variation, and availability vary widely, which lead many service providers to turn to Hierarchical QoS (H-QoS). When implemented correctly, H-QoS strategies provide application acceleration, management of bandwidth per flow or per priority, and SLA assurance while maximizing access bandwidth efficiency.

This article provides a technical overview of H-QoS for the Skylight element: GT. It begins with an overview of the general structure and architecture, then follows with an in-depth discussion of concepts and definitions. Several configuration examples are provided to illustrate the concepts in context.

Standard QoS

The simplest form of QoS is implemented by allocating a predetermined quantity of committed and/or excess (that is, best-effort) bandwidth per application or per customer. Doing so ensures that the customer’s performance expectations are met. For example, a customer requiring 2 Mbps of committed bandwidth for VoIP services and 10 Mbps best-effort bandwidth for Internet access would have the Committed Information Rate (CIR) and Excess Information Rate (EIR) profiles shown in the table below as Class of Service 1 (CoS1, top priority) and Class of Service 2 (CoS2, lower priority):

Establishing a Basic QoS Scheme Using Dedicated Bandwidth

In this example, the service provider must plan 12 Mbps of access capacity for the customer served by this access link. Although at least 2 Mbps must be firmly committed, the other 10 Mbps could be overprovisioned in the access network. The link provided to the customer would have a total provisioned aggregate bandwidth capability of 12 Mbps, even though a significant proportion of the link might not be used on a regular basis.

Hierarchical QoS (H-QoS)

Hierarchical QoS recognizes the inefficiency of overprovisioning for worst-case usage scenarios, and makes better use of network resources and access bandwidth. It achieves these improvements by giving preferential treatment (priority) to applications considered to be more important (that is. QoS-sensitive) and by allowing bandwidth sharing between services. By treating the unique requirements of each application individually, service providers can thus maintain QoS for each application while greatly increasing the number of concurrent applications sharing a single EVC.

If a simple H-QoS scheme was applied to the customer requirements, the service provider would be able to supply the same functionality to the customer over a 10 Mbps link instead of the 12 Mbps allocated with basic QoS. The table below illustrates how a basic QoS hierarchy can be implemented to achieve these results:

Establishing H-QoS Through Hierarchical Bandwidth Allocation

In this scenario, the service provider defines that CoS1 has priority over CoS2 and provisions a 10 Mbps link. When traffic with CoS1 is present, the network dedicates up to 2 Mbps CIR to the VoIP service, leaving the remainder to CoS2 (best-effort Internet service). When no VoIP traffic is present, the 2 Mbps assigned to CoS1 are made available to CoS2 packets, thereby providing a total capacity of 10 Mbps for Internet access.

In both the standard and H-QoS examples illustrated above, CoS2 is defined as best-effort (EIR); there are no guarantees that the full 10 Mbps capacity is available for the Internet access application. This means that the expected performance is delivered equally by both the CoS ad H-QoS implementations; however, the H-QoS implementation directly achieves 20% savings in bandwidth efficiency that benefits both the access and core networks. Furthermore, the H-QoS implementation still enables network overprovisioning for the aggregate service (EVC) EIR of 8 Mbps.

H-QoS Functional Overview

The Skylight element: GT is equipped with six dedicated queues per port, as well as 12 user-assignable queues. When operating in protection mode, the dedicated queues associated with the LAG ports are unavailable because the LAG uses its own logical queues instead.

The system supports shaping on each individual queue, as well as the ability to shape an output stream associated with a group of queues. This concept is referred to as a Bandwidth Profile Envelope in the MEF 10.3 standard.

The Skylight element: GT’s queuing, shaping, and scheduling functions are closely interconnected, as shown below:

Queuing, Shaping and Scheduling on the Skylight element: GT

The first level of QoS can be achieved by configuring a traffic-shaping queue for each individual service. The second level of QoS involves binding services under a shaping envelope. Adding a port shaper can provide a further level of QoS by shaping all the traffic that travels through a physical port.

H-QoS Implementation Details

This section describes how to implement H-QoS on the Skylight element: GT in greater detail.

Queuing Profile

The role of a queuing profile is to map data frames to a queue, based on the frame’s internal CoS value. A queuing profile is associated with an output port, and maps all possible CoS value to one queue or several queues. All queues in a given map are associated with the same output port.

The queues that make up a queuing profile can be dedicated queues (DQ), logical queues (LQ), or user-assignable queues (AQ). The queue combinations within a given queuing profile can be any of the following:

• DQ only
• LQ only
• AQ only
• DQ and AQ
• LQ and AQ

Queuing Profile with Multiple Queues

Congestion Management

The system supports two different mechanisms to actively manage traffic congestion:

• Tail-Drop is a simple mechanism based on fixed thresholds for green or yellow traffic.
• BLUE is a more sophisticated active queue management algorithm that is based on packet loss and link utilization.

Tail Drop with Colored Levels

The system supports two levels (that is, thresholds) for a given queue: a green level and a yellow level. These levels define the maximum space available in the queue for green or yellow frames, respectively. The algorithm continually monitors the queue size to determine whether the queue contains sufficient room to receive new frames of each color.

Colored Tail-Drop Mechanism

The green and yellow levels are defined in the user interface by the following parameters:

Queue Management Parameters (Tail Drop)

BLUE Algorithm

BLUE is an active queue management algorithm that manages congestion control based on packet loss and link utilization history instead of queue occupancy. BLUE maintains a single probability (pm) to mark and/or drop packets. If the queue is continually dropping packets due to buffer overflow, BLUE increases pm, thus increasing the rate at which new packets will be dropped. Conversely, if the queue becomes empty or if the link is idle, BLUE decreases its marking probability. This approach effectively allows BLUE to learn the correct rate at which packets need to be dropped.

If the queue is close to dropping packets, pm is increased by the factor d1. If the queue is empty or close to being empty, pm is decreased by the factor d2.

The BLUE parameter freeze_time determines the time interval between two successive updates of pm. It allows changes in the marking probability to take effect before the value is updated again.

The BLUE algorithm is given below:

BLUE Algorithm

BLUE Algorithm Levels

The following parameters are used to configure BLUE in the user interface:

Queue Management Parameters (BLUE)

Traffic-Shaping Queue

Every queue in the system can support shaping. The traffic shaper’s implementation is based on the MEF 10.3 standard and uses a dual-token bucket algorithm. The shaper’s behavior is defined through the following parameters:

Queue Shaper Parameters

Shaping Envelope

The MEF 10.3 Bandwidth Profile Envelope is a mechanism that enables sharing unused bandwidth between flows. In the MEF definition, a flow’s unused bandwidth can be given to other flows. You define in a list how the sharing will take place, then store that information in a group called the Shaping Envelope.

The Shaping Envelope contains an ordered list of queues for which each flow’s shaping is defined, and for which the tokens’ overflow destination is specified. An example of a Shaping Envelope is presented in the figure below.

Each flow in an envelope is ordered, then assigned a rank. Doing so defines the order by which the overflowing between flows will occur. To overflow into a lower rank’s flow, the coupling flag (CF) must be set to 0. Below the lowest rank (rank #1), the envelope’s own coupling flag (CF0) is used to control whether the overflowing CIR tokens are shared or dropped.

• If CF0 = 0, the overflowing tokens are dropped.
• If CF0 = 1, the bandwidth unused by the CIRs is redirected to the highest-ranking yellow bucket.

The yellow bucket always overflows from the highest rank in an envelope to the lowest rank. After the last flow, any remaining tokens of the EIR are lost.

Shaping Envelope

Scheduling

The role of the scheduler is to select the queues from which the service frames will be extracted over time. The scheduler operates under two concurrent modes: strict priority and round-robin. Scheduling between queues with different priorities is based on strict priority, whereas scheduling between queues with the same priority is performed in a round-robin approach.

A queue’s priority and color are configurable. A queue can be configured as green or yellow if it does not shape. A green queue has a higher priority than a yellow queue. If the queue is configured to perform shaping, its color status is either green (CIR) or yellow (EIR), depending on how the traffic conforms to CIR vs. EIR when it is shaped.

Each outgoing port also has five queues reserved for specific Operation, Administration, and Maintenance (OAM) usage. The OAM queues are named as follows:

• CPU
• Packet Generator
• Monitor1
• Loopback
• Monitor2

Sixteen levels of queue priority are defined internally. The top levels (8-15) are reserved for internal OAM queues, and the lower levels (0-7) are for user traffic queues. The following figure depicts the overall scheduling system priorities.

Scheduling System Priorities

Port Shaping

The port shaper can be enabled if needed to shape all egressing traffic at port-level. The port shaper is a single token bucket system. The CIR and CBS are user-configurable.

The port shaper also provides the option to debit the outgoing CPU traffic (if any) from the port's CIR bucket. Although the CPU traffic is never shaped, you can choose to handle it separately from the port CIR or to use CIR tokens.

Configuration Examples

This section covers the following examples:

• Example 1: Basic QoS configuration with two services
• Example 2: A three-to-one aggregation, where the services coming on three physical customer ports are bundled, then transmiited out one network port.

Example 1: Basic QoS Configuration

This example shows how to configure QoS for two classes for service, with two traffic-shaping queues.

Requirements:

• One Skylight element: GT (or GT-S)
• Firmware version 6.2 or higher

Physical Setup:

Service Definition:

Configuration Steps:

1. Configure the traffic-shaping queues based on CoS requirements.

2. Configure the queuing profile.

3. Configure the traffic classifiers (filters).

4. Configure the traffic policies.

Each of these steps is explained below.

Step 1: Configure the traffic-shaping queues
You can create the services listed in the Service Definition above using basic traffic-shaping queues (non-sharing MEF 10.2 type).

The table below lists the parameters that must be configured in the system based on the service definition:

Traffic-Shaping Queue Configuration Parameters

This configuration is depicted in the figure below:

Two-Queue Traffic Shaping without Token Sharing

This basic example uses two dedicated queues from PORT-4, that is, one for each service to be created.

1. Access the page Traffic ▶ Shaping ▶ Queue ▶ Configuration. A list of all available shaping queues displays.

2. Make a selection from the Port drop-down list to limit the display to only the PORT-4 queues.

3. Click PORT-4-1 and configure the Premium service queue as follows:

• Enter a Name for the queue, such as Premium.
• Set the Priority to 3 (scheduling priority assigned to the queue).
• Enable the Shaping state.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate values to 40000 kbps.
• Set the Committed Burst Size value to 8 KiB; it can be set to a higher value if required.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0.
• The Excess Burst Size value is irrelevant, since EIR is set to 0.
• The default Maximum queue size is 64 KiB, but can be set to a different value as appropriate.

4. Click Apply.

5. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

6. Click PORT-4-2 and configure the Standard service queue as follows:

• Enter a Name for the queue, such as Standard.
• Set the Priority to 1.

• Enable the Shaping state.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate value to 60000 kbps.
• Set the Committed Burst Size value to 64 KiB; can be set to a higher value if required.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 40000 kbps.
• Set the Excess Burst Size value to 64 KiB; can be set to a higher value if required.
• Set the Maximum queue size to 1024 KiB.
• Click Apply.

Step 2: Configure the queuing profile
Because two dedicated queues from PORT-4 are being used to create the services, the default queuing profile for PORT-4 must be edited to configure how the customer’s traffic will be mapped to each of the two queues.

1. Access the page Traffic ▶ Shaping ▶ Port ▶ Default Queuing Profile.
   A list of all default queuing profiles for the unit displays.

2. Click the PORT-4 queuing profile and configure this profile as follows:

• According to the Service Definition table, Premium traffic is assigned PCP 3. Consequently, PCP-3 traffic must be mapped to the Premium queue.
• Similarly, the Service Definition indicates that Standard traffic is assigned PCP 1. PCP-1 traffic must therefore be mapped to the Standard queue.
• Other PCP values are unused and can be mapped to the Standard queue.

The PORT-4 default queuing profile must be as follows:

Step 3: Configure the traffic classifiers (filters)
A VID set can be created as a way to filter the Premium service traffic tagged with C-VLAN 100 that is ingressing from the customer network.

1. Access the page Traffic ▶ VLAN ▶ VID Sets
   The VID sets are displayed in a grid, grouped by policy list.

2. Click Add.
   The VID Set page appears.

3. Configure the VID set filter as follows:

• Set the Policy list to Traffic-3.
• Enter a Name for the new VID set, such as Premium.
• Set the VLAN Type to C-VLAN.
• In the VD list (VIDs), enter 100.

4. Click Apply.

Standard traffic is any traffic other than C-VLAN 100. To filter this kind of traffic, use the preconfigured Layer 2 catchAll filter.

Step 4: Configure the traffic policies
For the Premium service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 3-1 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to default-queuing-profile.
• Set the Filter type to VID Set, and the Filter to Premium.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1000 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 3. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Standard service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.
2. Select Policy 3-2 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to default-queuing-profile.
• Set the Filter type to L2 Filter, and the Filter to catchAll.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1000 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 1. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

Example 2: H-QoS in a 3:1 Aggregation

This example shows how to configure H-QoS in a 3:1 aggregation:

• Three UNI ports, and one NNI port
• One customer per UNI port
• Four classes of service (CoS) are defined per customer

Requirements:

• One Skylight element: GT (or GT-S)
• Firmware version 6.2 or higher

Physical Setup:

Service Definition:
Customer 1

Total bandwidth: 100 Mbps

Configuration Parameters:

The total CIR is 50 Mbps; the total EIR is 50 Mbps. If all CIR and EIR tokens are used (that is, none are left over to be shared), the total bandwidth will be 100 Mbps, as specified in the requirements.

If, for example, the VoIP service is not used, its bandwidth (10 Mbps) can be shared with the Premium service, hence a CIRmax of 50 Mbps. Likewise, if the first two services were to use only all of their bandwidth allocation, the unused bandwidth can be shared with the Standard service. Setting the EIRmax to 100 Mbps is precisely what allows the Standard service to receive any unused bandwidth (up to 50 Mbps) from the higher-ranking services. In such a case, the total bandwidth is still 100 Mbps, which meets the service definition requirements.

The following diagram illustrates how bandwidth is shared in the three-queue envelope configuration used in this example:

Three-Queue Traffic Shaping Envelope

Customers 2 and 3 have identival service definitiions. Only the VLAN tagging parameters differ.

Customer 2

Total bandwidth: 100 Mbps

Customer 3

Total bandwidth: 100 Mbps

Configuration Steps:

1. Configure the traffic-shaping queues for Customer 1.
2. Configure the queuing profile for Customer 1.
3. Configure the shaping envelope for Customer 1.
4. Configure the traffic-shaping queues for Customer 2.
5. Configure the queuing profile for Customer 2.
6. Configure the shaping envelope for Customer 2.
7. Configure the traffic-shaping queues for Customer 3.
8. Configure the queuing profile for Customer 3.
9. Configure the shaping envelope for Customer 3.
10. Configure the traffic classifiers (filters).
11. Configure the traffic policies.

Step 1: Configure the traffic-shaping queues for Customer 1

Three dedicated queues from PORT-4 are used for Customer 1, that is, one for each service to be created.

1. Access the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.
   A list of all available shaping queues displays.

2. Click PORT-4-1 and configure the VoIP service queue as follows:

• Enter a Name for the queue, such as Cust1-VoIP.
• Set the Priority to 5.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate values to 10000 kbps.
• Leave the Committed Burst Size at its value of 1 KiB.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0 kbps.
• The Excess Burst Size value is irrelevant, since EIR and Maximum EIR are set to 0.
• Set the Maximum queue size and Yellow threshold to the minimum value of 16 KiB.

  ---

  Note: Allocating a small queue size can prevent introducing delay with VoIP.

  ---

• Click Apply.

3. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

4. Click PORT-4-2 and configure the Premium service queue as follows:

• Enter a Name for the queue, such as Cust1-Premium.
• Set the Priority to 3.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate to 40000 kbps and Maximum Committed Information Rate to 50000 kbps.
• Set the Committed Burst Size value to 8 KiB.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0 kbps.
• The Excess Burst Size value is irrelevant, since EIR and Maximum EIR are set to 0.
• Set the Maximum queue size and Yellow threshold values to 64 KiB.
• Click Apply.

5. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

6. Click PORT-4-3 and configure the Standard service queue as follows:

• Enter a Name for the queue, such as Cust1-Standard.
• Set the Priority to 1.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate values to 0 kbps.
• The Committed Burst Size value is irrelevant, since CIR and Maximum CIR are set to 0.
• Set the Excess Information Rate to 100000 kbps and Maximum Excess Information Rate to 150000 kbps.
• Set the Maximum queue size and Yellow threshold values to 512 KiB.
• Click Apply.

Step 2: Configure the queuing profile for Customer 1

1. Access the page Traffic ▶ Shaping ▶ Port ▶ Default Queuing Profile
   A list of all available queuing profiles displays.

2. Click the PORT-4 queuing profile and configure this profile as follows:

• According to the Service Definition, VoIP traffic is assigned PCP-5. Consequently, PCP-5 traffic must be mapped to the Cust1-VoIP queue.
• Premium traffic is assigned PCP-3 and must be mapped to the Cust1-Premium queue.
• Standard traffic is assigned PCP-1 and must be mapped to the Cust1-Standard queue.
• Other PCP values are unused and can be mapped to the Cust1-Standard queue.

Step 3: Configure the shaping envelope for Customer 1

1. Access the page Traffic ▶ Shaping ▶ Envelope.
   The Traffic Shaping Envelope Configuration page displays.

2. Click Add to create an envelope for Customer 1’s services as follows:

• Enter a Name for the envelope, such as Cust1-Envelope.
• From the Port drop-down list, select PORT-4.
• Set the Shaping Mode to INGRESS.
• Enable the Coupling-flag box.
• From the list of Available queues, move the Customer 1 queues into the Ranking list by selecting them then clicking the button.

  ---

  Note: Ensure that the queues’ ranking aligns with the service priorities you previously defined. Use the [+] and [-] buttons to reorder them if necessary.

  ---

• Click Apply.

Step 4: Configure the traffic-shaping queues for Customer 2

The three remaining dedicated queues from PORT-4 are used for Customer 2.

1. Access the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.
   A list of available shaping queues displays.

2. Click PORT-4-4 and configure the VoIP service queue as follows:

• Enter a Name for the queue, such as Cust2-VoIP.
• Set the Priority to 5.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate values to 10000 kbps.
• Leave the Committed Burst Size at its value of 1 KiB.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0 kbps.
• The Excess Burst Size value is irrelevant, since EIR and Maximum EIR are set to 0.
• Set the Maximum queue size and Yellow threshold to the minimum value of 16 KiB.
• Click Apply.

3. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

4. Click PORT-4-5 and configure the Premium service queue as follows:

• Enter a Name for the queue, such as Cust2-Premium.
• Set the Priority to 3.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate to 40000 kbps and Maximum Committed Information Rate to 50000 kbps.
• Set the Committed Burst Size value to 8 KiB.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0 kbps.
• The Excess Burst Size value is irrelevant, since EIR and Maximum EIR are set to 0.
• Set the Maximum queue size and Yellow threshold values to 64 KiB.
• Click Apply.

5. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

6. Click PORT-4-6 and configure the Standard service queue as follows:

• Enter a Name for the queue, such as Cust2-Standard.
• Set the Priority to 1.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate values to 0 kbps.
• The Committed Burst Size value is irrelevant, since CIR and Maximum CIR are set to 0.
• Set the Excess Information Rate to 100000 kbps and Maximum Excess Information Rate to 150000 kbps.
• Set the Excess Burst Size value to 64 KiB.
• Set the Maximum queue size and Yellow threshold values to 512 KiB.
• Click Apply.

Step 5: Configure the queuing profile for Customer 2

1. Access the page Traffic ▶ Shaping ▶ Queuing Profile.
   A list of all available queuing profiles for the unit displays.

2. Click Add.
   The Traffic Shaping Queuing Profile page displays.

3. Configure the queuing profile as follows:

• Enter a Name for the queuing profile, such as Cust2-Profile.
• Select PORT-4 from the Port drop-down list.
• Map PCP-5 to the Cust2-VoIP queue.
• Map PCP-3 to the Cust2-Premium queue.
• Map PCP-1 to the Cust2-Standard queue.
• Other PCP values are unused and can be mapped to the Cust2-Standard queue.

Step 6: Configure the shaping envelope for Customer 2

1. Access the page Traffic ▶ Shaping ▶ Envelope.
   The Traffic Shaping Envelope Configuration page displays.

2. Click Add to create an envelope for Customer 2’s services as follows:

• Enter a Name for the envelope, such as Cust2-Envelope.
• From the Port drop-down list, select PORT-4.
• Set the Shaping mode to INGRESS.
• Enable the Coupling-flag box.
• From the list of Available queues, move the Customer 2 queues into the Ranking list by selecting them then clicking the button.

  ---

  Note: Ensure that the queues’ ranking aligns with the service priorities you previously defined. Use the [+] and [-] buttons to reorder them if necessary.

  ---

• Click Apply.

Step 7: Configure the traffic-shaping queues for Customer 3

Three user-assignable queues are used for Customer 3.

1. Access the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.
   A list of all available shaping queues displays.

2. Click USR-1 and configure the VoIP service queue as follows:

• Select PORT-4 from the drop-down list for the Outgoing port.
• Enter a Name for the queue, such as Cust3-VoIP.
• Set the Priority to 5.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate to 10000 kbps.
• Leave the Committed Burst Size at its value of 1 KiB.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0 kbps.
• The Excess Burst Size value is irrelevant, since EIR and Maximum EIR are set to 0.
• Set the Maximum queue size and Yellow threshold to the minimum value of 16 KiB.

  ---

  Note: Allocating a small queue size can prevent introducing delay with VoIP.

  ---

• Click Apply.

3. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

4. Click USR-2 and configure the Premium service queue as follows:

• Select PORT-4 from the drop-down list for the Outgoing port.
• Enter a Name for the queue, such as Cust3-Premium.
• Set the Priority to 3.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate to 40000 kbps and Maximum Committed Information Rate to 50000 kbps.
• Set the Committed Burst Size value to 8 KiB.
• Set the Excess Information Rate and Maximum Excess Information Rate values to 0 kbps.
• The Excess Burst Size value is irrelevant, since EIR and Maximum EIR are set to 0.
• Set the Maximum queue size and Yellow threshold values to 64 KiB.
• Click Apply.

7. Return to the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

8. Click USR-3 and configure the Standard service queue as follows:

• Select PORT-4 from the drop-down list for the Outgoing port.
• Enter a Name for the queue, such as Cust3-Standard.
• Set the Priority to 1.
• Set the Shaping mode to INGRESS.
• Set the Committed Information Rate and Maximum Committed Information Rate values to 0 kbps.
• The Committed Burst Size value is irrelevant, since CIR and Maximum CIR are set to 0.
• Set the Excess Information Rate to 100000 kbps and Maximum Excess Information Rate to 150000 kbps.
• Set the Excess Burst Size value to 64 KiB.
• Set the Maximum queue size and Yellow threshold values to 512 KiB.
• Click Apply.

Step 8: Configure the queuing profile for Customer 3

1. Access the page Traffic ▶ Shaping ▶ Queuing Profile

2. Click Add.
   The Traffic Shaping Queuing Profile page displays.

3. Configure the queuing profile as follows:

• Enter a Name for the queuing profile, such as Cust3-Profile.
• Select PORT-4 from the Port drop-down list.
• Map PCP-5 to the Cust3-VoIP queue.
• Map PCP-3 to the Cust3-Premium queue.
• Map PCP-1 to the Cust3-Standard queue.
• Other PCP values are unused and can be mapped to the Cust3-Standard queue.

Step 9: Configure the shaping envelope for Customer 3

1. Access the page Traffic ▶ Shaping ▶ Envelope.
   The Traffic Shaping Envelope Configuration page displays.

2. Click Add to create an envelope for Customer 3’s services as follows:

• Enter a Name for the envelope, such as Cust3-Envelope.
• From the Port drop-down list, select PORT-4.
• Set the Shaping Mode to INGRESS.
• Enable the Coupling-flag box.
• From the list of Available queues, move the Customer 3 queues into the Ranking list by selecting them then clicking the button.

  ---

  *Note: Ensure that the queues’ ranking aligns with the service priorities you previously defined. Use the [+] and [-] *

  ---

• Click Apply.

Step 10: Configure the traffic classifiers

The various services defined in this example are EVC-based, which makes it possible to classify them in the traffic policies using VID set filters.

The following table lists the parameters to be configured for the VID sets:

VID Set Configuration Information for Example 2

Configure all 9 VID sets, based on the information provided in the table. The procedure below outlines the steps for configuring the first VID set.

1. Access the page Traffic ▶ VLAN ▶ VID Sets.
   The VID Set page appears. The VID sets are displayed in a grid, grouped by policy list.

2. Click Add and configure the VID set filter as follows:

• Set the Policy list to Traffic-1 (incoming port for Customer 1)
• Enter C100 as the Name for the new VID set.
• Set the VLAN Type to C-VLAN.
• In the VD list (VIDs), enter 100.
• Click Apply.

Repeat this procedure to create the other eight VID sets.

Step 11: Configure the traffic policies
CUSTOMER 1 Traffic Policies:

For the VoIP service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 1-1 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to default-queuing-profile.
• Set the Filter type to VID Set, and the Filter to C100.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1001 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 5. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Premium service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 1-2 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to default-queuing-profile.
• Set the Filter type to VID set, and the Filter to C110.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1001 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 3. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Standard service, follow these steps:

1. Access the page Traffic ▶ Policies. The Policy Lists page opens.
2. Select Policy 1-3 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to default-queuing-profile.
• Set the Filter type to VID Set, and the Filter to C120.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1001 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 4. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

CUSTOMER 2 Traffic Policies:

For the VoIP service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 2-1 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to Cust2-Profile.
• Set the Filter type to VID Set, and the Filter to C200.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1002 as the VLAN ID.
• Under CoS mapping, set the PCP Action to Direct.
• Under Direct mapping, set the PCP green value to 5. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Premium service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 2-2 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to Cust2-Profile.
• Set the Filter type to VID Set, and the Filter to C210.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1002 as the VLAN ID.
• Under CoS mapping, set the PCP Action to Direct.
• Under Direct mapping, set the PCP green value to 3. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Standard service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 2-3 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to Cust2-Profile.
• Set the Filter type to VID Set, and the Filter to C220.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1002 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 1. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

CUSTOMER 3 Traffic Policies:

For the VoIP service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 3-1 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to Cust3-Profile.
• Set the Filter type to VID Set, and the Filter to C300.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1003 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 5. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Premium service, follow these steps:

1. Access the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 3-2 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to Cust3-Profile.
• Set the Filter type to VID Set, and the Filter to C310.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1003 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 3. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.

For the Standard service, follow these steps:

1. Acces the page Traffic ▶ Policies.
   The Policy Lists page opens.

2. Select Policy 3-3 from the Policy Lists frame by clicking its name, then configure as follows:

• Set the Outgoing port to PORT-4.
• Set the Queuing Profile to Cust3-Profile.
• Set the Filter type to VID Set, and the Filter to C320.
• Under EVC mapping, set Push as the Encapsulation type, S-VLAN as the Ethertype, and enter 1003 as the VLAN ID.
• Under CoS mapping, set the PCP action to Direct.
• Under Direct mapping, set the PCP green value to 1. Doing so sets the PCP value in the S-VLAN tag, as well as the internal priority.
• Click Apply.