Wireless Access

Hi everyone,

I had issue in a MSM460. I though It was in failure state since I cound ping in the address 192.168.1..1 but could not log in the web console and was not detected buy a MSM760 Controller in my bussiness place.

Searching in this forum I found a post about the Access Point could be in controlled mode by Unified HP Solution and needs to be software converted by MSM HP Wlan Solution and in thus mode operate managed by a MSM Controller or in Autonomus mode.

I converted the MSM 460 with the software V6.5.0.1-HP560-B19720.cim.starup and works fine for me, in the controlled mode and in the autonomus one.

To load the software you have to put the MSM460 in tftp mode. For that put a paper clip in the reset botton, press it until the leds blink twice por second and release the paper clip.

Pay attention is about the tftp file transfer it should be done in the binary mode in the tftp client. In Windows Enviroment the comand line is tftp -i 192.168.1.1 V6.5.0.1-HP560-B19720.cim.starup image

It takes about 30 seconds to load the file and receive the message por sucessfull file transfer, the MSM460 will install the software and reboot. After that you need to reset the access to factory defaults to log in the web console. The factory defaults the AP is in controlled mode. 

I have ran into a similar problem with a MSM466 and it took me quite a while to navigate and find the correct information to correect the problem.

A couple of things, the firmware mentioned throughout several of these posts will work on the following APs: HP 425, 517, 560 as well as the MSM 430, 460, 466 and 466-R, which is per the v6.5.0.1 zip file release notes.

Next, if anyone receives a TFTP error, such as "Error on server: / Boot <code> (<date>) / Image validation failed: bad magic", this error is due to not using the "xxx.cim.startup" file or possibly it is corrupt.

