Is it possible to create 2 RSOe from 1 Afaria to 2 Relay server

[former_member686053]

Hi,

Can I create 2 RSOE from 1 afaria to 2 different Relay server?

Any configuration sample?

I have this but now work:

Example Syntax for the Afaria Master server:

-cs host=localhost;port=5002 -cr host=10.56.71.198;port=80;url_suffix=/IAS_relay_server/server/rs_server.dll;https=0;host=10.56.71.199;port=80;url_suffix=/IAS_relay_server/server/rs_server.dll;https=0 -f 2345 -id uf$0x -t 1234567890 -v 3

[former_member686053]

Thnx Tracy,

Now both sides are FULL

Now I have to test thins toplogy.

First I drop connection of an Afaria server

Then I drop connection of an Relay server.

Then I try 1 afaria and 1 relay

If all  works, I go to next step, sqlanywhere replication

[tracy_barkley]

Great news!  Have fun testing!

[former_member686053]

Seems no error Tracy

[tracy_barkley]

I would have to see the logs from the relays, and the OEs, and the two rs.configs.  That will require a support incident be opened.  Myself or any other engineer which takes the incident can then solve the issue.

Tracy

[former_member686053]

Hi Tracy,

I collect all logs and configs

Very long document. Thats why I shared in cloud shown as link below

https://astdisk.yasar.com.tr/owncloud/public.php?service=files&t=1f0c9a7ab62d950744db6f14d9df5e07

[tracy_barkley]

Tevfik,

I don't see anything wrong with any of the logs or setups.  I am not sure why that second server is only reporting partial.  The only thing I do notice is there are slight differences between the two rs.configs.  Can you rename the rs.config on the slave server and copy over the one from the master and then restart the relay server service on the slave.  Let me know if that changes the behavior.

Tracy

[former_member686053]

I tried to what u said.

I have 6 OE 3 of them from Master, other 3 are from Slave.

I check allOEs connected to Relays show below:

I. 2014-12-17 14:44:13.092+0200 <UpChannel-0001> Successfully connected to relay server: 172.31.254.88:5007

I. 2014-12-17 14:44:13.094+0200 <UpChannel-0000> Successfully connected to relay server: 172.31.255.88:5007

I. 2014-12-17 14:44:13.109+0200 <DnChannel-0000> Successfully connected to relay server: 172.31.255.88:5007

I. 2014-12-17 14:44:13.123+0200 <DnChannel-0001> Successfully connected to relay server: 172.31.254.88:5007

Is there any method to see what is wrong?

[tracy_barkley]

Assuming you are using the same RS.config on both servers, they should both be working at full if all the oes show channel 0 and 1.  Check the relay log on the relay 2 and see if there are any errors in there about OEs connecting.

Tracy

[former_member686053]

Now it seems ok. My Afaria RSOEs connect both relay server:

I. 2014-12-17 11:35:43.446+0200 Character encoding: windows-1252

I. 2014-12-17 11:35:43.446+0200 SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-12-17 11:35:43.446+0200

I. 2014-12-17 11:35:43.446+0200 Copyright © 2014 SAP AG or an SAP affiliate company.

I. 2014-12-17 11:35:43.446+0200 All rights reserved.

I. 2014-12-17 11:35:43.446+0200 Use of this software is governed by the Sybase License Agreement.

I. 2014-12-17 11:35:43.446+0200 Refer to http://www.sybase.com/softwarelicenses.

I. 2014-12-17 11:35:43.446+0200

I. 2014-12-17 11:35:43.452+0200 <OEHost>

I. 2014-12-17 11:35:43.452+0200 <OEHost> SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-12-17 11:35:43.452+0200 <OEHost> Machine AFARIAPNB is running Windows 2008R2 Build 7601 Service Pack 1

I. 2014-12-17 11:35:43.452+0200 <OEHost> Software built for X86_64

I. 2014-12-17 11:35:43.452+0200 <OEHost>

I. 2014-12-17 11:35:43.456+0200 <OEMaster> Successfully connected to backend server: 10.40.1.212:81

I. 2014-12-17 11:35:43.468+0200 <UpChannel-0000> Successfully connected to relay server: 172.31.255.88:5007

I. 2014-12-17 11:35:43.472+0200 <UpChannel-0001> Successfully connected to relay server: 172.31.254.88:5007

I. 2014-12-17 11:35:43.474+0200 <DnChannel-0000> Successfully connected to relay server: 172.31.255.88:5007

I. 2014-12-17 11:35:43.485+0200 <DnChannel-0001> Successfully connected to relay server: 172.31.254.88:5007

It ıs correct log. Right?

When I check on internet:

Relay #1 Overall availability Full

Relay #2 Overall availability Partial.

What does it mean ?

[tracy_barkley]

Yes that looks much better.

Full means all Backend servers are connected in.

Partial means that only some of the OEs are connected in for the back end farms.  One or more of the 2nd relays farms are not yet connected to that server.  Since you just rebuilt it, restart all the OES on both Afaria servers and see if it then reports full.

Tracy

[former_member686053]

I reinstall relay server. By installing I noticed a mistake:

I run RelayServer Service as local account. Thats why not work. Now I check rs_server.dll  and rs_client.dll. Theri overall availability is full.

Now let me ruun RSOEs again.

[former_member686053]

I do exactly same . I check working Relay and nonworking relay configuration. I believe that they are the same.

I do everything on manual step by step.

Really confusing

[former_member686053]

have you article about installing Relay ?

[tracy_barkley]

Check the binaries as well and make sure they are the same and that you haven't accidentally installed the 32 bit on the 64 bit OS.

[keith_nunn]

The documentation on installing and configuring Relay Server can be found here:

http://dcx.sap.com/index.html#sa160/en/relayserver/relayserver16.html

If you want to check the IIS log and verify you're seeing HTTP 400 status responses in the log when you test the rs_server.dll then we'll know it's a configuration issue.  From there, if you see any substatus code we can determine next steps from that.

Thanks,

Keith

[former_member686053]

Hi Tracy,

I think I mess up my config.

From Slave Afaria to Relay 1 OE not work.

E. 2014-12-15 16:30:34.191+0200 <UpChannel-0001> OEE1030: The Outbound Enabler was unable to connect to the Relay Server using 'host=172.31.254.88;port=5007;url_suffix=/ias_relay_server/server/rs_server.dll;' because of [MLC63: Unable to connect a socket. Network Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (winsock error code: 10060).]. Retrying...

Altough rsoe.config shows 172.31.255.88 ad -cr relay server.Why I get this error?

rsoe.config:

-id 4i5bc9

-f YASAR-IS

