[cisco-voip] restart servers after COP files installed on all servers or as each server install is finished?

[Matthew Loraditch]

To your out of service question, no they are not

Only the new device types that were added do not work til the reboot is finished

At least for upgrades you install on pub and then all other servers and then do all the reboots, I would do it same way for a device package

Matthew G. Loraditch - CCVP, CCNA, CCDA

1965 Greenspring Drive
Timonium, MD 21093

voice. 410.252.8830
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Friday, January 13, 2012 11:55 AM
To: Christophe Terpreau
Cc: Cisco VOIP
Subject: Re: [cisco-voip] restart servers after COP files installed on all servers or as each server install is finished?

the order of the servers is understood.

what i'm hoping to understand is whether or not rebooting each server after the software is installed (before beginning the install on another) is OK.

i guess the bigger question is this, is a server out of service once the installation has taken place and will only work once rebooted?

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Christophe Terpreau" <ct773q at intl.att.com<mailto:ct773q at intl.att.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "Cisco VOIP" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Friday, January 13, 2012 10:43:14 AM
Subject: RE: [cisco-voip] restart servers after COP files installed on all servers or as each server install is finished?


Hi, I usually install first on pub then tftp servers then subs. Reboot pub, tftps then subs (one server by CM group so service is still usable during the change)




Best Regards
Christophe Terpreau
AT&T BUSINESS SOLUTIONS
EMEA Voice Team
christophe.terpreau at att.com<mailto:christophe.terpreau at att.com>
+33149417737

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net]<mailto:[mailto:cisco-voip-bounces at puck.nether.net]> On Behalf Of Lelio Fulgenzi
Sent: Friday, January 13, 2012 4:35 PM
To: Cisco VOIP
Subject: [cisco-voip] restart servers after COP files installed on all servers or as each server install is finished?

I opened a case with the TAC to get some assistance with respect to installing multiple COP files. They suggested that I install all COP files then proceed with the restart of the cluster. However, they also suggested that I install the COP files on all the servers first and then restart the cluster.

If I have to wait until all the servers have their files installed before rebooting, it's going to be a much longer service interruption since phones won't have a server to connect to once the backups are gone.

I'd rather (if allowed) restart the server after the files are installed.

Also, the instructions say to use the web browser to do the install, is there an option to use the CLI?

Thoughts?



---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120113/dfe62e9e/attachment.html>