IPAM - bulk changes

Question

Hi, everyone,

I'm looking for a way to make bulk changes in IPAM. We have 100s of locations with multiple VLANs per location. I need a way to disable all scanning (ICMP and SNMP) on all the subnets, but enable ICMP scanning on 2 VLANs per location every 7 days.

I tried using the export to .cvs, modify the subnets, and import the changes; but there is apparently a bug that won't let the import work.

Does someone have a API script that would work for this?

Thanks in advance. (Version 2026.2.0)

deverts · Answer

Thank you very much for the detailed response. The "typical" network structure is (all of this is fake, just providing an example) - I only care about scanning Management networks: (this is the supernet) 10.x.x.x.x/xx -Management (VLAN x) 10.x.1.x/25 (scan this) -AP Management (VLAN x) 10.x.1.128/25 (scan this) -Wired Access (VLAN x) 10.x.2.0/24 (don't scan this) -WiFi Access (VLAN x) 10.x.3.0/24 (don't scan this) I hadn't considered using a custom property to make this easier. Now my mind is racing with ideas. 😋 If "Management" or "AP Management" is not spelled out or is misspelled, for example, I could use a simple custom field called "scan" with a Yes/No and if "Yes" apply the scanning settings and if "No" disable scanning. hhhmmm….thinking now, thank you!

mr.castaneda · Answer

That’s a great use case, and I can see why doing this by hand would get old very quickly with that many locations.

Out of the box, IPAM lets you:

* Control the global ICMP/SNMP scan behavior under Settings > All Settings > IPAM Settings > Manage Subnet Scan Settings
* Turn scanning on or off on a per-subnet basis in the subnet properties (you’ve basically found the same knobs the UI is using already).

There isn’t a single built-in “apply this pattern to all subnets except these VLANs” button today, but what you’re asking for is a good fit for the IPAM API:

* Use the SWIS/Orion SDK to query all IPAM subnets.
* Tag or filter the two “scan-allowed” VLANs per location (for example, by name, custom property, or group).
* In a loop: * For the VLANs you do want scanned, set the subnet’s scan settings to ICMP enabled, SNMP disabled, and your desired interval.
* For everything else, flip the subnet to scanning disabled.

* Schedule that PowerShell script to run weekly so your pattern is reapplied automatically.

The knowledge base (KB) article that walks through using the SWIS API for IPAM (with examples and links to the GitHub IPAM API reference) is here:

https://support.solarwinds.com/Success_Center/IP_Address_Manager_(IPAM)/Knowledgebase_Articles/SWIS_API_to_perform_IPAM_operations

I don’t have your exact environment to test, so I don’t want to paste a “one-size-fits-all” script that might not match your naming/CP scheme, but the basic structure would be:

* One SWQL query to pull the subnets you care about
* A bit of PowerShell logic to decide “special VLAN” vs “everything else”
* One SWIS update call per subnet to toggle the scan settings

On the CSV route: since you’re hitting what looks like a bug on import, I’d also recommend opening a support case with the failing CSV and your IPAM version (2026.2.0) so the team can either get that fixed or confirm any current limitations.

If you’re open to sharing how you’re identifying those two VLANs per site (naming pattern or a custom property), folks here can help you sketch out the exact SWQL filter and PowerShell loop.