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

Fitting Catalyst 8000 Into an Enterprise Agreement

Catalyst 8200/8300 routing subscriptions do not have to be bought one SKU at a time. This section maps how those subscriptions fold into a Cisco Enterprise Agreement (EA 3.0), what the EA changes about growth, renewals, and portability, and the specific tier constraint that decides whether an EA is even an option for a given routing deployment.

What a Cisco EA Is (EA 3.0 and Its Workloads)

The Cisco Enterprise Agreement 3.0 is a single contract vehicle that collapses many individual software subscriptions into one agreement, with one anniversary date, purchased through one partner. EA 3.0 spans six portfolios: Networking Infrastructure, Applications Infrastructure, Collaboration, Provider Connectivity, Security, and Services. Each portfolio is a "workload" you can enroll independently — you do not have to buy all six.

For Catalyst 8000, only the Networking Infrastructure portfolio matters. Inside it sits the Cisco DNA for SD-WAN and Routing suite, which is where Catalyst 8200/8300 routing and SD-WAN subscriptions live, alongside the DNA Switching and Wireless suites, the Meraki suites, and the Nexus/SAN data-center suites. A DNA enrollment aggregates spend across Switching, Wireless, and SD-WAN/Routing to reach its commitment floor, so a routing-heavy buyer can cross the threshold faster if they are also modernizing campus switching or wireless under the same enrollment.

The value proposition is fixed, predictable pricing that is generally lower than unit-by-unit buying; consolidation of dozens of SKUs into a suite; and automatic access to updates and upgrades within the suite. To qualify, a customer commits to at least $100K Total Contract Value in full-commit suites over a 3- or 5-year term. (Program summaries sometimes cite a historical ~$250K-over-three-years figure as the level where pricing advantages become meaningful; the hard DNA-enrollment minimum is $100K TCV.)

Figure 6.1: How Catalyst 8000 routing subscriptions roll up into the Networking EA workload

flowchart TD
    A["Catalyst 8200 routing/SD-WAN subscriptions"] --> D["DNA for SD-WAN and Routing suite"]
    B["Catalyst 8300 routing/SD-WAN subscriptions"] --> D
    D --> W["Networking Infrastructure workload"]
    S["DNA Switching suite"] --> W
    L["DNA Wireless suite"] --> W
    W --> E["Cisco EA 3.0 contract"]

How Catalyst 8000 Routing Maps In

Here is the single most important constraint, and it is easy to miss: Catalyst 8000 routing enters an EA only at the DNA / Network Advantage tier. The Catalyst Routing Essentials subscription cannot be purchased inside an Enterprise Agreement — nor inside an MSLA buying program. If a site's routing requirement genuinely tops out at Essentials, it is an a-la-carte purchase, full stop, and no EA structuring will change that.

This constraint used to have an upper option: DNA Premier for SD-WAN and Routing. That tier was discontinued (reported effective ~August 2024), which means the practical EA path for Catalyst 8200/8300 is now singular — the DNA Advantage SD-WAN and Routing suite. Advantage is both the floor and, for most routing buyers, the ceiling.

A few mechanics follow from enrolling at Advantage:

True Forward and the 20% Growth Allowance

The EA's commercial engine is True Forward, and it is the opposite of the traditional ELA True Up. Under True Up, a vendor audits at a year-end milestone and back-bills for whatever you over-deployed — deploy 120 against 100 purchased, and you pay retroactively for the extra 20. Under True Forward, growth is never charged retroactively; the contract is simply revised forward at the next annual True Forward date. You are billed going forward for what you now run, not punished for the period you already ran it.

Layered on top is the 20% growth allowance: during the term you may deploy up to 20% more applicable devices or users, free of charge, before any billing event triggers. Buy 100, deploy up to 120, no charge and no True Forward event. The allowance spans any product family within the suites you purchased and applies to perpetual, SaaS, and support entitlements. Cross beyond the 20% buffer and you are still not back-billed — the overage is reconciled forward at the next billing period.

