Filter
Top Products
InRow RC Operation and Maintenance Manual32
BOOTP & DHCP configuration
The default TCP/IP configuration setting, BOOTP & DHCP, assumes that a properly configured BOOTP or
DHCP server is available to provide TCP/IP settings to Network Management Cards. The Network
Management Card first attempts to discover a properly configured BOOTP server, and then a DHCP server. It
repeats this pattern until it discovers a BOOTP or DHCP server.
If neither of these servers is available, see “Local access to the control console” on page 33, or
“Remote access to the control console” on page 33 to configure the needed TCP/IP settings.
A user configuration (.ini) file can function as a BOOTP or DHCP boot file. For more information, see
the TCP/IP configuration section of the User Guide, available from the Utility CD or the Schneider
Electric Web site, www.schneider-electric.com.
BOOTP: For the Network Management Card to use a BOOTP server to configure its TCP/IP settings, it must
find a properly configured RFC951-compliant BOOTP server.
1. In the BOOTPTAB file of the BOOTP server, enter the MAC address of the Network Management Card,
and the IP addresses of the subnet mask, and default gateway, and an optional bootup file name. Look
for the MAC address on the display interface (Path: Main > Configure Network) or on the label on the
back of the Network Management Card.
2. When the Network Management Card reboots, the BOOTP server provides it with the TCP/IP settings.
– If you specified a bootup file name, the Network Management Card attempts to transfer that file from
the BOOTP server using TFTP or FTP. The Network Management Card 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 Network
Management Card remotely through its Web interface or control console; user name and password
are both Schneider Electric, by default.
See your BOOTP server documentation to create a bootup file.
DHCP: You can use a RFC2131/RFC2132-compliant DHCP server to configure the TCP/IP settings for the
Network Management Card.
This section summarizes communication between the Network Management Card and a DHCP
server. For more details about how a DHCP server can configure the network settings for a Network
Management Card, see “DHCP Configuration” in the User Guide.
1. A Network Management Card 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 value of the Network Management Card)
– A User Class Identifier (by default, the identification of the application firmware of the Network
Management Card)
2. A properly configured DHCP server responds with a DHCP offer that includes all of the settings that the
Network Management Card needs for network communication. The DHCP offer also includes the
Vendor Specific Information option (DHCP option 43). By default, the Network Management Card will
ignore DHCP offers that do not encapsulate the Schneider Electric cookie in the Vendor Specific
Information option using the following hexadecimal format: