<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I've found it useful to put your duplicate network behind separate
NAT router.<br>
<br>
Create a L2 (only L2, no L3 interface) VLAN on your production
network, call it "Isolated"<br>
Pick a L2/L3 network that can be your NAT "outside" This network
should be fully reachable in the enterprise and have some free IP
addresses on it (like 5-10 free addresses)<br>
<br>
Find a separate physical router (like an old 28xx), Connect the
outside interface to your switch on an access port that was selected
for the NAT "outside"<br>
Connect the inside interface of the router to your switch on a port
mapped to the "isolated" L2-only network<br>
<br>
On the NAT router inside interface create the duplicate IP network
as your production UC network<br>
(don't run any routing protocols, just use a static default on the
NAT router to get back to the core network for mgmt)<br>
On the NAT router outside, assign an IP to the interface for
management. Then configure simple 1:1 NATs for each of your voice
servers. Trunk the "isolated", L2 only, VLAN into your VMware host
and assign to the guest UC VMs<br>
<br>
Since the duplicate IP interface only exists on the NAT router
"inside" interface and you don't have any L3 IP address created on
the isolated VLAN, your duplicate network is safely isolated yet
reachable.<br>
<br>
You'll be able to reach the voice servers via the NAT "outside"
address<br>
The voice servers will be able to "reach out" to the production
network for NTP, LDAP. sFTP, etc. but appear to come from the NAT
address.<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/20/2015 9:40 AM, Lelio Fulgenzi
wrote:<br>
</div>
<blockquote
cite="mid:1041450529.44186171.1445352039520.JavaMail.zimbra@uoguelph.ca"
type="cite">
<div style="font-family: Verdana; font-size: 10pt; color: #000000">
<div><br>
</div>
<div>My major concern is IP address conflicts. Right now, with
my offline network, it's completely isolated, with the UCS
solution, unless I buy a UCS server(s) that is sized
accordingly to hold the VMs sized for my production
environment (which is unlikely), I'll have to consider feeding
the UCS servers with the offline network which is a duplicate
of the production network.</div>
<div><br>
</div>
<div>While technically possible, it would mean that the entire
team be aware of this special configuration and not mess with
anything that could bridge the configurations and cause IP
address conflicts. I'm envisioning a separate network cable
plugged into our offline switch/routers that would connect to
the UCS server(s) in a separate VLAN. Unfortunately, I'm not
up to speed with the intricacies of the UCS systems and VM,
etc. and whether or not that would cause issues.</div>
<div><br>
</div>
<div>As with other organizations, we're under pressure to keep
systems up and running 24 hours a day. We're improving our
service availability design to hopefully help us going
forward. For example, building an almost exact duplicate of
our auto-attendant and call processing on Unity Express, so
that we can do work on Connection while peoples business can
continue at 3 in the morning while we do work. </div>
<div><br>
</div>
<div>We may revisit the offline upgrade in lieu of an inplace
upgrade, but I'm not sure we're there yet.</div>
<div><br>
</div>
<div>Lelio</div>
<div><br>
</div>
<div><br>
</div>
<div><span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst, Network Infrastructure<br>
Computing and Communications Services (CCS)<br>
University of Guelph<br>
<div><br>
</div>
519‐824‐4120 Ext 56354<br>
<a class="moz-txt-link-abbreviated" href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.uoguelph.ca/ccs">www.uoguelph.ca/ccs</a><br>
Room 037, Animal Science and Nutrition Building<br>
Guelph, Ontario, N1G 2W1<span name="x"></span><br>
</div>
<div><br>
</div>
<hr id="zwchr">
<div
style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"
data-mce-style="color: #000; font-weight: normal; font-style:
normal; text-decoration: none; font-family:
Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Ryan
Huff" <a class="moz-txt-link-rfc2396E" href="mailto:ryanhuff@outlook.com"><ryanhuff@outlook.com></a><br>
<b>To: </b>"Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
<b>Cc: </b>"Kevin Przybylowski"
<a class="moz-txt-link-rfc2396E" href="mailto:kevinp@advancedtsg.com"><kevinp@advancedtsg.com></a>, "Anthony Holloway"
<a class="moz-txt-link-rfc2396E" href="mailto:avholloway+cisco-voip@gmail.com"><avholloway+cisco-voip@gmail.com></a>, "Cisco VoIP Group"
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Sunday, October 18, 2015 7:04:42 PM<br>
<b>Subject: </b>Re: [cisco-voip] How Many Docs Does it Take
to Prep for an Upgrade?<br>
<div><br>
</div>
<div>Lelio, what challenges are you facing in your next
upgrade on UCS?</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">I don't think staging is so much
'the old way of doing it' as much as it is depending on the
engagement and timeline, in my opinion. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">If the target environment is only
sized for the production VMs (and your coming from MCS) ....
it might be difficult to do a bridge in the target
environment. In that case, I would advocate pulling the DRS
and upgrading offnet, unless the customer can spin-up an
sftp server that you can use to shuffle DRS on. At that
point though, I'd say it is going to take just as long, one
way or the other.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Virtual to virtual with plenty of
room in the datastores can certainly, and easily be done
onnet. In place upgrades are another great case for onnet
upgrades without staging.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">As Anthony mentioned earlier, PCD
is only valuable (IMO) in a rather limited set of
circumstances and has enough nuances that I don't bother
with it. PCD has a ways to go before I'd consider using it
in practice; it's a good idea -just too early for me.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Some organizations have
change-controls that mandate major upgrades be ran in
tandem/staged, then switched once signed off on. In those
cases, I'll usually advocate upgrading the device loads on
the current version before the switch, so at least the
phones move over quick.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Thanks,</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Ryan</div>
<div id="AppleMailSignature"><br>
Sent from my iPad</div>
<div><br>
On Oct 18, 2015, at 6:36 PM, Lelio Fulgenzi <<a
moz-do-not-send="true" href="mailto:lelio@uoguelph.ca"
target="_blank" data-mce-href="mailto:lelio@uoguelph.ca"><a class="moz-txt-link-abbreviated" href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a></a>>
wrote:<br>
<div><br>
</div>
</div>
<blockquote>
<div>
<div>We've built an offline network where we have staged
the last couple of upgrades. It's worked out well. We
basically test everything we can to ensure operability.
The day of the cutover there's an overall downtime of
about 90 minutes but some things come up sooner. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">I'm hoping to come up with a
similar approach to the next one. But it would be using
ucs so I'm not sure how to make that work just yet. <br>
<div><br>
</div>
Sent from my iPhone</div>
<div><br>
On Oct 16, 2015, at 3:52 PM, Kevin Przybylowski <<a
moz-do-not-send="true"
href="mailto:kevinp@advancedtsg.com" target="_blank"
data-mce-href="mailto:kevinp@advancedtsg.com"><a class="moz-txt-link-abbreviated" href="mailto:kevinp@advancedtsg.com">kevinp@advancedtsg.com</a></a>>
wrote:<br>
<div><br>
</div>
</div>
<blockquote>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
data-mce-style="font-size: 11.0pt; font-family:
'Calibri',sans-serif; color: #1f497d;">It is
very time consuming to stage in the lab…
Installs, DRS’s, Upgrades, etc… I’ve only done
them in the past if there was a large gap in
versions. It looks like PCD PCD is getting
better so it looks like a valid option nowadays
for bare metal to esx migration/upgrades. </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
data-mce-style="font-size: 11.0pt; font-family:
'Calibri',sans-serif; color: #1f497d;"> </span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"
data-mce-style="font-size: 11.0pt;
font-family: 'Calibri',sans-serif;">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"
data-mce-style="font-size: 11.0pt; font-family:
'Calibri',sans-serif;"> cisco-voip [<a
moz-do-not-send="true"
href="mailto:cisco-voip-bounces@puck.nether.net"
target="_blank"
data-mce-href="mailto:cisco-voip-bounces@puck.nether.net"><a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a></a>]
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Friday, October 16, 2015 3:42 PM<br>
<b>To:</b> Ryan Huff <<a
moz-do-not-send="true"
href="mailto:ryanhuff@outlook.com"
target="_blank"
data-mce-href="mailto:ryanhuff@outlook.com"><a class="moz-txt-link-abbreviated" href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a></a>><br>
<b>Cc:</b> Cisco VoIP Group <<a
moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net"
target="_blank"
data-mce-href="mailto:cisco-voip@puck.nether.net"><a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></a>><br>
<b>Subject:</b> Re: [cisco-voip] How Many Docs
Does it Take to Prep for an Upgrade?</span></p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">You sound more organized than
I am. I would like to see what you have, sure.
Thanks for the offer.</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I've never staged an
upgrade in my lab, though I have heard of
plenty of people doing this. Is it really
something to consider or is that a thing of
the past? Like pulling a drive from the
array? Not too mention, I rarely have time to
perform two upgrades on a project like this.
I barely get enough time to upgrade the system
once.</p>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Fri, Oct 16, 2015 at
1:56 PM, Ryan Huff <<a
moz-do-not-send="true"
href="mailto:ryanhuff@outlook.com"
target="_blank"
data-mce-href="mailto:ryanhuff@outlook.com"><a class="moz-txt-link-abbreviated" href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a></a>>
wrote:</p>
<blockquote style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in"
data-mce-style="border: none; border-left:
solid #CCCCCC 1.0pt; padding: 0in 0in 0in
6.0pt; margin-left: 4.8pt; margin-right: 0in;">
<div>
<div>
<p class="MsoNormal">I use an excel spread
sheet with a hyperlink to the base doc
in one sheet with notes and details
gathered in the sheet.Then I create
additional worksheets of subordinate
documentation and notes and then make
references from the base sheet to the
subordinate sheets. I also have a sheet
for customer discovery (current dns, ip,
device loads .... etc). It ends up
looking a lot like a Gantt chart.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">If you'd like, I can
sanitize and send one to you, to compare
notes and see if there is anything of
use to you.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Also, If time
permits, and it's feasible, I like to
stage a mock upgrade in my lab with
customer data (drs ... etc) and do a dry
run.</p>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"
data-mce-style="margin-bottom: 12.0pt;"><br>
<br>
-------- Original message --------<br>
From: Anthony Holloway <br>
Date:10/16/2015 2:38 PM (GMT-05:00) <br>
To: Cisco VoIP Group <br>
Subject: [cisco-voip] How Many Docs Does
it Take to Prep for an Upgrade?</p>
<div>
<p class="MsoNormal">Does anyone else do
this? Gather all of the documentation
ahead of time, because inevitably you're
going to revisit a document more than
once? There are a lot of documents to
gather! Anything I could be doing
better? Tips? Tricks?</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I create a
spreadsheet of all of the pertinent
documents I need to review or
reference, like in this screenshot.
There's over 90 documents in this
list. Granted, I don't read them all
front to back, but some I do, and for
others I need to reference information
within them nonetheless. You never
know when you might find a small font
hidden note in there.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">E.g., From the 8945
Release Notes</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><i>"Release
9.4(2)SR1 can only be upgraded from
9.3(4) and later. Releases prior to
9.3(4) have to be upgraded to 9.3(4)
first."</i></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><i>Source: <a
moz-do-not-send="true"
href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8941_8945/firmware/9_4_2SR1/english/release_notes/P415_BK_RB1FD4B7_00_release-notes-942sr1.html#P415_TK_IA5F5D63_00"
target="_blank"
data-mce-href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8941_8945/firmware/9_4_2SR1/english/release_notes/P415_BK_RB1FD4B7_00_release-notes-942sr1.html#P415_TK_IA5F5D63_00">
8945 9.4(2)SR1 Release Notes</a></i></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I actually missed
this one recently, and unlike 7900
series phones, they phone will just
brick itself and never register.
Causing you to walk to every phone and
reset power to it, or walk the mac
address tables of your layer 2 network
and shut/no shut the ports.</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</blockquote>
<blockquote>
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net"
target="_blank"
data-mce-href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br>
<span><a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank"
data-mce-href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</div>
</blockquote>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>