Manage software repository | Manage Software Upgrade and Repository | Cisco Catalyst SD-WAN Upgrade Guide

Describes how to manage the software repository, including adding, updating, and removing software images, to ensure your Cisco devices have access to the correct versions for installation and upgrades.

Register a remote server

Registering a remote server with Cisco SD-WAN Manager allows you to add software image locations to the software repository and perform device or controller software upgrades using these images.

This task enables centralized management of software images and streamlines the upgrade process for devices and controllers.

In a multitenant Cisco Catalyst SD-WAN deployment, only the provider can register a remote server and perform software upgrades using images on the remote server.

When a Cisco Catalyst SD-WAN device is running on release 17.15.1, if the remote FTP server is configured with a non-standard port, you cannot upgrade the device because the image cannot be downloaded. Reconfigure the FTP server to use standard ports to proceed with the upgrade.

Ensure you are using supported protocols and port configurations for successful image downloads and upgrades.

Before you begin

Ensure you have access to Cisco SD-WAN Manager and the necessary credentials to register a remote server.

Verify that the remote server is reachable and configured with supported protocols (HTTP, FTP, or SCP).

Follow these steps to register a remote server in Cisco SD-WAN Manager:

Procedure

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Repository.
Click Add Remote Server.

In the Add Remote Server slide-in page, configure the following fields:


Server Info	Server Name: Enter a name for the server. Server IP or DNS Name: Enter the IP address or the DNS name of the server. Protocol: Choose HTTP, FTP, or SCP. Port: Enter the access port number.
Credentials	User ID: Enter the user ID required to access the server. The username can contain only the following characters: a-z, 0-9, ., _, and -. Password: Enter the password required to access the server. The password can contain only the following characters: a-z, A-Z, 0-9, _, , ., +, =, %, and -. Note* Special characters such as /, ?, :, @, and SPACE, which are used in URLs and are needed for proper parsing of fields so files can be fetched properly with the relevant protocol, are not supported in the username and the password. The use of the valid characters is supported starting from Cisco vManage Release 20.9.1.
Image Info	Image Location Prefix: Enter the folder path where the uploaded images must be stored. For SCP, use the absolute directory path as the Image Location Prefix; for FTP or HTTP, use the relative path from the home directory. VPN: Enter the VPN ID, either the transport VPN, management VPN, or service VPN

Click Add to add the remote server.

After completing this task, the remote server is registered in Cisco SD-WAN Manager, and you can add software image locations from the remote server to the software repository for device or controller upgrades.

What to do next

Enable devices to use a remote repository server

See Enable Software Updates by a Remote Repository Server.

Manage a remote server

Configure and manage remote server settings in the Cisco SD-WAN Manager software repository to ensure proper storage and retrieval of software images.

Enable viewing, editing, and removal of remote server configurations as needed for software management.

This task is relevant when you need to add, modify, or delete remote server entries used for storing software images in the Cisco SD-WAN Manager software repository.

Perform this task when updating server details, changing credentials, or managing image storage locations for software distribution.

Use this procedure during initial setup or when server information changes.

Before you begin

Ensure you have access to the Cisco SD-WAN Manager interface and the necessary permissions to manage remote servers.

Verify that no software image entries from the remote server exist in the software repository if you plan to edit or delete the server.

Follow these steps to manage a remote server in the software repository:

Procedure

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Repository.
For the desired remote server, click ….
To view the remote server settings, click View Details.

To edit the remote server settings, click Edit. Edit any of the following settings as necessary and click Save.

Note

You cannot edit the remote server settings if you have added locations of any software images on the remote server to the Cisco SD-WAN Manager software repository. If you wish to edit the remote server settings, remove the software image entries from the software repository and then edit the settings.

