Saucepan

User Tools

Site Tools

Trace: • ddns • cloud_network_automation • dog • dnssec • ecosystem • dhcp • best_practice • high_availability • deploy_nios_vm • ipv4
infoblox_nios:discovery_network_insight

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
infoblox_nios:discovery_network_insight [2025/01/20 09:15] – [Mass Network Import] bstaffordinfoblox_nios:discovery_network_insight [2025/12/10 00:39] (current) – [Best Practice] bstafford
Line 11: Line 11:
  
 A NetworkInsight appliance can be standalone. It can't do DNS or DHCP but it can gather IPAM data just like a "normal" NIOS Grid. A NetworkInsight appliance can be standalone. It can't do DNS or DHCP but it can gather IPAM data just like a "normal" NIOS Grid.
 +===== Best Practice =====
 +[[https://docs.infoblox.com/space/InfobloxDiscoveryBestPractices/16089111/Introduction|Best Practice documentation for Discovery]].
 +
 +
 +
 +"complete ping sweep" being enabled Grid wide is bad. It should only be used on /24. Don't enable at Grid level.
 +===== Latency =====
 +Locate member close to the networks being discovered (<500ms RTT)
 ===== Speed of Discovery ===== ===== Speed of Discovery =====
 In very tiny lab network, added a subnet to Palo VM and Network Insight added it to IPAM 99 minutes later. In very tiny lab network, added a subnet to Palo VM and Network Insight added it to IPAM 99 minutes later.
 +===== Device Support =====
 +For extra device support ("drivers"), get support to raise a NEWDEVICE ticket with engineering.
 +===== Changing Networks on Switches =====
 +
 +====Unmanged Networks====
 +  * If an UNMANGED network is resized on a switch (larger or smaller), it is resized and any defined objects inside the original UNMANGED network are deleted (tested with "IP Reservations").
 +  * If an UNMANAGED network is made larger on a switch, and if there is something already there (e.g. another network), NIOS will create an UNMANAGED network container. The original UNMANAGED network will be deleted (including any IP Reservations) but the MANAGED network (necessary to create the IP object) will remain as a MANAGED network (along with any IP Reservations) inside the UNMANAGED container.
 +    * >> The problem here is that IPAM no longer reflects the fact that an existing network has been resized and a manually created network that didn't exist on the network is still represented in IPAM.
 +
 +====Managed Networks====
 +  * If an empty MANAGED network is made smaller on a switch, a MANAGED container is created and an UNMANAGED network is created inside the container.
 +  * If an empty MANAGED network is made larger on a switch, an UNMANAGED network container is created and the MANAGED network is inside the container.
 +  * If a MANAGED network is made smaller on a switch and if there is an IP Reservation in the original network, the MANAGED network does not change. (regardless of whether the IP Reservation fits into the new network)
 +    * >> The problem here is that IPAM no longer reflects the fact that an existing network has been resized (made smaller).
 +
 +  * If a MANAGED network is made larger on a switch and if there is an IP Reservation in the network that is still in the network, the MANAGED network remains but will be put inside an UNMANAGED container that reflects the new network size.
 +      * >> The problem here is that IPAM no longer reflects the fact that an existing network has been resized (made larger).
 +  * If a MANAGED network is made larger on a switch, and if there is an IP Reservation that was in an adjacent network (MANAGED), NIOS will create an UNMANAGED container to represent the newly resized, larger network and also keep the original (since it is manged, it can't be resized). Any IP Reservations inside either network (original MANAGED network or adjacent MANAGED network that fall inside the new, larger network) will remain in NIOS.
 +
 +
 +
 ===== Mass Network Import ===== ===== Mass Network Import =====
 If you find a huge number of networks have been discovered, they will be unmanaged. To make them managed "en-masse", create a filter for unmanaged and then perform a IBCSV export. Use that file in CSV import DELETE mode to remove them. Then use the same file in ADD mode to add them back. Then they will be managed. If you find a huge number of networks have been discovered, they will be unmanaged. To make them managed "en-masse", create a filter for unmanaged and then perform a IBCSV export. Use that file in CSV import DELETE mode to remove them. Then use the same file in ADD mode to add them back. Then they will be managed.
Line 28: Line 57:
 When the Grid Master database reaches its maximum capacity (the maximum capacity varies based on the appliance model), the Grid Master stops updating the database and requests that the Grid member stop the discovery. When the discovering Grid member database reaches its capacity, the Grid member pauses the discovery. When the Grid Master database reaches its maximum capacity (the maximum capacity varies based on the appliance model), the Grid Master stops updating the database and requests that the Grid member stop the discovery. When the discovering Grid member database reaches its capacity, the Grid member pauses the discovery.
  
 +===== Capacity =====
 +  * P = Probe
 +  * C = Consolidator
  
 +^ Model ^ Device Limit (P) ^ Interface Limit (P) ^ Device Limit (C) ^ Interface Limit (C) ^
 +|ND-805 | 400 | 15,000 | | |
 +|ND-906 | 500 | 19,000 | | |
 +|ND-1405 | 4,000 | 110,000 | | |
 +|ND-1606 | 5,000 | 145,000 | | |
 +|ND-2205 | 8,000 | 250,000 | 16,000 | 500,000 |
 +|ND-2306 | 10,000 | 332,500 | 20,000 | 665,000 |
 +|ND-4005 | 15,000 | 700,000 | 40,000 | 2,600,000 |
 +|ND-4106 | 21,000 | 1,000,000 | 50,000 | 3,458,000 |
 ===== Convert Unmanaged to Managed ===== ===== Convert Unmanaged to Managed =====
  
Line 34: Line 75:
  
 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. 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.
 +
 +If discovered subnet (specifically subnet; not IP) is not converted to manged, then if the subnet is removed from network, it can just vanish from NIOS. I've seen it vanish in a lab and not vanish in a production network.
 +
 +If you convert a subnet to managed, if the subnet is removed, then it remains in NIOS and the "last discovered will just get older and older".
infoblox_nios/discovery_network_insight.1737364537.txt.gz · Last modified: by bstafford