Quick Take
要点速览： Dell Connectrix, HPE B-series, and IBM b-type FC switches are ordering skins of Brocade silicon. Cross-walk each family to a Gen 6, Gen 7, or Gen 8 base before RFQ so port, PoD, optic, and support years stay equal. One OEM path per purchase order; kit codes not on a dated sheet stay pending confirmation.
What Does OEM FC Part-Number Cross-Reference Mean?
速答： Cross-reference means translating an OEM marketing family—DS-7720B, SN6700B, SAN64B-7—into the Broadcom Brocade base such as G720, then rebuilding every quote column to the same ports, licenses, optics, and support years. It is a procurement map, not a claim that kit stickers are byte-identical across OEMs.
Definition: An OEM Fibre Channel SAN switch part-number cross-reference is a buyer worksheet that maps Dell Connectrix, HPE B-series, and IBM b-type family names to the underlying Brocade (Broadcom) platform generation and form factor. The goal is an equal-BOM RFQ: same ASIC generation, same licensed port floor, same optic class, same dual-fabric count, and comparable support years—so LIST or channel deltas are attributable to commercial path, not mismatched hardware.
This page publishes public family aliases (for example DS-66xx / DS-77xx / G610 / G620 / G720 class). Exact kit MPNs such as some Dell 210- director rows or IBM reseller feature codes remain pending confirmation until a dated OEM sheet or quote prints them. Soft channel prices are industry estimate / pending confirmation.
Why Do Equal-BOM RFQs Need a Brocade Base Map?
速答： Without a base map, buyers compare a Dell 24-port G720 kit to an HPE 56/24 string to an IBM machine type and think they priced peers. They did not. Generation traps (SN6600B versus SN3700B) and missing PoD or SFP-DD lines make the cheapest column the wrong ASIC or an incomplete fabric.
Storage contracts often lock the OEM skin—Connectrix with PowerStore, B-series with HPE arrays, b-type with IBM Storage—while CapEx committees still demand three quotes. The only honest comparison starts from the Brocade base model, then re-skins each column. Pair this map with the Gen 7 OEM RFQ lineup when the buy is 64G Gen 7, and with the 64Gb FC SAN BOM checklist when HBAs and array modules must travel with the fabric.
| Failure pattern | What happens | Fix on the RFQ |
|---|---|---|
| Compare OEM stickers only | Different generations or port floors | Write Brocade base + Gen on line 1 |
| Mix OEM kit codes on one PO | Entitlement and spares break | One catalog per purchase order |
| Ignore PoD / SFP-DD | G720 stops at 56 SFP+ ports | Equalize PoD and DD optics |
| Skip TruFOS / optic policy | FOS upgrade or link blocked later | Support years + optic class columns |
Which Dell, HPE, and IBM Families Map to Which Brocade Base?
速答： Gen 6 peers include G610/G620/G630 with DS-66xx and SN6600B-class names. Gen 7 heroes are G710/G720/G730 with DS-7710B/DS-7720B/DS-7730B, SN3700B/SN6700B/SN6750B, and IBM 8969-class machine types. Gen 8 peers are G820/X8 with DS-8820B, SN6800B/SN8800B, and IBM 8634/8635-class families. Kit OPNs stay pending confirmation without a dated sheet.
Use family names below for RFQ language. Kit-level OPNs printed on a dated Dell DS-7700B sheet, HPE QuickSpecs, or IBM machine-type matrix may be attached as evidence; inventing codes is forbidden. SN6600B is Gen 6 G620—not Gen 7 G710 (that entry is SN3700B).
| Generation | Brocade base | Dell Connectrix | HPE B-series | IBM b-type (public) |
|---|---|---|---|---|
| Gen 6 — 32G ASIC class (illustrative families) | ||||
| Gen 6 | G610 | DS-6610B class | SN3000B class | SAN24B-6 class — MTM pending confirmation |
| Gen 6 | G620 | DS-6620B class | SN6600B | SAN64B-6 class |
| Gen 6 | G630 | DS-6630B class | SN6650B class (not G710) | SAN96B-6 / dense class — pending confirmation |
| Gen 6 | X6 directors | ED-DCX6-* class | SN8600B class | SAN256B-6 / SAN512B-6 (8960 family historically) |
| Gen 7 — 64G ASIC class | ||||
| Gen 7 | G710 | DS-7710B | SN3700B | SAN24B-7 8969-P24 |
| Gen 7 | G720 | DS-7720B | SN6700B | SAN64B-7 8969-P64/R64 |
| Gen 7 | G730 | DS-7730B | SN6750B | SAN128B-7 8969-P96/R96 |
| Gen 7 | X7-4 / X7-8 | ED-DCX7-4B / ED-DCX7-8B | SN8700B 4-/8-slot | SAN256B-7 8961-F74 / SAN512B-7 8961-F78 |
| Gen 7 | 7850 extension | MP-7850B | pending official HPE QS | SAN42B-R7 8969-R42 |
| Gen 8 — 128G ASIC class | ||||
| Gen 8 | G820 | DS-8820B | SN6800B | SAN64B-8 8634-class |
| Gen 8 | X8-4 / X8-8 | ED-DCX8-* class | SN8800B | SAN256B-8 / SAN512B-8 8635 family |
Buyer traps: HPE G720 kits often print 56/24 (SFP+ math); Dell/Broadcom write 24 → 64 with SFP-DD required to hit 64. That string is not Gen 8 G820 24/56. IBM 8961 is X7 (Gen 7); 8635 is X8 (Gen 8)—do not mix machine types on one PO. Director empty chassis are not fabrics: blades, ICL, PSU, and fans stay separate lines.
Limitation of this map: it equalizes hardware families for RFQ language. It does not transfer support contracts, TruFOS entitlement, or spare-kit OPNs across OEMs. Cisco MDS estates need a different OS column—see peer MDS guides in Related.
How Do You Cross-Reference OEM FC Part Numbers Before You RFQ?
速答： Freeze generation and port floor first, map every OEM family string to a Brocade base, equalize PoD optics airflow and support years, lock TruFOS and secure-optics policy, then RFQ Fabric A and Fabric B on one OEM catalog only. Attach dated OEM sheets for kit codes; leave blanks pending confirmation.
- Step 1 — Freeze generation and port floor. Write Gen 6, Gen 7, or Gen 8, the licensed port target, and dual independent fabrics on the brief before opening catalogs.
- Step 2 — Map OEM families to Brocade base. Translate DS- / SN- / SAN*B or machine-type strings using the table above. Flag name traps (SN6600B ≠ G710).
- Step 3 — Equalize BOM columns. Align base ports, PoD licenses, SFP+ versus SFP-DD counts, reach class, airflow (FTR/RTF or R/F), power cords, rails, and support years across every OEM you will compare.
- Step 4 — Lock TruFOS and optics policy. Confirm how each OEM renews support for TruFOS certificates and whether Gen 7/8 secure optics are mandatory. Reject third-party SFPs that the policy will block mid-upgrade.
- Step 5 — RFQ one OEM path per PO. Submit mirrored Fabric A and Fabric B packages. Never place HPE SN6700B kits next to Dell DS-7720B
210-rows and IBM 8969 lines on a single purchase order.
What TruFOS and Optics Caveats Break OEM Cross-Quotes?
速答： TruFOS certificates gate Fabric OS upgrades when support entitlement lapses—traffic can keep running while firmwaredownload is blocked. Gen 7 and Gen 8 secure-optics policies can reject mismatched SFPs. Equal-BOM RFQs must price support years and optic class beside every chassis column.
Cross-walking DS-7720B to SN6700B to SAN64B-7 does not merge support contracts. Each OEM serial still needs its own entitlement path for TruFOS XML from the Broadcom support portal (License ID / WWN). See the TruFOS certificate recovery guide before you schedule a dual-fabric FOS window.
- Support years: Quote the same coverage window on every OEM column (for example 36 months) or the “cheapest” column is often under-supported.
- Secure / OEM optics: Gen 7/8 estates frequently require qualified SFP+/SFP-DD SKUs. Third-party optics that link at install may fail policy after a FOS upgrade.
- Speed follows optic + peer: A Gen 7 chassis shipping with 32G factory optics is still Gen 7 silicon—not a Gen 6 G620. Do not relabel it SN6600B.
- SFP-DD on G720/G730: Hitting 64 ports on G720 needs SFP-DD PoD and matching DD optics; SFP+ alone tops out at 56. Equalize that math on Dell, HPE, and IBM columns alike.
真实应用场景
速答： Use the three scenarios below to pick which OEM skin stays locked by the storage contract while the Brocade base and equal-BOM columns stay comparable. Cite the scenario ID on the RFQ so vendors price the same generation and port floor.
Scenario 1: PowerStore + Connectrix dual-fabric refresh
Workload profile: Dell arrays with Connectrix DS-77xx / DS-8820B-class fabrics and a written Gen 7 or Gen 8 target.
Architectural fit: Keep Dell OEM on the PO; still map DS-7720B to G720 (or DS-8820B to G820) so CapEx can dual-quote HPE/IBM skins at equal ports, PoD, and optics without changing ASIC math.
Scenario 2: HPE Alletra / B-series estate equalizing a Dell bid
Workload profile: Production SN6700B / SN3700B inventory; finance asks for a Connectrix alternate.
Architectural fit: Freeze SN6700B = G720 and SN3700B = G710 on the brief. Reject any SN6600B line labeled as Gen 7. Equalize 56/24 versus 24→64 naming before comparing stickers.
Scenario 3: IBM b-type machine-type freeze for mainframe-adjacent SAN
Workload profile: IBM Storage networking with SAN*B families and machine types (8969 / 8961 Gen 7 versus 8634 / 8635 Gen 8).
Architectural fit: Write machine-type generation on line 1. Do not mix 8961 X7 with 8635 X8 on one PO. Cross-walk to G720/X7 or G820/X8 peers only after FICON/CUP requirements are explicit on the quote.
Who Should Use This OEM Cross-Reference — and Who Should Not?
速答： Fit buyers who must compare Dell, HPE, and IBM FC switch quotes for one Brocade generation under a storage-contract OEM skin. Unfit for Cisco MDS-only designs, single-fabric production, or anyone inventing kit MPNs. Also unfit if TruFOS and optic policy will stay undefined through cutover.
- Fit: Equal-BOM RFQs across Connectrix / B-series / b-type; Gen 6→7 or Gen 7→8 refresh committees; dual-fabric bank and hospital cores that need comparable LIST corridors.
- Unfit: MDS NX-OS estates without a Brocade column; Huawei OceanStor SNS-only contracts without a separate SNS map; TGStor channel paths mixed onto a Dell/HPE/IBM PO; grey-market optics with no support plan.
- Decision tree: If the storage contract locks one OEM → map peers for CapEx only, order the locked skin. If CapEx is OEM-agnostic → pick one catalog after the equal-BOM table, then freeze airflow and optic SKUs.
常见问题
速答： DS-7720B peers G720; SN6700B peers G720; do not mix OEM kits on one PO. SN6600B is Gen 6 G620, not G710. TruFOS and optic class belong on every equal-BOM column. Send family strings and port floor to TAOHAN for a dual-fabric risk review.
Same Gen 7 ASIC class, different ordering skin. DS-7720B is the Dell Connectrix marketing family for G720. Quote one OEM path, matching ports, PoD, optics, and support years—do not treat the strings as interchangeable kit codes on one PO.
No. Both map to G720-class silicon, but catalog lines, serial entitlement, and spare kits stay OEM-specific. Mixing R7M / SN6700B kits with Dell 210- / DS-7720B rows creates two POs pretending to be one fabric order.
Expired support can block TruFOS certificates and FOS upgrades even when traffic still runs. Gen 7/8 secure-optics policies can reject mismatched SFPs. Equal-BOM columns must include support years and optic class, not chassis stickers alone.
No. SN6600B maps to Gen 6 G620. Gen 7 entry is SN3700B for G710 and SN6700B for G720. Mislabeling SN6600B as Gen 7 breaks PoD, optic, and FOS assumptions on the RFQ.
Send the OEM family strings, target generation, port floor, and optic/reach matrix via 提交 BOM / Contact TAOHAN or email info@021taohan.com. You receive a dual-fabric equal-BOM package from a global free-port hub.
参考资料
速答： Verify family aliases against Broadcom Brocade product pages, Dell Connectrix datasheets, HPE B-series QuickSpecs, and IBM b-type machine-type documentation before freezing kit OPNs. This page is a procurement map only; dated OEM PDFs remain the authority for exact codes and machine-type feature strings.
- Broadcom — Brocade G720 switch product page — Gen 7 mid-range base used as the G720 cross-walk anchor
- Dell — Connectrix DS-7700B / DS-7710B spec sheet — public Connectrix DS-77xx family documentation
- HPE Store — SN6700B (G720) product page — B-series SN6700B QuickSpecs / Store path
- IBM — b-type SAN switch and Broadcom product matrix — machine-type to Broadcom family map
Key Takeaway
核心结论： Start every multi-OEM FC RFQ from the Brocade base and generation, then re-skin Dell, HPE, or IBM columns with equal ports, PoD, optics, and support years. One OEM catalog per PO. TAOHAN supplies Connectrix, HPE B-series, and IBM b-type FC switches with competitive pricing for equal-BOM dual-fabric packages.