Header Only - DO NOT REMOVE - Extreme Networks

How to set up Wing controller that will connect directly to ISP ip address?


I have a virtual VX9000 controller, a 7522 ap and an ISP static ip.

9 replies

Userlevel 6
Hi Ronaldo,

could you give me a little wider description of what you are about to do?
As VX9000 is virtualized machine, you always need to think about hypervisor.

If this is in house server you need to prepare the connection to assign external IP, if this is cloud based installation, you might have this directly.

Either or, please find VX9000 installation guide here so you can learn a little more on how to setup VX while installing or here to find system reference guide for general release WiNG 5.8 (not sure what version you have).
If there are not other restrictions, you may assign manual IP address to your VX VLAN and have it accessible publicly.

Then you'll just pre-stage APs or let them use DHCP option 191 to find controller.
Little outdated, yet valid documentation to be found here.

EDIT: Option 60 is not valid anymore. This is changed to WiNG. I believe.

Regards,
Ondrej
What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks
Userlevel 6
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

HI Ronaldo,

If I understand correctly, below topology is what you wish to have, right?



If yes, this will be in control of hypervising server. You may use forwarding, VLAN tunneling or segmentation.
VX9000 will be only part of specific subnet in scope of hypervisor and will accept ISP or manually added IP address.

Every AP keen to adopt to this VX9000 will need to know its public IP.
Also port UDP 24576 has to be open on VX side for MINT (level2) adoption.

Regards,
Ondrej
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

Hi Ondrej,

Can you share a link where i can learn how to do this configuration. I am really lost here. Total newbie. Thanks.

Regards,
Ronaldo
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

I am testing via a laptop by the way. VX9000 is installed on the same laptop as a virtual machine. The laptop, AP, and the ISP cable are inserted on one same PoE switch. this is my set up. Will this work?
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

Also, I noticed in your diagram that VX9000 is in the same network segment as the ISP?
Userlevel 6
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

Hi Ronaldo,

I am afraid that the part of hypervisor is out of my scope and level of knowledge.
You could do a simple routing rules on your VM server and VX9000 will be easily accessible from ISP side, but again - this is out of VX configuration scope.

In the end, only thing that matters here is how physical connection traverses the hypervisor to the virtual machine. WiNG system is ready to use whatever IP address you supply it with.

Regards,
Ondrej
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

It's alright Ondrej, thanks for the help 🙂
Userlevel 4
Ronaldo Asimao wrote:

What we are trying to achieve is that vx9000 should not be connected to the existing private network. We will be having a dedicated leased line from our ISP to be configured on it. Then connect some APs for internet distribution. I'm not sure if you get what I am trying to say, my English is not that good. i am also new to wireless technology. Thanks

Hi,
do you solve the problem? You need to separate all the networks.

Adoption via fix ISP IP can be done like internal, DHCP, DNS or static AP entry (pre-staged).

If you test it with one Switch, you can create VLANs to separate all traffics between VX, internal network an AP network.

BR Timo

Reply