Think this is the first and only good video for an example of LACP.. I think the configuration is a PITA. Those steps make sense afterwards, they don't seem straightforward to me. Thanks, my vMotion is now running flawlessly
You're not using LACP on the Cisco side. You are using static port-channels as evidenced by the protocol in your output being blank. You must use "channel-group # mode active/passive" to enable LACP. This static configuration will not dynamically reroute traffic if one of the links goes down. LACP will notice the loss of neighborship and push traffic out the remaining links in the channel.
Thanks for the video, it's very helpful! one thing to point out as someone else did, you set channel-group 1 mode on instead of channel-group 1 mode active. From this setup (with the ESXI side being passive) channel-group 1 mode active should be the proper command, because without this, no LACP negotiation is actually taking place and unfortunately no redundancy is present either.
Brilliant video! Very well explained. Thank you for taking the time to make it. I do agree with a few of the other comments that I needed to replace to the mode command to "active" in order to negotiate the LACP protocol. Other than that, this worked perfectly. Thank you again sir!
Bro--I want to tell you that I appreciate your video and good explanation on the setup---it's very well explained. also wanna tell you that you are the only one on youtube that doing vDS LAG video that is not 10 years old...again Thanks!
Could accessing an individual esxi host become more difficult during network issues, if the vmk is inside a lag? What is seen at the keyboard and monitor terminal when you look in the networking menu (the yellow text screen.) Does placing the vmk inside the lag, increase the speed of migrating a VM between hosts?
Kreg. Placing the vmk inside the lag does not increase the speed of migrating a VM as far as I can tell. It does benefits you because it allows you to do it from a centralized UI (vCenter). In my experience in a production environment, you should leave at least one physical adapter per ESXi host out of the LAG in case you need to recover the vCenter server later on. I hope this helps.
I think you also need the ESXi hosts to be licensed with Enterprise Plus, in order to get a Distributed switch, which will have the LACP support. There is no LACP support that I understand, to be in a Standard switch.
Think this is the first and only good video for an example of LACP.. I think the configuration is a PITA. Those steps make sense afterwards, they don't seem straightforward to me. Thanks, my vMotion is now running flawlessly
You're not using LACP on the Cisco side. You are using static port-channels as evidenced by the protocol in your output being blank. You must use "channel-group # mode active/passive" to enable LACP. This static configuration will not dynamically reroute traffic if one of the links goes down. LACP will notice the loss of neighborship and push traffic out the remaining links in the channel.
thank you. This video is everything
Awesome!
Thanks for the video, it's very helpful! one thing to point out as someone else did, you set channel-group 1 mode on instead of channel-group 1 mode active. From this setup (with the ESXI side being passive) channel-group 1 mode active should be the proper command, because without this, no LACP negotiation is actually taking place and unfortunately no redundancy is present either.
Brilliant video! Very well explained. Thank you for taking the time to make it. I do agree with a few of the other comments that I needed to replace to the mode command to "active" in order to negotiate the LACP protocol. Other than that, this worked perfectly. Thank you again sir!
sotaque de BR em man
❤
Awesome. thank you
Bro--I want to tell you that I appreciate your video and good explanation on the setup---it's very well explained. also wanna tell you that you are the only one on youtube that doing vDS LAG video that is not 10 years old...again Thanks!
thx for help
Hello Sir, How are you? I am using your Video and having difficulties to ping my vCenter? Please help me?
Great video, but you should configure mode active on the switch side otherwise you are not really using LACP negotiation
Is there any performance improvements after configuring LAG?
Excellent . liked it. very informtive. cheers
Your explanation is clear and to the point, clearly demonstrated as well. Many thanks
Cisco ACI Support engineer sent us your video. =)
Thanks for posting this dude, really helped me out
tnx for the video, it helped a lot brother
Thank you!
Your video truly helped me out!
Great video. Thank you so much
Could accessing an individual esxi host become more difficult during network issues, if the vmk is inside a lag? What is seen at the keyboard and monitor terminal when you look in the networking menu (the yellow text screen.)
Does placing the vmk inside the lag, increase the speed of migrating a VM between hosts?
Kreg. Placing the vmk inside the lag does not increase the speed of migrating a VM as far as I can tell. It does benefits you because it allows you to do it from a centralized UI (vCenter). In my experience in a production environment, you should leave at least one physical adapter per ESXi host out of the LAG in case you need to recover the vCenter server later on. I hope this helps.
Thanks a lot for this video! It helped us a lot!
Great instructions. Much appreciate it!
Very Helpful video.
thanks
Is LACP supported in the v7 Hypervisor?
Yes it is supported as far as I am concerned.
@@itseasy8296 in the free version? Could you maybe explain how? The necessity settings don't seem to exist
@@mythinktube Are you using the ESXi vSphere software or are you using the vCenter? You can only configure LACP using vCenter and not the vSphere.
I think you also need the ESXi hosts to be licensed with Enterprise Plus, in order to get a Distributed switch, which will have the LACP support. There is no LACP support that I understand, to be in a Standard switch.