Top questions
Popular discussions about programming, compatibility and testing of optical transceivers.
We inherited a pair of Connectrix DS-7720B (Brocade G720) for a new fabric, and I haven't got anywhere near zoning yet, because not one of the double density ports will come up. Every single one of them says the same thing in switchshow: What is in the rack: Connectrix DS-7720B / Brocade G720…
I run pfSense on a small box with a Chelsio T580 and I want one of the QSFP+ ports feeding four 10G hosts instead of a single 40G link. The breakout cable is still on its way, so I would rather have the card in the right mode before it lands. pfSense box, Chelsio T580, one QSFP+ port sitting on a…
The poster compiled and loaded i40e 3.4.2 on Ubuntu 16.04 for an Intel XL710-QDA2 dual-port 40GbE adapter. The driver loaded fine, but as soon as non-Intel QSFP+ cables were attached dmesg reported "Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected." and no link…
4votes
3comments
124views
We run packet capture on a handful of Napatech cards and I am putting together the optics order for the next rack. Before spending anything I want to understand what the qualified module list actually means in practice, because the wording leaves room for interpretation. Napatech NT40E3 and NT20E3…
Two Jetson Thor devices achieved 100G connectivity directly but with poor speed, and when each was connected to a 100G switch no link formed, although the same optics and cables passed a 100G loopback test against a different switch. The poster wondered whether insufficient speed was breaking…
We hand over industrial cabinets with the customer's own monitoring on top, so readable DDMI on the uplink ports is part of the acceptance list. On an RGS200-12P the two ports that matter refuse to print anything at all after DDMI is enabled, even though both links are up and forwarding. Zyxel…
A new UDM Pro replaced a USG-3; plugging its LAN SFP+ port into the free SFP port of a UniFi Switch 24 with a known-good SFP+ DAC (taken from a working switch-to-switch link) gave no link on either UDM Pro port, and manually setting the UDM Pro port to 1 Gbps did not help. Several other users…
We have a leased dark pair between two POPs, roughly 115 km, and both ends land on a Cisco Catalyst 6506. The requirement is modest: one gigabit, no DWDM, no channel plan, just a working point to point link. What came back when I asked Cisco how to build it from their own catalogue was an…
A Huawei S6700 iStack did not form because the optical modules on the dedicated stacking ports 45-48 were of different types; the platform requires identical transceivers on those ports. The four ports 45-48 are the fixed stacking ports, and mixing, for example, an SR module on one and an LR module…
We took over a small aggregation site and one of the 10G uplinks has not come up since the module in it was swapped. The module is listed as incompatible with the CRS226, so that is where suspicion landed first, but the readings do not look like a rejected module to me. MikroTik CRS226 at the…
A Cisco Catalyst 3850-24XS with an SFP-10G-LR (1310 nm) connects over a single-mode cross-connect to a Tier-1 carrier's layer-2 DWDM equipment in the same data center. When the carrier shuts the circuit down, TenGigabitEthernet2/0/23 goes 'down, line protocol is down (notconnect)' yet 'show…
A Chelsio CC2-S320E-SR (110-1114-30) dual-port SFP+ card recognised by TrueNAS would not link to a Dell PowerConnect 6224 through a QSFPTEK 0.5 m passive DAC: no link lights and status: no carrier, even after assigning IPs to cxgb0/cxgb1. Looping the DAC between two switch ports worked, and looping…
A CSS326 (SwOS 2.12) uplinked to an RB4011 throuhg an FS.com 10G active DAC accumulated Rx MAC errors, Rx FCS errors and Tx pauses. Cleaning the DAC connectosr did not help, and the poster asked whether SwOS had SFP+ bugs. Hardware involved: MikroTik CSS326-24G-2S+, MikroTik RB4011, FS.com 10G…
After upgrading to Proxmox VE 8 with the 6.x kernel, on-board Intel X553 SFP+ ports that worked on kernel 5.15.108 showed NO-CARRIER even with the cable and module connected. The regression was traced to an upstream ixgbe commit (565736048bd5) that broke auto-negotiation handling for X550/X553…
The thread starter documented that 82599-based X520 cards carry an undocumented EEPROM bit (IXGBEDEVICECAPSALLOWANYSFP, lowest bit of the capability word at byte offset 0x58, typically 0xFC locked / 0xFD unlocked) that decides whether non-Intel active SFP+ modules are accepted on ESXi and Windows…