Error codes and workarounds

Edit online

Resolve known error codes and warning codes by applying the recommended workarounds.

The following list includes some known error codes, their descriptions, and recommended workarounds:

The following list includes some known warning codes, their descriptions, and recommended workarounds:

ERR-MIST-RUNTIME: Recovered from Runtime Panic

Symptom
When a Go runtime panic is raised within a scope block and recovered by a defer statement using HandlePanic(s), the message ERR-MIST-RUNTIME: Recovered from Runtime Panic is displayed.
Cause
This issue occurs due to one or more of the following reasons:
  • Accessing nil pointers or uninitialized maps or slices during API parsing or decoding.
  • Performing invalid type assertions or JSON unmarshal operations without error checks.
  • Accessing elements out of bounds in paginated results or device lists.
  • Making incorrect assumptions about data returned from the Mist API.
Solution

To resolve this issue, enable debug logging and collect logs for 10 to 15 minutes. For more information about how to collect the logs, see Collecting logs. After you collect the logs, open a support case with IBM Support and attach the logs.

ERR-MIST-401: Authentication Failed due to Invalid Org ID or API Token / ERR-MIST-403: Permission Denied – Access Blocked

Symptom
When the system tries to authenticate with the Mist cloud API using an invalid organization ID or a missing, expired, or deleted API token, the messages ERR-MIST-401: Authentication Failed due to Invalid Org ID or API Token or ERR-MIST-403: Permission Denied – Access Blocked are displayed. These messages can also appear during the following operations:
  • Initial integration setup.
  • Scheduled data pulls.
  • Validation of site or device contexts through the API.
Cause
This issue occurs due to one or more of the following reasons:
  • The organization ID is incorrect, mistyped, or does not exist.
  • The API token is missing, malformed, expired, or revoked.
  • The organization ID in the Mist dashboard does not match the token that is used, or the token does not belong to that organization.
  • The API token is deleted from the Mist dashboard after the integration is configured.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify the integration status in Integration Manager. If the status shows Warning or Failed, enable debug logging and review the collector agent logs. For more information about how to view the logs, see Collecting logs.
  2. Verify the organization ID.
    1. Verify that the organization ID that you provided in SevOne matches the organization ID displayed in your Mist dashboard.

    2. To view the organization ID that your Mist API token is associated with, run a command like this.

      curl -v -H "Authorization: Token <api-key>" https://<mist-url>/api/v1/self

      The following sample output is displayed.

      {
    "privileges": [
        {
            "scope": "org",
            "org_id": "xx-xx-xx-xx-xx",
            ...
        }
    ]
}

      Verify that the organization ID displayed in the output matches the organization ID that you used in SevOne.

If the issue persists, open a support case with IBM Support and attach the collector agent logs.

ERR-MIST-400: Bad Request – Invalid API Syntax or Parameters / ERR-MIST-404: Resource Not Found

Symptom
When the Mist cloud API receives an invalid request, the messages ERR-MIST-400: Bad Request – Invalid API Syntax or Parameters or ERR-MIST-404: Resource Not Found are displayed. These messages appear during the following situations:
  • The request contains syntax errors or violates required parameters.
  • The request includes incorrect query values, unsupported fields, or invalid pagination parameters.
  • The requested resource does not exist or is deleted.
  • When querying specific site IDs, device IDs, or organization-scoped endpoints.
Cause
This issue occurs due to one or more of the following reasons:
  • Malformed query string. For example, non-integer values for limit or page.
  • Endpoint path is syntactically correct but improperly constructed.
  • Missing or incompatible fields in the query string.
  • Usage of fields that are not allowed for the requested resource.
  • Mistyped or invalid site ID, organization ID, or device ID.
  • The requested object no longer exists or deleted.
  • Requesting from the wrong organization context.
Solution
To resolve this issue, perform the following workaround steps:
  1. verify that the organization ID that you provided in SevOne matches the organization ID displayed in your Mist dashboard. Check the following parameters for typos or errors:
    • Admin portal URL
    • API token
    • Organization ID
  2. Enable debug logging and collect logs for 10 to 15 minutes. For more information about how to collect the logs, see Collecting logs. After you collect the logs, open a support case with IBM Support and attach the logs.

