Connect the installation server's second interface, NIC1, to the Ethernet switch connecting the NIC0 interfaces of the nodes.

Log in to the installation server as superuser.

Create the file /etc/hostname.cluster-network-interface-name (hme0 in this procedure) on the installation server:

# touch /etc/hostname.hme0

Edit the /etc/hostname.hme0 file to add the host name of the installation server, for example, installation-server-cluster.

Choose an IP address for the network interface that is connected to the cluster, for example, 10.250.1.100.

Edit the /etc/hosts file on the installation server to add the IP address that you chose in Step 5.

Set the netmask of the cluster network in the /etc/netmasks file:

10.250.1.0     255.255.255.0

Download the LDoms software from the Sun Software Download Center from the following website: http://www.sun.com/download

Download the Solaris 10 11/06 OS SPARC or newer from the following website: http://www.sun.com/software/solaris

Download the following Solaris patches from SunSolve at: http://sunsolve.sun.com

Download the Sun system firmware version 6.4.4 or newer from SunSolve at: http://sunsolve.sun.com

Copy the LDoms software package to the machine where it will be installed and unpack the software.

On the Netra HA Suite installation server, copy the software as follows:

# rcp LDoms_Manager-1_0-RR.zip 10.130.1.10:/var/tmp/
# rcp 118833-36.zip 10.130.1.10:/var/tmp/
# rcp 125043-01.zip 10.130.1.10:/var/tmp/
# rcp 124921-02.zip 10.130.1.10:/var/tmp/

On the console of the systems that will run LDoms (for example, on 10.130.1.10 and 10.130.1.20), unzip the software as follows:

# cd /var/tmp
# unzip LDoms_Manager-1_0-RR.zip
# unzip 118833-36.zip
# unzip 125043-01.zip
# unzip 124921-02.zip

Patch the Solaris to include the latest Logical Domains updates.

• Login on the console and apply the patches in single-user mode as follows:

  
  

  # init S # cd /var/tmp/ # patchadd 118833-36 # touch /reconfigure # shutdown -i6 -g0 -y

  
  

• Install patches for virtual console and LDoms drivers and utilities when the system has rebooted:

  
  

  # cd /var/tmp/ # patchadd 125043-01 # patchadd 124921-02

  
  

Ensure that the system firmware version on your system is up to date. LDoms 1.0 software requires system firmware 6.4.4 or newer for Netra CP3060 blades or Netra T2000 servers.

To check which firmware is present on your system, connect to the system controller (ALOM) on your Netra CP3060 or Netra T2000 server and run the following command:

sc> showhost
System Firmware 6.4.4 Netra CP3060 2007/04/20 10:15
Host flash versions:
Hypervisor 1.4.1 2007/04/02 16:37 
OBP 4.26.1 2007/04/02 16:25 
Netra[TM] CP3060 POST 4.26.0 2007/03/26 16:47
sc>

The instructions, binary files, and tools needed to perform a firmware upgrade are located in the patch package, as shown in the following code example.

# rcp 126402-01.zip 10.130.1.10:/var/tmp
# cd /var/tmp
# unzip 126402-01.zip
# more /var/tmp/126402-01/sysfwdownload.README

Install the LDoms Manager software.

# cd /var/tmp/LDoms_Manager-1_0-RR
# ./Install/install-ldm 

When prompted, select the recommended settings for the Solaris Security Toolkit.

Reboot the system to activate the patches and to start the LDoms Manager software.

# shutdown -i6 -g0 -y

After the reboot, LDoms will be active with one logical domain named ’primary’ running on the system. This domain is the control domain.

The control domain can be accessed through the serial console, or by using Secure Shell. All other ports have been disabled by the Solaris Security Toolkit to ensure that the control domain is as secure as possible.

Log in on the control domain and set the path to access the LDoms Manager command line tool:

# ssh 10.130.1.10
# export PATH=/opt/SUNWldm/bin:$PATH

Set up virtual services in control domain.

These services provide console, disk, and network access for the guest domains.

1. For the virtual disk server:

   
   

   # ldm add-vdiskserver primary-vds0 primary

   
   

2. For the virtual console server:

   
   

   # ldm add-vconscon port-range=5000-5100 primary-vcc0 primary

   
   

3. Configure two virtual network switches to enable CGTP:

   
   

   # ldm add-vswitch net-dev=e1000g0 primary-vsw0 primary # ldm add-vswitch net-dev=e1000g1 primary-vsw1 primary

   
   

4. Set the resources available to the control domain to limit the resources used by the control domain so that they are free to be used by the guest domains.

   
   

   # ldm set-mau 2 primary # ldm set-vcpu 8 primary # ldm set-memory 2G primary

   
   

