06-04-2020 05:40 AM
Dear Team;
i created Downloadable ACL in ise for a VLAN 10.50.30.0 /24
in this vlan we are able to ping gateway and servers , but not address ip 10.50.30.100 , the ping not working for any address in this vlan
first configuration
permit udp any eq bootpc any eq bootps
permit udp any any eq 53
permit ip any host 10.50.30.254 (gateway)
permit ip any host 10.50.30.100
permit ip any host 192.168.16.30 (server)
permit ip any host 192.168.16.34 (server)
i changed the configuration
permit udp any eq bootpc any eq bootps
permit udp any any eq 53
permit ip any host 10.50.30.254 (gateway)
permit ip any host 10.50.30.100
permit ip any host 192.168.16.30 (server)
permit ip any host 192.168.16.34 (server)
permit icmp any host 10.50.30.100 echo-reply
permit icmp any host 10.50.30.100 unreachable
permit icmp any host 10.50.30.100 time-exceeded
but the problem still persists
Solved! Go to Solution.
06-12-2020 04:01 PM
This sounds more like a routing/ACL issue than an ISE issue since ISE is applying the ACL successfully to the switch.
Suggest calling TAC to help you troubleshoot since the community suggestions have stopped.
06-04-2020 09:06 PM
06-05-2020 06:31 AM
Hi @Nadia Bbz ,
In addition to what @Francesco Molino said, start at the basic troubleshooting:
check if the DACL was downloaded and applied successfully:
show auth session interface Gi x/y detail
show ip access-list interface Gi x/y
If you are in the same VLAN, check if your machine has learn the ARP.
If you are not in the same VLAN, check if the traceroute is working.
Take capture on 10.50.30.100 and see if it's getting packets. Take capture on your machine to see if you are sending the packets correctly.
06-07-2020 09:29 AM - edited 06-07-2020 09:29 AM
Adding to the others. IP Device Tracking or SISF-Based Device Tracking needs working on your Cisco IOS-based switch for DACL to work.
Best to start troubleshooting by not using DACL at all and then PERMIT_ALL_IPV4_TRAFFIC (or another DACL that permit all access).
06-08-2020 02:04 AM - edited 06-08-2020 02:06 AM
Hey @hslai @Anurag Sharma @Francesco Molino ;
Thanks for your help I greatly appreciate it.
yes ACL are applied to the user session
Result for troubleshooting
1/ tracert 10.50.30.100
Traceroute to WKS01.xx.xx [10.50.30.100], 30 hops max
1 * * * request timed out
2 * * * request timed out
3 * * * request timed out .
4 * * * request timed out.
2/ tracert 192.168.16.30
Traceroute to serv.xx.xx [192.168.16.30], 30 hops max
1 3 ms <1 ms <1 ms 10.50.30.254
2 <1 ms <1 ms <1 ms xx.xx.xx.xx
3 13 ms <1 ms <1 ms xx.xx.xx.xx
4 1 ms 1 ms 1 ms serv.xx.xx [192.168.16.30]
3/ arp -a
Interface : 10.50.30.101 --- 0x9
internet Address physique Type
10.50.30.100 xx-xx-xx-xx-xx-xx dynamic
10.50.30.254 xx-xx-xx-xx-xx-xx dynamic
10.50.30.255 xx-xx-xx-xx-xx-xx static
xx.xx.xx.xx xx-xx-xx-xx-xx-xx static
xx.xx.xx.xx xx-xx-xx-xx-xx-xx static
xx.xx.xx.xx xx-xx-xx-xx-xx-xx static
255.255.255.255 xx-xx-xx-xx-xx-xx static
when i type this command show auth session interface Gi x/y detail i see that the DACL is applied successfully
show ip access-list interface Gi x/y no result because ACL is created in ISE not in Switch
i created another DACL with PERMIT_ALL_TRAFFIC [ permit ip any any]
The ping work for any address in this Vlan
06-08-2020 04:18 AM
Hi @Nadia Bbz ,
arp -a
Interface : 10.50.30.101 --- 0x9
internet Address physique Type
10.50.30.100 xx-xx-xx-xx-xx-xx dynamic
The above output shows that we are able to learn the L2 address. The traceroute packets (ICMP) should have just gone to the server at 10.50.30.100 itself. I'd suggest you check the following two things:
06-09-2020 06:33 PM
06-12-2020 04:01 PM
This sounds more like a routing/ACL issue than an ISE issue since ISE is applying the ACL successfully to the switch.
Suggest calling TAC to help you troubleshoot since the community suggestions have stopped.
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