Balancing on etherchannel

I'm trying to aggregate the 2 NIC physical rather than run in failover mode.

I changed the grouping of cards NETWORK load balancing for the Group vswitch and port to "from route of IP hash." With the switch etherchannel configured on 'static', I can ping the box from the VM, but I can't reach it with the switch on ' 802.11ad (LACP).» I've read elsewhere in the communities that ESXi 4 does not support LACP (but that it supports 802.11ad - are - they the same thing?). The only choice my switch offers for etherchannel is static or lacp. Which one should I use?

When you look in the configuration section, there is a situation of group vswitch alert notification both port that says 'the function of hash IP load balancing does not support physical cards in standby mode. Change all cards pending the status of the uplink. Where I would make this change?

Thanks for your time.

On the vSwitch properties. You can choose what uplinks will be active. The KB http://kb.vmware.com/kb/1004048 have very detailed information on this subject.

Marcelo Soares

VMWare Certified Professional 310/410

Master virtualization technology

Globant Argentina

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

Tags: VMware

Similar Questions

  • ESXi 4.1 and KS.cfg

    Hello

    I'm working on my KS.cfg file for a script of ESXi 4.1 installation. I was wondering about the command dryrun. I have this command at the top of my KS.cfg file. This create a log file or just spit the results on the screen? Mine doesn't seem to work. Here's my kickstart file. Any suggestions would be welcome, because this file can be a Booger to configure.

    KS.cfg

    dryrun

    password super rootpw secret

    install URLS http://10.x.x.x/ESXi

    Wings firstdisk - overwritevmfs

    reset

    #Network installation type

    network - bootproto = static - addvmportgroup = false - device = vmnic0 - ip = 10.x.x.x - netmask = 255.255.255.0 - gateway = 10.x.x.x - nameserver = 10.x.x.x - hostname = FQDN of the server

    AcceptEULA

    firstboot % - not supported - interpreter = busybox

    #Assign PortGroup management VIRTUAL local area network

    esxcfg-vswitch - v 10 - p 'Management' vSwitch0

    #Add vmnic1 Teddy to vSwitch0

    esxcfg-vswitch - L vmnic1 vSwitch0

    #Add new vSwitch for vMotion

    esxcfg-vswitch - a vSwitch1

    #Add vMotion Portgroup to vSwitch1

    esxcfg-vswitch - a vMotion vSwitch1

    #Add Teddy vmnic2 to vSwitch1

    esxcfg-vswitch - L vmnic2 vSwitch1

    #Add bear vmnic3 to vSwitch1

    esxcfg-vswitch - L vmnic3 vSwitch1

    IP vmknic vmk1 #Assign

    esxcfg-vmknic - a-i n 255.255.255.0 10.x.x.x Pei vMotion

    #Assign VLAN vMotion PortGroup

    esxcfg-vswitch - v 20 - p "vMotion" vSwitch1

    #Add new vSwitch for Virtual Machines

    esxcfg-vswitch - a vSwitch2

    #Add machine virtual Portgroup to vSwitch2

    esxcfg-vswitch - a network of VM vSwitch2

    #Add machine virtual Portgroup to vSwitch2

    esxcfg-vswitch - a DMZ vSwitch2

    #Add Teddy vmnic4 to vSwitch2

    esxcfg-vswitch - L vmnic4 vSwitch2

    #Add bear vmnic5 to vSwitch2

    esxcfg-vswitch - L vmnic5 vSwitch2

    #Assign VLAN for Machine virtual PortGroup

    esxcfg-vswitch - v - 30 p "The Virtual Machine Network" vSwitch2

    #Assign VLAN for Machine virtual PortGroup

    esxcfg-vswitch - v - 40 p "DMZ" vSwitch2

    Sleep 10

    #set vMotion for vmk

    Vim - cmd vmk1 vmotion/hostsvc/vnic_set

    Vim - cmd hostsvc/net/refreshment

    Sleep 10

    #Change balancer for Etherchannel-

    Vim - cmd hostsvc/net/vswitch_setpolicy-- nicteaming - political = loadbalance_ip vSwitch0

    Vim - cmd hostsvc/net/vswitch_setpolicy-- nicteaming - political = loadbalance_ip vSwitch1

    Vim - cmd hostsvc/net/vswitch_setpolicy-- nicteaming - political = loadbalance_ip vSwitch2

    #Set DNS

    Cat > /etc/resolv.conf < < EOF

    search domain.com

    10.x.x.x nameserver

    10.x.x.x nameserver

    1. Config of time NTP

    echo "Configuring NTP"

    restrict default kod nomodify notrap noquerynopeer echo > /etc/ntp.conf

    restrict the 127.0.0.1 echo > > /etc/ntp.conf

    0 ntp preliminary server echo > > /etc/ntp.conf

    driftfile/var/lib/ntp/drift echo > > /etc/ntp.conf

    / sbin/chkconfig--level 345 ntpd on

    /etc/init.d/ntpd stop

    /etc/init.d/ntpd start

    #enable SSH TechSupportMode

    Vim - cmd hostsvc/enable_remote_tsm

    Vim - cmd hostsvc/start_remote_tsm

    Vim - cmd hostsvc/net/refreshment

    Just the kickstart of the stanza dryrun analysis and valid syntax, and you should get a pop-up window indicating whether or not is it or if there were errors/warnings. Everything is recorded in /var/log/esxi_install.log that you can take a look at logging to the console by pressing alt + f1

    Here is a blog on ESXi 4.1 kickstart tips/tricks - http://www.virtuallyghetto.com/2010/09/automating-esxi-41-kickstart-tips.html

    =========================================================================

    William Lam

    VMware vExpert 2009,2010

    VMware VCP3, 4

    VMware VCAP4-DCA

    VMware scripts and resources at: http://www.virtuallyghetto.com/

    Twitter: @lamw

    repository scripts vGhetto

    Introduction to the vMA (tips/tricks)

    Getting started with vSphere SDK for Perl

    VMware Code Central - Scripts/code samples for developers and administrators

    VMware developer community

    If you find this information useful, please give points to "correct" or "useful".

  • 2 GB Cisco EtherChannel Cisco 3750 x 2960S

    Hello

    Im trying to configure an EtherChannel between my stack of 3750 and my stack of 2960S.

    I have 2 3750 x in the form of battery. (2 switches).

    I have 4 2960 s in the form of battery. (4 switches).

    I need to create a channel of 2 GB between them. My heart is the 3750 and my stack of 4 2960 s is on another floor, so I want to create a channel of 2 GB between them.

    I know that you can create a PO between them, but what I want to do is to create a channel of 2 GB between them that run at the same time, active on both ports of 1 GB.

    Is this possible and how? This is my current setup until now:

    Change the battery 3750

    Interface Port-channel10
    Description ETHSW04 - 1.5
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    spanning tree cost 15

    Interface Port-channel11
    Description of uplink BRP at ETHSW04 - 1.5
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    spanning tree cost 1

    interface GigabitEthernet1/0/39
    Description ETHSW04 uplink - 1.5
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-group 10

    interface GigabitEthernet1/0/40
    Description ETHSW04 uplink - 1.5
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-group 10

    interface GigabitEthernet2/0/39
    Description Uplink of BRP - uplink ETHSW04 - 1.5
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-Group 11

    interface GigabitEthernet2/0/40
    Description Uplink of BRP - uplink ETHSW04 - 1.5
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-Group 11

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

    Battery 2960 s

    Interface Port - Channel 1
    Description CORE01 uplink
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    spanning tree cost 15

    Interface Port-canal2
    Uplink BRP to CORE02 description
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    spanning tree cost 1

    interface GigabitEthernet1/0/47
    Description CORE1-G1/0/39
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-group 1

    interface GigabitEthernet1/0/48
    Description CORE1-G1/0/40
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-group 1

    interface GigabitEthernet4/0/47
    BRP-CORE2-G2/0/39 description
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    spanning tree portfast
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-group 2
    !
    interface GigabitEthernet4/0/48
    BRP-CORE2-G2/0/40 description
    switchport trunk allowed vlan 1,210,220,214,216,220,306,406
    switchport mode trunk
    added mac-SNMP trap notification change
    deleted mac-SNMP trap notification change
    spanning tree portfast
    loop of spanning tree guard
    channel-protocol lacp
    active in mode channel-group 2

    Thank you...

    Not possible AFAIK.
    LACP will provide examples of the use of load balancing and redundancy that is good enough for most.
    Other then that you would have to watch the 10GB uplinks between switches for more bandwidth.

  • The traffic is not correctly distributed through each link of etherchannel.

    Dear team,

    You can all have a clue on below.

    I have a cisco 3560 and created the port-channel switch and assign the port two to Po1 switch is connected to the HP VC.

    The question is highly uses a single port and on the other port no traffic is there.

    Please find below the config for your reference.

    Cisco 3560

    Switch1 #sh su etherchannel

    Flags: - Low P - D bundled in port-channel

    I have - autonomous s - suspended

    H Eve (LACP only)

    R - Layer 3 S - Layer2

    U - running f - cannot allocate an aggregator

    M - don't use, minimum contacts not satisfied

    u - unfit to tied selling

    w waiting to be aggregated

    d default port

    Number of channels in use: 4

    Number of aggregators: 4

    Protocol for the Port-Channel port group

    ------+-------------+-----------+-----------------------------------------------

    1 Po1 (SU) LACP Gi0/28 (P) Gi0/30 (P)

    2 Po2 (SU) - Gi0/22 (P) Gi0/23 (P) Gi0/24 (P)

    Gi0/25 (P) Gi0/26 (P) Gi0/27 (P)

    3 Po3 (SU) - Gi0/6 (P) Gi0/7 (P) Gi0/8 (P)

    Gi0/9 (P) Gi0/10 (P) Gi0/11 (P)

    4 (SU) Po4 - Gi0/1 (P) Gi0/14 (P)

    #sh Switch1 run int po1

    Building configuration...

    Current configuration: 166 bytes

    !

    Interface Port - Channel 1

    Description HP VC

    switchport trunk encapsulation dot1q

    switchport trunk allowed vlanXXXX

    switchport mode trunk

    end

    #sh Switch1 run int g0/28

    Building configuration...

    Current configuration: 223 bytes

    !

    interface GigabitEthernet0/28

    Server HP VC Description

    switchport trunk encapsulation dot1q

    switchport trunk allowed vlan XXXX

    switchport mode trunk

    channel-protocol lacp

    active in mode channel-group 1

    end

    #sh Switch1 run int g0/30

    Building configuration...

    Current configuration: 223 bytes

    !

    interface GigabitEthernet0/30

    Server HP VC Description

    switchport trunk encapsulation dot1q

    switchport trunk allowed vlan XXXX

    switchport mode trunk

    channel-protocol lacp

    active in mode channel-group 1

    end

    Switch1 #.

    Kind regards

    Prasad

    Disclaimer

    The author of this announcement offers the information in this publication without compensation and with the understanding of the reader that there is no implicit or explicit adequacy or adaptation to any purpose.  Information provided is for information purposes only and should not be interpreted as making the professional advice of any kind. Use information from this announcement is only at risk of the reader.

    RESPONSIBILITY

    Any author will be responsible for any damage that it (including, without limitation, damages for loss of use, data or profits) arising out of the use or inability to use the information in the view even if author has been advised of the possibility of such damages.

    Poster

     

    If you see a load imbalance to THE switch (i.e. from your server), then you should see if your server has any load balancing options like the switch has no control over this.

    If you see load imbalance OF switch (IE your server), then your need to select the best hash algorithm, for your traffic load balancing features.  Often by default of the switch is not the best.  Often using IP source and destination addresses works well.

    Sometimes, realize that the switch does not offer a good hash algorithm for your traffic for load balancing.  For example, if the majority of your traffic was between two hosts (replication, for example), all the traffic that would take the same link.  (Note: a hash of 6500 offers which includes port numbers for such situations, but not 3K switches.)

    This link http://www.cisco.com/c/en/us/support/docs/lan-switching/etherchannel/12023-4.html, explains your choices on different Cisco switches.

  • Slow EtherChannel?

    Hello

    I have 2x2950s and 2x3550s putting in place etherchannels between them. Everything looks ok, but the speed is always around 100 Mbps, even if there are a of the trunks 2xFE everywhere.

    I tried to isolate, connecting 2x2950s all - even, I get 100 Mbps max...

    My basic topology:

    PC with a NIC - 2950 GB - 2950 - PC with a Go

    Results of Iperf:

    [4] 172.16.1.144 local port 5001 connected with 172.16.1.28 port 51554

    [4] 0, 0 - dry 10.0 102 Mbps 85.4 MB

    [4] 172.16.1.144 local port 5001 connected with 172.16.1.28 port 51675

    [4] 0, 0 - dry 10.0 107 MB 89.3 Mbps

    I tried to change the PO/active - always the same ports. When I connect these PCs to the same 2950 switch using two gigabit ports, I get:

    [4] 0, 0 - dry 10.0 390 MB 327 Mbps

    I also tried to copy to PC3 to both PC1 and PC2, at the same time to ensure that she can balance the load - unfortunately I was getting 5-6 Mbps for each connection only

    I missed something obvious?

    My config and show the basic commands:

    SWITCH1

    #sh Switch1 run int po1

    Building configuration...

    Current configuration: 207 bytes

    !

    Interface Port - Channel 1

    ETHERCHANNEL description

    switchport vlan trunk native 2

    switchport trunk allowed vlan 1-4 991 002-1005

    switchport mode trunk

    switchport nonegotiate

    FlowControl send

    end

    #sh Switch1 run int f0/18

    Building configuration...

    Current configuration: 190 bytes

    !

    interface FastEthernet0/18

    switchport vlan trunk native 2

    switchport trunk allowed vlan 1-4 991 002-1005

    switchport mode trunk

    switchport nonegotiate

    active in mode channel-group 1

    end

    #sh Switch1 run int f0/19

    Building configuration...

    Current configuration: 190 bytes

    !

    interface FastEthernet0/19

    switchport vlan trunk native 2

    switchport trunk allowed vlan 1-4 991 002-1005

    switchport mode trunk

    switchport nonegotiate

    active in mode channel-group 1

    end

    Switch1 #sh ethe

    Switch1 #sh su etherchannel

    Switch1 #sh etherchannel summary

    Flags: D - low P - port-channel

    I have - autonomous s - suspended

    H Eve (LACP only)

    R - Layer 3 S - Layer2

    u - unfit to tied selling

    U - running f - cannot allocate an aggregator

    d default port

    Number of channels: 1

    Number of aggregators: 1

    Protocol for the Port-Channel port group

    ------+-------------+-----------+----------------------------------------------

    1 Po1 (SU) LACP Fa0/18 (P) Fa0/19 (Pd)

    Switch1 #sh int po1

    Port-channel 1 is up, line protocol is up (connected)

    Material is EtherChannel, address is 0009.43ae.ce13 (bia 0009.43ae.ce13)

    Description: ETHERCHANNEL

    MTU 1500 bytes, BW 200000 Kbit, DLY 1000 usec,

    reliability 255/255, txload 5/255, rxload 1/255

    Encapsulation ARPA, loopback not set

    Full-duplex, 100 MB/s, media type is the unknown media type

    input stream control is turned off, output flow control is disabled

    Members in this channel: Fa0/18 Fa0/19

    Type of the ARP: ARPA, ARP Timeout 04:00

    Last entry at 00:01:23, 00:00:00 exit, exit hang never

    Final cleaning of "show interface" counters never

    Input queue: 0/75/0/0 (size/max/drops/dumps); Total output drops: 0

    Strategy of queues: fifo

    Output queue: 0/40 (size/max)

    5 minute input rate 89000 bps, 172 packets/s

    5 minute output rate 4495000 bps, 354 packets/s

    2831392 package, 2669151653 bytes, 1056 no input buffer

    Received 36665 broadcasts (29399 multicast)

    0 Runts, 0 giants, 0 shifters

    entry 0, 0 CRC errors, frame 0, 0, saturation, ignored 1056

    Watchdog 0, multicast 29399, break 0 comments

    entry packets 0 with condition of dribble detected

    2885680 packets output, 3152464741 bytes, 0 underruns

    0 output errors, 0 collisions, 1 interface resets

    0 babbles, collision end 0, 0 deferred

    carrier, 0 no carrier, lost 0 0 output BREAK

    output buffer, the output buffers 0 permuted 0 failures

    SWITCH2


    SWITCH2 #sh run int po1

    Building configuration...

    Current configuration: 206 bytes

    !

    Interface Port - Channel 1

    ETHERCHANNEL description

    switchport vlan trunk native 2

    switchport trunk allowed vlan 1-4 991 002-1005

    switchport mode trunk

    switchport nonegotiate

    FlowControl send

    end

    SWITCH2 #sh run int f0/18

    Building configuration...

    Current configuration: 190 bytes

    !

    interface FastEthernet0/18

    switchport vlan trunk native 2

    switchport trunk allowed vlan 1-4 991 002-1005

    switchport mode trunk

    switchport nonegotiate

    active in mode channel-group 1

    end

    SWITCH2 #sh run int f0/19

    Building configuration...

    Current configuration: 190 bytes

    !

    interface FastEthernet0/19

    switchport vlan trunk native 2

    switchport trunk allowed vlan 1-4 991 002-1005

    switchport mode trunk

    switchport nonegotiate

    active in mode channel-group 1

    end

    #sh su ethe SWITCH2

    Flags: D - low P - port-channel

    I have - autonomous s - suspended

    H Eve (LACP only)

    R - Layer 3 S - Layer2

    u - unfit to tied selling

    U - running f - cannot allocate an aggregator

    d default port

    Number of channels: 1

    Number of aggregators: 1

    Protocol for the Port-Channel port group

    ------+-------------+-----------+--------------------------------------------

    1 Po1 (SU) LACP Fa0/18 (Pd) Fa0/19 (P)

    #sh int po1 SWITCH2

    Port-channel 1 is up, line protocol is up (connected)

    Material is EtherChannel, address is 000a.b7dd.3d12 (bia 000a.b7dd.3d12)

    Description: ETHERCHANNEL

    MTU 1500 bytes, BW 200000 Kbit, DLY 1000 usec,

    reliability 255/255, txload 1/255, rxload 4/255

    Encapsulation ARPA, loopback not set

    Full-duplex, 100 MB/s, media type is the unknown media type

    input stream control is turned off, output flow control is disabled

    Members in this channel: Fa0/18 Fa0/19

    Type of the ARP: ARPA, ARP Timeout 04:00

    Last entry of 00:00:00, 00:02:58 exit, exit hang never

    Final cleaning of "show interface" counters never

    Input queue: 0/75/0/0 (size/max/drops/dumps); Total output drops: 0

    Strategy of queues: fifo

    Output queue: 0/40 (size/max)

    5 minute input rate 3268000 bps, 254 packets/s

    5 minute output rate 56000 bps, 117 packets/s

    2896053 package, 3157891899 bytes, 0 no buffer entry

    Received 33572 broadcasts (28209 multicast)

    0 Runts, 0 giants, 0 shifters

    entry 0, 0 CRC errors, frame 0, saturation 0, 0 ignored

    Watchdog 0, multicast 28204, break 0 comments

    entry packets 0 with condition of dribble detected

    2755632 packets output, 2612593705 bytes, 0 underruns

    0 output errors, 0 collisions, 1 interface resets

    0 babbles, collision end 0, 0 deferred

    carrier, 0 no carrier, lost 0 0 output BREAK

    output buffer, the output buffers 0 permuted 0 failures

    Well your ports located in the channel of the port are 100Meg ports so certainly you will get no more 100Meg out of it.  When you perform a method on the default channel port load balancing switch is CBC - mac.  Which means that if PC1 has a x.x.x MAC and this is the source of all data might exceed the first link.  Now, if you add another PC with a MAC of y.y.y that might exceed the second link.  Top of the line past offers better and more granular load balancing of methods such as mac source and destination or IP, ports etc.

  • 4 GB with Etherchannel connected to a Dell server ports

    Hello

    I need to connect 4 physical 1 GB of a switch port 4500 for a dell with the team server.

    The thing that is not working, I tried to put the traffic with the iperf and never goes more than 1 GB

    All suggest? Thank you!

    the configuration below:

    interface GigabitEthernet6/38
    switchport access vlan 26
    active in mode channel-group 3
    spanning tree portfast
    end

    (ditto for the 4 ports)

    !

    Interface Port-canal3
    switchport
    switchport access vlan 26
    end

    !

    port-channel - the balance of the CBC - mac support
    Interface Port-canal3
    Interface Port-Channel 4
    active in mode channel-group 3
    active in mode channel-group 3
    active in mode channel-group 3
    active in mode channel-group 3

    !

    RO. CPD. CR # see the etherchannel 3 Summary
    Flags: - Low P - D bundled in port-channel
    I have - autonomous s - suspended
    R - Layer 3 S - Layer2
    U - running f - cannot allocate an aggregator

    M - don't use, minimum contacts not satisfied
    u - unfit to tied selling
    w waiting to be aggregated
    d default port

    Number of channels in use: 2
    Number of aggregators: 2

    Protocol for the Port-Channel port group
    ------+-------------+-----------+-----------------------------------------------
    3 Po3 (SU) LACP Gi6/38 (P) Gi7/12 (P) Gi7/45 (P)
    Gi7/46 (P)

    ro etherchannel load-balance. CPD. CR #Show
    Load balancing EtherChannel Configuration:
    CBC - mac

    EtherChannel load balancing address by protocol used:
    No - IP: Source MAC address
    IPv4: Source MAC address
    IPv6: Source MAC address

    How do you send the traffic? From a PC connected to Cat4500 or have iperf running on Dell Server?

    What happens if traffic beyond 1 G, it starts that drop packets? What kind of traffic drive you to iperf?

    See you soon,.

    -amit singh

  • Configuration of the Cisco etherchannel stack: flag stuck in stand alone

    I'm putting in place an etherchannel for my stack of Cisco (switch Catalyst 3750 G x 2), with a port on each switch the etherchannel. The example of battery cross http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00806cb982.shtml using as a guide, I created my channel. However when I discovered "show etherchannel summary 6 ' it says that both my ports are stand-alone, when I want them to be in port channel grouped in. Thank you in advance for your help, I added all the information I could think.

    Here is how I created the etherchannel

    sailing-sw-1 #conf t

    sailing-sw-1 (config) #interface gigabiteethernet 0/1/10

    active in sail-sw-1(config-if) mode #channel-group 6

    sailing-sw-1(config-if) #switchport trunk encapsulation dot1q

    sailing-sw-1(config-if) #switchport mode trunk

    sailing-sw-1(config-if) #exit

    sailing-sw-1 (config) #interface gigabiteethernet 0/1/10

    active in sail-sw-1(config-if) mode #channel-group 6

    sailing-sw-1(config-if) #switchport trunk encapsulation dot1q

    sailing-sw-1(config-if) #switchport mode trunk

    sailing-sw-1(config-if) #exit

    sailing-sw-1 (config) #exit

    The running-config

    sailing-sw-1 #show running-config

    Building configuration...

    Current configuration: 5390 bytes

    !

    version 12.2

    no service button

    horodateurs service debug uptime

    Log service timestamps uptime

    no password encryption service

    !

    sailing-sw-1 hostname

    !

    boot-start-marker

    boot-end-marker

    !

    Select the 5 secret...

    !

    !

    !

    high-level description of the cisco-global macro

    No aaa new-model

    1 supply ws-c3750g-24ts switch

    2 available ws-c3750g-24ts switch

    mtu 1500 routing system

    Uni-directional aggressive

    !

    !

    !

    MLS qos map cos-dscp 0 8 16 24 32 46 46 56

    !

    Crypto pki trustpoint TP-self-signed-538118016

    enrollment selfsigned

    name of the object cn = IOS - Self - signed - certificate - 538118016

    revocation checking no

    rsakeypair TP-self-signed-538118016

    !

    !

    TP-self-signed-538118016 crypto pki certificate chain

    certificate self-signed 01

    30...

    AF

    quit smoking

    !

    !

    !

    errdisable recovery cause link-flap

    60 errdisable recovery interval

    port-channel - the balance of the load src-dst-mac

    !

    spanning tree mode rapid pvst

    spanning tree default loopguard

    No spanning tree optimize transmission of bpdus

    spanning tree extend id-system

    !

    internal allocation policy of VLAN ascendant

    !

    !

    !

    Interface Port-channel6

    !

    GigabitEthernet1/0/1 interface

    No auto mdix

    !

    interface GigabitEthernet1/0/2

    No auto mdix

    !

    interface GigabitEthernet1/0/3

    No auto mdix

    !

    interface GigabitEthernet1/0/4

    No auto mdix

    !

    interface GigabitEthernet1/0/5

    No auto mdix

    !

    interface GigabitEthernet1/0/6

    !

    interface GigabitEthernet1/0/7

    No auto mdix

    !

    interface GigabitEthernet1/0/8

    No auto mdix

    !

    interface GigabitEthernet1/0/9

    No auto mdix

    !

    interface GigabitEthernet1/0/10

    switchport trunk encapsulation dot1q

    switchport mode trunk

    No auto mdix

    active in mode channel-group 6

    !

    interface GigabitEthernet1/0/11

    No auto mdix

    !

    interface GigabitEthernet1/0/12

    No auto mdix

    !

    interface GigabitEthernet1/0/13

    No auto mdix

    !

    interface GigabitEthernet1/0/14

    No auto mdix

    !

    interface GigabitEthernet1/0/15

    No auto mdix

    !

    interface GigabitEthernet1/0/16

    No auto mdix

    !

    interface GigabitEthernet1/0/17

    No auto mdix

    !

    interface GigabitEthernet1/0/18

    No auto mdix

    !

    interface GigabitEthernet1/0/19

    No auto mdix

    !

    interface GigabitEthernet1/0/20

    No auto mdix

    !

    interface GigabitEthernet1/0/21

    No auto mdix

    !

    interface GigabitEthernet1/0/22

    No auto mdix

    !

    interface GigabitEthernet1/0/23

    No auto mdix

    !

    interface GigabitEthernet1/0/24

    No auto mdix

    !

    interface GigabitEthernet1/0/25

    !

    interface GigabitEthernet1/0/26

    !

    interface GigabitEthernet1/0/27

    !

    interface GigabitEthernet1/0/28

    !

    GigabitEthernet2/0/1 interface

    No auto mdix

    !

    interface GigabitEthernet2/0/2

    No auto mdix

    !

    interface GigabitEthernet2/0/3

    No auto mdix

    !

    interface GigabitEthernet2/0/4

    No auto mdix

    !

    interface GigabitEthernet2/0/5

    No auto mdix

    !

    interface GigabitEthernet2/0/6

    !

    interface GigabitEthernet2/0/7

    No auto mdix

    !

    interface GigabitEthernet2/0/8

    No auto mdix

    !

    interface GigabitEthernet2/0/9

    No auto mdix

    !

    interface GigabitEthernet2/0/10

    switchport trunk encapsulation dot1q

    switchport mode trunk

    No auto mdix

    active in mode channel-group 6

    !

    interface GigabitEthernet2/0/11

    No auto mdix

    !

    interface GigabitEthernet2/0/12

    No auto mdix

    !

    interface GigabitEthernet2/0/13

    No auto mdix

    !

    interface GigabitEthernet2/0/14

    No auto mdix

    !

    interface GigabitEthernet2/0/15

    No auto mdix

    !

    interface GigabitEthernet2/0/16

    No auto mdix

    !

    interface GigabitEthernet2/0/17

    No auto mdix

    !

    interface GigabitEthernet2/0/18

    No auto mdix

    !

    interface GigabitEthernet2/0/19

    No auto mdix

    !

    interface GigabitEthernet2/0/20

    No auto mdix

    !

    interface GigabitEthernet2/0/21

    No auto mdix

    !

    interface GigabitEthernet2/0/22

    No auto mdix

    !

    interface GigabitEthernet2/0/23

    No auto mdix

    !

    interface GigabitEthernet2/0/24

    No auto mdix

    !

    interface GigabitEthernet2/0/25

    !

    interface GigabitEthernet2/0/26

    !

    interface GigabitEthernet2/0/27

    !

    interface GigabitEthernet2/0/28

    !

    interface Vlan1

    the IP 192.168.0.1 255.255.255.0

    !

    default IP gateway - 192.168.76.102

    IP classless

    IP http server

    IP http secure server

    !

    activate the IP sla response alerts

    !

    !

    Line con 0

    line vty 0 4

    password Mil19

    opening of session

    line vty 5 15

    password Mil19

    opening of session

    !

    end

    Interface port-channel 6

    (in the example, there should be this line "identified in this channel: Gi2/article-gi1/0/10 0 / 10 ')


    sailing-sw-1 #show interfaces port-channel 6

    Channel6 port is down, line protocol is down (notconnect)

    Material is EtherChannel, address is 0000.0000.0000 (bia 0000.0000.0000)

    MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

    reliability 255/255, txload 1/255, rxload 1/255

    Encapsulation ARPA, loopback not set

    KeepAlive set (10 sec)

    Link auto-duplex type, automatic speed is automatic, media type is unknown

    input stream control is turned off, output flow control is not supported

    Type of the ARP: ARPA, ARP Timeout 04:00

    Last entry, never, never hang output

    Final cleaning of "show interface" counters never

    Input queue: 0/75/0/0 (size/max/drops/dumps); Total output drops: 0

    Strategy of queues: fifo

    Output queue: 0/40 (size/max)

    5 minute input rate 0 bps, 0 packets/s

    5 minute output rate 0 bps, 0 packets/s

    0 packets input, 0 bytes, 0 no buffer

    Received 0 emissions (0 multicasts)

    0 Runts, 0 giants, 0 shifters

    entry 0, 0 CRC errors, frame 0, saturation 0, 0 ignored

    Watchdog 0, multicast 0, break 0 comments

    entry packets 0 with condition of dribble detected

    exit 0 packets, 0 bytes, 0 underruns

    0 output errors, 0 collisions, 1 interface resets

    0 babbles, collision end 0, 0 deferred

    carrier, 0 no carrier, lost 0 0 output BREAK

    output buffer, the output buffers 0 permuted 0 failures

    EtherChannel 6 Summary

    sailing-sw-1 #show etherchannel 6 Summary

    Flags: - Low P - D bundled in port-channel

    I have - autonomous s - suspended

    H Eve (LACP only)

    R - Layer 3 S - Layer2

    U - running f - cannot allocate an aggregator

    M - don't use, minimum contacts not satisfied

    u - unfit to tied selling

    w waiting to be aggregated

    d default port

    Number of channels: 1

    Number of aggregators: 1

    Protocol for the Port-Channel port group

    ------+-------------+-----------+-----------------------------------------------

    6 Po6 (SD) LACP Gi1/0/10 (I) Gi2/0/10 (I)

    Hello

    It seems that the grouping of NIC Linux box does not work properly. Please

    Check on the side of Linux.

    Kind regards

    NT

  • DSwitch load balancing

    I have DSwitch 5.5 in vsphere 6.0

    Two 5.5 esxi hosts to connect to these virtual switch of two network cards.

    NICs works in IP HASH (the real switch side cisco 3570 I did port channel). Everything works fine, but I have question.

    Can I do a load balancing for a single host examle: IP hash, on the other - on the virtual port original? If say, how? I can see only one setting for all VDswitch

    Can I do a load balancing for a single host examle: IP hash, on the other - on the virtual port original? If say, how? I can see only one setting for all VDswitch

    As you can see on your screenshots, settings are for port group and not overall overall dvSwitch. You can have different settings for each physical ESXi host though, all guests must use the same algorithm as specified by the port or load balancing groups. If you want different settings by physical ESXi hist, then you will need to use the local standard and undistributed vSwitches, but we can ask the question of whether such a potentially unpredictable and inconsistent configuration is desirable.

    On a side note, you can set up several groups of ports with different parameters on a vSwitch (d). However, mixture etherchannel/LAG/LACP IP - hash based load balancing with any other balancing as virtual port ID in the same uplink / vSwitch (d) is not supported.

    In addition, it is not sensible, your acts only physical switch as a single channel for all traffic and will not be able to differentiate as several ports on an ESXi host groups could do.

  • doubt sober etherchannel

    I have a 5.1 esxi host com 3 while rede conectadas em um cisco 2960 switch. Neste servidor so tem um servidor virtual.

    no switch configurei o nas etherchannel portas wave are conectadas as 3 while rede servidor, e no fiz vsphere as configuracoes abaixo:

    Load Balancing: route based on the hash of the IP

    Network failover detection: the only link status

    Notify the switches: Yes

    BACKSPACE: Yes

    monitorei as portas turn e trafega dados nas 3 portas so a 100 MB, mas EU tenho uma banda of 300 MB available devido ao etherchannel

    p / fazer o tests estou um using portable conectado na porta giga, copiando um great land, a taxa of transfer e sempre 100 MB

    to isso estiver product, then o beneficio usar o e etherchannel is EU tivesse but VMs instaladas, silt estariam compartilhando uma banda 300 MB, for example, is tivesse 3 VMs, poderia copy 3 Archives a cada 100 mb 1.

    e assim mesmo that works?

    SEU entendimento esta product, e uma unica VM PODES is beneficiar don't etherchanell is ela to farm but Communicando com um destino, veja:

    Function Hash IP route

    Route in function Hash IP works by taking the IP source and destination addresses and by performing a mathematical calculation on each package to determine what uplink in the team to use. Balancing the load being based on source and destination IP addresses, a single VM contacting several IP addresses can balance its load on all NICs in the team and make better use of the available bandwidth.

    Cast: VMware KB: understanding IP Hash load balancing

  • Failback when using Etherchannel and FCoE

    I have an environment that I am able to dig in for the purposes of learning, but I can't it.  Since I can't make any changes to the environment and experience, I wanted to ask a few questions here.  I'm trying to figure out what that the failback option of virtual exchanges must be defined on when using FCoE and etherchannel.

    The environment consists of:

    • FCoE
    • 2 cards of CNA
    • EtherChannel
    • vPLEX
    • Cluster of metro
    • Nexus 5000


    Each host connects to a single vDS and each portgroup is configured to use:

    • Load balance policy: route based on the hash of the IP
    • Active uplinks: two 10 GbE CNAs
    • Eve & uplinks used: no
    • Physical switch is configured for etherchannel.


    The vSphere networking 5.5 guide says the following for failback on vDS trade option:


    Failback Select Yes or no to disable or enable failback. This option determines how a physical card is returned to active duty after recovering from a failure. If failback is set to Yes (the default), the adapter is returned to active duty as soon as their recovery, moving the daughtercard, which resumed its accommodation, as appropriate. If failback is set to no, an adapter failing has been idle even after the recovery until another active adapter fails, requiring a replacement.


    This evokes the assets & Eve links and since using etherchannel requires that all active links with no standby connection, this means that the restore option does not apply to etherchannel configurations?  Or applies to the way in which the load is re -distributed when a link comes back after having been conducted? 


    For example, that we have a portgroup with two uplinks (uplink1 & uplink2), load balancing policy, the hash value of the IP and physical switch ports are in an etherchannel configuration.  During the normal operation of the IP of the hash calculations (http://blogs.vmware.com/kb/2013/03/troubleshooting-network-teaming-problems-with-ip-hash.html) are made and the load is distributed across the two uplinks.  Let's say the physical switch that connects uplink2 in goes down.  The ESXi hosts connected to that vDS immediately come into uplink2 equation which means uplink1 would only result in the calculation of hash IP?  What is the impact of the automatic restore option when uplink2 is back?  If failback is set to no, uplink2 still wouldn't be in the equation?  If so, how you would get it back in the equation?  Or when the link is up is immediately shot down there regardless of the restore option?  It feels like I'm missing something here. 

    Also, I read that attributing no failback is recommended when using IP storage, because it can lead to port heartbeat that can cause performance issues with the storage.  But I also read that traffic to an etherchannel appears as a single MAC/connection address.  This recommendation apply in an etherchannel configuration?  Are port and MAC stir the same thing?  Or is beating port just at the moment where the link goes up and down and MAC beat is when the MAC's switch between two ports?

    Sorry if these are fundamental questions, but not being a networking guy and not being is not able to experiment makes it hard.  Thanks for any help.

    The Member State of the binding not arise unless the link is established on both sides.

    I agree with the statement portfast. All the links go to an ESXi server do not participate in spanning tree protocols. The goal is to transition to a State of transfer immediately on the link turning upward. This must be paid regardless of the use of an OFFSET.

    LACP will dynamically build the GAL and validate the configuration on both sides is correct. I prefer LACP (dynamic LAG) on any static sort of LAG, but this requires a switch on the side of vSphere distributed. If you have the VDS, using LACP. However, LACP does not solve the problem of covering tree (you still want to avoid using tree covering weight on the SHIFT going the ESXi host).

  • Can we do vmotion between hosts with load balancing in network cards grouping different strategy.

    Hello

    We are implementin new host in our Infra and do some vmotions between different groups. A group a host with balancing 'route based on IP hash. " Can we do Vmotion to another cluster where the hosts have different load balancing policies. In addition, if we change the policy on new hosts in furture of load balancing is loss of downtime or a package?

    Kind regards

    Vikram Kumar

    First of all, no problem from VMs one ESX to another, they use different political Multipathing.

    Second, if you use IP hash, it means you are using etherchannel (or LACP) on the physical layer - configuration/cancellation of the configuration that almost always require that the uplinks are not used by any VMs, so you have time to synchronize the physical and virtual configuration. It is not a time out, but you need to plan accordingly - all depends on your physical network capacity.

  • Ethernet VMware with Cisco EtherChannel and Trunking Question

    Hello

    Trying to get our etherchannels works correctly with our network administrator. Here is our config with a few questions.

    1. as it is to create the trunk between switch and host directly, can I use spanning tree portfast chest edge ?

    2. when don't we use no ip address and when not for this configuration? I see online showing examples with and without it.

    3. in some articles, he described in access mode , while in others he said dot1q trunk mode. See here for the access mode. Admin think it should use dot1q.

    4 Etherchannel is fully support and preferred extending from links on maps, right? Not all of the links on the same card?

    5 is this the case in order to change the load balancing algorithm in vmware first or first to the work of cisco? I did first vmware. (IP-hash)

    It's on a series with 4 cards/blades 6500 switch.

    !
    interface Port-channel200
     switchport
     switchport access vlan 81
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 69,81,172,896
     switchport mode trunk
     switchport nonegotiate
    !
    interface GigabitEthernet2/35
     switchport
     switchport access vlan 81
     switchport trunk allowed vlan 69,81,172,896
     switchport mode trunk
     switchport nonegotiate
     spanning-tree portfast edge
     channel-group 200 mode on
    !
    interface GigabitEthernet8/10
     switchport
     switchport access vlan 81
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 69,81,172,896
     switchport mode trunk
     switchport nonegotiate
     spanning-tree portfast edge
     channel-group 200 mode on
    

    DITGUY2012 wrote:

    Wow Josh. If only you had written documentation. That's the trouble with him. People like me get final instructions, because we're not the guys from network 24 x 7. Great documentation would be layout, the reasons to go this way or that way you did just. That being said, here's my summary based on this discussion.

    1. we have several VLANS that descends from 3 links on the etherchannel. Thus, we should use mode trunk because there is not a single.

    2. we have an another etherchannel with just 1 vlan (vmotion), but in all of two links. This should be the access mode. Or is it still trunk because it's the multiple links?

    3. I don't know what crash dump logger is, or how it applies to my situation.

    4. I saw the bpduguard setting before what exactly is the syntax to use for us? 6500 series.

    5. I don't know if our switch would deliver on that port. How can I tell? At this moment I have switchport setting in there.

    Thank you!

    No problem for reference, the other question of documentation is one of the languages. Their word etherchannel on HP networking hardware, 'trunk' and has nothing to do with the discussion of port "access vs circuit", which they call "tag unidentified vs.

    1 Yes

    2. you would certainly make an access port.

    3. If your server never begins to have a problem with break, VMware can a copy of the accident for the debug log. You can see an article on setting up here: put in place the collector of Dump ESXi 5.0 | VMware vSphere Blog - VMware Blogs.

    4 I'm sorry I'm not familiar with this model

    5. I think if the switchport parameter is here and connectivity seems to work, you can consider yourself safe

  • VM simple Load Balancing with 4 physical network adapters

    I have one main server with 4 cards of physical network dedicated to this server in a vSwitch. I wanted to know the proper way to balancing configuration in vSphere to allow a theoretical throughput of 4 Gbit/s. The options I have, as you know:

    1. Port according to ID - this the method by default when you have 2 or more physical NIC connected to a virtual switch. The VM traffic is realized on a physical NETWORK card based on the VMs virtual port ID and is incremented in the style of round robin. So if you have 2 NICs physical network, the first drop of will traffic VMs that the first NIC, the second VM shuts down to the second NIC, third comes out first NETWORK card and operating system on - host ESXi does not resemble the traffic so if VMs 1,3,5 are heavy network users they will go on the same NETWORK adapter even if the second NETWORK card can be totally unused
    2. Address based MAC - based similar to port, but the physical NETWORK adapter is selected according to the MAC address of virtual machines
    3. IP hash database - the physical NETWORK adapter is selected based on the starting and destination IP address - so if a virtual machine connect to several IP addresses that traffic will be disttibuted on all physical network cards - note this will require LACp be configured on the physical spend this ost ESXi connects to

    The first two sound me as they would give me what I want from the physical NIC selection is based on the virtual source, not the destination machine. So, since I have only a virtual computer, the LB would never use a physical NIC and I'd be stuck with 1 Gbps.

    The third option seems more promising, but I do not have much exposure to the management switch. LACP would be similar to the creation of a trunk on my 3Com switch 2848 reference? It seems likely, but I wanted to run it by the experts to make sure.

    Thank you!

    EDIT: I think I just found the killer. Cited in the manual for my switch:

    The switch does not support the aggregation of links
    Protocol LACP (Control), which is specified in the IEEE standard
    802.3ad.

    Does that mean I'm desperate to do my 4 Gbps with the swithc and I MUST get a LACP switch?

    You will need either LACP or EtherChannel on your switch upstream to support IP hash configuration, install, configure, manage Volume 1 book for ESXi 5.0. With hash IP, MAC address of the virtual computer may appear on any of the physical interfaces available for the vSwitch (at least for the outbound traffic), which would cause problems on the side of the physical switch unless a method of aggregation (LACP or EtherChannel) link type is enabled.

    Mike

  • The order of failover and load balancing

    Hello

    I have the following scenario. An ESXi with 4 Gbps vmnic. The questions are:

    (1) if I have a group of ports configured for 'Route based on the original virtual Port code' in the policy of balancing load, and for the same port group I the option button 'Override switch failover command"checked, where I set up 3 of the active adapters vmnic, as well as the other vmic remaining as unused adapter, the ESXi uses the policy that I have configured (in this case 'Route based on the original port code') between the three vmnic load balancing marked as active? Or he uses them in the order that they appear in the section active cards?

    (2) Suppossed, I configured the four physical switch ports in an etherchannel group to use 'Route based on the IP hash' load balancing policy. In this situation, then I configured for a certain group of port to only used two active adapters and two others as unused? In this case, ESXi should balance the load using the method hash IP but only in two active adapters? Or it is a misconfigiuration and I should not configure my nic teaming in this way?

    (3) the official setup guide says "NOTICE on IP requires the physical switch be configured with etherchannel. For all other options, etherchannel must be disabled. ». How can I I configured my virtual network, if I have a few groups of political ports based on the hash of the IP to use load balancing and another uses 'Route based on the original port code. This is the case when I for example have two management ports using the same vSwitch with four vmnic (where they are configured as an Etherchannel in the physical switch). I would port one or several groups for virtual machines that use the IP of the hash method of balancing the load and vmkernel ports por management uses only a single adapter active with no back and as "based on the source port ID" load balancing as best practices said.

    Now, the four vmnic is the same for all traffic. The physical switch ports must be configured in an etherchannel group because certain groups of ports will use the method of IP hash, but others are not. The configuration guide I said SHOULD NOT use etherchannel if I won't use the hash IP method, but I'LL use it, but only in groups of one or more ports.

    Maybe I do not share the same vmnic from this situation.

    Finally, it's a philosophical question. What is the difference between 'The route based on the source port ID' and the 'road based on the source MAC Hash' load balancing policy? What is the purpose of the second? It is assumed that if I had two different MAC address in a virtual machine, it would be because I had two different virtual cards inside the virtual machine, which would be connected to two different port ID in the vSwitch, I can use the first strategy (based on the original port code). In other words, which would be the case where I had the traffic entering the same vSwitch but port ID with different source MAC address, so I should chose the method to distinguish the Source MAC address load balancing traffic?

    Thank you.

    Guido.

    (1) as long as you override vmnic only and don't change the policy for this group of ports, he uses the policy configured at level vSwitch and use the selected interface 3 with this policy

    (2) it should work, I don't think it's a problem for the switch receive packets on a subset of the aggregation. I do not think that Etherchannel is supported (IIRC, it is a Cisco proprietary protocol, VMware only supports LACP passive, which corresponds to the Port channel world Cisco.) Trouble me if I'm wrong!)

    (3) I think that's all right, as I have explained in 2), there is no special negotiations with the consolidation of VMware, the important thing only I know is to configure the port on the side of the switch channel if you decide to use the IP hash (that will lead to important questions)

    4) (self labeled) I think it may differ in some cases individuals, as when the operating system use the same MAC address for both NICs (aggregation in-vm) or if you advertise several MAC address for the same network card (ESX in a VM for example would make for its VM). Such cases differently affect this setting.

    That is the right question, and I'm curious to know if someone wants to develop on it!

  • NET consolidation balancing option.

    Hi dear all,

    I have doubt in the net grouping feature in vmware to load balancing.

    In the load balancing option, we find three options

    1 :-Id Port Orgination

    2:-source MAC Hash

    3:-Hash IP.

    I want to understand the working procedure of each of the three.

    You can help.

    bhaskardixit wrote:

    I have doubt in the net grouping feature in vmware to load balancing.

    In the load balancing option, we find three options

    1 :-Id Port Orgination

    2:-source MAC Hash

    3:-Hash IP.

    I want to understand the working procedure of each of the three.

    In short, the first two uses a fixed medium to connect a virtual NETWORK adapter to virtual machines with one outgoing vmnic. It requires no installation on the physical switches. A single VM could not get more bandwidth than 1 physical vmnic.

    'Hash IP' policy takes a more complex configuration on the physical switch (called switches Cisco Etherchannel), but could, in some situations, give more bandwidth to a virtual machine unique.

Maybe you are looking for