Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Download and Run the Apstra Cloud Services Setup Validation Tool

This topic walks you through the process of downloading and running the Apstra Cloud Services (ACS) setup validation tool. This tool verifies that you have configured the various devices and services of your DC fabric correctly.

Before proceeding, ensure that:

Use this tool to check the health and connectivity of your ACS-managed DC fabric. The tool performs a series of checks to verify the required prerequisites below. Additionally, in order to ensure an optimal setup process for your DC fabric, the tool verifies that you have completed the onboarding steps for Apstra, Apstra Edge, and ACS. The tool performs the following checks:

  • Apstra version is 4.1.2 or later

  • Apstra API is reachable from Apstra VM

  • Flowcoll service is configured correctly and up and running

  • Apstra Flow is reachable from Apstra VM

  • Apstra Flow API is reachable from Apstra VM

  • Apstra VM is reachable

  • Opensearch service is up and running

  • SFlow, SNMP, and collector IP are present in configlet

  • JCloud certificate is present

  • IBA probe is present in blueprint

  • Devices associated with a blueprint can reach Apstra Flow VM

  • Apstra Edge is configured correctly and active

  • Cloud URL (https://dc.ai.juniper.net) is reachable

To download and run the ACS Setup Validation Tool:

Note: We documented this process using ACS Setup Validation Tool version 0.1.26. The version you download might be a later version.
  1. Download the latest tarball file from the Juniper Downloads site.
    Note:

    To avoid any connectivity issues between the Apstra VM and other VMs or services, we recommend that you install the ACS Setup Validation Tool on the same VM as the Apstra controller.
  2. Extract the tarball.
  3. Navigate to the validation tool directory.
  4. Enter the environment variables in the sample.env file.
  5. Run the tool with the .env file provided (no interaction required).
  6. Run the tool interactively. In this mode, you must provide each of the parameters in sample.env.
  7. (Optional) Use the --help command for additional precheck options.
  8. (Optional) Change the default location of the .precheck.json file where the tool populates the PASS/FAIL/SKIPPED status results.
  9. (Optional) View the validation tool logs.
  10. (Optional) Create a debugging tarball to store logs and config files for offline debugging support.
    If you need help troubleshooting your setup, Juniper uses these files for useful information about your setup. Juniper redacts sensitive information from the config files before collection. No sensitive information about your setup is collected.
    1. Set the COLLECT_DEBUG_DATA variable to true in sample.env.
    2. Run the validation tool.
      An acs_setup_validation_debug_<timestamp> tarball is created.