networks on switch side

[khaliqamar]

hello,

I need some help on these questions, thanks

1- can I use EtherChannel on psychical switch level  and VLAN on a ESXi side with standard swtich ?

2- If i give two NICs to network admin and ask him to do etherchannel (bonding), can i handle it from standaard switch.

[unsichtbare]

1. Yes
2. Use: Route based on IP Hash

I hesitate to recommend IP Hash, due to considerable limitations associated. Personally, I would choose this method only if I saw network saturation on either of the uplinks

Please see: VMware KB: Understanding IP Hash load balancing

[khaliqamar]

thank you guys,

[vmrulz]

Hey Ray, don't be offended but somebody who has a vcp5-dcv I would think should be able to answer these basic questions?

The answers are of course, it depends. It depends on what kind of physical hardware you have on each end. If you have a standard rack mount x86 server with 2 or more NIC's and you have Ethernet switches capable of creating a Cisco Etherchannel or an LACP channel then you should be able to. It doesn't matter whether you're using vmware Standard or Distributed vswitches.

[vmrulz]

Sorry didn't mean to be a dick just thought it was interesting and it did turn into a mildly interesting thread. You'd think they would support a cross vendor standard such as LACP.

I forgot that I'm doing LACP further up the virtualized stack at my Virtual Connect modules.

[bharathl]

LACP is not supported on standard switches so you need to use the static link aggregation from the Physical switch side. Also for teaming you need to use the IP Hash from the virtual switch side and failure detection method set on link status only. If you are overriding the virtual switch settings on the port group level you have to use the same teaming policy on port group level also. Also all the Phyiscal NICs in active list and no standby or unused NICs.

[narenotpp]

I agree with bharathl,

vNetwork standard switch doesn't support LACP.

and I don't see any issue raising queries, even if you are vcp5-dcv. So don't feel shy asking any question in community when you are not too sure of something.

it's all about knowledge sharing and helping each other.

[unsichtbare]

npadmani wrote:

I agree with bharathl,

vNetwork standard switch doesn't support LACP.

and I don't see any issue raising queries, even if you are vcp5-dcv. So don't feel shy asking any question in community when you are not too sure of something.

it's all about knowledge sharing and helping each other.

I respectfully disagree with npadmani. Per: VMware KB: Host requirements for link aggregation for ESXi and ESX

"The only load balancing option for vSwitch or vDistributed Switch that can be used with EtherChannel is IP HASH"

I still don't like vDS (or whatever they are officially called this week) and only use them where there is a significant advantage justified by use case.

In either case vSS or vDS, use of IP hash has significant limits and should be enabled only when there is a reason to do so.

-J

P.S. I strongly agree with npadmani in that there is no room for criticism of a legitimate question. There are many users that try to increase their numbers with nonsensical and content-less posts, but the original question did not seem to me to be one of them.

[bharathl]

Standard switch supports only static link aggregation not the dynamic link aggregation (LACP)

[narenotpp]

Thanks a lot for your inputs unsichtbare

Above quote taken from KB

VMware KB: Sample configuration of EtherChannel / Link Aggregation Control Protocol (LACP) with ESXi/ESX and Cisco/H…

Last updated: 15/Mar/2015

[khaliqamar]

I was having a doubt on networking side so thats why asked it. I appreciate all of you.

Actually network admin confused me on it. So i asked this question.

I am just a student of this vmware platform.

I was not sure that etherchannel is having a capability to do VLAN tagging and bonding separably.

According to my research iphash required IEEE802.3ad settings on switch which referred as Etherchannel and then we can configure with virtual switch and vDS not required.

for LACP & CDP we need NIC load policy and must have VDS.

Do you guys thinks that its good idea to have ip hash nic teaming and link aggregation VLANs (etherchannel) +bonding on physical switch.

why you guys will prefer virtual port ID nic teaming instead of IPhash if your physical switches are capable to provide IEEE802.3ad or LACP/CDP.