April 10, 2013 at 14:53Installing Nexus 1000V on vSphere 5.1 (Part Two)
- Tutorial
In the first part of the article, I did a general overview of the Cisco Nexus 1000v product and deployed application (VSM).
In this section, I’ll show you how to configure VSM and install VEM — to fully prepare your Cisco Nexus 1000v for use in vSphere.
1) Configuring VSM
Go to global configuration mode and run the setup command:
The settings dialog opens (in bold I highlight the input values):
If the installation was selected Manually mode , then the answer in the next step Yes , if the installation has been specified Installer - the following steps are skipped by selecting No . Parameters may vary, depending on your needs:
We look at what happened:
The configuration is ready, save:
Be sure to reboot the machine with VSM.
The first VSM machine is ready, now you need to connect it to vCenter and create a DVS.
First, add the plugin to vSphere Client, for this you need to go via the web to our VSM.
Download Extention.xml to the local computer.
Open vSphere Client, Plugins -> Manage Plugins
Right-click and add a new plugin, choosing the downloaded file.
It is important to note that for each instance of the switch you must add its plugin, otherwise, it will not connect to the vCenter server.
Plugin configuration:
Register it, a warning pops up, click Ignore and OK.
Plugin added:
I have two - since I set one switch earlier.
After adding the plugin, go to the console of our VM and check the connection with the vCenter server with the command:
There are no connections, they need to be configured.
There are several ways to configure. The first method is through the installation of the Cisco Nexus 1000V Installer App (the downloaded archive from cisco.com should contain a folder with the .jar file): The
second method is manual, through the command line.
I will show the manual installation method.
We go into global configuration mode, and enter the following commands:
When installing the vCenter server, I indicated the port for it as 8081 - it should be taken into account if you have a different port.
In Inventory -> Networking, you can see that the switch has been added: The
configuration is now complete.
2) Installing VEM in the core of the hypervisor.
VEM is installed directly in the core of the hypervisor.
It, like VSM, can be installed in several ways.
The first way is to install VEM through VUM updates (VMware Update Manager).
The second way - if VUM does not have access to the Internet, then you can install it by installing the vib-package. The package is in the archive downloaded from cisco.com:
Depending on the version of the hypervisor, you need to install a specific package.
Since I can update the hypervisor through VUM without any problems, I will use the first method.
Go to the Update Manager section on the vSphere client home page.
We go to the Baseline and Groups section , create a new Baseline group :
Name it and select the type of host extensions .
Next, in the filter, select the manufacturer and version of vSphere.
Select what is needed, add them and click Next.
Select the host on which you plan to install updates, go to the Update Manager tab.
Add the created baseline to it:
Click Scan, VUM will show that add-ons have not been installed. Click Remediate and install the necessary add-ons, of course, the add-on version must match the version of VSM.
I will not say that it is advisable to release the host from the machines before the update and send it to the maintenance mode.
We are waiting for the installation to finish, the hosts should not reboot.
3) Install Secondary VSM.
Installing a second machine for the HA cluster is very similar to installing the first, only much easier.
It is placed from the same OFV template as the first.
During installation, select the configuration of the Nexus 1000V Secondary:
Network interface settings should be identical to the first machine:
In the next step, only the items must be filleda and b ! Paragraphs c, d, e are not required.
In paragraph a, you must specify the same ID as the first machine, in paragraph b the same password that was specified when installing the first machine.
We are waiting for VM to unfold from this template and start it.
If everything went right, then after loading we will see the following in the console:
The machine found the active VSM and became in standby mode.
If this does not happen, then you need to run setup. It is necessary to indicate in it that this is a secondary machine, after that reboot - everything should work. If not, then you need to look at the network settings - maybe some VLANs are not rolled.
You can verify VSM with the show module command executed on the active host:
This completes the installation process.
After installation, it will be necessary to add hosts to the Nexus 1000v switch, migrate the network of machines to the new switch, and remove the standard switch.
In this section, I’ll show you how to configure VSM and install VEM — to fully prepare your Cisco Nexus 1000v for use in vSphere.
1) Configuring VSM
Go to global configuration mode and run the setup command:
switch # configure terminal
switch (config) # setup
The settings dialog opens (in bold I highlight the input values):
Enter HA role [standalone / primary / secondary]: primary
Enter the domain id <1-4095> 2
[############################ ##############] 100%
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.
If the installation was selected Manually mode , then the answer in the next step Yes , if the installation has been specified Installer - the following steps are skipped by selecting No . Parameters may vary, depending on your needs:
Would you like to enter the basic configuration dialog (yes / no): yes
Create another login account (yes / no) [n]: no
Configure read-only SNMP community string (yes / no) [n]: no
Configure read- write SNMP community string (yes / no) [n]: no
Enter the switch name: PM-NX-03
Continue with Out-of-band (mgmt0) management configuration? [yes / no] [y]: yes
Mgmt0 IPv4 address: 10.4.1.100
Mgmt0 IPv4 netmask: 255.255.0.0
Configure the default-gateway: (yes / no) [y]: yes
IPv4 address of the default gateway: 10.4.1.147
Configure Advanced IP options (yes / no)? [n]: no
Enable the telnet service? (yes / no) [y]: yes
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
Enable the http-server? (yes / no) [y]: yes
Configure NTP server? (yes / no) [n]: no
Configure svs domain parameters? (yes / no) [y]: yes
Enter SVS Control mode (L2 / L3): L2
Enter control vlan <1-3967, 4048-4093>: 54
Enter packet vlan <1-3967, 4048-4093>: 54
Would you like to edit the configuration? (yes / no) [n] no
We look at what happened:
The following configuration will be applied:
Switchname PM-NX-03
interface Mgmt0
ip address 10.4.1.100 255.255.0.0
no shutdown
no telnet server enable
ssh key rsa 1024 force
ssh server enable
feature http-server
svs-domain
svs mode L2
control vlan 54
packet vlan 54
domain id 2
vlan 54
The configuration is ready, save:
Use this configuration and save it? (yes / no) [y]: yes
[########################################## #] 100%
Be sure to reboot the machine with VSM.
The first VSM machine is ready, now you need to connect it to vCenter and create a DVS.
First, add the plugin to vSphere Client, for this you need to go via the web to our VSM.
Download Extention.xml to the local computer.
Open vSphere Client, Plugins -> Manage Plugins
Right-click and add a new plugin, choosing the downloaded file.
It is important to note that for each instance of the switch you must add its plugin, otherwise, it will not connect to the vCenter server.
Plugin configuration:
Register it, a warning pops up, click Ignore and OK.
Plugin added:
I have two - since I set one switch earlier.
After adding the plugin, go to the console of our VM and check the connection with the vCenter server with the command:
show svs connections
There are no connections, they need to be configured.
There are several ways to configure. The first method is through the installation of the Cisco Nexus 1000V Installer App (the downloaded archive from cisco.com should contain a folder with the .jar file): The
second method is manual, through the command line.
I will show the manual installation method.
We go into global configuration mode, and enter the following commands:
PM-NX-03 # conf t
PM-NX-03 (config) # svs connect vc
PM-NX-03 (config-svs-conn) # remote ip address 10.4.1.50 port 8081
PM-NX-03 (config-svs -conn) # protocol vmware-vim
PM-NX-03 (config-svs-conn) # vmware dvs datacenter-name M1
PM-NX-03 (config-svs-conn) # connect
When installing the vCenter server, I indicated the port for it as 8081 - it should be taken into account if you have a different port.
In Inventory -> Networking, you can see that the switch has been added: The
configuration is now complete.
2) Installing VEM in the core of the hypervisor.
VEM is installed directly in the core of the hypervisor.
It, like VSM, can be installed in several ways.
The first way is to install VEM through VUM updates (VMware Update Manager).
The second way - if VUM does not have access to the Internet, then you can install it by installing the vib-package. The package is in the archive downloaded from cisco.com:
Depending on the version of the hypervisor, you need to install a specific package.
Since I can update the hypervisor through VUM without any problems, I will use the first method.
Go to the Update Manager section on the vSphere client home page.
We go to the Baseline and Groups section , create a new Baseline group :
Name it and select the type of host extensions .
Next, in the filter, select the manufacturer and version of vSphere.
Select what is needed, add them and click Next.
Select the host on which you plan to install updates, go to the Update Manager tab.
Add the created baseline to it:
Click Scan, VUM will show that add-ons have not been installed. Click Remediate and install the necessary add-ons, of course, the add-on version must match the version of VSM.
I will not say that it is advisable to release the host from the machines before the update and send it to the maintenance mode.
We are waiting for the installation to finish, the hosts should not reboot.
3) Install Secondary VSM.
Installing a second machine for the HA cluster is very similar to installing the first, only much easier.
It is placed from the same OFV template as the first.
During installation, select the configuration of the Nexus 1000V Secondary:
Network interface settings should be identical to the first machine:
In the next step, only the items must be filleda and b ! Paragraphs c, d, e are not required.
In paragraph a, you must specify the same ID as the first machine, in paragraph b the same password that was specified when installing the first machine.
We are waiting for VM to unfold from this template and start it.
If everything went right, then after loading we will see the following in the console:
The machine found the active VSM and became in standby mode.
If this does not happen, then you need to run setup. It is necessary to indicate in it that this is a secondary machine, after that reboot - everything should work. If not, then you need to look at the network settings - maybe some VLANs are not rolled.
You can verify VSM with the show module command executed on the active host:
This completes the installation process.
After installation, it will be necessary to add hosts to the Nexus 1000v switch, migrate the network of machines to the new switch, and remove the standard switch.