ERR-MIST-429: Rate Limit Exceeded

Symptom
If the Mist API rate limit is exceeded, the system displays the message ERR-MIST-429: Rate Limit Exceeded. The API response includes a Retry-After header that specifies how long you must wait before sending another request.
Cause
This issue occurs due to one or more of the following reasons:
  • Excessive polling or frequent batch API calls within a short time window.
  • Sharing an API token across multiple collectors or services.
Solution
To resolve this issue, create a new API token in the Mist dashboard and update the integration device with the new token. For more information, see Create API Tokens.

ERR-MIST-5xx: Mist Server Error

Symptom
When an internal error, including infrastructure failures, timeouts, gateway errors, or internal service crashes, occurs in the Mist server, the message ERR-MIST-5xx: Mist Server Error is displayed.
Cause
This issue occurs due to one or more of the following reasons:
  • Mist backend systems are under maintenance or experiencing high load.
  • An internal error occurred while processing the request.
  • The API endpoint is temporarily unavailable.
Solution
To resolve this issue, perform the following workaround steps:
  1. Escalate the issue to Juniper Mist Support if it persists or is critical.
  2. Enable debug logging and collect logs for 10 to 15 minutes. For more information about how to collect the logs, see Collecting logs. After you collect the logs, open a support case with IBM Support and attach the logs.

ERR-MIST-UNEXPECTED-STATUS-CODE: Unknown or Unhandled Status Code

Symptom
When the system encounters an HTTP status code that is not explicitly handled, the message ERR-MIST-UNEXPECTED-STATUS-CODE: Unknown or Unhandled Status Code is displayed. The fallback applies to any status code other than 200, 400-429, and 5xx.
Cause
This issue occurs due to one or more of the following reasons:
  • Mist returned a non-standard HTTP status code.
  • API behavior changed or a new version is introduced.
  • Unexpected redirect, HTTP 418, or a custom Mist response.
Solution
To resolve this issue, perform the following workaround steps:
  1. Enable debug logging and collect logs for 10 to 15 minutes. For more information about how to collect the logs, see Collecting logs. After you collect the logs, open a support case with IBM Support and attach the logs.
  2. Compare the response with Mist API Reference to identify any newly introduced codes or behaviors.
  3. Escalate the issue to Juniper Mist Support if the problem persists or is critical.

ERR-MIST-SITE-001: Failed to Unmarshal Site List Batch

Symptom
When the Mist API returns data that can't be decoded into the expected site structure, the message ERR-MIST-SITE-001: Failed to Unmarshal Site List Batch is displayed. The GetSitesList method stops processing the current batch, but subsequent batches might still load.
Cause
This issue occurs due to one or more of the following reasons:
  • Mist API response schema changed, fields are missing, or JSON is malformed.
  • Partial site data returned due to a network interruption or timeout.
  • Mist organization includes newly added fields that are not supported by the current collector version.
Solution
To resolve this issue, perform the following workaround steps:
  1. Retry the collection after a few minutes. The issue might be transient.

  2. Verify the API response format using the Mist Developer Console or tools such as Postman.

    • API URL can be either api.ac2.mist.com or api.mist.com.
    • To determine the correct API endpoint for your organization, check the address bar in the Juniper Mist portal. For more information, see API Endpoints and Global Regions.

    For example, run a command like this:

    curl -X GET -H "Authorization: Token <api-key>" https://<api_url>/api/v1/orgs/<org-id>/sites
  3. Confirm that the Mist API token has the read:sites permission.
  4. If the issue persists, open a support case with IBM Support and attach the following details:
    • Full error message and timestamp.
    • Collector version (NMS collector-Mist build number).
    • A redacted example of the Mist API response payload.

ERR-MIST-INIT: Error in NewAppConfig

Symptom
When the collector can't load or parse the config.yaml configuration file during startup, the message ERR-MIST-INIT: Error in NewAppConfig is displayed. If the configuration file can't be processed, the collector does not start.
Cause
This issue occurs due to one or more of the following reasons:
  • The configuration file is missing or unreadable.
  • YAML syntax is invalid or field names are misconfigured.
  • Configuration parameters are unsupported or deprecated.
  • File permissions are incorrect, or the directory path is misaligned in the container or deployment.
Solution
To resolve this issue, perform the following workaround steps:

  1. Verify that the config.yaml configuration file exists in the correct directory and is readable by the collector process.

    The Mist collector configuration file is located at /config/collectors/mist/<org_name>/config.yaml. If multiple integrations or organizations are onboarded, a separate configuration file is created for each.

  2. Validate the YAML file integrity by using a linter. For example, yamllint.
  3. Review configuration paths for spelling and make sure that the hierarchy matches expected fields such as system, nms, and mist.
  4. Restart the collector after correcting configuration issues.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • A sanitized copy of the config.yaml file.

ERR-MIST-INIT: Error Initializing Agents

Symptom
When the collector fails to initialize one or more core agents, such as DeviceStatsAgent, CacheBootstrapAgent, MetadataAgent, ObjectTypeInstallerAgent or UpdateIntegrationStatusAgent, the message ERR-MIST-INIT: Error Initializing Agents is displayed.
Cause
This issue occurs due to one or more of the following reasons:
  • Mist API credentials are missing or incorrect in the configuration.
  • Redis service is unavailable or misconfigured (sharedCache dependency).
  • NMS connectivity or authentication issues.
  • Required agent dependencies are not installed or are corrupted.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify Mist API credentials in the config.yaml configuration file, including the organization ID.
  2. Validate network connectivity from the collector to:
    • Mist API endpoint, that is, api.mist.com.
    • SevOne NMS endpoint for device and object transport.
  3. Check the Mist plugin logs to confirm whether the integration is fetched correctly. If needed, set the log level to debug in the config.yaml configuration file for the specific integration and review the agent logs for errors. For more information, see Collecting logs.
  4. Restart the collector pod.
  5. If the issue persists, open a support case with IBM Support and attach the logs and configuration parameters.

ERR-MIST-INIT: Error in Collector.Bootstrap

Symptom
When the collector core process can't bootstrap properly, the message ERR-MIST-INIT: Error in Collector Bootstrap is displayed. This condition usually indicates that the process failed to register or initialize all available agents.
Cause
This issue occurs due to one or more of the following reasons:
  • Configuration mismatch between CollectorName and registered agents.
  • Startup race condition between Redis cache and NMS connections.
  • Network proxy blocking external API registration.
Solution
To resolve this issue, perform the following workaround steps:
  1. Review collector logs to identify which agent failed to register.
  2. If you use a corporate proxy, verify that the proxy settings are correctly applied by using environment variables such as http_proxy, https_proxy, or no_proxy.
  3. Make sure that all agent modules are loaded without version mismatches. Cross-check image tags or build versions.
  4. Stop and restart the collector after you confirm that network dependencies such as Mist API, Redis, and NMS are stable.

  5. If the collector remains in a Bootstrap failure state, open a support case with IBM Support. Attach the collector startup logs, and agent initialization summary message.

    To collect the logs, run a command like this:

    podman logs --tail=300 nms-collections-mist-collector > /root/bootstrap_failure.log 2>&1

    A new file named bootstrap_failure.log is created in the root directory.

ERR-MIST-INIT: Error in DeviceStatsAgent or MetadataAgent

Symptom
When you load V2 agents that are designed for high-volume data collection from Mist, the message ERR-MIST-INIT: Error in DeviceStatsAgent or MetadataAgent is displayed.
Cause
This issue occurs due to one or more of the following reasons:
  • Mist API permissions are insufficient to retrieve device statistics or metadata.
  • Large organization datasets cause API pagination or rate-limit errors.
  • Redis cache is expired or inaccessible during the initial data load.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify the Mist API token permissions. Make sure that the API token includes the permissions read:devices, read:orgs, and read:sites.
  2. Monitor the Mist API usage and verify that the request quotas are not exceeded. Use Mist Status Dashboard to monitor the API usage.
  3. If collection remains stalled or the agent fails repeatedly, open a support case with IBM Support and attach the following details:
    • Error log showing the failure message.
    • Organization ID and API token (do not share the secret).

    • Approximate number of devices and sites in the organization.

      You can retrieve device and site counts using the Mist API. Run a command like this: 
      curl -X GET \
 --url 'https://<api_url>/api/v1/orgs/<org_id>/inventory/count'  \
 -H 'Authorization: Token <api_token>' \
 -H 'Accept: application/json, application/vnd.api+json' \
 -d 'type=ap' \
 -d 'distinct=status' \
 -d 'limit=100'
      • API URL can be either api.ac2.mist.com or api.mist.com.
      • To determine the correct API endpoint for your organization, check the address bar in the Juniper Mist portal. For more information, see API Endpoints and Global Regions.

ERR-MIST-INIT: Error in CacheBootstrapAgent

Symptom
When the collector failed to populate or reload the Redis cache from persistent data, the message ERR-MIST-INIT: Error in CacheBootstrapAgent is displayed. This prevents stateful data recovery during restart.
Cause
This issue occurs due to one or more of the following reasons:
  • Redis connectivity issue (unreachable or authentication failure).
  • Cache file corruption in /config/collector/mist/data/.
  • Insufficient file system permissions or missing mount path.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify the Redis service health. Run a command like this: 
    redis-cli ping
  2. Check collector mount path. Verify that the path /config/collector/mist/data/ exists and has write permissions.
  3. Make sure that the Redis credentials in the config.yaml configuration file match the server ACLs.
  4. Clear the stale lock file located at /config/collector/mist/data/nms_device_cache.lock, then restart the collector.
  5. If cache repopulation continues to fail, open a support case with IBM Support and attach the Redis logs and the collector configuration details.

ERR-MIST-INIT: Error in Collector.RunAgentOnDemand

Symptom
When an individual agent fails to execute through RunAgentOnDemand, the message ERR-MIST-INIT: Error in Collector.RunAgentOnDemand is displayed. RunAgentOnDemand is typically used for testing or for manual data collection runs.
Cause
This issue occurs due to one or more of the following reasons:
  • Invalid agent name passed through the CLI or orchestration layer.
  • Missing dependencies for the selected agent. For example, Mist client or cache.
  • Misconfigured runtime variables during custom agent invocation.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify the agent name in the CLI syntax. Make sure correct spelling and case sensitivity. 
    ./mist_collector --run-agent=DeviceStatsAgent
  2. Confirm that the corresponding agent configuration exists in the config.yaml configuration file.
  3. Collect CLI output and logs for the session.
  4. If on-demand runs fail for multiple agents, open a support case with IBM Support to investigate any underlying API or module dependency issues.

Shutdown or Signal Handling Issues

Symptom
The collector might hang or fail to stop gracefully when it receives termination signals such as SIGINT or SIGTERM.
Cause
This issue occurs due to one or more of the following reasons:
  • Background worker threads or agents do not exit as expected.
  • Communication with Redis or Mist is interrupted during shutdown.
  • Resource cleanup is incomplete due to process privilege restrictions.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the collector process owner (typically sevone) has the required permissions.
  2. Allow up to one minute for a graceful shutdown before you force termination.
  3. If the process remains stuck, run a manual cleanup. 
    pkill -f mist-collector
  4. Check the logs in /log/mist_collector/ for messages such as Error in Shutdown() while terminating.
  5. If shutdown failures occur frequently, open a support case with IBM Support and attach the logs and timestamps.

ERR-MIST-OT: Object Type Installation Failures

Symptom
When the ObjectTypeInstallerAgent fails to create required object types or indicators in NMS, devices might be created without the proper object structure to hold metrics. The message ERR-MIST-OT: Object Type Installation Failures is displayed.
Cause
This issue occurs due to one or more of the following reasons:
  • The logs show messages such as ERR-MIST-OT: Failed to create object type or ERR-MIST-OT: Failed to create indicator.
  • NMS connectivity or credentials are incorrect.
  • The NMS user does not have permissions to create object types and indicators.
  • The required object types already exist in NMS but have different definitions.
Solution
To resolve this issue, perform the following workaround steps:
  1. Restart the collector to retry object type installation: 
    podman restart nms-collections-mist-collector
  2. If the issue persists, open a support case with IBM Support and attach the agent logs. For more information about how to collect the agent logs, see Collecting logs.

ERR-MIST-META: Device ID Resolution Failures

Symptom
When the MetadataAgent fails to map Mist device UUIDs to NMS device IDs, the message ERR-MIST-META: Device ID Resolution Failures is displayed. This prevents metadata from being populated.
Cause
This issue occurs due to one or more of the following reasons:
  • Devices are not yet created in NMS by the DeviceStatsAgent.
  • Cache misses when resolving device-to-ID mappings.
  • Timing delays between DeviceStatsAgent and MetadataAgent operations.
  • Device name changes leading to mapping mismatches.
  • Redis cache issues that affect stored device mappings.
Solution
To resolve this issue, perform the following workaround steps:
  1. Make sure that the DeviceStatsAgent completes before the MetadataAgent runs.
  2. Verify that the devices are created in NMS.
  3. Allow additional time for initial device creation before expecting metadata.

  4. Check Redis for device mapping keys. Run commands like these:

    podman exec -it nms-nms-redis redis-cli
KEYS "*mistdata:nms:device*"

    The following sample output is displayed:

    1) "IBM SevOne RTP Lab:mistdata:nms:device_id_by_uuid:00000000-0000-0000-1000-xxxxxx"
2) "IBM SevOne RTP Lab:mistdata:nms:device_id_by_uuid:00000000-0000-0000-1000-xxxxxx"
  5. If the issue persists, restart the collector to rebuild device mappings.

ERR-MIST-002: Network Failure During Mist API Call

Symptom
The collector logs the message ERR-MIST-002: Network failure during Mist API call when it cannot reach the Mist API endpoint.
Cause
This issue occurs due to one or more of the following reasons:
  • DNS resolution failure.
  • TLS certificate validation failures.
  • Network connectivity issues between the collector and the Mist API.
  • Proxy or firewall restrictions blocking outbound API access.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the configured Mist API host is reachable from the collector environment.
  2. Confirm that DNS resolution for the Mist API hostname is working as expected.
  3. Check whether TLS inspection, certificate trust, proxy configuration, or firewall rules are blocking outbound API traffic.
  4. If a proxy is configured, verify that the proxy settings and credentials are correct. For more information, see Proxies.
  5. Retry the operation after network connectivity is restored.
  6. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The configured Mist API host value.
    • Relevant proxy or network configuration details.

ERR-MIST-ORG-DEV-001: Failed to Fetch Organization Device Stats Page

Symptom
The collector logs ERR-MIST-ORG-DEV-001: iterator next failed while fetching paged organization device statistics from Mist.
Cause
This issue occurs when a paged device statistics request fails before the response payload can be processed.
Solution
To resolve this issue, perform the following workaround steps:
  1. Review the integration logs for related entries that appear immediately before or after this message to identify the underlying Mist API failure.
  2. Check whether the issue is caused by network connectivity, authorization, or API throttling.
  3. Verify that the Mist API token and organization configuration are correct.
  4. If a proxy is configured, verify that the proxy settings and credentials are correct. For more information, see Proxies.
  5. Retry the inventory collection after the underlying API issue is resolved.
  6. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The affected organization ID.
    • The approximate time when the failure occurred.

ERR-MIST-ORG-DEV-002: Failed to Unmarshal Device Stats Page

Symptom
The collector logs ERR-MIST-ORG-DEV-002: unmarshal device stats page failed when the Mist device statistics response cannot be parsed.
Cause
This issue occurs due to one or more of the following reasons:
  • Malformed or incomplete JSON returned by the Mist API.
  • Schema changes in the Mist API response payload.
Solution
To resolve this issue, perform the following workaround steps:
  1. Retry the operation to determine whether the issue is temporary.
  2. Verify that the Mist API returns a valid and complete response.
  3. Check whether a proxy, gateway, or security device is modifying the API response.
  4. Confirm that the collector is connected to the correct Mist API endpoint.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • A sanitized sample of the API response, if available.

ERR-MIST-DEVICE-CREATION: Failed to Get Organization Device Stats

Symptom
The collector logs ERR-MIST-DEVICE-CREATION: failed to get org device stats during device creation initialization.
Cause
This issue occurs when the device creation workflow cannot retrieve Mist inventory device statistics.
Solution
To resolve this issue, perform the following workaround steps:
  1. Review related Mist API log messages to identify the underlying cause of the inventory retrieval failure.
  2. Verify network connectivity between the collector and the Mist API.
  3. Confirm that the API token, organization ID, and API host are configured correctly.
  4. Check whether the Mist API is rate limiting or rejecting requests.
  5. Wait for the next scheduled collection cycle or manually trigger a collection to verify the issue is resolved.
  6. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The config.yaml file.

ERR-MIST-DEVICE-CREATION: Failed to Bulk Create Devices

Symptom
The collector logs ERR-MIST-DEVICE-CREATION: failed to bulk create devices when sending device creation requests to NMS.
Cause
This issue occurs due to one or more of the following reasons:
  • NMS rejected one or more device creation requests.
  • Duplicate device names exist in NMS.
  • Payload validation failed for one or more devices.
Solution
To resolve this issue, perform the following workaround steps:
  1. Check whether devices with the same names already exist in NMS.
  2. Verify that the device information being synchronized from Mist is valid and complete.
  3. Verify that the target NMS environment is available and accepting device creation requests.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after correcting any duplicate or invalid device entries.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The list of affected device names, if available.

ERR-MIST-DEVICE-CREATION: Failed to Rename Device in NMS Using BulkEditDevice

Symptom
The collector logs ERR-MIST-DEVICE-CREATION: failed to rename device in NMS using BulkEditDevice when an existing NMS device cannot be updated.
Cause
This issue occurs when the rename or IP patch request fails in NMS.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the target device still exists in NMS.
  2. Verify that the updated device name and IP address do not conflict with another device already present in NMS.
  3. Check whether naming rules or IP validation requirements in NMS are preventing the update.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after correcting the conflicting values.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The affected device name and IP address.

ERR-MIST-SITE-DEVICE-METADATA-002: Failed to Get Sites List From Mist API

Symptom
The collector logs ERR-MIST-SITE-DEVICE-METADATA-002: failed to get sites list from Mist API during site metadata extraction.
Cause
This issue occurs when the site metadata workflow cannot retrieve the Mist site inventory.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the configured Mist organization ID is correct.
  2. Verify that the API token has permission to read site information for the organization.
  3. Check network connectivity between the collector and the Mist API.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after resolving any authorization or rate-limit issues.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The config.yaml file.

ERR-MIST-SITE-DEVICE-METADATA-015: Failed to Update Metadata Batch for Site Devices

Symptom
The collector logs ERR-MIST-SITE-DEVICE-METADATA-015: Failed to update metadata batch for site devices while sending metadata updates to NMS.
Cause
This issue occurs when one or more metadata update requests fail during batch submission to NMS.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the affected site devices exist in NMS.
  2. Verify that the required metadata schema is available in NMS.
  3. Check whether required metadata values are missing or invalid.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after correcting the identified issue.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The affected site names or device names.
    • The integration device ID and organization ID.

ERR-MIST-SLE-STATS-001: Failed to Get SLE Stats From Mist API

Symptom
The collector logs ERR-MIST-SLE-STATS-001 when it cannot retrieve Wi-Fi, Wired, or WAN SLE statistics from Mist.
Cause
This issue occurs when one of the SLE statistics API calls fails before the data can be processed.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the API token and organization ID are correct and authorized to access SLE statistics.
  2. Check network connectivity to the Mist API.
  3. Determine whether the failure is related to API throttling or a temporary Mist service issue.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after correcting the identified issue.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The affected organization ID.
    • The approximate time when the SLE statistics request failed.

ERR-MIST-SLE-STATS-003: Failed to Get Site List From Mist API

Symptom
The collector logs ERR-MIST-SLE-STATS-003: failed to get site list from Mist API while building SLE statistics data.
Cause
This issue occurs when the SLE statistics workflow cannot retrieve the site list needed to map SLE data to site names.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the organization ID configured for the collector is correct.
  2. Verify that the API token can access site information for the organization.
  3. Check connectivity to the Mist API and verify that requests are not being rate limited.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after correcting the identified issue.
  5. If the issue persists, open a support case with IBM Support and attach the full log snippet.

ERR-MIST-UPDATE-INTEGRATION-009: Failed to Update Plugin Device Status

