Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Troubleshooting Juniper CloudX

This chapter takes you through the steps involved in checking if your switch is communicating with Mist cloud by using CloudX.

To check if a switch communicates with Mist cloud using CloudX:

  1. Run the below CLI commands on the switch:

    To verify CloudX through the Mist portal, you can use the steps below:

    1. Log in to the Mist portal (manage.mist.com).
    2. Click Switches > switch name to go to the switch detail page.
    3. Click any port or a range of ports.

      If CloudX is running, the Packet Capture button is enabled; otherwise, the button is grayed out.

    You can also check if CloudX is enabled on multiple switches by using the Mist portal.

    To do that, click Site > Switch Packet Captures > Add Switch.

    The switches listed here are all CloudX-enabled.

  2. Verify that Mist Cloud Daemon (mcd) and Junos Mist Daemon (jmd) are running.

    mcd is responsible for enabling communication between the switch and the cloud. It maintains a secure WebSocket connection to the terminator in the cloud.

    jmd is used for:

    • Generating periodic statistics for the device.
    • Applying device configuration.
    • Gathering device events.
    • Initiating device functions (such as packet capture and software updates).
    • Returning results from requested functions (such as files and streamed data).

    To verify that jmd and mcd are running, use the following CLIs:

  3. Check the jmd and mcd logs for any errors by using the CLI commands below. Typically, jmd logs shows issues related to configuration or stats. The mcd logs report issues related to the connectivity between the switch and the cloud.
  4. If jmd or mcd is not running for some reason, try restarting it, as shown in the sample below.
  5. If the switch is not connecting to the cloud, check its reachability by using a ping and curl test. These tests will help you check if the required firewall ports are allowed.

    The cloud endpoints are not set up to respond to ping tests; however, running a ping test will ensure that DNS resolves FQDN. Here is a sample ping test:

    Here is a sample curl test:

    A valid response from the curl test proves that the jma-terminator in the Mist cloud is reachable. A lack of response or receipt of an error will indicate that the path between the switch and the cloud is blocking these ports, likely because of the firewall. The URLs used in the test are the same as those in firewall ports and differ between cloud instances.

Related Documentation