After a discovery, key information is collected and displayed in the following tabs: Data Management tab -> Devices -> Interfaces, Networks, IP Addresses, and Assets tabs of Grid Manager. You can view information about each discovered entity in one of these tabs. For more information, see Viewing Discovered Devices and their Properties.
A discovered entity is considered "unmanaged" if it is discovered in a network for which no information is being stored in the NIOS database. You are not able to configure unmanaged objects in NIOS. Depending on the nature of the discovered entity, you may convert certain unmanaged entities into managed objects so you can manage them through Grid Manager. When an entity is in the managed state, you can configure settings such as applying permissions to it, limiting who can modify the configurations and deployments, and when those changes can be applied. You cannot do so with unmanaged objects.
Grid Manager allows you to convert certain unmanaged devices, interfaces, networks, and assets to the following IPAM object types:

• Host record, as described in About Host Records.

• A and PTR records, as described in Managing A Records and in Managing PTR Records.

• Fixed IPv4 Address, as described in Configuring IPv4 Fixed Addresses.

• Fixed IPv6 Address, Configuring IPv6 Fixed Addresses.

When converting unmanaged entities to managed objects in NIOS, you can choose to convert them one at a time or as a group. To convert a single entity, just select a specific entity and perform the conversion. To convert multiple entities to the same IPAM object type, you can select the entities you want to manage and then perform a bulk conversion. You can also perform an automatic conversion for unmanaged entities in a network view by configuring conversion rules at the Grid level. For information about how to create conversion rules, see Configuring Automatic Conversion Rules.

For more information about how to convert unmanaged entities to managed objects, see the following sections:

• For unmanaged devices, see Converting Unmanaged Devices to Managed Devices below.

• For unmanaged interfaces, see Converting Unmanaged Interfaces to Managed Status below.

• For unmanaged networks from the Data Management -> Devices -> Networks tab, see Converting Unmanaged Networks to Managed Status below.

• For unmanaged networks from the IPAM or DHCP tab, see Converting Unmanaged Networks under IPAM to Managed Status below.

• For unmanaged IP Addresses, see Converting Unmanaged IP Addresses to Managed Status below.

• For unmanaged assets, see Converting Unmanaged Assets to Managed Status below.

• For automatic conversions using global conversion rules, see About Automatic Conversion Rules.

Converting Unmanaged Devices to Managed Devices

Device discovery allows you to define a fully managed state for any discovered routers, switches, firewalls, end hosts, and other network infrastructure devices. The process differs from converting an unmanaged network, because you can bind a discovered device to a fixed address, a PTR Record, a host record or an IPv4 reservation. Doing so offers the following benefits:

• Host Record – Infoblox hosts are data objects that contain DNS, DHCP, and IPAM data of the assigned addresses. Host objects allow you to assign multiple IPv4 and IPv6 addresses to a host. When you create a host record, you are specifying the name-to-address and address-to-name mappings for the IP address that you assign to the host. The Infoblox DNS server then uses this data to respond to DNS queries for the host. This establishes the identity of any infrastructure device or asset on the network. For more information, see About Host Records.

• A Record – An A (address) record is a DNS resource record that maps a domain name to an IP address. A records essentially tell DNS that a host exists inside a domain, as part of a forward-mapping zone. All traffic to a domain or subdomain is directed to the IP address specified by the A record. The DNS zone must exist in the Grid Manager before attempting to assign A records to devices. For more information about A records, see Managing A Records.

• PTR Record – Maps a device IP address to a host name in a reverse-mapping zone. The zone must already be defined before assigning the new PTR record object. For more information about PTR records, see Managing PTR Records.

• Fixed Address – A fixed address represents a persistent link between an IP address and one of the following: MAC address, Client identifier, or Circuit ID/remote ID in the DHCP relay agent option (option 82). Most applications in the current context are for a MAC address. You can configure fixed addresses for network devices, such as routers and printers, that do not frequently move from network to network. By creating fixed addresses for network devices, clients can reliably reach them by their domain names. Some network devices, such as web or FTP servers, can benefit from having fixed addresses for this reason. For more information about these object types, see Configuring IPv4 Fixed Addresses and Configuring IPv6 Fixed Addresses.

Each object type has its own characteristics that you may apply to specific types of discovered devices. For many infrastructure devices such as routers, or Assets such as servers, a fixed address is a likely choice.
Begin by examining the Data Management –> Devices page. The Managed column, as shown in in the following figure, can list one of three possible states for all discovered devices:

• Blank value–indicates that the device is not known to IPAM, because insufficient information is available to identify and catalog the device at the present time;

