rhel 7 network connected with no carrier
Hi i've configured an ethernet with ip4 connection
on vmware i disconnect the cable but the connection looks up with no carrier.
DEVICE TYPE STATE CONNECTION
eno16780032 ethernet connected eno16780032
lo loopback unmanaged --
eno16780032: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:50:56:94:3c:da brd ff:ff:ff:ff:ff:ff
inet A.B.C.D/24 brd A.B.C.255 scope global eno16780032
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe94:3cda/64 scope link
valid_lft forever preferred_lft forever
which part of is missing?
thanks
Responses
Red Hat
Guru
7252 points
UP means the interface is "logically up", the operating system has been told to activate the interface. Usually the next step after this is to add an IP address, either manually or via DHCP.
NO-CARRIER means link is not detected. On a real NIC, this would be the physical cable being plugged in or not.
Red Hat
Guru
7252 points
You stated "on vmware i disconnect the cable".
If you've made a virtual cable "disconnected" in the virtualization platform, this is evidently represented as a disconnected state in the virtual network interface.
centos7.5 replaced RHEL 6.8 , now backups are slower network VM card is vmxnet 3
ethtool ens192 Settings for ens192: Supported ports: [ TP ] Supported link modes: 1000baseT/Full 10000baseT/Full Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 10000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Supports Wake-on: uag Wake-on: d
Why ?
Red Hat
Guru
7252 points
This could be many things. If it's a backup workload, it could be disk-bound and perhaps some filesystem difference is the restriction.
If the new system was RHEL 7, I would suggest you open a support case to investigate the specific issue more.
As it is CentOS 7, you can't get support from us. You could try on the CentOS forum. You could look up use of Linux performance tools to identify bottlenecks.
We provide several scripts which collect relevant data such as monitor.sh and watcher-cron but on CentOS the analysis of the collected data is up to you.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.