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
Store

Script to syncronize Node name and system name.

Hi,

We have a few thousand nodes in Orion. Some of the site routers are being upgraded by telecom operators and the naming scheme has changed slightly. This is why we now have over 300 devices where the node name doesn't match the system name (SNMP name) anymore. Could someone provide me with a short SQL script that would change the node names to match the system names?

Some routers have several addresses that need to be monitored. By browsing this forum, I have gotten the impression that it is not possible to configure several addresses for nodes. Thus we will have to add the same routers with the secondary addresses to Orion. To avoid collecting redundant SNMP statistics, we'll name the additional routers with "-secondary" suffix (e.g. office-cityx-gw and office-cityx-gw-secondary) and enable only ping polling for the secondaries. Since the nationwide router upgrade project is still under way, it is likely that there will be more changes to the SNMP names in the near future. Thus I would appreciate a suggestion on how to modify the script so that it would check if the original node name has the "-secondary" suffix and it would append it to the new node name derived from the system name. This way I could run the script again in a half an year without losing the manually added "-secondary" suffixes.

Best regards,

Marko

Find more posts tagged with

Accepted answers

All comments

FormerMember

This is something I would love to have as well, can anyone wtih scripting knowledge help?

savell

I would do this via SQL rather than a script.

Try a select first...

select caption, sysname, ip_address from nodes where sysname <> caption

If you are then sure that the update is required (and the correct updates are listed) - turn it into an update...

update nodes set caption = sysname where sysname <> caption

Make sure you have a good backup for the database - I'm really not sure if the caption field is referenced elsewhere within Solarwinds (i.e. use at own risk).

Dave.

savell

I'm not sure I understand the comment "Some routers have several addresses that need to be monitored. By browsing this forum, I have gotten the impression that it is not possible to configure several addresses for nodes"

You would normally monitor a device via the loopback address, and then select as many of the interfaces as you require to monitor (most of the interfaces will have another IP address assigned).

Perhaps I mis-understand what you are trying to achieve.

Dave.

FormerMember

I would do this via SQL rather than a script.
Try a select first...
select caption, sysname, ip_address from nodes where sysname <> caption
If you are then sure that the update is required (and the correct updates are listed) - turn it into an update...
update nodes set caption = sysname where sysname <> caption
Make sure you have a good backup for the database - I'm really not sure if the caption field is referenced elsewhere within Solarwinds (i.e. use at own risk).
Dave.

Hi Dave,

I ran this and my nodes after the polling interval are updated with the old caption, do you know why this would happen? I can confirm that DNS isn't working on these devices and the sysnames are different from the caption name.

thanks

Dave

savell

I would stop the Netperfmon service first, and then make the database update. Netperfmon may cache the names I suspect.

Dave.

mleinio

I'm not sure I understand the comment "Some routers have several addresses that need to be monitored. By browsing this forum, I have gotten the impression that it is not possible to configure several addresses for nodes"
You would normally monitor a device via the loopback address, and then select as many of the interfaces as you require to monitor (most of the interfaces will have another IP address assigned).

Dave, you are correct on this "you would normally" part.

However, in this case, the customer is not only collecting the statistics but also using NPM for network monitoring. So, the customer requires all the IP addresses configured for every router to be at least ping-monitored in NPM. That creates a situation where one device has several instances in NPM.

(The customer requirement makes sence, doesn't it? They want to ensure that all the device IP addresses are responding.)

Are there any future plans to implement such a capability to NPM that one device can have several IP addresses? So only one of them (selectable) is used to collect SNMP data but all of those are pinged?

Regards,

Markku