-t YASAR-IS1

-cs "host=10.40.1.212;port=81;"

-cr "host=172.31.255.88;port=5007;url_suffix=/ias_relay_server/server/rs_server.dll"

-q

-o c:\Temp\rsoe.l

rs.config:

#--------------------
# Relay server peers
#--------------------
[relay_server]
enable          = yes
host            = 172.31.255.88
http_port       = 5007
https_port      = 443
description     = Machine #1 in RS farm

[relay_server]
enable          = yes
host            = 172.31.254.88
http_port       = 5007
https_port      = 443
description     = Machine #2 in RS farm

#---------------
# Backend farms
#---------------
[backend_farm]
enable  = yes
id              = YASAR-IS
client_security = off
backend_security= off

#-----------------
# Backend servers
#-----------------
[backend_server]
enable = yes
farm    = YASAR-IS
id      = 4i5pih
token = YASAR-IS

[backend_server]
enable = yes
farm    = YASAR-IS
id      = 4i5bc9
token = YASAR-IS1

[keith_nunn]

Hi, Tevfik.

The error you're seeing is indicating a general network failure.  Try to reach the following URL from the OE machine:

http://172.31.255.88:5007/ias_relay_server/server/rs_server.dll

For me, the DNS "ars.yasar.com.tr" works but the IP you're using doesn't.  When I check nslookup I see a very different IP than the one you're using.  So the IP may be incorrect.

Thanks,

Keith Nunn
SAP Active Global Support

SAP Canada

[former_member686053]

Hi Keith,

I check the link u r  given.

Seems overal avilability is full

There is two IP address for ars.yasar.com.tr

Because theere s two Relay server. and I wanna wotk them load balancing mode.

SO DNS load balancing as round robin.

But from LAN to DMZ, i mean from afaria to relay I use IP address.

I error logs, shows slave afaria not connect to  Relay #2 (172.31.254.88) . But ın rsoe.config file. I try to connect from Slave afara ot Relay #1

What u suggest?

[former_member686053]

There is two IP I convert them to DMZ IP by NAT:

