Open Defects

import certificate manually

efa certificates device install --ips x,y --certType

Allow firmware download process to complete. Status of the same can be checked using command

efa inventory device firmware-download show --fabric {fabric name}

Allow firmware download process to complete. Status of the same can be checked using command

efa inventory device firmware-download show --fabric {fabric name}

When the switch configurations drift from the intended configurations in EFA due to scenarios as follows:

1. L3 Epg is created with large ctag-range (e.g. 2-2000)

2. EFA configured VLANs and PO configurations are manually removed from the switch.

3. Switch is reloaded in maintenance mode

Remove the devices from fabric and re-add

efa fabric device remove --name <fabric-name> --ip <device-ips>

efa inventory device delete --ip <device-ips>

efa fabric device add-bulk --name <fabric-name> --rack <rack-name> --username <username> --password <password> --ip <device-ips>

With below steps issue can be observed.

1) Create VRF/EPG having route target, static route and bgp configuration.

2) Introduce drift in VRF route target or static route or bgp configuration on SLX switch.

3) Update device from efa command "efa inventory device update --ip <device ip>"

4) Check device drift using efa command as "efa inventory drift-reconcile execute --ip <device ip>"

5) VRF shows as "cfg-in-sync" though its child configuration was drifted.

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.

1) Configure non-clos fabric

2) Create tenant, vrf, epg

3) Admin down device

4) Create multiple epg's , delete an existing epg

5) Manually delete vrf from admin down device

6) Admin up device

7) After admin up, for epg which is in delete-pending theapp-state moved to cfg-ready

Execute below steps to hit this condition

1) Create fabric on MCT paired device

2) Create Tenant/PO/VRF/EPG

3) Enable MM mode on both device

4) Perform EFA backup

5) Delete EPG/VRF/PO/Tenant

6) Delete fabric

7) Restore EFA backup

8) Reload device one by one

After these steps check PO on both device, "cluster-client auto" will not configured on first reloaded device.

Please follow below steps,

1) Create tenant/VRF/PO/EPG

2) As soon as EPG creation pushed configuration on device, remove them from device.

3) Check drift using inventory CLI as "efa inventory drift-reconcile execute --ip --device-ip <device ip>"

1) Configure clos fabric (Medium scale fabric)

2) Create tenant

3) Admin down the devices

4) Create port-channels, vrfs and epgs

5) Admin up the following devices

Wait for the DRC to be success

6) Repeat step 3

Wait for the devices to put into maintenance mode

7) Create bgp peer-group and dynamic peers

8) Delete all epg's

9) Repeat step 5

10) Vrfs are getting deleted from admin up devices

11) EPG app-state move to cfg-refresh-err

EPG update anycast-ip-delete operation succeeded for deletion of provisioned anycast-ip for admin-down device.

This issue is observed only if an update anycast-ip-add operation is performed after device is put in admin down state and the new config is in non-provisioned state followed by anycast-ip-delete operation for already configured anycast-ip.

Steps to reproduce issue:

1) Configure EPG with anycast-ip (ipv4/ipv6)

2) Make one device admin-down

3) Anycast-ip update-add new anycast-ip (ipv6/ipv4)

4) Update-delete provisioned anycast-ip configured in step-1 (ipv4/ipv6)

Step (4) should fail as IP is already configured on the device and trying to delete it should fail as part of APS.

1) Add ports in empty EPG

2) Delete ports from epg right away

3) Add ports into EPG. Which can have error.

Please follow below steps,

1) Create fabric/tenant/PO/EPG

2) Take EFA backup

3) Delete EPG/PO/tenant/fabric

4) Restore EFA backup taken in step (2)

5) Delete tenant from which was created before backup

6) Create same tenant again

7) Create PO under same tenant

As after restore MCT peer details are Nil so we need to perform DRC after restore taken backup.

After step (4) above, we need to perform DRC using inventory CLI as

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

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

1) Create L3 EPG with anycast-ip/anycast-ipv6

