Licensing with Cisco DNA and Smart Licensing

Learning Objectives

A Catalyst 8000 router is closer to a smartphone on a carrier plan than to a laptop you own outright: you own the hardware, but most of what makes it useful — SD-WAN, advanced security, automation, analytics — arrives through a subscription you must keep current. Even the speed of the box and its ability to encrypt traffic at full rate are gated by licensing, not just by the silicon. This guide walks through the two-stack model, Smart Licensing Using Policy, and HSEC/throughput controls.

Pre-Quiz: Licensing Tiers

A customer renews nothing when their Catalyst 8300's DNA subscription term ends. What is the most accurate description of the router's state afterward?

The router stops forwarding all traffic until a new subscription is applied. It keeps routing at its owned Network-stack tier but loses DNA features like advanced SD-WAN and analytics. It reverts to DNA Essentials regardless of which tier was purchased. It automatically migrates into Cisco Networking Subscription.

Why is it incorrect to pair Network Essentials with DNA Advantage on a Catalyst 8000?

DNA Advantage requires more memory than Network Essentials hardware provides. The two stacks are tier-matched, so the Network and DNA tiers must align (Essentials with Essentials, Advantage with Advantage). DNA Advantage is perpetual while Network Essentials is term-based, so the terms conflict. Network Essentials cannot run SD-WAN at all under any DNA tier.

A branch engineer says, "We bought DNA Advantage, now we need to add the SD-WAN product license." What is wrong with this statement?

SD-WAN is only available with DNA Premier, not Advantage. The DNA subscription is the SD-WAN license; there is no separate SD-WAN product to buy. SD-WAN requires a separate perpetual SEC license that was retired. SD-WAN is licensed by the throughput tier, not the DNA tier.

Which statement best captures the relationship between the throughput tier (T0–T3) and the DNA feature tier?

They are the same control expressed two different ways. The throughput tier is a separate software-enforced cap on forwarding bandwidth, distinct from the DNA feature tier. A higher DNA tier automatically removes any throughput cap. Throughput tiers apply only to the C8000V and never to hardware platforms.

A planner assumes their Catalyst 8000 routers can move to Cisco Networking Subscription (CNS) along with their switches. Why is this assumption flawed?

CNS is more expensive, so it is never economical for routers. Routing is explicitly excluded from CNS today; Catalyst 8000 routers stay on the Network + DNA model. CNS only covers hardware purchased after 2026. CNS requires HSEC licenses that routers cannot hold.

1. Licensing Tiers

Key Points

The Two-Stack Model: Network Stack vs. DNA Stack

The single most important idea in Catalyst 8000 licensing is that every router carries two licenses, not one. Cisco organizes IOS XE licensing into two parallel "stacks." The Network stack maps to the routing feature set, comes in two tiers (Essentials and Advantage), and behaves as a perpetual license — even after everything else expires, the box keeps routing. The DNA stack is the subscription add-on that rides on top, comes in three tiers (Essentials, Advantage, Premier), and is term-based (rented for 3, 5, or 7 years).

A useful analogy: the Network stack is like owning a car and the DNA stack like a subscription to a navigation-and-driver-assist service. When the subscription lapses, the car still drives — you simply lose the smart features layered on top. The two stacks are tier-matched: Network Essentials pairs with DNA Essentials, Network Advantage pairs with DNA Advantage. In ordering this usually appears as a single bundled SKU. On the 8200 and 8300 the DNA subscription is mandatory; the older perpetual add-ons (SEC, UC, APP) have been retired.

Figure 4.1: The two-stack model and tier-matching

graph TD R["Catalyst 8000 Router"] --> NS["Network Stack (perpetual): routing rights"] R --> DS["DNA Stack (term-based): SD-WAN, automation, analytics"] NS --> NE["Network Essentials"] NS --> NA["Network Advantage"] DS --> DE["DNA Essentials"] DS --> DA["DNA Advantage"] DS --> DP["DNA Premier"] NE -. tier-matched .- DE NA -. tier-matched .- DA NA -. tier-matched .- DP
Catalyst 8000 Router Network stack (perpetual) DNA stack (term-based) Network Essentials routing rights Network Advantage richer routing rights DNA Essentials core SD-WAN, basic telemetry DNA Advantage full SD-WAN, deep analytics DNA Premier Advantage + bundled security dotted lines = tier-matched pairings (Advantage also covers Premier)
The two stacks reveal side by side: the perpetual Network stack and the term-based DNA stack, with Essentials, Advantage, and Premier staggering in and the tier-matched pairings drawn last.

