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

How to change multiple IP's in Orion without changing hostname or custom properties

Working with an existing implementation of Orion, where devices are largely individually added/removed/updated. I have a requirement as part of a data center move, to update new IP addresses for about 320 of our devices already in Orion, without changing hostname, custom property information, or resource selection (volumes selected/interfaces/hardware health/ect). Some are SNMP, some are ICMP only. The cutover for when the devices IP addresses will change is over a 48 hour period, so manually updating 320 devices after those device IP's are updated, then manually rediscovering them isn't efficient and will take too long. Any suggestions or recommendations on how best to do an import on the IP's for these while retaining custom property details and resource selections. We are not running a regularly scheduled discovery on our devices.

Find more posts tagged with

Perl

API

Accepted answers

hilbertd21

we used the script as the basis for a simple version we were able to get to work. thanks! Doug

All comments

RichardLetts

I'd write a small perl or powershell script using the API to update the value

Here is an (untested) perl version, takes an input file of nodeid and ip addresses (note the use of ip2guid to set that as well otherwise things will not work as you expect )

#!/usr/bin/perluse SOAP::Transport::HTTP;use XML::Simple;use SW::Orion;use SW::InformationService;use strict;my $nodeid;my $ip;my $hostname = 'hostname'; # fill in a hostnamemy $username = 'username';my $password = 'password';my $endpoint = "https://$hostname:17778/SolarWinds/InformationService/OrionBasic";my $xs = XML::Simple->new();my $swis = SW::InformationService->new();$swis->outputxml('true');$swis->proxy($endpoint);$swis->proxy->http_request->authorization_basic($username, $password);while ( <> ) {   my ($nodeid, $ip) = split;   &propUpdate( $nodeid,'IPAddress', $ip);   &propUpdate( $nodeid,'IPAddressguid', &ip2guid($ip));}exit 0;############################sub propUpdate {   my $nodeID=shift;   my $prop=shift;   my $newprop=shift;   print "$nodeID, {$prop=>$newprop}\n";   my $response = $swis->Update("swis://localhost/Orion/Orion.Nodes/NodeID=$nodeID",  {$prop=>$newprop}); return if ($response eq '<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Header><log xmlns="http://schemas.solarwinds.com/2007/08/informationservice"/></s:Header><s:Body><UpdateResponse xmlns="http://schemas.solarwinds.com/2007/08/informationservice"/></s:Body></s:Envelope>');   print $response;}

/RjL

#perl #api

hilbertd21

Hi Richard!

Thanks for the guideance. I'll review this with our development team to see how this could work. The only other option I see is doing a new discovery based on a list of all the new ip addresses, which would require re-doing multiple bulk field custom property changes, and much customized individual node application component adjustments, updating Atlas, etc.

hilbertd21

we used the script as the basis for a simple version we were able to get to work. thanks! Doug