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.
Hi all, presenting my plan for ISE upgrade to find out any potential flaws/caveats, could you please provide feedback? Diagram is attached for clarity.
A. Existing deployment: 2.6 (patch 12)B. Target deployment: 3.1 (patch 10)C. 6x VMs are built on t...
I've used the "Check Bug Applicability" tool for this bug ID, and for all 7 S/Ns I've entered into it, the result was "The FN72424/bug CSCwc47544 is not applicable...".
Once we eventually got access to the access points CLI, it was obvious that all a...
Hi all, the original plan had been recently followed in real life. Here is the updated plan that was tested and can be reliably adopted if anybody still needs to upgrade from ISE 2.6 to the currently recommended release (and upgrading to 3.1 is a nec...
Hi, @balaji.bandi ,
Thank you for your reply. Yes, joining each node to the AD separately is included in the process. Smart licensing is also considered (the necessary licenses have been procured and verified in the Smart Account) and connectivity to...
Hi @Arne Bier ,
Thank you for the reply and pointing out the inaccuracy in my post. Yes, it was a typo there: NODE_A242 (SAN/SMnT/PSN) is the node being de-registered from 2.6 first, and a freshly mint 3.1 VM is taking over its name and address. The ...
I’ve double checked and found out what the issue was. All serial numbers that I’ve submitted to the tool originally, had an “S” accidentally prepended to them. I.e., instead of the actual S/N FGLxxxxxxxx I’ve submitted to the tool the value of “SFGLx...
