[cisco-voip] Preservation Mode, long time for call setups...

Wed Nov 27 20:09:20 EST 2019

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.

I even opened a documentation defect to help correct the example given in
the install guide:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr85341/

Install Guide:

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

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.

A little nugget from vmware vpshere 6.5 docs:

"ESXi 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."

Source:
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.networking.doc/GUID-523FDFBD-EAEC-44A5-9451-F63EB792F156.html

On Wed, Nov 27, 2019 at 6:57 PM Kent Roberts <kent at fredf.org> wrote:

> 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).
>
> However….
>
> Whenever you have issues, check the SRND and make sure your base design is
> supported.
>
> Good Luck!
>
>
> On Nov 27, 2019, at 5:48 PM, Jonathan Charles <jonvoip at gmail.com> wrote:
>
> Would you recommend changing it to Originating Port ID?
>
>
> Jonathan
>
> On Wed, Nov 27, 2019 at 6:25 PM Ryan Huff <ryanhuff at outlook.com> wrote:
>
>> I would expect the same behavior from PAgP with ESXi.
>>
>> -Ryan
>>
>> On Nov 27, 2019, at 19:19, Jonathan Charles <jonvoip at gmail.com> wrote:
>>
>> 
>> They are channel group ON... (so, no LACP) on the switch...
>>
>>
>> Jonathan
>>
>> On Wed, Nov 27, 2019 at 6:16 PM Ryan Huff <ryanhuff at outlook.com> wrote:
>>
>>> 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.
>>>
>>> https://kb.vmware.com/s/article/2034277
>>> <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>
>>>
>>> Sent from my iPhone
>>>
>>> On Nov 27, 2019, at 19:11, Ryan Huff <ryanhuff at outlook.com> wrote:
>>>
>>> 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.
>>> 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.
>>>
>>> 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).
>>>
>>> What is the reason for suspecting you need to change the NIC teaming to
>>> active/passive?
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>> On Nov 27, 2019, at 18:17, Jonathan Charles <jonvoip at gmail.com> wrote:
>>>
>>>
>>> 
>>>
>>> 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)
>>>
>>>
>>> Customer is reporting Preservation Mode kicking in on the LAN and some
>>> calls taking a long time to setup.
>>>
>>>
>>> Currently, VMware is set to Route based on IP Hash with PAgP channel
>>> groups.
>>>
>>>
>>> I think we need to change it to  Route Based on Originating Virtual Port
>>> instead, but I cannot prove it before hand...
>>>
>>>
>>> What could be causing the Preservation Mode on the LAN?
>>>
>>>
>>>
>>> Jonathan
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> cisco-voip mailing list
>>>
>>> cisco-voip at puck.nether.net
>>>
>>>
>>> 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
>>> <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>
>>>
>>> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191127/7abae980/attachment.htm>