Updated on: 04 February 2020
VMware Pulse IoT Center | Version 2.0.2 | On-Premise GA Release
What's in the Release NotesThe release notes cover the following topics:
- About VMware Pulse IoT Center
- What's New in this Release
- Gateways Certified for Use
- Before You Begin
- Known Issues
About VMware Pulse IoT Center
VMware Pulse IoT Center is a secure, enterprise-grade, edge infrastructure and IoT device management solution that provides visibility and control over all IoT use cases. It helps companies to onboard, configure, monitor, manage and secure IoT devices and infrastructure. The solution enables IT and Operational Technology (OT) to simplify device management and operationalize IoT use cases quickly by reducing the complexity of managing all the heterogeneous edge and IoT systems in one place.
VMware Pulse IoT Center Version 2.0 includes the following new features and capabilities by their feature category:
- Onboard certified gateways and connected devices securely to the Service Offering through a low-touch enrollment process
- Configure gateways, connectivity to gateways, and application/containers on gateways
- Setup of device properties and metrics through device template
- Define metrics collection frequency and batch size
Monitor and Troubleshoot IoT Infrastructure
- Set up alert definition and notification through email or REST API
- Monitor device health and detect abnormalities
- Troubleshoot through system log and audit log
- Act by sending supported commands to devices
Manage IoT Infrastructure
- Enable policy-driven over-the-air software lifecycle management
- Manage the software and security patch update approval process
- View alerts, metrics trends, and granular status of software update execution on the dashboard
- Visualize the representation of the parent-child topology
- Manage certified heterogeneous devices and gateways with different hardware, operating systems, and communication protocols
- Role-based user access according to organizations and use cases.
What's New in this Release
Release 2019.16 - Released February 04, 2020
VMware Pulse IoT Center Server Version 126.96.36.1993 | VMware Pulse IoTC Agent Version 15426927
- Easily integrate your Single Sign On (SSO)
- You can now use the SAML SSO to authenticate user access.
- Simply provide OTA updates to new things and sub-organizations
- Perform OTA updates on ‘Thing devices’ that are enrolled after the campaign starts.
- OTA Campaigns now support Organization hierarchy.
- Richer and more convenient Advanced Search
- You can now search across multiple templates in Advanced Search.
- Organization is now visible in Advanced Search results.
- Automatic update of device lists for Alert Definitions
- Periodic background evaluation of search filter criteria to automatically add or remove devices in device list based Alert Definitions.
- Robust Load Balancing with High Availability (HA)
- You can now deploy Load Balancer in Active-Passive Mode to enable HA.
Gateways Certified for Use
The VMware Compatibility Guide lists the Gateways and Edge Systems that are certified for use with VMware Pulse IoT Center:
- Edge Gateways: https://www.vmware.com/resources/compatibility/vcl/edgeiot.php
- Embedded Systems: https://www.vmware.com/resources/compatibility/vcl/embeddediot.php
Before You Begin
Before you begin using VMware Pulse IoT Center, ensure that you meet the following requirements:
Procure and Manage
- You must receive an invitation from the VMware Pulse IoT Center Service to use VMware Pulse IoT Center cloud hosted environment (SaaS).
- You must have a valid VMware ID to access VMware's Cloud Services products.
- Set up default user accounts and group accounts for different roles.
- Get the Organization Administrator login credentials for VMware Pulse IoT Center. Follow the VMware Pulse IoT Center Service invitation link and provision an instance for your organization.
- Create roles for various permissions that are suited to your organization. The following roles are created by default, and can be used as a reference:
- Default Administrator
- Monitoring Administrator
- Campaign Administrator
- Gateway Administrator
- Ensure that the Gateways and Edge Systems are certified for use with VMware Pulse IoT Center.
- Install the IoTC Agent package on your gateways: Perform the following steps:
- Log in to the VMware Pulse IoT Center UI.
- From the top right of the home page, click the settings icon and click Downloads.
- Download the IoTC Agent tarball Pulse Agent (x86_64), Pulse Agent (arm), or Pulse Agent (aarch64) to your local system.
- Copy the IoTC Agent tarball to the gateway file system by using SSH.
- Extract the IoTC Agent tarball on the gateway.
- Create a device template using VMware Pulse IoT Center to enroll gateways or thing devices.
Technical Configuration and Code Integration
- Download the Command Line Interface (v2) package management tool from VMware Pulse IoT Center > Downloads.
- Using the Command Line Interface (v2) tool, structure the update packages according to the VMware Pulse IoT Center recommended
- Use the
DefaultClientfile as a binary or code to perform the following operations from the gateway. The
DefaultClientfile is available at:
- Metrics Ingestion
- Edit or Read Properties
- Add Devices
- By default, the
DefaultClientbinary collects the device metrics such as CPU usage and memory usage from the gateway. While creating a template, ensure that you do not remove the CPU-Usage and Memory-Usage metrics that are available in the template by default. Specifically, ensure that you do not change the metrics name and data type.
Known IssuesThe following known issues will be fixed in the upcoming releases.
- The agent config file does not get updated when you delete all the proxy configurations in the template.
After enrolling a gateway, edit the device template with proxy settings and check the agent config file. The proxy settings are updated. When you delete all the proxy settings in the template, the agent config file does not update the changes.
Add a proxy setting with an invalid proxy IP address. This will update the proxy type in the agent config file to NO_PROXY.