Release Notes for the Catalyst 4500E Series Switch, Cisco IOS XE Release 3.9.xE
Supported Hardware on the Catalyst 4500-E Series Switch
Supported E-Series Hardware on Cisco IOS XE Release 3.9.xE
Wired Web UI (Device Manager) System Requirements
OpenFlow Version and Cisco IOS Release Support
Features Not Supported on the Cisco Catalyst 4500-E Series Switch
New Features in Cisco IOS XE Release 3.9.2E
New Features in Cisco IOS XE Release 3.9.1E
New Features in Cisco IOS XE Release 3.9.0E
Wireless Web UI Software Requirements
Access Points and Mobility Services Engine
Interoperability with Other Client Devices
Identifying Hardware Revisions on the Switch Chassis
Upgrading ROMMON Image for Supervisor Engine 8-E
Identifying an +E Chassis and ROMMON
Open Caveats for Cisco IOS XE Release 3.9.xE
Resolved Caveats in Cisco IOS XE Release 3.9.2E
Resolved Caveats in Cisco IOS XE Release 3.9.1E
First Published: July 28, 2016
This release note describes the features, modifications, and caveats for the Cisco IOS XE Release 3.9.xE, on the Catalyst 4500E Series Switches with Supervisor Engine 7-E, 7L-E, 8-E, and 8L-E.
Note Beginning with Cisco IOS XE Release 3.8.1E, Supervisor Engine 8L-E is available with ROMMON 15.1(1r)SG6.
Note For the Supervisor Engine 8-E to support Cisco IOS XE Release 3.9.xE, the ROMMON version must be upgraded to 15.1(1r)SG5. (Refer to Upgrading the System Software).
Cisco IOS XE Release 3.9.xE is a feature rich new software feature release for IOS and IOS-XE based Catalyst Access Switching products.
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
For more information on the Catalyst 4500E series switches, visit the following URL:
http://www.cisco.com//en/US/products/hw/switches/ps4324/index.html
Note Although this release note and those for the Catalyst 4500-X Series Switches differ, each leverages the same Software Configuration Guide and Command Reference Guide.
The Enterprise Services image supports all Cisco Catalyst 4500E Series software features based on Cisco IOS Software, including enhanced routing.
The IP Base image supports Open Shortest Path First (OSPF) for Routed Access, Enhanced Interior Gateway Routing Protocol (EIGRP) "limited" Stub Rout ing, Nonstop Forwarding/Stateful Switchover (NSF/SSO), and RIPv1/v2. The IP Base image does not support enhanced routing features such as BGP, Intermediate System-to-Intermediate System (IS-IS), Full OSPF, Full Enhanced Interior Gateway Routing Protocol (EIGRP) & Virtual Routing Forwarding (VRF-lite).
The LAN Base image complements the existing IP Base and Enterprise Services images. It is focused on customer access and Layer 2 requirements and therefore many of the IP Base features are not required.
Starting with Cisco IOS Release XE 3.5.0E, OSPF Routed Access in IP Base support rose to 1000 routes.
Customers with Catalyst 4500 Series Switches who need the latest hardware and software features should migrate to Cisco IOS XE Release 3.9.xE.
IOS XE 3.2.xSG is an active maintenance train that supports Sup7E only.
IOS XE 3.4.xSG is a maintenance train supporting Sup7E and Sup7L-E.
IOS XE 3.6.xSG is a maintenance train supporting Sup7E, Sup7L-E and Sup8-E.
IOS XE 3.9.xE, 3.7.xE, 3.5.xE, and 3.3.0SG are standard releases (SM).
IOS XE 3.8.xE is a maintenance train supporting Sup7E, Sup7L-E and Sup8-E.
IOS XE 3.8.1E and later supports Sup8L-E.
IOS XE 3.8.xE, 3.6.xE, 3.4.xSG, and 3.2.xSG are extended maintenance (EM) releases.
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:
Note For information about wireless web UI requirements, see “Wireless Web UI Software Requirements” section
Table 1 Supported Hardware on Cisco Catalyst 4500-E, 3
Table 2 Supported Pluggable Transceiver Modules, 6
Table 3 Power over Ethernet on Cisco Catalyst 4500-E, 7
Catalyst 4500-E series switch Supervisor Engine 7-E Note This engine is supported on E-series, R-E, and R+E chassis. |
|
Catalyst 4500-E series switch Supervisor Engine 7L-E Note This engine is supported on E-series, R-E, and R+E chassis. |
|
Catalyst 4500-E series switch Supervisor Engine 8-E This engine is supported on E-series and R+E and R-E1 chassis. |
|
Catalyst 4500-E series switch Supervisor Engine 8L-E This engine is supported on E-series and R+E and R-E 1 chassis. |
|
Catalyst 4500E 48-Port UPOE with 12 Multigigabit ports and 36 10/100/1000 ports. This module supports the Cisco Multigigabit technology for 802.11ac Wave2 and 10GBASE-T speeds. |
|
18-port 1000BASE-X (GBIC) Gigabit Ethernet switching module. |
|
12-port 1000BASE-T Gigabit Ethernet and 2-GBIC ports switching module. |
|
24-port 10/100/1000BASE-T Gigabit Ethernet RJ-45 switching module |
|
48-port 1000BASE-LX (small form-factor pluggable) Gigabit Ethernet fiber optic interface switching module. |
|
48-port 10/100/1000BASE-T Gigabit Ethernet switching module. |
|
6-port Alternately-Wired 10/100/1000BASE-T Catalyst 4500 series Power over Ethernet (PoE) 802.3af or 1000BASE-X SFP. |
|
24-port 10/100/1000BASE-T RJ-45 Catalyst 4500 series PoE 802.3af. |
|
48-port 10/100/1000BASE-T, Gigabit Ethernet module with PoE IEEE 802.3af. This module is supported on Supervisor Engines 7E and7LE, but not on Supervisor Engines 8E and 8LE. This module is not supported in VSS mode. |
|
48-port 10/100/1000BASE-T, Gigabit Ethernet module with IEEE 802.3af PoEP and IEEE 802.3at PoEP. This module is supported on Supervisor Engines 7-E and7L-E, but not on Supervisor Engines 8-E and 8L-E. |
|
12-port 1000BASE-X (small form factor pluggable) module with jumbo frame support |
|
Non-blocking 24-port 1000BASEX (small form factor pluggable) module |
|
80 ports with Gigabit compact SFP (4:1 oversubscribed); 40 modules of Gigabit SFP line card (1000BaseX), providing 24 gigabits per-slot capacity (SFP optional) (2:1 oversubscribed) |
|
48 port 10/100/1000BT with 2 to 1 oversubscription and jumbo frame support |
|
48 port 10/100/1000 Mb with 2 to 1 oversubscription PoE 802.3af providing up to 20 Watts power/port |
|
48 port 10/100/1000 Mb with 2 to 1 oversubscription PoE 802.3at providing up to 30 Watts power/port |
|
48-port 10/100/1000 line card nonblocking PoE 802.3at providing up to 30 Watts power/port |
|
48-port 10/100/1000 line card nonblocking PoE 802.3at and 60 watt UPoE PoE linecard with Ethernet Energy Efficient feature. |
|
48-port 10/100/1000 nonblocking line card with the Ethernet Energy Efficient feature |
|
48-port 1000Base-X SFP (small form factor pluggable) line card |
|
24-port 1000Base-X SFP (small form factor pluggable) line card |
|
12-port 1000Base-X SFP (small form factor pluggable) line card |
|
24-port 100BASE-FX Fast Ethernet MT-RJ multimode fiber switching module. |
|
48-port 100BASE-FX Fast Ethernet MT-RJ multimode fiber switching module |
|
48-port 100BASE-LX10 Fast Ethernet MT-RJ single-mode fiber switching module. |
|
24-port 10/100BASE-TX RJ-45 Cisco Catalyst 4500 series PoE 802.3af. |
|
32-port 10/100 Fast Ethernet RJ-45, plus 2-port 1000BASE-X (GBIC) Gigabit Ethernet switching module. |
|
48-port 10/100 Fast Ethernet RJ-21 Cisco Catalyst 4500 series PoE 802.3af telco. |
|
48-port 10/100 Fast Ethernet RJ-45 Cisco Catalyst 4500 series PoE 802.3af. This module is supported only on Supervisor Engines 7-E and 7L-E, but not supported on Supervisor Engines 8-E and 8L-E. |
|
32-port 10/100 Fast Ethernet RJ-45 modular uplink switching module. |
|
32-port 10/100 Fast Ethernet, plus 2-port 1000BASE-X (GBIC) Gigabit Ethernet services module. |
|
1.To support Supervisor Engine 8-E or 8L-E, the Cisco Catalyst 4507R-E Switch chassis must have hardware revision 2.0 or higher.For information about identifying the revision numbers see the “Identifying Hardware Revisions on the Switch Chassis” section. |
Cisco 10-Gigabit Ethernet Transceiver Modules Compatibility Matrix |
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/10GE_Tx_Matrix.html |
Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix |
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/GE_Tx_Matrix.html |
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/100MB_Tx_Matrix.html |
|
Cisco Wavelength Division Multiplexing Transceivers Compatibility Matrix |
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6982.html |
Cisco 40-Gigabit Ethernet Transceiver Modules Compatibility Matrix |
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/transceiver_modules/compatibility/matrix/40GE_Tx_Matrix.html |
Table 3 Power over Ethernet on Cisco Catalyst 4500-E
Power over Ethernet on the Cisco Catalyst 4500E Series Platform Data Sheet |
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/product_data_sheet09186a00801f3dd9.html |
A brief list of primary E-Series hardware supported by Cisco IOS XE Release 3.9.xE is shown in Table 4 .
– Windows 2000, Windows 2003, Windows XP, Windows Vista, or Windows 7
– With JavaScript enabled: Internet Explorer 6.0 and 7.0, or Firefox 26.0
Table 5 is a detailed list of features supported on Catalyst 4500-E Supervisor Engine 7-E, Supervisor Engine 7L-E, Supervisor Engine 8-E, and Supervisor Engine 8L-E running Cisco IOS XE Release 3.9.xE categorized by image type. Please visit Feature Navigator for package details:
http://tools.cisco.com/ITDIT/CFN/
Note Wireless features supported on Supervisor Engine 8-E are available only on IP Base and Enterprise Services images.
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 |
|||
Cisco TrustSec—IEEE 802.1ae MACSec encryption on user facing ports |
|||
Cisco TrustSec—IEEE 802.1ae MACSec encryption on user facing ports SSO |
|||
Cisco TrustSec—IEEE 802.1ae MACSec encryption between switch-to-switch links using Cisco SAP (Security Association Protocol) |
|||
Class Based Ethernet CoS Matching & Marking (802.1p & ISL CoS) |
|||
Easy VSS2 |
|||
IEEE 802.1s Multiple Spanning Tree (MST) Standard Compliance |
|||
IEEE 802.1t3 |
|||
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 (ND) Inspection |
|||
IPv6 First Hop Security (FHS) Phase 2: Lightweight DHCPv6 Relay Agent (LDRA) Neighbor Discovery (ND) Multicast Suppress Source and Prefix Guard4 |
|||
IPv6 Multicast — Multicast Listener Discovery (MLD) Protocol, Versions 1 and 2 |
|||
IPv6 Multicast — RPF Flooding of Bootstrap Router (BSR) Packets |
|||
Yes 4 |
|||
Yes 4 |
|||
Yes5 |
|||
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 ISATAP Tunnels (in software) |
|||
IPv6 Tunneling — Automatic IPv4-compatible Tunnels (in software) |
|||
IPv6 Tunneling — Manually Configured IPv6 over IPv4 Tunnels (in software) |
|||
Medianet — Integrated Video Traffic Simulator (hardware-assisted IP SLA); IPSLA generator and responder |
|||
Medianet — 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 Access6 |
|||
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 |
|||
RPR Mode for Catalyst 4500-E In-Chassis Redundant Supervisors with VSS |
|||
Smart Install Director—Configuration-only Deployment and Smooth Upgrade |
|||
Source Specific Multicast (SSM) - IGMPv3,IGMP v3lite, and URD |
|||
Time Domain Reflectometry (TDR)7 |
|||
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) — REP, Flexlinks, UDLD, Fast UDLD |
|||
Wired Guest Access8 |
|||
The following table provides OpenFlow compatibility information for the Cisco Catalyst 4500-E Series Switches. 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.
Table 6 Image Support for OpenFlow Version and Cisco IOS Release Support for Cisco OpenFlow Plug-In
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-E series switch with Supervisor Engine 7-E and Supervisor Engine 7L-E:
The Cisco IOS XE Release 3.9.xE Documentation Roadmap provides quick and easy access to all relevant documentation for specific platforms. Look for Quick Links to Platform Documentation on the respective platform documentation pages. For more information, see http://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-xe-3e/tsd-products-support-series-home.html.
These sections describe the new and changed information for Catalyst 4500E Series Switches running Cisco IOS XE software:
As Table 12 shows, each version of Cisco IOS XE has an associated Cisco IOS version:
Table 13 lists the supported products for the wireless features.
Table 14 lists the specific supported Cisco access point models.
Table 15 lists the software compatibility matrix.
For more information on the compatibility of wireless software components across releases, see the Cisco Wireless Solutions Software Compatibility Matrix.
This section describes the interoperability of this version of the switch software release with other client devices.
Table 16 lists the client types on which the tests were conducted. The clients included laptops, handheld devices, phones, and printers.
No configuration is allowed on internal interfaces.
Status/Stats of internal ports are visible under service internal command.
– Supported only in ipbase and entservices license.
– Supported only in install mode.
– Supported only in cat4500es8-universalk9* (Crypto) images
– Requires rommon version 15.1(1r)SG5 or later
– DC bootup logs are stored in bootflash (max 5 files, 1 per reload) with dc_console_log-yyyymmdd-hhmmss-UTC format.
– After DC becomes operational, the logs are forwarded to BB's syslog. DC logs have a prefix of DC-SLOT<slot-no>:
– DC crash info and system reports are stored at crashinfo-dc: and slavecrshinfo-dc: for active-dc and stby-dc respectively
– A new AP, which has only factory default configurations, sends an L3 Broadcast Discovery message to learn and discover a WLC. Then the WLCs in the broadcast domain respond to this request. This request also has the number of APs they can support and how many APs are currently connected. The AP then would send a Join message to the least loaded WLC among the list.
– When there is an explicit primary WLC IP address configured on the AP, the AP sends a unicast WLC discovery message to this specific WLC. There could also be WLCs that the AP learned about in its past associations with the WLCs and it would send a Unicast Discovery to these WLCs too. After the WLCs respond to this query, it matches with the primary WLC name and IP address and if the match is found, it will join the WLC. If there is an invalid WLC name or IP, then it will not match and it will join the other WLCs that would have responded to the unicast query. If no other WLC responded to the AP, it would send an L3 broadcast discovery message again.
– There is a difference in behavior between how the Sup 8-E based MA or MC handles the Unicast L3 Discovery packet as compared to the Catalyst 3850 Switch in MA or MC mode.
On Catalyst 3850 Switches—Any packet received on the management VLAN is terminated and not forwarded to the unicast IP address in the discovery even if the address does not belong to itself. When a primary base IP of the WLC is configured, the MA does not forward the unicast packets and the AP therefore falls back to sending a broadcast discovery packet which terminates on the Catalyst 3850 Switch.
On Sup 8-E—On the Sup 8-E MA, however, the unicast discovery packet, if received on the management VLAN, is forwarded to the right destination based on the IP address in the discovery packet. Therefore, it reaches the destined WLC and joins it and not the SUP 8-E if the destination IP address is other than the SUP 8-E itself. This results in AP joining the MC and not the MA.
For details on how to upgrade ROMMON, refer to:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/release/note/OL_30306-01.html
Note If dual supervisor engines are present, first upgrade your software to Cisco IOS XE 3.2.0SG or higher, then upgrade your ROMMON to version 15.0(1r)SG7 to avoid an uplinks issue (CSCtj54375).
The hardware revision is a number that represents a hardware upgrade. Enter the show idprom chassis privileged EXEC command on the switch chassis to know its current revision number
Some chassis require a certain hardware revision to be operable with certain devices. For example, the Cisco Catalyst 4507R-E Switch chassis must have hardware revision 2.0 or higher to support Supervisor Engine 8-E or 8L-E. Before you install Supervisor Engine 8-E or 8L-E on the Catalyst 4507R-E Switch chassis, verify that the chassis has the required revision number.
The following is a sample output of the show idprom chassis command on a Catalyst 4507R-E Switch. Note the “ Hardware Revision
” field here is “ 2.0
”:
For Cisco IOS XE Release 3.9.xE, the ROMMON image must be upgraded to use version 15.1(1r)SG5. The IOS XE Bundle format for Supervisor Engine 8-E has changed, necessitating a new ROMMON image.
The following [error] messages might be observed if IOS XE 3.7.xE images are booted with older ROMMON images:
When supervisor engine 1 (sup1) is in ROMMON and supervisor engine 2 (sup2) is in IOS, only sup2 can read the idprom contents of chassis’ idprom. Chassis type is displayed as “+E” in the output of the show version command. Conversely, sup1 can only display the chassis type as “E.”
When both sup1 and sup2 are in ROMMON, both engines can read the chassis’ idprom. Chassis type is displayed correctly as “+E” in the output of the show version command.
When both sup1 and sup2 are in IOS, both engines can read the chassis’ idprom. Chassis type is displayed correctly as “+E” in the output of the show version command.
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.
3. Dec 5 03:57:24.121: %CAPWAP-3-ONE_AP_PER_PORT: AP (mac:6c20.56a6.4fc4) is not allowed on port:Po2. Only one AP per port is allowed.
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
– 10/100/1000BaseT Premium POE E Series WS-X4648-RJ45V+E (JAE1348OY52)
– 4 Sup 7-E 10GE (SFP+), 1000BaseX (SFP) WS-X45-SUP7-E (CAT1434L0G4)
the following restrictions apply:
– Sub-interfaces are not supported on 1 Gigabit and Ten-Gigabit interfaces.
– Port-channel members do not support multiple classification criteria for a QoS policy.
– CEF is disabled automatically when uRFP is enabled and TCAM is fully utilized.
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
Workaround: Use any X2-pluggable module on its own in the WS-X4606-X2-E line card. CSCuc70321
Workaround: Observe the show module command output. CSCua79513
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), which is the online successor to Bug Toolkit, is designed to improve the effectiveness in network risk management and device troubleshooting. The 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 tool has a provision to filter bugs based on credentials to provide external and internal bug views for the search input.
To view the details of a caveat listed in this document:
1. Access the BST (use your Cisco user ID and password) at https://tools.cisco.com/bugsearch/.
Use the Bug Search Tool to view the details of a caveat listed in this section:
Refer to the following documents for additional Catalyst 4500 series information:
http://www.cisco.com//en/US/products/hw/switches/ps4324/index.html
http://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-xe-3e/products-documentation-roadmaps-list.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/catalyst4500e/installation/guide/Eseries.html
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/hardware/configuration/notes/OL_25315.html
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
Software release notes, configuration guides, command references, and system message guides are available at the following URLs:
http://www.cisco.com/c/en/us/support/switches/catalyst-4500-series-switches/products-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
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_system_message_guides_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
You can also use the Command Lookup Tool at:
http://tools.cisco.com/Support/CLILookup/cltSearchAction.do
http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi
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 acknowledgement: “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].