Show controllers ethernet output
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2012 07:40 AM - edited 03-07-2019 05:31 AM
I recently configured a network with a 4500 Sup7E and a 3560G with jumbo frame support. I am trying to confirm operation. On the 4500 this is straight forward using "sho int g0/nn count detail". A portion of that output lists tx and rx frame sizes:
Port InPkts 64 OutPkts 64 InPkts 65-127 OutPkts 65-127
Gi7/22 1631978 10708759 2220567 2087120
Port InPkts 128-255 OutPkts 128-255 InPkts 256-511 OutPkts 256-511
Gi7/22 4629 48616 118361 29112
Port InPkts 512-1023 OutPkts 512-1023
Gi7/22 136697 50803
Port InPkts 1024-1518 OutPkts 1024-1518 InPkts 1519-1548 OutPkts 1519-1548
Gi7/22 3075507 2083072 7 3
Port InPkts 1549-9216 OutPkts 1549-9216
Gi7/22 10165747 225
The 3560 doesn't support that command. The closest I can come to finding the number of jumbo packets is "show controllers ethernet" (example below). On the transmit side I assume that jumbo frames would be tallied in the "Too large frames" counter. The receive side is a little more ambiguous. There are 2 counters that seem to be duplicates, "Valid frames, too large" and "Valid oversize frames". In operation they are not. I am seeing the "Valid frames, too large" counter incrementing while the "Valid oversize frames" remains at zero. The command reference doesn't help disambiguate this too much:
Invalid frames, too large: The number of frames received that were larger than maximum allowed MTU size (including the FCS bits and excluding the frame header) and that have either an FCS error or an alignment error.
Valid frames, too large: The number of frames received on an interface that are larger than the maximum allowed frame size.
Valid oversize frames: The number of frames received on an interface that are larger than the maximum allowed frame size and have valid FCS values. The frame size includes the FCS value but does not include the VLAN tag.
What is "the maximum allowed frame size"? The standard 1500 bytes or the 9000 bytes I configured? Does anyone know how to monitor switching of jumbo frames? Is there another command?
Switch#show contr ether g0/17
Transmit GigabitEthernet0/17 Receive
684222060 Bytes 2135012435 Bytes
8847049 Unicast frames 7946185 Unicast frames
134833 Multicast frames 80 Multicast frames
3890 Broadcast frames 10 Broadcast frames
0 Too old frames 2134998162 Unicast bytes
0 Deferred frames 13633 Multicast bytes
0 MTU exceeded frames 640 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 3468166 Minimum size frames
0 8 collision frames 1140891 65 to 127 byte frames
0 9 collision frames 514 128 to 255 byte frames
0 10 collision frames 117680 256 to 511 byte frames
0 11 collision frames 88850 512 to 1023 byte frames
0 12 collision frames 2204544 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 0 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 925630 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
2015060 64 byte frames 0 Valid frames, too small
755379 127 byte frames
19709 255 byte frames 0 Too old frames
40955 511 byte frames 0 Valid oversize frames
257472 1023 byte frames 0 System FCS error frames
5897197 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames
-Jeff
- Labels:
-
Other Switching
