{"id":1063,"date":"2010-09-13T20:07:54","date_gmt":"2010-09-14T01:07:54","guid":{"rendered":"http:\/\/www.jasemccarty.com\/blog\/?p=1063"},"modified":"2010-09-13T20:07:54","modified_gmt":"2010-09-14T01:07:54","slug":"hey-guys-why-does-this-vm-have-3-nics","status":"publish","type":"post","link":"https:\/\/www.jasemccarty.com\/blog\/hey-guys-why-does-this-vm-have-3-nics\/","title":{"rendered":"Hey guys, why does this VM have 3 NICs?"},"content":{"rendered":"<p>Virtualization, as many say, is a journey.\u00a0 Some people are well down the path, while others are still beginning to understand how it works.\u00a0 This post is about a situation I recently came across where I had help with the understanding of how things really work.<\/p>\n<p><strong>The Situation<\/strong><br \/>\nI was performing some routine maintenance on some ESX hosts and some VM&#8217;s at one of my many jobs and noticed something a little strange.<\/p>\n<p>Several of the guests had more NICs listed in the guest than vCenter reported. I took a closer look, and I couldn&#8217;t believe my eyes.\u00a0 One of the other admins had configured teamed NICs. Keep in mind, that these guests only utilized a single IP address, without any type of multi-homed configuration.<\/p>\n<p>I thought to myself, &#8220;<em>Teamed NICs, in a VM?<\/em>&#8221; How could this be? Using VMware since Workstation 1.0, I had never seen teamed NICs inside the VM.<\/p>\n<p>I had to pose the question &#8220;<em>Why do we need teamed NIC&#8217;s in a VM?<\/em>&#8221;<\/p>\n<p>I got a very quick response of &#8220;<em>For redundancy.<\/em>&#8221;\u00a0 This response was said with a sense of authority and direction.<\/p>\n<p><strong>NIC Teaming<\/strong><br \/>\nNIC teaming is handled by software provided by the NIC vendor, and is typically used to make two (or more) NICs appear as a single NIC.<\/p>\n<p>For those familiar with VMware products, often times the NIC used in a VM, is a VMware Accelerated NIC.\u00a0 I wasn&#8217;t aware of any software that could do this with the VMware Accelerated NIC.\u00a0 Upon further examination, the VM&#8217;s were configured to use the Intel e1000 NIC, rather than the VMware Accelerated NIC.<\/p>\n<p><a href=\"http:\/\/www.jasemccarty.com\/blog\/wp-content\/uploads\/2010\/09\/PROWIN32.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1067 alignleft\" title=\"PROWIN32\" src=\"http:\/\/www.jasemccarty.com\/blog\/wp-content\/uploads\/2010\/09\/PROWIN32.png\" alt=\"\" width=\"95\" height=\"94\" \/><\/a>After further investigation I found that the admin had downloaded the Intel e1000 NIC drivers, along with the teaming software, from Intel.\u00a0 This software package provided the ability to team the two NICs.\u00a0 That&#8217;s why the VM reported 3 NICs (2 e1000 + the Team).<\/p>\n<p>Why did the admin team the NICs, <strong>redundancy<\/strong> was the answer.\u00a0 This was because in the traditional physical server configuration, physical NICs were always teamed in this environment, with each NIC connected to a different switch. What was missed, was that the physical NICs were already redundant at the vSwitch level.<\/p>\n<p><strong> <\/strong>In explaining how the vSphere configuration works, we all agreed that it wasn&#8217;t necessary to team NICs inside a VM in our configuration.<\/p>\n<p><strong>Further Discussion?<\/strong><br \/>\nAre there any configurations that you can think of where teamed NICs would be needed?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Virtualization, as many say, is a journey.\u00a0 Some people are well down the path, while others are still beginning to understand how it works.\u00a0 This &hellip; <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[34,103,105,111],"class_list":["post-1063","post","type-post","status-publish","format-standard","hentry","category-virtualization","tag-e1000","tag-vm","tag-vmware","tag-vsphere"],"_links":{"self":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/1063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/comments?post=1063"}],"version-history":[{"count":0,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/posts\/1063\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/media?parent=1063"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/categories?post=1063"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jasemccarty.com\/blog\/wp-json\/wp\/v2\/tags?post=1063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}