[c-nsp] Using EoMPLS where you'd normally use a VLAN

[Arie Vayner (avayner)]

Jason,

You can do this with some of the devices. For example 7600 with ES+ (or
ES20/SIP) modules can terminate a pseudowire (either point to point or
VPLS...) on a SVI and also have layer 3 configuration on it. The same
applies to ASR9000...

This can be used for many interesting solutions such as HSRP across an
MPLS domain, Layer 3 services for a VPLS domain etc.

The extra hardware is required as this requires extra processing...

Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jason Lixfeld
Sent: Tuesday, April 27, 2010 01:50
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Using EoMPLS where you'd normally use a VLAN

I'm wondering if I can use EoMPLS in a situation where I'd normally use
a VLAN.

For example, in a VLAN centric network, I'd have a node connected to an
access port on switch 1.  Switch 1 would be connected directly to switch
2 over an appropriately configured 802.1q trunk port or access port.
I'd assign an IP to an SVI on switch 2 and as long as the SVI had the
same VLAN identifier as the access port on switch 1, I could pass
traffic between the SVI on switch 2 and the node connected to the access
port on switch 1.

Is there an equivalent to this in EoMPLS land where I could do the same
thing using two devices that were both acting as P+PE devices?  I know
that normally you can't assign an IP address on an interface that is
also configured with an xconnect, but I'm wondering if there's a feature
out there somewhere that could make this sort of thing possible.
_______________________________________________
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/