02-27-2025 12:18 PM - edited 02-27-2025 03:33 PM
Overview
The devices under Catalyst Center inventory can have multiple SMU, subpackage or APSP. One can have same site with multiple same type of devices, but they might not have same packages. For example - eWLC package is a pre-requisite for APSP package but not applicable to other Cat9K devices without the eWLC package.
As of today (release 2.3.7.7), the Catalyst Center admin needs to separately mark the APSP image golden for eWLC devices and then upgrade those devices separately from the non-eWLC devices running the same image version. If the devices are not correctly identified and tagged, the SWIM process fails due to the unsupported APSP package even though the base image and all other packages match. Identifying such devices during SWIM upgrade every time and marking/un-marking the sub-packages/SMUs/APSP as golden based on the device type (non-WLC vs eWLC) can be tedious especially when this needs to be done for multiple devices across different sites.
This document covers the use of device tags to map specific SMU/packages to appropriate devices (under image repository) based on those tags. This prevents the need to individually mark or un-mark the subpackage/SMUs golden or not based on the device role even when using the same base image version.
Use Case Covered
This document demonstrates how to use Tags to push APSP images to only a sub-set of the Cat9K switches which have the eWLC subpackage installed and ignore the APSP image for the Ca9K switches which do not have the eWLC package installed. All the switches get the same base image and all other SMUs. Once the tags are correctly assigned, the process is seamless with no need to toggle the golden images repeatedly for devices based on the role/capability.
Although, we cover the eWLC vs non-eWLC scenario with tags here but the same logic can be used for other use cases where devices need different SMU/sub-packages with the same base image.
NOTE: In this document we are covering distribution only as the activation does not require any different steps for tagging the device or marking the appropriate SMU/sub-package golden. The user should simply continue with activation after distribution, without having to make any changes to the tags or the golden images. Or both operations can be combined from the SWIM workflow so that activation is automatically initiated after successful distribution.
Setup Details
Running Image Used - 17.6.4
Golden Image – 17.12.4
Device Tag for Non-WLC Switches: Non-WLC (Hostname: FAB-B-BR2)
Device Tag for Switches with WLC package: WLC (Hostname: FAB-B-FE1)
SMUs for 17.12.4
SMU cat9k_iosxe.17.12.04.CSCwk22887.SPA.smu.bin
SMU cat9k_iosxe.17.12.04.CSCwk25954.SPA.smu.bin
SMU cat9k_iosxe.17.12.04.CSCwm47533.SPA.smu.bin
SMU cat9k_iosxe.17.12.04.CSCwm49453.SPA.smu.bin
DMP cat9k_iosxe.17.12.04.CSCwj12978.SPA.dmp.bin
PKG C9800-SW-iosxe-wlc.17.12.04.SPA.bin (For WLC only)
APSP cat9k_iosxe.17.12.04.CSCwn02956.SPA.apsp.bin (For WLC only)
Summary of Steps:
Common steps for WLC and non-WLC switches to be performed on Catalyst Center for base image and SMU distribution:
1. Create and Assign Tags to the devices from inventory UI
2. Image Repository
2.1 Mark Golden Image: 17.12.4
2.2 Assign Device Roles/Tags - "Roles: All" + "Non-WLC" + "WLC"
(The same device tags should be used for the devices under inventory. Use existing tags as applicable (if the WLC and Non-WLC devices are already tagged based on the WLC role but with different tags)
Addons Marked Golden and Tags Used
SMU (5) - Device Roles/Tags - "Roles: All" + "Non-WLC" + "WLC"
Sub-package (1)
APSP (1) - Device Roles/Tags : Rolls: All + WLC
Inventory View (Focus: Software image)
Device tagged as "Non-WLC" OR "WLC" as applicable
Running Image: cat9k_iosxe.17.06.04.SPA.bin
Golden Image: cat9k_iosxe.17.12.04.SPA.bin, cat9k_iosxe.17.12.04.CSCwm47533.SPA.smu.bin, cat9k_iosxe.17.12.04.CSCwk25954.SPA.smu.bin, cat9k_iosxe.17.12.04.CSCwk22887.SPA.smu.bin, cat9k_iosxe.17.12.04.CSCwj12978.SPA.dmp.bin, cat9k_iosxe.17.12.04.CSCwm49453.SPA.smu.bin
(For the device tagged as "Non-WLC", we should not see the WLC package or the APSP image.)
3.2 Device tagged as "WLC"
Running Image: cat9k_iosxe.17.06.04.SPA.bin, C9800-SW-iosxe-wlc.17.06.04.SPA.bin
Golden Image: cat9k_iosxe.17.12.04.SPA.bin, cat9k_iosxe.17.12.04.CSCwm47533.SPA.smu.bin, cat9k_iosxe.17.12.04.CSCwk25954.SPA.smu.bin, cat9k_iosxe.17.12.04.CSCwk22887.SPA.smu.bin, cat9k_iosxe.17.12.04.CSCwj12978.SPA.dmp.bin, cat9k_iosxe.17.12.04.CSCwm49453.SPA.smu.bin,cat9k_iosxe.17.12.04.CSCwn02956.SPA.apsp.bin, C9800-SW-iosxe-wlc.17.12.04.SPA.bin
(For the device tagged as "WLC" we should see the WLC package and the APSP image as well.)
4.0 WLC device state before the upgrade
FAB-B-FE1# show install summary
[ Switch 1 ] Installed Package(s) Information:
State (St): I - Inactive, U - Activated & Uncommitted,
C - Activated & Committed, D - Deactivated & Uncommitted
--------------------------------------------------------------------------------
Type St Filename/Version
--------------------------------------------------------------------------------
IMG C 17.06.04.0.4912
PKG C flash:C9800-SW-iosxe-wlc.17.06.04.SPA.bin
--------------------------------------------------------------------------------
Auto abort timer: inactive
--------------------------------------------------------------------------------
4.1 WLC Device Image Distribution (GUI)
We see 7 Addons for the WLC device.
Skipping Activation:
Schedule:
Summary:
4.2 After Successful Distribution:
Base image (1), WLC Sub-package (1), SMU (5)
On the device we see the 17.12.4 base image + WLC image + 5 Addons (SMU) copied on the flash:
FAB-B-FE1#sh flash: | i smu|apsp|dmp|SPA.bin
4 1306917133 Feb 14 2025 19:51:39.0000000000 +00:00 cat9k_iosxe.17.12.04.SPA.bin
49 653112828 Feb 14 2025 20:19:28.0000000000 +00:00 C9800-SW-iosxe-wlc.17.12.04.SPA.bin
251 42504 Feb 14 2025 19:59:32.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwm47533.SPA.smu.bin
254 5596 Feb 14 2025 20:02:06.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwk25954.SPA.smu.bin
255 34352 Feb 14 2025 20:04:42.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwk22887.SPA.smu.bin
262 10995124 Feb 14 2025 20:07:18.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwj12978.SPA.dmp.bin
264 22024 Feb 14 2025 20:09:52.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwm49453.SPA.smu.bin
265 498615784 Feb 14 2025 20:13:59.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwn02956.SPA.apsp.bin
17.12.4 base image + WLC sub-package will be in "Inactive" state:
FAB-B-FE1#show install summary
[ Switch 1 ] Installed Package(s) Information:
State (St): I - Inactive, U - Activated & Uncommitted,
C - Activated & Committed, D - Deactivated & Uncommitted
--------------------------------------------------------------------------------
Type St Filename/Version
--------------------------------------------------------------------------------
IMG C 17.06.04.0.4912
PKG C flash:C9800-SW-iosxe-wlc.17.06.04.SPA.bin
IMG I 17.12.04.0.4826
PKG I flash:C9800-SW-iosxe-wlc.17.12.04.SPA.bin
5.0 Non-WLC Device Image Distribution
Non-WLC device state before the upgrade
FAB-B-BR2# show install summary
[ Switch 1 ] Installed Package(s) Information:
State (St): I - Inactive, U - Activated & Uncommitted,
C - Activated & Committed, D - Deactivated & Uncommitted
--------------------------------------------------------------------------------
Type St Filename/Version
--------------------------------------------------------------------------------
IMG C 17.06.04.0.4912
5.1 Non-WLC Device Image Distribution (GUI)
We see 5 Addons in the screenshot above (unlike WLC device where we saw 7 (APSP + WLC subpackage)).
Skipping Activation:
Schedule:
Summary:
5.2 After Successful Distribution:
On the device we see the 17.12.4 base image + 5 Addons (SMU):
FAB-B-BR2#show flash: | i smu|SPA.bin
4 1306917133 Feb 14 2025 19:37:47.0000000000 +00:00 cat9k_iosxe.17.12.04.SPA.bin
168 42504 Feb 14 2025 19:47:10.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwm47533.SPA.smu.bin
169 5596 Feb 14 2025 19:49:45.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwk25954.SPA.smu.bin
170 34352 Feb 14 2025 19:52:20.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwk22887.SPA.smu.bin
171 10995124 Feb 14 2025 19:54:56.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwj12978.SPA.dmp.bin
172 22024 Feb 14 2025 19:57:30.0000000000 +00:00 cat9k_iosxe.17.12.04.CSCwm49453.SPA.smu.bin
FAB-B-BR2#
17.12.4 base image will be in "Inactive" state:
FAB-B-BR2#show install summary
[ Switch 1 ] Installed Package(s) Information:
State (St): I - Inactive, U - Activated & Uncommitted,
C - Activated & Committed, D - Deactivated & Uncommitted
--------------------------------------------------------------------------------
Type St Filename/Version
--------------------------------------------------------------------------------
IMG C 17.06.04.0.4912
IMG I 17.12.04.0.4826
Continue with image activation via the SIWIM workflow after successful distribution.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: