Server will send this notification to its NB Clients (NMS / OSS) whenever
a managed network element turns unreachable (ICMP).
temsServerPerfMetricMinorTCA
.1.3.6.1.4.1.37963.6.3.1.3.10
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
.1.3.6.1.4.1.37963.6.3.1.3.11
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
.1.3.6.1.4.1.37963.6.3.1.3.12
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
.1.3.6.1.4.1.37963.6.3.1.3.13
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
.1.3.6.1.4.1.37963.6.3.1.3.14
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
.1.3.6.1.4.1.37963.6.3.1.3.15
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
.1.3.6.1.4.1.37963.6.3.1.3.16
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
.1.3.6.1.4.1.37963.6.3.1.3.17
capacity management KPI monitoring alarms.
Source is cluster[vclusterId]/ 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
.1.3.6.1.4.1.37963.6.3.1.3.18
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
.1.3.6.1.4.1.37963.6.3.1.3.19
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
.1.3.6.1.4.1.37963.6.3.1.3.2
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
.1.3.6.1.4.1.37963.6.3.1.3.20
Server will send this notification to its NB Clients (NMS / OSS) upon its
detection of cluster status change
alarmFromVCenter
.1.3.6.1.4.1.37963.6.3.1.3.21
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
.1.3.6.1.4.1.37963.6.3.1.3.22
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
.1.3.6.1.4.1.37963.6.3.1.3.23
Server will send this notification to its NB Clients (NMS / OSS) whenever
cli template configuration failed.
cliTemplateConfigSuccess
.1.3.6.1.4.1.37963.6.3.1.3.24
Server will send this notification to its NB Clients (NMS / OSS) whenever
cli template configuration succeeds.
alarmtriggeredCliTemplateConfigFailed
.1.3.6.1.4.1.37963.6.3.1.3.25
Server will send this notification to its NB Clients (NMS / OSS) whenever
alarm triggered cli template configuration failed.
alarmtriggeredCliTemplateConfigSuccess
.1.3.6.1.4.1.37963.6.3.1.3.26
Server will send this notification to its NB Clients (NMS / OSS) whenever
alarm triggered cli template configuration succeeds.
alarmSnmpNotificationFailure
.1.3.6.1.4.1.37963.6.3.1.3.27
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
.1.3.6.1.4.1.37963.6.3.1.3.28
Server will send this notification to its NB Clients (NMS / OSS) to reports that
in cluster topology standby node moved to down state.
masterSlaveStandbyNodeUp
.1.3.6.1.4.1.37963.6.3.1.3.29
Server will send this notification to its NB Clients (NMS / OSS) to reports that
in cluster topology standby node moved to up state.
networkElementManageable
.1.3.6.1.4.1.37963.6.3.1.3.3
Server will send this notification to its NB Clients (NMS / OSS) to clear the
not manageable events raised previously.
networkElementAutoUnmanage
.1.3.6.1.4.1.37963.6.3.1.3.32
Device has been automatically unmanaged due to authentication failure.
networkElementManage
.1.3.6.1.4.1.37963.6.3.1.3.33
Device has been managed successfully.
unSupportedNetworkElementVersion
.1.3.6.1.4.1.37963.6.3.1.3.4
Server will send this notification to its NB Clients (NMS / OSS) whenever it
encounters / discovers a Network element running an Unsupported software version.
cliLoginFailed
.1.3.6.1.4.1.37963.6.3.1.3.5
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
.1.3.6.1.4.1.37963.6.3.1.3.6
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
.1.3.6.1.4.1.37963.6.3.1.3.7
a Failure during Data Collection.
NB managers can either ignore it (or) log-it.
temsServerPerfMetricCriticalTCA
.1.3.6.1.4.1.37963.6.3.1.3.8
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
.1.3.6.1.4.1.37963.6.3.1.3.9
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
affirmedTemsNotifications 
suppressAlarms 
networkElementNotReachable