Troubleshooting Network Issues with Pulse

This article covers common network-related issues that can prevent Pulse from connecting to TM1 instances or functioning correctly in your environment.

How Pulse Connects to TM1

Pulse communicates with TM1 instances exclusively via the TM1 REST API. For each TM1 instance, Pulse needs:

• The REST API port to be open and reachable from the Pulse server (default: 8010 or as configured in tm1s.cfg via HTTPPortNumber).

• The Pulse Monitor port (8094 by default) to be accessible from the Pulse Application Server when using a centralized setup.

Common Network Issues

Pulse Cannot Connect to a TM1 Instance

Symptoms: Instance shows as offline or disconnected in Pulse.

Steps to diagnose:

1. From the Pulse server, open a browser and navigate to:

   http://<TM1Server>:<RESTAPIPort>/api/v1/$metadata

   If this does not return an XML response, the REST API port is not accessible.

2. Check that the TM1 REST API is enabled in tm1s.cfg:

   HTTPPortNumber=8010

3. Verify firewall rules allow TCP traffic on the REST API port from the Pulse server to the TM1 server.

4. If TM1 uses SSL, ensure Pulse is configured with the correct HTTPS port and certificate settings.

Pulse Monitor Not Reachable

Symptoms: Pulse Application Server cannot communicate with the Pulse Monitor on a remote TM1 server.

Resolution:

• Verify port 8094 is open on the TM1 server's firewall for inbound TCP connections from the Pulse Application Server.

• Check the monitor.yml file on the TM1 server to confirm httpport matches the port used.

• Test connectivity:

  http://<TM1Server>:8094

Proxy Environments

If the Pulse server requires a proxy to reach TM1 instances, configure proxy support in Pulse.cfg:

Once enabled, proxy settings can be configured per Pulse Environment in the Administration section of the web client.

SSL Certificate Issues

If TM1 instances use custom or self-signed SSL certificates, Pulse may reject the connection.

Resolution:

• Import the TM1 server's SSL certificate into the Java truststore used by Pulse.

• Alternatively, use a certificate signed by a trusted Certificate Authority (CA).

• See Considerations When Enabling SSL to TM1 with Custom Certificates for full steps.

Timeout Errors

If Pulse times out when connecting to TM1 instances:

1. Increase the REST API timeout values in Pulse.cfg:

   [Monitoring] ServerThreadTimeoutSeconds = 120

2. Check whether the TM1 server is under heavy load — high CPU or memory on TM1 can cause slow REST API responses.

Useful Diagnostic Tools