Relay Affiliation does not work well

(imported topic written by ShigeT)

Hi all,

Please tell me about “Relay Affiliation”.

TEM version is 8.2.1175.

I have the following settings:

  • TEM Server : not affiliation group

  • TEM Relay1 : affiliation group ( name is “relaygroup”)

  • TEM Relay2 : affiliation group ( name is “relaygroup”)

  • TEM Relay3 : affiliation group ( name is “relaygroup”)

  • TEM Relay4 : affiliation group ( name is “relaygroup”)

  • TEM Client1 : seeklist is “relaygroup”

  • TEM Client2 : seeklist is “relaygroup”

===

I think TEM Client should select TEM Relay.

However, TEM Client selects TEM Server after selecting TEM Relay.

======================================

Fri, 01 Feb 2013 13:03:09 +0900 Client detected possible network connection event.

Fri, 01 Feb 2013 13:03:09 +0900 DebugMessage Beginning Relay Select

Fri, 01 Feb 2013 13:03:09 +0900 Relay Selection: Setting control server

Fri, 01 Feb 2013 13:03:09 +0900 Relay Selection: For agent only.

Fri, 01 Feb 2013 13:03:09 +0900 Relay Selection: Initializing automatic selection with affiliations relaygroup

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: Seeking ‘relaygroup’ affiliated relay.

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: host: relay1. priority:0 weight:100

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: host: relay2. priority:0 weight:100

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: host: relay3. priority:0 weight:100

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: host: relay4. priority:0 weight:100

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.101 at TTL 1

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.102 at TTL 1

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.103 at TTL 1

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.104 at TTL 1

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.101 at TTL 2

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.102 at TTL 2

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.103 at TTL 2

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.104 at TTL 2

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.101 at TTL 3

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.102 at TTL 3

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.103 at TTL 3

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.104 at TTL 3

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.101 at TTL 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.102 at TTL 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.103 at TTL 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.104 at TTL 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.101 at TTL 5

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.102 at TTL 5

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.103 at TTL 5

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.104 at TTL 5

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Received echo reply from 10.1.1.101 at distance 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Received echo reply from 10.1.1.102 at distance 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Received echo reply from 10.1.1.103 at distance 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Received echo reply from 10.1.1.104 at distance 4

Fri, 01 Feb 2013 13:03:11 +0900 VerboseMessage RelaySelectLog: Selecting 10.1.1.101:52311 at 0-4

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: Attempt to select relay1:52311

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: Attempting to register via with parent. http://relay1:52311/cgi-bin/bfenterprise/clientregister.exe

Fri, 01 Feb 2013 13:03:11 +0900 Relay Selection: Attempt to register with http://relay1:52311/cgi-bin/bfenterprise/clientregister.exe

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage RegisterOnce: Attempting to register with ‘http://relay1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=8.2.1175.0&Body=13775178&SequenceNumber=615&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&MaxHops=4&Root=http://temserver%3A52311&AdapterInfo=10-0b-a9-c0-e7-f8_10.1.1.0%2F22_10.1.1.212_0&AdapterIpv6=10-0b-a9-c0-e7-f8^fe80%3A%3A81d3%3A2a77%3Aac90%3Ab71f%2F64_0

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage RegisterOnce: None authentication used.

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage Unrestricted mode

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage Not in grace period

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage Configuring listener without wake-on-lan

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage Registered with url ‘http://relay1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=8.2.1175.0&Body=13775178&SequenceNumber=615&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&MaxHops=4&Root=http://temserver%3A52311&AdapterInfo=10-0b-a9-c0-e7-f8_10.1.1.0%2F22_10.1.1.212_0&AdapterIpv6=10-0b-a9-c0-e7-f8^fe80%3A%3A81d3%3A2a77%3Aac90%3Ab71f%2F64_0

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage Registration Server version 8.2.1175.0 , Relay version 8.2.1175.0

Fri, 01 Feb 2013 13:03:13 +0900 Relay Selection: Setting control server relay1:52311

Fri, 01 Feb 2013 13:03:13 +0900 Relay Selection: Selection Complete

Fri, 01 Feb 2013 13:03:13 +0900 Relay Selection: Finished (selected nearby relay).

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage EvaluationManager::SetProcessingAction (on)

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage ShutdownListener

Fri, 01 Feb 2013 13:03:13 +0900 DebugMessage SetupListener success: IPV4/6



Fri, 01 Feb 2013 15:41:51 +0900 Client detected possible network connection event.


Fri, 01 Feb 2013 15:41:51 +0900 DebugMessage Beginning Relay Select


Fri, 01 Feb 2013 15:41:51 +0900 Relay Selection: Setting control server


Fri, 01 Feb 2013 15:41:51 +0900 Relay Selection: For agent only.


Fri, 01 Feb 2013 15:41:51 +0900 Relay Selection: Initializing automatic selection with affiliations relaygroup


Fri, 01 Feb 2013 15:41:52 +0900 Relay Selection: Going direct.


Fri, 01 Feb 2013 15:41:52 +0900 Relay Selection: Attempting to register via with parent. http://temserver:52311/cgi-bin/bfenterprise/clientregister.exe


Fri, 01 Feb 2013 15:41:52 +0900 Relay Selection: Attempt to register with http://temserver:52311/cgi-bin/bfenterprise/clientregister.exe


Fri, 01 Feb 2013 15:41:53 +0900 DebugMessage RegisterOnce: Attempting to register with 'http://temserver:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=8.2.1175.0&Body=13775178&SequenceNumber=616&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&Root=http://temserver%3a52311&AdapterInfo=10-0b-a9-c0-e7-f8_10.1.1.0%2f22_10.1.1.212_0&AdapterIpv6=10-0b-a9-c0-e7-f8%5efe80%3a%3a81d3%3a2a77%3aac90%3ab71f%2f64_0'


Fri, 01 Feb 2013 15:41:54 +0900 DebugMessage RegisterOnce: None authentication used.


Fri, 01 Feb 2013 15:41:54 +0900 DebugMessage Unrestricted mode


Fri, 01 Feb 2013 15:41:54 +0900 DebugMessage Not in grace period


Fri, 01 Feb 2013 15:41:54 +0900 DebugMessage Configuring listener without wake-on-lan


Fri, 01 Feb 2013 15:41:54 +0900 DebugMessage Registered with url 'http://temserver:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=8.2.1175.0&Body=13775178&SequenceNumber=616&MinRelayVersion=6.0.0.0&CanHandleMVPings=1&Root=http://temserver%3a52311&AdapterInfo=10-0b-a9-c0-e7-f8_10.1.1.0%2f22_10.1.1.212_0&AdapterIpv6=10-0b-a9-c0-e7-f8%5efe80%3a%3a81d3%3a2a77%3aac90%3ab71f%2f64_0'


Fri, 01 Feb 2013 15:41:54 +0900 DebugMessage Registration Server version 8.2.1175.0 , Relay version 8.2.1175.0


Fri, 01 Feb 2013 15:41:54 +0900 Relay Selection: Setting control server temserver:52311


Fri, 01 Feb 2013 15:41:54 +0900 Relay Selection: Selection Complete


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.1 at TTL 1


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.1 at TTL 2


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.1 at TTL 3


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.1 at TTL 4


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Pinging 10.1.1.1 at TTL 5


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Received echo reply from 10.1.1.1 at distance 4


Fri, 01 Feb 2013 15:41:55 +0900 VerboseMessage RelaySelectLog: Selecting 10.1.1.1:52311 at 0-4


Fri, 01 Feb 2013 15:41:55 +0900 Relay Selection: Finished (selected root).


Fri, 01 Feb 2013 15:41:55 +0900 DebugMessage EvaluationManager::SetProcessingAction (on)


Fri, 01 Feb 2013 15:41:55 +0900 DebugMessage ShutdownListener


Fri, 01 Feb 2013 15:41:55 +0900 DebugMessage SetupListener success: IPV4/6


=========================================


TEM Client selected TEM Relay(relay1) at 13:03.


But TEM Client selected TEM Server(temserver) at 15:41.


Can someone help me?


Thanks,


Shige

(imported comment written by SystemAdmin)

Did you restart your relays after setting their affiliation?

(imported comment written by ShigeT)

Hi Alan,

Did you restart your relays after setting their affiliation?

Yes.

I checked the client log of the past.

There were times when TEM Client selects the TEM relay or when TEM Client selects the TEM server.

Setting of TEM Server

_BESRelay_Register_Affiliation_AdvertisementList : *

Setting of all TEM Relay

_BESRelay_Register_Affiliation_AdvertisementList : relaygroup;*

Setting of all TEM Client

_BESClient_Register_Affiliation_SeekList : relaygroup

I doubt the possibility of the following known bug of TEM.

“IV22432: AUTOMATIC RELAY SELECTION PROCESS FAILING IN VERSION 8.2.1175 OF THE TEM AGENT.”

(http://www-01.ibm.com/support/docview.wss?uid=swg1IV22432)

But I couldn’t find the following error message.

"Relay Selection: error in DoSelectionLoop around SelectHost

(Socket Error: Windows Error 00002726: An invalid argument was

supplied.)

I understand as follows:

  • Step 1

TEM Client try to select the TEM Relay of Affiliation group.

  • Step 2

If TEM Client can’t select the TEM Relay, then TEM Client try to select the other TEM Relay.

  • Step 3

If TEM Client can’t select the “All” TEM Relay, then TEM Client try to select the TEM Server.

===

Thanks,

Shige

(imported comment written by SystemAdmin)

If you haven’t done so already, you will want open a PMR support case with the L2 Support team. You can do this via the Service Request tool (https://www-946.ibm.com/support/servicerequest) or by calling the support line for the region of the world you are in (http://www.ibm.com/planetwide/region.html)

(imported comment written by ShigeT)

Hi Adam

I have already consulted PMR.

Fri, 01 Feb 2013 13:00:15

0900 DebugMessage Beginning Relay Select

Fri, 01 Feb 2013 13:00:15

0900 Relay Selection: Setting control server

Fri, 01 Feb 2013 13:00:15

0900 Relay Selection: For agent only.

Fri, 01 Feb 2013 13:00:15

0900 Relay Selection: Initializing automatic selection with affiliations relaygroup

Fri, 01 Feb 2013 13:00:17

0900 Relay Selection: Going direct.

I think that “Going direct” means that TEM Client selects TEM Server.

TEM Server does not belong to the Relay group (relaygroup).

I don’t think that TEM Client select TEM Server even in this case, not TEM relay.

I wait for the answer of PMR.

Thanks,

Shige

(imported comment written by SystemAdmin)

Hi Shige,

Please email your PMR number to me (amcdonal@us.ibm.com) and I will follow up on it for you.

Thanks,

Adam

(imported comment written by ShigeT)

Hi Adam,

Please email your PMR number to me (amcdonal@us.ibm.com) and I will follow up on it for you

I sent a mail to you.

Thanks for your support!

Best Regards,

Shige