5. Save the LDoms configuration:

   
   

   # ldm add-config nhas

   
   

6. Reboot the system:

   
   

   # shutdown -i6 -g0 -y

   
   

7. After rebooting the system, start up the virtual console service:

   
   

   # svcadm enable vntsd

   
   

Create a guest domain named men15. This domain will be a master-eligible node in the Netra HA Suite cluster.

# ldm create men15
# ldm set-mau 2 men15
# ldm set-vcpu 8 men15
# ldm set-memory 2G men15
# ldm ldm add-vnet vnet0 primary-vsw0 men15
# ldm add-vnet vnet1 primary-vsw1 men15

Create the disk image that will be used as the virtual disk for the master-eligible node.

The virtual disk is mapped to normal file in the control domain.

# mkfile 16G /test1/bootdisk_men15.img
# ldm add-vdiskserverdevice /test1/bootdisk_men15.img vol1@primary-vds0
# ldm add-vdisk vdisk1 vol1@primary-vds0 men15
# ldm set-variable auto-boot\?=false men15
# ldm bind-domain men15

Create a guest domain named nmen35. This domain will be a non-master eligible node.

# ldm create nmen35
# ldm set-mau 2 nmen35
# ldm set-vcpu 8 nmen35
# ldm set-memory 2G nmen35
# ldm add-vnet vnet0 primary-vsw0 nmen35
# ldm add-vnet vnet1 primary-vsw1 nmen35
# ldm set-variable auto-boot\?=false nmen35
# ldm bind-domain nmen35

Create the virtual disk for the node.

Note that this non-master eligible node will be a dataless node. To create a diskless node instead of a dataless node, do not perform the following tasks:

# mkfile 4G /test1/bootdisk_nmen35.img 
# ldm add-vdiskserverdevice /test1/bootdisk_nmen35.img vol2@primary-vds0
# ldm add-vdisk vdisk1 vol2@primary-vds0 nmen35

Start the guest domains:

# ldm start men15
# ldm start nmen35

The virtual console of the guest domains are only accessible through the control domain.

Use the following commands to access the consoles of the guest domains from outside the control domain:

men15:   ssh 10.130.1.10 telnet localhost 5000
nmen35:  ssh 10.130.1.10 telnet localhost 5001

The nodes should now be at the ok-prompt in Open Boot PROM.

Repeat and to set up the second Netra CP3060 or Netra T2000 system so a four-node cluster is ready to install Netra HA Suite.

In cluster_definition.conf, use vnet0 and vnet1 as network interfaces for all nodes. Use the ldm ls-bindings command in the control domain to get the MAC addresses for vnet0 and vnet1 in each domain:

MEN_INTERFACES=vnet0 vnet1
NMEN_INTERFACES=vnet0 vnet1

Use c0d0s0, c0d0s1, and the like as disk slice names:

SLICE=c0d0s0 3072  /               -      logging       MEN,DATALESS
SLICE=c0d0s3 128   unnamed         -        -           MEN
SLICE=c0d0s4 128   unnamed         -        -           MEN
SLICE=c0d0s5 2048  /SUNWcgha/local c0d0s3 logging       MEN
SLICE=c0d0s6 8192  /export         c0d0s4 logging       MEN
SLICE=c0d0s1 free  swap            -        -           MEN,DATALESS

Add the patches required by LDoms to addon.conf:

SMOSSERVICEPATCH=118833-36  <path to patch directory> - I USR_SPECIFIC Y Y Y 
PATCH_WITH_PKGADDPATCH=118833-36  <path to patch directory> - S LOCAL  N Y N 
PATCH=125043-01  <path to patch directory> - I LOCAL Y Y Y SMOSSERVICE
PATCH=T124921-02 <path to patch directory> - I LOCAL Y N Y SMOSSERVICE

Use the following command to jump-start the nodes instead of using the more commonly used boot net - install command:

ok boot /virtual-devices@100/channel-devices@200/network@0 - install 

Use the following command to boot the diskless nodes after the master-eligible nodes are installed:

ok ldm set-variable boot-device=\
"/virtual-devices@100/channel-devices@200/network@0:dhcp,,,,,5 \ 
/virtual-devices@100/channel-devices@200/network@1:dhcp,,,,,5" nmen35 
ok boot

In the control domain, update the OpenBoot PROM variables to make the nodes boot automatically.

For diskless nodes, type the following:

# ldm set-variable \
  boot-device=/virtual-devices@100/channel-devices@200/disk@0 men15
# ldm set-variable auto-boot\?=true men15

For dataless nodes, type the following:

# ldm set-variable \
  boot-device=/virtual-devices@100/channel-devices@200/disk@0 nmen35
# ldm set-variable auto-boot\?=true nmen35 

Repeat the preceding step for men25 and nmen45.