Home › Spotlights
Cisco switches — Catalyst and Nexus sourcing
The spotlight page for the desk's most-quoted line: Cisco switching from access-layer Catalyst models to Nexus data centre fabrics.
Access, core and fabric in one list
Cisco switch BOMs usually span three layers at once — Catalyst 9200L-class access switches, Catalyst 9500-class core, and Nexus 9300 fabric switches — and the desk prices them as one list. The models we list (C9200L-24P-4X-E, C9500-24X-E, the Nexus N9K-C9336C-FX2) lead this page; other Catalyst and Nexus strings are quoted from the same ranges.
Include optics and stacking or breakout cables on the same BOM. A switch list without its transceivers is half a design, and the quotation is the moment to catch it.
Reference models buyers ask about
- C9200L-24P-4X-E
- C9500-24X-E
- C1300-24FP-4G
- N9K-C9336C-FX2
Send the part number and quantity for a line price.
How a Catalyst list gets priced
Send the list as model strings, one per line, with a quantity and a destination city. Each string is checked as written — family, port count, uplink module, PoE class — because on Catalyst ranges the suffix decides the price more often than the headline model does. Lines that read cleanly are priced; lines with a gap, such as an uplink choice the BOM leaves open, come back with the choice named rather than silently assumed.
Licensing is handled as its own pass. Where the design names a software tier, that tier is priced with its switch; where the BOM is silent, the quotation states which tier, if any, its price carries. That single line is what keeps a switch order from arriving short of what the network design expected to run.
Checking the design, not just the models
A switch list is a design wearing a spreadsheet. Stack counts have to match the closets they serve, uplink speeds have to match the core they feed, and PoE budgets have to cover the phones, cameras and access points hanging off each access switch. When the list itself shows a junction that does not close — an uplink slower than the access layer below it, a budget thinner than the device count — the quotation flags it instead of pricing the problem through.
That flagging is part of the service, not an upsell: the buyer keeps full control of the design, and the desk's job is to make sure what was priced is what the design meant. Flags arrive attached to the line they belong to, so a project engineer can answer them one by one.
Mixed generations and shelf spares
Few real estates are single-generation. A list that mixes earlier Catalyst families with current ones is priced line by line without penalty — continuity orders are a normal shape here, and each string is checked against its own family's variants rather than forced into a current-range mould.
Spares deserve their own lines in the same order: a shelf spare for each switch class in the design, the stacking cables the stacks assume, and spare power supplies where the design runs redundant power. Bought with the main order, spares consolidate into the same shipment at the same freight logic instead of arriving as expensive singletons later.
Common questions
Can you price a mixed Catalyst + Nexus BOM?
Yes — that is the standard shape of a Cisco switch inquiry here.
What about licence suffixes?
Copy them into the inquiry exactly; licence and power suffixes change the quoted variant.
What should a Cisco switch inquiry include?
Exact model strings, a quantity per line, named licence tiers where the design fixes them, and a destination city. Accessory lines — modules, stacking cables, optics — belong on the same list.
Can spares be quoted separately from a switch rollout?
Yes — send the installed model strings and the spare quantities wanted; spares are priced as their own quotation when the rollout is already placed.