Controllerless Networks

Reply
Highlighted
Contributor I

Multi vlan on virtual controller

Hi all friends and experts,

This is the first time we are working with virtual controller, please let me know if im wrong and give me some ideas

We have
05 IAP 325
Vlan 100 : 192.168.1.0/24 for staff
Vlan 101 : 192.168.2.0/24 for guest
Vlan 103 : 192.168.3.0/24 for device management
SW cisco : 2960
External DHCP server
-----------------------------------
Physical topology
Eth0 AP 01 - fa0/10 : trunking, native vlan103, trunking allow all
Eth0 AP 02 - fa0/11 : access vlan 103
Eth0 AP 03 - fa0/12 : acess vlan 103
Eth0 AP 04 - fa0/13 : acess vlan 103
Eth0 AP 05 - fa0/14 : acess vlan 103
----------------------------------—---------
1. Only virtual controller (ap 01) must be trunk?
2. From ap 02 to 05 we need only config as access port ?
3. How to config trunk port on IAP ( ap 01 )
5. After ap 01 booted , it will become master and all ap going to discovery and auto join ?
6. I need only config ssid,,,,vlan provide, key.... on virtual controller ( master ap) after that all ap 02 to 05 wii syn this configurations form mater ?

Regards, and thank you so much
Lee Nguyen

Accepted Solutions
Highlighted
Guru Elite

Re: Multi vlan on virtual controller

7.  One of the other access points will take over and be the master.

 

8. The first AP that comes up is the master.  Every other AP that comes up locates the master on the same subnet via broadcast.  They join the master and download the entire configuration from the master.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba Technical Webinars

View solution in original post


All Replies
Highlighted
Guru Elite

Re: Multi vlan on virtual controller

1.  All access points need to be connected to a trunk

2.  All access points need to be connected to a trunk

3.  You do not configure a trunk port on the IAP side.  It will tag user traffic based on the VLAN configured in the SSID.

4.  Make sure that the untagged VLAN on each port is 103, so that IAPs can get an ip address from VLAN 103 (the management VLAN).

5.  Yes.

6.  Yes.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba Technical Webinars
Contributor I

Re: Multi vlan on virtual controller

Thank you for your information

Hi Colin, one more question:

7. If the virtual controller (ap 01) go down, so what is going on? All ap cannot working at time ?

8. If 01 is master, and 02 to 05 is ap client but it is different vlan, in this case ap client can auto discovery the master or we need manually config, acess to each ap and point ip of master ?

Thank you Colin and all friends
Highlighted
Guru Elite

Re: Multi vlan on virtual controller

7.  One of the other access points will take over and be the master.

 

8. The first AP that comes up is the master.  Every other AP that comes up locates the master on the same subnet via broadcast.  They join the master and download the entire configuration from the master.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba Technical Webinars

View solution in original post

Highlighted
Contributor I

Re: Multi vlan on virtual controller

Hi Colin,

 

Thank you so much!, thank you for your information, IAP is working fine.

Cheers,

Lee Nguyen

Highlighted
Occasional Contributor I

Re: Multi vlan on virtual controller

I know this is fourm is old but I am implemeting the same.

 

We currently bought license for Aruba Central and all configuration is done in Central. So, as you stated above that you do not need to config trunk on IAP port side under Access Point Port > Wired Port Profiles? 

What should the port profile for main wired connection to ethernet0/0 be then? Just plan access allow all?

Highlighted
Guru Elite

Re: Multi vlan on virtual controller

You do not need to configure a port profile.

 

By default, any management traffic will be untagged on the AP port.  Any user traffic on VLAN 1 with the "Network Assigned" designation, by default will be untagged.  Any user traffic on any other VLAN with the "Network Assigned" designation will be tagged on that VLAN.  No configuration of port profiles necessary.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba Technical Webinars
Highlighted
Occasional Contributor I

Re: Multi vlan on virtual controller

Thank you, I was able to fix my problem and got it working.

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