5Metered Rack PDU User’s Guide
DHCP. You can use an RFC2131/RFC2132-compliant DHCP server to configure the TCP/IP settings for
the Rack PDU.
This section summarizes the Rack PDU’s communication with a DHCP server. For more
detail about how a DHCP server can configure the network settings for a Rack PDU, see
“DHCP response options” on page 63.
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)
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 (
01) is the code.
– The second byte (
04) is the length.
– The remaining bytes (
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 Address
check box in the Web interface, you can require the DHCP server to provide an
“APC” cookie, which supplies information to the Rack PDU: Administration >
Network>TCP/IP>ipv4 settings.
To Next Page
Loading...