Wireless Access

 View Only
last person joined: yesterday 

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

2 questions about configuration view of Aruba WLC

This thread has been viewed 12 times
  • 1.  2 questions about configuration view of Aruba WLC

    MVP
    Posted Oct 21, 2021 03:04 AM
    1) how to see which configuration is applied on each level towards local WLCs, e.g. we have such hierarchy:

    region
      |
    site
      |
    local WLC

    which command will show configuration part which pushed from site/region level and which is configured locally on WLC

    2) when WLC or guest anchor first connects towards MM, which command will show which configuration is pushed from MM towards local WLC ? This question comes from bug/problem when local WLC with basic config connects to MM, MM pushes wrong config to it (e.g. wrong interfaces and etherchannel settings) and local WLC loses connection.


  • 2.  RE: 2 questions about configuration view of Aruba WLC
    Best Answer

    EMPLOYEE
    Posted Oct 21, 2021 07:46 AM
    1. At any level in the MM, "show configuration effective" will show the configuration that a node at that level will receive.  Use "cd" to navigate and then the command to see the effective configuration.  Use "show configuration node-hierarchy" to see all the folders you have created.

    Quite frankly very few organizations need many folders deep.  ap-groups will satisfy most organizations just fine.

    2.  On the WLC, "show running-configuration" will show what is on that WLC.  When an MM sends a configuration to a WLC that disconnects the WLC, the WLC will attempt to "roll back" the last change that has been made.  That is your opportunity to revert the last change on the MM so that when the WLC connects back, it will not again download the faulty configuration.



     


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