Summary:
Upgrading from previous XCO versions to 4.0.2, may prevent static BFD entries from being deleted or re-added.
Background:
When upgrading from previous versions to XCO 4.0.x, the schema update for static BFD entries will not transition properly.
Impact:
- Pre-existing BFD entries will no longer be editable.
Products Affected:
ExtremeCloud Orchestrator (XCO) Embedded TPVM
ExtremeCloud Orchestrator (XCO) Server
Software Affected:
XCO 4.0.2, 4.03, 4.04, 4.0.5
Symptoms:
- Unable to delete nor re-add BFD static route entry
- XCO health shows Green/Success throughout, no alarms, and no visible indication of database inconsistency.
Error Observed when attempting to delete:
# Delete attempt:
efa tenant vrf update --tenant "<TENANT-NAME>" --name “<VRF_NAME>" \
--operation static-route-bfd-delete \
--ipv4-static-route-bfd 192.168.0.2,10.0.0.3,10.0.0.4,300,300,3
–”? "record not found"
# Add attempt (to overwrite):
efa tenant vrf update ... --operation static-route-bfd-add ...
–”? "Static Route BFD ... already exist for device: 192.168.0.2"
Solution:
- Contact Extreme GTAC to obtain binary and for information on how to repair the tables.
- Standalone recovery binary bfd_recovery.tar.gz bash script:
- Is idempotent safe to run multiple times; it exits with "nothing to do" if already applied.
- Has no service impact, no XCO restart required; the SLX-OS datapath is unaffected.
- Creates an audit log at /tmp/xco_bfd_recovery_<timestamp>/.
- Take an XCO database backup: efa system backup
- Transfer binary to TPVM active node (via secure transfer from Extreme Networks):
cd /apps/efadata/
tar -xvzf bfd_recovery.tar.gz
chmod +x bfd_recovery
./bfd_recovery
Caution: Run on the TPVM active node only. Take an XCO database backup before executing.
- Corrected in XCO 4.1.0 where the upgrade process will correctly set "dest_prefix = '' for migrated rows and set the proper column default during schema migration.
Please see the full Field Notice here for more details and future updates.
