APC AP8941, AP89XX User Manual

User Guide

Switched Rack Power Distribution

Unit

AP89xx

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

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

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

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

Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Recovering from a Lost Password . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Rack PDU Front Panel.................................................... 8

Network Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

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

Load indicator LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Command Line Interface.............................................. 11

About the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . .11

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

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

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

Metered Rack PDU User Guide i

About the Main Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Using the Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . .13

Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Command Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Network Management Card Command Descriptions . . . . . . . . . . .16

about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

alarmcount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

appcli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

clrrst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

dns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

eventlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

portSpeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

resetToDef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

snmp, snmpv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

tcpip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

tcpip6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

xferINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

xferStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Metered Rack PDU User Guide ii

Device Command Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

bkLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

bkNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

bkOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

bkReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

bkRestrictn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

devLowLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

devNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

devOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

devReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

devStartDly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

humLow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

humMin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

humReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

olAssignUsr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

olCancelCmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

olDlyOff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

olDlyOn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

olDlyReboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

olGroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

olName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

olOff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

olOffDelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

olOn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

olOnDelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

olRbootTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

olRboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

olStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

olUnasgnUsr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

ph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

phNearOver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

phOverLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

phReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

phRestrictn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

prodInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

sensorName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

tempHigh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

tempMax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

tempReading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

userAdd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

userDelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

userList . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

userPasswd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

whoami . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Network Port Sharing Commands. . . . . . . . . . . . . . . . . . . . . . . . . . .45

Metered Rack PDU User Guide iii

Web Interface................................................................. 46

Supported Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Logging On to the Web Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

URL address formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Web Interface Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Device status icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Quick Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Other Web interface features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

About the Home Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

The Overview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

The Alarm Status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Device Management...................................................... 51

About the Device Manager Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Viewing the Load Status and Peak Load . . . . . . . . . . . . . . . . . . . . .51

Configuring Load Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

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

Set the Coldstart Delay for the Rack PDU . . . . . . . . . . . . . . . . . . . .52

Reset Peak Load and kWh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Set the Overload Outlet Restrictions . . . . . . . . . . . . . . . . . . . . . . . .53

Configure and Control Outlet Groups. . . . . . . . . . . . . . . . . . . . . . . .53

Group Control using Network Port Sharing . . . . . . . . . . . . . . . . . . 53

Outlet group terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Purpose and benefits of outlet groups . . . . . . . . . . . . . . . . . . . . . . 54

System requirements for outlet groups . . . . . . . . . . . . . . . . . . . . . 54

Rules for configuring outlet groups . . . . . . . . . . . . . . . . . . . . . . . . 55

Enable outlet groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Create a local outlet group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Create multiple global outlet groups . . . . . . . . . . . . . . . . . . . . . . . 57

Edit or delete an outlet group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Typical outlet group configurations . . . . . . . . . . . . . . . . . . . . . . . . 58

Verify your setup and configuration for global outlet groups . . . 59

Metered Rack PDU User Guide iv

Outlet Settings for Outlets and Outlet Groups. . . . . . . . . . . . . . . . .59

Initiate a control action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Configure outlet settings and the outlet name . . . . . . . . . . . . . . . 61

Scheduling Outlet Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Actions you can schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Schedule an outlet event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Edit, disable, enable, or delete a scheduled outlet event . . . . . . . 63

Outlet Manager Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Configure an outlet user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Outlet Manager and Network Port Sharing . . . . . . . . . . . . . . . . . . . 63

Environment.................................................................. 64

Configure Temperature and Humidity Sensors . . . . . . . . . . . . . . . .64

Logs................................................................................ 65

Use the Event and Data Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Data log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Use FTP or SCP to retrieve log files . . . . . . . . . . . . . . . . . . . . . . . . 68

Network Port Sharing Event Logs and Traps. . . . . . . . . . . . . . . . . .69

Data Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Administration: Security .............................................. 70

Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Setting user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configure the RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Summary of the configuration procedure . . . . . . . . . . . . . . . . . . . 72

Configuring a RADIUS server on UNIX® with shadow passwords 72

Supported RADIUS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Inactivity Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Metered Rack PDU User Guide v

Administration: Network Features...............................73

TCP/IP and Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . 73

TCP/IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

DHCP response options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Port Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Ping Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

SNMPv1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Administration: Notification.........................................83

Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Types of notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configuring event actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Active, Automatic, Direct Notification . . . . . . . . . . . . . . . . . . . . . . . 85

E-mail notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

SNMP Trap Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Remote Monitoring Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Administration: General Options.................................90

Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Set the Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Daylight saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Use an .ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Metered Rack PDU User Guidevi

Event Log and Temperature Units. . . . . . . . . . . . . . . . . . . . . . . . . . .92

Color-code event log text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Change the default temperature scale . . . . . . . . . . . . . . . . . . . . . . .92

Reset the Rack PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Configure Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

About the Rack PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Device IP Configuration Wizard ...................................94

Capabilities, Requirements, and Installation . . . . . . . . . . . . . . . . . .94

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

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Use the Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Launch the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

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

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

How to Export Configuration Settings.........................96

Retrieving and Exporting the .ini File . . . . . . . . . . . . . . . . . . . . . . . .96

Summary of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Contents of the .ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

INI and Network Port Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Detailed procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

The Upload Event and Error Messages. . . . . . . . . . . . . . . . . . . . . . .99

The event and its error messages . . . . . . . . . . . . . . . . . . . . . . . . . .99

Messages in config.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Errors generated by overridden values . . . . . . . . . . . . . . . . . . . . . .99

Related Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

File Transfers...............................................................100

How to Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Benefits of upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . . .100

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

Metered Rack PDU User Guide vii

Firmware File Transfer Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Using the Firmware Upgrade Utility . . . . . . . . . . . . . . . . . . . . . . . . 101

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

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

How to upgrade multiple Rack PDUs . . . . . . . . . . . . . . . . . . . . . . . 102

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

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

Verifying Upgrades and Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 104

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

Last Transfer Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

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

Troubleshooting..........................................................105

Rack PDU Access Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

For problems that persist or are not described here, see the back cover of this

manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

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

Network Management Card Command Descriptions . . . . . . . . . . 106

Device Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Metered Rack PDU User Guideviii

Introduction

Product Features

The APC by Schneider Electric Switched Rack Power Distribution Unit (PDU) may be used as a stand­alone, network-manageable power distribution device or up to 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. The Rack PDU provides full control over outlets
through remote commands and user interface settings.

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), StruxureW are
Data Center Expert, or Simple Network Management Protocol (SNMP). (T o 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.

• Four levels of user access accounts: Administrator , Device User, Read-Only User, and Outlet User

• Independent outlet control.

• Configurable power delays.

• Up to twenty-four independent outlet user accounts.

• 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).

Switched 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 87 for information about how SNMP access to the Rack PDU is

controlled.

Types of User Accounts

The Rack PDU has four levels of access (Administrator, Device User , Read-Only User , and Outlet 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 77.

• An Outlet User has the following restricted access:

– Access through the Web interface and command line interface.
– Access to the same menus as a Device User, but with limited capability to change

configurations, control devices, delete data, or use file transfer options. Links to configuration
options are visible but are disabled. The Outlet User has access to the Outlet Control menu
option that allows the user to control the outlets assigned by the Administrator. Outlet Users
cannot clear the event or data logs.

The user name and password are defined by the Administrator during the process of adding a
new Outlet User.

2Switched 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.

Switched 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 52
– “Command Line Interface” on page 14
– “Rack PDU Front Panel” on page 9

4Switched 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 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 102

• “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 99.

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

If neither of these servers is available, see “Device IP Configuration Wizard” on page 102 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.

Switched 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 52 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 82.

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.

6Switched 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:

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

8Switched 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.



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.

Switched 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.)



Outlet status LED Illuminates green when the outlet is energized. (Each outlet has an



outlet LED.)

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.

!

10Switched Rack PDU User Guide

Display Tree Example 1

Switched Rack PDU User Guide11

Display Tree Example 2

12Switched 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 81.

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.

