After the network configuration fails, ipxe cannot ping through any ip address, even 127.0.0.1

[IAseven]

I have two physical servers of the same model and bios version on two networks. After I configure the network after ipxe is started, one server works properly while the other server cannot ping any ip address. Even if ping 127.0.0.1 is used, a timeout message is displayed.
The ip and network configuration is correct when I confirm, and the network configuration is normal when I start centos7 on the machine in the network environment in question, but the network configuration is wrong only in the ipxe environment.
Here is my script for configuring the network in ipxe:

#!ipxe
echo set
ifopen net0 \
&& vcreate --tag 1045 net0 \
&& set net0-1045/ip 10.230.45.118 \
&& set net0-1045/gateway 10.230.45.254 \
&& set net0-1045/netmask 255.255.255.0 \
&& sleep 1
echo ***********************************
echo vcreate --tag 1045 net0
echo set net0-1045/ip 10.230.45.118
echo set net0-1045/gateway 10.230.45.254
echo set net0-1045/netmask 255.255.255.0
echo ***********************************

echo show xxxx
show net0-1045/ip
show net0-1045/gateway
show net0-1045/netmask

ping --count 3 10.230.45.118 || shell

The following is a screenshot of the NIC of my physical machine：

ipxe ping Error message

I would like to know how to use debug=xxx in make to troubleshoot this problem.

Thank you very much for your opinion

[NiKiZe]

Since we don't have enough information yet to know if this is an issue with iPXE I moved it to discussions.

You have 2 servers, are these identical?
What does ifstat show on these 2 machines after configuration?
How do you start iPXE?

You seem to already have debugs enabled?

[NiKiZe]

Your tests in iPXE is pinging localhost, does that differ between working and non working? If not that isn't really a relevant test.

If you have network issues, consider tcpdump to check where packets are dropped or similar.

[IAseven]

When I ping 127.0.0.1 in ipxe, the same error is displayed. In principle, ping 127.0.0.1 should not go through the NIC

[mcb30]

Please note that iPXE does not set up any kind of localhost route, and 127.0.0.1 has no meaning to iPXE. It will simply treat it as a normal external IPv4 address and try to send packets out on to the network.

Pinging a local interface's IP address will similarly not do what you expect.

Since iPXE does not have support for listening sockets, we don't bother to include the extra logic that would be required to route packets back to our own local addresses, and any tests involving pinging a local or loopback address will not give any meaningful result.

[IAseven]

Thank you very much for your answer. May I ask, in my case, which debug parameters should be specified in make to better troubleshoot this problem?

[NiKiZe]

I'm not sure we know what your "problem" is?
What is your end goal? What do you want to do in iPXE? What happens if you try to do any kind of download? Do you get any errors? And have you checked what the server sees when you try to make a download?

Rather than iPXE, I would debug network port configuration and traffic, as well as server traffic.

[IAseven]

Thank you very much, the cause of the problem has been found. The parameters configured on the upstream switch cause a delay in arp learning. You must wait 1 minute to learn the mac of the network card. After I changed the configuration of the switch, it is normal