Not sure if this is what you are looking for but this is in the 5.050 online help:
:: SNMP Traps ::
This configuration allows the system to send Admin notification events as SNMP traps to the configured trap host(s). Special SNMP monitoring software is needed to catch those traps.
The SNMP OIDs (object identifiers) used are in the private enterprise range (.1.3.6.1.4.1.9789). The OID for notification events is 1500, the level of the notification (DEBUG = 0, INFO = 1, WARN = 2, CRIT = 3) and the id of the respective notification (000 - 999) are appended. Only information from the subject of the notifications is transmitted.
Example: notification INFO-354: "Intrusion Protection Pattern Up2Date succeeded" will use the OID .1.3.6.1.4.1.9789.1500.1.354 and will have the following string value: "[][INFO][354]", where is the hostname of the system.
On a side note...why do you need this for AD/LDAP auth? I have a couple different ASL's going against Novell eDirectory and Windows AD and never needed that.
Not sure if this is what you are looking for but this is in the 5.050 online help:
:: SNMP Traps ::
This configuration allows the system to send Admin notification events as SNMP traps to the configured trap host(s). Special SNMP monitoring software is needed to catch those traps.
The SNMP OIDs (object identifiers) used are in the private enterprise range (.1.3.6.1.4.1.9789). The OID for notification events is 1500, the level of the notification (DEBUG = 0, INFO = 1, WARN = 2, CRIT = 3) and the id of the respective notification (000 - 999) are appended. Only information from the subject of the notifications is transmitted.
Example: notification INFO-354: "Intrusion Protection Pattern Up2Date succeeded" will use the OID .1.3.6.1.4.1.9789.1500.1.354 and will have the following string value: "[][INFO][354]", where is the hostname of the system.
On a side note...why do you need this for AD/LDAP auth? I have a couple different ASL's going against Novell eDirectory and Windows AD and never needed that.