Uniqcli

How to budget a Cisco Catalyst 9300 refresh: ports, PoE, licensing, and services

A line-item approach to scoping a Catalyst 9300 refresh, so the number you bring to finance survives the year it has to live in.

UT
Uniqcli Team
May 12, 2026 · 10 min read
Share
How to budget a Cisco Catalyst 9300 refresh: ports, PoE, licensing, and services

Key takeaways

  • Hardware is rarely the largest line in a Catalyst 9300 refresh once you add the right PoE budget, uplinks, stacking cables, and multi-year licensing.
  • Port count and PoE class drive the chassis decision: count powered devices and their wattage classes before you pick 24 vs 48 ports or PoE+ vs UPOE.
  • Licensing is a recurring subscription, not a one-time SKU; Network Essentials vs Network Advantage and the matching Cisco DNA term shape the multi-year total.
  • Smart Net Total Care and lifecycle services belong in the capital request from day one, not as a surprise renewal in year two.
  • Public-sector buyers should fold TAA, contract vehicle, and CLIN structure into the estimate early so the budget and the purchase path agree.

Start with the load, not the catalog

Most Catalyst 9300 budgets go wrong in the first hour, when someone opens the price list before they have counted what actually plugs in. A switch refresh is a power-and-port problem first and a hardware problem second. Before you look at a single SKU, build an inventory of every device that terminates on the access layer: phones, wireless access points, cameras, badge readers, clinical devices, and the growing pile of IoT endpoints that quietly draw PoE. That count, and the wattage class behind it, decides almost everything downstream.

The Cisco Catalyst 9300 Series is the workhorse of the enterprise access layer, and Cisco positions it that way in its own switching portfolio. The family spans fixed 24- and 48-port copper models, multigigabit variants for Wi-Fi 6E and Wi-Fi 7 uplinks, and fiber SKUs for aggregation. Picking among them is not about brand preference. It is about matching the number of active ports, the PoE class each port must deliver, and the uplink speed your distribution layer expects.

A practical first pass: list current ports in use, add a realistic three-year growth factor, then round up to the next chassis size only if the headroom is genuinely needed. Buying 48-port switches to fill 30 ports is a common way to inflate a budget by a third before licensing even enters the picture. When you are sizing the broader access design, our Catalyst switching overview walks through where the 9300 fits against the rest of the campus stack.

Ports and uplinks: size the chassis to the three-year plan

Port density is the most visible line in the budget and the easiest to get wrong in both directions. The 24-port models suit wiring closets and smaller IDFs where device counts are stable. The 48-port models earn their keep in dense floors, clinical wings, and classrooms where every drop is live. Cisco also offers multigigabit copper models that deliver 2.5, 5, and 10 Gbps over existing Category cabling, which matters when you are feeding Wi-Fi 7 access points that can saturate a 1 Gbps link.

Uplinks are where budgets quietly leak. The 9300 uses modular uplink modules rather than fixed ports, so 10G, 25G, and 40G options are a separate line item you must scope deliberately. If your distribution or core is moving to 25G, the uplink module and the matching optics need to be in the bill of materials now, not discovered during cutover. The Wi-Fi 7 transition in particular pushes more traffic toward the access layer, and our Wi-Fi 7 planning guide explains why uplink headroom is no longer optional in dense environments.

Two more lines belong in this section. Stacking cables for StackWise are not included by default and are required if you intend to run switches as a single logical unit. Optics and transceivers, whether Cisco-branded or qualified third-party, can add meaningfully to a large refresh. Spell both out as their own quantities so finance sees the real number rather than a hardware figure that doubles at the loading dock.

PoE math is the budget you forget until it bites

Power over Ethernet is where a clean hardware estimate turns into a real one. The 9300 line supports PoE, PoE+, Cisco UPOE, and UPOE+, and each step up changes both the switch SKU and the power supply you must specify. A port that only needs to run a desk phone has very different requirements from one feeding a pan-tilt-zoom camera, a high-density Wi-Fi 7 access point, or a UPOE+ device pulling up to 90 watts.

Here the trap is the per-switch power budget. A 48-port switch does not automatically deliver full PoE+ on every port at once; the total available power depends on the installed power supplies. If you populate all 48 ports with PoE+ devices and undersize the supply, you will brown out ports under load. The fix is to total your per-port wattage demand, add margin, and then choose power supply units and, where appropriate, redundant supplies to match. The IEEE maintains the underlying PoE standards, and the IEEE specifications are worth checking when you are reconciling device wattage classes against switch capability.

