APC AP88XX, AP8861, AP8886 User Manual

User Guide

Metered Rack Power Distribution Unit

AP88XX

Contents

Introduction..................................................................... 1

Product Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Access Priorities for Logging on. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Types of User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Watchdog Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Network interface watchdog mechanism . . . . . . . . . . . . . . . . . . . . . 3

Resetting the network timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Network Port Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

About the Network Port Sharing Feature . . . . . . . . . . . . . . . . . . . . . 3

Display ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Establish Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

TCP/IP configuration methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

INI file utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

DHCP and BOOTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Recovering from a Lost Password . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Rack PDU Front Panel.................................................... 9

Display Tree Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Display Tree Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Network Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

10/100 LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Load indicator LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Command Line Interface.............................................. 14

About the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . .14

Metered Rack PDU User Guide i

Log on to the Command Line Interface . . . . . . . . . . . . . . . . . . . . . .14

Remote access to the command line interface . . . . . . . . . . . . . . . 14

Local access to the command line interface . . . . . . . . . . . . . . . . . 15

About the Main Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Using the Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . .16

Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Command Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Network Management Card Command Descriptions . . . . . . . . . . .19

about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

alarmcount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

clrrst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

dns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

eventlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

portSpeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

resetToDef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

snmp, snmpv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

tcpip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

tcpip6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

xferINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

xferStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Metered Rack PDU User Guide ii

Device Command Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Network Port Sharing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 31

bkLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

bkNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

bkOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

bkReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

devLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

devNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

devOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

devReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

humLow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

humMin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

humReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

phLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

phNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

phOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

phReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

prodInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

sensorName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

tempHigh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

tempMax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

tempReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

whoami . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Web Interface................................................................. 40

Supported Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Logging On to the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

URL address formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Web Interface Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Device status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Quick Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Other Web interface features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Network Port Sharing on the Web Interface. . . . . . . . . . . . . . . . . . .44

Group Control using Network Port Sharing . . . . . . . . . . . . . . . . . . 44

About the Home Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

The Overview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

The Alarm Status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Metered Rack PDU User Guide iii

Device Management...................................................... 47

About the Device Manager Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Viewing the Load Status and Peak Load . . . . . . . . . . . . . . . . . . . . .47

Configuring Load Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Configure the Name and Location of the Rack PDU . . . . . . . . . . . .48

Resetting Peak Load and kWh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Environment.................................................................. 49

Configure Temperature and Humidity Sensors . . . . . . . . . . . . . . . .49

Logs................................................................................ 50

Use the Event and Data Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Data log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

How to use FTP or SCP to retrieve log files . . . . . . . . . . . . . . . . . . 54

Administration: Security .............................................. 55

Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Setting user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configure the RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Summary of the configuration procedure . . . . . . . . . . . . . . . . . . . 57

Configuring a RADIUS server on UNIX® with shadow passwords 57

Supported RADIUS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

RADIUS and Network Port Sharing . . . . . . . . . . . . . . . . . . . . . . . . . 57

Inactivity Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Administration: Network Features .............................. 59

TCP/IP and Communication Settings . . . . . . . . . . . . . . . . . . . . . . . .59

TCP/IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

DHCP response options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Metered Rack PDU User Guide iv

Port Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Ping Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Web. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

SNMPv1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Administration: Notification......................................... 69

Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Types of notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Active, Automatic, Direct Notification. . . . . . . . . . . . . . . . . . . . . . . .71

E-mail notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

SNMP Trap Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Remote Monitoring Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Administration: General Options................................. 76

Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Set the Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Daylight saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Use an .ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Event Log and Temperature Units. . . . . . . . . . . . . . . . . . . . . . . . . . .78

Color-code event log text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Change the default temperature scale . . . . . . . . . . . . . . . . . . . . . . 78

Reset the Rack PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Configure Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

About the Rack PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Metered Rack PDU User Guide v

Device IP Configuration Wizard...................................80

Capabilities, Requirements, and Installation. . . . . . . . . . . . . . . . . . 80

How to use the Wizard to configure TCP/IP settings . . . . . . . . . . . 80

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Use the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Launch the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configure the basic TCP/IP settings remotely . . . . . . . . . . . . . . . . 80

