Craig White wrote:
>
> OK, I've been tracking this conversation, installed/configured/started
> OpenNMS and have discovered everything and in fact, edited
> service-configuration.xml as recommended.
>
> I'm sort of comparing this to Zenoss which I had to stop (snmp
> conflicts) to run OpenNMS.
>
> I can see each port on the 48 port managed switch and go to 'View Node
> Link Detailed Info' but it doesn't tell me much about the
> device/computer plugged into a specific port.
Let it soak overnight. It goes out of its way not to kill your network
and has a long startup delay and times between polls - all tunable in
the xml files, of course.
> While I don't want to be quick to dismiss OpenNMS, it seems to fall way
> short of Zenoss so I'm thinking that there's a bunch of stuff that
> probably needs to be tweaked.
It mostly does the right thing by default, although if you want
bandwidth graphs on the non-IP ports on your switches you either need to
set it up for each node or change snmpStorageFlag to "all'
in datacollection-config.xml
I am interested in a comparison with Zenoss - but wait until you know
your way around opennms. Just ask on the opennms list if it doesn't do
something you expect.
> I got the impression that NetDisco would actually tell me the IP Address
> (perhaps reverse the DNS name) of the device connected to specific port
> on my managed switch. I didn't go for the NetDisco route for install
> because I didn't like the idea of getting a bunch of CPAN perl modules
> installed rather than using rpm packages.
Assuming it can get the info from the switch, it will - and give you
clickable link to the other device's node info.
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
