[Top] [All Lists]

Re: [NV-L] Interface Down

To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Subject: Re: [NV-L] Interface Down
From: James Shanks <jshanks@us.ibm.com>
Date: Wed, 5 Dec 2007 11:34:45 -0500
Delivery-date: Wed, 05 Dec 2007 16:32:42 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <620938.97584.qm@web43133.mail.sp1.yahoo.com>
List-help: <mailto:nv-l-request@lists.ca.ibm.com?subject=help>
List-id: Tivoli NetView Discussions <nv-l.lists.ca.ibm.com>
List-post: <mailto:nv-l@lists.ca.ibm.com>
List-subscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe>
List-unsubscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe>
Reply-to: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Sender: nv-l-bounces@lists.ca.ibm.com
Yes, it's by design.  netmon only sends an interface down event when the
interface was up on the previous check.  That's the whole point, that this
is new information.   It knows what it  what the last status was because
it's stored in the topology database.

I'm not at all sure what kind of a solution you are asking for.  Why should
netmon send you a duplicate event?  I did not follow your remarks about
TEC and Remedy , so I don't see how that is relevant.   What I got from
your first post was that your operations people messed up.  How is NetView
supposed to prevent that?

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp

NV-L mailing list
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)

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

Archive operated by Skills 1st Ltd

See also: The NetView Web