Lists the known limitations of the Cisco ISE Cloud Central Agent to help understand any functionality constraints.
Refer to this topic to understand the limitationsns in the Cisco ISE Cloud Central Agent .
|
Issue |
Condition |
Recommended action |
|---|---|---|
|
The agent cannot connect after a pxGrid certificate expires. |
The pxGrid certificate on the ISE deployment is expired. |
Replace the expired certificate in Cisco ISE, then check the agent connection again. |
|
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 certificate status in Cisco ISE and replace any expired or invalid certificate. |
|
The agent connection may be lost after an ISE upgrade. |
After a Cisco ISE upgrade, the agent status is not found or disconnected. |
Reinstall the agent using the supported installation procedure. |