Search This Blog

Monday, February 13, 2012

Juniper/Cisco MPLS Layer-2 VPN configuration


Here is the following scenario:


The following post will explain how to configure an MPLS Layer-2 VPN, using single interface, to multiple far end interfaces, where both Juniper and Cisco routers are been used.

This is taken from a production network which I configured lately to one of our customers.

Topology setup:
       -          An MPLS network based on LDP/MPLS, IGP, BGP, MP-BGP
       -          AGG1 - An aggregation switch which terminate customer’s layer 2 connections
       -          3x PE routers (PE1 and PE2 are Juniper J6350 and PE3 is Cisco 7206VXR)
       -          Customer’s switches and CPE’s

Note that the interfaces, which connected from the switches, to the MPLS Layer-2 VPN ingress interface, should be in trunk mode.

The following configuration is referring to PE routers:

PE1 Configuration (Juniper router)
      1.       Make sure router’s loopback is configured under mpls and ldp protocols else configure it:
root@PE1# set protocols mpls interface lo0.0
root@PE1# set protocols ldp interface lo0.0

      2.       Configure the physical ingress router interface for 802.1q tagging for a cross-connect:
root@PE1# set interfaces ge-0/0/2 vlan-tagging
root@PE1# set interfaces ge-0/0/2 encapsulation vlan-ccc

      3.       Configure the appropriate interfaces as units under the physical interface:
root@PE1# set interfaces ge-0/0/2 unit 2900 encapsulation vlan-ccc vlan-id 2900
root@PE1# set interfaces ge-0/0/2 unit 2077 encapsulation vlan-ccc vlan-id 2077

      4.       Now configure the Layer-2 circuit under protocols:
[edit protocols]
root@PE1# set l2circuit neighbor 155.1.1.2 interface ge-0/0/2.2900 virtual-circuit-id 2900
root@PE1# set l2circuit neighbor 155.1.1.2 interface ge-0/0/2.2900 no-control-word
root@PE1# set l2circuit neighbor 155.1.1.2 interface ge-0/0/2.2900 encapsulation-type ethernet-vlan
root@PE1# set l2circuit neighbor 155.1.1.2 interface ge-0/0/2.2900 mtu 1500 
root@PE1# set l2circuit neighbor 155.1.1.3 interface ge-0/0/2.2077 virtual-circuit-id 2900
root@PE1# set l2circuit neighbor 155.1.1.3 interface ge-0/0/2.2077 no-control-word
root@PE1# set l2circuit neighbor 155.1.1.3 interface ge-0/0/2.2077 encapsulation-type ethernet-vlan
root@PE1# set l2circuit neighbor 155.1.1.3 interface ge-0/0/2.2077 mtu 1500
The configurations are per neighbor and for each VLAN configure a separate interface and interface settings.
     
      5.       Apply commit
root@PE1# commit

PE2 Configuration (Juniper router)
Pretty much the same as PE1

      1.       Make sure router’s loopback is configured under mpls and ldp protocols else configure it:
root@PE2# set protocols mpls interface lo0.0
root@PE2# set protocols ldp interface lo0.0

      2.       Configure the physical ingress router interface for 802.1q tagging for a cross-connect:
root@PE2# set interfaces ge-3/0/0 vlan-tagging
root@PE2# set interfaces ge-3/0/0 encapsulation vlan-ccc

      3.       Configure the appropriate interfaces as units under the physical interface:
root@PE2# set interfaces ge-3/0/0 unit 2900 encapsulation vlan-ccc vlan-id 2900

      4.       Now configure the Layer-2 circuit under protocols:
[edit protocols]
root@PE2# set l2circuit neighbor 155.1.1.1 interface ge-3/0/0.2900 virtual-circuit-id 2900
root@PE2# set l2circuit neighbor 155.1.1.1 interface ge-3/0/0.2900 no-control-word
root@PE2# set l2circuit neighbor 155.1.1.1 interface ge-3/0/0.2900 encapsulation-type ethernet-vlan
root@PE2# set l2circuit neighbor 155.1.1.1 interface ge-3/0/0.2900 mtu 1500 

      5.       Apply commit
root@PE1# commit

PE3 Configuration (Cisco router)
     
      1.       Configure the physical interface:  
interface GigaEthernet2/0
 no ip address
 load-interval 30
 duplex full
end

      2.       Configure the logical interface:
interface GigaEthernet2/0.2077
 encapsulation dot1Q 2077
 xconnect 155.1.1.1 2077 encapsulation mpls
end

      3.       Save the configuration:
Router(config)# wr

Verification

Check Layer-2 link status:
Juniper:
root@PE1> show l2circuit connections extensive
Layer-2 Circuit Connections:

