document11

OL-12413-02

C H A P T E R 11
Creating Virtual Server Groups
These topics describe procedures for creating virtual server groups using the Virtual Server Groups menu:

• Creating a Virtual Server Group, page 11-1.

• Adding a Model Virtual Server to a Virtual Server Group, page 11-15.

• Adding One Virtual Server to a Virtual Server Group, page 11-51.

• Adding Multiple Virtual Servers to a Virtual Server Group, page 11-58.

The descriptions in this chapter use only a part of the functionality offered by the Virtual Server Group menu. For information about how to view and manage existing virtual server groups and the virtual servers they contain, see Chapter 12, “Managing Virtual Server Groups.”

Creating a Virtual Server GroupThese topics describe the steps required to create a virtual server group:

• Starting the Wizard for Creating a Virtual Server Group, page 11-1

• Step 1 of 5—Configuring General Group Properties, page 11-2

• Step 2 of 5—Specifying Minimum Equipment Requirements, page 11-5

• Step 3 of 5—Configuring Network Interfaces for a Virtual Server Group, page 11-7

• Step 4 of 5—Configuring Group Access to Fibre Channel Gateway Ports, page 11-11

• Step 5 of 5—Configuring Shared Storage, page 11-13

• After Creating a Virtual Server Group, page 11-14

Starting the Wizard for Creating a Virtual Server GroupUse the virtual server group wizard to configure the virtual server group and set the properties that will apply to all virtual servers that you add to the Group. To invoke the wizard, follow these steps:

Step 1 Launch VFrame Director, if it is not already open.

Step 2 Click the + next to the VFrame site icon.

Step 3 Click Virtual Server Groups in the navigation tree.

The Virtual Server Groups summary window displays.

11-1Cisco VFrame InfiniBand Director User Guide

Chapter 11 Creating Virtual Server Groups Creating a Virtual Server Group

Step 4 From the Select an Action drop-down menu, choose Add New Virtual Server Group to launch the virtual server group wizard, which steps through the process of creating a virtual server group, and later, virtual servers and images.

The virtual server groups Introduction window appears.

Figure 11-1 Add Virtual Server Groups Introduction Window

Step 5 Note the prerequisites that must be performed in advance of creating a virtual server group in the Before You Begin section. Refer to the Chapter 3, “Installing and Performing Initial Configuration of the VFrame Site” to add all of your assets to the VFrame site.

Step 6 Click the Next button to continue the process of creating a new virtual server group. This process involves five steps. See the “Step 1 of 5—Configuring General Group Properties” section on page 11-2.

Step 7 Click the Cancel button to stop creating the new virtual server group. A virtual server group is not saved until all five steps are complete.

Step 1 of 5—Configuring General Group PropertiesUse the Step 1 of 5 General Group Properties window to specify the virtual server group name and description, login and shutdown information, the maximum size of the group, and group-wide customization parameters.

To configure the properties, follow these steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so.

See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Step 1 of 5 - General Group Properties window appears after you have launched the wizard and clicked the Next button.


OL-12413-02


Figure 11-2 Add Virtual Server Groups—General Group Properties

Step 2 Enter a name for a new virtual server group in the Name field.

Step 3 Enter a description for a new virtual server group in the Description field.

Step 4 Enter the maximum number of servers that should be allowed in the virtual server group in the Maximum Physical Servers field.

Make sure that this number is high enough to accommodate all of the servers in your group. If you attempt to add a virtual server over this number, the VFrame Director will allow the virtual server to be added, but that virtual server will not have a physical server to assign to it.

Step 5 Enter the user name for the virtual server group in the Login field. The login should be the login of an Administrator capable of running the shutdown command that is specified. VFrame does not configure the login and password information.

Step 6 Enter the password for the new virtual server group in the Password field. The password should be the login of an Administrator capable of running the shutdown command that is specified. VFrame does not configure the login and password information.

Step 7 Reenter the password in the Confirm Password field.

Step 8 Enter the command that should be used to gracefully shut down the OS of the virtual server into the Shutdown Command field.

For Linux hosts, enter:

ssh=/sbin/shutdown –h now

For Windows hosts, enter:

netrpc


OL-12413-02


For Solaris hosts, enter:

ssh=/usr/sbin/shutdown -i 0 -g 0 -y

Step 9 Click the Add button to enter customizations to be adjusted for this virtual server group in the Customization Properties field. Refer to the “Specifying Customization Properties” section on page 11-4.

Step 10 Click the Back button to return to the Add Virtual Server Group window without saving changes.

Step 11 Click the Next button to continue creating the virtual server group.

The Minimum Equipment window opens. See the “Step 2 of 5—Specifying Minimum Equipment Requirements” section on page 11-5.

Step 12 Click the Cancel button to exit the wizard and return to the Virtual Server Groups window without saving changes.

Specifying Customization Properties

To add customized properties for the new virtual server group, follow these steps:

Step 1 From the Step 1 of 5 - General Group Properties window, click the Add button.

The Customization Properties window appears. Use this window to adjust standard customizations applied to the virtual server group by default with the installed customization script.

Figure 11-3 Add Customizations for the Whole Virtual Server Group

Step 2 Enter the property to be customized in the Property field.

Step 3 Enter the value to be associated with the property in the Value field.

In the example shown in Figure 11-3, the interface for the public IP is modified from the default, which is ib0, to ib0.8002. Refer to the “Understanding Image Manipulation and Customization” section on page 13-1 for a more detailed explanation.

Customizations for the virtual server group override Image level properties with the same name.

For Solaris-based virtual server groups, the following customization parameter must be defined to make the virtual servers full members of the mgmt partition:

• Property: mgmt.partition

• Value: full

Step 4 Click the OK button to save customization changes for the virtual server group and return to the Step 1 of 5 General Group Properties window.


OL-12413-02


The newly configured property shows in the Customization Properties field.

Step 5 Click the Cancel button to exit the window without saving changes.

Step 2 of 5—Specifying Minimum Equipment RequirementsUse the Step 2 of 5 - Minimum Equipment window to specify required capabilities of physical servers that will be allowed to join a virtual server group. If a physical server is needed for service, VFrame Director checks the standards that you set in the Minimum Equipment window and determines if a particular server meets those requirements. If the server hardware does not fit the specified standards, the server will not be used for that virtual server group. You can be more strict or less strict in your specifications, depending on the needs of your applications. Default values are set to the least restrictive. Use the default values unless you have a need to be more restrictive.

When you enter your requirements for the virtual server in the Minimum Equipment window, keep in mind that some requirements are considered satisfied if a server is found to have greater than or equal to the specified standard, and some requirements must be equal.

For example, if you set a requirement that the only type of CPU that can be used by the virtual server group is Intel, then any server being considered must have an Intel CPU to satisfy the requirement. However, if you set a CPU speed of 2000 MHz, then any server with a speed greater than or equal to 2000 MHz would satisfy the requirement.

Prerequisite

Power control must be configured for all physical servers (except the VFrame Director) before VFrame can use the device. If power control is not configured for a physical server, it is implicitly considered not to meet the minimum equipment requirements as power control is required for all managed servers. If power control is not defined for a physical server, that physical server can not be assigned to a virtual server.

Procedure

To set the minimum equipment requirements, follow these steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so.

See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Step 2 of 5 - Minimum Equipment window appears after you have launched the wizard and completed step 1.


OL-12413-02


Figure 11-4 Minimum Equipment Window for a Virtual Server Group

Step 2 Enter the type of CPU that the virtual server group will accept in the CPU Type field, such as Xeon. This field can be entered with free-form text and is case-insensitive.

Leave the entry empty if you do not want to specify this field. This field must be empty for Windows servers.

If you type an entry in this field, the virtual server group will require that any physical server be equal to this entry for it to be allowed into the group.

Step 3 Enter the minimum number of CPUs that a server must have in order to be accepted by the virtual server group in the # CPUs field.

The virtual server group will require that any physical server be greater than or equal to this entry for it to be allowed into the group. Set to 0 if you want to ignore this field.

Step 4 Enter the minimum CPU speed in MHz that this virtual server group will accept in the CPU speed field. For example, 1800 MHz.

CPUs with speeds equal to or over this amount will also be allowed into the group. Set to 0 if you want to ignore this field.

Step 5 Enter the minimum amount of memory in Mbytes that this virtual server group will accept in the Memory field. For example, 1 MB.

Servers with memory equal to or exceeding this amount will be allowed into the group. Set to 0 if you do not want to specify this field.

Step 6 From the Minimum Number of HCAs drop-down menu, choose the minimum number of HCAs required by this virtual server group.

Any servers allowed into the virtual server group will be required have equal to the number of HCAs that you specify. Possible values are 1 and 2. The default is 1.

Step 7 Enter the type of chipset a server must have to join a virtual server group in the Chipset field. Use this field if you have specific requirements in order for devices to be utilized. This field can be entered with free-form text and is case-insensitive.

Leave this field blank to allow a server with any kind of chipset to be used.

If you type an entry in this field, the virtual server group will require that any physical server be equal to this entry for it to be allowed into the Group.


OL-12413-02


Step 8 Click the Back button to return to the Step 1 of 5 - General Group Properties window without saving changes.

Step 9 Click the Next button to continue creating the virtual server group.

The Network Interfaces window opens. See the “Step 3 of 5—Configuring Network Interfaces for a Virtual Server Group” section on page 11-7.

Step 10 Click the Cancel button to return to the Virtual Server Groups summary window without saving changes.

Step 3 of 5—Configuring Network Interfaces for a Virtual Server GroupUse the Step 3 of 5 - Network Interfaces window to associate existing management or IPoIB network interface ranges for your virtual server group, or add new ranges.

Separate management interface ranges for each virtual server group provide network isolation between virtual server groups. Alternatively, if isolation of virtual server groups is not critical to your site, you can share management interface ranges among multiple virtual server groups. Sharing ranges has the following benefits:

• Avoids proliferation of IP addresses and p-keys.

• Reduces the number of IP interfaces that you must configure on the VFrame Director.

• Allows the VFrame Director to manage more virtual server groups before it hits the limit of the number of partitions to which a host can be a member.

Similarly, you can also associate an existing IPoIB network interface range with the virtual server group or create a new IPoIB interface range.

These topics describe the two methods:

• Configuring an Existing Network Interface Range, page 11-7

• Configuring a New Network Interface Range, page 11-8

Configuring an Existing Network Interface Range

These steps add an existing management interface to the virtual server group. The procedure is exactly the same for adding an IPoIB network interface.

To configure an existing network interface range, follow these steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so. See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Step 3 of 5 - Network Interfaces window appears as shown in Figure 11-5 after you have launched the wizard and completed steps 1 and 2.


OL-12413-02


Figure 11-5 Configure Network Interfaces for the Virtual Server Group

Step 2 Check the check box to the left of the Name field for that interface to add the existing interface range to the virtual server group.

To add all listed interface ranges to the virtual server group, check the check box next to Name in the table header.

Step 3 Click the Back button to return to the Minimum Equipment window without saving changes.

Step 4 Click the Next button to add the interface and continue creating the virtual server group. The Step 4 of 5 - WWPN Allocation window opens. See the “Step 4 of 5—Configuring Group Access to Fibre Channel Gateway Ports” section on page 11-11.


Step 6 (Solaris only) Use the command line interface (CLI) or Element Manager to create multicast groups for each partition on which IPoIB interfaces will be used in Solaris.

For example, to create a multicast group for the management partition, enter the following CLI command on the SFS server switch running the master subnet manager:

SFS-3012 (config)# ib sm subnet-prefix fe:80:00:00:00:00:00:00 multicast ipoib p_key 99:99

See the Cisco SFS Product Family Command Reference for additional details about how to create multicast groups.

