Customer Service Center

Objective/Summary If issues with high impact are discovered after release, a patch is created to resolve them.   Patch should be installed on Velocity only if Spirent team has recommended it.   Environment/Versions Spirent Velocity & VDS    Procedure Patch Installation Instructions   Spirent will provide the patch containing these files: patch-vel-version.tar.gz – this is the patch patch-vel-version.tar.gz.sha1 – this is used for checksum   copy the file patch-vel-version.tar.gz to your local drive. SSH into your Velocity VM Create a folder called hotfix under the /data folder, if it does not already exist. If /data/hotfix folder already exists, delete all existing patch files (Velocity doesn’t allow multiple patches; latest version contains all the fixes from previous patch versions) Use scp/winscp/FileZilla to copy the patch (patch-vel.tar.gz) into /data/hotfix directory of your Velocity VM once the patch has been copied, check the integrity of the file: issue command: sha1sum patch-vel- version.tar.gz the id returned should match the one from patch-vel- version.tar.gz.sha1 Reboot the Velocity VM.   After reboot, notice that Velocity login page will display the build information: Velocity version build number (patch-vel-number.tar), to indicate that the patch has been applied.   Instructions to uninstall the Patch:   Before any upgrade of the system, it is mandatory to remove all patch files from /data/hotfix folder.   Remove patch as follows: SSH to Velocity and issue command: rm -r /data/hotfix*” shutdown your Velocity instance before upgrading VDS