Fwd: VLAN-based EoMPLS

I think between PE01 and PE02 you are using layer3 and since eom is layer2
you need to make your core has layer2 to allow vlan 100. Basically, you
would need trunk between PE01 and PE02. Also, you can use l2 port-channel.
Moreover, could you paste output of "sh mpls l2tr binding"?.

Thanks,

Karthik.

PE01#show mpls ldp discovery
Local LDP Identifier:

  1.1.1.1:0
  Discovery Sources:
  Interfaces:
      GigabitEthernet1/1/1 (ldp): xmit/recv
          LDP Id: 2.2.2.2:0
  Targeted Hellos:
      1.1.1.1 -> 2.2.2.2 (ldp): active/passive, xmit/recv
          LDP Id: 2.2.2.2:0
PE01#show mpls ldp ne
PE01#show mpls ldp neighbor
  Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0
      TCP connection: 2.2.2.2.23803 - 1.1.1.1.646
      State: Oper; Msgs sent/rcvd: 11/10; Downstream
      Up time: 00:03:21
      LDP discovery sources:
        GigabitEthernet1/1/1, Src IP addr: 10.0.0.2
        Targeted Hello 1.1.1.1 -> 2.2.2.2, active, passive
      Addresses bound to peer LDP Ident:
        2.2.2.2 10.0.0.2

PE02#sh mpls ldp discovery
Local LDP Identifier:

  2.2.2.2:0
  Discovery Sources:
  Interfaces:
      GigabitEthernet1/1/1 (ldp): xmit/recv
          LDP Id: 1.1.1.1:0
  Targeted Hellos:
      2.2.2.2 -> 1.1.1.1 (ldp): active/passive, xmit/recv
          LDP Id: 1.1.1.1:0
PE02#sh mpls ldp ne
PE02#sh mpls ldp neighbor
  Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 2.2.2.2:0
      TCP connection: 1.1.1.1.646 - 2.2.2.2.23803
      State: Oper; Msgs sent/rcvd: 12/13; Downstream
      Up time: 00:05:00
      LDP discovery sources:
        GigabitEthernet1/1/1, Src IP addr: 10.0.0.1
        Targeted Hello 2.2.2.2 -> 1.1.1.1, active, passive
      Addresses bound to peer LDP Ident:
        1.1.1.1 192.168.30.30 10.0.0.1

Blogs and organic groups at http://www.ccie.net
Received on Thu Oct 28 2010 - 21:55:34 ART