I agree. I am generally game to try just about anything, but I would
not be brave enough to manipulate Selection Name, or any other 'name'
type field in Netview's database using nvdbimport. I always
thought it was a bit of an oversight that nvdbimport allowed that
to be done. Before going too far with this, I would first make sure
that you can actually delete such a renamed node.
This is a discovery package, not a drawing package. If you are
going to manipulate it to that extent, I suspect that you are going
to wind up covering up problems that Netview is trying to reveal.
So take a backup!
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
James
Shanks/Raleigh To: IBM NetView Discussion
<nv-l@tkg.com>
/IBM@IBMUS cc:
Sent by: Subject: RE: [NV-L] dns/host/win2k
dns
owner-nv-l@tkg and netview
.com
10/23/01 09:17
AM
Please respond
to IBM NetView
Discussion
I am not certain about this, but you could have problems later if you
follow this procedure.
I am thinking specifically about events issues, such as "highlight node on
map" or "query smartset" in a ruleset. If the trap comes in
fully-qualified, and your selection name is not, then I am not certain that
either of those two things will work.
Charlie may be on to something with what he showed you, but he has not
showed it to anyone in NetView Support and it has not been rigorously
tested by Verification, I'll guarantee you that. And I don't think we are
not prepared to take an APAR to make this work if it does not. So I'd be
careful about implementing something this radical.
James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com
"Barr, Scott"
<Scott_Barr@csgsystems.com> To: "'IBM NetView
Sent by: owner-nv-l@tkg.com Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L]
10/23/2001 08:52 AM dns/host/win2k dns and netview
Please respond to IBM NetView
Discussion
If selection name is the issue - we wrote a script in Administrators class
that we added to the xnmtrap config for "Node Added" trap. When discovery
occurs the script is called and strips the selection name. Run discovery
and
voila, selection names on "IsNode"=yes objects has the domain name
stripped.
Thanks to Charlie "Bubba" for the script help. If anyone wants it let me
know.
-----Original Message-----
From: Jane Curry [mailto:jane.curry@skills-1st.co.uk]
Sent: Tuesday, October 23, 2001 1:59 AM
To: IBM NetView Discussion
Subject: Re: [NV-L] dns/host/win2k dns and netview
I'm not sure what the heartache is over long names. NetView is sensible
enough to put short names in labels on the topology GUI (even though it
discovers FQDN and uses these for the Selection Name field). My personal
rule is to ensure DNS is up, working and comprehensive before going
anywhere
NetView. The administrative overhead of getting /etc/hosts in synch is
just
not worth the effort - and what do you do re multi-homed hosts? /etc/hosts
cannot resolve multiple addresses to a single name.
The other question is what do you do when you have a machine name clash
(company mergers, departments going UDI,...)?? DNS is designed to give
global resolution and definitely scales to meet that challenge.
If you are looking to produce reports from your event log / trapd.log that
you explicitly want to have short names, I'd be more tempted to look at
post-processing in my report generation, to strip off the domain name.
Cheers,
Jane
"Todd H." wrote:
> 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?
>
> --
> Todd H.
> http://www.toddh.net/
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
--
Tivoli Certified Enterprise Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2001 Jane Curry <jane.curry@skills-1st.co.uk>. All rights
reserved.
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|