Apstra Edge Logs

If Apstra Edge shows as Unregistered or is unable to connect to DC Assurance or Apstra, check the Apstra Edge container logs to diagnose the problem.

1. Connect to the Apstra VM via SSH.

2. View the Apstra Edge logs using:

   docker logs apstra_edge | tail -n 1000

   This command displays the last 1000 lines of the Apstra Edge container logs. Review the output for error messages. From the logs, you can diagnose:

   • Whether the Apstra Edge has successfully registered with DC Assurance, or why registration is failing.
   • Whether the Edge is successfully and is collecting sFlow data from the Flow collector.
   • Whether Apstra topology data is being pulled from Apstra Data Center Director and sent to DC Assurance.

   Common issues include incorrect credentials, network connectivity problems, firewall rules blocking outbound traffic, or mismatched registration IDs. Verify the following:

   • The registration ID from DC Assurance matches what you configured in the Apstra UI.
   • Network connectivity exists between the Apstra VM and DC Assurance cloud services (dc.ai.juniper.net and ep-term.ai.juniper.net).
   • Firewall rules allow outbound TCP 443 traffic to the required cloud endpoints. See the Network Connectivity and Firewall Requirements section in Prerequisites for the list of required ports and services.
   • If behind a proxy, the Apstra Edge is configured to route through the proxy correctly.