Saucepan

User Tools

Site Tools

Trace: • bloxconnect • misc • discovery_vdiscovery • netbios • useful_nios • snmp • summary • rpz_feeds • multimaster_dns • decryption
infoblox_nios:discovery_vdiscovery

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
infoblox_nios:discovery_vdiscovery [2024/03/30 17:21] – [VMware] bstaffordinfoblox_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. 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]] [[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 ===== ===== Best Practice =====
infoblox_nios/discovery_vdiscovery.1711819286.txt.gz · Last modified: by bstafford