Skip to content

IP Fabric v8.0

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: 7.12.5 → 8.0.10).
  • Any version in the current major line → any newer version in the current major line (for example: 8.0 → 8.2).
  • An upgrade to 8.2 can be only performed from version 7.12.5 or newer.

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.

Known Issues

Connectivity Report — MAC Address and Vendor Values Empty

In 8.0.x, rows in Discovery → Connectivity Report display empty MAC Address and Vendor values for:

  • New discovery on any 8.0.x version.
  • Snapshots from before or during 8.0.x.
  • Upgrades from 7.12.5 — prior data is wiped and not restored by re-running discovery.

Fixed

Version 8.0.8 resolves this issue.

Invalid Proxy Settings Cause Discovery to Fail to Start

Discovery may fail to start, discovering zero devices, with the error:

Call to Discovery API failed: Invalid URL

A blank proxy URL configured via sudo ipf-cli-config -p causes this issue:

http_proxy=http://:@:/
https_proxy=http://:@:/

Workaround

Log in to IP Fabric over SSH and reconfigure the proxy:

sudo ipf-cli-config -p

Enter valid proxy details, or select direct connection to disable the proxy. Discovery runs after the proxy is configured.

Breaking Changes

PostgreSQL Upgrade to Version 17

IP Fabric 8.0 migrates the PostgreSQL database from version 15 to 17, delivering improved performance.

Recommendation

Before upgrading, run Clear DB to release the collected data. The migration temporarily duplicates the database on PostgreSQL 17 and may fail if disk utilisation exceeds 49%.

Clear DB uses a two-step confirmation: select Clear Database first, then Keep Settings. This releases the data from the database while preserving all your settings. Select Keep Settings to avoid losing your configuration.

Podman

  • As of v8.0.0, Podman replaced Docker. See Extensions for details.

Container Runtime & Subnet Change

The default container subnet also changes from 172.17.0.0/16 (Docker) to 10.88.0.0/16 (Podman), and the service is now started via:

sudo systemctl enable --now podman.socket

If 10.88.0.0/16 overlaps with your network, configure a custom subnet first — see Unable to Discover Devices in 10.88.0.0/16 Subnet.

Extensions are not migrated during upgrade

Extensions are not automatically migrated from Docker to Podman when you upgrade to v8.0.0. If you use extensions, recreate them after the upgrade. Ensure you have the original images available — either Dockerfile, tar, or tar.gz. If not, export existing extensions before the upgrade. Deploy them afterward in the UI.

# docker images
IMAGE          TAG     IMAGE ID         CREATED       SIZE
extension1     latest  9516fb7634ba     3 weeks ago   236MB
# docker save <image>:<tag> -o <image_name>-<tag>.tar
# gzip <image_name>-<tag>.tar

Download the exported images via SFTP or SCP. Then deploy the new extensions in the UI.

Force-stopping

  • As of v8.0.0, force-stopping the Topology Calculation process is temporarily unavailable
    • A fix will ship in a future release
    • As a temporary workaround, restart the ipf-api service to stop the process: systemctl restart ipf-api.service

Updater

  • The Updater service is removed from the system. Database ingestion is now part of IP Fabric API. View related logs in ipf-api service logs (see Service Logs).
  • For product architecture changes, see Architecture in IP Fabric Overview.

API: Path-Based Versioning Removed

Requests that include /v7.x in the URL path now return HTTP 410 Gone.

Migration

Remove the /v7.x segment from all API request URLs. Response payloads are unchanged and no extra headers are needed. To target a specific endpoint version, use the X-API-Version request header instead. See API Versioning for details.

v8.0.10 (September 18th, 2026; GA)