• No–Shows that the device in the Devices table is not managed under IPAM or Grid Manager, but enough information is collected and the device can be converted to the Managed state.

• Yes–The device in the table is a managed object with an IPAM object type (host, A record, PTR record or fixed address).

An Action icon shown as a gear in each row for the table) provides the quickest access to the Convert feature for unmanaged devices, as shown in the following figure. You can also click Convert in the Toolbar to select the object type.

 Unmanaged Devices That May be Converted to IPAM objects

To convert unmanaged devices to managed objects:

1. From the Data Management tab, select the Devices tab.

2. Click the Next Page and Last Page icons to locate the device you want to convert.

3. To convert a single device : Click the Action icon
   

    next to the device you want to convert (this automatically selects it), and then select Convert –> To Host, To A Record, To PTR Record, or To Fixed Address from the menu.
   To convert multiple devices (bulk conversion): Select the checkboxes of the devices you want to convert to the same IPAM object type. From the Toolbar, select Convert -> To Host, To A & PTR Record, or To Fixed Address from the menu.

4. For a single device: The respective object editor appears based on the conversion type you have selected. For example, if you select To Host, the Host editor appears. In the editor, define the required General settings for the new object. You can also define other settings you need from any of the tabs in the editor. For details about how to configure these settings, refer to the online Help in Grid Manager or see the appropriate sections in this guide.
   For bulk conversion: The respective bulk conversion wizard (such as the Convert Unmanaged IP Addresses to Host Record wizard) appears based on the conversion type you have selected.
   Note that the Network Insight creates the names of the new managed objects using the Discovered Name (FQDN) for the entities being converted. In the wizard, Grid Manager displays the IP addresses of the selected devices that are eligible for conversion in the Selected IP Addresses table. Entities that are not eligible for conversion will not be converted and will not appear in this table. 

   Based on the selected conversion type, complete the following to start a bulk conversion:

   1. To Host: You can select Enable in DNS and/or Enable in DHCP so the appliance can serve DNS and/or DHCP for the selected IP addresses in the host record. When you enable DNS, you must select a DNS zone for all entities that do not have an FQDN.

   2. To A & PTR Record: Network Insight converts the selected entities to A & PTR records simultaneously. You must select a DNS zone for all entities that do not have an FQDN.

   3. To Fixed Address: Network Insight automatically converts all selected IP addresses to fixed addresses in a bulk conversion. As with host record and A/PTR record conversions, entities without a Discovered Name are not eligible for conversions to fixed addresses.

5. In all bulk conversions, you can define extensible attributes for the selected IP addresses. After you configure the necessary settings, you can convert the discovered entities immediately or schedule the conversion by selecting Later and entering the date and time.

6. Click Save & Close to make the conversion. You can return to the managed object at any time to make further configuration changes.

In the Managed column for all converted entities, Grid Manager displays Yes to indicate their managed status. You can now manage these IPAM objects through Grid Manager.

Converting Unmanaged Interfaces to Managed Status

Interfaces that appear in the Interfaces table for a device may be converted to managed status, under specific circumstances. If an interface is bound to an IP address that is present in an IPAM network (for example, a leaf network inside a network container under IPAM), that interface can be converted to managed status.
For any device, any interface with a hotlink to IPAM may be converted. Examples are shown in the following figure. 

Device Interfaces Available for Conversion

In bookmark1443the figure above, two interfaces provide a link to their respective IPAM interface pages, and show an IPAM Type of Unmanaged. These ports may be converted to IPAM objects and managed under Grid Manager.

1. From the Data Management tab, select the Devices tab.

2. Click the Next Page and Last Page icons to locate the device through which you want to locate the interfaces to convert.

3. Click the Name link of the device.

4. Click the Interfaces tab for the chosen device. This tab lists all ports discovered on the device.

5. To convert a single interface: Click the Action icon
   

    next to the interface you want to convert (this automatically selects it), and then select Convert –> To  Host, To  A  Record, To  PTR  Record, or To  Fixed  Address from the menu.
   To convert multiple interfaces (bulk conversion): Select the checkboxes of the interfaces you want to convert. From the Toolbar, select Convert -> To  Host, To  A &  PTR  Record, or To  Fixed  Address from the menu. 

