The following defects, which were previously disclosed as open, were resolved in Extreme Fabric Automation 3.1.0.
| Parent Defect ID: | EFA-12784 | Issue ID: | EFA-12784 |
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: |
After fabric configure if lldp links on slx devices are manually made no shut, "efa fabric debug config-gen-reason --name <fabric-name> --device <device-ip>" will display added entries for device. After sometime even if devices are shown as cfg-in-sync in "efa fabric show", "efa fabric debug config-gen-reason --name <fabric-name> --device <device-ip>" will display the added lldp entries. Again if other lldp links of the same device are added, "efa fabric debug config-gen-reason <>" command will display the previously added entries along with the newly added lldp entries. |
||
| Condition: |
1) Create and configure clos/non-clos fabric 2) Add new lldp links between any two devices of the fabric 3) Execute "efa inventory device update", followed by "efa fabric show" and "efa fabric debug config-gen-reason" 4) Again add new lldp links between the same devices of the fabric 5) Execute "efa inventory device update", followed by "efa fabric show" and "efa fabric debug config-gen-reason" 6) LLDP entries added in both step (2) and step (4) are displayed in "efa fabric debug config-gen-reason" |
||
| Recovery: | The inconsistency between the output of "efa fabric show" and "efa fabric debug config-gen-reason" has no functional impact. Subsequent execution of "efa fabric configure" command will bring the consistency in the outputs. | ||
| Parent Defect ID: | EFA-12792 | Issue ID: | EFA-12792 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | Considering D1 and D2 are the connected fabric devices when the "ip address" configuration is removed from a fabric interface of D1, the device D2 will be marked as cfg-refreshed | ||
| Condition: |
Below are the steps to reproduce the issue: 1) D1 and D2 are the connected fabric devices. "ip address" configuration from a fabric interface is removed manually from the fabric device D1 2) Trigger DRC on the device D1 or re-configure the ip address (removed in step 1) on the fabric device D1 3) Fabric device D2 connected to the device D1 will move to cfg-refreshed state |
||
| Workaround: | |||
| Recovery: |
Either wait for auto-update or manually perform inventory update. CLI to perform manual recovery "efa inventory device update --ip <remoted-device-ip>" Note: The app state of the device D2 will be marked as cfg-in-sync in the subsequent cycle of inventory device update which is auto-triggered every 30 minutes. |
||
| Parent Defect ID: | EFA-13178 | Issue ID: | EFA-13178 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | Fabric configuration failed to reconcile when DRC was on-going and user initiated a EFA backup | ||
| Condition: | EFA's backup needs to stop services to ensure that the database is in quiet state, so that the backup is consistent. | ||
| Workaround: | Users should run a backup once the devices are completed going through DRC | ||
| Recovery: | Recovery would be to run DRC operation on that device again once the backup is completed. | ||
| Parent Defect ID: | EFA-14289 | Issue ID: | EFA-14289 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | When BGP or Static Prefix Independent Convergence is configured as disabled, Drift and Reconcile will not address a drifted state. | ||
| Condition: | The condition is that Prefix Independent Convergence is configured as the default value of disabled on EFA, but the SLX has drifted off of the default value into enabled. | ||
| Workaround: | Prefix Independent Convergence reconcile failure can be worked around by configuring as enabled or by avoiding configuring SLX manually off of the default disabled state. | ||
| Recovery: | Prefix Independent Convergence drift must be reconciled on the SLX device. | ||
| Parent Defect ID: | EFA-14447 | Issue ID: | EFA-14447 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | Linux exit codes for failed EFA commands return incorrectly. | ||
| Parent Defect ID: | EFA-14474 | Issue ID: | EFA-14474 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | During the device removal from fabric, the ip and ipv6 access-list configurations are not removed from the device | ||
| Condition: |
Below are the steps to reproduce the issue: 1) Configure 5-stage CLOS fabric 2) Create EPG of type port-profile on the spine/super spine devices along with port-profile ACLs 3) Remove spine/super spine device from fabric |
||
| Recovery: | Manually remove the stale ip/ipv6 ACLs from the device | ||
| Parent Defect ID: | EFA-14823 | Issue ID: | EFA-14823 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | When the BGP peers are created with update source IPv6 values that are not in a compressed format or which have capitals in them (Example: fd00:1:950::A and fd00:1:950::0) followed by the execution of the DRC, then the bgp peers transition to cfg-refreshed state | ||
| Condition: |
Steps to reproduce: 1. Create a bgp peer with update source ip in non compressed format or with capitals 2. Do an inventory DRC with drift only 3. The bgp peers get into a refreshed state because of the update source ip mismatch |
||
| Workaround: | Create the bgp peers with compressed update source ips and without capitals | ||
| Recovery: | Delete the bgp peer through EFA and recreate it through EFA using compressed update source ips and without capitals | ||
| Parent Defect ID: | EFA-14895 | Issue ID: | EFA-14895 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | .efa tenant update results in error message "....not available in the application" | ||
| Parent Defect ID: | EFA-14943 | Issue ID: | EFA-14943 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.1 |
| Symptom: | EFA Upgrade from 2.6.1 to 2.7 fails at "Error in database migration for policy" | ||
| Parent Defect ID: | EFA-15341 | Issue ID: | EFA-15341 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | Port 8079 of standby (efa/tpvm) ip is responding to request when using tls1.0 and tls1.1 | ||
| Parent Defect ID: | EFA-15521 | Issue ID: | EFA-15521 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.3.2 |
| Symptom: | in a EVPN EFA setup how is loopback addresses distributed ? | ||
| Parent Defect ID: | EFA-15665 | Issue ID: | EFA-15665 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.6 |
| Symptom: | EFA upgrade 2.17 (2.4.6 GA) ->2.22 (3.0.0 GA) failed | ||
| Parent Defect ID: | EFA-15731 | Issue ID: | EFA-15731 |
|---|---|---|---|
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | efa stopped working because of some pods went down | ||