UEFI pxe boot problem from a network
-
@Sebastian-Roth said in UEFI pxe boot problem from a network:
ip a s
root@fogus ~]# ip a s 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: ens2f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether b0:26:28:78:ce:d0 brd ff:ff:ff:ff:ff:ff inet 148.60.4.1/21 brd 148.60.7.255 scope global noprefixroute ens2f0np0 valid_lft forever preferred_lft forever inet6 fe80::b226:28ff:fe78:ced0/64 scope link valid_lft forever preferred_lft forever 3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 4c:d9:8f:8e:41:0f brd ff:ff:ff:ff:ff:ff 4: ens2f1np1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether b0:26:28:78:ce:d1 brd ff:ff:ff:ff:ff:ff 5: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 4c:d9:8f:8e:41:10 brd ff:ff:ff:ff:ff:ff 6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:1e:69:b9 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 7: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:1e:69:b9 brd ff:ff:ff:ff:ff:ff
ip r s default via 148.60.7.254 dev ens2f0np0 proto static metric 102 148.60.0.0/21 dev ens2f0np0 proto kernel scope link src 148.60.4.1 metric 102 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
-
@lebrun78 Please post output of the two commands:
ip a s
andip r s
-
@Sebastian-Roth Fog server is on the vlan where boot uefi pxe works
-
@Sebastian-Roth Yes, if I change vlan, it works…
-
@lebrun78 Well than it doesn’t receive PXE boot information at all. Can you take one of those machines and put it into the other VLAN. Does it PXE boot??? Just want to make sure this is not a model specific issue.
-
No bootable device found
-
This is strange. This is the second issue we have relating to pxe booting not working for uefi but working for bios.
What error are you seeing on the target computer when pxe booting in uefi mode?