Release Notes for the Catalyst 4500-X Series Switches, Cisco IOS XE Release 3.10.xE
Supported Hardware on the Catalyst 4500-X Series Switches
OpenFlow Version and Cisco IOS Release Support
Features Not Supported on the Cisco Catalyst 4500-X Series Switches
New Features in Cisco IOS XE Release 3.10.3E
New Features in Cisco IOS XE Release 3.10.2E
New Features in Cisco IOS XE Release 3.10.1E
New Features in Cisco IOS XE Release 3.10.0E
Cisco IOS XE to Cisco IOS Version Number Mapping
Open Caveats for Cisco IOS XE Release 3.10.3E
Resolved Caveats for Cisco IOS XE Release 3.10.3E
Open Caveats for Cisco IOS XE Release 3.10.2E
Resolved Caveats for Cisco IOS XE Release 3.10.2E
Open Caveats for Cisco IOS XE Release 3.10.1E
Resolved Caveats for Cisco IOS XE Release 3.10.1E
Open Caveats for Cisco IOS XE Release 3.10.0E
Resolved Caveats in Cisco IOS XE Release 3.10.0E
Obtaining Documentation and Submitting a Service Request
First Published: August 8, 2017
This release note describes the features, modifications, and caveats for the Cisco IOS XE Release 3.10.xE software on the Catalyst 4500-X Series Switches.
Cisco IOS XE Release 3.10.xE is a feature rich new software feature release for IOS and IOS-XE based Catalyst Access Switching products.
Note Although Cisco Catalyst 4500E Series Switches and Cisco Catalyst 4500-X Series Switches have separate release notes, each leverages the same Software Configuration Guide and Command Reference Guide.
Cisco Catalyst 4500-X Series Switches support these license levels or feature sets.
The following permanent right-to-use licenses or base licenses are available:
Starting with Cisco IOS XE Release 3.10.0E, the following add-on license options are available:
To find information about platform support and to know which license levels a feature is available with, use Cisco Feature Navigator. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Customers with Catalyst 4500-X Series Switches who need the latest hardware and software features should migrate to Cisco IOS XE Release 3.10.xE.
Cisco IOS XE Release 3.8.xE 3.6.xE, and 3.4.xSG are extended maintenance (EM) trains supporting 4500-X.
Cisco IOS XE Release 3.10.xE, 3.9.xE, 3.7.xE, 3.5.xE, and 3.3.xSG and standard maintenance (SM) trains supporting 4500-X.
Support for Cisco IOS XE Release 3.9.xE follows the standard Cisco Systems® support policy, available at
http://www.cisco.com/en/US/products/products_end-of-life_policy.html
This section describes the system requirements:
The following table lists where you can find information about supported pluggable transceiver modules and the minimum Cisco IOS Software release required:
Table 2 is a detailed list of features supported on Catalyst 4500-X Series switches running Cisco IOS XE Release 3.10.xE categorized by image type. Please visit Feature Navigator for package details:
http://tools.cisco.com/ITDIT/CFN/
Application Visibility and Control with Domain Name System-Authoritative Source (AVC with DNS-AS) |
||
BGP Increased Support of Numbered as-path Access Lists to 500 |
||
Bidirectional Forwarding Detection (BFD) for Intermediate System to Intermediate System (IS-IS) |
||
CFM/IEEE 802.1ag — D8.1 standard Compliant CFM, Y.1731 multicast LBM / AIS / RDI / LCK, IP SLA for Ethernet |
||
Cisco-Port-QoS-MIB — Support for cportQosQueueEnqueuePkts and cportQosQueueDropPkts |
||
Class Based Ethernet CoS Matching & Marking (802.1p & ISL CoS) |
||
Easy VSS1 |
||
IEEE 802.1s Multiple Spanning Tree (MST) Standard Compliance |
||
IEEE 802.1t2 |
||
IEEE 802.3ad Link Aggregation (LACP) Port-Channel Standalone Disable |
||
IGMP Version 3 — Explicit Tracking of Hosts, Groups, and Channels |
||
IP Multicast Load Splitting - Equal Cost Multipath (ECMP) using S, G and Next-hop |
||
IPv6 First Hop Security (FHS): IPv6 Snooping (Data Gleaning, per-limit Address Limit) IPv6 Neighbor Discovery Inspection |
||
IPv6 First Hop Security (FHS) Phase 2: Lightweight DHCPv6 Relay Agent (LDRA) Neighbor Discovery (ND) Multicast Suppress Source and Prefix Guard3 |
||
Yes 4 |
||
IPv6 Multicast — Multicast Listener Discovery (MLD) Protocol, Versions 1 and 2 |
||
IPv6 Multicast — RPF Flooding of Bootstrap Router (BSR) Packets |
||
Yes 4 |
||
IPv6 Router Advertisement Options for Domain Name System (DNS) Configuration |
||
Yes4 |
||
IPv6 Services — Cisco Discovery Protocol (CDP) - IPv6 Address Family Support for Neighbor Information |
||
IPv6 Switching — CEFv6 Switched Automatic IPv4-compatible Tunnels (in software) |
||
IPv6 Switching — CEFv6 Switched Configured IPv6 over IPv4 Tunnels (in software) |
||
IPv6 Switching — CEFv6 Switched ISATAP Tunnels (in software) |
||
IPv6 Tunneling — Automatic IPv4-compatible Tunnels (in software) |
||
IPv6 Tunneling — Manually Configured IPv6 over IPv4 Tunnels (in software) |
||
Medianet 2.0 — Integrated Video Traffic Simulator (hardware-assisted IP SLA); IPSLA generator and responder |
||
Medianet 2.0 — Media Monitoring (Performance Monitoring and Mediatrace) |
||
NEAT Enhancement: Re-Enabling BPDU Guard Based on User Configuration |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
OSPF for Routed Access5 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
Yes 4 |
||
RADIUS Attribute 44 (Accounting Session ID) in Access Requests |
||
Smart Install Director—Configuration-only Deployment and Smooth Upgrade |
||
Source Specific Multicast (SSM) - IGMPv3,IGMP v3lite, and URD |
||
TrustSec: IEEE 802.1ae MACSec encryption on user facing ports |
||
TrustSec: IEEE 802.1ae MACSec encryption between switch-to-switch links using Cisco SAP (Security Association Protocol) |
||
UDP Forwarding Support for IP Redundancy Virtual Router Group |
||
Virtual Switching System (VSS) — Layer 2 Protocol Tunneling, VLAN Translation, and Q-in-Q |
||
Virtual Switching System (VSS) Phase 26 |
||
Virtual Switching System (VSS) — REP, Flexlinks, UDLD, and Fast UDLD |
||
The OVA package is available for download in the same location as your system image (.bin) file, on cisco.com
Note The OVA package is compatible only with its corresponding system image file name - as listed in the table below. Do not use an older version of the OVA package with a newer system image file, or a newer OVA package with an older system image file.
For information on MIB support, please refer to this URL:
ftp://ftp.cisco.com/pub/mibs/supportlists/cat4000/cat4000-supportlist.html
The following features are not supported on a Catalyst 4500-X Series switches:
With some exceptions, the VSS maintains “feature parity” with the standalone Catalyst 4500 or 4500-X series switches. Major exceptions include:
These sections describe the new and changed information for Catalyst 4500-X Series Switches running Cisco IOS XE software:
Introduces support for a new add-on licensing option. Features that are available with add-on license levels provide Cisco innovations on the switch, as well as on the Cisco Digital Network Architecture Center (Cisco DNA Center). You can activate or deactive add-on licenses by using the license right-to-use [ activate | deactivate ] [ addon { dna-essentials | dna-advantage }] { subscription | evaluation }[ acceptEULA ] command options. There are no changes in the way you activate or deactivate the existing (base) license options (Enterprise Services and IP Base), but there are restrictions to the permitted combinations of base and add-on licenses you can order. See the software configuration guide for more information. |
|
IPv6 Router Advertisement Options for Domain Name System (DNS) Configuration |
The Domain Name System (DNS) protocol controls the DNS, a distributed database with which you can map hostnames to IP addresses. The DNS record types support IPv6 addresses. This release introduces support for RFC 6106, which specifies IPv6 Router Advertisement (RA) options. These options are supported:
|
As Table 5 shows, each version of Cisco IOS XE has an associated Cisco IOS version:
If you are upgrading to Cisco IOS XE Release 3.9.xE and plan to use VSS, you must upgrade your ROMMON to IOS Version 15.0(1r)SG11.
Workaround : You have to enter the shutdown and then the no shutdown interface configuration command for traffic flow to resume. (CSCus14532)
The problem is seen on a Catalyst 4500 series switch running Cisco IOS-XE release 3.7.0E, when you configure QoS using Auto Qos and you try to delete an Auto QoS profile related policy map.
Workaround : To recover the deleted policy-map, remove all the policies related to that profile, remove Auto QoS configuration from the WLAN, and then reconfigure Auto QoS.
TFTP numbers its datagrams with a 16 bit field, resulting in a maximum of 65,536 datagrams. Because each TFTP datagram is 512 bytes long, the maximum transferable file is 65536 x 512 = 32 MB. If both the TFTP client (ROMMON) and the TFTP server support block number wraparound, no size limitation exists.
Cisco has modified the TFTP client to support block number wraparound. So, if you encounter a transfer failure, use a TFTP server that supports TFTP block number wraparound. Because most implementations of TFTP support block number wraparound, updating the TFTP daemon should fix the issue.
The outputs of certain commands, such as show ip route and show access-lists, contain non-deterministic text. While the output is easily understood, the output text does not contain strings that are consistently output. A general purpose specification file entry is unable to parse all possible output.
While a general purpose specification file entry may not be possible, a specification file entry might be created that returns the desired text by searching for text that is guaranteed to be in the output. If a string is guaranteed to be in the output, it can be used for parsing.
For example, the output of the show ip access-lists SecWiz_Gi3_17_out_ip command is this:
The first line is easily parsed because access list is guaranteed to be in the output:
The remaining lines all contain the term host. As a result, the specification file may report the desired values by specifying that string. For example, this line
will produce the following for the first and second rules
and the following for the third statement
Request the output of the show running-config command using NETCONF and parse that output for the desired strings. This is useful when the desired lines contain nothing in common. For example, the rules in this access list do not contain a common string and the order (three permits, then a deny, then another permit), prevent the spec file entry from using permit as a search string, as in the following example:
The XML output of show running-config command includes the following, which can then be parsed programmatically, as desired:
Workaround: Define a policy-map with a different name and then reattach. CSCti26172
– Decrease the number of monitors.
– Attach the same monitor to multiple targets. CSCti43798
Workaround: Use the dir device command (for example, dir bootflash:) to obtain the correct file count. CSCti74130
– At least 10K groups and roughly 20K mroutes exist.
– IGMP joins with source traffic transit to all the multicast groups.
This is caused by the large number of updates generating SPI messages that must be processed by the CPU to ensure that the platform is updated with the changes in all the entries.
You cannot clear a large number of mroutes at one time when traffic is still running.
Workaround: Do not clear all mroutes at once.
Workaround: Use the show version command. CSCtr30294
Workaround: Select an alternate destination or source port. CSCty05405
Workaround: Configure both dead-criteria and deadtime.
– Links flap for various Layer 3 protocols.
– A traffic loss of several seconds is observed during the upgrade process.
Workaround: Do not use the quick option with the issu changeversion command. CSCto51562
You will not experience this behavior with IPv4 access lists.
Workaround: During IPv6 access-list configuration, configure at least one IPv6 ACE before the "hardware statistics" statement. CSCuc53234
This applies to QoS policing only. QoS marking, shaping and sharing behave as expected.
Workaround: Apply FHS policies on a non EtherChannel port rather than a VLAN. CSCua53148
Because the Catalyst 4500-X is a “fixed” configuration device, in a VSS, you would expect the two systems to be labeled 'Module 1' and 'Module 2.’ However, because of software implementation similarities with the modular Catalyst 4500E series switches, the Standby switch is labeled 'Module 11.’
Workaround: None. QoS groups are not supported in VSS. CSCuc84739
These messages are cosmetic only, and no ssh services are available unless configured within IOS.
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Note For the latest information on PSIRTS, refer to the Security Advisories on CCO at the following URL:
http://www.cisco.com/en/US/products/products_security_advisories_listing.html
The Bug Search Tool (BST) allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The BST is designed to improve the effectiveness in network risk management and device troubleshooting. The tool has a provision to filter bugs based on credentials to provide external and internal bug views for the search input.
Refer to the Cisco Catalyst 4500-X Series Switches Documentation Home for information:
https://www.cisco.com/c/en/us/support/switches/catalyst-4500-x-series-switches/tsd-products-support-series-home.html
Installation guides and notes including specifications and relevant safety information are available at the following URLs:
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/hardware/regulatory/compliance/78_13233.html
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_installation_guides_list.html
http://www.cisco.com/en/US/products/ps12332/prod_installation_guides_list.html
Software release notes, configuration guides, command references, and system message guides are available at the following URLs:
http://www.cisco.com/en/US/products/ps12332/prod_release_notes_list.html
– Software Configuration Guides:
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_installation_and_configuration_guides_list.html
– Command Reference Guides: http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_command_reference_list.html
Platform- independent Cisco IOS documentation is available at the following URLs:
http://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-xe-3e/products-installation-and-configuration-guides-list.html
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mcl/allreleasemcl/all-book.html
The following notices pertain to this software license.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/)”.
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/)”.
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS”' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
“This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)”.
The word ‘cryptographic’ can be left out if the routines from the library being used are not cryptography-related.
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgment: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.