03-20-2018 04:43 AM - edited 03-20-2019 10:00 PM
Hello,
Anyone know more details about this issue? on any upgrade do you see that problem?
It says that apply to path1 and 2, but not say any workaround and not solved in any version.
Thanks, regards
04-30-2018 12:46 PM
The lack of details is insane, Also the workaround has been changed to upgrade to 2.4... Its kind of like my car has a bad spark plug so we need to change out the engine... Some updates from Cisco would be nice.
05-03-2018 05:39 AM
Since no one at Cisco wants to document the issue. Here is below for TAC. Hope this saves someone else time...
The problem is happening because of a known defect as some of the EDF objects are not getting synchronized between the nodes, manually syncing up is a workaround. If the alarms are not coming now then I will suggest to leave it.
This is fixed on ISE 2.4. It has also been tagged for 2.3 P4, however the planning would begin in mid of May, so it might take couple of months from then to get this defect in the patch.
10-04-2018 03:09 PM
Still not Fixed in 2.3 Patch 5.
10-05-2018 03:58 AM
I have not had any issues since installing patch 4. Was it specifically for alarm objects?
10-09-2018 03:43 PM
Yes, It appears so. Deployment has 2 ISE nodes.
1st node roles PRI(A), SEC(M)
2nd node roles SEC(A), PRI(M)
Modifying an alert configuration, this will generate the replication alarm and configuratoin is not replicated to 2nd node.
ie disable an alarm, but you will continue to recieve the alrams untill you do a full sync
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide