Single Hub and Multi-Spoke Deployment Scenario

this example shows you how to configure a hub and spoke edge cascading architecture where multiple spoke instances in the ot layer stream data to a single hub instance in the dmz layer scenario a manufacturing facility has two production lines, each with its own litmus edge instance collecting data from plcs, sensors, and scada systems the facility needs to aggregate this data in a dmz layer before publishing to cloud services and enterprise systems architecture in this example le coll 1 (spoke) collects data from production line 1 devices le coll 2 (spoke) collects data from production line 2 devices le 3 dmz (hub) aggregates data from both production lines and publishes to cloud services network topology ot network le coll 1 and le coll 2 are deployed at level 2/3 dmz network le dmz is deployed in the dmz layer firewall port 7422 is open on the dmz firewall for hub access connection direction spoke instances initiate outbound connections to the hub (no inbound connections required in ot) configuration workflow to configure the hub and spoke architecture enable edge cascading v2 on all instances configure le dmz as a hub instance create two accounts on le dmz (one for each production line) configure firewall rules on le dmz copy account tokens from le dmz configure le coll 1 and le coll 2 as spoke instances add stream connections on both spoke instances verify connections and data flow note in this example, account permissions are defined with topics which may not existing in your litmus edge instance(s) please define account permissions with topics that are present in your spoke litmus edge instances step by step configuration step 1 enable edge cascading v2 on all instances on each litmus edge instance (le coll 1, le coll 2, and le dmz) navigate to datahub > edge cascading set enable litmus edge cascading configuration to enabled step 2 configure le dmz as hub set instance type on le dmz navigate to datahub > edge cascading click the instance type dropdown and select hub click apply and then proceed create account for production line 1 on le dmz , create an account for le coll 1 click the accounts tab click add account and enter line1 collector in account name and click apply click the action menu (three dots) for the line1 collector account and select edit add the following topics devicehub alias plc1 > devicehub alias sensor1 > in prefix , enter from line1 click apply to save the configuration 2 3 create account for production line 2 on le dmz , create an account for le coll 2 click add account in account name , enter line2 collector and click apply click the action menu (three dots) for the line2 collector account and select edit add the following topics devicehub alias plc2 > devicehub alias sensor2 > in prefix , enter from line2 click apply to save the configuration 2 4 restart message broker on le dmz click restart to activate both accounts wait for the status to show connected with a green indicator 2 5 configure firewall rule on le dmz navigate to system > network > firewall > inbound rules click add rule enter the following details port 7422 protocol tcp interface select your dmz interface (e g , eth0) description edge cascading hub inbound access click add rule 2 6 copy account tokens on le dmz from the accounts tab, click the action menu for line1 collector and select view token click copy and save the token (you will use it on le coll 1) repeat for line2 collector and save the token (you will use it on le coll 2) step 3 configure le coll 1 as spoke 3 1 set instance type on le coll 1 navigate to datahub > edge cascading click the instance type dropdown and select spoke click apply and then proceed 3 2 add stream connection on le coll 1 in the streams tab, click add stream enter the following details token paste the token from the line1 collector account enable tls leave unchecked (unless tls is configured) click add stream 3 3 apply and verify connection on le coll 1 click restart to apply the stream configuration verify the status shows connected with a green indicator step 4 configure le coll 2 as spoke 4 1 set instance type on le coll 2 navigate to datahub > edge cascading click the instance type dropdown and select spoke click apply and then proceed 4 2 add stream connection on le coll 2 in the streams tab, click add stream enter the following details stream name to dmz hub token paste the token from the line2 collector account enable tls leave unchecked (unless tls is configured) click add stream 4 3 apply and verify connection on le coll 2 click restart to apply the stream configuration verify the status shows connected with a green indicator step 5 verify data flow on hub on le dmz , verify that data from both production lines is flowing test data in analytics navigate to analytics create a datahub subscribe processor and enter from line1 devicehub alias plc1 temperature from line2 devicehub alias plc2 temperature enable the debug button on the analytics processor to see the data in the debug console data flow example original topics on spoke instances le coll 1 publishes devicehub alias plc1 temperature devicehub alias plc1 pressure devicehub alias sensor1 status le coll 2 publishes devicehub alias plc2 temperature devicehub alias plc2 pressure devicehub alias sensor2 status prefixed topics on hub instance after streaming through edge cascading, le dmz receives from le coll 1 from line1 devicehub alias plc1 temperature from line1 devicehub alias plc1 pressure from line1 devicehub alias sensor1 status from le coll 2 from line2 devicehub alias plc2 temperature from line2 devicehub alias plc2 pressure from line2 devicehub alias sensor2 status the prefixes ensure there are no topic name conflicts when aggregating data from multiple sources