Release Notes for Cisco Catalyst 9400 Series Switches, Cisco IOS XE Amsterdam 17.3.x
Introduction
Cisco Catalyst 9400 Series Switches are Cisco’s leading modular enterprise switching access platform and have been purpose-built to address emerging trends of Security, IoT, Mobility, and Cloud.
They deliver complete convergence with the rest of the Cisco Catalyst 9000 Series Switches in terms of ASIC architecture with Unified Access Data Plane (UADP) 2.0 and UADP 3.0. The platform runs an Open Cisco IOS XE that supports model driven programmability, has the capacity to host containers, and run 3rd party applications and scripts natively within the switch (by virtue of x86 CPU architecture, local storage, and a higher memory footprint). This series forms the foundational building block for SD-Access, which is Cisco’s lead enterprise architecture.
Cisco Catalyst 9400 Series Switches are enterprise optimized with a dual-serviceable fan tray design, side to side airflow, and are closet-friendly with a16-inch depth
Whats New in Cisco IOS XE Amsterdam 17.3.8a
There are no new features in this release. This release provides a fix for CSCwh87343: Cisco IOS XE Software Web UI Privilege Escalation Vulnerability. For more information, see Security Advisory: cisco-sa-iosxe-webui-privesc-j22SaA4z.
Whats New in Cisco IOS XE Amsterdam 17.3.8
Hardware Features in Cisco IOS XE Amsterdam 17.3.8
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.8
There are no new software features in this release.
Whats New in Cisco IOS XE Amsterdam 17.3.7
Hardware Features in Cisco IOS XE Amsterdam 17.3.7
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.7
There are no new software features in this release.
Whats New in Cisco IOS XE Amsterdam 17.3.6
Hardware Features in Cisco IOS XE Amsterdam 17.3.6
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.6
There are no new software features in this release.
Whats New in Cisco IOS XE Amsterdam 17.3.5
Hardware Features in Cisco IOS XE Amsterdam 17.3.5
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.5
There are no new software features in this release.
Whats New in Cisco IOS XE Amsterdam 17.3.4
Hardware Features in Cisco IOS XE Amsterdam 17.3.4
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.4
There are no new software features in this release.
Whats New in Cisco IOS XE Amsterdam 17.3.3
Hardware Features in Cisco IOS XE Amsterdam 17.3.3
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.3
|
Feature Name |
Description, Documentation Link, and License Level Information |
|---|---|
|
Smart Software Manager On-Prem (SSM On-Prem) Support for Smart Licensing Using Policy |
SSM On-Prem is an asset manager, which works in conjunction with CSSM. It enables you to administer products and licenses on your premises instead of having to directly connect to CSSM. Here, a product instance is connected to SSM On-Prem, and SSM On-Prem becomes the single point of interface with CSSM. The product instance can be configured to push the required information to SSM On-Prem. Alternatively, SSM On-Prem can be set-up to pull the required information from a product instance at a configurable frequency. After usage information is available in SSM On-Prem, you must synchronize the same with CSSM, to ensure that the product instance count, license count and license usage information is the same on both, CSSM and SSM On‐Prem. Offline and online options are available for synchronization between CSSM and SSM On‐Prem. Minimum Required SSM On-Prem Version: Version 8, Release 202102. Minimum Required Cisco IOS XE Version: Cisco IOS XE Amsterdam 17.3.3. See System Mangement → Smart Licening Using Policy and System Management Commands. (A license level does not apply) |
|
MLDP-Based MVPN |
The MLDP-based MVPN feature provides extensions to Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) label switched paths (LSPs) for transport in the Multicast Virtual Private Network (MVPN) core network. See IP Multicast Routing Configuration Guide → MLDP-Based MVPN. |
Whats New in Cisco IOS XE Amsterdam 17.3.2a
Hardware Features in Cisco IOS XE Amsterdam 17.3.2a
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.2a
|
Feature Name |
Description, Documentation Link, and License Level Information |
|---|---|
|
Smart Licensing Using Policy |
An enhanced version of Smart Licensing, with the overarching objective of providing a licensing solution that does not interrupt the operations of your network, rather, one that enables a compliance relationship to account for the hardware and software licenses you purchase and use. With this licensing model, you do not have to complete any licensing-specific operations, such as registering or generating keys before you start using the software and the licenses that are tied to it. License usage is recorded on your device with timestamps and the required workflows can be completed at a later date. Multiple options are available for license usage reporting – this depends on the topology you implement. You can use the Cisco Smart Licensing Utility (CSLU) Windows application, or report usage information directly to CSSM. A provision for offline reporting for air-gapped networks, where you download usage information and upload to CSSM, is also available. Starting with this release, Smart Licensing Using Policy is automatically enabled on the device. This is also the case when you upgrade to this release. By default, your Smart Account and Virtual Account in CSSM is enabled for Smart Licensing Using Policy. For conceptual, configuration, migration, and troubleshooting information for Smart Licensing Using Policy, see the documentation links below. See System Mangement → Smart Licening Using Policy and System Management Commands. (A license level does not apply) |
|
Cisco DNA Center Support for Smart Licensing Using Policy |
Cisco DNA Center supports Smart Licensing Using Policy functionality starting with Cisco DNA Center Release 2.2.2. The corresponding minimum required Cisco IOS XE Release on the Cisco Catalyst 9400 Series Switches is Cisco IOS XE Amsterdam 17.3.2a. Implement the “Connected to CSSM Through a Controller” topology to have Cisco DNA Center manage a product instance. When you do, the product instance records license usage, but it is the Cisco DNA Center that initiates communication with the product instance to retrieve and report usage to Cisco Smart Software Manager (CSSM), and returns the acknowledgement (RUM ACK). In order to meet reporting requirements, Cisco DNA Center provides ad hoc or on-demand reporting, as well as scheduled reporting options. See System Mangement → Smart Licening Using Policy. (A license level does not apply) |
Whats New in Cisco IOS XE Amsterdam 17.3.1
Hardware Features in Cisco IOS XE Amsterdam 17.3.1
There are no new hardware features in this release.
Software Features in Cisco IOS XE Amsterdam 17.3.1
|
Feature Name |
Description, Documentation Link, and License Level Information |
|---|---|
|
BGP EVPN VXLAN
|
The following BGP EVPN VXLAN features are introduced in this release:
See BGP EVPN VXLAN. (Network Advantage) |
|
EIGRP Loop-Free Alternate (LFA) IP Fast Reroute (IPFRR) |
Enables the Enhanced Interior Gateway Routing Protocol (EIGRP) to reduce the routing transition time to less than 50 ms by precomputing repair paths or backup routes and installing these paths or routes in the Routing Information Base (RIB). See IP Routing → Configuring EIGRP Loop-Free Alternate IP Fast Reroute. (Network Essentials and Network Advantage) |
|
Enhanced SGACL Logging |
Introduces support for Security Group Access Control List (SGACL) logging using NetFlow hardware, which allows much higher logging rates. See Cisco TrustSec → Configuring Security Group ACL Policies. (Network Essentials and Network Advantage) |
|
IEEE 1588v2, Precision Time Protocol (PTP) support |
PTP is defined in IEEE 1588 as Precision Clock Synchronization for Networked Measurements and Control Systems, and was developed to synchronize the clocks in packet-based networks that include distributed device clocks of varying precision and stability. (Network Advantage) |
|
Link Aggregation Control Protocol (LACP) 1:1 Redundancy and Dampening |
Introduces support for:
See Layer 2 → Configuring EtherChannels. (Network Essentials and Network Advantage) |
|
MACSec Support with Cisco StackWise Virtual on Line Card Ports |
Introduces support for MACSec switch-to-switch connections using both MACSec Key Agreement (MKA) and Security Association Protocol (SAP) on line card ports when Cisco StackWise Virtual is configured on the device. See Security → MACsec Encryption. (Network Advantage) |
|
MPLS QoS - WRED |
Introduces support for weighted random early detection (WRED) in MPLS Quality of Service (QoS). This feature configures WRED to use the MPLS experimental bits (EXP) to calculate the drop probability of a packet. See Multiprotocol Label Switching → Configuring MPLS QoS. (Network Advantage) |
|
MPLS VPN InterAS Option AB |
Enables different autonomous systems to interconnect by using a single Multiprotocol Border Gateway Protocol (MP-BGP) session, which is enabled globally on the router. When different autonomous systems are interconnected in an MPLS VPN InterAS Option AB configuration, the entire network configuration is scaled and simplified, and maintains IP quality of service (QoS) functions between Autonomous System Boundary Router (ASBR) peers. See Multiprotocol Label Switching → Configuring MPLS VPN InterAS Options. (Network Advantage) |
|
Open Shortest Path First Nonstop Routing (OSPF NSR) |
Enables a device with redundant Route Processors (RPs) to maintain its Open Shortest Path First (OSPF) state and adjacencies across planned and unplanned RP switchovers, by checkpointing state information from OSPF on the active RP to the standby RP. OSPF uses this checkpointed information to continue operation without interruption when the switchover to standby RP occurs. See IP Routing. (Network Advantage) |
|
OSPFv2 Loop-Free Alternate (LFA) IP Fast Reroute (IP FRR) |
Enables Open Shortest Path First version 2 (OSPFv2) to use a precomputed alternate next hop to reduce failure reaction time when the primary next hop fails. You can configure a per-prefix LFA path that redirects traffic to a next hop other than the primary neighbor. See IP Routing → Configuring OSPFv2 Loop-Free Alternate IP Fast Reroute. (Network Essentials and Network Advantage) |
|
PoE Power Management |
Enables you to set port priority on interfaces, to determine which interface will shut down first in case of a power outage. See Interface and Hardware Components → Configuring Power over Ethernet. (Network Essentials and Network Advantage) |
|
Private VLAN (PVLAN) on Trunk Ports and Portchannels |
Enables configuration of private VLANs on isolated trunk ports, promiscuous trunk ports, and on port channels. See VLAN → Configuring Private VLANs. (Network Essentials and Network Advantage) |
|
Programmability
|
The following programmability features are introduced in this release:
|
|
Switch Integrated Security Features (SISF) - Throttling of ARP Packets |
Starting with this release, ARP packets are throttled to mitigate high CPU utilization scenarios. In a five second window, a maximum of 50 ARP broadcast packets per binding entry are processed by SISF. When the limit is reached, incoming ARP packets are dropped. Note that the limit of 50 in five seconds is for each binding entry, that is, for each source IP. |
|
VPLS: Routed Pseudowire IRB for IPv6 Unicast |
Introduces IPv6 support for Virtual Private LAN Service (VPLS) Routed Pseudowire Integrated Routing and Bridging (IRB). VPLS Routed Pseudowire enables a switch interface to route traffic instead of using a router. See Multiprotocol Label Switching → Configuring VPLS: Routed Pseudowire IRB for IPv6 Unicast. (Network Advantage) |
|
New on the Web UI |
|
|
There are no new features on the Web UI in this release. |
|
|
Serviceability |
|
|
monitor capture match |
The command was modified. The following keywords were introduced:
|
|
show bootflash: |
The command was modified. The following keywords were introduced:
|
|
show platform hardware fed active fwd-asic counters tla |
|
|
show switch stack-ports |
The command was modified. The detail keyword was introduced. It displays the stack interface link status and errors. |
|
show mpls ldp |
The command was introduced. It provides the following options:
|
|
show tech-support |
The command was modified. The following keywords were introduced:
|
|
System Report Files - Hostname |
In a complex network it is difficult to track the origin of a system-report file. In order to make the reports easily and uniquely identifiable, the hostname is now prepended to the system-report file name. |
Important Notes
Cisco StackWise Virtual - Supported and Unsupported Features
When you enable Cisco StackWise Virtual on the device
-
Layer 2, Layer 3, Security, Quality of Service, Multicast, Application, Monitoring and Management, Multiprotocol Label Switching, High Availability, VXLAN BGP EVPN, and Cisco Sofware-Defined Access are supported.
Contact the Cisco Technical Support Centre for the specific list of features that are supported under each one of these technologies.
-
Resilient Ethernet Protocol and Remote Switched Port Analyzer are NOT supported
Unsupported Features
-
Audio Video Bridging (including IEEE802.1AS, IEEE 802.1Qat, and IEEE 802.1Qav)
-
Cisco TrustSec Network Device Admission Control (NDAC) on Uplinks
-
Converged Access for Branch Deployments
-
Fast PoE
-
IPsec VPN
-
MACsec Switch to Switch Connections on C9400-SUP-1XL-Y.
-
Performance Monitoring (PerfMon)
-
Virtual Routing and Forwarding (VRF)-Aware web authentication
Complete List of Supported Features
For the complete list of features supported on a platform, see the Cisco Feature Navigator at https://cfnng.cisco.com.
Default Behaviour
Beginning from Cisco IOS XE Gibraltar 16.12.5 and later, do not fragment bit (DF bit) in the IP packet is always set to 0 for all outgoing RADIUS packets (packets that originate from the device towards the RADIUS server).
Supported Hardware
Cisco Catalyst 9400 Series Switches—Model Numbers
The following table lists the supported switch models. For information about the available license levels, see section License Levels.
|
Switch Model (append with “=” for spares) |
Description |
|---|---|
|
C9404R |
Cisco Catalyst 9400 Series 4 slot chassis
|
|
C9407R |
Cisco Catalyst 9400 Series 7 slot chassis
|
|
C9410R |
Cisco Catalyst 9400 Series 10 slot chassis
|
Supported Hardware on Cisco Catalyst 9400 Series Switches
|
Product ID (append with “=” for spares) |
Description |
|---|---|
|
Supervisor Modules |
|
|
C9400-SUP-1 |
Cisco Catalyst 9400 Series Supervisor 1 Module This supervisor module is supported on the C9404R, C9407R, and C9410R chassis. |
|
C9400-SUP-1XL |
Cisco Catalyst 9400 Series Supervisor 1XL Module This supervisor module is supported on the C9404R, C9407R, and C9410R chassis. |
|
C9400-SUP-1XL-Y |
Cisco Catalyst 9400 Series Supervisor 25XL Module This supervisor module is supported on the C9404R, C9407R, and C9410R chassis. |
|
Line Cards |
|
|
C9400-LC-24S |
24-port, 1 Gigabit Ethernet SFP module that supports 100/1000 BASET-T with Cu-SFP |
|
C9400-LC-24XS |
24-port Gigabit Ethernet module that supports 1 and 10 Gbps connectivity. |
|
C9400-LC-48H |
48-port Gigabit Ethernet UPOE+ module supporting up to 90W on each of its 48 RJ45 ports. |
|
C9400-LC-48P |
48-port, 1 Gigabit Ethernet POE/POE+ module supporting up to 30W per port. |
|
C9400-LC-48S |
48-port, 1 Gigabit Ethernet SFP module that supports 100/1000 BASET-T with Cu-SFP. |
|
C9400-LC-48T |
48-port, 10/100/1000 BASE-T Gigabit Ethernet module. |
|
C9400-LC-48U |
48-port UPOE 10/100/1000 (RJ-45) module supporting up to 60W per port. |
|
C9400-LC-48UX |
48-port, UPOE Multigigabit Ethernet Module with:
|
|
M.2 SATA SSD Modules1 (for the Supervisor) |
|
|
C9400-SSD-240GB |
Cisco Catalyst 9400 Series 240GB M2 SATA memory |
|
C9400-SSD-480GB |
Cisco Catalyst 9400 Series 480GB M2 SATA memory |
|
C9400-SSD-960GB |
Cisco Catalyst 9400 Series 960GB M2 SATA memory |
|
AC Power Supply Modules |
|
|
C9400-PWR-2100AC |
Cisco Catalyst 9400 Series 2100W AC Power Supply |
|
C9400-PWR-3200AC |
Cisco Catalyst 9400 Series 3200W AC Power Supply |
|
DC Power Supply Modules |
|
|
C9400-PWR-3200DC |
Cisco Catalyst 9400 Series 3200W DC Power Supply |
Optics Modules
Cisco Catalyst Series Switches support a wide range of optics and the list of supported optics is updated on a regular basis. Use the Transceiver Module Group (TMG) Compatibility Matrix tool, or consult the tables at this URL for the latest transceiver module compatibility information: https://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
Compatibility Matrix
The following table provides software compatibility information between Cisco Catalyst 9400 Series Switches, Cisco Identity Services Engine, Cisco Access Control Server, and Cisco Prime Infrastructure.
|
Catalyst 9400 |
Cisco Identity Services Engine |
Cisco Access Control Server |
Cisco Prime Infrastructure |
|---|---|---|---|
|
Amsterdam 17.3.8a |
2.7 |
- |
PI 3.10 + PI 3.10 latest maintenance release + PI 3.10 latest device pack See Cisco Prime Infrastructure 3.10 → Downloads. |
|
Amsterdam 17.3.8 |
2.7 |
- |
PI 3.10 + PI 3.10 latest maintenance release + PI 3.10 latest device pack See Cisco Prime Infrastructure 3.10 → Downloads. |
|
Amsterdam 17.3.7 |
2.7 |
- |
PI 3.10 + PI 3.10 latest maintenance release + PI 3.10 latest device pack See Cisco Prime Infrastructure 3.10 → Downloads. |
|
Amsterdam 17.3.6 |
2.7 |
- |
PI 3.10 + PI 3.10 latest maintenance release + PI 3.10 latest device pack See Cisco Prime Infrastructure 3.10 → Downloads. |
|
Amsterdam 17.3.5 |
2.7 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Amsterdam 17.3.4 |
2.7 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Amsterdam 17.3.3 |
2.7 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Amsterdam 17.3.2a |
2.7 |
- |
PI 3.8 + PI 3.8 latest maintenance release + PI 3.8 latest device pack See Cisco Prime Infrastructure 3.8 → Downloads. |
|
Amsterdam 17.3.1 |
2.7 |
- |
PI 3.8 + PI 3.8 latest maintenance release + PI 3.8 latest device pack See Cisco Prime Infrastructure 3.8 → Downloads. |
|
Amsterdam 17.2.1 |
2.7 |
- |
PI 3.7 + PI 3.7 latest maintenance release + PI 3.7 latest device pack See Cisco Prime Infrastructure 3.7 → Downloads. |
|
Amsterdam 17.1.1 |
2.7 |
- |
PI 3.6 + PI 3.6 latest maintenance release + PI 3.6 latest device pack See Cisco Prime Infrastructure 3.6 → Downloads. |
|
Gibraltar 16.12.8 |
2.6 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Gibraltar 16.12.7 |
2.6 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Gibraltar 16.12.6 |
2.6 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Gibraltar 16.12.5b |
2.6 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Gibraltar 16.12.5 |
2.6 |
- |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Gibraltar 16.12.4 |
2.6 |
- |
PI 3.8 + PI 3.8 latest maintenance release + PI 3.8 latest device pack See Cisco Prime Infrastructure 3.8 → Downloads. |
|
Gibraltar 16.12.3a |
2.6 |
- |
PI 3.5 + PI 3.5 latest maintenance release + PI 3.5 latest device pack See Cisco Prime Infrastructure 3.5 → Downloads. |
|
Gibraltar 16.12.3 |
2.6 |
- |
PI 3.5 + PI 3.5 latest maintenance release + PI 3.5 latest device pack See Cisco Prime Infrastructure 3.5 → Downloads. |
|
Gibraltar 16.12.2 |
2.6 |
- |
PI 3.5 + PI 3.5 latest maintenance release + PI 3.5 latest device pack See Cisco Prime Infrastructure 3.5 → Downloads. |
|
Gibraltar 16.12.1 |
2.6 |
- |
PI 3.5 + PI 3.5 latest maintenance release + PI 3.5 latest device pack See Cisco Prime Infrastructure 3.5 → Downloads. |
|
Gibraltar 16.11.1 |
2.6 2.4 Patch 5 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4 → Downloads. |
|
Gibraltar 16.10.1 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
| Fuji 16.9.8 |
2.5 2.1 |
5.4 5.5 |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Fuji 16.9.7 |
2.5 2.1 |
5.4 5.5 |
PI 3.9 + PI 3.9 latest maintenance release + PI 3.9 latest device pack See Cisco Prime Infrastructure 3.9 → Downloads. |
|
Fuji 16.9.6 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
|
Fuji 16.9.5 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
|
Fuji 16.9.4 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
|
Fuji 16.9.3 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
|
Fuji 16.9.2 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest maintenance release + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
|
Fuji 16.9.1 |
2.3 Patch 1 2.4 Patch 1 |
5.4 5.5 |
PI 3.4 + PI 3.4 latest device pack See Cisco Prime Infrastructure 3.4→ Downloads. |
|
Fuji 16.8.1a |
2.3 Patch 1 2.4 |
5.4 5.5 |
PI 3.3 + PI 3.3 latest maintenance release + PI 3.3 latest device pack See Cisco Prime Infrastructure 3.3→ Downloads. |
| Everest 16.6.4a |
2.2 2.3 |
5.4 5.5 |
PI 3.1.6 + Device Pack 13 See Cisco Prime Infrastructure 3.1 → Downloads. |
| Everest 16.6.4 |
2.2 2.3 |
5.4 5.5 |
PI 3.1.6 + Device Pack 13 See Cisco Prime Infrastructure 3.1 → Downloads. |
|
Everest 16.6.3 |
2.2 2.3 |
5.4 5.5 |
PI 3.1.6 + Device Pack 13 See Cisco Prime Infrastructure 3.1 → Downloads |
|
Everest 16.6.2 |
2.2 2.3 |
5.4 5.5 |
PI 3.1.6 + Device Pack 13 See Cisco Prime Infrastructure 3.1 → Downloads |
|
Everest 16.6.1 |
2.2 |
5.4 5.5 |
PI 3.1.6 + Device Pack 13 See Cisco Prime Infrastructure 3.1 → Downloads |
Web UI System Requirements
The following subsections list the hardware and software required to access the Web UI:
Minimum Hardware Requirements
|
Processor Speed |
DRAM |
Number of Colors |
Resolution |
Font Size |
|---|---|---|---|---|
|
233 MHz minimum2 |
512 MB3 |
256 |
1280 x 800 or higher |
Small |
Software Requirements
Operating Systems
-
Windows 10 or later
-
Mac OS X 10.9.5 or later
Browsers
-
Google Chrome—Version 59 or later (On Windows and Mac)
-
Microsoft Edge
-
Mozilla Firefox—Version 54 or later (On Windows and Mac)
-
Safari—Version 10 or later (On Mac)
ROMMON and CPLD Versions
ROM Monitor (ROMMON)
ROMMON, also known as the boot loader, is firmware that runs when the device is powered up or reset. It initializes the processor hardware and boots the operating system software (Cisco IOS XE software image). The ROMMON is stored on the following Serial Peripheral Interface (SPI) flash devices on your switch:
-
Primary: The ROMMON stored here is the one the system boots every time the device is powered-on or reset.
-
Golden: The ROMMON stored here is a backup copy. If the one in the primary is corrupted, the system automatically boots the ROMMON in the golden SPI flash device.
ROMMON upgrades may be required to resolve firmware defects, or to support new features, but there may not be new versions with every release.
Complex Programmable Logic Device (CPLD)
CPLD refers to hardware-programmable firmware. CPLD upgrades are not mandatory but may be required to resolve firmware defects, or to support new features. The upgrade process can be completed after upgrading the software image. There may not be new CPLD versions with every release.
The following table provides ROMMON and CPLD version information for the Cisco Catalyst 9400 Series Supervisor Modules. For ROMMON and CPLD version information of Cisco IOS XE 16.x.x releases, refer to the corresponding Cisco IOS XE 16.x.x release notes of the respective platform.
|
Release |
ROMMON Version (C9400-SUP-1, C9400-SUP-1XL, C9400-SUP-1XL-Y) |
CPLD Version (C9400-SUP-1, C9400-SUP-1XL, C9400-SUP-1XL-Y) |
ROMMON Version (C9400X-SUP-2, C9400X-SUP-2XL) |
CPLD Version (C9400X-SUP-2, C9400X-SUP-2XL) |
|---|---|---|---|---|
|
Amsterdam 17.3.8a |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.8 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.7 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.6 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.5 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.4 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.3 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.2a |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.3.1 |
17.3.1r[FC2] |
19082605 |
- |
- |
|
Amsterdam 17.2.1 |
17.1.1r |
19082605 |
- |
- |
|
Amsterdam 17.1.1 |
17.1.1r |
19032905 |
- |
- |
Upgrading the Switch Software
This section covers the various aspects of upgrading or downgrading the device software.
 Note |
You cannot use the Web UI to install, upgrade, or downgrade device software. |
Finding the Software Version
The package files for the Cisco IOS XE software are stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch.
Note |
Although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration and does not change if you upgrade the software license. |
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Software Images
|
Release |
Image Type |
File Name |
|---|---|---|
|
Cisco IOS XE Amsterdam 17.3.8a |
CAT9K_IOSXE |
cat9k_iosxe.17.03.08a.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.08a.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.8 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.08.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.08.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.7 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.07.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.07.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.6 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.06.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.06.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.5 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.05.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.05.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.4 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.04.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.04.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.3 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.03.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.03.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.2a |
CAT9K_IOSXE |
cat9k_iosxe.17.03.02a.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.02a.SPA.bin |
|
|
Cisco IOS XE Amsterdam 17.3.1 |
CAT9K_IOSXE |
cat9k_iosxe.17.03.01.SPA.bin |
|
No Payload Encryption (NPE) |
cat9k_iosxe_npe.17.03.01.SPA.bin |
Upgrading the ROMMON
To know the ROMMON or bootloader version that applies to every major and maintenance release, see ROMMON and CPLD Versions.
You can upgrade the ROMMON before, or, after upgrading the software version. If a new ROMMON version is available for the software version you are upgrading to, proceed as follows:
-
Upgrading the ROMMON in the primary SPI flash device
This ROMMON is upgraded automatically. When you upgrade from an existing release on your switch to a later or newer release for the first time, and there is a new ROMMON version in the new release, the system automatically upgrades the ROMMON in the primary SPI flash device, based on the hardware version of the switch when you boot up your switch with the new image for the first time.
-
Upgrading the ROMMON in the golden SPI flash device
You must manually upgrade this ROMMON. Enter the upgrade rom-monitor capsule golden switch command in privileged EXEC mode.
Note
-
Golden ROMMON upgrade is only applicable to Cisco IOS XE Amsterdam 17.3.5 and later releases.
-
Golden ROMMON upgrade will fail if the FPGA version is 17101705 or older. To upgrade the FPGA version, see Upgrading the Complex Programmable Logic Device Version.
-
In case of a Cisco StackWise Virtual setup, upgrade the active and standby supervisor modules.
-
In case of a High Availability set up, upgrade the active and standby supervisor modules.
-
After the ROMMON is upgraded, it will take effect on the next reload. If you go back to an older release after this, the ROMMON is not downgraded. The updated ROMMON supports all previous releases.
Software Installation Commands
|
Summary of Software Installation Commands |
|
|---|---|
|
To install and activate the specified file, and to commit changes to be persistent across reloads:
To separately install, activate, commit, cancel, or remove the installation file: |
|
|
add file tftp: filename |
Copies the install file package from a remote location to the device and performs a compatibility check for the platform and image versions. |
|
activate [ auto-abort-timer] |
Activates the file, and reloads the device. The auto-abort-timer keyword automatically rolls back image activation. |
|
commit |
Makes changes persistent over reloads. |
|
rollback to committed |
Rolls back the update to the last committed version. |
|
abort |
Cancels file activation, and rolls back to the version that was running before the current installation procedure started. |
|
remove |
Deletes all unused and inactive software installation files. |
Upgrading in Install Mode
Follow these instructions to upgrade from one release to another, in install mode. To perform a software image upgrade, you must be booted into IOS via boot flash:packages.conf .
Before you begin
 Caution |
