Troubleshoot secure event connector registration failure

This task helps you identify and resolve common issues that prevent the Secure Event Connector (SEC) from successfully registering to the eventing cloud service.

Symptom: Registration of Cisco Secure Event Connector to cloud eventing service fails.

Diagnosis: These are the most common reasons that the SEC fails to register to the eventing cloud service.

  • The SEC is unable to reach the Eventing cloud service from SEC

    Repair: Ensure that Internet is accessible on port 443 and DNS is configured correctly.

  • Registration failure due to invalid or expired one-time-password in SEC bootstrapdata

    Repair:

Procedure

Step 1

SSH to the host VM as the admin user, typically cdo.

Step 2

Switch to the sdc user usingthe command: sudo su - sdc.

Step 3

View the connector log by running command sdc eventing logs --type connector.

Note

If the registration has failed due to an invalid token, you see an error message in the log file similar to the example below:

context:(*contextImpl).handleFailed] registration - CE2001: Registration failed - Failed to register the device because of invalid token. Retry with a new valid token.

Step 4

Remove the SEC.

Step 5

Add a new SEC in the UI and re-onboard.

The Secure Event Connector successfully registers to the cloud eventing service and registration failures are resolved.