NMC2 AP9537 Firmware Failure (Application transfer failed)

Anonymous user · ‎2021-06-30

Good morning all,

I have tried updating the firmware on my NMC2 AP9537 card. I cannot load the application (webgui) after failed installation.

I can login through telnet to see the about information, please see below:

Schneider Electric Network Management Card AOS v6.5.6

-------------------------------------------------------------------------------

Name : apc90A24C Date : 06/05/2018

Contact : Unknown Time : 15:39:57

Location : Unknown User : Super User

Up Time : 0 Days 0 Hours 13 Minutes Stat : P+ N4+ N6+ A-

Type ? for command listing

Use tcpip command for IP address(-i), subnet(-s), and gateway(-g)

apc>about

E000: Success

Hardware Factory

---------------

Model Number: AP9537SUM

Serial Number: 5A1530T09234

Hardware Revision: 05

Manufacture Date: 07/25/2015

MAC Address: 00 C0 B7 90 A2 4C

Management Uptime: 0 Days 0 Hours 13 Minutes

Application Module

---------------

Invalid Module Header!

APC OS(AOS)

---------------

Name: aos

Version: v6.5.6

Date: Mar 30 2018

Time: 16:51:08

APC Boot Monitor

---------------

Name: bootmon

Version: v1.0.8

Date: Apr 8 2014

Time: 10:59:40

apc>

This is the error log that I get when I try to do the firmware update. I've successfully completed this task on 3 other ones onsite so far so maybe this one is defective?

Starting Upgrade 06/05/18 11:18:43

-----------------

[06/05/18 11:18:43] 10.10.12.156: Pinging (via ICMP) device

[06/05/18 11:18:43] 10.10.12.156: Device connection passed

[06/05/18 11:18:44] 10.10.12.156: Testing FTP Log-in

[06/05/18 11:18:48] 10.10.12.156: FTP Log-in passed

[06/05/18 11:18:49] 10.10.12.156: Saving data file

[06/05/18 11:18:52] 10.10.12.156: AOS Prior to firmware transfer: Network Management Card AOS v6.2.0

[06/05/18 11:18:52] 10.10.12.156: APP Prior to firmware transfer: Smart-UPS & Matrix-UPS APP v6.2.0

[06/05/18 11:18:52] 10.10.12.156: Saving event & configuration files

[06/05/18 11:19:21] 10.10.12.156: Transferring firmware file (1/3): Boot Monitor

[06/05/18 11:19:28] 10.10.12.156: Boot Monitor transfer successful

[06/05/18 11:19:30] 10.10.12.156: Restarting network interface

[06/05/18 11:20:12] 10.10.12.156: Device connection passed

[06/05/18 11:20:14] 10.10.12.156: Testing FTP Log-in

[06/05/18 11:20:15] 10.10.12.156: FTP Log-in passed

[06/05/18 11:20:16] 10.10.12.156: Transferring firmware file (2/3): OS

[06/05/18 11:28:21] 10.10.12.156: OS transfer successful

[06/05/18 11:28:23] 10.10.12.156: Restarting network interface

[06/05/18 11:28:43] 10.10.12.156: Pinging (via ICMP) device

[06/05/18 11:29:42] 10.10.12.156: Device connection passed

[06/05/18 11:29:43] 10.10.12.156: Testing FTP Log-in

[06/05/18 11:29:44] 10.10.12.156: FTP Log-in successful

[06/05/18 11:29:45] 10.10.12.156: Transferring firmware file (3/3): application

[06/05/18 11:35:45] 10.10.12.156: ERROR --> Application transfer failed

That is all the information I can provide, any help is greatly appreciated.

Thank you,
Justin

BillP · ‎2021-06-30

Can you log in via Telnet and try a reboot on the management interface (won't affect the UPS output), then re-try pushing the sumx.bin file like Matt suggested?

If that doesn't work, just in case, I'd try to download the .exe and re-try with a new copy of the sumx .bin file. I see it said invalid module header through Telnet when you shared the output originally so if you try a different version of the file and it still works, you could also try from a different PC just to be sure there is no corruption to the file that is preventing the NMC from thinking its a valid file with a valid header.

We could also go back and see if it accepts a different version of firmware, like the original version you started with too, which we can provide. Depending on the results, then we can device what direction to go in or suggestion to make.

See Answer In Context

B-DoubleE_apc · ‎2021-06-30

Hi Justin,

If the application fails to load once (due to possibly a connection interruption or something outside of your control), I've had good luck in fixing it by manually applying a firmware update over FTP, instead of re-running the wizard. This link should take you to the FTP section of our knowledge base article, follow the steps for NMC2 and let us know if it works. I'd recommend doing everything, transferring the Bootmon file and AOS first, then the APP file last.

Anonymous user · ‎2021-06-30

Hi Matt,

Thank you for this great article. I have followed the steps, and could not upload the sumx bin.

Log report:

C:\Users\Justin\Downloads\APC>ftp 10.10.12.156

Connected to 10.10.12.156.

220 AP9537SUM Network Management Card AOS v6.5.6 FTP server ready.

550 NOOP requested action not taken.

User (10.10.12.156:(none)): apc

331 User name okay, need password.

Password:

230 User logged in, proceed.

ftp> bin

200 TYPE Command okay.

ftp> hash

Hash mark printing On ftp: (2048 bytes/hash mark) .

ftp> put apc_hw05_sumx_656.bin

200 PORT Command okay.

150 File status okay; about to open data connection.

##############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################

Connection closed by remote host.

ftp> bye

I did the apc_hw05_bootmon_108.bin file first, the apc_hw05_aos_656.bin second and apc_hw05_sumx_656.bin last. When I login via my browser I only see the aos bin displayed under the main index.

I appreciate the continued assistance regarding this.

Thanks,
Justin

BillP · ‎2021-06-30

Can you log in via Telnet and try a reboot on the management interface (won't affect the UPS output), then re-try pushing the sumx.bin file like Matt suggested?

If that doesn't work, just in case, I'd try to download the .exe and re-try with a new copy of the sumx .bin file. I see it said invalid module header through Telnet when you shared the output originally so if you try a different version of the file and it still works, you could also try from a different PC just to be sure there is no corruption to the file that is preventing the NMC from thinking its a valid file with a valid header.

We could also go back and see if it accepts a different version of firmware, like the original version you started with too, which we can provide. Depending on the results, then we can device what direction to go in or suggestion to make.