Different types of licenses are required for the Nexus 5500 and Nexus 5600.
Table 1-15 describes each license and the features it enables.
Table 1-15 Nexus 5500 Product Licensing
FabricPath Services Package
FCoE NPV Package
Layer 3 Base Services Package
Unlimited static routes and maximum of 256 dynamic routes:
Layer 3 Enterprise Services Package
N55-LAN1K9 includes the following features in addition to the ones under N55-BAS1K9 license:
Storage Protocols Services Package
Native Fibre Channel
NOTE: To manage the Nexus 5500 and Nexus 5600, two types of licenses are needed: the DCNM LAN and DCNM SAN. Each is a separate license.
Nexus switches have a grace period, which is the amount of time the features in a license package can continue functioning without a license.
Enabling a licensed feature that does not have a license key starts a counter on the grace period. You then have 120 days to install the appropriate license keys, disable the use of that feature, or disable the grace period feature.
If at the end of the 120-day grace period the device does not have a valid license key for the feature, the Cisco NX-OS software automatically disables the feature and removes the configuration from the device. There is also an evaluation license, which is a temporary license. Evaluation licenses are time bound (valid for a specified number of days) and are tied to a host ID (device serial number).
Is Your Network Ready for the New Era? Cisco announced its new Catalyst series switches-the Catalyst 9000 Series, introducing an entirely new era of networking. The Network. Intuitive.
There are three series in the new Catalyst 9000 switch family:
1. Catalyst 9300 Series (LAN Access Switches): the top fixed-access enterprise network switch series, stacking to 480 Gbps.
2. Catalyst 9400 Series (LAN Access Switches): the leading modular-access switches for enterprise, the Catalyst 9400 Series supports up to 9 Tbps.
3. Catalyst 9500 Series (LAN Core and Distribution Switches): the industry’s first fixed-core 40-Gbps switch for the enterprise.
In this article we will talk about the new Catalyst 9300 Series, the Next Level of the Market-Leading Fixed Access Switching Platform.
Will the Catalyst 9300 replace the Catalyst 3850 Series? Definitely, it is the best replacement for the Catalyst 3850 Series. Why? Let’s check the more detailed features of the Cisco Catalyst 9300 Series.
Switch models and configurations
The Cisco Catalyst 9300 Series is made up of seven different switch models. Any of the models can be used together in a stack of up to eight units.
The Table below lists port scale and power details for the Cisco Catalyst 9300 Series models.
Cisco Catalyst 9300 Series Switch configurations
Total 10/100/1000 or Multigigabit Copper Ports
Default AC Power Supply
Available PoE Power
24 Cisco UPOE
48 Cisco UPOE
24 Multigigabit Cisco UPOE (100 Mbps or 1, 2.5, 5, or 10 Gbps)
The Cisco Catalyst 9300 Series Switches support optional network modules for uplink ports. The default switch configuration does not include the network module. When you purchase the switch, you can choose from the network modules described in the following Table.
- Uplink modules supported on all 9300 Series copper models
- Online Insertion and Removal (OIR) supported on all uplink modules
Network module numbers and descriptions
9300 Series 4x 1G Network Module
9300 Series 8x 10G Network Module
9300 Series 2x 40G Network Module
9300 Series 4x Multigigabit Network Module
Please note: Existing 3850 network modules are also supported in the Catalyst 9300 Series platforms.
The Cisco Catalyst 9300 Series Switches support dual redundant power supplies. The switches ship with one power supply by default, and the second power supply can be purchased when the switch is ordered or at a later time. If only one power supply is installed, it should always be in power supply bay #1. The switches also ship with three field-replaceable fans.
Table3 lists the different power supplies available in these switches and available PoE power.
Table3. Power supply models
Default Power Supply
Available PoE Power
24-port data switch
48-port data switch
24-port PoE+ switch
48-port PoE+ switch
24-port Cisco UPOE switch
48-port Cisco UPOE switch
24-port Multigigabit Cisco UPOE switch
490W – Support in Open IOS-XE 16.6
Power supply requirements for PoE and PoE+
24-Port PoE Switch
48-Port PoE Switch
PoE on all ports (15.4W per port)
1 PWR-C1-1100WAC or 2 PWR-C1-715WAC
PoE+ on all ports (30W per port)
1 PWR-C1-1100WAC or 2 PWR-C1-715WAC
2 PWR-C1-1100WAC or 1 PWR-C1-1100WAC and 1 PWR-C1-715WAC
Power supply requirements for Cisco UPOE
24-Port UPOE Switch
48-Port UPOE Switch
24-Port Multigigabit UPOE Switch
Cisco UPOE (60W per port) on all ports (24-port switch) or up to 30 ports (48-port switch)
1 PWR-C1-1100WAC and 1 PWR-C1-715WAC
● Perpetual PoE: With Perpetual PoE, the PoE power is maintained during a switch reload. This is important for IoT endpoints such as PoE-powered lights, so that there is no disruption during switch reboot.
● Fast PoE: When power is restored to a switch, PoE starts delivering power to endpoints without waiting for the operating system to fully load, thereby speeding up the time for the endpoint to start up.
Cisco Catalyst 9300 Series Switches run on Open IOS XE 16.5.1a release or later. This software release includes all the features listed earlier in the Platform Benefits section.
- Up to 8 Switches can be stacked together using back stacking cables
- All 9300 models are supported in the stack
- All the switches in the stack should run the same IOS and License
- Mixed stacking between 9300 and 9300 is not supported
Cisco Catalyst 9300 Series StackPower
“Zero-Footprint” RPS Deployment
• Provides RPS functionality with Zero RPS Footprint
• Pay-as-you-grow architecture–similar to the Data Stack
• 1+N Redundancy with Inline Power
• Up to 4 Switches in a StackPower Ring
• Multiple StackPower Possible within one Data Stack
• Up to 9 Switches in a star topology with XPS
Mapping Between Cisco Catalyst 3850 and 9300
Catalyst 9300 24-port data only switch
Catalyst 9300 24-port PoE+ switch
Catalyst 9300 24-port UPOE switch
Catalyst 9300 24-port mGig and UPOE switch
Catalyst 9300 48-port data only switch
Catalyst 9300 48-port PoE+ switch
Catalyst 9300 48-port UPOE switch
Learn More: Why Migrate to Cisco Catalyst 9300 Switches?
There are 2 methods of booting and running IOS XE software in 3850 switch/stack.
By default, the switches are shipped in Install mode.
Bundle mode: Bundle mode is where we boot the switch/stack using the .bin file. This is the traditional method of booting the switch where the switch extracts the .bin file to the RAM of the switch and run from there.
Install Mode: Install mode is where we pre-extract the .bin file in the flash and boot the witch/stack using the packages.conf file created during the extraction.
Install mode is the recommended mode of running the switch. Not all features may be available in this Bundle mode
IOS XE installation and software rollback are supported only when the switch is running in “Install” mode. (i.e.: The commands “software install” and “software rollback”.)
Use “software expand” command to convert the switch into Install mode from Bundle mode. The steps are mentioned below.
Upgrading a stand-alone switch:
The packages and provisioning file used to boot in installed mode must reside in the flash.
Booting in installed mode from usbflash0: or TFTP is not supported.
Booting a bundle in bundle mode is just like booting a monolithic IOS image.
For example: boot flash:cat3k_caa-universalk9.SSA.03.08.83.EMD.150-8.83.EMD.bin
Hence, the boot variable should not be pointing to the .bin file. If so, the switch will boot in Bundle mode. The boot variable should be pointing to the “packages.conf” file in order for the switch to boot in Install mode.
Before doing the upgrade, we need to check the mode in which the switch is currently booted in.
C3850#show version | begin Switch Port
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 32 WS-C3850-24T 03.03.01SE cat3k_caa-universalk9 INSTALL •ß Install mode
Upgrading from Install mode:
By default, switches are shipped in Install mode.
In order to upgrade the switch from Install mode, please follow the below-mentioned procedure.
- •1. Download the new image from the TFTP server to the flash / USB on the switch. (optional)
Copy tftp: flash:
Copy tftp: usbflash0:
- •2. Use the command “software install” to install the newly downloaded image (or) the image present in the network.
C3850-01#software install file <source>:<filename.bin> new
The “new” keyword is used so that that the post-install package set should contain only the packages being installed. The old packages file will be renamed for future rollback purpose. Without this option, the post-install package set is a merged set of the currently installed software and the new packages being installed.
The source can be
- flash: or usbflash0: (or a sub-directory of these)
- The network via tftp, ftp or http
NOTE: When performing ‘software install’ on a switch with a source bundle that resides in the network, the source bundle is first downloaded to RAM on switch. The source bundle is deleted from RAM when the operation completes.
Refer to the configuration guide to know about the other optional parameters of this command,
Directory of flash:/
29511 -rwx 220716072 Oct 15 2012 12:57:59 +00:00 cat3k_caa-universalk9.SSA.03.08.88.EMP.150-8.88.EMP.bin
C3850#software install file flash:cat3k_caa-universalk9.SSA.03.08.88.EMP.150-8.88.EMP.bin
[1 ]: Creating pending provisioning file
[1 ]: Finished installing software. New software will load on reboot.
[1 ]: Committing provisioning file
[1 ]: Do you want to proceed with reload? [yes/no]: n
Once the installation is completed, reload the switch and it will boot into the newly installed IOS XE image.
From Bundle mode:
If the switch is currently running in “Bundle” mode, then we need to use the “software expand” command to convert the switch into the Install mode first and then install the new IOS XE.
The ‘software expand’ exec command is used to extract the package files and the provisioning file (packages.conf) from a source bundle (possibly the running bundle) and copy them to the specified destination directory in a local storage device.
This command will typically be used to convert from the bundle running mode to the installed running mode.
NOTE: When performing ‘software expand’ on a switch with a source bundle that resides in local storage, the source bundle is first copied to the corresponding local storage device on the switch. The source bundle used for the expand operation is left intact after it is expanded.
NOTE: When performing ‘software expand’ on a switch with a source bundle that resides in the network, the source bundle is first downloaded to RAM of the switch. The source bundle is deleted from RAM on the switch when the operation completes.
This example uses the following steps to prepare a switch for booting in installed mode, i.e., booting a package provisioning file (packages.conf)
- Boot in bundle mode using ‘boot flash:<bundle name>’
Can also boot from usbflash0: or via tftp
- Use the ‘software clean file flash:’ command to remove any unused package, bundle and provisioning files from flash:
- Use the ‘software expand running to flash:’ command to expand the running bundle to flash:
- Reload the switch
- Boot the installed packages using ‘boot flash:packages.conf’
The 'software rollback' exec command can be used to revert to a previous version of the installed software package set (i.e., an older packages.conf file)
This functionality relies on the existence of one or more 'rollback provisioning files’ in flash:, along with all of the .pkg files listed in the rollback provisioning file(s)
- The rollback provisioning files are visible in flash: as packages.conf.00-, packages.conf.01-, etc.
- packages.conf.00- is a snapshot of the packages.conf file as it looked prior to the last installation operation
- packages.conf.01- is a snapshot of the packages.conf file as it looked two installations ago
- And so on
When the 'software rollback' command is used, packages.conf.00- becomes packages.conf. packages.conf.01- becomes packages.conf.00-. And so on
Note: If the 'software clean' command is used, future attempts to do a software rollback are likely to fail