MPLS LDP CISCO 7200 and Junos Olive

[Paul Dremyn Gomez Chong]

Hi:

i'm implementing a Lab  MPLS envirment my topology is <cisco7200PE(f3/0)>---<(em0.0)JunosOliveRR>

My config: CISCO Lo(3.3.3.3)

=========================

mpls ldp router-id loopback 0 force

interface Loopback0

ip address 3.3.3.3 255.255.255.255
ip router isis CORE

interface FastEthernet3/0 
description LINK_ROUTER_REFLECTOR_JUNIPER
ip address 10.0.0.41 255.255.255.252
ip router isis CORE
speed 10
mpls ip

===================================

JUNIPER OLIVE Lo(6.6.6.6)

set interfaces em0 unit 0 family inet address 10.0.0.42/30 primary
set interfaces em0 unit 0 family iso
set interfaces em0 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 6.6.6.6/32
set interfaces lo0 unit 0 family iso address 47.0004.004d.0001.0001.0c20.1111.00
set routing-options router-id 6.6.6.6
set routing-options autonomous-system XXX
set protocols mpls interface all
set protocols isis level 1 disable
set protocols isis interface em0.0 point-to-point
set protocols isis interface em0.0 level 2 metric 10
set protocols isis interface lo0.0 passive
set protocols isis interface lo0.0 level 2 metric 10
set protocols isis interface lo0.0 level 2 hello-interval 10
set protocols isis interface lo0.0 level 2 hold-time 30
set protocols ldp transport-address 6.6.6.6
set protocols ldp interface all
set protocols ldp interface lo0.0
conectivity between cisco and junos exist and isis neighbor es up but ldp not.

some troubleshouting:

PE3#show mpls ldp neighbor --->no appears

PE3#show mpls interfaces
Interface IP Tunnel BGP Static Operational
FastEthernet3/0 Yes (ldp) No No No Yes ---> ldp operation es Yes

PE3#show mpls ldp parameters
LDP Feature Set Manager: State Initialized
LDP features:
Protocol version: 1
Session hold time: 180 sec; keep alive interval: 60 sec
Discovery hello: holdtime: 15 sec; interval: 5 sec
Discovery targeted hello: holdtime: 90 sec; interval: 10 sec
Downstream on Demand max hop count: 255

root@RRCLONAR> show ldp interface
Interface Label space ID Nbr count Next hello
em0.0 6.6.6.6:0 0 4   ---------------------------> interface ldp JUNOS
lo0.0 6.6.6.6:0 0 0

root@RRCLONAR> show ldp neighbor ---->no appears

root@RRCLONAR> show interfaces em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 17
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps
Device flags : Present Running
Interface flags: SNMP-Traps
Link type : Full-Duplex
Current address: 08:00:27:99:aa:a9, Hardware address: 08:00:27:99:aa:a9
Last flapped : 2016-08-31 14:30:21 UTC (00:19:22 ago)
Input packets : 569
Output packets: 1124

Logical interface em0.0 (Index 64) (SNMP ifIndex 18)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 569
Output packets: 1124
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re, Is-Primary
Addresses, Flags: Primary Is-Preferred Is-Primary
Destination: 10.0.0.40/30, Local: 10.0.0.42, Broadcast: 10.0.0.43
Protocol iso, MTU: 1497
Flags: Is-Primary
Protocol mpls, MTU: 1488, Maximum labels: 3
Flags: Is-Primary

root@RRCLONAR> show isis adjacency
Interface System L State Hold (secs) SNPA
em0.0 PE3 2 Up 22

==============================================

thanks in advance

[Nagendra Kumar Nainar]

Hi,

On Cisco side, LDP router ID is set to loopback0. Loopback0 interface is part of ISIS BACKBOND while F3/0 (I guess towards Juniper) is part of ISIS CORE. 

If LDP Router ID is not reachable, the session will not be established.

You need to have reachability from 3.3.3.3 (loopback of Cisco) to 6.6.6.6 (Juniper loopback).

Advertise them as part of same ISIS and it should come up.

HTH,

Nagendra

[Paul Dremyn Gomez Chong]

Hi Nagendra:

i appreciate your response, but  i omited the ISIS name for security purposes.

i know the both loobacks (junos and cisco) are exchange.in the isis:

PE3#show ip route | i 6.6.6.6
i L2 6.6.6.6 [115/73] via 10.0.0.42, 00:01:55, FastEthernet3/0

root@RRCLONAR> show route | match 3.3.3.3
3.3.3.3/32 *[IS-IS/18] 00:02:45, metric 20
1:6147:100:3.3.3.3:239.192.1.1/144

root@RRCLONAR> ping 3.3.3.3 source 6.6.6.6
PING 3.3.3.3 (3.3.3.3): 56 data bytes
64 bytes from 3.3.3.3: icmp_seq=0 ttl=255 time=32.841 ms

i thinks the isis is correct but my problems is for ldp.

Thanks

[Nagendra Kumar Nainar · Accepted solution]

Hi

can you get "show MPLS LDP discovery" 

[Paul Dremyn Gomez Chong]

Hi Nagendra: this is the info, PE3 also has 2 ldp with other cisco routers in up

PE3#show mpls ldp dis
PE3#show mpls ldp discovery
Local LDP Identifier:
3.3.3.3:0
Discovery Sources:
Interfaces:
POS1/0 (ldp): xmit/recv
LDP Id: 1.1.1.1:0
FastEthernet3/0 (ldp): xmit/recv
LDP Id: 6.6.6.6:0
GigabitEthernet6/0 (ldp): xmit/recv
LDP Id: 8.8.8.8:0
PE3#

PE3#show mpls ldp neighbor
Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 3.3.3.3:0
TCP connection: 1.1.1.1.646 - 3.3.3.3.35450
State: Oper; Msgs sent/rcvd: 3125/3107; Downstream
Up time: 1d20h
LDP discovery sources:
POS1/0, Src IP addr: 10.0.0.65
Addresses bound to peer LDP Ident:
1.1.1.1 10.0.0.9 10.0.0.65 10.0.0.50
10.0.0.34 10.0.0.26
Peer LDP Ident: 8.8.8.8:0; Local LDP Ident 3.3.3.3:0
TCP connection: 8.8.8.8.39011 - 3.3.3.3.646
State: Oper; Msgs sent/rcvd: 3078/3063; Downstream
Up time: 1d19h
LDP discovery sources:
GigabitEthernet6/0, Src IP addr: 10.0.0.53
Addresses bound to peer LDP Ident:
8.8.8.8 10.0.0.33 10.0.0.37 10.0.0.6
10.0.0.53
PE3#