From: Tom Rogers (cccie71@yahoo.com)
Date: Thu Jul 08 2004 - 00:54:55 GMT-3
Thank you guys for the response. I am at point where I need to make a decision between 7204 VXRs and 3550 EMIs. I am going to be given Fa 100mb handout by the provider.
Basically I ll need to 2 Fa connections, one to the provider and the other to my lan at each site.
I am going to have 20 such remote locations all layer 2 handouts
(in one broadcast domain), with the hub as 2 gig handout.
I have several 7200s and 3550s as spare.
What should I use? Which will have the better throughput?
thanks
Brian Dennis <bdennis@internetworkexpert.com> wrote:
The newest version of the 3550 IOS supports Frame Relay. See below:
Rack1SW1#sho ver
Cisco Internetwork Operating System Software
IOS (tm) C3550 Software (C3550-I5K2L2Q3-M), Version 12.1(21)EA2, RELEASE
SOFTWARE (fc2)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Fri 24-Jun-04 00:51 by yenanh
Image text-base: 0x00003000, data-base: 0x0093F1B4
ROM: Bootstrap program is C3550 boot loader
Rack1SW1 uptime is 9 hours, 13 minutes
System returned to ROM by power-on
System image file is
"flash:/c3550-i5k2l2q3-mz.121-21.EA2/c3550-i5k2l2q3-mz.121-21.EA2.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
Rack1SW1#
Rack1SW1#sho run interface fa0/1
Building configuration...
Current configuration : 166 bytes
!
interface FastEthernet0/1
no switchport
switchport mode wan
ip address 129.1.124.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 129.1.124.2 102 broadcast
no frame-relay inverse-arp
end
Rack1SW1#show frame pvc int fa0/1
PVC Statistics for interface FastEthernet0/1 (Frame Relay DTE)
Active Inactive Deleted Static
Local 1 0 0 0
Switched 0 0 0 0
Unused 2 2 0 0
DLCI = 102, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
FastEthernet0/1
input pkts 1 output pkts 0 in bytes 34
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
switched pkts 0
Detailed packet drop counters:
no out intf 0 out intf down 0 no out PVC 0
in PVC down 0 out PVC down 0 pkt too big 0
shaping Q full 0 pkt above DE 0 policing drop 0
pvc create time 07:29:50, last time pvc status changed 06:59:32
Rack1SW1#
;-)
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
James
Sent: Wednesday, July 07, 2004 6:49 PM
To: MMoniz
Cc: Ken Diliberto; ccielab@groupstudy.com
Subject: Re: Limitations of 3550emi
On Wed, Jul 07, 2004 at 09:27:20PM -0400, MMoniz wrote:
> Actually it will if you cross pins 1-2..3-6 to 1-2...4-5 !!!!! lol
oh sweet, can you put frame-relay DLCI entries in the TCAM too and make
it
hardware linerate frame-relay switch? :)
-J
>
> At least the light may come on for a moment!!
>
> Also I don't believe the 3550 supports ISIS.
>
>
> Cat-3550(config)#router ?
> bgp Border Gateway Protocol (BGP)
> egp Exterior Gateway Protocol (EGP)
> eigrp Enhanced Interior Gateway Routing Protocol (EIGRP)
> igrp Interior Gateway Routing Protocol (IGRP)
> isis ISO IS-IS
> iso-igrp IGRP for OSI networks
> mobile Mobile routes
> odr On Demand stub Routes
> ospf Open Shortest Path First (OSPF)
> rip Routing Information Protocol (RIP)
> static Static routes
>
> Cat-3550(config)#router isis
> Cat-3550(config)#
>
> At least on this code
>
> c3550-i5k2l2q3-mz.121-14.EA1.bin
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Ken Diliberto
> Sent: Wednesday, July 07, 2004 8:57 PM
> To: ccielab@groupstudy.com
> Subject: Re: Limitations of 3550emi
>
>
> You mean even though the T1 plug fits in the Ethernet connector it
won't
> work??? :-)
>
> The 3550 doesn't support certain policy routing features and traffic
> shaping/policing features as well.
>
> Cisco has documents for each IOS release on the 3550 that say what
isn't
> supported.
>
> Ken
>
> Kenneth Wygand wrote:
>
> >?
> >Not to mention the (sometimes not so) obvious fact that the 3550 EMI
can
> only handle ethernet interfaces... won't work for a T1 circuit... ;-)
> >
> >Ken
> >
> >________________________________
> >
> >From: nobody@groupstudy.com on behalf of James
> >Sent: Wed 7/7/2004 7:56 PM
> >To: Tom Rogers
> >Cc: ccielab@groupstudy.com
> >Subject: Re: Limitations of 3550emi
> >
> >
> >
> >On Wed, Jul 07, 2004 at 04:25:43PM -0700, Tom Rogers wrote:
> >
> >
> >>Hi group,
> >>Can some list me the limitations 3550emi in comparison to a router?
> >>
> >>
> >
> >3550 EMI has unupgradeable 64MB RAM. This is not enough to do full
BGP
> >routing with ISP's. It's good enough to participate in an IBGP + IGP
with
> >limited set of routes in a small end POP/ethernet colo environment
though.
> >
> >It also cannot do a few minor stuff that adds a little bit of
annoyance
> such
> >as lack of uRPF, even though it takes the command properly.
> >
> >The QoS/traffic rate limitation features are also restricted on 3550
if you
> >want to compare with a full blown router.
> >
> >Further, Cisco has tradition of being slow or not following up to its
pre
> >marketing claims on modular Layer3 switches. Don't expect exciting
new
> features.
> >
> >It is worth noting that 3750 had been advertised with IPv6 capability
since
> >the beginning and still no IPv6? heh.
> >
> >-J
> >
> >
> >
> >>Thanks
> >>Tom
>
>
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:49 GMT-3