Cisco Nexus 1000V Getting Started Guide, Release 4.0(4)SV1(3)
Configuring the Software Using the GUI
Downloads: This chapterpdf (PDF - 1.28MB) The complete bookPDF (PDF - 3.86MB) | Feedback

Configuring the Software Using the GUI

Table Of Contents

Configuring the Software Using the GUI

GUI Software Configuration Process

Guidelines and Limitations

Setting Up the VSM Virtual Machine Using the GUI

Configuring the VSM HA Role


Configuring the Software Using the GUI


This chapter describes how to use the GUI application to configure your new Cisco Nexus 1000V software, and includes the following sections.

GUI Software Configuration Process

Guidelines and Limitations

Setting Up the VSM Virtual Machine Using the GUI

Configuring the VSM HA Role

GUI Software Configuration Process

The following section will guide you through this process. After completing each procedure, return to this section to make sure you complete all required procedures in the correct sequence.


Step 1 Set up the VSM virtual machine using the "Setting Up the VSM Virtual Machine Using the GUI" procedure.

Step 2 Add the Cisco Nexus 1000V licenses.


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 3 Do one of the following:

If you are adding dual VSMs, continue with the next step.

If this VSM is a standalone VSM, its HA role has been automatically configured. Go to Step 5.

Step 4 Configure the HA role for this VSM using the "Configuring the VSM HA Role" procedure.

Step 5 You have completed this process. Return to the "Software Configuration Process" section on page 2-6 to continue setting up your VSM software.


Guidelines and Limitations

This configuration process has the following guidelines and limitations:

This configuration requires that you are using VUM.

The migration process only supports Layer 2.

To prevent disruptions in connectivity, any VMs residing on the host where the VSM vSwitch is added must be powered off.

To use the GUI for migration, any VMs residing on the host where the VSM vSwitch is added must be powered off.

This process moves all PNICs used by the VSM from the vSwitches to the Cisco Nexus 1000V DVS.

To prevent disruptions in connectivity, all port profiles are created with a system VLAN. You can change this after migration if needed.


Caution Host management connectivity may be interrupted if VMware kernel 0, vSwitch interface 0 are migrated and the native vlan is not correctly specified here.

To use the GUI for migration, the DVS created in part 1 of the app must create the SVS connection with the same datacenter where the VSM host resides.

Setting Up the VSM Virtual Machine Using the GUI

You can use this procedure to configure the VSM as follows:

Create port profiles for the following port groups:

Control

Management

Packet

Create uplink port profiles.

Create port profiles for VMware kernel NICs.

Create a VLAN to be used for system login and configuration, and control and packet traffic.


Note 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.


Enable SSH and configure an SSH connection.

Create a Cisco Nexus 1000V plug-in and register it on the vCenter server.

Migrate each VMware port group or kernel NIC to the correct port-profile.

Migrate each PNIC from the VMware vSwitch to the correct uplink on the DVS.

Add the host to the DVS.

Power off and then restart the VSM.

BEFORE YOU BEGIN

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

You have the following Cisco Nexus 1000V domain information:

Control VLAN ID

Packet VLAN ID

Domain ID

DETAILED STEPS


Step 1 In your browser address field, enter the VSM IP address.

The Cisco Nexus 1000V home page opens.

Step 2 Click Launch Application.

A security screen opens asking if you want to run this application.

Step 3 Click Run.

The Enter VSM Credentials screen opens.

The GUI shows a complete list of the setup steps in the left hand panel, and the configuration in progress in the right hand panel.

Step 4 Enter a password for the Adminisrator and then click Next.

The Enter vCenter Credentials screen opens.

Step 5 Enter the following vCenter credentials.

vCenter IP address

Secure HTTP port

Port 443 is configured by default, but you can change this if needed.

vCenter User ID (for a vCenter user with administrator-level privileges)

vCenter Password (for a vCenter user with administrator-level privileges)

Step 6 Click Next.

The VSM Host screen opens.

Step 7 Choose a host for the VSM and click Next.

