Configuring New Environments

The Sun Data Center Reference Architecture captures and applies best practices to define a generic data center configuration. This architecture can then be reliably and quickly assembled, tested, and deployed with lower risk and lower total cost of ownership (TCO). Data Center Reference Architecture Implementations are instantiations of the Sun Data Center Reference Architecture that provide complete details with actual hardware and software products and technologies, along with services, to meet customer requirements. Data Center Reference Architecture Implementations are pre-designed, pretested groups of components for small, medium, and large data centers, and provide a production-ready target environment for enterprise consolidation and migration projects.

The Sun Data Center Reference Architecture Implementation framework is a flexible combination of SunFire Servers, Sun StorEdge^TM storage arrays, Sun Java^TM Enterprise System and Solaris software, as well as LAN and SAN infrastructure. For more information, see the Sun Data Center Reference Architecture web site.

Process Overview

1. Prepare the hardware for the N1 SPS Master Server, OS provisioning server, and boot and install servers.

2. Obtain the N1 SPS software.

3. Install the N1 SPS Master Server, as explained in Installing the N1 Service Provisioning System 5.1 in Sun N1 Service Provisioning System 5.1 Installation Guide.

4. Install the N1 SPS RA and N1 SPS command-line interface (CLI) on the OS provisioning server

5. Install the N1 SPS RA and N1 SPS CLI on the Solaris boot and install server

6. Install the N1 SPS RA on the Linux boot and install server

7. Prepare the RAs on the OS provisioning server, Solaris boot and install server, and Linux boot and install server. For information, see How to Prepare a Physical Host in Sun N1 Service Provisioning System 5.1 System Administration Guide.

For safety, back up the N1 SPS database. For information, see Chapter 9, Backing Up and Restoring, in Sun N1 Service Provisioning System 5.1 System Administration Guide.

How to Enable the Master Server to Use Session IDs

Steps

1. Edit the Master Server configuration file.

   By default, this file is located at the following location:

   /opt/SUNWn1sps/N1_Service_Provisioning_System_5.1/server/config/config.properties

2. If this is an existing N1 SPS installation, follow these steps:

   1. Find the session ID entry that looks similar to the following: config.allowSessionIDOnHosts=masterserver,biss1

   2. Change the value after the equals sign to the names of the OS provisioning server and the Solaris boot and install server.

      For example: config.allowSessionIDOnHosts=myspsserver,sol10bis

3. If this is a new N1 SPS installation, add a line similar to the following: config.allowSessionIDOnHosts=masterserver,biss1

   The value after the equals sign must include the names of the OS provisioning server and the Solaris boot and install server.

4. Adjust global plan execution timeouts for your environment.

   Change the following entries in the config.properties file:

   pe.defaultPlanTimeout=12000
   pe.nonPlanExecNativeTimeout=12000

   Where the timeouts are in seconds. Timeout should be greater than the longest plan run operation that you expect for your site. The default plan timeout is 30 minutes (1800 seconds). The default native timeout is 10 minutes (600 seconds). The above example shows an arbitrary higher timeout value of 200 minutes (12000 seconds).

5. To enable these changes, stop and restart the Master Server.

   Login to the Master Server as n1sps and type the following commands:

   # cr_server stop # cr_server start

   By default, these commands are in the following file:

   /opt/SUNWn1sps/N1_Service_Provisioning_System_5.1/server/bin