Setting up internal IPs on SolusVM (with CentOS or RedHat)

Hey there, I ran into a bit of an oddity today, so I figured I’d post it on up here to hopefully save someone else a bit of trouble. 🙂

We’ve recently been using SolusVM internally for our dev infrastructure and have been enjoying it. I’m currently in the process of lighting up a new datacenter w/ a proper A/B network setup and hit an oddity for the SolusVM side of things.

SolusVM is pretty good about setting up just about everything you need, however not so much here. Here’s a quick way to get Internal addressing working on your CentOS Based machines.

This assumes that ETH0 is your public interface and that ETH1 is your private network interface. It’ll also bring up the bridge under the name “Xenintbr0” this is the default that SolusVM looks for.

So first off, your /etc/sysconfig/network-scripts/ifcfg-eth1 file should look like this…

DEVICE=eth1
ONBOOT=yes
BRIDGE=xenintbr0
HWADDR=00:25:90:68:E9:D1

That tells CentOS to configure ETH1 as a bridging device. Now let’s get an IP on that thing! Go ahead and create a file in /etc/sysconfig/network-scripts/ called ‘ifcfg-xenintbr0’ and populate it as follows… You should use the internal IP you want bound to this server in the configuration and your own subnet. In this case, my hardware node has an internal IP of 10.0.0.8/24.

DEVICE=xenintbr0
TYPE=Bridge
BOOTPROTO=static
ONBOOT=yes
IPADDR=10.0.0.8
NETMASK=255.255.255.0
DELAY=0

Finally, one last file… This will be /etc/sysconfig/network-scripts/route-xenintbr0

10.0.0.0/24 via 10.0.0.8 dev xenintbr0

This tells CentOS to create a route for 10.0.0.0/24 using 10.0.0.8 as the gateway.

After that, you should be able to do a ‘service network restart’ and be done! Any VMs you bring up in SolusVM and bind an internal address to should “just work”. 🙂

Add Comment

Required fields are marked *. Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.