Configure or reconfigure the TCP/IP settings locally . . . . . . . . . . 81

How to Export Configuration Settings ........................82

Retrieving and Exporting the .ini File. . . . . . . . . . . . . . . . . . . . . . . . 82

Summary of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Contents of the .ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

INI and Network Port Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Detailed procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

The Upload Event and Error Messages . . . . . . . . . . . . . . . . . . . . . . 85

The event and its error messages . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Messages in config.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Errors generated by overridden values . . . . . . . . . . . . . . . . . . . . . . 85

Related Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

File Transfers.................................................................86

How to Upgrade Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Benefits of upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Firmware module files (Rack PDU) . . . . . . . . . . . . . . . . . . . . . . . . . 86

Firmware File Transfer Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Using the Firmware Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . . 87

Use FTP or SCP to upgrade one Rack PDU . . . . . . . . . . . . . . . . . . 87

Use XMODEM to upgrade one Rack PDU . . . . . . . . . . . . . . . . . . . . 88

How to upgrade multiple Rack PDUs . . . . . . . . . . . . . . . . . . . . . . . . 89

Using the Firmware Upgrade Utility for multiple upgrades . . . . . . 89

Using a USB flash drive to upgrade one Rack PDU . . . . . . . . . . . . 89

Verifying Upgrades and Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Verify the success or failure of the transfer . . . . . . . . . . . . . . . . . . 91

Last Transfer Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Verify the version numbers of installed firmware. . . . . . . . . . . . . . 91

Metered Rack PDU User Guidevi

Troubleshooting ............................................................92

Rack PDU Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Appendix A: List of Supported Commands................93

Network Management Card Command Descriptions . . . . . . . . . . .93

Device Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Metered Rack PDU User Guide vii

Introduction

Product Features

The APC by Schneider Electric Metered Rack Power Distribution Unit (PDU) may be used as a stand­alone, network-manageable power distribution device or up to 4 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 unit comes with one terminator installed. It is not needed for stand-alone operation of this unit. 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, its command line interface (CLI),
StruxureWare, or Simple Network Management Protocol (SNMP). (To use the PowerNet MIB with an
SNMP browser, see the PowerNet SNMP Management Information Base (MIB) Reference Guide,
available at www.apc.com.) Rack PDUs have these additional features:

• Peak load, and power and energy monitoring for all connected loads.

• Voltage, current, and power monitoring for phases.

• Current monitoring for outlet banks.

• Configurable alarm thresholds that provide network and visual alarms to help avoid overloaded
circuits.

• Three levels of user access accounts: Administrator, Device User, and Read-Only User.

• 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 system events.

• SNMP traps, Syslog messages, and e-mail notifications based on the severity level or category of
the Rack PDU and system events.

• Security protocols for authentication and encryption.

• Network Port Sharing: Up to four Rack PDUs can be connected using the In and Out ports so that
only one network connection is necessary.

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 an APC Uninterruptible Power Supply
(UPS).

Metered Rack PDU User Guide1

Access Priorities for Logging on

Only one user at a time can log on to the Rack PDU. The priority for access, beginning with the highest
priority, is as follows:

• Local access to the command line interface from a computer with a direct serial connection to the
Rack PDU

• Telnet or Secure SHell (SSH) access to the command line interface from a remote computer

• Web access, either directly or through StruxureWare Data Center Expert
Note: See “SNMP” on page 65 for information about how SNMP access to the Rack PDU is

controlled.

Types of User Accounts

The Rack PDU has three levels of access (Administrator, Device User, and Read-Only User), which are
protected by user name and password requirements.

• An Administrator can use all of the menus in the Web interface and all of the commands in the
command line interface. The default user name and password are both apc.

• A Device User can access only the following:

– In the Web interface, the menus on the Device Manager tab, the Environment tab, and the

event and data logs, accessible under the Events and Data headings on the left navigation
menu of the Logs tab. The event and data logs display no button to clear the log.

– In the command line interface, the equivalent features and options.

The default user name is device, and the default password is apc.

• A Read-Only User has the following restricted access:

– Access through the Web interface only.
– Access to the same tabs and 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.

The default user name is readonly, and the default password is apc. To set User Name and
Password values for the three account types above, see “Setting user access” on page 55.

