Something Wrong in Master Slave Afaria Design

[former_member686053]

Hi, I try to set up and master-slave afaria environment.

I have two Afaria Server in two different location

AfariaPNB (Master) : 10.40.1.212

AfariaKMP (Slave) : 10.96.1.212

And there are two Relay server on same location's DMZ.

AfariaRelayPNB (In front of Master Afaria) : rs2.yasar.com.tr (172.31.255.88)

AfariaRelayKMP (In front of Slave Afaria) : rs3.yasar.com.tr (172.31.254.88)

I can run RSOEs from master afaria to its First server. But after 20 sec later connection drops.

I can run RSOE from slave afaria to Firt Relay Server. But after 20 sec later conenction drops

here is Configurations:

Both Relay Server have same config:

rs.config:

#-------------------------------------
# Relay server options
#-------------------------------------
[options]
#start = no
verbosity = 3

#--------------------
# Relay server peers
#--------------------
[relay_server]
enable          = yes
host            = rs2.yasar.com.tr
http_port       = 5007
https_port      = 443
description     = Machine #1 in RS farm

[relay_server]
enable          = yes
host            = rs3.yasar.com.tr
http_port       = 5007
https_port      = 443
description     = Machine #2 in RS farm

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

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

[backend_server]
enable = yes
farm    = YASAR-IS2
id      = 4i5bc9
token = YASAR-IS22

#---------------
# Backend farms
#---------------
[backend_farm]
enable  = yes
id              = es-afaria2
active_cookie = no
backend_security= no
description = Enrollment Farm

[backend_server]
enable  = yes
farm     = es-afaria2
id       = es-afaria2
description = Enrollment Server #1

[backend_server]
enable  = yes
farm     = es-afaria2
id       = es-afaria22
description = Enrollment Server #2
#---------------
# Backend farms
#---------------
[backend_farm]
enable  = yes
id              = ps-afaria2
active_cookie = no
backend_security= no
description = Portal Package Farm

[backend_server]
enable  = yes
farm     = ps-afaria2
id       = ps-afaria2
description = Package Server #1

[backend_server]
enable  = yes
farm     = ps-afaria2
id       = ps-afaria22
description = Package Server #2

Master server rsoe.config:

-id 4i5pih

-f YASAR-IS2

-t YASAR-IS2

-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.log

Slave Server rsoe.config:

-id 4i5bc9

-f YASAR-IS2

-t YASAR-IS22

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

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

-q

-v 5

-o c:\Temp\rsoe.log

And here is log files:

Master Afaria RSOE log:

I. 2014-11-27 14:23:16.822+0200 Character encoding: windows-1252

I. 2014-11-27 14:23:16.822+0200 SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-11-27 14:23:16.822+0200

I. 2014-11-27 14:23:16.822+0200 Copyright © 2014 SAP AG or an SAP affiliate company.

I. 2014-11-27 14:23:16.822+0200 All rights reserved.

I. 2014-11-27 14:23:16.822+0200 Use of this software is governed by the Sybase License Agreement.

I. 2014-11-27 14:23:16.822+0200 Refer to http://www.sybase.com/softwarelicenses.

I. 2014-11-27 14:23:16.822+0200

I. 2014-11-27 14:23:16.824+0200 <OEHost>

I. 2014-11-27 14:23:16.824+0200 <OEHost> SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-11-27 14:23:16.824+0200 <OEHost> Machine AFARIAPNB is running Windows 2008R2 Build 7601 Service Pack 1

I. 2014-11-27 14:23:16.824+0200 <OEHost> Software built for X86_64

I. 2014-11-27 14:23:16.824+0200 <OEHost>

I. 2014-11-27 14:23:16.827+0200 <OEMaster> Successfully connected to backend server: 10.40.1.212:81

I. 2014-11-27 14:23:16.859+0200 <UpChannel-0000> Successfully connected to relay server: rs2.yasar.com.tr:5007

I. 2014-11-27 14:23:16.866+0200 <DnChannel-0000> Successfully connected to relay server: rs2.yasar.com.tr:5007

I. 2014-11-28 10:30:42.765+0200 Waiting on OEMaster thread to terminate..

I. 2014-11-28 10:30:44.170+0200 OEMaster thread terminated.

