Differences

This shows you the differences between two versions of the page.

--- infoblox_nios:discovery_vdiscovery [2024/02/07 11:55] – [Network Discovery] bstafford
+++ infoblox_nios:discovery_vdiscovery [2024/04/04 09:33] (current) – bstafford
@@ Line 1: / Line 1: @@
-====== Network Discovery ======
+====== vDiscovery ======
 For NIOS vDiscovery to work with ESXi and to add DNS names to discovered objects, we need the Cloud Network Automation licence and the NIOS Grid must have the DNS zones added (even if the zones are not assigned to any appliance and even if Infoblox is not actually used for DNS). Otherwise, we just detect if the IP addresses are in use or not. We also need to create the networks in advanced. If we don't, the data doesn't get added.
@@ Line 5: / Line 5: @@
 [[https://docs.infoblox.com/space/vniosazure/37486690/Performing+vDiscovery+on+VNets|Discovery in Azure]]
+===== Performance =====
+TE-2215 with NIOS 8.6.3 (where new AWS sync engine was released) can syn thousands of zones across hundreds of different VPCs.
 ===== Best Practice =====
@@ Line 13: / Line 16: @@
 ===== VMware =====
-We can run vdiscovery against VMware VCentre
+  * You can run vDiscovery against VMware VCentre
+  * If you run vDiscovery against VMware where a VM is powered off, the powered off VM will be ignored.
+  * If you run vDiscovery against VMware where a VM does NOT have VMware Tools installed, VMware won't be aware of the VM's IP address and vDiscovery will ignore the VM with error message ''VM: <serial number> (name: <name>) has been ignored''
 ===== DNS Variables =====