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.
Good day everyone We have an old ISE deployment that was registered to a license that will expire in the beginning of December 2025. This deployment is EOL and will be replaced by a new ISE deployment. A new license was procured that will expire in 2...
We have a 3 node deployment ISE1-PAN (Admin, MNT, PSN), ISE2-SPAN (Admin, MNT, PSN) and ISE3-HEALTH (Health node)To test the failover we shut the network ports on the ISE1-PAN, after the configured polling intervals the ISE3-HEALTH triggered the f...
Initially we want to run the old and new deployments concurrently and want to use the same IP ranges for the new servers.Eg:Current deployment has single persona nodes, excluding out of band management (CIMC)CPT_Admin1 - 10.12.13.2 (VlanX) DataCPT_Ad...
The purpose is to test the feature to see how it operates and determine if it is suitable for our environment and if not use the manual failover procedure. We have now encountered this issue and we need some guidance on how to recover back to the pre...
It is the design of the deployment architecture. We are still in pre-production and busy testing the failover scenarios and this what happened during testing. We now want to recover back to where all the nodes are back and in sync.ISE1-PAN is operati...
Thank you for the reply yes, it looks like that is the same process.The current deployment is on 3.1 patch 4. Our main concern was just to confirm that when we upgrade the 1st server for the new deployment to 3.4 patch 7 and make it the Primary node ...
