Pathway for DR NSP system upgrade from Release 25.11 or later

Purpose

Use this pathway through the documentation to access detailed procedures for a DR NSP system. Table 9-2, DR system upgrade actions, by NSP cluster from Release 25.11 or later lists the sequence of high-level actions involved in the upgrade. The table has a separate column for each NSP cluster.

Concurrent task execution

You can perform some upgrade actions on each cluster at the same time. Actions that you can perform concurrently on each cluster are in table rows that span the Primary NSP cluster and Standby NSP cluster columns.

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

Note: If your NSP deployment includes NFM-P on a release earlier than Release 24.4 and an auxiliary database is installed, you must follow the auxiliary database steps specified in General NFM-P Release 25.11 or earlier upgrade pathway.

Table 9-2: DR system upgrade actions, by NSP cluster from Release 25.11 or later

DR mode	Primary NSP cluster	Standby NSP cluster
D U P L E X	Perform “How do I display the NSP cluster status?” in the NSP System Administrator Guide to: identify the primary and standby NSP clusters verify the operational state of each NSP cluster
Perform To prepare for an NSP system upgrade from Release 25.11 or later to do the following: back up the NSP software configuration download the NSP installation software verify the cluster readiness for the upgrade perform special upgrade preconfiguration If you manually installed RHEL OS, To prepare DRBD kernel modules for RHEL 9 nodes
The remaining links in the table lead to step sections in To upgrade an NSP cluster from Release 25.11 or later.
Back up NSP deployer host configuration files Disable SELinux enforcing mode Apply OS update to NSP deployer host Prepare for Kubernetes upgrade Upgrade Kubernetes registry Configure Kubernetes deployer Restore NSP system files Configure NSP software DR-specific instructions
S I M P L E X		Stop and undeploy NSP cluster, scenario 1 or Stop and undeploy NSP cluster, scenario 2 Apply OS update to NSP cluster VMs If you manually installed RHEL OS, To prepare DRBD kernel modules for RHEL 9 nodes
O U T A G E	Stop and undeploy NSP cluster, scenario 1 Stop and undeploy NSP cluster, scenario 2 Upgrade auxiliary database Note: Skip Upgrade auxiliary database if your deployment includes NFM-P. Apply OS update to NSP cluster VMs If you manually installed RHEL OS, To prepare DRBD kernel modules for RHEL 9 nodes Upgrade Kubernetes deployment environment Install Kubernetes secrets Add TLS certificates Copy certificate for secure connections Restore NSP Data Reconfigure storage settings Upgrade NSP software Monitor NSP initialization
S I M P L E X	Verify upgraded NSP cluster operation Upgrade MDM adaptors Upgrade or enable additional components and systems
	Upgrade Kubernetes deployment environment Upgrade NSP software Monitor NSP initialization Verify upgraded NSP cluster operation Upgrade MDM adaptors Upgrade or enable additional components and systems
D U P L E X	Note: The simplex state persists until device discovery is complete. Purge Kubernetes image files Purge NSP image files Restore SELinux enforcing mode Import NFM-P users and groups Configure remote authentication sources Remove path-control subscriptions Restore classic telemetry collection Synchronize LSP paths Perform post-upgrade tasks

DR mode

Primary NSP cluster

Standby NSP cluster

Perform “How do I display the NSP cluster status?” in the NSP System Administrator Guide to:

identify the primary and standby NSP clusters
verify the operational state of each NSP cluster

Perform To prepare for an NSP system upgrade from Release 25.11 or later to do the following:

back up the NSP software configuration
download the NSP installation software
verify the cluster readiness for the upgrade
perform special upgrade preconfiguration
If you manually installed RHEL OS, To prepare DRBD kernel modules for RHEL 9 nodes