You must comply with these cautionary guidelines during an upgrade:
|
Note |
Disconnecting and reconnecting power to a Cisco Catalyst 9400 Series Supervisor 1 Module within a 5-second window, can corrupt the boot SPI. |
Note that you can use this procedure for the following upgrade scenarios.
|
When upgrading from ... |
Permitted Supervisor Setup (Applies to the release you are upgrading from) |
First upgrade to... |
To upgrade to ... |
||
|---|---|---|---|---|---|
|
Cisco IOS XE Everest 16.6.14
|
Upgrade a single supervisor, and complete the boot loader and CPLD upgrade. After completing the first supervisor upgrade, remove and swap in the second supervisor. After both supervisors are upgraded, they can be inserted and booted in a high availability setup.
|
Cisco IOS XE Everest 16.6.3 Follow the upgrade steps as in the Release Notes for Cisco Catalyst 9400 Series Switches, Cisco IOS XE Everest 16.6.x → Upgrading the Switch Software → Upgrading in Install Mode |
Cisco IOS XE Amsterdam 17.3.x |
||
|
Cisco IOS XE Everest 16.6.2 and later releases |
This procedure automatically copies the images to both active and standby supervisor modules. Both supervisor modules are simultaneously upgraded. |
Not applicable |
When upgrading from Cisco IOS XE Everest 16.6.1 to a later release, the upgrade may take a long time, and the system will reset three times due to rommon and complex programmable logic device (CPLD) upgrade. Stateful switchover is supported from Cisco IOS XE Everest 16.6.2
Use the procedure described here to upgrade the device in the following configurations:
-
Standalone
-
Cisco StackWise Virtual
-
Cisco StackWise Virtual without ISSU
The sample output in this section displays upgrade from Cisco IOS XE Amsterdam 17.2.1 to Cisco IOS XE Amsterdam 17.3.1 using install commands.
Procedure
|
Step 1 |
Clean-up install remove inactive
Use this command to clean-up old installation files in case of insufficient space and to ensure that you have at least 1GB of space in flash, to expand a new image. The following sample output displays the cleaning up of unused files, by using the install remove inactive command:
|
||
|
Step 2 |
Copy new image to flash |
||
|
Step 3 |
Set boot variable |
||
|
Step 4 |
Install image to flash install add file activate commit
Use this command to install the image. The following sample output displays installation of the Cisco IOS XE Amsterdam 17.3.1 software image in the flash memory:
|
||
|
Step 5 |
Verify installation After the software has been successfully installed, check that the ten new After the image boots up, use this command to verify the version of the new image. The following sample output of the show version command displays the Cisco IOS XE Amsterdam 17.3.1 image on the device:
|
Downgrading in Install Mode
Follow these instructions to downgrade from one release to another, in install mode. To perform a software image downgrade, you must be booted into IOS via boot flash:packages.conf .
Before you begin
Note that you can use this procedure for the following downgrade scenarios:
|
When downgrading from ... |
Permitted Supervisor Setup (Applies to the release you are downgrading from) |
To ... |
||
|---|---|---|---|---|
|
Cisco IOS XE Amsterdam 17.3.x |
This procedure automatically copies the images to both active and standby supervisor modules. Both supervisor modules are simultaneously downgraded.
|
Cisco IOS XE Amsterdam 17.2.x or earlier releases. |
Note |
New switch models that are introduced in a release cannot be downgraded. The release in which a module is introduced is the minimum software version for that model. We recommend upgrading all existing hardware to the same release as the latest hardware. |
Use the procedure described here to downgrade the device in the following configurations:
-
Standalone
-
Cisco StackWise Virtual
-
Cisco StackWise Virtual without ISSU
The sample output in this section shows downgrade from Cisco IOS XE Amsterdam 17.3.1 to Cisco IOS XE Amsterdam 17.2.1, using install commands.
Procedure
|
Step 1 |
Clean-up install remove inactive
Use this command to clean-up old installation files in case of insufficient space and to ensure that you have at least 1GB of space in flash, to expand a new image. The following sample output displays the cleaning up of unused files, by using the install remove inactive command:
|
||
|
Step 2 |
Copy new image to flash |
||
|
Step 3 |
Set boot variable |
||
|
Step 4 |
Downgrade software image Use one of these options, to downgrade:
The following example displays the installation of the
cat9k_iosxe.17.02.01.SPA.bin software image to flash, to downgrade the switch by using the install add file activate commit command. You can point to the source image on your tftp server or in flash if you have it copied to flash.The following example displays sample output when downgrading the switch by using the install rollback to committed command.
|
||
|
Step 5 |
Verify version show version
After the image boots up, use this command to verify the version of the new image.
The following sample output of the show version command displays the Cisco IOS XE Amsterdam 17.2.1 image on the device:
|
In Service Software Upgrade (ISSU) with Cisco StackWise Virtual and Dual Supervisor Module Configuration
Follow the instructions described here to perform an In Service Software Upgrade (ISSU) upgrade. Use the procedure described here, only for the releases indicated in the table below. For more general information about ISSU release support and recommended releases, see this technical reference document: In-Service Software Upgrade (ISSU).
Before you begin
Note that you can use this ISSU procedure only for the following scenarios:
|
When upgrading from... |
Use these commands... |
To... |
|---|---|---|
|
Cisco IOS XE Amsterdam 17.3.1 |
install add file activate issu commit |
Cisco IOS XE Amsterdam 17.3.x |
|
Not applicable |
ISSU does not support downgrade. To downgrade, see Downgrading in Install Mode. |
Not applicable |
Procedure
|
Step 1 |
enable Enables privileged EXEC mode. Enter your password if prompted. |
|
Step 2 |
install add file activate issu commit Use this command to automate the sequence of all the upgrade procedures, including downloading the images to both the switches, expanding the images into packages, and upgrading each switch as per the procedures. The following sample output displays installation of Cisco IOS XE Amsterdam 17.3.2a software image with ISSU procedure. |
|
Step 3 |
show version Use this command to verify the version of the new image. The following sample output of the show version
command displays the Cisco IOS XE Amsterdam 17.3.2a image on the
device:
|
|
Step 4 |
show issu state [detail] Use this command to verify that no ISSU process is in pending state. |
|
Step 5 |
exit Exits privileged EXEC mode and returns to user EXEC mode. |
Upgrading the Complex Programmable Logic Device Version
You can trigger a CPLD version upgrade after upgrading the software image. During CPLD upgrade, the supervisor module automatically power cycles. This completes the CPLD upgrade process for the supervisor module but also causes traffic disruption. Therefore, auto-upgrade of CPLD is not supported. You must manually perform CPLD upgrade.
Upgrading the CPLD Version: High Availability Setup
Beginning in the privileged EXEC mode, complete the following steps:
Before you begin
When performing the CPLD version upgrade as shown, the show platform command can be used to confirm the CPLD version after the upgrade. This command output shows the CPLD version on all modules. However, the CPLD upgrade only applies to the supervisors, not the line cards. The line cards CPLD version is a cosmetic display. After the upgrade is completed in a high availability setup, the supervisors will be upgraded, but the line cards will still show the old CPLD version. The version mismatch between the supervisors and line cards is expected until a chassis reload.
Procedure
|
Step 1 |
Upgrade the CPLD Version of the standby supervisor module Enter the following commands on the active supervisor:
The standby supervisor module reloads automatically and the upgrade occurs in ROMMON. During the upgrade, the supervisor module automatically power cycles and remains inactive for approximately 5 minutes. Wait until the standby supervisor module boots up and the SSO has formed (HOT) before you proceed to the next step; this takes approximately 17 minutes. |
||
|
Step 2 |
Perform a switch over
This causes the standby supervisor (on which you have completed the CPLD upgrade in Step 1) to become the active supervisor module |
||
|
Step 3 |
Upgrade the CPLD Version of the new standby supervisor module Repeat Step 1 and all its substeps.
|
Upgrading the CPLD Version: Cisco StackWise Virtual Setup
Beginning in the privileged EXEC mode, complete the following steps:
Procedure
|
Step 1 |
Upgrade the CPLD version of the standby supervisor module Enter the following commands on the active supervisor: |
|
Step 2 |
Reload the standby supervisor module
The upgrade occurs in ROMMON. During the upgrade, the supervisor module automatically power cycles and remains inactive for approximately 5 minutes. Wait until the standby supervisor module boots up and the SSO has formed (HOT) before you proceed to the next step; this takes approximately 17 minutes. |
|
Step 3 |
Perform a switch over
This causes the standby supervisor (on which you have completed the CPLD upgrade in step 1) to become the active supervisor module |
|
Step 4 |
Upgrade the CPLD version of the new standby supervisor module Perfom Steps 1 and 2, including all substeps, on the new standby supervisor module |
Upgrading the CPLD Version: Single Supervisor Module Setup
Beginning in the privileged EXEC mode, complete the following steps:
Procedure
|
Upgrade the CPLD version of the active supervisor module Enter the following commands on the active supervisor:
The supervisor module reloads automatically and the upgrade occurs in ROMMON. During the upgrade, the supervisor module automatically power cycles and remains inactive for approximately 5 minutes. |
Licensing
This section provides information about the licensing packages for features available on Cisco Catalyst 9000 Series Switches.
License Levels
The software features available on Cisco Catalyst 9400 Series Switches fall under these base or add-on license levels.
Base Licenses
-
Network Essentials
-
Network Advantage—Includes features available with the Network Essentials license and more.
Add-On Licenses
Add-On Licenses require a Network Essentials or Network Advantage as a pre-requisite. The features 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).
-
DNA Essentials
-
DNA Advantage— Includes features available with the DNA Essentials license and more.
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 https://cfnng.cisco.com. An account on cisco.com is not required.
Available Licensing Models and Configuration Information
-
Cisco IOS XE Fuji 16.8.x and earlier: RTU Licensing is the default and the only supported method to manage licenses.
-
Cisco IOS XE Fuji 16.9.1 to Cisco IOS XE Amsterdam 17.3.1: Smart Licensing is the default and the only supported method to manage licenses.
In the software configuration guide of the required release, see System Management → Configuring Smart Licensing.
-
Cisco IOS XE Amsterdam 17.3.2a and later: Smart Licensing Using Policy, which is an enhanced version of Smart Licensing, is the default and the only supported method to manage licenses.
For more information, see Configuring Licenses on Cisco Catalyst 9000 Series Switches.
For a more detailed overview on Cisco Licensing, go to Cisco Software Licensing Guide.
License Levels - Usage Guidelines
-
The duration or term for which a purchased license is valid:
Smart Licensing Using Policy
Smart Licensing
-
Perpetual: There is no expiration date for such a license.
-
Subscription: The license is valid only until a certain date (for a three, five, or seven year period).
-
Permanent: for a license level, and without an expiration date.
-
Term: for a license level, and for a three, five, or seven year period.
-
Evaluation: a license that is not registered.
-
-
Base licenses (Network Essentials and Network-Advantage) are ordered and fulfilled only with a perpetual or permanent license type.
-
Add-on licenses (DNA Essentials and DNA Advantage) are ordered and fulfilled only with a subscription or term license type.
-
An add-on license level is included when you choose a network license level. If you use DNA features, renew the license before term expiry, to continue using it, or deactivate the add-on license and then reload the switch to continue operating with the base license capabilities.
-
When ordering an add-on license with a base license, note the combinations that are permitted and those that are not permitted:
Table 1. Permitted Combinations DNA Essentials
DNA Advantage
Network Essentials
Yes
No
Network Advantage
Yes5
Yes
5 You will be able to purchase this combination only at the time of the DNA license renewal and not when you purchase DNA-Essentials the first time. -
Evaluation licenses cannot be ordered. They are not tracked via Cisco Smart Software Manager and expire after a 90-day period. Evaluation licenses can be used only once on the switch and cannot be regenerated. Warning system messages about an evaluation license expiry are generated only 275 days after expiration and every week thereafter. An expired evaluation license cannot be reactivated after reload. This applies only to Smart Licensing. The notion of evaluation licenses does not apply to Smart Licensing Using Policy.
Scaling Guidelines
For information about feature scaling guidelines, see these datasheets for Cisco Catalyst 9400 Series Switches:
Limitations and Restrictions
-
Control Plane Policing (CoPP)—The show run command does not display information about classes configured under
system-cpp policy, when they are left at default values. Use the show policy-map system-cpp-policy or the show policy-map control-plane commands in privileged EXEC mode instead. -
Cisco TrustSec restrictions—Cisco TrustSec can be configured only on physical interfaces, not on logical interfaces.
-
Flexible NetFlow limitations
-
You cannot configure NetFlow export using the Ethernet Management port (GigabitEthernet0/0).
-
You can not configure a flow monitor on logical interfaces, such as layer 2 port-channels, loopback, tunnels.
-
You can not configure multiple flow monitors of same type (ipv4, ipv6 or datalink) on the same interface for same direction.
-
-
Hardware limitations—When you use Cisco QSFP-4SFP10G-CUxM Direct-Attach Copper Cables, autonegotiation is enabled by default. If the other end of the line does not support autonegotation, the link does not come up.
-
Interoperability limitations—When you use Cisco QSFP-4SFP10G-CUxM Direct-Attach Copper Cables, if one end of the 40G link is a Catalyst 9400 Series Switch and the other end is a Catalyst 9500 Series Switch, the link does not come up, or comes up on one side and stays down on the other. To avoid this interoperability issue between devices, apply the the speed nonegotiate command on the Catalyst 9500 Series Switch interface. This command disables autonegotiation and brings the link up. To restore autonegotiation, use the no speed nonegotiation command.
-
In-Service Software Upgrade (ISSU)
-
ISSU from Cisco IOS XE Fuji 16.9.x to Cisco IOS XE Gibraltar 16.10.x or to Cisco IOS XE Gibraltar 16.11.x is not supported. This applies to both a single and dual supervisor module setup.
-
While performing ISSU from Cisco IOS XE Fuji 16.9.x to Cisco IOS XE Gibraltar 16.12.x, if interface-id snmp-if-index command is not configured with OSPFv3, packet loss can occur. Configure the interface-id snmp-if-index command either during the maintenance window or after isolating the device (by using maintenance mode feature) from the network before doing the ISSU.
-
While ISSU allows you to perform upgrades with zero downtime, we recommend you to do so during a maintenance window only.
-
If a new feature introduced in a software release requires a change in configuration, the feature should not be enabled during ISSU.
-
If a feature is not available in the downgraded version of a software image, the feature should be disabled before initiating ISSU.
-
-
M.2 SATA SSD drive: With bootloader version 16.6.2r, you cannot access the M.2 SATA SSD drive at the ROMMON prompt (
rommon> dir disk0). The system displays an error message indicating that the corresponding file system protocol is not found on the device. The only way to access the drive when on bootloader version 16.6.2r, is through the Cisco IOS prompt, after boot up. -
No service password recovery—With ROMMON versions R16.6.1r and R16.6.2r, the 'no service password-recovery' feature is not available.
-
QoS restrictions
-
When configuring QoS queuing policy, the sum of the queuing buffer should not exceed 100%.
-
For QoS policies, only switched virtual interfaces (SVI) are supported for logical interfaces.
-
QoS policies are not supported for port-channel interfaces, tunnel interfaces, and other logical interfaces.
-
Stack Queuing and Scheduling (SQS) drops CPU bound packets exceeding 1.4 Gbps.
-
-
Redundancy—The supervisor module (hardware) supports redundancy. Software redundancy is supported starting with Cisco IOS XE Everest 16.6.2. However, the associated route processor redundancy (RPR) feature is not supported.
Before performing a switchover, use the show redundancy , show platform , and show platform software iomd redundancy commands to ensure that both the SSOs have formed and that the IOMD process is completed.
In the following sample output for the show redundancy , note that both the SSOs have formed.Switch# show redundancy Redundant System Information : ------------------------------ Available system uptime = 3 hours, 30 minutes Switchovers system experienced = 2 Standby failures = 0 Last switchover reason = active unit removed Hardware Mode = Duplex Configured Redundancy Mode = sso Operating Redundancy Mode = sso Maintenance Mode = Disabled Communications = Up Current Processor Information : ------------------------------- Active Location = slot 3 Current Software state = ACTIVE Uptime in current state = 2 hours, 57 minutes Image Version = Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.8.1, RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2018 by Cisco Systems, Inc. Compiled Tue 27-Mar-18 13:43 by mcpre BOOT = bootflash:packages.conf; CONFIG_FILE = Configuration register = 0x1822 Peer Processor Information : ---------------------------- Standby Location = slot 4 Current Software state = STANDBY HOT Uptime in current state = 2 hours, 47 minutes Image Version = Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.8.1, RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2018 by Cisco Systems, Inc. Compiled Tue 27-Mar-18 13:43 by mcpre BOOT = bootflash:packages.conf; CONFIG_FILE = Configuration register = 0x1822In the following sample output for the show platform software iomd redundancy command, note that both SSOs have formed and theHA_STATEfield isready.Switch# show platform software iomd redundancy Configured Redundancy Mode = sso Operating Redundancy Mode = sso Local RF state = ACTIVE Peer RF state = STANDBY HOT slot PSM STATE SPA INTF HA_STATE HA_ACTIVE 1 ready started ready 00:01:16 2 ready started ready 00:01:22 3 ready started ready 00:01:27 ***active RP 4 ready started ready 00:01:27 <output truncated>In the following sample output for the show platform command, note that theStatefor all the linecards and supervisor modules isok. This indicates that the IOMD processes are completed.Switch# show platform Chassis type: C9407R Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 1 C9400-LC-24XS ok 3d09h 2 C9400-LC-48U ok 3d09h R0 C9400-SUP-1 ok, active 3d09h R1 C9400-SUP-1 ok, standby 3d09h P1 C9400-PWR-3200AC ok 3d08h P2 C9400-PWR-3200AC ok 3d08h P17 C9407-FAN ok 3d08h <output truncated> -
Secure Shell (SSH)
-
Use SSH Version 2. SSH Version 1 is not supported.
-
When the device is running SCP and SSH cryptographic operations, expect high CPU until the SCP read process is completed. SCP supports file transfers between hosts on a network and uses SSH for the transfer.
Since SCP and SSH operations are currently not supported on the hardware crypto engine, running encryption and decryption process in software causes high CPU. The SCP and SSH processes can show as much as 40 or 50 percent CPU usage, but they do not cause the device to shutdown.
-
-
Smart Licensing Using Policy: Starting with Cisco IOS XE Amsterdam 17.3.2a, with the introduction of Smart Licensing Using Policy, even if you configure a hostname for a product instance or device, only the Unique Device Identifier (UDI) is displayed. This change in the display can be observed in all licensing utilities and user interfaces where the hostname was displayed in earlier releases. It does not affect any licensing functionality. There is no workaround for this limitation.
The licensing utilities and user interfaces that are affected by this limitation include only the following: Cisco Smart Software Manager (CSSM), Cisco Smart License Utility (CSLU), and Smart Software Manager On-Prem (SSM On-Prem).
-
TACACS legacy command: Do not configure the legacy tacacs-server host command; this command is deprecated. If the software version running on your device is Cisco IOS XE Gibraltar 16.12.2 or a later release, using the legacy command can cause authentication failures. Use the tacacs server command in global configuration mode.
-
Uplink Symmetry—When a redundant supervisor module is inserted, we recommend that you have symmetric uplinks, to minimize packet loss during a switchover.
Uplinks are said to be in symmetry when the same interface on both supervisor modules have the same type of transceiver module. For example, a TenGigabitEthernet interface with no transceiver installed operates at a default 10G mode; if the matching interface of the other supervisor has a 10G transceiver, then they are in symmetry. Symmetry provides the best SWO packet loss and user experience.
Asymmetric uplinks have at least one or more pairs of interfaces in one supervisor not matching the transceiver speed of the other supervisor.
-
USB Authentication—When you connect a Cisco USB drive to the switch, the switch tries to authenticate the drive against an existing encrypted preshared key. Since the USB drive does not send a key for authentication, the following message is displayed on the console when you enter password encryption aes command:
Device(config)# password encryption aes Master key change notification called without new or old key -
VLAN Restriction—It is advisable to have well-defined segregation while defining data and voice domain during switch configuration and to maintain a data VLAN different from voice VLAN across the switch stack. If the same VLAN is configured for data and voice domains on an interface, the resulting high CPU utilization might affect the device.
-
HTTP Services Restriction—If you configure ip http active-session-modules none and ip http secure-active-session-modules none commands, NGINX process will be held down. This will prevent HTTP or HTTPS from running. Use the ip http session-module-list command to enable the required HTTP modules.
-
YANG data modeling limitation—A maximum of 20 simultaneous NETCONF sessions are supported.
-
Embedded Event Manager—Identity event detector is not supported on Embedded Event Manager.
-
The File System Check (fsck) utility is not supported in install mode.
Caveats
Caveats describe unexpected behavior in Cisco IOS-XE releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Cisco Bug Search Tool
The Cisco 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.
To view the details of a caveat, click on the identifier.
Open Caveats in Cisco IOS XE Amsterdam 17.3.x
There are no open caveats in this release.
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.8a
|
Identifier |
Description |
|---|---|
|
Cisco IOS XE Software Web UI Privilege Escalation Vulnerability. For more information, see Security Advisory: cisco-sa-iosxe-webui-privesc-j22SaA4z |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.8
There are no resolved caveats in this release.
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.7
|
Identifier |
Description |
|---|---|
|
Standby SUP intermittently not coming up when Grant or Dimple is in chassis |
|
|
Multicast traffic may stop after ISSU or stby reload followed by switchover if stby AppGigE enabled |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.6
|
Identifier |
Description |
|---|---|
|
Switch crash while removing private vlan mapping from port-channel interface. |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.5
|
Identifier |
Description |
|---|---|
|
SVL Hung - CPU HOG by Process - "Crimson Flush Transaction" |
|
|
9400 SVL damages the startup config on bootup when CSSM unreachable |
|
|
Memory leakage is getting incremented whenever dnac-ca crl fails |
|
|
%CRIMSON-3-DATABASE_MEMLEAK: Database memory leak detected in /tmp/rp/tdldb/0/IOS_PRIV_OPER_DB |
|
|
Cat9400 SVL: Static inline power config for the 2nd switch got lost on staggered booting |
|
|
Cat9400 SVL: MCL error is seen on SSO s/o if the 2nd sup is provisioned AND is a different type |
|
|
SNMP: sub-interface octet counter reports wrong value |
|
|
IOS-XE Kernel Memory Leak due to growing Slab Utilization |
|
|
Cat9400: configuration disabling OBFL on standby supervisor lost upon reload |
|
|
Incorrect L3 LISP instance ID on Cef table for VN's |
|
|
Cat9k | DHCP unicast ACK not forwarded to the client when DHCP snooping is enabled |
|
|
CAT 9400 | 17.3.x | LiteON PSU in standby slot goes to faulty state after some time |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.4
|
Identifier |
Description |
|---|---|
|
Wrong values for transceivers (DOM) in Cat9k Core switches |
|
|
SVL // DHCP discover relayed in a different vlan |
|
|
Manually configured MAC address is programmed in hardware when interface is admin down |
|
|
Netconf & Netconf-yang are not enabled on the Ext-Nodes as part of PnP config. |
|
|
Yang requests from DNAC to IoT devices related to device Licensing are failing on the device |
|
|
Vlan randomly stop forwarding DHCP pkts - Wedged input interface queue |
|
|
STACK : Stale mac entry in the member switch causing the connectivity issues. |
|
|
Disruption of IP communication due to AUTH_DRIVEN_DROP on uplinks when flapping downlink ports |
|
|
Profinet (PN-PTCP) frames overwhelming L2 Control CoPP queue on Cat9K |
|
|
ETA+AVC: After active timer expiry, multiple FNF exports sent for same flow |
|
|
Private Native Vlan packets are erroneously tagged |
|
|
Cat9400: iomd helddown after switchover then inserting LC or ISSU Upgrade |
|
|
Traffic failed if incoming interface MPLS and 2+ outgoing interfaces (ECMP) with recursive routing |
|
|
DHCP snooping and PVLAN dropping DHCP Offer unicast packet on C9K |
|
|
Cat9XXX may experience an unexpected reboot with Critical process fed fault on fp_0_0 |
|
|
Radius protocol generate jumbo frames for dot1x packets |
|
|
Switch forwards traffic received on ports in blocking BLK state |
|
|
Catalyst 9K Switch may crash on ISSU upgrade if run debug issu all |
|
|
C9400 switch may reload with Last reload reason: RP-CPU |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.3
|
Identifier |
Description |
|---|---|
|
SVL Crash when performing SUP failover on a scaled setup |
|
|
Ports remains in notconnect state when moved from L2 to L3 to L2 |
|
|
Configuring reserved PO 127 & 128 in SVL setup disables show etherchannel CLI |
|
|
User can config up to 255 vrf instead of 256 vrfs |
|
|
Catalyst 9k: FED crash after reaching webauth scale of about 1k sessions |
|
|
Loopback error is not detected on trunk interface |
|
|
Unexpected reload caused by the FED process. |
|
|
'SL using Policy' to SL downgrade to 16.12.4 leads to \"Initial Registration-First Attempt Pending\" |
|
|
C9400 SVL linecard of standby in inserted(physical) status after boot up w/ single power module only |
|
|
Dot1x Client mac in dropped state post switchover |
|
|
Cat9400: Line protocol flap observed in specific interface frequently on C9400-LC-24S/48S |
|
|
[SDA] SISF marking mac as tentative |
|
|
Switch Crashes when enabling RSPAN Destination port |
|
|
GLC-GE-100FX Version 02 is not working with C9400-LC-48S (ACCELINK) |
|
|
Cat9k switches may roll back to old software after unexpected switchover event |
|
|
VRF leaking using self-GRE tunnels causes traffic to be punted to CPU. |
|
|
EVPN Type-2 IP/MAC route is created for not-connected SVI |
|
|
Switch might enter a bootloop with SWITCH_DISABLE_PASSWORD_RECOVERY & IGNORE_STARTUP_CFG set to 1 |
|
|
OIR of Active SUP resulted all LC in hw-faulty status |
|
|
CAT 9400 | LiteON PSU in standby slot goes to faulty state after some time |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.2a
|
Identifier |
Description |
|---|---|
|
Whenever Acct-terminate-cause is 24 the duplicate set of traffic counts is sent as 0. |
|
|
Cat9K - incorrect source mac address used for L3 packets after L3 link flap |
|
|
Power allocation issue in 16.9.x/16.12.x |
|
|
Cat9k reboot due to ACL count being huge. |
|
|
Unexpected Reload when a VLAN is created within the range 2-1002 |
|
|
Interface Not Passing Traffic after Boot-up with IE 3400 with forced speed/duplex setting on IE |
|
|
DHCPv6 RELAY-REPLY dropped when punted on cat9k |
|
|
sessmgrd memory leak when CTS PAC download fails |
|
|
CLI should be auto-upgraded from "tacacs-server" cli to newer version while upgrading |
|
|
Random L3 ports stop traffic processing on SDA internal border nodes |
|
|
Cat9k Active stack switch crash while applying the CTS configuration |
|
|
snmp monitoring tool timesout for ciscoEntitySensorMIB 1.3.6.1.4.1.9.9.91.1.1.1.1 |
|
|
CAT9K: PRD18: SISF Crash seen on device when left traffic running overnight |
|
|
On Auth port, timestamp update is not happening for Authz MAC address upon RX of control-plane/BPDU |
|
|
IPv6 communication stops working post applying ipv6 source-guard on interface |
|
|
L3 ECMP load balancing not working as expected for fragmented packets. |
|
|
IPV4 and IPV6 Per-User ACL is not working together on singe authentication session |
|
|
inconsistent behaviour for autoconf template binding after switchover |
|
|
Route not fully programmed in the hardware for macsec enabled end-point |
|
|
random ports remain in down, down state after randomly bouncing and changing VLAN |
|
|
Dot1Q Native vlan tag is ignored after configuring Layer2 Vlan on 16.12.4 code |
|
|
Cat9k in VXLAN with directed-broadcast on egress interface duplicates broadcast traffic |
|
|
CAT9K reload due to "Critical process cmand fault on rp_0_0 (rc=139)" |
Resolved Caveats in Cisco IOS XE Amsterdam 17.3.1
|
Identifier |
Description |
|---|---|
|
EPC with packet-len opt breaks CPU in-band path for bigger frames |
|
|
SVL node may get removed if one of the SVL links goes bad. |
|
|
Cat9k PoE models - when configuring speed 100 and duplex full on both sides, interface will not come up |
|
|
DHCPv6 RELAY-REPLY packet is being dropped |
|
|
cmcc crash following oir events |
|
|
PnP over 40gig uplink doesn't work with dual SUP |
|
|
C9400: ISSU fails in stage 4 and new active SUP reloads |
|
|
DHCP server sends out a NAK packet during DHCP renewal process. |
|
|
Unable to use VLAN range 4084-4095 for any business operations |
|
|
C9400: System reload with last reload reason in Rommon as Unrecoverable Error |
|
|
Nvram Failed to initializae ( startup missing ) |
|
|
QoS ACL matching incorrectly when udp range is used |
|
|
C9400: %PMAN-0-PROCFAILCRIT: R0/0: pvp: A critical process cmand has failed |
|
|
Cat9400 - Some 3rd-Party phones do not bring up the interface with 'no mdix auto' configured. |
|
|
interface with 100FX SFP stuck in up-state |
|
|
LACP link suspend or PAgP link getting into error-disabled if stack-mac persistent timer is set |
|
|
ISSU upgrade: ISSU fails after stage 2, Standby SUP goes into ROMMON |
|
|
MACSEC issue in SDA deployment |
Troubleshooting
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website at this URL:
https://www.cisco.com/en/US/support/index.html
Go to Product Support and select your product from the list or enter the name of your product. Look under Troubleshoot and Alerts, to find information for the problem that you are experiencing.
Related Documentation
Information about Cisco IOS XE at this URL: https://www.cisco.com/c/en/us/products/ios-nx-os-software/ios-xe/index.html
All support documentation for Cisco Catalyst 9400 Series Switches is at this URL: https://www.cisco.com/c/en/us/support/switches/catalyst-9400-series-switches/tsd-products-support-series-home.html
Cisco Validated Designs documents at this URL: https://www.cisco.com/go/designzone
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: https://cfnng.cisco.com/mibs
Communications, Services, and Additional Information
-
To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
-
To get the business results you’re looking for with the technologies that matter, visit Cisco Services.
-
To submit a service request, visit Cisco Support.
-
To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco DevNet.
-
To obtain general networking, training, and certification titles, visit Cisco Press.
-
To find warranty information for a specific product or product family, access Cisco Warranty Finder.
Cisco Bug Search Tool
Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.
Feedback