Ucs 2.2(1d) leads to vmware network outtages

Since the update to 2.2(1d) we have network timeouts / outtages between vsphere vm's hosted on ucs b-series servers and the rest of the world outside vmware / ucs. first occured with sles10 guests, but windows 2008 and more are also involved. any idas or similar experiences?

Hello,
I don't want this to be taken as a recommendation, but more as an informative post in response to your concerns about the the Cisco tech may have said in regards to it being expected behavior. But just for reference, this would be in line with your option #3 you have listed above.
Layer 2 Disjoint Upstream Packet Forwarding in End-Host Mode
Server links (vNICs on the blades) are associated with a single uplink port (which may also be a PortChannel). This process is called pinning, and the selected external interface is called a pinned uplink port. The process of pinning can be statically configured (when the vNIC is defined), or dynamically configured by the system.
In Cisco UCS Manager Release 2.0, VLAN membership on uplinks is taken into account during the dynamic pinning process. VLANs assigned to a vNIC are used to find a matching uplink. If all associated VLANs of a vNIC are not found on an uplink, pinning failure will occur.
The traffic forwarding behavior differs from that in Cisco UCS Manager Release 1.4 and earlier in the way that the incoming broadcast and multicast traffic is handled. A designated receiver is chosen for each VLAN, rather than globally as in Cisco UCS Manager Release 1.4 and earlier.
This is from the following link:
http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/white_paper_c11-692008.html
So as you can see, that behavior has been present since 1.4 release and onwards. There will only be one designated receiver per vlan. This may be why the tech mentioned that as a viable workaround. in your case, it would be to ensure that the ports we need to multicast are set to do so on a specific vlan, and that that vlan is only allowed on one interface (or port-channel). If we have it enabled on multiple uplinks and they are not listening on the one they are pinned to, we may see that traffic be dropped.
Regards,
-Gabriel

