Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Adopt Apstra Edge in Data Center Assurance

For Data Center Assurance to connect to Apstra Data Center Director through Apstra Edge, you need to adopt Apstra Edge in Data Center Assurance. After Apstra Edge is adopted successfully, Data Center Assurance generates a registration code for the edge. This registration code can be used only once and must be configured in Apstra Data Center Director to complete edge registration.

CAUTION:

The edge registration code is for one-time use only. After the Apstra Edge registers with Data Center Assurance on first boot, the code is no longer valid. After the first reboot, Apstra uses a stored secret.

The docker container on which the edge runs can be installed anywhere in the data center - either on the same virtual machine (VM) on which Apstra is running or on a different VM. If edge is installed on the same VM as Apstra is installed, you need to take care during upgrades to ensure that the edge installation is not removed.

After the edge is initialized and configured, the status of the edge will be displayed in Data Center Assurance as Registered. The Cloud Connectivity status indicates that the edge is connected with the cloud and Apstra Connectivity status indicates that the edge is connected with Apstra Controller. That is, you can monitor the connectivity status between Data Center Assurance and Apstra Edge, and between Apstra Edge and Apstra from the Data Center Assurance UI without having to access Apstra.

To adopt Apstra Edge:

  1. Log in to HPE Mist Networking Data Center Assurance and select your organisation if prompted.
  2. Navigate to the DC Edges page.

  3. Click Adopt Apstra Edge.

    The Adopt Apstra Edge wizard opens.

The Adopt Apstra Edge wizard guides you through each step of the Edge onboarding workflow.

Step 1 Enter Apstra Edge Details

Provide details about the Apstra Edge connections.

Figure 1: Apstra Edge Connection Details Adopt Apstra Edge wizard page to add Edge connection details.
  1. Enter information about the Apstra Edge device.
    Table 1: Apstra Edge Device Details

    Field

    Description

    Edge Name

    Unique name to identify Apstra Edge configured in the data center.

    Management URL

    URL to connect to the Data Center Director instance.

    The URL must follow one of the following formats:

    • For IPv4 addresses—https://ipv4-address

      For example: https://192.168.1.1

    • For IPv6 addresses—https://[ipv6-address]

      For example: https://[3fff:192:158:3::114]

    Username

    Username to log into the Data Center Director instance.

    Password

    Password to log into the Data Center Director instance.
  2. Expand the Flow Server Details section and enter the Flow Server information.

    Adding Flow Server connection details allows Data Center Assurance to collect flow data from the Apstra instance. After Flow Server Details are configured, you can view information about the data center network topology, hosts, endpoints, services, and anomalies on the App Aware and the Impact Analysis pages.

    You can configure as many flow servers as required. Click the "+" icon under the Flow Server section and enter details for the additional flow servers.

    Table 2: Flow Server Configuration

    Field

    Description

    Flow Server Name

    Name of the Apstra Flow server.

    Management URL

    OpenSearch REST API URL to connect to the Apstra Flow server.

    The URL must follow one of the following formats:

    • For IPv4 addresses—https://ipv4-address:port-number

      For example: https://192.168.1.2:9200

    • For IPv6 addresses—https://[ipv6-address]:port-number

      For example: https://[3fff:192:158:3::115]:9200

    Username

    Username to log into Apstra Flow server.

    Password

    Password to log into Apstra Flow server.
    Note:

    • If multiple Apstra Flow servers collect flow data from their respective sites and are configured to a single Apstra Edge device, you can add each flow server to the Apstra Edge device and receive the site flow data on Data Center Assurance.

    • The Apstra Flow information collected from the Apstra instance is stored in Data Center Assurance database for seven days.
  3. Expand the vCenter Details section and enter the vCenter information.

    Adding vCenter connection details allows Data Center Assurance to collect information from the vCenter about the virtualized environments and the alarms detected on VMs. After the details for vCenter are configured, you can view information about the VM layer on the App Aware, the Impact Analysis, and the Dashboard Topology pages. You can configure parameters for multiple vCenters.

    Table 3: vCenter Configuration

    Field

    Description

    vCenter Name

    A unique, user-defined name of the vCenter.

    Management URL

    REST API URL to connect to the vCenter server.

    The URL must follow one of the following formats:

    • For IPv4 addresses—https://ipv4-address

      For example: https://192.168.1.3

    • For IPv6 addresses—https://[ipv6-address]

      For example: https://[3fff:192:158:3::116]

    Username

    Username to log into vCenter server.

    Password

    Password to log into vCenter server.
  4. Expand the Job Scheduler Details section and enter the Job Scheduler information.

    Adding job scheduler server details allows Data Center Assurance to collect information from the job scheduler about job activity and status. After the details for a job scheduler are configured, you can view job-related information on the App Aware and the Dashboard Topology pages.

    Table 4: Job Scheduler Configuration

    Field

    Description

    Job Scheduler Name

    A unique, user-defined name of the job scheduler.

    Management URL

    OpenSearch REST API URL to connect to the job scheduler.

    The URL must follow one of the following formats:

    • For IPv4 addresses—https://ipv4-address:port-number

      For example: https://192.168.1.4:9200

    • For IPv6 addresses—https://[ipv6-address]:port-number

      For example: https://[3fff:192:158:3::117]:9200

    Username

    Username to log into job scheduler.

    Token

    Token to log into the job scheduler.

    Note:

    Create a token with a long validity period on the job scheduler since it cannot be renewed.

    Scheduler Type

    The type of job scheduler.

    REST API Version

    The version number of the REST API.

    Cluster Name

    The cluster name for the job scheduler.
  5. Click Generate Registration Key to move to the next step.

