Unix v2 Endpoint Deletion Failure on Inaccessible Hosts

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

When attempting to delete a Unix v2 endpoint that is no longer reachable (e.g., the server has been shut down or decommissioned), the Provisioning Server may return a connection timeout error. This occurs because the connector server attempts to establish a connection to the endpoint to verify its status before proceeding with the deletion.

Environment

Identity Manager 14.x

Cause

The deletion operation fails because the endpoint is unpingable or the service port is closed. The Provisioning Server requires connectivity to the endpoint to process the deletion request successfully.

Resolution

To delete an inaccessible or shut-down endpoint, use one of the following methods:

Method 1: Host File Redirection (Recommended Workaround) If the endpoint is unreachable, you can trick the Provisioning Server into believing it is connecting to a reachable host:

1. Identify the hostname of the shut-down endpoint.
2. On the Identity Manager Provisioning Server, edit the local hosts file (e.g., /etc/hosts or C:\Windows\System32\drivers\etc\hosts).
3. Add an entry mapping the endpoint’s hostname to the IP address of a reachable, pingable server in your network.
4. Retry the deletion of the endpoint from the Provisioning Manager.
5. Once the endpoint is successfully deleted, remove the entry you added to the hosts file.

Method 2: Prevention

• Always delete endpoints from the Provisioning Manager before shutting down or decommissioning the underlying host.

Error Details If you attempt to delete an unreachable endpoint, you may see the following error in your logs: ETA_E_0011, Endpoint 'Hostname' deletion failed: Connector Server Add failed: code 52 (UNAVAILABLE) JCS@#######: Connection timed out: connect (ldaps://hostname:20411)