E.7.2 Preparations for Servers

In addition to the operations in "Chapter 8 Defining and Configuring the Server Environment", the following operations are necessary.

Install and configure OVM for SPARC
When installing an OS on a physical server, refer to the server virtualization software manual.
Enabling the Logical Domains Manager daemon, and then configure the definition files for enabling Solaris Zones to register VM hosts based on whether the Logical Domains Manager daemon is enabled or disabled.
For details, refer to "Appendix G Definition Files" in the "Setup Guide CE".
Configure SSH connection
Perform configuration to enable the root, with administrator authority of the guest domain, to establish SSH connections from the admin server of Resource Orchestrator to the VM host using the admin LAN.
Configure the virtual console
Configure the virtual console using the ldm command.
Install the RSCD agent
When using the function that needs BMC BladeLogic Server Automation described in "Table 11.6 Functional Differences Depending on Server Virtualization Software" in "11.1 Deciding Server Virtualization Software", do so using the following procedure.
1. Install the RSCD agent.
2. Add the managed server to BladeLogic.
  At this time, specify the IP address of the managed server when adding it.
For details, contact Fujitsu technical staff.
Pre-configuration of Server Management Software
When coordinating with BMC BladeLogic Server Automation, register BMC BladeLogic Server Automation in Resource Orchestrator as server management software. Perform pre-configuration before registration.
For details on pre-configuration, refer to "H.1 Coordination with BMC BladeLogic Server Automation" in the "Setup Guide CE".
Preparation for creating an L-Server with an image specified
- When creating an L-Server with a Solaris 10 image specified
  When creating an L-Server with a Solaris 10 image specified, coordinate Resource Orchestrator with BMC BladeLogic Server Automation, and install the OS using the JumpStart function of Solaris.
  Therefore, the following setup is necessary.
  1. Enable the provisioning function of Application Server of BMC BladeLogic Server Automation.
  2. Create a JumpStart server.
    For details, refer to the manual of Solaris.
    Supported configuration of the JumpStart server
    "Installation method"
    Resource Orchestrator only supports installation via a Local Area Network.
    Resource Orchestrator does not support the following installation styles.
    - Installation via a Wide Area Network
    - Installation from media
    "Boot method"
    Resource Orchestrator only supports a boot server (A system that acquires network information by RARP).
    Resource Orchestrator does not support booting by a DHCP server.
    Configuration contents of the JumpStart server
    The settings related to clients are not required. For details, refer to the manual of Solaris.
  3. Store the file required for coordination with BMC BladeLogic Server Automation in the JumpStart server.
    For details, contact Fujitsu technical staff.
    Store the following files in the JumpStart server.
    - rscd.sh (*1)
    - bmisolaris.tar (*1)
    - nsh-install-defaults (*2)
    - check file (*3)
    *1 It is a file included in BladeLogic Server Automation.
    *2 Create the response file required for RSCD agent installation, and store it in the JumpStart server.
    *3 Copy from the installation media of the OS. For details on the copy source, refer to the Solaris manual.
  4. Install an RSCD agent in the installation server.
  5. Add the installation server to BladeLogic.
  6. Configure the datastore of BMC BladeLogic Server Automation.
    Create a datastore instance of "Jumpstart DataStore".
  7. Configure the system package type of BMC BladeLogic Server Automation.
    Configure the system package type of "Solaris 10 Sparc".
- When creating an L-Server with a Solaris 11 image specified
  When creating an L-Server with a Solaris 11 image specified, coordinate Resource Orchestrator with BMC BladeLogic Server Automation, and install the OS using the Automated Installation (hereinafter AI) function of Solaris.
  Therefore, the following setup is necessary.
  1. Enable the provisioning function of Application Server of BMC BladeLogic Server Automation.
  2. Create an Automated Installation server.
    For details, refer to the manual of Solaris.
    Supported configuration of the Automated Installation server
    Create the Automated Installation service, without setting up DHCP.
    Configuration contents of the Automated Installation server
    The settings related to clients are not required. For details, refer to the manual of Solaris.
    Creation of an IPS repository server for the OS is also necessary.
    Create an Automated Installation service using the following name.
    ROR_AI
  3. Store the file required for coordination with BMC BladeLogic Server Automation in the Automated Installation server.
    For details, contact Fujitsu technical staff.
    Store the following files in the Automated Installation server.
    - rscd.sh (*1)
    - bmisolaris.tar (*1)
    - nsh-install-defaults (*2)
    *1 It is a file included in BladeLogic Server Automation.
    *2 Create the response file required for RSCD agent installation, and store in the Automated Installation server.
  4. Install an RSCD agent in the installation server.
  5. Add the installation server to BladeLogic.
  6. Configure the datastore of BMC BladeLogic Server Automation.
    Create a datastore instance of "AI DataStore".
  7. Configure the system package type of BMC BladeLogic Server Automation.
    Configure the system package type of "Solaris 11 Sparc".