It looks to me like the interface is managed even though the box is
not. Note that the TopM Inteface list shows that the interface has a
status of Up. That should say Unmanaged. At certain code levels,
and under certain conditions, it is possible that the 'unmanage' did
not soak all the way down to the interface level. I would make sure
you are at the latest code level, and then do some database
maintenance, and manage/unmanage those things again. I promise
you that you are not supposed to be getting Netview events about
unmanaged nodes. That's what Unmanaged means - netmon ignores
them.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
pweischer@MMM.COM@tkg.com on 05/14/2001 08:15:37 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: IBM NetView Discussion <nv-l@tkg.com>
Subject: Re: [NV-L] Events from unmanaged nodes
I use the 'default' map only. The events I am talking about are NetView
events.
What could be wrong?
Regards
Peter Weischer
-----------------------------------------------------------------------
Event Monitor entry:
05/14/01 12:57:37 PM,Critical,DEDD100170,Interface 169.5.19.86 down.
CRITICAL,,1.3.6.1.4.1.2.6.3,58916867,Netmon-related,
ovobjprint output:
D:\usr\nv_config>ovobjprint -s DEDD100170
OBJECTID SELECTION NAME
OBJECT: 660
FIELD ID FIELD NAME FIELD VALUE
10 Selection Name "DEDD100170"
11 IP Hostname "DEDD100170"
14 OVW Maps Exists 1
15 OVW Maps Managed 0
73 IP Status Unmanaged(5)
76 isIPRouter FALSE
99 IP Name "DEDD100170"
103 vendor Unset(0)
114 isNode TRUE
116 isComputer TRUE
117 isConnector FALSE
119 isBridge FALSE
120 isRouter FALSE
121 isHub FALSE
141 isDHCPClient FALSE
147 isIP TRUE
170 manually_managed FALSE
172 isSNMPSupported FALSE
178 SNMPAgent Unset(0)
215 TopM Interface Count 1
221 TopM Interface List "169.5.19.86 Down
169.5.19.86 255.255.248.0 <None>
other "
244 XXMAP Protocol List "IP"
|--------+------------------------->
| | "Leslie Clark" |
| | <lclark@us.ibm.|
| | com> |
| | |
| | 14.05.2001 |
| | 06:27 |
| | Please respond |
| | to IBM NetView |
| | Discussion |
| | |
|--------+------------------------->
>--------------------------------------------------------------------|
| |
| To: IBM NetView Discussion <nv-l@tkg.com> |
| cc: (bcc: Peter Weischer/GE-Europe/3M/US) |
| Subject: Re: [NV-L] Events from unmanaged nodes |
>--------------------------------------------------------------------|
Let's be clear about this. If a node is unmanaged IN ALL MAPS, then
there will be NO interface up/down events generated. This is true on
NT as well as on AIX. If you are getting Netview events for unmanaged
nodes, you must therefore have more than one map, and the nodes
are managed in at least one of those maps.
If you have thousands of unwanted workstations, you can exclude
them from discovery by using a seedfile; you can also umanaged
them.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
John Nicholson <jnicholson@epo.org>@tkg.com on 05/09/2001 06:05:33 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] Events from unmanaged nodes
I see the same on NetView 6.01 for NT; the only way I found to avoid
pinging
thousands of unmanaged workstations was to turn off discovery and delete
them.
On AIX, unmanaging nodes _does_ stop netmon pinging them - surely it is
supposed
to work the same way on NT?
Regards,
John Nicholson
pweischer@mmm.com wrote:
> Hello,
> in the event browser of NetView 6.02 for NT, I can see interface up/down
and
> node up/down events of unmanaged nodes. Is that correct?
>
> Regards
>
> Peter Weischer
>
> _________________________________________________________________________
> 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
|