Versions Compared

Version Old Version 6 New Version Current
Changes made by

Syed Sarfraz Hussain

Anthony Lai

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue

  • The

...

  • JetStream DR UI

...

  • may indicate

...

  • the warning

...

  • “Subscription status unknown. Please check the management server’s external connectivity.”

...

If you navigate to jetDR > configurations the subscription ID will report a yellow tag (if we hover the mouse pointer it will report Unknown as below)

...

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

    • Mousing over the icon indicates the status “Unknown”

...

Troubleshooting

  1. Validate the connection from the MSA to the MMS server (40.112.243.46). If it fails, it may report as bellow (in this case subscription issue is expected)

    • 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 will report MMS connections timeout (as below), if and review the file.

    • If there is a communication between the MSA and MMS

    server.

    • 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 there is any a firewall is trying to block blocking the MMS server (jsdr-mms.azurewebsites.net/40.112.243.46) via on port 443.

Resolution

...

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

  • If it is connected wait for some time and the connection appears valid, wait a period of time to see if the warning goes away automatically.

  • If the warning stays then persists, restart the vme2 service on MSA will resolve it #service vme2 restart

Note

Failure to address this issue and if the MSA is unable to validate the subscription ID, it could result in the suspension of VM protection. There is a grace period of 14 days before suspension occurs.

Reference:

Subscription Issue

Steps to get subscription id from Azure marketplace

  • 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 Tomcat8service 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.

...

Note

If the issue persists resulting in the MSA being /wiki/spaces/KBDR/pages/

...

2781282609, 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.