F5 and NetScaler Node Physical CI Relationship

F5 Node and NetScaler Node CIs previously had no formal CMDB relationship to their underlying physical server CIs. The linkage existed only as a reference in the Primary Details tab, so the Relationships tab showed no connection and the Business Service Map was missing the dependency. The Process DevOps job now instantiates a formal Instantiate relationship after discovery, making the physical server dependency visible in both the Relationships tab and the Business Service Map.

Where the relationship appears

The new relationship is visible in the following locations:

Location	What changed
CMDB > F5 Node or NetScaler Node CI > Relationships tab	A formal Instantiate relationship to the physical server CI is now visible after Process DevOps runs.
ViVID and Business Service Map	The F5 or NetScaler node-to-physical-server dependency appears in service and dependency map views.

Procedure

Complete the following steps after upgrading to v6.1.2 to create and verify the new relationship.

1. Run the Process DevOps job after discovery.

   Trigger the Process DevOps job following your next F5 or NetScaler discovery run, or wait for the next scheduled run. Relationships are created automatically.

2. Verify the node relationships and Business Service Map.

   Confirm that the dependency is now visible:

   1. Open any affected F5 Node or NetScaler Node CI in the CMDB.

   2. Open the Relationships tab and confirm that the Instantiate relationship to the physical server CI is listed.

   3. Open the Business Service Map for an affected service and confirm that the new dependency appears.