nv-l

Re: nslookup on the Server and device labels...

1999-06-13 19:13:53
Subject: Re: nslookup on the Server and device labels...
From: Leslie Clark <lclark AT US.IBM DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Sun, 13 Jun 1999 19:13:53 -0400
I believe you were misinformed. The labels on the map will stop at the
first dot in the  object name. The actual SelectionName will be long, but
the label will be short. Since SelectionNames are usually only handled
programmatically, their length should not be a big issue.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking



Hello All.

I am about to perform my migration of Netview from 4.1 to 5.1.
I recently had to enable both forward and reverse name resolution on the
Netview Server before I could make it a Managed Node within my TMR.

Now, I have been informed that the reason only half the name resolution was
enabled (i.e. can do a nslookup server_hostname but not a nslookup
server_IP)on the Netview V4.1 Server was because any devices discovered
would have the full label, i.e. "someServer.machine.domain.com" instead of
just "someServer". All of these 'long' hostnames would make the Map
unbearable to read. Thus, sometime again, name resolution was limited)

So my question is, once I migrate to Netview 5.1 (keeping in ming that  I
have enable both forward and reverse name resolution on the Netview server)
will all of my ~2000 devices now come up with the 'long' hostnames instead
of the 'short' hostnames they presently have?

And secondly, will newly discovered devices have the 'long' hostname ?

If anyone has any experience with this, any insight would be greatly
appreciated.

Sincerely,

Gord Michaels.







______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

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