Pre-upgrade Considerations
The following steps provide pre-upgrade procedure to identify the impacted service extension templates and device templates migration.
Procedure
Step 1 |
To identify the impacted templates: Download the template-migration.tar file from the CCO based on the Current and Target version of the VTS. |
||||||
Step 2 |
Fix the templates: 2a. Fix the templates manually: You can fix templates manually. With the available list of impacted template files you can fix each one of the templates to be compatible with the target version. For example, after executing the script "./find-impacted-templates-252-262.sh" you can find a file named "sample1.impacted.keys" in my templates directory along with an already exported template called/named "sample1.json".
When you open the "sample1.impacted.Keys" file, you can view the following entry:
The above entry indicates that in the upgrade-to version the "mask" attribute was either altered or deleted. To figure out the exact changes, open the traget <schema name>.txt under the vts-launchers/schemas directory and seek the path up until the change. In this example, we seek the string "config/nx:router/ospf{}/area{}/range".
Since there is no "/mask" it is clear that the attribute was deleted. To identify the attribute that was added,
You can view the targeted VTC version in the VTS GUI as shown in below figure: As shown in the below image, remove the "mask" attribute and add it as "./xx" to the ip address and do that fix in the json file: After the fix as shown in the above image, the sample1.jason file is ready to be used during the migration process. Follow the above steps and migrate all the impacted templates in the templates directory according to the new model. To automate the 2a section, you can refer to the sample conversion script which will convert the impacted templates to the format compatible to VTS262.
Steps to be performed:
2b. To fix the templates by creating a dummy target VM: If there is a target VTC VM available, recreate the impacted templates with the same name and export as json files by running the following command from the NCS CLI:
For VTS2.6.2 as it supports multi sites, when you create a template in VTS 2.6.2 you can view this template under the specific site. If you are exporting the templates from VTS-2.6.2, use the command:
where default-site-id is 111C3493-DFC6-4D54-8E0C-02470CA25111 These json files can be used for template migration in the next step by copying to "/home/admin/templates-for-migration" in the VTC VM instead of fixing the existing templates. |
||||||
Step 3 |
Copy the migrated templates to the VTC 2.5.2 machine |