Configuration Guidelines For Use Of Auto-Init And Manual Mode - Alcatel-Lucent 7210 SAS M Configuration Manual

Configuration Guidelines for use of Auto-init and Manual mode

•
•
•
•
•
•
7210 SAS M, T, X, R6 Basic System Configuration Guide
Ethernet management port does not support Auto-Init mode. The use of DHCP to obtain
the BOF file from the network and other system parameters is currently not supported on
Ethernet management port.
In auto-init mode, DHCP requests sent out by the node are in two formats. The system
attempts to communicate with the DHCP server in these two formats, one after another(if
necessary).
−
Initially, the DHCP requests are sent out 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 above request period,
DHCP requests are sent without VLAN tags (that is, null-tagged packets).
In auto-init mode, DHCP client expects the following options to contain the BOF file
name and the server IP address. BOF file can be downloaded through FTP or TFTP based
on the information a client receives from DHCP server. Listed below are the ways in
which DHCP client will try to obtain the file:
−
1. Using the vendor specific option : The client searches for the option "43" in
the DHCP reply. This provides the URL which has 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.
−
2. Collating server-name and file-name : If the option "43" is not found in the
DHCP reply, then a URL has to be formed by using the tftp-server name and the
boot-file retrieved via TFTP. IP address of TFTP server is obtained from DHCP
Option "66" or the "sname" field of a DHCP message and filename on the TFTP
server is obtained from DHCP Option "67" or the "file" field of a DHCP message.
In the manual mode, if the OOB port is enabled (that is the "eth-mgmtdisable" is set to
"no"), the OOB port is used to download the TIMOS image file and configuration file
specified in the BOF file, and the system boot is successfully completed. If a system boot
fails, the uplink A and uplink B parameters are used to retrieve the TIMOS image and
configuration files.
For 7210 SAS-M 24F 2XFP (10GigE) (both standard and ETR variants) and 7210 SAS-X
devices, the DHCP requests are sent out of port 1/1/25 and 1/1/26 as part of auto-init. The
system attempts to obtain the system parameters and the BOF file location by sending out
DHCP requests on the following ports in the order that appears as 1/1/1, 1/1/2, 1/1/25 and
1/1/26. It sends out the DHCP request on a single port at a given time and waits for the
DHCP server to respond. If a successful server response is received, the auto-init process
uses the information to bootup the system. If no responses are received from the server
within a stipulated time, it sends out DHCP requests on the next port in the order above,
looping through all the ports until a successful response is received from the server or the
user interrupts the boot process.
For 7210 SAS-M 24F 2XFP 10G MDA cannot be used for auto-init. The use of DHCP to
obtain the BOF file is not supported with the 10G MDA.
Boot Option Files
Page 131