Process for NE upgrade
Stages
1 |
Verify the management type for the node. The upgrade process will be different for MDM managed and NFM-P managed nodes. For operations performed on nodes discovered through mixed-mode or model-driven management, CLI access management must be enabled on the node. The following types of CLI access must be enabled, in the order shown: md-cli, and classic-cli. For SR OS device commissioning information, see the Management Interface Protocol Configuration section in the adaptor documentation. For additional information if needed, see the NE documentation. |
2 |
Import node software images as needed; see How do I import a node software image?. |
3 |
Start the upgrade operation; see How do I start or schedule a new operation? |
4 |
View the operation in the Operations tab to monitor it; see How do I view current operations and executions?. |
5 |
You can stop or pause an existing operation, and start or stop a phase within an operation. Operations can be paused manually by a user, or automatically by crossing a configured threshold (for example, percentage of failed executions). Phases that are waiting can be manually started, and a phase that is in progress can be stopped or paused.
See How do I start, stop, or pause an operation?. |
6 |
When the upgrade is complete, the NE reboots and raises a reboot alarm. The reboot alarm triggers an NE-specific discovery scan. When the discovery scan detects a version change, the NE information is updated. |
7 |
After the upgrade is complete, you can check the History list to verify success, troubleshoot failures, or check schedules for future operations. See How do I view the details of completed operations? |
8 |
To perform a rollback, see How do I perform a rollback on a target in an operation?. |