The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to create a connection and connect to a server, how to disconnect from a server, and how to view server connections.
This chapter includes the following topics:
•Information About Server Connections
•Connecting to the vCenter Server
•Disconnecting From the vCenter Server
In order to connect to vCenter Server or an ESX server, you must first define the connetion in the Cisco Nexus 1000V including the following:
•A connection name
•The protocol used
•The server IP address
•The server DNS name
•The datacenter name
All communication with vCenter Server is secured by the TLS protocol.
Use this procedure to configure a connection and then connect to vCenter server or an ESX server.
•You are logged in to the CLI in EXEC mode.
•You know the datacenter name.
•The vCenter Server management station is installed and running.
•You know the vCenter Server IP address or hostname.
•The ESX servers are installed and running.
•The management port is configured.
•The vCenter Server is reachable from the Cisco Nexus 1000V.
•The Cisco Nexus 1000V appliance is installed.
•If you are configuring a connection using a hostname, DNS is already configured.
•You have already registered an extension with the vCenter Server. The extension includes the extension key and public certificate for the VSM. vCenter Server uses these to verify the authenticity of the request it receives from the VSM. For instructions about adding and registering an extension, see the Cisco Nexus 1000V Software Installation Guide, Release 4.0(4)SV1(1).
1. config t
2. svs connection name
3. protocol vmware-vim
4. remote {ip address address A.B.C.D | hostname name}
5. vmware dvs datacenter-name name
6. connect
|
|
|
---|---|---|
Step 1 |
config t Example: n1000v# config t n1000v(config)# |
Places you into CLI Global Configuration mode. |
Step 1 |
svs connection name Example: n1000v (config#) svs connection VC n1000v(config-svs-conn#) |
Places you into Connection Configuration mode for adding this connection between Cisco Nexus 1000V and either a particular ESX server or the vCenter Server. By using a name, information for multiple connections can be stored in the configuration. |
Step 2 |
protocol vmware-vim [http] Example: n1000v(config-svs-conn#) protocol vmware-vim n1000v(config-svs-conn#) |
Specifies that this connection uses the VIM protocol. This command is stored locally. •http: Specifies that the VIM protocol runs over HTTP. The default is to use HTTP over SSL (HTTPS). |
Step 3 |
Do one of the following: •If you are configuring an IP address, go to Step 4. •If you are configuring a hostname, go to Step 5. |
|
Step 4 |
remote ip address ipaddress Example: n1000v(config-svs-conn#) remote ip address 192.168.0.1 n1000v(config-svs-conn#) Go to Step 6. |
Specifies the IP address of the ESX server or vCenter Server for this connection. This command is stored locally. |
Step 5 |
remote hostname hostname Example: n1000v(config-svs-conn#) remote hostname vcMain n1000v(config-svs-conn#) |
Specifies the DNS name of the ESX server or vCenter Server for this connection. This command is stored locally. Note DNS is already configured. |
Step 6 |
vmware dvs datacenter-name name Example: n1000v(config-svs-conn#) vmware dvs datacenter-name Hamilton-DC n1000v(config-svs-conn#) |
Identifies the datacenter name in the vCenter Server where Cisco Nexus 1000V is to be created as a distributed virtual switch (DVS). You can use this command before or after connecting. The datacenter name is stored locally. |
Step 7 |
connect Example: n1000v(config-svs-conn#) connect |
Initiates the connection. If the username and password have not been configured for this connection, the user is prompted for a username and password. The default is no connect. There can be only one active connection at a time. If a previously-defined connection is up, an error message displays and the command is rejected until the user closes the previous connection by entering no connect. |
Example:
n1000v# config t
n1000v (config)# svs connection VC
n1000v(config-svs-conn#) protocol vmware-vim
n1000v(config-svs-conn#) remote ip address 192.168.0.1
n1000v(config-svs-conn#) vmware dvs datacenter-name Hamilton-DC
n1000v(config-svs-conn#) connect
n1000v# show svs connections
connection VC:
ip address: 192.168.0.1
protocol: vmware-vim https
certificate: default
datacenter name: Hamilton-DC
DVS uuid: ac 36 07 50 42 88 e9 ab-03 fe 4f dd d1 30 cc 5c
config status: Enabled
operational status: Connected
n1000v#
Use this procedure to disconnect from the vCenter Server, for example, after correcting a vCenter Server configuration
•You are logged in to the Cisco Nexus 1000V in EXEC mode.
•You have configured an Cisco Nexus 1000V connection using the "Connecting to the vCenter Server" procedure.
•The Cisco Nexus 1000V is connected to vCenter Server/ESX.
Use this procedure to remove the DVS from the vCenter Server.
•You are logged in to the CLI in EXEC mode.
•You have configured a connection using the "Connecting to the vCenter Server" procedure.
•The Cisco Nexus 1000V is connected to vCenter Server/ESX.
•The Server Administrator has already removed from the VI client all of the hosts connected to Cisco Nexus 1000V. For more information, see the VMware documentation.
This section includes the following topics:
•Information about Host Mapping
•Removing Host Mapping from a Module
When a VSM detects a new VEM, it automatically assigns a free module number to the VEM and then maintains the mapping between the module number and UUID of a host server. This mapping is used to assign the same module number to a given host server.
Use this procedure to remove the mapping of a module to a host server.
•You are logged in to the CLI in EXEC mode.
•You have already removed the host from the Cisco Nexus 1000V DVS on vCenter.
1. config t
2. no vem module-number
3. show module vem mapping
4. copy running-config startup-config
Use this procedure to map a module number to a different host server UUID.
•You are logged in to the CLI in EXEC mode.
•You have already removed the host from the Cisco Nexus 1000V DVS on vCenter using the "Removing Host Mapping from a Module" procedure.
Note If you don't first remove the existing host server mapping, the new host server is assigned a different module number.
1. config t
2. vem module number
3. host vmware id server-bios-uuid
4. show module vem mapping
5. copy running-config startup-config
Use this procedure in EXEC mode to view the mapping of modules to host servers.
Step 1 show module vem mapping
Example:
n1000v(config)# show module vem mapping
Mod Status UUID License Status
--- ----------- ------------------------------------ --------------
3 powered-up 93312881-309e-11db-afa1-0015170f51a8 licensed
n1000v(config)#
Use this procedure to view connections.
•You are logged in to the CLI in any command mode.
•You have configured the connection using the "Connecting to the vCenter Server" procedure.
•The Cisco Nexus 1000V is connected to vCenter Server/ESX.
Use this procedure to view the configured domain.
•You are logged in to the CLI in any command mode.
•You have configured a domain using the "Creating the Domain" procedure on page 3-1.
Use this procedure to display the running configuration.
•You are logged in to the CLI in any command mode.
•You have configured Cisco Nexus 1000V connections using the "Connecting to the vCenter Server" procedure.
•The Cisco Nexus 1000V is connected to vCenter Server/ESX.
Example:
n1000v(config-acl)# show running-config
version 4.0(1)
feature port-security
username adminbackup password 5 $1$Oip/C5Ci$oOdx7oJSlBCFpNRmQK4na. role network-operator
username admin password 5 $1$N1mX5tLD$daXpuxlAPcIHoz53PBhy6/ role network-admin
telnet server enable
ssh key rsa 1024 force
kernel core target 0.0.0.0
kernel core limit 1
system default switchport
ip access-list my66
10 permit ip 1.1.1.1/32 1.1.1.2/32
snmp-server user admin network-admin auth md5 0x90f3798f3e894496a11ec42ce2efec9c priv 0x90f3798f3e894496a11ec42ce2efec9c localizedkey
snmp-server enable traps entity fru
snmp-server enable traps license
vrf context management
ip route 0.0.0.0/0 172.28.15.1
switchname srini-cp
vlan 40-43,45-48
vdc srini-cp id 1
limit-resource vlan minimum 16 maximum 4094
limit-resource monitor-session minimum 0 maximum 32
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 192
limit-resource u4route-mem minimum 32 maximum 256
limit-resource u6route-mem minimum 16 maximum 256
interface Ethernet6/2
inherit port-profile uplinkportprofile1
interface Ethernet6/3
inherit port-profile uplinkportprofile2
interface Ethernet6/4
inherit port-profile uplinportprofile3
interface Ethernet7/2
inherit port-profile uplinkportprofile1
interface mgmt0
ip address 172.28.15.163/24
interface Vethernet1
inherit port-profile vm100
interface Vethernet2
inherit port-profile vm100
interface Vethernet3
inherit port-profile vm100
interface Vethernet4
inherit port-profile vm100
interface Vethernet5
interface Vethernet6
boot kickstart bootflash:/svs-kickstart-mzg.4.0.1a.S1.0.82.bin sup-1
boot system bootflash:/svs-mzg.4.0.1a.S1.0.82.bin sup-1
boot system bootflash:/isan.bin sup-1
boot kickstart bootflash:/svs-kickstart-mzg.4.0.1a.S1.0.82.bin sup-2
boot system bootflash:/svs-mzg.4.0.1a.S1.0.82.bin sup-2
boot system bootflash:/isan.bin sup-2
ip route 0.0.0.0/0 172.28.15.1
port-profile uplinkportprofile1
capability uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1,40-43
no shutdown
system vlan 1,40-43
state enabled
port-profile vm100
vmware port-group
switchport mode access
switchport access vlan 43
ip port access-group my100 out
ip port access-group my66 in
no shutdown
state enabled
port-profile uplinkportprofile2
capability uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 45-46
no shutdown
state enabled
port-profile uplinportprofile3
capability uplink
vmware port-group
switchport trunk allowed vlan 47-48
state enabled
port-profile uplinkportprofile3
no shutdown
svs-domain
domain id 163
control vlan 41
packet vlan 42
svs connection VCR5
protocol vmware-vim
remote ip address 172.28.30.83
vmware dvs datacenter-name cisco-DC
connect
n1000v(config-acl)#
Use this procedure to display module information, including a view of the DVS from Cisco Nexus 1000V.
•You are logged in to the CLI in any command mode.
•You have configured the Cisco Nexus 1000V connection using the "Connecting to the vCenter Server" procedure.
•The Cisco Nexus 1000V is connected to vCenter Server/ESX.
•The Server Administrator has already added the host running Cisco Nexus 1000V to the DVS in vCenter Server.
1. show module
2. show server-info
3. show interface brief
4. show interface virtual
Example
n1000v# show module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 1 Virtual Supervisor Module Nexus1000V active *
2 48 Virtual Ethernet Module ok
3 48 Virtual Ethernet Module ok
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
1 4.0(0)S1(0.82) 0.0 --
2 NA 0.0 --
3 NA 0.0 --
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
2 02-00-0c-00-02-00 to 02-00-0c-00-02-80 NA
3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
1 172.18.217.180 esx-1
2 172.18.117.44 487701ee-6e87-c9e8-fb62-001a64d20a20 esx-2
3 172.18.217.3 4876efdd-b563-9873-8b39-001a64644a24 esx-3
* this terminal session
Example
n1000v# show server_info
Mod Status UUID
--- ----------- ----
2 powered-up 34303734-3239-5347-4838-323130344654
3 absent 371e5916-8505-3833-a02b-74a4122fc476
4 powered-up 4880a7a7-7b51-dd96-5561-001e4f3a22f9
5 absent 48840e85-e6f9-e298-85fc-001e4f3a2326
6 powered-up eb084ba6-3b35-3031-a6fe-255506d10cd0
n1000v#
Example
n1000v# show interface brief
--------------------------------------------------------------------------------
Port VRF Status IP Address Speed MTU
--------------------------------------------------------------------------------
mgmt0 -- up 172.28.15.211 1000 1500
--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth2/2 1 eth trunk up none a-1000(D) --
--------------------------------------------------------------------------------
Interface VLAN Type Mode Status Reason MTU
--------------------------------------------------------------------------------
Example
n1000v# show interface virtual
--------------------------------------------------------------------------------
Port Adapter Owner Mod Host
--------------------------------------------------------------------------------
Veth49 R-VM-1 2 mcs-srvr35
This section provides the server connections feature release history.
|
|
|
---|---|---|
Server Connections |
4.0(4)SV1(1) |
This feature was introduced. |