Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Bill Talley 
1.  That's kind of a loaded question.   90% bugs where  bugs also includes the 
system is "functioning as designed".  Most failures I've encountered, as a 
partner, occur as a result of the applications heavy reliance on DNS (if 
configured) and NTP.  Would be nice if there was an option to bypass the error 
and proceed based on host file entries or hardware clock as opposed to outright 
failing because let's say, there are two different PTR records for the same 
host or DNS/NTP are down for maintenance (different server group).  I get the 
security/reliability piece of it, but why can't the developers permit the 
upgrade to complete and present the same  "DNS is unreachable/invalid" or "NTP 
is unreachable" message after the upgrade completes like they any other time of 
operation?

2.  Same amount of planning as I do when upgrades fail, about 8-12 hours.

Thanks for asking for feedback.


Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.

> On Aug 23, 2017, at 8:37 AM, Ryan Ratliff (rratliff)  
> wrote:
> 
> Quick 2 question poll, feel free to unicast or share your response with the 
> group.
> 
> 1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
> of failures are due to a bug vs something in the environment (user error, db 
> updates, etc)?  
> % bug:
> % not a bug:
> Yes it’s a very subjective question but that’s ok, use your judgement.
> 
> 2. When an upgrade goes smoothly with no issues, how much time do you put 
> into the planning and preparation for the upgrade (not the execution)?
> 
> Thanks,
> 
> -Ryan
> 
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Lelio Fulgenzi 

To add to this, we had a unity connection v11.5 install go awry because it 
didn't make sure the serviceability component was completed installing before 
timing out and restarting the server. The TAC had never seen anything like it 
before. No errors in the install logs. Just an entire missing component. 

Adding because I know how close the cucm and connection installs are. 


Sent from my iPhone

> On Aug 23, 2017, at 9:46 AM, Lelio Fulgenzi  wrote:
> 
> 1)
> 
> 10% bug
> 90% other
> 
> I think it's happened only once to be honest. 
> 
> 2)
> 
> Aside from service packs, we have taken an offline upgrade approach. This 
> typically involves at least one or two failed upgrades for whatever reason. 
> We then make sure we can replicate two or three successful upgrades. That 
> takes anywhere from a week to two weeks if we're able to concentrate on just 
> those tasks. But that's never the case.
> 
> Preparing for the upgrades involves reading release notes and reconciling a 
> user defined compatibility matrix. That takes a weeks or so. Dedicated, but 
> it ends up being stretched over more time.
> 
> Lelio
> 
> 
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
> 
> 519-824-4120 Ext 56354
> le...@uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
> 
> 
> -Original Message-
> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
> Ryan Ratliff (rratliff)
> Sent: Wednesday, August 23, 2017 9:38 AM
> To: cisco-voip list
> Subject: [cisco-voip] UCM Upgrade Poll
> 
> Quick 2 question poll, feel free to unicast or share your response with the 
> group.
> 
> 1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
> of failures are due to a bug vs something in the environment (user error, db 
> updates, etc)?  
> % bug:
> % not a bug:
> Yes it’s a very subjective question but that’s ok, use your judgement.
> 
> 2. When an upgrade goes smoothly with no issues, how much time do you put 
> into the planning and preparation for the upgrade (not the execution)?
> 
> Thanks,
> 
> -Ryan
> 
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] 11.5.1su3 and 12.0 release notes

2017-08-23 Thread Lelio Fulgenzi 

I hope they clear this up soon. The worst part is, they (Cisco) mentioned that 
SU3 isn't even the final version we should expect to be running come September 
2018.

I cried a little inside when I read that in the forums.



Sent from my iPhone

On Aug 23, 2017, at 5:10 PM, Charles Goldsmith 
> wrote:

Several sections in the New and Changed Features mentions 12.0 features, and I 
wasn't sure if this was a copy/paste issue, or if these features are available 
in su3 as well.

