Release Automation

Expand all | Collapse all

other NAC is currently becoming master

Jump to Best Answer
  • 1.  other NAC is currently becoming master

    Broadcom Employee
    Posted 07-31-2014 11:14 AM

    Hi all!

     

    I have a problem using Release Automation 5.

    In some moments when using the ROC, the server returns the message: http status 500 - Request Rejected: Other NAC is currently becoming Master.

    Follow the print:

    print.png

    I'm using 2 servers for Management Server. Never had this error until the second machine was installed.

     

    Anyone can help me?

     

    Thanks,

    Francis



  • 2.  Re: other NAC is currently becoming master
    Best Answer

    Broadcom Employee
    Posted 07-31-2014 11:54 AM

    Hi,

     

       When you have two NAC's you need to make sure that only one NAC is being actively used, so all ROC and ASAP UI's should be connecting to the active node only, if a ROC or ASAP UI session is connected to the secondary node this will cause the Master node to switch. We recommend setting up a VIP that can be used by all users and this VIP is directed to one of the nodes and in the event of a issue with this node you can redirect traffic to the secondary node.

     

        Hope this helps

    Keith



  • 3.  Re: other NAC is currently becoming master

    Broadcom Employee
    Posted 08-04-2014 09:42 AM

    Hi Keith!

     

    Thanks for your answer, you helped me a lot! Now It's clear for me how the Management Servers works. Just for high availability not for load balance.

     

    Do you now how I configure that in BIGIP?

     

    Regards,

    Francis