The following defects were closed in Extreme Fabric Automation 2.6.1.
| Parent Defect ID: | EFA-10305 | Issue ID: | EFA-10305 |
|---|---|---|---|
| Reason Code: | Not Reproducible | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.2 |
| Symptom: | EndpointGroup creation fail with error - "Device: <ip-address> has a VRF <vrf-name> configuration with different number of Static Routes" | ||
| Workaround: | No workaround | ||
| Recovery: |
Below are the steps to recover from the issue: 1. Delete VRF from all EndpointGroups by performing EPG Update <vrf-delete> operation 2. Add VRF to EndpointGroups by performing EPG Update <vrf-add> operation |
||
| Parent Defect ID: | EFA-10387 | Issue ID: | EFA-10387 |
|---|---|---|---|
| Reason Code: | Already Reported | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
| 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-10389 | Issue ID: | EFA-10389 |
|---|---|---|---|
| Reason Code: | Not Reproducible | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
| Symptom: | When upgrade process is quit at any possible stage, older EFA stack doesn't get identified from the same node on which process has been initiated. | ||
| Condition: |
If user selects "No" when EFA asks for final confirmation before upgrade process gets started, the process gets terminated, but older stack can't be identified any longer on SLX. Checking "show efa status" reflects "EFA application is not installed. Exiting..." However there is no functional impact on EFA setup and EFA setup continues to work properly on TPVMs with existing version. |
||
| Workaround: | Upgrade process can be initiated again from peer node | ||
| Parent Defect ID: | EFA-10398 | Issue ID: | EFA-10398 |
|---|---|---|---|
| Reason Code: | Working as Designed | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
| Symptom: | EFA Tenant REST Request fails with an error "service is not available or internal server error has occurred, please try again later" | ||
| Condition: | Execution of the EFA Tenant REST requests which take more time (more than 15 minutes) to get completed | ||
| Workaround: |
Execute "show" commands to verify if the failed REST request was indeed completed successfully. Re-execute the failed REST request as applicable. |
||
| Recovery: | No recovery | ||
| Parent Defect ID: | EFA-10778 | Issue ID: | EFA-10778 |
|---|---|---|---|
| Reason Code: | Insufficient Information | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.3 |
| Symptom: | efa inventory device firmware-download prepare': 'Failed to prepare devices' | ||
| Condition: | |||
| Workaround: | Wait for FWDL to complete. We will lock out any modifications to the prepared list while a FWDL execution is in progress for the given fabric, even if it's a device that is not undergoing a FWD | ||
| Recovery: | |||
| Parent Defect ID: | EFA-10879 | Issue ID: | EFA-10879 |
|---|---|---|---|
| Reason Code: | Insufficient Information | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.3 |
| Symptom: | switch hangs in MM mode | ||
| Condition: | ssh rule is missing in iptables after maintenance mode reboot. | ||
| Parent Defect ID: | EFA-10967 | Issue ID: | EFA-10967 |
|---|---|---|---|
| Reason Code: | Already Reported | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.3 |
| Symptom: | Fabric-wide Firmware download will fail on timeout if the number of devices in the prepare group is greater than 5. | ||
| Workaround: | The number of devices in the Fabric-wide Firmware download prepare group should be less than or equal to 5. | ||
| Parent Defect ID: | EFA-11238 | Issue ID: | EFA-11238 |
|---|---|---|---|
| Reason Code: | Already Implemented | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | Services restarted due to Kubernetes restarting. Kubernetes restarted because Mariadb was not ready for a while. | ||
| Workaround: | Rebooting the node would fix this issue and cause Mariadb and Galera cluster to come up in the right states | ||
| Recovery: | Rebooting the node should fix this issue, however there no better workaround at the moment | ||
| Parent Defect ID: | EFA-11401 | Issue ID: | EFA-11401 |
|---|---|---|---|
| Reason Code: | Configuration/User Error | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | Execution error: 500 Internal Server Error after upgrade to 2.5.4 | ||
| Condition: | If invalid IP address are provided in virtual routes CLI. | ||
| Parent Defect ID: | EFA-11421 | Issue ID: | EFA-11421 |
|---|---|---|---|
| Reason Code: | Configuration/User Error | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.6 |
| Symptom: | EFA upgrade failed from 2.4.6 to 2.5.4 -Installation failed. | ||
| Condition: | If old EFA installation was not complete | ||
| Parent Defect ID: | EFA-11606 | Issue ID: | EFA-11606 |
|---|---|---|---|
| Reason Code: | Design Limitation | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
| Symptom: | EFA in non operational state after SLX reboot during EFA upgrade | ||
| Condition: | IF SLX is rebooted during EFA installation. | ||
| Parent Defect ID: | EFA-11674 | Issue ID: | EFA-11674 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | Upgrade from 20.3.2b to 20.3.2d on 18-switch node failed. | ||
| Condition: | uncommitted firmware version on the switches which leads to this error. | ||
| Parent Defect ID: | EFA-11685 | Issue ID: | EFA-11685 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | TPVM upgrade from 4.2.4 to 4.3.0 failed during EFA re-deployment step | ||
| Condition: | If standby tpvm node is shutdown before tpvm upgrade on the active node was completed | ||
| Parent Defect ID: | EFA-11719 | Issue ID: | EFA-11719 |
|---|---|---|---|
| Reason Code: | Feature/Function Not Supported | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | EFA response: Error : undefined response type when issue command "efa fabric setting update --name fab-158 --rack-ld-l3-backup-port 0/30 --rack-ld-mct-ports 0/30,0/31" | ||
| Parent Defect ID: | EFA-11783 | Issue ID: | EFA-11783 |
|---|---|---|---|
| Reason Code: | Configuration/User Error | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | efa inventory drift-reconcile execute is failing. | ||
| Condition: | conflicting out of band entries between SLX' config and tenant's configuration | ||
| Parent Defect ID: | EFA-11798 | Issue ID: | EFA-11798 |
|---|---|---|---|
| Reason Code: | Insufficient Information | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | TPVM Migration Fails while upgrading SLX | ||
| Condition: | Unknown | ||
| Workaround: | Closed due to insufficient information | ||
| Parent Defect ID: | EFA-11876 | Issue ID: | EFA-11876 |
|---|---|---|---|
| Reason Code: | Configuration/User Error | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
| Symptom: | Installation of efa-2.5.4 on ubuntu 18.04 VM fails at 99% | ||
| Condition: | During uninstallation of EFA, there is an error in deletion of efa user | ||
| Parent Defect ID: | EFA-11880 | Issue ID: | EFA-11880 |
|---|---|---|---|
| Reason Code: | Already Reported | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.3 |
| Symptom: | EFA 2.5.2 Re-deploy post a TPVM Rollback failed on first attempt. Failed to start efa services | ||
| Parent Defect ID: | EFA-12283 | Issue ID: | EFA-12283 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | Severity: | S3 - Moderate |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | MGMT Interface - netstat port is not displayed | ||
| Condition: | Not a valid defect | ||
| Parent Defect ID: | EFA-12428 | Issue ID: | EFA-12428 |
|---|---|---|---|
| Reason Code: | Not a Software Defect | Severity: | S2 - Major |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | EFA deploy failed: Default gateway is not reachable | ||
| Condition: | Issue was with customer setup, not a valid defect | ||