User Guide InfraStruxure 150kVA Power Distribution Unit PDPB150G6F
Contents Introduction ..................................................................... 1 Product Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Network management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Internal Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Overview . . . . . . . . . . .
Interface Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 12 ? or help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 about . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 alarmcount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Panels & Subfeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Breakers & Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Manufacturing Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Input Contacts . . . . . .
icTarget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 icName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 icLoc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 icNormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 icAlarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration: Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Inactivity Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Administration: Network Features . . . . . . . . . . . . . . . . . . . . . . . . . . 75 TCP/IP Settings . . . .
Export Configuration Settings ..................................... 98 Retrieve and Export the .ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Summary of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Contents of the .ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Detailed procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 The Upload Event and Error Messages . . . . . . . . . . . .
Introduction Product Features The Network Management Card (NMC) in your Power Distribution Unit (PDU) provides power distribution and management of electrical power to equipment racks. The NMC provides full management capabilities over a network using Telnet, Secure SHell (SSH), HyperText Transfer Protocol (HTTP), HTTP over Secure Sockets Layer (HTTPS), File Transfer Protocol (FTP), Secure CoPy (SCP), Modbus, and Simple Network Management Protocol (SNMP) versions 1 and 3.
Network management features These applications and utilities work with a PDU that connects to the network through its Network Management Card (NMC): • StruxureWare—Provide enterprise-level power management and management of APC agents, PDUs, information controllers, and environmental monitors • APC PowerNet® Management Information Base (MIB) with a standard MIB browser—Perform SNMP SETs and GETs and to use SNMP traps • Device IP Configuration Wizard—Configure the basic settings of one or more Network Manage
• A Read-Only User has the following restricted access: – Access through the Web interface only. You must use the Web interface to configure values for the Read-Only User. – Access to the same tabs and menus as a Device User, but without any capability to change configurations, control devices, delete data, or use file transfer options. Links to configuration options are visible but disabled, and the event and data logs display no button to clear the log.
Watchdog Features Overview To detect internal problems and recover from unanticipated inputs, the NMC 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 NMC implements internal watchdog mechanisms to protect itself from becoming inaccessible over the network. For example, if the NMC does not receive any network traffic for 9.
Command Console Overview Overview Use either a local (serial) connection, or a remote (Telnet or SSH) connection with a computer on the same network as the PDU to access the command line interface. Use case-sensitive user name and password entries to log on (by default, apc and apc for an Administrator, or device and apc for a Device User). A Read-Only User cannot access the command line interface. If you cannot remember your user name or password, see “How to Recover from a Lost Password” on page 3.
Local access to the command line interface For local access, use a computer that connects to the 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 the port. 2. Connect the provided serial cable (part number 940-0299) from the selected port on the computer to the configuration port at the PDU. 3. Run a terminal program (e.g.
• The User field reports whether you logged in through the Administrator or Device Manager account. (The Read Only User account cannot access the command line interface.) When you log on as Device Manager (equivalent to Device User in the Web interface), you can access the event log, configure some settings, and view the number of active alarms. User : Administrator • The Stat field reports the PDU status. Stat:P+ N+ A+ P+ IPv4 only The APC operating system (AOS) is functioning properly.
Options The command line interface provides options to configure the network settings and manage the PDU. At the command line interface, use commands to configure the PDU. To use a command, type the command and press ENTER. Commands and arguments are completely case insensitive. 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.
Command syntax Item Description <> Options are preceded by a hyphen. Definitions of options are enclosed in angle brackets. For example: -dp If a command accepts multiple options or an option accepts mutually exclusive arguments, the values may be enclosed in brackets. A pipe symbol (vertical line) between items enclosed in brackets or angle brackets indicates the word OR, meaning that the items are mutually exclusive. You must use one of the items. [] | Argument Quoting.
Syntax examples [ []] For the above example: arg1 must be used, but arg2-4 are optional. If arg2 is used, then arg3a or arg3b must also be used. arg4 is optional, but arg1-3 must be precede arg4. With most commands if the last argument is omitted then the command provides information to the user, otherwise the last argument is used to change/set new information.
Command Response Codes The command line interface reports all command operations with the following format: E [0–9][0–9][0–9]: Error message Code Message Notes E000 Success E001 Successfully Issued 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 E200 Input error Only reported when an error occurs during the execution of a command.
Interface Management Commands ? or help Access: Administrator, Device Description: View a list of all the commands available to your account type. To view help text for a specific command, type the command followed by a question mark (?) or the word help.
about Access: Administrator, Device Description: View hardware and firmware information (Model Number, Serial Number, Manufacture Dates). 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 Description: Display the count alarms that are present with-in the system. The 'all' option is the default when no parameters are entered. Option Arguments Description -p all View the number of active alarms reported by the NMC. 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.
boot Access: Administrator only Description: Allows the user to get/set the network startup configuration of the device, such as setting boot mode (DHCP vs BOOTP vs MANUAL). Defines how the NMC 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 dhcp | bootp | manual Define how the TCP/IP settings will be configured when the NMC turns on, resets, or restarts.
cd Access: Administrator, Device User Description: Allow the user to set the working directory of the file system. The working directory is set back to the root directory '/' when the user logs out of the command line interface.
date Access: Administrator only Definition: Set the date and time. 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 Select the numerical format in which to display all dates in this user interface.
dir Access: Administrator, Device Description: Display the files and folders stored in the working directory. Example: apc> dir E000: Success --wx-wx-wx 1 --wx-wx-wx 1 -rw-rw-rw- 1 drwxrwxrwx 1 drwxrwxrwx 1 drwxrwxrwx 1 drwxrwxrwx 1 drwxrwxrwx 1 drwxrwxrwx 1 drwxrwxrwx 1 apc apc apc apc apc apc apc apc apc apc apc apc apc apc apc apc apc apc apc apc 3145728 3145728 45000 0 0 0 0 0 0 0 Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar 3 4 6 3 3 3 3 3 3 3 2012 2012 2012 2012 2012 2012 2012 2012 2012 2012 aos.
eventlog Access: Administrator, Device User Description: View the date and time you retrieved the event log, the status of the PDU, and the status of sensors. 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.
exit or quit Access: Administrator, Device User Description: Exit/Quit/ Leave the command line interface session. Example: apc> exit Bye format Access: Administrator only Description: Reformat the file system and erase all security certificates, encryption keys, configuration settings, and the event and data logs. Be careful with this command. Note: To reset to the default configuration, use the resetToDef command. Parameters: None, but you must enter a "YES" to confirm after the command has been issued.
ping Access: Administrator, Device 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 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 192.168.1.50 is connected to the network, type: apc> ping 192.168.1.50 E000: Success Reply from 192.168.1.
prompt Access: Administrator, Device User Description: Allow the user to change the format of the prompt, either short or long. 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.
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 “RADIUS” on page 73. Additional authentication parameters for RADIUS servers are available at the Web interface of the PDU. See “RADIUS” on page 73.
reboot Access: Administrator only Description: Restart the interface of the PDU. Confirm the operation by entering a "YES" after the command has been entered. Example: apc> reboot E000: Success Reboot Management Interface Enter 'YES' to continue or to cancel Rebooting... resetToDef Access: Administrator only Description: Reset all configuration parameters to the factory default. Confirm the operation by entering a "YES" after the command has been entered.
system Access: Administrator only Description: View and set the system name, contact, and location. If no parameters are entered, then the device displays all of the current system descriptions. If the second parameter is not entered, then the device displays the current system description. If the second parameter is entered, that parameter is stored at the appropriate retentive memory address.
tcpip6 Access: Administrator only Description: Enable IPv6 and view and manually configure these network settings for the PDU: Option Argument Description -S enable | disable Enable or disable IPv6. -man enable | disable Enable manual addressing for the IPv6 address of the NMC. -auto enable | disable Enable the NMC to automatically configure the IPv6 address. -i Set the IPv6 address of the PDU. -g Set the IPv6 address of the default gateway.
web Access: Administrator Description: Enable access to the Web interface using HTTP or HTTPS. For additional security, you can change the port setting for HTTP and HTTPS to any unused port from 5000 – 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: http://152.214.12.114:5000 Option Argument Definition -S disable | http | https Configure access to the Web interface.
xferStatus Access: Administrator only Description: View the result of the last INI file transfer. Example: apc> xferStatus E000: Success Result of last file transfer: Failure unknown See “Verifying Upgrades and Updates” on page 105 for descriptions of the transfer result codes.
Device Management Commands Many device management commands are settable and will accept data values in integer or floating-point format. Once a value has been entered it may be rounded based on the command. For example: If the user sets a command to a value of 1.33 and that command has a resolution of 0.1, then the value will be rounded to 1.3. The value will be checked against the acceptable range of the command before being accepted. The commands are logically segmented to represent the physical device.
Panels & Subfeed Power distribution is accomplished through two breaker panels and one subfeed. In this application, subfeed #1 monitors distribution panel 1, subfeed #2 monitors distribution panel 2 and subfeed #3 monitors the distribution subfeed. This information is vital to and repeated in the subfdTarget command.
Breakers & Cables Each breaker and associated cables can be queried for status, configured for alarm thresholds and identified with name and location. The Command Console implements a "panel.breaker” notation in the commands, for example: 2.13 indicates panel 2 breaker 13.
Output Relays The output relays provide a means to generate an external signal based on predetermined conditions. The signal can be generated based on subfeed and/or system voltage and current thresholds and frequency deviation and input contacts. This functionality is more intuitive to configure on the web interface.
sysOutput Access: Administrator, Device Description: View each phase-to-phase voltage, each phase-to-neutral voltage, load supported by each phase and the frequency. Output measurements are made at the transformer. Example: apc> sysOutput 1. L1-L2,0V,L2-L3,0V,L3-L1,0V 2. L1,119V,19.4A,2.4kW,1.0,L2,119V,22.9A,2.7kW,1.0,L3,118V,21.1A,2.6kW,1.0 3. 60.0Hz sysAlrmCfg Access: Administrator, Device Description: View the configuration of the system alarm thresholds.
sysThrMxV Access: Administrator, Device Description: Configure the maximum voltage (L-N) alarm threshold and enable corresponding critical alarm. Parameters: [] [] Fraction = percent above device nominal voltage. Example: apc> sysAlrmCfg 1. MaxV,+20%,Disable,HiV,+12%,Disable,LoV,-12%,Disable,MinV,-20%,Disable 2. MaxA,0%,Disable,HiA,0%,Disable,LoA,0%,Disable,MinA,0%,Disable,Freq, Disable apc> sysThrMxV 25 Enable 1. 25%,Enable apc> sysAlrmCfg 1.
sysThrMnV Access: Administrator, Device Description: Configure the minimum voltage (L-N) alarm threshold and enable a corresponding critical alarm. The minus sign is implied, not expressed. Parameters: [] [] Fraction = percent below device nominal voltage. Example: apc> sysThrMnV 1. -20%,Disable apc> sysThrMnV Enable 1. -20%,Enable apc> sysThrMnV 1.
sysThrLoI Access: Administrator, Device Description: Configure the low current alarm threshold and enable a corresponding warning alarm. Parameters: [] [] Fraction = percent of rated current. Example: apc> sysThrLoI 1. 0%,Disable apc> sysThrLoI 30 Enable 1. 30%,Enable apc> sysThrLoI 1. 30%,Enable sysThrMnI Access: Administrator, Device Description: Configure the low current alarm threshold and enable a corresponding warning alarm.
subfdStatus Access: Administrator, Device Description: If no parameter is entered, the status of the subfeeds is displayed (name, alarm condition, power and location). If a parameter is entered, the alarm status, subfeed breaker position, breaker rating, energy usage and date last reset are displayed. Current, percent of capacity, power and current alarm per phase are also displayed. Parameters: [] Subfeed = 1 to number of subfeeds.
subfdLoc Access: Administrator, Device Description: Configure the location of the targeted subfeed. Parameters: [] location = a string of up to 20 characters Example: apc> subfdTarget 1 1. Enable,Enable,89%,Enable,72%,Enable,30%,Enable,20%,Disable 2. Open,Critical,160A,765kWh,10/27/2012 apc> subfdStatus 1. Panel 1, Normal,0.0kW,Sub Location 1 2. Panel 2, Normal,0.0kW,Sub Location 2 3. Subfeed, Normal,0.0kW,Sub Location 3 apc> subfdLoc "New Location 1" 1. Panel 1, Normal,0.
subfdThrMx Access: Administrator, Device Description: Configure the maximum load alarm threshold and critical alarm for target subfeed. Parameters: [[] [ ]] Thresh = % rated load Example: apc> subfdStatus 1 1. Normal,Open,160A,765kWh,10/27/2012 2. Disable,Enable,90%,Disable,70%,Disable,20%,Disable,10%,Disable apc> subfdThrMx 95 enable 1. Disable,Enable,95%,Enable,70%,Disable,20%,Disable,10%,Disable apc> subfdStatus 1 1. Normal,Open,160A,765kWh,10/27/2012 2.
subfdThrLo Access: Administrator, Device Description: Configure the low load alarm threshold and warning alarm for the target subfeed. Parameters: [[] [ ]] Thresh = % rated load Example: apc> subfdStatus 1 1. Normal,Open,160A,765kWh,10/27/2012 2. Disable,Enable,95%,Enable,75%,Enable,20%,Disable,10%,Disable apc> subfdThrLo 25 enable 1. Disable,Enable,95%,Enable,75%,Enable,25%,Enable,10%,Disable apc> subfdStatus 1 1. Normal,Open,160A,765kWh,10/27/2012 2.
subfdBrkr Access: Administrator, Device Description: Configure the breaker position critical alarm for the target subfeed. Parameters: [] Example: apc> subfdStatus 1 1. Normal,Open,160A,765kWh,10/27/2012 2. Disable,Enable,95%,Enable,75%,Enable,25%,Enable,5%,Enable apc> subfdBrkr disable 1. Disable,Disable,95%,Enable,75%,Enable,25%,Enable,5%,Enable apc> subfdStatus 1 1. Normal,Open,160A,765kWh,10/27/2012 2.
brkrPanel Access: Administrator, Device Description. Select the panel containing the breaker to access. The response to a brkrPanel selection is to display the following information, two lines per breaker. The first line contains panel, breaker, breaker name, breaker location, breaker cable description, breaker rating, corresponding CT rating, alarm status, power, energy consumption and date of last energy reset date.
Example: apc>brkrStatus 1. 1.1,pb1-1,Unknown,,20A,50A,Normal,0.0kW,1.7kWh,08/01/2012 2. 1.1,L1,0.0A,0.0%,1.3,L2,0.0A,0.0%,1.5,L3,0.0A,0.0% 3. 1.7,pb1-7,Unknown,,30A,50A,Normal,0.0kW,0.0kWh,08/01/2012 4. 1.7,L1,0.0A,0.0%,1.9,L2,0.0A,0.0%,1.11,L3,0.0A,0.0% 5. 1.13,pb1-13,Unknown,,30A,50A,Normal,0.0kW,0.0kWh,08/01/2012 6. 1.13,L1,0.0A,0.0%,1.15,L2,0.0A,0.0%,1.17,L3,0.0A,0.0% 7. 1.21,pb1-21,Unknown,,30A,50A,Normal,0.0kW,0.0kWh,08/01/2012 8. 1.21,L2,0.0A,0.0%,1.23,L3,0.0A,0.0% 9. 1.
brkrName Access: Administrator, Device Description. Configure the name on the breaker selected by the previous brkrTarget and brkrPanel commands. The response generated is the same as the two line response generated by the brkrStatus command with no parameter. Parameters: (name = string of up to 20 characters. Quotes are required if string contains a space.) Example: apc> brkrStatus 2 1. 1.2,Unknown,Unknown,Unknown,30A,50A,Normal,30.2kW,60.2kWh,11/08/2012 2. 1.2,L1,10.2A,34.0%,1.4,L2,10.4A,34.6%,1.
brkrAlrm Access: Administrator, Device Description. Enables alarm generation on the cable breaker selected by the brkrTarget and brkrPanel commands. The response contains 1 line containing the panel.breaker, followed by the alarm thresholds and enables. Parameters: (switch=enable|disable) Example: apc> brkrstatus 2 1. 1.2,Newname 1.2,Newloc 1.2,Unknown,30A,50A,Normal,30.2kW,60.2kWh,11/08/ 2012 2. 1.2,L1,10.2A,34.0%,1.4,L2,10.4A,34.6%,1.6,L3,10.6A,35.3% 3. 1.
brkrThrMx Access: Administrator, Device Description. Configure the max load alarm threshold and critical alarm on the breaker selected by the brkrTarget and brkrPanel commands. Valid threshold values are 0-100% where ThrMx > ThrHi > ThrLo > ThrMn. Parameters: [] [] (Thresh = % rated load) Example: apc> brkrstatus 2 1. 1.2,Newname 1.2,Newloc 1.2,Unknown,30A,50A,Normal,30.2kW,60.2kWh,11/08/ 2012 2. 1.2,L1,10.2A,34.0%,1.4,L2,10.4A,34.6%,1.6,L3,10.6A,35.3% 3. 1.
brkrThrLo Access: Administrator, Device Description. Configure the low load alarm threshold and warning alarm on the breaker selected by the brkrTarget and brkrPanel commands. Valid threshold values are 0-100% where ThrMx > ThrHi > ThrLo > ThrMn. Parameters: [] [] (Thresh = % rated load ) Example: apc> brkrstatus 2 1. 1.2,Newname 1.2,Newloc 1.2,Unknown,30A,50A,Normal,30.2kW,60.2kWh,11/08/ 2012 2. 1.2,L1,10.2A,34.0%,1.4,L2,10.4A,34.6%,1.6,L3,10.6A,35.3% 3. 1.
brkrRstkWh Access: Administrator, Device Description. Reset the usage and usage date on the breaker selected by the brkrTarget and brkrPanel commands. Parameters: None. Example. apc> cblRstkWh brkrstatus 2 1. 1.2,Newname 1.2,Newloc 1.2,Unknown,30A,50A,Normal,30.2kW,60.2kWh,11/08/ 2012 2. 1.2,L1,10.2A,34.0%,1.4,L2,10.4A,34.6%,1.6,L3,10.6A,35.3% 3. 1.2,Enable,85%,25A,Enable,65%,19A,Enable,13%,3A,Disable,5%,1A,Disable apc> brkrrstkWh Panel 1, Breaker 2 reset kWh complete apc> brkrstatus 2 1. 1.2,Newname 1.
brkrAdd Access: Administrator, Device Description. Add a breaker at the panel position selected by the brkrTarget and brkrPanel commands. The required inputs are the number of poles, the CT rating and breaker rating. Parameters: <# poles> #poles = number of poles the breaker protects (must be 1,2,3) CT = rating of the current transformer monitoring the positions (must be 50 | 100) Rating = rating of the breaker being monitored (must be <= 100) Example. apc> brkrPanel 2 1. 2.
mfactMeter Access: Administrator, Device Description: Displays model number, serial number, date of manufacture and firmware revision for each metering device in the PDU. Example: apc> mfactMeter 1. 0P3464,0534640902807779,10/08/2010,01.02 2. 0P3464,0534640902807783,10/08/2010,01.02 mfactIs Access: Administrator, Device Description: Reads and displays two panels of currents directly from the Veris board. Example: apc> mfactIs 1. Panel 1 2. 1-0.0,2-0.0,3-0.0,4-0.0,5-0.0,6-0.0,7-0.0, 3. 8-0.0,9-0.0,10-0.
10. 11. 12. 13. 14. 8-50,9-50,10-50,11-50,12-50,13-50,14-50, 15-50,16-50,17-50,18-50,19-50,20-50,21-50, 22-50,23-50,24-50,25-50,26-50,27-50,28-50, 29-50,30-50,31-50,32-50,33-50,34-50,35-50, 36-50,37-50,38-50,39-50,40-50,41-50,42-50, mfactkWs Access: Administrator, Device Description: Reads and displays two panels of the power readings, in kilowatts, directly from the Veris board. See the Veris modbus documentation for scaling. Example: apc> mfactkWs 1 1. Panel 1 single phase power values 2.
mfactkWhs Access: Administrator, Device Description: Reads and displays two panels of the energy readings, in kilowatts, directly from the Veris. See Veris modbus documentation for scaling. Example: apc> mfactkWhs 1. Panel 1 energy values 2. 1-5382772, 2-0, 3-5605433, 4-0, 5-7642557, 6-0, 7-0, 3. 8-14428603, 9-3236, 10-8239745, 11-1094, 12-10269935, 13-102348, 14-0, 4. 15-3248, 16-0, 17-12494896, 18-0, 19-2071234, 20-0, 21-23854, 5. 22-5382772, 23-0, 24-5605433, 25-0, 26-7642557, 27-0, 28-0, 6.
icStatus Access: Administrator, Device Description: Display input contact, alarm status, alarm severity, alarm enable, contact state and location of each input contact in the PDU. Example: apc> icStatus 1. User Contact 2. User Contact 3. User Contact 4.
icLoc Access: Administrator, Device Description: Configure the location of the targeted input contact. Parameters: location = character string of up to 20 characters. Example: apc> icStatus 1. New Contact 1,Normal,Critical,Enable,Open,Location 1 2. User Contact 2,Normal,Warning,Enable,Open,Location 2 3. User Contact 3,Normal,Warning,Enable,Open,Location 3 4. User Contact 4,Normal,Critical,Enable,Open,Location 4 apc> icLoc "Door Switch" 1.
icAlarm Access: Administrator, Device Description: Enable/disable alarm of the targeted input contact. Parameters: alarm = enable|disable Example: apc> icStatus 1. New Contact 1,Critical,Critical,Open,Door Switch 2. User Contact 2,Normal,Warning,Open,Location 2 3. User Contact 3,Normal,Warning,Open,Location 3 4. User Contact 4,Normal,Critical,Open,Location 4 apc> icAlarm disable //disabling clears the alarm 1. New Contact 1,Normal,Critical,Closed,Door Switch apc> icStatus 1.
orStatus Access: Administrator, Device Description: Display the output relay name and the state of each output relay in the PDU. Example: apc> orStatus 1. Output Relay 2. Output Relay 3. Output Relay 4. Output Relay 1,Closed 2,Closed 3,Closed 4,Closed orTarget Access: Administrator, Device Description: Select the output relay to configure. Parameters: [relay] relay = output relay of interest(normally 1|2|3|4). Example: apc> orTarget 1 1.
orNormal Access: Administrator, Device Description: Configure the normal state of the targeted output relay. The output relay will remain in the normal state until a condition occurs that causes the output relay to change to the state opposite the normal state. Parameters: normal state = open|closed. Example: apc> orTarget 1 1. Output Relay 1,Closed apc> orStatus 1. Output Relay 2. Output Relay 3. Output Relay 4. Output Relay 1,Closed 2,Closed 3,Closed 4,Closed apc> orNormal open 1.
orSubxxxx Access: Administrator, Device Description: This category of alarm mapping commands associates a subfeed threshold alarm with the output relay/relays designated in the parameters. With no parameter, display the current associated relays. Subfeed alarm association commands: orSub1MxI orSub1HiI orSub1LoI orSub1MnI orSub1Brk orSub2MxI orSub2HiI orSub2LoI orSub2MnI orSub2Brkr Parameters: [ ] relay = output relay to be triggered(normally 1|2|3|4). Example: apc> orSub1Brkr 1.
Parameters: [ ] relay = output relay to be triggered(normally 1|2|3|4). Example: apc> orSysFreq 1. System Frequency,1,disable,2,disable,3,disable,4,disable apc> orSysFreq 4 enable 1. Subfeed 1 Breaker Position,1,disable,2,disable,3,disable,4,enable orICxxxxx Access: Administrator, Device Description: This category of alarm mapping commands associates an input contact alarm with the output relay/relays designated in the parameters.
Web Interface Introduction Supported Web browsers You can use Microsoft® Internet Explorer (IE) 7.x and higher (on Windows operating systems only) or Mozilla Firefox 3.0.6 or higher (on all operating systems) to access the PDU through its Web interface. Other commonly available browsers may work but have not been fully tested by APC. The PDU cannot work with a proxy server.
URL address formats Type the DNS name or IP address of the PDU in the URL address field of the Web browser 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...” Internet Explorer, Firefox Someone else is logged on. “This page cannot be displayed.
Home Page Overview On the Home tab, displayed when you log on to the Web interface, you can view active alarm conditions and the most recent events recorded in the event log. Quick status icons. At the upper right corner of every page, one or more icons indicate the current operating status of the PDU and the number of active alarms of that severity: Icon Description Critical: A critical alarm exists, which requires immediate action.
How to Use the Tabs, Menus, and Links Tabs In addition to the tab for the Home page, the following tabs are displayed. Click a tab to display a set of menu options: • Power Distribution: View the power output of the PDU and its breakers, and configure alarm thresholds. • Environment: Configure the name and normal state of the PDU’s input contacts and output relays. • Alarms: View active alarms and recent events, and configure how the relays will respond to PDU alarms.
Menus Left navigation menu. Each tab (except the tab for the home page) has a left navigation menu, consisting of headings and options: • If a heading has indented option names below it, the heading itself is not a navigational link. Click an option to display or configure parameters. • If a heading has no indented option names, the heading itself is the navigational link. Click the heading to display or configure parameters. Top menu bar.
The Power Distribution Tab Access detailed PDU status information Path: Power Distribution > Overview The first time you select the Power Distribution tab, the Overview page displays. If an alarm caused by an output power condition exists, a status icon and accompanying text display on the page. Path: Power Distribution > System Output > Measurements This page lists detailed information about power leaving the PDU: • Voltage: The phase-to-phase output voltage (e.g.
View and edit branch circuit breaker settings Path: Power Distribution > Panel # > even/odd Select a group of circuit breakers (Panel 1 [01..42] [even|odd], Panel 2 [01..42] [even|odd]) to view the following data: • Pos: The position of the breaker on the circuit breaker panel. • Rating: The rating of the breaker occupying this panel position, in amps. • Status: The state of the breaker. – Normal: The breaker is operating normally. – Warning: The low or high rating threshold has been violated.
The Environment Tab View and configure input contact settings Path: Environment > Input Contacts The first time you select the Environment tab the Input Contacts page displays. View the name of each input contact, its alarm status, and its current state. Up to four inputs can be connected to the PDU. Click the name of the input to configure a descriptive name (up to 14 characters), the location, and to define its normal state. An alarm will be generated when the input switches to the abnormal state.
Event and Data Logs Event log Path: Logs > Events You can view, filter, or delete the event log. By default, the log displays all events recorded during the last two days. 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. For information about configuring event actions, see “Configuring by event” on page 42.
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.
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.
Using 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.
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. You can use the del command to clear the contents of either log. ftp>del event.txt or ftp>del data.txt You will not be asked to confirm the deletion. • If you clear the data log, the event log records a deleted-log event. • If you clear the event log, a new event.txt file records the event. 5. Type quit at the ftp> prompt to exit from FTP.
APC supports the authentication and authorization functions of RADIUS (Remote Authentication Dial-In User Service). • When a user accesses the PDU that has RADIUS enabled, an authentication request is sent to the RADIUS server to determine the user’s permission level. • RADIUS user names used with the PDU are limited to 32 characters. Select one of the following: • Local Authentication Only: RADIUS is disabled. Local authentication is enabled.
Configure the RADIUS Server. You must configure your RADIUS server to work with the 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 APC Security Handbook. 1. Add the IP address of the PDU to the RADIUS server client list (file). 2. Users must be configured with Service-Type attributes unless Vendor Specific Attributes (VSAs) are defined.
Administration: Network Features Path: Administration > Network TCP/IP Settings Path: Administration > Network > TCP/IP The TCP/IP option on the side menu bar, selected by default when you choose Network on the top menu bar, displays the current IP address, subnet mask, default gateway, and MAC address of the PDU.
Setting Description Manual The IP address, subnet mask, and default gateway must be configured manually. Click Next>>, and enter the new values. BOOTP A BOOTP server provides the TCP/IP settings. At 32-second intervals, the PDU requests network assignment from any BOOTP server: • If it receives a valid response, it starts the network services. • If it finds a BOOTP server, but a request to that server fails or times out, the PDU stops requesting network settings until it is restarted.
DHCP response options Each valid DHCP response contains options that provide the TCP/IP settings that the PDU needs to operate on a network, and other information that affects the operation of the PDU. Vendor Specific Information (option 43). The PDU uses this option in a DHCP response to determine whether the DHCP response is valid. This option contains up to two APC-specific options in a TAG/LEN/DATA format: the APC Cookie and the Boot Mode Transition. • APC Cookie.
Other options. The 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 PDU can use. • Time Offset (option 2): The offset of the 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 PDU can use.
• Select naming to define the host name and domain name of the PDU: – Host Name: After you configure a host name here and a domain name in the Domain Name field, users can enter a host name in any field in the PDU interface (except e-mail addresses) that accepts a domain name. – Domain Name: You need to configure the domain name here only. In all other fields in the PDU interface (except e-mail addresses) that accept domain names, the PDU adds this domain name when only a host name is entered.
Web Path: Administration > Network > Web > options Option Description access To activate changes to any of these selections, log off from the PDU: • Disable: Disables access to the Web interface. (You must use the command line interface to reenable access. Select Network and Web/SSL/TLS. Then for HTTP, select Access and Enabled. For HTTPS access, also select Web/SSL and Enabled.
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 v1 and v2: Do not enable both versions 1 and 2 of SSH unless you require both. (They use extensive processing power.
SNMP SNMPv1. Path: Administration > Network > SNMPv1 > options 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.
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 PDU supports only MD5 authentication and DES encryption.
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 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.
Administration: Notification Path: Administration > Notification Event Actions Path: Administration > Notification > Event Actions > options 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 – Syslog notification • Indirect notification in the event log.
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 If the event persists for the specified time, notification is sent. If the condition clears before the time expires, no notification is sent.
E-mail notification Overview of setup. Use the Simple Mail Transfer Protocol (SMTP) to send e-mail to up to four recipients when an event occurs. To use the e-mail feature, you must define the following settings: • The IP addresses of the primary and, optionally, the secondary Domain Name System (DNS) servers. (See “DNS” on page 78.) • The IP address or DNS name for SMTP Server and From Address. (See “SNMP traps” on page 89.) • The e-mail addresses for a maximum of four recipients.
SMTP. Path: Administration > Notification > E-mail > server Setting Description Local SMTP Server The IP address or DNS name of the local SMTP server. Note: This definition is required only when SMTP Server is set to Local.
SNMP traps Trap Receivers. Path: Administration > Notification > SNMP Traps > trap receivers View trap receivers by NMS IP/Host Name. You can configure up to six trap receivers. • To open the page for configuring a new trap receiver, click Add Trap Receiver. • To modify or delete a trap receiver, first click its IP address or host name to access its settings.
Syslog Path: Logs > Syslog > options The PDU can send messages to up to four Syslog servers when an event occurs. The Syslog servers record events that occur at network devices in a log that provides a centralized record of events. This user’s guide does not describe Syslog or its configuration values in detail. See RFC3164 for more information about Syslog. Identifying Syslog Servers.
Syslog Test and Format example. Path: Logs > Syslog > test Send a test message to the Syslog servers configured through the servers option. 1. Select a severity to assign to the test message. 2. Define the test message, according to the required message fields – The priority (PRI): the Syslog priority assigned to the message’s event, and the facility code of messages sent by the PDU. – The Header: a time stamp and the IP address of the PDU.
Set the Date and Time Path: Administration > General > Date & Time > mode Set the time and date used by the PDU. You can change the current settings manually or through a Network Time Protocol (NTP) Server: • Manual Mode: Do one of the following: – Enter the date and time for the PDU. – Mark the check box Apply Local Computer Time to match the date and time settings of the computer you are using. • Synchronize with NTP Server: Have an NTP Server define the date and time for the PDU.
Use an .ini File Path: Administration > General > User Config File Use the settings from one PDU to configure another. Retrieve the config.ini file from the configured PDU, customize that file (e.g., to change the IP address), and upload the customized file to the new PDU. The file name can be up to 64 characters, and must have the.ini suffix. Status Reports the progress of the upload. The upload succeeds even if the file contains errors, but a system event r reports the errors in the event log.
To reconfigure any of the following, click the link name in the Display column: • Display: The short link name displayed on each interface page • Name: A name that fully identifies the target or purpose of the link • Address: Any URL—for example, the URL of another device or server About the PDU Path: Administration > General > About The hardware information is especially useful to APC Customer Support to troubleshoot problems with the PDU.
APC Device IP Configuration Wizard Capabilities, Requirements, and Installation How to use the Wizard to configure TCP/IP settings The APC Device IP Configuration Wizard configures the IP address, subnet mask, and default gateway of one or more PDUs. You can use the Wizard in either of the following ways: • Remotely over your TCP/IP network to discover and configure unconfigured PDUs on the same network segment as the computer running the Wizard.
Use the Wizard Note: Most software firewalls must be temporarily disabled for the Wizard to discover unconfigured PDUs. Launch the Wizard The installation creates a shortcut link in the Start menu to launch the Wizard. Configure the basic TCP/IP settings remotely Prepare to configure the settings. Before you run the Wizard: 1. Contact your network administrator to obtain valid TCP/IP settings. 2.
Configure or reconfigure the TCP/IP settings locally 1. Contact your network administrator to obtain valid TCP/IP settings. 2. Connect the serial configuration cable (which came with the PDU) from an available communications port on your computer to the serial port of the card or device. Make sure no other application is using the computer port. 3. From the Start menu, launch the Wizard application. 4. If the PDU is not configured, wait for the Wizard to detect it. Otherwise, click Next>. 5.
Export Configuration Settings Retrieve and Export the .ini File Summary of the procedure An Administrator can retrieve the .ini file of a PDU and export it to another PDU or to multiple PDUs. 1. Configure one PDU to have the settings you want to export. 2. Retrieve the .ini file from that PDU. 3. Customize the file to change at least the TCP/IP settings. 4. Use a file transfer protocol supported by the PDU to transfer a copy to one or more other PDUs.
Customizing. You must customize the file before you export it. 1. Use a text editor to customize the file. – Section headings, keywords, and pre-defined values are not case-sensitive, but string values that you define are case-sensitive. – Use adjacent quotation marks to indicate no value. For example, LinkURL1="" indicates that the URL is intentionally undefined. – Enclose in quotation marks any values that contain leading or trailing spaces or are already enclosed in quotation marks.
The Upload Event and Error Messages The event and its error messages The following event occurs when the receiving PDU completes using the .ini file to update its settings. Configuration file upload complete, with number valid values If a keyword, section name, or value is invalid, the upload by the receiving PDU succeeds, and additional event text states the error. Event text Description Configuration file warning: Invalid keyword on line number. A line with an invalid keyword or value is ignored.
File Transfers Upgrading Firmware Benefits of upgrading firmware When you upgrade the firmware on the PDU: • You obtain the latest bug fixes and performance improvements. • New features become available for immediate use. Keeping the firmware versions consistent across your network ensures that all PDUs support the same features in the same manner. Firmware files (PDU) A firmware version consists of two modules: An APC Operating System (AOS) module and an application module.
Firmware File Transfer Methods To upgrade the firmware of a PDU, use one of these methods: • From a networked computer running a Microsoft Windows operating system, use the firmware upgrade tool downloaded from the APC Web site. • From a networked computer on any supported operating system, use FTP or SCP to transfer the individual AOS and application firmware modules.
6. When FTP confirms the transfer, type quit to close the session. 7. After 20 seconds, repeat step 2 through step 6. In step 5, use the application module file name. SCP. To use Secure CoPy (SCP) to upgrade firmware for a PDU: 1. Identify and locate the firmware modules described in the preceding instructions for FTP. 2. Use an SCP command line to transfer the AOS firmware module to the PDU. The following example uses xxx to represent the version number of the AOS module: scp apc_hw03_aos_xxx.bin apc@158.
Use XMODEM to upgrade one PDU To upgrade the firmware for one PDU that is not on the network, you must extract the firmware files from the firmware upgrade tool (see “To extract the firmware files:” on page 101). To transfer the files: 1. Obtain the individual firmware modules (the AOS module and the application module) from www.apc.com/tools/download. 2. Select a serial port at the local computer and disable any service that uses the port. 3.
Verifying Upgrades and Updates Verify the success or failure of the transfer To verify whether a firmware upgrade succeeded, use the Network menu in the command line interface and select the FTP Server option to view Last Transfer Result, or use an SNMP GET to the mfiletransferStatusLastTransferResult OID. Last Transfer Result codes Code Description Successful The file transfer was successful. Result not available There are no recorded file transfers.
APC Worldwide Customer Support Customer support for this or any other APC product is available at no charge in any of the following ways: • Visit the APC Web site to access documents in the APC Knowledge Base and to submit customer support requests. – www.apc.com (Corporate Headquarters) Connect to localized APC Web sites for specific countries, each of which provides customer support information. – www.apc.com/support/ Global support searching APC Knowledge Base and using e-support.
