Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Recommended starting and stopping sequences for NSM services

0

0

Article ID: KB11263 KB Last Updated: 14 Oct 2016Version: 8.0
Summary:

This article discusses the recommended starting and stopping sequences for NSM services in standalone and high-availability configurations.

Solution:

Note: JTAC recommendation is to stop processes, then start them. Using the "restart" command should be avoided.  


Standalone NSM Configuration

Recommended startup sequence for NSM services:

  1. Start the GUI server:

    /etc/init.d/guiSvr start  
    OR
    service guiSvr start

  2. Start the device server:

    /etc/init.d/devSvr start
    OR
    service devSvr start

  3. Start the HA server:

    /etc/init.d/haSvr start
    OR
    service haSvr start

Recommended stopping sequence for NSM services:

  1. Stop the HA server:

    /etc/init.d/haSvr stop
    OR
    service haSvr stop

  2. Stop the device server:

    /etc/init.d/devSvr stop
    OR
    service devSvr stop

  3. Stop the GUI server:

    /etc/init.d/guiSvr stop
    OR
    service guiSvr stop


High-Availability NSM Configuration

Recommended startup sequence for NSM services

  1. Start the HA server:  (Desired Active server first, then Desired Standby server.)

    /etc/init.d/haSvr start

Recommended stopping sequence for NSM services

  1. Be sure you know which GuiSvr server is active.

    • Option 1: 

        GuiSvr

            Look at:   /etc/init.d/guiSvr status   or  service guiSvr status

            The Active guiSvr will list all processes as on, Standby only lists guiSvrManager as on.
        
         DevSvr:

              /etc/init.d/devSvr status  or  service devSvr status

              The Active devSvr will list all processes as on, Standby will list all processes as off.

    • Option 2: 

          /usr/netscreen/HaSvr/utils/haStatus

               The output will list the status or the local and remote servers.

  2. Notice if the DB is currently synchronized (guiSvr only).

              From the client: Select Administer, Server manager > server monitor > last GuiSvr replication (bottom right).  If in-sync, it will list the current time.
             
              From the CLI: /usr/netscreen/HaSvr/utils/haStatus

                       DB status shows "in-sync".
  3. Stop the HA server. (Make sure you are stopping the Standby first, then Active to prevent data loss or corruption.)

               /etc/init.d/haSvr stop

Extended-HA Note:  DevSvr HA Pair and GuiSvr HA Pair work with each other (Gui/Dev don't interact for HA start/stop operations).  Recommended Stop process: Standby servers, (order doesn't matter), Active Servers (DevSvr, then GuiSvr is preferred, but not critical).  Use the steps above to determine Active/Standby, and database sync status.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search