Hi Carl,
Check that the remote devices support the TCP-MIB.
$ snmpwalk -v1 -c <community> <ip-address> .1.3.6.1.2.1.6.13.1.1
Alternatively, you could switch on port scanning. Change
zTransportPreference zProperty to "snmp|portscan".
-Eric
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=4542#4542
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
mrcarl81 wrote:
ah, alright. My feet are a little more wet now. I jumped in and modeled the
device and I'll just stick with v1. I wanted to make sure that there was not
some sort of major feature that I would miss out on if I didn't use a later
version or read-write.
It looks like most of the stuff worked. Its collecting performance data on the
processors, memory, and network. And its got a pretty good idea for most of
the stuff that's going on.
Still, under the hardware tab it only has information for the memory and nothing else. Is there a configuration option that I've got wrong such that it cannot discover what processors are in the system? When adding the devices I did model everything under /Device/Server/Linux
Also, I noticed that on the machine Zenoss is running on (which is also
debian), things showed up a little differently. For example, ssh and a number
of other services show up for the Zenoss machine but not the nodes I'm adding
even though they are all /Device/Server/Linux and both running ssh. Is there
something that Zenoss does differently to probe the Zenoss server? (I did look
at that blurb in the manual to make sure that the output of uname -n matched
the name of the device in zenoss).
------------------------
Carl Van Arsdall
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
