groups of ports (number of network cards)

Similar Questions

• ESX, number of network cards, NETIOC or traditional approach

  Hi all

  I have a question of design on the network of an ESX environment configuration.

  In short, we must decide how many cards per server, we need.

  It's an ESX cluster for a Cloud Computing environment (hosting).

  I told my boss about 8 cards per server would be appropriate (4-port ethernet cards).

  He said, however, that I am crazy in the coconut with so many NICs per host,

  because of the complex network management / wiring.

  and said that the 2 network cards should be sufficient, or maximum 4.

  We don't know yet if we'll use NETIOC or the traditional approach

  with multiple VSWITCHEs to separate the network flow.

  That's what I had in mind when using no NETIOC:

  THE VM NETWORK:

  VSWITCH1 - ETH0 (active) = physical NIC 0_port0

  Eth1 (at rest) = physical NIC 1_port0

  VMOTION NETWORK:

  VSWITCH2 - ETH2 (active) = physical NIC 0_port1

  Eth3 (at rest) = physical NIC 1_port1

  IP STORAGE NETWORK:

  VSWITCH3 - ETH4 (active) = physical NIC 2_port0

  (Passive) ETH5 = physical NIC 3_port0

  NETWORK FAULT TOLERANCE:

  VSWITCH4 - ETH6 (active) = physical NIC 2_port1

  (Passive) ETH7 = physical NIC 3_port1

  Is it really that crazy to have 8 adapters per ESX host?

  If so, the 6 is acceptable?

  I think 6 would work if we combine vmotion and storage over IP on the same VSWITCH,

  or tolerance vmotion and the fault on the same VSWITCH.

  He thinks that 4 is an absolute minimum.

  Somehow, I don't think it's a good idea to combine the vmotion/ipstorage/and fault tolerance

  on the same network adapter. I think that if we get only 4 adapters for each host.

  We forget storage over IP and keep all related storage

  connected with Fibre Channel.

  But maybe I am too greedy-NIC here?

  Currently, we do not fault tolerance

  but I think that there is a demand for it in the future.

  It is, therefore, may be an exaggeration to allocate separate physical maps to do this.

  It might be better to combine it with the flow VMOTION?

  That's what I had in mind when using NETIOC:

  1 virtual switch, whose actions for the load balancing,

  and with the load database grouping enabled.

  SHARING OF NETWORK FLOWS:

  VMOTION 20 |  VSWITCH1 | eth0_ACTIVE

  MGMT 10 |                         | eth1_ACTIVE

  NFS 20 |                         | eth2_ACTIVE

  FT                  10  |                         | eth3_ACTIVE

  VM                 40  |                         | eth4_ACTIVE

  |                         | eth5_ACTIVE

  |                         | eth6_STANDBY

  |                         | eth7_STANDBY

  It may take a higher share for NFS valuie.

  We don't know yet what kind of goal, NFS data warehouses will be used.

  There will also be Fibre Channel connected to data warehouses.

  In the NETIOC scenario, if 8 physical NIC are really too much, I guess we could

  do with 6

  But 6 also seems to be a minimum in this situation for me,

  or can come out us with 4?

  Also, about NETIOC, given that this kind of thing is still pretty new (since 4.1),

  anyone here have experience with the new NETIOC feature on

  a distributed switch?

  I would get at least 6 cards per server,

  better one or two network cards too much that you do not use at the beginning.

  but have the option to use, at least be blocked eventually.

  not being able to implement a feature (for example. Fault tolerance)

  because you have no free NIC more.

  Or otherwise, they should just go with 2x10GB NIC,.

  and distribute the stream with NETIOC.

  It would greatly simplify cabling and management.,.

  and give more bandwidth

  Well...

  Any input would be greatly appreciated.

  Concerning best practices, you will need 8-

  vMotion and your management network (you had left it) can share a pare - woth the pair configured active / standby management and standby/active for vMotion - FT, VM Network and Sotrage IP network should all be insulated and redundnat - depending on your load I/O that you can condense up to four network adapters with FT/VMs and storage over IP sharing the same NIC but on different VLAN -

