Defects Closed without Code Changes

The following defects are closed in EFA 2.4.0.

Parent Defect ID: EFA-2857 Issue ID: EFA-2857
Reason Code: Will Not Fix Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: Addition of fabric ports and MCT ports to the tenant succeeds even though these ports cannot be used to connect to any endpoints.
Condition: Addition of fabric ports (ports connecting leaf to spine, spine to super-spine etc) and MCT ports (ports connecting the multi-homed leaf) to the tenant.
Workaround: Fabric ports and MCT ports to be not added to the tenant.
Parent Defect ID: EFA-4045 Issue ID: EFA-4045
Reason Code: Not Reproducible Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.1.0
Symptom: MCT configuration of two leafs on already Configured fabric was modified manually by replacing the existing MCT ports with a different ports and later updating inventory causing the Leaf devices to go into refresh error, expectation was to push the config of old MCT ports to new
Workaround:

Configure the fabric with force

efa fabric configure --name <> --force

Recovery: Reconfigure fabric with force
Parent Defect ID: EFA-5590 Issue ID: EFA-5590
Reason Code: Already Reported Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: EFA CLI behavior on pressing <tab> following a complete command will execute the command handler or will get stuck in cli if waiting on user input on background
Condition:

(efa:root)root@ubuntu:~/efa/efa_40# efa inventory rma execute --ip 10.24.95.157 --co<tab>

- cli gets stuck and needs ^C^C to exit, as it is waiting on user input on backend

(efa:extreme)extreme@tpvm2:~$ efa fabric create --name fab4 – <tab>

- this creates a fabric

Workaround: These can be avoided by using ‘?‘ before the tab and using the complete command options. In most cases this behavior will not cause an issue, but issue may be seen in cases where there are multiple optional keywords eg in fabric-create, rma execute, fabric add bulk , etc.
Recovery: Press ^C^C to exit a command thats stuck on cli. Reverse any command executed as above, if it is not intended.
Parent Defect ID: EFA-5689 Issue ID: EFA-5689
Reason Code: Feature/Function Not Supported Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: VRF Backup routing configuration on the SLXOS-9140 will be inadequate and hence the backup routing functionality will not work on SLXOS-9140.
Condition: L3 EPG create or update operation with the member ports residing on SLXOS-9140.
Workaround: Backup routing needs to be disabled at the fabric setting level if the fabric has SLXOS-9140 devices.
Recovery: Backup routing needs to be disabled at the fabric setting level if the fabric has SLXOS-9140 devices.
Parent Defect ID: EFA-5952 Issue ID: EFA-5952
Reason Code: Design Limitation Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.2.0
Symptom: While executing drift-reconcile port-channels created between MCT pairs and are part of EPG's will be shown as drifted even though the SLX running config is in sync.
Condition: This happens when drift is executed while SLX is in maintenance mode.
Recovery: Turn off maintenance mode and execute inventory device update which will sync the right status.
Parent Defect ID: EFA-6835 Issue ID: EFA-6835
Reason Code: Already Implemented Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: EFA CLIs did not respond following bulk add of devices
Condition: Register more 7 devices into EFA at same time using add-bulk fabric CLI in HA multi-node setup.
Workaround: Register less then 5 devices in EFA at same time.
Recovery: Restart the EFA sever by reloading the Switch.
Parent Defect ID: EFA-7237 Issue ID: EFA-7237
Reason Code: Already Reported Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom:

EFA system backup is generated using efa system backup command.

Undeply EFA and install fresh EFA

Restore EFA backup generated earlier using "efa system restore" command

The restore process preserves the config backup interval and count. However the auto config backup process is not taking backups as configured.

Condition: Auto Config backup process does not take expected number of backups as configured.
Workaround: User can take config backup manually using "efa inventory config-backup execute".
Recovery: Fresh install or restart of EFA application would start the auto config backup process
Parent Defect ID: EFA-7264 Issue ID: EFA-7264
Reason Code: Not Reproducible Severity: S2 - High
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: After SLX Switch reload, Configuration drift in port channel members do not get reconciled by EFA
Condition:

Below are the steps when the configuration drift created does not get reconciled by EFA:

- Configuration of fabric/tenant/po/vrf/epg

- 'maintenance mode enable-on-reboot ' enabled on the switch

- Drift in configuration created by deleting port channel

- Reloading of the switch

- As part of reconcilation, port channel was created but Eth <port> was not aggregated to channel-group.

Workaround: None
Recovery:

Execute manual Drift and Reconcile using this command:

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

Parent Defect ID: EFA-7326 Issue ID: EFA-7326
Reason Code: Cannot Fix Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: VRF used in EndpointGroup having invalid Target Network cause Drift & Reconcile operation to fail with error- "Target network is invalid"
Condition:

1) VRF is created with Invalid Target Network in earlier version of EFA (before EFA 2.3.0)

2) EndpointGroup is created with same VRF in earlier version of EFA (before EFA 2.3.0)

3) Drift and Reconcile operation is performed

Workaround: NA
Recovery:

1) Delete EndpointGroup using VRF having invalid Target Network

2) Delete VRF

3) Recreate VRF with valid Target Network

4) Recreate EndpointGroup with new VRF

Parent Defect ID: EFA-7389 Issue ID: EFA-7389
Reason Code: Will Not Fix Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.0
Symptom: In a very rare scenario, http daemon may not start
Workaround: Reload SLX device
Parent Defect ID: EFA-7406 Issue ID: EFA-7406
Reason Code: Working as Designed Severity: S3 - Medium
Product: Extreme Fabric Automation Reported in Release: EFA 2.3.1
Symptom: When EPG deleted during admin-down for any device, after admin-up for that device app-state changed to cfg-refreshed
Condition:

1) Configure non-clos fabric

2) Create tennat, vrf, po and epg's

3) Make any of the device to admin down

4) During admin-down, delete one of the epg's created

5) Make same device admin-up

6) EPG app-state moved to cfg-refreshed instead of cfg-in-sync

Workaround: NA
Recovery: Delete epg once device admin state is up.