3.5 Configuring the Server Environment

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
The SNMP trap destination must be the admin server's 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
The SNMP trap destination must be the admin server's IP address.

Enable the following function referring the instructions given in the management board's manual.

SNMP agent

Mode Switch Settings for the Operator Panel (SPARC Enterprise M Series Servers)

When managing SPARC Enterprise M series servers using Resource Coordinator VE, set the mode switch of operator panel to "Locked" in the OpenBoot configuration to automatically start up the OS when powering on SPARC Enterprise M series servers.

Chassis Settings (SPARC Enterprise M4000/M5000/M8000/M9000 servers)

Refer to the remote management controller manual to apply the settings chosen in "3.1.5 Chassis Settings (SPARC Enterprise M4000/M5000/M8000/M9000 servers)" 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 remote management controller)
User name
Password
SNMP community
SNMP trap destination
The SNMP trap destination must be the admin server's IP address.

Refer to the instructions given in the XSCF manual and enable the following functions.

SNMP agent
SSH service
HTTPS service
Domain autoboot

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
The SNMP trap destination must be the admin server's IP address.

For SPARC Enterprise M3000 servers, refer to the XSCF manual and enable the following services.

SNMP agent
SSH service
HTTPS service
Domain autoboot

For SPARC Enterprise T series servers, refer to the ILOM manual and enable the following services.

SNMP agent
SSH configuration
HTTPS configuration
IPMI status

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.

System BIOS

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)

Internal SCSI BIOS: These are the BIOS settings for the internal SCSI disk(s) of a managed server.
Enable or disable booting from internal disks as appropriate.

FC-HBA BIOS: 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
System BIOS
Set the boot order as follows.
1. Boot from the first admin LAN network interface (NIC1 (Index1))
2. Boot from the network interface used by the admin LAN (NIC2 (Index2))
3. Boot from CD-ROM (when a CD-ROM drive is connected)
4. 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.
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 "6.1.3 Registering Managed Servers".
Internal SCSI BIOS
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.
FC-HBA BIOS
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
System BIOS
Enable the FC-HBA BIOS.
Set the boot order as follows.
1. Boot from the first admin LAN network interface (NIC1 (Index1))
2. Boot from the network interface used by the admin LAN (NIC2 (Index2))
3. Boot from CD-ROM (when a CD-ROM drive is connected)
4. 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.
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 "6.1.3 Registering Managed Servers".
Internal SCSI BIOS
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.
FC-HBA BIOS
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 page.
URL: http://www.fujitsu.com/global/services/computing/server/ia/ (As of August 2011)
When using VIOM (SAN boot)
System BIOS
Enable the FC-HBA BIOS.
Set the boot order as follows.
1. Boot from the first admin LAN network interface (NIC1 (Index1))
2. Boot from the network interface used by the admin LAN (NIC2 (Index2))
3. Boot from CD-ROM (when a CD-ROM drive is connected)
4. 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 "6.1.3 Registering Managed Servers".
Internal SCSI BIOS
Apply the same settings as those described in the above "When using HBA address rename for SAN boot" section.
FC-HBA BIOS
Apply the same settings as those described in the above "When using HBA address rename for SAN boot" section.
When using VIOM (iSCSI boot)
System BIOS
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.
1. Boot from the first admin LAN network interface (NIC1 (Index1))
2. Boot from the network interface used by the admin LAN (NIC2 (Index2))
3. Boot from the network interface used for the iSCSI LAN (NIC3 (Index3))
4. 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.
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 "6.1.3 Registering Managed Servers".
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.
Internal SCSI BIOS
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.
FC-HBA BIOS
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.

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 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.

OBP (Open Boot Prom) Settings (SPARC Enterprise)

When managing SPARC Enterprise servers from Resource Coordinator VE, set the "autoboot?" option to "true" in the OBP configuration. Otherwise, the operating system will not automatically start up when powering on SPARC Enterprise servers.

SAN boot settings
Configure the following settings on OBP for automatic boot from SAN storage devices.
- auto-boot?
  Set to "true".
- boot-device
  Set with a boot disk identifier at the beginning.
Configure the following settings on OBP for HBAs connected to the boot disk.
- HBA boot
  Enable the function.
- Topology
  Set to NPORT connection.
- Target devices
  Configure based on values set in "3.3.4 Settings for ETERNUS SF Storage Cruiser Integration".

For details, refer to "SPARC Enterprise - ETERNUS SAN Boot Environment Build Guide" of the Fibre Channel card driver manual.

Settings for ServerView Operations Manager (VMware ESXi)

When managing VMware ESXi using Resource Coordinator VE, register the target VMware ESXi with ServerView Operations Manager.

For details, refer to the ServerView Operations Manager manual.