[c-nsp] Yet another "wont fix because its on the 7500"

Rodney Dunn rodunn at cisco.com
Tue Apr 18 09:47:58 EDT 2006


Joe,

It just so happens the TAC engineer that has this case sits beside
me. I'd been working with him on this to try and get a clear message
from the BU's. This is one of the main problems with the 75xx.

You can configure about every feature in IOS on it but they
are not all tested/supported due to it's distributed switching
architecture. This is one such feature combination.

We have passed the information to the PM's of the MPLS and
75xx BU and it's their decision to make if they will dedicate
the time/resources to rewrite and set up testbeds to verify this
feature combination. Given only one or two customers have ever
asked for this on the 75xx it will probably not get added.

It's more than just fixing the switching vector to handle the
rewrites in the MPLS path. For us to claim support we have to
add it in testbeds to it's constantly tested and that is a business
decision by the BU's. The TAC engineer was trying very hard to get
the right answer for you even though it wasn't the answer you (or
us either for that matter) we were hoping to get.

I'm still trying to see if we can get it to work in the code without
a lot of extra work but it's not looking too good.

We can take this offline.

Rodney


On Mon, Apr 17, 2006 at 05:03:43PM -0400, Joe Maimon wrote:
> CSCed78665 Title: ICMP Echo-reply from c7507s tagged int. have corrupted 
> PPPoE header
> 
> Took over six months for TAC to come back and say
> 
> Since 7500 isnt targetted as broadband aggregation, its perfectly 
> acceptable that packets from tagged interfaces cant output properly to 
> pppox interfaces.
> 
> This is crap.
> _______________________________________________
> 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/


More information about the cisco-nsp mailing list