Brad - what about Cat6500 with SIP-600 on the networks facing ports (mpls) and WS-X6748 on the customer facing ports?Would that work for your scenario below - each customer has a unique vlan? SIP-600 is supported on Cat 6500 according to the docs.
I know that if want to use local significant VLANs customers then I would need to move to EVC concept on 7600 on 12.2(33)SRB (or even A?) Cat 6500 does not support EVC, correct? Thanks, Marlon On Wed, Jan 28, 2009 at 4:37 PM, Brad Hedlund <[email protected]> wrote: > On 1/28/09 1:41 PM, "Arie Vayner (avayner)" <[email protected]> wrote: > > > VPLS requires either SIP or ES20 cards both on customer and core facing > > sides. > > It depends. If Marlon is giving each customer their own unique VLAN (e.g. > Cust A gets VLAN 10, Cust B gets VLAN 20, and so on.) then the customer > facing ports can be plain 1Q trunks with no MPLS encapsulation required. > In > this scenario the customer facing ports could be WS-X6748, for example. > And > of course the ports with 'mpls ip' enabled forming the VPLS core must be > SIP > or ES20. The VPLS 'xconnect' statements would be applied to each > customer's > SVI. > > interface VLAN 10 > description Customer A > xconnect vfi VLAN10_CUST-A > interface VLAN 20 > description Customer B > xconnect vfi VLAN20_CUST-B > > 6500 can now support VPLS over GRE with SIP-400 and SXI code. But I > definitely agree that 7600 is better for native VPLS, and supporting > interface speeds up to 10GE. > > Cheers, > > Brad Hedlund > [email protected] > http://www.internetworkexpert.org > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