SHA256 (ipfabric-update-8-0-10+0.tar.zst.sig) = d31993d20bb19b06e468779dfe29ceef78c15eace6de560faf5fba5b205a65e0
MD5 (ipfabric-update-8-0-10+0.tar.zst.sig) = be399b22ad1da21aa6affe3eb6383016
SHA256 (ipfabric-8-0-10+0.qcow2) = 3f04f2cc6f179f3ce528a8f0ab04b827515e50d2d296487cc13d53e096a78c92
MD5 (ipfabric-8-0-10+0.qcow2) = 5e9d6b60b7896ed7f66bdb494592a914
SHA256 (ipfabric-8-0-10+0.vmdk) = 2146d428cff894f612fbaf0c860e9a4051f8549afee5d947d997dfbd51484943
MD5 (ipfabric-8-0-10+0.vmdk) = f42dfde37c6f8c78fe21d0c867c4e29f
SHA256 (ipfabric-8-0-10+0.vhdx.zst) = b0734e9969febfd7a7238c3f1f05d9b805b4bdc7222341be3defaf9c9886ca85
MD5 (ipfabric-8-0-10+0.vhdx.zst) = 6317d847027cef663e07a38e5e71da39
SHA256 (unsupported-ESXi6.7U2-ipfabric-8-0-10+0.ova) = f9173d6e54f44cd70c037f328be2a816bb99b961f03486f9fdca24398eb2622c
MD5 (unsupported-ESXi6.7U2-ipfabric-8-0-10+0.ova) = 6eb32fc410fd0078fe43dddc3ae9fc85
SHA256 (unsupported-ESXi7.0-ipfabric-8-0-10+0.ova) = 4fa5c5664492e20f0bc986d9fa04eb9c23b1de2792af3914bea74ee325d817d0
MD5 (unsupported-ESXi7.0-ipfabric-8-0-10+0.ova) = b17b22432c1a564288faf332e431d0b4
SHA256 (ESXi8.0-ipfabric-8-0-10+0.ova) = 837939d373caf15f0357e415b1ae1cc9a1f4cc50fe0a0d291163b7b33aef302f
MD5 (ESXi8.0-ipfabric-8-0-10+0.ova) = 9af4273734f648ff18744906295f4264

Bug Fixes

Path Lookup

  • Fixed path lookup incorrectly reporting DROP: Security evaluation error for valid paths.
  • Reduced redundant SQL queries in path lookup graph generation, fixing UI timeouts on large topologies.
  • Fixed Fortinet FortiGate VDOM path analysis incorrectly directing traffic to Transit instead of continuing through the VDOM link.

Discovery

  • Fixed an intermittent issue causing Azure devices to be missing from discovery.
  • Fixed non-deterministic Routing Domain attribution for edge devices in the inventory devices table.

Parsing

  • Fixed HPE Aruba 5400R switches running incorrect stacking commands, which prevented discovery of secondary stack members.
  • Fixed Extreme VOSS route parsing not matching a single space between the next hop and VRF, causing missing routes.

Tables/API

  • Fixed private-link endpoint tables always returning a null IPv6 address due to an incorrect JSON path.
  • Fixed API token creation using a different API endpoint that exposed all system roles instead of only the user’s assigned roles.

Extensions

  • Fixed inability to delete extensions via the UI after they were removed manually with the Docker CLI.

v8.0.9 (September 4th, 2026; GA)

Improvements

  • Stuck discovery doesn’t delete the snapshot when manually stopped.

Bug Fixes

  • Fixed E2E Path Lookup issues after unloading and reloading a snapshot.
  • Prevented non-admin users from deleting arbitrary API tokens.
  • Fixed Configuration Import/Export failures caused by using Manual Link.
  • Fixed Cisco ASA parsing errors in acl and nat44.
  • Fixed a getNeighborsIpv4 topology calculations that could fail with PostgreSQL error.
  • Fixed Fortinet FortiGate VDOM link path analysis that routed traffic through Transit instead of the adjacent VDOM.

v8.0.8 (August 27th, 2026; GA)

Improvements

  • Improved GCP discovery to reduce the number of errors.

Bug Fixes

  • Fixed a critical error that caused MAC Address and Vendor rows in the Connectivity Report and POST /tables/reports/discovery-tasks to display as empty.
  • Fixed Fortinet FortiGate neighbor discovery so remote Arista EOS L3 switches no longer display as endpoints or unmanaged neighbors.
  • Fixed the Discovery API stop handler, which returned HTTP 500 and marked canceled discovery jobs as status:error when the Cancel button triggered it.
  • Restarting Kafka from Support-Status page caused termination of ipf-api.
  • Fixed IGMPv2 Multicast Tree Lookup diagrams that omitted the expected RP.
  • Fixed missing discovery data caused by the RangeError: Map maximum size exceeded error.

v8.0.7 (August 19th, 2026; GA)

Improvements

  • Enabled compression for the OpenAPI document.
  • Optimized the slow PostgreSQL getCloudVnicsByIp query used to retrieve cloud vNICs by IP address.
  • Added the missing memberSN column for Meraki stacks to interface tables in the GUI and API.