The VSM VM and Port Groups screen opens.

Step 8 Choose your VSM from the selection list.

Step 9 Do one of the following:

Click Default to use the default configuration, click Next, and and then go to Step 11.

This configures one VLAN (the management VLAN) for use in the control, management, and packet port profiles. Go to Step 11.

Click Advanced to configure a VLAN for each port profile separately, and then continue with the next step.

Step 10 Choose your port groups from the selection lists, enter VLAN IDs, and then click Next.

Step 11 In the VSM Config Options screen, add the following for your VSM and then click Next.

Switch name

Administrator user name and password

Management IP address, subnet mask, and gateway IP address

The VSM VM must be run on the same IP subnet as the ESX 4.0 hosts that it manages.

Domain ID

Datacenter name

vSwitch native VLAN


Caution Host management connectivity may be interrupted if VMware kernel 0, vSwitch interface 0 are migrated and the native vlan is not correctly specified here.

Whether to enable telnet

Step 12 Review the configuration in the VSM Summary Screen,

.

Step 13 Do one of the following:

To make corrections, click Prev, go back to the previous screens, and make corrections.

If the configuration is accurate, continue with the next step.

Step 14 Click Next.

The configuration is applied to the VSM.

A summary screen displays the progress as the configuration completes on the VSM.

The completed VSM configuration is displayed and you are prompted to migrate the host and networks to the new DVS.

Step 15 Do one of the following:

Click Yes to have the host automatically migrated to the new DVS and continue with the next step.

Click No to continue without migrating the host to the DVS, then click Next and go to Step 20.

Step 16 Click Next.

A summary screen displays the details of the proposed migration.

Step 17 Click Finish.

The migration starts and progress is displayed.

Step 18 Click Finish.

A summary of the configuration displays.

Step 19 Go to Step 21.

Step 20 Click Finish.

A summary of the configuration displays.

Step 21 You have completed the setup of the Cisco Nexus 1000Vsoftware.
Return to the GUI Software Configuration Process.


Configuring the VSM HA Role

You can use this procedure to change the role of a VSM to one of the following after it is already in service:

standalone

primary

secondary

BEFORE YOU BEGIN

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

If you are changing a standalone VSM to a primary or secondary VSM, be sure to first isolate it from the other VSM in the pair as follows:

Disconnect the VSM VM management and control ports from the switch.

Stop the control and management VLAN in the upstream switch.

This prevents any interaction between the two VSMs during the change. Then power the VM off from the vSphere Client before reconnecting it as standby.

You are logged in to the CLI in EXEC mode.

The HA redundancy states are active and standby.

A change from a standalone to a primaryVSM takes effect immediately.

SUMMARY STEPS

1. show system redundancy status

2. system redundancy role {standalone | primary | secondary}

3. show system redundancy status

4. copy running-config startup-config

DETAILED STEPS

 
Command
Purpose

Step 1 

show system redundancy status

Example:

switch# show system redundancy status

Redundancy role

---------------

administrative: standalone

operational: standalone


Redundancy mode

---------------

administrative: HA

operational: None


This supervisor (sup-1)

-----------------------

Redundancy state: Active

Supervisor state: Active

Internal state: Active with no standby


Other supervisor (sup-2)

------------------------

Redundancy state: Not present

switch#

Displays the current redundancy status for the VSM(s).

Step 2 

system redundancy role [standalone | primary | secondary]

Example:

n1000v# system redundancy role primary

n1000v#

Designates the HA role of the VSM.

Step 3 

show system redundancy status

Example:

show system redundancy status

Redundancy role

---------------

administrative: primary

operational: primary


Redundancy mode

---------------

administrative: HA

operational: None


This supervisor (sup-1)

-----------------------

Redundancy state: Active

Supervisor state: Active

Internal state: Active with no standby


Other supervisor (sup-2)

------------------------

Redundancy state: Not present

switch#

(Optional) Displays the current redundancy status for the VSM(s).

Step 4 

copy running-config startup-config

Example:

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

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