Table 1. Remote server settings
Server Info	Server Name: Enter a name for the server. Server IP or DNS Name: Enter the IP address or the DNS name of the server. Protocol: Choose HTTP, FTP, or SCP. Port: Enter the access port number.
Credentials	User ID: Enter the user ID required to access the server. The username can contain only the following characters: a-z, 0-9, ., _, and -. Password: Enter the password required to access the server. The password can contain only the following characters: a-z, A-Z, 0-9, _, , ., +, =, %, and -. Note* Special characters such as /, ?, :, @, and SPACE, which are used in URLs and are needed for proper parsing of fields so files can be fetched properly with the relevant protocol, are not supported in the username and the password. The use of the valid characters is supported starting from Cisco vManage Release 20.9.1.
Image Info	Image Location Prefix: Enter the folder path where the uploaded images must be stored. For SCP, use the absolute directory path as the Image Location Prefix; for FTP or HTTP, use the relative path from the home directory. VPN: Enter the VPN ID, either the transport VPN, management VPN, or service VPN.

To delete the remote server, click Remove. Confirm that you wish to remove the remote server in the dialog box.

Note

Before deleting a remote server, remove any entries for software images on the remote server that you have added to the Cisco SD-WAN Manager software repository.

The remote server is added, updated, or removed in the Cisco SD-WAN Manager software repository, and the server settings are applied as configured.

What to do next

After managing the remote server, verify that the server appears correctly in the software repository and that image uploads or downloads function as expected.

Test connectivity and credentials to ensure successful access to the remote server.

Add software images to the repository

Add software images to the Cisco SD-WAN Manager software repository to enable upgrades for edge devices, Cisco Catalyst SD-WAN Controller, or Cisco SD-WAN Manager controllers.

Store images on the local Cisco SD-WAN Manager server or reference images on a remote file server.
Support upgrade workflows for various deployment scenarios.

This task is required before performing software upgrades on edge devices or controllers managed by Cisco SD-WAN Manager. The repository supports storing images locally or referencing remote servers, and different transfer methods may be used depending on your network environment and file size.

In a multitenant deployment, only the provider can register a remote server and add locations of software images to the repository. Disk space limitations may affect image uploads, especially in cluster environments.

Uploading images may fail if disk space on any node in a cluster is low. Ensure /opt/data/ remains below 80% utilization.
When downloading from a remote server, use only valid characters for user ID, password, and URL as specified in the notes.

Before you begin

Ensure you have access to the Cisco SD-WAN Manager software repository and the necessary software image files.

For remote server storage, register the remote server with Cisco SD-WAN Manager in advance.

Follow these steps to add software images to the repository:

Procedure

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Repository.
Click Software Images.
Click Add New Software.
Choose the location for the software image.
- Store the image on the local Cisco SD-WAN Manager server
- Store the image on a remote Cisco SD-WAN Manager server
- Software image is stored on a remote server
Note

Store NFVIS upgrade images on the local Cisco SD-WAN Manager server.

To store the image on the local Cisco SD-WAN Manager server for download over a control plane connection, choose Manager. The Upload Software to Manager dialog box opens.
1. Drag and drop the software image file to the dialog box or click Browse to select the image from a directory on the local Cisco SD-WAN Manager server.
2. Click Upload to add the image to the software repository.
To store the image on a remote Cisco SD-WAN Manager server for download over an out-of-band management connection, choose Remote Server - Manager. The Upload Software to Remote Server - Manager dialog box opens.
1. In the Manager Hostname/IP Address field, enter the IP address of an interface on the Cisco SD-WAN Manager server that is in a management VPN (typically, VPN 512).
2. Drag and drop the software image file to the dialog box, or click Browse to select the image from a directory on the local Cisco SD-WAN Manager server.
3. Click Upload.
If the software image is stored on a remote server, choose Remote Server (preferred). The Add New Software via Remote Server slide-in pane appears. Ensure the remote server is registered with Cisco SD-WAN Manager.
1. Click Image to upload a new software image, or SMU Image to upload an SMU image. The default selection is Image.
2. From the Remote Server Name drop-down list, choose the desired remote server.
3. Image Filename: Enter the image filename, including the file extension. For an SMU image, the file extension must be .SMU.bin.
4. For an SMU image, enter the correct SMU Defect ID and choose the correct SMU Type. An incorrect defect ID or SMU type selection can cause the software upgrade to fail.
5. Click Save.
Note
From Cisco vManage Release 20.7.1, you can store software images on a remote file server that is reachable through an FTP or HTTP URL. The Cisco SD-WAN Manager server sends this URL to the Cisco Catalyst SD-WAN device, which downloads the images. In a multitenant deployment, only the provider can register a remote server and add image locations to the repository.

