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

[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