One came to mind: 
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/SU3/cucm_b_release-notes-cucm-imp-1151su3/cucm_b_release-notes-cucm-imp-1151su3_chapter_00.html#reference_6D6A4367D19A6A792BA1844DE6F9A9A5

Also, of note, 12.0 doesn't have info about apple's new APNs changes that SU3 
has, I'm assuming that feature will come to an SU for 12.0 or was it just not 
documented?

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/12_0_1/cucm_b_release-notes-for-cucm-imp-1201/cucm_b_release-notes-for-cucm-imp-1201_chapter_00.html

Thanks
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Ryan Huff 
I would tend to agree that the overall installation process could improve (not 
that I want to give up my ANSI art or anything). Most of the installation 
process today is merely an extension of the underlying Linux kernel. I would 
settle for more verbose feedback when errors are encountered, like dumping the 
syslog to the tmp folder on a jailed CLI that I have access to at all points 
during the install instead of the rain dance you have to do today with the 
serial port.

-RH

On Aug 23, 2017, at 4:47 PM, Anthony Holloway 
> wrote:

Wow, it's kind of cool that you're even asking.  Thanks for that.

Already I can see this is going to be a wide gap in responses. Partner vs end 
user, this customer vs that customer, this version vs that version, this 
scenario vs that one, and on, and on, and on.

1) I feel like it's always a bug (100%), in that, developers should code 
solutions that can work around most issues.  E.g., I had an upgrade fail on a 
CUCM because the ntp was 0.us.pool.ntp.org, despite 
CUCM happily syncing to it in the current version.  OR Common partition not 
having enough space, when devs could just purge old logs to make room, or 
simply make better logs to begin with (I do admit, moving to compress logs 
[TAR/GZ] was sweet)

2) This is a painful one for me, but I put in a lot of time preparing for an 
upgrade.  A large portion of the time is, in my opinion, wasted finding the 
right documentation and then trying to interpret it.  Here's a fun one: there's 
over 100 documents an Engineer needs to reference in preparation for what I 
would consider a low-medium level environment.  I've posted this before, but 
I'll post it again, I have a matrix of documents I need to reference during the 
planning and execution phase of an upgrade:

[http://cisco-voip.markmail.org/download.xqy?id=rrs3zlxbamemgodr=1]

On Wed, Aug 23, 2017 at 8:38 AM Ryan Ratliff (rratliff) 
> wrote:
Quick 2 question poll, feel free to unicast or share your response with the 
group.

1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
of failures are due to a bug vs something in the environment (user error, db 
updates, etc)?
% bug:
% not a bug:
Yes it’s a very subjective question but that’s ok, use your judgement.

2. When an upgrade goes smoothly with no issues, how much time do you put into 
the planning and preparation for the upgrade (not the execution)?

Thanks,

-Ryan

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Charles Goldsmith 
But Anthony, we all know you are an over achiever!

And that's ok, it makes you one of our experts on here too...

On Wed, Aug 23, 2017 at 3:46 PM, Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Wow, it's kind of cool that you're even asking.  Thanks for that.
>
> Already I can see this is going to be a wide gap in responses. Partner vs
> end user, this customer vs that customer, this version vs that version,
> this scenario vs that one, and on, and on, and on.
>
> 1) I feel like it's always a bug (100%), in that, developers should code
> solutions that can work around most issues.  E.g., I had an upgrade fail on
> a CUCM because the ntp was 0.us.pool.ntp.org, despite CUCM happily
> syncing to it in the current version.  OR Common partition not having
> enough space, when devs could just purge old logs to make room, or simply
> make better logs to begin with (I do admit, moving to compress logs
> [TAR/GZ] was sweet)
>
> 2) This is a painful one for me, but I put in a lot of time preparing for
> an upgrade.  A large portion of the time is, in my opinion, wasted finding
> the right documentation and then trying to interpret it.  Here's a fun one:
> there's over 100 documents an Engineer needs to reference in preparation
> for what I would consider a low-medium level environment.  I've posted this
> before, but I'll post it again, I have a matrix of documents I need to
> reference during the planning and execution phase of an upgrade:
>
>
>
>
> On Wed, Aug 23, 2017 at 8:38 AM Ryan Ratliff (rratliff) <
> rratl...@cisco.com> wrote:
>
>> Quick 2 question poll, feel free to unicast or share your response with
>> the group.
>>
>> 1. When you or your customers have a UCM or IMP upgrade fail, what
>> percentage of failures are due to a bug vs something in the environment
>> (user error, db updates, etc)?
>> % bug:
>> % not a bug:
>> Yes it’s a very subjective question but that’s ok, use your judgement.
>>
>> 2. When an upgrade goes smoothly with no issues, how much time do you put
>> into the planning and preparation for the upgrade (not the execution)?
>>
>> Thanks,
>>
>> -Ryan
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] 11.5.1su3 and 12.0 release notes

