<div dir="ltr">Yeah, it's unfortunate that in the BE6K installation documentation it's telling you to use LACP when BE's don't come with (and likely never use) the higher license for ESXi.<div><br></div><div>I even opened a documentation defect to help correct the example given in the install guide:</div><div><br></div><div><a href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr85341/">https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr85341/</a> <br></div><div><br></div><div>Install Guide:</div><div><br></div><div><a href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/BE6000/InstallationGuide/12_5/be6k_b_installation-guide-M5-1251/be6k_b_installation-guide-1251_appendix_0110.html">https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/BE6000/InstallationGuide/12_5/be6k_b_installation-guide-M5-1251/be6k_b_installation-guide-1251_appendix_0110.html</a> <br></div><div><br></div><div>As far as the load balancing goes, IP hash is supported on standard vswitches however. You do need to make sure your switch(es) are configured the same way though.</div><div><br></div><div>A little nugget from vmware vpshere 6.5 docs:</div><div><br></div><div>"<span class="gmail-ph gmail-productname" id="gmail-GUID-523FDFBD-EAEC-44A5-9451-F63EB792F156__PRODUCTNAME_151DEB637A324DC9B6DDD7091D718B38" style="box-sizing:border-box;color:rgb(33,37,41);font-family:Metropolis,"Avenir Next","Helvetica Neue",Arial,sans-serif;font-size:14px;background-color:rgb(250,250,250)">ESXi</span><span style="color:rgb(33,37,41);font-family:Metropolis,"Avenir Next","Helvetica Neue",Arial,sans-serif;font-size:14px;background-color:rgb(250,250,250)"> hosts support only 802.3ad link aggregation in Static mode . You can only use a static Etherchannel with vSphere Standard Switches. LACP is not supported. To use LACP, you must have a vSphere Distributed Switch 5.1 and later or Cicso Nexus 1000V. If you enable IP hash load balancing without 802.3ad link aggregation and the reverse, you might experience networking disruptions."</span></div><div><span style="color:rgb(33,37,41);font-family:Metropolis,"Avenir Next","Helvetica Neue",Arial,sans-serif;font-size:14px;background-color:rgb(250,250,250)"><br></span></div><div><span style="color:rgb(33,37,41);font-family:Metropolis,"Avenir Next","Helvetica Neue",Arial,sans-serif;font-size:14px;background-color:rgb(250,250,250)">Source: </span><a href="https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-523FDFBD-EAEC-44A5-9451-F63EB792F156.html">https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-523FDFBD-EAEC-44A5-9451-F63EB792F156.html</a></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 27, 2019 at 6:57 PM Kent Roberts <<a href="mailto:kent@fredf.org">kent@fredf.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">Check Cisco’s docs.. Some of those modes are only supported/not supported on different setups, and configurations. I haven’t looked lately, but last I knew the free version of VMware wasn’t supported. (Maybe they have changed and I am out of date). <div><br></div><div>However….</div><div><br></div><div>Whenever you have issues, check the SRND and make sure your base design is supported.</div><div><br></div><div>Good Luck!</div><div><br><div><br><blockquote type="cite"><div>On Nov 27, 2019, at 5:48 PM, Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:</div><br><div><div dir="ltr">Would you recommend changing it to Originating Port ID?<div><br></div><div><br></div><div>Jonathan</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 27, 2019 at 6:25 PM Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
I would expect the same behavior from PAgP with ESXi.<br>
<br>
<div dir="ltr">-Ryan</div>
<div dir="ltr"><br>
<blockquote type="cite">On Nov 27, 2019, at 19:19, Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">They are channel group ON... (so, no LACP) on the switch...
<div><br>
</div>
<div><br>
</div>
<div>Jonathan</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Nov 27, 2019 at 6:16 PM Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">AFAIK, VMware has always required a distributed vSwitch for LACP, but the earliest reference I can find tonight is 5.1, though I believe it’s referenced the same way in the documentation of every version since then.
<div><br>
</div>
<div><a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkb.vmware.com%2Fs%2Farticle%2F2034277&data=02%7C01%7C%7C68933632a9034cb6982808d77398b185%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637104971952651559&sdata=hpirlhOhpUibcfreuD26bRnR3D2w5NtTGqjxz3f0uIU%3D&reserved=0" target="_blank">https://kb.vmware.com/s/article/2034277</a><br>
<br>
<div dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
<blockquote type="cite">On Nov 27, 2019, at 19:11, Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr"><span>Route based on IP hash should be fine for 802.3ad, but technically, VMWare only supports it with a distributed vSwitch (would need an EA or Enterprise license for the hypervisor, not the “free” license) and not a standard vSwitch.</span><br>
<span>I’ve seen it work with a standard vSwitch, for long periods of time even, and then the CAM table on a switch gets rebuilt (switch reload, power loss ...etc), then all hell breaks loose and you can’t get teaming to work again.</span><br>
<span></span><br>
<span>If those c220s are business editions and/or have the “free” license (non enterprise), then that’s likely a problem. You’d likely see evidence of this in the switch syslog (Mac flaps, possibly err-disable... etc).</span><br>
<span></span><br>
<span>What is the reason for suspecting you need to change the NIC teaming to active/passive?</span><br>
<span></span><br>
<span>Phones going into SRST mode (may be displayed as preservation mode on phones) is an indication the phone’s IP lost network connectivity to all the call control servers listed in the phone’s configuration (xml) file.</span><br>
<span></span><br>
<span>The delayed call setup could be due to the call traversing an unexpected/unoptimized network path, due to disruption in it’s connection to its preferred call control server.</span><br>
<span></span><br>
<span>Thanks,</span><br>
<span></span><br>
<span>Ryan</span><br>
<span></span><br>
<blockquote type="cite"><span>On Nov 27, 2019, at 18:17, Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Customer has a two C220-M4S's with CUCM 11.5... both C-series are connected to the same 4-stack 3850 (port channel, mode on)</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Customer is reporting Preservation Mode kicking in on the LAN and some calls taking a long time to setup.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Currently, VMware is set to Route based on IP Hash with PAgP channel groups.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>I think we need to change it to Route Based on Originating Virtual Port instead, but I cannot prove it before hand...</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>What could be causing the Preservation Mode on the LAN?</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Jonathan</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>_______________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>cisco-voip mailing list</span><br>
</blockquote>
<blockquote type="cite"><span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
</blockquote>
<blockquote type="cite"><span><a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C68933632a9034cb6982808d77398b185%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637104971952661564&sdata=fJcqdFCeqj8ntcObGdrIHjmbBT4mfc%2BULyoJSxFHjy4%3D&reserved=0" target="_blank">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7Cb14bf9fd1c424ebc097e08d7738fe904%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637104934237145806&sdata=HcJICAAFuKb4WDeyLDo7qgvHfV24V7ecL5VjbkegSvU%3D&reserved=0</a></span><br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote></div>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></div></blockquote></div><br></div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>