Recent changes to HAMN_Setup_MNs

HAMN_Setup_MNs modified by Lissa Valletta

Lissa Valletta — Thu, 24 Jul 2014 13:29:10 -0000

--- v17
+++ v18
@@ -1,10 +1,10 @@
 ## Setup xCAT on the Primary Management Node

-The procedure described in [Setting_Up_a_Linux_xCAT_Mgmt_Node] or [XCAT_AIX_Cluster_Overview_and_Mgmt_Node_] can be used for the xCAT setup on the primary management node. If DB2 will be used as the xCAT database system, please refer to the doc [Setting_Up_DB2_as_the_xCAT_DB]. 
+The procedure described in [Setting_Up_a_Linux_xCAT_Mgmt_Node] or [XCAT_AIX_Cluster_Overview_and_Mgmt_Node] can be used for the xCAT setup on the primary management node. If DB2 will be used as the xCAT database system, please refer to the doc [Setting_Up_DB2_as_the_xCAT_DB]. 

 ## Setup xCAT on the Standby Management Node

-The procedure described in [Setting_Up_a_Linux_xCAT_Mgmt_Node] or [XCAT_AIX_Cluster_Overview_and_Mgmt_Node_] can also be used for the xCAT setup on the standby management node. The database system on the standby management node should be the same as the one running on the primary management node. 
+The procedure described in [Setting_Up_a_Linux_xCAT_Mgmt_Node] or [XCAT_AIX_Cluster_Overview_and_Mgmt_Node] can also be used for the xCAT setup on the standby management node. The database system on the standby management node should be the same as the one running on the primary management node. 

 If shared disks are used between the two management nodes, when setting up the standby management node, the shared disks should not be mounted on the standby management node. Make sure the xcatd can be up and running with whatever database is used as part of the xCAT setup verification on the standby management node. 

@@ -27,18 +27,20 @@
   * Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. You also need to modify the system configuration to prevent the xcatd and DHCP from being started automatically after reboots. For example, use chkconfig command on Linux and use rmssys command on AIX: 

 On AIX: 
-    
+ 
+~~~~   
        stopsrc -s xcatd
        rmssys -s xcatd
-    
+~~~~     

 On Linux: 
-    
+
+~~~~     
        service xcatd stop
        chkconfig --level 345 xcatd off
        service dhcpd stop
        chkconfig --level 2345 dhcpd off
-    
+~~~~

HAMN_Setup_MNs modified by Guang Cheng Li

Guang Cheng Li — Mon, 23 Jun 2014 15:25:22 -0000

--- v16
+++ v17
@@ -43,5 +43,5 @@

-  1. Stop the HPC software daemons like TEAL, CNM, LL and GPFS and modify system configuration to prevent them from being started automatically. 
-  2. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>
+  * Stop the HPC software daemons like TEAL, CNM, LL and GPFS and modify system configuration to prevent them from being started automatically. 
+  * (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>

HAMN_Setup_MNs modified by Guang Cheng Li

Guang Cheng Li — Mon, 23 Jun 2014 15:25:22 -0000

--- v15
+++ v16
@@ -12,19 +12,19 @@

 After the xCAT setup is done on the standby management node, perform the following additional configuration steps: 

-  1. Make sure the primary management node can resolve the hostname of the standby management node, and vice versa. 
-  1. Setup ssh authentication between the primary management node and standby management node. It should be setup as "passwordless ssh authentication" and it should work in both directions. The summary of this procedure is: 
-    1. cat keys from /.ssh/id_rsa.pub on the primary management node and add them to /.ssh/authorized_keys on the standby management node. Remove the standby management node entry from /.ssh/known_hosts on the primary management node prior to issuing ssh to the standby management node. 
-    2. cat keys from /.ssh/id_rsa.pub on the standby management node and add them to /.ssh/authorized_keys on the primary management node. Remove the primary management node entry from /.ssh/known_hosts on the standby management node prior to issuing ssh to the primary management node. 
-  2. Make sure the time on the primary management node and standby management node is synchronized. Some tips on setting up the timezone and time: 
-    1. Command echo $TZ returns the current timezone setting 
-    2. Command date and chtz can be used to adjust the time and timezone. 
-    3. To setup ntp on the management nodes on AIX: 
-      1. Update the /etc/ntp.conf file with a valid ntp server. 
-      2. stopsrc -s xntpd 
-      3. startsrc -s xntpd 
-      4. Use ntpq -p to show the peer status of the ntp server, should see * to left of server after successful association with server is established 
-  3. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. You also need to modify the system configuration to prevent the xcatd and DHCP from being started automatically after reboots. For example, use chkconfig command on Linux and use rmssys command on AIX: 
+  * Make sure the primary management node can resolve the hostname of the standby management node, and vice versa. 
+  * Setup ssh authentication between the primary management node and standby management node. It should be setup as "passwordless ssh authentication" and it should work in both directions. The summary of this procedure is: 
+    * cat keys from /.ssh/id_rsa.pub on the primary management node and add them to /.ssh/authorized_keys on the standby management node. Remove the standby management node entry from /.ssh/known_hosts on the primary management node prior to issuing ssh to the standby management node. 
+    * cat keys from /.ssh/id_rsa.pub on the standby management node and add them to /.ssh/authorized_keys on the primary management node. Remove the primary management node entry from /.ssh/known_hosts on the standby management node prior to issuing ssh to the primary management node. 
+  * Make sure the time on the primary management node and standby management node is synchronized. Some tips on setting up the timezone and time: 
+    * Command echo $TZ returns the current timezone setting 
+    * Command date and chtz can be used to adjust the time and timezone. 
+    * To setup ntp on the management nodes on AIX: 
+      * Update the /etc/ntp.conf file with a valid ntp server. 
+      * stopsrc -s xntpd 
+      * startsrc -s xntpd 
+      * Use ntpq -p to show the peer status of the ntp server, should see * to left of server after successful association with server is established 
+  * Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. You also need to modify the system configuration to prevent the xcatd and DHCP from being started automatically after reboots. For example, use chkconfig command on Linux and use rmssys command on AIX: 

 On AIX:

HAMN_Setup_MNs modified by Guang Cheng Li

Guang Cheng Li — Mon, 23 Jun 2014 15:25:22 -0000

--- v14
+++ v15
@@ -10,9 +10,6 @@

 When installing and configuring DB2 software on the standby management node, you should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB]. Install DB2 and run db2sqlsetup to setup the xCAT database. 

-LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 
-
-  
 After the xCAT setup is done on the standby management node, perform the following additional configuration steps: 

   1. Make sure the primary management node can resolve the hostname of the standby management node, and vice versa. 
@@ -27,6 +24,24 @@
       2. stopsrc -s xntpd 
       3. startsrc -s xntpd 
       4. Use ntpq -p to show the peer status of the ntp server, should see * to left of server after successful association with server is established 
-  3. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. You also need to modify the system configuration to prevent the xcatd and DHCP from being started automatically after reboots. 
-  4. Stop the HPC software daemons like TEAL, CNM, LL and GPFS and modify system configuration to prevent them from being started automatically 
-  5. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>
+  3. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. You also need to modify the system configuration to prevent the xcatd and DHCP from being started automatically after reboots. For example, use chkconfig command on Linux and use rmssys command on AIX: 
+
+On AIX: 
+    
+       stopsrc -s xcatd
+       rmssys -s xcatd
+    
+
+On Linux: 
+    
+       service xcatd stop
+       chkconfig --level 345 xcatd off
+       service dhcpd stop
+       chkconfig --level 2345 dhcpd off
+    
+
+  
+
+
+  1. Stop the HPC software daemons like TEAL, CNM, LL and GPFS and modify system configuration to prevent them from being started automatically. 
+  2. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>

HAMN_Setup_MNs modified by Guang Cheng Li

Guang Cheng Li — Mon, 23 Jun 2014 15:25:21 -0000

--- v13
+++ v14
@@ -27,5 +27,6 @@
       2. stopsrc -s xntpd 
       3. startsrc -s xntpd 
       4. Use ntpq -p to show the peer status of the ntp server, should see * to left of server after successful association with server is established 
-  3. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. 
-  4. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>
+  3. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. You also need to modify the system configuration to prevent the xcatd and DHCP from being started automatically after reboots. 
+  4. Stop the HPC software daemons like TEAL, CNM, LL and GPFS and modify system configuration to prevent them from being started automatically 
+  5. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>

HAMN_Setup_MNs modified by Guang Cheng Li

Guang Cheng Li — Mon, 23 Jun 2014 15:25:21 -0000

--- v12
+++ v13
@@ -6,20 +6,16 @@

 The procedure described in [Setting_Up_a_Linux_xCAT_Mgmt_Node] or [XCAT_AIX_Cluster_Overview_and_Mgmt_Node_] can also be used for the xCAT setup on the standby management node. The database system on the standby management node should be the same as the one running on the primary management node. 

-LKV:The hostname and IP address of the Standby MN should be the same as the primary. Don't they have to be the same for DB2 to work. DB2 server was configured with a certain hostname and ip. I think if they are different, DB2 will be trying to contact the primary MN to service the database. For testing be sure and actually shutdown the primary and make sure DB2 can really run just on the Standby. Also, run something like the "/opt/ibm/db2/V9.7/instance/db2ilist" on the Standby to see if the Standby recognizes the xcatdb instance. 
+If shared disks are used between the two management nodes, when setting up the standby management node, the shared disks should not be mounted on the standby management node. Make sure the xcatd can be up and running with whatever database is used as part of the xCAT setup verification on the standby management node. 

-LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. ( We must make sure the xcatdb userid and group are on the Standby, this is usually created by db2sqlsetup). Another file arethe entries we put in /etc/services for db2. If those entries are not there the service nodes will not be able to contact the standby management node. Again with the primary down, see if the service nodes can get to the database via the Standby management node. 
+When installing and configuring DB2 software on the standby management node, you should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB]. Install DB2 and run db2sqlsetup to setup the xCAT database. 

 LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 

-If shared disks are used between the two management nodes, when setting up the standby management node, the shared disks should not be mounted on the standby management node. Make sure the xcatd can be up and running with whatever database is used as part of the xCAT setup verification on the standby management node. 
-
+  
 After the xCAT setup is done on the standby management node, perform the following additional configuration steps: 

   1. Make sure the primary management node can resolve the hostname of the standby management node, and vice versa. 
-
-LKV: This implies they are different, can they be different? The hostname is put in the created instance of DB2. I had thought the database fail in the past by changing the hostname on the system. Also the credentials that were generated for xCAT on the Primary have a hostname in the credential and it is reflected in the Policy Table and the SSH keys that are distributed to the nodes and service nodes. If the Standby has a different hostname, do the Credentials and SSH keys and policy table still work? This comes down to again, shutting down the Primary and making sure we can run when only the Standby is available. 
-
   1. Setup ssh authentication between the primary management node and standby management node. It should be setup as "passwordless ssh authentication" and it should work in both directions. The summary of this procedure is: 
     1. cat keys from /.ssh/id_rsa.pub on the primary management node and add them to /.ssh/authorized_keys on the standby management node. Remove the standby management node entry from /.ssh/known_hosts on the primary management node prior to issuing ssh to the standby management node. 
     2. cat keys from /.ssh/id_rsa.pub on the standby management node and add them to /.ssh/authorized_keys on the primary management node. Remove the primary management node entry from /.ssh/known_hosts on the standby management node prior to issuing ssh to the primary management node.

HAMN_Setup_MNs modified by Lissa Valletta

Lissa Valletta — Mon, 23 Jun 2014 15:25:21 -0000

--- v11
+++ v12
@@ -17,10 +17,13 @@
 After the xCAT setup is done on the standby management node, perform the following additional configuration steps:

   1. Make sure the primary management node can resolve the hostname of the standby management node, and vice versa. 
-  2. Setup ssh authentication between the primary management node and standby management node. It should be setup as "passwordless ssh authentication" and it should work in both directions. The summary of this procedure is: 
+
+LKV: This implies they are different, can they be different? The hostname is put in the created instance of DB2. I had thought the database fail in the past by changing the hostname on the system. Also the credentials that were generated for xCAT on the Primary have a hostname in the credential and it is reflected in the Policy Table and the SSH keys that are distributed to the nodes and service nodes. If the Standby has a different hostname, do the Credentials and SSH keys and policy table still work? This comes down to again, shutting down the Primary and making sure we can run when only the Standby is available. 
+
+  1. Setup ssh authentication between the primary management node and standby management node. It should be setup as "passwordless ssh authentication" and it should work in both directions. The summary of this procedure is: 
     1. cat keys from /.ssh/id_rsa.pub on the primary management node and add them to /.ssh/authorized_keys on the standby management node. Remove the standby management node entry from /.ssh/known_hosts on the primary management node prior to issuing ssh to the standby management node. 
     2. cat keys from /.ssh/id_rsa.pub on the standby management node and add them to /.ssh/authorized_keys on the primary management node. Remove the primary management node entry from /.ssh/known_hosts on the standby management node prior to issuing ssh to the primary management node. 
-  3. Make sure the time on the primary management node and standby management node is synchronized. Some tips on setting up the timezone and time: 
+  2. Make sure the time on the primary management node and standby management node is synchronized. Some tips on setting up the timezone and time: 
     1. Command echo $TZ returns the current timezone setting 
     2. Command date and chtz can be used to adjust the time and timezone. 
     3. To setup ntp on the management nodes on AIX: 
@@ -28,5 +31,5 @@
       2. stopsrc -s xntpd 
       3. startsrc -s xntpd 
       4. Use ntpq -p to show the peer status of the ntp server, should see * to left of server after successful association with server is established 
-  4. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. 
-  5. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>
+  3. Stop the xcatd daemon and DHCP service, for example, using commands stopsrc -s xcatd and stoprsc -s dhcpsd on AIX. 
+  4. (Optional) Backup the xCAT database tables for the current configuration on primary management node, using command dumpxCATdb -p <backupdir>

HAMN_Setup_MNs modified by Lissa Valletta

Lissa Valletta — Mon, 23 Jun 2014 15:25:21 -0000

