I have a very bizarre issue. TFTP transfers are very slow when I have my server hooked up to my Cisco 3750. Transfers were working fine a few weeks ago. However, if I hook my server up to a netgear 5 port unmanaged switch, and then the netgear to the 3750 tftp transfers work fine.
TFTP Dead Slow: Server -> Cisco 3750 <- Client [Both server and client are connected to the 3750]
TFTP Normal: Server -> Netgear -> Cisco 3750 <- Client [Client is hooked up to 3750, where as the server is connected to the netgear, and the netgear is connected to the 3750]
All other services on the server (ssh, nfs, etc...) work as expected and I don't have any network holds ups.
Also, I introduced another tftp server on the network and that is connected directly into the switch stack. I don't have any problems with using that tftp server.
I will post my switch configuration a little later, but I just have trunk links configured and 3 vlans setup with vtp.
I am very confused as to why a netgear 5 port unmanaged switch is fixing my problems.
Didi you check the interface stats on the 3750 when the server was connected to it. It might be dute to speed/ duplex mismatch on the interface when the server was connected. Sometime hardware problems create these kind of issues.It could also be due to bad patch cable connecting the server and the switch. Did you give a check to all that?
Both the server and the switch port autonegotiated full duplex at 1000Mb/s. I also tried manually setting full-duplex + 1000Mbps on both the switch and the server with no luck. I'm pretty sure the cable is ok, since I am using the same cable to connect the server to the netgear switch. Also, other services such scp, nfs, etc... work fine at normal speeds.
I did try another patch cable for kicks without any improvments.
You are seeing CRC errors on the interface. This means that there is some sort of hardware incompatibility issue or the devices are not negotiating speed/duplex/other link parameters properly. As a first step, I would change the cable to a known good cable (If there are any patch panels along the path, bypass them). The next step would be to check the server side to see if there are any parameters that are hard coded (in addition to speed/duplex). Sometimes there are driver issues with certain hardware that result in these kind of issues. Please check the latest driver availability for the Ethernet card.
I've tried about 3-4 different cables all with the errors and the orginal cable I was using, I knew work. That cable hasn't been moved since I setup the server. In addition, if I set the speed on the switchport to 100Mbps all is good. As soon as I bump it up to 1000Mbps we have problems.
Edit: I am using linux so of course there aren't newer nic modules so to speak and I checked and I haven't had a kernel upgrade since I've installed debian on this box.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...