>>> lclark@us.ibm.com 11/01/01 03:12PM
>>>
This emphasizes a point I believe I mentioned recently, and that
is:
Netview does not change the name of a node if you LOSE
name
resolution. It also does not change the value of the
'isSNMPSupported'
field if you lose SNMP access. These are two external
factors
that it pays to keep an eye on. Because of this, I like to keep
a
utility script handy and check from time to time. A script that does
an
snmpget of sysName against the Selection Name will tell you
both things at
once. This is especially helpful when you are first
setting up Netview
and it is uncovering all sorts of little anomalies
in your network. If you
have such a report, you can just hand it to
the responsible parties. And you
can use it to verify the progress
of your
cleanup.
Cordially,
Leslie A. Clark
IBM Global Services -
Systems Mgmt &
Networking
Detroit
Robin
James
<robin.james@thal
To: IBM NetView Discussion <nv-l@tkg.com>
esatm.com>
cc:
Sent
by:
Subject: Re: [NV-L]
Nameserver
owner-nv-l@tkg.co
m
11/01/01 11:38
AM
Please respond
to
IBM
NetView
Discussion
Many thanks Leslie.
Your comment sparked an idea because
the node was discovered when DNS
was running. When we cleared the databases
and started Netview again the
node was discovered without DNS and the colour
changed correctly when
the node was halted and
booted.
--
Robin
email:
robin.james@thalesatm.com
tel: +44 (0)
1633-862020
fax: +44 (0) 1633-868313
Leslie Clark
wrote:
>
> It is supposed to turn red on the map. You might check to
see if you are
> getting any ipmap errors in the nettl log or in
$HOME/nv6000.log. The
> ipmap application is one that is automatically
restarted if it fails, but
> it
> is not supposed to fail. Sounds
like a support issue to me. (If you did
> not have a DNS running on the
Netview system when you discovered
> the node, you would not need one
now.)
>
> Cordially,
>
> Leslie A. Clark
> IBM
Global Services - Systems Mgmt & Networking
>
Detroit
>
>
>
Robin
James
>
<robin.james@thal
To: NetView
Discussion
<nv-l@tkg.com>
>
esatm.com>
cc:
>
Sent
by:
Subject:
[NV-L]
Nameserver
>
owner-nv-l@tkg.co
>
m
>
>
>
11/01/01 10:03
AM
>
Please respond
to
>
IBM
NetView
>
Discussion
>
>
>
> We halted a node and its symbol
stayed green on the IP Internet submap
> instead of turning
red.
>
> The Topology Database (ovtopodump) showed the correct
state, that is the
> node was down.
>
> The trapd log showed
no Node Down/Marginal events.
>
> Tracing the netmon process
(/usr/OV/bin/netmon -M 63) showed that netmon
> correctly detected when
the node was halted. However the submap was
> never
updated.
>
> In the Netview Diagnosis Guide it describes the role of
the domain
> nameserver (DNS) in map synchronisation. As it happens the
DNS process
> was not running on our Netview computer. Is this the reason
why the
> symbol did not turn red?
>
> Does Netview require
DNS to be available or will it be able to work with
> some other means of
mapping the IP address, for example /etc/hosts ?
>
> FYI we're using
a dead-end Netview setup - NV 5.1.3 on TRU64 UNIX 5.0F
>
:-)
>
> TIA
> --
> Robin
> email:
robin.james@thalesatm.com
> tel: +44 (0) 1633-862020
>
fax: +44 (0) 1633-868313
>
_________________________________________________________________________
>
NV-L List information and Archives:
http://www.tkg.com/nv-l>
>
_________________________________________________________________________
>
NV-L List information and Archives:
http://www.tkg.com/nv-l_________________________________________________________________________
NV-L
List information and Archives:
http://www.tkg.com/nv-l_________________________________________________________________________
NV-L
List information and Archives:
http://www.tkg.com/nv-l