I'd like to start off some discussion about the Nexus1000v with vSphere 6.5 which has just been released.
I have successfully run up a test ESXi and VCSA server and am looking at installing the N1kv in this environment. Note: I have had success and understanding of this from running this under VCSA-6.0 and ESXi-6.0 so I have used these products before - but not yet under 6.5.
As of now the N1kv is not officially supported/validated on this release but I'd like to get as far as I can with installing it anyway. It looks like the problems may be mostly just about packaging and installation process rather than binary incompatibility.
So far the issues I have had are:
1. There is no vib to install on ESXi-6.5, and the ESXi-6.0 vib fails to install:
[root@vmware-2:~] esxcli software vib install -v /vmfs/volumes/55023178-7d2b0288-46fb-a0369f00f4aa/cross_cisco-vem-v320-18.104.22.168.2.5.0-6.0.1.vib
VIB Cisco_bootbank_cisco-vem-v320-esx_22.214.171.124.2.5.0-6.0.1 requires esx-base = 6.0.0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
Is there a way to force this vem to load? I believe - but haven't tested - that this vib should be compatible with ESXi-6.5
2. With the vSphere Desktop client no longer supported or functional with VCSA 6.5, how can we import the cisco_nexus_1000v_extension.xml file with the embedded certificate into VCSA?
3. Has there been any indication from Cisco as to the timeframe or supportability and/or updates of the N1kv to allow it to work seamlessly with vSphere 6.5?
Hello folks - 6.5a works ok, VSM installs in vSphere and while VMware doesn't make it easy to integrate the plugin with vCenter, here is a great workaround I used and it was flawless:
I simply inserted these steps and the plugin works just fine.
Wes, can you or Cisco please comment on when ESXi 6.5 will be supported for Nexus 1000V? There's FUD being spread out there that Nexus 1000V will never be supported on ESXi 6.5. If that's the case, we need to abandon plans to buy 1000V Advanced+VSG, and start looking for other solutions.
Further, I have been unable to download Nexus 1000V from CCO since Dec 7th, and after 9 emails to email@example.com (most of which trying to get them to understand 1) this is a product cisco has, 2) it's free, and 3) no, I can't give you a PAK for a free product) there has been no response after supposed "internal escalation". I'm still stuck on 3.1.15 while 3.2.8 is available, but unable to be downloaded.
Judging by this forum, and this link
I'm not the only one. In fact, hitting "register" for the free trial gives me a 404 error.
If Cisco is not going to support this product going forward, it would be great if Cisco would at least let people know. End of Life notices were just posted for version 4, which leads me to believe the product isn't dead... but all of Cisco's actions speak to the contrary.
Please let me know this product is moving forward.
Hello, I'm hoping there is an update with ETA on this, or at least confirmation that VMware hasn't eliminated the possibility of N1K support on vCenter 6.5?
Got yesterday the information (deep cisco information) that in End of Q1 2017 Cisco will offer a Version running on vSphere 6.5. Hopefully this will be confirmed (official) very soon.
Bad news from VMware:
VMware is announcing the iiscontinuation of its thiri party virtual
switch (vSwitch) program. VMware intenis to ieprecate the APIs
usei by thiri party virtual switches, ani expects to remove the
APIs as part of a future upiate to VMware vSphere 6.5 as well
as future releases of the vSphere platform. Customers are
encouragei to begin migrating from thiri party vSwitches
incluiing Cisco Nexus 1000V, Cisco VM-FEX, Cisco AVS, HPE
5900v ani IBM DVS 5000v to vSphere Distributei Switch.
VMware will continue to support the 3ri party virtual switch APIs,
up to VMware vSphere 6.5 Upiate 1 ani prior vSphere versions,
as long as an active support ani subscription services contract
exists. In the next major vSphere release, ani upiate releases
post vSphere 6.5 Upiate 1, thiri party vSwitch APIs will be
completely removei ani thiri party vSwitches will no longer
VMware is making free migration tools available to assist
customers in transitioning to vSphere Distributei Switch or,
customers can work with VMware's Professional Services
If you are using 3ri party vSwitches, please contact your sales
representative with any questions ani to begin a transition plan.
So Cisco, what does this mean??
Andy, where did you receive this information? This has been suspected but to date I haven't seen anything from VMware on the matter. I also got the promise of Q1 support update from Cisco, but if 1000V support is going away after 6.5U1 we will have to make much bigger plans (that's a really short notice for deprecating such a huge piece of vmware).
If you received this in an email communication rather than published somewhere could you forward me a copy?
this is an information from VMware (basicly Screenshot from "My VMware"), but i get told that this will be a KB comming soon.
This will bring a lot of company's in big trouble.
Moving forward, VMware will have a single virtual switch strategy that focuses on two sets of native virtual switch offerings – VMware vSphere® Standard Switch and vSphere Distributed Switch™ for VMware vSphere, and the Open virtual switch (OVS). This strategy is about investing in the priorities of our customers and simplifying the platform to create the best, most secure experience possible.
It's not what is stated but what is not stated that is very revealing. Their strategy going forward does not include third party Virtual Switches - because apparently 99% of their vSphere customers use their Native Virtual Switch.
Ivan Pelelnjak also wrote about it here:
now its really official:
FYI, Release 5.2.1SV3(3.1) was released yesterday. Release notes show:
"This release of the Cisco Nexus 1000V supports vSphere 5.5, 6.0, and 6.5a release trains."
Release notes here
I'm still unable to download it, as I reported to Cisco in January - they apparently haven't fixed the issue with CCO entitlements.
I didn't see anything in the release notes responding re: VMware's announcements.
It's a shame - I'd pay for 1000V+VSG in a heartbeat if it were going to be supported. I migrated a couple hosts to VDS last night, and the fact that I have to do it through the slow, flash-based VMware web client made the job 5 times longer.
The 99% customer base VMware mentions are either people who don't know any better or are just drinking the VMware kool-aid.
That's really interesting piece of information. If this is just an internal memo from VMware, we should wait for Cisco's response. I'm pretty sure the install base of 3rd party vSwitches are quite huge.
I've worked out how to install vSphere 6.5 with Nexus 1000V (or well, I actually did a somewhat upgrade from 6.0).
For the adventurous, here are my steps:
Since I was upgrading from vSphere 6.0, I already had ESXi 6.0 hosts installed. I'm not a fan of automated vCenter upgrades, so I installed a clean vCenter 6.5. While migrating everything over, I quickly found out that I cannot find a way to import my previous N1K extension. Temporarily migrated everything to a dVS.
So, since deploying N1K via OVAs obviously wouldn't work now, I decided to try VSUM. Installed it and deployed a Nexus 1000V. That worked, but.. VEM modules were shown as unsupported. Alright, updated all the VEM modules on the ESXi (6.0) hosts. Nexus 1000V started to work again.
After that I started to upgrade ESXi hosts to 6.5. No go - couldn't remediate since the N1K VEM was incompatible with ESXi 6.5.
Used the hacky solution provided by Reuben Farrelly above with slight modifications. Instead of changing the dependency to 6.5.0, I changed it to "greater than 5.5.0". If wouldn't have done that, I would've had to
*) Remove the previous VEM from all ESXis
*) Upgrade to ESXI 6.5
*) Install the repackaged VIB
Changing it to greater than 5.5.0 simplified it. Now I just had to
*) Upgrade the VEM on all the hosts (scripted it over SSH)
*) Upgrade ESXi to 6.5
Everything seems to work. N1K shows all modules attached and networking works.
Obviously a hacky solution but if you're coming from vSphere 6.0 and just interested in trying out vSphere 6.5, this is probably one of the easiest ways.
have you tried installing N1KV using VSUM? This is rather straight forward process (with vCenter App 6.0).