重庆思庄Oracle、、PostgreSQL、Redhat认证学习论坛
标题: 虚拟机挂起重启后,rhel7 里面无法启动网卡的解决办法 [打印本页]
作者: 郑全 时间: 2025-6-14 11:51
标题: 虚拟机挂起重启后,rhel7 里面无法启动网卡的解决办法
本帖最后由 郑全 于 2025-6-14 11:53 编辑
[root@kesrac02 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:0c:29:99:74:15 brd ff:ff:ff:ff:ff:ff
3: ens36: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:0c:29:99:74:1f brd ff:ff:ff:ff:ff:ff
发现ens33,ens36 全部没有IP了
看配置文件,都全在
[root@kesrac02 ~]# cd /etc/sysconfig/network-scripts/
[root@kesrac02 network-scripts]# ls -ltr
total 256
-rwxr-xr-x. 1 root root 1876 Dec 9 2018 ifup-TeamPort
-rwxr-xr-x. 1 root root 1755 Dec 9 2018 ifup-Team
-rwxr-xr-x. 1 root root 1556 Dec 9 2018 ifdown-TeamPort
-rwxr-xr-x. 1 root root 1621 Dec 9 2018 ifdown-Team
-rw-r--r--. 1 root root 30988 May 22 2020 network-functions-ipv6
-rw-r--r--. 1 root root 20678 May 22 2020 network-functions
-rwxr-xr-x. 1 root root 5419 May 22 2020 init.ipv6-global
-rwxr-xr-x. 1 root root 1836 May 22 2020 ifup-wireless
-rwxr-xr-x. 1 root root 2780 May 22 2020 ifup-tunnel
-rwxr-xr-x. 1 root root 3303 May 22 2020 ifup-sit
-rwxr-xr-x. 1 root root 2001 May 22 2020 ifup-routes
-rwxr-xr-x. 1 root root 4154 May 22 2020 ifup-ppp
-rwxr-xr-x. 1 root root 4997 May 22 2020 ifup-post
-rwxr-xr-x. 1 root root 1064 May 22 2020 ifup-plusb
-rwxr-xr-x. 1 root root 650 May 22 2020 ifup-plip
-rwxr-xr-x. 1 root root 11893 May 22 2020 ifup-ipv6
-rwxr-xr-x. 1 root root 12075 May 22 2020 ifup-ippp
-rwxr-xr-x. 1 root root 13758 May 22 2020 ifup-eth
-rwxr-xr-x. 1 root root 910 May 22 2020 ifup-bnep
-rwxr-xr-x. 1 root root 12415 May 22 2020 ifup-aliases
-rwxr-xr-x. 1 root root 1462 May 22 2020 ifdown-tunnel
-rwxr-xr-x. 1 root root 1456 May 22 2020 ifdown-sit
-rwxr-xr-x. 1 root root 870 May 22 2020 ifdown-routes
-rwxr-xr-x. 1 root root 1068 May 22 2020 ifdown-ppp
-rwxr-xr-x. 1 root root 2130 May 22 2020 ifdown-post
-rwxr-xr-x. 1 root root 4540 May 22 2020 ifdown-ipv6
-rwxr-xr-x. 1 root root 781 May 22 2020 ifdown-ippp
-rwxr-xr-x. 1 root root 6532 May 22 2020 ifdown-eth
-rwxr-xr-x. 1 root root 654 May 22 2020 ifdown-bnep
-rw-r--r--. 1 root root 254 May 22 2020 ifcfg-lo
-rwxr-xr-x. 1 root root 10357 Oct 14 2020 ifup-ib
-rwxr-xr-x. 1 root root 6190 Oct 14 2020 ifdown-ib
lrwxrwxrwx. 1 root root 24 Dec 6 2024 ifdown -> ../../../usr/sbin/ifdown
lrwxrwxrwx. 1 root root 11 Dec 6 2024 ifdown-isdn -> ifdown-ippp
lrwxrwxrwx. 1 root root 22 Dec 6 2024 ifup -> ../../../usr/sbin/ifup
lrwxrwxrwx. 1 root root 9 Dec 6 2024 ifup-isdn -> ifup-ippp
-rw-r--r-- 1 root root 369 Mar 24 21:08 ifcfg-ens33
-rw-r--r-- 1 root root 360 Mar 24 21:23 ifcfg-Wired_connection_1
[root@kesrac02 network-scripts]# cat ifcfg-ens33
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ens33
DEVICE=ens33
ONBOOT=yes
IPADDR=192.168.133.20
PREFIX=24
GATEWAY=192.168.133.2
DNS1=192.168.133.2
IPV6_PRIVACY=no
UUID=c96bc909-188e-ec64-3a96-6a90982b08ad
[root@kesrac02 network-scripts]# nmcli con
NAME UUID TYPE DEVICE
ens33 c96bc909-188e-ec64-3a96-6a90982b08ad ethernet --
Wired connection 1 2ebc77d7-148f-3008-8a8b-8ccbc010bef8 ethernet --
[root@kesrac02 network-scripts]# ifup ens33
Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged).
[root@kesrac02 network-scripts]# nmcli dev connect ens33
Error: Failed to add/activate new connection: Connection 'ens33' is not available on device ens33 because device is strictly unmanaged
看到一个帖子说,这个表示设备没有被networkmanager管理
这个错误提示表明你的设备(网卡)没有被NetworkManager管理。
在默认情况下,NetworkManager应该会自动管理所有的网络设备,除非在配置文件中明确指定了某些设备不受NetworkManager管理。如果你发现某个设备无法被NetworkManager识别或者管理,可能的原因是:
在NetworkManager的配置文件 /etc/NetworkManager/NetworkManager.conf 中,[keyfile] 部分的 unmanaged-devices
参数包含了你的设备名,例如:unmanaged-devices=interface-name:ens33;
这样NetworkManager就不会去管理ens33设备。
设备正在被其他服务(比如systemd-networkd或者network service)管理,导致NetworkManager无法对其进行管理。
当你执行 nmcli n on 后,NetworkManager开始管理所有的网络设备,因此你的问题得到了解决。你可以通过检查和修改NetworkManager的配置文件来确保它能够正常管理你的网络设备
解决办法:
nmcli n on
root@kesrac02 network-scripts]# nmcli n on
[root@kesrac02 network-scripts]# nmcli con
NAME UUID TYPE DEVICE
ens33 c96bc909-188e-ec64-3a96-6a90982b08ad ethernet ens33
Wired connection 1 2ebc77d7-148f-3008-8a8b-8ccbc010bef8 ethernet ens36
kan'l
欢迎光临 重庆思庄Oracle、、PostgreSQL、Redhat认证学习论坛 (http://bbs.cqsztech.com/) |
Powered by Discuz! X3.2 |