Host Outbound Traffic IEEE802.1p Rewrite
This topic describes how to rewrite the IEEE 802.1p field in the Ethernet frame header for host outbound traffic, that is, traffic generated by the Routing Engine. You can set a global value for the priority code point that applies to all host outbound traffic. Additionally, or alternatively, you can specify that rewrite rules are applied to all host outbound traffic on egress logical interfaces. These are rules that you have previously configured to set the IEEE 802.1p field for data traffic on those interfaces.
To configure the IEEE 802.1p field settings:
(Optional) Specify a global default value for the IEEE 802.1p field for all host outbound traffic.
(Optional) Specify that the IEEE 802.1p rewrite rules for the egress logical interfaces are applied to all host outbound traffic on those interfaces.
Configuring a Global Default IEEE 802.1p Value for All Host Outbound Traffic
This task describes how to configure a global default value for the IEEE 802.1p field for all host outbound traffic.
To configure a global default value for the IEEE 802.1p field:
Apply Egress Interface Rewrite Rules to the IEEE 802.1p Field for All Host Outbound Traffic on an 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.
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. See Configuring Rewrite Rules.
Associate the rewrite rules to the desired egress logical interfaces. See Applying Rewrite Rules to Output 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). See Overriding the Input Classification.
To configure the rewrite rules to apply to the host outbound traffic IEEE 802.1p field:
Enabling IEEE 802.1p rewrite rules for host outbound traffic without creating any corresponding IEEE 802.1p rewrite rules sets the IEEE 802.1p code point to be automatically 000 for all host generated traffic that exits that interface.
[edit class-of-service host-outbound-traffic ieee-802.1] user@host# set rewrite-rules
For example:
[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;
}
}
Platform-Specific Host Outbound Traffic Rewrite Behavior
Use Feature Explorer to confirm platform and release support for 802.1p rewrite rules for host outbound traffic.
Use the following table to review platform-specific behaviors for your platform:
|
Platform |
Difference |
|---|---|
|
ACX7000 |
ACX7000 routers support only the |