IP Fabric v6.10
Upgrade Version Policy
We support the following upgrade paths:
- The latest version in the previous major line → any version in the
current major line (for example,
5.0.2
→6.1.3
). - Any version in the current major line → any newer version in the current
major line (for example,
6.0.1
→6.2.3
). - The latest version in the current major line → any version in the
next major line (for example,
6.2.5
→7.1.3
).
Clearing Browser Cache
After upgrading IP Fabric to a newer version, you should see the Your
application has been updated and must be refreshed
dialog in the main GUI.
It is usually sufficient to just click the Refresh button.
However, in case of issues with the main GUI or if you did not see the mentioned dialog, please force refresh your browser cache.
The key combination for doing this depends on your operating system. In your browser window with your IP Fabric appliance’s URL open, use one of the following key combinations:
- Windows:
Ctrl
+F5
- macOS:
Command
+Shift
+R
- Linux:
Ctrl
+F5
This will only affect the browser cache for the IP Fabric appliance.
v6.10.7 (February 4th, 2025; GA)
SHA256 (ipfabric-update-6-10-7+0.tar.gz.sig) = a2e066672810aeb48210c8e361888e7525bd42e58436a49c4c223c03b72bc20a
MD5 (ipfabric-update-6-10-7+0.tar.gz.sig) = f3b15495664f76f29afdb89059f622a4
SHA256 (ipfabric-6-10-7+0.ova) = 2997e64716a3d518b946824ecd91954b4b80d2539b42325638d4ba2a793049ce
MD5 (ipfabric-6-10-7+0.ova) = a41c1e5bb2f4da39421307da9eaef527
SHA256 (ipfabric-6-10-7+0.qcow2) = 2cecdd26a7ef2d6e052d6ea15df593f27aa4f2bb8b8c2e284ead48b910470815
MD5 (ipfabric-6-10-7+0.qcow2) = 26e2f183f5ea7ef4af8e7c718a8e6dba
SHA256 (ipfabric-6-10-7+0.vmdk) = 4a858e0a13d3c30462ea959cd475da3b94ae0f6cec68eab19615948e2b780fab
MD5 (ipfabric-6-10-7+0.vmdk) = 02e056826dbcf9cca33d36292d02af92
- A critical vulnerability has been fixed. We strongly recommend that all customers upgrade to this version. If upgrading is not feasible, please contact our support team for assistance in applying the hotfix.
- Resolved kernel-related issues that prevented older installations from upgrading to the
7.0
release.
v6.10.6 (December 30th, 2024; GA)
- The login method for the new upgrade portal to version 7.x has been changed. Basic authentication has been replaced with a cookie-based login method.
v6.10.5 (November 27th, 2024; GA)
- Fixed issue for air-gapped environments unable to reach
callhome.ipfabric.io
service.
v6.10.4 (October 21st, 2024; GA)
New Upgrade Process
The upgrade process for the IP Fabric appliance has been updated.
Starting from version 6.10
and for later 6.x
releases, there are now two
distinct upgrade branches.
Upgrade to 6.x
Based Version
The upgrade process for version 6.10
and later remains consistent with
previous versions. You can perform the upgrade either online or by uploading the
upgrade package.
The upgrade is performed through the familiar System Update interface.
Additionally, the interface now includes a link to upgrade to versions 7.0
and
higher.
Upgrade to 7.x
Based Version
When you choose to upgrade to version 7.x
, you will be redirected to the new
upgrade service.
This service requires re-authentication with osadmin
account, even if you are
already logged in the System Administration interface.
After successful authentication, the new upgrade interface appears, providing two options:
- Manually upload the upgrade file.
- Upgrade over the internet, if the appliance is connected.
The new upgrade service operates on port 443
, so no additional firewall ports
need to be opened.
During the upgrade, the service displays the progress, and once the upgrade is complete, the appliance will reboot automatically.
Note
When both upgrades (6.x
and 7.x
) are available, it is recommended to upgrade
to the 7.x
version.
In this case, the green indicator on the appliance will show the 7.x
upgrade.
API Changes
API Endpoints Deprecation
The below API endpoints have been marked as deprecated and the intention is to
remove them in the next major version 7.0
.
/tables/interfaces/transfer-rates/*
/tables/interfaces/errors/*
except for/tables/interfaces/errors/disabled
/tables/interfaces/drops/*
Improvements
- Improvements – Cisco APIC:
- When an unsupported class is received in API response, the unsupported class
is removed in the next request. Previously, this functionality did not work
when the
returnPartialData
configuration parameter was set totrue
. - Vendor API client logging was extended.
- When an unsupported class is received in API response, the unsupported class
is removed in the next request. Previously, this functionality did not work
when the
- Versa Routing Table Processing – The processing speed of routing tables has been dramatically improved, resulting in a significant performance boost. This enhancement resolves issues where discovery process would get stuck when processing very large routing tables.