Normal or Anomaly?? 450 Issue?

[OmegaVTX]

Here is a brief layout...

me > 450 > 8600 > 1200 > 450 > client
100> 100 > gig > gig >100 > 100 <---fiber speed

I can ping the 8600 and get <1ms and I can ping the 1200 and client from my location and get 1ms.

If I ping either 450 I get outragous ping times ranging from 20-170ms!!!

Also If I tracert the 450's I see the increased ping time... So I am confused why I am not seeing aggragate reflected in the ping to the client? or 8600 for that matter or how to correct this... if it is a problem.

Oh 1 more quickie... why would I get an error when trying to change 100mb fiber link on a 1200 to auto (for testing) and get the error that AutoNegotiation Is Not Supported?

Thanks!
Jason

 

[JeroeNortel]

Hi Jason,

The higer ping reply sounds familiar to me. We also experiencing the same except with other types of switches. However the ping replies from devices behind the switch are faster than the replies from the switch itself. It seems this is a certain way of behaviour/programming the switch is replying ping requests. Maybe it has something to do with the management of the switch because replies from devices/cliënts behind the switch are pretty good (<10ms)!
As long as this doesn't has effect on the running services (production environment) we can live with this.
I can't tell you what's the reason of the error when changing the speed settings, probably this is a kind of built in option which is not supported yet in the software release you're using. I bet on it this would be in one of the following releases!

Regards,
JeroeNortel

 

[jimbopalmer]

On the 450s, ping time was pretty good through the 3.x versions of software, but the 4.x code really taxes the CPU. Rather than make the switch perform badly for end users, the programmers sapped the management responsiveness instead. (works fast, reports slow)

I tried to remain child-like, all I acheived was childish.

 

[dane775]

What jimbo said...*nodding*

 

[OmegaVTX]

Thanks guys! Makes me feel better... some ;-p