ISE 1.1.4 to 1.2 Upgrade Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2016 10:47 PM - edited 03-10-2019 11:51 PM
Hi,
I'm trying to replicate a customer setup in my lab before upgrading the production servers. I have two VMs that I have patched to level 13 (the latest 1.1.4 patch available) but when I go to do the upgrade I get the following message:-
% Error: Unable to inform the current Primary that a new deployment is being formed.
Starting application after rollback
Looking at the Deployment page on the Primary node it tells me the secondary node is in sync.
One question - if I create a repository from the GUI on the primary node, should that appear on the secondary? I only ask to see if this is an indication of problems.
Both nodes are on the same subnet - so nothing in the way.
Does anyone have any ideas?
Thanks
Al
- Labels:
-
AAA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2016 09:27 AM
It has been a while since I have worked with 1.1.x but as far as I remember when you create repositories from:
1. CLI - The repository is local and not replicated to the the rest of the nodes in the deployment
2. GUI - The repository is replicated to all nodes in the deployment.
Thus, if you are not seeing the repository in your secondary node and due to the error message that you are getting, I am guessing that you are having some sort of replication and/or communication issue.
You can try to manually sync up the nodes and then test again.
I hope this helps!
Thank you for rating helpful posts!