Repeat this command for additional partitions that are used for IPoIB. These multicast groups should be created before the IPoIB driver is loaded on the Solaris host. For example, create the interfaces when you create the virtual server group (before virtual server creation).

Configuring a New Network Interface Range

These steps add a new IPoIB interface to the virtual server group. The procedure is exactly the same for adding a management network interface.

To configure a new network interface range, follow these steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so. See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Step 3 of 5 - Network Interfaces window appears after you have launched the wizard and completed steps 1 and 2.


OL-12413-02


Figure 11-6 Configure Network Interfaces for the Virtual Server Group

Step 2 Click the Create New Interface button.

The Add Network Interface dialog box appears.

Figure 11-7 Add Network Interface Dialog Box

Step 3 Assign a unique name to the network interface for the virtual server group in the Name field.

Step 4 Assign an interface alias in the Alias field. For example, you could associate a new IPoIB connection with the interface “ib0.”

Step 5 Enter the IP address at which the range of addresses should begin for the virtual server group in the Base IP Address field.

The Base IP Address is the lowest address in the range of IP addresses that will be used by the virtual servers. By default, each virtual server that is added will cause the IP address to be incremented by 1.

If the new interface will be a management interface, this IP address should be a private, nonbridged network address such as 192.168.10.1.

Step 6 Enter a network range for the new network interface in the Range Size field.


OL-12413-02


The range is the total number of addresses that are allowed to be added above the base IP address. For example, enter the number 4 if you want to allocate addresses 192.168.50.3 through192.168.50. 6 to this virtual server group.

Step 7 Enter the subnet mask assigned to the virtual server group in the Subnet Mask field.

Step 8 Enter the default gateway of the virtual server group in the Default Gateway field.

Step 9 Enter your own unique partition key (p_key), such as 99:99, in the IB Partition field to associate the network interface with an InfiniBand partition.

Step 10 In the Management Network field, click the True radio button if this range will be a management interface range. Otherwise, click the False radio button.

Step 11 Specify whether or not the interface is to be automatically configured on the VFrame Director hosts in the Auto Configure Interface On Director(s) field by clicking the Yes or No radio button.

Click No if the interface is an Ethernet interface.

If the new interface is an IP over InfiniBand interface, you can select Yes or No:

• Click Yes to automatically configure the network interface range on the VFrame Director hosts.

• Click No if you prefer to configure the management interface on the VFrame Director host manually. See the “(Optional) Configuring a Management Interface on the VFrame Director Host” section on page 3-11.

Note A failed attempt to auto-configure the VFrame Director host is the equivalent of clicking the No radio button; you must then configure the management interface on the VFrame Director host manually.

Step 12 Click Cancel to return to the Virtual Server Group Network Interfaces window without saving your changes.

Step 13 Click Add to create the new network interface.

The Virtual Server Group Network Interfaces window displays. The new interface is added to the list.

Figure 11-8 Network Interfaces for the Virtual Servers in a Virtual Server Group

Step 14 Verify that a check mark appears in the box next to the interface you just added.

Step 15 Click the Create New Interface button to create another network interface.

Step 16 Click the Back button to return to the Minimum Equipment window without saving changes.


OL-12413-02


Step 17 Click the Next button to add the interface and continue creating the virtual server group. The Step 4 of 5 - WWPN Allocation window opens. See the “Step 4 of 5—Configuring Group Access to Fibre Channel Gateway Ports” section on page 11-11.

Step 18 Click the Cancel button to return to the Virtual Server Group summary window without saving changes.

Note Cancelling virtual server creation does not delete the network interface you just created. You can delete the network interface only from the Assets menu. See “Deleting a Network Interface” section on page 9-55.

Step 19 (Solaris only) Use the command line interface (CLI) or Element Manager to create multicast groups for each partition on which IPoIB interfaces will be used in Solaris.

For example, to create a multicast group for the management partition, enter the following CLI command on the SFS server switch running the master subnet manager:

SFS-3012 (config)# ib sm subnet-prefix fe:80:00:00:00:00:00:00 multicast ipoib p_key 99:99

See the Cisco SFS Product Family Command Reference for additional details about how to create multicast groups.

Repeat this command for additional partitions that are used for IPoIB. These multicast groups should be created before the IPoIB driver is loaded on the Solaris host. For example, create the interfaces when you create the virtual server group (before virtual server creation).

Step 4 of 5—Configuring Group Access to Fibre Channel Gateway PortsUse the Step 4 of 5 - FC Port Access window to control the access that virtual servers in a group have to the fibre channel gateway ports. For example, you may have created several different pools of fiber channel ports (see the “Creating Fibre Channel Port Pools” section on page 3-7), but want this group of virtual servers to use only one of those groups.

All of the fibre channel port pools that you have created appear in this window as available to the virtual server group, and you can choose to allow access or restrict access as needed.

To configure group access to Fibre Channel gateway ports, follow these steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so. See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Step 4 of 5 - FC Port Access window appears after you have launched the wizard and completed steps 1, 2, and 3.


OL-12413-02


Figure 11-9 Set the Fibre Channel Port Access for the Group

Step 2 View an existing group of fibre channel port groups in the Port Pool field. Click the name of an existing group to view or edit the properties of the port group, such as adding more physical gateway ports. See the “Viewing Fibre Channel Port Pools” section on page 9-8.

Step 3 View the description of the fibre channel port group in the Pool Description field. See the “Viewing Fibre Channel Port Pools” section on page 9-8.

Step 4 View the number of the fibre channel ports available to the port pool in the Pool Size field. This number can be changed by adding or subtracting from the fibre channel port group (refer to the “Viewing and Editing Port Pool Details” section on page 9-14).

Step 5 Enter the number of WWPNS that should be allocated to the virtual server group in the # WWPNs field.

Ports of type NL_Port are members of two-port gateways. Currently supported Fibre Channel gateways have two ports only. For ports of type NL_Port, the number of WWPNs determines the number of ports allocated to each virtual server in the group.

Ports of type E_Port or F_Port are members of four-port gateways. For ports of type E_Port or F_Port, the number of WWPNs determines the number of four-port Gateways allocated to each virtual server in the group.

Note Only two-port gateways are currently supported.

By default, a virtual server group is assigned 0 ports, which means that none of the virtual servers in that group have access to any of the fiber channel gateway ports in that pool. Leave the # WWPNs at 0 to restrict the virtual server group from using a particular group of ports.

Enter a value greater than 0 in the # WWPNs field to allow the virtual servers in this group to have access to a particular group of ports.

Note If you do not change the default in the # WWPNs field from 0 for any of the port pools, the virtual servers that you add to this group will not have access to any storage.

If you are unsure, allocate all ports from the pools that you want to access from this virtual server group. For example, if the Pool Size is 4, set # WWPNs also to 4.

Step 6 Click the Back button to return to the Network Interface window without saving changes.


OL-12413-02


Step 7 Click the Next button to continue creating the virtual server group. The Step 5 of 5 - Shared Storage window opens. See the “Step 5 of 5—Configuring Shared Storage” section on page 11-13.


Step 5 of 5—Configuring Shared StorageShared storage is configured at the Group level, while dedicated storage is configured at the virtual server level.

To configure shared storage, follow these steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so. See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Step 5 of 5 - Shared Storage window appears after you have launched the wizard and completed steps 1 through 4.

Shared storage is used among all the virtual servers that have been created within a virtual server group. This functionality supports your shared storage (database shared files) and requires your application support (cluster fileshare).

For Linux servers, you can configure shared storage. For Windows servers, you cannot use shared storage.

Figure 11-10 Assign Shared Storage to the Virtual Server Group

Step 2 View the WWPN of any previously discovered shared storage in the virtual server group in the Name field. View the Logical ID of the LUN.

Step 3 View the current status of shared storage in the State field. The possible states are described in Table 5-3 on page 5-7.

Step 4 View the assigned description of any shared storage for the virtual server group in the Description field. The description of LUNs can be changed in this window for easier identification.

Step 5 View the size of the LUN in the Size field.


OL-12413-02


Step 6 Click the Assigned check box to select the shared storage to which you want to assign the virtual server group.

The Assigned check box is dimmed and cannot be checked if the storage LUN has already been assigned to another virtual server. This protection is enforced by default so long as the No button is selected in the “Allow selection of storage assigned to another virtual server” field. Use caution if you choose to override this protection.

After checking the Assigned box, edit the description field to describe how the LUN is used. The description aides in identification later, For example, Linux Shared LUN.

The Device ID box appears next to the chosen storage after checking the Assigned box.

Step 7 Enter the order in which the storage will be used into the Device ID field. The Device ID refers to the order that the storage will be used.

Device ID 0 indicates the boot device. Do not use the integer 0 for any shared storage.

This mechanism provides an alternate path to the boot LUN in case the primary path is not available.

The Device ID field is used in both shared and dedicated storage to configure the order in which a disk will be used.

Note the following information about device IDs:

• Span dedicated and shared storage

• Must be numbered 0 through n - 1, where n is the number of devices. For example, three disks would be numbered as 0, 1, 2.

• The device that is numbered 0 is the boot device.

• Target binding is used on the host to order targets.

Step 8 Click the Finish button.

Step 9 The Virtual Group Creation Successful window appears when you have completed the creation of the virtual server. See the “After Creating a Virtual Server Group” section on page 11-14.

After Creating a Virtual Server GroupNow that you have successfully created a virtual server group, the Virtual Server Group Creation Successful window appears and gives you the option of returning to the Virtual Server Groups summary window, or adding virtual servers to your newly created virtual server group.

After creating a virtual server group, follow theses steps:

Step 1 Begin the Add Virtual Server Group wizard, if you have not already done so. See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1. The Virtual Server Group Creation Successful window appears after you have launched the wizard and entered the fields in steps 1 - 5.


OL-12413-02

Chapter 11 Creating Virtual Server Groups Adding a Model Virtual Server to a Virtual Server Group

Figure 11-11 Successful Creation of a Virtual Server Group

Step 2 Click the Return to Summary button to go to the Virtual Server Group Summary window without adding virtual servers to the group. You can return to the virtual server group later to add virtual servers. See the “Viewing and Using Virtual Server Group Summary Information” section on page 12-2.

Step 3 Click the Add Virtual Server(s) button to begin adding virtual servers to the group. See the “Starting the Wizard for Adding a Model Virtual Server” section on page 11-15.

Adding a Model Virtual Server to a Virtual Server GroupThese topics describe the steps required to add a model virtual server to a virtual server group.

• Starting the Wizard for Adding a Model Virtual Server, page 11-15

• Step 1 of 8—Configuring General Properties of a Model Virtual Server, page 11-16

• Step 2 of 8—Confirming Network Interfaces for a Model Virtual Server, page 11-18

• Step 3 of 8—Configuring Fibre Channel World Wide Names for a Model Virtual Server, page 11-19

• Step 4 of 8—Configuring Dedicated Storage for a Model Virtual Server, page 11-20

• Step 5 of 8—Initializing Storage for a Model Virtual Server, page 11-21

• Step 6 of 8—Assigning a Physical Server to a Model Virtual Server, page 11-22

• Step 7 of 8—Installing the Operating System on a Model Virtual Server, page 11-23

• Step 8 of 8—Creating a Snapshot Image of a Model Virtual Server, page 11-43

• After Creating a Model Virtual Server, page 11-51

Starting the Wizard for Adding a Model Virtual ServerTo start the wizard, follow these steps:

Step 1 Create a virtual server group, if you have not already done so. See the “Starting the Wizard for Creating a Virtual Server Group” section on page 11-1.

If you previously created a virtual server group and have not yet added virtual servers, click the virtual server group in the summary window. See the “Viewing and Using Virtual Server Group Summary Information” section on page 12-2.

The Introduction window appears.


OL-12413-02


Figure 11-12 Introduction to Add Virtual Server to a Virtual Server Group

