http://www.yellow-bricks.com/2009/04/09/kens-view-on-service-console-redundancy-and-my-take/
Can anyone advise please on above setup on the latest version of Vmware 5.1 is is best still to seperate the management network.
I have always agreed this is best practice but its open to discusion.
We are on a trunked network and have had issue with a port group dropping on ocassion - this bound to 3 nics. teamed at switch level not port group level. Service console shares the production switch port.
However load balance did not kick in - to move over the vm's to the other 2 nics. Its as if VMware did not know the portgroup had dropped.
1. Do we need to turn on beacon probing perhaps
2. Any views on above please - option to seperate the managment network and move to vmotion network.
3. How can we investigate a dropped port group - suppose option is to move vnic 2 to its own switch and use a cross over cable and boot a vm on it.
Config -
vswitch 0
production - port groups & Management Networks - 3 nics
vswitch 1
vmoition - 2 nics
vswitch 2
Ftolerance - 1 nic
Thanks
John A
