My next stop on the trail of voodoo problem determination would be to
adjust the configuration of snmpCollect, cutting the maxpdu size in half,
so it does not ask for so much stuff at once, turn the retry down from
1 hour to 15 minutes, and after it gets restarted, toggle tracing on
and if it still happens, see if there are any more clues in the
snmpCol.trace
file. It can get very verbose with the -T and -V options. See the
man page for the snmpCollect command.

The other voodoo thing is to reset the snmp agent on those devices,
especially the IBM switch.

Cordially,

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


                                                                                
                                                        
                      "Duble, Ethan"                                            
                                                        
                      <Ethan.Duble@coope        To:       Leslie 
Clark/Southfield/IBM@IBMUS                                             
                      rtools.com>               cc:                             
                                                        
                                                Subject:  RE: [nv-l] cant 
collect snmp on certain devices                               
                      05/13/2002 01:53                                          
                                                        
                      PM                                                        
                                                        
                                                                                
                                                        
                                                                                
                                                        



yes , to both , we only use a /etc/host file and seedfile , discovery is
turned off

i have removed it (completely) from the netview database ( easy to do with
one map ) , netmon always finds it , changes to proper icon , (cisco router
icon) , after discovery , we monitor via the seedfile using snmpstatus
polling

tis very odd

Ethan

-----Original Message-----
From: Leslie Clark [mailto:lclark AT us.ibm DOT com]
Sent: Monday, May 13, 2002 1:00 PM
To: Duble, Ethan
Subject: Re: [nv-l] cant collect snmp on certain devices


Hmm. Does that name resolve in both directions? And does it
resolve to the same address every time?

Cordially,

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




                      "Duble, Ethan"

                      <Ethan.Duble@coope        To:
nv-l AT lists.tivoli DOT com
                      rtools.com>               cc:

                                                Subject:  [nv-l] cant
collect snmp on certain devices
                      05/13/2002 12:13

                      PM








netview 7.1.1 / aix 4.3.3

I am having a problem collecting snmp information on 2 (out of 45) routers
and one ibm switch. Netview discovers them fine , snmp is running , i can
snmp walk them , browse mib etc , however when i try to graph data or look
in the snmpCollect log i see netmon message

"Tue May 07 00:55:20 2002 : SNMP send to Apex-1.cis.7206.apx returned:
        An error occurred in building out bound data.
        Deferring SNMP of all collections on Apex-1.cis.7206.apx
        60 minutes (1.00 hours).  Send event (via
        snmpCollect -C <node>) to retry sooner. "

when the next hour passes and it tries again , it fails

any ideas folks ?

Ethan
Coopertools




---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)