| |
|
1 |
Node upgrade can be created from two different locations: Device Management, All Operations or Device Management, Node Images. Navigate to either location to begin this procedure.
|
2 |
If you navigated to All Operations, select Operation, Operation Type and choose "nsp-ne-upgrade-with-phases" from the list.
|
3 |
If you navigated to Node Images, locate the SR OS tab and click  , Upgrade...
Select Operation, Operation Type and choose "nsp-ne-upgrade-with-phases" from the list.
|
4 |
Select Target family product and all other options:
Operation Control: When upgrading multiple NEs at the same time, users can select "Per Phase" if targets (nodes) proceed as a group - which means all nodes must complete the current phase before proceeding to the next - OR "Per target" target and proceed to the next phase immediately regardless if the other targets are complete or not.
Rollback Type: Applicable for phases that support rollback - Activate and Reboot.
|
5 |
Select  TARGETS, NEs or Predefined NE groups.
|
6 |
Select Operation Inputs:
Target Software Version: Select the version of the image from the list; the images that show in the drop down are the ones imported to Node Images.
Is ISSU: Defaulted to False, set to True only for nodes that support ISSU. Check the "SR OS Software Release Notes" documentation for the node chassis types that support ISSU.
Auto Cleanup: Defaulted to True. When set to True, it will auto-delete all images in the images directory that are not referenced in the bof.
Free Space Post Upgrade: The expected free disk space % after upgrade, and only used when autoCleanup is set to True.
|
7 |
Users can select any of these optional Advanced Inputs for each of the phases:
Configure the Advanced Inputs as needed:
|
Parameter |
Description |
|
Window Size
Failure Threshold |
These two parameters work together to define an automatic stopping point for the operation due to failed workflow executions:
-
Window size specifies the sample size to use when calculating whether a threshold has been crossed.
-
Failure threshold specifies the percentage of executions failed that will trigger the automatic stop.
For example, with a window size of 200 and a failure threshold of 50%, the operation will automatically stop after 100 failed executions. The phase and operation are paused and any not-started executions remain in not-started status. |
|
The following parameters can be configured separately for each phase of the operation: pre-checks, software download, software activation, and NE reboot or CMP switchover. |
|
|
These parameters specify how the workflow executions will be managed. The pre-check steps themselves are defined in the applicable workflow.
-
Concurrency Count: maximum number of executions to run concurrently.
-
Phase Timeout and Average Execution Threshold: if these parameters are configured, the operation automatically stops after the specified time. The phase and operation are paused and any not-started executions remain in not-started status. |
|
8 |
View/Edit Schedule:
If the user selected Operational Control - "Per phase" in Step 3, the phases will only have the option to run manually.
If the user selected Operation Control - "Per target" in Step 3, they can select to run each phase manually, immediately, or after a delay (min).
|
9 |
After selecting all the options for an upgrade, users can Run or Save. A saved operation can be viewed from Device Management, All Operations with Saved status. Users can start operation at any time.
End of steps |