• How to list all the vm with more than one network card?

  Hello

  Is it possible to only list all my s vm in my environment with more than one network card?

  I tried using the Get-NetowrkAdapter cmdlet, but could not get the desired results.

  Get - VM | Get-NetworkAdapter | Select-Object Name. ConvertTo-HTML-head $a - body "Virtual Machines < H2 > < / H2 > ' | Out-file D:\vms.htm

  Thank you

  Hello, AGFlora-

  Of course, you can do this with the standard as cmdlets:

  ## using standard cmdletsGet-VM | Select Name, @{n="NumNICs"; e={(Get-NetworkAdapter -VM $_ | Measure-Object).Count}} | ?{$_.NumNICs -gt 1}
  

  Or, if you want to get the results a little (or a lot) more quickly, you can use the cmdlet Get-view as:

  ## fast-like, using Get-ViewGet-View -ViewType VirtualMachine -Property Name,Config.Hardware.Device | Select Name,@{n="NumNICs"; e={($_.Config.Hardware.Device | ?{$_ -is [VMware.Vim.VirtualEthernetCard]} | Measure-Object).Count}} | ?{$_.NumNICs -gt 1}
  

  Those are both by selecting the names of virtual machines and their number of network cards.  Then you can direct this output to Export-Csv, ConvertTo-HTML, what you like.  What to do for you?

• Routing between two network cards

  I have 8 fiber switches that are configured to use a private network for management.

  The subnet is 192.168.8.0/24.

  I have a W2K3 (SERVER A) server with two NICS, a NIC (192.168.8.1) is attached to

  the 192.168.8.0 subnet and the other (192.168.100.14) NETWORK adapter is attached to the subnet 192.168.100.0/24.

  I put up two persistent routes of road between these NICS using the following commands:

  Pei route add 192.168.8.0 mask 255.255.255.0 192.168.100.14

  Pei route add 192.168.100.0 mask 255.255.255.0 192.168.8.1

  I have an other W2K3 server (SERVER B) with a single NETWORK (192.168.100.12) card that must be able

  to connect with the fiber switches via tcp/ip. Packets should be routed to this server.

  On that I put in place a permanent route:

  Pei route add 192.168.8.0 mask 255.255.255.0 192.168.100.14

  Everything works very well.

  (Assumes that the SERVER-A and SERVER B are now turned off)

  I'm trying to reproduce this on my VMware ESX Server 3.5upd3.

  ESX server has two NICS, one attached to each of the subnets. I create a virtual machine to replace SERVER-a

  with the same number of network cards and the same IP addresses.

  I then create routes as follows:

  Pei route add 192.168.8.0 mask 255.255.255.0 192.168.100.14

  Pei route add 192.168.100.0 mask 255.255.255.0 192.168.8.1

  PROBLEM: as soon as I add the second route I can no longer ping any server on the 192.168.100.0 subnet.

  This also causes connections to last very long.

  Do I need to implement routing between network adapters ESX scale to make this work?

  If so maybe want the command look like? If not, what could be my problem?

  Thank you for the helpful answers

  If you want to configure your machine as a router, you will need to notify the router is the next hop.  Now, the next machine break is its own interfaces, which will not work.  And since you are running some sort of routing protocol, provide two solutions to exit the server is not a good idea, because he doesn't know that one to use.  It will use 1 for some and another for some.

  Do what you intend (or I think you intend), you must delete the static routes and choose a default route, which will be your next jump.  This should be another router in your environment.  Then, the other servers that you want to route via ServerA, ServerA interface on this segment would remind you.

  Hope that makes sense.

  -KjB

• Number of groups of ports and VLANs by vSwitch

  Hi all

  I'm looking for any insight or best practices in what concerns the number of VLANs that are ongoing to shared resources on a vSwitch.  Our ESX servers, there are 6 physical network adapters associated with (using the property intellectual hash).  These cards are the uplinks to the vSwitch which provides the virtual machine networks.   We use VLAN Tagging (VST) and created groups of ports for each Vlan ID.  Until now, we have about 7 groups of ports for 7 different VLAN.     I know the max is 512, but are there aspects to add several groups / VLAN port that I'm missing?  (We use vSphere 4.1)

  Thank you...

  Groups of ports by vCenter limit is 5000, but you do not sound as it reaches.

  Really, for the number, you have (7) you are a pretty small network as much as standard implementations are going, and you'll be fine.

  I don't think it is interesting to look at if you really expect to be using all six ports - it is rare for aggregation in order to get increases in actual performance beyond two, and often 'more' is not better.

  LACP changes things a bit, but it does not apply to many environments.

