User`s guide

Metered Rack PDU for High Density
8
If a BOOTP server is unavailable, see
“APC Device IP Configuration Wizard”
on page 6, “Local access to the control
console” on page 9, or “Remote access to
the control console” on page 10 to
configure TCP/IP settings.
1. Enter the Rack PDUs MAC and IP addresses,
the subnet mask and default gateway settings,
and an optional bootup file name in the
BOOTPTAB file of the BOOTP server.
For the MAC address, look on the
back of the Rack PDU or on the
Quality Assurance slip included in
the package.
2. 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, the
Rack PDU can be configured remotely by
using Telnet or by using the Web interface:
user name and password are both apc, by
default.
To create a bootup file, see your
BOOTP server documentation.
DHCP. You can use a RFC2131/RFC2132-
compliant DHCP server to configure the
TCP/IP settings for the Rack PDU.
This section summarizes the Rack PDU
communication with a DHCP server. For
more detail about how a DHCP server is
used to configure the network settings for
the Rack PDU, see “DHCP
Configuration Settings” in the User’s
Guide.
1 . The Rack PDU sends a DHCP request that
uses the following to identify itself:
–Vendor Class Identifier (APC by default).
–Client Identifier (by default, the Rack PDUs
MAC address).
–User Class Identifier (by default, the
identification of the Rack PDU’s application
firmware).
2. A properly configured DHCP server responds
with a DHCP offer that includes all of the
settings that the Rack PDU needs for network
communication. The DHCP offer also
includes the Vendor Specific Information