Defects Closed without Code Changes
The following defects were closed in Extreme Fabric Automation 3.1.0.
| Parent Defect ID: |
EFA-13339 |
Issue ID: |
EFA-13339 |
| Reason Code: |
Insufficient Information |
| 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-14667 |
Issue ID: |
EFA-14667 |
| Reason Code: |
Working as Designed |
| 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 border-leaf from spine
pod and connect directly to the super-spine pod |
| Parent Defect ID: |
EFA-14860 |
Issue ID: |
EFA-14860 |
| Reason Code: |
Configuration/User Error |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.6.1 |
| Symptom: |
EFA multi node build upgrade with
node replacement fails with (exit code 255) |
| Parent Defect ID: |
EFA-14940 |
Issue ID: |
EFA-14940 |
| Reason Code: |
Already Implemented |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.0 |
| Symptom: |
EFA Upgrade from 2.6.1 to 2.7 has
missing config or database and is in default |
| Parent Defect ID: |
EFA-15099 |
Issue ID: |
EFA-15099 |
| Reason Code: |
Not Reproducible |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.5.5 |
| Symptom: |
EFA command "efa inventory device
update" failed with : Reason: context deadline exceeded |
| Parent Defect ID: |
EFA-15194 |
Issue ID: |
EFA-15194 |
| Reason Code: |
Will Not Fix |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.0 |
| Symptom: |
Disabling TLS1.0 and TLS1.1 |
| Parent Defect ID: |
EFA-15281 |
Issue ID: |
EFA-15281 |
| Reason Code: |
Insufficient Information |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.5.5 |
| Symptom: |
Devices in "cfg refreshed"
state |
| Parent Defect ID: |
EFA-15332 |
Issue ID: |
EFA-15332 |
| Reason Code: |
Question Answered |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.5.4 |
| Symptom: |
EFA 2.5.4 Active TPVM went to down
status for about 1 minute |
| Parent Defect ID: |
EFA-15415 |
Issue ID: |
EFA-15415 |
| Reason Code: |
Configuration/User Error |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.2 |
| Symptom: |
EFA "execute-cli" command failed due
to HTTP server not accepting connections (for extended
period) |
| Parent Defect ID: |
EFA-15450 |
Issue ID: |
EFA-15450 |
| Reason Code: |
Already Implemented |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.5.5 |
| Symptom: |
EFA system back-up "stuck" |
| Parent Defect ID: |
EFA-15480 |
Issue ID: |
EFA-15480 |
| Reason Code: |
Insufficient Information |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.5.5 |
| Symptom: |
Cannot create L3 HandOff EPG due to
the reuse of BD and VNI |
| Parent Defect ID: |
EFA-15487 |
Issue ID: |
EFA-15487 |
| Reason Code: |
Insufficient Information |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 3.1.0 |
| Symptom: |
Need notification of the
certification expiry after login into the efa . Working in 2.7.1 but
not in 3.0.0 |
| Parent Defect ID: |
EFA-15507 |
Issue ID: |
EFA-15507 |
| Reason Code: |
Not a Software Defect |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.2 |
| Symptom: |
TPVM failed to upgrade from 4.5.1 >
4.5.3 |
| Parent Defect ID: |
EFA-15514 |
Issue ID: |
EFA-15514 |
| Reason Code: |
Not Reproducible |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.2 |
| Symptom: |
EFA 3.0.0 VM is down, came up when
stop services |
| Parent Defect ID: |
EFA-15867 |
Issue ID: |
EFA-15867 |
| Reason Code: |
Cannot Fix |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.0 |
| Symptom: |
TPVM missing after Standby SLX was
upgraded |
| Parent Defect ID: |
EFA-15872 |
Issue ID: |
EFA-15872 |
| Reason Code: |
Working as Designed |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.0 |
| Symptom: |
Device has a VRF VoLTE configuration
with different number of Static Routes |
| Parent Defect ID: |
EFA-15935 |
Issue ID: |
EFA-15935 |
| Reason Code: |
Working as Designed |
| Product: |
Extreme Fabric Automation |
Reported in Release: |
EFA 2.7.2 |
| Symptom: |
EFA Rest responses are not in link
with EFA CLI |