I’ve read Ken’s article on Service Console redundancy a couple of times, When is it OK to default on your VI? As I also wrote on the VMTN Blog I really love Ken’s posts so far. They are in depth and Ken knows what he is talking about. His argument, keep it simple, make sense.
Basically, what we’ve done is to let everything default. All the adapters are active, the load balancing method is virtual switch port based and nothing is overridden by the port groups.
But I actually don’t agree with Ken on this one. I never use “virtual port id” load balancing for the Service Console and VMkernel, especially not if I combine these two port groups on one vSwitch.
Call me a control freak if you like, but I want to know which port group is using which vmnic. I always use an Active/Standby scenario for the vSwitch that holds the Service Console and VMkernel. Let me steal Ken’s excellent diagram to give you an idea what I’m talking about:
If anything goes wrong there’s full redundancy, which is a must have. The setup can be scripted in a couple of lines and if you need to troubleshoot you know exactly which physical NIC is being used for what purpose. The Service Console and the VMkernel/VMotion are just too important to be guessing where they are running in my opinion, especially in large environments. I want every server to be exactly the same, I don’t want to have the Service Console running on vmnic0 on the first server and on vmnic2 on the next. Like I said… I like to be in control, full control.
For those who want to set this up via a scripted install:
/usr/bin/vimsh -n -e “hostsvc/net/portgroup_set –nicorderpolicy-active=vmnic0 –nicorderpolicy-standby=vmnic2 vSwitch0 ‘Service Console’”
/usr/bin/vimsh -n -e “hostsvc/net/portgroup_set –nicorderpolicy-active=vmnic2 –nicorderpolicy-standby=vmnico vSwitch0 VMkernel”