Reference a wrapper Chapter topic here
Read Me First
Related References
User Documentation
Communications, Services, and Additional Information
-
Sign up for Cisco email newsletters and other communications at: Cisco Profile Manager.
-
For information on the latest technical, advanced, and remote services to increase the operational reliability of your network visit Cisco Services.
-
To browse and discover secure, validated enterprise-class apps, products, solutions, and services, visit Cisco Devnet.
-
To obtain general networking, training, and certification titles from Cisco Press Publishers, visit Cisco Press.
-
To find warranty information for a specific product or product family, visit Cisco Warranty Finder.
-
To view open and resolved bugs for a release, access the Cisco Bug Search Tool.
-
To submit a service request, visit Cisco Support.
Documentation Feedback
To provide feedback about Cisco technical documentation use the feedback form available in the right pane of every online document.
Release Notes for Cisco SD-WAN Controllers, Cisco SD-WAN Release 20.5.x
 Note |
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. |
These release notes accompany the Cisco SD-WAN Controllers, Cisco SD-WAN Release 20.5.x, which provides Cisco SD-WAN capabilities. They include release-specific information for Cisco vSmart Controllers, Cisco vBond Orchestrators, Cisco vManage as applicable to Cisco SD-WAN Controllers.
For release information about Cisco IOS XE SD-WAN devices, refer to Release Notes for Cisco IOS XE SD-WAN Devices, Cisco IOS XE Release Bengaluru 17.5.x.
For release information about Cisco vEdge Devices, refer to Release Notes for Cisco vEdge Devices, Cisco SD-WAN Release 20.5.x.
What's New for Cisco SD-WAN Controllers Release 20.5.x
Cisco is constantly enhancing the SD-WAN solution with every release and we try and keep the content in line with the latest enhancements. The following table lists new and modified features we documented in the Configuration, Command Reference, and Hardware Installation guides.
What's New for Cisco IOS XE Release 17.5.x
This section applies to Cisco IOS XE SD-WAN devices.
| Feature | Description |
|---|---|
|
Cisco SD-WAN Getting Started |
|
|
Support for Deploying Cisco Catalyst 8000V Instances on Alibaba Cloud |
Starting from this release, Cisco Catalyst 8000V instances can be deployed on Alibaba Cloud. |
|
Cisco SD-WAN operates together with Cisco Smart Software Manager (CSSM) to provide license management through Cisco vManage. Cisco vManage can show available DNA licenses, assign licenses to devices, and report license consumption to CSSM. Cisco vManage can show available DNA licenses, assign licenses to devices, and report license consumption to CSSM. |
|
|
Cisco SD-WAN Support for the Cisco ASR 1006-X Platform with an RP3 Module |
Starting from this release, Cisco SD-WAN supports the Cisco ASR 1006-X platform with a Cisco ASR 1000 Series Route Processor 3 module installed. |
|
Systems and Interfaces |
|
|
This feature enables a device to automatically determine the bandwidth for WAN interfaces in VPN0 during day 0 onboarding by performing a speed test using an iPerf3 server. |
|
|
HTTP/HTTPS Proxy Server for Cisco vManage Communication with External Servers |
Cisco vManage uses HTTP/HTTPS to access some web services and for some REST API calls. Beginning Cisco vManage Release 20.5.1, you can channel the HTTP/HTTPS communication through an HTTP/HTTPS proxy server. |
|
This feature provides for the configuration of authorization, which authorizes commands that a user enters on a device before the commands can be executed, and accounting, which generates a record of commands that a user executes on a device. |
|
|
This feature introduces role-based access control (RBAC) based on sites or resource groups. It is a method of authorizing system access for users based on a combination of user groups and resource groups. For large Cisco SD-WAN deployments across multiple geographical locations, this feature helps you to split the network administration among different regional administrators. |
|
|
This feature allows you to review the last edited configuration when a configuration push to the device fails. A copy of the last edited configuration is saved and can be retrieved to allow edits to the configuration before the next push. |
|
|
This feature adds support for TCP MSS adjustment on Cisco IOS XE SD-WAN devices on both directions of the Cisco SD-WAN tunnel interface. |
|
|
This feature provides the option to clear the Don't Fragment bit in the IPv4 packet header for packets being sent out on a Cisco SD-WAN tunnel . When you clear the Don't Fragment configuration, packets larger than the interface MTU are fragmented before being sent. |
|
|
Migrate Single-Tenant Cisco SD-WAN Overlay to Multitenant Cisco SD-WAN Deployment |
You can migrate a single-tenant Cisco SD-WAN overlay to a multitenant deployment using a sequence of Cisco vManage API calls. |
|
This feature allows you to save the device template configuration changes in Cisco vManage, and then apply these configuration changes to multiple Cisco IOS XE SD-WAN devices later. The ability to save configuration changes simplifies generating larger device template configurations and applying them to devices. |
|
|
Enhancement to Jumbo Frames Support |
Jumbo Frames support is extended for 10 GE and 100 GE interfaces on Cisco IOS XE SD-WAN devices. Starting Cisco IOS XE Release 17.5.x, the MTU can range from 576 through 9216 bytes on these 10 GE and 100 GE interfaces. |
|
NAT Configuration Guide |
|
|
This feature allows you to advertise NAT routes through OMP to the branch routers. You can configure this feature only through Cisco vManage device CLI template. |
|
|
This feature enhances the service-side NAT functionality to include the ability to configure NAT pool and centralized data policy for static NAT mapping. If configured, the static NAT can only be applied if the data policy match conditions are met. |
|
|
Routing |
|
|
With this feature, the number of paths that can be exchanged between Cisco vSmart Controllers is increased to 128. |
|
|
This feature adds support for automatic selection of an RP candidate using a PIM BSR in an IPv4 multicast overlay. There is no single point of failure because every site has a local RP. A Cisco IOS XE SD-WAN device is selected as the RP, not a service-side device. |
|
|
Redistribution of Replicated BGP Routes into OSPF, EIGRP Protocols |
This feature allows you to leak (or replicate) BGP routes between the global VRF and service VPNs, and redistribute the leaked BGP routes. The redistribution of the leaked routes to the EIGRP and OSPF protocols occurs after replicating the BGP routes into the corresponding VRF. |
|
Policies |
|
|
This feature lets you match and set communities using a control policy. Control policies are defined and applied on Cisco SD-WAN devices to manipulate the communities. With this feature, you can match and assign single or multiple BGP community tags to your prefixes based on which routing policies can be manipulated. |
|
|
This feature enhances match action conditions to achieve parity with all the features configured on Cisco IOS XE SD-WAN devices while creating a centralized data policy. When you are setting up next-hop-loose action, this feature helps to redirect application traffic to an available route when next-hop address is not available. |
|
|
This feature introduces a new policy action fallback-to-best-path to pick the best path or color out of the available colors. When the data traffic does not meet any of the SLA class requirements, this feature allows you to select the best tunnel path criteria sequence using the option Fallback Best Tunnel option under each SLA class to avoid packet loss. |
|
|
You can now enable or disable logging of dropped packets in case of a link failure. You can also configure how often the packet flows are logged. |
|
|
Security |
|
|
Geolocation-Based Firewall Rules for Allowing or Denying Network Traffic Based on Geolocation |
This feature enables you to configure firewall rules for allowing or denying network traffic based on the source and destination location instead of IP addresses. This feature adds a new object group, geo, where you can specify countries and continents as objects in an Access Control List (ACL). An object group ACL simplifies policy creation in large networks, especially if the ACL changes frequently. New object-group and geo commands were added. |
|
This feature automates the provisioning of tunnels from Cisco SD-WAN routers to Zscaler. Using your Zscaler partner API credentials, you can automatically provisions tunnels to Zscaler Internet Access (ZIA) Public Service Edges. You can choose Zscaler in the Cisco Security Internet Gateway (SIG) and SIG credentials feature templates to automate tunnel provisioning. |
|
| With this feature, Cisco IOS XE SD-WAN devices can exchange SGT over the overlay network using SXP. Use SXP when your hardware does not support the inline propagation
of SGTs.
This feature also extends support for SGACL enforcement on Cisco IOS XE SD-WAN devices by configuring SGACL policies. |
|
|
This feature lets you customize the amount of resources that Unified Threat Defense features use on a router. You can use larger resource profiles to process packets simultaneously. Simultaneously processing packets reduces the latency that security features can introduce to the packet processing of the device. |
|
|
High Availability |
|
|
This feature provides support for disaster recovery for a Cisco vManage deployment with a single primary node. |
|
|
Cloud OnRamp |
|
|
This feature adds the ability to balance traffic for cloud applications across multiple direct internet access (DIA) interfaces. |
|
|
Support for Pay As You Go License for Cisco Catalyst 8000V Edge Software Instances |
Added support for using Cisco Catalyst 8000V Edge Software instances with pay as you go (PAYG) licenses when creating a new cloud gateway in Amazon Web Services (AWS), in addition to the previously supported bring your own license (BYOL) model. |
|
RMA Support for Cisco CSP Devices (Cloud onRamp for Colocation) |
This feature allows you to replace a faulty CSP device by creating backup copies of the device, and then restoring the replacement device to a state it was in before the replacement. The VMs running in HA mode operate uninterrupted with continuous flow of traffic during device replacement. |
|
Clone Service Groups in Cisco vManage (Cloud onRamp for Colocation) |
This feature allows you to create copies of service groups for different RBAC users, without having to enter the same configuration information multiple times. By cloning a service group, you can easily create service chains by leveraging the stored service chain templates. |
|
Colocation Multitenancy Using Role-Based Access Control (Cloud onRamp for Colocation) |
This feature enables a service provider to manage multiple colocation clusters and share these clusters across tenants by using multiple colocation groups. In a multitenant setup, service providers don't need to deploy a unique colocation cluster for each tenant. Instead, the hardware resources of a colocation cluster are shared across multiple tenants. With multitenancy, service providers ensure that tenants view only their data by restricting access based on roles of individual tenant users. |
|
You can deploy a Cisco Catalyst 8000v Edge Software (Cisco Catalyst 8000V) instance as the interconnect gateway in the Megaport fabric and connect an SD-WAN branch location to the interconnect gateway. From the interconnect gateway, you can create software-defined interconnects to an AWS cloud onramp or another interconnect gateway in the Megaport fabric. |
|
|
This feature enables you to specify the service area that your Microsoft 365 application belongs to. |
|
|
This release enables the use of the AWS TGW Connect feature to connect a cloud gateway to an AWS Transit Gateway. This GRE based connection type offers improved bandwidth, scaling, and security compared to the use of IPSec VPN tunnel connections. |
|
|
This feature leverages the AWS Transit Gateway support to connect branch devices to the cloud. The branch devices connect to transit gateway using an IPSec tunnel-based secure channel to access the applications hosted in the cloud. This feature supports scenarios where Cisco vManage instantiates, manages, and controls the AWS Transit Gateway. |
|
|
The feature allows branch sites to access workloads running in the Google Cloud. It also allows branch sites to send and receive traffic across different regions and sites through Google Global Network. As part of the solution, cloud gateways are instantiated in different regions. Cloud gateways consist of a pair of Cisco Catalyst 8000V instances with their interfaces anchored in three different VPCs. This feature supports site-to-cloud and site-to-site connectivity. |
|
|
AppQoE |
|
|
Support for Additional Platforms as Controllers for AppQoE Service Nodes |
This release extends the service controller role to additional device models—C8500L-8S4X and ASR1006-X. |
|
This feature enables a programmatic setting of the maximum transmission unit (MTU) size to 1500 for the network connecting the service controllers and service nodes. This automation prevents broken communication due to packet fragmentation that can bring down the throughput requirements. |
|
|
This release extends DRE to Cisco SD-WAN. DRE is a compression technology that reduces the size of data transmitted over the WAN and enables more effective utilization of the WAN. |
|
|
This feature provides an express method for configuring an intent-based performance monitor with the help of predefined monitoring profiles. Configure this feature using the CLI Add-on feature template in Cisco vManage. |
|
|
Monitor and Maintain |
|
|
View Loss Percentage, Latency, Jitter, and Octet Information for Tunnels |
This feature provides a single chart option in Cisco vManage for viewing tunnel information, such as packet loss, latency, jitter, and octets. |
|
This feature enhances the monitoring of Unified Threat Defense (UTD) features on Cisco SD-WAN devices. The feature allows you to view the CPU, memory, and traffic usage on your device. You can also view the health of individual UTD features. |
|
|
This feature optimises the alarms on Cisco vManage by automatically suppressing redundant alarms. This allows you to easily identify the component that is causing issues. You can view these alarms in . |
|
|
SNMP |
|
|
This feature enables you to configure SNMP using a CLI template or a CLI add-on feature template. You can also encrypt the supported variables in the CLI configuration. |
|
|
Plug and Play |
|
|
You can now monitor and troubleshoot your Day-0 device onboarding using WebUI through PnP onboarding. If the automated PnP onboarding fails, you can manually onboard your device. |
|
| Admin-Tech Enhancement |
With this feature, the admin tech file now includes the show platform hardware qfp active classification feature-manager statistics command, which displays CFM error statistics. |
What's New for Cisco SD-WAN Release 20.5.x
This section applies to Cisco vEdge devices.
| Feature | Description |
|---|---|
|
Systems and Interfaces |
|
|
HTTP/HTTPS Proxy Server for Cisco vManage Communication with External Servers |
Cisco vManage uses HTTP/HTTPS to access some web services and for some REST API calls. Beginning Cisco vManage Release 20.5.1, you can channel the HTTP/HTTPS communication through an HTTP/HTTPS proxy server. |
|
This feature provides for the configuration of authorization, which authorizes commands that a user enters on a device before the commands can be executed, and accounting, which generates a record of commands that a user executes on a device. |
|
|
This feature introduces role-based access control (RBAC) based on sites or resource groups. It is a method of authorizing system access for users based on a combination of user groups and resource groups. For large Cisco SD-WAN deployments across multiple geographical locations, this feature helps you to split the network administration among different regional administrators. |
|
|
Migrate Single-Tenant Cisco SD-WAN Overlay to Multitenant Cisco SD-WAN Deployment |
You can migrate a single-tenant Cisco SD-WAN overlay to a multitenant deployment using a sequence of Cisco vManage API calls. |
|
Routing |
|
|
With this feature, the number of paths that can be exchanged between Cisco vSmart Controllers is increased to 128 limit. |
|
|
Policies |
|
|
This feature enhances match action conditions in a centralized data policy for parity with the features configured on Cisco vEdge devices. When you are setting up next-hop-loose action, this feature helps to redirect application traffic to an available route when next-hop address is not available. |
|
|
This feature introduces a new policy action fallback-to-best-path to pick the best path or color out of the available colors. When the data traffic does not meet any of the SLA class requirements, this feature allows you to select the best tunnel path criteria sequence using the Fallback Best Tunnel option under each SLA class to avoid packet loss. |
|
|
This feature introduces a configurable delay (dampening) mechanism on data plane tunnels to minimize the effects of tunnel flapping on the WAN links. The dampening process removes a tunnel from the SLA class until it stops flapping and becomes stable. |
|
|
Security |
|
|
This features integrates the Layer 7 Health Check feature with automatic tunnels to SIGs. When you create an automatic tunnel using the Cisco Secure Internet Gateway (SIG) template to Zscaler or Cisco Umbrella, a tracker is also created to monitor and load balance or failover tunnels. You can customize the parameters based on which the tracker load balances or fails over tunnels. |
|
|
This feature automates the provisioning of tunnels from Cisco SD-WAN routers to Zscaler. Using your Zscaler partner API credentials, you can automatically provisions tunnels to Zscaler Internet Access (ZIA) Public Service Edges. You can choose Zscaler in the Cisco Security Internet Gateway (SIG) and SIG credentials feature templates to automate tunnel provisioning. |
|
|
High Availability |
|
|
This feature provides support for disaster recovery for a Cisco vManage deployment with a single primary node. |
|
|
Cloud OnRamp |
|
|
RMA Support for Cisco CSP Devices (Cloud onRamp for Colocation) |
This feature allows you to replace a faulty CSP device by creating backup copies of the device, and then restoring the replacement device to a state it was in before the replacement. The VMs running in HA mode operate uninterrupted with continuous flow of traffic during device replacement. |
|
Clone Service Groups in Cisco vManage (Cloud onRamp for Colocation) |
This feature allows you to create copies of service groups for different RBAC users, without having to enter the same configuration information multiple times. By cloning a service group, you can easily create service chains by leveraging the stored service chain templates. |
|
Colocation Multitenancy Using Role-Based Access Control (Cloud onRamp for Colocation) |
This feature enables a service provider to manage multiple colocation clusters and share these clusters across tenants by using multiple colocation groups. In a multitenant setup, service providers don't need to deploy a unique colocation cluster for each tenant. Instead, the hardware resources of a colocation cluster are shared across multiple tenants. With multitenancy, service providers ensure that tenants view only their data by restricting access based on roles of individual tenant users. |
|
Monitor and Maintain |
|
|
View Loss Percentage, Latency, Jitter, and Octet Information for Tunnels |
This feature provides a single chart option in Cisco vManage for viewing tunnel information, such as packet loss, latency, jitter, and octets. |
|
This feature enhances the monitoring of Unified Threat Defense (UTD) features on Cisco SD-WAN devices. The feature allows you to view the CPU, memory, and traffic usage on your device. You can also view the health of individual UTD features. |
|
|
This feature optimises the alarms on Cisco vManage by automatically suppressing redundant alarms. This allows you to easily identify the component that is causing issues. You can view these alarms in . |
|
|
This feature is used to debug any packet loss on Cisco vEdge devices in the forwarding plane. |
|
|
SNMP |
|
|
Support introduced for AES-256 bit Authentication Protocol called SHA-256. |
|
Cisco vManage Upgrade Paths
For information about Cisco vManage upgrade procedure, see Upgrade Cisco vManage Cluster.
| Starting Cisco vManage Version | Destination Version | ||||||||
|---|---|---|---|---|---|---|---|---|---|
|
19.2.x |
20.1.x |
20.3.x |
20.4.x |
20.5.x |
|||||
|
18.x/19.2.x |
Direct Upgrade |
Direct Upgrade |
Check disk space*
For cluster upgrade procedure**: request nms configuration-db upgrade
|
Step upgrade through 20.3.x |
Step upgrade through 20.3.x |
||||
|
20.1.x |
Not Supported |
Direct Upgrade |
Direct Upgrade For cluster upgrade procedure**: request nms configuration-db upgrade
|
Direct Upgrade For cluster upgrade procedure**: request nms configuration-db upgrade
|
Step upgrade through 20.3.x |
||||
|
20.3.x |
Not Supported |
Not Supported |
Direct Upgrade |
Direct Upgrade |
Direct Upgrade For cluster upgrade procedure**: request nms configuration-db upgrade
|
||||
|
20.4.x |
Not Supported |
Not Supported |
Not Supported |
Direct Upgrade |
Direct Upgrade For cluster upgrade procedure**: request nms configuration-db upgrade
|
||||
*To check the free disk space using CLI,
-
Use the vshell command to switch to vshell
-
In vshell, use the df -kh | grep boot command
**Cluster upgrade must be performed using CLI
-
Use the following command to upgrade the configuration database . This must be done on one node only in the cluster:
request nms configuration-db upgradeNote
We recommend the data base size in the disk is less than or equal to 5GB. Use the
request nms configuration-db diagnosticcommand to check the data base size. This is applicable only for upgrades of devices running Cisco vManage Release 20.1.1 and later.
-
Enter login credentials, if prompted. Login credentials are prompted if all vManage server establish control connection with each other. After a successful upgrade, all configuration-db services are UP across the cluster and the application-server is started.
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 Controllers Release 20.5.1.2
This section details all fixed and open bugs for this release. These bugs are available in the Cisco Bug Search Tool
Resolved Bugs for Cisco SD-WAN Controllers Release 20.5.1.2
|
Bug ID |
Description |
|---|---|
|
Evaluation of Cisco SD-WAN for Log4j 2.x DoS vulnerability fixed in 2.17 |
Bugs for Cisco SD-WAN Controllers Release 20.5.1.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 SD-WAN Controllers Release 20.5.1.1
|
Bug ID |
Description |
|---|---|
|
Evaluation of Cisco vManage for Log4j RCE (Log4Shell) vulnerability |
Bugs for Cisco SD-WAN Controllers Release 20.5.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 SD-WAN Controllers Release 20.5.1
|
Bug ID |
Description |
|---|---|
|
snmp trap source interface template changes for Cisco IOS XE SD-WAN device not present |
|
|
MTT Network > Device> Real Time options wont be displayed if we login with SSO |
|
|
Cisco vManage: neo4j transient exception - database not upto the required version |
|
|
Vedge devices' BIDNTVRFD remote error to a new primary DC |
|
|
Select control connection TAB for any vsmarts, it will never show vbond connections |
|
|
Cisco vManage WebServer uses a hard coded self-signed certificate |
|
|
vSmart Upgrade From 20.1.12 to 20.3.1 Failing With Error "Failed to install: " |
|
|
Cisco vManage is not generating the TLS Proxy Certificate after Device comes online |
|
|
SG attach fails with Placement Failed Error - VM BW not met even though there are no SC's attached |
|
|
vBond/vSmart Upgrade Failed and Rollback due to Upgrade confirm not received. |
|
|
Prompt an error on CLI when Cisco vManage boot partition is full |
|
|
Cisco IOS XE SD-WAN device Unable to configure ospf simple password authentication |
|
|
VNF Install fail - VNF packages are not sync'd/copied in new added Cisco vManage node in Cisco vManage cluster |
|
|
Upgrade 20.3->20.4, ND Profile->LAN page does not show global vlan, spanning-tree and native-vlan |
|
|
Checkbox is not usable under Update Device Template tab |
|
|
add device check for alarm process |
|
|
ND Profile -> LAN preview does not show global VLAN, spanning-tree and/or trunk native VLAN info |
|
|
Fail to upload images to software repository post Cisco vManage upgrade to 19.2.4 |
|
|
Generic SIG template is not getting added to device Template |
|
|
Cisco vManage - TACACS requests are sourced from old interface IP after IP changed |
|
|
Cisco vManage: Template push may fail after upgrading to 20.4 |
Open Bugs for Cisco SD-WAN Controllers Release
|
Bug ID |
Description |
|---|---|
|
[SIT] AWS instance Cisco vManage unable to reach devices after upgrade to 20.5.999 image |
|
|
Audit log not generating for any action on 20.5 |
|
|
1 Cisco vManage GUI login lead 4 PAM login failures so two GUI login failure lead to account lock |
|
|
CLI template does not push logging buffered community config |
|
|
Cisco vManage pushes its own configurations to the Cisco IOS XE SD-WAN device |
|
|
Serviceability: provide a way to check the config-db file size |
|
|
Edit of a SG which is already attached to the cluster doesnt allow SC edit to match placement req |
|
|
Stats DB configuration is not available on vmange GUI |
|
|
Destination device drop-down doesn't show devices after speed test run |
|
|
VM lifecycle events does NOT show in Monitor-> Events Page |
|
|
Configuratoin upgrade in cluster failed in 20.3.3 code |
|
|
MTT : SD-AVC REST APIs calls task stuck in scheduled state after creating / editing custom appli |
|
|
Seeing full GC allocation failure with 20.3.2.1 code |
|
|
VNF Actions on Tenant Page result in ERROR |
|
|
Cisco vManage MTT 20.4.1 bringup on c5.18xlarge fails |
|
|
df -kh output is misleading and Cisco vManage platform until we reload the VM |
|
|
Invalid info for "Cloud Provider Management Reference" column showing AWS reference for GCP |
|
|
Object Object error upon login on new Cisco vManage deployed using ova |
|
|
"ip network-broadcast" command on Cisco vManage Templates for Cisco IOS XE SD-WAN devices missing |
|
|
After Cisco vManage upgrade, BW values for SRIOV Pnics are considered 10240 instead of 10000 |
|
|
ompd not responsive after generating admin tech on 20.3.2 |
|
|
Policy Template push failure from Cisco vManage 20.4.1.1 to 17.2 |
|
|
vSmarts crashing due to OOM after upgrade to 20.4.1.1 |
|
|
Cisco vManage: motd api will retrieve line break by removing the slash character and keeping "n" |
|
|
BGP Template configuration not working Properly on CoR for IaaS AWS |
|
|
Navigating to device details URL in Cisco vManage results in re-direct |
|
|
Cisco vManage manage-user function is not working properly |
|
|
Changing Config-DB ID/Password from default to non-default on a cluster of more than 3 members |
|
|
PWK - Overlay tunnel goes down with overnight traffic (No Crash) |
|
|
Adding a new SC to an attached SG when no resources available saves SC although SC not provisioned |
|
|
Call Feature Template: Number Pattern does not accept characters '[ ]' , '$' and '^' |
|
|
Cisco vManage dashboard doesn't show device status even when control is up/up |
|
|
Destination device drop-down doesn't show devices after speed test run |
|
|
Configuration DB upgrade in cluster failed in 20.3.3 code |
|
|
MTT : SD-AVC REST APIs calls task stuck in scheduled state after creating / editing custom appli |
|
|
Data collection status stuck in Queued state after performing VNF start/stop/reboot |
|
|
Cisco vManage MTT 20.4.1 bringup on c5.18xlarge fails |
|
|
Cisco vManage boots up with TLOC in down state after reset of WAN interface or reinstall of the root-chain |
|
|
Cisco vManage Multicoud on ramp, cant attach 8kv - GUI form cant see the UUIDs entered |
|
|
Cisco vManage template: Object-group still in use, can't be emptied.Error received from the device is |
Controller Compatibility Matrix and Server Recommendations
For compatibility information and server recommendations, see Cisco SD-WAN Controller Compatibility Matrix and Server Recommendations.
Related Documentation
Full Cisco Trademarks with Software License
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
Feedback