2017-08-23 Thread Charles Goldsmith 
Several sections in the New and Changed Features mentions 12.0 features,
and I wasn't sure if this was a copy/paste issue, or if these features are
available in su3 as well.

One came to mind:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/11_5_1/SU3/cucm_b_release-notes-cucm-imp-1151su3/cucm_b_release-notes-cucm-imp-1151su3_chapter_00.html#reference_6D6A4367D19A6A792BA1844DE6F9A9A5


Also, of note, 12.0 doesn't have info about apple's new APNs changes that
SU3 has, I'm assuming that feature will come to an SU for 12.0 or was it
just not documented?

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/12_0_1/cucm_b_release-notes-for-cucm-imp-1201/cucm_b_release-notes-for-cucm-imp-1201_chapter_00.html

Thanks
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Anthony Holloway 
Wow, it's kind of cool that you're even asking.  Thanks for that.

Already I can see this is going to be a wide gap in responses. Partner vs
end user, this customer vs that customer, this version vs that version,
this scenario vs that one, and on, and on, and on.

1) I feel like it's always a bug (100%), in that, developers should code
solutions that can work around most issues.  E.g., I had an upgrade fail on
a CUCM because the ntp was 0.us.pool.ntp.org, despite CUCM happily syncing
to it in the current version.  OR Common partition not having enough space,
when devs could just purge old logs to make room, or simply make better
logs to begin with (I do admit, moving to compress logs [TAR/GZ] was sweet)

2) This is a painful one for me, but I put in a lot of time preparing for
an upgrade.  A large portion of the time is, in my opinion, wasted finding
the right documentation and then trying to interpret it.  Here's a fun one:
there's over 100 documents an Engineer needs to reference in preparation
for what I would consider a low-medium level environment.  I've posted this
before, but I'll post it again, I have a matrix of documents I need to
reference during the planning and execution phase of an upgrade:



On Wed, Aug 23, 2017 at 8:38 AM Ryan Ratliff (rratliff) 
wrote:

> Quick 2 question poll, feel free to unicast or share your response with
> the group.
>
> 1. When you or your customers have a UCM or IMP upgrade fail, what
> percentage of failures are due to a bug vs something in the environment
> (user error, db updates, etc)?
> % bug:
> % not a bug:
> Yes it’s a very subjective question but that’s ok, use your judgement.
>
> 2. When an upgrade goes smoothly with no issues, how much time do you put
> into the planning and preparation for the upgrade (not the execution)?
>
> Thanks,
>
> -Ryan
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Ryan Huff 
1.) Bug Poll

  Legitimate bugs (which I define as unexpected behavior in consistent with 
published Cisco documentation): 2%

  Customer Issue: 98%


2.) I usually devote 16-20 hours of planning and prepping the upgrade 
(Documentation, Visio, building the bridge if it's that kind of upgrade ... 
etc). If I have extravagant products in play like Social Miner ... the now 
defunct MediaSense ... etc, I might add a little more time but right around the 
20 hour mark is where I feel comfortable.