--- v10
+++ v11
@@ -8,7 +8,9 @@

 LKV:The hostname and IP address of the Standby MN should be the same as the primary. Don't they have to be the same for DB2 to work. DB2 server was configured with a certain hostname and ip. I think if they are different, DB2 will be trying to contact the primary MN to service the database. For testing be sure and actually shutdown the primary and make sure DB2 can really run just on the Standby. Also, run something like the "/opt/ibm/db2/V9.7/instance/db2ilist" on the Standby to see if the Standby recognizes the xcatdb instance. 

-LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. ( We must make sure the xcatdb userid and group are on the Standby, this is usually created by db2sqlsetup). Another file arethe entries we put in /etc/services for db2. If those entries are not there the service nodes will not be able to contact the standby management node. Again with the primary down, see if the service nodes can get to the database via the Standby management node. LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 
+LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. ( We must make sure the xcatdb userid and group are on the Standby, this is usually created by db2sqlsetup). Another file arethe entries we put in /etc/services for db2. If those entries are not there the service nodes will not be able to contact the standby management node. Again with the primary down, see if the service nodes can get to the database via the Standby management node. 
+
+LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 

 If shared disks are used between the two management nodes, when setting up the standby management node, the shared disks should not be mounted on the standby management node. Make sure the xcatd can be up and running with whatever database is used as part of the xCAT setup verification on the standby management node.

HAMN_Setup_MNs modified by Lissa Valletta

Lissa Valletta — Mon, 23 Jun 2014 15:25:21 -0000

--- v9
+++ v10
@@ -8,7 +8,7 @@

 LKV:The hostname and IP address of the Standby MN should be the same as the primary. Don't they have to be the same for DB2 to work. DB2 server was configured with a certain hostname and ip. I think if they are different, DB2 will be trying to contact the primary MN to service the database. For testing be sure and actually shutdown the primary and make sure DB2 can really run just on the Standby. Also, run something like the "/opt/ibm/db2/V9.7/instance/db2ilist" on the Standby to see if the Standby recognizes the xcatdb instance. 

-LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. ( We must make sure the xcatdb userid and group are on the Standby, this is usually created by db2sqlsetup). LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 
+LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. ( We must make sure the xcatdb userid and group are on the Standby, this is usually created by db2sqlsetup). Another file arethe entries we put in /etc/services for db2. If those entries are not there the service nodes will not be able to contact the standby management node. Again with the primary down, see if the service nodes can get to the database via the Standby management node. LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 

 If shared disks are used between the two management nodes, when setting up the standby management node, the shared disks should not be mounted on the standby management node. Make sure the xcatd can be up and running with whatever database is used as part of the xCAT setup verification on the standby management node.

HAMN_Setup_MNs modified by Lissa Valletta

Lissa Valletta — Mon, 23 Jun 2014 15:25:21 -0000

--- v8
+++ v9
@@ -6,9 +6,9 @@

 The procedure described in [Setting_Up_a_Linux_xCAT_Mgmt_Node] or [XCAT_AIX_Cluster_Overview_and_Mgmt_Node_] can also be used for the xCAT setup on the standby management node. The database system on the standby management node should be the same as the one running on the primary management node. 

-LKV:The hostname and IP address of the Standby MN should be the same as the primary. Don't they have to be the same for DB2 to work. DB2 server was configured with a certain hostname and ip. I think if they are different, DB2 will be trying to contact the primary MN to service the database. For testing be sure and actually shutdown the primary and make sure DB2 can really run just on the Standby. 
+LKV:The hostname and IP address of the Standby MN should be the same as the primary. Don't they have to be the same for DB2 to work. DB2 server was configured with a certain hostname and ip. I think if they are different, DB2 will be trying to contact the primary MN to service the database. For testing be sure and actually shutdown the primary and make sure DB2 can really run just on the Standby. Also, run something like the "/opt/ibm/db2/V9.7/instance/db2ilist" on the Standby to see if the Standby recognizes the xcatdb instance. 

-LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 
+LKV: When using the DB2 database install the DB2 software on the Standby Management Node. You should follow the instructions in [Setting_Up_DB2_as_the_xCAT_DB] to install the DB2 software and all prerequisite software on the Standby Management Node. Only install DB2 do not run db2sqlsetup to setup the xCAT database, this was already done on the Primary Management Node. ( We must make sure the xcatdb userid and group are on the Standby, this is usually created by db2sqlsetup). LKV: Is this where we should tell about stopping the daemons ( xCAT, TEAL, CNM, LL,etc) and changing the configuration so they do not start on reboot? 

 If shared disks are used between the two management nodes, when setting up the standby management node, the shared disks should not be mounted on the standby management node. Make sure the xcatd can be up and running with whatever database is used as part of the xCAT setup verification on the standby management node.