01-06-2015 02:05 AM - edited 03-10-2019 10:19 PM
Hi,
while reading about Closed mode deployment of ISE, I came across conflict in Cisco's "HowTo-10-Universal_Switch_Config" and "HowTo-25-Closed_Mode" documents.
According to "HowTo-10-Universal_Switch_Config", in Closed Mode, we need to apply a ACL on switch port as follows
ip access-list ext ACL-DEFAULT
remark DHCP
permit udp any eq bootpc any eq bootps
remark DNS
permit udp any any eq domain
remark Ping
permit icmp any any
remark PXE / TFTP
permit udp any any eq tftp
remark Drop all the rest
deny ip any any log
But according to "HowTo-25-Closed_Mode", in Closed Mode, we don't apply this ACL on switchport.
So my question is, if the ACL need to applied on Switchport or not..and how it will affect switchport
Thanks,
Aditya
Solved! Go to Solution.
01-12-2015 06:11 PM
Sorry for the delay Aditya as I got really busy at work. Did you read the link that I provided? It really provides answers and different options to your issue.
I personally prefer NOT to configure an ACL and let the system use the default one. However, if you choose that path, make sure that you are always returning a DACL with your authorization profiles, even if it is just "permit ip any any"
Thank you for rating helpful posts!
01-06-2015 10:32 AM
Hello Aditya-
Very good question. The default ACL will always be there on the switch weather you configure one or not. Check out this document:
You have two options:
1. Create your own default ACL to avoid the default one (that only allows DHCP). Your default ACL should be more permissive than the default one. For instance, mine always included "permit ip any any." That way authenticated and authorized hosts are not blocked from accessing any resources on the network.
2. Always return a DACL in your ISE authorization profiles (even if it is just "permit ip any any". That way the default-ACL is removed
I prefer method number #2 that way I don't have to bother with the default ACL and it also allows me to control traffic based on the different authorization profiles and DACLs that I apply.
I hope this helps!
Thank you for rating helpful posts!
01-07-2015 02:55 AM
Hi Neno,
Thanks for reply.
I agree that DACLs should be included in profile.
The main objective of "Closed Mode" is to provide access only after 802.1x authentication.
while reading about "Closed Mode", I came across conflict in Cisco Documents as I mentioned earlier.
so my question is, should we apply ACL on the port or no need to apply any ACL on port in "Closed Mode"
Thanks,
Aditya
01-12-2015 06:11 PM
Sorry for the delay Aditya as I got really busy at work. Did you read the link that I provided? It really provides answers and different options to your issue.
I personally prefer NOT to configure an ACL and let the system use the default one. However, if you choose that path, make sure that you are always returning a DACL with your authorization profiles, even if it is just "permit ip any any"
Thank you for rating helpful posts!
01-14-2015 03:34 AM
Hi Neno,
Thank you for reply.
Regards,
Aditya
01-14-2015 09:23 AM
You are welcome! Glad I could help!
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