Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Anyone know if IPAM discoveries are integrated with Orion?

My question is, does anyone know if when a subnet is discovered in Orion, it must also be discovered in IPAM? It seams like that's the case and if true, means that some subnets are discovered twice.

We're trying to consolidate discoveries, so if this isn't necessary, I can remove one of them.

Find more posts tagged with

Accepted answers

All comments

jm_sysadmin

They are separate, but you can use the IPAM scan to narrow the discovery for other parts of Orion if you want.

I used to have a script that sent IPs to a discovery job, but I can't find it. You could use the examples in the SDK to completely automate it. Or just use something like the SWQL below to export it from IPAM and paste it into a discovery task. I would further limit it to the subnets you care about first.

SELECT  IPI.IPAddress, N.IPAddress
FROM IPAM.IPInfo IPI
LEFT Join Orion.Nodes N ON IPI.IPAddress = N.IPAddress
WHERE IPI.IPStatusText NOT LIKE 'Available' AND N.IPAddress IS NULL

mesverrum

Piggybacking, I have had to do a lot of custom work over the years when i was consulting for clients to more tightly integrate Orion and IPAM, because natively they pretty much act like they aren't even related to eachother. Discovering an IP in IPAM has no built in capability to add that node to monitoring, and adding an ip or subnet to monitoring does not pass any data to IPAM. I understand they have to keep the products functional for cases where people don't necessarily have all the products, but if the big seller for SW is the single pane of glass and integrations then there is a LOT of room to improve IPAM by integrating it with data that already exists from other modules.

In the mean time, until they make those native features, you can accomplish a really impressive amount of integration on your own just by poking around in the db and correlating things in SQL or the API.

ttopham1

Thanks man, I was hoping to avoid that but wanted to ask at least.

tkercher

@jm_sysadmin can you please elaborate on how i can make the above use case of pushing the new IP's IPAM discovers to a discovery job? How did you set this up, where does the script run etc.?

jm_sysadmin

I basically feed the IPs that aren't in Orion already into a discovery job, which is mostly what @mesverrum put together, and some from the Samples SDK.

(+) Powershell script to use the API to discover interfaces on nodes - Orion SDK - The Orion Platform - THWACK (solarwinds.com)

More from him at his git: GitHub - Mesverrum/MyPublicWork

and from Solarwinds: OrionSDK/Samples/PowerShell at master · solarwinds/OrionSDK · GitHub

The scripts that you care about all have Discovery in the name but there is lots of good content besides that.

jm_sysadmin

I didn't answer all the things you asked, I run some of me things from the Orion server as a scheduled task today, but we are centralizing all of our schedule scripts for a bunch of things in an automation server. (We use RunDeck)