The following defects are open in ExtremeCloud Orchestrator 3.2.0.
| Parent Defect ID: | XCO-3438 | Issue ID: | XCO-3438 |
|---|---|---|---|
| Product: | XCO | 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 may 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 may 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: | XCO-3445 | Issue ID: | XCO-3445 |
|---|---|---|---|
| Product: | XCO | 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: | XCO-3448 | Issue ID: | XCO-3448 |
|---|---|---|---|
| Product: | XCO | 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 <fabirc-name>" so that the superspine devices move to cfg-in-sync state | ||
| Parent Defect ID: | XCO-3458 | Issue ID: | XCO-3458 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | Port breakout fails for SLX devices with "generic message error". On device new split ports are created. | ||
| Recovery: |
login to SLX CLI and remove the breakout of port using these steps: Run following commands configuration terminal hardware connector <slot/interface> breakout mode <4x10g/4x25g> no breakout e.g. if the port 0/50 got this issue, following are the commands to run after login to CLI Freedom7-Bng# configure t Entering configuration mode terminal Freedom7-Bng(config)# hardware Freedom7-Bng(config-hardware)# connector 0/50 Freedom7-Bng(config-connector-0/50)# breakout mode 4x10g Freedom7-Bng(config-connector-0/50)# no breakout |
||
| Parent Defect ID: | XCO-3471 | Issue ID: | XCO-3471 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | Stale BGP Peer-group entry configured under router BGP on SLX Border leaf and Spine devices with none of the BGP neighbors linked with the Peer group. | ||
| Condition: |
1. Create a 3-stage CLOS fabric, add devices with MCT leaf, spine, and border-leaf and configure the fabric 2. Convert the 3-stage CLOS fabric to a 5-stage CLOS fabric using the fabric migrate command "efa fabric migrate --type "3-to-5-stage" --source-fabric <source-fabric> --destination-3-stage-leaf-spine-pod <pod-name> --destination-3-stage-border-leaf-pod <pod-name>" 3. Add super-spine POD devices to the migrated 5-stage CLOS fabric 4. Disconnect the BorderLeaf to Spine links and reconnect the BorderLeaf to Super-Spine links 5. Configure the migrated 5-stage CLOS fabric |
||
| Recovery: | Manually delete the stale BGP peer-groups from both the Border Leaf and Spine devices | ||
| Parent Defect ID: | XCO-3472 | Issue ID: | XCO-3472 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | XCO IP/VIP change is not updated on device for telemetry/streaming and syslog | ||
| Condition: | Once the XCO is installed and devices are discovered in Visibility installation, if the XCO node IP/VIP changes, those are not updated on device for receiving the statistics and syslog. | ||
| Workaround: | Change the XCO IP/VIP before discovering the devices. | ||
| Recovery: | Required to delete and add all devices again after the IP/VIP of XCO is changed. | ||
| Parent Defect ID: | XCO-4127 | Issue ID: | XCO-4127 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Ports are not listed in the port-channel creation for SLX NPB devices | ||
| Condition: | Even though the ports are not used in any other configurations, the ports are not listed in the port-channel creation. For these ports, speed is set to auto-negotiation, and ports are not connected with cable. | ||
| Workaround: | For breakout ports, make sure that cables are connected so that port speed will be updated. | ||
| Recovery: | NA | ||
| Parent Defect ID: | XCO-4128 | Issue ID: | XCO-4128 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Port-channel partial configuration are present on device for SLX NPB devices | ||
| Condition: | Port-channel configuration failed from UI, on device still the partial configuration is present. | ||
| Workaround: | Make sure that all the configuration information are correctly populated from UI so that configuration will not fail on device. | ||
| Recovery: | Login to SLX CLI and delete the given port channel and click on refresh configuration on XCO UI from device action list. | ||
| Parent Defect ID: | XCO-4129 | Issue ID: | XCO-4129 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Disable of vn-tag header strip and enabling of 802.1BR header strip fails from XCO GUI for SLX NPB | ||
| Condition: | When vn-tag header strip is enabled on an interface, disabling the vn-tag header strip and enabling the 802.1BR header strip in a single operation fails from XCO GUI. | ||
| Workaround: | Disable the vn-tag header strip in first operation (save the port update) and then edit port again for enabling 802.1BR header strip option. | ||
| Recovery: | NA | ||
| Parent Defect ID: | XCO-4146 | Issue ID: | XCO-4146 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 2.7.2 |
| Symptom: | The fabric devices continue to remain in cfg-refresh-err state after the tpvm fail over. | ||
| Condition: |
1.Fabric devices are already in cfg-refresh-err state due to LLDP Link down(LD) event. 2. Bring up the LLDP links responsible for the fabric devices to be in cfg-refresh-err state. 3. Execute the TPVM failover by 'tpvm stop' and 'tpvm start' commands during the LLDP Link up (LA) event handling caused by 2. |
||
| Recovery: |
1The user triggers LD/LA event by flapping the interface links which are the devices are in the cfg-refreshed state even though DRC wouldn't help out to recover the device to the cfg-sync state and the pending reason is "LA/LD". 1.1. "shutdown" the interface link on the physical link on Devices follow by "efa inventory device udpate --ip <device-ip>", which generates LD events 21.. "no shutdown" the interface link on the physical link on Devices follow by "efa inventory device udpate --ip <device-ip>", which generates LA events 1.3. If the pending config contains "LA" : Execute "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" on the devices which are in cfg-refresh-err /cfg-refreshed state [or] IF the pending config contains "LD,LA" : Execute "efa fabric configure --name <fabric-name>" to clean up the configuration on devices which are in cfg-refresh-err /cfg-refreshed state. [OR] 2. The user reboots the devices without maintenance mode which are the devices are in cfg-refreshed state even though DRC wouldn't help out to recover the device to the cfg-sync state. 2.1. "reload" the switches without out maintenance mode to enable 2.2. Execute "efa inventory drift-reconcile execute --ip <device-ip> --reconcile" on the devices which are in cfg-refresh-err /cfg-refreshed state. |
||
| Parent Defect ID: | XCO-4180 | Issue ID: | XCO-4180 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.0.0 |
| Symptom: | Http Login/Logout Raslogs repeatedly observed on device side, after CLI execution. | ||
| Condition: | During Ntp create/delete operation, few repeated logs are observed on device. | ||
| Workaround: |
On device side we can configure Raslog to suppress/Ignore logs. logging raslog message SEC-1206 suppress //to supress logging raslog console CRITICAL //to discard other types and show only critical |
||
| Recovery: | It is a non-functional issue and has no impact on the overall system operations. | ||
| Parent Defect ID: | XCO-5235 | Issue ID: | XCO-5235 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | High Memory utilization by litestream process | ||
| Condition: | Condition not known. | ||
| Workaround: | Not Applicable | ||
| Recovery: |
Following steps need to be followed. 1. Check for litestream process on active using ps aux | grep litestream 2. Use following command to restart. systemctl restart litestream. |
||
| Parent Defect ID: | XCO-5263 | Issue ID: | XCO-5263 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.0 |
| Symptom: | Failed to report telemetry not streamed from device | ||
| Condition: | When SLX device is discovered from XCO and statistics are getting streamed using telemetry service. Device is not sending statistics using telemetry service. | ||
| Workaround: | Select the individual device and verify the statistics are streaming from device. | ||
| Parent Defect ID: | XCO-5788 | Issue ID: | XCO-5788 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | Preparing for a fabric-wide firmware download either through CLI or the XCO GUI results in an incorrect grouping of leaf and border-leaf devices where the MCT peers are placed in the same firmware download group. | ||
| Condition: | A timing window exists where immediately performing a fabric-wide firmware download through the XCO GUI or preparing for a fabric-wide firmware download through the CLI right after adding devices to a fabric and configuring the fabric can result in an incorrect firmware download grouping of leaf and border-leaf devices. | ||
| Workaround: | If a fabric-wide firmware download is to be performed right after adding devices to and configuring the fabric, then use "efa inventory device discovery-time list --fabric <fabric name>" to poll for the completion of the fabric configuration. Every device in the fabric should have a "FabricConfigure" reason listed in order to proceed with the fabric-wide firmware download preparation and execution. | ||
| Recovery: | None | ||
| Parent Defect ID: | XCO-5795 | Issue ID: | XCO-5795 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | The data in the previous page has the ethernet interfaces as well as other interfaces even though the page is supposed to contain only the ethernet interfaces | ||
| Condition: |
Below are the steps to reproduce the issue: 1. In the XCO GUI Device Inventory view, the user selects the "Network Essentials" options from the row action menu. 2. The user navigates to page next page 2. And then comes back to the previous page |
||
| Parent Defect ID: | XCO-5931 | Issue ID: | XCO-5931 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.0.1 |
| Symptom: | Firmware Not Committed" but "Firmware Download Show Overall Status" shows "Device Update In Progress | ||
| Condition: |
For the firmware download workflow, it will perform the FWDL on each device as prescribed by the grouping and then finally do a "quick" device update (device links only) for all devices that have participated in the FWDL. The purpose of the device links only update is to ensure the fabric configurations are in-sync after the FWDL workflow has completed since devices were rebooted to activate the new firmware. In this customer case they only did a FWDL of a single device, but the workflow is the same... a device links only update will be performed at the end. The firmware download show command contains the individual device's status in the table and the "Overall Status" at the bottom reflects EFA's overall status of the FWDL workflow which includes the Device links only update. |
||
| Workaround: | The user must poll for the Overall Status Completion to proceed for another FWDL workflow prepare/execute. | ||
| Recovery: | Not applicable. | ||
| Parent Defect ID: | XCO-5990 | Issue ID: | XCO-5990 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | A detailed progress bar (with upgrade state) is not available in the Device Inventory view. | ||
| Condition: |
Below are the steps to reproduce: 1. In XCO GUI, the user opens the option for Fabric Topology view for a fabric 2. In Fabric Topology View, the user chooses the option of "Upgrade Fabric" from "Fabric Actions". 3. The "Fabric Upgrade" form is visible. The user selects an upgrade with or without the "auto-commit" option. 4. Once the user confirms the upgrade, the progress bar is visible in the "Fabric Topology" view. 5. While the firmware download is in progress the user switches to the "Device Inventory" view and searches for the device upgraded. |
||
| Parent Defect ID: | XCO-5993 | Issue ID: | XCO-5993 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | The notifications show "Devices Upgrade Ongoing" instead of "Devices Restore Ongoing" | ||
| Condition: |
Below are the steps to reproduce the issue: 1. In GUI XCO, the user opens the "Fabric Topology" view for a fabric. 2. The user selects the "Upgrade Firmware" option from the "Fabric Actions" 3. The Firmware Upgrade form is visible. The user selects the firmware upgrade of fabric with no "Auto Commit" option. 4. Once the upgrade is initiated, the Fabric Topology view shows the progress bar and state of the operation. 5. The user waits for the download to be completed and for the progress bar to show around 80% completion. Fabric Commit and Restore options will be available. 6. The user selects the Restore option |
||
| Parent Defect ID: | XCO-6054 | Issue ID: | XCO-6054 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | Once the firmware upgrade is completed, the progress bar will show around 80% completion since the user has not chosen the auto-commit option during the firmware upgrade. | ||
| Condition: |
Below are the steps to reproduce the issue: 1. In XCO GUI user navigates to the Topology view of a fabric 2. The user chooses the "Firmware Upgrade" option under "Fabric Actions". 3. Firmware Upgrade form is visible. The user chooses to perform firmware download with "Activate" and no "Auto Commit" option. 4. The user confirms the upgrade options. 5. The user will be able to see the progress of the ongoing upgrade operation. |
||
| Parent Defect ID: | XCO-6070 | Issue ID: | XCO-6070 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | A detailed progress bar status is not showing under the "Device Inventory" view but is visible only under the "Fabric Topology" view or "Fabric Device" view. | ||
| Condition: |
Below are the steps to reproduce: 1. In XCO GUI, the user opens the "Device Inventory" view. 2. The user selects devices from a fabric and clicks on the "Upgrade Firmware" option from the table action menu. 3. The "Fabric Upgrade" form is visible. The user selects an upgrade for the selected devices. 4. Once the user confirms the upgrade, a progress bar is visible in the "Device Inventory" view. 5. The user changes the page and comes back to the same page. The progress bar is not visible. 6. The user switches to the "Fabric Topology" view for the fabric of the particular devices. The progress bar is visible. |
||
| Parent Defect ID: | XCO-6172 | Issue ID: | XCO-6172 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | SLX currently doesn‘t support configuring both IPv4 and IPv6 DNS together. When both IPv4 and IPv6 DNS are configured during tpvm deployment, only one trusted peer config takes effect. | ||
| Workaround: | The best practice is to use IPV4 DNS for XCO deployment. | ||
| Parent Defect ID: | XCO-6189 | Issue ID: | XCO-6189 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | SLX currently doesn‘t support configuring both IPv4 and IPv6 trusted peers together. When both IPv4 and IPv6 trusted-peers are configured after tpvm deploy, only one trusted peer config takes effect. | ||
| Workaround: | The best practice is to use IPV4 trusted peer for XCO deployment. | ||
| Parent Defect ID: | XCO-6355 | Issue ID: | XCO-6355 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: |
When all spine devices are prepared for a firmware download in the same group, a validation error will be returned stating that the last operational spine cannot be added. This validation error can be bypassed by first adding all but one spine in the default group, then finally adding the last spine in the default group. |
||
| Workaround: |
Through CLI, prepare all devices by IP address using the force parameter. "efa inventory device firmware-download prepare add --ip <comma separated list of device IPs> --firmware-host <registered firmware-host IP address> --firmware-directory <firmware distribution path> --force". This will enable all devices in the fabric to be prepared for a simultaneous firmware-download where traffic loss is expected. |
||
| Recovery: | None | ||
| Parent Defect ID: | XCO-6360 | Issue ID: | XCO-6360 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.1 |
| Symptom: | Few Important system logs are not seen in XCO UI. | ||
| Condition: | Device is discovered from XCO and some of cards are removed/inserted in device. | ||
| Parent Defect ID: | XCO-6398 | Issue ID: | XCO-6398 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | Logs for monitor service and efa-monitor service are not available. | ||
| Condition: | If the user runs, 'efactl clean', the services do not write to logs anymore. | ||
| Workaround: |
Restart the specific services on all nodes of XCO after running 'efactl clean'. sudo systemctl restart monitor sudo systemctl restart efamonitor |
||
| Parent Defect ID: | XCO-6429 | Issue ID: | XCO-6429 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.1 |
| Symptom: | ACL hits displayed on stats table while it should maintain its position during stats update | ||
| Condition: | ACL hits dynamically keep moving around and it can't track of hits. | ||
| Workaround: | Sequence number is implemented and rest of the things will be fixed in next release. | ||
| Parent Defect ID: | EFA-16128 | Issue ID: | XCO-6466 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | EFA 3.1.1 |
| Symptom: | Full IPv4/IPv6 address are not seen for policy rules. | ||
| Condition: | When user launch troubleshoot and monitor page to select the rules. | ||
| Workaround: | Mouse over tip is provided so that user can get the complete address. | ||
| Recovery: | NA | ||
| Parent Defect ID: | XCO-6510 | Issue ID: | XCO-6510 |
|---|---|---|---|
| Product: | XCO | Reported in Release: | XCO 3.2.0 |
| Symptom: | The "Network Essentials" option is listed as a device action for the NPB device and a blank page is opened when the user clicks on that. | ||
| Condition: | NPB device is discovered in XCO and user clicks on the device action (for the NPB device) from the inventory page. | ||
| Workaround: | Don't select the networks essentials for NPB devices from device inventory page. | ||