This section describes how to configure servers and chassis for Resource Orchestrator.
Chassis Settings (for Blade Servers)
Refer to the management blade manual to apply the settings chosen in "4.1.1.2 Chassis Settings (for Blade Server Environments)" to the management blade.
Note that the SNMP community must be set to Write (read and write) access.
Admin IP address (IP address of the management blade)
SNMP community name
SNMP trap destination
This must be the IP address of the admin server.
Refer to the management blade manual to set the following SNMP agent settings.
Set Agent SNMP Enable
Set to "enable".
Set Agent SNMP Security Enable
Set to "disable".
Note
When powering off a chassis together with its enclosed server blades, servers are shut down using the graceful shutdown option of the management blade. To enable this feature, all servers within the chassis should have a ServerView Agents installed.
Chassis Settings (for PRIMEQUEST)
Refer to the management board manual to apply the settings chosen in "4.1.1.4 Chassis Setting Values (For PRIMEQUEST)" to the management board.
Note that the SNMP community must be set to Write (read and write) access.
Admin IP address (Virtual IP address of the management board)
User name
Password
SNMP community name
SNMP trap destination
This must be the IP address of the admin server.
Enable the following function referring the instructions given in the management board's manual.
SNMP Agent
Remote Management Controller Settings (for Non-Blade Servers)
Refer to the remote management controller manual to configure the following on the IPMI controller.
IP address
User name
Password
SNMP trap destination
This must be the IP address of the admin server.
BIOS Settings of Managed Servers
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 an LND-PG203 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)
If "UEFI" and "Legacy" are displayed when configuring boot settings from the network interface, select "Legacy".
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 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
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 "2.4.2 Registering Blade Servers" and "2.5.1 Registering Rack Mount or Tower Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If "UEFI" and "Legacy" are displayed when configuring boot settings from the network interface, select "Legacy".
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/ (As of February 2012) |
OS Settings for Managed Servers
When using the following functions, configure the OS to respond to ping commands.
Auto-Recovery (for rack mount or tower servers)
Configuration of monitoring information (ping monitoring)
Settings for ServerView Operations Manager (VMware ESXi)
When managing VMware ESXi using Resource Orchestrator, register the target VMware ESXi with ServerView Operations Manager.
For details, refer to the ServerView Operations Manager manual.