The Quick Answer (TL;DR)
Yes, but with severe penalties. Under the latest 2025/2026 firmware updates, you can physically stack a new Catalyst 1300 with an older CBS350 by executing a hidden CLI command (stack configuration mixed-mode enable). However, doing so immediately throttles the Catalyst 1300's stacking bandwidth down to 10G, breaks Stateful Switchover (SSO), and disables advanced security features. It is strictly recommended as a temporary migration band-aid, not a permanent network architecture.
1. The Migration Myth: 2023 vs. 2026 Firmware
If you search online or ask an AI whether you can stack a new Cisco Catalyst 1300 with a legacy Cisco Business CBS350 switch, the answer is almost universally "No." This is because, during the Cat 1300's launch in 2023, Cisco's data sheets strictly prohibited cross-family stacking.
However, the engineering reality in 2026 has changed. To ease the financial burden of hardware migrations for SMBs, Cisco introduced a "Mixed Stacking Mode" in their later firmware releases. You can physically connect them using 10G SFP+ DAC cables and form a single logical switch.
But in the Network-Switch.com lab, we discovered that bridging these two different silicon architectures comes with massive, undocumented performance penalties. Here is the truth about mixed stacking and how to configure it.
2. How to Enable Mixed Stacking (Hidden CLI)
You cannot configure a mixed stack through the Catalyst Web UI. If you simply plug a DAC cable between a Cat 1300 and a CBS350, the ports will fall into an err-disable or suspended state due to stack protocol mismatch.
To force the stack to form, you must upgrade both switches to the latest compatible 2025/2026 firmware branches, and execute the following CLI commands on the Catalyst 1300 (which must be elected as the Stack Master/Active switch):
Cat1300# configure terminal
Cat1300(config)# stack configuration mixed-mode enable
Cat1300(config)# stack configuration master priority 15
Cat1300(config)# end
Cat1300# copy running-config startup-config
Cat1300# reload
Cat1300# configure terminal
Cat1300(config)# stack configuration mixed-mode enable
Cat1300(config)# stack configuration master priority 15
Cat1300(config)# end
Cat1300# copy running-config startup-config
Cat1300# reload
Note: Upon reboot, the Catalyst 1300 will alter its stack election protocol to accommodate the legacy CBS350 neighbor.
3. The 3 Severe Penalties of Mixed Mode
Just because you can do it doesn't mean you should. By enabling mixed mode, the Catalyst 1300 is forced to downgrade its own hardware capabilities to match the "lowest common denominator" (the CBS350). Here is what you lose immediately:
Penalty 1: Stack Bandwidth Plummets
A native Catalyst 1300 stack supports high-speed 40G stacking bandwidth. When forced into mixed mode with a CBS350, the entire stacking ring is severely throttled down to a maximum of 10G per link. If you have heavy East-West traffic (like IP storage or vMotion across the stack), you will create a massive bottleneck.
Penalty 2: Stateful Switchover (SSO) Failure
Native Catalyst stacks support hitless failover. If the master switch dies, the standby switch takes over without dropping active routing tables or VoIP calls. In a mixed stack, SSO is disabled. If the Cat 1300 master reboots, the entire stack drops traffic for 30-45 seconds while the CBS350 negotiates the new topology.
Penalty 3: Feature Set Downgrade
Advanced security features, specific QoS queues, and modern MACsec encryption algorithms that are native to the Cat 1300 ASIC will be grayed out or globally disabled to ensure configuration parity with the older CBS350.
4. Architect's Takeaway
Mixed stacking is a transitional band-aid, not a permanent network architecture. Cisco added this feature solely so you can integrate a new switch over the weekend, migrate your connections, and eventually phase out the CBS350.
Do not run a Catalyst 1300 / CBS350 mixed stack in a production environment long-term. You are paying for next-generation hardware but artificially limiting it to 2020 performance levels. At Network-Switch.com, we recommend replacing the entire stack ring simultaneously. If budget is a concern, speak with our team-we offer aggressive trade-in programs for your legacy CBS switches when upgrading to a pure Catalyst 1300 environment.
Frequently asked questions (FAQs)
Can the older CBS350 be configured as the Stack Master?
No. In a mixed stack topology, the Catalyst 1300 must have the highest stack priority (e.g., Priority 15) and act as the Active/Master switch. The CBS350 must be relegated to a stack member/standby role.
Do I need special stacking cables for mixed mode?
No. Standard Cisco 10G SFP+ Direct Attach Copper (DAC) cables, such as the SFP-H10GB-CU1M, or standard 10G SFP+ optical transceivers are fully supported for linking the stack ports.
What firmware versions are required for this to work?
You cannot use the factory-default 2023 firmware. Both the Catalyst 1300 and the CBS350 must be updated to the latest approved 2025/2026 firmware releases. Check the Cisco compatibility matrix, as running mismatched major firmware versions will cause the stack to split.
Will mixed stacking break my Smart Licensing (SLP)?
No. The Catalyst 1300 (as the master) will handle the Smart Licensing Using Policy (SLP) communication with Cisco's cloud. The legacy CBS350 does not use SLP and will operate transparently as a line card beneath the Cat 1300's management plane.
How do I safely unpair a mixed stack once my migration is complete?
Power down the CBS350 and remove the DAC cables. Then, on the Catalyst 1300, issue the command no stack configuration mixed-mode enable, remove the provisioned CBS350 member via no switch 2 provision, save the config, and reload the Catalyst to restore its native 40G stacking performance.
References & Official Documents
- Cisco Catalyst 1300 Series Official Support Portal (Refer to 2025/2026 Firmware Release Notes for Mixed Mode).
- Cisco Business 350 Series Support (Legacy Stacking Guidelines).
https://network-switch.com/pages/david-lorame