Starting from Cisco vManage Release 20.9.1, when downloading an image from a remote server manually, ensure that only the following valid characters are used:
- User ID: a-z, 0-9, ., _, -
- Password: a-z, A-Z, 0-9, _, *, ., +, =, %, -
- URL Name or Path: a-z, A-Z, 0-9, _, *, ., +, =, %, -, :, /, @, ?, ~

After completing this task, the software image is available in the Cisco SD-WAN Manager repository for use in device or controller upgrades. The repository supports local and remote image storage, enabling flexible upgrade workflows.

What to do next

Proceed to initiate a software upgrade using the newly added image as required for your devices or controllers. Monitor disk space usage to avoid upload failures in future operations.

View the software images

Use the Cisco SD-WAN Manager menu to access the Software Repository window, where you can view available software images, their versions, locations, and file details.

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Respository.

The Software Repository window displays the images avaialable in the repository.

The Software Version column lists the version of the software image, and the Controller Version column lists the version of Cisco SD-WAN Control Components that is equivalent to the software version. The Cisco SD-WAN Control Components version is the minimum supported version. The software image can operate with the listed Cisco SD-WAN Control Components version or with a higher version.
The Software Location column indicates where the software images are stored, either in the repository on the Cisco SD-WAN Manager server, or in a repository in a remote location.
The Available Files column lists the names of the software image files.
The Updated On column shows when the software image was added to the repository.
The ... option for a desired software version provides the option to delete the software image from the repository.

In Cisco vManage Release 20.6.1 and earlier releases, when two or more software images have the same software version but are uploaded with different filenames, the images are listed in a single row. The Available Files column lists the different filenames. This listing scheme is disadvantageous when deleting software images as the delete operation removes all the software images corresponding to a software version.

From Cisco vManage Release 20.7.1, when two or more software images have the same software version but are uploaded with different filenames, each software image is listed in a separate row. This enables you to choose and delete specific software images.

Add virtual images to the repository

This task enables you to add virtual images to the repository in Cisco SD-WAN Manager for use in your network environment.

Facilitates the management and deployment of virtual images through various upload options, including remote server, manager, and remote server-manager.

Use this task when you need to add new or updated virtual images to the Cisco SD-WAN Manager software repository for deployment to network devices.

This process is relevant when onboarding new applications, updating existing images, or preparing images for deployment across devices managed by Cisco SD-WAN Manager.

Choose the appropriate upload method based on your network setup and file size requirements.

Before you begin

Ensure you have access to Cisco SD-WAN Manager and the necessary permissions to add virtual images to the repository.

If using the remote server option, verify that a remote server is registered with Cisco SD-WAN Manager. For details, see Register Remote Server.

Follow these steps to add virtual images to the repository:

Procedure

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Repository.
Click Virtual Images.
Click Add New Virtual Image and choose one of these options: Remote Server (preferred), Manager, or Remote Server - Manager.
- Remote Server (preferred): Link to an image uploaded to a remote server. The Add Virtual Image with Remote Server Details slide-in pane appears. (This option does not store the image on the local Cisco SD-WAN Manager server.)
  - For Cisco vManage Release 20.11.1 and later, follow these steps:
    1. Click Add New Virtual Image and choose Remote Server (preferred).
    2. In the Image Name field, enter the file name of the image.
    3. In the Image description field, enter a description of the image.
    4. (Optional) Click the Add Tags field and choose tags for the virtual image file.
    5. In the Select service type field, choose App-Hosting.
      
      The following applications are supported:
      
      UTD-Snort-Feature
      
      DRE-Optimization-Feature
      
      ThousandEyes-Enterpeise-Agent
      
      Cybervision-Enterprise-Agent
      
      For standard filenames, Cisco SD-WAN Manager automatically displays the attributes of the image file.
      
      For non-standard filenames, enter the following manually:
      
      App type: Choose an application type from the drop-down list.
      
      Enter version: Enter the version as free text.
      
      Cisco SD-WAN Manager automatically chooses the x86_64 architecture. You can choose a different architecture if necessary from the drop-down list.
    6. Click the Remote Server Name field and choose a remote server.
    7. In the Image File Path field, enter a path from the root directory of the remote server.
      
      If you do not enter a path, Cisco SD-WAN Manager uses the root directory.
    8. (Optional) To provide another server that contains the image, click Add Remote Server, and enter the details of the additional server.
    9. Click Add.
    Note
    Before choosing this option, ensure that you have registered a remote server with Cisco SD-WAN Manager. For more information on how to register a remote server, see Register Remote Server.
