Routing

Expand all | Collapse all

Help with debug l2circuit stiching to VPLS instance

Jump to Best Answer
  • 1.  Help with debug l2circuit stiching to VPLS instance

    Posted 10-01-2019 06:38

    Hello everyone.

    I`m trying to set up l2circuit stiching to VPLS between ex4600 and MX104 routers.

    image.png

     

    l2circuit on EX4600:

    neighbor 1.1.1.1 {
        interface ge-0/0/12.4050 {
            virtual-circuit-id 254124050;
            description "PW: OptoMgt 4050 HQ";
            switchover-delay 180000;
            backup-neighbor 2.2.2.2;
        }
    }
    

    interface:

    flexible-vlan-tagging;
    mtu 9000;
    encapsulation flexible-ethernet-services;
    unit 4050 {
        encapsulation vlan-ccc;
        vlan-id 4050;
    }

    On MX104 side:

    neighbor 172.18.1.254 {
        interface lt-0/1/0.5 {
            virtual-circuit-id 254124050;
        }
    }
    

    interfaces:

    show interfaces lt-0/1/0.5
    encapsulation vlan-ccc;
    vlan-id 4050;
    peer-unit 6;
    family ccc;
    
    show interfaces lt-0/1/0.6
    encapsulation vlan-bridge;
    vlan-id 4050;
    peer-unit 5;
    

     

    lt-0/1/0.6 is bound to vpls instance to bridge domain.

    The l2circuit is up and running

        lt-0/1/0.5(vc 254124050)  rmt   Up     Oct  1 15:49:15 2019           3
          Remote PE: 1.1.1.1, Negotiated control-word: No
          Incoming label: 313120, Outgoing label: 59
          Negotiated PW status TLV: Yes
          local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
          Local interface: lt-0/1/0.5, Status: Up, Encapsulation: VLAN
          Flow Label Transmit: No, Flow Label Receive: No
    

    But i cannot see any mac addresses learned from lt-interface in bridge domain, and in monitor interface i can only see Input packets and no outgoing packets:

    Interface: lt-0/1/0.5, Enabled, Link is Up
    Flags: SNMP-Traps 0x4000
    Encapsulation: VLAN-CCC
    VLAN-Tag [ 0x8100.4050 ]
    Local statistics:                                                Current delta
      Input bytes:                         0                                   [0]
      Output bytes:                        0                                   [0]
      Input packets:                       0                                   [0]
      Output packets:                      0                                   [0]
    Remote statistics:
      Input bytes:                   3288023 (2808 bps)                     [2112]
      Output bytes:                        0 (0 bps)                           [0]
      Input packets:                   51404 (5 pps)                          [33]
      Output packets:                      0 (0 pps)                           [0]
    Traffic statistics:
      Input bytes:                   3288023                                [2112]
      Output bytes:                        0                                   [0]
      Input packets:                   51404                                  [33]
      Output packets:                      0                                   [0]
    

    The problem is that i have two l2circuit connections configured same way  bound to VPLS and they are working perfect. The problem is with only one stiched l2circuit.

     

     

     

     

     

     

     

     

     

     

     

     

     



  • 2.  RE: Help with debug l2circuit stiching to VPLS instance

     
    Posted 10-01-2019 07:56

    Hello,

    Seems like you have incorrect encapsulation for the vpls interface ie lt-0/1/0.6. Can you change the encapsulation to vlan-vpls?

    Can you please provide your VPLS instance configuration and output of show vpls connection?

     

    Thanks,

    Mayank Shah

     

    *** Please mark the response as accepted if it helps resovle the issue so others can benefit from the post.



  • 3.  RE: Help with debug l2circuit stiching to VPLS instance

    Posted 10-01-2019 11:16

    Hello Mayank

    Here is instance config:

    instance-type virtual-switch;
    route-distinguisher 1.1.1.1:2001;
    vrf-target target:100:2000;
    protocols {
        vpls {
            no-tunnel-services;
            site B1 {
                site-identifier 3;
            }
        }
    }
    bridge-domains {
        BD-4050 {
            domain-type bridge;
            vlan-id 4050;
            interface ae1.4050;
            interface ae0.4050;
            interface lt-0/1/0.4;
            interface lt-0/1/0.6;
        }
    }

     

    Edge protection: Not-Primary
      Local site: B1 (3)
        connection-site           Type  St     Time last up          # Up trans
        2                         rmt   Up     Oct  1 21:20:16 2019           1
          Remote PE: 2.2.2.2, Negotiated control-word: No
          Incoming label: 262146, Outgoing label: 29
          Local interface: lsi.1053184, Status: Up, Encapsulation: VPLS
          local site 3 remote site 2
    

     



  • 4.  RE: Help with debug l2circuit stiching to VPLS instance

     
    Posted 10-02-2019 06:47

    Hello,

    Your concern is that traffic is not going out of lt-0/1/0.5 towards the vpls tunnel, right?

    Can you make sure you are receiving the traffic on you l2-circuit from the EX?

    In addition, there is discrepancy in the output you have provided in original post - 

    For MX104 you provided the l2-circuit configuration as below - 

    neighbor 172.18.1.254 {
        interface lt-0/1/0.5 {
            virtual-circuit-id 254124050;
        }
    }

     

    However, the output of l2circuit connection does not point to the same neighbor - it says neighbor is 1.1.1.1

        lt-0/1/0.5(vc 254124050)  rmt   Up     Oct  1 15:49:15 2019           3
          Remote PE: 1.1.1.1, Negotiated control-word: No <<<<<<<<<<<<<<<<<<<<<<
          Incoming label: 313120, Outgoing label: 59
          Negotiated PW status TLV: Yes
          local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
          Local interface: lt-0/1/0.5, Status: Up, Encapsulation: VLAN
          Flow Label Transmit: No, Flow Label Receive: No

     Can you please help clarify these outputs ?

     

    Thanks 

    Mayank Shah



  • 5.  RE: Help with debug l2circuit stiching to VPLS instance

    Posted 10-02-2019 07:51

    I`m sorry. 

    Correct l2circuit config:

    neighbor 3.3.3.3 {
        interface lt-0/1/0.5 {
            virtual-circuit-id 254124050;
        }
    }

    This output is from MX104:

     lt-0/1/0.5(vc 254124050) rmt Up Oct 2 14:08:56 2019 1
    Remote PE: 3.3.3.3, Negotiated control-word: No
    Incoming label: 313216, Outgoing label: 67
    Negotiated PW status TLV: Yes
    local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
    Local interface: lt-0/1/0.5, Status: Up, Encapsulation: VLAN
    Description: PW->VPLS: OptoMgt 4050 HQ
    Flow Label Transmit: No, Flow Label Receive: No

    And this one is from EX:

        ge-0/0/12.4050(vc 254124050) rmt Up    Oct  2 14:09:04 2019           1
          Remote PE: 1.1.1.1, Negotiated control-word: No
          Incoming label: 67, Outgoing label: 313216
          Negotiated PW status TLV: Yes
          local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
          Local interface: ge-0/0/12.4050, Status: Up, Encapsulation: VLAN
             Flow Label Transmit: No, Flow Label Receive: No 


  • 6.  RE: Help with debug l2circuit stiching to VPLS instance

     
    Posted 10-03-2019 06:34

    Hello,

    Thank you for the information. Did you get an opportunity to check if the traffic is coming over the PW to MX104? Can you please capture the below - 

    show route 3.3.3.3

    show interface <the next-hop interface from above> | match rate

     

    Verify if there is incoming traffic on this interface. It should be same or greater than the incoming traffic of ge-0/0/12.4050 of EX.

    show interface ge-0/0/12.4050 extensive | match "pps" 

    Capture the above from EX switch

    Kindly let me know.



  • 7.  RE: Help with debug l2circuit stiching to VPLS instance

    Posted 10-03-2019 07:07

    Hello.

    Interface stats on EX show 0:

    Interface: ge-0/0/12.4050, Enabled, Link is Up
    Flags: SNMP-Traps 0x4000
    Encapsulation: VLAN-CCC
    VLAN-Tag [ 0x8100.4050 ]
    Local statistics:                                                Current delta
      Input bytes:                         0                                   [0]
      Output bytes:                        0                                   [0]
      Input packets:                       0                                   [0]
      Output packets:                      0                                   [0]
    Remote statistics:
      Input bytes:                         0 (0 bps)                           [0]
      Output bytes:                        0 (0 bps)                           [0]
      Input packets:                       0 (0 pps)                           [0]
      Output packets:                      0 (0 pps)                           [0]
    Traffic statistics:
      Input bytes:                         0                                   [0]
      Output bytes:                        0                                   [0]
      Input packets:                       0                                   [0]
      Output packets:                      0                                   [0]
    

    There is traffic from the side of MX.

    I`ve got l2circuit from EX to MX from port ge-0/0/10 and it is working as expected.



  • 8.  RE: Help with debug l2circuit stiching to VPLS instance

     
    Posted 10-03-2019 14:30

    Hello,

    Thank you for the information. From the outputs, you are not sending any traffic from EX to MX for the affected l2-circuit.

    Thus your original concern why traffic is not going out of lt-0/1/0.5 towards the vpls tunnel is no longer valid then. Since you do not have any traffic from the EX to MX on this l2circuit.

    Is your current problem on why you do not see the traffic going out of EX ge-0/0/12.4050? That is the traffic you are sending from MX towards EX.

    Can you please provide the below output from MX104 - 

    show route 3.3.3.3

    show interface <the next-hop interface from above> | match rate

    Above will help understand if the traffic is leaving the MX104 towards the EX or not.

     

    Thanks,

    Mayank Shah

     



  • 9.  RE: Help with debug l2circuit stiching to VPLS instance

    Posted 10-04-2019 04:18

    Hello.

    There is traffic coming to EX from MX.

    Interface: xe-2/0/3.2, Enabled, Link is Up
    Flags: SNMP-Traps 0x4000
    Encapsulation: ENET2
    VLAN-Tag [ 0x8100.2 ]
    Local statistics:                                                Current delta
      Input bytes:                 145944816                                 [562]
      Output bytes:                184435625                                 [520]
      Input packets:                 2132714                                   [8]
      Output packets:                2136458                                   [6]
    Remote statistics:
      Input bytes:                2084665245 (11040 bps)                   [21987]
      Output bytes:               7082619740 (13272 bps)                   [25929]
      Input packets:                25202632 (13 pps)                        [219]
      Output packets:               34104234 (19 pps)                        [307]
    Traffic statistics:
      Input bytes:                2230610061                               [22549]
      Output bytes:               7267055365                               [26449]
      Input packets:                27335346                                 [227]
      Output packets:               36240692                                 [313]
    Protocol: inet, MTU: 8978, Flags: None
    

    I`ve got l2circiuit EX->MX on the end of which i terminate subscribers and it is working.



  • 10.  RE: Help with debug l2circuit stiching to VPLS instance
    Best Answer

    Posted 10-07-2019 04:33

    Well, i`ve rebooted EX and everything is working now.