SDM-MIB: View SNMP OID List / Download MIB

The MIB module for the SDM (SmartStream Device Manager).

This trap is issued periodically as defined by the heartbeat interval to indicate that the SDM is alive and is capable of sending traps northbound.

This trap is issued when the SDM application is started.

This trap is issued when the SDM application is shutdown orderly. This trap may not be sent when the SDM prematurely aborts or is not properly shutdown.

This trap is issued when the SDM resynchronizes to a particular trap destination. Additional information is provided in the following variable-bindings: trapAdditionalInfoInteger1 - Type of resynchronization where 1=Resynch All, 2=Resynch Time, and 3=Resynch=Active trapAdditionalInfoInteger2 - Time (only applicable for Type=2)

This trap is issued when the resynchronization to a particular trap destination has completed. The following Additional Information variable-bindings are used to describe the resynchronization completion status as follows: trapAdditionalInfoInteger1 - Status of resynchronization where 0=No Error 1=User Abort 2=SDM Shutdown 3=Database Error

This is now obsolete. This trap is issued when a managed object such as a device or group is added to the system. A managed object can be added to the system in various ways (e.g. manually adding a device or discovering a device), and the sdmProbableCauseId and sdmProbableCauseText varbinds are used to provide additional information. When the managed object corresponds to a device, the varbinds sdmObjectIPAddress, trapNetworkElemModelNumber, trapNetworkElemSerialNum, trapNetworkElemOperState, trapNetworkElemAdminState and trapNetworkElemAvailStatus reflect the state of the device when the device was added to the system. For other managed objects, these varbinds are NULL. For all managed objects, the trapNetworkElemAlarmStatus varbind reflects the aggregate alarm status of the managed object and the sdmObjectDescription varbind contains a user-defined description associated with the managed object.

This is now obsolete. This trap is issued when a managed object such as a device or group is deleted from the system. The sdmProbableCauseId and sdmProbableCauseText varbinds are used to provide additional information on the deletion. When the managed object corresponds to a device, the varbinds sdmObjectIPAddress, trapNetworkElemModelNumber, trapNetworkElemSerialNum, trapNetworkElemOperState, trapNetworkElemAdminState and trapNetworkElemAvailStatus reflect the state of the device when the device was deleted from the system. For other managed objects, these varbinds are NULL. For all managed objects, the trapNetworkElemAlarmStatus varbind reflects the aggregate alarm status of the managed object and the sdmObjectDescription varbind contains a user-defined description associated with the managed object.

This trap is issued in response to an event generated on SDM. The sdmProbableCause and sdmProbableCauseText varbinds identify the event while the sdmObjectIPaddress and sdmObjectName varbinds identify the managed object. The trapPerceivedSeverity varbind identifies the current severity.

This trap is issued to indicate that the SDM detected a change to the state of an active alarm for a managed object. In other words, an active alarm was cleared or the perceived severity of the alarm changed. The sdmProbableCause and sdmProbableCauseText varbinds identify the alarm while the sdmObjectIPaddress and sdmObjectName varbinds identify the managed object. The trapPerceivedSeverity varbind identifies the current severity.

This trap describes a critical 'Other' fault. This trap is issued when the highest severity of all 'Other' faults for the given managed object is 'Critical'. An 'Other' fault is a miscellaneous category used to describes any fault that does not belong to one of the other categories.

This trap describes a Major 'Other' fault. This trap is issued when the highest severity of all 'Other' faults for the given managed object is 'Major'. An 'Other' fault is a miscellaneous category used to describes any fault that does not belong to one of the other categories.

This trap describes a minor 'Other' fault. This trap is issued when the highest severity of all 'Other' faults for the given managed object is 'Minor'. An 'Other' fault is a miscellaneous category used to describes any fault that does not belong to one of the other categories.