Legend for connection status (St)  
EI -- encapsulation invalid      NP -- interface h/w not present  
MM -- mtu mismatch               Dn -- down                      
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down   
CM -- control-word mismatch      Up -- operational               
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          IB -- TDM incompatible bitrate
NC -- intf encaps not CCC/TCC    TM -- TDM misconfiguration
BK -- Backup Connection          ST -- Standby Connection
CB -- rcvd cell-bundle size bad  SP -- Static Pseudowire
LD -- local site signaled down   RS -- remote site standby
RD -- remote site signaled down  XX -- unknown

Legend for interface status 
Up -- operational           
Dn -- down                  
Neighbor: 155.1.1.2
    Interface                 Type  St     Time last up          # Up trans
    ge-0/0/2.2900(vc 2900)    rmt   Up     Feb 12 03:35:59 2012           1
      Remote PE: 155.1.1.2, Negotiated control-word: No
      Incoming label: 324768, Outgoing label: 319760
      Negotiated PW status TLV: No
      Local interface: ge-0/0/2.2900, Status: Up, Encapsulation: VLAN
    Connection History:
        Feb 12 03:35:59 2012  status update timer 
        Feb 12 03:35:58 2012  PE route changed    
        Feb 12 03:35:58 2012  Out lbl Update                    319760
        Feb 12 03:35:58 2012  In lbl Update                     324768
        Feb 12 03:35:58 2012  loc intf up                ge-0/0/2.2900
Neighbor: 155.1.1.3
    Interface                 Type  St     Time last up          # Up trans
    ge-0/0/2.2077(vc 2077)    rmt   Up     Feb 13 00:34:09 2012           1
      Remote PE: 155.1.1.3, Negotiated control-word: No
      Incoming label: 324752, Outgoing label: 42
      Negotiated PW status TLV: No
      Local interface: ge-0/0/2.2077, Status: Up, Encapsulation: VLAN
    Connection History:
        Feb 13 00:34:09 2012  status update timer 
        Feb 13 00:34:09 2012  PE route changed    
        Feb 13 00:34:09 2012  Out lbl Update                        42
        Feb 13 00:34:09 2012  In lbl Update                     324752
        Feb 13 00:34:09 2012  loc intf up                ge-0/0/2.2077

Cisco:
router#show xconnect all detail
Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State
UP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No Hardware
XC ST  Segment 1                         S1 Segment 2                         S2
------+---------------------------------+--+---------------------------------+--
UP     ac   Gi2/0.2077 2077(Eth VLAN)    UP mpls 155.1.1.1:2077            UP
            Interworking: none                   Local VC label 42             
                                                 Remote VC label 324752        
                                                 pw-class:    
                



16 comments:

  1. The post is written in very a good manner and it contains many useful information for me. expressvpn free trial

    ReplyDelete
  2. I have recently started a blog, the info you provide on this site has helped me greatly. Thanks for all of your time & work. top android vpn

    ReplyDelete
  3. I have been reading for the past two days about your blogs and topics, still on fetching! Wondering about your words on each line was massively effective. Techno-based information has been fetched in each of your topics. Sure it will enhance and fill the queries of the public needs. Feeling so glad about your article. Thanks…!
    selenium training in chennai
    selenium online courses best selenium online training
    selenium testing training
    selenium classes

    ReplyDelete
  4. Thanks for sharing this valuable information to our vision. You have posted a worthy blog keep sharing.
    Digital Marketing Course In Kolkata
    Web Design Course In Kolkata
    SEO Course In Kolkata

    ReplyDelete
  5. The development of artificial intelligence (AI) has propelled more programming architects, information scientists, and different experts to investigate the plausibility of a vocation in machine learning. Notwithstanding, a few newcomers will in general spotlight a lot on hypothesis and insufficient on commonsense application. machine learning projects for final year In case you will succeed, you have to begin building machine learning projects in the near future.

    Projects assist you with improving your applied ML skills rapidly while allowing you to investigate an intriguing point. Furthermore, you can include projects into your portfolio, making it simpler to get a vocation, discover cool profession openings, and Final Year Project Centers in Chennai even arrange a more significant compensation.


    Data analytics is the study of dissecting crude data so as to make decisions about that data. Data analytics advances and procedures are generally utilized in business ventures to empower associations to settle on progressively Python Training in Chennai educated business choices. In the present worldwide commercial center, it isn't sufficient to assemble data and do the math; you should realize how to apply that data to genuine situations such that will affect conduct. In the program you will initially gain proficiency with the specialized skills, including R and Python dialects most usually utilized in data analytics programming and usage; Python Training in Chennai at that point center around the commonsense application, in view of genuine business issues in a scope of industry segments, for example, wellbeing, promoting and account.

    ReplyDelete
  6. Someone who has completed and passed CCNA training will have the knowledge to set up all manner of home and business networks. CCNA Classes in Pune

    ReplyDelete