1. Physical connections. Make 100% certain that you're full duplex on both switchports that you're connected to.
2. Check for errors on those interfaces.
3. Check processor utilization at the time that you're getting high latency. The switch could be overloaded.
Are they in the same subnet? I'm assuming so since you said same L2 vlan, but if you have 1 server's primary as 192.168.1.1 and that same server's secondary as 192.168.2.1 and you're pinging another server that's at 192.168.2.2, then the 1st server will source that address as 192.168.1.1 and may need to cross a l3 vlan. If that's the case, you may want to also trace to see if the path is truly taking what you think it should be.
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...