||From the vSphere Client, choose File > Deploy OVF Template.
||In the Source screen, specify the location of the OVA file and click Next. |
The OVF Template Details screen opens displaying product information, including the size of the file and the size of the VM disk.
||Read the Cisco Nexus 1000V License Agreement.|
||Click Accept and then click Next.|
||Add the VSM name, choose the folder location within the inventory where it will reside, and click Next. |
The name for the VSM must be unique within the inventory folder and less than 80 characters.
Figure 1. Deploy OVF Template Screen
||In the Deployment Configuration Screen, from the Configuration drop-down list, choose Nexus 1000V Installer. |
This choice configures the primary VSM using the GUI setup dialog.
||Click Next. |
||Choose the data center or cluster on which to install the VSM. |
||Choose the datastore in which to store the file if one is available. |
On this page, you choose from datastores already configured on the destination cluster or host. The virtual machine configuration file and virtual disk files are stored on the datastore. Choose a datastore large enough to accommodate the virtual machine and all of its virtual disk files.
||Choose the Thick provisioned disk format for storing virtual machine virtual disks, and click Next.
The storage is allocated on demand as data is written to the virtual disks.
This disk format is not supported for Cisco Nexus 1000V.
All storage is immediately allocated.
This format is only available with VMWare ESXi 5.0.
All storage for the virtual disk is allocated in advance.
||In the Network Mapping screen, choose the networks (the control, management, and packet port groups) that are present in your inventory.|
||Do one of the following: |
- If you are installing software on a primary VSM, specify the following properties for your primary VSM:
- VSM domain ID
- Admin password
- Management IP address
- Management IP subnet mask
- Management IP gateway
- If you are installing software on a secondary VSM, specify only the following properties for your secondary VSM (all other properties are acquired on synchronization with the primary VSM), and then click Next:
- VSM domain ID (use the same domain ID entered for the primary).
- Admin password (use the same password entered for the primary).
Figure 2. Properties Screen
||In the Ready to Complete Screen, if the configuration is correct, click Finish. |
||Click Close. |
You have completed installing the Cisco Nexus 1000V software.
||Right-click the VSM and choose Open Console.|
||Click the green arrow to power on the VSM.|
||Enter the following commands at the VSM prompt. |
switch# configure terminal
||Enter the HA role. |
If you do not specify a role, standalone is assigned by default.
This example shows the HA role as primary.
Enter HA role[standalone/primary/secondary]: primary
---- Basic System Configuration Dialog ----
This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.
*Note: setup is mainly used for configuring the system initially,
when no configuration is present. So setup always assumes system
defaults and not the current system configuration values.
Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.
Would you like to enter the basic configuration dialog (yes/no):
This example shows the HA role as secondary.
Enter HA role[standalone/primary/secondary]: secondary
Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :
||Do one of the following: |
- If you are setting up the primary/active VSM, go to Step 18.
- If you are setting up the secondary/standby VSM, then continue with the next step.
||If you have set up the VSM virtual machine (VM) to boot from the CD-ROM, and are installing the secondary VSM from the ISO image attached to your CD-ROM, remove the virtual CD-ROM now so that the VSM does not boot from the CD. |
This step is necessary if you have set up the VSM VM to boot from the CD-ROM before the hard drive.
||If you are setting up the secondary/standby VSM, when prompted to reboot the VSM, answer yes. |
The secondary VSM VM is rebooted and brought up in standby mode.
The password on the secondary VSM is synchronized with the password on the active/primary VSM.
Any configuration made on the active/primary VSM is now automatically synchronized with the standby.
This example shows the system rebooting when the HA role is set to secondary.
Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :y
HA mode set to secondary. Rebooting now...
You have completed this procedure for the secondary VSM.
||Enter yes to enter the basic configuration dialog. Would you like to enter the basic configuration dialog (yes/no): yes|
||Enter no to create another Login account. |
Create another login account (yes/no) [n]: no
||Enter no to configure a read-only SNMP community string. |
Configure read-only SNMP community string (yes/no) [n]: no
||Enter no to configure a read-write SNMP community string. |
Configure read-write SNMP community string (yes/no) [n]: no
||Enter a name for the switch. |
Enter the switch name: n1000v
||Enter yes to configure out-of-band management and then enter the mgmt0 IPv4 address and subnet mask. |
Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]: yes
Mgmt0 IPv4 address: 172.28.15.152
Mgmt0 IPv4 netmask: 255.255.255.0
||Enter yes to configure the default gateway. |
Configure the default-gateway: (yes/no) [y]: yes
IPv4 address of the default gateway : 172.23.233.1
||Enter no to configure advanced IP options. |
Configure Advanced IP options (yes/no)? [n]: no
||Enter yes to enable the Telnet service. |
Enable the telnet service? (yes/no) [y]: yes
||Enter yes to enable the SSH service and then enter the key type and number of key bits. |
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
For more information, see the document, Cisco Nexus 1000V Security
||Enter yes to enable the HTTP server. |
Enable the http-server? (yes/no) [y]: yes
||Enter no to configure the NTP server. |
Configure NTP server? (yes/no) [n]: no
||Enter yes to configure the SVS domain parameters and then enter the mode (L2 or L3), and the control and packet VLAN IDs. |
Configure svs domain parameters? (yes/no) [y]: yes
Enter SVS Control mode (L2 / L3) : L2
Enter control vlan <1-3967, 4048-4093> : 100
Enter packet vlan <1-3967, 4048-4093> : 101
||Enter yes to configure the VEM feature level and then enter 0 or 1. |
Vem feature level will be set to 4.2(1)SV1(5.2b),
Do you want to reconfigure? (yes/no) [n] yes
Current vem feature level is set to 4.2(1)SV1(5.2b)
You can change the feature level to:
vem feature level is set to the highest value possible
The system now summarizes the complete configuration and asks if you want to edit it.
The following configuration will be applied:
ip address 172.28.15.152 255.255.255.0
no telnet server enable
ssh key rsa 1024 force
ssh server enable
svs mode L2
control vlan 100
packet vlan 101
domain id 101
||Do one of the following: |
- If you do not want to edit the configuration enter no and continue with the next step.
- If you want to edit the configuration, enter yes and return to Step 19 to revisit each command.
Would you like to edit the configuration? (yes/no) [n]:no
||Enter yes to use and save this configuration. |
If you do not save the configuration now, none of your changes will be part of the configuration the next time that the switch is rebooted. Enter yes to save the new configuration and to ensure that the kickstart and system images are also automatically configured.
Use this configuration and save it? (yes/no) [y]: yes
The new configuration is saved into nonvolatile storage.
You can use the setup routine to update the configuration done in Step 18 through Step 33 at any time by entering the setup command in EXEC mode. Once setup begins, press Enter to skip a command. Press Ctrl-C to skip the remaining commands.
If you are installing redundant VSMs, make sure that you configure the software on the primary VSM before installing the software on the secondary VSM.
||Create the SVS connection manually or go to Establishing the SVS Connection. |