DNA Essentials, Advantage, and Premier

The DNA-stack tier determines which subscription features light up. DNA Essentials delivers core SD-WAN, basic device management, and basic telemetry — often enough for a branch doing SD-WAN with direct internet access break-out. DNA Advantage adds the full SD-WAN feature set with advanced policies, richer security/segmentation, deeper analytics, and ecosystem integration (ISE, Secure Network Analytics, ThousandEyes); the DNA portion typically runs 50–100% more than Essentials. DNA Premier sits above Advantage as a bundle rolling in additional Cisco software entitlements (such as advanced security/threat services). Critically, the DNA subscription is the SD-WAN license — there is no separate SD-WAN product.

TierSD-WAN fabricSecurity / segmentationAnalytics & assuranceRouting pairingRelative cost
DNA EssentialsCore SD-WAN, basic app-aware routingBaseline; limited advanced featuresBasic monitoring/telemetryNetwork EssentialsLowest
DNA AdvantageFull SD-WAN, advanced policies & app optimizationEnhanced security, richer segmentationDeeper analytics, ecosystem integrationNetwork Advantage~50–100% higher
DNA PremierFull SD-WAN (Advantage set)Advantage plus bundled advanced security/threat servicesAdvantage analytics plus bundled servicesNetwork AdvantageHighest

What Happens When the Term Expires

Because the DNA stack is a rental, expiry matters. When a DNA term ends and is not renewed, the device keeps routing using the Network tier you own, but you lose DNA-only capabilities (advanced SD-WAN control, certain automation/analytics, DNA cloud services) and entitlement to new DNA-scope feature updates and subscription support. The danger is that this happens quietly — routing continues, so nobody notices until an SD-WAN feature or support case is needed. Track end dates and budget renewals against the hardware lifecycle (a 5-year term aligned to a 5-year refresh is a common pattern).

Figure 4.2: What persists and what is lost when the DNA term expires

flowchart TD E["DNA subscription term ends, not renewed"] E --> K["KEPT: routing via owned Network tier (Essentials/Advantage)"] E --> L["LOST: advanced SD-WAN control, automation, analytics, DNA cloud services"] E --> U["LOST: entitlement to new DNA-scope feature updates and subscription support"] K --> Q["Quiet failure: routing continues, so lapse goes unnoticed"] L --> Q U --> Q Q --> M["Mitigation: track end dates and budget renewals to lifecycle"]

Throughput-Based Tiers (T0/T1/T2/T3)

Beyond the feature stacks, Catalyst 8000 ordering includes a throughput tier — a software-enforced cap on how much traffic the router will forward. The platform supports multiple levels (commonly grouped T0–T3, mapping to ascending bandwidth ranges such as 50 Mbps, 100 Mbps, 250 Mbps, 500 Mbps, 1 Gbps and higher). IOS XE polices the data plane to the configured tier, so capable hardware still caps forwarding at the tier you licensed. On the C8000V you configure throughput explicitly; on hardware it is generally tied to your DNA license selection. As the HSEC section shows, the throughput tier and the crypto cap are independent controls.

Cisco Networking Subscription: Why Routers Are Excluded

Cisco has introduced Cisco Networking Subscription (CNS) as a unified subscription spanning many product families — but routing is explicitly excluded from CNS today. Catalyst 8000 routers stay on DNA subscriptions; you cannot migrate them into CNS. In a mixed environment, your switches and wireless may move to CNS (36-month minimum term) while your routers stay on the Network + DNA model. Plan budgets accordingly.

Post-Quiz: Licensing Tiers

A customer renews nothing when their Catalyst 8300's DNA subscription term ends. What is the most accurate description of the router's state afterward?

The router stops forwarding all traffic until a new subscription is applied. It keeps routing at its owned Network-stack tier but loses DNA features like advanced SD-WAN and analytics. It reverts to DNA Essentials regardless of which tier was purchased. It automatically migrates into Cisco Networking Subscription.

Why is it incorrect to pair Network Essentials with DNA Advantage on a Catalyst 8000?

DNA Advantage requires more memory than Network Essentials hardware provides. The two stacks are tier-matched, so the Network and DNA tiers must align (Essentials with Essentials, Advantage with Advantage). DNA Advantage is perpetual while Network Essentials is term-based, so the terms conflict. Network Essentials cannot run SD-WAN at all under any DNA tier.

A branch engineer says, "We bought DNA Advantage, now we need to add the SD-WAN product license." What is wrong with this statement?