Switched 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
(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. An Administrator has full access to
the command line interface, a Device user and Outlet User have limited access, and a Read-Only user is
completely restricted.

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 byuser name and

password, but not the high security benifits 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

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 cliet, 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 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.

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

Switched Rack PDU User Guide15

• 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

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.

16Switched 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.

Switched 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

18Switched Rack PDU User Guide

Network Management Card Command Descriptions

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

appcli

Access: Administrator, Device User, Outlet User
Description: Access the Rack PDU Command Line Interface.

Switched 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 81
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, Outlet 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, Outlet User
Description: Clear reset reason.

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

Switched 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 98.

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, Outlet User
Description: View the files and folders stored on the Rack PDU.

22Switched Rack PDU User Guide

dns

Access: Administrator only
Definition: Configure the manual Domain Name System (DNS) settings.

Parameter Argument Description

-OM enable | disable Override the manual DNS.

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

Set the primary DNS server.

Set the secondary DNS server.

Set the domain name IPv6.

eventlog

Access: Administrator, Device User, Outlet User
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 Close the event log and return to the command line interface.
ENTER Update the log display. Use this command to view events that were recorded after you last

retrieved and displayed the log.

SPACEBAR View the next page of the event log.

B

D

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.

exit

Access: Administrator, Device User, Outlet User
Description: Exit from the command line interface session.

format

Access: Administrator only
Description: Reformat the file system of the Rack PDU and erase all security certificates, encryption

keys, configuration settings, and the event and data logs. Be careful with this command.
Note: To reset the Rack PDU to its default configuration, use the

resetToDef command.

Switched Rack PDU User Guide23

FTP

Access: Administrator only
Description: Enable or disable access to the FTP server. Optionally, change the port setting to the

number of any unused port from 5001 to 32768 for added security.

Option Argument Definition

-p <port number> 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.

-S enable | disable Configure access to the FTP server.

Example: To change the TCP/IP port to 5001, type:

ftp -p 5001

help

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

Example 1: To view a list of commands available to someone logged on as a Device User, type:

help

help.

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

alarmcount help

netstat

Access: Administrator, Device User, Outlet User
Description: View the status of the network and all active IPv4 and IPv6 addresses.

ntp

Access: Administrator
Description: View and configure the network time protocol parameters.

Option Argument Definition

-OM enable | disable Override the manual settings.

-p <primary NTP

server>

-s <secondary NTP

server>

Specify the primary 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

24Switched Rack PDU User Guide

ping

Access: Administrator, Device User
Description. Determine whether the device with the IP address or DNS name you specify is connected

to the network. Four inquiries are sent to the address.

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: To determine whether a device with an IP address of 150.250.6.10 is connected to the

network, type:

ping 150.250.6.10

portSpeed

Access: Administrator
Description:

Option Arguments Description

-s auto | 10H | 10F |
100H | 100 F

Example:

To configure the TCP/IP port to communicate using 100 Mbps with 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 83 for more information about the port speed
settings.

communication (communication in only one direction at a time), type:

portspeed -s 100H

prompt

Access: Administrator, Device User
Description: Configure the command line interface prompt to include or exclude the account type of

the currently logged-in user. Any user can change this setting; all user accounts will be updated to use the
new setting.

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: To include the account type of the currently logged-in user in the command prompt, type:

prompt -s long

quit

Access: Administrator, Device User, Outlet User
Description: Exit from the command line interface session (this works the same as the exit command).

Switched Rack PDU User Guide25

radius

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

Additional authentication parameters for RADIUS servers are available at the Web interface of the Rack

PDU. See “RADIUS” on page 78 for more information.
For detailed information about configuring your RADIUS server, see the Security Handbook, available
at www.apc.com.

Option Argument Description

-a local | radiusLocal
| radius

-p1

-p2

-s1

-s2

-t1

-t2

<server IP> The server name or IP address of the primary or secondary RADIUS server.

<server secret> The shared secret between the primary or secondary RADIUS server and the

<server timeout> The time in seconds that the Rack PDU waits for a response from the primary

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.

Note: RADIUS servers use port 1812 by default to authenticate users. T o use

a different port, add a colon followed by the new port number to the end of the
RADIUS server name or IP address.

Rack PDU.

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

reboot

Access: Administrator only
Description: Restart the interface of the Rack PDU.

26Switched Rack PDU User Guide

resetToDef

Access: Administrator only
Description: Reset all parameters to their default.

Option Arguments Description

-p all | keepip Reset all configuration changes, including event actions, 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

snmp, snmpv3

Access: Administrator only
Description: Enable or disable SNMP 1 or SNMP 3.

Option Arguments Description

-S enable | disable Enable or display the respective version of SNMP, 1 or 3.

Example: To enable SNMP version 1, type:

snmp -S enable

system

Access: Administrator only
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 15 for more information about system status).

Option Argument Description

-n <system name> Define the device name, the name of the person responsible for the

-c <system contact>

device, and the physical location of the device.

Note: If you define a value with more than one word, you must

-l <system location>

enclose the value in quotation marks.
These values are also used by StruxureWare Data Center Expert and
the Rack PDU’s SNMP agent.

Example 1: To set the device location as Test Lab, type:

system -l “Test Lab”

Example 2: To set the system name as Don Adams, type:

system -n “Don Adams”

Switched Rack PDU User Guide27

tcpip

Access: Administrator only
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. Do not use the 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.

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

tcpip6

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

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.

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

28Switched Rack PDU User Guide

user

Access: Administrator only
Description: Configure the user name, password, and inactivity timeout for the Administrator, Device

User, and Read-Only User account types. For information on the permissions granted to each account
type, see “Types of User Accounts” on page 2.

Option Argument Description

-an

-dn

-rn

-ap

-dp

-rp

-t <minutes> Configure the time (3 minutes by default) that the system waits before

<admin name>
<device name>
<read-only name>

<admin password>
<device password>
<read-only password>

Set the case-sensitive user name for each account type. The maximum
length is 10 characters.

Set the case-sensitive password for each account type. The maximum
length is 32 characters. Blank passwords (passwords with no characters)
are not allowed.

logging off an inactive user.

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

web

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

Option Argument Definition

-S disable | http | https Configure access to the Web interface. When HTTPS is enabled, data is
encrypted during transmission and authenticated by digital certificate.

-ph <http port #> Define the TCP/IP port used by HTTP to communicate with the Rack
PDU (80 by default).

-ps <https port #> Define the TCP/IP port used by HTTPS to communicate with the Rack
PDU (443 by default).

Example: To prevent all access to the Web interface, type:

web -S disable

Switched Rack PDU User Guide29

xferINI

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

xferStatus

Access: Administrator only
Description: View the result of the last file transfer. See “Verifying Upgrades and Updates” on

page 113 for descriptions of the transfer result codes.

30Switched Rack PDU User Guide

Device Command Descriptions

Network Port Sharing Commands

The Command Line Interface 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: 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.

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

Example 3: To view the low-load threshold setting for banks 1 and 2 on guest Rack PDU 3, type:

apc> bkLowLoad 3:1-2
E000: Success
1: 0 A
2: 0 A

bkNearOver

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

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

Switched Rack PDU User Guide31

bkOverLoad

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

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

bkReading

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

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

bkRestrictn

Access: Administrator, Device User
Description: Set or read the overload restriction feature to prevent users from applying power to outlets

when an overload threshold is violated. Acceptable arguments are
phases, choose from the following options. Type:

all, a single phase, a range, or a comma-separated list

none, near, and over. T o specify

of phases.

Example 1: To set the overload restriction for phase three to none, type:

apc> bkRestrictn 3 none
E000: Success

Example 2: To view the overload restrictions for all phases, type:

apc> bkRestrictn all
E000: Success
1: over
2: near
3: none

Example 3: To view the overload restrictions for all banks on guest Rack PDU 2, type:

apc> bkRestrictn 2:all
E000: Success
1: None
2: None

32Switched Rack PDU User Guide

devLowLoad

Access: Administrator, Device User
Description: Set or view the low-load threshold in kilowatts for the device.
Example 1: To view the low-load threshold, type:

apc> dev
E000: Success

0.5 kW

Example 2: To set the low-load threshold to 1 kW, type:

apc> dev 1.0
E000: Success

Example 3: To set the low-load threshold to 1.5 kW on guest Rack PDU 3, type:

apc> devLowLoad 3:1.5
E000: Success

devNearOver

Access: Administrator, Device User
Description: Set or view the near-overload threshold in kilowatts for the device.
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

devOverLoad

Access: Administrator, Device User
Description: Set or view the overload threshold in kilowatts for the device.
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

Switched Rack PDU User Guide33

devReading

Access: Administrator, Device User
Description: View the total power in kilowatts or total energy in kilowatt-hours for the device.

Argument Definition

power View the total power in kilowatts.
energy View the total energy in kilowatt-hours.

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

Example 3: To view the total power for guest Rack PDU 3, type:

apc> devReading 3:power
E000: Success

4.2 kW

devStartDly

Access: Administrator, Device User
Description: Set or view the amount of time in seconds, which is added to each outlet’s Power On

Delay before the outlet will turn on after power is applied to the Switched Rack PDU. Allowed values
are within the range of 1 to 300 seconds or never (never turn on).

Example 1: To view the cold start delay, type:

apc> devStartDly
E000: Success
5 seconds

Example 2: To set the cold start delay to six seconds, type:

apc> devStartDly 6
E000: Success

Example 3: To set the cold start delay to six seconds on guest Rack PDU 2, type:

apc> devStartDly 2:6
E000: Success

Example 4: To view the cold start delay on guest Rack PDU 2, type:

apc> devStartDly 2:
E000: Success
6 sec

34Switched Rack PDU User Guide

humLow

Access: Administrator, Device User
Description: Set or view the low humidity threshold as a percent of the relative humidity.
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

humMin

Access: Administrator, Device User
Description: Set or view the minimum humidity threshold as a percent of the relative humidity.
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

humReading

Access: Administrator, Device User, Outlet User
Description: View the humidity value from the sensor.
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

Switched Rack PDU User Guide35

olAssignUsr

Access: Administrator
Description: Assign control of outlets to an outlet user that exists in the local database.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

