Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

Issue

  • The JetStream DR UI may indicate the warning “Subscription status unknown. Please check the management server’s external connectivity.

subscription1.png

  • On the Configurations screen the Subscription ID is reported with a yellow icon.

    • Mousing over the icon indicates the status “Unknown

subscription2.png

Troubleshooting

  1. Validate the connection from the MSA to the MMS server (40.112.243.46).

    • The following error may be reported if the connection fails:

[root@fs087-msa ~]# curl -v https://40.112.243.46:443

About to connect() to 40.112.243.46 port 443 (#0)
Trying 40.112.243.46... Connection refused
couldn't connect to host
Closing connection #0
curl: (7) couldn't connect to host

  1. From the MSA, navigate to /var/lib/vme2/logs/ > jss.log and review the file.

    • If there is a communication between the MSA and MMS servers an MMS connection timeout error may be reported:
      2023-12-08 14:44:18,912 ERROR [Thread-8] (ReplicationSiteHelper.java:490) MMS status check failed.
      at com.jetstream.jss.task.systemtask.MmsCommunicationTask.updateStatus(MmsCommunicationTask.java:152)

  2. Check if a firewall is blocking the MMS server (jsdr-mms.azurewebsites.net/40.112.243.46) on port 443.

Resolution

  • Open port 443 on the MMS server and verify connectivity to it from the MSA using the curl command: curl -v https://jsdr-mms.azurewebsites.net:443

  • If the connection appears valid, wait a period of time to see if the warning goes away automatically.

  • If the warning persists, restart the vme2 service on the MSA using the command: #service vme2 restart

    • The Postgresql and Tomcat8 services used by JetStream DR software will be stopped and then restarted.

    • The Postgresql service is the MSA DB service and the Tomcat8 service is a webserver service.

  • Verify that status of the MSA services using the command: #service vme2 status. Pgsql and Tomcat8 services should both appear running.

image-20240212-090238.png

If the Tomcat8 service does not start, it can be manually restarted with the command #service msa-tomcat restart (only available for JetStream DR software version 4.3 and beyond).

If the issue persists resulting in the MSA being unable to validate the Subscription ID, it can result in suspension of VM protection.

  • No labels