Skip to content

IP Fabric v6.10

Unreleased Version

This is an upcoming IP Fabric version, which has not been released yet and is not available for download.

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.26.1.3).
  • Any version in the current major line → any newer version in the current major line (for example, 6.0.16.2.3).
  • The latest version in the current major line → any version in the next major line (for example, 6.2.57.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.4 (October 21st, 2024; GA)

SHA256 (ipfabric-update-6-10-4+0.tar.gz.sig) = fa6e94456a842e03a740c1b8ebae66fa26bd14d55667b0dcb732e06b925eac5b
MD5 (ipfabric-update-6-10-4+0.tar.gz.sig) = e93ed0db74f6c24fab801c1ea6f8a3da
SHA256 (ipfabric-6-10-4+0.ova) = ee5d9148b4ef8060421e37b5866bb8c411db7873e3e6ba7001a826662c1cc353
MD5 (ipfabric-6-10-4+0.ova) = 4ebd3b8329947dc46f4e5fbe66e0148d
SHA256 (ipfabric-6-10-4+0.qcow2) = 7b9809fb92feff9fb9f3bbb521e562d132d05cd0dfcfdd01c0e9cdc0b63d0347
MD5 (ipfabric-6-10-4+0.qcow2) = 01cb0fb21fc7adc6f1e58b5c03a1cf32
SHA256 (ipfabric-6-10-4+0.vmdk) = 5668857bfb46be8349e9744046be6495c00e2a6a3042598fd2c6f219e876e8c0
MD5 (ipfabric-6-10-4+0.vmdk) = f22702794e6b0ab626ff09228066da7e

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 options

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.

Authentication for 7.x upgrades

Note

If you have disabled sign-in pop-ups (i.e., the sign-in window does not appear), you can log in directly using the following URL:

https://osadmin:<password>@<IP Fabric FQDN or URL>

After successful authentication, the new upgrade interface appears, providing two options:

  1. Manually upload the upgrade file.
  2. Upgrade over the internet, if the appliance is connected.

Steps to upgrade system to 7.x

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.

Progress bar of the upgrade

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 to true.
    • Vendor API client logging was extended.
  • 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.