A spares check for the new year: what's on the shelf, and is the coding still right?
Yearly spares check per site: count your spare optics, check coding after upgrades and hardware swaps, test them and review your SLAs. With a printable checklist.
It's the last week of the year. Somewhere in your Amsterdam rack there's a box of spare optics. Are you sure what's in it, and that your switch still accepts them? Here's a printable checklist for a yearly spares check per site: count, check coding, test, label, and line up your SLAs and budget for next year.
Why once a year
In October we wrote about what to have ready when a transceiver dies at 4 pm. You make that plan once. But a network doesn't stand still for a year, and your spares box ages with it. A few things that happen in twelve months:
- Spares got used and not replaced — someone took one out in March for an incident. Nobody ordered a new one.
- There's new hardware — a switch was replaced, an uplink went from 10G to 25G. The spares for the old ports are still there, the ones for the new ports aren't.
- The coding no longer fits — more on that below.
- Contracts expire — maintenance contracts, SLAs and delivery agreements have an end date.
New year is a logical moment: budgets restart, and it's usually quiet enough to open a rack.
Coding drift
CodingCoding The vendor identification in a transceiver's EEPROM. Many switches only accept optics coded for their own brand. lives in the transceiver's EEPROM: vendor name, vendor OUI, part number and serial number, as defined in SFF-8472. Your switch reads it and decides whether to accept the optic.
Coding drift is what we call the point where your spares and your platform have grown apart. It happens in three ways:
- Hardware swap — you installed a switch from a different brand. Your spares still carry the old brand's coding. They fit the port and do nothing.
- Different platform, same brand — not every optic is supported on every platform. Vendors publish per-platform compatibility matrices for exactly this reason.
- Firmware upgrade — which optics a platform supports is tied to the software release. Cisco's matrices list a minimum software release per platform, and whether DOM is supported. After a major upgrade it's worth trying your spares again.
There are tricks to make a switch accept unknown optics. We deliberately don't name them here: at 4 pm you want a spare that just works, not a configuration you have to remember first.
Test, don't just count
Counting tells you how many there are. Testing tells you whether they work. Plug each spare into the equipment it's meant for once, check that it's recognised and read the DOM values: temperature, Tx power and bias current should look normal.
Record the serial number while you're at it. It's stored in the EEPROM, so you can read it on your switch and tie your list directly to what's in your ports. A spare you can't find on your list doesn't exist as far as your incident plan is concerned.
Labels and a list per site
A box labelled "spares" is not an inventory. Per site, you want a list with, for each spare: type and form factor, reach and wavelength, coding (for which platform), serial number, date of the last test, and the matching patch cords. Put a label on the box that points to that list.
Checklist: spares check per site
- Count all spare optics, DACs, AOCs and patch cords per site.
- Compare the list with what's in your racks now: types, speeds and platforms.
- Check per spare that the coding matches the current platform.
- Check your vendor's compatibility matrix after firmware upgrades to confirm your optics are still supported.
- Test every spare in the target equipment and read DOM.
- Record the serial number and test date per spare.
- Replace used spares and order spares for new port types.
- Label the box and record the list in your incident plan.
- Check the end dates of your maintenance contracts, SLAs and delivery agreements.
- Reserve budget for top-ups, replacements and new platforms in the coming year.
What to do now
Print the checklist, book an hour per site in the first weeks of January and work through it. If spares turn out to be missing or the coding no longer fits, we deliver optics and cables with the right coding, same day in Amsterdam.
Rather not keep track of this yourself? With a Recovery Kit, a set of spare modules and cables sits at your site, with an emergency delivery agreement included. With a Stand-by SLA, an engineer is at your rack within 4 hours during agreed time windows. You'll find both on our services page, and if you're reviewing next year's contracts anyway: now is the time.

Founder of FiberNxt and Xyphen IT
Yvan Watchman is the founder of FiberNxt and Xyphen IT. He has been building and running networks and data centre infrastructure in and around Amsterdam for years.
Related products and services
Frequently asked questions
How often should I check my spares?
At least once a year per site, plus after every hardware swap, every change of switch vendor and every major firmware upgrade. A fixed yearly check around new year works well, because budgets and contracts restart then too.
What is coding drift?
That's our name for spares that no longer match what's in your rack. You still have SFP+ modules coded for your old switch vendor, but a different brand is installed now. They fit physically, but your switch won't accept them. You find out when you need them.
Can FiberNxt resupply my spares with the right coding?
Yes. Tell us which platforms you run per site and we'll deliver optics with the matching coding. With a Recovery Kit they're ready on site, with an emergency delivery agreement included.