Set up Lighthouse as a Connected Resource Gateway (CRG)

Notes: Opengear is transitioning from Automation Gateway (AG) to Connected Resource Gateway (CRG) for access, control, and management of connected resources:
  • CRG will be the primary solution moving forward, offering improved scalability, security, and continued enhancements.
  • New users should begin with CRG as the recommended option, while existing AG users are encouraged to migrate to CRG.
  • AG discovered resources are not automatically accessible on CRG.
  • To migrate to CRG, you must set up CRG as if you are setting up a new implementation.

Prerequisites:

  • The external DNS configuration must have the entries to point to the Lighthouse:

    • To register in the DNS, ensure that you use the address format: *.crg.your1stlighthouseaddress.com *.crg.your2ndlighthouseaddress.com.

    • You only require DNS if you want to proxy the GUI for http/https.

  • Smart Management Fabric. If this is already set up, you can start at step 7.


  1. Optional: Create and upload the Lighthouse SSL Certificate and ensure that it is valid for all sub-domains.

    Note: For Connected Resource Gateway (CRG), add the following subdomain patterns to your certificate:
    *.crg.your1stlighthouseaddress.com
    *.crg.your2ndlighthouseaddress.com

  2. Optional: To add any resources via the domain name for the resource (rather than IP address), ensure that Lighthouse is configured to use an appropriate DNS server. If Lighthouse:

    • gets its primary IP address via DHCP, configure the DHCP server to specify the DNS server to use.
    • uses a static IP address, edit the configuration for that connection on the Interfaces page and ensure that a DNS server address is configured.

    Note: If you only want to add resources via IP address, you can skip this step.

  3. Enable Smart Management Fabric.

  4. Create a Smart Management Fabric Template for enrolling nodes.
    You can apply this template either on enrollment via bundle OR at any time by pushing a template..

    Notes:
    • If you are completing these steps for third-party nodes, then you do not require a SMF template and can skip this step.
    • If you have existing nodes, and you push the SMF template, then steps 5 and 6 are not required.

  5. Create an Enrollment Bundle and ensure that the Smart Management Template is linked to the bundle under the Bundle Templates section.

  6. Enroll the node.
    The node initially shows as enrolled with no templates applied.
    The linked template is pushed and applied to the node.

  7. Add a resource.

    Notes:
    • Lighthouse attempts to discover the configured routes, to ensure they exist, every 60 seconds. During this time, the following toast message may appear: 'The provided address is not an SMF discovered subnet.' This message also appears if there is no route in SMF to your device; check that you added a node near that network and configured SMF on that node (via template) correctly.
    • Lighthouse now polls to check connectivity to the resource. When established, the appropriate HTTP, HTTPS and SSH icons are enabled.

  8. Click the appropriate icon to connect to the resource.