E N D
1. Clustering GroupWise® 7On Open Enterprise Server Linux Gregg A. Hinchman
Consultant
Hinchman Consulting
gregg@hinchmanconsulting.com
2. IntroductionPresentation Outline Introduction
Speakers
Presentation Business
Planning
Definitions and Tools
Cluster Design
GroupWise® Design
Implementation
Domain and MTA
Post Office and POA
GroupWise Internet Agent
GWHA
Summary
3. IntroductionSpeakers Gregg A. Hinchman
Self-Unemployed Consultant, www.HinchmanConsulting.com
11+ years of GroupWise® Experience
5 years of Clustering experience
Author:
“Success with Clustering GroupWise 7” www.TayKratzer.com
Co-Author:
“Success with GroupWise Document Management”
GroupWise® Cool Solutions Articles
Consultants Corner
GroupWise Advisor Magazine Articles
4. IntroductionSpeakers Morris Blackham
16 yrs working with WP Office, GroupWise®
Original WordPerfect Office “Swat” team
Consultant with teltrust.com/dotOne
5 yrs as GroupWise Internet Agent QA engineer
Currently development manager for GW CPR maintenance team
The 'Godfather' of GroupWise
5. IntroductionPresentation Business Topic
We will discuss Best Practices for Planning and implementing GroupWise® 7 on Open Enterprise Server Linux.
Format
Discussion will be led with supporting examples given.
Questions
Please hold until 'Question Breaks'
Knowledge:
Advanced GroupWise 7
OES Linux
Related Sessions:
Consultants Corner: Successful GroupWise 7 Consolidations
The Art of Business Continuance
6. Open Enterprise Server LX Cluster Planning Definitions and Tools Definitions
Cluster - A group of servers and a SAN
Node - A server in a cluster
LUN's - Logical Unit Number (Disk Space on a SAN)
Cluster Resource - Virtual Server - not NSS only in Linux
Design Matrix – Planning data
OES Linux/SUSE® Linux
Tools
ConsoleOne®
*NEW* Migration Kit for NetWare® to Linux
iManager
Novell Remote Manager (NRM)
7. Open Enterprise Server LX Cluster Planning Definitions and Tools File Systems
NSS
Advantages
Disadvantages
EXT3
Advantages
Disadvantages
ReiserFS
Advantages
Disadvantages
9. Open Enterprise Server LXCluster Planning Our Company
10. Open Enterprise Server LX Cluster Planning Cluster Design LUN's
SAN's -Support OES Linux?
Naming Standards
Cluster Nodes
Support OES Linux?
HBA's support OES Linux?
Naming Standards
Disk Space
Disk Segment
Volumes
Mount Points
Cluster Resources
Naming Standards -Consider with GroupWise® in mind
IP Address Standards
11. Open Enterprise Server LX Cluster Planning GroupWise® Design Domain and MTA
What information is needed to cluster a Domain and MTA?
Naming and Numbering Standards
Cluster Resource Names-Consider in Cluster Planning
Volume Names
Directory Paths
IP Addresses
Ports
MTP
HTTP
12. Open Enterprise Server LX Cluster Planning GroupWise® Design Post Office and POA
What information is needed to cluster a Post Office and POA?
Cluster Resource Name
Volume Name
Directory Path
IP Address
Ports
C/S
/IP
MTPINPORT and MTPOUTPORT
HTTP
13. Open Enterprise Server LX Cluster Planning GroupWise® Design Gateways - GroupWise Internet Agent
New Alternate GWIA failover for MTA's
Must be on same resource as owning domain
Create an A record for secondary IP addresspoint MX record to the A record
Set Bind Exclusive to TCP/IP address
Yes, it binds for all protocols!
Leave Postfix running listening on loopback address (default)
14. Open Enterprise Server LX Cluster Planning GroupWise® Design
15. Open Enterprise Server LX Cluster Planning GroupWise® Design
17. Open Enterprise Server LX Cluster Planning GroupWise® Design GroupWise Design Matrix
18. Open Enterprise Server LX Cluster Planning GroupWise® Design Agents must be installed on each cluster node
Why?? - RPM database issues
Log and Startup files are on cluster resource
Designate one node as the “install node”
Online resource to “install node” prior to agent configuration
Or create a Cluster Resource for Software Distribution Directory - online to node for agent configuration
Import cluster data to all other nodes
Create mount points on appropriate cluster nodes
Can create mount point with cluster resource load script
“ignore_error mkdir /mnt/mountpoint”
19. Implementation – File System File systems
NSS
Create pool identical to NetWare® cluster
use iManager or NSSMU
Native Linux File Systems
Must uses EVMS to create containers and volumes
See TID 3003435 for details and requirements
remove existing segment manager
create container
create volume
create file system
20. Implementation – File System
21. Implementation – File System Native Linux File Systems
Create cluster resource manually
Use iManager
Create using Generic IP template
Use script from TID 3003435 to activate/deactive the container
Test online/offline of resource before GroupWise® install
22. ImplementationDomain and MTA Cluster resource must be online before installation
Resource = Cluster volume and secondary IP address
Use “install –-cluster” or select Cluster Install on initial dialog
Agent install path is hard coded
/opt/novell/groupwise/agents
Agents must be installed to all appropriate nodes
Enter path to cluster resource mount point
Log path, startup files point to <mountpoint>/opt/groupwise/share
23. ImplementationDomain and MTA Loading the MTA
/opt/novell/groupwise/agents/bin/gwmta @/<mntpoint>/groupwise/agents/share/utah.mta
/etc/init.d/grpwise start utah
Unload the MTA
/etc/init.d/grpwise stop utah
Edit Cluster load/unload scripts
Test the Cluster Resource
24. DEMO TIME!!!
25. Questions and Answers
26. ImplementationPost Office and POA Configure the Cluster Resource
Load Script
Unload Script
Fail Over
Loading the POA
/opt/novell/groupwise/agents/bin/gwpoa @/<mntpoint>/groupwise/agents/share/provo.poa
/etc/init.d/grpwise start provo.utah
Unload the POA
/etc/init.d/grpwise stop provo.utah
Edit load/unload scripts and test the Cluster Resource
27. DEMO TIME!!!
28. Questions and Answers
29. ImplementationGroupWise® Internet Agent Install and configure to GWIA's owning domain node
Set TCP/IP address to secondary IP address
Set Bind Exclusive
Loading GWIA
/opt/novell/groupwise/agents/bin/gwgwia @/<mntpoint>/groupwise/agents/share/gwia.cfg
/etc/init.d/grpwise start utah.gwia
telnet to port 25 to validate SMTP Listener
add GWIA load command to Domains cluster load/unload scripts
30. DEMO TIME!!!
31. Questions and Answers
32. ImplementationGWHA GWHA and GWHA.CONF on each node
gwha.conf provides start/stop info for the grpwise script
Install has “import clustering data” option
Writes all agent config data to gwha.conf on each node
Install must be done from a SDD
Creates /gwinst/clusterimport.conf
GWMonitor uses GWHA to provide agent restart capabilities in Linux
GWMonitor detects if agent is down and issues a restart request to GWHA
GWHA configuration
xinetd service – disabled by default
Protect using SSL
modify /etc/init.d/grpwise-ma script to enable HA polling.
33. DEMO TIME!!!
34. Summary Protected Memory
Not on Linux
Registering to the Nodes (RPM)
Designed to run agents in daemon mode
Cluster Command line options
cluster offline <resource>
cluster online <resource> <node>
cluster migrate <resource> <node>
cluster status
Or use iManager
Novell Clustering Services™ logging events in /var/log/message
No Agent Screens loaded on nodes by default
35. Summary Knowledge:
ATT Clustering Class
Clustering Book - www.TayKratzer.com (For Planning Only)
Consulting - Fast Track
Planning:
Hardware
GroupWise® Design Matrix
IP Addresses, Ports, etc.
Fail Over
Novell® Interoperability Guide
http://www.novell.com/documentation/gw7/index.html?page=/documentation/gw7/gw7_interop/data/alse1z7.html
36. Questions and Answers
38. Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell.
Unpublished Work of Novell, Inc. All Rights Reserved.
This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
General Disclaimer
This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. Novell, Inc., makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.
39. Implementation – Filesystem