Routing

last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
Back to discussions
Expand all | Collapse all

l2circuit ccc connection not coming up - thoughts

  • 1.  l2circuit ccc connection not coming up - thoughts

    Posted 01-22-2015 13:26

    I'm working on a lab network and trying trying to bring up a l2circuit connection between two PEs.  I am unable to bring up the connection due to an OL error.  MPLS core is build using rsvp tunels using OSPF for IGP and BGP for signalling.  From everything I check everything is working as it should but I can't get the l2circuit connection up.  I've attached the PE configs.  

     

    root@vMX7> show mpls lsp
Ingress LSP: 2 sessions
To              From            State Rt P     ActivePath       LSPname
192.168.1.5     192.168.1.7     Up     0 *                      vMX7-to-vMX5
192.168.1.6     192.168.1.7     Up     0 *                      vMX7-to-vMX6
Total 2 displayed, Up 2, Down 0

Egress LSP: 2 sessions
To              From            State   Rt Style Labelin Labelout LSPname
192.168.1.7     192.168.1.6     Up       0  1 FF       3        - vMX6-to-vMX7
192.168.1.7     192.168.1.5     Up       0  1 FF       3        - vMX5-to-vMX7
Total 2 displayed, Up 2, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

root@vMX7> show l2circuit connections
Layer-2 Circuit Connections:

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 192.168.1.5
    Interface                 Type  St     Time last up          # Up trans
    ge-0/0/2.513(vc 1200001203) rmt OL
Neighbor: 192.168.1.6
No l2circuit connections found

root@vMX7>

     

    root@vMX5> show mpls lsp
Ingress LSP: 2 sessions
To              From            State Rt P     ActivePath       LSPname
192.168.1.6     192.168.1.5     Up     0 *                      vMX5-to-vMX6
192.168.1.7     192.168.1.5     Up     0 *                      vMX5-to-vMX7
Total 2 displayed, Up 2, Down 0

Egress LSP: 2 sessions
To              From            State   Rt Style Labelin Labelout LSPname
192.168.1.5     192.168.1.6     Up       0  1 FF       3        - vMX6-to-vMX5
192.168.1.5     192.168.1.7     Up       0  1 SE       3        - vMX7-to-vMX5
Total 2 displayed, Up 2, Down 0

Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0

root@vMX5> show l2circuit connections
Layer-2 Circuit Connections:

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 192.168.1.6
No l2circuit connections found
Neighbor: 192.168.1.7
    Interface                 Type  St     Time last up          # Up trans
    ge-0/0/2.513(vc 1200001203) rmt OL

root@vMX5>

     

     

    Any help would be appreciated. Just trying to understand how the circuits are signaled and brought up and I think I'm just missing something that will be obvious in hindsight.  I do have VPLS connections running fine on this network.

    Attachment(s)

    txt
    vMX5.txt   4 KB 1 version
    txt
    vMX7.txt   4 KB 1 version


  • 2.  RE: l2circuit ccc connection not coming up - thoughts

     
    Posted 01-22-2015 14:13

    If you are trying to use LDP for label distribution, I don't see where you have lo0.0 configured in the LDP configuration group you've defined. 



  • 3.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-22-2015 14:36

    The LDP configurations under group no longer apply as I've deleted ldp under protocols and with no match the configurations will not be added. LDP was my first attempt at setting up the network and no longer use ldp for label distribution.  



  • 4.  RE: l2circuit ccc connection not coming up - thoughts

     
    Posted 01-22-2015 18:46

    What's the output of 'show route 192.168.1.5' from the 192.168.1.7 router?  'OL' usually means that there is no label binding for the remote neighbor.

     

    We usually configure the 'encapsulation-type' for the l2circuit, along with the VC ID, as a default.  I don't believe that would cause your problem, though.



  • 5.  RE: l2circuit ccc connection not coming up - thoughts

     
    Posted 01-22-2015 22:07

    I see that your config is missing the loopback interfaces under the MPLS / RSVP protocols config.

     

     



  • 6.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-23-2015 13:00

    As sugested I've added lo0.0 under mpls and rsvp with no effect.



  • 7.  RE: l2circuit ccc connection not coming up - thoughts

     
    Posted 01-23-2015 13:34

    lo0.0 definition in the mpls and rsvp stanzas is not necessary.  It is only necessary for label binding for ldp.

     

    What is the status of 'show interfaces ge-0/0/2'?  What model device is this - an actual vMX?  Just for the heck of it, can you delete the ge-0/0/2.0 logical unit and change the config of the physical interface to 'vlan-tagging' and 'encapsulation vlan-ccc'?  I'm wondering if the flexible-vlan-encapsulation isn't working for some reason.



  • 8.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-23-2015 13:42

    Here's the requested output.  And yes these are vMX's.

     

    root@vMX7> show interfaces ge-0/0/2
