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 220.127.116.11.
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 18.104.22.168 & 22.214.171.124.
The VX9000 running 126.96.36.199. 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 188.8.131.52 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?
Best answer by Drooly McGee
Thanks for your reply.
Yes, this was the same response I had from GTAC; that basically to use WING 184.108.40.206. 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 220.127.116.11.so thanks for the info on 7.2.x. & 18.104.22.168.