Troubleshoot health status failures

You can run a health status check to review the overall health of Security Connector. If Security Connector is offline, this process pinpoints where a failure is occurring. If you cannot resolve an issue, contact ​Akamai​ Support.

This table describes Security Connector operations that are checked and the mitigation steps that are suggested to resolve a failure:

Operation

Description

Resolution to Failure

AMG Activation

Indicates whether Security Connector was successfully activated.

Confirm that:

  • Security Connector is activated. To activate Security Connector, see [Activate the security connector](doc:generate-activation-code1).connector](doc:generate-activation-code1).
  • Run a connectivity test in the Security Connector network diagnostics to identify the connectivity issue that is causing this failure. For more information, see [Run a connectivity test](doc:run-connectivity-test).

AMG Connectivity

Indicates whether Security Connector can connect to ​Akamai​.

Confirm that:

  • Security Connector is activated. To activate Security Connector, see [Activate the security connector](doc:generate-activation-code1).connector](doc:generate-activation-code1).
  • Run a connectivity test in the Security Connector network diagnostics to identify the connectivity issue that is causing this failure. For more information, see [Run a connectivity test](doc:run-connectivity-test).

CAS Key Rotation

Security Connector backend service.

Confirm that:

  • Security Connector is activated. To activate Security Connector, see [Activate the security connector](doc:generate-activation-code1).connector](doc:generate-activation-code1).
  • Run a connectivity test in the Security Connector network diagnostics to identify the connectivity issue that is causing this failure. For more information, see [Run a connectivity test](doc:run-connectivity-test).

CAS Registration

Security Connector backend service that is responsible for activation.

Confirm that:

  • Security Connector is activated. To activate Security Connector, see [Activate the security connector](doc:generate-activation-code1).connector](doc:generate-activation-code1).
  • Run a connectivity test in the Security Connector network diagnostics to identify the connectivity issue that is causing this failure. For more information, see [Run a connectivity test](doc:run-connectivity-test).

CAS Reporting

Backend service that’s responsible for ETP Reports.

Confirm that:

  • Security Connector is activated. To activate Security Connector, see [Activate the security connector](doc:generate-activation-code1).connector](doc:generate-activation-code1).
  • Run a connectivity test in the Security Connector network diagnostics to identify the connectivity issue that is causing this failure. For more information, see [Run a connectivity test](doc:run-connectivity-test).

CSI Authentication Token

Token that’s used to deliver logs and data to ETP reports.

Confirm that:

  • Security Connector is allowed to access <> Cloud services over port 443.443.
  • Security Connector can reach the CSI service. You can run a ping test with the CSI service hostname. To find this hostname, see [View debug information](doc:security-connector-status#view-debug-information). To perform a ping test, see [Run a Ping test](doc:security-connector-status#run-a-ping-test).

CSI Log Posting

Service that’s used to deliver logs and data to ETP reports.

Confirm that:

  • Security Connector is allowed to access <> Cloud services over port 443.443.
  • Security Connector can reach the CSI service. You can run a ping test with the CSI service hostname. To find this hostname, see [View debug information](doc:security-connector-status#view-debug-information). To perform a ping test, see [Run a Ping test](doc:security-connector-status#run-a-ping-test).

CPU Load

Operation that tracks the overall traffic load of Security Connector.

  • Verify the configuration to check if only risky domains are sent to Security Connector for IP attribution.attribution.
  • Verify if any test traffic is directed to the Security Connector IP address.

Disk Use

Operation that tracks disk space of the Security Connector VM.

  • Verify the configuration to check if only risky domains are sent to Security Connector for IP attribution.attribution.
  • Verify if any test traffic is directed to the Security Connector IP address.address.
  • Review the logging mode of the Security Connector web console.

NTP Sync

Operation for Network Time Protocol synchronization.

Confirm that your firewall is not blocking UDP port 123.

Web Console Certificate

Operation for checking whether the Web Console Certificate is valid

Confirm that:

  • The root CA is installed on the device that’s used to access the Security Connector Web Console.
  • Security Connector is activated.
  • The browser supports signed Elliptic Curve Digital Signature Algorithm (ECDSA) certificates.

View Security Connector health status

You can check the overall health of Security Connector. If Security Connector is offline, this area of the console allows you to identify the operation where the failure occurred.

To view Security Connector health status:

  1. In the Security Connector main menu, press 6 or use the arrow keys to select View Health Status and then press Enter. Security Connector performs the health check.
  2. If a failure occurs, see Health status check for more information on how to resolve the issue.

Did this page help you?