Wireless Access

 View Only
last person joined: 2 days ago 

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

Issues when converting from virtual controller to physical standalone mobility controller 7210

This thread has been viewed 21 times
  • 1.  Issues when converting from virtual controller to physical standalone mobility controller 7210

    Posted 26 days ago
    Hi,

    Thanks in advance for any assistance,

    We used to have IAPs running on virtual controller (mixed aps; i.e. 205, 505, etc..) and all had uplink vlan configured to 2 and the the switches' ports were configured to tagged on the SSIDs vlans and untagged on vlan 2. Everything was working excellent.

    We installed a new standalone controller 7210 and configured its interface GE 0/0/0 (the one connected to the network) as trunk with access vlan 2 (same as aps vlan and management vlan of the controller).
    We then converted all iap to campus aps and pointed to the IP of the new controller.

    We then configured all migrated APs' switches' ports to only access (untagged) on vlan 2 (removed tagged vlans of the SSIDs from the ports).

    We have only the LIC-AP installed, no PEF no other LICs on the new controller.

    We have configured the SSIDs as tunnel mode and link the required vlans to it.

    Ever since the wireless network is very unstable (sometimes too much timeouts on the APs, drops when pinging 8.8.8.8, etc..)

    we tried many scenarios, as switching the SSIDs to bridge mode, leaving APs' switches port as tagged and controller's switch port as untagged, etc.. and nothing worked.

    We are using AOS 8.6.

    Any suggestions please,

    Appreciated


  • 2.  RE: Issues when converting from virtual controller to physical standalone mobility controller 7210

    MVP EXPERT
    Posted 26 days ago
    Hi Devandroid,

    Based on your description this could have many causes. Because it's a new setup it's most likely a misconfiguration somewhere.

    • Did you install latest conservative firmware release ?
    • Is it a wireless or ethernet issue ?
    • Is there a wireless design ?
    • What are the radio settings?
    • If you like share the "show configuration effective" output to get known your configuration.

    For fast solving your issue please call Aruba TAC support to assist you find the root cause.

    ------------------------------
    Marcel Koedijk | MVP Expert 2022 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
    ------------------------------



  • 3.  RE: Issues when converting from virtual controller to physical standalone mobility controller 7210

    Posted 26 days ago
    Thanks @mkk,

    Honestly we do not have a valid support contract, that's why I am here to get assistance.

    Regards.​​


  • 4.  RE: Issues when converting from virtual controller to physical standalone mobility controller 7210

    EMPLOYEE
    Posted 25 days ago
    Can you have a look at the controller log (show log all 300  ... where 300 is the last 300 lines). Do you maybe see your APs 'bouncing'?
    What is the output of 'show ap active' and 'show ap database'? Are your APs 'stable' connected to the controller?
    Can you check all of the switch ports for errors?
    Could it be that you created a network loop?
    Note that the controller has spanning tree (the original one, not per VLAN), which may result into ports getting blocked where they shouldn't? If you plug in two ports of a controller in the same switch, you may see spanning tree hitting in even if the ports have no VLANs in common.

    Running the SSID in tunneled mode, and have the client VLANs only at the controller, should give the best stability.

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------