<user> A user that exists in the local database. (See “userAdd” on page 50.)

Example 1: To assign a user named Bobby to outlets 3, 5 through 7, and 10, type:

apc> olAssignUsr 3,5-7,10 bobby
E000: Success

Example 2: To assign a user named Billy to all outlets, type:

apc> olAssignUsr all billy
E000: Success

Example 3: To assign a user named Billy to all outlets on guest Rack PDU 3, type:

apc> olAssignUsr 3:all billy
E000: Success

olCancelCmd

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Cancels all pending commands for an outlet or group of outlets.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example 1: To cancel all commands for outlet 3, type:

apc> olCancelCmd 3
E000: Success

Example 2: To cancel all commands for outlet 3 on guest Rack PDU 3, type:

apc> olCancelCmd 3:all
E000: Success

36Switched Rack PDU User Guide

olDlyOff

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Turns off an outlet or group of outlets after the Power Off Delay (see “olOffDelay” on

page 41).

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example 1: To turn off outlets 3, 5 through 7, and 10, type:

apc> olDlyOff 3,5-7,10
E000: Success

Example 2: To turn off all outlets, type:

apc> olDlyOff all
E000: Success

Example 3: To turn off all outlets on guest Rack PDU 2, type:

apc> olDlyOff 2:all
E000: Success

olDlyOn

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Turns on an outlet or group of outlets after the Power On Delay (see “olOnDelay” on

page 42).

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example 1: To turn on outlets 3, 5 through 7, and 10, type:

apc> olDlyOn 3,5-7,10
E000: Success

Example 2: To turn on an outlet with the configured name of Outlet1, type:

apc> olDlyOn outlet1
E000: Success

Switched Rack PDU User Guide37

olDlyReboot

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Cycles power to an outlet or a group of outlets. The specified outlets will be turned off

based on the configured Power Off Delay (see “olOffDelay” on page 41). After the longest Reboot
Duration (see “olRbootTime” on page 43) of the selected outlets, the outlets will then begin to turn on
based on the configured Power On Delays (see “olOnDelay” on page 42) set for the specified outlets.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example 1: To cycle power to outlets 3, 5 through 7, and 10, type:

apc> olDlyReboot 3,5-7,10
E000: Success

Example 2: To cycle power to an outlet with the configured name of Outlet1, type:

apc> olDlyReboot outlet1
E000: Success

Example 3: To cycle power to all outlets on guest Rack PDU 2, type:

apc> olDlyReboot 2:all
E000: Success

38Switched Rack PDU User Guide

olGroups

Access: Administrator, Device User, and Outlet User.
Description: List the outlet synchronization groups defined on the switched rack PDU. (See “Configure

and Control Outlet Groups” on page 61 for more information.)

Example 1: To list outlet synchronization groups on the Host Rack PDU, type:

apc> olGroups
Outlet Group Method: Enabled via Network
Outlet Group A:

159.215.6.141Outlets: 2,4-7,9

159.215.6.143Outlets: 2,7,8
Outlet Group B:

159.215.6.141Outlets: 1

159.215.6.166Outlets: 1
E000: Success

Example 2: To list outlet synchronization groups on guest Rack PDU 2, type:

apc> olGroups 2:
Outlet Group Method: Local Only
Outlet Grp A:
RPDU Outlets: 3,10-12,16
Outlet Grp B:
RPDU Outlets: 13,14
Outlet Grp C:
RPDU Outlets: 6,7
Outlet Grp E:
RPDU Outlets: 23,24
E000: Success

Example 3: To list outlet synchronization groups on guest Rack PDU 3, type:

apc> olGroups 3:
Outlet Group Method: Enabled via In/Out Ports
Outlet Grp A:
RPDU1 Outlets: 3,9,24
RPDU2 Outlets: 3,10,11,16
RPDU4 Outlets: 3,8
Outlet Grp B:
RPDU1 Outlets: 5,8,13
RPDU4 Outlets: 5,6
Outlet Grp C:
RPDU1 Outlets: 10,11,19
E000: Success

Switched Rack PDU User Guide39

olName

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Set or view the name configured for an outlet.

Argument Definition

all All device outlets.
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

<newname> The name for a specific outlet. Use only letters and numbers.

Example: To configure the name for outlet 3 to BobbysServer, type:

apc> olName 3 BobbysServer
E000: Success
3: BobbysServer
5: BillysServer
6: JoesServer
7: JacksServer

Example 2: To view the names of outlets 3 through 5 on guest Rack PDU 2, type:

apc> olName 2:3-5
E000: Success
3: BobbysServer
4: Outlet 4
5: Outlet 5

olOff

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Turn off an outlet or group of outlets without any delay.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example 1: To turn off outlets 3 and 5 through 7, type:

apc> olOff 3,5-7
E000: Success

Example 2: To turn off outlets 1 through 3 on guest Rack PDU 2, type:

apc> olOff 2:1-3
E000: Success

40Switched Rack PDU User Guide

olOffDelay

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Set or view the time delay for the Off Delayed command (see “olDlyOff” on page 37) and

for a Reboot Delayed command (see “olDlyReboot” on page 38).

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

<time> A time for the delay within the range of 1 to 7200 seconds (2 hours).

Example 1: To set a 9-second delay for turning off outlets 3 and 5 through 7, type:

apc> olOffDelay 3,5-7 9
E000: Success

Example 2: To view the delay for the Off Delayed command for outlets 3 and 5 through 7, type:

apc> olOffDelay 3,5-7
E000: Success
3: BobbysServer: 9 sec
5: BillysServer: 9 sec
6: JoesServer: 9 sec
7: JacksServer: 9 sec

Example 3: To set a 15-second delay for turning off outlets 2-4 on guest Rack PDU 2, type:

apc> olOffDelay 2:2-4 15
E000: Success

olOn

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Turn on an outlet or group of outlets without any delay.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example: To turn on outlets 3 and 5 through 7, type:

apc> olOn 3,5-7
E000: Success

Example 2: To turn on outlets 3 and 5 through 7 on guest Rack PDU 3, type:

apc> olOn 3:3,5-7
E000: Success

Switched Rack PDU User Guide41

olOnDelay

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Set or view the time delay for the On Delayed command (see “olDlyOn” on page 37) and

for or a Reboot Delayed command (see “olDlyReboot” on page 38).

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

<time> A time for the delay within the range of 1 to 7200 seconds (2 hours).

Example 1: To set a 6-second delay for turning on outlets 3 and 5 through 7, type:

apc> olOnDelay 3,5-7 6
E000: Success

Example 2: To view the delay for the On Delayed command for outlets 3 and 5 through 7, type:

apc> olOnDelay 3,5-7
E000: Success
3: BobbysServer: 6 sec
5: BillysServer: 6 sec
6: JoesServer: 6 sec
7: JacksServer: 6 sec

42Switched Rack PDU User Guide

olRbootTime

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Set or view the amount of time an outlet will remain off for a Reboot Delayed command

(see “olDlyReboot” on page 38).

Example 1: To view the time set for outlets 3 and 5 through 7 to remain off during a reboot, type:

apc> olRbootTime 3,5-7
E000: Success
3: BobbysServer: 4 sec
5: BillysServer: 5 sec
6: JoesServer: 7 sec
7: JacksServer: 2 sec

Example 2: To set the time for outlets 3 and 5 through 7 to remain off during a reboot, type:

apc> olRbootTime 3,5-7 10
E000: Success
3: BobbysServer: 10 sec
5: BillysServer: 10 sec
6: JoesServer: 10 sec
7: JacksServer: 10 sec

Switched Rack PDU User Guide43

olReboot

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: Cycle power to an outlet or group of outlets without any delays. If more than one outlet is

specified, then those outlets will be cycled together.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example: To reboot outlets 3 and 5 through 7, type:

apc> olReboot 3,5-7
E000: Success

olStatus

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: View the status of specified outlets.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

Example 1: To view the status for outlets 3 and 5 through 7, type:

apc> olStatus 3,5-7
E000: Success
3: BobbysServer: On
5: BillysServer: Off
6: JoesServer: Off
7: JacksServer: On

Example 2: To view the status for outlets 5 through 7 on guest Rack PDU 2, type:

apc> olStatus 2:5-7
E000: Success
5: Outlet 5: On
6: Outlet 6: On
7: Outlet 7: On

44Switched Rack PDU User Guide

olUnasgnUsr

Access: Administrator
Description: Remove control of outlets from an outlet user that exists in the local database.

Argument Definition

all All device outlets.
<outlet name> The name configured for a specific outlet. (See “olName” on page 40.)
<outlet#> A single number or a range of numbers separated with a dash, or a comma-

separated list of single outlet numbers and number ranges.

<user> A user that exists in the local database.

Example 1: To remove a user named Bobby from control of outlets 3, 5 through 7, and 10, type:

apc> olUnasgnUsr 3,5-7,10 bobby
E000: Success

Example 2: To remove a user named Billy from control of all outlets, type:

apc> olUnasgnUsr all billy
E000: Success

phLowLoad

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

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

