What steps are needed for VNA when migrating Spectrum on new operating system
search cancel

What steps are needed for VNA when migrating Spectrum on new operating system


Article ID: 192985


Updated On:


CA Spectrum CA eHealth


This weekend we are migrating Spectrum from windows 2012 to windows 2016. We have VNA integrated.  What steps are needed to prevent migration problems with VNA inventory?


Release : 10.3

Component : Spectrum Core / SpectroSERVER


Make sure that an online backup does not kick off during this time. Disable the online backup on the VNM until this process is done.

Enable VNA Inventory debug from the OneClick Administration page - Debugging - VNA Integration Information and VNA Notification Sync
Disable VNA-OneClick Integration from the OneClick
As soon as the integration is disabled all SDN models will start to be deleted. This can take a couple of hours depending on the number of models.
Ensure all models are deleted before proceeding. You can check to make sure no models exist under “SDN Manager” and to double check, review the tomcat log file. You should see this entry when the delete starts:
Jun 12, 2020 08:57:02.202 (pool-3-thread-18) (SDNIntegrationServlet) - SDN Integration Manager clean-up started..

And when it is finished you will see this message:

Jun 12, 2020 08:57:02.232 (pool-3-thread-18) (SDNIntegrationServlet) - SDN Integration Manager clean-up done..

Save the SSDB and DDMDB after all the models are removed.

Perform Spectroserver and OneClick migrations using the DB’s saved during step 4.
Perform any VNA related upgrades or migrations or plugin additions\deletions at this point prior to enabling the integration.
Enable VNA-OC integration which starts pushing all SDN inventory with new Entity_UUID’s.
Check the Host name on the SDN Manager model for FQDN