Step 2 Click the Model virtual server, including installation of the operating system radio button to add a virtual server that includes a new operating system (OS) and its applications.

The model virtual server option assumes that you are about to create the virtual server that will contain the golden image for the remainder of the virtual servers in the group. You will manually install the operating system and Applications in a later step. See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16.

Step 3 Click the (1 - 32) additional virtual servers from an existing image radio button if you have already created an OS and application image, and enter the number of virtual servers that you want to create in the dialog box. Use this option if you have previously created a virtual server for the group, and have already made a golden image. If you are adding just one virtual server, skip to the “Step 1 of 5—Configuring General Group Properties” section on page 11-2. If you are adding more than one virtual server, skip to the “Adding Multiple Virtual Servers to a Virtual Server Group” section on page 11-58.

Virtual servers are created after a virtual server group is made. For your convenience, once a virtual server is named on the first page it will be saved, and you can exit the process at any time. You can then return to the wizard through the Summary page, and complete the process. The virtual server will remain in the Creating state until the configuration is complete.

Step 4 Click the Next button and proceed to the “Adding a Model Virtual Server to a Virtual Server Group” section on page 11-15, the “Step 1 of 5—Configuring General Properties of One Virtual Server” section on page 11-53, or to the “Step 1 of 3—Configuring General Properties for Multiple Virtual Servers” section on page 11-60.

Step 5 Click the Cancel button to exit the Virtual Server wizard.

Step 1 of 8—Configuring General Properties of a Model Virtual ServerThese instructions assume you are creating a virtual server with a new image. If you already have an image, refer to the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” procedure on page 11-16.

To configure general properties of a model virtual server, follow these steps:

Step 1 Go to the Virtual Server wizard introduction window. See the “Starting the Wizard for Adding a Model Virtual Server” section on page 11-15.

Step 2 Click the Model Virtual Server, including installation of the operating system radio button. The Step 1 of 8 - General Virtual Server Properties window appears, as shown in Figure 11-13.


OL-12413-02


Figure 11-13 Add Virtual Server to a Virtual Server Group with New Image—Step 1

Step 3 Enter a name for the virtual server in the Hostname field. This text is a short description that will assist you in selecting the host from a list.

Note This name should be the hostname of the machine exactly.

Step 4 Enter a description for the virtual server in the Description field. This text is a longer description of the virtual server.

Step 5 (Optional) Click the Add button to enter customizations to be added to this group in the Customization Properties field. Refer to the “Understanding Image Manipulation and Customization” section on page 13-1.

Use this field to adjust properties that are set by the standard customization script. Customizations for the virtual server override virtual server group level properties with the same name.

Step 6 Click the Back button to return to the previous window without saving changes.

Step 7 Click the Next button to continue adding the model server. The Step 2 of 8 Virtual Server Network Interfaces window opens. See the “Step 2 of 8—Confirming Network Interfaces for a Model Virtual Server” section on page 11-18.

Step 8 Click the Cancel button to return to the Virtual Servers summary window without saving changes.


OL-12413-02


Step 2 of 8—Confirming Network Interfaces for a Model Virtual ServerTo confirm network interfaces for a model virtual server, follow these steps:

Step 1 Complete Step 1 of the Virtual Server wizard. See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 2 of 8 - Virtual Server Network Interfaces window appears as shown in Figure 11-14.


Step 2 View the name of the network interface assigned to the virtual server in the Name field, and the associated alias in the Alias field.

The base IP address was configured for the virtual server group, as described in the “Step 3 of 5—Configuring Network Interfaces for a Virtual Server Group” section on page 11-7, and each virtual server increments the base IP by 1.

The management interface is added automatically.

Step 3 View or edit the IP address of the network interface in the IP Address field.

Note If you change the IP address that is automatically assigned to the virtual server, verify that the new address is still within the range that was specified for the virtual server group. For example, if you specified a range of 10, you will be able to allocate only 9 addresses above the base.


Step 5 Click the Next button to continue add the model virtual server.

The Step 3 of 8 Virtual Server FC WWNs window opens. See the “Step 3 of 8—Configuring Fibre Channel World Wide Names for a Model Virtual Server” section on page 11-19.



OL-12413-02


Step 3 of 8—Configuring Fibre Channel World Wide Names for a Model Virtual Server

To configure WWNs for a model virtual server, follow these steps:

Step 1 Complete Steps 1 and 2 of the Virtual Server wizard.

See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 3 of 8 - Virtual Server FC WWNs window appears.


Step 2 View the Fibre Channel World Wide Node Names (WWNNs) that have been generated for the new virtual server in the WWNNs field.

a. If you are using access control on the storage array, configure the array to allow storage access to the displayed WWNs.

b. If you are using zoning on your SAN, note this WWNN. You will need to add this identifier to your zone configuration. Refer to the Cisco VFrame InfiniBand Third-Party Integration Guide for fibre channel zone configuration samples.

These WWNNs are applied to a physical server when it is assigned to this virtual server.

Step 3 View the virtual World Wide Port Names (WWPNs) and World Wide Node Names (WWNNs) for the fibre channel gateway in the WWNN and WWPN fields.

a. If you are using zoning on your SAN, note the WWPN and WWNN values. You will need to add this identifier to your zone configuration. Refer to the Cisco VFrame InfiniBand Third-Party Integration Guide for Fibre Channel zone configuration samples.

These WWPNs and WWNNs are applied to a physical server when it is assigned to this virtual server.

Step 4 View the group of fibre channel ports assigned to the virtual server in the Port Pool field. Refer to the “Viewing Fibre Channel Port Pools” section on page 9-8 for more information about grouping fibre channel ports.



OL-12413-02


Step 6 Click the Next button to continue creating the model virtual server. The Step 4 of 8 Virtual Server Storage window opens. See the “Step 4 of 8—Configuring Dedicated Storage for a Model Virtual Server” section on page 11-20.


Step 4 of 8—Configuring Dedicated Storage for a Model Virtual ServerTo configure dedicated storage for a model virtual server, follow these steps:

Step 1 Complete Steps 1 through 3 of the Virtual Server wizard.

See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 4 of 8 - Virtual Server Storage window appears.


Step 2 View the WWPN of any previously discovered dedicated storage in the virtual server group in the Name field. View the Logical ID of the LUN.

Step 3 View the current status of shared storage in the State field. For example, an Inactive state may indicate that the LUN is not being used, but could also indicate that the LUN is not reachable.

Step 4 View the description previously assigned to the shared storage in the Description field. To edit the description, see the “Viewing or Modifying Target Properties” section on page 9-41.

Step 5 View or edit the description of a LUN in the Description field.

It is recommended that you change the generic description to something that identifies the use of the LUN. For example, LUN for virtual server 2 Red Hat image.


Step 7 View any previously assigned shared storage in the Assigned field. Select the dedicated storage to which you want to assign the virtual server by clicking the Assigned check box.


OL-12413-02


The Device ID box appears next to the chosen storage.

If you will be using multipathing software on the virtual server, you can enhance path redundancy by assigning multiple paths to a given LUN.


Device ID 0 indicates the boot device.

The VFrame Director uses SRP logical unit (LU) remapping (SRP LU ID) to achieve the desired order of LUs.

Step 9 Click the radio button in the Alternative Boot field if the LUN is to be designated as an alternative boot LUN. The LUN designated as an alternative boot LUN must have the same logical LUN ID as the primary boot LUN and must be accessed through a different target. VFrame enforces these rules by dimming the Alternative Boot field radio buttons for all target/LUN pairs except those that comply with the rule.

This mechanism provides an alternative path to the boot LUN in case the primary path is not available.


Step 11 Click the Next button to continue creating the model virtual server. The Step 5 of 8 Virtual Server Storage window opens. See the “Step 5 of 8—Initializing Storage for a Model Virtual Server” section on page 11-21.


Step 5 of 8—Initializing Storage for a Model Virtual ServerTo initialize storage for a model virtual server, follow these steps:


See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 5 of 8 - Initialize Storage window appears.

Figure 11-17 Prepare Storage Before Creating Image—Step 5

Step 2 Click the Initialize Storage button to prepare the storage for use.


OL-12413-02


Although this step is optional, it is highly recommended. The process can take over a minute per gigabyte of dedicated storage, depending on the speed of your storage devices. However, initializing the dedicated storage significantly reduces the amount of time that it takes to create a new image and deploy that image.

The Initializing Storage process can also be performed at a later time, but should be done before you install the operating system and applications on the dedicated storage of the virtual server.

A progress indicator shows the percentage complete of the storage initialization job. You will receive a message indicating that the storage initialization is complete.


Step 4 Click the Next button to skip storage initialization or to move on after the initialization is complete.

The Step 6 of 8 - Physical Server window opens. See the “Step 6 of 8—Assigning a Physical Server to a Model Virtual Server” section on page 11-22.


Step 6 of 8—Assigning a Physical Server to a Model Virtual ServerTo assign a physical server to a model virtual server, follow these steps:


See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 6 of 8 - Physical Server window appears, as shown in Figure 11-18.


Step 2 From the Please select the physical server you wish to use drop-down menu, choose a physical server to assign to the virtual server. The physical server will be powered on and be used to install the operating system and applications associated with this virtual server.

Prerequisite steps to assigning the physical server include the following:

a. Manually configure the IP interface of the first physical server, if you have not already done so. Additional virtual servers that use the installed image will have interfaces configured automatically by a customization script. The customization script is included in the host driver installation. Refer to the “Understanding Image Manipulation and Customization” section on page 13-1.

b. Power off the physical server before assigning it to a virtual server. VFrame will power the physical server on.


OL-12413-02


c. Make sure that you have configured power management for the physical server before you attempt to assign it to a virtual server. VFrame will power on the server once it is assigned.

d. Only physical servers that meet previously -defined minimum equipment requirements and have power control defined will appear in the list.

A warning appears if there are no physical servers available that meet the Minimum Equipment Requirements, as specified in the “Step 2 of 5—Specifying Minimum Equipment Requirements” section on page 11-5. If you do not have a physical server that meets the requirements, you can edit the requirements for the virtual server group; refer to the “Viewing and Editing Minimum Equipment Requirements” section on page 12-21.


Step 4 Click the Next button to continue creating the model virtual server. The Step 7 of 8 - Install OS and Applications window opens. See the “Step 7 of 8—Installing the Operating System on a Model Virtual Server” section on page 11-23.


Step 7 of 8—Installing the Operating System on a Model Virtual ServerUse the OS installation CD-ROM along with the Cisco driver CD-ROM to perform the physical installation of the operating system and applications.

The following procedures describe a Linux installation, a Solaris installation, and a Windows 2000 installation:

• Installing Linux on a Host, page 11-23

• Installing Windows on a Host, page 11-26

• Installing Solaris on a Host, page 11-31

A customization script is included and enabled by default in Linux host drivers. The purpose of this script is to customize the configuration of a server based on the properties assigned to it by VFrame.

Using the customization scripts, the VFrame Director writes the basic networking information for the virtual server to the customization answer file. To view all the parameters that are customized by the VFrame Director by default, see Table 13-1 on page 13-2.

For additional sample installations, refer to the Cisco SFS Boot over InfiniBand User Guide for Linux or the Cisco SFS Boot over InfiniBand User Guide for Windows.

Installing Linux on a Host

To install Red Hat Enterprise Linux 3.0 and Red Hat 9, follow these steps:

Step 1 Complete steps 1 through 6 of the Virtual Server wizard.

See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 7 of 8 - Install OS and Applications window appears, as shown in Figure 11-19.


OL-12413-02



Step 2 Make sure that you have keyboard access to the host before you begin the installation.

Step 3 Place the first installation CD in your host and boot the server from the CD.

Step 4 At your host CLI, exit interactive mode.

