Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 16
▀ P-GW Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
358
To consolidate L2-level QoS marking across all interfaces, marking IP-DSCP values will be left to individual
applications as applications build IP headers. The DSCP value in IP-header will then be used to derive the L2 QoS
Values by platform (NPU). This derivation will be done in two steps.
applications as applications build IP headers. The DSCP value in IP-header will then be used to derive the L2 QoS
Values by platform (NPU). This derivation will be done in two steps.
1. DSCP will be mapped to an Internal-QoS value using a system-wide table.
2. Internal-QoS will be mapped to actual L2 value (either or both of 802.1p/MPLS) using a per-vrf based table.
2. Internal-QoS will be mapped to actual L2 value (either or both of 802.1p/MPLS) using a per-vrf based table.
Internal-QoS (Internal-Per-Hop-Behavior/IPHB) consists of 5 bits. 3 bits of class-of-service is user-configurable, while
the remaining 2 bits are left for future use to dynamically stamp a drop eligibility based on a rate-monitor.
the remaining 2 bits are left for future use to dynamically stamp a drop eligibility based on a rate-monitor.
The 64 DSCP values will map, each to any of the available 8 COS values of Internal-QoS. The 5 bits of Internal-QoS
will then map to 3+1 bits of 802.1p (the tos and drop-eligibility-indicator) and 3 bits of MPLS-Traffic-Class.
will then map to 3+1 bits of 802.1p (the tos and drop-eligibility-indicator) and 3 bits of MPLS-Traffic-Class.
In addition, the explicit configuration of 802.1p/MPLS-EXP is being deprecated and it will be replaced by new
construct of internal-qos.
construct of internal-qos.
Previous Behavior: Operator can set 802.1p and mpls priorities in the
qci-qos-mapping
table.
New Behavior: Operator can only configure internal-qos parameters.
Customer Impact: Due to backward compatibility, previous configuration should still work.
Going forward, customer can only configure
internal-qos
in
qci-qos-mapping
table.
Command Changes
associate
This new command is used to associate an internal QoS L2 mapping table to a VPN context.
configure
context vpn_name
associate l2-mapping-table name l2_mapping_table_name
default associate l2-mapping-table
end
Notes:
l2-mapping-table name l2_mapping_table_name
Specifies the name of an existing internal table from which to map QoS to L2 values.
map_table_name
is an alphanumeric string of 0 through 80 characters.
default
: Associates the system-default table with this context.
If an l2-mapping-table association is made at both the VRF and VPN level, the VRF level takes precedence.
If no explicit association is created/configured, the system-default mapping table is used.
associate l2-mapping-table
This new command is used to associate an internal QoS L2 mapping table to a specific VPN Routing and Forwarding
(VRF).
(VRF).
configure