Cluster Add and Delete member Procedure:

Note down the boot disks for all the systems in cluster especially TESTSYSTEM
# ls -la /etc/fdmns/root1_domain
lrwxr-xr-x   1 root     system        15 Mar 23  2002 dsk3a -> /dev/disk/dsk3a

# ls -la /etc/fdmns/root2_domain

Note down path for disk dsk3a using
# hwmgr -show scsi
# hwmgr -show scsi -full -id <id for dsk3>

      SCSI                DEVICE    DEVICE  DRIVER NUM  DEVICE FIRST 
 HWID:  DEVICEID HOSTNAME   TYPE      SUBTYPE OWNER  PATH FILE   VALID PATH
-------------------------------------------------------------------------
  145:  10       testsystem        disk      none    2      6    dsk3   [5/7/1]   

 Save important files:

Copy important files to a temporary directory.

# mkdir /testsystem_original 
# cp -r /cluster/members/member1/var/adm/lmf /testsystem_original/lmf
# cp /etc/sysconfigtab /testsystem_original
# cp /cluster/members/member1/etc/rc.config /testsystem_original
# cp /cluster/members/member1/etc/inet.local  /testsystem_original
# cp /cluster/members/member1/etc/securettys /testsystem_original
# cp /cluster/members/member1/etc/ntp.conf /testsystem_original
# cp /cluster/members/member1/etc/routes /testsystem_original
# swapon –s 
# note down the boot patch from Console.

Shutdown testsystem before deleting member
Enter command on testsystem:
# shutdown -h now

Delete Member
From other member livesystem Start Delete and then Add member
Enter following command to delete member
# clu_delete_member
Enter a cluster member ID []:1
Checking cluster member ID: 1.
You entered '1' as the member ID.

  	Is this correct? [yes]:yes
   	
	Do you want to continue to delete a cluster member? [no]:yes  Deleting member disk boot partition files.
Member disk boot partition files deleted  
Initial cluster deletion successful, member '1' can no longer join    the cluster. Deletion continuing with cleanup.
Deleting Member Specific Directories.
   Deleting: /cluster/members/member1/.
   Deleting: /usr/cluster/members/member1/.
   Deleting: /var/cluster/members/member1/.
clu_delete_member: The deletion of cluster member '1' completed successfully.

Adding  Member 

# clu_add_member
This is the TruCluster Add Member Program.
   
You will need the following information in order to add a member to the cluster:
   
       - Hostname
       - Member ID (1-63)
       - Members Votes
       - Member's boot disk (for example, dsk7)
       - Member's virtual cluster interconnect IP name
       - Member's virtual cluster interconnect IP address
       - Member's physical cluster interconnect devices
       - Member's NetRAIN device name
       - Member's physical cluster interconnect IP address
       - Member's cluster license
Adding a member involves the following steps:   
       Labeling the boot disk (when required)
       Creating AdvFS domains
       Creating additional CDSLs
       Updating configuration files
   
You then boot genvmunix from the new member's boot disk. At the first boot, the new member:
   
       Configures layered product subsets
       Builds a kernel and copies it to the member's boot disk
       Boots the new kernel
	Do you want to continue adding this member? [yes]: yes

Each cluster member has a hostname, which is assigned to the HOSTNAME variable in /etc/rc.config.
   
	Enter the new member's fully qualified hostname []:testsystem
Checking member's hostname: testsystem.
  
You entered 'testsystem' as this member's hostname.
   	Is this name correct? [yes]:
   
The next available member ID for a cluster member is '1'.
   
	Enter a cluster member ID [1]:
Checking cluster member ID: 1.
You entered '1' as the member ID.
   	Is this correct? [yes]:

The number of votes for a member is an integer, usually 0 or 1.

   	Enter the number of votes for this member [1]:
Checking number of votes for this member: 1.
   
You entered '1' as the number votes for this member.
   	
	Is this correct? [yes]:

Each member has its own boot disk, which has an associated device name; for example, 'dsk5'.
   
  	Enter the device name of the member boot disk []: dsk3
Checking the member boot disk: dsk3.
   
You entered 'dsk1' as the device name of this member's boot disk.
   	Is this correct? [yes]:

Device 'ics0' is the default virtual cluster interconnect device.
   Checking virtual cluster interconnect device: ics0.  
The virtual cluster interconnect IP name 'testsystem-ics0' was formed by appending '-ics0' to the system's hostname.
To use this default value, press Return at the prompt.
   
Each virtual cluster interconnect interface has a unique IP name (a hostname) associated with it.
   
Enter the IP name for the virtual cluster interconnect [testsystem-ics0]:testsystem-mc0

Checking virtual cluster interconnect IP name: testsystem-mc0.  
You entered 'testsystem-mc0' as the IP name for the virtual cluster interconnect.
  	Is this name correct? [yes]:

The virtual cluster interconnect IP address '192.168.1.1' was found in the /etc/hosts file as the address associated with the cluster virtual interconnect IP name.
      
   Enter the IP address for the virtual cluster interconnect [192.168.1.9]:

Checking virtual cluster interconnect IP address: 192.168.1.9.
You entered '192.168.1.9' as the IP address for the virtual cluster interconnect.
 	Is this address correct? [yes]:

	Enter the physical cluster interconnect device name(s) [mc0]:
