functionality as virtual machines are moved between hosts (which is the reason I like
to use this log as an example). Remember that SCVMM requires hosts to have the
same logical switch available for placement during Live Migrations.
Figure 3.28 Viewing the status of logical switch deployment
The eagle-eyed reader may notice that the logical switch creation on
savdalhv20.savilltech.net (second line down from the top of Figure 3.28) shows
that it completed with information, which was not the case for the
savdalhv21.savilltech.net, which I configured second (the top line). The
information was as follows:
Information (26844)
Virtual switch (Datacenter Switch) is not highly available because the switch
is not available in host (savdalhv21.savilltech.net).
SCVMM is telling me that I deployed a logical switch to a server that is part of a
cluster, and that because the same logical switch is not available in the other node of
the cluster, it is not highly available. This is why I don’t get an information message
when adding the logical switch to the second node, because the logical switch is
available on both nodes. Figure 3.29 shows another set of logs showing that I removed
a logical switch from a host, changed the logical switch to use SET instead of LBFO
teaming, and then deployed the switch to the host. The upshot of these changes in
SCVMM is that the VM Switch on the host is deleted, the NIC team is deleted, and a
new VM Switch is deployed that now uses the NICs with SET.