Cisco 2514 a bottle kneck?

C

Carlosinfl

Loves the juice
Joined
Sep 25, 2002
Messages
6,633
According to my LAN setup, http://carlwill.com/network/LAN.png

I am being told the Cisco 2514 router will slow my network performance from broadbandreports forum members. I am not really sure and wanted to ask my fellow [H] members.

I am 100% aware that this type of equipment or setup is over kill in my network but with me, its "use it or lose it".

Thanks for any info you can provide.
 
how do you have 3 eth interfaces off of the 2514? I only see 2 AIU's and 2 Serial's being available with no expansion slots.
 
Why do you assume I have 3 ethernet interfaces on the 2514?

There are only 2.

From the smoothwall to the 2514 to the switch.
 
From the diagram it looks like the cable modem comes i your 'public' interface, the smoothwall is off a 'DMX' port and then the LAN is plugged into a 'private' port. I'm used to PIX's where that would be the typical setup.
Make the dashed arrow point to the smoothwall?
Why even have the Smoothwall? The 2514 and ACL's should be able to take care of pretty much everything for you.
How fast is your cable connection?
 
I use the 2514 at home and it works just fine for RR interweb. While it may be true that some people will say this maxes out around 3mbps or so, but traffic is king. It depends on what type of traffic you are sending, size of packets, destinations and sources.

Be sure to enable a few things for optimal performance:
Code: 
ip cef
!
interface Ethernetx
 no ip redirects
 no ip proxy-arp
 ip route-cache flow
!
no ip http server

I also do SNMP, NTP, NAT, SYSLOG, ACLs, QoS marking/policing and traffic shaping all on this box. You can see my stats here: http://www.osbjmg.com/mrtg/ (I haven't been uploading much lately, actually my 2514 was out of commission for a while because it took me some time to realize I was hitting a DHCP bug when RR upgraded their DHCP servers. I upgraded and now I am back in service:) )

Here's a tip: never ever ever ever point your default route to ethernetX, always use the next hop IP address when going across a multi-access medium. If you do not, you will arp for everything not in your arp table and this takes time and resources.
 
You'd be better off grabbing an old x86 box (400MHz) and slapping on an operating system such as freebsd /openbsd/linux and route packets faster than this cupholder =)
 
You must log in or register to reply here.
Back
Top