Cisco WS-X6248-RJ-45 - Catalyst 6000 Expansion Module Manual de usuario Pagina 32

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 42
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 31
Cisco Systems, Inc.
All contents are Copyright © 1992–2002 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.
Page 32 of 42
In CatOS, the policing parameters, such as rate, burst, and related actions, are defined first in a policer statement. A
QoS ACL is configured which identifies both the traffic to-be-policed and references the appropriate policer. Then,
the QoS ACL needs to be committed and applied to a port or VLAN, as with normal ACL configuration.
In Cisco IOS Software, the ACL is defined first. The policing parameters are defined in one of two configurations
modes. This depends on the type of policer being implemented and the specific differences are discussed in the
following sections.
Aggregate Policers
There are two forms of aggregate policers that can be defined in the Cisco IOS Software: Shared Aggregate Policers
and Per-Interface Aggregate Policers.
Shared Aggregate Policers (sometimes referred to as Named Aggregate Policers) are applied to a group of interfaces/
VLANs and provide the function of policing traffic across all interfaces and/or classes cumulatively. As an example,
use the shared aggregate policer when a 100-Mbps rate limit should be applied to four different interfaces combined.
These policers are supported in both CatOS and Cisco IOS Software. The following table shows a configuration
comparison of the two implementations.
Note:
In CatOS, the rate is measured in Kbps and the burst is specified in Kb. In the Cisco IOS Software, the rate
is measured in bps and the burst is specified in bytes. These differences are true for all policer types.
Per-Interface Aggregate Policers are applied to an interface and traffic class, individually. These policies can be
applied to multiple interfaces, but the policer polices each interface separately. As an example, use the Per Interface
Aggregate policer when a 100-Mbps rate limit should be applied individually to four different interfaces. These
policers are only supported in Cisco IOS Software
4
.
CatOS Cisco IOS Software
set qos policer aggregate ag1 rate
1000000 burst 32 drop
set qos acl ip ag_acl trust-dscp
aggregate ag1 any
set qos acl map ag_acl 3/5
access-list 101 permit ip any any
mls qos aggregate-policer ag1 10000000
4625 conform-action transmit exceed-
action drop
policy-map limit-named
class class-ag1 access-group 101
police aggregate ag1
interface fastethernet 3/5
service-policy input limit-named
4. Similar functionality can be achieved in CatOS, but it requires configuring a unique policer for each interface in question. The Cisco IOS
implementation of per-interface policers requires that the policer is defined only once, but applied separately.
Vista de pagina 31
1 2 ... 27 28 29 30 31 32 33 34 35 36 37 ... 41 42

Comentarios a estos manuales

Sin comentarios