Wireless Access

 View Only
last person joined: 20 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Vlan configuration on 7210 Controller

This thread has been viewed 19 times
  • 1.  Vlan configuration on 7210 Controller

    Posted Feb 21, 2018 10:30 PM

    Hi community,


    On my company we are deploying a wireless network, working with AP 335, 7210 Controllers, 3810M and 5406 SW and a Virtual Mobility Master.


    The controllers are in md mode, managed by the Mobilty Master. 


    On site A,B,C we have the following scenario:


    7210 Controller: LACP port (G0/0/0-1 port members) native vlan 1, allowed vlans: 3387 and any other vlan required.

    On the switches side we have an LACP with this config:

    untagged vlan 1

    tagged vlan 3387, x, x, x


    So for example, if we need a new ssid and that ssid is based on vlan 10 then we add that vlan to LACP ports on both sites (controllers and switches)


    Everything works well with the config mentioned. 


    On site Z we have the following scenario:


    The site has an existing network all in vlan 1, an SSID assigned to vlan 1.

    The controller is in vlan 2 and we also have the vlan 3387. 


    What we want to do is to replace the existing APs with our 335 APs and broadcast two SSIDs: one based on vlan 1 and another based on vlan 3387. 


    The problem occurs when we start the controller configuration using the full dialog throug the console. If we put the vlan 2 as native vlan the controller appears on the Mobility Master for a couple of minutes but after that the controller goes down and we cannot reach it anymore (if we issue a ping for example). 


    So we have left the vlan 1 by default and everything works well. But when we create a Wlan assigned to vlan 1 and the clients connects to it, they receive vlan 2 IPs. 


    The configuration on the switch is:

    LACP port 

    tagged vlan 1,3387

    untagged vlan 2



    LACP port 

    tagged vlan 2,3387

    untagged vlan 1 (native)

    It seems like a wrong configuration but actually it works.

    If we config the controller with:

    tagged vlan 1,3387

    untagged vlan 2 (native) it goes down and then we lose the controller from the mobility master.


    So the question is how can we get the controller works with vlan 2 as native and vlan 1,3387 for ssids. 


    Sorry for the extended message. 

    Thank you in advance. 





  • 2.  RE: Vlan configuration on 7210 Controller

    Posted Feb 22, 2018 05:03 AM

    Have you set the controller's management VLAN like this:

    <Assuming you are in the MD's context>

    config t

    controller-ip vlan 2

  • 3.  RE: Vlan configuration on 7210 Controller

    Posted Feb 26, 2018 12:21 PM

    Hi cjoseph thanks.


    Im gonna try that as soon as possible because the controller physically far from our company. 

    I think we have to turn on disaster mode right?