policy-map (Class of Service)
Syntax
policy-map policy-map-name {
inet-precedence proto-ip code-point [alias | bits];
inet-precedence proto-mpls code-point [alias | bits];
inet6-precedence proto-ip code-point [alias | bits];
inet6-precedence proto-mpls code-point [alias | bits];
dscp proto-ip code-point [alias | bits];
dscp proto-mpls code-point [alias | bits];
dscp-ipv6 proto-ip code-point [alias | bits];
dscp-ipv6 proto-mpls code-point [alias | bits];
exp all-label code-point [alias | bits];
exp outer-label code-point [alias | bits];
ieee-802.1 outer code-point [alias | bits];
ieee-802.1 outer-and-inner code-point [alias | bits];
ieee-802.1ad outer code-point [alias | bits];
ieee-802.1ad outer-and-inner code-point [alias | bits];
}
Hierarchy Level
[edit class-of-service]
Description
Define the packet-marking scheme (rewrite rules) for a customer. Traditionally, packet marking in
Junos uses the forwarding class and loss priority determined from a behavior
aggregate (BA) classifier or multifield classifier. This approach does not allow
rewrite rules to be directly assigned for each customer because of the limited
number of combinations of forwarding class and loss priority.
policy-map enables you to define rewrite rules on a
per-customer basis.
On devices running Junos OS, creating a policy map requires you to enable
enhanced-ip, enhanced-ethernet, or
enhanced-mode under [edit chassis network-services].
On devices running Junos OS Evolved, you must enable
policy-map-marking on each egress logical interface that
you want to do policy map marking. You enable
policy-map-marking at the [edit class-of-service
interfaces
interface-name
unit
unit-number] hierarchy level.
Policy maps have the following configuration restrictions:
-
When configuring both
proto-ipandproto-mplsoptions forinet-precedence,inet6-precedence,dscp, ordscp-ipv6, you must configure both options with the same code point or code point alias. -
You cannot configure
inet-precedenceanddscpin the same policy map. -
You cannot configure
inet6-precedenceanddscp-ipv6in the same policy map. -
In case of MPLS SWAP/PUSH operation, only the new labels are marked on all label-switching routers (LSRs), except the penultimate hop case where if it exposes the next label in the stack, then the exposed label is marked. Therefore, with the penultimate hop, the service label is changed.
-
You cannot configure
ieee-802.1andieee-802.1adin the same policy map. -
You cannot configure both
outerandouter-and-inneroptions forieee-802.1andieee-802.1adcode points in the same policy map. -
For IEEE 802.1ad with the
outer-and-inneroption, the discard eligibility (DE) bit is marked only for the outer VLAN header. For the inner VLAN header, only the three CoS Bits are marked.
You assign the policy map to a customer through a firewall action on an ingress or egress firewall filter (where the match conditions identify the customer). Alternatively, you can also assign a policy map to an ingress interface or a routing instance. A policy map is executed on a packet just before it is queued, so it overrides any other packet-marking scheme that was previously applied to the packet.
Options
alias |
The predefined CoS code point alias on the device. |
bits |
The bit pattern for the CoS code point. |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 16.1R1.
inet6-precedence options added in Junos OS Release 24.2R1.
Refer to Feature Explorer for platform and release support information.