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

Export Configuration Settings

Usage:

Retrieving and Exporting the .ini File

Summary of the Procedure

An Administrator can retrieve the .ini file of a UPS Network Management Card (NMC) and export the file to another NMC or to multiple NMCs.

Configure an NMC to have the settings you want to export.

Retrieve the .ini file from that NMC.

Customize the file to change at least the TCP/IP settings.

Use a file transfer protocol supported by the NMC to transfer a copy to one or more other NMCs. For a transfer to multiple NMCs, use an FTP or SCP script or the .ini file utility.

Each receiving NMC uses the file to reconfigure the NMCs own settings and then deletes the file.

Contents of the .ini File

The config.ini file you retrieve from an NMC contains the following:

section headings and keywords, only supported for the device from which you retrieve the file: Section headings are category names enclosed in brackets. Keywords, under each section heading, are labels describing specific NMC settings. Each keyword is followed by an equals sign and a value, either the default or a configured value.
The Override keyword: With the default value, this keyword prevents the exporting of one or more keywords and the device-specific values. For example, in the [NetworkTCP/IP] section, the default value for Override (the MAC address of the NMC) blocks the exporting of values for the SystemIP, SubnetMask, DefaultGateway, and BootMode.

Detailed Procedures

Retrieving

To set up and retrieve, an .ini file to export:

If possible, use the interface of an NMC to configure the NMC with the settings to export. Directly editing the .ini file risks introducing errors.

To use FTP to retrieve config.ini, from the configured NMC:
1. Open a connection to the NMC, using the NMCs IP address:
  "ftp> open ip_address"
1. Log on using the Administrator user name and password.
1. Retrieve the config.ini file containing the NMCs settings:
  "ftp> get config.ini"

The file is written to the folder from which you launched FTP.

ReferenceTo retrieve configuration settings from multiple NMCs and export the settings to other NMCs, see Release Notes: ini File Utility, version 1.0.

Customizing

Customize the file before you export the file.

Use a text editor to customize the file.
- Section headings, keywords, and pre-defined values are not case-sensitive, but string values that you define are case-sensitive.
- Use adjacent quotation marks to indicate no value. For example, LinkURL1="" indicates that the URL is intentionally undefined.
- Enclose in quotation marks any values that contain leading or trailing spaces or are already enclosed in quotation marks.
- To export scheduled events, configure the values directly in the .ini file.
- To export a system time with the greatest accuracy, if the receiving NMCs can access a Network Time Protocol server, configure enabled for NTPEnable:
"NTPEnable=enabled"
Alternatively, reduce transmission time by exporting the [SystemDate/Time] section as a separate .ini file.
- To add comments, start each comment line with a semicolon.

Copy the customized file to another file name in the same folder:
- The file name can have up to 64 characters and must have the .ini suffix.
- Retain the original customized file for future use. The file that you retain is the only record of your comments.

Transferring the File to a Single NMC

To transfer the .ini file to another Network Management Card, do either of the following:

From the "Web interface" of the receiving NMC, select the "Administration" tab, "General" on the top menu bar, and "User Config File" on the left navigation menu. Enter the full path of the file, or use "Browse".

Use any file transfer protocol supported by Network Management Cards, FTP, FTP Client, SCP, or TFTP. The following example uses FTP:
1. From the folder containing the copy of the customized .ini file, use FTP to log in to the NMC to which you are exporting the .ini file:
  "ftp> open ip_address"
1. Export the copy of the customized .ini file to the root directory of the receiving NMC:
  "ftp> put filename.ini"

Exporting the File to Multiple NMCs

Use FTP or SCP, but write a script that incorporates and repeats the steps used for exporting the file to a single NMC.
Use a batch processing file and the .ini file utility.

ReferenceTo create the batch file and use the utility, see Release Notes: ini File Utility, version 1.0 .

The Upload Event and Error Messages

The Event and Event Error Messages

The following event occurs when the receiving Network Management Card completes using the .ini file to update the NMCs settings.

"Configuration file upload complete, with number valid values"

If a keyword, section name, or value is invalid, the upload by the receiving NMC succeeds, and additional event text states the error.

Show/hide table

Table 1
Event text	Description
Configuration file warning: Invalid keyword on line number. Configuration file warning: Invalid value on line number.	A line with an invalid keyword or value is ignored.
Configuration file warning: Invalid section on line number.	If a section name is invalid, all keyword/value pairs in that section are ignored.
Configuration file warning: Keyword found outside of a section on line number.	A keyword entered at the beginning of the file is ignored.
Configuration file warning: Configuration file exceeds maximum size.	If the file is too large, an incomplete upload occurs. Reduce the size of the file, or divide the file into two files, and try uploading again.

Messages in config.ini

A device associated with the NMC from which you download the config.ini file must be discovered successfully in order for the NMC configuration to be included. If the device (such as a UPS) is not present or is not discovered, the config.ini file contains a message under the appropriate section name, instead of keywords and values. For example:

"UPS not discovered"

"IEM not discovered"

If you did not intend to export the configuration of the device as part of the .ini file import, ignore these messages.

Errors Generated by Overridden Values

The Override keyword and the keyword value will generate error messages in the event log when the NMC blocks the exporting of values.

ReferenceRefer to the "Contents of the .ini file" section in this chapter for information about which values are overridden.

Because the overridden values are device-specific and not appropriate to export to other NMCs, ignore these error messages. To prevent these error messages, delete the lines that contain the Override keyword and the lines that contain the values that the lines override. Do not delete or change the line containing the section heading.