6. For a single interface: The respective object editor appears based on the conversion type you have selected. For example, if you select To  Host, the Host editor appears. In the editor, define the required General settings for the new object. You can also define other settings you need from any of the tabs in the editor. For details about how to configure these settings, refer to the online Help in Grid Manager or see the appropriate chapters in this guide.
   For bulk conversion: The respective bulk conversion wizard (such as the Convert  Unmanaged  IP  Addresses  to  Host  Record wizard) appears based on the conversion type you have selected.
   Note that the Network Insight creates the names of the new managed objects using the Discovered Name (FQDN) for the entities being converted. In the wizard, Grid Manager displays the IP addresses of the selected devices that are eligible for conversion in the Selected  IP  Addresses table. Entities that are not eligible for conversion will not be converted and will not appear in this table.

   Based on the selected conversion type, complete the following to start a bulk conversion:

   1. To Host: You can select Enable in DNS and/or Enable in DHCP so the appliance can serve DNS and/or DHCP for the selected IP addresses in the host record. When you enable DNS for the record, you must select a DNS zone for all entities that do not have an FQDN.

   2. To A & PTR Record: Network Insight converts the selected entities to A & PTR records simultaneously. You must select a DNS zone for all entities that do not have an FQDN.

   3. To Fixed Address: Network Insight automatically converts all selected IP addresses to fixed addresses in a bulk conversion. As with host record and A/PTR record conversions, entities without a Discovered Name FQDN are not eligible for conversions to fixed addresses.

7. In all bulk conversions, you can define extensible attributes for the selected IP addresses. After you have configured the necessary settings, you can convert the discovered entities immediately or schedule the conversion by selecting Later and entering the date and time.

     7. Click Save & Close to make the conversion. The interface is associated with the new IPAM object.
         In the IPAM Type column for all converted entities, Grid Manager displays Managed to indicate their managed status. You can now manage these IPAM objects through Grid Manager.

Converting Unmanaged Networks to Managed Status

On the Data Management –> Devices page, click a device name, and then open the Networks tab. You see the following types of networks based on their managed or unmanaged status:

• Unmanaged: These networks are displayed in yellow rows with the value of No in the Managed column. Shows that the network is not managed under IPAM/Grid Manager, but enough information is catalogued so that the network can be converted to managed status. You can provision these networks onto devices.

• Managed: These networks are displayed in white rows with the value of Yes in the Managed column. These networks are currently managed under IPAM, converted to an IPAM network. You can provision and de-provision managed networks.

• The so called "non-NIOS networks": These networks are displayed in grey rows with a blank value in the Managed column. Indicates that the network is discovered but available information is insufficient to identify and catalog the network in IPAM at the present time. This can be due to the following reasons:

  • The admin or operation status of the corresponding interface is "down". That is, the interface is either disconnected physically or disabled by administrator.

  • The prefix length for the network is /32 (ipv4) or /128 (ipv6). Network Insight treats this as a route to a specific device rather than a subnet, therefore it does not create such network in IPAM.

  • The route for this interface is configured incorrectly.

  • The route is learned from a remote source via BGP, OSPF and so on (i.e., indirect next hop), or come from a static route using the netmgmt protocol. Network Insight creates networks in IPAM for only direct and local routes from routing tables.

  • The network is within a VRF and the VRF is not mapped to a network view. VRF mapping is required in this case for the network to appear in IPAM. Some time after the VRF is mapped, the network turns from non-NIOS to unmanaged, or managed if the network is already present in IPAM.

Unmanaged networks listed under discovered devices present the same conversion features as networks listed under IPAM (see the following section Converting Unmanaged Networks under IPAM to Managed Status below).

Converting a network in the device context is the same as converting it at the top IPAM level. You cannot apply services or IPAM objects to IP addresses in unmanaged networks until the networks are converted to managed status. Many operations cannot be carried out on unmanaged networks, including editing, splitting, resizing, permissions changes and many other tasks.

1. From the Data Management tab, select the Devices tab.

2. Click the Next Page and Last Page icons to locate the device through which you want to locate the assets to convert.

3. Click the device name.

4. Click the Networks tab.

5. To convert a single network: Click the Action icon
   

    next to the network you want to convert to the Managed state (this automatically selects it), and then select Convert from the menu.
   To convert multiple networks (bulk conversion): Select the checkboxes of the networks you want to convert to the Managed state. From the Toolbar, select Convert from the menu.

6. The Network editor appears. In the editor, define the required General settings for the network. You can also define other settings you need from any of the tabs in the editor. For details about how to configure these settings, refer to the online Help in Grid Manager.

   Note Networks inherit discovery setting from their parent networks. Discovery will be disabled for networks that do not have a parent network.

1. If necessary, select the Disable for DHCP checkbox. When you convert a network to managed status, Grid Manager uses the discovered Router IP for the network to automatically populate the Router IP value in DHCP configurations for the selected network. Selecting this option disallows the converted network from being usable under DHCP.

