Administrator's Guide v4.1.1 Manual

Policer behavior for L2 and L3 control packets TABLE 81
Protocol Ingress Policer Egress Policer
LLDP Enabled if protocol is not enabled and disabled if protocol is enabled. Disabled
LACP Enabled if protocol is not enabled and disabled if protocol is enabled. Disabled
STP Enabled if protocol is not enabled and disabled if protocol is enabled. Disabled
DOT1X Enabled if protocol is not enabled and disabled if protocol is enabled. Disabled
PIM Disabled Enabled
OSPF Disabled Enabled
IGMP Disabled Enabled
VRRP/VRRP-E Disabled Enabled
When a Layer 2 control protocol is not enabled on an interface, packets are dropped during ingress
and are subjected to ingress policing. Layer 3 control packets, irrespective of whether they are
protocol-enabled or not, will not be subject to ingress and egress policing.
Lossless traffic with Policer
The following are considerations for lossless traffic:
• Policing is applicable only for lossy traffic. Lossless traffic should not get policed. For port-based
policing, apply a policy-map to an interface even if PFC is configured on that interface. The CoS
value (priority) on which PFC is applied is excluded from being policed.
• Remapped priority values should not include lossless priorities. Do not remap lossy traffic priorities
to lossless traffic priorities and vice-versa.
• Policer attributes conform-set-tc and exceed-set-tc should not be set to a lossless traffic class.
Configuring QoS
The following sections discuss configuring QoS, including fundamentals, traffic class mapping,
congestion control, rate limiting, BUM storm control, scheduling, DCB QoS, Brocade VCS Fabric QoS,
policer functions, and Auto QoS.
Configuring QoS fundamentals
NOTE
Refer to User-priority mapping on page 472.
Lossless traffic with Policer
486 Network OS Administrator’s Guide
53-1003225-04