You are here

Part 6. Sun Cluster 3.2: Adding a New node to the cluster

Adding a New node to the cluster:

First we need to modify the allowed hosts acl, so the new server can join the cluster:

[root@vm2:/]# claccess allow -h vm1 (10-03 23:24)
[root@vm2:/]# cluster show (10-03 23:24)

=== cluster ===

cluster name: vmclus
clusterid: 0x4e743d17
installmode: disabled
heartbeat_timeout: 10000
heartbeat_quantum: 1000
private_netaddr: 172.16.0.0
private_netmask: 255.255.248.0
max_nodes: 64
max_privatenets: 10
udp_session_timeout: 480
global_fencing: pathcount
node list: vm3, vm2

=== host access control ===

cluster name: vmclus
allowed hosts: vm1 ---------------> no we have vm1 allowed to join the cluster
authentication protocol: sys

On vm1 server, we launch scinstall:

vm1# ./scinstall

*** Main Menu ***

Please select from one of the following (*) options:

* 1) Create a new cluster or add a cluster node
2) Configure a cluster to be JumpStarted from this install server
3) Manage a dual-partition upgrade
4) Upgrade this cluster node
5) Print release information for this cluster node

* ?) Help with menu options
* q) Quit

Option: 1

*** New Cluster and Cluster Node Menu ***

Please select from any one of the following options:

1) Create a new cluster
2) Create just the first node of a new cluster on this machine
3) Add this machine as a node in an existing cluster

?) Help with menu options
q) Return to the Main Menu

Option: 3

*** Add a Node to an Existing Cluster ***

This option is used to add this machine as a node in an already
established cluster. If this is a new cluster, there may only be a
single node which has established itself in the new cluster.

Before you select this option, the Sun Cluster framework software must
already be installed. Use the Java Enterprise System (JES) installer
to install Sun Cluster software.

Press Control-d at any time to return to the Main Menu.

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

>>> Typical or Custom Mode <<<

This tool supports two modes of operation, Typical mode and Custom.
For most clusters, you can use Typical mode. However, you might need
to select the Custom mode option if not all of the Typical defaults
can be applied to your cluster.

For more information about the differences between Typical and Custom
modes, select the Help option from the menu.

Please select from one of the following options:

1) Typical
2) Custom

?) Help
q) Return to the Main Menu

Option [1]: 2

>>> Sponsoring Node <<<

For any machine to join a cluster, it must identify a node in that
cluster willing to "sponsor" its membership in the cluster. When
configuring a new cluster, this "sponsor" node is typically the first
node used to build the new cluster. However, if the cluster is already
established, the "sponsoring" node can be any node in that cluster.

Already established clusters can keep a list of hosts which are able
to configure themselves as new cluster members. This machine should be
in the join list of any cluster which it tries to join. If the list
does not include this machine, you may need to add it by using
claccess(1CL) or other tools.

And, if the target cluster uses DES to authenticate new machines
attempting to configure themselves as new cluster members, the
necessary encryption keys must be configured before any attempt to
join.

What is the name of the sponsoring node? vm2

>>> Cluster Name <<<

Each cluster has a name assigned to it. When adding a node to the
cluster, you must identify the name of the cluster you are attempting
to join. A sanity check is performed to verify that the "sponsoring"
node is a member of that cluster.

What is the name of the cluster you want to join? vmclus

Attempting to contact "vm2" ... done

Cluster name "vmclus" is correct.

Press Enter to continue:

.............................

Your responses indicate the following options to scinstall:

scinstall -i \
-C vmclus \
-N vm2 \
-A trtype=dlpi,name=e1000g0 -A trtype=dlpi,name=e1000g1 \
-m endpoint=:e1000g0,endpoint=switch1 \
-m endpoint=:e1000g1,endpoint=switch2

Are these the options you want to use (yes/no) [yes]?

Checking device to use for global devices file system ... done

Adding node "vm1" to the cluster configuration ... done
Adding adapter "e1000g0" to the cluster configuration ... done
Adding adapter "e1000g1" to the cluster configuration ... done
Adding cable to the cluster configuration ... done
Adding cable to the cluster configuration ... done

Copying the config from "vm2" ... done

Copying the postconfig file from "vm2" if it exists ... done
done

Setting the node ID for "vm1" ... done (id=3)

Verifying the major number for the "did" driver with "vm2" ... done

Checking for global devices global file system ... done
Updating vfstab ... done

Verifying that NTP is configured ... done
Initializing NTP configuration ... done

Updating nsswitch.conf ... done

Adding cluster node entries to /etc/inet/hosts ... done

Configuring IP multipathing groups ...done

Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.100511120139
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.

Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.

Updating file ("ntp.conf.cluster") on node vm3 ... done
Updating file ("hosts") on node vm3 ... done
Updating file ("ntp.conf.cluster") on node vm2 ... done
Updating file ("hosts") on node vm2 ... done

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

Rebooting ...

updating /platform/i86pc/boot_archive

Once the server has rebooted, the node joins the cluster ok:

vm1# ./cluster status

=== Cluster Nodes ===

--- Node Status ---

Node Name Status
--------- ------
vm3 Online
vm2 Online
vm1 Online

=== Cluster Transport Paths ===

Endpoint1 Endpoint2 Status
--------- --------- ------
vm3:e1000g1 vm2:e1000g1 Path online
vm3:e1000g0 vm2:e1000g0 Path online
vm3:e1000g1 vm1:e1000g1 Path online
vm3:e1000g0 vm1:e1000g0 Path online
vm2:e1000g1 vm1:e1000g1 Path online
vm2:e1000g0 vm1:e1000g0 Path online

=== Cluster Quorum ===

--- Quorum Votes Summary ---

Needed Present Possible
------ ------- --------
3 4 4

--- Quorum Votes by Node ---

Node Name Present Possible Status
--------- ------- -------- ------
vm3 1 1 Online
vm2 1 1 Online
vm1 1 1 Online

--- Quorum Votes by Device ---

Device Name Present Possible Status
----------- ------- -------- ------
quoromd1 1 1 Online

With a 3 node cluster we don't need a quorum device, but we are going to be more HA if we have allways Node-1 votes from the quorum device or devices.

We can't continue because the iscsi disks we have don't support scsi-3 reservations, they only support scsi-2 reservation that works ok but only for 2 nodes, the cluster needs scsi reservations on all shared disks for fencing, so the only way we can get the shared disks working in the 3 nodes is not using scsi reservations, which means that we need to disable fencing(NOT the best thing to do but this is just for the testing), because currently we have installed sun cluster 3.2 update 1, it doesn't have the possibility to disable fencing, it was introduced in update 2, so on the next post we are going to update the cluster to 3.2 update 3.

Unix Systems: 

Add new comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.

Fatal error: Class CToolsCssCache contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (DrupalCacheInterface::__construct) in /homepages/37/d228974590/htdocs/sites/all/modules/ctools/includes/css-cache.inc on line 52