|
RE: [nv-l] How to permanently set nodes to unmanged state
2005-05-12 13:12:02
Glen,
Just want to cover two items to make
sure they are not the cause of your problem:
1) Do a "ps -ef |grep netmon"
and confirm that netmon is using the seedfile you are expecting it to use
2) Adding negative entries will not
remove nodes that are already discovered. You would need to delete "object"
from "all" submaps (and "all" maps if you have more
than one) first.
3) netmon will not partial discover
a device, so if a device as multiple interfaces and was discovered with
an interface that is not negated in the seedfile, all interfaces will be
discovered regardless of negative entries.
If netmon is truely using a seedfile
with negative entries (and the nodes are not already discovered), netmon
should not discover them.....if they are being wrongly discovered, then
I would suggest turning on full netmon tracing, capturing the rediscovery
of these devices, and providing the netmon.trace, trapd.log , and netmon
seedfile to NetView Support to help you debug.
Cheers,
Gareth Holl
Staff Software Engineer
gholl AT us.ibm DOT com
ITIL Foundations Certified
IBM Certified Deployment Professional
--Tivoli Data Warehouse v1.2
--Tivoli Enterprise Console v3.8 Network
Management
IBM Software Group - Tivoli Software
Research Triangle Park, North Carolina.
"Glen Warn" <Glen.Warn AT pemcocorp DOT com>
Sent by: owner-nv-l AT lists.us.ibm DOT com
05/12/2005 12:59 PM
|
|
To
| <nv-l AT lists.us.ibm DOT com>
|
|
cc
|
|
|
Subject
| RE: [nv-l] How to permanently
set nodes to unmanged state |
|
Hi Paul,
I've actually tried putting them in both ways:
!10.10.10.25-35 (as an example)
or
!10.10.10.25
!10.10.10.26
!10.10.10.27
!10.10.10.28
etc
Neither seem to make Netview ignore them. I am assuming the
#Workstations is a comment on the end of line for admin purposes - if
that is wrong please let me know.
Glen Warn
PEMCO Corporation Computer Services (PCCS)
glen.warn AT pemcocorp DOT com
206-628-5770
-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]
On Behalf Of Paul
Sent: Thursday, May 12, 2005 9:28 AM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] How to permanently set nodes to unmanged state
Glen,
If its a range of addresses you can add something like this to the
seedfile:
!10.10.10.25-200 #Workstations
Or something like that. Im not sure how the "limit discovery"
puts it
int the seedfile off the top of my head.
Paul
Glen Warn wrote:
>Hi Paul,
>
>Good point. I've tried adding them to the netmon.seed "limit
discovery"
>but they still keep getting discovered. Any ideas?
>
>
>Glen Warn
>PEMCO Corporation Computer Services (PCCS) glen.warn AT pemcocorp DOT com
>206-628-5770
>
>-----Original Message-----
>From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]
>On Behalf Of Paul
>Sent: Tuesday, May 03, 2005 4:10 AM
>To: nv-l AT lists.us.ibm DOT com
>Subject: Re: [nv-l] How to permanently set nodes to unmanged state
>
>Glen,
>Why discover them in the first place?
>
>Paul
>
>
>Glen Warn wrote:
>
>
>
>>I have several remote access subnets (a few dial, some vpn) where
>>remote users are allocated DHCP addresses. I do not want
to manage
>>these nodes and set them to unmanaged - but Netview keeps setting
them
>>
>>
>
>
>
>>back to managed (and inevitably changes their state to down) -
I
>>suspect because it detects the connection as new (different MAC
>>address perhaps) even though the IPs are the same. Is there
way to
>>permanently set a block of addresses to unmanaged?
>>
>>Netview 7.1.4
>>
>>Thanks for your time,
>>Glen Warn
>>PEMCO Corporation Computer Services (PCCS) glen.warn AT pemcocorp DOT com
>><mailto:glen.warn AT pemcocorp DOT com> 206-628-5770
>>
>>
>>
>
>
>
>
>
>
>
>
|
|
|
