- You need to open the box
- The box is locked
- The key is inside the box
- Goto 1.
This is my experience with vsx_util change_interfaces in both R77.30 and R80.40.
Use case: Migrating VSX gateways from CP appliances to open servers, where source interfaces are "ethN-nn" and destination interfaces are "ethNN".
For various reasons (default Gaia partitioning & lazy admin) the vsx_util change_interfaces process failed part way through and needs to complete. On the initial run, the option to "delete old interfaces" was selected, to ensure they are removed from the DB as they don't exist on the target hardware. The process seems to continue OK and reconfigure all the virtual systems in all domains, until we invoke vsx_util reconfigure to reconfigure the new gateway.
The process fails, because eth1-01 is in the database and not on the gateway. Does vsx_util have amnesia? I'm sure I told it to remove them.
We attempt to remove the old interfaces from the object in the GUI, however the push process fails. Why? Because "Initial policy is installed on the VSX".
fw unloadlocal to the rescue? Nope... new error this time, "Error retrieving policy installed on the VSX". I recall using dbedit on R77.30 to fix this a long time ago, however dbedit continuously crashed forcing us to restore the MDS from a backup to recover from this state.
