Linux active agent interface discovery problem

[Schuyler]

Greetings,

I've got a zabbix install monitoring about 500 of a mix of Solaris and Linux hosts with the zabbix agent. Our entire zabbix install is on 2.2.3.

When I set an agent to use all active checks, especially when I modify the Network Interface Discovery to use Zabbix agent (active), it tends to miss the aggregate or bonded interfaces (aggxx or bondxx) on both platforms. Simply changing the type to Zabbix agent picks up all the interfaces.

If I change a working host (not using active) to active checks, it marks the bondxx interfaces as "not supported" and eventually deletes them (I think after the 30 day defined interval passes).

To test, create a bond interface on Linux (such as https://access.redhat.com/site/docum...aces-chan.html), then clone the Template OS Linux and edit all of the discovery rules (or at least just the interface ones) to use Zabbix agent (active). It will pick up the ethxx interfaces but not the bondxx interfaces.

I've predominantly tested this on RHEL6.

I'm trying to use all or even mostly active agents to reduce the poller load on the zabbix server. Right now I have to have everything except the network interface as active.

Thanks!

[Schuyler]

So what I'm trying to find is:

1) Is this the expected result from using interface discovery prototypes on active agents?
2) If not, what needs to happen to get this fixed?
3) Is there a work-around that lets me use active agents?

For 3) above, I'm thinking I'd have to split the discovery into its own template and make that a non-active agent - but what a messy pain that sounds like.