We're integrating our Aruba platform into our enterprise alerting pipeline that will bypass AirWave. This involves adding a few new SNMP trap receivers, but with the default enabled traps list so large, I'm worried we might overwhelm the new servers.
There are quite a few that I think are unnecessary, but it's unclear to me if AirWave is making use of those traps in the backend. A good example would be `wlsxUserEntryCreated`. Can I safely disable that trap without impacting AirWave data integrity?
Alternatively, is it possible to enable/disable trap receivers on a per-OID basis?