Header Only - DO NOT REMOVE - Extreme Networks

V2110 ESXi 6.5


Userlevel 2
Hi All,

Is it possible to run V2110 on ESXi 6.5? Release notes suggests the following:

The V2110 is packaged in the .OVA file format defined by VMware. It must be deployed on a VMware ESX or ESXi host running version 4.1 u1, 5.0, or 5.1 of vSphere.

Not sure.

Thank you,
Mykahylo

26 replies

Userlevel 6
Hello, Mikhaylo!

In newer RelNotes - The V2110 is supported on ESXi version 5.5 and 6.0
It's mean that V2110 tested on this ESXi releases.

Asked our VMWare colleagues - they tell that if soft work on 5.5 and 6.0 then it would be working on 6.5

Thank you!
Userlevel 2
Hello Alex,

Thanks for your reply. Am l able to get a trial version to test this first before buying a license?

Regards,
Mykhaylo
Userlevel 6
Mykhaylo Skrypka wrote:

Hello Alex,

Thanks for your reply. Am l able to get a trial version to test this first before buying a license?

Regards,
Mykhaylo

You have to talk with your local representative (in your country).
They can generate trial license.

Relying on your name - am I right that you from Ukraine?
If yes - you can wright to MUK company, local distributor. (or directly to me 🙂 )

Thank you!
Userlevel 2
Mykhaylo Skrypka wrote:

Hello Alex,

Thanks for your reply. Am l able to get a trial version to test this first before buying a license?

Regards,
Mykhaylo

Hi Alex,

Yeap l am from Ukraine but based in UK (London) 🙂
Can you still help or l need to talk to UK distributor?

thanks,
Mykhaylo
Userlevel 6
Mykhaylo Skrypka wrote:

Hello Alex,

Thanks for your reply. Am l able to get a trial version to test this first before buying a license?

Regards,
Mykhaylo

Mykhaylo!

I think it's better to talk with your local dist.
Because in feature it would be more simple to work with issues in testing 🙂 (if such be present)

Thank you!
Userlevel 4
V10.31.01 due out at the end of March will support 6.5.

Thanks,

Will
Userlevel 5
For reference - https://gtacknowledge.extremenetworks.com/articles/Q_A/What-versions-of-ESXi-does-the-V2110-support
Userlevel 2
Thanks all
Userlevel 1
Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?
Userlevel 6
Dusan K. wrote:

Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?

Dusan

Did you upgrade v2110 hardware?

https://gtacknowledge.extremenetworks.com/articles/Q_A/Should-I-upgrade-if-my-vmware-vsphere-client-has-a-virtual-hardware-upgrade-option-available-for-my-v2110-controller
https://gtacknowledge.extremenetworks.com/articles/Solution/After-upgrading-my-V2110s-Virtual-Hardware-all-configurations-are-lost

-Gareth
Userlevel 1
Dusan K. wrote:

Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?

Hi Gareth,

I was following the Article #000013111: "Firmware Version 10.31 and newer support ESXi 5.5, 6.0 and 6.5."
How to upgrade the VM HW to 6.5 then? Latest .ova file is 10.11.x which is only supported on 6.0.

-Dusan
Userlevel 6
Dusan K. wrote:

Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?

Hi Dusan

There is no need to upgrade the virtual hardware, it should be left at the same version as the official OVA.

-Gareth
Userlevel 1
Dusan K. wrote:

Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?

Quote:
"Firmware Version 10.31 and newer support ESXi 5.5, 6.0 and 6.5."
"Validation of V2110 with VMWare ESXi 6.5 - Added support for VMWare ESXi 6.5 to the V2110."
Q: In what way? And should the customer want to upgrade to 6.5?
Userlevel 6
Dusan K. wrote:

Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?

Hi Dusan

You are correct, those versions of ESXi are supported with that version of v2110 software.

What is not supported is updating the virtual hardware, updating the virtual hardware is analogous to replacing an entire PC hardware system and expecting pre-installed software to support it the new configuration.

So if you are on ESXi 6.5 and hardware 8 and have issues, then please open a case with GTAC and we will look at it.

