adjusting our architecture
Posted: Wed Mar 02, 2016 11:56 am
We have been running core for a while now, and recently purchased XI. I have set up a box (hostname nagtest) and given it an IP in order to test migration from core to xi. Due to some of the advanced configs I had implemented in core, the import didn't go as smoothly as I'd hoped, and it took about two weeks to get everything up and running with service dependencies, host and service groups, etc working as expected. So now we have a machine that looks like it will soon be ready to go prod and take over officially for our old core box.
The issue is I activated nagtest in order to access some items like bulk importing and such. On registering, I see that we cannot change the IP. While that throws off my plan a bit in terms of architecture, I can adjust my plans. This leads to my questions:
* Are there any issues with changing the hostname? When this becomes the prod XI box, leaving the hostname as nagtest would be confusing.
* Are there any issues with bringing up a second box to test upgrades and additional components?
The issue is I activated nagtest in order to access some items like bulk importing and such. On registering, I see that we cannot change the IP. While that throws off my plan a bit in terms of architecture, I can adjust my plans. This leads to my questions:
* Are there any issues with changing the hostname? When this becomes the prod XI box, leaving the hostname as nagtest would be confusing.
* Are there any issues with bringing up a second box to test upgrades and additional components?