2) Take one of EPG device administratively down

3) Bring device admin up which was taken down in previous step

4) While device is coming up administratively, try EPG Update "anycast-ip-delete" operation

1) NetConf error for epg update port-group-add operation. Caused due to conflicting anycast-ip added to EPG using anycast-ip-add operation.

2) Error for epg update port-group-add operation. Caused due to configuring different anycast-ip for same vlan in EPG using anycast-ip-add operation.

1) If the user provides conflicting anycast-ip in empty EPG then it should throw an error.

* Create EPG1 with port/po, vrf, vlan, anycast-ip

* Create EPG2 without port/po

* Add new VRF to EPG2

* Add conflicting anycast-ip already used in EPG1 with different vrf

* Add port to EPG

2) Multiple EPG sharing the same VRF, VLAN with different anycast-ip should throw an error.

* Create EPG1 with port/po, vrf, vlan, anycast-ip

* Create EPG2 without port/po

* Add vrf to EPG1 which is used in EPG2

* Add new anycast-ip to EPG

* Add port to EPG (This will cause conflict)

Delete conflicting anycast-ip from EPG.

Add correct anycast-ip.

Add port/po to EPG.

Creating EPG with the same VRF configuration fails due to static route key mismatch.

Steps:

1) Create Tenant, Vrf (with staticRoute), EPG

2) Check "sh run vrf" and "sh run router bgp" on device

3) delete EPG

4) Create VRF on device directly using config in step 2

5) Update inventory service

6) Try to create EPG with same VRF. (compareVrf fails due to key mismatch)

1) Remove Vrf from SLX.

2) Update inventory using "efa inventory device update ..."

3) Create EPG using "efa tenant epg create ..."

Steps to reproduce issue:

1) Assign multiple IPs to the physical port on SLX.

2) Create Tenant using same L3 port.

3) Check Tenant show output.

L3 ports having multiple IPs will have repeated entry in the "efa tenant show" output.

When the ports provided by the user in “tenant update port-delete operation” contains all the ports owned by the port-channel, the PO goes into delete pending state. However, the ports are not deleted from the PO.

They get deleted from the tenant though.

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.

Remove the Trunk Parent port added to the VM and add it back again.

e.g.

Max-L2-ss3VirtIoVM2_Test1==> VM Name

Max-L2-ss3VirtIoTrunkPort2_Test1 ==> Parent Port of the Sub Port that is down

openstack server remove port Max-L2-ss3VirtIoVM2_Test1 Max-L2-ss3VirtIoTrunkPort2_Test1

openstack server add port Max-L2-ss3VirtIoVM2_Test1 Max-L2-ss3VirtIoTrunkPort2_Test1

On SLX use the following commands to get rid of the partial bgp-peer.

SLX(config)# router bgp

SLX(config-bgp-router)# neighbor pg1 peer-group

SLX(config-bgp-router)# no neighbor pg1 peer-group

1) In a CLOS fabric setup with MCT pair of border-leafs, create VRF with routing-type as centralized and select MCT pair of border-leafs as centralized routers.

2) Remove one of the MCT pair border-leaf from the fabric

3) Add same/different border-leaf to the fabric and run fabric configure command

4) Wait for sometime and run VRF Update "centralized-router-add" operation to add newly added border-leaf as centralized router

Run EPG configure as follows:

"efa tenant epg configure --name <epg-name> --tenant <tenant-name>"

1) Confirm firmware download is complete on the device, use “show firmwaredownloadstatus” on the device.

2) Update device in EFA using command: “efa inventory device update --ip <device ip list>”.

3) After this other operation can be performed on the device.

4) This flag will automatically reset via periodic device update however periodic device update interval defaults to 1 hour.

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.

The issue is seen with the below steps

1) Configure a fabric

2) Create Tenant

3) Create multi-homed portchannel

4) Bring one of the devices of the MCT pair(having the PO created in step 3) admin-down to create a partial success topology

5) Create EPGs on the partial success topology

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.