Policy based routing on RHEL

If you configure multiple network cards in your RHEL machine with more than one gateway then you can use “policy based routing” to configure the network traffic in a way where the traffic will leave the same interface where the traffic came from.

This procedure is described in this Red Hat KCS article.

I also created a Puppet module to configure policy based routing on RHEL 6 / 7. Currently this module does not handle Bond or VLAN tagged interfaces. You can find my module here.

Test and fix your Puppet code with Puppet Lint

Puppet Lint is a nice tool to check the syntax of your Puppet code. Common errors can be fixed directly with Puppet Lint. It can also be included to CI tools like Jenkins if you want to check your Puppet code during a Jenkins build job for example.

Find out more about Puppet Lint here.

Test your Puppet custom fact

If you are creating a custom fact and want to test the output of your fact then you need to perform the following command:

$ FACTERLIB=/path/to/your/fact/ facter

Satellite 6 => Configure multiple network cards with static IP’s during host provisioning on VMWare

Satellite 6 offers the possibility to provision a host with multiple network cards, however an issue is faced when using VMWare in conjuction with Satellite 6 and you want to provision multiple network interfaces with static IP addresses.

What happens is that after the provisioning of a virtual machine is complete, multiple network cards are added, but only the primary interface (which is used for PXE / DHCP during installation) is configured correctly.

I created a workaround to get this working. I described this solution in an official Red Hat KCS article which is now verified by Red Hat Engineering and published to the public. You can find this article here.