2Metered Rack PDU User Guide

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 System:
Warmstart event is recorded in the event log.

Network interface watchdog mechanism

The Rack PDU implements internal watchdog mechanisms to protect itself from becoming inaccessible
over the network. For example, if the Rack PDU does not receive any network traffic for 9.5 minutes
(either direct traffic, such as SNMP, or broadcast traffic, such as an Address Resolution Protocol [ARP]
request), it assumes that there is a problem with its network interface and restarts.

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 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

About the Network Port Sharing Feature

You can use the Network Port Sharing feature to view the status of and configure and manage up to four
Rack PDUs using only one network connection. This is made possible by connecting the Rack PDUs via
the "In" and "Out" ports on the Rack PDU front panel.
Note: All Rack PDUs in the group must be using the same Rack PDU firmware revision, 5.1.5 or later
(excluding v6.0.5 EnergyWise), in order to support the Network Port Sharing Feature.

Display ID

The display ID is a number, 1 to 4, used to uniquely identify the Rack PDUs in a group. After two or
more Rack PDUs are connected to one another in a group, they can be identified on the various
interfaces by the use of this "Display ID". This Display ID is viewable on the LCD by selecting the
Display Settings > Display ID > Show option on the LCD keypad.

Installation Instructions

Connect up to four Rack PDUs. 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 Network Port
Sharing group should reside in the same rack enclosure.

Connect the "Network" port of one of the grouped Rack PDUs to a network hub or switch. This unit
will be the "Host" for the Rack PDU group. A Host is defined as a Rack PDU that is connected to the
network and is part of a Rack PDU group. 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.

Metered Rack PDU User Guide3

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 "Device Manager > Load
Management > device load > Display ID" field.

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. (See “Establish Network Settings” on page 5.)

4. Begin using the Rack PDU by way of one of the following:

– “Web Interface” on page 40
– “Command Line Interface” on page 14
– “Rack PDU Front Panel” on page 9

4Metered Rack PDU User Guide

Establish Network Settings

Note: Disregard the procedures described in this section if you have StruxureWare Data Center Expert

as part of your system. See the documentation for your StruxureWare Data Center Expert device for
more information.

You must configure the following TCP/IP settings before the Rack PDU can operate on a network:

• IP address of the Rack PDU

• Subnet mask

• Default gateway

Note: If a default gateway is unavailable, use the IP address of a computer that is located on the
same subnet as the Rack PDU and that is usually running. The Rack PDU uses the default
gateway to test the network when traffic is very light.

Note: Do not use the loopback address (127.0.0.1) as the default gateway address for the Rack
PDU. It disables the card and requires you to reset TCP/IP settings to their defaults using a local
serial login.

See “Watchdog Features” on page 3 for more information about the watchdog role of the default
gateway.

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 80

• “DHCP and BOOTP configuration” on page 5

• “Command Line Interface” on page 7

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 “Use an .ini File” on page 77.

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
“Use an .ini File” on page 77.

If neither of these servers is available, see “Device IP Configuration Wizard” on page 80 or “Command
Line Interface” on page 7.

BOOTP. For the Rack PDU to use a BOOTP server to configure its TCP/IP settings, it must find a

properly configured RFC951-compliant BOOTP server.
In the BOOTPTAB file of the BOOTP server, enter the Rack PDU’s MAC address, IP address, subnet

mask, and default gateway , and, optionally, a bootup file name. Look for the MAC address on the bottom
of the Rack PDU or on the Quality Assurance slip included in the package.

Metered Rack PDU User Guide5

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 40 or “Command Line Interface” on page 7; the
user name and password are both apc, by default. To create a bootup file, see your BOOTP server
documentation.

DHCP. Y ou 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 60.

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 Vendor Specific Information option.
Note: By selecting the Require vendor specific cookie to accept DHCP Addr ess check box

in the Web interface, you can require the DHCP server to provide an “APC” cookie, which
supplies information to the Rack PDU: Administration > Network>TCP/IP>ipv4 settings.

6Metered Rack PDU User Guide

Command Line Interface

1. Log on to the command line interface. See “Log on to the Command Line Interface” on page 14.

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

a.

