Unable to access the BMC after enabling then disabling DHCP from WebUI.
Environment:
IGX Orin 700 Board Kit, with BMC firmware from SW-1.0.
Steps to reproduce the problem:
Open BMC WebUI (from 192.168.1.110). Enable “DHCP” under “Settings / Network”.
Refer to (Optional) Configure Ubuntu as a DHCP Host and set up a DHCP server. Hook up the BMC with the DHCP server and reboot the BMC. The BMC should get a new IP address assigned by the DHCP server this time around, say, 10.1.1.100.
Open BMC WebUI using the new IP (10.1.1.100). Disable “DHCP” under “Settings / Network”. Supposedly, the BMC should revert back to using fixed IP (192.168.1.110?).
Reboot the BMC. It is observed that the BMC does not respond to 192.168.1.110.
The BMC becomes inaccessible from Ethernet. We are not able to reproduce this issue multiple times, since it would cause BMC to fail.
Question:
Is there a way to force the BMC to restore its factory default settings (fixed IP at 192.168.1.110)?
Could you share the IPv4 configurations in WebUI(Settings / Network/IPv4)?
I’m not able to connect to the BMC any more.
At the last time I logged in the BMC WebUI (before disabling DHCP), I only see the entry of the DHCP-assigned IP address in the table. I thought the IP address would be restored to default (192.168.1.110) after disabling DHCP. But it didn’t.
The IGX Orin 700 Board Kit was shipped to a customer for testing and product development. When the customer returned the Board Kit back to us, I was informed that DHCP was enabled for BMC.
I’m not sure whether the customer has removed the static IP entry 192.168.1.110 manually (or maybe it’s removed automatically when DHCP is enabled)…
Do you know the exact IP address assigned by your host?
I set 192.168.1.2 as the fixed IP address for the host PC. I also set up DHCP server on the host PC so 192.168.1.10 (note: not 110) gets assigned to the BMC. That worked. But after I disabled DHCP on the BMC, I’m no longer able to connect to the BMC.
Have you tried to access BMC console through serial interface manually?
I haven’t. Do I need certain jig to do that? Could you point me to the corresponding documentation? Thanks.
Yes, you have to use 192.168.1.10 to access BMC first(so that you can access WebUI), and add static 192.168.1.110 entry back.
Or performing factory reset in WebUI: Operations → Factory reset → Reset BMC settings → Reset
Even if I plug the BMC to another IGX Orin baseboard, it still cannot get an IP address, right? Do you mean I can somehow log into BMC from the IGX Orin system?
Maybe I gave wrong info in my previous response.
Can your board boot successful currently? (i.e. if you can access the Tegra console?)
If so, please share the result of $ ip -br addr show from Tegra console.
The IGX Orin system could still boot (even when BMC cannot be accessed). Here is the result of $ ip -br addr show.
igx@IGX-IEC-20250507:~$ ip -br addr show
lo UNKNOWN 127.0.0.1/8 ::1/128
enP5p3s0f0np0 DOWN
enP5p3s0f1np1 DOWN
enP1p3s0 UP
enP1p53s0 UP
can0 DOWN
can1 DOWN
usb0 UNKNOWN
wlx0c9d92bafdb2 UP 10.130.16.43/24 fe80::a93e:bcfd:801d:31f2/64
l4tbr0 DOWN
usb1 DOWN
usb2 DOWN
docker0 DOWN 172.17.0.1/16
igx@IGX-IEC-20250507:~$
By the way, I have also tried to mount the BMC module onto another working IGX Orin board. It did not resolve the problem. I don’t think that triggered a factory reset of the BMC module. The BMC module still doesn’t respond to 192.168.1.110 (no response for ping).
Could you reboot the IGX Orin and run this command again to check if there’s an interface called enx82a33d87651f?
If so, please run the following commands on Tegra console to access BMC.
$ sudo ip addr add 10.0.1.1/24 dev enx82a33d87651f
$ sudo ip link set enx82a33d87651f up
$ ssh root@10.0.1.110
If not, maybe you have to send BMC module back to us for further check.
I cannot find the interface with the name enx82a33d87651f.
igx@IGX-IEC-20250507:~$ ip -br addr show
lo UNKNOWN 127.0.0.1/8 ::1/128
enP1p3s0 UP
enP1p53s0 UP
enxde04127ea424 UP
enP5p3s0f0np0 DOWN
enP5p3s0f1np1 DOWN
can0 DOWN
can1 DOWN
wlx0c9d92bafdb2 UP 10.130.16.78/24 fe80::a93e:bcfd:801d:31f2/64
l4tbr0 DOWN
usb0 DOWN
usb1 DOWN
docker0 DOWN 172.17.0.1/16
igx@IGX-IEC-20250507:~$ sudo ip addr add 10.0.1.1/24 dev enx82a33d87651f
[sudo] password for igx:
Cannot find device "enx82a33d87651f"
igx@IGX-IEC-20250507:~$
igx@IGX-IEC-20250507:~$ ip -br addr show
lo UNKNOWN 127.0.0.1/8 ::1/128
enP1p3s0 UP
enP1p53s0 UP
enx0a1f7105b9c1 UP
enP5p3s0f0np0 DOWN
enP5p3s0f1np1 DOWN
can0 DOWN
can1 DOWN
wlx0c9d92bafdb2 UP 10.130.16.78/24 fe80::a93e:bcfd:801d:31f2/64
l4tbr0 DOWN
usb0 DOWN
usb1 DOWN
docker0 DOWN 172.17.0.1/16
igx@IGX-IEC-20250507:~$
So, I tried it with enx0a1f7105b9c1 instead. And it worked.
igx@IGX-IEC-20250507:~$ sudo ip link set enx0a1f7105b9c1 down
igx@IGX-IEC-20250507:~$ sudo ip addr add 10.0.1.1/24 dev enx0a1f7105b9c1
igx@IGX-IEC-20250507:~$ sudo ip link set enx0a1f7105b9c1 up
igx@IGX-IEC-20250507:~$ ssh root@10.0.1.110
root@10.0.1.110's password:
root@bmc-tc119:~#