Wireless Access

 View Only
last person joined: 6 hours ago 

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

7005 controller standalone config copy when moved to Mobility Conductor

This thread has been viewed 8 times
  • 1.  7005 controller standalone config copy when moved to Mobility Conductor

    Posted May 05, 2022 01:54 PM
    Folks,

    I've got a 7005 controller with an AP using 8.6.0.11. I've install two virtual Mobility Conductors that are working in L3 redundancy.

    I am clear how to factory default it and join the vMCs, but that controller, as a stand alone, has a number of SSIDs, Clearpass roles, AAA, SNMP, SSH, etc. settings. 

    I've backed up the config and moved it offline, as well as leaving a copy on the controller.

    Now, the question, is there an easy to load the config, say that items such as SNMP, AAA, DNS, etc. are attached to the vMC group for all the 7005's I have (like 50), and put other configs - such as VLAN L3 addresses, DHCP zone configs, etc.?

    Or do I need to copy and  paste from a text text file?  Or GUI them all in separately? Both options are painful. Especially in that, if we get most of the common settings under the group, each of the 50+ controllers we move will need 10-15 separate CLI entries which are specific to each controller.

    If you know of any docs or videos on Aruba or on the 'net, please let me know.

    Thanks,

    -Ambi


    ------------------------------
    Ambidexter
    ------------------------------


  • 2.  RE: 7005 controller standalone config copy when moved to Mobility Conductor

    EMPLOYEE
    Posted May 05, 2022 05:31 PM
    Please see the ArubaOS Fundamentals Guide here:  https://community.arubanetworks.com/blogs/archive-user1/2020/10/19/arubaos-8-fundamentals-guide

    Also, take a look at the Airheads Broadcasting Youtube Channel for videos.

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
    ------------------------------