Physical interface: ge-0/0/2, Enabled, Physical link is Up
  Interface index: 139, SNMP ifIndex: 515
  Link-level type: Flexible-Ethernet, MTU: 1522, MRU: 1530, Speed: 1000mbps,
  BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Source filtering: Disabled, Flow control: Enabled
  Pad to minimum frame size: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  CoS queues     : 8 supported, 8 maximum usable queues
  Current address: 00:05:86:71:98:02, Hardware address: 00:05:86:71:98:02
  Last flapped   : 2015-01-23 14:20:06 MST (00:20:00 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 232 bps (0 pps)
  Active alarms  : None
  Active defects : None
  Interface transmit statistics: Disabled

  Logical interface ge-0/0/2.0 (Index 333) (SNMP ifIndex 526)
    Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.512 ]
    Encapsulation: VLAN-VPLS
    Input packets : 11
    Output packets: 303
    Protocol vpls, MTU: 1522
      Flags: Is-Primary

  Logical interface ge-0/0/2.513 (Index 334) (SNMP ifIndex 525)
    Flags: Up SNMP-Traps 0x4000
    VLAN-Tag [ 0x8100.513 ] In(pop) Out(push 0x8100.513)
    Encapsulation: VLAN-CCC
    Input packets : 0
    Output packets: 0
    Protocol ccc, MTU: 1522
      Flags: Is-Primary

  Logical interface ge-0/0/2.32767 (Index 335) (SNMP ifIndex 535)
    Flags: Up SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ]  Encapsulation: ENET2
    Input packets : 0
    Output packets: 45
    Protocol multiservice, MTU: Unlimited
      Flags: None
-----------------------------------------------------------------
root@vMX5> show interfaces ge-0/0/2
Physical interface: ge-0/0/2, Enabled, Physical link is Up
  Interface index: 139, SNMP ifIndex: 515
  Link-level type: Flexible-Ethernet, MTU: 1522, MRU: 1530, Speed: 1000mbps,
  BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Source filtering: Disabled, Flow control: Enabled
  Pad to minimum frame size: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  CoS queues     : 8 supported, 8 maximum usable queues
  Current address: 00:05:86:71:25:02, Hardware address: 00:05:86:71:25:02
  Last flapped   : 2015-01-23 14:06:43 MST (00:34:53 ago)
  Input rate     : 304 bps (0 pps)
  Output rate    : 80 bps (0 pps)
  Active alarms  : None
  Active defects : None
  Interface transmit statistics: Disabled

  Logical interface ge-0/0/2.0 (Index 333) (SNMP ifIndex 526)
    Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.512 ]
    Encapsulation: VLAN-VPLS
    Input packets : 559
    Output packets: 0
    Protocol vpls, MTU: 1522
      Flags: Is-Primary

  Logical interface ge-0/0/2.513 (Index 334) (SNMP ifIndex 535)
    Flags: Up SNMP-Traps 0x4000
    VLAN-Tag [ 0x8100.513 ] In(pop) Out(push 0x8100.513)
    Encapsulation: VLAN-CCC
    Input packets : 164
    Output packets: 0
    Protocol ccc, MTU: 1522
      Flags: Is-Primary

  Logical interface ge-0/0/2.32767 (Index 335) (SNMP ifIndex 525)
    Flags: Up SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ]  Encapsulation: ENET2
    Input packets : 0
    Output packets: 77
    Protocol multiservice, MTU: Unlimited
      Flags: None

     



  • 9.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-23-2015 13:48

    Here is the requested output after the changes to the interface configurations.  As expected it did not have an effect on the connection.

    root@vMX7> show configuration interfaces ge-0/0/2
vlan-tagging;
encapsulation vlan-ccc;
unit 513 {
    encapsulation vlan-ccc;
    vlan-id 513;
    input-vlan-map pop;
    output-vlan-map push;
    family ccc;
}
root@vMX7> show l2circuit connections
Layer-2 Circuit Connections:

<...>

Neighbor: 192.168.1.5
    Interface                 Type  St     Time last up          # Up trans
    ge-0/0/2.513(vc 1200001203) rmt OL
Neighbor: 192.168.1.6
No l2circuit connections found

root@vMX7> show interfaces ge-0/0/2
Physical interface: ge-0/0/2, Enabled, Physical link is Up
  Interface index: 139, SNMP ifIndex: 515
  Link-level type: VLAN-CCC, MTU: 1518, MRU: 1526, Speed: 1000mbps,
  BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Source filtering: Disabled, Flow control: Enabled
  Pad to minimum frame size: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  CoS queues     : 8 supported, 8 maximum usable queues
  Current address: 00:05:86:71:98:02, Hardware address: 00:05:86:71:98:02
  Last flapped   : 2015-01-23 14:20:06 MST (00:25:50 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  Active alarms  : None
  Active defects : None
  Interface transmit statistics: Disabled

  Logical interface ge-0/0/2.513 (Index 336) (SNMP ifIndex 525)
    Flags: Up SNMP-Traps 0x4000
    VLAN-Tag [ 0x8100.513 ] In(pop) Out(push 0x8100.513)
    Encapsulation: VLAN-CCC
    Input packets : 0
    Output packets: 0
    Protocol ccc, MTU: 1518
      Flags: Is-Primary

  Logical interface ge-0/0/2.32767 (Index 337) (SNMP ifIndex 535)
    Flags: Up SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ]  Encapsulation: ENET2
    Input packets : 0
    Output packets: 6
    Protocol multiservice, MTU: Unlimited
      Flags: None

