Adding static routes

Adding static routes to the BMC Discovery server is necessary only on rare occasions. Routing is configured on routing devices, therefore it should not be necessary to configure static routes on CentOS servers or clients. However, if you require this type of configuration you can store the routes in a /etc/sysconfig/network-scripts/route-interface file. Static routes should only be configured for different subnets.

For example, static routes for the eth0 interface would be stored in the file /etc/sysconfig/network-scripts/route-eth0 with a format similar to the following:

ADDRESS0=172.21.22.65
 NETMASK0=255.255.255.255
 GATEWAY0=172.21.19.68
 ADDRESS1=172.21.20.0
 NETMASK1=255.255.255.0
 GATEWAY1=172.21.19.68

In this example, two static routes are added to the IP 172.21.22.65, and network 172.21.20.0/24 to the GW GATEWAY1=172.21.19.68.

Static routing requires an equivalent interface file, which may or may not exist depending on your network configuration. If it does not exist, you must create one, even if DHCP is being used to obtain the network configuration. This config must contain NAME and DEVICE options. The following is an example of ifcfg-eth0 config file matching the example above, for an eth0 interface which obtains its network configuration from DHCP:

DEVICE="eth0"
NAME="eth0"
BOOTPROTO="dhcp"
ONBOOT="yes"


Note

These ifcfg-interface and route-interface files should have permissions 755 and belong to the root user and the root group.

For more information about configuring static routes, see the Red Hat documentation. Further, you should take into consideration the warnings regarding support of OS customization for your appliance.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*