DHCP. You can use a RFC2131/RFC2132- compliant DHCP server to configure the TCP/IP settings for the PDU.
This section summarizes the PDU communication with a DHCP server. For more detail about how a DHCP
See also server is used to configure the network settings for the PDU, see “DHCP Configuration Settings” in the User’s Guide.
1.The PDU sends a DHCP request that uses the following to identify itself:
Vendor Class Identifier (APC by default)
Client Identifier (by default, the PDU’s MAC address)
User Class Identifier (by default, the identification of the PDU’s application firmware)
2.A properly configured DHCP server responds with a DHCP offer that includes all of the settings that the PDU needs for network communication. The DHCP offer also includes the Vendor Specific Information option (DHCP option 43). By default, the PDU ignores DHCP offers that do not encapsulate the APC cookie in the Vendor Specific Information option using the following hexidecimal format:
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 also
See your DHCP server documentation to add code to the Vendor Specific Information option.
You can use a local computer to disable the APC cookie requirement. To use a local computer, see “Local access to the control console” on page 12. To change the control console’s DHCP Cookie Is setting, an Advanced option in the TCP/IP menu, use Telnet or another remote accessing method. To access the control console, see “Remote access to the control console” on page 13.
Metered Rack Power Distribution Unit | 11 |