Step 2 Register the Apstra Edge on Data Center Director

Before you can receive data in Data Center Assurance, Apstra Edge must be installed and registered with your Apstra Data Center Director instance.

A key is generated in order to register the Apstra Edge on your Data Center Director instance. Copy this registration key and follow the steps below.

  1. Log into Apstra Data Center Director.
  2. Navigate to Platform>Apstra Edge.
    Figure 2: Register Apstra Edge on Data Center Director Register Apstra Edge on Data Center Director
  3. Click the + button in the top right to launch a new Apstra Edge container.
  4. In the Registration Key field, paste the registration key you copied from Data Center Assurance.
  5. Leave all other fields at their default values and click Create.

    This action registers the Apstra Edge device using the Edge version included in the Data Center Director install package.

    Figure 3: Registration Key for Apstra Edge Registration Key for Apstra Edge
    Note:

    If you enter an incorrect registration key, you must delete the Apstra Edge from Data Center Assurance and restart the onboarding process.
  6. Return to the Adopt Apstra Edge wizard on Data Center Assurance. After the Edge has been successfully registered on Data Center Director, a message is displayed confirming cloud connectivity.
    Figure 4: Apstra Edge Registration Adopt Apstra Edge wizard page to register the Edge.

    A site corresponding to the blueprint deployed in the data center is created on the Sites page.

  7. Click Proceed to System Checks to move to the next step.

Step 3 Run System Checks on the Apstra Edge (Optional)

The pre-flight checks feature verifies whether certain prerequisites and configuration requirements are met, and provides actionable guidance on how to resolve potential issues.

In this step, run pre-flight checks on the Edge level to verify whether the configuration requirements for the Apstra Edge are met.

Note:

  • Running System Checks is an optional step. Click Skip to skip the Edge-level pre-flight check and go to the next step.

  • The onboarded Apstra Edge must be running version 0.44.1 or above to run pre-flight checks.
  1. Click Run System Checks.

    The Edge level pre-flight checks start running in the background. After the pre-flight checks are complete, the pass/fail results of all the tests run are displayed.

  2. If any of the tests have failed, expand the test failure message to view more details. Follow the remediation actions provided and re-run the system checks to verify the Edge configuration.
  3. Once all the system checks pass, click Proceed to Site Checks.
    Figure 5: System Checks on Apstra Edge Adopt Apstra Edge wizard page with system check results.

