Hi there,
We have a valid nagiosxi subscription and I would like to move our existing server over to a new one. How do I re license an existing licence key against a new IP address?
Cheers
Andy
relicensing
Re: relicensing
You cannot switch IP addresses after activation if you are using version 2011R1.7 or later. However, your license is good for 3 activations (intended for a production server, backup server, and testing server - but you can use them however you wish).
You may also contact our sales department for more activations and they would be happy to grant you more activations (within reason). Their email address is [email protected].
You may also contact our sales department for more activations and they would be happy to grant you more activations (within reason). Their email address is [email protected].
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: relicensing
Hello there,
Ok, so that brings up a question I am probably going to face regarding this issue... I have all of my servers in the AWS EC2 cloud and "randomly" they change their internal IP. I have the external IP set to a static EIP, so that won't change, but when I activated my NagiosXI instance, I noticed it used the internal 10.x.x.x IP, which could change at any moment (believe me, it really happens randomly). Upon the server changing its internal IP, what will happen to my production NagiosXI server? Will it ignore the fact it has a different IP than it was activated against, since it is still an activated instance? Or will it choke and I am flying blind in production at that point, until I can reactivate? Is there a way to force NagiosXI to use the public EIP, which isn't going to change?
Thanks,
-Todd
Ok, so that brings up a question I am probably going to face regarding this issue... I have all of my servers in the AWS EC2 cloud and "randomly" they change their internal IP. I have the external IP set to a static EIP, so that won't change, but when I activated my NagiosXI instance, I noticed it used the internal 10.x.x.x IP, which could change at any moment (believe me, it really happens randomly). Upon the server changing its internal IP, what will happen to my production NagiosXI server? Will it ignore the fact it has a different IP than it was activated against, since it is still an activated instance? Or will it choke and I am flying blind in production at that point, until I can reactivate? Is there a way to force NagiosXI to use the public EIP, which isn't going to change?
Thanks,
-Todd
Re: relicensing
Todd,
You will have to find a way to set up your Nagios server with a static IP address. Forget the fact that your license is good for 3 activations. Nothing will work properly if your IP changes once in a while... You won't be able to set up your agents, for instance NRPE, etc. I am not familiar with the cloud technology, but there should be a way to set a static IP for Nagios. If the IP changes, you will be asked to re-activate and you "burn out" one more activation.
You will have to find a way to set up your Nagios server with a static IP address. Forget the fact that your license is good for 3 activations. Nothing will work properly if your IP changes once in a while... You won't be able to set up your agents, for instance NRPE, etc. I am not familiar with the cloud technology, but there should be a way to set a static IP for Nagios. If the IP changes, you will be asked to re-activate and you "burn out" one more activation.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: relicensing
That's just the way cloud services work, or at least Amazon's implementation of cloud services...Randomly changing IPs.
Though, this won't affect service checks or anything like that, as I do have a static IP (aforementioned EIP = Elastic IP) for the public facing IP (50.x.x.x). The problem is that NagiosXI only sees the internally facing IP (10.x.x.x), which changes at random intervals. I have all of my checks using the static IP, but if my internal IP changes, apparently the whole system is hosed. Is there anyway to force the activation to use the external IP (or hostname) and not use the internal IP?
Thanks,
-Todd
Though, this won't affect service checks or anything like that, as I do have a static IP (aforementioned EIP = Elastic IP) for the public facing IP (50.x.x.x). The problem is that NagiosXI only sees the internally facing IP (10.x.x.x), which changes at random intervals. I have all of my checks using the static IP, but if my internal IP changes, apparently the whole system is hosed. Is there anyway to force the activation to use the external IP (or hostname) and not use the internal IP?
Thanks,
-Todd
Re: relicensing
Todd,
Just wanted to give you heads up. We are working on your problem. As soon as we find a solution for it, we will let you know.
Just wanted to give you heads up. We are working on your problem. As soon as we find a solution for it, we will let you know.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: relicensing
That is awesome to hear! Thanks for working on this. I truly look forward to a fix.
-Todd
-Todd
Re: relicensing
We'll change this in the next release (hopefully R1.9), so that an IP address change won't force re-activation.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Ethan Galstad
President
Ethan Galstad
President