Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring ATM QoS or Shaping

• CBR, rtVBR, nrtVBR, and UBR
• Policing on a per VC basis
• Independent PCR and SCR policing
• Counting policing actions

Circuit Emulation PICs provide pseudowire service towards the core. This section describes the ATM service QoS features.

• cell—atm-ccc-cell-relay encapsulation
• aal5—atm-ccc-vc-mux

Note: Only ATM pseudowires are supported; no other encapsulation types are supported.

Since cells within a VC cannot be re-ordered, and since only the VC is mapped to a pseudowire, classification is not meaningful in the context of a pseudowire. However, different VCs can be mapped to different classes of traffic and can be classified in the core network.

Such a service would connect two ATM networks with an IP/MPLS core. Figure 1 shows that the routers marked PE are equipped with Circuit Emulation PICs.

Figure 1: Two ATM Networks with QoS Shaping and Pseudowire Connection

Figure 1 shows that traffic is shaped in the egress direction towards the ATM networks. In the ingress direction towards the core, the traffic is policed and the appropriate action is taken. Depending on a very elaborate state machine in the PIC, the traffic is either discarded or sent towards the core with a particular QoS class.

Each port has four transmit queues and one receive queue. Packets arrive from the ingress network on this single queue. Remember that this is per port and multiple VCs arrive on this queue, each with its own QoS class. To simplify unidirectional connections, only a Circuit Emulation PIC (PE 1 router) to Circuit Emulation PIC (PE 2 router) configuration is shown in Figure 2.

Figure 2: VC Mapping with Circuit Emulation PICs

Figure 2 shows the four VCs with different classes mapped to different pseudowires in the core. Each VC has a different QoS class and is assigned a unique queue number. This queue number is copied to the EXP bits in the MPLS header as follows:

Qn concatenated with CLP -> EXP

Qn is 2 bits and can have four combinations; 00, 01, 10, and 11. Since CLP cannot be extracted from the PIC and put into each packet prefix, it is 0. The valid combinations are shown in Table 1.

• VC 7.100 -> 00
• VC 7.101 -> 01
• VC 7.102 -> 10
• VC 7.103 -> 11

  Note: Lower queue numbers have higher priorities.

• VC 7.100 -> 000
• VC 7.101 -> 010
• VC 7.102 -> 100
• VC 7.103 -> 110

A packet arriving on VC 7.100 at the ingress router has the queue number 00 before being forwarded to the Packet Forwarding Engine. The Packet Forwarding Engine then translates this to 000 EXP bits in the core. At the egress router, the Packet Forwarding Engine retranslates this to queue 00 and stamps the packet with this queue number. The PIC receiving this queue number sends the packet out on the transmit queue that is mapped to queue 0, which could be the highest priority transmit queue on the egress side.

To briefly summarize, shaping and policing are possible. Classification is possible at the VC level by mapping a specific VC to a particular class.

To configure QoS shaping for Circuit Emulation PICs, use the shaping statement and its subordinate statements at the [interfaces at-fpc/pic/port unit n] hierarchy level. Most Circuit Emulation PIC QoS CLI commands are similar to those used for the ATM2 PIC QoS features. The interface configuration is sent to the PIC and the PIC driver configures the PIC appropriately.

The Routing Engine and the Packet Forwarding Engine prefix the packet with information including a field that indicates the queue number associated with the VC.

Circuit Emulation PICs internally define queue 0 for CBR, queue 1 for RTVBR, queue 2 for VBR, and queue 3 for UBR.