apitsos
Verified User
Hello there,
I may need your help on the following issue...
We have a production server that works with four IPs. The first one is the server, the next two are as NS and the fourth one is completely free. These 4 IPs let say that are XXX.XXX.121.132 - XXX.XXX.121.135. The mask is 255.255.255.0 and they worked just fine for about two years!
Now we need to move on another subnet and get rid of these IPs. The new ones will be also 4 IPs and they will be XXX.XXX.122.132 - XXX.XXX.122.135. The mask for these IPs is 255.255.255.224, so they are part of a /27 block and more specifically the block is the XXX.XXX.122.128/27.
Please assume that it is about a production web server that runs several websites and we can't accept downtime. So we need to have a short period of about a week that both networks and all the IPs will be available and reponding, so we will be able to smoothly change the DNS zones of the served domains and make the switch without downtime. For this reason we had to use VLAN tagging, as this was something that could be provided by the provider anyway.
The first ones were working all these years without VLAN tagging and the port from the switch was providing them unttagged. Server was in connection via eth0, so we had eth0:1, eth0:2, eth0:3 and eth0:4. Now we changed that and we used the VLAN ID, so the configuration changed and the above settings became eth0.3:1, eth0.3:2, eth0.3:3 & eth0.3:4. Of course VLAN ID was 3 for that "old" network on XXX.XXX.121.132 - XXX.XXX.121.135.
We also prepared the new IPs, by configuring eth0.313:1, eth0.313:2, eth0.313:3 & eth0.313:4. The VLAN ID for our new block of IPs is 313.
Then we tried to reach websites by using the ability of DA http://XXX.XXX.121.132/~user, which worked perfectly for the old IPs, but not for the new ones!
I tried to add the new ones under the IP management (admin level), but I got an error message saying that the IP [FONT=verdana, arial, helvetica, sans-serif]already exists on eth0! Apart from that, the IPs were added on the table! The strange thing here is that they didn't respond on the http://XXX.XXX.122.132/~user.[/FONT]
[FONT=verdana, arial, helvetica, sans-serif]Gateways are also configured properly (different gateway for each VLAN).[/FONT]
[FONT=verdana, arial, helvetica, sans-serif]Any ideas what are we doing wrong? Also what would be the best practice here, in order to have a smooth change on the websites from the one IP to the other without downtime. Please advise.
Thanks a lot in advance for your time and the support!
Kind regards,
Angelos Pitsos[/FONT]
I may need your help on the following issue...
We have a production server that works with four IPs. The first one is the server, the next two are as NS and the fourth one is completely free. These 4 IPs let say that are XXX.XXX.121.132 - XXX.XXX.121.135. The mask is 255.255.255.0 and they worked just fine for about two years!
Now we need to move on another subnet and get rid of these IPs. The new ones will be also 4 IPs and they will be XXX.XXX.122.132 - XXX.XXX.122.135. The mask for these IPs is 255.255.255.224, so they are part of a /27 block and more specifically the block is the XXX.XXX.122.128/27.
Please assume that it is about a production web server that runs several websites and we can't accept downtime. So we need to have a short period of about a week that both networks and all the IPs will be available and reponding, so we will be able to smoothly change the DNS zones of the served domains and make the switch without downtime. For this reason we had to use VLAN tagging, as this was something that could be provided by the provider anyway.
The first ones were working all these years without VLAN tagging and the port from the switch was providing them unttagged. Server was in connection via eth0, so we had eth0:1, eth0:2, eth0:3 and eth0:4. Now we changed that and we used the VLAN ID, so the configuration changed and the above settings became eth0.3:1, eth0.3:2, eth0.3:3 & eth0.3:4. Of course VLAN ID was 3 for that "old" network on XXX.XXX.121.132 - XXX.XXX.121.135.
We also prepared the new IPs, by configuring eth0.313:1, eth0.313:2, eth0.313:3 & eth0.313:4. The VLAN ID for our new block of IPs is 313.
Then we tried to reach websites by using the ability of DA http://XXX.XXX.121.132/~user, which worked perfectly for the old IPs, but not for the new ones!
I tried to add the new ones under the IP management (admin level), but I got an error message saying that the IP [FONT=verdana, arial, helvetica, sans-serif]already exists on eth0! Apart from that, the IPs were added on the table! The strange thing here is that they didn't respond on the http://XXX.XXX.122.132/~user.[/FONT]
[FONT=verdana, arial, helvetica, sans-serif]Gateways are also configured properly (different gateway for each VLAN).[/FONT]
[FONT=verdana, arial, helvetica, sans-serif]Any ideas what are we doing wrong? Also what would be the best practice here, in order to have a smooth change on the websites from the one IP to the other without downtime. Please advise.
Thanks a lot in advance for your time and the support!
Kind regards,
Angelos Pitsos[/FONT]
