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

Bulk Import of Nodes with their select interfaces

I have installed a fresh new version of 10.1.1 NPM. I have my old version's (10.1) db backed up. The old version has something wrong with it, BUT i can get to all the tables (most interestingly, the dbo.Nodes and dbo.Interfaces tables.)

I can easily get an Excel file that has each node listed with it's respective interfaces I need to monitor.

The interfaces were chosen at seemingly random in the sense that I can't write any rules to import these type but ignore those type etc. Network Discovery sucks in this fashion and way too many clicks and searching to do it thru there.

I have about 90 nodes with 300 interfaces to add and I do NOT want to do it again manually.

Anyone know enough SQL magic to get those nodes back into the new (blank) NPM.dbo.Nodes table? and then the associated Interfaces? Any concern about other related tables missing info? I figure I just do a rediscover or poll-now once they're all there....

I was looking to see if I could use Discovery to just point to a txt or csv file that has all the Node's IPs, community name and each Interface but I'm coming up short.

A SQL stored procedure or import is what I'm looking for. Again, both tables are blank in my new install. Just want to populate the Nodes AND correct Interfaces in. Historical data isn't needed. I can then begin polling and I'm happy.

(some wish list items; my Alerts though I didn't have a ton, and any dependencies though I didn't have a ton)

Thanks for looking! I do have some SQL resources available to me at work but their time is scarce and I'd like to have a game plan before I approach them.

-Mark

Find more posts tagged with

Accepted answers

All comments

netlogix

I haven't messed with this script but I found it while I was reading though some posts.

This work?

Does that work?

MarkatWork

Hey thanks for that link. I'm going to keep it and mull it over, however, at first glance it appears to need a predictable description on the interfaces that I want to monitor. Unfortunately, the various interfaces that I'm monitoring dont have consistent or predictable interface descriptions (the descriptions describe the various things the ports are doing).

The part that detects multiple MAC addresses I'm sure I can use in the future, but for my initial import it's not just those. Its a great way to detect Uplinks tho! But I'm not just monitoring uplinks.

If that script could be modified somehow to let me feed it a text or csv file with the node name, IP and interfaces that would work...

For example;

NODE SYSNAME IPADDR INTERFACE

Switch1 192.168.0.1 gi0/9

Switch1 192.168.0.1 gi0/49

Switch3 192.168.0.87 gi0/2

Switch3 192.168.0.87 gi0/5

Switch3 192.168.0.87 gi0/18

Switch3 192.168.0.87 gi0/51

etc etc

MarkatWork

Background:

I am gathering statistics on several switches and several interfaces on each switch. There are 3 tables involved in this. Dbo.Nodes -it contains Primary Key NodeID for each switch. Dbo.Interfaces contains Primary Key InterfaceID for each interface and foreign Key NodeID. Dbo.Pollers table has 2 lines for each node polled, and 2 lines for each interface polled. (There are 4 types of polls the system does; 2 types to interfaces and 2 types to switches). The app knows to take the NetObject in the dbo.Pollers table and infer if it is a Node or an Interface, and which Primary Key value to know what IP/MAC to actually poll. (Format is N: for node followed by the NodeID PK or I: for interface followed by the InterfaceID PK).

For each switch, the dbo.Pollers table has 2 rows of (PollerID, PollerType, NetObject). 1^st row has PollerType of Poller_CR and the NetObject is N:[NodeID] and the second row has PollerType of Poller_RT and the NetObject is still N:[NodeID]. The PollerID is a primary key but has no relationship anywhere else.

Similarly, for each interface that I monitor, that same dbo.Pollers table has 2 rows of (PollerID, PollerType, NetObject). One has a PollerType of Poller_IT and the NetObject is I:[InterfaceID] and the second row has the PollerType of Poller_IE and the same NetObject (I:[InterfaceID])

So I took the old Nodes and Interfaces tables and imported them into the new corresponding tables in the new install. I had to turn off Identity and Primary Key on the old table to be able select and copy all the data in that table and keep/include the PK. Also had to turn those off on the new table so when I pasted them in, it didn't create a new PK for each row. Then went back and restore the Identity and Primary key settings on the new table, being sure to set the seed number to the next number in the sequence.

I then added a new switch and interface thru the web GUI to see what it looked like in the tables. In the Nodes table, there were some Nulls in fields of my imported data that had values for the one that went thru the web GUI so I set those imported ones accordingly. Also set EngineID. My old install had a diff Engine ID.

So now i have all the Nodes and their respective interfaces in and tied together with their PK's and FK's. The only thing next was to create a row for each of the pollers for each of the switches and interfaces. I used excel to create those values and just pasted each into the dbo.Pollers table.

Restarted all the services for good measure and we'll wait to see if the db maintenance that occurs each night cleans out any anamolies.

I can now see data showing up on my interface charts though!

MarkatWork

Background:

Restarted all the services for good measure and we'll wait to see if the db maintenance that occurs each night cleans out any anamolies.

I can now see data showing up on my interface charts though!

netlogix

Nice! Sounds like a lot of work and brute force to get it all in there and working right! Thanks for the post too... (I'm gonna bookmark it just in case I ever need to do that)

So everything looks *ok* now?