Cisco ISE Cloud Central Agent Integration Guide

Cisco ISE Cloud Central Common Setup Issues

Updated: November 12, 2026

Want to summarize with AI?

Lists common issues of the Cisco ISE Cloud Central Agent and troubleshooting tips.

The Cisco ISE Cloud Central Agent setup page displays the recent operation output after you initiate cloud tethering for easy reference and troubleshooting.

Use this table to identify and troubleshoot common issues of the Cisco ISE Cloud Central Agent.

Table 1. Common setup issues and actions
Issue	Condition	Recommended action
The installation bundle or repository cannot be found.	Installation fails with a message that the bundle or repository is missing.	Confirm that the repository name is correct and that the bundle is in that repository under its original filename. Run the installation command again.
The Cisco ISE release or available disk space is unsupported.	Installation fails because the ISE release is unsupported or the appliance does not have enough free space.	Confirm that your Cisco ISE release and patch meet requiremens and that at least 4 GB of free space is available on the node.
The tethering token is rejected.	The token has expired or was previously used.	The token might have expired or already been used. In Cisco Cloud Control, open the integration’s edit page and reset the agent credentials. Enter the replacement token at the CLI prompt. You do not need to reinstall the agent.
Cisco ISE cannot reach Cisco Cloud Control.	The agent cannot connect or the integration does not become active.	Confirm that outbound HTTPS traffic from Cisco ISE to Cisco Cloud Control is allowed. For the required destination IP addresses, refer to Outbound connectivity requirements. These addresses apply to Cisco ISE Cloud Central Agent connectivity.
Cisco ISE sign-in fails during setup.	The installer rejects the administrator credentials.	Use a Cisco ISE account with the Super Admin role and check the password. The installer prompts you to sign in again.
The pxGrid client does not become active.	Setup is waiting for a new pxGrid client to become active.	In Cisco ISE, approve the pxGrid client by choosing Administration > pxGrid Services > Client Management. You can also change settings in the Cisco ISE Cloud Central Agent GUI at `https://<ISE node>/ise-cloud-central-agent/setup/`. If your browser displays a certificate warning, do not continue. Install the Cisco ISE Admin certificate first.
The agent is already installed on this node.	Installation reports that the agent is already installed.	Do not reinstall until the correct procedure is confirmed.
Setup was interrupted or Finish setup was selected too early.	You left the page or selected Finish setup too early.	In Cisco Cloud Control, open the Cisco ISE integration from Integrations in Cisco Cloud Control and select Resume setup. Generate a new token if the existing token has expired or was already used..
The agent cannot connect after a pxGrid certificate expires.	The pxGrid certificate on the ISE deployment is expired.	Replace the expired pxGrid certificate in Cisco ISE, then check the agent connection. For certificate requirements, refer to Certificate requirements for Cisco ISE nodes.
The agent is disconnected after a PAN or MnT failover.	The agent status is Not found or Disconnected after a failover.	Reinstall the Cisco ISE Cloud Central Agent using the supported installation procedure.
The deployment has multiple agent installations.	An agent was installed on more than one ISE node in the same deployment.	Install the agent on the Primary PAN (PPAN) only.
The Users page may not show endpoint updates in real time.	An endpoint receives an update, but the change has not appeared in Cisco Cloud Control.	Check again later; if the information remains stale, contact Cisco Support.
Deleted endpoints may still appear in Cisco Cloud Control.	Endpoints have been purged from Cisco ISE but remain visible in Cisco Cloud Control.	Contact Cisco Support if the records remain visible.
The agent connection is unavailable after the agent stops unexpectedly.	The agent process has stopped and has not restarted automatically.	stopped and has not restarted automatically.Restart the agent using the supported Cisco ISE procedure
A certificate issue may prevent integration.	The Cisco ISE system certificate or pxGrid certificate is invalid, expired, or otherwise unsuitable.	Check the Cisco ISE system and pxGrid certificates. Replace any expired or invalid certificate. For certificate requirements, refer to Certificate requirements for Cisco ISE nodes
The agent connection may be lost after an ISE upgrade.	Cisco ISE is upgraded from 3.3 Patch 12 to 3.5 Patch 5, or from 3.4 Patch 7 to 3.5 Patch 4 and the agent no longer connects.	Reinstall the agent using the supported installation procedure.

Contact Support

If the issue persists, open a Cisco Support case.

Include the following information:

Cisco ISE release and patch
Cisco ISE Cloud Central Agent version
The time the issue occurred
The agent and integration status shown in the setup page and Cisco Cloud Control
The agent logs from [location] and the Cisco ISE logs from [location]

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.