This section provides information about upgrading a traditional Sentinel installation, and also about upgrading the operating system in a traditional Sentinel installation.
Enable the maintenance mode on the cluster:
crm configure property maintenance-mode=true
Maintenance mode helps you to avoid any disturbance to the running cluster resources while you update Sentinel. You can run this command from any cluster node.
Verify whether the maintenance mode is active:
crm status
The cluster resources should appear in the unmanaged state.
Upgrade the passive cluster node:
Stop the cluster stack:
rcopenais stop
Stopping the cluster stack ensures that the cluster resources remain accessible and avoids fencing of nodes.
Log in as root to the server where you want to upgrade Sentinel.
Extract the install files from the tar file:
tar xfz <install_filename>
Run the following command in the directory where you extracted the install files:
./install-sentinel --cluster-node
After the upgrade is complete, restart the cluster stack:
rcopenais start
Repeat Step 3 for all passive cluster nodes.
Remove the autostart scripts so that the cluster can manage the product.
cd /
insserv -r sentinel
Upgrade the active cluster node:
Back up your configuration, then create an ESM export.
For more information about backing up data, see Backing Up and Restoring Data
in the NetIQ Sentinel Administration Guide.
Stop the cluster stack:
rcopenais stop
Stopping the cluster stack ensures that the cluster resources remain accessible and avoids fencing of nodes.
Log in as root to the server where you want to upgrade Sentinel.
Run the following command to extract the install files from the tar file:
tar xfz <install_filename>
Run the following command in the directory where you extracted the install files:
./install-sentinel
After the upgrade is complete, start the cluster stack:
rcopenais start
Remove the autostart scripts so that the cluster can manage the product.
cd /
insserv -r sentinel
Run the following command to synchronize any changes in the configuration files:
csync2 -x -v
Disable the maintenance mode on the cluster:
crm configure property maintenance-mode=false
You can run this command from any cluster node.
Verify whether the maintenance mode is inactive:
crm status
The cluster resources should appear in the Started state.
(Optional) Verify whether the Sentinel upgrade is successful:
rcsentinel version
This section provides information about how to upgrade the operating system to a major version, such as upgrading from SLES 11 to SLES 12, in a Sentinel HA cluster. When you upgrade the operating system, you must perform few configuration tasks, to ensure that Sentinel HA works correctly after you upgrade the operating system.
Perform the steps described in the following sections:
To upgrade the operating system:
Log in as root user to any node in the Sentinel HA cluster.
Run the following command to enable the maintenance mode on the cluster:
crm configure property maintenance-mode=true
The maintenance mode helps you to avoid any disturbance to the running cluster resources while you upgrade the operating system.
Run the following command to verify whether the maintenance mode is active:
crm status
The cluster resources should appear in the unmanaged state.
Ensure that you have upgraded Sentinel to version 8.0 or later on all the cluster nodes.
Ensure that all the nodes in the cluster are registered with SLES and SLESHA.
Perform the following steps to upgrade the operating system on the passive cluster node:
Run the following command to stop the cluster stack:
rcopenais stop
Stopping the cluster stack ensures that the cluster resources remain inaccessible and avoids fencing of nodes.
Upgrade the operating system. Perform the steps in Section 25.4, Upgrading the Operating System.
Repeat step 6 on all the passive nodes to upgrade the operating system.
Repeat step 6 on the active node to upgrade the operating system on it.
Repeat step 6b to upgrade the operating system on shared storage.
Ensure that the operating system on all the nodes in the cluster is upgraded to SLES12 SP1.
To configure iSCSI targets:
On the shared storage, check if the iSCSI LIO package is installed. If it is not installed yet, go to YaST2 Software Management and install the iSCSI LIO package (iscciliotarget RPM).
Perform the following steps on all the nodes in the cluster:
Run the following command to open the file which contains the iSCSI initiator name:
cat /etc/iscsi/initiatorname.iscsi
Note the initiator name which will be used for configuring iSCSI initiators:
For example:
InitiatorName=iqn.1996-04.de.suse:01:441d6988994
These initiator names will be used while configuring iSCSI Target Client Setup.
Click Service and select the When Booting option to ensure that the service starts when the operating system boots.
Select the Global tab, deselect No Authentication to enable authentication, and then specify the user name and the password for incoming and outgoing authentication.
The No Authentication option is enabled by default. However, NetIQ recommends that you enable authentication to ensure that the configuration is secure.
Click Targets, and click Add to add a new target.
Click Add to add a new LUN.
Leave the LUN number as 0, browse in the Path dialog (under Type=fileio) and select the /localdata file that you created. If you have a dedicated disk for storage, specify a block device, such as /dev/sdc.
Repeat steps 6 and 7, and add LUN 1 and select /networkdata this time.
Repeat steps 6 and 7, and add LUN 2 and select /sbd this time.
Leave the other options at their default values. Click Next.
Modify iSCSI Target Client Setup screen is displayed.
Click Add. When prompted for Client Name, specify the initiator name you have copied in Step 2. Repeat this step to add all the client names, by specifying the initiator names.
The list of client names will be displayed in the Client List.
(Conditional) If you have enabled authentication in Step 4, provide the authentication credentials you specified in Step 4.
Select a client, select Edit Auth> Incoming Authentication, and specify the user name and password. Repeat this for all the clients.
Click Next to select the default authentication options, and then click Finish to exit the configuration. Restart iSCSI if prompted.
Exit YaST.
To configure iSCSI initiators:
Connect to one of the cluster nodes (node01) and Start YaST.
Click Network Services > iSCSI Initiator.
If prompted, install the required software (iscsiclient RPM).
Click Service, and select When Booting to ensure that the iSCSI service is started on boot.
Click Discovered Targets.
NOTE:If any previously existing iSCSI targets are displayed, delete those targets.
Select Discovery to add a new iSCSI target.
Specify the iSCSI Target IP address (10.0.0.3).
(Conditional) If you have enabled authentication in Step 4 in Configuring iSCSI Targets, deselect No Authentication. In the Outgoing Authentication section, enter the authentication credentials you specified while configuring iSCSI targets.
Click Next.
Select the discovered iSCSI Target with the IP address 10.0.0.3 and select Log In.
Perform the following steps:
Switch to Automatic in the Startup drop-down menu.
(Conditional) If you have enabled authentication, deselect No Authentication.
The user name and the password you have specified should be displayed in the Outgoing Authentication section. If these credentials are not displayed, enter the credentials in this section.
Click Next.
Switch to the Connected Targets tab to ensure that you are connected to the target.
Exit the configuration. This should have mounted the iSCSI Targets as block devices on the cluster node.
In the YaST main menu, select System > Partitioner.
In the System View, you should see new hard disks of the LIO-ORG-FILEIO type (such as /dev/sdb and /dev/sdc) in the list, along with already formatted disks (such as /dev/sdb1 or /dev/<SHARED1).
Repeat steps 1 through 12 on all the nodes.
To configure the HA cluster:
Start YaST2 and go to High Availability > Cluster.
If prompted, install the HA package and resolve the dependencies.
After the HA package installation, Cluster—Communication Channels is displayed.
Ensure that Unicast is selected as the Transport option.
Select Add a Member Address and specify the node IP address, and then repeat this action to add all the other cluster node IP addresses.
Ensure that Auto Generate Node ID is selected.
Ensure that the HAWK service is enabled on all the nodes. If it is not enabled, run the following command to enable it:
service hawk start
Run the following command:
ls -l /dev/disk/by-id/
The SBD partition ID is displayed. For example, scsi-1LIO-ORG_FILEIO:33caaa5a-a0bc-4d90-b21b-2ef33030cc53.
Copy the ID.
Open the sbd file (/etc/sysconfig/sbd), and change the ID of SBD_DEVICE with the ID you have copied in step 7.
Run the following commands to restart the pacemaker service:
rcpacemaker restart
Run the following commands to remove the autostart scripts, so that the cluster can manage the product.
cd /
insserv -r sentinel
Repeat steps 1 through 10 on all the cluster nodes.
Run the following command to synchronize any changes in the configuration files:
csync2 -x -v
Run the following command to disable the maintenance mode on the cluster:
crm configure property maintenance-mode=false
You can run this command from any cluster node.
Run the following command to verify whether the maintenance mode is inactive:
crm status
The cluster resources should appear in the Started state.