Tuesday, September 27, 2011

Configuring MPLS EoMPLS VLAN Mode - L2VPN

In this blogtorial we will configure EoMPLS VLAN mode so we can preserve the VLAN tagging from one site to another. Consider the simple topology and let's get started. 


Relevant Configurations are posted below.


I posted in my previous blogtorial 'Configuring MPLS L2VPN InterAS VPWS - EoMPLS Port Mode' on how to configure L2 VFI / Pseudowire class / etc, however we will do it again here.

So first let's get R1 and R2 configured.

R1 and R2
R1 and R2
Now let's get the PE (R3 and R4) configured.

R3 and R4
R3 and R4


Now let's get CE (R5 and R6) configured. Note that ISL encapsulation is not supported in EoMPLS VLAN Mode.

R5 and R6. 


Let's verify. Here is a wireshark capture of R5 Fast 1/1 which connects to R3. Notice the VLAN tagging on the ICMP Reply from R6.



As you can see VLAN tags are preserved between R5 <-->R6


Many more articles to come so stay tuned. "Join this Site" on the right ------->

Please post if you have any comments or suggestions.

ITHITMAN
Posted by
Labels: , , , ,

11 comments:

  1. AnonymousNovember 13, 2011 at 9:55 AM

    Hi there,
    were you able to configure this stuff on GNS3?
    As far as I know you need specific hardware that is not possibile to emulate using GNS3.

    Cheers.
    Marco
    hazzarola|a.t|hotmail|d.o.t|com

    ReplyDelete
  2. AnonymousNovember 13, 2011 at 10:03 AM

    ops... I didn't noticed that you vere using VPWS and not VPLS that is supported only on 7600

    ReplyDelete
  3. Arwin ReprakashNovember 13, 2011 at 11:06 PM

    :) I wish I could do vpls on gns as well as multipoint vpws.

    ReplyDelete
  4. AnonymousSeptember 4, 2012 at 8:06 AM

    *Sep 4 16:54:53.018: %SW_MGR-3-CM_ERROR: Connection Manager Error - provision segment failed [SSS:AToM:1810901] - no circuit found., -Traceback= 0x6121EDD0 0x62C91088 0x62C9115C 0x621075D0 0x62C8ECFC 0x63015428 0x63015500 0x62C8F66C 0x62C8F7E8 0x62C81CE4 0x63015428 0x63015500 0x62C82890 0x62C7DB20 0x62C81314 0x62C81760
    *Sep 4 16:54:53.054: %SW_MGR-3-CM_ERROR_CLASS: Connection Manager Error: Class SSS: - unable to unbind segment 2., -Traceback= 0x6121EDD0 0x62C81FB4 0x62C821A0 0x63015428 0x63015500 0x62C82890 0x62C7DFD8 0x62C81354 0x62C81760

    What does it mean? Thanks

    ReplyDelete
    Replies
    1. Arwin ReprakashSeptember 4, 2012 at 8:20 AM

      I am not sure. Sounds like an issue with GNS3.I would start with a new topology.

      Delete
  5. AnonymousSeptember 4, 2012 at 8:45 AM

    I've built shown topology on c7200 and GNS3. Connection between R3->R1 and R4->R2 OK. But between R1->R2 down. :(

    ReplyDelete
  6. AnonymousSeptember 4, 2012 at 8:46 AM

    sorry GNS 0.8.3

    ReplyDelete
  7. AnonymousSeptember 5, 2012 at 1:24 PM

    Something wrong! I tried to create official Cisco scenario from http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fsstitch.html.
    Result is the same:
    "*Sep 5 22:20:58.703: %SW_MGR-3-CM_ERROR: Connection Manager Error - provision segment failed [SSS:AToM:4102] - no switch available., -Traceback= 0x6121EDD0 0x62C91088 0x62C9115C 0x621075D0 0x62C8ECFC 0x63015428 0x63015500 0x62C8F66C 0x62C8F7E8 0x62C81CE4 0x63015428 0x63015500 0x62C82890 0x62C7DB20 0x62C81314 0x62C81760
    *Sep 5 22:21:59.707: %SW_MGR-3-CM_ERROR: Connection Manager Error - provision segment failed [SSS:AToM:4104] - no switch available., -Traceback= 0x6121EDD0 0x62C91088 0x62C9115C 0x621075D0 0x62C8ECFC 0x63015428 0x63015500 0x62C8F66C 0x62C8F7E8 0x62C81CE4 0x63015428 0x63015500 0x62C82890 0x62C7DB20 0x62C81314 0x62C81760
    "

    ReplyDelete
  8. AnonymousSeptember 5, 2012 at 1:28 PM

    Could you, please, tell me, what version of IOS did you use in your example?

    Thanks!

    ReplyDelete
  9. UnknownMarch 10, 2014 at 5:52 AM

    Can u send this topology file to me.(xxx2092@gmail.com)

    ReplyDelete

Subscribe to: Post Comments (Atom)