Release Notes for Cisco Catalyst 9600 Series Switches, Cisco IOS XE Amsterdam 17.3.x

Introduction

Cisco Catalyst 9600 Series Switches are the next generation purpose-built 40 GigabitEthernet and 100 GigabitEthernet modular core and aggregation platform providing resiliency at scale with the industry’s most comprehensive security while allowing your business to grow at the lowest total operational cost. They have been purpose-built to address emerging trends of Security, IoT, Mobility, and Cloud.

They deliver complete convergence in terms of ASIC architecture with Unified Access Data Plane (UADP) 3.0. The platform runs an Open Cisco IOS XE that supports model driven programmability, Serial Advanced Technology Attachment (SATA) Solid State Drive (SSD) local storage, and a higher memory footprint). The series forms the foundational building block for SD-Access, which is Cisco’s lead enterprise architecture.

It also supports features that provide high availability, advanced routing and infrastructure services, security capabilities, and application visibility and control.

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

Customizable Switching Database Manager (SDM) Templates

Allows you to configure a customizable SDM template. In the customized template, you can assign resources to different features based on your requirement.

See System Management → Configuring SDM Templates.

(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 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 Advantage)

IPv6 Multicast Virtual Private Network (MVPNv6)

Enables service providers to use their existing IPv4 backbone to provide multicast-enabled private IPv6 networks to their customers.

See IP Multicast Routing → Configuring MVPNv6.

(Network Advantage)

Link Aggregation Control Protocol (LACP) 1:1 Redundancy and Dampening

Introduces support for:

  • LACP 1:1 Redundancy: Supports an EtherChannel configuration with one active link and fast switchover to a hot standby link.

  • LACP 1:1 Hot Standby Dampening: Configures a timer that delays switchover back to the higher priority port after it becomes active.

See Layer 2 → Configuring EtherChannels.

(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 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 Advantage)

Programmability

  • gNMI Configuration Persistence

  • gNOI Certificate Management

  • gNOI Bootstrapping with Certificate Service

  • YANG Data Models

The following programmability features are introduced in this release:

  • gNMI (gRPC Network Management Interface) Configuration Persistence: Ensures that all successful changes made through the gNMI SET RPC persist after a device restart.

  • gNOI Certificate Management: The gRPC Network Operations Interface (gNOI) Certificate Management service provides RPCs to install, rotate, get certificate, revoke certificate, and generate certificate signing request (CSR).

  • gNOI Bootstrapping with Certificate Service: After installing gNOI certificates, bootstrapping is used to configure or operate a target. gNMI bootstrapping is enabled by using the gnxi-secure-int command and disabled by using the secure-allow-self-signed-trustpoint command.

  • YANG Data Models: For the list of Cisco IOS XE YANG models available with this release, navigate to: https://github.com/YangModels/yang/tree/master/vendor/cisco/xe/1731.

    Revision statements embedded in the YANG files indicate if there has been a model revision. The README.md file in the same GitHub location highlights changes that have been made in the release.

    (Network Essentials and 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:

  • packet-length : Specifies packet length filter for packet capture

  • access-list : Specifies access-list filter for packet capture

show bootflash:

The command was modified. The following keywords were introduced:

  • namesort : Sorts the output based on file name

  • sizesort : Sorts the output based on file size

  • timesort : Sorts the output based on the timestamp of the file

See .

show platform hardware fed active fwd-asic counters tla

  • The command output was enhanced to display the TLA counters information.

  • The change keyword was deprecated.

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 mpls ldp discovery : Displays the status of the LDP discovery process

  • show mpls ldp neighbor : Displays the status of LDP sessions.

  • show mpls ldp bindings : Displays the contents of the Label Information Base (LIB).

show tech-support

The command was modified. The following keywords were introduced:

  • show tech-support confidential : The confidential keyword was introduced, to mask sensitive information in the output of show tech-support command.

  • show tech-support monitor : The monitor keyword was introduced. It displays Switched Port Analyzer (SPAN) monitor-related information.

  • show tech-support pvlan : The pvlan keyword was introduced. It displays Private VLAN-related information.

Important Notes

Unsupported Features

  • Cisco Application Visibility and Control (AVC)

  • Network-Based Application Recognition (NBAR) and Next Generation NBAR (NBAR2)

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.

Accessing Hidden Commands

This section provides information about hidden commands in Cisco IOS XE and the security measures that are in place, when they are accessed. These commands are only meant to assist Cisco TAC in advanced troubleshooting and are not documented.

Hidden commands are available under:

  • Category 1—Hidden commands in privileged or User EXEC mode. Begin by entering the service internal command to access these commands.

  • Category 2—Hidden commands in one of the configuration modes (global, interface and so on). These commands do not require the service internal command.

Further, the following applies to hidden commands under Category 1 and 2:

  • The commands have CLI help. Enter enter a question mark (?) at the system prompt to display the list of available commands.

    Note: For Category 1, enter the service internal command before you enter the question mark; you do not have to do this for Category 2.

  • The system generates a %PARSER-5-HIDDEN syslog message when a hidden command is used. For example:
    *Feb 14 10:44:37.917: %PARSER-5-HIDDEN: Warning!!! 'show processes memory old-header ' is a hidden command. 
    Use of this command is not recommended/supported and will be removed in future.
    
    

Apart from category 1 and 2, there remain internal commands displayed on the CLI, for which the system does NOT generate the %PARSER-5-HIDDEN syslog message.


Important

We recommend that you use any hidden command only under TAC supervision.

If you find that you are using a hidden command, open a TAC case for help with finding another way of collecting the same information as the hidden command (for a hidden EXEC mode command), or to configure the same functionality (for a hidden configuration mode command) using non-hidden commands.


Supported Hardware

Cisco Catalyst 9600 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

C9606R

Cisco Catalyst 9606R Switch

  • Redundant supervisor module capability

  • Four linecard slots

  • Hot-swappable fan tray, front and rear serviceable, fan tray assembly with 9 fans.

  • Four power supply module slots

Supported Hardware on Cisco Catalyst 9600 Series Switches

Product ID

(append with “=” for spares)

Description

Supervisor Modules

C9600-SUP-1

Cisco Catalyst 9600 Series Supervisor 1 Module

This supervisor module is supported on the C9606R chassis

SATA1 SSD2 Modules (for the Supervisor)

C9K-F2-SSD-240GB

Cisco Catalyst 9600 Series 240GB SSD Storage

C9K-F2-SSD-480GB

Cisco Catalyst 9600 Series 480GB SSD Storage

C9K-F2-SSD-960GB

Cisco Catalyst 9600 Series 960GB SSD Storage

40 or 100 GigabitEthernet Line Cards

C9600-LC-24C

Cisco Catalyst 9600 Series 24-Port 40GE/12-Port 100GE Line Card.

It supports:

  • 12 ports of 100 GigabitEthernet (GE) or 24 ports of 40GE

  • QSFP on all ports and QSFP28 on the 100 GE ports

25 GigabitEthernet Line Cards

C9600-LC-48YL

Cisco Catalyst 9600 Series 48-Port 25GE/10GE/1GE line card.

It supports:

  • 48 ports of 25 GE, 10GE or 1GE

  • SFP28, SFP+ transceivers on all ports

10 GigabitEthernet Line Cards

C9600-LC-48TX

Cisco Catalyst 9600 Series 48-port of 10GE/5GE/2.5GE/1GE/100Mbps/10 Mbps line card.

  • Provides 48 10 G, 5 G, 2.5 G, 1 G, 100 Mbps and 10Mbps interfaces by default. These ports can be interchangeably used as 10 G, 5 G, 2.5 G, 1 G, 100 Mbps and 10 Mbps ports.

  • All the 48 ports support 10 G, 5 G, 2.5 G, 1 G, 100 Mbps and 10 Mbps speeds.

1 GigabitEthernet Line Cards

C9600-LC-48S

Cisco Catalyst 9600 Series 48-Port 1GE line card.

It supports:

  • 48 ports of 1GE.

  • SFP transceivers on all ports

AC Power Supply Modules

C9600-PWR-2KWAC

Cisco Catalyst 9600 Series 2000W AC Power Supply Module3

DC Power Supply Modules

C9600-PWR-2KWDC

Cisco Catalyst 9600 Series 2000W DC Power Supply Module

1 Serial Advanced Technology Attachment (SATA)
2 Solid State Drive (SSD) Module
3 Power supply output capacity is 1050W at 110 VAC.

Compatibility Matrix

The following table provides software compatibility information.

Catalyst 9600

Cisco Identity Services Engine

Cisco Access Control Server

Cisco Prime Infrastructure

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

-

-

Gibraltar 16.12.4

2.6

-

-

Gibraltar 16.12.3a

2.6

-

-

Gibraltar 16.12.3

2.6

-

-

Gibraltar 16.12.2

2.6

-

-

Gibraltar 16.12.1

2.6

-

-

Gibraltar 16.11.1

2.6

2.4 Patch 5

5.4

5.5

-

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 minimum4

512 MB5

256

1280 x 800 or higher

Small

4 We recommend 1 GHz
5 We recommend 1 GB DRAM

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)

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.1

CAT9K_IOSXE

cat9k_iosxe.17.03.01.SPA.bin

No Payload Encryption (NPE)

cat9k_iosxe_npe.17.03.01.SPA.bin

ROMMON Upgrades

The ROM monitor (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. To know the ROMMON or bootloader version that applies to every major and maintenance release, refer to the table below.

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

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.

Release

ROMMON or Boot Loader Version

For Cisco IOS XE Amsterdam 17.3.1

The ROMMON version is 17.3.1r[FC2].
ROM: IOS-XE ROMMON
BOOTLDR: System Bootstrap, Version 17.3.1r[FC2], RELEASE SOFTWARE (P)
<output truncated>

When the boot loader upgrade occurs, while booting, you will see the following on the console:

*Jul 16 20:06:09.800: %IOSXEBOOT-4-BOOTLOADER_UPGRADE: (rp/0): ### Thu Jul 16 20:06:09 Universal 2020 PLEASE DO NOT POWER CYCLE ### BOOT LOADER UPGRADING
*Jul 16 20:06:46.922: %IOSXEBOOT-4-BOOTLOADER_UPGRADE: (rp/0): Thu Jul 16 20:06:46 Universal 2020 boot loader upgrade successful 
*Jul 16 20:06:46.929: %IOSXEBOOT-4-BOOTLOADER_UPGRADE: (rp/0): Thu Jul 16 20:06:46 Universal 2020 Supervisor will not be reloaded. 
New BOOTLOADER will activate with next reload or switchover

Software Installation Commands

Summary of Software Installation Commands

To install and activate the specified file, and to commit changes to be persistent across reloads:

install add file filename [ activate commit]

To separately install, activate, commit, cancel, or remove the installation file: install ?

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.

In-Service Software Upgrade

Cisco IOS XE Amsterdam 17.3.1 is the first extended maintenance release in the Cisco IOS XE 17.x.x release train. In-Service Software Upgrade (ISSU) from the extended maintenance release of one major release train, to another, is not supported (any 16.x.x to any 17.x.x is not supported).

For upgrades, see Upgrading in Install Mode, in this document.

For more information about ISSU, see the following Technical Reference document: In-Service Software Upgrade (ISSU).

Upgrading in Install Mode

Follow these instructions to upgrade from one release to another, using install commands, in install mode. To perform a software image upgrade, you must be booted into IOS through boot flash:packages.conf .

Before you begin


Caution

You must comply with these cautionary guidelines during an upgrade:

  • Do not power cycle the switch.

  • Do not disconnect power or remove the supervisor module.

  • Do not perform an online insertion and replacement (OIR) of either supervisor (in a High Availability setup), if one of the supervisor modules in the chassis is in the process of a bootloader upgrade or when the switch is booting up.

  • Do not perform an OIR of a switching module (linecard) when the switch is booting up.


Note that you can use this procedure for the following upgrade scenarios:

When upgrading from ...

To...

Cisco IOS XE Amsterdam 17.2.x or earlier releases

Cisco IOS XE Amsterdam 17.3.x

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:
Switch# install remove inactive
install_remove: START Fri Jul 17 19:51:48 UTC 2020
Cleaning up unnecessary package files
Scanning boot directory for packages ... done.
Preparing packages list to delete ...
    cat9k-cc_srdriver.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-espbase.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-guestshell.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-rpbase.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-rpboot.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-sipbase.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-sipspa.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-srdriver.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-webui.17.02.01.SPA.pkg
      File is in use, will not delete.
    cat9k-wlc.17.02.01.SPA.pkg
      File is in use, will not delete.
    packages.conf
      File is in use, will not delete.
  done.
 
The following files will be deleted:
[switch 1]:
/flash/cat9k-cc_srdriver.17.01.01.SPA.pkg
/flash/cat9k-espbase.17.01.01.SPA.pkg
/flash/cat9k-guestshell.17.01.01.SPA.pkg
/flash/cat9k-rpbase.17.01.01.SPA.pkg
/flash/cat9k-rpboot.17.01.01.SPA.pkg
/flash/cat9k-sipbase.17.01.01.SPA.pkg
/flash/cat9k-sipspa.17.01.01.SPA.pkg
/flash/cat9k-srdriver.17.01.01.SPA.pkg
/flash/cat9k-webui.17.01.01.SPA.pkg
/flash/cat9k-wlc.17.01.01.SPA.pkg
/flash/packages.conf
 
Do you want to remove the above files? [y/n]y

[switch 1]:
Deleting file flash:cat9k-cc_srdriver.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-espbase.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-guestshell.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-rpbase.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-rpboot.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-sipbase.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-sipspa.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-srdriver.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-webui.17.01.01.SPA.pkg ... done.
Deleting file flash:cat9k-wlc.17.01.01.SPA.pkg ... done.
Deleting file flash:packages.conf ... done.
SUCCESS: Files deleted.
--- Starting Post_Remove_Cleanup ---
Performing Post_Remove_Cleanup on all members
[1] Post_Remove_Cleanup package(s) on switch 1
[1] Finished Post_Remove_Cleanup on switch 1
Checking status of Post_Remove_Cleanup on [1]
Post_Remove_Cleanup: Passed on [1]
Finished Post_Remove_Cleanup
 
SUCCESS: install_remove Fri Jul 17 19:52:25 UTC 2020
Switch#
Step 2

Copy new image to flash

  1. copy tftp:[[//location]/directory]/filenameflash:

    Use this command to copy the new image from a TFTP server to flash memory. The location is either an IP address or a host name. The filename is specified relative to the directory used for file transfers. Skip this step if you want to use the new image from a TFTP server.
    Switch# copy tftp://10.8.0.6/image/cat9k_iosxe.17.03.01.SPA.bin flash:
    destination filename [cat9k_iosxe.17.03.01.SPA.bin]?
    Accessing tftp://10.8.0.6/image/cat9k_iosxe.17.03.01.SPA.bin...
    Loading /cat9k_iosxe.17.03.01.SPA.bin from 10.8.0.6 (via GigabitEthernet0/0): 
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    [OK - 601216545 bytes]
     
    601216545 bytes copied in 50.649 secs (11870255 bytes/sec)
    
     
  2. dir flash:*.bin

    Use this command to confirm that the image has been successfully copied to flash.
    Switch# dir flash:*.bin
    Directory of flash:/*.bin
     
    Directory of flash:/
     
    434184 -rw- 601216545    Jul 17 2020 10:18:11 -07:00 cat9k_iosxe.17.03.01.SPA.bin
    11353194496 bytes total (8976625664 bytes free)
    
    
Step 3

Set boot variable

  1. boot system flash:packages.conf

    Use this command to set the boot variable to flash:packages.conf .
    Switch(config)# boot system flash:packages.conf
    
  2. no boot manual

    Use this command to configure the switch to auto-boot. Settings are synchronized with the standby switch, if applicable.
    Switch(config)# no boot manual
    Switch(config)# exit
  3. write memory

    Use this command to save boot settings.
    Switch# write memory
  4. show bootvar

    Use this command to verify the boot variable (packages.conf) and manual boot setting (no):
    Switch# show bootvar
    BOOT variable = bootflash:packages.conf
    MANUAL_BOOT variable = no
    BAUD variable = 9600
    ENABLE_BREAK variable = yes
    BOOTMODE variable does not exist
    IPXE_TIMEOUT variable does not exist
    CONFIG_FILE variable = 
    
    Standby BOOT variable = bootflash:packages.conf
    Standby MANUAL_BOOT variable = no
    Standby BAUD variable = 9600
    Standby ENABLE_BREAK variable = yes
    Standby BOOTMODE variable does not exist
    Standby IPXE_TIMEOUT variable does not exist
    Standby CONFIG_FILE variable = 
Step 4

Install image to flash

install add file activate commit

Use this command to install the image.

We recommend that you point to the source image on a TFTP server or the flash , if you have copied the image to flash memory.

The following sample output displays installation of the Cisco IOS XE Amsterdam 17.3.1 software image to flash:
Switch# install add file flash:cat9k_iosxe.17.03.01.SPA.bin activate commit
_install_add_activate_commit: START Fri Jul 17 16:37:25 IST 2020

*Jul 17 16:37:26.544 IST: %INSTALL-5-INSTALL_START_INFO: R0/0: install_engine: Started install one-shot flash:cat9k_iosxe.17.02.01.SPA.bin 
install_add_activate_commit: Adding PACKAGE
install_add_activate_commit: Checking whether new add is allowed ....

This operation requires a reload of the system. Do you want to proceed? 
Please confirm you have changed boot config to flash:packages.conf [y/n]y

--- Starting initial file syncing ---
Copying image file: flash:cat9k_iosxe.17.03.01.SPA.bin to standby
Info: Finished copying flash:cat9k_iosxe.17.03.01.SPA.bin to standby
Finished initial file syncing

--- Starting Add ---
Performing Add on Active/Standby
  [R0] Add package(s) on R0
  [R0] Finished Add on R0
  [R1] Add package(s) on R1
  [R1] Finished Add on R1
Checking status of Add on [R0 R1]
Add: Passed on [R0 R1]
Finished Add

Image added. Version: 17.3.01

install_add_activate_commit: Activating PACKAGE
Following packages shall be activated:
/flash/cat9k-wlc.17.03.01.SPA.pkg
/flash/cat9k-webui.17.03.01.SPA.pkg
/flash/cat9k-srdriver.17.03.01.SPA.pkg
/flash/cat9k-sipspa.17.03.01.SPA.pkg
/flash/cat9k-sipbase.17.03.01.SPA.pkg
/flash/cat9k-rpboot.17.03.01.SPA.pkg
/flash/cat9k-rpbase.17.03.01.SPA.pkg
/flash/cat9k-guestshell.17.03.01.SPA.pkg
/flash/cat9k-espbase.17.03.01.SPA.pkg
/flash/cat9k-cc_srdriver.17.03.01.SPA.pkg

This operation may require a reload of the system. Do you want to proceed? [y/n]y

--- Starting Activate ---
Performing Activate on Active/Standby
*Jul 17 16:45:21.695 IST: %INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS: R0/0: rollback_timer: Install auto abort timer will expire in 7200 seconds  [R0] Activate package(s) on R0
  [R0] Finished Activate on R0
  [R1] Activate package(s) on R1
  [R1] Finished Activate on R1
Checking status of Activate on [R0 R1]
Activate: Passed on [R0 R1]
Finished Activate

*Jul 17 16:45:25.233 IST: %INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS: R1/0: rollback_timer: Install auto abort timer will expire in 7200 seconds--- Starting Commit ---
Performing Commit on Active/Standby
  [R0] Commit package(s) on R0
  [R0] Finished Commit on R0
  [R1] Commit package(s) on R1
  [R1] Finished Commit on R1
Checking status of Commit on [R0 R1]
Commit: Passed on [R0 R1]
Finished Commit

Install will reload the system now!
SUCCESS: install_add_activate_commit  Fri Jul 17 16:46:18 IST 2020
Note 
The system reloads automatically after executing the install add file activate commit command . You do not have to manually reload the system.
Step 5

Verify installation

After the software has been successfully installed, use the dir flash: command to verify that the flash partition has ten new .pkg files and two .conf files.

  1. dir flash:*.conf

    The following is sample output of the dir flash:*.pkg command:
    Switch# dir flash:*.pkg
    Directory of flash:/*.pkg
    Directory of flash:/
    475140 -rw- 2012104    Mar 31 2020 09:52:41 -07:00 cat9k-cc_srdriver.17.02.01.SPA.pkg
    475141 -rw- 70333380   Mar 31 2020 09:52:44 -07:00 cat9k-espbase.17.02.01.SPA.pkg
    475142 -rw- 13256      Mar 31 2020 09:52:44 -07:00 cat9k-guestshell.17.02.01.SPA.pkg
    475143 -rw- 349635524  Mar 31 2020 09:52:54 -07:00 cat9k-rpbase.17.02.01.SPA.pkg
    475149 -rw- 24248187   Mar 31 2020 09:53:02 -07:00 cat9k-rpboot.17.02.01.SPA.pkg
    475144 -rw- 25285572   Mar 31 2020 09:52:55 -07:00 cat9k-sipbase.17.02.01.SPA.pkg
    475145 -rw- 20947908   Mar 31 2020 09:52:55 -07:00 cat9k-sipspa.17.02.01.SPA.pkg
    475146 -rw- 2962372    Mar 31 2020 09:52:56 -07:00 cat9k-srdriver.17.02.01.SPA.pkg
    475147 -rw- 13284288   Mar 31 2020 09:52:56 -07:00 cat9k-webui.17.02.01.SPA.pkg
    475148 -rw- 13248      Mar 31 2020 09:52:56 -07:00 cat9k-wlc.17.02.01.SPA.pkg
    
    491524 -rw- 25711568   Jul 17 2020 11:49:33 -07:00  cat9k-cc_srdriver.17.03.01.SPA.pkg
    491525 -rw- 78484428   Jul 17 2020 11:49:35 -07:00  cat9k-espbase.17.03.01.SPA.pkg
    491526 -rw- 1598412    Jul 17 2020 11:49:35 -07:00  cat9k-guestshell.17.03.01.SPA.pkg
    491527 -rw- 404153288  Jul 17 2020 11:49:47 -07:00  cat9k-rpbase.17.03.01.SPA.pkg
    491533 -rw- 31657374   Jul 17 2020 11:50:09 -07:00  cat9k-rpboot.17.03.01.SPA.pkg
    491528 -rw- 27681740   Jul 17 2020 11:49:48 -07:00  cat9k-sipbase.17.03.01.SPA.pkg
    491529 -rw- 52224968   Jul 17 2020 11:49:49 -07:00  cat9k-sipspa.17.03.01.SPA.pkg
    491530 -rw- 31130572   Jul 17 2020 11:49:50 -07:00  cat9k-srdriver.17.03.01.SPA.pkg
    491531 -rw- 14783432   Jul 17 2020 11:49:51 -07:00  cat9k-webui.17.03.01.SPA.pkg
    491532 -rw- 9160       Jul 17 2020 11:49:51 -07:00  cat9k-wlc.17.03.01.SPA.pkg
    
    11353194496 bytes total (8963174400 bytes free)
    
    
  2. dir flash:*.conf

    The following is sample output of the dir flash:*.conf command. It displays the .conf files in the flash partition; note the two .conf files:

    • packages.conf—the file that has been re-written with the newly installed .pkg files.

    • cat9k_iosxe.17.03.01.SPA.conf— a backup copy of the newly installed packages.conf file.

    Switch# dir flash:*.conf
     
    Directory of flash:/*.conf
    Directory of flash:/
    
    16631  -rw- 4882 Jul 17 2020 05:39:42 +00:00  packages.conf
    16634  -rw- 4882 Jul 17 2020 05:34:06 +00:00  cat9k_iosxe.17.03.01.SPA.conf
    
    
Step 6

Upgrade the ROMMON version

upgrade rom-monitor capsule golden

A new ROMMON version is available for Cisco IOS XE Amsterdam 17.3.1. After you enter the command, confirm upgrade at the system prompt.

In case of a high availability set up or a Cisco StackWise Virtual set up, remember to upgrade the active and standby.


Switch# upgrade rom-monitor capsule golden R0 
This operation will reload the switch and take a few minutes to complete. Do you want to proceed (y/n)? [confirm]y
Switch#
Initializing Hardware...
<output truncated>

For more information about this, see ROMMON Upgrades in this document.

Step 7

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.3.1 image on the device:
Switch# show version
Cisco IOS XE Software, Version 17.03.01
Cisco IOS Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.3.1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2020 by Cisco Systems, Inc..
<output truncated>

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 through boot flash:packages.conf .

Before you begin

Note that you can use this procedure for the following downgrade scenarios:

When downgrading from ...

To ...

Cisco IOS XE Amsterdam 17.3.x

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.

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:
Switch# install remove inactive
 install_remove: START Fri Jul 17 11:42:27 IST 2020

Cleaning up unnecessary package files

No path specified, will use booted path bootflash:packages.conf

Cleaning bootflash:
  Scanning boot directory for packages ... done.
  Preparing packages list to delete ... 
    cat9k-cc_srdriver.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-espbase.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-guestshell.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-rpbase.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-rpboot.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-sipbase.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-sipspa.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-srdriver.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-webui.17.03.01.SSA.pkg
      File is in use, will not delete.
    cat9k-wlc.17.03.01.SSA.pkg
      File is in use, will not delete.
    packages.conf
      File is in use, will not delete.
  done.
SUCCESS: No extra package or provisioning files found on media. Nothing to clean.

SUCCESS: install_remove  Fri Jul 17 11:42:39 IST 2020

--- Starting Post_Remove_Cleanup ---
Performing Post_Remove_Cleanup on all members
[1] Post_Remove_Cleanup package(s) on switch 1
[1] Finished Post_Remove_Cleanup on switch 1
Checking status of Post_Remove_Cleanup on [1]
Post_Remove_Cleanup: Passed on [1]
Finished Post_Remove_Cleanup
 
SUCCESS: install_remove Fri Jul 17 19:52:25 UTC 2019
Switch#

Step 2

Copy new image to flash

  1. copy tftp:[[//location]/directory]/filenameflash:

    Use this command to copy the new image from a TFTP server to flash memory. The location is either an IP address or a host name. The filename is specified relative to the directory used for file transfers. Skip this step if you want to use the new image from a TFTP server.
    Switch# copy tftp://10.8.0.6/image/cat9k_iosxe.17.02.01.SPA.bin flash:
    Destination filename [cat9k_iosxe.17.02.01.SPA.bin]?
    Accessing tftp://10.8.0.6//cat9k_iosxe.17.02.01.SPA.bin...
    Loading /cat9k_iosxe.17.02.01.SPA.bin from 10.8.0.6 (via GigabitEthernet0/0): 
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    [OK - 508584771 bytes]
    508584771 bytes copied in 101.005 secs (5035244 bytes/sec)
     
    
  2. dir flash:

    Use this command to confirm that the image has been successfully copied to flash.
    Switch# dir flash:*.bin
    Directory of flash:/*.bin
     
    Directory of flash:/
     
    434184 -rw- 508584771 Jul 17 2020 13:35:16 -07:00 cat9k_iosxe.17.02.01.SPA.bin
    11353194496 bytes total (9055866880 bytes free)
    
    
Step 3

Set boot variable

  1. boot system flash:packages.conf

    Use this command to set the boot variable to flash:packages.conf .
    Switch(config)# boot system flash:packages.conf
    
  2. no boot manual

    Use this command to configure the switch to auto-boot. Settings are synchronized with the standby switch, if applicable.
    Switch(config)# no boot manual
    Switch(config)# exit
  3. write memory

    Use this command to save boot settings.
    Switch# write memory
  4. show bootvar

    Use this command to verify the boot variable (packages.conf) and manual boot setting (no):
    Switch# show bootvar
    BOOT variable = bootflash:packages.conf
    MANUAL_BOOT variable = no
    BAUD variable = 9600
    ENABLE_BREAK variable = yes
    BOOTMODE variable does not exist
    IPXE_TIMEOUT variable does not exist
    CONFIG_FILE variable = 
    
    Standby BOOT variable = bootflash:packages.conf
    Standby MANUAL_BOOT variable = no
    Standby BAUD variable = 9600
    Standby ENABLE_BREAK variable = yes
    Standby BOOTMODE variable does not exist
    Standby IPXE_TIMEOUT variable does not exist
    Standby CONFIG_FILE variable = 
Step 4

Downgrade software image

install add file activate commit

Use this command to install the image.

We recommend that you point to the source image on a TFTP server or the flash , if you have copied the image to flash memory.

The following example displays the installation of the Cisco IOS XE Amsterdam 17.2.1 software image to flash, by using the install add file activate commit command.
Switch# install add file flash:cat9k_iosxe.17.02.01.SPA.bin activate commit
_install_add_activate_commit: START Fri Jul 17 21:37:25 IST 2020

*Jul 17 16:37:26.544 IST: %INSTALL-5-INSTALL_START_INFO: R0/0: install_engine: Started install one-shot flash:cat9k_iosxe.17.02.01.SPA.bin 
install_add_activate_commit: Adding PACKAGE
install_add_activate_commit: Checking whether new add is allowed ....

This operation requires a reload of the system. Do you want to proceed? 
Please confirm you have changed boot config to flash:packages.conf [y/n]y

--- Starting initial file syncing ---
Copying image file: flash:cat9k_iosxe.17.02.01.SPA.bin to standby
Info: Finished copying flash:cat9k_iosxe.17.02.01.SPA.bin to standby
Finished initial file syncing

--- Starting Add ---
Performing Add on Active/Standby
  [R0] Add package(s) on R0
  [R0] Finished Add on R0
  [R1] Add package(s) on R1
  [R1] Finished Add on R1
Checking status of Add on [R0 R1]
Add: Passed on [R0 R1]
Finished Add

Image added. Version: 17.02.1
install_add_activate_commit: Activating PACKAGE
Following packages shall be activated:
/flash/cat9k-wlc.17.02.01.SPA.pkg
/flash/cat9k-webui.17.02.01.SPA.pkg
/flash/cat9k-srdriver.17.02.01.SPA.pkg
/flash/cat9k-sipspa.17.02.01.SPA.pkg
/flash/cat9k-sipbase.17.02.01.SPA.pkg
/flash/cat9k-rpboot.17.02.01.SPA.pkg
/flash/cat9k-rpbase.17.02.01.SPA.pkg
/flash/cat9k-guestshell.17.02.01.SPA.pkg
/flash/cat9k-espbase.17.02.01.SPA.pkg
/flash/cat9k-cc_srdriver.17.02.01.SPA.pkg

This operation may require a reload of the system. Do you want to proceed? [y/n]y

--- Starting Activate ---
Performing Activate on Active/Standby

*Jul 17 21:45:21.695 IST: %INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS: R0/0: rollback_timer: Install auto abort timer will expire in 7200 seconds  [R0] Activate package(s) on R0
  [R0] Finished Activate on R0
  [R1] Activate package(s) on R1
  [R1] Finished Activate on R1
Checking status of Activate on [R0 R1]
Activate: Passed on [R0 R1]
Finished Activate


*Jul 17 21:45:25.233 IST: %INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS: R1/0: rollback_timer: Install auto abort timer will expire in 7200 seconds--- Starting Commit ---
Performing Commit on Active/Standby
  [R0] Commit package(s) on R0
  [R0] Finished Commit on R0
  [R1] Commit package(s) on R1
  [R1] Finished Commit on R1
Checking status of Commit on [R0 R1]
Commit: Passed on [R0 R1]
Finished Commit

Install will reload the system now!
SUCCESS: install_add_activate_commit  Fri Jul 17 21:46:18 IST 2020
Note 
The system reloads automatically after executing the install add file activate commit command. You do not have to manually reload the system.
Step 5

Verify version

show version

After the image boots up, use this command to verify the version of the new image.

Note 
When you downgrade the software image, the ROMMON version does not downgrade. It remains updated.
The following sample output of the show version command displays the Cisco IOS XE Amsterdam 17.2.1 image on the device:
Switch# show version
Cisco IOS XE Software, Version 17.02.01
Cisco IOS Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.2.1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2019 by Cisco Systems, Inc.
<output truncated>

Field-Programmable Gate Array Version Upgrade

A field-programmable gate array (FPGA) is a type of programmable memory device that exists on Cisco switches. They are re-configurable logic circuits that enable the creation of specific and dedicated functions.

There is no FPGA upgrade in Cisco IOS XE Amsterdam 17.3.1.

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 9600 Series Switches fall under these base or add-on license levels.

Base Licenses

  • Network Advantage

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 Advantage

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.

License Types

The following license types are available:

  • 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.

License Levels - Usage Guidelines

  • Base licenses (Network-Advantage) are ordered and fulfilled only with a permanent license type.

  • Add-on licenses (DNA Advantage) are ordered and fulfilled only with a 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.

  • 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.

Smart Licensing

Cisco Smart Licensing is a unified license management system that manages all the software licenses across Cisco products.

It enables you to purchase, deploy, manage, track and renew Cisco Software. It provides information about license ownership and consumption through a single user interface.

The solution is composed of Smart Accounts and Cisco Smart Software Manager. The former is an online account of your Cisco software assets and is required to use the latter. Cisco Smart Software Manager is where you can perform all your licensing management related tasks, such as, registering, de-registering, moving, and transferring licenses. Users can be added and given access and permissions to the smart account and specific virtual accounts.


Important

Cisco Smart Licensing is the default and the only available method to manage licenses.

Deploying Smart Licensing

The following provides a process overview of a day 0 to day N deployment directly initiated from a device. Links to the configuration guide provide detailed information to help you complete each one of the smaller tasks.

Procedure

Step 1

Begin by establishing a connection from your network to Cisco Smart Software Manager on cisco.com.

In the software configuration guide of the required release, see System Management → Configuring Smart Licensing → Connecting to CSSM

Step 2

Create and activate your Smart Account, or login if you already have one.

To create and activate Smart Account, go to Cisco Software Central → Create Smart Accounts. Only authorized users can activate the Smart Account.

Step 3

Complete the Cisco Smart Software Manager set up.

  1. Accept the Smart Software Licensing Agreement.

  2. Set up the required number of Virtual Accounts, users and access rights for the virtual account users.

    Virtual accounts help you organize licenses by business unit, product type, IT group, and so on.

  3. Generate the registration token in the Cisco Smart Software Manager portal and register your device with the token.

    In the software configuration guide of the required release, see System Management → Configuring Smart Licensing → Registering the Device in CSSM


With this,

  • The device is now in an authorized state and ready to use.

  • The licenses that you have purchased are displayed in your Smart Account.

Using Smart Licensing on an Out-of-the-Box Device

If an out-of-the-box device has the software version factory-provisioned, all licenses on such a device remain in evaluation mode until registered in Cisco Smart Software Manager.

In the software configuration guide of the required release, see System Management → Configuring Smart Licensing → Registering the Device in CSSM

How Upgrading or Downgrading Software Affects Smart Licensing

Smart Licensing is the default and only license management solution; all licenses are managed as Smart Licenses.

Note how upgrading to a release that supports Smart Licensing or moving to a release that does not support Smart Licensing affects licenses on a device:

  • When you downgrade to a release where Smart Licensing is not supported—all smart licenses on the device are converted to traditional licenses and all smart licensing information on the device is removed.

Scaling Guidelines

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.

  • Convergence: During SSO, a higher convergence time is observed while removing the active supervisor module installed in slot 3 of a C9606R chassis.

  • Hardware Limitatons — Optics:

    • Copper cables are not supported with 25GE, 40GE, and 100GE configurations

    • Installation restriction for C9600-LC-24C linecard with CVR-QSFP-SFP10G adapater —This adapter must not be installed on an even numbered port where the corresponding odd numbered port is configured as 40GE port. For example, if port 1 is configured as 40GE, CVR-QSFP-SFP10G must not be installed in port 2.

      Installation restriction for C9600-LC-24C linecard with CVR-QSFP-SFP10G adapater — If you insert a 40-Gigabit Ethernet Transceiver Module to odd numbered port, the corresponding even numbered port does not work with CVR-QSFP-SFP10G adapter.

  • Hardware Limitatons — Power Supply Modules:

    • Input voltage for AC power supply modules—All AC-input power supply modules in the chassis must have the same AC-input voltage level.

    • Using power supply modules of different types—When mixing AC-input and DC-input power supplies, the AC-input voltage level must be 220 VAC.

  • In-Service Software Upgrade (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.

  • Memory leak—When a logging discriminator is configured and applied to a device, memory leak is seen under heavy syslog or debug output. The rate of the leak is dependent on the quantity of logs produced. In extreme cases, the device may fail. As a workaround, disable the logging discriminator on the device.

  • 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.

  • 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.

  • 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.

  • 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
  • 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.

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.1

Identifier

Description

CSCvr92287

EPC with packet-len opt breaks CPU in-band path for bigger frames

CSCvs14673

SVL node may get removed if one of the SVL links goes bad.

CSCvs15485

Cat9k PoE models - when configuring speed 100 and duplex full on both sides, interface will not come up

CSCvs22896

DHCPv6 RELAY-REPLY packet is being dropped

CSCvs39968

CAT 9500 & 9600 crashes on transceiver insertion

CSCvs84212

DHCP server sends out a NAK packet during DHCP renewal process.

CSCvs89792

INJECT_FEATURE_ESCAPE: Egress IP packet delivered via legacy inject path for NetBios packets

CSCvs97551

Unable to use VLAN range 4084-4095 for any business operations

CSCvt13518

QoS ACL matching incorrectly when udp range is used

CSCvt35095

Connection for L3 interfaces and SVIs may go down when power cycled SVL active switch comes online.

CSCvt59448

LACP link suspend or PAgP link getting into error-disabled if stack-mac persistent timer is set

CSCvt99199

MACSEC issue in SDA deployment

CSCvu87973

Catalyst 9600 cannot further fragment multicast fragments

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 16 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 9600 Series Switches is at this URL: https://www.cisco.com/c/en/us/support/switches/catalyst-9600-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: http://www.cisco.com/go/mibs

Communications, Services, and Additional Information

  • To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.

  • To get the business impact 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 Marketplace.

  • 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.