06-27-2018 07:57 AM - edited 03-08-2019 03:30 PM
I am seeing the counter of jumbo packets going up on 2 ports connected to a server when neither the server or switch is configured for jumbo. The switch is a Nexus 3500 series. Anyone know why?
06-27-2018 12:12 PM
06-27-2018 12:47 PM
Yes as the ports are trunks allowing a couple vlans.
06-27-2018 01:58 PM
I think that behavior is only on the Nexus series. Can you post the output from one of the interfaces?
I think that is harmless anyway.
HTH
06-27-2018 02:10 PM
Ok here is sh interface. I was having an issue before as to why I was concerned. Jumbo seen on same port on Switch b that the same server is dual homed to.
Sw_A# sh interface et1/8
Ethernet1/8 is up
Dedicated Interface
Belongs to Po2
Hardware: 100/1000/10000 Ethernet, address: 00d7.8faa.5caf (bia 00d7.8faa.5caf)
Description: NetApp_Node1_eth1
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 32/255
Encapsulation ARPA
Port mode is trunk
full-duplex, 1000 Mb/s, media type is 1G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 06:38:17
Last clearing of "show interface" counters 06:38:34
1 interface resets
Load-Interval #1: 30 seconds
30 seconds input rate 129695864 bits/sec, 10680 packets/sec
30 seconds output rate 1997016 bits/sec, 3452 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 128.87 Mbps, 10.56 Kpps; output rate 1.88 Mbps, 3.17 Kpps
RX
248606923 unicast packets 802 multicast packets 0 broadcast packets
248602363 input packets 376930697408 bytes
242881368 jumbo packets 0 storm suppression packets
0 runts 0 giants 7 CRC 0 no buffer
7 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
75586218 unicast packets 0 multicast packets 13 broadcast packets
75586231 output packets 5495379870 bytes
15257 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause
06-27-2018 06:19 PM
Can you post the output of "sh que int et1/8"?
HTH
06-27-2018 06:37 PM
It won't take that command closest thing is sh int queuing-drop history.
Here is a counters if this helps or let me know what else.
Ethernet1/8
Rx Packets: 413373546
Rx Unicast Packets: 413377564
Rx Multicast Packets: 1340
Rx Jumbo Packets: 403751721
Rx Bytes: 626606672174
Rx Packets from 0 to 64 bytes: 339852
Rx Packets from 65 to 127 bytes: 25403
Rx Packets from 128 to 255 bytes: 106689
Rx Packets from 256 to 511 bytes: 362119
Rx Packets from 512 to 1023 bytes: 239275
Rx Packets from 1024 to 1518 bytes: 8553854
Rx Trunk Packets: 413377564
Tx Packets: 123161431
Tx Unicast Packets: 123161410
Tx Broadcast Packets: 21
Tx Jumbo Packets: 25191
Tx Bytes: 8986472051
Tx Packets from 0 to 64 bytes: 114723381
Tx Packets from 65 to 127 bytes: 90750
Tx Packets from 128 to 255 bytes: 8138634
Tx Packets from 256 to 511 bytes: 78381
Tx Packets from 512 to 1023 bytes: 46767
Tx Packets from 1024 to 1518 bytes: 58327
Tx Trunk Packets: 123144455
Input CRC Errors: 9
Input Errors: 9
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide