MC Not Secured Alarm
The alarm is applicable only to the Media Transcoding Cluster feature (
acMCNotSecuredAlarm
|
Alarm |
acMCNotSecuredAlarm |
||||||||
|---|---|---|---|---|---|---|---|---|---|
|
OID |
1.3.6.1.4.1.5003.9.10.1.21.2.0.151 |
||||||||
|
Description |
This alarm is sent when the connection between the Signaling Component (SC) and at least one of the Media Components (MC) remains unsecured when the upgrade of all the MCs by SC does not fully complete. This typically happens when SC failover occurs during the upgrade of the MCs from an unsecured media cluster version to a secured (TLS) one. |
||||||||
|
Default Severity |
Warning |
||||||||
|
Source Varbind Text |
Board#1/clusterManager#0/MTCE#xxx |
||||||||
|
Event Type |
securityServiceOrMechanismViolation |
||||||||
|
Probable Cause |
versionMismatch |
||||||||
|
Severity |
Condition |
Text |
Corrective Action |
||||||
|
Warning |
When the SC is configured to operate in the secured (TLS) mode and then a switchover to the redundant SC occurs, an MC in the cluster still connects to SC in an unsecured (TCP) mode. As a result, the connection between SC and MC remains unsecured. |
"MC <MTCEName> should be upgraded" "MC <MTCEName> should be restarted" |
Reset or upgrade the MC. |
||||||
|
SC is configured to operate in the secured (TLS) mode and MC is configured to operate in the unsecured (TCP) mode. However, there is no MC image in the SC repository and therefore, the MC cannot be upgraded and is still connected in the unsecured mode. |
"MC <MTCEName> should be upgraded" |
Upload an MC image to the SC repository and then upgrade the MC that is currently connected in the unsecured mode. |
|||||||
|
Cleared |
|
- |
- |
||||||