Bug Fixes

  • Restored identity confirmation prompts for LDAP/SSO administrators who update a local user’s password.
  • Updated the Summary of Issues so ABUnsupportedDevice rows match the Unsupported device filter.
  • Prevented custom policies from silently inheriting built-in scope permissions for job operations.
  • Fixed discovery startup failures caused by invalid proxy settings. The failure reported Call to Discovery API failed: Invalid URL.
  • Restored GCP Endpoint Group names for VMs in the NCM Cloud Virtual Machines technology table.
  • Corrected commas in Azure network interface Public IPv4 Addresses values in the New Cloud Model.
  • Fixed partial operation of Configuration Management’s Syslog Triggered collection for Cisco devices after configuration changes and write commands.
  • Fixed device configuration collection failing with Discovery API is not reachable - body/devices/x/credentialsId must be string.
  • Restored the Stop and Cancel buttons in the Jobs menu for discovery, backup, snapshot, and device configuration collection jobs with non-empty scopes.

v8.0.6 (August 3rd, 2026; GA)

Improvements

  • Increased the body size limit for Discovery and configuration management API endpoints to handle large Discovery History requests.

Bug Fixes

  • Cisco ACI fixes:
    • Fixed E2E Path Lookup issue where the nexthop was not found for internal networks.
    • Resolved missing ACI infrastructure hop before the first hop in E2E Path Lookup between ACI Leaf and Check Point GAIA (host2gw).
  • Fixed missing devices in snapshots after discovery runs caused by absent vTaskId entries.
  • Corrected configuration download to enter enable mode before running the show running-config command.

v8.0.5 (July 30th, 2026; GA)

Improvements

  • Newly added license fields (for example, cloud licensing and AIM) now propagate via license upload and remain consumable by older product versions.

Bug Fixes

  • Resolved stuck discovery and missing data when the scanner runs, caused by setState(done) for snapshot X matched no rows — row missing, snapshot may have been evicted.
  • Resolved a Discovery API is not reachable error when using Collect device configurations in version 8.0.4.
  • Resolved a snapshot load/unload issue in version 8.0.4 that caused errors during snapshot operations. Also fixed an issue where devices in snapshots disappeared or were wiped out during load/unload.
  • Fixed Cloud Path Lookup queries that caused database deadlocks when another snapshot unloads, due to TRUNCATE requiring an EXCLUSIVE lock.
  • Cisco:
    • Prevented a multi-context firewall from stalling the rest of the discovery process.
    • Corrected a wrong Vendor API slug displayed in Cisco APIC technology tables.
    • Fixed path lookup inaccuracies in Cisco ACI environments.
    • Resolved Cisco Smart Licensing parsing issues.
  • Huawei:
    • Fixed SSH client connection failures to some versions of Huawei devices.
  • VeloCloud:
    • Resolved missing interface details for LAG1 in tasks/l2Interfaces.
    • Fixed missing next hops for subnets in tasks/routingTable.
  • Fixed ABParseError Could not validate the rule collection - "dnat": TypeError: Cannot read properties of undefined (reading 'reduce') during rule collection validation.
  • Fixed ABTaskMapResultError Cannot find BGP summary for neighbor <ip>, VRF <name>.

v8.0.4 (July 22nd, 2026; GA)

Improvements

  • Added a new SSH credentials option in Device Credentials to support SSH key authentication during discovery, for devices that have this option configured.

Technology Tables

  • Added a new SPBM (Shortest Path Bridging MAC, IEEE 802.1aq) section under Technology with two tables:
    • Services (/technology/spbm/services) – I-SID service entries distributed by IS-IS across the fabric. Includes the advertising node, backbone VLAN, bound access interfaces (SAPs), and whether each entry is locally originated or learned.
    • B-MAC Forwarding (/technology/spbm/bmac) – SPBM underlay unicast forwarding entries toward destination backbone MAC addresses (B-MACs). Includes the backbone VLAN, destination fabric node, egress interface, and path metric.
    • Initially supported on Extreme Networks VOSS and Alcatel-Lucent Enterprise AOS / OmniSwitch. See Shortest Path Bridging MAC (SPBM) for details.
  • Added two new tables under Inventory > Hosts:
    • Virtual Machines (/inventory/hosts/virtual-machines)
    • Virtual Machine Interfaces (/inventory/hosts/virtual-machines-interfaces)
    • Both are device-centric inventory tables, currently populated with VMware NSX-T data only. Available without any feature flag. They are intended to replace the existing /technology/cloud/endpoints location for VMware virtual machine data, which will no longer show VMware entries when the New Cloud Model feature flag is enabled, as those tables are moving away from a device-centric model.

