•If you are configuring Layer 3 control, see the Domain Configuration section in the Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3), and then continue with the next step.

•If you are not configuring Layer 3 control, continue with the next step.

Note The software provides licenses for 16 CPU sockets for a period of 60 days. These licenses are used only if there are no permanent licenses installed on the VSM. The evaluation period of 60 days starts when you install the software.

If you have purchased licenses, see the Cisco Nexus 1000V License Configuration Guide, Release 4.0(4)SV1(3).

Step 17 When asked to enable the SSH service, answer yes and then enter the key type and number of key bits.For more information, see the document,Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(3).

Example:

Enable the ssh service? (yes/no) [y]: yes
Type of ssh key you would like to generate (dsa/rsa) : rsa
Number of key bits <768-2048> : 1024

Step 18 When asked to configure the NTP server, answer no.

Example:

Configure NTP server? (yes/no) [n]: no

Step 19 When asked to configure the VEM feature level, answer yes and then enter 0 or 1.

Example:

Configure vem feature level? (yes/no) [n]: yes

Current vem feature level is set to 4.0.(4)SV1(1)
You can change the feature level to:

1 4.0(4)SV1(2)

Enter an index from the list above <1-1> or 0 if you don't want to change:

The system now summarizes the complete configuration and asks if you want to edit it.

Example:

The following configuration will be applied:

Switchname n1000v

interface Mgmt0

ip address 172.28.15.152 255.255.255.0

no shutdown

telnet server enable

ssh key rsa 1024 force

ssh server enable

svs-domain

control vlan 260

packet vlan 260

domain id 152

Step 21 Do one of the following:

•If you do not want to edit the configuration answer no and continue with the next step.

•If you want to edit the configuration, answer yes and return to Step 9 to revisit each command.

Example:

Would you like to edit the configuration? (yes/no) [n]:no

Step 22 When asked to use and save this configuration, answer yes.

Caution If you do not save the configuration now, then none of your changes are part of the configuration the next time the switch is rebooted. Enter
yes to save the new configuration. This ensures that the kickstart and system images are also automatically configured.

Example:

Use this configuration and save it? (yes/no) [y]: yes

[########################################] 100%

The new configuration is saved into nonvolatile storage, after which the running and the startup copies of the configuration are identical.

Note You can use the setup routine to update the configuration done in Step 8 through Step 22 at any time by entering the setup command in EXEC mode. Once setup begins, press Enter to skip a command. Use ctrl-c to skip the remaining commands.

Creating a Cisco Nexus 1000V Plug-In on the vCenter Server

Use the following guidelines and your VMware documentation to install and register the Cisco Nexus 1000V plug-in (extension) on the vCenter Server.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

•You have already downloaded a copy of the following file from the VSM home page (point your browser to the IP address of the active VSM):

–cisco_nexus1000v_extension.xml

•Using an old or corrupt version of the cisco_nexus1000v_extension.xml file could result in an error message.

Note To avoid downloading an obsolete cached copy of the file, make sure to first refresh your browser window.

•You know the IP address of the active VSM.

•A plug-in must be added to the vCenter Server for every VSM connecting to it.

If you have dual supervisors, both use the same plug-in.

Note If you see the error, "The specified parameter was not correct," then you have tried to register a plugin that is already registered. See the Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3).

DETAILED STEPS

Step 1 Open the vSphere Client.

The local host—VMware Infrastructure Client dialog box opens.

Step 2 From the Plug-Ins menu, choose Manage Plug-Ins.

The Plug-In Manager dialog box opens.

Step 3 Right-click the white space within the dialog box, and choose New Plug-In from the popup menu.

The Register Plug-In dialog box opens.

Step 4 Click Browse and choose the cisco_nexus1000v_extension.xml file that you downloaded from the VSM home page.

Step 5 Click Register Plug-In.

Note If you see the error, "The specified parameter was not correct," then you have tried to register a plugin that is already registered. See the Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3).

Step 6 In the Security Warning dialog box, click Ignore to continue using the certificate.

Step 7 In the Register Plug-in dialog box, click OK.

The plug-in is created and registered.

Step 8 Verify that the extension now shows up in the Plug-in Manager window.

Connecting to the vCenter Server

You can use this procedure to configure the connection between the VSM and the vCenter Server and then save the configuration in persistent memory across reboots and restarts.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

•You are logged in to the standalone or active VSM in EXEC mode.

•The extension for the Cisco Nexus 1000V is already registered as a plug-in on the vCenter Server.

•You know the datacenter name, which is case-sensitive.

•The datacenter already exists on the vCenter Server.

•You know the IP address of the vCenter Server.

