We'd like to extend central vlans to branch offices in the same manner as RAP. Does anyone know how to get this done using a branch office controller instead? About 20 site APs, no local services available.
What kind of controllers do you have at Branch and at HQ?
What version of ArubaOS, and is there a Mobility Master?
If you don't already have a controller...did you know that you can achieve this with IAP also?
Hi!
What´s your use case for extending central VLANs out to the branches? Alot of the benefits with a branch-office controller comes when you use the local subnets and the controller as the default gateway. I´d only extend vlans centrally for very specific use cases.
If you still want to extend VLANs you might take a look at creating GRE tunnels.
Cheers,
Our "branch" office look more like offsite locations. We have dedicated vlans for UPS, cameras, security devices, etc. It's useful to have remote sites look like "campus" to clients. -- Jim
You can get everything to look and work like your main campus using local VLANs and L3-routing instead of extending VLANs. Only difference would be that you´ll end up in another IP subnet on each remote location. Segmenting different types of devices could be done via user-roles instead of dedicated VLANs.
Do you guys have Clearpass?
We do not have Clearpass. I can get the wireless part working using local subnets. We have several vlans that would convenient to extend -- switch management, UPS, cameras, etc. I can do one of these using a L2 tunnel with source and destination address of the controllers. It seems I could do another using a destination IP address on the master controller but doesn't seem to work. Branch 7030 to 7210 master. Also tried source as vlan #. I'm sure I'm missing something major. Steps? Thanks!
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.