217.31.39.199  >>  convert to  >>  172.31.254.88 (Relay #2)

82.222.9.57  >>  convert to  >>  172.31.255.88 (Relay #1)

[keith_nunn]

Try the other server from the OE machine as well.  255 is the one that's initiated via the OE config but the error is coming from trying to connect to 254, which I missed before.

http://172.31.254.88:5007/ias_relay_server/server/rs_server.dll

[former_member686053]

First miss typeing on DNS:

172.131.39.199 is correct one.

I changed this.

But:

I tried this from lan and  internet

When I use:

http://172.31.254.88:5007/ias_relay_server/server/rs_server.dll

I got 404

when I use :

http://172.31.254.88:5007/

I got IIS default page

When I try from internet:

http://217.131.39.199:5007/ias_relay_server/server/rs_server.dll/

I got vad request message on browser

Even I do what explained on Instalaltion guide. I had those errors

[keith_nunn]

Hi, Tevfik.

I can't test using your internal IPs but I did verify the external one returns a "Bad Request" (HTTP 400) error.  If the IP is definitely correct and your internal NAT is good then we should be able to check the IIS log on the Relay Server that's not working and see if there are any entries related to the error we see in the browser.  So we'd hope to find a 400 status code with a substatus of something other than 0.

Aside from that, I would just double check the configuration of that machine against the one that works.  Verify the application pool and virtual directory settings as well as the "ISAPI and CGI Restrictions" module to ensure the RS dlls are allowed the same on both systems and pointing to valid files.  Also, be sure the bitness matches the app pool settings. (x64 vs. x86)

Thanks,

Keith

[former_member686053]

Hi,

Hope you have great weekend.

I tried to test my env. for enrollment. It looks  ok.

But after enrollment, if I try to reconnect from my client, something failed

I still search what is mistaken

Error occures in each connection

Session reason: Manual

Connectiong: to HTTP://ars.yasar.com.tr:5007

Connected to ars.yasar.com.tr:5007

NewServer:True

KeyHash:7sUVsomething

EncryptionAlg:4

--[sid: {0000000-0000-0000-00000000000..0}]

Communication failure with ars.yasar.com.tr:5007 Farm ID:YASAR-IS2

Failed at 15/12/2014 1:42 PM

Altough farm name is YASAR-IS, where comes from YASAR-IS2?

In client configuration i see this YASAR-IS2

how can i fix it?

[tracy_barkley]

I did have a great weekend.  Thanks for asking, and I hope yours was good too.  Check the server >configuration> relay server page for each server.  Make sure it is correct there.
Once it is, you may need to regenerate the enrollment code to populate the value.

[former_member686053]

I run rsoes manually an process.

I created new RSOE by using server >configuration> relay server

then I try to run 6 OEs.

Failed

really toooo complicated and confusing process this farm issue.

[tracy_barkley]

I know you run the OEs manually, but the enrollment policy has to pull the value from somewhere and it pulls it from the relay server page.  Don't use the relay server page to run your oes.  Just make sure the value is the correct one.  You may have to check it to edit and make the yasar-is, and then uncheck it.  Recreate the enrollment policies.

[former_member686053]

Now, link looks ok:

http://ars.yasar.com.tr:5007/ias_relay_server/client/rs_client.dll/es-afaria/aips/aipService.svc/Get...

and code is: gUgMnzV

I try to enroll my device now...

Failed

I look at relay servers log. there is no log about connection.

Where U have to look at on relays? Maybe something about IIS?

[tracy_barkley]

You should see that URL(shortened)  appear in the IIS logs on the relay server and in the IIS log of one of the enrollment servers.  You should also see the traffic in the relay log and the OE. There is some good news though, we are getting closer here.  When I go to your server I do get the help page from the enrollment server.  Can you check the IIS logs of the enrollment servers after an attempt and see if you see the getenrollmentseeddata portion showing in the log?

Tracy

[former_member686053]

Master enrollment OE config:

-id es-afaria1

-f es-afaria

-cs "host=10.40.1.212;port=80;"

-cr "host=rs2.yasar.com.tr;port=5007;url_suffix=/ias_relay_server/server/rs_server.dll" 

-q

-o c:\Temp\rsoe-enroll.log

slave afaria enrollment OE config:

-id ps-afaria2

-f ps-afaria

-cs "host=10.96.1.212;port=80;"

-cr "host=rs2.yasar.com.tr;port=5007;url_suffix=/ias_relay_server/server/rs_server.dll" 

-v 1

-q

-o c:\Temp\rsoe-ps1.log

[tracy_barkley]

Tevfik,

Yes normally your OE points to itself assuming you have the component installed there. The configuration we are now talking about is not the relay.  in the Afaria admin on the enrollment server.  Make sure the farm id there is es-afaria.

[former_member686053]

OK. let me ask one more thing..

on RSOE configs;

-cs parameter is always local host rigt?

I mean in Afaria slave enrollment RSOE config shows itself as -cs .. right?

[keith_nunn]

Nearly always.  There may be a need at some point to run the OE on a separate machine from the backend server but it's rare that it's done.  As long as the OE is running the same machine where the backend process runs for which it's being used then -cs would always be the local machine.

-Keith

[former_member686053]

Now I amlittle bit busy. But tomorrow first job is trying this. Then I hope I can close this post

thnx

[former_member686053]

Now I try:

Failed.

Log is:

E. 2014-12-11 17:17:36.853+0200 <2536.2596.-> RSE1001: Client specified an unrecognized farm name 'es-afaria1' in the URL

And Inspection of Enrollment code is :

http://ars.yasar.com.tr:5007/ias_relay_server/client/rs_client.dll/es-afaria1/aips/aipService.svc/Ge...

why ?

[keith_nunn]

Tevfik,

Your farm name is "es-afaria", not "es-afaria1".  That appears to be your backend server ID.  So the URL should have "/es-afaria/" in it.  Check your Enrollment Server configuration settings and ensure that's the value you specified in the farm ID field.  If it's set properly, check the enrollment code's long URL and see if it shows properly there.  If you have to change the farm or if the long URL is incorrect then you'll need to generate a new enrollment code. 

If you're using the Self-Service Portal be sure to update the settings for that to use the new code as well.

Thanks,

Keith Nunn
SAP Active Global Support
SAP Canada

[kirankola]

your farm name is 'es-afaria" not 'es-afaria1'

following should work:

http://ars.yasar.com.tr:5007/ias_relay_server/client/rs_client.dll/es-afaria/aips/aipService.svc/Get...

[former_member686053]

Argghh..

I uncomment that line.

Now service is ok.

and log fille attached.

Seems it is ok.

No need to change dns  to IP for relay server.

I. 2014-12-11 16:42:21.091+0200 Character encoding: windows-1252
I. 2014-12-11 16:42:21.091+0200 SAP Sybase Relay Server Version 16.0.0.1824
I. 2014-12-11 16:42:21.091+0200
I. 2014-12-11 16:42:21.091+0200 Copyright © 2014 SAP AG or an SAP affiliate company.
I. 2014-12-11 16:42:21.091+0200 All rights reserved.
I. 2014-12-11 16:42:21.091+0200 Use of this software is governed by the Sybase License Agreement.
I. 2014-12-11 16:42:21.091+0200 Refer to http://www.sybase.com/softwarelicenses.
I. 2014-12-11 16:42:21.091+0200
I. 2014-12-11 16:42:21.091+0200 Machine AFARIARELAYPNB is running Windows 2008R2 Build 7601 Service Pack 1
I. 2014-12-11 16:42:21.091+0200 Software built for X86_64
I. 2014-12-11 16:42:21.091+0200 Time zone offset from UTC in minutes: 120
I. 2014-12-11 16:42:21.091+0200 <rshost> Parsing config file 'C:\RelayServer\ias_relay_server\server\rs.config'
I. 2014-12-11 16:42:21.091+0200 <rshost> Estimated shared memory requirement per backend server: 66728
I. 2014-12-11 16:42:21.091+0200 <rshost> Reserving 3401800 bytes of shared memory per backend server with high download for a maximum of 10 servers.
I. 2014-12-11 16:42:21.091+0200 <rshost> Creating shared memory with size 77594624
I. 2014-12-11 16:42:21.091+0200 <rshost> Starting Relay Server 'ias_relay_server_host'
I. 2014-12-11 16:42:21.091+0200 <rshost> Start logging to 'C:\RelayServer\ias_relay_server\server\log.txt'
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> RSHost version: 16.0.0.1824
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [options]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   shared_mem = 10M (+64M based on initial config)
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   oe_timeout_minute = auto
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   status_refresh_sec = 15
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_pad_size = 1460
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [relay_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   host = rs2.yasar.com.tr
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   http_port = 5007
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   https_port = 443
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description = Machine #1 in RS farm
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [relay_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   host = rs3.yasar.com.tr
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   http_port = 5007
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   https_port = 443
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description = Machine #2 in RS farm
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_farm]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = YASAR-IS
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   client_security = off
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   backend_security = off
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   active_cookie = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   active_header = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forward_x509_identity = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forwarder_certificate_subject =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forwarder_certificate_issuer =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   max_client_buffer = 1M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   renew_overlapped_cookie = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   socket_level_affinity = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_farm]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = es-afaria
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   client_security =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   backend_security =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   active_cookie = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   active_header = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forward_x509_identity = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forwarder_certificate_subject =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forwarder_certificate_issuer =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   max_client_buffer = 1M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   renew_overlapped_cookie = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   socket_level_affinity = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_farm]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = ps-afaria
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description = Portal Package Farm
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   client_security =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   backend_security = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   active_cookie = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   active_header = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forward_x509_identity = no
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forwarder_certificate_subject =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   forwarder_certificate_issuer =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   max_client_buffer = 1M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   renew_overlapped_cookie = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   socket_level_affinity = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   farm = YASAR-IS
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = 4i5pih
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   mac = !
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   token = ***************
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   down_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   farm = YASAR-IS
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = 4i5bc9
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   mac = !
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   token = ***************
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   down_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   farm = es-afaria
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = es-afaria1
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   mac = !
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   token = ***************
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   down_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   farm = es-afaria
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = es-afaria2
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description =
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   mac = !
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   token = ***************
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   down_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   farm = ps-afaria
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = ps-afaria1
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description = Package Server #1
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   mac = !
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   token = ***************
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   down_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> [backend_server]
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   enable = yes
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   farm = ps-afaria
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   id = ps-afaria2
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   description = Package Server #2
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   mac = !
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   token = ***************
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   up_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   down_trip_limit = 2000M
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   verbosity = inherit
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master>   inherited verbosity = 3
I. 2014-12-11 16:42:21.107+0200 <2928.2808.rshost:master> Recorded new configuration in shared memory
I. 2014-12-11 16:42:21.108+0200 <2928.2808.rshost:master> Shared memory low water mark: 30896560
I. 2014-12-11 16:42:21.108+0200 RSR element convention -------------- Relay Server Record (RSR) element naming convention --------------
I. 2014-12-11 16:42:21.108+0200 RSR element convention b: prefix       Byte count
I. 2014-12-11 16:42:21.108+0200 RSR element convention c: prefix       General numeric counter
I. 2014-12-11 16:42:21.108+0200 RSR element convention i: prefix       ID or numeric code
I. 2014-12-11 16:42:21.108+0200 RSR element convention m: prefix       Time measured in milliseconds
I. 2014-12-11 16:42:21.108+0200 RSR element convention x: prefix       Hex number
I. 2014-12-11 16:42:21.108+0200 RSR element convention <name:string>   Variable length named string values
I. 2014-12-11 16:42:21.108+0200 RSR element convention oe              Element reported by the Outbound Enabler
I. 2014-12-11 16:42:21.108+0200 RSR element convention up              Element associated with the request (excluding the response) from the Relay Server to the backend
I. 2014-12-11 16:42:21.108+0200 RSR element convention rtp             Element associated with round-trip transport and processing of the last up and first down packet
I. 2014-12-11 16:42:21.108+0200 RSR element convention dn              Element associated with the response from the backend to the Relay Server
I. 2014-12-11 16:42:21.108+0200 RSR element convention in              Reading
I. 2014-12-11 16:42:21.108+0200 RSR element convention out             Writing
I. 2014-12-11 16:42:21.108+0200 RSR element convention A.B             B is a child component or an aspect of A
I. 2014-12-11 16:42:21.108+0200 RSR element convention pkt/packet      Refers to the packet created by the Relay Server and/or the Outbound Enabler for communication over the up/down channel
I. 2014-12-11 16:42:21.108+0200 RSR element list ------------- Description of Relay Server Record (RSR) elements --------------
I. 2014-12-11 16:42:21.108+0200 RSR element x:sfp         Session fingerprint assigned by the Relay Server as one of the affinity attributes
I. 2014-12-11 16:42:21.108+0200 RSR element i:oe.sidx     Session index assigned by the Outbound Enabler as one of the affinity attributes
I. 2014-12-11 16:42:21.108+0200 RSR element flag[0]       Affinity decision; Values: n=new, c=continue, h=homed, r=renew, x=expired
I. 2014-12-11 16:42:21.108+0200 RSR element flag[1]       Request persistence; Values: p=persistent, n=non-persistent
I. 2014-12-11 16:42:21.108+0200 RSR element flag[2]       Request transfer encoding; Values: k=chunked, l=content-length
I. 2014-12-11 16:42:21.108+0200 RSR element flag[3]       Response persistence; Values: p=persistent, n=non-persistent, u=unknown
I. 2014-12-11 16:42:21.108+0200 RSR element flag[4]       Response transfer encoding; Values: k=chunked, l=content-length, u=unknown
I. 2014-12-11 16:42:21.108+0200 RSR element b:up          Request size in bytes
I. 2014-12-11 16:42:21.108+0200 RSR element b:dn          Response size in bytes
I. 2014-12-11 16:42:21.108+0200 RSR element c:up.pkt      Number of upward request packets created by the Relay Server
I. 2014-12-11 16:42:21.109+0200 RSR element m:up          Request relaying period involving interleaving reads from the client, writes to the up channel, and request packetization performed by the Relay Server
I. 2014-12-11 16:42:21.109+0200 RSR element m:up.in       Sum of time spent waiting for request payload from the client within the request relaying period
I. 2014-12-11 16:42:21.109+0200 RSR element m:up.out      Sum of time spent writing packet to the up channel within the relaying period
I. 2014-12-11 16:42:21.109+0200 RSR element m:rtp         Round-trip processing period from the sending of the last request packet to the receiving of the first response packet between the Relay Server and the backend server, including

the backend processing time
I. 2014-12-11 16:42:21.109+0200 RSR element m:oe.rtp      Round-trip processing period from the sending of the last request packet to the receiving of the first response packet between the Outbound Enabler and the backend server,

including the backend processing time
I. 2014-12-11 16:42:21.109+0200 RSR element m:rtp.kpi     Round-trip relay processing and transport time of the last request packet and the first response packet between the Relay Server and the Outbound Enabler calculated as (m:rtp -

m:oe.rtp)
I. 2014-12-11 16:42:21.109+0200 RSR element c:dn.pkt      Number of downward response packets received from the Outbound Enabler
I. 2014-12-11 16:42:21.109+0200 RSR element m:dn          Response relaying period involving interleaved reads from the down channel and writes to the client
I. 2014-12-11 16:42:21.109+0200 RSR element m:dn.in       Sum of time spent waiting for response packets from the down channel within the response relaying period
I. 2014-12-11 16:42:21.109+0200 RSR element m:dn.out      Sum of time spent waiting for writing response payload to the client within the response relaying period
I. 2014-12-11 16:42:21.109+0200 RSR element m:oe.dn       Response receiving period observed by the Outbound Enabler. This period overlaps with time counted in m:dn.in and m:dn.out
I. 2014-12-11 16:42:21.109+0200 RSR element m:close       Elapsed time between the end of m:dn and exiting the rs_client extension
I. 2014-12-11 16:42:21.109+0200 RSR element b:dn.maxLQ    Peak memory usage of the local response packet queue of this request
I. 2014-12-11 16:42:21.109+0200 RSR element c:dn.maxSQ    Peak number of response packets in the shared memory response packet queue of this request
I. 2014-12-11 16:42:21.109+0200 RSR element i:dn.stts     HTTP response status
I. 2014-12-11 16:42:21.109+0200 RSR element i:err         Error ID
I. 2014-12-11 16:42:21.109+0200 RSR element i:warn        Warning ID
I. 2014-12-11 16:42:21.109+0200 RSR element m:appTO       Application timeout of the request
I. 2014-12-11 16:42:21.109+0200 RSR element err           Name of the error
I. 2014-12-11 16:42:21.109+0200 RSR element warn          Name of the warning
I. 2014-12-11 16:42:21.109+0200 RSR element oe.err        Name of the Outbound Enabler error
I. 2014-12-11 16:42:21.109+0200 RSR element oe.err.p0     First error parameter from the Outbound Enabler
I. 2014-12-11 16:42:21.109+0200 RSR element oe.err.p1     Second error parameter from the Outbound Enabler
I. 2014-12-11 16:42:21.109+0200 RSR element oe.err.p2     Third error parameter from the Outbound Enabler
I. 2014-12-11 16:42:21.109+0200 RSR element up.ua         User agent header of the request
I. 2014-12-11 16:42:21.109+0200 RSR element up.uq         URL query parameters
I. 2014-12-11 16:42:21.109+0200 RSR element up.AfHdr      Affinity header in request
I. 2014-12-11 16:42:21.109+0200 RSR element up.cookie     Cookie header in request
I. 2014-12-11 16:42:21.109+0200 RSR element others...     Composite request label in this format: <processId.threadId.F(BackendFarmIdx)B(BackendServerIdx)S(BackendSessionNum)R(RequestIdx)> <BackendFarmName> <BackendServerName> [SAP

passport key]
I. 2014-12-11 16:42:21.109+0200 RSR header -------------- Relay Server Record (RSR) header --------------
I. 2014-12-11 16:42:21.109+0200 RSR header  x:sfp  i:oe.sidx  flag       b:up       b:dn |  c:up.pkt       m:up    m:up.in   m:up.out |     m:rtp   m:oe.rtp  m:rtp.kpi |  c:dn.pkt       m:dn    m:dn.in   m:dn.out    m:oe.dn |   m:close |

b:dn.maxLQ c:dn.maxSQ | i:dn.stts  i:err i:warn |   m:appTO ...other-variable-length-elements...
I. 2014-12-11 16:42:23.215+0200 <2968.1768.-> Received a new OE request
I. 2014-12-11 16:42:23.215+0200 <2968.1768.-> 202 bytes OE_UPCHANNEL_CONNECT(farm=ps-afaria;backend=ps-afaria1;mac=00-50-56-81-06-7f!!;token=****;protocol=8;oeu=11e929a6078a4f81b6fe50cc5d637786)
I. 2014-12-11 16:42:23.215+0200 <2968.1768.-> Processing up channel connect request
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Authenticating up channel first time connection
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Using RSOE protocol version 8
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Engaging...
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Engaged
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> 45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=2;bidx=0;rsid=_unused_;rsu=0d973e4581324b769a8c45f0ac833f9f;dtl=2097152000;oet=1)
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Established for server 'ps-afaria1' in farm 'ps-afaria'
I. 2014-12-11 16:42:23.215+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Waiting for client request
I. 2014-12-11 16:42:23.246+0200 <3088.3128.-> Received a new OE request
I. 2014-12-11 16:42:23.246+0200 <3088.3128.-> 72 bytes OE_DNCHANNEL_CONNECT(fidx=2;bidx=0;oeu=11e929a6078a4f81b6fe50cc5d637786;rsu=0d973e4581324b769a8c45f0ac833f9f;oei=Standalone RSOE 16.0.0.1824;2 bytes puncture)
I. 2014-12-11 16:42:23.246+0200 <3088.3128.-> Processing down channel connect request
I. 2014-12-11 16:42:23.246+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> Authenticating down channel
I. 2014-12-11 16:42:23.246+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> Authenticated
I. 2014-12-11 16:42:23.248+0200 <3088.3128.-> Received a new OE request
I. 2014-12-11 16:42:23.252+0200 <3088.3128.-> 49152 bytes OE_DNCHANNEL_CONNECT(fidx=2;bidx=0;oeu=11e929a6078a4f81b6fe50cc5d637786;rsu=0d973e4581324b769a8c45f0ac833f9f;oei=Standalone RSOE 16.0.0.1824;49082 bytes puncture)
I. 2014-12-11 16:42:23.252+0200 <3088.3128.-> Processing down channel connect request
I. 2014-12-11 16:42:23.252+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> Authenticating down channel
I. 2014-12-11 16:42:23.252+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> Established for server 'ps-afaria1' in farm 'ps-afaria'
I. 2014-12-11 16:42:23.252+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> Waiting for server response with trip left: 2097102848
I. 2014-12-11 16:42:24.111+0200 <3164.3204.-> Received a new OE request
I. 2014-12-11 16:42:24.111+0200 <3164.3204.-> 197 bytes OE_UPCHANNEL_CONNECT(farm=YASAR-IS;backend=4i5bc9;mac=00-50-56-81-62-56!!;token=****;protocol=8;oeu=180d1c71866e4eef8edfc8579193a7a5)
I. 2014-12-11 16:42:24.111+0200 <3164.3204.-> Processing up channel connect request
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Authenticating up channel first time connection
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Using RSOE protocol version 8
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Engaging...
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Engaged
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> 45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=0;bidx=1;rsid=_unused_;rsu=a60c0fa3120c4aca86f134c239259afe;dtl=2097152000;oet=1)
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Established for server '4i5bc9' in farm 'YASAR-IS'
I. 2014-12-11 16:42:24.111+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Waiting for client request
I. 2014-12-11 16:42:24.111+0200 <2192.2232.-> Received a new OE request
I. 2014-12-11 16:42:24.111+0200 <2192.2232.-> 202 bytes OE_UPCHANNEL_CONNECT(farm=es-afaria;backend=es-afaria2;mac=00-50-56-81-62-56!!;token=****;protocol=8;oeu=a845a4054add42f885d65fbec86d5c61)
I. 2014-12-11 16:42:24.111+0200 <2192.2232.-> Processing up channel connect request
I. 2014-12-11 16:42:24.111+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Authenticating up channel first time connection
I. 2014-12-11 16:42:24.111+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Using RSOE protocol version 8
I. 2014-12-11 16:42:24.111+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Engaging...
I. 2014-12-11 16:42:24.112+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Engaged
I. 2014-12-11 16:42:24.112+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> 45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=1;bidx=1;rsid=_unused_;rsu=9384bfd008574483ac8c7223734024a5;dtl=2097152000;oet=1)
I. 2014-12-11 16:42:24.112+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Established for server 'es-afaria2' in farm 'es-afaria'
I. 2014-12-11 16:42:24.112+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Waiting for client request
I. 2014-12-11 16:42:24.135+0200 <2112.2144.-> Received a new OE request
I. 2014-12-11 16:42:24.135+0200 <2112.2144.-> 72 bytes OE_DNCHANNEL_CONNECT(fidx=0;bidx=1;oeu=180d1c71866e4eef8edfc8579193a7a5;rsu=a60c0fa3120c4aca86f134c239259afe;oei=Standalone RSOE 16.0.0.1824;2 bytes puncture)
I. 2014-12-11 16:42:24.135+0200 <2112.2144.-> Processing down channel connect request
I. 2014-12-11 16:42:24.135+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> Authenticating down channel
I. 2014-12-11 16:42:24.135+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> Authenticated
I. 2014-12-11 16:42:24.138+0200 <2112.2144.-> Received a new OE request
I. 2014-12-11 16:42:24.143+0200 <3044.2108.-> Received a new OE request
I. 2014-12-11 16:42:24.143+0200 <3044.2108.-> 72 bytes OE_DNCHANNEL_CONNECT(fidx=1;bidx=1;oeu=a845a4054add42f885d65fbec86d5c61;rsu=9384bfd008574483ac8c7223734024a5;oei=Standalone RSOE 16.0.0.1824;2 bytes puncture)
I. 2014-12-11 16:42:24.143+0200 <3044.2108.-> Processing down channel connect request
I. 2014-12-11 16:42:24.143+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> Authenticating down channel
I. 2014-12-11 16:42:24.143+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> Authenticated
I. 2014-12-11 16:42:24.145+0200 <3044.2108.-> Received a new OE request
I. 2014-12-11 16:42:24.150+0200 <2112.2144.-> 49152 bytes OE_DNCHANNEL_CONNECT(fidx=0;bidx=1;oeu=180d1c71866e4eef8edfc8579193a7a5;rsu=a60c0fa3120c4aca86f134c239259afe;oei=Standalone RSOE 16.0.0.1824;49082 bytes puncture)
I. 2014-12-11 16:42:24.150+0200 <2112.2144.-> Processing down channel connect request
I. 2014-12-11 16:42:24.150+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> Authenticating down channel
I. 2014-12-11 16:42:24.150+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> Established for server '4i5bc9' in farm 'YASAR-IS'
I. 2014-12-11 16:42:24.150+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> Waiting for server response with trip left: 2097102848
I. 2014-12-11 16:42:24.157+0200 <3044.2108.-> 49152 bytes OE_DNCHANNEL_CONNECT(fidx=1;bidx=1;oeu=a845a4054add42f885d65fbec86d5c61;rsu=9384bfd008574483ac8c7223734024a5;oei=Standalone RSOE 16.0.0.1824;49082 bytes puncture)
I. 2014-12-11 16:42:24.157+0200 <3044.2108.-> Processing down channel connect request
I. 2014-12-11 16:42:24.157+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> Authenticating down channel
I. 2014-12-11 16:42:24.157+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> Established for server 'es-afaria2' in farm 'es-afaria'
I. 2014-12-11 16:42:24.157+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> Waiting for server response with trip left: 2097102848
I. 2014-12-11 16:42:24.422+0200 <2088.2280.-> Received a new OE request
I. 2014-12-11 16:42:24.422+0200 <2088.2280.-> 202 bytes OE_UPCHANNEL_CONNECT(farm=ps-afaria;backend=ps-afaria2;mac=00-50-56-81-62-56!!;token=****;protocol=8;oeu=2d43e90a9425489ca066d7490e6a8409)
I. 2014-12-11 16:42:24.422+0200 <2088.2280.-> Processing up channel connect request
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Authenticating up channel first time connection
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Using RSOE protocol version 8
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Engaging...
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Engaged
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> 45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=2;bidx=1;rsid=_unused_;rsu=be239c55d12a494c852164784a05a45b;dtl=2097152000;oet=1)
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Established for server 'ps-afaria2' in farm 'ps-afaria'
I. 2014-12-11 16:42:24.422+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Waiting for client request
I. 2014-12-11 16:42:24.442+0200 <1920.1752.-> Received a new OE request
I. 2014-12-11 16:42:24.443+0200 <1920.1752.-> 72 bytes OE_DNCHANNEL_CONNECT(fidx=2;bidx=1;oeu=2d43e90a9425489ca066d7490e6a8409;rsu=be239c55d12a494c852164784a05a45b;oei=Standalone RSOE 16.0.0.1824;2 bytes puncture)
I. 2014-12-11 16:42:24.443+0200 <1920.1752.-> Processing down channel connect request
I. 2014-12-11 16:42:24.443+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> Authenticating down channel
I. 2014-12-11 16:42:24.443+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> Authenticated
I. 2014-12-11 16:42:24.445+0200 <1920.1752.-> Received a new OE request
I. 2014-12-11 16:42:24.457+0200 <1920.1752.-> 49152 bytes OE_DNCHANNEL_CONNECT(fidx=2;bidx=1;oeu=2d43e90a9425489ca066d7490e6a8409;rsu=be239c55d12a494c852164784a05a45b;oei=Standalone RSOE 16.0.0.1824;49082 bytes puncture)
I. 2014-12-11 16:42:24.457+0200 <1920.1752.-> Processing down channel connect request
I. 2014-12-11 16:42:24.457+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> Authenticating down channel
I. 2014-12-11 16:42:24.457+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> Established for server 'ps-afaria2' in farm 'ps-afaria'
I. 2014-12-11 16:42:24.457+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> Waiting for server response with trip left: 2097102848
I. 2014-12-11 16:42:26.350+0200 <952.580.-> Received a new OE request
I. 2014-12-11 16:42:26.350+0200 <952.580.-> 202 bytes OE_UPCHANNEL_CONNECT(farm=es-afaria;backend=es-afaria1;mac=00-50-56-81-06-7f!!;token=****;protocol=8;oeu=c63e8902a66f406e84e2700dfc275d05)
I. 2014-12-11 16:42:26.350+0200 <952.580.-> Processing up channel connect request
I. 2014-12-11 16:42:26.350+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Authenticating up channel first time connection
I. 2014-12-11 16:42:26.350+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Using RSOE protocol version 8
I. 2014-12-11 16:42:26.350+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Engaging...
I. 2014-12-11 16:42:26.350+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Engaged
I. 2014-12-11 16:42:26.350+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> 45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=1;bidx=0;rsid=_unused_;rsu=a18dac1070574713b9b14963c19e1088;dtl=2097152000;oet=1)
I. 2014-12-11 16:42:26.351+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Established for server 'es-afaria1' in farm 'es-afaria'
I. 2014-12-11 16:42:26.351+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Waiting for client request
I. 2014-12-11 16:42:26.351+0200 <784.564.-> Received a new OE request
I. 2014-12-11 16:42:26.351+0200 <784.564.-> 197 bytes OE_UPCHANNEL_CONNECT(farm=YASAR-IS;backend=4i5pih;mac=00-50-56-81-06-7f!!;token=****;protocol=8;oeu=75dfb870f7e6464d890be8c98c839b24)
I. 2014-12-11 16:42:26.351+0200 <784.564.-> Processing up channel connect request
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Authenticating up channel first time connection
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Using RSOE protocol version 8
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Engaging...
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Engaged
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> 45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=0;bidx=0;rsid=_unused_;rsu=232b33671e0a4a9aa6606deb5c6a255d;dtl=2097152000;oet=1)
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Established for server '4i5pih' in farm 'YASAR-IS'
I. 2014-12-11 16:42:26.351+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Waiting for client request
I. 2014-12-11 16:42:26.381+0200 <592.1464.-> Received a new OE request
I. 2014-12-11 16:42:26.381+0200 <592.1464.-> 72 bytes OE_DNCHANNEL_CONNECT(fidx=1;bidx=0;oeu=c63e8902a66f406e84e2700dfc275d05;rsu=a18dac1070574713b9b14963c19e1088;oei=Standalone RSOE 16.0.0.1824;2 bytes puncture)
I. 2014-12-11 16:42:26.381+0200 <592.1464.-> Processing down channel connect request
I. 2014-12-11 16:42:26.381+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> Authenticating down channel
I. 2014-12-11 16:42:26.381+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> Authenticated
I. 2014-12-11 16:42:26.381+0200 <2132.2308.-> Received a new OE request
I. 2014-12-11 16:42:26.381+0200 <2132.2308.-> 72 bytes OE_DNCHANNEL_CONNECT(fidx=0;bidx=0;oeu=75dfb870f7e6464d890be8c98c839b24;rsu=232b33671e0a4a9aa6606deb5c6a255d;oei=Standalone RSOE 16.0.0.1824;2 bytes puncture)
I. 2014-12-11 16:42:26.381+0200 <2132.2308.-> Processing down channel connect request
I. 2014-12-11 16:42:26.382+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> Authenticating down channel
I. 2014-12-11 16:42:26.382+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> Authenticated
I. 2014-12-11 16:42:26.383+0200 <592.1464.-> Received a new OE request
I. 2014-12-11 16:42:26.383+0200 <2132.2308.-> Received a new OE request
I. 2014-12-11 16:42:26.387+0200 <592.1464.-> 49152 bytes OE_DNCHANNEL_CONNECT(fidx=1;bidx=0;oeu=c63e8902a66f406e84e2700dfc275d05;rsu=a18dac1070574713b9b14963c19e1088;oei=Standalone RSOE 16.0.0.1824;49082 bytes puncture)
I. 2014-12-11 16:42:26.387+0200 <592.1464.-> Processing down channel connect request
I. 2014-12-11 16:42:26.387+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> Authenticating down channel
I. 2014-12-11 16:42:26.387+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> Established for server 'es-afaria1' in farm 'es-afaria'
I. 2014-12-11 16:42:26.387+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> Waiting for server response with trip left: 2097102848
I. 2014-12-11 16:42:26.387+0200 <2132.2308.-> 49152 bytes OE_DNCHANNEL_CONNECT(fidx=0;bidx=0;oeu=75dfb870f7e6464d890be8c98c839b24;rsu=232b33671e0a4a9aa6606deb5c6a255d;oei=Standalone RSOE 16.0.0.1824;49082 bytes puncture)
I. 2014-12-11 16:42:26.387+0200 <2132.2308.-> Processing down channel connect request
I. 2014-12-11 16:42:26.387+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> Authenticating down channel
I. 2014-12-11 16:42:26.387+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> Established for server '4i5pih' in farm 'YASAR-IS'
I. 2014-12-11 16:42:26.387+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> Waiting for server response with trip left: 2097102848
I. 2014-12-11 16:42:53.633+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Sending a liveness packet
I. 2014-12-11 16:42:53.633+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> 4 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:53.633+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> 1460 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:53.633+0200 <2968.1768.F2B0Up> <ps-afaria> <ps-afaria1> Waiting for client request
I. 2014-12-11 16:42:54.009+0200 <2928.2808.rshost:master> RS cpu: 0.00  Idle cpu: 98.96
I. 2014-12-11 16:42:54.054+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> 4 bytes OE_DNCHANNEL_NOOP()
I. 2014-12-11 16:42:54.054+0200 <3088.3128.F2B0Dn> <ps-afaria> <ps-afaria1> Waiting for server response with trip left: 2097102844
I. 2014-12-11 16:42:54.553+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Sending a liveness packet
I. 2014-12-11 16:42:54.553+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> 4 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:54.553+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> 1460 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:54.553+0200 <3164.3204.F0B1Up> <YASAR-IS> <4i5bc9> Waiting for client request
I. 2014-12-11 16:42:54.553+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Sending a liveness packet
I. 2014-12-11 16:42:54.553+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> 4 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:54.553+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> 1460 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:54.553+0200 <2192.2232.F1B1Up> <es-afaria> <es-afaria2> Waiting for client request
I. 2014-12-11 16:42:54.833+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Sending a liveness packet
I. 2014-12-11 16:42:54.834+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> 4 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:54.834+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> 1460 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:54.834+0200 <2088.2280.F2B1Up> <ps-afaria> <ps-afaria2> Waiting for client request
I. 2014-12-11 16:42:54.964+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> 4 bytes OE_DNCHANNEL_NOOP()
I. 2014-12-11 16:42:54.964+0200 <3044.2108.F1B1Dn> <es-afaria> <es-afaria2> Waiting for server response with trip left: 2097102844
I. 2014-12-11 16:42:54.964+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> 4 bytes OE_DNCHANNEL_NOOP()
I. 2014-12-11 16:42:54.964+0200 <2112.2144.F0B1Dn> <YASAR-IS> <4i5bc9> Waiting for server response with trip left: 2097102844
I. 2014-12-11 16:42:55.260+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> 4 bytes OE_DNCHANNEL_NOOP()
I. 2014-12-11 16:42:55.260+0200 <1920.1752.F2B1Dn> <ps-afaria> <ps-afaria2> Waiting for server response with trip left: 2097102844
I. 2014-12-11 16:42:56.768+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Sending a liveness packet
I. 2014-12-11 16:42:56.768+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> 4 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:56.768+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> 1460 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:56.768+0200 <952.580.F1B0Up> <es-afaria> <es-afaria1> Waiting for client request
I. 2014-12-11 16:42:56.768+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Sending a liveness packet
I. 2014-12-11 16:42:56.768+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> 4 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:56.768+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> 1460 bytes RS_UPCHANNEL_NOOP()
I. 2014-12-11 16:42:56.768+0200 <784.564.F0B0Up> <YASAR-IS> <4i5pih> Waiting for client request
I. 2014-12-11 16:42:57.190+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> 4 bytes OE_DNCHANNEL_NOOP()
I. 2014-12-11 16:42:57.190+0200 <2132.2308.F0B0Dn> <YASAR-IS> <4i5pih> Waiting for server response with trip left: 2097102844
I. 2014-12-11 16:42:57.190+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> 4 bytes OE_DNCHANNEL_NOOP()
I. 2014-12-11 16:42:57.190+0200 <592.1464.F1B0Dn> <es-afaria> <es-afaria1> Waiting for server response with trip lef

