Apc Inrow Acrc301s User Guide
Apc Inrow Acrc301s User Guide
990-5567-001
Publication Date: January 2014
Schneider Electric IT Corporation Legal Disclaimer
The information presented in this manual is not warranted by the Schneider Electric IT Corporation to be authoritative,
error free, or complete. This publication is not meant to be a substitute for a detailed operational and site specific
development plan. Therefore, Schneider Electric IT Corporation assumes no liability for damages, violations of codes,
improper installation, system failures, or any other problems that could arise based on the use of this Publication.
The information contained in this Publication is provided as is and has been prepared solely for the purpose of evaluating
data center design and construction. This Publication has been compiled in good faith by Schneider Electric IT
Corporation. However, no representation is made or warranty given, either express or implied, as to the completeness or
accuracy of the information this Publication contains.
IN NO EVENT SHALL SCHNEIDER ELECTRIC IT CORPORATION, OR ANY PARENT, AFFILIATE OR
SUBSIDIARY COMPANY OF SCHNEIDER ELECTRIC IT CORPORATION OR THEIR RESPECTIVE
OFFICERS, DIRECTORS, OR EMPLOYEES BE LIABLE FOR ANY DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE, SPECIAL, OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT
LIMITATION, DAMAGES FOR LOSS OF BUSINESS, CONTRACT, REVENUE, DATA, INFORMATION, OR
BUSINESS INTERRUPTION) RESULTING FROM, ARISING OUT, OR IN CONNECTION WITH THE USE
OF, OR INABILITY TO USE THIS PUBLICATION OR THE CONTENT, EVEN IF SCHNEIDER ELECTRIC
IT CORPORATION HAS BEEN EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SCHNEIDER ELECTRIC IT CORPORATION RESERVES THE RIGHT TO MAKE CHANGES OR UPDATES
WITH RESPECT TO OR IN THE CONTENT OF THE PUBLICATION OR THE FORMAT THEREOF AT
ANY TIME WITHOUT NOTICE.
Copyright, intellectual, and all other proprietary rights in the content (including but not limited to software, audio, video,
text, and photographs) rests with Schneider Electric It Corporation or its licensors. All rights in the content not expressly
granted herein are reserved. No rights of any kind are licensed or assigned or shall otherwise pass to persons accessing this
information.
This Publication shall not be for resale in whole or in part.
Contents
Introduction.................................................................................. 1
Product Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
IPv4 initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
IPv6 initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network management with other applications . . . . . . . . . . . . . . . . . . . 2
Display Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Alarm LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Link-RX/TX (10/100) LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Watchdog Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Network interface watchdog mechanism . . . . . . . . . . . . . . . . . . . . . . . . 6
Resetting the network timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
How to Log On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
URL address formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Home Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Notification Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Types of notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuring event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
E-mail notification screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SNMP trap receiver screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
SNMP traps test screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Remote Monitoring Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
General Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Identification screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Date/Time screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Creating and importing settings with the configuration file . . . . . . . 42
Configuring the links screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
File Transfers............................................................................. 57
Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Firmware module files (InRow RC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Troubleshooting ....................................................................... 63
Network Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
The InRow Cooling ACRC301S and ACRC301H are Web-based, IPv6-ready products. They
can manage supported devices using multiple open standards such as:
Features:
Use Modbus RTU to view the network settings through the building management system.
For more information about the UIs, see “Web User Interface” on page 7. See
“SNMP screens” on page 31 for information about how SNMP access to the
cooling unit is controlled. See “Modbus” on page 33 for information on Modbus
access.
• A Super User/Administrator can use all of the menus in the UI and all of the commands in
the command line interface. Administrator user types can be deleted. The default user
name and password are both apc.
• A Device User has read and write access to device-related screens. Administrative
functions like Session Management under the Security menu and Firewall under Logs
are grayed out.
– The default user name is device, and the default password is apc.
• Read-only User has the following restricted access:
– Access through the Web UI and command line interface (CLI) only.
– Access to the same menus as a Device User above, but without the capability to
change configurations, control devices, delete data, or use file transfer options. Links
to configuration options are visible but disabled. (The Event and Data Logs display no
button for this user to clear the log.)
– The default user name is readonly and the default password is apc.
• A Network-only User can only log on using the Web user interface (UI) and CLI (telnet
not serial). A network-only user has read-write access to the network-related menus only.
There is no default name and password.
To set User Name and Password values for the top three account types, see “Local
Users” on page 21.
Display
Reset 10/100
Micro
SD
Service
Port
USB
na4331a
Console
Power LED The cooling unit is powered when the LED is illuminated.
Unit firmware is updating when LED is blinking.
Check Log LED When this LED is illuminated, a new entry has been made
to the event log.
Display Reset button Resets the display microprocessor. This has no effect on
the air conditioner controller.
Serial Configuration port Connects the display to a local computer to configure initial
network settings or access the command line interface
(CLI).
Condition Description
Off No Alarms
Solid yellow Warning Alarm
Solid red Critical Alarm
Status LED
This LED indicates the status of the display.
Condition Description
Off One of the following situations exist:
• The display is not receiving input power.
• The display is not operating properly. It may need to be
repaired or replaced. Contact Schneider Electric
Customer Support.
Solid green The display has valid TCP/IP settings.
Solid orange A hardware malfunction has been detected in the display.
Contact Schneider Electric Customer Support.
Flashing green The display does not have valid TCP/IP settings.
Flashing orange The display is making BOOTP requests.
Alternately flashing green If the LED is flashing slowly, the display is making DHCP
and orange requests.
If the LED is flashing rapidly, the display is starting up.
Condition Description
Off One or more of the following situations exist:
• The display is not receiving input power.
• The cable or device that connects the cooling unit to the
network is disconnected or not functioning properly.
• The display itself is not operating properly. It may need
to be repaired or replaced. Contact Schneider Electric
Customer Support
Solid green The display is connected to a network operating at 10
megabits per second (Mbps).
Solid orange The display is connected to a network operating at 100
Mbps.
Flashing green The display is receiving or transmitting at 10 Mbps.
Flashing orange The display is receiving data packets at 100 Mbps.
1. Select a serial port on the local computer, and disable any service that uses that port.
2. Connect the provided serial cable (part number 940-0299) to the selected port on the
computer and to the configuration port on the display.
3. Run a terminal program (such as HyperTerminal®) and configure the selected port for
9600 bps, 8 data bits, no parity, 1 stop bit, and no flow control.
4. Press Enter, repeatedly if necessary, to display the User Name prompt. If you are unable
to display the User Name prompt, verify the following:
– The serial port is not in use by another application.
– The terminal settings are correct as specified in step 3.
– The correct cable is being used as specified in step 2.
5. Press the Reset button. The Status LED will flash alternately orange and green. Press
the Reset button a second time immediately while the LED is flashing to reset the user
name and password to their defaults temporarily.
6. Press Enter, repeatedly if necessary, to display the User Name prompt again, then use
the default, apc, for the user name and password. (If you take longer than 30 seconds to
log on after the User Name prompt is redisplayed, you must repeat step 5 and log on
again.)
7. At the command line interface, use the following commands to change the Password
setting, which is apc at this stage:
user -n <user name> -pw <user password>
8. Type quit or exit to log off, reconnect any serial cable you disconnected from the
computer, and restart any service you disabled on the cooling unit.
Watchdog Features
Overview
To detect internal problems and recover from unanticipated input, the display uses internal,
system-wide watchdog mechanisms. When it restarts to recover from an internal problem, a
System: Network Interface restarted event is recorded in the event log.
See “Web access screen” on page 29 for information on how to select, enable, and
disable the protocols that control access to the UI and to define the Web-server ports
for the protocols.
The cooling unit cannot work with a proxy server. Before you can use a browser to access the
UI of the cooling unit, you must do one of the following:
• Configure the browser to disable the use of a proxy server for the cooling unit.
• Configure the proxy server so that it does not proxy the specific IP address of the cooling
unit
How to Log On
Overview
You can use the DNS name or the System IP address of the cooling unit for the URL address of
the UI. Use your case-sensitive user name and password to log on. If you do not have a user
name and password assigned, the default user name can be used and differs by account type:
When HTTPS is enabled, the cooling unit generates its own certificate. This certificate
negotiates encryption methods with your browser. Refer to the Security Guide on the http://
www.apc.com cooling unit web site for more details.
HTTP http://Web1
HTTPS https://Web1
HTTP http://139.225.6.133
HTTPS https://139.225.6.133
HTTP http://139.225.6.133:5000
HTTPS http://139.225.6.133:5000
HTTP http://[2001:db8:1::2c0:b7ff:fe00:1100]:5000
One or more icons and accompanying text indicate the current operating status of the cooling
unit:
Symbol Description
No Alarms: No alarms are present.
In the upper-right corner of every screen, the same icons report the cooling unit status. If any
Critical or Warning alarms exist, the number of active alarms also displays.
Icons and links. To make any screen the “home” screen (i.e., the screen that displays first
when you log on), go to that screen, and click the icon in the top right corner.
Click to revert to displaying the Home screen when you log on.
At the lower left on each screen of the interface, there are three configurable links to useful
websites. By default, the links access the URLs for these Web pages:
To reconfigure the links, see “Configuring the links screen” on page 42.
You can configure your cooling unit and network using the Configuration menu
options. See “Configuring Your Settings” on page 17.
Unit Status
Path: Main > Status > Unit
This screen displays useful information about the cooling unit.
Overview
Operating Mode. Identifies the operating mode of the cooling unit.
• Standby: The cooling unit is receiving power but not enabled for cooling.
• On: The cooling unit is cooling.
• Idle: The cooling unit is no longer cooling due to active alarms.
• Maintenance: Testing mode used by qualified service personnel.
Rack Inlet Temperature. The maximum temperature of the rack inlet temperature sensors
connected to the unit.
Supply Air Temperature. The temperature of the air leaving the cooling unit.
Return Air Temperature. The temperature of the air entering the cooling unit.
Dew Point Temperature. The dew point of the environment (ACRC301H only).
Airflow. The velocity at which air flows into or out of the unit.
Fan Speed. The speed of the fans that regulate the airflow through the cooling unit.
Cool Demand. The output required of the cooling unit to meet the current heat load of the
conditioned space.
Unit Energy. The electrical energy consumed by the unit since the last Reset Unit Energy
command (Main > Configuration > Unit > Unit Configuration).
Unit Power. The electrical power being consumed by the cooling unit.
Detailed Status
Chilled Water Valve Position. The position of the valve that controls how much chilled water
enters the cooling unit.
Chilled Water Flow. The rate at which chilled water flows through the cooling unit.
Entering Chilled Water Temperature. The temperature of the chilled water as it enters the
cooling unit.
Coil Chilled Water Temperature. The temperature of chilled water entering the coil
(ACRC301H only).
Standby Input State. The current state of the input. If the input is in an abnormal state, an alarm
will occur and the unit will stop cooling.
Output 1-4 State. The current state of the four output relays.
Filter Differential Pressure. The difference in air pressure across the air filter.
Active Power Source. The power source being used by the unit. The unit supports a redundant
power input.
• Unit
• Condensate Pump (ACRC301S only)
• Circulation Pump (optional for ACRC301H only)
• Fan Power Supply 1-2
• Air Filter
NOTE: When the air filter is replaced, use the Air Filter Serviced button to reset the
maintenance alarm.
• Fan 1-8 (Fan 1 is the bottom fan; Fan 8 is the top fan)
Group Status
Path: Main > Status > Group
This screen displays the status of the group of cooling units connected by A-Link.
Overview
Cool Output. The actual cooling output of the cooling group.
Cool Demand. The output required to meet the current heat load of the conditioned space.
Cool Setpoint. The temperature setting that the air entering the rack should maintain (InRow,
CACS modes only).
Airflow. The total airflow output of the cooling units in the cooling group.
Maximum Rack Inlet Temperature. The highest rack temperature reported by any cooling unit
in the cooling group.
Minimum Rack Inlet Temperature. The lowest rack temperature reported by any cooling unit in
the cooling group.
• Over: Airflow provided by the cooling units is more than the load requires.
• Okay: Airflow provided by the cooling units is equal to what the load requires.
• Under: Airflow provided by the cooling units less than the load requires.
• N/A: The cooling units are not using the Active Flow Controller.
Group Units
Name. The names of cooling units in this group.
App Version. The application version of the display of cooling units in the group.
Network Status
Path: Main > Status > Network
The Network screen displays information about your network.
Default Gateway. The IP address of the router used to connect to the network.
Mode. How the IPv4 settings are assigned: Manual, DHCP, or BOOTP.
DHCP Server. The IP address of the DHCP server. This is only displayed if Mode is DHCP.
Lease Acquired. The date/time that the IP address was accepted from the DHCP server.
Lease Expires. The date/time that the IP address accepted from the DHCP server expires and
will need to be renewed.
Active Secondary DNS Server. The IP address of the secondary DNS server.
Active Domain Name (IPv4/IPv6). The IPv4/IPv6 domain name that is currently in use.
Active Domain Name (IPv6). The IPv6 domain name that is currently in use.
Unit Configuration
Under the Configuration > Unit menu, several options are available to make changes to the
cooling unit.
Unit thresholds
Path: Main > Configuration > Unit > Thresholds
This menu displays various unit thresholds, their sensor value, and the editable threshold
setting. After making changes to a given threshold temperature, click Apply to confirm
changes, or Cancel to revert to previous settings. An example of this would be if the water
temperature exceeds the temperature defined by the corresponding Temperature Threshold,
an alarm will occur.
Rack Inlet Temperature High Threshold. The air entering the rack at the temperature sensor.
Supply Air Temperature High Threshold. The air leaving the cooling unit.
Return Air Temperature High Threshold. The air entering the cooling unit.
Entering Chilled Water High Temperature Threshold. The chilled water entering the cooling
unit.
Startup Delay. The delay begins when the cooling unit is started and initialized. The cooling unit
cannot begin operation until this delay has expired. Use the start-up delay to restart equipment
sequentially in your room after a scheduled downtime.
Idle on Leak Detect. When set to Yes, the cooling unit will enter idle mode if a Water Detected
Error activates. Set to No to disable the cooling unit from entering idle mode if a leak is
detected.
Idle on Cool Fail. When set to Yes, the cooling unit will enter idle mode if the cooling unit is
unable to supply conditioned air. Set to No to disable the cooling unit from entering idle mode if
a cooling failure is detected.
Bypass Valve Position. Reflects the position of the manual bypass valve. This setting must
match the physical setting of the valve. When the bypass valve is closed, the maximum chilled
water flow is limited via the Maximum Chilled Water Flow setting.
Air Filter. The number of hours the air filter has been in operation.
Air Filter Serviced. Select this check box to reset an Air Filter Run Hours Violation or air filter
status after the physical air filter is cleaned or replaced.
Air Filter Service Interval. Enter the number of weeks between air filter service alarms.
Air Filter Type. The type of air filter installed in the cooling unit: Standard or Pleated.
Maximum Chilled Water Flow. Restricts the maximum chilled water flow rate of the unit. This
setting is only used when the bypass valve is closed. The input range is 0-100 gallons per
minute (0-379 liters per minute). Only qualified service personnel can make changes to this
setting.
Chilled Water Valve Control. The setting used to determine chilled water flow. When
Automatic is selected, the unit operates based on measured demand. Only qualified service
personnel can make changes to this setting.
Power Source. Indicates the number of power sources connected to the cooling unit. Select
Single when using one power connection. Select Dual when using two power connections.
Number of Rack Inlet Temp Sensors in Unit. The number of expected rack inlet sensors for
the unit. The maximum number of rack inlet temperature sensors is four.
Number of Leak Detectors in Unit. The number of expected leak detectors in the unit. The
maximum number of leak detectors is four.
Unit Service Alarm Enable. Enable or Disable the unit service alarm. Only qualified service
personnel can make changes to this setting.
Unit Service Alarm Interval. Enter the number of weeks between unit service alarms.Only
qualified service personnel can make changes to this setting.
Unit Energy. The electrical energy consumed by the unit since the last time the Unit Energy
has been reset or the cooling unit has been powered on.
Reset Unit Energy. Select this check box to reset the Unit Energy.
Under Current Settings, use the check boxes under each output name to specify whether the
output will change that relay to the abnormal state when the selected alarm is active. More than
one output can be selected for a specified alarm. No more than 20 alarms per output can be
selected.
Setpoints
A setpoint is the target value that a cooling group will maintain in the environment. The default
setpoints are appropriate for most cooling applications.
Cool Setpoint. Set the temperature that the cooling group should maintain. The setpoint must
be within 18.0–35.0°C (64.4–95.0°F).
NOTE: This is the temperature maintained at the rack inlets.
Supply Air Setpoint. The setpoint must be within 15.0–30.2°C (59.0–86.4°F). The Supply Air
Setpoint will be the required temperature of the air expelled into the surrounding environment.
NOTE: The Supply Air Setpoint is defined by the field service representative when the cooling
group is commissioned.
Delta-T Setpoint. When the group is programmed for HACS or RACS mode and an AFC is not
being used, this property specifies the desired temperature difference across the equipment
from the following options.
• 10°F/5.6°C
• 15°F/8.3°C
• 20°F/11.1°C
• 25°F/13.9°C
• 30°F/16.7°C
• 35°F/19.4°C
• 40°F/22.2°C
Group Configuration
Number of Units in Group. Indicates the number of cooling units in this cooling group. Up to
twelve cooling units can be joined together to work as a single cooling group.
Configuration Type. The airflow control strategy for the cooling units of this cooling group. Only
qualified service personnel can make changes to this setting.
• In-Row: Air flow is horizontal to allow in-row operation of the cooling. The loads share a
common open cold aisle.
• HACS (Hot Aisle Containment System): Air flow in the room is controlled by enclosing
the hot air aisle. The loads share an enclosed common hot aisle. This is not a sealed
system.
• RACS (Rack Air Containment System): Air flow in the enclosure is controlled by a
ducting system fitted to the enclosure. This is not a sealed system.
• CACS (Cold Aisle Containment System): Air flow in the room is controlled by
enclosing the cold air aisle. The loads share an enclosed common cold aisle. This is not
a sealed system.
Maximum Fan Speed. Defines the maximum speed at which the fans in the unit operate when
in Auto mode.
NOTE: Reducing the fan speed will affect the cooling capacity of the unit.
Number of Active Flow Controllers. Sets number of AFC units in the group (0 to 5).
Active Flow Control Bias. This setting is used to control the difference between the cooling
airflow and the airflow of the load as measured by the Active Flow Controller(s). A setting of
Zero will control the fans to match the airflow of the load. A setting of Positive will provide
more cooling airflow than required by the load. A setting of Negative will provide less cooling
airflow than required by the load. Only qualified service personnel should make changes to
these settings.
Altitude. Set the altitude (in feet or meters) of the cooling unit above sea level. This number is
used to estimate the density of air and is a factor in pressure measurement.
Airflow control. When Automatic is selected, the cooling unit operates based on measured
demand. When set to 60%, 70%, 80%, 90%, 100%, the fans will operate at the selected output.
Cool Gain “P”. The proportional multiplier (gain) for this mode or actuator. The proportional
multiplier adjusts for the difference (error) between the measured temperature and the setpoint.
The proportional multiplier is expressed in percent of output per unit error. Only qualified
service personnel can make changes to this setting.
Cool Derivative “D”. The derivative multiplier (derivative) for this mode or actuator. The
derivative multiplier adjusts the output for rapid changes in the error, correcting for the rate of
change of the error over time. It is expressed in percent of output for each unit of error per
minute (error divided by minutes). Only qualified service personnel can make changes to this
setting.
Cool Reset Rate “I”. The integral multiplier (reset rate) for this mode or actuator. The integral
multiplier adjusts for error measurement and for the amount of time that the error has existed.
The integral multiplier adds to or subtracts from the output in small increments to correct for the
offset error caused by the proportional contribution. It is expressed in percent of output for each
minute and unit of error (error multiplied by minutes). Only qualified service personnel can
make changes to this setting.
Security Menu
Session management screen
Path: Main > Configuration > Security > Session Management
Enabling Allow Concurrent Logins means that two or more users can log on at the same
time. Each user has equal access and each interface (HTTP, FTP, telnet console, serial
console (CLI), etc.) counts as a logged-in user.
Ping response
Path: Main > Configuration > Security > Ping Response
Enable the IPv4 Ping Response check box to allow the cooling unit to respond to network
pings. This does not apply to IPv6.
Local Users
Use these menu options to view, and to set up access and individual preferences (like
displayed date format), for the cooling unit user interfaces. This applies to users as defined by
their logon name.
Path: Main > Configuration > Security > Local Users > Management
From this menu, an administrator or super user can view the users allowed access to the UI.
Click on the name link to view details and to edit or delete a user.
Click Add User to add a user. On the resulting User Configuration screen, you can add a user
and withhold access by clearing the Access check box. The maximum length for both the
name and password is 64 characters, with less for multi-byte characters. You have to enter a
password.
To change an administrator/ super user setting, you must supply the current password as a
security measure.
Session Timeout. Use to configure the length of time that the various UIs wait before logging-
out this user (three minutes by default). If you change this value, the user must log-off for the
change to take effect.
Serial Remote Authentication Override. The cooling unit will allow a user with this enabled to
log-on to the cooling unit using the password for local authentication. Remote Authentication
Override must be enabled on the Configuration > Security > Session Management screen
for this to function.
• Event Log Color Coding: Select the check box to enable color-coding of alarm text
recorded in the event log based on severity. (System-event entries and configuration-
change entries do not change color because they considered informational events.)
• Export Log Format: Exported log files can be formatted using CSV (comma-separated
values) or tab-delimited.
• Temperature Scale: Select the temperature scale for measurements in this UI. US
Customary corresponds to Fahrenheit, and Metric corresponds to Celsius.
• Date Format: Select the date form for the UI.
• Language: Select the default language for the UI. This can be set when you log on also.
You can also specify different languages for e-mail recipients and SNMP trap receivers.
See “E-mail notification screens” on page 37 and “SNMP trap receiver screen” on
page 39.
Path: Main > Configuration > Security > Local Users > Default Settings
Setting up defaults can make adding users quicker. Use this option to set defaults for the
options on the Management screen. A remote RADIUS user will also use these default
settings.
The following authentication and authorization functions of remote authentication dial-in user
service (RADIUS) are supported:
• When a user accesses the cooling unit or other network-enabled device that has
RADIUS enabled, an authentication request is sent to the RADIUS server to determine
the permission level of the user.
• RADIUS user names are limited to 32 characters with the cooling unit.
Select one of the following:
For example, the command to change the access setting to local would be
radius -a local
• List the RADIUS servers (a maximum of two) available to the cooling unit and the time-
out period for each.
• Configure the authentication parameters for a new or existing RADIUS server by clicking
on a RADIUS server link.
The RADIUS Server menu for each RADIUS server contains the following options:
RADIUS Server. The name or IP address (IPv4 or IPv6) of the RADIUS server.
Port. The port on which the RADIUS server listens to authenticate users. This is port 1812 by
default but can be changed to any unused port between 5000-32678.
Secret. The shared secret between the RADIUS server and the cooling unit.
Reply Timeout. The time in seconds that the cooling unit waits for a response from the
RADIUS server.
Test Settings. Enter the user name and password configured on the RADIUS server order to
test the configured settings.
Skip Test and Apply. Applies the RADIUS server settings without testing.
Add the IP address of the cooling unit to the RADIUS server client list (file).
1. Users must be configured with Service-Type attributes unless Vendor Specific Attributes
(VSAs) are defined. If no Service-Type attributes are configured, users will have read-
only access (on the UI only).
2. VSAs can be used instead of the Service-Type attributes provided by the RADIUS
server.
3. VSAs require a dictionary entry and a RADIUS user’s file. In the dictionary file, define
the names for the ATTRIBUTE and VALUE keywords, but not for the numeric values. If
you change numeric values, RADIUS authentication and authorization will not work.
VSAs take precedence over standard RADIUS attributes.
Configuring a RADIUS server on UNIX® with shadow passwords. If UNIX shadow password
files are used (/etc/passwd) with the RADIUS dictionary files, the following two methods can be
used to authenticate users:
• If all UNIX users have administrative privileges, add the following to the RADIUS “user”
file. To allow only Device Users, change the APC-Service-Type to Device.
DEFAULT Auth-Type = System
APC-Service-Type = Admin
• Add user names and attributes to the RADIUS “user” file, and verify the password
against /etc/passwd. The following example is for users bconners and thawk:
APC-Service-Type = Admin
APC-Service-Type = Device
Supported RADIUS servers. FreeRADIUS and Microsoft IAS 2003 are supported. Other
commonly available RADIUS applications may work but have not been fully tested.
Firewall Menus
Path: Main > Configuration > Security > Firewall
Configuration. Enable or disable the overall firewall functionality. Any configured policy is also
listed, even if the firewall is disabled.
Active Policy. Select an active policy from the available firewall policies. The validity of policy is
also listed here.
Active Rules. When a firewall is enabled, this lists the individual rules that are being enforced
by a current active policy. You can edit existing rules and add or delete new rules here.
Load Policy. Load a policy (with .fwl suffix) from a source external to this device.
Test. Temporarily enforce the rules of a chosen policy for a time that you specify.
Manual. Specify your IPv4 address, subnet mask, default gateway here.
BOOTP. At 32-second intervals, the device requests network assignment from any BOOTP
server:
• If a DHCP server is found, but the request to that server does not work or times out, it
stops requesting network settings until it is restarted.
• Optionally, you can set up the device with Require vendor specific cookie to accept
DHCP Address in order to accept the lease and start the network services.
Vendor Class: This should be APC. This is only available if BOOTP or DHCP is selected.
Client ID. The MAC address of the device. If you change this value, the new value must be
unique on the LAN. This is only available if BOOTP or DHCP is selected.
User Class: The name of the application firmware module. This is only available if BOOTP or
DHCP is selected.
You have a choice of using manual or automated IP addressing. It is possible to use them both
concurrently. For Manual, select the check box and then enter the System IPv6 address and
the Default Gateway.
Select the Auto Configuration check box to enable the system to obtain addressing prefixes
from the router (if available). It will use those prefixes to automatically configure IPv6
addresses.
Option Description
Router Controlled When this radio box is selected, DHCPv6 is controlled by the M (Managed Address
Configuration Flag) and O (Other Stateful Configuration Flag) flags received in IPv6
router advertisements.
When a router advertisement is received, the cooling unit checks whether the M and O
flags are set. The cooling unit interprets them as follows:
• Neither is set: Indicates that the local network has no DHCPv6 infrastructure. The
cooling unit uses Router Advertisements and manual configuration to get non-link-
local addresses and other settings.
• M, or M and O are set: In this situation, full DHCPv6 address configuration occurs.
DHCPv6 is used to obtain addresses AND other configuration settings. This is known
as “DHCPv6 stateful”.
Once the M flag has been received, the DHCPv6 address configuration stays in effect
until the interface in question has been closed, even if subsequent Router
Advertisement packets are received in which the M flag is not set.
If an O flag is received first, then an M flag is received subsequently, the cooling unit
performs full address configuration upon receipt of the M flag.
• Only O is set: In this situation, the cooling unit sends a DHCPv6 Info-Request
packet. DHCPv6 is used to configure “other” settings (such as location of DNS
servers), but NOT to provide addresses. This is known as “DHCPv6 stateless”.
Address and DHCPv6 is used to obtain addresses AND other configuration settings. This is known
Other Information as “DHCPv6 stateful”.
Non-Address DHCPv6 is used to configure “other” settings (such as location of DNS servers), but
Information Only NOT to provide addresses. This is known as “DHCPv6 stateless”.
Never DHCPv6 is NOT used for any configuration settings.
Vendor Specific Information (option 43). The cooling unit uses this option in a DHCP
response to determine whether the DHCP response is valid. This option contains an option in a
TAG/LEN/DATA format, called the APC Cookie. This is disabled by default.
• IP Address (from the yiaddr field of the DHCP response, described in RFC2131): The
IP address that the DHCP server is leasing to the cooling unit.
• Subnet Mask (option 1): The Subnet Mask value that the cooling unit needs to operate
on the network.
• Router, i.e., Default Gateway (option 3): The default gateway address that the cooling
unit needs to operate on the network.
• IP Address Lease Time (option 51): The time duration for the lease of the IP Address to
the cooling unit.
• Renewal Time, T1 (option 58): The time that the cooling unit must wait after an IP
address lease is assigned before it can request a renewal of that lease.
• Rebinding Time, T2 (option 59): The time that the cooling unit must wait after an IP
address lease is assigned before it can seek to rebind that lease.
Other options. The cooling unit also uses these options within a valid DHCP response. All of
these options except the last are described in RFC2132.
• Network Time Protocol Servers (option 42): Up to two NTP servers (primary and
secondary) that the cooling unit can use.
• Time Offset (option 2): The offset of the cooling unit's subnet, in seconds, from
Coordinated Universal Time (UTC).
• Domain Name Server (option 6): Up to two Domain Name System (DNS) servers
(primary and secondary) that the cooling unit can use.
• Host Name (option 12): The host name that the cooling unit will use (32-character
maximum length).
• Domain Name (option 15): The domain name that the cooling unit will use (64-character
maximum length).
• Boot File Name (from the file field of the DHCP response, described in RFC2131): The
fully qualified directory-path to a user configuration file (.ini file) to download. The siaddr
field of the DHCP response specifies the IP address of the server from which the cooling
unit will download the .ini file. After the download, the cooling unit uses the .ini file as a
boot file to reconfigure its settings.
You can change the setting by choosing a radio button under Port Speed:
• For Auto-negotiation (the default), network devices negotiate to transmit at the highest
possible speed, but if the supported speeds of two devices are not matched, the slower
speed is used.
• Alternatively, you can choose 10 Mbps or 100 Mbps, each with the following options:
– Half-Duplex (communication in only one direction at a time)
– Full-Duplex (communication in both directions on the same channel simultaneously).
Use the options under Manual Domain Name System Settings to configure the Domain Name
System (DNS):
Override Manual DNS Settings. Enabling the Override Manual DNS Settings means that
configuration data from other sources like DHCP take precedence over the manual
configurations here.
Primary DNS Server. Specify the Primary DNS Server and, optionally, the Secondary DNS
Server with IPv4 or IPv6 addresses. For the cooling unit to send email, you must at least define
the IP address of the primary DNS server.
• The cooling unit waits up to 15 seconds for a response from the primary DNS server or
the secondary DNS server. If the cooling unit does not receive a response within that
time, email cannot be sent. Use DNS servers on the same segment as the cooling unit or
on a nearby segment, but not across a wide-area network (WAN).
• After you define the IP addresses of the DNS servers, test it.
System Name Synchronization. Enabling this synchronizes the DNS hostname with the
cooling unit system name. Click on the System Name link to define it.
Host Name. After you configure a host name here and a domain name in the Domain Name
field, users can enter a host name in any field in the cooling unit interface (except e-mail
addresses) that accepts a domain name.
Domain Name (IPv4/IPv6). For the cooling unit interface, you only need to configure the
domain name here. In all other fields in this UI — except email addresses — that accept
domain names, the cooling unit defaults to adding this domain name when only a host name is
entered.
• To override the expansion of a specified host name by the addition of a domain name, set
this domain name field to its default, somedomain.com or to 0.0.0.0.
• To override the expansion of a specific host name entry (for example, when defining a
trap receiver), include a trailing period. The cooling unit recognizes a host name with a
trailing period (such as mySnmpServer.) as if it were a fully-qualified domain name and
does not append the domain name.
Domain Name (IPv6). Specify the IPv6 domain name here.
• For Query Type, select the method to use for the DNS query, see table below.
• For Query Question, specify the value to be used for the selected query type as
explained in the table.
HTTP. Select this check box to enable access through HTTP. HTTP does not encrypt user
names, passwords, and data during transmission.
HTTPS. Select this check box to enable access through HTTPS. HTTPS encrypts user names,
passwords, and data during transmission.
HTTP Port. The port used for HTTP connection. The port range is 5000–32768: default is 80.
HTTPS Port. The port used for HTTPS connection. The port range is 5000–32768: default is
443.
NOTE: You must use a colon (:) in the address field of the browser to specify the port number.
For example, for a port number of 5000 and an IP address of 152.214.12.114 enter
http(s)://152.214.12.114:5000.
Require Authentication Cookie. If enabled, a session cookie will be used for authentication
tracking within the browser. The cookie will be removed upon session end.
Limited Status Access. Select whether or not to display a read-only, public Web page with
basic device status. This feature is disabled by default and can be set via the Use as default
page option to show as the default landing page when a user accesses the device with just the
IP/hostname (no specific page listed).
• Valid certificate: A valid certificate was installed or was generated by the cooling unit.
Click on this link to view the contents of the certificate.
• Certificate not installed: A certificate is not installed or was installed by FTP or SCP to
an incorrect location. Using Add or Replace Certificate File installs the certificate to the
correct location: /ssl on the cooling unit.
• Generating: The cooling unit is generating a certificate because no valid certificate was
found.
• Loading: A certificate is being activated on the cooling unit.
IMPORTANT: If you install an invalid certificate, or if no certificate is loaded while SSL is
enabled, the cooling unit generates a default certificate, a process which delays access to the
interface for up to one minute. You can use the default certificate for basic encryption-based
security, but a security alert message displays whenever you log on.
Add or Replace Certificate File. Browse to the certificate file created with the Security Wizard.
Console screen
Path: Main > Configuration > Network > Console > Access
Console access. Console access enables use of the command line interface (CLI).
You can enable access to the CLI through either Telnet or SSH or through both, by using the
Enable check boxes. Telnet does not encrypt user names, passwords, and data during
transmission whereas SSH 2 does.
For the ports to be used to communicate with the cooling unit, you can change the setting to
any unused port from 5000 to 32768 for additional security.
• Telnet Port: This is 23 by default. You must then use a colon (:) or a space to specify the
non-default port, as required by your Telnet client program.
For example, for port 5000 and an IP address of 152.214.12.114, your Telnet client
requires one of the these commands:
telnet 152.214.12.114:5000 or telnet 152.214.12.114 5000
• SSH Port: This is 22 by default. See the documentation for your SSH client for the
command line format required to specify a non-default port. See also “SSH Host Key”
below.
Path: Main > Configuration > Network > Console > SSH Host Key
If you are using SSH (Secure Shell Protocol) for console (CLI) access, you can add, replace, or
remove the host key on the User Host Key screen.
NOTE: To reduce the time required to enable SSH, create and upload a host key in advance. If
you enable SSH with no host key loaded, the cooling unit takes up to one minute to create a
host key, and the SSH server is not accessible during that time.
To use SSH, you must have an SSH client installed. Most Linux and other UNIX platforms
include an SSH client, but Microsoft Windows operating systems do not. Clients are available
from various vendors.
SNMP screens
All user names, passwords, and community names for SNMP are transferred over the network
as plain text. If your network requires the high security of encryption, disable SNMP access or
set the access for each community to Read. (A community with Read access can receive
status information and use SNMP traps.)
When using StruxureWare Data Center Expert to manage a cooling unit on the public network
of a StruxureWare system, you must have SNMPv1 or SNMPv3 enabled in the cooling unit
interface. Read access will allow the StruxureWare device to receive traps from the cooling
unit, but Write access is required while you use the cooling unit user interface to set the
StruxureWare device as a trap receiver.
Path: Main > Configuration > Network > SNMPv1 > Access
Use Access to enable or disable SNMP version 1 as a method of communication with the
cooling unit.
Path: Main > Configuration > Network > SNMPv1 > Access Control
Access Control. You can configure up to four access control entries to specify which Network
Management Systems (NMSs) have access to the cooling unit. To edit, click a community
name.
• By default, a community has access to the cooling unit from any location on the network.
• If you configure multiple access control entries for any one community name, it means
that one or more of the other communities have no access to the device.
Community Name. The name that an NMS must use to access the community. The maximum
length is 15 ASCII characters, and the default names are public, private, public2, and private2.
NMS IP/Host Name. The IPv4 or IPv6 address, IP address mask, or host name that controls
access by NMSs. A host name or a specific IP address (for example, 149.225.12.1) allows
access only by the NMS at that location. IP addresses that contain 255 restrict access as
follows:
Path: Main > Configuration > Network > SNMPv3 > Access
For GETs, SETs, and trap receivers, SNMPv3 uses a system of user profiles to identify users.
An SNMPv3 user must have a user profile assigned in the MIB software program to perform
GETs and SETs, to browse the MIB, and to receive traps.
To use SNMPv3, you must have a MIB program that supports SNMPv3.
The cooling unit supports SHA or MD5 authentication and AES or DES encryption.
Enable SNMPv3 Access under the Access menu enables this method of communication with
this device.
Path: Main > Configuration > Network > SNMPv3 > User Profiles
By default, User Profiles lists the settings of four user profiles configured with the user names
apc snmp profile1 through apc snmp profile4, with no authentication and no privacy (no
encryption). To edit the following settings for a user profile, click a user name in the list.
User Name. The identifier of the user profile. SNMP version 3 maps GETs, SETs, and traps to a
user profile by matching the user name of the profile to the user name in the data packet being
transmitted. A user name can have up to 32 ASCII characters.
Privacy Protocol. The implementation of SNMPv3 supports AES and DES as the protocols for
encrypting and decrypting data. You must use both a privacy protocol and a privacy password,
otherwise the SNMP request is not encrypted.
In turn, you cannot select the privacy protocol if no authentication protocol is selected.
Path: Main > Configuration > Network > SNMPv3 > Access Control
You can configure up to four access control entries to specify which Network Management
Systems (NMSs) have access to the cooling unit. To edit, click a user name.
By default one entry is assigned to each of the four user profiles. You can edit these settings to
apply more than one entry to any one user profile to grant access by several specific IP
addresses, host names, or IP address masks.
• By default, all NMSs that use that profile have access to this device.
• If you configure multiple access control entries for one user profile, it means that one or
more of the other user profiles must have no access to this device.
User Name. From the drop-down list, select the user profile to which this access control entry
will apply. The choices available are the four user names that you configure through the User
Profiles option.
NMS IP/Host Name. The IP address, IP address mask, or host name that controls access by
the NMS. A host name or a specific IP address (for example, 149.225.12.1) allows access only
by the NMS at that location. An IP address mask that contains 255 restricts access as follows:
Modbus
Use the Modbus menu to set up communications between the cooling unit and the building
management system.
Configure the Modbus by enabling Serial or TCP Access and adding the required values.
Target Unique ID. Each Modbus device must have a unique target identification number. Enter
a unique number (between 1 and 247) for the cooling unit.
Path: Main > Configuration > Network > Modbus > TCP
Access. FTP transmits files without encrypting them. For encrypted file transfer, use Secure
CoPy (SCP). SCP is automatically enabled when you enable SSH, but you must disable the
FTP Server here to enforce high-security file transfer.
NOTE: At any time that you want a device to be accessible for management by StruxureWare
Data Center Expert, FTP Server must be enabled in the Network Management Card interface
of that cooling unit.
Port. The TCP/IP port of the FTP server (21 by default). The FTP server uses both the
specified port and the port one number lower. The allowed non-default port numbers are
indicated on the screen: 21, and 5001–32768.
NOTE: Configuring the FTP server to use a non-default port enhances security by requiring
users to append the port name to the IP address in an FTP command line. The appended port
name must be preceded by a space or colon depending on the FTP client used.
Notification Menu
Types of notification
You can configure notification actions to occur in response to an event. You can notify users of
an event in any of several ways:
• Active, automatic notification: The specified users or monitoring devices are contacted
directly.
– E-mail notification
– SNMP traps
– Remote Monitoring Service
– Syslog notification
• Indirect notification
– Event log: If no direct notification is configured, users must check the log to determine
which events have occurred
1. To find an event, click on a column heading to see the lists under the Device Events or
System Events categories.
Or you can click on a sub-category under these headings, like Security or
Temperature.
2. Click on the event name to view or change the current configuration, such as recipients
to be notified by e-mail, or Network Management Systems (NMSs) to be notified by
SNMP traps.
If no Syslog server is configured, items related to Syslog configuration are not displayed.
When viewing details of an event configuration, you can enable or disable event
logging or Syslog, or disable notification for specific e-mail recipients or trap
receivers, but you cannot add or remove recipients or receivers. To add or remove
recipients or receivers, see the following:
Field Description
Delay n time before If the event persists for the specified time, the notification is sent. If the
sending condition clears before the time expires, no notification is sent.
For events that have an associated clearing event, you can also set these parameters. (An
example of an event with its clearing event is RC: Fan 2 Error Detected and RC: Fan 2
Error Corrected.
• The IP addresses of the primary and, optionally, the secondary Domain Name System
(DNS) servers.
• The IP address or DNS name for the SMTP Server and From Address.
• The e-mail addresses for a maximum of four recipients.
• You can use the To Address setting of the recipients option to send e-mail to a text-based
screen.
Path: Main > Configuration > Notification > E-mail > Server
This screen lists your primary and secondary DNS servers and displays the following fields:
From Address. The contents of the From field in e-mail messages sent by the cooling unit:
• In the format user@ [IP_address] (if an IP address is specified as Local SMTP Server)
• In the format user@domain (if DNS is configured and the DNS name is specified as
Local SMTP Server) in the e-mail messages.
NOTE: The local SMTP server may require that you use a valid user account on the
server for this setting. See the server documentation.
SMTP Server. The IPv4/ IPv6 address or DNS name of the local SMTP server.
NOTE: This definition is required only when the SMTP server is set to Local.
Port. The SMTP port number, with a default of 25. The range is 1–65535.
User Name, Password, and Confirm Password. If your mail server requires authentication,
enter your user name and password here. This performs a simple authentication, not SSI.
• Never: The SMTP server does not require nor support encryption.
• If Supported: The SMTP server advertises support for STARTTLS but doesn't require
the connection to be encrypted. The STARTTLS command is sent after the
advertisement is given.
• Always: The SMTP server requires the STARTTLS command to be sent on connection
to it.
• Implicitly: The SMTP server only accepts connections that begin encrypted. No
STARTTLS message is sent to the server.
Require CA Root Certificate. This should only be enabled if the security policy of your
organization does not allow for implicit trust of SSL connections. If this is enabled, a valid root
CA certificate must be loaded onto the cooling unit for encrypted e-mails to be sent.
File Name. This field is dependent on the root CA certificates installed on the cooling unit and
whether or not a root CA certificate is required.
Path: Main > Configuration > Notification > E-mail > Recipients
Specify up to four e-mail recipients. Click on a name to configure the settings.
To Address. The user and domain names of the recipient. To use e-mail for paging, use the e-
mail address for the recipient’s pager gateway account (for example,
myacct100@skytel.com). The pager gateway will generate the page.
To bypass the DNS lookup of the IP address of the mail server, use the IP address in brackets
instead of the e-mail domain name, e.g., use jsmith@[xxx.xxx.x.xxx] instead of
jsmith@company.com. This is useful when DNS lookups are not working correctly.
Format:. The long format contains name, location, contact, IP address, serial number of the
device, date and time, event code, and event description. The short format provides only the
event description.
• Local: This is through the site-local SMTP server. This recommended setting ensures
that the e-mail is sent using the site-local SMTP server. Choosing this setting limits
delays and network outages and retries sending e-mail for many hours. When choosing
the Local setting you must also enable forwarding at the SMTP server of your device and
set up a special external e-mail account to receive the forwarded e-mail. Check with your
SMTP server administrator before making these changes.
• Recipient: This is the SMTP server of the recipient. The cooling unit performs an MX
record look-up on the recipients e-mail address and uses that as its SMTP server. The e-
mail is only sent once so it could easily be lost.
• Custom: This setting enables each e-mail recipient to have its own server settings.
These settings are independent of the settings given under “SMTP Server” above.
When installed, the certificate details also display here. An invalid certificate will display “n/a”
for all fields except File Name.
Certificates can be deleted using this screen. Any e-mail recipients using the certificate should
be manually modified to remove reference to this certificate.
Path: Main > Configuration > Notification > E-mail > Test
Send a test message to a configured recipient.
The trap receivers are displayed by NMS IP/Host Name, where NMS stands for Network
Management System. You can configure up to six trap receivers.
To configure a new trap receiver, click Add Trap Receiver. To edit (or delete) one, click its IP
address/host name.
Trap Generation. Enable (the default) or disable trap generation for this trap receiver.
NMS IP/Host Name. The IPv4/ IPv6 address or host name of this trap receiver. The default,
0.0.0.0, leaves the trap receiver undefined.
Language. Select a language from the drop-down list. This can differ from the UI and from
other trap receivers.
Select either the SNMPv1 or SNMPv3 radio button to specify the trap type. For an NMS to
receive both types of traps, you must separately configure two trap receivers for that NMS, one
for each trap type.
• Community Name: The name (“public” by default) used as an identifier when SNMPv1
traps are sent to this trap receiver.
• Authenticate Traps: When this option is enabled (the default), the NMS identified by the
NMS IP/Host Name setting will receive authentication traps (traps generated by invalid
attempts to log on to this device).
SNMPv3. Settings for SNMPv3.
• User Name: Select the identifier of the user profile for this trap receiver.
If you delete a trap receiver, all notification settings configured under “Configuring event
actions” for the deleted trap receiver are set to their default values.
Last Test Result. The result of the most recent SNMP trap test. A successful SNMP trap test
verifies only that a trap was sent; it does not verify that the trap was received by the selected
trap receiver. A trap test succeeds if all of the following are true:
• The SNMP version (SNMPv1 or SNMPv3) configured for the selected trap receiver is
enabled on this device.
• The trap receiver itself is enabled.
• If a host name is selected for the To address, that host name can be mapped to a valid IP
address.
To. Select the IP address or host name to which a test SNMP trap will be sent. If no trap
receiver is configured, a link to the Trap Receiver configuration screen is displayed.
To purchase the RMS service, contact your vendor or click on the link on the top part
of this screen: APC RMS Web site.
Registration. Once you have purchased the service, you activate RMS for the cooling unit.
Select Enable APC Remote Monitoring Service, select Register Company and Device or
Register Device Only, complete the form, and click Apply.
Use the Reset APC Remote Monitoring Service Registration check box to discontinue the
service, whether permanently or temporarily (for example, if you are moving a cooling unit).
General Menu
This menu contains miscellaneous configuration items including device identification, date and
time, exporting and importing your cooling unit configuration options, the three links at the
bottom left of the screen, and consolidating data for troubleshooting purposes.
Identification screen
Path: Main > Configuration > General > Identification
Define the Name, the Location (the physical location), and the Contact (the person
responsible for the device) used by
The Name and Location fields also identify the device when you register for the Remote
Monitoring Service.
Date/Time screen
Path: Main > Configuration > General > Date/Time > Mode
Set the time and date used by the cooling unit. You can change the current settings manually or
through a Network Time Protocol (NTP) Server:
With both, you select the Time Zone. This is your local time difference with Coordinated
Universal Time (UTC), also known as Greenwich Mean Time (GMT).
• Override Manual NTP Settings: If you select this, data from other sources (typically
DHCP) take precedence over the NTP configurations you set here.
• Primary NTP Server: Enter the IP address or domain name of the primary NTP server.
• Secondary NTP Server: Enter the IP address or domain name of the secondary NTP
server, when a secondary server is available.
• Update Interval: Define, in hours, how often the cooling unit accesses the NTP Server
for an update. Minimum: 1; Maximum: 8760 (1 year).
• Update Using NTP Now: Initiate an immediate update of the date and time by the NTP
Server.
Path: Main > Configuration > General > Date /Time > Daylight Savings
Daylight Saving Time (DST) is disabled by default. You can enable traditional United States
DST, or enable and configure a customized daylight saving time to match how Daylight Saving
Time is implemented in your local area.
When customizing DST, the system puts the clock forward by an hour when the time and date
you specify under Start is reached and puts the clock back an hour when the time and date you
specify under End is reached.
• If your local DST always starts or ends on the fourth occurrence of a specific weekday of
a month (e.g., the fourth Sunday), choose Fourth/Last. If a fifth Sunday occurs in that
month, you should still choose Fourth/Last.
• If your local DST always starts or ends on the last occurrence of a specific weekday of a
month, whether it is the fourth or the fifth occurrence, choose Fifth/Last.
To reconfigure a link, click the link name in the Name column. You can reset the links to their
defaults at any time by clicking on Reset to Defaults.
Syslog Server. Uses IPv4/ IPv6 addresses or host names to identify from one to four servers to
receive Syslog messages sent by the cooling unit.
Port. The user datagram protocol (UDP) port that the cooling unit will use to send Syslog
messages. The default UDP port assigned to Syslog is 514.
Syslog settings
Path: Main > Configuration > Logs > Syslog > Settings
Message Generation. Enable the generation and the logging of Syslog messages for events
that have Syslog configured as a notification method.
Facility Code. Selects the facility code assigned to the Syslog messages of the cooling unit
(User, by default).
NOTE: User best defines the Syslog messages sent by the cooling unit. Do not change this
selection unless advised to do so by the Syslog network or system administrator.
Select a severity to assign to the test message and then define the test message. Format the
message to consist of the event type (for example, APC, System, or Device) followed by a
colon, a space, and the event text. The message can have a maximum of 50 characters.
• The priority (PRI): the Syslog priority assigned to the message event, and the facility
code of messages sent by the cooling unit.
• The Header: a time stamp and the IP address of the cooling unit.
• The message (MSG) part:
• The TAG field, followed by a colon and space, identifies the event type.
• The CONTENT field is the event text, followed (optionally) by a space and the event
code.
Example: APC: Test Syslog is valid.
Event log
By default, the log displays all events recorded during the last two days, starting with the latest
events.
Additionally, the log records any event that sends an SNMP trap, except SNMP authentication
failures, and abnormal internal system events.
You can enable color coding for events on the Main > Configuration > Security > Local
Users Management screen.
To open the log in a text file or to save the log to disk, click on the floppy disk icon( ) on the
same line as the Event Log heading.
You can also use FTP or Secure CoPy (SCP) to view the event log. See “How to use
FTP or SCP to retrieve log files” on page 49.
Filtering event logs. Use filtering to omit information you don’t want to display.
• Filtering the log by date or time: Use the Last or From radio buttons. (The filter
configuration is saved until the cooling unit restarts.)
• Filtering the log by event severity or category:
– Click Filter Log.
– Clear a check box to remove it from view.
– After you click Apply, text at the upper right corner of the Event Log page indicates
that a filter is active. The filter is active until you clear it or until the cooling unit
restarts.
• Removing an active filter:
– Click Filter Log.
– Click Clear Filter (Show All).
– As Administrator, click Save As Default to save this filter as the new default log view
for all users.
• Events are processed through the filter using OR logic. If you apply a filter, it works
regardless of the other filters.
• Events that you cleared in the Filter By Severity list never display in the filtered Event
Log, even if selected in the Filter by Category list.
• Similarly, events that you clear in the Filter by Category list never display in the filtered
Event Log.
Deleting event logs. To delete all events, click Clear Log. Deleted events cannot be retrieved.
To disable the logging of events based on their assigned severity level or their event
category, see “Configuring event actions” on page 35.
Since domain names generally change less frequently than IP addresses, enabling reverse
lookup can improve the ability to identify addresses of networked devices that are causing
events.
Reverse lookup is disabled by default. You should not need to enable it if you have no DNS
server configured or have poor network performance because of heavy network traffic.
CAUTION: When you resize the event log in order to specify a maximum size, all existing log
entries are deleted. When the log subsequently reaches the maximum size, the older entries
are deleted.
Data log
Use the data log to display measurements about the cooling unit, the power input to the cooling
unit, and the ambient temperature of the cooling unit.
The steps to display and resize the data log are the same as for the event log, except that you
use menu options under Data instead of Events.
Filtering data logs. Use filtering to omit information you don’t want to display.
• Filtering the log by date or time: Use the Last or From radio buttons. (The filter
configuration is saved until the cooling unit restarts.)
• Filtering the log by event severity or category:
a. Click Filter Log.
b. Clear a check box to remove it from view.
c. After you click Apply, text at the upper right corner of the Data Log page indicates
that a filter is active. The filter is active until you clear it or until the cooling unit
restarts.
• Removing an active filter:
d. Click Filter Log.
e. Click Clear Filter (Show All).
f. As Administrator, click Save As Default to save this filter as the new default log
view for all users.
Deleting data logs. To delete all events, click Clear Data Log. Deleted events cannot be
retrieved.
NOTE: Because the interval specifies how often the data is recorded, the smaller the interval,
the more times the data is recorded and the larger the log file.
NOTE: JavaScript® must be enabled in your browser to use the graphing feature. Alternatively,
you can use FTP or SCP to import the data log into a spreadsheet application, and graph data
in the spreadsheet
Graph Data . Select the data items that correspond to the abbreviated column headings in the
data log to graph multiple data items. Hold down CTRL to select multiple items.
Graph Time. Select Last to graph all records or to change the number of hours, days, or weeks
for which data log information is graphed. Select a time option from the drop-down menu.
Select From to graph data logged during a specific time period.
NOTE: Enter time using the 24-hour clock format.
Launch Graph in New Window. Click Launch Graph in New Window to launch the data log
graph in a new browser window that provides a larger view of the graph.
• FTP Server: The IP address or host name of the server where the file will reside.
• User Name/Password: The user name with password required to send data to the
repository file. This user must also be configured to have read and write access to the
data repository file and the directory (folder) in which it is stored.
• File Path: The path to the repository file.
• Filename: The name of the repository file (an ASCII text file), e.g. datalog.txt. Any new
data is appended to this file: it does not overwrite it.
• Unique Filename: Select this check box to save the log as mmddyyyy_<filename>.txt,
where filename is what you specified in the Filename field above. Any new data is
appended to the file but each day has its own file.
• Delay n hours between uploads: The number of hours between uploads of data to the
file (max. 24 hours).
• Upon failure, try uploading every n minutes: The number of minutes between
attempts to upload data to the file after a failed upload.
– Up to n times: The maximum number of times the upload will be attempted after it
fails initially.
– Until upload succeeds: Attempt to upload the file until the transfer is completed.
Path: Main > Logs > Data > Size
Use Data Log Size to specify the maximum number of log entries.
CAUTION: When you resize the data log in order to specify a maximum size, all existing log
entries are deleted. When the log subsequently reaches the maximum size, the older entries
are deleted.
Firewall Logs
Path: Main > Logs > Firewall
If you create a firewall policy, firewall events will be logged here. For more information on
implementing a policy, see “Firewall Menus” on page 24.
The information in the log can be useful to help the technical support team solve problems. Log
entries contain information about the traffic and the rules action (allowed, discarded). When
logged here, these events are not logged in the main Event Log (see “Event log” on page 45).
A firewall log contains up to 50 of the most recent events. The firewall log is cleared when the
display reboots.
• The file reports all events or data recorded since the log was last deleted or, in the case
of the data log, truncated because it reached maximum size.
• The file includes information that the event log or data log does not display.
– The version of the file format (first field)
– The date and time the file was retrieved
– The Name, Contact, and Location values and IP address of the cooling unit
– The unique Event Code for each recorded event (event.txt file only)
– The cooling unit uses a four-digit year for log entries. You may need to select a four-
digit date format in your spreadsheet application to display all four digits.
If you are using the encryption-based security protocols, see “To use SCP to retrieve
the files” on page 49. If you are using unencrypted authentication methods for
security, see “To use FTP to retrieve the files” on page 49.
To use SCP to retrieve the files. Enable SSH on the cooling unit (see “Console screen” on
page 30“).
To use FTP to retrieve the files. To use FTP to retrieve the event.txt or data.txt file:
1. At a command prompt, type ftp and the IP address of the cooling unit, and press ENTER.
If the Port setting for the FTP Server option has been changed from its default (21),
you must use the non-default value in the FTP command.
For Windows-based FTP clients, use the following command, including spaces. (For
some FTP clients, you must use a colon instead of a space between the IP address
and the port number.)
ftp>open ip_address port_number
To set a non-default port value to enhance security for the FTP Server, see
“FTP server screen” on page 34. You can specify any port from 5001 to
32768.
2. Use the case-sensitive User Name and Password for the Super User/Administrator or
Device User to log on. For Administrator, apc is the default for the user name and
password. For the Device User, the defaults are device for user name and apc for
password.
3. Use the get command to transmit the text of a log to your local drive.
ftp>get event.txt
or
ftp>del data.txt
Display. Gives information about the display unit including the Name, Location, Application
Version, and OS Version.
Controller. Gives information about the controller including the Model Number, Serial
Number, Firmware Revision, and Hardware Revision.
Hardware Factory. This hardware information is useful for troubleshooting problems with your
cooling unit device. Management Uptime refers to the length of time this management
interface has been running continuously; that is, the length of time since the cooling unit has
been warm or cold started.
Application Module, APC OS (AOS), and APC Boot Monitor. This information is useful for
troubleshooting and for determining if updated firmware is available, www.apc.com/tools/
download.
• Name: The name of the firmware module. The APC AOS module is always named aos,
and the boot monitor module is always named bootmon.
• Version: The version number of the firmware module. Version numbers of the modules
may differ, but compatible modules are released together. Never combine application
modules and AOS modules from different releases.
NOTE: If the boot monitor module must be updated, a boot monitor module is included in
the firmware release. Otherwise, the boot monitor module that is installed on the card is
compatible with the firmware update.
• Date/Time: The date and time at which the firmware module was loaded.
Support screen
Path: Main > About > Support
With this option, you can consolidate various data in this interface into a single zipped file for
troubleshooting purposes and customer support. The data includes the event and data logs,
the configuration file, and complex debugging information.
Click Generate Logs to create the file and then Download. You are asked whether you want to
view or save the zipped file.
You can also search for devices already on the network by entering an IP range to define the
search. The Utility scans the IP addresses in the defined range and discovers cooling units that
already have a DHCP-assigned IP address.
For detailed information on the Utility, see the Knowledge Base on the support page
of the www.apc.com website and search for 3061 (the ID of the relevant article).
To use the DHCP Option 12 (AOS 5.1.5 or higher), see Knowledge Base ID
FA156110.
System requirements
The Device IP Configuration Wizard runs on Microsoft® Windows® 2000, Windows Server®
2003, Windows Server® 2012, and on 32- and 64-bit versions of Windows XP, Windows Vista,
Windows 2008, Windows 7, and Windows 8 operating systems.
The Device IP Configuration Wizard supports cards that have firmware version 3.0.x or higher
and is for IPv4 only.
Installation
To install the Device IP Configuration Wizard from a downloaded executable file
1. Go to http://www.apc.com/tools/download.
2. Download the Device IP Configuration Wizard.
3. Run the downloaded executable file.
When installed, the Device IP Configuration Wizard is available through the Windows Start
menu options.
1. Configure a cooling unit with the desired settings and export them.
2. Retrieve the .ini file from that cooling unit.
3. Customize the file to change the TCP/IP settings at least.
4. Use a file transfer protocol supported by the cooling unit to transfer a copy to one or
more other cooling units. For a transfer to multiple cooling units, use an FTP or SCP
script or the .ini file utility.
Each receiving cooling unit uses the file to reconfigure its own settings and then deletes it.
• Section headings and keywords (only those supported for the particular device from
which you retrieve the file): Section headings are category names enclosed in brackets
([ ]). Keywords, under each section heading, are labels describing specific cooling unit
settings. Each keyword is followed by an equals sign and a value (either the default or a
configured value).
• The Override keyword: With its default value, this keyword prevents the exporting of
one or more keywords and their device-specific values. For example, in the
[NetworkTCP/IP] section, the default value for Override (the MAC address of the
cooling unit) 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:
1. If possible, use the interface of a cooling unit to configure it with the settings to export.
(Directly editing the .ini file risks introducing errors).
2. To use FTP to retrieve config.ini from the configured cooling unit:
a. Open a connection to the cooling unit using its IP address:
ftp> open ip_address
b. Log on using the Super User/Administrator user name and password.
c. Retrieve the config.ini file containing the settings of the cooling unit:
ftp> get config.ini
The file is written to the folder from which you launched the FTP.
Customizing. You must customize the file before you transfer it to another cooling unit.
• From the user interface of the receiving cooling unit, select Configuration > General >
User Config File. Enter the full path of the file, or use Browse on your local PC.
• Use any file transfer protocol supported by the cooling units, i.e., FTP, FTP Client, SCP,
or TFTP. The following example uses FTP:
a. From the folder containing the copy of the customized .ini file, use FTP to log-in to
the cooling unit to which you are exporting the .ini file:
ftp> open ip_address
b. Export the copy of the customized .ini file to the root directory of the receiving
cooling unit:
ftp> put filename.ini
Transferring the file to multiple cooling units. Follow these steps:
1. Use FTP or SCP, but write a script that incorporates and repeats the steps used for
exporting the file to a single cooling unit.
2. Use a batch processing file and the .ini file utility.
See “Contents of the .ini file” on page 53 for information about which values are
overridden.
Because the overridden values are device-specific and not appropriate to export to other
cooling units, 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 they override. Do
not delete or change the line containing the section heading.
Related Topics
On Windows operating systems, instead of transferring .ini files, you can use the Device IP
Configuration Wizard to update the basic TCP/IP settings of the cooling unit and configure
other settings through its user interface.
Upgrading here means simply placing the module files on the cooling unit; there is no
installation required. Check regularly on http://www.apc.com/tools/download for any new
upgrades.
Module Description
1 boot monitor (bootmon) Roughly equivalent to the BIOS of a PC
2 American Power Conversion Operating System Can be considered the operating system of the
(AOS) cooling unit
3 application Specific to the cooling unit device type
(Each module contains one or more Cyclical Redundancy Checks (CRCs) to protect its data
from corruption.)
The boot monitor module, the AOS, and the application file names share the same basic
format:
apc_hardware-version_type_firmware-version.bin
• apc: Indicates the context.
• hardware-version: “hw0n” where ‘n’ identifies the hardware version on which you can
use this file.
• type: Identifies which module.
• version: The version number of the file.
• bin: Indicates that this is a binary file.
• On a Windows operating system, use the Firmware Upgrade Utility downloaded from the
http://www.apc.com website.
• On any supported operating system, use FTP or SCP to transfer the individual AOS and
application firmware modules.
• For a cooling unit that is NOT on your network, use XMODEM through a serial
connection to transfer the individual firmware modules from your computer to the cooling
unit.
• Use a USB drive to transfer the individual firmware modules from your computer.
See “Use a USB drive to transfer and upgrade the files” on page 60.
Using the Utility for upgrades on Windows-based systems. On any supported Windows
operating system, the Firmware Upgrade Utility automates the transferring of the firmware
modules, in the correct module order.
Unzip the downloaded firmware upgrade file and double-click the .exe file. Then enter the IP
address, the user name, and the password in the dialog fields and click Upgrade Now. You can
use the Ping button to test your entered details.
See also “Using the Firmware Upgrade Utility for multiple upgrades on Windows” on
page 56.
Using the Utility for manual upgrades, primarily on Linux. On non-Windows operating
systems, the Firmware Upgrade Utility extracts the individual firmware modules but does not
upgrade the cooling unit.
1. After obtaining the files from the downloaded firmware upgrade file, run the Firmware
Upgrade Utility (the .exe file).
2. At the prompts, click Next, and then specify the directory location to which the files will
be extracted.
3. When the Extraction Complete message displays, close the dialog box.
• The cooling unit must be on the network, with its system IP, subnet mask, and default
gateway configured.
• The FTP server must be enabled at the cooling unit.
To transfer the files, perform these steps (this procedure assumes bootmon does not need
upgrading):
7. When FTP confirms the transfer, type quit to close the session.
8. After 20 seconds, repeat step 3 through step 7, using the application module file name
at step 6.
SCP. To use Secure CoPy (SCP) to upgrade firmware for the cooling unit, follow these steps
(this procedure assumes bootmon does not need upgrading):
1. Locate the firmware modules, see “Using the Utility for manual upgrades, primarily on
Linux.” on page 53.
2. Use an SCP command line to transfer the AOS firmware module to the cooling unit. The
following example uses nnn to represent the version number of the AOS module:
scp apc_hw06_aos_nnn.bin apc@158.205.6.185:apc_hw05_aos_nnn.bin
3. Use a similar SCP command line, with the name of the application module, to transfer
the application firmware module to the cooling unit. (Always upgrade the AOS before the
application module).
To transfer the files (this procedure assumes bootmon does not need upgrading):
1. Select a serial port at the local computer and disable any service that uses the port.
2. Connect the provided serial configuration cable (part number 940-0299) to the selected
port and to the serial port at the cooling unit.
3. Run a terminal program such as HyperTerminal, and configure the selected port for
57600 bps, 8 data bits, no parity, 1 stop bit, and no flow control.
4. Press the Reset button on the cooling unit, then immediately press the Enter key twice,
or until the Boot Monitor prompt displays: BM>
5. Type XMODEM, then press Enter.
6. From the terminal program’s 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.
(Always upgrade the AOS before the application module).
7. To install the application module, repeat step 5 and step 6. In step 6, use the application
module file name.
8. Type reset or press the Reset button to restart the cooling unit.
For information about the format used for firmware modules, see “Firmware module
files (InRow RC)” on page 57.
AOS=apc_hw06_aos_609.bin
APP=apc_hw06_acrc2g_609.bin
6. Place upload.rcf in the apcfirm folder on the flash drive.
7. Insert the flash drive into a USB port on your cooling unit.
8. Press the Display Reset button and wait for the card to reboot fully.
9. Check that the upgrade was completed successfully using the procedures in “Verifying
Upgrades”.
• Cooling unit Firmware Upgrade Utility on Windows. See “Using the Firmware
Upgrade Utility for multiple upgrades on Windows” on page 56.
• Use FTP or SCP. To upgrade multiple cooling units using an FTP client or using SCP,
write a script which automatically performs the procedure.
• Export configuration settings. You can create batch files and use a utility to retrieve
configuration settings from multiple cooling units and export them to other cooling units.
Utility is available from the Knowledge Base: http://www.apc.com/site/support/
index.cfm/faq/index.cfm.
Using the Firmware Upgrade Utility for multiple upgrades on Windows. After downloading
the Upgrade Utility from the cooling unit downloads page on the www.apc.com website, double
click on the exe file to run the utility (which ONLY works with IPv4) and follow these steps to
upgrade your cooling unit firmware:
1. In the utility dialog, type in an IP address, a user name, and a password, and choose the
Ping button if you need to verify the IP address.
2. Click the Device List button to open the iplist.txt file. Here you should type all cooling
unit devices to upgrade with the necessary information: IP, user name, and password.
For example,
SystemIP=192.168.0.1
SystemUserName=apc
SystemPassword=apc
Verifying Upgrades
Verify the success of the transfer
To verify whether a firmware upgrade succeeded, you can use the xferStatus command in the
command line interface to view the last transfer result. Alternatively, you can use an SNMP
GET to the mfiletransferStatusLastTransferResult OID.
See “SNMP screens” on page 31, “SNMP trap receiver screen” on page 39,
and “SNMP traps test screen” on page 40.
Traps received at an See your NMS documentation to verify that the traps are properly integrated in
NMS are not the alarm/trap database.
identified
© Schneider Electric, APC and the APC logo are owned by Schneider Electric Industries S.A.S., or its affiliated
companies. All other trademarks are property of their respective owners.
990-5567-001 1/2014