When to upgrade?
-
@steveits Yes, yes it is.
Well the question of "when" was answered by Mother Nature for me Tues at 930am EDT when power went out.
Took the opportunity to rearrange and label cables and put the 4100 into service. Of course I couldn't test until now when power came back.But the surgery was a success.
-
HA between those would be complex even given available IPs because they don't share any interfaces. There are no igb NICs in the 4100. So you would need to use a few dirty tricks!
Better to avoid that.Steve
-
@stephenw10 But...I thought that was no longer an issue?
https://docs.netgate.com/pfsense/en/latest/highavailability/pfsync.html#pfsync-and-physical-interfaces“This is no longer the case on pfSense Plus software version 22.01 and later and pfSense CE software version 2.6.0 and later. On these versions, the states are no longer bound to interfaces in the way described in this section.”
-
@steveits The 2440 is running 2.4.4 or something; it was running fine so never updated when it was available and before losing power it said "no updates available", so that likelyu would have needed "dirtier tricks".
I own my cable modem, so comcast is handing out a public IP for WAN not sure what would happen if I tried to hook up 2 on a switch behind it. Probably violate some hidden term somewhere.
But it was an interesting idea I'll have to investigate just for the knowledge.
-
@steveits said in When to upgrade?:
@stephenw10 But...I thought that was no longer an issue?
https://docs.netgate.com/pfsense/en/latest/highavailability/pfsync.html#pfsync-and-physical-interfacesHmm, that is a good point. It could be I've just been doing it that way too long.
It's true that states no longer reference the physical NIC names directly. However I would still not recommend trying to setup an HA pair between anything but identical hardware.@mer said in When to upgrade?:
The 2440 is running 2.4.4
Be aware that if you had an issue with the 4100 and had to switch back to the 2440 you could not import the 4100 config into it. So any changes you had made to the config since switching would be lost.
I would upgrade the 2440 to 23.01 once you are happy with he 4100 as the primary device.Steve
-
@stephenw10 I assume I'll need to contact support for a link to an image for the SG2440?
I've been tweaking the config for a while, the most that changes is DHCP static mappings when we get new phones, so I basically put the 4100 behind it, then walked through my checklist/network diagram and recreated the config on the 4100, compared the two, tweaked, compare. The only difference between the two are the IPs for LAN and LAN2/OPT1.Thanks for all the ideas.
-
@mer said in When to upgrade?:
contact support for a link to an image for the SG2440
yes. https://docs.netgate.com/pfsense/en/latest/solutions/sg-2440/reinstall-pfsense.html
alt answer: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors. Though 2.4 is pretty old and Netgate will usually recommend here to just install new. If you did get it to work I'd personally try upgrading to "previous stable version" first instead of jumping all the way forward, but that still skips multiple versions.
-
@steveits Thanks. I know my 2440 is old, but it's been a "ain't broke don't fix it but plan an upgrade" The 4100 is running nicely so at the moment the 2440 becomes a test system.
-
I would upgrade it to 23.01 now while there's no pressure.
-
@stephenw10 Staples has nothing on Netgate in the "That was easy" department. :)
10 mins to get the image, 5 to find a usb stick and burn it, maybe 20 total to install 23.01 to a different mSATA and restore the old config. Yep, half hour total.
Good job. Thanks.