| changing IPs in KCMS [message #123021] |
Wed, 22 July 2015 15:01  |
Michael Monnerie
Messages: 4
Registered: July 2015
Location: Korneuburg, Austria, Euro...
|
|
|
|
Seems we have a lot of problems because our IPs changed, and those are in most config files. Now I wanted to change this, but it seems too hard. I guess I'll re-install the VMs from scratch.
There really should be
1) a script to change IPs
2) a way to setup a fixed IP for an instance during initial setup
And we also want to set a fixed. manual IP before we go to production with KCMS. What is the "correct" way to setup a fixed IP for each VM? I guess during install we must ensure DHCP gives the IP we want to assign later, and where do we setup the fixed IP so your scripts are not going nuts, and will cause no problem during upgrade?
Michael Monnerie
|
|
|
|
| Re: changing IPs in KCMS [message #123106 is a reply to message #123021] |
Tue, 28 July 2015 00:44  |
nate.keegan
Messages: 46
Registered: June 2015
|
|
|
|
I have been tossing this one around as far as setting IP for a host role.
The best that I have come up with so far is to limit the scope on the DHCP server to the number of IP addresses needed in total (i.e. if you have five total Kerio Multi-Server systems then a five address pool).
Initially I thought I would be able to address this via DHCP reservation and setting/generating our own MAC to use with each VM but the script does not like that during installation when it comes time to setup networking.
For grins we converted the vmdk file over to an ISO and booted successfully on physical hardware but the installation blows up at the network addressing portion of the installation so the same mechanism seems to key on a vanilla vmnic rather than using a custom MAC or a non-vmnic interface.
I would like to see a mechanism of some sort on the Puppet server where you could specify an inventory roster of sorts:
kerio-backend1 192.168.1.10
kerio-backend2 192.168.1.11
kerio-im 192.168.1.12
etc
Our procedure right now then is if we need to recycle a host name (say kerio-backend2 needs to be rebuilt) is to remove the DHCP lease for the problem host, reset the Puppet system certificate for the problem hostname, and then use the same hostname on a fresh installtion.
This works pretty well although we had to figure it out piecemeal via trial and error.
Our setup is behind a load balancer so say 192.168.1.1 is the LB inside interface, 192.168.1.2 is the DHCP server, and then our Kerio systems start via DHCP at 192.168.1.10 and are mapped to installation order so that Puppet is 192.168.1.10 (first IP in pool), LDAP is 192.168.1.11 (second IP in pool), etc.
|
|
|
|
Members
Search
Help
Register
Login
Home
