Great to know that my VLAN changing article has helped you. I guess the power of command line & service console never seems to fade out .

Enjoy,
Eiad

I am glad that you both have found it useful.

Enjoy,
Eiad

I am sorry, but I had a bit of hard time trying to understand what you are trying to achieve. Though if what you need is to have the service console has a dedicated NIC & the VMS to have another dedicated NIC then yes its possible to do so.

One way to achieve the above would be to create two virtual switches & each use a different NIC card. You dedicate one virtual switch for Service Console & use the other one for the VM NICs. Another way to achieve the same would be to create one switch with two port groups, & dedicate a different NIC to each port group.

If you only have two NIC cards in your server, then you can connect these cards to trunk port on the switch & team them from the ESX side. That will allow you to create multiple port groups on the vSwitch with each having its own segregated vLan although all the traffic is passing on the same two NIC cards.

For your last point, its totally not clear as you will require a shared storage to achieve vMotion no matter what. Though you can always build your software iSCSI, use NAS, or use third party solution which can get the local disk on ESX server look like a shared disk to be used for VMotion.

I hope this help,
Eiad

thanks for use ful post. I need information if i have already ESX4 2 box with 3 VMs each, but networking is installed as typical, i.e. only NIC is used from both boxes, for Serv console and no VLANs defined.
If now i want to segregare the CS and VMs NICs traffic to other PHYSICAL NICs of both boxes it is posible?
Can we join 2 ESX hosts with Cross Cable to interconnect and testing Vmotion as there is no storage inside them?

BR,
Aamir