9
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.
In the BOOTPTAB file of the BOOTP server, enter the Network Management Card’s MAC address, IP address, subnet mask, and
default gateway, and, optionally, a bootup file name. Look for the MAC address on the bottom of the Network Management Card or
on the Quality Assurance slip included in the package.
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 command line interface; the user name and password are both apc, by default.
To create a bootup file, see your BOOTP server documentation.
DHCP.
You can use an RFC2131/RFC2132-compliant DHCP server to configure the TCP/IP settings for the Network Management
Card.
This section summarizes the Network Management Card’s communication with a DHCP server. For more detail about how a DHCP
server can configure the network settings for a Network Management Card, see “DHCP Configuration” in the Network Management
Card
User’s Guide
on the
Utility
CD.
1.
The 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 of the Network Management Card)
•
A User Class Identifier (by default, the identification of the application firmware installed on the Network Management
Card)
2.
A properly configured DHCP server responds with a DHCP offer that includes all 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 ignores DHCP offers that do not encapsulate the APC cookie
in DHCP option 43 using the following hexadecimal 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 your DHCP server documentation to add code to the Vendor Specific Information option.
Note:
To disable the requirement that a DHCP offer include the APC cookie, clear the check box
Require vendor specific cookie to
accept DHCP Address
in the Web interface:
Administration > Network>TCP/IP>DHCP.
Alternately, at the command line interface, use this command to disable the DHCP cookie requirement:
boot -c disable
Local access to the command line interface
You can use a computer connected to the serial port on the front of the Network Management Card to access the command line
interface.
1.
Select a serial port at the local computer, and disable any service that uses that port.
2.
Use the provided serial cable (IBM part number 46M5366) to connect the selected port to the serial port on the front panel of
the Network Management Card.
3.
Run a terminal program (such as HyperTerminal) and configure the selected port for 9600 bps, 8 data bits, no parity, 1 stop
bit, and no flow control. Save the changes.
4.
Press
Enter
, repeatedly if necessary, to display the
User Name
prompt.
5.
Use
apc
for the user name and password.
See “Command line interface” on page 10 to finish the configuration.
