Loading...
Loading...
Symptom Code Severity Description Condition 21000 Warning The system encountered an unexpected issue evaluating whether the CAS service can be disabled to mitigate security risk. Contact support to ensure that CAS remains enabled if used, or is disabled if not used. If the CAS_CONFIG_UPDATE_TASK is not created in the RT table due to any exception, this alert gets generated.
The CAS protocol is disabled by default on new installations and during upgrades (if CAS is not in use) to mitigate a security vulnerability (VRT-28848). During fresh install or upgrade to OBS 4.2+, this functionality checks for the special key CONFIG_KEY configId ClusterId in the RT table. If the Cluster ID is not found, system internal logic detects the missing ID and automatically disables CAS by updating the CMF parameter com.emc.ecs.service.cas.settings to disabled , then stopping the CAS service. The alert 21000 is raised when the CAS auto-disable task encounters an unexpected failure
This alert indicates the CAS auto-disabling task failed due to an unexpected error. The CAS CMF flag ( com.emc.ecs.service.cas.settings ) may still be enabled even though CAS is not in use. 1. Check CAS CMF Status: admin@localhost:~>svc_param info com.emc.ecs.service.cas.settings svc_param v1.2.5 (svc_tools v2.28.0) Started 2026-02-26 01:40:57Param: com.emc.ecs.service.cas.settings Description whether cas should start Default value (active) disabled Configured Value < Never modified > Modification reason None Last modified None 2. If CAS is not in use, m anually disable it. This stops the CAS service. svc_param set com.emc.ecs.service.cas.settings -v disabled -r "CAS is not used in this federation" 3. If CAS is in use, the customer should acknowledge the security risk of running CAS.
Click on a version to see all relevant bugs