Re: [Seagull-users] How to open multiple concurrent channels/sessions

[Peter M. <P.Mills@F5.com>]

Volker,

BTW in this case Seagull is acting as the Server.

Regards

Peter

From: Peter Mills
Sent: 22 December 2011 17:26
To: 'Volker Bensberg'
Cc: gul...@li...; Lee Orrick
Subject: RE: [Seagull-users] How to open multiple concurrent channels/sessions

Volker

Thanks

It seems like if you are polling using different (TCP) channel connections each time, each channel "name" used needs to be explicitly defined and referenced both within the config and scenario sections.   In this particular case the destination port is the same but the source port is continually changing, so for each and every poll you would have to manually add another channel name

<define entity="channel"
    name="channel-1"
    protocol="diameter-v1"
    transport="trans-1"
    open-args="mode=client;dest=127.0.0.1:3868">
  </define>

  <define entity="channel"
    name="channel-2"
    protocol="diameter-v1"
    transport="trans-1"
    open-args="mode=client;dest=127.0.0.1:3868">
  </define>
Etc.

Appreciate some clarification of the global=no option but it seems that by so doing you no longer have to explicitly configure a set of channels in the config file but you still have to do so within the scenario which could save some typing!

Regards

Peter
From: Volker Bensberg [mailto:VBe...@or...]<mailto:[mailto:VBe...@or...]>
Sent: 22 December 2011 16:59
To: Peter Mills
Cc: gul...@li...<mailto:gul...@li...>; Lee Orrick
Subject: Re: [Seagull-users] How to open multiple concurrent channels/sessions

Hi,

I assume you asking for 3 different features seagull supports:

1. Multiple sessions over one channel
   If you run the example located in exe-env/diameter-env/run
   you will see that the number of concurrent sessions just depends on the
   "call-rate" defined in config file

   To run this is a good exercise to get familiar with seagull.

2. Multiple channels.
   For this you have to define it in the config like this
   For every channel define a unique name and port.

  <define entity="channel"
    name="channel-2"
    protocol="diameter-v1"
    transport="trans-1"
    open-args="mode=client;dest=127.0.0.1:3868">
  </define>

  <define entity="channel"
    name="channel-2"
    protocol="diameter-v1"
    transport="trans-1"
    open-args="mode=client;dest=127.0.0.1:3869">
  </define>

   In the scenario file it looks like this

<scenario>
  ...
  <traffic>
   <send channel="channel-1">
         ....
   </send>
    ....
   <send channel="channel-2">
         ....
   </send>
  </traffic>
</scenario


3. Open a channel in the traffic section of a scenario
   In the config file you set global=no"

   <define entity="channel" name="channel-1" global="no" protocol="diameter-v1" transport="trans-1" open-args="mode=client;dest=127.0.0.1:3868">

The scenario looks like this. See the open and close statements.

<scenario>
  ...
  <traffic>
    <send channel="channel-1">
      <action>
        <open args="mode=client;dest=">127.0.0.1:3868</open>
        ...
      </action>
      ...
    </send>

    <receive channel="channel-1">
      ...
    </receive>
     ...

    <receive channel="channel-1">
      ...
      <action>
        ...
        <close></close>
      </action>
    </receive>
  </traffic>
</scenario


Peter Mills <P.Mills@F5.com<mailto:P.Mills@F5.com>> wrote on 22.12.2011 17:14:29:

> From: Peter Mills <P.Mills@F5.com<mailto:P.Mills@F5.com>>
> To: "gul...@li...<mailto:gul...@li...>" <gul...@li...<mailto:gul...@li...>>
> Cc: Lee Orrick <l.o...@f5...<mailto:l.o...@f5...>>
> Date: 22.12.2011 17:15
> Subject: Re: [Seagull-users] How to open multiple concurrent channels/sessions
>
> Hi
>
> I am fairly new user of Seagull and trying to establish how it can be configured to service
> multiple concurrent channels/session requests using the same scenario file.
>
> Does the following mean that Seagull can only accept one call at a time and that call must be
> closed down before the next can be processed?
>
> An example config would be much appreciated.
>
>
>
> number-calls
>
> Number of calls to be done. It is available for client and server. Once the number of calls is
> reached, no new calls are :
> - placed by the client(note that some additional calls can be placed, but no less)
> - accepted by the server.
> WARNING: the init section of the scenario is considered as one call for the server side.
>
>
>
> I also noticed that there is a command called global="no" which may help.
>
> <define entity="channel"
>     name="channel-1"
>     protocol="diameter-v1"
>     transport="trans-1"
>     open-args="mode=server;source=127.0.0.1:3868">
>   </define>
>
>
> global
>
> Indicate if a channel is declared and used globally (opened once) or needs to be opened for each
> scenario call (using the "open" action). By default, the channel is declared globally. adding
> global="no" will allow to open channels in the scenarios
>
>
>
> Thanks
>
> Peter------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev_______________________________________________
> Gull-users mailing list
> Gul...@li...<mailto:Gul...@li...>
> https://lists.sourceforge.net/lists/listinfo/gull-users

The information included in this e-mail and any files transmitted with it is strictly confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this e-mail as well as any attachment from your system. If you are not the intended recipient you are not authorized to use and/or copy this message and/or attachment and/or disclose the contents to any other person.