[tracy_barkley]

Tevfik,

That looks substantially better.  Have you tried an enrollment yet?  I see both enrollment servers OEs connected there.

[former_member686053]

Now I noticed and remember that, I comment Relay #2 in config file. Bec whenI write in config file , relay service not working. shown below:

And Error:

And rs log file:

I. 2014-12-11 16:11:01.179+0200 Character encoding: windows-1252

I. 2014-12-11 16:11:01.179+0200 SAP Sybase Relay Server Version 16.0.0.1824

I. 2014-12-11 16:11:01.179+0200

I. 2014-12-11 16:11:01.179+0200 Copyright © 2014 SAP AG or an SAP affiliate company.

I. 2014-12-11 16:11:01.179+0200 All rights reserved.

I. 2014-12-11 16:11:01.179+0200 Use of this software is governed by the Sybase License Agreement.

I. 2014-12-11 16:11:01.179+0200 Refer to http://www.sybase.com/softwarelicenses.

I. 2014-12-11 16:11:01.179+0200

I. 2014-12-11 16:11:01.179+0200 Machine AFARIARELAYPNB is running Windows 2008R2 Build 7601 Service Pack 1

I. 2014-12-11 16:11:01.179+0200 Software built for X86_64

I. 2014-12-11 16:11:01.179+0200 Time zone offset from UTC in minutes: 120