- Manager: Upload a file to the local Cisco SD-WAN Manager repository using a control-plane connection. This option is useful for uploading small files. The Upload VNF’s Package to Manager dialog box opens.
  1. Drag and drop the virtual image file to the dialog box or click Browse to select the virtual image file from a directory on the local Cisco SD-WAN Manager server.
  2. In the Description field, enter the description.
  3. In the drop-down list, choose Image Package or Scaffold.
  4. Click the Add Tags field and choose tags for the virtual image file.
  5. Click Upload to add the virtual image file to the repository.
- Remote Server - Manager: Store the virtual image file on a remote Cisco SD-WAN Manager server and download the virtual image file to Cisco Catalyst SD-WAN devices over an out-of-band management connection. The Upload VNF’s Package to Remote Server - Manager dialog box opens.
  1. In the Manager Hostname/IP Address field, enter the IP address of an interface on the Cisco SD-WAN Manager server that is in a management VPN (typically, VPN 512).
  2. Drag and drop the virtual image file to the dialog box or click Browse to select the virtual image file from a directory on the local Cisco SD-WAN Manager server.
  3. In the Description field, enter the description of the virtual image file.
  4. In the drop-down list, choose Image Package or Scaffold.
  5. Click the Add Tags field and choose tags for the virtual image file.
  6. Click Upload.
  Note
  
  To upload virtual images using the Manager or Remote Server - Manager options, use files with extensions, .tar, .gz, .tar or .qcow2. For more information on the steps to upload virtual images with extensions .tar, gz, .tar or .qcow2, refer to Upload VNF image
  
  .

After completing this task, the selected virtual images are added to the Cisco SD-WAN Manager repository and are available for deployment to network devices.

What to do next

Verify that the virtual images appear in the repository and are ready for deployment as needed.

Refer to related documentation for deploying or managing the uploaded images.

Upload the VNF Images

The VNF images are stored in the SD-WAN Manager software repository. These VNF images are referenced during service chain deployment, and then they are pushed to Cisco NFVIS during service chain attachment.

Procedure

From the SD-WAN Manager menu, choose Maintenance > Software Repository .
To add a prepackaged VNF image, click Virtual Images , and then click Upload Virtual Image .
Choose the location to store the virtual image.
- To store the virtual image on the local SD-WAN Manager server and download it to CSP devices over a control plane connection, click Manager . The Upload VNF’s Package to Manager dialog box appears.
  1. Drag and drop the virtual image file or the qcow2 image file to the dialog box or click Browse to choose the virtual image from the local SD-WAN Manager server. For example, CSR.tar.gz, ASAv.tar.gz, or ABC.qcow2
  2. If you upload a file, specify the type of the uploaded file: Image Package or Scaffold . Optionally, specify a description of the file and add custom tags to the file. The tags can be used to filter images and scaffold files when creating a service chain.
  3. If you upload a qcow2 image file, specify the service or VNF type: FIREWALL or ROUTER . Optionally, specify the following:
    - Description of the image
    - Version number of the image
    - Checksum
    - Hash algorithm
    You can also add custom tags to the file that can be used to filter images and scaffold files when creating a service chain.
    Note
    
    It is mandatory to upload a scaffold file if you choose a qcow2 image file.
    
    The option to select a qcow2 image file is available from Cisco SD-WAN Release 20.6.1 . In Cisco SD-WAN Release 20.6.1 and earlier releases, you can select only a tar.gz file.
  4. Click Upload to add the image to the virtual image repository. The virtual image repository table displays the added virtual image, and it available for installing on the CSP devices.
