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

Sanity Check: Changing Main Orion Server IP,

Sanity Check here. We are planning on changing the IP of our Main Orion Polling engine. We have stood up a temporary Additional Polling Engine (APE) with an IP on the new network. Would it be possible to do the following?

1. Point all nodes to new APE

2. Add new IP into SNMP for nodes not running the agent

3. Change IP on main Orion Polling Engine

4. Force an update of the agents (We have a mix of SNMP and Windows Agents)

5. Move all nodes back to main Polling Engine

6. Shutdown APE

Anything wrong with my logic here? Did I forget anything? Any help is appreciated!

Find more posts tagged with

Accepted answers

shuth

You should just be able to change the IP of the main polling engine assuming your firewall rules, device ACLs, etc. allow the new IP address.

Stop SolarWinds services
Change the IP address of the server
Run the Configuration Wizard
OPTIONAL - Reboot the server

If you change the hostname, that's a completely different story requiring either a HA failover or editing the database.

Or run up a HA like @stevenstadel suggested.

All comments

stevenstadel

I suggest using the free temporary trial HA license to move the primary engine, this will maintain all monitoring and update all the relevant tables, and give you a clean new primary server with your new IP. This also gives you a failback if you run into any issues that have nodes hardcoded to the old IP for syslog, or an SNMP config. How to Migrate Orion to a New Server With Zero Downtime - Product Blog - Resources - THWACK - SolarWinds Community. No need for the APE with this method.

shuth

You should just be able to change the IP of the main polling engine assuming your firewall rules, device ACLs, etc. allow the new IP address.

Stop SolarWinds services
Change the IP address of the server
Run the Configuration Wizard
OPTIONAL - Reboot the server

If you change the hostname, that's a completely different story requiring either a HA failover or editing the database.

Or run up a HA like @stevenstadel suggested.

cmcdonald8811

Will the Windows Agents be updated automatically after running the Configuration Wizard? We have a mix of SNMP and Windows Agents in our environment.

shuth

I'm not sure. The agent configuration file on your monitored servers should have the hostname and IP address of the polling engine. SolarWinds devs would have to comment on how the agent initiates communication back (does it use IP only? if direct IP fails, does it try to resolve the hostname with DNS? etc)

If you've already run up the APE and sorted out firewall rules, you could go with the method in your original post.

Select every node and change polling engine (Manage Nodes -> More menu -> Change Polling Engine).
Update main server IP (and run Config Wizard)
Move all nodes back to main polling engine
Shutdown the APE and remove the polling engine from SolarWinds

Or run up the HA. In the HA scenario, the agents will be updated with the HA details so that when you failover and they cannot connect to the original server then they will connect to the HA. If you remove HA, the config files should be updated again.

Most of the hassle is firewalls and device ACLs for SNMP.

The agent configuration file is SolarWinds.Agent.Service.exe.cfg in C:\Program Files (x86)\SolarWinds\Agent\

If you wanted to test, theoretically you could pick a test server, shutdown the agent, edit the file to include the wrong IP (but correct hostname), restart the agent and see if it connects properly to the polling engine. Observe the results - does the agent connect OK back to SW and update the IP addresses? Does the node go down during these steps? etc

There's a few ways to do this and agents are finnicky. I had one client with a Main server and an APE. When DST changed, the agents on the main server were fine but all the agents on the APE stopped working until I restarted SolarWinds services...