ethernet not coming online after remote reboot
 

I have a Centos7 machine that has some odd behavior with its ethernet ports.

When sitting at the server console i can reboot the system normally and networking functions as expected. Whenever the system is rebooted remotely the ethernet port will not come online until the cable is removed and reconnected.

after a remote reboot I can visit the console and login as a local account but cannot bring the interface online without removing and replacing the cable.

my /etc/sysconfig/network file is simple

# Created by anaconda
NETWORKING=yes

the interface file is as follows
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=RightPort
UUID=71345fbb-7f98-4bd1-bd0b-309a255dfd2d
DEVICE=enp2sOf1
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_PRIVACY=no
NM_CONTROLLED=no


i have added the NM_CONTROLLED line for troubleshooting, i have tried putting the values for onboot and nm_controlled in quotes as shown in various forums and guides i have read through, but I cannot figure this out.

Does anyone have a suggestion?

Why are you using DHCP on a server?

How are you rebooting remotely?

that is the interface file, I suppose i should have said it differently than "the interface file is as follows"
that is my ifcfg-enp2s0f1 file. the network file is only one line long.

I am using DHCP because I do not control the network here. I create a reservation in a webportal so as to get the same address after reboot (not my preferred method but it is what I have to work with). my problem is not with addressing though. I don't get any link lights until i unplug and replace the cable.

when rebooting remotely via ssh i have tried using the reboot command, and shutdown -r 0. both have the same effect.

what is most curious to me is that when i reboot from the console the network comes up every time, it it only when I reboot from an ssh session that i have network problems. i am able to replicate it locally at the console by connecting via ssh to the localhost and issuing the reboot command.

Yeah, I cannot explain this. I'm guessing that the variable NAME doesn't have to match the DEVICE like it does on all my machines.

Send reboot and add in some small wait. Then log off really quick. ???

No dice renaming the port or delaying the shutdown. I am perplexed.

Did you delay and log off? When I've seen this before I'd have to be logged off before the shutdown began.

Maybe some /var logs might reveal the issue.