Wireless Access

last person joined: 22 hours ago 

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

Mobility Master - Configuration at Managed Network Node

This thread has been viewed 4 times
  • 1.  Mobility Master - Configuration at Managed Network Node

    Posted May 28, 2020 11:11 PM

    Hello Airheads,

     

    If you have a mobility master with configuration and the controllers at the managed network node, is there anyway to copy this configuration to a group and remove all managed network node configuration to follow best practice?

     

    Regards

     



  • 2.  RE: Mobility Master - Configuration at Managed Network Node

    EMPLOYEE
    Posted May 29, 2020 04:56 AM

    I have not found a neat way to move configuration from a higher point in the hierarchy to a lower point.

     

    That is also why all guidelines tell you not to do any configuration on the /md/ level.

     

    You will need to remove a lot of related/dependent configuration from the higher level, then you can re-enter it on the lower level. In practice, I ended up in a few cases by replicating configuration with different names on the lower level and once configuration elements are no longer used on /md/ you can remove it there.

     



  • 3.  RE: Mobility Master - Configuration at Managed Network Node

    Posted May 29, 2020 09:14 AM

    Thanks Herman, is there an easy way to output all the configuration at the /md node in the command line?

     

    Regards

    Chris



  • 4.  RE: Mobility Master - Configuration at Managed Network Node

    EMPLOYEE
    Posted May 29, 2020 09:23 AM
    cd /md
    show configuration committed

    ... should do that.



  • 5.  RE: Mobility Master - Configuration at Managed Network Node

    Posted Jun 16, 2020 11:09 PM

    As Herman stated "show configuration committed", performed at a specific node level will show the commands that were specifically entered at that node. If you want to see the configuration that exists at a specific node, which include the settings at the specific node, along with any configuration that has been inherited from node levels above, then the command is "show configuration effective". If you want to identify where the configuration was inherited from, then the command is "show configuration effective detail". This will show each configuration command, and to the right of it, you will see the node level where the command was set/inherited from. Below is a small clip from the command.

     

    (MM1) [mynode] #show configuration effective detail
    crypto-local pki PublicCert master-ssh-pub-cert master-ssh-pub-cert # inherited from [/]


    master-l3redundancy # local [/mm/mynode]

     

    l3-peer-ip-address 192.168.240.100 ipsec ****** # local [/mm/mynode]

     

    l3-sync-state Primary # local [/mm/mynode]

     

    l3-sync-time 2 # local [/mm/mynode]

     

    I hope this helps,