Should I use .tar.gz, or single step upgrade .zip package to upgrade to 9.3.x from my current version (8.1.x, 9.1.x, 9.2.x)?
Use the .tar.gz files of the concerned platforms to upgrade the SD-WAN software to 9.3.x. After the SD-WAN software is upgraded to 9.3.x version, perform change management using the .zip package to transfer/stage OS component software packages. After activation, the MCN transfers/stages OS components for all the relevant branches.
After upgrading to 9.3.0 using single step upgrade package (.zip file) do I need to perform .upg upgrade on each appliances?
No, OS software update/upgrade will be taken care by the single step upgrade .zip package and it is installed as per the scheduling details provided by you in the Change Management Settings of the respective sites.
Why should I use .tar.gz followed by .zip package to upgrade from pre-9.3 to 9.3.x , and why not directly use .zip package of 9.3.x?
Single Step upgrade package is supported from release 9.3.0 build 161 onwards. On earlier release versions (prior to 9.3) this package is not recognized. When the single step upgrade .zip package is uploaded into the Change Management inbox, the system throws an error stating that the package is not recognized. Hence, first upgrade the SD-WAN software to release 9.3 or above version and then perform Change Management using the .zip package.
How will the OS Components be installed through single step upgrade, if .upg upgrade is not performed?
The MCN will transfer/stage OS components software packages based on the appliance model, after the Change Management is completed using single step upgrade .zip package. After activation, the MCN starts transferring/staging the OS components software packages for the branches that need them for the scheduled update/upgrade.
How do I install OS components, without scheduling for later installations?
Set the Maintenance Window value to ‘0’ for instant installation of the OS components.
What is the use of scheduling installation? Can I use schedule instructions to upgrade SD-WAN alone?
Scheduled installation was introduced in SD-WAN 9.3 release and is applicable for OS components only and not for SD-WAN software upgrade. With single step upgrade, you need not log into each appliance to perform OS components upgrade and the scheduling option allows you to schedule the OS components installation at a different time other than SD-WAN software version upgrade.
Why does the scheduling information in Change Management Settings page displays past schedule date by default and what does it mean?
The Change Management Settings page displays the default scheduling information i.e., ‘"start": "2016-05-21 21:20:00", "window": 1, "repeat": 1, "unit": "days"’. If the date is a past date it means that, the scheduled installation is based on the time and other parameters like maintenance window, repeat window, and unit and not the date.
What is default schedule installation date/time set to, is it generic or local appliance dependent?
By default the scheduling details is set as ‘2016-05-21 at 21:20:00 (Maintenance window of 1 hours and repeated every 1 days)’. This detail is local appliance site dependent.
How can I install OS Components immediately without waiting for the maintenance / scheduled window?
Set the Maintenance Window value to ‘0’ in Change Management Setting page, this overrides the scheduled installation time.
Which package should I use for upgrade when current software version is 9.3.x or above?
Use single step upgrade .zip package to upgrade to any higher versions when the current software version is 9.3.x or above.
When does the OS Components files get transferred/staged to the branches?
The OS components files are transferred/staged to relevant braches after the activation is completed when Change Management is done using single step upgrade .zip package to upgrade the system.
Which appliances receive OS Components files? Is it platform dependent or do all branches receive it.
Appliances that are hypervisor based such as, SD-WAN – 400, 800, 1000, 2000 SD-WAN and Bare metal SD-WAN - 2100 running on EE license will receive OS components to upgrade.
How does scheduling work?
By default the scheduling details is set as ‘2016-05-21 at 21:20:00 (Maintenance window of 1 hours and repeated every 1 days)’ and it implies that the system will check if new software is available for installation every day as repeat value is set to ‘1 days’ and will have maintenance window of ‘1 hours’ and the installation will get triggered/attempted (if new software is available) at 21:20:00 (local appliance time) effective from ‘2016-05-21’
How do I get to know if the OS Components have been upgraded?
In the Status column, you will see a green tick mark. On hovering over it, you will see ‘Upgrade is Successful’' message.
Can I use tar.gz file to upgrade to next release, when single step upgrade was used for previous software upgrade?
You can use tar.gz file to upgrade, but it is not recommended because you would need to perform .upg upload to upgrade OS component software by logging into each applicable appliances. From release 9.3 version 1 onwards the ‘Update Operating System Software’ page is depreciated, hence you would need to perform change management with .zip package to upgrade the OS components.
How can we validate the current running versions of OS Components?
Currently you cannot validate the current running versions of OS components from the SD-WAN GUI. You need to login from each console or get STS to view this information.
What difference it would make if I have bare metal appliances in my network? Does scheduling impact bare metal / Virtual appliances?
Bare Metal appliances such as, SD-WAN – 410,2100,4100,5100 SD-WAN run only SD-WAN software and they do not need any OS components packages. These platforms are treated on par with SD-WAN VPX in terms of software need. The MCN will not transfer OS components packages to these appliances. Setting scheduling information will not take effect for these appliances, as they do not have any OS components that needs upgrade.
How does Single Step Upgrade work in HA environment / deployment?
In HA deployment at MCN we have a limitation, where the active MCN switch’s/toggles the role of primary MCN during Change Management and Standby/Secondary MCN takes over. In this case, you need to perform Change Management once again with the .zip package on the active MCN for the packages or you can switch back to primary MCN by toggling the role of active MCN so that original primary MCN can take up the role for the OS components packages to be staged to other branches.
How does single step upgrade work in HA environment / deployment?
While performing single step upgrade in HA deployment, the role of the primary MCN and the Standby MCN is toggled. This is a limitation. If this happens, perform Change Management again with the .zip package on the active MCN. Alternatively, you can switch back to the primary MCN by toggling the role of the active MCN so that the original primary MCN can stage OS components packages to the branches.
Is single step upgrade support for ZTD to boot strap the appliances?
Yes, it can be used.
Can I use single step upgrade to upgrade my standalone WAN opt?
Can I use single step upgrade to upgrade standalone WANOP appliance deployed in 2Box mode?
No. Only SD-WAN appliance part of 2Box mode would be upgraded and not the WANOP standalone appliance.