FIELD GUIDESource-led reference

P200 / Pluggable I/O / Connector

SFP / SFP+ / SFP28 host connector form

The SFP-family host interface uses a 20-position connector form for hot-swappable pluggable modules in the cited product series.

Also called SFP SFP+ SFP28 20 pin SFP

The same physical module family can carry different electrical/optical standards; form factor alone does not establish link capability.

Look for

Identify the host cage and exact module standard separately, including speed, media and vendor/device support.

Claim inspection dates: 2026-10-05, 2026-10-11 · Independent review pending

Image inspection / P200

See the view. Check its scope.

1 registered view for this reference. Different part examples are not automatically mates; all remain not to scale and independently unapproved.

SFP / SFP+ / SFP28 host connector form: SFP-family host connector form / 20 positions. Equipment-side pluggable-module cage opening; simplified front face. Qualitative source-linked recognition study, not a pinout or a dimensional guide. (private workspace)

P200 / Inherited recognition study

SFP / SFP+ / SFP28 host connector form

SFP / SFP+ / SFP28 host connector form

Equipment-side pluggable-module cage opening; simplified front face · Other declared component

Not to scale. Technical and rights review pending.

Inspect view & provenance (private workspace)

Network notes / Pluggable hosts / P200

Does an SFP cage tell me which module and cable will work?

FIELD NOTES 05

No. The host connector/cage, removable module and network-facing interface are different objects. Identify all three before checking the exact host’s module support. C200C · C200D

Component or signal: documented distinction and remaining check
CheckDocumented distinctionWhat this does not establish
Host sideAmphenol describes a 20-position host connector enclosed in a metal cage on a board. C200CA host component is not the removable transceiver or a compatibility list.
Optical exampleCisco’s note describes optical SFP/SFP+ modules with LC network connections. C200DThe host-side form does not establish wavelength, fiber type or the far-end optic.
Copper exampleThe same note describes a 1000BASE-T SFP module with an RJ45 network connection. C200DCheck the exact supported module/host combination; do not assign every cage an optical connector.
Read the part and the device.
Separate three identities: host port, removable module/assembly and network-facing connection. Copy the equipment and module part numbers, not just “SFP”.
Keep this requirement open.
Cross-generation operation, firmware support, power/thermal limits, optic wavelength and working-link performance remain host-specific.

Keep this limit: A hot-swappable component description is not a universal handling instruction or an approved host/module/cable path. C200C · C200D

Documented support · named example only

Can documented SFP modules have different network-facing connectors?

Cisco depicts LC optical examples and an RJ45 1000BASE-T example.

Boundary. These examples do not qualify a module for an arbitrary SFP-family host.

Next check. Read the exact host-supported module list and intended medium.

S506 · C200D (private workspace)

Not established · named example only

Does a host connector/cage page approve a module for a switch?

The Amphenol pages identify host-side components, not an installed switch/module pairing.

Boundary. No cross-generation, firmware or optical support is implied.

Next check. Use the exact switch or NIC vendor’s module qualification list.

S507 · S508 · C200C (private workspace) · C201C (private workspace)

Before choosing the cable or component

  1. Find the exact host model, port mode and supported module list.
  2. Read the complete module or DAC assembly part number and its network-facing medium.
  3. Confirm the far-end optic/device and the full supported path.

Source check · 14 October 2026. The component description and module-interface captions were checked. Current support matrices and the user’s hardware/firmware were not.

Source-qualified reference, not a wiring, optical-link or compatibility approval. Each linked claim and source carries its own recorded inspection date and review status. Selected source checks do not constitute independent technical or rights approval.

Existing source trail: S507 · S506.

Network, fiber and RF questions · QSFP+ host connector form · QSFP-DD host connector / cage form

Read the evidence and its scope · 3 observations

C200A (private workspace) — Amphenol identifies an UltraPort SFP-family host connector as a 20-position hot-swappable I/O form used for SFP+ and SFP28 applications.

V36 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction or end-to-end compatibility proof.

S203

C200C (private workspace) — Amphenol describes UltraPort SFP as a 20-position hot-swappable I/O connector enclosed within a metal cage mounted on a host PCB. The host connector and cage are not the removable network transceiver itself.

V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

S507

C200D (private workspace) — Cisco depicts optical SFP modules with LC network connections and a 1000BASE-T SFP module with an RJ45 network connection. The SFP host-side form does not by itself identify the network-facing connector, medium or supported host/module combination.

V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

S506

Source interpretation is not independent engineering review, hardware testing, wiring advice or a public-release approval.

V117 / READER FIELD GUIDE / COPPER NETWORKS

Before you connect or replace

SFP is a module interface, not an Ethernet socket

No. SFP/SFP+/SFP28 refers here to the host receptacle form. The pluggable module defines an exposed media interface; choose only equipment-supported modules and appropriate copper/fiber connections.

Three checks and exact source trail ↗

Separate the SFP module from its optic connector

No. An SFP host cage is not a declared optical port until a suitable module is installed. Transceiver model, media type, connector format and supported equipment determine the path.

Three checks and exact source trail ↗

Editorial decision guidance only. A connector identity or nominal pitch does not establish approved mating, safe wiring or a supported device combination.

Flagship atlas NETWORK / MODULE

SFP cages: optics require qualification

A family resemblance between SFP, SFP+ and SFP28 does not qualify a transceiver for a particular switch or router. The exact port, module part, medium and far-end optics must be supported.

LP01 P200
Conceptual four-stage decision path: SFP host cage; then Module identity; then Cable / fiber; then Far-end port. Every stage requires independent verification; this is not a drawing of connector contact geometry.
Decision map, not a plug drawing or electrical wiring diagram. The original connector specimen remains above; this sequence shows what needs proof after shape identification.

Four facts to keep separate

01

Host connector

Amphenol identifies a 20-position SFP-family host connector in SFP+ and SFP28 applications. Evidence: C200A

02

Port electronics

A compatible-looking module is not evidence that a host port supports its signal mode or rate. Evidence: C200A

03

Module / cable

Optic versus DAC, manufacturer part number and cable type require their own equipment documentation. Evidence: C200A

04

Far endpoint

Both network endpoints and the optical/electrical medium must satisfy the system requirements. Evidence: C200A

Common wrong conclusion

Do not promote the presence of an SFP-family cage into “all SFP28 modules are backward compatible with SFP+”.

What to check next

  1. Find the host switch/router hardware model, port type and supported transceiver list.
  2. Read the exact module/DAC identity, cable/fiber and operating mode at both ends.
  3. Confirm configuration and far-end link requirements; no speed or optical budget is promised from a cage alone.
Why these statements are qualified · claim and source context

This is an original editorial decision study tied to existing source-checked claims. The following source inspections have not been renewed by this new page presentation, and none is independent engineering or model-by-model qualification.

  • S203 · Amphenol Communications SolutionsSFP series overview · source reviewed 2026-10-05 · Identifies the hot-swappable SFP-family host interface as a 20-position connector form used for SFP+ / SFP28 applications.

Unresolved: Actual device fit, required physical tolerances, pinouts, negotiations, electrical safety and hardware interoperability still require the identified manufacturer's documentation and any necessary independent review.

Signal-path fieldbook

Before a cable or module is ordered.

Read the answer, keep mechanical fit separate from the signal path, and verify the named endpoint. These editorial studies reuse inherited source records; no compatibility has been laboratory confirmed.

V106N01 / pluggable networkDevice qualification required

Will an SFP28 transceiver work in any SFP+ port because the cage looks right?

Field answerThe shared cage outline is only the mechanical layer. Amphenol documents a 20-position UltraPort SFP-family host interface for SFP+ and SFP28 applications, but that connector-series evidence does not qualify a particular switch, transceiver, host mode or fiber link.

Conceptual path: documented host port and cage, exact module or copper assembly, and far endpoint each require their own checks. Physical fit alone does not verify a network link.
Interpretation study, not a wiring or mating diagram. In order: Identify the named host port and cage—not just the front opening. / Confirm the exact optic, DAC or cable assembly and supported host mode. / Check the far endpoint and optical/electrical medium; no automatic link claim. This is not evidence of a working connection.

Four checks that must stay separate

Evidence layerWhat is established or still conditional
Host connector / cageAmphenol UltraPort SFP+ is a 20-position host connector inside a metal cage; this is not the removable optic.
Signal and device supportA host port must explicitly support the intended transceiver and link mode. Shape and the connector maker’s performance envelope do not establish switch firmware support.
Module and mediumA transceiver, direct-attach cable and optical link are different assemblies; verify each exact module, fiber or copper path and opposite endpoint.
Manufacturer scopeS203 describes the UltraPort product series, not an approval for every SFP+ switch or SFP28 optic SKU.

Check next, in this order

  1. Identify the exact switch or NIC model, port label and published supported modules.
  2. Match the complete optic/DAC part number and host-approved mode; check its specified electrical or optical medium.
  3. Compare the far-end module, cable or fiber specification, operating mode and system logs before assigning a cause.

Not yet established There is no manufacturer device-specific interoperability matrix, link-partner test, fiber budget or firmware qualification for the user’s actual pair of products.

Read the claim and manufacturer source boundaries

Existing scoped claims: C200A (V36 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction or end-to-end compatibility proof.). No newly authored empirical specifications; manufacturer catalogue claims remain conditional on the actual part and host.

  • S203 · Amphenol Communications SolutionsSFP series overview; inherited review 2026-10-05. Identification/reference scope only. V36 does not convert this source into a universal pinout, fabrication drawing, electrical approval or end-to-end compatibility verdict.

Existing inspection dates remain unchanged. This editorial synthesis is not a physical mating test, pinout, optical budget, manufacturer device approval or deployment authorization.

Visual atlas / P200 / 2026

Recognize the right physical clue.

FIGURE · REVIEW PENDING
SFP / SFP+ / SFP28 host connector form: SFP-family host connector form / 20 positions. Equipment-side pluggable-module cage opening; simplified front face. Qualitative source-linked recognition study, not a pinout or a dimensional guide.
Equipment-side host cage. Equipment-side pluggable-module cage opening; simplified front face.

What to look for

SFP-family host connector form / 20 positions

What the drawing does not prove

Qualitative widths show different host form classes; no cage dimension, connector contact or faceplate is copied.

Neither shared module names nor cage resemblance guarantees optical, copper, speed, firmware or vendor support.

No fabrication dimensions, conductor routing, guaranteed fit or device approval. For electrical, power and optical interfaces, follow the original equipment instructions.

Figure evidence, orientation & usage rights

Uses previously recorded V112 manufacturer claim/source inspections; October 2026 supplementary public-source spot checks are documented separately, not treated as a refreshed approval.

Original Port & Cable interpretive vector, no third-party photo, copied CAD, logo or vendor drawing. Third-party product photos, logos and source drawings are not redistributed. pending independent expert assessment; publication approval remains closed.

Original claim identifiers: C200A (private workspace). Legacy evidence dates and rights assessments remain as recorded.

The useful distinction

Recognize it. Then verify it.

The SFP-family host interface uses a 20-position connector form for hot-swappable pluggable modules in the cited product series. [C200A]

Amphenol describes UltraPort SFP as a 20-position hot-swappable I/O connector enclosed within a metal cage mounted on a host PCB. The host connector and cage are not the removable network transceiver itself. [C200C]

Cisco depicts optical SFP modules with LC network connections and a 1000BASE-T SFP module with an RJ45 network connection. The SFP host-side form does not by itself identify the network-facing connector, medium or supported host/module combination. [C200D]

Source-scoped identification facts

Each value retains its exact example, role and measurement axis. Facts from different parts must not be combined into an invented component.

Documented examples; not a mating drawing or compatibility approval
Nominal contacts20S203Source-backed host-connector position count; module electrical assignments are outside V36.
Positions / cavity span20 (Claim C200A); 20 (Claim C200C)S203 · S507Recorded source-scoped values; named examples do not describe every family variant or establish compatibility. V36 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction or end-to-end compatibility proof. V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.
Contact rows2 (Claim C200B); 2 (0744410010)S217 · S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. Molex product 744410010 documents an SFP/SFP+ host receptacle with 20 loaded circuits, two rows, right-angle orientation and 0.80 mm mating-interface pitch. | V37 engineering-depth sidecar fact; source-checked but not independently human-approved, not a fabrication drawing, and not a safe-substitution or repair instruction. 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.
Contact pitch0.8 mm Example mating-interface pitch (Recorded example component); 0.8 mm mating interface (0744410010)S217 · S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. example_component; SFP/SFP+/SFP28 host receptacle 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.
Connector rolesocket; socket (0744410010)S203 · S217 · S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. SFP/SFP+/SFP28 host receptacle 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.
Keying / polarizationKeyed/polarized/locked to mating part; PCB locator and retention (0744410010)S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.
ManufacturerMolex (0744410010)S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.
Series74441 (0744410010)S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.
Exact part / implementation0744410010 (0744410010)S217Named source examples retain separate role, part, view and axis limits; values are not a universal family specification. 0744410010. Documented role: socket. 20loaded contacts; exact right-angle SMT part. No shape-based throughput approval.

Not recorded: Populated contacts, Dimensions / axis, Contact gender / arrangement, Mounting, Coupling / latch, Shell / form, Recorded markings, View convention. Unknown fields stay unknown; illustrations supply no measurements or pin assignments.

Recorded variant and source limits
  • The 0.80 mm pitch and two-row construction are example-component facts, not a universal fabrication envelope.
  • No SFP electrical pin map is published in this profile.
  • SFP-family module capability remains module- and host-specific.
  • Classic SFP gigabit datacom / INF-8074i: MSA Appendix B Figure 1 host-board connector-block view, same orientation as Appendix A Figure 4; ASIC left,bezel right.
  • SFP+ transceiver interface / SFF-8431: Figure 1 host PCB top view: host/insertion left,bezel right; right column 10 top to1 bottom,left11 top to20 bottom. Figure 2 module top/through-board views.
  • SFP28 SFF-8472-managed interface / SFF-8419: Figure 7-1 host PCB top view: host/insertion left,bezel right. Figure 7-2 bottom pads viewed from top through board; top pads viewed from top. Rate-select labels conflict.
  • Amphenol AQP-XPB4-XXX SFP28 AOC end: Numbered manufacturer table; source-verified host spatial layout is not imported from other products.
  • Broadcom AFBR-57E6APZ SFP for FDDI/Fast Ethernet: Figure 2 p. 2 is the module PCB connection diagram: top of board, with bottom of board as viewed through top of board. Contact functions transfer by number to the host; host footprint mirroring is not inferred.
  • Coherent FTLX8574D3BCL SFP+: Manufacturer host-board connector diagram p. 2 has arrows Towards Bezel and Towards ASIC. Numbered table p. 3 used; the p. 2 pin-9 signal conflict is unresolved.
  • Coherent FTLF8536P5xyL SFP28 single-rate 25GbE: p. 2 Diagram of Host Board Connector Block Pin Numbers and Names: host to left with module insertion direction; bezel to right. Do not transfer to a module-bottom view.
  • Coherent FTLF8536P5xyV SFP28 dual-rate 10/25GbE: p. 2 Diagram of Host Board Connector Block Pin Numbers and Names: host to left with module insertion direction; bezel to right. Do not transfer to a module-bottom view.
Report a correction to these facts →

Bounded facts, visible unknowns

Specifications and limits

