[c-nsp] mpls hw limits on 7206

[David Freedman]

Yes, if you are implementing ethernet L2VPNs and wish to allow your 
customers to have the ability to carry standard "ip mtu" (1500B) inside 
their ethernet frames, then steer clear of the following interface types 
for the uplink to the core / other MPLS routers:

- PA-FE-TX
- PA-2FE-TX
- PA-FE-FX
- IO/FE
- IO/2-FE

The reason for this was recently highlighted here:

https://puck.nether.net/pipermail/cisco-nsp/2006-June/031765.html

since these interface types can only carry up to 1530 bytes 
"on-the-wire" (i.e as an ethernet PDU) they are incapable of also 
carrying the customer's ethernet payload and AToM control word as well

If you are only doing L3VPN / RFGC2457bis with these interfaces as 
uplink, providing you are not carrying anything extra from the customer 
(such as a stack of the customer's own MPLS labels when using CsC) then 
you should be fine

Alternatives to these interfaces are :

- PA-GE (allthough throughput is not wonderful for price)
- NPE-G1/NPE-G2 10/100/1000 ports
- Anything else that isn't ethernet based (i.e serial / ATM)

Kind Regards,

David Freedman



Michael Long wrote:
> Are there any hardware limitations on the 7206's that I need to be aware 
> of when implementing MPLS. It just looks like it's going to be l2 or l3 
> vpns, no TE, but I'd hate to get halfway through and find out I'm going 
> to need to upgrade some piece of hardware to make this work. It looks 
> like the hardware is 6 cisco 7206VXR (NPE400) with 512megs of ram. Any 
> ideas?
> 
> Thanks,
> 
> Mike
> _______________________________________________
> 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/
>