While adding the Big F5 LB, errors similar to 'Path Intent not found and Network Map not generated for the datasource.' are seen.

Products

• VCF Operations for Networks

Issue/Introduction

After adding the Big F5 switch as a datasource, the following error is seen : Path search and intent verification may not be available for some devices. 1 device on network map is not being processed correctly.

You might see parser related errors in the logs as below :

2025-11-28T05:16:27.893Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## inferDeviceTypes:4731 Device name: XXXXXXXX_XXXXX_##.##.#.##, Inferred device type: DT_LOAD_BALANCER
2025-11-28T05:16:27.893Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## validate:5714 Validating device XXXXXXXX_XXXXX_##.##.#.##
2025-11-28T05:16:27.893Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## validate:5779 Validating interface 0.1
2025-11-28T05:16:27.893Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## validate:5779 Validating interface 0.2
2025-11-28T05:16:27.893Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## validate:5779 Validating interface mgmt
2025-11-28T05:16:27.893Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## validate:5779 Validating interface HA
2025-11-28T05:16:27.894Z ERROR veriflow.core.Interface XXXXXXXX_XXXXX_##.##.#.## validate:1457 Aggregated interface HA with an empty member list cannot be active.
2025-11-28T05:16:27.894Z INFO veriflow.core.Device XXXXXXXX_XXXXX_##.##.#.## validate:5779 Validating interface Production
2025-11-28T05:16:27.894Z ERROR veriflow.core.Interface XXXXXXXX_XXXXX_##.##.#.## validate:1457 Aggregated interface Production with an empty member list cannot be active.
2025-11-28T05:16:27.894Z ERROR configutils.veriflow.Parser XXXXXXXX_XXXXX_##.##.#.## parse:972 Exception
java.lang.IllegalStateException: One or more device object members have not been configured correctly. Please check the logs. Aborting.

 

Environment

VCF Operations for Networks

Resolution

The F5 BIG-IP comes in either i-series or  r-series:

The F5 BIG-IP iSeries architecture, combined with vCMP (Virtual Clustered Multiprocessing), provides a high-performance, multi-tenant environment.
Similarly, the F5 BIG-IP rSeries utilizes a virtualized instance of the F5OS platform, which is deployed on a Kubernetes-based hypervisor. The F5OS platform (specifically the BIG-IP Tenant) is the next-generation equivalent of a vCMP Guest. A Tenant is a virtual machine that runs on top of the F5OS hypervisor; each Tenant is functionally equivalent to a vCMP Guest or a standard BIG-IP Virtual Edition (VE).

Because both series utilize virtualization functionality (vCMP on iSeries and F5OS Tenancy on rSeries), and because certain implementations associated with vCMP are not currently supported on VCF Operations for Networks, only specific versions of F5 switches can be added as data sources to VCF Operations for Networks.

Please refer to the list of supported data source versions that can be added to VCF Operations for Networks below: Supported Products and Versions - Broadcom TechDocs