For a two-leaf MCT pair, you can enable configurations to succeed when only one node of the pair is reachable.
By default, when a REST operation succeeds on one device but fails on another, configuration changes are rolled back for both devices. For more information, see Rollback Scenarios for Data Consistency.
The reason being EFA doesn't want to leave stale configurations on the devices. If stale configurations are left on the devices, then bringing the devices (with stale configurations) back into EFA will be erroneous considering the full brownfield support is missing in EFA.
Command type and name |
---|
Inventory commands |
efa inventory device compare --ip |
efa inventory drift-reconcile --ip |
efa inventory device setting update --ip |
efa inventory rma --ip |
efa inventory config-backup execute --ip |
efa inventory config-replay execute --ip |
efa inventory device update --fabric |
efa inventory device firmware-download prepare add --ip |
efa inventory device update --ip |
efa inventory device interface set-speed --ip |
efa inventory device interface set-breakout --ip |
efa inventory device interface unset-breakout --ip |
efa inventory device interface set-mtu --ip |
efa inventory device system set-mtu --ip |
efa inventory device interface set-admin-state --ip |
efa inventory device running-config persist --ip |
Fabric commands |
efa fabric configure --name |
efa fabric device remove --ip <> --name <> Allowed with the --no-device-cleanup option. |
efa fabric show-config --name |
efa fabric topology show underlay --name |
efa fabric topology show overlay --name |
efa fabric topology show physical --name |