Important

   

Starting version 8.9.03, BMC Network Automation is renamed to TrueSight Network Automation. This space contains information about BMC Network Automation 8.9.02 and previous versions. For TrueSight Network Automation 8.9.03 and later releases, see the TrueSight Network Automation documentation.

Understanding data types

The following data types can be found in the variables for each of the trap types:

  • enaTypeChangeID: Contains the Change ID from the job that generated the trap.
  • enaTypeConditionTrace: The evaluation trace of Conditions which triggered the policy. Conditions are user-defined. Multiple Conditions can be strung together to form an ultimate True or False logical result. Conditions must consist of exactly one triggering condition which is connected with 0 to many non-Triggering Conditions using logical operators (AND, OR, or NOT).

    Policies have a triggering condition and an optional set of additional non-triggering conditions formed into a boolean expression. The trace always shows the triggering condition as evaluated to true. The value of the enaTypeConditionTrace includes the Triggering Condition=True.
    This is followed by the boolean expression that shows the non-triggering conditions, followed by the true/false values of the non-triggering conditions that satisfied the policy.

    Note

    The enaTypeConditionTrace data type is populated When the trap is sent as a result of a policy. It is not populated when the trap is sent from a job.

    Examples

    • Single triggering condition:
      [Change Detected Now=True]
    • Triggering Condition connected by AND with three non-Triggering Conditions, all connected together by AND. Therefore, all non-triggering conditions must be True:
      [Discrepancy Detected Now=True; ((Change Detected Past 48) && (Change Detected Past 24) && (Change Detected Past 12)); Change Detected Past 48=True; Change Detected Past 24=True; Change Detected Past 12=True]
    • Triggering condition connected by AND with three non-triggering conditions connected together by OR. Therefore, just one of the non-triggering conditions must be True:
      [Discrepancy Detected Now=True; ((Change Detected Past 48) && (Change Detected Past 24) && (Change Detected Past 12)); Change Detected Past 48=True]
  • enaTypeAnnotation: The user-defined Annotation assigned to the Send Trap Action.
  • enaTypeTriggeringDevice: The value of the Name field of the triggering device.
    This is typically the name of the device that was involved in the condition that the policy was checking (that is, the device that was changed, the device that has a rule violation, the device that has a Running versus Startup discrepancy, and so on).
    For a trap action defined in a job, the user can select which device is included in this field.
  • enaTypeTriggeringEventDescription: The triggering condition is associated with a keyword. A keyword has a type value of Event, Discrepancy, or Change. If the keyword type is Event and the assigned Event has a system hard coded Event Description, the value of this Event Description appears in the enaTypeTriggeringEventDescription field of the trap.

    Note

    Do not confuse the Event Description with the User Defined Dynamic Field in the keyword called Description. They are not the same. The only way to view the actual Event Description is in the event log (Home > Events).

    For a trap action run by a Job, this field is empty.

  • enaTypeServerUrl: The URL to the BMC Network Automation application server that sent the trap. This value is useful when multiple servers are reporting to the same SNMP trap receiver.
  • enaTypeTriggeringDeviceExternalID: Unique ID of the triggering device as imported from an external system such as BMC Atrium CMDB.
Was this page helpful? Yes No Submitting... Thank you

Comments