MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Unsigned32
                                                    FROM SNMPv2-SMI
                                                      -- RFC 2578
RowStatus, StorageType, TimeStamp, TruthValue, VariablePointer
                                                    FROM SNMPv2-TC
                                                      -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP
                                                    FROM SNMPv2-CONF
                                                      -- RFC 2580
SnmpAdminString, SnmpSecurityModel, SnmpSecurityLevel
                                                    FROM SNMP-FRAMEWORK-MIB
                                                      -- RFC 3411
ITSBerString, ITSCounter32, ITSPositive8, ITSRelativeRowPointer, ITSUnsigned8, 
ITSCounter16
                                                    FROM ISO26048-1-FieldDevice
fdGlobalMIB, fdAdminGlobal, fdGlobalConformance
                                                    FROM ISO26048-1-Global
fdOwnerEntry, fdOwnerIndex
                                                    FROM ISO26048-1-Owner
  

This MIB defines a mechanism by which a manager can configure actions to be performed based on user-defined comparisons using data within the field device. Copyright (C) International Organization for Standardization (ISO). This MIB module is part of ISO 26048-1; see ISO 26048-1 for full legal notices.

A node defining management information related to the administration of the conditional trigger table.

The number of times the evaluation of any enabled conditional trigger has failed since the last reboot. For example, a trigger evaluation might fail if a variable in an expression cannot be obtained.

The number of times any enabled conditional trigger has fired (i.e., evaluated to 'true') since the last reboot.

The number of times an attempt by a conditional trigger to call an action group failed (e.g., the action group was not defined).

A table containing management information about the conditional triggers associated with each owner. It is recommended that administrators are granted read-write access to the entire table while owners are only granted read-access to their specific row(s).

A row in the fdOwnerCondTriggerTable.

The maximum number of rows that this owner is allowed to manage within the fdCondTriggerTable at any point in time.

The number of times an 'active' conditional trigger for this owner failed to evaluate its defined condition (e.g., due to data not being available, processor overload, etc) since the last discontinuity, as defined by the fdOwnerTimeStamp.

The number of times any conditional trigger associated with this owner has been fired since the last discontinuity, as defined by the fdOwnerTimeStamp.

The number of times a conditional trigger fired for this owner but the call to the action group failed (e.g., due to the referenced row not being active) since the last discontinuity, as defined by the fdOwnerTimeStamp.

The options supported by the conditional triggering system within the field device: Valid bits are: Value | Description current | The field device supports 'current' sample types delta | The field device supports 'delta' sample types onChange | The field device supports 'onChange' triggers (mode) greaterThan | The field device supports 'greaterThan' triggers lessThan | The field device supports 'lessThan' triggers hysteresis | The field device supports 'hysteresis' triggers periodic | The field device supports 'periodic' triggers equal | The field device supports 'equal' triggers notEqual | The field device supports 'notEqual' triggers creation | The field device supports 'creation' triggers deletion | The field device supports 'deletion' triggers bitwiseAnd | The field device supports 'bitwiseAnd' triggers

The minimum value of fdCondTriggerObjectFrequency that can be set under any condition.

An explanation (or a reference to an explanation, such as with a URL that points to a user guide) for any special rules for setting frequency limits. For example, if a handful of objects support a zero frequency but others have higher limits, the fdCondTriggersFrequencyLimit would be set to zero (0), but the notes would provide complete details about what limits apply to all objects.

A table containing the configuration and status information for each conditional trigger.

A row in the fdCondTriggerTable.

A locally-unique, administratively assigned index for the trigger within the scope of fdOwnerIndex.

A description of the trigger's function and use.

