2-Pack 1m/3.28ft 10G Direct Attach Copper Cable, SFP+ Passive Twinax DAC Cable for Cisco SFP-H10GB-CU1M, Ubiquiti, Arista, D-Link, Intel, Meraki, Mikrotik, Netgear, TP-Link etc.
4.6 (50 items)
Limited Time Sale$14.39 cheaper than the new price!!
Free cash-on-delivery fees for purchases over $99
Product details
| Management number | 217002028 | Release Date | 2026/04/19 | List Price | $9.60 | Model Number | 217002028 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
- 【SFP+ to SFP+ DAC Cable】10GBase-CU, 1m/3.3ft, 30AWG, passive, 2-pair differential twinax cable
- 【Wide Compatibility】Compatible with Ubiquiti UniFi UC-DAC-SFP+, Cisco SFP-H10GB-CU1M, Meraki, Mikrotik, Netgear, Intel, Fortinet, TP-Link, D-Link, Linksys, Zyxel, Broadcom, Quanta, PaloAlto, F5 etc.
- 【Signal Integrity Testing】100% tested for performance and interoperability (Passed by TDR & VNA). 10G SFP+ DAC cable is a good alternative to link 10G SFP+ ports.
- 【Low Power Consumption】Less than 0.1W with EEPROM I2C; Operating temperature: -20 to 85°C (-4 to 185°F)
- 【Technical Support】30 Days Free-returned, 3 Year Free Warranty and Lifetime Technology Support.
| Color | Black |
|---|---|
| Gauge | 30.0 |
| Model | CAB-10GSFP-P1M-CSC(x2)-A |
| Frequency | 10 GHz |
| Brand Name | Alwong |
| Cable Type | PVC Copper Cable |
| Item Shape | Round |
| Unit Count | 2.0 Count |
| Manufacturer | Alwong |
| Connector Type | Sfp+ |
| Number of Pins | 24 |
| Number of Items | 2 |
| Connector Gender | Male-to-Male |
| Specification Met | Sfp+ Msa |
| Compatible Devices | Cisco SFP-H10GB-CUXM; Ubiquiti UACC-DAC-SFP10-XM; Netgear AXC76XX |
| Data Transfer Rate | 10 Gigabits Per Second |
| Indoor Outdoor Usage | Indoor, Outdoor |
| Connectivity Technology | Ethernet |
| Ethernet Cable Category | Cat 6a |
| Recommended Uses For Product | Networking, Storage, Telecommunications |
| Other Special Features of the Product | High Speed |
Network Transceivers
Correction of product information
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form