Product Documentation

Appearance

7.1.2
7.0.2
6.9.3
5.4.17
5.2.31

Enabling Remote Diagnostics ​

Before you can configure remote diagnostics, make sure that connectivity is established with the diagnostics server and that the appliance is registered for diagnostics support.

  1. Check remote diagnostics server connectivity. (If your appliance is going to use email-based diagnostics, you can skip this step.)

Test connectivity to the diagnostics server by doing an ssh to the manager node on the appliance, then running the following telnet command. .

$ telnet phonehome.yellowbrick.io 443
Trying 10.30.20.160...
Connected to phonehome.yellowbrick.io. 
Escape character is '^]'.

This output shows that the manager node can connect to the server at port 443. You can enter CTRL+C to escape. If this command hangs, you will need to get connectivity resolved before you can proceed.

  1. Make sure the appliance is registered, or re-register it if necessary.

Yellowbrick always ships appliances that are already registered. Verify this by using the ybcli system status command. If for some reason the registration is lost, follow these steps to re-register the cluster with Yellowbrick.

Use ybcli system register to execute the registration process and get the Yellowbrick cluster certificates. Running this command makes a registration request using REST, generates the certificates, and returns them in the REST response:

YBCLI (PRIMARY)> system register <tenant-name> <system-name>

where <tenant-name> is the company name and <system-name> is the system name. Yellowbrick has so far named all systems Yellowbrick1 to YellowbrickN. This step requires connectivity to the Yellowbrick diagnostics web service on port 443. If connectivity is blocked at the customer site and registration is lost, contact Yellowbrick support for a manual registration.

Parent topic:Remote Diagnostics