This trap describes a warning 'Other' fault. This trap is issued when the highest severity of all 'Other' faults for the given managed object is 'Warning'. An 'Other' fault is a miscellaneous category used to describes any fault that does not belong to one of the other categories.

This trap describes a cleared 'Other' fault. This trap is issued when either all active 'Other' faults for the given managed object are 'Clear' or no 'Other' faults exist. An 'Other' fault is a miscellaneous category used to describes any fault that does not belong to one of the other categories.

This trap describes an informational 'Other' fault. This trap is issued when the highest severity of all 'Other' faults for the given managed object is 'Informational'. An 'Other' fault is a miscellaneous category used to describes any fault that does not belong to one of the other categories.

This trap describes a critical 'Communications' fault. This trap is issued when the highest severity of all 'Communications' faults for the given managed object is 'Critical'. A 'Communications' fault usually describes a problem with procedures or processes used to exchange information between two or more components within the system.

This trap describes a major 'Communications' fault. This trap is issued when the highest severity of all 'Communications' faults for the given managed object is 'Major'. A 'Communications' fault usually describes a problem with procedures or processes used to exchange information between two or more components within the system.

This trap describes a minor 'Communications' fault. This trap is issued when the highest severity of all 'Communications' faults for the given managed object is 'Minor'. A 'Communications' fault usually describes a problem with procedures or processes used to exchange information between two or more components within the system.

This trap describes a warning 'Communications' fault. This trap is issued when the highest severity of all 'Communications' faults for the given managed object is 'Warning'. A 'Communications' fault usually describes a problem with procedures or processes used to exchange information between two or more components within the system.

This trap describes a cleared 'Communications' fault. This trap is issued when either all active 'Communications' faults for the given managed object are 'Clear' or no 'Communications' faults exist. A 'Communications' fault usually describes a problem with procedures or processes used to exchange information between two or more components within the system.

This trap describes an informational 'Communications' fault. This trap is issued when the highest severity of all 'Communications' faults for the given managed object is 'Informational'. A 'Communications' fault usually describes a problem with procedures or processes used to exchange information between two or more components within the system.

This trap describes a critical 'Quality of Service' fault. This trap is issued when the highest severity of all 'Quality of Service' faults for the given managed object is 'Critical'. A 'Quality of Service' fault usually describes degradation in the quality of service.

This trap describes a major 'Quality of Service' fault. This trap is issued when the highest severity of all 'Quality of Service' faults for the given managed object is 'Major'. A 'Quality of Service' fault usually describes degradation in the quality of service.

This trap describes a minor 'Quality of Service' fault. This trap is issued when the highest severity of all 'Quality of Service' faults for the given managed object is 'Minor'. A 'Quality of Service' fault usually describes degradation in the quality of service.

This trap describes a warning 'Quality of Service' fault. This trap is issued when the highest severity of all 'Quality of Service' faults for the given managed object is 'Warning'. A 'Quality of Service' fault usually describes degradation in the quality of service.

This trap describes a cleared 'Quality of Service' fault. This trap is issued when either all active 'Quality of Service' faults for the given managed object are 'Clear' or no 'Quality of Service' faults exist. A 'Quality of Service' fault usually describes degradation in the quality of service.

This trap describes an informational 'Quality of Service' fault. This trap is issued when the highest severity of all 'Quality of Service' faults for the given managed object is 'Informational'. A 'Quality of Service' fault usually describes degradation in the quality of service.

This trap describes a critical 'Processing Error' fault. This trap is issued when the highest severity of all 'Processing Error' faults for the given managed object is 'Critical'. A 'Processing Error' fault is used to describe a software or processing failure.

This trap describes a Major 'Processing Error' fault. This trap is issued when the highest severity of all 'Processing Error' faults for the given managed object is 'Major'. A 'Processing Error' fault is used to describe a software or processing failure.

This trap describes a minor 'Processing Error' fault. This trap is issued when the highest severity of all 'Processing Error' faults for the given managed object is 'Minor'. A 'Processing Error' fault is used to describe a software or processing failure.

