Quick Take
要点速览： Ports on Demand (PoD) enables unused Fibre Channel cages after a lower base count. Day-one CapEx is often lower than a fully populated kit, but total cost depends on later PoD buys, matching optics, and support years. G720 needs SFP-DD PoD to hit 64 ports. No invented PoD list dollars — soft quotes pending confirmation.
What Ports on Demand Licensing Is
速答： Ports on Demand is a paid entitlement that turns on physical cages already present in a fixed switch or director. The chassis ships with a base port count; PoD kits raise the enabled count in published increments. PoD is not an SFP, not TruFOS, and not a support renewal — those remain separate BOM lines.
Definition: A Brocade Ports on Demand (PoD) license is a commercial entitlement that enables unused Fibre Channel port cages on a switch or director that already contains the physical hardware. Buyers pay for a base configuration (for example eight or twenty-four enabled ports) and add PoD kits when growth arrives. Directors also sell ICL PoD kits that unlock Inter-Chassis Link capacity separate from device-port blades.
OEM skins — Dell Connectrix, HPE B-series, IBM, Lenovo, Hitachi, and channel product names such as TGStor — sell the same ASIC families under different PoD part numbers. Same generation does not make those SKUs interchangeable on one purchase order. Enterprise software bundles (Fabric Vision, Trunking, Extended Fabric, Integrated Routing, and FICON CUP where published) often ship included on OEM kits; do not repurchase them, but still line-item PoD, TruFOS, and support years.
- Fit this page: Fixed Gen 7 / Gen 8 FC switch RFQs, director ICL growth, dual-OEM quotes that mix base kits with PoD increments, or budgets that compare day-one CapEx to multi-year TCO.
- Boundary: Inventing PoD list dollars; treating PoD as free optics; claiming G720 64 ports on SFP+ only; pasting BSN November hardware percents onto OEM PoD SKUs without confirmation.
For the full Gen 7 hardware map, use the Gen 7 OEM RFQ lineup. For channel-book percentage moves that mention POD kits as a hardware class, see the BSN November 2026 price notice — that sibling is a percent book, not a PoD dollar table.
How Does PoD Compare to Fully Populated Ports?
速答： Fully populated kits light more ports on day one and simplify optic planning. PoD kits defer CapEx until growth is real, but later PoD plus optics plus support can close or reverse the gap. Score both paths on lit-port need, optic inventory, and renewal cliffs — not on a single chassis sticker. Dollar deltas stay pending confirmation.
Procurement teams often treat “PoD” as a discount switch. The accurate comparison is total FC SAN cost across CapEx timing, optic inventory, and support coverage years. A base-plus-PoD path wins when growth is uncertain and unused cages would sit dark for years. A fully populated path wins when the fabric must light near-max ports in the first maintenance window, or when finance refuses mid-contract true-ups.
| Dimension | Ports on Demand path | Fully populated path |
|---|---|---|
| Day-one CapEx | Usually lower — base ports + selective PoD | Usually higher — more enabled ports up front |
| Growth flexibility | Add PoD kits in published increments | Already lit; growth needs another chassis or blade |
| Optics risk | High if PoD buys omit matching SFPs | Lower if factory kits include optics for lit ports |
| Support / TruFOS cliff | Renewals may follow enabled entitlement growth | Coverage sized to the full kit earlier |
| Admin / change risk | More PO events; entitlement must match cages | Fewer license events; larger unused inventory risk |
| Best fit | Phased edge growth, uncertain host count | Known dense attach in first 90 days |
| Price evidence | Qualitative; official book pending confirmation | Qualitative; official book pending confirmation |
Limitation of this comparison: it does not publish PoD SKU list prices or channel net. Soft corridors without a dated seller book are industry estimates only. Re-run the table when the OEM or BSN book changes — for example when a channel notice moves G720/G820 plus POD or X8 ICL POD as a hardware class.
Worked example — PoD vs full-port CapEx shape (industry estimate)
Illustrative dual-fabric G720 estate: need 40 lit ports today, plan 64 lit ports at month 18. Numbers below are not list prices — they are relative cost units (CU) used only to show shape. Replace every CU with the seller’s dated book before CapEx freeze. All figures: industry estimate / pending confirmation.
| Path | Day-one (40 lit) | Growth to 64 | Indicative total CU |
|---|---|---|---|
| PoD path | Base 24 + PoD to ~40 + optics for 40 | Later SFP+ / SFP-DD PoD + optics for +24 | ~100 CU day-one → ~145–160 CU after growth |
| Fully populated path | Near-max enabled kit + optics for 40–64 | Mostly optic fill; fewer license events | ~130–150 CU day-one → ~140–155 CU after growth |
- Read the shape: PoD often wins day-one CapEx (~15–30% lower CU in this sketch) but can close to parity once SFP-DD PoD, matching DD optics, and support true-ups land.
- G720-specific cliff: the jump from 56 (SFP+) to 64 (SFP-DD) is a separate entitlement + optic class — omit it and acceptance fails even if CU looked cheap.
- Do not paste CU into a PO. Request official PoD / optic / support lines; mark soft corridors pending confirmation.
Why Optics Plus PoD Create BOM Traps
速答： A lit port needs three things: PoD entitlement, a compatible optic, and a peer that negotiates the same speed. Buying PoD without optics leaves dark cages. Buying 64G optics without SFP-DD PoD on a G720 leaves you stuck at 56 SFP+ ports. Count cages, licenses, and optics on separate rows.
The most expensive PoD mistakes are not the license line itself — they are mismatched optics and wrong generation math. Gen 7 G720 hardware is forty-eight SFP+ cages plus eight SFP-DD cages. SFP+ alone reaches fifty-six ports. Reaching sixty-four requires SFP-DD PoD and matching SFP-DD optics. Gen 8 G820 fixed-switch math is commonly written as twenty-four base scaling toward fifty-six on SFP+ PoD without the G720-style sixty-four via SFP-DD. Mixing “24/64” and “24/56” strings on one PO mis-orders both licenses and optics.
| Platform | Base → max (published scale) | PoD / optics trap |
|---|---|---|
| G710 | 8 → 24 (two 8-port SFP+ PoD) | No SFP-DD; single fixed PSU — do not plan dual-PSU HA |
| G720 | 24 → 64 (56 on SFP+; 64 needs SFP-DD PoD) | Claiming 64 without SFP-DD PoD + DD optics fails acceptance |
| G730 | 48 → 128 (SFP+ PoDs + SFP-DD PoD) | Order of PoD kits can vary; still need DD optics for DD ports |
| G820 (Gen 8) | Fixed mid-range; PoD with chassis on commercial books | Do not paste G720 24/64 language onto G820 24/56 math |
| X7 / X8 directors | Blade ports + separate ICL PoD kits | Enterprise bundle ≠ free ICL PoD; ICL optics class differs by generation |
Factory kits that include optics for the base count still leave growth ports dark until you buy both PoD and optics. Spare SFP inventory should track the enabled plan, not the empty cage count. For equal-BOM speed strategy across HBAs and arrays, pair this page with the 64Gb FC SAN BOM checklist.
How Do Renewal Cliffs Change After PoD Growth?
速答： Support and TruFOS renewals often follow the covered or enabled configuration. Enabling a large PoD block mid-contract can raise the next renewal even when day-one CapEx looked cheap. Freeze support years and entitlement on the RFQ. Soft renewal dollars remain pending confirmation on the OEM or BSN book.
PoD is a CapEx lever; renewals are an OpEx cliff. When the fabric grows from a twenty-four-port base to fifty-six or sixty-four enabled ports, coverage language may track the larger entitlement. Buyers who only compare chassis stickers miss the renewal step-up. TruFOS certificate and Active support calendars are separate from PoD kits — do not assume a PoD PO extends support years automatically.
- Write the renewal clock: support end date, TruFOS status, and whether coverage is per chassis serial or per enabled ports.
- Align PoD growth windows: if a large PoD buy lands ninety days before renewal, ask whether the renewal prices the new entitlement immediately.
- Separate channel books: a Broadcom BSN percent move on POD hardware classes is not an automatic OEM PoD price change — pending confirmation per seller.
- Avoid double-pay: Enterprise software bundle inclusion does not remove the need to quote TruFOS and support years.
Portal entitlement hygiene still matters before you open cases after a growth event. Use the BSN register and upgrade access guide when the support path is Broadcom-aligned, and the TruFOS certificate guide when certificate cliffs sit next to PoD growth.
Who Should Choose PoD versus Fully Populated?
速答： Choose PoD when host and array attach will grow over twelve to twenty-four months and unused cages would sit dark. Choose fully populated when dense attach is certain in the first maintenance window. Unfit: buyers who need a public PoD price table on this page, or who mix OEM PoD SKUs on one PO.
Decision rule: if more than about half of the cages will stay dark for a year, PoD usually wins on CapEx timing — provided you budget optics and renewal true-ups. If the fabric must light near-max ports for a storage refresh in ninety days, fully populated kits reduce license events and optic mismatches. Directors almost always need an explicit ICL PoD plan; empty chassis hope is not a fabric.
- Fit PoD: Phased VMware / database host growth; dual-fabric edge switches with uncertain ISL count; CapEx gates that forbid buying unused ports today.
- Fit fully populated: Known dense array refresh; acceptance tests that require max port count; finance that blocks mid-year license POs.
- Unfit this page alone: Need for published PoD list dollars; Cisco MDS-only estates; Huawei SNS-only quotes; inventing TGStor PoD MPNs not on the dated OEM sheet.
How to RFQ an FC SAN BOM with PoD Lines
速答： Six steps: freeze lit ports now and at twelve to twenty-four months, map platform PoD scale, split chassis / PoD / optics / support columns, verify SFP-DD entitlement, compare qualitative TCO without inventing dollars, then RFQ each OEM book separately.
- Step 1 — Freeze lit ports today and at 12–24 months. Count array front-end FC ports, host initiators, ISLs, and planned growth. Separate must-light-now ports from optional growth cages.
- Step 2 — Map platform PoD scale. Write G710 8 to 24, G720 24 to 64 with SFP-DD for 64, G730 48 to 128, G820 24/56 math, and director ICL PoD kits as their own class.
- Step 3 — Split BOM columns. Create columns for chassis base, PoD kits, optics by speed and reach, TruFOS, and support years. Do not merge PoD into a single hardware lump.
- Step 4 — Check SFP-DD versus SFP+ entitlement. Before claiming max ports, confirm whether the last increment needs SFP-DD PoD. Reject quotes that claim G720 64 ports on SFP+ only.
- Step 5 — Compare day-one PoD CapEx versus full-populate TCO. Score CapEx timing, optic inventory risk, and renewal cliffs qualitatively. Mark any soft dollar corridor as industry estimate / pending confirmation.
- Step 6 — RFQ OEM books separately. Quote Dell, HPE, IBM, Hitachi, TGStor, and BSN PoD lines on separate columns. Never mix OEM PoD SKUs on one purchase order. Send the split BOM for a compatibility and delivery risk assessment.
真实应用场景
速答： Three common estates: phased edge growth on G710/G720, director ICL PoD expansion, and dual-OEM PoD versus full-populate bake-offs. Map your workload to one scenario before freezing CapEx so equal-BOM RFQs stay comparable across lit ports, optics speeds, and support years.
Scenario 1: Phased Edge Growth (CapEx Bound)
Workload Profile: Two fabrics of mid-range switches start at twenty-four enabled ports while host clusters grow over eighteen months.
Architectural Fit: Base kit plus scheduled PoD increments; pre-buy only the optics needed for the next growth wave; document SFP-DD need if the target is G720 at sixty-four ports.
Scenario 2: Director ICL Expansion (Scale Bound)
Workload Profile: X7 or X8 directors add a second chassis or raise ICL bandwidth after device-port blades are already lit.
Architectural Fit: Line-item ICL PoD separately from Enterprise software; match ICL optic class to generation (QSFP vs OSFP); do not treat included fabric features as free ICL entitlement.
Scenario 3: Dual-OEM Bake-Off (Commercial Bound)
Workload Profile: Procurement compares Dell Connectrix, HPE B-series, and a channel product path on the same ASIC generation.
Architectural Fit: Equal lit-port count, equal optic speeds, equal support years; keep PoD SKUs in separate columns; never merge OEM part numbers onto one PO to chase a fake delta.
Common PoD Procurement Pitfalls
速答： Avoid treating PoD as free ports, claiming G720 64 without SFP-DD, buying optics without entitlement, mixing OEM PoD SKUs, ignoring renewal step-ups, and inventing list dollars. Enterprise bundle inclusion does not remove TruFOS or support line items from the RFQ.
- PoD without optics. Entitlement alone does not light a port.
- G720 64 on SFP+ only. Fifty-six is the SFP+ ceiling; sixty-four needs SFP-DD PoD and DD optics.
- G720 24/64 mixed with G820 24/56. Different generation math — wrong licenses and optics.
- Repurchasing Enterprise bundle. Usually included; still quote PoD, TruFOS, and support.
- ICL treated as free. Director ICL PoD is a paid kit class.
- One PO, many OEM skins. Dell, HPE, Hitachi, IBM, TGStor, and BSN PoD codes are not interchangeable.
- Ignoring renewal cliffs. Mid-contract PoD growth can raise the next support true-up.
- Publishing invented PoD dollars. Soft corridors need a dated book — pending confirmation.
常见问题
速答： PoD enables unused cages after a base count. Day-one CapEx is often lower than full populate, but optics and renewals can reverse the gap. G720 needs SFP-DD PoD for 64 ports. OEM PoD SKUs are not interchangeable. No invented list dollars on this page.
Ports on Demand is a license kit that enables unused physical Fibre Channel cages after a lower base port count. The ASIC and cages ship in the chassis; PoD turns entitlement on. It is not an optic and not a support renewal.
Day-one CapEx is often lower with a base kit plus selective PoD. Total cost can reverse after later PoD buys, matching optics, and support years on the larger entitlement. Treat any dollar gap as industry estimate pending confirmation on the official book.
G720 hardware is 48 SFP+ plus 8 SFP-DD cages. SFP+ alone reaches 56 ports. Reaching 64 requires SFP-DD PoD plus matching SFP-DD optics. A 24/56 string is Gen 8 G820 math, not G720 24/64.
Yes for every lit port. PoD enables the port; optics set speed and reach; the peer HBA or array port must match. Ordering PoD without optics leaves dark cages on the floor.
Support and TruFOS often price against the enabled or covered configuration, not the empty base alone. Plan renewal cliffs when PoD growth lands mid-contract. Confirm coverage years on the OEM or BSN book — pending confirmation for any soft quote.
No. Same Broadcom ASIC generation does not make OEM PoD part numbers interchangeable. Keep Dell Connectrix, HPE B-series, Hitachi, IBM, TGStor, and BSN columns on separate purchase orders.
References
速答： Validate platform names and port cages on Broadcom public G710, G720, and X8 pages plus product briefs. This page publishes no PoD list dollars. Request the seller’s dated PoD price book on RFQ for commercial confirmation before you freeze CapEx.
- Broadcom Brocade G720 Switch — product page
- Broadcom Brocade G710 Switch — product page
- Broadcom Brocade X8 Director — product page
- Brocade G720 Switch Product Brief (docs.broadcom.com)
- Brocade G710 Switch Product Brief (docs.broadcom.com)
Port-scale facts (G710 8→24, G720 SFP-DD for 64, director ICL PoD as paid kits) align with Broadcom product materials and OEM ordering sheets cited on sibling Gen 7 / Gen 8 RFQ pages. Soft commercial dollars remain industry estimate / pending confirmation.
Key Takeaway
核心结论： Score PoD versus fully populated on lit-port timing, optics pairing, and renewal cliffs — not on the chassis sticker alone. Keep PoD, optics, TruFOS, and support as separate columns. Reject G720 64-port claims without SFP-DD. Shanghai TaoHan Industrial Co., Ltd. supplies Brocade FC switch configurations with competitive pricing.