Workflow to upgrade a redundant Release 22.9 or later NFM-P system

Description

The following is the sequence of high-level actions required to upgrade a redundant NFM-P system at Release 22.9 or later.

Stages

Note: The Upgrade redundant system links lead to sections in To upgrade a redundant Release 22.9 or later NFM-P system.

Prepare system for upgrade
 

Perform To prepare for an NFM-P system upgrade from Release 22.9 or later.


Upgrade redundant system
 

Check the available disk space; see Check pre-upgrade disk space.


Stop and disable the standby main server; see Stop and disable standby main server [Main2].


If the system includes auxiliary servers, stop the [Aux2] auxiliary servers; see Stop auxiliary servers [Aux2].


Disable the system redundancy functions; see Disable database redundancy.


Upgrade the standby main database, which becomes the new primary main database; see Upgrade standby main database [DB2].

  1. Stop the main database.

  2. Run a script on the database station to prepare for the Oracle software installation.

  3. Install the database packages.

  4. Run the database upgrade script.

  5. Verify and modify the database configuration, as required.


Upgrade the standby main server; see Upgrade standby main server [Main2].


Start the PKI server; see Start PKI server.


Configure the new primary main server; see Configure new primary main server [Main2].


10 

If the NFM-P is not in a shared-mode NSP deployment, restore the local NSP databases on the new primary main server; see Restore embedded nspOS, independent deployment.


11 

If required, enable Windows Active Directory for client access; see Enable Windows Active Directory access.


12 

If required, configure ADFS to enable Common Access Card, or CAC, client access; see Enable CAC access.


13 

If the NFM-P is integrated with an WS-NOC system, configure the integration; see Configure WS-NOC integration.


14 

If the NFM-P system includes one or more NSP analytics servers or Flow Collectors, stop each; see Stop NSP analytics servers, NSP Flow Collectors.


15 

If the NFM-P system includes auxiliary servers, upgrade the [Aux2] auxiliary servers; see Upgrade auxiliary servers [Aux2].


16 

If the system includes redundant auxiliary database clusters, verify the most recent data synchronization; see Verify auxiliary database synchronization.


17 

If the system includes redundant auxiliary database clusters, enable cluster maintenance mode; see Enable maintenance mode on auxiliary database agent.


18 

If the system includes redundant auxiliary database clusters, upgrade the standby cluster; see Upgrade standby auxiliary database cluster.


19 

Stop and disable the original primary main server; see Stop and disable original primary main server [Main1].

Note: This stage marks the beginning of the network management outage.


20 

If the system includes one or more NSP Flow Collectors, upgrade each NSP Flow Collector Controller and Flow Collector; see Upgrade NSP Flow Collector Controllers, Flow Collectors.


21 

If the NFM-P system includes auxiliary servers, stop the [Aux1] auxiliary servers; see Stop auxiliary servers [Aux1].


22 

Stop the original primary main database; see Stop original primary main database [DB1].


23 

If the system includes a standalone auxiliary database cluster, upgrade the cluster; see Upgrade auxiliary database, if not redundant.


24 

If the system includes redundant auxiliary database clusters, enable maintenance mode for the former primary cluster; see Enable maintenance mode for auxiliary database agent.


25 

If the system includes redundant auxiliary database clusters, stop the former primary cluster; see Stop former primary auxiliary database cluster.


26 

Start the new primary main server; see Start new primary main server [Main2].


27 

If the system includes auxiliary servers, start the [Aux2] auxiliary servers; see Start auxiliary servers [Aux2].


28 

If the system includes redundant auxiliary database clusters, activate the upgraded former standby cluster, see Activate upgraded former standby auxiliary database cluster.


29 

If the system includes one or more NSP analytics servers, upgrade each analytics server; see Upgrade analytics servers.


30 

Upgrade or install at least one NFM-P single-user client or client delegate server; see Enable GUI client.

Note: This stage marks the end of the network management outage.


31 

Perform sanity testing on the NFM-P system using a GUI client; see Test upgraded system using GUI client.


32 

Uninstall the original primary main database; see Uninstall original primary database [DB1].


33 

Install the new standby main database; see Install new standby main database [DB1].

  1. Stop the main database.

  2. Run a script to prepare for the Oracle software installation.

  3. Install the database packages.

  4. Configure the standby database.

  5. Verify and modify the database configuration, as required.


34 

Reinstantiate the standby database; see Reinstantiate standby database.


35 

If the NSP system includes redundant auxiliary database clusters, upgrade the former primary cluster; see Upgrade former primary auxiliary database cluster.


36 

Upgrade the original primary main server as the new standby main server; see Upgrade original primary main server [Main1].


