Truesight Orchestration peer on multi-homed server fails to connect to grid

Knowledge Article

Article Number

000364697

Old Article Number

000089530

Article Type

Solutions to a Product Problem

Title

Truesight Orchestration peer on multi-homed server fails to connect to grid

Summary

We have TSO installed on a peer with multiple IP addresses. It tries to connect to other peers using the wrong IP address and never joins the grid.

Product

BMC Atrium Orchestrator Platform

Component

BMC Atrium Orchestrator Platform

Applies to

BMC Atrium Orchestrator Platform, All versions.
TrueSight Orchestration Platform, All versions.

Problem

After installing a new BMC Atrium Orchestration / TrueSight Orchestration (TSO) peer. When starting it, it never joins the grid; it always displays as red in Grid Manager even though the service is running. When we check the logs for other peers, the below errors are captured in the logs.

WARN TopologyParticipant : When [HANode on [Peer name=CDP1 id=[JmsPeerId urn:jxta:uuid-59616261646162614E504720503250333AD4E4DC97E94B2AB61234567890ABCDEF]], isMasterCandidate=true] processing message with messageID=1265642623791 from peer
'[JmsPeerId urn:jxta:uuid-59616261646162614E504720503250333AD4E4DC97E94B2AB61234567890ABCDEF]',
an exception occurred:
Summary: P2P message transmission failed.
Detail: The return pipe ("urn:jxta:uuid-59616261646162614E504720503250333AD4E4DC97E94B2AB61234567890ABCDEF") indicated in the request cannot be resolved.
Cannot send response. Ignoring request.

The server does have two IP addresses, and in the network logging that the new peer is using the wrong IP address. For example, it is trying to communicate using an external IP instead of an internal IP. How we can direct the peer to the correct IP address?

Cause

During startup, a peer gets its IP address from the server. On a multi-homed server the operating system may return any IP address, which means the peer may use an IP address other than the one you intend.

Solution

On your new peer, open the file [TSO_HOME]/server/.jms/broker-config.xml. The file will look like this:

<broker-config>
<external>false</external>
<uri>ssl://10.11.12.123:8083?connectionTimeout=1000</uri>
</broker-config>

The <uri> element value listed in this file is the IP address the peer sends to the other peers. If that IP address is not valid or reachable from other peers, peer communication will fail and the peer will not be able to join the grid. To correct this, follow these steps:

Stop the peer service.
Open the file [TSO_HOME]/server/.jms/broker-config.xml
In the <uri> element, change the IP address to an IP address other peers can use to communicate with this peer.
Save the file and start the peer service.
If the peer fails to join the grid, open broker-config.xml and add <listen-addresses> and <advertise-addresses> blocks to the file. These settings explicitly control the IP address on which the peer listens and the address it advertises to other peers:

<broker-config>
<external>false</external>
<uri>ssl://10.11.12.123:8083?connectionTimeout=1000</uri>
<listen-addresses>
<address>10.11.12.123</address>
</listen-addresses>
<advertise-addresses>
<address>10.11.12.123</address>
</advertise-addresses>
</broker-config>

Save the file and restart the peer service.

After performing any change, go to the folder [TSO_HOME]\server\.jms\disco on the existing peers and check the contents of the discovery file for the new peer. If it contains the old IP address, copy the updated file with the correct IP address from the new peer to the other peers.

You may want your peer to use multiple IP addresses for different communications, as when it needs one IP to connect to other peers and a second IP to connect to Development Studio. In that case you can add multiple <address> elements to the <advertise-addresses> block:

<advertise-addresses>
<address>172.xx.xx.xx</address>
<address>10.xx.xx.xx</address>
</advertise-addresses>

Attachment(s):