- To store the image on a remote SD-WAN Manager server and then download it to CSP devices, click Remote Server - Manager . The Upload VNF’s Package to Remote Server-Manager dialog box appears.
  1. In the Manager Hostname/IP Address field, enter the IP address of an interface on SD-WAN Manager server that is in the management VPN (typically, VPN 512).
  2. Drag and drop the virtual image file or the qcow2 image file to the dialog box, or click Browse to choose the virtual image from the local SD-WAN Manager server.
  3. If you upload a file, specify the type of the uploaded file: Image Package or Scaffold . Optionally, specify a description of the file and add custom tags to the file. The tags can be used to filter images and scaffold files when creating a service chain.
  4. If you upload a qcow2 image file, specify the service or VNF type: FIREWALL or ROUTER . Optionally, specify the following:
    - Description of the image
    - Version number of the image
    - Checksum
    - Hash algorithm
    You can also add custom tags to the file that can be used to filter images and scaffold files when creating a service chain.
    Note
    
    It is mandatory to upload a scaffold file if you choose a qcow2 image file.
    
    The option to select a qcow2 image file is available from Cisco SD-WAN Release 20.6.1 . In Cisco SD-WAN Release 20.6.1 and earlier releases, you can select only a tar.gz file.
  5. Click Upload to add the image to the virtual image repository. The virtual image repository table displays the added virtual image, and it is available for installing on the CSP devices.

You can have multiple VNF entries such as a firewall from same or from different vendors. Also, you can add different versions of VNF that are based on the release of the same VNF. However, ensure that the VNF name is unique.

Create a Customized VNF Image

You can upload one or more qcow2 images in addition to a root disk image as an input file along with VM-specific properties, bootstrap configuration files (if any), and generate a compressed TAR file. Through custom packaging, you can:

Create a custom VM package along with image properties and bootstrap files (if needed) into a TAR archive file.
Tokenize custom variables and apply system variables that are passed with the bootstrap configuration files.

Ensure that the following custom packaging requirements are met:

Root disk image for a VNF–qcow2
Day-0 configuration files–system and tokenized custom variables
VM configuration–CPU, memory, disk, NICs
HA mode–If a VNF supports HA, specify Day-0 primary and secondary files, NICs for a HA link.
Additional Storage–If more storage is required, specify predefined disks (qcow2), storage volumes (NFVIS layer)

Before you begin

Procedure

From the SD-WAN Manager menu, choose Maintenance > Software Repository .

Click Virtual Images > Add Custom VNF Package .

Configure the VNF with the following VNF package properties and click Save.

Table 2. VNF Package Properties
Field	Mandatory or Optional	Description
Package Name	Mandatory	The filename of the target VNF package. It’s the Cisco NFVIS image name with .tar or .gz extensions.
App Vendor	Mandatory	Cisco VNFs or third-party VNFs.
Name	Mandatory	Name of the VNF image.
Version	Optional	Version number of a program.
Type	Mandatory	Type of VNF to choose. Supported VNF types are: Router, Firewall, Load Balancer, and Other.

Note

To package a VM qcow2 image, click File Upload, and browse to choose a qcow2 image file.

To choose a bootstrap configuration file for VNF, if any, click Day 0 Configuration and click File Upload to browse and choose the file.

Include the following Day-0 configuration properties:

Table 3. Day-0 Configuration
Field	Mandatory or Optional	Description
Mount	Mandatory	The path where the bootstrap file gets mounted.
Parseable	Mandatory	A Day-0 configuration file can be parsed or not. Options are: Enable or Disable . By default, Enable is chosen.
High Availability	Mandatory	High availability for a Day-0 configuration file to choose. Supported values are: Standalone, HA Primary, HA Secondary.

Note

If any bootstrap configuration is required for a VNF, create a bootstrap-config or a day0-config file.

