...
| Anchor | ||||
|---|---|---|---|---|
|
...
Before creating a vDiscovery job and performing vDiscovery in Azure, you must integrate the discovery application with Azure Active Directory (Azure AD) to provide secure sign in and authorization. To integrate the application with Azure AD, you must first register the application details with Azure AD through the Azure classic portal.
You can also register a service principal using the Azure CLI or PowerShell. If you choose to use the CLI or PowerShell, refer to the Microsoft documentation for information about the Azure authentication mechanism and how to create a service principal with Azure Resource Manager, available at https://azure.microsoft.com/en-us/documentation/articles/resource-group-authenticate-service-principal/#authe nticate-service-principal-with-password---azure-cli.
If you choose to use the Azure classic portal to register a service principal, you may still need to use the Azure CLI or PowerShell to customize the access scope for the newly created service principal. The default access scope is the subscription scope that is associated with the user who creates the service principal.
To create and integrate a vDiscovery application through the Azure classic portal:
...
After you have set up the vDiscovery application in Azure Active Directory, you must add this application as a new user to your vNIOS for Azure subscription through the Azure resource manager portal, and then define its administrative role.
To add the application as a new user and define its role:
- Go to the Microsoft Azure web site.
- Log in to your Microsoft Azure account.
- On the Microsoft Azure web site, go to your Infoblox vNIOS for Azure subscription and select All settings on the right panel.
- In the Settings panel, select Users, and then click the + Add to add new access. In the Select a role panel, click Reader.
- In the Add users panel, locate the newly created vDiscovery application. You can use the filter function to locate the application. Select the application, and then click Select to create the user. Click OK in the Add access panel to save your configuration.
- You have added the new applications as a user with the Reader role
You can now configure and perform a vDiscovery job through Grid Manager (Infoblox GUI). Ensure that you have the following information that you previously recorded in order to configure a vDiscovery job:
- Client ID = Client ID in NIOS
- Key value = Client Secret in NIOS
- Token endpoint URL = Service Endpoint in NIOS
When creating a new vDiscovery job, select Azure as the Server Type. Infoblox also recommends that you select "The tenant's network view" as the network views for both public and private IP addresses. For detailed information about vDiscovery jobs and how to configure them, refer to Configuring vDiscovery Jobs in the Infoblox NIOS Administrator Guide.
...
When you configure vDiscovery jobs, you can enable the appliance to automatically create DNS records for discovered virtual entities in your VNets. When you enable this feature, NIOS automatically adds Host records or A and PTR records to the authoritative zones for the discovered IP addresses based on your configuration. You can also enter a formula that NIOS uses to create the DNS names for the discovered IP addresses based on their VM parameters such as vm_name or discovered_name for data discovered through Azure. By doing so, NIOS is able to discover public and private IP addresses by looking up the corresponding DNS names.
Discovered data includes IP addresses for the VMs and associated information such as VM name, VM ID, tenant ID, and others. Note that corresponding zones must already exist in order for NIOS to add DNS records. Otherwise, NIOS does not add any DNS records and it logs a message to the syslog.
NIOS automatically adds DNS records (in the network views specified for vDiscovery) based on the following conditions:
- The corresponding DNS zones must already exist in the NIOS database. NIOS does not automatically create DNS zones for the records.
- To create a PTR records, the corresponding reverse-mapping zone must exist.
- A DNS zone cannot be associated with more than one DNS view. NIOS does not create DNS records for zones that are associated with multiple DNS views.
- NIOS adds new DNS records only if the VM name for the discovered IP address is available and there is no conflict between the discovered data and the associated network view.
The following matrix captures some scenarios about how vDiscovery handles various actions and what the outcome is for the information on the Cloud Platform appliance and in the NIOS database.
Note: vDiscovery modifies records that are created by the vDiscovery process only. It does not create or update DNS records that are originally created by other admin users.
...
Actions and Conditions
...
Cloud Platform Data before vDiscovery
...
Cloud Platform Data after vDiscovery
...
NIOS Data before vDiscovery
...
NIOS Data after vDiscovery
...
- Add new VM (vma) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; no DNS records
...
No data for vma
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
- Add new VM (vma) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery or admin)
...
No data for vma
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
- Add new interface to existing VM (vma) with the same discovered name on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1,
10.10.10.2)
...
- Add new interface to existing VM (vma) with the same discovered name on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
- Add new interface to existing VM (vma) with different discovered name (vmb) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vma.corp1.com 10.10.10.2
vmb.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: vmb.corp1.com (10.10.10.2)
...
- Add new interface to existing VM (vma) with different discovered name (vmb) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vma.corp1.com 10.10.10.2
vmb.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: vmb.corp1.com (10.10.10.2)
...
- Remove existing VM (vma) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com
...
No data for vma
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
...
- Remove existing VM (vma) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com
...
No data for vma
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
- Remove existing interface (10.10.10.2) from VM (vma) with different discovered name (vmb) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com 10.10.10.2
vmb.corp1.com
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: vmb.corp1.com (10.10.10.2)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
- Remove existing interface (10.10.10.2) from VM (vma) with different discovered name (vmb) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com 10.10.10.2
vmb.corp1.com
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: vmb.corp1.com (10.10.10.2)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: vmb.corp1.com (10.10.10.2)
...
- Update record name (from vma to vm1) for the existing interface (10.10.10.1) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vm1.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vm1.corp1.com (10.10.10.1)
...
- Update record name (from vma to vm1) for the existing interface (10.10.10.1) on Cloud Platform appliance
- Automatic creation of Host records
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vm1.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: vm1.corp1.com (10.10.10.1)
...
- Automatic creation of Host records
- Change FQDN template from ${discover_name) to ${vm_name}
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com vm_name: ABC
...
10.10.10.1
vm1.corp1.com vm_name: ABC
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: ABC.corp1.com (10.10.10.1)
...
- Automatic creation of Host records
- Change FQDN template from ${discover_name) to ${vm_name}
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com vm_name: ABC
...
10.10.10.1
vm1.corp1.com vm_name: ABC
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
Host record: ABC.corp1.com (10.10.10.1)
...
- Change vDiscovery task configuration from creation of Host record to A and PTR records
- In NIOS: existing zone corp1.com; existing Host record (originally created by vDiscovery)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
A record: vma.corp1.com (10.10.10.1)
...
- Change vDiscovery task configuration from creation of Host record to A and PTR records
- In NIOS: existing zone corp1.com; existing Host record (originally created by admin)
...
10.10.10.1
vma.corp1.com
...
10.10.10.1
vma.corp1.com
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
...
Zone: corp1.com
Host record: vma.corp1.com (10.10.10.1)
A record: vma.corp1.com (10.10.10.1)
...
Note: If the ${vm_name} parameter of an instance contains any special character, the appliance will not be able to identify this instance and will convert it to a managed VM using the vm_id parameter.
...
