<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Oh, and this only applies to CM 4.x. CM5.x and later changes all the
rules.<br>
<br>
/Wes<br>
<br>
On Wednesday, September 30, 2009 2:13:41 PM, Wes Sisk
<a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a> wrote:<br>
<blockquote cite="mid:4AC39FD5.2060401@cisco.com" type="cite">
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
yep. something that keeps L1/L2/L3 up and lets the server use the IP
bound to the ethernet interface. If you use DHCP that clearly
introduces other limitations.<br>
<br>
/wes<br>
<br>
On Wednesday, September 30, 2009 2:08:05 PM, Lelio Fulgenzi
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a> wrote:<br>
<blockquote
cite="mid:143016065.9802561254334085678.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">so,
changing the VLAN on the switch is good enough?<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt<br>
<br>
<br>
----- Original Message -----<br>
From: "Wes Sisk" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a><br>
To: "Lelio Fulgenzi" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
Cc: "Dane" <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:dane@pktloss.net"><dane@pktloss.net></a>, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Sent: Wednesday, September 30, 2009 1:35:00 PM GMT -05:00 US/Canada
Eastern<br>
Subject: Re: [cisco-voip] Restoring 4.1(3)sr5d Publisher?<br>
<br>
<link href="/zimbra/css/msgview.css?v=081117021119" rel="stylesheet">
If TAC engineer is not familiar then yes, please do escalate. It is
still supported and this knowledge is still available to help you.<br>
<br>
Otherwise -<br>
it is good to install and upgrade the publisher offline. It is not
good to take the publisher offline by simply unplugging the network
cable. That takes down the IP interface and causes numerous problems
with installs and upgrades.<br>
<br>
/Wes<br>
<br>
On Wednesday, September 30, 2009 11:40:55 AM, Lelio Fulgenzi <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a>
wrote:<br>
<blockquote
cite="mid:631312948.9722221254325255153.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Your
process is what I would do. Get it running to the version you have now
offline and then once you have restored everything from backup shut
down the publisher, plug it in and then restart it. once it is
restarted, you will have to restart the TFTP server and other
subscribers.<br>
<br>
Hopefully you don't have to republish the databases. But if you do, you
can use the dbhelper tool to do that.<br>
<br>
Hopefully others will help.<br>
<br>
P.S. If your TAC engineer is not familiar with 4.1, then I would ask to
have the case escalated to someone who has 4.1 experience.<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt<br>
<br>
<br>
----- Original Message -----<br>
From: "Dane" <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:dane@pktloss.net" target="_blank"><dane@pktloss.net></a><br>
To: <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Sent: Wednesday, September 30, 2009 11:21:46 AM GMT -05:00 US/Canada
Eastern<br>
Subject: [cisco-voip] Restoring 4.1(3)sr5d Publisher?<br>
<br>
We had a drive fail on our publisher and had someone swap it out last<br>
night. Well it seems they made a couple of mistakes and left me no<br>
option but having to rebuild and restore now.<br>
<br>
Were running 4.1(3)sr5d and have a current BARS backup.<br>
<br>
Problem is all the media we have is some what old so I am having to<br>
install and upgrade and upgrade and upgrade to get back to where we<br>
were.<br>
<br>
My concern centers around the fact that this is the publisher that is<br>
down and having to be rebuilt using older media and then upgrading to<br>
get back to the point we were. Is there a risk in corrupting or<br>
interrupting the subscriber that is currently operational and running<br>
everything? I am afraid of the publisher coming back online too early<br>
during the process and somehow overwriting information on the<br>
subscriber before the publisher is fully built.<br>
<br>
My TAC engineer isn't familiar with the 4.1 release and windows side<br>
of things. Currently the plan he suggests based on the media we have<br>
available is to install 4.0.2 (from media) offline (unplug cable),<br>
then upgrade it to 4.1(3), then upgrade to 4.1(3)sr5d, then install<br>
BARS from that version of CM and do the restore of the BARS backup<br>
data.<br>
<br>
Does this sound right to others?<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>