Subscribe

Performing a vfiler migrate from fas6040 to new 3240 - ip space issue

Good afternoon all

I have been working on this for a while, and have found out the
following - the protection manager gui doesn’t work well with multiple vlans

That being said, I have been able to get my test vfiler
migration to work ,with the following issue:

On my source vfiler (old), the ipaddress of the vfiler is in the
default ipspace. x.x.253.165

On my destination (new), the ipaddress is is the same vlan as
above, but it now resides on a vlan/ipsapce versus the default ipspace(vlan253 - the
name in use) on a vif of e0a and e0b

My question - is there a way to migrate this without manually
editing rc/interfaces afterword’s. I tried using the vif-vlan name as the specified
interface but received "interface does not exist" error. To perform
the test I had to use the vif name with vlan, this succeeded, but put the moved
vfiler in the default ipsapce on the new physical filer, when it is supposed to
end up on VLAN 253.

Any ideas? I have a prod box to move, and would prefer minimal
intervention

Thanks

Larry

Re: Performing a vfiler migrate from fas6040 to new 3240 - ip space issue

As long a the interface is in the same Ipspace vlan or not it should work. I haven't had issues between interface types as long as the target interface is in the same Ipspace name a the source.