Table of Contents HOL EMT

Transcription

1 Table of Contents Lab Overview - - Internet of Things (IoT): VMware Pulse IoT Center & LIOTA (Little IoT Agent)... 2 Lab Guidance... 3 Introducing Pulse IoT Center & LIOTA (Little IoT Agent)... 9 Module 1 - VMware Pulse IoT Center: Console Overview (30 minutes) Introduction Overview of Pulse IoT Center: Walkthrough Create and Save a Filter Alerts and Notifications Admin Users Conclusion Module 2 - VMware Pulse IoT Center: Onboard and Update IoT Gateway (30 minutes)..65 Introduction Login to The Pulse IoT Console Sideload Image to IoT Device Validate Liotd Client Registration Unenroll IoT Device Troubleshooting Conclusion Module 3 - VMware Pulse IoT Center: LIOTA (45 minutes) Introduction Liota with VMware Pulse Quick Start Add Product for Metric Collection Conclusion Page 1

2 Lab Overview - - Internet of Things (IoT): VMware Pulse IoT Center & LIOTA (Little IoT Agent) Page 2

3 Lab Guidance Note: It will take more than 90 minutes to complete this lab. You should expect to only finish 1-2 of the modules during your time. The modules are independent of each other so you can start at the beginning of any module and proceed from there. You can use the Table of Contents to access any module of your choosing. The Table of Contents can be accessed in the upper right-hand corner of the Lab Manual. VMware Pulse IoT Center is an end to end infrastructure management solution that enables OT (Operational Technology) and IT organizations to onboard, manage, monitor and secure their IoT use cases. Liota, a component of the Pulse IoT Center agent, is an open source project offering convenience for IoT solution developers to create edge system data orchestration applications. In this lab, you will explore the features of VMware Pulse IoT Center as well as onboard an IoT gateway. In addition, you will gain experience using Liota. The objective of this lab to give an overview of VMware s solution for Internet of Things (IoT) by showing the capabilities of VMware Pulse IoT Center and Liota. The lab will help the user become familiar with the console used to manage, monitor and secure IoT infrastructure. Lab Module List: Module 1 - VMware Pulse IoT Center: Console Overview (30 minutes) (Basic) VMware Pulse IoT Center enables organizations to easily onboard, manage, monitor and secure diverse IoT edge systems and connected devices through a single unified console. In this module, you will walk through the Pulse IoT Center console and learn how to navigate the dashboards, filter devices and view device details, create custom alerts, view notifications and manage admin users. Module 2 - VMware Pulse IoT Center: Onboard and Update IoT Gateway (30 minutes) (Basic) In this module you will walk through the steps to onboard an IoT gateway into VMware Pulse IoT Center and view live metrics from the device in the console. You will also deploy an over-the-air (OTA) product to update the gateway. Module 3 - VMware Pulse IoT Center: LIOTA (45 minutes) (Intermediate) Liota is an open source project offering convenience for IoT solution developers to create edge system data orchestration applications. In this module we will help you become familiar with Liota. Please see GitHub for more information on this open source project. Lab Captains: Page 3

4 Module 1 - Sheng Sheen, Staff Partner Solutions Architect, USA Module 2 - Kevin Brady, Sr. Partner Solutions Engineer, USA Module 3 - Sheng Sheen, Staff Partner Solutions Architect, USA This lab manual can be downloaded from the Hands-on Labs Document site found here: This lab may be available in other languages. To set your language preference and have a localized manual deployed with your lab, you may utilize this document to help guide you through the process: Location of the Main Console 1. The area in the RED box contains the Main Console. The Lab Manual is on the tab to the Right of the Main Console. 2. A particular lab may have additional consoles found on separate tabs in the upper left. You will be directed to open another specific console if needed. 3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All your work must be done during the lab session. But you can click the EXTEND to increase your time up to 9 hours and 30 minutes. Each click gives you an additional hour. Page 4

5 Alternate Methods of Keyboard Data Entry During this module, you will input text into the Main Console. Besides directly typing it in, there are two very helpful methods of entering data which make it easier to enter complex data. Click and Drag Lab Manual Content Into Console Active Window You can also click and drag text and Command Line Interface (CLI) commands directly from the Lab Manual into the active window in the Main Console. Accessing the Online International Keyboard You can also use the Online International Keyboard found in the Main Console. 1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar. Page 5

6 Click once in active console window In this example, you will use the Online Keyboard to enter the sign used in addresses. The sign is Shift-2 on US keyboard layouts. 1. Click once in the active console window. 2. Click on the Shift key. Click on key 1. Click on the "@ key". Notice sign entered in the active console window. Page 6

7 Activation Prompt or Watermark When you first start your lab, you may notice a watermark on the desktop indicating that Windows is not activated. One of the major benefits of virtualization is that virtual machines can be moved and run on any platform. The Hands-on Labs utilizes this benefit and we are able to run the labs out of multiple datacenters. However, these datacenters may not have identical processors, which triggers a Microsoft activation check through the Internet. Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoft licensing requirements. The lab that you are using is a self-contained pod and does not have full access to the Internet, which is required for Windows to verify the activation. Without full access to the Internet, this automated process fails and you see this watermark. This cosmetic issue has no effect on your lab. Look at the lower right portion of the screen Page 7

8 Please check to see that your lab is finished all the startup routines and is ready for you to start. If you see anything other than "Ready", please wait a few minutes. If after 5 minutes your lab has not changed to "Ready", please ask for assistance. Page 8

9 Introducing Pulse IoT Center & LIOTA (Little IoT Agent) What is VMware Pulse IoT Center What Is VMware Pulse IoT Center? 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 (Operational Technology) and IT organizations to onboard, manage, monitor and secure IoT infrastructure Here are some key terms you ll be hearing often in IoT discussions. The more important ones that may be new to some people are Edge, and Edge System or Gateway, and OT. The Edge is a general term that describes computing systems performing data processing near the source of the data, inclusive of sensors, actuators, and devices interacting and communicating with real-time data from smart products and services. Fog is another term that you may hear referring to similar concepts. Key IoT Terminology 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. Edge System An edge system connects an IoT sensor or other device using its internal local area network and protocol (ex. CAN bus, Profibus, Modbus, serial, Zigbee, BACnet, etc.) with an external wide area network and protocol (ex. TCP/ IP) or the Internet. Gateway A type of edge system that can be an embedded or stand alone device. Connected Device - "things", sensors, actuators, etc... Page 9

10 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. Architecting an IoT Solution An IoT architecture looks simple but is exponentially complicated by diversity, scale and bi-directionality. In a 2 tiered example, powered IP cameras may be able to communicate via wired or wireless connections directly to compute resources and other datacenter components in non colocated environments. While it is simple, it also lacks control points, and doesn t lend itself to great defense in depth security strategies. For instance, IoT bots and malware infecting hundreds of thousands of IP camera and DVR s have launched DDoS attacks against service providers, resulting in massive outages. In the second example, many IoT devices are low powered and use diverse sets of network protocols. These devices often require colocated edge systems/gateways to communicate back to applications living in datacenters, creating a 3 tired architecture. This also offers a service insertion point for Pulse services and is the primary targeted architecture for current use cases. Page 10

11 Content and Control Plane In an IoT application environment, it s helpful to think of an IoT-ready architecture in terms of a content plane and a control plane. The content plane is where all the insight rich data from connected things is analyzed to drive business decisions and process efficiences. Whereas the control plane refers to the IoT infrastructure itself along with the capabilities to manage, monitor and secure it. Much focus is given to the data generated and analyzed from the things, which is used to solve critical problems among many other uses. However, what about the things themselves? Are they enterprise grade? How are these being managed and patched, and are they secure? There is a whole IoT infrastructure layer underneath which enables the content plane and is integral to any IoT implementation. Pulse IoT Center is primarily focused on solving these problems. Page 11

12 VMware Pulse IoT Center Blueprint The high-level services breakdown is shown in this blueprint example. The Edge generally represents a non-datacenter or public cloud location such as a manufacturing facility, retail location, distribution center, or any place where IoT sensors and gateways would be located to facilitate business, operational, or other industrial processes. The Pulse IoT Center agents run on gateways in those locations. Management and analytical platforms may be in one or more locations in the cloud, datacenter, or edge location depending on requirements and constraints for data movement and processing. Bandwidth, power, processing time, and data volume all become major factors in an IoT deployment, and make the edge a strategic location for the distribution of compute services. Pulse IoT Center Infrastructure Management Blueprint A blueprint has emerged for functionality and capabilities necessary to manage the IoT control plane in enterprise-scale production environments. Key requirements include: Support for diverse protocols IoT infrastructure management tools should provide vendor neutral management for the wide variety of protocols and data formats. Through the LIOTA agent running on edge systems and gateways, and our VMware s industry leading device management expertise, we can onboard heterogeneous IoT devices. Automated detection, configuration, management of edge systems IoT management solutions require automated onboarding, software updates and timely action according to preconfigured rules. Page 12

