Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
The CX Cloud Agent setup fails on connectivity verification, please see attached picture.Everything outgoing is allowed in the firewall.
nslookup from a machine in the same subnet to:cloudsso.cisco.com, api-cx.cisco.com etc works fine.
What could be ...
We have manually upgraded CSPCs from (2.10.0.1 and 2.10.0.4) to 2.10.0.7 successfully. But when login to GUI it prompts with "Collector Version Upgrade ... There is a new version of CSPC 2.10.0.6 available ..."
We tested with "systemctl restart admi...
CSPC 2.10.0.4 to 2.10.0.5 via GUI fails. So I'm trying via admin shell and run into the following situation.
The download initiated but after several hours its status is unclear. I'm wondering how to proceed further?
admin# download sp-30.3.0-5-0-lnx...
On An ISE multi-node fully distributed deployment, in a customer environment with multiple sites (more than 10) and endpoints not exceeding 2K in each site; deploying a dedicated PSN(VM appliances) on each site that will take care of sessions for tha...
We have a current certificate chain with a root certificate and an intermediate certificate that expires in two months.
In our case, we do not use the internal PKI that is built into ISE, but an external PKI where the root and intermediate certificat...
GUI is still prompting "Collector Version Upgrade ... There is a new version of CSPC 2.10.0.6 available ..." despite of CLI showing 2.10.0.7 as the current version.
As per the CLI "show version -d" the SP and JeOS seems to match 2.10.0.7
admin# sh version -dBuild-name : Collection Platform Software 2.10.0.7Package-type : ServicePackVersion : sp-30.3.0-7-0-lnx64Component : CSPC BaseVersion : 2.10.0.7Package-type ...
Still cannot delete an entitlement, getting error "Collector deactivation failed. Please try again. If the issue persists, find help in the community".
The problem it causing is that the reports are showing data comming from the inactive Collector.
OK, 15 PSN --> Large deployment.
Does it mean that all 15 PSNs should also be of Large profile size? despite of (some of them) are taking care of only up to 2K endpoints? Or is it possible to have PSNs with Small profile size among them?
Is there onl...
