Optical Transceiver Upgrade Checklist: From Port Audit to Deployment-Ready BOM
Plan an optical transceiver upgrade with a practical checklist for auditing ports, fiber, compatibility, quantities, validation and rollout before building the final BOM.
An optical upgrade should not begin with a list of module part numbers. It should begin with a controlled record of every link that will change.
For an ISP, WISP or system integrator, a single upgrade may involve several switch vendors, different port generations, mixed fiber routes, BiDi pairs, spare requirements and phased site access. A module can match the target speed and form factor yet still be wrong for the host, fiber, connector, wavelength direction, optical power window or operating plan.
The practical sequence is:
This guide explains the information to control at each step. It is a project-planning framework, not a substitute for the specifications and compatibility evidence of the exact equipment and transceivers selected.
1. Define What the Upgrade Must Change
Start by separating the business requirement from the proposed optical solution. “Upgrade the network to 25G” or “replace the old optics” does not explain which links need more capacity, why they need it or what must remain in service during migration.
Record the upgrade objective for each affected link:
- Current and target port speed
- Capacity or service constraint being addressed
- Required activation date
- Whether the change is a permanent upgrade, temporary migration or capacity trial
- Whether both endpoints change at the same time
- Required redundancy and acceptable outage window
- Expected growth during the planned service life
- Whether existing fiber, patching and passive components must be reused
Do not assume every link in the project needs the same optical design. A short equipment-room connection, a 20 km access route and a fiber-constrained backhaul path may belong to one commercial project but require different interfaces and validation plans.
2. Audit the Installed Ports Before Selecting Optics
Build the installed-base record from the equipment at both ends of every link. Model names alone are not enough when a chassis supports several line cards or a port supports several operating modes.
| Audit item | What to record |
|---|---|
| Site and link identity | Site A, Site B, link ID, service and rack or panel references |
| Host equipment | Vendor, exact device model, chassis and line card or network interface card (NIC) |
| Software | Current operating-system or firmware version and any planned upgrade |
| Port | Port number, physical form factor, configured speed and supported modes |
| Lane mode | Native interface or breakout arrangement, lane count and remote-end mapping |
| FEC | Current setting and the requirement for the proposed interface, if applicable |
| Installed optic | Original part number, coding profile, wavelength, connector and direction |
| Monitoring | Required digital optical monitoring or digital diagnostic monitoring (DOM/DDM) fields |
| Environment | Indoor or outdoor cabinet, temperature requirement and site-access constraints |
A shared form factor does not prove that a module is supported. Port mode, software, FEC, breakout configuration, coding and monitoring behavior may all affect the result. If the equipment record is incomplete, keep the module selection provisional.
For the detailed information needed before assessing third-party optics, use the optical transceiver compatibility check guide.
3. Build a Link Matrix, Not a Shopping List
The link matrix is the engineering source for the BOM. Give every connection one row and record both endpoints in that row. This prevents a quantity total from hiding an incompatible pair or a missing remote-side module.
At minimum, include:
| Link field | Required information |
|---|---|
| Identity | Link ID, Site A, Site B and service role |
| Interfaces | Host, line card/NIC, port and target speed at both ends |
| Fiber path | Single-mode or multimode fiber, strand count, route length and measured loss when available |
| Connections | Connector type and polish, patch panels, splices and intermediate passive devices |
| Optical design | Interface family, wavelength or wavelength pair and intended reach class |
| Configuration | Breakout, lane mapping, FEC and required port settings |
| Compatibility | Coding target and evidence status for each host |
| Quantity | Working units, remote-end units, samples and approved spares |
| Deployment | Site owner, migration window, validation status and rollback reference |
If the main task is selecting an interface for one backhaul route, the ISP/WISP backhaul optics selection guide provides the deeper speed, fiber, reach and loss decision process.
4. Check the Existing Fiber Plant
An equipment upgrade does not automatically make the existing optical path suitable for the new interface. Inspect the route as part of the design, especially when the target speed, connector architecture or wavelength plan changes.
Confirm:
- Fiber type and, where relevant, installed fiber grade
- Actual route length rather than straight-line distance
- Number of usable strands
- Connector type and polish at every interface
- Patch panels, adapters, splices and intermediate cabinets
- Existing splitters, filters, MUX/DEMUX units or optical add/drop multiplexers
- Measured end-to-end insertion loss when available
- Known contamination, repair or high-loss history
- Whether the proposed design changes simplex, duplex or parallel-fiber requirements
For each proposed module, compare the complete path with its verified transmit-power and receive-power limits. Include applicable passive losses and engineering margin. Check both insufficient received power and potential receiver overload; do not select attenuation from distance alone.
When the existing fiber cannot support the target architecture cleanly, document the alternatives rather than forcing one transceiver choice. Options may include changing the optical interface, changing patching, adding fiber, using a verified BiDi pair or evaluating a controlled WDM design.
5. Separate Optical Fit From Host Compatibility
Every BOM line needs two different decisions:
- Optical fit: Does the proposed pair match the fiber, connector, wavelength, path loss and remote interface?
- Host fit: Does each platform support the module identity and required port configuration?
Use a clear evidence status for each BOM line, for example:
- Specification reviewed
- Coding profile confirmed
- Controlled sample validation required
- Controlled validation completed under recorded conditions
- Field acceptance pending
- Conflict or exception requiring review
Do not convert a supplier statement, a matching form factor or successful recognition in a different platform into a universal compatibility claim.
6. Control BiDi, Breakout and Wavelength-Specific Lines Explicitly
Directional and lane-specific products need more control than a generic quantity total.
BiDi pairs
For single-fiber BiDi links, record the transmit and receive wavelengths at both ends. The modules must be complementary: the transmitter at one end must match the receiver at the other. Keep the pair relationship and site direction in the BOM instead of listing one family name with a combined quantity.
Breakout links
Record the parent port, breakout mode, lane count, cable or fiber assembly and the remote port assigned to each lane. Confirm that both hosts support the intended mode and that the optical and electrical interface requirements align.
CWDM and DWDM channels
Record the wavelength or frequency channel, MUX/DEMUX or add/drop port, direction, passive path and channel-level optical budget. A WDM BOM must include the passive components and their insertion losses; colored optics alone do not define a deployable system.
7. Turn the Link Matrix Into a Controlled BOM
The BOM should preserve the engineering identity of every item while allowing procurement to total quantities. A practical BOM has one controlled version and links each line back to the affected sites and links.
Recommended fields include:
| BOM field | Purpose |
|---|---|
| BOM line ID | Stable reference for changes and approvals |
| Link and site mapping | Shows where each unit will be installed |
| Product identity | Form factor, speed, interface, reach class, wavelength and connector |
| Host coding | Target vendor/platform profile for each endpoint |
| Direction or lane | BiDi end, WDM channel or breakout lane where applicable |
| Quantity type | Production, sample, spare or rollback unit |
| Evidence status | Specification, coding, validation and open limitations |
| Revision status | Added, changed, removed, approved or pending review |
Keep engineering and commercial quantities aligned but separate. A module needed for sample validation is not yet an approved production quantity. A spare is not an extra unnamed unit; it should map to an approved optical and coding identity that the operations team can deploy correctly.
8. Review Quantities by Link, Direction and Project Phase
Counting ports is not always the same as counting modules. A conventional point-to-point link normally needs a module at each end. A BiDi link needs the correct complementary end at each site. A breakout design may need one parent-side assembly and several remote interfaces. A WDM project may require wavelength-specific optics and passive units at several locations.
Use four quantity views:
- Link quantity: What is required to complete every planned connection?
- Site quantity: What must be delivered and labeled for each location?
- Phase quantity: What is needed for pilot, first rollout and later migration stages?
- Spare quantity: Which exact identities need approved operational replacements?
9. Validate a Representative Sample Before Full Rollout
A sample plan should test the configurations that carry the most risk, not merely the easiest link to access.
Choose representative cases such as:
- Each host vendor and relevant platform family
- Each important software or firmware branch
- Each optical interface family
- Each BiDi wavelength direction
- Each breakout or lane configuration
- Each required FEC mode
- The highest-loss or otherwise demanding path class
- Any link with passive WDM components
Record the test configuration and results. Depending on the project, checks may include module recognition, alarms, DOM/DDM visibility, intended port mode, link establishment, traffic, error counters and optical readings. A result from one host and software version should not be presented as proof for every platform in the rollout.
10. Plan the Migration and Rollback
An approved BOM is not yet a migration plan. Before deployment, define the sequence for changing both ends of each link and the conditions for stopping or reverting the work.
The rollout record should identify:
- Change window and responsible engineer
- Site access and remote coordination
- Pre-change configuration and optical readings
- Exact items assigned to the link
- Order of endpoint changes
- Required port-mode or FEC changes
- Acceptance checks
- Failure and escalation criteria
- Rollback modules, configuration and time limit
- Final installed serial or asset references where required
Begin with a controlled pilot when the project contains new platforms, new coding profiles, new optical architectures or difficult-to-access sites. Expand only after the pilot evidence supports the next phase.
Final Optical Transceiver Upgrade Checklist
Before approving the production BOM, confirm that:
- ☐Every affected link has a stable link ID and two identified endpoints.
- ☐Exact hosts, line cards/NICs, ports and software versions are recorded.
- ☐Current and target speeds and port modes are confirmed.
- ☐Breakout, lane mapping and FEC requirements are documented where applicable.
- ☐Fiber type, connector, route length and passive path are recorded.
- ☐Measured loss is included where available; assumptions remain clearly marked.
- ☐Optical power is checked against exact proposed module limits in both directions.
- ☐Host coding and compatibility evidence are tracked separately from optical fit.
- ☐BiDi pairs are complementary and mapped to the correct sites.
- ☐WDM channels and passive components are included in the channel plan and budget.
- ☐Working, sample, spare and rollback quantities are separated.
- ☐Every BOM line maps back to a link, site, direction or lane.
- ☐A representative sample-validation plan is approved.
- ☐Migration, acceptance and rollback steps are documented.
- ☐Open conflicts and unverified items are visible before ordering.
Frequently Asked Questions
What information is required before building an optical transceiver upgrade BOM?
Start with the exact hosts and ports at both ends, current and target speeds, software versions, port and breakout modes, FEC requirements, installed optics, fiber type, connectors, route distance or measured loss, passive components, quantities and rollout timing. Unknown inputs should remain marked for review rather than being replaced with assumptions.
Can the same transceiver be used at both ends of every link?
Not automatically. Conventional duplex interfaces may use the same optical type at both ends, but host coding can differ. BiDi links require complementary transmit and receive wavelengths. WDM and breakout designs may also require direction-, channel- or lane-specific components. Verify both endpoints as a pair.
Is matching the target speed and form factor enough?
No. Speed and form factor do not establish fiber, connector, wavelength, optical-power or host compatibility. Port mode, software, FEC, breakout, coding and monitoring requirements may also affect the deployment.
Should nominal reach be used as the route-loss allowance?
No. Nominal reach is not a substitute for the verified transmitter and receiver limits of the exact module or for an end-to-end loss calculation. Use measured route loss when available and include connectors, splices, passive devices and engineering margin.
How should spare optics be included in the BOM?
List spares by the exact approved product and coding identity they replace. For BiDi, wavelength-specific ends must be stocked and labeled correctly. Set quantities from criticality, installed population, replacement time, site access and interchangeability rather than applying an unsupported universal percentage.
Does a successful sample prove the full rollout is compatible?
Only within the recorded test scope. A sample result supports the specific host, software, port mode, optical path and test conditions used. Additional platform or configuration variants may require separate review or validation.
When should Axonode review the project?
Request a review before the production BOM is locked, especially when the project includes mixed host vendors, BiDi directions, breakout ports, WDM channels, new software, long or high-loss routes, or phased delivery. Early review makes missing inputs and exceptions easier to correct before quantities are committed.
Prepare the Upgrade Information Before Requesting a Quote
The most useful RFQ is not a flat list of “10G” or “100G” modules. It is a controlled link and port record that explains where each item must operate.
Axonode can help organize a mixed optics BOM and review the product identity, coding scope, wavelength pairing and deployment inputs before ordering. Send the equipment and port details for both ends, software versions, target speeds, fiber and connector information, route distance or measured loss, required quantities, site mapping and migration timeline.
For broader product-family and deployment support, see the ISP/WISP backhaul optics solution, or contact Axonode to discuss the upgrade BOM.