This trap describes a warning 'Processing Error' fault. This trap is issued when the highest severity of all 'Processing Error' faults for the given managed object is 'Warning'. A 'Processing Error' fault is used to describe a software or processing failure.

This trap describes a cleared 'Processing Error' fault. This trap is issued when either all active 'Processing Error' faults for the given managed object are 'Clear' or no 'Processing Error' faults exist. A 'Processing Error' fault is used to describe a software or processing failure.

This trap describes an informational 'Processing Error' fault. This trap is issued when the highest severity of all 'Processing Error' faults for the given managed object is 'Informational'. A 'Processing Error' fault is used to describe a software or processing failure.

This trap describes a critical 'Equipment' fault. This trap is issued when the highest severity of all 'Equipment' faults for the given managed object is 'Critical'. An 'Equipment' fault is used to describe a hardware equipment failure.

This trap describes a Major 'Equipment' fault. This trap is issued when the highest severity of all 'Equipment' faults for the given managed object is 'Major'. An 'Equipment' fault is used to describe a hardware equipment failure.

This trap describes a minor 'Equipment' fault. This trap is issued when the highest severity of all 'Equipment' faults for the given managed object is 'Minor'. An 'Equipment' fault is used to describe a hardware equipment failure.

This trap describes a warning 'Equipment' fault. This trap is issued when the highest severity of all 'Equipment' faults for the given managed object is 'Warning'. An 'Equipment' fault is used to describe a hardware equipment failure.

This trap describes a cleared 'Equipment' fault. This trap is issued when either all active 'Equipment' faults for the given managed object are 'Clear' or no 'Equipment' faults exist. An 'Equipment' fault is used to describe a hardware equipment failure.

This trap describes an informational 'Equipment' fault. This trap is issued when the highest severity of all 'Equipment' faults for the given managed object is 'Informational'. An 'Equipment' fault is used to describe a hardware equipment failure.

This trap describes a critical 'Environmental' fault. This trap is issued when the highest severity of all 'Environmental' faults for the given managed object is 'Critical'. An 'Environmental' fault is used to describe a problem or condition relating to the enclosure in which the equipment resides.

This trap describes a Major 'Environmental' fault. This trap is issued when the highest severity of all 'Environmental' faults for the given managed object is 'Major'. An 'Environmental' fault is used to describe a problem or condition relating to the enclosure in which the equipment resides.

This trap describes a minor 'Environmental' fault. This trap is issued when the highest severity of all 'Environmental' faults for the given managed object is 'Minor'. An 'Environmental' fault is used to describe a problem or condition relating to the enclosure in which the equipment resides.

This trap describes a warning 'Environmental' fault. This trap is issued when the highest severity of all 'Environmental' faults for the given managed object is 'Warning'. An 'Environmental' fault is used to describe a problem or condition relating to the enclosure in which the equipment resides.

This trap describes a cleared 'Environmental' fault. This trap is issued when either all active 'Environmental' faults for the given managed object are 'Clear' or no 'Environmental' faults exist. An 'Environmental' fault is used to describe a problem or condition relating to the enclosure in which the equipment resides.

This trap describes an informational 'Environmental' fault. This trap is issued when the highest severity of all 'Environmental' faults for the given managed object is 'Informational'. An 'Environmental' fault is used to describe a problem or condition relating to the enclosure in which the equipment resides.

This trap describes a critical 'Integrity' fault. This trap is issued when the highest severity of all 'Integrity' faults for the given managed object is 'Critical'. An 'Integrity' fault is used to indicate that information may have been illegally modified, inserted or deleted.

This trap describes a Major 'Integrity' fault. This trap is issued when the highest severity of all 'Integrity' faults for the given managed object is 'Major'. An 'Integrity' fault is used to indicate that information may have been illegally modified, inserted or deleted.

