Netris 4.14.0 Release Notes (Jul/31/2026)

What’s new in Netris 4.14.0?

Netris 4.14.0 is a feature release focused on fabric flexibility and multi-tenant scale. It decouples BGP session placement from physical port topology and exposes InfiniBand fabric path visibility through the Netris API. It also extends DHCPv6 relay support to more switch platforms, extends Server Cluster provisioning, and ships a substantial set of platform bug fixes.

Note

Apache CloudStack integration. Enhancements to the Netris integration for Apache CloudStack are landing alongside 4.14.0, delivered as part of the CloudStack 4.22 codebase.

Features

  • BGP Session and Peer-Port Decoupling (Cumulus). On Cumulus, configure a BGP session on one switch while the port facing the BGP peer resides on another switch, giving you full flexibility in how BGP sessions are distributed across the fabric — independent of where peer connectivity physically lands. Works with any peer type (firewall, router, or server), and existing same-switch BGP configurations continue to work unchanged.

  • InfiniBand Fabric Topology Visibility via API (UFM Integration). Query the full InfiniBand fabric path for any bare-metal GPU server directly through the Netris API, with each switch hop identified by tier (leaf, spine, and core). List and filter servers by switch to support placement, blast-radius analysis, and maintenance planning, with UFM-sourced data and freshness indicators.

Enhancements

  • DHCPv6 Relay for V-Nets (Arista). Extends DHCPv6 relay support to Arista, so V-Nets can relay DHCPv6 requests to an external DHCPv6 server for both L2VPN and L3VPN configurations — including across VPC peering to a centralized server — completing IPv6 parity with existing IPv4 DHCP relay.

  • VLAN ID Selection for Server Clusters. Specify a VLAN ID per V-Net at Server Cluster creation instead of relying only on automatic allocation, so cluster VLANs align with an externally planned numbering scheme.

  • Per-V-Net VPC Selection in Server Clusters. Assign each V-Net in a Server Cluster to a different VPC at creation time, instead of the whole cluster mapping to a single VPC, so resources can be split across separate administrative domains within one cluster. Default single-VPC behavior is unchanged.

Bug fixes

  • Fixed unnecessary VRF creation on switches for V-Nets configured without an IP default gateway; only L2 VNI configuration is now applied.

  • Fixed the disk-space monitoring check on Arista switches.

  • Fixed the topology validation check on Arista switches.

  • Fixed BGP ECMP paths being capped at 16 on Arista switches. Now configured to platform maximum.

  • Fixed ACLs not being applied correctly on Arista switches where a trunk port reported its allowed VLANs as a range. Note: with this fix in place, some switches may now receive additional ACLs.

  • Fixed topology diagram rendering to use the inventory-profile fabric type for correct switch placement.

  • Fixed RDNSS configuration incorrectly rejecting valid IPv6 addresses.

  • Fixed bond interfaces being auto-populated for V-Net members when Automatic Link Aggregation is disabled in the inventory profile.

  • Fixed an issue where Netris would return “no V-net” to CloudStack hypervisors for recently created V-Nets, thus preventing workloads from deploying.

  • Fixed ARP and neighbor entries silently not being programmed on CloudStack hosts using EVPN/VXLAN bridges. The interface list is now re-evaluated continuously, so interfaces that appear later, or that flap, are picked up automatically.

  • Fixed the CloudStack agent creating VXLAN interfaces without the intended bridge-port settings. MAC learning is now disabled and ARP/ND neighbor suppression enabled on the VXLAN bridge port, as specified.

  • Fixed V-Net search by label returning no results.

Security fixes

No security fixes in this release.

Deprecation Notices

  • Site Mesh removed. Site Mesh is no longer supported. The Site Mesh main menu entry and the Site Mesh options in Site configuration have been removed from the controller UI, and the corresponding resources have been removed from the API and the Terraform provider. Automation and Terraform configurations that reference Site Mesh must be updated before upgrading.

  • MASQUERADE NAT action removed. The MASQUERADE action was selectable in NAT configuration but was never supported by SoftGate. It has been removed. API and Terraform configurations that specify a MASQUERADE NAT rule are now rejected and must be updated before upgrading.

References