Troubleshoot a remote galaxy connection

Local services

The AVEVA Watchdog Service is a utility to start all the System Platform Core Services. The Watchdog Service starts automatically when you start your operating system.

The Watchdog Service and other services are tightly coupled with Application Server configuration and run-time operations.

• The Watchdog Service must be running in order to create service instances and nodes, to deploy, undeploy, or delete user-defined services.

• The Watchdog service must be running whether or not you are using a multi-galaxy environment.

Do not stop the Watchdog service even if you do not plan to use a multi-galaxy environment.

These steps use general Windows operating system for illustration.

1. From the Windows Start menu open Windows Administrative Tools, then select Component Services. The Component Services utility opens.

2. Open Services (Local).

3. Select the AVEVA Watchdog Service to view its state.

4. If the Watchdog service is not running, Start the service.

5. Close the Component Services utility.

Service discovery configuration

By default, the Local Galaxy Server primary node is not configured (blank), and must be designated before you can enable galaxy pairing.

By default, the Cross Galaxy Server primary node is not configured (blank), and must be set to the designated Cross Galaxy Server before you can enable galaxy pairing.

There can be only one Cross Galaxy Server in a multi-galaxy environment. All galaxies in the environment must designate the same Cross Galaxy Server primary node.

Do these steps for each galaxy in the multi-galaxy environment for which you are having connectivity issues.

6. From the IDE ribbon, select Galaxy, then Configure.

7. Select Communication, then Cross-galaxy server.

8. Verify or configure the Local Galaxy Server Primary node as the local galaxy GR node.

9. Verify or configure the Cross Galaxy server Primary node as the node you have defined as the Cross Galaxy Server for all paired galaxies.

Multi-Galaxy configuration

Multi-Galaxy configuration establishes and maintains the trust relationship between paired galaxies for the duration of the pairing session.

Remote pairing must be enabled on each GR to be paired, each of which requires the same unique passphrase.

10. From the IDE ribbon, select Galaxy, then Configure.

11. Select Communication, then Cross-galaxy server to open Multi-Galaxy configuration page.

12. Verify that the galaxy or galaxies to be paired are listed in the Galaxy Repository list box.

    1. If a particular galaxy is not listed, select the Add button to open the Select Galaxy Repository to pair with dialog box.

    2. Enter the Target Galaxy Repository node in the text box.

    3. Enter the Passphrase in the text box.

13. If pairing fails, ensure that remote pairing is enabled on the target GR, and that you have the correct passphrase entered.

Services configuration

The user-configurable Application Server Services provide communication channels for attribute browsing and run-time data access.

By default one instance of each service is configured and locally deployed.

At least one instance of each service must be deployed on each galaxy in the multi-galaxy environment for multi-galaxy communication to function.

Note: When you set or change the Local Galaxy Server or the Cross Galaxy Server, the core ASB services automatically restart. This can create a timing issue if you immediately deploy a platform. The ASBMxDataProvider and the ASBAuthentication services can fail to deploy. Run-time connectivity would then fail in the multi-galaxy environment.

For more information about configuring Application Server Services, see Configure and deploy PCS services.

For browsing issues, verify the ASBGRBrowsing service instance.

For run-time data subscription issues, verify the ASBMxDataProvider service instance on the publisher side, and ensure that the galaxy is deployed.

For secured write issues, verify the ASBAuthentication service instance.

14. From the IDE ribbon, select Galaxy, then Configure.

15. Select System, then Services to open the Configure Services dialog box.

16. Expand the GR node in the hierarchy pane to view the installed services. Expand each service in the hierarchy to view the service instances.

    1. Select the instance to view its configuration in the configuration pane.

    2. Verify that the Galaxy Name is correct (ASBGRBrowsing service only).

    3. Verify that the service instance is assigned to a node, visible in the Assignments pane, and that the node is correct.

    4. Verify that the service instance is deployed.

17. Edit the service instance configurations as necessary.

Client configuration

The Galaxy Browser, Object Viewer, and Managed InTouch applications can function as clients to browse attributes in the System Platform namespace, or to subscribe to run-time data.

Using these clients in a multi-galaxy environment is described in Access multiple galaxies.

For Object Viewer communication errors, review the Attribute Reference syntax. In particular, ensure that the correct <GalaxyName>: prefix is present and points to the correct galaxy.

For Galaxy Browser errors, ensure that you have selected the correct galaxy in the Galaxy: list box.

For Managed InTouch errors:

• Ensure that you have selected the correct galaxy when accessing tagnames and attributes from the Galaxy Browser.

• Ensure that syntax is correct, including the "Galaxy:" access name prefix, and the full attribute reference in quotes, with the remote galaxy prefix as part of the expression. Correct any incorrect syntax.

  Note: If you selected InTouch HMI Development and Run Time during installation, you cannot create a multi-galaxy environment. This installation does not include a GR, required for multi-galaxy functionality.

Security configuration

OS User with domain users only and OS Group (supports only domain users) are the only security models supported in a multi-galaxy environment.

Security issues, evident with failed writes, can occur for any of the following possible causes:

• Security mode of galaxy is set to Galaxy Security

• Security mode of InTouch is not set to ArchestrA

• User has not logged into the remote Galaxy at least once

• Security modes of local and remote galaxies don’t match

• User doesn’t have sufficient permissions to perform the write

• Default User Authentication service is not deployed on the GR node

For information about security configuration, see Configure security.

In the IDE, set the security mode to Galaxy Security.

In InTouch HMI, set the security mode to ArchestrA.

In the multi-galaxy environment, set local and remote galaxy security to the same mode for each galaxy.

In the multi-galaxy environment, log into each remote galaxy at least one time (for each user who requires access to those galaxies and has sufficient write permissions).

In the Configure Services dialog, verify the ASBAuthentication service instance.

18. From the IDE, select the Galaxy menu, then Configure.

19. Select System, then Services to open the Configure Services dialog box.

20. Expand the GR node in the hierarchy pane to view the installed services. Expand the each service in the hierarchy to view the service instances.

    1. Select the instance to view its configuration in the configuration pane.

    2. Verify that the service instance is assigned to a node, visible in the Assignments pane, and that the node is correct.

    3. Verify that the service instance is deployed.

21. Edit the service instance configurations as necessary.

Unpairing galaxies

Unpairing galaxies requires that communication is established with the remote node to be unpaired. If communication with a remote galaxy is broken, unpairing with that node will fail.

This condition can occur in different scenarios, including:

• The remote node is down or not on the network.

• The System Authentication service is not running.

• The Watchdog service is not running

• A mismatch or corruption has occurred in a security key.

When an unpair operation fails, you will see the Un-pair operation with remote Galaxy Repository failed error message and dialog box.

This dialog box offers you a choice to force the unpair, or to wait until the remote GR is back online.

• Select Yes to force the unpair.

  The forced unpairing occurs only on the local GR. When the remote GR is back online, any client running on the remote GR will be unaware that an unpairing has occurred, and will still be able to discover and connect to the service on the local GR from which you performed the failed unpairing operation.

• Select No to end the unpairing operation and wait until the remote GR is back online.

  When you select No, the system takes no action, and pairing remains as configured.

  You can now troubleshoot why the remote GR is offline, then retry the unpairing operation.