The information presented in this manual is not warran ted by the APC by Schn eider Electric to be auth orit ative,
error free, or complete. This publication is not meant to be a substitute for a detailed operational and site
specific development plan. Therefore, APC by Schneider Electric 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 APC by
Schneider Electric. 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 APC BY SCHNEIDER ELECTRIC, OR ANY PARENT, AFFILIATE OR SUBSIDIARY
COMPANY OF APC BY SCHNEIDER ELECTRIC 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 APC BY SCHNEIDER ELECTRIC HAS BEEN EXPRESSLY ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. APC BY SCHNEIDER ELECTRIC 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 right s in the content (including bu t not limited to soft ware, audio,
video, text, and photographs) rests with APC by Schneider Electric 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.
The APC by Schneider Electric Switched Rack Power Distribution Unit (PDU) may be used as a stand-alone,
network-manageable power distribution device or up to four devices can be connected together using one
network connection. The Rack PDU provides real-time remote monitoring of connected loads. User-defined
alarms warn of potential circuit overloads. The Rack PDU provides full control over outlets through remote
commands and user interface settings.
Your Rack PDU comes with a terminator installed in the display In or Out port. In stand-alone operation of
Switched Rack PDU models, one terminator must be installed in the display In or Out port. To use Network Port
Sharing between up to four units, a terminator must be installed in the In port at one end of the group and
another on the Out port at the other end of the group.
You can manage a Rack PDU through its Web User Interface (Web UI), its Command Line Interface (CLI),
StruxureWare, or Simple Network Management Protocol (SNMP). (To use the PowerNet MIB with an SNMP
browser, see the PowerNet SNMP Management Information Base (MIB) Reference Guide, available at
www.apc.com.) Rack PDUs have these additional features:
• Device power, peak power, apparent power, power factor and energy.
• Phase voltage, current, peak current, power, apparent power and power factor.
• Bank current and peak current (for models that support breaker banks).
• Configurable alarm thresholds that provide network and visual alarms to help avoid overloaded
circuits.
• Various levels of access: Super User, Administrator, Device User, Read-Only, Outlet User, and
Network-Only User (These are protected by user name and password requirements).
• Multiple user login feature which allows up to four users to be logged in simultaneously.
• Individual outlet control.
• Configurable power delays.
• Event and data logging. The event log is accessible by Telnet, Secure CoPy (SCP), File Transfer
Protocol (FTP), serial connection, or web browser (using HTTPS access with SSL, or using HTTP
access). The data log is accessible by web browser, SCP, or FTP.
• Email notifications for Rack PDU and Network Management Card (NMC) system events.
• SNMP traps, Syslog messages, and email notifications based on the severity level or category of
the Rack PDU and NMC system event.
• Security protocols for authentication and encryption.
• Network Port Sharing (NPS). Up to four Rack PDUs of any model can be connected using the In
and Out ports so that only one network connection is necessary.
• NPS guest firmware auto-update feature allows the NPS host to automatically pass a firmware
update to its connected guests. This feature will be functional for all guests that have AOS
firmware version 6.1.3 or later.
• RF Code wireless monitoring support via serial port connection
• Cisco EnergyWise certified.
NOTE: The Rack PDU does not provide power surge protection. To ensure that the device is protected from
power failure or power surges, connect the Rack PDU to a Schneider Electric Uninterruptible Power Supply
(UPS).
1Switched Rack PDU AP89XX User Guide
Types of User Accounts
The Rack PDU has various levels of access (Super User, Administrator, Device User, Read-Only User, Outlet
User, and Network-Only User), which are protected by user name and password requirements. Up to four
users are allowed to login to the same Rack PDU simultaneously (available in AOS version 6.1.3 or later).
• An Administrator or the Super User can use all of the menus in the Web UI and all of the
commands in the CLI. Administrator user types can be deleted, but the Super User cannot be
deleted.
The default user name and password for the Super User are both apc.
–The Super User or Administrator can manage another Administrator's account (enable,
disable, change password, etc).
• 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.
• A Read-Only User has the following restricted access:
– Access to the same menus as a Device User, 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 to clear the log.
• An Outlet User has the following restricted access:
– Access through the Web User Interface and Command Line Interface.
– Access to the same menus as a Device User, but with limited capability to change
configurations, control devices, delete data, or use file transfer options. Links to configuration
options are visible but are disabled. The Outlet User has access to the Outlet Control menu
option that allows the user to control only the outlets assigned by the Administrator. Outlet
Users cannot clear the event or data logs. The user name and password are defined by the
Administrator during the process of adding a new Outlet User.
• A Network-Only User can only log on using the Web UI and CLI (telnet, not serial). A networkonly user has read/right access to the network rela te d men us only.
Watchdog Features
Overview
To detect internal problems and recover from unanticipated inputs, the Rack PDU uses internal, system-wide
watchdog mechanisms. When it restarts to recover from an internal problem, a Network Interface Restarted
event is recorded in the event log.
Network interface watchdog mechanism
The Rack PDU implements internal watchdog mechanisms to protect itself from becoming inaccessible over
the network. For example, if the Rack PDU does not receive any network traffic for 9.5 minutes (either direct
traffic, such as SNMP, or broadcast traffic, such as an Address Resolution Protocol [ARP] request), it assumes
that there is a problem with its network interface and restarts. The network interface watchdog mechanism is
only enabled on a PDU that discovers an active network inte rf ac e co nn ec tio n at start-up. T his allows guest
PDUs in a Network Port Sharing chain to function normally without rebooting every 9.5 minutes.
Resetting the network timer
To ensure that the Rack PDU does not restart if the network is quiet for 9.5 minutes, the Rack PDU attempt s to
contact the default gateway every 4.5 minutes. If the gateway is present, it responds to the Rack PDU, and the
response restarts the 9.5-minute timer. If your application does not require or have a gateway, specify the IP
address of a computer that is running on the network and is on the same subnet. The network traffic of that
computer will restart the 9.5-minute time frequently enough to prevent the Rack PDU from restarting.
Switched Rack PDU AP89XX User Guide2
Network Port Sharing (NPS)
About the Network Port Sharing Feature
You can use the Network Port Sharing feature to view the status of and configure and manage up to four Rack
PDUs using only one network connection. This is made possible by connecting the Rack PDUs via the In and
Out ports on the Rack PDU front panel.
NOTE: All Rack PDUs in the group must be using the same Rack PDU firmware revision, 5.1.5 or later
(excluding v6.0.5 EnergyWise), in order to support the Network Port Sharing Feature.
Display ID
The display ID is a number, 1 to 4, used to un iquely identify the Rack PDUs in a group. After two or more Rack
PDUs are connected to one another in an NPS group, they can be identified on the various interfaces by the
use of this "Display ID". This Display ID is viewable in the top left corner of the display. Alternatively, a larger
Display ID “shadow” can be enabled on the LCD by selecting the Display Settings > Display ID > Show option
on the LCD keypad.
Installation Instructions
Connect up to four Rack PDUs via the In and Out ports on the Rack PDU. Insert an RJ45 terminator (in cluded)
in the unused In/Out ports on each end of the chain.
NOTE: Failure to use terminators may cause a loss of communication on the Rack PDUs.
NOTE: To reduce the possibility of communication issues, the maximum total length of cabling connecting
Rack PDUs in a group should not exceed 10 meters. All Rack PDUs in a NPS group should reside in the same
rack enclosure.
Connect the "Network" port of one of the grouped Rack PDUs to a network hub or switch. This unit will be the
Host for the Rack PDU group. Guest PDU data will be viewable on the Host PDU. Set up network functionality
for this Host Rack PDU as specified in the Establish Network Settings section. The Host will automatically
discover any Guest PDUs connected via In/Out ports. The Rack PDU group is now available via the Host's IP
address.
NOTE: Only one Rack PDU in an NPS group is allowed to be the host. If two host Rack PDUs are connected
together, one will automatically be chosen to be the single host for the NPS group. The user also has the
option to select a particular guest to be the host as long as that guest has an active network link.
The host Rack PDU supports many features that are not supported b y NPS guest s. These includ e, but are not
limited to:
• SNMP rPDU2Group OIDs
• EnergyWise support
• Initiating AOS/App firmware updates for guest Rack PDUs
• Time synchronization for guest Rack PDUs
• Data logging for the guest Rack PDUs
Specific assignment of Display IDs
Follow the instructions below before powering up any of the Rack PDUs in the group.
If it is desired to have a specific assignment of Display IDs, this can be achieved by powering up the units for
the first time in the desired order, 1 to 4. For example, before powering up any of the Rack PDUs connected in
a group, determine the Display ID order that you wou ld like. Then, first power up the unit that you would like to
have Display ID 1. After that unit has initialized and the LCD has started displaying its screens, power on the
unit that you would like to have Display ID 2. Continue in the same way for units 3 and 4, if applicable for your
setup.
NOTE: The Display ID can be configured from the Web User Interface via the "Configuration > RPDU > Device
> Display ID" field. The Display ID can also be configured from the CLI interface via the dispID command.
3Switched Rack PDU AP89XX User Guide
Firmware Upgrade with NPS
At start-up and routinely during operation, the rPDU2g NPS host compares its own AOS and application
versions with the versions found on each guest. In the event of a version difference, the host copies its AOS
and then its application to the non-complying guests via the NPS chain.
NOTE: Automatic firmware upgrade is only available for Rack PDUs running AOS version v6.1.3 or later as
this functionality requires resident firmware support in the NPS host and guest s. This functionality requires that
any replacement Rack PDUs also be running AOS version v6.1.3 or later to maintain correct operation of the
NPS chain.
RF Tag
The Rack PDU supports the RF Code sensor tag for Schneider Electric Rack PDUs. The tag enables data
center managers to wirelessly monitor power consumption and utilization with the enterprise-class Asset RF
Code Zone Manager. The Zone Manager middleware consumes information about power attribute values as
reported by the Rack PDU. The RF Code sensor tag for Schneider Electric works in concert with the Rack
PDUs with firmware v6.1.0 or later. To implement an RF Code sensor tag solution, plug the tag into the RJ-12
socket labeled Serial Port. Scroll the LCD menu to highlight the RF Code Control entry, press the Select
button. Press the select button again to enable. The Rack PDU will immediately reboot and start serial
communication with the tag. When an NPS guest RF tag is removed, the NPS host will signal an alarm. In
order to clear this alarm, one must replace the tag and disable the tag in the LCD menu. Then the error will be
cleared and the NPS guest will auto reboot.
The RF Tag reports per-phase load voltage/amperage/power readings every 10 minutes and device power/
energy use, per-outlet watt-hour/switch state/RMS current, and phase outlet voltages/bank overload state
readings every hour. Outlet an d bank readings are Rack PDU model dependent as all models do not support
monitoring. The complete RF solution requires an RF Code reader, an RF Code Zone Manager, or RF Code
Asset Manager. For more information see: www.rfcode.com.
EnergyWise
The Rack PDU has the capability of becoming a Cisco EnergyWise Entity. This entity reports power usage and
alarms in the EnergyWise Domain.
To exercise this capability, plug the Rack PDU network port into a Cisco switch/router that supports the
EnergyWise Domain. Log into the Web User Interface of the Rack PDU and navigate to the Configuration/RPDU/EnergyWise web page. Click on the enable radio button to initiate the task. The task will generate
unique parent and children names, default roles, keywords and importance values that comply with
EnergyWise requirements. Customization of the aforementioned is supported by clicking on any of the
underlined entities to navigate to a configuration web page.
The EnergyWise port, domain name and shared secret may also be modified, but must be coord inated with the
same parameters in the Cisco gear.
The Rack PDU implementation supports a single p arent, multiple children h ierarchy. The parent may exist as a
standalone Rack PDU or as the host Rack PDU for an NPS chain of Rack PDUs. The parent usage reports the
power consumed by the Rack PDUs themselves, including any NPS guest Rack PDUs. The children report
either inlet power or, in the case of monitored outlets, the power consumed at the outlet. Both parent and
children report a usage level (0-10 scale). The parent and inlet usage are always reported as 10 or “ On”. In the
case of switched outlets the actual state of the switch is reported and m ay also be altered by the Cisco device.
When the parent is the host Rack PDU of an NPS chain, the reported parent power is the sum of the parent
and each of the NPS guests. The parent also reports an inlet entity for itself and for each guest as well as an
outlet entity for each host outlet and each outlet of every guest.
The remaining configurable items are string variables that ma y be modified as needed and are ret ained acro ss
power cycles or reboots.
Switched Rack PDU AP89XX User Guide4
EnergyWise and NPS
RPDUs support Cisco EnergyWise with Rack PDU v6.0.9 firmware or later. The Rack PDU EnergyWise
application generates a family tree at startup. This tree is reported to Cisco hardware during the discovery
process.
For an initial installation, either establish the NPS chain and enable EnergyWise on the host or enable
EnergyWise on the host and then disable and re-enable EnergyWise after the NPS communication is
established. Clearly, the first option is simpler.
For Rack PDU replacement, the following procedure should be followed. Power down the Rack PDU – any
children associated with this Rack PDU will report EW levels and usage as zero. On the Status/Rack PDU/Group web page, there should be a check box to allow the user to remove the now non-functio ning Rack PDU
from the NPS chain. Once removed from the chain, any children associated with that Rack PDU will report “.0.”
in the display identifier portion of the EW name field. At this time, one can replace the Rack PDU with another
of the same model and expect the EnergyWise to function properly again once communication is established.
If for some reason the replacement model is different, EnergyWise will have to be disabled and re-enabled
after NPS communication is established, to upda te the family tree and the order of data reported. For more
information see: www.cisco.com/en/us/products/ps10195/index.html.
Getting Started
To start using the Rack PDU:
1. Install the Rack PDU using the Rack Power Distribution Unit Installation Instructions that were
shipped with your Rack PDU.
2. Apply power and connect to your network. Follow the directions in the Rack Power Distribution Unit Installation Instructions.
3. Establish network settings
4. Begin using the Rack PDU by way of one of the following:
– “Web User Interface” on page 88
– “Command Line Interface” on page 17
– “Rack PDU Front Panel” on page 10
5Switched Rack PDU AP89XX User Guide
Establish Network Settings
IPv4 initial setup
You must define three TCP/IP settings for the Rack PDU before it can operate on the network:
• The IP address of the Rack PDU
• The subnet mask of the Rack PDU
• The IP address of the default gateway (only needed if you are going off segment)
NOTE: If a default gateway is unavailable, use the IP address of a computer tha t is located on the
same subnet as the Rack PDU and is usually running. The Rack PDU used the default ga teway to
test the network when traffic is very light.
NOTE: Do NOT use the loopback address (127.0.0.1) as the default gateway. Doing so disables the card. To
enable again, you must log on using a serial connection and reset the TCP/IP settings to their defaults.
For detailed information on how to use a DHCP server to configure the TCP/IP settings at an Rack PDU,
see.“DHCP response options” on page 119
IPv6 initial setup
IPv6 network configuration provides flexibility to accommodate your requirements. IPv6 can be used anywhere
an IP address is entered on this interface. You can configure manually, automatically, or using DHCP.
TCP/IP configuration methods
Use one of the following methods to define the TCP/IP settings needed by the Rack PDU:
• “Device IP Configuration Wizard” on page 148
• “DHCP and BOOTP configuration”
• “Command Line Interface” on page 17
.ini file utility
You can use the .ini file export utility to export .ini file settings from configured Rack PDUs to one or more
unconfigured Rack PDUs. For more information, see “Creating and importing settings with the config file” on
page 136.
DHCP and BOOTP configuration
The default TCP/IP configuration setting, DHCP, assumes that a properly configured DHCP server is available
to provide TCP/IP settings to Rack PDU. You can also configure the setting for BOOTP.
A user configuration (INI) file can function as a BOOTP or DHCP boot file. For more information, see “Creating
and importing settings with the config file” on page 136.
If neither of these servers is available, see “Device IP Configuration Wizard” on page 148 or “Device IP
Configuration Wizard” on page 148.
BOOTP: For the Rack PDU to use a BOOTP server to configure its TCP/IP settings, it must find a properly
configured RFC951-compliant BOOTP server.
In the BOOTPTAB file of the BOOTP server, enter the Rack PDU’s MAC address, IP address, subnet mask,
and default gateway, and, optionally, a bootup file name. Look for the MAC address on the bottom of the Rack
PDU or on the Quality Assurance slip included in the package.
When the Rack PDU reboots, the BOOTP server provides it with the TCP/IP settings.
• If you specified a bootup file name, the Rack PDU attempts to transfer that file from the BOOTP
server using TFTP or FTP. The Rack PDU assumes all settings specified in the bootup file.
• If you did not specify a bootup file name, you can configure the other settings of the Rack PDU
remotely through its “Web User Interface” on page 88 or “Command Line Interface” on page 17;
the user name and password are both apc, by default. To create a bootup file, see your BOOTP
server documentation.
Switched Rack PDU AP89XX User Guide6
DHCP: You can use an RFC2131/RFC2132-compliant DHCP server to configure the TCP/IP settings for the
Rack PDU.
This section summarizes the Rack PDU’s communication with a DHCP server. For more detail about how a
DHCP server can configure the network settings for a Rack PDU, see “DHCP response options” on page 119.
1. The Rack PDU sends out a DHCP request that uses the following to identify itself:
– A Vendor Class Id entifier (APC by default)
– A Client Identifier (by default, the MAC address of the Rack PDU)
– A User Class Identifier (by default, the identification of the app lication firmware inst alled on the
Rack PDU)
– A Host Name (by default, apcXXYYZZ with XXYYZZ being the last six digits of the PDU). This
is known as DHCP Option 12.
2. A properly configured DHCP server responds with a DHCP offer that includes a ll the settings that
the Rack PDU needs for network communication. The DHCP offer also includes the Vendor
Specific Information option (DHCP option 43). The Rack PDU can be configured to ignore DHCP
offers that do not encapsulate the APC cookie in DHCP option 43 using the following
hexadecimal format. (The Rack PDU does not requ ire this co ok ie by de fa u lt.)
Option 43 = 01 04 31 41 50 43
Where:
– The first byte (01) is the code.
– The second byte (04) is the length.
– The remaining bytes (31 41 50 43) are the APC cookie.
See your DHCP server documentation to add code to the Vendor Specific Information option.
NOTE: By selecting the Require vendor specific cookie to accept DHCP Address check
box in the Web User Interface, you can require the DHCP server to provide an “APC” cookie,
which supplies information to the Rack PDU.
Network Management with Other Applications
These applications and utilities work with a Rack PDU which is connected to the network.
• PowerNet
SETs and GETs and use SNMP traps
• StruxureWare — Provide enterprise-level power management and management of agents, Rack
PDUs, and environmental monitors.
• Device IP Configuration Utility — Configure the basic settings of one or more Rack PDU over the
network, see “Device IP Configuration Utility”
• Security Wizard — Create components neede d to help with security for the Rack PDUs wh en you
are using Secure Sockets Layer (SSL) and related protocols and encryption routines.
®
Management Information Base (MIB) with a standard MIB bro wser — Pe rform SNMP
7Switched Rack PDU AP89XX User Guide
Command Line Interface (CLI)
1. Log on to the CLI. See “Log on to the CLI” on page 17.
2. Contact your network administrator to obtain the IP address, subnet mask, and default gateway
for the Rack PDU.
3. Use these three commands to configure network settings. (Text in italics indicates a variable.)
For each variable, type a numeric value that has the format xxx.xxx.xxx.xxx.
For example, to set a system IP address of 156.205.14.141, type the following command and
press E
tcpip -i 156.205.14.141
4. Type exit. The Rack PDU restarts to apply the changes.
NTER:
Switched Rack PDU AP89XX User Guide8
Recovering from a Lost Password
You can use a local computer (a computer that connects to the Rack PDU or other device through the serial
port) to access the Command Line Interface.
1. Select a serial port at the local computer, and disable any service that uses that port. NOTE: If
your computer does not have a serial port, you will need to acquire a machine that has one or
purchase an adapter to fit your machine.
2. Connect the serial cable (Schneider Electric part number 940-0144A) to the selected port on the
computer and to the Serial port at the Rack PDU.
3. Run a terminal program (such as Tera Term
for 9600 bps, 8 data bits, no parity, 1 stop bit, and no flow control.
4. Press
5. Press the Reset button. The Status LED will flash alternately orange and green within 5 to 7
6. Press
7. At the Command Line Interface, use the following commands to change the Password setting,
ENTER, repeatedly if necessary, to display the User Name prompt. If you are unable to
display the
– 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.
seconds of pressing the Reset button. Press the Reset button a second time immediately when
the LED begins flashing to reset the user name and password to their defaults temporarily.
default, apc
the
User Name prompt is re-displayed, you must repeat step 5 and log on again.)
which is apc at this stage:
User Name prompt, verify the following:
ENTER, repeatedly if necessary, to display the User Name prompt again, then use the
, for the user name and passwo rd. (If you t ake lo nger tha n 30 second s to log on af te r
®
or HyperTerminal®) and configure the selected port
user -n <user name> -pw <user password>
For example, to change the Super User password to XYZ type:
user -n apc -cp apc -pw XYZ
8. Type quit or exit to log off, reconnect any serial cable you disconnected, and restart any
service you disabled.
9Switched Rack PDU AP89XX User Guide
Rack PDU Front Panel
Serial
In
Out
USB
Reset
Main
Menu
Select
Scroll
- Warning
- OK
- Overload
pdu0713a
MA
apc
MA
apc12345678
MA
pdu0714a
MA
Pha
Ne
MA
Temp/ Hum idi ty
SELECT
0
0
0
4.37 kW
MAIN
NOTE: Your Rack PDU is configured so the display backlight turns off after 10 minutes of inactivity. The
backlight can be turned on by depressing any button below the display.
ItemFunction
Network
x
pdu0711a
Display
Main Menu button
Scroll button
Select button
Shows information about the Rack PDU. In normal operation,
input voltage, current, and power refreshes every five seconds.
To reverse the text, select Display settings, scroll to Orientation
and press Select.
Device N
37.8%RH
24.5ºC
12345678
ame
SELECT
0
IN
0
24.5ºC
SELECT
37.8%RH
IN
Device Name
Press to view the Rack PDU electrical input.
SELECT
0
0
IN
1.23 kW
Press once to display the menu. Press
additional times to highlight the desired
menu option.
se Info
Outlet Current
SELECT
twork
IN
T em p/Humidity
With a menu option highlighted, press the
Select button to display Rack PDU
information. (Network information is shown
SELECT
at right.)
IPv4 Address
IN
10.234.576.89
pdu0712a
pdu0724a
pdu0715a
Switched Rack PDU AP89XX User Guide10
Serial
In
Out
Temp/ Hum idi ty
USB
Reset
Main
Menu
Select
Scroll
- Warning
- OK
- Overload
SELECT
0
0
0
4.37 kW
MAIN
Network
x
ItemFunction
Load Indicator LEDsIndicates the status of the Rack PDU load. See “Load Indicator
LED” on page 12.
Temp/Humidity portPort for connecting an optional Schneider Electric Temperature
Sensor (AP9335T) or an optional Schneider Electric
Temperature/Humidity Sensor (AP9335TH).
pdu0740a
In and Out ports
USB port
Outlet status LEDIlluminates green when the outlet is energized. (Eac h outlet has
For use with the Network Port Sharing feature.
For use with a flash drive for firmware upgrades - 5V @ 100ma.
an outlet LED.)
RJ-12 Serial PortPort for connecting the Rack PDU to a terminal emulator
program for local access to the Command Line Interface. Use
the supplied serial cable (Schneider Electric part number
940-0144A).
10/100 Base-T Connector
Network status LED
10/100 LED
Reset button
Connects the Rack PDU to the network.
See “Network Status LED” on page 12.
See “10/100 LED” on page 12.
Resets the Rack PDU without affecting the outlet status.
11Switched Rack PDU AP89XX User Guide
Network Status LED
ConditionDescription
One of the following situations exists:
Off
Solid GreenThe Rack PDU has valid TCP/IP settings.
•The Rack PDU is not receiving input power.
•The Rack PDU is not operating properly. It may need to be repaired or
replaced. Contact Customer Support.
Solid Orange
Flashing GreenThe Rack PDU does not have valid
A hardware failure has been detected in the Rack PDU. Contact Customer
Support.
TCP/IP settings.
Flashing OrangeThe Rack PDU is making BOOTP requests.
Alternately flashing Green
and Orange
1. If you do not use a BOOTP or DHCP server, see “Establish Network Settings” on page 6 to configure the TCP/IP
settings of the Rack PDU.
2. To use a DHCP server, see “TCP/IP and Communication Settings” on page 118.
If the LED is flashing slowly, the Rack PDU is making DHCP
If the LED is flashing rapidly, the Rack PDU is starting up.
2
requests1.
10/100 LED
ConditionDescription
One or more of the following situations exists:
•The Rack PDU is not receiving input power.
•The cable that connects the Rack PDU to the network is disconnected or
Off
defective
•The device that connects the Rack PDU to the network is turned off.
•The Rack PDU itself is not o perating pr operly. It may need to be repaired or
replaced. Contact Customer Support.
Solid Green
The Rack PDU is connected to a network operating at 10 Me gabits per second
(Mbps).
Solid OrangeThe Rack PDU is connected to a network operating at 100 Mbps.
Flashing GreenThe Rack PDU is receiving or transmitting data packets at 10 Mbps.
Flashing OrangeThe Rack PDU is receiving or transmitting data packets at 100 Mbps.
Load Indicator LED
The load indicator LED identifies near-overload (warning) and overload (critical) conditions for the Rack PDU.
ConditionDescription
Solid GreenOK. No near-overload (warning) or overload (critical) alarms are present.
Solid Yellow
Flashing RedOverload. At least one overload (critical) alarm is present.
Warning. At least one near-overloa d (warning) alarm is present, but no
overload (critical) alarms are present.
Switched Rack PDU AP89XX User Guide12
Example 1
1. 14.1 A
2. 14.2 A
3. 14.3 A
SELECTMAIN
pdu0719a
Phase 2
208.0 V
14.2 A
1.23 kW
SELECTMAIN
Phase 3
208.0 V
14.3 A
1.23 kW
SELECTMAIN
SELECTMAIN
1
phase
Phase
Info
Phase
Outlets?
Y
e
s
No
Y
e
s
SELECTMAIN
Phase 1
208.0 V
14.1 A
1.23 kW
Input
208.0 V
14.1 A
SELECTMAIN
1.23 kW
pdu0780a
Temp/Humidity
Software Info
SKU/Serial #
SELECTMAIN
Phase Info
Display Settin gs
Network
SKU/SN
RF Code Control
RF Code
Log to Fla sh
NOTE: If there are more selections available than can be
shown on the display, they will appear on multiple pages.
Multiple pages are indicated by the arrow in the corner of
the screen.
NOTE: “T emp/Humidity” only appears when an AP9335T
or AP9335TH sensor is attached.
Display Tree
Main
Menu
Phase
Info
T/H
Network
SW Info
Disp
Settings
USB
Phase Current
Phase to
No
Voltage
L1 - 2: 208V
L2 - 3: 208V
L3 -1: 208 V
13Switched Rack PDU AP89XX User Guide
Example 2
pdu0710c
IPv4 Address
255.255.255.255
SELECTMAIN
Network
Sensor
Temp: 45.6ºC
Hum: 37.8%
SELECTMAINSELECTMAIN
Model
AP8XXX
Serial Nu m ber
ZAxxxxxxxxxx
SELECTMAIN
APP
Enabled
SELECTMAIN
Press “Select”
WILL REBOOT
IPv6 Address
1234:5678:9012
3456:7890:1234
5678:9012
SELECTMAIN
00 00 00
00 00 00
SELECTMAIN
LCD Contrast
5 / 9
Press “Select”
SELECTMAIN
MAIN
LCD Backlight
Auto-On
to switch
MAIN
Normal
to switch
Hide
SELECTMAIN
to switchto adjust
No
Yes
each IPv6 addr)
SELECTMAIN
Disp. Settings
SKU/SN
SW Info
T/H
SELECTMAIN
XX previous records
Display Tree
RF Code
Log to Flash
AOS
RF Code - Console
6.5.6
6.5.6
IPv6 Address
MAC Address
(scrolls through
LCD Orientation
Press “Select”
SELECT
Press “Select”
SELECT
Network Port
Sharing Group
Display ID
Press “Select”
Log to Fla sh
Press <select> to start export
Switched Rack PDU AP89XX User Guide14
Example 3
Main
Menu
pdu072 0a
2 bank
Yes
N
o
S
E
L
E
C
T
M
A
I
N
1
.
2
3
k
W
2
1
Sensor
N
o
S
E
L
E
C
T
M
A
I
N
1
.
2
3
k
W
2
1
3
3 bank
Yes
N
o
4 bank
Yes
N
o
5 bank
Yes
N
o
S
E
L
E
C
T
M
A
I
N
1
.
2
3
k
W
2
1
4
3
S
E
L
E
C
T
M
A
I
N
1
.
2
3
k
W
1
3
5
4
2
S
E
L
E
C
T
M
A
I
N
1
.
2
3
k
W
1
3
5
4
2
6
6 bank
Yes
S
E
L
E
C
T
M
A
I
N
0
0
1
.
2
3
k
W
MAIN
Monitor Status
Yes
0
.
2
4
5
º
C
.
7
3
8
%
H
R
c
e
a
m
v
i
N
e
D
c
1
a
p
M
A
N
I
e
8
7
6
4
5
2
3
T
C
E
L
E
S
15Switched Rack PDU AP89XX User Guide
Example 4
S
E
L
E
C
T
M
A
I
N
0
2
4
.
5
º
C
3
7
.
8
%
R
H
D
e
v
i
c
e
N
a
m
e
a
p
c
1
2
3
4
5
6
7
8
S
E
L
E
C
T
M
A
I
N
1
.
2
3
k
W
1
3
5
4
2
6
S
E
L
E
C
T
M
A
I
N
0
0
1
.
2
3
k
W
S
E
L
E
C
T
M
A
I
N
5
.
6
7
k
W
1
3
5
4
2
6
S
E
L
E
C
T
M
A
I
N
5
9
.
0
º
C
3
0
.
0
%
R
H
D
e
v
i
c
e
N
a
m
e
a
p
c
1
2
3
4
5
6
7
8
Normal Status
Indicator
Reading
Warning
(Near O verload)
Indicator
Critical
(Overload)
Indicator
Normal Status
Indicator
Threshold
Violation
Indicator
V
Monitor Status Indicators
NOTE: Both warning and critical temperature threshold violations will display as “High Temp”. Both warning
and critical humidity threshold violations will display as “Low Humidity”. The icon in the upper left corner of
the display interface is the indicator of either a warning or critical event. You must have installed an optional
APC by Schneider Electric Temperature/Humidity Sensor (AP9335TH) to your Rack PDU in order to use the
Humidity related status screens.
Device Load
Bank Load Graphs
(No Indicator = No rmal Status)
Warning
7
.
8
9
k
W
1
2
3
4
5
6
M
N
A
I
S
E
L
E
C
T
Most Critical
Sensor Status
p
e
h
T
g
m
i
H
Critical
Threshold
iolation
Indicator
D
a
p
A
M
m
i
u
d
y
i
H
t
L
w
o
.
C
2
5
4
º
H
0
.
1
0
R
%
N
a
e
m
e
c
v
i
e
6
7
8
4
5
3
2
c
1
N
I
C
L
T
E
E
S
pdu072 1a
Switched Rack PDU AP89XX User Guide16
Command Line Interface
About the Command Line Interface (CLI)
You can use the Command Line In terface to view the status of and configure a nd manag e the Rack PDU ( and
any connected Rack PDUs, if using the Network Port Sharing Feature). In addition, the Command Line
Interface enables you to create scripts for automated operation. You can configure all parameters of a Rack
PDU (including those for which there are not specific CLI commands) by using the CLI to transfer an INI file to
the Rack PDU. The CLI uses XMODEM to perform the transfer, however, you cannot read the current INI file
through XMODEM.
Log on to the CLI
To access the Command Line Interface, you can use either a local (serial) connection or a remote (Telnet or
SSH) connection with a computer on the same network as the Rack PDU.
Remote access to the Command Line Interface
You can choose to access the Command Line Interface through Telnet and/or SSH. Telnet is enabled by
default. You do not have to enable either.
To enable or disable these access methods, use the Web User Interface. On the Configuration tab, select
Network from the menu to open the Console Access page. Click to check the desired Enable box. Click
Apply to save your changes or Cancel to leave the page.
17Switched Rack PDU AP89XX User Guide
Telnet for basic access
Telnet provides the basic security of authentication by user name and password, but not the high-security
benefits of encryption.
To use Telnet to access the Command Line Interface:
1. From a computer that has access to the network on which the Rack PDU is installed, at a
command prompt, type telnet and the IP address for the Rack PDU (for example, telnet
139.225.6.133, when the Rack PDU uses the default Telnet port of 23), and press
If the Rack PDU uses a non-default port number (from 5000 to 327 68 ), you must in clu de a colon
or a space, depending on your Telnet client, between the IP address (or DNS name) and the port
number. (These are commands for general usage: Some clients do not allow you to specify the
port as an argument and some types of Linux might want extra commands).
2. Enter the user name and password (by default, apc and apc for the Super User).
If you cannot remember your user name or p assword, see “Recover ing from a Lost Password” on
page 9.
ENTER.
SSH for high-security access
If you use the high security of SSL for the Web interface, use SSH for access to the Command Line Interface.
SSH encrypts user names, passwords, and transmitted data. The interface, user accounts, and user access
rights are the same whether you access the Command Line Interface through SSH or Telnet, but to use SSH,
you must first configure SSH and have an SSH client program installed on your computer.
Local access to the Command Line Interface
For local access, use a computer that connects to the Rack PDU through the serial port to access the
Command Line Interface:
1. Select a serial port at the computer and disable any service that uses that port.
2. Connect the serial cable (Schneider Electric part number 940-0144A) from the selected serial
port on the computer to the Serial port on the Rack PDU.
3. Run a terminal program (e.g., Tera Term or HyperTerminal) and configure the selected port for
9600 bps, 8 data bits, no parity, 1 stop bit, and no flow control.
4. Press
ENTER. It may take mu ltiple (up to thr ee) attempt s to get a prompt to a ppear. At the prompt,
enter your user name and password.
Switched Rack PDU AP89XX User Guide18
About the Main Screen
Schneider Electric Network Management Card AOS vx.x.x
(c) Copyright 2018 All Rights Reserved RPDU 2g vx.x.x
-------------------------------------------------------------------------Name : Test Lab Date : 5/30/2018
Contact : Don Adams Time : 5:58:30
Location : Building 3 User : Administrator
Up Time : 0 Days, 21 Hours, 21 Minutes Stat : P+ N4+ N6+ A+
Type ? For command listing
Use tcpip for IP address (-i), subnet (-s), and gateway (-g)
APC>
Following is an example of the main screen, which is disp lay ed when you log on to the Com m a nd Line
Interface of a Rack PDU.
• Two fields identify the operating system (AOS) and application (APP) firmware versions. The
application firmware name identifies the type of device that connects to the network. In the
example above, the application firmware for the Rack PDU is displayed.
Network Management Card AOSvx.x.x
RPDU 2g vx.x.x
• Three fields identify the system name, contact person, and location of the Rack PDU.
Name : Test Lab
Contact : Don Adams
Location : Building 3
• An Up Time field reports how long the Rack PDU Management Interface has been running since
it was last turned on or reset.
Up Time: 0 Days, 21 Hours, 21 Minutes
• Two fields identify when you logged in, by date and time.
Date: 05/30/2018
Time: 5:58:30
• The
• A
User field identifies whether you logged in through th e Super User , Administrator or Device
Manager account.
User: Administrator
Stat field reports the Rack PDU status.
Stat:P+ N4+ N6+ A+
P+ The APC operating system (AOS) is functioning properly.
IPv4
only
N+ N+N4+ N6+The network is functioning properly.
N? N6? N4? N6?A BOOTP request cycle is in progress.
N– N6- N4- N6-The Rack PDU failed to connect to the network.
IPv6
only
IPv4 and
IPv6*
Description
N! N6! N4! N6!Another device is using the Rack PDU IP address.
* The N4 and N6 values can be different from one another: you could, for
example, have N4- N6+.
19Switched Rack PDU AP89XX User Guide
A+The application is functioning properly.
A–The application has a bad checksum.
A?The application is initializing.
A!The application is not compatible with the AOS.
NOTE: If P+ is not displayed, contact the Schneider Electric Customer Care Center.
Using the CLI
At the Command Line Interface, you can use comma nds to configure the Rack PDU. To use a command, type
the command and press
Options are case-sensitive.
While using the Command Line Interface, you can also do the following:
• Type ? and press
• To obtain information about the purpose and syntax of a specified command, type the command,
a space, and ? or the word help. For example, to view RADIUS configuration options, type:
radius ?
or
radius help
• Press the
the
UP and DOWN arrow keys to scroll through a list of up to ten previous c omm an d s.
• Type at least on e letter of a command and press the
commands that match the text you typed in the command line.
• Type exit or quit to close the connection to the Command Line Interface.
ENTER. Commands and arguments are valid in lowercase, upperca se, or mixed case.
ENTER to view a list of available commands, based on your account type.
UP arrow key to view the command that was entered most recently in th e session. Use
TAB key to scroll through a list of valid
Switched Rack PDU AP89XX User Guide20
Command Syntax
ItemDescription
-Options are preceded by a hyphen.
< >
[ ]
|
Example of a command that supports multiple options:
ftp [-p <port number>] [-S <enable | disable>]
In this example, the ftp command accepts the option -p, which defines the port number, and the option -S,
which enables or disables the FTP feature.
To change the FTP port number to 5010, and enable FTP:
Definitions of options are enclosed in angle brackets. For example:
-dp <device password>
If a command accepts multiple options or an option accepts mutually
exclusive arguments, the values may be enclosed in brackets.
A vertical line between items enclosed in brackets or angle bracket s indicates
that the items are mutually exclusive. You must use one of the items.
1. Type the ftp command, the port option, and the argument 5010:
ftp -p 5010
2. After the first command succeeds, type the ftp command, the enable/disable option, and the
enable selection:
ftp -S enable
Example of a command that accepts mutually exclusive arguments for an option:
alarmcount -p [all | warning | critical]
In this example, the option -p accepts only three arguments: all, warning, or critical. For example, to view the
number of active critical alarms, type:
alarmcount -p critical
The command will fail if you type an argument that is not specified.
21Switched Rack PDU AP89XX User Guide
Command Response Codes
The command response codes enable scripted operations to detect error conditions reliably without having to
match error message text:
The CLI reports all command operations with the following format:
E [0-9] [0-9] [0-9] : Error message
CodeMessageCodeMessage
E000SuccessE200Input Error
E001Successfully IssuedE201No Response
E002Reboot required for change to take effectE202User already exists
E100Command failedE203User does not exist
E101Command not foundE204User does not have access to this
command
E102Parameter ErrorE205Exceeds Maximum Users
E103Command Line ErrorE206Invalid value
E104User Level DenialE207Outlet Command Error: Device not