The patch package install fail clear notification.
hwBaseLinkSubHealthy
.1.3.6.1.4.1.2011.5.25.348.2.12.1
The base plane link subhealth value was larger than the threshold, Base plane goes subhealth. The problem may cause a high packet loss rate.
hwBaseLinkSubHealthyResume
.1.3.6.1.4.1.2011.5.25.348.2.12.2
The base plane link subhealth value was lower than the threshold. Base plane goes health.
hwRUCreateFailAlarm
.1.3.6.1.4.1.2011.5.25.348.2.13.1
The VM create RU failed. And the RU can not work normal.
hwRUCreateFailResume
.1.3.6.1.4.1.2011.5.25.348.2.13.2
The VM has created the RU.
hwVnfcConnectionLost
.1.3.6.1.4.1.2011.5.25.348.2.2.1
The connection between the VNFP and VNFC fails.
hwVnfcConnectionResume
.1.3.6.1.4.1.2011.5.25.348.2.2.2
The connection between the VNFP and VNFC is restored.
hwVMInconsist
.1.3.6.1.4.1.2011.5.25.348.2.3.1
Local VM resources are inconsistent with VM resources on the MANO.
hwVMInconsistResume
.1.3.6.1.4.1.2011.5.25.348.2.3.2
Local VM resources are consistent with VM resources on the MANO.
hwVMAdd
.1.3.6.1.4.1.2011.5.25.348.2.3.3
The VM was added.
hwVMDelete
.1.3.6.1.4.1.2011.5.25.348.2.3.4
The VM was deleted.
hwVMFaultAlarm
.1.3.6.1.4.1.2011.5.25.348.2.3.5
A fault occurs on a VM.
hwVMFaultAlarmResume
.1.3.6.1.4.1.2011.5.25.348.2.3.6
The fault on the VM is cleared.
hwVirtualPortDown
.1.3.6.1.4.1.2011.5.25.348.2.4.1
The virtual interface went Down.
hwVirtualPortDownResume
.1.3.6.1.4.1.2011.5.25.348.2.4.2
The virtual interface Down alarm was cleared.
hwVNFMConnectionFault
.1.3.6.1.4.1.2011.5.25.348.2.5.1
The connection between the VNF and VNFM was faulty.
hwVNFMConnectionFaultResume
.1.3.6.1.4.1.2011.5.25.348.2.5.2
The fault in the connection between the VNF and VNFM was rectified.
hwVMMemoryUsageRisingAlarm
.1.3.6.1.4.1.2011.5.25.348.2.6.1
When the Memory usage remains greater than the Memory alarm threshold for a period of time, this alarm is generated.
hwVMMemoryUsageResume
.1.3.6.1.4.1.2011.5.25.348.2.6.2
When the Memory usage remains less than the Memory alarm clearance threshold for a period of time, this alarm is cleared.
hwVMCPUUsageRisingAlarm
.1.3.6.1.4.1.2011.5.25.348.2.7.1
When the average CPU usage is greater than the CPU alarm threshold, this alarm is generated.
hwVMCPUUsageResume
.1.3.6.1.4.1.2011.5.25.348.2.7.2
When the average CPU usage is less than the CPU alarm clearance threshold, this alarm is cleared.
hwVMDiskInvalid
.1.3.6.1.4.1.2011.5.25.348.2.8.1
This object indicates that an alarm is generated when a VM disk fails.
hwVMDiskInvalidResume
.1.3.6.1.4.1.2011.5.25.348.2.8.2
This object indicates that an alarm is cleared when a VM disk fault is rectified.
hwVMDiskPartitionInValid
.1.3.6.1.4.1.2011.5.25.348.2.8.3
An alarm was generated when a disk partition was unavailable.
hwVMDiskPartitionInValidResume
.1.3.6.1.4.1.2011.5.25.348.2.8.4
The alarm was cleared when the disk partition became available.
hwVMDiskPartitionSpacinsufficient
.1.3.6.1.4.1.2011.5.25.348.2.8.5
An alarm was generated when the disk partition's(except the log partition) available space was below the threshold.
hwVMDiskPartitionSpacinsufficientResume
.1.3.6.1.4.1.2011.5.25.348.2.8.6
The alarm was cleared when the disk partition's(except the log partition) available space was above the threshold.
hwVMDiskPartitionUseageRising
.1.3.6.1.4.1.2011.5.25.348.2.8.7
When the disk partition usage(except the log partition) is greater than the specified overload threshold within a statistical period, the alarm is reported.
hwVMDiskPartitionUseageResume
.1.3.6.1.4.1.2011.5.25.348.2.8.8
When the disk partition usage(except the log partition) fell and remained below 10% of the specified overload threshold within a statistical period, the alarm is cleared.