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.
Get Network Device Profiles
All network device profiles uploaded to the ISE community should be tagged with ise-nad-profile.
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).
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.N?T
I'm sure people might have come across this problem numerous times previously. However, I was unabe to get something on this page. So posting this. We have a deployment where we are turning on wired NAC with dot1x with MAB as failover. My understandi...
HiWe have bunch of Cisco ISE virtual appliance with software version 2.6 and smart license installed. We have 2 PAN & PSN (Pri & Sec) and couple of PSN. Out of this we have to move one of the PAN to new VLAN with new IP address. Please advise...
Dear community members, a customer have to regenerate a S2S-Tunnel (IKEv1) on his ASA runneing a 9.X release but the IPsec Proposal is still missing (see attached ASDM screen dump).He has still an old ASCII configuration but he cannot find a IPsec Pr...
Hi Guys,I am reaching out for some help in making some configuring changes to a cisco 2901 router.I am looking to make a firewall change to allow SFTP (port 22) access on 184.108.40.206 through to 10.0.80.12 server from WAN IP 220.127.116.11.Would highly app...