SD-WAN is only available with DNA Premier, not Advantage. The DNA subscription is the SD-WAN license; there is no separate SD-WAN product to buy. SD-WAN requires a separate perpetual SEC license that was retired. SD-WAN is licensed by the throughput tier, not the DNA tier.

Which statement best captures the relationship between the throughput tier (T0–T3) and the DNA feature tier?

They are the same control expressed two different ways. The throughput tier is a separate software-enforced cap on forwarding bandwidth, distinct from the DNA feature tier. A higher DNA tier automatically removes any throughput cap. Throughput tiers apply only to the C8000V and never to hardware platforms.

A planner assumes their Catalyst 8000 routers can move to Cisco Networking Subscription (CNS) along with their switches. Why is this assumption flawed?

CNS is more expensive, so it is never economical for routers. Routing is explicitly excluded from CNS today; Catalyst 8000 routers stay on the Network + DNA model. CNS only covers hardware purchased after 2026. CNS requires HSEC licenses that routers cannot hold.
Pre-Quiz: Smart Licensing Using Policy

How does Smart Licensing Using Policy (SLP) fundamentally differ from legacy Smart Licensing for unenforced licenses?

SLP requires a registration token before any feature can be used. SLP uses a "use now, report later" model — unenforced licenses work immediately and usage is reported per policy. SLP eliminates the need for CSSM entirely. SLP keeps the device in evaluation mode until Cisco grants authorization.

A router using SLP cannot reach any reporting destination for several months. What happens to its unenforced licensed features?

They are disabled until a RUM report is successfully accepted. They keep working; the report simply goes overdue and the router logs syslog warnings. The router falls back into evaluation mode. The router reloads automatically to clear the licensing state.

What does a RUM report contain, and what is its role under SLP?

An authorization token the router must obtain before using features. Structured usage data (licenses in use, quantities, device IDs, timestamps) that the router sends to CSSM to report consumption. A firmware image that updates the licensing agent. A billing invoice generated by the router for the customer.

A bank keeps its routers entirely off the public internet but must still report license usage. Which SLP approach fits best?

Direct Smart Transport over HTTPS straight to Cisco's cloud. On-prem CSLU/CSSM Satellite, or offline file export/import, neither requiring routers to reach the internet directly. Legacy token registration, which works offline. Disabling licensing entirely, since offline routers are exempt.

In CSSM, a license type shows Purchased 50, In Use 60. What does this indicate and how is it flagged?

A healthy surplus of 10 licenses, flagged as Balance positive. Usage exceeds entitlement (Balance -10), flagged by CSSM as Insufficient Licenses. A reporting error that the router will auto-correct on next reload. That 10 licenses have expired and must be renewed.

2. Smart Licensing Using Policy

Key Points

From "Register First" to "Report Usage"

Legacy Smart Licensing (16.x and early 17.x) followed an "obtain authorization before use" model: you generated a token, ran license smart register idtoken ..., and the device sat in evaluation mode until Cisco authorized it. If it could not reach Cisco it risked falling out of compliance with noisy warnings. SLP, introduced in IOS XE 17.3.2, flips this to "trust, then verify by reporting": no registration token for unenforced licenses, no evaluation mode, unenforced licenses authorized by default, and usage reporting replacing continuous authorization on a policy schedule.

AspectLegacy Smart LicensingSmart Licensing Using Policy (SLP)
Initial stateEvaluation mode mandatoryNo evaluation mode (unenforced licenses)
Device registrationToken registration requiredNo registration for unenforced licenses
AuthorizationExplicit authorization from CSSMUnenforced licenses authorized by default
ConnectivityContinuous/frequent for compliancePeriodic usage reporting per policy
If offlineCould fall out of complianceFeatures keep working; reports go overdue
Configuration effortCall-home, transport, tokenJust configure features; transport for reporting only

CSSM, RUM Reports, and Trust

Cisco Smart Software Manager (CSSM) is the central cloud portal managing your Smart Account, virtual accounts, and entitlements. Under SLP it is the system of record: for each license type it shows Purchased, In Use, and Balance (Purchased − In Use). With 50 CUBE sessions purchased and 20 in use, CSSM shows Purchased 50, In Use 20, Balance 30. If usage exceeds entitlement (balance goes negative), CSSM flags Insufficient Licenses.

