This document provides an example of TACACS+ authentication configuration on a Nexus switch. By default, if you configure the Nexus switch in order to authenticate through Access Control Server (ACS), you are automatically placed in the network-operator/vdc-operator role, which provides read-only access. In order to be placed in the network-admin/vdc-admin role, you need to create a shell on the ACS 5.2. This document describes that process.
Ensure that you meet these requirements before you attempt this configuration:
Define your Nexus switch as a client in ACS.
Define the IP address and an identical shared secret key on the ACS and Nexus.
Note: Create a checkpoint or a backup on Nexus before you make any changes.
The information in this document is based on these software and hardware versions:
Nexus 5000, 5.2(1)N1(1)
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
there are two Tunnels in NSX edge 1- one between NSX to branch ( Sophos FW ) and it is working fine no issue 2- another one in the same NSX and other sites ( Sophos ) also and we have some times ( 3-4) disconnection ...
I'm reviewing a CISCO CES configuration. There is a profanity dictionary, however it doesn't seem to be used or working. How can I determine if any filters or other settings use a particular dictionary?
Hi All, I have a scenario. We have a VOIP server. VoIP is only accessible publicly for specific ips. i have users sitting on remote location.When they connect with vpn they can configure their soft phones with VOIP private ip but they cannot configur...
When i connect the cisco vpn with my job server. I am trying to work but if i try to do something the program gave me an error "vpn connection terminated smartcard removed from reader" how can i fix it? Can you please help me about this situation immediat...
Hi, I have a problem with my AnyConnect Split-tunnel configuration. When connected I am able to ping or reach internal subnets which have been specified in the split-tunnel ACL but I can't ping nor reach any public sites that I want to be reached th...