nv-l

Re: [nv-l] Vital QIP and NetView....what if

2003-08-07 17:46:09
Subject: Re: [nv-l] Vital QIP and NetView....what if
From: Paul <pstroud AT bellsouth DOT net>
To: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
Date: Thu, 07 Aug 2003 17:32:47 -0400
I assume you have a known range of addresses or a name you could build a smartset
off of?

What if you set the node down delete interval to something around 5 minutes for this
smartset?

I don't know if this will work or not, I worked this problem with Scott in the beginning
and this never dawned on me at the time....might be worth a try.

Paul




Barr, Scott wrote:

This is only a problem on the non-windows version of NetView. I have made an enhancement request um, about two years ago to have the Unix version of NetView properly handle DHCP desktops.
The ways we tried (unsucessfully) to fix this was to unmanage the old
interface and demand poll the box but that didn't work because the box
became unmanaged and therefore discovery poll didn't pick up the
change - since it never got a discover poll since it was unmanaged.
If you come up with a solution before IBM codes the appropriate
support for DHCP in NetView I would be interested in what you do. This
is neither a new problem nor a small problem but I haven't gotten
anywhere trying to get around it.
PMR numbers are available on request.

-----Original Message-----
From:   Cowan, Christopher [mailto:Christopher_Cowan AT sra DOT com]
Sent:   Thu 8/7/2003 3:40 PM
To:     'nv-l AT lists.tivoli DOT com'
Cc: Subject: [nv-l] Vital QIP and NetView I just noticed another in a string of annoyances generated by my customer's
use of Vital QIP.   The most recent one was with NetView.

Basically, I have non-SNMP managed desktops (of course that almost goes
without saying, since nobody SNMP manages their desktops ;) that have their
DHCP lease expire.   They quickly get a new address, with the appropriate
changes made to DNS by QIP.   The old address may also be reclaimed fairly
quickly, as well.
There are several race conditions here that contribute to the problem.
Basically, netmon does not follow the address change, and assumes it is
seeing a NIC added to the host.    It then depicts it as a router. I am
running NetView 7.1.3 on Solaris, so to the best of my knowledge it doesn't
have the dhcp option flag in the seed file (like the windows version).

Bottom line: I wondering if there an easy way to prevent netmon from making this assumption given Vital's behavior?
--
Chris Cowan
Sr. ESM Consultant
SRA International

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

*NOTE*
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)





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

*NOTE*
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>