Step 5 At the boot prompt, enter the linux dd askmethod command to prompt the installer to run the Cisco driver CD.

Step 6 At the Do you have a driver disk? prompt, choose Yes.

Step 7 On the Driver Disk Source screen, select your CD-ROM, and then click OK.

The Insert Driver Disk screen appears.

Step 8 Remove the Linux installation CD and place the Cisco driver CD in the drive, and then click OK. The ts_srp_host driver loads.

Step 9 At the Do you wish to load any more driver disks? screen, choose no.

The Installation Method window appears.


OL-12413-02


Figure 11-20 Select Installation Method

Step 10 Select the media from which you want to install the packages and complete the installation as you normally would.

Note Install the boot loader to the SRP drive. If you have a local ATA drive, by default the host will be configured to install the boot loader on the ATA drive, which you must avoid.

Step 11 Verify that the host installs the boot loader on the SRP drive.

Step 12 Remove the driver CD and reboot the host.

Step 13 If your host includes a local disk, reboot your host and enter BIOS setup, and then reconfigure the boot order so that SRP Boot comes first. Save your changes.

Step 14 As your host reboots, press the x key when the “Type ‘x’ to configure boot options” prompt appears during the boot process.

Step 15 Enter the menu number of the Well Known Service Name that you want to use as the boot target.

Step 16 Press s to save the configuration.

Step 17 Press x to exit interactive mode and finish booting.

Step 18 Configure the management interface on the first virtual server in the virtual server group.

This action is necessary for the first virtual server in the group so that the VFrame Director can begin communication with the virtual servers. Additional virtual servers will use the customization script (installed with drivers) to configure the management interface automatically.

a. Log into the host onto which you just installed the image. If the host does not have a local drive, use KVM or a serial connection to connect to the host.


OL-12413-02


b. Configure the management interface.

[root@Virtual Server 1 root]# cd /usr/local/topspin/sbin[root@Virtual Server 1 sbin]# ./ipoibcfg add ib0 99:99 mgmt

c. Add the address of the virtual server (refer to the “Step 3 of 5—Configuring Network Interfaces for a Virtual Server Group” section on page 11-7).

[root@Virtual Server 1 sbin]# ifconfig mgmt 172.20.200.3

Step 19 On the VFrame GUI Step 7 of 8 - Install OS and Applications window, click the Ping Test button to verify that the VFrame Director can reach the virtual server. The virtual server will be powered down by VFrame before creating an image of the virtual server.


Step 21 Click the Next button when the installation is complete.

The VFrame Director attempts to ping the new virtual server and displays results. The Step 8 of 8 - Create Snapshot Image (Optional) window opens. See the “Step 8 of 8—Creating a Snapshot Image of a Model Virtual Server” section on page 11-43.


Installing Windows on a Host

These topics describe how to install Windows on a model server:

• Installing the Windows Image Locally, page 11-26

• Adding Windows IB Drivers to the Image, page 11-27

• Copying a Windows Image onto Storage LUN, page 11-28

• Merging IB Interfaces, page 11-28

• Creating the mgmt Interface on the Windows Host, page 11-29

• Testing and Completing the Installation, page 11-31

Installing the Windows Image Locally

To install the Windows image locally, follow these steps:

Step 1 Select a server onto which you want to install your golden image. This server must have a local disk and an HCA installed.

Step 2 Unassign the physical server from any virtual server, if it was previously assigned.

Step 3 Configure the server BIOS to boot from the local hard disk before SRP boot.

Step 4 Power on the physical server and install Windows on the local hard disk.

Step 5 Install any necessary Windows patches.


OL-12413-02


Adding Windows IB Drivers to the Image

To add Windows IB drivers to the image, follow these steps:

Step 1 Install InfiniBand drivers on the server with the Windows image.

a. Log into your Windows host. Insert the boot driver CD or download the boot over IB Win2k3 drivers.

Note For VFrame managed hosts, it is critical that you install only boot over InfiniBand (BOIB) drivers. For example, Topspin-ib-boot-W2k-release_number.exe.

b. Begin the installation.

The product Install window appears.

c. Click the Next button.

The Installation in Progress window appears with the status of the installation.

A Windows driver dialog box appears. The dialog box explains that the new drivers do not contain a Windows signature. Although the drivers are not digitally signed, they are tested using the Microsoft HCT suite. WHQL submission materials are available on request (CAN files, an so on).

d. Click the Continue Anyway button each time the Windows logo testing dialog box appears.

e. Click the Yes button.

Important: Ignore the Found New Hardware Wizard when it appears, as it will continue without user intervention. This window appears three times: twice for the IPoIB and once for SRP.

The Installation Complete window appears.

f. Click the Finish button.

g. Reboot the server.

Step 2 Verify the Windows IB boot drivers.

a. Log in to your host.

b. Choose Start > Programs > Topspin InfiniBand SDK.

If icons appear in the Topspin InfiniBand SDK folder, the installation succeeded.

c. Choose Start > Settings > Network and Dial-up Connections.

The Network and Dial-up Connections window opens.

d. Verify that a Topspin over IB Virtual Channel Adapter entry appears for each HCA port.

e. Right-click My Computer, and then choose Manage from the right-click menu.

The Computer Management window opens.

f. Click Device Manager, and then expand Network Adapters to verify that your IB interfaces function properly.

g. Check the LEDs on the physical HCA after you connect the HCA to a server switch with an InfiniBand cable. Verify that your cables are seated properly and verify a solid green LED for physical connection. A yellow LED indicates that the Subnet Manager is able to communicate with the host.

h. Verify that IPoIB adapters on the task bar appear connected.

The IP over InfiniBand Adapter pop-up appears.


OL-12413-02


i. If the ports do not appear active, right-click an IPoIB adapter port and choose Scan for hardware changes.

Copying a Windows Image onto Storage LUN

Note The storage LUN must be the same size or bigger than the server’s local disk.

To copy the Windows image onto the storage LUN, follow these steps:

Step 1 Install Hard Disk Manager, if you have not already done so.

Step 2 Reboot to finish the installation of Hard Disk Manager.

Step 3 Choose My Computer > Manager > Disk Management to start the Windows Disk Administrator.

Verify that the SRP disk appears.

Step 4 Configure the SRP disk to be a Basic Disk rather than a Dynamic Disk.

Step 5 Choose Start > Programs > Paragon Partition Manager > Hard Disk Manager to launch your partitioning software.

Step 6 Verify that the C: drive is the same size as the associated LU or smaller.

Step 7 Right-click the local disk (Disk 0) and select Copy hard disk... from the right-click menu.

The Copy hdd0 to window opens.

Step 8 From the Destination Disk drop-down menu, choose your LU, and then click OK.

Step 9 Reboot your server.

Paragon software copies the local disk to the SRP LU. The Windows boot resumes when the copy is finished.

Step 10 Power off the physical server to stop the boot process.

Step 11 Remove the local drive from the host or enter the server BIOS and disable the local drive.

Step 12 Change the boot order to boot from InfiniBand SRP before local hard disk.

Step 13 Boot the server.

The server boots from the SRP disk. The SRP disk becomes drive C.

Merging IB Interfaces

To merge IB interfaces, follow these steps:

Step 1 Log in to the Windows 2000 GUI.

Step 2 Merge the IB ports as follows:

a. Right-click My Computer and choose Manage.

b. Choose Device Manager.


OL-12413-02


c. Right-click the Cisco’s IPoIB interface and choose Properties.

d. Click the Properties tab.

Step 3 Check the Port Failover State check box and confirm the failover when the dialog box appears.

Step 4 Click OK.

Step 5 Click OK to reboot on the host.

Creating the mgmt Interface on the Windows Host

To create the mgmt interface on the Windows host, follow these steps:

Step 1 Log back into the Windows GUI.

Step 2 Right-click My Computer and choose Manage.

Step 3 Choose Device Manager.

Step 4 Right-click the Cisco’s IPoIB interface and click Properties.

Step 5 Click the Properties tab.

Step 6 Check the Create a new IP over IB Virtual Interface check box.

Step 7 Enter 99:99 in the Pkey field, and then click OK.

Step 8 Choose Start > Settings > Control Panel > Network and Dial-up Connections.

The Network and Dial-up Connections window opens.

Step 9 Note the name of both ib0 and mgmt connections. Copy the name of the mgmt connection for use in a later step.

Step 10 Use DHCP to set all network interfaces to avoid the same IP address appearing on the network when deploying the image to multiple virtual server groups at the same time.

a. Double-click one of the interfaces in the Network and Dial-up Connections window.

A status window opens.

b. Click the Properties button.

A properties window opens.

c. Double-click Internet Protocol (TCP/IP).

The Internet Protocol (TCP/IP) Properties window opens.

d. Click the Obtain an IP address automatically radio button to use DHCP to assign the IP address.

e. Click the Obtain DNS server address automatically radio button to use DHCP to assign the DNS address.

f. Click the OK button to return to close the Internet Protocol (TCP/IP) Properties window.

Step 11 Configure additional IPoIB interfaces, as appropriate, such as those needed for “data” interfaces for the virtual server group.


OL-12413-02


Adding Customization Parameters

These steps customize the mgmt.alias and, optionally, the device ID and partition number for the virtual server group. Perform these steps now while the Windows server is up and you can access required information.

To add customization parameters, follow these steps:

Step 1 Expand Virtual Server Groups in the VFrame navigation tree, click the Windows virtual server group name, and then click the General tab.

The Virtual Server Group Properties window appears.

Step 2 Add the mgmt.alias property to the virtual server group customization properties.

This step matches the mgmt interface in Windows with the corresponding interface name in VFrame.

a. Click the Add button to enter information into the Customization Properties field.

The Add Customization Properties dialog box appears.

b. In the Property field, enter mgmt.alias.

c. In the Value field, enter the name of the interface.

This value must be the exact same name as shown on the Network and Dial-up Connections window.

d. Click the OK button.

The Virtual Server Group Properties window refreshes with the new parameter added.

Step 3 Customize the device ID and the number of the partition.

a. Click the Add button.

The Add Customization Property dialog box appears again.

b. In the Property field, type properties.destination.

c. (Optional) In the Value field, enter the deviceID.Partition #.

By default, 0.1 is used. If your device ID is 0 (the boot disk) and your partition is 1 (the default in most cases), then you do not need to complete this part of the customization.

The device ID identifies the disk on which Sysprep was installed. In most cases this is 0, which is the boot disk. View the device IDs in the Storage Assignments for the virtual server group if you are not sure of the value.

The Partition number identifies the numbered partition on which Sysprep was installed. You can look at your partitions through Windows Partition Manager by going to My Computer > Manage > Disk Management.

For example, if you installed sysprep on the first partition, the parameter would look like this: Value: 0.1

d. Click the OK button.


Step 4 Click Apply.

Step 5 To return to the Virtual Server wizard at the point where you stopped, click the Virtual Servers tab, and then click the name of the virtual server you are creating.


OL-12413-02


Testing and Completing the Installation

To test and complete the installation in the VFrame GUI, Step 7 of 8 - Install OS and Applications window, follow these steps:

Step 1 Click the Ping Test button to verify that the VFrame Director can reach the virtual server.

VFrame powers down the virtual server before creating an image of the virtual server.




Step 4 Click the Cancel button to return to the Virtual Servers window without saving changes.

Installing Solaris on a Host

These topics describe how to install Solaris on a model server:

• “Before Installing Solaris” section on page 11-31

• “Installing Solaris” section on page 11-32

• “Enabling Root Logins over Secure Shell (ssh)” section on page 11-41

• “Updating Device Names for the Model Virtual Server” section on page 11-37

• “Configuring Storage” section on page 11-37

• “Configuring Storage for EMC Symmetrix Only” section on page 11-37

• “Configuring Storage (All Storage Types)” section on page 11-40

