nv-l
[Top] [All Lists]

Re: dns/host/win2k dns and netview

To: nv-l@lists.tivoli.com
Subject: Re: dns/host/win2k dns and netview
From: netview@toddh.net (Todd H.)
Date: 22 Oct 2001 15:44:32 -0500
This issue of "Any way to shorten the FQDN when netview reports
alerts, or are ya stuck with what your resolver gives ya?" came up in
our recent NetView class that Scott and I attended.

As leslie mentioned, having a "hosts then DNS" policy along with
listing only shortnames in /etc/hosts does work around it, but creates
added administrative overhead of synchronizing DNS and /etc/hosts.

I think we concluded in the class that you can run a script to export
the object database (/usr/OV/bin/nvdbformat), chop down the selection
name to the hostname, and then update the object database accordingly
(with /usr/OV/bin/nvdbimport)--without having to do DNS tricks.  There
are man pages for each of these.

For autodiscovery folks, then the question is maintenance.  I think
Scott was whipping up a script to be launched when the internal
NetView "node added" internal trap was seen--the script would fixup
the selection name to be the hostname alone on the fly. 

Can anyone think of any downsides to this other than the possibility
of a name collision?

-- 


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

Archive operated by Skills 1st Ltd

See also: The NetView Web