Symptom
The collector logs ERR-MIST-UPDATE-INTEGRATION-009: Failed to update plugin device status while writing integration status back to NMS.
Cause
This issue occurs when the final integration status update request to NMS fails.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the NMS platform is reachable from the collector.
  2. Verify that the integration device ID is valid and still exists in NMS.
  3. Check whether there are temporary NMS availability or API issues.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after connectivity or platform issues are resolved.
  5. If the issue persists, open a support case with IBM Support and attach the full log snippet.

ERR-MIST-META-EXTRACT: SetStreamingData Failed

Symptom
The collector logs ERR-MIST-META-EXTRACT: SetStreamingData failed during metadata extraction.
Cause
This issue occurs when metadata extract streaming data cannot be queued for downstream processing.
Solution
To resolve this issue, perform the following workaround steps:
  1. Restart the collector to clear any temporary pipeline or memory condition.
  2. Verify that device inventory data is being collected before the metadata phase begins.
  3. Check for related errors in the same log window that might indicate upstream data collection failures.
  4. Wait for the next scheduled collection cycle or manually trigger a collection after the upstream issue is corrected.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • Related log entries from the same collection cycle.

ERR-MIST-META-TRANSFORM: Invalid OrgPageDeviceData

Symptom
The collector logs ERR-MIST-META-TRANSFORM: invalid OrgPageDeviceData during metadata transformation.
Cause
This issue occurs when the metadata transform phase receives data in an unexpected format.
Solution
To resolve this issue, perform the following workaround steps:
  1. Restart the collector to determine whether the condition is temporary.
  2. Check for earlier log messages indicating inventory collection or extract-stage failures.
  3. Verify that the collector completed the earlier processing stages before metadata transformation started.
  4. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • Related log entries from the same collection cycle.
    • The organization ID and integration device ID.

ERR-MIST-META-LOAD: Invalid TransformStreamingData

Symptom
The collector logs ERR-MIST-META-LOAD: invalid TransformStreamingData during the metadata load phase.
Cause
This issue occurs when the metadata load stage receives malformed or unexpected transform output.
Solution
To resolve this issue, perform the following workaround steps:
  1. Restart the collector.
  2. Review earlier log entries to identify metadata extract or transform failures that cause invalid load input.
  3. Verify that the metadata processing completed in the earlier stages of the same run.
  4. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • Related metadata errors from the same run.
    • The organization ID and integration device ID.

ERR-MIST-DEVICE-DESC-EXTRACT: SetStreamingData Failed

Symptom
The collector logs ERR-MIST-DEVICE-DESC-EXTRACT: SetStreamingData failed while enqueueing device description updates.
Cause
This issue occurs when device description extract data cannot be passed into the downstream pipeline.
Solution
To resolve this issue, perform the following workaround steps:
  1. Restart the collector.
  2. Review earlier log entries to identify metadata extract or transform failures that cause invalid load input.
  3. Verify that the metadata processing completed in the earlier stages of the same run.
  4. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • Related metadata errors from the same run.

ERR-MIST-DEVICE-DESC: Failed to Update Device Description in NMS

Symptom
The collector logs ERR-MIST-DEVICE-DESC: failed to update device description in NMS when writing the generated Mist model description to NMS.
Cause
This issue occurs when the partial device update request fails for the target NMS device.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that the affected device still exists in NMS.
  2. Verify that the NMS platform is reachable and accepting update requests.
  3. Wait for the next scheduled collection cycle or manually trigger a collection to determine whether the issue istemporary.
  4. Check whether the affected device has conflicting or incomplete data in NMS.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • The affected device name or identifier.

WAR-MIST-DEVICE-STATS-001: Failed to Unmarshal Device Stats Page

Symptom
When the agent could not parse a device stats page received from Mist because of an invalid or unexpected data structure, the message WAR-MIST-DEVICE-STATS-001: Failed to Unmarshal Device Stats Page is displayed. The entire page is skipped, but device collection continues for subsequent pages.
Cause
This issue occurs due to one or more of the following reasons:
  • The Mist API returned unexpected data or an incomplete or broken page.
  • A temporary network issue caused a truncated HTTP response.
  • The API endpoint behavior changed, such as new or deprecated fields being present.
