Knowledge Center Search


 

Why Does the Secondary HA Server Not Fail Over When the Primary Server Becomes Available?

  [KB4909] Show KB Properties

  [KB4909] Hide KB Properties

Categories:
Knowledge Base ID: KB4909
Last Updated: 25 May 2010
Version: 6.0

Summary:
The Secondary server will not automatically fail over when the Primary server becomes available. The failover must be performed manually.

Problem or Goal:

Solution:

To force the Secondary HA server to fail over to the Primary server, perform the following steps:

  1. Ensure there are no users connected to the server. This can be viewed by executing netstat -an | grep 7801 on the Active GUI Server

  2. Log in to the Secondary NSM server via SSH as the root user and perform an manual replication
    /usr/netscreen/HaSvr/utils/replicateDb ha

  3. Execute the following command:
    /etc/init.d/haSvr stop

  4. Login to the Primary server via SSH as the root user and execute the below command:
    /etc/init.d/haSvr start

note: If the Secondary NSM server has the GUI server and Device server installed on two different systems, repeat Step 1 through Step 4 on both the GUI server and Device server.

Once the above steps are completed, the Primary server will be active and secondary will be shutdown. To start the Secondary server in the backup mode, login via SSH and execute the below command:

/etc/init.d/haSvr start

note: Login via the NSM GUI and verify that the Primary NSM server is Active and Secondary NSM server is in the stand-by mode.

Purpose:
Configuration

Related Links:

 

 

ASK THE KB

Question or KB ID:


 


 

 
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.