Pathway to upgrade a redundant Release 25.11 or earlier NFM-P system

Description

Use this pathway through the documentation to access detailed procedures for upgrading a redundant NFM-P system at Release 25.11 or earlier.

Stages

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

Prepare system for upgrade
 
1 

Perform To prepare for an NFM-P system upgrade from Release 25.11 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 required, enable Windows Active Directory for client access; see Enable Windows Active Directory access.

11 

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.

12 

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

13 

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

14 

If the deployment includes an auxiliary database, update the auxiliary database schema on the standby auxiliary database cluster; see Update standby auxiliary database schema.

15 

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.

16 

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.

17 

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

18 

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

19 

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

20 

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

21 

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

22 

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

23 

If the deployment includes an auxiliary database, activate the upgraded standby (first) cluster, see Activate upgraded standby auxiliary database cluster.

24 

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.

25 

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

26 

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

27 

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.

28 

Reinstantiate the standby database; see Reinstantiate standby database.

29 

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

30 

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

31 

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

32 

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

33 

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

34 

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

35 

If the deployment includes an auxiliary database, update the auxiliary database schema on the primary (second) auxiliary database cluster; see Update primary (second) auxiliary database schema.

36 

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

37 

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

38 

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

39 

If the deployment includes an auxiliary database, activate the primary (second) auxiliary database cluster; see Disable maintenance mode for auxiliary database agents.

40 

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

41 

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

42 

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

43 

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

44 

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.

45 

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 pathway tasks in a format that involves two operators, A and B, who perform tasks concurrently when possible.

Table 15-2: Pathway 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 25.11 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 — Enable Windows Active Directory access

Stage 11 — Stop NSP analytics servers, NSP Flow Collectors

Stage 12 — Upgrade auxiliary servers [Aux2]

Stage 13 — Upgrade standby auxiliary database cluster

Stage 14 — Update standby auxiliary database schema

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

Stage 16 — Perform NSP Flow Collector migration

O

U

T

A

G

E

Stage 17 — Stop auxiliary servers [Aux1]

Stage 18 — Stop original primary main database [DB1]

Stage 19— Stop former primary auxiliary database cluster

Stage 20 — Integrate NFM-P and NSP cluster

Stage 21 — Start new primary main server [Main2]

Note: The outage persists until device discovery completes.

Stage 22 — Start auxiliary servers [Aux2]

Stage 23 — Activate upgraded standby auxiliary database cluster

S

I

M

P

L

E

X

—

Stage 24 — Enable GUI client

Stage 25 — Test upgraded system using GUI client

Stage 26 — Uninstall original primary database [DB1]

Stage 27 — Install new standby main database [DB1]

—

Stage 28 — Reinstantiate standby database

Stage 30 — Upgrade original primary main server [Main1]

Stage 31 — Configure new standby main server [Main1]

Stage 29 — Upgrade former primary auxiliary database cluster

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

Stage 33 — Enable Windows Active Directory access

Stage 34 — Integrate NFM-P and NSP cluster

Stage 35 — Update primary (second) auxiliary database schema

Stage 36 — Start new standby main server [Main1]

Stage 37 — Upgrade auxiliary servers [Aux1]

Stage 38 — Start auxiliary servers [Aux1]

Stage 39 — Disable maintenance mode for auxiliary database agents

Stage 40 — Verify auxiliary database status

D

U

P

L

E

X

Stage 41 — Check post-upgrade disk space

Stage 42 — Install or upgrade single-user GUI clients

Stage 43 — Install or upgrade client delegate servers

Stage 44 — Restore TLS version and cipher support configuration

Stage 45 — Configure and enable firewalls