Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Applying a Rewrite Rule Definition to a Subscriber Interface in a Dynamic Profile

Rewrite rules define the marking for various CoS values, including DSCP, DSCP IPv6, IP precedence, and IEEE 802.1 CoS values. Rewrite rules have an associated forwarding class and code-point alias or bit set.

For dynamic CoS, you define the rewrite rules mapping for the CoS values statically, then reference the rewrite rule configuration in the dynamic profile for the subscriber interface.

To configure a rewrite rule in a dynamic profile:

  1. Define the rewrite-rules mapping for the traffic that passes through all queues on the interface. The available rewrite-rules types for dynamic CoS are dscp, dscpv6, ieee-802.1 and inet-precedence.

    See Configuring Rewrite Rules.

  2. Apply the rewrite-rules definition to the subscriber interface in the dynamic profile.
    [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number]user@host# edit rewrite-rules
  3. Configure the applicable rewrite rule markers in the dynamic profile.
    • For DSCP:
      [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number rewrite-rules]user@host# set dscp (rewrite-name | default)
    • For DSCPv6:
      [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number rewrite-rules]user@host# set dscp-ipv6 (rewrite-name | default)
    • For IEEE 802.1:
      [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number rewrite-rules]user@host# set ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner)
    • For inet-precedence:
      [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number rewrite-rules]user@host# set inet-precedence (rewrite-name | default)

Published: 2012-11-29