Nexus 5548 "show interface" output: difference between "input" and "jumbo" packet counters?

noemi.berry · ‎02-02-2015

In "show interface" output on a Nexus, both "input packets" and "jumbo" counters are given, and they're different. What do they mean? Does the input packets counter mean ALL packets, including jumbo? What is the threshold between "input" and "jumbo"?

The interface is configured for MTU 9216, but displays MTU 1500. I'll guess that the "input" counter means frames sized 64 - 1500, and "jumbo" means 1501 - 9216, but there's no indication that 1500 is anything more than a display error.

Also, is the "input" counter inclusive of the "jumbo" count?

Nexus5548# show int eth1/30

Ethernet1/30 is up

Hardware: 1000/10000 Ethernet, address: 547f.eec7.b7e5 (bia 547f.eec7.b7e5)

MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec

Load-Interval #2: 5 minute (300 seconds)

input rate 507.95 Mbps, 55.41 Kpps; output rate 52.67 Mbps, 41.48 Kpps

RX

1211570942425 unicast packets 1493668 multicast packets 2181 broadcast packets

1211572438274 input packets 1297260294121170 bytes

606942154661 jumbo packets 0 storm suppression bytes

0 runts 0 giants 0 CRC 0 no buffer

0 input error 0 short frame 0 overrun 0 underrun 0 ignored

0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop

0 input with dribble 0 input discard

0 Rx pause

TX

963058213408 unicast packets 2496305921 multicast packets 165929356 broadcast packets

965720448685 output packets 195031410581408 bytes

34410403264 jumbo packets

18 output errors 0 collision 0 deferred 0 late collision

0 lost carrier 0 no carrier 0 babble 0 output discard

0 Tx pause

Nexus5548# show queuing int eth1/30

Ethernet1/30 queuing information:

TX Queuing

qos-group sched-type oper-bandwidth

0 WRR 100

RX Queuing

qos-group 0

q-size: 470080, HW MTU: 9216 (9216 configured)

drop-type: drop, xon: 0, xoff: 470080

Statistics:

Pkts received over the port : 390178800

Ucast pkts sent to the cross-bar : 390007564

Mcast pkts sent to the cross-bar : 171236

Ucast pkts received from the cross-bar : 849647150

Pkts sent to the port : 1045944237

Pkts discarded on ingress : 0

Per-priority-pause status : Rx (Inactive), Tx (Inactive)

Thanks!

noemi.berry · ‎02-03-2015

Found the answer.

Anatomy of RX packet counters on a Cisco Nexus 5548:

Nexus5548# show int eth1/29

RX

6387682660 unicast packets 1495485 multicast packets 164 broadcast packets

6389178309 input packets 589693485138 bytes

5146969 jumbo packets 0 storm suppression bytes

* "input" = unicast + multicast + broadcast (all non-jumbo)

* "jumbo" = frames sized 1519 bytes to the MTU bytes defined on the interface

* "jumbo" frames are counted separately from non-jumbo ("input")

* (unicast, multicast and broadcast "jumbo" frames appear to be rolled into the

one "jumbo" counter)

This can be seen another way with the 'count detail' command, correlated to "show int" output:

Nexus5548# show int eth1/29 count detailed

Ethernet1/29

Rx Packets: 6389178309 <-- input

Rx Unicast Packets: 6387682660 <-- unicast

Rx Multicast Packets: 1495485 <-- multicast

Rx Broadcast Packets: 164 <-- broadcast

Rx Jumbo Packets: 5146969 <-- jumbo

Rx Bytes: 589693485138

Rx Packets from 0 to 64 bytes: 1059418 <-- non-jumbo start

Rx Packets from 65 to 127 bytes: 6072007478 +

Rx Packets from 128 to 255 bytes: 11055520 +

Rx Packets from 256 to 511 bytes: 287107435 +

Rx Packets from 512 to 1023 bytes: 12801466 +

Rx Packets from 1024 to 1518 bytes: 23 <-- non-jumbo end

Rx Trunk Packets: 6387682823 <-- unicast + broadcast

fyi.