Brocade Multi-Service IronWare Security Configuration Guide (Supporting R05.6.00) - Manual (Page 154)

136 Multi-Service IronWare Security Configuration Guide
53-1003035-02
Filtering and priority manipulation based on 802.1p priority
3
• 4 – qosp4
• 5 – qosp5
• 6 – qosp6
• 7 – qosp7
If a packet’s 802.1p value is forced to another value by its assignment to a lower value queue,
it will retain that value when it is sent out through the outbound port.
The default behavior on previous revisions of this feature was to send the packet out with the
higher of two possible values: the initial 802.1p value that the packet arrived with or the new
(higher) priority that the packet has been “forced” to.
• priority-mapping – Matches on the packet’s 802.1p value. This option does not change the
packet’s forwarding priority through the device or mark the packet.
• drop-precedence – Assigns traffic that matches the ACL to a drop precedence value between 0
-3.
drop-precedence-force – This keyword applies in situations where there are conflicting priority
values for packets on an Ingress port, that conflict can be resolved by performing a priority merge
(the default) or by using a force command to direct the device to use a particular value above other
values. The drop-precedence-force keyword specifies that if a drop precedence is applied on the
port the ACL keyword will override existing or default mappings, however, if forced at the ingress
port, the port value will prevail over the acl value. Assigns traffic that matches the ACL to a drop
precedence value between 0 -3.
Example using the priority option (IPv4)
In the following IPv4 example, access list 100 assigns TCP packets with the source and destination
addresses specified to internal priority 2 and maps them to the 802.1p value 2 when outbound.
Brocade(config)#access-list 100 permit tcp 10.1.1.0/24 10.23.45.0/24 priority 2
The priority parameter specifies one of the 8 internal priorities of the Brocade device. Possible
values are between 0 and 7. If the outgoing interface is an 802.1q interface, the packet will have its
802.1p (QoS) priority marked with the new priority defined in this ACL.
Example using the priority force option
In the following IPv4 ACL example, access list 100 assigns UDP packets with the source and
destination addresses specified to the internal priority 3.
Brocade(config)#access-list 100 permit udp 10.1.1.0/24 10.23.45.0/24
priority-force 3
The priority-force parameter specifies one of the 8 internal priorities of the Brocade device.
Possible values are between 0 and 7.
For limitations when using the priority-force parameter, please see “Configuration considerations
for IPv4 outbound ACLs on VPLS, VLL, and VLL-Local endpoints” .
Example using the priority mapping option
In the following IPv4 ACL example, access list 100 permits UDP packets with the source and
destination addresses specified and the 802.1p priority 7.