BladeCenter carrier compatibility record
========================================
Source: https://yenra.com/bladecenter/carrier-blade.html
Updated: September 16, 2026

Save a private copy and fill in the fields. Use unknown for unverified items.
Keep evidence references and observations separate from assumptions.
This record is a planning aid; use model-specific manuals for service.

Inspection or trial date: ____________________
Record owner: ____________________

Chassis machine type, firmware, power and cooling configuration:
________________________________________________________________

Management module identity and firmware:
________________________________________________________________

Carrier part number, board revision and firmware:
________________________________________________________________

For each bay: module part number, revision, dimensions and role:
________________________________________________________________

PCIe lanes, root complex/endpoint roles and Ethernet path:
________________________________________________________________

Required telecom clocks and documented connections:
________________________________________________________________

Power and thermal limits from applicable manuals:
________________________________________________________________

Management, OS, driver and application versions:
________________________________________________________________

For each compatibility claim: document, revision, page, date checked:
________________________________________________________________

Result per claim: supported / conflicting / unknown:
________________________________________________________________

Known working configuration and exported records:
________________________________________________________________

Authorized service procedure and recovery route:
________________________________________________________________

Planned acceptance task and success evidence:
________________________________________________________________

Unresolved dependencies, next action and responsible person:
________________________________________________________________