[cisco-voip] router selection......
Norton, Mike
mikenorton at pwsd76.ab.ca
Fri May 24 18:21:38 EDT 2013
Well, in my environment, we rarely buy SmartNet (various reasons), but good point.
As for what routing duties a Layer 3 switch can do, there are limitations. Everything I needed was easily doable with the top-level IOS license on the 3560-X (which doubles its price), but certainly wouldn’t work for everyone.
QoS, policing, shaping, etc. are fairly doable, though IIRC some things can only be done ingress *or* egress, whereas an ISR could do the same tasks in both directions simultaneously. Firewalling is just simple ACLs obviously, and you have to plan them carefully to make sure they get processed in ASIC and not CPU.
It does look pretty ridiculous having 22 empty dust receptacles on the front, but same is true of the 3550 that my WAN provider uses as their demarc. Once at the end of their useful routing life, they can be repurposed into non-critical places as access switches.
-mn
From: Scott Voll [mailto:svoll.voip at gmail.com]
Sent: May-24-13 2:37 PM
To: Lelio Fulgenzi
Cc: Norton, Mike; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] router selection......
Yes, but...... now your also buying Smartnet on two devices. But I do get your point. Difficult piece is does your layer 3 switch support QoS. Policing, shaping, etc?
Scott
On Fri, May 24, 2013 at 10:54 AM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:
that's a very good point Mike. most of the time the licenses are not transferable. sometimes modules are though, sometimes. ;)
---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph
519‐824‐4120 Ext 56354<tel:519%E2%80%90824%E2%80%904120%20Ext%2056354>
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Mike Norton" <mikenorton at pwsd76.ab.ca<mailto:mikenorton at pwsd76.ab.ca>>
To: "Scott Voll" <svoll.voip at gmail.com<mailto:svoll.voip at gmail.com>>, cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Friday, May 24, 2013 1:21:19 PM
Subject: Re: [cisco-voip] router selection......
Add my vote for separating routing and voice. That way when you outgrow your routing capacity, you’re not forced to buy new voice gateway capabilities. Or vise-versa.
Last summer I replaced all my ISR G1s with Layer 3 switches for WAN routing and 2901s for voice gateway. Now, next time we outgrow the routing capacity, we won’t have to buy new VWICs, SRST licensing, etc. because the voice gateway won’t need to change. Or when CUCM upgrades make the voice gateway IOS obsolete, we won’t need to buy new WAN routing.
-mn
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Scott Voll
Sent: May-24-13 8:53 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>; cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
Subject: [cisco-voip] router selection......
Sorry for the cross post. But I wasn't sure which was the better forum to post in.
I currently have a 2951 running voice, Security, VPN, and Data. it works really great for our current needs. BUT we are going to start pushing more that 300mbps and this router is only rated for 296mbps per the spec sheet.
What is the next move up to support up to gig throughput and still support ZBFW, GRE, IPSEC, PRI's for Voice, and QoS at Gig speeds?
Do I have to separate out my WAN (use an ASR) and then continue with the 2951 for my security / voice?
What are my options?
Thanks
Scott
_______________________________________________
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/20130524/c51ba84b/attachment.html>
More information about the cisco-voip
mailing list