450 Stops Responding to Ping Periodically, but Always Forwards Frames

[AbstractZero]

This is weird. Sometimes one of my 450 switches stops responding to ping. While it is unresponsive, I can still ping THROUGH the switch to equipment on the far side. My configuration is:

Me ---- 450a ---- 8600 ---- 450b ---- 450c ---- host

The problem is in 450b. Sometimes pings to it will timeout for a minute or more. During this time, the host at the end can still be reached! Further, even the 8600 switch cannot ping 450b when it is "down." But end-to-end connectivity never stalls.

WHAT IN THE WORLD IS THIS????

--Eric

 

[ydral]

hi,

It's maybe that !

Problems Resolved in This Release
Upgrading to previous code version (4.5.0 ) may cause a slow down in the management of the
units/stacks. This problem could be severe at times and management tools may report units/stacks as
being down. This issue is resolved in 4.5.1 release (Q00956327).

regards
.

 

[JohnE66]

What seems to have solved the ping issues for us is to make sure the bridging forwarding database timers are larger then the arp timeouts on the 8600s with the ISTs. This is required due to the fdb learning over the IST and how and when it arps to find the devices on the SMLTs.