BIOS settings of managed servers must be set if neither VIOM or ISM is used.
If VIOM or ISM is used, boot order settings must be configured in the VIOM or ISM profile. For details, refer to "7.1.1 Registering Profiles" in the "User's Guide VE".
The following BIOS configurations must be modified.
This is the system BIOS for a managed server.
Enable or disable the internal SCSI BIOS and FC-HBA BIOS as appropriate, and set up the appropriate boot order.
Note
The BIOS settings of server blades include an option to automatically start up servers when their enclosing chassis is powered on. For details, refer to the server blade manual.
For PRIMERGY BX900/BX400, when a PG-LND203 is mounted as the LAN expansion card of the server blade, do not set the NIC of the LAN expansion card as [disable] in the server blade's BIOS settings.
The connections between server blades and LAN switch blades are not shown correctly, when [disable] is set.
The following functions do not operate correctly.
Changing and setting the VLAN for LAN switch blades (internal and external ports)
Server switchover (changing network settings while a server is switched over)
For PRIMERGY BX900/BX400 series, if "UEFI" and "Legacy" are displayed when configuring boot settings from the network interface, select [Legacy].
Set PXE VLAN Support to [Disabled] when the server switchover method is HBA address rename.
These are the BIOS settings for the internal SCSI disk(s) of a managed server.
Enable or disable booting from internal disks as appropriate.
This is a BIOS setting that relates to FC-HBAs that have been installed as an expansion card in the blade server.
Enable or disable SAN boot as well as the connection of a SAN storage environment by means of a Fibre Channel switch.
Configure the following settings depending on the operating environment.
When Using the Backup/Restore or Cloning Function
Set the boot order as follows.
Boot from the first admin LAN network interface (NIC1 (Index1))
Boot from the network interface used by the admin LAN (NIC2 (Index2))
Boot from CD-ROM (when a CD-ROM drive is connected)
Boot from the disk
For servers with a system BIOS providing [Keep Void Boot Options] in their Boot menu, set [Enabled] for [Keep Void Boot Options].
Furthermore, when using a managed server as a spare server, after storage connected due to server switchover is recognized by BIOS, perform BIOS settings.
Otherwise, the boot order may be changed.
Note
Do not change the boot order once a managed server has commenced operation. Even when booting from disk, there is no need to change the boot order.
Step 2 is only required for a redundant admin LAN configuration.
NICs other than NIC1 and NIC2 can also be used for the admin LAN. In this case, switch the order of step 1 and step 2. When using NICs other than NIC1 and NIC2 for the admin LAN, specify the same NIC configured in this procedure when registering the server.
For details, refer to "7.3 When Using Blade Servers" and "7.4 When Using Rack Mount and Tower Servers" in the "User's Guide VE"
The servers to which a cloning image is deployed should have the same internal SCSI BIOS settings as those of the server from which the image was collected. Similarly, when using server switchover, primary servers and their spare servers should have the same internal SCSI BIOS settings.
When using HBA address rename and SAN storage only for data storing purposes, disable boot from the SAN. Refer to the manual of each FC-HBA for details on FC-HBA BIOS settings.
This setting is only required if a SAN storage system is used.
When using HBA address rename for SAN boot
Enable the FC-HBA BIOS.
Set the boot order as follows:
Boot from the first admin LAN network interface (NIC1 (Index1))
Boot from the network interface used by the admin LAN (NIC2 (Index2))
Boot from CD-ROM (when a CD-ROM drive is connected)
Boot from a storage device
For servers with a system BIOS providing [Keep Void Boot Options] in their Boot menu, set [Enabled] for [Keep Void Boot Options].
Furthermore, when using a managed server as a spare server, after storage connected due to server switchover is recognized by BIOS, perform BIOS settings.
Otherwise, the boot order may be changed.
Note
Do not change the boot order once a managed server has commenced operation. Even when booting from disk, there is no need to change the boot order.
NICs other than NIC1 and NIC2 can also be used for the admin LAN. In this case, switch the order of step 1 and step 2. When using NICs other than NIC1 and NIC2 for the admin LAN, specify the same NIC configured in this procedure when registering the server.
For details, refer to "7.3.2 Registering Blade Servers" or "7.4.1 Registering Rack Mount or Tower Servers" in the "User's Guide VE".
If "UEFI" and "Legacy" are displayed when configuring boot settings from the network interface, select "Legacy".
If the managed server does not have an internal SCSI disk, disable the option to boot from an internal SCSI disk. However, in some cases (depending on a combination of factors such as server model, HBA model, and firmware), this option should either be enabled or disabled. Refer to the FC-HBA manual for instructions on whether or not to enable or disable boot from internal SCSI disk.
Enable booting from SAN storage devices.
Refer to the manual of each FC-HBA for details on FC-HBA BIOS settings.
Note
Restart the server saving BIOS configuration changes.
HBA address rename may not work properly with older BIOS firmware versions.
Please obtain and update the latest BIOS firmware from the following web site.
URL: http://www.fujitsu.com/global/services/computing/server/ia/ |
When Using VIOM or ISM (SAN Boot)
Enable the FC-HBA BIOS.
Set the boot order as follows:
Boot from the first admin LAN network interface (NIC1 (Index1))
Boot from the network interface used by the admin LAN (NIC2 (Index2))
Boot from CD-ROM (when a CD-ROM drive is connected)
Boot from a storage device
Note
NICs other than NIC1 and NIC2 can also be used for the admin LAN. In this case, switch the order of step 1 and step 2. When using NICs other than NIC1 and NIC2 for the admin LAN, specify the same NIC configured in this procedure when registering the server.
For details, refer to "7.3.2 Registering Blade Servers" or "7.4.1 Registering Rack Mount or Tower Servers" in the "User's Guide VE".
Apply the same settings as those described in the above "When using HBA address rename for SAN boot" section.
Apply the same settings as those described in the above "When using HBA address rename for SAN boot" section.
When Using VIOM (iSCSI Boot)
Enable iSCSI boot for the NIC that is used for the iSCSI LAN.
Use the VIOM server profile for the iSCSI boot parameter settings.
For details on server profile setup, refer to the ServerView Virtual-IO Manager manual.
Set the boot order as follows:
Boot from the first admin LAN network interface (NIC1 (Index1))
Boot from the network interface used by the admin LAN (NIC2 (Index2))
Boot from the network interface used for the iSCSI LAN (NIC3(Index3))
Boot from the network interface used for the iSCSI LAN (NIC4(Index4))
Note
Do not change the boot order once a managed server has commenced operation. Even when booting from disk, there is no need to change the boot order.
NICs other than NIC1 and NIC2 can also be used for the admin LAN. In this case, switch the order of step 1 and step 2. When using NICs other than NIC1 and NIC2 for the admin LAN, specify the same NIC configured in this procedure when registering the server.
For details, refer to "7.3.2 Registering Blade Servers" or "7.4.1 Registering Rack Mount or Tower Servers" in the "User's Guide VE".
When using NIC3 or NIC4 for the admin LAN, use NICs other than NIC3 and NIC4 for the iSCSI LAN. In this case, switch the order of step 3 and step 4.
If the managed server does not have an internal SCSI disk, disable the option to boot from an internal SCSI disk. However, in some cases (depending on a combination of factors such as server, model, and firmware), this option should either be enabled or disabled. Refer to the hardware manual for instructions on whether or not to enable or disable boot from internal SCSI disk.
Disable the function.
When Using VIOM or ISM (Local Boot)
Apply the same settings as those described in the above "When using the backup/restore or cloning function" section.
