Virtual Switch

[mydxbtester]

I had just installed Hyper-V role to my new Server 2012 R2, had configured/added virtual switch but I can still see both existing LOM1 and Virtual switch on connections. I should be able to see only vEthernet (Virtual Switch) but I see both so I am not able to use the interface to my new virtual machines.

 

How can I get this sorted out? To be able to see only the vEthernet virtual interface with the IP address of my current LOM1 in it?

 

Edited January 24, 2016 by mydxbtester

[rich_tech]

What type of port is the one specified as LOM ?

I googled and it seems to be a lights out management port from a quick google, if its only for remote management, you may have difficulty using it for any proper networking purposes.

 

From my experiences with Hyper-V if its a normal ethernet port, when you create the virtual switch, it just takes over and the previous port hides away, the fact that hasn't happened may point to issues with the original network card.

[mydxbtester]

LOM (NIC) is what it's named on my server. It's where my Ethernet cable is connected to our Gigabit switch.

From my previous experience too with 2008 R2, it's automatic and takes the IP address and configure it to itself while hiding the original Ethernet port.

 

Now, it's not the case as shown on the figure above.

 

I have (4) LOM ports actually. NIC1=LOM, NIC2=LOM1, etc..

[rich_tech]

I would suggest removing the virtual switch off the box as a test, going through all the NIC settings for the ethernet port that you want to use as the virtual switch port that you want to use and checking that everything is ok on there before re-enabling the virtual switch and adding ports on there.

 

Make sure its an external switch type as well and allow management OS to use the switch too to prevent any issues with its connectivity offhand when your testing.

[snagrat]

Did you add the virtual switch when you added the role?

 

If so remove the virtual switch, apply everything and add it again.

 

Has happened a few time to me when adding through server manager

[dapaulio]

I have seen NIC's that are on the mainboard being named LOM i assume to differentiate between them and a HBA card. Lights Out tend to have their own NIC which do not show up in Network connections.

 

Sounds like you may have missed something when creating the virtual switch. I remove it and try again

 

Is LOM1 part of a teamed connection? Did you select the team connection when installing the virtual switch?