Configuring Translation Tables on SONET/SDH OC48/STM16 IQE PICs
The SONET/SDH OC48/STM16 IQE PIC supports four types of translation tables: IP precedence, IPv4 DSCP, IPv6 DSCP, and MPLS (EXP). You can configure a maximum of eight tables for each supported type. If a translation table is enabled for a particular type of traffic, then behavior aggregate (BA) classification of the same type must be configured for that logical interface. That is, if you configure an IPv4 translation table, you must configure IPv4 BA classification on the same logical interface.
To configure ToS translation on the SONET/SDH OC48/STM16 IQE PIC:
Access the class-of-service hierarchy:
[edit] user@host# edit class-of-service
Define the type of translation table:
[edit class-of-service] translation-table { (to-dscp-from-dscp | to-dscp-ipv6-from-dscp-ipv6 | to-exp-from-exp | to-inet-precedence-from-inet-precedence) table-name { to-code-point value from-code-points (* | [ values ]); } }
On the SONET/SDH OC48/STM16 IQE PIC, incoming ToS bit translation is subject to the following rules:
Locally generated traffic is not subject to translation.
The
to-dscp-from-dscp
translation table type is not supported if an Internet precedence classifier is configured.The
to-inet-precedence-from-inet-precedence
translation table type is not supported if a DSCP classifier is configured.The
to-dscp-from-dscp
andto-inet-precedence-from-inet-precedence
translation table types cannot be configured on the same unit.The
to-dscp-from-dscp
andto-inet-precedence-from-inet-precedence
translation table types are supported for IPv4 packets.Only the
to-dscp-ipv6-from-dscp-ipv6
translation table type is supported for IPv6 packets.Only the
to-exp-from-exp
translation table type is supported for MPLS packets.The
from-code-points
statement establishes the values to match on the incoming packets. Thedefault
option is used to match all values not explicitly listed, and, as a single entry in the translation table, to mark all incoming packets on an interface the same way. Theto-code-point
statement establishes the target values for the translation. If an incoming packet header ToS bit configuration is not covered by the translation table list and a*
option is not specified, the ToS bits in the incoming packet header are left unchanged.
Translation tables are not supported if fixed classification is configured on the logical interface.