6.5.1

e In the Port Group Properties section, type a network label that identifies the port group that you
are creating and optionally a VLAN ID.
f Click Finish.
4 In the vSphere Distributed Switch view, migrate the VMkernel adapter for the network to a standard
switch.
a Select the vSphere Distributed Switch view, and for the distributed switch, click Manage Virtual
Adapters.
b In the Manage Virtual Adapters wizard, select the VMkernel adapter from the list and click
Migrate.
c Select the newly created or another standard switch to migrate the adapter to, and click Next.
d Enter a network label that is unique in the scope of the host and optionally a VLAN ID for the
management network, and click Next.
e Review the settings on the target standard switch and click Finish.
5 In the vSphere Web Client, configure the distributed port group for the management network with
correct settings.
6 Migrate the VMkernel adapter for the management network from the standard switch to a port on the
distributed switch by using the Add and Manage Hosts wizard.
For information about the Add and Manage Hosts wizard, see the vSphere Networking
documentation.
7 If you have moved the physical adapter from the proxy switch to the standard switch, you can
reattach it to the distributed switch again by using the Add and Manage Hosts wizard.
Alarm for Loss of Network Redundancy on a Host
An alarm reports a loss of uplink redundancy on a vSphere standard or a distributed switch for a host.
Problem
No redundant physical NICs for a host are connected to a particular standard or a distributed switch, and
the following alarm appears:
Host name or IP Network uplink redundancy lost
Cause
Only one physical NIC on the host is connected to a certain standard or a distributed switch. The
redundant physical NICs are either down or are not assigned to the switch.
For example, assume that a host in your environment has physical NICs vmnic0 and vmnic1 connected to
vSwitch0, and the physical NIC vmnic1 goes offline, leaving only vmnic0 connected to vSwitch0. As a
result, the uplink redundancy for vSwitch0 is lost on the host.
vSphere Troubleshooting
VMware, Inc. 91