Download the template-migration.tar file from the CCO based on the Current and Target version of the VTS.

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:

config/nx:router/ospf{}/area{}/range{}/mask

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,

• Use a target VTC machine with the target version.

• Create that path as part of a new template.

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:

• Step 1: Once you identify the templates which are impacted using template migration script, you can copy this ‘Sample_Conversion2521_262.py’ script to the vts-launcher directory.

• Step 2: Download both the packages pexpect and ptyprocess and install them as listed below.

  • Copy the below two packages to /home/admin in VTS252 VM.

    - ptyprocess-0.5.2.tar.gz

    - pexpect-4.4.0.tar.gz

• Step 3: Login to VTS252 VM as admin, switch to root by running sudo su -

  • Extract the packages:

    #tar -zxvf ptyprocess-0.5.2.tar.gz

    #tar -zxvf pexpect-4.4.0.tar.gz

  • Install ptyprocess first:

    Navigate to /home/admin/ptyprocess-0.5.2 directory, do ‘chmod 777 *’ and run

    #python3 setup.py install

  • Install pexpect:

    Navigate to /home/admin/pexpect-4.4.0 directory, do ‘chmod 777 *’ and run

    #python3 setup.py install

    Once done, go back to the /vts-launcher directory and run the conversion script. At the Username/Password prompt, enter UI login credentials.

    VTS-252-To-262/vts-launcher# python3 Sample_Conversion2521_262.py
    
    Enter VTS Username: admin
    Enter VTS Password: 
    

  Here impacted templates will get converted to the vts262 compatible format and are stored in the ‘templates-for-migration/’ directory, which is located in cd /vts-launcher/../templates-for-migration directory.

• Step 4: Copy templates-for-migration directory to /home/admin and follow the upgrade process steps by providing proper permissions and proceeding with the upgrade process.

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:

- show running-config templates template <template name> | display json | save ./tmp/<template name>.json

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:

% show running-config vts-service sites site 111C3493-DFC6-4D54-8E0C-02470CA25111 templates template N7K-RS | display json | save /tmp/N7K-RS.json

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.