adding additional IP's

First off, I would not necessarily trust your hosting provider telling you that the IPs are correctly setup on their end in their network routing as I've seen far too many say that and it turn out to be a problem in the setup on their end and not on the server itself causing the problem.

With that said, there can be a great many reasons why your IPs are not working which could be caused either by the configuration on your server or by the routers at your hosting provider. It can also be not working if some other server at your hosting provider's network is using the same IPs either accidentally double assigning the IPs or if some other server user is using IPs they were not authorized to use!

The first thing to look at is the configuration on your own server and make sure the IPs do in fact appear in "WHM" and also "ifconfig" in your server's Linux configuration. Are the IPs correct? Do you have the correct netmask? A common mistake is to install the correct IP address but use the wrong netmask!

Typical netmask is 255.255.255.0 but many hosts also use other variations for their local network such as 255.255.255.254, 255.255.255.192, and so forth so you need to make certain you are using the correct netmask for your provider or your IP addresses again will not work properly.

Once the IP addresses are installed, they will not function until the network interface is restarted on your server. This can be done from the Linux shell (WHM can't always be reliable to do this) but the quickest easiest way to make 100% certain the network interface is restarted after a new IP installation is just simply reboot the server!

Apache (your web server) will not immediately recognize the IPs if you don't rebuild the Apache configuration so do not necessarily rely on whether or not you can connect to the IPs from the web to know if they are working or not. You should try to ping the IPs and see if you get any response from those IPs and that will be your first indication that the IPs are working. You could also try to access another service that doesn't require specific IP configuration such as SSH and see if you can make a connection using the new IPs verses your main server IP address.

As a side footnote mention, any firewall application such as CSF, APF, or even Iptables itself can actually interfere with connectivity of newly added IP addresses on servers so also make sure any firewall is configured correctly as well.

Hopefully the above information helps you out. If you think you need any additional help or would just like someone to take a real quick look to see what is actually going on, I'd be more than happy to give you a hand with that.

Good luck with your new IP installation situation

 

Not a problem ... I sent you a private message with details how to contact me.

In all probability, I could likely tell you in a matter of few seconds what exactly is wrong.

In any case though, following the guidelines of the items to look at in my previous message above should help you or your server management company quickly track down the source of the problem.

 

You have been waiting to get your IPs working for 8 days?

Two days ???? Wow! Didn't know anyone took that long --- should be more like 2 hours, not 2 days.

 

Per what you just said and assuming your server management company has properly fully checked everything then I refer you back again to what I said in the first paragraph of my first message about about not trusting what your hosting provider says about them setting up everything correctly on their end.

It sounds like from what you've just said that your hosting provider in fact may have not setup their end correctly after all.

Double check again the IPs and netmasks on your server against the information that your hosting provider gave you and if those do in fact match, combined with what your server management company already said, there is a very good chance that the problem is on your hosting provider's side and they probably didn't setup the routing correctly for those IP addresses in order to properly route to your server.

 

If your hosting provider continues to say the problem is not on their end and your current server management company fails to step in and handle that issue with your hosting provider on your behalf as they really should be doing, that is what you are paying them for --- then go ahead and use the email address I gave you in the private message earlier to contact me!

Upon your asking, I will verify the problem really truly on the end of the hosting provider and not some configuration item on your server itself and I will personally talk to your provider and help you get this sorted out!

Nobody it going to point fingers around me and say oh "it's not our fault, blah blah blah!" :D

EDIT: Nevermind. Just saw you already wrote me and based on the information you wrote in the email and relayed to me from your hosting provider, it sounds very much like it really is your server management company who is to blame for your IPs not working. I'm writing a reply back to you now to make it easier to understand what it is that your hosting provider was telling you in their message with regard to the incorrect network adapter being used.

 

I have the same issue with the same hosting provider, i have to restart the network for the second IP block to work /etc/init.d/network restart

 

You should not need to restart the network service if you add additional IP addresses the cPanel way, using Home » IP Functions » Add a New IP Address.

If you ever do need to restart the network service, for any reason, you also need to restart the ipaliases service. ipaliases is what cPanel uses to bind the additional IP addresses to the network interface. Additional IP addresses added using cPanel are listed in /etc/ips. They do not have entries in /etc/sysconfig/network-scripts. Use this command to restart ipaliases so the additional IP addresses will be bound:

Code:

# /scripts/restartsrv_ipaliases