Edge Manager Q1 2017

These are the new features and known and resolved issues for Edge Manager.

Note: US West users must use Edge Manager with Predix Machine version 17.1.0 or later.

New Features

Edge Manager contains the following new features:

BOM Management
You can now define a BOM and upload it to Edge Manager. The BOM lists all the software packages and applications, with dependencies among them, that are installed on a GE Digital-provisioned device.
Edge Manager BOM management includes:
  • Import a BOM to Edge Manager.
  • The ability to install BOMs on devices.
  • View a list of BOMs that are currently installed on the device.

For more information, see c_About_BOM_Lists.html#concept_09b9d41c-79fa-4c1d-b7b2-58aa7afbb80e.

Alerts
You can now view and filter alerts for managed devices.

For more information, see c_About_Alerts.html#concept_5c006910-8f28-4472-86c0-39428a7d6e64.

Bluetooth and WiFi Status
You can now see Bluetooth and WiFi connection status for a device on the Device Details page.

For more information, see Viewing the Device Summary.

VPN Management
You can start and stop VPN management on a device using Edge Manager. You can also set the log verbosity for the VPN connection.
Time Zone Setting
Ability to select Local or UTC time as a global setting.

For more information, see Setting the Time Format.

Add Additional Notes for Packages
You can now add additional notes for packages when you upload them to the Edge Manager repository.
APM and Edge Manager Integration
Edge Manager integration with APM allows users with an APM tenant to use Edge Manager and vice versa.

With this new feature, you can enroll devices with Edge Manager and use the APM Time Series instance to ingest data. All users and devices in Edge Manager are separated by tenancy.

This feature works with both certificate and OAuth based enrollment.

Note: For OAuth, when a device is created, the device ID must be unique across all tenants. If the device ID is not unique, adding the device causes an error.
Note: Contact the APM Service Ops team to get a tenant provisioned.

Resolved Issues

The following issues have been resolved in this release:

  • The issue where devices become unreachable in environments with a large number of devices has been fixed.

Known Issues

This release contains the following known issues:

BOM does not support .config files
BOM does not support .config. This means you cannot use BOM to upgrade a machine to new features.
Workaround: Upload configurations to Edge Manager as an “application” so the BOM can use it.
  • Issues with Firefox And Chrome browsers:
    • There is a plug-in conflict that causes the browser to crash (GE internal only) when downloading a file, or when viewing the output of a command.

      The same plug-in conflict causes an error when uploading a large file (hundreds of MB).

      Workaround:

      For Firefox: Run Firefox in Safe mode to disable Firefox plug-ins.

      For Chrome:
      1. Run Chrome in Incognito mode.
      2. In Settings > Extensions, if you have the DGExtension, ensure that it is disabled by unselecting the checkbox.
  • Operations start, execution start, and elapsed time display differently for the top level versus operation details when there is only one operation. This is due to how the summary is calculated versus how the operation detail is calculated.
  • You can create groups with the same name as an existing group and attach it to the same parent.

    Workaround: To avoid creating groups with duplicate names, verify that there are no existing groups with the same name.

  • You cannot save a filter if the name has more than 63 characters.

    Workaround: Use fewer than 63 characters in filter names.

  • If a device is placed in inventory but not enrolled, and software or configuration packages are sent to that device, and one of the Edge Manager services fails and needs to be restarted, then those software or configuration packages may need to be redeployed to that device.
  • There is a known issue with deleting a group with a large number (over 5,000) of devices. Do not create such large groups, or move devices incrementally out of large groups so you can delete the group.