Fixed Known Issues

This section lists previously-open known issues that are now fixed. Issues closed prior to the previous major release will gradually age out and be removed from this list.

Fixed in this release:

  • When the telemetry data for Edge or Edge services is requested, there will be a lag of approximately 4 minutes in the data being displayed.
  • UI will reflect an delayed update of the Latest Data Session Start and Latest Data Session End fields in the More Information drawer's cellular tab due to the MNO for Vodafone SIMs.
  • When onboarding cellular devices, if multiple APNs are configured for a CSP, internet and messaging services may stop working.

    Workaround: restrict cellular devices to a single APN per CSP.

  • For cellular devices and Cloud Connectors using AT&T service, the ECP UI does not validate between the Network Priority checkbox and compatible APNs. If there is a mismatch, the user could be charged at a higher rate while receiving standard data prioritization. Only the following APNs listed in the UI support Network Priority.
    • ecp.oracle.com (QoS)
    • ecp.t.oracle.com (QoS)
    • nxtgenphone (QoS)

    Workaround: Ensure that the above APNs are not associated with devices where Network Priority is not expected.

  • The Customer filter chip must not be removed from the Cloud Connector or Device Inventory page's Search box.
  • The top 5 applications shown on the Application memory usage graph shown in a Cloud Connector's Overview Tab, are not necessarily the top 5 running on the Cloud Connector itself.
  • On a Device's Application tab, after clicking Sort Ascending or Sort Descending, the application list displays 'There are no applications associated with this device.'
  • Not all Applications added in Hardware Group are reflected in applications tab of associated device.
  • For non-MDM cellular devices with single SIMs, after deactivation, the SIM state according to the MNO is not updated on the UI.
  • Cloud Connectors and Devices assigned to customer tenants may appear in the inventory, even after the tenant is suspended.
  • Monthly and daily warnings for data and SMS usage appear identically on the UI.
  • When using the Add Hardware guided flow, when choosing a target customer to onboard the hardware, the first click is not accepted. Workaround - click the customer name a second time on the drop down value.
  • When navigating to a Cloud Connector's details page from a Satellite Terminal row's Edge Node column on the Satellite Terminals Inventory page, that Cloud Connector's actions are immediately visible on a single line rather than only being accessed by clicking the Actions menu.
  • When MNOs return multiple bearers, the cellular connection is not set up properly.
  • When the browser is set to a relatively small width and the bottom-most bar responsively changes to move all tabs that don't fit under a "..." option, when clicking the hidden tabs from under the "..." option, the redirections to the appropriate pages are incorrect
  • Device details downloads may not include the most recent fields and structure.
  • The top-application-usage API reports a 500 error code on a Resource Type error instead of reporting a 404 error.

Fixed in the previous release:

  • Onboarding multiple MDM-enrolled devices with the same Make and Serial number, an invalid combination, causes the Remaining Battery Charge and Storage Usage in the last 24 hours chart to display incorrectly.

    Workaround: Ensure each onboarded Device has a unique make and serial number pair.

  • After drilling down from the Issues page to a specific issue and navigating with the next/previous buttons, an Affected IoT Device section may incorrectly display on the screen.
  • When placing the mouse over a data point on the Dashboard page's Edge Node Usage graph for satellite data, an incorrect unit for the value displays on the screen.
  • When a SIM card is deactivated, the system ceases to record data, SMS, and voice usage for the inactive period. Consequently, the dashboard charts will reflect "missing days" corresponding to the time when the SIM was inactive. This is evident through gaps or missing data points on the timeline of the charts.
  • For edge nodes where Satellite and Ethernet interfaces are enabled, when both of these interfaces are displayed as disconnected in the interface status column, the Lifecycle and Connectivity state columns may display as Active and Connected respectively.
  • Bulk onboarding of edge nodes that use Satellite for WAN access intermittently fail.
  • Intermittently, after performing a deactivate and wipe operation on MDM managed devices, the devices do not deactivate after the action.
  • The Dashboard's Edge Nodes in Use and Network priority chart does not match corresponding data presented on the Inventory page.
  • The following known issues have been observed against the interactions between ECP and our MNO partners:
    • Due to a lag in MNOs sending ECP usage data, the device overview charts often do not include up-to-date display usage.
    • The last day of the month’s data usage may be excluded from ECP’s reports and dashboards due to MNOs’ lag in sending data. MNO Reports are off by a day and Daily and Monthly usage warnings may not get generated.
    • Daily and monthly data usage warnings may not appear at the end of the day due to some notifications about session usage being received from the MNOs after the session ends (during the next day).
    • Cellular device connectivity state may remain in a connected state for a while even after the mobile device data has or the device itself has been turned off.
    • The device overview graph on a cellular device (IoT Device and Edge Node) may reflect inconsistent data when reviewed day-to-day for Data, SMS, and Voice.

  • On the resize column popup for a column, if you remove the default width and click submit, then width of that column will be zero.

    WorkAround: Enter a proper width in the resize popup and click submit. If a blank value is submitted for any of the column, then manually drag the column's width or can re-submit with proper value.