I. 2014-11-28 10:41:14.612+0200 Character encoding: windows-1252

I. 2014-11-28 10:41:14.612+0200 SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-11-28 10:41:14.612+0200

I. 2014-11-28 10:41:14.612+0200 Copyright © 2014 SAP AG or an SAP affiliate company.

I. 2014-11-28 10:41:14.612+0200 All rights reserved.

I. 2014-11-28 10:41:14.612+0200 Use of this software is governed by the Sybase License Agreement.

I. 2014-11-28 10:41:14.612+0200 Refer to http://www.sybase.com/softwarelicenses.

I. 2014-11-28 10:41:14.612+0200

I. 2014-11-28 10:41:14.614+0200 <OEHost>

I. 2014-11-28 10:41:14.614+0200 <OEHost> SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-11-28 10:41:14.614+0200 <OEHost> Machine AFARIAPNB is running Windows 2008R2 Build 7601 Service Pack 1

I. 2014-11-28 10:41:14.614+0200 <OEHost> Software built for X86_64

I. 2014-11-28 10:41:14.614+0200 <OEHost>

I. 2014-11-28 10:41:14.618+0200 <OEMaster> Successfully connected to backend server: 10.40.1.212:81

I. 2014-11-28 10:41:14.650+0200 <UpChannel-0000> Successfully connected to relay server: rs2.yasar.com.tr:5007

I. 2014-11-28 10:41:14.656+0200 <DnChannel-0000> Successfully connected to relay server: rs2.yasar.com.tr:5007

E. 2014-11-28 10:41:35.672+0200 <UpChannel-0001> OEE1030: The Outbound Enabler was unable to connect to the Relay Server using 'host=rs3.yasar.com.tr;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...

Slave Afaria RSOE log:

I. 2014-11-28 11:18:15.919+0200 Character encoding: windows-1252

I. 2014-11-28 11:18:15.919+0200 SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-11-28 11:18:15.919+0200

I. 2014-11-28 11:18:15.919+0200 Copyright © 2014 SAP AG or an SAP affiliate company.

I. 2014-11-28 11:18:15.919+0200 All rights reserved.

I. 2014-11-28 11:18:15.919+0200 Use of this software is governed by the Sybase License Agreement.

I. 2014-11-28 11:18:15.919+0200 Refer to http://www.sybase.com/softwarelicenses.

I. 2014-11-28 11:18:15.919+0200

I. 2014-11-28 11:18:15.921+0200 <OEHost>

I. 2014-11-28 11:18:15.921+0200 <OEHost> SAP Sybase Outbound Enabler Version 16.0.0.1824

I. 2014-11-28 11:18:15.922+0200 <OEHost> Machine AFARIAKMP is running Windows 2008R2 Build 7601 Service Pack 1

I. 2014-11-28 11:18:15.922+0200 <OEHost> Software built for X86_64

I. 2014-11-28 11:18:15.922+0200 <OEHost>

I. 2014-11-28 11:18:15.931+0200 <OEMaster> Successfully connected to backend server: 10.96.1.212:81

I. 2014-11-28 11:18:15.955+0200 <UpChannel-0000> Successfully connected to relay server: rs2.yasar.com.tr:5007

I. 2014-11-28 11:18:15.969+0200 <DnChannel-0000> Successfully connected to relay server: rs2.yasar.com.tr:5007

E. 2014-11-28 11:18:36.976+0200 <UpChannel-0001> OEE1030: The Outbound Enabler was unable to connect to the Relay Server using 'host=rs3.yasar.com.tr;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...

What I did, My all RSOE's from master or Slave try to connect toFirs relay server. Is it correct?

Hre is Device communication Configuration page:

Master Afaria Server Devicecommunication page:

Slave Afaria Server Devicecommunication page:

What is wrong in my configuration?

[Former Member]

Also,

Just FYI

http://wiki.scn.sap.com/wiki/display/SAPMOB/Explanation+of+Relay+Server+and+Relay+Server+Outbound+En...

Zoe

[former_member686053]

THnx Tracy,

Now there is 6 RSOE connected to Relay 1

3 from Master 3 from Slave.

What I have to do if Master afaria goes down

or Relay 1 Goes down?

[tracy_barkley]

