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
about
Access: Super User, Administrator, Device User, Read Only
Description: Displays system information (Model Number, Serial Number,
Manufacture Dates, etc.)
Parameters: None
Example: apc> about
E000: Success
Hardware Factory
--------------Model Number: AP8XXX
Serial Number: ST0913012345
Hardware Revision: HW05
Manufacture Date: 3/4/2015
MAC Address: 00 05 A2 18 00 01
Management Uptime: 0 Days 1 Hour 42 Minutes
Error Message: E000
alarmcount
Access: Super User, Administrator, Device User, Read Only
Description: Displays alarms present in the system.
Option Argument Description
-p all View the number of active alarms reported by the Rack PDU.
Information about the alarms is provided in the event log.
warning View the number of active warning alarms.
critical View the number of active critical alarms.
Example: To view all active warning alarms, type:
apc> alarmcount
E000: Success
AlarmCount: 0
Error Message: E000, E102
23 Metered Rack PDU
boot
Access: Super User, Administrator
Description: Allows the user to get/set the network startup configuration of the device, such as
setting boot mode (DHCP vs BOOTP vs MANUAL).
Option Argument Description
-b
<boot
mode>
-c [<enable | disable>]
-v [<vendor class>] Vendor Class is APC
-i [<client id>] The MAC address of the NMC, Which uniquely identifies it
-u [<user class>] The name of the application firmware module.
Example: Using a DHCP server to obtain network settings:
dhcp | bootp | manual Define how the TCP/IP settings will be configured when
the Rack PDU turns on, resets, or restarts. See “TCP/IP
and Communication Settings” on page 78 for information
about each boot mode setting.
dhcp and dhcpBootp boot modes only . Ena ble or disable
(Require DHCP Cookie)
apc> boot
E000: Success
Boot Mode: manual
Non-Manual Mode Shared Settings
------------------------------Vendor class: <device class>
Client id: XX XX XX XX XX XX
User class: <user class>
After IP assignment: gotoDhcpOrBootp
the requirement that the DHCP server provide the APC
cookie.
on the network.
DHCP Settings
------------Retry then stop: 4
DHCP cookie is: enable
BOOTP Settings
--------------
Retry then fail: never
On retry failure: prevSettings
Error Message: E000, E102
bye
Access: Super User, Administrator, Device User, Read Only
Description: Exit the CLI
Example: bye
Error Message: None
Metered Rack PDU24
cd
Access: Super User, Administrator, Device User, Read Only
Description: Allows the user to set the working directory of the file system. The working directory is
set back to the root directory ‘/’ when the user logs out of the CLI.
Parameters: <dicrectory name>
Example:
apc> cd logs
E000: Success
apc> cd /
E000: Success
Error Message: E000, E102
clrrst
Access: Super User, Administrator, Device User
Description: Clear reset reason.
Example: None
Error Message: None
console
Access: Super User, Administrator
Description: Define whether users can access the command line interface using Telnet, which is
enabled by default, or Secure SHell (SSH), which provides protection by transmitting user names,
passwords, and data in encrypted form. You can change the Telnet or SSH port setting for additional
security. Alternately, disable network access to the command line interface.
Parameters:
Option Argument Description
-S disable | telnet | ssh Configure access to the command line interface, or use
the disable command to prevent access. Enabling SSH
enables SCP and disables Telnet.
-t <enable | disable>]
(telnet)
-pt <telnet port n> Define the Telnet port used to communicate with the Rack
PDU (23 by default).
-ps <SSH port n> Define the SSH port used to communicate with the Rack
PDU (22 by default).
-b 2400 | 9600 | 19200 |
38400
Example 1:
To enable SSH access to the command line interface, type:
console -S ssh
Example 2: To change the Telnet port to 5000, type:
Telnet: enabled
SSH: disabled
Telnet Port: 23
SSH Port: 22
Baud Rate: 9600Parameters:
Configure the speed of the serial port connection (9600
bps by default).
25 Metered Rack PDU
date
Access: Super User, Administrator
Definition: Get and set the date and time of the system.
To configure an NTP server to define the date and time for the Rack PDU, see “Date/T ime screen” on
page 94.
Parameters:
Option Argument Description
-d <“datestring”> Set the current date. The format must match the current -f setting.
-t <00:00:00> Configure the current time, in hour s, minutes, and seconds. Use the
24-hour clock format.
-f mm/dd/yy |
dd.mm.yyyy |
mmm-dd-yy |
dd-mmm-yy |
yyyy-mm-dd
-z <time zone
offset>
Select the numerical format in which to display all dates in this user
interface. Each letter m (for month), d (for day), and y (for year)
represents one digit. Single-digit days and months are displayed with a
leading zero.
Set the difference with GMT in order to specify your time zone. This
enables you to synchronize with other people in different time zones.
Example 1:
To display the date using the format yyyy-mm-dd, type:
date -f yyyy-mm-dd
Example 2: To define the date as October 30, 2015, using the format configured in the preceding
example, type:
date -d “2015-10-30”
Example 3: To define the time as 5:21:03 p.m., type:
date -t 17:21:03
Error Message: E000, E100, E102
delete
Access: Super User, Administrator
Description: Delete a file in the file system.
Parameters:
Argument Description
<file name> Type the name of the file to delete.
Example:
apc> delete /db/prefs.dat
E000: Success
Error Messages: E000, E102
Metered Rack PDU26
dir
Access: Super User, Administrator, Device User, Read Only
Description: Displays the content of the working directory.
Example: apc> dir
E000: Success
--wx-wx-wx 1 apc apc 3145728 Mar 3 2015 aos.bin
--wx-wx-wx 1 apc apc 3145728 Mar 4 2015 app.bin
-rw-rw-rw- 1 apc apc 45000 Mar 6 2015 config.ini
drwxrwxrwx 1 apc apc 0 Mar 3 2015 db/
drwxrwxrwx 1 apc apc 0 Mar 3 2015 ssl/
drwxrwxrwx 1 apc apc 0 Mar 3 2015 ssh/
drwxrwxrwx 1 apc apc 0 Mar 3 2015 logs/
drwxrwxrwx 1 apc apc 0 Mar 3 2015 sec/
drwxrwxrwx 1 apc apc 0 Mar 3 2015 dbg/
drwxrwxrwx 1 apc apc 0 Mar 3 2015 pdu/
Error Messages: E000
dns
Access: Super User, Administrator
Definition: Configure the manual Domain Name System (DNS) settings.
Parameter Argument Description
-OM <enable |
disable>
-p <primary DNS
server>
-s <secondary
DNS server>
-d <domain name> Set the domain name.
-n <domain name
IPv6>
-h <host name> Set the host name.
-y <enable |
disable>
Example: None
Error Message: E000
Override the manual DNS.
Set the primary DNS server.
Set the secondary DNS server.
Set the domain name IPv6.
System-hostname sync
27 Metered Rack PDU
Access: Super User, Administrator, Device User
Description: View email
Parameters:
Parameters Argument
-g[n] <enable | disable> (Generation)
-t[n] <To Address>
-o[n] <long | short> (Format)
-l[n] <Language Code>
-r [n] <Local | recipient | custom> (Route)
Custom Route Option
-f[n] <From Address>
-s{n} <SMTP Server>
-p[n] <Port>
-a[n] <enable | disable> (Authentication)
-u[n] <User Name>
-w[n] <Password>
-e[n] <none | ifsupported | always |
implicit> (Encryption)
-c[n] <enable | disable > (Required
Certificate)
-i[n] <Certificate File Name>
n= Email Recipient Number 1,2,3 or 4)
Example:
None
Error Message: None
Metered Rack PDU28
eventlog
Access: Super User, Administrator, Device User, Read Only
Description: View the date and time you retrieved the event log, the status of the Rack PDU, and
the status of sensors connected to the Rack PDU. View the most recent device events and the date
and time they occurred. Use the following keys to navigate the event log:
Key Description
ESC
ENTER
SPACEBAR
B
D
Close the event log and return to the command line interface.
Update the log display . Use this command to view events that were record ed after you
last retrieved and displayed the log.
View the next page of the event log.
View the preceding page of the event log. This command is not available at the main
page of the event log.
Delete the event log. Follow the prompts to confirm or deny the deletion. Deleted
events cannot be retrieved.
Example:
apc> eventlog
---- Event Log ---------------------------------------------------- Date: 03/06/2015 Time: 13:22:26
----------------------------------- Metered Rack PDU: Communication Established
Date Time Event
-------------------------------------------------------------- 03/06/2015 13:17:22 System: Set Time.
03/06/2015 13:16:57 System: Configuration change. Date format
preference.
03/06/2015 13:16:49 System: Set Date.
03/06/2015 13:16:35 System: Configuration change. Date format
preference.
03/06/2015 13:16:08 System: Set Date.
03/05/2015 13:15:30 System: Set Time.
03/05/2015 13:15:00 System: Set Time.
03/05/2015 13:13:58 System: Set Date.
03/05/2015 13:12:22 System: Set Date.
03/05/2015 13:12:08 System: Set Date.
03/05/2015 13:11:41 System: Set Date.
<ESC>- Exit, <ENTER>- Refresh, <SPACE>- Next, <D>- Delete
Error Message: E000, E100
29 Metered Rack PDU
exit or quit
Access: Super User, Administrator, Device User, Read Only
Description: Exit from the CLI session.
Parameters: None
Example:
apc> exit
Bye
Error Message: None
firewall
Access: Super User, Administrator
Description: Establishes a barrier between a trusted, secure internal network and another network.
Parameters:
Parameters Argument Description
-S <enable | disable> Enable or disable the Firewall.
-f <file name to activate> Name of the firewall to
activate.
-t <file name to test>
<duration time in minutes>
-fe No argument. List only Shows active file errors.
-te No argument. List only Shows test file errors.
-c No argument. List only Ca n cel a fire wa ll test .
-r No argument. List only Shows active firewall rules.
-l No argument. List only Shows firewall activity log.
Name of firewall to test and
duration time in minutes.
Error Message:
None
format
Access: Super User, Administrator
Description: Allows the user to format the FLASH file system. This will delete all configuration data,
event and data logs, certificates and keys.
Example:
apc> format
Format FLASH file system
Warning: This will delete all configuration data,
event and data logs, certs and keys.
Enter 'YES' to continue or <ENTER> to cancel:
apc>
Error Message: None
Metered Rack PDU30
ftp
Access: Super User, Administrator
Description: Get/set the ftp configuration data,
Note: The system will reboot if any configuration is changed.
Option Argument Definition
-p <port number>
(valid ranges are:
21 and 5000-32768)
-S enable | disable Configure access to the FTP server.
Define the TCP/IP port that the FTP server uses to
communicate with the Rack PDU (21 by default). The FTP
server uses both the specified port and the port one number
lower than the specified port.
Example: To change the TCP/IP port to 5001, type:
apc> ftp -p 5001
E000: Success
apc> ftp
E000: Success
Service: Enabled
Ftp Port: 5001
apc> ftp -p 21
E000: Success
Error Message: E000, E102
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
help.
Example 1: To view a list of commands available to a Device User, type:
help
Example 2: To view a list of options that are accepted by the alarmcount command, type:
alarmcount help
Error Message: None
lang
Access: Super User, Administrator, Device User, Read Only
Description: Language in use
Example: Languages enUs - English
Error Message: None
31 Metered Rack PDU
lastrst
Access: Super User, Administrator, Device User
Description: Last reset reason
Parameters: Usage: lastrst -- Last reset reason
Example:
09 Coldstart Reset
E000: Success
Error Message: None
ledblink
Access: Super User, Administrator, Device User
Description: Sets the blink rate to the LED on the Rack Power Distribution Unit (RPDU).
Parameters: None
Example:
usage: ledblink -- Configuration Options ledblink <duration time in minutes>
Error Message: None
logzip
Access: Super User, Administrator, Device User
Description: Places large logs into a zip file before sending.
Parameters:
Usage: logzip -- Configuration Options
logzip [-m <email recipient>] (email recipient number (1-4))
Example:
Generating files
Compressing files into /dbg/debug_ZA1023006009.tar
E000: Success
Error Message: E000
Metered Rack PDU32
netstat
Access: Super User, Administrator, Device User, Read Only
Description: Displays incoming and outgoing network connections.
Parameters:
Usage: netstat -- Configuration Options netstat
Example:
Current IP Information:
Family mHome Type IPAddress
Status
IPv6 4 auto FE80::2C0:B7FF:FE51:F304/64
configured
IPv6 0 manual ::1/128
configured
IPv4 0 manual 127.0.0.1/32
configured
Error Message: None
ntp
Access: Super User, Administrator
Description: Synchronizes the time of a computer client or server.
Option Argument Definition
-OM enable | disable Override the manual settings.
-p <primary NTP server> Specify the primary server.
-s <secondary NTP server> Specify the secondary server.
Example 1: To enable the override of manual setting, type:
ntp -OM enable
Example 2: To specify the primary NTP server, type:
ntp -p 150.250.6.10
Error Message: E000
33 Metered Rack PDU
ping
Access: Super User, Administrator, Device User
Description Perform a network ‘ping’ to any external network device.
Argument Description
<IP address or DNS name> Type an IP address with the format xxx.xxx.xxx.xxx, or the DNS
name configured by the DNS server.
Example:
apc> ping 192.168.1.50
E000: Success
Reply from 192.168.1.50: time(ms)= <10
Reply from 192.168.1.50: time(ms)= <10
Reply from 192.168.1.50: time(ms)= <10
Reply from 192.168.1.50: time(ms)= <10
Error Message: E000, E100, E102
portSpeed
Access: Super User, Administrator
Description: Allows the user to get/set the network port speed.
Note: The system will reboot if any configuration is changed.
Option Arguments Description
-s auto | 10H |
10F | 100H |
100 F
H = Half Duplex
F = Full Duplex
Example:
apc> portspeed
E000: Success
Port Speed: 10 Half_Duplex
apc> portspeed -s 10h
E000: Success
apc> portspeed
E000: Success
Port Speed: 10 Half_Duplex
Define the communication speed of the Ethernet port. The auto
command enables the Ethernet devices to negotiate to transmit at
the highest possible speed. See “Port Speed” on page 80 for more
information about the port speed settings.
10 = 10 Meg Bits
100 = 100 Meg Bits
apc> portspeed -s auto
E000: Success
Error Message: E000, E102
Metered Rack PDU34
prompt
Access: Super User, Administrator, Device User
Description: Allows the user to change the format of the prompt, either short or long.
Option Argument Description
-s long The prompt includes the account type of the currently logged-in user.
short The default setting. The prompt is four characters long: APC>
Example:
apc> prompt –s long
E000: Success
Administrator@apc>prompt –s short
E000: Success
Error Message: E000, E102
pwd
Access: Super User, Administrator, Device User, Read Only
Description: Used to output the path of the current working directory.
Parameters: pwd
Example: Usage: pwd -- Configuration Options
Error Message: None
35 Metered Rack PDU
radius
Access: Super User, Administrator
Description: View the existing RADIUS settings, enable or disable RADIUS authentication, and
configure basic authentication parameters for up to two RADIUS servers.
For a summary of RADIUS server configuration and a list of supported RADIUS servers, see
“Configure the RADIUS Server” on page 76.
Additional authentication parameters for RADIUS servers are available at the Web interface of the
Rack PDU. See “RADIUS” on page 75 for more information.
For detailed information about configuring your RADIUS server, see the Security Handbook,
available at www.schneider-electric.com.
Option Argument Description
-a local |
radiusLocal
| radius
-p1
-p2
<server IP> The server name or IP addre ss of the pr ima r y or sec on d ar y RA DIUS
Configure RADIUS authentication:
local—RADIUS is disabled. Local authentication is enabled.
radiusLocal—RADIUS, then Local Authentication. RADIUS and
local authentication are enabled. Authentication is requested from the
RADIUS server first. If the RADIUS server fails to respond, local
authentication is used.
radius—RADIUS is enabled. Local authentication is disabled.
server.
Note: RADIUS servers use port 1812 by default to authenticate users.
To use a different port, add a colon followed by the new port number to
the end of the RADIUS server name or IP address. The Rack PDU
supports ports 1812, 5000 to 32768.
-s1
-s2
-t1
-t2
<server
secret>
<server
timeout>
The shared secret between the primary or secondary RADIUS server
and the Rack PDU.
The time in seconds that the Rack PDU waits for a response from the
primary or secondary RADIUS server.
Example 1:
To view the existing RADIUS settings for the Rack PDU, type
radius and press ENTER.
Example 2: To enable RADIUS and local authentication, type:
radius -a radiusLocal
Example 3: To configure a 10-second timeout for a secondary RADIUS server, type:
radius -t2 10
Error Message: E000, E102
Metered Rack PDU36
reboot
Access: Super User, Administrator
Description: Restart the NMC interface of the Rack PDU only. Forces the network device to reboot.
User must confirm this operation by entering a “YES” after the command has been entered.
Parameters: None
Example:
apc> reboot
E000: Success
Reboot Management Interface
Enter 'YES' to continue or <ENTER> to cancel : <user enters ‘YES’>
Rebooting...
Error Message: E000, E100
resetToDef
Access: Super User, Administrator
Description: Reset all parameters to their default.
Option Arguments Description
-p all | keepip all = all configuration data, including the IP address.
keepip -= all configuration data, except the IP address.
Reset all configuration changes, inclu din g ev en t act ion s, device
settings, and, optionally, TCP/IP configuration settings.
Example: To reset all of the configuration changes except the TCP/IP settings for the Rack PDU,
type:
resetToDef -p keepip
Enter 'YES' to continue or <ENTER> to cancel : : <user enters ‘YES’>
all User Names, Passwords.
Please wait...
Please reboot system for changes to take effect!
Error Message: E000, E100
37 Metered Rack PDU
session
Access: Super User, Administrator, Device User
Description: Records who is logged in, the serial, time and ID.
Parameters:
Option Arguments
Session [-d <session nID>] (Delete)
-M <Enable | disable> (Multi-User Enable)
-a <enable | disable (Remote Authentication Override)
Example:
User Interface Address Logged In Time ID
-----------------------------------------------------------------------apc Serial 00:00:05 1
Error Message: E000
smtp
Access: Super User, Administrator, Device User
Description: Internet standard for electronic mail.
Option Argument
-f <From Address
-s <SMTP Server>
-p <Port>
-a <enable | disable> (Authentication)
-u <User Name>
-w <Password>
-e <none | ifavail | always | implicit> (Encryption)
-c <enable | disable> (Require Certificate)
-i <Certificate File Name>
1
Port options are 25, 465, 587, 5000 to 32768
1
Example:
From: address@example.com
Server: mail.example.com
Port: 25
Auth: disabled
User: User
Password: <not set>
Encryption: none
Req. Cert: disabled
Cert File: <n/a>
Error Message: E000
Metered Rack PDU38
snmp
Access: Super User, Administrator
Description: Enable or disable SNMP.
Option Arguments Description
-c <Community> Identify the group of Rack PDUs
-a <read | write | writeplus | disable> Set the access level
-n <IP or Domain Name> The host’s name or address
-S enable | disable Enable or disable the respective version
Example: To enable SNMP version 1, type:
Access Control #: 1
Community: public
Access Type: read
Address: 0.0.0.0
Access Control #: 2
Community: private
Access Type: write +
Address: 0.0.0.0
of SNMP
Error Message: None
snmpv3
Access: Super User, Administrator
Description: Enable or disable SNMP 3
.
Option Arguments Description
-S enable | disable Enable or disable the respective version
-u [n] User Name User Name
-c [n] <Community> Identify the group of Rack PDUs
-a [n] <read | write | writeplus | disable> Set the access level
-n [n] <IP or Domain Name> The host’s name or address
-ap [n] <sha | md5 | none> (Authentication Protocol)]
-pp [n] <aes | des | none> (Privacy Protocol)]
-ac [n] <enable | disable> (Access)
-au [n] <Nms Ip>] [n] = Access Control # = 1,2,3, or 4)
Example: To enable SNMP version 3, type:
Access Control #: 3
Community: public
Access Type: read
Address: 0.0.0.0
of SNMP
Access Control #: 2
Community: private
Access Type: write +
Address: 0.0.0.0
Error Message:None
39 Metered Rack PDU
snmptrap
Access: Super User, Administrator
Description: Enable or disable SNMP trap generation
Parameters:
Option Arguments
-c{n} <Community>
-r[n] <Receiver NMS IP>
-l[n] <Language> [language code]
-t[n] <Trap Type> [snmpV1 | snmpV3]]
-g[n] <Generation> [enable | disable]
-a[n] <Auth Trap> [enable | disable]
-u[n] <profile1 | profile2 | profile3 | profile4> (User Name)
n=Trap receiver # = 1,2,3,4,5 or 6
Error Message:
None
system
Access: Super User, Administrator
Description: View and set the system name, the contact, the location and view up time as well as
the date and time, the logged-on user, and the high-level system status P, N, A (see “About the Main
Screen” on page 18 for more information about system status).
Option Argument Description
-n <system-name> Define the device name, the name of the person responsible for
-c <system-contact>
-l <system-location>
-m <system-message> When defined, a custom message will appear on the log on
-s <enable | disable>]
(system-hostname
sync)
the device, and the physical location of the device.
Note: If you define a value with more than one word, you must
enclose the value in quotation marks.
These values are also used by StruxureWare and the Rack
PDU’s SNMP agent.
screen for all users.
Allow the host name to be synchronized with the system name
so both fields automatically contain the same value.
Note: When enabling this feature, the system name identifier
can no longer contain a space character (since it will be
synchronized to the host name field).
Example 1: To set the device location as Test Lab, type:
system -l “Test Lab”
Example 2: To set the system name as Rack 5, type:
system -n “Rack 5”
Metered Rack PDU40
tcpip
Access: Super User, Administrator
Description: View and manually configure these network settings for the Rack PDU:
Option Argument Description
-i <IP address> Type the IP address of the Rack PDU, using the format
xxx.xxx.xxx.xxx
-s <subnet mask> Type the subnet mask for the Rack PDU.
-g <gateway> Type the IP address of the default gateway.
loopback address (127.0.0.1) as the default gateway.
-d <domain name> Type the DNS name configured by the DNS server.
-h <host name> Type the host name that the Rack PDU will use.
-S enable | disable Enable or disable IPv4.
Example 1: To view the network settings of the Rack PDU, type tcpip and press ENTER.
Example 2: To manually configure an IP address of 150.250.6.10 for the Rack PDU, type:
tcpip -i 150.250.6.10
Do not use the
tcpip6
Access: Super User, Administrator
Description: Enable IPv6 and view and manually configure these network settings for the Rack
PDU:
Option Argument Description
-S enable | disable Enable or disable IPv6.
-man enable | disable Enable manual addressing for the IPv6 address of the Rack
PDU.
-auto enable | disable Enable the Rack PDU to automatically configure the IPv6
address.
-i <IPv6 address> Set the IPv6 address of the Rack PDU.
-g <IPv6 gateway> Set the IPv6 address of the default gateway.
-d6 router | statefull
| statelss | never
Example 1: To view the network settings of the Rack PDU, type tcpip6 and press ENTER.
Example 2: To manually configure an IPv6 address of 2001:0:0:0:0:FFD3:0:57ab for the
Rack PDU, type:
tcpip6 -i 2001:0:0:0:0:FFD3:0:57ab
Set the DHCPv6 mode, with parameters of router controlled,
statefull (for address and other information, they maintain their
status), stateless (for information other than address, the status
is not maintained), never.
41 Metered Rack PDU
user
Access: Super User, Administrator
Description: Configure the user name, password, and inactivity timeout for each account types.
You can’t edit a user name, you must delete it and then create a new user. For information on the
permissions granted to each account type, see “Types of User Accounts” on page 2.
Option Argument Description
-n <user>
-pw <user password>
-pe <user permission>
-d
-e enable | disable
-st <session timeout>
-sr enable | disable
-el enable | disable Indicate the Event Log color coding.
-lf tab | csv Indicate the format for exporting a log file.
-ts us | metric Indicate the temperature scale, fahrenheit or celsius.
<user description>
Specify these options for a user.
Enable overall access.
Specify how long a session lasts waits before logging off a
user when the keyboard is idle.
Bypass RADIUS by using the serial console (CLI)
connection, also known as Serial Remote Authentication
Override
-df <mm/dd/yyyy |
dd.mm.yyyy | mmm-ddyy | dd-mmm-yy |
yyyy-mm-dd>
-lg
-del <user name> Delete a user.
-l Display the current user list.
<language code (e.g.
enUs)>
Specify a date format.
Specify a user language.
Example 1: To change the Administrator user name to XYZ, type:
user -an XYZ
Example 2: To change the log off time to 10 minutes, type:
user -t 10
Metered Rack PDU42
userdflt
Access: Super User, Administrator
Description: Complimentary function to “user” establishing default user preferences.
There are two main features for the default user settings:
Determine the default values to populate in each of the fields when the Super User or Administrator-
level account creates a new user. These values can be changed before the settings are applied to
the system.
For remote users (user accounts not stored in the system that are remotely authenticated such as
RADIUS) these are the values used for those that are not provided by the authenticating server. For
example, if a RADIUS server does not provide the user with a temperature preference, the value
defined in this section will be used.
Parameters:
Options Argument Description
-e <enable | disable> (Enable) By default, user will be enabled or
disabled upon creation. Remove
(Enable) from the end
-pe <Administrator | Device | Read-Only |
Network-Only> (user permission)
-d <user description> Provide a user description.
-st <session timeout> minute(s) Provide a default session timeout.
-bl <bad login attempts> Number of incorrect login attempts a
-el <enable | disable> (Event Log Color
Coding)
-lf <tab | csv> (Export Log Format) Specify the log export format, tab or
-ts <us | metrics> (Temperature Scale) Specify the user's temperature
-df <mm/dd/yyyy | dd.mm.yyyy | mmm-dd-yy |
dd-mmm-yy | yyyy-mm-dd> (Date Format)
-lg <language code (enUs, etc)> User language
-sp <enable | disable> Strong password
-pp <interval in days> Required password change interval
Specify the user's permission level
and account type.
user has before the system disables
their account. Upon reaching this
limit, a message is displayed
informing the user the account has
been locked. The Super User or an
Administrator-level account is
needed to re-enable the account to
allow the user to log back in.
Note: A Super User account cannot
be locked out, but can be manually
disabled if necessary.
Enable or disable event log color
coding.
CSV.
scale. This setting is also used by
the system when a user preference
is not available (for example, email
notifications).
Specify the user's preferred date
format.
Error Message:
None
43 Metered Rack PDU
web
Access: Super User, Administrator
Description: Enable access to the Web interface using HTTP or HTTPS.
For additional security, you can change the port setting for HTTP and HTTPS to any unused port
from 5000 to 32768. Users must then use a colon (:) in the address field of the browser to specify the
port number. For example, for a port number of 5000 and an IP address of 152.214.12.114, type:
http://152.214.12.114:5000
Parameters:
Option Argument Definition
-h enable | disable Enable or disable access to the user interface for HTTP.
Enable or disable access to the user interface for HTTPS.
-s enable | disable
-ph <http port #>
-ps <https port #>
Example 1:
To prevent all access to the web interface, type:
web -S disable
Example:
To define the TCP/IP port used by HTTP, type:
apc> web
E000: Success
Service: http
Http Port: 5000
Https Port: 443
apc> web -ph 80
E000: Success
Error Message: E000, E102
When HTTPS is enabled, data is encrypted during
transmission and authenticated by digital certificate.
Specify the TCP/IP port used by HTTP to communicate
with the Rack PDU (80 by default). The other available
range is 5000–32768.
Specify the TCP/IP port used by HTTPS to communicate
with the Rack PDU (443 by default). The other available
range is 5000–32768.
whoami
Access: Super User, Administrator, Device Only, Read Only
Description: Provides login information on the current user.
Parameters: None
Example:
apc> whoami
E000: Success
apc>
Error Message: None
Metered Rack PDU44
xferINI
Access: Super User, Administrator
Description: Use XMODEM to upload an INI file while you are accessing the command line
interface through a serial connection. After the upload completes:
• If there are any system or network changes, the command line interface restarts and you
must log on again.
• If you selected a baud rate for the file transfer that is not the same as the default baud
rate for the Rack PDU, you must reset the baud rate to the default to reestablish
communication with the Rack PDU.
Parameters: None
Example:
apc> xferINI
Enter 'YES' to continue or <ENTER> to cancel : <user enters ‘YES’>
------- File Transfer Baud Rate----------------------------- 1- 2400
2- 9600
3- 19200
4- 38400
> <user enters baudrate selection>
Transferring at current baud rate (9600), press <ENTER>...
<user presses <ENTER>>
Start XMODEM-CRC Transfer Now!
CC
<user starts sending INI>
150 bytes have successfully been transmitted.
apc>
Error Message: None
xferStatus
Access: Super User, Administrator
Description: View the result of the last file transfer. See “Verifying Upgrades and Updates” on
page 116 for descriptions of the transfer result codes.
Parameters: None
Example:
apc> xferStatus
E000: Success
Result of last file transfer: Failure unknown
Error Message: E000
45 Metered Rack PDU
Device Command Descriptions
Network Port Sharing Commands
The CLI allows commands to be sent to guest Rack PDUs. The user may specify the Display ID of
the Rack PDU to be commanded, followed by a colon, before the first argument (or as the first
argument, if the command does not normally have arguments). Providing a Display ID is optional,
omitting it will simply command the local Rack PDU. For example:
<command> <id>:<arg1> <arg2>
This will send <command> to the Rack PDU with the Display ID <id>.
<id>
is delimited from <arg1> with a colon character; do not include any spaces between
<id>:<arg1>, as spaces are used to delimit arguments.
bkLowLoad
Access: Super User, Administrator, Device User
Description: Set or view the bank low-load threshold current in amps. You can specify all banks, a
single bank, a range, or a comma-separated list of single banks and/or ranges.
Parameters:
[id#:]<all | bank#> [current]
bank# = A single number or a range of n umber s sep arated with a da sh or a comma;
separated list of single bank number and/or number ranges.
current = The new bank threshold (Amps)
Example 1: To set the low-load threshold for all banks to 1A, type:
apc> bkLowLoad all 1
E000: Success
Example 2: To view the low-load threshold setting for banks 1 through 3, type:
apc> bkLowLoad 1-3
E000: Success
1: 1 A
2: 1 A
3: 1 A
Error Messages: E000, E102
Metered Rack PDU46
bkNearOver
Access: Super User, Administrator, Device User
Description: Set or view the bank near-overload threshold current in amps. You can specify all
banks, a single bank, a range, or a comma-separated list of single banks and/or ranges.
Parameters:
[id#:]<all | bank#> [current]
Example 1: To set the near-overload threshold for all banks to 10A, type:
apc> bkNearOver all 10
E000: Success
Example 2: To view the near-overload threshold setting for banks 1 through 3, type:
apc> bkNearOver 1-3
E000: Success
1: 10 A
2: 10 A
3: 10 A
Example 3: To view the near-overload threshold setting for banks 1 and 2 on guest Rack PDU 3,
type:
apc> bkNearOver 3:1-2
E000: Success
1: 16 A
2: 16 A
Error Messages: E000, E102
bkOverLoad
Access: Super User, Administrator, Device User
Description: Set or view the bank overload threshold current in amps. You can specify all banks, a
single bank, a range, or a comma-separated list of single banks and/or ranges.
Parameters:
[id#:]<all | bank#> [current]
Example 1: To set the bank overload threshold for all banks to 13A, type:
apc> bkOverLoad all 13
E000: Success
Example 2: To view the bank overload threshold setting for banks 1 through 3, type:
apc> bkOverLoad 1-3
E000: Success
1: 13 A
2: 13 A
3: 13 A
Error Messages: E000, E102
47 Metered Rack PDU
bkReading
Access: Super User, Administrator, Device User, Read Only
Description: View the current reading (measurement) in amps for a bank. You can specify all
banks, a single bank, a range, or a comma-separated list of single banks and/or ranges.
Parameters:
[id#:]<all | bank#> [current]
Example 1: To view the current reading for bank 3, type:
apc> bkReading 3
E000: Success
3: 4.2 A
Example 2: To view the current reading for all banks, type:
apc> bkReading all
E000: Success
1: 6.3 A
2: 5.1 A
3: 4.2 A
Error Messages: E000, E102
Metered Rack PDU48
devLowLoad
Access: Super User, Administrator, Device User
Description: Set or view the low-load threshold in kilowatts for the device.
Parameters: [id#:][threshold] = New power threshold (Kilowatts).
Example 1: To view the low-load threshold, type:
apc> devLowLoad
E000: Success
0.5 kW
Example 2: To set the low-load threshold to 1 kW, type:
apc> devLowLoad 1.0
E000: Success
Error Messages: E000, E102
devNearOver
Access: Super User, Administrator, Device User
Description: Set or view the near-overload threshold in kilowatts for the device.
Parameters: <id#:][threshold] = New outlet threshold (Kilowatts).
Example 1: To view the near-overload threshold, type:
apc> devNearOver
E000: Success
20.5 kW
Example 2: To set the near-overload threshold to 21.3 kW, type:
apc> devNearOver 21.3
E000: Success
Error Messages: E000, E102
devOverLoad
Access: Super User, Administrator, Device User
Description: Set or view the overload threshold in kilowatts for the device.
Parameters: <id#:][threshold] = New outlet threshold (Kilowatts).
Example 1: To view the overload threshold, type:
apc> devOverLoad
E000: Success
25.0 kW
Example 2: To set the overload threshold to 25.5 kW, type:
apc> devOverLoad 25.5
E000: Success
Example 3: To view the overload threshold for guest Rack PDU 3, type:
apc> devOverLoad 3:
E000: Success
5.0 kW
Error Messages: E000, E102
49 Metered Rack PDU
devReading
Access: Super User, Administrator, Device User, Read Only
Description: View the total power in kilowatts or total energy in kilowatt-hours for the device.
Parameters: [id#:] [power | energy | appower | pf]
Argument Definition
<power> View the total power in kilowatts.
<energy> View the total energy in kilowatt-hours.
<appower> View the total apparent power in kVA.
<pf> View the power factor
Example 1: To view the total power, type:
apc> devReading power
E000: Success
5.2 kW
Example 2: To view the total energy, type:
apc> devReading energy
E000: Success
200.1 kWh
Error Messages: E000, E102
dispID
Access: Super User, Administrator
Description: Sets or reads the device’s Display ID.
Parameters: [id#:] [new_id] = Set the Display ID.
Example 1:
apc> dispID
E000: Success
RPDU ID: 1*
apc> dispID 2
E000: Success
RPDU ID: 2*
apc> dispID 3: 2
E000: Success
Error Message: E000, E102
Metered Rack PDU50
energyWise
Access: Super User, Administrator, Device User
Description: Cisco IOS® software for monitoring, controlling, and reporting the energy use of
information technology (IT).
Parameters:
Option Argument
-e <enable | disable>] (Enable)
-p <Port>
-d <Domain>]
-m <enable | disable>] (Secure Mode)
-s <Shared Secret>
-v (Toolkit Version)
-n [outlet #] <Name>] (0 for Parent)
-r [outlet #] <Role>] (0 for Parent)
-k [outlet #] <Keywords>] (0 for Parent)
-i [outlet #] <1-100>] (0 for Parent) (Importance)
Example:
Enable: Disabled
Port: 43440
Domain Name:
Secure Mode: Shared Secret
Shared Secret: <hidden>
Toolkit Version: (rel2_7)1.2.0
Name (P): apc51F304
Name (C1): apc51F304.1.Outlet1
Name (C2): apc51F304.1.Outlet2
Name (C3): apc51F304.1.Outlet3
Name (C4): apc51F304.1.Outlet4
Name (C5): apc51F304.1.Outlet5
Name (C6): apc51F304.1.Outlet6
Name (C7): apc51F304.1.Outlet7
Name (C8): apc51F304.1.Outlet8
Role (P): Rack Power Distribution Unit
Role (C1): Outlet
Role (C2): Outlet
Role (C3): Outlet
Role (C4): Outlet
Role (C5): Outlet
Role (C6): Outlet
Role (C7): Outlet
Role (C8): Outlet
Keywords (P): apc,pdu,rackpdu
Keywords (C1): apc,pdu,rackpdu,outlet
Keywords (C2): apc,pdu,rackpdu,outlet
Keywords (C3): apc,pdu,rackpdu,outlet
Keywords (C4): apc,pdu,rackpdu,outlet
Keywords (C5): apc,pdu,rackpdu,outlet
Keywords (C6): apc,pdu,rackpdu,outlet
Keywords (C7): apc,pdu,rackpdu,outlet
51 Metered Rack PDU
Keywords (C8): apc,pdu,rackpdu,outlet
Importance (P): 1
Importance (C1): 1
Importance (C2): 1
Importance (C3): 1
Importance (C4): 1
Importance (C5): 1
Importance (C6): 1
Importance (C7): 1
Importance (C8): 1
Error Message: None
Metered Rack PDU52
Temperature/Humidity Sensor Note: You must have installed an optional Schneider Electric
Temperature/Humidity Sensor
(AP9335TH) to your Rack PDU in order to use the Humidity related
commands.
humHyst
Access: Super User, Administrator, Device User
Description: Sets and reads the humidity threshold hysteresis
Parameters: [id#:] [ value ] = new threshold hysteresis value (% RH)
Example:
apc> humHyst
E000: Success
6 %RH
apc> humHyst 5
E000: Success
Error Message: E000, E102
humLow
Access: Super User, Administrator, Device User
Description: Set or view the low humidity threshold as a percent of the relative humidity.
Parameters: [id#:] [ humidity ] = new low humidity threshold
Example 1: To view the low humidity threshold, type:
apc> humLow
E000: Success
10 %RH
Example 2: To set the low humidity threshold, type:
apc> humLow 12
E000: Success
Example 3: To view the low humidity threshold on guest Rack PDU 3, type:
apc> humLow 3:
E000: Success
10 %RH
Error Message: E000, E102
53 Metered Rack PDU
humMin
Access: Super User, Administrator, Device User
Description: Set or view the minimum humidity threshold as a percent of the relative humidity
Parameters: [id#:] [ humidity ] = new minimum humidity threshold.
Example 1: To view the minimum humidity threshold, type:
apc> humMin
E000: Success
6 %RH
Example 2: To set the minimum humidity threshold, type:
apc> humMin 8
E000: Success
Example 3: To set the minimum humidity threshold on guest Rack PDU 3 to 18% RH, type:
apc> humMin 3:18
E000: Success
Error Message: E000, E102
humReading
Access: Super User, Administrator, Device User, Read Only
Description: View the humidity value from the sensor.
Parameters: [id#:]
Example 1: To view the humidity value, type:
apc> humReading
E000: Success
25 %RH
Example 2: To view the humidity value on guest Rack PDU 2, type:
apc> humReading 2:
E000: Success
48 %RH
Error Message: E000, E102, E201
lcd
Access: Super User, Administrator, Device User
Description: Turn the LCD On/Off
Parameters: [id#:] [ on|off ]
Example:
apc> lcd off
E000: Success
apc> lcd 1: on
E000: Success
Error Message: None
Metered Rack PDU54
lcdBlink
Access: Super User, Administrator
Description: Blink the LCD Back-light for the specified period
Parameters: [id#:] [ time ] = is the number of minutes to blink the display. It can be cancelled
by pressing a button on the LCD. Valid range is [1-10]
Example:
apc> lcdBlink
E000: Success
25 %RH
Error Messages: None
phLowLoad
Access: Super User, Administrator, Device User
Description: Set or view the phase low-load threshold in kilowatts. To specify phases, choose from
the following options. Type:
all, a single phase, a range, or a comma-separated list of phases.
Parameters: <”all” | phase#> <current>
phase#
= A single number or a range of numbers separated with a dash or a comma; separated list
of single bank number and/or number ranges.
current = The new phase threshold (Amps).
Example 1: To set the low-load threshold for all phases to 1 kW, type:
apc> phLowLoad all 1
E000: Success
Example 2: To view the low-load threshold for phases 1 through 3, type:
apc> phLowLoad 1-3
E000: Success
1: 1 A
2: 1 A
3: 1 A
Error Message: E000, E102
55 Metered Rack PDU
phNearOver
Access: Super User, Administrator, Device User
Description: Set or view the phase near-overload threshold in kilowatts.
Parameters: <”all” | phase#> <current>
phase#
= A single number or a range of numbers separated with a dash or a comma; separated list
of single bank number and/or number ranges.
current = The new phase threshold (Amps).
Example 1: To set the near-overload threshold for all phases to 10 kW, type:
apc> phNearOver all 10
E000: Success
Example 2: To view the near-overload threshold for phases 1 through 3, type:
apc> phNearOver 1-3
E000: Success
1: 10 A
2: 10 A
3: 10 A
Error Message: E000, E102
phOverLoad
Access: Super User, Administrator, Device User
Description: Set or view the phase overload threshold in kilowatts. T
Parameters:
<”all” | phase#> <current>
phase#
= A single number or a range of numbers separated with a dash or a comma; separated list
of single bank number and/or number ranges.
current = The new phase threshold (Amps).
Example 1: To set the overload threshold for all phases to 13 kW, type:
apc> phOverLoad all 13
E000: Success
Example 2: To view the overload threshold for phases 1 through 3, type:
apc> phOverLoad 1-3
E000: Success
1: 13 A
2: 13 A
3: 13 A
Error Message: E000, E102
Metered Rack PDU56
phReading
Access: Super User, Administrator, Device User, Read Only
Description: View the current, voltage, or power for a phase. Set or view the phase near-overload
threshold in kilowatts. You can specify all phases, a single phase, a range, or a comma-separated list
of phases.
Parameters: < all | phase# > < current | voltage | power | appower | pf >
Example 1: To view the measurement for current for phase 3, type:
apc> phReading 3 current
E000: Success
3: 4 A
Example 2: To view the voltage for each phase, type:
apc> phReading all voltage
E000: Success
1: 120 V
2: 120 V
3: 120 V
Example 3: To view the power for phase 2 on guest Rack PDU 3, type:
apc> phReading 3:2 power
E000: Success
2: 40 W
Error Message: E000, E102
phTophVolts
Access: Super User, Administrator, Device User, Read Only Description:
Read the phase-to-phase voltage on multi-phase devices.
Parameters: [id#]
id# = The display identifier of the Rack Power Distribution Unit (RPDU) – normally 1. However, in an
NPS environment, the value will be 1 through number of NPS remotes.
Example 1:
apc> phTophVolts 1
E000: Success
1: L1-2 208 V
2: L2-3 208 V
3: L3-1 208 V
Error Messages: E000, E102
57 Metered Rack PDU
prodInfo
Access: Super User, Administrator, Device User, Read Only
Description: View information about the Rack PDU.
Parameters: [id#]
Example: To view the product information for this Rack PDU, type:
apc> prodInfo
E000: Success
AOS X.X.X
Metered Rack PDU X.X.X
Model: AP8XXX
Present Outlets: XX
Metered Outlets: XX
Max Current: XX A
Phases: X
Banks: X
Uptime: 0 Days 0 Hours 0 Minutes
NPS Type: Host
NPS Status: Active
Network Link: Link Active
Error Messages: None
sensorName
Access: Super User, Administrator, Device User
Description: Set or view the name assigned to the Rack PDU Temp/Humidity port.
Parameters: [id#:][newname]
Example 1: To set the name for the port to “Sensor1,” type:
apc> sensorName Sensor1
E000: Success
Example 2: To then view the name for the sensor port, type:
apc> sensorName
E000: Success
Sensor1
Example 3: To set the name for the sensor port on guest Rack PDU 2 to “Sensor1,” type:
apc> sensorName 2:Sensor1
E000: Success
Error Messages: E000, E102
Metered Rack PDU58
Temperature Sensor Note: You must have installed an optional Schneider Electric Temperature
Sensor (AP9335T) to your Rack PDU in order to use the Temperature related commands.
tempHigh
Access: Super User, Administrator, Device User
Description: Set or view the high-temperature threshold in either Fahrenheit or Celsius.
Parameters: [id#:] < F | C > [<temperature>] = New high temperature threshold
Example 1: To set the high-temperature threshold to 70º Fahrenheit, type:
apc> tempHigh F 70
E000: Success
Example 2: To view the high-temperature threshold in Celsius, type:
apc> tempHigh C
E000: Success
21 C
Example 3: To view the high-temperature threshold of guest Rack PDU 2 in Fahrenheit, type:
apc> tempHigh 2:F
E000: Success
85 F
Error Messages: E000, E102
tempHyst
Access: Super User, Administrator, Device User
Description: Set and displays the temperature threshold hysteresis
Parameters: [id#:] < F | C > [<temperature>] = new temperature hysteresis value.
Example:
apc> tempHyst F 6
E000: Success
apc> tempHyst C
E000: Success
3 C
Error Message: E000, E102
59 Metered Rack PDU
tempMax
Access: Super User, Administrator, Device User
Description: Set or view the max-temperature threshold in either Fahrenheit or Celsius.
Parameters: [id#:] < F | C > [<temperature>] = new max temperature threshold.
Example 1: To set the max-temperature threshold to 80º Fahrenheit, type:
apc> tempMax F 80
E000: Success
Example 2: To view the max-temperature threshold in Celsius, type:
apc> tempMax C
E000: Success
27 C
Example 3: To view the max-temperature threshold of guest Rack PDU 3 in Fahrenheit, type:
apc> tempMax 3:F
E000: Success
95 F
Error Message: E000, E102
tempReading
Access: Super User, Administrator, Device User
Description: View the temperature value in either Fahrenheit or Celsius from the sensor.
Parameters: [id#:] < F | C > = temperature
Example 1: To view the temperature value in Fahrenheit, type:
apc> tempReading F
E000: Success
51.1 F
Example 2: To view the temperature value of guest Rack PDU 3 in Celsius, type:
apc> tempReading 2:C
E000: Success
23.5 C
Error Message: E000, E102, E201
Metered Rack PDU60
Web Interface
Supported Web Browsers
Y ou can use Microsof t® Internet Explorer® (IE) 7.x and higher (on Windows® operating systems only)
or Mozilla
Web interface. Other commonly available browsers may work but have not been fully tested by
Schneider Electric.
The Rack PDU cannot work with a proxy server. Before you can use a Web browser to access the
Web interface of the Rack PDU, you must do one of the following:
®
Firefox® 3.0.6 or higher (on all operating systems) to access the Rack PDU through its
• Configure the Web browser to disable the use of a proxy server for the Rack PDU.
• Configure the proxy server so that it does not proxy the specific IP address of the Rack
PDU.
Logging On to the Web Interface
Overview
You can use the DNS name or System IP address of t he Rack PDU f or the URL address of t he W e b
interface. Use your case-sensitive user name and password to log on.
The default user name and password for the Super User are both apc. For all other user types,
there is no default user name or password. The Super User or an Administrator created by the
Super User, must define the user name and password and other account characteristics for these
users.
Note: If you are using HTTPS (SSL/TLS) as your access protocol, your login credentials are
compared with information in a server certificate. If the certificate was created with the Security
Wizard, and an IP address was specified as the common name in the certificate, you must use an IP
address to log on to the Rack PDU. If a DNS name was specified as the common name on the
certificate, you must use a DNS name to log on.
61 Metered Rack PDU
URL address formats
Type the DNS name or IP address of the Rack PDU in the Web browser’s URL address field and
press
ENTER. When you specify a non-default Web server port in Internet Explorer, you must include
http:// or https:// in the URL.
Common browser error messages at log-on
Error Message Browser Cause of the Error
“This page cannot be displayed.” Internet Explorer Web access is disabled, or the
“Unable to connect.” Firefox
URL format examples
• For a DNS name of Web1:
–
http://Web1 if HTTP is your access mode
–
https://Web1 if HTTPS (HTTP with SSL) is your access mode
• For a System IP address of 139.225.6.133 and the default Web server port (80):
–
http://139.225.6.133 if HTTP is your access mode
–
https//139.225.6.133 if HTTPS (HTTP with SSL) is your access mode
• For a System IP address of 139.225.6.133 and a non-default Web server port (5000):
URL was not correct.
–
http://139.225.6.133:5000 if HTTP is your access mode
–
https://139.225.6.133:5000 if HTTPS (HTTP with SSL) is your access mode
• For a System IPv6 address of 2001:db8:1::2c0:b7ff:fe00:1100 and a non-default Web
server port (5000):
http://[2001:db8:1::2c0:b7ff:fe00:1100]:5000 if HTTP is your access mode
Metered Rack PDU62
Web Interface Features
Read the following to familiarize yourself with basic Web interface features for your Rack PDU.
Tabs
The following tabs are available:
• Home: Appears when you log on (This is the d efault tab when you lo g on. To change the
login page to a different page, click on the green pushpin at the top right side of the
browser window while on the desired page). View active alarms, the load status of the
Rack PDU, and the most recent Rack PDU events. For more information, see “About
Home” on page 66.
• Status: Gives the user the status of the Rack PDU and Network. The RPDU tab covers
the status of alarms, groups, device, phase, bank, and environment. Network t ab covers
just the network. See “Status Tab” on page 67.
• Control: The Control tab covers Security and Network. Much more information is
covered under these tabs and will be described in the Control tab section.
• Configuration: The Configuration tab covers RPDU, Security, Network, Notification,
General and Logs. Much more information is covered under each of these tabs and will
be described in the Configuration tab section.
• Tests: The Tests tab covers Rack PDU and Network. The RPDU tab covers LCD Blink
and the Network tab covers LED Blink. Both will be further described later in the Tests
section of the document.
• Logs: The Logs section covers: Event, Data and Firewall. The Event and Data tabs
cover more information which will be further discussed later in the Logs section of the
document.
• About: The About section covers RPDU and Network, which will be further discussed
later in the About section of the document.
63 Metered Rack PDU
Device status icons
One or more icons and accompanying text indicate the current operating status of the Rack PDU:
Symbol Description
Critical: A critical alarm exists, which requires immediate action.
Warning: An alarm condition requires attention and could jeopard ize your data or
equipment if its cause is not addressed.
No Alarms: No alarms are present, and the Rack PDU and NMC are oper at ing
normally.
At the upper right corner of every page, the web interface displays the same icons currently
displayed on the Home page to report Rack PDU status:
• The No Alarms icon if no alarms exist.
• One or both of the other icons (Critical and Warning) if any alarms exist, and after each
icon, the number of active alarms of that severity.
Quick Links
At the lower left on each page of the interface, there are three configurable links. By default, the links
access the URLs for these Web pages:
• Link 1: The home page of Schneider Electric’s web site
• Link 2: Demonstrations of Schneider Electric Web-enabled products
• Link 3: Information on Schneider Electric Remote Monitoring Service
Located in the upper right hand corner of each page:
• User name (click to change user preferences)
• Language (if available, click to change language preference)
• Log Off (click to log the current user off of the web interface)
• Help (click to view help contents)
• (click to set the current web page to be the log in home page)
Example:
Log In Home: To make any screen the “home” screen (i.e., the screen that displays first
when you log on), go to that screen, and click the icon in the top right corner.
Click to revert to displaying the Home screen when you log on.
Metered Rack PDU64
Network Port Sharing (NPS) on the Web User Interface (UI)
Group Control using Network Port Sharing
The web interface of the Rack PDU will have additional capabilities if the Rack PDU is part of an
NPS group. This includes an NPS Group S tatu s web page and an NPS Group Configuration pag e. In
addition, for web pages that support NPS Rack PDUs, the user can select a different Rack PDU in
the group to view by selecting the Rack PDU Display ID of the unit he or she would like to view.
Each Rack PDU in the NPS group is denoted with a Rack PDU icon followed by its Display ID (1
to 4). The Rack PDU that the user is logged into is displayed with an additional asterisk (*) following
the Display ID.
Note: The Reset/Reboot web page has many additional reset/reboot options for Ra ck PDU group s.
These include individual Rack PDU reset to defaults, individual Rack PDU rebooting, and clearing of
guest PDU lost communication alarms by removing the guests from the group.
65 Metered Rack PDU
About Home
The Home page contains the following information: Active Alarms, Load Status and Recent Device
Events. Active Alarms will show if any alarms exist. If no alarms exist, a green check mark with the
words ”No Alarms Present” will show. The Load Status shows a colored bar demonstrating the level
of the Bank, Phase and Device loads. To see the Device Status select the More link at the bottom of
the list.The Recent Device Events box will list the five most recent device Events by the device by
Date, Time and Event.
The Overview view
In the Load Status area, view the load for the device in kW and for the phases and banks in amps,
as applicable. The green, yellow, and red meter shows the current load status: normal, near
overload, or overload.
Note: If a low load threshold was configured the meter will also include a blue segment to the left of
the green.
In the Rack PDU Parameters box the reader will find the Name, Location, Contact, Model Number,
Rating, User (type of user account accessing the Rack PDU) and Uptime (the amount of time the
Rack PDU has been operating since the last reboot from either a power cycle or a reboot of the
Management Interface).
In the Recent Device Events box are the Events which have occurred most recently and the dates
and times they occurred. A maximum of five Events are shown at one time. Click More Events to go
to the Logs tab to view the entire event log.
Metered Rack PDU66
Status Tab
About the Status Tab
Use the Status tab to:
• View the load status for the Rack PDU and Network Status
• Under the Rack PDU tab readers can scroll and access: Alarms, Device, Phase, Bank,
and Environment.
• Under the Network tab the reader can view the current IPv4 and IPv6 settings.
67 Metered Rack PDU
View the Load Status and Peak Load
Path: Status > RPDU
Alarms:
Group: Network Port sharing Group Status. List the Properties, Metering and firmware version
Lists Device Alarm St atus.
information. Change Host RPDU can be accessed from its link at the bottom of the page.
Device: Shows status of device. Lists Status, Properties and Configuration information.
Phase: Shows Phase Status. The phase settings can also be configured via a Configure Phase
Settings link at the bottom of the page. Configuration can be changed as well.
Bank: Shows bank status. List current size and demonstrates range on a colored red, green and
yellow sliding bar. The bank settings can be changed via a Configure Bank status link at the bottom
of the page.
Environment: Shows Alarm Status, Temperature, Humidity and can configure Temperature and
Humidity Configuration after pressing the Configure link.
View the Network Status
Path: Status > Network
The Network screen displays information about your network.
Current IPv4 Settings
System IPThe IP address of the unit.
Subnet MaskThe IP address of the sub-network.
Default GatewayThe IP address of the router used to connect to the network.
MAC AddressThe MAC address of the unit.
ModeHow the IPv4 settings are assigned: Manual, DHCP, or BOOTP.
DHCP ServerThe IP address of the DHCP server. This is only displayed if Mode is DHCP.
Lease AcquiredThe date/time that the IP address was accepted from the DHCP server.
Lease ExpiresThe date/time that the IP address accepted from the DHCP server expires and will
need to be renewed.
Current IPv6 Settings
TypeHow the IPv6 settings are assigned.
IP AddressThe IP address of the unit.
Prefix LengthThe range of addresses for the sub-network.
Domain Name System Status
Active Primary DNS ServerThe IP address of the primary DNS server.
Active Secondary DNS ServerThe IP address of the secondary DNS server.
Active Host NameThe host name of the active DNS server.
Active Domain Name (IPv4/IPv6)The IPv4/IPv6 domain name that is currently in use.
Active Domain Name (IPv6)The IPv6 domain name that is currently in use.
Ethernet Port Speed
Current Speed. The current speed assigned to the Ethernet port.
Metered Rack PDU68
Control
The Control menu options enable you to take immediate actions affecting active user management
and the security of your network.
Managing User Sessions
Path: Control > Security > Session Management
The Session Management menu displays all active users currently connected to the RPDU. To view
Information about a given user, click their user name. The Session Details screen displays basic
information about the user including what interface they are logged-in to, their IP address, and user
authentication. There is also an option to Terminate Session for the user.
Resetting the Network Interface
Path: Control > Network > Reset/Reboot
This menu gives you the option to reset and reboot various components of the network interface.
Users have the option to Reboot Management Interface,
Note: Rebooting the Management Interface only restarts the Rack PDU’s Network Management
Interface.
Reset All: Clear the Exclude TCP/IP checkbox to reset all configuration values; mark the Exclude
TCP/IP checkbox to reset all values except TCP/IP.
Reset Only: (Resetting may take up to a minute) Options include:
• TCP/IP settings: Set TCP/IP Configuration to DHCP & BOOTP, its default setting,
request requiring that the Rack PDU receive its TCP/IP settings from a DHCP or BOOTP
server. See “View the result of the test DNS in the Last Query Response field.”
• Event configuration: Reset all changes to event configuration, by event and by group,
to their default settings.
• Guest PDU lost communication alarms by removing corresponding guest Rack PDUs.
• Host Display ID and Remove all Guest Rack PDUs.
• RPDU to Defaults.
• For NPS groups:
Guest PDU lost Communication alarms by removing corresponding guest Rack PDUs.
Host Display ID and remove all guest Rack PDUs
Host to Defaults
Guest to Defaults
Guest Management Interface (Reboot)
69 Metered Rack PDU
Configuration
About the Configuration Tab
Under the Configuration tab, several menu options are available to make changes to the
Rack PDUs.
• Configure a name and location for the Rack PDU
• Click user-configurable links to open web pages for specific devices connected to the
Rack PDU
Metered Rack PDU70
Configure Load Thresholds
Path: Main > Configuration > RPDU
View the load for the device, phases, and banks. The indicator in the green, yellow, and red meter
shows the current load status: normal, near overload, or overload. If a low load threshold was
configured, the meter will include a blue segment to the left of the green. When viewing the Device
Load, the triangle above the meter indicates peak load.
Note: The Rack PDU generates an alarm when any bank exceeds its rated value. However, if a
circuit breaker trips, there is no definitive indication that the circuit breaker is open, other than that
the current for that bank will drop. Set the Low Load Warning to 1 amp for these reasons:
• The default setting for the Low Load Warning is 0 amps. This effectively disables the
warning. With a setting of 0 amps for the Low Load Warning, the web interface will not
indicate that a circuit breaker may have tripped.
• A 1 amp detection threshold for the Low Load Warning for Bank Load Management will
help to indicate that a circuit breaker may have tripped.
To configure load thresholds
1. T o configure load thresholds for the device, phases, or banks, make a selection from the
Configuration > RPDU > Device and Phase and Bank drop-down menu.
2. Set Overload Alarm, Near Overload Warning, and Low Load Warning thresholds.
3. Click Apply to save your settings.
Configure RPDU Name and Location
Path: Configuration > RPDU > Device
The name and location you enter will appear on the Home tab.
1. Enter a name and location and contact.
2. Click Apply to save.
Reset Peak Load and kWh
Path: Configuration > RPDU > Device
1. Click the Configuration tab, then RPDU, then Device.
2. Click the Peak Load and Kilowatt-Hours check boxes as desired.
3. Click Apply.
71 Metered Rack PDU
Configure Temperature and Humidity Sensors
Path: Configuration > RPDU > Environment
Note: To use this feature, you must have installed an optional Schneider Electric Temperature
Sensor (AP9335T) or Schneider Electric Temperature/Humidity Sensor (AP9335TH) to your Rack
PDU.
For temperature:
• If the high temperature threshold is reached, the system generates a Warning alarm.
• If the maximum temperature threshold is reached, th e syste m generates a Critical alarm.
Similarly, for humidity:
• If the low humidity threshold is reached, the system generates a Warning alarm.
• If the minimum humidity threshold is reached, the system generates a Critical alarm.
Note: Click the thermometer symbol in the upper right corner to toggle between
Fahrenheit and Celsius.
To configure temperature and humidity sensors:
1. Enter values for minimum, maximum, high, and low thresholds.
2. Enter Hysteresis values.
3. Enable alarm generation as desired.
4. Click Apply.
Hysteresis This value specifies how far past a threshold the temperatu re or humidity must return to
clear a threshold violation.
• For Maximum and High temperature threshold violations, the clearing point is the
threshold minus the hysteresis.
• For Minimum and Low humidity threshold violations, the clearing point is the threshold
plus the hysteresis.
Increase the value for Temperature Hysteresis or Humidity Hysteresis to avoid multiple alarms if
temperature or humidity that has caused a violation then wavers slightly up and down. If the
hysteresis value is too low, such wavering can cause and clear a threshold violation repeatedly.
Example of rising but wavering temperature: The maximum temperature threshold is 85°F, and
the temperature hysteresis is 3°F. The temperature rises above 85°F, violating the threshold. It then
wavers down to 84°F and then up to 86°F repeatedly, but no clearing event and no new violation
occur. For the existing violation to clear, the temperature would have to drop to 82°F (3°F below the
threshold).
Example of falling but wavering humidity: The minimum humidity threshold is 18%, and the
humidity hysteresis is 8%. The humidity falls below 18%, violating the threshold. It then wavers up to
24% and down to 13% repeatedly, but no clearing event and no new violation occur. For the existing
violation to clear, the humidity would have to rise to above 26% (8% past the threshold).
Metered Rack PDU72
Security
Session Management screen
Path: Configuration > Security > Session Management
Enabling Allow Concurrent Logins means that two or more users can log on at the same time.
Each user has equal access and each interface (HTTP, FTP, telnet console, serial console (CLI),
etc.) counts as a logged-in user.
Remote Authentication Override: The Rack PDU supports Radius storage of passwords on a server.
However, if you enable this override, the Rack PDU will allow a local user to log on using the
password for the Rack PDU that is stored locally on the Rack PDU. See also “Local Users” and
“Remote Users authentication”.
Ping Response
Path: Configuration > Security > Ping Response
Select the Enable check box for IPv4 Ping Response to allow the Rack PDU to respond to network
pings. Clear the check box to disable an Rack PDU response. This does not apply to IPv6.
Local Users
Use These menu options to view, and to set up access and individual preferences (like displayed
date format), to the Rack PDU user interfaces. This applies to users as defined by their logon name.
Path: Configuration > Security > Local Users > Management
Setting user access With this option an Administrator or Super User can list and configure the
users allowed access to the UI. The Super User user account always has access to the Rack PDU.
Click on Add User to add a user. On the resulting User Configuration screen, you can add a user
and withhold access by clearing the Access check box. User names and passwords are casesensitive. The maximum length for both the name and password is 64 bytes, with less for multi-byte
characters. You have to enter a password. Blank p asswords, (p asswords with no characters) are not
allowed.
Note: Values greater than 64 bytes in Name and Password might get truncated. To change an
Administrator/Super User setting, you must enter all three password fields.
Use Session Timeo ut to configure the time (3 minutes by default) that the UI waits before logging of f
an inactive user. If you change this value, you must log off for the change to take effect.
Note: This timer continues to run if a user closes the browser window without first logging Off by
clicking Log Off at the upper right.Because that user is still considered to be logged on, no user can
log on until the time specified as Minutes of Inactivity expires. For example, with the default value
for Minutes of Inactivity, if a user closes the browser window without logging off, no user can log on
for 3 minutes.
Serial Remote Authentication Override By selecting this option, you can bypass RADIUS by using
the serial console (CLI) connection. This screen enables it for the selected user, but it must also be
enabled globally to work, (through the “Session Management” screen).
73 Metered Rack PDU
Default settings Determine the default values to populate in each of the fields when the Super User
or Administrator-level account creates a new user. These values can be changed before the settings
are applied to the system.
• Access: Put a check in the Enable box to allow access.
• User Type: Select the user type from the dropdown menu.
• User Description: Type the user Description in the box.
• Session Timeout: Select from 1 to 60 seconds.
• Bad Login Attempts. Set the number of failed login attempts the user can have. Select
from 0 to 99 attempts. 0= unlimited.
User Preferences This option is enabled by default.
• Event Log Color Coding: Mark the checkbox to enable color-coding of alarm text
recorded in the event log. System event entries and configuration change entries do not
change color.
Text Color Alarm Severity
Red Critical: A critical alarm exists, which requires immediate action.
Orange
Green Alarm Cleared: The conditions that caused the alarm have improved.
Black
Warning: An alarm condition requires attention and could jeopardize
your data or equipment if its cause is not addressed.
Normal: No alarms are present. The Rack PDU and all connected
devices are operating normally.
• Change the default temperature scale: Select the temperature scale, US Customary
(Fahrenheit) or Metric (Celsius), in which to display all temperature measurements in
this user interface.
• Export Log Format: Configure which format the event log should be displayed in when
exported (downloaded). Tab (default) allows fields to be tab-delimited whereas CSV is
comma-separated.
• Date Format: Select the numerical format in which to display all dates in this user
interface. In the selections, each letter m (for month), d (for day), and y (for year)
represents one digit. Single-digit days and months are displayed with a leading zero.
• Language: Select the user interface display languages from the drop-down box.
Password Requirements
• Strong Passwords: Configure whether new passwords created for user accounts will
require additional rules such as at least one lowercase character, one uppercase
character, one number, and one symbol.
• Password Policy: Select the duration (in days) to which the user will be required to
change their password. A value of 0 days disables this feature (by default).
Metered Rack PDU74
Remote Users
Authentication Specify how you want users to be authenticated at logon.
Path: Configuration > Security > Remote Users > Authentication
For information about local authentication (not using the centralized authentication of a RADIUS
server), see the Security Handbook, available at www.schneider-electric.com.
The authentication and authorization functions of RADIUS (Remote Authentication Dial-In User
Service) is supported.
• When a user accesses the Rack PDU or other network-enabled device that has RADIUS
enabled, an authentication request is sent to the RADIUS server to determine the User
permission level.
• RADIUS user names used with the Rack PDU are limited to 32 characters.
Select one of the following:
• Local Authentication Only: RADIUS is disabled. Local authentication is enabled.
• RADIUS, then Local Authentication: RADIUS and local authentication are enabled.
Authentication is requested from the RADIUS server first. If the RADIUS server fails to
respond, local authentication is used.
• RADIUS Only: RADIUS is enabled. Local authentication is disabled.
Note: If RADIUS Only is selected, and the RADIUS server is unavailable, or improperly
configured, remote access is unavailable to all users. You must use a serial connection
to the command line interface and change the access setting to local or radiusLocal to
regain access. For example, the command to change the access setting to local would
be: radius -a local
RADIUS
Path: Configuration > Security > Remote Users > RADIUS
Use this option to do the following:
• List the RADIUS servers (a maximum of two) available to the Rack PDU an d the time-out
period for each.
• Click on a link, and configure the parameters for authentication by a new RADIUS server.
• Click a listed RADIUS server to display and modify its parameters.
RADIUS Setting Definition
RADIUS Server The server name or IP address (IPv4 or IPv6) of the RADIUS server.
Click on a link to configure the server.
Note: RADIUS servers use port 1812 by default to authenticate users.
The Rack PDU supports ports 1812, 5000 to 32768.
Secret The shared secret between the RADIUS server and the Rack PDU.
Reply Timeout The time in seconds that the Rack PDU waits for a response from the
RADIUS server.
Test Settings Enter the Administrator user name and password to test the RADIUS
server path that you have configured.
Skip Test and Apply Do not test the RADIUS server path. (Not recommended)
75 Metered Rack PDU
Configure the RADIUS Server
Summary of the configuration procedure
You must configure your RADIUS server to work with the Rack PDU.
For examples of the RADIUS users file with V endor Specific Attributes (VSAs) and an example of an
entry in the dictionary file on the RADIUS server, see the Security Handbook.
1. Add the IP address of the Rack PDU to the RADIUS server client list (file).
2. Users must be configured with Service-Type attributes unless Vendor Specific Attributes
(VSAs) are defined. If no Service-Type attributes are configured, users will have readonly access (on the Web interface only).
See your RADIUS server documentation for information about the RADIUS users file,
and see the Security Handbook for an example.
3. VSAs can be used instead of the Service-Type attributes provided by the RADIUS
server. VSAs require a dictionary entry and a RADIUS users file. In the dictionary file,
define the names for the ATTRIBUTE and VALUE keywords, but not for the numeric
values. If you change numeric values, RADIUS authentication and authorization will fail.
VSAs take precedence over standard RADIUS attributes.
Configuring a RADIUS server on UNIX® with shadow passwords
If UNIX shadow password files are used (/etc/passwd) with the RADIUS dictionary files, the following
two methods can be used to authenticate users:
• If all UNIX users have administrative privileges, add the following to the RADIUS “user”
file. To allow only Device Users, change the APC-Service-Type to
DEFAULT Auth-Type = System
APC-Service-Type = Admin
Device.
• Add user names and attributes to the RADIUS “user” file, and verify the password
against /etc/passwd. The following example is for users
bconners Auth-Type = System
APC-Service-Type = Admin
thawk Auth-Type = System
APC-Service-Type = Device
bconners and thawk:
Supported RADIUS servers
FreeRADIUS and Microsoft IAS 2003 are supported. Other commonly available RADIUS
applications may work but have not been fully tested.
RADIUS and Network Port Sharing
Note: See the Security Handbook for Network Management Cards for more information on using
RADIUS.
Metered Rack PDU76
Firewall Menus
Path: Configuration > Security > Firewall
Configuration
Enable or disable the overall firewall functionality. Any configured policy is also
listed, even if the firewall is disabled.
Active Policy Select an a ctive policy from the available firewall policies. The validity of policy is also
listed here.
Active Rules When a firewall is enabled, this lists the individual rules that are being enforced by a
current active policy. You can edit existing rules and add or delete new rules here.
Create/Edit Policy Create a new policy or edit an existing one.
Load Policy Load a policy (with .fwl suffix) from a source external to this device.
Test Temporarily enforce the rules of a chosen policy for a time that you specify.
77 Metered Rack PDU
Network Features
TCP/IP and Communication Settings
TCP/IP
Path: Configuration > Network > TCP/IP
The TCP/IP option on the left navigation menu, selected by default when you choose Network on
the top menu bar, displays the current IPv4 address, subnet mask, default gateway, MAC address,
and boot mode of the Rack PDU. For information on DHCP and DHCP options, see RFC2131 and
RFC2132.
Setting Description
Enable Enable or disable IPv4 with this check box.
Manual Configure IPv4 manually by entering the IP address, subnet mask, and default gateway.
BOOTP A BOOTP server provides the TCP/IP settings. At 32-second intervals, the Rack PDU
requests network assignment from any BOOTP server:
• If the Rack PDU receives a valid response, it starts the network services.
• If the Rack PDU finds a BOOTP server, but a request to that server fails or times out, the
Rack PDU stops requesting network settings until it is restarted.
• By default, if previously configured network settings exist, and the Rack PDU receives no
valid response to five requests (the original and four retries), it uses the previously
configured settings so that it remains accessible.
Click Next>> to access the BOOTP Configuration page to change the number of retries or
the action to take if all retries fail :
• Maximum retries: Enter the number of retries that will occur when no valid response is
received, or zero (0) for an unlimited number of retries.
• If retries fail: Select
DHCP The default setting. At 32-second intervals, the Rack PDU requests network assignment
from any DHCP server.
• If the Rack PDU receives a valid response, it does not (as previously) require the APC
cookie from the DHCP server in order to accept the lease and start the network services.
• If the Rack PDU finds a DHCP server, but the request to that server fails or times out, it
stops requesting network settings until it is restarted.
• Require vendor specific cookie to accept DHCP Address: By selecting this check box,
you can require the DHCP server to provide a cookie which supplies information to the
Rack PDU.
1.
The default values for these three settings on the configuration pages generally do not need to be
changed:
Use prior settings (the default) or Stop BOOTP request.
1
1
•Vendor Class: APC
•Client ID: The MAC address of the Rack PDU, which uniquely identifies it on the local area network
(LAN)
•User Class: The name of the application firmware module
Metered Rack PDU78
DHCP response options
Each valid DHCP response contains options that provide the TCP/IP settings that the Rack PDU
needs to operate on a network, and other information that affects the operation of the Rack PDU.
Vendor Specific Information (option 43) The Rack PDU uses this option in a DHCP response to
determine whether the DHCP response is valid. This option contains an APC-specific option in a
TAG/LEN/DATA format, called the APC Cookie. This is disabled by default.
• APC Cookie. Tag 1, Len 4, Data “1APC”
Option 43 communicates to the Rack PDU that a DHCP server is configured to service devices.
Following, in hexadecimal format, is an example of a V endor S pecific I nformation option that contains
the APC cookie:
Option 43 = 0x01 0x04 0x31 0x41 0x50 0x43
TCP/IP options The Rack PDU uses the following options within a valid DHCP response to define
its TCP/IP settings. All of these options except the first are described in RFC2132.
• IP Address (from the yiaddr field of the DHCP response, described in RFC2131): The
IP address that the DHCP server is leasing to the Rack PDU.
• Subnet Mask (option 1): The Subnet Mask value that the Rack PDU needs to operate on
the network.
• Router, i.e., Default Gateway (option 3): The default gateway address that the Rack
PDU needs to operate on the network.
• IP Address Lease T ime (option 51): The time du ration for the lease of the IP Address to
the Rack PDU.
• Renewal Time, T1 (option 58): The time that the Rack PDU must wait after an IP
address lease is assigned before it can request a renewal of that lease.
• Rebinding Time, T2 (option 59): The time that the Rack PDU must wait after an IP
address lease is assigned before it can seek to rebind that lease.
Other options The Rack PDU also uses these options within a valid DHCP response. All of these
options except the last are described in RFC2132.
• Network Time Protocol Servers (option 42): Up to two NTP servers (primary and
secondary) that the Rack PDU can use.
• Time Offset (option 2): The offset of the Rack PDU's subnet, in seconds, from
Coordinated Universal Time (UTC).
• Domain Name Server (option 6): Up to two Domain Name System (DNS) servers
(primary and secondary) that the Rack PDU can use.
• Host Name (option 12): The host name that the Rack PDU will use (32-character
maximum length).
• Domain Name (option 15): The domain name that the Rack PDU will use (64-character
maximum length).
• Boot File Name (from the file field of the DHCP response, described in RFC2131): The
fully qualified directory-path to a user configuration file (.ini file) to download. The siaddr
field of the DHCP response specifies the IP address of the server from which the Rack
PDU will download the .ini file. After the download, the .ini file is used as a boot file to
reconfigure the settings.
79 Metered Rack PDU
Path: Configuration > Network > TCP/IP > IPv6 settings
Setting Description
Enable Enable or disable IPv6 with this check box.
Manual Configure IPv6 manually by entering the IP address and the default gateway.
Auto
Configuration
DHCPv6
Mode
When the Auto Configuration check box is selected, the system obtains addressing
prefixes from the router (if available). It uses those prefixes to automatically configure
IPv6 addresses.
Router Controlled: Selecting this option means that DHCPv6 is controlled by the
Managed(M) and Other(O) flags received in IPv6 router advertisements. When a
router advertisement is received, the NMC checks whether the M or the O flag is set.
The NMC interprets the state of the M (Managed Address Configuration Flag) and O
(Other Stateful Configuration Flag) "bits" for the following cases:
• Neither is set: Indicates the local network has no DHCPv6 infrastructure. The NMC
uses router advertisements and manual configuration to get addresses that are not
link-local and other settings.
• M, or M and O are set: In this situation, full DHCPv6 address configuration occurs.
DHCPv6 is used to obtain addresses AND other configuration settings. This is known
as DHCPv6 stateful. Once the M flag has been received, the DHCPv6 address
configuration stays in effect until the interface in question has been closed. This is
true even if subsequent router advertisement packets are received in which the M
flag is not set.
If an O flag is received first, then an M flag is received subsequently, the NMC
performs full address configuration upon receipt of the M flag
• Only O is set: In this situation, the NMC sends a DHCPv6 Info-Request packet.
DHCPv6 will be used to configure “other” settings (such as location of DNS servers),
but NOT to provide addresses. This is known as DHCPv6 stateless.
Address and Other Information: With this radio box selected, DHCPv6 is used to
obtain addresses AND other configuration settings. This is known as DHCPv6
stateful.
Non-Address Information Only: With this radio box selected, DHCPv6 will be used
to configure "other" settings (such as location of DNS servers), but NOT to provide
addresses. This is known as DHCPv6 stateless.
Never: Select this to disable DHCPv6.
Port Speed
Path: Configuration > Network > Port Speed
The Port Speed setting defines the communication speed of the TCP/IP port.
• For Auto-negotiation (the default), Ethernet devices negotiate to transmit at the highest
possible speed, but if the supported speeds of two devices are unmatched, the slower
speed is used.
• Alternatively, you can choose 10 Mbps or 100 Mbps, each with the option of half-duplex
(communication in only one direction at a time) or full-duplex (communication in both
directions on the same channel simultaneously).
Metered Rack PDU80
DNS
Path: Configuration > Network > DNS > Configuration
Use the options under Configuration to configure and test the Domain Name System (DNS):
• Override Manual DNS Settings: Selection of Override Manual DNS Settings will result
in configuration data from other sources (typically DHCP) taking precedence over the
manual configurations set here.
• Select Primary DNS Server or Secondary DNS Server to specify the IPv4 or IPv6
addresses of the primary and optional secondary DNS server. For the Rack PDU to send
e-mail, you must at least define the IP
– The Rack PDU waits up to 15 seconds for a response from the primary DNS server or
secondary DNS server (if specified). If the Rack PDU does not receive a response
within that time, e-mail cannot be sent. Use DNS servers on the sa me segment as the
Rack PDU or on a nearby segment (but not across a wide-area network [WAN]).
– Define the IP addresses of the DNS servers then enter the DNS name of a computer
on your network to look up the IP address for that computer to verify correct
operation.
• System Name Synchronization: Allow the system name to be synchronized with the
host name so both fields automatically contain the same value.
Note: When enabling this feature, the system name identifier can no longer contain a
space character (since it will be synchronized to the host name field).
address of the primary DNS server.
• Host Name: Configure a host name here and a domain name in the Domain Name field
then users can enter a host name in any field in the NMC interface (except e-mail
addresses) that accepts a domain name.
• Domain Name (IPv4/IPv6): Configure the domain name here only. In all other fields in
the NMC interface (except e-mail addresses) that accept domain names, the Rack PDU
adds this domain name when only a host name is entered.
– To override all instances of the expansion of a specified host name by the addition of
the domain name, set the domain name field to its default, somedomain.com, or to
0.0.0.0.
– To override the expansion of a specific host name entry, include a trailing period. The
NMC recognizes a host name with a trailing period (such as mySnmpServer.) as if it
were a fully-qualified domain name and does not append the domain name.
• Domain Name (IPv6): Specify the IPv6 domain name here.
Test
Path: Configuration > Network > DNS > Test
Use this option to send a DNS query that tests the setup of your DNS servers by looking up the IP
address. View the result of a test in the Last Query Response field.
• Select test to send a DNS query that tests the setup of your DNS servers:
–As Query Question, identify the value to be used for the selected query type:
Query Type Selected Query Question to Use
by Host The URL
by FQDN The fully qualified domain name, my_server.my_domain
by IP The IP address
by MX The Mail Exchange address
81 Metered Rack PDU
Web
Path: Configuration > Network > Web > Configuration
Option Description
access To activate ch anges to any of these selections, log off from the Rack PDU:
• Disable: Disables access to the Web interface. (To re-enable access, log in to the
command line interface, then type the com m a nd http -S enable. For HTTPS
access, type https -S enable.)
• Enable HTTP (the default): Enables Hypertext Transfer Protocol (HTTP), which
provides Web access by user name and password, but does not encrypt user names,
passwords, and data during transmission.
• Enable HTTPS: Enables Hypertext Transfer Protocol (HTTPS) over Secure Sockets
Layer (SSL). SSL encrypts user names, passwords, and data during transmission, and
authenticates the Rack PDU by digital certificate. When HTTPS is enabled, your
browser displays a small lock icon.
See “Creating and Installing Digital Certificates” in the Security Handbook, available at
www.schneider-electric.com.
HTTP Port: The TCP/IP port (80 by default) used to communicate by HTTP with the Rack
PDU.
HTTPS Port: The TCP/IP port (443 by default) used to communicate by HTTPS with the
Rack PDU.
ssl
certificate
For either of these ports, you can change the port setting to any unused port fro m 5000 to
32768 for additional security. Users must then use a colon (:) in the address field of the
browser to specify the port number. For example, for a port number of 5000 and an IP
address of 152.214.12.114:
http://152.214.12.114:5000
https://152.214.12.114:5000
Add, replace, or remove a security certificate.
Status:
• Not installed: A certificate is not installed, or was installed by FTP or SCP to an
incorrect location. Using Add or Replace Certificate File installs the certificate to the
correct location, /ssl on the Rack PDU.
• Generating: The Rack PDU is generating a certificate because no valid certificate was
found.
• Loading: A certificate is being activated on the Rack PDU.
• Valid certificate: A valid certificate was installed or was generated by the Rack PDU.
Click on this link to view the contents of the certificate.
If you install an invalid certificate, or if no certificate is loaded when you enable
SSL, the Rack PDU generates a default certificate, a process which delays access
to the interface for up to one minute. You can use the default certificate for basic
encryption-based security, but a security alert message displays whenever you log on.
Add or Replace Certificate File: Enter or browse to the certificate file created with the
Security Wizard.
See “Creating and Installing Digital Certificates” in the Security Handbook, available at
www.schneider-electric.com, to choose a method for using digital certificates created
by the Security Wizard or generated by the Rack PDU.
Remove: Delete the current certificate.
Metered Rack PDU82
Console
Path: Configuration > Network > Console >
Option Description
access • Disable: Disables all access to the command line interface.
• Enable Telnet (the default): Telnet transmits user names, passwords, and data without
encryption.
• Enable SSH: SSH transmits user names, passwords, and data in encrypted form,
providing protection from attempts to intercept, forge, or alter data during transmission.
Configure the ports to be used by these protocols:
• Telnet Port: The Telnet port used to com m u nic ate with the Ra ck PDU (2 3 by de fa u lt).
You can change the port setting to any unused po rt from 5000 to 32768 for additional
security. Users must then use a colon (:) or a space, as required by your Telnet client
program, to specify the non-default port. For example, for port 5000 and an IP address of
152.214.12.114, your Telnet client requires one of the these commands:
• SSH Port: The SSH port used to communicate with the Rack PDU (22 by default). You
can change the port setting to any unused port from 5000 to 32768 for additional
security. See the documentation for your SSH client for the command line format
required to specify a non-default port.
options
telnet 152.214.12.114:5000
telnet 152.214.12.114 5000
ssh host
key
Status indicates the status of the host key (private key):
• SSH Disabled: No host key in use: When disabled, SSH cannot use a host key.
• Generating: The Rack PDU is creating a host key because no valid host key was found.
• Loading: A host key is being activated on the Rack PDU.
• Valid: One of the following valid host keys is in the /ssh directory (the required location
on the Rack PDU):
•A 1024-bit or 2048-bit host key created by the Security Wizard
•A 2048-bit RSA host key generated by the Rack PDU
Add or Replace: Browse to and upload a host key file created by the Security Wizard.
To use the Security Wizard, see the Security Handbook, available at www.schneider-
electric.com.
Note: To reduce the time required to enable SSH, create and upload a host key in
advance. If you enable SSH with no host key loaded, the Rack PDU takes up to one
minute to create a host key, and the SSH server is not accessible during that time.
Remove: Remove the current host key.
Note: To use SSH, you must have an SSH client installed. Most Linux and other UNIX platforms
include an SSH client, but Microsoft Windows operating systems do not. Clients are available from
various vendors.
83 Metered Rack PDU
SNMP
All user names, passwords, and community names for SNMP are transferred over the network as
plain text. If your network requires the high security of encryption, disable SNMP access or set the
access for each community to Read. (A community with Read access can receive st atus information
and use SNMP traps.)
When using StruxureWare to manage a Rack PDU on the public network, you must have SNMP
enabled in the Rack PDU interface. Read access will allow the StruxureWare to receive traps from
the Rack PDU, but Write access is required while you use the interface of the Rack PDU to set the
StruxureWare as a trap receiver.
For detailed information on enhancing and managing the security of your system, see the Security
Handbook, available at www.schneider-electric.com.
Network Port Sharing
All Rack PDUs in a group can be accessed through the Host Rack PDU via SNMP "rPDU2" OIDs
available in our PowerNet-MIB.
The full path to these OIDs is:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).apc(318).products(1).hardware(1).rPDU2(2
6)
Individual Rack PDUs can be identified in the SNMP MIB tables by viewing the corresponding
"Module" OIDs in each table. These Module OIDs will return the Display ID of the Rack PDU.
Example Module OIDs: rPDU2IdentModule, rPDU2DeviceConfigModule,
rPDU2SensorTempHumidityConfigModule
In order to be backwards compatible with previous versions, the Host Rack PDU will always be the
first index in any table that supports multiple Rack PDUs. In addition, after the Rack PDU group is set
up, the index order of guest Rack PDUs should not change even if the Display ID is changed or a
Rack PDU temporarily loses communication. The index order should only change if you manually
remove a Rack PDU from the group.
A MIB table walk should skip the indexes associated with a Rack PDU that has temporarily lost
communication.
Metered Rack PDU84
SNMPv1
Path: Configuration > Network > SNMPv1 > options
Option Description
access Enable SNMPv1 Access: Enables SNMP version 1 as a method of communication with
this device.
access
control
You can configure up to four access control entries to specify which Network
Management Systems (NMSs) have access to this device. The opening page for access
control, by default, assigns one entry to each of the four available SNMPv1 communities,
but you can edit these settings to apply more than one entry to any community to grant
access by several specific IPv4 and IPv6 addresses, host names, or IP address masks.
To edit the access control settings for a community, click its community name.
• If you leave the default access control entry unchanged for a community, that
community has access to this device from any location on the network.
• If you configure multiple access control entries for one community name, the limit of
four entries requires that one or more of the other communities must have no access
control entry . If no access control entry is listed for a community , that community has no
access to this device.
Community Name: The name that an NMS must use to access the community. The
maximum length is 15 ASCII characters, and the default community names for the four
communities are public, private, public2, and private2.
NMS IP/Host Name: The IPv4 or IPv6 address, IP address mask, or host name that
controls access by NMSs. A host name or a specific IP address (such as 149.225.12.1)
allows access only by the NMS at that location. IP addresses that contain 255 restrict
access as follows:
• 149.225.12.255: Access only by an NMS on the 149.225.12 segment.
• 149.225.255.255: Access only by an NMS on the 149.225 segment.
• 149.255.255.255: Access only by an NMS on the 149 segment.
• 0.0.0.0 (the default setting) which can also be expressed as 255.255.255.255: Access
by any NMS on any segment.
Access Type: The actions an NMS can perform through the community.
• Read: GETS only, at any time
• Write: GETS at any time, and SETS when no user is logged onto the Web interface or
command line interface.
• Write+: GETS and SETS at any time.
• Disable: No GETS or SETS at any time.
85 Metered Rack PDU
SNMPv3
Path: Configuration > Network > SNMPv3 > options
For SNMP GETs, SET s, and trap receivers, SNMPv3 uses a system of user profiles to identify users.
An SNMPv3 user must have a user profile assigned in the MIB software program to perform GETs
and SETs, browse the MIB, and receive traps.
Note: To use SNMPv3, you must have a MIB program that supports SNMPv3.
The Rack PDU supports SHA or MD5 authentication and AES or DES encryption.
Option Description
access SNM P v3 Ac ce ss : Enables SNMPv3 as a method of communication with this device.
user
profiles
By default, lists the settings of four user profiles, configured with the user names apc
snmp profile1 through apc snmp profile4, and no authentication and no privacy (no
encryption). To edit the following settings for a user profile, click a user name in the list.
User Name: The identifier of the user profile. SNMP version 3 maps GETs, SETs, and
traps to a user profile by matching the user name of the profile to the user name in the
data packet being transmitted. A user name can have up to 32 ASCII charac te rs.
Authentication Passphrase: A phrase of 15 to 32 ASCII characters (apc auth
passphrase, by default) that verifies that the NMS communicating with this device
through SNMPv3 is the NMS it claims to be, that the message has not been changed
during transmission, and that the message was communicated in a timely manner,
indicating that it was not delayed and that it was not copied and sent again later at an
inappropriate time.
Privacy Passphrase: A phrase of 15 to 32 ASCII ch ar ac te rs (apc crypt
passphrase, by default) that ensures the privacy of the data (by means of encryption)
that an NMS is sending to this device or receiving from this device through SNMPv3.
Authentication Protocol: The Schneider Electric implementation of SNMPv3 supports
SHA and MD5 authentication. Authentication will not occur unless an authentication
protocol is selected.
Privacy Protocol: The implementation of SNMPv3 supports AES and DES as the
protocols for encrypting and decrypting data. Privacy of transmitted data requires that a
privacy protocol is selected and that a privacy passphrase is provided in the request from
the NMS. When a privacy protocol is enabled but the NMS does not provide a privacy
passphrase, the SNMP request is not encrypted.
Note: You cannot select the privacy protocol if no authentication protocol is selected.
Metered Rack PDU86
Option Description
access
control
Y ou can con figure up to four access control entries to specify which NMSs ha ve access to
this device. The opening page for access contro l, by default, assig ns one entry to each of
the four user profiles, but you can edit these settings to apply more than one entry to any
user profile to grant access by several specific IP addresses, host names, or IP address
masks.
• If you leave the default access control entry unchanged for a user profile, all NMSs that
use that profile have access to this device.
• If you configure multiple access entries for one user profile, the limit of four entries
requires that one or more of the other user profiles must have no access control entry. If
no access control entry is listed for a user profile, no NM S that uses that profile has any
access to this device.
To edit the access control settings for a user profile, click its user name.
Access: Mark the Enable checkbox to activate the access control specified by the
parameters in this access control entry.
User Name: From the drop-down list, select the user profile to which this access control
entry will apply. The choices available are the four user names that you configure through
the user profiles option on the left navigation menu.
NMS IP/Host Name: The IP address, IP address mask, or host name that controls
access by the NMS. A host name or a specific IP address (such as 149.225.12.1) allows
access only by the NMS at that location. An IP address mask that contains 255 restricts
access as follows:
• 149.225.12.255: Access only by an NMS on the 149.225.12 segment.
• 149.225.255.255: Access only by an NMS on the 149.225 segment.
• 149.255.255.255: Access only by an NMS on the 149 segment.
• 0.0.0.0 (the default setting) which can also be expressed as 255.255.255.255: Access
by any NMS on any segment.
FTP Server
Path: Configuration > Network > FTP Server
The FTP Server settings enable (by defa ult) or disable access to the FTP server and specify the TCP/
IP port (21 by default) that the FTP server uses to communicate with the Rack PDU. The FTP server
uses both the specified port and the port one number lower than the specified port.
You can change the Port setting to the number of any unused port from 5001 to 32768 for added
security. Users must then use a colon (:) to specify the non-default port number. For example, for
port 5001 and IP address 152.214.12.114, the command would be
Note: FTP transfers files without encryption. For higher security , disable the FTP server , and transfer
files with SCP. Selecting and configuring Secure SHell (SSH) enables SCP automatically.
At any time that you want a Rack PDU to be accessible for management by StruxureWare, FTP
Server must be enabled in the Rack PDU interface.
For detailed information on enhancing and managing the security of your system, see the Security
Handbook, available at www.schneider-electric.com.
ftp 152.214.12.114:5001.
87 Metered Rack PDU
Notifications
Event Actions
Path: Configuration > Notification
Types of notification
You can configure event actions to occur in response to an event or group of events. These actions
notify users of the event in any of several ways:
• Active, automatic notification. The specified users or monitoring devices are contacted
directly.
– E-mail notification
–SNMP traps
– Remote Monitoring Service
– Syslog notification
• Indirect notification
– Event log. If no direct notification is configured, users must check the log to determine
which events have occurred
You can also log system performance d at a to use for device mo nitoring. See “Logs in
the Configuration Menu” on page 96 for information on how to configure and use this
data logging option.
– Queries (SNMP GETs)
For more information, see “SNMP” on page 84. SNMP enables an NMS to perform
informational queries. For SNMPv1, which does not encrypt dat a before transmission,
configuring the most restrictive SNMP access type (READ) enables informational
queries without the risk of allowing remote configuration changes.
Configure event actions
Path: Configuration > Notification > Event Actions > By Event
By default, logging an event is selected for all events. To define event actions for an individual event:
1. To find an event, click on a column heading to see the lists under the Device Events or
System Events categories.
Or you can click on a sub-category under these headings, like Security or
Temperature.
2. Click on the event name to view or change the current configuration, such as recipients
to be notified by e-mail, or Network Management Systems (NMSs) to be notified by
SNMP traps.
If no Syslog server is configured, items related to Syslog configuration are not displayed.
Note: When viewing details of an event configuration, you can enable or disable event logging or
Syslog, or disable notification for specific e-mail recipients or trap receivers, but you cannot add or
remove recipients or receivers. To add or remove recipients or receivers, see the following:
• “Identifying Syslog servers” on page 96
• “Path: Configuration > Notification > E-mail > Recipients” on page 91
• “Path: Configuration > Notification > SNMP Traps > Trap Receivers” on page 92
Metered Rack PDU88
Path: Configuration > Notification > Event Actions > By Group
To configure a group of events simultaneously:
1. Select how to group events for configuration:
– Select Events by Severity, and then select one or more severity levels. You cannot
change the severity of an event.
– Select Events by Category, and then select all events in one or more pre-defined
categories.
2. Click Next to move to the next screen to do the following:
a. Select event actions for the group of events.
• To select any action except Logging (the default), you must first have at least one
relevant recipient or receiver configured.
• If you selected Logging and have configured a Syslog server, select Event Log
or Syslog on the next screen. See “Logs in the Configuration Menu” on page 96
3. Click Next to move to the next screen to do the following:
a. If you selected Logging on the previous screen, select Enable Notifications or
Disable Notification.
b. If you selected Email Recipients on the previous screen, select the e-mail
recipients to configure.
c. If you selected Trap Receivers on the previous screen, select the trap receiver to
configure.
4. Click Next to move to the next screen to do the following:
a. If you are configuring Logging settings, view the pending actions and click Apply
to accept the changes or click Cancel to revert to the previous settings.
b. If you are configuring Email Recipients or Trap Receivers, select Enable
Notifications or Disable Notification and set the notification timing settings (see
“Notification parameters” on page 90 for more information on these settings).
5. Click Next to move to the next screen to do the following:
a. View the pending actions and click Apply to accept the changes or click Cancel to
revert to the previous settings.
89 Metered Rack PDU
Notification parameters. These configuration fields define e-mail parameters for sending
notifications of events.
They are usually accessed by clicking the receiver or recipient name.
Field Description
Delay n time before
sending
Repeat at an interval of n The notification is sent repeatedly at the specified interval (the default is
Up to n times During an active event, the notification repeats for this number of times.
or
Until condition clears The notification is sent repeatedly until the condition clears or is
If the event persists for the specified time, the notification is sent. If the
condition clears before the time expires, no notification is sent.
every 2 minutes until the condition clears).
resolved.
Note: For events that have an associated clearing event, you can also set these parameters.
E-mail notification screens
Use Simple Mail Transfer Protocol (SMTP) to send e-mail to up to four recipients when an event
occurs. To use the e-mail feature, you must define the following settings:
• The IP addresses of the primary and, optionally, the secondary Domain Name System
(DNS) servers.
• The IP address or DNS name for the SMTP Server and From Address.
• The e-mail addresses for a maximum of four recipients.
• Y ou can use the To Address setting of the recipients option to send e-mail to a text-based
screen.
Path: Configuration > Notification > E-mail > Server
This screen lists your primary and secondary DNS servers and displays the following fields:
From Address. The contents of the From field in e-mail messages sent by the RPDU:
• In the format user@ [IP_address] (if an IP address is specified as Local SMTP Server)
• In the format user@domain (if DNS is configured and the DNS name is specified as
Local SMTP Server) in the e-mail messages.
Note: The local SMTP server may require that you use a valid user account on the
server for this setting. See the server documentation.
SMTP Server. The IPv4/ IPv6 address or DNS name of the local SMTP server.
Note: This definition is required only when the SMTP server is set to Local.
Authentication. Enable this if the SMTP server requires authentication.
Port. The SMTP port number, with a default of 25. The range is 25, 465, 587, 5000 to 32768.
User Name, Password, and Confirm Password. If your mail server requires authentication, enter
your user name and password here. This performs a simple authentication, not SSL.
Metered Rack PDU90
Use SSL/TLS. Select when encryption is used.
• Never: The SMTP server does not require nor support encryption.
• If Supported: The SMTP server advertises support for STARTTLS but doesn't require
the connection to be encrypted. The STARTTLS command is sent after the
advertisement is given.
• Always: The SMTP server requires the STARTTLS command to be sent on connection
to it.
• Implicitly: The SMTP server only accepts connections that begin encrypted. No
STARTTLS message is sent to the server.
Require CA Root Certificate. This should only be enabled if the security policy of your organization
does not allow for implicit trust of SSL connections. If this is enabled, a valid root CA certificate must
be loaded onto the RPDU for encrypted e-mails to be sent.
File Name. This field is dependent on the root CA certificates installed on the RPDU and whether or
not a root CA certificate is required.
Path: Configuration > Notification > E-mail > Recipients
Specify up to four e-mail recipients. Click on a name to configure the settings.
Generation Enables (default) or disables sending e-mail to the recipient.
To Address The user and domain names of the recipient. To use e-mail for paging, use the e-mail
address for the recipient’s pager gateway account (for example,
myacct100@skytel.com). The
pager gateway will generate the page.
To bypass the DNS lookup of the IP address of the mail server, use the IP address in brackets
instead of the e-mail domain name, e.g., use jsmith@[xxx.xxx.x.xxx] instead of
jsmith@company.com. This is useful when DNS lookups are not working correctly.
Language The language which the e-mail notification will be sent in. This is dependent on the
installed language pack (if applicable).
Port The SMTP port number, with a default of 25. The range is 25, 465, 587, 5000 to 32768.
Format: The long format contains name, location, cont act, IP address, serial number of the device,
date and time, event code, and event description. The short format provides only the event
description.
Server Select one of the following methods for routing e-mail:
• Local: This is through the site-local SMTP server. This recommended setting ensures
that the e-mail is sent using the site-local SMTP server. Choosing this setting limits
delays and network outages and retries sending e-mail for many hours. When choosing
the Local setting you must also enable forwarding at the SMTP server of your device and
set up a special external e-mail account to receive the forwarded e-mail. Check with your
SMTP server administrator before making these changes.
• Recipient: This is the SMTP server of the recipient. The RPDU performs an MX record
look-up on the recipients e-mail address and uses that as its SMTP server. The e-mail is
only sent once so it could easily be lost.
• Custom: This setting enables each e-mail recipient to have its own server settings.
These settings are independent of the settings given under “SMTP Server” above.
91 Metered Rack PDU
Path: Configuration > Notification > E-mail > SSL Certificates
Load a mail SSL certificate on the RPDU for greater security. The file must have an extension of
.crt or .cer. Up to five files can be loaded at any given time.
When installed, the certificate details also display here. An invalid certificate will display “n/a” for all
fields except File Name.
Certificates can be deleted using this screen. Any e-mail recipients using the certificate should be
manually modified to remove reference to this certificate.
Path: Configuration > Notification > E-mail > Test
Send a test message to a configured recipient.
SNMP trap receiver screen
Path: Configuration > Notification > SNMP Traps > Trap Receivers
With Simple Network Management Protocol (SNMP) traps, you can automatically get notifications for
significant RPDU events. They are a useful tool for monitoring devices on your network.
The trap receivers are displayed by NMS IP/Host Name, where NMS stands for Network
Management System. You can configure up to six trap receivers.
To configure a new trap receiver, click Add Trap Receiver. To edit (or delete) one, click its IP
address/host name.
Trap Generation. Enable (the default) or disable trap generation for this trap receiver.
NMS IP/Host Name. The IPv4/ IPv6 address or host name of this trap receiver. The default, 0.0.0.0,
leaves the trap receiver undefined.
Language. Select a language from the drop-down list. This can differ from the UI and from other trap
receivers.
Select either the SNMPv1 or SNMPv3 radio button to specify the trap type. For an NMS to receive
both types of traps, you must separately configure two trap receivers for that NMS, o ne for each trap
type.
SNMPv1. Settings for SNMPv1.
• Community Name: The name (“public” by default) used as an identifier when SNMPv1
traps are sent to this trap receiver.
• Authenticate Trap s: When this option is e nabled (the default), the NMS identified by the
NMS IP/Host Name setting will receive authentication traps (traps generated by invalid
attempts to log on to this device).
SNMPv3. Settings for SNMPv3.
• User Name: Select the identifier of the user profile for this trap receiver.
If you delete a trap receiver, all notification settings configured under “Configuring event actions” for
the deleted trap receiver are set to their default values.
Metered Rack PDU92
Loading...