Many of the 3rd party NAD profiles on this page is based on the community effort and any questions regarding the 3rd party support information within this page should be posted to the community forum. Please do not contact Cisco TAC for support regarding the NAD profiles within this page. Please refer to ISE compatibility guides for Cisco QA tested NADs. Also, read Does ISE support my NAD document for additional information on how to find out support for your NAD.
ISE Supports the RADIUS and TACACS Protocols
If your network access device can issue access control requests using the standard RADIUS and TACACS protocols then ISE can support it! ISE 2.0 and laterHowever, vendor hardware, software, vendor-specific attributes may affect what you need to do to implement your desired scenarios and capabilities. For more considerations on this topic, please see Does ISE Support My Network Access Device?.
Get Network Device Profiles and Configurations
All network device profiles and configurations uploaded to the ISE community should be tagged with ise-nad-profile. You may view a filtered list of all documents assigned a specific tag such as ise-nad-profile
How to Contribute Network Device Profiles
You may contribute a Network Device Profile to the community, too:
You should have created and tested your Network Device Profile in ISE under Administration > Network Resources > Network Device Profile.
Verify that the name of your profile matches the following naming convention to enable others to quickly identify what it is for: <Vendor>_<Series/Model>
Export your Network Device Profile to an XML file on your local computer
Choose Create > Uploaded File and select your exported network device profile XML file. Note: the Communities site will automatically convert your uploaded .XML file into a .ZIP file archive
Write a Description that includes the details about how it was configured and what hardware and software you tested with.
Include ise-nad-profile as one of the Tags. You may include other tags (ise,nad,profile,<vendor>, etc.) but using ise-nad-profile is how we enable you to quickly filter all documents within the Communities site for just network device profiles!
Network Device Profiles and Configs
Starting ISE 2.0, ISE supports third-party network access devices (NADs) for Authentication, Authorization and Accounting as well as advanced ISE flows such as Profiling, Posture assessment, Guess Access and BYOD. See the ISE Compatibility Guides for guidance on known supported vendors & platforms and recommended software versions.
Some of the advanced flows require special support from the NAD, such as RADIUS COA and URL Redirect in order to work properly. In case the NAD doesn't support those capabilities, see ISE 2.1 supports Auth VLAN
Third party NADs that don't support URL redirect can still be used by ISE in Auth VLAN deployment, where in this case, ISE is acting as the DHCP and DNS server. upon user connection, ISE assigns a temporary IP to the endpoint and upon first web request, ISE redirects the user to CWA to perform authentication. after successful authentication the endpoint in connected to the network with IP address assigned by the company's DHCP server. Minimal requirements for this topology is dynamic VLAN assignment and CoA (SNMP or standard).
The profiles below have been known to work. The profiles in bold are included in ISE 2.x.
Note: The first profile for a vendor & device does not have a type. Additional profiles will be named with different Types since multiple Series may use the same profile or the same family may have software updates that change the profile type.