Equipment Support > Hardware By Brand > Cisco > Cisco router for fios 150/65 internet service

Cisco router for fios 150/65 internet service

reply to kevin108302
150 means gig-e ports... 2821, 2851, 891, and up. Anything with dual gig-e should be able to handle it. HOWEVER, the more services / nat'd connections, the slower it's going to get. An ASA5510 would do better under high-touch loads -- IPS/IDS, lots of NAT, etc. I know first hand a 2851 will not be able to push that much traffic (not even 45Mbps) with NAT enabled; pure routing, it has no problems.

reply to kevin108302
If you can afford it, I'd probably go with an ISR G2 router anyways.

Regards

reply to cramer
Thanks for the responses guys. I'm looking at the 1941 as a possible solution with the lowest cost. Will run NAT and possibly one or two VPN connections.

reply to kevin108302
For VPN, think you'll have to budget for a base+SEC licence, due to the whole 15.x licencing scheme.

Let us know how it goes.

Regards

reply to kevin108302
Decent choice, although depending on your traffic patterns and usage, an ASA might be a better choice if your on a budget.

I do know however, that one of our clients is running a 150/150 symmetric pipe with NAT, and is using a 3945 to do so (although it barely breaks a sweat with a peak of 40% and user base of 5k users).

reply to kevin108302
OC-3 speed WAN CKT a 3945 / 3945E class by Cisco's cookbook. Watch out, the ASA is can be "lost in multi speak" with IPS enablement, two ratings, TRANSACTIONAL (much slower, closer to real world, rarely published publicly by Cisco, and then to partners, usually about one-half of RICH-MEDIA), and RICH-MEDIA.

reply to kevin108302
I'd recommend a Fortinet 40C or a 60C or a Juniper SSG20

OT: How can you stand the CLI on the Fortinets Geek Kid?

OT: unlike you, I ain't anal about cli... Web configuration is where's it at on some gear. I don't dis a manufacturer just because of that and No Cisco can hang with Fortinet when it comes to performance...

reply to Da Geek Kid
I like the SSG20 better personally. The Fortinets sometimes have tunnel issues I've found.

reply to Da Geek Kid
lol its not about some elitest CLI preference geek, its about integration with provisioning systems that use the CLI. You cant run a provider by clicking around on a web gui for thousands of customers. It needs to be automated and template driven from a provisioning database, and that means a CLI interface for the tools to deploy changes.

aha... For that you would need FortiManager and you'd use the XML API to interact with your FortiGates. Just like CSM and NMS from Cisco and Juniper...

XML shouldnt be an issue (We have been dabbling in XML CLI with NXOS for a while) I will see if i can get an eval license for FortiMangler to go with our lab FortiGate.