To add a Day-0 configuration, click Add , and then click Save . The Day-0 configuration appears in the Day 0 Config File table. You can tokenize the bootstrap configuration variables with system and custom variables. To tokenize variables of a Day-0 configuration file, click View Configuration File next to the desired Day-0 configuration file. In the Day 0 configuration file dialog box, perform the following tasks:

Note

The bootstrap configuration file is an XML or a text file, and contains properties specific to a VNF and the environment. For a shared VNF, see the Custom Packaging Details for Shared VNF topic and additional references in Cisco SD-WAN Cloud OnRamp for Colocation Solution Guide for the list of system variables that must be added for different VNF types. .
1. To add a system variable, in the CLI configuration dialog box, select, and highlight a property from the text fields. Click System Variable . The Create System Variable dialog box appears.
2. Choose a system variable from the Variable Name drop-down list, and click Done . The highlighted property is replaced by the system variable name.
3. To add a custom variable, in the CLI configuration dialog box, choose and highlight a custom variable attribute from the text fields. Click Custom Variable . The Create Custom Variable dialog box appears.
4. Enter the custom variable name and choose a type from Type drop-down list.
5. To set the custom variable attribute, do the following:
  - To ensure that the custom variable is mandatory when creating a service chain, click Type next to Mandatory .
  - To ensure that a VNF includes both primary and secondary day-0 files, click Type next to Common .
6. Click Done , and then click Save . The highlighted custom variable attribute is replaced by the custom variable name.
To upload extra VM images, expand Advance Options , click Upload Image , and then browse to choose an extra qcow2 image file. Choose the root disk, Ephemeral disk 1, or Ephemeral disk 2, and click Add . The newly added VM image appears in the Upload Image table.

Note

Ensure that you don’t combine ephemeral disks and storage volumes when uploading extra VM images.

To add the storage information, expand Add Storage , and click Add volume . Provide the following storage information and click Add. The added storage details appear in the Add Storage table.

Table 4. Storage Properties
Field	Mandatory or Optional	Description
Size	Mandatory	The disk size that is required for the VM operation. If the size unit is GiB, the maximum disk size can be 256 GiB.
Size Unit	Mandatory	Choose size unit. The supported units are: MIB, GiB, TiB.
Device Type	Optional	Choose a disk or CD-ROM. By default, disk is chosen.
Location	Optional	The location of the disk or CD-ROM. By default, it’s local.
Format	Optional	Choose a disk image format. The supported formats are: qcow2, raw, and vmdk. By default, it’s raw.
Bus	Optional	Choose a value from the drop-down list. The supported values for a bus are: virtio, scsi, and ide. By default, it’s virtio.

To add VNF image properties, expand Image Properties and enter the following image information.

Table 5. VNF Image Properties
Field	Mandatory or Optional	Description
SR-IOV Mode	Mandatory	Enable or disable SR-IOV support. By default, it’s enabled.
Monitored	Mandatory	VM health monitoring for those VMs that you can bootstrap. The options are: enable or disable. By default, it’s enabled.
Bootup Time	Mandatory	The monitoring timeout period for a monitored VM. By default, it’s 600 seconds.
Serial Console	Optional	The serial console that is supported or not. The options are: enable or disable. By default, it’s disabled.
Privileged Mode	Optional	Allows special features like promiscuous mode and snooping. The options are: enable or disable. By default, it’s disabled.
Dedicate Cores	Mandatory	Facilitates allocation of a dedicated resource (CPU) to supplement a VM's low latency (for example, router and firewall). Otherwise, shared resources are used. The options are: enable or disable. By default, it’s enabled.

To add VM resource requirements, expand Resource Requirements and enter the following information.