13 Ability to monitor, analyze, and orchestrate data Providing complete control of data and managing it according to preset rules. Security by design Any IoT infrastructure management solution should provide security at all levels of the device and data lifecycle. The Little IoT Agent (LIOTA) The Little IoT Agent (LIOTA) For a truly seamless, end-to-end connected experience, it is important to create an IoT app framework that supports interoperability. One step in this direction is to implement a 3-tier architecture which connects your devices to the data centers via intelligent gateways. Although these gateways are excellent hubs, the problem of diverse IoT things in your organization being unable to speak the same language still persists.this is usually solved by creating different versions of an IoT application for different kinds of gateways/edge devices which can be a huge overhead. Liota was specifically created to simplify this task by providing a common model and building blocks for unified data acquisition and orchestration. What is Liota? Liota is a vendor-neutral, open source SDK for building IoT gateway applications for managing, monitoring and orchestrating data between things, gateways and the cloud/ data center. Liota can help control where, when, and how to gather telemetry from connected devices and transfer it to the cloud/data center. It does this by providing Page 13

14 complete abstractions to accelerate the development of IoT applications and simplify connection and control flows across the 3-tier architecture. Liota is an open source project offering convenience for IoT solution developers to create IoT Edge System data orchestration applications. Liota has been generalized to allow, via modules, interaction with any data-center component, over any transport, and for any IoT Edge System. It is an SDK/ Framework for easily writing portable, modular, dynamic IoT gateway data orchestration apps. Liota applications can be written to collect telemetry from any "things" connected to edge systems, regardless of manufacturer, device type or communication protocol. Easy-to-use and provides enterprise-quality modules for interacting with IoT Solutions Runs on gateways/edge systems BSD 2-Clause License Requirements and Prerequisites Prerequisites for Pulse IoT Center Installation A basic installation of Pulse IoT Center will require 6 virtual machines and appliances (2) Windows Server 2012 R2 (2008 R2 or 2012 are also supported) for small installations and proof of concept it may be possible to run on a single machine. AirWatch SQL Database (requires SQL Server 2012 or 2008) AirWatch Application Server Pulse OVA s consists of 3 Ubuntu VM appliances MQTT Broker Page 14

15 Pulse API Server Pulse Console vrops OVA for Pulse GA vrops appliance with Helix adapter Other Requirements IP addresses for each server Certificates are required for each server. Public/Trusted Certificates are recommended, or certificates will need to be created and imported into keystores to create trust between server components Page 15

16 Module 1 - VMware Pulse IoT Center: Console Overview (30 minutes) Page 16

17 Introduction This Module contains the following lessons: Overview of Pulse IoT Center: Walkthrough Create and Save a Filter Alerts and Notifications Admin Users Pulse IoT Center The Internet of Things (IoT) is rapidly transforming traditional business models and operational processes to boost innovation and growth. An IoT-ready infrastructure has unique requirements with onboarding, configuring, managing and securing connected devices, and as a tidal wave of IoT use cases reaches your organization, your IT and Operational Technology (OT) departments may struggle to keep up. VMware can help organizations achieve IoT infrastructure excellence and deliver successful business outcomes that meet the needs of both your IT and OT organizations. What Is VMware Pulse IoT Center? VMware Pulse IoT Center is a secure, enterprise-grade, end-to-end IoT infrastructure management solution that allows OT and IT to have complete control over their IoT use cases, from the edge all the way to the cloud. It helps companies to onboard, manage, monitor, and secure all things and infrastructure for IoT. Note that this lab is a simulation of a live, production IoT environment where actual end point devices would be constantly reporting data. In this lab Page 17

18 environment data simulators are used to provide end point data. Due to limitations in the simulated Hands On Labs environment there are occasions where data from this simulator will not be refreshed properly, in this case some of the data may not populate correctly and some of the Alerts may not function properly. This lab is built with Pulse IoT release 1.0. Release 1.1 simplifies the enrollment experience, adds support for single sign on and improves the device reporting. For more information on Pulse IoT and the Pulse IoT 1.1 release please see our website : And our IoT 1.1 blog : For more information on the Pulse 1.1 product. Key Features Edge device management Ability to support heterogeneous things and gateways with different hardware, operating systems, and communication protocols Infrastructure analytics Ability to identify anomalies with real-time monitoring and perform infrastructure analytics Single point console A single point of monitoring and management for the IoT infrastructure (composed of edge systems and connected devices) for both IT and OT users OTA updates Ability to provide over-the-air updates to connected edge systems and things Security across IoT value chain Provides secure onboarding, authentication and authorization for ongoing communication, over the air updates on secure channels and the ability to contain threats using enterprise wipe Visualize relationships between things and gateways Provides pictorial representation of the topology of the IoT infrastructure 2 tier or 3 tier in a parent child relationship diagram On-premises support Offered as an on-premises solution for deployment flexibility and security; future versions will also be offered as cloud-hosted Enterprise integrations Quick and easy integration with existing server-side monitoring and alerting capability through REST APIs along with flexible clientside integration through a Python-based SDK Page 18

19 Key Components Key Components Pulse IoT Center is composed of two primary components: A management console (server-side) The server-side component includes the following set of services: Admin Console for dashboard and setting alerts and notifications APIs for enterprise integrations and extensibility Infrastructure Monitoring module for alerts and symptom configuration Device Management module for OTA software lifecycle management emqtt Broker for onboarding and configuration An agent (client-side) that sits on IoT gateways and edge systems The clientside component includes: An open-source SDK that can be customized to interface with and ingest telemetry from any edge systems or connected devices An agent that delivers data samples from devices to the server and receives packages, such as configuration changes and software updates Page 19

20 Pulse Services Overview Pulse Services Overview Pulse Services Provides the primary user interface for Pulse IoT Center. Pulse Console Serves as the primary UI for Pulse IoT Center. Pulse Console provides the primary user interface. Supported browsers: Firefox, Chrome Basic account used for login in v1.0. vidm support planned for next release. Pulse IoT Center features a comprehensive REST API for quick and easy enterprise integrations. Any data presented in the console can be extracted via an API call. URL of the API reference page addr>/api/docs Note: This should be used only after logging in to console for first time Page 20

21 Pulse API Server Interfaces to lifecycle management and monitoring services and provides connection to the Pulse Console Lifecycle Management - Services are used to manage and update gateways and connected devices. AirWatch serves as the backend management system which provides OTA (over-the-air) updates to edge systems and devices. Gateways are on-boarded via an enrollment process. AirWatch Cloud Messaging and Device Services agents communicate with the AirWatch server to send updates, ensure compliance, and enforce policies. Cloud Messaging Agent (AWCM) message queue that notifies agents of new updates for connected devices Device Services Agent (AWDS) - provides Over-the-Air (OTA) updates to gateways. The device organization topology allows devices and gateways to be visualized via a 2-tier hierarchy according to parent-child relationships. Currently very similar to the standard AirWatch installation process, leveraging a backend SQL database. These installation packages are unique to Pulse IoT Center. Monitoring Services - collects device and gateway metrics and provides them to the Pulse API Server. An adapter is installed as a vrops solution to connect with the MQTT Broker and gather data sent from gateways. vrealize Operations Manager serves as the backend device monitoring and analysis engine for Pulse IoT Center. The GA vrops ova is used as the monitoring backend for Pulse. The Helix adapter is installed as a vrops solution component and interfaces with the MQTT Broker. vrops receives messages from the MQTT Broker, which receives device information from the gateway/edge system. vrops updates the Pulse API server, which provides data to the Pulse UI. MQTT (Message Queue Telemetry Transport) Service messaging broker that enables communication between monitoring services and agent. The Pulse MQTT Broker is a scalable, reliable, enterprise-grade message hub for IoT, M2M, Smart Hardware and Mobile Messaging Applications MQTT is often used for connecting devices running a small code footprint, such as sensors, that are operating in remote locations with limited bandwidth. The MQTT Broker virtual appliance is included in the OVA for Pulse IoT Center. Pulse uses EMQ (Erlang MQTT Broker or emqtt), which is a distributed, massively scalable, and highly extensible MQTT message broker written in Erlang/OTP. One node support can handle up to 1.3 million concurrent connections on a 12 Core, 32G CentOS server. EMQ is fully open source and licensed under Apache Version 2.0. Page 21

22 LIOTA (Little IoT Agent) Installed on edge systems to collect telemetry data Page 22

23 Overview of Pulse IoT Center: Walkthrough In this lesson, you will walkthrough an overview of the Pulse IoT Center. Login to Pulse IoT Center Console You will begin by logging into the Pulse IoT Center Console. 1. Double-Click on the Google Chrome shortcut on the desktop to launch the browser. Page 23

24 Login to Pulse IoT Center Console You will begin by logging into the Pulse IoT Center Console. NOTE: When you start the Chrome browser, a couple of browser tabs may open by default. This is expected. 1. Click on the VMware Pulse bookmark from the Bookmarks Toolbar. 2. Under Username, enter sysadmin. This is the default admin username for VMware Pulse IoT Center. 3. Under Password, enter VMware1! 4. Click on the Login button to continue. Page 24

25 Dashboard This is an overview of the Pulse IoT Solution. 1. This left hand column is the main navigation pane. As you can see, there s various different sections of the console you are seeing. Main Dashboard, Alert Definitions, Notifications, OTA Updates, Admin, Org Groups and Settings. 2. The next thing you re looking at is the main dashboard. In this view, you see several modules and columns that display different statistics about your IoT deployment. In the main view, you have 8 managed devices: 7 connected devices and 1 edge system. Note that as you progress through this lab your console view may differ slightly from the images in this manual. 1. The far right column is a modular view that can be switched between Managed Objects and Alerts. 2. There are several ways to search and filter devices including: A Search Box, Page 25

