Giants are the frames that are greater than 1514 byte on a non-jumbo port.
Prior to the the 12.0(5.2)XU release, the switch would discard frames larger than 1514 bytes.
These counters are incremented in 10/100 ports when the port is configured for frames larger than 1514 bytes:
Input errors (The port LED may turn amber when a large packet is received or transmitted by the port.)
The bytes transmitted and bytes received do not reflect the actual number of bytes transmitted and received for large frames. Also, the broadcast count does not get incremented if the packet received or transmitted is a broadcast frame.
These counters are incremented in gigabit ports when the port is configured for frames larger than 1514 bytes:
Too large valid frames
This is also documented in Cisco bug ID CSCdr70758.
You can issue the vlanvlan-idmtu 2018 command to increase the maximum transmission unit (mtu) size upto 2018 bytes, so that the switch does not drop the large frames. The giant counter still increments.
I recently did an upgrade with AT&T from an older ADI/MIS 45M/45M DS3 circuit to a ADI/MIS 100M/100M circuit. Both of these are being provided over fiber run into my office. Both of these are serviced by my local LEC Frontier Communications. In the pr...
Hi all, we have configured dynamic vpn in a firewall which is behind a Cisco firewall. But remote clients are unable to connect to vpn configured in the firewall which isbehind the router where isp link terminates. Any help on how we ...
I’ve done the initial config with the express config utility. Now I can see the switch on my network but all login attempts are rejected no matter what combos I use. Seems to be working correctly, I just can’t manage it. Any help appreciated.
I am new to working with Cisco stuff and asking questions on here, so I hope I am asking this in proper form.I have a Linksys home router, connected to a Cisco 3825 router, connected to a Cisco 3560 switch.The router is working well and able to ping the i...