This section explains how to define setting values for server environments.
This section explains the preparations for setup of server environments.
Define the Server Environment
Define the following values for the server environment in advance.
Chassis setting values (settings for blade servers and PRIMEQUEST)
Settings for rack mount servers and tower servers
For details on how to define server environments, refer to "4.1.1 Defining the Server Environment".
For the servers not using server management software, refer to "For rack mount or tower servers" in "4.1.1.3 Settings for Rack Mount or Tower Servers".
For servers other than HP servers, a Baseboard Management Controller (hereinafter BMC) is used for server management.
Configure the Server Environment
Configure the following values for the server environment in advance.
Chassis settings (settings for blade servers and PRIMEQUEST)
iRMC settings (remote management controller)
BIOS settings of managed servers
For details on how to configure server environments, refer to "4.1.2 Configuring the Server Environment".
For configuration of a server environment not using server management software, refer to "Remote Management Controller Settings (for Non-Blade Servers)" of "4.1.2 Configuring the Server Environment".
For the servers other than HP servers, replace the remote management controller with a BMC.
Configuration when Creating a Physical L-Server
When creating a physical L-Server, it is necessary to configure VIOM or HBA address rename settings as well as defining and configuring the server environment.
Usage methods of HBA address rename and VIOM differ depending on the hardware of the managed servers used to create a physical L-Server.
Blade Servers
Use VIOM.
Rack Mount Servers
Use HBA address rename.
Note
When using iSCSI boot, VIOM is required in the server environment.
For details, refer to "Appendix D Design and Configuration when Creating a Physical L-Server".
Choose values for the following management blade settings, given the following criteria:
This name is used to identify the chassis on the admin server. Each chassis name must be unique within the system.
The first character must be alphabetic, and the name can contain up to 10 alphanumeric characters and hyphens ("-").
These IP addresses can be used to communicate with the admin server.
This community name can contain up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
This must be the IP address of the admin server.
Note
To enable server switchover and cloning between servers in different chassis, use the same SNMP community for each chassis.
Resource Orchestrator supports the following types of remote management controllers to manage servers.
For PRIMERGY Servers
iRMC2
For HP Servers
iLO2 (integrated Lights-Out)
For DELL or IBM Servers
BMC (Baseboard Management Controller)
Choose values for the following remote management controller settings according to the criteria listed below.
These IP addresses can be used to communicate with the admin server.
Name of the user account used to log in the remote management controller and gain control over the managed server.
A user account with at least administration privileges within the remote management controller must be specified.
The user name can contain up to 16 alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e).
If a user account with a name of 17 or more characters has already been set up, either create a new user account or rename it with a name of up to 16 characters.
Password used to log in the remote management controller with the above user name.
The user name can contain up to 16 alphanumeric characters and symbols (ASCII characters 0x20 to 0x7e).
If a user account with password of 17 or more characters has already been set up, either create a new user account or change the password with one of up to 16 characters.
The destination for SNMP traps sent by the remote management controller should be set as the admin server's IP address.
For PRIMERGY servers, the server status can be monitored from external server management software (ServerView Agents). In that case, choose a value for the following setting.
Name of the SNMP community used to communicate with the server management software (ServerView Agents) on the managed server.
This community name can contain up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
Note
Use the same SNMP community for each server when using server switchover and cloning functions.
Choose values for the following management board settings, given the following criteria:
This name is used to identify the PRIMEQUEST chassis on the admin server. Each chassis name must be unique within the system.
The first character must be alphabetic, and the name can contain up to 10 alphanumeric characters and hyphens ("-").
These IP addresses can be used to communicate with the admin server.
Name of the user account used to log into remote server management and gain control over the managed server.
A user account with at least administration privileges within the remote server management must be specified.
This user name must be between 8 and 16 alphanumeric characters long.
Password used to log in the remote management controller with the above user name.
This password must be between 8 and 16 alphanumeric characters long.
This community name can contain up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-").
This must be the IP address of the admin server.
Note
To enable server switchover and cloning between servers in different chassis, use the same SNMP community for each chassis.
