3Com Switch 8800 Advanced Software V5 Configuration Guide
Configuring QoS Policy 843
with the traffic statistics action, and the action of redirecting traffic to the CPU
cannot be used in conjunction with any other traffic actions.
■ The tunnel redirecting policy can be configured only in port view on D-type
modules.
■ Only D-type modules support the action of creating an outer VLAN tag and the
action of marking service provider network VLAN ID.
■ B-type modules cannot mark one CoS value separately. Four CoS values (dot1p,
dscp, drop-precedence, and local-precedence) must be marked together on
B-type modules.
■ On B-type modules, the priority marking action cannot be configured in
conjunction with the traffic policing action or the traffic statistics action.
■ On all modules, in the action of obtaining other precedence values through a
colored priority mapping table, the DSCP precedence and the 802.1p
precedence must be modified at the same time and cannot be modified
separately.
■ On all the modules, the 802.1p precedence marking action, the local
precedence marking action, and the drop precedence marking action cannot
be configured with the action of obtaining other precedence values through an
uncolored priority mapping table at the same time.
■ When configuring the action of redirecting traffic to an aggregation group and
applying the corresponding policy to a port, make sure that the action of
marking service provider network VLAN ID is configured at the same time. If
the corresponding policy is applied in VLAN view, the action of marking service
provider network VLAN ID is unnecessary to be configured at the same time.
■ When configuring the action of redirecting traffic to the next hop, make sure
that the type of ACL rules is consistent with that of the address the traffic is to
be redirected to. That is, you cannot redirect traffic to an IPv6 address using
IPv4 ACL rules or redirect traffic to an IPv4 address using IPv6 ACL rules.
■ The interface the traffic is to be redirected to must be an I/O Module interface.
■ The aggregation CAR action cannot be configured in conjunction with the
traffic statistics action.
■ With the action of redirecting traffic to the CPU configured, any of the other
traffic actions cannot be configured.
■ The action of marking service provider network VLAN ID (or the action of
creating an outer VLAN tag) cannot be configured with any traffic redirecting
action except the action of redirecting traffic to an aggregation group.
■ The action of marking service provider network VLAN ID cannot be configured
in conjunction with the action of creating an outer VLAN tag.
Configuration example
1 Network requirements
Configure a traffic behavior test and perform traffic policing with the CAR being
100 kbps.
2 Configuration procedure
# Enter system view.