The router feeds CSSM through RUM reports — structured data showing which licenses are in use, quantities (throughput level, session count), device identifiers, timestamps, and policy metadata. The product instance continuously records usage, generates reports, stores them until sent, and logs alerts if a report becomes overdue. The policy governs how often you must report (e.g., 30, 90, or 365 days); general guidance is a report within 90 days of a usage change. Trust is now a policy-driven state: the router sends a RUM report, CSSM associates it with the account and returns confirmation, and the device tracks whether it holds a valid current policy and reported within the window. A stale trust state produces warnings, but unenforced features keep working.

Reporting Methods: Online, On-Prem, and Air-Gapped

SLP supports three transports so you can match licensing to your security posture: (1) Direct online (Smart Transport) — HTTPS straight to Cisco's cloud CSSM, configured with license smart transport smart; (2) On-prem via CSLU or CSSM Satellite — deploy a Cisco Smart License Utility registered to your Smart Account and point the router at it, then the on-prem server syncs to cloud CSSM; (3) Offline / air-gapped file exchange — the router accumulates usage, you export a RUM file, upload it to CSSM from a connected machine, then download and import updated policy/trust. You can verify state with show license all and show license usage, and trigger reporting with license smart sync all.

Figure 4.3: RUM report flow from router to CSSM across the three transports

flowchart LR PI["Router (product instance): records usage, generates RUM reports per policy"] PI --> T1["Smart Transport: HTTPS direct"] PI --> T2["CSLU / on-prem CSSM"] PI --> T3["Offline file export (CLI/USB)"] T1 --> CSSM["Cloud CSSM: system of record (Purchased / In Use / Balance)"] T2 --> CSSM T3 --> FILE["Upload file from connected machine"] FILE --> CSSM CSSM --> ACK["Returns acceptance + updated policy/trust"] ACK --> PI
Router generates RUM reports Smart Transport HTTPS direct CSLU / on-prem syncs to cloud Offline file export CLI / USB upload Cloud CSSM system of record Purchased/In Use/Balance RUM RUM file file ACK + policy
A RUM report leaves the router and travels along one of three transports — direct Smart Transport, CSLU/on-prem, or an offline file upload — to cloud CSSM, which glows as it records usage and returns an acceptance plus updated policy/trust.
Post-Quiz: Smart Licensing Using Policy

How does Smart Licensing Using Policy (SLP) fundamentally differ from legacy Smart Licensing for unenforced licenses?

SLP requires a registration token before any feature can be used. SLP uses a "use now, report later" model — unenforced licenses work immediately and usage is reported per policy. SLP eliminates the need for CSSM entirely. SLP keeps the device in evaluation mode until Cisco grants authorization.

A router using SLP cannot reach any reporting destination for several months. What happens to its unenforced licensed features?

They are disabled until a RUM report is successfully accepted. They keep working; the report simply goes overdue and the router logs syslog warnings. The router falls back into evaluation mode. The router reloads automatically to clear the licensing state.

What does a RUM report contain, and what is its role under SLP?

An authorization token the router must obtain before using features. Structured usage data (licenses in use, quantities, device IDs, timestamps) that the router sends to CSSM to report consumption. A firmware image that updates the licensing agent. A billing invoice generated by the router for the customer.

A bank keeps its routers entirely off the public internet but must still report license usage. Which SLP approach fits best?

Direct Smart Transport over HTTPS straight to Cisco's cloud. On-prem CSLU/CSSM Satellite, or offline file export/import, neither requiring routers to reach the internet directly. Legacy token registration, which works offline. Disabling licensing entirely, since offline routers are exempt.

In CSSM, a license type shows Purchased 50, In Use 60. What does this indicate and how is it flagged?

A healthy surplus of 10 licenses, flagged as Balance positive. Usage exceeds entitlement (Balance -10), flagged by CSSM as Insufficient Licenses. A reporting error that the router will auto-correct on next reload. That 10 licenses have expired and must be renewed.
Pre-Quiz: HSEC and Throughput

A Catalyst 8000 is licensed for a 1 Gbps throughput tier but has no HSEC license. What throughput will encrypted (IPsec) traffic actually achieve?

The full ~1 Gbps, since the tier sets the limit. About 250 Mbps, because the export-control crypto cap applies without HSEC. Zero, because encryption is fully blocked without HSEC. Exactly 500 Mbps, half the tier.

What is the correct mental model for how the throughput tier and HSEC interact?

HSEC raises the throughput tier by one level. They are two independent gates; encrypted throughput is limited by whichever gate is lower. The throughput tier only matters once HSEC is installed. HSEC and the throughput tier always produce the same number.

