Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synchronization Issue with CISCO ISE #5

Open
amriunix opened this issue Nov 30, 2020 · 6 comments
Open

Synchronization Issue with CISCO ISE #5

amriunix opened this issue Nov 30, 2020 · 6 comments

Comments

@amriunix
Copy link

IL;DR

Following the documentation (README.md), we've faced an ISE synchronization issue with the latest docker image of adaptive-policy-ise-sync from docker hub.

Bug Identification

8

9

From the screenshots above you can see that the adaptive-policy-ise-sync didn't synchronized with the CISCO ISE

Bug Confirmation

To confirm the source of this bug, we tested the first docker version and it works as it need to be!

10

@joshand
Copy link
Collaborator

joshand commented Nov 30, 2020

Apologies - I forgot that I broke out the sync logic into a separate process that was not added to the docker start script. I just pushed a new version of the Docker image and this should be working now, so if you re-pull it should work. Please let me know!

@amriunix
Copy link
Author

amriunix commented Dec 3, 2020

Hello, now i can see that the synchronization works great. However I figure out that i can't synchronize all SGTs from ISE to Meraki !

@joshand
Copy link
Collaborator

joshand commented Dec 3, 2020

Can you provide some detail of exactly what you are seeing? You've marked the SGTs that you want to sync, correct?

@amriunix
Copy link
Author

amriunix commented Dec 7, 2020

It was just a bug!
I figured out that if you choose the ISE as an Authoritative Source, then you need only to select the SGTs with "Meraki missing" because if you select a SGT with "ISE Missing" it will crash the application.

image

@joshand
Copy link
Collaborator

joshand commented Dec 7, 2020

Hmmmm, well that is definitely not supposed to happen. Did you receive errors in your console that you can provide?

@amriunix
Copy link
Author

amriunix commented Dec 8, 2020

Actually, i didn't check that because the container was running in background.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants