Italy joined 11 months ago
6 questions
11 comments
Network engineer from Turin. Mostly Dell and HPE.
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…
On a Lanner NCA-1510 the four Intel X553 ports (ix0-ix3) worked, but two Intel I210 Gigabit Fiber Network Connection interfaces (device 0x15368086) with SFP cages were absent in OPNsense even after loading ifigb via tunables; pfSense detected them by default. Another user had the same with a…
Putting a fibre run between two comms rooms in the same building and using a pair of TRENDnet TFC-1000MSC converters (1000BASE-T to 1000BASE-SX) to bridge it. Copper side goes straight into the switches we already have, nothing unusual in the config. TRENDnet TFC-1000MSC at each end, each on its…
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…
Intel X520 (82599) cards enforce a list of approved SFP+ modules; under Linux the ixgbe parameter helps, but on Windows or ESXi there is no such option. The gist provides a Python script that reads the card EEPROM with ethtool -e and sets bit 0 of the byte at offset 0x58 (0 = Intel modules only, 1…
On an HP 5120-EI the poster inserted an Allied Telesis AT-SPEX 1310 nm SFP and got a PHONY ENTITY trap plus OPTMOD/4/FIBERSFPMODULENOWINVALID: This is not a supported transceiver for this platform; the port never came up. The poster looked for a command to disable enforcement of SFP coding. Later…