The number of connected IoT devices is estimated to skyrocket from 8.4 billion in 2017 to over 20 billion in 2020. Enterprises will need a way to manage these devices and analyze their data to drive business decisions and efficiencies.
VMware Pulse IoT Center is an end-to-end IoT management solution that enables OT and IT organizations to onboard, manage, monitor and secure IoT infrastructure.
Scenario to understand the use of Vmware Pulse IOTC
Suppose in a retail shop, CCTV Surveillance Cameras are installed & 20 people entered the shop, however, the surveillance camera application detected only 10 walked by. VMware Pulse IOTC is not the application which would give us these numbers.
In this scenario, VMware Pulse IOTC would help to check
Is the Camera working?
Is it connected to a network?
Is it connected to an IoT Gateway?
Is the SD card plugged in or not?
Did someone pull out the SD card?
IoT gateway is a BareMetal that doesn’t run any virtualization.
IoT – The Internet of things (IoT) is the inter-networking of physical devices, vehicles (also referred to as “connected devices” and “smart devices”), buildings, and other items embedded with electronics, software, sensors, actuators, and network connectivity which enable these objects to collect and exchange data
Edge – computing systems performing data processing near the source of the data, which includes a wide array of sensors, actuators, and devices interacting with and communicating real-time data from smart products and services.
Gateway – An Internet of Things (IoT) gateway is a device which serves as the connection point between IoT devices and the cloud. This gateway can be a hardware appliance or virtual. IoT Gateway connects “simple” devices with no operating systems, like sensors, to the network.
Connected Device – A connected device or a Thing device is a nonstandard computing device that can transmit data and is connected to a Gateway. The Thing device connects to a Gateway and sends information to the server through the VMware Pulse SDK Client that is running on the Gateway.
Registered Device – A registered device is a virtual Gateway that is created on the server. A registered device does not have a physical Gateway associated with it.
Enrolled Device – A registered Gateway is enrolled when a physical Gateway is associated with it.
VMware Pulse IoTC Agent – The VMware Pulse IoTC Agent is a component that resides in the Gateway. It connects the VMware Pulse IoT Center services to run commands and to send operational metrics to the IoTC services. The VMware Pulse IoTC Agent offers an SDK that exposes APIs. Third-party applications can use these APIs on the Gateway to interact with VMware Pulse IoT Center.
OT – Operational technology (OT) is hardware and software that detects or causes a change through the direct monitoring and/or control of physical devices, processes and events in the enterprise.
Brief rundown of the Deployment
- Create an Address Record (A Record) and a Pointer Record (PTR) for both forward and reverse resolution in the DNS using the hostname and IP address. VMware Pulse IoTC generates a self-signed certificate based on this DNS. You can test the configuration using the nslookup command for Windows operating systems and dig command for Linux or Mac operating systems.
- Ensure that the vCenter access is set up with at least 100 GB of hard disk space for a single node deployment. For information related to capacity, see the VMware Pulse IoTC 2.0.0 Sizing Guide.
- Ensure that network objects are created and configured in vSphere to deploy the virtual machine. For ports exposed and to be controlled, refer to the Topology Diagram.
- If you do not intend to use the default SSL certificates that the OVA generates during deployment, ensure that the SSL certificates from trusted certificate authorities (CAs) or private CAs are present. SSL certificates must be packaged in the PKCS12 format with the complete certificate chain in the order of intermediate to root, and must follow the signing hierarchy. It is recommended that a certificate is valid for at least two years.
- To access the VMware Pulse IoTC console and the VMware Pulse IoT Administration console, you must enable port numbers 443 and 8443 in the network. VMware Pulse IoTC instance consists of multiple nodes (VMs) where the application services are exposed on port 443 and the VMware Pulse IoTC Administration console is exposed on the port 8443. The port 8443 is used only by administrators who are installing and configuring the VMware Pulse IoTC and is not meant for users who are accessing features of VMware Pulse IoTC.
- Ensure that port 25, the default SMTP port, is reachable from the VMware Pulse IoTC server to the SMTP server, and the connections are TLS enabled.
- Ensure that you have a valid license key. Evaluation period is for 30 days.
More Details can be found here
Once VMware Pulse IOTC OVA is downloaded from the Link, the same OVA need to be used to deploy Load Balancer & 3 Servers.
- Deploy a load balancer node.
- Set up the load balancer node. LB is a role that is assigned once the OVA is deployed & you access the VM using the link https://:8443
- Deploy a server node Node 1 using OVA
- Set up the server node Node 1. Server is a role that is assigned once the OVA is deployed & you access the VM using the link https://:8443
- Deploy & Set up the server nodes Node 2 and Node 3
- Manage Certificates (if required)