Reference a wrapper Chapter topic here
Read Me First
 Note |
To achieve simplification and consistency, the Cisco SD-WAN solution has been rebranded as Cisco Catalyst SD-WAN. In addition, from Cisco IOS XE SD-WAN Release 17.12.1a and Cisco Catalyst SD-WAN Release 20.12.1, the following component changes are applicable: Cisco vManage to Cisco Catalyst SD-WAN Manager, Cisco vAnalytics to Cisco Catalyst SD-WAN Analytics, Cisco vBond to Cisco Catalyst SD-WAN Validator, Cisco vSmart to Cisco Catalyst SD-WAN Controller, and Cisco Controllers to Cisco Catalyst SD-WAN Control Components. See the latest Release Notes for a comprehensive list of all the component brand name changes. While we transition to the new names, some inconsistencies might be present in the documentation set because of a phased approach to the user interface updates of the software product. |
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 vEdge Device, Cisco SD-WAN Release 20.6.x
Note |
To achieve simplification and consistency, the Cisco SD-WAN solution has been rebranded as Cisco Catalyst SD-WAN. In addition, from Cisco IOS XE SD-WAN Release 17.12.1a and Cisco Catalyst SD-WAN Release 20.12.1, the following component changes are applicable: Cisco vManage to Cisco Catalyst SD-WAN Manager, Cisco vAnalytics to Cisco Catalyst SD-WAN Analytics, Cisco vBond to Cisco Catalyst SD-WAN Validator, Cisco vSmart to Cisco Catalyst SD-WAN Controller, and Cisco Controllers to Cisco Catalyst SD-WAN Control Components. See the latest Release Notes for a comprehensive list of all the component brand name changes. While we transition to the new names, some inconsistencies might be present in the documentation set because of a phased approach to the user interface updates of the software product. |
These release notes accompany the Cisco SD-WAN Release 20.6.x, which provides Cisco Catalyst SD-WAN capabilities. They include release-specific information for Cisco Catalyst SD-WAN Controllers, Cisco Catalyst SD-WAN Validators, Cisco SD-WAN Manager as applicable to Cisco vEdge devices.
Related Releases
For release information about Cisco IOS XE Catalyst SD-WAN devices, refer to Release Notes for Cisco IOS XE SD-WAN Devices, Cisco IOS XE Release 17.6.x.
For release information about Cisco Catalyst SD-WAN Control Components, refer to Release Notes for Cisco Catalyst SD-WAN Control Components, Cisco Catalyst SD-WAN Control Components Release 20.6.x
What's New for Cisco SD-WAN Release 20.6.x
This section applies to Cisco vEdge devices.
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. For information on additional features and fixes that were committed to the SD-WAN solution, see the Resolved and Open Bugs section in the Release Notes.
| Feature | Description |
|---|---|
|
This feature provides support for configuring Cisco SD-WAN Manager alerts to generate an alarm and a syslog message for any disaster recovery workflow failure or event that occurs. |
|
|
This feature allows you to reset the RSA private and public keys, and generate a CSR that uses a new key pair. In earlier releases, the generation of CSR used the existing key pair. |
| Feature | Description |
|---|---|
|
Support to Configure NTP Server using Localized Policy CLI |
This feature allows you to configure the NTP server feature on Cisco SD-WAN devices using the Cisco SD-WAN Manager localized CLI policy. |
| Feature | Description |
|---|---|
|
Cisco Catayst SD-WAN Getting Started |
|
|
Simplifies adding Cisco SD-WAN Manager servers to a cluster by identifying servers based on personas. A persona defines what services run on a server. |
|
|
Support for Reverse Proxy with Cisco IOS XE Catalyst SD-WAN Devices and Cisco SD-WAN Multitenancy |
With this feature, you can deploy a reverse proxy device in your overlay network between Cisco IOS XE Catalyst SD-WAN devices and Cisco SD-WAN Manager and Cisco SD-WAN Controller. Also, this feature enables you to deploy a reverse proxy device in both single-tenant and multitenant overlays that include Cisco vEdge or Cisco IOS XE Catalyst SD-WAN edge devices. |
|
Systems and Interfaces |
|
|
Dual Endpoint support for interface status tracking on Cisco vEdge devices |
This feature allows you to configure tracker groups with dual endpoints using the Cisco SD-WAN Manager System template and associate each template group to an interface. The dual endpoints provide redundancy for tracking the status of transport interfaces to avoid false negatives. |
|
This feature allows you to create users and user groups with required read and write permissions for Cisco SD-WAN Manager policies. RBAC for policies provides users with the access to all the details of policies to help maximize the operational efficiency. It makes it easier to meet configuration requirements and guarantees that authorized users on the system are only given access to what they need. |
|
|
With this feature, a service provider can control the number of WAN edge devices a tenant can add to their overlay network. By doing so, the provider can utilize Cisco Catalyst SD-WAN control components resources efficiently. |
|
|
This feature enables you to migrate a multitenant Cisco Catalyst SD-WAN overlay comprising shared Cisco SD-WAN Manager instances and Cisco SD-WAN Validator, and tenant-specific Cisco SD-WAN Validator to a multitenant overlay comprising shared Cisco SD-WAN Manager instances, Cisco SD-WAN Validator, and Cisco vSmart Controllers. |
|
|
Routing |
|
|
Route Manipulation for Leaked Routes with OMP Administrative Distance |
This feature allows you to configure the OMP administrative distance option to prefer OMP routes over MPLS routes. |
|
Policies |
|
|
This feature extends Network-Based Application Recognition (NBAR) support to Cisco SD-WAN vEdge devices. |
|
|
This feature is an enhancement to support more than six SLA classes per policy on Cisco SD-WAN devices. |
|
|
Application-aware Routing and Data Policy SLA Preferred Colors |
This feature provides different behaviors to choose preferred colors based on the SLA requirements when both application-aware routing policy and data policies are configured. |
|
Cisco Catalyst SD-WAN Security |
|
|
Authentication Types |
The authentication types supported from Cisco SD-WAN Release 20.6.1 differ from the authentication types supported in Cisco SD-WAN Release 20.5.1 and earlier releases. For a Cisco vEdge device running Cisco SD-WAN Release 20.5.1 or earlier, if you have configured authentication types using the Cisco Security feature template, you must update the the authentication types in the template after you upgrade the device software to Cisco SD-WAN Release 20.6.1 or later. To update the authentication types, do the following:
|
|
Cloud OnRamp |
|
|
This feature allows you to connect to Cloud onRamp for SaaS by means of a SIG tunnel. Cloud onRamp for SaaS over SIG tunnels provides you secure access to the SaaS applications, and the capability to automatically select the best possible SIG tunnel for accessing the SaaS applications. |
|
|
Cisco Catalyst SD-WAN Monitor and Maintain |
|
|
Generate System Status Information for a Cisco SD-WAN Manager Cluster Using Admin Tech |
This feature adds support for generating an admin-tech file for a Cisco SD-WAN Manager cluster. The admin-tech file is a collection of system status information intended for use by Cisco Catalyst SD-WAN Technical Support for troubleshooting. Prior to this feature, Cisco Catalyst SD-WAN was only able to generate an admin-tech file for a single device. |
|
This feature adds support for viewing generated admin-tech files whenever the admin-tech files are available on a device. You can view the list of generated admin-tech files and then decide which files to copy from your device to Cisco SD-WAN Manager. You can then download the selected admin-tech files to your local device, or delete the downloaded admin-tech files from Cisco SD-WAN Manager, the device, or both. |
|
|
Embedded Packet Capture for Cisco vEdge Devices Using CLI Commands |
This feature provides an alternative method to capture traffic data to troubleshoot connectivity issues between Cisco vEdge devices and Cisco SD-WAN Manager using supported CLI commands. As part of this feature, the following commands are introduced to capture traffic details: - request stream capture - show packet-capture details |
|
This feature adds support for real time monitoring of numerous device configuration details including routing, license, policy, Cloud Express, Cisco SD-WAN Validator, TCP optimization, SFP, tunnel connection, license, logging, and Cisco Umbrella information. Real time monitoring in Cisco SD-WAN Manager is similar to using show commands in the CLI of a device. There are many device configuration details for Cisco SD-WAN Manager. Only a subset of the device configuration details is added in Cisco IOS XE Release 17.6.1a and Cisco vManage Release 20.6.1. |
|
|
This feature allows you to disable data collection for Cisco Catalyst SD-WAN telemetry using Cisco SD-WAN Manager. Data collection for telemetry is enabled by default. |
|
|
This feature lets you view detailed information about the flow of traffic from a device. You can use this information to assist with troubleshooting. |
|
|
This feature adds support to include template and policy configuration details in audit logs. You can view the current and previous configuration details for any action in Cisco SD-WAN Manager. |
|
|
This feature lets you view detailed information about the flow of traffic from a device. |
|
|
Cisco Catalyst SD-WAN SNMP |
|
|
This feature adds support for receiving the following SNMP trap notifications:
|
|
Important Notes, Known Behavior, and Workaround
-
Starting from Cisco SD-WAN Release 20.5.1, Cloud onRamp for IaaS isn't supported for Cisco vEdge Cloud Router running on Cisco SD-WAN Release 20.5.1. However, Cloud onRamp for IaaS is supported with AWS as the cloud provider for Cisco vEdge Cloud Routers using Cisco SD-WAN Release 20.4.1 and earlier. Cloud onRamp for IaaS is also supported with Microsoft Azure as the cloud provider for Cisco vEdge Routers using Cisco SD-WAN Release 20.3.1 and earlier.
-
In Cisco SD-WAN Release 20.5.1, the cloud-init bootstrap configuration that you generate for the Cisco vEdge Cloud Router cannot be used for deploying the Cisco Cloud vEdge Router running on Cisco SD-WAN Release 20.5.1. However, you can use the bootstrap configuration for deploying the Cisco vEdge Cloud Router running on Cisco SD-WAN Release 20.4.1 and earlier versions.
- Cisco vManage Release 20.3.1 implements a hardened security posture to comply with FedRamp guidelines. As a result, your vAnalytics login credentials that are stored locally get erased on upgrading the software, and you cannot access the vAnalytics service directly through Cisco SD-WAN Manager. In this case, log in to vAnalytics using this URL: https://analytics.viptela.com. If you can’t find your vAnalytics login credentials, open a case with Cisco TAC support.
-
For Cisco SD-WAN Release 20.4.1, you must run the messaging server on all the active instances of the Cisco SD-WAN Manager cluster when deploying the Cisco SD-WAN Manager cluster. See the High Availability Configuration Guide for vEdge Routers for more information.
-
For information about upgarde paths, see Cisco vManage Upgrade Paths.
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 Release 20.6.7
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 Release 20.6.7
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge device cannot resolve Cisco SD-WAN Validator on the loopback interface. |
|
|
On Cisco vEdge 1000 device, customer is seeing the clock getting reset after RTC reports PWRFAIL. |
|
|
Cisco vEdge device symnat flag got stuck even when not behind nat. |
|
|
Cisco vEdge device is crashing due to FP Core dying. |
|
|
The "show bfd history" is not showing the "up" status after BFD tunnel recovers from flapping on Hub Cisco vEdge device. |
|
|
BFD Tunnel convergence is taking couple more seconds longer. |
|
|
Cisco ISR1100 : Interface went up/down state with speed 100m and no auto-neg configured post upgrade to 20.6 |
|
|
Cisco vEdge device version 20.6.5.3 are not generating Alarms for High CPU. |
Bugs for Cisco SD-WAN Release 20.6.6
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 Release 20.6.6
| Identifier | Headline |
|---|---|
|
Interface diagnostic commands won't show desired output on code 20.6.3.2 for Cisco vEdge-2000. |
|
|
Current flows are not getting cleared post disabling app-visibility. |
|
|
20.8: On-Demand tunnel not coming up between Cisco vEdge device and Cisco IOS XE Catalyst SD-WAN device sites. |
|
|
Cisco vEdge-1000/ 20.6.5 / SSHd and vConfd spiking CPU up to 100%. |
|
|
The DNS Cache populating without a valid response. |
|
|
I2C bus gets hang leading h/w operation application failiure on 20.6 |
|
|
Cisco vEdge-2000 ftmd daemon crash. Signal 10. |
|
|
Cisco vEdge device: Same label is assigned to different vpns. |
|
|
Tracker on Cisco vEdge device does not come up after reboot. |
Open Bugs for Cisco SD-WAN Release 20.6.6
| Identifier | Headline |
|---|---|
|
On Cisco vEdge-1000, Customer is seeing the clock getting reset after RTC reports PWRFAIL. |
|
|
Port number that is lower than 1024 are chosen as the DIA NAPT source port in Cisco vEdge device. |
|
|
Cisco vEdge-2000 - Fiber interfaces go down randomly. |
|
|
The "show bfd history" not showing the "up" status after BFD tunnel recovers from flapping on Hub Cisco vEdge device. |
|
|
Cisco vEdge-5000 upgrade failure from 20.6 to 20.9 |
|
|
High CPU in Cisco vEdge device caused by minigzip process. |
|
|
Microsoft Azure: Cisco vEdge device/Cisco Catalyst SD-WAN Controller VHD image doesn't prompt initial admin password wizard. |
|
|
[SITLite] After deconfigure ipsec+pwk , unable to recover all bfd sessions |
Bugs for Cisco SD-WAN Release 20.6.5.4
Resolved Bugs for Cisco SD-WAN Release 20.6.5.4
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge 5000 device inbuilt certificate expiring on 12th November 2023 |
Bugs for Cisco SD-WAN Release 20.6.5.3
Resolved Bugs for Cisco SD-WAN Release 20.6.5.3
|
Identifier |
Headline |
|---|---|
|
The app-server java process is not initiating in 6 node 20.6 cluster |
|
|
The max netconf sessions reached in confd which causes login failure for vManage |
|
|
Cisco vEdge upgrade from 20.3.4 to 20.6.3 failed |
|
|
Cisco vEdge: TLS control connections flapping with vSmart upgraded to 20.6 |
|
|
Cisco SD-WAN Manager is not generating alarm notifications to be sent to Webhooks server. |
|
|
The DTLS session with the vBond does not come up due to OOO packets received at the vEdge |
|
|
The IGMP not receiving joins after upgrading to 20.6.4 |
|
|
Cisco vEdge: Certificate issue on Cisco vEdge devices |
Bugs for Cisco SD-WAN Release 20.6.3.3
Resolved Bugs for Cisco SD-WAN Release 20.6.3.3
|
Identifier |
Headline |
|---|---|
|
The duplicate entries of interface seen multiple VPN on performing reboot/upgrade |
|
|
[SIT] core.vtracker file found on Cisco vEdge 1000 |
|
|
The 20.9 -Edit template lock and FSM stuck state issue |
|
|
The time out : no response seen on running SNMPwalk on Cisco vEdge 5000 |
|
|
The IKEv2/vEdge long failover time |
|
|
Cisco vEdge: Data traffic loss was seen because of IPsec RX Auth Failures and Window drops |
|
|
The shaping-rate is programmed to another interface in the same VPN. |
|
|
Cisco vEdge upgrade from 20.3.4 to 20.6.3 failed |
|
|
The high CPU seen across vEdge platform |
|
|
Cisco vEdge: Certificate issue on Cisco vEdge devices |
|
|
The Cisco vEdge routing table did not remove deleted default route |
|
|
On doing OIR for 1G Fiber SFP, interface is not coming up |
|
|
Cisco vEdge 5000 "fp_dump -ec" CLI Corrupts Forwarding Cores |
|
|
The SNMPD crash seen on running Snmpwalk - 20.6.2 Cisco vEdge 5000 |
|
|
Cisco vEdge 5000 interface not coming up post shut/un-shut |
|
|
The ZIA not re-trying request to zscalar if the WAN interface gets an ip address with a little delay. |
|
|
Cisco vEdge 1000: Multiple crash seen on Cisco vEdge 1000 with DPI enabled and Scaled flows |
Bugs for Cisco SD-WAN Release 20.6.1.2
Resolved Bugs for Cisco SD-WAN Release 20.6.1.2
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge: Certificate issue on Cisco vEdge devices |
Bugs for Cisco SD-WAN Release 20.6.4.1
Resolved Bugs for Cisco SD-WAN Release 20.6.4.1
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge: Certificate issue on Cisco vEdge devices |
Bugs for Cisco SD-WAN Release 20.6.5.2
Resolved Bugs for Cisco SD-WAN Release 20.6.5.2
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge: Certificate issue on Cisco vEdge devices |
Bugs for Cisco SD-WAN Release 20.6.3.2
Resolved Bugs for Cisco SD-WAN Release 20.6.3.2
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge: Certificate issue on Cisco vEdge devices |
Bugs for Cisco SD-WAN Release 20.6.5
Resolved Bugs for Cisco SD-WAN Release 20.6.5
|
Identifier |
Headline |
|---|---|
|
Duplicate entries of interface seen multiple VPN on performing reboot/upgrade |
|
|
Cisco vEdge devices pimd crash on 20.3.5 |
|
|
Cisco vEdge devices 5K "fp_dump -ec" CLI Corrupts Forwarding Cores |
|
|
Shaping-rate is programmed to another interface in the same VPN. |
|
|
High CPU seen across Cisco vEdge devices platform |
|
|
On doing OIR for 1G Fiber SFP, interface is not coming up |
|
|
20.9 -Edit template lock and FSM stuck state issue |
|
|
APP Engine ID wrongly set to 0 - invalid (0) |
|
|
Cisco vEdge devices: Data traffic loss was seen because of IPsec RX Auth Failures and Window drops |
|
|
Cisco vEdge devices 5k interface not coming up post shut/un-shut |
|
|
ZIA not re-trying request to zscalar if the WAN interface gets an ip address with a little delay. |
|
|
Cisco vEdge devices is not connecting to second vSmart after both assigned Cisco SD-WAN Controller is down |
|
|
"Error in packet.: (genError) A general failure occured" seen when running snmpwalk on Cisco vEdge devices-cloud |
Open Bugs for Cisco SD-WAN Release 20.6.5
|
Identifier |
Headline |
|---|---|
|
LSC Interrupts not seen for interface post reboot and interfave protocol status remians down |
|
|
Cisco vEdge devices upgrade from 20.3.4 to 20.6.3 failed |
|
|
Wrong reboot reason reported when Cisco vEdge devices 2k/1k goes for unexpected reboot |
|
|
Control Connections flapping after Cisco SD-WAN Controller upgrade to 20.6.2 version when using tls. |
|
|
Cisco vEdge devices 2000 reloads without generating a core file |
|
|
Azure Viptela Cisco vEdge devices/vSmart VHD image doesn't prompt initial admin password wizard |
Bugs for Cisco SD-WAN Release 20.6.4
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 Release 20.6.4
|
Identifier |
Headline |
|---|---|
|
Enhancement request to restrict access to GDB tool for non root users. i.e. restrict to 0700 |
|
|
[SIT] core.vtracker file found on Cisco vEdge devices 1000 |
|
|
Getting "Error in packet.: (genError) A general failure occured" when running snmpwalk on Cisco vEdge devices |
|
|
IKEv2/Cisco vEdge devices long failover time |
|
|
After failover Existing primary Cisco vEdge devices stops receiving traffic and forwarding - 20.6.2 |
|
|
Cisco vEdge devices: ECMP for DP based DIA is not maintained if AAR policy applied |
|
|
Cisco vEdge devices-5000 not able to configure more than 4 SLA's |
|
|
SNMPD crash seen on running Snmpwalk - 20.6.2 Cisco vEdge devices5K |
|
|
Affinity logic not working if entire CG1 vsmarts shutdown |
|
|
Cisco vEdge devices USB directory requires root access on 20.6 |
|
|
Supress Sysmgr sig 9 from hitting wtmp history post killing critical process |
|
|
Cisco vEdge devices-100 will not boot after a power cycle if connected to a terminal server |
|
|
Cisco vEdge devices 5K: Fragmented packets don't get transmitted out of the device |
Open Bugs for Cisco SD-WAN Release 20.6.4
|
Identifier |
Headline |
|---|---|
|
Cisco vEdge devices 1000 after upgrading to 20.6.1 Error: application communication failure is seen |
|
|
20.3.x Cisco vEdge devices SNMP template push failing from 20.6 Cisco SD-WAN Manager after 1st successful push |
|
|
Cisco vEdge devices dns-redirect is not workling with Zscaler |
|
|
Cisco vEdge devices 1K silent reboot Warm Reset(CHIP RESET) |
|
|
Cisco vEdge devices5k interface not coming up post shut/un-shut |
|
|
Cisco vEdge devices cloud will rename ge interface as eth interfaces on 20.6.3 on openstack hypervisor |
|
|
Azure Viptela Cisco vEdge devices/vSmart VHD image doesn't prompt initial admin password wizard |
|
|
After the vpn list change, the DP, AAR and CLFOWD polices stopped working on the routers. |
Bugs for Cisco SD-WAN Release 20.6.3
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 Release 20.6.3
| Bug ID | Description |
| Loopback interface not reachable when the gateway set to the virtual vrrp ip | |
| Interested traffic(FTP/SIP/ICMP...) can't be forwarded properly after Cisco vEdge Device device rebooting. | |
| Cisco vEdge Device access controlled via TACACS+ prevents user from performing certain configurations | |
| Cisco vEdge Device 2k crashed due to kernel panic while generated admin-tech from Cisco SD-WAN Manager | |
| Device not rebooting after an intentional crash | |
| Cisco vEdge Device interface tracker reporting down status in vdebug constantly while on the CLI its up. | |
| Cisco vEdge Device marking the routes as invalid in OMP when the control policy is changed. | |
| Hardware Random Number generation shouldn't include TPM RNG until mutexing occurrs | |
| Endpoint Tracker stays down when ip address changed from dhcp to static | |
| Cisco vEdge Device 5k TPM failure resulting TLOC disable | |
| ZBFW zone-pair (service to service) not working as expected. | |
| Affinity on Cisco vEdge Device will fulfill EQUILIBRIUM when it loses the included vSmart group ID. |
Open Bugs for Cisco SD-WAN Release 20.6.3
| Bug ID | Description |
| Cisco vEdge Devicenot accepting 2 static routes if one of them is Null0 | |
| Affinity logic not working if entire CG1 vsmarts shutdown | |
| After failover Existing primary Cisco vEdge Device stops receiving traffic and forwarding - 20.6.2 | |
| Cisco vEdge Device: fails to reboot automatically after FP watchdog failure | |
| Azure Cisco SD-WAN Cisco vEdge Device/Cisco Catalyst SD-WAN Controller VHD image doesn't prompt initial admin password wizard | |
|
After the vpn list change, the DP, AAR and CLFOWD polices stopped working on the routers. |
Bugs for Cisco SD-WAN Release 20.6.2
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 Release 20.6.2
|
Bug ID |
Description |
|---|---|
|
SSH to Loopback not working |
|
|
QOS-3-INVALID_BQS_QUEUE_INFO: Drop policy given an invalid scheduling queue/wred 0/0 -Traceback |
|
|
Cisco Catalyst SD-WAN policy is not correctly programmed in Cisco IOS XE Catalyst SD-WAN device |
|
|
C8500 QFP FirewallNonsession drops when starting 80K flows |
|
|
IPV6 route is breaking control connection. |
|
|
AppQoE DP stats for active connections shows huge bogus value |
|
|
Cisco IOS XE Catalyst SD-WAN device: Multicast UnconfiguredIpv4Fia drop when multicast interworks with service chain/NAT DIA |
|
|
OMP continues to redistribute BGP route with down bit set (SoO) |
|
|
"show sdwan tunnel statistics bfd" and "clear sdwan tunnel statistics" issues |
|
|
Bootstrap aaa config issues due to default aaa config |
|
|
17.6.1_auto:SNMP failure on bfdSessionsListSystemIp |
|
|
FNF: Reload due to a memory allocation failure in Cisco IOS XE Catalyst SD-WAN device |
|
|
MT: Template push with thousand eye feature failed for ISR4461 after PnP workflow |
|
|
ISR1100 - Cisco IOS XE Catalyst SD-WAN device: Tx queue hang issue on RJ45 ports |
|
|
Cisco Catalyst SDWAN tunnels are not coming up in Multilink Frame relay sub-interface |
|
|
Data plane crash seen on C8200-UCPE-1N8 with upgrade of c8kv from 17.5.1 to 17.6.1 build |
|
|
Flow-Control Goes down when configurating manual speed and remove the auto negotiation |
|
|
Data-policy direction-all with empty action is causing to ignore app-route-policy |
|
|
Zscaler SIG tunnels not coming up after reboot due to HTTP/RESP/CODE 400 |
|
|
Extranet local switch crash when mdata is enabled. |
|
|
ISR4k:BFD scaling: Not able to scale more that 2048 BFD sessions |
|
|
Cisco IOS XE Catalyst SD-WAN device crash with sdwan overlay multicast: "CPU Usage due to Memory Pressure exceeds threshold" |
|
|
VEdge VRRP-VIP IP address not responding in multi VPN |
|
|
vEdge DST Root CA X3 Expiration causing umbrella integration to fail |
|
|
vEdge 20.6.1: Locally sourced DNS packets uses incorrect interface while resolving Cisco Catalyst SD-WAN Validator hostname. |
|
|
vEdge 20.6.1: Control connection fails to come up due to DTLS handshake failure. |
|
|
vEdge 20.6.1: BGP route is not considered to reach DNS server during Cisco Catalyst SD-WAN Validator hostname DNS lookup |
|
|
vEdge: Out of Order IKE Negotiation causes IKE to get stuck |
Open Bugs for Cisco SD-WAN Release 20.6.2
|
Bug ID |
Description |
|---|---|
|
Packet drops due to QoS Policy after upgrading from 20.3.3 to 20.6.0.101 |
|
|
Nutella 6G/Vedge 5K: BFD sessions take long time to come up after clearing omp sessions |
|
|
sit_regression; speedtest.py- test_speedtest_2edges: Failed to start iperf client |
|
|
Azure Viptela vEdge/vSmart VHD image doesn't prompt initial admin password wizard |
|
|
After the vpn list change, the DP, AAR and CLFOWD polices stopped working on the routers. |
Bugs for Cisco SD-WAN 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 SD-WAN Release 20.6.1
|
Bug ID |
Description |
|---|---|
|
Cisco vEdge 1000 rebooted with Software initiated - Daemon 'ftmd' failed |
|
|
Cisco vEdge 5k-LLQ policer rate on interface 10ge0/0 change after reboot on version 20.1.932 |
|
|
Cloud-init tries to configure dhcp ip on eth0 interface on ESXI (support VMware*) |
|
|
Control connection to Cisco vManage does not failover from IPv6 interface to IPv4 interface |
|
|
ASR1K - ACE entry added after object-group is missing in hardware causing packets drops |
|
|
Routes redistributed to the OSPF/BGP that shouldn't be filtered by the routing-policy are filtered |
|
|
Global Route leaking feature do not import routes if the route policy name is lengthy |
|
|
Cisco vEdge running 19.2.31 crashes with dbgd failed message while doing speed test |
|
|
shaping-rate value on main interface doesn't apply on traffic through sub interface on Cisco vEdge 5k |
|
|
Cisco vEdge show interface command shows wrong information for speed |
|
|
Additional counter to capture the mismatch between control and data plane hash table ZBF records. |
|
|
FTMD crash seen after customer tried to add a second tracker to an interface |
|
|
In 20.3.2.1 transport interface distribution, view percentage utilization shows blank |
|
|
Cisco vEdge:PIMD crash after few min of multicast traffic received |
|
|
Cloud Cisco vEdge crash on bfdmgr_update_sla_mapping |
|
|
On MTT Cisco vManage system IP persists after invalidating and deleting the edge devices. |
|
|
Cisco vEdge-2000 dropping arp replies post upgrading to 20.5.1 |
|
|
DNS resolution fails from VPN 511 - request download vpn 511 <URL> |
|
|
[20.6.1-EFT] vBond Software upgrade from SW ver 20.3 to 20.6.1 EFT image is failing |
|
|
20.6: Cisco vManage Main Dashboard , with Top Application Data => SSL proxy, data is empty |
Open Bugs for Cisco SD-WAN Release 20.6.1
|
Bug ID |
Description |
|---|---|
|
ASR1K - ACE entry added after object-group is missing in hardware causing packets drops |
|
|
On MTT Cisco vManage system IP persists after invalidating and deleting the edge devices. |
|
|
Cisco vEdge not initiating arp request after upgrading |
|
|
Nutella 6G/Cisco vEdge 5K: BFD sessions take hours to come up after clearing omp sessions |
|
|
Set local tloc does not respect DPI sticky rule |
|
|
Cisco vEdge CLoud Heat template is chaning Interface names on SW Version 20.5 |
|
|
20.6: Cisco vManage Main Dashboard , with Top Application Data => SSL proxy, data is empty |
|
|
After the vpn list change, the DP, AAR and CLFOWD polices stopped working on the routers. |
Cisco Catalyst SD-WAN Control Components Compatibility Matrix and Server Recommendations
For compatibility information and server recommendations, see Cisco Catalyst SD-WAN Control Components Compatibility Matrix and Server Recommendations.
Supported Devices
For device compatibility information, see Cisco Catalyst SD-WAN Device Compatibility.
Redesign of Cisco SD-WAN Manager GUI
From Cisco vManage Release 20.6.1, Cisco SD-WAN Manager GUI is redesigned and offers a new visual display. Besides the new sign in screen, this section presents a comparative summary of the significant changes between older Cisco vManage releases and Cisco vManage Release 20.6.1 and later.
Change in Navigation Menu
From Cisco vManage Release 20.6.1, the navigation menu at the top left of the Cisco SD-WAN Manager window is collapsed, and can be expanded to view the menu options. The previous releases of Cisco SD-WAN Manager have a static side-bar navigation menu.
Change in Position of the User Profile and Sign Out Options
From Cisco vManage Release 20.6.1, the User Profile and Sign Out options are moved to the bottom of the collapsible side-bar menu in the left pane. In the previous releases, these options are available at the top-right corner of Cisco SD-WAN Manager.
Change in Presentation of the Main Dashboard
From Cisco vManage Release 20.6.1, the position of Select Resource Group drop-down menu is shifted to the left.
Other Changes
The redesign includes:
-
New icons across Cisco SD-WAN Manager
Figure 8. Example of Icons in Cisco vManage Release 20.5.1 and Earlier 
Figure 9. Example of Icons in Cisco vManage Release 20.6.1 and Later 
-
New design for GUI elements such as tabs and buttons
Figure 10. Example of GUI Elements in Cisco vManage Release 20.5.1 and Earlier 
Figure 11. Example of GUI Elements in Cisco vManage Release 20.6.1 and Later 
-
New design for search bars across Cisco SD-WAN Manager
Figure 12. Example of Search Bar in Cisco vManage Release 20.5.1 and Earlier 
Figure 13. Example of Search Bar in Cisco vManage Release 20.6.1 and Later 
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.
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