[ER] Testing Node Agent - Master Server connectivity

Introduction

This article shall serve as a guide on testing the ER Node/Proxy Agent's connection to your Master Server using the in-built Connection Diagnostic Tool.

The diagnostic tool provides useful collective information for us to troubleshoot any connection issues with Enterprise Recon.
In the case of any connectivity issues, it is recommended that you run the tool first and take a screenshot of the results before submitting a support ticket.

Prerequisites

  • Ensure you have root access/administrative rights
  • If you have firewall installed, ensure that your Node Agent is allowed to communicate with the Master Server (port 11117)
    For the full list of ports used, please refer to this article.

 

How to use (Linux)

  1. Open up a Terminal window (CTRL + ALT + T)
  2. Enter the command; cd /var/lib/er2
  3. Stop the ER service by entering the command; er2-agent -stop
  4. Run the Enterprise Recon Connection Diagnostic Tool by entering the command; er2-diagnostic
  5. You should see this prompt,

    Screenshot_from_2016-04-06_16_25_34.png

    ... the path shown, '/var/lib/er2/agent.cfg' is the default agent configuration path, if you have moved 'agent.cfg' to another directory please input the correct path, otherwise press Enter
  6. Let the diagnostic tool run
  7. When finished, the tool will display either a "Diagnostic SUCCESSFUL" or "Diagnostic FAILED" message

 

How to use (Windows)

  1. Open up a Command Prompt window as Administrator
  2. Enter the command; cd C:\Program Files (x86)\Ground Labs\Enterprise Recon 2 
    (if you have installed Enterprise Recon to another directory, use that path instead)
  3. Run the Enterprise Recon Connection Diagnostic Tool by entering the command; er2_diagnostic
  4. You should see this prompt,

    ER2_Diagnostic_Tool__Windows_.png

    ... the path shown, 'C:\Program Files (x86)\Ground Labs\Enterprise Recon 2\agent.cfg' is the default agent configuration path, if you have moved 'agent.cfg' to another directory please input the correct path, otherwise press Enter.
  5. Let the diagnostic tool run
  6. When finished, the tool will display either a "Diagnostic SUCCESSFUL" or "Diagnostic FAILED" message

 

Conclusion

When the Enterprise Recon Connection Diagnostic Tool is done, it will show a rundown of various connection activities and information.
Should you need our help with any connectivity issues, please include a screenshot of the diagnostic results in your support ticket.

 

All information in this article is accurate and true as of the last edited date.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.