I. 2014-12-11 16:11:01.179+0200 <rshost> Parsing config file 'C:\RelayServer\ias_relay_server\server\rs.config'

E. 2014-12-11 16:11:01.179+0200 <rshost> RSF11044: Invalid property name at line 19 in configuration file 'C:\RelayServer\ias_relay_server\server\rs.config'

I. 2014-12-11 16:11:01.180+0200 <rshost> Finished

When I look line19  :

enable          = yes

[kirankola]

Can you try following:

- Uncomment #[relay_server]

- Also rs2.yasar.com.tr and rs3.yasar.com.tr are relay server hosts? Can you try with the IP address

[former_member686053]

Can u explain a litle bit more??

[tracy_barkley]

I can try.  In the rs config you should have two relay servers defined.  Relay 1 should be first and relay 2 is second.  Each has its settings defined.  The backend settings the OE will reach out to.  When an OE connects in, it pulls this peer list.  It then disconnects and reconnects to each relay defined in the peer list.  You should see this occurring in the OE logs.

Something like this.

#---------------------------------

#relay server peers

#---------------------------------

[relay-server]

enable=yes

host=10.10.10.100

http_port=80

https_port=443

Description relay 1

[relay-server]

enable=yes

host=10.10.10.101

http_port=80

https_port=443

