Selecting and commissioning a switch with optics in mind
Optics are where a switch project meets reality: the box is chosen for ports, features and price, and then a module that "should work" does not, the uplink cage cannot power the 40 km optic, the airflow is backwards for the rack, or the first software upgrade errdisables half the links. This page is two checklists — what to check about optics when selecting a switch, and how to commission it from unboxing to a DDM baseline — plus an acceptance test that catches marginal links before users do.
Selection criteria
| Criterion | Question to answer | Where the answer lives |
|---|
| Port count and speeds | how many downlinks at which speed, how many uplinks, growth for 3–5 years | design (Roles & topologies) |
| Oversubscription | downlink ÷ uplink capacity acceptable for the traffic | Ports & uplinks |
| Cage generations | SFP28 vs SFP56, QSFP28 vs QSFP-DD/OSFP; which older modules the cages accept | Port types & cages |
| Speed and breakout rules | port groups, which ports break out, 1G support in SFP+ cages, QSA | hardware installation guide |
| Optics policy | strict OEM, list-checking, permissive; documented override; effect of upgrades | How each NOS validates a module |
| Supported-optics list | are the PMDs you need (LR, ER, BiDi, CWDM, DWDM tunable, 100G ZR) on the platform's list | Compatibility matrices |
| Cage power budget | class per port; ZR/tunable/10GBASE-T SFP+ support | Power & consumption |
| Airflow direction | port-side intake or exhaust SKU matching the rack | Switch classes |
| Environment | ambient range; industrial grade needed? | Temperature grades |
| Forwarding features | L2/L3, VXLAN/EVPN, MLAG, PFC/ECN for storage/AI | Forwarding basics |
| Stacking / pairing | stack cables or front-port VCP; MLAG peer-link ports consumed | Stacking & MLAG |
| Management | OOB port, console type, APIs, telemetry for DDM, SNMP MIBs | Management & monitoring |
| Software lifecycle | release cadence, LTS trains, ISSU, end-of-support dates | vendor lifecycle pages |
| Support model | what the vendor supports with third-party optics; TAC stance | contract |
| Total cost | switch + licences + optics (often 30–60 % of the port cost at 100G+) + power + spares | BOM |
| Redundancy | PSUs, fans, supervisors; uplinks on different modules | Switch classes |
Optics bill of materials
| Item | Count rule |
|---|
| Downlink DAC/AOC | one per server port, length by rack position (1/2/3 m) |
| Uplink modules | 2 × (uplinks per switch) — both ends |
| Breakout cables | per split port; MPO trunks and cassettes for parallel optics (Breakout & MPO) |
| Stack / peer-link cables | per pair or ring |
| Management | 1G copper or LX per switch to the OOB network |
| Spares | 5–10 % per type, at least 2 of each; more for long-lead items (ER, DWDM) |
| Cleaning and test | one-click cleaners, inspection scope, light source/power meter, a reference module per type |
Commissioning checklist
- Unbox and inspect — serial numbers, PSUs, fan trays, airflow SKU, uplink modules; photograph the faceplate.
- Inventory the optics — read every module on the bench (vendor, PN, SN, date, compliance, power class, firmware) and record it against its planned port (Check transceiver, Code database).
- Console in — set the management IP on the OOB port and VRF, credentials, NTP, syslog, SNMP/telemetry targets (Management & monitoring).
- Software — upgrade to the target release before configuring ports; read the release notes for transceiver items (Compatibility matrices & firmware).
- Policy lines —
service unsupported-transceiver / allow-unsupported-transceiver / transceiver phony-alarm-disable if the fleet needs them; errdisable recovery. - Port configuration — speeds, FEC, auto-negotiation (on for DAC, off for optics), breakout maps, descriptions, LAG/MLAG membership (Port configuration recipes).
- Insert modules — clean every connector, insert with the bail open, listen for the latch; DAC/AOC pull tabs upward on dual-row cages as the guide says.
- Verify each port — module recognised, correct type string, link up at intended speed, FEC counters zero (Verifying optics on a switch).
- Baseline DDM — record Rx/Tx power, bias, temperature per port ("link passport"); compare Rx to the budget (Monitoring, Rx power & budget).
- Acceptance test — see below.
- Document — port map, optics inventory with serials, cable IDs, photos, config backup; label both cable ends.
- Spares on site — stored in ESD bags, dust caps on.
Acceptance test
| Test | Method | Pass |
|---|
| Link stability | monitor carrier-transitions / flap counters for 24 h | zero flaps |
| Error-free | CRC/FCS and FEC uncorrectable counters after 24 h of traffic | zero uncorrectable; corrected FEC stable, not climbing |
| Throughput | iperf/TRex between hosts across each uplink (or LAG member pinned) | ≥ 95 % of line rate |
| Power margin | Rx power vs sensitivity per link | ≥ 3 dB margin (≥ 2 dB for SR on MMF) |
| Temperature | module DDM temperature at full fan speed and at normal | below high-warning with ≥ 10 °C margin |
| Failover | pull one uplink / one PSU / one stack cable | traffic continues, alarms raised, restores cleanly |
| Redundant-path check | shut one MLAG peer / spine | ECMP/LAG reconverges within design time |
| Management | SNMP walk of transceiver objects, telemetry subscription, syslog receipt | data arrives for every port |
Common commissioning mistakes
| Mistake | Consequence | Fix |
|---|
| Configuring ports before the software upgrade | policy or syntax changes on upgrade | upgrade first |
| Mixed airflow SKUs in one rack row | hot optics on the reversed box | order matching SKUs |
| 40 km / ZR module in a cage rated class 4 | module stays in low power | check budgets (Power & thermal) |
| AN left on for optics, off for DAC | link down with good levels | FEC & AN |
| No cleaning before insertion | marginal Rx from day one | clean and inspect |
| Third-party optics untested on the platform/release | errdisable on a Friday | test one of each first (Third-party optics) |
| No DDM baseline | later degradation invisible | record the passport |
| Unlabelled cables and undocumented breakout children | hours lost in every incident | label and document (Port naming & LEDs) |
In CodingBox
Step 2 of the commissioning list is the bench: reading every module before it is racked produces the inventory, catches wrong PMDs and mislabelled parts, and — where the platform demands it — is the moment to code identities so that step 8 passes on the first try (Check transceiver, EEPROM editor).