tcpip -s yourSubnetMask

b.

tcpip -g yourDefaultGateway

c.

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:

Metered Rack PDU User Guide7

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 (APC 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
8 data bits, no parity, 1 stop bit, and no flow control.

) and configure the selected port for 9600 bps,

4. Press

ENTER, repeatedly if necessary, to display the User Name prompt. If you are unable to

display the User Name prompt, verify the following:

– The serial port is not in use by another application.
– The terminal settings are correct as specified in step 3.
– The correct cable is being used as specified in step 2.

5. Press the Reset button. The Status LED will flash alternately orange and green. Press the Reset
button a second time immediately while the LED is flashing to reset the user name and password
to their defaults temporarily.

6. Press

ENTER, repeatedly if necessary, to display the User Name prompt again, then use the

default, apc, for the user name and password. (If you take longer than 30 seconds to log on after
the User Name prompt is re-displayed, you must repeat step 5 and log on again.)

7. At the command line interface, use the following commands to change the User Name and
Password settings, both of which are now apc:

user -an yourAdministratorName
user -ap yourAdministratorPassword

For example, to change the Administrator user name to Admin, type:

user -an Admin

8. Type quit or exit to log off, reconnect any serial cable you disconnected, and restart any service
you disabled.

8Metered Rack PDU User Guide

Rack PDU Front Panel

Note: Your APC product 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 every five seconds. To
reverse the text, press and hold simultaneously for five seconds
the Main Menu (), Scroll (), and Select () buttons.

Main Menu button Press to view the Rack PDU electrical input,



shown below.

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. Software Info is shown below.

Metered Rack PDU User Guide9

Item Function

OK, Warning, Overload LED Indicates the status of the Rack PDU load. See “Load indicator



LED” on page 13.

T emp/Humidity port Port for connecting an APC Temperature Sensor (AP9335T) or an



APC 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 (APC part number 940-0144A).

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.

10Metered Rack PDU User Guide

Display Tree Example 1

Metered Rack PDU User Guide11

Display Tree Example 2

12Metered Rack PDU User Guide

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 APC 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 APC

Customer Support.
Flashing Green The Rack PDU does not have valid TCP/IP settings.
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 5 to configure the
TCP/IP settings of the Rack PDU.

2. To use a DHCP server, see “TCP/IP and Communication Settings” on page 59.

If the LED is flashing slowly, the Rack PDU is making DHCP2 requests1.

If the LED is flashing rapidly, the Rack PDU is starting up.

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 APC Customer Support.

Solid green The Rack PDU is connected to a network operating at 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.

Metered Rack PDU User Guide13

Command Line Interface

About the Command Line Interface

You can use the command line interface to view the status of and configure and manage the Rack PDU.
In addition, the command line interface enables you to create scripts for automated operation. An

Administrator has full access to the command line interface, a Device user has limited access, and a

Read-Only user is completely restricted. (For additional details, see “Types of User Accounts” on
page 2.)

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 Command Line Interface

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 access the command line interface through T elnet or SSH. Telnet is enabled by default. Enabling
SSH disables Telnet.

To enable or disable these access methods, use the Web interface. On the Administration tab, select
Network on the top menu bar, and then the access option under Console on the left navigation menu.

Telnet for basic access. Telnet provides the basic security of authentication by user name and

password, but not the high-security benefits of encryption.
To use Telnet to access the command line interface:

1. From a computer that has access to network on which the Rack PDU is installed, at a command

prompt, type

139.225.6.133, when the Rack PDU uses the default Telnet port of 23), and press ENTER.

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 don’t 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 an Administrator, or device and
apc for a Device User).

If you cannot remember your user name or password, see “Recovering from a Lost Password” on
page 8.

