7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
Boot options
– ports 1/1/49, 1/1/50 (10GE ports) on the 48-port 7210 SAS-Sx 1/10GE, 7210 SAS-S 1/10GE
variants
– ports 1/1/65, 1/1/66 (100GE ports), and ports 1/1/1, 1/1/2 (which are 10GE ports) on the 7210 SAS-
Sx 10/100GE 64SFP+ 4CFP4 variant
– ports 1/1/c1/1 and 1/1/c2/1, and 10 GE ports 1/1/1 and 1/1/2 on the 7210 SAS-Sx 10/100GE 64SFP
+ 4QSFP28 variant
The boot loader continuously iterates over the previously mentioned ports, sending out DHCP requests
until the boot loader receives a response from the host.
• When the chassis-role parameter for the node is set to standalone, DHCP requests are sent out of the
following ports:
– ports 1/1/27, 1/1/28 (10GE ports) and ports 1/1/1, 1/1/2 (1GE ports) on the 24-port 7210 SAS-Sx
1/10GE, 7210 SAS-S 1/10GE, and 7210 SAS-Mxp variants
– ports 1/1/51, 1/1/52 (10GE ports) and ports 1/1/1, 1/1/2 (1GE ports) on the 48-port 7210 SAS-Sx/S
1/10GE, and 7210 SAS-S 1/10GE variants
– ports 1/1/67, 1/1/68 (100GE ports) and ports 1/1/1, 1/1/2 (10GE ports) on the 7210 SAS-Sx
10/100GE 64SFP+ 4CFP4 variant
– ports 1/1/c3/1 and 1/1/c4/1, and 10 GE ports 1/1/1 and 1/1/2 on the 7210 SAS-Sx 10/100GE 64SFP
+ 4QSFP28 variant
In addition, the boot loader will attempt to load the TiMOS image (both.tim) from the local flash if
auto-init fails (that is, no responses were received from the DHCP server).
• When the node is shipped from the factory (with the chassis-role set to factory-default) and powered
up for the first time, the node sends out DHCP requests on the following ports:
– 10GE ports 1/1/25, 1/1/26, 1/1/27, and 1/1/28 on the 24-port 7210 SAS-Sx 1/10GE, 7210 SAS-S
1/10GE, and 7210 SAS-Mxp
– 10GE ports 1/1/49, 1/1/50, 1/1/51 and 1/1/52 on the 48-port 7210 SAS-Sx 1/10GE and 7210 SAS-S
1/10GE
– the first two 1GE ports, 1/1/1 and 1/1/2, on all 7210 SAS-Sx/S 1/10GE and 7210 SAS-Mxp variants
On a 7210 SAS-Sx 10/100GE CFP4 platform shipped from the factory, the DHCP requests are sent out
of the first two 10GE ports (1/1/1 and 1/1/2) and all 100GE ports (1/1/65, 1/1/66, 1/1/67, and 1/1/68).
On a 7210 SAS-Sx 10/100GE 64SFP+ 4QSFP28 variant, the DHCP requests are sent out of ports 1/1/
c1/1, 1/1/c2/1, 1/1/c3/1, and 1/1/c4/1, and the first two 10 GE ports (1/1/1 and 1/1/2). To change this,
connect to the console and modify the chassis-role parameter value to either satellite or standalone,
as required. After the chassis-role parameter is updated, the node attempts autoinit to retrieve the
BOF.
4.3 Persistence
Optionally, the BOF persist parameter can specify whether the system should preserve system indexes
when a save command is executed. During a subsequent boot, the index file is read along with the
configuration file. As a result, a number of system indexes are preserved between reboots, including
the interface index. If persistence is not required and the configuration file is successfully processed,
the system becomes operational. If persistence is required, a matching x.ndx file must be located and
successfully processed before the system can become operational. Matching files (configuration and index
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
145
SPACER TEXT
To Next Page
Loading...