cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
787
Views
0
Helpful
1
Replies

1 Way LDP between SRX210/Cisco 2901

meritcisco
Level 1
Level 1

Working on a MPLS SP lab. It appears I am unable to establish 2 way ldp session between my Juniper SRX and Cisco 2901. My SRX shows an ldp neighbor, but my 2901 does not. Output below. I'm sure this is likely an issue with the SRX and I am awaiting feedback from their forums, however just wanted to see if I was missing anything on the cisco side.

 

P-R11Cisco_2901#show mpls ldp  neighbor 
    Peer LDP Ident: 3.47.28.11:0; Local LDP Ident 34.72.90.1:0
        TCP connection: 3.47.28.11.646 - 34.72.90.1.23300
        State: Oper; Msgs sent/rcvd: 225/221; Downstream
        Up time: 02:59:02
        LDP discovery sources:
          GigabitEthernet0/0, Src IP addr: 10.254.255.5
        Addresses bound to peer LDP Ident:
          3.47.28.11      10.254.255.5   
 
*Apr 14 03:07:21.735: ldp: Discovery hold timer expired for adj 0x3DE75A60, 9.17.82.10:0, will close conn
*Apr 14 03:07:21.735: ldp: Unregistered from LDP TCB database tcb 0x3DE7AC84 [key 9659], total 2
*Apr 14 03:07:21.735: ldp: Closing ldp conn 34.72.90.1:11413 <-> 9.17.82.10:646, adj 0x3DE75A60
*Apr 14 03:07:23.775: ldp: Opening ldp conn; adj 0x3DE75A60, 34.72.90.1 <-> 9.17.82.10; with normal priority
*Apr 14 03:07:23.775: ldp: No MD5 password protection for peer 9.17.82.10:0
*Apr 14 03:07:23.775: ldp: Registered TCB with LDP TCB database tcb 0x227578BC [key 9676], total 3
P-R11Cisco_2901#
P-R11Cisco_2901#
*Apr 14 03:07:38.775: ldp: Discovery hold timer expired for adj 0x3DE75A60, 9.17.82.10:0, will close conn
*Apr 14 03:07:38.775: ldp: Unregistered from LDP TCB database tcb 0x227578BC [key 9676], total 2
*Apr 14 03:07:38.775: ldp: Closing ldp conn 34.72.90.1:64580 <-> 9.17.82.10:646, adj 0x3DE75A60
 
root@PE-R8FW3JunOS_SRX210> show ldp neighbor 
Address            Interface          Label space ID         Hold time
10.254.255.2       fe-0/0/5.0         34.72.90.1:0             13
 
root@PE-R8FW3JunOS_SRX210> show ldp overview   
Instance: master
  Router ID: 9.17.82.10
  Message id: 3
  Configuration sequence: 1
  Deaggregate: disabled
  Explicit null: disabled
  IPv6 tunneling: disabled
  Strict targeted hellos: disabled
  Loopback if added: yes
  Route preference: 9
  Capabilities enabled: none
  Protocol modes:
    Distribution: unsolicited
    Retention: liberal
    Control: ordered
  Sessions:
    Nonexistent: 1
  Timers:
    Keepalive interval: 10, Keepalive timeout: 30
    Link hello interval: 5, Link hello hold time: 15
    Targeted hello interval: 15, Targeted hello hold time: 45
    Label withdraw delay: 60
  Graceful restart:
    Restart: enabled, Helper: enabled, Restart in process: false
    Reconnect time: 60000, Max neighbor reconnect time: 120000
    Recovery time: 160000, Max neighbor recovery time: 240000
  Traffic Engineering:
    Bgp igp: disabled
    Both ribs: disabled
    Mpls forwarding: disabled
  IGP:
    Tracking igp metric: disabled
    Sync session up delay: 30
  Session protection:
    Session protection: disabled
    Session protecton timeout: 0
  Interface addresses advertising:
    9.17.82.10
    10.254.255.3

Interface GigabitEthernet0/1:
        Type Unknown
        IP labeling enabled (ldp):
          Interface config
          IGP config
        LSP Tunnel labeling not enabled
        IP FRR labeling not enabled
        BGP labeling not enabled
        MPLS operational
        MTU = 1500​
 
 
 
1 Reply 1

Harold Ritter
Spotlight
Spotlight

From the output provided, you do not have a fully functional LDP session from either side. From the SRX side, you see the following that tells you that this side does not consider the neighbor to be functional:

 

root@PE-R8FW3JunOS_SRX210> show ldp overview   
Instance: master
  Router ID: 9.17.82.10
...
  Sessions:
    Nonexistent: 1
 
The issue comes partly from the different commands in IOS and JUNOS to check the neighbor relationship.
 
IOS: show mpls ldp nei
JUNOS: show ldp session
 
Regards,

 

 

Regards,
Harold Ritter, CCIE #4168 (EI, SP)