Page Comparison

A vDiscovery job retrieves information about virtual entities in cloud environments that are managed through CMPs such as VMware, OpenStack, and AWS. You must first select a member to run the vDiscovery job. To ensure that the job is executed properly, verify the connection between the discovering member and the discovered endpoint. If you select HTTPS as the protocol for communication, you must upload either an SSL CA (Certified Authority) certificate or a self-signed SSL certificate to the Grid. For information about how to upload a certificate, see Managing Certificates.
Note that when you disable any virtual entities or interfaces on the CMP, the appliance excludes them from the vDiscovery job. In situations where the discovering member you select to perform vDiscovery jobs is disconnected from the Grid Master, the member continues to execute vDiscovery jobs based on the configured schedule. Newly discovered data replaces previously discovered data. The last set of discovered data is considered the most
up-to-date and is sent to the Grid Master when the member reconnects with the Grid Master.
When you configure vDiscovery jobs, you can enable the Infoblox NIOS appliance to automatically create DNS records for discovered IP addresses of VM instances that are served by the NIOS appliance. You can configure the appliance to add DNS records for specific DNS views associated with the network view defined for public and private IP addresses of VM instances served by the appliance. For more information about this feature, see Creating DNS Records for Newly Discovered VMs.
Before you configure and start a vDiscovery job, there are a few guidelines to consider. For more information, see
Guidelines for Configuring vDiscovery Jobs.

...

• Updatediscovereddataformanagedobjects: Select this check box if you want the appliance to update discovered data for all corresponding NIOS objects (if they exist in NIOS). If you do not select this check box, the appliance updates only the discovered data for unmanaged objects. None of the managed data will be updated. This check box is selected by default.
• ForeverynewlydiscoveredIPaddress,create: Select this check box to enable NIOS to automatically create or update DNS records for discovered network entities and VM instances (except for cloud adapters such as AWS or DDNS) if the records were originally created by vDiscovery. For more information about this feature, see Creating DNS Records for Newly Discovered VMs.
  • Host: Select this to automatically create Host records for discovered entities.
  • A&PTRRecord: Select this to automatically create A and PTR records for discovered entities. Note that the DNS zones and reverse-mapping zones to which the records belong must exist in NIOS before the vDiscovery job is executed. Otherwise, vDiscovery does not create the records.
  • TheDNSnamewillbecomputedfromtheformula: Enter the formula that NIOS uses to create the DNS records for each discovered VM address. For example, if there are two IP addresses associated with a VM, NIOS creates two DNS records, or a host record with two IP addresses, depending on your configuration. You must use the syntax of ${parameter name} for the formula.
    For AWS, OpenStack, and VMware cloud platforms, this field supports the following parameters: vm_id, vm_name, discovered_name, tenant_ID, tenant_name, subnet_id, subnet_name, network_id, network_name, vport_name, ip_address, ip_address_octet1 or 1, ip_address_octet2 or 2, ip_address_octet3 or 3, ip_address_octet4 or 4 . Note that it does not support IPv6 addresses.
    For example, when you enter ${vm_name}.corpxyz.com and the discovered vm_name = XYZ, the DNS name for this IP becomes XYZ.corpxyz.com . When you enter ${discover_name} here and the discovered name for the IP is ip-172-31-1-64.us-west-1.compute.internal, the DNS name for this IP is ip-172-31-1-64.us-west-1.compute.internal.
• Under Select the DNS view to which the DNS records are being added, select one or both of the following:

• • Use this DNS view for public IPs: Select this check box to add DNS records to a specific DNS view for public IPs. Select a DNS view from the drop-down list. If you do not select a DNS view, the DNS records are added to the default DNS view.
  • Use this DNS view for private IPs: Select this check box to add DNS records to a specific DNS view for private IPs. Select a DNS view from the drop-down list. If you do not select a DNS view, the DNS records are added to the default DNS view.

Note that the Use this DNS view for public IPs and Use this DNS view for private IPs fields will be disabled, if you select The tenant’s network view (if it does not exist, create a new one) option when you define the network views to which discovered data belongs for both public and private IP addresses, as described in Defining Network Views.

Under When discovered data is linked to managed data, select any combination of the following.

...