On an ISR 4000, an engineer installs the Boost (Performance) license but IPsec still tops out near 250 Mbps. Why?

Boost removes the general forwarding cap but does not address crypto; HSEC is still needed. Boost and HSEC are the same license under different names. Boost only applies to plaintext on the Catalyst 8000, not the ISR. The router needs a reload before Boost affects crypto throughput.

Site B must carry ~800 Mbps of encrypted hub traffic with advanced SD-WAN and ecosystem integration. What licensing does it need?

DNA Essentials, 250 Mbps tier, no HSEC. Network/DNA Advantage, ~1 Gbps tier, and an active HSEC-K9 license. DNA Advantage and HSEC, but the throughput tier is irrelevant. Network Essentials plus a Boost license to lift the crypto cap.

HSEC and the throughput tier are both correct, yet measured throughput still falls short of the licensed ceiling. What is a likely cause?

The export-control cap is still active despite HSEC. Feature overhead (zone-based firewall, IPS, NetFlow, heavy QoS) consumes data-plane cycles, holding real throughput below the ceiling. The DNA subscription has silently downgraded the tier. RUM reports are overdue, which throttles forwarding.

3. HSEC and Throughput

Key Points

The HSEC License and the 250 Mbps Crypto Cap

A Catalyst 8000 licensed for 1 Gbps of throughput may still refuse to push more than ~250 Mbps of encrypted traffic — because of export control, not hardware. U.S. regulations historically required vendors to limit high-speed strong encryption in certain territories. Cisco implements this as a soft cap of ~250 Mbps on encrypted (IPsec/crypto) throughput and on tunnel/SA scale, lifted only with an export-control license. SEC-K9 enables standard crypto but stays export-limited; HSEC-K9 (High-Security Export Control) removes the limitation so the router can use its full crypto capability, subject to whatever throughput tier you hold. The cap applies only to encrypted traffic — on a 1 Gbps router without HSEC, unencrypted traffic flows near 1 Gbps while IPsec stubbornly tops out around 250 Mbps. That is the classic symptom: tunnels that never exceed ~200–250 Mbps no matter how much WAN bandwidth you provision.

Throughput Tiers and HSEC Are Independent

The key mental model: the throughput tier and HSEC are two separate gates, and your encrypted throughput is limited by whichever is lower.

To push more than 250 Mbps of IPsec you need both a throughput tier high enough for the target bandwidth and an active HSEC license.

Figure 4.4: The two independent gates limiting encrypted throughput

flowchart TD TRAF["Encrypted (IPsec) traffic"] --> G1{"Gate 1: Throughput tier"} G1 --> G2{"Gate 2: HSEC license present?"} G2 -->|"No HSEC"| CAP["Export cap ~250 Mbps applies"] G2 -->|"HSEC active"| FULL["Limited only by throughput tier"] CAP --> RESULT["Effective encrypted rate = lower of the two gates"] FULL --> RESULT
0 250M 500M 1 Gbps Gate 1 — Throughput tier (1 Gbps) Gate 2 — HSEC: NOT present → export cap ~250M Effective encrypted rate = lower of the two gates clamped to ~250 Mbps Tier allows 1 Gbps, but with no HSEC the export cap (~250M) wins — the green "effective" bar is clamped to the lower gate. Plaintext, meanwhile, would still reach 1 Gbps.
Two gates fill in: the throughput tier reaches 1 Gbps, but HSEC is absent so the export cap stops at ~250 Mbps. The effective encrypted-throughput bar is then clamped to the lower of the two — a vivid picture of why both gates must be cleared.

Boost / Performance Licenses

On the older ISR 4000 series, Cisco used a Performance (Boost) license to lift an artificial cap on overall forwarding — letting the box run unthrottled up to its hardware limits. Boost is not HSEC: Boost removes the general forwarding cap, HSEC removes the crypto cap. On an ISR 4K you can install Boost and still see IPsec stuck at ~250 Mbps because HSEC is missing — you need both. On the Catalyst 8000 the Boost role is filled by the throughput tiers, but the same logic holds: high crypto throughput requires a high tier and HSEC.

Installing and Verifying HSEC

