IP Fabric v6.4

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.

Upgrade Notices

• During the update process, locked snapshots will be unloaded together with other snapshots and their lock will be preserved. Therefore, such snapshots won’t be deleted by snapshot retention.

• Upgrade to 6.4 may break custom SSO integrations and will require a change to the /etc/ipf-dex.yaml file. Since the 6.3.2 release, we are omitting minor API version for SSO configuration, and only major version will need to be changed with the next major IP Fabric version. Simply replace the vX.Y string in this file with v6 and then run systemctl restart ipf-dex.

  staticClients:
    - id: ipfabric
      redirectURIs:
        - "https://demo1.eu.ipfabric.io/api/vX/auth/external/azure"
  

  For more information, please refer to the SSO documentation. If you would like assistance, please contact your Solution Architect.

v6.4.3 (GA, October 16^th, 2023)

SHA256 (ipfabric-update-6-4-3+2.tar.gz.sig) = 4480ddcf82cd59c0be28b8bb026fc1f8f4a6be149ba4fde66f16b49eabb07771
MD5 (ipfabric-update-6-4-3+2.tar.gz.sig) = 315d40eb4feac978d7ce8365b4f8dc14
SHA256 (ipfabric-6-4-3+2.qcow2) = e6851eb5575e92d3af4be71fe36e7e902ca9332f91d61370a7f46759a10a4254
MD5 (ipfabric-6-4-3+2.qcow2) = 832bd482d11c7efb23f17f5ad135e2f7
SHA256 (ipfabric-6-4-3+2.ova) = b81d3829de02ee7e79f91a83b16e94b9bd93a619141552d51e7ab098798ae191
MD5 (ipfabric-6-4-3+2.ova) = a8e6c92f419933e5a248632b51269902

For the list of delivered tickets, please consult the Low-Level Release Notes for 6.4.3.

v6.4.2

For the list of delivered tickets, please consult the Low-Level Release Notes for 6.4.2.

Experimental Features

Newly added features which need to be explicitly enabled in service files. If you are interested in trying them out, please contact our Support or Solution Architect team and we will gladly help you with enabling these features.

SUBNETS_TO_ALLOW_PROCESSING_DUPLICIT_IP

By default, IP Fabric excludes CLI jobs from the discovery process based on already discovered devices and their local interface IP addresses. If you have duplicate IP addresses in the network, then it can be worthy to whitelist some subnets.

v6.4.1

For the list of delivered tickets, please consult the Low-Level Release Notes for 6.4.1.

Bug Fixes

• Discovery process may get stuck when processing last devices in the queue. Also Remaining devices for the discovery are now being correctly removed from the queue.

v6.4.0 (September 15^th, 2023)

Not a GA

This release is available only to early adopters for testing purposes.

SHA256 (ipfabric-update-6-4-0+2.tar.gz.sig) = e649a26382020ec3256ea7a554d49256a89276f3f048adfbdc06a31fe20c747f
MD5 (ipfabric-update-6-4-0+2.tar.gz.sig) = d634c3b286fdf3c268c50b0d90be80a9
SHA256 (ipfabric-6-4-0+2.qcow2) = 50a1c62a5a2899f8ae363f7fd910d3b28cf4e5dd4e15c45dfcaa5a7ad2c72cf4
MD5 (ipfabric-6-4-0+2.qcow2) = 4088907421e099f5dee774d4fcdbd5fc
SHA256 (ipfabric-6-4-0+2.ova) = 95a3e8224dbef7749cace5ead1f1eca6a1c199d8f4e25bef2df9bd3a21362b95
MD5 (ipfabric-6-4-0+2.ova) = dc05c9c7c76013cfa8e308e9e380915b

For the list of delivered tickets, please consult the Low-Level Release Notes for 6.4.0.

GUI

• Added support for bulk actions on Vendor APIs (in both the global and snapshot-specific settings). This is useful for enabling, disabling or deleting all (or multiple) Vendor APIs at once.

  

Network Discovery

• IP Fabric
  • When the discovery process is automatically stopped due to a discovery service being restarted multiple times, the resulting snapshot will be marked as FAILED (and it will contain a The discovery process failed. Data in this snapshot is incomplete. note).
  • Discovery services tasker and worker can now use 10GB of RAM instead of 6GB.
• Palo Alto
  • PAN-OS – added support for SNMP (see our feature matrix for more details)
• AWS
  • Update the related IAM policy prior to upgrading to 6.4. Download the policy JSON file IAM-policy-IPF_6.4.json.
  • Transit Gateway routing significant update – added support for connect, peering and direct-connect-gateway attachments. Improved support for VPC and VPN attachments.
  • Initial Direct Connect support – Direct Connect Gateway with transit virtual interfaces only. E2E path-lookup over Direct Connect isn’t fully supported yet.
• New source of information for identifying neighbours
  • We now support ACI endpoint tables as a possible source of information for identifying neighbours during the discovery process. You may add/remove the ACI endpoints entry in the What information is used to identify neighbours field in Settings → Discovery & Snapshots → Discovery Settings → Discovery tasks settings.
  • We only consider devices as neighbours if their OUIs are enabled for discovery in Settings → Discovery & Snapshots → Global Configuration → OUI.

Experimental Features

Newly added features which need to be explicitly enabled in service files. If you are interested in trying them out, please contact our Support or Solution Architect team and we will gladly help you with enabling these features.

• Cisco
  • ACI – added basic support for Service Graphs
    • Service Graphs inventory added to SDN
    • supported rules can be found in Routing policies