Compatible Matrix for 10Gtek XFP Cable
Some brands of systems are encrypted due to their exclusiveness to third-party products, so cables for these systems need special coding inside to realize their compatibility with these systems. Here are some of the compatibility testing records for 10GTEK's XFP cables:
Cisco system is encrypted and requires Cisco original coding. 10gtek's compatible testing result: Working
Alcate-Lucent system is encrypted and requires Alcate-Lucent coding. 10gtek's compatible testing result: Working
Juniper system is encrypted and requires Juniper coding. 10gtek's compatible testing result: Working
Extreme system is encrypted and requires Extreme coding. 10gtek's compatible testing result: Working
Brocade system is encrypted and requires Brocade coding. 10gtek's compatible testing result: Working
Force10, Intel, Huawei, H3C/3com, Nortel, Foundry support our Standard OEM coding. 10gtek's compatible testing result: Working
For other brands, since we are lack of relative testing environment, currently the compatibility is uncertain. If you have any demands on them, pls get back to me for compatibility confirmation first.
We tried to make a compatible matrix as clear as possible, but still, many details are hard to include. The
actual compatibility performance is subject to the real working situation.
10GTEK's XFP Cables can meet compatibility* with Cisco System. The XFP products include:
? XFP optical transceiver modules.
? XFP to XFP passive DAC Twinax Cables.
? XFP to XFP active DAC Twinax Cables.
? XFP to SFP+ passive DAC Twinax Cables.
? XFP to SFP+ active DAC Twinax Cables.
? 40GBASE QSFP+ to 4 XFP (10GBASE) breakout cables
1. For the above products which involve 2 kinds of connectors (such as XFP to SFP+ cable, QSFP+ to 4 XFP breakout cable), when ordering, please specify the brand of systems that will link with the two connectors separately, e.g. SFP+ for Intel and XFP for Cisco, so that no confusion is caused.
2. "Meet Compatibility*" means: WORKING with systems, without link or identification problems.
Please note (Take Cisco as an example)::
To "meet Compatibility*" with system, we need to modify the EEPROM information, without short notice. The information may include but not limited to "P/N", "Length", "Vendor", etc