Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #194348

Re: All of my enoX interfaces are mapped to eth0

Show all headers | View raw

On Fri 30 Mar 2018 at 16:19:30 (-0400), David Parker wrote:
> Hello,
> 
> I have two identical HP servers running Debian 9.  One of them is a clean
> install of 9, whereas the other was upgraded from Debian 8.
> 
> The one that was upgraded has no networking issues (indeed, it still uses
> the ethX interface names).  However, the one that was installed from
> scratch is having an issue which I can't seem to figure out.  There are 4
> network interfaces -- eno[1-4] -- but they are all getting mapped to eth0.
> It looks like they were mapped correctly until I reloaded the network
> driver a few days ago.  Any idea how I can get them back into a 1:1 mapping
> with the actual physical interfaces, instead of all pointing to the same
> one?
> 
> Some dmesg output for reference:
> 
> [Wed Mar 28 17:00:45 2018] tg3.c:v3.137 (May 11, 2014)
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.0 eth0: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e0
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.0 eth0: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.0 eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.0 eth0: dma_rwctrl[00000001]
> dma_mask[64-bit]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.1 eth1: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e1
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.1 eth1: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.1 eth1: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.1 eth1: dma_rwctrl[00000001]
> dma_mask[64-bit]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.2 eth2: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e2
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.2 eth2: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.2 eth2: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.2 eth2: dma_rwctrl[00000001]
> dma_mask[64-bit]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.3 eth3: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e3
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.3 eth3: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.3 eth3: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:00:45 2018] tg3 0000:03:00.3 eth3: dma_rwctrl[00000001]
> dma_mask[64-bit]
> 
> 
> 
> *[Wed Mar 28 17:00:45 2018] tg3 0000:03:00.1 eno2: renamed from eth1[Wed
> Mar 28 17:00:45 2018] tg3 0000:03:00.0 eno1: renamed from eth0[Wed Mar 28
> 17:00:45 2018] tg3 0000:03:00.3 eno4: renamed from eth3[Wed Mar 28 17:00:45
> 2018] tg3 0000:03:00.2 eno3: renamed from eth2*
> 
> Looks fine, but then...
> 
> [Wed Mar 28 17:12:33 2018] tg3.c:v3.137 (May 11, 2014)
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.0 eth0: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e0
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.0 eth0: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.0 eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.0 eth0: dma_rwctrl[00000001]
> dma_mask[64-bit]
> *[Wed Mar 28 17:12:33 2018] tg3 0000:03:00.0 eno1: renamed from eth0*
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.1 eth0: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e1
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.1 eth0: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.1 eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.1 eth0: dma_rwctrl[00000001]
> dma_mask[64-bit]
> *[Wed Mar 28 17:12:33 2018] tg3 0000:03:00.1 eno2: renamed from eth0*
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.2 eth0: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e2
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.2 eth0: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.2 eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.2 eth0: dma_rwctrl[00000001]
> dma_mask[64-bit]
> *[Wed Mar 28 17:12:33 2018] tg3 0000:03:00.2 eno3: renamed from eth0*
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.3 eth0: Tigon3
> [partno(629133-001) rev 5719001] (PCI Express) MAC address d8:9d:67:2c:ec:e3
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.3 eth0: attached PHY is 5719C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.3 eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[1] TSOcap[1]
> [Wed Mar 28 17:12:33 2018] tg3 0000:03:00.3 eth0: dma_rwctrl[00000001]
> dma_mask[64-bit]
> *[Wed Mar 28 17:12:33 2018] tg3 0000:03:00.3 eno4: renamed from eth0*
> 
> I should note that this server is now in production, so it would be
> fantastic if I can solve this without taking down eno1 as that is the
> primary network link.  Any help is greatly appreciated.

Colour me stupid but can you explain what the problem is. All I see is
two sets of logs, both of which result in this assignment:

 eno1: MAC address d8:9d:67:2c:ec:e0
 eno2: MAC address d8:9d:67:2c:ec:e1
 eno3: MAC address d8:9d:67:2c:ec:e2
 eno4: MAC address d8:9d:67:2c:ec:e3

Your system is using scheme 1 to arrive at this state:
"Names incorporating Firmware/BIOS provided index numbers
for on-board devices (example: eno1)".

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

All of my enoX interfaces are mapped to eth0 David Parker <dparker@utica.edu> - 2018-03-30 22:30 +0200
  Re: All of my enoX interfaces are mapped to eth0 David Wright <deblis@lionunicorn.co.uk> - 2018-03-31 02:00 +0200
    Re: All of my enoX interfaces are mapped to eth0 David Parker <dparker@utica.edu> - 2018-03-31 04:10 +0200
      Re: All of my enoX interfaces are mapped to eth0 David Wright <deblis@lionunicorn.co.uk> - 2018-03-31 04:40 +0200
        Re: All of my enoX interfaces are mapped to eth0 David Parker <dparker@utica.edu> - 2018-03-31 05:20 +0200
          Re: All of my enoX interfaces are mapped to eth0 David Wright <deblis@lionunicorn.co.uk> - 2018-03-31 16:20 +0200
            Re: All of my enoX interfaces are mapped to eth0 David Parker <dparker@utica.edu> - 2018-04-02 17:40 +0200
              Re: All of my enoX interfaces are mapped to eth0 David Wright <deblis@lionunicorn.co.uk> - 2018-04-02 20:50 +0200

csiph-web