System conversion to redundancy workflow
Description
The following is the sequence of high-level actions required to convert a standalone NFM-P system to a redundant system. Each link is a reference to a section in To convert a standalone NFM-P system to a redundant system.
Stages
1 |
Configure TLS and firewalls, as required; see Perform security preconfiguration. |
2 |
Back up the NFM-P configuration files; see Back up configuration files. |
3 |
Download the required installation files; see Download installation files. |
4 |
Gather the system information required for the conversion; see Gather required information. |
5 |
Close the unrequired NFM-P client sessions; see Close client sessions. |
6 |
Back up the main database; see Back up database. |
7 |
Stop the main server; see Stop main server. |
8 |
Convert the standalone database to a primary database; see Convert standalone database to primary database. |
9 |
Convert the standalone server to a primary main server; see Convert standalone main server to primary main server. |
10 |
Create an Oracle management user account and configure the associated system parameters on the standby main database station; see Prepare new station for standby database installation. |
11 |
Install the standby database; see Install standby database. |
12 |
Install the standby main server; see Install standby main server. |
13 |
If required, enable Windows Active Directory for client access; see Enable Windows Active Directory access. |
14 |
If required, configure ADFS to enable Common Access Card, or CAC, client access;; see Enable CAC access. |
15 |
If required, configure WS-NOC integration with the NFM-P; see Configure WS-NOC integration. |
16 |
Start the standby main server; see Start standby main server. |
17 |
Reinstantiate the standby database; see Reinstantiate standby database. |
18 |
Use an NFM-P GUI client to perform sanity testing on the newly redundant NFM-P system. |
19 |
Configure and enable firewalls, if required; see Configure and enable firewalls. |