configuring a cluster

# svcprop network/rpc/bind:default |grep local_only

config/local_only boolean true

# svccfg

svc:> select network/rpc/bind

svc:/network/rpc/bind> setprop config/local_only=false

svc:/network/rpc/bind> quit

# svcadm refresh network/rpc/bind:default

# svcprop /system/webconsole:console |grep tcp_listen

options/tcp_listen boolean false

# svccfg

svc:> select system/webconsole

svc:/system/webconsole> setprop options/tcp_listen=true

svc:/system/webconsole> quit

# svcadm refresh svc:/system/webconsole:console

# /usr/sbin/smcwebserver restart

Restarting Oracle Java(TM) Web Console Version 3.1 ...

The console is running

configure IPMP

# ls -l /etc/hostname* from sivss010

-rw-r--r-- 1 root root 51 Sep 12 16:52 /etc/hostname.e1000g0

-rw-r--r-- 1 root root 18 Sep 12 16:53 /etc/hostname.e1000g1

sivss026 netmask + broadcast + group sc_ipmp0 up

# cat /etc/hostname.e1000g1

group sc_ipmp0 up

After configuring the ipmp #init 6

# Update the /etc/hosts both servers

Configure the NTP

Copy /etc/inet/ntp.conf from another server

# svcs -a |grep -i ntp

# svcadm enable svc:/network/ntp:default

#open the ssh root

permit root login yes

# svcadm restart svc:/network/ssh:default

Generate ssh keys for root

Server A

# /usr/bin/ssh-keygen -t rsa

#scp -rp /.ssh/id_rsa.pub root@serverB:/tmp

Server B

#mkdir -p /.ssh

#cat /tmp/id_rsa.pub >> /.ssh/authorized_keys

Copy the cluster sofware form sivss010 to tmp

# cd /tmp
# unzip solaris-cluster-3_3u2-ga-x86.zip

## cd Solaris_x86

# ./installer

# Select oracle solaris cluster 3.3u2 and Select oracle cluster agent 3.3u2

Click next

# unselect install multilingual packages and choose no

#click next

#Click Install
# click next

# Select configure later.

#choose no = No internet connection needs to be confirmed.

cluster configuration

Export the path on vi /etc/profile

And add

PATH=/usr/cluster/bin:$PATH

export PATH

Note: And log out and login.

#scinstall

choose 1) Create a new cluster or add a cluster node

choose 1) Create a new cluster

Do you want to continue (yes/no) [yes]?

choose 2) Custom

What is the name of the cluster you want to establish? sivsc500

Node name (Control-D to finish): sivss026

Node name (Control-D to finish): sivss027

Node name (Control-D to finish): ^D

This is the complete list of nodes:

sivss026

sivss027

Is it correct (yes/no) [yes]?

Should this cluster use at least two private networks (yes/no) [yes]?

Does this two-node cluster use switches (yes/no) [yes]? no (what we have is not
currently working)

Select the first cluster transport adapter:

1) e1000g2

2) e1000g3

3) Other

Option: 1

Adapter "e1000g2" is an Ethernet adapter.

Searching for any unexpected network traffic on "e1000g2" ... done

Unexpected network traffic was seen on "e1000g2".

"e1000g2" may be cabled to a public network.

Do you want to use "e1000g2" anyway (yes/no) [no]? yes

The "dlpi" transport type will be set for this cluster.

Name of adapter (physical or virtual) on "sivss027" to which "e1000g2" is

###

Select the second cluster transport adapter:

1) e1000g2

2) e1000g3

3) Other

Option: 2

Adapter "e1000g3" is an Ethernet adapter.

Searching for any unexpected network traffic on "e1000g3" ... done

Unexpected network traffic was seen on "e1000g3".

"e1000g3" may be cabled to a public network.

Do you want to use "e1000g3" anyway (yes/no) [no]? yes

Name of adapter (physical or virtual) on "sivss027" to which "e1000g3" is

Is it okay to accept the default network address (yes/no) [yes]?

Is it okay to accept the default network address (yes/no) [yes]?

Is it okay to accept the default netmask (yes/no) [yes]?

Plumbing network address 172.16.0.0 on adapter e1000g2 >>

Do you want to turn off global fencing (yes/no) [no]?

Do you want to disable automatic quorum device selection (yes/no) [no]? yes
(do to later)

The default is to use lofi.

For node "sivss026",

Is it okay to use this default (yes/no) [yes]?

For node "sivss027",

Is it okay to use this default (yes/no) [yes]?

Configuring global device using lofi on sivss027: done

Is it okay to create the new cluster (yes/no) [yes]?

During the cluster creation process, cluster check is run on each of

the new cluster nodes. If cluster check detects problems, you can

either interrupt the process or check the log files after the cluster

has been established.

Interrupt cluster creation for cluster check errors (yes/no) [no]?

Cluster Creation

Log file - /var/cluster/logs/install/scinstall.log.7977

Started cluster check on "sivss026".

Started cluster check on "sivss027".

cluster check failed for "sivss026".

cluster check failed for "sivss027".

Refer to the log file for details.

The name of the log file is /var/cluster/logs/install/scinstall.log.7977.

Configuring "sivss027" ... done

Rebooting "sivss027" ... done

Configuring "sivss026" ... done

Rebooting "sivss026" ...

Log file - /var/cluster/logs/install/scinstall.log.7977

Rebooting ...

updating /platform/i86pc/boot_archive