-Ryan



From: cisco-voip  on behalf of Ryan Ratliff 
(rratliff) 
Sent: Wednesday, August 23, 2017 9:37 AM
To: cisco-voip list
Subject: [cisco-voip] UCM Upgrade Poll

Quick 2 question poll, feel free to unicast or share your response with the 
group.

1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
of failures are due to a bug vs something in the environment (user error, db 
updates, etc)?
% bug:
% not a bug:
Yes it’s a very subjective question but that’s ok, use your judgement.

2. When an upgrade goes smoothly with no issues, how much time do you put into 
the planning and preparation for the upgrade (not the execution)?

Thanks,

-Ryan

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Matthew Loraditch 
I've had a bug once or twice, so 10% maybe??

We have very simple installs, no clusters more than 2 servers, no user bases 
more than a 1000, and nothing more sophisticated added other than CCX or CUACA. 
We upgrade internally to the latest version first, but outside of a quick 
release notes reading and verification of compatibility it's not a lot of prep, 
maybe 30 minutes to an hour. Albeit, I usually am following along in the 
communities for the betas and various partner and CCP webcasts so I'm aware of 
any big changes/caveats ahead of time (like the end of support phone models, 
etc)

Matthew G. Loraditch – CCNP-Voice, CCNA-R, CCDA
Network Engineer
Direct Voice: 443.541.1518

Facebook | Twitter | LinkedIn | G+

-Original Message-
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Ratliff (rratliff)
Sent: Wednesday, August 23, 2017 9:38 AM
To: cisco-voip list 
Subject: [cisco-voip] UCM Upgrade Poll

Quick 2 question poll, feel free to unicast or share your response with the 
group.

1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
of failures are due to a bug vs something in the environment (user error, db 
updates, etc)?  
% bug:
% not a bug:
Yes it’s a very subjective question but that’s ok, use your judgement.

2. When an upgrade goes smoothly with no issues, how much time do you put into 
the planning and preparation for the upgrade (not the execution)?

Thanks,

-Ryan

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Lelio Fulgenzi 
1)

10% bug
90% other

I think it's happened only once to be honest. 

2)

Aside from service packs, we have taken an offline upgrade approach. This 
typically involves at least one or two failed upgrades for whatever reason. We 
then make sure we can replicate two or three successful upgrades. That takes 
anywhere from a week to two weeks if we're able to concentrate on just those 
tasks. But that's never the case.

Preparing for the upgrades involves reading release notes and reconciling a 
user defined compatibility matrix. That takes a weeks or so. Dedicated, but it 
ends up being stretched over more time.

Lelio


---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1


-Original Message-
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Ratliff (rratliff)
Sent: Wednesday, August 23, 2017 9:38 AM
To: cisco-voip list
Subject: [cisco-voip] UCM Upgrade Poll

Quick 2 question poll, feel free to unicast or share your response with the 
group.

1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
of failures are due to a bug vs something in the environment (user error, db 
updates, etc)?  
% bug:
% not a bug:
Yes it’s a very subjective question but that’s ok, use your judgement.

2. When an upgrade goes smoothly with no issues, how much time do you put into 
the planning and preparation for the upgrade (not the execution)?

Thanks,

-Ryan

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] UCM Upgrade Poll

2017-08-23 Thread Ryan Ratliff (rratliff) 
Quick 2 question poll, feel free to unicast or share your response with the 
group.

1. When you or your customers have a UCM or IMP upgrade fail, what percentage 
of failures are due to a bug vs something in the environment (user error, db 
updates, etc)?  
% bug:
% not a bug:
Yes it’s a very subjective question but that’s ok, use your judgement.

2. When an upgrade goes smoothly with no issues, how much time do you put into 
the planning and preparation for the upgrade (not the execution)?

Thanks,

-Ryan

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip