Release Notes for Cisco SD-WAN Cloud onRamp for Colocation Solution, Release 20.6.1


The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on standards documentation, or language that is used by a referenced third-party product.

Find all the information you need about this release—new features, known behavior, resolved and open bugs, and related information.

New Features

This section lists the new and modified features that are supported on the Cisco SD-WAN Cloud OnRamp for Colocation solution.

Important Note

Deactivate cluster workflow is not supported: The workflow to deactivate a cluster and then subsequently activate the cluster is not supported through vManage. Therefore, it is recommended to delete and recreate the cluster, instead.

Resolved and Open Bugs

About the Cisco Bug Search Tool

Use the Cisco Bug Search Tool to access open and resolved bugs for a release.

The tool allows you to search for a specific bug ID, or for all bugs specific to a product and a release.

You can filter the search results by last modified date, bug status (open, resolved), severity, rating, and support cases.

Bugs for Cisco SD-WAN Cloud OnRamp for Colocation Solution Release 20.6.1

This section details all fixed and open bugs for this release. These are available in the Cisco Bug Search Tool through the Resolved Bug Search.

Resolved Bugs for Cisco vManage

All resolved vManage bugs for this release are available in the Cisco Bug Search Tool through the Resolved Bug Search.

Bud ID



In the monitoring screen, Real-Time pnic_stats on vManage UI doesnt show Tx packets.


Service chain does not get attached if service chain QoS bandwidth is greater than 5GBPS.


Cluster deactivate is not supported when cluster is stuck in init state.


In multi-cluster case, when one cluster CCM task is in-progress, VNF install fails on other cluster.


Adding a new servicew chain to an attached service group when no resources are available saves service chain although service chain isn't provisioned.


When NTP is incorrectly entered as 72.163.32, it causes traffic blackhole as VLAN configuration is rejected by switch.


PAFW Day-0 configuration should have unique UUID and if it is changed to a variable, vManage cannot generate value for that UUID causing template attach of service chain to fail.


vManage should not allow user to configure Backup Server Settings when cluster is inactive.


Traffic fails when Cisco Catalyst 8000V is a single VNF chain and shared with another chain with firewall as the first VNF.


Add/Delete CSP with system ip conflict error followed by sync results in vManage time out.


vManage should mark multitenant cluster from Activate state to failure when template push fails.


Placement fails even if resources available with combination of SA and HA VNF's in the chain.


After vManage upgrade, bandwidth values for SRIOV PNICs are considered 10240 instead of 10000.


UI needs to validate RBAC username, not to have space in colocation cluster credentials page.


In vManage Monitor, the oubound VNIC of th first shared VNF shows other VLANs as well along with data VLANs.


In vManage Monitor > Network Functions, the last shared VNF that is deployed is not updated as shared VNF.


VNF Actions, START/STOP/ RESTART from the tenant page results in ERROR.


Attaching a shared service chain with only one VNF in the chain causes failure.

CSCvw31595 SG attach fails with Placement Failed Error - VM BW not met even though there are no SC's attached.


SG attach fails with error Failed to update configuration-Exception in interface xml {} null.


Allocated + Available is not equal to Total CPU/Memory in vManage UI.


Attaching Shared VNF as a single instance fails - java.lang.IndexOutOfBoundsException: Index: 1.


In multi-cluster case, when one cluster CCM task is in progress, VNF install fails on other cluster.


VNF stats shows empty for 1 hr data in network util/CPU util/Memory util/disk util.


ServiceChain Health Monitoring stats is empty for the last 1 hr data - "No data to Display".

Resolved Bugs for Device

All resolved device bugs for this release are available in the Cisco Bug Search Tool through the Resolved Bug Search.

Bud ID



Traffic fails when service group attach in template push to CCM fails - "Exception in Interface xml {} null".


Reattach service chain before detach complete results in template push fail- "Flavor already exists ".


VNF is Alive but the VNF image is not validated due to length > 128, VNF Install detach/attach.


One VM is in error state after hostaction reboot.


CSP device upgrade showed Success on vManage UI even though device rolled back.


Attaching or detaching of service groups fails due to configuration database being locked by session.


The attaching or detaching service chain causes failure some times and vManage shows the error–Outstanding changes in database on CSP.


pkt capture on VM OVS VNIC is not working for VMs that are deployed in Cisco NFVIS 4.1.1, 4.2.1, and master.

Open Bugs for Cisco vManage

All open Cisco vManage bugs for this release are available in the Cisco Bug Search Tool through the Open Bug Search.

Bug ID



Shared clouddock cluster activation shows FAILED after claiming its successful


If service-group is detached before VNF install completes configuration database is locked


CCM config rejection does NOT cause Cluster to be marked in "Failed" State


When trying to detach a service chain from cluster, if all steps are not completed by clicking complete and instead you go back to the browser, the detach option changes to attach option.


Editing and updating the description field of service group does not get saved.


Modifying a High Availability (HA) enabled service group to Non-HA service group returns an error and deletes all service chains in that Service Group.


Service group attach fails with error - "Error - Cannot create. Image already exists".


If service group is detached before VNF install completes, configuration database is locked.


VNF State shows green on vManage while VNF Install is still in progress and VNF is yet to be deployed.


After upgrading CSPs, data collection is stuck at queued state for CSPs in Rediscover Network.

Open Bugs for Device

All open device bugs for this release are available in the Cisco Bug Search Tool through the Open Bug Search.

Bug ID



No Proper error is displayed for RPC error reported on CCM "Colo-config-status" when switch rejects


Cat9k running config and CDB not in SYNC after RPC rejection due to limit of 63 vlans


End-End Ping fine but SCHM UNHEALTHY on MT cluster


Cluster activation failure due to management interface administratively down on Catalyst 9500-40X switch.


The service chain health monitoring fails on ~8 IPSEC terminated tunnels - eth105'. Failed to check data path health.


Cisco ASAv fails to boot up intermittently and is stuck.


NTP Clock doesn't sync causing certification install to fail on CSP.


After hostaction reboot , the VMs are stuck in rebooting state and multiple subsystems stopped on UCSC.

Software Requirements Matrix

Software Matrix

The following are the supported versions for Cisco Enterprise NFV Infrastructure Software, Cisco vManage, Cisco vBond Orchestrator, Cisco vSmart Controller, and Cisco Catalyst 9500 switches.



Cisco vManage Cisco vManage Release
Cisco vBond Orchestrator Cisco SD-WAN Release 20.6.1
Cisco vSmart Controller Cisco SD-WAN Release 20.6.1

Cisco Enterprise NFV Infrastructure Software (NFVIS)

Release 4.6.1

Cisco Catalyst 9500-40X and Cisco Catalyst 9500-48Y4C Release 17.3.1, 17.3.3

All release-specific information for Cisco vSmart Controllers, Cisco vBond Orchestrators, Cisco vManage is included in Cisco SD-WAN Release Notes.

The supported VNFs and Cisco PNFs in this solution are:


You must procure license for the required VNFs. Alternatively, you can choose to bring your own Day-0 configuration and repackage the VNFs, if required.

Table 1. Validated Cisco VNFs



Cisco CSR1000V

17.1.1, 17.2, 17.3.1a

Cisco Catalyst 8000V

17.4.1a, 17.5.1a

Cisco IOS XE SD-WAN Device

16.12.2r, 17.2.1r, 17.3.1a

Cisco ASAv

9.12.2, 9.13.1, 9.15.1

Cisco FTDv/NGFW, 6.5.0-115, 6.6.3

Cisco vEdge Cloud Router

19.2.1, 20.1.1, 20.3.1, 20.4.1, 20.5.1

Table 2. Validated Third-party VNFs



Palo Alto Firewall (PAFW)


Fortinet Firewall



R80.30, R80.40

Table 3. Validated Cisco PNFs



Cisco FTD

Model: FPR-9300, 6.5

Cisco ASR 1000 Series

17.1, 17.2, 17.3

Related Documentation