The following defects, which were previously disclosed as open, were resolved in Extreme Fabric Automation 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 2.5.5.
Parent Defect ID: | EFA-5732 | Issue ID: | EFA-5732 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.2.0 |
Symptom: | When firmware download is in progress, fabric delete command is accepted without an error. | ||
Condition: | If fabric delete command is submitted when firmware download is in progress, it fails. |
Parent Defect ID: | EFA-6501 | Issue ID: | EFA-6501 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.3.0 |
Symptom: | Configuration Drift for VRF still shown in "cfg-in-sync" though its child configuration are drifted on SLX switch. |
Parent Defect ID: | EFA-7324 | Issue ID: | EFA-7324 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.3.0 |
Symptom: | Continuous create/delete of BGP peer-group and peer can finally cause CLI errors |
Parent Defect ID: | EFA-8090 | Issue ID: | EFA-8090 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | When a fabric containing more than 15 newly registered devices is deployed using the CLI 'efa fabric configure', an attempt to add ports of any of these devices to a tenant within 5 minutes may fail. The error will indicate that the ports have not yet been registered in the fabric | ||
Condition: | Attempt to add device ports of a recently configured fabric to a tenant may fail with an error indication that the ports have not yet been registered in the fabric |
Parent Defect ID: | EFA-8152 | Issue ID: | EFA-8152 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | While graceful-restart(GR) updating with value TRUE and inflight transition triggered as a part of EFA rollover then update will continue as a part of inflight transition. | ||
Condition: | Update GR with value TRUE and perform EFA rollover on HA setup. |
Parent Defect ID: | EFA-8155 | Issue ID: | EFA-8155 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | "cluster-client auto" is not configured under port channel for first reloaded device. |
Parent Defect ID: | EFA-8257 | Issue ID: | EFA-8257 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | EFA is not able to detect drift for configuration like VRF/VE/VLAN/EVPN |
Parent Defect ID: | EFA-8269 | Issue ID: | EFA-8269 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | EPG app-state moved to cfg-refresh-err after epg delete and admin up |
Parent Defect ID: | EFA-8273 | Issue ID: | EFA-8273 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | EPG Update "vrf-add" operation gives success when EPG is in "vrf-delete-pending" state |
Parent Defect ID: | EFA-8315 | Issue ID: | EFA-8315 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | User adds ports in empty EPG and immediately deletes them. The following adding ports into EPG can have error as duplicate entry |
Parent Defect ID: | EFA-8322 | Issue ID: | EFA-8322 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | EPG Update "anycast-ip-delete" operation gives different output/result when one of the EPG device is admin down |
Parent Defect ID: | EFA-8334 | Issue ID: | EFA-8334 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | system backup and restore causes epg state to be in cfg-refresh-err |
Parent Defect ID: | EFA-8335 | Issue ID: | EFA-8335 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | system backup and restore causes following manual DRC has errors |
Parent Defect ID: | EFA-8443 | Issue ID: | EFA-8443 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | For Tenant created with L3 port having multiple ip-address associated with it, "efa tenant show" will have repeated entries of that L3 port. |
Parent Defect ID: | EFA-8465 | Issue ID: | EFA-8465 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | The "efa inventory device firmware-download prepare add" command fails with "Please specify 'fullinstall' option in firmware download cmdline as GLIBC versions change". |
Parent Defect ID: | EFA-8507 | Issue ID: | EFA-8507 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | Certain vlans are missed in configuration when stacks are created in quick succession within a script with no delay. |
Parent Defect ID: | EFA-8512 | Issue ID: | EFA-8512 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | On SLX there can have partial config of neighbor under router bgp. The "show running command router bgp" from SLX shows invalid command "neighbor pg1" (Assume the bgp-group name is pg1). There's no corresponding command to delete this. |
Parent Defect ID: | EFA-8517 | Issue ID: | EFA-8517 |
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Config deployment on EFA takes longer time after stack create complete |
Parent Defect ID: | EFA-8526 | Issue ID: | EFA-8526 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | VRF Update "centralized-router-add" fail with error "[x, y] are MCT pair. Update the VRF with both devices together as centralized routers" |
Parent Defect ID: | EFA-8573 | Issue ID: | EFA-8573 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | In few cases, networks in EPG will remain in cfg-in-sync state even if they are created with partial success topology (MCT pair with one admin-up device and one admin-down device). |
Parent Defect ID: | EFA-8628 | Issue ID: | EFA-8628 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | Tenant does not contain any Ports, state of EPG is "vrf-delete-pending" and EPG Update "vrf-delete" fail with error- "EPG cannot be updated with tenant having no ports" |
Parent Defect ID: | EFA-8665 | Issue ID: | EFA-8665 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.1 |
Symptom: | VRF configuration present on Border Leaf devices |
Parent Defect ID: | EFA-8669 | Issue ID: | EFA-8669 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | EFA is not reachable after secondary node down/up of 8720. (kube-system pods are not responding) |
Parent Defect ID: | EFA-8701 | Issue ID: | EFA-8701 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.1 |
Symptom: | EFA becomes unresponsive and the OS reports that there is no disk space. |
Parent Defect ID: | EFA-8773 | Issue ID: | EFA-8773 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.1 |
Symptom: | When the address family config is manually removed from the SLX followed by DRC, the DRC fails with the error - "Error: VRF Address Family not configured". |
Parent Defect ID: | EFA-8802 | Issue ID: | EFA-8802 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.1 |
Symptom: | Same epg will be allowed to update with different port properties value, however the first configured value will take effect |
Parent Defect ID: | EFA-8827 | Issue ID: | EFA-8827 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.1 |
Symptom: | CEP port will remain in "cfg-refreshed" state even after the DRC is successful. |
Parent Defect ID: | EFA-8848 | Issue ID: | EFA-8848 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.1 |
Symptom: | When a configuration drift is introduced on a physical port on the SLX device, followed by a DRC on the device, the reconcile status displays "Portchannel" and "Vlan" reconciliation status as success even though the same were not drifted. |
Parent Defect ID: | EFA-8966 | Issue ID: | EFA-8966 |
---|---|---|---|
Severity: | S4 - Low | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.0 |
Symptom: | BGP peer group deletion fails when the deletion is attempted using a tenant not owning the BGP peer group. |
Parent Defect ID: | EFA-9009 | Issue ID: | EFA-9009 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Creation or update of an EPG involving a port group comprising more than 50 ports and 100 or more VLANs may take more than 6 minutes and may fail |
Parent Defect ID: | EFA-9065 | Issue ID: | EFA-9065 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.3 |
Symptom: | EFA Port Channel remains in cfg-refreshed state when the port-channel is created immediately followed by the EPG create using that port-channel |
Parent Defect ID: | EFA-9346 | Issue ID: | EFA-9346 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | When the MCT Port channel membership is changed via config changes on SLX (out of band), Fabric service will not mark the device to be in cfg-refreshed state |
Parent Defect ID: | EFA-9400 | Issue ID: | EFA-9400 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.4 |
Symptom: | When the EPG is in "port-group-delete-pending" state, the subsequent "port-group-delete" operations will not clean up any configurations from the admin up devices. |
Parent Defect ID: | EFA-9443 | Issue ID: | EFA-9443 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | resilient-hash max-path is seen on the vrf even though it was deleted from the VRF (when the device was down) using VRF update rh-max-path-delete operation followed by the admin up of the device. |
Parent Defect ID: | EFA-9451 | Issue ID: | EFA-9451 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.3 |
Symptom: | In a brownfield deployment with the existing/stale MCT cluster-client configuration imported into EFA, the EPG creation fails when the MCT cluster-client ID conflicts with the MCT cluster-client ID already consumed by an out-of-band created MCT cluster-client. |
Parent Defect ID: | EFA-9467 | Issue ID: | EFA-9467 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | When a BGP peer-group create with an invalid MD5 password is attempted on an SLX device via EFA, the creation will fail with a valid error from SLX, resulting in the rollback of the failed operation which further results in a stale/partial configuration "neighbor <peer-group-name>" on the SLX. |
Parent Defect ID: | EFA-9487 | Issue ID: | EFA-9487 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | When bgp static peers are created (on a partial success topology) with the target device being admin down device followed by admin up of the admin down device, the dev-state/app-state continue to be not-provisioned/cfg-refreshed instead of provisioned/cfg-in-sync. |
Parent Defect ID: | EFA-9932 | Issue ID: | EFA-9932 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | System API throws a 502 error after a restore is run. |
Parent Defect ID: | EFA-9941 | Issue ID: | EFA-9941 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.3 |
Symptom: | EPG create with a CEP port (already used in another EPG) fails with the NETCONF RPC Error "NOTAKNOWNRESOURCEID" |
Parent Defect ID: | EFA-9944 | Issue ID: | EFA-9944 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | If port channel speed is modified on the device. In the mean time member ports are deleted from PO. Issue DRC from EFA, the DRC will fail with error and PO speed is not get reconciled: "10.20.246.3:ethernet:0/19 to Portchannel po2 failed due to netconf rpc [error] %Error: Port-channel should be admin down for speed to be configured" |
Parent Defect ID: | EFA-9945 | Issue ID: | EFA-9945 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Make config changes of channel group mode on SLX for the interface belongs to some PO. Issue DRC from EFA. Drift and reconcile will not detect this change and correct it. |
Parent Defect ID: | EFA-9968 | Issue ID: | EFA-9968 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | DRC fail with error "Delete and Update operations are not supported in a singled transaction. Please try them individually." |
Parent Defect ID: | EFA-9974 | Issue ID: | EFA-9974 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | [SQA] DRC after firmware download failed with reason 'drift and reconcile failed due to efa failover' |
Parent Defect ID: | EFA-9988 | Issue ID: | EFA-9988 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | If the SLX device is in firmware-download-in-progress state, then the DRC (drift and reconcile) fails, But the failure reason is not shown in the DRC output |
Parent Defect ID: | EFA-10016 | Issue ID: | EFA-10016 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: |
BGP Peer creation fails with the error "failed to fetch BgpAddressFamily data" because of the intermittent connectivity loss of EFA with SLX. Rollback also failed leaving the stale config on SLX. |
Parent Defect ID: | EFA-10018 | Issue ID: | EFA-10018 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Deployment may fail in the step "Checking default gateway reachability on all nodes" due to network reachability issue with gateway |
Parent Defect ID: | EFA-10022 | Issue ID: | EFA-10022 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | questions on EFA for static vs dynamic LAG delay |
Parent Defect ID: | EFA-10041 | Issue ID: | EFA-10041 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | The "efa inventory device tpvm-upgrade execute" command to upgrade to a new tpvm version will result in a failed tpvm upgrade where the previous tpvm image will be rolled back and restored. |
Parent Defect ID: | EFA-10052 | Issue ID: | EFA-10052 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | After upgrade EFA from pre-2.5.0 to 2.5.0, the "Fabric Status" in "efa fabric show" is shown as "configure-success". |
Parent Defect ID: | EFA-10064 | Issue ID: | EFA-10064 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | During the required fullinstall firmware download of SLXOS from 20.2.3f to 20.3.2a the TPVM configuration through exec-mode commands are not converted to the running-config. |
Parent Defect ID: | EFA-10067 | Issue ID: | EFA-10067 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | In a node replacement scenario, the standby node will not have a TPVM configured nor running. When the "efa inventory device tpvm-upgrade" command is run against this replacement node, the TPVM deployment and upgrade to the new TPVM version fails. |
Parent Defect ID: | EFA-10071 | Issue ID: | EFA-10071 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | [EFA] - High CPU on logrotate - making EFA slow |
Parent Defect ID: | EFA-10073 | Issue ID: | EFA-10073 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Getting Error : Port :172.16.18.3:port-channel:1 ClientID : 1001 already configured, conflicting with tenant-service generated ID 1 |
Parent Defect ID: | EFA-10094 | Issue ID: | EFA-10094 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | In a fabric-wide firmware download, other firmware download operations such as firmware commit and restore error out stating that a firmware download execution is in progress. However, after the active EFA node switch is upgraded and rebooted, this check is no longer enforced and other firmware download operations are allowed even though the fabric-wide firmware download operation is still in progress. |
Parent Defect ID: | EFA-10099 | Issue ID: | EFA-10099 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: |
When the md5-password is updated on an already provisioned fabric, the existing tenant vrf backup routing bgp neighbours will be updated with the new md5-password followed by the clearing of the bgp neighbours. Updation of md5-password and clearing of the corresponding bgp neighbours happens one SLX device at a time, hence resulting in the session being down time till the process is complete for both the devices of the MCT pair. |
Parent Defect ID: | EFA-10115 | Issue ID: | EFA-10115 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Redeployment of EFA 2.5.0 fails on a multi-node when one of the nodes in the cluster is changed. |
Parent Defect ID: | EFA-10121 | Issue ID: | EFA-10121 |
---|---|---|---|
Severity: | S2 – High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | TPVM and Apps/EFA running in TPVM, will be removed after copy default-config startup-config" and "reload system" commands on SLX. |
Parent Defect ID: | EFA-10126 | Issue ID: | EFA-10126 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Users might see a failure message when doing a node replacement when running the installer in GUI mode, when the progress is around 18% although the node replacement proceeds |
Parent Defect ID: | EFA-10135 | Issue ID: | EFA-10135 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Efa system - manual setting of backup schedule not taken into use |
Parent Defect ID: | EFA-10137 | Issue ID: | EFA-10137 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Efa fabric device add-bulk failed with Validate Fabric [Failed] Missing Links |
Parent Defect ID: | EFA-10139 | Issue ID: | EFA-10139 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | efa fabric device add-bulk failed with Server unreachable during leaf-pair expansion |
Parent Defect ID: | EFA-10141 | Issue ID: | EFA-10141 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | [EFA] - HA Deployment 2.5.0 - Configuring database server Failed |
Parent Defect ID: | EFA-10142 | Issue ID: | EFA-10142 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Journals are kept under pending status even though dynamic marking of failure when the parent journal fails |
Parent Defect ID: | EFA-10143 | Issue ID: | EFA-10143 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Modifications needed in the current efa-journal Table display entries |
Parent Defect ID: | EFA-10206 | Issue ID: | EFA-10206 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | [EFA 2.4 -> 2.5] KeepAlived log files changed to check reachability of Peer or GW is not updated any more |
Parent Defect ID: | EFA-10243 | Issue ID: | EFA-10243 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | Portchannels, EndpointGroups port configuration is not reconciled on SLX |
Parent Defect ID: | EFA-10266 | Issue ID: | EFA-10266 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | When concurrent EPG update on bd-enabled tenant with vrf-add operation is requested where the commands involve large number of vlans, local-ip and anycast-ip addresses, one of them may fail with the error "EPG: <epg-name> Save for Vlan Records save Failed". |
Parent Defect ID: | EFA-10267 | Issue ID: | EFA-10267 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | [EFA] Inconsistencies OpenAPI definition |
Parent Defect ID: | EFA-10284 | Issue ID: | EFA-10284 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: |
When a bgp peer-group update operations are performed after the device is admin down, the entire config from admin up device gets deleted. Steps to reproduce this issue: 1. Create bgp peer group 2. Admin down both devices 3. peer add fails with appropriate message 4. Admin up one of the devices 5. perform peer-group add 6. update bgp peer group to delete the peer that was created in step 1 for both devices 7. perform bgp configure operation while one of the devices is still in admin down state After performing the configure operation when one of the devices is still down, the entire config from admin up device gets deleted. |
Parent Defect ID: | EFA-10285 | Issue ID: | EFA-10285 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | [EFA] Slow upgrade of SLX OS on EFA - 6 hours for 18 switches |
Parent Defect ID: | EFA-10289 | Issue ID: | EFA-10289 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | EFA performs "copy running-config startup-config" after firmware download is started ( just before reload) which causes config loss during SLX full install scenario |
Parent Defect ID: | EFA-10304 | Issue ID: | EFA-10304 |
---|---|---|---|
Severity: | S3 – Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | NTP configuration present on SLX is not considered by EFA for DRC |
Parent Defect ID: | EFA-10358 | Issue ID: | EFA-10358 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | SLX upgrade to 20.3.2A - traffic outage + Maintenance Mode Disable Failed |
Parent Defect ID: | EFA-10365 | Issue ID: | EFA-10365 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.6 |
Symptom: | Found cluster in unstable state after spontaneous + ~simultaneous reboot. |
Parent Defect ID: | EFA-10370 | Issue ID: | EFA-10370 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | A tpvm-upgrade and firmware-download execution can be launched simultaneously which could possibly lead to both EFA HA nodes going down at the same time. |
Parent Defect ID: | EFA-10380 | Issue ID: | EFA-10380 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | When preparing the fabric for a firmware-download where the fabric has more than 10 devices, up to 10 devices will be prepared successfully but the rest of the devices will error out stating "Cannot find firmware. The server is inaccessible or firmware path is invalid. Please make sure the server name or IP address, the user/password and the firmware path are valid." |
Parent Defect ID: | EFA-10403 | Issue ID: | EFA-10403 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | EFA fabric state shows as "cfg-refreshed", and there is drift in the configuration identified by EFA compare with SLX. |
Parent Defect ID: | EFA-10412 | Issue ID: | EFA-10412 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | While polling the "efa inventory device firmware-download show" command, the user can sometimes observe the firmware download status change to the "Firmware Committed" status completion after the device has been reloaded with the new firmware during the workflow, but then change back and continue to the end. |
Parent Defect ID: | EFA-10446 | Issue ID: | EFA-10446 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | Issue with CLOS Spine SLX upgrade via EFA 2.5.1 - Upgrade complete - status down. |
Parent Defect ID: | EFA-10451 | Issue ID: | EFA-10451 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | The tpvm-upgrade command fails during the device "TPVM Upgrade" step with a "Detailed Status" of "device tpvm upgrade has completed, but the trusted peer configuration could not be reconfigured on the device." |
Parent Defect ID: | EFA-10452 | Issue ID: | EFA-10452 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | EFA 2.5.1 - SLX-OS : 20.2.3fa --> 20.3.2b upgrade issues |
Parent Defect ID: | EFA-10456 | Issue ID: | EFA-10456 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | 'efa inventory device firmware-download show' loses info about switches upgraded but not committed. |
Parent Defect ID: | EFA-10459 | Issue ID: | EFA-10459 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | Tenant creation fails: Error: sql: transaction has already been committed or rolled back |
Parent Defect ID: | EFA-10461 | Issue ID: | EFA-10461 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | DRC is incorrectly reconciling ports resulting in SLX stuck in maintenance mode |
Parent Defect ID: | EFA-10466 | Issue ID: | EFA-10466 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | what are the different stages during FWDL of status field |
Parent Defect ID: | EFA-10468 | Issue ID: | EFA-10468 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: |
When the MCT Port channel attribute like description, speed is changed by user through SLX CLI or other out of band means, "efa fabric show --name fabric_name" doesn't show the app state of the device as "cfg refreshed". When the MCT Port channel member attribute like port description, lacp mode, lacp timeout or lacp type is changed by user through SLX CLI or other out of band means, "efa fabric show --name fabric_name" doesn't show the app state of the device as "cfg refreshed". |
Parent Defect ID: | EFA-10473 | Issue ID: | EFA-10473 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.4.6 |
Symptom: | attempting to update the description field for a peer-group |
Parent Defect ID: | EFA-10503 | Issue ID: | EFA-10503 |
---|---|---|---|
Severity: | S3 - Medium | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | Stop/Start the TPVM executed on the EFA standby node causes HA failover. |
Parent Defect ID: | EFA-10504 | Issue ID: | EFA-10504 |
---|---|---|---|
Severity: | S2 - High | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | drift reconcile looses native-vlan setting (EFA upgrade & switch reload) |
Parent Defect ID: | EFA-10521 | Issue ID: | EFA-10521 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | DRC fails after SLX upgrade (via EFA) from 20.2.3d to 20.2.3fa |
Parent Defect ID: | EFA-10524 | Issue ID: | EFA-10524 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.0 |
Symptom: | efa fabric delete" returns "Bad Gateway" |
Parent Defect ID: | EFA-10532 | Issue ID: | EFA-10532 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | Subinterfaces and virtual routes are not available after 'efa restore' with system generated backup file. |
Parent Defect ID: | EFA-10537 | Issue ID: | EFA-10537 |
---|---|---|---|
Severity: | S4 - Minor | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | The command "efa inventory device firmware-download prepare add" fails with "Duplicate entry for key device_id". |
Parent Defect ID: | EFA-10540 | Issue ID: | EFA-10540 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | The firmware-download restore command does not wait for drift-reconciliation completion even though the restore workflow for the device states that it is completed successfully. |
Parent Defect ID: | EFA-10542 | Issue ID: | EFA-10542 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | DRC is not reconciling VLAN configs on phy ports or port-channels for VLAN based network EPGs. |
Parent Defect ID: | EFA-10552 | Issue ID: | EFA-10552 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | .SLX upgrade (via EFA) from 20.2.3d to 20.2.3fa failed with DRC timeout |
Parent Defect ID: | EFA-10571 | Issue ID: | EFA-10571 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | POs in not connected state after upgrading and running drift-reconcile |
Parent Defect ID: | EFA-10573 | Issue ID: | EFA-10573 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | EFA port dampening - does not throw error in case of invalid command syntax |
Parent Defect ID: | EFA-10585 | Issue ID: | EFA-10585 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | VLAN and Ve conf for one Border Leaf is also pushed to the other |
Parent Defect ID: | EFA-10587 | Issue ID: | EFA-10587 |
---|---|---|---|
Severity: | S4 - Minor | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | .EFA Periodic Backup shown as User Generated |
Parent Defect ID: | EFA-10591 | Issue ID: | EFA-10591 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | EFA 2.5.2 Re-deploy post a TPVM Rollback failed on first attempt. Failed to start efa services |
Parent Defect ID: | EFA-10614 | Issue ID: | EFA-10614 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | efa command fails with "dial tcp xx.xx.xx.xx:80: connect: connection refused" message |
Parent Defect ID: | EFA-10618 | Issue ID: | EFA-10618 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | .EFA - Border-Leaf role missing from software - efa inventory device list |
Parent Defect ID: | EFA-10682 | Issue ID: | EFA-10682 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.1 |
Symptom: | .EPG cannot be created only with the non-existing port channel name |
Parent Defect ID: | EFA-10691 | Issue ID: | EFA-10691 |
---|---|---|---|
Severity: | S2 - Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | EFA CLI error response: Service Unavailable |
Parent Defect ID: | EFA-10696 | Issue ID: | EFA-10696 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | SLX hangs in maintenance mode for about 1 hour after reboot |
Parent Defect ID: | EFA-10715 | Issue ID: | EFA-10715 |
---|---|---|---|
Severity: | S3 – Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.3 |
Symptom: |
EFA will incorrectly report static IPs are not configured after the following sequence of steps: add static IPs; remove static IPs; readd same static IPs. |
||
Workaround: | Confirm the existence of the static IPs on the TPVM by viewing the following file: /apps/efadata/misc/multiaccess/mgmt_static_ips.txt |
Parent Defect ID: | EFA-10746 | Issue ID: | EFA-10746 |
---|---|---|---|
Severity: | S3 – Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
Symptom: | no backup was generated with 'efa system backup --device-ip' |
Parent Defect ID: | EFA-10762 | Issue ID: | EFA-10762 |
---|---|---|---|
Severity: | S3 - Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.2 |
Symptom: | Couldn‘t use “&” symbol in password for firmware-download from EFA |
Parent Defect ID: | EFA-11059 | Issue ID: | EFA-11059 |
---|---|---|---|
Severity: | S3 – Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
Symptom: | EFA port dampening - does not throw error in case of invalid command syntax |
Parent Defect ID: | EFA-11094 | Issue ID: | EFA-11094 |
---|---|---|---|
Severity: | S3 – Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
Symptom: | EFA return 'invalid value' output for 100Mbps set speed command |
Parent Defect ID: | EFA-11203 | Issue ID: | EFA-11203 |
---|---|---|---|
Severity: | S3 – Moderate | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
Symptom: | All tenant CLI commands result in failure. | ||
Condition: | 'efactl status' command shows more than two pods in Running state on standby node. | ||
Recovery: | Reboot the standby node to correct the state of the system. Rerun commands after the system is restored. |
Parent Defect ID: | EFA-11342 | Issue ID: | EFA-11342 |
---|---|---|---|
Severity: | S2 – Major | ||
Product: | Extreme Fabric Automation | Reported in Release: | EFA 2.5.4 |
Symptom: |
Issue#1: Unexpected error updating traefik with new certificates Issue#2: EFA CLI doesn‘t work(efa login command fails) |
||
Condition: |
Condition for Issue#1 : One of the node goes into NotReady state(Kubernetes node). This results in traefik pod to take some time to come up.
Condition for Issue#2 : Kubernetes considers traefik pod is in active-active state instead of active/standby. |
||
Recovery |
Recovery for Issue#1: No impact on EFA functionality. EFA will recover once the Node status is back to normal which usually takes a few minutes.
Recovery for Issue#2: EFA is not usable. Reload of the node will recover the system |