TrueNas Scale cannot reach IPMI address
Description
Problem/Justification
Impact
Activity

Caleb April 25, 2022 at 4:29 PM
thanks for the update.

Lee Davis April 16, 2022 at 6:09 PM
I should also add that there is still NO issue hitting the BMC directly without the IP and all other remote management NOT on this machine works fine hitting that IP. Looking at my other startup scripts (which I haven't touched in years) all do this without an ip.
I think I was wrong about this NOT being an issue before. I think it was just different setups. I checked a couple other servers that have what I believe is a shared network controller sideband interface and seeing the same results and also explains the arp entries. Likely also explains why all hell broke loose when I blew away my arp table debugging this.
I think I can consider this resolved unless I'm way off base on my theory, as it doesn't appear unique to this setup or Scale.

Lee Davis April 14, 2022 at 3:41 PM
Thanks !

Bonnie Follweiler April 14, 2022 at 1:01 PM
Thank you .
I have moved this ticket into our queue to review now.
An engineering representative will update with any further questions or details in the near future.

Michelle Johnson April 13, 2022 at 7:57 PM
Thank you for your report, !
Would you attach a debug file to the Private Attachments area of this issue ticket.
To generate a debug file on TrueNAS SCALE, log in to the TrueNAS web interface, go to System Settings > Advanced, then click Save Debug and wait for the file to download to your local system.
Details
Details
Assignee

Reporter

Since moving to SCALE I've run into the following issue:
TrueNAS-SCALE-22.02.0.1
Supermicro; X12SPi-TF
Network: bonded/Lagg
Console: dedicated network port
Hi, when testing some startup scripts to make some modifications via IPMITOOL, I noticed I couldn't resolve the IP. I tested this on my local terminal and got the following (Which worked):
```
ping 172.17.17.20
PING 172.17.17.20 (172.17.17.20) 56(84) bytes of data.
64 bytes from 172.17.17.20: icmp_seq=1 ttl=62 time=0.783 ms
64 bytes from 172.17.17.20: icmp_seq=2 ttl=62 time=0.783 ms
```
However, I try this from a terminal on my TrueNAS Scale box, I get the following:
```
ping 172.17.17.20
PING 172.17.17.20(172.17.17.20) 56(84) bytes of data.
From 172.17.0.1 icmp_seq=1 Destination Host Unreachable
From 172.17.0.1 icmp_seq=2 Destination Host Unreachable
```
ARP results:
```
Pre:
arp -e
Address HWtype HWaddress Flags Mask Iface
172.17.0.8 ether aa:aa:aa:aa:aa:aa C kube-bridge
172.18.18.1 ether cc:cc:cc:cc:cc:cc C bond0
172.17.0.10 ether bb:bb:bb:bb:bb:bb C kube-bridge
Ping:
ping 172.17.17.20
PING 172.17.17.20 (172.17.17.20) 56(84) bytes of data.
From 172.17.0.1 icmp_seq=1 Destination Host Unreachable
After:
arp -e
Address HWtype HWaddress Flags Mask Iface
172.17.0.8 ether aa:aa:aa:aa:aa:aa C kube-bridge
172.18.18.1 ether cc:cc:cc:cc:cc:cc C bond0
172.17.0.10 ether bb:bb:bb:bb:bb:bb C kube-bridge
172.17.17.20 (incomplete) kube-bridge
```