IP issue after changing to new server.

[bclark94]

After changing from DA to a new DA I am having an issue with all my IP based sites not resolving in the world, but locally I am able to get the websites.

Here is what I did: I shut down the old server with a power off command, then I rebooted the new server in runlevel 3 (it was running in runlevel 4 so that startips did not cause any IP conflicts). Messed around with the license for DA and had to update a link for squirrelmail. Verfied that all services were up and running with both DA and nagios on a seperate server. Ran for about two hours with no known errors until we got 3 seperate calls about their sites not working. Checked common denomiator was that they were all IP based sites. They had 3 different ISPs( could be possible that they do hit a common wire before our noc). Had a tech that was on call to verfify that they to could not get in, he was able to get to sites on the main server but not any of the IP based sites.

I am very confused why this is happening. Any idea to help me would be apperiated.

 

[nobaloney]

You didn't give us much information.

For example, are both machines using the same IP#s, are you using a managed switch with an arp-cache, etc.

Look here for more information on what we need to help you.

Jeff

 

[bclark94]

While the data from the old server is being synced to the new server over ethernet the machines do not share their eth0 IP ( 64.212.56.9 and 64.212.59.253 ), however I do run the machine in runlevel 4 with startips turned off so that no IP conflicts occur. Both machine have the same fqdn. hosting.webhostplace.com. When I thought I had everything working I switch inittab to runlevel 3 and change the IP 64.212.59.253 -> 64.212.56.9. Shutdown the old server wait about a minute and reboot the new server. Run GetLicense.sh to update license and restart DA.

At this point of time I checked several sites to see if they were live which they seemed to be, about an 90 minutes my support team reported that we had 3 customers reporting that the no longer could get email or webpages for their site. Around two hours I shut down the new server, and boot the old server. The problem went away.

We do have a smart switch and we also use cisco routers both maintain list of MAC addresses.

 

[floyd]

Did you clear the arp? You have to clear arp in the router for sure.

 

[nobaloney]

floyd, I thought of that but I don't know how that would mean it would work first, and then stop working. Perhaps if two different servers are trying to serve the same IP#s. That's why I asked if he was using a managed switch with an arp-cache.

I keep getting stuck on the statement startips turned off; if the startips script isn't run then the server won't be answering to the IP#s for those domains.

bclark94, unless you're willing to leave the system in a non-running state long enough for one of us to check it from our own part of the world, and give us real domain name/IP# combinations, then it's not easy to help you.

Jeff

 

[floyd]

Perhaps bclark94 is local to the new server, accessing it from inside the network and not going through the router. If that is true he will see the new server without having to clear the arp on the router but people on the outside will be going through the router and the router is trying to direct them to the wrong mac address. bclark94, did it stop working for you as well? From the same place it was working previously? Did you trying pinging all the ip's from outside like from dnsstuff.com?

I am not trying to sound like a know-it-all or anything. Just throwing out and option that I know has confounded me in the past.