• “Preparing a File System for Customization Properties File” section on page 11-40

• “Configuring the mgmt Interface” section on page 11-41

• “Installing and Configuring the Miniroot” section on page 11-42

• “Configuring Default Boot Options” section on page 11-42

• “Testing and Completing the Installation” section on page 11-43

Before Installing Solaris

Before installing Solaris, check that the entities described in the following steps have been correctly configured. These entities are typically configured during virtual server group creation. To check the entities, follow these steps:

Step 1 Verify that the command for gracefully shutting down virtual servers has been correctly set as follows:

ssh=/usr/sbin/shutdown -i 0 -g -y

Use the Virtual Server Group Properties window to confirm that this command has been correctly configured or to make corrections. See the “Viewing and Editing General Virtual Server Group Properties” section on page 12-6 for details.


OL-12413-02


Step 2 Verify that the following customization property has been correctly defined to make virtual servers full members of the mgmt partition:

mgmt.partition=full

Use the Virtual Server Group Properties window to confirm that this customization property is correctly set or to make corrections. See the “Viewing and Editing General Virtual Server Group Properties” section on page 12-6 for details.

Step 3 Verify that a multicast group exists for each partition on which IPoIB interfaces will be used on Solaris.

Check for multicast groups using either the command line interface or Element manager. See the “Configuring an Existing Network Interface Range” section on page 11-7 for information about creating these multicast groups.

Step 4 Obtain the following patches from Sun Microsystems:

• P118855-19 Patch Cluster

• IDR125308-01 IB Support Patch

• P124573-03 SRP Patch

If you will be installing Solaris to an EMC CLARiiON, you must obtain patch IDR125345-05 from Sun to perform the installation.

Installing Solaris

The Solaris customization script will configure an IP network using IP network multipathing (IPMP). All physical interfaces in the same partition will belong to the same multipathing group. The alias defined in VFrame will be used as the IPMP group name, so no spaces are allowed in this alias.

Note These installation instructions install only Solaris 10 update 2 for x86.

Install Solaris directly on your SAN using the OS installation media, along with the SRP driver disk.

To install Solaris, follow these steps:

Step 1 Obtain the SRP driver from the Sun website, which you will add at the appropriate time during install. Refer to http://www.sun.com/solaris/ for more information about the Solaris 10 OS.


See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 7 of 8 - Install OS and Applications window appears, as shown in Figure 11-19.


OL-12413-02



Step 3 Make sure you have keyboard access to the host before you begin the installation.

Step 4 Place the installation CD in your host and boot the server from the CD.

Figure 11-22 Media Boot the Solaris Server

Step 5 Install the Solaris 10 operating system.

a. Identify the console.

b. Install the drivers by selecting option 5 (Apply Driver Updates) when presented with the various types of installations, as shown in Figure 11-23.

Insert the SRP driver disk when prompted and type c to install from the CD.


OL-12413-02


Figure 11-23 Installing the Drivers

When the driver installation completes, you should see the text message “installing driver update in the miniroot,” which confirms that the SRP driver has loaded correctly. See the sample display in Figure 11-24.

Figure 11-24 Driver Update Complete


OL-12413-02


c. Reinsert the installation CD if necessary, press Ctrl-C to return to the Installation Type menu, and enter your choice at the prompt. Choose either option 3 for a desktop session or option 4 if you are using a serial console.

d. Perform the system configuration. Follow the instructions on a series of screens that guide you through the Solaris OS configuration process.

At the Network Connectivity dialog box, choose No, as shown in Figure 11-25. VFrame will configure networking in a later step.

Figure 11-25 Selecting the Network Connectivity

At the Type of Install dialog box, choose Custom Install.

During the installation you will be prompted to partition the disk as needed. It is important to partition the disk as follows:

– Make the first partition a PRI DOS partition of about 100 MB.

– Configure the second partition as type Solaris using the remaining free space.

After creating these partitions, you should see a screen similar to Figure 11-26.


OL-12413-02


Figure 11-26 PRI DOS and Solaris Partitions

e. Complete the installation.

On completion, the server reboots and displays the Solaris Welcome screen, as shown in Figure 11-27.

Figure 11-27 Installation Complete

Adding patches

After installing Solaris 10 Update 2, apply the following patches in this order:

1. P118855-19 Patch Cluster

2. IDR125308-01 IB Support Patch

3. P124573-03 SRP Patch


OL-12413-02


Updating Device Names for the Model Virtual Server

On x86 systems, you might need to update device names manually. If you are using Sun Storage, multiplexed I/O (MPxIO) might already have been enabled during the install so the names might already be updated. See the Solaris Fibre Channel Storage Configuration and Multipathing Support Guide for more information.

Manual modification of the model virtual server is required if either of the following is true:

• The initial Solaris installation is done with MPxIO disabled.

• The initial Solaris installation is unable to recognize the storage array.

In these cases, after MPxIO is configured and enabled, the device names used will change. In x86 systems, these circumstances require a manual change to some configurations such as vfstab.

You can determine if MPxIO is active for your installation by running the mount command. Inspect the device on which the root file system is mounted. If it looks like this:

/dev/dsk/c4t5006048ACCD1E290d0s0

where the numbers after the “t” and before the lowercase “d” correspond to the target WWPN, then MPxIO is not active.

If it looks like this:

/dev/dsk/c6t6006048000018791002653594D304541d0s0

Where the numbers after the “t” and before the lowercase “d” correspond to the LU logical ID, then MPxIO is active.

If manual modification of device names is not required—that is, MPxIO is active and the initial Solaris installation does recognize the storage array—then proceed to the “Configuring Storage (All Storage Types)” section on page 11-40. Otherwise, continue with the “Configuring Storage” section on page 11-37.

Configuring Storage

The following instructions describe how to activate MPxIO for the SRP devices on an EMC Symmetrix storage array. If you have a different storage array, the steps will be similar. However, you will need to update the scsi_vhci.conf file for your array. After copying the version of the file for Symmetrix, update the device-type-scsi-options-list for your array.

The vendor ID must be 8 characters (for example, EMC followed by 5 spaces, or HITACHI followed by one space), and the product ID can be up to 16 characters. For example:

device-type-scsi-options-list = “HITACHI DF600F”, “symetric-option”;

symmetric-option = 0x1000000;

This information is available from the SCSI inquiry data. You can view the vendor ID and product ID in either of the following ways:

• Through the Element Manager by choosing FibreChannel > SRP > LUs tab.

• From the Solaris host by running the inquiry command using the format application.

Configuring Storage for EMC Symmetrix Only

After the installation is finished you must enable MPxIO for Symmetrix. MPxIO for x86 Solaris 10 is enabled by default, but the scsi_vhci.conf does not have the proper EMC Symmetrix entries.


OL-12413-02


To configure storage for EMC Symmetrix, follow these steps:

Step 1 Find the logical ID for the boot LUN of the virtual server. You can find it on the virtual server’s storage assignment page:

a. In the VFrame GUI, click Virtual Server Groups in the navigation tree.

b. Click the name of the virtual server in the Virtual Server Groups summary window.

c. Click the virtual server Storage Assignments tab.

d. Click the logical unit to bring up the Logical Unit Properties page.

e. Copy the value of the logical ID from this page, for example:

6006048000018791002653594d304541

Step 2 Open the /boot/solaris/bootenv.rc file in a text editor.

a. Find the following line:

setprop bootpath /ib/ioc@5AD0000020FA0,5AD0000020FA0/disk@5006048accd1e290,0:a

b. Replace that line with the following line, where the numbers between the lowercase “g” and the colon (:) correspond to the logical ID that you copied in the previous step.

setprop bootpath /scsi_vhci/disk@g6006048000018791002653594d304541:a

c. Save and exit the file.

Step 3 Overwrite the /kernel/drv/scsi_vhci.conf file with the scsi_vhci.conf file from the VFrame Solaris Support package. Two things are changed in the new version of this file:

• The load-balance option is set to none.

• Entries are added to recognize the EMC Symmetrix storage array.

Step 4 Reboot the host:

# reboot -- -s

The system comes up in single user maintenance mode. Enter the root password to get a shell prompt.

Step 5 Enter the mount command and verify that / is mounted on the MPxIO device. The mountpoint looks similar to this:

/scsi_vhci/disk@g6006048000018791002653594d304541:a

The root file system will be read mounted only.

Step 6 Remount the root file system for read/write:

# mount -o remount,rw /devices/`mount | grep scsi | cut -c 6-56` /

Step 7 Rebuild the /dev/dsk and /dev/rdsk special device nodes:

# devfsadm -C

The MPxIO style device names should now appear in those directories.

Step 8 View the directories to verify:

# ls /dev/dsk


OL-12413-02


Step 9 Adjust the /etc/vfstab file to reflect the new device node names. For example, the old device names will look like this:

/dev/dsk/c4t5006048ACCD1E290d0s1 /dev/dsk/c4t5006048ACCD1E290d0s0 /dev/dsk/c4t5006048ACCD1E290d0s7

The new names should resemble this output:

/dev/dsk/c6t6006048000018791002653594D304541d0s0/dev/dsk/c6t6006048000018791002653594D304541d0s1/dev/dsk/c6t6006048000018791002653594D304541d0s7

Note The new names should match the entries in the /dev/dsk and /dev/rdsk directories.

The substitution can be done in a text editor. This example uses vi:

a. Open /etc/vfstab using vi:

vi /etc/vfstab

b. Enter the command in vi (substitute the values of your devices):

:%s/c4t5006048ACCD1E290/c6t6006048000018791002653594D304541/g

c. Verify all entries were correctly substituted. The entries are case sensitive and must match the entries in /dev/dsk and /dev/rdsk exactly. Enter the command to save and exit:

:wq

If you make a mistake, you can enter the command to exit without saving changes:

:q!

Step 10 Reboot the system:

# reboot

The system comes up in maintenance mode again with a warning about /etc/devices/mdi_scsi_vhci_cache and /etc/devices/mdi_ib_cache differing from the boot archive.

Step 11 Give the root password to get the maintenance prompt, and then run the following commands:

# svcadm clear system/boot-archive# exit

Press Ctrl-D and allow the system to boot all the way.

Step 12 Reboot once more.

# reboot

The system should come up without problems.


OL-12413-02


Configuring Storage (All Storage Types)

For all storage vendors, if you did not copy the scsi_vhci.conf file and MPxIO is already active for your disk, then one update is required.

To disable load balancing in MPxIO, follow these steps:

Step 1 Open the /kernel/drv/scsi_vhci.conf file with a file editor. Figure 11-28 shows an example scsi_vhci.conf file configured for Sun storage.

Step 2 Set the value of the load-balance option to none:

load-balance="none";

Figure 11-28 Example scsi_vhci.conf file

Step 3 Save your changes to this file.

Step 4 Perform a reconfiguration reboot of the host:

# touch /reconfigure# shutdown -g0 -y -i6

Preparing a File System for Customization Properties File

To prepare a file system for the customization properties file, follow these steps:

Step 1 Create a PCFS file system for the customization properties file.

We recommend creating the PCFS file system on the first partition configured in step 5 of the “Installing Solaris” section on page 11-32.

a. Find the root storage device by entering the mount command without any parameters. From the resulting list of mounted file systems, find the line that corresponds to the root device (/):

# mount.../ on /dev/dsk/c0t600C0FF0000000000033D25236442C01d0s0...

b. Create the PCFS file system using the mkfs command. Follow these rules when entering the command:


OL-12413-02


– Begin the argument with /dev/rdsk to specify a raw device.

– Replace the trailing “s0” characters in the device name with “p0:c” to specify the first partition of the boot device.

# mkfs -F pcfs /dev/rdsk/c0t600C0FF0000000000033D25236442C01d0p0:cConstruct a new FAT file system on /dev/rdsk/c0t600C0FF0000000000033D25236442C01d0p0:c: (y/n)? y

