The use of collections in SNMP config was put in as an aid to defining
polling criteria, not alternate community names, which is why you find it
hard to use for that purpose.
The 2048 character limit is an architectural one and cannot be altered by
any user action.
The only alternative I see for you is to use wild card entries based upon
the IP addresses of your new devices.
Otherwise you will have to put an entry in our SNMP config for each of them
just as you put an entry into DNS for each of them. I know this is a lot
of work but within the limits of the current design there are no
alternatives.
I am sorry that the function doesn't do what you want. If you would like
to see it changed to better assist you, then please send a note to
netview@tivoli.com for consideration in a future release.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Prokott, Joe" <Joe.Prokott@WESTGROUP.COM> on 01/21/99 03:22:11 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: James Shanks)
Subject: Defining Collections BEFORE Discovery so Collection "SNMP Config.
" can be used
How can I extend the length of defining a NV rule from 2048 characters? We
are using collection definitions for BOTH "SNMP Configuration" and grouping
of similar devices together. Since we are using NV collections for
defining
SNMP community names, the device name must be in the NV rule *before* the
device is actually in the NV database. If it is not, the correct community
name used for initial NV discovery will NOT be used.
Thus, we must use an "Object List" to create the collection. Is there any
other way of defining the collection other than using the "Object List" if
we need to define a collection rule before the device is actually defined
in
the NV database? If so, how? If not, how can I extend the NV rule so that
I can put more that 2048 charaters in the definition of the rule? We have
some collections that have 300+ nodes and an object list that includes all
of these nodes is much longer than 2048 characters.
I find the support for the "SNMP Configuraion" to accept entries based on
collection is a catch 22 - the community name is needed BEFORE initial
discovery, yet all NV collection rules except "Object List" rely on NV
database fields determined AFTER initial discovery. So, how can I most
effectively define these collection rules to define the community name for
a
collection of devices, without having the device already discovered? After
all, if the device is already discovered correctly in NV, shouldn't the
community name already be correctly defined and why would I need to define
the community name for the collection?
Joe Prokott - West Group
Network Architect
610 Opperman Drive
St. Paul, MN 55123
Phone: 651-687-4536
Fax: 651-687-6946
E-mail: joe.prokott@westgroup.com
|