Workflow: redundant NFM-P shutdown and restart

Description

The following is the sequence of high-level actions required to stop and start the redundant NFM-P system components in a graceful manner for maintenance purposes.

Stages
Align redundancy roles
 

If the primary main server and database are in separate data centers, perform How do I perform a main database switchover using the NFM-P client GUI? to align the primary components in the primary data center.


Perform orderly shutdown of standby components
 

If the system includes NSP Flow Collectors:

  1. Stop each Flow Collector in the standby data center, as described in How do I start or stop an NSP Flow Collector?.

  2. Stop each Flow Collector Controller in the standby data center, as described in How do I start or stop an NSP Flow Collector Controller?.


If the system includes an auxiliary database, stop the auxiliary database cluster in the standby data center, as described in How do I stop an auxiliary database cluster?.


If the system includes one or more auxiliary servers, perform the following steps; see How do I stop an auxiliary server? for information.

  1. Stop each Reserved auxiliary server of the standby main server.

  2. Stop each Preferred auxiliary server of the standby main server.


Stop the standby main server, as described in How do I stop a main server?.


Stop the standby main database.

  1. Log in to the main database station as the root user.

  2. Open a console window.

  3. Enter the following to stop the Oracle proxy:

    systemctl stop nfmp-oracle-proxy.service ↵

  4. Enter the following to stop the main database:

    systemctl stop nfmp-main-db.service ↵


Perform maintenance on standby components
 

Perform the required maintenance on the NFM-P components in the standby data center.


Perform orderly startup of standby components
 

Start the standby main database.

  1. Log in to the main database station as the root user.

  2. Open a console window.

  3. Enter the following to start the Oracle proxy:

    systemctl start nfmp-oracle-proxy.service ↵

  4. Enter the following to start the main database:

    systemctl start nfmp-main-db.service ↵


Start the standby main server, as described in How do I start a main server?.


10 

If the system includes one or more auxiliary servers, perform the following steps; see How do I start an auxiliary server? for information.

  1. Start each Reserved auxiliary server of the standby main server.

  2. Start each Preferred auxiliary server of the standby main server.


11 

If the system includes one or more auxiliary servers, perform the following steps; see How do I start an auxiliary server? for information.

  1. Start each Preferred NFM-P auxiliary server of the standby main server.

  2. Start each Reserved NFM-P auxiliary server of the standby main server.


12 

If the system includes an auxiliary database, start the auxiliary database cluster in the standby data center, as described in How do I start an auxiliary database cluster?.


13 

If the NSP deployment includes NSP Flow Collectors:

  1. Start each Flow Collector Controller in the standby data center, as described in How do I start or stop an NSP Flow Collector Controller?.

  2. Start each Flow Collector in the standby data center, as described in How do I start or stop an NSP Flow Collector?.


Switch redundancy roles
 
14 

Perform a server activity switch to change the standby main server role to primary, as described in How do I perform a server activity switch?.

The standby main server assumes the primary role.


15 

If automatic database realignment is not enabled, perform a database switchover; perform How do I perform a main database switchover using the NFM-P client GUI? or How do I perform a main database switchover using a CLI script?.

The standby main database assumes the primary role.


Perform orderly shutdown of former primary components
 
16 

If the system includes NSP Flow Collectors:

  1. Stop each Flow Collector in the former primary data center, as described in How do I start or stop an NSP Flow Collector?.

  2. Stop each Flow Collector Controller in the former primary data center, as described in How do I start or stop an NSP Flow Collector Controller?.


17 

If the system includes an auxiliary database, stop the auxiliary database cluster in the former primary data center, as described in How do I stop an auxiliary database cluster?.


18 

If the system includes one or more auxiliary servers, perform the following steps; see How do I stop an auxiliary server? for information.

  1. Stop each Reserved auxiliary server of the former primary main server.

  2. Stop each Preferred auxiliary server of the former primary main server.


19 

Stop the former primary main server, as described in How do I stop a main server?.


20 

Stop the former primary main database.

  1. Log in to the main database station as the root user.

  2. Open a console window.

  3. Enter the following to stop the Oracle proxy:

    systemctl stop nfmp-oracle-proxy.service ↵

  4. Enter the following to stop the main database:

    systemctl stop nfmp-main-db.service ↵


Perform maintenance on former primary components
 
21 

Perform the required maintenance on the NFM-P components in the former primary data center.


Perform orderly startup of former primary components
 
22 

Start the former primary main database.

  1. Log in to the main database station as the root user.

  2. Open a console window.

  3. Enter the following to start the Oracle proxy:

    systemctl start nfmp-oracle-proxy.service ↵

  4. Enter the following to start the main database:

    systemctl start nfmp-main-db.service ↵


23 

Start the former primary main server, as described in How do I start a main server?.


24 

If the system includes one or more auxiliary servers, perform the following steps; see How do I start an auxiliary server? for information.

  1. Start each Reserved auxiliary server of the former primary main server.

  2. Start each Preferred auxiliary server of the former primary main server.


25 

If the system includes one or more auxiliary servers, perform the following steps; see How do I start an auxiliary server? for information.

  1. Start each Preferred NFM-P auxiliary server of the former primary main server.

  2. Start each Reserved NFM-P auxiliary server of the former primary main server.


26 

If the system includes an auxiliary database, start the auxiliary database cluster in the former primary data center, as described in How do I start an auxiliary database cluster?.


27 

If the NSP deployment includes NSP Flow Collectors:

  1. Start each Flow Collector Controller in the former primary data center, as described in How do I start or stop an NSP Flow Collector Controller?.

  2. Start each Flow Collector in the former primary data center, as described in How do I start or stop an NSP Flow Collector?.


Restore initial redundancy roles
 
28 

If required, restore the initial redundancy roles so that the former primary main server and database again assume the primary roles.

  1. Perform a server activity switch to restore the initial primary and standby main server roles, as described in How do I perform a server activity switch?.

    The former primary and standby main server roles are restored.


29 

If automatic database realignment is not enabled, perform a database switchover; perform How do I perform a main database switchover using the NFM-P client GUI? or How do I perform a main database switchover using a CLI script?.

The former primary and standby main database roles are restored.