The following configuration guidelines apply for the auto-init and manual modes:
The use of DHCP to obtain the BOF from the network and other system parameters is currently not supported on Ethernet management ports. Consequently, the Ethernet management port does not support auto-init mode.
In auto-init mode, DHCP requests sent out by the node are in two formats. The system attempts communication with the DHCP server in these two formats, one after another (if necessary), in the following order:
Initially, DHCP requests are sent out to the DHCP server with a priority VLAN tag (VLAN ID = 0, dot1p PCP bits set to 7).
If no response is received from the DHCP server during the preceding request period, DHCP requests are sent without VLAN tags (that is, null-tagged packets).
In auto-init mode, the BOF can be downloaded through FTP or TFTP based on the information a client receives from the DHCP server. The DHCP client tries the following options to obtain the BOF name and the server IP address:
using the vendor-specific option
The client searches for option 43 in the DHCP reply. This provides the URL to be accessed through FTP. For example, ftp://abcd:xyz@10.0.0.2/test/bof.cfg. If this file is found, the client retrieves this file.
collating server-name and file-name
If option 43 is not found in the DHCP reply, a URL is formed by using the TFTP server name and the BOF retrieved via TFTP. The IP address of the TFTP server is obtained from DHCP option 66 or the ‟sname” field of a DHCP message, and the filename on the TFTP server is obtained from DHCP option 67 or the ‟file” field of a DHCP message.
The 7210 SAS-D, 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T try ports 1/1/1 and 1/1/2 to boot in the auto-init mode.
The 7210 SAS-Dxp tries ports in the following order to boot in the auto-init mode:
1/1/11 and 1/1/12 (10GE fiber ports)
1/1/7 and 1/1/8 (1GE fiber ports)
The 7210 SAS-K 3SFP+ 8C tries ports in the following order to boot in the auto-init mode:
1/1/1 and 1/1/2 (10GE fiber ports)
1/1/10 and 1/1/11 (1GE fiber ports)