Open Defects

In a CLOS fabric, multiple fabric ports belonging to different fabric devices can have the same IP address assigned incorrectly.

For example: interface ethernet 0/x on device D1 and ethernet 0/y on device D2 can have an ip-address 10.1.1.1/31 assigned.

1. Disable the LLDP protocol under the interfaces ethernet 0/x on D1 and ethernet 0/y on D2

2. Execute "efa inventory device update --ip <device-ip>" for both D1 and D2

3. Execute "efa fabric configure --name <fabric-name>"

Set the higher value for the user token expiry using "efa auth settings token update" CLI. The default access token expiry value is 1 hour.

Example: efa auth settings token update --type=ACCESS --hours=2 --minutes=30

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. Configure a single rack(MCT Pair) Non-CLOS fabric with the SLX devices

2. All links between the MCT pair are brought down

3. "efa fabric show" output indicates the devices with the app-sate set as "cfg-refresh-err"

4. Reload the SLX devices

5. There are connectivity issues towards the SLX from EFA after reload

1. Fix the network connectivity issue between EFA and the SLX devices

2. Execute "lldp disable" followed by "lldp enable" under the physical interfaces interconnecting the MCT pair

3. Execute "efa inventory device update --ip <device-ip>" on the MCT pair

On BR-SLX9540, BR-SLX9640, SLX9740-40C, SLX9740-80C

1. Configure a fabric and create a BD based tenant, vrf and Port channel under the tenant

2. Configure L3 EPG under the BD based tenant using the vrf and Port channel created in step 1.

3. Step 2 will result in 'Tenant-profile' pw-profile configuration under the Bridge domain corresponding to the Tenant ctag.

4. Delete the port channel which has the associated LIF to the BD (discussed in step 3) on the switch.

OR

Delete the LIF present in the Port channel or Ethernet Port that is associated with the BD (discussed in step 3) on the switch.

5. Execute the DRC for the switch using CLI 'efa inventory drift-reconcile execute --ip <ip-address> --reconcile'

6. Step 5 will result in 'default' pw-profile configuration instead of 'Tenant-profile' under the Bridge domain corresponding to the Tenant ctag and EPG ctags will remain in 'cfg-refreshed' state.

Note: The issue is reproducible on BR-SLX9540, BR-SLX9640, SLX9740-40C, SLX9740-80C platforms only.

Port-group add operation on a Layer-3 EPG of a bridge-domain enabled tenant that shares ctag with other EPGs may fail. on certain conditions with the error:

Device: <device-1-IP> Ctag: <ctag> Anycast <IP-1> subnet is conflicting with already configured Ve 4097 : Anycast <IP-1> on the device <device-1>

1. Configure two layer-3 EPGs with shared ctags and with ports from different SLX devices that are connected as MCT pair

2. Do an EPG port-group-delete update operation on one EPG to remove all its ports

3. Re-add the same ports back to the EPG

The step 3 will fail with the symptom mentioned above.

Add the devices to fabric in the following sequence

1)First add devices that have preconfigured configs

2)Add remaining devices that don't have any configs stored

Removing the devices and adding the devices again to fabric in following sequence

1)First add devices that have preconfigured configs

2)Add remaining unconfigured devices.

Add EFA CA to the trust store in the browser.

Incase of an IP change, regenerate the EFA server certificate using CLI. Refer to Administration guide for details.

Below are 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

1. Check if we have enough disk space as mentioned in system requirements,

2. On the install dir , change to docker_images and import the images using following command

k3s ctr image import docker_k3s_images.tar

3. execute efactl start

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