exp (Rewrite rules)

Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules exp] hierarchy level.

The default mapping.

By default, IP precedence rewrite rules alter the first three bits on the type-of-service (ToS) byte while leaving the last three bits unchanged. This default behavior applies to rewrite rules you configure for MPLS packets with IPv4 payloads. You configure these types of rewrite rules by including the mpls-inet-both or mpls-inet-both-non-vpn option at the [edit class-of-service interfaces interface interface-name unit logical-unit-number rewrite-rules exp rewrite-rule-name protocol] hierarchy level. The IP precedence rewrite rules explanation does not apply to ACX Series Universal Metro routers.

On interfaces configured on Modular Port Concentrators (MPCs) and Modular Interface Cards (MICs) on MX Series 5G Universal Routing Platforms and EX Series switches, we highly recommend that you configure the default option when you configure a behavior aggregate (BA) classifier that does not include a specific rewrite rule for MPLS packets. Doing so ensures that MPLS exp value is rewritten according to the BA classifier rules configured for forwarding or packet loss priority. This does not apply to ACX Series Universal Metro routers.

Specify one or more protocol matching criteria:

• mpls-any—Apply to MPLS packets, write MPLS header only.

• mpls-inet-both—Apply to IPv4 MPLS packets, write MPLS and IPv4 header.

• mpls-inet-both-non-vpn—Apply to IPv4 MPLS packets, write MPLS and IPv4 header for only non VPN traffic.

Junos OS Evolved supports only the mpls-any option. Devices running Junos OS Evolved do not support different rewrite rules for VPN and non-VPN traffic.