This is a use case if you are procuring a 16.1R2 S11 appliance and trying to onboard it on Director version 21.2.3


NOTE: You cannot upgrade from 16.1R2-Sx to 20.2.4 with VOS build currently running 16.1R2-Sx where x < 8

 The VOS/CPE needs to be on 16.1R2-S8/S11 at least.


Download Link:

16.1R2S11: https://versanetworks.box.com/s/50muiv9rgkpb6ocwmskshq2q8wixtytt



Direcroe Running 21.2.3. There is a compatibility issue with 16.1R2S11 appliances when you try to onboard and the template workflow is not set with the preferred software version or global is not set to a newer version


First, copy the min 20.2.4 .bin image at least to the appliance /home/versa/packages folder and add the necessary permissions using the following command


NOTE: 20.2.4 is just an example but you can also run any hotfix or current 20.2.x, 21.1.x, and 21.2.x Image to do this


Download Link:

20.2.4: https://versanetworks.box.com/s/vnyxofqezpk2utogavlbg6stzl3qjs1l

21.1.4: https://versanetworks.box.com/s/9wjp95iz94itjccqm0ruewur4htnqgi8

21.2.3: https://versanetworks.app.box.com/folder/168829564793?v=21-2-3-GA-GO


(Reach out to Versa Support for any specific release if not available in the above link)


How to move the image to the appliance if the appliance is not reachable from Director



You may have to move the package to the /tmp folder first and change the permission and once done then you can move the package to /home/versa/packages


  • cd /tmp
  • sudo chmod 755 <package-name>
  • mv <package> /home/versa/packages


Please follow either of the two options to upgrade


Option 1) If you want to run the upgrade on top of the current image then we recommend using the CLI command

> request system package upgrade <package>

Monitor upgrade: tail -f /var/log/versa/upgrade.log


Or 


Option 2) Once you move the image then on the appliance do the below to have a clean installation of the new package by removing the existing package,

 

  • Add 20.2.4 package in /home/versa/packages   <--------- Make sure of this before running below
  • vsh stop 
  • sudo dpkg --purge versa-flexvnf
  • sudo rm -rf /opt/versa
  • sudo rm -rf /var/versa
  • cd /home/versa/packages
  • sudo ./<vos-package>
  • sudo reboot        <-------------- Mandatory.
  • sudo dpkg -l | grep -v ^ii    <------------- to make sure no packages are in an inconsistent state.


One new package is installed successfully then do the below to complete the RMA process


Export the configuration from the Versa Director, Select the Device, and Click on the Export option to down the config to make sure we have a backup if case RMA fails to load the correct config.


  • Delete the appliance from the Director
  • Workflow > Device > Template > Replace the SN > Re-deploy
  • Run the staging script to onboard the device


========================================================================================


Bug Detail for Failed RMA using replace SN


Error On Director Task


Springboot Director backend Error



Bug-ID: 89945

Description: The API used to fetch the private and public keys from the appliance could not validate the availability of the appliance causing the keys to not get pulled in from the Director.


This is leading to the RMA failing, as the Post-staging template will not get pushed.


Fix Release: 21.2.4


As a workaround for RMA until the fix is made at the code level for [89945]:


We have to delete the appliance from the Administration > Appliances Tab, then update the Serial Number and re-deploy the device workflow. Then re-onboard the Device-Workflow. Please note that any appliance level changes made at the older appliance may not be preserved in this case.


If you still have an issue after this, please contact versa support.