Network interface state "DOWN"

TrueNAS General
1

Hello, This is my first post here so I’ll do my best to supply you with as much information as I can to make this easier.

Problem: The interface I use for iSCSI connections is set to DOWN and I can not bring it back up. I get 100% packet loss when pinging the address I assigned to the interface from all sources.

You should also note, this connection is a direct line from my TrueNAS box to my desktop via 10gb Twinax. My desktop interface is configured to 10.10.10.1 The TrueNAS interface is set to 10.10.10.2/2

Also to be clear, this has worked for quite some time, just yesterday when I booted the trueNAS box up everything looked normal it gave me the option to view the webui from https://10.10.10.2/ (it didn’t work but it was listed in the “The Web user interface is at:”)

I have checked and triple checked the settings are correct on both systems, also since both systems use Intel(R) Ethernet Server Adapter X520-2’s which are dual port, I tried using the other port disabling the one not in use.

Here is a ifconfig -a dump

root@truenas[~]# ifconfig -a
ix0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: 10gbtwinax
        options=4e53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
        ether 90:e2:ba:cb:6f:20
        inet 10.10.10.2 netmask 0xc0000000 broadcast 63.255.255.255
        media: Ethernet autoselect
        status: no carrier
        nd6 options=9<PERFORMNUD,IFDISABLED>
ix1: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4e53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
        ether 90:e2:ba:cb:6f:21
        media: Ethernet autoselect
        status: no carrier
        nd6 options=9<PERFORMNUD,IFDISABLED>
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether fc:aa:14:9d:02:50
        inet 192.168.0.24 netmask 0xffffff00 broadcast 192.168.0.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
        groups: pflog

ix0 is the interface in question.

Thank you for your time and please advise if you require any additional information.

2

ix0 and ix1 show no carrier. Twinax? Is that a DAC setup?
Do you have two intel coded transceivers and a fiber patch cable to test or another DAC?

3

So Twinax is a type of copper cable that allows for 10BG bandwidth by having the SFP built into the cable itself. here’s an image of one.
Twinax Cable

I do not have any fiber in my setup, just 1 CAT6 for the WebUI and the 10Gb Twinax for the iSCSI connection. I do have other Twinax cables and have tested them with the same results.

4

do you see ‘SFP unsupported’ messages on TrueNAS on the console? I forgot to ask what version of TrueNAS. The message and the bypass for unsupported SFP transceivers is different between Core and Scale. I am wondering if that is the issue.

I recently put in two of those NICS and I had to do the bypass on TrueNAS core with Avago transceiver and Windows HAD to have an Intel coded transceiver. I went with ones from 10GTek but FS.com is also a source I have seen mentioned.

Does the ifconfig -a dump look the same if you boot without the cable plugged in? Guessing bad transceiver on one end and/or mismatched transceiver coding to the NIC with other cables.

I think you can try hot plugging if you have static ip set on both machines.

5

I have no idea what I did that fixed the issue, but in any case, it’s working as intended again. Thank you for your time and consideration.

1 Like