[j-nsp] LDP issue between M10i and ERX

[Junaid]

Iftikhar and Oliver,

Many thanks for your inputs. I enabled LDP on loopback (but only on
the M10i side) but the result is the same. Dont you think that running
LDP on loopback is required for establishing directed/targeted LDP
session? Is there something I am missing on the ERX side?

Regards,

Junaid

On Tue, Apr 15, 2008 at 1:17 PM, Schmidt Oliver <OSchmidt at axians.de> wrote:
>
>  Woking configuration:
>  protocols {
>     mpls {
>         interface ge-0/1/0.2;
>     }
>     ldp {
>         interface ge-0/1/0.2;
>         interface lo0.0;
>     }
>
>  You need the lo0 interface to establish the ldp session (Hello packages).
>
>
>
>  -----Ursprüngliche Nachricht-----
>  Von: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] Im Auftrag von Junaid
>  Gesendet: Dienstag, 15. April 2008 09:43
>  An: juniper-nsp
>  Betreff: Re: [j-nsp] LDP issue between M10i and ERX
>
>
>
>  A little help required people .... :(
>
>  Regards,
>  Junaid
>
>
>  On Mon, Apr 14, 2008 at 8:28 PM, Junaid <junaid.x86 at gmail.com> wrote:
>  > Hi,
>  >
>  >  I am trying to enable MPLS between ERX1440 and M10i routers. The
>  >  routers are connected via an Ethernet switch. I have three Cisco
>  >  routers on the same subnet as well. Strangely, all routers are able to
>  >  form LDP sessions with each other but M10i and ERX are not
>  >  establishing LDP session. Although both junipers are able to establish
>  >  LDP with three ciscos but they are not able to form LDP with each
>  >  other. I received the following debug logs on junipers:
>  >
>  >  Legend:
>  >  -----------
>  >  AAA.BBB.CCC.DDD : Loopback IP address of ERX
>  >  WWW.XXX.YYY.ZZZ : Loopback IP address of M10i
>  >
>  >
>  >  On M10i:
>  >
>  >   Connection AAA.BBB.CCC.DDD state Opening -> Open
>  >   Session AAA.BBB.CCC.DDD state Connecting -> Initialized
>  >   Session AAA.BBB.CCC.DDD state Initialized -> OpenSent
>  >   LDP sent TCP PDU WWW.XXX.YYY.ZZZ -> AAA.BBB.CCC.DDD (none)
>  >   ver 1, pkt len 52, PDU len 48, ID WWW.XXX.YYY.ZZZ:0
>  >    Msg Initialization (0x200), len 38, ID 182964
>  >      TLV SesParms (0x500), len 14
>  >        Ver 1, holdtime 30, flags <> (0x0)
>  >        vect_lim 0, max_pdu 4096, id AAA.BBB.CCC.DDD:0
>  >      TLV GracefulRestartParms (0x8503), len 12
>  >        Reconnect time 0 ms, recovery time 0 ms.
>  >   Unexpected EOF from AAA.BBB.CCC.DDD
>  >
>  >
>  >  ON ERX:
>  >
>  >  ldpMessages (default): ldp_demux.c:677: LDPDemuxProcessSesMsg: WWW.XXX.YYY.ZZZ
>  >  ldpMessages (default):   Msg Initialization (0x200), len 38, ID 182949
>  >  ldpMessages (default):     TLV SesParms (0x500), len 14
>  >  ldpMessages (default):       Ver 1, holdtime 30, flags <Downstream
>  >  Unsolicited, Loop Detection disabled> (0x0)
>  >  ldpMessages (default):       vect_lim 0, max_pdu 4096, id AAA.BBB.CCC.DDD:0
>  >  ldpMessages (default):     TLV GracefulRestartParms (0x8503), len 12
>  >  ldpMessages (default):       FT Flags <Learn From Network Flag set>, (0x1)
>  >  ldpMessages (default):       Reconnect time 0 ms, recovery time 0 ms.
>  >  ldpMessages (default): LDPDemuxProcessSesMsg: Recv init message for
>  >  passive session
>  >  ldpGeneral (default): ldp_demux.c:820: LDPDemuxProcessSesMsg: Peer
>  >  Does not exists for WWW.XXX.YYY.ZZZ
>  >  ldpGeneral (default): ldp_tcp_read.c:640: LDPProcessCommSap: The sap
>  >  handle has been put in the error list
>  >  ldpPeer (default): TCPClose: hHandle 0x8d3ed654 socket 0x8d3ed2e4 to
>  >  WWW.XXX.YYY.ZZZ:1291
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:606: FiconTcpSocket
>  >  acceptNotify: 0x8d3ed674 sapHandle 0x8d3ed7b4, acceptCount = 1
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:3548:
>  >  doSocketNotify: sap 0x8d3ed7b4 acceptCount 1
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:3570:
>  >  doSocketNotify: sap 0x8d3ed7b4 FiconTcpSocket 0x8d3ed674
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:2486: TCPAccept:
>  >  hHandle 0x8d3ed654 socket 0x8d3ed2e4 local port 646 remote
>  >  WWW.XXX.YYY.ZZZ:4762
>  >  ldpMessages (default): [LDPDemuxProcessAccept]: Accepted TCP
>  >  connection from WWW.XXX.YYY.ZZZ:4762 on socket 0x8d3ed654
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:725: FiconTcpSocket
>  >  receiveNotify: 0x8d3ed2e4 sapHandle 0x8d3ed654
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:3548:
>  >  doSocketNotify: sap 0x8d3ed654 receive event acceptCount 0
>  >  ldpPeer (default): rsFiconCrldpNetworkServices.cc:3570:
>  >  doSocketNotify: sap 0x8d3ed654 FiconTcpSocket 0x8d3ed2e4
>  >  ldpGeneral (default): ldp_tcp_read.c:284: LDPProcessCommSap: Message
>  >  received over non Session Socket, map to session
>  >
>  >
>  >  I have used the following config templates for junipers:
>  >
>  >
>  >  For Juniper (JunOS):
>  >
>  >  # set interfaces ge-0/1/0 unit 2 family mpls
>  >  # set protocols mpls interface ge-0/1/0.2
>  >
>  >  # set routing-options router-id <loopback 0 IP address>
>  >  # set protocols ldp interface ge-0/1/0.2
>  >  # set protocols ldp transport-address router-id
>  >
>  >
>  >  For Juniper (JunOSe):
>  >
>  >  #(config)# mpls
>  >  #(config)# mpls ldp
>  >
>  >  #(config)# interface g1/0
>  >  #(config-if)# mpls
>  >  #(config-if)# mpls ldp
>  >
>  >
>  >
>  >  Any idea what the issue could be?
>  >
>  >
>  >  Regards,
>  >  Junaid
>  >
>
> _______________________________________________
>  juniper-nsp mailing list juniper-nsp at puck.nether.net
>  https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>  Sitz der NK Networks & Services GmbH: Von-der-Wettern-Straße 15, 51149 Köln
>  Registergericht: Amtsgericht Köln, Registernummer HRB 30805
>  Geschäftsführer: Tonis Rüsche
>
>