Build a short PoE worksheet for each closet so the power line is grounded in counted devices rather than a guess, and carry it into the bill of materials for every site in the refresh.

  • Count devices by PoE class (15.4W, 30W, 60W, 90W) and sum the load
  • Add 20 to 30 percent margin for growth and inrush
  • Select power supply wattage and decide on redundancy per closet
  • Confirm the chosen 9300 SKU supports the class on the ports you need

Licensing is a subscription, so model it across years

The single biggest reason Catalyst 9300 budgets get rejected is treating licensing as a one-time hardware add-on. It is not. The 9300 ships with a perpetual Network Essentials or Network Advantage license tier, and on top of that sits a Cisco DNA subscription with a defined term, typically three, five, or seven years. The tier and term you choose are a recurring cost that has to be modeled across the full ownership window, not buried in a single capital number.

Network Essentials covers core Layer 2 and Layer 3 switching for straightforward access deployments. Network Advantage unlocks the automation, segmentation, and assurance features that justify the platform in the first place, including the policy and telemetry hooks that integrate with Cisco Catalyst Center. If your roadmap includes software-defined access, macro and micro segmentation, or rich assurance, Advantage is usually the honest choice, and pretending Essentials will suffice only defers the cost. Our Catalyst Center page covers what the Advantage tier actually buys you in day-two operations.

Two decisions save real money here. First, co-terminate licenses so every switch in the estate renews on the same date rather than scattering renewals across the calendar. Second, decide between standalone subscriptions and a Cisco Enterprise Agreement if the refresh is large enough to make an EA economical. Our licensing and lifecycle team models both paths and the true-up implications so the multi-year line is defensible before it reaches finance.

Smart Net and services are part of the capital ask

A switch you cannot get an RMA on at 2 a.m. is a liability, not an asset. Smart Net Total Care is the support and hardware-replacement contract that keeps a 9300 estate serviceable, and Cisco describes its coverage tiers and entitlements in the Smart Net Total Care program detail. The mistake is leaving it out of the initial request so it lands as a surprise renewal the following fiscal year, when the budget is already spent.

Service level matters as much as the line item itself. An 8x5 next-business-day contract is fine for a back-office closet and badly wrong for an emergency department or a manufacturing floor that cannot wait until tomorrow for a spare. Match the SLA to the criticality of each site rather than buying one tier across the estate. For environments where downtime is measured in revenue or patient safety, our managed operations practice carries spares and handles the RMA so your team does not.

Deployment and design services round out the real total. Staging, configuration, structured cutover, and post-cutover assurance are work that happens whether or not it is in the budget; the only question is whether you planned for it. Folding these into the capital request through our deployment and design services keeps the project from stalling between purchase order and production.

End of life is a deadline, not a footnote

If part of what you are replacing is approaching end of sale or end of support, the refresh has a deadline whether you acknowledge it or not. Running production on a platform past its last day of support means no software fixes, no security patches, and no guaranteed hardware replacement. Cisco publishes the milestones that govern this in its end-of-life policy, and those dates should anchor the timing of your budget request.

The smart move is to align the refresh to the support calendar so you are buying ahead of the cliff rather than scrambling after it. That timing also gives you negotiating room, because a rushed emergency purchase rarely lands the best pricing or the best lead time. Build the EoL dates of the outgoing gear into the same spreadsheet as the new hardware, and the urgency of the capital request becomes self-evident to anyone reviewing it.

Lead time is the quiet companion of end of life. Switching hardware can carry multi-week or multi-month lead times depending on configuration and PoE class, so a budget approved too close to the support deadline can still leave you exposed. Start the procurement conversation early enough that manufacturing and shipping windows fit inside your runway, not outside it.

Public-sector buyers: fold compliance into the estimate

For federal, DoD, SLED, and healthcare buyers, the budget and the purchase path have to agree before the request goes up the chain. A Catalyst 9300 estimate that ignores Trade Agreements Act sourcing, the right contract vehicle, and CLIN structure is a number that cannot actually be executed. The compliance work is not a separate project; it is a constraint on the line items themselves, from country of origin to the contract the order rides on.

