manually adding a member to a purescale system

Taken from my test system

Given

=====

[root@s0 ~]# mmlscluster

GPFS cluster information

========================

  GPFS cluster name:         gpfsdomain.s0

  GPFS cluster id:           16217308675852594251

  GPFS UID domain:           gpfsdomain.s0

  Remote shell command:      /usr/bin/ssh

  Remote file copy command:  /usr/bin/scp

GPFS cluster configuration servers:

-----------------------------------

  Primary server:    s0

  Secondary server:  s1

 Node  Daemon node name  IP address     Admin node name  Designation

---------------------------------------------------------------------

   1   s0                192.168.1.30   s0               quorum-manager

   2   s1                192.168.1.31   s1               quorum-manager

[root@s0 ~]# mmaddnode -N s2:quorum-manager

Mon Mar 23 19:43:53 GMT 2015: mmaddnode: Processing node s2

mmaddnode: Command successfully completed

mmaddnode: Warning: Not all nodes have proper GPFS license designations.

    Use the mmchlicense command to designate licenses as needed.

mmaddnode: Propagating the cluster configuration data to all

  affected nodes.  This is an asynchronous process.

[root@s0 ~]# mmchlicense server --accept -N s2

The following nodes will be designated as possessing GPFS server licenses:

        s2

mmchlicense: Command successfully completed

mmchlicense: Propagating the cluster configuration data to all

  affected nodes.  This is an asynchronous process.

[root@s0 ~]# mmlscluster

GPFS cluster information

========================

  GPFS cluster name:         gpfsdomain.s0

  GPFS cluster id:           16217308675852594251

  GPFS UID domain:           gpfsdomain.s0

  Remote shell command:      /usr/bin/ssh

  Remote file copy command:  /usr/bin/scp

GPFS cluster configuration servers:

-----------------------------------

  Primary server:    s0

  Secondary server:  s1

 Node  Daemon node name  IP address     Admin node name  Designation

---------------------------------------------------------------------

   1   s0                192.168.1.30   s0               quorum-manager

   2   s1                192.168.1.31   s1               quorum-manager

   3   s2                192.168.1.132  s2               quorum-manager

[root@s0 ~]# mmstartup -N s2

Mon Mar 23 19:54:47 GMT 2015: mmstartup: Starting GPFS ...

[root@s0 ~]# ssh s2 df

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/mapper/vg_ai0-lv_root

                      44969032  23905924  18778772  57% /

tmpfs                  1027532       112   1027420   1% /dev/shm

/dev/sda1               495844    100408    369836  22% /boot

[root@s0 ~]# mmmount all -a

Mon Mar 23 19:58:15 GMT 2015: mmmount: Mounting file systems ...

[root@s0 ~]#  db2iupdt -d -add -m s2 –mnet s2 i1

DBI20154E  The command failed because one or more invalid or unsupported parameters were specified. Command name: "db2iupdt". List of invalid or unsupported parameters specified: "–mnet".

[root@s0 ~]#

[root@s0 ~]#  db2iupdt -d -add -m s2:s2 i1

DBI1473W  Parameter -m hostname:netname is deprecated. The

      deprecated parameter is replaced by new parameter

      -m hostname -mnet netname. Command: db2iupdt.

Explanation:

The deprecated parameter might be removed from a future release.

User response:

Replace the deprecated parameter with the new parameter in any scripts

or applications.

DBI1446I  The db2iupdt command is running.

DB2 installation is being initialized.

 Total number of tasks to be performed: 11

Total estimated time for all tasks to be performed: 1104 second(s)

Task #1 start

Description: Installing DB2 files on remote hosts

Estimated time 600 second(s)

Task #1 end

Task #2 start

Description: Installing or updating DB2 HA scripts for IBM Tivoli System Automation for Multiplatforms (Tivoli SA MP)

Estimated time 40 second(s)

Task #2 end

Task #3 start

Description: Installing or updating DB2 Cluster Scripts for IBM General Parallel File System (GPFS)

Estimated time 40 second(s)

Task #3 end

Task #4 start

Description: Registering licenses on remote hosts

Estimated time 40 second(s)

Task #4 end

Task #5 start

Description: Compiling GPL

Estimated time 30 second(s)

Task #5 end

Task #6 start

Description: Setting default global profile registry variables

Estimated time 1 second(s)

Task #6 end

Task #7 start

Description: Register NTP

Estimated time 40 second(s)

Task #7 end

Task #8 start

Description: Initializing instance list

Estimated time 5 second(s)

Task #8 end

Task #9 start

Description: Initiating the remote host list

Estimated time 5 second(s)

Task #9 end

Task #10 start

Description: Configuring DB2 instances

Estimated time 300 second(s)

Task #10 end

Task #11 start

Description: Updating global profile registry

Estimated time 3 second(s)

Task #11 end

The execution completed successfully.

For more information see the DB2 installation log at "/tmp/db2iupdt.log.8928".

DBI1070I  Program db2iupdt completed successfully.

[root@s0 s2]# su - i1

[i1@s0 ~]$ db2instance -list

ID        TYPE             STATE                HOME_HOST               CURRENT_HOST            ALERT   PARTITION_NUMBER        LOGICAL_PORT    NETNAME

--        ----             -----                ---------               ------------            -----   ----------------        ------------    -------

0       MEMBER           STARTED                       s1                         s1               NO                  0                   0         s1

1       MEMBER           STARTED                       s2                         s2               NO                  0                   0         s2

128     CF               PRIMARY                       s0                         s0               NO                  -                   0         s0

HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT

--------                   -----                ----------------        -----

      s2                  ACTIVE                              NO           NO

      s0                  ACTIVE                              NO           NO

      s1                  ACTIVE                              NO           NO

Some connections:

[i1@s2 ~]$ db2 list application global

Auth Id  Application    Appl.      Application Id                                                 DB       # of

         Name           Handle                                                                    Name    Agents

-------- -------------- ---------- -------------------------------------------------------------- -------- -----

I1       db2jcc_applica 88         192.168.1.30.28310.150323210758                                SAMPLE   1    

I1       db2jcc_applica 65605      192.168.1.32.55618.150323210931                                SAMPLE   1    

[i1@s2 ~]$ db2 list application at member 0

Auth Id  Application    Appl.      Application Id                                                 DB       # of

         Name           Handle                                                                    Name    Agents

-------- -------------- ---------- -------------------------------------------------------------- -------- -----

I1       db2jcc_applica 88         192.168.1.30.28310.150323210758                                SAMPLE   1    

[i1@s2 ~]$ db2 list application at member 1

Auth Id  Application    Appl.      Application Id                                                 DB       # of

         Name           Handle                                                                    Name    Agents

-------- -------------- ---------- -------------------------------------------------------------- -------- -----

I1       db2jcc_applica 65605      192.168.1.32.55618.150323210931                                SAMPLE   1