Vendor Support

Extreme VOSS & Alcatel-Lucent Enterprise AOS

  • SPBM (Shortest Path Bridging MAC, IEEE 802.1aq) – Added support for collecting SPBM I-SID services and B-MAC unicast forwarding data. The data displays under Technology > SPBM. See Shortest Path Bridging MAC (SPBM) and the Feature Matrix for more details.

Cisco

D-Link

  • Extended IPv6 support for all D-Link switch families, including the DES-3000 family switches (DES-3028, DES-3052, DES-3200), DGS-1210/ME and DGS-1250.
  • Newly supported features include:
    • Managed IPv6 addresses
    • IPv6 routing table
    • Neighbor discovery

Meraki

  • Added support for MX L3 outbound firewall rules and MX L7 firewall rules, visible under Technology > Security > Zone Firewall. Note that L3 rules referencing FQDN objects are not supported. IP Fabric collects IP-based rules only.
  • Added support for Group Policy firewall rules with time scheduling (currently visible but not enforced in path lookup). Also added support for VPN-to-VPN firewall rules, visible under Technology > Security > Zone Firewall.
  • Added support for NAT rules — port forwarding, one-to-one, and one-to-many — visible under Technology > Addressing > NAT.
  • Added support for MS switch ACL rules with VLAN selector, visible under Technology > Security > ACL and reflected in path lookup results.
  • Added support for License information discovery across Meraki organizations. Licenses display under Technology > Management > Licenses and cover co-term, per-device, and subscription licensing models.

Versa

  • Interface Collection Split – A new feature flag ENABLE_VERSA_VOS_INTERFACES_SPLIT changes how the system collects interface data from Versa Director. When enabled, the single heavy interfaces?deep call is replaced by separate lightweight calls (interfaces/brief, interfaces/detail, and interfaces/dynamic-tunnels). This improves reliability on directors that struggle to return the full payload. For more information, see Feature Flags.

API Endpoint Deprecation

VM Cloud Endpoint Tables

The /technology/cloud/endpoints/virtual-machines-interfaces table is deprecated in v8.0 and marked for removal in a future major release. It previously covered AWS, Azure, GCP, and VMware NSX-T.

  • When the New Cloud Model feature flag is enabled, public cloud (AWS, Azure, GCP) network interface data is available at /technology/cloud/network-interfaces. VMware NSX-T data moves to the new /inventory/hosts/virtual-machines and /inventory/hosts/virtual-machines-interfaces inventory tables and is no longer shown under the cloud endpoints tables.
  • When the feature flag is disabled, the existing table continues to work unchanged.

Automation Concerns

Update all scripts, automations, intent rules, and reports that reference /technology/cloud/endpoints/virtual-machines-interfaces before upgrading to the release that removes it.

Experimental Features

VTY Line Transport Methods for Cisco

A new feature flag ENABLE_CISCO_LINE_VTY enables collection of operational data from Cisco IOS and IOS-XE VTY lines. When enabled, IP Fabric runs the show line vty <id> command per VTY range. This discovers permitted transport methods, such as SSH and Telnet.

Disabled by default. For more information, see Feature Flags.

New Cloud Model

A new feature flag ENABLE_NEW_CLOUD_MODEL enables the New Cloud Model (NCM). When enabled, cloud infrastructure is modeled using cloud-native constructs instead of adapted on-premises abstractions, improving the accuracy of network diagrams, path lookup, and technology tables.

Disabled by default. For more information, see Feature Flags.

JSON Schema Task Validation

A new opt-in feature flag ENABLE_JSON_SCHEMA_TASK_VALIDATION validates selected discovery task results against JSON Schema definitions from product contracts instead of legacy Joi schemas.

Disabled by default. For more information, see Feature Flags.

New Services

This release introduces two new services that support discovery:

  • discovery-api — acts as the gateway to discovery services. All discovery control runs through discovery-api.
  • Kafka — exchanges discovery artifacts with other services.

Operating System Change

  • As of 8.0.0, the appliance runs Debian 13/Trixie as its underlying operating system.