Establishing a Litmus Edge-Litmus Edge Manager Connection: From the Litmus Edge Manager Side

for details on the litmus edge side of port customization, see establishing a litmus edge litmus edge manager connection from the litmus edge side docid\ ckervyedbx0b2osvnatbj a litmus edge instance is activated by the litmus edge manager in the following set of steps litmus edge user enters activation url and activation code see step 2 create an activation request in litmus edge section of activate an edge device docid\ tdj648wjgatvqzyx79uwb for details litmus edge attempts to establish an initial connection with inbound port 443/tcp (https) of litmus edge manager litmus edge manager receives the connection at its inbound port 443/tcp (https) litmus edge sends an activation request that is received, and approved by litmus edge manager see step 3 approve the activation request in litmus edge manager section of activate an edge device docid\ tdj648wjgatvqzyx79uwb for details litmus edge sends activation requests on port 443/tcp of litmus edge manager litmus edge manager user accepts the activation request in ui litmus edge manager responds to the activation request with litmus remote credentials litmus edge attempts to establish a permanent connection with inbound port 51820/udp (remote access) of litmus edge manager litmus edge manager receives the connection at inbound port 51820/udp (remote access) litmus edge confirms the permanent connection with litmus edge manager the permanent connection becomes a secure two way (bi directional) connection both litmus edge and litmus edge manager use litmus edge's to litmus edge manager's inbound port 51820/udp (remote access) to communicate with each other port customization for litmus edge manager open 443 (https) inbound/ingress to receive the initial contact from litmus edge open 51820 (remote access) inbound/ingress to receive the permanent connection from litmus edge ensure all outbound communication is available to be able to reach litmu s edge additional connection supporting litmus edge's default generic mqtt ssl connector to litmus edge manager after a litmus edge litmus edge manager connection has been established, the litmus edge manager can receive metrics docid\ xz4okukesfg7rdekrlhpu data or events docid\ qh9pncut g1k lz9p4 m3 data (enabling event forwarding is needed) from a litmus edge instance for litmus edge manager to receive the data, the litmus edge instance must enable its default generic mqtt ssl connector ( integration docid\ wpqo1fe02tmx3askewqu6 ) once the connector is enabled, the litmus edge instance will attempt to reach a connection at litmus edge manager's inbound port 8883/tcp note ports 443 and 51820 are required for establishing the initial connection port 8883 is used for ongoing data transmission once the connection is in place for additional details about each port, please refer to the system requirements docid\ vcocnbl2dlgagwsj3ycdm port customization for litmus edge manager open 8883 (mqtt) inbound/ingress to receive the special data from litmus edge