[cisco-voip] Comments on Call Manager Upgrade Plan (My first upgrade)

Thu Sep 24 17:35:13 EDT 2009

Jeff,

You should NOT reboot & switch version your publisher until all subscribers are properly upgraded.

Your plan should be.

4. Upgrade your publisher - Do not reboot
5  Upgrade Subscriber - Do not reboot
6 ...
7 Upgrade Last Subscriber
8 Reboot & Switch Version Publisher
9 Wait 5-10 minutes until Publisher starts up completely
10 Reboot & Swith Version Subscribers.
11 TEST

Keep in mind that the installer won´t allow you to install the subscribers until you have upgraded the publisher.
Once the pub is upgraded, you can upgrade all the subscribers in parallel, if you wish.

One thing I do to ensure the servers are up is to have RTMT running at all times. Once a servers comes back online and starts reporting againt its status in RTMT, i am sure all processes are up. (The reporting service (AMC Service, if my memory serves me)  is the last service to come up on a server.

Best Regards,

 ARIEL ROZA
Service Delivery Engineer
 LOGICALIS
Peru 327 1° Piso - C.A.B.A. - Argentina - C1063ACH
Tel/Fax: +54 (11) 4344-0300
ariel.roza at la.logicalis.com
www.la.logicalis.com
www.logicalisnow.com
 Por favor, piense en el medioambiente antes de imprimir este email. 
La presente información se envía únicamente para el destinatario, y contiene información de carácter CONFIDENCIAL o PRIVLEGIADA.
La modificación, retransmisión, difusón, copia u otro uso de esta información por cualquier medio, por personas distintas al destinatario, están estrictamente prohibidas.

From: Jeff Ruttman
Sent: Thu 24/09/2009 10:56
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Comments on Call Manager Upgrade Plan (My first upgrade)

Greetings,

I see by the Cisco Alert at the very end of this email that I'll have to do my first CCM upgrade this weekend--or bust!  I have a few questions from the OS Admin Guide and a couple more in my "upgrade plan.'  Not a major upgrade; I'm upgrading from 6.1.2 to 6.1.4(SU1).  Any comments will be appreciated greatly.

OS Guide says this:
Starting with Cisco Unified Communications Manager version 6.1(1), CAPF uses the Certificate Manager Infrastructure to manage its certificates and keys. Because of this, when you upgrade to version 6.1(1) or higher, CAPF keys and certificates automatically get regenerated. You must then rerun the CTL Client application to upgrade the CTL file. For information on using CAPF with Cisco Unified Communications Manager, refer to the Cisco Unified Communications Manager Security Guide.
Obtain licenses for Cisco Unified Communications Manager 6.1(1) before upgrading to this release. You must import your new licenses after upgrading to enable the system. Refer to Cisco Unified Communications Manager Administration Guide for information about licensing and obtaining licenses.
I see that the Cisco CTL Provider service is deactivated on all our servers.  This does not apply to me then?

OS Guide says:
During the installation of upgrade software, the upgrade may appear to stall. The upgrade log stops displaying new log messages.
Where/how do I access the installation log?

Here is my little plan (with some questions)
1. Ensure a good backup.
2. DVD into drive.
3. Login to OS Admin on Publisher.
4. Run through install and reboot to upgraded partition.
(Should I do any testing at this point?)
5. Rinse and Repeat on our 2 Subscribers.
(If the CCM version upgrade has newer phone loads, at what point will phones begin grabbing the new loads?  After the Pub comes on line after the upgrade?  When I reboot the first Sub and phones re-register to the other Sub?  Or will I just reset all the phones that will get a new load after all the servers are upgraded?)
6. See that phone and GWs are all registered.  Test incoming/outgoing calling.  Test that I can make database changes on the Pub....
(What other testing do you recommend?)

Thanks
jeff

From: CiscoNotificationService at cisco.com [mailto:CiscoNotificationService at cisco.com] 
Sent: Thursday, September 24, 2009 3:30 AM
To: Jeff Ruttman
Subject: Cisco Notification Alert -7800 MCS Servers_Daily-09/24/2009 08:29 GMT

Cisco Notification Service Alert: 
________________________________________________________________________________

Cisco Notification Alert -7800 MCS Servers_Daily-09/24/2009 08:29 GMT

Field Notices-Cisco 7800 Series Media Convergence Servers-09/23/2009 08:13 GMT-09/24/2009 07:30 GMT

Title: Field Notice: FN - 63255 - MCS-7825-I2 & IBM x306m, BIOS 1.42 & 1.43 error prevents a system from booting if rebooted after October 1, 2009  [Cisco 7800 Series Media Convergence Servers]
Url: http://www.cisco.com/en/US/customer/ts/fn/632/fn63255.html
Description: A defect in the HostRAID BIOS 2106 (included with System BIOS version 1.42 and 1.43) will prevent a server from booting successfully if the server is rebooted after October 1, 2009. This is caused by a defect in the IBM BIOS and is documented in IBM RETAIN Tip: H182636 
Date: 2009-09-23 06:55:21.0

For more information you can visit the Product Field Notice Summary: http://www.cisco.com/en/US/support/tsd_products_field_notice_summary.html 
________________________________________________________________________________

To unsubscribe this notification click the following url :
http://www.cisco.com/cisco/support/notifications/addedit.html?notiId=22132

Help us improve this facility. To give feedback you can visit the Cisco Notification Service: http://www.cisco.com/cisco/support/notifications.html#feedback 

CONFIDENTIALITY NOTICE: The information contained in this email including attachments is intended for the specific delivery to and use by the individual(s) to whom it is addressed, and includes information which should be considered as private and confidential. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you have received this message in error, please reply to the sender immediately and delete the original message and any copy of it from your computer system. Thank you. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090924/e19e6d1e/attachment.html>