SFP / SFP+ / SFP28 host connector form facts and limitations
Documented identification20-position SFP-family host connector form. [C200A]
Mechanical dimensionsNo independently reviewed mechanical drawing in V36; do not use this page for fabrication, fit testing or tolerance work.
Engineering pinoutSource-checked engineering profile available; independent review pending. Open engineering profile →
Verified device listNot included. Check exact device and accessory documentation.
A boundary, not an omission to guess around.

Use the source-backed form or position count only for identification. Resolve ratings, protocol, direction, wiring, cable construction and exact device support from the relevant equipment and component documentation.

Before you connect

What to check

  1. Identify the exact connector family and variant from the equipment or cable documentation.
  2. Keep shape, contact count, protocol, electrical rating and device support as separate facts.
  3. Do not force, rewire or adapt a connector from this recognition record; resolve the remaining requirements first.
Trace a supported connection class →

Pins & wiring

Pinout

Choose the exact wiring. Pin numbers follow its stated view; a schematic does not establish physical positions. Check your exact device before wiring.

What the status labels mean
Confirmed
Recorded research passes agree within this variant; this is not independent human review or hardware validation.
Single source
Only one underlying document, or one pass, supports this assignment.
Device-specific
Supported for the named equipment or wiring only. Check your device’s manual.
Unverified
Missing or conflicting evidence. Do not wire from this row.
Not connected
The source explicitly says NC, no contact or no pin for this wiring.
Wiring variant

Classic SFP gigabit datacom / INF-8074i

View and evidence limits

MSA Appendix B Figure 1 host-board connector-block view, same orientation as Appendix A Figure 4; ASIC left,bezel right.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • Two label conflicts internal to SFF-8419 remain unresolved; both source labels retained.
  • SFP112/SFP224 CMIS, AS0/AS1, passive cables, arbitrary vendor-specific behavior and supported link capability are not established.
SFP-family host connector mechanical identifierMSA Appendix B Figure 1 host-board connector-block view, same orientation as Appendix A Figure 4; ASIC left,bezel right.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VeeT (single_source)12: TX Fault (single_source)23: TX Disable (single_source)34: MOD-DEF2 (single_source)45: MOD-DEF1 (single_source)56: MOD-DEF0 (single_source)67: Rate Select (single_source)78: LOS (single_source)89: VeeR (single_source)910: VeeR (single_source)1011: VeeR (single_source)1112: RD- (single_source)1213: RD+ (single_source)1314: VeeR (single_source)1415: VccR (single_source)1516: VccT (single_source)1617: VeeT (single_source)1718: TD+ (single_source)1819: TD- (single_source)1920: VeeT (single_source)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.

Not yet independently confirmed. No settled pin table is available for this wiring.

Sources (1)

SFP+ transceiver interface / SFF-8431

View and evidence limits

Figure 1 host PCB top view: host/insertion left,bezel right; right column 10 top to1 bottom,left11 top to20 bottom. Figure 2 module top/through-board views.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • Two label conflicts internal to SFF-8419 remain unresolved; both source labels retained.
  • SFP112/SFP224 CMIS, AS0/AS1, passive cables, arbitrary vendor-specific behavior and supported link capability are not established.
SFP-family host connector mechanical identifierFigure 1 host PCB top view: host/insertion left,bezel right; right column 10 top to1 bottom,left11 top to20 bottom. Figure 2 module top/through-board views.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VeeT (single_source)12: Tx_Fault (single_source)23: Tx_Disable (single_source)34: SDA (single_source)45: SCL (single_source)56: Mod_ABS (single_source)67: RS0 (single_source)78: Rx_LOS (single_source)89: RS1 (single_source)910: VeeR (single_source)1011: VeeR (single_source)1112: RD- (single_source)1213: RD+ (single_source)1314: VeeR (single_source)1415: VccR (single_source)1516: VccT (single_source)1617: VeeT (single_source)1718: TD+ (single_source)1819: TD- (single_source)1920: VeeT (single_source)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.

Not yet independently confirmed. No settled pin table is available for this wiring.

Sources (1)

SFP28 SFF-8472-managed interface / SFF-8419

View and evidence limits

Figure 7-1 host PCB top view: host/insertion left,bezel right. Figure 7-2 bottom pads viewed from top through board; top pads viewed from top. Rate-select labels conflict.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • Two label conflicts internal to SFF-8419 remain unresolved; both source labels retained.
  • SFP112/SFP224 CMIS, AS0/AS1, passive cables, arbitrary vendor-specific behavior and supported link capability are not established.
SFP-family host connector mechanical identifierFigure 7-1 host PCB top view: host/insertion left,bezel right. Figure 7-2 bottom pads viewed from top through board; top pads viewed from top. Rate-select labels conflict.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VeeT (single_source)12: Tx_Fault (single_source)23: Tx_Disable (single_source)34: SDA (single_source)45: SCL (single_source)56: Mod_ABS (single_source)67: Not confirmed (unverified)78: Rx_LOS (single_source)89: Not confirmed (unverified)910: VeeR (single_source)1011: VeeR (single_source)1112: RD- (single_source)1213: RD+ (single_source)1314: VeeR (single_source)1415: VccR (single_source)1516: VccT (single_source)1617: VeeT (single_source)1718: TD+ (single_source)1819: TD- (single_source)1920: VeeT (single_source)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.

Not yet independently confirmed. No settled pin table is available for this wiring.

Sources (1)

Amphenol AQP-XPB4-XXX SFP28 AOC end

Device-specific wiring. Check your device’s manual before connecting or applying power.

View and evidence limits

Numbered manufacturer table; source-verified host spatial layout is not imported from other products.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • Two label conflicts internal to SFF-8419 remain unresolved; both source labels retained.
  • SFP112/SFP224 CMIS, AS0/AS1, passive cables, arbitrary vendor-specific behavior and supported link capability are not established.
SFP-family host connector mechanical identifierNumbered manufacturer table; source-verified host spatial layout is not imported from other products.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VeeT (device_specific)12: Tx_Fault (device_specific)23: Tx_Disable (device_specific)34: SDA (device_specific)45: SCL (device_specific)56: Mod_ABS (device_specific)67: RS0 (device_specific)78: Rx_LOS (device_specific)89: RS1 (device_specific)910: VeeR (device_specific)1011: VeeR (device_specific)1112: RD- (device_specific)1213: RD+ (device_specific)1314: VeeR (device_specific)1415: VccR (device_specific)1516: VccT (device_specific)1617: VeeT (device_specific)1718: TD+ (device_specific)1819: TD- (device_specific)1920: VeeT (device_specific)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.
Amphenol AQP-XPB4-XXX SFP28 AOC end — source-scoped contact map
PinSignalWhat it doesStatus
1VeeTGround reference and return.Device-specific
Sources
2Tx_FaultSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
3Tx_DisableSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
4SDAControl, detection or configuration connection; check the source and device.Device-specific
Sources
5SCLControl, detection or configuration connection; check the source and device.Device-specific
Sources
6Mod_ABSControl, detection or configuration connection; check the source and device.Device-specific
Sources
7RS0Control, detection or configuration connection; check the source and device.Device-specific
Sources
8Rx_LOSSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
9RS1Control, detection or configuration connection; check the source and device.Device-specific
Sources
10VeeRGround reference and return.Device-specific
Sources
11VeeRGround reference and return.Device-specific
Sources
12RD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
13RD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
14VeeRGround reference and return.Device-specific
Sources
15VccRPower connection (VccR). Check the specified supply.Device-specific
Sources
16VccTPower connection (VccT). Check the specified supply.Device-specific
Sources
17VeeTGround reference and return.Device-specific
Sources
18TD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
19TD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
20VeeTGround reference and return.Device-specific
Sources
Sources (1)

Broadcom AFBR-57E6APZ SFP for FDDI/Fast Ethernet

Device-specific wiring. Check your device’s manual before connecting or applying power.

View and evidence limits

Figure 2 p. 2 is the module PCB connection diagram: top of board, with bottom of board as viewed through top of board. Contact functions transfer by number to the host; host footprint mirroring is not inferred.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • NU means not used, not proven physically unconnected. Pin 2 is explicitly held low by this module.
  • FTLX8574D3BCL PDF p. 2 labels pin 9 VeeR; p. 3 labels it RS1 and says no connection required. It is explicitly unverified rather than choosing one label. The p. 2 figure also prints 1 at the bottom position where the table has pin 10, so that spatial numbering is not used.
  • These are named optical module examples, not universal assignments for copper SFP, DAC, other rates, vendor modules or equipment PCB solder tails. Power ratings and compatibility are not generalized.
SFP-family host connector mechanical identifierFigure 2 p. 2 is the module PCB connection diagram: top of board, with bottom of board as viewed through top of board. Contact functions transfer by number to the host; host footprint mirroring is not inferred.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VEET (device_specific)12: NU (device_specific)23: Tx Disable (device_specific)34: MOD-DEF2 (device_specific)45: MOD-DEF1 (device_specific)56: MOD-DEF0 (device_specific)67: NU (device_specific)78: LOS (device_specific)89: VEER (device_specific)910: VEER (device_specific)1011: VEER (device_specific)1112: RD- (device_specific)1213: RD+ (device_specific)1314: VEER (device_specific)1415: VCCR (device_specific)1516: VCCT (device_specific)1617: VEET (device_specific)1718: TD+ (device_specific)1819: TD- (device_specific)1920: VEET (device_specific)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.
Broadcom AFBR-57E6APZ SFP for FDDI/Fast Ethernet — source-scoped contact map
PinSignalWhat it doesStatus
1VEETGround reference and return.Device-specific
Sources
2NUControl, detection or configuration connection; check the source and device.Device-specific
Sources
3Tx DisableSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
4MOD-DEF2Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
5MOD-DEF1Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
6MOD-DEF0Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
7NUControl, detection or configuration connection; check the source and device.Device-specific
Sources
8LOSControl, detection or configuration connection; check the source and device.Device-specific
Sources
9VEERGround reference and return.Device-specific
Sources
10VEERGround reference and return.Device-specific
Sources
11VEERGround reference and return.Device-specific
Sources
12RD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
13RD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
14VEERGround reference and return.Device-specific
Sources
15VCCRPower connection (VCCR). Check the specified supply.Device-specific
Sources
16VCCTPower connection (VCCT). Check the specified supply.Device-specific
Sources
17VEETGround reference and return.Device-specific
Sources
18TD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
19TD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
20VEETGround reference and return.Device-specific
Sources
Sources (1)

Coherent FTLX8574D3BCL SFP+

Device-specific wiring. Check your device’s manual before connecting or applying power.

View and evidence limits

Manufacturer host-board connector diagram p. 2 has arrows Towards Bezel and Towards ASIC. Numbered table p. 3 used; the p. 2 pin-9 signal conflict is unresolved.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • FTLX8574D3BCL PDF p. 2 labels pin 9 VeeR; p. 3 labels it RS1 and says no connection required. It is explicitly unverified rather than choosing one label. The p. 2 figure also prints 1 at the bottom position where the table has pin 10, so that spatial numbering is not used.
  • These are named optical module examples, not universal assignments for copper SFP, DAC, other rates, vendor modules or equipment PCB solder tails. Power ratings and compatibility are not generalized.
SFP-family host connector mechanical identifierManufacturer host-board connector diagram p. 2 has arrows Towards Bezel and Towards ASIC. Numbered table p. 3 used; the p. 2 pin-9 signal conflict is unresolved.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VEET (device_specific)12: TFAULT (device_specific)23: TDIS (device_specific)34: SDA (device_specific)45: SCL (device_specific)56: MOD_ABS (device_specific)67: RS0 (device_specific)78: RX_LOS (device_specific)89: Not confirmed (unverified)910: VEER (device_specific)1011: VEER (device_specific)1112: RD- (device_specific)1213: RD+ (device_specific)1314: VEER (device_specific)1415: VCCR (device_specific)1516: VCCT (device_specific)1617: VEET (device_specific)1718: TD+ (device_specific)1819: TD- (device_specific)1920: VEET (device_specific)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.
Coherent FTLX8574D3BCL SFP+ — source-scoped contact map
PinSignalWhat it doesStatus
1VEETGround reference and return.Device-specific
Sources
2TFAULTControl, detection or configuration connection; check the source and device.Device-specific
Sources
3TDISControl, detection or configuration connection; check the source and device.Device-specific
Sources
4SDAControl, detection or configuration connection; check the source and device.Device-specific
Sources
5SCLControl, detection or configuration connection; check the source and device.Device-specific
Sources
6MOD_ABSControl, detection or configuration connection; check the source and device.Device-specific
Sources
7RS0Control, detection or configuration connection; check the source and device.Device-specific
Sources
8RX_LOSSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
9Not confirmedNo settled assignment. Do not wire from this row.Unverified
Sources
10VEERGround reference and return.Device-specific
Sources
11VEERGround reference and return.Device-specific
Sources
12RD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
13RD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
14VEERGround reference and return.Device-specific
Sources
15VCCRPower connection (VCCR). Check the specified supply.Device-specific
Sources
16VCCTPower connection (VCCT). Check the specified supply.Device-specific
Sources
17VEETGround reference and return.Device-specific
Sources
18TD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
19TD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
20VEETGround reference and return.Device-specific
Sources
Sources (1)

Coherent FTLF8536P5xyL SFP28 single-rate 25GbE

Device-specific wiring. Check your device’s manual before connecting or applying power.

View and evidence limits

p. 2 Diagram of Host Board Connector Block Pin Numbers and Names: host to left with module insertion direction; bezel to right. Do not transfer to a module-bottom view.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • FTLX8574D3BCL PDF p. 2 labels pin 9 VeeR; p. 3 labels it RS1 and says no connection required. It is explicitly unverified rather than choosing one label. The p. 2 figure also prints 1 at the bottom position where the table has pin 10, so that spatial numbering is not used.
  • These are named optical module examples, not universal assignments for copper SFP, DAC, other rates, vendor modules or equipment PCB solder tails. Power ratings and compatibility are not generalized.
SFP-family host connector mechanical identifierp. 2 Diagram of Host Board Connector Block Pin Numbers and Names: host to left with module insertion direction; bezel to right. Do not transfer to a module-bottom view.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VEET (device_specific)12: TFAULT (device_specific)23: TDIS (device_specific)34: SDA (device_specific)45: SCL (device_specific)56: MOD_ABS (device_specific)67: RS0 / NC (not_connected)78: RX_LOS (device_specific)89: RS1 / NC (not_connected)910: VEER (device_specific)1011: VEER (device_specific)1112: RD- (device_specific)1213: RD+ (device_specific)1314: VEER (device_specific)1415: VCCR (device_specific)1516: VCCT (device_specific)1617: VEET (device_specific)1718: TD+ (device_specific)1819: TD- (device_specific)1920: VEET (device_specific)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.
Coherent FTLF8536P5xyL SFP28 single-rate 25GbE — source-scoped contact map
PinSignalWhat it doesStatus
1VEETGround reference and return.Device-specific
Sources
2TFAULTControl, detection or configuration connection; check the source and device.Device-specific
Sources
3TDISControl, detection or configuration connection; check the source and device.Device-specific
Sources
4SDAControl, detection or configuration connection; check the source and device.Device-specific
Sources
5SCLControl, detection or configuration connection; check the source and device.Device-specific
Sources
6MOD_ABSControl, detection or configuration connection; check the source and device.Device-specific
Sources
7RS0 / NCNot connected or absent in this named wiring.Not connected
Sources
8RX_LOSSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
9RS1 / NCNot connected or absent in this named wiring.Not connected
Sources
10VEERGround reference and return.Device-specific
Sources
11VEERGround reference and return.Device-specific
Sources
12RD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
13RD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
14VEERGround reference and return.Device-specific
Sources
15VCCRPower connection (VCCR). Check the specified supply.Device-specific
Sources
16VCCTPower connection (VCCT). Check the specified supply.Device-specific
Sources
17VEETGround reference and return.Device-specific
Sources
18TD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
19TD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
20VEETGround reference and return.Device-specific
Sources
Sources (1)

Coherent FTLF8536P5xyV SFP28 dual-rate 10/25GbE

Device-specific wiring. Check your device’s manual before connecting or applying power.

View and evidence limits

p. 2 Diagram of Host Board Connector Block Pin Numbers and Names: host to left with module insertion direction; bezel to right. Do not transfer to a module-bottom view.

  • P200 SFP / SFP+ / SFP28 host — **Partial; internal source conflicts remain** — A: SFP MSA, SFF-8431, SFF-8419/SFF-8402 and Amphenol AOC. B: Broadcom SFP and Coherent SFP+/SFP28 module datasheets. Common supply, management and differential data contacts align. B's Fast Ethernet SFP does not implement the MSA's fault/rate-select functions on 2/7. Legacy SFP 9 is ground; SFP+ and dual-rate SFP28 use a rate-select role. B's single-rate SFP28 explicitly makes 7/9 NC. **A's SFF-8419 rev 2.0a conflicts internally on labels at 7/9; B's Coherent SFP+ datasheet conflicts internally at 9 (VeeR versus RS1).** Those rows stay unverified. Different documents; another module's map cannot resolve either source's contradiction.
  • FTLX8574D3BCL PDF p. 2 labels pin 9 VeeR; p. 3 labels it RS1 and says no connection required. It is explicitly unverified rather than choosing one label. The p. 2 figure also prints 1 at the bottom position where the table has pin 10, so that spatial numbering is not used.
  • These are named optical module examples, not universal assignments for copper SFP, DAC, other rates, vendor modules or equipment PCB solder tails. Power ratings and compatibility are not generalized.
SFP-family host connector mechanical identifierp. 2 Diagram of Host Board Connector Block Pin Numbers and Names: host to left with module insertion direction; bezel to right. Do not transfer to a module-bottom view.SCHEMATIC · physical positions unconfirmedNot to scale · check the named wiring and device manual1: VEET (device_specific)12: TFAULT (device_specific)23: TDIS (device_specific)34: SDA (device_specific)45: SCL (device_specific)56: MOD_ABS (device_specific)67: RS0 (device_specific)78: RX_LOS (device_specific)89: RS1 (device_specific)910: VEER (device_specific)1011: VEER (device_specific)1112: RD- (device_specific)1213: RD+ (device_specific)1314: VEER (device_specific)1415: VCCR (device_specific)1516: VCCT (device_specific)1617: VEET (device_specific)1718: TD+ (device_specific)1819: TD- (device_specific)1920: VEET (device_specific)20powergrounddataConfigshieldNCUnknown
Schematic only · physical contact positions unconfirmed. Original drawing · not to scale. Scroll sideways if needed.
Coherent FTLF8536P5xyV SFP28 dual-rate 10/25GbE — source-scoped contact map
PinSignalWhat it doesStatus
1VEETGround reference and return.Device-specific
Sources
2TFAULTControl, detection or configuration connection; check the source and device.Device-specific
Sources
3TDISControl, detection or configuration connection; check the source and device.Device-specific
Sources
4SDAControl, detection or configuration connection; check the source and device.Device-specific
Sources
5SCLControl, detection or configuration connection; check the source and device.Device-specific
Sources
6MOD_ABSControl, detection or configuration connection; check the source and device.Device-specific
Sources
7RS0Control, detection or configuration connection; check the source and device.Device-specific
Sources
8RX_LOSSignal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
9RS1Control, detection or configuration connection; check the source and device.Device-specific
Sources
10VEERGround reference and return.Device-specific
Sources
11VEERGround reference and return.Device-specific
Sources
12RD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
13RD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
14VEERGround reference and return.Device-specific
Sources
15VCCRPower connection (VCCR). Check the specified supply.Device-specific
Sources
16VCCTPower connection (VCCT). Check the specified supply.Device-specific
Sources
17VEETGround reference and return.Device-specific
Sources
18TD+Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
19TD-Signal conductor. Pair, polarity and direction follow this named wiring.Device-specific
Sources
20VEETGround reference and return.Device-specific
Sources
Sources (1)

What is not established

This field note does not approve a connection, adapter, cable assembly, rewiring scheme or fabricated part. It intentionally omits unsupported pin assignments and mechanical tolerances.

Your next step

Move from the form to the requirement.

The source trail

Evidence for this page

AI-assisted inspection is not independent engineering review. Source scope and access limitations are disclosed below. Procedural checklists are editorial requirements, not hardware measurements.

Back to first citation ↑
C200ASource checked · pending review

Amphenol identifies an UltraPort SFP-family host connector as a 20-position hot-swappable I/O form used for SFP+ and SFP28 applications.

Amphenol Communications Solutions · UltraPort SFP connector series ↗

Locator: SFP series overview
Access: public page. Identification/reference scope only. V36 does not convert this source into a universal pinout, fabrication drawing, electrical approval or end-to-end compatibility verdict.

