Configuring Tacacs with Nexus 1000v

Hi Experts,Does
anyone share a sample configuration of AAA (Tacacs+) with Nexus 1000v?
I have found some documents, but it only covers authentication, no one
document found that can cover authorization, and accounting in detail
with Nexus 100v.Thanks and Regards,
Ahmed Shahzad.
Hi Ahmed,
Check out the below link for TACAS configuration in Nexus 1000
http://cco.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0/security/configuration/guide/security_4tacacs.html
Hope to Help !!
Ganesh.H

Similar Messages

Weird syslog format messages with Nexus 1000v

I'm trying out the Nexus 1000v, and have the VEM configured to write logs to my syslog server. The thing is, the messages are in a weird format that my log management tools cannot parse. Here is an example:
<189>: 2012 Oct 21 15:22:40 UTC: %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on unknown_session
I found the documentation rather amusing, where it states "The syslog client functionality is RFC-5424 compliant" - doesn't look like they've even read the RFC! This is closer to the format of the older (but more often found in the wild, RFC3164... though not compliant with that either :/
Anyway, I guess the main issue here is that the hostname of the 1000v is not being added to the logs (it is set in my config). Any ideas how I can fix this?
Thanks!

Hi,
Do you have vCenter install on Win2012 Server? The installation would not continue until you have vCenter installed.
Hardik

VN-Tag with Nexus 1000v and Blades

Hi folks,
A while ago there was a discussion on this forum regarding the use of Catalyst 3020/3120 blades switches in conjunction with VN-tag. Specifically, you can't do VN-Tag with that Catalyst blade switch sitting inbetween the Nexus 1000V and the Nexus 5000. I know there's a Blade switch for the IBM blade servers, but will there be a similar version for the HP C-class blades? My guess is NO, since Cisco just kicked HP to the curb. But if that's the case, what are my options? Pass-through switches? (ugh!)
Previous thread:
https://supportforums.cisco.com/message/469303#469303

wondering the same...

New vcenter server but keeping database with nexus 1000v

I have been reading through all the details of migrating to new hardware for the vcenter server with the nexus 1000v. i wish to avoid doing the vswitch thing. If I am keeping the same database but just moving to new hardware and possibly new ip address I was hoping to be able to do something along the lines of.
Leave everything as is,
Reinstall vcenter on new server and point to existing database.
reconnect the esx hosts
disconnect the VSM
get the xml from the vsm
install on vcenter server
reconnect the VSM to the new server
all should be good.
From my reading it appears as tho most of the issues are around connecting to a fresh database.
Is there anything wrong with my assumptions??
Regards Justin

I have done this before but I always keep the same name an IP so that I don't have to reconnect each ESXi host and my vSphere Client users don't have to use a different name.
What I do in this scenario is build the new server with a temp name/IP.
Backup the vCenter DB and SSL certs (this is very important).
Power down the old vCenter.
Re-IP/Re-Name the new to match the old.
Copy the SSL certs to the proper location (C:\ProgramData\VMware\VMware VirtualCenter\SSL)
Create your DSN and install vCenter using the old DB. The DB will be upgraded.
Your hosts will automatically connect to the new server.

Install and Configure Nexus 1000V

Hi all !! Hope everyone is well !!
I just purchase 2 Nexus 1000V's. Could someone give me some guidance on how to go about installing / configuring a Nexus 1000V switch ? This is my first time working with Nexus series switches. Thanks in advance !!!
D.

Hi,
Here are some of the documents and video links that will help you to proceed futher with Nexus 1000v installation:
http://www.cciemachine.com/en/US/products/ps9902/prod_installation_guides_list.html
http://www.google.co.in/search?q=nexus+1000v+installation&hl=en&client=firefox-a&hs=Hnt&rls=org.mozilla:en-US:official&prmd=v&source=univ&tbs=vid:1&tbo=u&ei=WtloTI6hAc-rcbb98I8F&sa=X&oi=video_result_group&ct=title&resnum=4&ved=0CCwQqwQwAw

VWLC and Nexus-1000V

Hi Experts!
Does anybody try to install vWLC on ESX with Nexus-1000V as switch?
All deployment guide are based on standard VMWare vSwitch and I can not find any information about questions:
1. Is vWLC compatible with Nexus-1000V?
2. What configuration should be done on Nexus-1000V to vWLC works properly?

Hi Dave,
You can access below URL for nexus 1000v -4.0(4)SV1(3b) docs:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3_b/roadmap/guide/n1000v_roadmap.html
And
Nexus5000
http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html
BR,
John Meng

[Nexus 1000v] VEM can't be add into VSM

hi all,
following my lab, i have some problems with Nexus 1000V when VEM can't be add into VSM.
+ on VSM has already installed on ESX 1 (standalone or ha) and you can see:
Cisco_N1KV# show module
Mod Ports Module-Type                       Model               Status
1    0      Virtual Supervisor Module         Nexus1000V          active *
Mod Sw                Hw
1    4.2(1)SV1(4a)     0.0
Mod MAC-Address(es)                         Serial-Num
1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP        Server-UUID                           Server-Name
1    10.4.110.123     NA                                    NA
+ on ESX2 that 's installed VEM
[root@esxhoadq ~]# vem status
VEM modules are loaded
Switch Name      Num Ports   Used Ports Configured Ports MTU     Uplinks
vSwitch0         128         3           128               1500    vmnic0
VEM Agent (vemdpa) is running
[root@esxhoadq ~]#
any advices for this,
thanks so much

Hi,
i'm having similar issue: the VEM insatlled on the ESXi is not showing up on the VSM.
please check from the following what can be wrong?
This is the VEM status:
~ # vem status -v
Package vssnet-esx5.5.0-00000-release
Version 4.2.1.1.4.1.0-2.0.1
Build 1
Date Wed Jul 27 04:42:14 PDT 2011
Number of PassThru NICs are 0
VEM modules are loaded
Switch Name     Num Ports   Used Ports Configured Ports MTU     Uplinks
vSwitch0         128         4           128               1500   vmnic0
DVS Name         Num Ports   Used Ports Configured Ports MTU     Uplinks
VSM11           256         40         256               1500   vmnic2,vmnic1
Number of PassThru NICs are 0
VEM Agent (vemdpa) is running
~ # vemcmd show port
LTL   VSM Port Admin Link State PC-LTL SGID Vem Port
   18               UP   UP   F/B*     0       vmnic1
   19             DOWN   UP   BLK       0       vmnic2
* F/B: Port is BLOCKED on some of the vlans.
Please run "vemcmd show port vlans" to see the details.
~ # vemcmd show trunk
Trunk port 6 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 16 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 18 native_vlan 1 CBL 0
vlan(111) cbl 1, vlan(112) cbl 1,
~ # vemcmd show port
LTL   VSM Port Admin Link State PC-LTL SGID Vem Port
   18               UP   UP   F/B*     0       vmnic1
   19            DOWN   UP   BLK       0       vmnic2
* F/B: Port is BLOCKED on some of the vlans.
Please run "vemcmd show port vlans" to see the details.
~ # vemcmd show port vlans
                       Native VLAN   Allowed
LTL   VSM Port Mode VLAN   State Vlans
   18             T       1   FWD   111-112
   19             A       1   BLK   1
~ # vemcmd show port
LTL   VSM Port Admin Link State PC-LTL SGID Vem Port
   18               UP   UP   F/B*     0       vmnic1
   19             DOWN   UP   BLK       0       vmnic2
* F/B: Port is BLOCKED on some of the vlans.
Please run "vemcmd show port vlans" to see the details.
~ # vemcmd show port vlans
                       Native VLAN   Allowed
LTL   VSM Port Mode VLAN   State Vlans
   18             T       1   FWD   111-112
   19             A       1   BLK   1
~ # vemcmd show trunk
Trunk port 6 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 16 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 18 native_vlan 1 CBL 0
vlan(111) cbl 1, vlan(112) cbl 1,
~ # vemcmd show card
Card UUID type 2: ebd44e72-456b-11e0-0610-00000000108f
Card name: esx
Switch name: VSM11
Switch alias: DvsPortset-0
Switch uuid: c4 be 2c 50 36 c5 71 97-44 41 1f c0 43 8e 45 78
Card domain: 1
Card slot: 1
VEM Tunnel Mode: L2 Mode
VEM Control (AIPC) MAC: 00:02:3d:10:01:00
VEM Packet (Inband) MAC: 00:02:3d:20:01:00
VEM Control Agent (DPA) MAC: 00:02:3d:40:01:00
VEM SPAN MAC: 00:02:3d:30:01:00
Primary VSM MAC : 00:50:56:ac:00:42
Primary VSM PKT MAC : 00:50:56:ac:00:44
Primary VSM MGMT MAC : 00:50:56:ac:00:43
Standby VSM CTRL MAC : ff:ff:ff:ff:ff:ff
Management IPv4 address: 10.1.240.30
Management IPv6 address: 0000:0000:0000:0000:0000:0000:0000:0000
Secondary VSM MAC : 00:00:00:00:00:00
Secondary L3 Control IPv4 address: 0.0.0.0
Upgrade : Default
Max physical ports: 32
Max virtual ports: 216
Card control VLAN: 111
Card packet VLAN: 112
Card Headless Mode : Yes
       Processors: 8
Processor Cores: 4
Processor Sockets: 1
Kernel Memory:   16712336
Port link-up delay: 5s
Global UUFB: DISABLED
Heartbeat Set: False
PC LB Algo: source-mac
Datapath portset event in progress : no
~ #
On VSM
VSM11# sh svs conn
connection vcenter:
   ip address: 10.1.240.38
   remote port: 80
   protocol: vmware-vim https
   certificate: default
   datacenter name: New Datacenter
   admin:
   max-ports: 8192
   DVS uuid: c4 be 2c 50 36 c5 71 97-44 41 1f c0 43 8e 45 78
   config status: Enabled
   operational status: Connected
   sync status: Complete
   version: VMware vCenter Server 4.1.0 build-345043
VSM11# sh svs ?
connections Show connection information
domain       Domain Configuration
neighbors   Svs neighbors information
upgrade     Svs upgrade information
VSM11# sh svs dom
SVS domain config:
Domain id:   1
Control vlan: 111
Packet vlan: 112
L2/L3 Control mode: L2
L3 control interface: NA
Status: Config push to VC successful.
VSM11# sh port
           ^
% Invalid command at '^' marker.
VSM11# sh run
!Command: show running-config
!Time: Sun Nov 20 11:35:52 2011
version 4.2(1)SV1(4a)
feature telnet
username admin password 5 $1$QhO77JvX$A8ykNUSxMRgqZ0DUUIn381 role network-admin
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip domain-lookup
hostname VSM11
snmp-server user admin network-admin auth md5 0x389a68db6dcbd7f7887542ea6f8effa1
priv 0x389a68db6dcbd7f7887542ea6f8effa1 localizedkey
vrf context management
ip route 0.0.0.0/0 10.1.240.254
vlan 1,111-112
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile type ethernet Unused_Or_Quarantine_Uplink
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type ethernet system-uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 111-112
no shutdown
system vlan 111-112
description "System profile"
state enabled
port-profile type vethernet servers11
vmware port-group
switchport mode access
switchport access vlan 11
no shutdown
description "Data Profile for VM Traffic"
port-profile type ethernet vm-uplink
vmware port-group
switchport mode access
switchport access vlan 11
no shutdown
description "Uplink profile for VM traffic"
state enabled
vdc VSM11 id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 32 maximum 32
limit-resource u6route-mem minimum 16 maximum 16
limit-resource m4route-mem minimum 58 maximum 58
limit-resource m6route-mem minimum 8 maximum 8
interface mgmt0
ip address 10.1.240.124/24
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-1
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-2
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-2
svs-domain
domain id 1
control vlan 111
packet vlan 112
svs mode L2
svs connection vcenter
protocol vmware-vim
remote ip address 10.1.240.38 port 80
vmware dvs uuid "c4 be 2c 50 36 c5 71 97-44 41 1f c0 43 8e 45 78" datacenter-n
ame New Datacenter
max-ports 8192
connect
vsn type vsg global
tcp state-checks
vnm-policy-agent
registration-ip 0.0.0.0
shared-secret **********
log-level
thank you
Michel

Loop prevention in Nexus 1000V

Hello
I am wondering if there is a mechanism that I can use to secure a network against the L2 loop crated on the vserver side, in the Vmware environment with Nexus 1000V.
I know, that Nexus 1000V can prevent against the loop on the external links but, there is no information that there are any features that can prevent against the loop caused by the bridge configured on the OS side on the VMware's virtual server.
Thank you in advance for an answer.
Regards
Lukas

Hello Lukas,
To prevent loops, N1KV does not switch traffic between physical NICs and also, it silently drops the traffic between vNICs that are the bridged by OS.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/guide_c07-556626.html#wp9000156
We do not need explicit configuration on N1KV.
Padma

DCNM - Nexus 1000v compatibility

Is DCNM v5.2(2a) compatible with Nexus 1000v v4.2(1)SV1(4a)?
We are getting an SNMP OID error when we try.
The compatibility matrix (http://www.cisco.com/en/US/partner/docs/switches/datacenter/sw/5_x/dcnm/matrix/matrix.html) is unclear.

Hello Grant.
4.2(1) is the NX-OS version for N1k. The matrix indicates all SV1(4) versions are supported
SV14# sh version | inc system
system: version 4.2(1)SV1(4a)
Please let us know the exact SNMP OID error. You may want to debug snmp errors on the N1k side when attempting to add the N1k.

Trunking Vlans in Nexus 1000V

I am looking to design a solution for a customer and they run a very tight hosting environment with Nexus 1000V switches and want to setup private vlans as they are running out of vlans
I need to find some info on if it is possible to trunk a private vlan between 2 nexus switches
Or any info on private vlans on Nexus 1000V
Thanks
Roger

Hello Roger,
Yes, pVLANs can be trunked between switches. A good discussion can be found here. Have you considered VXLAN as an alternative to pVLANs? VXLAN allows up to 16M segments definied though they differ slightly from pVLAN in that all VMs in a VXLAN segment can communicate.
Matthew

Can a Nexus 1000v be configured to NOT do local switching in an ESX host?

Before the big YES, use an external Nexus switch and use VN-Tag. The question is when there is a 3120 in a blade chassis that connects to the ESX hosts that have a 1000v installed on the ESX host. So, first hop outside the ESX host is not a Nexus box.
Looking for if this is possible, if so how, and if not, where that might be documented. I have a client who's security policy prohibits switching (yes, even on the same VLAN) within a host (in this case blade server). Oh and there is an insistance to use 3120s inside the blade chassis.
Has to be the strangest request I have had in a while.
Any data would be GREATY appreciated!

Thanks for the follow up.
So by private VLANs, are you referring to "PVLAN":
"PVLANs: PVLANs are a new feature available with the VMware vDS and the Cisco Nexus
1000V Series. PVLANs provide a simple mechanism for isolating virtual machines in the
same VLAN from each other. The VMware vDS implements PVLAN enforcement at the
destination host. The Cisco Nexus 1000V Series supports a highly efficient enforcement
mechanism that filters packets at the source rather than at the destination, helping ensure
that no unwanted traffic traverses the physical network and so increasing the network
bandwidth available to other virtual machines"

Nexus 1000V. problem when working with the console VMWare

I have a problem when working with the console VMWare.
Sometimes it is impossible to connect any of the hypervisor to the guest OS managed by them.
I get the message: "Unable connect to the MKS: Host address lookup for server <name of the hypervisor> failed: No such host is known."
This message always appears in conjunction with the reconfiguration of virtual switch: "Reconfigure vNetwork Distributed Switch .... Initiated by Cisco_Nexus_1000V_ ....."
Upon completion of the reconfiguration, Communication console, with guest OS is restored, or on its own or after a reboot srv-vc.
In this time, I do not see any message in Nexus 1000v log.
What is this?
Thanks in advance.

Smells of a DNS issue. Are you sure your ESX hosts are reachable from your client via DNS hostname? Try pinging them from a command prompt/terminal. You may have DNS server issues.
As a temp fix, edit your [windowspath]/system32/etc/drivers/hosts file and manually add the ESX host name and IP, then re-test.
Regards,
Robert

Nexus 1000v integeration with SCVMM

Hi fellows,
Can some one please guide to a good step by step document on integeration of Nexus 1000v (appliance) with SCVMM, and Windows hypervisor?

Hello,
It is not officially released and work is still in progress.
You can find links to demo of current pre-release software here
http://blogs.cisco.com/datacenter/nexus-1000v-provides-cloud-switching-to-new-windows-server-2012-platform/
Padma

Nexus 1000v VSM can't comunicate with the VEM

This is the configuration I have on my vsm
!Command: show running-config
!Time: Thu Dec 20 02:15:30 2012
version 4.2(1)SV2(1.1)
svs switch edition essential
no feature telnet
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip host Nexus-1000v 172.16.0.69
hostname Nexus-1000v
errdisable recovery cause failed-port-state
vem 3
host vmware id 78201fe5-cc43-e211-0000-00000000000c
vem 4
host vmware id e51f2078-43cc-11e2-0000-000000000009
priv 0xa2cb98ffa3f2bc53380d54d63b6752db localizedkey
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1-2
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile type ethernet Unused_Or_Quarantine_Uplink
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type ethernet vmware-uplinks
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1-3967,4048-4093
channel-group auto mode on
no shutdown
system vlan 2
state enabled
port-profile type vethernet Management
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet vMotion
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet ServidoresGestion
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet L3-VSM
capability l3control
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
system vlan 2
state enabled
port-profile type vethernet VSG-Data
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet VSG-HA
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
vdc Nexus-1000v id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 1 maximum 1
limit-resource u6route-mem minimum 1 maximum 1
interface mgmt0
ip address 172.16.0.69/25
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1.bin sup-1
boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1.bin sup-2
boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1.bin sup-2
svs-domain
domain id 1
control vlan 1
packet vlan 1
svs mode L3 interface mgmt0
svs connection vcenter
protocol vmware-vim
remote ip address 172.16.0.66 port 80
vmware dvs uuid "ae 31 14 50 cf b2 e7 3a-5c 48 65 0f 01 9b b5 b1" datacenter-n
ame DTIC Datacenter
admin user n1kUser
max-ports 8192
connect
vservice global type vsg
tcp state-checks invalid-ack
tcp state-checks seq-past-window
no tcp state-checks window-variation
no bypass asa-traffic
vnm-policy-agent
registration-ip 172.16.0.70
shared-secret **********
policy-agent-image bootflash:/vnmc-vsmpa.2.0.0.38.bin
log-level
for some reason my vsm can't the the vem. I could before, but then my server crashed without doing a copy run start and when it booted up all my config but the uplinks was lost.
When I tried to configure the connection again it wasn't working.
I'm also attaching a screen capture of the vds
and a capture of the regular switch.
I will appreciate very much any help you could give me and will provide any configuration details that you might need.
Thank you so much.

Carlos,
Looking at vds.jpg, you do not have any VEM vmkernel interface attached to port-profile L3-VSM. So fix VSM-VEM communication problem, you either migrate your VEM management vmkernel interface to L3-VSM port-profile of the vds, or create new VMkernel port on your VEM/host and attach it to L3-VSM port-profile.

Prime Infrastructure 2.x tacacs+ with radiator

Trying to setup Prime Infrastructure 2.x (2.2) to use Tacacs+. The Tacacs service is running on a Linux server running Radiator(4.12). With Radius and Radiator all we needed to do is define the user group and all the tasks associated with that group were inherited.
When configuring the TACACs configuration files have tried various permutations of adding the cisco-avpair(cisco-av-pair) reply attrs on authentication and/or authorization. When defining the group or using the individual tasks I get the following error message:
"no authorization information found for remote authenttication user. please check the correctness of the associated task(s) and Virtual Domain(s) in the remote server"
<ServerTACACSPLUS>
Key SECRET
Port 49
GroupMemberAttr OSC-Authorize-Group
# General Authorization rule format:
AuthorizeGroup core-group permit protocol=HTTP service=NCS {cisco-av-pair="virtual-domain0=ROOT-DOMAIN" cisco-av-pair="role0=Super Users" }
</ServerTACACSPLUS>

It's not yet supported. Cisco doesn't generally publish roadmaps publicly for future support. The best you can do via public sources is to continue to watch the Supported Devices lists for updates.
As of right now, here is a list of the current data center switches supported (in PI 2.1):
Cisco Nexus 6004 Switch
Cisco Nexus 5596T Switch
Cisco Nexus 5010 Switch
Cisco Nexus 5020 Switch
Cisco Nexus 5020T Switch
Cisco Nexus 7000 10-Slot Switch
Cisco Nexus 7000 18-Slot Switch
Cisco Nexus 1000V Series Switches
Cisco Nexus 1010 Virtual Services Appliance
Cisco Nexus 4001I Switch Module for IBM BladeCenter
Cisco Nexus 4005I Switch Module for IBM BladeCenter
Cisco Nexus 5548P Switch
Cisco Nexus 5548UP Switch
Cisco Nexus 5596UP Switch
Cisco Nexus 3064 Switch
Cisco Nexus 3048 Switch
Cisco Nexus 3016 Switch
Cisco Nexus 7000 9-Slot Switch
Cisco Nexus 9500 Switch
Cisco Nexus 3548 Switch

Configuring Tacacs with Nexus 1000v

Similar Messages

Maybe you are looking for