26 Organization Groups Direct Device Filtering Managed Objects You are going to start by drilling into an individual device. 1. On the right column, select the drop-down menu of Active Alerts and change it to All Managed Objects 2. Click on the first Edge System to view its details. Page 26

27 Edge System Selecting the device record in the managed objects view will bring that (device / edge system) into focus, allowing you to view its details: 1. Including the number of Managed Objects associated with this Edge System. You have one Edge system and 7 Connected Devices. Zero Active Alerts. 2. Over time, there are zero Alert Trends. 3. Let's scroll the scrollbar down further to view the rest of the managed objects' details. Page 27

28 Edge System You can now view that Gateway's properties and system metrics. 1. Properties are relatively static values that will change infrequently over time. 2. Metrics are a much more real-time set of data, time-series based data. 3. Here you can turn on additional charts for Memory utilization. 4. By simply scrolling the mouse over the chart, you can go into the time-series data at tighter frequency. Below that you have a spanning tree map of the gateway on the far left and all the connected device in the middle. 5. Let's scroll the scrollbar down further to view the spanning tree map and all its connected devices. Page 28

29 Edge System You have a spanning tree map (Child Hierarchy) of the gateway on the far left and all the connected devices in the middle. 1. Select the TemperatureSensor device. The Simulator01BuildingTermostat should appear. 2. Click on the Simulator01BuildingTermostatVMW16Sim003 device to drill in further. Page 29

30 Connected Device By drilling into a category and its attached device, you now can view that particular thing's data. 1. Let's scroll the scrollbar down further to view the rest of the Connected Device data. Page 30

31 Connected Device Here you see a very similar dashboard of Connected Device Properties and Connected Device Metrics. In this case, you are viewing Temperature data. Here again, you see that time-series data. 1. Try scrolling your mouse while inside the timed window to zoom in or out. Page 31

32 Connected Device Metrics You can also filter this based off of initial time windows: 1. Select Last 1 day from the drop-down menu. NOTE: Depending on when this lab environment was created for you, you may not have much historical data. So, when you choose Last 1 Day the graph may not have enough historical data to show more details. Your graph may look the same as the graph for Last 1 hour. 2. As you move it to broader time/data, instead of seeing individual time-series data it displays us the Minimum / Maximum values to make it easier to comprehend. NOTE: Again, you may not have enough historical data if the environment was just created for you. 3. Select the Edge System link to step up a level, back to our Edge System. Page 32

33 Edge System Back at the Edge System, 1. Scroll the scrollbar down further to view the spanning tree map (Child Hierarchy) and all its connected devices again. You can see several categories all at the same time. As an administrator, you can get a holistic view of all devices that are connected and what the impact would be if this edge gateway goes offline for any particular reason. 2. Select the Elevator device. The Simulator01BuildingElevatorVMW16Sim003 should appear. 3. Select the Glass device. The Simulator01BuildingGlasVMW16Sim003s should appear. 4. Select the TemperatureSensor device. The Simulator01BuildingTermostatVMW16Sim003 should appear. 5. Select All Managed Objects to continue. Page 33

34 Create and Save a Filter In this lesson, you are going to create and save a Filter, so you can later find a particular Gateway much easier. Resource Filters 1. Click on the Filter icon next to the title Dashboard. 2. Click and set the Resource Filters to Edge Systems. 3. Select the Property "State" to filter on. 4. You will enter the state california since this device exists in California. 5. Click Add to add the property state as a filter. Page 34

35 Resource Filters You will add a second filter to indicate the floor number. You can continue to add additional filters to narrow the scope as required. 1. Select the Property "floor_no" to filter on from the drop-down. 2. Enter the number 3 to filter on the 3rd floor. 3. Click Add to add the property floor_no to the filter. You now have 2 filters: State and floor_no defined. 4. Scroll down the scrollbar to continue. Page 35

36 Save Filter You can add additional Alert Filters. You can apply filter immediately or save the filter for future use. 1. Enter 3rd floor devices as the Filter name. 2. Click Save to save this filter. 3. You will also click Apply Filter to immediately apply this filter. Page 36

37 Filter Objects With this filter applied, you see the Filter Objects view is going to update to reflect just a single Edge System. 1. On the right hand column, select Filtered Objects and you will see the 1 Edge System listed. 2. Select the Edge System to drill into the Edge System. Page 37

38 Filter Objects The Edge System is now displayed and you need to determine this is indeed the Edge System you are looking for. 1. Scroll down the scrollbar down to the Edge Systems Properties section. Page 38

39 Filter Objects 1. You can see this is indeed the Edge System you are looking for and it has been correctly filtered by State - california and floor_no - 3. Page 39

40 Alerts and Notifications In this lesson, you will walkthrough creating an alert and notification. Alert Definitions Still logged in as sysadmin, you will now add a new Alert. 1. You will start by selecting ALERT DEFINITIONS. 2. Click on Add New to add a new Alert. NOTE: If for some reason you are not seeing the side navigation bar where you can select the Alert Definitions, then your screen resolution may be too low. You can either increase the resolution or choose ALERT DEFINITIONS from the drop-down menu to the left of the vmware logo. Page 40

41 Alert Definition Details Here you will define the Alert details: 1. Start by giving it a Name: CPU Utilization 2. Set Object Type to Edge System. 3. Set Alert Type to Health. 4. Set Alert Severity to Warning. 5. Wait Cycles and Cancel Cycles are number of consecutive, above/below the threshold values to trigger an alert. You will set the Wait Cycles to Set the Cancel Cycles to Click Next to continue. Page 41

42 Symptoms Now you will define a Symptom. 1. Click Create Symptom. Page 42

43 Create Symptom The Symptom you are defining is the threshold for an Excessive CPU utilization percentage. 1. Enter the Name: Excessive CPU. 2. Select Severity of Warning. 3. Leave the defaults for Wait Cycles. 4. Leave the defaults for Cancel Cycles. 5. Select default Type of Metric. 6. Select default Threshold of Static. 7. Under Condition, Select CPU Utilization. NOTE: You may see another CPUUtilization with no spaces. That is expected, because you have another Alert with such name created in a Sample Alert. So, make sure you select the Condition with CPU Utilization with a space, the one you just named. 8. Select Greater than > from the drop-down menu. Page 43

44 9. Enter 2.0 as the threshold trigger. Note: There is very light load in this lab, so you want it to trigger above the 2% threshold. 10. Click Save to continue. Symptoms 1. Make sure that the Excessive CPU Symtom is defined and checked, click Next to continue. NOTE: You can safely ignore the unchecked Sample Symptom. That is just there as an example. Recommendations Page 44

45 For Recommendations, when an alert goes off automatically you will have someone check for stuck processes. 1. Click on Create Recommendation. Create Recommendations 1. Under description, you will enter Check for stuck processes. 2. Click Save to Continue. Page 45

46 Recommendation Selected 1. Make sure the new recommendation is defined and checked. Click Next to Continue. NOTE: You can safely ignore the unchecked Sample Recommendation Description. That is just there as an example. Page 46

47 Review & Save 1. Now you will review the new alert definition and click Save to continue. Notifications To send an notification when an alert is triggered, you will create a new Notification. 1. Select Notifications from the left navigation pane. Page 47

48 2. Click on Add New to add a new notification. Add Notification 1. You will name this CPU Alert. 2. Under Description, enter Alert for excessive CPU utilization. 3. Select Object Type of Edge System. 4. Select Severity of Warning. Deselect the other severities. 5. Select Type of Health. Deselect the other types. 6. Under , you will enter alertadmin@corp.loc 7. Click Save to continue. Page 48

49 Notifications Now you have a notification configured. When an alert is triggered, an alert will be sent to your Administrator. Currently, you see it has not been triggered yet so you will continue to the next couple of steps and you should see the alert later. Note: Since this lab is using simulated data there are instances where the data will not populate quickly enough to generate an alert. Page 49

50 Admin Users In this lesson, you will walkthrough adding a "Consoleadmin" User. Admin 1. On the left navigation pane, select Admin. 2. Click on Create Admin. Page 50

51 Create Admin Now you are going to create a new Admin to login to the system. 1. You will give this user a Username of holuser. 2. Enter the Password: VMware1! 3. Confirm Password: VMware1! 4. Leave the Prompt User to change password on first login selected. 5. Enter First Name of HOL. 6. Enter Last Name of User. 7. Select Group Name of VMware from the drop-down menu. 8. Enter Address of holuser@corp.loc 9. Select Save to continue. Page 51

52 Admin Now you will elevate the role of the Username holuser to a Consoleadmin. 1. Click on the Pencil icon to edit Username holuser. Page 52

53 Update Role 1. Change our Role Name to Consoleadmin. 2. Click Save to continue. Page 53

54 Logout Now you will logout from user sysadmin and log back in as holuser. 1. Select from the sysadmin menu, the Logout option to logout. Page 54

55 Login Now you will login as holuser. 1. Enter Username holuser 2. Enter Password VMware1! 3. Click Login Page 55

56 Change Password You are prompted to change the password since you left the default to change the password on first login. 1. Enter Old Password: VMware1! 2. Enter New password: VMware1!VMware1! 3. Confirm new password: VMware1!VMware1! 4. Click Update to Continue. Page 56

57 End User License Agreement You will agree to the End User License Agreement. 1. Check the I Agree to the Terms of Service checkbox. 2. Check the I Agree to the Terms of Service checkbox again on the bottom. 3. Select the bottom Accept button to Continue. Page 57