S203: full source recordInspect review dependencies → (private workspace)

Claim scope: V36 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction or end-to-end compatibility proof.. Next review due 2027-01-03.

Back to first citation ↑
C200CSource checked · pending review

Amphenol describes UltraPort SFP as a 20-position hot-swappable I/O connector enclosed within a metal cage mounted on a host PCB. The host connector and cage are not the removable network transceiver itself.

Amphenol Communications Solutions · Amphenol UltraPort SFP — connector and metal cage roles ↗

Locator: Description: 20-position hot-swappable I/O connector enclosed in metal cage on host PCB
Access: public page. Product-family host construction only; no inference of a given transceiver or switch operating mode. No raw HTML or manufacturer image archive is represented as retained.

S507: full source recordInspect review dependencies → (private workspace)

Claim scope: V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.. Next review due 2027-01-09.

Back to first citation ↑
C200DSource checked · pending review

Cisco depicts optical SFP modules with LC network connections and a 1000BASE-T SFP module with an RJ45 network connection. The SFP host-side form does not by itself identify the network-facing connector, medium or supported host/module combination.

Cisco · Cisco — SFP host role and optical/copper network faces ↗

Locator: Overview; Figure 1 optical SFP with LC; Figure 2 1000BASE-T SFP with RJ45; Figure 3 SFP+
Access: public page. Manufacturer examples of removable transceivers and network-facing connections; exact host-supported modules remain a separate requirement. No raw HTML or manufacturer image archive is represented as retained.

S506: full source recordInspect review dependencies → (private workspace)

Claim scope: V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.. Next review due 2027-01-09.

Suggest a correction to this field note →

Put this field note to work.

Add to discovery trayRecord an unsaved candidate (private workspace)

Compare look-alikes: SFP versus QSFP-family pluggable I/O

Candidate selection does not confirm the identity or capabilities of your physical item.

Evidence behind this page

Scope first. Source second. Approval separate.

3 linked sources · 3 scoped claims · 0 sources with inspection/access flags.

Page scope: catalogue_expansion_v36

Assessment 2026-10-22 · earliest scheduled source review 2027-01-03. This is a recorded-date assessment, not a live source check. Page-level independent review is not established by this panel.

Inspect 3 source scopes, access limits and dates

S203 · UltraPort SFP connector series

Amphenol Communications Solutions · Manufacturer / product-owner domain · inspected 2026-10-05 · due 2027-01-03

Within inspection window

Scoped support: Identifies the hot-swappable SFP-family host interface as a 20-position connector form used for SFP+ / SFP28 applications.

Not established / limitations: Identification/reference scope only. V36 does not convert this source into a universal pinout, fabrication drawing, electrical approval or end-to-end compatibility verdict.

Locator: SFP series overview

S506 · Cisco — SFP host role and optical/copper network faces

Cisco · Manufacturer / product-owner domain · inspected 2026-10-11 · due 2027-01-09

Within inspection window

Scoped support: Manufacturer examples of removable transceivers and network-facing connections; exact host-supported modules remain a separate requirement.

Not established / limitations: Manufacturer examples of removable transceivers and network-facing connections; exact host-supported modules remain a separate requirement. No raw HTML or manufacturer image archive is represented as retained.

Locator: Overview; Figure 1 optical SFP with LC; Figure 2 1000BASE-T SFP with RJ45; Figure 3 SFP+

S507 · Amphenol UltraPort SFP — connector and metal cage roles

Amphenol Communications Solutions · Manufacturer / product-owner domain · inspected 2026-10-11 · due 2027-01-09

Within inspection window

Scoped support: Product-family host construction only; no inference of a given transceiver or switch operating mode.

Not established / limitations: Product-family host construction only; no inference of a given transceiver or switch operating mode. No raw HTML or manufacturer image archive is represented as retained.

Locator: Description: 20-position hot-swappable I/O connector enclosed in metal cage on host PCB

Trace 3 claims to their source records

C200A · P200

Amphenol identifies an UltraPort SFP-family host connector as a 20-position hot-swappable I/O form used for SFP+ and SFP28 applications.

Claim scope: V36 catalogue-expansion identification fact only; not independent technical approval, fabrication data, wiring instruction or end-to-end compatibility proof.

Source links: S203 · Evidence trail → (private workspace)

C200C · P200

Amphenol describes UltraPort SFP as a 20-position hot-swappable I/O connector enclosed within a metal cage mounted on a host PCB. The host connector and cage are not the removable network transceiver itself.

Claim scope: V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

Source links: S507 · Evidence trail → (private workspace)

C200D · P200

Cisco depicts optical SFP modules with LC network connections and a 1000BASE-T SFP module with an RJ45 network connection. The SFP host-side form does not by itself identify the network-facing connector, medium or supported host/module combination.

Claim scope: V121 named-product or explicitly scoped manufacturer distinction only; no wiring instruction, independent engineering approval or end-to-end compatibility guarantee.

Source links: S506 · Evidence trail → (private workspace)

Prepare this page for review → (private workspace)Read the evidence method →

Recorded evidence only. An inspection date, publisher label, source link or generated packet is not independent technical review, hardware testing, fabrication approval or a compatibility verdict.