The following defects are open in Extreme Fabric Automation 3.0.0.
| Parent Defect ID: | EFA-9570 | Issue ID: | EFA-9570 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
| Symptom: | Add Device Failed because ASN used in border leaf showing conflict | ||
| Condition: | If there are more than one pair of Leaf/border leaf devices then devices which are getting added first will get the first available ASN in ascending order and in subsequent addition of devices if one of device is trying to allocate the same ASN because of brownfield scenario then EFA will throw an error of conflicting ASN | ||
| Workaround: |
Add the devices to fabric in the following sequence 1)First add devices that have preconfigured configs 2)Add remaining devices that don't have any configs stored |
||
| Recovery: |
Removing the devices and adding the devices again to fabric in following sequence 1)First add devices that have preconfigured configs 2)Add remaining unconfigured devices. |
||
| Parent Defect ID: | EFA-10062 | Issue ID: | EFA-10062 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
| Symptom: | Removing a device from Inventory does not clean up breakout configuration on interfaces that are part of port channels. | ||
| Condition: | This condition occurs when there is breakout configuration present on device that is being deleted from Inventory, such that those breakout configurations are on interfaces that are part of port-channels | ||
| Workaround: | Manually remove the breakout configuration, if required. | ||
| Recovery: | Manually remove the breakout configuration, if required. | ||
| Parent Defect ID: | EFA-10063 | Issue ID: | EFA-10063 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
| Symptom: | Deleting device from EFA Inventory does not bring up the interface to admin state 'up' after unconfiguring breakout configuration | ||
| Condition: | This condition occurs when there is a breakout configuration present on the device that is being deleted from EFA Inventory | ||
| Workaround: | Manually bring the admin-state up on the interface, if required | ||
| Recovery: | Manually bring the admin-state up on the interface, if required | ||
| Parent Defect ID: | EFA-12784 | Issue ID: | EFA-12784 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| 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 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| 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-13124 | Issue ID: | EFA-13124 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | When endpoint group create or update operation REST requests of multiple endpoint groups each with 50+ ctags are issued concurrently, one or two of the requests can fail with "Error 1452: Cannot add or update a child row: a foreign key constraint fails" or with an error indicating database timeout or an error indicating failure of network property delete. | ||
| Condition: | When multiple endpoint group requests are processed concurrently, some of the database requests initiated by EFA can cause database to abort one of the request with the above mentioned error | ||
| Workaround: | Execute the commands sequentially | ||
| Recovery: | EFA database and SLX device configurations are always not affected by this error and hence no recovery is required. The failed commands shall be rerun sequentially to successful completion of the expected operations | ||
| Parent Defect ID: | EFA-13171 | Issue ID: | EFA-13171 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: |
After fabric configure, when neighbor device goes down or comes up, based on how other devices are connected to it, events are triggered on the affected (connected) devices where few validations are done and errors if found are stored for each device. These errors can be seen in "efa fabric error show --name <fabric-name>" output. If DRC is performed on any of these devices having errors and if drift and reconcile are success, then the device will be shown as cfg in-sync state in "efa fabric show" output but errors will continue to exist for the device in "efa fabric error show" output Note: The inconsistency between the output of "efa fabric show" and "efa fabric error show" has no functional impact. |
||
| Condition: |
1) Create and configure clos 2) Bring one of the leaf node down (i.e. reload the device) 3) The affected (connected) devices will move to 'cfg refresh error' that can be seen in "efa fabric show" output and the actual errors can be seen in "efa fabric error show --name <fabric-name>" output 4) Perform DRC with reconcile option on one of the device in 'cfg refresh error' by executing "efa inventory drift-reconcile execute --ip <deviceIP> --reconcile" 5) If DRC is succeeds, then the "efa fabric show" output displays the above device (which was in 'cfg refresh error' state) in "cfg in-sync" state and "efa fabric error show" output will continue to display the errors that were seen for the same device in step (3) |
||
| Recovery: | Subsequent execution of "efa fabric configure" command will bring consistency in the outputs. | ||
| Parent Defect ID: | EFA-13178 | Issue ID: | EFA-13178 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| 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 after the devices are completed going through DRC | ||
| Recovery: | Recovery would be to run DRC operation on that device again after the backup is completed. | ||
| Parent Defect ID: | EFA-13339 | Issue ID: | EFA-13339 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | The EFA notification service does not send a syslog alert message when an EFA inventory device firmware-download operation fails. | ||
| Condition: | The user attempts to prepare a device for a firmware download using "efa inventory device firmware-download prepare add --ip <device IP>" when the device's management connectivity is unreachable. | ||
| Workaround: | Although the syslog alert message is not available, both the CLI and REST response contain an appropriate error message about the reason for the firmware-download prepare error and the device's connectivity issue. | ||
| Recovery: | None | ||
| Parent Defect ID: | EFA-14289 | Issue ID: | EFA-14289 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| 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-14407 | Issue ID: | EFA-14407 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | Super spine devices continue to remain in cfg-refreshed state even after the invalid topology connections (i.e. superspine to superspine connections) are removed by disabling the LLDP links between the super spine devices followed by a DRC (Drift and Reconcile) | ||
| Condition: |
Below are the steps to reproduce the issue 1. Configure a 5-stage CLOS fabric 2. Enable the LLDP link(s) between the superspine devices 3. App state of superspine devices moves to cfg-refresh-error 4. Disable the LLDP link(s) (which were enabled in step 2) between the superspine devices 5. App state of superspine devices moves to cfg-refreshed 6. Execute "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" for the super-spine devices |
||
| Recovery: | Execute "efa fabric configure --name <fabric-name>" so that the superspine devices move to cfg-in-sync state | ||
| Parent Defect ID: | EFA-14474 | Issue ID: | EFA-14474 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| 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-14667 | Issue ID: | EFA-14667 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | In a 5-stage clos, if border-leaf is not connected to super-spine and it is connected to one/more spine devices, validation succeeds without any error and fabric comes up | ||
| Condition: |
1) Create a 5-stage clos fabric with border-leaf node connected to one/more spine devices and not connected to super-spine node 2) Configure fabric |
||
| Recovery: | Separate the bordel-leaf from spine pod and connect directly to the super-spine pod | ||
| Parent Defect ID: | EFA-14687 | Issue ID: | EFA-14687 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.0 |
| Symptom: | DRC will not identify the drift and hence will not reconcile the drifted configuration | ||
| Condition: |
Below are the steps to reproduce the issue: 1. Configure multi rack Non-CLOS fabric. 2. Manually remove the below set of configurations on device under router-bgp no neighbor 172.x.x.x password xxxx no neighbor 172.x.x.x update-source loopback 1 no neighbor 172.x.x.x peer-group overlay-ebgp-group address-family l2vpn evpn no retain route-target all 3. Execute "efa inventory drift-reconcile execute --ip <device-ip>" |
||
| Recovery: | Manually reconfigure the removed configurations from the device | ||
| Parent Defect ID: | EFA-14283 | Issue ID: | EFA-14283 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 3.0.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 | ||