My understanding is that now you have rolled back to virtual hardware 8 and are on ESXi 6.5, everything is working, please correct me if I'm wrong.

-Gareth
Userlevel 1
Dusan K. wrote:

Hi!
Initially deployed V2110-10.11.03.0004.ova on ESXi 5.0 (VM version 😎 then upgraded to v10.31.04.0009 then upgraded ESXi to 6.5 (VM version 13). Unable to access V2110 ever since.
Any clue?

ESXi 5.5 & Virtual Hardware Version 10 was the highest we could get with V2110-10.11.03.0004.ova template, which is based on version 8.
For future ESXi upgrades you should bring V2110 hw version up ...
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&external...
Userlevel 7
Is the VM set to paravirtual as mentioned in the release notes...

http://documentation.extremenetworks.com/release_notes/extremewireless/9035069-03_ExtremeWireless_v1...

You need to be more precise... what do you mean with "unable to access" ?
Via GUI or via ssh, could you log in via the VM console

-Ron
Userlevel 1
Ron wrote:

Is the VM set to paravirtual as mentioned in the release notes...

http://documentation.extremenetworks.com/release_notes/extremewireless/9035069-03_ExtremeWireless_v1...

You need to be more precise... what do you mean with "unable to access" ?
Via GUI or via ssh, could you log in via the VM console

-Ron

Sure. Paravirtual was set at the installation.
Userlevel 1
Hi Ron,

no ping response, no GUI, ... only log in via VM console was possible. All the settings looked fine.
VM Hardware change back to 8 solved it 😕

-Dusan
Userlevel 7
I had the same issue before - please reboot the controller via the console.

# shutdown reboot
Userlevel 1
Ron,

please be informed that I can get v10.31.04.0009 operating with ESXi 5.5 (v10) highest.
Tried with # shutdown reboot as suggested with all other higher options 6.0/6.5 but no success.
Userlevel 6
Dusan,

I'm running v10.31 on VMware 6.0 without problems.

I installed the v10.11 OVA and upgraded it to v10.31.

You just need to make sure the SCSI controller is set to VMware Paravirtual, or the VM won't boot...

Userlevel 1
dflouret wrote:

Dusan,

I'm running v10.31 on VMware 6.0 without problems.

I installed the v10.11 OVA and upgraded it to v10.31.

You just need to make sure the SCSI controller is set to VMware Paravirtual, or the VM won't boot...



Hi Daniel,

must be something else as SCSI was set to Paravirtual from the very beginning.

The thing is that .ova template is based on Virtual Hardware Version 8, not supported in ver. 6.5 and future ... that's my customer's concern.

I am sure Extreme will make a new .ova based on newer VM HW ver.
Userlevel 7
It could be that it has nothing to do with VM/ESX.

In short before you where able to access the controller via GUI and ssh but after the upgrade that doesn't work (can't even ping) but you'd access the controller via the VM console.

From that the simple answer would be that the settings of the port that you use to access the controller got lost during the upgrade.

I'd check/configure the port settings again via the VM console.
Userlevel 1
Ron wrote:

It could be that it has nothing to do with VM/ESX.

In short before you where able to access the controller via GUI and ssh but after the upgrade that doesn't work (can't even ping) but you'd access the controller via the VM console.

From that the simple answer would be that the settings of the port that you use to access the controller got lost during the upgrade.

I'd check/configure the port settings again via the VM console.

Port settings checked via VM console and remained intact. All looked fine. Now, why connectivity was lost ... ?!
Userlevel 7
Ron wrote:

It could be that it has nothing to do with VM/ESX.

In short before you where able to access the controller via GUI and ssh but after the upgrade that doesn't work (can't even ping) but you'd access the controller via the VM console.

From that the simple answer would be that the settings of the port that you use to access the controller got lost during the upgrade.

I'd check/configure the port settings again via the VM console.

Did you upgrade the hardware version by chance?
https://gtacknowledge.extremenetworks.com/articles/Solution/After-upgrading-my-V2110s-Virtual-Hardwa...

Reply