Contract vehicles shape both pricing and process. Whether the order moves through NASA SEWP, a GSA schedule, or another vehicle changes the paperwork and sometimes the unit cost, and Cisco documents how it works within federal acquisition through its federal contracts resources, alongside the NASA SEWP and GSA programs themselves. Choosing the vehicle early lets you build an estimate that matches how the money is actually allowed to move.

Configuration and hardening add real, fundable work for regulated environments. STIG-aligned baselines, secure configuration, and the documentation that auditors expect all take time and belong in the services line. Buyers should scope this through our government and defense practices so the security posture is priced in rather than discovered during an assessment. The DoD STIG library is the reference our engineers configure against for those deployments.

Put the line items together

A defensible Catalyst 9300 budget is the sum of eight categories, not one hardware quote. The chassis and port count, the uplink modules and optics, the PoE power supplies and stacking cables, the license tier and DNA term, Smart Net coverage, deployment and design services, EoL-driven timing, and compliance overhead for regulated buyers. Miss any one and the number you bring to finance will not survive contact with reality.

The healthiest version of this exercise produces a spreadsheet where every line traces back to a counted device, a chosen SLA, or a compliance requirement. That traceability is what gets a capital request approved on the first pass, because reviewers can see the reasoning instead of a single opaque total. When you are ready to turn the worksheet into firm pricing, our team can validate the BOM and return a Catalyst 9300 quote with the licensing and services modeled across the full term.

Cisco products involved

  • Cisco Catalyst 9300 Series Switches
  • Cisco Catalyst 9300X
  • Cisco Catalyst 9300L
  • Cisco UPOE and UPOE+
  • Cisco StackWise
  • Cisco DNA / Network Advantage licensing
  • Cisco Smart Net Total Care
  • Cisco Catalyst Center

Bottom line: Budget the Catalyst 9300 as eight line items, not one quote, and every number you bring to finance will hold up. Send us your port counts and PoE load for a Catalyst 9300 quote with licensing and services modeled across the full term.

Frequently asked questions

How much should I budget for Catalyst 9300 licensing on top of the hardware?

Licensing is a recurring subscription, not a one-time SKU, so it has to be modeled across the full ownership window. The 9300 carries a perpetual Network Essentials or Network Advantage tier plus a Cisco DNA subscription with a three-, five-, or seven-year term. Most regulated and automation-heavy deployments need Network Advantage, and co-terminating the subscriptions keeps renewals on a single defensible date.

What is the difference between PoE, PoE+, UPOE, and UPOE+ for budgeting?

Each step delivers more power per port and changes both the switch SKU and the power supply you must specify. PoE and PoE+ cover phones and most access points, while UPOE and UPOE+ feed higher-draw devices up to 90 watts. The budgeting risk is the total per-switch power budget: a 48-port switch needs power supplies sized to your actual summed load, plus margin, or ports will brown out under full PoE+.

Do I really need Smart Net Total Care in the initial budget?

Yes, and leaving it out is the most common reason a refresh surprises finance in year two. Smart Net Total Care provides the support and hardware-replacement entitlement that keeps the estate serviceable. Match the SLA to each site's criticality rather than buying one tier across the estate, since an emergency department or factory floor cannot wait for next-business-day replacement.

How do end-of-life dates affect when I should budget the refresh?

End of sale and end of support are hard deadlines that should anchor the timing of your capital request. Running production past last day of support means no patches and no guaranteed replacement. Align the refresh to Cisco's published EoL milestones and start procurement early, because switching hardware can carry multi-week or multi-month lead times that have to fit inside your runway.

What extra costs apply for federal, DoD, or SLED Catalyst 9300 purchases?

Public-sector budgets have to account for TAA-compliant sourcing, the right contract vehicle such as NASA SEWP or a GSA schedule, and CLIN structure, all of which can affect both unit cost and process. STIG-aligned hardening and the documentation auditors expect are real, fundable work that belongs in the services line rather than being discovered during an assessment.

UT
Written & maintained by

Uniqcli Team

The Uniqcli Team is an authorized Cisco partner specializing in Catalyst wireless, switching, datacenter fabric, licensing, and managed services for U.S. federal, state, local, and education customers. We scope Cisco bills of materials, validate procurement paths (TAA, FIPS, contract vehicles), and deliver design, deployment, and managed operations.

Ready to scope your Cisco build?

Build a quote
How to budget a Cisco Catalyst 9300 refresh: ports, PoE, licensing, and services | Uniqcli