1 Reply Latest reply on Apr 28, 2017 12:52 AM by aiyoh79

    Compatibility between SX1012 40G breakout cable with server with Intel X552 chip

    aiyoh79

      Hi,

       

      I just got a Mellanox SX1012 as well as few break out cables. As i am trying out the breakout cable, i found that it does not work with my Supermicro server (5018D8-AR12L) which has 10G port based on Intel X552.

       

      Below is the lspci info from Supermicro server

       

      04:00.0 Ethernet controller: Intel Corporation Ethernet Connection X552 10 GbE SFP+

      04:00.1 Ethernet controller: Intel Corporation Ethernet Connection X552 10 GbE SFP+

       

      The same breakout cable does work for another server from Gigabyte which has on board Mellanox chip.

       

      84:00.0 Ethernet controller: Mellanox Technologies MT27520 Family [ConnectX-3 Pro]

       

      Is there any issue when the breakout cable is used on adapter other than from Mellanox? Thanks.

       

      Cw

       

      5018D8-AR12L

        • Re: Compatibility between SX1012 40G breakout cable with server with Intel X552 chip
          aiyoh79

          Just to share more information:

           

          The system (Ubuntu 16.04) can detect that this is a DAC module but can't detect speed and duplex mode.

           

          Settings for eno7:

                  Supported ports: [ FIBRE ]

                  Supported link modes:   10000baseT/Full

                  Supported pause frame use: Symmetric

                  Supports auto-negotiation: No

                  Advertised link modes:  10000baseT/Full

                  Advertised pause frame use: Symmetric

                  Advertised auto-negotiation: No

                  Speed: Unknown!

                  Duplex: Unknown! (255)

                  Port: Direct Attach Copper

                  PHYAD: 0

          Transceiver: external

          Auto-negotiation: off

                  Supports Wake-on: d

                  Wake-on: d

                  Current message level: 0x00000007 (7)

          drv probe link

                  Link detected: no

           

          ethtool -m eno7

          Identifier : 0x03 (SFP)

                  Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)

          Connector : 0x21 (Copper pigtail)

                  Transceiver codes : 0x01 0x00 0x00 0x04 0x00 0x04 0x80 0xd5

                  Transceiver type : Infiniband: 1X Copper Passive

                  Transceiver type : Ethernet: 1000BASE-CX

                  Transceiver type : FC: Copper Passive

                  Transceiver type : FC: Twin Axial Pair (TW)

                  Transceiver type : FC: 1200 MBytes/sec

                  Transceiver type : FC: 800 MBytes/sec

                  Transceiver type : FC: 400 MBytes/sec

                  Transceiver type : FC: 200 MBytes/sec

                  Transceiver type : FC: 100 MBytes/sec

          Encoding : 0x00 (unspecified)

                  BR, Nominal : 10300MBd

                  Rate identifier : 0x00 (unspecified)

                  Length (SMF,km) : 0km

                  Length (SMF) : 0m

                  Length (50um) : 0m

                  Length (62.5um) : 0m

                  Length (Copper) : 3m

                  Length (OM3) : 0m

                  Passive Cu cmplnce. : 0x01 (SFF-8431 appendix E) [SFF-8472 rev10.4 only]

                  Vendor name : Mellanox

                  Vendor OUI : 00:02:c9

                  Vendor PN : MC2609130-003

                 Vendor rev : A3

                  Option values : 0x00 0x00

                  BR margin, max : 0%

                  BR margin, min : 0%

                  Vendor SN : MT1713VS01917

                  Date code : 170323

           

          Trying to set the speed or advertise the correct speed also not working.

           

          ethtool -s eno7 speed 10000

          Cannot set new settings: Invalid argument

            not setting speed

          ethtool -s eno7 advertise 0x1000

          Cannot set new settings: Invalid argument

           

          Is there any more thing i can try, does using other cable such as cable from Intel a possible solution?

           

          Cw