Installation guide

www.vmware.com
370
VMware ESX Server Administration Guide
insmod vmxnet_console devName=”vmnic1;vmnet_0”
The devName parameter is a comma-separated list of names of VMkernel network
adapters and virtual networks.
When you install the module, it adds the appropriate number of eth<n> devices on
the service console in the order that you list the VMkernel network adapter and virtual
network names after the devName parameter. In the example above, if the service
console already had a network adapter named eth0, when you load
vmxnet_console with vmnic1 and vmnet_0; vmnic1 is seen as eth1 on the
service console and vmnet_0 is seen as eth2.
Once the eth<n> devices are created on the service console, you can bring the
interfaces up in the normal manner. For example, if you want the service console to
use IP address 10.2.0.4 for the network accessed via the vmnic1 adapter, use the
following command:
ifconfig eth1 up 10.2.0.4
If you want an easy way to see which eth<n> devices are added by the insmod
command, you can add the tagName parameter to the insmod command, as
shown in this example:
insmod vmxnet_console devName=”vmnic1;vmnet_0”
tagName=<tag>
In this case the vmxnet_console module adds the names of each of the eth<n>
devices that it created to /var/log/messages. Each message begins with the
string <tag>.
To figure out the names of the devices that were added, use this command:
grep <tag> /var/log/messages
Starting Shared VMkernel Network Adapters and Virtual
Networks when the Service Console Boots
There are two ways you can configure the service console to start VMkernel network
adapters when the service console boots. The simpler case involves sharing a network
adapter other than eth0. Sharing eth0 is more complicated and is described later.
Continuing with the example from the previous section, you can append the
following lines to /etc/rc.d/rc.local:
insmod vmxnet_console devName=”vmnic1;vmnet_0”
ifconfig eth1 up 10.2.0.4
ifconfig eth2 up 63.93.12.47