close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

keyboard_arrow_right

Applying Rewrite Rules to Output Logical Interfaces

date_range 14-Dec-23

arrow_backward

arrow_forward

To assign the rewrite-rules configuration to the output logical interface, include the rewrite-rules statement at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level:

[edit class-of-service interfaces interface-name unit logical-unit-number]
rewrite-rules {
    dscp (rewrite-name | <default>) protocol protocol-types;
    dscp-ipv6 (rewrite-name | <default>) protocol protocol-types;
    exp (rewrite-name | <default>) protocol protocol-types;
    exp-push-push-push <default>;
    exp-swap-push-push <default>;
    ieee-802.1 (rewrite-name | <default>) inet-prec vlan-tag (outer | outer-and-inner);
    inet-precedence (rewrite-name | <default>) protocol protocol-types;
    inet6-precedence (rewrite-name | <default>) protocol protocol-types;
}

On M120, M320 with an Enhanced III FPC, MX Series routers and T 4000 routers with Type 5 FPCs and EX Series switches, you can combine the dscp or inet-prec and exp options to set the DSCP or IP precedence bits and MPLS EXP bits independently on IP packets entering an MPLS tunnel.

For IQ PICs, you can configure only one IEEE 802.1 rewrite rule on a physical port. All logical ports (units) on that physical port should apply the same IEEE 802.1 rewrite rule. If you configure more than one IEEE 802.1 rewrite rule for the IQ PIC, the configuration check fails.

Logical interfaces do not support multiple dscp rewrite rules or multiple dscp-ipv6 rewrite rules for the same protocol.

In the following example, the DSCP bits specified in ss-dscp are applied to packets entering the MPLS tunnel on ge-2/1/1, and the DSCP bits specified in ss-v6dscp are applied to IPv6 packets. The EXP bits are set to the bit configuration specified in ss-exp:

content_copy zoom_out_map
[edit class-of-service interfaces]
ge-2/1/1
    unit 10 {
        rewrite-rules {
            dscp ssf-dscp protocol mpls; # Applies to IPv4 packets entering MPLS tunnel
            dscp-ipv6 ss-v6dscp protocol mpls; # Applies to IPv6 packets entering MPLS tunnel
            exp ss-exp; # Sets label EXP bits independently
        }
    }
}

You can use interface wildcards for interface-name and logical-unit-number. You can also include Layer 2 and Layer 3 rewrite information in the same configuration.

Note:

On M Series routers only, if you include the control-word statement at the [edit protocols l2circuit neighbor address interface interface-name] hierarchy level, the software cannot rewrite MPLS EXP bits.

DSCP and DSCP IPv6 rewrite rules are supported on M Series and T Series routers when non-queuing PICs are installed, but are disabled when queuing PICs are installed with the following exceptions:

On M320 routers, DSCP rewrite is supported on IQ, IQ2, IQE, and IQ2E PICs when used with the Enhanced III FPC.
On M120 routers, DSCP rewrite is supported on IQ, IQ2, IQE, and IQ2E PICs.

DSCP and DCSP IPv6 rewrite rules are supported on MX Series routers with MPC/MIC interfaces and on EX Series switches.

Inet6 precedence rewrite rules are supported on MX Series routers with MPC/MIC interfaces.

DSCP rewrite rules are not supported on T Series routers when IQ, IQ2, IQE, IQ2E, SONET/SDH OC48/STM16 IQE, or PD-5-10XGE-SFPP PICs are installed.

On M320 and T Series routers (except for T4000 routers with Type 5 FPCs), for a single interface, you cannot enable a rewrite rule on a subset of forwarding classes. You must assign a rewrite rule to either none of the forwarding classes or all of the forwarding classes. When you assign a rewrite rule to a subset of forwarding classes, the commit does not fail, and the subset of forwarding classes works as expected. However, the forwarding classes to which the rewrite rule is not assigned are rewritten to all zeros.

For example, if you configure a Differentiated Services Code Point (DSCP) rewrite rule, the bits in the forwarding classes to which you do not assign the rewrite rule are rewritten to 000000; if you configure an IP precedence rewrite rule, the bits in the forwarding classes to which you do not assign the rewrite rule are rewritten to 000.

Note:

ACX 5448 supports rewrite on services such as:

L2 (VLAN, VLAN-CCC - Priority Code Point (PCP))
L3 (IPv4 and IPv6 - Differentiated Services Code Point (DSCP))
MPLS (EXP - Experimental Bits)

For L2, rewrite information resides in the VLAN translation entry at the egress side. Without that entry, rewrite does not take place.

For VLAN-CCC (local cross-connect), the rewrite is supported by enabling VLAN translation entry in the same manner as that for L2.

arrow_backward PREVIOUS Setting Ingress DSCP Bits for Multicast Traffic over Layer 3 VPNs

NEXT arrow_forward Rewriting MPLS and IPv4 Packet Headers

Class of Service User Guide (Routers and EX9200 Switches)

Applying Rewrite Rules to Output Logical Interfaces

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Class of Service User Guide (Routers and EX9200 Switches)

Applying Rewrite Rules to Output Logical Interfaces

Related Documentation

Stay in touch