Wireless Access

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

adding 7030 controllers as managed device to mobility master fails

This thread has been viewed 3 times

  • 1.  adding 7030 controllers as managed device to mobility master fails

    Posted Aug 29, 2018 10:26 AM

    Hi,

     

    we want to add two 7030 in a remote location to our mobility master.

    MM is at 8.3.0.1, controllers were planned to remain at 8.2.1.1.

    Since we had difficulties we now have one 7030 at 8.2.1.1 and the other one at 8.3.0.1. This ensures, that version missmatch is not our problem.

     

    At the beginning we hat PSK missmatch for IPSec for MD to MM communication and fixed that.

    Now Tunnels are up (we see isakmp sa and ipsec sa).

    After connections show switches shows "Update Required". After a while that changes to "CONFIG ROLLBACK". Same is shown as alert in WebUI.

     

    Neither audit log in WebUI nor "show configuration failure" provide any output.

     

    "show switches" shows config ID of "0" for the two controllers. So they never syncronized any configurtion successfully.

     

    Any hints:

    - what else besides configuration missmatches can show this behaviour

    - how we could further debug this

     

    In parallel we are opening a TAC case...

     

    Kind Regards,

     

    Jörg



  • 2.  RE: adding 7030 controllers as managed device to mobility master fails

    EMPLOYEE
    Posted Aug 31, 2018 07:29 AM

    What is the connectivity between the 7030s and the MM?



  • 3.  RE: adding 7030 controllers as managed device to mobility master fails

    Posted Sep 03, 2018 03:43 AM

    Hi,

     

    its a layer 3 connection via MPLS circuits.

     

    Regards, Jörg



  • 4.  RE: adding 7030 controllers as managed device to mobility master fails
    Best Answer

    Posted Sep 03, 2018 03:47 AM

    Hi,

     

    problem is solved together with TAC.

    Seems like a config folder on MM got corrupted somehow.

     

    Solution was:

    - delete MD config of involved controllers

    - delete Folder

    - create new folder with different name

    - factory default the two 7030 controllers

    - add them to the new folder

    - rename folder to planned name

     

    Just deleting folder and recreating it with the same name did not work.

     

    Kudos go to TAC :-)

     

    Controllers are now running at 8.2.1.1 and MM at 8.3.0.1.

     

    Regards,

     

    Jörg