Alarm for SCRX Health Degradation
Article ID: 391490
Updated On:
Products
Issue/Introduction
The SCRX container on the host node from where the alarm is emitted is down.
Environment
Impacted NSX Version 4.2.2
Impact is that traffic will not be subject to IDPS rules / policies, and malicious traffic could go undetected.
Cause
This scenario is rare, and it is not possible to attribute this to a specific reason. The alarm has been created to inform the user about the degradation.
Resolution
Login to the ESX host for which the alarm is generated and stop the
SCRX pod using the command `/etc/init.d/nsx-scx-<pod number> stop`.
After it has stopped, restart the pod using the command
`/etc/init.d/nsx-scx-<pod-number> start`.
Verify the status of the SCRX pod using the command
`/etc/init.d/nsx-scx-<pod-number>` to see if it is running.
If the pod does not appear in running state, collect the support
bundle and contact Broadcom Support.
===========
If the security services container on the host is down after attempting a resize operation, you may try these steps:
1. Change the desired size on the cluster via the UI or API:
/policy/api/v1/infra/settings/scrx/cluster-configs/<clusterid>
2. Alternatively, increase capacity on the host to support the configured size.
Feedback
