Installation guide

CHAPTER 11 Networking
371
Another method is to set up the files /etc/sysconfig/network-scripts/
ifcfg-eth1 and /etc/sysconfig/network-scripts/ifcfg-eth2
with the appropriate network information. And be sure the ONBOOT= line is
ONBOOT=yes. The ifcfg-eth1 file for this example would be
DEVICE=eth1
BOOTPROTO=static
BROADCAST=10.255.255.255
IPADDR=10.2.0.4
NETMASK=255.0.0.0
NETWORK=10.0.0.0
ONBOOT=yes
In this case, the lines you add to /etc/rc.d/rc.local would be:
insmod vmxnet_console devName=”vmnic1;vmnet_0”
ifup eth1
ifup eth2
Sharing the Service Console’s Network Adapter with Virtual
Machines
Caution: If you intend to share the adapter that is eth0 on the service console, be
careful as you implement the following steps. In order to configure ESX Server initially,
you need to have a network connection. Once the initial configuration is set, you
make several changes. At one point in the process, there is no network connection to
the service console, and you must work directly at the server.
When you first install and configure ESX Server, the VMkernel is not loaded, so the
service console needs to control the network adapter that is eth0. When you
configure ESX Server, assign the adapter that is eth0 to the service console.
Once you have completely configured ESX Server properly and rebooted the
machine, the VMkernel is loaded. At that point, you need to take the following steps:
1. Edit /etc/modules.conf and comment out the line that refers to alias
eth0.
If the original line is
alias eth0 e100
edit it to be
# alias eth0 e100
This disables eth0 on the service console when it boots.
2. Use the VMware Management Interface to reconfigure the server. Log in as root
and go to http://<hostname>/pcidivy, then click the Edit link for the