Re: [CentOS] CentOS 7.3 and e1000e

2017-07-09 Thread Eliezer Croitoru
What I did on couple of my CentOS boxes is:
- use a bridge which is connected to the specific nic(will always look as up
after boot)
- Run a cron script that checks if the nic state is "NO-CARRIER" or other
weird situations like no  IP address and try to run ifdown X-nic and then
ifup X-nic.

Depends on the hardware and situation you might need to choose what fits
youe environment as a solution instead of fixing the whole CentOS distro.

All The Bests,
Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il



-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Jerry Geis
Sent: Saturday, July 8, 2017 05:00
To: CentOS mailing list <centos@centos.org>
Subject: [CentOS] CentOS 7.3 and e1000e

Hi All  - I have a box running the above. Power was lost long enough that
UPS did not work. When power came back on the C7 box boots way faster than
the switch and resulted in no network. power cycling the C7 box resulted in
network.

This even happened a second time. The only way to get the box back was to
power cycle. the box is remote and no keyboard and mouse connected.

Any thoughts on why the e1000e would not talk to the switch ? The switch is
an unmanaged linksys - could not get the model. It auto negotiates to
1G/full.

Thanks, for any thoughts.

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-09 Thread Richard Beels


At 07/07/2017 at 22:00, Shakespearean monkeys danced on Jerry Geis's 
keyboard and said:



Any thoughts on why the e1000e would not talk to the switch ? The switch is
an unmanaged linksys - could not get the model. It auto negotiates to
1G/full.


+1 on the switch not being completely up itself.

You could also stick in a (longer) pause at the boot screen.

Cheers!

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-08 Thread John Jasen
This may be the wrong approach, but install the
NetworkManager-config-server rpm. It sets a config option to allow
interfaces to be configured before being available, which may help.



On 07/08/2017 07:45 AM, Jerry Geis wrote:
>> Do you use NetworkManager or the network sysv service?
> I use the sysv service
> Thanks,
>
> Jerry
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-08 Thread Jonathan Billings
On Jul 8, 2017, at 7:45 AM, Jerry Geis  wrote:
>> Do you use NetworkManager or the network sysv service?
> 
> I use the sysv service

Had you used NetworkManager, it would have detected the network coming up and 
started networking.  This is one of the reasons why I continue to use NM for 
our servers, I’ve been in similar situations (where power is restored to the 
rack with computers in it before to the rack with the networking equipment).  
The ‘network’ sysv service just runs once and gives up if it can’t bring up the 
network.

The problem with LINKDELAY= is that it will always slow down the network 
service (even if the network is fine), and if you set it too high, might cause 
other services which rely on it to time out.  


--
Jonathan Billings 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-08 Thread Jerry Geis
>Do you use NetworkManager or the network sysv service?

I use the sysv service
Thanks,

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-08 Thread Jonathan Billings
On Jul 7, 2017, at 10:00 PM, Jerry Geis  wrote:
> Hi All  - I have a box running the above. Power was lost long enough that
> UPS did not work. When power came back on the C7 box boots way faster than
> the switch and resulted in no network. power cycling the C7 box resulted in
> network.


Do you use NetworkManager or the network sysv service?

--
Jonathan Billings 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-08 Thread Tru Huynh
On Fri, Jul 07, 2017 at 10:00:17PM -0400, Jerry Geis wrote:
> Hi All  - I have a box running the above. Power was lost long enough that
> UPS did not work. When power came back on the C7 box boots way faster than
> the switch and resulted in no network. power cycling the C7 box resulted in
> network.

/usr/share/doc/initscripts-9.49.37/sysconfig.txt
...
/etc/sysconfig/network-scripts/ifcfg- and
...
LINKDELAY=
  Time that the system should pause after the specific interface is
  enabled.  This may be useful if one interface is connected to a
  switch which has spanning tree enabled and must wait for STP to
  converge before the interface should be considered usable.
...

Tru

-- 
Tru Huynh 
http://pgp.mit.edu:11371/pks/lookup?op=get=0xBEFA581B


pgpnWN2dF7P2J.pgp
Description: PGP signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.3 and e1000e

2017-07-08 Thread John R Pierce

On 7/7/2017 7:00 PM, Jerry Geis wrote:

Hi All  - I have a box running the above. Power was lost long enough that
UPS did not work. When power came back on the C7 box boots way faster than
the switch and resulted in no network. power cycling the C7 box resulted in
network.



an unmanaged switch should be live within milliseconds of power being 
applied, it doesn't make sense that an OS could boot up before its working.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS 7.3 and e1000e

2017-07-07 Thread Jerry Geis
Hi All  - I have a box running the above. Power was lost long enough that
UPS did not work. When power came back on the C7 box boots way faster than
the switch and resulted in no network. power cycling the C7 box resulted in
network.

This even happened a second time. The only way to get the box back was to
power cycle. the box is remote and no keyboard and mouse connected.

Any thoughts on why the e1000e would not talk to the switch ? The switch is
an unmanaged linksys - could not get the model. It auto negotiates to
1G/full.

Thanks, for any thoughts.

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos