SpanVA .153 and old have been deprecated
Article ID: 370655
Updated On: 04-07-2025
Products
Issue/Introduction
SpanVA version 1.15.3.153.0-19rc and older are now EOS (End of Service) and have been deprecated. Versions .153 and older run on CentOS and is no longer supported by the vendor. CentOS has announced the EOL (End of Life) June 30, 2024. You can read more from CentOS here.
Broadcom recommends immediate upgrade to 1.15.3.166.0 which runs Oracle Linux.
Delaying the upgrade would leave the existing SpanVA in an unsupported state without patches or vulnerability notifications. If a failure occurs, provisioning a new SpanVA and recreating services may be required.
Resolution
How to Upgrade\Migrate from CentOS .153 SpanVA to the lastest SpanVA running Oracle Linux 1.15.3.166.0:
Upgrade SpanVA 1.15.3.153.0-19rc (CentOS)
Existing SpanVA: Auto-update or manually apply as configured from the SpanVA
Migrate to SpanVA 1.15.3.166.0 (Oracle Linux)
- Existing SpanVA: Auto-update or manual apply 1.15.3.153.0-19rc
- Backup the existing SpanVA running 1.15.3.153.0-19rc
- Deploy a new SpanVA 1.15.3.166.0
- Restore the existing SpanVA settings from the backup that was taken post *.153
See TechDOCS.
See KB391038 for in-depth steps regarding the migration or steps required for a parallel install (no migration).
New deployments are 1.15.3.166.0 by default.
Additional Information
See What's New in Symantec SpanVA for more detail.
Q&A:
Q: Will the SpanVA fail if I do not immediately upgrade\migrate to *.166?
A: The SpanVA will continue to function. Any new features or fixes would only be available after the migration to *.166. Having a good backup from the *.153 version will cut down on risk as the backup can be restored to the new *.166 deployment.
Q: Can I delete the SpanVA and move the services to another SpanVA?
A: Data-sources, tokens\mappings and Adsync cannot be moved manually to a new SpanVA. They would need to be recreated.
Feedback