58 Active Alerts Now that you are logged in and enough time has passed, you have actually trapped an alert. One of our devices has gone above the CPU threshold that we configured earlier. 1. You can see you have 1 Health related alert. 2. Scroll down the scrollbar to see the Alert Trend. Note: Since this lab is using simulated data there are instances where the data will not populate quickly enough to generate an alert do not worry as this is an affect of using a simulator to produce data. Page 58

59 Alert Trends You can see the Alert Trend is starting to populate. 1. Let's drill into the 1 Health Alert by clicking on the CPU Utilization Alert that was triggered. Note: Since this lab is using simulated data there are instances where the data will not populate quickly enough to generate an alert do not worry as this is an affect of using a simulator to produce data. Page 59

60 Acknowledge Alert You can see all the data here. The red line is where you set the threshold at 2.0%. You can see that the CPU has been above that threshold enough times consistently to trigger this alert. 1. You can clear the Alert by selecting the Acknowledge button or if it then drops below the threshold enough consecutive times that it will clear itself. Note: Since this lab is using simulated data there are instances where the data will not populate quickly enough to generate an alert do not worry as this is an affect of using a simulator to produce data. Page 60

61 Alert Cleared You now see the Alerts have been cleared. Logout as holuser Page 61

62 Now you will logout from user holuser and log back in as sysadmin. 1. Select from the sysadmin menu, the Logout option to logout. Page 62

63 Conclusion In this module, we have provided a quick overview of the Pulse Console. Navigating, searching, filtering devices, viewing device properties and metrics. You have created an alert and notification and seeing an alert being triggered and clearing the alerts. You've finished Module 1 Congratulations on completing Module 1. If you are looking for additional information on Pulse IoT Center, please take a look on our website: Proceed to any module below which interests you the most: Module 2 - VMware Pulse IoT Center: Onboard and Update IoT Gateway (30 minutes) (Basic) In this module you will walk through the steps to onboard an IoT gateway into VMware Pulse IoT Center and view live metrics from the device in the console. You will also deploy an over-the-air (OTA) product to update the gateway. Module 3 - VMware Pulse IoT Center: LIOTA (45 minutes) (Advanced) Liota is an open source project offering convenience for IoT solution developers to create edge system data orchestration applications. In this module we will help you become familiar with Liota. Please see GitHub for more information on this open source project. How to End Lab Page 63

64 If you wish to end your lab NOW please click on the END button. This will end your Hands On Labs session. Otherwise please continue to Module 2 or Module 3 as described on the previous step. Page 64

65 Module 2 - VMware Pulse IoT Center: Onboard and Update IoT Gateway (30 minutes) Page 65

66 Introduction This module provides a basic introduction on how to enroll an edge device into Pulse IoT. In this module you will be registering a simulated edge device on a simulated gateway. This installation normally is done targeting a physical device however due to labconstraints both the edge device and the gateway are Virtual Machines. The procedures used are exactly the same as those which would be used on physical hardware. This Module contains the following lessons: Login to Pulse IoT Console Sideload Image to IoT Device Validate Liotd Client Registration Troubleshooting Unenroll IoT Device Pulse IoT Center Architecture Gateway / Edge System Overview What is a gateway / edge system? 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 a virtual appliance. Why are gateways important? They are used for Coupling and Decoupling IoT devices and serve as the control point between sensitive IoT devices and the cloud or data center. They are also used to connect "simple" devices with no operating systems, like sensors, to the network. Page 66

67 Gateway Requirements to run Pulse IoT Center Agents: Both x86 and ARM A8 and A9 processors are supported. Minimum Requirements for a device to run Pulse IoT Center Agents: Operating system with Python or later (Python 3.x currently not supported) libc 2.19 or later version libssl & libcrypto PROJECT LIOTA - The Smart Little Agent for Big IoT For a truly seamless, end-to-end connected experience, it is important to create an IoT app framework that supports interoperability. One step in this direction is to implement a 3-tier architecture which connects your devices to the data centers via intelligent gateways. Although these gateways are excellent hubs, the problem of diverse IoT things in your organization being unable to speak the same language still persists.this is usually solved by creating different versions of an IoT application for different kinds of gateways/edge devices which can be a huge overhead. Liota was specifically created to simplify this task by providing a common model and building blocks for unified data acquisition and orchestration. What is Liota? Liota is a vendor-neutral, open source SDK for building IoT gateway applications for managing, monitoring and orchestrating data between things, gateways and the cloud/ data center. Liota can help control where, when, and how to gather telemetry from connected devices and transfer it to the cloud/data center. It does this by providing complete abstractions to accelerate the development of IoT applications and simplify connection and control flows across the 3-tier architecture. Note that due to limitations in the simulated Hands On Labs environment that this lab is built with Pulse IoT release 1.0. Release 1.1 simplifies the enrollment experience, adds support for single sign on and improves the device reporting. For more information on Pulse IoT and the Pulse IoT 1.1 release please see our website : And our IoT 1.1 blog : For more information on the Pulse 1.1 product. Why should I use Liota? Liota is functionally useful on any IoT edge system, and any of its connected devices, that require management. Liota (written in Python) resides primarily on IoT gateways/ Page 67

68 edge systems, and provides a common way for enterprises to manage and leverage multi-vendor gateways within their IoT infrastructures.it allows interaction between any device and any data-center component, over any transport, and through any IoT gateway/edge system. It is easy-to-use and has been successfully tested with many gateway and cloud components from both VMware and the community, such as AWS IoT, ThingWorx, IBM Bluemix, the open-source tool Graphite, and, of course VMware Pulse IoT Center. Key Components Key Components Liota applications are comprised of six basic abstractions that represent a complete data flow from a device attached to the edge system to an application in a data-center. They are loaded and unloaded with a Package Manager. Connected Device represents a device (a data-source attached to or on an IoT gateway or edge system) DeviceComms is an abstraction of the communication mechanisms between a device and an edge system Edge System represents the hardware and software platforms of an IoT gateway or edge system Metric represents a time-series stream from a data source to a datacenter application (a stream of (number, timestamp) tuples) Data-Center Component is an abstraction of the protocol and formata datacenter component requires DCCComms is an abstraction of the communication mechanisms between the edge system and data-center Liota Dynamic Packages Package Manager allows the loading and unloading of Liota packages.a liota package is a Python class having: A dependency list (of other packages) Code to obtain configuration from registry and references to objects from other packages A run method A clean_up method LIOTA on Github Contributing to Liota Want to hack on Liota and add your own DCC component? Awesome! Just fork the project in order to start contributing the code. Page 68

69 Login to The Pulse IoT Console You will begin by logging into the Pulse IoT Center Console. If the Google Chrome browser is not open from the previous session then open a Google Chrome window. 1. Double-Click on the Google Chrome shortcut on the desktop to launch the browser. Page 69

70 Start the Pulse IoT Dashboard There will be 2 tabs at the top of the Chrome Browser window: 1. Pulse IoT Dashboard 2. Pulse Administrative Dashboard (which we will open in future steps) 3. The Pulse Administrative Console window should be open Page 70

71 Login to the Pulse IoT Center Administrative Console Login to the Pulse IoT Center Administrative Console. Note: In this lesson you will toggle between two Pulse consoles which will look very similar, the Administrative Console which you are opening now and a second, Lifecycle Management Console. Note the Usernames are different the Pulse console uses "sysadmin" and Lifecycle Management Console uses "administrator" however the passwords are the same (VMware1!) 1. Under Username, enter sysadmin. This is the default admin username for VMware Pulse IoT Administrative Center. 2. Under Password, enter VMware1!. 3. Click on the Login button to continue. This may take a little while to open, please be patient. Page 71

72 Pulse Administrative Dashboard This is the Pulse Administrative Dashboard, feel free to explore by clicking on any of the icons in the dashboard. When you are done browsing here click on the second browser tab highlighted above (1). This is the Lifecycle Management Console. Note that as you progress through this lab your console view may differ slightly from the images in this manual. Page 72

73 Login to the Lifecycle Management Console as Administrator 1. Under Username, enter administrator. This is the default admin username for VMware Pulse IoT Lifecycle Dashboard. 2. Under Password, enter VMware1!. 3. Click on the Login button to continue. This may take a little while to open, please be patient. Page 73

74 Explore The Lifecycle Dashboard This is the Pulse Lifecycle Management Dashboard, feel free to explore by clicking on any of the icons in the dashboard. When you are done browsing: 1. If not already selected click "Devices" on the left side menu. 2. Expand "Staging and Provisioning". 3. Select "Staging". NOTE: If you do not see the vertical dashboard on the left hand side click the three horizontal bars next to VMWARE as shown below to expand the dashboard. Note that as you progress through this lab your console view may differ slightly from the images in this manual. Page 74

75 Initiate the Generation of the Sideload Package Here you are generating a Linux tar archive file which will be sideloaded to the IoT device. 1. Click the sideload button to initiate the generation of the tar archive (the sideload button is highlighted in YELLOW). Page 75

76 Generate The Sideload Package 1. Enter a passphrase which will be used in a later PuTTY session for authentication, you can use any passphrase but it is recommended to use VMware1! for consistency. Make note of the passphrase since it cannot be reset. Note that the Organization name is filled in for you already. 2. Hit "Download" to initiate the download of the tar archive to the server. Page 76