37 

Configure the new standby main server; see Configure new standby main server [Main1].


38 

If required, enable Windows Active Directory for client access; see Enable Windows Active Directory access.


39 

If required, configure ADFS to enable Common Access Card, or CAC, client access; see Enable CAC access.


40 

If the NFM-P is integrated with an WS-NOC system, configure the integration; see Configure WS-NOC integration.


41 

Start the new standby main server; see Start new standby main server [Main1].


42 

If the system includes auxiliary servers, upgrade the [Aux1] auxiliary servers; see Upgrade auxiliary servers [Aux1].


43 

If the system includes auxiliary servers, start the [Aux1] auxiliary servers; see Start auxiliary servers [Aux1].


44 

If the system includes redundant auxiliary database clusters, activate each cluster; see Disable maintenance mode for auxiliary database agents.


45 

If the system includes an auxiliary database, verify that the auxiliary database is functioning correctly; see Verify auxiliary database status.


46 

Recheck the available disk space; see Check post-upgrade disk space.


47 

Install or upgrade single-user GUI clients, as required; see Install or upgrade single-user GUI clients.


48 

Install or upgrade client delegate servers, as required; see Install or upgrade client delegate servers.


49 

Stop the PKI server; see Stop PKI server.


50 

If the NFM-P system has customized TLS version and cipher support, restore the custom TLS support settings; see Restore TLS version and cipher support configuration.


51 

Configure and enable firewalls, if required; see Configure and enable firewalls.

Concurrent task execution

Some system upgrade operations require considerable time. To reduce the duration of a redundant system upgrade, you can perform some actions concurrently.

The following table lists the redundant system upgrade workflow tasks in a format that involves two operators, A and B, who perform tasks concurrently when possible.

Table 16-2: Workflow for concurrent task execution during redundant upgrade

System redundancy mode

Operator A actions

Operator B actions

D

U

P

L

E

X

Stage 1 — Actions described in To prepare for an NFM-P system upgrade from Release 22.9 or later

Stage 2Check pre-upgrade disk space

Stage 3Stop and disable standby main server [Main2]

Stage 4Stop auxiliary servers [Aux2]

Stage 5Disable database redundancy

S

I

M

P

L

E

X

Stage 6Upgrade standby main database [DB2]

Stage 7Upgrade standby main server [Main2]

Stage 8Start PKI server

Stage 9Configure new primary main server [Main2]

Stage 10Restore embedded nspOS, independent deployment

Stage 11Enable Windows Active Directory access

Stage 12Enable CAC access

Stage 13Configure WS-NOC integration

Stage 14Stop NSP analytics servers, NSP Flow Collectors

Stage 16Verify auxiliary database synchronization

Stage 17Enable maintenance mode on auxiliary database agent

Stage 18Upgrade standby auxiliary database cluster

Stage 15Upgrade auxiliary servers [Aux2]

O

U

T

A

G

E

Stage 19Stop and disable original primary main server [Main1]

Stage 23Upgrade auxiliary database, if not redundant

Stage 20Upgrade NSP Flow Collector Controllers, Flow Collectors

Stage 24Enable maintenance mode for auxiliary database agent

Stage 21Stop auxiliary servers [Aux1]

Stage 25Stop former primary auxiliary database cluster

Stage 22Stop original primary main database [DB1]

Stage 27Start auxiliary servers [Aux2]

Stage 26Start new primary main server [Main2]

Note: The outage persists until device discovery completes.

Stage 28Activate upgraded former standby auxiliary database cluster

S

I

M

P

L

E

X

Stage 29Upgrade analytics servers

Stage 30Enable GUI client

Stage 31Test upgraded system using GUI client

Stage 32Uninstall original primary database [DB1]

Stage 33Install new standby main database [DB1]

Stage 34Reinstantiate standby database

Stage 36Upgrade original primary main server [Main1]

Stage 35Upgrade former primary auxiliary database cluster

Stage 37Configure new standby main server [Main1]

Stage 38Enable Windows Active Directory access

Stage 39Enable CAC access

Stage 40Configure WS-NOC integration

Stage 41Start new standby main server [Main1]

Stage 42Upgrade auxiliary servers [Aux1]

Stage 43Start auxiliary servers [Aux1]

Stage 44Disable maintenance mode for auxiliary database agents

Stage 45Verify auxiliary database status

D

U

P

L

E

X

Stage 46Check post-upgrade disk space

Stage 47Install or upgrade single-user GUI clients

Stage 48Install or upgrade client delegate servers

Stage 49Stop PKI server

Stage 50Restore TLS version and cipher support configuration

Stage 51Configure and enable firewalls