• iDRAC 7 express, grouping of network cards

  Hello

  I can't access iDRAC when the grouping of NETWORK cards is configured. Is it according to the design guidelines? There is no work around for this?

  #idrac7express #NICteaming  

  Hello.

  Yes, it's normal. IDRAC Express does NOT use a NETWORK card dedicated for remote access, but rather use a LAN on motherboard (LOM) as a shared port. Now, once you have Teaming on the LOM ports, then the iDRAC Express cannot share all the ports with the team. The solution is to upgrade to iDRAC Enterprise that uses another port dedicated team card NETWORK for management traffic. See page 4 of the link: downloads.dell.com/.../integrated-dell-remote-access-cntrllr-7-v1.30.30_Setup%20Guide_en-us.pdf;. l = en & cs = 555 & s = biz

• Grouping of NETWORK cards

  Hello

  I am new to virtualization and have a basic question about the collection of NETWORK adapters. I have a host with a NETWORK card with 2 ports (vmnic0 and vmnic1). I have a network cable connected to vmnic0 and vmnic1 is open without any network connection to the outside world. Can I use grouping of NETWORK cards in this case? Or both network adapters must be connected to the network for NIC teaming to work?

  You can certainly configure everything as if the two vmnic was active. However, with a single uplink connected to a physical switch, it may not make much sense.

  André