Solution
To resolve this issue, perform the following workaround steps:
  1. Restart the collector and retry the collection. The issue might be transient.
  2. Verify that other Mist API calls are working and that device stats are visible in the Mist dashboard.
  3. Check the Mist service status for any known outages or data issues.
  4. If the issue persists for multiple collection cycles, open a support case with IBM Support and attach the agent logs. For more information about how to collect the agent logs, see Collecting logs.

WAR-MIST-DEVICE-STATS-002: Failed to Unmarshal Device Type Probe

Symptom
When the agent can't detect the device type when parsing a device record from Mist, the message WAR-MIST-DEVICE-STATS-002: Failed to Unmarshal Device Type Probe is displayed. The affected record is skipped.
Cause
This issue occurs due to one or more of the following reasons:
  • A malformed or incomplete device record is received from Mist.
  • A Mist API or device firmware bug resulted in a missing or empty type field.
  • An unexpected new device type is introduced that is not in the allowed list. For example, ap, gateway, switch.
Solution
To resolve this issue, perform the following workaround steps:
  1. Make sure that all devices in the Mist organization are healthy and online. Log in to the Mist dashboard and go to Access Points in the left navigation pane.
  2. If new device types are recently added to the Mist platform, verify that your collector supports them.
  3. If the issue persists, open a support case with IBM Support and attach a sample of the raw Mist API response for analysis.

WAR-MIST-DEVICE-STATS-003: Failed to Unmarshal Access Point Device

Symptom
When the agent detects a device of type ap but can't parse its detailed statistics record, the message WAR-MIST-DEVICE-STATS-003: Failed to Unmarshal Access Point Device is displayed. The device is skipped for the current collection cycle.
Cause
This issue occurs due to one or more of the following reasons:
  • The response contained incomplete, truncated, or corrupted Access Point data.
  • The Mist API format changed or a field was renamed.
  • The device sent malformed data because of a firmware or configuration issue.
Solution
To resolve this issue, perform the following workaround steps:
  1. Confirm that the Access Point is responsive, and runs on the latest firmware.
  2. Review the Mist API documentation for changes related to Access Point statistics. For more information, see Mist API Reference.
  3. If the issue persists, open a support case with IBM Support and attach the API response.

WAR-MIST-UPDATE-INTEGRATION: Integration ID Issues

Symptom
The UpdateIntegrationStatusAgent updates the integration status in NMS based on collection results. When the agent can't find a valid integration ID to update, the message WAR-MIST-UPDATE-INTEGRATION: Integration ID Issues is displayed.
Cause
This issue occurs due to one or more of the following reasons:
  • The integration_id is missing in the configuration file.
  • The integration is not properly created in NMS.
  • The configuration file format is incorrect.
  • The integration is deleted or changed in NMS.
Solution
To resolve this issue, perform the following workaround steps:
  1. Make sure that the integration_id parameter is included in the config.yaml configuration file if it is not present. 
    ...
nms:
  api:
    distribution_peer_list: [0]
    host: 127.0.0.1
    insecure_tls_connection: true
    m2m_client_id: mist-collector
    m2m_client_secret: <client-secret>
    timeout: 60s
    integration_id: <integration-id>
  run_agents_immediately_and_exit_collector: true
...
  2. Restart the collector after you fix the configuration.
  3. If needed, create a new integration in NMS and update the configuration.
  4. If the issue persists, open a support case with IBM Support and attach the agent logs. For more information about how to collect the agent logs, see Collecting logs.

WRN-MIST-SNMP-001: Failed to Fetch SNMP Configuration

Symptom
The collector logs WRN-MIST-SNMP-001: Failed to fetch SNMP config from API, SNMP will be disabled as a warning when SNMP-configured devices are found in the Mist Portal.
Cause
This issue occurs when the collector cannot retrieve SNMP plugin configuration for the integration device.
Solution
To resolve this issue, perform the following workaround steps:
  1. Verify that SNMP is enabled and configured for the integration in NMS.
  2. Confirm that all required SNMP configuration fields are complete and valid.
  3. Check that the integration device is reachable and that the collector can retrieve plugin configuration.
  4. If SNMP monitoring is required, update the SNMP configuration and rerun the collector.
  5. If the issue persists, open a support case with IBM Support and attach the following details:
    • The full log snippet.
    • A sanitized export or screenshot of the SNMP configuration.