For a growing WAN edge, this combination is the whole point: you can light up new Catalyst 8300s ahead of the paperwork, absorb a fifth of that growth for free, and settle up prospectively instead of writing a retroactive compliance check.

Figure 6.2: True Forward timeline — growth absorbed during the term, one forward adjustment at renewal

timeline
    title True Forward over a One-Year Term
    Start of term : Baseline 100 devices purchased : No billing event
    Months 1-6 : Deploy new Catalyst 8300s : Within 20 percent allowance, free
    Months 7-11 : Device count reaches 120 : Still inside allowance band
    Annual True Forward date : Contract revised forward to new baseline : Billed prospectively, never back-billed
    New term forward : Reset baseline carries the added devices : True Up model would have back-billed the overage

Dated caveat — Services EA only. Cisco's Services EA is shifting from True Forward to a True Up model for hardware support on all new and renewed Services EA bookings starting July 26, 2026, to align billing with actual annual consumption. This change is scoped to the Services EA hardware-support workload. It does not apply to the Networking / DNA software suites that carry Catalyst 8000 routing — those remain True Forward. Do not let a 2026 services-billing change get mis-scoped into your DNA suite negotiation.

Portability and Co-Termination

Two EA benefits materially de-risk a multi-year Catalyst 8000 program.

Portability. Cisco DNA software for the Catalyst 8000 family is not node-locked to hardware. Licenses move across platforms, across product families, and across hardware generations, provided the target meets the subscription tier and throughput requirements. That means an 8200-to-8300 swap, or a refresh onto a later generation, does not strand entitlement — the subscription follows the workload, not the chassis. Migrating existing DNA licenses into an EA can also yield credits for unused remaining term on what you already hold.

Co-termination. The EA enforces a single anniversary / renewal date org-wide by default. Suites and add-ons bought after the initial order co-terminate with that order automatically, as long as at least 12 months remain in the term. This is genuinely an EA-exclusive perk: outside an EA, DNA subscriptions can only co-term when there is a three-year minimum overlap, so a subscription added in year 3 of a 5-year a-la-carte estate simply cannot be aligned to the same end date. Inside the EA, that restriction disappears — one renewal event, one negotiation, one date to manage.

EA vs A La Carte: When It Pays

An EA wins when the footprint is large enough, long enough, and messy enough to reward consolidation. The signals are concrete: planned Cisco software spend clearing the $100K DNA minimum (and ideally the ~$250K-over-three-years range where discounts bite), a habit of many scattered a-la-carte buys, poor license visibility, or a history of paying True Up penalties. A la carte still wins for small or single-product footprints below the threshold, genuinely short-term needs, any buyer who cannot commit to a 3- or 5-year term, and — decisively — any routing requirement that is Essentials-only, since Essentials is not EA-eligible at all.

DimensionEnterprise Agreement (EA 3.0)A La Carte
Entry minimum$100K TCV; 3- or 5-year termNone; buy as needed
Eligible routing tierDNA / Network Advantage and above onlyAny tier, including Essentials
Growth handling20% free allowance, then reconciled forwardBuy each increment at list/negotiated rate
Over-deployment billingTrue Forward — revised forward, no back-chargesBack-billed / new PO per addition
Co-terminationAutomatic if ≥12 months remain; no overlap ruleOnly with 3-year minimum overlap
PortabilityNot node-locked; credits for unused term on migrationPortable, but no EA migration credits
PricingFixed, predictable, best available price pointPer-transaction; misses EA-only discounting
Admin overheadOne contract, one date, one partnerMany SKUs, dates, and renewals to track

The opinionated read: if Catalyst 8200/8300 is part of a broader, multi-year networking modernization and every site needs Advantage anyway, the EA is the correct default — the True Forward buffer and co-termination alone justify it. The one hard disqualifier is the Essentials-tier requirement. If your routing genuinely lives at Essentials, the EA question is already answered for you, and the conversation moves back to transactional buying covered earlier in this guide.

References