Alcatel 9000 Guía de usuario Pagina 548

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 702
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 547
Using Condition Groups in Policies Configuring QoS
page 26-42 OmniSwitch 6800/6850/9000 Network Configuration Guide June 2006
This command specifies that port 2/1 will be deleted from the techpubs port group at the next qos apply.
To delete a port group, use the no form of the policy port group command with the relevant port group
name. The port group must not be associated with any policy condition. For example:
-> no policy port group techpubs
The port group techpubs will be deleted at the next qos apply. If techpubs is associated with a policy
condition, an error message will display instead:
ERROR: techpubs is being used by condition 'cond4'
In this case, remove the port group from the condition first; then enter the no policy port group
command. For example:
-> policy condition cond4 no source port group
-> no policy port group techpubs
The policy condition command removes the port group from the policy condition. (See “Creating Policy
Conditions” on page 26-27 for more information about configuring policy conditions.) The port group will
be deleted at the next qos apply.
Port Groups and Maximum Bandwidth
Maximum bandwidth policies are applied to source (ingress) ports and/or flows. If a port group condition
is used in the policy, the bandwidth value specified is shared across all ports in the group.This also applies
to flows that involve more than one port. For example, if a policy specifies a maximum bandwidth value
of 10M for a port group containing 4 ports, the total bandwidth limit enforced is 10M for all 4 ports.
Note the following when configuring ingress maximum bandwidth policies:
On an OmniSwitch 6800 switch, bandwidth shaping is done on a per port basis and is not shared across
multiple ports.
If a policy condition applies to ports that are located on different slots, the maximum bandwidth limit
specified is multiplied by the number of slots involved. For example, if a rule is configured to apply a
maximum bandwidth limit of 10M to ports 1/1, 3/10, and 4/5, then the actual bandwidth limit enforced
for all three ports is 30M.
The maximum traffic received by a destination port is also dependant on how many slots are sending
traffic to the destination port. However, each slot is restricted to sending only 10k.
If a policy condition applies to ports that are all on the same slot, then the maximum bandwidth value
specified in the rule is not increased.
Ingress bandwidth limiting is done using a granularity of 64K bps.
The show active policy rule command displays the number of packets that were dropped because they
exceeded the ingress bandwidth limit applied by a maximum bandwidth policy.
Egress Bandwidth Shaping
To limit the bandwidth on egress ports, use the qos port maximum bandwidth command. For example,
-> qos port 1/1 maximum bandwidth 10k
Note the following when configuring a bandwidth limit for egress ports:
Egress bandwidth limiting is done using a granularity of 64K bps.
Vista de pagina 547
1 2 ... 543 544 545 546 547 548 549 550 551 552 553 ... 701 702

Comentarios a estos manuales

Sin comentarios