[c-nsp] ldp session down

[1router.geek]

I'm running into a problem trying to move some ldp tunnels from a gsr
running 12.0(26)s2 code to a new 6513 with 12.2(33)sra.
The new code is treating the ldp session differently than the old code.
I've got a case open with Cisco but they've been less
than helpful to this point.  The problem is with sessions
to a juniper router that's configured to use a non primary loopback for the
transport address.  We have standardized ldp to use lo1 on cisco's and
a non-primary on all junipers so we can control ldp routing
with a policy based on the /24 for the ldp addresses.  To date we haven't
had any problems with this but now I'm trying to move some sessions
off the gsr to the 6513 and the sessions to the junipers won't come up
on the 6513.

Any ideas on why the sra code is disabling this because of router id?
The s2 code
recognizes the router id is different and brings the ldp session up
with the primary
router id while the tcp connection is to the configured transport address.


not working:
sh mpls l2 vc destination 208.174.15.5 detail
Local interface: Gi10/6.711 up, line protocol up, Eth VLAN 711 up
 Destination address:
208.174.15.5, VC ID: 11711, VC status: down
   Output interface: if-?(0), imposed label stack {}
   Preferred path: not configured
   Default path: no route
   Next hop: Invalid MOI
 Create time: 00:07:28, last status change time: 00:07:28

 Signaling protocol: LDP, peer 208.174.15.5:0 down
   MPLS VC labels: local 1050, remote unassigned
   Group ID: local 0, remote unknown
   MTU: local 1500, remote unknown

   Remote interface description:
 Sequencing: receive disabled, send disabled
 VC statistics:
   packet totals: receive 0, send 0
   byte totals:   receive 0, send 0
   packet drops:  receive 0, send 0


show ip ro 208.174.15.5
Routing entry for 208.174.15.5/32
  Known via "isis", distance 115, metric 24, type level-2
  Redistributing via isis

  Last update from 208.175.200.242 on Vlan240, 1w2d ago
  Routing Descriptor Blocks:
  * 208.175.200.242, from
208.172.2.61, via Vlan240
      Route metric is 24, traffic share count is 1

#sh ip cef 208.174.15.5
208.174.15.5/32
  nexthop
208.175.200.242 Vlan240 label 451

#sh mpls forwarding-table 208.174.15.5
Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
Label  Label or VC   or Tunnel Id      Switched      interface

767    451           208.174.15.5/32   0             Vl240      208.175.200.242

Mar 20 03:08:55.124 GMT: %ATOM_TRANS-4-CONFIG: 208.174.15.5 mismatches
the peer router id 208.172.2.61
Mar 20 03:09:04.268 GMT: ldp-trgtnbr:
208.174.15.5 Received address deletion
notif start; flags 0x1F
Mar 20 03:09:04.268 GMT: ldp-trgtnbr: 208.174.15.5 Clear peer start; flags 0x17

Mar 20 03:09:04.268 GMT: ldp-trgtnbr:

tdp_disable_non_directly_connected_session; target 208.174.15.5
Mar 20 03:09:04.268 GMT: ldp-trgtnbr: 208.174.15.5 Undefer cleanup start;

clearcnt 0, flags 0x14
Mar 20 03:09:04.272 GMT: ldp-trgtnbr: 208.174.15.5 Set peer start; flags 0x10
Mar 20 03:09:04.272 GMT: ldp-trgtnbr: 208.174.15.5
 Defer peer cleanup; cleancnt
1
Mar 20 03:09:04.272 GMT: ldp-trgtnbr: 208.174.15.5 Set peer finished; flags
0x1F
Mar 20 03:09:04.272 GMT: ldp-trgtnbr:
208.174.15.5 Undefer cleanup finish;
clearcnt 1, flags 0x1F
Mar 20 03:09:04.272 GMT: ldp-trgtnbr: 208.174.15.5 Clear peer finished; flags
0x1F
Mar 20 03:09:04.272
 GMT: ldp-trgtnbr: 208.174.15.5 Received address deletion
notif finish; flags 0x1F
Mar 20 03:09:04.276 GMT: ldp-trgtnbr: Disable session, target 208.174.15.5
 dhcb
walk, rev 13


working:
Mar 20 03:33:50.771 GMT: ldp-trgtnbr: 208.174.15.5 Clear peer finished; flags
0x13
Mar 20 03:33:50.771 GMT: ldp-trgtnbr:
208.174.15.5 Received address deletion
notif finish; flags 0x13
Mar 20 03:33:50.775 GMT: ldp-trgtnbr: Disable session, target 208.174.15.5 dhcb
walk, rev 36
Mar 20 03:33:
52.587 GMT: %LDP-5-NBRCHG: LDP Neighbor 208.172.2.61:0 is UP
Mar 20 03:33:53.199 GMT: ldp-trgtnbr: 208.174.15.5 Received address addition
notif start; flags 0x13

Mar 20 03:33:53.199 GMT: ldp-trgtnbr: 208.174.15.5 Set peer start; flags 0x13
Mar 20 03:33:53.199 GMT: ldp-trgtnbr: 208.174.15.5 Set peer finished; flags

0x1F
Mar 20 03:33:53.199 GMT: ldp-trgtnbr: 208.174.15.5 Received address addition
notif finish; flags 0x1F
Mar 20 03:33:53.199 GMT: %ATOM_TRANS-4-CONFIG:
208.174.15.5 is not a router id,
use 208.172.2.61 instead



Any ideas as to why the behavior has changed?

thanks in advance,
sean