IP Fabric v8.0
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:
7.12.4→8.0.1). - Any version in the current major line → any newer version in the current
major line (for example:
8.0→8.1). - An upgrade to
8.0can be only performed from version7.12.4or 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
.
Breaking Changes
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 <iamge_name>-<tag>.tar.gz
# gzip <iamge_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-apiservice 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-apiservice logs (see Service Logs).
v8.0.1 (UNRELEASED)
.
Fixes
.
New Features
.
Improvements
.
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.
- Services (
GUI
.
Path Lookup
.
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 - VTY Line Transport Methods – Available only when you enable the specific Experimental Feature.
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
.
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. 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. See Feature Flags.
Miscellaneous
.
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.