Now it gets interesting, I've narrowed it down. Reverse lookup is OK
now, but that's not it. For some reason ustivux02's object properties do
not show isManager=TRUE. I've rediscovered it with no change. Pretty
sure the reason it's reporting ustivux01 as UP is because that server is
in the Manager submap. It's not reporting ux02 as up because it doesn't
think it's a NetView server--there's no renaming issue at all.
I searched on this in the archives and assumed a rediscover would take
care of it. Snmpd.conf is identical to ustivux01's settings.
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of James Shanks
Sent: Thursday, August 18, 2005 10:14 AM
Subject: Re: [nv-l] Internal NetView UP trap reporting wrong hostname
Never seen this before.
reset_ci rebuilds the ovorsd section of the database. You can check
in it with ovorsutil -d.
Does that show that we think we are on ustivux02 or ustivux01?
If that's correct, then I don't think anything went wrong with the
Are you certain that the /etc/hosts file on this box is correct and that
matches what's in DNS?
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited. [v.E.1]