All MIBs › SDM-MIB
Organization: Motorola Broadband Home Solutions
Last Updated: 2010-04-21
Category: Cable and DOCSIS
Description: Manages Motorola Broadband DOCSIS cable modem provisioning, registration, and downstream statistics.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is SDM-MIB?
SDM-MIB supports Motorola's SmartStream Device Manager (SDM), a network element/event management component historically associated with Motorola broadband and cable infrastructure products. Rather than exposing raw hardware counters, its objects model management events about other devices in the network: a probable cause code and descriptive text, the affected object's name, type, IP address, and category, plus a reference URL for more detail. Its monitoring value is therefore primarily fault/status oriented, letting an operator see which devices SDM has flagged and why, effectively acting as an alarm/event correlation feed layered on top of whatever device-specific status MIBs generate the underlying counters. It depends conceptually on the identity/addressing conventions of the devices it describes but is not shown to import other management MIBs directly in this excerpt. It is typically deployed within a Motorola broadband network management system monitoring cable modems, headend, or other broadband access equipment for operational faults. Engineers can download the SDM-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in SDM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Motorola broadband/cable network element (e.g. cable modem or headend equipment) managed via SmartStream Device Manager
Monitoring Examples
An operator would poll sdmObjectName, sdmObjectType, and sdmObjectIPAddress to identify which managed device an alert refers to, then read sdmProbableCause and sdmProbableCauseText (with sdmProbableCauseName) to understand the nature of the problem, such as a loss-of-signal or provisioning failure. The sdmCategory object lets alerts be grouped by class of issue, and sdmUrl can point to a management console page with further remediation detail. A spike in probable-cause events tagged against the same sdmObjectIPAddress would indicate a persistently misbehaving device worth escalating.
What Can Be Monitored
- probable cause of reported faults
- affected device name/type/IP address
- event category
- reference URL for event detail
This MIB depends on
Related MIBs
Imported Objects
From BCS-IDENT-MIB
| giproducts | OBJECT-IDENTITY |
From BCS-TRAPS-MIB
| trapAdditionalInfoInteger1 | OBJECT-TYPE |
| trapAdditionalInfoInteger2 | OBJECT-TYPE |
| trapAdditionalInfoInteger3 | OBJECT-TYPE |
| trapChangedObjectId | OBJECT-TYPE |
| trapIdentifier | OBJECT-TYPE |
| trapNETrapLastTrapTimeStamp | OBJECT-TYPE |
| trapNetworkElemAdminState | OBJECT-TYPE |
| trapNetworkElemAlarmStatus | OBJECT-TYPE |
| trapNetworkElemAvailStatus | OBJECT-TYPE |
| trapNetworkElemModelNumber | OBJECT-TYPE |
| trapNetworkElemOperState | OBJECT-TYPE |
| trapNetworkElemSerialNum | OBJECT-TYPE |
| trapPerceivedSeverity | OBJECT-TYPE |
| trapSequenceId | OBJECT-TYPE |
| trapText | OBJECT-TYPE |
From SNMP-COMMUNITY-MIB
| snmpTrapAddress | OBJECT-TYPE |
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE |
From SNMPv2-TC
| DateAndTime | |
| DisplayString |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| sdm | 1.3.6.1.4.1.1166.1.100 | The MIB module for the SDM (SmartStream Device Manager). | ||
| INT sdmCategory | 1.3.6.1.4.1.1166.1.100.1.8 | INTEGER | accessible-for-notify | The object identifies the category, i.e. ITU Event Type, associated with the current trap. |
| sdmConfiguration | 1.3.6.1.4.1.1166.1.100.4 | |||
| sdmFault | 1.3.6.1.4.1.1166.1.100.3 | |||
| STR sdmObjectDescription | 1.3.6.1.4.1.1166.1.100.1.3 | DisplayString | accessible-for-notify | This object contains a user-defined description for the managed object associated with the current trap. |
| IP sdmObjectIPAddress | 1.3.6.1.4.1.1166.1.100.1.4 | IpAddress | accessible-for-notify | 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. |
| STR sdmObjectName | 1.3.6.1.4.1.1166.1.100.1.5 | DisplayString | accessible-for-notify | The object describes the name used by the SDM to uniquely identify the managed object associated with the current trap. |
| STR sdmObjectType | 1.3.6.1.4.1.1166.1.100.1.6 | DisplayString | accessible-for-notify | The object identifies the type of managed object associated with the current trap. |
| STR sdmProbableCause | 1.3.6.1.4.1.1166.1.100.1.1 | DisplayString | accessible-for-notify | 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. |
| STR sdmProbableCauseName | 1.3.6.1.4.1.1166.1.100.1.9 | DisplayString | accessible-for-notify | This object identifies the display name (title) of the event/alarm responsible for triggering this notification. |
| STR sdmProbableCauseText | 1.3.6.1.4.1.1166.1.100.1.2 | DisplayString | accessible-for-notify | 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. |
| sdmSystem | 1.3.6.1.4.1.1166.1.100.2 | |||
| sdmTraps | 1.3.6.1.4.1.1166.1.100.0 | |||
| sdmTrapVarbinds | 1.3.6.1.4.1.1166.1.100.1 | |||
| STR sdmUrl | 1.3.6.1.4.1.1166.1.100.1.7 | DisplayString | accessible-for-notify | The object contains an URL that provides additional information about the current trap. |
| NTF trapAlarmTransition | 1.3.6.1.4.1.1166.1.100.0.100 | 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. | ||
| NTF trapClearedCommunicationsFault | 1.3.6.1.4.1.1166.1.100.0.115 | 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. | ||
| NTF trapClearedEnvironmentalFault | 1.3.6.1.4.1.1166.1.100.0.155 | 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. | ||
| NTF trapClearedEquipmentFault | 1.3.6.1.4.1.1166.1.100.0.145 | 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. | ||
| NTF trapClearedIntegrityFault | 1.3.6.1.4.1.1166.1.100.0.165 | 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. | ||
| NTF trapClearedOperationalFault | 1.3.6.1.4.1.1166.1.100.0.175 | 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. | ||
| NTF trapClearedOtherFault | 1.3.6.1.4.1.1166.1.100.0.105 | 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. | ||
| NTF trapClearedPhysicalFault | 1.3.6.1.4.1.1166.1.100.0.185 | 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. | ||
| NTF trapClearedProcessingErrorFault | 1.3.6.1.4.1.1166.1.100.0.135 | 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. | ||
| NTF trapClearedQualityOfServiceFault | 1.3.6.1.4.1.1166.1.100.0.125 | 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. | ||
| NTF trapClearedSecurityFault | 1.3.6.1.4.1.1166.1.100.0.195 | 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. | ||
| NTF trapClearedTimeDomainFault | 1.3.6.1.4.1.1166.1.100.0.205 | 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. | ||
| NTF trapCriticalCommunicationsFault | 1.3.6.1.4.1.1166.1.100.0.111 | 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. | ||
| NTF trapCriticalEnvironmentalFault | 1.3.6.1.4.1.1166.1.100.0.151 | 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. | ||
| NTF trapCriticalEquipmentFault | 1.3.6.1.4.1.1166.1.100.0.141 | 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. | ||
| NTF trapCriticalIntegrityFault | 1.3.6.1.4.1.1166.1.100.0.161 | 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. | ||
| NTF trapCriticalOperationalFault | 1.3.6.1.4.1.1166.1.100.0.171 | 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. | ||
| NTF trapCriticalOtherFault | 1.3.6.1.4.1.1166.1.100.0.101 | 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. | ||
| NTF trapCriticalPhysicalFault | 1.3.6.1.4.1.1166.1.100.0.181 | 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. | ||
| NTF trapCriticalProcessingErrorFault | 1.3.6.1.4.1.1166.1.100.0.131 | 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. | ||
| NTF trapCriticalQualityOfServiceFault | 1.3.6.1.4.1.1166.1.100.0.121 | 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. | ||
| NTF trapCriticalSecurityFault | 1.3.6.1.4.1.1166.1.100.0.191 | 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. | ||
| NTF trapCriticalTimeDomainFault | 1.3.6.1.4.1.1166.1.100.0.201 | 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. | ||
| NTF trapEventNotification | 1.3.6.1.4.1.1166.1.100.0.99 | 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. | ||
| NTF trapInformationalCommunicationsFault | 1.3.6.1.4.1.1166.1.100.0.116 | 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. | ||
| NTF trapInformationalEnvironmentalFault | 1.3.6.1.4.1.1166.1.100.0.156 | 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. | ||
| NTF trapInformationalEquipmentFault | 1.3.6.1.4.1.1166.1.100.0.146 | 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. | ||
| NTF trapInformationalIntegrityFault | 1.3.6.1.4.1.1166.1.100.0.166 | 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. | ||
| NTF trapInformationalOperationalFault | 1.3.6.1.4.1.1166.1.100.0.176 | 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. | ||
| NTF trapInformationalOtherFault | 1.3.6.1.4.1.1166.1.100.0.106 | 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. | ||
| NTF trapInformationalPhysicalFault | 1.3.6.1.4.1.1166.1.100.0.186 | 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. | ||
| NTF trapInformationalProcessingErrorFault | 1.3.6.1.4.1.1166.1.100.0.136 | 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. | ||
| NTF trapInformationalQualityOfServiceFault | 1.3.6.1.4.1.1166.1.100.0.126 | 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. | ||
| NTF trapInformationalSecurityFault | 1.3.6.1.4.1.1166.1.100.0.196 | 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. | ||
| NTF trapInformationalTimeDomainFault | 1.3.6.1.4.1.1166.1.100.0.206 | 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. | ||
| NTF trapMajorCommunicationsFault | 1.3.6.1.4.1.1166.1.100.0.112 | 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. | ||
| NTF trapMajorEnvironmentalFault | 1.3.6.1.4.1.1166.1.100.0.152 | 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. | ||
| NTF trapMajorEquipmentFault | 1.3.6.1.4.1.1166.1.100.0.142 | 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. | ||
| NTF trapMajorIntegrityFault | 1.3.6.1.4.1.1166.1.100.0.162 | 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. | ||
| NTF trapMajorOperationalFault | 1.3.6.1.4.1.1166.1.100.0.172 | 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. | ||
| NTF trapMajorOtherFault | 1.3.6.1.4.1.1166.1.100.0.102 | 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. | ||
| NTF trapMajorPhysicalFault | 1.3.6.1.4.1.1166.1.100.0.182 | 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. | ||
| NTF trapMajorProcessingErrorFault | 1.3.6.1.4.1.1166.1.100.0.132 | 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. | ||
| NTF trapMajorQualityOfServiceFault | 1.3.6.1.4.1.1166.1.100.0.122 | 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. | ||
| NTF trapMajorSecurityFault | 1.3.6.1.4.1.1166.1.100.0.192 | 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. | ||
| NTF trapMajorTimeDomainFault | 1.3.6.1.4.1.1166.1.100.0.202 | 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. | ||
| NTF trapMinorCommunicationsFault | 1.3.6.1.4.1.1166.1.100.0.113 | 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. | ||
| NTF trapMinorEnvironmentalFault | 1.3.6.1.4.1.1166.1.100.0.153 | 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. | ||
| NTF trapMinorEquipmentFault | 1.3.6.1.4.1.1166.1.100.0.143 | 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. | ||
| NTF trapMinorIntegrityFault | 1.3.6.1.4.1.1166.1.100.0.163 | 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. | ||
| NTF trapMinorOperationalFault | 1.3.6.1.4.1.1166.1.100.0.173 | 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. | ||
| NTF trapMinorOtherFault | 1.3.6.1.4.1.1166.1.100.0.103 | 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. | ||
| NTF trapMinorPhysicalFault | 1.3.6.1.4.1.1166.1.100.0.183 | 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. | ||
| NTF trapMinorProcessingErrorFault | 1.3.6.1.4.1.1166.1.100.0.133 | 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. | ||
| NTF trapMinorQualityOfServiceFault | 1.3.6.1.4.1.1166.1.100.0.123 | 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. | ||
| NTF trapMinorSecurityFault | 1.3.6.1.4.1.1166.1.100.0.193 | 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. | ||
| NTF trapMinorTimeDomainFault | 1.3.6.1.4.1.1166.1.100.0.203 | 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. | ||
| NTF trapSdmHeartbeat | 1.3.6.1.4.1.1166.1.100.0.1 | 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. | ||
| NTF trapSdmObjectAdded | 1.3.6.1.4.1.1166.1.100.0.6 | 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. | ||
| NTF trapSdmObjectRemoved | 1.3.6.1.4.1.1166.1.100.0.7 | 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. | ||
| NTF trapSdmResynchCompleted | 1.3.6.1.4.1.1166.1.100.0.5 | 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 | ||
| NTF trapSdmResynchStarted | 1.3.6.1.4.1.1166.1.100.0.4 | 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) | ||
| NTF trapSdmStarted | 1.3.6.1.4.1.1166.1.100.0.2 | This trap is issued when the SDM application is started. | ||
| NTF trapSdmStopped | 1.3.6.1.4.1.1166.1.100.0.3 | 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. | ||
| NTF trapWarningCommunicationsFault | 1.3.6.1.4.1.1166.1.100.0.114 | 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. | ||
| NTF trapWarningEnvironmentalFault | 1.3.6.1.4.1.1166.1.100.0.154 | 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. | ||
| NTF trapWarningEquipmentFault | 1.3.6.1.4.1.1166.1.100.0.144 | 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. | ||
| NTF trapWarningIntegrityFault | 1.3.6.1.4.1.1166.1.100.0.164 | 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. | ||
| NTF trapWarningOperationalFault | 1.3.6.1.4.1.1166.1.100.0.174 | 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. | ||
| NTF trapWarningOtherFault | 1.3.6.1.4.1.1166.1.100.0.104 | 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. | ||
| NTF trapWarningPhysicalFault | 1.3.6.1.4.1.1166.1.100.0.184 | 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. | ||
| NTF trapWarningProcessingErrorFault | 1.3.6.1.4.1.1166.1.100.0.134 | 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. | ||
| NTF trapWarningQualityOfServiceFault | 1.3.6.1.4.1.1166.1.100.0.124 | 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. | ||
| NTF trapWarningSecurityFault | 1.3.6.1.4.1.1166.1.100.0.194 | 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. | ||
| NTF trapWarningTimeDomainFault | 1.3.6.1.4.1.1166.1.100.0.204 | 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. |
RFC description
SmartStream Device Manager MIB supporting northbound alarm and event notification traps for network element management.
Start monitoring Motorola broadband/cable network element (cable modem/headend) managed via SmartStream Device Manager with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.