Wireless Access

 View Only

  • 1.  Aruba Controller hierarchy nodes not updating from MM

    Posted 18 days ago
    Edited by JW-d1e947 18 days ago

    Hello,

    I have an open TAC case but hoping someone has an idea of why some of my controllers (4 out of 7) are not updating the PSK of an SSID we have across all controllers when I update from the top level node on the conductor.

    I have checked and the profile is the same on all the controllers.  TAC suggested updating to 8.10.0.23 from 8.10.0.19 but same issue.  

    Anything I should be checking please.

    Thanks in advance.



  • 2.  RE: Aruba Controller hierarchy nodes not updating from MM

    Posted 18 days ago

    Three of seven taking the change points at a wpa-passphrase set lower in the hierarchy, and the upgrade changing nothing fits that. The PSK is a single-instance setting, so a value at a group or device node beats /md even when the profile name matches everywhere. The Understanding Configuration Hierarchy page covers that override rule: https://arubanetworking.hpe.com/techdocs/ArubaOS/AOS_8x_WebHelp/Content/arubaos-solutions/config-hierarchy/unde-conf-hier.htm

    On the conductor, run show configuration committed <node-path> for each node between /md and one of the failing MDs, its own device node included, and look for a wpa-passphrase line in that ssid-profile. It's encrypted, so you're looking for the line, not the value. Delete it there and the /md value flows down.

    If nothing's overriding it, compare Configuration State and Config ID for the 4 against the 3 in show switches (command reference: https://arubanetworking.hpe.com/techdocs/CLI-Bank/Content/aos8/sh-switches.htm) and check show configuration failure.



    ------------------------------
    Dustin Burns
    @Worldcom Exchange, Inc.
    www.wei.com

    - - -
    The comments I post here are my own, and not my employers
    If my post was useful accept solution and/or give kudos
    Personal Blog: www.networkfieldnotes.com
    - - -
    ------------------------------



  • 3.  RE: Aruba Controller hierarchy nodes not updating from MM

    Posted 9 days ago

    JW, did any node between /md and the failing MDs turn up its own wpa-passphrase line? If not, check whether the 4 show an older Config ID than the 3 in show switches, since that means they aren't taking commits at all. If deleting it sorted things, marking the fix helps the next person who hits this.



    ------------------------------
    Dustin Burns
    @Worldcom Exchange, Inc.
    www.wei.com

    - - -
    The comments I post here are my own, and not my employers
    If my post was useful accept solution and/or give kudos
    Personal Blog: www.networkfieldnotes.com
    - - -
    ------------------------------



  • 4.  RE: Aruba Controller hierarchy nodes not updating from MM

    Posted 9 days ago

    Hello Dustin, 

    When I run the command show configuration committed /md from the MM I do indeed see the SSID listed with the wpa-passphrase in cyphertext. 

    What commands do I run to delete this please?


    Original Message


  • 5.  RE: Aruba Controller hierarchy nodes not updating from MM

    Posted 9 days ago

    Hey Jonathan,

    On your controllers with the wrong PSK, look at `show configuration effective detail` to see where in the hierarchy the passphrase is coming from.

    Also check `show switches` on the MCr to confirm the configuration is synced.

    If this is a sync issue, you may need to make some arbitrary change to force a config push.


    Original Message


  • 6.  RE: Aruba Controller hierarchy nodes not updating from MM

    Posted 9 days ago

    Don't delete that one. /md is the node you push from, so the wpa-passphrase line there is the value you want flowing down. The override, if there is one, sits below it: a group node or a failing controller's own device node. On the conductor, show configuration devices gives each controller's node path; change-config-node to a failing one and run show configuration effective detail, which tags each line with the node it came from (the show configuration reference covers the forms: https://arubanetworking.hpe.com/techdocs/CLI-Bank/Content/aos8/sh-conf.htm). A passphrase sourced from anything but /md is your culprit.

    Clearing it at that node: wlan ssid-profile "<name>", no wpa-passphrase, exit, write memory (the change-config-node reference shows the node-path form: https://arubanetworking.hpe.com/techdocs/CLI-Bank/Content/aos8/change-conf-node.htm). The /md value takes over on the next push. Repeat for each of the four.

    If every line reads /md, it isn't an override but a sync problem, which is where JS's Config ID check in show switches and show configuration failure come in.



    ------------------------------
    Dustin Burns
    @Worldcom Exchange, Inc.
    www.wei.com

    - - -
    The comments I post here are my own, and not my employers
    If my post was useful accept solution and/or give kudos
    Personal Blog: www.networkfieldnotes.com
    - - -
    ------------------------------

    Original Message


Related Content