7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
Boot options
– boot the system by retrieving the BOF from the network, using DHCP to retrieve the network location
of the BOF (auto-init mode); auto-init mode is the default boot procedure if there is no manual
intervention during the first boot of the node
See the appropriate chassis installation guide for more information about using the available system
boot options for the specific 7210 SAS platform.
Note:
• If the operator executes the reset command in the boot loader prompt or the admin>reboot
auto-init command in the TiMOS CLI, 7210 SAS resets the current BOF, reboots, and initiates
auto-init mode after the reboot.
• The operator can manage a 7210 SAS node through an external physical network. Managing
a node through an external physical network secures the management network by restricting
access to service customers and service data.
4.1.2.1 Auto-init mode
Note:
Auto-init is supported on all 7210 SAS platforms as described in this document, except the
7210 SAS-R6, 7210 SAS-R12, and platforms operating in standalone-VC mode.
During the first boot or a reboot after the execution of the admin>reboot auto-init command, if the user
does not intervene to create the BOF in the manual mode, the system, by default, runs the auto-init
procedure after a wait time. The default wait time is 3 seconds. Two designated ports are used for auto-init:
front panel port 1 and 2. Auto-init requires a DHCP server to be configured in the network and reachable
by the system. DHCP requests are directed out of one uplink port at a time because all other ports in the
system are down.
Note:
Some systems use other ports in addition to front panel port 1 and 2. See Configuration notes for
7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp for
information about specific ports used to send DHCP request for 7210 SAS platforms.
If a DHCP server is present in the network, the system expects to receive an IP address, default gateway
information, and a BOF location in the response returned by the DHCP server. Upon receiving these
parameters from the DHCP server, the system applies the IP configuration and downloads the BOF from
the location specified by the DHCP server. The BOF is saved in the flash drive and used for subsequent
reboots. The bootstrap image processes the BOF parameters to boot the system. See Configuration file
and TiMOS image loading for information about the BOF processing.
Before the node attempts to use DHCP to obtain the BOF and image files, you can configure the following
link parameters in the BOF to suit your deployment needs:
• the uplink ports to use
• VLAN ID used
• link speed
• duplex setting for the link
• auto-negotiation capability for the link
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
123
SPACER TEXT
To Next Page
Loading...