Table 6. VM Resource Requirements
Field	Mandatory or Optional	Description
Default CPU	Mandatory	The CPUs supported by a VM. The maximum numbers of CPUs supported are 8.
Default RAM	Mandatory	The RAM supported by a VM. The RAM can range 2–32.
Disk Size	Mandatory	The disk size in GB supported by a VM. The disk size can range 4–256.
Max number of VNICs	Optional	The maximum number of VNICs allowed for a VM. The number of VNICs can from range 8–32 and by default, the value is 8.
Management VNIC ID	Mandatory	The management VNIC ID corresponding to the management interface. The valid range is from 0 to maximum number of VNICs.
Number of Management VNICs ID	Mandatory	The number of VNICs.
High Availability VNIC ID	Mandatory	The VNIC IDs where high availability is enabled. The valid range is from 0–maximum number of VNICs. It shouldn’t conflict with management VNIC Id. By default, the value is 1.
Number of High Availability VNICs ID	Mandatory	The maximum number of VNIC IDs where high availability is enabled. The valid range is 0–(maximum number of VNICs-number of management VNICs-2) and by default, the value is 1.

To add day-0 configuration drive options, expand Day 0 Configuration Drive options and enter the following information.

Table 7. Day-0 Configuration Drive Options
Field	Mandatory or Optional	Description
Volume Label	Mandatory	The volume label of the Day-0 configuration drive. The options are: V1 or V2. By default, the option is V2. V2 is the config-drive label config-2. V1 is config-drive label cidata.
Init Drive	Optional	The Day-0 configuration file as a disk when mounted. The default drive is CD-ROM.
Init Bus	Optional	Choose an init bus. The supported values for a bus are: virtio, scsi, and ide. By default, it’s ide.

The Software Repository table displays the customized VNF image, and image is available for choosing when creating a custom service chain.

View VNF Images

Procedure

From the SD-WAN Manager menu, choose Maintenance > Software Repository .
Click Virtual Images .
To filter the search results, use the filter option in the search bar.

The Software Version column provides the version of the software image.

The Software Location column indicates where the software images are stored. Software images can be stored either in the repository on the SD-WAN Manager server or in a repository in a remote location.

The Version Type Name column provides the type of firewall.

The Available Files column lists the names of the VNF image files.

The Update On column displays when the software image was added to the repository.
For the desired VNF image, click ... and choose Show Info .

Delete a software image from the repository

Delete a software image from the vManage software repository to free up storage space and maintain an organized repository.

Remove outdated or unnecessary software images from the system.

This task is performed when you need to manage the software images stored in the vManage repository, such as when images are no longer needed or to optimize storage.

Deleting unused images helps prevent clutter and ensures that only relevant software versions are available for deployment.

Perform this task when a software image is no longer required for device upgrades or rollbacks.

Before you begin

Ensure you have access to the vManage software repository and the necessary permissions to delete images.

Verify that the image you want to delete is not currently being downloaded to a router.

Follow these steps to delete a software image from the repository:

Procedure

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Repository.
For the desired software image, click ... and choose Delete.

If a software image is being downloaded to a router, you cannot delete the image until the download process completes. After deletion, the image is removed from the repository and is no longer available for device upgrades or rollbacks.

What to do next

After deleting the image, verify that the repository contains only the required software images for your network operations.

Consider performing a repository audit to ensure no critical images were removed unintentionally.

Delete a software image

Delete unnecessary software images from a Cisco Catalyst SD-WAN device to free up storage and keep only relevant versions.

Maintain optimal device performance by removing unused software images.

This task is performed when you need to manage device storage or remove outdated software images from your Cisco Catalyst SD-WAN device.

Use this procedure in environments where multiple software versions are present and only certain versions are required.

Applicable for administrators managing software upgrades and device maintenance.

Before you begin

Ensure you have access to the Cisco SD-WAN Manager interface and appropriate permissions to delete software images.

Verify that the devices are connected and visible in the vManage dashboard.

Follow these steps to delete a software image from a Cisco Catalyst SD-WAN device:

Procedure

From the Cisco SD-WAN Manager menu, choose Maintenance > Software Upgrade.
Click WAN Edge, Control Components, or Manager.
Choose one or more devices from which to delete a software image.
Click the Delete Available Software.

The Delete Available Software dialog box opens.
Choose the software version to delete.
Click Delete.

The selected software image is removed from the device, freeing up storage and ensuring only required versions remain available.

What to do next

Verify that the deleted software image no longer appears in the device's available software list.

Confirm device functionality after image removal.