I have 2 unit of ISE appliance. 3415-k9. Herein after call ISE A and ISE B. Initially the appliance is come with version 2.0. The client want the site A to setup 2 x ISE with version 2.3 and the policy to be follow the HQ policy, but do not join the HQ cluster.
In order to make it faster, I have registered ISE A to HQ cluster to sync the configuration, and then deregister it to make it as standalone. ISE A had been successfully upgraded to version 2.3 patch 1. ISE B had been factory default (Previously with configuration), then upgraded to version 2.3 patch 1 without configuration.
After upgraded of both ISE, I try to register ISE B into ISE A to form cluster. After couple of time, it show sync failed and registration failed. I am pretty sure the dns had no issue as I can ping to each other using fqdn. If the dns having issue, the error message will pop up when i click submit during register node.
Note:
1. Both ISE A and ISE B are within same segment of IP.
2. Both ISE using ver2.3 patch 1.
My Question:
1. since ISE A join the HQ cluster before as PSN, would it be possible causing my issue when i use it as All in one unit after deregister from HQ cluster?
2. As per my current temporary setup, HQ PAN node IP same segment as ISE A and ISE B. Would it be possible that within the IP segment, there should not be 2 different cluster appear? Meaning when i move the ISE A and ISE B out of this segment, the issue will resolve?
3. Would it be possible it hitting ver 2.3 bugs? Anybody face the similar problem? Any suggestion to resolve the problem?
