Netgate 5100 Upgrade requires mapping/remapping of interfaces
-
So in ref to the title, this has happened to me over the last few upgrade cycles. The last one being done today from 22.01 to 22.05. The upgrade seems to complete just fine each time, however when it performs the reboot part of the process, it reaches a point where it waits for user input on mapping the interfaces again. So I have to tell it the WAN is IGB0, LAN is IGB1, OPT1 is ix0, OPT2 is ix1, OPT3 is ix2, and OPT4 is ix3. Once that's done, it boots up successfully without any further user action taken. It's a bit of a pain because I have to drive to the site and console into the unit. Or I'd have to rig up a laptop/desktop to connect always to the console port, then remote in to the console connected device to perform the steps, which again, a pain. I was wondering if others have experienced the same issue. I did a quick look through the forums but didn't see any similar issues/postings. It's not a huge issue because it only occurs during an upgrade, not necessarily during a simple reboot of the unit outside of an upgrade process. But it would be nice not to have a pain in my....server room :)
-
The boot process stops at that point (in any boot) is the config contains assigned interfaces that don't exist on the firewall. So commonly that might be an assigned USB device (ue0) that has been removed or has gone into standby power mode. But it could be other interfaces.
That should not happen on a normal upgrade, especially of you only have the standard NICs as you have listed.
Steve
-
@stephenw10
When I migrated the config a while back from an old Netgate device to, at that time, a new Netgate 5100, I never cleaned up the old VLANs that were assigned to an interface. I had to originally do this because the old unit didn't have enough physical interfaces, so I 802.1q trunked its LAN interface allowing it to handle a couple networks.
When I looked today I saw that the old VLANs were under Interfaces/VLANs but not assigned to any interface under Interfaces/Interface Assignments. So I simply deleted them as they're no longer needed nor used. -
@johnpitton For what it's worth, Netgate has helped in the past when migrating from one Netgate appliance to another with config adjustments. In the future (or even now if you feel there might be issues) it may be worth engaging Netgate support to look at the config and let them know you're trying to migrate between X and Y Netgate and could just a review of the config to adjust for booting.
-
@rune-san quite aware of that and thanks, but it's really not that hard migrating configs. I just simply forgot to remove some cruft which was the root cause of my described issue.
Thanks again @stephenw10 for helping look in the right direction. -
Hmm, well unassigned interfaces should not be a problem there. Additionally VLANs are specifically excluded from the check as a subinterface type:
https://github.com/pfsense/pfsense/blob/master/src/etc/inc/util.inc#L2415So I would have guess it was something else. Not sure what that could have been though.
Steve