<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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: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";}
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.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="http://www.cisco.com/en/US/prod/prod_warranty09186a00800b5594.html">http://www.cisco.com/en/US/prod/prod_warranty09186a00800b5594.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">No such thing as TAC Supported 3<sup>rd</sup> Party anything. That’s not to say you can’t use it though. It’s like asking the dealer for help with your aftermarket
Stereo. What the URL talks about is if you complain your steering wheel doesn’t work, and they figure it’s not working because of the new stereo they can charge you for the troubleshooting time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Nate<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Wednesday, November 30, 2011 2:57 PM<br>
<b>To:</b> Chase Voisin<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] ISR 2800 support in new CUCM 8.6 (and future<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:10.0pt;font-family:"Verdana","sans-serif";color:black">This is the first I've heard of TAC supported third party memory. Maybe the Cisco folk on the list can confirm/deny this?<br>
<br>
Is there a Cisco link which lists the approved 3rd party memory?<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">
<hr size="2" width="100%" align="center" id="zwchr">
</span></div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">"Chase Voisin" <<a href="mailto:chase.voisin@gmail.com">chase.voisin@gmail.com</a>><br>
<b>To: </b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>
<b>Cc: </b><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Sent: </b>Wednesday, November 30, 2011 4:53:46 PM<br>
<b>Subject: </b>Re: [cisco-voip] ISR 2800 support in new CUCM 8.6 (and future<br>
<br>
Here is an example.<br>
<br>
<a href="http://www.memoryx.net/mem2821512d.html">http://www.memoryx.net/mem2821512d.html</a><br>
<br>
This is some memory for a 2821. You can buy it and TAC will support<br>
it per the description.<br>
<br>
<br>
<br>
<br>
<br>
On Wed, Nov 30, 2011 at 1:35 PM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<br>
> "TAC certified memory from third party" ???<br>
><br>
> Can you provide references for this statement? I was under the impression<br>
> the only Cisco supported memory is Cisco memory.<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 (ANNU)<br>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
> Cooking with unix is easy. You just sed it and forget it.<br>
> - LFJ (with apologies to Mr. Popeil)<br>
><br>
><br>
> ________________________________<br>
> From: "Chase Voisin" <<a href="mailto:chase.voisin@gmail.com">chase.voisin@gmail.com</a>><br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Sent: Wednesday, November 30, 2011 1:55:44 PM<br>
> Subject: Re: [cisco-voip] ISR 2800 support in new CUCM 8.6 (and future<br>
><br>
><br>
> I saw this one and I recently went through this same process of<br>
> determining memory requirements. The most accurate way I know of<br>
> without opening the router to check the memory is do a show ver and<br>
> look for this line<br>
><br>
><br>
> Cisco 2811 (revision 53.51) with 247808K/14336K bytes of memory.<br>
><br>
> Take your memory since it is based on two separate components and add those<br>
> up<br>
><br>
> In this case it comes out to 262144. Divide that up by 1024 and you<br>
> get your total memory expressed in MB, in this case 256 MB, too little<br>
> to run IOS 15.1.x so upgrade was needed in this case.<br>
><br>
> We looked at memoryx for our memory and compared it to Cisco. Cisco<br>
> was over 10x the cost of some of the TAC certified memory from third<br>
> party.<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>
<p class=MsoNormal><span style='font-size:7.0pt';font-family:'"Helvetica","Tahoma","Arial","sans-serif"'><font color="#666666"><br><br> NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.</span><o:p></o:p></span></p><BR>
</DIV></body>
</html>