<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>I'd have to agree with Dennis, and not just because we work at the same company. :)</div>
<div><br>
</div>
<div>Yes, bandwidth is cheap, Erick. However, experience has shown that a branch office running a few bonded T1s or T3s isn't going to be as reliable as a customers data center LAN. If you put a subscriber out at a remote site, running on an ISR G2, can you
image the impact of that site's circuit was flapping over a few days (carriers aren't always the quickest to dispatch)?</div>
<div><br>
</div>
<div>I would rather keep my CUCM servers in 1-2 data centers with some sort of other resilient data connection in between. If one of the branches has a circuit flap issue, only that branch is affected, not the entire environment.</div>
<div><br>
</div>
<div>Scalability is another thing. Unless you setup a supercluster, you're not going to get past the eight subscriber limitation in CUCM. You're going to wind up with some sites running off a remote CUCM anyway.</div>
<div><br>
</div>
<div>Last thing… Cisco is extremely strict regarding the hardware requirements for virtualized UC servers. I can't imagine them ever approving an ESXi-based UC solution running off a service module. Even the SRE-910SM falls short with a Intel Core Duo, 1.86
Ghz and 8GB of RAM. Such a setup would only potentially be able to support a single UC virtualized application.</div>
<div>
<div><span class="Apple-style-span" style="font-size: medium; "><font class="Apple-style-span" face="Calibri"><br>
Thanks!<br>
<br>
Matthew Berry, CCIE #26721 (Voice) <br>
CDW | Sr. Unified Communications Engineer <br>
Single Number Reach: +1.763.592.5987 <br>
Email: matthew.berry@cdw.com<br>
</font></span></div>
<div><span class="Apple-style-span" style="font-family: monospace; font-size: medium; "><br>
</span></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Wellnitz, Erick A." <<a href="mailto:erick.wellnitz@kattenlaw.com">erick.wellnitz@kattenlaw.com</a>><br>
<span style="font-weight:bold">Date: </span>Tue, 30 Aug 2011 16:59:50 +0000<br>
<span style="font-weight:bold">To: </span>Dennis Heim <<a href="mailto:Dennis.Heim@cdw.com">Dennis.Heim@cdw.com</a>>, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>>, Nick Matthews <<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [cisco-voip] UCS chassis redundancy<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">We already do it with standard server hardware. Database replication is a non-issue. Bandwidth is cheap. Upgrades aren’t a problem seeing as
they can be staged and run the ‘switch version’ command at a later time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Lower bandwidth situations would be a no go.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Dennis Heim<br>
<b>Sent:</b> Tuesday, August 30, 2011 11:54 AM<br>
<b>To:</b> Lelio Fulgenzi; Nick Matthews<br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] UCS chassis redundancy<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">I am going to go with “NO” on that. Imagine database replication across all sites? Imagine doing major version upgrades.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; color: rgb(31, 73, 125); font-family: Arial, sans-serif; ">Dennis Heim<br>
Network Voice Engineer<br>
CDW Advanced Technology Services<br>
10610 9<sup>th</sup> Place<br>
Bellevue, WA 98004<br>
<br>
317.569.4255 Single Number Reach<br>
317.569.4201 Fax</span><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><br>
<a href="mailto:dennis.heim@cdw.com"><span style="font-size:10.0pt">dennis.heim@cdw.com</span></a></span><u><span style="font-size: 11pt; color: blue; font-family: Calibri, sans-serif; "><br>
</span></u><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><a href="http://www.cdw.com/content/solutions/unified-communications/">cdw.com/content/solutions/unified-communications/</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">
<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Tuesday, August 30, 2011 8:51 AM<br>
<b>To:</b> Nick Matthews<br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] UCS chassis redundancy<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; ">won't it be great when the VMware service modules on the ISR G2s support installing CUCM on it? a full subscriber at each remote
site. ;)<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>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; ">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; ">From:
</span></b><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; ">"Nick Matthews" <<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>><br>
<b>To: </b>"Erick A. Wellnitz" <<a href="mailto:erick.wellnitz@kattenlaw.com">erick.wellnitz@kattenlaw.com</a>><br>
<b>Cc: </b><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Sent: </b>Tuesday, August 30, 2011 11:42:59 AM<br>
<b>Subject: </b>Re: [cisco-voip] UCS chassis redundancy<br>
<br>
I'm seeing a lot of B-series at the data center and a C-series at a remote site or DR. Otherwise, a second chassis isn't *too* expensive. The bulk of the cost is in the blades and the 6100s. You still need power supplies, IO, chassis, but it's not too bad.
Seeing a decent amount of 2nd chassis as well. A lot of the DC types that are putting their blades in there as well help offset the cost.<br>
<br>
-nick<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; ">On Tue, Aug 30, 2011 at 9:46 AM, Wellnitz, Erick A. <<a href="mailto:erick.wellnitz@kattenlaw.com" target="_blank">erick.wellnitz@kattenlaw.com</a>> wrote:<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Has anyone had issues with the UCS blade chassis being a single point of failure? What happens if the chassis itself fails? DO people have redundant
chassis installed? A C series UCS for disaster situations? <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">I don’t like having all my eggs in one basket.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:10.0pt;color:#333333">ERICK A. WELLNITZ
</span></b><span style="font-size:10.0pt;color:black"><br>
</span><span style="font-size:10.0pt;color:#333333">Network Engineer</span><span style="font-size:10.0pt;color:black"><br>
</span><b><span style="font-size:10.0pt;color:#83A6BD">Katten Muchin Rosenman LLP</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="background:white;padding:.75pt .75pt .75pt .75pt">
<pre><span style="color:black">===========================================================<o:p></o:p></span></pre>
<pre><span style="color:black">CIRCULAR 230 DISCLOSURE: Pursuant to Regulations Governing Practice Before the Internal Revenue<o:p></o:p></span></pre>
<pre><span style="color:black">Service, any tax advice contained herein is not intended or written to be used and cannot be used<o:p></o:p></span></pre>
<pre><span style="color:black">by a taxpayer for the purpose of avoiding tax penalties that may be imposed on the taxpayer.<o:p></o:p></span></pre>
<pre><span style="color:black">===========================================================<o:p></o:p></span></pre>
<pre><span style="color:black">CONFIDENTIALITY NOTICE:<o:p></o:p></span></pre>
<pre><span style="color:black">This electronic mail message and any attached files contain information intended for the exclusive<o:p></o:p></span></pre>
<pre><span style="color:black">use of the individual or entity to whom it is addressed and may contain information that is<o:p></o:p></span></pre>
<pre><span style="color:black">proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you<o:p></o:p></span></pre>
<pre><span style="color:black">are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or <o:p></o:p></span></pre>
<pre><span style="color:black">distribution of this information may be subject to legal restriction or sanction. Please notify<o:p></o:p></span></pre>
<pre><span style="color:black">the sender, by electronic mail or telephone, of any unintended recipients and delete the original <o:p></o:p></span></pre>
<pre><span style="color:black">message without making any copies.<o:p></o:p></span></pre>
<pre><span style="color:black">===========================================================<o:p></o:p></span></pre>
<pre><span style="color:black">NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has<o:p></o:p></span></pre>
<pre><span style="color:black">elected to be governed by the Illinois Uniform Partnership Act (1997).<o:p></o:p></span></pre>
<pre><span style="color:black">===========================================================<o:p></o:p></span></pre>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; "><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 10pt; color: black; font-family: Verdana, sans-serif; "><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
_______________________________________________ cisco-voip mailing list <a href="mailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net</a> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a> </span>
</body>
</html>