As long as your OEs have connected to both relays, having relay 1 go down isn't a problem as relay 2 will work.  One caveat for this is you need to have the address the clients are connected to load balanced between the two relays.

The same goes for the master and slave.  It depends on client type and certain functions are dependent on the master, but as long as both servers connect to both relays, if the master is down the slave will still answer.  This does mean you should have redundant enrollment servers and package servers.

Tracy

[former_member686053]

Really thanks,

There is only two issue Ihave to ask as final:

1.)You said " One caveat for this is you need to have the address the clients are connected to load balanced between the two relays."

What about DNS? can resolve my problem instead of using load balancer?

2.) SQL replication I Istall SQL Anywhere on both Afaria server. POssible to replicate SQL data from master to slave afaria. In master afaria goes down case, I show database on slave afaria. Possible?

Regard

[tracy_barkley]

Tevfik,

1) DNS is fine as well. I just recommend using some sort of solution than cant/will hit either relay for the best performance.

2) Not really.  The slave would not be looking for the dB locally.  For Disaster Recovery, I recommend you check out this document

http://scn.sap.com/docs/DOC-59494

Tracy

[former_member686053]

Now I start to go step by step.

First ,  I change my rs.config file to conenct only server communications.

Both afaria servers can connect to "first" realy server.

I need to know where I connect enrollment RSOEs to wich server?

Master Afaria RSOEs ( enrollment and package server rsoe) should connect only "First Relay" server? or both Relay Servers?

Likewise, Slave afaria RSOEs should conenct only "Second Relay" serveri or master server or both?

[tracy_barkley]

Both Afaria servers connect to relay 1.  Once relay 1 connect to relay 1, that relay tells them there are peer relays and to disconnect and reconnect to relay 1 and 2.  This happens automatically.  Currently from your log, it looks like they aren't succeeding on the connection to relay 2.   Since you are using the IP in the RSOE, make sure that the two Afaria servers can actually reach rs3.yasar.com.tr on post 5007. You may want to try and put the IPs in the rs.config instead of the relay server DNS names.

Tracy

[tracy_barkley]

Yes, they both should connect to the first relay.  What version of relay server is this?  Is it windows or Linux?  Is the IIS/Apache listening on 5007 in netstat when the relay server service is started? There isn't a firewall blocking 500 between these two servers is there?

[former_member686053]

Hi Tracy,

SAP Sybase Relay Server Version 16.0.0.1824

I Use Win 2008 R2 and IIS 7.5

Both Relay listen port 5007

and port 5007 is open for severs in firewall rules.

But first, connection occurs, then after 20 sec later drops.

[former_member686053]

Hi again,

I see an article:

http://frontline.sybase.com/support/resolutionDetails.aspx?KBID=4575

In there, both Afaria andMaster server connect to both Relay server. By using this(Applied on Afaria6):

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

        Example Syntax for the Afaria Slave 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 uz67 -t 2345678901 -v 3

I do it same config by changing my parameters and hostnames:

-cs host=localhost;port=81 -cr "host=rs2.yasar.com.tr;port=5007;url_suffix=/ias_relay_server/server/rs_server.dll;host=rs3.yasar.com.tr;port=5007;url_suffix=/IAS_relay_server/server/rs_server.dll"

-f YASAR-IS -id 4i5pih -t YASAR-IS -v 3 -q -o c:\Temp\rsoe.log

But I got this:

<OEHost> OEE1030: The Outbound Enabler was unable to connect to the Relay Server using 'host=rs2.yasar.com.tr;port=5007;url_suffix=/ias_relay_server/server/rs_server.dll;host=rs3.yasar.com.tr;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...

Something change from Afaria 6 to Afaria7?

Because this config not work on my env.

http://frontline.sybase.com/support/resolutionDetails.aspx?KBID=4575http://frontline.sybase.com/support/resolutionDetails.aspx?KBID=4575http://frontline.sybase.com/support/resolutionDetails.aspx?KBID=4575http://frontline.sybase.com/support/resolutionDetails.aspx?KBID=4575

[tracy_barkley]

That KBA is years back, and versions of relay back. You should connect the OE both to the primary relay and let them set up the peer relationship.

[former_member686053]

Ok then, Iwi,ll test it.

Regards