Use this procedure to create a user-defined Per Hop Behavior (PHB) profile for Tunnel segments and Pseudowire (PW) segments. A PHB profile is the externally observable forwarding behavior applied at a DS-compliant (Diff-Serv) node belonging to a DS domain. See PHB profile.
For each MPLS packet received there is a EXP-bits field in the MPLS header. For each EXP value received the user must associate a PHB.
PHB profile AIDs are uniquely assigned by the system:
The AID for a PHB Profile is PHBPROF-{2-8}.
The AID for a User defined PHB Profile is PHBPROF-{3-8}.
A proprietary factory PHB profile is identified by PHBPROF-2. It cannot be deleted or modified.
Refer to the Alcatel-Lucent 1850 Transport Service Switch (TSS-5) TL1 Command Guide for T-MPLS, for help on using TLI commands.
1 |
Login to the VLNC42B. |
2 |
From the Navigation menu, select TMPLS → Quality of Service → PHB Profile Configuration. Equivalent TL1 command: ent-phb-prof. Result: The PHB Profile Configuration screen displays. |
3 |
In the PHB Profile drop-down box, select Create to create a new profile or select an existing profile to modify. |
4 |
In the drop-down boxes for each of the EXP Bit (0-7), select the parameters as required, then click Submit. Valid values: {EF, HIGH2, AF1, AF2 [AF21, AF22], AF3, AF4 [AF41, AF42], DE [Green: DE-G Yellow:DE-Y], LOW2}. Equivalent TLI command: Enter ENT-PHB-PROF:[TID]::[CTAG]::EXP0,EXP1,EXP2,EXP3,EXP4,EXP5,EXP6,EXP7; where EXP0 thru EXP7 associates a PHB class to the MPLS packets with the specified EXP value 0 -7. Example, Profile #2: ENT-PHB-PROF:::QOS001::EF,HIGH2,AF1,AF2,AF3,AF4,DE,LOW2; Note: The Exp Bit # and PHB class value is one to one mapping. The PHB class should be unique in each Exp Bit #. For example, if EF is selected for the Exp Bit 0, then it shall not be available for other Exp Bit #. Result: An Access Identifier (PHBPROF-{3-8}) is assigned for the PHB profile. End of steps |
In the E2T direction, ETS inFlows on a UNI can be configured to support different CIR/CBS and PIR/PBS values (with policing enabled).
The color information is used to control drop probability on the T-MPLS NNI within the VLNC42B.
At the same time the color information is encoded in the EXP-bits according to the configured PHB profile in the E2T direction.
In the T2E direction, EXP-bits are decoded and the color information is used to control drop probabilities at the terminating UNI.
Beginning in Release 7.2.2, Alcatel-Lucent 1850 TSS-5 supports two profiles.
A PHB Profile is the externally observable forwarding behavior applied at a DS-compliant (Diff-Serv) node belonging to a DS domain. When a T-MPLS circuit is created, it is associated to the default PHB mapping table or, the user can create a new PHB mapping table and associate the PHB to it.
A set of “data treatments” (defined as PHB Scheduling Classes [PSCs]) are applied to packets on each NE inside the DiffServ domain, where this treatment includes both:
Selection of the queue and schedule discipline to apply at NE egress interface
Congestion thresholds to be applied over NE egress queues.
The user can profile the NE forwarding behavior for TU Segment and PW Segment, combining PHB. Table 9-1, PSC set and related CIR, PIR, CBS and PBS relationship shows the MPLS Diff-Serv Forwarding Plane as supported in the System with corresponding Ethernet Forwarding Classes and Queue types (either Strict Priority queue or Weighted Fair Queue). The user can use the following PSCs:
EF — MPLS Expedited Forwarding. MPLS Scheduling Class Type used for giving preferential queuing treatment in a Strict Priority queue. Useful Class for providing low-loss, low-jitter and low-delay handling within a MPLS node.
HIGH2 — MPLS Scheduling Class Type used for delay/jitter sensitive traffic and sharing both the same relationship with MPLS PSC bandwidth-based parameters and the same queuing type as in MPLS EFPSC.
AF — Assured Forwarding. MPLS Scheduling Class Type defines 4 independent forwarding classes (denotes as AF1, AF2, AF3, AF4). These PSCs are used when, in case of congestion, is necessary to define the drop precedence of a packet according to AFn class. Both Green and Yellow packets belonging to the same AF class are not requested to be re-ordered from the System: both Green and Yellow packets belonging to the same AF class are requested to be sent to the same egress WFQ forwarding queue. Profile #1 is composed of 4 PHB {AF31,AF32,AF41,AF42}. Profile #2 is composed of 8 PHB {AF11,AF12, AF21,AF22,AF31,AF32,AF41,AF42}
DE — Default Behavior. MPLS Scheduling Class Type identifies the existing “best effort” traffic.
LOW2 — The same queuing type and the same relationship with MPLS PSC bandwidth-based parameters as in MPLS DE PSC.
Refer to the ent-phb-prof command in the Alcatel-Lucent 1850 Transport Service Switch (TSS-5) TL1 Command Guide for T-MPLS for more information.
PHB |
Profile |
Ethernet Forwarding Class |
Bandwidth based PSC parameters |
Queue Type | |||
---|---|---|---|---|---|---|---|
CIR |
PIR |
CBS |
PBS | ||||
EF |
Profile 1 and 2 |
Gua |
(PIR=CIR)&(CIR>0) |
(PBS=CBS)&(CBS>0) |
Strict Priority | ||
High2 |
Profile 1 and 2 |
Gua(2) |
(PIR=CIR)&(CIR>0) |
(PBS=CBS)&(CBS>0) |
Strict Priority | ||
AF1 |
Profile 2 |
Reg(1) |
(PIR>=CIR)&(CIR>=0) |
(PBS>0)&(CBS>=0) |
Weighted Fair Queue | ||
AF2 |
Profile 2 |
Reg |
(PIR>=CIR)&(CIR>=0) |
(PBS>0)&(CBS>=0) |
Weighted Fair Queue | ||
AF3 |
Profile 1 and 2 |
Reg(3) |
(PIR>=CIR)&(CIR>=0) |
(PBS>0)&(CBS>=0) |
Weighted Fair Queue | ||
AF4 |
Profile 1 and 2 |
Reg(4) |
(PIR>=CIR)&(CIR>=0) |
(PBS>0)&(CBS>=0) |
Weighted Fair Queue | ||
DE |
Profile 1 and 2 |
BE |
(PIR>=CIR)&(CIR>=0) |
(PBS>0)&(CBS>=0) |
Weighted Fair Queue | ||
LOW2 |
Profile 2 |
BackGr |
(PIR>=CIR)&(CIR>=0) |
(PBS>0)&(CBS>=0) |
Weighted Fair Queue |
Copyright © 2011 Alcatel-Lucent. All rights reserved. |