Re: [nv-l] Managing clusters

[Stephen Hochstetler <shochste@us.ibm.com>]

Bill,

Here is my 2 cents. Using DNS or /etc/hosts, create 3 separate hosts statements. Have NetView discover it as 3 hosts.

emailN1 - 10.20.30.2
emailN2 - 10.20.30.3
emailserver - 10.20.30.1, 10.20.30.4, 10.20.30.5

Then, if you loose N1 or N2, you get a hostdown trap for N1 or N2, but the function is still running.
If you loose all the virtual addresses, you get a hostdown trap saying the emailserver is down.


Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678) FAX - 512-838-6931
http://www.redbooks.ibm.com
"Evans, Bill" <Bill.Evans@hq.doe.gov>

"Evans, Bill" <Bill.Evans@hq.doe.gov>
Sent by: owner-nv-l@lists.us.ibm.com

05/13/2005 12:07 PM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	[nv-l] Managing clusters

Our MS Exchange team has put together clusters of e-mail servers.  Each cluster has five IP addresses I can see with NetView.

• 10.20.30.1 EmailServer # Virtual address
• 10.20.30.2 EmailServer-N1 # Real address
• 10.20.30.3 EmailServer-N2 # Real address
• 10.20.30.4 EmailServer-CL # Virtual address
• 10.20.30.5 EmailServer-MSDTC # Virtual address

The three virtual addresses migrate between N1 and N2.  
 
Has anyone configured NetView to handle such a cluster in a rational manner for display and notifications?  My first thought has been to identify the virtual addresses as HSRP and instantiate only the real nodes.  The result was traps with IP addresses instead of hostnames.  
 
Suggestions are solicited.

Bill Evans
Tivoli NetView Support for DOE
301-903-0057