This section describes how to configure servers and chassis for Resource Coordinator VE.
Chassis Settings (for Blade Servers)
Refer to the management blade manual to apply the settings chosen in "3.1.1 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
SNMP trap destination
Set the admin server IP address.
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 Agent installed.
Chassis Settings (PRIMERGY Partition Models)
Refer to the management board manual to apply the settings chosen in "3.1.4 Chassis Settings (Settings for PRIMERGY Partition Models)" 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
SNMP trap destination
Set the admin server IP address.
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 community (for SPARC Enterprise servers)
SNMP trap destination
Set the admin server IP address.
For SPARC Enterprise servers, refer to the XSCF manual to enable the following services.
SNMP agent
SSH Service
HTTPS Service
Note
When assigning multiple IP addresses to multiple network interfaces on a XSCF module, make sure that the IP address used by Resource Coordinator VE is assigned to the first of those network interfaces.
BIOS Settings for 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.
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
Note
Do not change the boot order once a primary 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.
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 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
Note
Do not change the boot order once a primary server has commenced operation. Even when booting from disk, there is no need to change the boot order.
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 the BIOS settings required for each HBA.
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 page.
URL: http://www.fujitsu.com/global/services/computing/server/ia/ (As of February 2010) |
When using VIOM (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
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 which 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 primary server has commenced operation. Even when booting from disk, there is no need to change the boot order.
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 (Local boot)
Apply the same settings as those described in the above "When using the backup/restore or cloning function" section.
Managed Server OS Settings (for Rack Mount or Tower Servers)
When using the auto-recovery function, configure the OS to respond to ping commands.
Settings for Server Virtualization Software
Server virtualization software must be configured appropriately for Resource Coordinator VE.
Refer to "A.2 Configuration Requirements" for details on the required server virtualization software settings.
OpenBoot Settings for SPARC Enterprise Servers
When managing SPARC Enterprise servers from Resource Coordinator VE, set the "autoboot?" option to "true" in the OpenBoot configuration. Otherwise, the operating system won't automatically start up when powering on SPARC Enterprise servers.