Similar Messages

  • How can I use PowerShell to Remove "Ghost" (Old Hidden) VMware Network Adapters in Windows 7?

    We recently upgrade the virtual hardware of some of our VMware VM's running Windows 7. One side-effect is that in Windows on these machines, an instance of the NIC from the previous version of virtual hardware remains, as a hidden
    device. This can be easily found manually on a machine by enabling Device manager to show hidden devices (registry and a menu option - View...Show Hidden Devices). You can then just right-click on the device in question and uninstall.
    The problem here, like in so many other tasks, is that you may have multiple instances, on multiple machines. We had just that, and in scouring the internet for a PowerShell only script to resolve the issue, I could not find one. Therefore, I've written
    my own.
    This exact script is only seeking out VMware "VMXNET3" nic cards, but could be easily adapted to find Ghost NIC's for a different vendor using my example. There are also some commented lines left in to aid you as an example of how you can
    test the various queries in your own environment, on a test machine, before a full-blown deployment. 
    NOTE: Please try this out (at your own risk - I am not responsible for how this works out for you), and please vote for my answer to this dilemma if this helped you. I'd appreciate it after all of the sweat the script took to crank out.
    Thanks!
    P.S. This script, of course, requires that Powershell is installed and enabled on the target computer. It then must be run as System - In our environment it is being remotely pushed through a software delivery systems, which runs this scrpt
    as system.
    THE SCRIPT:
    CLS
    #Querying WMI for Ghost NICs and Returning Criteria...
     Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
     Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
     Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
     Write-Host ""
     Write-Host "Checking Powershell Version" -Foreground Yellow
     $host.version
     Write-Host ""
     Write-Host "Searching for Ghost NIC's" -Foreground Yellow
     $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
     $Ghosts | Select-Object Name,DeviceID
     If ($Ghosts -NE $NULL)
      Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
      Write-Host ""    
      else
      Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
      Write-Host ""    
      EXIT 0
    #Using Criteria to Obtain the GUID of each Ghost NIC
     Write-Host "Getting NIC Variables" -Foreground Yellow
     foreach ($_ in $Ghosts) {
      $DID = $_.DeviceID
      If ($DID -NE $NULL)
      Write-Host "The NIC DID: $DID"
      else
      Write-Host "$DID is NULL - Exiting..."
      EXIT 666
      if($DID -NOTLIKE "1*")
       Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
       Write-Host "" 
       $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000$DID"
      ELSE
       $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00$DID"
      $GUID = $NICREG.NetCfgInstanceId
      Write-Host "The NIC GUID: $GUID"
                    $PNPDID = $NICREG.DeviceInstanceID
      $PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
      Write-Host "The truncated PNPDevice ID is $PNPDID"
      Write-Host ""
      Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
      $NICREGPATH = @(1..50)
      foreach ($_ in $NICREGPATH)
       $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
       if($TESTREG -EQ $FALSE)
        #Write-Host ""
        #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED     
        ELSE
        #Write-Host "True - NIC $_ Exists" -Foreground Green
        $NICID = $_    
        $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
        #Write-Host "The Sub-Key Path To Query = $SubPath1"
        $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
        #Write-Host "The Sub-Key Path To Query = $SubPath2"
        $NICProperties = Get-ItemProperty $SubPath1
        #$NICProperties
        $Match = $NICProperties.ServiceName    
        #$Match
        foreach ($_ in $Match) {
        #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
        #Write-Host ""
        if($_ -NE $GUID)
        #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                                    #Write-Host ""
        ELSE
        Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
        Remove-Item $SubPath1 -Recurse  -ErrorAction SilentlyContinue
        Remove-Item $SubPath2 -Recurse  -ErrorAction SilentlyContinue
        $CCS = @("ControlSet001", "ControlSet002")
        foreach ($_ in $CCS) {
         $CCS = $_
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose 
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
                                             if($DID -NOTLIKE
    "1*")
                  $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                             Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
           ELSE
           $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
           Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
    #This is our Success check at the end
     Write-Host ""
     Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
              $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
     $Ghosts | Select-Object Name,DeviceID
      If ($Ghosts -NE $NULL)
      Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
      Write-Host ""
      EXIT 666
      else
      Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
      Write-Host ""    
      EXIT 0

    THE SCRIPT:
    CLS
    #Querying WMI for Ghost NICs and Returning Criteria...
    Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
    Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
    Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
    Write-Host ""
    Write-Host "Checking Powershell Version" -Foreground Yellow
    $host.version
    Write-Host ""
    Write-Host "Searching for Ghost NIC's" -Foreground Yellow
    $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
    $Ghosts | Select-Object Name,DeviceID
    If ($Ghosts -NE $NULL)
      Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
      Write-Host ""   
      else
      Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
      Write-Host ""   
      EXIT 0
    #Using Criteria to Obtain the GUID of each Ghost NIC
    Write-Host "Getting NIC Variables" -Foreground Yellow
    foreach ($_ in $Ghosts) {
      $DID = $_.DeviceID
      If ($DID -NE $NULL)
      Write-Host "The NIC DID: $DID"
      else
      Write-Host "$DID is NULL - Exiting..."
      EXIT 666
      if($DID -NOTLIKE "1*")
       Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
       Write-Host ""
       $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000$DID"
      ELSE
       $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00$DID"
      $GUID = $NICREG.NetCfgInstanceId
      Write-Host "The NIC GUID: $GUID"
                    $PNPDID = $NICREG.DeviceInstanceID
      $PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
      Write-Host "The truncated PNPDevice ID is $PNPDID"
      Write-Host ""
      Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
      $NICREGPATH = @(1..50)
      foreach ($_ in $NICREGPATH)
       $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
       if($TESTREG -EQ $FALSE)
        #Write-Host ""
        #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED    
        ELSE
        #Write-Host "True - NIC $_ Exists" -Foreground Green
        $NICID = $_   
        $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
        #Write-Host "The Sub-Key Path To Query = $SubPath1"
        $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
        #Write-Host "The Sub-Key Path To Query = $SubPath2"
        $NICProperties = Get-ItemProperty $SubPath1
        #$NICProperties
        $Match = $NICProperties.ServiceName   
        #$Match
        foreach ($_ in $Match) {
        #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
        #Write-Host ""
        if($_ -NE $GUID)
        #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                                    #Write-Host ""
        ELSE
        Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
        Remove-Item $SubPath1 -Recurse  -ErrorAction SilentlyContinue
        Remove-Item $SubPath2 -Recurse  -ErrorAction SilentlyContinue
        $CCS = @("ControlSet001", "ControlSet002")
        foreach ($_ in $CCS) {
         $CCS = $_
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
                                             if($DID -NOTLIKE
    "1*")
                  $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                             Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
           ELSE
           $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
           Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
    #This is our Success check at the end
    Write-Host ""
    Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
              $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
    $Ghosts | Select-Object Name,DeviceID
      If ($Ghosts -NE $NULL)
    Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
      Write-Host ""
      EXIT 666
      else
      Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
      Write-Host ""   
      EXIT 0
    Hello Octavio,
    I'm having similar issues with azure VMs (windows server 2008 and 2012). I noticed that the name of the network adapter changes every time the servers are turned off and then on.
    For example every time I perform that action on each VM, the network adapter became to "Microsoft Hyper-V Network Adapter #3" (and then #4, #5, etc).
    I found in to many forums that to resolve that is needed to remove Hidden (Ghost) Network Adapters and most of the people is doing that manually from the device manager (right click on the hidden network adapter and select uninstall).
    Then I found this script created by you and made some changes to find Description -like "Microsoft Hyper-V Network*".
    It seems to find the adapters and also remove them (based on the script results). But if I go to the device manager after restarting the server, all hidden (ghost) adapters are still there (for example Microsoft Hyper-V Network Adapter
    #2, Microsoft Hyper-V Network Adapter #3, Microsoft Hyper-V Network Adapter #4, Microsoft Hyper-V Network Adapter #n).
    The only thing I noticed after running the script is that, in the Control Panel -> Network and Sharing Center, the name of the adapter has no # (Now is shown as “Ethernet” and before as “Ethernet #”)
    This is my script, could you please take a look and tell me if there is something wrong o missing?
    CLS
    #Querying WMI for Ghost NICs and Returning Criteria...
    Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
    Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
    Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
    Write-Host ""
    Write-Host "Checking Powershell Version" -Foreground Yellow
    $host.version
    Write-Host ""
    Write-Host "Searching for Ghost NIC's" -Foreground Yellow
    $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "Microsoft Hyper-V Network*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
    $Ghosts | Select-Object Name,DeviceID
    If ($Ghosts -NE $NULL)
      Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
      Write-Host ""    
      else
      Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
      Write-Host ""    
      EXIT 0
    #Using Criteria to Obtain the GUID of each Ghost NIC
    Write-Host "Getting NIC Variables" -Foreground Yellow
    foreach ($_ in $Ghosts) {
      $DID = $_.DeviceID
      If ($DID -NE $NULL)
      Write-Host "The NIC DID: $DID"
      else
      Write-Host "$DID is NULL - Exiting..."
      EXIT 666
      if($DID -NOTLIKE "1*")
       Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
       Write-Host "" 
       $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\000$DID"
      ELSE
       $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\00$DID"
      $GUID = $NICREG.NetCfgInstanceId
      Write-Host "The NIC GUID: $GUID"
                    $PNPDID = $NICREG.DeviceInstanceID
      $PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
      Write-Host "The truncated PNPDevice ID is $PNPDID"
      Write-Host ""
      Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
      $NICREGPATH = @(1..50)
      foreach ($_ in $NICREGPATH)
       $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
       if($TESTREG -EQ $FALSE)
        #Write-Host ""
        #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED     
        ELSE
        #Write-Host "True - NIC $_ Exists" -Foreground Green
        $NICID = $_   
        $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
        #Write-Host "The Sub-Key Path To Query = $SubPath1"
        $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
        #Write-Host "The Sub-Key Path To Query = $SubPath2"
        $NICProperties = Get-ItemProperty $SubPath1
        #$NICProperties
        $Match = $NICProperties.ServiceName    
        #$Match
        foreach ($_ in $Match) {
        #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
        #Write-Host ""
        if($_ -NE $GUID)
        #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                                    #Write-Host ""
        ELSE
        Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
        Remove-Item $SubPath1 -Recurse  -ErrorAction SilentlyContinue
        Remove-Item $SubPath2 -Recurse  -ErrorAction SilentlyContinue
        $CCS = @("ControlSet001", "ControlSet002")
        foreach ($_ in $CCS) {
         $CCS = $_
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose 
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
                                             if($DID -NOTLIKE "1*")
                  $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                             Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
           ELSE
           $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
           Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
         $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
         Remove-Item $reg1 -Recurse  -ErrorAction SilentlyContinue -verbose
    #This is our Success check at the end
    Write-Host ""
    Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
              $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "Microsoft Hyper-V Network*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
    $Ghosts | Select-Object Name,DeviceID
      If ($Ghosts -NE $NULL)
    Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
      Write-Host ""
      EXIT 666
      else
      Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
      Write-Host ""    
      EXIT 0

  • Using OracleVM in VMWare - Network problem

    Hi,
    I'm desperately trying to install OracleVM in VMware workstation - just for testing purposes of course. However I simply cannot connect to the VM manager once it has installed...
    When the installation is complete, it says to connect to .... go to http://127.0.0.1/em. Obviously this is wrong as it is the address of the local machine relative to itself. I have installed OracleVM server & manager 7 times now attempting to try different networking options to get it working - but no luck.
    I currently have OracleVM Server & Manager installed inside a VMware VM. Networking is set to NAT (but have also tried Bridged and host-only). ifconfig in client gives this:
    https://www.sugarsync.com/pf/D851631_6278798_671551
    When using bridged, Oracle VM server is at least able to ping the outside world (pinged google to test), however in NAT mode this fails too.
    Have already tried doing a ifup eth0 - but no luck here either.
    Any clues?
    Thanks

    This article has some good info http://appletoolbox.com/2011/03/facetime-activation-error-could-not-sign-in-plea se-check-your-network-connection-and-try-again-fix/ and there is also Apple's FaceTime troubleshooting page http://support.apple.com/kb/HT4319. Maybe these will help.

  • C240 M3 with VIC 1225 VMware network issue

    Just got my hands on a few C240 M3′s with the VIC 1225 adapter and began setting them up as a VMware 5.1 U1 cluster. I’ve configured 8 vNICs per host: 2 for Management, 2 for VMotion, 2 for iSCSI, and 2 for VM traffic. Each pair of vNICs has one pinned to uplink 0 and the other to uplink 1. vNICs are set to trunk mode in the VIC since I am tagging multiple VLANs from VMware. The hosts are physically connected to a stacked pair of Cisco 4500-X switches; physical uplink 0 to one switch, uplink 1 to the other switch. Switch ports are trunked to allow the VLANs we plan to use. Portfast is enabled. VMware vSwitches using Source Port ID for Load Balancing and the vNICs are active/active for Management and VM traffic. No port channel or Etherchannel is configured on the swtiches.
    After creating a VM for vCenter and joining the hosts to it, I started migrating existing VMs from an old cluster and saw odd network behavior. It seems whenever a VM or vmkernel interface are on any vNIC pinned to the same physical uplink on the same host, they can’t talk to each other.
    Example: VM1 and VM2 are on host 1. VM1′s network adapter is pinned to vNIC1 using VLAN 10 which uses physical uplink 0. VM2′s network adapter is pinned to vNIC2 using VLAN 10 which uses physical uplink 1. VM1 and VM2 can ping each other. If I move VM2′s network adapter to any vNIC that uses physical uplink 0, just like VM1, then VM1 and VM2 can no longer ping each other. Or if host 1′s management IP is pinned to vNIC 1 on physical uplink 0, any VM on host 1 using a vNIC also pinned to physical uplink 0 cannot ping the host.
    Anyone have any ideas?  Is something configured incorrectly on the switch?  On the VIC?
    Thanks!

    Hello Michael,
    I assume VIC is operating Classical Ethernet ( CE ) mode and VM1 and VM2 are in different vswitchs for the non-working scenario, ( where there vNICs used by vSwitch are pinned to physical uplink ) .
    If this is the scenario, the frames have to be switched upstream switch and needs to be forwarded back on the same switch interface. Any IEEE standards based switch will not forward such traffic flow.
    You might want to take advantage of Adapter-FEX or adapt changes to design to accommodate such traffic flows.
    HTH
    Padma

  • Vmware network problem

    I'm running Archlinux on Vmware Workstation 6.5.
    During installation It set up network and downloaded some packages.
    I had options of manual, DHCP, etc. and I choosed DHCP, everything worked and all, and I downloaded the packages...
    After installation was done I rebooted and thought I should install xorg through pacman.
    When I booted back into Arch first thing I did was,
    ifconfig eth0 up && dhcpcd eth0
    Then to make sure It was up and all, I did
    ping 192.168.1.1
    (my router)
    So far, so good.
    Then (correct me if I'm wrong), I thought I should update my system and all, and I did a
    pacman -Su
    Took like ages, tho. But finally everything worked.
    For some reason I figured I should reboot (for forks, daemons, dependencies, etc.)
    I did the same thing as before (setup the network with dhcpcd).
    Then for instalation of xorg I did:
    pacman -S xorg
    , first I got some Y/n's (I did Y[es] on both of them), then It seems to be an error about failure retrieving the packages from core database. (I'm sorry I can't post the error message on account I have deleted the vmware-image, since it seemed to hate me..)
    Bottom line:
    Have anyone else had this problem? If so ... help?

    Unsuccessful bump, is unsuccessful.

  • VMWare - networking and ESXi installation questions

    Hey all, hoping for some assistance on building my servers.
    I am likely going with SuperMicro 2028R-E1CR24N due to cost and the fact that I can put Samsung Pro 845DC SSD drives in there and it will be covered under warranty (does anyone use SuperMicro today?), but am still considering HP DL Gen9 series servers because, well, they are HP and its always a slightly safer bet than SuperMicro...but the costs with SSD drives is just too high
    Question 1.....
    I am unsure whether to get 10GB RJ 45 NICs or the 10GB SFP+ NICs
    Not sure between Intel 520X, 540, 560...etc.
    The switches these servers will be plugging into will be Cisco 3750X switches, they currently don't have 10GB SFP+ modules yet but I could easily purchase though.
    So I am unsure if SFP+ provides better and TRUE 10GB throughput and bandwidth? Or is RJ45 10gb NICs ok and I simply just plug them into the regular ports on the switch (I think they are set to auto/auto/1GB though?)
    I also have the option for X540 Quad Port 10GBAse-T but unsure if I need it or how it could help me...
    Question 2....
    SuperMicro doesn't have slots for SD or MicroSD cards for the ESXi installation but they do have a 64GB Sata 6GB/s Disk on Module (MLC)..I know I don't need the space and it doesn't look like it needs one of the regular drivebays on the server for this, so will this be sufficient?
    Does anyone use this today and how is the performance?
    HP has slots for MicroSD cards...
    Thanks all!

    The minimum version, for both Windows 8 and 8.1, is ESXi 5.1
    To upgrade, you need to upgrade at least one of your hosts to ESXi 5.1. To manage that host with vCenter, you will need to upgrade vCenter to 5.1 as well, which will manage your ESXi 5.0 and 5.1 hosts. See the following link for interoperability: http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php
    Here is the link to upgrade a host to ESXi 5.1:
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032757
    Here is the link to upgrade from vCenter 5.0 to 5.1:
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032283
    I strongly recommend you use the VMware Interoperability Guide, in case you have older ESXi hosts (i.e. 3.5) that will no longer be managed when you move to vCenter 5.1.
    Hope that helps.

  • Basic UCS networking

    Hi Guys
    Im new to UCS and I need some help getting network connectivity up and running from my UCS blade servers.
    I have a Nexus 5K connected to a 6248FI.
    Nexus Port config is:
    interface Ethernet1/8
      description Portchannel to Fibre Interconnect A
      switchport mode trunk
      switchport trunk native vlan 2025
      spanning-tree port type edge trunk
    I've configured a unified uplink port on the FI so i've got FC and Ethernet going through the same port.
    FI port config:
    interface Ethernet1/32
      description UF: UnifiedUplink
      pinning border
      switchport mode trunk
      switchport trunk native vlan 2025
      switchport trunk allowed vlan 1,2025-2026,2276,4048
      udld disable
      no shutdown
    The Vnic on my server looks like this :
    interface Vethernet833
      description server 1/4, VNIC 1-fabric-A
      switchport mode trunk
      no pinning server sticky
      pinning server pinning-failure link-down
      no cdp enable
      switchport trunk allowed vlan 2276
      bind interface port-channel1290 channel 833
      service-policy type queuing input default-in-policy
      no shutdown
    Now , the thing is , i've put an IP address on the server and it cannot ping the default gateway.
    I've been following online guides as to how to set things up but cannot for the life of me figure out why this isnt working!
    any pointers would be greatly appreciated.
    Thanks
    AK

    Can you please clarify
    - you are using UCS Blade system ?
    - which OS did you install
    - what do you mean by
    Now , the thing is , i've put an IP address on the server and it cannot ping the default gateway.
    I've been following online guides as to how to set things up but cannot for the life of me figure out why this isnt working!
     do you talk about CIMC, or OS ?

  • Losing network connection and NIC acts weird from warm/hot weather/temperatures?

    Hello.
    Is there a known issue on MSI P43 NEO3-F (MSI-7514) motherboards' onboard RealTek RTL8168C (P)/8111C(P) PCI-E Gigabit Ethernet NIC network disconnecting and acting weird during warm/hot weather?
    I noticed lately and back on 1/11/2009 night when weather got warm/hot (e.g., my room can get over 85F degrees, but lately it has been 80F degrees), my network would lose its connection. See http://img9.imageshack.us/img9/5580/screenshots.gif for a few SpeedFan's sensor readings when the incidents occurred. I have never seen this happen when the weather is cooler (60-70F degrees in my room).
    I also think this only happens if I am using the PC lightly (nothing intensive) like watching fullscreen videos (video overlay), surfing the Web, etc. I don't see any errors or evidences that it happens when idled (e.g., asleep or out). Uptime doesn't seem to matter since I have seen days to 3.5 hours.
    I tried upgrading network driver twice (e.g., Realtek_XP_5714_0219 from
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false ...), disabling Kerio Personal Firewall v2.1.5 (XP's disabled already), releasing and renewing IP address (works, but still no network -- can't even ping my router!), unplugging and replugging the cat5 cable (do see the network port lights on), touching the network jack and hardware inside and outside of the case (not hot), trying another cat5 cable and a network port on a switch instead router's), changing from "Minimal Power Management" to full power (no underclocking/slowing down when idled), etc.
    During the disconnections, I tried:
    C:\>tracert 192.168.0.1
    Tracing route to 192.168.0.1 over a maximum of 30 hops
      1     *        *        *     Request timed out.
      2     *        *        *     Request timed out.
      3     *        *     ^C
    IPCONFIG.EXE /ALL when having network problems:
    Windows IP Configuration
            Host Name . . . . . . . . . . . . : FOOBAR
            Primary Dns Suffix  . . . . . . . :
            Node Type . . . . . . . . . . . . : Hybrid
            IP Routing Enabled. . . . . . . . : No
            WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter VMware Network Adapter VMnet8:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
            Physical Address. . . . . . . . . : 00-50-56-C0-00-08
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.134.1
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
    Ethernet adapter VMware Network Adapter VMnet1:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
            Physical Address. . . . . . . . . : 00-50-56-C0-00-01
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.80.1
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
    Ethernet adapter HDTV Tuner 2:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : TechniSat DVB-PC TV Star PCI #3
            Physical Address. . . . . . . . . : 00-D0-D7-30-19-C1
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 169.254.178.3
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 169.254.178.1
            Lease Obtained. . . . . . . . . . : Saturday, February 28, 2009 6:55:04 PM
            Lease Expires . . . . . . . . . . : Monday, July 13, 2009 11:28:08 PM
    Ethernet adapter HDTV Tuner 1:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : TechniSat DVB-PC TV Star PCI
            Physical Address. . . . . . . . . : 00-D0-D7-30-1A-1D
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . . . . : Yes
            IP Address. . . . . . . . . . . . : 169.254.178.4
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . :
            DHCP Server . . . . . . . . . . . : 169.254.178.1
            Lease Obtained. . . . . . . . . . : Saturday, February 28, 2009 6:55:21 PM
            Lease Expires . . . . . . . . . . : Monday, July 13, 2009 11:28:25 PM
    Ethernet adapter Local Area Connection 15:
            Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC
            Physical Address. . . . . . . . . : 00-21-85-1A-C6-72
            Dhcp Enabled. . . . . . . . . . . : No
            IP Address. . . . . . . . . . . . : 192.168.0.82
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            Default Gateway . . . . . . . . . : 192.168.0.1
            DNS Servers . . . . . . . . . . . : 192.168.0.1
                                                4.2.2.1
    I checked Windows XP Pro. SP3's event logs and noticed these during the disconnections:
    Event logs showed:
    Event Type:    Information
    Event Source:    Tcpip
    Event Category:    None
    Event ID:    4201
    Date:        2/28/2009
    Time:        6:42:23 PM
    User:        N/A
    Computer:    FOOBAR
    Description:
    The system detected that network adapter \DEVICE\TCPIP_{51FDDE0F-0935-416E-8FE0-3E1A50847D41} was connected to the network, and has initiated normal operation over the network adapter.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 02 00 50 00   ......P.
    0008: 00 00 00 00 69 10 00 40   ....i..@
    0010: 02 00 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    Event Type:    Information
    Event Source:    BROWSER
    Event Category:    None
    Event ID:    8033
    Date:        2/28/2009
    Time:        6:47:22 PM
    User:        N/A
    Computer:    FOOBAR
    Description:
    The browser has forced an election on network \Device\NetBT_Tcpip_{89F40100-0D8D-4C33-A32D-3D91CAEB3FBD} because a master browser was stopped.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Event Type:   Information
    Event Source:   Tcpip
    Event Category:   None
    Event ID:   4201
    Date:      3/1/2009
    Time:      6:19:08 AM
    User:      N/A
    Computer:   FOOBAR
    Description:
    The system detected that network adapter \DEVICE\TCPIP_{51FDDE0F-0935-416E-8FE0-3E1A50847D41} was connected to the network, and has initiated normal operation over the network adapter.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 02 00 50 00   ......P.
    0008: 00 00 00 00 69 10 00 40   ....i..@
    0010: 02 00 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    Event Type:   Information
    Event Source:   Tcpip
    Event Category:   None
    Event ID:   4201
    Date:      3/1/2009
    Time:      6:19:20 AM
    User:      N/A
    Computer:   FOOBAR
    Description:
    The system detected that network adapter \DEVICE\TCPIP_{51FDDE0F-0935-416E-8FE0-3E1A50847D41} was connected to the network, and has initiated normal operation over the network adapter.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 02 00 50 00   ......P.
    0008: 00 00 00 00 69 10 00 40   ....i..@
    0010: 02 00 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    I also noticed the disconnections usually start with red X icon in my taskbar with its bubble and then later the long disconnection even though no red X (1 GB and connected). If I were to disconnect the cat5 cable from NIC, then it wouldn't even detect it is missing the cable!
    The only way to fix this was to reboot (best way and last longer) OR disable network connection and re-enable it (Windows XP's Network Connections) or the NIC itself (Device Manager), but that doesn't always last long (maybe a minute). Example of my pings right after disabling and re-enabling NIC:
    C:\>ping 192.168.0.1 -t
    Pinging 192.168.0.1 with 32 bytes of data:
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
    Request timed out.
    Request timed out.
    Reply from 192.168.0.1: bytes=32 time<1ms TTL=150
    MSINFO32 in case it helps (seems OK to me, but I am not a hardware expert):
    [Conflicts/Sharing]
    Resource   Device   
    I/O Port 0x00000000-0x00000CF7   PCI bus   
    I/O Port 0x00000000-0x00000CF7   Direct memory access controller   
    I/O Port 0x000003C0-0x000003DF   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   
    I/O Port 0x000003C0-0x000003DF   ATI Radeon HD 4800 Series   
    IRQ 21   Intel(R) ICH10 Family USB Universal Host Controller - 3A38   
    IRQ 21   OHCI Compliant IEEE 1394 Host Controller   
    IRQ 21   TechniSat DVB-PC TV Star PCI   
    IRQ 23   Intel(R) ICH10 Family USB Universal Host Controller - 3A34   
    IRQ 23   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A   
    I/O Port 0x0000B000-0x0000BFFF   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   
    I/O Port 0x0000B000-0x0000BFFF   ATI Radeon HD 4800 Series   
    IRQ 16   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   
    IRQ 16   ATI Radeon HD 4800 Series   
    IRQ 16   Intel(R) ICH10 Family USB Universal Host Controller - 3A37   
    IRQ 16   Standard Dual Channel PCI IDE Controller   
    IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 2 - 3A42   
    IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A   
    IRQ 16   ASUS TV880 Video Capture (NTSC)   
    IRQ 17   Microsoft UAA Bus Driver for High Definition Audio   
    IRQ 17   Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40   
    IRQ 17   Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC   
    Memory Address 0xD0000000-0xDFFFFFFF   Intel(R) 4 Series Chipset PCI Express Root Port -
    2E21   
    Memory Address 0xD0000000-0xDFFFFFFF   ATI Radeon HD 4800 Series   
    IRQ 18   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C   
    IRQ 18   Intel(R) ICH10 Family USB Universal Host Controller - 3A36   
    IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A39   
    IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A35   
    IRQ 19   Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A20   
    IRQ 19   Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26   
    Memory Address 0xA0000-0xBFFFF   PCI bus   
    Memory Address 0xA0000-0xBFFFF   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   
    Memory Address 0xA0000-0xBFFFF   ATI Radeon HD 4800 Series   
    Memory Address 0xFED90000-0xFED93FFF   System board   
    Memory Address 0xFED90000-0xFED93FFF   System board   
    I/O Port 0x000003B0-0x000003BB   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   
    I/O Port 0x000003B0-0x000003BB   ATI Radeon HD 4800 Series   
    [IRQs]
    Resource   Device   Status   
    IRQ 9   Microsoft ACPI-Compliant System   OK   
    IRQ 16   Intel(R) 4 Series Chipset PCI Express Root Port - 2E21   OK   
    IRQ 16   ATI Radeon HD 4800 Series   OK   
    IRQ 16   Intel(R) ICH10 Family USB Universal Host Controller - 3A37   OK   
    IRQ 16   Standard Dual Channel PCI IDE Controller   OK   
    IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 2 - 3A42   OK   
    IRQ 16   Intel(R) ICH10 Family PCI Express Root Port 6 - 3A4A   OK   
    IRQ 16   ASUS TV880 Video Capture (NTSC)   OK   
    IRQ 17   Microsoft UAA Bus Driver for High Definition Audio   OK   
    IRQ 17   Intel(R) ICH10 Family PCI Express Root Port 1 - 3A40   OK   
    IRQ 17   Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC   OK   
    IRQ 21   Intel(R) ICH10 Family USB Universal Host Controller - 3A38   OK   
    IRQ 21   OHCI Compliant IEEE 1394 Host Controller   OK   
    IRQ 21   TechniSat DVB-PC TV Star PCI   OK   
    IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A39   OK   
    IRQ 19   Intel(R) ICH10 Family USB Universal Host Controller - 3A35   OK   
    IRQ 19   Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A20   OK   
    IRQ 19   Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26   OK   
    IRQ 18   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3C   OK   
    IRQ 18   Intel(R) ICH10 Family USB Universal Host Controller - 3A36   OK   
    IRQ 23   Intel(R) ICH10 Family USB Universal Host Controller - 3A34   OK   
    IRQ 23   Intel(R) ICH10 Family USB Enhanced Host Controller - 3A3A   OK   
    IRQ 20   Creative SB Audigy 2 ZS (WDM)   OK   
    IRQ 22   TechniSat DVB-PC TV Star PCI #3   OK   
    IRQ 0   System timer   OK   
    IRQ 8   System CMOS/real time clock   OK   
    IRQ 13   Numeric data processor   OK   
    IRQ 4   Communications Port (COM1)   OK   
    IRQ 6   Standard floppy disk controller   OK   
    IRQ 1   Standard 101/102-Key or Microsoft Natural PS/2 Keyboard   OK   
    IRQ 12   Microsoft PS/2 Mouse   OK   
    IRQ 14   Intel(R) ICH10 Family SMBus Controller - 3A30   OK
    My detailed computer configurations can be found here: http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary computer).
    Thank you in advance.

    Quote from: NovJoe on 02-March-09, 23:10:05
    Force your NIC to run at 100Mbps full duplex and see how it goes.
    Check your router / switch ports as well as cables.
    I will try 100 Mbps if it happens again. So far, it hasn't occurred after installing the driver supplied by MSI's Web site and not RealTek's Web site. The room temperatures even got warmer like 83F degrees.
    As for router and switch, what am I checking for? Other computers didn't have any problems. As for cat5 cables, I already tried another one like I said in my original post.

  • Cisco UCS RAID SAS 2008M-8i Mezzanine Card Performance?

    I recently purchased a UCS C220 bundle, which includes a Cisco UCS RAID SAS 2008M-8i Mezzanine Card.  I'm planning on deploying this as a standalone server running XenServer 6.2 in the near future.
    I'm happy with the unit and testing is good, but for one aspect.  The disk IO throughput on it seems to be far short of what I expected.  I have a desktop PC with an Intel DZ77GA-70K motherboard as a lab spare, and the disk IO I can achieve from that server with the same disks exceeds what the C220 seems to be able to achieve, on a consistent repeatable basis.
    The testing I am doing is based around two benchmarks:
    1. A 400G file copy between the two machines, over the network back-to-back to note the maximum sustained throughput, and
    2. A mix of runs with 'sysbench' to mix of tests of local IO, of sequential and random reads and writes, with the command: "sysbench --test=fileio --file-total-size=150G --file-test-mode=seqrd --init-rng=on --max-time=300 --max-requests=0 run"
    For #1, I run a copy to/from an HP MicroServer Gen8, which has 12TB of disk space on it in a Linux RAID0 configuration (4x3TB Seagate drives).  If I copy files to or from this HP Server to the Intel DZ77GA-70K I am able to easily saturate the 1G network, achieving a sustained 960MBit/s for an hour or more at a time.  If I then take the exact same SATA disks from the DZ77GA-70K, connect these into the UCS box and do the exact same network copy with the exact same OS, I'm only about to get around ~400-500MBit/sec of sustained throughput.
    For #2, the test results of which are entirely local to the C220, come in around 105-110 MByte/sec on a sequential read, which drops to around 2 MByte/sec on a random read or write test.  No surprise of the enormous drop - because random reads/writes are a pretty tough IO load, but I would expect sequential reading should be much better.  I can get consistent sysbench seqrd results from the MicroServer of around 300 MByte/sec, for example.
    I can consistently replicate this with Redhat 6.5, as well as Gentoo (running the latest linux kernel) as well as from a Xen 6.2SP1 Hypervisor install on the C220 (tested from the Dom0 domain itself, as well as a Linux guest) all 64 bit.  Jumbo frames are enabled end-to-end also, and CPU is not bottlenecking.  Latest firmware is installed on all components.  The ucs-cxxx-drivers.1.5.4a.iso image states that for the Redhat and Xen systems, that the required drivers are included in the OS, so I don't need to worry about installing them separately.  Presumably the Gentoo system has even newer drivers again because it has a very new kernel, but alas the throughputs are the same on all of those systems.
    I have tried with SATA as well as a SAS drive, and the test results are also practically the same.  All disks in all servers are Seagate 6.0 Gb/s units, and none of the servers are swapping to disk at any stage.
    I am happy with network IO - I can completely saturate the 1G ports easily, and I'm convinced that's not a part of the problem here.
    What could cause this sort of performance?  Storage card logs in CIMC don't indicate anything is wrong and none of the OS's are indicating issues of any sort, but it certainly does seem something isn't right in that I'm getting significantly superior performance from a desktop motherboard and the MicroServer, than an enterprise grade server, when testing with the exact same hard drives.
    Questions:
    - Is the 2008M-8i card considered a low-end RAID card or should I be getting reasonable throughput from it?  I was anticipating performance at least as good as a desktop motherboard, but this doesn't seem to be the case.  The RAID card as a component is more expensive than an entire MicroServer or Intel Motherboard so it should run much better, yes?
    - What sort of performance should I expect out of this card on a single sequential read or write?
    - Can this RAID card run drives just as JBOD's or do all disks have to be initialised in an array (even if just a RAID0 array with 1 disk)?  It seems if they are added to the server they do not show up to any OS until they are initialised as part of an array, although I haven't delved into the BIOS settings of the card itself (only from CIMC so far).
    - I recall seeing something about best practice of having two virtual drives on these cards, what is the impact in running more, given the card certainly allows more to be created (I currently have 4 while I am testing)
    -  I noticed on Cacti graphs while rebuilding a RAID1 array that the CPU ran hotter while the array was being rebuilt, and cooled down once the rebuild had completed, which indicates the rebuild was using up CPU on the host hardware.  Should this not have been entirely transparent to the system if the RAID activity is offloaded to this card, or is an increase in CPU to be expected?
    I'm very keen to find out others experiences of this card, what people have done to get good throughput out of it, or if I should go back to a whitebox server with an Intel board   :-)
    Thanks,
    Reuben

    Hello Reuben,
    I reached out to colleagues who are more knowledge on this topic and here is their response.
    - Is the 2008M-8i card considered a  low-end RAID card or should I be getting reasonable throughput from  it?  I was anticipating performance at least as good as a desktop  motherboard, but this doesn't seem to be the case.   The RAID card as a component is more expensive than an entire  MicroServer or Intel Motherboard so it should run much better, yes? -
    2008M-8i card is a entry/value card with an  expected performance which is better than a software RAID. This card  doesn’t utilise memory in a standard RAID 0/1 configuration.
    - What sort of performance should I expect out of this card on a single sequential read or write? - We should expect around 1GB sequential read (refer link http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/whitepaper_c11-728200.html)
    - Can this RAID card run drives  just as JBOD's or do all disks have to be initialised in an array (even  if just a RAID0 array with 1 disk)?  It seems if they are added to the  server they do not show up to any OS until they  are initialised as part of an array, although I haven't delved into the  BIOS settings of the card itself (only from CIMC so far). -
    This card can be used in JBOD mode. To enable JBOD mode you need to use MegaCLI commands.  This option is not present as a default  configuration.
    Please note: Once we enable the JBOD mode – it  cannot be reverted back to the default RAID mode setting.
    - I recall seeing something about  best practice of having two virtual drives on these cards, what is the  impact in running more, given the card certainly allows more to be  created (I currently have 4 while I am testing)  -
    This doesn’t apply for this card as it  does not have any cache. Can you please point us  to the document about best practice of having two virtual drives ?
    -  I noticed on Cacti graphs while  rebuilding a RAID1 array that the CPU ran hotter while the array was  being rebuilt, and cooled down once the rebuild had completed, which  indicates the rebuild was using up CPU on the  host hardware.  Should this not have been entirely transparent to the  system if the RAID activity is offloaded to this card, or is an increase  in CPU to be expected? - Creating/Deleting/Modifying a RAID volume is a CPU independent operation. 

  • Leading zeros in XLS sheet

    Hello Experts,
    I have one report in ALV format. It is displayed perfect.
    When we download it into XLS format it appends leading zeros in 'NETWORK no' Field.
    Can you all please help me how to remove it?
    Remember, ALV is showing perfect o/p. So
    CONVERSION_EXIT_ALFA_OUTPUT  or any other FM in that category is of no use.
    Also there is no code to download in XLS. User selects Standord procedure to download from ALV.
    But he is getting Leading zeros.
    I would be thankful for the help.
    Best Regards,
    Harish

    HI Joshia,
    Lets consider you are downloading MATNR which comes with leading Zero.
    We solve this by below case .
    you can download the value in character format with preceding single quote .
    if you are downloading 000010 means, assign that value as '000010.
    So that, excel can treat it as character & the zeros will be retained.
    While uploading the data to internal table it_material
    CONCATENATE '"' it_material-matnr into it_material-matnr.
    append it_material.

  • In Order to Configure TCP/IP, You Must Install and Enable a Network Adapter Card

    I get this message when I try to TCP/IP settings in any network card. 
    "In Order to Configure TCP/IP, You Must Install and Enable a Network Adapter Card"
    What I have tried:
    1. Removed card, did not click on "Remove driver". Then re-scanned in device manager. This usually leads to the network card showing up with a yellow exclamation mark, and I can not get it work again (have to use system restore).
    2. Removed card, deinstalled driver, re-installed driver. 
    3. Rebooted a thousand times. 
    4. Used the Lenovo drivers.
    5. Used the Intel drivers. 
    Doesn't matter what I do, I'm stuck with yellow exclamation marks in the end for the LAN and WLAN card, with not hope to repair them.
    Driver version for the Intel 82579LM is 12.9.15.0
    Driver version for the centrino advanced-n 6205 is 15.10.4.2
    I'd really like some help on how to fix this so I'm able to configure my network manually. 

    For clarity, as your machine MTM number lists it with another type of WLAN adapter, and apparently, therein lies your problem.
    How To Fix Error Message : In Order To Configure TCP/IP , You Must Install And Enable Network Adapte...
    [How To Fix] In Order to Configure TCP/IP, You Must Install and Enable a Network Adapter Card
    ThinkPad W540 (20BG) - i7-4800MQ/24GB // ThinkPad T440s (20AQ) - i7-4600U/12GB
    ThinkPad T440p (20AW) - i7-4800MQ/16GB // ThinkPad Helix (3698-6EU) - i5-3337U/4GB
    ThinkPad W520 (4282-W4Q) - i7-2720QM/32GB // ThinkPad T400 (2767-W1C) - P9500/8GB
    ThinkPad T61 (7665-CTO) - T7700/4GB // ThinkPad T60p (8741-C2G) - T7400/4GB

  • OEL 4 on VMware Static IP configuration.

    Hi
    I am trying to install OEL4 as a guest OS on VMware workstation 5 host OS is Vista.
    My problem is that i cant use DHCP. Sometimes my laptop is connected to Internet some times not. Now i want to access my Virtual machine from Host Os using Putty. For that i need a static IP address. Please suggest what should be the DNS , Gateway and IP Address .
    Thanks in Advance

    you have three options in vmware network:
    - bridged networking
    - host only
    - nat
    If you want to access Internet or lan network host, from your guest host, you must to use bridged networking o NAT.
    If you use bridged networking, you must to user the same network configuration of your host. If use NAT, you can use DHCP to get the configuration from vmware-dhcp server.
    You can use host only, if you dont need access to lan-host-network (but you can access from your host using putty). In that case, you can use DHCP to get the configuration from vmware-dhcp server.
    Your DNS settings, must be the same DNS that you use in your host (in case you use bridget networking o nat).
    Gateway must be the same gateway you user in your host (in case you user bridget network). If you use nat, gateway is provided by vmware-dhcp server.
    If you user host-only, you dont need gateway.

  • CUCM - UCS Server Replacement

    Hi All,
    We have installed CUCM 9.1.2 on UCS 220-M3 server (standby hardware). Now we are going to replace the UCS server.
    Has any other vmware method or tool available to migrate the virtual machines one UCS to another UCS ? { VM's are resided in DAS) ?

    Technically, Cisco only supports it if using shared storage- http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#VMware_vMotion
    But it usually works fine from a technical standpoint. Just might not get support if something goes wrong with the migration.

  • UCS Design - Where to begin?

    Hello all,
    I recently was given a project to install UCS. It's new to me. We have purchased the following:
    - 2 2960 switches
    - 2 F5 Load Balancers
    - 2 6120 Fabric Interconnects
    - 2 MDS 9148's
    - 1 5108 Blade Chassis
    - EMC Storage (Celerra)
    I understand physically how to connect them all together, but is there some kind of best practice document that tells me things such as how many VSAN's, zones to create, or where to port-channel connections together? The customer is open to any new ideas, so if anyone has a good design or some quick pointers they'd like to share, it would be greatly appreciated.
    Thanks,
    Bobby Grewal

    Bobby,
    I have yet to see a comprehensive guide that contains all the information you're looking for.  There are guides posted on this community & CCO which discuss various topics regarding UCS.  When talking about Best Practices the best method may be to keep recommendations in small digestable chunks. Since no two DC environments are identical, one man's best practice, may be another's man's bottleneck .  Alot of your design considerations also depend on applications, expected load and infrastructure capabilities.  'll shed some advice on a few topics you can take into consideration for your design.
    Let's start from our blades and work our way up.
    Chassis Uplinks
    Assuming you have up to 8 blades in your single Chassis you'll need to first decide how many uplinks you want to use between your Chassis and Fabric Interconnects (FIs).  Supported configurations are 1, 2, or 4 uplinks which provide a max oversubscription of 2:1, 4:1 and 8:1.  Depending on your application bandwidth requirements you may be fine with 2 Uplinks per IOM.  Since you'll get the first 8 ports (6120) or 16 ports (6140) included with the base system, there's nothing stopping you from utilising all four.  People sometimes have reservations about oversubscription, but I can tell you a properly engineered system should be designed with overscription as part of the picture.  Keep in mind this connection a lossless 10G connection.  No TCP retransmissions or dropped frames, which make it much more efficient than standard ethernet.
    Fabric Interconnect Uplinks - Ethernet
    Here's where you will provide all the LAN connectivity for your UCS system into your distribution or core networking layer.  Again, the # of uplinks from each FI will depend on load, but most people start with at least 2 x 10G uplinks in a port channel to their upstream switches and add additional member interfaces as the links near saturation.  Without knowing what the upstream connecting switches your using (2960's or other) willl dictate how many and what toplogies you can take advantage of.  Example - If you had Nexus 5000 or Nexus 7000 switches upstream you could implement virtual port channels offering dual active links from each FI to each switch.  FI's act as your access layer switches, hopefully you have some distribution-level switches to connect into.
    Fabric Interconnect Uplinks - Fibre Channel
    As of the latest release of software (1.4.x) you can take advantage of SAN Port Channels and VSAN trunking.  Previously FC uplinks were treated individually, and allowed to carry only a single VSAN.  This new feature greatly increases the redudancy and efficiency of your SAN fabric being able to bundle 2 or 4 links towards your MDS core switches in a SAN port channel.  With the MDS 9148's support for 8GB FC, you can also minimize the amount of FC uplinks needed from your FI's assuming you have the six port 1/2/4/8 FC modules (Part ID N10-E0060) in your FIs.  If only the only option is 4GB FC due to cost or equipment you can use 2 or more FC uplinks to provide the necessary bandwidth. In terms of VSANs, I've seen two main designs.  One keeping a single VSAN on each Fabric Interconnect - with each FI uplinked to a single SAN Switch.  The other is creating both VSANs on each FI, with each FI uplinking to both SAN Switches.  Most people prefer to keep the SAN fabrics completely separate, but having the both VSANs exist on each FI ensures you maintain access to each fabric in the event a single FI should fail.  Zoning is another intersting topic.  Under legacy practices it was common to create a zone for each host.  This ensured maximum security for hosts & targets.  Since UCS allows us to pre-define WWN pools for quick deployments & provisioning, I see more & more customers implementing interface zoning. This allows you to zone the incoming FC interface coming from UCS with the designated storage targets.  The major advantage of this is once you configure this, you don't have to touch zoning to faciliate the deployment of any UCS hosts.  Drawback is that you now rely on the LUN masking to protect your data.  The management overhead required to deploy zones for each & every new host can be significant, so consider each benefit carefully.
    EMC Celerra NAS
    This is an interesting topic regarding 1.4 software capabilities.  If your EMC Celerra is going to be mainly for UCS access, you can direclty attach the NAS to the FI's.  This is a new feature called Direct Attach Storage. This allows you to connect a NAS such as the Celerra as an Appliance Port to the FI.  If the NAS is intended to server many other devices then you would be better off connecting it to your core network and allow UCS to access it via the uplinks.
    I'll update this thread as I have other suggetions.
    Regards,
    Robert

  • TAP driver / identified vs unidentified networks

    Hi.  I'm running Win7 build 7000, trying to get both my OpenVPN connection and my coLinux connection (TAP-Win32 v9.0.0.4 and 8.0.0.4 respectively) to be identified as Home networks. 
    Currently they each show as "Unidentified network" / "Local only" (sometimes even as participating in the same unidentified network.)  "Local only" is correct, as I don't want to use them as default routes; and I certainly care that I can't name them, but I would like to figure out how to set things up so that I don't have to mark them as Home/Private networks every boot.
    What makes a network "unidentified"?  Absence of a gateway? dhcpv6?  I tried adding a connection-specific DNS suffix to each :) 
    What makes a network identifiable?
    Thanks in advance for any information,
    Arya
    P.S. Here is what I assume is the relevant part of my ipconfig /all output:
    Ethernet adapter OpenVPN:
       Connection-specific DNS Suffix  . : vpn
       Description . . . . . . . . . . . : TAP-Win32 Adapter V9
       Physical Address. . . . . . . . . : 00-FF-D7-7A-74-AD
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::d166:3a1e:30b9:b2e1%20(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.18.0.12(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Thursday, April 02, 2009 9:09:56 AM
       Lease Expires . . . . . . . . . . : Friday, April 02, 2010 9:09:56 AM
       Default Gateway . . . . . . . . . :
       DHCP Server . . . . . . . . . . . : 10.18.0.0
       DHCPv6 IAID . . . . . . . . . . . : 520159191
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-63-E7-20-00-11-43-63-14-3D
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter coLinux:
       Connection-specific DNS Suffix  . : colinux
       Description . . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux)
       Physical Address. . . . . . . . . : 00-FF-F0-51-BC-E3
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::cd23:57d3:f832:e433%18(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.7.0.1(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 453050352
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-63-E7-20-00-11-43-63-14-3D
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Hi
    Use this powershell script it makes necessary changes in registry i found it on the web looking for solution to the same problem under vmware network adapters and modified it to work with tap open vpn devices.
    # see http://msdn2.microsoft.com/en-us/library/bb201634.aspx
    # *NdisDeviceType
    # The type of the device. The default value is zero, which indicates a standard
    # networking device that connects to a network.
    # Set *NdisDeviceType to NDIS_DEVICE_TYPE_ENDPOINT (1) if this device is an
    # endpoint device and is not a true network interface that connects to a network.
    # For example, you must specify NDIS_DEVICE_TYPE_ENDPOINT for devices such as
    # smart phones that use a networking infrastructure to communicate to the local
    # computer system but do not provide connectivity to an external network.
    # Usage: run in an elevated shell (vista/longhorn) or as adminstrator (xp/2003).
    # PS> .\fix-vmnet-adapters.ps1
    # boilerplate elevation check
    $identity = [Security.Principal.WindowsIdentity]::GetCurrent()
    $principal = new-object Security.Principal.WindowsPrincipal $identity
    $elevated = $principal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
    if (-not $elevated) {
    $error = "Sorry, you need to run this script"
    if ([System.Environment]::OSVersion.Version.Major -gt 5) {
    $error += " in an elevated shell."
    } else {
    $error += " as Administrator."
    throw $error
    function confirm {
    $host.ui.PromptForChoice("Continue", "Process adapter?", [Management.Automation.Host.ChoiceDescription[]]@("&No", "&Yes"), 0) -eq $true}
    # adapters key
    pushd 'hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}'
    # ignore and continue on error
    dir -ea 0 | % {
    $node = $_.pspath
    $desc = gp $node -name driverdesc
    if ($desc -like "*TAP-Win*") {
    write-host ("Found adapter: {0} " -f $desc.driverdesc)
    if (confirm) {
    new-itemproperty $node -name '*NdisDeviceType' -propertytype dword -value 1
    popd
    # disable/enable network adapters
    gwmi win32_networkadapter | ? {$_.name -like "*TAP-Win*" } | % {
    # disable
    write-host -nonew "Disabling $($_.name) ... "
    $result = $_.Disable()
    if ($result.ReturnValue -eq -0) { write-host " success." } else { write-host " failed." }
    # enable
    write-host -nonew "Enabling $($_.name) ... "
    $result = $_.Enable()
    if ($result.ReturnValue -eq -0) { write-host " success." } else { write-host " failed." }
    Jarek

Maybe you are looking for