MCE to ME Connectivity Check

This section describes how to verify that the Management Control Engine (MCE) can communicate with the Mediation Engine (ME).

This check confirms:
  • Network connectivity (HTTPS)
  • TLS certificate trust
  • API authentication
Run the following command from the MCE server CLI:
curl -sS \
  --connect-timeout 10 \
  --max-time 30 \
  --cacert /path/to/<ME_CERTIFICATE>.pem \
  -H "X-API-Key: <TOKEN>" \
  "https://<ME_HOST>/me/MonitorGraph?selected=%5B195%5D&raw_data=true&period=1&format=json"
If the request fails, check the following common issues:
  • Incorrect certificate path

    Ensure the --cacert path points to a valid ME CA certificate file.

  • Invalid or expired API token

    Verify that the X-API-Key value is correct and active.

  • Network connectivity issues
  • Confirm that HTTPS traffic (port 443) is not blocked between MCE and ME.
  • Untrusted TLS certificate

    Ensure the ME certificate is signed by a CA included in the specified PEM file.

Parameter Reference
Parameter Description
--cacert Path to the ME CA certificate (PEM format) on the MCE server
-H "X-API-Key: <TOKEN>" API token used to authenticate with the ME
<ME_HOST> Hostname or IP address of the Mediation Engine
selected=%5B195%5D URL-encoded array [195]; specifies the monitoring graph ID
period=1 Time period for the query (1 = most recent period)
format=json Specifies JSON output format
The following example shows a completed connectivity check command:
curl -sS \
  --connect-timeout 10 \
  --max-time 30 \
  --cacert /opt/certs/me-cert.pem \
  -H "X-API-Key: abc123xyz" \
  "https://me.example.com/me/MonitorGraph?selected=%5B195%5D&raw_data=true&period=1&format=json"