Cisco Catalyst 3650 switch (left) beside its Catalyst 9300L replacement (right) on a white background - Catalyst 3650 end of support guide, Reef Telecom

Cisco Catalyst 3650 Support Ended October 31, 2026: What to Do If You Are Still Running Them

· Reef Telecom· 5 min read

On October 31, 2026, Cisco's Last Date of Support for the Catalyst 3650 passed. Nothing in your wiring closet noticed: a 3650 switching traffic on October 30 kept switching it on November 1, and will probably keep doing so for years. What ended is not the hardware's working life but Cisco's side of the bargain — which makes this milestone easy to ignore and worth planning around. If your access layer still runs on 3650s, here is what changed, how exposed you are, and the order to act in.

The timeline that led here

Cisco announced the 3650's end of life on October 31, 2020, in its end-of-sale and end-of-life bulletin for the family (notice EOL14617). The milestones then arrived in the usual order:

  • October 31, 2021 — end of sale: the last day to order a 3650 through Cisco.
  • October 31, 2022 — end of software maintenance releases, and the last day to attach a new service contract to a unit that did not already have one.
  • January 29, 2026 — end of service contract renewal: after this date, an existing Cisco contract on a 3650 could no longer be extended.
  • October 31, 2026 — end of vulnerability and security support, and the Last Date of Support itself.

That last line does the real work. In Cisco's own wording, after the Last Date of Support all support services for the product are unavailable and the product becomes obsolete. Two practical consequences follow. First, there is no longer a Cisco contract to fall back on: TAC cases, hardware replacement under a Cisco agreement, and the renewal option are all closed, not merely winding down. Second, the security side is finished — October 31, 2026 was also the last date on which Cisco engineering could release a planned remedy for a security vulnerability in the platform, and ordinary software maintenance releases had already ended back in 2022. A vulnerability found in a 3650 next year is one you mitigate yourself, by configuration, segmentation, or replacement.

Step one: count what you actually have

Lifecycle plans go wrong when they are built on a rough guess at the installed base. Before deciding anything, take a proper inventory: read the chassis product ID from each switch (the label, or show inventory), and count every stack member as a unit in its own right — a three-switch stack is three 3650s to replace, power, and find rack space for, not one line on a spreadsheet. For each unit, note three things alongside the model: what it powers (desk phones, access points, cameras, or data-only ports), what its uplinks are (1G or 10G, copper or fibre), and what depends on it (a single office closet is a different risk from the switch carrying your call platform or your building's cameras). That short exercise usually splits the estate into a small group that matters urgently and a larger group that can move on a calmer schedule.

Step two: triage by risk, not by age

Not every unsupported switch is an emergency, and treating them all as one wastes the budget on the wrong closets first. Move first the units where a failure or an unpatched vulnerability hurts most: switches feeding phones and wireless, anything carrying core rather than edge traffic, and any 3650 whose management interface is reachable from networks you do not fully control. A 3650 running a quiet, segmented printer VLAN still belongs on the replacement list, but it can honestly sit near the bottom. Write the reasoning down: a short, dated note — "these closets migrate this quarter because of X; these wait because of Y" — turns running unsupported hardware from an oversight into a managed decision.

Your three real options

1. Run on for a while, deliberately. This is legitimate for the low-risk tail, provided it is time-boxed and backed up. Keep a cold spare on the shelf — refurbished 3650s such as the WS-C3650-48PS-S are still readily available — keep a current copy of every running configuration somewhere that is not the switch itself, and tighten management access, because no security fix is coming. What this option cannot do is become the permanent plan by default; set the review date when you choose it.

2. Migrate to the Catalyst 9300L. Cisco's own bulletin maps 3650 part numbers to Catalyst 9300L replacements in its migration table: a 24-port PoE 3650 with 2x10G uplinks maps to the C9300L-24P-4X-A, and a 48-port full-PoE 3650 with 2x10G uplinks maps to the C9300L-48PF-4X-A. Reef stocks both as refurbished units — the C9300L-24P-4X-A and the C9300L-48PF-4X-A — and matching your existing port count, PoE class, and uplink speed to the table is a far safer starting point than re-specifying the closet from scratch. Match the licence tier deliberately too: the migration table's examples land on Network Advantage, so check whether your 3650s were running features that need that tier before ordering an Essentials unit to save the difference.

3. Migrate in waves. For most estates this is the honest answer: option 2 for the closets that failed the triage, option 1 with a fixed end date for the rest. Waves also spread the two real costs of a switch refresh — the hardware spend and the out-of-hours change windows — across quarters instead of stacking them into one painful month.

Planning the swap itself

A 3650-to-9300L change is a like-for-like access refresh, not a redesign, but four checks prevent most of the surprises. Do the PoE maths per closet: count what the phones, access points, and cameras actually draw today, and confirm the replacement's PoE budget covers it with headroom, rather than assuming a 48-port switch powers 48 devices the same way the old one did. Confirm uplinks: if the 3650 used 10G SFP+ uplinks, keep 10G on the replacement (the models above carry fixed 4x10G SFP+ uplinks) and check your existing optics and fibre type still suit. Plan stacking as new work, not a carry-over — budget the stacking hardware for the new platform instead of assuming the 3650 kit transfers. And keep one removed 3650, configured, until each new closet has run cleanly for a few weeks; it is the cheapest rollback plan you will ever have.

Where Reef fits

Reef sells the refurbished 9300L models above with our 10-year warranty, same-day shipping on orders placed by 4 PM EST, and free shipping on orders over $300 — and once a closet is on the 9300 family, ongoing hardware coverage is available through a Reef Support contract for the Catalyst 9300 series, so the replacement platform does not drift toward the same unsupported corner the 3650 reached. If you would like a second pair of eyes on the inventory exercise, send us the product IDs from your closets and we will map each one to its 9300L counterpart from Cisco's table.

Nothing about October 31 makes a healthy 3650 stop working. What the date removed is the safety net — Cisco support, contract renewal, and security remedies are all closed. The right response is neither panic nor indefinite delay: count the estate, triage it honestly, migrate the closets that matter first, and put a date on the rest.