The type of trigger test to perform. The following text provides the special rules for each value: The term 'monitored value' referenced in the text below is 1. The value referenced by the fdCondTriggerObject, if the fdCondTriggerSampleType is 'current' or 2. The current value referenced by the fdCondTriggerObject minus the previously read value of this same object, if the fdCondTriggerSampleType is 'delta' other: Fires: Not defined by this standard; use of all objects is undefined. Startup: Not defined by this standard. Resets: Not defined by this standard. onChange: Fires: fdCondTriggerAction when the monitored value changes (includes creation and deletion) fdCondTriggerSampleType: Must be 'current' Startup: Does not fire on initialization Resets: Upon each firing greaterThan: Fires: fdCondTriggerAction when the monitored value is greater than fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration fdCondTriggerObject: Points to an integer-based object instance Startup: Based on fdCondTriggerStartup Resets: When value falls below fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration lessThan: Fires: fdCondTriggerAction when the monitored value is less than fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration fdCondTriggerObject: Points to an integer-based object instance Startup: Based on fdCondTriggerStartup Resets: When value rises above fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration hysteresis: Fires: - fdCondTriggerAction when when the monitored value is greater than the value of fdCondTriggerValue - fdCondTriggerAction2 when the monitored value is less than the value of the fdCondTriggerValue2 fdCondTriggerObject: Points to an integer-based object instance Startup: Based on fdCondTriggerStartup and fdCondTriggerStartup2 Resets: The fdCondTriggerAction when the fdCondTriggerAction2 fires The fdCondTriggerAction2 when the fdCondTriggerAction fires periodic: Fires: fdCondTriggerAction every fdCondTriggerValue seconds Startup: Based on fdCondTriggerStartup Resets: Resets upon firing equal: Fires: fdCondTriggerAction when the monitored value is equal to fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration fdCondTriggerObject: Points to an integer-based object instance Startup: Based on fdCondTriggerStartup Resets: When value is no longer equal to fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration notEqual: Fires: fdCondTriggerAction when the monitored value is not equal to fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration fdCondTriggerObject: Points to an integer-based object instance Startup: Based on fdCondTriggerStartup Resets: When value is equal to fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration creation: Fires: fdCondTriggerAction when the object pointed to by fdCondTriggerObject is created Startup: Based on fdCondTriggerStartup; must be false if wildcarded Resets: Resets upon firing deletion: Fires: fdCondTriggerAction when the object pointed to by fdCondTriggerObject is deleted Startup: Based on fdCondTriggerStartup; must be false if wildcarded Resets: Resets upon firing bitwiseAnd: Fires: fdCondTriggerAction when any bits set in the object pointed to by fdCondTriggerObject are also set in fdCondTriggerValue for a period longer than fdCondTriggerTruthDuration. In other words, a bitwise AND is performed on the values referenced by fdCondTriggerObject and fdCondTriggerValue and if any bits are set in the resulting value, the trigger is fired. Startup: Based on fdCondTriggerStartup Resets: When no bits match for a period longer than fdCondTriggerTruthDuration octetBitwiseAnd: Fires: fdCondTriggerAction when any bits set in the object pointed to by fdCondTriggerObject are also set in fdCondTriggerValueOctet for a period longer than fdCondTriggerTruthDuration. In other words, a bitwise AND is performed on the values referenced by fdCondTriggerObject and fdCondTriggerValue and if any bits are set in the resulting value for the defined duration, the trigger is fired. The value referenced by fdCondTriggerObject must be derived from an OCTET STRING or BITS; otherwise the evaluation shall fail. Startup: Based on fdCondTriggerStartup Resets: When no bits match for a period longer than fdCondTriggerTruthDuration

An indication of the value to monitor. Allowed values are: Value | Description other | Not defined in this standard current | The monitored value shall be the current value of the object | instance referenced by fdCondTriggerObject delta | The monitored value shall be the value calculated by taking | the current value of the object instance referenced by | fdCondTriggerObject and subtracting the previously reported | value of the same object. NOTE: Delta operations require at least two readings, separated by fdCondTriggerObjectFrequency, for a comparison to be made.

The value to use for the test specified by fdCondTriggerMode. This object is ignored when the mode is 'onChange', 'periodic', 'creation', or 'deletion'. For the 'hysteresis' mode, this value shall be an integer representing the rising threshold. The value of this object shall include the Type, Length, and Value portions of the BER encoding; if the Type field does not correspond to the type of object referenced by fdCondTriggerObject and this value is required for the selected Mode, the RowStatus shall report a status of 'notReady' and CfgMessage object shall indicate the reason. NOTE: while the logic of hysteresis is always integer-based, the Type field should indicate the SNMP type (e.g., Integer32 versus Unsigned32).

