Use the
efa fabric migrate
command.
efa fabric migrate
--type {3-to-5-stage}
--source-fabric <source-3-stage-clos-fabric>
--destination-3-stage-leaf-spine-pod <3-stage-pod-name>
--destination-3-stage-border-leaf-pod <border-leaf-pod-name>
--super-spine-asn-block <super-spine-asn-range>
--super-spine-peer-group <peer-group-name>
efa:root)root@admin01:~# efa fabric migrate –help
Migrate a 3-stage CLOS fabric to 5-stage CLOS fabric
Usage:
efa fabric migrate [flags]
Flags:
--type string Type of migration [3-to-5-stage] (default "3-to-5-stage")
--source-fabric string Name of the 3-stage CLOS fabric to be migrated
--destination-3-stage-leaf-spine-pod string Name of the 3-stage POD into which the leaf and spine devices (of the 3-stage CLOS fabric)
need to be moved during migrate
--destination-3-stage-border-leaf-pod string Name of the 3-stage POD into which the border-leaf devices (of the 3-stage CLOS fabric)
need to be moved during migrate
--super-spine-asn-block string ASN block to be used by the super-spine devices of the migrated 5-stage CLOS fabric
--super-spine-peer-group string Peer Group to be used by the spine devices of the migrated 5-stage CLOS fabric
- No or least traffic
loss.
- The command supports
migration of a single fabric from 3-stage to 5-stage and not merging of
multiple 3-stage Clos fabrics into a single 5-stage fabric.
- If border-leaf is present /
not-present in the fabric, then you must / must not provide the
destination-border-leaf-pod.
- If the border-leaf is connected to the spine devices in an existing 3-stage
Clos fabric and you want the border-leaf to be connected to the spine even
in the migrated 5-stage Clos fabric, the migration allows this.. Provide the
same pod name for both the destination-3-stage-leaf-spine-pod and
destination-3-stage-border-leaf-pod.
- Migration is supported with multiple single-homed, multiple multi-homed
border-leaf devices.
