Cloud Managed Networks

 View Only
last person joined: 2 days ago 

Forum to discuss all things related to HPE Aruba Networking Central and UXI Network Management, including deployment of managed networks, configuration, best practices, APIs, Cloud Guest, AIOps, Presence Analytics, and other included Applications

Aruba Central Essential Features - Groups

This thread has been viewed 74 times
  • 1.  Aruba Central Essential Features - Groups

    Posted Jan 10, 2023 03:27 PM


    A Group in Aruba Central is the primary configuration element that functions as a container for device management, monitoring, and maintenance.

    Groups enable administrators to manage devices efficiently by using either a UI-based configuration workflow or CLI-based configuration template.

    Groups provide the following functions and benefits:

        • Ability to provision different types of devices in a group. For example, a group can consist of Instant APs, Gateways, and Switches.
        • Ability to create a configuration base and add devices as necessary. When you assign a new device to a group, it inherits the configuration that is currently applied to the group.
        • Ability to create a clone of an existing group. If you want to build a new group based on an existing group, you can create a clone of the group and customize it as per your network requirements.


    A device can be part of only one group at any given time.
    Groups in Aruba Central are mutually exclusive (independent) and do not follow a hierarchical model.
    There are two special groups in Aruba central:  default and unprovisioned

        • Default group: A system-defined group to which Aruba Central assigns all new devices with factory default configuration. When a new device with factory default configuration connects to Aruba Central, it is automatically added to the default group.
        • Unprovisioned group: Devices that have a customized configuration when connecting to Aruba Central will be marked as Unprovisioned. To preserve the device configuration, create a new group and assign this device to the newly created group. To overwrite the configuration, move the unprovisioned device to an existing group

    Achievable IT and Business Outcomes

      • Groups will reduce the time and effort required by IT teams during deployment and provisioning of AP, switches and gateways 
      • Accelerate time to value with zero touch provisioning
      • Provide increased operational efficiency by simplifying and automating device onboarding and configuration workflows


    • Understand how ArubaOS 10 and ArubaOS 8 architecture differences affect desired outcomes
    • Refer to the Validated Solution Guides for more design and deployment best practices
    • Enlist support from Aruba SE for Aruba AOS10 architecture deployment
    • Plan for ArubaOS 10 before deployment
    • Ask Aruba Sales Team (TM and SE) for help
    • ArubaOS 10 Resources to help you:
      • Central help article about ArubaOS 10: Click here
      • Campus WLAN architecture - ArubaOS 10: Click here
      • Campus WLAN deployment - ArubaOS 10: Click here
      • List of currently supported devices on ArubaOS 10: Click here.

    Groups: Hardware, architecture and network roles
    Groups HW, architecture and network roles

     Aruba has recently released a new WLAN architecture named Aruba AOS 10.

     It introduces a major architectural change that utilizes Aruba Central for operation and management of Aruba Access Points (APs) and Gateways.

     What are the main differences between ArubaOS 10 and ArubaOS 8?

    • Under ArubaOS 8, the wireless solution must be deployed in one of the two modes:
      • Controller-based for campus – CAP
      • Controller-less for branches and remote worker – IAP and RAP
    • Under ArubaOS 10, the wireless solution is unified into one single software architecture for campus, branch, and remote, delivering these benefits:
      • Now you can deploy any AP anywhere, manage it all the same way and from the same location.
      • We've eliminated the need for on-premises based controllers, even for campus deployments.
      • No more complexity, no more silos, and fewer tools with the same management experience means reduced IT training and support costs.

     Consider these differences in architecture, when designing and deploying Aruba WLAN to maximize your ROI


     Microbranch network role
    For small branch deployments, Aruba offers an Instant AP-based SD-WAN solution, where the AP acts as gateway for remote access in addition to providing wireless connectivity
     Campus / Branch network role
    A typical campus network encompasses a set of buildings in close proximity with a large number of Wi-Fi-connected clients and applications deployed in public, private, and hybrid clouds

    A branch network is generally an offshoot of the campus network with a small area of operation. A branch network also typically leverages a full stack networking solution combining both LAN and WAN in a single box

    How to create Groups?
    This  video shows how to create Groups in Aruba Central

    Aruba Customer Success Team