Applying Egress Interface Rewrite Rules to the IEEE 802.1p Field for All Host Outbound Traffic on the Interface
This topic describes how to apply rewrite rules for egress logical interfaces to the IEEE 802.1p field for all host outbound traffic on those interfaces on MX Series routers and EX Series switches.
This task requires separately configured rewrite rules that map packet loss priority information to the code point value in the 802.1p field for data traffic on egress logical interfaces. See Rewriting Packet Headers to Ensure Forwarding Behavior.
To configure the rewrite rules:
Configure the CoS rewrite rules to map the forwarding class to the desired value for the 802.1p field.
Associate the rewrite rules to the desired egress logical interfaces.
(Optional) Configure the forwarding class for host outbound traffic. Do not configure this forwarding class if you want to use the default forwarding class assignment (input classification).
To configure the rewrite rules to apply to the host outbound traffic IEEE 802.1p field:
Configure the rewrite rules.
[edit class-of-service host-outbound-traffic ieee-802.1] user@host# set rewrite-rules
Note:Enabling IEEE 802.1p rewrite rules for host outbound traffic on a DPC installed on an MX Series device without creating any corresponding IEEE 802.1p rewrite rules on a logical interface on the DPC causes the IEEE 802.1p code point to be automatically set to 000 for all host generated traffic that exits that logical interface.
[edit class-of-service]
rewrite-rules {
ieee-802.1 rewrite_foo {
forwarding-class network-control {
loss-priority low code-point 101;
}
}
}
interfaces {
ge-1/0/0 {
unit 100 {
rewrite-rules {
ieee-802.1 rewrite_foo vlan-tag outer-and-inner;
}
}
}
}
host-outbound-traffic {
forwarding-class network-control;
}
host-outbound-traffic {
ieee-802.1 {
rewrite-rules;
}
}