• Grouping of NETWORK cards causing the ESXi to retransmit ethernet frames received.

  I had an HP Proliant DL380 G5 ESXi 5.1.0 connected to a Cisco 3750 Switch stack.

  All by performing a tcpdump on a host without a report, I discovered that he was under the bombardment with ethernet frames for the MAC address of a computer virtual located on a host across the data center. After a few brief troubleshooting, I discovered that I was able to stop those erroneous frames by disabling NETWORK adapters on my VMWare host group.
  
  I believe that in my situation when ESXi is configured to use two network cards to all frames received on vmnic0 and retransmits them on vmnic1 and vice-vesa. I experienced these symptoms when ESXi is configured for failover with an active adapter and adapter mode standby and I also experienced the same symptoms in the following load balancing configuration.
  

  
  

  Symptoms: some time after activating the load balancing, all frames Ethernet for the MAC address of a virtual computer on the affected host are broadcast on each switch port in the entire data center.
  
  Steps to reproduce:
  (1) implementation below configuration.
  (2) unplug the ethernet cable connecting vmnic1 and switch1 port gi2/0/4
  (3) run the host 1.1.1.1 EI - n - q tcpdump on any machine physics linux in the data center (don't even have to be connected directly to 1).
  Confirm there is no packet seen with the IP address of 1.1.1.1 destination
  (4) plug the cable between vmnic1 and switch1 gi2/0/4 port ethernet
  (5) wait 60 to 120 seconds
  (6) watch a burst of frames ethernet with the destination MAC address of the VM (which owns 1.1.1.1) in the output of tcpdump

  Cisco Configuration:

  hostname switch1
  !
  src-dst-ip port-channel load-balance

  !

  interface GigabitEthernet1/0/4

  Description vmnic0.host0 (NIC 1)

  switchport trunk encapsulation dot1q

  switchport mode trunk

  channel-group mode 4 on

  spanning tree portfast trunk

  end

  !

  interface GigabitEthernet2/0/4

  Description vmnic1.host0 (NIC 2)

  switchport trunk encapsulation dot1q

  switchport mode trunk

  channel-group mode 4 on

  spanning tree portfast trunk

  end

  !

  Interface Port-Channel 4

  Host0 description

  switchport trunk encapsulation dot1q

  switchport mode trunk

  spanning tree portfast trunk

  end

  
  Configuration of ESXi
  vSwitch0

  Grouping of NETWORK cards / Load Balancing: route based on IP Hash
  Grouping of NETWORK cards / failover detection network: link status only
  Grouping of NETWORK cards / notify switches: Yes
  NIC Teaming / relief: Yes
  Grouping of NETWORK cards / adapters active: vmnic0, vmnic1
  NIC Teaming / standby adapters: nothingness
  NIC adapters grouping / unused: nothingness
  Security / Promiscious Mode: reject

  Security / MAC address changes: accept
  Security / forged passes: accept

  
  #1 Virtual Machine port group
  Network label: 'Public '.

  VLAN: 27
  Grouping of NETWORK cards: all unchecked (inherited)

  #2 Virtual Machine port group
  Network label: "trunk".
  VLAN: 4095
  Grouping of NETWORK cards: all unchecked (inherited)

  VM kernel Port #1
  Network label: 'management '.
  VLAN: 2

  Grouping of NETWORK cards: all unchecked (inherited)

  VM #1
  

  OS: Windows Server 2003
  NIC 1 / adapter: Flexible
  NIC 1 / network Label: 'Public '.

  IP address: 1.1.1.1/24

  I apologize for the delay in my response.

  Unplug physically 2 cable NETWORK card on the host and configuration mirrored port on the switchport to 1 NETWORK adapter of the host, I have been able to confirm that the host VMWare issues guides on NIC1 with a destination MAC address of one of its own VM.

  After carefully reviewing the captured data, I noticed that the destination frames wrong "02:bf:cb:50:a2:76" MAC address actually belonged to "Local Area Connection 1' one of my Windows 2003 Server WHAT VM installed on the suspected host.

  Dig a little deeper, I discovered that this virtual NETWORK card is presented to the operating system as
  Name: Local 1 network connection
  "Type: VMware Accelerated AMD PCNet adapt."
  MAC: 02-BF-CB-50-A2-76

  But the configuration of the virtual machine in vCentre is
  Name: Network adapter 1
  Type: Flexible
  MAC: 00: 0C: 29:fa:e8:83

  Note the different MAC addresses.

  Digging a little further I discovered that Windows 2003 server has configured on "Local 1 network connection" network load balancing and NLB is the cause of the altered MAC address.

  Rather than to investigate further I have just placed a load balancer linux before the server windows 2003 cluster and that you turn off NLB.

  But I suspect that there is still a fundamental problem in the Virtual Switch VMware with how he learns the MAC addresses of the virtual machine is using flexible vNIC. In particular, with a virtual machine that uses a form to override the MAC address such as that used by NLB.

• Failed to create FT logging with grouping of NETWORK cards

  I use vSphere vCenter 5.1 and 5.1.

  I create a port group of kernel VM on a new vSwitch, assign two NICs used on my ESX Server and logging FT. I have then add a second port VM kernel group to the two network cards and also assign FT logging. When I do this FT Logging the first port of kernel VM group is disabled. If I then manually enable FT gones then a second by logging on the first group of ports of kernel VM mode off.

  The same thing happens when I create 2 vSwitches, assign 1 NIC to each of them and assign the FT logging.

  I wanted to create my FT Logging predisposees in this way to match what I've done with vMotion and VM Network.

  I do something wrong or you can have a group of ports per server for recording of FT? Please notify.

  Thank you

  Multi-NIC VMotion is a new feature in vSphere 5.0. Multi-NIC FT has not yet been introduced. You mentioned trade Multi-NIC VM, but it is not possible either. While you can have two interchanges to connect to the same VLAN they must have unique names and a VM NIC may connect only to a unique name.

  What advantage do you hope to achieve with Multi - NIC FT? If the goal is more throughput 10G is the only option currently. If the lens is better traffic load balancing so that you could watch LACP on the vDS.

• Tests... Grouping of NETWORK cards - based IP Hash

  Hello!

  I am configuring the NETWORK cards on my vSwitch grouping feature. I configured several ports in two physical switches (two HP Procurve 2810) (HP 2810 switches obtained haven´t etherchannel) LACP mode available. Right now, everything is Ok.

  So my question is: How can I test if the IP hash function works well, it is, connecting the same virtual machine with the help of several physical NIC according to computers ask server information?

  I thought about using "sniffer" or something like that. More ideas?

  PS: I tried to configure the collection of NETWORK adapters - Hash IP without configuration LACP in my physical switch and I noticed haven´t alarms or internal errors. May I take it that it works well?

  Thanks for all!

  With ESXTOP command you can see network load on each physical network adapter. Press N to see details on the network.

  I'm not familiar with the switches HP, but (like Cisco), it should be possible to see the counters on LACP or detailed statistics on your switch.

  If you do not use load balancing on your physical switch, all incoming traffic from the network of your virtual machine can come on one single network card.

• Best way to make the physical NETWORK card-&gt; vmnic number?

  Is there a known way to understand the link between the vmnic0, vmnic1... logical names and their relationship to physical network cards of ESX/ESXi? In other words, if you get on a new server with, say, 6 physical ports and a config on one vmnic, how do you know which translates to correct physics?

  The means that I can think of are:

  • Check the MAC address within vSphere Client, but then you must somehow know the MAC of the physical NETWORK adapter

  • check the number of PCI of vSphere Client, but this seems a bit difficult to understand?

  • fix pull cables and are looking for "plugged" or not.

  So, how do you do this, if necessary?

  In fact, it is quite easy to see which port on a teddy bear refers to things in the VMware environment...

  Look under configuring the host tab/Server/network element equipment adapters... This will show each NIC and what vmnic # are assigned to the ports. It will also show the MAC address of each port. If they are assigned to vSwitches, it will also show this info...

  

  You can also see the Networking section (still under the Configuration tab) to see the vmnic # assigned to each vSwitch...

  

  Multiport NIC generally have markings on the plate PCI to let you know which is which... All you really need to know is what is the beginning of numbering.

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• Grouping of network cards on the PowerEdge R320 and R720 servers

  Hello

  I have several R320 servers with quad port NIC broadcom. I would like to configure the collection of NETWORK adapters on the Server 2008 R2, but I couldn't find a download on the website of Dell application, could someone ' a please point me in the right direction.

  I also have a Dell server with Vmware Esxi 5.1 R720, is it possible to configure NETWORK cards on this grouping?

  Thank you

  Dan

  Guys,

  Is the possible consolidation of NETWORK cards? I would have thought that it is something that would be fairly simple with the right driver.

• Broadcom NetXtreme II 5709 quad port NETWORK card driver

  When I look at the Broadcom page for pilots for the NetXtreme II 5709 NIC, NIC is addressed isn't dual port quad-port. This driver is compatible with the version of four ports?

  In this case, I will get the latest version of the driver installed

  Not sure why you posted this in the forum of storage, but in general a quad port card is just two controllers dual port on a single physical card.   On the PCI bus, you see what appears to be four (or two on card dual port) individual network cards.  Although there are two ports on a single chip.

  I.e.

  # lspci | grep Broadcom

  02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI - X bridge (Rev. c3)

  03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)

  06:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI - X bridge (Rev. c3)

  07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12)

