GroupWise 8 - 3 node Cluster (OES2) - Scripts for YOU!

0 Likes

Do you want to do a GroupWise 8, 3 node Cluster with NSS Volumes on OES2 Linux? If so then here are your scripts! This should make your life a lot easier in the trenches!



iN this scenario: 1 Post Office, 2 Domains, GWIA and WebAccess. (1000 users)



Load POA
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=GWPO
exit_on_error ncpcon mount GWPO=230
exit_on_error add_secondary_ipaddress 10.2.1.64
exit_on_error ncpcon bind --ncpservername=GWPO_VS --ipaddress=10.2.1.64
ignore_error /etc/init.d/grpwise start GWPO3SACS.GWDOMAINSACS
exit 0



Unload POA
. /opt/novell/ncs/lib/ncsfuncs
ignore_error /etc/init.d/grpwise stop GWPO3SACS.GWDOMAINSACS
sleep 10
ignore_error fuser -k /media/nss/GWPO
ignore_error ncpcon unbind --ncpservername=GWPO_VS --ipaddress=10.2.1.64
ignore_error del_secondary_ipaddress 10.2.1.64
ignore_error nss /pooldeact=GWPO
exit 0



Load Primary Domain
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=GWDOM
exit_on_error ncpcon mount GWDOM=253
exit_on_error add_secondary_ipaddress 10.2.1.65
exit_on_error ncpcon bind --ncpservername=GWDOM_VS --ipaddress=10.2.1.65
exit_on_error /etc/init.d/grpwise start GWDOMAINSACS
exit 0




Unload Primary Domain
. /opt/novell/ncs/lib/ncsfuncs
#Request Service Stop
ignore_error /etc/init.d/grpwise stop GWDOMAINSACS
sleep 8
#Stop Service Otherwise
ignore_error fuser -k /media/nss/GWDOM
ignore_error ncpcon unbind --ncpservername=GWDOM_VS --ipaddress=10.2.1.65
ignore_error del_secondary_ipaddress 10.2.1.65
ignore_error nss /pooldeact=GWDOM
exit 0



Load Secondary Domain with GWIA and WebAccess
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=GWSECDOM
exit_on_error ncpcon mount GWSECDOM=252
exit_on_error add_secondary_ipaddress 10.2.1.66
exit_on_error ncpcon bind --ncpservername=GWSECDOM_VS --ipaddress=10.2.1.66
exit_on_error /etc/init.d/grpwise start GWSECDOM
sleep 5
exit_on_error /etc/init.d/grpwise start gwia.gwsecdom
sleep 5
exit_on_error /etc/init.d/grpwise start WEBAC80A
exit 0



Unload Secondary Domain, GWIA and Webaccess
. /opt/novell/ncs/lib/ncsfuncs
ignore_error /etc/init.d/grpwise stop GWSECDOM
ignore_error /etc/init.d/grpwise stop gwia.gwsecdom
ignore_error /etc/init.d/grpwise stop WEBAC80A
sleep 20
ignore_error fuser -k /media/nss/GWSECDOM
ignore_error ncpcon unbind --ncpservername=GWSECDOM_VS --ipaddress=10.2.1.66
ignore_error del_secondary_ipaddress 10.2.1.66
ignore_error nss /pooldeact=GWSECDOM
exit 0

Labels:

How To-Best Practice
Comment List
Anonymous
Parents
  • Hello,

    A very nice info...

    But I just have a question.

    I have seen in the GW documentation that if the WebAccess agent can be installed in a cluster environment, the Web Application part (tomcat/apache) cannot...

    So, would be possible to know how did you install the Web Application component in your cluster system ?

    Tx a lot ...

    Cheers,

    Stephan
Comment
  • Hello,

    A very nice info...

    But I just have a question.

    I have seen in the GW documentation that if the WebAccess agent can be installed in a cluster environment, the Web Application part (tomcat/apache) cannot...

    So, would be possible to know how did you install the Web Application component in your cluster system ?

    Tx a lot ...

    Cheers,

    Stephan
Children
  • I believe it says you can't cluster the webaccess application, I don't think it says you can't install it on the cluster node. While I have actually gotten it to work as a cluster resource the simplest method is to install the gwapplication on all nodes in the cluster. You can leave it there and direct users to the cluster resource address or use them to load balance the traffic across the cluster nodes.
Related Discussions
Recommended