Standard view Table view

AFFIRMED-TEMS-NOTIFICATION-MIB

        Management Information for notification/alarming the NB NMS / OSS Systems.
Source file
AFFIRMED-TEMS-NOTIFICATION-MIB
Last revised
Identity
affirmedTemsNotifications
Base OID
1.3.6.1.4.1.37963.6.3.1
Imported Objects
AFFIRMED-TEMS-OBJECTS-MIB perfMetricClearThreshold perfMetricCriticalThreshold perfMetricMajorThreshold perfMetricMinorThreshold temsServerPerfMetric temsServerPerfMetricCollectedValue
AFFIRMED-TEMS-SNMP-MIB affirmedSnmpNotifications
AFFIRMED-TEMS-TC-MIB AlarmLevel AlarmLevelString
SNMPv2-SMI IpAddress MODULE-IDENTITY NOTIFICATION-TYPE
SNMPv2-TC DateAndTime DisplayString TEXTUAL-CONVENTION TruthValue
Net-SNMP examples using the microsoft MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'AFFIRMED-TEMS-NOTIFICATION-MIB' -M '/opt/observium/mibs/microsoft:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AFFIRMED-TEMS-NOTIFICATION-MIB::affirmedTemsNotifications'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'AFFIRMED-TEMS-NOTIFICATION-MIB' -M '/opt/observium/mibs/microsoft:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AFFIRMED-TEMS-NOTIFICATION-MIB::affirmedTemsNotifications'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (23)
affirmedTemsNotifications
.1.3.6.1.4.1.37963.6.3.1
notificationConfig
.1.3.6.1.4.1.37963.6.3.1.1
suppressAlarms r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.37963.6.3.1.1.1
notificationObjects
.1.3.6.1.4.1.37963.6.3.1.2
temsServerTimeStamp
SNMPv2-TCDateAndTime
 .1.3.6.1.4.1.37963.6.3.1.2.1
emsNodeIPAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.37963.6.3.1.2.10
emsClusterChangeNotificationData
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.11
vCenterOldStatus
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.12
vCenterNewStatus
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.13
vCenterTargetObjectType
Enumeration
 .1.3.6.1.4.1.37963.6.3.1.2.14
alarmRemedy
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.15
alarmAdditionalInfo
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.16
alarmTrapOID
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.17
elementHostName
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.18
alarmSeverity
AFFIRMED-TEMS-TC-MIBAlarmLevelString
 .1.3.6.1.4.1.37963.6.3.1.2.2
alarmDiagnosticData
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.3
networkElementIPAddress
SNMPv2-SMIIpAddress
 .1.3.6.1.4.1.37963.6.3.1.2.4
networkElementSoftwareVersion
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.5
cliUserName
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.6
notificationAddress
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.7
sourceComponent
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.8
alarmCategory
SNMPv2-TCDisplayString
 .1.3.6.1.4.1.37963.6.3.1.2.9
temsNorthBoundNotifications
.1.3.6.1.4.1.37963.6.3.1.3
Dependencies (10) 5 direct · 5 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. AFFIRMED-SNMP-MIBmicrosoft
  3. AFFIRMED-TEMS-SNMP-MIBmicrosoft
  4. SNMPv2-TCrfc
  5. AFFIRMED-TEMS-TC-MIBmicrosoft
  6. IANAifType-MIBrfc
  7. RFC-1212rfc
  8. RFC1155-SMIrfc
  9. RFC1213-MIBrfc
  10. AFFIRMED-TEMS-OBJECTS-MIBmicrosoft
  11. AFFIRMED-TEMS-NOTIFICATION-MIBmicrosoftselected