Description relay 2

[kirankola]

Like Tracy mentioned:

Here is the one more example:

Some Notes:

- Typically you will be using same rs.config file in both the relay servers

- Try and monitor the RSOE traffic in the following scenario:

From Afaria, point to one of the relay server and failover should be automatic (because of the available peer list)

Regards,

Kiran

[former_member686053]

Hi tracy,

I dont think like that, because, this toplogy worked when there is only one relay server. Now I have two relay server (rs2 and rs3) and there is a dns name (ars.yasar.com.tr) which for load balancing.

here is nslookup output:

Name: ars.yasar.com.tr
Address: 217.31.39.199  #--> rs3 real IP (It is NAT in FRW)
Name: ars.yasar.com.tr
Address: 82.222.9.57   #--> rs2 real IP (It is NAT in FRW)

When request comes from client to ars.yasar.com.tr and then Relay 1 (rs2)  I think there will be no problem. Bec. all rsoes from afaria master and relay goes to Relay 1.

But if request reaches Relay 2 no answer from relay. bec. there is no rsoe.

And here is RSOEs:

Master:

Slave:

Is there anything wrong in this topology?

[tracy_barkley]

Nothing is wrong with the topology.  In the OE you should see a connect to the first relay server, which you do.  You should then see it pull the peer list and disconnect and reconnect back to RS1 and RS2.  In the RS.config on the relay server, you should have both relays defined in the peer list and this file should be identical on both servers. 