77 Archive Creation 1. Do not proceed to the next section until the download of the tar archive is complete, the download will show in the bottom left of the Sideload Staging Package window. Note the message "Please be patient" will remain, when you see the "SideLoadStaging...tar..." appear then the operation is complete. 2. Once the download is complete you can close this browser window and move to the next section. Page 77

78 Sideload Image to IoT Device In this session you will be using WinSCP and PuTTY to migrate the tar archive to the IoT device which you will be registering with Pulse. You will use WinSCP to create a temporary download directory on the device which you are registering and use PuTTY for the installation of the Liota agent. You will then complete the process and register the device with the Pulse server. Open WinSCP 1. Open the desktop shortcut "gateway1" by double-clicking it to initiate a WinSCP session. Page 78

79 Select "Create New Folder" On the right hand side of the WinSCP Window (under /tmp) : 1. Click the folder icon to open the "create a new folder " window (if you hover over the folder it will say create new directory). Page 79

80 Create A Download Directory 1. Name the folder "pulse", by default this window will have the default folder name of "new folder" clear the new folder name by either hitting the delete key or by backspacing and enter "pulse" for the folder name. 2. Click "OK" to create the "/tmp/pulse" folder. Change Directory to "Pulse" Page 80

81 1. Double click on the "pulse" folder you just created to change directory to "/tmp/ pulse". Copy the Tar Archive 1. Drag the SideLoadStagingfileofgateway file from under "Downloads" on the left to the "pulse" directory on the right. 2. You should now see the file under "/tmp/pulse". Page 81

82 Close WinSCP 1. You can close WinSCP as you no longer need this open. Page 82

83 Terminate The WinSCP Session 1. Click OK to terminate the WinSCP session. Begin a PuTTY Session 1. Open PuTTY from the taskbar. Page 83

84 Open A PuTTY Session For Gateway1 1. Select "gateway1" by clicking on it. 2. Click "Open" to initiate a PuTTY session with the Linux Gateway1 server. Page 84

85 Login to Gateway1 1. Login as "holuser". There is no password. Switch to the Pulse Download Directory 1. Type "cd /tmp/pulse" to change directory to the "pulse" directory you created previously using WinSCP. Page 85

86 Validate The Files Copied to "/tmp/pulse" 1. Type "ls" to validate the files. 2. Verify the SideLoadStaging file you copied previously with WinSCP is present. Page 86

87 Unpack the Tar Archive File Unpack the archive using the Linux tar command. 1. Enter "tar -xvzf./sideloadstaging_stagingfileforgateway_vmware.tar.gz. Note that you can: 1. drag the text above to the PuTTY window. 2. Type "tar -xvzf./side* " (and Linux will expand the file name for you). 3. You can use the tab complete feature to complete the command, type "./Side followed by TAB Page 87

88 Verify the Unpacked Files After the tar command completes type "ls" to verify the files which were un-archived, you should see the files in BLUE and RED in the window above. Page 88

89 Switch Directory to the Agent Installation Directory 1. type "cd agent" to change to the agent directory where the tar files were unpacked. 2. type "ls" to show the install files, you should see the two files listed above in GREEN. Page 89

90 Install the Pulse Agent Initiate the installation of the Pulse agent by invoking the ice-client shell installation script. The command requires administrative privilege so it will require the "sudo" command to be used in conjunction with the installation shell. Type : sudo./ice-client-linux-x86_ sh You can drag and drop the command into the PuTTY window or type "sudo./ice", followed by the "tab" key to fill out part of the installation shell file name, then type "-" followed by the "tab" key again. Then hit enter to begin the installation. Page 90

91 Enter The Passphrase Ignore the "Failed to execute operation" message, this is a normal part of the install script. The passphrase was the one set previously in the "Sideload Staging" step. Enter whatever Passphrase you entered during the "Sideload Staging" step. Hint: The suggested passphrase when you created the sideload archive was "VMware1!". Note that no text will appear when you type. After typing the Passphrase hit "enter". Page 91

92 Successful Install Of the Liotd Agent If you entered the correct passphrase you will see "Installation Successful" and a message to run the iotcc command to register the edge system. If the Liotd Agent was successfully installed ( Installation successful message) then skip the next step Page 92

93 Install Of LiotD Failed If you see the message highlighted above in YELLOW you most likely entered a incorrect passphrase. in this case simply re-run the installer from the step above (sudo./ice-client-linux-x86_ sh).and enter the passphrase you set when you created the sideload package. Once you have successfully installed the Liotd Agent proceed to the next step. Page 93

94 INITIATE THE IOTCC CLIENT 1. Enter the command "sudo /opt/ice-client/iotcc", this will initiate the session to register the appliance with the gateway. The command requires administrative privilege so make sure you prefix the command with "sudo". Do not enter anything for User ID yet. Please Read Before Proceeding : The next steps will require switching between the PuTTY session and the Pulse Dashboard where you will copy a one-use User ID and Password from the Pulse console to the PuTTY window, these are required to connect to the gateway. You will be getting these credentials from the Pulse Dashboard as shown in the following steps. The credentials are one-time use only and are unique to this session. Please take careful note in the following steps as you switch back and forth between the PuTTY session and the Pulse console. Page 94

95 RESUME THE PULSE CONSOLE 1. Re-open the Chrome Browser by clicking "Staging & Provisioning" Select The "VMware Pulse" tab 1. For the next steps you will be resuming the Pulse Administrative console. Return to the Pulse console by clicking the "VMware Pulse" browser tab Page 95

96 Open The Administrator View 1. Open the Administrator view by clicking on the "ADMIN" icon on the left hand menu. Page 96

97 Open The Onboarding Credentials Window 1. Click "Onboarding Credentials" Page 97

98 GENERATE ONBOARDING CREDENTIALS 1. Click "Generate Onboarding Credentials" to generate a one-time use set of credentials to register the appliance with the gateway Page 98

99 COPY THE CREDENTIALS to The PuTTY Session In the following steps a one-time use User ID and Password will be generated, please follow the instructions exactly. You cannot use click-cut & click-paste, you must use the copy function as highlighted above. The credentials will be copied one at a time. Again be careful to use the "Copy" button and Do Not use cut/paste to copy these credentials, you must use the "Copy" button highlighted above to copy the Login and Password, one at a time to the PuTTY console.the one-time use credentials fior logging into the Liotd agent will be generated as shown above. Note: It is important to make sure you use the "Copy" button to copy the Login and Password to the Putty window, if you attempt to use cut/paste or drag and drop the authentication will fail and you wil have to repeat this step. Page 99

100 Copy The One-time Use Login Hitting the "Copy" key will cause the text to be highlighted in BLUE, again use the DO NOT use cut/paste use the (2) "Copy" button. Page 100

101 Paste The Login Credentials Into The PuTTY Window Switch back to the PuTTY window, RIGHT click your mouse on "User ID" line, the User ID copied from the Pulse Administrator console should appear. Hit the enter key.note the User ID is unique to your session and will differ from the User ID displayed above. Page 101

102 User ID Entered Successfully Page 102

103 Copy The One-time Use Password From The Pulse Console Return to the Pulse Administrator console, again use the "Copy" key to copy the password Hitting the "Copy" key will cause the text to be highlighted in BLUE, again use thedo NOT use cut/paste use the (1) "Copy" button. Page 103

104 Paste The One-time Use Password Into The PuTTY Window 1. As with "User ID" you will Right Click after "Password". Note you will not see any text copied, Linux does not display password text. Hit enter after you copy the password. 2. In a few minutes you will see a message "Liotad started" this indicates that the process to start the daemon on the appliance has started. This will take from 1-3 minutes, please be patient. Page 104

105 Liotd Started 1. The connection to the gateway has been initiated. Please be patient the connection to the gateway can take between 4-7 minutes please be patient. Page 105

106 Liotd Registration Successful 1. If successful, you will see the message "Registration Successful". If you received this message, this concludes this chapter and you can proceed to the next chapter to validate the Liotd registration. If you did not receive this message and more then 5-7 minutes have elapsed then there was a problem with the registration with the gateway. If the registration with the gateway was not successful you have three options: 1. You can proceed with the "Troubleshooting" chapter of this module, 2. You can leave this module and proceed with module Three (Module Three is not dependent on this module) or, 3. You can quit and re-start the lab. Page 106

107 Note if you choose to restart this lab you do not have to start at Chapter One, you can resume the lab at Chapter Two. Page 107

108 Validate Liotd Client Registration Close The Credentials Window Close the Credentials window as it's no longer needed. Click "Close" Page 108

109 Return to The Staging And Provisioning Console Return to the Staging and Provisioning Console by clicking the Staging & Provisioning tab. Verify Registration Page 109

110 1. Click "Devices" in the left hand menu 2. The Linux Gateway is now registered with Pulse IoT 3. Click the name of the device which was just registered Review Device Information Review information abou the device. Check Proxy Relationships Page 110

111 Scroll down to "Proxy Relationships" and click on "Child Count" Review The Sensors Associated With The Device These are sensors which are reporting data to the IoT device. Page 111

112 Return to The Pulse Dashboard The new devices can also be viewed from the Pulse dashboard 1. Click the "VMware Pulse" tab to refresh the Pulse Dashboard 2. Go to the search bar on the far right and type "vmwarehol" you will see 'hol_gateway1" appear. This is the gateway you added. 3. Click on the gateway which appears under the searchbar Page 112

