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

2019-11-28 Thread Ryan Huff
tive/standby. Thanks, Ryan From: Jonathan Charles mailto:jonv...@gmail.com>> Sent: Wednesday, November 27, 2019 7:48 PM To: Ryan Huff mailto:ryanh...@outlook.com>> Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> mailto:cisco-voip@puck.n

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

2019-11-28 Thread Ryan Huff
p@puck.nether.net<mailto:cisco-voip@puck.nether.net> mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco-voip] Preservation Mode, long time for call setups... Would you recommend changing it to Originating Port ID? Jonathan On Wed, Nov 27, 2019 at 6:25 PM Ryan Huff mai

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

2019-11-28 Thread Anthony Holloway
t is not, I'd consider un-teaming and just going to >> active/standby. >> >> Thanks, >> >> Ryan >> >> -- >> *From:* Jonathan Charles >> *Sent:* Wednesday, November 27, 2019 7:48 PM >> *To:* Ryan Huff >&

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

2019-11-28 Thread Jonathan Charles
t going to > active/standby. > > Thanks, > > Ryan > > ---------- > *From:* Jonathan Charles > *Sent:* Wednesday, November 27, 2019 7:48 PM > *To:* Ryan Huff > *Cc:* cisco-voip@puck.nether.net > *Subject:* Re: [cisco-voip] Preservation M

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

2019-11-27 Thread Ryan Huff
hether nic teaming is a material requirement in your environment, but if it is not, I'd consider un-teaming and just going to active/standby. Thanks, Ryan From: Jonathan Charles Sent: Wednesday, November 27, 2019 7:48 PM To: Ryan Huff Cc: cisco-voip@puck.

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

2019-11-27 Thread Anthony Holloway
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.co

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

2019-11-27 Thread Kent Roberts
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, chec

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

2019-11-27 Thread Jonathan Charles
Would you recommend changing it to Originating Port ID? Jonathan On Wed, Nov 27, 2019 at 6:25 PM Ryan Huff wrote: > I would expect the same behavior from PAgP with ESXi. > > -Ryan > > On Nov 27, 2019, at 19:19, Jonathan Charles wrote: > >  > They are channel group ON... (so, no LACP) on the

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

2019-11-27 Thread Ryan Huff
I would expect the same behavior from PAgP with ESXi. -Ryan On Nov 27, 2019, at 19:19, Jonathan Charles wrote:  They are channel group ON... (so, no LACP) on the switch... Jonathan On Wed, Nov 27, 2019 at 6:16 PM Ryan Huff mailto:ryanh...@outlook.com>> wrote: AFAIK, VMware has always requi

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

2019-11-27 Thread Ryan Huff
Well, at the very least, I would say that’s an unsupported configuration (using LACP on ESXi with a standard switch); that alone should be enough justification to change that. As for “proof”, you’d see it in the switch’s syslog. However, the matter at hand (preservation mode), is due to a loss o

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

2019-11-27 Thread Jonathan Charles
They are channel group ON... (so, no LACP) on the switch... Jonathan On Wed, Nov 27, 2019 at 6:16 PM Ryan Huff 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 t

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

2019-11-27 Thread Jonathan Charles
I remembered another UCS set to IP Hash and having all kinds of connectivity issues... this is a standard switch, not a distributed and just the basic license. On Wed, Nov 27, 2019 at 6:11 PM Ryan Huff wrote: > Route based on IP hash should be fine for 802.3ad, but technically, VMWare > only sup

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

2019-11-27 Thread Ryan Huff
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 Sent from my iPhone On Nov 27, 2019, a

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

2019-11-27 Thread Ryan Huff
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 tim

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

2019-11-27 Thread Jonathan Charles
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 chann