[former_member686053]

Android only.

Let me search logs first.

[tracy_barkley]

Also http://ars.yasar.com.tr:5007/ias_relay_server/client/rs_client.dll/es-afaria1/ gives a 404 from here.  You may have a mismatch in capitalization.  I don't think the es-afaria1 OE is connecting to the server

[former_member686053]

Hi,

As you told ;

I create 3 RSOE's (afaria, enrollment and package server) for each Master and Afaria Servers. And connnected from Afarias to Relay 1 Server.

I set an DNS name to laod balancing (ars.yasar.com.tr)

And create an enrollment (grduWFe) and inspect that it looks ok ( ttp://ars.yasar.com.tr:5007/ias_relay_server/client/rs_client.dll/es-afaria1/aips/aipService.svc/Get...

But try to enroll my devices ,I get "enrollment failed)

Any trick about that?

[tracy_barkley]

Tevfik,

At this point you need to see where the point of failure is.  Does the request from the client show up in the iis log of the relay server and the relay log?  Does it show up in one of the OE logs for the enrollment server on the Afaria machines?  If it shows up there, does it show up in the IIS logs for the enrollment server?  Are there errors in any of these logs?  Does anything show up in the server message log?  Once you know where the attempt to enroll stops, it will be easier to proceed.  Is this IOS or android?

[kirankola]

Keith answered your question.

The server URL can map directly to a Relay Server or it can map to a load balancer. If the server URL maps to a load balancer, the load balancer forwards the request to one of the Relay Servers running in the farm. The Relay Server that receives the request from the Outbound Enabler returns the connection information for all Relay Servers in the farm.

Also check this:

http://dcx.sybase.com/index.html#sa160/en/relayserver/ml-relayserver-s-4622472.html

Regards,

Kiran

[keith_nunn]

You can create a cluster with multiple Relay Servers.  You would need to define all RS peers, backend farms and backend servers in the Relay Server's configuration file and then copy that config file to all Relay Server's in the farm.  In the OE config you would specify a single address, either one RS or a load-balanced address. 

When the OE starts up and connects to the address specified in the -cr switch, the RS it reaches will deliver the peer list from its configuration back to the OE.  The OE then disconnects and initiates connections to every RS peer that was provided (including a connection back to the initial RS, generally) to service connections for its farm that come into any RS in the cluster.

Let me know if any of that isn't clear or you need further details.

Thanks,

Keith Nunn
SAP Active Global Support
SAP Canada

[former_member686053]

Or,

Can I put 2 Relay Server (after -cr parameter) into one  RSOE?

[tracy_barkley]

I believe if you put two parameters into one OE the second is ignored in newer versions of the Relay.