Defects Closed with Code Changes

The following defects, which were previously disclosed as open, are resolved in EFA 2.4.0.

Parent Defect ID: EFA-3512 Issue ID: EFA-3512
Severity: S4 - Low
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: EPG create might fail with VNI resource not being available in the fabric
Condition:

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.

Parent Defect ID: EFA-3694 Issue ID: EFA-3694
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Request processing takes longer time and CLI remains hung till the request is processed. EPG update may fail if the wait time is more than 16 minutes.
Condition:

1. Create EPG with 100 networks.

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

Parent Defect ID: EFA-3717 Issue ID: EFA-3717
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.1.0
Symptom: BD based L3 EPG networks will go into cfg-refresh-err state if out-of-band configured BD-LIFs (without associated VLAN) are present on the switch.
Condition:

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.

Parent Defect ID: EFA-4056 Issue ID: EFA-4056
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom:

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.

Condition:

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.

Parent Defect ID: EFA-5064 Issue ID: EFA-5064
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom:

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.

Condition: Configure L3 EPG with only anycast-ip and no anycast-ipv6.
Parent Defect ID: EFA-5257 Issue ID: EFA-5257
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom:

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.

Condition: Issue can be observed when vrf-add and vrf-delete operation is executed on Endpoint Group in quick succession multiple times.
Parent Defect ID: EFA-5623 Issue ID: EFA-5623
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: Drift and reconcile logs are not notified to the Notification engine.
Parent Defect ID: EFA-5675 Issue ID: EFA-5675
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: EPG update "vrf-add" operation can fail with the reason as vrf to be added has conflicting vrf on the switch.
Condition:

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.

Parent Defect ID: EFA-5708 Issue ID: EFA-5708
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: Device status remains in cfg-in-sync when devices have mismatch in selective configs w.r.t to intended configs
Condition: Periodic discovery identifies the drift and raise appropriate events; most of the events that are handled do not change the device state from cfg-in-sync to cfg-refresshed
Parent Defect ID: EFA-5834 Issue ID: EFA-5834
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: EPG creation with 4K ctags can result in switch going un-responsive
Condition: EPG create operation with 4K ctags.
Parent Defect ID: EFA-5936 Issue ID: EFA-5936
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: Overlay-Gateway/Cluster Instance is remaining on the switch.
Condition: Configure EPG/Networks on a fabric device and delete device from the fabric.
Parent Defect ID: EFA-6318 Issue ID: EFA-6318
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.1
Symptom: In Case of Clos Fabric , Cluster drift gets identified for all the devices which are part fabric as soon as fabric gets created even though actual drift is not present on the SLX switch.
Condition:

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.

Parent Defect ID: EFA-7062 Issue ID: EFA-7062
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Device settings for Maintenance mode in EFA is not updated when the device's state changes.
Condition: Device may come out of Maintenance mode state based on actions from EFA like Drift-reconcile or a change via CLI in SLX device. The latest state of device will not be automatically updated in the 'efa inventory device settings show' in efa
Parent Defect ID: EFA-7080 Issue ID: EFA-7080
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom:

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.

Condition:

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.

Parent Defect ID: EFA-7114 Issue ID: EFA-7114
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom:

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

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

Condition:

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.

Parent Defect ID: EFA-7119 Issue ID: EFA-7119
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: If any delete nature CLI of "service bgp peer" has failed then bgp service status is not moving to the "delete-pending" state.
Condition:

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.

Parent Defect ID: EFA-7132 Issue ID: EFA-7132
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Vlan description is missing after reconciliation
Condition:

- Remove the VLAN configuration from the device

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

- Description configuration is missing for reconciled VLANs

Parent Defect ID: EFA-7142 Issue ID: EFA-7142
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Pressing the tab key in the EFA command line when the current command is complete and has no further available options can result in the command being executed silently by the shell.
Condition: This is not reliably reproducible.
Parent Defect ID: EFA-7144 Issue ID: EFA-7144
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: 'Drift and Reconcile' for a device is skipped when EFA admin of device is performed with 'force' option
Condition: When 'efa inventory admin-state up' command is issued with a 'forcce' option
Parent Defect ID: EFA-7155 Issue ID: EFA-7155
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom:

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.

Condition:

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.

