F5 Node to Linux Server CI Mapping

The Physical CI mapping logic in Process DevOps previously looked up only Windows Server blueprints when matching F5 Node CIs to backend server CIs, leaving Linux Server-backed nodes unmatched. As a result, Physical CI Asset ID was never populated and no relationship was created for SNMP-only Linux environments. The mapping logic now includes the Linux Server blueprint alongside Windows Server, so F5 Nodes backed by Linux Servers have their Physical CI Asset ID populated and the appropriate CMDB relationship created.

Where the fix appears

The completed F5-to-Linux mapping is visible in the following locations:

Location	What changed
CMDB > F5 Node CI > Primary Details tab	Physical CI Asset ID is now populated for F5 Nodes backed by Linux Server CIs.
CMDB > F5 Node CI > Relationships tab	The relationship to the corresponding Linux Server CI is created during DevOps processing.
ViVID and Business Service Map	The F5 Node-to-Linux Server backend dependency is now visible.

Procedure

Complete the following steps after upgrading to v6.1.2 to map existing F5 Nodes to their Linux Server CIs.

1. Run Process DevOps after F5 SNMP discovery.

   Trigger the Process DevOps job after your next F5 SNMP discovery run, or wait for the next scheduled run. The fix takes effect automatically.

2. Verify the Physical CI mapping on F5 Node CIs.

   Open the affected F5 Node CI in the CMDB and confirm that the Physical CI Asset ID field is populated with the correct Linux Server CI identifier.