...
Note: For new installations, an IP discovery task is automatically created by default. You can choose to disable the IP discovery after you have set up your appliance. However, you must configure and manually schedule vDiscovery jobs in order for the appliance to detect and collect information about virtual entities in the clouds. When you upgrade from a previous NIOS release to NIOS 7.2 and later, former VM Discovery tasks are divided into separate vDiscovery jobs based on the server endpoints defined in the VM Discovery tasks. All new vDiscovery jobs inherit the same discovery schedule from the old tasks. You must manually enable the new vDiscovery schedules in order for the appliance to perform vDiscovery jobs. For information about how to enable the vDiscovery schedule, see Scheduling vDiscovery Jobs .
After a discovery, the appliance updates the database with the discovered data based on the discovery configuration. For example, you can configure the appliance to merge newly discovered data, consolidate managed data, or update unmanaged data. The appliance also identifies unmanaged and conflict data after a discovery. Unmanaged data is discovered data that is not configured for DNS or DHCP and has no associated NIOS objects. Conflict data is discovered data that is configured for DNS or DHCP and has associated NIOS object or objects, but certain key values are different than those in the NIOS database. For information about guidelines the appliance uses to update discovered data, see Guidelines Before Starting a Discovery and Guidelines for Configuring vDiscovery Jobs .
NIOS 8.1NIOS Administrator Guide (Rev. A)641
IP Discovery and vDiscovery
Grid Manager displays discovered data in the Discovered Data section of the IP address properties panel when you drill down to individual IPs. For information about how to view and manage discovered data, see Viewing Discovered Data and Managing Discovered Data . The appliance records admin operations in the audit log and discovery operations in the syslog.
Figure 14.1 shows a high-level perspective of the discovery processes. You can configure and initiate an IP discovery from the Discovery Manager wizard and a vDiscovery from the vDiscovery Job wizard. You must first select a Grid member that runs the discovery tasks. After you configure an IP discovery task and a vDiscovery job, the Grid Master sends the discovery requests to the selected member. Based on the configuration of the discovery tasks, the selected member runs the discovery and collects information about discovered hosts and virtual entities from the specified networks and cloud platforms. The Grid member then reports the discovered results to the Grid Master. Based on the discovery configuration, the Grid Master updates the database with discovered data.
| Anchor | ||||
|---|---|---|---|---|
|
<place for figure>
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
You can initiate a discovery and manage discovered data based on your administrative permissions. You must have read/write permission to "Network Discovery" to initiate and manage IP discovery and vDiscovery. You must have at least read-only permission to "All Tenants" and "All Network Views" to view discovered data in the VMs (by IP Address) tab in the Cloud tab. To take actions on discovered data, such as resolving conflicts or clear unmanaged data, you must have read/write permissions. For information about how to configure admin permissions, see About Administrative Permissions .
Following are permission guidelines for initiating and controlling a discovery:
...