VMware, Inc. 83
Chapter 3 Installing and Configuring ESX Server on Blade Servers
5 Reboot ESX Server for your changes to take effect unless you are creating a VLAN
for the service console. See “Creating a VLAN with NIC Teaming for the Service
Console” on page 83.
Creating VLANs with NIC Teaming on IBM Blade Servers
System administrators use virtual LANs, or VLANs to increase performance and
security. VLANs also improve manageability and network tuning by defining
broadcast domains without the constraint of physical location.
You can create VLANs for the service console and the virtual machines.
Creating a VLAN with NIC Teaming for the Service Console
1 Create a bond between the two NICs as described in the previous section, “Using
NIC Teaming on IBM Blade Servers” on page 82. However, do not reboot ESX
Server at this time.
2Using vi or a similar text editor, edit /etc/rc.local and add the following lines to
the end of the file, where x is the bond number you selected and y is the VLAN tag
number (from 1 to 4095). These lines allow you to use the vmxnet_console module
to give network access through the bond to the service console.
#vmxnet_console through bond<x> VLAN<y>
/etc/rc.d/init.d/network stop
rmmod vmxnet_console
insmod vmxnet_console devName=”bond<x>.<y>”
/etc/init.d/network start
mount -a
3 Configure the physical ports on your external switch (not the switch on
BladeCenter) to be trunk ports that support the VLANs IDs that you have chosen.
4 Reboot ESX Server.
Creating VLANs with NIC Teaming for Virtual Machines
1 Create a bond between the two NICs as described in “Using NIC Teaming on IBM
Blade Servers” on page 82.
2 As root, log into the VMware Management Interface and create VLANs for your
virtual machines. Refer to the ESX Server 2.5 Administration Guide at
www.vmware.com/support/ for complete instructions.
Comentarios a estos manuales