Management Functions of 2520-8-PoE stop working

[John H. Miller]

I have a 2520-8-PoE switch that every now and then, for no apparent reason seems to go off-line from a management perspective. I cannot ping it, I cannot browse to it, nor can I telnet to it. The console port works, but I can't ping anything on my network. There is nothing in the log fles to indicate an issue, only that it can't get to the SNTP server. Once I reboot the switch everything is fine again. The software is current (S.14.30) and the configuration is fairly simple. I can post it if someone believes it necessary.

Has anyone else seen this issue or is it a known problem with this switch.

Thanks - John

[YenLin]

Hi we've got different situation in our environment. When we was using S.14.30. all of them have very bad latency problem. It can reaches more then 2000 ms. So, I suggest you upgrade to S.15.09.0012. I think you will satisfy this version.

Additionally, It's better to set it back to default then paste after your upgrade IOS.

Good luck!

[paulgear]

Hi John,

I don't work on the site any more, but i had a 2520 that was exhibiting very similar erratic behaviour, in a network where there were plenty of other 2510, 2600, 2800, 4100, and 5400 series switches working just fine.  Upgrading firmware as suggested above is probably the first step i would take, but if the behaviour continues i would suggest logging a fault with HP.

[Michael_Breuer]

Hello John,

this is a know problem. See this thread for details: http://h30499.www3.hp.com/t5/ProCurve-ProVision-Based/2520-8-PoE-Spanning-Tree-Problem/m-p/5570975

Upgrading to 15.x would be the best way.

Cheers,

Michael

[Emil_G]

Hi,

For me the description looks pretty much like this bug

Version S.14.40 Status: Released and fully supported, and posted on the web. The following problem was resolved in software version S.14.40.

■ Management (CR_0000127197) - The 2520-8-PoE Switch (J9137A) might become inaccessible to in-band management until the switch is rebooted. Note that the switch's console port is unaffected and works properly during the problem time. This improves the original Management fix (CR_0000115882) in S.14.38.

[John H. Miller]

Thanks to everyone that replied. I should have checked to see if there was an update, but I relied on the automatic notification to let me know. Best check my subscriptions. :-)

Anyway, based on your comments, I am sure an upgrade will address the issue. Again, Thanks to all - John

EDIT - OK, my bad. I already had S.15.9.07 downloaded, just had not deployed. It seems to be the latest one available. I saw .012 referenced above, but it does not seem to be generally available yet. I an sure 7 will be fine and should address my situation.

[Emil_G]

Hi,

If you want to use the S.15.09.x branch then you have to contact the support and request at least S.15.09.0013. This release contains the fix 0000127197. As far as I know S.15.09.0015 is the latest available at the moment.

I know this is a little bit confusing but the S.15.x is not the follow up release of S.14.x. Both branches are running parallely. The S.15.x has a different feature set.

This particular issue was detected with both branches. Fixed with S.14.40 and S.15.09.0013.

[John H. Miller]

Good to know. Since I just upgraded to S.15.09.00007 is it safe to go back to S.14.40 (which IS generally available) as opposed to contacting support to get S.15.09.0013?

Thanks - John