113 Review Device Information From The Edge Systems Dashboard The Edge Systems dashboard displays information on the edge devices being managed, location, state and other metrics. Scroll down to review information on the devices. Page 113

114 Review Device Hierarchy Relationships 1. Scroll down to "Child Hierarchy" 2. Click "SimulatedDevices" Page 114

115 Device Hierarchy Relationships Displayed This displays the hierarchy of the devices from the Gateway device to the individual sensors. This completes the mandatory part of Module 2. Optionally you can unregister the device you installed in this step. This is optional and is not required for Module 3. You can proceed with the unregistration process or skip ahead to module 3. Page 115

116 Unenroll IoT Device This section is optional, the unenrollment of the device is not required for this lab however if you wish to unenroll the device you have just registered in this module then proceed with the following steps. Restore PuTTY Session if the PuTTY session window from earlier in this module is not still open on the student desktop, go to the taskbar and restore the PuTTY session. Page 116

117 Unenroll The Device Using PuTTY Unenroll the IoT device by typing the command "sudo /opt/ice-client/agent unenroll" Delete The Installation Files Uninstall the installation files. Page 117

118 Type the command "sudo /opt/ice-client/agent uninstall". Continue With Uninstall Ignore this error if it appears, the uninstall should have cleaned up the install files, running the "sudo /opt/ice-client/agent uninstall" command merely confirms that the cleanup from the "sudo /opt/ice-client/agent unenroll" command was successful. Verify the Unenrollemnt in the AirWatch/Pulse Console 1. Return to the AirWatch/Pulse Lifecycle Management Console. It may be in the system tray from the previous steps. If it is not still open from previous steps, return to the Chrome browser and click the second tab for the AirWatch/Pulse Lifecycle Management Console. You may need to login again as the session may have timed out. The login is "administrator" and the password is "VMware1!" Page 118

119 Select The AirWatch Console Tab Page 119

120 Select Details View 1. Select "details view" Open The Device List View 1. Click on "List View" Page 120

121 Verify The Device Is Unenrolled The device is now reporting that is has been unenrolled Select The Gateway Click on the device name "VMwarehol_gateway1_70077" Page 121

122 Verify Device Unenrollment You will see the device has been unenrolled it will remain in this state until it is reenrolled or deleted. This concludes this optional step and concludes Module 2. Page 122

123 Troubleshooting If you do not receive the message "Registration Successful" and more than 5 minutes have elapsed then there is a problem with the Liota Agent. This is likely because the copy of the UserID/ password was not successful. Since the password is not visible to the user if the copy operaton fails and the password is not copied the authentication of the device to the Pulse server will not be successful. You will preform the following steps. 1. If the PuTTY window is not open, reopen the putty window. 2. Enter "CTRL-C" to terminate the current iotcc process. 3. Repeat all of the steps from "Initiate the Iotcc Client" with one exception, the Onboarding Credentials window will still be open, as depicted in the screen shot below. You will click on (2) "Generate Another Onboarding Credential" and then proceed with the rest of the steps listed under "Initiate the Iotcc Client" 4. If the registration of Liotd is successful skip ahead to "Verify Devices Were Registered" otherwise proceed to "Uninstall the Mis-generated Client" Restore the PuTTY window Page 123

124 If the PuTTY session window is not currently active, restore the PuTTY session by clicking on the link on the toolbar. In the PuTTY session window Enter "CTRL-C" to terminate the current iotcc process. Return to The Pulse Dashboard Return to the AirWatch/Pulse console to generate a new set of user/password credentials, click "ADMIN" on the left hand side menu. Page 124

125 Generate Another Set of One-time Use Credentials Click "Generate Another Onboarding Credentials". The credentials generated previously are no longer valid, these are one time credentials. Initiate The Copy of The One-time Use Credentials Page 125

126 As you did previously, you will be copying a new set of credentials to the PuTTY window. Again tale care to use the "Copy" button and not cut/paste or drag and drop. Copy The One-time Use Login Hitting the "Copy" key will cause the text to be highlighted in BLUE, again use the DO NOT use cut/paste use the (2) "Copy" button. Page 126

127 Paste The One-time Use Login to PuTTY Switch back to the PuTTY window, RIGHT click on "User ID" line, the User ID copied from the Pulse Administrator console should appear. Hit the enter key. Note the User ID is unique to your session and will differ from the User ID displayed above, the User ID generated will also differ from the one generated in the previous steps. the credentials are one-use and unique per registration. Page 127

128 Password Prompt The Password prompt now appears Page 128

129 Copy The One-time Use Password Return to the Pulse Administrator console, again use the "Copy" key to copy the password Hitting the "Copy" key will cause the text to be highlighted in BLUE,again use the DO NOT use cut/paste use the (1) "Copy" button. Page 129

130 Paste The One-time Use Password to PuTTY 1. As with "User ID" you will Right Click after "Password".Note you will not see any text copied, Linux does not display password text.hit enter after you copy the password. 2. In a minute or so you will see a message "Liotad started" this indicates the process to start the daemon on the appliance has started.this will take from 1-5 minutes, be patient. 3. If successful, you will see the message "Registration Successful" 4. Minimize do not close the Putty session as it will be required at the end of this Module If you do not receive the message "Registration Successful" and more than 5 minutes have elapsed then it is likely that the tar archive generated during the sideload generation steps was not successful. At this point you can repeat the steps to generate a new sideload file, copy the tar archive, unpack the tar archive and repeat the registration or you may choose to end this lab and start over. Page 130

131 Conclusion In this lesson you learned to : 1. Login to the Pulse IoT console. 2. Set the Organizational View. 3. Generate and download standard sideload package. 4. Install and register a edge device. In the next chapter you will learn how to customize a sideload package. You've finished Module 2 Congratulations on completing Module 2. If you are looking for additional information on IoT, try one of these: You can find more information about Liota on Github by clicking this link Or the QBR code below Proceed to any module below which interests you most. Module 1 - VMware Pulse IoT Center: Console Overview(30 minutes) (Basic) VMware Pulse IoT Center enables organizations to easily onboard, manage, monitor and secure diverse IoT edge systems and connected devices Page 131

132 through a single unified console. In this module, we will walk through the Pulse IoT Center console and learn how to navigate the dashboards, filter devices and view device details, create custom alerts, view notifications and manage admin users. Module 3 - VMware Pulse IoT Center: LIOTA (45 minutes) (Advanced) Liota is an open source project offering convenience for IoT solution developers to create edge system data orchestration applications. In this module we will help you become familiar with Liota. Please see GitHub for more information on this open source project How to End Lab If you wish to end your lab NOW please click on the END button. This will end your Hands On Labs session. Otherwise please continue to Module 1 or Module 3 as described on the previous step. Page 132

133 Module 3 - VMware Pulse IoT Center: LIOTA (45 minutes) Page 133

134 Introduction This Module contains the following lessons: Liota with VMware Pulse Quick Start Add Product for Metric Collection Project LIOTA PROJECT LIOTA - The Smart Little Agent for Big IoT For a truly seamless, end-to-end connected experience, it is important to create an IoT app framework that supports interoperability. One step in this direction is to implement a 3-tier architecture which connects your devices to the data centers via intelligent gateways. Although these gateways are excellent hubs, the problem of diverse IoT things in your organization being unable to speak the same language still persists.this is usually solved by creating different versions of an IoT application for different kinds of gateways/edge devices which can be a huge overhead. Liota was specifically created to simplify this task by providing a common model and building blocks for unified data acquisition and orchestration. What is Liota? Page 134

135 Liota is a vendor-neutral, open source SDK for building IoT gateway applications for managing, monitoring and orchestrating data between things, gateways and the cloud/ data center. Liota can help control where, when, and how to gather telemetry from connected devices and transfer it to the cloud/data center. It does this by providing complete abstractions to accelerate the development of IoT applications and simplify connection and control flows across the 3-tier architecture. Note that due to limitations in the simulated Hands On Labs environment that this lab is built with Pulse IoT release 1.0. Release 1.1 simplifies the enrollment experience, adds support for single sign on and improves the device reporting. For more information on Pulse IoT and the Pulse IoT 1.1 release please see our website : And our IoT 1.1 blog : For more information on the Pulse 1.1 product. Why should I use Liota? Liota is functionally useful on any IoT edge system, and any of its connected devices, that require management. Liota (written in Python) resides primarily on IoT gateways/ edge systems, and provides a common way for enterprises to manage and leverage multi-vendor gateways within their IoT infrastructures.it allows interaction between any device and any data-center component, over any transport, and through any IoT gateway/edge system. It is easy-to-use and has been successfully tested with many gateway and cloud components from both VMware and the community, such as AWS IoT, ThingWorx, IBM Bluemix, the open-source tool Graphite, and, of course VMware Pulse IoT Center. Key Components Key Components Liota applications are comprised of six basic abstractions that represent a complete data flow from a device attached to the edge system to an application in a data-center. They are loaded and unloaded with a Package Manager. Connected Device represents a device (a data-source attached to or on an IoT gateway or edge system) DeviceComms is an abstraction of the communication mechanisms between a device and an edge system Edge System represents the hardware and software platforms of an IoT gateway or edge system Metric represents a time-series stream from a data source to a datacenter application (a stream of (number, timestamp) tuples) Page 135