Example 3: To view the low-load threshold for phases 1 on guest Rack PDU 3, type:

apc> phLowLoad 3:1
E000: Success
1: 1 A

Switched Rack PDU User Guide45

phNearOver

Access: Administrator, Device User
Description: Set or view the phase near-overload 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.

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

phOverLoad

Access: Administrator, Device User
Description: Set or view the phase overload 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.

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

46Switched Rack PDU User Guide

phReading

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

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

phRestrictn

Access: Administrator
Description: Set or view the overload restriction feature to prevent outlets from turning on when the

overload alarm threshold is violated. Acceptable arguments are
phases, choose from the following options. Type:

all, a single phase, a range, or a comma-separated list

none, near, and over. T o specify

of phases.

Example 1: To set the overload restriction for phase three to none, type:

apc> phRestrictn 3 none
E000: Success

Example 2: To view the overload restrictions for all phases, type:

apc> phRestrictn all
E000: Success
1: over
2: near
3: none

Switched Rack PDU User Guide47

prodInfo

Access: Administrator, Device User, Outlet User
Description: View information about the Rack PDU.
Example 1: To view the product information for this Rack PDU, type:

apc> prodInfo
E000: Success
AOS X.X.X
Switched Rack PDU X.X.X
Model: AP8XXX
Present Outlets: XX
Switched Outlets: XX
Metered Outlets: XX
Max Current: XX A
Phases: X
Banks: X

Example 2: To view the product information for guest Rack PDU 2, type::

apc> prodInfo 2:
E000: Success
AOS X.X.X
Switched Rack PDU X.X.X
Model: AP8XXX
Present Outlets: XX
Switched Outlets: XX
Metered Outlets: XX
Max Current: XX A
Phases: X
Banks: X

sensorName

Access: Administrator, Device User
Description: Set or view the name assigned to the Rack PDU Temp/Humidity port.
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

48Switched Rack PDU User Guide

tempHigh

Access: Administrator, Device User
Description: Set or view the high-temperature threshold in either Fahrenheit or Celsius.
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

tempMax

Access: Administrator, Device User
Description: Set or view the max-temperature threshold in either Fahrenheit or Celsius.
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

tempReading

Access: Administrator, Device User, Outlet User
Description: View the temperature value in either Fahrenheit or Celsius from the sensor.
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

Switched Rack PDU User Guide49

userAdd

Access: Administrator
Description: Add an outlet user to the local user database.
Example: To add a user named Bobby, type:

apc> userAdd Bobby
E000: Success

userDelete

Access: Administrator
Description: Remove an outlet user from the local user database.
Example: To remove a user named Bobby, type:

apc> userDelete Bobby
E000: Success

userList

Access: Administrator, Device User, and Outlet User, but only for outlets to which the user is assigned.
Description: List the users and the outlets assigned to them.
Example 1: When logged in as the Administrator, type:

apc> userList
E000: Success
Local: admin: 1,2,3,4,5,6,7,8
Local: Bobby: 1,3
Local: Billy: 2,5
Local: Joe 4,6
Local: Jack 7,8

Example 2: When logged in as Billy, type:

apc> userList
E000: Success
Local: Billy: 2,5

userPasswd

Access: Administrator.
Description: Set an outlet User password.
Example: To set Bobby’s password to “abc123,” type:

apc> userPasswd Bobby abc123 abc123
E000: Success

50Switched Rack PDU User Guide

whoami

Access: Administrator, Device User, Outlet User
Description: View the user name of the active user.
Example:

apc> whoami
E000: Success
admin

Switched Rack PDU User Guide51

Web Interface

Supported Web Browsers

You can use Microsoft® Internet Explorer® (IE) 7.x and higher (on Windows® operating systems only)
or Mozilla
interface. Other commonly available browsers may work but have not been fully tested by APC.

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 Web

• 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 the Rack PDU for the URL address of the Web
interface. Use your case-sensitive user name and password to log on. The default user names follow and
differ by account type:

• apc for an Administrator

• device for a Device User

• readonly for a Read-Only User

The default password is apc for all three account types. For Outlet User accounts, there is no default user
name or password. An Administrator must define the user name and password and other account
characteristics for an Outlet User. See .

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

For information about the Web page displayed when you log on, see “About the Home Tab” on page 58.

52Switched Rack PDU User Guide

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

“You are not authorized to view this page” or
“Someone is currently logged in...”

“This page cannot be displayed.” Internet Explorer Web access is disabled, or
“Unable to connect.” Firefox

Internet Explorer,
Firefox

Someone else is logged on

the URL was not correct.

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

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

–

Switched Rack PDU User Guide53

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. View active alarms, the load status of the Rack PDU, and

the most recent Rack PDU events. For more information, see “About the Home Tab” on
page 58.

• Device Manager: View the load status, configure load thresholds, and view and manage peak

load measurements for all connected devices, phases, and banks as applicable. Manage and
control outlets. For more information, see “About the Device Manager Tab” on page 59.

• Environment: View temperature and humidity sensor data, if a sensor is connected to the Rack
PDU.

• Logs: View event, data, and system logs.

• Administration: Configure security, network connection, notification, and general settings.

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 jeopardize your data or equipment if

its cause is not addressed.

No Alarms: No alarms are present, and the Rack PDU and NMC are operating 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.

T o return to the Home tab to view its summary of the Rack PDU status, including the active alarms, click
a quick status icon on any page of the interface.

54Switched Rack PDU User Guide

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 the APC Web site

• Link 2: Demonstrations of APC Web-enabled products

• Link 3: Information on APC Remote Monitoring Services.

To reconfigure the links, see “Configure Links” on page 101.

Other Web interface features

• The IP address appears in the upper left corner.

• A context-sensitive Help link and Log off link are located in the upper right corner.

Switched Rack PDU User Guide55

Network Port Sharing on the Web Interface

Group Control using Network Port Sharing

The web interface of the Rack PDU will have additional capabilities if the Rack PDU is part of a group.
These capabilities are only displayed if the Rack PDU is part of a group. This includes a "Group Status"
page, and the ability to select which Rack PDU to view data from.

The Group Status page lists basic information for the Host Rack PDU and any connected guests. Guests
are denoted using a Rack PDU icon and the Display ID.

Information on the Group Status page includes name, location, contact, basic model properties, firmware
revision information, and group communication status of each Rack PDU. In addition, the Group Status
page allows the user to remove any Rack PDUs that have been removed from the group and are in a lost
communication state.

56Switched Rack PDU User Guide

Most of the web pages under the Home, Device Manager, and Environment tabs allow you to switch
between Rack PDUs for viewing status and configuration/control. This switching is accomplished by
selecting the Rack PDU Display ID of the unit you would like to view . This is located at the top right of
each table that supports multiple Rack PDUs. The Host Rack PDU that you are logged into is always
denoted with an asterisk (*) following the Display ID.

Note: The Reset/Reboot web page has many additional reset/reboot options for Rack PDU groups.
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.

Switched Rack PDU User Guide57

About the Home Tab

Use the Home tab to view active alarms, the load status of the Rack PDU, and the most recent Rack
PDU events.

The Overview view

Path: Home > Overview

The top of the Overview indicates the alarm status. If one or more alarms are present, the number and
type of alarms are indicated with a link to the Alarm Status view, where you can view descriptions of
each alarm. If no alarms exist, the Overview displays, “No Alarms Present.”

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 that if a low load threshold was configured the meter will also include a blue segment to
the left of the green. Hover over the colors to view the configured load thresholds.

Click More to go to the Device Manager tab to configure thresholds and to view and manage peak load
information.

In the device parameters area, view the name, contact, location, current rating, type of user account
accessing the Rack PDU, and 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. [For more information, see “Reset
the Rack PDU” on page 100.]

In the Recent Device Events area, view, in reverse chronological order, the events that 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.

The Alarm Status view

Path: Home > Alarm Status

The Alarm Status view provides a description of all alarms present. For details about a temperature or
humidity threshold violation, click the Environment tab.

58Switched Rack PDU User Guide

Device Management

About the Device Manager Tab

Path: Device Manager

Use the Device Manager tab to:

• View the load status for the Rack PDU

• Manage and control outlets

• Configure a name and location for the Rack PDU

• View and manage the peak load measurement

• Click user-configurable links to open web pages for specific devices connected to the Rack PDU

Viewing the Load Status and Peak Load

Path: Device Manager > Load Management options

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.

Configuring Load Thresholds

Path: Device Manager > Load Management options

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 Threshold to 1 amp for these reasons:

• The default setting for the Low Load Warning Threshold is 0 amps. This effectively disables the
warning. With a setting of 0 amps for the Low Load Warning Threshold, 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. Click the Device Manager tab.

2. To configure load thresholds for the device, phases, or banks, make a selection from the Load

Management menu.

3. Set Overload Alarm, Near Overload Warning, and Low Load Warning thresholds.

4. Click Apply.

Switched Rack PDU User Guide59

Configure the Name and Location of the Rack PDU

Path: Device Manager > Device Load

The name and location you enter appear on the Home tab.
Note: You can set the Name and Location through either the Device Manager tab or the Administration

