Installing Nexus 1000V on vSphere 5.1 (Part Two)
In the first part of the article, I did a general overview of the Cisco Nexus 1000v product and deployed applains (VSM).
In this part, I will show how you can configure VSM and install VEM — to fully prepare the Cisco Nexus 1000v to work in vSphere.
1) Configure VSM
Go to the global configuration mode and run the setup command:
')
The settings dialog opens (in bold, I highlight the input values):
If during installation Manually mode was selected, then in the next step we answer Yes , if during the installation Installer was specified, then we skip the next steps by selecting No. Parameters may vary, depending on your needs:
Look what happened:
Configuration is ready, save:
Be sure to reboot the machine with VSM.
The first VSM machine is ready, now you need to establish its connection to the vCenter and create a DVS.
First we add the plugin to the vSphere Client, for this you need to go through the web to our VSM.
Download Extention.xml to a 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 it is necessary to add its plug-in, otherwise it will not connect to the vCenter server.
Plugin configuration:
Register it, get a warning, click Ignore and OK.
Plugin added:
I have two - since I put 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.
You can customize in several ways. The first way is through installing Cisco Nexus 1000V Installer App (in the downloaded archive from cisco.com there should be a folder with a .jar file):
The second way - manually, through the command line.
I will show the installation method manually.
Go to the global configuration mode, and enter the following commands:
When installing the vCenter server, I specified the port for it 8081 - it is worth considering this if you have a different port.
In Inventory -> Networking you can see that the switch is added:
The setting is over.
2) Installing VEM into the hypervisor core.
VEM is installed directly into the core of the hypervisor.
It, as well as VSM can be installed in several ways.
The first way is to install VEM via VUM updates (VMware Update Manager).
The second way - if the VUM does not have access to the Internet, then you can install it through the installation of the vib-package. The package is in the archive downloaded from cisco.com:
Depending on the version of the hypervisor, you must install a specific package.
Since I can update the hypervisor via VUM without any problems, I will use the first method.
Go to the Update Manager section on the vSphere client home page.
Go to the section Baseline and Groups , create a new group Baseline :
We name it and select the type of host extensions .
Next, select the manufacturer and version of vSphere in the filter.
Select what you need, add them and click Next.
Select the host on which you plan to install the updates, go to the Update Manager tab.
We add to it the created baseline:
Click Scan, VUM will show that the add-ons have not been installed. We click Remediate and install the necessary add-ons, of course the version of the add-on should coincide with the version of VSM.
I will not say that the host is desirable to release from the machines before the update and send it to the Maintenance mode (Maintenance mode).
We are waiting for the end of the installation, the hosts should not restart.
3) Installing Secondary VSM.
Installing a second machine for an HA cluster is very similar to installing one, only much simpler.
It is placed from the same OFV template as the first one.
When installing, select the Nexus 1000V Secondary configuration:
Network interface settings must be identical to the first machine:
In the next step, you need to fill in items a and b only ! Items c, d, e are not required.
In paragraph a, you must specify the same ID as the first car, in paragraph b the same password that was specified when installing the first car.
We are waiting for the VM to unfold from this template and launch it.
If everything went right, then after loading we will see the following in the console:
The car found an active VSM and went into standby mode.
If this does not happen, then you need to run setup. It is necessary to indicate that it is a secondary machine, then reboot - everything should work. If not, then you need to look at the network settings - maybe not any VLANs.
You can check VSM using 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 a new switch, and remove the standard switch.
In this part, I will show how you can configure VSM and install VEM — to fully prepare the Cisco Nexus 1000v to work in vSphere.
1) Configure VSM
Go to the 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 system configuration. Setup configures only enough connectivity for management of the system.
* Note: setup is mainly used for configuring the system when it is present. It doesn’t always have the current system configuration values.
Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.
If during installation Manually mode was selected, then in the next step we answer Yes , if during the installation Installer was specified, then we skip the next steps by selecting No. Parameters may vary, depending on your needs:
The 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
Look 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
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 establish its connection to the vCenter and create a DVS.
First we add the plugin to the vSphere Client, for this you need to go through the web to our VSM.
Download Extention.xml to a 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 it is necessary to add its plug-in, otherwise it will not connect to the vCenter server.
Plugin configuration:
Register it, get a warning, click Ignore and OK.
Plugin added:
I have two - since I put 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.
You can customize in several ways. The first way is through installing Cisco Nexus 1000V Installer App (in the downloaded archive from cisco.com there should be a folder with a .jar file):
The second way - manually, through the command line.
I will show the installation method manually.
Go to the 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 specified the port for it 8081 - it is worth considering this if you have a different port.
In Inventory -> Networking you can see that the switch is added:
The setting is over.
2) Installing VEM into the hypervisor core.
VEM is installed directly into the core of the hypervisor.
It, as well as VSM can be installed in several ways.
The first way is to install VEM via VUM updates (VMware Update Manager).
The second way - if the VUM does not have access to the Internet, then you can install it through the installation of the vib-package. The package is in the archive downloaded from cisco.com:
Depending on the version of the hypervisor, you must install a specific package.
Since I can update the hypervisor via VUM without any problems, I will use the first method.
Go to the Update Manager section on the vSphere client home page.
Go to the section Baseline and Groups , create a new group Baseline :
We name it and select the type of host extensions .
Next, select the manufacturer and version of vSphere in the filter.
Select what you need, add them and click Next.
Select the host on which you plan to install the updates, go to the Update Manager tab.
We add to it the created baseline:
Click Scan, VUM will show that the add-ons have not been installed. We click Remediate and install the necessary add-ons, of course the version of the add-on should coincide with the version of VSM.
I will not say that the host is desirable to release from the machines before the update and send it to the Maintenance mode (Maintenance mode).
We are waiting for the end of the installation, the hosts should not restart.
3) Installing Secondary VSM.
Installing a second machine for an HA cluster is very similar to installing one, only much simpler.
It is placed from the same OFV template as the first one.
When installing, select the Nexus 1000V Secondary configuration:
Network interface settings must be identical to the first machine:
In the next step, you need to fill in items a and b only ! Items c, d, e are not required.
In paragraph a, you must specify the same ID as the first car, in paragraph b the same password that was specified when installing the first car.
We are waiting for the VM to unfold from this template and launch it.
If everything went right, then after loading we will see the following in the console:
The car found an active VSM and went into standby mode.
If this does not happen, then you need to run setup. It is necessary to indicate that it is a secondary machine, then reboot - everything should work. If not, then you need to look at the network settings - maybe not any VLANs.
You can check VSM using 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 a new switch, and remove the standard switch.
Source: https://habr.com/ru/post/171639/
All Articles