When the fdCondTriggerMode value is 'hysteresis' mode, this value shall represent the falling threshold. This value shall be ignored for all other values of fdCondTriggerMode. The value of this object shall include the Type, Length, and Value portions of the BER encoding; if the Type field does not correspond to the type of object referenced by fdCondTriggerObject and this value is required for the selected Mode, the RowStatus shall report a status of 'notReady' and CfgMessage object shall indicate the reason. NOTE: while the logic of hysteresis is always integer-based, the Type field should indicate the SNMP type (e.g., Integer32 versus Unsigned32).

The object identifier of the MIB object instance to sample to see if the trigger should fire. If the fdCondTriggerMode is 'onChange', 'creation', or 'deletion', and fdCondTriggerWildcard is set to 'true', this value shall represent the common root portion of the object identifier for all object instances to be monitored. Bad object identifiers or a mismatch between truncating the identifier and the value of fdCondTriggerWildcard result in an operation as one would expect when providing the wrong identifier to a Get or GetNext operation. The Get will fail or get the wrong object. The GetNext will indeed get whatever is next, proceeding until it runs past the initial part of the identifier and perhaps many unintended objects for confusing results. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.

Control for whether fdCondTriggerObject is to be treated as fully- specified or wildcarded, with 'true' indicating wildcard. This value is ignored (i.e., always treated as 'false') if the value of fdCondTriggerMode is not 'onChange', 'creation', or 'deletion'.

The unique identifier associated with the snmpTargetAddrEntry from which to obtain the value to be checked. A length of 0 indicates the local system. In this case, access to the object(s) indicated by fdCondTriggerObject is under the security credentials of the requester that set fdCondTriggerRowStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks (RFC 3411). Otherwise, for values other than a zero-length string, access rights are checked according to the security parameters for the indicated target as defined in the snmpTargetParamsTable.

The management context from which to obtain fdCondTriggerObject. For example, if a device is a proxy agent, it might support local data in addition to data representing one or more remote devices. Each set of data is contained within a named context per the rules defined in the Architecture for Describing SNMP Management Frameworks (RFC 3411).

The number of seconds to wait between trigger samples. To encourage consistency in sampling, the interval is measured from the beginning of one check to the beginning of the next and the timer is restarted immediately when it expires, not when the check completes. If the next sample begins before the previous one completed the system shall record an evalError. A frequency of 0 indicates instantaneous recognition of the condition. This is not possible in many cases, but may be supported in cases where it makes sense and the system is able to do so. This feature allows the MIB to be used in implementations where such interrupt-driven behavior is possible and is not likely to be supported for all MIB objects even then since such sampling generally has to be tightly integrated into low-level code. Systems that can support a value of zero SHOULD document those cases where it can be used. In cases where it can not, setting this object to 0 shall result in an 'inconsistentValue' error.

If the sample type is 'current' and the mode is 'greaterThan', 'lessThan', 'equal', 'notEqual', 'integerBitwiseAnd', or 'octetBitwiseAnd', the logic within this paragraph applies. If the frequency is zero (0), this value indicates the duration, in tenths of seconds, that the condition must be true prior to the trigger firing. If the frequency is greater than zero (0), this value represents the number of sequential times the the condition must evaluate to true before the trigger fires. In the latter case, the value zero (0) shall operate as if it were a one (1). For example, if the mode is 'equal' and the frequency is 60, the field device will check the object instance every minute. If the fdCondTriggerTruthDuration is set to zero or one, the trigger will fire the first time the evaluation returns 'true'. If the value of fdCondTriggerTruthDuration is two, the trigger will only fire when the evaluation returns 'true' two times in a row. In either case, the trigger will not reset until the evaluation returns false. If the sample type is 'delta' or if the mode is 'onChange', 'hysteresis', 'periodic', 'creation', or 'deletion', this value shall be ignored and the trigger will fire upon the monitored condition initially evaluating to true.

