Discovery and visibility of related IPs on different resource groups in Azure infrastructures - Adaptive Applications - BlueCat Gateway

Discovery and visibility of related IPs on different resource groups in Azure infrastructures - Adaptive Applications - BlueCat Gateway - 24.1.1

Cloud Discovery & Visibility Administration Guide

Locale

English

Product name

BlueCat Gateway

Version

24.1.1

On Azure infrastructures, CDV supports discovery and visibility across multiple Azure private endpoints (PEs) and multiple virtual machines (VMs) that have related IPs and are distributed on different resource groups.

CDV imports host records for these PEs and VMs as generic records. Within Address Manager, CDV links the PEs and VMs with their related IP addresses in the User-Defined Link (UDL) named CDV Device-IP Link.

Links between PEs/VMs and their IPs are established only after both resource groups are discovered. That is, both the group that contains the PEs/VMs, and the group that contains the Virtual Networks and their IP addresses.

Note: To make sure links between the PEs/VMs and their IP addresses are properly established, both resource groups must be discovered sequentially. When running discovery jobs, make sure the job that discovers one resource group finishes before starting the other. This includes during initial discovery, during rediscovery, when restarting CDV jobs after database migration, when restarting containers, and when importing exported jobs.

UDL example (virtual machines)

Within Address Manager, you can find the CDV Device-IP Link in the User-Defined Link Types workflow:

Within the UDL, each link between a VM device and its destination is a separate entry:

UDL example (virtual networks and private endpoints)

Within Azure, you create the following resource groups:

A virtual network group:

A private endpoint group:

Discovery or visibility of both groups creates a UDL in Address Manager: