Ethernet showing disconnected

Issues related to configuring your network
Post Reply
samnetic
Posts: 4
Joined: 2017/06/12 11:33:56

Ethernet showing disconnected

Post by samnetic » 2017/06/12 11:40:40

Hello,

We have this Centos 7.3.1611 (64 bit) server (kernel 3.10.0-514.10.2.el7.x86_64).

It recently became inaccessible.

When we checked our NOC control panel, we could see the ethernet showing as disconnected.

Our NOC mentioned they see following error on server console:
error rshosting.PNG
error rshosting.PNG (20.6 KiB) Viewed 2755 times
The server came back on its own without any changes made and the NOC mentioned server was disconnected as link went down due to above error.

Can someone please advise what is that error related to?

I searched on google, and someone suggested about port range. I checked the port range on our server and it is as follows:

cat /proc/sys/net/ipv4/ip_local_port_range
24576 65534

Any help will be greatly appreciated.
Thanks in advance.

aks
Posts: 3073
Joined: 2014/09/20 11:22:14

Re: Ethernet showing disconnected

Post by aks » 2017/06/12 16:12:30

/proc/sys/net/ipv4/ip_local_port_range
That's the local port range see http://www.faqs.org/docs/securing/chap6sec70.html (a little dated now, but valid none the less). Usually used for "ephemeral ports" see https://en.wikipedia.org/wiki/Ephemeral_port

Anything in dmesg and/or journalctl?

User avatar
TrevorH
Site Admin
Posts: 33218
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Ethernet showing disconnected

Post by TrevorH » 2017/06/12 16:22:55

I don't think that ip_local_port_range has anything to do with the subsequent errors.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

samnetic
Posts: 4
Joined: 2017/06/12 11:33:56

Re: Ethernet showing disconnected

Post by samnetic » 2017/06/13 09:40:41

Thank you for your replies. I just wanted to confirm the same.

Our NOC confirmed it was bad ethernet cable. Thank you for clearing my doubt as our NOC support was relating the error with network connectivity and I was doubtful for the same, hence wanted to confirm before I could argue with them.

The issue is resolved, so we can safely close this thread.

Post Reply