Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

2610 Crash

DrewL
Occasional Advisor

2610 Crash

Shortly after enabling LACP and connecting the links and then testing them two out of three of my 2610's randomly crashed. The 3 2610's are connected to a 2810 that is running firmware from 2006. WHen HP finally fixes their site i'll download the latest firmware because i noticed that the crash was fixed for the 2810's but didn't see anything about the 2610's. When I logged into the switch i had this in the log:

TLB Miss: Virtual Addr=0x00000000 IP=0x8
Task ID=0x85cd7dd0 fp:0x00000000 sp:0x8

I dont want to put this switches into a live environment if there going to be randomly crashing. They have not done it in a few days but I would rather be safe then sorry.

Thanks!
5 REPLIES
DrewL
Occasional Advisor

Re: 2610 Crash

It happened again after enabling snmpv3 and having Procurve manager discover the switch...

TLB Miss: Virtual Addr=0x00000000 IP=0x800a97f8 Task='mSnmpCtrl'
Task ID=0x85cc8050 fp:0x00000000 sp:0x85cc7db0 ra:0x800a94c8 sr:0x1000fc01

Anyone know anything about this.

Switch has the latest IOS.
DrewL
Occasional Advisor

Re: 2610 Crash

Had to disable snmpv3 as all switches would crash with it enabled....
DrewL
Occasional Advisor

Re: 2610 Crash

More info if needed

System went down: 05/09/08 12:03:17
Saved crash information:
TLB Miss: Virtual Addr=0x00000000 IP=0x800a97f8 Task='mSnmpCtrl'
Task ID=0x85ccd0d0 fp:0x00000000 sp:0x85ccce30 ra:0x800a94c8 sr:0x1000fc01

Re: 2610 Crash

i'm not sure if i can help you but i have a couple of these new switches and I feel like the software is nowhere near ready yet. Make sure you are running R.11.07 and not R.11.04 which is incorrectly shown as the latest release on some parts of the Procurve site, this has fixes for a lot of things.

DrewL
Occasional Advisor

Re: 2610 Crash

Thanks for the reply Martin. I am running the latest IOS R.11.07 and would agree that the software seems "incomplete" if you will. Those crashes that i was experiencing would happen after enabling SNMPv3. If you have a couple 2610's that are not live you should give snmpv3 a try. Snmpv1/2 seems to be fine but as an admin the security of those versions are less than desirable. ;)