Saucepan

User Tools

Site Tools

Trace: • forwarding • dnssec • dot_doh • ssh • best_practice • delegation • cloud_network_automation • dns_exfiltration • powershell • dns_servers
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/04/25 13:53] – [Speed of Discovery] 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 ===== ===== Latency =====
 Locate member close to the networks being discovered (<500ms RTT) 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 ===== ===== Changing Networks on Switches =====
  
Line 49: 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 =====
  
infoblox_nios/discovery_network_insight.1745589215.txt.gz · Last modified: by bstafford