[erlang-questions] Multiple Diameter Connection issue

[Dinusha Ganganath Perera]

Dear Anders,

Please find the trace.

Thanks & BRs,
Dinusha

On Thu, Oct 19, 2017 at 5:28 PM, <anders.gs.svensson@REDACTED> wrote:

> Hi Dinusha.
>
> Enable the following trace while your nodes are trying to connect and
> it will narrow it down.
>
> dbg:tracer().
> dbg:p(all,[c,timestamp]).
> dbg:tp(diameter_peer_fsm, start, x).
> dbg:tp(diameter_peer_fsm, terminate, x).
>
> Send me the resulting output in the Erlang logs. You can disable the
> trace with dbg:stop_clear().
>
> Anders
>
>
>
> Dinusha Ganganath Perera writes:
> > Dear Anders,
> >
> > My Application is client.
> >
> > I am trying to establish multiple connections with remote Diameter
> Server.
> >
> >
> >
> > Thanks & BRs,
> > Dinusha
> >
> >
> >
> >
> >
> > On Thu, Oct 19, 2017 at 2:59 PM, <anders.gs.svensson@REDACTED>
> wrote:
> >
> >     Hi Dinusha.
> >
> >     Which of the two nodes in your test is running OTP/diameter: client,
> >     server, or both?
> >
> >     Anders
> >
> >
> >
> >     Dinusha Ganganath Perera writes:
> >     > Dear Anders,
> >     >
> >     > Thanks for your reply.
> >     >
> >     > I upgraded Erlang and current version of diameter library is 2.1.
> >     >
> >     > But issue is not resolved.
> >     >
> >     >
> >     > Thanks & BRs,
> >     > Dinusha
> >     >
> >     > On Tue, Oct 17, 2017 at 4:15 PM, <anders.gs.svensson@REDACTED>
> wrote:
> >     >
> >     >     diameter 1.3 is from OTP R15B03, released in November 2012,
> which is
> >     >     the release that added the restrict_connections option, which
> looks
> >     to
> >     >     be what you're having problems with. I don't recall any issues
> (not
> >     >     that I recall much of anything from 2012), and don't see
> anything in
> >     >     the release notes, but I suggest trying with a more recent
> release
> >     for
> >     >     starters.
> >     >
> >     >     The latest is diameter 2.1.1 in OTP 20.1.2. (Although there's
> a fix
> >     to
> >     >     a problem introduced in 20.1 coming in 20.1.3, unrelated to
> >     >     restrict_connections.)
> >     >
> >     >     Anders
> >     >
> >     >
> >     >     erlang-questions-request@REDACTED writes:
> >     >     > Date: Mon, 16 Oct 2017 21:24:34 +0545
> >     >     > From: Dinusha Ganganath Perera <dinushaganganath@REDACTED>
> >     >     > To: erlang-questions@REDACTED
> >     >     > Subject: [erlang-questions] Multiple Diameter Connection
> issue
> >     >     > Message-ID:
> >     >     >       <CAOMUzJjp06Dx=i8ty4T38cS_kGDiwECMM1GECmL1uqTPyG6xRw@
> >     mail.gmail.com
> >     >     >
> >     >     > Content-Type: text/plain; charset="utf-8"
> >     >     >
> >     >     > Hi All,
> >     >     >
> >     >     > I tried to establish two diameter connection to same
> diameter peer
> >     and
> >     >     port
> >     >     > (used two different source port).
> >     >     > One connection was established successfully and other
> connection
> >     was
> >     >     > failed.
> >     >     > The failed connection sent below tcp packets to diameter
> peer, but
> >     did
> >     >     not
> >     >     > sent CER to diameter node.
> >     >     >
> >     >     > 1. sent [SYN] to diameter node
> >     >     > 2. received [SYN, ACK] from diameter node
> >     >     > 3. sent [ACK] to diameter node
> >     >     > 4. sent [FIN, ACK] to diameter node
> >     >     > 5. received [FIN, ACK] from diameter node
> >     >     >
> >     >     > If I down established connection, then failed one is
> successfully
> >     >     > established.
> >     >     >
> >     >     > I used below application services,
> >     >     >
> >     >     > {application,
> >     >     > [{alias, smsc_diameter_cli_dia_1},
> >     >     > {dictionary, rfc4006_cc_Gy},
> >     >     > {module, smsc_diameter_clii_cb},
> >     >     > {answer_errors, callback},
> >     >     > {sequence, {0,19}},
> >     >     > {share_peers, true},
> >     >     > {use_shared_peers, true},
> >     >     > {restrict_connections, false}]}
> >     >     >
> >     >     >
> >     >     > I used diameter-1.3 erlang library.
> >     >     >
> >     >     >
> >     >     > Please help me to solve this issue.
> >     >     >
> >     >     >
> >     >     > Thanks & BRs,
> >     >     > Dinusha
> >     >
> >     >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171019/a90bfb4d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Charging2_2017-10-19_17-46-48.log
Type: application/octet-stream
Size: 122160 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171019/a90bfb4d/attachment.obj>