| Add_workflow_for_techpubs |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a0c857f0393d01583fcf9db40009, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc1e0747, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a0c86a195e2c016a28f1445d000a, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced60ca3, userName='null'} |
|---|
| REV2 | UserResourceIdentifier{userKey=8a00a0c85fd202bb01600fc680190023, userName='null'} |
|---|
|
Prior Prior to the upgrade, the new software load (for example, dsc_swe_20_x_x_xxx_upgrade.sh file) is uploaded from the
Global Support Portal onto a space accessible by the KVM, VMWare, OpenStack or
hypervisor.
...
- run the upgrade file on Management/Routing VM of the hypervisor that contains this file
- upgrade the system using the upgrade script on the same Management/Routing VM
...