Network Management Card and Network Management Card with Environmental Monitoring for the UPSB505 Uninterruptible Power Supply Caterpillar

File Transfer

Usage:

How to Upgrade Firmware

Benefits of Upgrading Firmware

When you upgrade the firmware on the UPS Network Management Card (NMC):

You obtain the latest bug fixes and performance improvements.
New features become available for immediate use.

Keeping the firmware versions consistent across your network ensures that all NMCs support the same features in the same manner.

Firmware Files (Network Management Card)

A firmware version consists of three modules: An AOS module, an application module, and a boot monitor (bootmon) module. Each module contains one or more Cyclical Redundancy Checks (CRCs) to protect the modules data from corruption during transfer.

The AOS, application, and boot monitor module files used with the NMC share the same basic format:

"cat_hardware-version_type_firmware-version.bin"

cat : Indicates the context.
hardware-version : hw0x identifies the version of the hardware on which you can use this binary file.
type : Identifies whether the file is the AOS, module, the application module, or the boot monitor module for the NMC.
version : The version number of the file.
bin : Indicates that this file is a binary file.

Obtain the Latest Firmware Version

Note: In a manual upgrade, you can skip the bootmon installation if there are no updates. With the NMC2 Firmware Upgrade Utility, any bootmon update is automatic.

NMC2 Firmware Upgrade Utility for Microsoft Windows Systems

The NMC2 Firmware Upgrade Utility automates the transferring of the firmware modules on any supported Windows operating system. Find the latest firmware release for your product and the automated utility included in the product. Never use a utility designated for one product to upgrade the firmware of another product.

Manual Upgrades, Primarily for LINUX Systems

If no computer on your network is running a Microsoft Windows operating system, upgrade the firmware of your NMCs by using the separate AOS and application firmware modules.

Note: In manual upgrades, load the boot monitor module first, then the operating system module, and finally, the application module.

To extract the firmware files:

Run the NMC2 Firmware Upgrade Utility.

At the prompts, click "Next>", and then specify the directory location to which the files will be extracted.

When the "Extraction Complete" message displays, close the dialog box.

Firmware File Transfer Methods

To upgrade the firmware of an NMC, use one of these methods:

From a networked computer running a Microsoft Windows operating system, use the NMC2 Firmware Upgrade Utility.

Note: The utility only works with an NMC that has an IPv4 address.

From a networked computer on any supported operating system, use FTP or SCP to transfer the individual AOS and application firmware modules.
For a Network Management Card that is not on your network, use XMODEM through a serial connection to transfer the individual firmware modules from your computer to the NMC.

Show/hide table

NOTICE

When you transfer individual firmware modules, transfer the AOS module to the NMC before you transfer the application module.

Use FTP or SCP to Upgrade One Network Management Card

FTP

To use FTP, to upgrade one NMC over the network:

The NMC must be connected to the network, and the system IP, subnet mask, and default gateway must be configured.
The FTP server must be enabled at the NMC.
The firmware files must be extracted from the NMC2 Firmware Upgrade Utility.

To transfer the files:

At a computer on the network, open a command prompt window. Go to the directory that contains the firmware files, and list the files:
"C:\>cd cat"
"C:\cat>dir"
For the listed files, xxx represents the firmware version number:
- "cat_hw05_aos_xxx.bin"
- "cat_hw05_application_xxx.bin"

Open an FTP client session:
"C:\cat>ftp"

Type open and the IP address of the NMC, and press "ENTER". If the "port" setting for the FTP Server has changed from the default of "21", use the non-default value in the FTP command.
- For Windows FTP clients, separate a non-default port number from the IP address by a space. For example:
"ftp> open 150.250.6.10 21000"
- Some FTP clients require a colon instead before the port number.

Log on as Administrator : "cat" is the default user name and password.

Upgrade the AOS. In the example, xxx is the firmware version number :
"ftp> bin"
"ftp> put cat_hw05_aos_xxx.bin"

When FTP confirms the transfer, type "quit" to close the session.

After 20 seconds, repeat step 2 through step 6. In step 5, use the application module file name.

SCP

To use Secure CoPy (SCP), to upgrade firmware for the NMC:

Identify and locate the firmware modules described in the preceding instructions for FTP.

Use an SCP command line to transfer the AOS firmware module to the NMC. The following example uses xxx to represent the version number of the AOS module:
"scp cat_hw05_aos_xxx.bin cat@158.205.6.185:cat_hw05_aos_xxx.bin"

Use a similar SCP command line, with the name of the application module, to transfer the application firmware module to the NMC.

How to Upgrade Multiple Network Management Cards

NMC2 Firmware Upgrade Utility