This trap describes a minor 'Integrity' fault. This trap is issued when the highest severity of all 'Integrity' faults for the given managed object is 'Minor'. An 'Integrity' fault is used to indicate that information may have been illegally modified, inserted or deleted.

This trap describes a warning 'Integrity' fault. This trap is issued when the highest severity of all 'Integrity' faults for the given managed object is 'Warning'. An 'Integrity' fault is used to indicate that information may have been illegally modified, inserted or deleted.

This trap describes a cleared 'Integrity' fault. This trap is issued when either all active 'Integrity' faults for the given managed object are 'Clear' or no 'Integrity' faults exist. An 'Integrity' fault is used to indicate that information may have been illegally modified, inserted or deleted.

This trap describes an informational 'Integrity' fault. This trap is issued when the highest severity of all 'Integrity' faults for the given managed object is 'Informational'. An 'Integrity' fault is used to indicate that information may have been illegally modified, inserted or deleted.

This trap describes a critical 'Operational' fault. This trap is issued when the highest severity of all 'Operational' faults for the given managed object is 'Critical'. An 'Operational' fault usually describes a problem or condition regarding the provisioning or configuration of a network element service.

This trap describes a Major 'Operational' fault. This trap is issued when the highest severity of all 'Operational' faults for the given managed object is 'Major'. An 'Operational' fault usually describes a problem or condition regarding the provisioning or configuration of a network element service.

This trap describes a minor 'Operational' fault. This trap is issued when the highest severity of all 'Operational' faults for the given managed object is 'Minor'. An 'Operational' fault usually describes a problem or condition regarding the provisioning or configuration of a network element service.

This trap describes a warning 'Operational' fault. This trap is issued when the highest severity of all 'Operational' faults for the given managed object is 'Warning'. An 'Operational' fault usually describes a problem or condition regarding the provisioning or configuration of a network element service.

This trap describes a cleared 'Operational' fault. This trap is issued when either all active 'Operational' faults for the given managed object are 'Clear' or no 'Operational' faults exist. An 'Operational' fault usually describes a problem or condition regarding the provisioning or configuration of a network element service.

This trap describes an informational 'Operational' fault. This trap is issued when the highest severity of all 'Operational' faults for the given managed object is 'Informational'. An 'Operational' fault usually describes a problem or condition regarding the provisioning or configuration of a network element service.

This trap describes a critical 'Physical Violation' fault. This trap is issued when the highest severity of all 'Physical Violation' faults for the given managed object is 'Critical'. A 'Physical Violation' fault is used to indicate that a physical resource has been violated.

This trap describes a Major 'Physical Violation' fault. This trap is issued when the highest severity of all 'Physical Violation' faults for the given managed object is 'Major'. A 'Physical Violation' fault is used to indicate that a physical resource has been violated.

This trap describes a minor 'Physical Violation' fault. This trap is issued when the highest severity of all 'Physical Violation' faults for the given managed object is 'Minor'. A 'Physical Violation' fault is used to indicate that a physical resource has been violated.

This trap describes a warning 'Physical Violation' fault. This trap is issued when the highest severity of all 'Physical Violation' faults for the given managed object is 'Warning'. A 'Physical Violation' fault is used to indicate that a physical resource has been violated.

This trap describes a cleared 'Physical Violation' fault. This trap is issued when either all active 'Physical Violation' faults for the given managed object are 'Clear' or no 'Physical Violation' faults exist. A 'Physical Violation' fault is used to indicate that a physical resource has been violated.

This trap describes an informational 'Physical Violation' fault. This trap is issued when the highest severity of all 'Physical Violation' faults for the given managed object is 'Informational'. A 'Physical Violation' fault is used to indicate that a physical resource has been violated.

This trap describes a critical 'Security' fault. This trap is issued when the highest severity of all 'Security' faults for the given managed object is 'Critical'. A 'Security' fault usually describes a problem securing a service or program.

