Application Management Troubleshooting Tips
Following information provide assistance when working with IoT OD applications.
| Issue | Action |
|---|---|
| The Applications tab is not available in the left menu, and on the device details page, the Applications widget and Applications tab are also not available. | Check if the user has been assigned a Role with Manage Application permission, such as Device Operator-- to access Application Management. |
| Uploading an application fails. | Check the file type and format of the application package. Check that the latest IOx client release is used to package the application. Check if one application is being uploaded at a time. Retry to check if it is a temporary issue. Ensure that the application package size is within the limits as specified in the application upload UI workflow. |
| Changing version of an application fails. | Ensure that the device has sufficient resources required for the new version. Check the current version and transitional status from application instance page or application tab in the device details page. Check if any errors are displayed in the application instance status field. Check the application logs for any initial errors if the new application version fails to launch. Download the tech support bundle and analyze the CAF logs for any issues during the application upgrade or startup. |
| The device is not present in the list of available devices on application installation screen. | Check the event logs to ensure that the onboarding procedure was successful and the application management was enabled on the device successfully. Troubleshoot the application by following these steps: Go to Inventory > Select Network Device Name > Applications. Platform details will appear on the screen. * Try using Refresh IOx. * Resolve the issue mentioned in the Last error on the device field. Retry Refresh IOx. * If the issue continues, use the Tech Support Download option to download the logs from IOx and examine them to identify the problem. |
| Device is visible in Application Management screen, but the state is not Discovered. | Check if the device and IoT OD are connected. Check the device event logs if IPSec tunnel related errors affecting connectivity to the device. Check the Platform Details on the Applications tab of the device details page to see if IOx is running successfully on the device or using "show" commands related to IOx (exact commands will depend on the device type) from the device troubleshooting page. Try to download the Tech support bundle and analyze the CAF logs for any issues in the IOx startup. |
| Device is visible in Application Management screen but the state is not Discovered and the error message in the tool tip indicates Unauthorized or Too many failed login requests please try after some time. | This happens due to a mismatch between the GOS (guest-os) image version and the IOS version and this mismatch happens when there is an error during firmware upgrade due to which the GOS does not get upgraded. Use following commands to verify versions and contact Cisco support to confirm the issue: * Show version * Show platform hyper * Show platform guest-OS Upgrade to one of the latest firmware versions. |
| A blank browser tab results from a client-side failure to download the tech support log bundle. | This happens when the size of the tech support log bundle is very large. The maximum size depends on the available RAM in your computer where the browser is running. Refresh the page and close other applications to free up RAM and try again. |
| During the installation of an application, a device is highlighted in grey and marked as "Incompatible architecture." | This happens when a device is not compatible with the CPU architecture for which the application was developed. For instance, the device supports CPU architecture aarch64, but the application is designed for CPU architecture x86_64. |
| During the installation of an application, a device is highlighted in grey and marked as "Device supports only Cisco-signed applications." | This happens when the application is not Cisco-signed and the device's IOx platform does not support such applications. For instance, IOx runs on device types like IE-3200 but does not support non-Cisco signed applications. |