[cisco-voip] Migrating a Cisco 2901 to a Cisco 4321

[Matthew Collins]

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 at puck.nether.net] On Behalf Of Ryan Huff
Sent: 12 May 2017 21:21
To: NateCCIE <nateccie at gmail.com>
Cc: Cisco VOIP <cisco-voip at 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 at gmail.com<mailto:nateccie at 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 at outlook.com<mailto:ryanhuff at 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 at gmail.com<mailto:nateccie at 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 at gmail.com<mailto:jcolon424 at 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 at outlook.com<mailto:ryanhuff at 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 at gmail.com<mailto:avholloway+cisco-voip at gmail.com>> wrote:
Rashmi Patel ( rashmika.patel at zones.com<mailto:rashmika.patel at 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 at vt.edu<mailto:bmeade90 at 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 at gmail.com<mailto:jcolon424 at 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 at outlook.com<mailto:ryanhuff at 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 at heliontechnologies.com<mailto:MLoraditch at 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 at puck.nether.net] On Behalf Of norm.nicholson at kitchener.ca<mailto:norm.nicholson at kitchener.ca>
Sent: Friday, May 12, 2017 7:31 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at 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 at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170515/2ca20ca5/attachment.html>