Techguide · Cisco Catalyst 8000 Licensing
Overview
← Back to overview
Section 7 of 7

Ordering, Migration, and Lifecycle Management

This section turns the licensing model into purchasing decisions: how to read a Catalyst 8000 part number, how to stand up the Smart Account and CSSM machinery that every subscription depends on, how to migrate from a la carte DNA into an Enterprise Agreement and from Gen1 ISR hardware into Gen2, and how to handle the recurring realities of renewals, co-termination, and RMAs without overpaying or stranding entitlements.

Decoding a Catalyst 8000 PID

The hardware PID encodes slot count and port layout in a fixed positional grammar. Reading it correctly prevents the two most expensive ordering errors: buying the wrong slot density and mis-sizing the port mix.

C 8300 - 2N2S - 4T 2X
│  │      │      │  │
│  │      │      │  └─ 2X = two 10-Gigabit ports (X = 10G)
│  │      │      └──── 4T = four 1-Gigabit copper ports (T = 1G)
│  │      └─────────── 2N2S = 2 NIM slots + 2 SM slots
│  │                          (1N1S = one of each)
│  └────────────────── 8300 = platform series (8200 = fixed/smaller branch)
└───────────────────── C = Cisco Product ID prefix

Applied to the fixed-port lineup: C8300-2N2S-4T2X carries 4×1G plus 2×10G across 2 NIM and 2 SM slots; C8300-2N2S-6T trades the 10G ports for six 1G copper; C8300-1N1S-4T2X and C8300-1N1S-6T halve the module slots. The 8200 line reuses the scheme — C8200-1N-4T is one NIM slot and 4×1G, and C8200L-1N-4T is the lower-cost fixed "L" variant.

The critical point: the hardware PID is orthogonal to the software entitlement. A network-stack license and a DNA-stack subscription are separate SKUs, and at least one subscription is a mandatory attach at initial hardware purchase. The chassis PID tells you nothing about what the box is licensed to do.

Figure 7.1: Anatomy of a Catalyst 8000 PID

flowchart LR
    PID["C8300-2N2S-4T2X: full chassis PID"]
    PID --> C["C = Cisco Product ID prefix"]
    PID --> SER["8300 = platform series (8200 = fixed/smaller branch)"]
    PID --> SLOT["2N2S = 2 NIM slots + 2 SM slots (1N1S = one of each)"]
    PID --> T["4T = four 1G copper ports (T = 1G)"]
    PID --> X["2X = two 10G ports (X = 10G)"]

Smart Account and CSSM setup

Every Catalyst 8000 subscription lands in a Smart Account and is managed through Cisco Smart Software Manager (CSSM). Getting this structure right before hardware arrives avoids devices that cannot register and licenses that cannot be found.

A Smart Account is the purchase container — licenses deposit into it automatically and are available for use immediately. Virtual Accounts are sub-pools inside it, used to segment licenses and product instances by site, business unit, or function. Catalyst 8000 runs Smart Licensing Using Policy (SLP) on IOS XE, which supports direct-to-CSSM, CSLU (Cisco Smart License Utility), SSM On-Prem, and fully offline deployment models.

  1. At software.cisco.com, open Administration and select "Get a Smart Account or Request Access to an Existing Smart Account."
  2. Verify the associated Cisco.com profile details and accept the Smart Software Licensing Agreement.
  3. Create one or more Virtual Accounts to organize licenses by site or function.
  4. Assign user roles with the access rights required to deposit, view, and reassign licenses.
  5. Open Smart Software Licensing under the License tab in CSSM to confirm deposited entitlements.
  6. Register each device against the Virtual Account, establishing the SLP trust relationship (direct, via CSLU, via SSM On-Prem, or offline).

Provision the account and Virtual Account structure before devices ship. A box that boots with no path to CSSM still runs, but you lose centralized visibility and cannot cleanly assign pooled entitlements.

Migration paths: DNA-to-EA and Gen1-to-Gen2

Two migrations dominate procurement planning: consolidating a la carte DNA subscriptions into an Enterprise Agreement, and replacing Gen1 ISR/ASR hardware with Gen2 Catalyst 8000.

A la carte DNA into an EA. Tier upgrades and EA moves are financially forgiving: upgrading DNA Essentials to DNA Advantage — or folding a subscription into an EA — grants 100% credit on the remaining value of the current subscription, and tiers can be upgraded mid-term. An EA is the one exception to mandatory attach: EA holders can order Catalyst 8000 hardware without selecting a DNA subscription up front, then book the subscriptions later through "brownfield" ATOs. An EA is typically a 3-year commit with true-up rights (add devices without separate POs) and portfolio-level discounting. Unused a la carte term converts to credit on the way in.

Figure 7.2: A la carte DNA into an Enterprise Agreement

flowchart TD
    A["Per-device a la carte DNA subscriptions"]
    A --> B["Residual term converts to 100% credit"]
    B --> C["Consolidated Enterprise Agreement (3-year commit)"]
    A --> D["Mid-term tier upgrade: Essentials to Advantage"]
    D --> C
    C --> E["True-up: add devices without separate POs"]
    C --> F["Brownfield ATOs: book DNA subs later"]
    C --> G["Portfolio-level discounting"]

Gen1 ISR/ASR into Gen2 Catalyst 8000. Catalyst 8200/8300 are the Gen2 successors to the ISR 4000 line — C8300 for modular or larger branches, C8200 for smaller fixed deployments; ASR 1000 maps upward to C8300/C8500 by scale. The hard constraint: perpetual/RTU licenses transfer within a product series but not across series or generations. ISR 4000 perpetual licenses do not carry to Catalyst 8000 — budget for net-new subscriptions on the Gen2 gear. HSECK9 is the narrow exception, and only in place: an existing HSECK9 authorization code registered to the Smart Account is honored after that specific instance is upgraded to SLP (Device Led Conversion), but it does not migrate to a different chassis. Before requesting a replacement quote, capture the current config, installed NIM/SM modules, WAN bandwidth, license tier, and required support term.

Renewals, co-termination, and RMA

Terms and co-termination. DNA-stack add-ons come in 3-year and 5-year terms, with 7-year available on certain add-ons. Under an EA, all subscriptions can be co-termed to a single common end date. Outside an EA, a newly added subscription can be co-termed to an existing end date as long as the 3-year minimum is met — a 5-year subscription bought in 2021 and ending 2026 lets a 2022 add-on be co-termed to also end in 2026. Best practice is to apply a renewal as a single license key covering all current devices for X years, extending the org's co-term date while holding the device limit constant.

At expiry. For traditional routing, base features remain usable via CLI but WAN management through Cisco Catalyst Center is lost; for SD-WAN, WAN management stops entirely. To fall back cleanly, deactivate the DNA-stack add-on and reload to the perpetual network-stack.

RMA. Smart Licensing decouples entitlements from the chassis, which makes hardware replacement simple: register the replacement device, then release the license from the failed instance in CSSM so the pool reassigns automatically — no per-device re-hosting. For legacy traditional licenses, use the License Registration Portal (software.cisco.com → Traditional Licenses → Access LRP), open the Devices tab, choose Move Licenses Between Devices, select Yes for "Returning Device," enter the RMA number, add the replacement device info, and submit; escalate failures through a licensing case in Support Case Manager. Portability remains bounded to a platform class or series.

Figure 7.3: License lifecycle from order to RMA reassignment

flowchart LR
    A["PO / order placed"] --> B["License deposits into Smart Account"]
    B --> C["Device registers to Virtual Account (SLP trust)"]
    C --> D["Mid-term tier upgrade (100% credit)"]
    D --> E["Co-termed renewal to common end date"]
    E --> F["RMA: release from failed instance, pool reassigns"]

Common ordering mistakes

MistakeConsequenceHow to avoid
Omitting the mandatory subscriptionOrder rejected; box cannot be quoted without a networking + DNA/Routing Essentials subAttach a subscription at initial purchase, or order under an EA (the sole exception)
Ordering the wrong throughput tierTier 2+ (>250 Mbps) silently pulls HSECK9/SLAC into scope, or the box is cappedConfirm platform, tier, and operating mode (autonomous vs. SD-WAN) before quoting
Ordering DNA separately from hardwareHSECK9 is not auto-added; the box cannot exceed the 250 Mbps crypto ceilingOrder HSECK9 explicitly whenever DNA is booked apart from the chassis
Assuming the license ships preconfiguredDevice boots without the intended tier activeSet license boot level and throughput on-device, then reload
Mismatching network and DNA tiersAdd-on will not pair (Advantage must match Advantage)Order matching tiers across both stacks
Assuming Gen1 perpetuals carry to Gen2Stranded budget; ISR 4000 licenses do not cross to Catalyst 8000Plan net-new Catalyst 8000 subscriptions in the migration budget

When hardware and DNA are ordered together, HSECK9 is auto-added when applicable; the moment you split them, that safety net disappears. Treat the joint-order default as the safe path and the split order as the one requiring a manual HSECK9 line item.

References