nv-l

Re: [nv-l] Howto list only managed nodes ???

2005-11-03 16:30:57
Subject: Re: [nv-l] Howto list only managed nodes ???
From: Jane Curry <jane.curry AT skills-1st.co DOT uk>
To: nv-l AT lists.us.ibm DOT com
Date: Thu, 03 Nov 2005 21:25:49 +0000
If you are about to get deluged with a load of PCs that you don't want to discover at all, a common assumption (not always correct, but sometimes good) is that "PCs" don't support SNMP. If that holds good for you, you could put an entry in your seedfile of:
@OID .1.3.6.1.*

This says ONLY to discover something that returns any valid OID - non-SNMP nodes won't get discovered. If you explicitly want to prohibit discovery of Windows PCs with a contactable SNMP agent, you could use in the seedfile:
!@OID .1.3.6.1.4.1.311.*

This says DON'T discover SNMP-capable nodes from the Mr Gates empire (the 311 bit).

As James and Paul have suggested, if you don't have a remit to manage PCs - you are far better off preventing their discovery in the first place.

Cheers,
Jane

James Shanks wrote:

This node is not unmanaged.  Both

75              IP Status                       Normal(2)
15              OVW Maps Managed                1

indicate that.  When a node is unmanaged, the maps managed count will be
zero and the IP Status will be Unmanaged.

You cannot automate what you don't understand, so your first job will be to
try to create smartsets to cull out the various PC's you eventually want to
unmanage.  Use ovobjprint to print the database, and then find
representative samples.  Then try creating smartsets to group them based on
common characteristics, vendor, isComputer, whatever.    This is likely to
be an iterative process.  Rome wasn't built in ad ay and neither will you
be able to get control of an out-of-control installation in a day either.

If there was no mandate to manage the PC's, then perhaps a better approach
than trying unmanage thousands of devices you don't care about would have
been to limit discover to just those things you do care about.  You can do
that in the seed file.  But then you have to delete and rediscover the
entire network.  serversetup gives you that option.

My 2 cents

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group



--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <jane.curry AT skills-1st.co DOT uk>.  All rights 
reserved.