[j-nsp] Junos MPLS/LDP L2circuit label issue

[Scott Harvanek]

Hello folks, I'm trying to setup a l2circuit between a M20 box running 
Junos 8.5 and a cisco 1841 over two bonded T1s, the relevant 
configuration bits follow:

 > show configuration interfaces lsq-3/0/0
per-unit-scheduler;
unit 3 {
     encapsulation multilink-ppp;
     family inet {
         address 10.7.7.1/30;
     }
     family mpls;
}

 > show configuration interfaces ge-2/0/0
vlan-tagging;
encapsulation vlan-ccc;
unit 777 {
     encapsulation vlan-ccc;
     vlan-id 777;
}

 > show configuration protocols mpls
interface all;

 > show configuration protocols ldp
interface lsq-3/0/0.3;
interface lo0.0;


 > show configuration protocols l2circuit
neighbor 10.104.1.2 {
     interface ge-2/0/0.777 {
         virtual-circuit-id 777;
     }
}

 > show configuration protocols ospf
traffic-engineering;
export ospf;
area 0.0.0.0 {
interface lsq-3/0/0.3 {
         authentication {
             simple-password //## SECRET-DATA
         }
     }
}


 > show ldp database
Input label database, 101.101.1.7:0--101.101.1.2:0
   Label     Prefix
       3     101.101.1.2/32
  100000     L2CKT CtrlWord VLAN VC 777

Output label database, 101.101.1.7:0--101.101.1.2:0
   Label     Prefix
  100912     101.101.1.2/32
       3     101.101.1.7/32


 > 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          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 101.101.1.2
     Interface                 Type  St     Time last up          # Up 
trans
     ge-2/0/0.777(vc 777)      rmt   Up     Feb 21 16:27:26 
2012           1
       Local interface: ge-2/0/0.777, Status: Up, Encapsulation: VLAN
       Remote PE: 101.101.1.2, Negotiated control-word: Yes (Null)
       Incoming label: 100864, Outgoing label: 100000
         Time                  Event                   Interface/Lbl/PE
         Feb 21 16:27:26 2012  status update timer
         Feb 21 16:27:24 2012  PE route changed
         Feb 21 16:27:24 2012  Out lbl Update                    100000
         Feb 21 16:27:24 2012  In lbl Update                     100864
         Feb 21 16:27:24 2012  loc intf up                 ge-2/0/0.777


As you can see, the juniper thinks the VC is up but it's not sending the 
label out as per the ldp database and so the cisco side never sees it up 
or the label information.
At this point I believe the cisco is operating properly as it is sending 
the L2CKT information.

The Juniper does install everything in mpls.0:

 > show route table mpls

mpls.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 01:24:50, metric 1
                       Receive
1                  *[MPLS/0] 01:24:50, metric 1
                       Receive
2                  *[MPLS/0] 01:24:50, metric 1
                       Receive
100864             *[L2CKT/7] 00:25:55
 > via ge-2/0/0.777, Pop       Offset: 4
100912             *[LDP/9] 00:25:55, metric 1
 > via lsq-3/0/0.3, Pop
100912(S=0)        *[LDP/9] 00:25:55, metric 1
 > via lsq-3/0/0.3, Pop
ge-2/0/0.777       *[L2CKT/7] 00:25:55, metric2 1
 > via lsq-3/0/0.3, Push 100000 Offset: -4


I've tried many different traceoptions but nothing has proven useful in 
generating an error message that can be acted upon.  Does anyone have 
any ideas on why a label that exists both on the l2circuit and in mpls.0 
would not be getting inserted into the ldp database such as this?

thanks guys,