Missing eth0 after upate to 7.7

[Francesco Alfano]

I have update to 7.7 and now i missing network connection: The ifconfig eth0 
returnsDevice not found.
How can I resolve the problem ?

Re: Missing eth0 after upate to 7.7

[Steven C Timm]

I don’t know about your machine but I have seen on other SL7 machines that what 
was eth0 turns to eth1 and so forth.  Do ifconfig -a
That will show you all interfaces on the machine.  Then use ethtool on them to 
see which one has the link.

Steve

From: owner-scientific-linux-us...@listserv.fnal.gov 
 on behalf of Francesco Alfano 
<0bdf64e162f4-dmarc-requ...@listserv.fnal.gov>
Sent: Wednesday, September 11, 2019 6:42:05 AM
To: scientific-linux-users 
Subject: Missing eth0 after upate to 7.7

I have update to 7.7 and now i missing network connection:
The ifconfig eth0 returns
Device not found.

How can I resolve the problem ?

Re: SL6 end of life

[Dobos, Tamas]

Dear Scientific Linux users/contributors,
Our product is currently based on SL 6.10 and we are looking for the 
information whether it is possible to have long term support from Security 
point of view after SL6 will reach EOL. 
I know that RHEL 6 ELS will be continued after November 30, 2020 till June 30, 
2024 for additional subscription.
Unfortunately upgrading to SL7 would be costly for us.

Do you know whether we can get Extended Life-cycle Support for the SL6 somehow?

Thanks and best regards,
Tamás

Re: Missing eth0 after upate to 7.7

[Teh, Kenneth M.]

systemd based machines don't use ethX anymore. There is a more reliable naming 
scheme described here.

> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.freedesktop.org_wiki_Software_systemd_PredictableNetworkInterfaceNames_&d=DwIF-g&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=r6yNOWImSOHQP7nksDZAzQXDRFb52SFP3q08jQNE358&s=2gqVMIg2JhFlhK_y-M-bVzc7nP1586T5HmS4c3vX5hs&e=
>  

I've been using the #3 scheme which is based on the geographical location of 
the 
network card. The system will prefer schemes #1 and #2 if the bios numbers them 
but #3 always works nevertheless during installs.



On 9/11/19 6:51 AM, Steven C Timm wrote:
> I don’t know about your machine but I have seen on other SL7 machines that 
> what 
> was eth0 turns to eth1 and so forth.  Do ifconfig -a
> That will show you all interfaces on the machine.  Then use ethtool on them 
> to 
> see which one has the link.
> 
> Steve
> 
> *From:* owner-scientific-linux-us...@listserv.fnal.gov 
>  on behalf of Francesco 
> Alfano 
> <0bdf64e162f4-dmarc-requ...@listserv.fnal.gov>
> *Sent:* Wednesday, September 11, 2019 6:42:05 AM
> *To:* scientific-linux-users 
> *Subject:* Missing eth0 after upate to 7.7
> I have update to 7.7 and now i missing network connection:
> The ifconfig eth0 returns
> Device not found.
> 
> How can I resolve the problem ?

Re: Missing eth0 after upate to 7.7

[Steven C Timm]

At Fermilab we have a lot of machines on which systemd/udev still falls through 
to the unpredictable ethX system of naming  (#5 scheme in the article you 
referred to below) and whose eth0-eth4 rearrange themselves on every reboot.  
Quite an issue if you are trying to make bridged networks out of them.

Since Francesco's system is using the 3rd method and calling his interface 
enp3s0, that is not his problem. think his main problem is getting a link 
light--and those can come and go as well in most versions of SL7.

Steve




From: Teh, Kenneth M. 
Sent: Wednesday, September 11, 2019 9:02 AM
To: Steven C Timm ; scientific-linux-users 
; edace...@yahoo.it 
Subject: Re: Missing eth0 after upate to 7.7

systemd based machines don't use ethX anymore. There is a more reliable naming
scheme described here.

> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.freedesktop.org_wiki_Software_systemd_PredictableNetworkInterfaceNames_&d=DwIF-g&c=gRgGjJ3BkIsb5y6s49QqsA&r=10BCTK25QMgkMYibLRbpYg&m=vZT0HjMvd2fgq2QWE2bKe2tPO2kV2oZlv4_YnyhdXPc&s=zgJQ8rvbvqFcZwlaL-M3FTu-OUoFYlH0yXXWzuTbcBw&e=

I've been using the #3 scheme which is based on the geographical location of the
network card. The system will prefer schemes #1 and #2 if the bios numbers them
but #3 always works nevertheless during installs.



On 9/11/19 6:51 AM, Steven C Timm wrote:
> I don’t know about your machine but I have seen on other SL7 machines that 
> what
> was eth0 turns to eth1 and so forth.  Do ifconfig -a
> That will show you all interfaces on the machine.  Then use ethtool on them to
> see which one has the link.
>
> Steve
> 
> *From:* owner-scientific-linux-us...@listserv.fnal.gov
>  on behalf of Francesco Alfano
> <0bdf64e162f4-dmarc-requ...@listserv.fnal.gov>
> *Sent:* Wednesday, September 11, 2019 6:42:05 AM
> *To:* scientific-linux-users 
> *Subject:* Missing eth0 after upate to 7.7
> I have update to 7.7 and now i missing network connection:
> The ifconfig eth0 returns
> Device not found.
>
> How can I resolve the problem ?

Re: Missing eth0 after upate to 7.7 (Solved)

[Francesco Alfano]

Thanks for your time,I  solved the problem this way:
in /etc/udev/rules.d
I created the file:
70-persistent-net.rules
with the following content:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="20:cf:30:f2:e1:ad", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

so I restarted the PC (!) and configured the network with nm-connection-editor .
I could probably use
 udevadm control --reload-rules && udevadm trigger


instead of rebooting, but it doesn't seem to have worked.

Il mercoledì 11 settembre 2019, 16:02:46 CEST, Teh, Kenneth M. 
<0864eace5c83-dmarc-requ...@listserv.fnal.gov> ha scritto:  
 
 systemd based machines don't use ethX anymore. There is a more reliable naming 
scheme described here.

> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.freedesktop.org_wiki_Software_systemd_PredictableNetworkInterfaceNames_&d=DwIF-g&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=r6yNOWImSOHQP7nksDZAzQXDRFb52SFP3q08jQNE358&s=2gqVMIg2JhFlhK_y-M-bVzc7nP1586T5HmS4c3vX5hs&e=
>  

I've been using the #3 scheme which is based on the geographical location of 
the 
network card. The system will prefer schemes #1 and #2 if the bios numbers them 
but #3 always works nevertheless during installs.



On 9/11/19 6:51 AM, Steven C Timm wrote:
> I don’t know about your machine but I have seen on other SL7 machines that 
> what 
> was eth0 turns to eth1 and so forth.  Do ifconfig -a
> That will show you all interfaces on the machine.  Then use ethtool on them 
> to 
> see which one has the link.
> 
> Steve
> 
> *From:* owner-scientific-linux-us...@listserv.fnal.gov 
>  on behalf of Francesco 
> Alfano 
> <0bdf64e162f4-dmarc-requ...@listserv.fnal.gov>
> *Sent:* Wednesday, September 11, 2019 6:42:05 AM
> *To:* scientific-linux-users 
> *Subject:* Missing eth0 after upate to 7.7
> I have update to 7.7 and now i missing network connection:
> The ifconfig eth0 returns
> Device not found.
> 
> How can I resolve the problem ?
  

Re: [EXTERNAL] Re: Missing eth0 after upate to 7.7

[ONeal, Miles]

I have always tied MAC addresses to the EthX ports. One problem solved.

-Miles

On Sep 11, 2019, at 09:09, Steven C Timm mailto:t...@fnal.gov>> 
wrote:

At Fermilab we have a lot of machines on which systemd/udev still falls through 
to the unpredictable ethX system of naming  (#5 scheme in the article you 
referred to below) and whose eth0-eth4 rearrange themselves on every reboot.  
Quite an issue if you are trying to make bridged networks out of them.

Since Francesco's system is using the 3rd method and calling his interface 
enp3s0, that is not his problem. think his main problem is getting a link 
light--and those can come and go as well in most versions of SL7.

Steve




From: Teh, Kenneth M. mailto:t...@anl.gov>>
Sent: Wednesday, September 11, 2019 9:02 AM
To: Steven C Timm mailto:t...@fnal.gov>>; scientific-linux-users 
mailto:scientific-linux-users@fnal.gov>>; 
edace...@yahoo.it 
mailto:edace...@yahoo.it>>
Subject: Re: Missing eth0 after upate to 7.7

