Security

 View Only
last person joined: 17 hours ago 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

Cluster join stuck at "Restore local node config failed."

This thread has been viewed 14 times

  • 1.  Cluster join stuck at "Restore local node config failed."

    Posted 5 days ago

    Clearpass Cluster join stuck at "Restore local node config failed."

    Looks like the same as here: Airheads Community but down-sizing the MTU on both ends does not help.

    Trying with 6.12.0 and 6.12.2 - Joining from different sites. (Same Subnet -> no issue)



  • 2.  RE: Cluster join stuck at "Restore local node config failed."

    Posted 5 days ago

    Hi

    I have not run into this issue, but on the other hand we run all customers on 6.11. Just using 6.12 on some lab servers so far.

    In your case I would open a TAC case to get help in the troubleshooting.



    ------------------------------
    Best Regards
    Jonas Hammarbäck
    MVP Guru 2024, ACEX, ACDX #1600, ACCX #1335, ACX-Network Security, Aruba SME, ACMP, ACSA
    Aranya AB
    If you find my answer useful, consider giving kudos and/or mark as solution
    ------------------------------

    Original Message


  • 3.  RE: Cluster join stuck at "Restore local node config failed."

    Posted 5 days ago

    Okay - this does not help me out in any way...


    Original Message


  • 4.  RE: Cluster join stuck at "Restore local node config failed."

    Posted 2 days ago

    I ran into this same issue while migrating to 6.11 from 6.10. Found out I had to make sure within clusterwide parameters > standby publisher tab > Enable Publisher Failover =FALSE before taking the backup.


    Original Message


  • 5.  RE: Cluster join stuck at "Restore local node config failed."

    Posted 4 hours ago

    Okay - indeed i had a standby publisher before. 

    Disabled that but still no luck.

    In the meantime i resetted the database on both ends (as this is not in production yet) - still no change.

    So at the moment I point it as network issue!? But how could I be sure?


    Original Message