none
Hyper-V and 2008 Core

    Question

  • We have some HP dl380 with 4 NIcs in them, we at first were just using one nic so we disabled the rest, I also used a core configuring program to disable IP6. now we want to enabled the other nics and the Addon NIC card worked fine but the second onbard nic will not enable no matter what we do.


    can anyone help?


    Monday, March 2, 2009 5:17 PM

Answers

  • ***Update***

    I have installed the latest WDK from MSDN and low and behold there is a amd64 version of the devcon tool.  That version of the tool ran and successfully removed my troubled interfaces.  After a reboot they were all re-installed and fully functional.

    So I believe that my problem was related to hardware changes that for some reason required a re-install of the NIC's.  Thank goodness I found a working version of Devcon.

    Thanks.
    • Marked as answer by hothondaguy Thursday, March 5, 2009 10:25 PM
    Thursday, March 5, 2009 10:22 PM

All replies

  • Have you tried using the netsh command?

    i.e.

    netsh

    int

    set int name="Local Area Connection" admin=enabled


    Give that a try.

    PS.

    If you need to see all interfaces type "int show int"

    Monday, March 2, 2009 5:58 PM
  • yes we have, it looks like it does something but then doesn't change the setting, like i said we were able to re-enable the pci-e card nics but not the second onboard nic.
    Monday, March 2, 2009 6:01 PM
  • The only thing I can think of doing is uninstalling the adapters and re-installing. Now you may question - how the hell can I do that?

    2 ways

    1). If you have HP Insight Manager you can force a re-install of the drivers.
    2). Re-install via the command line.

    I will explain the second option in a bit more depth. There is a tool available called devcon.exe which allows you to remove devices via the command line,  I believe the x86 version of this is readily available. The x64 was a bit harder to come by (obviously required for Hyper-V hosts).

    I managed to find a copy on a Windows XP x64 installation media.

    There are plenty of examples around on how to use it (if I remember rightly).

    Once you have worked out to uninstall the adapters you can either reboot or scan for hardware changes via a remote device manager. Hope this helps.

    I'm not sure if I am allowed to provide you with a copy because of license restrictions.

    Richard

    Tuesday, March 3, 2009 5:51 PM
  • Hi,

     

    I tried to perform the following command on my Server Core VM, and all succeed.

    ---------------------------

    netsh interface set interface name = “Local Area Connection” admin = disabled
    netsh interface set interface name = “Local Area Connection” admin = enabled

    ---------------------------

     

    And I found your another post discuss the similar problem,

     

    NIC Issues and Server Core

    http://social.technet.microsoft.com/forums/en-US/winservercore/thread/8351b0fa-421b-4480-8b7c-6cc38905ca99

     

     

    According to ResidentAlien’s description, I suspect there maybe some incompatibility problem.

     

    You can try to install a full version of Window Server 2008 and use the command to test whether the same issue persists. If possible, please install Windows 2008 Server Core on another computer to test whether the same issue occue.

     

     

    Best regards,

    Vincent Hu

    Wednesday, March 4, 2009 1:40 AM
    Moderator
  •  I have used those commands, a fresh install of core everything works ok, but i am confused as to why its only the onboard NIC that cannot be re-enabled. the Pci-e nic ports were diabled at the same time as the secondary on-board nic and those were able to be re-enabled without any issue whatsoever, we have tried to install the latest drivers via pnputil didn't work, it would be nice if we had the ability to removed the nics from device manager, so it would be nice if we could remotely manage devices(not read only mode).

    i dont think rebuilding a box should be an option, one other complaint is that if you rebuild a Hyper-v, u best either make sure you exported the VM's or migrated them to another box, because they cannot be re-imported.

    Jeromey
    Wednesday, March 4, 2009 2:38 PM
  • Have you tried using devcon.exe yet to remove the drivers so that it can re-install the adapters? This tool was a lifesaver with some NICS that didn't automatically unbind the Hyper-V switch binding. the tool really isn't much fun to use, but its did work for me.
    Wednesday, March 4, 2009 5:22 PM
  • Yes i just tried that, everything i do wether its Restart, remove, enable, disable, they all say no devices removed or restarted depending on the command that i ran.


    Jeromey
    Wednesday, March 4, 2009 6:13 PM
  • Are you sure you have got the right command - it takes quite a lot of attempts to ensure you are removing the right device or any device at all). It took a while to find the right device ID or device ID with wildcard. Annoyingly I don't have an example anymore.
    Wednesday, March 4, 2009 6:42 PM
  • here is my status, i have no broken the PCIe adapters as well. the first device that is disabled is the problem child. 

    C:\patch\BC>devcon status =net
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500
        Name: HP NC373i Multifunction Gigabit Server Adapter
        Device is disabled.
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&323FB026&0&20050300
        Name: HP NC373i Multifunction Gigabit Server Adapter #2
        Driver is running.
    PCI\VEN_8086&DEV_105E&SUBSYS_7044103C&REV_06\6&3875998F&0&00000010
        Name: HP NC360T PCIe DP Gigabit Server Adapter
        Device has a problem: 19.
    PCI\VEN_8086&DEV_105E&SUBSYS_7044103C&REV_06\6&3875998F&0&01000010
        Name: HP NC360T PCIe DP Gigabit Server Adapter #2
        Device has a problem: 19.

    this is what i have been trying are these commands

    C:\patch\BC>devcon remove "B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&24
    9B009F&0&20050500"
    No devices removed.

    C:\patch\BC>devcon restart "B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&2
    49B009F&0&20050500"
    No devices restarted.

    C:\patch\BC>devcon disable "B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&2
    49B009F&0&20050500"
    No devices disabled.

    C:\patch\BC>devcon enable "B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&24
    9B009F&0&20050500"
    No devices enabled.

    thanks
    Jeromey
    Wednesday, March 4, 2009 7:38 PM
  • The problem is that it won't be able to find that device with the below command:

    devcon remove "B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500"


    Don't ask me why, but it won't - I went through this process and it doesn't make any sense.

    Now I had a problem with 2 NICs - so I could afford for both of them to uninstalled.

    I would suggesting trying a couple of things:

    1). Use a command that isn't likely to break anything (I think there is a display or list command) - because its likely you can remove a lot of devices if your command isn't correct.
    2). Then try using wildcards or stripping the device string.

    i.e. *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500*
    or  *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*

    I will see if I have the command I used anywhere - might be on the servers c:\ drive somewhere...

    It took a lot of trial and error.
    Wednesday, March 4, 2009 7:51 PM
  • here is i have gotten

    C:\patch\BC>devcon remove *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0
    &20050500*
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500: Remove f
    ailed
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&323FB026&0&20050300: Remove f
    ailed
    No devices removed.
    'PCI_164C14E4' is not recognized as an internal or external command,
    operable program or batch file.
    'SUBSYS_7038103C' is not recognized as an internal or external command,
    operable program or batch file.
    The system cannot find the path specified.
    '249B009F' is not recognized as an internal or external command,
    operable program or batch file.
    '0' is not recognized as an internal or external command,
    operable program or batch file.
    '20050500*' is not recognized as an internal or external command,
    operable program or batch file.

    C:\patch\BC>devcon list *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*
    devcon Usage: devcon [-r] [-m:\\<machine>] <command> [<arg>...]
    For more information type: devcon help
    'PCI_164C14E4' is not recognized as an internal or external command,
    operable program or batch file.
    'SUBSYS_7038103C' is not recognized as an internal or external command,
    operable program or batch file.
    'REV_12\*' is not recognized as an internal or external command,
    operable program or batch file.

    C:\patch\BC>devcon status *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500
        Name: HP NC373i Multifunction Gigabit Server Adapter
        Device is disabled.
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&323FB026&0&20050300
        Name: HP NC373i Multifunction Gigabit Server Adapter #2
        Driver is running.
    2 matching device(s) found.
    'PCI_164C14E4' is not recognized as an internal or external command,
    operable program or batch file.
    'SUBSYS_7038103C' is not recognized as an internal or external command,
    operable program or batch file.
    'REV_12\*' is not recognized as an internal or external command,
    operable program or batch file.

    C:\patch\BC>devcon remove  "*L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*"
    No devices removed.

    C:\patch\BC>devcon remove  *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500: Remove f
    ailed
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&323FB026&0&20050300: Remove f
    ailed
    No devices removed.
    'PCI_164C14E4' is not recognized as an internal or external command,
    operable program or batch file.
    'SUBSYS_7038103C' is not recognized as an internal or external command,
    operable program or batch file.
    'REV_12\*' is not recognized as an internal or external command,
    operable program or batch file.

    C:\patch\BC>devcon remove *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500: Remove f
    ailed
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&323FB026&0&20050300: Remove f
    ailed
    No devices removed.
    'PCI_164C14E4' is not recognized as an internal or external command,
    operable program or batch file.
    'SUBSYS_7038103C' is not recognized as an internal or external command,
    operable program or batch file.
    'REV_12\*' is not recognized as an internal or external command,
    operable program or batch file.

    C:\patch\BC>devcon restart *L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\*
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&249B009F&0&20050500: Restart
    failed
    B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12\6&323FB026&0&20050300: Restart
    failed
    No devices restarted.
    'PCI_164C14E4' is not recognized as an internal or external command,
    operable program or batch file.
    'SUBSYS_7038103C' is not recognized as an internal or external command,
    operable program or batch file.
    'REV_12\*' is not recognized as an internal or external command,
    operable program or batch file.

    C:\patch\BC>

    Wednesday, March 4, 2009 7:57 PM
  • Hi,

     

    I recommend that you contact HP for more information about the compatibility of HP DL380 with Windows Server 2008.

     

    I found a post on HP’s website, it said DL380G4 does not support Hyper-V. So please make sure your server is compatible with Windows Server 2008. Thanks for your understanding.

     

    DL380 G4 and Hyper V

    http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1236243136702+28353475&threadId=1317207

     

     

    Best regards,

    Vincent Hu

    Thursday, March 5, 2009 11:30 AM
    Moderator
  • We are using a DL380G5 not G4, these are comptabile with hyper-v because we are running hyper-v on these systems. we have 5 of them running.

    Jeromey
    Thursday, March 5, 2009 2:33 PM
  • I think some of us are missing the point.  Forget that Hyper-v is installed.  How do I determine the error that is preventing the NIC's from being enabled?  There is no error, nothing in the event logs, so what is one to do?

    I would assume that an easy way try and resolve the issue would be to remove and re-install the NIC's.  Why does that simple task seem to be impossible in Core?  Sure you can delete the NIC dirvers via "sc delete" but good luck re-installing them.  Everything I did left me with missing Interfaces and thus I was forced to re-install Core.

    So does anyone know how to remove a device from decive manager and re-add it?

    SC delete "drivername"  (worked great), but nothing adds them back.  Not installing the driver either from the PSP or pnputil -i -a <driverinf>.

    I believe that the issue for me revolves around the hardware.  I broke a few NIC's the other day playing with their IRQ settings in the BIOS.  Even after setting them back exactly I was never able to enable them again.  So I believe my fix would be related to re-installing the interfaces.





    Thursday, March 5, 2009 6:21 PM
  • Yes - devcon.exe does work if you can get the command correct - annoyingly I can't find my example - I deleted the text file off the server. Once you've used the tool you can reboot and it will re-install the adapter.

    As I said though, getting the command correct is a nightare. Without trying it again on the server I can't help with the syntax much more I am afraid.
    Thursday, March 5, 2009 6:25 PM
  • Ok here is a good one for you...

    Devcon has 2 versions as far as I can tell.  Devcon 32 bit and Devcon 64 bit for Itanium processors.  Devcon 32 bit will run on an intel 64 bit (non-Itanium) system but does not work very well.

    From MS:

    I386\DevCon.exe32-bit DevCon tool binary. This will not function completely on 64-bit Windows.
    Ia64\DevCon.exe64-bit DevCon tool binary.


    So what in the hell are you supposed to use on a CORE 64 bit (non-Itanium) Intel system?

    This explains why every command other than status or find results in a fail.  Is there a secret place you can download a 64 bit intel version of devcon.exe?  If not is there a secret command that allows you to actually manage your devices in Core?  Other then editing the registry.
    Thursday, March 5, 2009 9:10 PM
  • ***Update***

    I have installed the latest WDK from MSDN and low and behold there is a amd64 version of the devcon tool.  That version of the tool ran and successfully removed my troubled interfaces.  After a reboot they were all re-installed and fully functional.

    So I believe that my problem was related to hardware changes that for some reason required a re-install of the NIC's.  Thank goodness I found a working version of Devcon.

    Thanks.
    • Marked as answer by hothondaguy Thursday, March 5, 2009 10:25 PM
    Thursday, March 5, 2009 10:22 PM
  • Glad you got it sorted.

    As I said in my previous post a working x64 version (amd64) can be found on an XP x64 installation CD.
    Friday, March 6, 2009 8:38 AM