Dave,
Loading mibs right now only helps with snmp trap parsing not model
collection. Model collection is controlled by plugins that map the
"real world" to the zenoss model. Our default plugin for interfaces
uses the MIB-II interface and ip tables. I'm guessing that your
firewall doesn't publish the vlans in this mib. We can also collect
interfaces over ssh or telnet by running commands on the remote box.
Take a look at $ZENHOME/DataCollector/plugins/zenoss/cmd/linux/
ifconfig.py for an example. Unfortunately, writing a plugin is not
well documented yet.
-EAD
On Aug 31, 2006, at 2:28 PM, DAVE CUSHING wrote:
I have a fortigate 3000 firewall that I wish to monitor using ZenOSS.
It has a gigabit interface that has 45 different VLANs on it that form
part of our internal network. To the Fortigate these all appear as
separate interfaces, but ZenOSS only shows performance stats for the
parent interface and not the VLAN sub- interfaces.
I have loaded the MIB and re- discovered the device, but that didn't
seem to make any difference at all. How would I get ZENOSS to gather
performance data 'automagically' for these interfaces? It would be
terribly onerous to have to enter OIDs for all 40 odd interfaces.
Is there a way I can leverage the information in the MIB? I don't see
the benefit of loading the MIB in, as I cannot find any reference to
the
OIDs contained in the MIB in ZENOSS anywhere.
Thanks for helping out a newbie :)
_______________________________________________
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
