Cisco Nexus 7000 Series Configuration Manual page 40

Nx-os quality of service configuration guide
Hide thumbs Also See for Nexus 7000 Series:
Table of Contents

Advertisement

Attaching and Detaching a QoS Policy Action
Note
• You must enable the tunnel feature by entering the feature tunnel command and configure the tunnel
before you attach policies.
• On Fabric Extender (FEX) interfaces, you can configure only the type qos policies. However, you cannot
configure the type qos policies that refer to classes that match with the access control lists (ACLs) that
are configured for the FEX external interfaces.
• The type queuing policies are currently not supported on FEX interfaces.
The system-defined type queuing class maps (see
page
15) are attached to each interface unless you specifically attach a different class map.
Note
The device restricts QoS policies to one per interface per direction (ingress or egress) for each of the policy
types qos and queuing.
Policies that are defined at multiple interfaces have the following restrictions:
• A QoS policy attached to the physical port takes effect when the port is not a member of a port channel.
• A QoS policy attached to a port channel takes effect even when policies are attached to member ports.
• A QoS policy attached to a VLAN is applied to all ports in that VLAN that do not have other policies
specifically applied.
• One ingress policy type queuing is supported for each Layer 2 port- and Layer 2 port-channel interface
in both the ingress and egress direction. Egress type qos policies are not allowed on Layer 2 port or Layer
2 port-channel interfaces.
• One ingress and one egress QoS policy are supported for each Layer 3 and Layer 3 port-channel interface.
• One ingress and one egress QoS policy are supported for each VLAN.
• One ingress and one egress queuing policy are supported for each Layer 2 port-, Layer 2 port-channel,
Layer 3 port-, and Layer 3 port-channel interface.
• When a VLAN or port channel, or both, touches multiple forwarding engines, all policies that enforce a
rate are enforced per forwarding engine.
• For example, if you configure a policer on a specific VLAN that limits the rate for the VLAN to 100
Mbps and if you configure one switch port in the VLAN on one module and another switch port in the
VLAN on another module, each forwarding engine can enforce the 100-Mbps rate. In this case, you
could actually have up to 200 Mbps in the VLAN that you configured to limit the rate to 100 Mbps.
Note
Default queuing policies are active, unless you configure and apply another policy. For the default queuing
policies, see
The interface where a QoS policy is applied is summarized in the table below. Each row represents the interface
levels. The entry descriptions are as follows:
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
24
Table 8: System-Defined Queuing Policy Maps, on page
Table 6: System-Defined Type queuing Class Maps, on
18.
Using Modular QoS CLI

Advertisement

Table of Contents
loading

Table of Contents