EoMPLS and EVC

When a pseudowire is configured on a VLAN interface, the pseudowire becomes a virtual Layer 2 port in that VLAN or bridge domain. You can configure other types of L2 ports, such as EFP ports and switch ports in the same bridge domain. Switch functions, such as MAC address learning, flooding, and forwarding to learned MAC addresses apply to all the Layer 2 ports, including the pseudowire.

There are two methods to configuration the EoMPLS pseudowire  with EVC.
  
Method1:  Cross-Connect on an EFP interface. 
The configuration is below
!configuration On SwitchA

SwitchA(config)# interface GigabitEthernet0/3
SwitchA(config-if) switchport trunk allowed vlan none
SwitchA(config-if) switchport mode trunk
SwitchA(config-if) service instance 1 ethernet
SwitchA(config-if) encapsulation dot1q 12
SwitchA(config-if) xconnect 12.12.12.12 123 encapsulation mpls


!configuration On SwitchB

SwitchB(config)# interface GigabitEthernet0/3
SwitchB(config-if) switchport trunk allowed vlan none
SwitchB(config-if) switchport mode trunk
SwitchB(config-if) service instance 1 ethernet
SwitchB(config-if) encapsulation dot1q 12
SwitchB(config-if) xconnect 12.12.12.11 123 encapsulation mpls

Method1 configuring Cross-Connect on an EFP Interface directly. This method is not flexible.  It can’t use bridge domain to bridge multiple service instances

Method2.  Configuring the cross-connect on vlan interface.
The configuration is below:
!configuration On SwitchA

SwitchA(config)# interface GigabitEthernet0/1
SwitchA(config-if) switchport access vlan 100

SwitchA(config)# interface GigabitEthernet0/2
Switch(config-if) switchport mode trunk

SwitchA(config)# interface GigabitEthernet0/3
SwitchA(config-if) switchport trunk allowed vlan none
SwitchA(config-if) switchport mode trunk
SwitchA(config-if) service instance 1 ethernet
SwitchA(config-if) encapsulation dot1q 100
SwitchA(config-if) rewrite ingress tag pop 1 symmetric
SwitchA(config-if) bridge-domain 100
!SwitchA(config)# interface GigabitEthernet0/4 
SwitchA(config-if) service instance 2 ethernet
SwitchA(config-if) encapsulation dot1q 100
SwitchA(config-if) rewrite ingress tag pop 1 symmetric
SwitchA(config-if) bridge-domain 100

SwitchA(config)# interface Vlan100
SwitchA(config-if) no ip address
SwitchA(config-if) xconnect 12.12.12.12 123 encapsulation mpls


!configuration On SwitchB

SwitchB(config)# interface GigabitEthernet0/10
SwitchB(config-if) switchport access vlan 100

SwitchB(config)# interface GigabitEthernet0/13
SwitchB(config-if) switchport trunk allowed vlan none
SwitchB(config-if) switchport mode trunk
SwitchB(config-if) service instance 1 ethernet
SwitchB(config-if) encapsulation dot1q 100
SwitchB(config-if) rewrite ingress tag pop 1 symmetric
SwitchB(config-if) bridge-domain 100
!
SwitchB(config)# interface GigabitEthernet0/14 
SwitchB(config-if) service instance 2 ethernet
SwitchB(config-if) encapsulation dot1q 100
SwitchB(config-if) rewrite ingress tag pop 1 symmetric
SwitchB(config-if) bridge-domain 100

SwitchB(config)# interface Vlan100
SwitchB(config-if) no ip address
SwitchB(config-if) xconnect 12.12.12.11 123 encapsulation mpls

Method2 is very flexible.   it use the bridge-domain bundle multiple ports together then using the vlan interface to do the xconnect for traffic coming from multiple ports

For Network Design, Build and Consulting Services, 

please visit:

www.unistreamnetworks.com