Troubleshoot 802.1X with an LDAP identity store
Users authenticate on the switch through RADIUS against an LDAP directory, and nobody gets on. Follow the failure reasons from the switch to the RADIUS log to the directory and fix each layer.
Scenario
SW1 sends 802.1X requests to the RADIUS server ISE (10.99.99.10). ISE has no local users: it binds to the directory DC (10.99.99.20, base dc=corp,dc=local) as cn=svc-ise,dc=corp,dc=local and maps the Engineering group to VLAN 10 and Sales to VLAN 20. Yesterday the directory team rotated the service account's password to Ld4p!2026, and since then bob (Engineering, PC1) and carol (Sales, PC2) cannot get on. The shared secret for SW1 on ISE is Cisco!Rad. Find and fix every fault so both users land in their VLANs.
Your tasks
- bob on PC1 is authorized by 802.1X into VLAN 10 and has a DHCP lease in 10.10.10.0/24.
- carol on PC2 is authorized by 802.1X into VLAN 20 and has a lease in 10.20.20.0/24.
The lab checks the result, not the exact commands. For example, a ping task passes only when the ping really succeeds through the network you built.