11-04-2019 08:54 AM
hi,
We are using 2.4 patch 9 ISE version, We have created various MAB group to allow the non dot1x supported devices. and also we have migrated the sites to closed mode.
Currently we observe few endpoints which are added to the MAB group are getting removed to the MAB group automatically and device authentication has failed which has caused the downtime in the network.
Could you please advice is there any specific reason for the endpoints to get removed automatically from the Cisco ISE MAB group.
regards
Arjun.S
Solved! Go to Solution.
11-04-2019 09:22 AM
11-04-2019 09:12 AM
Hi Arjun,
You should open a TAC case to determine the actual cause.
If you do not have the "static group assignment" checked, its possible profiling is changing the endpoint. When you change it back, the device more than likely will not re-profile to change the group again.
If you do have "Static group assignment" checked, you could be facing a bug like CSCvi73782 or CSCvk55076
11-04-2019 09:22 AM
11-04-2019 10:46 PM
Hi,
Please correct me if my understanding is wrong.
1: When we manually add a device to the MAB group "Static Assignment Group" will be checked automatically.
2: Endpoint Purge is for the device which not profiled by ISE, if a endpoint is added to a MAB group it will not be Purged.
regards
Arjun.S
11-05-2019 06:24 AM
1. Statically assign an endpoint if you do not want it to automatically change from the group.
2. Endpoint purge can be for any endpoint group. By default, it removes endpoints that are 30 days old from GuestEndpoints or RegisteredDevices.
You can check your rules under Administration > Identity Management > Settings > Endpoint Purge
If the group you are using does not match anything there, you should upgrade your patch level to the nest patch for 2.4. If it reproduces, please contact TAC.
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