The following defects were closed in Extreme Fabric Automation 2.7.0.
| Parent Defect ID: | EFA-9456 | Issue ID: | EFA-9456 |
|---|---|---|---|
| Reason Code: | Insufficient Information | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.3 |
| Symptom: | EFA fabric configuration fails on a large fabric topology of 30 switches. | ||
| Condition: | The issue will be observed if devices being added to fabric have IP addresses assigned on interfaces and these IP addresses are already reserved by EFA for other devices. | ||
| Workaround: |
Delete the IP addresses on interfaces of devices having conflicting configuration so that new IP addresses can be reserved for these devices. One way to clear the device configuration is using below commands: 1. Register the device with inventory efa inventory device register --ip <ip1, ip2> --username admin --password password 2. Issue debug clear "efa fabric debug clear-config --device <ip1, ip2>" |
||
| Recovery: |
Delete the IP addresses on interfaces of devices having conflicting configuration so that new IP addresses can be reserved for these devices. One way to clear the device configuration is using below commands: 1. Register the device with inventory efa inventory device register --ip <ip1, ip2> --username admin --password password 2. Issue debug clear "efa fabric debug clear-config --device <ip1, ip2>" 3. Add the devices to fabric |
||
| Parent Defect ID: | EFA-9799 | Issue ID: | EFA-9799 |
|---|---|---|---|
| Reason Code: | Already Implemented | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
| Symptom: | 'efa status' response shows standby node status as 'UP' when node is still booting up | ||
| Condition: | If SLX device is reloaded where EFA standby node resides, then 'efa status' command will still show the status of standby as UP. | ||
| Workaround: | Retry the same command after some time. | ||
| Parent Defect ID: | EFA-10093 | Issue ID: | EFA-10093 |
|---|---|---|---|
| Reason Code: | Working as Designed | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
| Symptom: | Deletion of the VLAN/BD based L3 EPGs in epg-delete-pending state will result in creation and then deletion of the VLAN/BD on the admin up device where the VLAN/BD was already removed | ||
| Condition: |
Issue occurs with the below steps: 1. Create L3 EPG with VLAN/BD X on an MCT pair 2. Admin down one of the devices of the MCT pair 3. Delete the L3 EPG. This results in the L3 configuration removal (corresponding to the L3 EPG getting deleted) from the admin up device and no config changes happen on the admin down device and the EPG transits to epg-delete-pending state 4. Admin up the device which was made admin down in step 2 5. Delete the L3 EPG which transited to epg-delete-pending state in step 3 |
||
| Recovery: | Not needed | ||
| Parent Defect ID: | EFA-10525 | Issue ID: | EFA-10525 |
|---|---|---|---|
| Reason Code: | Already Reported | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
| Symptom: | -EFA OVA services not starting if no IP address is obtained on bootup. | ||
| Condition: |
When EFA OVA is deployed, and does not obtain a DHCP IP address, not all EFA services will start |
||
| Workaround: |
Configure static IP, or obtain IP address from DHCP. cd /opt/godcapp/efa type: source deployment.sh When the EFA installer appears, select Upgrade/Re-deploy Select OK Select single node, Select OK Select the default of No for Additional management networks. Select yes when prompted to redeploy EFA. Once EFA has redeployed, all services should start |
||
| Parent Defect ID: | EFA-10684 | Issue ID: | EFA-10684 |
|---|---|---|---|
| Reason Code: | Insufficient Information | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
| Symptom: | EFA cannot start - Init:ErrImageNeverPull | ||
| Parent Defect ID: | EFA-12058 | Issue ID: | EFA-12058 |
|---|---|---|---|
| Reason Code: | Not Reproducible | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.0 |
| Symptom: | The error 'Error updating traefik with efasecret' is seen during node replacement. | ||
| Condition: | EFA node replacement is successful. | ||
| Workaround: | Re-add subinterfaces using 'efa mgmt subinterfaces' CLI. | ||
| Parent Defect ID: | EFA-12081 | Issue ID: | EFA-12081 |
|---|---|---|---|
| Reason Code: | Insufficient Information | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
| Symptom: | Installing k3s container orchestration Failed. | ||
| Workaround: | Feature is already implemented in EFA 2.5.3 | ||
| Parent Defect ID: | EFA-12105 | Issue ID: | EFA-12105 |
|---|---|---|---|
| Reason Code: | Already Implemented | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.0 |
| Symptom: | A "Drift Reconcile Completion Status Failure" may occur during an EFA firmware download of an SLX device in a fabric. | ||
| Condition: |
A DRC status failure can occur if the SLX device also fails during the firmware download. The DRC failure is observed during the drift-reconcile completion step on either the spine node that is hosting the active EFA node TPVM or any device in the same firmware download group which is concurrently running the firmware download workflow at the time of HA failover. This is likely due to the SLX device rebooting and activating the new firmware. During the EFA HA failover, the REST endpoint for the go-inventory service is not established properly and causes the drift-reconcile process to fail. |
||
| Workaround: | None | ||
| Recovery: | Run "efa inventory drift-reconcile execute --ip <SLX device IP address> --reconcile" to retry the drift-reconcile process on the failed device. | ||
| Parent Defect ID: | EFA-12154 | Issue ID: | EFA-12154 |
|---|---|---|---|
| Reason Code: | Already Implemented | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.0 |
| Symptom: | A firmware download can fail with "Firmware Download Failed" status. | ||
| Condition: |
1) The current SLX firmware version on the devices which are being upgraded must be 20.2.3c, 20.2.3d, 20.2.3e, and 20.3.4. 2) The --noAutoCommit flag is specified for firmware download execution. 3) Any device that is in the same firmware download group with the device hosting the active EFA node, can encounter the firmware download failure. The firmware download failure occurs when the active EFA node is reloaded to activate the new firmware while the other device is in the middle of an SLX firmware download. The HA failover will cause the firmware download workflows to be restarted at the last completed step. Since the SLX firmware download did not complete, the SLX firmware download command will be issued to the device again. The SLX firmware 20.2.3c through 20.3.4 returns an error stating that it "Cannot start download before the new image is committed." |
||
| Workaround: | Prepare a group list that contains only active EFA nodes and execute at the end of the SLX upgrade cycle | ||
| Parent Defect ID: | EFA-12228 | Issue ID: | EFA-12228 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | Efa system backup failure | ||
| Recovery: | No Recovery | ||
| Parent Defect ID: | EFA-12247 | Issue ID: | EFA-12247 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
| Symptom: | EFA External DCO Interface went missing post EFA Upgrade | ||
| Condition: | When EFA is upgraded to a newer version, EFA backup is taken before the upgrade procedure is triggered. The backup file is named "EFA-Upgrade-<Version>-<Build>.tar". If restore is performed using this backup file, then management subinterfaces and routes will not be available. | ||
| Workaround: |
For restore procedure, use any 'User' generated backup file. The migration support was actually added in EFA 2.5.4 |
||
| Recovery: | In case the restore is already performed, then recreate the subinterfaces and routes using CLI. | ||
| Parent Defect ID: | EFA-12331 | Issue ID: | EFA-12331 |
|---|---|---|---|
| Severity: | S3 – Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | DRC takes too long to complete when a switch reload causes a transient Kubernetes error. | ||
| Recovery: | The system will recover on its own | ||
| Parent Defect ID: | EFA-12429 | Issue ID: | EFA-12429 |
|---|---|---|---|
| Reason Code: | Not Reproducible | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.0 |
| Symptom: | After failover active EFA down, Standby is up | ||
| Parent Defect ID: | EFA-12539 | Issue ID: | EFA-12539 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.1 |
| Symptom: | EPG update request with port-group-add operation and EPG create request where multiple ctags are mapped to one bridge-domain, may fail with error "Error 1452: Cannot add or update a child row" | ||
| Condition: |
Error will be observed when one of the following use cases are executed on bridge-domain enabled tenant. Use case-1: 1. Create an EPG with multiple ctags mapped to one bridge-domain and with ports across SLX devices that are not part of an MCT pair Use case-2: 1. Create an EPG with multiple ctags mapped to one bridge-domain and with ports or port-channels on one SLX device 2. Update the EPG with port(s) on new SLX device that is not an MCT pair of first device |
||
| Workaround: | Create the EPG with all the required ports and with one ctag-bridge-domain mapping first. Then do epg update with ctag-add-range operation to add additional ctags to the same bridge-domain | ||
| Recovery: | Rollback is automatically performed so no stale config is left on the switch. No recovery is required | ||