Hierarchically Trap-Filtering possible?
Hello,
I've got a question: For exampe, If I have a trap-processors for the enterprise-oid ".1.3.6.1.4.1.9" (Cisco), can I then add a second trap-processor for the enterprise-oid ".1.3.6.1.4.1.9.9.41.1.2.3.1" (Firewall-UDP-Request-Discarded-Trap), which is a sub-part of the first oid?
In my case, I have two trap-processors, let it be "T1" and "T2:
T1 - The "Cisco Configuration Management" trap processor, predefined by OPManager:
Name: "Cisco Configuration Management"
Generic Type: "enterpriseSpecific(6)"
Specific Type: "1"
Enterprise OID: ".1.3.6.1.4.1.9"
Message: "[...]"
Severity: "Trouble"
Status: "Enable"
T2 - My own generated trap processor:
Name: "Test"
Generic Type: "enterpriseSpecific(6)"
Specific Type: "1"
Enterprise OID: ".1.3.6.1.4.1.9.9.41.1.2.3.1"
Message: "[...]"
Severity: "Trouble"
Status: "Enable"
So If I enable T1, T2 does not seem to work. If I deactivate T1, T2 works. The sorting by name in the list of trap-processoers doesnt have influence on this, so the name of the trap-processor doesn't seem to matter!
What I want to do is, that if T2 does not fit with the recieved trap, OPManager looks for other sub-oid an then, if it cant find a fitting oid, it takes the main enterprise oid, in my example of T1! That would be a hierarchical chain of trap-processors, seraching in it from buttom up!
Is this feature implemented in OPManager and if it is, how can I use it?
Kind regards,
Markus
I've got a question: For exampe, If I have a trap-processors for the enterprise-oid ".1.3.6.1.4.1.9" (Cisco), can I then add a second trap-processor for the enterprise-oid ".1.3.6.1.4.1.9.9.41.1.2.3.1" (Firewall-UDP-Request-Discarded-Trap), which is a sub-part of the first oid?
In my case, I have two trap-processors, let it be "T1" and "T2:
T1 - The "Cisco Configuration Management" trap processor, predefined by OPManager:
Name: "Cisco Configuration Management"
Generic Type: "enterpriseSpecific(6)"
Specific Type: "1"
Enterprise OID: ".1.3.6.1.4.1.9"
Message: "[...]"
Severity: "Trouble"
Status: "Enable"
T2 - My own generated trap processor:
Name: "Test"
Generic Type: "enterpriseSpecific(6)"
Specific Type: "1"
Enterprise OID: ".1.3.6.1.4.1.9.9.41.1.2.3.1"
Message: "[...]"
Severity: "Trouble"
Status: "Enable"
So If I enable T1, T2 does not seem to work. If I deactivate T1, T2 works. The sorting by name in the list of trap-processoers doesnt have influence on this, so the name of the trap-processor doesn't seem to matter!
What I want to do is, that if T2 does not fit with the recieved trap, OPManager looks for other sub-oid an then, if it cant find a fitting oid, it takes the main enterprise oid, in my example of T1! That would be a hierarchical chain of trap-processors, seraching in it from buttom up!
Is this feature implemented in OPManager and if it is, how can I use it?
Kind regards,
Markus