Hear, hear. But don't make the mistake one customer I know of made,
and put your main DNS on the same box as Netview. You do want to be
able to reboot you Netview system without scheduling an outage at
midnight to avoid inconveniencing users!
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
James_Shanks@TIVOLI.COM@tkg.com on 11/03/2000 11:19:12 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: Re: [NV-L] NetView status polling and DNS
Trapd relies heavily on name resolution -- there are two names to resolve
in every trap -- and the same kind of resolution happens down the line in
nvcorrd and actionsvr, if you are running rulesets which look a hostnames.
As has been said before, putting at least a caching DNS on the NetView box
or even in the same subnet is often the single greatest thing you can do to
improve performance.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|