136 Data-Center Component is an abstraction of the protocol and formata datacenter component requires DCCComms is an abstraction of the communication mechanisms between the edge system and data-center Liota Dynamic Packages Package Manager allows the loading and unloading of Liota packages.a liota package is a Python class having: A dependency list (of other packages) Code to obtain configuration from registry and references to objects from other packages A run method A clean_up method LIOTA on Github Contributing to Liota Want to hack on Liota and add your own DCC component? Awesome! Just fork the project in order to start contributing the code. Page 136

137 Liota with VMware Pulse Quick Start In this lesson, you will modify some configuration files, upload to Pulse to generate a new Sideload package which you will use to enroll gateway2. Login to Pulse IoT Center Console You will begin by logging into the Pulse IoT Center Console. 1. Double-Click on the Google Chrome shortcut on the desktop to launch the browser. Page 137

138 Login to Pulse IoT Center Console 1. Click on the VMware Pulse bookmark from the Bookmarks Toolbar. 2. Under Username, enter sysadmin. This is the default admin username for VMware Pulse IoT Center. 3. Under Password, enter VMware1! 4. Click on the Login button to continue. Page 138

139 Dashboard From the Dashboard, you are going to launch the Lifecycle Management Console. 1. Click on OTA Updates from the left navigation pane. Page 139

140 Lifecycle Management Console 1. Click PROCEED to continue. Page 140

141 Lifecycle Management Console 1. For User name, enter administrator 2. For Password, enter VMware1! 3. Click Log In to continue. Page 141

142 Configuration Files Now you are in the organization named VMware. 1. Verify that the top header says VMware. 2. Double-click on the folder named Liota on the Desktop to open it. NOTE: You may have to make the browser window smaller to see the Desktop. 3. In this folder, you have several files related to LIOTA. You are going to modify one of its files. Right-click on general_edge_system.py and select Open with Edit with Notepad++. general_edge_system.py The sample package contains specifications of GeneralEdgeSystem, replace the "EdgeSystemName" with the logic to auto-generate the unique name every time this package is loaded based on the user flow. Unique identifier can be from the system(mac address) or devices to generate the unique name. Page 142

143 Edit general_edge_system.py In this example, you are going to change the name of the EdgeSystem you will enroll with Pulse IoT Center. Feel free to use your own name in the format of FirstnameLastname1. 1. Edit the name of the GeneralEdgeSystem to be FirstnameLastname1. 2. Click the Save icon up top to save the file. 3. Close the Notepad++ editor by clicking on the Red X. Page 143

144 Files/Actions Back on the Lifecycle Management Console, you will now Add the Files/Actions. NOTE: If at any point during the lab your login session to the Lifecycle Management Console expires, you can re-login to the Lifecycle Management Console using the username/password: administrator/vmware1! 1. With the Devices menu selected on the left, select Staging & Provisioning to expand its submenus. 2. Under Staging & Provisioning, select Components. 3. Under Components, select Files/Actions. 4. Now you are at the Files/Actions page, click on Add Files/Actions to continue. Page 144

145 Add Files/Actions 1. Select Linux to continue. Page 145

146 Add Files/Actions 1. Here you will give this Files/Actions a name. Feel free to use your own name in the format of FirstName LastName. This name will be used later when you select it to be included in the Sideload Package. NOTE: The EdgeSystem name you will use is in the format of FirstnameLastname1, which is different from this name. 2. Leave the rest as defaults and click the Files tab to continue. Page 146

147 Add Files/Actions Now you will add the edited general_edge_system.py file into the system. 1. Under the Files Tab, click on Add Files. Add Files/Actions 1. Click on Choose Files button to choose the file. Page 147

148 Add Files/Actions 1. From the Open file dialog within the Desktop folder, click on the Liota folder. NOTE: You may have to click on the Desktop folder on the left if you are not already in the Desktop folder. Page 148

149 Add general_edge_system.py 1. Click on general_edge_system.py to select this file to add. Remember, this is the file that you modified. 2. Click Open to continue. Add Files/Actions 1. Now that you have chosen the file, click Save to continue. Page 149

150 Add Files/Actions You will provide the Download Path (the path on the gateway where you want to upload this file to) in this window. 1. For Download Path, enter the path /opt/liota-packages/ 2. Click Save to continue. Page 150

151 Add Files/Actions Now you will add one more file. 1. Click on Add Files again. Page 151

152 Add Files/Actions 1. Click on Choose Files button to choose the file. Page 152

153 Add iotcc_mqtt.py 1. Click on iotcc_mqtt.py to select this file to add. 2. Click Open to continue. iotcc_mqtt.py This is a sample user package which creates a IoTControlCenter DCC object and registers edge system on IoTCC over MQTT Protocol to acquire "registered edge system", i.e. iotcc_edge_system. This package has dependency on credentials package which is pre-loaded during the installation in order to provide the required credentials and configuration parameters in the liota package manager registry. The properties for the edge system can be set as 'key:value' pair, you can also set the location by passing the 'latitude:value' and 'longitude:value' as properties in the user package. If the unregister call is included in the clean up method then the resource will be unregistered and the entire history will be deleted from Pulse IoT Control Center so comment the logic if the unregistration of the resource is not required to be done on the package unload. The retry mechanism has been implemented for important calls like registration, create_relationship or set_property in case of exception. User Configurable Retry and Delay Settings can be tweaked by user as per the targeted scale. Page 153

154 Add Files/Actions 1. Now that you have chosen the file, click Save to continue. Add Files/Actions You will provide the Download Path (the path on the gateway where you want to upload this file to) in this window. Page 154

155 1. For Download Path, enter the path /opt/liota-packages/ 2. Click Save to continue. Add Files/Actions 1. Click Save to Add these files. Page 155

156 Staging Now you are going to the Staging section. In Staging, you are going to create a Sideload Package which will Add Files of the name FirstName LastName that you just defined in the last few steps. 1. Under Staging & Provisioning, select Staging to continue. Staging 1. Click the Add Staging button. Page 156

157 Add Staging 1. Click Linux to continue. Page 157

158 Add Staging Under the General tab: 1. For Name, enter FirstName LastName. Again, feel free to use your own name if you would like. 2. For Agent, select from the drop-down menu Pulse-Linux-x86_ Note: If the version number is higher, it is ok. Select the one with x86_64 in the name. 3. Click on the top Manifest tab to continue. Page 158

159 Add Staging You are now going to add a couple of Files/Actions to create the Sideload package. 1. Click Add. Page 159

160 Add Staging In this first action, you will tell it to install a root cert. 1. For Action(s) To Perform, select Install Profile. 2. For Profile, click in the text box and select root cert 3. Click on Save to continue. Page 160

161 Add Staging 1. Click Add to add another Action. Page 161

162 Add Staging For this second action, you will tell it to add the Add File named FirstName LastName that you created in the previous section. 1. For Action(s) To Perform, select Install Files / Actions from the drop-down menu. 2. For Files/Actions, Start typing FirstName LastName and select the name FirstName LastName. Note: If you used your own name for this, make sure you type in the corresponding name. 3. Click Save to continue. Page 162

163 Add Staging You now have the two actions defined. This will be the Sideload package that you will generate which will install the root cert and add the corresponding files that you defined. 1. Click Save to continue. Page 163

164 Sideload Now that you have the Staging named FirstName LastName defined, you will use it to generate a Sideload Staging Package. 1. In the FirstName LastName row, click on the Sideload icon to generate a Sideload Staging Package. Generate Sideload Staging Package Page 164

165 The default Organization Group should be listed as VMware by default. 1. For Passphrase, you will enter VMware1! 2. Click Download to continue. This will generate a tar.gz file to your local Downloads directory. SCP Sideload Staging Package to gateway2 With the tar.gz file download completed, you will now launch SCP to gateway2 to copy the Sideload Package to gateway2. 1. Double-click on the gateway2 icon on the Desktop. Page 165

166 SCP Sideload Staging Package to gateway2 This launches the WinSCP app, you will now use this to SCP the tar.gz file up to gateway2. 1. Click the SideLoadStaging_FirstNameLastName_VMware.tar.gz file and drag it to the default /tmp directory on gateway2. SCP Sideload Staging Package to gateway2 1. Verify the SideLoadStaging_FirstNameLastName_VMware.tar.gz file is now in the /tmp directory. 2. Close WinSCP by clicking on the Red X button. 3. Click OK to terminate the session and close WinSCP. Page 166

167 SSH to gateway2 Now you will SSH to gateway to unpack the Sideload Package and install the Client. 1. Click on the PuTTy icon from the taskbar to launch it. Page 167

168 SSH to gateway2 1. Click on gateway2. 2. Click Open to continue. Page 168

169 Login to gateway2 1. Login as holuser, no password is required. Page 169

170 Extract SideLoadStaging File Now you will extract the tar.gz file. 1. Enter cd /tmp 2. Enter ls to display the files. The SideLoadStaging_FirstNameLastName_VMware.tar.gz file should be there. 3. Enter tar -xvzf SideLoadStaging_FirstNameLastName_VMware.tar.gz to untar the file. Page 170

171 Client Install You will now install the Client. 1. Enter cd agent 2. Enter ls to see the ice-client-linux-x86_ sh file exists. 3. Enter sudo./ice-client-linux-x86_ sh to execute the script. Continue in the next step. Page 171

172 Enter the Passphrase 1. Enter the Passphrase: VMware1! Note: This should match what you defined from the console. Page 172

173 Installation successful 1. You should get an Installation successful message. Page 173

