The following defects, which were previously disclosed as open, were resolved in Extreme Fabric Automation 2.7.2.
| Parent Defect ID: | EFA-13158 | Issue ID: | EFA-13158 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | "efa inventory drift-reconcile execute --ip <device-ip>" fails with the error "Error: Monitor session already configured" | ||
| Condition: |
Below are the steps to reproduce the issue 1. Create a mirror session on an SLX device using EFA 2. Modify the mirror session configuration on SLX by changing any of the attributes e.g. source, destination, direction, etc. 3. Perform "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" |
||
| Recovery: | Delete existing monitor session from the device and then execute "efa inventory drift-reconcile execute --ip <device-ip>" | ||
| Parent Defect ID: | EFA-13379 | Issue ID: | EFA-13379 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | Some of the backup routing neighbors get stuck in cfg-refreshed state and the same can be seen in the DRC output | ||
| Condition: |
Below are the steps to reproduce the issue 1. Create and configure a fabric with backup routing enabled 2. Create a Tenant, a PO, 5 VRFs and 5 EPGs 3. Update the fabric setting (for the fabric created in step 1) with md5 password 4. Perform fabric configure |
||
| Recovery: |
1. Remove backup routing neighbor md5-password from the VRFs which are in cfg-refreshed state (as seen in the DRC output) 2. Execute DRC to reconcile the configs and to move the cfg-refreshed configurations to cfg-in-sync |
||
| Parent Defect ID: | EFA-13535 | Issue ID: | EFA-13535 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | SLX app-state stuck in cfg-error after toggling MCT cluster ports | ||
| Condition: | |||
| Workaround: | None | ||
| Recovery: | Run device update when observed. | ||
| Parent Defect ID: | EFA-13669 | Issue ID: | EFA-13669 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | A "Tenable"scan detects the use of TL v 1.0 and 1.1. | ||
| Condition: | A "Tenable" scan was done on EFA interfaces on TPVM showing the issue. | ||
| Workaround: | None | ||
| Recovery: | None | ||
| Parent Defect ID: | EFA-13717 | Issue ID: | EFA-13717 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | The command "efa inventory device interface list" for a particular interface will show oper state down when the SLX shows oper state up. | ||
| Workaround: | None | ||
| Recovery: | Run manual device update. | ||
| Parent Defect ID: | EFA-13971 | Issue ID: | EFA-13971 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.1 |
| Symptom: | "Border Leaves (BL's) stop forwarding traffic for ~ 6 minutes when a config restore is performed" | ||
| Condition: | Customer is doing a config restore as part of regression testing and after BL's leave Maintenance mode there is ~6 minute loss of traffic from host devices. After about 6 minutes issue clears and traffic begins to flow again. | ||