which firmware should i use to update MSM 760 to 5.5.3.0

[temuri426]

hello , 

i need to update firmware to 5.5.3.0, there are two options in this link  :  https://h10145.www1.hp.com/downloads/SoftwareReleases.aspx?ProductNumber=J9420A

thanks

[Fredrik Lönnman]

Use "5.5.3 - STEP ONE (MSM730/750/76x)" if you suspect you have boot sector corruption on your MSM430/460/466 running code < 5.5.2.0, otherwise use the regular 5.5.3.0 update.

[Mark Wibaux]

There are some customer support notices regarding this.

MSM430, MSM460, MSM466 802.11n Access Points - Software update required to avoid software corruption

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02845122

MSM430, 460, 466 Access Points - Two Step Installation Instructions for Prevention of Startup/Boot Problems

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03099741&jumpid=em_alerts_us-us_Dec11_xbu_all_all_1533098_100976_networking_critical_006_0

[temuri426]

hello, 

   i have done all of this configs , also i've  got the 5.7.0 firmware with little hotfix for boot loader. firslty i run this hotfix as they said and after that upgraded firmware to  5.7.0 version.  But promlem still exists , every second day users are losing conectivity.  after restarting devices several times AP's are working ok.

   there are some messages in logs , can ou please explain  what does this means: 

Dec 19 21:41:47 warning maestro_mas SG1383N2R6 Cannot take proper handling action on event from the system message bus, skipping (event='evLocalFirmwareRetrieval')

Dec 19 21:43:33 warning maestro_mas SG1383N2R6 Last message repeated 18 times

Dec 21 16:26:23 err kernel SG1383N2R6 e1000: eth1: e1000_clean_tx_irq: Detected Tx Unit Hang

Dec 21 16:26:40 err kernel SG1383N2R6 Last message repeated 4 times

Dec 21 16:26:40 warning statspoller SG1383N2R6 [44:1E:A1:C2:80:E2]: Transfer of SC statistics information failed: (28/0)

Dec 21 16:54:09 warning maestro_mas SG1383N2R6 Cannot take proper handling action on event from the system message bus, skipping (event='evLocalConfigChanged')

Dec 21 16:57:53 warning mapconf SG1383N2R6 SOAP configuration process <29215>: terminating upon maestro request.

Dec 21 16:59:35 warning maestro_mas SG1383N2R6 Cannot take proper handling action on event from the SC management message bus, skipping (event='evLocalTunnelDown')

Dec 21 17:00:54 err maestro_sla SG1383N2QV Failed to identify discovery port.

Dec 21 17:04:24 warning webs SG1383N2R6 Logout requested by login takeover

Dec 21 17:12:23 warning maestro_mas SG1383N2R6 Cannot take proper handling action on event from the system message bus, skipping (event='evLocalConfigChanged')

Dec 21 17:14:49 err mapconf SG1383N2R6 SOAP FAULT: SOAP-ENV:Client "Invalid configuration"

Dec 21 17:14:49 err mapconf SG1383N2R6 Detail: <error><errorcode>1009</errorcode><errorinfo>Configuration commit timeout.</errorinfo></error>

Dec 21 17:14:49 err mapconf SG1383N2R6 [98:4B:E1:E8:23:9E] CONFIG_full_vsc_security() failed, VSC <Agruni/2/2>.

Dec 21 17:14:58 warning maestro_mas SG1383N2R6 Cannot take proper handling action on event from the SC management message bus, skipping (event='evLocalTunnelDown')

Dec 21 17:16:30 warning monitord SG1383N2QV Watchdog Update after 32 seconds uptime=156855

Dec 21 17:16:30 err maestro_sla SG1383N2QV Failed to identify discovery port.

many thanks

[Evan_ISS]

---

@temuri426 wrote:

hello, 

   i have done all of this configs , also i've  got the 5.7.0 firmware with little hotfix for boot loader. firslty i run this hotfix as they said and after that upgraded firmware to  5.7.0 version.  But promlem still exists , every second day users are losing conectivity.  after restarting devices several times AP's are working ok.

---

We have had no end of problems with version 5.7.0 so this might be your issue.

The behaviour is like you describe only in our case it has taken a more sinister turn with the Web Interface (on the Controller) becoming unresponsive or configuration changes that show as applied on the Controller actually not being propagated to the APs. Some APs also become unresponsive randomly.

I have 3 Cases open regarding this with HP, one of the responses I got (and I quote) was the following: "For now we do not recommend customer for using 5.7 version, as we have seen some inconsistency with this release from many of our customers, 5.5.4.0 is the most stable and engineering preferred version".

When I challenged said support "consultant" as to why there is no announcement anywhere regarding this and as to the reason why the software is still available for download I got the usual HP "drone" nosnsense.

We had to downgrade to 5.5.4 as the WLAN was unusable most of the time. If the feedback I got is correct you might want to steer clear of 5.7.0 and downgrade to 5.5.4. Also 5.5.4 is a single update (not a two stage process like 5.5.3).

[temuri426]

Evan_ISS

thanks for answer,.

i 've already fixed this problem by changing the controllers.  we were troubleshooting with hp support, there were also another issues. we decided to replace controllers.  now they are working great.... :)