2. If necessary, click the Discovery tab and click Enable Discovery to start discovery on the network after it is converted to Managed state. You can also elect not to discover the network, by leaving the checkbox clear.

   • Click Select Member to choose the Probe member through which the network may be discovered.

   • If necessary, click Override under Polling Options, and modify the device discovery polling options for the network. You can also specify Discovery Exclusions or a Discovery Blackout period.

   • A number of associated DNS and DHCP services are also available for configuration for the new IPAM network, including DHCP Forwarding, IPv4 DDNS settings, and an array of other DDI service settings for the network. None of these configurations are required in order for the network to be in Managed state, but may be required for other purposes.

     7. Click Save & Close to make the conversion.
         In the Managed column in the Networks tab, Grid Manager displays Yes for all converted entities to indicate their Managed status. You can now manage the networks through Grid Manager.

Converting Unmanaged Networks under IPAM to Managed Status

The IPAM tab lists all discovered networks as unmanaged, highlighted in yellow. Administrators cannot apply services or IPAM objects to IP addresses in unmanaged networks until the networks are converted to managed status. You can explore unmanaged networks through the IP Map and IP List views, but many operations cannot be carried out on unmanaged networks, including editing, splitting, resizing, permissions changes and other tasks.

Unmanaged networks can be converted at the IPAM main page and at the device level under Data Management –> Devices, selecting a device and opening the Networks page.  
Under IPAM, the Managed column for the Network tables can show one of two possible states for all discovered IPAM networks:

• No–Shows that the network is not managed under IPAM/Grid Manager, but enough information is catalogued that the device can be converted to Managed state. This state is required before a network can be converted to managed status.

• Yes–The network shown in the table is now Managed under IPAM, converted to an IPAM network.

You can discover the network again after it is converted, or keep discovery disabled and execute it at another time, or impose blackout periods that limit the time windows under which discovery can execute on the network. Other management benefits include the ability to enable Infoblox services to the network;

1. From the Data Management tab, select the IPAM tab.

2. To convert a single network: Click the Action icon
   

   next to the network you want to convert to the Managed state (this automatically selects it), and then select Convert from the menu.
   To convert multiple networks (bulk conversion): Select the checkboxes of the networks you want to convert to the Managed state. From the Toolbar, select Convert from the menu.
   You do not need to take further action other than Save & Close to set the network as Managed.

3. If necessary, you can select the converted network and do the following in the Network editor:

4. Select the Disable for DHCP checkbox to disallow the converted network from being usable under DHCP.

   • If necessary, click the Discovery tab and click Enable Discovery to start discovery on the network immediately after it is converted to Managed state. You can also elect not to discover the network, by leaving the checkbox clear.

   • Click Select Member to choose the Probe member through which the network may be discovered.

   • If necessary, click Override under Polling Options, and modify the device discovery polling options for the network. You can also specify Discovery Exclusions, port control settings, or a Discovery Blackout period.

   • A number of associated DNS and DHCP services are also available for configuration for the new IPAM network, including DHCP Forwarding, IPv4 DDNS settings, and an array of other DDI service settings for the network. None of these configurations are required in order for the network to be in Managed state, but may be required for other purposes.

5. The IPAM main page shows Yes as the value for the network under the Managed column. The network is now under management of IPAM and can participate in Infoblox services.

Converting Unmanaged IP Addresses to Managed Status

The principle for converting an IP address to managed status is the same for IP addresses as for interfaces. If an IP address is unmanaged but is present in IPAM, the IP can be converted to managed status.
Figure 15.6 Converting an IP Address to Managed Status

1. From the Data Management tab, select the Devices tab.

2. Click the Next Page and Last Page icons to locate the device through which you want to locate the IP address to convert.

3. Click the Name of the device.

4. Click the IP Addresses tab for the chosen device. The IP address page lists all ports discovered on the selected device.

5. To convert a single IP address : Click the Action icon
   

    next to the IP address you want to convert (this automatically selects it), and then select Convert–>To Host, To A Record, To PTR Record, or To Fixed Address from the menu.
   To convert multiple IP addresses (bulk conversion): Select the checkboxes of the IP addresses you want to convert. From the Toolbar, select Convert->To Host, To A & PTR Record, or To Fixed Address from the menu.