tab. A change in one affects the other.

1. Click the Device Manager tab, then device load from the Load Management menu.

2. Enter a name and location.

3. Click Apply.

Set the Coldstart Delay for the Rack PDU

Path: Device Manager > Device Load

The Coldstart Delay is the number of seconds added to each outlet’s Power On Delay before an outlet
will turn on after power is applied to the Rack PDU. Allowed values are from 1 to 300 seconds,
Immediate, or Never (never turn on).

1. Click the Device Manager tab, then device load from the Load Management menu.

2. Make a selection for Coldstart Delay.

3. Click Apply.

Reset Peak Load and kWh

Path: Device Manager > Device Load

1. Click the Device Manager tab, then device load from the Load Management menu.

2. Click the Peak Load and Kilowatt-Hours check boxes as desired.

3. Click Apply.

60Switched Rack PDU User Guide

Set the Overload Outlet Restrictions

Path: Device Manager > Phase Load and Bank Load

Prevent users from applying power to outlets during an overload condition. You can set the following
restrictions for each phase and bank:

• None: Users can apply power to outlets regardless of an Overload Alarm or Near Overload
Warning.

• On Warning: Users cannot apply power to an outlet on the selected phase or bank if the current
for that phase or bank has exceeded the Near Overload Warning threshold.

• On Overload: Users cannot apply power to an outlet on the selected phase or bank if the current
for that phase or bank has exceeded the Overload Alarm threshold.

To set Overload Outlet Restrictions:

1. Click the Device Manager tab, then phase load or bank load from the Load Management

menu.

2. Make selections for Overload Outlet Restriction.

3. Click Apply.

Configure and Control Outlet Groups

Outlet group terminology

An outlet group consists of outlets that are logically linked together on the same Rack PDU. Outlets that
are in an outlet group turn on, turn off, and reboot in a synchronized manner:

• A local outlet group consists of two or more outlets on a Rack PDU. Only the outlets in that group
are synchronized.

• A global outlet group consists of one or more outlets on a Rack PDU. One outlet is configured as
a global outlet, which logically links the outlet group to outlet groups on up to three other Rack
PDUs. All outlets in the linked global outlet groups are synchronized.

– For global outlet groups, the initiator outlet group is the group that issued the action.
– For global outlet groups, a follower outlet group is any other outlet group that is synchronized

with the initiator outlet group.

When you apply an outlet control action to outlets that are members of an outlet group, the outlets are
synchronized as follows:

• For a global outlet group, use the delay periods and reboot duration configured for the global
outlet of the initiator outlet group.

• For a local outlet group, the outlets use the delay periods and reboot duration of the lowest­numbered outlet in the group.

Switched Rack PDU User Guide61

Purpose and benefits of outlet groups

By using groups of synchronized outlets on Rack PDUs, you can ensure that outlets turn on, turn off, and
reboot in a synchronized manner. Synchronizing control group actions through outlet groups provides
the following benefits.

• Synchronized shutdown and startup of the power supplies of dual-corded servers prevents
erroneous reporting of power supply failures during a planned system shutdown or reboot.

• Synchronizing outlets by using outlet groups provides more precise shutdown and restart timing
than relying on the delay periods of individual outlets.

• A global outlet is visible to the user interface of any Rack PDU to which it is linked.

System requirements for outlet groups

To set up and use synchronized outlet control groups:

• You need a computer that can initiate synchronized control operations through the Web interface
or command line interface of the Rack PDUs or through SNMP.

• All of the Rack PDUs must use firmware that has the same version number for both the APC
Operating System (AOS) module and the application module.

• All of the Rack PDUs must be configured with the same “Member Name”.

• If you are using Network mode, you will also need the following items. These are not necessary if
you are using Network Port Sharing mode over the In/Out ports.

– You need a 10/100Base-T TCP/IP network, with an Ethernet hub or switch that has a power

source not shared by the computers or other devices being synchronized.
– All of the Rack PDUs must be on the same subnet.
– Outlet groups you synchronize must have the same Multicast IP address, outlet group port,

authentication phrase, and encryption phrase. Make sure each Ethernet switch that connects

Rack PDUs allows Multicast network traffic for that Multicast IP address.

Rules for configuring outlet groups

For a system that uses outlet groups, the following rules apply:

• A Rack PDU can have more than one outlet group, but an outlet can belong to only one outlet
group.

• A local outlet group, which has no global outlet, must consist of two or more outlets.

• You can synchronize a global outlet group on one Rack PDU with a global outlet group on each of
three other Rack PDUs.

– In a global outlet group, you can designate only one outlet to be a global outlet, linking to

outlet groups on other Rack PDUs for the purpose of synchronization. That global outlet can
be the only outlet in its group, or the group can consist of multiple outlets.

– A global outlet of one outlet group must have the same physical outlet number as the global

outlet of any other outlet group to which it links.

• To create and configure outlet groups, you must use the Web interface or export configuration file
(.ini file) settings from a configured Rack PDU. The command line interface lets you display
whether an outlet is a member of an outlet group and lets you apply control actions to an outlet
group, but the command line interface does not let you set up or configure an outlet group.

62Switched Rack PDU User Guide

Enable outlet groups

Click the Device Manager tab and select Group Configuration from the Outlet Groups left navigation
menu. Configure the following parameters, and click Apply.

Enable creation of outlet groups.

Parameters Description

Device Level
Outlet Group

To create an outlet group, you must enable the desired group method.
Choices are Disabled, Local Only, Enabled via Network, and Enabled
via In/Out Ports (Network Port Sharing).

Enable support for global outlet groups (linked groups).

Parameters Description

Member Name To link outlet groups on multiple Switched Rack PDUs, you must

define the same Member name on each of the Rack PDUs.
Note: A maximum of four devices can be configured with the same
Member name.

Setting parameters for outlet groups using Network mode.

Parameters Description

Multicast IP To link outlet groups on multiple Switched Rack PDUs, you must

define the same Multicast IP address on each of the Rack PDUs.
Note: A maximum of four devices can be configured with the same
Member name and Multicast IP address.

Authentication
Phrase

Encryption
Phrase

Outlet Group
Port

A phrase of 15 to 32 ASCII characters that verifies that the device is
communicating with other devices, that the message has not been
changed during transmission, and that the message was communicated
in a timely manner. The authentication phrase indicates that it was not
delayed and that it was not copied and sent again later at an
inappropriate time.

A phrase of 15 to 32 ASCII characters that ensures the privacy of the
data (by means of encryption).

The port number on which the device will communicate with other
devices. This must be the same on all PDUs in a group.

Note: Devices attempting to synchronize with Outlet Groups on other devices using network mode must
all have the same Authentication Phrase and Encryption Phrase. The values are hidden to the user.

Create a local outlet group

1. From the Device Manager tab, select Information from the Outlet Groups left navigation

menu.

2. Make sure outlet groups are enabled. (See “Enable outlet groups” on page 63.)

3. Click Create Local Outlet Group.

4. Select the checkboxes of the outlets that will be in the group and assign the group a name in the
Outlet Group Name field. You must select at least two outlets.

Switched Rack PDU User Guide63

Create multiple global outlet groups

To set up multiple global outlet groups that link to outlet groups on other Rack PDUs:

1. From the Device Manager tab, select Information from the Outlet Groups left navigation

menu.

2. Make sure outlet groups are enabled. (See “Enable outlet groups” on page 63.)

3. Click Create Global Outlet Groups.

4. Select the checkboxes of the outlets that will be in the group and then click "Apply and Select
Global Outlets" to select the global outlet for the group. If there is only one outlet in the group,
it will automatically be assigned as the global outlet.

5. To add outlets to any of the global outlet groups you created, see “Edit or delete an outlet group” .

Edit or delete an outlet group

1. From the Device Manager tab, select Information from the Outlet Groups left navigation
menu.

2. In the Configure Group table, click on the number or name of the outlet group to edit or delete.

3. When editing an outlet group you can do any of the following:

– Rename the outlet group.
– Add or remove outlets by clicking the checkboxes to mark or unmark them.

Note: You cannot remove an outlet from an outlet group that contains only two outlets unless
the remaining outlet is a global outlet.

4. To delete the outlet group, click Delete Outlet Group.

64Switched Rack PDU User Guide

Typical outlet group configurations

The following configuration shows two Rack PDUs, each with eight outlet groups. Each outlet group
consists of a single global outlet. Each outlet group  on the first Rack PDU is linked to the outlet group

in the same location on the second Rack PDU. One power cord of a dual-corded server  is



connected to each outlet on the first Rack PDU, and its other cord is connected to the corresponding
outlet on the second Rack PDU, ensuring that output power from both power sources to the server will
turn on or off in a synchronized manner in response to an outlet control action.

The following configuration shows three sets of synchronized outlets. Global outlets are shown in black.
Outlet groups are enclosed in red rectangles.






These four global outlet groups synchronize a total of 19 outlets.
These two global outlet groups synchronize 6 outlets, 2 in one group

and 4 in the other.
This local outlet group synchronizes 3 outlets on the same Rack PDU.

Switched Rack PDU User Guide65

Verify your setup and configuration for global outlet groups

To ensure that your setup meets all system requirements for outlet groups and that you have configured
the outlet groups correctly , select Information from the Outlet Gr oups left navigation menu in the Web
interface to view the groups and their connections:

• The Configure Group table displays the following:

– All configured outlet groups on the current Rack PDU.
– The outlets in each group by outlet number.
– Any outlet groups on other Rack PDUs with which a global outlet group is synchronized. Each

Rack PDU is identified by its IP address if using network mode, or Display ID if using
Network Port Sharing over In/Out ports. Each global outlet is displayed in bold text..

• The Global Outlet Overview section displays the following:

– The IP address or Display ID of the current Rack PDU.
– The IP address or Display ID of any Rack PDUs that contain global outlets that are available

to be synchronized with outlet groups on other Rack PDUs.

– All global outlets configured on the Rack PDUs, regardless of whether they are

synchronizedwith outlet groups on the current Rack PDU.

Outlet Settings for Outlets and Outlet Groups

Initiate a control action

Note: If you apply an outlet control action to outlets or outlet groups, the following delays are used for

the action:

• For an individual outlet (not in an outlet group), the action uses the delay periods and reboot

duration configured for that outlet.

• For a global outlet group, the action uses the delay periods and reboot duration configured for the

global outlet.

• For a local outlet group, the action uses the delay periods configured for the lowest-numbered

outlet in the group.

To control the outlets on your Rack PDU:

1. From the Device Manager tab, select Control from the left navigation menu.

2. Mark the checkboxes for each individual outlet or outlet group to control, or select the All
Outlets checkbox.

3. Select a Control Action from the list, and click Next >>. On the confirmation page that explains
the action, choose to apply or cancel it.

66Switched Rack PDU User Guide

Control actions you can select.

Option Description

No Action Do nothing.
On Immediate Apply power to the selected outlets.
On Delayed Apply power to each selected outlet according to its value for Power On Delay.
Off Immediate Remove power from the selected outlets.
Off Delayed Remove power from each selected outlet according to its value for Power Off

Reboot Immediate Remove power from each selected outlet. Then apply power to each of these

Reboot Delayed Remove power from each selected outlet according to its value for Power Off

Cancel Pending Commands Cancel all commands pending for the selected outlets and keep them in their

†

If a local outlet group is selected, only the configured delays and reboot duration of the lowest-numbered outlet of
the group are used. If a global outlet group is selected, only the configured delays and reboot duration of the global
outlet are used.

†

Delay.

outlets according to its value for Reboot Duration.

†

Delay. Wait until all outlets are off (the highest value for Reboot Duration), and
then apply power to each outlet according to its value for Power On Delay.

present state.
Note: For global outlet groups, you can cancel a command only from the inter-

face of the initiator outlet group. The action will cancel the command for the ini­tiator outlet group and all follower outlet groups.

†

†

Switched Rack PDU User Guide67

Configure outlet settings and the outlet name

The following settings are available:

Setting Description

Name Set the name for one or more outlets. The name is displayed next to the outlet

number on status screens.

External Link Define an HTTP or HTTPS link to a Web site or IP address.

• http://www.apc.com links the outlet to the home page of the APC Web site.

• http://pdu_ip_address, where pdu_ip_address is the IP address of the Rack

PDU and links the outlet to the Web interface of the Rack PDU at the IP
address, enabling authorized users to log on.

Power On Delay Set the number of seconds that the Rack PDU waits after a command is issued

before applying power to an outlet.
Note:To configure an outlet to remain off at all times, select the Never radio

button next to Power On Delay.

Power Off Delay Set the number of seconds that the Rack PDU waits after a command is issued

before removing power from an outlet.
Note:To configure an outlet to remain on at all times, select the Never radio but-

ton next to Power Off Delay.

Reboot Duration Set the number of seconds an outlet remains off before restarting.

To configure outlet settings or outlet names, select the Device Manager tab and then Configuration
from the left navigation menu. Click the Configure Multiple Outlets button in the Outlet
Configuration section or click the outlet name.

• Configure outlet settings for multiple outlets:

– Select the checkboxes next to the numbers of the outlets you want to modify, or select the All

Outlets checkbox.
– Enter values for Name and Link, and click the Apply button immediately below the list.
– Enter values for Power On Delay, Power Off Delay, or Reboot Duration, and click the

Apply button immediately below the list.

• Configure outlet settings for a single outlet:

– Enter values for Name and Link, and click the Apply button immediately below the list.
– Enter values for Power On Delay, Power Off Delay, or Reboot Duration, and click the

Apply button immediately below the list.

68Switched Rack PDU User Guide

Schedule Outlet Actions

Actions you can schedule

To configure values for Power On Delay, Power Off Delay, and Reboot Duration for each outlet, see
“Configure outlet settings and the outlet name” on page 68. Although you must use the Web interface to
schedule outlet actions, you can set these values in either the Web or command line interfaces.

For any outlets you select, you can schedule any of the actions listed in the following table to occur
daily; at intervals of one, two, four, or eight weeks; or only once.

Option Description

No Action Do nothing.
On Immediate Apply power to the selected outlets.
On Delayed Apply power to each selected outlet according to its value for Power On Delay.
Off Immediate Remove power from the selected outlets.
Off Delayed Remove power from each selected outlet according to its value for Power Off

Reboot Immediate Remove power from each selected outlet. Then apply power to each of these

Reboot Delayed Remove power from each selected outlet according to its value for Power Off

†

Delay.

outlets according to its value for Reboot Duration.

Delay. Wait until all outlets are off (the highest value for Reboot Duration), and
then apply power to each outlet according to its value for Power On Delay.

†

†

†

†

If a local outlet group is selected, only the configured delays and reboot duration of the lowest-numbered outlet of
the group are used. If a global outlet group is selected, only the configured delays and reboot duration of the global
outlet are used.

Schedule an outlet event

1. At the Web interface, select the Device Manager tab and then Scheduling from the left

navigation menu.

2. On the Outlet Scheduling page, select how often the event will occur (One-Time, Daily, or

Weekly), and click the Next button.
Note: If you select Weekly, you can choose to have the event occur once every week or once

every two, four, or eight weeks.

3. On the Schedule a Daily Action page, in the Name of event text box, replace the default name,

Outlet Event, with a name that will identify your new event.

4. Use the drop-down lists to select the type of event and when it will occur.

The date format for one-time events is mm/dd, and the time format for all events is hh/mm, with
the two-digit hour specified in 24-hour time.

– An event that is scheduled daily or at one of the intervals available in the Weekly selection

continues to occur at the scheduled interval until the event is deleted or disabled.

– You can schedule a one-time event to occur only on a date within 12 months of the date on

which you perform the scheduling. For example, on December 26, 2011, you could schedule a
one-time event on any date from the current date until December 26, 2012.

5. Use the checkboxes to select which outlets will be affected by the action. You can select one or

more individual outlets or All Outlets.

6. Click Apply to confirm the scheduling of the event, or Cancel to clear it.

When you confirm the event, the summary page is re-displayed, with the new event displayed in the list
of scheduled events.

Switched Rack PDU User Guide69

Edit, disable, enable, or delete a scheduled outlet event

1. At the Web interface, select the Device Manager tab and then Scheduling from the left

navigation menu.

2. In the event list in the Scheduled Outlet Action section of the Scheduling page, click on the

name of the event.

3. On the Daily/Weekly scheduled action detail page, you can do any of the following:

– Change details of the event, such as the name of the event, when it is scheduled to occur, and

which outlets are affected.

– Under Status of event at the top of the page you can perform the following tasks:

• Disable the event, leaving all its details configured so that it can be re-enabled later. A
disabled event will not occur. An event is enabled by default when you create it.

• Enable the event, if it was previously set to Disable.

• Delete the event, removing the event completely from the system. A deleted event cannot
be retrieved.

4. When you finish making changes on this page, click Apply to confirm the changes or Cancel.

Outlet Manager Menu

Create and configure outlet user accounts. Individual outlets can be assigned a user with an Outlet User
account. An Outlet User account allows control only to the outlets assigned. The configuration of outlets
is allowed to those with Administrator rights. The Device Manager has limited outlet configuration
rights.

Configure an outlet user

1. At the Web interface, select the Device Manager tab and then Outlet Manager from the left

navigational menu.

2. Click the Add New User button.

3. Type in the information for the following options and click Apply to confirm the changes.

Option Description

User Name Set the outlet user name. "New User" is reserved and is not allowed.

Note:A user name in orange indicates the user account has been disabled.
Password Set the outlet user password.
User Description Set identification/description of outlet user.
Account Status Enable, disable, or delete outlet user's account.
Device outlet access Select the outlets the user can access.

Outlet Manager and Network Port Sharing

Outlet users can be assigned outlets on any Rack PDU in a group with switched outlets. The outlet users
will be stored on the Host PDU. In the web interface, you can view outlets assigned to a particular PDU
by clicking on its Display ID in the window. Outlet users can be configured on the Device Manager >
Outlet Manager web page.

