Edge Cascading v2 Configuration

this guide explains the configuration options available for edge cascading v2 for complete setup examples, see the docid\ lji4culciksylbtfiz5j9 topic prerequisites before configuring edge cascading v2 litmus edge version all instances must be on version 4 0 5 or newer network connectivity ensure network connectivity between hub and spoke instances firewall access port 7422 must be accessible on hub instances for incoming connections enable edge cascading v2 before configuring any instance, enable the edge cascading v2 beta feature navigate to datahub > edge cascading set enable litmus edge cascading configuration to enabled instance types hub accepts incoming connections from spoke instances and aggregates data when to use deploy at aggregation layers (dmz and it) where data from multiple sources converges configuration access manage incoming connections in the accounts tab monitoring activity in the logs tab spoke initiates outbound connections to hub instances and streams data upward when to use deploy at edge collection points (ot layer) where data originates configuration access manage outbound connections in the streams tab monitor activity in the logs tab both (hybrid) acts as both hub and spoke simultaneously, accepting incoming connections and initiating outbound connections when to use deploy at intermediate layers (dmz) that aggregate data from lower levels and stream to higher levels configuration access manage incoming connections (hub mode) in the accounts tab manage outbound connections (spoke mode) in the streams tab monitor activity in the logs tab hub configuration accounts accounts define authentication and permissions for spoke instances connecting to a hub to create an account navigate to datahub > edge cascading > accounts click add account enter an account name and click apply click the action menu (three dots) for the account and select edit add topics and prefix as needed click apply to save the configuration click restart to activate the account account settings account name descriptive identifier for the account alphanumeric characters only, no spaces, and a maximum 100 characters must be unique within the hub instance topics defines which data streams the spoke can access you can add multiple topics per account supports standard topic naming alphanumeric, hyphens, underscores, periods use the forward slash > wildcard at the end to match all subtopics (for example, devicehub alias device1 >) each topic is evaluated independently prefix automatically prepended to all topics from this account helps identify data source when aggregating from multiple spokes cannot contain wildcard characters example prefix from line1 transforms devicehub alias plc1 temp to from line1 devicehub alias plc1 temp account tokens after creating an account, generate and copy the authentication token click the action menu (three dots) for the account select view token click copy to copy the token provide the token to the spoke instance administrator token security tokens are encrypted and contain connection details store tokens securely and share tokens only with authorized spoke administrators tokens remain valid until manually reset token management to reset a token navigate to accounts tab click the action menu for the account select reset token copy the new token and update all connected spoke instances important resetting a token immediately disconnects all spoke instances using the old token firewall configuration hub instances require inbound access on port 7422 manual configuration navigate to system > network > firewall > inbound rules click add rule configure port 7422 protocol tcp interface select your network interface description edge cascading hub inbound access spoke configuration streams streams define outbound connections from a spoke instance to hub instances to add a stream navigate to datahub > edge cascading > streams click add stream configure stream settings click validate and click save click restart to establish the connection stream settings token authentication token from the hub instance account contains hub connection details and permissions paste the complete token provided by the hub administrator enable tls optional encryption for data in transit when enabled, provide tls certificates must match hub tls configuration recommended for production deployments stream status after applying the configuration, verify the connection status connected (green) active connection to hub disconnected (yellow) connection lost, attempting reconnection failed (red) connection error that requires intervention connection validation checklist hub instance is online and accessible firewall rules allow port 7422 access to hub token is valid and not reset network connectivity between spoke and hub multiple streams a spoke instance can connect to multiple hub instances simultaneously use cases redundant data paths for high availability streaming different topics to different hubs multi site data distribution each stream operates independently with its own token and permissions hybrid configuration hybrid instances combine hub and spoke functionality configure the accounts tab for incoming spoke connections (hub mode) configure the streams tab for outgoing hub connections (spoke mode) restart to activate all configurations both sets of connections operate independently and can be configured in any order monitoring and verification connection logs view detailed logs for troubleshooting and monitoring navigate to datahub > edge cascading > logs review connection events, authentication results, and data flow use time range selector for historical logs click download logs for offline analysis connection dashboard monitor real time status and metrics navigate to datahub > edge cascading > dashboard review connection status for all streams and accounts with these metrics connection uptime data throughput authentication events error counts data flow verification verify data is flowing correctly on hub instances navigate to flows manager or analytics subscribe to prefixed topics for example, if prefix is from lecoll1 and original topic is devicehub alias device1 tag1 , subscribe to from lecoll1 devicehub alias device1 tag1 verify data appears with correct prefixes advanced configuration tls encryption hub tls configuration perform the following on the instance enabled as a hub navigate to datahub > edge cascading select the enable tls checkbox in the enable tls dialog, confirm that you want to enable tls by clicking enable tls click the lock icon 🔒to view the ca certificate copy and save the ca certificate in a secure location you will apply the certificate on all spoke instances click restart spoke tls configuration when adding a stream connection, you can enable tls for the connection to the hub instance click the add stream button in the stream configuration section in the stream configuration dialog, select enable tls after saving the stream connection, the ca certificates section displays click the add certificate button paste the ca certificate that you copied from the hub instance click save copy the hub hostname and connection url ip address for example hub hostname litmus edge 005057b908d7 connect url ip 10 17 10 20 navigate to system > network > dns/ntp servers in the host file section, click add a new host binding enter the ip address and host name of the hub instance navigate back to datahub > edge cascading and restart by clicking the restart button for more information on host file mapping, see https //app archbee com/docs/wraxt1hpevkwz3x orupb/pgzwsr3dtjm4dgl2x93ab#k8ngu note hub and spoke tls settings must be compatible host file entry on spoke instance with details to hub instance is required for successful connection configuration restart most configuration changes require restarting the message broker click restart on the edge cascading page the message broker restarts with new configuration connections re establish automatically and no system reboot is required restart triggers instance type changes new or modified accounts (hub) new or modified streams (spoke) tls configuration changes