Printer FriendlyEmail Article Link

Spirent Velocity: How to upgrade Velocity to latest version if you are several releases behind?

Objective/Summary
If an upgrade needs to be done from an older version of Velocity like 6.xà8.x (several releases in between) there are a lot of things to take into consideration to ensure a smooth migration.
 
Environment/Versions
Spirent Velocity & VDS 
 
Procedure
A typical upgrade process consists of these steps:
  • Switch of Velocity and perform offline backup of iTE database (iTE-data-offline.bak)
  • Run Velocity and download configuration(json) and remove hotfix_directory/patch (if any), clear jboss
  • Power off Velocity and change iso
  • Power off iTE and change iso
  • Run iTE, make the proper config
  • Run Velocity, make the proper config
  • Upgrade external agent (if any)
  • Perform testing on upgraded setup (reservations/tests/inventory changes)
 
Important notes:
For example upgrading from 6.1 to 8.2 could be done like this: 6.1à7.0à7.1à7.3à8.0à8.2 (usually we recommend upgrade process by two)
  • On licensing area :
    • ensure the license file will be compatible with 8.2 release
    • update license server package (if there’s external license server in place)
  • Check  VMware versions to ensure compatibility of supported version is satisfied
  • Ensure resource requirements can be fulfilled (CPU, memory, disk space)
  • Ensure you have downloaded the iso images from CSC beforehand
  • To download older versions from CSC, please filter by ‘Archived Release’ (left) and pick the desired version (right) from the list:
  • Starting with 8.0 release, iTE has been renamed VDS (Velocity Data Store)

Product : Velocity Core,Velocity Portfolio