6. For a single IP address: The respective object editor appears based on the conversion type you have selected. For example, if you select ToHost, the Host editor appears. In the editor, define the required General settings for the new object. You can also define other settings you need from any of the tabs in the editor. For details about how to configure these settings, refer to the online Help in Grid Manager or see the appropriate chapters in this guide.
   For bulk conversion: The respective bulk conversion wizard (such as the Convert Unmanaged IP Addresses to Host Record wizard) appears based on the conversion type you have selected. 
   Note Network Insight creates the names of the new managed objects using the Discovered Name (FQDN) for the entities being converted. In the wizard, Grid Manager displays the IP addresses of the selected devices that are eligible for conversion in the Selected IP Addresses table. Entities that are not eligible for conversion will not be converted and will not appear in this table. 

   Based on the selected conversion type, complete the following to start a bulk conversion: 

   1. To Host: You can select Enable in DNS and/or Enable in DHCP so the appliance can serve DNS and/or DHCP for the selected IP addresses in the host record. When you enable DNS for the record, you must select a DNS zone for all entities that do not have an FQDN.

   2. ToA&PTRRecord: Network Insight converts the selected entities to A & PTR records simultaneously. You must select a DNS zone for all entities that do not have an FQDN.

   3. ToFixedAddress: Network Insight automatically converts all selected IP addresses to fixed addresses in a bulk conversion. As with host record and A/PTR record conversions, entities without a Discovered Name FQDN are not eligible for conversions to fixed addresses.
      In all bulk conversions, you can define extensible attributes for the selected IP addresses. After you have configured the necessary settings, you can convert the discovered entities immediately or schedule the conversion by selecting Later and entering the date and time.
      Click Save&Close to make the conversion. You can return to the managed object at any time to make further configuration changes.

      7. In the Managed column for all converted entities, Grid Manager displays Yes to indicate the Managed status. The selected IP addresses are associated with the newly converted IPAM objects. You can now manage these IPAM objects through Grid Manager.

Converting Unmanaged Assets to Managed Status

1. From the Data Management tab, select the Devices tab.

2. Click the Next Page and Last Page icons to locate the device through which you want to locate the assets to convert.

3. Click the Name of the device.

4. Click the Assets tab for the chosen device. The Assets page lists all network devices that have been detected through connections to the current device. If the device is a switch, you may see a list of end hosts and network servers in the list, along with any other network infrastructure devices that are neighboring the current device.

5. To convert a single asset: Click the Action icon
   

    next to the asset you want to convert (this automatically selects it), and then select Convert –> To Host, To A Record, To PTR Record, or To Fixed Address from the menu.
   To convert multiple assets (bulk conversion): Select the checkboxes of the assets you want to convert. From the Toolbar, select Convert -> To Host, To A & PTR Record, or To Fixed Address from the menu.

6. For a single asset: The respective object editor appears based on the conversion type you have selected. For example, if you select To Host, the Host editor appears. In the editor, define the required General settings for the new object. You can also define other settings you need from any of the tabs in the editor. For details about how to configure these settings, refer to the online Help in Grid Manager or see the appropriate chapters in this guide.
   For bulk conversion: The respective bulk conversion wizard (such as the Convert Unmanaged IP Addresses to Host Record wizard) appears based on the conversion type you have selected. 
   Note Network Insight creates the names of the new managed objects using the Discovered Name (FQDN) for the entities being converted. In the wizard, Grid Manager displays the IP addresses of the selected devices that are eligible for conversion in the Selected IP Addresses table. Entities that are not eligible for conversion will not be converted and will not appear in this table. 

   Based on the selected conversion type, complete the following to start a bulk conversion:

   1. To Host: You can select Enable in DNS and/or Enable in DHCP so the appliance can serve DNS and/or DHCP for the selected IP addresses in the host record. When you enable DNS for the record, you must select a DNS zone for all entities that do not have an FQDN.

   2. To A & PTR Record: Network Insight converts the selected entities to A & PTR records simultaneously. You must select a DNS zone for all entities that do not have an FQDN.

   3. To Fixed Address: Network Insight automatically converts all selected assets to fixed addresses in a bulk conversion. As with host record and A/PTR record conversions, entities without a Discovered Name FQDN are not eligible for conversions to fixed addresses.

In all bulk conversions, you can define extensible attributes for the selected assets. After you have configured the necessary settings, you can convert the discovered entities immediately or schedule the conversion for a later date by selecting Later and entering the date and time.

      7. Click Save & Close to make the conversion. You can return to the managed object at any time to make further configuration changes.
          In the Managed column for all converted entities, Grid Manager displays Yes to indicate the managed status. The selected assets are associated with the newly converted IPAM objects. You can now manage these IPAM objects through Grid Manager.