Configuration of Domains across subnets

Domains Across Different Subnets

RV communications are based upon UDP and therefore will not cross a router to a different
subnet. This means that if a domain must span different subnets then one of the following
three choices must be made:

• 1. Use RVRD binaries to transfer the domain related RV messages (for an RV based domain) between the
different subnets.
• 2. Use EMS as the domain transport.
• 3. Have the machines on the remote subnet connect to an RV daemon on the Administrator subnet.

Note that option 3 is NOT recommended and is included in the above list for completeness.
This option has a number of known issues which include:

• The tibhawkhma binary will not start on one of the machines so the status of that machine will not be
reported correctly.
• Inappropriate microagents will be loaded if the two machines are using different operating systems.

Using RVRD
There needs to be at least one RVRD binary running on the Admin network and one running
on each separate remote network. However, it is recommended to have two RVRD binaries
running on each network, one for domain Hawk traffic and one for domain data traffic.

No changes need to be made to the domain configuration, instead an RVRD needs to be

started up for each of the daemon parameters used in the domain. By default these are
tcp:7500 for the domain data traffic and tcp:7474 for the domain Hawk traffic. The RVRD
binary acts as a replacement for an RVD binary in that it will also listen and broadcast RV
messages on the local subnet. This means that you cannot (and do not need to) have an
RVD and RVRD running on the same listen parameter on the same machine. This does
mean that you must ensure that on the machine where RVRD runs, that these binaries are
started before any process that might try to use RV, such as the Admin server or Hawk
Agent. If there is no RV binary running then these processes will start an RVD and that will
prevent the RVRD from starting.

There are details about setting up RVRDs in the TIBCO Rendezvous Administration
documentation - chapter 5, Routing Daemon.

Generated by Clearspace on 2011-01-17-06:00

1
Configuration of Domains across subnets

Subjects that must be imported/exported

At a minimum, the following subjects need to be imported and exported to allow domain
communications to occur between the two subnets: For the domain Hawk communications:

_HAWK.>

For the domain data communications:

com.tibco.repo.>

com.tibco.pof.>

If a secondary server is used within the domain (on a different subnet from the primary
Admin server)

_RVFT.>

_RVCM.>

_RVCMQ.>

If there are applications listening/sending on specific subjects then these will also need to be
imported/exported.

Using EMS
If EMS is used as the transport then no additional setup is required above what would
normally be needed for adding a machine to an EMS based domain. Note however, that
client machines do need to be able to access both the EMS server and the database that
stores the domain data.

Document References
TIBCO Rendezvous documentation (this can be found in the directory

<TIBCO HOME>/tibrv/doc

Troubleshooting
• Diagnosing communication issues

Generated by Clearspace on 2011-01-17-06:00

2
Configuration of Domains across subnets

For an RV based domain, try using tibrvlisten/tibrvsend, which can be found in the
RV_HOME/bin directory. Test each of the subjects listed previously and try sending
messages in both directions across the RVRD bridge.

• Stopping timeout messages from occurring when trying to deploy to a remote machine.

First make sure that the communication across subnets is working(using

tibrvlisten/tibrvsend). Then try increasing the value of the timeout parameter
java.property.tra_deploy_timeout in the file

<Admin Home>/domain/<domainName>/bin/tibcoadmin_[domainName].tra

• Checking the RVRD configuration

You can check the setup of the RVRD configuration by running the command:

rvrd -idle -store store file

The output will look similar to the content in the text box below.

H:\>rvrd -idle -store c:/rvrd_temp.store TIB/Rendezvous daemon

Copyright 1994-2008 by TIBCO Software Inc.

All rights reserved.

Version 8.1.1 V1 4/24/2008

2009-02-10 16:33:43 rvrd: Command line: rvrd -idle -store c:/rvrd_temp.store

2009-02-10 16:33:43 rvrd: Hostname: myComputer

2009-02-10 16:33:43 rvrd: Hostname IP address: 10.100.2.107

2009-02-10 16:33:43 rvrd: Detected IP interface: 10.100.2.107 (IP00)

2009-02-10 16:33:43 rvrd: Detected IP interface: 127.0.0.1 (loopback)

2009-02-10 16:33:43 rvrd: Using store file c:/rvrd_temp.store

2009-02-10 16:33:43 rvrd: Initializing random pool...

2009-02-10 16:33:43 rvrd: Logging: Connections - On, Subject Interest - Off, Subject Data
- Off.

Generated by Clearspace on 2011-01-17-06:00

3
Configuration of Domains across subnets

2009-02-10 16:33:43 rvrd: Http interface - http://myComputer.emea.tibco.com:7580/

2009-02-10 16:33:43 rvrd: Https interface - https://myComputer.emea.tibco.com:2569/

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Defined.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Neighbor DIVRM.ENSV0069.TEST

defined. Neighbor host name: ensv0069.eni.pri. Neighbor port: 8003. Local port: 8003. Link
cost: 1.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Local network 8610.10.130.3.127.LN

defined. Interface: 0.0.0.0. Service UDP port: 0, Service spec: 8610, Network spec: . Link
cost: 1.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Export subject com.tibco.repo.> from

local network 8610.10.130.3.127.LN.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Import subject com.tibco.repo.> with

weight 10 for local network 8610.10.130.3.127.LN.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Local network 8605.10.130.3.127.LN

defined. Interface: 0.0.0.0. Service UDP port: 0, Service spec: 8605, Networ

k spec: . Link cost: 1.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Export subject com.tibco.repo.> from

local network 8605.10.130.3.127.LN.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Export subject _RVCM.> from local

network 8605.10.130.3.127.LN.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Import subject com.tibco.repo.> with

weight 10 for local network 8605.10.130.3.127.LN.

2009-02-10 16:33:43 rvrd: DIVRM.ENSV01FX.TEST: Import subject _RVCM.> with weight

10 for local network 8605.10.130.3.127.LN.

Information to be sent to TIBCO Support

If there is a communication issue within the domain then open an SR with TIBCO Support
and upload the following:

• If RVRD is in use, the RVRD xml configuration, which can be obtained from the RVRD user interface, and
the results of using tibrvlisten/tibrvsend between the two subnets.

Generated by Clearspace on 2011-01-17-06:00

4
Configuration of Domains across subnets

• The RVRD store file, the location and name of which will be defined on the RVRD command line.
• <TRA HOME>/domain/<domainName>/logs/administrator.log
• The Administrator console output.

If there is a problem deploying an application or viewing status regarding the remote

machines then open an SR and upload the following from both the Administrator and client
machines.

• <TRA HOME>/domain/<domainName>/logs/hawk.log
• <TRA HOME>/domain/<domainName>/logs/hawkagent.log
• <TRA HOME>/domain/<domainName>/logs/tsm.log

From the Administrator machine alone:

• <TRA HOME>/domain/<domainName>/logs/administrator.log

Generated by Clearspace on 2011-01-17-06:00

5