Header Only - DO NOT REMOVE - Extreme Networks
Solved

VX9000 Initial Setup

  • 3 July 2020
  • 7 replies
  • 132 views

Hi everyone. I hope some of you will be able to help me.

I’m attempting to setup a virtual VX9000 appliance on Microsoft Hyper-V which is running on Windows Server 2016 DataCenter.

Now I am familiar, but by no means an expert on WING as we have two standalone RFS4010 controllers running WING 5.8.4.0.

I’m still evaluating which version of WING to use on the VX9000 and to that end I’ve setup versions of the VX9000 running both WING 5.9.1.10 & 7.4.0.0.

The VX9000 running 7.4.0.0. on initial startup doesn’t receive a DHCP address from our DHCP Server (Windows 2016 Server Standard) and the status of interface VLAN1 given by SHOW IP INTERFACE BRIEF is “unassigned(DHCP)” although STATUS & PROTOCOL are both shown as up. Changing the VLAN1 IP address to a static one still results in the VX9000 still not connecting. PINGS and connecting to the Web GUI fail.

Contrast this with the WING 5.9.1.10 version which gets a DHCP address immediately on first startup and is reachable via the DHCP address and when changed to a static IP.

Long setup, but hopefully now a shorter question:

What am I missing? What has changed between these WING versions?

Many Thanks.

icon

Best answer by Drooly McGee 20 July 2020, 10:56

Hi Martin8052,

Thanks for your reply.

Yes, this was the same response I had from GTAC; that basically to use WING 7.4.0.0. on Hyper-V (I’m using Windsows Server 2016), a Legacy Network Adapter has to be used. I agree with you, this seems a backward step and shouldn’t be the solution. I hadn’t tried any other “7” WING versions prior to 7.4.0.0.so thanks for the info on 7.2.x. & 7.3.1.0.

Kind Regards. 

View original

7 replies

Userlevel 6

Drooly, I’ve not setup a VX9K in Hyper-V before, but it is supported, so not sure what’s happening here.

If it were me, as a test, I would attempt to assign a static IP address to the VX9K, even though it’s not getting a DHCP lease, and then see if the VX9K actually has access to that network and can reach the DHCP server.  It would be interesting to hear the results of that test.

Hi Chris,

Thanks for your reply.

Yes I’ve done that and assigned a static IP address to it. It still has no connectivity though.

Just to be clear this only happens with WING 7.4.0.0. When I use a Virtual VX9000 running 5.9.1.0 on the same host it connects initially with a DHCP address and maintains connectivity when the IP address is changed to a static one.

I’m at a loss as to why the difference between the two versions though.

Kind Regards

Userlevel 6

Understood.  I don’t think I’ll be of much help here beyond this one suggestion.  I really not would have expected there to be ANY differences in this area between WiNG-5 and WiNG-7 (from a setup standpoint, there IS no difference).  If both WING-5 and WiNG-7 would have behaved this way, then would have then say it’s a Hyper-V issue.

I think that unless someone runs across your question that has dealt with this specific scenario before, this is going to be an issue that GTAC is going to have to look into.

Thanks Chris,

Appreciate your help. I’ll raise a case with GTAC and see if they can shed any light on the problem.

Kind Regards.

Userlevel 1

Hello,

I have seen that since Wing 7.3.1.1 there is something broken with network and Hyper-V. If I install Wing 7.3.1.1 or newer on a Hyper-V Host (testet Server 2012 R2 and Server 2019) the Interface is Down (seen in “Show interface ge1” and “show interface swtichboard”)

If I add in Hyper-V Manager an Legacy Network Adapter to the VM, I get a connected Interface. But using legacy virtual network adapter shouldnt be the solution, as it was working till Wing 7.2.x.

BTW Wing 7.3.1.0 doesnt even start on Hyper-V, but there is already a techdoc on this case.

Martin

Hi Martin8052,

Thanks for your reply.

Yes, this was the same response I had from GTAC; that basically to use WING 7.4.0.0. on Hyper-V (I’m using Windsows Server 2016), a Legacy Network Adapter has to be used. I agree with you, this seems a backward step and shouldn’t be the solution. I hadn’t tried any other “7” WING versions prior to 7.4.0.0.so thanks for the info on 7.2.x. & 7.3.1.0.

Kind Regards. 

Userlevel 1

Hi Drooly,

the cause is probably the new Linux Kernel 4.14.142 they are using since 7.3.1.0. I opened also a GTAC case, lets wait what I got as a response.

The 7.3.1.0 doesn’t even start on Hyper-V, but this is a know issue.

Martin

 

Reply