70Switched Rack PDU User Guide

Environment

Configure Temperature and Humidity Sensors

Path: Environment

Through the Environment tab, when you have a temperature or a temperature and humidity sensor
connected to the Rack PDU, you can set thresholds for Warning and Critical alarm generation (see
“Device status icons” on page 54 for details on each type of alarm).

For temperature:

• If the high temperature threshold is reached, the system generates a Warning alarm.

• If the maximum temperature threshold is reached, the system 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. (See “Hysteresis” on page 71 for details.)

3. Enable alarm generation as desired.

4. Click Apply.

Hysteresis. This value specifies how far past a threshold the temperature 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).

Switched Rack PDU User Guide71

Logs

Use the Event and Data Logs

Event log

Path: Logs > Events > options

You can view, filter, or delete the event log. By default, the log displays all events recorded during the
last two days in reverse chronological order.

For lists of all configurable events and their current configuration, select the Administration tab,
Notification on the top menu bar, and by event under Event Actions on the left navigation menu. See
“Configure by event” on page 92.

To display the event log (Logs > Events > log):

• By default, view the event log as a page of the Web interface. The most recent event is recorded
on page 1. In the navigation bar below the log:

– Click a page number to open a specific page of the log.
– Click Previous or Next to view the events recorded immediately before or after the events

listed on the open page.

– Click << to return to the first page or click >> to view the last page of the log.

• To see the listed events on one page, click Launch Log in New Window from the event log page
to display a full-screen view of the log.

®

Note: In your browser's options, JavaScript
New Window button.

You can also use FTP or Secure CoPy (SCP) to view the event log. See “Use FTP or SCP to retrieve log
files” on page 76.

must be enabled for you to use the Launch Log in

72Switched Rack PDU User Guide

To filter the log (Logs > Events > log):

• Filtering the log by date or time: To display the entire event log, or to change the number of
days or weeks for which the log displays the most recent events, select Last. Select a time range
from the drop-down menu, then click Apply. The filter configuration is saved until the Rack PDU
restarts.

T o display events logged during a specific time range, select From. Specify the beginning and
ending times (using the 24-hour clock format) and dates for which to display events, then click
Apply. The filter configuration is saved until the Rack PDU restarts.

• Filtering the log by event: To specify the events that display in the log, click Filter Log. Clear
the checkbox of an event category or alarm severity level to remove it from view. Text at the
upper right corner of the event log page indicates that a filter is active.
As Administrator, click Save As Default to save this filter as the default log view for all users. If
you do not click Save As Default, the filter is active until you clear it or until the Rack PDU
restarts.
To remove an active filter, click Filter Log, then Clear Filter (Show All).

Note: Events are processed through the filter using OR logic.
Events that you do not select from the Filter By Severity list never display in the filtered event
log, even if the event occurs in a category you selected from the Filter by Category list.
Events that you do not select from the Filter by Category list never display in the filtered event
log, even if devices in the category enter an alarm state you selected from the Filter by Severity
list.

To delete the log (Logs > Events > log):

To delete all events recorded in the log, click Clear Log on the Web page that displays the log. Deleted
events cannot be retrieved. T o disable the logging of events based on their assigned severity level or their
event category, see “Configure by event” on page 92.

To configure reverse lookup (Logs > Events > reverse lookup):

Reverse lookup is disabled by default. Enable this feature unless you have no DNS server configured or
have poor network performance because of heavy network traffic.

With reverse lookup enabled, when a network-related event occurs, both the IP address and the domain
name for the networked device associated with the event are logged in the event log. If no domain name
entry exists for the device, only its IP address is logged with the event. Since domain names generally
change less frequently than IP addresses, enabling reverse lookup can improve the ability to identify
addresses of networked devices that are causing events.

To resize the event log (Logs > Events > size):

By default, the event log stores 400 events. You can change the number of events the log stores. When
you resize the event log, all existing log entries are deleted. To avoid losing log data, use FTP or SCP to
retrieve the log before you enter a new value in the Event Log Size field. See “Use FTP or SCP to
retrieve log files” on page 76.

When the log is full, the older entries are deleted.

Network Port Sharing event logs and traps.

Rack PDU events from guest PDUs are sent to the host PDU for inclusion into its log. The log entry will
include the Display ID of the unit that the event occurred on.
These events are then handled the same as local events from the host PDU. Therefore alarms, SNMP
traps, e-mails, Syslog, etc will support Rack PDU events and alarms from all Rack PDUs in a group.

Example event log: Rack PDU 4: Outlet #2 off.
Note: System events will only be logged for the host PDU. System events from guest PDUs will not be

logged on the host PDU.

Switched Rack PDU User Guide73

Data log

Path: Logs > Data > options

The data log records the current and power for the device, phase, and banks, as well as temperature and
humidity at the specified time interval. Each entry is listed by the date and time the data was recorded.

To display the data log (Logs > Data > log):

• By default, view the data log as a page of the W eb interface. The most recent data item is recorded
on page 1. From the navigation menu below the log:

– Click a page number to open a specific page of the log.
– Click Previous or Next to view the data recorded immediately before or after the data that is

listed on the open page.

– Click << to return to the first page of the log, or click >> to view the last page of the log.

• To see the listed data on one page, click Launch Log in New Window from the data log page to
display a full-screen view of the log.

Note: In your browser's options, JavaScript

must be enabled for you to use the Launch Log in

New Window button.

Alternatively, you can use FTP or SCP to view the data log. See “Use FTP or SCP to retrieve log files”

on page 76.

To filter the log by date or time (Logs > Data > log):

To display the entire data log or to change the number of days or weeks for which the log displays the
most recent events, select Last. Select a time range from the drop-down menu, then click Apply. The
filter configuration is saved until the device restarts.

To display data logged during a specific time range, select From. Specify the beginning and ending
times (using the 24-hour clock format) and dates for which to display data, then click Apply. The filter
configuration is saved until the device restarts.

To delete the data log:

To delete all data recorded in the log, click Clear Data Log on the Web page that displays the log.
Deleted data cannot be retrieved.

To set the data collection interval (Logs > Data > interval):

Define, in the Log Interval setting, how frequently data is sampled and stored in the data log, and view
the calculation of how many days of data the log can store, based on the interval you selected. When the
log is full, the older entries are deleted. To avoid automatic deletion of older data, enable and configure
data log rotation, described in the next section.

74Switched Rack PDU User Guide

To configure data log rotation (Logs > Data > rotation):

Set up a password-protected data log repository on a specified FTP server. Enabling rotation causes the
contents of the data log to be appended to the file you specify by name and location. Updates to this file
occur at the upload interval you specify.

Parameter Description

Data Log Rotation Enable or disable (the default) data log rotation.
FTP Server Address The location of the FTP server where the data repository file is stored.
User Name The user name required to send data to the repository file. This user must also

be configured to have read and write access to the data repository file and the

directory (folder) in which it is stored.
Password The password required to send data to the repository file.
File Path The path to the repository file.
Filename The name of the repository file (an ASCII text file).
Delay X hours between

uploads
Upload every X minutes The number of minutes between attempts to upload data to the file after an

Up to X times The maximum number of times the upload will be attempted after an initial

Until Upload Succeeds Attempt to upload the file until the transfer is completed.

The number of hours between uploads of data to the file.

upload failure.

failure.

To resize the data log (Logs > Data > size):

By default, the data log stores 500 records. You can change the number of records the log stores. When
you resize the data log, all existing log records are deleted. To avoid losing records, use FTP or SCP to
retrieve the log before you enter a new value in the Data Log Size field. See “Use FTP or SCP to retrieve
log files” on page 76.

When the log is full, the older entries are deleted.

Network Port Sharing Data Log.

The host Rack PDU will poll data from guest PDUs so that data from all PDUs in a group are available.
To view data from a different Rack PDU in a group, select the desired Rack PDU from the "Filter Log"
pull-down list.

Similarly for data log graphing, you can select a different Rack PDU by clicking on the "Change Data
Filter" button.

Switched Rack PDU User Guide75

Use FTP or SCP to retrieve log files

An Administrator or Device User can use FTP or SCP to retrieve a tab-delineated event log file
(event.txt) or data log file (data.txt) and import it into a spreadsheet.

• The file reports all events or data recorded since the log was last deleted or (for the data log)
truncated because it reached maximum size.

• The file includes information that the event log or data log does not display.

– The version of the file format (first field)
– The date and time the file was retrieved
– The Name, Contact, and Location values and IP address of the Rack PDU
– The unique Event Code for each recorded event (event.txt file only)

Note: The Rack PDU uses a four-digit year for log entries. You may need to select a four-digit
date format in your spreadsheet application to display all four digits.

If you are using the encryption-based security protocols for your system, use SCP to retrieve the log file.
If you are using unencrypted authentication methods for the security of your system, use FTP to retrieve

the log file.
See the Security Handbook, available at www.apc.com, for information on available protocols and

methods for setting up the type of security you need.

To use SCP to retrieve the files. To use SCP to retrieve the event.txt file:

scp username@hostname_or_ip_address:event.txt ./event.txt

