Try our new documentation site (beta).
Filter Content By
Version
Text Search
${sidebar_list_label} - Back
Filter by Language
Troubleshooting Connectivity Issues
You can test to see if a Remote Services node is reachable with the node ping command:
> grbcluster node ping --server=server1 Node is not reachable
The node latency command provides additional details:
> grbcluster node latency ADDRESS LATENCY NBERR server1 1.12813ms 0 server2 1.218103ms 0This will display the latency from the client machine to each node in the cluster.
Add the —describe flag to see an explanation of each field:
> grbcluster node latency --describe ADDRESS - Node address LATENCY - latency between the local client and a node NBERR - Number of errors
![](/wp-content/plugins/hd_documentations/content/images/documentation-ampl-guide.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/documentation-cloud.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/documentation-example-tour.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/documentation-quick-start.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/documentation-reference-manuals.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/documentation-remote-services.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/quickstart-os-linux.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/quickstart-os-mac-osx.webp?x70725)
![](/wp-content/plugins/hd_documentations/content/images/quickstart-os-windows.webp?x70725)