root@vMX7>

     

    root@vMX5> show configuration interfaces ge-0/0/2
vlan-tagging;
encapsulation vlan-ccc;
unit 513 {
    encapsulation vlan-ccc;
    vlan-id 513;
    input-vlan-map pop;
    output-vlan-map push;
    family ccc;
}
root@vMX5> show l2circuit connections
Layer-2 Circuit Connections:

<...>

Neighbor: 192.168.1.6
No l2circuit connections found
Neighbor: 192.168.1.7
    Interface                 Type  St     Time last up          # Up trans
    ge-0/0/2.513(vc 1200001203) rmt OL

root@vMX5> show interfaces ge-0/0/2
Physical interface: ge-0/0/2, Enabled, Physical link is Up
  Interface index: 139, SNMP ifIndex: 515
  Link-level type: VLAN-CCC, MTU: 1518, MRU: 1526, Speed: 1000mbps,
  BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Source filtering: Disabled, Flow control: Enabled
  Pad to minimum frame size: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  CoS queues     : 8 supported, 8 maximum usable queues
  Current address: 00:05:86:71:25:02, Hardware address: 00:05:86:71:25:02
  Last flapped   : 2015-01-23 14:06:43 MST (00:39:55 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  Active alarms  : None
  Active defects : None
  Interface transmit statistics: Disabled

  Logical interface ge-0/0/2.513 (Index 339) (SNMP ifIndex 535)
    Flags: Up SNMP-Traps CCC-Down 0x4000
    VLAN-Tag [ 0x8100.513 ] In(pop) Out(push 0x8100.513)
    Encapsulation: VLAN-CCC
    Input packets : 0
    Output packets: 0
    Protocol ccc, MTU: 1518
      Flags: Is-Primary

  Logical interface ge-0/0/2.32767 (Index 340) (SNMP ifIndex 525)
    Flags: Up SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ]  Encapsulation: ENET2
    Input packets : 0
    Output packets: 10
    Protocol multiservice, MTU: Unlimited
      Flags: None

root@vMX5>

     

     



  • 10.  RE: l2circuit ccc connection not coming up - thoughts

     
    Posted 01-23-2015 13:57

    Just trying to help and try different things because I don't see anything wrong with your config.  Sorry my suggestion didn't work.  Go ahead and change it back and good luck.



  • 11.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-23-2015 14:23

    I appreciate the help.  I was just hoping someone had an idea and it may just be something that's not working quite right with the vMX code.  I'll keep poking around



  • 12.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 09-15-2015 10:53

    Hi, 

    Was your problem resolved. Can you share the resolution pls. 

     



  • 13.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-23-2015 12:59

    I've usually not required encapsulation type for the l2circuit but I will try that next as for your requested outputs they are as follows:

     

    root@vMX7> show route 192.168.1.5

inet.0: 14 destinations, 15 routes (14 active, 0 holddown, 0 hidden)
@ = Routing Use Only, # = Forwarding Use Only
+ = Active Route, - = Last Active, * = Both

192.168.1.5/32     @[OSPF/10] 00:01:55, metric 3
                    > to 1.1.7.1 via ge-0/0/0.0
                   #[RSVP/7/1] 00:01:50, metric 3
                    > to 1.1.7.1 via ge-0/0/0.0, label-switched-path vMX7-to-vMX5

inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.1.5/32     *[RSVP/7/1] 00:01:50, metric 3
                    > to 1.1.7.1 via ge-0/0/0.0, label-switched-path vMX7-to-vMX5

     

    root@vMX5> show route 192.168.1.7

inet.0: 15 destinations, 16 routes (15 active, 0 holddown, 0 hidden)
@ = Routing Use Only, # = Forwarding Use Only
+ = Active Route, - = Last Active, * = Both

192.168.1.7/32     @[OSPF/10] 00:03:45, metric 3
                    > to 1.1.5.1 via ge-0/0/0.0
                   #[RSVP/7/1] 00:03:37, metric 3
                    > to 1.1.5.1 via ge-0/0/0.0, label-switched-path vMX5-to-vMX7

inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.1.7/32     *[RSVP/7/1] 00:03:37, metric 3
                    > to 1.1.5.1 via ge-0/0/0.0, label-switched-path vMX5-to-vMX7

root@vMX5>

     



  • 14.  RE: l2circuit ccc connection not coming up - thoughts

    Posted 01-24-2015 09:03

    Hello,

    For L2circuits to work, one needs to run LDP on lo0.0 interface - this is required for LDP to accept targeted sessions.

     

    set protocols ldp interface lo0.0

     - should fix Your issue.

    HTH

    Thanks

    Alex