04-16-2025 03:52 AM - edited 04-16-2025 05:25 AM
Solved! Go to Solution.
04-16-2025 06:21 AM
@Davis-Revent-12 I don't foresee a problem with this, MACsec will be enabled on the interfaces connecting the switches and NAC (802.1X/MAB) enabled on the switchports the endpoints are connected too. The switches will need a mgmt IP address to be able to communicate with ISE using RADIUS and configured for NAC.
Yes you can daisy chain another switch, just don't enable NAC on the interfaces between switches.
04-16-2025 06:21 AM
@Davis-Revent-12 I don't foresee a problem with this, MACsec will be enabled on the interfaces connecting the switches and NAC (802.1X/MAB) enabled on the switchports the endpoints are connected too. The switches will need a mgmt IP address to be able to communicate with ISE using RADIUS and configured for NAC.
Yes you can daisy chain another switch, just don't enable NAC on the interfaces between switches.
04-16-2025 07:23 PM - edited 04-16-2025 07:32 PM
Hi Rob
Thanks for the confirming what I thought also. Yeah I cannot see why it would not work., Noted also on not enabling NAC on any of the switch to switch connections be it they use macsec or not .
So our connection would be something along these lines
Site 1 FD switch <Fiber with macseclink> Site 2 switch A <Fiber link> Site 2 Switch B .
Site 2 switches access ports only enabled with NAC
Cheers
04-16-2025 06:34 AM
Should be no issue.
04-16-2025 07:24 PM
Thanks for responding back also and confirming as such
Cheers
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