Notifications / Traps (31)
NameOIDDescription
networkElementNotReachable
networkElementIPAddress alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.1
Management Server will send this notification to its NB Clients (NMS / OSS) whenever
a managed network element turns unreachable (ICMP).
temsServerPerfMetricMinorTCA
networkElementIPAddress AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetric AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetricCollectedValue AFFIRMED-TEMS-OBJECTS-MIBperfMetricMinorThreshold alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.10
Management Server will send this notification to its NB Clients (NMS / OSS) to report
a Minor Threshold Crossing Alert, whenever the Minor Threshold limit is
crossed for the current Performance Metric
temsServerPerfMetricClearTCA
networkElementIPAddress AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetric AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetricCollectedValue AFFIRMED-TEMS-OBJECTS-MIBperfMetricClearThreshold alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.11
Management Server will send this notification to its NB Clients (NMS / OSS) to Clear
the previously raised Critical / Major / Minor TCA for this Performance Metric.
alarmFromNetworkElement
networkElementIPAddress sourceComponent alarmCategory alarmSeverity alarmDiagnosticData temsServerTimeStamp alarmRemedy alarmAdditionalInfo alarmTrapOID elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.12
Management Server will send this notification to its NB Clients (NMS / OSS) to report
an Alarm Raised due to the occurrence of a trap from the Network Element.
Severity List includes Cleared. the Clear Alarm should clear the previous raise Alarm.
The combination of networkElementIPAddress, sourceComponent (if any), alarmCategory (if available)
and alarmSeverity shall be used to uniquely identify a specific root cause
hotStandbyTakesOver deprecated
alarmDiagnosticData temsServerTimeStamp
.1.3.6.1.4.1.37963.6.3.1.3.13
Indicates a Switchover of the Management server from primary to Standby Server.
Note: This alarm will be triggered only when the Management Server is deployed in a Primary - HotStandBy mode.
primaryServerisRestored deprecated
alarmDiagnosticData temsServerTimeStamp
.1.3.6.1.4.1.37963.6.3.1.3.14
Indicates that the Primary Management Server has been restored back in Service.
Note: This alarm will be triggered only when the Management Server is deployed in a Primary - HotStandBy mode.
alarmfromElementManagementSystem
networkElementIPAddress sourceComponent alarmCategory alarmSeverity alarmDiagnosticData temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.15
Management Server will send this notification to its NB Clients (NMS / OSS) to report
an Alarm Raised due to the occurence of a trap from the Network Management System.
Severity List includes Cleared. the Clear Alarm should clear the previous raise Alarm.
The combination of networkElementIPAddress, sourceComponent (if any), alarmCategory (if available)
and alarmSeverity shall be used to uniquely identify a specific root cause
geoRedundancyGroupMismatch
sourceComponent networkElementIPAddress alarmDiagnosticData alarmSeverity temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.16
Management server will send this notification to its NB clients (NMS / OSS) when it detects
mismatch information from EMS, active and standby network element
The networkElementIpAddress attribute is populated with the Mgmt Server IP address
vnfScaleKpiMonitorAlarm
sourceComponent networkElementIPAddress alarmDiagnosticData alarmSeverity temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.17
Dynamic VM capacity management KPI monitoring alarms.
Source is cluster[vclusterId]/<KPIName> where KPIName can be
DCMSession, WSMSession, ASMConn, ASMThruput.
Severity may be of one of the three values: MAJOR, CRITICAL, CLEARED
MAJOR The respective KPI is transitioned to one of the following states:
Underload threshold crossed for 80% of the duration or
Overload threshold crossed for 80% of the duration
CRITICAL The respective KPI is transitioned to one of the following states:
Underload condition
Overload condition
CLEARED The respective KPI is transitioned to one of the following states:
Normal condition, i.e. in neither underload nor overload condition
The networkElementIpAddress attribute is populated with the Mgmt Server IP address
vnfScaleOutAlarm
sourceComponent networkElementIPAddress alarmDiagnosticData alarmSeverity temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.18
Generated when VM scale out operation fails
Source is cluster[vclusterId]/node[vnodeId]. Severity will be CRITICAL.
The networkElementIpAddress attribute is populated with the Mgmt Server IP address
vnfScaleInAlarm
sourceComponent networkElementIPAddress alarmDiagnosticData alarmSeverity temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.19
Generated when VM scale in operation fails
Source is cluster[vclusterId]/node[vnodeId]. Severity will be CRITICAL.
The networkElementIpAddress attribute is populated with the Mgmt Server IP address
networkElementNotManageable
networkElementIPAddress alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.2
Management Server will send this notification to its NB Clients (NMS / OSS) whenever
a managed network element is reachable via ICMP but not reachable via the Management protocol (SNMP / TL1 )
emsClusterStatusChangeNotification
emsNodeIPAddress emsClusterChangeNotificationData alarmSeverity temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.20
Management Server will send this notification to its NB Clients (NMS / OSS) upon its
detection of cluster status change
alarmFromVCenter
networkElementIPAddress alarmCategory vCenterTargetObjectType vCenterOldStatus vCenterNewStatus alarmDiagnosticData sourceComponent temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.21
Management Server will send this notification to its NB Clients (NMS / OSS) to report
an Alarm Raised due to the occurence of a trap from VCenter Server
cliLoginSuccess
networkElementIPAddress cliUserName alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.22
Management Server will send this notification to its NB Clients (NMS / OSS) whenever it
could be login to the CLI (or TL1) session of the Network Element using the supplied
Credentials
cliTemplateConfigFailed
networkElementIPAddress alarmDiagnosticData sourceComponent temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.23
Management Server will send this notification to its NB Clients (NMS / OSS) whenever
cli template configuration failed.
cliTemplateConfigSuccess
networkElementIPAddress alarmDiagnosticData sourceComponent temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.24
Management Server will send this notification to its NB Clients (NMS / OSS) whenever
cli template configuration succeeds.
alarmtriggeredCliTemplateConfigFailed
networkElementIPAddress alarmDiagnosticData sourceComponent temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.25
Management Server will send this notification to its NB Clients (NMS / OSS) whenever
alarm triggered cli template configuration failed.
alarmtriggeredCliTemplateConfigSuccess
networkElementIPAddress alarmDiagnosticData sourceComponent temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.26
Management Server will send this notification to its NB Clients (NMS / OSS) whenever
alarm triggered cli template configuration succeeds.
alarmSnmpNotificationFailure
sourceComponent alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.27
Management Server will send this notification to its NB Clients (NMS / OSS) upon its
Failure to forward the trap to NB Clients registered for Trap Forwarding.
masterSlaveStandbyNodeDown
networkElementIPAddress alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.28
Management Server will send this notification to its NB Clients (NMS / OSS) to reports that
in cluster topology standby node moved to down state.
masterSlaveStandbyNodeUp
networkElementIPAddress alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.29
Management Server will send this notification to its NB Clients (NMS / OSS) to reports that
in cluster topology standby node moved to up state.
networkElementManageable
networkElementIPAddress alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.3
Management Server will send this notification to its NB Clients (NMS / OSS) to clear the
not manageable events raised previously.
networkElementAutoUnmanage
networkElementIPAddress alarmCategory alarmSeverity alarmDiagnosticData temsServerTimeStamp alarmRemedy elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.32
Device has been automatically unmanaged due to authentication failure.
networkElementManage
networkElementIPAddress alarmCategory alarmSeverity alarmDiagnosticData temsServerTimeStamp elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.33
Device has been managed successfully.
unSupportedNetworkElementVersion
networkElementIPAddress networkElementSoftwareVersion alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.4
Management Server will send this notification to its NB Clients (NMS / OSS) whenever it
encounters / discovers a Network element running an Unsupported software version.
cliLoginFailed
networkElementIPAddress cliUserName alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.5
Management Server will send this notification to its NB Clients (NMS / OSS) whenever it
could not login to the CLI (or TL1) session of the Network Element using the supplied
Credentials
alarmEmailNotificationFailure
notificationAddress alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.6
Management Server will send this notification to its NB Clients (NMS / OSS) upon its
Failure to send the E-Mail Notification to NB Clients registered for E-Mail Notification
dataCollectionFailure
networkElementIPAddress AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetric alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.7
Indicates a Failure during Data Collection.
NB managers can either ignore it (or) log-it.
temsServerPerfMetricCriticalTCA
networkElementIPAddress AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetric AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetricCollectedValue AFFIRMED-TEMS-OBJECTS-MIBperfMetricCriticalThreshold alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.8
Management Server will send this notification to its NB Clients (NMS / OSS) to report
a Critical Threshold Crossing Alert, whenever the Critical Threshold limit is
crossed for the current Performance Metric
temsServerPerfMetricMajorTCA
networkElementIPAddress AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetric AFFIRMED-TEMS-OBJECTS-MIBtemsServerPerfMetricCollectedValue AFFIRMED-TEMS-OBJECTS-MIBperfMetricMajorThreshold alarmDiagnosticData temsServerTimeStamp alarmSeverity elementHostName
.1.3.6.1.4.1.37963.6.3.1.3.9
Management Server will send this notification to its NB Clients (NMS / OSS) to report
a Major Threshold Crossing Alert, whenever the Major Threshold limit is
crossed for the current Performance Metric