Schneider Electric AP88XX Users Manual
User Guide
Rack Power Distribution Unit
Metered
AP88XX
990-5568A-001
Publication Date: May, 2015
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 ha s bee n compiled in g ood faith b y Schneid er
Electric IT Corporation. However, no representation is made or warranty given, either express or implied, as to
the completeness or accuracy of the informati on this Pub lica tio n co ntains.
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 right s in the content (including bu t not limited to soft ware, 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 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Types of User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Watchdog Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Network interface watchdog mechanism . . . . . . . . . . . . . . . . . . . . . . . . 3
Resetting the network timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Network Port Sharing (NPS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
About the Network Port Sharing Feature . . . . . . . . . . . . . . . . . . . . . . . . 3
Display ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Specific assignment of Display IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Firmware Upgrade with NPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
RF Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
EnergyWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
EnergyWise and NPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Establish Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
IPv4 initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
IPv6 initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
TCP/IP configuration methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
.ini file utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
DHCP and BOOTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Network Management with Other Applications . . . . . . . . . . . . . . . . . . . 8
Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Recovering from a Lost Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Rack PDU Front Panel ............................................................11
Network Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10/100 LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Load indicator LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Display Tree Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Display Tree Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Command Line Interface........................................................ 16
About the Command Line Interface (CLI). . . . . . . . . . . . . . . . . . . . . . . 16
Log on to the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Remote access to the command line interface . . . . . . . . . . . . . . . . . . 16
Telnet for basic access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SSH for high-security access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Local access to the command line interface . . . . . . . . . . . . . . . . . . . . 17
About the Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Metered Rack PDU i
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Command Response Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Network Management Card Command Descriptions . . . . . . . . . . . . . 22
? or help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
alarmcount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
bye . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
clrrst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
dns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
eventlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
exit or quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
ftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
lang . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
lastrst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ledblink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
logzip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
portSpeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
resetToDef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
smtp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
snmpv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
snmptrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
tcpip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
tcpip6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
userdflt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
whoami . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
xferINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
xferStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Metered Rack PDU ii
Device Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Network Port Sharing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
bkLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
bkNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
bkOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
bkReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
devLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
devNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
devOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
devReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
dispID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
energyWise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
humHyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
humLow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
humMin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
humReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
lcd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
lcdBlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
phLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
phNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
phOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
phReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
phTophVolts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
prodInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
sensorName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
tempHigh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
tempHyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
tempMax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
tempReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Web Interface............................................................................61
Supported Web Browsers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Logging On to the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
URL address formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Web Interface Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Device status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Quick Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Network Port Sharing (NPS) on the Web User Interface (UI) . . . . . . 65
Group Control using Network Port Sharing . . . . . . . . . . . . . . . . . . . . . 65
About Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
The Overview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Metered Rack PDU iii
Status Tab ..................................................................................67
About the Status Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
View the Load Status and Peak Load . . . . . . . . . . . . . . . . . . . . . . . . . . 68
View the Network Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Current IPv4 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Current IPv6 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Domain Name System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Ethernet Port Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Control......................................................................................... 69
Managing User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Resetting the Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Configuration.............................................................................70
About the Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configure Load Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
To configure load thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configure RPDU Name and Location . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Reset Peak Load and kWh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configure Temperature and Humidity Sensors . . . . . . . . . . . . . . . . . . 72
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Session Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Ping Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configure the RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Supported RADIUS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
RADIUS and Network Port Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Firewall Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Network Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
TCP/IP and Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Port Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SNMPv1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configure event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
E-mail notification screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
SNMP trap receiver screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
SNMP traps test screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Remote Monitoring Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Metered Rack PDUiv
General Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Identification screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Date/Time screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Creating and importing settings with the config file . . . . . . . . . . . . . . 95
Configure Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Logs in the Configuration Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Identifying Syslog servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Syslog settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Syslog test and format example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Tests Tab .................................................................................... 98
Setting the RPDU LCD or LED Lights to Blink . . . . . . . . . . . . . . . . . . . 98
Logs Tab.....................................................................................99
Event, Data and Firewall Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Data log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Firewall Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Use FTP or SCP to retrieve log files . . . . . . . . . . . . . . . . . . . . . . . . . . 103
About Tab.................................................................................105
About the Rack PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Device IP Configuration Wizard.........................................106
Capabilities, Requirements, and Installation . . . . . . . . . . . . . . . . . . . 106
How to use the Wizard to configure TCP/IP settings . . . . . . . . . . . . 106
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
How to Export Configuration Settings..............................107
Retrieving and Exporting the .ini File . . . . . . . . . . . . . . . . . . . . . . . . . 107
Summary of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Contents of the .ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
.ini and Network Port Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Detailed procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
The Upload Event and Error Messages . . . . . . . . . . . . . . . . . . . . . . . 110
The event and its error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Messages in config.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Errors generated by overridden values . . . . . . . . . . . . . . . . . . . . . . . 110
Related Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
File Transfers...........................................................................111
Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Benefits of upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Firmware module files (Rack PDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Metered Rack PDU v
Firmware File Transfer Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Using the Firmware Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Use FTP or SCP to upgrade one Rack PDU . . . . . . . . . . . . . . . . . . . 113
Use XMODEM to upgrade one Rack PDU . . . . . . . . . . . . . . . . . . . . . 114
Use a USB drive to transfer and upgrade the files . . . . . . . . . . . . . 114
How to upgrade multiple RPDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Using the Firmware Upgrade Utility for multiple upgrades . . . . . . 115
Updating firmware for Network Port Sharing (NPS) Groups . . . . . 115
Verifying Upgrades and Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Verify the success or failure of the transfer . . . . . . . . . . . . . . . . . . . 116
Last Transfer Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Verify the version numbers of installed firmware. . . . . . . . . . . . . . . 116
Troubleshooting .....................................................................117
Rack PDU Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
SNMP Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Metered Rack PDUvi
Introduction
Product Features
The Schneider Electric Metered 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 with
one network connection. The Rack PDU provides real-time remote monitoring of connected loads.
User-defined alarms warn of potential circuit overloads.
Your AP88xx Metered Rack PDU comes with a terminator 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 interface (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.schneider-electric.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, 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.
• 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.
• E-mail notifications for Rack PDU and Network Management Card (NMC) system
events.
• SNMP traps, Syslog messages, and e-mail 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 gu est s 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).
1 Metered Rack PDU
Types of User Accounts
The Rack PDU has various levels of access (Super User, Administrator, Device User, Read-Only
User, a nd Network-Only User), which are protected by user name and p assword 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 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 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.
• A Network-Only User can only log on using the Web UI and CLI (telnet, not serial). A
network-only user has read/right access to the network related menus only.
Metered Rack PDU2
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 traff ic 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 and active
network interface connection at start-up. This allows guest PDUs in a Network Port Sh aring cha in 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
attempts 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.
Network Port Sharing (NPS)
About the Network Port Sharing Feature
You can use the Network Po rt Sharing feature to view the status of and configure and ma nage 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 uniquely 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
(included) 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.
3 Metered Rack PDU
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 by NPS guests. These include,
but are not limited to:
•
SNMP rPDU2Group OIDs
• Ene
•Initiating AOS/APP firmware updates for guest Rack PDUs
•Time synchronization for guest Rack PDUs
•
rgyWise support
Dat
a 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 would 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 interface via the "Configuration > RPDU >
Device > Display ID" field. The Display ID can also be configured from the CLI interface via the
dispID command.
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 guests. 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.
Metered Rack PDU4
RF Tag
The Rack PDU supports the RF Code sensor tag fo r Schneider Electric Rack PDUs. The tag enables
data center managers to wirelessly monitor power consumption and utilization with the enterpriseclass 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 t ag for Schneider Electric
works in concert with the AP8XXX Rack PDUs with firmware v6.0.9 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 t ag. 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, and phase outlet voltages/bank overload st ate readings every hour . T he 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 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
coordinated with the same parameters in the Cisco gear.
The Rack PDU implementation supports a single paren t, multiple children hierarchy. 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 inlet power. Both parent and children report a usage level (0-10
scale). The parent and inlet usage are always reported as 10 or “On”. When the parent is the host
Rack PDU of an NPS chain, the reported parent power is the sum of the p arent and e ach of the NPS
guests. The parent reports an inlet entity for itself and for each guest. The remaining configurable
items are string variables that may be modified as needed and are retained across power cycles or
reboots.
5 Metered Rack PDU
EnergyWise and NPS
AP8XXX 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. 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-functioning 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, you 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 update 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 Interface” on page 61
– “Command Line Interface” on page 16
– “Rack PDU Front Panel” on page 11
Metered Rack PDU6
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: 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 79
IPv6 initial setup
IPv6 network configuration provides flexibility to accommodate your requirement s. IPv6 can be use d
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 106
• “DHCP and BOOTP configuration”
• “Command Line Interface” on page 16
.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 95.
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 95.
If neither of these servers is available, see “Device IP Configuration Wizard” on page 106 or “Device
IP Configuration Wizard” on page 106.
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 BOOTPT AB 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 Interface” on page 61 or “Command Line Interface” on
page 16; the user name and password are both apc, by default. To create a bootup file,
see your BOOTP server documentation.
7 Metered Rack PDU
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 79.
1. The Rack PDU sends out a DHCP request that uses the following to identify itself:
– A Vendor Class Identifier (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 application firmware
installed 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 all 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 require this
cookie by default.)
Option 43 = 01 04 31 41 50 43
Where:
– The first byte (
– The second byte (
– The remaining bytes (
01) is the code.
04) is the length.
31 41 50 43) are the APC cookie.
See your DHCP server documentation to add code to the V endor Specific Information
option.
Note: By selecting the Require vendor specific cookie to accept DHCP Address
check box in the web interface, you can require the DHCP server to provide an “APC”
cookie, which supplies information to the Rack PDU:
Configuration > Network >TCP/IP > IPv4 Settings.
Network Management with Other Applications
These applications and utilities work with a Rack PDU which is connected to the network.
• PowerNet
Perform SNMP 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 Ra ck PDU
over the network, see “Device IP Configuration Utility”
• Security Wizard — Create components needed to help with security for the Rack PDUs
when you are using Secure Sockets Layer (SSL) and related protocols and encryption
routines Access priority for logging on
®
Management Information Base (MIB) with a standard MIB browser —
Metered Rack PDU8
Command Line Interface (CLI)
1. Log on to the CLI. See “Log on to the CLI” on page 16.
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.)
tcpip -i yourIPaddress
tcpip -s yourSubnetMask
tcpip -g yourDefaultGateway
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:
9 Metered Rack PDU
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.
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 HyperTerminal
9600 bps, 8 data bits, no parity, 1 stop bit, and no flow control.
®
) and configure the selected port for
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 alterna tely oran ge an d gre en within 5
to 7 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.
6. Press
ENTER, repeatedly if necessary, to display the User Name prompt again, then use
the default, apc, for the user name and passwo rd. (If you take longer than 30 seconds to
log on after the User Name prompt is re-displayed, 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>
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.
Metered Rack PDU10
Rack PDU Front Panel
pdu0535a
Serial
In
Out
y
USB
Reset
Main
Menu
Select
Scroll
- Warning
- OK
- Overload
SELEC
4
pdu051
MAIN
p
MAIN
p
pdu0512b
MAIN
Display Settings
Software Info
Network
SKU/Serial #
MAIN
p
Temp/ H u m i dit
SELECT
Input
229 V
19.1 A
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.
Item Function
Display Shows information about the Rack PDU. In normal
operation, input voltage, current, and power refreshes e very
five seconds. To reverse the text, press and hold
simultaneously for five seconds the Main Menu (), Scroll
(), and Select () buttons.
Network
x
19.1 A
229 V
.37 kW
Main Menu button Press to view the Rack PDU electrical
Input
TMAIN
4a
input.
Scroll button Press once to display the menu. Press
additional times to highlight the desired
menu option.
Select button With a menu option highlighted, press the
Select button to display Rack PDU
information. Network information is
shown.
SELECT
Input
229 V
19.1 A
4.37 kW
du0511a
SELECT
Input
229 V
19.1 A
4.37 kW
du0511a
SELECT
SELECT
123.456.78.91
IPv4 Addr ess
du0513a
11 Metered Rack PDU
Serial
In
Out
Temp/ H u m i dity
USB
Reset
Main
Menu
Select
Scroll
- Warning
- OK
- Overload
SELECT
Input
229 V
19.1 A
4.37 kW
MAIN
Network
x
Item Function
Load Indicator LED Indicates the status of the Rack PDU load. See “Load indicator
LED” on page 13.
Temp/Humidity port Port for connecting an optional Schneider Electric Temperature
Sensor (AP93T) or an optional Schneider Electric Temperature/
Humidity Sensor (AP9335TH).
In and Out ports For use with the Network Port Sharing feature.
USB port (For use with a flash drive for firmware upgrades - 5V @ 100ma.)
RJ-12 Serial Port Port 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).
pdu0535d
10/100 Base-T Connector Connects the Rack PDU to the network.
Network status LED See “Network Status LED” on page 13.
10/100 LED See “10/100 LED” on page 13.
Reset button Resets the Rack PDU without affecting the outlet status.
Metered Rack PDU12
Network Status LED
Condition Description
Off One of the following situations exists:
• 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 Green The Rack PDU has valid TCP/IP settings.
Solid Orange A hardware failure has been detected in the Rack PDU. Contact Customer
Support.
Flashing Green The Rack PDU does not have valid
Flashing Orange The 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 7 to configure the TCP/IP
settings of the Rack PDU.
2. To use a DHCP server, see “TCP/IP and Communication Settings” on page 78.
If the LED is flashing slowly, the Rack PDU is making DHCP
If the LED is flashing rapidly, the Rack PDU is starting up.
TCP/IP settings.
2
requests1.
10/100 LED
Condition Description
Off 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
defective
• The device that connects the Rack PDU to the network is turned off.
• The Rack PDU itself is not operating properly. It may need to be repaired or
replaced. Contact Customer Support.
Solid green The Rack PDU is connected to a network operating a t 10 Megabits per second
(Mbps).
Solid orange The Rack PDU is connected to a network operating at 100 Mbps.
Flashing green The Rack PDU is receiving or transmitting data packets at 10 Mbps.
Flashing orange The Rack PDU is receiving or transmitting data packets at 100 Mbps.
Load indicator LED
The load indicator LED identifies overload and warning conditions for the Rack PDU.
Condition Description
Solid Green OK. No load alarms (warning or critical) are present.
Solid Yellow Warning. At least one load warning alarm is present, but no critical alarms are
present.
Flashing Red Overload. At least one load critical alarm is present.
13 Metered Rack PDU
Display Tree Example 1
Software Info
SKU/Serial #
RF Code Contro
l
SELECTMAIN
5 sec 5 sec
5 sec5 sec
5 sec
Main
SELECTMAIN
Phase 1
208.0 V
14.3 A
1.23 kW
14.3 A
SELECTMAIN
Phase 3
208.0 V
14.3 A
1.23 kW
SELECTMAIN
Sensor
Temp: 45.6ºC
Hum: 37.8%
SELECTMAIN
1: 14.1 A
2: 14.2 A
3: 14.3 A
SELECTMAIN
Active
SELECTMAIN
5 sec
Network
Temp/Humidity
T/H
Network
SW Info
SKU/SN
pdu0531e
1: 0.0 A
2: 0.0 A
3: 0.0 A
SELECTMAIN
5 sec
metered banks
enabled
Appears only when a
sensor is active
Only when device is
phase to phase
5 sec
L1-2: 20 8V
L2-3: 20 8V
L3-1: 20 8V
SELECTMAIN
Phase 2
208.0 V
1.23 kW
Display Settin gs
Only when device has
Bank Current
Voltage
Only when RF code is
Phase Current
RF Code
Disp.Settings
RF Code Control
Metered Rack PDU14
Display Tree Example 2
MAIN
SELECT
LCD Contrast
5/9
Press “Select”
to adjust
LCD backlight
Auto-On
Press “Select”
to switch
MAIN
SELECT
MAIN
SELECT
LCD Orientation
Normal
Press “Select”
to switch
MAIN
SELECT
Display ID
Hide
Press “Select”
to switch
No
YesNetwork Port Sharing Group
Display Settings
MAIN
SELECT
IPv4 Address
10.218.116.139
IPv6 Address
FF80::200:87FF
FE51:F304
MAIN
SELECT
MAIN
SELECT
MAC Address
00 C0 B7
51 F304
Network
MAIN
SELECT
Sensor
Temp: 45.6 C
Hum: 37.8%
T/H
o
Model
AP8xxx
Serial Number
ZAxxxxxxxxxxx
MAIN
SELECT
SKU/SN
MAIN
SELECT
AOS
6.0.0
APP
6.0.0
SW info
MAIN
SELECT
RF Code-Console
Enabled
Press “Select”
WILL REBOOT
RF Code
Control
15 Metered Rack PDU
Command Line Interface
About the Command Line Interface (CLI)
You can use the command line interface to view the status of and configure and manage 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 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.
Metered Rack PDU16
Telnet for basic access
Telnet provides the basic security of authentication by user name and password, but not the highsecurity 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 139.225.6.133, when the Rack PDU uses the default Telnet port of 23), and
press
ENTER.
telnet and the IP address for the Rack PDU (for example,
If the Rack PDU uses a non-default port number (from 5000 to 32768), you must include
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 password, see “Recovering from a Lost
Password” on page 10.
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 account s,
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., HyperTerminal) and configure the selected port for 9600
bps, 8 data bits, no parity, 1 stop bit, and no flow control.
4. Press
ENTER. At the prompts, enter your user name and password.
17 Metered Rack PDU
About the Main Screen
Schneider Electric Network Management Card AOS vx.x.x
(c)Copyright 2015 All Rights Reserved RPDU 2g vx.x.x
-------------------------------------------------------------------------Name : Test Lab Date : 06/30/2015
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 displayed when you log on to the command 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 AOS vx.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: 10/30/2013
Time: 5:58:30
• The User field identifies whether you logged in through the Super User, Administrator
or Device Manager account.
User: Administrator
Metered Rack PDU18
• A 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.
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+.
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.
IPv6
only
Note: If P+ is not displayed, contact the Schneider Electric Customer Care Center.
Using the CLI
IPv4 and
IPv6*
Description
At the command line interface, you can use commands to configure the Rack PDU. To use a
command, type the command and press
ENTER. Commands and arguments are valid in lowercase,
uppercase, or mixed case. Options are case-sensitive.
While using the command line interface, you can also do the following:
• Type
? and press ENTER to view a list of available commands, based on your account
type.
• 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 UP arrow key to view the command that was entered most recently in the
session. Use the
UP and DOWN arrow keys to scroll through a list of up to ten previous
commands.
• Type at least one letter of a command and press the
TAB key to scroll through a list of
valid commands that match the text you typed in the command line.
• Type
exit or quit to close the connection to the command line interface.
19 Metered Rack PDU
Command Syntax
Item Description
- Options are preceded by a hyphen.
< > 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 brackets indicates that the items
are mutually exclusive. You must use one of the items.
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
To change the FTP port number to 5010, and enable FTP:
-S, which enables or disables the FTP feature.
1. Type the ftp command, the port option, and the argument
ftp -p 5010
5010:
2. After the first command succeeds, type the ftp command, the enable/disable option, and
enable selection:
the
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.
Metered Rack PDU20
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
Code Message
E000 Success
E001 Successfully Issued
E002 Reboot required for change to take ef fect
E100 Command failed
E101 Command not found
E102 Parameter Error
E103 Command Line Error
E104 User Level Denial
E105 Command Prefill
E106 Data Not Available
E107 Serial communication with the Rack PDU has been lost
21 Metered Rack PDU
Network Management Card Command Descriptions
? or help
Access: Super User, Administrator, Device User, Read Only
Description: View a list of all the CLI commands available to your account type. To view help text
for a specific command, type the command followed by a question mark.
Parameters: [<command>]
Example 1:
apc> ?
Network Management Card Commands:
--------------------------------------------------------------------? about alarmcount boot cd date
delete dir eventlog exit format ftp
help ping portspeed prompt quit radius
reboot resetToDef system tcpip user web
xferINI xferStatus
Example 2:
apc> help boot
Usage: boot -- Configuration Options
boot [-b <dhcpBootp | dhcp | bootp | manual>] (Boot Mode)
[-a <remainDhcpBootp | gotoDhcpOrBootp>] (After IP
Assignment)
[-o <stop | prevSettings>] (On Retry Fail)
[-c <enable | disable>] (Require DHCP Cookie)
[-s <retry then stop #>] (Note: 0 = never)
[-f <retry then fail #>] (Note: 0 = never)
[-v <vendor class>]
[-i <client id>]
[-u <user class>]
Error Message: E000, E102
Metered Rack PDU22
Loading...