SUMMARY STEPS

1. config t

2. svs connection connection_name

3. vmware dvs datacenter-name dc_name

4. protocol vmware-vim

5. remote ip addressip_address

6. connect

7. show svs connections

8. copy running-config startup-config

DETAILED STEPS

Command

Description

Step 1

config t

Example:

n1000v# config t

n1000v(config)#

Enters global configuration mode.

Step 2

svs connection name

Example:

n1000v (config#) svs connection VC

n1000v(config-svs-conn#)

Enters connection configuration mode for adding this connection between Cisco Nexus 1000V and the vCenter Server. By using a name, information for multiple connections can be stored in the configuration.

Step 3

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 4

remote ip address ipaddress

Example:

n1000v(config-svs-conn#) remote ip address 172.28.15.150

n1000v(config-svs-conn#)

Specifies the IP address of the ESX server or vCenter Server for this connection. This command is stored locally.

Step 5

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 6

connect

Example:

n1000v(config-svs-conn#) connect

Initiates the connection.

Note It may take up to 10 seconds to connect the first time.

If the username and password have not been configured for this connection, the user is prompted for a username and password.

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 you close the previous connection using the no connect command.

Note If the connection is not initiated, see the Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3).

Step 7

show svs connections [name]

Example:

n1000v(config-svs-conn#) show svs connections vc

connection VC:

hostname: 172.28.15.150

protocol: vmware-vim https

certificate: default

datacenter name: HamiltonDC

DVS uuid: 6d fd 37 50 37 45 05 64-b9 a4 90 4e 66
eb 8c f5

config status: Enabled

operational status: Connected

n1000v(config-svs-conn#)

Displays the current connections to the Cisco Nexus 1000V for verification.

A Cisco Nexus 1000V DVS is created on vCenter Server and is visible through vSphere Client under Inventory > Networking.

Note If your connection to the vCenter Server is shut down unexpectedly, the Cisco Nexus 1000V does not automatically restore it. In this case, you must restore the connection manually using the following command sequence,

no connectconnect

Step 8

copy running-config startup-config

Example:

n1000v(config-svs-conn#) copy running-config startup-config

[########################################] 100%

n1000v(config-port-prof)#

The connection to the vCenter Server is setup and copied from the running configuration to the startup configuration where it is saved persistently through reboots and restarts.

Caution If you do not copy this configuration to the startup configuration, then in the event of a VSM reboot, this connection configuration is discarded.

Caution You must store the port profiles in the Cisco Nexus 1000V startup configuration so that they are saved in the event of a restart or reboot. Otherwise, in the event of a VSM reboot, port groups continue to exist on the vCenter Server but not on the VSM.

Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created using the following characteristics:

•name—The port profile name can be up to 80 characters and must be unique for each port profile on the Cisco Nexus 1000V.

•type—(Optional) The port profile type can be Ethernet or vEthernet. Once configured, the type cannot be changed. The default is the vEthernet type.

Defining a port profile type as Ethernet allows the port profile to be used for physical (Ethernet) ports. In the vCenter Server, the corresponding port group can be selected and assigned to physical ports (PNICs).

Note If a port profile is configured as an Ethernet type, then it cannot be used to configure VMware virtual ports.

•You don't need to configure the system port profile on the secondary VSM. Once this configuration is made, the primary VSM automatically synchronizes with the secondary VSM.

•You can save the commands used here in a file, copy it to bootflash, and run it as a script. For more information about using scripts, see the Cisco Nexus 1000V Getting Started Guide, Release 4.0(4)SV1(3).

•The port profile name you designate in this procedure is your choice.

•If you want to use the system-uplink port profile to carry your data traffic, then add the data VLAN to the system-uplink port profile and make the corresponding changes on the upstream switch.

BEFORE YOU BEGIN

•Cisco recommends that you use the same VLAN for control, packet, and management, but that you do not place data traffic on this VLAN. For flexibility, you can configure separate VLANs.

•You are logged in to the standalone or active VSM in EXEC mode.

•You don't need to configure the data port profile on the secondary VSM. Once this configuration is made in the primary VSM, it automatically synchronizes with the secondary VSM.

•You can save the commands used here in a file, copy it to bootflash, and run it as a script. For more information about using scripts, see the Cisco Nexus 1000V Getting Started Guide, Release 4.0(4)SV1(3).

•The port profile name you designate in this procedure is your choice.

Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created using the following characteristics:

•name—The port profile name can be up to 80 characters and must be unique for each port profile on the Cisco Nexus 1000V.

•type—(Optional) The port profile type can be Ethernet or vEthernet. Once configured, the type cannot be changed. The default is the vEthernet type.

Defining a port profile type as Ethernet allows the port profile to be used for physical (Ethernet) ports. In the vCenter Server, the corresponding port group can be selected and assigned to physical ports (PNICs).

Note If a port profile is configured as an Ethernet type, then it cannot be used to configure VMware virtual ports.

Step 3

descriptionprofiledescription

Example:

n1000v(config-port-prof)# description "Data profile for VM Traffic"

n1000v(config-port-prof)#

Adds a description of up to 80 ASCII characters to the port profile. This description is automatically pushed to the vCenter Server.

Step 4

switchport mode access

Example:

n1000v(config-port-prof)# switchport mode access

n1000v(config-port-prof)#

Designates that the new port profile is used as an access port,

Step 5

switchport access vlanvlan_ID

Example:

n1000v(config-port-prof)# switchport access vlan 20

Specifies the access VLAN for the new port profile.

Step 6

no shutdown

Example:

n1000v(config-port-prof)# no shutdown

n1000v(config-port-prof)#

Administratively enables all ports in the new port profile.

Step 7

vmware port-group [portgroup_name]

Example:

n1000v(config-port-prof)# vmware port-group data20

n1000v(config-port-prof)#

Designates the port profile as a VMware port group.

The port profile is mapped to a VMware port group. When a vCenter Server connection is established, this port group is then distributed to the virtual switch on the vCenter Server.

Step 8

state enabled

Example:

n1000v(config-port-prof)# state enabled

n1000v(config-port-prof)#

Enables the new data port profile for VM traffic.

The configuration for ths new data port profile is applied to the assigned ports. The VMware port group is created in the vSwitch on the vCenter Server.

A Distributed Virtual Port Group is now visible under the VSM Name on the vSphere Client Inventory > Networking > DataCenter tab.

Step 9

show port-profile name profile-name

Example:

n1000v(config-port-prof)# show port-profile name data260

port-profile data20

description: "Data profile for VM traffic"

type: vethernet

status: enabled

capability l3control: no

pinning control-vlan: -

pinning packet-vlan: -

system vlans: none

port-group: data20

max ports: -

inherit:

config attributes:

switchport mode access

switchport access vlan 20

no shutdown

evaluated config attributes:

switchport mode access

switchport access vlan 20

no shutdown

assigned interfaces:

n1000v(config-port-prof)#

(Optional) Displays the port profile configuration that will be bound to the physical NIC for VM traffic.

Step 10

copy running-config startup-config

Example:

n1000v(config-port-prof)# copy running-config startup-config

[########################################]
100%

n1000v(config-port-prof)#

Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

Caution If you do not copy this configuration to the startup configuration, then in the event of a VSM reboot, this port group will continue to exist on the vCenter Server but not on the VSM

Adding an ESX 4.0 Host to the DVS

Use this procedure and your VMware documentation to add the host to the DVS.

Note If you are using VUM, then this procedure also installs the Cisco Nexus 1000V software onto the VEM automatically when the host is added to the switch.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

•The corresponding interface on the upstream switch must already be configured to allow the same VLANs as configured in the system-uplink port profile.

•In the example in this procedure, the traffic flow is set up as follows:

Traffic

VMNIC

Control VLAN

system-uplink VMNIC

Packet VLAN

system-uplink VMNIC

VM data

VM-uplink Port Group

Note If you use the system-uplink profile to carry data traffic and the system-uplink profile has already been defined, then you do not need to assign the vm-uplink profile to another vmnic.

•If you are not using VUM, you have already installed the VEM software on the host using the Cisco Nexus 1000V Virtual Ethernet Module Software Installation Guide, Release 4.0(4)SV1(3).

•If you are using VUM, this procedure triggers VUM to install the Cisco Nexus 1000V VEM package.

•If you are using VUM, you have already loaded VUM and created a database for patches on the vCenter Server using the VMware instructions.

Caution The automatic VEM software installation by VUM might fail with a proxy server enabled in VUM. This is due to a VMware limitation. The workaround is to disable the proxy during the software installation.

•The VMware Enterprise Plus license must already be installed on the host before the host can be added to the DVS. If not, then the host will not show up in the Add Host to Distributed Virtual Switch dialog box and you cannot add it.

•The VSM is already connected to the vCenter Server.

•To add multiple uplinks to the DVS and form a port channel with them, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(3).

DETAILED STEPS

Step 1 In the vSphere Client, click Inventory ‡ Networking.

You should see the following that you create when :

–A DVS with the switch name that you configured.

–The port profiles that you created.

Step 2 Do one of the following:

•If the DVS and the port profiles are present, continue with the next step.