[Top] [All Lists]

[nv-l] Strategies for dealing with clusters, interface names, TEC events

To: <nv-l@lists.tivoli.com>
Subject: [nv-l] Strategies for dealing with clusters, interface names, TEC events
From: Jon_Austin@bankone.com
Date: Thu, 13 Feb 2003 13:34:54 -0500
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Thu, 13 Feb 2003 18:46:21 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-help@lists.tivoli.com>
List-post: <mailto:nv-l@lists.tivoli.com>
List-subscribe: <mailto:nv-l-subscribe@lists.tivoli.com>
List-unsubscribe: <mailto:nv-l-unsubscribe@lists.tivoli.com>
Mailing-list: contact nv-l-help@lists.tivoli.com; run by ezmlm
Thread-index: AcLTRQ6q7zwzL5lQQTmJVk3QEwBS8QARxxjw
Thread-topic: nv-l Digest 13 Feb 2003 09:36:36 -0000 Issue 231
We are a legacy installation of NetView, since the 4.x to 5.x days. We are 
current at 7.1 heading on the current level this year.

Our implementation was architect way back last millennium. Our mission is 
        Up/Down status polling on server class systems and network devices 
        SNMP trap processing 

        Everything munges through with a single target path: T/EC, and then an 
incident management system.

Way back when a decision was made to use /etc/hosts entries to make NetView 
objects without domain names. It allowed us not to have to truncate the names 
in T/EC. 

However, with the increased use of clustering architectures, and assigning 
multiple names and IP addresses to a physical server device, we're trying to 
grok out how to properly distinguish between a cluster server (with an 
associated IP address) and a cluster service (with another associated IP 
address) end-to-end, from interface down/node down, all the way to incident 

I would greatly appreciate any thoughts on the subject, detailed on conceptual.

Should we be evolving our NetView configuration away from a local /etc/hosts 

Can NetView handle at discovery time associating different names (derivable 
from DNS) as labels for different interfaces so we can treat a Cluster Service 
(and IP) like a virtual node from detecting interface loss through to incident 
management? We are extremely bullish on automation where possible.

Jon C Austin
Enterprise Management
Technology Operations
Bank One Card Services
(302)282-3498 (phone)

This transmission may contain information that is privileged, confidential 
and/or exempt from disclosure under applicable law. If you are not the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, 
or use of the information contained herein (including any reliance thereon) is 
STRICTLY PROHIBITED. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format. Thank you

To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web