Step 4 Run Site Checks on the Blueprints (Optional)

Run pre-flight checks on the blueprint level to verify whether the configuration requirements for the sites are met.

Note:

  • Running Site Checks is an optional step. Click Skip to skip the site-level pre-flight check and go to the next step.

  • The onboarded Apstra Edge must be running version 0.44.1 or above to run pre-flight checks.
  1. Select the check boxes for the sites on which you want to run pre-flight checks.
  2. Click Run Site Checks.

    The Site level pre-flight checks start running in the background. After the pre-flight checks are complete, the pass/fail results of all the tests run are displayed.

  3. If any of the tests have failed, expand the test failure message to view more details. Follow the remediation actions provided and re-run the system checks to verify the site configuration.
  4. Once all the site checks pass, click Complete Setup.
    Figure 6: Site Checks on Blueprints Adopt Apstra Edge wizard page with site check results.

Step 5 Complete Edge Adoption

Verify that the Edge configuration is completed correctly.

  • The wizard displays the registration status of the Edge, the Edge version, and the pass/fail results of the system and site checks. Click the cards to go back to any of the steps as required.
    Figure 7: Edge Adoption Complete Adopt Apstra Edge wizard page with onboarded Edge version, status, and system and site check results.
  • After successful onboarding of the Edge, click View all Edges. The newly onboarded Edge is listed in the DC Edges page.
  • To onboard a new Apstra Edge, click Onboard another Edge and the Adopt Apstra Edge wizard resets.

Manage Onboarded Apstra Edges

The DC Edges page displays the list of onboarded Edge devices along with their version and connection details.

Figure 8: DC Edges Page The DC Edges page with the list of onboarded Edges and their details.

After an Apstra Edge has been onboarded, Data Center Assurance allows you to perform the following actions:

  1. Run Pre-flight Checks

    You can run the pre-flight checks at any point after onboarding. To run pre-flight checks on an adopted Edge, select the Edge device or blueprint from the DC Edges page and click Run Pre-flight Checks. For more information, see Pre-Flight Checks.

  2. Delete Apstra Edge

    To delete an adopted Edge, select the Edge from the DC Edges page, click Actions>Release.

    The Confirm Release dialog box appears with a pre-deletion check list of configured DC Hub content packs or Marvis Minis. Ensure that you do not want to retain these configurations before proceeding with deletion. If there are no content packs or Marvis Minis configurations found, you can click Release to delete the Apstra Edge.

    Deleting the adopted Edge from Data Center Assurance also removes the connectivity with edge. Once the Edge is deleted, the action is not reversible and Data Center Assurance will not be able to receive information from Data Center Director. To resume receiving information, you must perform the Edge onboarding process again.

  3. Modify Apstra Edge

    To modify an adopted Edge, select the Edge from the DC Edges page, click Actions>Modify Edge.

    The Modify Apstra Edge dialog box opens with the Edge connection details. Modify the fields as necessary and click Modify. The onboarded Apstra Edge will be updated with the modified connection details.

  4. Upgrade Apstra Edge

    When an Edge is registered and onboarded for the first time, it runs the latest version of Edge available in the Data Center Director install package. Ensure that the Edge version is up-to-date to use the latest Data Center Assurance features.

    The Upgrade Status column displays New Version Available when a higher Edge version is available. To perform a remote Edge upgrade on an adopted Edge, select the Edge device or blueprint from the DC Edges page and click Upgrade Edge. For more information, see Upgrade Apstra Edge from Data Center Assurance.

    Note:

    The install package of every new Data Center Director release includes the latest Edge version as on the day of the release. When you upgrade the Data Center Director instance, the Edge version is automatically upgraded to the version available in the Data Center Director install package.

Note:

For Apstra Edge version 0.63.0 or later, the Edge service may generate and clean up temporary files in the container's /tmp directory during normal operation. Ensure that /tmp is configured to be a disk-backed filesystem and not as a memory-backed filesystem (tmpfs).