Reference the content in these sections if you already have GroupWise running on a cluster and you need to upgrade to a newer version of GroupWise.
As with any upgrade, you must upgrade the primary domain first.
Stop all GroupWise agents that are running on the node that you want to upgrade first.
Install the GroupWise Server component on the first node.
Follow the instructions in Step 1 through Step 9 in Linux: Installing the GroupWise Server Software
in the GroupWise Installation Guide.
IMPORTANT:Do not start the GroupWise Admin console after installing the GroupWise software.
Continue with Configuring the GroupWise Admin Service to Function in a Cluster.
You must configure the GroupWise Admin Service to function in a cluster, so that it keeps track of which cluster resources are available to it at each point in time. Configuring the GroupWise Admin Service for clustering ensures that files associated with domains and post offices are created on cluster volumes, rather than on individual cluster nodes.
|
File |
Standard Location |
Clustered location |
|---|---|---|
|
Domain SSL Certificate, MTA SSL Certificate, GWIA SSL Certificate |
/opt/novell/groupwise/certificates |
/groupwise/certificates (a peer to the domain folder) |
|
Post Office SSL Certificate, POA SSL Certificate |
/opt/novell/groupwise/certificates |
/groupwise/certificates (a peer to the post office folder) |
|
MTA Log Files |
/var/log/novell/groupwise/
domain.mta |
/groupwise/agents/logs (a peer to the domain folder) |
|
GWIA Log Files |
/var/log/novell/groupwise/
gwia.domain |
/groupwise/agents/logs (a peer to the domain folder) |
|
POA Log Files |
/var/log/novell/groupwise/
post_office.poa |
/groupwise/agents/logs (a peer to the post office folder) |
Run the following command to enable the GroupWise Admin Service to run in a clustering environment:
gwadminutil config -cluster enable
You should receive the following response:
Cluster: enabled Default Port: 9710
Use the following command to restart the GroupWise Admin Service.
rcgrpwise restart gwadminservice
Your GroupWise system is now ready to function in a cluster.
For convenience, configure the GroupWise Installation console to use an authentication mode of a user name and password, rather than the default token-based authentication mode:
gwadminutil installcfg -m user -u user_name -p password
Continue with Upgrading Domains and Post Offices.
For background information about upgrading your GroupWise system, see GroupWise System Upgrade
in the GroupWise Installation Guide.
In a web browser, start the GroupWise Installation console:
https://domain_server_secondary_ip_address:9710/gwadmin-console/installProvide the user name as password that you established in Step 3 in Configuring the GroupWise Admin Service to Function in a Cluster.
In the GroupWise Installation console, click Upgrade an Existing Domain or Post Office GroupWise 18.
The Installation console provides a list of agents on the current node. The list is built from the gwha.conf file.
(Conditional) If there are any domains or post offices that are not currently online to this node, select them, and then click Remove to remove them from the list.
For each domain and post office, verify that the IP address in the list is the secondary IP address of the cluster resource.
For each domain and post office, verify that there are no port conflicts for the Admin port.
(Conditional) If you need to change the IP address or Admin port for a domain or post office, click the name of the domain or post office, update the information, and then click OK.
Click Next to continue with the upgrade.
On the Credentials page:
(Conditional) If the primary domain is being upgraded, specify the user name for the GroupWise Super Admin, and type the password twice for confirmation.
or
Specify the IP address, Admin port, and Admin credentials of the owning domain.
Click Next to display the Summary page.
Review the summary, and then click Finish.
Continue with Finishing the GroupWise Software Upgrade.
To finish the GroupWise Software Upgrade, you need to repeat the same tasks above on each cluster node:
On each cluster node, repeat the steps in the following sections:
Configuring the GroupWise Admin Service to Function in a Cluster
Upgrading Domains and Post Offices
Remember that you cannot upgrade a post office until its owning domain has been upgraded.
Continue with Providing New Load and Unload Scripts.
After upgrade, you need to replace the existing “load” and “unload” scripts as shown in the example steps below:
In iManager, replace the existing load script for each cluster resource with a new load script that is similar to the following example:
#!/bin/bash ./opt/novell/ncs/lib/ncsfuncs exit_on_error nss /poolact=DOM exit_on_error ncpcon mount DOM=254 exit_on_error add_secondary_ipaddress 151.155.136.248 exit_on_error ncpcon bind --ncpservername=DOM --ipaddress=151.155.136.248 exit_on_error novcifs --add '--vserver=".cn=DOM.ou=servers.o=novell.t=GW14-TREE."' --ip-addr=151.155.136.248
# Start grpwise service systemctl start grpwise.service
#create agent services exit_on_error /opt/novell/groupwise/admin/gwsc -i /media/nss/DOM/utah exit_on_error /opt/novell/groupwise/admin/gwsc -i /media/nss/DOM/utah/wpgate/gwia exit_on_error /opt/novell/groupwise/admin/gwsc -i /media/nss/DOM/provo/
#start admin service listeners exit_on_error /opt/novell/groupwise/admin/gwadmin-ipc start utah cluster exit_on_error /opt/novell/groupwise/admin/gwadmin-ipc start provo.utah cluster
#start GroupWise agents gwsc -start utah gwsc -start gwia.utah gwsc -start provo.utah
This sample cluster load script performs the following actions:
Establishes what to do for certain error conditions.
Creates the GroupWise agent services (if they do not already exist).
Starts the GroupWise Admin Service listeners with clustering enabled for the MTA and POA.
Starts the POA, MTA, and GWIA (in that order if all are present)
Replace the existing unload script for each cluster resource with a new unload script that is similar to the following example:
#!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # Stop admin service listeners ignore_error /opt/novell/groupwise/admin/gwadmin-ipc stop utah ignore_error /opt/novell/groupwise/admin/gwadmin-ipc stop provo.utah
# Stop GroupWise agents gwsc -stop utah gwsc -stop gwia.utah gwsc -stop provo.utah
#Remove agent service gwsc -u /media/nss/DOM/utah gwsc -u /media/nss/DOM/utah/wpgate/gwia gwsc -u /media/nss/DOM/provo/
ignore_error novcifs --remove '--vserver=".cn=DOM.ou=servers.o=novell.t=GW14-TREE."' --ip-addr=151.155.136.248 ignore_error ncpcon unbind --ncpservername=DOM --ipaddress=151.155.136.248 ignore_error del_secondary_ipaddress 151.155.136.248 ignore_error nss /pooldeact=DOM exit 0
This sample cluster unload script performs the following actions:
Stops the GroupWise Admin Service listeners for the MTA and POA
Stops the MTA, GWIA, and POA (in that order if all are present)
Lists error conditions that can be ignored
NOTE:The pkill command used in earlier versions of the GroupWise unload script is no longer needed. In GroupWise 18, the grpwise script terminates GroupWise agent processes according to the wait setting specified in the gwha.conf file. The default is 60 seconds. If that amount of time is not sufficient to ensure a clean shutdown of the agents in your GroupWise system, increase the wait setting as needed.
Continue with Testing the Upgraded Cluster.
Follow the instructions in Testing Your Clustered GroupWise System on Linux to verify that the GroupWise Administration Console keeps track of the cluster resources that are currently available to it.