Once Java finishes launching, you’ll be brought into a wizard for the initial configuration. Now onwards to actually performing the initial configuration of the Nexus 1000v.įire up your browser and navigate to the management IP you configured for the Nexus 1000v:Ĭlick on the Launch Installer Application link on the webpage presented: The Nexus 1000v has been successfully deployed with the ova file. Once completed, you can proceed with powering up the virtual machine and watch the console as the Nexus 1000v boots: Once you click finish, the virtual machine will begin to deploy: The following provides you with a summary of the settings you’ve entered during the initial configuration: Without going into too much detail, make sure you choose the appropriate port groups you’ll be using for the 3 networks specified:Įnter the appropriate password, management IP, management mask, management gateway: I always prefer to use Thick for appliances such as these: Here you get to choose whether you want to use Thick or Thin provisioning. The reason for this is obvious: if your host goes down, you want to make sure you don’t have both Nexus 1000v on the same host. In the following window, you are asked to specify the host in which you would like to use to host the Nexus 1000v and it is important to note that if you do not intend to use automated DRS or manually move the Nexus 1000v to another host, you should write down which host you’re going to use for the FIRST Nexus 1000v and proceed with using a DIFFERENT host for the SECOND passive Nexus 1000v.
#Vmware esxi 5 sv 51249 blogs manual
Unless you have plans to go through the manual install, choose theĬontinue with choosing your cluster belonging to the appropriate data center: Name the Nexus 1000v VSM according to your naming convention:
#Vmware esxi 5 sv 51249 blogs install
Locate the ova file in the Install folder (the one I’m using is nexus-1000v.4.0.4.SV1.3b.ova):Ĭlicking next will show the following window presenting you with the information about the Nexus 1000v you’re deploying: My suggestion? Check the Cisco website for the latest build.ĭownload the latest build available (the one I used was Nexus1000v.4.0.4.SV1.3b.zip), unzip the package into a folder and VI Client to vCenter. Note: One of the things I noticed while looking for the latest version was that if I were to log into the VMware product downloads page, the latest version posted was 1.3 (not a or b) but if I log into Cisco’s site, I would see 1.3b which was the latest version. So the bug seems to be that if the vmx file is referencing a PortGroup that does not exist, you can not edit the mapping of the NICs.There isn’t much on this post as the purpose of it is just to show what a Cisco Nexus 1000v 4.0.4.SV1.3b install looks like. I finally just rename the "VM Network" PortGroup to "Management" and then is worked.
I tried editing the VM several times and it would never actually take. It keeps telling me that PortGroup "Management" could not be found. I then tried to change NIC 1 to be "VM Network" and pressed save. In past versions of VMware Clients, it would reset back to "VM Network" or nothing. But when you try to edit the settings for the Linux VM in the embedded Host Client you will see that both NICs are mapped to PortGroup Foo.
The VM on ESX Server 2 could not find the PortGroup "Management" which is to be expected. I shut down the Linux VM and moved it (SCP) to ESX Server 2. However, I did not rename the "VM Network" PortGroup to "Management" on ESX Server 2 like I had done on ESX Server 1. When I setup the vSwithes and PortGroups on ESX Server 2, I setup a new vSwitch and a new PortGroup called Foo. NIC 1 = PortGroup Management, NIC 2 = PortGroup Foo. I moved (SCP) a Linux VM from one ESX Server 1 (ver 5.5) to ESX Server 2 (ver 6) that is running the embedded Host Client and can not set the NIC PortGroup mappings.