Step 2 Verify the new file system by mounting it. Follow these rules when entering the command:

• Begin the argument with /dev/dsk to specify a non-raw device.

• Replace the trailing “s0” characters with “p1” to specify the first partition of the boot device.

# mount -F pcfs /dev/dsk/c0t600C0FF0000000000033D25236442C01d0p1 /mnt

Configuring the mgmt Interface

Configure the mgmt interface so that VFrame Director can shut down the host.

To configure the mgmt interface, follow these steps:

Step 1 Find the device to configure:

# modload ibd# find /devices/ -name "*ibd*"/devices/pci...450@2/pci15b3,5a46@1/pci15b3,5a44@0/ibport@2,ffff,ipib:ibd2/devices/pci...450@2/pci15b3,5a46@1/pci15b3,5a44@0/ibport@1,ffff,ipib:ibd0/devices/pci...450@2/pci15b3,5a46@1/pci15b3,5a44@0/ibport@2,9999,ipib:ibd3/devices/pci...450@2/pci15b3,5a46@1/pci15b3,5a44@0/ibport@1,9999,ipib:ibd1

In this example, we choose the ibd1 device with the assumption that the VFrame Director’s mgmt interface is configured to use InfiniBand partition 99:99 for IPoIB traffic. The output contains two lines with IB partition 99:99, because there are two ports on the server’s HCA attached to an SFS switch. In this example, ibd1 corresponds to port number 1 of the HCA.

Step 2 Configure one of the physical interfaces associated with the mgmt partition:

# ifconfig ibd1 plumb# ifconfig ibd1 172.20.200.8/16 up

Enabling Root Logins over Secure Shell (ssh)

After the OS is installed, log in to the host and enable root logins over secure shell (ssh).

To enable root logins over ssh, follow these steps:

Step 1 Open the /etc/ssh/sshd_config file in an editor.

Step 2 Search for “PermitRootLogin”.

Step 3 Change the line to “PermitRootLogin yes”. See Figure 11-29.


OL-12413-02


Figure 11-29 Editing the /etc/sshd_config file

Step 4 Save and exit the file.

Step 5 Run the following command from the shell:

# svcadm refresh ssh

Installing and Configuring the Miniroot

To install and configure the miniroot, follow these steps:

Step 1 Install the VFrame Director miniroot by copying it from the VFrame Solaris Support package to the /boot directory:

# cp x86.miniroot-vfd /boot/x86.miniroot-vfd

Step 2 Add an entry in the VFrame Director miniroot to the GRUB configuration in /boot/grub/menu.lst.

To add the VFrame Director miniroot entry, first copy the configuration for the Solaris fail-safe option, and then update the title and module lines. It is important that the root and kernel lines are the same as in the fail-safe option:

# normaldefault=0title VFrame Customizationroot (hd0,1,a)kernel /boot/multiboot kernel/unix -smodule /boot/x86.miniroot-vfd

Step 3 Add a comment, as shown, to set the default boot option for when the customization scripts have finished. This entry becomes the default boot entry in GRUB after customization. This comment is read by the VFrame Director customization script. It must be in comment format because it is not used by the Solaris boot process.

Step 4 Save the file and exit the editor.

Configuring Default Boot Options

To update the default boot entry to use the VFrame customization, follow these steps:

Step 1 List the options as follows:

# bootadm list-menuThe location for the active GRUB menu is: /boot/grub/menu.lstdefault 0timeout 100 Solaris 10 6/06 eds_ibsrp_s10u2.4 X861 Solaris failsafe2 Solaris VFrame Customization

Step 2 Set the VFrame Customization as the default:

# bootadm set-menu default=2


OL-12413-02


Figure 11-30 shows a sample dialog.

Figure 11-30 Configuring the Miniroot—GRUB Configuration

Testing and Completing the Installation

To test and complete the installation in the VFrame GUI, Step 7 of 8 - Install OS and Applications window, follow these steps:

Step 1 Click the Ping Test button to verify that the VFrame Director can reach the virtual server.

VFrame powers down the virtual server before creating an image of the virtual server.





Step 8 of 8—Creating a Snapshot Image of a Model Virtual ServerUse this window to create a deployable image from the installation you performed in the “Step 7 of 8—Installing the Operating System on a Model Virtual Server” section on page 11-23.

The procedure for performing these tasks varies depending on whether you are creating a snapshot for a Linux server, a Windows server, or a Solaris server. These topics describe the following procedures:

• Creating the Snapshot Image—Linux and Solaris Servers, page 11-44

• Creating the Snapshot Image—Windows Servers, page 11-45


OL-12413-02


Creating the Snapshot Image—Linux and Solaris Servers

To create a snapshot image on a Linux or Solaris server, follow these steps:

Step 1 Complete Step 1 - 7 of the Virtual Server wizard. See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 8 of 8 - Create Snapshot Image window appears, as shown in Figure 11-31.


Step 2 Assign a name to the image in the Image Name field.

Step 3 Enter a description for the new image in the Description field.

The image will be a copy of the virtual server you have created, so you might want to describe the image based on the installed OS and applications.

Step 4 Click the Add button and enter any specific properties for the image in the Customization Properties field.

The Customization Properties field is a list of customizable properties that you want to be associated with an image. VFrame Director uses this field when deploying an image to a virtual server.

Virtual server properties override virtual server group properties with the same name, as well as overriding the default customizations that are applied to every virtual server.

For example, the following customization property overrides the default behavior and skips the customization step.

• Property: customize

• Value: false


OL-12413-02


Refer to the “Optional Reserved Properties” section on page 13-2 for more information on this field.


Step 6 Click the Create Image button to make a copy of the image that you have installed on the physical server. The physical server is powered-down by VFrame.

When the image copy is complete, see the “After Creating a Model Virtual Server” section on page 11-51.

Note After you create the first image in a virtual server group, you should recustomize that virtual server using the newly created image. This action is required so that the static address you configured manually will be made persistent by the customization script. The customization script allows the IP address of the virtual server to be written to the network configuration files so that the interface comes up on boot. Refer to the “Viewing and Managing Master Images” section on page 13-5.

Step 7 Click the Skip button to copy the image at a later time.

Step 8 Click the Cancel button to return to the Virtual Server summary window without saving changes.

Creating the Snapshot Image—Windows Servers

To create a snapshot image on a Windows server, perform these tasks:

• Installing and Running the Sysprep Application, page 11-45

• Creating the Templates, page 11-46

• Customizing the Location of the Windows Template in VFrame, page 11-49

• Completing the Image Creation, page 11-49

Installing and Running the Sysprep Application

Note Do not install any software that is dependent on the computer’s Security IDs (SIDs) until you have finished deploying the image to that virtual server, because the combination of running Sysprep and deploying the image gives each new virtual server a unique SID.

To install and run the Sysprep application, follow these steps:

Step 1 Download the version 1.1 software from Microsoft at this location:

http://www.microsoft.com/windows2000/downloads/tools/sysprep/default.asp

http://support.microsoft.com/kb/838080/

Step 2 Save the sysprep program to a temporary file. For example, C:\Temp.

Step 3 Navigate to the temporary location and double-click the icon for the application.

Step 4 Click the Run button when the security warning appears.

Step 5 Extract the files to the temporary folder you selected, and then click Ok.

Step 6 Click Ok when the extraction is complete.


OL-12413-02


Several folders appear.

Step 7 Double-click the Tools folder.

Step 8 Copy the following files to the C:\sysprep folder of the Windows physical server:

• setupcl.exe

• sysprep.exe

This operation ensures that the directory on which Sysprep is installed will not be removed after the customization procedure.

Note The VFrame Director is case-sensitive. The sysprep directory must be entered in lowercase. If you have the directory $oem$, make sure that this is also entered in lowercase. If you do not have the oem directory, the VFrame Director will add it for you.

Step 9 Run sysprep.exe.

Sysprep shuts down the physical server. Use the -forceshutdown parameter with Sysprep if the computer does not shut down.

Creating the Templates

The VFrame Director allows the creation of multiple customization templates to configure hostname, IP addresses, and other options.

For Windows 2000 image customization, create a sysprep.inf file as a template for the virtual server group. Generally, the Sysprep.inf answer file is used by the Sysprep application to automate the MiniSetup process. In this case, the VFrame Director uses the sysprep.inf file to define properties for the virtual server. Refer to the Windows documentation from Microsoft Corporation for format requirements for the answer file.

To create the template, follow these steps:

Step 1 Create a directory on the VFrame Director to store your templates.

For example, use the path /usr/local/topspin/vframe/image/depot/templates.

Step 2 Create a sysprep.inf template for each Windows virtual server group.

The VFrame Director replaces VFrame-defined tags in the template with the specific properties for a virtual server group, such as hostname and IP address, as shown in the following example:

[Unattended] OemSkipEula=Yes DriverSigningPolicy=IgnoreInstallFilesPath=\sysprep EMSSkupUnattendedProcessing=1

[GuiUnattended] AdminPassword=AdministratorPassword OemSkipRegional=1 OemSkipWelcome=1 TimeZone=020

[UserData]FullName=”User Name” OrgName=”Company Name”


OL-12413-02


ComputerName="[[hostname]]" ProductID="EXAMP-LEPRO-DUCTI-D1234-56789" [LicenseFilePrintData] AutoUsers="10" AutoMode="PerServer"

[Identification] joinworkgroup=workgroup

[Networking]

Refer to Microsoft documentation, such as Microsoft Windows 2000 Guide to Unattended Setup for more information.

[unattended]

• OemSkipEula=Yes

The Yes setting implies that the person performing the installation has read and agreed to the contents of the License Agreement included with the Sysprep product.

• DriverSigningPolicy=Ignore

Enter Ignore so that an unattended setup continues, even if a driver is not signed.

• InstallFilesPath=\sysprep

The InstallFilesPath is case-sensitive. This entry is not required, and will be added by VFrame Director, if not specified. Do not define this field unless you have a specific requirements to do so.

• EMSSkipUnattendedProcessing=1

Add this line to avoid the EMS Connection Deleted dialog box when deploying Windows 2003 server images as servers with console redirection enabled.

[GuiUnattended]

• AdminPassword= AdministratorPassword

Sets up the Administrator account password.

• OemSkipRegional=1

Set to 1 to allow the unattended setup to skip the Regional Options page in GUI-mode Setup and Mini-Setup.

• OemSkipWelcome=1

Set to 1 to allow the unattended setup to skip displaying the Welcome page in GUI-mode Setup and Mini-Setup.

• TimeZone=020

Specifies the time zone where the computer is located. If the key is not present, the user is prompted to select a time zone. For a list of valid time zone indices, see the Windows sysprep documentation at http://www.microsoft.com/technet/prodtechnol/windows2000pro/deploy/unattend/sp1ch01.mspx.

The following list shows some commonly used time zone indexes:

– 004 = Pacific

– 101 = Mountain (U.S. and Canada)

– 020 = Central (U.S. and Canada)

– 035 = Eastern (U.S. and Canada)

– 110 = W. Europe


OL-12413-02


– 095 = Central Europe

– 210 = China

[UserData]

• FullName=“UserName”

Specifies the user’s full name. If the key is empty or missing, the user is prompted to enter a name. This parameter is used to ensure that the setup mode is completely unattended.

• OrgName=“CompanyName”

This entry specifies an organization’s name.

• computername=“hostname”

This entry specifies the computer name. If the ComputerName key is empty or missing, the user is prompted to enter a computer name. If the value is *, Setup generates a random computer name based on the organization name specified.

• ProductID=“EXAMP-LEPRO-DUCTI-D1234-56789”

This entry specifies the Microsoft Product Identification (Product ID) number.

[LicenseFilePrintData]

