7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
Boot options
files) must have the same filename prefix such as test123.cfg and test123.ndx, and are created at
the same time when a save command is executed. The persistence option must be enabled to deploy the
Network Management System (NMS). The default is off.
Traps, logs, and console messages are generated if problems occur and SNMP shuts down for all SNMP
gets and sets; however, traps are issued.
4.4 Configuration guidelines for auto-init and manual mode
This section describes the configuration guidelines for the auto-init and manual modes:
• The Ethernet management port does not support auto-init mode. The use of DHCP to obtain the BOF
from the network and other system parameters is currently not supported on Ethernet management
ports.
• 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 after the DHCP request is sent, 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, 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.
– 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
boot-file 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.
• In manual mode, if the OOB port is enabled (that is, if no eth-mgmt-disable is configured), the OOB
port is used to download the TIMOS image file and configuration file specified in the BOF, and the
system boot is successfully completed. If a system boot fails, the uplinkA and uplinkB parameters are
used to retrieve the TIMOS image and configuration files.
• On a factory-shipped 7210 SAS-T device, the system attempts the auto-init process (that is, sends
DHCP requests) using the first two 1GE ports (1/1/1 and 1/1/2 on 7210 SAS-T) and the last two 10GE
ports (1/1/25 and 1/1/26 on 7210 SAS-T). See System boot options for 7210 SAS-Mxp, 7210 SAS-
Sx 1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Sx 10/100GE in satellite mode and System boot
options for 7210 SAS-Mxp, 7210 SAS-S 1/10GE, 7210 SAS-Sx 1/10GE, and 7210 SAS-Sx 10/100GE in
standalone mode for information about ports used for bootup on these platforms.
• The system sends out the DHCP request on a single port at a time and waits for the DHCP server to
respond. If a successful server response is received, the auto-init process uses the information to boot
up the system. If no response is received from the server within a stipulated time, the system sends out
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
146
SPACER TEXT
To Next Page
Loading...