Open Defects

Follow the steps to reproduce the issue:

1. Configure multi rack Non-CLOS fabric.

2. Manually remove the below set of configurations on device under

router-bgp

no neighbor 172.x.x.x password xxxx

no neighbor 172.x.x.x update-source loopback 1

no neighbor 172.x.x.x peer-group overlay-ebgp-group

address-family l2vpn evpn

no retain route-target all

3. Execute "efa inventory drift-reconcile execute --ip <device-ip>"

Below are the steps to reproduce the issue

1. Configure a 5-stage CLOS fabric

2. Enable the LLDP link(s) between the superspine devices

3. App state of superspine devices moves to cfg-refresh-error

4. Disable the LLDP link(s) (which were enabled in step 2) between the superspine devices

5. App state of superspine devices moves to cfg-refreshed

6. Execute "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" for the super-spine devices

login to SLX CLI and remove the breakout of port using these steps:

Run following commands

configuration terminal

hardware

connector <slot/interface>

breakout mode <4x10g/4x25g>

no breakout

e.g. if the port 0/50 got this issue, following are the commands to run after login to CLI

Freedom7-Bng# configure t

Entering configuration mode terminal

Freedom7-Bng(config)# hardware

Freedom7-Bng(config-hardware)# connector 0/50

Freedom7-Bng(config-connector-0/50)# breakout mode 4x10g

Freedom7-Bng(config-connector-0/50)# no breakout

1. Create a 3-stage CLOS fabric, add devices with MCT leaf, spine, and border-leaf and configure the fabric

2. Convert the 3-stage CLOS fabric to a 5-stage CLOS fabric using the fabric migrate command

"efa fabric migrate --type "3-to-5-stage" --source-fabric <source-fabric> --destination-3-stage-leaf-spine-pod <pod-name> --destination-3-stage-border-leaf-pod <pod-name>"

3. Add super-spine POD devices to the migrated 5-stage CLOS fabric

4. Disconnect the BorderLeaf to Spine links and reconnect the BorderLeaf to Super-Spine links

5. Configure the migrated 5-stage CLOS fabric

1.Fabric devices are already in cfg-refresh-err state due to LLDP Link down(LD) event.

2. Bring up the LLDP links responsible for the fabric devices to be in cfg-refresh-err state.

3. Execute the TPVM failover by 'tpvm stop' and 'tpvm start' commands during the LLDP Link up (LA) event handling caused by 2.

1.0 The user triggers LD/LA event by flapping the interface links which are the devices are in the cfg-refreshed state even though DRC wouldn't help out to recover the device to the cfg-sync state and the pending reason is "LA/LD".

1.1. "shutdown" the interface link on the physical link on Devices follow by "efa inventory device udpate --ip <device-ip>", which generates LD events

1.2. "no shutdown" the interface link on the physical link on Devices follow by "efa inventory device udpate --ip <device-ip>", which generates LA events

1.3. If the pending config contains "LA" : Execute "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" on the devices which are in cfg-refresh-err /cfg-refreshed state [or] IF the pending config contains "LD,LA" : Execute "efa fabric configure --name <fabric-name>" to clean up the configuration on devices which are in cfg-refresh-err /cfg-refreshed state.

[OR]

2. The user reboots the devices without maintenance mode which are the devices are in cfg-refreshed state even though DRC wouldn't help out to recover the device to the cfg-sync state.

2.1. "reload" the switches without out maintenance mode to enable

2.2. Run "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" on the devices which are in cfg-refresh-err /cfg-refreshed state.

logging raslog message SEC-1206 suppress //to supress

logging raslog console CRITICAL //to discard other types and show only critical

For the firmware download workflow, it will perform the FWDL on each device as prescribed by the grouping and then finally do a "quick" device update (device links only) for all devices that have participated in the FWDL.

The purpose of the device links only update is to ensure that the fabric configurations are in-sync after the FWDL workflow has completed since devices are rebooted to activate the new firmware.

In this customer case, they only did a FWDL of a single device, but the workflow is the same, a device links only update will be performed at the end.

The firmware download show command contains the individual device's status in the table and the "Overall Status" at the bottom reflects EFA's overall status of the FWDL workflow which includes the Device links only update.