TE for VPLS customers

[urs.shrestharana]

Hi all,

Is it possible to configure TE for individual customer, instead to forward all traffic (all customers traffic) in single tunnel. where all customers are in VPLS (l2VPN).

eg. A diagram is attached herewith for further reference : one TE tunnel for customer CE-a and same like for others customers.

Thank you.

Uttam

[judebryant]

Please not everyone.

When using pseudowires, customer mac address's are not learned by your core mpls network.

however, in vpls, customer mac addresses are learned.  So be careful when using vpls, unless you have implemented 802.1ah

Regards

Jude Bryant

Pioneer Telephone

[judebryant]

OK,

so I did some research.

example

Ethernet pseudowire type/mode tagged or 0x00004

(lan1)==(tagged traffic)==>{interface}PE/P[R1]{mpls cloud}[R2]PE/P{interface}==>(tagged traffic)==(lan2)

vlan 123 is not globally defined.

mac address from both lan1 and lan2 are not learned within the cloud

this is a point to point pseudowire.

router 1

lo0

ip address 10.10.10.1

interface 3/0/1

service instance 100 ethernet

encapsulation dot1q 123

rewrite ingress tag pop 1 symmetric

xconnection 10.10.10.2 100 encapsulation mpls

router 2

lo0

ip address 10.10.10.2

interface 3/0/1

service instance 100 ethernet

encapsulation dot1q 123

rewrite ingress tag pop 1 symmetric

xconnect 10.10.10.2 100 encapsulation mpls

the packets ingress from lan 1 is tagged with vlan123

because of this the service instance is making decisions based on matching this tagged traffic (encapsulation dot1q 123)

example

Ethernet pseudowire type/mode raw or 0x00005

(lan1)==(tagged or untagged traffic)==>{interface}PE/P[R1]{mpls cloud}[R2]PE/P{interface}==>(tagged or untagged traffic)==(lan2)

vlan 123 is not globally defined.

mac address from both lan1 and lan2 are not learned within the cloud

this is a point to point pseudowire.

the service instances do not try to match vlan tags so we use the word default for encapsulation type.  not decisions are made.  this is raw mode

traffic in traffic out

router 1

lo0

ip address 10.10.10.1

interface 3/0/1

service instance 100 ethernet

encapsulation default

rewrite ingress tag pop 1 symmetric

xconnection 10.10.10.2 100 encapsulation mpls

router 2

lo0

ip address 10.10.10.2

interface 3/0/1

service instance 100 ethernet

encapsulation default

rewrite ingress tag pop 1 symmetric

xconnect 10.10.10.2 100 encapsulation mpls

the packets ingress from lan 1 is tagged with vlan123 or untagged

now we can create a service instance that is not making decisions based on matching this tagged traffic (encapsulation default)

anything that comes in on this port tagged or untagged goes thru

this is similar to a layer2 tunnel, however this tunnel can be protected by a backup pseudowire..

Hoped I explained this in a clear matter.  If not please ask any questions you mave have.

Please refer to the document provided by

shivlu jain

Modes Of Ethernet Over MPLS (EoMPLS)

thanks Shivlu

and Regards

Jude Bryant

Pioneer Telephone

[Riccardo Romani]

Hi, i have vpls with two vfi used for two different ce. I have conf two tunnel but on igp routing  table ospf one tunnel is used  as next hop for Both remote pw loopbacks and this si something i don’t want . I want the  routing through first tunnel to’ first remote pseudowire loopback and the second tunnel to be used to re ah the second remote pseudowire loopback. How  can i do ? Pleas help.