Wireless Access

Hi All,

We have recently purchased a HP MSM422 Access Point (Colubris MAP625).

It was working fine in our test environment, so we have moved it to production. We use 802.1x with dynamic VLAN assignments.

We see the MSM422 reboot itself at different times, and we are working on trying to find a solution.

I have been taking a syslog of all events and we have found the following information when the system resets: (This may be hard to read)

2009-04-22 09:34:43 Local1.Debug 172.16.70.1 br0: received tcn bpdu on port 3(eth0)
2009-04-22 09:34:43 Local1.Debug 172.16.70.1 br0: topology change detected, propagating
2009-04-22 09:34:45 Local1.Info 172.16.70.1 monitord: Reset Status - cause=5
2009-04-22 09:34:45 Local1.Info 172.16.70.1 monitord: Free memory left before reset 79224KB+13304KB
2009-04-22 09:34:45 Local1.Info 172.16.70.1 monitord: Last panic info: Msg:dpr:Kill ISR: **bleep**=c00330e4 lr=c003303c sp=c0178870 trap=300 msr=1032 dar=4 Panic Call Backtrace: C01A0000 C013F128 C013F4D8 C0140A04 C002176C C001D6A0 C001D508 C001D0C4 C0005E54 C0004DC0 C0006568 C0006584 C018F430 000035F0
2009-04-22 09:34:47 Local1.Info 172.16.70.1 br0: received tcn bpdu on port 3(eth0)
2009-04-22 09:34:47 Local1.Debug 172.16.70.1 br0: topology change detected, propagating
2009-04-22 09:34:49 Local1.Info 172.16.70.1 br0: received tcn bpdu on port 3(eth0)
2009-04-22 09:34:49 Local1.Debug 172.16.70.1 br0: topology change detected, propagating
2009-04-22 09:34:52 Local1.Info 172.16.70.1 br0: received tcn bpdu on port 3(eth0)
2009-04-22 09:34:52 Local1.Debug 172.16.70.1 br0: topology change detected, propagating
2009-04-22 09:34:55 Local1.Info 172.16.70.1 br0: received tcn bpdu on port 3(eth0)
2009-04-22 09:34:55 Local1.Debug 172.16.70.1 br0: topology change detected, propagating
2009-04-22 09:34:56 Local1.Info 172.16.70.1 monitord: (eth0) Link is now synced up to state UP
2009-04-22 09:35:00 Local1.Info 172.16.70.1 monitord: Unit information:(5.2.4.0-01-6771) (MSM422) (ID=28)

The firmware is 5.2.4.0, i have read somewhere that there is a 5.2.6.0 out there, but we have been unable to locate it on the HP website. I am unsure if this will solve the issue.

Has anybody else come across this problem?

We use a HP PoE, plugged into a 1000mb port.

I am basically trying to find if anybody knows what a reset cause=5 actually means. I cannot find an error code document anywhere.

Any assitance would be greatly appreciated.

Regards,

Adam.

 

P.S. This thread has been moved from Communications, Wireless (Legacy ITRC forum) to MSM Series. -HP Forum Moderator

I am having the same issue, did you ever find a solution to this problem?

Hi Chris,

At this stage we have not seen a fix worth noting. We have been experimenting with a different firmware (5.3.2.14-01-7349), but this has not proved to help in any way as we are still seeing random reboots.

We now have 2 in one location and 6 in another location, all within fairly close range of each other. One of the 422's in the first location reboots quite frequently (every few days), yet the other one has stayed up for 17 or more days. Out of the other area where there are 6 422's, 5 stay up and 1 reboots frequently.

I am still finding it hard to pin down what causes it.

Getting help from HP on this issue has proved difficult.

We are close to purchasing a controller, it will be interesting to see if this changes the situation.

The log file does not tell us where or why it reboots, so it has been hard to diagnose.

Please let me know if you ever find a solution also.

Hello Adam,

You can find the information of the cause code's from the AskProCurve database, just search for the words "cause code" and it should pull up the document for you (also bunch of other nice documents in there).

(for your convinience here is a quick link to that page: https://my.procurve.com/knowledgebase/knowledgemanagement.aspx?wp=showarticle&id=622)

So in short cause code 5:

- "restart requested by firmware upon a fatal system error"

Right, so had a quick look at your log above and unfortunately it doesn't reveal the root cause of the crash other than detecting topology changes that are happening at the time of the issue.

I would recon collecting up following data (before and after the crash) from your device and contact support:

GUI=

- Filtered log:
Tools > System log > Filtered log > button â save logâ

- Unfiltered log:
Tools > System log > Unfiltered log > button â save logâ

- Sysinfo.bin:
Maintenance > System > Save system information ( there is a button called â downloadâ ¦â )

- topology map of your network.

- And "show tech all" from your switch where the AP is connected:

in CLI: #copy command 'show tech all' tftp <TFTP server=""> <FILENAME> [*ENTER*]

Best regards,

Jouni Kosonen
ProCurve Networking by HP.
EMEA</FILENAME></TFTP>