The initial state of the trigger upon fdCondTriggerEnabled being enabled. In the case of the 'greaterThan', 'lessThan', 'equal', and 'notEqual' modes, if this value is true, the trigger shall initiate in a ready-to- fire state upon fdCondTriggerEnabled changing to 'enabled'. As a result, if the condition specified by this trigger is true when placed in the 'enabled' state, the trigger will immediately fire. It will then have to reset before firing again. If this value is false, the trigger shall initiate in a fired state upon fdCondTriggerEnabled changing to 'enabled'. As a result, if the condition specified by this trigger is true when placed in the 'enabled' state, the trigger will not fire immediately; instead, the trigger will first have to reset before firing. In the case of the 'hysteresis' mode, this object indicates the initial state of the rising trigger; the initial state of the falling trigger shall be defined by fdCOndTriggerStartupReady2. In the case of the 'periodic' mode, this value shall indicate whether the trigger will fire instantaneously (true) upon enablement and every fdCondTriggerFrequency seconds thereafter, or if it will only start firing after the first fdCondTriggerFrequency seconds after being enabled. In the case of the 'creation' and 'deletion' modes, this value shall be 'false' if fdCondTriggerWildcard is 'true'; otherwise, the value of fdCondTriggerRowStatus shall automatically transition to 'notReady'. The first reading of existing object instances shall be used to identify the baseline from which the trigger will detect creation or deletion events; the trigger will then reset after this initialization. In the case of 'creation' or 'deletion' modes with fdCondTriggerWildcard set to 'false', this value shall operate as described above. In the case of the 'onChange' mode, this value shall be ignored. The initial check in the onChange mode is always used to set the baseline against which changes are detected.

If the value of fdCondTriggerMode is 'hysteresis', this object indicates the initial state of the falling trigger. The initial state of the rising trigger shall be defined by fdCondTriggerStartup. This object is ignored for all other values of fdCondTriggerMode.

The row of the fdActionTable to be called when this trigger fires. In the case of the hysteresis mode, this only represents the action to be called for the rising trigger.

If the mode is hysteresis, this object specifies the row of the fdActionTable to be called when the falling trigger fires. This value is ignored for all other modes.

Implementation-specific message that may be used by the field device to report errors and explain why the status is notInService or notReady.

The number of times the evaluation of this conditional trigger has failed since its last discontinuity. For example, a trigger evaluation might fail if a variable in an expression cannot be obtained. The last discontinuity is indicated by the fdCondTriggerTimeStamp.

The number of times this conditional trigger has fired (i.e., evaluated to 'true') since its last discontinuity. The last discontinuity is indicated by the fdCondTriggerTimeStamp.

The number of times this conditional trigger fired but the call to the action group failed (e.g., due to the referenced row not being active) since the last discontinuity. The last discontinuity is indicated by the fdCondTriggerTimeStamp.

The value of sysUpTime at the last discontinuity of any of the counters associated with this row of the fdCondTriggerTable. Discontinuities occur when the row is created.

The security model used to activate this row of the fdCondTriggerTable, retrieve the value of fdCondTriggerObject for evaluation and call fdCondTriggerActions and fdCondTriggerActions2.

The security level used to activate this row of the fdCondTriggerTable, retrieve the value of fdCondTriggerObject for evaluation and call fdCondTriggerActions and fdCondTriggerActions2.

The security name used to activate this row of the fdCondTriggerTable, retrieve the value of fdCondTriggerObject for evaluation and call fdCondTriggerActions and fdCondTriggerActions2.

The storage type for this conceptual row. Conceptual rows having the value 'permanent' shall allow the row status to be set to 'notInService'.

The status of this conceptual row. The row status shall indicate 'notReady' whenever the security model, level, and name do not provide read access to the object referenced by fdCondTriggerObject or do not provide write access to the fdActionGroupDescription object referenced by either fdCondTriggerActions or fdCondTriggerActions2. At a minimum, these access rights shall be verified whenever (1) any configuration parameter in this conceptual row is changed and (2) any changes are made to the vacmSecurityToGroupTable, vacmAccessTable, or vacmViewTreeFamilyTable. Any attempt to modify any read-create object within this conceptual row while the value of this object is active(1) shall result in an inconsistentValue error.

A node containing conformance statements related to the fdCondTriggerMIB, as defined in ISO/TS 20684-3.

A node for compliance statements for the fdCondTriggerMIB.

A node for group definitions related to fdCondTriggerMIB.

All implementations shall support the fdCondTriggerWildcard object but implementations may constrain the value to be 'false'. If a device constrains the value to 'false', it may also treat the object as read-only.

Management information for the administration of conditional triggers.

Management information that identifies the capabilities of conditional triggers.