Hi list,
sorry for the noise, it seems that SNMP implementation on Sun
machines is far from being state-of-the art, digging on SunSolve I
found tens of bug reports.
My apologies to Intermapper folks, this is a Sun problem. In fact if
you do a simple snmpwalk to the SP processor of a Sun v20z you get:
# snmpwalk -t 20 -v 2c -c public <IP_REMOVED>
SNMPv2-MIB::sysDescr.0 = STRING: Linux localhost 2.4.18 #1 Fri Apr 1
15:23:25 CST 2005 ppc
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9237.2.1
SNMPv2-MIB::sysUpTime.0 = Timeticks: (28297624) 3 days, 6:36:16.24
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING: localhost
SNMPv2-MIB::sysLocation.0 = STRING:
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (32) 0:00:00.32
SNMPv2-MIB::sysORID.1 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.2 = OID: SNMP-FRAMEWORK-
MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.3 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORDescr.1 = STRING: View-based Access Control Model
for SNMP.
SNMPv2-MIB::sysORDescr.2 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.3 = STRING: The MIB for Message Processing and
Dispatching.
SNMPv2-MIB::sysORDescr.4 = STRING: The management information
definitions for the SNMP User-based Security Model.
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (31) 0:00:00.31
SNMPv2-MIB::sysORUpTime.2 = Timeticks: (31) 0:00:00.31
SNMPv2-MIB::sysORUpTime.3 = Timeticks: (31) 0:00:00.31
SNMPv2-MIB::sysORUpTime.4 = Timeticks: (32) 0:00:00.32
and then it timeouts without browsing all the other OIDS. Raising the
timeout treshold does not help so it's an SNMP implementation problem
on the v20z side.
My apologies again to the list, ciao
Alessandro
On Nov 13, 2006, at 1:45 PM, Alessandro Dellavedova wrote:
Hi Jakob,
thanks for your hints, unfortunately the problem is still there but
I can add another piece to the mosaic.
The problem is not in my probe, since also the basic SNMP - Basic
OID distributed with Intermapper has the same symptoms:
13:40:48 SNMP pkt not handled from <IP_REMOVED>, ID = 13dd9820
I suppose it's an Intermapper internal SNMP parser problem, I hope
that some IM engineer can take a look at this (yes, I can open the
firewall if you need to test).
Thanks,
Alessandro
------------------------------------------------------------
Alessandro Dellavedova
IT Manager
European Institute of Oncology - Department of Experimental Oncology
Via Ripamonti, 435 - 20141 Milano (Italy)
[EMAIL PROTECTED]
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
