This nic or that nic?


When getting your head around networking in HyperV the first time, I find it helpful if your network cards are different manufacturers.  Now in real life this is nearly impossible as the Quad card on most servers means all 4 are the same name.  That said as others have pointed out, even on a production box you can throw in a more generic network card for the management role so you can more easily know which nic is which.


And do you have iLos or Drac cards too?  Even the HP microserver comes with the ability to purchase a $80 remote access card to the hardware.  This is a card that will let you get to the base hardware even if the OS doesn’t boot.

3 Thoughts on “This nic or that nic?

  1. Another alternative for iLo/Drac is intel vPro.

    It’s intended for workstations, but I’m not sure why, because for small/cheap servers, it’s a godsend. It does a lot of what e.g. iLo does as well (remote KVM, remote virtual CD/DVD/Floppy mount, remote poweron/-off/reset, etc), but to use it, you only need a motherbord with in Intel Q-series chipset (which are about ~$10-$15 more expensive than their cheaper counterparts) and a compatible cpu (which in current generation is a core i5).

    This means that you can build a cheap SBS server, or storage server (one in which it’s ok to use some consumer components) which you can remotely control, remote install the OS even, pretty much as if it had the expensive server-grade OOB management cards in them :)

  2. Kenneth Westergaard on May 31, 2012 at 5:33 am said:

    Personally I always just unplug each card in turn and name it accordingly to their physical placement.
    Ie.
    onboard nic port 2
    external nic port 1
    external nic port 2

  3. Joe Raby on May 31, 2012 at 1:37 pm said:

    Me too!

    I would use shortened names though, like “LAN1″, “LAN2″, etc. I find that sometimes they aren’t numbered the same way on the mobo label as they when Windows enumerates the controllers, which is just asinine.

Post Navigation