topic Re: E-MSM430 cannot be controlled by MSM760 in M and MSM Series

E-MSM430 cannot be controlled by MSM760

Edvar Lima — Tue, 17 May 2011 02:06:38 GMT

When I connect the E-MSM430 AP to the network it is discovered by the MSM760 controller on a PENDING state and showing the status WAITING FOR ACCEPTANCE. If I try to authorize the device I get the following message:

Could not take the appropriate web action for a device, please retry later

after that the device disappears for 20 seconds or so and then it's discovered again on a PENDING state.

I get this on the System Log of the MSM760:

Date Level Program Message May 17 11:56:46 err maestro_sc [98:4B:E1:E7:AB:C9] Error creating device configuration block for AP

May 17 11:56:46 crit maestro_sc Last message repeated 1 times

And this on the Event Log:

History of 98:4B:E1:E7:AB:C9 ?

Number of events in log: 30

Date & Time Category Operation Status

2011-05-17 11:57:38 Controlled AP Discovery Death

2011-05-17 11:57:28 Controlled AP Discovery Authorized

2011-05-17 11:57:28 Controlled AP Discovery Detected

2011-05-17 11:57:28 Controlled AP Discovery Undetected

2011-05-17 11:56:46 Controlled AP Discovery Death

2011-05-17 11:56:36 Controlled AP Discovery Authorized

2011-05-17 11:56:35 Controlled AP Discovery Detected

2011-05-17 11:56:35 Controlled AP Discovery Undetected

2011-05-17 11:56:02 Controlled AP Discovery Death

2011-05-17 11:55:53 Controlled AP Discovery Authorized

2011-05-17 11:55:53 Controlled AP Discovery Detected

2011-05-17 11:55:53 Controlled AP Discovery Undetected

2011-05-17 11:55:11 Controlled AP Discovery Death

2011-05-17 11:55:01 Controlled AP Discovery Authorized

2011-05-17 11:55:01 Controlled AP Discovery Detected

2011-05-17 11:55:01 Controlled AP Discovery Undetected

When I click on the AP name (S/N) when it shows as PENDING, I get this:

Could not display the selected AP, please retry later (entity='device',filter='98:4B:E1:E7:AB:C9')

The selected AP has not been created in the configuration file yet and so cannot be configured.

There are 20x MSM422 devices connected to the controller and they are working fine. I tried the above with 2 different E-MSM430 APs and I get the exact same result.

How can I get these things working with the MSM760 Controller? It worked flawlesly with the MSM422s.

Re: E-MSM430 cannot be controlled by MSM760

Fredrik Lönnman — Tue, 17 May 2011 05:43:09 GMT

What version are you running on the MSM760? You need at least 5.5.0 to support the MSM430.

Re: E-MSM430 cannot be controlled by MSM760

Edvar Lima — Tue, 17 May 2011 05:44:44 GMT

Thanks! That might be it... I'm running 5.3.1.0-01-7143

Re: E-MSM430 cannot be controlled by MSM760

Fredrik Lönnman — Tue, 17 May 2011 05:46:16 GMT

Ah no that wont work ;)

Re: E-MSM430 cannot be controlled by MSM760

Glen Willms — Wed, 12 Dec 2012 03:20:02 GMT

DId you ever resolve this issue? I'm encountering this issue and I'm looking for a fix.

I have two MSM760 Controllers Teamed and I think that the APs I'm experiencing issues with were on the slave controller.

Re: E-MSM430 cannot be controlled by MSM760

Edvar Lima — Wed, 12 Dec 2012 03:22:11 GMT

After the firmware upgrade everything worked fine.

Re: E-MSM430 cannot be controlled by MSM760

Glen Willms — Wed, 12 Dec 2012 03:36:19 GMT

I'm running 5.7.1.1. There is no new firmware for me to go to. :(

Re: E-MSM430 cannot be controlled by MSM760

Edvar Lima — Wed, 12 Dec 2012 03:40:14 GMT

It did work on 5.5.0 however I was only using 1 controller. No teaming with another one.

The problem was the firmware version on the new access points being newer than the controller old firmware.

Re: E-MSM430 cannot be controlled by MSM760

Arimo — Mon, 17 Dec 2012 16:26:04 GMT

Hi all

A little clarification to the answer above.

The problem isn't that the AP firmware is newer. The reason for failure on 5.3-firmware is that MSM430/460/466 APs require FW version 5.5.3. User who has purchased one of these new APs can freely download the required FW from HPN website for his controller.

If you encounter this issue with FW version 5.7.x, please contact support.