Designing and Managing Behavior Models
-
Using Trap Masks - How NerveCenter Decodes SNMP v2c/v3 Traps -
Because SNMP v2c/v3 traps use a different architecture that extends security and administration, the mechanics of how NerveCenter receives an SNMP v2c/v3 trap is different than how it receives an SNMP v1 trap.
When an SNMPv3 trap is received by the NerveCenter Server, it attempts to decode the trap. If the SNMP engine sending the trap is not registered with NerveCenter, then NerveCenter installs the engine.
If the user name that is listed in the trap's header does not match NCUser, NerveCenter outputs a `Configuration Mismatch' error in the V3 Operation Error Status field of the Node Definition window (SNMP page) and stops attempting to decode the trap.
Next, if the user name matches and the security level is other than NoAuthNoPriv, NerveCenter tries to decode the trap with an MD5 authority protocol and a DES privacy protocol. Should decoding fail, NerveCenter uses the SHA authority protocol. When this fails, NerveCenter outputs a `Configuration Mismatch' error and stops attempting to decode the trap.
Finally, if the authorization/privacy portion of the trap decode is successful, then NerveCenter checks for the v3 trap's context. If the context fails, NerveCenter outputs a `Configuration Mismatch' error and stops attempting to decode the trap.
V3 Operation Error Status Field of the SNMP Tab
| About Trap Masks | Listing Trap Masks |
| 29 July 2003 |