• vSphere replication - grouping of NETWORK cards

  We have a large virtual machine (60 to VMDK) we need to replicate to a second host.  We are currently receiving about 100 MB/s and it seems we're reached the limit of 1 GB.  I want to increase the bandwidth available for this large replication work by aggregating traffic through several nic is it possible?  If so, how?

  I tried the following approach, thinking that these operations can be based on the same transfer mechanism, but it has not made a difference.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & addresses...

  The KB points it is grouping of network cards that will help when you lost the active NIC then stand by will pass your tgraffic.

  Now coming to your scenario, you need to configure the user profile of the NIOC here you have to devote all the speed of the network to this replication job card. You cannot aggregate multiple Nic for reaching the combined capacity. We have a concept called LAG and LACP. but it will also give the speed that is independent to the different traffic

• Grouping of NETWORK cards reverse the policy

  When I apply a profile esxi 5.0 to 5.1 host, I got the following configuration message. any ideas?

  Hello

  This is mentioned in the 5.1 version of vSphere notes:

  Compliance policy network outages continue to host profiles created from applied guests 5.1 ESXi ESXi 4.1 or ESXi 4.0 hosts
  After you apply a profile created from an ESXi 4.1 or ESXi 4.0 host host to a 5.1, the failures of compliance profile next host ESXi host could continue:

  For the network policy for the Group [NAME of GROUP of PORT] port spec.policy.nicTeaming.failureCriteria property does not match
  For the network policy for the Group [NAME of GROUP of PORT] port spec.policy.nicTeaming.reversePolicy property does not match

  
  

  Network settings above are not supported on ESXi 5.1 hosts and are configured is more when you apply a host profile with these settings.

  Solution: Two options are available:

  • After applying host initially created from an ESXi 4.1 host to a host profile ESXi 5.1, create a new profile of the host from the host ESXi 5.1 and which attach to this 5.1 ESXi host and other affected 5.1 ESXi hosts.
  • Change the policy of grouping of NETWORK adapters in the profile of the host to the option user must explicitly choose political instead of the strategy of grouping NIC specified.

  Now I know IVotre profiles are at the origin of 5.0 but the thought to mention it anyway