topic Re: MSM430 in M and MSM Series

MSM430

Juggyv — Thu, 31 May 2012 07:15:58 GMT

Hello, I have a MSM430 that boots up, gets an IP address assigned to it and then it gets no further. The AP are all on the same subnet as the controller and I have reset the configuration but it does the same. I have tried other MSM430s and these behave fine, both new and from another implementation it is just this one. I can ping the IP it is assigned but I cannot browse to it via http or https or telnet and the HP console cable and a straight through and cisco console cable all do not gain me access to the console.

My question is am I wasting time here trying to fix this and should I just get it swapped out? I beleive it was working under a previous version 5.3 and after I upgraded to 5.7 this stopped.

Any help appreciated

Re: MSM430

Arimo — Thu, 31 May 2012 11:50:35 GMT

call support, that should do it.

Re: MSM430

Ck1000 — Thu, 31 May 2012 14:38:04 GMT

Hi,

You must downgrade your version of firmware.

5.7.0.2 has been deleted from HP Software Updates page... No communication from HP to this customers..

The support is useless in this case.

I don't understand why...

Re: MSM430

Arimo — Thu, 31 May 2012 15:31:16 GMT

Please note - can't access the web interface. To downgrade that's needs to be possible. There's a trick how the AP can be retrieved when HTTP isn't accessible, but only we at support can provide the necessary recovery firmware.

Re: MSM430

Juggyv — Fri, 01 Jun 2012 22:31:06 GMT

Thanks everyone for your comments. I have downgraded the controller firmware to see if an older one picks up this AP but to no avail. I have tried numerous console cables but get nothing on the screen, I think it has different pinouts but I cannot find a part number for this cable and I do not see why I should have to try to make one. The AP gets an IP address, I see this on the controller then nothing else. I cannot telnet to the AP, I cannot SSH or http or https to the controller. To top it off, I have raised a call with HP who are insisting I provide them with logs for an AP I cannot get access to! I have factory reset it away from the DHCP server also and tried it on 192.168.1.1 and it still does the same.

I know the controller works as other APs work, this one just does not want to play ball. Any help would be great, especially with the darn console cable so I can keep the powers at HP happy,

Re: MSM430

Juggyv — Sat, 02 Jun 2012 17:40:26 GMT

Just some more info, I made the console cable exactly how the manual said it should be made but to no avail. I tried an MSR30 cable and I got the below output but no more. I have tried this on working an non working APs which makes me think the MSM430 has to be either enabled or booted into.

The SSH to a new AP works fine as does the access of 192.168.1.1 from the web portal, the one with a problem doesnt even get this far. I hope is is a dud as its starting to drive me crazy.

setup_arch: bootmem

mpc85xx_rdb_setup_arch()

arch: exit

Re: MSM430

RudyW — Tue, 09 Apr 2013 18:21:01 GMT

I am having the same problemw with a new MSM710 controller and 5 MSM430 APs. Were you able to resolve your issue?

Re: MSM430

Peter_Debruyne — Wed, 10 Apr 2013 13:26:21 GMT

As discussed above, the AP firmware must be recovered in some kind of tftp mode.

This requires holding the reset of the AP a long time (fast blinking), which enables the tftp server on the AP. From a remote station, you can then upload the recovery image to the AP.

This is a special image however, which only HP support can give you.

So you have to log a call with support for this ...

Best regards,Peter

Re: MSM460

Sanjaypal — Fri, 28 Mar 2014 05:11:19 GMT

Hi, I Have received a new AP MSM460 from HP on place of faulty. I ,m facing two issue in this AP. 1st is after configuring. I restarted then its not ping or not going to default IP.

2nd: I have coneteced this AP by console then i,m getting a error while AP reboot.

Error is --------

setup_arch: bootmem
mpc85xx_rdb_setup_arch()
arch: exit

Pls suggest what i will do..................

Sanjay Pal

Re: MSM460

RudyW — Fri, 28 Mar 2014 14:04:26 GMT

Hello:

It is possible that you need to tell the AP to perform a factory default reset.

1. Use a pen or unfolded paperclip for the reset button.

2. Unplug the AP.

3. While pressing down the reset button plug in the AP.

4. Keep holding the reset button until the lights blink three times.

5. Release the button.

If the AP needs to download new firmware, it will take about 5 minutes. (Assuming the AP can find the controller via the DHCP or DNS methods.)

Re: MSM460

Arimo — Mon, 14 Apr 2014 14:56:39 GMT

This:

setup_arch: bootmem
mpc85xx_rdb_setup_arch()
arch: exit

... is NOT, repeat NOT an error message. It does not imply that the AP is failing. It just means that the console settings are incorrect. That does not really matter, as the console port isn't intended for a management interface in the first place. It's a troubleshooting tool in case you run into problems, only really useful for us geeks here.

For Juggyv's issue I double Peter - call support to get startup file. When you do it correctly it's only a few second job, and it usually does get a device back to its senses.

Sanjay, I'm sorry but I do not really follow you. Do you have a controlled environment? If yes, then you do not configure the AP at all. The only config to do is to provision the AP if you use L3 discovery.

My suggestion:

1. Connect the suspect AP to the same switch and VLAN where your controller connects to - the interface you use for discovering, that is.

2. Restore factory default settings as described by Rudy. I'd like to clarify the procedure a bit, though.

- Press Reset

- All LEDs will come ON for a couple of seconds

- All LEDs will go OFF for a couple of seconds

- All LEDs will start blinking slowly (~1/sec)

- On the third slow blink release Reset button.

The controller should pick up the AP.

To put the device in the TFTP mode you follow exactly the same process, except for last step. You keep the Reset button pressed until all LEDs start blinking faster (~2/sec). Then release Reset, and the AP will default to 192.168.1.1 and accept FW flash through TFTP. However as Peter said normal FW file won't work, but you will need to contact support.

Re: MSM460

Juggyv — Sun, 25 May 2014 13:38:04 GMT

Hi - this ended up being a dud - No firmware up/down etc or pinning it would work. HP swapped it and everything back to normal. A big waste of time. If you get an AP that displays similar traits and is not contactable in any way then I suggest getting HP To swap it.

Re: MSM460

ilker areels — Tue, 09 Aug 2016 11:12:17 GMT

reset doesn't work, i still see

setup_arch: bootmem
mpc85xx_rdb_setup_arch()
arch: exit

Re: MSM460

MinhChang — Thu, 29 Sep 2016 17:59:16 GMT

Hope someone can upload special firmware that they've mentioned above to here so that we can download.
Now I have some AP met this problem. The only way for me is contact HP support and replace new one.
But I still need way how to fix by myself

Re: MSM460

razu2444 — Sat, 09 Sep 2017 17:08:05 GMT

This worked a treat.

I don't thinks its 3 blinks though. I hit the reset button, blinks once after a few seconds. Thereafter I waited another 3 blinks and on the third I let go.

Thanks!

Re: MSM460

chain.young — Thu, 08 Jul 2021 04:14:07 GMT

I can access COM1 CLI with parameters - speed 115200 bps & no flow controll.