[c-nsp] ME-C3750 code on plain WS-C3750?

Rubens Kuhl Jr. rubensk at gmail.com
Sun Jan 7 09:12:18 EST 2007


Cisco pricing can be very, very flexible sometimes. :-)
What is the 6500 config you thinked of, Cat6503+Sup32+ what line card ?


Rubens


On 1/7/07, Peter Salanki <peter.salanki at bahnhof.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The ME6524 is a lot more expensive than the matching 6500-chassis
> configuration. So unless your rackspace is very expensive, you could
> probably get away with a 6503 at a lower cost.
>
> 7 jan 2007 kl. 14.02 skrev Rubens Kuhl Jr.:
>
> >>> And the Network Processor is attached only to the 2 "Enhanced
> >>> Services" ports, so unless you have only two uplinks and use only L3
> >>> on them (as MPLS requires "routerport" ), this will end up using
> >>> all 4
> >>> gigabit ports, connecting the 2 non-enhanced ports to the 2 enhanced
> >>> ports.
> >>>
> >>
> >>     So we get MPLS on a couple of uplinks but not across the board?
> >
> > Sadly, yes.
> >
> >>> 3750 Metro software has also plenty of annoying bugs (like
> >>> traceroute
> >>> not working) and limitations (not capable of balancing etherchannel
> >>> based on MPLS label is one of them).
> >>>
> >>
> >>     Traceroute results are hidden in some MPLS scenarios, no? Or
> >> is this
> >> a case where it should work and doesn't?
> >
> > The second. You can get the bug id on the release notes.
> >
> >>> Cisco has a metro with up to 32 gigabit ports called ME6524, now in
> >>> FCS phase. As the name suggests, it's based on 6500 with native
> >>> supervisor support for MPLS, so I hope it will be more stable than
> >>> 3750 Metro. Beware that it doesn't support VPLS, though.
> >>>
> >>
> >>     Instability in the 3750 ... does this extend to the other ME type
> >> switches?
> >
> > I hope not, and in my experience, what's inside counts more than the
> > marketing name.
> > So it's more likely that ME6524 have more strong and weak points in
> > common with Cat6500 and 7600, than with its 37xx counterpart.
> >
> > It's based on PFC3C, which seems to be a PFC3BXL feature set with
> > PFC3B TCAM sizes.
> > Software is ME6500-only today (12.2 ZU), but it will be merged with
> > mainline in the future (which leaves a question to what mainline it
> > will be synced, 6500 or 7600).
> >
> >
> >
> > Rubens
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> Med vänliga hälsningar
>
> Peter Salanki
> Nätansvarig
> Bahnhof AB (AS8473)
> www.bahnhof.se
> Kontor: +46855577132
> Mobil: +46709174932
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (Darwin)
>
> iD8DBQFFoPG0iQKhdiFGiogRAqgrAJ48ILSH97OFf6c2SKshXgEteSX/fACeL7y9
> l9uxk/qPfKcFEgHWfmCDSck=
> =myyb
> -----END PGP SIGNATURE-----
>



More information about the cisco-nsp mailing list