The following defects, which were previously disclosed as open, were resolved in Extreme Fabric Automation 3.0.0.
| Parent Defect ID: | EFA-11335 | Issue ID: | EFA-11335 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | On scaled setup CLI: "efa tenant service bgp peer operational show" failed with the error "service is not available". | ||
| Condition: |
Below are the steps to reproduce the issue: 1. A tenant is configured with the member ports spanning across 8 devices of the fabric. 2. All 8 devices are configured with 100 VRFs and each VRF has 2 static and 1 dynamic peer. 3. Execute "efa tenant service bgp peer operational show" |
||
| Workaround: | Execute "efa tenant service bgp peer operational show --tenant <tenant-name> --vrf <tenant-vrf-name>" instead of "efa tenant service bgp peer operational show --tenant <tenant-name>" or "efa tenant service bgp peer operational show" | ||
| Parent Defect ID: | EFA-12133 | Issue ID: | EFA-12133 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | On the last port-group delete, VRF VRF1 is not cleaned up from the device, when the VRF is shared across the EPGs. | ||
| Condition: |
Below are the steps to reproduce the issue: 1. Create L3 EPG EPG1 with Device1Port1 and VRF1. 2. Create L3 EPG EPG2 with Device1Port2, Device2Port1, and VRF1 3. Update EPG EPG2 with "port-group-delete" of Device1Port2 4. Update EPG EPG1 with "port-group-delete" of Device1Port1. This is the last port getting deleted from the device which should have resulted in the deletion of the VRF VRF1 from the Device1. |
||
| Recovery: |
Recovery way 1: 1. Delete EPG1. 2. EPG2 update with port-group add D1P2 and then remove D1P2 from EPG. After the port removal D1P2 (last-port) vrf will be removed from the device.
Recovery way 2: Manually remove the vrf from the device.. Inventory update. |
||
| Parent Defect ID: | EFA-12710 | Issue ID: | EFA-12710 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: |
With rollback , Multi-node upgrade with node replacement is not supported. This happens when user gives command efa deploy with-rollback for multi-node replacement, user is given option 1) Multi Node Build Upgrade and 2) Multi Node Build Upgrade With Node Replacement . If user chooses the option 2 Multi Node Build Upgrade With Node Replacement . Installer prompts "With rollback , replacement upgrade not supported Do you wish to restart the install? (yes/no)" |
||
| Condition: | This happens when user gives command efa deploy with-rollback for Multi Node Build Upgrade With Node Replacement | ||
| Workaround: |
When the installer prompts, 1) Multi Node Build Upgrade and 2) Multi Node Build Upgrade With Node Replacement . if User presses option 2 , Installer prompts "With rollback , replacement upgrade not supported Do you wish to restart the install? (yes/no)" User can input no to halt the installation and press yes if he wants to go for option 1) Multi Node Build Upgrade |
||
| Recovery: |
When the installer prompts, 1) Multi Node Build Upgrade and 2) Multi Node Build Upgrade With Node Replacement . if User presses option 2 , Installer prompts "With rollback , replacement upgrade not supported Do you wish to restart the install? (yes/no)" User can input no to halt the installation |
||
| Parent Defect ID: | EFA-12823 | Issue ID: | EFA-12823 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | Prefix Independent Convergence is not detected as drifted and it will not get reconciled. | ||
| Condition: | Occasionally when preforming DRC in maintenance mode on reboot state, the Prefix Independent Convergence fails to detect refreshed state. | ||
| Workaround: | Working around the drift detection is done by validating Prefix Independent Convergence has not drifted before reloading into maintenance mode. | ||
| Recovery: | When Prefix Independent Convergence is not being detected as refreshed, re-configuring the value will enable drift detection to function. | ||
| Parent Defect ID: | EFA-13080 | Issue ID: | EFA-13080 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | Some configurations when removed from the device will not cause the EFA to move the device to cfg-refresh state. | ||
| Condition: |
Case1: EFA doesn't move device to config-refresh on device update. Config does NOT Reconcile on drift-reconcile: Fabric devices app state should be cfg-refreshed, after peer-keepalive configuration removed manually in slx Fabric devices app state should be cfg-refreshed, after "ip address" configuration under a fabric interface removed manually in slx Fabric devices app state should be cfg-refreshed, after loopback interface configuration under a fabric is removed manually in slx Fabric devices app state should be cfg-refreshed, after "address-family l2vpn evpn" is removed Fabric devices app state should be cfg-refreshed, after "no neighbor <ip> next-hop-self" is removed Case2 : EFA doesn‘t move device to config-refresh on device update. Config does Reconcile on manual drift-reconcile: Fabric devices app state should be cfg-refreshed, after "maximum-paths" configuration under router bgp removed manually in slx Fabric devices app state should be cfg-refreshed, after "graceful-restart" configuration under router bgp removed manually in slx |
||
| Workaround: |
Manually configure the device back in case 1 Run manual drift-reconcile OR manually configure device back will recover the config in case 2 |
||
| Parent Defect ID: | EFA-13083 | Issue ID: | EFA-13083 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | "efa tenant po show", "efa tenant vrf show", "efa tenant epg show", "efa tenant service mirror session show" doesn't show the configuration in cfg-refreshed state even though the configurations (which should have been present but) are not present on the SLX | ||
| Condition: |
Below are the steps to reproduce the issue 1. Configure fabric, tenant, po, vrf, epg, mirror session 2. Execute "efa system backup" 3. Delete the devices from inventory 4. Execute "efa system restore" using the backup taken in step 2 5. Execute "efa tenant po show", "efa tenant vrf show", "efa tenant epg show", "efa tenant service mirror session show" |
||
| Recovery: | Execute "efa inventory device update --ip <device-ip>" and then check the output of "efa tenant po show", "efa tenant vrf show", "efa tenant epg show", "efa tenant service mirror session show" to see the configurations in cfg-refreshed state | ||
| Parent Defect ID: | EFA-13187 | Issue ID: | EFA-13187 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | EFA REST CLI to fetch list of tenants can fail with error "Error : Cannot find Tenant <tenant-name>" when there are large number of tenants and epgs configured on them. | ||
| Condition: | When there are large number of tenants with ports spanning across 30+ devices with multiple EPGs configured, database access can be under heavy load causing the above error | ||
| Workaround: | This is a transient error. Re-execute the same REST command. If this error is observed, information about individual tenant objects can be fetched by 'efa tenant show --name <tenant-name>' | ||
| Recovery: | There is no recovery required as the EFA and SLX configurations are not altered as part of this issue | ||
| Parent Defect ID: | EFA-13254 | Issue ID: | EFA-13254 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.1 |
| Symptom: | 3 of EFA Pods fails Liveliness or Readiness checks causing Init containers to stop and causing crashloopback | ||
| Parent Defect ID: | EFA-13322 | Issue ID: | EFA-13322 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: |
At the end of upgrade, the installer displays a message associated with a fresh install and not an upgraded install. The installer will show "Extreme Fabric Automation Stack is now deployed and ready" instead of "Extreme Fabric Automation Stack has been upgraded successfully" This is harmless and the upgrade procedure is unaffected. |
||
| Condition: | When a single-node installation of EFA is upgraded using the SLX CLI with-rollback option | ||
| Parent Defect ID: | EFA-13370 | Issue ID: | EFA-13370 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.7.0 |
| Symptom: | No alert messages are sent to configured syslog relp subscribers when there is a failure while configuring inventory device interface settings such as admin state, speed, mtu etc. | ||
| Condition: | The lack of logging occurs when there is a failure while configuring inventory device interface settings, such as a failure to establish connection to a device. | ||
| Workaround: | The failure is logged in the inventory log file and can be reviewed there. | ||
| Recovery: | After the failure condition is corrected there is no need for an alert message to be sent to configured syslog relp subscribers. | ||
| Parent Defect ID: | EFA-14427 | Issue ID: | EFA-14427 |
|---|---|---|---|
| Severity: | S3 - Moderate | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.5 |
| Symptom: | .FlexiLab - How to migrate EFA from one machine to other | ||
| Parent Defect ID: | EFA-14773 | Issue ID: | EFA-14773 |
|---|---|---|---|
| Severity: | S2 - Major | ||
| Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.6.1 |
| Symptom: | efa system backup fabric failing with error "tls: bad record mac" | ||