How high you can set it depends on your adapter and network, but
I would be comfortable trying -Q 32 almost anywhere. I would also
look for other reasons for it being behind. If you are using the OID
entries in the seedfile to exclude discovery, keep in mind that netmon
checks those stub objects reqularly to see if they have turned into
something that is allowed, and if they are non-snmp, that could tie
things up. Also if you have lots of non-snmp things (or stubs) and have
long timeout/retry settings that apply to them. In that case you
should consider refining those timeout settings so that they are
only long where they are needed.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit


"Westphal, Raymond" <RWestphal AT erac DOT com>@tkg.com on 03/06/2001 11:41:26 
AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   "NV List (E-mail)" <nv-l AT tkg DOT com>
cc:
Subject:  [NV-L] SNMP Queue Size



Hello Everyone.

I manage a NetView for Unix 6.0.1 server on AIX. ovobjprint -S shows
approximately 20,000 objects. netmon is always behind on the snmp polling
and never behind on the icmp status polling.

Would you recommend increasing the SNMP queue size?

Thanks.

Ray Westphal
Enterprise Rent-A-Car


_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l