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 contains the following sections:
In order to connect to vCenter Server or an ESX server, you must first define the connection in theCisco Nexus 1000V including the following:
InterCloud Extender will fail to attach as a module on the VSM if its tunnel interface and the VSM management are on the same subnet.
Before beginning this procedure, you must be logged in to the CLI in EXEC mode.
You must know the following:
You must be sure the following is set up:
switch# config t switch(config)# svs connection VC switch(config-svs-conn)# protocol vmware-vim switch(config-svs-conn)# remote ip address 192.168.0.1 switch(config-svs-conn)# vmware dvs datacenter-name Hamilton-DC switch(config-svs-conn)# connect switch# 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 switch#
This section includes the following topics:
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 the universally unique identifier (UUID) of a host server. This mapping is used to assign the same module number to a given host server.
Before beginning this procedure, be sure you have done the following:
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | switch# configure terminal | Places you in global configuration mode. |
||
Step 2 | switch(config)# no vem module-number | Removes the specified module from software.
|
||
Step 3 | switch(config)# show module vem mapping | (Optional) Displays the mapping of modules to host servers. |
||
Step 4 | switch(config)# copy running-config startup-config | Copies the running configuration to the startup configuration. |
switch# configure terminal switch(config)# no vem 4 switch(config)# no vem 3 cannot modify slot 3: host module is inserted switch(config)# show module vem mapping Mod Status UUID License Status --- ----------- ------------------------------------ -------------- 3 powered-up 93312881-309e-11db-afa1-0015170f51a8 licensed switch(config-vem-slot)# copy running-config startup-config
Before beginning this procedure, be sure you have done the following:
Note |
If you do not first remove the existing host server mapping, the new host server is assigned a different module number. |
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Places you in global configuration mode. |
Step 2 | switch(config)# vem module number | Places you in VEM slot configuration mode. |
Step 3 | switch(config-vem-slot)# host vmware id server-bios-uuid | Assigns a different host server UUID to the specified module. |
Step 4 | switch(config-vem-slot)# show module vem mapping | (Optional) Displays the mapping of modules to host servers. |
Step 5 | switch(config-vem-slot)# copy running-config startup-config | Copies the running configuration to the startup configuration. |
switch# config t switch(config)# vem 3 switch(config-vem-slot)# host vmware id 6dd6c3e3-7379-11db-abcd-000bab086eb6 switch(config-vem-slot)# show module vem mapping Mod Status UUID License Status --- ----------- ------------------------------------ -------------- 3 powered-up 93312881-309e-11db-afa1-0015170f51a8 licensed 4 absent 6dd6c3e3-7379-11db-abcd-000bab086eb6 licensed switch(config-vem-slot)# copy running-config startup-config
|
Mod Status UUID License Status --- ----------- ------------------------------------ -------------- 3 powered-up 93312881-309e-11db-afa1-0015170f51a8 licensed n1000v(config)#
Use the following command to verify the configured domain:
Command |
Description |
---|---|
show svs domain |
Displays the domain configured on the Cisco Nexus 1000V. |
n1000v# show svs domain SVS domain config: Domain id: 98 Control vlan: 70 Packet vlan: 71 Sync state: - n1000v#
Use one of the following commands to verify the configuration:
Command |
Description |
---|---|
show running-config |
Displays the current configuration. If the Cisco Nexus 1000V is not connected to a vCenter Server or ESX server, the output is limited to connection-related information. |
show svs domain |
Displays the domain configured on the Cisco Nexus 1000V. |
show module |
Displays module information. |
show server_info |
Displays server information. |
show interface brief |
Displays interface information, including the uplinks to vCenter Server. |
show interface virtual |
Displays virtual interface information. |
show module vem mapping |
Displays the mapping of modules to host servers. |
Use one of the following commands to verify the configuration:
Command |
Description |
---|---|
show module |
Displays module information. |
show server_info [name] |
Displays server information. |
show interface brief |
Displays interface information, including the uplinks to vCenter Server. |
show interface virtual |
Displays virtual interface information. |
Feature Name |
Releases |
Feature Information |
---|---|---|
Server Connections |
Release 5.2(1)IC1(1.1) |
This feature was introduced. |