Wireless Access

last person joined: 18 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

Issues while Deploy Mobility Controller as Standalone

This thread has been viewed 1 times
  • 1.  Issues while Deploy Mobility Controller as Standalone

    Posted Nov 01, 2019 08:57 PM

    Hi Guys
    During my test before deployment I have some question :
    Q1- how i can assign interface to act as wan
    Q2- if i have two wan interface ex(WAN1, WAN2) , how i can forward specific traffic to WAN1 and rest of traffic to WAN2
    Q3- I have outdoor AP has been assigned to ap group but not broadcasting any signal , on the other hand i have another indoor AP in the same group and broadcasting signal normally, so how i can solve this issue ?
    Q4- I have ssid (XZ) assigned to Vlan (X1) DHCP has been created to this vlan , user can connect to xz and pull ip from vlanx1 but with no internet , i had configured ip default gateway for the controller probably but still the same issue , rule has been assigned with any any permit , so is there is any something missing ?
    Q5- can i access campus AP through managment IP ?
    Q6- i would like some one to explain briefly the hierarchy for assigning rules for specific SSID

    Thanks Guys for all your assistances



  • 2.  RE: Issues while Deploy Mobility Controller as Standalone
    Best Answer

    EMPLOYEE
    Posted Nov 04, 2019 04:26 AM

    That is a lot of questions, and you probably should consult your Aruba partner or local Aruba SE to get the better answers for your specific situation.

     

    A1: there is no concept of WAN interface on standalone controllers. You can put any interface in any VLAN and do routing and/or NAT on the VLAN interface to achieve 'WAN interface' functionality.

    A2: You can do this with policy based routing. With Aruba SD-Branch, it is much easier to set such things up.

    A3: What is likely is that you may have limited the allowed channels that ARM can pick from to a set that does not include the channels that are allowed for outdoor operations. Or if you have an AP with external antennas and not configured the antenna parameters. Quickest is to consult an Aruba partner or Aruba Support to find out what is happening.

    A4: You probably have a routing issue (if NAT is done outside your controller) or not configured NAT on the outgoing traffic.

    A5: Yes, if you enabled telnet in the AP System profile, but there is not so much to see/do on a campus AP as it just tunnels to the controller.

    A6: This is covered in training and the product documentation. That is not brief but I'd advise you to either have it set up for you by an experienced engineer or invest in training and learning how the system works which may not be a brief exercise. Without good understanding there is a significant risk of misconfiguration which may lead to insecure or poor performing implementations.



  • 3.  RE: Issues while Deploy Mobility Controller as Standalone

    Posted Nov 06, 2019 05:56 PM

    Thanks