Release Notes for Cisco IOS XE SD-WAN Devices, Cisco IOS XE Release Bengaluru 17.4.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 IOS XE Release Bengaluru 17.4.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 IOS XE SD-WAN devices.
For release information about Cisco vEdge Devices, refer to Release Notes for Cisco vEdge Devices, Cisco SD-WAN Release 20.4.x.
What's New for Cisco IOS XE Release Bengaluru 17.4.x
This section applies to Cisco IOS XE SD-WAN 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 |
|---|---|
|
Cisco SD-WAN Getting Started |
|
| Support for Deploying Cisco Catalyst 8000V Instances for Supported Cloud Services Provider Platforms |
Starting from this release, Cisco Catalyst 8000V instances can be deployed on Cloud Services Provider portals such as Google Cloud Platform, Microsoft Azure and Amazon Web Services. |
|
This feature enables you to add and manage root certificate authority (CA) certificates. |
|
|
This feature enables you to configure subject altenative name (SAN) DNS Names or uniform resource identifiers (URIs). It enables multiple host names and URIs to use the same SSL certificate. |
|
|
Upgrade the Software of Cisco ISR1100 Series Integrated Services Routers to Cisco IOS XE |
This release introduces Cisco IOS XE SD-WAN support for Cisco ISR1100 Series Integrated Services Routers (Cisco ISR1100-4G, Cisco ISR1100-6G, and Cisco ISR1100-4GLTE). These devices can use either Cisco vEdge software or Cisco IOS XE SD-WAN. You can upgrade these routers from Cisco vEdge software to Cisco IOS XE SD-WAN, or vice-versa. |
|
One Touch Provisioning: Onboard Cisco IOS XE SD-WAN Devices Using Generic Bootstrap Configuration |
You can generate a generic bootstrap configuration on Cisco vManage and use this configuration to onboard multiple Cisco IOS XE SD-WAN devices. When you boot a device with the generic bootstrap configuration, the device is listed on Cisco vManage as an unclaimed WAN edge device. To complete the onboarding, claim the device on Cisco vManage and attach a device template that configures the system IP address and site ID. |
|
Systems and Interfaces |
|
|
This feature allows you to use type 6 passwords that use secure reversible encryption. This encryption provides enhanced security by using more secure algorithms to encrypt your passwords. These passwords are supported for the templates detailed in . |
|
|
This feature provides templates for configuring a supported cellular gateway as an IP pass-through device. This release supports the Cisco Cellular Gateway CG418-E. |
|
|
With Cisco SD-WAN multitenancy, a service provider can manage multiple customers, called tenants, from Cisco vManage. In a multitenant Cisco SD-WAN deployment, tenants share Cisco vManage instances, Cisco vBond Orchestrators and Cisco vSmart Controllers. Tenant data is logically isolated on these shared resources. |
|
|
Starting Cisco IOS XE Release 17.4.1a, you can use additional commands in CLI Add-on feature templates. |
|
|
Jumbo Frames Support |
Jumbo Frames are supported for 1 GE interfaces on Cisco IOS XE SD-WAN devices. Starting Cisco IOS XE Release 17.4.1a, the MTU can range from 576 through 9216 bytes on these 1 GE interfaces. |
|
Routing |
|
|
Ability to Match and Set Communities during BGP to OMP Redistribution |
This feature enhances the implementation of match and set clauses for redistribution from BGP to OMP and vice versa on Cisco IOS XE SD-WAN devices. You can redistribute the routes from a BGP into an OMP routing process, using the
|
|
Policies |
|
|
This feature provides support for a new match condition that you can use to specify a list of ICMP messages for centralized data policies, localized data policies, and Application-Aware Routing policies. For information on matching ICMP messages in a centralized data policy, see Match Parameters - VPN List. For information on matching ICMP messages in a localized data policy, see Match Parameters. For information on matching ICMP messages in an Application-Aware Routing policy, see Structural Components of Policy Configuration for Application-Aware Routing. |
|
|
With this feature, while creating a data policy, you can define an application list along with other match criteria and redirect the application traffic to a Secure Internet Gateway (SIG). |
|
|
This release extends Enhanced Policy Based Routing (ePBR) to Cisco SD-WAN. ePBR is a protocol-independent traffic-steering mechanism that routes traffic based on flexible policies for traffic flows. You can create ePBR policies using CLI add-on templates in Cisco vManage. |
|
|
This feature enahances the capabilities of directing traffic to next-hop addresses based on the SLA definitions. These SLA definitions along with the policy to match and classify traffic types can be used to direct traffic over specific Cisco SD-WAN tunnels. The SLA definition comprises of values of loss, latency and jitter, which are measured using the BFD channel that exists between two TLOCs. |
|
|
This feature enables export of packet to external collector over IPv6 transport on Cisco IOS XE SD-WAN devices and provides the visibility of IPv6 network traffic. If you want to monitor IPv4 and IPv6 traffic together, this feature enables you to modify the cache size on the data plane. Cisco Flexible NetFlow (FNF) is a technology that provides customized visibility into network traffic. In Cisco SD-WAN, FNF enables exporting data to Cisco vManage which makes it easy for the customers to monitor and improve their network. |
|
|
Security |
|
|
This feature allows you to create sets of rules called rule sets. Rule sets are a method to create multiple rules that have the same intent. You can also re-use rule sets between security policies. |
|
|
This feature lets you configure port-scanning detection and apply a severity level (low, medium, or high) for identifying and classifying potential attacks using a CLI template. |
|
|
This feature allows you to use the SIG template to steer application traffic to Cisco Umbrella or a Third party SIG Provider. The application traffic is steered to a SIG based on a defined data policy and other match criteria. This feature also allows you to configure weights for multiple GRE/IPSEC tunnels for distribution of traffic over multiple tunnels. Equal-cost multi-path (ECMP) routing and load balancing is supported on multiple GRE/IPSEC tunnels. |
|
|
TCP Optimization |
|
|
This feature allows you to configure multiple AppQoE service nodes that are external to the intercepting edge routers or AppQoE service controllers. It extends AppQoE support to edge routers in which AppQoE can't run as an integrated service node. This feature also allows AppQoE to scale, where integrated AppQoE has limitations on the throughput and number of connections. The ability to configure multiple AppQoE service nodes help meet the scale and throughput requirements of large enterprise sites, such as data centers. |
|
|
Cloud OnRamp |
|
|
Azure Government Cloud Support for Cisco IOS XE SD-WAN Devices |
This feature allows you to configure the Cisco Catalyst 8000V devices on Microsoft Azure Government Cloud. With these cloud devices now supported on Microsoft Azure Government Cloud, Government Cloud customers can use the same advanced routing and security benefits, which are already available on Azure public cloud. |
|
AWS Government Cloud Support for Cisco IOS XE SD-WAN Devices |
Starting from this release, Cisco Catalyst 8000V devices are supported on AWS Government Cloud. |
|
Application Feedback Metrics for Office 365 Best Path Selection on Cisco IOS XE SD-WAN Devices |
This feature adds new metrics as inputs to the best-path selection algorithm for Office 365 traffic. The new inputs include best-path metrics from Microsoft Cloud Services. The feature also provides a new page for viewing detailed logs of the input data used by the best path algorithm. |
|
This feature enhances Cloud OnRamp integration with Microsoft Azure by allowing Cisco Catalyst 8000V Edge Software (Cisco Catalyst 8000V) to be deployed inside the Azure Virtual WAN Hub instead of deploying it in transit VNets. It also automates the Cisco SD-WAN fabric connection to Azure Virtual WAN Hub through Cisco Catalyst 8000V. The connectivity between inter-region Azure Virtual WAN Hubs is also supported. In addition, you can convert the Azure virtual WAN hubs created using Cisco vManage into secured hubs by deploying Azure firewall inside them. However, secured virtual hubs can only be configured using the Microsoft Azure portal. |
|
|
Integration of Cisco SD-WAN and Azure Virtual WAN Hub Using Azure Portal |
As part of the integration of Cisco SD-WAN with Azure Virtual WAN, you can also use the Azure portal to upload bootstrap configuration files for Cisco Catalyst 8000V instances. These instances can then be used to create a virtual WAN hub using the Azure portal. |
|
Support for Cisco Cloud Services Platform, CSP-5456 (Cloud onRamp for Colocation) |
Starting from this release, Cisco CSP-5456 is supported on the Cloud onRamp for Colocation solution. The CSP-5456 offers a higher capacity of 56 cores, which maximizes the placement of VNFs in service chains. |
|
Support for Cisco Catalyst 8000V Devices (Cloud onRamp for Colocation) |
Starting from this release, Cisco Catalyst 8000V devices are now supported as a validated VNF in the Cloud onRamp for Colocation solution. |
|
Onboarding CSP Device with Day-0 Configuration Using USB Drive (Cloud onRamp for Colocation) |
This feature enables you to onboard CSP devices by loading the Day-0 configuration file to a USB drive. Use this onboarding option when you can't access the Internet to reach the Plug-and-Play Connect server. |
|
Monitor and Maintain |
|
|
Ethernet Connectivity Fault Management Support on Cisco IOS XE SD-WAN Devices |
Starting from this release Cisco SD-WAN supports the Ethernet Connectivity Fault Management functionality on Cisco IOS XE SD-WAN devices. This feature helps to monitor the Carrier Ethernet Network links. |
|
Binary trace enhances the troubleshooting of Cisco SD-WAN daemons. Binary trace logs messages from the daemons in a binary format. Messages are logged faster in the binary format, improving the logging performance, and use lesser storage space than in the ASCII format. The binary trace CLI allows you to set the debug levels for additional process modules compared to the debug command. From Cisco IOS XE Release 17.4.1a, binary trace is supported for the following Cisco SD-WAN daemons:
|
|
|
Cisco SD-WAN Command Reference Guide |
|
|
This feature adds information about crypto utilization to the show platform resources command on the supported routers. |
|
|
High Availability Configuration Guide |
|
|
This feature provides validated support for disaster recovery for a 6 node Cisco vManage cluster. |
|
New and Enhanced Hardware Features
New Features
-
Support for UCS-E module—This feature adds a UCS-E template in Cisco vManage for configuring Cisco Unified Computing System (UCS) E-Series servers. For related information, see Getting Started Guide for Cisco UCS E-Series Servers and the Cisco UCS E-Series Network Compute Engine and Configuring Devices using vManage.
Note
Currently, backplane interfaces are not supported for UCS-E module. Only external connectivity is supported.
-
Support for Cisco IR1101 Integrated Services Router Rugged—Cisco SD-WAN capability can now be enabled onCisco IR1101 Integrated Services Router Rugged. The following notes apply to this support:
-
Controller devices (Cisco vBond orchestrators, Cisco vManage NMSs, and Cisco vSmart controllers) must run Cisco SD-WAN Release 19.2 or later.
-
The default topology is full mesh, but the hub and spoke topology is often used for IoT applications.
-
Cisco SD-WAN support on the Cisco IR1101 Integrated Services Router Rugged requires Cisco IOS-XE Release 16.12.
-
The Cisco IR1101 Integrated Services Router Rugged has four fixed switch-ports. Make sure to select the correct template.
-
The CLI template is not currently supported.
-
Starting from Cisco IOS-XE Release 16.12.1, Cisco IR1101 Integrated Services Router Rugged has dual LTE support with LTE extension module.
-
We recommend using up to 50 BFD sessions for scaling.
-
Important Notes, Known Behavior, and Workaround
-
From Cisco SD-WAN Release 20.4.1.1, Microsoft Azure environment is supported for deploying Cisco SD-WAN controllers (Cisco vBond orchestrator, Cisco vSmart controller, and Cisco vManage). The support is limited to Cisco SD-WAN cloud-based deployments only.
-
Cisco IOS XE SD-WAN devices with the SFP-10G-SR module do not support online insertion and removal (OIR) of this module.
- 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 vManage. 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.
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 |
|||||
|
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 |
||||
|
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
|
||||
|
20.3.x |
Not Supported |
Not Supported |
Direct Upgrade |
Direct Upgrade |
||||
|
20.4.x |
Not Supported |
Not Supported |
Not Supported |
Direct 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 IOS XE Release 17.4.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 IOS XE Release 17.4.2
|
Bug ID |
Description |
|---|---|
|
Cisco IOS XE SD-WAN device crashes while running web traffic testing with security features enabled |
|
|
CSR1000v crashing frequently with Critical software exception error. |
|
|
On-demand tunnel is not setup with AAR SLA class and CXP feature enabled |
|
|
C8500-12X4QC does not send logs to Cisco vManage when harddisk is not installed |
|
|
SDWAN BFD is not re-establishing after network flap |
|
|
App-aware policy need to be honored when queuing is not set by localized policy |
|
|
Crash in DSP causing an mcpcc-lc-ms core file |
|
|
Duplicate Bytes & Packet when Q in Q is configured |
|
|
Router reload due sdwan nbar init process |
|
|
Cisco IOS XE SD-WAN device object-group is not in sync between IOS and Confd. |
|
|
VPN label is changing upon vEdge reboot |
|
|
vSmarts crashing due to OOM after upgrade to 20.4.1.1 |
|
|
Cisco vManage available entropy exhaustion on some setup |
Open Bugs for Cisco SD-WAN Release 17.4.2
|
Bug ID |
Description |
|---|---|
|
cpp-mcplo-ucode crash due to stuck thread with extranet route leaking between vpns |
|
|
DDNS feature triggers crash on 16.X/17.X releases due to memory corruption |
Bugs for Cisco SD-WAN Controller Release 20.4.1.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 Controller Release 20.4.1.2
|
Bug ID |
Description |
|---|---|
|
Frequent crashes/kernel panics on vEdge 100 models |
|
|
Policy Template push failure from Cisco vManage 20.4.1.1 to 17.2 |
|
|
Order of DNS entries fails with <bad-element>dns-server-list</bad-element> |
|
|
Update button stops working after adding DHCP option |
|
|
Directory ownership changed after reload/upgrade |
|
|
Container logs seen growing unbounded without log rotation |
|
|
Devices goes "Out-of-sync" and can't re-push template with security policy and fail with "bad-cli" |
Bugs for Cisco IOS XE Release 17.4.1b
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 IOS XE Release 17.4.1b
|
Bug ID |
Description |
|---|---|
|
vEdge DPI for MS Teams does not work well |
|
|
vmanage DHCP option 150 not allow multiple ip address |
|
|
Fragmented packets may be dropped inbound on tunnel of cEdge with service-side NAT configuration |
|
|
PPPoE config on Gig interface failed , vManage not handling ip mtu and mtu correctly |
|
|
vManage 6 Node CLuster on Azure takes 2 mins to login to vManage UI. |
|
|
Slowness in viewing ty policy , list & editing security policy. |
|
|
Mapping for AWS TGW does not start when Azure vWAN mapping exists |
|
|
after upgrading to from 17.3.2 to 17.4.1, the device loses control connections |
|
|
20.4 policy name restrictions may break existing templates on upgrade |
|
|
Increase process wait timeout for configdb upgrade |
|
|
cEdge stuck in INIT state with vSmart |
|
|
vManage misconfigures cEdge ebgp-multihop which causes BGP BFD down |
|
|
20.4 template push on ISR4451 failing with VRRP config |
|
|
vManage template/policy push performance optimizations needed |
|
|
In a cluster, an App server starting dependency should check a cluster, not just local service |
|
|
BFD for BGP doesn't work on cEdge ASR1k |
|
|
statsdb container crashes on 20.4 128GB azure vmanage |
|
|
Template deattach got stuck after upgrade to 20.4 IR |
|
|
Speed test initiated from ISR1k failed |
Open Bugs for Cisco SD-WAN Release 17.4.1b
|
Bug ID |
Description |
|---|---|
|
vBond/vSmart Upgrade Failed and Rollback due to Upgrade confirm not received |
|
|
vManage admin tech failing intermittently |
|
| CSCvx38058 |
vBond kernel panic seen on reload |
Bugs for Cisco IOS XE Release 17.4.1a
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 IOS XE Release 17.4.1a
|
Bug ID |
Description |
|---|---|
|
Drop cEdge requirement for dot1Q subinterface MTU to be 4 Bytes less than main interface |
|
|
New Password is asked even when the Template used a non default admin Password |
|
|
explicit acl needed for cellular intf for control connection bringup |
|
|
[17.2.1]:policy service path and tunnel path commands stop working after reload |
|
|
ASR1k - all Platform : Observing IpFragErr for EMIX traffic with basic IPSEC config |
|
|
ASR IOS-XE SDWAN router bfd sessions not coming up if BGP routing is not providing a local next hop. |
|
|
ASR1k crash when doing a FIB lookup |
|
|
Template push is failing as vManage is trying to disable link recovery for cellular controller. |
|
|
Default route missing for second TLOC during script run, and control connection get stuck |
|
|
cpp_cp_svr_ledp crash seen during SIT Regression |
|
|
[SIT] Ramanos lost control and crashed after attaching device template |
|
|
Day 0 Config Bringup after Power OFF/ON | C1121X-8PLTEP |
|
|
sdwan multicast cEdge rpf failure even with unicast route present in rib and omp |
|
|
CLI template push for banner login <> configuration fails on cedge |
|
|
Backward compatibility issue for model between vManage version 20.3 and device version 17.2 |
|
|
[DyT]: TTM not updating link routes and omp routes are not getting updated |
|
|
IOS-XE SD_WAN router crashed after upgrade to 17.3.1a |
|
|
cEdge data-policy breaks SRST media stream with default-action accept or accept in sequence |
|
|
PMTU Discovery may negotiate an incorrect MTU on XE SDWAN routers |
|
|
BFD sessions flap after multiple control connection flaps to the vSmart. - Polaris side commit |
|
|
XE SDWAN router crash due to system memory exhaustion caused by FTM memory growth |
|
|
SDWAN 17.2.1/17.4.1 - cEdge router may restart after pushing multiple traffic data policies together |
|
|
TSN: AAA Server Down issue using type 6 password |
Open Bugs for Cisco IOS XE Release 17.4.1a
|
Bug ID |
Description |
|---|---|
|
SDWAN17.3- "NAT" Ping fails for packets originated from router - Reason packets drop "Ipv4NoRoute" |
|
|
After enable FEC and FNF with 100K flow per seconds for 40mins, C8500 crashes |
|
|
IPSEC tunnels to AWS TGW failing when VPN tunnel doesn't allow all traffic |
|
|
O365 CoR-SaaS shows random losses |
|
|
Connected route is not imported into OMP database unless flap interface with C8KV platform |
|
|
4451 : FTMD crash @ bfdmgr_session_get_from_record_index with traffic soak |
|
|
[cEdge/CSR1kv] IPv6 Underlay, IPv6 fragmented but packet size is smaller than MTU |
|
|
Enable AES encryption on cEdge and encrypt umbrella and zscaler secret/password |
|
|
tunnel interface remains up even when the physical interface not have IP address |
|
|
vEdge/cEdge - rekey timer expires, but tunnels stay up |
|
|
Not all OMP routes getting installed |
|
|
Fragmented packets may be dropped inbound on tunnel of cEdge with service-side NAT configuration |
|
|
Bfd session stuck in invalid state |
|
|
Intra-zone ZBFW policy does not apply on hardware level |
|
|
After reload cEdge cellular interfaces in shutdown state are brought up |
|
|
crash. seen during sh plat sof sdwan fo next-hop overlay id 0xf8000090 |
|
|
DPI flow telemetry generated by IOS-XE, for some flows tunnel identifiers are missing |
|
|
Traceroute from Service VPN to remote Service VPN not showing the correct Hops |
|
|
ASR-1K router is not programming correct next-hop for the destination prefix. |
|
|
cEdge: IP MTU and MTU misconfiguration |
|
|
Promethium: Box crashed at cpp_bfd_sdwan_stats_modify during longevity testing |
|
|
cEdge directly-connected routes missing from routing table |
|
|
nat pool config using sub-interfaces does not work after reload |
|
|
Broadcast packets dropped even with "ip network-broadcast" and "ip directed-broadcast" configured |
Controller Compatibility Matrix and Server Recommendations
For compatibility information and server recommendations, see Cisco SD-WAN Controller Compatibility Matrix and Server Recommendations.
Supported Devices
For device compatibility information, see Cisco SD-WAN Device Compatibility.
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