• AutoUsers= “number of client licenses <greater than 5>”

This entry specifies the number of client licenses purchased for the server being installed. This key is only valid if AutoMode = PerServer

The number specified must be greater than five, otherwise, unattended setup mode fails and the user is prompted to choose a value through the user interface.

• AutoMode= “PerServer”

This entry specifies whether a Windows 2000 server is to be installed in a per-seat or a per-server license mode. If AutoMode = PerServer, the AutoUsers key must also be specified.

[Identification]

• joinworkgroup=NameOfWorkgroup

This entry specifies the name of the workgroup in which the computer participates. You can specify either this key or the JoinDomain key, but you cannot specify both. For example: JoinWorkgroup = MYUSERGROUP

Step 3 Save the file in the Template directory that you created.

You can save the template using any unique name, such as Windows2000.inf. Make sure that you note the exact path and name so that you can enter it into the Customization field for the virtual server group. See the “Customizing the Location of the Windows Template in VFrame” section on page 11-49.

Step 4 Create a new template for each new Windows virtual server group, using a new file name.

For example, if you are creating a new virtual server group for Windows 2003, you would need to create a new template specific to that group.


OL-12413-02


Customizing the Location of the Windows Template in VFrame

To customize the location of the Windows template for the virtual server group in VFrame, follow these steps:

Step 1 Expand Virtual Server Groups in the VFrame navigation tree.

Step 2 Click the Windows virtual server group name.

Step 3 Click the General tab.

The Virtual Server Group Properties window appears. In the Customization Properties field, the mgmt.alias and properties.destination parameters should already be set, as described in the “Adding Customization Parameters” section on page 11-30.

Step 4 Click the Add button.

The Add Customization Property dialog box appears.

Step 5 In the Property field, enter customize.

Step 6 In the Value field, enter the path to the directory in which you saved the sysprep.inf file in the “Creating the Templates” section on page 11-46. For example, /usr/local/topspin/vframe/image/depot/templates/Windows2000.inf

Step 7 Click the OK button.


Step 8 To return to the Virtual Server wizard at the point you stopped, click the Virtual Servers tab, and then click the name of the virtual server that you are creating.

Completing the Image Creation

To complete the creation of the Windows image, follow these steps:


See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Step 8 of 8 - Create Snapshot Image window appears.


OL-12413-02



Step 2 Assign a name to the image in the Image Name field.

Step 3 Enter a description for the new image in the Description field.

The image will be a copy of the virtual server you have created, so you may want to describe the image based on the installed OS and applications.

Step 4 Leave the Customization Properties field blank.

Refer to the “Optional Reserved Properties” section on page 13-2 for more information on this field.


Step 6 Click the Create Image button to take a copy of the image that you have installed to the physical server. The physical server is powered down by VFrame.

When the image copy is complete, see the “After Creating a Model Virtual Server” section on page 11-51.

Note After you create the first image in a virtual server group, you will either recustomize the image on the model server or redeploy that image back to the virtual server from which you created it. This action is required so that the static address you configured manually will be updated to use the customization script instead. The customization script allows the address of the physical device to take on the address of any virtual server to which it is assigned. Refer to the “Viewing and Managing Master Images” section on page 13-5.


OL-12413-02

Chapter 11 Creating Virtual Server Groups Adding One Virtual Server to a Virtual Server Group

Step 7 Click the Skip button to copy the image at a later time.


After Creating a Model Virtual ServerOnce the virtual server creation is complete you can create additional virtual servers onto which to deploy the new virtual server image.

After creating a model virtual server, follow these steps:

Step 1 Complete Step 1 - 8 of the Virtual Server wizard.

See the “Step 1 of 8—Configuring General Properties of a Model Virtual Server” section on page 11-16. The Virtual Server Creation Complete window appears.

This window indicates that the new virtual server has been created, but does not necessarily mean that the process of creating an image of that virtual server is complete.

Figure 11-33 Virtual Server Process Complete

Step 2 Click the Back to Summary button to view the process of the image creation.

The status of the image must be “Ready” before you can use the new image. Refer to Figure 13-2 on page 13-5.

Step 3 Click the Create Another button to begin the Virtual Server wizard again.

Once a virtual server is created with a new image, you can create additional virtual servers from existing image and deploy the new image to those virtual servers. Refer to the “Adding One Virtual Server to a Virtual Server Group” section on page 11-51 or “Adding Multiple Virtual Servers to a Virtual Server Group” section on page 11-58.

Adding One Virtual Server to a Virtual Server GroupThese topics describe the windows and steps required to add one virtual server at a time to a virtual server group:

• Starting the Wizard for Adding One Virtual Server to a Virtual Server Group, page 11-52

• Step 1 of 5—Configuring General Properties of One Virtual Server, page 11-53

• Step 2 of 5—Confirming Network Interfaces for One Virtual Server, page 11-54


OL-12413-02


• Step 3 of 5—Configuring Fibre Channel World Wide Names for One Virtual Server, page 11-55

• Step 4 of 5—Configuring Dedicated Storage for One Virtual Server, page 11-56

• Step 5 of 5—Deploying the Image on One Virtual Server, page 11-57

To add multiple virtual servers at a time, see the “Adding Multiple Virtual Servers to a Virtual Server Group” section on page 11-58.

Starting the Wizard for Adding One Virtual Server to a Virtual Server GroupThis procedure assumes that you have already created a model virtual server for the virtual server group. If not, go back and add one as described in “Adding a Model Virtual Server to a Virtual Server Group” section on page 11-15.

To add one virtual server to a virtual server group that already has a model virtual server defined, begin by starting the virtual server wizard. To start the wizard, follow these steps:

Step 1 Start the virtual server wizard in one of the following ways:

• After adding a virtual server to a virtual server group, click Create Another on the Virtual Server Creation Complete window. The wizard Introduction window appears, as shown in Figure 11-34.

• Alternatively, if you previously created a virtual server group and have added virtual servers:

– Click the virtual server group in the Virtual Server Groups summary window. The Virtual Servers summary window displays. See the “Viewing and Using Virtual Server Group Summary Information” section on page 12-2.

– From the Select an Action drop-down menu, choose Add Virtual Server(s). The wizard Introduction window appears.

Figure 11-34 Introduction to Add Virtual Server to a Virtual Server Group

Step 2 Click the (1 - 32) additional virtual servers from an existing image radio button, and enter 1 in the dialog box.

You can enter a number greater than 1 to add more than one virtual server in a bulk operation. To do so, follow the instructions in “Adding Multiple Virtual Servers to a Virtual Server Group” section on page 11-58.


OL-12413-02


Step 3 Click the Next button and proceed to the “Step 1 of 5—Configuring General Properties of One Virtual Server” section on page 11-53.

Step 4 Click the Cancel button to exit the Virtual Server wizard.

Step 1 of 5—Configuring General Properties of One Virtual ServerTo configure the properties on one virtual server, follow these steps:

Step 1 Go to the Virtual Server Wizard Introduction window and specify that you want to add one virtual server to the virtual server group, as described in the “Starting the Wizard for Adding One Virtual Server to a Virtual Server Group” section on page 11-52, and then click Next.

The Step 1 of 5 - General Virtual Server Properties window appears, as shown in Figure 11-35.

Figure 11-35 Add Virtual Server for Server with Existing Image—Step 1

Step 2 Enter a name for the virtual server in the Host Name field. This text is a short description that will assist you in selecting the host from a list.

Note If you are creating a virtual server to be associated with a VFrame Director host, the hostname must match the host name of the physical server.

Step 3 Enter a description for the virtual server in the Description field. This text is a longer description of the virtual server.

Step 4 Click the Add button to enter customizations for the Virtual Sever in the Customization Properties field. Refer to the “Understanding Image Manipulation and Customization” section on page 13-1.

Use this field to adjust properties that are set by the standard customization script. Customizations for the virtual server override the virtual server group level properties with the same name.


OL-12413-02


Step 5 Click the Next button.

The Step 2 of 5 - Virtual Server Network Interfaces window opens. See the “Step 2 of 5—Confirming Network Interfaces for One Virtual Server” section on page 11-54.

Step 6 Click the Cancel button to cancel the virtual server creation, discarding all changes, and return you to the virtual servers Summary screen.

Step 2 of 5—Confirming Network Interfaces for One Virtual ServerTo confirm network interfaces for one additional virtual server, follow these steps:

Step 1 Complete Step 1 of the Virtual Server wizard.

See the “Step 1 of 5—Configuring General Properties of One Virtual Server” section on page 11-53. The Step 2 of 5 - Virtual Server Network Interfaces window appears.

Figure 11-36 Add Virtual Server to a Virtual Server Group with Existing Image—Step 2

Step 2 View the name of the network interface in the Name field and its alias in the Alias field.

Step 3 View or edit the IP address of the network interface in the IP Address field.

Note If you change the IP address that is automatically assigned to the virtual server, verify that the new address is still within the range that you specified for the virtual server group. For example, if you specified a range of 10, you will be able to allocate only 9 addresses above the base.

Step 4 Click the Back button to return to the previous window. Any changes you made to the current window are remembered and will still be there when you return to this screen.

Step 5 Click the Next button. The Step 3 of 5 Virtual Server FC WWNs window opens. See the “Step 3 of 5—Configuring Fibre Channel World Wide Names for One Virtual Server” section on page 11-55.

Step 6 Click the Cancel button to return to the previous window without saving changes.


OL-12413-02


Step 3 of 5—Configuring Fibre Channel World Wide Names for One Virtual Server

To configure Fibre Channel WWNs, follow these steps:

Step 1 Complete steps 1 and 2 of the Virtual Server wizard (begin with the “Step 1 of 5—Configuring General Properties of One Virtual Server” section on page 11-53). The Step 3 of 5 - Virtual Server FC WWNs window appears.


Step 2 View the number of the HCA in the Virtual Adapter field. If two adapters were installed, they would be numbered 0 and 1.

Step 3 View the virtual Fibre Channel World Wide Node Names (WWNNs) that have been generated for the new virtual server in the WWNNs field.

• If you are using access control on the storage array, configure the array to allow storage access to the displayed WWNs.

• If you are using zoning on your SAN, note this WWNN. You will need to add this identifier to your zone configuration. Refer to the Cisco VFrame InfiniBand Third-Party Integration Guide for Fibre Channel zone configuration samples.

These WWNNs are applied to a physical server when it is assigned to this virtual server.

Step 4 View the virtual World Wide Port Names (WWPNs) and World Wide Node Names (WWNNs) for the fibre channel gateway in the WWNN and WWPN fields.

If you are using zoning on your SAN, note the WWPN and WWNN values. You will need to add this identifier to your zone configuration. Refer to the Cisco VFrame InfiniBand Third-Party Integration Guide for Fibre Channel zone configuration samples.

These WWPNs and WWNNs are applied to a physical server when it is assigned to this virtual server.

Step 5 View an existing group of fibre channel port groups in the Port Group field. Click the name of an existing group to view or edit the properties of the port group, such as adding more physical gateway ports. See the “Viewing and Editing Port Pool Details” section on page 9-14.


OL-12413-02



Step 7 Click the Next button. The Step 4 of 5 Virtual Server Storage window opens. See the “Step 4 of 5—Configuring Dedicated Storage for One Virtual Server” section on page 11-56.


Step 4 of 5—Configuring Dedicated Storage for One Virtual ServerTo configure dedicated storage, follow these steps:

Step 1 Complete steps 1 through 3 of the Virtual Server wizard (begin with the “Step 1 of 5—Configuring General Group Properties” section on page 11-2). The Step 4of 5 - Virtual Server Storage window appears.


In the “Allow selection of storage assigned to another virtual server” field, the No button is selected by default. This default selection prevents you from allocating the same dedicated storage to this virtual server as has already been assigned to another virtual server.