174 Register the Edge System Notice it states to run /opt/ice-client/iotcc to register the Edge System. That is what you will execute next. 1. Enter sudo /opt/ice-client/iotcc. See the next few steps for the Onborading Credentials (User ID and Password). Page 174

175 Generate Onboarding Credentials You will go to the console to generate the Onboarding Credentials. 1. Select your first browser tab, VMware Pulse. This should be your Pulse IoT Console. 2. On the left navigation pane, click on ADMIN. 3. Click on the Onboarding Credentials button on the upper-right. Page 175

176 Generate Onboarding Credentials 1. Click on the Generate Onboarding Credentials button. Page 176

177 Generate Onboarding Credentials From this Onborading Credentials screen, you see the Login User ID and Password provided. There are Copy buttons available to use to copy the long text into the Clipboard. 1. Click on the Copy button next to the Login User ID. Page 177

178 Generate Onboarding Credentials Back in the gateway2 PuTTy session you will now paste the User ID. 1. Right-click on the mouse to Paste the User ID to the terminal. Page 178

179 Generate Onboarding Credentials You will now repeat the same for the Password. 1. Click on the Copy button next to the Password. Page 179

180 Registration successful Back in the gateway2 PuTTy session you will now paste the Password. Note: This time you will not see the hidden password, but it should be pasted. If it does not work the first time, you may want to try again. 1. Right-click on the mouse to Paste the Password to the terminal. You should see the Liotad (Liota Daemon) started and Registration of the EdgeGateway to the Pulse IoT Center successful. Page 180

181 Registration successful 1. Back to the Pulse IoT Console, you can now click the Close button. Page 181

182 Dashboard 1. Again, verify you are on the first browser tab, VMware Pulse. This is the Pulse IoT Console. 2. Select Dashboard from the left navigation pane if it is not already selected. 3. On the right search box, start entering the text FirstnameLastname1 to search for the EdgeGateway. NOTE: Your EdgeGateway name may be your own name and should be in the format FirstnameLastname1. 4. Select the FirstnameLastName1 EdgeGateway to view its Dashboard. Validate 1. Validate the FirstnameLastname1 Edge System Dashboard appears. Page 182

183 Validate 1. Back on the second browser tab, Lifecycle Management Console - Staging & Provisioning. 2. Click Cancel to continue. Page 183

184 Validate 1. Under DEVICES -> List View, you should now see the list of devices. 2. The List View should show the new EdgeGateway FirstnameLastname1. Page 184

185 Add Product for Metric Collection In this lesson, you will create a new software package that will be deployed to the gateway. This will then publish some new metrics to the Pulse IoT Console. Files/Actions Note: You may have to re-login again if your session has ended. The username/password for this Lifecycle Management Console is administrator/vmware1! You will now Add some Files and Actions to perform to gather some metrics from our EdgeGateway. 1. Make sure you are on the second browser tab which is the Lifecycle Management Console. 2. DEVICES should be selected on the left navigation pane. 3. Select Staging & Provisioning. 4. Select Components. 5. Click on Files/Actions. 6. Click on the Add Files/Actions button. Page 185

186 Add Files/Actions 1. Click Linux to continue. Page 186

187 General 1. In the General tab, for Name enter Metric Collection. 2. Select the Files tab to continue. Page 187

188 Files 1. Under the Files tab, you will now click on Add Files. Add Files 1. Click on Choose Files button to choose the file. Page 188

189 Add Files 1. Click on iotcc_mqtt_edge_system_stats.py to select this file to add. 2. Click Open to continue. iotcc_mqtt_edge_system_stats.py This is a sample user package to publish the basic edge system stats which we believe are required to monitor the health status of the edge system from Pulse IoT Control Center. Optional mechanism: If the device raises an intermittent exception during metric collection process it will be required to be handled in the user code otherwise if an exception is thrown from user code the collection process will be stopped for that metric. If the None value is returned by User Defined Method(UDM) then metric value for that particular collector instance won't be published. Page 189

190 Add Files 1. Now that you have chosen the file, click Save to continue. Add Files You will provide the Download Path (the path on the gateway where you want to upload this file to) in this window. Page 190

191 1. For Download Path, enter the path /usr/lib/liota/packages 2. Click Save to continue. Manifest 1. Select the Manifest tab. 2. Click Add Action to Install a Manifest. Page 191

192 Add Manifest: Action to Perform: Run Under Add Manifest, you will now select an Action(s) to Perform. 1. From the Action(s) to Perform drop-down menu, select Run. Page 192

193 Add Manifest Command Line and Arguments to run 1. The Command Line and Arguments to run will be in the format of /usr/lib/liota/packages/liotad/liotapkg.sh load filename hashvalue Filename will be iotcc_mqtt_edge_system_stats (without the.py extension) and you will need to find the hash value of the file in the next step and it will be 57f cb2b15148d86b2e7f2c451f74b9d You can leave this field blank for now. You will enter it once you find the hash value in the next step. 2. Click on the Windows Command Prompt icon to launch a prompt so you can find out the hash value of this file. Page 193

194 Find the hash value of iotcc_mqtt_edge_system_stats.py file 1. At the Windows Command Prompt, type cd Desktop\Liota 2. Type dir at the prompt to see a directory listing to verify the file iotcc_mqtt_edge_system_stats.py exists in the folder. 3. Type certutil -hashfile iotcc_mqtt_edge_system_stats.py SHA1 This SHA1 hash value of 57f cb2b15148d86b2e7f2c451f74b9d is what you need for the Manifest Command Line argument. Page 194

195 Add Manifest Command Line and Arguments to run 1. You will now enter the full command: /usr/lib/liota/packages/liotad/ liotapkg.sh load iotcc_mqtt_edge_system_stats 57f cb2b15148d86b2e7f2c451f74b9d NOTE: You may select the text from this manual and drag the text into the lab environment textbox as a shortcut instead of typing this. 2. Click Save to continue. Page 195

196 Save You now have an Action defined to load the file. 1. Click Save to continue. Page 196

197 Add Product Now you are going to add a new product. 1. Select Product List View. 2. Click on Add Product. Page 197

198 Add Product 1. Click Linux to continue. Page 198

199 Add Product: General 1. Enter the Name: Metric Collection 2. Under Assignment Groups, start typing VMware and select the VMware (VMware) group that pops up. 3. Select Manifest tab to continue. Page 199

200 Add Manifest 1. Click on Add button to add a Manifest. Page 200

201 Add Manifest 1. For Action(s) to Perform, select Install Files / Actions 2. For Files/Actions, start typing Metric Collection and select the Metric Collection Files/Actions that you defined in an earlier step. 3. Click Save to continue. Page 201

202 Activate Now that you have the new Product named Metric Collection defined, you are now ready to Activate it. 1. Click on Activate button to activate this product. Page 202

203 View Device Assignment In this screen, you can see the devices that you can assign to. 1. Click on Activate button to assign the Product Metric Collection to the device(s). Page 203

204 SSH to gateway2 Now that you have activated the new product, you are going to see if it is publishing the metrics to the Pulse IoT Center. 1. Click on the PuTTy icon to launch the PuTTY Client to SSH to gateway2. Page 204

205 SSH to gateway2 1. Click on gateway2. 2. Click Open to continue. Page 205

206 tail liota.log 1. Login as holuser 2. At the prompt, type tail -f /var/log/liota/liota.log You should see some metrics being published to Pulse IoT Center. NOTE: Although you see the metrics here, there may be a 5-10 minutes delay before it will show up on the console. Page 206

207 Dashboard 1. Click on the the first browser tab, and this should take you to the main Pulse IoT Console. 2. Click on Dashboard if it is not already showing the main Dashboard view. 3. From the drop down menu on the left column, select All Managed Objects. 4. You should see the Edge System named FirstNameLastname1 on the list. Click on this Edge System to continue. Page 207

208 Edge System Dashboard You are now at the Edge System Dashboard. 1. Click the scroll bar to get to the Edge System Metrics section. Page 208

209 Edge System Metrics This is where you will see the new metrics published shortly. You will not see the Edge System Metrics right away. If you are willing to wait and refresh the screen after about 5-10 minutes, you will see the Edge System Metrics being captured in this dashboard view. You know the metrics are being published when you reviewed the liota.log a few steps before this. Page 209

210 Conclusion In this module you modified some LIOTA configuration files, Added Files to Pulse IoT to generate a new Sideload package which you then used to enroll gateway2. You then created a new software package that you deployed and activated to the gateway to publish some new metrics to the Pulse IoT Console. You've finished Module 3 Congratulations on completing Module 3. If you are looking for additional information on Pulse IoT and LIOTA, try one of these: Pulse IoT Center - LIOTA - Proceed to any module below which interests you most. Module 1 - VMware Pulse IoT Center: Console Overview(30 minutes) (Basic) VMware Pulse IoT Center enables organizations to easily onboard, manage, monitor and secure diverse IoT edge systems and connected devices through a single unified console. In this module, we will walk through the Pulse IoT Center console and learn how to navigate the dashboards, filter devices and view device details, create custom alerts, view notifications and manage admin users. Module 2 - VMware Pulse IoT Center: Onboard and Update IoT Gateway (30 minutes) (Basic) In this module you will walk through the steps to onboard an IoT gateway into VMware Pulse IoT Center and view live metrics from the device in the console. You will also deploy an over-the-air (OTA) product to update the gateway. Page 210