|
|
|
Policing makes it possible for you to limit the bandwidth for ingress queues. You limit the bandwidth by specifying the guaranteed bit rate for a port. If this bit rate is exceeded, the switch drops the excess packets.
For example, if you set policing on an ingress queue to be 5 Mbps, and traffic exceeds that 5 Mbps rate, all traffic that exceeds the 5Mbps is dropped.
Only 80-series modules that are licensed for routing support the policing feature.
The policing algorithm includes a normal burst threshold. This threshold sets the size of bursts that is guaranteed transfer.
The switch uses queue 0 to forward protocol packets (ARP, VRRP, OSPF, and so on) to the supervisor module. If you enable policing on queue 0, be sure to allocate the queue enough bandwidth for management packets and learned packets. Failure to allocate enough bandwidth to the queue may result in poor network performance. Do not disable this queue by allocating it 0 bits per second (bps). If you disable the queue, all protocol packets and learned packets are discarded before reaching the supervisor module.
For information about how to set up policing, see "Setting Up Policing" later in this chapter.
Note: Avaya recommends that you do not set a port using policing as the source port or mirror port for a port mirror. When the switch limits the bandwidth of a port, packets are subject to random drop. If packets from a source port or mirror port are dropped, the mirror traffic may not match the source traffic.
This section contains the procedures:
|
|
|