Proper way to restore configuration on new vm
-
Hi there,
I'm facing lately issues with my 2.5.2-RELEASE (amd64) running on VM.
Issues I'm facing is that when I'm trying to add new interfaces, trying to create DMZ network, this pfsense vm gets corrupted somehow, and I loose connection to it, because it somehow disconnects everything.
I'm connected over VPN to this remote pfsense, and whenever this happens, I cut off myself completely.Anyway, I would like to create backup file, and do restore on other VM, which I will then upgrade to 2.6.0.
First thing to ask, in such scenario, would you consider migrating to other VM, set up from scratch, or would you anyway just issue update on it, and forget it about hustle?When I try to migrate configuration, I get Interface mismatch issue, and how I understand, I will have to rename all interfaces. I tried that option on my test environment, but seems that I don't quite understand what is being done there with renaming VLAN's . I didn't get possibility to rename them all.
Does anyone have experience with this?
Thanks in advance.
-
@dzonic90 said in Proper way to restore configuration on new vm:
I'm trying to add new interfaces
Yeah vms like to reorder the interfaces when you add a new one. Check the mac address of your current interfaces, and then make sure they are assigned correctly after you add a new one.
-
@johnpoz So, we should call this "expected" behavior then?
It's not that pfSense is misbehaving? -
@dzonic90 if you search here on the forums you will find lots of threads about it - yeah its a vm thing..
-
@johnpoz Thanks man!
-
@dzonic90 said in Proper way to restore configuration on new vm:
@johnpoz So, we should call this "expected" behavior then?
It's not that pfSense is misbehaving?It is both in my opinion. You have to understand that the names (e.g. opt10, hn2) for every interface have to stay the same. The only way to accomplish that is to edit the config in an editor.
To do that, you have to know the new hardware-names of the interfaces (e.g. opt10, vmx2). Good luck.
-
@Bob-Dig Which means in practice, I need to firstly edit interface names on new VM to reflect interface names of old instance, and then only after doing that, I can restore desired backup from the old VM, right?
-
@dzonic90 its not difficult - check the mac addresses of the interfaces before you add a new one and what they are assigned too. then via console just hit 1 to assign interfaces and make sure they are all assigned correctly..
If it take you more than like 1 minutes I would be surprised.
Its best if you know your going to need more than 4 to add them from the git go, or you could just use vlans on the virtual interface you assign so that your not actually adding more virtual nics to the pfsense vm.
-
@johnpoz Thing is, when I do new interface, or do any change which causes to change interface assignments, I get my connection lost, so no console, no anything. It's a remote system on which I'm connected over VPN :)
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
@dzonic90 said in Proper way to restore configuration on new vm:
so no console, no anything. It's a remote system on which I'm connected over VPN :)
That is bad. Is the vm from the same hypervisor or is it different. How do you do this anyway, if you loose the connection?
-
@dzonic90 said in Proper way to restore configuration on new vm:
@johnpoz Thing is, when I do new interface, or do any change which causes to change interface assignments, I get my connection lost, so no console, no anything. It's a remote system on which I'm connected over VPN :)
advice: don't add interfaces to a pfsense-VM remotely
if you have to do it:
1)get someone on-site ready with a cellular hotspot that has direct connection to the hypervisor management interface
2)add the VM interfaces over this cellular link
3)open the VM console of your pfsense and reassign the interfaces -
@Bob-Dig It is the VM from the same hypervisor - also on the same hypervisor, VMWare ESXi.
I usually hoped for the best when doing such changes
Same with upgrades. -
@heper Yeap, this seems like the only way to do it.
Thanks! -
@dzonic90 said in Proper way to restore configuration on new vm:
It is the VM from the same hypervisor - also on the same hypervisor, VMWare ESXi.
Then you only have to create the exact same interfaces beforehand, should be doable.
-
How many interfaces do you have already? How many are you adding?
ESXi will reorder the NICs when you add more than 4.
-
@Bob-Dig I'm currently doing it in test env. Will see, I hope for the best.
-
@stephenw10 It has more, 8 or 9, something like that.
-
Hmm, I forget if it reorders again at higher numbers. But not the usual limit people hit though.
-
@stephenw10 Uhhh, wait, you mentioned NICs, I thought on interfaces. sorry. It has VLANs and other interfaces, altogether it makes 8-9, but NICs, it has 2 I think.
My bad. -
Ah, well still not hitting that then.
