nv-l
[Top] [All Lists]

[nv-l] Permanently Ignore Interface?

To: nv-l@lists.us.ibm.com
Subject: [nv-l] Permanently Ignore Interface?
From: "Duppong, Jason" <jason.duppong@thomson.com>
Date: Wed, 6 Apr 2005 22:57:53 -0500
Delivery-date: Thu, 07 Apr 2005 04:58:25 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Hello List,
I think I know the answer to this already, but I wanted to bounce it off the
list anyways.  Is it possible to have Netview permanently ignore an
interface or interfaces on a node?  I know I can unmanage interfaces, but
the problem we have is interfaces that are already unmanaged somehow get
managed again when something happens to that node (I'm thinking a
configuration scan).  I've been able to narrow the problem down to a handful
of nodes whose interfaces are on the same subnet even though the nodes are
completely unrelated.  A couple other cases involve nodes with duplicate IP
addresses even though the nodes are unrelated.  As much as I would like to,
I'm unable to "fix" these problems due to the nature of these nodes.  A
search through the archives has not turned up anything that helpful, so I'm
hoping someone might have a better solution then what I'm currently doing or
planning.  Currently I have a cron job that unmanages the interfaces in
question.  I'm thinking about writing a script that would collect the MAC
addresses on the problem interfaces and use the list in our alerting
infrastructure to drop any alert from these interfaces, but since we don't
really care about these interfaces at all, the ideal solution would be to
configure Netview so it simply ignores everything about the interface.

Thanks for any help in advance!

Jason Duppong
Senior Systems Engineer
Thomson Legal and Regulatory Technical Services

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

Archive operated by Skills 1st Ltd

See also: The NetView Web