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

[Ryan Huff]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170512/88bccd4a/attachment.html>