Pathway for standalone NSP system upgrade from Release 25.11 or later
Purpose
Use this pathway through the documentation to access detailed procedures for upgrading a standalone NSP system. Table 9-1, Pathway for concurrent task execution during standalone NSP system upgrade from Release 25.11 or later lists the redundant system upgrade pathway tasks in a format that involves two operators, A and B, who perform tasks concurrently when possible.
Concurrent task execution
Some system upgrade operations require considerable time. To reduce the duration of a standalone system upgrade, you can perform some actions concurrently.
Note: The Upgrade standalone system links lead to sections in To upgrade a standalone 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-1: Pathway for concurrent task execution during standalone NSP system upgrade from Release 25.11 or later
|
Operator A actions |
Operator B actions | |
|---|---|---|
|
Perform To prepare for an NSP system upgrade from Release 25.11 or later to do the following: | ||
|
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 | ||
|
O U T A G E |
||
|
Note: Skip this stage if your deployment includes NFM-P. | ||
|
If you manually installed RHEL OS, To prepare DRBD kernel modules for RHEL 9 nodes Upgrade Kubernetes deployment environment | ||
|
Restore SELinux enforcing mode Configure remote authentication sources Remove path-control subscriptions | ||