This trap describes a major 'Security' fault. This trap is issued when the highest severity of all 'Security' faults for the given managed object is 'Major'. A 'Security' fault usually describes a problem securing a service or program.

This trap describes a minor 'Security' fault. This trap is issued when the highest severity of all 'Security' faults for the given managed object is 'Minor'. A 'Security' fault usually describes a problem securing a service or program.

This trap describes a warning 'Security' fault. This trap is issued when the highest severity of all 'Security' faults for the given managed object is 'Warning'. A 'Security' fault usually describes a problem securing a service or program.

This trap describes a cleared 'Security' fault. This trap is issued when either all active 'Security' faults for the given managed object are 'Clear' or no 'Security' faults exist. A 'Security' fault usually describes a problem securing a service or program.

This trap describes an informational 'Security' fault. This trap is issued when the highest severity of all 'Security' faults for the given managed object is 'Informational'. A 'Security' fault usually describes a problem securing a service or program.

This trap describes a critical 'Time Domain' fault. This trap is issued when the highest severity of all 'Time Domain' faults for the given managed object is 'Critical'. A 'Time Domain' fault usually describes a problem synchronizing to the system time.

This trap describes a major 'Time Domain' fault. This trap is issued when the highest severity of all 'Time Domain' faults for the given managed object is 'Major'. A 'Time Domain' fault usually describes a problem synchronizing to the system time.

This trap describes a minor 'Time Domain' fault. This trap is issued when the highest severity of all 'Time Domain' faults for the given managed object is 'Minor'. A 'Time Domain' fault usually describes a problem synchronizing to the system time.

This trap describes a warning 'Time Domain' fault. This trap is issued when the highest severity of all 'Time Domain' faults for the given managed object is 'Warning'. A 'Time Domain' fault usually describes a problem synchronizing to the system time.

This trap describes a cleared 'Time Domain' fault. This trap is issued when either all active 'Time Domain' faults for the given managed object are 'Clear' or no 'Time Domain' faults exist. A 'Time Domain' fault usually describes a problem synchronizing to the system time.

This trap describes an information 'Time Domain' fault. This trap is issued when the highest severity of all 'Time Domain' faults for the given managed object is 'Informational'. A 'Time Domain' fault usually describes a problem synchronizing to the system time.

This object identifies the probable cause associated with the current trap. For SDM collated alarms, the probable cause identifies the specific alarm failure responsible for triggering this notification. When multiple alarms of the same category are active at the same time for a given managed object, the probable cause corresponds to the active alarm with the highest severity for the reported category. Moreover, when the highest severity alarm for a given category clears, the probable cause may change if another active alarm of the same category is active for the given managed object. For SDM northbound events, this object is not always applicable. Each northbound event description indicates whether this object is applicable. For those northbound events where this object is not applicable, this object will be NULL.

This object identifies the description for the above probable cause and contains the alarm description of the alarm responsible for triggering this notification. For those SDM northbound event where probable cause is not applicable, this object will be NULL.

This object contains a user-defined description for the managed object associated with the current trap.

This object contains the IP address (where applicable) for the managed object associated with the current trap. For those managed objects that do not have an IP address (e.g. user-defined groups), this object will be NULL.

The object describes the name used by the SDM to uniquely identify the managed object associated with the current trap.

The object identifies the type of managed object associated with the current trap.

The object contains an URL that provides additional information about the current trap.

The object identifies the category, i.e. ITU Event Type, associated with the current trap. Enumeration: 'catEnvironmental': 6, 'catEquipment': 5, 'catOperational': 8, 'catNA': 0, 'catQualityOfService': 3, 'catIntegrity': 7, 'catPhysical': 9, 'catTimeDomain': 11, 'catOther': 1, 'catCommunications': 2, 'catProcessingError': 4, 'catSecurity': 10.

This object identifies the display name (title) of the event/alarm responsible for triggering this notification.