Checking physical cluster interconnect interface device name(s): mc0.
You entered 'mc0' as your physical cluster interconnect interface device name(s). 
	Is this correct? [yes]:
Do you wish to register the TruCluster Server license for this new member at this time? [yes]:no

	Member's hostname:                                 testsystem
      Member's ID:                                       1
     	Number of votes assigned to this member:           1
      Member's boot disk:                                dsk3     
	Member's virtual cluster interconnect devices:     ics0
      Member's virtual cluster interconnect IP name:     testsystem-mc0
      Member's virtual cluster interconnect IP address:  192.168.1.9
      Member's physical cluster interconnect devices:    mc0
      Member's NetRAIN device name:                      Not-Applicable
      Member's physical cluster interconnect IP address: Not-Applicable
  	Member's cluster license:                          Not Entered
	Do you want to continue to add this member? [yes]:
   
  Creating required disk labels.
     Creating disk label on member disk: dsk3.
     Initializing cnx partition on member disk: dsk3h.
   
   Creating AdvFS domains:
     Creating AdvFS domain 'root1_domain#root' on partition 'dsk3a'.
   
   Creating cluster member-specific files:
     Creating new member's root member-specific files.
     Creating new member's usr member-specific files.
clu_add_member: Initial member 1 configuration completed successfully.
From the newly added member's console, perform the following steps to
   complete the newly added member's configuration:
    
        Boot the newly added member using genvmunix:
           >>>boot -file genvmunix <new-member-boot-device>
                            
Enter Boot Command from TESTSYSTEM SRM prompt:
	P00>>>boot -file genvmunix  “Path for the disk”

   	Would you like to run clu_netsetup at this time? [yes]:
  
  **** TruClusters Add Member Network Interface Configuration ****  
   1  Configure Interface  
   2  Exit
   Enter the number for your choice: 1

***** CONFIGURE/DELETE NETWORK INTERFACES *****  
You can configure or delete network interfaces.  Configuration information is updated in /etc/rc.config and /etc/hosts.  Choose "configure" or "delete" at the prompt.
   
Enter whether you want to "(c)onfigure" or "(d)elete" network interfaces.
  If you are finished, press the RETURN key: c
   
   You will now be asked a series of questions about the system.
   Default answers are shown in square brackets ([]). To use a
   default answer, press the RETURN key.
   
   This machine contains the following network interfaces:
            alt0
            alt1
		alt2
            ee0
            ee1
            ee2
            ee3
		tu0
		tu1
		tu2
            sl0

 	Which interface do you want to configure [alt0]: ee2
  	You want to configure "ee0".  Is this correct [yes]? 
  	Enter the hostname for interface "ee2" []: testsystem

The hostname for interface "ee2" is "testsystem".
   	
	Is this correct [yes]? 

Enter the Internet Protocol (IP) address for interface "ee2" in dot notation []:10.10.10.109
The IP address for interface "ee2" is "10.10.10.109 ".
   	
	Is this correct [yes]?

Enter the subnet mask in dot notation [255.255.255.0]: 255.255.255.0
The subnet mask for "ee2" is "255.255.225.0".

   	Is this correct [yes]?

Restore the saved files with changes as below

Licenses
# cp /testsystem_original/lmf/ldb /cluster/members/member1/var/adm/lmf
# lmf reset
# lmf list

ntp.conf
Copy saved ntp.conf to its original location
# cp /testsystem_original/ntp.conf  /cluster/members/member1/etc/ntp.conf

routes
Edit and insert following entry for the default route in
/cluster/members/member1/etc/routes

default 10.10.10.1

rc.config
Change NetRAIN entries in 
/cluster/members/member1/etc/rc.config as follows:
HOSTNAME: testsystem
NUM_NETCONFIG: 0 
NETDEV_0: ics0 
IFCONFIG_0: 192.168.1.9 netmask 255.255.255.0 
NETDEV_1: nr0 
IFCONFIG_1: 10.10.10.109  netmask 255.255.225.0 filter 
NRDEV_0="nr0"
NRCONFIG_0="ee0,ee2"
NR_DEVICES="1"

inet.local 
Insert following lines at end of
/cluster/members/member1/etc/inet.local
lan_config -i nr0 -a 0 -x 1 -s 100
lagconfig -c
lagconfig -p alt1 key=1
lagconfig -p alt2 key=1

sysconfigtab
Check difference between /etc/sysconfigtab and /Testsystem_original/sysconfigtab
# diff /etc/sysconfigtab /Testsystem_original/sysconfigtab

Modify swap devices under vm: as follows

swapdevice=/dev/disk/dsk3b,/dev/vol/rootdg/testsystem-swapvol

Check parameters under proc and modify as follows
proc:
	proc:
	max_per_proc_data_size = 2147483648
        max_per_proc_stack_size = 134217728
        max_proc_per_user = 1024
        max_threads_per_user = 16384
        per_proc_data_size = 1073741824
        per_proc_stack_size = 134217728

ipc:
	msg_mni = 256
        msg_tql = 128
        sem_mni = 2048
        sem_msl = 400
        sem_opm = 48
        sem_ume = 48
	shm_max = 2147483648
        shm_mni = 2048
        shm_seg = 128
lsm:
 lsm_rootdev_is_volume=0

Reboot the system 
# shutdown –r now

Check Cluster status
# clu_get_info -full

Check Network Interfaces
# ifconfig –a

Start service ptestsystem from other member

# caa_start ptestsystem