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.
Back to discussions
Expand all | Collapse all

Inteherited vs local configurations on MC's

This thread has been viewed 0 times

  • 1.  Inteherited vs local configurations on MC's

    Posted Oct 18, 2019 06:24 PM

    I have 2 MC's that have a mixed configuration.

     

    Most of the configuraiton is inherited from the /MD/xx node-hierarchy.

     

    Some is configured locally.

     

    Is there an easy way to strategically restore the inheritance for a few things for example "wlan ssid-profile" or "wlan virtual-ap"?

     

     



  • 2.  RE: Inteherited vs local configurations on MC's
    Best Answer

    EMPLOYEE
    Posted Oct 18, 2019 07:16 PM

    Type "show configuration node-hierarchy"

    type "CD <name of your node>"

    If you type "show configuration committed" at that level, it will tell you everything you have configured only at that node.



  • 3.  RE: Inteherited vs local configurations on MC's

    Posted Oct 19, 2019 01:52 AM

    Thank you... that helped remove some of those changes on the individual controller.

     

    Should NTP settings be set in the /md/controller and inherited down at the actual MC?  or actually set on the MC?



  • 4.  RE: Inteherited vs local configurations on MC's

    EMPLOYEE
    Posted Oct 19, 2019 04:57 AM

    If all controllers need to have the same ntp server, it can be created as high up as /md.



  • 5.  RE: Inteherited vs local configurations on MC's

    Posted Oct 22, 2019 08:03 PM

    As Cjoseph stated, settings such as NTP can be set as high up as /md, however it is generally recommended that you do not make changes at the /md level. Create an organizational group node below /md and make your global settings at that level. Such as /md/<company name>/<location>/ and then in the location group node you would then have your device nodes. Your global settings would be made at /md/<company name>. With a Mobility Master (MM) you can have a maximum hierarchy depth of 4 group node levels, eg. /md/level1/level2/level3/level4/devicenode.

     

    I hope this helps,