To use SCP to retrieve the data.txt file, use the following command:
scp username@hostname_or_ip_address:data.txt ./data.txt

To use FTP to retrieve the files. To use FTP to retrieve the event.txt or data.txt file:

1. At a command prompt, type

ftp and the IP address of the Rack PDU, and press ENTER.

If the Port setting for the FTP Server option (set through the Network menu of the
Administration tab) has been changed from its default (

21), you must use the non-default

value in the FTP command. For W indows FTP clients, use the following command, including
spaces. (For some FTP clients, you must use a colon instead of a space between the IP address
and the port number.)

ftp>open ip_address port_number

To set a non-default port value to enhance security for the FTP Server, see “FTP Server” on
page 90. You can specify any port from 5001 to 32768.

2. Use the case-sensitive User Name and Password for Administrator or Device User to log on. For

Administrator, apc is the default for User Name and Password. For the Device User, the defaults
are device for User Name and apc for Password.

3. Use the get command to transmit the text of a log to your local drive.

ftp>get event.txt

or

ftp>get data.txt

4. Type quit at the ftp> prompt to exit from FTP.

76Switched Rack PDU User Guide

Administration: Security

Local Users

Setting user access

Path: Administration > Security > Local Users > options

The Administrator user account always has access to the Rack PDU.
The Device User and Read-Only User accounts are enabled by default. To disable the Device User or

Read-Only User accounts, select the user account from the left navigation menu, then clear the Enable
checkbox.

You set the case-sensitive user name and password for each account type in the same manner. Maximum
length is 64 characters for a user name and 64 characters for a password. Blank passwords (passwords
with no characters) are not allowed.

For information on the permissions granted to each account type (Administrator, Device User, and Read­Only User), see “Types of User Accounts” on page 2.

Account Type Default User Name

Administrator apc apc Web interface and command

Device User device apc
Read-Only User readonly apc Web interface only

Default Password Permitted Access

line interface

Remote Users

Authentication

Path: Administration > Security > Remote Users > Authentication Method

Use this option to select how to administer remote access to the Rack PDU.
For information about local authentication (not using the centralized authentication of a RADIUS

server), see the Security Handbook, available at www.apc.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.

Switched Rack PDU User Guide77

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: Administration > Security > Remote Users > RADIUS

Use this option to do the following:

• List the RADIUS servers (a maximum of two) available to the Rack PDU and 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. Non-stan-

dard ports are currently unsupported.
Secret The shared secret between the RADIUS server and the Rack PDU.
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.

78Switched Rack PDU User Guide

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 Vendor 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-T ype attributes unless Vendor Specific Attributes (VSAs)
are defined. If no Service-T ype attributes are configured, users will have read-only 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

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

Device.

Supported RADIUS servers

FreeRADIUS and Microsoft IAS 2003 are supported. Other commonly available RADIUS applications
may work but have not been fully tested.

Switched Rack PDU User Guide79

RADIUS and Network Port Sharing

Note: See the Security Handbook for APC Network Management Cards for more information on using

RADIUS.
For RADIUS users file with VSAs, outlets on guest Rack PDUs can be associated to RADIUS users by

using the following method.
# give user access to outlets 1, 2, and 3 on unit 1,

# outlet 7 on unit 2, outlets 1 through 6
# on unit 3, and outlets 1,2,4 through 6, 7 through 10,
# and 20 on unit 4

newOutletUser Auth-Type = Local, User-Password = "newoutlets"
APC-Service-Type = Outlet,
APC-Outlets = "1[1,2,3];2[7];3[1-6];4[1,2,4-6,7-10,20];"

Inactivity Timeout

Path: Administration > Security > Auto Log Off

Use this option to configure the time (3 minutes by default) that the system waits before logging off 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.

80Switched Rack PDU User Guide

Administration: Network Features

TCP/IP and Communication Settings

TCP/IP settings

Path: Administration > 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 Use prior settings (the default) or Stop BOOTP request.

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:

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

Switched Rack PDU User Guide81

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 options 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 Vendor Specific Information 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 Time (option 51): The time duration 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.

82Switched Rack PDU User Guide

Path: Administration > 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: Administration > 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).

Ping Response

Path: Administration > Network > Ping Response

• Select the Enable check box for IPv4 Ping Response to allow the NMC to respond to network
pings. Clear the check box to disable an NMC response. This does not apply to IPv6.

Switched Rack PDU User Guide83

DNS

Path: Administration > Network > DNS > options

Use the options under DNS to configure and test the Domain Name System (DNS):

• Select

• Host Name: Configure a host name here and a domain name in the Domain Name field then

• Domain Name (IPv4): Configure the domain name here only. In all other fields in the NMC

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

users can enter a host name in any field in the NMC interface (except e-mail addresses) that
accepts a domain name.

interface (except e-mail addresses) that accept domain names, the NMC 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.

address of the primary DNS server.

• Domain Name (IPv6): Specify the IPv6 domain name here.

• Select

test to send a DNS query that tests the setup of your DNS servers:

– As Query Type, select the method to use for the DNS query:

• by Host: the URL name of the server

• by FQDN: the fully-qualified domain name

• by IP: the IP address of the server

• by MX: the Mail Exchange used by the server

– 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

– View the result of the test DNS request in the Last Query Response field.

84Switched Rack PDU User Guide

Web

Path: Administration > Network > Web > options

Option Description

access To activate changes 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 command 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.apc.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 from 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.

• V alid 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
the interface for up to one minute.

based security, but a security alert message displays whenever you log on.

Rack PDU generates a default certificate, a process which delays access to

You can use the default certificate for basic encryption-

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.apc.com, to choose a method for using digital certificates created by the Security W izard or

generated by the Rack PDU.

Remove: Delete the current certificate.

Switched Rack PDU User Guide85

Console

Path: Administration > Network > Console >

options

Option Description

access Choose one of the following for access by Telnet or Secure SHell (SSH):

• 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 communicate with the Rack PDU (23 by default). You can

•
change the port setting to any unused port 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:

telnet 152.214.12.114:5000
telnet 152.214.12.114 5000

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

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 APC Security Wizard, see the Security Handbook, available at www.apc.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
host key, and the SSH server is not accessible during that time.

Rack PDU takes up to one minute to create a

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.

86Switched Rack PDU User Guide

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 status information and use SNMP
traps.)

When using StruxureWare Data Center Expert to manage a Rack PDU on the public network of an
StruxureWare Data Center Expert, you must have SNMP enabled in the Rack PDU interface. Read
access will allow the StruxureWare Data Center Expert 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 Data Center
Expert as a trap receiver.

For detailed information on enhancing and managing the security of your system, see the Security
Handbook, available at www.apc.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(26)

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 PDU
temporarily loses communication. The index order should only change if you manually remove a Rack
PDU from the group.

An MIB table walk should skip the indexes associated with a Rack PDU that has temporarily lost
communication.

Switched Rack PDU User Guide87

SNMPv1

Path: Administration > 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 T ype: 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.

88Switched Rack PDU User Guide

SNMPv3

Path: Administration > Network > SNMPv3 > options

For SNMP GETs, SETs, and trap receivers, SNMPv3 uses a system of user profiles to identify users. An
SNMPv3 user must have a user profile assigned in the MIB software program to perform GETs and
SETs, 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 SNMPv3 Access: 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

edit the following settings for a user profile, click a user name in the list.

through apc snmp profile4, and no authentication and no privacy (no encryption). To

User Name: The identifier of the user profile. SNMP version 3 maps GETs, SETs, and traps to a

user profile by matching the user name of the profile to the user name in the data packet being
transmitted. A user name can have up to 32 ASCII characters.

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

Switched Rack PDU User Guide89

Option Description

access
control

You can configure up to four access control entries to specify which NMSs have access to this
device. The opening page for access control, by default, assigns 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 NMS 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: Administration > Network > FTP Server

The FTP Server settings enable (by default) 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 Dat Center

Expert, 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.apc.com.

ftp 152.214.12.114:5001.

90Switched Rack PDU User Guide

Administration: Notification

Event Actions

Path: Administration > Notification > Event Actions > options

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
– APC 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 data to use for device monitoring. See “Data log” on

page 74 for information on how to configure and use this data logging option.

– Queries (SNMP GETs)

For more information, see “SNMP” on page 87. SNMP enables an NMS to perform
informational queries. For SNMPv1, which does not encrypt data before transmission,
configuring the most restrictive SNMP access type (READ) enables informational queries
without the risk of allowing remote configuration changes.

Configure event actions

Notification parameters. For events that have an associated clearing event, you can also set the

following parameters as you configure events individually or by group, as described in the next two
sections. To access the parameters, click the receiver or recipient name.

Parameter Description

Delay x time before
sending

Repeat at an interval
of x time

Up to x times During an active event, the notification repeats for this number of times.
Until condition

clears

If the event persists for the specified time, a notification is sent. If the condition clears
before the time expires, no notification is sent.

The notification is sent at the specified interval (e.g., every 2 minutes).

The notification is sent repeatedly until the condition clears or is resolved.

Switched Rack PDU User Guide91