systemd based machines don't use ethX anymore. There is a more reliable naming
scheme described here.

> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.freedesktop.org_wiki_Software_systemd_PredictableNetworkInterfaceNames_&d=DwIF-g&c=gRgGjJ3BkIsb5y6s49QqsA&r=10BCTK25QMgkMYibLRbpYg&m=vZT0HjMvd2fgq2QWE2bKe2tPO2kV2oZlv4_YnyhdXPc&s=zgJQ8rvbvqFcZwlaL-M3FTu-OUoFYlH0yXXWzuTbcBw&e=

I've been using the #3 scheme which is based on the geographical location of the
network card. The system will prefer schemes #1 and #2 if the bios numbers them
but #3 always works nevertheless during installs.



On 9/11/19 6:51 AM, Steven C Timm wrote:
> I don’t know about your machine but I have seen on other SL7 machines that 
> what
> was eth0 turns to eth1 and so forth.  Do ifconfig -a
> That will show you all interfaces on the machine.  Then use ethtool on them to
> see which one has the link.
>
> Steve
> 
> *From:* 
> owner-scientific-linux-us...@listserv.fnal.gov
> mailto:owner-scientific-linux-us...@listserv.fnal.gov>>
>  on behalf of Francesco Alfano
> <0bdf64e162f4-dmarc-requ...@listserv.fnal.gov>
> *Sent:* Wednesday, September 11, 2019 6:42:05 AM
> *To:* scientific-linux-users 
> mailto:scientific-linux-users@fnal.gov>>
> *Subject:* Missing eth0 after upate to 7.7
> I have update to 7.7 and now i missing network connection:
> The ifconfig eth0 returns
> Device not found.
>
> How can I resolve the problem ?

Re: SL6 end of life

[David Sommerseth]

On 11/09/2019 13:46, Dobos, Tamas wrote:
> Dear Scientific Linux users/contributors,
> Our product is currently based on SL 6.10 and we are looking for the 
> information whether it is possible to have long term support from Security 
> point of view after SL6 will reach EOL. 
> I know that RHEL 6 ELS will be continued after November 30, 2020 till June 
> 30, 2024 for additional subscription.
> Unfortunately upgrading to SL7 would be costly for us.
> 
> Do you know whether we can get Extended Life-cycle Support for the SL6 
> somehow?

I would suggest having a talk with Red Hat about migrating your SL6 systems to
RHEL-6 systems.  Then you can sign up for the RHEL-6 ELS with them.

I have a hard time imagine anyone in the community would spend lots of time
and energy of their already restricted budgets (both in time and money
perspective) to help you save some money.  Which is why I rather recommend you
have a talk with Red Hat, as they do allocate time and resources to deliver
such a product already.

Just my 2cents.


-- 
kind regards,

David Sommerseth

Re: SL6 end of life

[Nico Kadel-Garcia]

On Wed, Sep 11, 2019 at 2:49 PM David Sommerseth
 wrote:
>
> On 11/09/2019 13:46, Dobos, Tamas wrote:
> > Dear Scientific Linux users/contributors,
> > Our product is currently based on SL 6.10 and we are looking for the 
> > information whether it is possible to have long term support from Security 
> > point of view after SL6 will reach EOL.
> > I know that RHEL 6 ELS will be continued after November 30, 2020 till June 
> > 30, 2024 for additional subscription.
> > Unfortunately upgrading to SL7 would be costly for us.
> >
> > Do you know whether we can get Extended Life-cycle Support for the SL6 
> > somehow?
>
> I would suggest having a talk with Red Hat about migrating your SL6 systems to
> RHEL-6 systems.  Then you can sign up for the RHEL-6 ELS with them.

It is also possible to migrate a live system from SL 6 to RHEL 6, and
back. It's a pain in the keister, since there are some conflicting
components such as "sl-release" and "redhat-release", and you have to
re-install every single RPM in order to be sure of consistent content.
But it can be done.

> I have a hard time imagine anyone in the community would spend lots of time
> and energy of their already restricted budgets (both in time and money
> perspective) to help you save some money.  Which is why I rather recommend you
> have a talk with Red Hat, as they do allocate time and resources to deliver
> such a product already.
>
> Just my 2cents.
>
>
> --
> kind regards,
>
> David Sommerseth