Parent Defect ID: EFA-7159 Issue ID: EFA-7159
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: MCT Port Channel Admin State is not reconciled
Condition: Issue will be observed when 1. MCT PO connecting the leaf pair is administratively shut-down explicitly via out of band management application like CLI and 2. maintenance-mode is set to enable-on-reboot and 3. Device is reloaded. After reload, Drift and reconcile doesn't set the admin state of MCT PO to UP.
Parent Defect ID: EFA-7181 Issue ID: EFA-7181
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Reconcilation of drifted Tenant Configuration fails for scaled configuration
Condition: Reconcile fails for a device on which EFA has configured many L3 networks (more than 300+ Networks) by one or more tenants.
Parent Defect ID: EFA-7200 Issue ID: EFA-7200
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: "router bgp" configs will be missing on the devices but Tenant service will not show drift for those configs and hence it will not reconcile those missing configs.
Condition:

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.

Parent Defect ID: EFA-7234 Issue ID: EFA-7234
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Reconciliation of drifts in the port-channel and description does not happen
Condition: This problem occurs only when drift is introduced specifically on speed and description along with admin-state or cluster-client configuration.
Parent Defect ID: EFA-7261 Issue ID: EFA-7261
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: "efa tenant epg show" and "efa tenant po show" will not reflect correct drift status if aggregator ports are removed.
Condition: This display issue is seen only when aggregator port is removed from device.
Parent Defect ID: EFA-7304 Issue ID: EFA-7304
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: While trying to upgrade from secure mode setup, the EFA installer prompts the user to choose between Secure mode and Standard mode.
Condition: This will be seen when proceeding through the menu options whenever an upgrade is performed.
Parent Defect ID: EFA-7312 Issue ID: EFA-7312
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom:

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

Drift-reconcile get triggered after default heartbeat miss threshold.

Condition: HA double fault failure.
Parent Defect ID: EFA-7322 Issue ID: EFA-7322
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Firmware-download 'Update State' shows 'In Progress' indefinitely when triggered on Active Node's SLX
Condition: When SLX firmware upgrade is initiated from the EFA (deployed in HA mode) on the same SLX device where EFA is co-resident and is current active node.
Parent Defect ID: EFA-7345 Issue ID: EFA-7345
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: A single-node EFA install at version 2.2 failed to upgrade to 2.3.
Condition: EFA 2.2 to EFA 2.3 upgrade fails only when EFA 2.2 was upgraded (not fresh install) from EFA 2.1.
Parent Defect ID: EFA-7396 Issue ID: EFA-7396
Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom: If EPG is in delete-pending state with partially cleaned up vlan config on port-channels, deleting the EPG could fail. EPG could remain in delete-pending state unless deleted with force option.
Condition: This condition can happen if EPGs in delete-pending state have partially cleaned up vlan configuration on port-channels. That is, the vlan configuration on port-channel is cleaned up on some devices. Deleting the EPG errors out stating that the configuration does not exist.
Parent Defect ID: EFA-7404 Issue ID: EFA-7404
Severity: S1 - Critical
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom: After firmware download devices from fabric shows a "cfg refresh error" state.
Condition: Inventory service discovery happened before lldp links got enabled on devices.
Parent Defect ID: EFA-7411 Issue ID: EFA-7411
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom: EFA firmware download fails intermittently
Condition: In cases where the switch config is large, this issue is observed intermittently
Parent Defect ID: EFA-7452 Issue ID: EFA-7452
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom: Maintenance mode triggered DRC (Drift and Reconcile) times out (and fails) with the scaled tenant configuration.
Condition:

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).

Parent Defect ID: EFA-7459 Issue ID: EFA-7459
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom: EFA firmware download fails
Condition: After starting EFA Firmware download the switch does not reboot and firmware download fails intermittently
Parent Defect ID: EFA-7538 Issue ID: EFA-7538
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom:

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.

Condition: Reloading both the SLX nodes multiple times.
Parent Defect ID: EFA-7565 Issue ID: EFA-7565
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: Portchannel Deletion failed with error "invalid character 'B' looking for beginning of value"
Condition:

1) Tenant service is stopped/not running

2) Portchannel delete command run

Parent Defect ID: EFA-7568 Issue ID: EFA-7568
Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.2
Symptom: Unable to re-install EFA in a multi-node environment after TPVM upgrade.
Condition: If TPVM upgrade is not performed using the procedure described in the deployment guide, under the section 'Upgrade SLX-OS, TPVM, and EFA Together'