[prev in list] [next in list] [prev in thread] [next in thread]
List: cisco-voip
Subject: Re: [cisco-voip] Migrating a Cisco 2901 to a Cisco 4321
From: Matthew Collins <mcollins () block ! co ! uk>
Date: 2017-05-15 12:39:31
Message-ID: 1D89CCC3241F774EA55C1FCF4564973A01F188B47B () BSMAIL001 ! blocksolutions ! local
[Download RAW message or body]
[Attachment #2 (text/plain)]
Unrelated to DSP but check out
http://www.cisco.com/c/en/us/support/docs/field-notices/641/fn64190.html
Router shows up as 98% memory utilisation when running IOS XE 3.X
Regards
Matthew Collins
From: cisco-voip [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ryan Huff
Sent: 12 May 2017 21:21
To: NateCCIE <nateccie@gmail.com>
Cc: Cisco VOIP <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Migrating a Cisco 2901 to a Cisco 4321
What I am trying to express, although perhaps worded ambiguously, is that all your \
TDM resources are on the NIM and that I don't believe you could share the DSP from \
the backplane along with the NIM resources, for the purposes of TDM.
I would agree that you are correct, in that any unallocated DSP on a NIM could be \
configured for other dspfarm tasks (Ex. Transcoding/Transrating, Hardware MTP .. \
etc).
http://www.cisco.com/c/en/us/support/docs/routers/4000-series-integrated-services-routers/118792-config-isr-00.html
Sent from my iPhone
On May 12, 2017, at 4:03 PM, NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>> \
wrote: What do mean by shareable to the backplane? It is my understanding that \
unused DSPs on a NIM can be used for conferencing/transcoding/MTP.
Sent from my iPhone
On May 12, 2017, at 2:00 PM, Ryan Huff \
<ryanhuff@outlook.com<mailto:ryanhuff@outlook.com>> wrote: I think that is where my \
lack of specificity comes into play; the NIM conversation I thought I was \
participating in was an extension of a convo this AM, regarding a T1 PRI, in which \
those DSP are reserved for TDM only, and not shareable to the backplane or vice a \
versa.
Thanks,
Ryan
On May 12, 2017, at 3:46 PM, NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>> \
wrote: TDM DSPs on the 4ks have to be on the NIM because there is no shared TDM \
clocking backplane like there is on the ISRs/ISR G2.
Dspfarm stuff can use extra dsps on a NIM and the motherboard DSPs can only be used \
for dspfarm tasks.
Sent from my iPhone
On May 12, 2017, at 1:35 PM, Jose Colon II \
<jcolon424@gmail.com<mailto:jcolon424@gmail.com>> wrote: I was under the same \
assumption of why there was a dsp slot on the NIM. I know I read a Cisco doc \
somewhere that lead me that direction.
On May 12, 2017 2:28 PM, "Ryan Huff" \
<ryanhuff@outlook.com<mailto:ryanhuff@outlook.com>> wrote: So this is interesting; I \
was under the impression the backplane DSP could not extend to the NIM (and is the \
fundamental reason, among others, that the NIM has its own DSP) .... looks like I \
have a new lab task :).
On May 12, 2017, at 3:09 PM, Anthony Holloway \
<avholloway+cisco-voip@gmail.com<mailto:avholloway+cisco-voip@gmail.com>> wrote: \
Rashmi Patel ( \
rashmika.patel@zones.com<mailto:rashmika.patel@zones.com> ) - 12:31 \
PM
Q: Does that mean conference resource will be used from NIM DSP not from mother board \
DSP resources
Priority: N/A
Dolan Spitler - 12:57 PM
A: When it comes to IP services (xcoding, conferencing, MTP) The motherboard DSP can \
be pooled with the NIM DSPs to increase the DSPfarm scale
Source: https://communities.cisco.com/docs/DOC-7823 (look for the 4000 event on Oct \
16th)
On Fri, May 12, 2017 at 1:17 PM Brian Meade <bmeade90@vt.edu<mailto:bmeade90@vt.edu>> \
wrote: My understanding is any dspfarm resources such as conferencing/transcoding use \
the motherboard resources while the ones on the NIM are just for the voice ports \
themselves.
On Fri, May 12, 2017 at 11:51 AM, Jose Colon II \
<jcolon424@gmail.com<mailto:jcolon424@gmail.com>> wrote: If you will be using DSP's \
you will need to decided if you will need them on the motherboard or on the T1 NIM. \
On the motherboard I believe it can only be used for conferencing. You will need them \
on the NIM for transcoding.
On May 12, 2017 6:42 AM, "Ryan Huff" \
<ryanhuff@outlook.com<mailto:ryanhuff@outlook.com>> wrote: T1 PRI commands are \
substantially different if that is in play.
Sent from my iPhone
On May 12, 2017, at 7:35 AM, Matthew Loraditch \
<MLoraditch@heliontechnologies.com<mailto:MLoraditch@heliontechnologies.com>> wrote: \
The vast majority of commands are the same. Netflow stuff is changed completely if \
you use that. Outside of updating interface names, most of our templates just \
worked.
Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
Network Engineer
Direct Voice: 443.541.1518<tel:(443)%20541-1518>
Facebook<https://www.facebook.com/heliontech?ref=hl> | \
Twitter<https://twitter.com/HelionTech> | \
LinkedIn<https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> | \
G+<https://plus.google.com/+Heliontechnologies/posts>
From: cisco-voip [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of \
norm.nicholson@kitchener.ca<mailto:norm.nicholson@kitchener.ca>
Sent: Friday, May 12, 2017 7:31 AM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] Migrating a Cisco 2901 to a Cisco 4321
We have a base config we use for building our 2901/11's . Will this work on the 4321 \
or do I have to start from scratch.
Thanks
Norm Nicholson
Telecom Analyst
City of Kitchener
(519) 741-2200 x 7000<tel:(519)%20741-2200>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
[Attachment #3 (text/html)]
<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: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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Unrelated to DSP but \
check out <o:p></o:p></span></p>
<p class="MsoNormal"><span \
style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p \
class="MsoNormal"><a \
href="http://www.cisco.com/c/en/us/support/docs/field-notices/641/fn64190.html">http://www.cisco.com/c/en/us/support/docs/field-notices/641/fn64190.html</a><span \
style="mso-fareast-language:EN-US"><o:p></o:p></span></p> <p class="MsoNormal"><span \
style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <p \
class="MsoNormal"><span style="mso-fareast-language:EN-US">Router shows up as 98% \
memory utilisation when running IOS XE 3.X <o:p></o:p></span></p>
<p class="MsoNormal"><span \
style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Century \
Gothic",sans-serif;color:#009DB1">Regards<o:p></o:p></span></p> <p \
class="MsoNormal"><span style="font-size:10.0pt;font-family:"Century \
Gothic",sans-serif;color:#009DB1"><o:p> </o:p></span></p> <p \
class="MsoNormal"><span style="font-size:10.0pt;font-family:"Century \
Gothic",sans-serif;color:#009DB1">Matthew Collins </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span \
style="mso-fareast-language:EN-US"><o:p> </o:p></span></p> <div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> \
cisco-voip [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Ryan \
Huff<br> <b>Sent:</b> 12 May 2017 21:21<br>
<b>To:</b> NateCCIE <nateccie@gmail.com><br>
<b>Cc:</b> Cisco VOIP <cisco-voip@puck.nether.net><br>
<b>Subject:</b> Re: [cisco-voip] Migrating a Cisco 2901 to a Cisco \
4321<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">What I am trying to express, although perhaps worded \
ambiguously, is that all your TDM resources are on the NIM and that I don't believe \
you could share the DSP from the backplane along with the NIM resources, for the \
purposes of TDM.<o:p></o:p></p> </div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">I would agree that you are correct, in that any unallocated DSP \
on a NIM could be configured for other dspfarm tasks (Ex. Transcoding/Transrating, \
Hardware MTP .. etc).<o:p></o:p></p> </div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><a \
href="http://www.cisco.com/c/en/us/support/docs/routers/4000-series-integrated-service \
s-routers/118792-config-isr-00.html">http://www.cisco.com/c/en/us/support/docs/routers/4000-series-integrated-services-routers/118792-config-isr-00.html</a><br>
<br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2017, at 4:03 PM, NateCCIE <<a \
href="mailto:nateccie@gmail.com">nateccie@gmail.com</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">What do mean by shareable to the backplane? It is my \
understanding that unused DSPs on a NIM can be used for conferencing/transcoding/MTP. \
<br> <br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2017, at 2:00 PM, Ryan Huff <<a \
href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">I think that is where my lack of specificity comes into play; \
the NIM conversation I thought I was participating in was an extension of a convo \
this AM, regarding a T1 PRI, in which those DSP are reserved for TDM only, and not \
shareable to the backplane or vice a versa.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Ryan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2017, at 3:46 PM, NateCCIE <<a \
href="mailto:nateccie@gmail.com">nateccie@gmail.com</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">TDM DSPs on the 4ks have to be on the NIM because there is no \
shared TDM clocking backplane like there is on the ISRs/ISR G2. <o:p></o:p></p> \
</div> <div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Dspfarm stuff can use extra dsps on a NIM and the motherboard \
DSPs can only be used for dspfarm tasks. <o:p></o:p></p> </div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2017, at 1:35 PM, Jose Colon II <<a \
href="mailto:jcolon424@gmail.com">jcolon424@gmail.com</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">I was under the same assumption of why there was a dsp slot on \
the NIM. I know I read a Cisco doc somewhere that lead me that \
direction.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On May 12, 2017 2:28 PM, "Ryan Huff" <<a \
href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<o:p></o:p></p> \
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm \
6.0pt;margin-left:4.8pt;margin-right:0cm"> <div>
<div>
<p class="MsoNormal">So this is interesting; I was under the impression the backplane \
DSP could not extend to the NIM (and is the fundamental reason, among others, that \
the NIM has its own DSP) .... looks like I have a new lab task :).<o:p></o:p></p> \
</div> <div id="m_6945223396453311172AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">On May 12, 2017, at 3:09 PM, \
Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" \
target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">Rashmi Patel ( <a href="mailto:rashmika.patel@zones.com" \
target="_blank"> rashmika.patel@zones.com</a> ) - 12:31 PM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Q: Does that mean conference resource will be used from NIM DSP \
not from mother board DSP resources<o:p></o:p></p> </div>
<div>
<p class="MsoNormal">Priority: N/A<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Dolan Spitler - 12:57 PM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">A: When it comes to IP services (xcoding, conferencing, MTP) The \
motherboard DSP can be pooled with the NIM DSPs to increase the DSPfarm \
scale<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Source: <a \
href="https://communities.cisco.com/docs/DOC-7823" \
target="_blank">https://communities.cisco.com/docs/DOC-7823</a> (look for the \
4000 event on Oct 16th)<o:p></o:p></p> </div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, May 12, 2017 at 1:17 PM Brian Meade <<a \
href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>> \
wrote:<o:p></o:p></p> </div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm \
6.0pt;margin-left:4.8pt;margin-right:0cm"> <div>
<p class="MsoNormal">My understanding is any dspfarm resources such as \
conferencing/transcoding use the motherboard resources while the ones on the NIM are \
just for the voice ports themselves.<o:p></o:p></p> </div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, May 12, 2017 at 11:51 AM, Jose Colon II <<a \
href="mailto:jcolon424@gmail.com" target="_blank">jcolon424@gmail.com</a>> \
wrote:<o:p></o:p></p> <blockquote style="border:none;border-left:solid #CCCCCC \
1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div>
<p class="MsoNormal">If you will be using DSP's you will need to decided if you will \
need them on the motherboard or on the T1 NIM. On the motherboard I believe it can \
only be used for conferencing. You will need them on the NIM for \
transcoding.<o:p></o:p></p> </div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On May 12, 2017 6:42 AM, "Ryan Huff" <<a \
href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> \
wrote:<o:p></o:p></p> <blockquote style="border:none;border-left:solid #CCCCCC \
1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div>
<div>
<p class="MsoNormal">T1 PRI commands are substantially different if that is in \
play.<br> <br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2017, at 7:35 AM, Matthew Loraditch <<a \
href="mailto:MLoraditch@heliontechnologies.com" \
target="_blank">MLoraditch@heliontechnologies.com</a>> wrote:<o:p></o:p></p> \
</div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="color:#1F497D">The vast majority of commands are the same. Netflow stuff is \
changed completely if you use that. Outside of updating interface names, most \
of our templates just worked.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="color:#1F497D"> </span><o:p></o:p></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="color:#1F497D"> </span><o:p></o:p></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="color:#1F497D"> </span><o:p></o:p></p> <div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span \
style="font-size:10.0pt;color:#1F497D">Matthew G. Loraditch – CCNP-Voice, \
CCNA-R&S, CCDA<br> Network Engineer<br>
Direct Voice: <a href="tel:(443)%20541-1518" \
target="_blank">443.541.1518</a></span><o:p></o:p></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="color:#1F497D"><a href="https://www.facebook.com/heliontech?ref=hl" \
target="_blank"><span style="font-size:8.0pt">Facebook</span></a></span><span \
style="font-size:8.0pt;color:#1F497D"> | </span><span style="color:#1F497D"><a \
href="https://twitter.com/HelionTech" target="_blank"><span \
style="font-size:8.0pt">Twitter</span></a></span><span \
style="font-size:8.0pt;color:#1F497D"> | </span><span style="color:#1F497D"><a \
href="https://www.linkedin.com/company/helion-technologies?trk=top_nav_home" \
target="_blank"><span style="font-size:8.0pt">LinkedIn</span></a></span><span \
style="font-size:8.0pt;color:#1F497D"> | </span><span style="color:#1F497D"><a \
href="https://plus.google.com/+Heliontechnologies/posts" target="_blank"><span \
style="font-size:8.0pt">G+</span></a></span><o:p></o:p></p> </div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span \
style="color:#1F497D"> </span><o:p></o:p></p> <div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> cisco-voip \
[<a href="mailto:cisco-voip-bounces@puck.nether.net" \
target="_blank">mailto:cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b><a \
href="mailto:norm.nicholson@kitchener.ca" \
target="_blank">norm.nicholson@kitchener.ca</a><br> <b>Sent:</b> Friday, May 12, 2017 \
7:31 AM<br> <b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" \
target="_blank">cisco-voip@puck.nether.net</a><br> <b>Subject:</b> [cisco-voip] \
Migrating a Cisco 2901 to a Cisco 4321<o:p></o:p></p> </div>
</div>
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We \
have a base config we use for building our 2901/11's . Will this work on the 4321 or \
do I have to start from scratch. <o:p></o:p></p>
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thanks<o:p></o:p></p>
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span \
style="color:#00B050">Norm Nicholson</span></b><o:p></o:p></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span \
style="color:#00B050">Telecom Analyst</span></b><o:p></o:p></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span \
style="color:#00B050">City of Kitchener</span></b><o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span \
style="color:#00B050"><a href="tel:(519)%20741-2200" target="_blank">(519) 741-2200 x \
7000</a></span></b><o:p></o:p></p> <p class="MsoNormal" \
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p> <p \
class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<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></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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></p>
</blockquote>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">_______________________________________________<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></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<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></p>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<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></p>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</body>
</html>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--===============1328153678592615593==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic