Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 2      Prev   1   2
cj_berlin

Avatar / Picture

Senior Member
Registered:
Posts: 244
Reply with quote  #16 
Curt,

NIC teaming works on layer 2 so you get ONE interface per team presented to the OS and just treat it as a single card.

Having multiple independent NICs plugged into the same switch doesn't usually make much sense, except in a virtualization host scenario where the NICs do not have IP config attached to them.

__________________
Evgenij Smirnov

My personal blog (German): http://www.it-pro-berlin.de/
My stuff on PSGallery: https://www.powershellgallery.com/profiles/it-pro-berlin.de/
0
nikolas.e

Senior Member
Registered:
Posts: 140
Reply with quote  #17 
Evgenij thank you so much for the information.

Example :

Server with one "quad port nic card". Before promoting the server to a domain controller i am going to setup nic teaming on my "quad port nic"

2 Ports will be active
1 Port will be standby


Guys sorry for asking to much and becoming boring but i need to verify this.

A Server with one NIC that has 4 Ports(Quad Port NIC) is exactly the same thing as other Server that has 4 Different NIC on it. Correct? I should treat it as the same thing and setup my nic teaming on a quad port nic with out worries.

Reply to me that i am correct  and that will make my day. [smile]







__________________
Just call me the 1000Questionsguy
0
cj_berlin

Avatar / Picture

Senior Member
Registered:
Posts: 244
Reply with quote  #18 
Yes, from the teaming point of view, a port is a port, the internal workings of the hardware don't matter. From the redundancy point of view, however, it's different: If a quad port NIC fails, four ports fail. If you have two dual port NICs and one card fails, you only lose two ports.
__________________
Evgenij Smirnov

My personal blog (German): http://www.it-pro-berlin.de/
My stuff on PSGallery: https://www.powershellgallery.com/profiles/it-pro-berlin.de/
0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 219
Reply with quote  #19 
  • I hope that Mark will cover some of this in his 2016 talk at Techextravaganza in Aug. in Atlanta.

    So for my clarity:
  • A four point NIC could be a point of failure.
  • Two or even 4 dual port NICs with Teaming provides better Layer 2 redundancy.
  • Teaming does not impede data transfer.

Now, at a few data centers when I dealt with more hardware, we installed a NIC for hardware monitoring.   But I forgot how that worked.  I have seen how some techs deploy server monitoring through the same NIC that the application uses and the system either performed poorly or was just overwhelmed by all the polling.  

As we all know there is a tendency to blame the application.  I deal more with the cloud now but I also have clients who have hosted systems.  In the past I have dealt with Techs managing the hosted systems of their clients and I was often disappointed in their troubleshooting abilities.  

Has anyone had virtual NIC issues with host systems using teaming on the physical layer?


__________________
Curt Spanburgh
0
nikolas.e

Senior Member
Registered:
Posts: 140
Reply with quote  #20 
Quote:
Originally Posted by cj_berlin
Yes, from the teaming point of view, a port is a port, the internal workings of the hardware don't matter. From the redundancy point of view, however, it's different: If a quad port NIC fails, four ports fail. If you have two dual port NICs and one card fails, you only lose two ports.



Thank you so much for your answer. Now its more clear to me. 

__________________
Just call me the 1000Questionsguy
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.