Wireless Access

Reply
Contributor I

Controller IP for each VLAN

When our original controller installation was done the tech created a layer 3 address on the controller for each of the VLANs that were trunked to the controller (AP VLANs, Client VLANs).  That L3 addresses on the controller are not being used as gateways for any of the wired or wireless clients.  Is there really any value in having a L3 address for each VLAN?  I couldn't find any documentation of it but perhaps there are some WIPS functionality that requires a L3 address for the controller on each VLAN that has APs or wireless clients in it?

Aruba Employee

Re: Controller IP for each VLAN

There are a few things that need an IP on the interface, including captive portal redirection and IGMP. There are probably others, but those are the ones off the top of my head.
Contributor I

Re: Controller IP for each VLAN

Thansk for the response.  Yeah I think you're correct that the captive portal subnet would need an IP.  I'm mainly interested in the other VLANs that simply house access points.

Contributor I

Re: Controller IP for each VLAN

Anyone know of any other reason?

Frequent Contributor II

Re: Controller IP for each VLAN

My thought is that you won't need them. I've had environments where there was a seperate Cisco L3 switch which handled all routing for all VLANs, however I still had a L3 address on the controller just for testing purposes. That way I could ping the controller for each VLAN just to verify connectivity.

Network Engineer | Airhead | Titus 3:5
Guru Elite

Re: Controller IP for each VLAN

Are you dealing with any multicast? (VOD, Vocera, etc)


Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Contributor I

Re: Controller IP for each VLAN

Nothing specific over wireless that I can think of.  perhaps some appletv crap?

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: