none
Cannot remove Hyper-V Virtual Network Adapter RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    In the process of working with SCVMM, a number of virtual NICs were created for cluster, management, and live migration traffic.  These do not have a single backing physical NIC.

    Do to other issues, the VM Host with these virtual NICs is not longer part of that SCVMM deployment.  (In fact, I threw out that deployment and started over.)  Unfortunately, because there is no longer any SCVMM associated with the VM host, it appears there is no way to remove the virtual network adapters.

    I have spent quite a bit of time searching the web, and all of the "solutions" assume there is a VM, SCVMM, etc. still around and associated with the virtual network adapter.  In my case, this IS NOT true.  These virtual network adapters are orphans, zombies, or what ever name you want to use.

    So, how do I get rid of them?  I'm assuming it will be using PowerShell, but so far I haven't been able to find any appropriate cmdlet.

    - Mark

    Friday, April 18, 2014 8:16 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mark,

    this guy seemed to have a similar issue and solved it 'the hard way'

    http://blogs.technet.com/b/chrad/archive/2010/02/28/hyper-v-lingering-internal-nics-unable-to-remove.aspx

    hope it helps

    //Christophe

    MCITP SA - MCP Active Directory - MCP Infrastructure - MCP Server Virtualization www.it101.eu

    Friday, April 18, 2014 8:44 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Christophe.

    I may have to resort to that.  It just seems odd that while there is a Get-NetAdapter there is no corresponding Remove-NetAdapter.  Also it is curious that the virtual NIC is called a "Hyper-V Virtual Network Adapter", the Hyper-V manager knows nothing about it, and there are no Hyper-V cmdlets (at least) to clean up.

    - Mark

    Friday, April 18, 2014 9:18 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    actually it does exist ;-) (as from PS 4.0)

    http://technet.microsoft.com/en-us/library/hh848565.aspx

    //Christophe

    MCITP SA - MCP Active Directory - MCP Infrastructure - MCP Server Virtualization www.it101.eu

    Friday, April 18, 2014 10:01 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well... almost :-P

    The Remove-VMNetworkAdapter cmdlet appears to require a VM (it least it did when I tried be before starting this thread :-)  Unfortunately, these vNICs are orphans.  They are not associated with any VM or logical switch.

    - Mark

    Friday, April 18, 2014 10:54 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you want to remove the rests of a logical switch deployment on a Hyper-V host, you should perform the following:

    1) Delete the Virtual Switch in Hyper-V Manager (all the vNICs will be based on this one)

    2) Delete the teaming configuration on the host.

    -kn

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

    Saturday, April 19, 2014 5:53 PM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Kristian.

    As I indicated in my original post and my reply the other day, these vNICs are not associated with any virtual switch.  In other words, there is no virtual switch (for these vNICs).  They are orphans.  It is because of this I have not been able to find any way to remove them as yet.

    - Mark

    Sunday, April 20, 2014 4:47 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry for not paying attention. I've seen the same as you, only on hosts that has been in-place upgraded from 2012 to 2012 R2. Is that the case here as well?

    -kn

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

    Monday, April 21, 2014 5:52 PM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    The system on which I'm seeing this problem is running W2K12R2.  It may have been upgraded but I don't believe it was.  In any event, the orphan vNICs were created long after any upgrade might have been done.  In other words, the W2K12R2 system has been stable for quite a while; before I started experimenting with System Center.

    - Mark

    Monday, April 21, 2014 6:01 PM
    |