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

Example 10-7. MTU Differences in a System with No-Drop Class
Click here to view code image
N7K-2# show int e3/1
Ethernet3/1 is down (Administratively down)
admin state is down, Dedicated Interface
Hardware: 1000/10000 Ethernet, address: e8b7.48cc.08bc
(bia e8b7.48cc.08bc)
MTU bytes (CoS values): MTU 1500(0-2,4-7)
bytes MTU 2112(3) bytes
BW 10000000 Kbit, DLY 10 usec, reliability 255/255,
txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
N7K-2# show int e4/1
Ethernet4/1 is down (Administratively down)
admin state is down, Dedicated Interface
Hardware: 10000 Ethernet, address: 0024.98eb.ff41 (bia
f866.f2ac.5aa8)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
N7K-2#
Queuing Policies
The Nexus 7000 supports a variety of modules that can be grouped into two families:
• M-Series modules, which have a hybrid ingress and egress buffering model
• F-Series modules, which have a primarily ingress buffering model
These different models impact where traffic is queued in the network, which is apparent in
the examples. The queuing capability of different modules within the same family can be
different based on the hardware implementation. The queuing capability displays as a string
of numbers and letters that can be confusing. A good example is 1P7Q4T. This is shorthand
for One Priority(1P) queue, Seven Queues(7Q) with Four Thresholds(4T) per queue.
Table 10-1 shows the queuing structure for the available modules in the Nexus 7000.
Table 10-1. Module Queuing Structures and Sizes