APC SUA1500i with Network Card 9617 : Failed Firmware Upgrade : Rescue Need

[Anonymous user]

Hello All,

I am using SmartUPS SUA1500i with network management card 9617 (i dont know the part number).

The network interface was working fine and had an old firmware (~year 2000, ver 3.0.x). It was configured as fixed IP address as there was no option in firmware to set DHCP for getting IP address.

I followed the instruction at:

[How do I upgrade the firmware on an APC Web/SNMP Management Card or Network Management Card?|http://jpaa-en.apc.com/cgi-bin/jpaa_en.cfg/php/enduser/std_adp.php?p_faqid=768&p_created=1010390400&...]

to try to upgrade the firmware to the latest one.

I downloaded the following file

[Network Management Card v3.7.2 complete firmware executable for Smart UPS with AP9617/8/9|ftp://restrict:Kop$74!@ftp.apc.com/restricted/hardware/nmcard/firmware/sumx/372/apc_hw02_aos373_sumx...]

I did not define any email recipients upon any event/log in the web UI.

After unzipping the file a command prompt asked for the IP address of the UPS, after that the firmware update procedure started, all the steps went fine , however at the last step of rebooting and accessing the network card it did fail. The result.txt file is mentioned as below "

*Using AOS file : AOS = apc_hw02_aos_373.bin*
*Using Application file: APP = apc_hw02_sumx_372.bin*
*Checking network connection ... Checking version information ...*

.....................Next........................

*Before Upgrading the NMC the AOS is: apc_hw02_aos_105.bin*
** Detected early version, two AOS upgrades required*
*Attempting to log in to 192.168.10.3 Log in sucessful*
*Loading OS, please wait OK*
*Please wait (2 minutes ) for system restart OK*
*Attempting connection to verify restart OK*
*Attempting to log in to 192.168.10.3 Log in sucessful*
*Loading OS, please wait OK*
*Please wait (2 minutes ) for system restart OK*
*Attempting connection to verify restart Failed to ping at 192.168.10.3System reboot failed. Aborting this Upgrade.*


*Not all Network Management Cards were upgraded successfully:*
*192.168.10.3: The Management Card at this address is not responsive.*

*Encountered 1 failures during upgrade.*

After that the network card main web interface is not accessible. When i point the web browser to the network card IP address I get the following screen

!http://img23.imageshack.us/img23/4025/apcups.jpg!

As mentioned on the screen I try to enter the network card via telnet (user/pass apc,apc) and I can only see the console with 4 options to go to configuration/network settings/device manager/system. But upon selecting any of these selection, none of the options give me any further screen and hence not working in the telnet console as well.

So how can I now rescue/restore the web interface to the network card with the updated firmware, and were all the settings and options saved in the earlier firmware would be restored or are they gone and have to be set again.

Thanks for help and support.


-----------EDIT---------------

I think i found out the problem

the results.txt files says

*Before Upgrading the NMC the AOS is: apc_hw02_aos_105.bin*
*Detected early version, two AOS upgrades required*

It means it first needs to be updated to *AOS 2.0.2*

There is a file named *"apc_hw02_aos_202.bin"* in the unzipped folder.

So now when I have already tried updating directly to ver 3.x.x without updating it first to ver 2.x.x , how can I restore back to first install ver 2.x.x.

Do i have to try to use the FTP rescue procedure, if it fails then can what is the method of going via the serial cable if needed.

Thanks again.

Message was edited by: AquaFire

[voidstar_apc]

>
So how can I now rescue/restore the web interface to the network card with the updated firmware ...
>

Failing to complete the update has no adverse effect on your settings.

It looks like it managed to load in the 3.xx AOS, but didn't load in the app. Run the firmware update utility again and you'll be all set to go. You can also FTP in the app directly. The firmware update utility just automates the whole process of FTPing in the update files.

[Anonymous user · Accepted solution]

Done.

First flashed ver 202 via FTP, waited for a while, then used the normal executable file to load OS and application 3.7.2.

UPS working now.

Thanks.