As part of migration, all the fabric configuration pushed to the devices through embedded
fabric (legacy EFA) are retrieved through the database dump file which is copied
from TPVM. Alternatively, you can connect to the TPVM server directly and run the
import CLI command to migrate.
The legacy EFA supports only 3 stage CLOS fabrics, so only 3 stage CLOS can be imported to
EFA.
In the fabric service back end the migration process involves the following steps:
-
Depending on the location of legacy EFA database file, the file is SCPed from
TPVM server to the host where EFA is running first and then uploaded to fabric
container at /tmp location.
-
Fetch all the devices that are
part of legacy EFA DB and register these switches with inventory service of EFA.
If any of the device registration fails, then other devices which were
successfully registered are also removed from inventory.
-
Fetch the fabric settings from
legacy EFA DB and create a new fabric (with user provided name) in EFA. If
fabric already exists with devices added to it, then an appropriate error is
returned. Ensure that the new fabric doesn‘t have any devices added to it.
-
Devices are added to the fabric
and fabric pre-validation is done. If fabric device addition or pre-validation
fails, an error is displayed, also fabric created previously is deleted and
devices are removed from the fabric and deregistered from inventory.
Configurations on the device are not cleaned and all the configurations that
existed prior to import are retained.
-
Post-validation phase is run
where fabric configuration is compared with configuration fetched from
inventory. If the data does not match, an error is displayed.
-
On successful migration, devices
are added in the fabric with provisioning state as “CFG-READY”.
-
Issue “configure fabric” to move
all the devices to “CFG-IN-SYNC” state.
