03-31-2020 09:29 AM - edited 03-31-2020 12:13 PM
Hello - We are just starting with Meraki and need to import Network Devices into ISE 2.4. Does Meraki gear require the need to build a custom Network Device Profile inside ISE or does it use the default Cisco profile? I looked at the design guide and couldn't see this outlined, I assume it would use the Cisco profile. Any thoughts or suggestions?
Thanks!
Solved! Go to Solution.
04-05-2020 07:26 AM
Meraki uses the existing Cisco network device profile.
You will notice in the Authorization Profiles section of How To: Integrate Meraki Networks with ISE that Meraki uses the Airespace ACL Name attributes from the AireOS WLC. There is even a Note that explains the re-use:
Note: The Airespace ACL Name is the name of the group policy configured on the Meraki cloud controller (Figure 3) for use with ISE Authorization Profile. The Meraki cloud controller can be configured to look for 1 of 3 compatible RADIUS messages from Cisco ISE: Filter-ID, Airespace-ACL-Name and Reply-Message. This example uses Airespace-ACL-Name.
04-05-2020 07:26 AM
Meraki uses the existing Cisco network device profile.
You will notice in the Authorization Profiles section of How To: Integrate Meraki Networks with ISE that Meraki uses the Airespace ACL Name attributes from the AireOS WLC. There is even a Note that explains the re-use:
Note: The Airespace ACL Name is the name of the group policy configured on the Meraki cloud controller (Figure 3) for use with ISE Authorization Profile. The Meraki cloud controller can be configured to look for 1 of 3 compatible RADIUS messages from Cisco ISE: Filter-ID, Airespace-ACL-Name and Reply-Message. This example uses Airespace-ACL-Name.
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