AP9630 Application Error

[Anonymous user]

I have a AP9630 that is no longer reporting back information properly. We did a switch replacement to the site but after the network came back online the card will no longer connect properly. The UPS unit was not powered down and all it did was move network ports. No firmware upgrade was done on this card in the past two years or during the switch replacement.

We are able to ping the card and get a web page to resolve for it but it states: 
"The Application was not able to load"
"You are attempting to access a Schnieder Device. There was a problem loading the application. Please login to the device via telnet for more details"

When we telnet to the device we can pull up about & system but it is showing Bootmon, AOS & App with a Invalid Module Header! 

Any idea what may be our next steps to get this card working again properly?

For command help: command ?
apc>about
E000: Success
Hardware Factory
---------------
Model Number: AP9630
Serial Number: ZA12140XXXX
Hardware Revision: 05
Hardware Factory
---------------
Model Number: AP9630
Serial Number: ZA12140XXXX
Hardware Revision: 05
Schneider Electric Network Management Card AOS v6.6.4
(c) Copyright 2018 All Rights Reserved
-------------------------------------------------------------------------------
Name : apc61ADE4 Date : 10/04/2014
Contact : Unknown Time : 03:09:44
Name: aos
Version: v6.6.4
Date: Aug 3 2018
Time: 16:00:07

APC Boot Monitor
---------------
Name: bootmon
Version: v1.0.8
Date: Apr 8 2014
Time: 10:59:40

apc>system
E000: Success
Host Name Sync: Disabled
Name: apc61ADE4
Contact: Unknown
Location: Unknown
Message:
DateTime: 10/04/2014:03:17:16
User: apc
Up Time: 0 Days 0 Hours 31 Minutes
Stat: P+ N4+ N6+ A-
Bootmon: Invalid Module Header!
AOS: Invalid Module Header!
App: Invalid Module Header!

[LarryK]

In the past where a prior firmware upgrade has gone off the rails, I was given the following information:

Reformat the device, which wipes flash memory and any remaining configurations entirely, including your current TCP/IP settings.

There are two different ways of doing this:

1) Press and hold the NMC's pinhole reset button for 20 to 30 seconds, ensuring the NMC's status LED is flashing green during this time. When it changes to amber or orange, release the reset button to let the format function complete and for the NMC to complete its reboot process.

or

2) Issue the "format" command via the command line via telnet, SSH, or local console. Issue the "reboot" command to complete the process.

Find the DHCP provided IP address of the NMC, access the web UI, reconfigure your settings, and then make sure you install the latest firmware upgrade (currently 7.0.4).

Hope that helps.

[Anonymous user · Accepted solution]

That info helped a bit. What i ended up doing was reloading the firmware via FTP per this thread. 

https://community.se.com/t5/Datacenter-Forum/Receiving-quot-The-Application-Was-Not-Able-to-Load-quo...