Catalyst 8000 manages HSEC through Smart Licensing / SLP. Verify with show license all, show license usage, and show platform hardware throughput level; look for an HSEC/HSEC-K9 entry with status IN USE or AUTHORIZED, and confirm the throughput level is high enough. If HSEC is missing: in SD-WAN deployments use the "Sync and Install HSEC Licenses" workflow in Cisco SD-WAN Manager (vManage); in autonomous mode follow the online or offline HSEC install guide (register with Smart Licensing, then install/activate HSEC). On the C8000V you set throughput explicitly and reload (e.g., platform hardware throughput level 500000); at or above 250 Mbps/T1 an HSEC license is required to avoid the export cap. Remember that feature overhead (zone-based firewall, IPS, NetFlow, heavy QoS) consumes data-plane cycles and can hold real throughput below the licensed ceiling even when HSEC and the tier are correct — check show platform hardware qfp active datapath utilization summary if numbers fall short.

Worked Example: Choosing the Right Tier

Site A — Small branch, simple SD-WAN. A Catalyst 8300 with SD-WAN, DIA break-out, basic app-aware routing, standard NAT/firewalling, and a 200 Mbps circuit all encrypted to the hub. Feature need → DNA Essentials + Network Essentials. Throughput → ~200 Mbps, all encrypted, below the 250 Mbps cap, so a 250 Mbps (T1-class) tier covers it and no HSEC is required. Term → 5 years. Result: Network Essentials + DNA Essentials, 250 Mbps tier, 5 years, no HSEC.

Site B — Regional hub, complex and high-speed. A Catalyst 8500 aggregating many branches with large-scale SD-WAN, advanced traffic engineering, segmentation, integrated security, and ecosystem integration, carrying ~800 Mbps of encrypted hub traffic. Feature need → DNA Advantage + Network Advantage. Throughput → ~800 Mbps encrypted, exceeding 250 Mbps, so a 1 Gbps (T2/T3-class) tier and an HSEC license — both gates cleared. Term → 5–7 years. Result: Network Advantage + DNA Advantage, ~1 Gbps tier, HSEC-K9, 5–7 years.

The reusable rule: default to Essentials, escalate to Advantage by exception, and add HSEC the moment your encrypted throughput target crosses ~250 Mbps.

Figure 4.5: License-selection decision tree

flowchart TD START["New site to license"] --> Q1{"Need advanced SD-WAN, rich segmentation, or ecosystem integration?"} Q1 -->|"No"| ESS["Network Essentials + DNA Essentials"] Q1 -->|"Yes"| ADV["Network Advantage + DNA Advantage (or Premier)"] ESS --> Q2{"Encrypted throughput > ~250 Mbps?"} ADV --> Q2 Q2 -->|"No"| TIER1["Size throughput tier to circuit; no HSEC needed"] Q2 -->|"Yes"| TIER2["High throughput tier + HSEC-K9 license"] TIER1 --> TERM["Choose term (3/5/7 yr) aligned to lifecycle"] TIER2 --> TERM
Post-Quiz: HSEC and Throughput

A Catalyst 8000 is licensed for a 1 Gbps throughput tier but has no HSEC license. What throughput will encrypted (IPsec) traffic actually achieve?

The full ~1 Gbps, since the tier sets the limit. About 250 Mbps, because the export-control crypto cap applies without HSEC. Zero, because encryption is fully blocked without HSEC. Exactly 500 Mbps, half the tier.

What is the correct mental model for how the throughput tier and HSEC interact?

HSEC raises the throughput tier by one level. They are two independent gates; encrypted throughput is limited by whichever gate is lower. The throughput tier only matters once HSEC is installed. HSEC and the throughput tier always produce the same number.

On an ISR 4000, an engineer installs the Boost (Performance) license but IPsec still tops out near 250 Mbps. Why?

Boost removes the general forwarding cap but does not address crypto; HSEC is still needed. Boost and HSEC are the same license under different names. Boost only applies to plaintext on the Catalyst 8000, not the ISR. The router needs a reload before Boost affects crypto throughput.

Site B must carry ~800 Mbps of encrypted hub traffic with advanced SD-WAN and ecosystem integration. What licensing does it need?

DNA Essentials, 250 Mbps tier, no HSEC. Network/DNA Advantage, ~1 Gbps tier, and an active HSEC-K9 license. DNA Advantage and HSEC, but the throughput tier is irrelevant. Network Essentials plus a Boost license to lift the crypto cap.

HSEC and the throughput tier are both correct, yet measured throughput still falls short of the licensed ceiling. What is a likely cause?

The export-control cap is still active despite HSEC. Feature overhead (zone-based firewall, IPS, NetFlow, heavy QoS) consumes data-plane cycles, holding real throughput below the ceiling. The DNA subscription has silently downgraded the tier. RUM reports are overdue, which throttles forwarding.

Your Progress

Answer Explanations