Hello, I think this is an issue that might have been caused by a previous tunable change to "fix" the issue before, but I can't remember where I read it or where it was. When I rebooted after applying 11.3-U4.1 my Freenas server seems to have bridged all of the NICs, even the ones assigned to my PFSense server. So, it basically is creating a broadcast storm. I only want FreeNAS to "talk" on ix0. The VM is using ix2 as WAN and ix3 as LAN. Ideas as to the cause?
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
Issue with NICs & VMs on patch to FreeNAS-11.3-U4.1
- Thread starter cadamwil
- Start date
OK, my suspicion of this being a tunable may be incorrect. There are only two tunables not "generated by autotune". They are
However, I did just notice that the hw.vmm.topology.cores_per_package is set to 6. I have recently upgraded to dual 10 core procs. However, the issue only occurred after the upgrade to 11.3-U4.1. Ideas?
linux_enable / YES / loader & hw.vmm.topology.threads_per_core / 2/ loaderHowever, I did just notice that the hw.vmm.topology.cores_per_package is set to 6. I have recently upgraded to dual 10 core procs. However, the issue only occurred after the upgrade to 11.3-U4.1. Ideas?
well, I "think" that this was resolved by changing the
hw.vmm.topology.cores_per_package to 10, the correct number of cores for my machine now, and it's segregating the NICs correctly.I thought wrong. I had an unscheduled reboot, don't plug a cisco serial cable into an APC UPS to update the firmware (it turns off), and after the reboot, back to broken. Any ideas?
Similar threads
