Symptoms With EFM 1.7 release, some previous warnings are now treated as errors, hence ParStream does not start via Systemctl Diagnosis Check the /var/log/parstream/server-xxxx.log file You might see errors like:   ERROR-77082: Number of maximum file descriptors (1024) is lower than recommended value 98304 ERROR-77113: Maximum number of mmap'ed areas (65530) is lower than recommended value 1966080. Solution ERROR-77082: Number of maximum file descriptors (1024) is lower than recommended value 98304 Include  LimitNOFILE=98034         in the "Service" section of the parstream systemd service file ( /usr/lib/systemd/system/parstream-database\@.service)   ERROR-77113: Maximum number of mmap'ed areas (65530) is lower than recommended value 1966080 Include the mmap config in  /etc/sysctl.conf vm.max_map_count=1966080 ... View more

Q. Where can I find the Cisco Kinetic DemoKit Setup Guide? A. Refer to the "Cisco Kinetic Demo Kit Guide" on Salesconnect (https://salesconnect.cisco.com/#/program/PAGE-10238 then under the "Demo Kit" tab )   Q. Where can I get support for the DemoKit? A. For support, visit the QPCS Knowledge base: http://kinetic.intellisite.io     Email: cisco-help@intellisite.io       Telephone: 888-410-4240 extension 280   Q. How do I order additional kits or renew license for realtime dashboards? A. Contact TechData for additional kits and license:     iot@techdata.com     (727) 539-7429 ext. 66100   Q. I am a Cisco Employee; how do I order the DemoKit and configure it? A. For Internal Cisco Kinetic DemoKit orders: Purchase IR829 via iProcurement and provision the gateway with GMM image: IR829 provisioning: https://developer.cisco.com/docs/kinetic/#!provision-a-gateway-cisco-gpt Purchase the Demokit without the IR829: Email cisco-help@intellisite.io to get a quote for the demokit and purchase it via iProcurement (NRE, NPI, Prototypes …. And vendor name “QPCS”) Login into Kinetic GMM cloud portal Folks with cisco.com email-id: “Create Account” on GMM portal https://developer.cisco.com/docs/kinetic/#!log-in/prerequisites Folks without cisco.com email-id: “Support” link to request account or GMM Pilot sign-up http://go2.cisco.com/gmmpilot   Add your new gateway to GMM https://developer.cisco.com/docs/kinetic/#!claim-gateways GMM Org: If using the “DemoKits” Org on the GMM US Cluster: (The “DemoKits” org is for gateways owned by the BU and Kinetic TSAs) Use template “DemoKit-CustomSubnet” For non BU and non-TSA users, your GMM login should provide you with a default Organization.   Login Information: Refer to the earlier sections of the DemoKit Setup Guide The NUC in the demokit should already have Ubuntu installed, configured as 192.168.100.3 and EFM installed IOx Application: The “DemoKits” Org already has the appropriate IOx application “EFM Demokit v1.2.2” For other GMM Orgs: Use the preconfigured EFM IOx application (efm_1_2_2_x86_64_demokit.tar.gz) https://cisco.box.com/v/demokitEFMapp The EFM IOx app in the IR829 is pre-configured. So, it should be able to connect to the Modbus PLC and extract data and connect upstream to the NUC (192.168.100.3) Configure the EFM Dataflow on the NUC (https://192.168.100.3:8443/dataflow.html) Verify you can see the downstream IR829 based EFM broker Open IR829 EFM dataflow: Update the “DemoKit ID” string to “Demokit-XXX” (XXX – your initials) Verify the Modbus DSlink connection is “Ready” and “Connected” Verify data is flowing in the dataflow from the PLC Verify data is being published to “data” node. Note down the parameter under data node (Ex: DemoKit) Open the NUC dataflow Verify the data from IR829 EFM broker is being received May need to update the “path” of the first block in the dataflow. It should match the “data” publish parameter on the IR. (Ex: /downstream/DemoKit809Broker/data/DemoKit) Update MQTT connection to DCM in NUC EFM https://developer.cisco.com/docs/kinetic/#!efm-to-dcm-via-mqtt Open NUC EFM dataflow Update the MQTT publish topic to match the newly created device topic. Now verify the MQTT connection shows as “Connected” Realtime Dashboards on NUC Open NUC Dataflow Editor (https://192.168.100.3:8443/dataflow.html) and then open https://192.168.100.3:8443/ This will open the DGLux designer page. Request a 180 day license. The license is auto-generated. Refresh the page after submission ... View more

EFM v1.6.1 IOx application now supports passing parameters via GMM. This capability now enables configuring an upstream broker for that EFM node via GMM UI.   Step 1: Install EFM 1.6.1 IOx app within GMM Step 2: Deploy this app on a gateway (The upstream broker can be configured in this step also.)     Step 3: After the app is deployed and started, open the app to reveal the application parameters and logs       Step 4: Configure upstream broker. (This will restart the app with the new configuration) Ignore the OPTIONAL tag for the fields. Follow the guidelines below.   Mandatory fields in "upstream" section: url : URL of the upstream broker  EFM 1.6 and later -> https://<Upstream Server>:443 EFM 1.5 and earlier -> https://<Upstream Server>:8443 enabled : change to "true" to enable the connection name : Local name of the connection, visible only to current node brokerName : Upstream name of the connection, visible to the upstream node (The default value is a IOX variable "${CAF_SYSTEM_NAME}", which provides the Serial Number of the IOx gateway.)   Optional fields in "upstream" section: group, token   Optional section: "ssl"   ... View more

  There are a couple of ways to connect EFM with DCM: DCM DSLink Using MQTT DSLink The MQTT method is outlined here. Install and start MQTT DSLink on EFM node         From dataflow editor page: Configure the MQTT link to connect to DCM   name <Any Name> URL ssl://us.ciscokinetic.io (or ssl://eu.ciscokinetic.io ... depending on which Kinetic cluster the gateway is managed from) username <Gateway user ID from Kinetic> see Kinetic screenshot below password  <Gateway password from Kinetic> see Kinetic screenshot below clientID  <Any unique ID> cert  <cert file from Kinetic> (see attached file)     Once the MQTT connection is configured. You can right click on the mqtt connection and choose "publish" operation (or click and drag the publish operation onto to the dataflow) to publish to DCM The MQTT topic to be used is also listed in the above picture with gateway details. (Use the observation topic) When using the MQTT Publish block in a dataflow, remember to set the "autorun" property to "true", so that any value/input change triggers a publish.     ... View more