Subscription Status Unknown
Issue
The JetStream DR UI may indicate the warning “Subscription status unknown. Please check the management server’s external connectivity.”
On the Configurations screen the Subscription ID is reported with a yellow icon.
Mousing over the icon indicates the status “Unknown”
Troubleshooting
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
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)
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
. PostgreSQL and Tomcat8 services should both appear running.
If the issue persists resulting in the MSA being unable to validate the Subscription ID, it can result in suspension of VM protection.
Restarting Tomcat Services (only)
From JetStream DR software version 4.3 and beyond it is possible to manually restart the Tomcat service only. Use the following command to restart Tomcat: #service msa-tomcat restart
.