Versions Compared

Old Version 8

changes.mady.by.user Shirly Tsang

Saved on

compared with

New Version 9

changes.mady.by.user Alex Mandel

Saved on

Key

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

...

In the left panel, you can view the overall status for each configuration component through the following status icons:

  • The checkmark iconImage Modified = The service is running properly and connectivity is good. No corrective action is required.
  • A blank, grey iconImage Modified = The service has not been started and no connectivity has been established. Configure the service if necessary.
  • The X iconImage Modified = The service or connectivity failed. Take corrective actions by modifying the configuration.

In the Configuration pane on the right, you can view the overall status for each service and individual component, as follows:

  • The OK iconImage Modified= The service, connection, and settings have been verified and functioning properly.
  • The Not Started iconImage Modified = The service or connection has not started yet.
  • The icons shows X and FailedImage Modified = The service, connection, and/or settings failed. Take corrective actions by modifying the configuration.
  • The Not Applicable iconImage Modified = No configuration has been set for this service, therefore, no verification is done until you set up the necessary configuration.

...

You can configure the Kubernetes Bridge settings in this section. If the network CIDRs are not configured, the Kubernetes Bridge uses the default IP of 10.42.0.0/16 for the cluster CIDR and 10.43.0.0/16 for the service CIDR. The system conduct a health check on the setting and displays OK if the settings are valid.

A screenshot of the Kubernetes Bridge Settings dialog box. It contains a text field for entering a Cluster CIDR, a text field for entering a Service CIDR, an OK button for the Kubernetes check, and an OK button for closing the dialog box.Image Modified

Authentication

...

The Device UI displays the join token and serial number of the host in this section. If authentication failed, you can verify the join token and correct in the join token field. If the authentication failed due to an incorrect serial number, you can modify the serial number in the Cloud Services Portal. Note that the serial number displayed here is automatically populated from the information you provided either via the Cloud Services Portal. You cannot modify the serial number here.

A screenshot of the Authentication dialog box. It contains a text field for entering a join token, a text field for entering a serial number, an OK button for Authentication, and an OK button for closing the dialog box.Image Modified

Cloud Connectivity

...

  1. Connect to the serial console of your host.
  2. Once you get health checks on the serial console as illustrated in the screenshot below, press Ctrl+c to connect to the host. You will be redirected to the debugging CLI login prompt.

    A screenshot of the debugging CLI login prompt.Image Modified
  3. Use the following credentials to log in:
    • Login: admin
    • Password: The last 8 digits of the serial number (without spaces)

      A screenshot of the login prompt on the debugging CLIImage Modified 

SSH

You can enable or disable a secure terminal connection on port 2022 to access the debugging CLI from the Device UI.

...

  1. Log in to the Cloud Service Portal.
  2. Enable local access on the host. For information, see Managing Local Access for Hosts.
  3. Launch and log in to the Device UI. For information, see Accessing the Device UI in this topic.
  4. Go to the SSH section and click Enable. Once you enable SSH, the Disable button appears.
    A screenshot of the debugging CLI for a host that is onlineImage Modified
  5. Use an SSH client to connect to the debug CLI on port 2022 (example: ssh -p 2022 admin@[remote_host_ip]).
  6. Use the following credentials to log in to the debug CLI:
    • Login: admin
    • Password: The last 8 digits of the serial number (without spaces).

...

  1. Launch and log in to the Device UI. For information, see Accessing the Device UI in this topic.
  2. Go to the SSH section and click Enable. Once you enable SSH, the Disable button appears.
    A screenshot of the debugging CLI for a host that is offlineImage Modified
  3. Use an SSH client to connect to the debug CLI on port 2022 (example: ssh -p 2022 admin@[remote_host_ip]).
  4. Use the following credentials to log in to the debug CLI:
    • Login: admin
    • Password: The last 8 digits of the serial number (without spaces)

...