One last hurdle was the AP started in controller mode ready to be provisioned for a controller.  Even though one should be able to switch it to autonomous mode within the AP menu, it would not.  Allowed it to connect to a MSM controller which updated(sync'd) the firmware and then selected the AP within the Defult Group.  Next, select menu Maintenance / System and "Switch to Autonomous Mode" which finally worked.

Attached to this message is the MSM software which contains the 6.5.0.1 code as well as the ".startup" file for when needing to rebuild an MSM-AP from the ground up.   Hope this helps as it has certainly provided a reliable fix for our scenario.

I have ran into a similar problem with a MSM466 and it took me quite a while to navigate and find the correct information to correect the problem.

A couple of things, the firmware mentioned throughout several of these posts will work on the following APs: HP 425, 517, 560 as well as the MSM 430, 460, 466 and 466-R, which is per the v6.5.0.1 zip file release notes.

Next, if anyone receives a TFTP error, such as "Error on server: / Boot <code> (<date>) / Image validation failed: bad magic", this error is due to not using the "xxx.cim.startup" file or possibly it is corrupt.

One last hurdle was the AP started in controller mode ready to be provisioned for a controller.  Even though one should be able to switch it to autonomous mode within the AP menu, it would not.  Allowed it to connect to a MSM controller which updated(sync'd) the firmware and then selected the AP within the Defult Group.  Next, select menu Maintenance / System and "Switch to Autonomous Mode" which finally worked.

Attached to this message is the MSM software which contains the 6.5.0.1 code as well as the ".startup" file for when needing to rebuild an MSM-AP from the ground up.   Hope this helps as it has certainly provided a reliable fix for our scenario.

I have ran into a similar problem with a MSM466 and it took me quite a while to navigate and find the correct information to correect the problem.

A couple of things, the firmware mentioned throughout several of these posts will work on the following APs: HP 425, 517, 560 as well as the MSM 430, 460, 466 and 466-R, which is per the v6.5.0.1 zip file release notes.

Next, if anyone receives a TFTP error, such as "Error on server: / Boot <code> (<date>) / Image validation failed: bad magic", this error is due to not using the "xxx.cim.startup" file or possibly it is corrupt.

One last hurdle was the AP started in controller mode ready to be provisioned for a controller.  Even though one should be able to switch it to autonomous mode within the AP menu, it would not.  Allowed it to connect to a MSM controller which updated(sync'd) the firmware and then selected the AP within the Defult Group.  Next, select menu Maintenance / System and "Switch to Autonomous Mode" which finally worked.

Attached is another important document detailing the TFTP process to reset an MSM-AP using the ".startup" file.

"Instructions for Converting an Access Point from Unified-Controlled to Using MSM Software

Attached to this message is the MSM software which contains the 6.5.0.1 code as well as the ".startup" file for when needing to rebuild an MSM-AP from the ground up.   Hope this helps as it has certainly provided a reliable fix for our scenario.

I have ran into a similar problem with a MSM466 and it took me quite a while to navigate and find the correct information to correect the problem.

A couple of things, the firmware mentioned throughout several of these posts will work on the following APs: HP 425, 517, 560 as well as the MSM 430, 460, 466 and 466-R, which is per the v6.5.0.1 zip file release notes.

Next, if anyone receives a TFTP error, such as "Error on server: / Boot <code> (<date>) / Image validation failed: bad magic", this error is due to not using the "xxx.cim.startup" file or possibly it is corrupt.

One last hurdle was the AP started in controller mode ready to be provisioned for a controller.  Even though one should be able to switch it to autonomous mode within the AP menu, it would not.  Allowed it to connect to a MSM controller which updated(sync'd) the firmware and then selected the AP within the Defult Group.  Next, select menu Maintenance / System and "Switch to Autonomous Mode" which finally worked.

You're a hero. Its infuriating the hoops you have to go through to find this stuff through these forums. Migrations and run arounds and non helpful answers from "staff" 

You are appreciated 

Attached is another important document detailing the TFTP process to reset an MSM-AP using the ".startup" file.

"Instructions for Converting an Access Point from Unified-Controlled to Using MSM Software

Attached to this message is the MSM software which contains the 6.5.0.1 code as well as the ".startup" file for when needing to rebuild an MSM-AP from the ground up.   Hope this helps as it has certainly provided a reliable fix for our scenario.

I have ran into a similar problem with a MSM466 and it took me quite a while to navigate and find the correct information to correect the problem.

A couple of things, the firmware mentioned throughout several of these posts will work on the following APs: HP 425, 517, 560 as well as the MSM 430, 460, 466 and 466-R, which is per the v6.5.0.1 zip file release notes.

Next, if anyone receives a TFTP error, such as "Error on server: / Boot <code> (<date>) / Image validation failed: bad magic", this error is due to not using the "xxx.cim.startup" file or possibly it is corrupt.

One last hurdle was the AP started in controller mode ready to be provisioned for a controller.  Even though one should be able to switch it to autonomous mode within the AP menu, it would not.  Allowed it to connect to a MSM controller which updated(sync'd) the firmware and then selected the AP within the Defult Group.  Next, select menu Maintenance / System and "Switch to Autonomous Mode" which finally worked.

Hello all,

Can somebody share MSM460 .cim.startup file?

I cannot find it in the portal.

Thank you in advance

You're a hero. Its infuriating the hoops you have to go through to find this stuff through these forums. Migrations and run arounds and non helpful answers from "staff" 

You are appreciated 

Attached is another important document detailing the TFTP process to reset an MSM-AP using the ".startup" file.

"Instructions for Converting an Access Point from Unified-Controlled to Using MSM Software

Attached to this message is the MSM software which contains the 6.5.0.1 code as well as the ".startup" file for when needing to rebuild an MSM-AP from the ground up.   Hope this helps as it has certainly provided a reliable fix for our scenario.

I have ran into a similar problem with a MSM466 and it took me quite a while to navigate and find the correct information to correect the problem.

A couple of things, the firmware mentioned throughout several of these posts will work on the following APs: HP 425, 517, 560 as well as the MSM 430, 460, 466 and 466-R, which is per the v6.5.0.1 zip file release notes.

Next, if anyone receives a TFTP error, such as "Error on server: / Boot <code> (<date>) / Image validation failed: bad magic", this error is due to not using the "xxx.cim.startup" file or possibly it is corrupt.

One last hurdle was the AP started in controller mode ready to be provisioned for a controller.  Even though one should be able to switch it to autonomous mode within the AP menu, it would not.  Allowed it to connect to a MSM controller which updated(sync'd) the firmware and then selected the AP within the Defult Group.  Next, select menu Maintenance / System and "Switch to Autonomous Mode" which finally worked.