Use caution if you choose to override this protection.

Step 2 View the WWPN of any previously discovered storage target in the Name field. View the Logical ID of the LUN under the storage target.

Step 3 View the current status of storage in the State field. The possible states are described in Table 5-3 on page 5-7.

Step 4 View the assigned description of any storage in the Description field.


Step 6 Click the Assigned check box beside the LUN you want to dedicate to a virtual server. The Device ID field appears.



OL-12413-02


You cannot check boxes in this column that are dimmed. These LUNs have already been assigned to other virtual servers. You can override this restriction in the “Allow collection of storage assigned to another virtual server field” by clicking the Yes button as described earlier in this procedure.


Device ID 0 indicates the boot device. View the order that has been assigned to any shared storage in the Device ID field. The VFrame Director uses SRP logical unit (LU) remapping (SRP LU ID) to achieve the desired order of LUs.

The Device ID field is used in both shared and dedicated storage to configure the order in which a disk will be used. The device IDs must be contiguous starting from 0.

Note the following information about device IDs:

• Span dedicated and shared storage.

• Must be numbered 0 - (n - 1), where n is the number of devices. For example, 3 disks would be numbered as 0, 1, 2.



Step 8 Click the radio button in the Alternative Boot field if the LUN is to be designated as an alternate boot LUN.

The LUN designated as an alternate boot LUN must have the same logical LUN ID as the primary boot LUN and must be accessed through a different target. VFrame enforces these rules by dimming the Alternate Boot field radio buttons for all target/LUN pairs except those that comply with the rule.


Step 9 Click the Back button to return to the previous window.

Step 10 Click the Next button. The Step 5 of 5 - Deploy Image window opens. See the “Step 5 of 5—Deploying the Image on One Virtual Server” section on page 11-57.


Step 5 of 5—Deploying the Image on One Virtual ServerTo deploy an image to one virtual server, follow these steps:

Step 1 Complete Steps 1 - 4 of the Virtual Server wizard (begin with the “Step 1 of 5—Configuring General Group Properties” section on page 11-2). The Step 5 of 5 - Deploy Image window appears.


OL-12413-02

Chapter 11 Creating Virtual Server Groups Adding Multiple Virtual Servers to a Virtual Server Group


Step 2 View the list of all existing images in the Name field.

Step 3 View the description of all existing images in the Description field.

Step 4 View the current status of image in the Status field.


Step 6 Click the radio button next to an existing image and click the Deploy Image button to select an image for deployment to the previously selected LUN.

You can watch the status of the image deployment in this window in the Jobs window (see the “Filtering and Viewing the Jobs Log” section on page 8-13).

Step 7 Click the Skip button to complete the virtual server creation without deploying an image onto storage. You can return later to deploy an image for this virtual server. Refer to the “Deploying an Image” section on page 13-8.


Adding Multiple Virtual Servers to a Virtual Server GroupThese topics describe how to add multiple virtual servers to a virtual server group, assuming the virtual server group has at least one virtual server with an image already installed.

Unlike the procedure for adding virtual servers one at a time, you will not be able to specify IP addresses for the virtual servers you are adding. Instead, VFrame Director will choose an IP address from the range specified during virtual server group creation. You will, however, be able to change the IP addresses after the virtual servers are created using the virtual servers Network tab. See the “Viewing and Editing Network Interfaces of a Virtual Server” section on page 12-76.

Similarly, you will not be able to identify specific LUNs for dedicated storage for each virtual server. Instead, you will specify a storage pool from which VFrame Director will allocate dedicated storage.


OL-12413-02


This section contains the following topics:

• Starting the Wizard for Adding Multiple Virtual Servers, page 11-59

• Step 1 of 3—Configuring General Properties for Multiple Virtual Servers, page 11-60

• Step 2 of 3—Configuring Storage for Multiple Virtual Servers, page 11-61

• Step 3 of 3—Deploying an Image to Multiple Virtual Servers, page 11-63

Starting the Wizard for Adding Multiple Virtual ServersTo specify the number of virtual servers you want to add to a virtual server group, follow these steps:

Step 1 Start the virtual server wizard in one of the following ways:

• After adding a virtual server to a virtual server group, click Create Another in the Virtual Server Creation Complete window. The wizard Introduction window appears, as shown in Figure 11-40.

• Expand Virtual Server Groups in the navigation tree, and then click the name of the virtual server group to which you want to add virtual servers. The Virtual Servers Summary screen displays.

From the Select an Action pull-down menu, choose Add Virtual Server(s).

The Add Virtual Server(s) Introduction screen displays as shown in Figure 11-40.

Figure 11-40 Add Virtual Servers Introduction Screen; Adding Multiple Virtual Servers

Step 2 Click the (1 - 32) additional virtual servers from an existing image radio button.

Step 3 Enter the number of virtual servers you want to add in the “(1 - 32) additional virtual servers from an existing image” dialog box.

The procedure described here assumes you enter a number in the range 2 to 32. If you enter 1 in this field, follow the procedure described in the “Adding One Virtual Server to a Virtual Server Group” section on page 11-51.

Step 4 To proceed to the next stage in adding multiple virtual servers, click Next and follow the steps described in the “Step 1 of 3—Configuring General Properties for Multiple Virtual Servers” section on page 11-60

Step 5 To cancel your input and exit the virtual server wizard, click Cancel.


OL-12413-02


Step 1 of 3—Configuring General Properties for Multiple Virtual ServersTo specify general properties of the virtual servers you are adding to the virtual server group, follow these steps:

Step 1 Go to the Virtual Server Wizard Introduction window and specify that you want to add multiple virtual servers to the virtual server group, as described in the “Starting the Wizard for Adding Multiple Virtual Servers” section on page 11-59, and click Next.

The Step 1 of 3—General Virtual Server Properties window appears, as shown in Figure 11-41.

Figure 11-41 Add Multiple Virtual Servers for Server With Existing Image—Step 1

Step 2 In the Starting Index field, enter a number to be used for the first index number in the Hostname field.

VFrame Director automatically increments this number to provide unique virtual server names. You also have the option to include this number in the Description field to provide unique virtual server descriptions.

Step 3 In the Hostname field, enter a name for the virtual server. This text is a short description that will assist you in selecting the host from a list. Enter {i} within the name string to insert an index number that distinguishes virtual servers by providing unique names, For example, if you add three virtual servers, enter 1 in the Starting Index field, and Region{i}Sales in the Hostname field, then the three added virtual servers will be named Region1Sales, Region2Sales, and Region3Sales.

If you omit the {i} designation, VFrame adds the index number to the end of the host name.

For example, if you add three virtual servers, enter 1 in the Starting Index field, and Sales Server in the Hostname field, then the three added virtual servers are named Sales Server1, Sales Server2, and Sales Server3.

Step 4 In the Description field, enter a description for the virtual server. This text is a longer description of the virtual server. You can optionally include the {i} string to create unique descriptions.

Step 5 Click the Add button to enter customizations for the virtual server in the Customization Properties field. Refer to the “Understanding Image Manipulation and Customization” section on page 13-1.


OL-12413-02


Use this field to adjust properties that are set by the standard customization script. Customizations for the virtual server override virtual server group level properties with the same name.


Step 7 Click the Next button to proceed to the next stage. See the “Step 2 of 3—Configuring Storage for Multiple Virtual Servers” section on page 11-61.

Step 8 Click the Cancel button to cancel the virtual server creation and return you to the virtual servers summary page.

Step 2 of 3—Configuring Storage for Multiple Virtual ServersUse the Step 2 of 3—Virtual Server Storage Window to instruct VFrame on how to select storage for each of the virtual servers you are creating. Add one row to this window for each device to be allocated to each virtual server. During this procedure, you assign one device ID at a time and select the storage pool from which VFrame chooses the target LUN pair for that device ID. See the “Viewing Storage Pool Assets” section on page 9-46 for details about creating storage pools.

To assign storage devices to multiple virtual servers, follow these steps:

Step 1 Complete the steps described in the “Starting the Wizard for Adding Multiple Virtual Servers” section on page 11-59 and in the “Step 1 of 3—Configuring General Properties for Multiple Virtual Servers” section on page 11-60.

The Step 2 of 3—Virtual Server Storage window displays as shown in Figure 11-42.


Step 2 Click Add Device.

A revised Step 2 of 3—Virtual Server Storage window displays as shown in Figure 11-43.


OL-12413-02


Figure 11-43 Add Multiple Virtual Servers for Server With Existing Image—Step 2 (Revised)

Step 3 In the Device ID field, enter the order in which the storage will be used. The Device ID refers to the order that the storage will be used.

Set the Device ID to 0 to indicates the boot device. View the order that has been assigned to any shared storage in the Device ID field. The VFrame Director uses SRP logical unit (LU) remapping (SRP LU ID) to achieve the desired order of LUs.

The Device ID field is used in both shared and dedicated storage to configure the order in which a disk will be used. The device IDs must be contiguous starting from 0.

Device IDs have the following properties:

• They span dedicated and shared storage.

• They must be numbered 0 - (n - 1), where n is the number of devices. For example, three disks would be numbered as 0, 1, 2.



Step 4 Use the Multipath ID field to specify multiple paths to the same LUN. Different device IDs with the same multipath ID refer to the same LUN through a different target.


Step 5 If the LUN is to be designated as an alternate boot LUN, set up boot LUN multipathing by checking the Alternative Boot radio button on the device with the same multipath ID as the device 0.

VFrame assigns the primary boot LUN and the alternative boot LUN with the same logical LUN ID through different targets.


Note You can assign only one boot LUN for a maximum of two paths for booting. You can assign additional paths to the same LUN through a combination of the Multipath ID field and multipathing software, but the additional paths can be used only for data access and not for booting.

Step 6 From the Storage Pool drop-down menu, choose the storage pool from which to obtain the target LUN pair for the specified storage device.

Step 7 Click Add Device to specify another device ID.


OL-12413-02


Another row appears in the storage table. Repeat steps 3 through 6 for the additional device ID.


Step 9 Click the Next button to proceed to the next step. The Step 3 of 3 - Deploy Image window opens. See the “Step 3 of 3—Deploying an Image to Multiple Virtual Servers” section on page 11-63.


Step 3 of 3—Deploying an Image to Multiple Virtual ServersTo deploy an image to multiple servers, follow these steps:

Step 1 Complete previous steps of the Virtual Server wizard:

• Starting the Wizard for Adding Multiple Virtual Servers, page 11-59.

• Step 1 of 3—Configuring General Properties for Multiple Virtual Servers, page 11-60.

• Step 2 of 3—Configuring Storage for Multiple Virtual Servers, page 11-61.

The Step 3 of 3 - Deploy Image window displays, as shown in Figure 11-44.


Step 2 View the list of all existing images in the Name field.

Step 3 View the description of all existing images in the Description field.

Step 4 View the current status of each image in the Status field.



Step 7 Click the radio button next to an existing image and click the Deploy Image button to select an image for deployment to the previously selected LUN.


OL-12413-02


You can watch the status of the image deployment in this window in the Jobs window. See the “Filtering and Viewing the Jobs Log” section on page 8-13, for details.

Click the Skip button to complete the virtual server creation without deploying an image onto storage. You can come back later to deploy an image for these virtual servers as described in the “Deploying an Image” section on page 13-8.

The Virtual Server Creation Complete window displays as shown in Figure 11-45.

Figure 11-45 Virtual Server Creation Complete Window

Step 8 Click the Back to Summary button to return to the Virtual Server Groups Summary window.

Step 9 Click the Create Additional Virtual Server(s) button to return to the Add Virtual Server Introduction screen.


OL-12413-02

document11

Documents

virtual server group

virtual server group

new virtual server group

virtual server group

virtual server group

virtual server group

virtual server groupscreating

model virtual server