Defects Closed with Code Changes

Execute EPG create, delete and re-create CLI in quick succession as below:

1. Create EPG/Networks with user-provided VNI parameter.

2. Delete EPG.

3. Create EPG again with the same parameters as in step-1.

1. Create EPG with 100 networks.

2. Update EPG with 20 ports/port-channels from one switch using "port-group-add" operation.

1. Create BD-LIF (without any associated VLAN) configuration manually on the switch followed by EFA inventory update.

2. Create EPG which results in the same BD-LIF on the switch.

The second EPG will get created successfully but the anycast-ipv6 provided in the second EPG will not get configured on the switch.

The second EPG create command should have failed with an error mentioning a unique anycast-ipv6 needs to be provided for a given BD name.

1. Create BD based L3 EPG with some BD label and an anycast-ipv6.

2. Create another BD based L3 EPG with the same BD label (as used in 1) but with a different anycast-ipv6.

EFA configures both "suppress-arp" (needed for ipv4) and "suppress-nd" (needed for ipv6) for the particular network (VLAN/BD).

EFA shouldn't have configured "suppress-nd" on the network.

When VRF is added and deleted to/from and Endpoint Group, in quick succession, multiple times, events received from inventory service can get interleaved with the commands.

This can cause EFA command execution path to find database entries that are yet to be deleted due to previous command run.

Execute EPG update "vrf-add", "vrf-delete" and "vrf-add" operation CLI in quick succession as below:

1. Update EPG for operation vrf-add.

2. Update EPG for operation vrf-delete.

3. Update the same EPG again with operation vrf-add for the same vrf which was deleted in step 2.

This issue observed with below steps,

1)Created CLOS Fabric with multiple MCT-Pairs and a Spine device

2)When checking drift for all devices part of fabric, Cluster Config can be seen as refreshed, but no impact can be seen on fabric show. Also drift status for fabric states false in drift o/p.

Tenant commands can take more time (> the timeout =1000 seconds) to complete and hence the failure.

The status of timed out fail command can be seen using the relevant "show" command.

The issue can happen in the below scenario:

1. EFA has a scaled tenant configuration.

2. Significant configuration drift introduced between SLX and EFA.

3. Inventory device update is performed resulting in configuration drift derivation of the tenant entities.

4. Tenant commands are executed when (3) is in progress.

Drift is shown for "pseudowire-profile" configuration in command,

"efa inventory drift-reconcile execute --ip <device ip>"

This is observed with below steps

- Create fabric with back routing enable and configure the fabric.

- Create epg and delete the same epg.

- Make one of cluster pair device as admin down.

- Create same epg which was created and deleted above.

- Make the admin down device as admin up.

- "pseudowire-profile" still remain as drifted.

Any delete nature CLI of "service BGP peer" has failed because any of the below-listed reasons will lead the BGP service to this state.

1. Device connectivity issues

2. Failed to deconfigure the peer on device

3. Targeted topology falls into the APS category.

- Remove the VLAN configuration from the device

- Reload the device with "maintenance mode on reboot enabled"

- Description configuration is missing for reconciled VLANs

Executing the command “EFA-sync execute” when one of the SLX switches in cluster is unreachable, could take several minutes to complete.

This happens only when multiple neutron entities have to be synced with EFA.

The command takes longer time to complete only when:

a)Out of sync configuration is large. That is, many neutron entities are out of sync on EFA.

b)One of the SLX nodes is not reachable.

This is observed with the below steps

1. Put SLXs in maintenance mode

2. Remove the router bgp configuration, few VRFs from the device.

3. Reboots both the MCT nodes where TPVMs containing EFA are hosted.

4. Verify after 30 mins, the switches are out of maintenance mode.

5. After a few iterations most of the BGP configs are missing.

This issue observed with below steps,

- Configured fabric/tenant/po/vrf/epg/bgp peer/peer-group

- Enabled maintenance mode enable-on-reboot on SLX switch.

- Reload SLX switch.

- Drift and Reconcile process shows drift for interface used in EPG which was not drifted.

Device setting parameters like health check enable, heartbeat miss threshold etc. shows as default values.

Drift-reconcile get triggered after default heartbeat miss threshold.

1) Create Fabric with backup routing enabled and MM enable-on-reboot on all the fabric switches.

2) Create tenants.

3) Create around 60 POs .

4) Create around 8 VRFs with static route bfd.

5) Create around 700 L3 EPGs using the POs and VRFs created in (3) and (4) respectively.

6) Create around 35 BGP peer group and BGP peers.

7) Reboot the fabric switch(es) which will trigger DRC on the rebooted switch(es).

The 'efa login' command does not work and responds with the message

"

CLI Failed.

EFA services are not operational yet. Please check service state using 'efactl status' command and retry the login once the services are up

"

When executing 'efactl status' command it shows pods in the active node being in "Unkown" state.

1) Tenant service is stopped/not running

2) Portchannel delete command run

1) Create Fabric having leaf pair and border-leaf pair.

2) Create Tenant with ports from leaf devices.

3) Create VRF using routing type as centralized and border-leaf(s) as centralized routers.

4) Create L3 EPGs using VRF created in step3 and ports from leaf devices.

5) Remove Border-Leaf devices from fabric or inventory.

6) Remove Leaf devices from fabric or inventory.

7) Delete EPG(s) created in step4.

1) Create VRF with routing type 'centralized'

2) Create EPG using VRF created in above step and ports from leaf devices & border-leaf(s)

3) Create another EPG using same VRF and different ports from leaf devices & border-leaf(s)

4) Remove border-leaf devices from fabric. After some time, it is observed both EPGs goes to "vrf-delete-pending" state

5) Perform EPG update "vrf-delete" on one of the EPG

6) Perform EPG update "vrf-delete" on another EPG

1) Create multiple stacks from OpenStack

2) Create multiple networks and routers, both centralized and distributed.

3) Ensured all epg/vrfs are created in EFA and on switch

4) Ran drift for all leaf and border leaf switches. They are showing drift for the some vlans created.

1) Create Tenant with ports.

2) Create EPG(s) on tenant created in step1.

3) Remove device(s) from fabric or inventory which are used in Tenant created in step1.

4) Delete EPG(s) created in step3.

This issue observed with below steps,

- Configured fabric/tenant/po/vrf/epg/bgp peer/peer-group

- Enabled maintenance mode enable-on-reboot on SLX switch.

- Reload SLX switch.

- Drift and Reconcile process shows drift for interface used in EPG which was not drifted.