How does Cloud Discovery handle Azure VMs with multiple NICs/IPs via a Management segment?

s-higurashi
Tera Contributor

15 hours ago

Hi Community,

I have a question regarding ServiceNow Cloud Discovery behavior for Azure VMs with multiple network interfaces.

Scenario: I am discovering Azure VMs using a MID Server. The target VMs are multi-homed and connected to two different network segments:

  1. Online Segment: For public/application traffic.

  2. Management Segment: For administrative tasks (This is where the MID Server resides).

The MID Server communicates with the target VMs exclusively through the Management Segment.

My Question: When a VM has multiple NICs and IP addresses, will Cloud Discovery be able to identify and populate all of them into the CMDB (Network Adapter [cmdb_ci_nic] and IP Address [cmdb_ci_ip_address] tables)?

Specifically, since the MID Server only has "line-of-sight" to the Management IP, I want to know if the discovery process (via Azure APIs or OS-level patterns) will still capture the details of the Online Segment NIC that it cannot directly ping.

Any insights on how ServiceNow reconciles these multiple interfaces in this specific architecture would be greatly appreciated.

Thanks in advance!

0 Helpfuls
  • 107 Views
1 REPLY 1

s-higurashi
Tera Contributor

2 hours ago

Just to add more context to my original question:

The reason I am asking about multiple NICs and IP addresses is that I want to ensure ServiceNow can correctly build dependency maps (CI relationships).

For instance, if an Application Server and a Database Server communicate over the Online Segment, I need to know if Cloud Discovery can still identify and map that relationship even though the MID Server is only connected via the Management Segment.

In short: Can ServiceNow visualize dependencies on the "Online" side based on information gathered from the "Management" side?

I would love to hear from anyone who has managed a similar multi-homed architecture. Thanks!

0 Helpfuls