upgrade failed

[Anonymous user]

I have a UPS with an old AP9617 card. It was old enough that it needed the two step upgrade. Using the wizard I just downloaded to a windows laptop, it did the first upgrade phase and then choked on the second round.

Here's the log file, redacted for my IP address:

Checking network connection ...  Checking version information ...

*************** Next **************

Before Upgrading the NMC the AOS is: apc_hw02_aos_102.bin

* Detected early version, two AOS upgrades required

Attempting to log in to 128.xxx.xxx.xxx ... 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 128.xxx.xxx.xxx ... 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 128.xxx.xxx.xxxSystem reboot failed. Aborting this Upgrade.

Not all Network Management Cards were upgraded successfully:

  128.xxx.xxx.xxx: The Management Card at this address is not responsive.

Encountered 1 failures during upgrade.

================

Now I can ping the device, and when I connect with a browser it tells me

Error: The application was not able to load. You are attempting to access an APC device. There was a problem loading the application. Please login to the device via telnet for more details.

That appears in the browser window.  Both telnet and ssh are refusing my connection attempt. I am probably going to start a hunt for one of those magic RS-232 cables to go plug into the thing. I am looking for advice on what might be the right next step. Thanks

[BillP]

I would FTP to the card and see if that works. If it does, do the ls command and tell me what files you see there in the file listing. Also, if the FTP prompt pops up, let me know what it says for the AOS version. For example:

C:\Users\>ftp 192.168.1.45

Connected to 192.168.1.45.

220 AP9617 Network Management Card AOS v3.7.3 FTP server ready.

User (192.168.1.45):(none)):

We can probably just try a manual FTP upgrade as the next step with the bin files and the order will depend on what files are currently on the card. Instructions are here -> How do I upgrade the firmware on an APC Network Management Card? | FAQs | Schneider Electric US

[Anonymous user]

Yes, FTP is working. Directory listing:

ftp> ls

227 Entering Passive Mode (128,114,130,214,200,117).

125 Data connection already open; transfer starting.

--wx-wx-wx  1 apc      apc      1572864 Feb 02  2010 apc_hw02_aos_373.bin

drwxrwxrwx  1 apc      apc            0 Feb 02  2010 sec/

226 Closing data connection.

=========

I find the instructions confusing. But FTP access seems hopeful. Let ne know what to do next.

[BillP · Accepted solution]

Ok, go ahead and connect to your card and put sumx372.bin file (which the exact file name is a little different) on there (assuming its a Smart UPS you're trying to put the AP9617 in).

Looks like you have the AOS loaded already so that is why we will go with the application file.

So, connect in and do:

> bin (for binary transfer mode which is required)

> hash

> put or drag and drop it from your desktop if on Windows after you type put and it will paste the file name for you.

Then press enter, then type bye to disconnect. Hopefully with what I said, maybe the instructions are a little easier to understand. You'll only need to update the application instead of the AOS for what I am asking.

[Anonymous user]

Thank you.  Only about 99 more to upgrade. . .

[Anonymous user]

I have now upgraded six 9617s with the windows PC program. In all cases, the PC program fails and leaves the management module with the new OS program running but the application (sumx) not loaded.  In all cases, the manual FTP rescue works.

What I found is that the windows application says it will wait 2 minutes for the mgmt module to reboot.  It then commences looking for it on the net. It tries to contact it for about 30 seconds and then the program gives up.  The time required for this reboot to complete and the mgmt module to resume answering pings is about 3.5 minutes.  So by the time the first reboot is finished, the Windows upgrade application has packed it in and gone home. I am running the application on XP Service Pack 2. It is not that the mgmt card does not reboot, it is that it doesn't do it as fast as the application thinks it should.

[BillP]

Yes, I've seen that before but not every time. The timing seems to be off a little bit. It probably depends on the version and size of the files loaded and which application which contributes to the timing. Glad it is all set though.