07-21-2025 03:51 PM
Hello,
For some reason, an authentication request for node 172.23.140.200 is hitting the wrong Network Devices Group, though there is a long prefix/32 available. Consequently, the wrong Policy-Set is chosen with Privilege Level1.
Usually ISE is expected to hit the longest prefix
#1 Arista_mgmt: 172.23.140.200/32
#6: Private-172-Network1: 172.23.128.0/20
Jun 19 17:27:22 ISE-1 CISE_Passed_Authentications 0485078549 4 0 2025-06-19 17:27:22.220 -04:00 59105442473 5201
NOTICE Passed-Authentication: Authentication succeeded, ConfigVersionId=71, Device IP Address=172.23.140.200,
DestinationIPAddress=******, DestinationPort=49, UserName=cvpadmin, Protocol=Tacacs, NetworkDeviceName=Private-172-Network1,
Type=Authentication, Action=Login, Privilege-Level=1,
Any advice is much appreciated.
07-22-2025 12:32 PM
3.1 patch 3 is very old at this point. I would not spend any time troubleshooting this issue until you upgrade to the latest 3.1 patch.
07-22-2025 01:01 PM
Did you try change device profile under network device list ?
MHM
07-23-2025 09:10 AM
Thank you MHM.
Under Work Centers > Network Access > Network Devices: the IP is listed under Network Devices List.
I would appreciate, if you could please guide me where the device profile is linked to the network device list.
Please keep in mind that other IPs in the same Network Device List are hitting the proper policy [based on the logs].
07-23-2025 09:40 AM
I check cisco doc and other notes
Device profile not send as radius attribute so ISE can not use it to identify device.
Retrun to IP conflict'
ISE support range of IP so you can use range of IP to exclude single device IP from device group
I.e. 10.0.0.100/32 single
10.0.0.0/24 device group
In ISE add IP for device group as
10.0.0.1-10.0.0.99
10.0.0.101-10.0.0.254
Hope this help you to solve problem
MHM
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