Hey Matt, Thanks for sticking with this.
On Friday, I fixed a problem modeling hard disks on windows boxen that have the SNMP informant stuff loaded on them. That fixes a common problem in recent releases. I think this is the problem you are having. > ImportError: No module named pysnmp Ugh.. my mistake. I did test this before sending to you, but I copied the wrong command to the message. Try this: python -c 'import pynetsnmp.netsnmp; print pynetsnmp.netsnmp.version' Another problem on friday: using the edit screen for a device would set the zSnmpVer string to empty, so make sure that it's set to "1" or "2c" as appropriate (seems you have). -Eric mwatson wrote: > running: > "python -c 'import pynetsnmp.pysnmp; print pynetsnmp.pysnmp.version' " > > I get: > > Traceback (most recent call last): > File "<string>", line 1, in ? > ImportError: No module named pysnmp > > > I;m sure this is probably just me doing something pretty stupid - my > knowledge of python is not all that grand. > > however... > > [EMAIL PROTECTED]:~/zenoss$ snmpwalk -V > NET-SNMP version: 5.3.1 > > Its also on a 32bit Ubuntu box running Gutsy Gibon - the Windows box is also > a 32bit box and is WIn2k3 standard (all 3 of them) > > I have since however found another commonality between the 2 machines that > are not working and a difference to the one that is not. > > > The 2 boxes having an issue both have the Dell OpenManage / Server > Administrator stuff on it, while the 3rd machine that Zenoss is talking to OK > does not have it installed. > > I have a funny feeling that this is the problem - I know that the openmanage > stuff does include snmp stuff - however like I said before, these 2 boxes > work just fine with a zenoss 2.0.0-2.0.5 install (haven;t tried 2.0.6 but i > have no reason tot hink it wouldn;t work). > > > > As for seting the zSnmpVer zProperty - my 1 Windows box that is working fine > had been set to "v2c", one that was not working was blank, and the other that > was not working had "1" - i;ve since tried setting 1 in both of the > non-working boxes and v2c for both as well, no setting seems to do the trick > there. > > Something else that I should point out, is that Zenoss does ADD and model the > device perfect fine through SNMP. > > I just deleted my device "LAWRENCE" went to "Add Device" > > This is what I;ve filled in: > > Device Name: 10.10.1.31 > Device Class Path: /Server/Windows > SNMP COmmunity: <My RO community here> > SNMP Port: left at default "161" > tag number: <blank> > serial number: <blank> > Production State: Production > Priority: Normal > Rack Slot left at default "0" > Comments: <Blank> > HW Manufacturer: "Dell" (I created the Dell manufacter since it seems 2.0.90 > doesn;t have these pre-populated) > HW Product: "PowerEdge 750" (again I created this) > OS Manufacturer: "Microsoft" (I created again) > OS Product: "WIndows Server 2003 Standard" (I created again) > Location Path: "/NCGC1" > Systems: "/MAIL" & "/ACCESS" > Groups: "/CN" & "/ADMIN" > > > > > This is what gets spewed back to me in the web interface: > > Add Device > > Time Level Module Message > 2007-09-21 17:24:12 INFO zen.Device device name 'LAWRENCE' for ip > '10.10.1.31' > 2007-09-21 17:24:12 INFO zen.Device setting hardware manufacturer > to Dell productName to PowerEdge 750 > 2007-09-21 17:24:12 INFO zen.Device setting os manufacturer to > Microsoft productName to Windows Server 2003 Standard > 2007-09-21 17:24:12 INFO zen.Device setting location to /NCGC1 > 2007-09-21 17:24:12 INFO zen.Device setting group ['/ADMIN', '/CN'] > 2007-09-21 17:24:12 INFO zen.Device setting system ['/ACCESS', > '/MAIL'] > 2007-09-21 17:24:12 INFO zen.Device setting status monitor to > ['localhost'] > 2007-09-21 17:24:12 INFO zen.Device setting performance monitor to > localhost > 2007-09-21 17:24:12 INFO zen.Device Executing command: > /home/zenoss/zenoss/bin/zenmodeler run --now -F -d LAWRENCE > 2007-09-21 17:24:19 INFO zen.Device INFO:zen.ZenModeler:starting > collector loop > 2007-09-21 17:24:19 INFO zen.Device INFO:zen.ZenModeler:collecting > for device LAWRENCE > 2007-09-21 17:24:19 INFO zen.Device INFO:zen.ZenModeler:no cmd > plugins found for LAWRENCE > 2007-09-21 17:24:19 INFO zen.Device INFO:zen.ZenModeler:snmp > collection device LAWRENCE > 2007-09-21 17:24:19 INFO zen.Device INFO:zen.ZenModeler:plugins: > zenoss.snmp.IpServiceMap, zenoss.snmp.InformantHardDiskMap, > zenoss.snmp.InterfaceMap, zenoss.snmp.DeviceMap, zenoss.snmp.HPDeviceMap, > zenoss.snmp.HRSWInstalledMap, zenoss.snmp.DellCPUMap, zenoss.snmp.CpuMap, > zenoss.snmp.HPCPUMap, zenoss.snmp.DellPCIMap, zenoss.snmp.DellDeviceMap, > zenoss.snmp.RouteMap, zenoss.snmp.HRSWRunMap, zenoss.snmp.HRFileSystemMap > 2007-09-21 17:24:19 INFO zen.Device INFO:zen.ZenModeler:no portscan > plugins found for LAWRENCE > 2007-09-21 17:24:21 INFO zen.Device INFO:zen.SnmpClient:snmp client > finished collection for LAWRENCE > 2007-09-21 17:24:21 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.IpServiceMap for device LAWRENCE > 2007-09-21 17:24:27 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.InformantHardDiskMap for device > LAWRENCE > 2007-09-21 17:24:28 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.InterfaceMap for device LAWRENCE > 2007-09-21 17:24:28 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.DeviceMap for device LAWRENCE > 2007-09-21 17:24:29 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.HPDeviceMap for device LAWRENCE > 2007-09-21 17:24:29 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.HRSWInstalledMap for device > LAWRENCE > 2007-09-21 17:24:34 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.DellCPUMap for device LAWRENCE > 2007-09-21 17:24:34 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.CpuMap for device LAWRENCE > 2007-09-21 17:24:34 INFO zen.Device > WARNING:zen.ApplyDataMap:attribute description not found on object 0 > 2007-09-21 17:24:35 INFO zen.Device > WARNING:zen.ApplyDataMap:attribute description not found on object 1 > 2007-09-21 17:24:35 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.HPCPUMap for device LAWRENCE > 2007-09-21 17:24:35 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.DellPCIMap for device LAWRENCE > 2007-09-21 17:24:35 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.DellDeviceMap for device LAWRENCE > 2007-09-21 17:24:35 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.RouteMap for device LAWRENCE > 2007-09-21 17:24:36 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.HRSWRunMap for device LAWRENCE > 2007-09-21 17:24:36 INFO zen.Device > INFO:zen.ApplyDataMap:processing zenoss.snmp.HRFileSystemMap for device > LAWRENCE > 2007-09-21 17:24:36 INFO zen.Device INFO:zen.ApplyDataMap:changes > applied > 2007-09-21 17:24:37 INFO zen.Device INFO:zen.ZenModeler:scan time: > 18.13 seconds > 2007-09-21 17:24:37 INFO zen.Device INFO:zen.ZenModeler:stopping... > 2007-09-21 17:24:39 INFO zen.DeviceLoader device 10.10.1.31 > loaded! > > > > > So there are no serious errors there at all and it collected all of that > through snmp. Just as zenoss monitors the box the errors appear. > > Like I said, I have a feeling that it has something to do with the dell > server administrator stuff... maybe server administrator is sending a > response that zenoss was expecting in a different format? I;m not sure... > > ------------------------ > Matt Watson > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://community.zenoss.com/forums/viewtopic.php?p=10969#10969 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users > _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
