Workflow to upgrade a redundant Release 22.6 or earlier NFM-P system

Description

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

Stages

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

Prepare system for upgrade
 
1 

Perform To prepare for an NFM-P system upgrade from Release 22.6 or earlier.

Upgrade redundant system
 
2 

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

3 

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

4 

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

5 

Disable the system redundancy functions; see Disable database redundancy.

6 

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.

7 

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

8 

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

9 

Restore the backed-up [Main2] data files; see Restore new primary main server [Main2] data files.

10 

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.

11 

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

12 

If the deployment includes an auxiliary database, upgrade the standby auxiliary database cluster; see Upgrade standby auxiliary database cluster.

13 

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.

14 

If the system includes one or more NSP Flow Collectors, migrate from using NSP Flow Collectors and Flow Collector Controllers to the Flow Collector functions in the NSP cluster; see Perform NSP Flow Collector migration.

15 

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

16 

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

17 

If the deployment includes an auxiliary database, stop the former primary auxiliary database cluster; see Stop former primary auxiliary database cluster.

18 

If the NFM-P is currently an independent deployment, integrate the NFM-P and the NSP cluster; see Integrate NFM-P and NSP cluster.

19 

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

20 

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

21 

If the deployment includes an auxiliary database, activate the upgraded former standby cluster, see Activate upgraded former standby auxiliary database cluster.

22 

If the system includes one or more NSP analytics servers, upgrade each analytics server; see Perform NSP analytics server migration to NSP cluster.

23 

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.

24 

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

25 

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

26 

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.

27 

Reinstantiate the standby database; see Reinstantiate standby database.

28 

If the NSP deployment includes an auxiliary database, upgrade the former primary auxiliary database cluster; see Upgrade former primary auxiliary database cluster.

29 

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

30 

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

31 

Restore the backed-up [Main1] data files; see Restore new standby main server [Main1] data files

32 

If the NFM-P is currently an independent deployment, integrate the NFM-P and the NSP cluster; see Integrate NFM-P and NSP cluster.

33 

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

34 

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

35 

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

36 

If the deployment includes an auxiliary database, activate each auxiliary database cluster; see Disable auxiliary database maintenance mode.

37 

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

38 

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

39 

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

40 

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

41 

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.

42 

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 15-1: 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.6 or earlier

Stage 2 — Check pre-upgrade disk space

Stage 3 — Stop and disable standby main server [Main2]

Stage 4 — Stop auxiliary servers [Aux2]

Stage 5 — Disable database redundancy

S

I

M

P

L

E

X

Stage 6 — Upgrade standby main database [DB2]

Stage 7 — Upgrade standby main server [Main2]

Stage 8 — Configure new primary main server [Main2]

Stage 9 — Restore new primary main server [Main2] data files

Stage 10 — Stop NSP analytics servers, NSP Flow Collectors

Stage 11 — Upgrade auxiliary servers [Aux2]

Stage 12 — Upgrade standby auxiliary database cluster

Stage 13 — Stop and disable original primary main server [Main1]

Stage 14 — Perform NSP Flow Collector migration

O

U

T

A

G

E

Stage 15 — Stop auxiliary servers [Aux1]

Stage 16 — Stop original primary main database [DB1]

Stage 17— Stop former primary auxiliary database cluster

Stage 18 — Integrate NFM-P and NSP cluster

Stage 19 — Start new primary main server [Main2]

Note: The outage persists until device discovery completes.

Stage 20 — Start auxiliary servers [Aux2]

Stage 21 — Activate upgraded former standby auxiliary database cluster

S

I

M

P

L

E

X

Stage 22 — Perform NSP analytics server migration to NSP cluster

Stage 23 — Enable GUI client

Stage 24 — Test upgraded system using GUI client

Stage 25 — Uninstall original primary database [DB1]

Stage 26 — Install new standby main database [DB1]

—

Stage 27 — Reinstantiate standby database

Stage 29 — Upgrade original primary main server [Main1]

Stage 30 — Configure new standby main server [Main1]

Stage 28 — Upgrade former primary auxiliary database cluster

Stage 31 — Restore new standby main server [Main1] data files

Stage 32 — Integrate NFM-P and NSP cluster

Stage 33 — Start new standby main server [Main1]

Stage 34 — Upgrade auxiliary servers [Aux1]

Stage 35 — Start auxiliary servers [Aux1]

Stage 36 — Disable auxiliary database maintenance mode

Stage 37 — Verify auxiliary database status

D

U

P

L

E

X

Stage 38 — Check post-upgrade disk space

Stage 39 — Install or upgrade single-user GUI clients

Stage 40 — Install or upgrade client delegate servers

Stage 41 — Restore TLS version and cipher support configuration

Stage 42 — Configure and enable firewalls