telnet and the IP address for the Rack PDU (for example, telnet

SSH for high-security access. If you use the high security of SSL for the Web interface, use SSH for

access to the command line interface. SSH encrypts user names, passwords, and transmitted data. The
interface, user accounts, and user access rights are the same whether you access the command line
interface through SSH or Telnet, but to use SSH, you must first configure SSH and have an SSH client
program installed on your computer.

14Metered Rack PDU User Guide

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 (APC 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.

About the Main Screen

Following is an example of the main screen, which is displayed when you log on to the command
line interface of a Rack PDU.

American Power Conversion Network Management Card AOS vx.x.x
(c)Copyright 2012 All Rights Reserved RPDU 2g PPPP vx.x.x

-------------------------------------------------------------------------­Name : Test Lab Date : 10/30/2012
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+

APC>

• Two fields identify the APC 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 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/2012
Time : 5:58:30

• The User field identifies whether you logged in through the Administrator or Device Manager

account. (The Read Only User account cannot access the command line interface.)

User : Administrator

Metered Rack PDU User Guide15

• A Stat field reports the Rack PDU status.

Stat : P+ N4 N6

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

IPv4 and
IPv6*

Description

Note: If P+ is not displayed, contact APC support staff.

Using the Command Line Interface

At the command line interface, 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

radius ?

? or the word help. For example, to view RADIUS configuration options, type:

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.

16Metered Rack PDU User Guide

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:

user [-an <admin name>] [-ap <admin password>]

In this example, the user command accepts the option -an, which defines the Administrator user name,
and the option
and password to XYZ:

-ap, which defines the Administrator password. To change the Administrator user name

1. Type the user command, one option, and the argument

user -ap XYZ

XYZ:

2. After the first command succeeds, type the user command, the second option, and the argument

XYZ:
user -an XYZ

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 PDU User Guide17

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 effect

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

18Metered Rack PDU User Guide

Network Management Card Command Descriptions

Access: Administrator, Device User
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.

Example: To view a list of options that are accepted by the alarmcount command, type:

alarmcount ?

about

Access: Administrator, Device User
Description: View hardware and firmware information. This information is useful in troubleshooting

and enables you to determine if updated firmware is available at the APC Web site.

alarmcount

Access: Administrator, Device User
Description:

Option Arguments 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:

alarmcount -p warning

To view all active warning alarms, type:

Metered Rack PDU User Guide19

boot

Access: Administrator only
Description: Define how the Rack PDU will obtain its network settings, including the IP address,

subnet mask, and default gateway. Then configure the BOOTP or DHCP server settings.

Option Argument Description

-b
<boot
mode>

-c enable | disable dhcp and dhcpBootp boot modes only. Enable or disable the requirement

The default values for these three settings generally do not need to be changed:

-v <vendor class>: APC

-i <client id>: The MAC address of the Rack PDU, which uniquely identifies it on the network

-u <user class>: The name of the application firmware module

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 59 for information about each boot mode setting.

that the DHCP server provide the APC cookie.

Example: To use a DHCP server to obtain network settings:

1. Type

boot -b dhcp

2. Enable the requirement that the DHCP server provide the APC cookie:

boot -c enable

cd

Access: Administrator, Device User
Description: Navigate to a folder in the directory structure of the Rack PDU.
Example 1: To change to the ssh folder and confirm that an SSH security certificate was uploaded to

the Rack PDU:

1. Type

2. Type

cd ssh and press ENTER.
dir and press ENTER to list the files stored in the SSH folder.

Example 2: To return to the main directory folder, type:

cd ..

clrrst

Access: Administrator, Device User
Description: Clear reset reason.

20Metered Rack PDU User Guide

console

Access: Administrator only
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.

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.

-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

Configure the speed of the serial port connection (9600 bps by default).

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:

console -pt 5000

Metered Rack PDU User Guide21

date

Access: Administrator only
Definition: Configure the date used by the Rack PDU.

To configure an NTP server to define the date and time for the Rack PDU, see “Set the Date and Time”
on page 76.

Option Argument Description

-d <“datestring”> Set the current date. Use the date format specified by the date -f
command.

-t <00:00:00> Configure the current time, in hours, 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> Set the difference with GMT in order to specify your time zone. This enables

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.

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, 2009, using the format configured in the preceding

example, type:

date -d “2009-10-30”

Example 3: To define the time as 5:21:03 p.m., type:

date -t 17:21:03

delete

Access: Administrator only
Description: Delete a file in the file system.

Argument Description

<file name> Type the name of the file to delete.

dir

Access: Administrator, Device User
Description: View the files and folders stored on the Rack PDU.

22Metered Rack PDU User Guide