☰

systemd 分析责任

tag-icon • tag-icon centos networking ip ip-address
systemd 分析责任

问题是

第一个问题：为什么我需要在登录屏幕出现后等待 eno3 5 分钟和 eno4 10 分钟的链接。我能做些什么吗？如果我尝试手动启动任何 eth，它会给我错误消息链接尚未准备好。

第二个问题：托管公司是否有可能设置此服务器必须通过 ip6 然后通过 ip4 连接其设备的方式（如果是这样）我是否需要将 ipv6 设置为静态来消除此问题？

在 centos 登录屏幕之前，我看不到任何路由。

[root@gtw4-ab ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

5 分钟后，第一个以太网自动启动

ixgbe 0000:01:00.1 eno4 NIC link is up 10gbps flow control rx-tx
IPv6 ADDRCONF(NETDEV_CHANGE): eno4 link becomes ready

[root@gtw4-ab ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     101    0        0 eno4

10 分钟后第二个以太网启动

ixgbe 0000:01:00.1 eno3 NIC link is up 10gbps flow control rx-tx
IPv6 ADDRCONF(NETDEV_CHANGE): eno3 link becomes ready

[root@gtw4-ab ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         91.115.6.254    0.0.0.0         UG    100    0        0 eno3
91.115.6.0      0.0.0.0         255.255.255.0   U     100    0        0 eno3
192.168.0.0     0.0.0.0         255.255.255.0   U     101    0        0 eno4

IP地址

[root@gtw4-ab ~]# 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: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether xx:xx:xx:xx:77:a2 brd ff:ff:ff:ff:ff:ff
    inet 91.115.6.100/32 scope global noprefixroute eno3
       valid_lft forever preferred_lft forever
    inet6 xxxx::xxxx:xxxx:xxx:77a2/64 scope link
       valid_lft forever preferred_lft forever
3: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether xx:xx:xx:x:77:a3 brd xx:x:ff:ff:ff:ff
    inet 192.168.0.20/24 brd 192.168.0.255 scope global noprefixroute eno4
       valid_lft forever preferred_lft forever
    inet6 xxx::xxxx:xxxx:xxxx:77a3/64 scope link
       valid_lft forever preferred_lft forever

伊诺3

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
IPADDR=91.115.6.100
PREFIX=32
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=eno3
UUID=xxxxx-xxxx-xxxx-881f-xxxxxxxxxxx
DEVICE=eno3
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
GATEWAY=91.115.6.254

诺4

DEVICE=eno4
BOOTPROTO=static
IPADDR=192.168.0.20
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet

系统

systemd 分析责任

      6.037s NetworkManager-wait-online.service
      4.528s cloud-init-local.service
      3.892s dracut-initqueue.service
      2.935s initrd-switch-root.service
      2.206s kdump.service
      1.459s sssd.service
      1.383s systemd-udev-settle.service
      1.090s polkit.service
       985ms tuned.service
       797ms cloud-init.service
       658ms cloud-final.service
       571ms cloud-config.service
       542ms gluster.mount
       479ms systemd-journald.service
       426ms boot.mount
       386ms data.mount
       379ms sysroot.mount
       367ms systemd-logind.service

答案1

原来是有缺陷的主板，他们更换了，现在可以正常工作了

相关内容