Use this utility for multiple firmware updates in IPv4 if you have Windows. The utility records all upgrade steps in a log as a good reference to validate the upgrade.

Export Configuration Settings

You can create batch files and use a utility to retrieve configuration settings from multiple NMCs and export the settings to other NMCs.

ReferenceSee Release Notes: ini File Utility, version 1.0.

Use FTP or SCP to Upgrade Multiple NMCs

To upgrade multiple NMCs using an FTP client or using SCP, write a script which automatically performs the procedure.

Using the NMC2 Firmware Upgrade Utility for Multiple Upgrades

After downloading from the website, double click on the exe file to run the utility (which ONLY works with IPv4) and follow these steps to upgrade your NMC firmware:

Type in an IP address, a user name, and a password, and choose the "Ping" button if you need to verify an IP address.

Choose the "Device List" button to open the iplist.txt file. This choice should list any device IP, user name, and password, for example,
"SystemIP=192.168.0.1"
"SystemUserName=cat"
"SystemPassword=cat"
The new utility works fine with any existing iplist.txt file that you have used with the old version of the utility.

Select the "Upgrade From Device List" check box to use the iplist.txt file. Clear this check box to upgrade the firmware using the IP, user name, and password you typed on the dialog box.

Choose the "Upgrade Now" button to start the firmware version update.

Choose "View Log" to verify any upgrade.

Use XMODEM to Upgrade One NMC

To use XMODEM to upgrade one NMC that is not on the network, extract the firmware files from the NMC2 Firmware Upgrade Utility.

To transfer the files:

Select a serial port at the local computer and disable any service that uses the port.

Connect the provided serial configuration cable to the selected port and to the serial port at the NMC.

Run a terminal program such as HyperTerminal, and configure the selected port for 57600 bps, eight data bits, no parity, one stop bit, and no flow control.

Press the "Reset" button on the NMC, then immediately press the "Enter" key twice, or until the Boot Monitor prompt displays: "BM>"

Type "XMODEM", then press "ENTER".

From the terminal programs menu, select XMODEM, then select the binary AOS firmware file to transfer using XMODEM. After the XMODEM transfer is complete, the Boot Monitor prompt returns.

To install the application module, repeat step 5 and step 6. In step 6, use the application module file name.

Type "reset" or press the "Reset" button to restart the NMC.

ReferenceFor information about the format used for firmware modules, refer to the "Firmware files (Network Management Card)" section of this chapter

Verifying Upgrades and Updates

Verify the Success or Failure of the Transfer

To verify whether the firmware upgrades succeeded, use the "xferStatus" command in the "command line interface" to view the last transfer result, or use an SNMP GET to the "mfiletransferStatusLastTransferResult" OID.

Last Transfer Result Codes

Show/hide table

Table 1
Code	Description
Successful	The file transfer was successful.
Result not available	There are no recorded file transfers.
Failure unknown	The last file transfer failed for an unknown reason.
Server inaccessible	The TFTP or FTP server could not be found on the network.
Server access denied	The TFTP or FTP server denied access.
File not found	The TFTP or FTP server could not locate the requested file.
File type unknown	The file was downloaded but the contents were not recognized.
File corrupt	The file was downloaded but at least one Cyclical Redundancy Check (CRC) failed.

Verify the Version Numbers of Installed Firmware

Use the "Web interface" to verify the versions of the upgraded firmware modules by selecting the "Administration" tab, "General" on the top menu bar, and "About" on the left navigation menu, or use an SNMP GET to the MIB II "sysDescr" OID. In the "command line interface", use the about command.

Adding and Changing Language Packs

The Network Management Card language pack files contain the information required to display the user interface in languages other than English. Each language pack contains up to five languages. The Language drop-down box will have up to five languages to choose from when you log on.

The user interface has nine languages available in all: French, Italian, German, Spanish, Brazilian Portuguese, Russian, Korean, Japanese, and Simplified Chinese.

The language pack files are available on the UPS Network Management Card 2 product download area. The language pack files all have an ".lpk" extension and the file naming convention is:

"<app name>_<app version>_<language codes>.1pk"

You might want to change the user interface language to one that is not currently available on your user interface. Download the language pack from the website, and follow these steps:

Connect to the NMC using FTP.

Transfer the required language pack to the Management. For example, type:
"put <full path/language pack name>.1pk"

When the file finishes the transfer, log off FTP and the NMC will reboot.

When the reboot is complete, the new language pack is ready for use.

Note: Any current language pack on the card is deleted before the new pack is transferred. Any problem with the pack transfer leaves the NMC with no language pack. Only English is available in that circumstance. If only English is available, try reloading the new language pack.