nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Class-map (qos): class-default (match-any)
set dscp 0
N7K-2#
QoS and Nexus 2000 Fabric Extenders
The Nexus 7000 supports Nexus 2000 series fabric extenders (FEX) to provide additional
options for server connectivity and Top of Rack (ToR) cabling architectures. The FEX is
considered a remote patch panel because it has no local switching capability, limited
buffering, and a minimal control plane. The FEX’s intelligence is derived from the upstream
or parent switch it is connected to. To provide this connectivity, there are two new types of
ports made available to the network administrator:
• FEX Host Interface (HIF): The ports on a FEX where servers and downstream
devices connect
• FEX Network Interface (NIF): The ports on a FEX used to connect to the parent
switch (uplinks)
From a QoS perspective, there are some restrictions for what types of policies can be
applied to a FEX configuration. Starting with the HIF
• Classification and marking are supported on HIFs through the QOS type policies.
• Queuing type policies are not supported on FEX HIF.
The NIF interfaces on a FEX have the following considerations:
• Queuing type policies can be applied in both ingress and egress directions.
• Queuing on FEX NIFs connected to an F2 module support two queues on ingress and
four queues on egress.
• Queuing on FEX NIFs connected to an M1 or M2 series module support eight queues
on both ingress and egress.
Example 10-16 illustrates the results of changing the queuing policy on a FEX HIF, whereas
Example 10-17 shows the application of a qos type policy to a FEX HIF.
Example 10-16. Changing the Queuing Policy on a FEX HIF
Click here to view code image
N7K-1-Agg1# config
Enter configuration commands, one per line. End with
CNTL/Z.
N7K-1-Agg1(config)#
N7K-1-Agg1(config)# int e101/1/1
N7K-1-Agg1(config-if)# service-policy type queuing in
default-in-policy
ERROR: Cannot apply queuing policy to