A virtual machine (VM) that can support a 50GB disk at minimum. ○. The ... operation can be automated by configuring Lighthouse to auto- approve nodes ...
LIGHTHOUSE 24.12.1
USER GUIDE
Lighthouse User Guide
COPYRIGHT ©
Opengear Inc. 2025. All Rights Reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of Opengear. Opengear provides this document "as is," without warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of fitness or merchantability for a particular purpose. Opengear may make improvements and/or changes in this manual or in the product(s) and/or the program(s) described in this manual at any time. This product could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes may be incorporated in new editions of the publication.
24.12.1
Copyright ©
2
CONTENTS
COPYRIGHT © CONTENTS WHAT'S NEW Software Release 24.12.1
Release Notes User Guide Updates Software Release 24.12 Release Notes User Guide Updates for Features
Subscription Updates Custom Login Message Network Configuration Updates Other User Guide Updates ABOUT THIS USER GUIDE LIGHTHOUSE OVERVIEW Lighthouse Architecture Lighthouse Virtual Machine Host Requirements CPU and RAM Guidelines Lighthouse to Node Interactions Lighthouse Certificate Management Precautions
24.12.1
Contents
Lighthouse User Guide
2 3 25 25 25 25 25 25 25 26 26 27 28 29 30 30 32 33 33 33 34
3
Configuration Scheduling Log File Use Multiple Lighthouses EULA and GPL LIGHTHOUSE USER INTERFACE Header Pane Settings Pane Users & Accounts Menu Items Settings Menu Items Lighthouse Admin Menu Items Menu Pane Node Tools Menu Items NetOps Menu Items Main Pane Grids and Controls
Multi-Select and Actions Filtering the Data Sorting Data on a Grid Column How to Search INSTALLING LIGHTHOUSE Lighthouse Virtual Machines Lighthouse VM Files
24.12.1
Contents
Lighthouse User Guide
35 35 35 35 36 37 38 38 39 40 43 43 44 45 45 47 47 48 48 49 50 50 50
4
Lighthouse User Guide
Lighthouse AWS VM Files
51
Lighthouse Azure VM Files
51
Lighthouse Hyper-V VM Files
51
Install Lighthouse VM on VMware
52
VMware vSphere 6.0 client on Windows
52
Requirements
52
Launch the vSphere Client and Connect to a vSphere Instance.
52
Import the VM Open Volume Format Image
54
Launch the Opengear Lighthouse Virtual Machine
55
Access the Console of a Headless Lighthouse Instance
56
VMware Workstation Player on Windows as Host
56
Import the Opengear Lighthouse VM file into VMware Workstation Player
56
VMware Workstation Pro on Windows as Host
57
Import the Lighthouse VM File Into VMware Workstation Pro
57
Install Lighthouse VM on Hyper-V on Windows
58
Run on Windows 10/Windows Server 2016
58
Remote Hyper-V Deployment With Pre-authenticated User
59
VirtualBox Deployments on Windows as Host
60
VirtualBox on Windows as Host
60
VirtualBox on macOS as Host
62
VirtualBox on Ubuntu as Host
64
VirtualBox on Fedora Workstation as Host
66
Install Lighthouse VM on Linux Hosts
67
24.12.1
Contents
5
Lighthouse User Guide
Virtual Machine Manager on Ubuntu as Host
67
Boxes on Fedora Workstation as Host
68
CentOS as Host
69
Install in the Cloud
70
Install in Azure
70
Before you Begin
70
Create Storage and add Lighthouse VHD Image
71
Create an Image
73
Create a Virtual Machine
74
Configure firewall rules for the Virtual Machine
77
Check endpoints in Lighthouse
79
Install in Amazon Web Services (AWS)
79
Before you begin
79
Changes to Default Settings
80
Limitations
81
Manually create an AMI on AWS
81
Subscribe to the Opengear Lighthouse AMI on AWS Marketplace
84
Configure and Launch the Instance
86
Add Disk Space to Lighthouse
89
Add a New Disk to AWS
90
Add a New Disk - qemu Specific Instructions
90
Add a New Disk - Azure
91
Add a New Disk - Hyper-V
91
24.12.1
Contents
6
Add a New Disk - VirtualBox Utilize the Added Disk on the Lighthouse VM
Increase the lh_data Logical Volume Mount the Hard Disks with ogconfig-cli SETTING UP LIGHTHOUSE Load Lighthouse Lighthouse IP Addresses Usage Example First Boot of the Lighthouse VM Set the Lighthouse Hostname Add External IP Addresses Manually Examine or Modify the Lighthouse SSL Certificate Set the Lighthouse Internal Clock Manual Configuration Automatic Configuration Set a Custom Login Message Set up Networking Requirements Examine or Modify the Lighthouse Session Settings Examine or Change Lighthouse VPN Network Settings Network Connections View available Network Connections Edit a Network Interface
24.12.1
Contents
Lighthouse User Guide
92 92 93 94 96 96 96 97 97 97 99 99 100 101 101 101 102 103 103 104 105 105 106
7
Lighthouse User Guide
Add a Network Connection
107
Edit a Network Connection
108
Delete a Network Connection
109
Enable Cell Health Reporting
109
Lighthouse MIBs
110
Generic Information About Lighthouse Version and Nodes Count
110
Available Information for an Enrolled Opengear Node
111
Available Information for an Enrolled Third-party Node
111
Available Licensing Information
112
Available Enrolled Node Cellular Health Information
112
Other SNMP Commands
112
Examples of Lighthouse MIB Queries that use SNMP
112
Set up Multiple Instances of Lighthouse
113
Set up Multi Instance
114
Steps to Setup Multi Instance
115
Enable Alternate REST API Ports
116
Configure the Alternate REST API
117
Configure Subnets for a Multiple Instance Lighthouse
117
Subnet Planning
118
Configure the Subnets between the Primary Lighthouse and its Nodes
118
Configure the Subnet between each Secondary Lighthouse and its Nodes
119
Configure Secondary Instance Information Prior to Enrollment
120
Unenroll a Secondary Instance
121
24.12.1
Contents
8
Promote a Secondary Instance Enable Alerting and Monitoring
SNMP Manager Settings SNMP Service Settings Syslog Server Management
View the Configured Syslog Servers Add a New Syslog Server Modify a Syslog Server Delete a Syslog Server Smart Management Fabric Enable Smart Management Fabric Use Smart Management Fabric IP Access Secure Provisioning Secure Provisioning Configuration Reserve an Interface for Smart management Fabric (SMF) Lighthouse OSPF Settings View OSPF Interfaces Add an OSPF Interface Edit an OSPF Interface Delete an OSPF Interface MANAGING LIGHTHOUSE Manage Subscriptions
24.12.1
Contents
Lighthouse User Guide
122 123 123 125 126 126 126 127 127 128 129 131 132 132 132 132 133 133 134 135 136 137 137
9
Subscription Types View Subscriptions Add a New Subscription to Lighthouse Assign Subscriptions to Nodes
Assign a Single Node to a Subscription Assign Multiple Nodes to a Subscription Update a Subscription to Lighthouse Upgrade Lighthouse About the Upgrade Process Prepare to Upgrade Lighthouse Perform an Upgrade of Lighthouse Upgrade a Primary Lighthouse Upgrade Multi Instance Lighthouse Upgrade Lighthouse via the CLI Upgrade via Local Terminal Upgrade via Local File System Upgrade NetOps Modules Upgrade via Lighthouse UI Troubleshoot the Upgrade Process Recover from a Failed Upgrade Promote a Secondary Lighthouse Restore a Configuration Backup Manually Retry Upgrade
24.12.1
Contents
Lighthouse User Guide
137 139 140 140 141 141 142 143 143 144 145 145 146 147 147 148 149 149 149 150 150 150 150
10
Configuration Backup Configuration Restore Shut Down or Restart Lighthouse Find the Current Lighthouse Instance Version
Version Information within the Lighthouse UI Version Information via the Local Shell Other Information Sources Shut Down a Running Lighthouse Instance Restart a Running Lighthouse Instance Return a Lighthouse Instance to Factory Settings Monitor Jobs CONFIGURING LIGHTHOUSE Manage Templates Manage Authentication Templates Create an Authentication Template Edit an Authentication Template Delete an Authentication Template Manage Script Templates Create a Script Template Edit a Script Template Delete a Script Template Manage Smart Management Fabric Templates Create a Smart Management Fabric Template
24.12.1
Contents
Lighthouse User Guide
152 152 153 154 154 154 155 155 156 156 157 158 158 159 159 161 162 162 163 163 164 164 166
11
Validate a Smart Management Fabric Template Edit a Smart Management Fabric Template Delete a Smart Management Fabric Template Manage User and Group Templates Create a User and Group Template Edit a User and Group Template
Edit a Users and Group Template Delete a Group from a Template Delete a User from a Template Delete a User and Group Template Delete Users or Groups from a Template Delete a Group from a Template Delete a User from a Template Push Templates Push a Template Manually Apply NetOps Modules via Template Disable NetOps Modules via Template Identify nodes running netOps Clean up nodes and disable NetOps Technical Support Reports Configure Lighthouse for Network Traffic Mirroring Configure Network Traffic Mirroring for Multiple Instances Troubleshoot Network Traffic Mirroring
24.12.1
Contents
Lighthouse User Guide
168 168 169 169 170 172 172 172 172 173 173 173 174 174 175 176 177 177 178 179 181 182 183
12
Lighthouse CLI, Serial Port, and REST API logging WORKING WITH LIGHTHOUSE NODES Enrollment Bundles
Assign Subscriptions to a Bundle Create an Enrollment Bundle Structure of an Enrollment Bundle File Manage the Enrollment Settings Enroll Nodes Enroll a Node via the Lighthouse Web UI Enroll a Node via the Node Web UI Enroll nodes via OM, ACM, CM, and IM Web UI
Enroll via OM, CM8xxx Web UI Enroll Via ACM and IM Web UI Enrollment via USB drive Download the Enrollment Bundle Enrollment via USB Manage Nodes View all Nodes Filter Nodes Assign or Remove a Node Tag Approve Pending Nodes Unenroll Nodes For a Node that has been Enrolled
24.12.1
Contents
Lighthouse User Guide
183 190 190 191 191 193 194 194 196 197 197 198 198 198 198 198 200 200 200 200 201 201 202
13
For a Node that is Pending Approval Connect to the Web-Management Interface of a Node
Connect from the Dashboard Connect from the Nodes Page Connect to the Serial Ports for a Node From the Nodes Page From the Ports Page Connect via SSH and Changing the Delimiter Character Connect via the Web Terminal Select Nodes using Shell-Based Tools Select Nodes Run commands on selected nodes Upgrade Nodes via the UI Firmware Files Upload a Firmware File Delete a Firmware File Create an upgrade task Cancel an upgrade task Copy a scheduled task Delete an upgrade task Retry an Upgrade Task Node Upgrade Runtime Behaviour Promote a Secondary Instance to Primary
24.12.1
Contents
Lighthouse User Guide
202 202 202 203 203 204 204 204 205 206 206 206 207 207 208 208 209 210 211 212 212 212 213
14
Skip Versions Time Zones Offline Nodes Lighthouse Availability and Stability Operations not Supported Back up Nodes Manage Ports View Ports for all Nodes View Port Information for a Node Filter Ports Create, Assign or Remove a Tag Access Port Logs Access Port Logs from the Nodes Page Access Port Logs from the Ports Page Manage Resources View Resources Filter Resources Create, Assign or Remove a Resource Tag Connect to a Resource Logging Add a Resource Edit a Resource Delete a Resource
24.12.1
Contents
Lighthouse User Guide
213 213 214 214 214 215 216 216 216 217 217 218 218 219 219 220 220 221 221 222 223 224 224
15
Bulk Deletion of Resources Set up Lighthouse as a Connected Resource Gateway (CRG) MANAGING FILTERS AND TAGS Manage Filters View Filters Create a Node Filter
Create from the Filter Management Page Create from the Node Filter Control Create a Port Filter Create from the Filter Management Page Create from the Port Filter Control Create a Resource Filter Create from the Filter Management Page Create from the Resource Filter Control Edit a Filter Edit a Filter from the Filter Management Page Edit a Filter from the Filter Control Delete a Filter Delete a Filter from the Filter Management Page Delete a Filter from the Filter Control Manage Tags View Tags Create a Node Tag
24.12.1
Contents
Lighthouse User Guide
224 225 228 228 228 229 229 230 231 231 232 234 234 235 236 236 237 238 238 239 240 240 241
16
Create a Resource Tag Edit a Tag Delete a Tag MANAGING LIGHTHOUSE USERS Role Description Manage User Groups Create a User Group Available Roles Create a User Group From an Existing Group Edit a User Group Delete a User Group Manage Roles CLI Permissions Reference Operation Permissions Reference Create a Role Edit a Role Delete a Role Manage Users Authentication modes Create a Local User
Create User Event Logs Edit a User Disable a User
24.12.1
Contents
Lighthouse User Guide
241 242 242 244 244 245 245 247 248 248 249 249 250 250 255 256 257 257 258 259 261 261 262
17
Disable a Root User Disable Local USERS Enable a User Enable a Root User Enable a Single User Delete a User Unlock a User Expire or Restore a User Password Expire a User Password Restore a User Password Manage Local Authentication Policy Set the Password Policy Set the Login Restrictions Configure Remote Authentication LDAP Configuration RADIUS Configuration TACACS+ configuration Configure SSH Authentication SAML Configuration for SSO Generic IdP Setup Generic IdP SAML Attribute Lighthouse IdP Setup Examples of Specific IdP Setups
24.12.1
Contents
Lighthouse User Guide
262 263 263 263 264 264 264 265 265 265 266 266 267 267 268 270 271 272 273 274 276 277 278
18
Okta Example - Create an Application Onelogin Example - Create an Application Azure Example - Active Directory Configure AUTH0 for IdP Create an Application (Enterprise applications) Configure AUTH0 Metadata for IdP Configure AUTH0 Roles for IdP Limitations of SAML Configuration IdP Metadata Certificate Expiry Make Changes to User Permissions SAML SSO User groups SAML SSO Users SAML SSO Support ADVANCED FUNCTIONALITY What is a NetOps Module Subscriptions Manage NetOps Modules NetOps Platform Security Change Docker IP Ranges Install NetOps Modules Perform NetOps Installation from an Online Repository Perform NetOps Installation from an Offline Repository Perform NetOps Installation from an Offline Repository via CLI
24.12.1
Contents
Lighthouse User Guide
278 281 283 287 287 289 290 290 290 291 291 291 291 293 293 293 294 294 295 296 296 297 297
19
Install Modules from the CLI Activate a NetOps Module
Preparation Procedure 'Always Activate' Mode on All Nodes (Automatic) Procedure Activate NetOps on Selected Nodes (Automatic) Procedure Activate the NetOps Module on Nodes (Manual) Select Nodes Pre-Flight Test Push Deactivate (remove) a NetOps Module Deactivate and Remove a NetOps Module via the API Deactivate and Remove NetOps Modules via CLI Secure Provisioning Secure Provisioning Configuration Management Stateless File Management Stateful Device Management Gateway How Secure Provisioning Works Support for Secure Provisioning Vendor Resources Supported by Secure Provisioning Connect to a Target Device
24.12.1
Contents
Lighthouse User Guide
298 298 299 299 299 300 300 300 301 301 302 302 302 302 303 303 304 304 305 305 307 307 308
20
Local Network Services Provided by Nodes Default Gateway DNS Server NTP Server Syslog Server
Secure Provisioning Configuration Device Resource Bundle Node Inventory Create a Device Configuration Example configuration files
CLI based Workflow Create Configuration YAML Define a Static Inventory: Define a Dynamic Inventory: How UI Fields Correspond to the YAML File (Example) Upload Configuration and Resources Option A. Secure Copy Method Option B. git Method Additional Resource Files and Device Type Files
Configure Device Resources via ZTP Device Resource Bundle Matching Resource Distribution Baseline vs Final Device Configuration
24.12.1
Contents
Lighthouse User Guide
309 309 309 310 310 310 310 311 311 312 313 314 316 316 318 321 321 322 323 324 324 325 325
21
Run a Script on a Newly Provisioned Device Monitor the ZTP Progress of a Resource WAN Gateway Services Advanced Options
Use Variables in Configuration File Templates Post-provisioning Scripts Ordered Provisioning Troubleshoot Secure Provisioning Secure Provisioning consists of several Docker containers Troubleshooting Commands for NetOps Modules IP Access Connectivity Use Advanced Options of IP Access Connect to WAN Zone Network Access Policies for Operations Manager Understand Access Policies Set up Network Access Policies set Access policies Troubleshoot IP Access View the Docker logs Use the Routing Table Automation Gateway Differences Between IP Access and Automation Gateway
24.12.1
Contents
Lighthouse User Guide
325 326 327 328 328 329 331 332 332 332 333 334 335 336 336 337 338 338 339 339 340 342 343
22
IP Access Automation Gateway Connect to a Remote Resource To Activate the Automation Gateway on an Enrolled Node Connect with REST/HTTP/HTTPS APIs Automation Gateway Service Discovery Access Multiple VLANs or Ports Group memberships Firewall Zones Multiple Layer 3 Network Connections COMMAND LINE TOOLS cert_manage Sub-Command :: run Sub-Command :: renew Sub-Command :: show Sub-Command :: validity Sub-Command :: offset Sub-Command :: logs cron mass_enroll_nodes mass_unenroll_nodes node-command node-info
24.12.1
Contents
Lighthouse User Guide
343 343 343 344 344 348 348 349 349 349 350 351 353 353 354 355 355 356 357 359 361 364 366
23
Example node-upgrade
Exit Status Output Messages Example support-report Example sysflash traffic_mirroring Example :: Enable Example :: Status Example :: Test Example :: Disable GLOSSARY
Lighthouse User Guide
367 368 370 370 370 372 372 373 375 377 377 377 377 378
24.12.1
Contents
24
Lighthouse User Guide
WHAT'S NEW
SOFTWARE RELEASE 24.12.1
The following updated documentation is available for Lighthouse 24.12.1.
RELEASE NOTES
For a full list of any features, improvements, or bug fixes for Lighthouse 24.12.1, see the Release Notes.
USER GUIDE UPDATES
The following user guide updates are available: l A number of formatting updates, particularly in the Manage Templates section. l The Install in Azure section is reorganized and updated to provide more details and a better
flow of information. l Additional detail around subnet requirements is added to the Configure subnets for multi-
instance Lighthouse topic.
SOFTWARE RELEASE 24.12
The following updated documentation is available for Lighthouse 24.12.
RELEASE NOTES
For a full list of all features, improvements, and bug fixes for Lighthouse 24.12, see the Release Notes.
USER GUIDE UPDATES FOR FEATURES
The following user guide updates are also available in addition to the feature documentation:
24.12.1
What's New
25
Lighthouse User Guide
SUBSCRIPTION UPDATES
The Lighthouse Core and Lighthouse Enhance subscriptions are described in Manage Subscriptions, with updated information when you Add a new subscription to Lighthouse, Assign Subscriptions to Nodes, and particularly when you Update a Subscription to Lighthouse to one of the new subscriptions. Installing Lighthouse Core or Lighthouse Enhance subscriptions deactivates NetOps modules, but some nodes may still try to run NetOps, so a set of clean up templates are described on Manage Templates. It is recommended to use these templates to clean up the nodes BEFORE you apply one of the subscriptions. Steps to perform the clean up are described on the new Disable NetOps Modules via Template topic. The following topics have also had updates to reflect changes made for the subscriptions where appropriate: l Lighthouse Overview l Settings Pane l Menu Pane l Manually Apply NetOps Modules via Template l Enrollment Bundles l Create an Enrollment Bundle l Advanced Functionality l Manage NetOps Modules
CUSTOM LOGIN MESSAGE
You can now set a custom login message that is visible to users before they log in to Lighthouse. The new Set a Custom Login Message topic has been added to describe how to set the message. User permissions describing who can set the message are described on Manage Roles.
24.12.1
What's New
26
Lighthouse User Guide
The following topics have also had updates to reflect changes made for the custom login message where appropriate: l Settings Pane l Examine or Modify the Lighthouse Session Settings l Enable Alternate REST API Ports
NETWORK CONFIGURATION UPDATES
The following sections of the manual are updated to reflect network configuration changes in Lighthouse, including the support of Net2 and OSPF settings. The Network Connections section has been updated to include information on adding network connections to interfaces on the new topics Add a Network Connection, Edit a Network Connection, and Delete a Network Connection. User permissions describing who can perform these activities is described on Manage Roles. The Smart Management Fabric section has been updated and includes a new: l topic to describe how to Reserve an Interface for Smart management Fabric (SMF). l section for Lighthouse OSPF Settings, including new topics that describe how to Add an OSPF
Interface, Edit an OSPF Interface, and Delete an OSPF Interface. The following topics have also had updates to reflect changes made for the network configuration updates where appropriate: l Settings Pane l Set the Lighthouse Hostname l Add External IP Addresses Manually l Manage Resources l Add a resource
24.12.1
What's New
27
Lighthouse User Guide
OTHER USER GUIDE UPDATES
The following user guide updates are also available in addition to the feature documentation: l The Lighthouse CLI, Serial Port, and REST API Logging section is available in the Configuring
Lighthouse section of the manual. l Updates on the Manage Ports page to reflect that you can now search by node name. l The Lighthouse Virtual Machine Requirements are updated to provide general guidelines for
any Lighthouse deployment. l The Install in Amazon Web Services section is rearranged to provide a better flow of the content
so that the steps are clearer. l There is new information around re-enrolling nodes to get updated configuration when you add
external IP addresses manually. l Updates are added to describe the linking between filters and user groups. This affects the
following pages: l Create Resource Filters l Create Port Filters l Delete Filters l Create a User Group l The steps to Configure AUTH0 for IdP are updated to replace rules with actions. l The following sections of the manual are rearranged to make content easier to find and more user friendly: l Lighthouse User Interface l Manage Filters l Manage Tags l A number of maintenance, consistency, and formatting updates to improve the content that may change how the information looked in the last release.
24.12.1
What's New
28
Lighthouse User Guide
ABOUT THIS USER GUIDE
This user guide describes how to use Lighthouse and is current as of 24.12.1. When using a minor release, there may or may not be a specific version of the user guide for that release.
24.12.1
About This User Guide
29
Lighthouse User Guide
LIGHTHOUSE OVERVIEW
Lighthouse allows you to centrally access, manage, and monitor a network of Opengear devices (referred to as nodes throughout this guide). Lighthouse is a virtual machine that can be hosted on various platforms like VMware or Hyper-V (on customer hardware) or on supported cloud providers (AWS or Azure). Access to specific features, to support your networking requirements, depends on your subscription type. For more information, see Manage Subscriptions.
LIGHTHOUSE ARCHITECTURE
Lighthouse is an API-driven platform that provides secure access to remote networks regardless of how devices are connected or how a user interacts with the system. In combination with select Opengear Appliances, Lighthouse can push and manage Docker containers to each remote location to provide additional functionality and automation. Users with the appropriate subscription type can enable Smart Management Fabric to allow all devices connected to a supported Opengear node to have direct routed IP access with each other. For example: l A user with access to Lighthouse from a device that is attached to the management subnet can
access any enrolled Opengear node and the third-party network equipment attached to the enrolled Opengear node via routed IP. l An enterprise user connected to an IP network with a route to an enrolled Opengear device can access any other enrolled Opengear device (via IP). l Devices attached to Opengear nodes can use IP routed connectivity to other devices attached to other Opengear nodes. l Network automation and configuration tools deployed on centrally located servers can use IP routed connectivity to devices and systems attached to Opengear nodes. For example, vCenter
24.12.1
Lighthouse Overview
30
Lighthouse User Guide
is the configuration tool and it is used to provision eSXI server instances attached to Opengear nodes.
Note: The Smart Management Fabric represents an advanced functionality designed to offer heightened flexibility and accessibility to network and IT professionals throughout the network fabric. However, users must acknowledge the potential risk of overexposing the network, which could lead to bypassing Layer 2 or Layer 3 access control measures.
Nodes connect to a central Lighthouse instance over an OpenVPN tunnel, and are accessed, managed, and monitored via services transported over the VPN tunnel.
24.12.1
Lighthouse Overview
31
Lighthouse User Guide
Note: This diagram depicts Lighthouse set up in a High Availability configuration. If there is no secondary Lighthouse, the setup remains the same but without the secondary elements.
LIGHTHOUSE VIRTUAL MACHINE HOST REQUIREMENTS
Lighthouse deploys as an application running in a Linux-based virtual machine (VM). To run a Lighthouse VM, the host computer must be able to run a VM manager and at least one full 64-bit Linux-based virtual machine. The Lighthouse binary is available in Open, VMware and Hyper-V specific Virtual Machine formats. VM managers such as Boxes, KVM and VirtualBox can make use of the open format. Lighthouse binaries are also available for cloud hosting services including Amazon's AWS, and Microsoft Azure. NetOps modules are released independently of Lighthouse software or Operations Manager firmware. These releases are shipped to Amazon's ECR Public Gallery, where they can be fetched by Lighthouse then deployed to all activated nodes by Lighthouse. NetOps modules can also be downloaded off the Opengear FTP site, and uploaded manually on Lighthouse. To host Lighthouse, the VM must be configured to support: l A minimum 50GB SCSI disk. Start with more if you think your network will expand. Additional
space may be required depending on your feature usage on Lighthouse and the scale of the network. l 1 x network interface card, preferably paravirtualised (virtio, vmxnet3), Realtek rtl8139, or Intel e1000 are also supported, bridged. l VGA console for initial setup.
Tip: CPU and RAM utilization increase with the number of enrolled nodes, network utilization and storage.
24.12.1
Lighthouse Overview
32
CPU AND RAM GUIDELINES
No. Nodes < 2500 Nodes > 2500 Nodes
Min. CPU Cores 4 x 64-bit CPU cores 8 x 64-bit CPU cores
Lighthouse User Guide
Min. RAM 16GB 32GB
Tip: For large deployments, contact us for guidance on the deployment options, including low and zero-touch enrollment.
LIGHTHOUSE TO NODE INTERACTIONS
When a node is enrolled to Lighthouse, a Virtual Private Network (VPN) tunnel is established between Lighthouse and the node. This provides secure encrypted IP networking, which is resilient to changes in the underlying network (such as node failover to cellular). Lighthouse interacts with the node over the VPN tunnel, mostly via the node's REST API and SSH. Nodes notify Lighthouse of changes to their configuration and status. The node web UI is accessible directly through Lighthouse and is proxied via the VPN. This allows secure user access to the node even if it is behind a firewall with no direct HTTPS access.
LIGHTHOUSE CERTIFICATE MANAGEMENT
Lighthouse uses X.509 certificates for node authentication to the Lighthouse VPN and REST API. Certificates are issued by the internal Lighthouse certificate authority as part of the node enrollment process, and are automatically renewed by Lighthouse before expiry. The replacement certificates are pushed from Lighthouse to connected nodes. Lighthouse manages certificates automatically, and no action is required by the customer. However, there are some things to be aware of:
24.12.1
Lighthouse Overview
33
Lighthouse User Guide
l Node certificates are revoked by Lighthouse when a node is unenrolled, or when the certificate has been replaced (after the replacement certificate has been used to successfully connect to the Lighthouse VPN). Revoked certificates cannot be used to authenticate to the Lighthouse VPN or REST API.
l The Lighthouse CA can be revoked after it has been renewed when all nodes have been notified of the change. Remediate or unenroll any disconnected nodes to complete this operation.
l If a node is disconnected from Lighthouse for an extended period of time, it may not be possible to push the updated certificate to the node. Lighthouse will retry the push job regularly until the node's existing certificate has expired, at which point the node will have to be manually reenrolled.
PRECAUTIONS
If an old Lighthouse configuration backup is restored to Lighthouse, the node certificate details in the backup may no longer match those on the nodes themselves, in which case the nodes will fail to connect to Lighthouse. Ensure that configuration backups of Lighthouse are kept up to date. Similarly, if a node has its configuration restored from an old backup, its certificate may no longer match the one expected in Lighthouse. In these cases, it will be necessary to unenroll and reenroll the node. To avoid these situations, ensure configuration backups of nodes are kept up to date.
Note: There is a limitation on Operations Manger (OM) and Console Manger CM8XXX nodes where a Lighthouse VPN connection configuration is not retained in the node backup.
The Lighthouse VPN certificate and client certificates validity periods should be no greater than the CA certificate used to issue them. The existing certificate validity periods can be seen by running the show sub-command and the pre-configured defaults by using the --defaults option.
24.12.1
Lighthouse Overview
34
Lighthouse User Guide
Lighthouse will automatically process scheduled certificate updates daily at 1 AM Lighthouse system time. Under normal circumstances there is no requirement to run cert_manage run manually.
CONFIGURATION
The cert_manage command can be used to control various aspects of certificate management in Lighthouse. The default settings are recommended, and should only be changed with caution. Only users with sudo access on the primary Lighthouse CLI (for example, via the admin group) can configure certificate management.
Note: All functionality is available only via the Lighthouse CLI. There is no UI or REST API interface for the certificate management feature. The Jobs page on the Lighthouse UI shows node certificate update jobs.
SCHEDULING
Certificate renewal jobs are scheduled using cron to run at 1 AM (Lighthouse system time), every day. An administrator may choose to update the frequency of the cron job under /etc/cron.d/rotate_certificates.cron.
LOG FILE
The certificate management logs can be found in /var/log/cert_manager.log.
USE MULTIPLE LIGHTHOUSES
Lighthouse offers high availability with the Multiple Instance feature, which allows you to set up secondary instances of Lighthouse. The secondary Lighthouses automatically replicate the database from the primary Lighthouse instance, and maintains connections to all of its enrolled nodes.
24.12.1
Lighthouse Overview
35
Lighthouse User Guide
Secondary instances may be used to view Lighthouse information specific to that instance, and to connect to its nodes via pmshell. Configuration changes must be performed on the primary Lighthouse instance, which will then update the information displayed on the secondary instance.
Note: Secondary Lighthouse user interfaces are read-only.
The multiple instance feature has the following limitations: l If external network addresses on the primary or secondary Lighthouses are updated after a
secondary Lighthouse has been enrolled, it may break replication. l Up to ten secondary instances can be enrolled. l Ensure that you re-configure instance specific settings such as hostname, external endpoints,
and time zone on a secondary instance before adding the secondary instance to the primary Lighthouse in a normal way through UI. l Only secondary Lighthouse instances with zero nodes can be enrolled to the primary Lighthouse. l Removing a secondary Lighthouse instance will initiate a factory reset of the removed Lighthouse.
EULA AND GPL
The current Opengear end-user license agreement can be found at Opengear License EULA | Digi International.
24.12.1
Lighthouse Overview
36
Lighthouse User Guide
LIGHTHOUSE USER INTERFACE
Lighthouse offers an easy to navigate interface to manage your network. The user interface consists of the following main sections: 1. Header Pane: Access to the Help menu, information for the Lighthouse instance, and a shortcut
to enroll a node. 2. Settings Pane: Access to Lighthouse settings including users and account management menu,
settings menu, and user options. 3. Menu Pane: Access to key dashboards to manage nodes, ports, connected resources, and
jobs, along with tools to configure nodes, access to a local web-based terminal, and NetOps management. 4. Main Pane: The main information pane.
24.12.1
Lighthouse User Interface
37
Lighthouse User Guide
HEADER PANE
The Header Pane provides access to the following:
Icon
Item
Description
Enroll Node
Opens the ENROLL NODES dialog, where you can Enroll a node via the Lighthouse Web UI.
Help
Opens the menu and access the following help options: l Generate Technical Support Report: Create and download a
report to assist the support teams. l View User Manual: Link to the latest published Lighthouse user
documentation. l Visit Support Website: Link to technical support contact inform-
ation as well as the Opengear Customer Portal resources.
System Information
Displays the system information panel that shows the software and API version information, and the licensing subscription summary. Click View Details at the bottom of the panel to display the subscriptions dashboard.
SETTINGS PANE
The Settings Pane provides access to the following:
Icon
Item
Description
Users & Accounts
Expands the Users & Accounts Menu Items to manage Lighthouse users and accounts including configuration of groups and roles, authentication policies, and SSH settings.
24.12.1
Lighthouse User Interface
38
Lighthouse User Guide
Icon
Item
Description
Settings
Expands the Settings Menu Items to manage Lighthouse settings including configuration of filters and tags, multi instance settings, Lighthouse services, and general system settings.
Lighthouse Admin
Expands the Lighthouse Admin Menu Items for personalization such as the Lighthouse user interface theme and access the sign out option.
USERS & ACCOUNTS MENU ITEMS
Menu Item
Description
Groups and Roles
Access to managing user groups and roles within Lighthouse.
Local Authentication Policy
Manage the Lighthouse password policy as well as login restrictions.
Local Users
Access to managing the local Lighthouse users, which user group they are linked to and the inherited permission sets applied from the user groups.
Remote Authentication
Configure and manage settings for remote authentication. Lighthouse supports local users only or remote authentication via Radius, TACACS+ and LDAP servers.
SSH Authentication
Access to configuring the SSH for password authentication and connection as Root User.
24.12.1
Lighthouse User Interface
39
Lighthouse User Guide
SETTINGS MENU ITEMS
FILTERS AND TAGS
Menu Item
Description
Filters
Manage filters for nodes, ports and resources. The filters are selectable in the main dashboards.
Tags
Manage tags that can be applied for nodes and resources.
MULTI INSTANCE
Menu Item Multi Instance VPN
Secondary Lighthouse
Description
Access to setup the range for VPN tunnels between the primary and Secondary Lighthouses.
Manage secondary Lighthouses.
SERVICES
Menu Item Alerting and Monitoring Cell Health Reporting
Console Gateway
Description
Manage setup and configuration for SNMP and SYSLOG services.
Enable and configure cell health reporting signal quality range and frequency of reporting.
Configure the port delimiter and SSH address for the console gateway.
24.12.1
Lighthouse User Interface
40
Lighthouse User Guide
SERVICES
Menu Item
Description
HTTPS Certificate
Manage the Lighthouse SSL certificate.
Lighthouse VPN
Setup the range for VPN tunnels between the Primary Lighthouse and Nodes, as well as the Smart Management Fabric network range.
Node Backup
Enable backup and storage of the node backups.
Smart Management Fabric
Opens the SMART MANAGEMENT FABRIC page where you can enable functionality utilizing dynamic routing protocols. This page has the following tabs: l SMF SETTINGS: Allows you to enable Smart Management Fabric.
l LIGHTHOUSE OSPF SETTINGS: Allows you to manage and configure Lighthouse OSPF settings.
SYSTEM
Menu Item
Description
Backup, Restore and Reset
Backup and restore Lighthouse configurations, and access to performing a reset of the system to factory defaults.
24.12.1
Lighthouse User Interface
41
SYSTEM
Menu Item Network Settings
General Settings
Subscriptions
System Upgrade Time Settings
24.12.1
Lighthouse User Guide
Description
Opens the NETWORK SETTINGS page where you can: l Setup the network settings and manage any external IP addresses or DNS
names of the system. l Manage and configure the available network connections and reserve inter-
faces for Smart management Fabric. This page displays a tab for the primary instance and then a tab each for any configured secondary instances.
Manage session settings and set a custom login message. Opens the GENERAL SETTINGS page with two tabs: l SESSION SETTINGS: Where you can set idle timeout periods for the
Web UI and CLI sessions and enable or disable the alternate API port status. See Examine or Modify the Lighthouse Session Settings. l CUSTOM LOGIN MESSAGE: Where you can set a custom login message. See Set a Custom Login Message.
Opens the SUBSCRIPTIONS page where you can manage available subscriptions and node assignments. This page has two tabs: l SUBSCRIPTIONS: Displays information about your subscriptions. See
View Subscriptions. l SUBSCRIPTION ASSIGNMENT: Displays nodes and their assigned sub-
scription and enabled you to assign subscriptions to nodes. See Assign Subscriptions to Nodes.
Perform a system upgrade.
Manually configure timezone information or set to automatic and configure the Network Time Protocol servers.
Lighthouse User Interface
42
LIGHTHOUSE ADMIN MENU ITEMS
Menu Item
Description
Theme
Select between Light, System and Dark themes.
Sign Out
Sign out of the Lighthouse session.
Lighthouse User Guide
MENU PANE
The Menu Pane provides access to the following items and displays them in the Main Pane:
Icon
Item
Description
Dashboard
Opens the Dashboard page where you can view an overview for the Lighthouse instance that shows current status of the nodes and the cell health. This is selected by default when you log in to Lighthouse.
Jobs
Opens the JOBS page where you can view an overview of currently running jobs and access jobs previously completed.
Nodes
Opens the NODES page where you can view a grid of nodes either enrolled in Lighthouse or pending enrollment.
Ports
Opens the PORTS page where you can view a dashboard that displays the status of all ports connected to node for which you have permissions to view/edit.
24.12.1
Lighthouse User Interface
43
Icon
Item
Resources
Terminal
Node Tools
NetOps
Lighthouse User Guide
Description
Opens the RESOURCES page where you can manage connected resources.
Opens the TERMINAL page for access to the Lighthouse local webbased terminal.
Expands the Node Tools Menu Items to manage config templates, enrollment bundles and firmware updates.
Expands the NetOps Menu Items to access components that enable automation of specific operational scenarios deployed as Docker containers. Availability of this option is dependent on your subscription type.
NODE TOOLS MENU ITEMS
Note: Availability of these options is dependent on your subscription type.
The Node Tools menu section provides access to the following:
Menu Item
Description
Config Templates
Create and manage config templates to push to the nodes.
Enrollment Bundles
Create and manage enrollment bundles.
24.12.1
Lighthouse User Interface
44
Menu Item Enrollment Settings Firmware Upgrade
Lighthouse User Guide
Description Manage the token nodes use to request an enrollment and the default subscript to use for call home node enrollments. Schedule and manage firmware updates.
NETOPS MENU ITEMS
The NetOps menu section provides access to the following:
Menu Item
Description
Manage NetOps Modules
Manage and redeploy NetOps modules.
NetOps Installation
Install NetOps modules.
IP Access
Manage settings for the IP Access NetOps module.
Automation Gateway
Manage your network using automation tools.
MAIN PANE
The Main Pane displays the Lighthouse pages and dashboards. This is where you can view or update information based on the selection you make in the Settings Pane or Menu Pane. Pages may display in the following types of format: l Dashboard style: A centralized overview of data and information for your Lighthouse instance. l Grid style: A grid of related information where you can see multiple sets of data at the same
time, and interact with the data as outlined in Grids and Controls.
24.12.1
Lighthouse User Interface
45
Lighthouse User Guide
l Form style: A page of fields, input controls, buttons, and validation where you can enter data and perform actions generally related to configuration.
EXAMPLE DASHBOARD STYLE PAGE
EXAMPLE GRID STYLE PAGE
24.12.1
Lighthouse User Interface
46
EXAMPLE FORM STYLE PAGE
Lighthouse User Guide
GRIDS AND CONTROLS
Some Lighthouse pages display data in grids. In grids you can select items, sort the information, and filter the data.
MULTI-SELECT AND ACTIONS
To take action on multiple items at the same time, select the check boxes on the left of the rows. The available actions are displayed above the top row of the grids. If you select the check box in the grid header, all check boxes in the grid are selected.
24.12.1
Lighthouse User Interface
47
Lighthouse User Guide
FILTERING THE DATA
To view and select custom filters, click the Filter drop-down and then select from the available filters. For information about filters, see Manage Filters and Tags.
SORTING DATA ON A GRID COLUMN
Some columns support sorting the values in the column in ascending or descending order. To show the sort control, hover over the column name and then click the control to modify the column sort order.
24.12.1
Lighthouse User Interface
48
Lighthouse User Guide
HOW TO SEARCH Enter a term in the Search control to filter the results. The AND operator is used if more than one search term is entered. To enter a multi-word search phrase, enclose them in double quotes.
24.12.1
Lighthouse User Interface
49
Lighthouse User Guide
INSTALLING LIGHTHOUSE
To install Lighthouse you require: l A virtual machine (VM) that can support a 50GB disk at minimum. l The correct image file.
LIGHTHOUSE VIRTUAL MACHINES
Lighthouse VM is available in several formats on our secure ftp sites, from where you can download and verify the checksums and install the appropriate files. Ensure you use the correct file for your upgrade.
Note: SHASUMS files to verify the download are available with the install packages.
LIGHTHOUSE VM FILES
Container
lighthouse-<year>-<month>-<version>-ovf.zip
lighthouse-<year>-<month>-<version>-vmx.zip
lighthouse-<year>-<month>-<version>.ova
lighthouse-<year>-<month>-<version>.lh_upg
Description
An Open Volume Format file inside a PKZIP archive. This is for use with virtual machine managers such as KVM and Virtual Box.
A VMware configuration file inside a PKZIP archive. This is for use with virtual machine managers from VMware.
An Open Virtual Appliance file. This is for use with virtual machine managers such as VM and Virtual Box as well as for use with virtual machine managers from VMware.
An upgrade file.
24.12.1
Installing Lighthouse
50
LIGHTHOUSE AWS VM FILES
Container
lighthouse-<year>-<month>-<version>.aws.lh_upg
Description An upgrade file.
llighthouse-<year>-<month>-<version>.aws.raw.tar
AWS deployment file.
lighthouse-aws-bootstrap.sh
A shell script for deploying on AWS.
Lighthouse User Guide
LIGHTHOUSE AZURE VM FILES
Container
lighthouse-<year>-<month>-<version>>.azure.lh_upg
Description An upgrade file.
lighthouse-<year>-<month>-<version>.azure.zip
Azure deployment files.
LIGHTHOUSE HYPER-V VM FILES
Container
Description
lighthouse-<year>-<month>-<version>.hyperv.zip
Hyper-V deployment file.
24.12.1
Installing Lighthouse
51
Lighthouse User Guide
INSTALL LIGHTHOUSE VM ON VMWARE
This section describes how to install Lighthouse VMs on VMware hosts including: l VMware vSphere 6.0 client on Windows l VMware Workstation Player on Windows l VMware Workstation Pro on Windows
VMWARE VSPHERE 6.0 CLIENT ON WINDOWS
This procedure was tested using the VMware Sphere Client 6.0 running on Windows 7 Enterprise SP 1.
REQUIREMENTS
Ensure the following preconditions are met before you start installation: l VMware vSphere 6.0 is installed and running on available hardware. l Access to a Windows computer on which the VMware vSphere 6.0 client is installed. l The installed client application must be able to connect to and manage the VMware vSphere
6.0 instance. l Finally, a copy of the Lighthouse binary in Open Volume Format is required, the .ovf file,
either copied to the Windows computer running the VMware vSphere 6.0 client or available via a URL.
LAUNCH THE VSPHERE CLIENT AND CONNECT TO A VSPHERE INSTANCE.
1. Launch the VMware vSphere Client: Start > All Programs > VMware > VMware vSphere Client. The VMware vSphere Client opens a login window.
24.12.1
Installing Lighthouse
52
Lighthouse User Guide
2. Select the IP address or name of the VMware vSphere instance where Lighthouse will be installed from the IP address/Name drop-down list.
3. Enter the User name and Password required to gain management privileges to the selected VMware vSphere instance.
4. Click Login or press Enter. The login window displays progress text in the bottom left corner: Connecting Loading inventory Loading main form Displaying main form The vSphere main form window opens.
24.12.1
Installing Lighthouse
53
Lighthouse User Guide
IMPORT THE VM OPEN VOLUME FORMAT IMAGE
To import the Lighthouse VM: 1. From the vSphere Client menu bar, choose File > Deploy OVF Template.
The Deploy OVF Template window displays, with the first stage, Source, pre-selected. 2. If the file Opengear Lighthouse VM.ovf is on a remote computer via a URL, enter the URL
in the Deploy from a file or URL field. Otherwise, click Browse. An Open dialog displays. a. Navigate to the directory containing the file Opengear Lighthouse VM.ovf. b. Select Opengear Lighthouse VM.ovf and click Open. 3. The Deploy OVF Template window opens again, with the Opengear Lighthouse VM.ovf file listed in the Deploy from a file or URL combo-box. Click Next. 4. The OVF Template Details stage displays, showing basic information about the Lighthouse VM encapsulated by the .ovf file. Click Next. 5. The Name and Location screen displays with the Name field pre-populated and pre-selected. The default name is Opengear Lighthouse VM. To change this, enter a new name. Click Next. 6. The Disk Format screen displays which data-store the Lighthouse VM's virtual disk uses, how much free space the virtual disk has available and which provisioning scheme is being used. Click Next. 7. The Network Mapping screen shows which destination or inventory network the Lighthouse VM's virtual network is mapped to. Click Next. 8. The Ready to Complete screen displays, listing the basic properties of the about-to-bedeployed virtual machine. To be able to power-up the new virtual machine after deployment, select the Power on after deployment checkbox. Click Finish. The Deploying Opengear Lighthouse VM progress dialog displays.
24.12.1
Installing Lighthouse
54
Lighthouse User Guide
When deployment is finished, the Deployment Completed Successfully alert displays. 9. Click Close.
The new virtual machine is now deployed and displays in the inventory list.
LAUNCH THE OPENGEAR LIGHTHOUSE VIRTUAL MACHINE
The vSphere Client provides several ways of launching a Virtual Machine hosted on a vSphere instance. Begin by selecting the Lighthouse VM from the vSphere Client's inventory list. The selected VM can then be launched by doing one of the following: l Select Inventory > Virtual Machine > Power > Power On. l Press Ctrl-B. l Click the Power On the virtual machine link in the Basic Tasks section of the Getting Started
tab. This option requires the Getting Started tab be front-most. If it is not already the front-most tab, make it active by clicking it. l Select Inventory > Virtual Machine > Open Console and then: l Click Power On in the console tool bar, or l Choose VM > Power > Power On from the console menu bar, or l Press Ctrl-B.
Note: Only the fourth option above results in the running virtual machine being accessible from within the vSphere Client. The first three boot the Lighthouse VM and run it as a headless system, that is, with no display on a monitor. However, you can access Lighthouse via the web UI or SSH.
24.12.1
Installing Lighthouse
55
Lighthouse User Guide
ACCESS THE CONSOLE OF A HEADLESS LIGHTHOUSE INSTANCE
If direct interaction with a running but headless Opengear Lighthouse VM is required, open a console window. Select the running Opengear Lighthouse VM in the inventory list for the vSphere Client, then do one of the following: l Select Inventory > Virtual Machine > Open Console. l Right-click and select Open Console from the context menu that displays.
VMWARE WORKSTATION PLAYER ON WINDOWS AS HOST
Follow these steps when VMware Workstation Player is installed on the host Windows machine. VMware-ready virtual machine files are stored in C:\Users\%USERNAME%\Virtual Machines\. This is the location selected by default by VMware Workstation Player. If another location is preferred, adjust this procedure as required. Prepare the Lighthouse VM file for import into VMware Workstation Player: 1. Move the lighthouse-<year>-<month>-<version>-vmx.zip archive to
C:\Users\%USERNAME%\Virtual Machines\. 2. Right-click the archive and select Extract All from the contextual menu.
A Select a Destination and Extract Files dialog opens. By default, the location is the same folder as the archive is in: C:\Users\%USERNAME%\Virtual Machines\. Leave this as the destination folder. 3. Uncheck the Show Extracted Files When Complete checkbox and then click Extract. A folder called lighthouse is created inside C:\Users\%USERNAME%\Virtual Machines\.
IMPORT THE OPENGEAR LIGHTHOUSE VM FILE INTO VMWARE WORKSTATION PLAYER
1. Launch VMware Workstation Player. 2. Click Open a Virtual Machine.
24.12.1
Installing Lighthouse
56
Lighthouse User Guide
3. Navigate to C:\Users\%USERNAME%\Virtual Machines\lighthouse\. VMware Workstation Player points to Libraries > Documents and includes C:\Users\%USERNAME%\My Documents\. Assuming this is the case, double-click Virtual Machines and then double-click Lighthouse.
4. If only one file, Lighthouse, is visible, double-click on it to add the Lighthouse virtual machine to the VMware Workstation 12 Player virtual machines list. If more than one file displays, double-click Lighthouse.vmx. The Lighthouse virtual machine is added to the VMware Workstation 12 Player virtual machines list.
5. With Opengear Lighthouse VM selected in the VMware Workstation 12 Player virtual machine list, click Play Virtual Machine to boot Lighthouse.
VMWARE WORKSTATION PRO ON WINDOWS AS HOST
This procedure assumes VMware Workstation Pro is already installed on the host Windows machine, and that VMware-ready virtual machine files are stored in C:\Users\%USERNAME%\Virtual Machines\. If another location is preferred, adjust the steps as required.
IMPORT THE LIGHTHOUSE VM FILE INTO VMWARE WORKSTATION PRO
Step 1. Preparation: This step prepares the Lighthouse VM file for import into VMware Workstation Pro. 1. Move the lighthouse-<year>-<month>-<version>-vmx.zip archive to
C:\Users\%USERNAME%\Virtual Machines\. 2. Right-click the lighthouse-<year>-<month>-<version>-vmx.zip archive and select
Extract All from the contextual menu. A Select a Destination and Extract Files dialog opens. The location is the same folder as the PKZip archive is in: C:\Users\%USERNAME%\Virtual Machines\. Leave this as the
24.12.1
Installing Lighthouse
57
Lighthouse User Guide
destination folder. 3. Uncheck the Show Extracted Files When Complete checkbox and then click Extract.
A folder called lighthouse is created inside C:\Users\%USERNAME%\Virtual Machines\. Step 2. Import Lighthouse VM file: 1. Click Open a Virtual Machine. 2. Navigate to C:\Users\%USERNAME%\Virtual Machines\lighthouse\.
VMware Workstation Pro points to Libraries > Documents and this library includes C:\Users\%USERNAME%\My Documents\. 3. Double-click Virtual Machines and then double-click Lighthouse. 4. If only one file, Lighthouse, displays, double-click the file to add the Lighthouse virtual machine to the VMware Workstation Pro virtual machines list. If more than one file displays, double-click Lighthouse.vmx. The Lighthouse virtual machine is added to the VMware Workstation Pro virtual machines list. 5. With the Opengear Lighthouse VM selected in the My Computer listing and the subsequent Opengear Lighthouse VM tab open, click Power on this virtual machine to boot Lighthouse.
INSTALL LIGHTHOUSE VM ON HYPER-V ON WINDOWS
This section describes how to install Lighthouse VMs on Hyper-V on Windows: l Hyper-V running on Windows 10 or Windows Server 2016. l VirtualBox deployments.
RUN ON WINDOWS 10/WINDOWS SERVER 2016
This procedure assumes Hyper-V is already installed on a Windows 10/Windows Server 2016 host machine and the required Zip archive, -hyperv.zip is in C:\Users\%USERNAME%$\Downloads.
24.12.1
Installing Lighthouse
58
Lighthouse User Guide
1. Unzip lighthouse-<year>-<month>-<version>-hyperv.zip. 2. Navigate to the extracted folder. Make sure lighthouse.vhd and lighthouse_virtual_
machine_registration.ps1 are in the folder. 3. Right-click and choose Run with Powershell to execute the Powershell script. 4. Leave the host name empty when prompted to deploy Lighthouse to local machine. 5. Launch Hyper-V Manager.
Lighthouse should be registered as a new VM image under Virtual Machine. 6. Select Lighthouse from the list and click Start in the Action Panel to boot Opengear
Lighthouse.
REMOTE HYPER-V DEPLOYMENT WITH PRE-AUTHENTICATED USER
In this scenario, the user who performs Lighthouse deployment does not have local access to Hyper-V installed on Windows 2016. However, user has access to a Windows 10 which can manage the Hyper-V server remotely. This procedure assumes Hyper-V is installed on Windows Server 2016 (or later) host machine and the required Zip lighthouse-<year>-<month>-<version>-hyperv.zip is in C:\Users\%USERNAME%$\Downloads. Windows 10 is already configured to manage Hyper-V on Windows Server 2016.
Note: Windows 10 and Windows Server 2016 must have the same user (same password) created. The user who performs the deployment must have permission to both execute the Powershell script and deploy the image on Hyper-V.
1. Login to Windows 10 with the user mentioned above. 2. Unzip lighthouse-<year>-<month>-<version>-hyperv.zip. 3. Navigate to the extracted folder. Make sure lighthouse.vhd and lighthouse_virtual_
machine_registration.ps1 are in the folder. 4. Right-click and choose Run with Powershell to execute the Powershell script.
24.12.1
Installing Lighthouse
59
Lighthouse User Guide
5. Enter the fully qualified domain name for Windows Server 2016 when prompted to deploy Lighthouse to the remotely-managed Windows Server 2016 machine.
6. Launch Hyper-V Manager. Lighthouse should be registered as a new VM image under Virtual Machine for Windows Server 2016.
7. Select Lighthouse from the list and click Start in the Action Panel to boot Opengear Lighthouse.
VIRTUALBOX DEPLOYMENTS ON WINDOWS AS HOST
Lighthouse can be installed on the following hosts: l VirtualBox on Windows as host l VirtualBox on macOS as host l VirtualBox on Ubuntu as Host l VirtualBox on Fedora Workstation as host
VIRTUALBOX ON WINDOWS AS HOST
Note: We recommend that VirtualBox users customize their instances and change their network cards to one other than e1000. We also suggest virtio for better performance.
This procedure assumes VirtualBox is already installed on the host machine and the required PKZIP archive, lighthouse-<year>-<month>-<version>-ovf.zip is in C:\Users\%USERNAME%$\Downloads. 1. Unzip lighthouse-ovf.
It may appear as lighthouse-<year>-<month>-<version>-ovf.zip depending on the Windows Explorer preference settings.
24.12.1
Installing Lighthouse
60
Lighthouse User Guide
2. Right click the lighthouse-ovf archive and select Extract all from the context menu. The Select a Destination and Extract Files dialog opens. The destination is C:\Users\%USERNAME%\Downloads\Lighthouse-ovf.
3. Uncheck the Show extracted files when complete checkbox and edit the destination by removing Lighthouse-ovf from the path.
4. Click Extract. A folder called lighthouse-ovf is created inside C:\Users\%USERNAME%\Downloads\.
5. Launch VirtualBox. The Oracle VM VirtualBox Manager window displays.
6. Choose File > Import Appliance. The Appliance to Import dialog opens.
7. Click Expert Mode. The Appliance to import dialog changes from Guided Mode to Expert Mode.
8. Click the icon of a folder with an upward pointing arrow superimposed. This icon is to the far right of the Appliance to import field. The Open File dialog displays with C:\Users\%USERNAME%\Documents as the current folder.
9. Navigate to C:\Users\%USERNAME%\Downloads\Lighthouse.ovf\Opengear Lighthouse VM\.
10. Select the file Opengear Lighthouse VM and click Open. 11. Double-click the text vm in the Name row and Configuration column to make it editable. 12. Type Opengear Lighthouse VM and press Enter. 13. Click Import.
A new virtual machine, called Opengear Lighthouse VM is added to the list of virtual machines available to Virtual Box. 14. Select Opengear Lighthouse VM from the list.
24.12.1
Installing Lighthouse
61
Lighthouse User Guide
15. Select Machine > Settings or click the Settings icon in the VirtualBox Manager toolbar or press Control+S. The Opengear Lighthouse VM - Settings dialog displays.
16. Click the System option in the list of options running down the left-hand side of the dialog. The dialog shows the System options available as three tabs: Motherboard, Processor, and Acceleration. Depending on the underlying hardware platform, Acceleration may be greyedout and unavailable. The Motherboard tab is preselected.
17. In the Motherboard tab, select the Hardware Clock in UTC Time checkbox. 18. Click OK or press Enter. 19. Select Opengear Lighthouse VM from the list and click Start in the Oracle VM VirtualBox
Manager toolbar to boot Lighthouse. Double-clicking Opengear Lighthouse VM in the list also boots Lighthouse.
Note: Selecting the Hardware Clock in UTC Time checkbox is necessary because Lighthouse expects the hardware clock to be set to UTC, not local time. Unlike other Virtual Machine Managers, Virtual Box both exposes this option as a user-adjustable setting and does not set it to UTC by default.
VIRTUALBOX ON MACOS AS HOST
VirtualBox should already installed on the host macOS machine and the required PKZIP archive, lighthouse-<year>-<month>-<version>-ovf.zip is in ~/Downloads. 1. Unzip lighthouse-<year>-<month>-<version>-ovf.zip.
The folder Lighthouse-ovf is created in ~/Downloads and contains the following files and folders:
24.12.1
Installing Lighthouse
62
Lighthouse User Guide
2. Launch Virtual Box. The Oracle VM VirtualBox Manager window displays.
3. Select File > Import Appliance or press Command+I. The Appliance to Import dialog sheet slides down from the Oracle VM VirtualBox Manager toolbar.
4. Click Expert Mode. The Appliance to Import dialog sheet changes from Guided Mode to Expert Mode.
5. Click the icon of a folder with an upward pointing arrow superimposed. This icon is to the far-right of the Appliance to Import field. The Open File dialog sheet slides down from the Oracle VM VirtualBox Manager toolbar. This sheet opens with ~/Documents as the current folder.
6. Navigate to ~/Downloads/Lighthouse.ovf/Opengear Lighthouse VM/. 7. Select Opengear Lighthouse VM and click Open.
Depending on the Finder Preferences settings, the file may present as Opengear Lighthouse VM.ovf. 8. Double-click the text vm in the Name row and Configuration column to make it editable. 9. Type Opengear Lighthouse VM and press Enter. 10. Click Import. A new virtual machine, called Opengear Lighthouse VM is added to the list of virtual machines. 11. Select Opengear Lighthouse VM from the list. 12. Choose Machine > Settings. Or click the Settings icon in the VirtualBox Manager toolbar. The Opengear Lighthouse VM Settings dialog displays. 13. Click the System option in the dialog's toolbar. The dialog shows the System options available as three tabs: Motherboard, Processor, and Acceleration. (Depending on the underlying hardware platform, Acceleration may be greyedout and unavailable). The Motherboard tab is preselected. 14. In the Motherboard tab, select the Hardware Clock in UTC Time checkbox.
24.12.1
Installing Lighthouse
63
Lighthouse User Guide
15. Click OK or press Enter. 16. Select Opengear Lighthouse VM from the list and click Start in the Oracle VM VirtualBox
Manager toolbar to boot Lighthouse. Double-clicking Opengear Lighthouse VM in the list also boots Lighthouse.
Notes: l Selecting the Hardware Clock in UTC Time checkbox is necessary because Lighthouse
expects the hardware clock to be set to UTC, not local time. Unlike other Virtual Machine Managers, Virtual Box both exposes this option as a user-adjustable setting and does not set it to UTC by default. l By default, VirtualBox stores virtual machines in ~/VirtualBox VMs. If this is the first virtual machine setup by VirtualBox, it creates the VirtualBox VMs folder in the current user's home-directory and a folder -- Opengear Lighthouse VM -- inside the VirtualBox VMs folder. The Opengear Lighthouse VM folder contains the files and folders which make up Lighthouse when run under Virtual Box.
VIRTUALBOX ON UBUNTU AS HOST
Before you begin the procedure, make sure that VirtualBox and all required support files are installed on the host machine and the PKZIP archive, -ovf.zip, is in ~/Downloads. 1. Unzip lighthouse-<year>-<month>-<version>-ovf.zip.
The folder Lighthouse-ovf is created in ~/Downloads and contains the following files and folders:
2. Launch Virtual Box. The Oracle VM VirtualBox Manager window displays.
24.12.1
Installing Lighthouse
64
Lighthouse User Guide
3. Choose File > Import Appliance. The Appliance to import dialog opens.
4. Click Expert Mode. The Appliance to Import dialog changes from Guided Mode to Expert Mode.
5. Click the icon of a folder with an upward pointing arrow superimposed. This icon is positioned to the right of the Appliance to Import field. A file navigation dialog, Choose a Virtual Appliance to Import, opens with ~/Documents as the current folder.
6. Navigate to ~/Downloads/Lighthouse.ovf/Opengear Lighthouse VM/. 7. Select Opengear Lighthouse VM.ovf and click Open. 8. Double-click the text vm in the Name row and Configuration column to make it editable. 9. Type Opengear Lighthouse VM and press Enter. 10. Click Import.
A new virtual machine, called Opengear Lighthouse VM is added to the list of virtual machines available to Virtual Box. 11. Select Opengear Lighthouse VM from the list and click Start in the Oracle VM VirtualBox Manager toolbar to boot Lighthouse. Double-clicking Opengear Lighthouse VM in the list also boots Lighthouse.
Note: VirtualBox stores virtual machines in ~/VirtualBox VMs. If this is the first virtual machine setup by VirtualBox it creates the VirtualBox VMs folder in the current user's homedirectory and a folder Opengear Lighthouse VM inside the VirtualBox VMs folder. Inside Opengear Lighthouse VM are the files and folders which make up Lighthouse when run under Virtual Box.
24.12.1
Installing Lighthouse
65
Lighthouse User Guide
VIRTUALBOX ON FEDORA WORKSTATION AS HOST
Before you begin, make sure that VirtualBox and all required support files are already installed on the host machine and the PKZIP archive, -ovf.zip is in ~/Downloads. 1. Unzip lighthouse-<year>-<month>-<version>-ovf.zip.
The Lighthouse.ovf folder is created in ~/Downloads and contains the following files and folders:
2. Launch Virtual Box. The Oracle VM VirtualBox Manager window displays.
3. Choose File > Import Appliance or press Control-I. The Appliance to Import dialog opens.
4. Click Expert Mode. The Appliance to Import dialog changes from Guided Mode to Expert Mode.
5. Click the icon of a folder with an upward pointing arrow superimposed. This icon is to the far right of the Appliance to Import field. The Open File dialog opens with ~/Documents as the current folder.
6. Navigate to ~/Downloads/Lighthouse.ovf/Opengear Lighthouse VM/. 7. Select Opengear Lighthouse VM and click Open. 8. Double-click the text vm in the Name row and Configuration column to make it editable. 9. Type Opengear Lighthouse VM and press Enter. 10. Click Import.
A new virtual machine, called Opengear Lighthouse VM is added to the list of virtual machines available to Virtual Box.
24.12.1
Installing Lighthouse
66
Lighthouse User Guide
11. Select Opengear Lighthouse VM from the list and click Start in the Oracle VM VirtualBox Manager toolbar to boot Lighthouse. Double-clicking Opengear Lighthouse VM in the list also boots Lighthouse.
Note: VirtualBox stores virtual machines in ~/VirtualBox VMs. If this is the first virtual machine setup by VirtualBox, it creates the VirtualBox VMs folder in the current user's homedirectory and a folder Opengear Lighthouse VM inside the VirtualBox VMs folder. Inside Opengear Lighthouse VM are the files and folders which make up Lighthouse when run under Virtual Box.
INSTALL LIGHTHOUSE VM ON LINUX HOSTS
This section describes how to install Lighthouse VMs on the following Linux hosts: l Ubuntu l Fedora Workstation l RHEL
VIRTUAL MACHINE MANAGER ON UBUNTU AS HOST
Virtual Machine Manager and all required support files should be installed on the host machine. 1. Expand lighthouse-<year>-<month>-<version>-raw.hdd.tar. 2. Launch Virtual Machine Manager. 3. Click New at the top left of the Virtual Machine Manager window (or choose File > New Virtual
Machine). The Source Selection window opens. 4. Click Select a file. A Select a Device or ISO File dialog slides into view. 5. Select the file lighthouse-<year>-<month>-<version>-raw.hdd and click Open in the
top right-corner of the dialog. A Review window opens providing basic information about the virtual machine or box, as Boxes
24.12.1
Installing Lighthouse
67
Lighthouse User Guide
calls them, to be created. 6. Click Create in the top right corner of the Review window.
A new virtual machine instance, Opengear_Lighthouse_VM-disk1, is created and presented in the Boxes window.
BOXES ON FEDORA WORKSTATION AS HOST
Boxes and all required support files should be installed on the host machine and lighthouse<year>.<month>.<release number>-ovf.zip is in ~/Downloads. 1. Unzip lighthouse-<year>-<month>-<version>-ovf.zip.
The Lighthouse.ovf folder is created in ~/Downloads and contains the following files and folders:
2. Launch Boxes. 3. Click New in the Boxes window title bar.
The Source Selection window opens. 4. Click Select a File.
A Select a Device or ISO File dialog opens. 5. Navigate to ~/Downloads/Lighthouse.ovf/Opengear Lighthouse VM/. 6. Select the file Opengear_Lighthouse_VM-disk1.vmdk and click Open in the top right-hand
corner of the dialog. A Review window opens providing basic information about the virtual machine (or `box', as Boxes calls them) to be created.
24.12.1
Installing Lighthouse
68
Lighthouse User Guide
7. Click Create in the top right corner of the Review window. A new virtual machine instance, Opengear_Lighthouse_VM-disk1 is created and presented in the Boxes window.
8. To rename the virtual machine instance, right-click on the machine instance and choose Properties from the contextual menu that displays. Click anywhere in the Name field to select and edit the name. Click Close to save the changes.
CENTOS AS HOST
CentOS should be installed, complete with the Gnome desktop environment as the host operating system. CentOS includes the full complement of KVM-centric virtualization tools including the GUI-based virtualization management tools Boxes and virt-manager and the shell-based virtualization management tool virsh. This procedure assumes Boxes is used to setup and manage the Lighthouse VM and that the required PKZIP archive, lighthouse-<year>-<month>-<version>-ovf.zip is in ~/Downloads. To install Lighthouse on CentOS: 1. Unzip lighthouse-<year>-<month>-<version>-ovf.zip.
The Lighthouse.ovf folder is created in ~/Downloads and contains the following files and folders:
2. Launch Boxes. 3. Click New in the Boxes title bar. 4. Navigate to ~/Downloads/Lighthouse.ovf/Opengear Lighthouse VM/.
24.12.1
Installing Lighthouse
69
Lighthouse User Guide
5. Select Opengear Lighthouse VM and click Open. A new virtual machine, called Opengear LighthouseVM is added to the list of virtual machines available to Boxes.
INSTALL IN THE CLOUD
This section describes how to install Lighthouse on the following supported cloud environments: l Azure l Amazon Web Services (AWS)
INSTALL IN AZURE
To install in the Microsoft Azure environment, complete the following steps: 1. Create storage and add Lighthouse VHD Image 2. Create an Image 3. Create a Virtual Machine 4. Configure firewall rules for the virtual machine 5. Check endpoints in Lighthouse
BEFORE YOU BEGIN
l Download a Lighthouse VHD image. You can find the latest Lighthouse in a zip file at the following URL: https://ftp.opengear.com/download/lighthouse_ software/current/lighthouse/azure.
Note: Ensure that you decompress the file and then validate the hash of the decompressed file.
l Install AzCopy following the instructions provided by Microsoft, See Get started with AzCopy. l Determine the user name you want to use for the Microsoft Azure admin user.
24.12.1
Installing Lighthouse
70
Lighthouse User Guide
l Ensure that you have an Azure user account with permission to create storage accounts. l Consider the ports that may need to be open on the firewall for the virtual machine.
CREATE STORAGE AND ADD LIGHTHOUSE VHD IMAGE
IMPORTANT: Before you perform this procedure, ensure that you have read the Before you begin section.
1. Login to the Microsoft Azure portal at https://portal.azure.com. 2. Under Azure Services, click the Storage Accounts icon. 3. Create a storage account:
a. At the top of the page, click Create. The Create a storage account page displays.
b. Create a storage account with at least 50GB of storage space.
Note: Navigate through the tabs and complete any mandatory fields as required for your organization, ensuring that you select at least 50GB of storage space.
c. At the bottom of the page, click Review + create. d. Wait for validation to complete, then at the bottom of the page, click Create. 4. Navigate to the newly created storage account.
Note: You can either click the Go to resource button immediately after the storage account is created, or you can navigate to Azure Services, click the Storage Accounts icon and then click the storage account.
5. In the left-hand menu, expand Data storage and then click Containers. 6. At the top of the page click + Container to create a new blob container.
24.12.1
Installing Lighthouse
71
Lighthouse User Guide
7. In the New container dialog on the right-hand side, enter a Name for the blob container, then click Create. The new container appears on the Containers page.
8. Use AzCopy to copy the Lighthouse VHD image into the Azure storage container:
Note: AzCopy is recommended because the VHD image is large and the upload can take a long time to complete through the Microsoft Azure portal.
a. Ensure that you have installed AzCopy. See the Before you begin section. b. Generate a SAS token to use in your AzCopy commands:
i. Ensure that you are viewing the newly created storage container.
Note: If you are still on the Containers page after step 7, click the name of the container.
ii. On the left-hand menu, expand Settings and then click Access policy. iii. Under the Stored access policies section, click Add policy.
The Add policy dialog displays. iv. Enter the Identifier. v. Click the Permissions drop-down and select Read, Write, and Create from the list. vi. Set a valid Start time and Expiry time. vii. Click OK.
The Add policy dialog closes. viii. At the top of the page, click Save. ix. On the left-hand menu, expand Settings and then click Shared access tokens.
x. From the Stored access policy drop-down, select the policy you added in steps iii to viii. xi. At the bottom of the page, click Generate SAS token and URL. xii. When they appear, copy the Blob SAS token and Blob SAS URL.
24.12.1
Installing Lighthouse
72
Lighthouse User Guide
Note: The Blob SAS token and Blob SAS URL must be copied at this point in the process as you cannot view the information again after this step.
c. Copy the Lighthouse VHD image into the Azure storage container using the following format: ./azcopy copy <path_to_local_image_file> "<blob_sas_url>". Ensure that you use the path to your local Lighthouse VHD image and the Blob SAS URL generated in steps xi and xii.
Note: You can also create a SAS token using Azure CLI. See Microsoft instructions to Create a user delegation SAS for a container.
9. Complete the steps in Create an Image.
CREATE AN IMAGE
1. Ensure that you have completed the steps in Create storage and add the Lighthouse VHD image.
2. In the Azure Portal, under Azure Services, click the Images icon. The Images page displays.
3. At the top of the page, click Create. The Create an image page displays.
4. On the Basics tab, configure the following settings:
Note: Navigate through the tabs and complete any mandatory fields as required for your organization, ensuring that the settings in the following table are configured as described.
24.12.1
Installing Lighthouse
73
Lighthouse User Guide
Section
Field
Instance details
Region
OS disk
OS type VM generation Storage blob
Configuration
From the drop-down, select the location that is the same as your storage account.
Select the Linux radio button.
Select the Gen 1 radio button.
1. Click Browse. 2. When the Storage accounts page displays, click the
storage account to use. 3. When the Containers page displays, click the
container to use. 4. Then from the specific container page, click the
Lighthouse VHD file you uploaded in Create storage and add the Lighthouse VHD image. 5. At the bottom of the page, click Select.
5. At the bottom of the page, click Review + Create. 6. Wait for validation to complete, then at the bottom of the page, click Create. 7. After deployment finishes, complete the steps in Create a virtual machine.
CREATE A VIRTUAL MACHINE
1. Ensure that you have completed the steps in Create an image. 2. Navigate to the image you created in step 1.
24.12.1
Installing Lighthouse
74
Lighthouse User Guide
Note: You can either click the Go to resource button immediately after the image is created, or you can navigate to Azure Services, click the Images icon and then click the image.
3. At the top of the page, click Create VM. The Create a virtual machine page displays.
4. On the Basics tab, configure the following settings:
Note: Navigate through the tabs and complete any mandatory fields as required for your organization, ensuring that the settings in the following table are configured as described.
Section Instance details
Field Size
Configuration
From the drop-down, select the required virtual machine instance size.
24.12.1
Installing Lighthouse
75
Section
Administrator account
Lighthouse User Guide
Field
Configuration
Authentication type
Select the radio button for the type of authentication the Microsoft Azure admin user will use:
l Password - password and confirm password field
l SSH public key If you select SSH public key authentication, the user is created without a password and will be unable to access the UI. You must set a password on lighthouse via SSH to login via GUI. To do this, log into Lighthouse via SSH keys, and use the ogpasswd utility to set the password in the following format: ogpasswd -u lh_admin -p MySecretPassword. Make sure that you replace "lh_admin" with the same username as the Mircrosoft Azure admin user that you enter in the next field and replace "MySecretPassword" with a password that meets your organizational requirements.
Username
Enter the username for the Microsoft Azure admin user. This defaults to "azureuser" but it is recommended to change this for security purposes.
SSH public key source
This defaults to Generate new key pair.
24.12.1
Installing Lighthouse
76
Lighthouse User Guide
Section
Field
Inbound port rules
Select inbound ports
Configuration
From the drop-down, select the inbound ports enabled for the Lighthouse instance; SSH and HTTPS.
5. At the bottom of the page, click the Next: Disks > button to move to the Disks tab. 6. Under OS disk, from the OS disk type drop-down, select the required storage option for the
boot disk. 7. At the bottom of the page, click Review + Create. 8. Wait for validation to complete, then at the bottom of the page, click Create.
Note: Depending on your key pair selection, a dialog may appear, click the appropriate option to continue.
9. In the left menu for the virtual machine, expand Help, and then click Serial console. The serial console opens and Lighthouse should now be deploying on Microsoft Azure.
10. Complete the steps in Configure firewall rules for the virtual machine.
CONFIGURE FIREWALL RULES FOR THE VIRTUAL MACHINE
Add these firewall rules on the virtual machine you deployed to allow nodes to enroll in Lighthouse. Talk to your organizational security team for any additional configuration required when adding these rules. 1. Ensure that you have completed the steps in Create a virtual machine. 2. Navigate to the virtual machine you created in step 1.
24.12.1
Installing Lighthouse
77
Lighthouse User Guide
Note: You can either click the Go to resource button immediately after the virtual machine is created, or you can navigate to Azure Services, click the Virtual Machines icon and then click the virtual machine.
3. In the left menu for the virtual machine, expand Networking, and then click Network settings.
Note: Your public IP address is listed at the top of the page.
4. Configure the following rules:
Note: To add each rule, click the Create port rule button and click Inbound port rule from the list that appears.
l Add a rule to allow UDP connections from any source to port 1194 on the instance's internal network address (10.0.0.x).
l Add a rule to allow UDP connections from any source to port 1195 on the instance's internal network address (10.0.0.x).
l Confirm that HTTPS and SSH are allowed from the initial setup. If not, add them. l You may require other ports open, depending on feature usage. For example:
l SNMP (UDP/161 or TCP/161) SNMP Management l OpenVPN (UDP/1195) Lighthouse Multiple Instance VPN l HTTPS (TCP/8443) Alternate REST API port 5. Return to the Virtual Machines page and select the virtual machine. 6. Complete the steps in Check endpoints in Lighthouse.
24.12.1
Installing Lighthouse
78
CHECK ENDPOINTS IN LIGHTHOUSE
Lighthouse User Guide
Note: Before you check the endpoints, ensure that you have created the SSH password to log into Lighthouse. For more information, see the Authentication type configuration information in step 4 of Create a virtual machine.
1. Ensure that you have completed the steps in Configure firewall rules for the virtual machine. 2. Open and log in to Lighthouse. 3. In the Settings Pane, select > SYSTEM > Network Settings.
The NETWORK SETTINGS page displays. 4. Under External Network Addresses, confirm that the Azure instance public IP address has
been added to the external endpoints.
Note: At a minimum, ensure that there is at least one IP address present for use in node and secondary Lighthouse enrollment.
INSTALL IN AMAZON WEB SERVICES (AWS)
To use Lighthouse with Amazon Web Services (AWS), you must have an Amazon Machine Image (AMI) that contains Lighthouse in the AWS region in which you want to deploy Lighthouse. You can: l Manually create an AMI on AWS, or l Subscribe to the Opengear Lighthouse AMI on AWS Marketplace
BEFORE YOU BEGIN
Before you perform any procedures in this section, ensure that you have an account on AWS with an IAM user, a key pair and an access key:
24.12.1
Installing Lighthouse
79
Lighthouse User Guide
l The IAM user should have, at a minimum, permissions to create, attach, delete, and snapshot EBS volumes as well as create an Amazon Machine Image (AMI).
l If you are using IAM Identity Center, you can use an IAM Identity Center user with the same permissions instead. Consult Amazon documentation for more information if required.
CHANGES TO DEFAULT SETTINGS
Caution: With Lighthouse version 24.06.0 and later, changes have been introduced related to the root user and SSH Password Authentication default settings that impact any newly launched Lighthouse AWS instances.
Changes impacting the root user: l For security purposes the root user is disabled by default. The root user can be enabled by
going to > USERS & ACCOUNTS > Local Users. l A new user called lhadmin is provided that should be used for initial configuration. l SSH connection for root is also disabled by default. To enable, navigate to > USERS &
Accounts > SSH Authentication. l Ensure to run all commands with appending sudo. Changes impacting SSH Password Authentication: l SSH Password Authentication is disabled by default. l User accounts require a Public SSH Key associated with the account. l Users will use their Private SSH key to connect via SSH. l The lhadmin user will default with the AWS key pair that was used to create the Lighthouse
Instance. l To associate a Public SSH Key to the account navigate to > USERS & ACCOUNTS > Local
Users and add the SSH Authentication Key to the user.
24.12.1
Installing Lighthouse
80
Lighthouse User Guide
LIMITATIONS
AWS support is currently limited to: l All standard Lighthouse operations. l Running on the AWS platform. l Providing aws-cli tools for interaction with AWS. l Loading the provided SSH key for the lhadmin user. l Running custom scripts on startup (see above). l Providing a lhadmin password via userdata (see above). At this time Lighthouse does not support: l Using AWS database services. l Using AWS redis services. l Using any of AWS scalability functionality.
Note: If you want to deploy Lighthouse across different AWS regions, an AMI is required in each region. Amazon supports copying AMIs between regions and offers a walkthrough of the necessary steps to do this.
MANUALLY CREATE AN AMI ON AWS
To create a private Lighthouse AMI, you should use a temporary Linux "build-box" EC2 instance.
Note: This is a one-time procedure. The AMI can be used to create multiple instances of Lighthouse, and upgrades can be performed through the Lighthouse Web UI.
24.12.1
Installing Lighthouse
81
Lighthouse User Guide
IMPORTANT: Before you perform this procedure, ensure that you have an account on AWS with an IAM user, a key pair and an access key. For more detailed requirements, see Before you begin.
1. Log into AWS, and navigate to the Instances page. 2. On the top-right of the page, click Launch Instances.
The Launch an instance page displays. 3. Create an AWS EC2 Linux instance, with the following settings:
Section
Configuration
Name and tags
Enter a name.
Application and OS Images (Amazon Machine Image)
Select Amazon Linux 2 or Amazon Linux 2023.
Instance type
Select t3.large instance type with a default (8 GiB) root volume.
Configure storage
Select 50GB gp3 volume
Note: Consult Amazon documentation for more information if required. 4. On the right-hand side of the page, click Launch Instance.
24.12.1
Installing Lighthouse
82
Lighthouse User Guide
5. On your machine, open a Command Line Interface to create a Lighthouse AMI, using the lighthouse-aws-bootstrap.sh script (usage information can be displayed by using the -h option) on the EC2 instance created in the previous steps: a. Connect via SSH to your instance on AWS using the username ec2-user and the private key you created previously. All subsequent steps must be performed on the instance.
Note: To do this, go to the Instances page and select the instance you created in the previous steps. On the -right-hand side of the details pane for the instance, click Connect then select the SSH client tab on the Connect to instance page. Follow the steps on the page to SSH into your instance.
b. Configure AWS using the following command: aws configure
c. Provide the access key and region details (other settings may be left unchanged). If you are using IAM Identity Center, you must instead configure using aws configure sso, and set the CLI Profile Name to be default.
d. Download the aws-bootstrap script: wget http://ftp.opengear.com/download/lighthouse_ software/current/lighthouse/aws/lighthouse-aws-bootstrap.sh
e. Run the lighthouse-aws-bootstrap.sh script as follows: bash ./lighthouse-aws-bootstrap.sh -n Lighthouse -r https://ftp.opengear.com/download/lighthouse_ software/current/lighthouse/aws/lighthouse-<year>-<month><version>.aws.raw.tar The following is an example of a running bootstrap script:
$ bash ./lighthouse-aws-bootstrap.sh -n Lighthouse -r \ > http://ftp.opengear.com/download/lighthouse_ software/current/lighthouse/aws/lighthouse-24.12.1.aws.raw.tar Downloading image... Image size is 54049899008 bytes (51 GiB)
24.12.1
Installing Lighthouse
83
Lighthouse User Guide
Creating volume... Attaching volume vol-09fb0b463f5a59eaf to EC2 instance... Cloning image onto volume... 0+852971 records in 0+852971 records out 54049899008 bytes (54 GB, 50 GiB) copied, 845.072 s, 64.0 MB/s Creating snapshot of volume... Waiting for snapshot snap-0f83746856d985070 to complete... Creating AMI from snapshot snap-0f83746856d985070... Done! Cleaning up...
f. Wait while the Lighthouse AMI is created. This can take up to 30 minutes.
g. After the AMI has been created, terminate the Linux EC2 instance to avoid incurring additional costs.
6. In AWS, navigate to the Amazon Machine Images (AMIs) page of the EC2 Management Console.
7. Select the Lighthouse AMI. The Imagine summary for ami-[ID] displays.
8. On the top-right of the page, click Launch instance from AMI. The Launch an instance page displays.
9. Complete the steps in Configure and Launch the Instance.
SUBSCRIBE TO THE OPENGEAR LIGHTHOUSE AMI ON AWS MARKETPLACE
Lighthouse is available on Amazon Web Services (AWS) Marketplace. You can subscribe to get access to our published AMIs.
Note: You must still contact Sales to obtain a license.
24.12.1
Installing Lighthouse
84
Lighthouse User Guide
IMPORTANT: Before you perform this procedure, ensure that you have an account on AWS with an IAM user, a key pair and an access key. For more detailed requirements, see Before you begin.
1. In your Web browser, go to AWS Marketplace: Opengear Lighthouse Software AMI. The Opengear Lighthouse Software AMI page displays.
Note: Log in if you are prompted to do so. Alternatively, you can log in to AWS Marketplace first, then type "Opengear Lighthouse Software AMI" into the marketplace search bar and click on the item that appears in the search results.
2. Subscribe to the AMI: view the purchase options and then accept the terms. 3. Navigate to your Manage subscriptions page.
You can find this under your AWS Marketplace Account information. A list of subscriptions appears. 4. Locate the Opengear Lighthouse Software AMI subscription in the list. 5. On the right-hand side of the row for the subscription, under Actions, click Launch. The Launch new instance page displays. 6. From the Software version drop-down, select the latest version of Lighthouse. 7. From the Region drop-down, select the region. 8. Click the Continue to launch through EC2 button. The Launch an instance page displays. 9. Complete the steps in Configure and Launch the Instance.
24.12.1
Installing Lighthouse
85
Lighthouse User Guide
CONFIGURE AND LAUNCH THE INSTANCE
1. Ensure that you have completed one of the following: l Manually created an AMI on AWS. l Subscribed to the Opengear Lighthouse AMI on AWS Marketplace.
Note: You should have the Launch an instance page open.
2. Configure the following sections:
Section
Configuration
Summary
On the right-hand side pf the page, enter the Number of instances you want to launch.
Names and tags
Enter any names and tags you want to use for the instance. These are user defined and set the configuration of what fields and values are displayed for the instance in AWS.
Application and OS Images (Amazon Machine Image)
This defaults to the AWS AMI that you have launched or selected. Confirm that the correct version, Lighthouse, or AMI are displayed in this section as appropriate.
Note: The user name in this section should display as lhadmin.
24.12.1
Installing Lighthouse
86
Lighthouse User Guide
Section Instance Type
Key Pair
Configuration
From the Instance Type drop-down, select the instance type. Lighthouse should run on a general purpose instance type, such as M5.
Note: If an instance type that supports "burstable" CPU such as T2 is used, ensure that unlimited CPU is selected, to avoid operational problems caused by CPU throttling.
For more information on Amazon EC2 instance types, see Amazon EC2 Instance types. When you chose your instance type, ensure that it is compatible with our recommended Lighthouse Virtual Machine Host Requirements.
EC2 requires a key pair to be specified when launching instances; from the Key pair name list, select your key pair. You should already have a key pair. For more information, see Before you begin.
24.12.1
Installing Lighthouse
87
Lighthouse User Guide
Section
Configuration
Network Settings
A security group should be created; select the Create security group radio button and complete the appropriate steps to create the security group. Lighthouse requires some ports to be open: l SSH (TCP/22) Secure Shell. Access should be limited to just your corporate
network. l HTTPS (TCP/443) Lighthouse Web UI and REST API. This is used by both
web browsers and nodes. For example, call-home enrollment. l OpenVPN (UDP/1194) Lighthouse VPN. This is used to communicate with
nodes after they are enrolled. l Other ports may be required to be opened, depending on feature usage. For
example:
o SNMP (UDP/161) SNMP Management o OpenVPN (UDP/1195) Lighthouse Multiple Instance VPN o HTTPS (TCP/8443) Alternate REST API port
Configure Storage
By default, the root volume is around 53 GiB. This may be sufficient, depending on your intended usage. It is easier to specify more storage now, but more can be added later.
24.12.1
Installing Lighthouse
88
Lighthouse User Guide
Section
Configuration
Advanced Details
Scroll down to the User data - optional heading, and in the text field, and set the lhadmin password for the instance in the following format: password=topSecretPassword123.
Note: If you do not specify the lhadmin password here, you can log into Lighthouse via SSH keys and use the ogpasswd utility to set the password: ogpasswd -u lhadmin -p MySecretPassword.
3. On the right-hand side of the page, click Launch Instance. On successful launch, a success message displays. The instance is now viewable on the Instances page, but may take five minutes to deploy.
4. To open Lighthouse from the instance: a. Ensure that you are viewing the Instances page in AWS. b. Click the Instance ID in the grid. c. In the details pane, click open address under the Public IPv4/IPv6 address.
ADD DISK SPACE TO LIGHTHOUSE
Additional physical volumes can be added to the volume group as required, and the logical volumes extended using lvextend and resize2fs to take advantage of the additional space. Before you add disk space: l Ensure you take a backup of Lighthouse l In the case of a multiple instance Lighthouse installation, consider upgrading all instances, not
merely the primary instance.
24.12.1
Installing Lighthouse
89
Lighthouse User Guide
After you add the disk space using one of the following procedures, expand the logical volume using the new disk space. See Utilize the Added Disk on the Lighthouse VM.
ADD A NEW DISK TO AWS
Launch a Lighthouse instance as per our guidelines or your own deployment processes and note the instance ID. To add a volume to an AWS Lighthouse without having to shut down the Lighthouse: 1. In the AWS web console, go to Volumes and create a new 50GB volume in the same
availability zone as your LH instance. 2. After the volume is created, select it and click the Actions button and select Attach Volume. 3. Enter the LH instance ID for the instance field and /dev/xvdb (or /dev/xvdd, /dev/xvde
and so on) as the device and click Attach. When you SSH into the LH you should be able to see the new volume as /dev/xvdb (or whatever device name you gave it).
ADD A NEW DISK - QEMU SPECIFIC INSTRUCTIONS
Launch a qemu Lighthouse instance as per our guidelines or your own deployment. To add a volume to the instance: 1. Shutdown the instance with the following command:
shutdown -h now 2. Create a new disk for the LH. You can use a different number for "count" which is in MiB.
dd if=/dev/zero of=/tmp/new_lh_disk.lh_hdd bs=1024k count=256 qemu-img convert -p -f raw -O qcow2 /tmp/new_lh_disk.lh /tmp/new_lh_ disk.qcow2
24.12.1
Installing Lighthouse
90
Lighthouse User Guide
3. Restart your qemu instance but make sure to add the new qcow2 disk to the command. Here is an example of what you should add to your qemu command when launching the instance: -drive if=scsi,file=/tmp/new_lh_disk.qcow2
Note: This is just an example. You should specify the disk in a similar way to how you specified the primary Lighthouse disk and make sure that the new disk is specified last, otherwise your disk will appear out of order when you boot the Lighthouse.
When the LH boots, you should have a new /dev/sdX device and the 'unused_disks' command should report that disk when you log in.
ADD A NEW DISK - AZURE
Launch the LVM Lighthouse instance as per our guidelines or your own deployment. To add a volume to the instance, use the following link to attach a new disk to your Lighthouse VM. Stop before you reach the section, "Connect to the Linux VM to mount the new disk." https://docs.microsoft.com/en-us/azure/virtual-machines/linux/attach-disk-portal
ADD A NEW DISK - HYPER-V
Launch the LVM Lighthouse instance as per our guidelines or your own deployment. To add a volume to the instance: 1. Shutdown your Hyper-V Lighthouse instance. 2. Open your Hyper-V manager. 3. Navigate to the VM list and locate your Lighthouse VM. 4. Right click on the instance and click Settings. 5. Click on the SCSI controller. 6. Select Hard drive on the right and click Add.
24.12.1
Installing Lighthouse
91
Lighthouse User Guide
7. Select Virtual hard disk and click New. 8. Follow the prompts and select the options that best suit your requirements and environment. 9. After you've created the disk, click Apply in the VM settings window. 10. Restart the Lighthouse.
ADD A NEW DISK - VIRTUALBOX
Launch the LVM Lighthouse instance as per our guidelines from the .ova file or your own deployment. To add a volume to the instance: 1. Shutdown the Lighthouse instance. 2. In the VirtualBox UI, locate your Lighthouse instance and right-click it. 3. Select Settings. 4. Select Storage on the left. 5. Click the Controller: SCSI in the disk list. 6. You will see two small icons, both with a green '+' symbol. Hover your mouse over the one that
says Adds a hard disk and click it. 7. Click the Create icon. 8. Follow the prompts to create a new disk image. 9. Select the new disk image and click the Choose button. 10. Click Ok to exit the VM settings window. 11. Restart Lighthouse.
UTILIZE THE ADDED DISK ON THE LIGHTHOUSE VM
After you have added additional disk space to Lighthouse using your preferred platform, you can expand the logical volume to use the new disk space using one of the following methods:
24.12.1
Installing Lighthouse
92
l Increase the LH_Data Logical Volume, OR l Mount the Hard Disks with ogconfig-cli
Note: The preferred method is to increase the LH_Data logical volume.
Lighthouse User Guide
INCREASE THE LH_DATA LOGICAL VOLUME
Note: This is the preferred method to use added disks on the Lighthouse VM.
1. Add the new disk to the LH VM (platform dependent, see Add Disk Space to Lighthouse). 2. Log into the shell on Lighthouse. you should see the new "unused" disk listed in the welcome
message. This is the case for any non-system disks aren't currently being used by the LVM system. 3. Create a partition on the new disk: fdisk /dev/sdb (or /dev/xvdb, or /dev/(sd|xvd)X
Note: Be sure specify the correct disk, it might be /dev/xvdb on AWS.
4. Type 'n' and ENTER to create a new partition. 5. Type 'p' and ENTER to create a primary partition. 6. Continue hitting ENTER to accept the defaults to use the whole disk. 7. Type 'w' and ENTER to write the changes and exit:
fdisk. 8. Add the new partition as a physical volume:
pvcreate /dev/sdb1
24.12.1
Installing Lighthouse
93
Lighthouse User Guide
Note: Assuming you are now using /dev/sdb1 that /dev/xvdb1 will now be mapped to /dev/sdb1 so make sure you use sdb1.
9. Extend the volume group with the new physical volume: vgextend lhvg /dev/sdb1
10. Assuming the new disk gives you at least 2GB of extra space, expand the lh_data logical volume: lvextend -L +2G /dev/mapper/lhvg-lh_data
11. Update the file system of the lh_data disk to use the extra space: resize2fs /dev/mapper/lhvg-lh_data
12. When you log into the shell, the disk should no longer be listed as "unused".
MOUNT THE HARD DISKS WITH OGCONFIG-CLI
Extra hard disks can be mounted in the Lighthouse VM by adding them to the configuration. Each new disk must have a partition created and formatted. Partitions can be created using fdisk or cfdisk, and should be formatted using the ext4 filesystem, using the mkfs.ext4 command: root@lighthouse:~# mkfs.ext4 /dev/sdb1 The directory in which to mount the filesystem must be created. In general, new filesystems should be mounted in the provided mountpoint of /mnt/au. Any other filesystems should be mounted within the filesystem mounted here. The UUID can be obtained by running blkid. This will output the UUID's of all the extra hard disks on the system. When referencing the UUID, ensure the entire UUID is enclosed within quote marks like this: "UUID=33464920-f54f-46b6-bd84-12f76eeb92da" else the command will not run correctly.
24.12.1
Installing Lighthouse
94
Lighthouse User Guide
Add the information to the configuration system using ogconfig-cli as follows, modifying the path for the specific situation.
ogcfg> var m !append system.mountpoints map {8435270-fb39-11e7-8fcf-4fa11570959}: Map <> ogcfg> set {m}.node "UUID=33464920-f54f-46b6-bd84-12f76eeb92da"{b8c37c6-fb39-11e7971c-23517b19319}: String </dev/sdb1> ogcfg> set {m}.path "/mnt/aux" {1fb50d8-fb39-11e7-994c-0f10b09cbd4}: String </mnt/aux> ogcfg> push OK
24.12.1
Installing Lighthouse
95
Lighthouse User Guide
SETTING UP LIGHTHOUSE
This section describes how to set up Lighthouse to monitor and manage your network.
LOAD LIGHTHOUSE
This section describes the initial setup stages for a new Lighthouse VM, from login, to setting external addresses, to setting the clock. When you first load Lighthouse, a warning message displays because of the default self-signed certificate. You can ignore this at first load, and later install your own valid certificate using > SERVICES > HTTPS Certificate to remove the warning message.
LIGHTHOUSE IP ADDRESSES
When the Lighthouse VM is booted and running, it can be reached via the following options: l The static address, 192.168.0.1. l The address it is assigned by any DHCP server it finds. Type ifconfig command to see which
IP address the VM has been allocated by DHCP. l Static IP address on another subnet, requiring IP address, mask, gateway. Only the first two options are available out-of-the-box. The static IP on another subnet has to be configured first. If there is no DHCP, and Lighthouse is not reachable on the default address 192.168.0.1, then the static IPv4 address can be changed from the console using the ogsetnetwork.sh command.
root@lighthouse:~# ogsetnetwork.sh --help
24.12.1
Setting up Lighthouse
96
Lighthouse User Guide
USAGE
ogsetnetwork.sh [Use options below to configure a static IP] -a, --address Static IP address to set -n, --netmask Netmask for IP address -g, --gateway Network gateway address -d, --dns1 Chosen DNS server #1 -D, --dns2 Chosen DNS #2
EXAMPLE
ogsetnetwork.sh -a 192.168.1.24 -n 255.255.255.0 -g 192.168.1.1
FIRST BOOT OF THE LIGHTHOUSE VM
Note: This section does not apply to Azure or AWS.
During boot, two screens open. 1. The first screen prompts to Select Lighthouse boot mode and displays four options:
l Graphics console boot l Graphics console recovery mode l Serial console boot l Serial console recovery mode
Graphics console boot is preselected and should not be changed. After the first boot has completed a message displays:
Welcome to Lighthouse. This is software version: 202512.1
24.12.1
Setting up Lighthouse
97
Lighthouse User Guide
2. The final step in the initial setup displays:
To complete initial setup, please set a new root password. Press ENTER to continue.
3. After pressing Enter, a prompt displays:
Enter new root password:
4. Enter a password and press Enter. Note: It is recommended that you set a temporary password at this point and change it to a very strong high-entropy password as soon as possible using the WebUI.
Tip: Keep in mind that non-US-English keyboards are not supported in the graphics console. 5. The confirm prompt displays:
Confirm given password
6. Re-enter the password and press Enter. Multiple configuration notices appear ending with a login prompt:
lighthouse login:
7. Enter root and press Enter. A password prompt displays:
Password:
8. Enter the newly-set password and press Enter. A standard bash shell prompt displays with the list of static, DHCP, and IPv6 addresses.
24.12.1
Setting up Lighthouse
98
Lighthouse User Guide
net1 192.168.0.1/24 net1:dhcp 192.168.1.186/24 net1 fe80::a00:27ff:fe39:daa3/64 root@lighthouse:~#
SET THE LIGHTHOUSE HOSTNAME
To set the hostname for a running Lighthouse instance: 1. In the Settings Pane, select > SYSTEM > Network Settings.
The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected. 2. Edit the Hostname as required.
Note: Host names must follow the naming conventions: l ASCII alphanumerical characters plus '-'. l Maximum 64 characters.
3. Under DIRECT ACCESS PORT CONFIGURATION, edit the SSH Port. 4. Click Apply.
ADD EXTERNAL IP ADDRESSES MANUALLY
On the initial Lighthouse boot, external endpoints are managed by Lighthouse and populated based on the current IPv4 and Ipv6 connections in Lighthouse. The external network address list updates depending on whether connections are added, updated, or removed. You can optionally add external IP addresses for a Lighthouse instance to the configuration for that instance. External IP addresses can be IPv4, IPv6, or DNS names and are sent to a remote node during Enrollment in the order configured. In general, these should not be changed except by a network support engineer.
24.12.1
Setting up Lighthouse
99
Lighthouse User Guide
l If you manually add external IP addresses to a Lighthouse configuration: l these addresses are sent to a remote node during enrollment. l any nodes that are already enrolled are not updated and must be re-enrolled to get the updated configuration. l Lighthouse no longer manages the list by default, and changes to connections do not change the external endpoints list.
l If you do not manually add external IP addresses, default external IP addresses are used.
Note: If you remove all external endpoints, then the list returns to Lighthouse Managed and populates the list with the connections on Lighthouse.
To add external addresses to the configuration for a Lighthouse instance: 1. In the Settings Pane, select > SYSTEM > Network Settings.
The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected. 2. Under EXTERNAL NETWORK ADDRESSES, click Add External Network Address.
The ADD EXTERNAL NETWORK ADDRESS dialog displays.
3. Enter the External Endpoint address.
4. If the ports used on the entered IP address are different from the default settings, change the API Port, VPN Port, or Multi-Instance VPN Port .
5. Click Add Address.
To change the order in which manually added IP addresses are sent to remote nodes:
1. Use the
icons to change the order in which the IP addresses are listed.
2. Click Apply.
EXAMINE OR MODIFY THE LIGHTHOUSE SSL CERTIFICATE
Lighthouse ships with a private SSL Certificate that encrypts communications between it and the browser. Most browsers display a warning message when first trying to access Lighthouse.
24.12.1
Setting up Lighthouse
100
Lighthouse User Guide
Note: If you plan to use the Lighthouse Multiple Instance feature, the certificate is used on all instances. In this case, we recommend using a wildcard certificate.
To examine this certificate or generate a new Certificate Signing Request: 1. In the Settings Pane, select > SERVICES > HTTPS Certificate.
The details of the CURRENT SSL CERTIFICATE display. 2. To generate a new SSL certificate, complete the fields in the NEW SIGNING REQUEST form.
SET THE LIGHTHOUSE INTERNAL CLOCK
Lighthouse and Node system times must be in sync. Enrollment can fail if there is a significant difference between the Lighthouse and the node. It is recommended that you use an NTP server to automatically manage the date and time. If you are using multiple instances, configure the time zone for the secondary instances before you add them as secondary instance. The only way to change the time zone after adding a secondary instance is to use the CLI.
MANUAL CONFIGURATION
To manually select the time zone: 1. In the Settings Pane, select > SYSTEM > Time Settings.
The TIME SETTING page displays with the TIMEZONE tab selected. 2. From the System Timezone drop-down, select the timezone for the Lighthouse instance. 3. Click Apply.
AUTOMATIC CONFIGURATION
To set time automatically:
24.12.1
Setting up Lighthouse
101
Lighthouse User Guide
Note: It is highly recommended that you use a NTP Server to automatically manage date and time.
1. In the Settings Pane, select > SYSTEM > Time Settings. The TIME SETTING page displays with the TIMEZONE tab selected.
2. Select the AUTOMATIC tab. 3. Under Network Time Protocol, select Enabled. 4. Click Add server. 5. In the NTP Server field, enter a working NTP Server address. 6. Click Apply.
SET A CUSTOM LOGIN MESSAGE
When you set a custom login message, the message is displayed before the user logs in: l On the Lighthouse login page. l In the CLI before the login prompts.
Note: To set a custom login message, you must have Full Access permission assigned on the Custom Login Message feature. For more information, see Operation Permissions Reference.
1. In the Settings Pane, select > SYSTEM > General Settings. The GENERAL SETTINGS page displays with the SESSION SETTINGS tab selected.
2. Select the CUSTOM LOGIN MESSAGE tab. 3. Select Enabled to turn on the Custom Login Message.
This is set to Disabled by default. When you set this field to Enabled, a warning is displayed to inform you that the message is displayed on the login page. 4. In the Message Content field:
24.12.1
Setting up Lighthouse
102
Lighthouse User Guide
a. Enter the message content. If Custom Login Message is Enabled, the Message Content field is required.
b. Use the Bold button to apply bold formatting as required. c. Use the Hyperlink button to insert a hyperlink. d. Click the Preview in Terminal button to preview the configured message.
The preview displays in a dialog, click Done to exit the preview. 5. Click Apply.
Note: If you Enable the Custom Login Message and do not enter a message, you are prompted to provide text or disable the message.
SET UP NETWORKING REQUIREMENTS
This section outlines the basic steps to setup networking requirements for Lighthouse including: l Lighthouse Session Settings l MTU of the Lighthouse VPN tunnel l Network connection l SNMP Manager Settings l SNMP Service l Cellular Health Settings l Lighthouse MIBs l Smart Management Fabric
EXAMINE OR MODIFY THE LIGHTHOUSE SESSION SETTINGS
To modify Web and CLI session settings:
24.12.1
Setting up Lighthouse
103
Lighthouse User Guide
1. In the Settings Pane, select > SYSTEM > General Settings. The GENERAL SETTINGS page displays with the SESSION SETTINGS tab selected.
2. Enter the Web Session Timeout. This value can be set from 1 to 1440 minutes.
3. Enter the CLI Session Timeout. This value can be set from 1 to 1440 minutes or set it to 0 to disable the timeout. Changes take effect the next time a user logs in via the CLI.
4. If required, select Enabled for Alternate API Port Status. This port is set to 8443. Enabling this API allows users who are using NAT for the Lighthouse to expose an external port publicly only for nodes that are attempting to enroll to the Lighthouse, and not for the other functionality available from the REST API. After this option is disabled, all endpoints should be accessible as per normal usage.
5. Click Apply.
EXAMINE OR CHANGE LIGHTHOUSE VPN NETWORK SETTINGS
The VPN network ranges for Lighthouse VPN (LHVPN) and Smart Management Fabric can be set up or modified. To setup the Lighthouse VPN: 1. In the Settings Pane, select > SERVICES > Lighthouse VPN. 2. Under VPN NETWORK RANGE:
a. Enter the Address Space: The range to be used for the VPN.
Note: The Address Space must be in the IPv4 Private Address Space, subnet must have enough space for the existing Enrolled Nodes to Lighthouse, cannot overlap with an existing subnet across lighthouse and the base address for the network range.
b. Enter the CIDR Subnet Mask: The Classless Inter-Domain Routing notation for the subnet mask for the VPN network.
24.12.1
Setting up Lighthouse
104
Lighthouse User Guide
c. Calculated Node Capacity: An auto-calculated field with the total number of usable nodes. d. Enter the Tunnel MTU: The MTU is the size, in bytes, of the largest packet supported by a
network layer protocol, including both headers and data. 3. Under SMART MANAGEMENT FABRIC NETWORK RANGE:
a. Enter the Address Space. b. Enter CIDR Subnet Mask. c. Calculated Node Capacity: An auto-calculated field with the total number of usable nodes. d. Smart Management Fabric MTU: an auto-calculated field, the Smart Management Fabric
MTU is based on a fixed offset off the LHVPN MTU.
NETWORK CONNECTIONS
When you boot Lighthouse, the physical interfaces and their connections are already available. This section describes the procedures if you need to configure additional connections.
IMPORTANT: If you have configured any additional interfaces using a method other than 'Add 2nd NIC Bash Shell Script', then you must migrate your configuration for the additional interfaces. Contact Support for migration information and assistance.
VIEW AVAILABLE NETWORK CONNECTIONS
To see the network connections available to Lighthouse: 1. In the Settings Pane, select > SYSTEM > Network Settings.
The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected. You can see a list of network interfaces made available when Lighthouse was booted.
24.12.1
Setting up Lighthouse
105
Lighthouse User Guide
Note: Additional interfaces are added to the VM that hosts Lighthouse. If you add additional interfaces, you must reboot Lighthouse to make the interface available to the Lighthouse instance for configuration.
2. Under NETWORK INTERFACES, click the drop-down button next to the interface for which you want to see available connections. The information expands and displays the available network connections for the selected interface.
EDIT A NETWORK INTERFACE
To edit a network interface:
Note: Editing the network settings may break connectivity.
1. In the Settings Pane, select > SYSTEM > Network Settings. The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected.
2. Click on the interface Name link within the grid. The UPDATE dialog displays.
3. Make the required changes.
Note: You can use the Reserved for Smart Management Fabric check box to reserve selected interfaces for use with Smart Management Fabric.
4. Click Update Interface.
Note: Do not change the Connection Type of default network interfaces. If a default interface is not required, edit the interface and select Disabled. If default-static and default-DHCP are changed to the same configuration method (that is, if both are set to Static assignment or both are set to DHCP), neither interface works.
24.12.1
Setting up Lighthouse
106
Lighthouse User Guide
ADD A NETWORK CONNECTION
1. In the Settings Pane, select > SYSTEM > Network Settings. The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected.
2. Under NETWORK INTERFACES, click the drop-down button next to the interface for which you want to add a connection. The information expands and displays the available network connections for the selected interface.
3. Click Add New Connection. The ADD CONNECTION dialog displays.
4. Select Enabled to enable the connection.
Note: You can set this to Disabled later if you want to turn the connection off without deleting it.
5. Enter a Name for the connection. 6. Enter a Description for the connection. 7. Select the address type from the following:
l IPv4 Static l IPv4 DHCP l IPv6 Static l IPv6 Automatic 8. If you selected IPv4 Static, or IPv6 Static, enter the following fields: l IPv4 Address or IPv6 Address l IPv4 Network Mask or IPv6 Prefix Length l Gateway
24.12.1
Setting up Lighthouse
107
Lighthouse User Guide
l Primary DNS Server l Secondary DNS Server 9. Click Add Connection.
The ADD CONNECTION dialog closes and the NETWORK SETTINGS page displays with the new connection listed under the expanded network interface. 10. At the bottom of the page, click Apply.
EDIT A NETWORK CONNECTION
1. In the Settings Pane, select > SYSTEM > Network Settings. The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected.
2. Under NETWORK INTERFACES, click the drop-down button next to the interface that has the connection you want to edit. The information expands and displays the available network connections for the selected interface.
3. Click the CONNECTION NAME of the connection you want to edit. The UPDATE [CONNECTION NAME] dialog displays.
4. Edit the fields as required.
Notes: You: l can edit the fields in the same way you would in Add a Network Connection. l cannot set the last known connection for a Lighthouse to Disabled.
5. Click Update Connection. The UPDATE [CONNECTION NAME] dialog closes and the NETWORK SETTINGS page displays.
6. At the bottom of the page, click Apply.
24.12.1
Setting up Lighthouse
108
Lighthouse User Guide
DELETE A NETWORK CONNECTION
1. In the Settings Pane, select > SYSTEM > Network Settings. The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected.
2. Under NETWORK INTERFACES, click the drop-down button next to the interface that has the connection you want to delete. The information expands and displays the available network connections for the selected interface.
3. Click the CONNECTION NAME of the connection you want to delete. The UPDATE [CONNECTION NAME] dialog displays.
4. Click Delete.
Note: You cannot delete the last known connection for a Lighthouse.
5. At the bottom of the page, click Apply.
CELLULAR HEALTH REPORTING
Administrative users can control the cellular health reporting settings under > SERVICES > Cell Health Reporting. When cell health checks are enabled, the network carrier, IMEI, IMSI, and ICCID of the downstream SIM being utilized are part of the information that is displayed in Lighthouse for managed nodes. If a managed node has the modem disabled/off, the appropriate status is shown in Lighthouse for the node.
ENABLE CELL HEALTH REPORTING
To enable Cell Health Reporting:
24.12.1
Setting up Lighthouse
109
Lighthouse User Guide
1. In the Settings Pane, select > SERVICES > Cell Health Reporting. The CELL HEALTH REPORTING page displays.
2. Select Enabled. The fields to configure cell health reporting display.
3. Set the Signal Quality Ranges to report. Click and drag the range handles to the range value corresponding to: Bad, Moderate, and Good.
4. Set the Frequency for Lighthouse to check the signal quality. 5. If you want to enable the cell connectivity test to get a complete cell health report, select Cell
Connectivity Test check box.
Note: This causes cell data consumption.
6. Click Apply.
LIGHTHOUSE MIBS
Lighthouse Management Information Bases (MIBs) can be found in /usr/share/snmp/mibs/. Lighthouse can be configured to expose managed node information such as node name, node model number, node port label, license status, etc. via SNMP. The MIBs turn the SNMP data into text that is more readable to human readers.
GENERIC INFORMATION ABOUT LIGHTHOUSE VERSION AND NODES COUNT
24.12.1
Setting up Lighthouse
110
AVAILABLE INFORMATION FOR AN ENROLLED OPENGEAR NODE ogLhNodesTable:
Lighthouse User Guide
AVAILABLE INFORMATION FOR AN ENROLLED THIRD-PARTY NODE
24.12.1
Setting up Lighthouse
111
AVAILABLE LICENSING INFORMATION
Lighthouse User Guide
AVAILABLE ENROLLED NODE CELLULAR HEALTH INFORMATION
ogLhNodeCellularHealth
OTHER SNMP COMMANDS To retrieve Lighthouse specific information use SNMP commands such as: l snmpwalk l snmpget EXAMPLES OF LIGHTHOUSE MIB QUERIES THAT USE SNMP Walk through the entire ogLighthouseMib using name:
snmpwalk -m ALL -v1 -c public 192.168.1.1 ogLighthouseMib snmpwalk -m ALL -M /usr/share/snmp/mibs -v1 -c public 192.168.1.1 ogLighthouseMib
Walk through the entire ogLighthouseMib using the OID directly:
snmpwalk -m ALL -M /usr/share/snmp/mibs -v1 -c public 192.168.1.1 1.3.6.1.4.1.25049.18.1
Get the total nodes enrolled in Lighthouse:
24.12.1
Setting up Lighthouse
112
Lighthouse User Guide
snmpget -m ALL -v1 -c public 192.168.1.1 ogLhNodesTotal.0 snmpwalk -m ALL -v1 -c public 192.168.1.1 ogLhNodesTotal
Get serial number with enrolled node having VPN address 192.168.128.2:
snmpwalk -m ALL -v1 -c public 192.168.1.1 ogLhNodeSerialNumber.192.168.128.2 snmpget -m ALL -v1 -c public 192.168.1.1 ogLhNodeSerialNumber.192.168.128.2
Get cellular health for all enrolled nodes:
snmpwalk -m ALL -c public -v 1 192.168.124.143 ogLhNodeCellularHealth OG-LIGHTHOUSE-MIB::ogLhNodeCellularHealth.192.168.128.2 = INTEGER: good(4) OG-LIGHTHOUSE-MIB::ogLhNodeCellularHealth.192.168.128.3 = INTEGER: good(4) OG-LIGHTHOUSE-MIB::ogLhNodeCellularHealth.192.168.128.4 = INTEGER: bad(2) OG-LIGHTHOUSE-MIB::ogLhNodeCellularHealth.192.168.128.5 = INTEGER: unknown(0) OG-LIGHTHOUSE-MIB::ogLhNodeCellularHealth.192.168.128.6 = INTEGER: bad(2)
SET UP MULTIPLE INSTANCES OF LIGHTHOUSE
This section discusses the licensing, setup, configuration, promoting and disconnecting of secondary instances, and upgrading of a multiple instance Lighthouse. The multiple instance functionality allows you to set up secondary or dependent instances of Lighthouse that automatically receive updates from a primary Lighthouse instance and maintains connections to all its remote nodes. Secondary instances are read-only. They may be used to view Lighthouse information specific to that instance using ogconfig-cli, and to connect via pmshell. Configuration changes must be performed on the primary instance, which then updates the information displayed on the secondary instance.
24.12.1
Setting up Lighthouse
113
Lighthouse User Guide
SET UP MULTI INSTANCE
Lighthouse supports up to 10 secondary instances for each primary Lighthouse instance. A Lighthouse with multiple instance support requires multiple separate subnets for Lighthouse VPN connections between: l each instance and its nodes. l the primary and secondary instance Lighthouses.
Note: Each subnet must not overlap any subnet in use by another Lighthouse instance.
Before you attempt to set up a multiple instance:
24.12.1
Setting up Lighthouse
114
Lighthouse User Guide
l Start with what will be the primary instance and one or more Lighthouse instances to act as secondary. All instances must have the same version of Lighthouse.
l Configure the networking information for each instance (hostname, external endpoints, network addresses, REST API port).
l Configure the time settings of each instance. l Ensure you have a subscription active on your primary Lighthouse.
STEPS TO SETUP MULTI INSTANCE
To set up multi Instance on the primary Lighthouse: 1. Ensure that you are on the primary Lighthouse. 2. In the Settings Pane, select > MULTI INSTANCE > Secondary Lighthouses.
The SECONDARY LIGHTHOUSES page displays. 3. Click Add Secondary Lighthouse.
The ADD SECONDARY LIGHTHOUSE page displays. 4. Enter the Description for the Lighthouse. 5. Enter the Network Address.
This field accepts either the current IP Address or the hostname. 6. Enter the Network Port for HTTPS connections. 7. Enter the Username. 8. Enter the Password. 9. Under VPN NETWORK RANGE, provide the following details:
l Address Space: enter a valid, unused network subnet to use as the secondary lhvpn address range.
l CIDR Subnet Mask
24.12.1
Setting up Lighthouse
115
Lighthouse User Guide
Notes: l Lighthouse displays the Calculated Node Capacity based on the values entered
reflecting the addressable nodes based on the network. l The secondary Lighthouse instance must be able to reach the primary instance on UDP
Port 1195.
10. Under SMART MANAGEMENT FABRIC RANGE, provide the following SMF range details if the secondary lighthouse is to be discoverable on the Smart Management Fabric: l Address Space l CIDR Subnet Mask
Note: Lighthouse displays the Calculated Node Capacity based on the values entered reflecting the addressable nodes based on the network.
11. Click Apply.
ENABLE ALTERNATE REST API PORTS
If you are planning to use the alternate REST API ports, you must make sure this option is enabled on both the primary and secondary Lighthouse servers, prior to enrollment of secondaries. Lighthouse will prevent the enrollment of a secondary Lighthouse instance if there is a mismatch in these settings. If this occurs, the message "Lighthouse is using Alternate API port" will be displayed on the secondary Lighthouse page. To fix the issue, either: l Enable the Alternate REST API port on both Lighthouse servers, or l Disable the Alternate REST API port on both Lighthouse servers, then delete the failed
Lighthouse Enrollment and try again.
24.12.1
Setting up Lighthouse
116
Lighthouse User Guide
CONFIGURE THE ALTERNATE REST API
The Alternate REST API Port is configured as follows: 1. In the Settings Pane, select > SYSTEM > General Settings.
The GENERAL SETTINGS page displays with the SESSION SETTINGS tab selected. The SESSION SETTINGS page displays. 2. For Alternate API Port Status, select Enabled. 3. Click Apply.
Note: Additional enrollment-only REST API port is 8443.
CONFIGURE SUBNETS FOR A MULTIPLE INSTANCE LIGHTHOUSE
A Lighthouse with multiple instance support requires multiple separate subnets for Lighthouse VPN connections between: l each instance and its nodes. l the primary and secondary Lighthouses. In a single Lighthouse, the defined subnet is used by Lighthouse to talk to all configured nodes. When you add a second Lighthouse, you must define a new subnet range that will talk to all of the same nodes.
Note: Each subnet must not overlap any subnet in use by another Lighthouse instance. See Subnet Planning.
24.12.1
Setting up Lighthouse
117
Lighthouse User Guide
SUBNET PLANNING
If you have multiple subnets next to each other, then they cannot overlap any other subnet in use by another Lighthouse. This means subnets that start next to each other cannot be extended after configuration, so it is important to consider how your subnet may grow over time. Consider the following: l The number of nodes you might possibly use; each subnet must be large enough to
accommodate all possible nodes that you will ever use with that Lighthouse instance. For example: l If you want to use 100 nodes, then you require a subnet with a minimum of 101 address
spaces to accommodate the Lighthouse instance and all nodes. l If you configure a subnet for only the address spaces required, and you configure another
subnet next to it, then you cannot extend the original subnet as it would overlap the second subnet. l The number of nodes available on your subscription. This does not dictate the size of your subnet, but you may require an upgrade to use your whole subnet.
CONFIGURE THE SUBNETS BETWEEN THE PRIMARY LIGHTHOUSE AND ITS NODES
1. Ensure that you are on the primary Lighthouse. 2. In the Settings Pane, select > MULTI INSTANCE > Multi Instance VPN.
The MULTI INSTANCE VPN page displays. 3. Enter the Address Space.
The address you enter here is effectively the network address. A specific type of address where all host parts of the address are 0, or one value less than the first useable IP address within a range.
24.12.1
Setting up Lighthouse
118
Lighthouse User Guide
4. Enter the CIDR Subnet Mask. The value selected here defines what part(s) of the Address Space is assigned to the network and what parts are assigned to the host. This determines how many addresses are available and what the range is.
Note: The Calculated Address Capacity is a calculated field and displays the addressable nodes based on the network.
CONFIGURE THE SUBNET BETWEEN EACH SECONDARY LIGHTHOUSE AND ITS NODES
1. Ensure that you are on the primary Lighthouse. 2. In the Settings Pane, select > MULTI INSTANCE > Secondary Lighthouses.
The SECONDARY LIGHTHOUSES page displays. 3. Click on the Instance Description for the secondary Lighthouse you want to edit.
The EDIT SECONDARY LIGHTHOUSE page displays. 4. Under VPN NETWORK RANGE:
a. Update the Address Space. The address you enter here is effectively the network address. A specific type of address where all host parts of the address are 0, or one value less than the first useable IP address within a range.
b. Update the CIDR Subnet Mask. The value selected here defines what part(s) of the Address Space is assigned to the network and what parts are assigned to the host. This determines how many addresses are available and what the range is.
Note: The Calculated Node capacity is a calculated field and displays the addressable nodes based on the network.
24.12.1
Setting up Lighthouse
119
Lighthouse User Guide
5. If you want the secondary lighthouse to be discoverable on the Smart Management Fabric, under SMART MANAGEMENT FABRIC RANGE, update the Address Space.
Notes: l The CIDR Subnet Mask is a calculated field. l The Calculated Node Capacity is a calculated field and displays the addressable
nodes based on the network.
CONFIGURE SECONDARY INSTANCE INFORMATION PRIOR TO ENROLLMENT
Other information that is specific to the secondary Lighthouse should be configured before enrolling but can be modified on the primary Lighthouse via ogconfig-cli. Instance specific information includes: l Hostname l Time zone l Networking l External interfaces
Note: The instance specific information is available on both the primary and secondary Lighthouses but it is read-only on the secondary Lighthouse.
Configurations of all Lighthouse instances are stored in lighthouse_configurations. These can be viewed via ogconfig-cli. The primary instance has a value of Primary for its role, and secondary instances have the value Secondary. The following is an example of the ogconfig-cli session:
24.12.1
Setting up Lighthouse
120
Lighthouse User Guide
root@lighthouse:~# ogconfig-cli ogcfg> print lighthouse_configurations[0].role lighthouse_configurations[0].role (string): 'Primary' ogcfg> print lighthouse_configurations[1].role lighthouse_configurations[0].role (string): 'Secondary'
Alternatively, the command /usr/bin/is_secondary outputs n for a primary Lighthouse or y for a secondary Lighthouse. To update the hostname of the secondary Lighthouse, run the following commands on the primary Lighthouse:
ogconfig-cli set lighthouse_configurations[1].hostname new_name push
UNENROLL A SECONDARY INSTANCE
To unenroll a secondary Lighthouse instance from the primary Lighthouse: 1. Ensure that you are on the primary Lighthouse. 2. In the Settings Pane, select > MULTI INSTANCE > Secondary Lighthouses.
The SECONDARY LIGHTHOUSES page displays. 3. Click on the Instance Description for the secondary Lighthouse you want to unenroll.
The EDIT SECONDARY LIGHTHOUSE page displays. 4. Click Unenroll Instance on the top-right of the page.
A confirmation message displays. 5. Click Confirm.
24.12.1
Setting up Lighthouse
121
Lighthouse User Guide
PROMOTE A SECONDARY INSTANCE
When a primary Lighthouse is no longer reachable, a secondary Lighthouse instance can be promoted to primary. The new primary can then be used to set up a secondary Lighthouse if required.
Caution: This should only be performed if the primary Lighthouse has no chance of returning, the procedure is not reversible and will break all node connections with the previous primary instance. The previous primary instance must be factory reset before it can be used again.
To promote a secondary instance to primary, login as root or run with sudo privileges on the secondary instance via console or ssh and run:
>sudo promote-secondary-lighthouse
Remove all dead connections from node side using the node's web UI. The Promotion tool deletes connection between primary and dependent instance but does not touch node connections. The new primary can then be used to enroll a secondary Lighthouse if required.
Note: If the previous primary becomes accessible again, it will not be able to connect to its enrolled nodes or the previous secondary Lighthouses.
l All scheduled firmware upgrades are cancelled in the event of a secondary Lighthouse promotion, and must be rescheduled.
l Firmware files are not replicated among the multiple instance cluster and must be re-uploaded to the new primary after promotion.
24.12.1
Setting up Lighthouse
122
Lighthouse User Guide
ENABLE ALERTING AND MONITORING
Administrative users can configure the Simple Network Management Protocol (SNMP) Manager settings and multiple external servers to export the syslog to via TCP or UDP. The SNMP Manager allows SNMP TRAP/INFORM messages to be sent from Lighthouse to a configured server any time a node connection status is changed. Lighthouse supports both v1/v2 and v3 SNMP versions, which can be running at the same time. The SNMP service is not enabled by default. The SNMP service starts after it has been configured correctly. If the user does not provide an Engine ID, an auto-generated ID will be used. Lighthouse Health statistics (load/uptime/memory usage, etc.) can be retrieved.
SNMP MANAGER SETTINGS
To enable SNMP Manager: 1. In the Settings Pane, select > SERVICES > Alerting and Monitoring.
The ALERTING AND MONITORING page displays with the SNMP MANAGER tab selected. 2. Select Enabled to enable the SNMP Manager. 3. Select one of the following to set the Manager Protocol: UDP, UDP over IPv6, TCP, or TCP
over IPv6. 4. Enter the Manager Address to receive SNMP messages. 5. Enter the Manager Port: the TCP/UDP port number to send SNMP messages to. 6. Select one of the following for the the SNMP protocol Version: v1, v2c, or v3.
Additional fields display depending on the version selected. 7. Complete the following actions depending on the selected SNMP protocol Version:
l If you selected v1, enter the SNMP Community to use for messages. l If you selected v2c:
24.12.1
Setting up Lighthouse
123
Lighthouse User Guide
a. Set the SNMP Message Type to TRAP or INFORM. b. Enter the SNMP Community to use for messages. l If you selected v3: a. Set the SNMP Message Type to TRAP or INFORM. b. Optional: If you select TRAP for the SNMP Message Type, specify an Engine ID for
sending an SNMP TRAP message.
Note: If the Engine ID is left blank, the auto-generated Engine ID from the SNMP Service is used. An Engine ID is not required for an SNMP INFORM message.
c. Enter the SNMP v3 Engine ID and required Configure SNMP Manager Settings. d. Enter the Username to send the messages as. e. Set the Authentication Protocol to MD5 or SHA. f. Enter the Authentication Password for the SNMP user. g. Set the Privacy Protocol to DES or AES. h. Enter a Privacy Password. 8. Under SNMP Message Settings, set the events to trigger a TRAP/INFORM notification by checking a combination of: l Node Connection Status: send an SNMP notification when a node connects or disconnects. l Secondary Replication Status: send an SNMP notification when problems occurs with database replication on secondary Lighthouse. l Node Cellular Health Status: to use Cellular Health Status change traps. 9. Click Apply. For information on the structure of notifications for Opengear nodes, refer to OG-LIGHTHOUSEMIB.mib.
24.12.1
Setting up Lighthouse
124
Lighthouse User Guide
SNMP SERVICE SETTINGS
To enable the SNMP Service: 1. In the Settings Pane, select > SERVICES > Alerting and Monitoring.
The ALERTING AND MONITORING page displays with the SNMP MANAGER tab selected. 2. Select the SNMP SERVICE tab. 3. Set the TCP/IP Protocol to UDP or TCP. 4. Enter the Location. 5. Enter the Contact. 6. Set the SNMP version the service supports by checking a combination of the following:
l v1/v2c l v3 7. If you checked v1/v2c, under SNMP V1 & V2C: a. Enter the Read-Only Community. b. Enter the Read-Write Community. 8. If you checked v3, under SNMP V3: a. Enter the Engine ID to override the automatically generated SNMPv3 Engine.
Note: If not specified, an Engine ID is automatically generated using Network Interface details.
b. Set the Security Level to No Security, Authentication, or Authentication and Encryption.
Tip: The SNMP v3 security level Authentication and Encryption is recommended.
c. Complete the following actions depending on the selected Security Level:
24.12.1
Setting up Lighthouse
125
Lighthouse User Guide
l If you selected No Security, enter the Read Only Username. l If you selected Authentication:
i. Enter the Read Only Username. ii. Set the Authentication Protocol to MD5 or SHA. iii. Enter and confirm the Authentication Password. l If you selected Authentication and Encryption: i. Enter the Read Only Username. ii. Set the Authentication Protocol to MD5 or SHA. iii. Enter and confirm the Authentication Password. iv. Set the Privacy Protocol to DES or AES. v. Enter and confirm the Privacy Password. 9. Click Apply.
SYSLOG SERVER MANAGEMENT
VIEW THE CONFIGURED SYSLOG SERVERS
1. In the Settings Pane, select > SERVICES > Alerting and Monitoring. The ALERTING AND MONITORING page displays.
2. Select the SYSLOG tab.
ADD A NEW SYSLOG SERVER
1. In the Settings Pane, select > SERVICES > Alerting and Monitoring. The ALERTING AND MONITORING page displays.
2. Select the SYSLOG tab. 3. Click the New Syslog Server button.
The CREATE NEW SYSLOG SERVER dialog displays.
24.12.1
Setting up Lighthouse
126
Lighthouse User Guide
4. Enter the Server Address. 5. Set the Protocol to UDP or TCP. 6. Enter the Port.
Note: For UDP the default port is 514. For TCP the default port is 601.
7. Click Create Syslog server.
MODIFY A SYSLOG SERVER
1. In the Settings Pane, select > SERVICES > Alerting and Monitoring. The ALERTING AND MONITORING page displays.
2. Select the SYSLOG tab. 3. Locate and click the SERVER ADDRESS of the server you want to modify.
The UPDATE dialog displays. 4. Modify the details as required. 5. Click Update Syslog server.
DELETE A SYSLOG SERVER
1. In the Settings Pane, select > SERVICES > Alerting and Monitoring. The ALERTING AND MONITORING page displays.
2. Select the SYSLOG tab. 3. Locate and click the SERVER ADDRESS of the server you want to delete. 4. Click Delete.
The DELETE SYSLOG SERVER confirmation dialog displays. 5. Click Delete.
24.12.1
Setting up Lighthouse
127
Lighthouse User Guide
SMART MANAGEMENT FABRIC
Smart Management Fabric represents an advanced functionality designed to offer heightened flexibility and accessibility to network and IT professionals throughout the network fabric. It empowers them by facilitating effective orchestration and management through the management network. As Smart Management Fabric expands its reachability through the utilization of OSPF and the integration of Opengear nodes and Lighthouse for establishing new paths, it is crucial to acknowledge the potential risk of overexposing the network, which could lead to bypassing Layer 2 or Layer 3 access control measures. While the communication between the Lighthouse and OpenGear nodes, such as OM, is safeguarded through a VPN connection, and the OSPF configuration is carefully restricted and secured, there exists a potential risk when devices like routers and switches under customer autonomy are configured within the OSPF process without adequate diligence. To address and mitigate these risks, the following strategies are recommended: l Conduct a meticulous examination of networks participating in OSPF advertisement, with a
suggestion to implement passive interfaces. l Execute comprehensive testing and verification to ensure that no routing occurs among
networks not involved in Smart Management Fabric. l Verify the activation of OSPF authentication to augment network security. Smart Management Fabric uses dynamic link state routing to allow IP connectivity to IT resources on IPv4 networks connected to compatible Opengear products: l via SSH, https (GUI), SPs/BMCs (iLO, iDRAC, etc.). l via commonly used automation tools such as RDP, Ansible, Python, vCenter.
24.12.1
Setting up Lighthouse
128
Lighthouse User Guide
To implement Smart Management Fabric an appropriate subscription type is required, as well as a supported (23.10.4 firmware and up) Opengear console server such as Operations Manager.
Note: Smart Management Fabric is advanced functionality that utilizes dynamic routing protocols. It is crucial to acknowledge the potential risk of overexposing your network.
ENABLE SMART MANAGEMENT FABRIC
After deploying the Lighthouse, to set up Smart Management Fabric to create an internal network area between Lighthouse and the console servers: 1. Log in to the Lighthouse web UI as a Lighthouse Administrator or the root user. 2. In the Settings Pane, select > SERVICES > Smart Management Fabric.
The SMART MANAGEMENT FABRIC page displays.
24.12.1
Setting up Lighthouse
129
Lighthouse User Guide
3. Select Enabled. 4. Enter the Internal Area ID for the backbone area for the internal network.
The area is a logical collection of internal networks, routers, and links with the same area identification. 5. Click Apply. To ensure the Smart Management Fabric stays up to date, these are the following scenarios that would require an additional push of configuration after the initial setup: l Any changes made to Smart Management Fabric VPN subnets for the Primary or Multi Instance Lighthouses. l A new Multi-Instance Lighthouse is added that is required to be part of the Smart Management Fabric network. l Any changes to the Lighthouse VPN for the Primary or Multi Instance Lighthouse that may include: l Any subnet changes. l Any changes to MTU for a specific node.
SMART MANAGEMENT FABRIC - A SAMPLE DEPLOYMENT
In this sample, the devices on two separate networks, can connect via Lighthouse, when Smart Management Fabric is enabled.
24.12.1
Setting up Lighthouse
130
Lighthouse User Guide
USE SMART MANAGEMENT FABRIC
To set up Lighthouse as the router for a deployment: 1. Configure the Address space. 2. Enable Smart Management Fabric and provide the internal area id. 3. Configure the Smart Management Fabric templates for the nodes.
SMART MANAGEMENT FABRIC AND NETOPS INTERACTIONS
The Smart Management Fabric feature can be used with the following NetOps features with some caveats related to the following:
24.12.1
Setting up Lighthouse
131
Lighthouse User Guide
l IP Access. l Secure Provisioning.
Note: Automation Gateway is not compatible with Smart Management Fabric.
IP ACCESS
The IP Access Subnet Address is not unique and is present on every IP Access enabled node. This will cause routing issues for the Smart Management Fabric if there are multiple IP Access enabled nodes.
SECURE PROVISIONING
The default Smart Management Fabric subnet range conflicts with the Secure Provisioning subnet range, however either change the Smart Management Fabric subnet range before enabling secure provisioning, or change the Secure Provisioning Subnet range before it is deployed.
SECURE PROVISIONING CONFIGURATION
The Secure Provisioning Subnet is not unique by default so if the default is used on more than one Smart Management Fabric node then it will effectively not be able to route to those Secure Provisioning connected devices. Customize the Secure Provisioning Subnet by setting a static IPv4 address on the Node's LAN interface before deploying Secure Provisioning. Secure Provisioning will then inherit the subnet range from a static IPv4 address on the node's LAN interface address.
RESERVE AN INTERFACE FOR SMART MANAGEMENT FABRIC (SMF)
Lighthouse can support multiple network interface connections and you can reserve those interfaces to allocate them for use in Smart Management Fabric (SMF). This reservation implies that the reserved interface is:
24.12.1
Setting up Lighthouse
132
Lighthouse User Guide
l safe for use in Lighthouse OSPF interface configuration. For more information, see Lighthouse OSPF Settings.
l not available for node or Lighthouse enrollment. When an interface is reserved for SMF, any connections associated with that interface cannot have subnets that fall in the range of the current external endpoint address list. 1. In the Settings Pane, select > SYSTEM > Network Settings.
The NETWORK SETTINGS page displays with the PRIMARY INSTANCE tab selected by default. 2. Under NETWORK INTERFACES, select the Reserved for Smart Management Fabric check box for the interface you want to reserve. 3. At the bottom of the page, click Apply.
LIGHTHOUSE OSPF SETTINGS
You can configure OSPF settings for networks to which Lighthouse is connected where the interface is reserved for Smart Management Fabric.
VIEW OSPF INTERFACES
1. In the Settings Pane, select > SERVICES > Smart Management Fabric. The SMART MANAGEMENT FABRIC page displays with the SMF SETTINGS tab selected.
2. Select the LIGHTHOUSE OSPF SETTINGS tab. A list of current Lighthouse instances displays.
3. Click the INSTANCE DESCRIPTION of the Lighthouse instance for which you want to view interfaces. The CONFIGURE OSPF LIGHTHOUSE page displays with a list of interfaces.
24.12.1
Setting up Lighthouse
133
Lighthouse User Guide
ADD AN OSPF INTERFACE
1. In the Settings Pane, select > SERVICES > Smart Management Fabric. The SMART MANAGEMENT FABRIC page displays with the SMF SETTINGS tab selected.
2. Select the LIGHTHOUSE OSPF SETTINGS tab. A list of current Lighthouse instances displays.
3. Click the INSTANCE DESCRIPTION of the Lighthouse instance to which you want to add an interface. The CONFIGURE OSPF LIGHTHOUSE page displays with a list of existing interfaces that are configured for OSPF.
4. Click Add OSPF Interface. The CONFIGURE OSPF INTERFACE FOR LIGHTHOUSE dialog displays.
5. From the Interface drop-down, select an interface. Only interfaces that are reserved for SMF display in this list. To reserve an interface, see Reserve an Interface for Smart Management Fabric (SMF).
6. Select the following check boxes as required: l Masquerade Interface: to show that traffic from this interface appears to come directly from the supported node to other devices in the subnet. l Passive Interface: if routes are not to be propagated to the network it is on.
7. Enter the OSPF Area. 8. Enter the Cost used in OSPF route calculations which indicates the overhead required to send
packets across the specified interface. 9. Select one of the following Authentication Methods:
l MD5 l Clear Text l No Authentication
24.12.1
Setting up Lighthouse
134
Lighthouse User Guide
10. Click Update Interface. The CONFIGURE OSPF INTERFACE FOR LIGHTHOUSE dialog closes and the CONFIGURE OSPF LIGHTHOUSE page displays.
11. At the bottom of the grid, click Apply.
EDIT AN OSPF INTERFACE
1. In the Settings Pane, select > SERVICES > Smart Management Fabric. The SMART MANAGEMENT FABRIC page displays with the SMF SETTINGS tab selected.
2. Select the LIGHTHOUSE OSPF SETTINGS tab. A list of current Lighthouse instances displays.
3. Click the INSTANCE DESCRIPTION of the Lighthouse instance with the interface you want to edit. The CONFIGURE OSPF LIGHTHOUSE page displays with a list of existing interfaces.
4. Click the INTERFACE that you want to edit. The CONFIGURE OSPF INTERFACE FOR LIGHTHOUSE dialog displays.
5. Edit the fields as required.
Note: You can edit the fields the same way you would in Add an OSPF Interface.
6. Click Update Interface. The CONFIGURE OSPF INTERFACE FOR LIGHTHOUSE dialog closes and the CONFIGURE OSPF LIGHTHOUSE page displays.
7. At the bottom of the grid, click Apply.
24.12.1
Setting up Lighthouse
135
Lighthouse User Guide
DELETE AN OSPF INTERFACE
1. In the Settings Pane, select > SERVICES > Smart Management Fabric. The SMART MANAGEMENT FABRIC page displays with the SMF SETTINGS tab selected.
2. Select the LIGHTHOUSE OSPF SETTINGS tab. A list of current Lighthouse instances displays.
3. Click the INSTANCE DESCRIPTION of the Lighthouse instance with the interface you want to edit. The CONFIGURE OSPF LIGHTHOUSE page displays with a list of existing interfaces.
4. Click the INTERFACE that you want to edit. The CONFIGURE OSPF INTERFACE FOR LIGHTHOUSE dialog displays.
5. Click Delete. The CONFIGURE OSPF INTERFACE FOR LIGHTHOUSE dialog closes and the CONFIGURE OSPF LIGHTHOUSE page displays.
6. At the bottom of the grid, click Apply.
24.12.1
Setting up Lighthouse
136
Lighthouse User Guide
MANAGING LIGHTHOUSE
This section describes how to manage Lighthouse to monitor and manage your network.
MANAGE SUBSCRIPTIONS
Lighthouse has a flexible, simplified subscription model that allows you to add extended functionality if required. If have a subscription with extra functionality, you can apply any extra functionality to the selected nodes only, giving you the flexibility to use different subscriptions for different nodes.
Note: Contact sales@opengear.com with a request for the type of subscription, including the number of nodes to which you want to apply the subscription. You will receive an encrypted .zip file.
SUBSCRIPTION TYPES
The following subscriptions are currently available to all Lighthouse customers:
Subscription Type
Description
Lighthouse Core (LC)
Provides base functionality to enroll, monitor, and manage nodes. This subscription does not contain any NetOps modules. When you apply this subscription, any previously installed NetOps modules are automatically deactivated.
24.12.1
Managing Lighthouse
137
Subscription Type
Lighthouse Enhance (LE)
Lighthouse User Guide
Description
Provides base functionality to enroll, monitor, and manage nodes plus the advanced feature sets Smart Management Fabric and Connected Resource Gateway. This subscription does not contain any NetOps modules. When you apply this subscription, any previously installed NetOps modules are automatically deactivated.
Note: From version 24.12 onwards, the Lighthouse evaluation license has the same features as the Lighthouse Enhance subscription.
Note: With the LC and LE subscriptions, NetOps modules will no longer be available. However, if you have the LE subscription, you can use the Smart Management Fabric and Connected Resource Gateway features for similar functionality.
The following subscriptions are currently available only to existing Lighthouse customers who already have these subscriptions:
Note: These subscriptions will be replaced by Lighthouse Core (LC) and Lighthouse Enhance (LE). If you are an existing customer, you can renew the subscription for 12 months, and then you must update your subscription. If you are a new Lighthouse customer, these subscriptions are not available.
24.12.1
Managing Lighthouse
138
Lighthouse User Guide
Subscription Type
Description
Enterprise Edition (EE)
Provides base functionality to enroll, monitor, and manage nodes plus the NetOps module IP Access.
Enterprise Automation Edition (AE)
Provides base functionality to enroll, monitor, and manage nodes plus the NetOps modules IP Access, Automation Gateway, and Secure Provisioning and the advanced feature sets Smart Management Fabric and Connected Resource Gateway.
If you install a Lighthouse Enhance (LE) or Lighthouse Core (LC) subscription on a Lighthouse with an existing Automation Edition (AE) or Enterprise Edition (EE) subscription, then: l the LE subscription replaces the AE subscription and the LC subscription replaces the EE
subscription. l you cannot reapply an AE or EE subscription after the LC or LE subscription is applied. l NetOps modules are automatically deactivated. It is recommended to perform a clean up of
NetOps BEFORE you apply an LC or LE subscription. See Disable NetOps modules via template.
VIEW SUBSCRIPTIONS
1. In the Settings Pane, select > SYSTEM > Subscriptions. The SUBSCRIPTIONS page displays with the SUBSCRIPTIONS tab selected. This tab displays information on your subscriptions including the type of subscriptions, number of assigned out of the total nodes available, subscription status, and the number of days before expiry.
Note: In the donut, green represents the number of nodes assigned to the subscription, and gray represents the number of assignments still available.
24.12.1
Managing Lighthouse
139
Lighthouse User Guide
2. To view your subscription assignments, select the SUBSCRIPTION ASSIGNMENT tab. This tab displays a grid of nodes with the respective subscription assigned.
Note: Node Filter and Search controls are available.
ADD A NEW SUBSCRIPTION TO LIGHTHOUSE
1. In the Settings Pane, select > SYSTEM > Subscriptions. The SUBSCRIPTIONS page displays with the SUBSCRIPTIONS tab selected.
2. Click Add Subscription for the applicable subscription type. The NEW SUBSCRIPTION dialog displays.
3. Click Select file to navigate to and select the required zip file.
Note: You can also drag and drop the zip file into the NEW SUBSCRIPTION dialog.
4. Click Apply.
ASSIGN SUBSCRIPTIONS TO NODES
Users can reassign nodes to different subscriptions to optimize features on their network. For example, if the user: l Previously had two license tiers, but only paid to renew one license tier. l Purchased a subscription with additional features for the first time, and wants the extra
functionality on some of their nodes. l Wants to swap which nodes have access to extra functionality available on a subscription.
Note: When you view subscriptions, the colors of the donut represent the number of nodes assigned to the subscription or still available.
24.12.1
Managing Lighthouse
140
Lighthouse User Guide
ASSIGN A SINGLE NODE TO A SUBSCRIPTION
To assign a single node to a subscription: 1. In the Settings Pane, select > SYSTEM > Subscriptions.
The SUBSCRIPTIONS page displays with the SUBSCRIPTIONS tab selected. 2. Select the SUBSCRIPTION ASSIGNMENT tab. 3. To assign a subscription to a node click the Assign subscription to node button in the
right-hand column for the required node. The ASSIGN SUBSCRIPTIONS dialog displays showing details of the node in the left panel and subscription options in the right panel. 4. Select from the available subscription options presented in the right panel. 5. Click Confirm Assignment.
ASSIGN MULTIPLE NODES TO A SUBSCRIPTION
To assign multiple nodes to a subscription: 1. In the Settings Pane, select > SYSTEM > Subscriptions.
The SUBSCRIPTIONS page displays with the SUBSCRIPTIONS tab selected. 2. Select the SUBSCRIPTION ASSIGNMENT tab. 3. Select the node(s) to add to a subscription by selecting the checkbox in the left column.
The Assign Subscriptions button is displayed above the table. 4. Click Assign Subscriptions.
The ASSIGN SUBSCRIPTIONS dialog displays showing details of the node in the left panel and subscription options in the right panel. 5. Select from the available subscription options presented in the right panel. 6. Click Confirm Assignment.
24.12.1
Managing Lighthouse
141
Lighthouse User Guide
Note: If a node that has Smart Management Fabric configured is reassigned to a subscription without Smart Management Fabric, the disable Smart Management Fabric template is automatically pushed to that node and it is no longer a part of the Smart Management Fabric network.
Tip: Another way to remove a node from a subscription is to unenroll the node. The subscription then becomes available to be assigned to another node.
UPDATE A SUBSCRIPTION TO LIGHTHOUSE
If you update a subscription, the replacement is up to the matching subscription tier, and if a lower tier is applied, Lighthouse determines which nodes are applied to the subscription. If you install a Lighthouse Enhance (LE) or Lighthouse Core (LC) subscription on a Lighthouse with an existing Automation Edition (AE) or Enterprise Edition (EE) subscription, then: l the LE subscription replaces the AE subscription and the LC subscription replaces the EE
subscription. l NetOps modules are automatically deactivated. It is recommended to perform a clean up of
NetOps BEFORE you upgrade to a LE or LC subscription. See Disable NetOps modules via template. To upgrade a subscription: 1. In the Settings Pane, select > SYSTEM > Subscriptions. The SUBSCRIPTIONS page displays with the SUBSCRIPTIONS tab selected. 2. Click Update Subscription for the applicable subscription type. The NEW SUBSCRIPTION dialog displays. 3. Click select file to navigate to and select the required zip file.
Note: You can also drag and drop the zip file into the NEW SUBSCRIPTION dialog.
24.12.1
Managing Lighthouse
142
Lighthouse User Guide
4. Click Apply. If the subscription update replaces an Automation Edition (AE) subscription with a Lighthouse Enhance (LE) subscription or replaces an Enterprise Edition (EE) subscription with a Lighthouse Core (LC) subscription, then: l any nodes that were associated with the AE or EE subscription are automatically associated with the LE or LC subscription as appropriate. l any enrollment bundles that were using an AE or EE subscription are automatically associated with the LE or LC subscription as appropriate. l a warning is displayed to confirm that: l NetOps modules are automatically deactivated. l you cannot reapply an AE or EE subscription after the LE or LC subscription is applied. l a clean up of NetOps is recommended, see Disable NetOps Modules via Template.
UPGRADE LIGHTHOUSE
Lighthouse can be upgraded using a .lh_upg image file. Note the following conditions: l AWS requires .aws.lh_upg and Microsoft Azure requires .azure.lh_upg. All other
platforms use the standard .lh_upg file. l Incremental upgrades to Lighthouse using lh_upg files are only supported from 20.Q3.x and
not earlier releases.
Note: Upgrades do not overwrite existing configurations or user files, however it is recommended that you perform a Configuration Backup before you upgrade a Lighthouse.
After the upgrade is complete, the Lighthouse instance reboots. It is unavailable during the reboot process.
ABOUT THE UPGRADE PROCESS
Lighthouse performs the following high-level steps to upgrade to the new version:
24.12.1
Managing Lighthouse
143
Lighthouse User Guide
1. Validates the upgrade image, and takes a backup of the current root file system and snapshot of data volume.
2. Reboots into the new root file system (from the upgrade image). 3. Performs data migrations and system re-configurations. 4. Commits the changes on success, or reverts on failure. 5. For Multiple Instance only, after a successful Primary upgrade: After a 10 minute delay,
secondary instances are automatically upgraded in sequence. Lighthouse uses LVM snapshots to manage storage during upgrade and data migration. If a failure occurs, the snapshot is used to revert the system to its previous state. In regard to software versions, Lighthouse must be upgraded in succession. For example, to upgrade to a version that is several releases newer than your current release, you must install all the major releases in between to install the newest one.
PREPARE TO UPGRADE LIGHTHOUSE
While upgrading Lighthouse is a simple process, the following tasks are best practices to ensure a successful upgrade: l Read the release notes, in particular any known issues or special requirements for the new
version l Provide a sufficiently large maintenance window to start and complete the upgrade. Larger
networks and more complex configurations will take more time. You can run q-stat to check the job queue status. l Download the correct upgrade image. l The current release can be found here: Opengear FTP l Archived releases are available here: Archives Opengear FTP l Verify the image integrity by checking against SHASUMS. For example, on Linux:
24.12.1
Managing Lighthouse
144
Lighthouse User Guide
$ sha1sum lighthouse-24.12.1.lh_upg 0f52c30a212566030a1742b6e3d5bf9316d89abd lighthouse-24.12.1.lh_upg
l Before starting the upgrade, generate a Technical Support Report. This can assist Opengear support with diagnosing upgrade issues.
l Use the df command to display disk usage by filesystem:
root@lighthouse:~# df /mnt/data/
l Ensure that you have enough disk space in /mnt/data. If you have less than 20% disk space available, clean up unnecessary files, or add disk space. If disk space is added to the primary instance, add additional space all secondary instances also.
l Take a Configuration Backup on the Primary Lighthouse. This can be used to restore the system in the event of failure during upgrade.
l Do not make any configuration changes during the upgrade process (includes secondary upgrades).
l Consider taking a Virtual Machine backup. If the Lighthouse storage has been increased (by adding additional physical volumes to LVM) then these must be included in the backup, and all storage volumes must be in sync.
l You can also consider running some technical checks before starting the upgrade to check job queues, memory, temporary filesystem (tmpfs), database integrity, and multiple instance status.
PERFORM AN UPGRADE OF LIGHTHOUSE
UPGRADE A PRIMARY LIGHTHOUSE
To upgrade a primary Lighthouse:
24.12.1
Managing Lighthouse
145
Lighthouse User Guide
1. In the Settings Pane, select > SYSTEM > System Upgrade. 2. Select the Upgrade Method, either Fetch image from HTTP/HTTPS Server or Upload
Image. l To upgrade via Fetch image from HTTP/HTTPS Server, enter the URL for the system
image in the Image URL text-entry field. l To upgrade via Upload Image, navigate to the directory containing the appropriate upgrade
image file and drag and drop the image onto the target page section or click select file to open a dialog.
Note: To upgrade to a version that is several releases newer than your current release, you must install all the major releases in between before the latest one.
3. Click Perform Upgrade. When the upgrade has started, the System Upgrade page displays feedback as to the state of the process.
Caution: The Advanced Options section should only be used as part of an Opengear Support call.
UPGRADE MULTI INSTANCE LIGHTHOUSE
Note: The upgrade must be performed through the Primary Lighthouse instance.
When the primary Lighthouse is updated, any secondary instance Lighthouses are updated after the primary has successfully booted. Secondary Lighthouse upgrades are performed in parallel (not in a queue) to speed up the overall process.
Note: If any Lighthouse fails to successfully upgrade along the way, the upgrade stops.
24.12.1
Managing Lighthouse
146
Lighthouse User Guide
Before a multiple instance upgrade is attempted, compatibility and status checks are performed on primary/secondary instances to pre-empt possible failure points. Where there are multiple instances of Lighthouse, when a system upgrade is being performed the status of secondary instances is flagged in the > SYSTEM > System Upgrade page. During a system upgrade, notification/status elements are flagged in the following scenarios: l When an upgrade is attempted, a pass/fail notification on the instance. l When an upgrade is attempted on a secondary instance, a pass/fail notification on the
associated primary instance.
Note: Information about the upgrade progress and status is visible by navigating to the Jobs page.
UPGRADE LIGHTHOUSE VIA THE CLI
Lighthouse includes a shell-based tool -- sysflash -- that allows a user with administrative privileges to upgrade the system for the instance from the local terminal.
Note: Before you use sysflash, we recommend that you check available disk space when manually uploading .lh upgrade files. We also suggest you use /mnt/nvram as the path.
UPGRADE VIA LOCAL TERMINAL
To upgrade the system for the Lighthouse instance using the Lighthouse local terminal: 1. Select Terminal. 2. At the [hostname] login: prompt, enter an administrator username and press Enter. 3. At the Password: prompt, enter the administrator's password and press Enter.
24.12.1
Managing Lighthouse
147
Lighthouse User Guide
4. To use sysflash with a .lh_upg file available via an HTTP or HTTP server, at the local terminal bash shell prompt, enter a URL that it is URL encoded.
>sysflash http[s]%3A%2F%2Fdomain.tld%2Fpath%2Fto%2Ffirmware-upgrade- image.lh_ upg
5. Press Enter.
UPGRADE VIA LOCAL FILE SYSTEM
To upgrade Lighthouse with sysflash and a .lh_upg file available via the local file system: 1. Select Terminal. 2. At the [hostname] login: prompt, enter an administrator username and press Enter. 3. At the Password: prompt, enter the administrator's password and press Enter. 4. At the local terminal bash shell prompt enter:
>sysflash /path/to/system-upgrade-image.lh_upg
5. Press Enter.
Note: sysflash includes several flags that allow for variations in the standard system upgrade process. These flags should not be used unless directed to do so by Opengear Support.
List the flags by running either of the following at a local terminal bash shell prompt: sysflash -h or sysflash --help
24.12.1
Managing Lighthouse
148
Lighthouse User Guide
UPGRADE NETOPS MODULES
NetOps modules are released independently of Lighthouse software or Operations Manager firmware.
Node upgrades may be carried out through the Lighthouse UI.
UPGRADE VIA LIGHTHOUSE UI
1. Log in to the Lighthouse web UI with a user assigned with Netops permissions. 2. In the Menu Pane, select NetOps > NetOps Installation.
The NETOPS INSTALLATION page displays with the ONLINE tab selected. 3. Select Online. 4. Click Start Online Sync.
TROUBLESHOOT THE UPGRADE PROCESS
There are two main reason why an upgrade fails:
Reason
Description
Migration failures
Lighthouse will return to the pre-upgrade state. An example of such a failure is malformed data in the database, which does not conform to more stringent schema checks in the new version.
System level failures
This would include environmental issues such as power loss during the upgrade. If such an issue prevented Lighthouse from rolling back to the previous state, Lighthouse may be left in an unusable state.
24.12.1
Managing Lighthouse
149
Lighthouse User Guide
RECOVER FROM A FAILED UPGRADE
If Lighthouse is in an unusable state (either as a result of upgrade problems, or any other catastrophic failure), you can: 1. Promote a secondary Lighthouse, or 2. Restore a configuration backup, or 3. Manually retry upgrade.
PROMOTE A SECONDARY LIGHTHOUSE
This requires multiple instances of Lighthouse. If the primary Lighthouse instance is unreachable, one of the existing secondary instances can be promoted to become the new primary Lighthouse instance. The old primary Lighthouse instance should be replaced with a fresh installation of Lighthouse. This can then be enrolled as a secondary to the newly promoted primary Lighthouse. For steps, see Promote a Secondary Instance.
RESTORE A CONFIGURATION BACKUP
Deploy a Lighthouse instance with the version you are upgrading from. Restore the configuration backup taken before the failed upgrade. For steps, see Configuration Restore.
MANUALLY RETRY UPGRADE
Manually retry via the CLI if a secondary upgrade fails. Determine the reason for the upgrade failure and resolve the issue before you retry the upgrade. Assistance from Opengear technical support may be required.
24.12.1
Managing Lighthouse
150
Troubleshoot a Failed Secondary Lighthouse Upgrade
Lighthouse User Guide
Note: The CLI interface commands have maintained references to unbound instances. Within the Lighthouse user interface, dependent instances have been renamed to Secondary Lighthouses.
To retry the upgrade for a secondary Lighthouse, first list the instance and identify the IDs of the secondary lighthouses that must be retried by running the retry_dependent_upgrades list command. retry_dependent_upgrades list command will list all the secondary lighthouses and their current status, as in the example below:
root@lighthouse:~# retry_dependent_upgrades list ID UUID Hostname Firmware Version Fw Status Lighthouse Status 2 lighthouse_configurations-2 lighthouse-2 22.11.2 not updated UpgradeFailed 3 lighthouse_configurations-3 lighthouse-3 24.02.0 updated Enrolled 4 lighthouse_configurations-4 lighthouse-4 22.11.2 not updated UpgradeFailed
In the example above, the Lighthouses with IDs 2 and 4 have failed to upgrade (note that the "Enrolled" status is the wanted status). To re-trigger an upgrade for those lighthouses run the following command. Ensure that the lighthouse IDs are comma separated:
retry_dependent_upgrades trigger -l 2,4
The method above is the recommended way but there is a shortcut to re-trigger all failed secondary upgrades by running the command below:
retry_dependent_upgrades trigger --failed
Note: Only one secondary upgrades at a time.
24.12.1
Managing Lighthouse
151
Lighthouse User Guide
You should be able to view the secondary upgrade progress in the primary Lighthouse UI as you would for a normal upgrade.
Contact Support
In the unlikely event that Lighthouse does not automatically recover, or your troubleshooting efforts fail, contact Opengear support for advice with the following information available to share: l If your instance is usable, download a Technical Support Report (from the Help menu). l The configuration backup taken before the upgrade process.
CONFIGURATION BACKUP
Before you perform a factory reset or system upgrade, you may want to backup the current Lighthouse configuration. To backup: 1. In the Settings Pane, select > SYSTEM > Backup, Restore and Reset.
The BACKUP, RESTORE AND RESET page displays with the CONFIGURATION BACKUP tab selected. 2. Optional: Specify any additional User Files you want to include in the backup. Enter one file or directory per line. 3. Specify whether to Encrypt Backup. To enable: a. Select Enabled. b. Enter and confirm a password. 4. Click Download Backup and save this file. The filename consists of a timestamp and lh_bak extension, for example: lighthouse20190710100325.lh_bak
CONFIGURATION RESTORE
To restore the configuration and user files:
24.12.1
Managing Lighthouse
152
Lighthouse User Guide
1. In the Settings Pane, select > SYSTEM > Backup, Restore and Reset. The BACKUP, RESTORE AND RESET page displays with the CONFIGURATION BACKUP tab selected.
2. Select the CONFIGURATION RESTORE tab. 3. Navigate to the directory that contains the appropriate configuration image file, then drag and
drop the file onto the target page section or click select file to open a dialog. Supported files: .lh_bak. 4. Enter the Backup Password if the configuration was encrypted. 5. Click Restore Backup. The CONFIGURATION RESTORE CONFIRMATION dialog displays. 6. Click Yes. Lighthouse restores the backup and any included user files, then restarts.
Considerations If Using Multiple Instances
Lighthouse Version BEFORE 23.04.1 23.04.1 AND LATER
Consideration
Existing dependent Lighthouse instances will not be synced with the primary, and must be deleted and re-enrolled again.
The newly restored primary should re-establish contact with the existing dependent instances. The databases may be out of sync at first, but will be re-synced automatically.
SHUT DOWN OR RESTART LIGHTHOUSE
The following sections describe the process to shut down or restart Lighthouse. This includes finding instance version, returning to factory setting, and shutting down or restarting a running version of Lighthouse.
24.12.1
Managing Lighthouse
153
Lighthouse User Guide
FIND THE CURRENT LIGHTHOUSE INSTANCE VERSION
You can find the current Lighthouse version in the following ways: l Displayed under the logo in the top-left of the display. l Located within the Lighthouse UI in the instance details. l Via the local Lighthouse shell.
VERSION INFORMATION WITHIN THE LIGHTHOUSE UI
1. In the Header Pane, click . The information panel expands.
VERSION INFORMATION VIA THE LOCAL SHELL
1. In the Menu Pane, select Terminal. The TERMINAL page displays.
2. At the [hostname] login: prompt, enter an administrator username and press Enter. 3. At the Password: prompt, enter the administrator password and press Enter. 4. At the bash shell prompt, enter cat /etc/version and press Enter.
The current Lighthouse instance's version is returned to STD OUT. For example: root@lighthouse:~# cat /etc/version 2022.Q1.0
Note: The procedure above uses the Web UI to reach the Lighthouse Local Terminal. This is not the only way to reach the Lighthouse shell and cat /etc/version works in any circumstance where an administrator has access to the Lighthouse shell. For example, many of the Virtual Machine Manager applications that can run a Lighthouse instance offer virtual console access. If this is available and an administrator logs in to the Lighthouse shell via this console, the command string works as expected.
24.12.1
Managing Lighthouse
154
Lighthouse User Guide
OTHER INFORMATION SOURCES
Two other command strings can be useful when specifics about a particular Lighthouse instance are required. Both these commands can be run by an administrator with access to a running Lighthouse instance's bash shell. First is cat /etc/sw*. This command concatenates the following four files to STD OUT:
/etc/sw_product /etc/sw_variant /etc/sw_vendor /etc/sw_version
For example:
# cat /etc/sw* lighthouse release opengear 2022.Q1.0
Second is cat /etc/issue. /etc/issue is a standard *nix text file which contains system information for presenting before the system's login prompt. On a Lighthouse instance, /etc/issue contains the vendor and Lighthouse product version.
# cat /etc/issue Opengear Lighthouse 2022.Q1.0 \n \l
SHUT DOWN A RUNNING LIGHTHOUSE INSTANCE
1. In the Menu Pane, select Terminal. The TERMINAL page displays.
24.12.1
Managing Lighthouse
155
Lighthouse User Guide
2. At the [hostname] login: prompt, enter an administrator username and press Enter. 3. At the Password: prompt, enter the administrator password and press Enter. 4. Enter the command shutdown now and press Enter.
The Lighthouse instance shuts down.
RESTART A RUNNING LIGHTHOUSE INSTANCE
1. In the Menu Pane, select Terminal. The TERMINAL page displays.
2. At the [hostname] login: prompt, enter an administrator username and press Enter. 3. At the Password: prompt, enter the administrator password and press Enter. 4. At the prompt enter one of the following commands:
l reboot and press Enter, or l shutdown -r now and press Enter. The Lighthouse instance shuts down and reboots.
RETURN A LIGHTHOUSE INSTANCE TO FACTORY SETTINGS
At some stage, you may require a return to the factory settings. You can do this either through the UI or by running a shell script if you have root access.
Note: During this process, the current Lighthouse configuration is overwritten and user files are deleted. If you want, you can create a backup of the configuration and any required user files.
To return a Lighthouse instance to its factory settings using the Lighthouse UI:
24.12.1
Managing Lighthouse
156
Lighthouse User Guide
1. Login to the Lighthouse as root.
Note: Other users, even those with full administrative privileges, do not have the permissions required to reset the Lighthouse VM to its factory settings.
2. In the Settings Pane, select > SYSTEM > Backup, Restore and Reset. The BACKUP, RESTORE AND RESET page displays with the CONFIGURATION tab selected.
3. Select the FACTORY RESET tab. 4. Read and understand the warning presented. 5. To proceed, type YES in the confirmation field. 6. Click Reset Lighthouse.
MONITOR JOBS
You can keep track of jobs in Lighthouse which are scheduled, running, or have run. To view current or scheduled jobs: 1. In the Menu Pane, select Jobs.
The JOBS page displays with the CURRENT tab selected. 2. To display jobs that have completed, select the ENDED tab. 3. Use the Filter Jobs control to refine the jobs displayed. 4. To view the details of a job, click the link in the Type column for the job.
The job details dialog displays.
24.12.1
Managing Lighthouse
157
Lighthouse User Guide
CONFIGURING LIGHTHOUSE
Lighthouse can be customized as required, by the creation of users and user groups, to enable Smart Management Fabric, for authentication, and to enable network traffic mirroring.
MANAGE TEMPLATES
Templates are a centralized way of changing the configuration for enrolled Opengear device nodes by pushing predefined configuration templates to selected nodes.
CUSTOM TEMPLATES
The following list describes the types of configuration templates that you can create and manage: l Authentication l Scripts l Smart Management Fabric l Users & Groups PREDEFINED TEMPLATES
The following list describes predefined templates that you can push/deploy as required.
Note: The availability of these templates is dependent on your subscription type.
l Port Logging l Templates to activate NetOps modules, see Manually Apply NetOps Modules via Template:
l IP Access l Automation Gateway l Secure Provisioning
24.12.1
Configuring Lighthouse
158
Lighthouse User Guide
l Templates to clean up nodes where NetOps is no longer used, see Disable NetOps Modules via Template.: l Disable IP Access l Disable Automation Gateway l Disable Secure Provisioning
Note: Clean up templates only work on Opengear devices.
MANAGE AUTHENTICATION TEMPLATES
Only users assigned to the Lighthouse Administrator role can access Node Tools > Config Templates > Authentication Templates and manage authentication templates.
CREATE AN AUTHENTICATION TEMPLATE
Note: Only Lighthouse Administrators can create authentication templates.
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Click New Config Template. The PICK A CONFIG TYPE selection options expand.
3. Select Authentication. The ADD AUTHENTICATION TEMPLATE page displays.
4. Under Template Details: a. Enter a Name for the template. b. Enter a Description for the template.
5. Under Authentication Settings:
24.12.1
Configuring Lighthouse
159
Lighthouse User Guide
a. Select Pre Populate to populate the template fields with the current Lighthouse remote authentication settings.
b. Select the required Scheme: l Local Users Only l Radius i. Enter the Address and Port for the remote authentication server . ii. If required, click Add Authentication Server to add an additional remote authentication server . iii. If required, click Add Accounting Server to add a remote accounting server. iv. Enter the Server Password and Confirm Password. l TACACS+ i. Enter the Address and Port for the remote authentication server. ii. If required, click Add Authentication Server to add an additional remote authentication server. iii. Select the TACACS+ login method used to authenticate to the server from PAP, CHAP, or Login. The selection defaults to PAP. To use DES encrypted passwords, select Login. iv. Enter the Server Password and Confirm Password. v. Enter the TACACS+ service with which to authenticate. This determines which set of attributes are returned by the server. Defaults to "raccess". l LDAP i. Enter the Address and Port for the remote authentication server. ii. If required, click Add Authentication Server to add an additional remote authentication server.
24.12.1
Configuring Lighthouse
160
Lighthouse User Guide
iii. If required, enter LDAP Base DN details. The distinguished name of the search base. For example: dc=my-company,dc=com.
iv. If required, enter LDAP Bind DN details. The distinguished name to bind to the server with. The default is to bind anonymously.
v. If required, enter Bind DN Password and Confirm Password. vi. If required, enter LDAP Username attribute details.
The LDAP attribute that corresponds to the login name of the user (commonly "sAMAccountName" for Active Directory, and "uid" for OpenLDAP). vii. If required, enter LDAP group membership attribute details. viii. Check the Ignore Referrals check box to disregard LDAP referrals to other servers (Only applied to OM Devices). ix. Select the SSL protocol. x. Check the Ignore SSL certificate errors check box to ignore errors encountered when accessing LDAPS servers. xi. Select and upload the CA certificate to validate LDAPS servers. 6. Click Save Template.
Notes: l When an authentication template is pushed to a node, the authentication settings at that
node are replaced by the authentication settings defined in the authentication template. l The authentication templates do not support the full list of settings that the Opengear
devices support. However, templates can be applied, and then additional settings configured manually.
EDIT AN AUTHENTICATION TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
24.12.1
Configuring Lighthouse
161
Lighthouse User Guide
2. The AUTHENTICATION tab is selected. 3. Select the name of the template to be modified.
The EDIT AUTHENTICATION TEMPLATE page displays. 4. Make the required changes. 5. Click Save Template.
DELETE AN AUTHENTICATION TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. The AUTHENTICATION tab is selected. 3. Select the name of the template to be deleted.
The EDIT AUTHENTICATION TEMPLATE page displays. 4. Click Delete Template.
A confirmation dialog displays. 5. Click Delete.
MANAGE SCRIPT TEMPLATES
Script Templates allow the user to upload arbitrary shell scripts to be run on a node. For example, a script may set additional configuration settings not available in other templates or store additional files onto the node such as certificates. The uploaded script must: l Have a .sh extension. l Be less than 1MB in size. Other than those, there are no other restrictions on the script file to be uploaded. When saved, the template stores the size and SHA1 checksum of the script. This can be used to verify the script contents of the template when saved.
24.12.1
Configuring Lighthouse
162
Lighthouse User Guide
To apply script templates, the selected nodes must be running firmware version 4.1.1 or later.
CREATE A SCRIPT TEMPLATE
Note: Only Lighthouse Administrators can create script templates.
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Click New Config Template. The PICK A CONFIG TYPE selection options expand.
3. Select Scripts. The ADD SCRIPT TEMPLATE page displays.
4. Enter a Name and Description for the template. 5. Enter the Script timeout.
This is the time to wait (in minutes) for the execution of the script. After timeout is reached, script will be stopped. 6. Select and upload the script file. Supported files: .sh 7. Click Save Template.
Note: Script checksum and Script size are displayed after the template with uploaded script is saved.
EDIT A SCRIPT TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the SCRIPT tab. 3. Select the name of the template you want to modify.
The EDIT SCRIPT TEMPLATE page displays.
24.12.1
Configuring Lighthouse
163
Lighthouse User Guide
4. Make the required changes. 5. Click Save Template.
DELETE A SCRIPT TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the SCRIPT tab. 3. Select the name of the template you want to delete.
The EDIT AUTHENTICATION TEMPLATE page displays. 4. Click Delete Template.
A confirmation dialog displays. 5. Click Delete.
MANAGE SMART MANAGEMENT FABRIC TEMPLATES
Smart Management Fabric allows you to create an enterprise grade Open Shortest Path First (OSPF) solution for network connectivity, configuration and troubleshooting devices connected to supported nodes on Lighthouse, wherever they may be.
Caution: Smart Management Fabric is an advanced feature. Prior to roll out, it is recommended to ensure its compliance with your enterprise security posture.
24.12.1
Configuring Lighthouse
164
Lighthouse User Guide
Smart Management Fabric uses dynamic link state routing to allow IP connectivity to IT resources regardless of whether the connection is either: l Physically, via USB, serial ports that are configured with IP addresses l Virtually, via SSH, https (GUI), SPs/BMCs (iLO, iDRAC, etc.) l Via commonly used automation tools such as RDP, Ansible, Python, vCenter Smart Management Fabric templates allow OSPF to be run on a node. For example, a template may set network addresses, subnet masks and authentication methods. To apply Smart Management Fabric templates, the selected nodes must be: l a supported Opengear appliance l running firmware version 23.10 or later.
Note: A user can override the smart management fabric configuration by using the command line interface tool.
24.12.1
Configuring Lighthouse
165
Lighthouse User Guide
CREATE A SMART MANAGEMENT FABRIC TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Click New Config Template. The PICK A CONFIG TYPE selection options expand.
3. Select Smart Management Fabric. The ADD SMART MANAGEMENT FABRIC TEMPLATE page displays.
4. Under Template Details: a. Enter the Name of the template. b. Enter the Description of the template.
5. Under OSPF Settings: a. Check the check boxes for the applicable Routing Options: l Check Redistribute Connected to redistribute directly connected routes to all routers in the attached Routing Information Protocol (RIP) domain. l Check Redistribute Kernel to share the static routes on the devices. b. Check the Enable Masquerading for all interfaces check box to override individual masquerading settings on interfaces. Select the OSPF Configuration Method. Select one of the following to send link-state advertisements on one of following: l Select Interface to advertise OSPF on the whole interface: i. Click Add Interface. The ADD INTERFACE dialog displays. ii. Enter the Interface Name. This must match the name of the interface on the device. iii. Check the Masquerade Interface check box to show that traffic from this interface appears to come directly from the supported node to other devices in the subnet.
24.12.1
Configuring Lighthouse
166
Lighthouse User Guide
iv. Check the Passive Interface check box if routes are not to be propagated to the network it is on.
v. Enter the OSPF Area. vi. Enter the link Cost used in OSPF route calculations which indicates the overhead
required to send packets across the specified interface. vii. Select the Authentication Method from MD5, Clear Text or No Authentication.
Note: For MD5 at least one key is required. Click Add Digest Key to enter the key details.
l Select Network to define which networks should be advertised. i. Click Add Network. ii. Enter the Address, Subnet Mask, and OPSF Area. iii. Click Add Interface. The ADD INTERFACE dialog displays.
iv. Enter the Interface Name. This must match the name of the interface on the device.
v. Check the Masquerade Interface check box to show that traffic from this interface appears to come directly from the supported node to other devices in the subnet.
vi. Check the Passive Interface check box if routes are not to be propagated to the network it is on.
vii. Enter the link Cost used in OSPF route calculations which indicates the overhead required to send packets across the specified interface.
viii. Select the Authentication Method from MD5, Clear Text or No Authentication.
Note: For MD5 at least one key is required. Click Add Digest Key to enter the key details.
24.12.1
Configuring Lighthouse
167
Lighthouse User Guide
6. Click Save Template.
VALIDATE A SMART MANAGEMENT FABRIC TEMPLATE
To check that the Smart Management Template is applied and to verify that OSPF is running and configured, login to Lighthouse and Appliances CLI. Run the following commands to validate that the Smart Management Fabric template is properly applied:
vtysh -c "show running-config" vtysh -c " sh ip ospf neigh" -c " sh ip ospf route"
The templated OSPF/SMF values display, for example:
EDIT A SMART MANAGEMENT FABRIC TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the SMART MANAGEMENT FABRIC tab. 3. Select the name of the template you want to modify.
The EDIT SMART MANAGEMENT FABRIC TEMPLATE page displays.
24.12.1
Configuring Lighthouse
168
4. Make the required changes. 5. Click Update Template.
Caution: Firewall rules are added to the nodes to allow OSPF traffic.
Lighthouse User Guide
Note: You cannot edit the system Disable Smart Management Fabric template.
DELETE A SMART MANAGEMENT FABRIC TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the SMART MANAGEMENT FABRIC tab. 3. Select the name of the template you want to delete.
The EDIT SMART MANAGEMENT FABRIC TEMPLATE page displays. 4. Click Delete Template.
A confirmation dialog displays. 5. Click Delete.
Note: You cannot delete the system Disable Smart Management Fabric template.
MANAGE USER AND GROUP TEMPLATES
To navigate to the page: 1. Select Node Tools > Config Templates. 2. Select the USERS AND GROUPS tab. Each template contains a list of user-defined groups and/or individual users. Each group has a defined role which determines what privileges group members have. User roles are defined by the groups of which they are a member.
24.12.1
Configuring Lighthouse
169
Lighthouse User Guide
Note: Each template must contain at least one group.
The available group roles are: l Node Administrator: maps to the administrator role on the nodes. l Node User: maps to the ports user role and the pmshell role on the nodes. Ports access can be
restricted if required.
CREATE A USER AND GROUP TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Click New Config Template. The PICK A CONFIG TYPE selection options expand.
3. Select Users & Groups. The ADD USERS AND GROUPS TEMPLATE page displays.
4. Enter a Name and Description for the template. 5. Set the group list:
Note: Groups provided in the list replace any user defined groups on the node.
a. Click Add Group. The ADD GROUP dialog displays.
b. Enter the Group Name. c. Enter the Description. d. Select the Role as either Node Administrator or Node User.
24.12.1
Configuring Lighthouse
170
Lighthouse User Guide
e. If you select the Node User role: l Check the Restrict accessible Serial Ports check box to enter the permitted serial ports range. l In the Permitted Serial Ports Range field, enter the ranges. Use the format start-finish e.g. 1,3-5,8.
f. Click Add Group. 6. Set the user list:
Note: Users provided in this list replace any user defined users on the node.
a. Click Add User. The ADD USER dialog displays.
b. Enter the User Name. c. Enter the Description. d. Enter the Password and Passsword Confirmation. e. Check the check box next to the GROUP NAME(S) to select the Group Membership for the
user. f. Click Add User. 7. Click Save Template.
Note: When a Users and Groups template is pushed to a node, all custom groups on that node are replaced by groups defined in the template. If no users are in the new template, existing users remain on the node. To push users, the selected nodes must be running firmware version 4.3.0 or later.
24.12.1
Configuring Lighthouse
171
EDIT A USER AND GROUP TEMPLATE
EDIT A USERS AND GROUP TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the USERS AND GROUPS tab. 3. Select the name of the template you want to modify.
The EDIT USERS AND GROUPS TEMPLATE page displays. 4. Make the required changes. 5. Click Save Template.
DELETE A GROUP FROM A TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the USERS AND GROUPS tab. 3. Select the name of the template you want to delete.
The EDIT USERS AND GROUPS TEMPLATE page displays. 4. Select the group name from the SET GROUP LIST section.
The UPDATE GROUP dialog displays. 5. Click Delete. 6. Click Save Template.
DELETE A USER FROM A TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the USERS AND GROUPS tab.
24.12.1
Configuring Lighthouse
Lighthouse User Guide
172
3. Select the name of the template you want to modify. The EDIT USERS AND GROUPS TEMPLATE page displays.
4. Select the username from the SET USER LIST section. The UPDATE USER dialog displays.
5. Click Delete. 6. Click Save Template.
DELETE A USER AND GROUP TEMPLATE
1. In the Menu Pane, select Node tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the USERS AND GROUPS tab. 3. Select the name of the template you want to delete.
The EDIT USERS AND GROUPS TEMPLATE page displays. 4. Click Delete Template.
A confirmation dialog displays. 5. Click Delete.
DELETE USERS OR GROUPS FROM A TEMPLATE
Lighthouse User Guide
Note: To save the template, the system requires a minimum of either one Group or one User added.
DELETE A GROUP FROM A TEMPLATE
1. To modify a template by deleting a group, select main menu. The CONFIG TEMPLATE dashboard displays.
Node Tools > Config Templates from the
2. Select the USERS AND GROUPS tab.
24.12.1
Configuring Lighthouse
173
Lighthouse User Guide
3. Select the template you want to modify. The EDIT USERS AND GROUPS TEMPLATE page displays.
4. Select the group you want to delete from the SET GROUP LIST section by clicking the name of the group. The UPDATE GROUP dialog displays.
5. Click the Delete button. The group is deleted.
6. Click Save Template to save the changes.
DELETE A USER FROM A TEMPLATE
1. To modify a template by deleting a group, select main menu. The CONFIG TEMPLATE dashboard displays.
Node Tools > Config Templates from the
2. Select the USERS AND GROUPS tab.
3. Select the user you want to delete from the SET USER LIST section by clicking the username. The UPDATE GROUP dialog displays
4. Select the user to be deleted. The UPDATE USER dialog displays
5. Click the Delete button. The user is deleted.
6. Click Save Template to save the changes.
PUSH TEMPLATES
Users with Lighthouse Administrator privileges (that is, users with the Lighthouse Administrator role or users who are members of groups with the Lighthouse Administrator role) can access
Node TOOLS > Config Templates and push templates affecting nodes in node filters linked to their role.
24.12.1
Configuring Lighthouse
174
Lighthouse User Guide
The following types of templates can be applied to selected nodes: l Authentication l Users and Groups l Script l Netops Module Activation l Port Logging l Smart Management Fabric Lighthouse Administrators can manually apply the Netops modules of Secure Provisioning, Automation Gateway, or IP Access to the suitable Opengear Console Server node.
PUSH A TEMPLATE
The process to push templates consists of four steps, each one a step in the overall wizard: 1. Select a template:
a. Select Node Tools > Config Templates. The CONFIG TEMPLATES page displays.
b. Select a template config type tab: l AUTHENTICATION l NETOPS MODULES l PORT LOGGING l SCRIPT l SMART MANAGEMENT FABRIC l USERS AND GROUPS
c. For the required template click the Push template icon on the right of the row. The PUSHING TEMPLATE page displays.
2. Select the target nodes: click the check boxes next to the target nodes.
24.12.1
Configuring Lighthouse
175
Lighthouse User Guide
Note: Third-party nodes are not supported for template execution.
3. Click Run Pre-Flight Test. This test run simulates what happens if the template is pushed to the selected nodes. After all nodes finish pre-flight, the Pre-flight Status goes green and the Push Configuration button becomes active.
4. Push the template: a. Click Push Configuration. b. Confirm the TEMPLATE RUN STATUS per node as displayed in the column. c. Confirm the PUSH STATUS per node as displayed in the column. d. Click Exit to Config Templates.
MANUALLY APPLY NETOPS MODULES VIA TEMPLATE
Note: The availability of these templates is dependent on your subscription type.
1. In the Menu Pane, select Node Tools > Config Templates. The CONFIG TEMPLATES page displays.
2. Select the NETOPS MODULES tab. The available templates display.
3. For the following templates, click the Push template icon on the right of the row: l Secure Provisioning: to apply Secure Provisioning to the selected nodes. l IP Access: to apply IP Access to the selected nodes. l Automation Gateway: to apply Automation Gateway to the selected nodes. The PUSHING TEMPLATE page displays.
4. Select the check boxes next to the required nodes.
24.12.1
Configuring Lighthouse
176
Lighthouse User Guide
Note: Only applicable Console Servers for the module display during this node selection step.
5. Click Run Pre-Flight Test. The test status is displayed in the PREFLIGHTSTATUS column for the node.
6. When pre-flight is complete, click Push Configuration.
DISABLE NETOPS MODULES VIA TEMPLATE
If NetOps is uninstalled, the nodes may continue to run NetOps modules and we recommend a node clean up.
Notes: l The availability of these templates is dependent on your subscription type. l Clean up templates only work on Opengear devices. l If you are cleaning up the nodes due to the installation of a subscription, it is recommended
to perform the clean up BEFORE you apply the subscription so that you can identify the nodes running NetOps before NetOps is disabled.
IDENTIFY NODES RUNNING NETOPS
IMPORTANT: If you have already deactivated NetOps (via subscription installation or otherwise) prior to identifying the nodes running NetOps, then this filter is not available and you can no longer identify the nodes.
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Click the Filter Nodes drop-down and select New Node Filter. The filter criteria section displays.
24.12.1
Configuring Lighthouse
177
Lighthouse User Guide
3. From the Field to search, select NETOPS > Module. 4. From the Value drop-down, select the appropriate NetOps module from Automation gateway,
IP Access, or Secure Provisioning. 5. To include multiple NetOps modules, click Add Criteria and repeat steps 3 and 4 for any
additional NetOps modules. 6. Click Apply.
The list of nodes updates to display only nodes running the selected NetOps modules.
CLEAN UP NODES AND DISABLE NETOPS
1. In the Menu Pane, select Node Tools > Config Templates. The CONFIG TEMPLATES page displays with the AUTHENTICATION tab selected.
2. Select the NETOPS MODULES tab. The available templates display.
3. For the following templates, click the Push template icon on the right of the row: l Disable Secure Provisioning: to disable Secure Provisioning if present on the selected node(s). l Disable IP Access: to disable IP Access if present on the selected node(s). l Disable Automation Gateway: to disable Automation Gateway if present on the selected node(s). The PUSHING TEMPLATE page displays.
Note: This page automatically has a filter applied to display only nodes with the selected NetOps module. You can remove the filter if required and display all enrolled nodes.
4. Select the check boxes next to the required nodes. 5. Click Run Pre-Flight Test.
The test status is displayed in the PREFLIGHTSTATUS column for the node.
24.12.1
Configuring Lighthouse
178
Lighthouse User Guide
6. When pre-flight is complete, click Push Configuration. The templates connect to the selected nodes and remove docker entries associated with the module and call the deactivate NOM endpoint.
TECHNICAL SUPPORT REPORTS
Lighthouse can generate a technical support report that includes Lighthouse configuration information and the current system log for the Lighthouse VM. The support technician may ask for this report if you contact Opengear Technical Support.
GENERATE A SUPPORT REPORT VIA THE LIGHTHOUSE INTERFACE
1. In the Header Pane, click to expand the help menu. 2. Select Generate Technical Support Report.
The help menu updates to display the following message: Report is being generated. Download starts automatically.
The generation completes and the help menu updates to display the following message: Report Downloaded Successfully.
GENERATE A SUPPORT REPORT VIA THE LOCAL TERMINAL
1. In the Menu pane, select Terminal. The TERMINAL page displays.
2. At the [hostname] login: prompt, enter an administrator username and press Enter. 3. At the password: prompt, enter the administrator password and press Enter. 4. At the bash shell prompt, enter: support-report -z > /tmp/support.zip and press
Enter.
24.12.1
Configuring Lighthouse
179
Lighthouse User Guide
The -z switch generates the same combined file produced by the download support report link noted in the Lighthouse UI specific procedure.
Note: In the example above, the redirect saves the generated zip file to /tmp/support.zip. However, be aware that the /tmp directory is deleted during a reboot, so the file might be saved to a different location.
Following are two options for copying the file from Lighthouse: 1. Use SCP from a Mac or Windows client. As scp only requires ssh access, no additional
configuration is required on Lighthouse for this to work.
$ scp root@192.168.0.2:/tmp/support.zip . root@192.168.0.2's password: support.zip 100% 321 604.0KB/s 00:00
Note: For Windows users, WinSCP on Win10 also works.
2. Use the FTP client on Lighthouse to copy the file to an FTP server. Passive mode must be used for this to work.
root@LH5-UK-Lab:/tmp# ftp ftp> open 192.168.0.216 Connected to 192.168.0.216. 220 im7200-demo-uk FTP server (GNU inetutils 1.4.1) ready. Name (192.168.0.216:root): fred 331 Password required for fred. Password: 230- *** Opengear UK Demo IM7216 *** 230 User fred logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> passive Passive mode on. ftp> bin 200 Type set to I. ftp> put support.zip 227 Entering Passive Mode (192,168,0,216,208,166)
24.12.1
Configuring Lighthouse
180
Lighthouse User Guide
150 Opening BINARY mode data connection for 'support.zip'. 226 Transfer complete. 4132664 bytes sent in 0.128 seconds (32262492 bytes/s) ftp> quit 221 Goodbye.
CONFIGURE LIGHTHOUSE FOR NETWORK TRAFFIC MIRRORING
Lighthouse can be integrated with a user's enterprise Intrusion Detection System (IDS) for realtime detection of security events in their network infrastructure.
24.12.1
Configuring Lighthouse
181
Lighthouse User Guide
Lighthouse allows users to configure the network traffic tap feature via the command line interface. The traffic_mirroring command: l Mirrors all network traffic over the encrypted OpenVPN tunnel between Lighthouse and the
Opengear supported appliances, and forwards all network traffic as decrypted packets to a configurable endpoint. The endpoint is expected to be a "gateway" IP address of an external device that is routable from Lighthouse. l Preserves the original UDP and TCP/IP header information while mirroring (so that the IDS can reassemble TCP streams and inspect the payload).
Note: Traffic mirroring is only supported on TCP and UDP.
l Provides an option to add a configurable VLAN tag to the Ethernet header. l Works with multiple instances. Only users with sudo access on the primary Lighthouse CLI (for example, via the admin group) can enable or disable traffic mirroring. Users must ensure that: l the traffic is routed to the required destination in their enterprise network. l their firewall rules allow traffic mirroring.
Note: All functionality is available only via the Lighthouse CLI. There is no UI or REST API interface for network traffic mirroring feature. For detailed CLI usage see traffic_ mirroring --help.
CONFIGURE NETWORK TRAFFIC MIRRORING FOR MULTIPLE INSTANCES
You can configure network traffic mirroring for multiple instances of Lighthouse. It can mirror traffic between Lighthouses, and between a node and a dependent Lighthouse.
24.12.1
Configuring Lighthouse
182
Lighthouse User Guide
If new dependent Lighthouses are added to a network that is mirroring traffic, they must be reconfigured for network traffic mirroring.
Note: All CLI configuration, including enabling and disabling, must be run on the primary Lighthouse. A dependent Lighthouse can only run the --test and --status arguments.
Users can specify different settings for each Lighthouse. For example: l A dependent Lighthouse can have a different VLAN ID (or no VLAN ID), and a different
destination IP. l A dependent Lighthouse can be set to only mirror node traffic, and not multi-instance traffic.
This is useful because the primary is already mirroring that traffic. l You can enable or disable network traffic mirroring per instance.
Note: All newly enrolled secondary Lighthouse instances have network traffic mirroring disabled by default.
TROUBLESHOOT NETWORK TRAFFIC MIRRORING
It is possible that there may be momentary periods of up to a few seconds where traffic is not being mirrored. For example mirroring outages of a few seconds can occur during: l Configuration if changes are being made to the VPN subnet or firewall. l The Lighthouse boot process. To ensure that traffic monitoring is uninterrupted, avoid rapid changes to configuration and repeated reboots of Lighthouse.
LIGHTHOUSE CLI, SERIAL PORT, AND REST API LOGGING
Lighthouse offers command line interface (CLI) and REST API logs.
24.12.1
Configuring Lighthouse
183
Lighthouse User Guide
Note: Logging is disabled by default.
When enabled, CLI and REST API logs can be found in /var/log/messages. All passwords are masked in the logs so that sensitive information is not stored in plain text or leaked. When you enable logging, you are not required to restart or log out and in again. There are a few caveats: l CLI logging only works for interactive (human-controlled) terminals. Commands generated by
automated scripts are not logged. l Commands such as ssh or telnet do not produce logs for the commands sent over the
connection. l Requests can be logged for all endpoints, however, only endpoints implemented in Lipy can
have responses logged.
Note: These logs are not intended to be used as a definitive record of all commands that have ever been run. A malicious user with full root access can circumvent anything.
For more details, see: https://ftp.opengear.com/download/documentation/api/lighthouse/og-restapi-specification-v3-7.html.
USE OGCONFIG-CLI TO ENABLE LOGGING
To enable logging, you should use ogconfig-cli. Use the following commands in a Lighthouse terminal to view, enable, or disable logging:
Command
Description
system.logging_cli_enabled
Enable or disable logging commands entered in the Lighthouse Terminal.
24.12.1
Configuring Lighthouse
184
Command system.logging_rest_ enabled
system.logging_rest_ request_enabled
Lighthouse User Guide
Description
Enable or disable basic logging for the REST API. These logs report the following information about every REST API call:
l Time l Request type (GET/POST/PUT/DELETE) l HTTP status code l Username l Source IP Address l Endpoint
Enable or disable request logging for every REST API call. In addition to the basic logging, also logs the request body that was provided by the client, if any. Requires system.logging_rest_enabled to be enabled.
USE OGCONFIG-CLI TO PERFORM CONFIG SEARCHES
You can perform simple config searches from inside ogconfig-cli with the find command.
Note: The element being searched must be a list, otherwise the command returns an error.
The syntax is: find <path of list to search> <element to search for> <value to search for> For example, to find enabled users use:
24.12.1
Configuring Lighthouse
185
Lighthouse User Guide
ogcfg > find users enabled true Or to find the enabled ports on a particular node set, use: ogcfg> find nodes[0].ports mode 'ConsoleServer'
ADD NODE AND PORT TO LIGHTHOUSE LOGS
Node and port logs use the pmshell function to log all access to nodes via Lighthouse , including which console, and which port was accessed by the user when logged in. When system logging is enabled, user and node selection and user and port selection is logged. To enable node and port logging on Lighthouse: 1. Select Terminal.
A local terminal window displays. 2. Login to a user that has rights to use CLI and ogconfig-cli. 3. Enable node and port logging through ogconfig-cli as follows:
root@lighthouse:~# ogconfig-cli ogcfg> set system.logging_cli_enabled true root-1-system_logging_cli_enabled: Integer <True> ogcfg> push OK ogcfg> exit
After node and port logging is enabled, you can view any logs recorded in your Lighthouse's syslog, located at /var/log/messages.
EXAMPLE LOGS
Here is an example of logs without request or response logging:
24.12.1
Configuring Lighthouse
186
Lighthouse User Guide
2020-03-17 15:29:37,237 INFO [root:117][waitress] POST 400 (root | 192.168.1.1) /api/v3.4/system/licenses/file 2020-03-17 15:30:23,034 INFO [root:117][waitress] GET 200 (root | 192.168.1.1) /api/v3.4/users?page=1&per_page=10
Here is an example of logs with request or response logging:
Note: These logs differ slightly due to being logged with different systems.
2020-05-11T05:45:09.567214+00:00 lighthouse rest_api_log[2465]: PUT 200 (root | fd07:2218:1350:4b:a438:f8ff:fe4f:65fc) -/api/v3.4/system/cli_session_timeout REQUEST={"system_cli_session_timeout":{"timeout":0}} 2020-05-11 05:45:18,999 INFO [lipy.logging.rest_api:62][waitress] GET 200 (root | fd07:2218:1350:4b:a438:f8ff:fe4f:65fc) -/api/v3.4/users?page=1&per_page=10 RESPONSE={'users': [{'username': 'root', 'description': 'System wide SuperUser account', 'enabled': True, 'id': 'users-1', 'no_password': False, 'expired': False, 'locked_out': False,'rights': {'delete': True, 'modify': True}, 'groups': ['groups-2']}], 'meta': {'total_pages': 1}}
ENABLE LOGGING
To enable logging, run these commands on the Lighthouse local terminal:
root@lighthouse:~# ogconfig-cli ogcfg> set <value> true root-1-<value>: Integer <True>
ogcfg> push OK ogcfg> exit
Replace <value> with the required setting:
24.12.1
Configuring Lighthouse
187
Lighthouse User Guide
l system.logging_cli_enabled l system.logging_rest_enabled l system.logging_rest_request_enabled (requires system.logging_rest_
enabled) l system.logging_rest_response_enabled (requires system.logging_rest_
enabled) To check if logging is enabled: To establish if logging is enabled run these commands on the Lighthouse local terminal: root@lighthouse:~# ogconfig-cli ogcfg> print system This produces output with Boolean values: system.logging_cli_enabled (bool): false l system.logging_rest_enabled (bool): false l system.logging_rest_request_enabled (bool): false l system.logging_rest_response_enabled (bool): false
DISABLE LOGGING
root@lighthouse:~# ogconfig-cli ogcfg> set <value> false root-1-<value>: Integer <False> ogcfg> push OK ogcfg> exit
Replace <value> with the required setting:
l
system.logging_cli_enabled
l
system.logging_rest_enabled
24.12.1
Configuring Lighthouse
188
l
system.logging_rest_request_enabled
l
system.logging_rest_response_enabled
Lighthouse User Guide
24.12.1
Configuring Lighthouse
189
Lighthouse User Guide
WORKING WITH LIGHTHOUSE NODES
After Lighthouse is installed and configured, enroll a small set of nodes, then create a set of tags and node filters that allow nodes access to be filtered to the correct subset of users. When these nodes are installed, test access to the Web UI and serial ports for the node. Node Filters, Port Filters and Resource Filters can be associated with a group, this restricts the group to only have access to those resources which match the filter. Note that these filters intersect for ports and nodes, if you give a user access to a node but access to the first port on every node, they can only access the first port on that node, and they won't be able to access the first port on any other nodes. If no filter is assigned, and the user has permissions to access the object in question ("Connected Resource Gateway" for resources and "Node and Devices (Base) for Nodes and Ports), then the user has access to all objects. Those permissions are disabled by default when you create a new role.
Note: You can leverage the Connected Resource Gateway to proxy via SSH, HTTP or HTTPS to configure your third-party nodes. For more information about configuring your thirdparty nodes, see Set up Lighthouse as a Connected Resource Gateway (CRG).
ENROLLMENT BUNDLES
An Enrollment Bundle stores provisioning information, allowing for bulk enrollment and manipulation of remote nodes. Applying an Enrollment Bundle during enrollment allows tags to be associated with nodes when they're first enrolled. This is useful for larger roll outs where many nodes are deployed with similar configuration and responsibilities. If relevant Node Filters have been set up, newly enrolled nodes are immediately visible for the relevant users to configure and use. Associating templates with an Enrollment Bundle allows you to run a set of templates on a node, after it is enrolled.
24.12.1
Working with Lighthouse Nodes
190
Lighthouse User Guide
ASSIGN SUBSCRIPTIONS TO A BUNDLE
l Every bundle is associated with a subscription. l If you only have one subscription, it is selected automatically. l If you have two subscriptions installed, then you must select which subscription to use for
nodes in the bundle.
CREATE AN ENROLLMENT BUNDLE
1. In the Menu Pane, select Node Tools > Enrollment Bundles. The ENROLLMENT BUNDLES page displays.
2. At the top of the page, cick Add Enrollment Bundle. The NEW ENROLLMENT BUNDLE page displays.
3. Under BUNDLE DETAILS: a. Enter a Name for the bundle. b. Enter a Token for the bundle. c. Set Auto-approve node to Enabled or Disabled. The default setting is Disabled. When Enabled, a device configured using this enrollment bundle is not placed in pending mode during the enrollment process. Instead, it is automatically approved for enrollment. d. Under Subscription Selection, select the subscription type you want to apply to the bundle. Where only one subscription is available, this is selected for you
4. Under BUNDLE TAGS, select or create the tags to apply to any nodes that enroll using this enrollment bundle: a. Click Add Tag. b. In the Tag Name field, either select a key from the drop-down, or type a new key and click Add new Tag.
24.12.1
Working with Lighthouse Nodes
191
Lighthouse User Guide
c. In the Tag Value field, either select a value from the drop-down or type a new value and click Add new Value.
5. Under BUNDLE TEMPLATES, select the templates to apply to any nodes that enroll using this Enrollment bundle: l To add a template: a. Click Add Templates. The CHOOSE TEMPLATES dialog displays. b. Select the check box for the templates you want to add. c. Click Add. l To remove a template, click the icon for the individual template.
Note: The templates in the table are executed in the order they appear. The templates can be reordered using the icons.
Caution: Template push operations stop if one template fails.
6. Under NETOPS MODULES, select the NetOps modules to automatically activate for any supported nodes:
Note: The availability of this section is dependent on your subscription type. If you have more than one subscription type, this section may be available but an error message may display if you try to add NetOps modules but did not select the right type of subscription in step 3.
l To add a bundle: a. Click Add Module. The CHOOSE MODULE dialog displays.
24.12.1
Working with Lighthouse Nodes
192
Lighthouse User Guide
b. Select the required NetOps Module from the list. c. Click Add. l To remove a bundle, click the icon for the individual bundle.
Note: The modules in the table are executed in the order they appear. The modules can be reordered by using the icons.
Caution: Module push operations stop if one template fails.
7. Click Apply.
STRUCTURE OF AN ENROLLMENT BUNDLE FILE
An enrollment bundle file, manifest.og, contains a series of field-value pairs that an unconfigured device can use to configure itself. Options that can be set in manifest.og include new firmware, custom configuration scripts, OPG config files, and Lighthouse Enrollment details. By default, manifest.og includes the following field-value pairs (with example values):
address=192.168.88.20 api_port=4443 bundle=bne-dc password=secret
Custom field-value pairs can be added manually. The field names are potential field names for a real-world, customized file, but the values following each field name are examples:
script=configure_ports.sh image=acm7000-3.16.6.image external_endpoints=192.168.1.2:4444,192.168.1.3:4445
24.12.1
Working with Lighthouse Nodes
193
Lighthouse User Guide
MANAGE THE ENROLLMENT SETTINGS
1. In the Menu Pane, select Node Tools > Enrollment Settings. The ENROLLMENT SETTINGS page displays.
2. Enter the Enrollment Token for nodes to request enrollment. 3. Select the Default Subscription for call home node enrollments.
The available nodes are displayed against the subscriptions. For more information about subscriptions, see Manage Subscriptions. 4. Optional: Click Download to download the manifest .og file. 5. Click Apply.
ENROLL NODES
Enrolling nodes is the process of connecting nodes to Lighthouse to make them available for access, monitoring, and management. A node is a device that can be enrolled with Lighthouse, allowing it to be accessed, managed, and monitored. You can enroll nodes in the following ways: l From the Lighthouse Web UI. l From the Node Web UI. l USB drive. l Mass Enrollment using Zero Touch Provisioning (ZTP). l Automatic enrollment of appliances as managed through the preference settings in the
Lighthouse Service Portal (LSP). The Lighthouse Service Portal is part of the Opengear Customer Portal.
Note: OPERATIONS MANAGER support may be partial for earlier releases, which may currently involve mass node enrollment using ZTP and enrollment via USB drive. However, all template types are supported.
24.12.1
Working with Lighthouse Nodes
194
Lighthouse User Guide
Credentials must be provided to authenticate either the Lighthouse during Enrollment via the Lighthouse WebUI, or the node during the other Enrollment scenarios. Lighthouse uses OpenVPN tunnels secured with certificate authentication to connect the Lighthouse instance and remote nodes. For the connections to work properly, the clocks/times between the Lighthouse instance and each remote node server must be synchronized. During the enrollment process when a new remote node is being added, if that node is not using NTP (Network Time Protocol) to synchronize its time, the node checks the HTTP Date header sent by Lighthouse in the enrollment request. The remote node then sets its own local system clock to match the time shown in that HTTP Date header from Lighthouse. This ensures that the new remote node has its time matched to the Lighthouse before the VPN tunnel is established, preventing potential time sync issues between the tunnel endpoints. If a remote node is relying on an NTP server to set its own time, it still checks the HTTP Date header sent by Lighthouse to affect the time synchronization but does not set its local time to that of the Lighthouse instance. When enrolling via Lighthouse, an administration username and password for the node must be provided. When enrolling via the node, an Enrollment token must be provided. A default Enrollment token can be set by selecting Node Tools > Enrollment Settings from the menu and individual tokens set per Enrollment bundle. Enrollment is a two-step process: 1. After enrollment begins, nodes receive their Enrollment package, and establish a VPN
connection to Lighthouse. 2. The node is now in the Pending state and must be Approved before the node is available for
access, management, or monitoring.
Note: This second step can be skipped by selecting the Auto-approve node checkbox when configuring an Enrollment bundle.
24.12.1
Working with Lighthouse Nodes
195
ENROLL A NODE VIA THE LIGHTHOUSE WEB UI
Lighthouse User Guide
Note: Enrollment via Lighthouse Web UI only works if the node is reachable from Lighthouse.
To enroll a node: 1. In the Header Pane, click Enroll Node.
The ENROLL NODES dialog displays. 2. From the Product Type drop-down, select the type of node to enrol.
You can select from: l Opengear device l Generic third party device l Avocent ACS6000 l Avocent ACS8000 l Avocent ACS Classic l Cisco 2900 Series l Digi Passport 3. Enter the Network Address. 4. Enter the Username, and Password of the node being enrolled.
Note: The Username and Password fields are for the login credentials required by the remote node being enrolled, not the login credentials used to login to the Lighthouse instance.
5. Select the Subscription Type. Each type shows the number of available subscriptions.
6. If required, you can also select to Auto-approve enrollment and/or Run pre-enrollment connectivity check.
24.12.1
Working with Lighthouse Nodes
196
Lighthouse User Guide
7. Click Enroll Node. When enrolled, the details for the console server are removed from the tab and added to the Nodes > ENROLLED tab.
Nodes > PENDING
ENROLL A NODE VIA THE NODE WEB UI
Note: If a node is behind a firewall, Lighthouse cannot initiate enrollment.
1. Access the Web UI for the node via its hostname or IP address. 2. Enter credentials and login. 3. Select Serial & Network > LIGHTHOUSE. 4. Enter the Server Address of Lighthouse (which can be hostname, FQDN, or IP address). 5. Optionally, enter the Server Port. 6. Enter the Enrollment Bundle (if a specific bundle is being used), and the Enrollment Token
(either the global token or the bundle-specific token). 7. Select Apply Settings.
The enrollment process begins. If Auto Approve is not enabled, when enrolled, the node displays in the Lighthouse Web UI under the Nodes > PENDING tab, with a Status of Approval. 8. Click the Approve Node icon in the right hand column.
Note: This step is applicable only if Auto Approve is not Enabled in the Enrollment Bundle.
ENROLL NODES VIA OM, ACM, CM, AND IM WEB UI
Nodes can be enrolled from other UIs such as the Operations Manager (OM).
24.12.1
Working with Lighthouse Nodes
197
Lighthouse User Guide
ENROLL VIA OM, CM8XXX WEB UI
Nodes can be enrolled into a Lighthouse instance on OPERATIONS MANAGER Web UI using the CONFIGURE > LIGHTHOUSE ENROLLMENT menu item and the lhvpn-callhome command. More details are available in the related Opengear appliance manuals.
ENROLL VIA ACM AND IM WEB UI
On the Web UI, select Serial & Network > Lighthouse to open the Request Enrollment with Lighthouse Server page.
ENROLLMENT VIA USB DRIVE
An unconfigured device can be enrolled using a USB drive loaded with an enrollment bundle.
DOWNLOAD THE ENROLLMENT BUNDLE
1. In the Menu Pane, select Node Tools > Enrollment Bundles. The ENROLLMENT BUNDLES page displays with a list of existing enrollment bundles.
2. On the row of the required bundle, click the icon to download . Depending on the browser's configuration, a manifest.og file either downloads to the local system or displays a dialog asking to specify where to download the file.
ENROLLMENT VIA USB
1. Copy manifest.og to the root directory on a USB drive. 2. Plug the USB drive into an unconfigured and powered-down device. 3. Power the device up.
On first boot, the device searches for the file -- manifest.og -- on any USB drives attached to the device and configures the device based on its contents.
24.12.1
Working with Lighthouse Nodes
198
Lighthouse User Guide
MASS ENROLLMENT USING ZTP
For mass node enrollments using ZTP, three new custom DHCP fields are handled by ZTP scripts. These fields contain the URL, Bundle Name and Enrollment Password used in an enrollment which is kicked off after all other ZTP handling is completed. If a reboot is required because of a config file being provided the enrollment starts after the reboot. Otherwise it happens immediately. Here is a sample configuration file for the ISC DHCP Server:
option space opengear code width 1 length width 1; option opengear.config-url code 1 = text; option opengear.firmware-url code 2 = text; option opengear.enroll-url code 3 = text; option opengear.enroll-bundle code 4 = text; option opengear.enroll-password code 5 = text; class "opengear-config-over-dhcp-test" { match if option vendor-class-identifier ~~ "^Opengear/"; vendor-option-space opengear; option opengear.config-url "http://192.168.88.1/config.xml"; option opengear.enroll-url "192.168.88.20"; option opengear.enroll-bundle ""; option opengear.enroll-password "default"; }
Note: The maximum amount of data allowable as DHCP options is 1200 bytes, including all overhead inherent in the structuring of this data. Individual options are limited to 255 characters.
24.12.1
Working with Lighthouse Nodes
199
Lighthouse User Guide
MANAGE NODES
After a node is enrolled, you can connect to it directly, either to monitor it, or to run commands on it, multiple nodes can be selected. Lighthouse allows you to manage all nodes. Nodes displays the status and number of all the ports on Lighthouse, which you have permissions to view/edit.
VIEW ALL NODES
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. To display nodes with an enrollment that has been initiated, select the PENDING tab.
FILTER NODES
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected. The following options are available: l Filter Nodes: create and save a new filter or select / edit an existing filter. l Enter a search term to filter the results. The AND operator is used if more than one search term is entered. To enter a multi word search phrase, enclose them in double quotes.
ASSIGN OR REMOVE A NODE TAG
Note: The following steps apply to enrolled nodes only.
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Click the Edit Node Tags icon. The ADD/EDIT TAGS dialog displays.
24.12.1
Working with Lighthouse Nodes
200
Lighthouse User Guide
3. Complete one of the following actions: l Create a new tag: a. Click Create new tag. A new row displays. b. Select a tag name. c. Select a tag value l Remove an assigned tag: a. Select Remove tag for the specific tag. The tag is removed from the list.
4. Click Apply.
APPROVE PENDING NODES
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Select the PENDING tab. 3. Perform one of the following actions:
l Individually: use the icon located in the right hand column to apply the action. l Multiple: use the 'checkboxes' to multi-select nodes and select Approve Selected. A Nodes approved message displays.
UNENROLL NODES
Note: If you want to unenroll a node(s) that is running IP Access, it is recommended to push the Disable IP Access template to the node BEFORE you unenroll otherwise the VPN may still form a connection. See Disable NetOps Modules via Template.
24.12.1
Working with Lighthouse Nodes
201
Lighthouse User Guide
FOR A NODE THAT HAS BEEN ENROLLED
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Select the check boxes for any nodes you want to unenroll. 3. Click Unenroll Selected.
A confirmation dialog displays. 4. Click Remove.
FOR A NODE THAT IS PENDING APPROVAL
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Select the PENDING tab. 3. Perform one of the following actions:
l Individually: click the icon located in the right\-hand column to apply the action. l Multiple: select the check boxes to multi-select nodes and then click Unenroll Selected. A confirmation dialog displays. 4. Click Remove.
CONNECT TO THE WEB-MANAGEMENT INTERFACE OF A NODE
After a node is enrolled, you can connect to the web-management interface for the enrolled node.
CONNECT FROM THE DASHBOARD
1. In the Menu Pane, select Dashboard. The NODES grid displays defaulted to the DISCONNECTED tab.
2. Select the CONNECTED tab.
24.12.1
Working with Lighthouse Nodes
202
Lighthouse User Guide
3. You can click the Access Web UI icon on the right of a connected node to access the Web UI of the node. The web-based login for that node loads.
4. Enter credentials and login.
Tip: A message displays at the bottom of the browser and provides a link to return to Lighthouse.
Note: The appearance of the Web UI depends on which device you have added.
CONNECT FROM THE NODES PAGE
You can access the WEB UI from the ENROLLED grid. For the required node, select the icon from the right hand column. 1. In the Menu Pane, select Nodes.
The NODES page displays with the ENROLLED tab selected. 2. Select the CONNECTED tab. 3. You can click the Access Web UI icon on the right of a connected node to access the Web
UI of the node. The web-based login for that node loads. 4. Enter credentials and login.
CONNECT TO THE SERIAL PORTS FOR A NODE
You can connect to the serial ports for the enrolled node via the Console Gateway option on the user interface if required. This allows the user to directly connect to any devices that are connected to the serial ports of the selected node.
24.12.1
Working with Lighthouse Nodes
203
Lighthouse User Guide
FROM THE NODES PAGE
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Use the Filter Nodes options to limit the displayed nodes. 3. Click the NODE NAME to connect to the serial ports for that node.
The Node Details page displays with the PORTS tab selected. This tab displays all the configured and unconfigured ports on the node. 4. Use the Web Terminal Access or SSH icons to access a particular port.
FROM THE PORTS PAGE
1. In the Menu Pane, select Ports. The PORTS page displays and shows all the ports on the connected nodes.
2. To find the port, use the Filter Ports or Filter Nodes options to restrict the listed resources within enrolled nodes.
3. Use the Web Terminal Access or SSH icons to access a particular port.
CONNECT VIA SSH AND CHANGING THE DELIMITER CHARACTER
When connecting with SSH, some web browsers associate the colon character with delimiting the protocol at the beginning of a URI so they don't pass these auto-generated URIs correctly. To work around this, the default delimiter character can be changed. To change this character: 1. In the Settings Pane, select > SERVICES > Console Gateway.
The CONSOLE GATEWAY page displays. 2. Enter a delimited character in the Console Gateway Port Delimiter.
The carat, ^, is the most common alternative.
24.12.1
Working with Lighthouse Nodes
204
Lighthouse User Guide
Note: The auto-generated link default delimiter is ':'. URI syntax ssh://username:console-server-name:port-number@lighthouse-ip-address
3. Select the Console Gateway SSH Address to choose an address from which to SSH.
Note: The list of available addresses contains the current network interfaces and external network addresses. The value defaults to net1:dhcp if it exists and net1:static otherwise. The additional external addresses can be added to this list using the > SYSTEM> Network Settings page.
EXAMPLE SSH SESSION
$ ssh adminuser:serial@lighthouse-name-or-ip-here 1: cm71xx Connect to remote > 1 1: Cisco Console 2: Port 2 Connect to port > 1 router#
CONNECT VIA THE WEB TERMINAL
To provide easy console port access, Lighthouse includes an HTML5 Web Terminal. The HTML5 Web Terminal includes native cut, copy, and paste support. 1. Locate the particular port from the Nodes or the Ports page. 2. Click the Web Terminal Access icon for the port.
The WEB TERMINAL page displays. 3. Use alt-x to return to navigation.
24.12.1
Working with Lighthouse Nodes
205
Lighthouse User Guide
SELECT NODES USING SHELL-BASED TOOLS
There are a number of ways to select nodes, also known as console servers, as targets on which to run a command. These can be used multiple times, or together, to select a range of console servers.
SELECT NODES
Select individually by name, address, Lighthouse VPN address, config index or smart group (as per --list- nodes output):
node-command --node-name BNE-R01-IM4248 node-command --node-address 192.168.0.33 node-command --node-index nodes-1 node-command --smartgroup="model-acm"
To select all nodes:
node-command --all
RUN COMMANDS ON SELECTED NODES
When nodes are selected, the commands to be run for each can be given. These are run on each managed node in parallel. Any command that can be run from a node shell can be run on each managed node.
Note: All commands are run as root.
For example, to check the version on two specific, configured nodes, selecting one by name and the other by index, run the following command:
24.12.1
Working with Lighthouse Nodes
206
Lighthouse User Guide
node-command --node-name BNE-R01-ACM7004-5 --node-index nodes-2 cat /etc/version
When using non-trivial selection arguments, check which target nodes have been selected on the initial command pass by using the --list-nodes switch rather than the final command.
UPGRADE NODES VIA THE UI
When you are required to upgrade nodes to the latest firmware, for example, for security fixes, use the Lighthouse UI to upgrade up to 5000 connected nodes per task. You can upgrade nodes either immediately or at a scheduled time, outside normal business hours. From the main menu, select Node Tools > Firmware Upgrade. Completed jobs with the nodes selected can be duplicated so as to allow easy sequential upgrades. Nodes that failed to upgrade can be re-scheduled. On opening the FIRMWARE UPGRADE page there are two tabs accessible, plus a Schedule Upgrade button, these are: l Upgrade Tasks: A filtered dashboard where you can view scheduled, in progress and
completed tasks and see their status. l File Manager: An area that allows upgrade files to be uploaded and a table that displays
previously uploaded files. l Node Firmware Upgrade scheduling wizard: This is where you can set up and schedule
firmware upgrades. The wizard is accessed by clicking on the + button in the Upgrade Tasks tab. Completed jobs with the nodes selected can be duplicated so as to allow easy sequential upgrades. Nodes that failed to upgrade can be re-scheduled.
FIRMWARE FILES
Before you upgrade, ensure that you have access to the required firmware file.
24.12.1
Working with Lighthouse Nodes
207
UPLOAD A FIRMWARE FILE
Lighthouse User Guide
Note: Only one file may be uploaded at a time using the upload tool. If multiple files are selected and placed in the drag and drop field, only the last file that was selected is uploaded.
1. In the Menu Pane, select > Node Tools > Firmware Upgrade. The FIRMWARE UPGRADE page displays with the UPGRADE TASKS tab selected.
2. Select the FILE MANAGER tab. 3. Complete one of the following actions to select the file:
l Click select file to select the file. l Drag and drop the file into the upload area. The file starts uploading and progress is displayed in the panel. Click the button to cancel in-progress uploads . If you close the website or if the HTTPS connection to Lighthouse is closed, the upload is cancelled.
DELETE A FIRMWARE FILE
To delete a firmware file that is no longer required: 1. In the Menu Pane, select > Node Tools > Firmware Upgrade.
The FIRMWARE UPGRADE page displays with the UPGRADE TASKS tab selected. 2. Select the FILE MANAGER tab. 3. Click the Delete button next to the firmware file you want to delete.
The Confirm Node Firmware Deletion dialog displays. 4. Click Remove.
24.12.1
Working with Lighthouse Nodes
208
Lighthouse User Guide
Note: If the selected firmware file is required by an ongoing or upcoming firmware upgrade task, an error message displays and the file is not deleted.
NODE UPGRADE TASKS
To upgrade a node you must set up a task.
CREATE AN UPGRADE TASK
The Node Upgrade UI is available in the Web UI under Node Tools > Node Firmware Upgrade. Use the UPGRADE TASKS tab to: l Upgrade a node l Schedule a node upgrade l Upload a new firmware file To upgrade a node use the task information table: 1. Click the Schedule Upgrade button (+) to schedule an upgrade (or start one immediately).
The Node Firmware Upgrade wizard displays. 2. Enter a name for the upgrade task. 3. Click the Select File button in the SELECT FIRMWARE pane.
The Select Firmware list displays. 4. Select the firmware or upload new firmware for the upgrade task. Click Select Firmware
button. Note that in the next step you must select the nodes to be upgraded with the firmware. The list of available and compatible nodes display in the Select Nodes pane. Note the messages in the Select Firmware pane. You can also use the Filter Nodes list to find the
24.12.1
Working with Lighthouse Nodes
209
Lighthouse User Guide
exact nodes you want to upgrade.
Note: Compatible nodes that have already been scheduled for an upgrade cannot be selected, these are visible in the list but appear greyed-out. Nodes that are not compatible with the firmware file are not listed.
5. Select the node(s). Click Next - Schedule Upgrade button. The page displays the Start Time pane and the nodes scheduled for upgrade.
6. Select the Start time as either Immediately after creation for immediate start, or, Set time. For Set Time, enter the Scheduled time Date and Time.
Note: The scheduled time is always in UTC.
7. Use the Allow/Disallow toggle to choose whether nodes can upgrade in failover mode or not. 8. Click Next Review and Confirm to go to the review screen. Check the schedule details are
correct.
Note: To change schedule details, click Back Schedule Upgrade, all local data is preserved while you change parameters on previous screens.
9. Select Confirm, and type Yes at the prompt, then click Confirm to create the task. If successful, a message displays that the task is created.
CANCEL AN UPGRADE TASK
You can cancel a task that has not yet completed the upgrade. To cancel an upgrade task: 1. In the Menu Pane, select Node Tools> Firmware Upgrade.
The FIRMWARE UPGRADE page displays with the UPGRADE TASKS tab selected. 2. In the task list, select the task name you want to cancel.
24.12.1
Working with Lighthouse Nodes
210
Lighthouse User Guide
The Task Details screen displays. 3. Click the X button (top-right) to cancel the task.
Note: You cannot cancel upgrade tasks that are already completed.
Limitations: l Do not cancel an upgrade job just as it is about to begin, for example, 10 seconds before or
after the start time. l If an upgrade is canceled while in progress, only nodes that have not yet upgraded are
canceled.
COPY A SCHEDULED TASK
You can copy a scheduled task to create a new upgrade task. The new upgrade task uses the nodes that were selected for the original task you are copying, for example to add or remove nodes from the list. You can also select different firmware or use the same firmware for the list of nodes.
Note: For a task to be copied, the task must have already run or been cancelled, and display an Upgrade Status of Completed.
1. In the Menu Pane, select Node Tools> Firmware Upgrade. The FIRMWARE UPGRADE page displays with the UPGRADE TASKS tab selected.
2. Select the task you want you copy, by clicking the task name in the task table. 3. Click the Copy button to copy the task.
A new task is created with the same nodes.
24.12.1
Working with Lighthouse Nodes
211
Lighthouse User Guide
DELETE AN UPGRADE TASK
Upgrades cannot be permanently deleted as they can offer a valuable insight into the health of the nodes when problem-solving and provide the version path that they have traversed over their lifetime. If the number of jobs is becoming unmanageable, or jobs must be deleted for security measures, the support team can advise on how to remove/clear them.
RETRY AN UPGRADE TASK
If an upgrade task fails, you can retry the node upgrades, provided the firmware file is still available. 1. In the Menu Pane, select Node Tools> Firmware Upgrade.
The FIRMWARE UPGRADE page displays with the UPGRADE TASKS tab selected. 2. Select the task you want to retry, by clicking the task name in the task table.
You can filter the task list by using the Completed with Errors filter. 3. In the task detail screen, click the Repeat task button.
Note: If the relative Firmware file has been deleted, the Repeat task button is disabled.
The Firmware Upgrade page displays.
NODE UPGRADE RUNTIME BEHAVIOUR
The following describes the behavior of the Node Upgrade tool while performing routine upgrade tasks.
Note: If the connection to the node is interrupted during the upgrade, the upgrade may be cancelled and will fail unless the upgrade was in the final stages and had no requirement for further interaction with Lighthouse. In this scenario Lighthouse may still report the node
24.12.1
Working with Lighthouse Nodes
212
Lighthouse User Guide
upgrade as failed if it was unable to confirm that the upgrade succeeded due to the node being disconnected during the validation period. Failure to upgrade one node does not affect other nodes in the upgrade job.
PROMOTE A SECONDARY INSTANCE TO PRIMARY
l All scheduled upgrades are cancelled when a secondary node is promoted to be the new primary node.
l Firmware files are not replicated among the multiple instance cluster and must be re-uploaded to the new primary after promotion.
See also Promote a Secondary Instance.
SKIP VERSIONS
If a node is scheduled to be upgraded from 21.03 directly to 22.01 (skipping 21.Q4), it will upgrade the node even if it has been manually upgraded to 21.04 before the scheduled upgrade starts.
Note: Lighthouse does not check or validate the version jumps for nodes, so there is a risk that the upgrade could fail if major versions are being skipped. Skipping versions is not recommended or supported, however, it is not disallowed.
TIME ZONES
Node upgrades can only be initiated or scheduled by an operator with administrator credentials while logged in at the primary lighthouse. The scheduling of the node upgrade is based on the time zone of the primary lighthouse. If the time zone of the primary lighthouse is changed before a scheduled upgrade starts, the schedule time is based on the new time zone. This may result in jobs not running at all, being skipped, ignored, or otherwise running at unpredictable times.
24.12.1
Working with Lighthouse Nodes
213
Lighthouse User Guide
Note: It is recommended that you avoid changing the system time of lighthouse, or its time zone, while jobs are scheduled.
OFFLINE NODES
If a node is offline or otherwise unreachable at the time of upgrade, the node is skipped. If the node is offline there is a one minute buffer before the scheduled upgrade is skipped and Lighthouse reports the node with a failed to upgrade status.
LIGHTHOUSE AVAILABILITY AND STABILITY
Lighthouse must be online and fully booted (preferably for at least a few minutes) before the upgrade starts. It is good practice to have Lighthouse online for a few hours before a node upgrade. This ensures that all the nodes that will be upgraded have re-established their connection and allows time to troubleshoot any issues. Do not attempt to change major Lighthouse settings, especially those involving the network or time zone, when an upgrade is underway or imminent. Do not conduct multiple major operations on nodes simultaneously, for example, do not apply templates to the node while it is being upgraded. Do not login to a node and change settings moments before an upgrade occurs.
Note: If Lighthouse is offline when a scheduled upgrade is due to start, the upgrade is not run.
OPERATIONS NOT SUPPORTED
The following operations are not supported as part of the Lighthouse Node upgrade process:
24.12.1
Working with Lighthouse Nodes
214
Lighthouse User Guide
Operation
Description
Unenroll nodes at upgrade
Unenrolling nodes as they are being upgraded is not supported as this could result in unexpected behavior.
Downgrade versions
Lighthouse does not allow downgrading of nodes, nor does it allow upgrading to an identical version. The node upgrade will skip nodes that are at the upgrade version or later, for example, if upgrading from version 21.03 to 21.04, it will ignore any nodes that are already at 21.04 or 22.01.
BACK UP NODES
Administrative users can enable automatic node backup. Up to 10 backups can be stored on a rolling basis.
Note: Node backup requires node firmware 4.6 or later.
To set up node backup: 1. In the Settings Pane, select > SERVICES > Node Backup.
The NODE BACKUP page displays. 2. To turn on the backup service, select Enabled.
Fields for the configuration of the backup appear. 3. Under Storage:
a. Select the Number of stored backups you want to keep. b. Set the Retention period after unenrollment to None, Forever, or a specific number of
Days. c. Enter the Location you want to store the backup files.
The default is /mnt/nvram/. d. Click Validate to make sure the location exists and has enough space to store them.
24.12.1
Working with Lighthouse Nodes
215
Lighthouse User Guide
4. Under SCHEDULING, configure the start time and cadence of the backups: a. For the Start time select one of the following: l Immediately. l Set Time; this opens editable Date and Time fields. b. Choose how often you want to Repeat the backup, select one of the following: l One Time Only. l Interval and enter the frequency.
5. Click Apply.
Note: You can modify these options by returning to > SERVICES > Node Backup at any time.
MANAGE PORTS
Lighthouse allows you to manage all ports connected to nodes. Ports displays the status and number of all the ports on Lighthouse, which you have permissions to view/edit.
VIEW PORTS FOR ALL NODES
1. In the Menu Pane, select Ports. The PORTS page displays.
VIEW PORT INFORMATION FOR A NODE
1. In the Menu Pane, select Ports. The PORTS page displays.
2. Select the NODE NAME for a node associated with the port. The ports management page displays.
24.12.1
Working with Lighthouse Nodes
216
Lighthouse User Guide
FILTER PORTS
1. In the Menu Pane, select Ports. The PORTS page displays.
2. The following options are available: l Filter Ports: create and save a new filter or select / edit an existing filter. l Filter Nodes: create and save a new filter or select / edit an existing filter. l Predefined filters: Show All, Configured Ports, Unconfigured Ports l Enter a search term to filter the results. The AND operator is used if more than one search term is entered. To enter a multi-word search phrase, enclose them in double quotes.
Note: You can use the search box to filter the ports by port attribute or node name.
CREATE, ASSIGN OR REMOVE A TAG
1. In the Menu Pane, select Ports. The PORTS page displays.
Note: You can also perform the following steps by accessing port information from the Nodes page.
2. Click the Add/Edit Tags icon. The ADD/EDIT TAGS dialog displays.
3. Complete one of the following actions: l Create a new tag a. Click Create new tag. A new row displays. b. Enter a tag name.
24.12.1
Working with Lighthouse Nodes
217
Lighthouse User Guide
l Assign an existing tag a. Click Select existing tag. A new row displays with the option to select an existing tag. b. Select the tag name.
l Remove an assigned tag a. Select Remove tag. The tag is removed from the list.
4. Click Update Tags. The CONFIRM CHANGES dialog displays.
5. Click Confirm.
ACCESS PORT LOGS
The node must be configured to display logs, and the user will have Logging > Port Logging access granted in the permissions set. Either Full Access or Read Only.
ACCESS PORT LOGS FROM THE NODES PAGE
1. In the Menu Pane, select Nodes. 2. Select the NODE NAME for a node that is enrolled and configured.
The ports management page displays. 3. Select the LOGS tab. 4. Select the PORT from the list. 5. Filter the list as required:
l Specify the date range. l Search for a log with a particular text using Filter Log Contents. 6. You can also download the displayed logs, or open a new window to view the logs in more detail.
24.12.1
Working with Lighthouse Nodes
218
Lighthouse User Guide
ACCESS PORT LOGS FROM THE PORTS PAGE
1. In the Menu Pane, select Ports. 2. Select the NODE NAME for a node that is enrolled and configured.
The ports management page displays. 3. Select the LOGS tab. 4. Select the PORT from the list. 5. Filter the list as required:
l Specify the date range. l Search for a log with a particular text using Filter Log Contents. 6. You can also download the displayed logs, or open a new window to view the logs in more detail.
Tip: You can also access the logs via the web terminal and SSH access for a configured device. To view the logs in more detail download the displayed logs, or open a new window.
MANAGE RESOURCES
Lighthouse allows users to manage resources connected to enrolled nodes that have implemented Smart Management Fabric so that resources can avail of client-less network access. The Smart Management Fabric network can be leveraged to allow users to manually add resources that exist on those networks. Users can specify three proxy methods through Lighthouse to provide client-less network access via: l HTTP l HTTPS l SSH
24.12.1
Working with Lighthouse Nodes
219
Lighthouse User Guide
Notes: l To proxy via HTTP or HTTPS to a resource, Lighthouse must be accessed through a
Domain. l Resources can only be used in a Lighthouse that has an appropriate subscription type.
However users can delete and view a resource on all subscriptions.
Operations to manage resources are on the Resources page. As a reminder the Connected Resource Gateway permissions must be set to Full Access as found under the Advanced Features in the Operation Permission table.
VIEW RESOURCES
1. In the Menu Pane, select Resources. The RESOURCES page displays.
FILTER RESOURCES
1. In the Menu Pane, select Resources. The RESOURCES page displays.
2. The following options are available: l Filter Resources: create and save a new filter or select / edit an existing filter. l Connectivity: Any Status, Connected, Disconnected. l Connected: at least one proxy protocol can be connected. l Disconnected: all proxy protocols are disconnected. l Enter a search term to filter the results. The AND operator is used if more than one search term is entered. To enter a multi word search phrase, enclose them in double quotes.
24.12.1
Working with Lighthouse Nodes
220
Lighthouse User Guide
CREATE, ASSIGN OR REMOVE A RESOURCE TAG
1. In the Menu Pane, select Resources. The RESOURCES page displays.
2. Click the RESOURCE NAME. The EDIT RESOURCE dialog displays.
3. Under TAGS, complete one of the following actions: l Create a new tag: 1. Click Create new tag. A new row displays. 2. Enter a name for the New tag. l Assign an existing tag: 1. Click Select existing tag. A new row displays with the option to select an existing tag. 2. Select the Existing tag name. l Remove an assigned tag; select Remove tag. The tag is removed from the list.
4. Click Update Resource.
CONNECT TO A RESOURCE
1. In the Menu Pane, select Resources. The RESOURCES page displays.
2. For a connected resource select an icon in the actions column to access via:
Note: When Smart Management Fabric is disabled, these icons are also disabled.
24.12.1
Working with Lighthouse Nodes
221
Lighthouse User Guide
l HTTP l HTTPS l SSH
Note: For SSH connections Lighthouse will not know the username for the target resource. When selecting SSH, a modal will appear to update the Target Resource Username. You may leave it blank and the user will be prompted to enter the Username when using SSH. This field will default to the Username of the current login session.
For an IP connection there are three different states that the connection can be within. The state can be seen when hovering over each one of the proxy access button for each resource.
Connection State
Description
Pending
When a resource is added for the first time, the state will come back as pending.
Connected
When Lighthouse can validate the connectivity via that specific protocol on the specified port, the hover state displays a timestamp of when the last time it was validated.
Failure
When Lighthouse can not validate the connectivity via that specific protocol on the specified port.
LOGGING
Connected Resource Gateway logging can be found in a file located in /var/log called crg.log. This file captures the following information: l If a Lighthouse user is granted access to a resource via HTTP, HTTPS or SSH. l If a Lighthouse user is rejected access to a resource due to Connected Resource Gateway
permission being set to Deny.
24.12.1
Working with Lighthouse Nodes
222
Lighthouse User Guide
l Unauthenticated users that try to access a resource are sent to an NGINX error page, which is captured in the existing NGINX access logs.
ADD A RESOURCE
Notes: l A user with role permissions including Full Access set for Advanced Features > Connected
Resource Gateway can add a new resource. l The Lighthouse UI does not allow bulk addition of resources and is performed one at a time
through the UI. Users can use the REST APIs to add multiple resources into the catalog. Refer to the /smf_resources/bulk POST request.
To add a new resource: 1. In the Menu Pane, select Resources.
The RESOURCES page displays. 2. Click the New Resource button.
The NEW RESOURCE dialog displays. 3. Enter a Name for the resource. 4. Enter a Network Address. 5. Under Services, select HTTP, HTTPS or SSH and enter the port number for that service.
For example, 80 is the default port for the HTTP service.
Note: When Smart Management Fabric is disabled, these buttons are also disabled.
6. Under TAGS, create, assign or remove a resource tag. 7. Click Add Resource.
24.12.1
Working with Lighthouse Nodes
223
EDIT A RESOURCE
Lighthouse User Guide
Note: The Lighthouse UI does not allow bulk updating of resources and is performed one at a time through the UI. Users can use the REST APIs to update multiple resources into the catalog. Refer to the /smf_resources/bulk PUT request.
1. In the Menu Pane, select Resources. The RESOURCES page displays.
2. Click the RESOURCE NAME of the resource. The EDIT RESOURCE dialog displays.
3. Edit the fields as required. 4. Under TAGS, create, assign or remove a resource tag. 5. Click Update Resource.
DELETE A RESOURCE
1. In the Menu Pane, select Resources. The RESOURCES page displays.
2. Click the RESOURCE NAME of the resource. The EDIT RESOURCE dialog displays.
3. Click the Delete button. A confirmation message displays.
4. Click Delete. The resource is deleted and a success notification displays.
BULK DELETION OF RESOURCES
1. In the Menu Pane, select Resources. The RESOURCES page displays.
24.12.1
Working with Lighthouse Nodes
224
Lighthouse User Guide
2. Select the check box next to each resource that you want to delete. 3. Click the Delete Selected button.
This button displays only after at least one resource is selected. A confirmation message displays. 4. Click Delete. The resource(s) is deleted and a success notification displays.
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: l CRG will be the primary solution moving forward, offering improved scalability, security,
and continued enhancements. l New users should begin with CRG as the recommended option, while existing AG users
are encouraged to migrate to CRG. l AG discovered resources are not automatically accessible on CRG. l To migrate to CRG, you must set up CRG as if you are setting up a new implementation.
Prerequisites: l The external DNS configuration must have the entries to point to the Lighthouse:
l To register in the DNS, ensure that you use the address format: *.crg.your1stlighthouseaddress.com *.crg.your2ndlighthouseaddress.com.
l You only require DNS if you want to proxy the GUI for http/https. l 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.
24.12.1
Working with Lighthouse Nodes
225
Lighthouse User Guide
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: l gets its primary IP address via DHCP, configure the DHCP server to specify the DNS server to use. l 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: l If you are completing these steps for third-party nodes, then you do not require a SMF
template and can skip this step. l 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.
24.12.1
Working with Lighthouse Nodes
226
Lighthouse User Guide
7. Add a resource.
Notes: l 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. l 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.
24.12.1
Working with Lighthouse Nodes
227
Lighthouse User Guide
MANAGING FILTERS AND TAGS
To provide clear and customized access to nodes, Lighthouse uses search expressions called filters which allow properties and user-supplied tags, consisting of a name and value, to be compiled into a search expression. These filters can be applied to Nodes, Ports, and Resources. Lighthouse also supports the management of customized tags that can be applied to Nodes, Ports, and Resources. These tags can be applied within the custom filters.
MANAGE FILTERS
Lighthouse has three types of filters: l Node Filters l Port Filters l Resource Filters These filters can be used to filter results on the Nodes, Ports and Resources pages, and control access to these objects by assigning the filter to a user group.
VIEW FILTERS
To view a list of filters available: 1. In the Settings Pane, select > FILTERS AND TAGS > Filters.
The FILTERS page displays with the NODE FILTERS tab selected. 2. Select the:
l NODE FILTERS tab to display a grid of available filters that you can apply when you view the Nodes page.
l PORT FILTERS tab to display a grid of available filters that you can apply when you view the Ports page.
24.12.1
Managing Filters and Tags
228
Lighthouse User Guide
l RESOURCE FILTERS tab to display a grid of available filters that you can apply when you view the Resources page.
CREATE A NODE FILTER
CREATE FROM THE FILTER MANAGEMENT PAGE
1. In the Settings Pane, select > FILTERS AND TAGS > Filters. The FILTERS page displays with the NODE FILTERS tab selected.
2. At the top of the page, click the New Filter button. The PICK A FILTER TYPE selection displays.
3. Select Node Filter. The NEW NODE FILTER dialog displays.
4. Enter a Node Filter Name. 5. Complete the fields for the filter criteria:
a. From the drop-down, select the Field to search. b. From the drop-down, select the Operator. c. Enter or select the Value to match. 6. To enter additional filter criteria: a. Click Add Criteria.
The Boolean operator displays with AND selected by default, and additional filter criteria display. b. Select the Boolean operator to apply to the filter criterion: l Select AND if the filter must match all values. l Select OR if one or the other of the values must match.
24.12.1
Managing Filters and Tags
229
Lighthouse User Guide
c. Enter or select the additional filter details in Field to search, Operator, and Value.
Note: Click the icon to remove additional search parameters as necessary.
7. Click Add Filter.
CREATE FROM THE NODE FILTER CONTROL
1. In the Menu Pane, select Nodes. The NODES page displays with the ENROLLED tab selected.
2. Click the Filter Nodes control. 3. Click the Select Node Filter drop-down and select New Node Filter.
The filter criteria section displays. 4. Complete the fields for the filter criteria:
a. From the drop-down, select the Field to search. b. From the drop-down, select the Operator. c. Enter or select the Value to match. 5. To enter additional filter criteria: a. Click Add Criteria.
The Boolean operator displays with AND selected by default, and additional filter criteria display. b. Select the Boolean operator to apply to the filter criterion: l Select AND if the filter must match all values. l Select OR if one or the other of the values must match. c. Enter or select the additional filter details in Field to search, Operator, and Value.
Note: Click the icon to remove additional search parameters as necessary.
6. Complete one of the following actions:
24.12.1
Managing Filters and Tags
230
Lighthouse User Guide
l Apply the filter without saving: Click Apply. The filter control updates to show Filter Nodes: New Node Filter * to indicate that a filter is applied but is not saved.
l Save the filter: a. Click the Save node filter icon. The SAVE NODE FILTER dialog displays. b. Enter the Node Filter Name. c. Review / update the filter criteria. d. Click Save and Apply. The filter control updates to show Filter Nodes: <Name of Filter> to indicate that a filter is applied.
Note: This is also available on the Nodes > PENDING tab.
CREATE A PORT FILTER
CREATE FROM THE FILTER MANAGEMENT PAGE
1. In the Settings Pane, select > FILTERS AND TAGS > Filters. The FILTERS page displays with the NODE FILTERS tab selected.
2. At the top of the page, click the New Filter button. The PICK A FILTER TYPE selection displays.
3. Select Port Filter. The NEW PORT FILTER dialog displays.
4. Enter a Port Filter Name. 5. Complete the fields for the filter criteria:
24.12.1
Managing Filters and Tags
231
Lighthouse User Guide
a. From the drop-down, select the Field to search. b. From the drop-down, select the Operator. c. Enter or select the Value to match. 6. To enter additional filter criteria: a. Click Add Criteria.
The Boolean operator displays with AND selected by default, and additional filter criteria display. b. Select the Boolean operator to apply to the filter criterion: l Select AND if the filter must match all values. l Select OR if one or the other of the values must match. c. Enter or select the additional filter details in Field to search, Operator, and Value.
Note: Click the icon to remove additional search parameters as necessary.
7. Click Add Filter.
Note: When filters are assigned to a user group, then the PORT FILTERS tab on the FILTERS page displays the number of user groups to which the filter is assigned. For more information about assigning a filter to a user group, see Create a User Group.
CREATE FROM THE PORT FILTER CONTROL
1. In the Menu Pane, select Ports. The PORTS page displays.
2. Click the Filter Ports control. 3. Click the Select Port Filter drop-down and select New Port Filter.
The filter criteria section displays. 4. Complete the fields for the filter criteria:
24.12.1
Managing Filters and Tags
232
Lighthouse User Guide
a. From the drop-down, select the Field to search. b. From the drop-down, select the Operator. c. Enter or select the Value to match. 5. To enter additional filter criteria: a. Click Add Criteria.
The Boolean operator displays with AND selected by default, and additional filter criteria display. b. Select the Boolean operator to apply to the filter criterion: l Select AND if the filter must match all values. l Select OR if one or the other of the values must match. c. Enter or select the additional filter details in Field to search, Operator, and Value.
Note: Click the icon to remove additional search parameters as necessary.
6. Complete one of the following actions: l Apply the filter without saving: Click Apply. The filter control updates to show Filter Ports: New Port Filter * to indicate that a filter is applied but is not saved. l Save the filter: a. Click the Save port filter icon. The SAVE PORT FILTER dialog displays. b. Enter the Port Filter Name. c. Review / update the filter criteria. d. Click Save and Apply. The filter control updates to show Filter Ports: <Name of Filter> to indicate that a filter is applied.
24.12.1
Managing Filters and Tags
233
Lighthouse User Guide
Note: When filters are assigned to a user group, then the PORT FILTERS tab on the FILTERS page displays the number of user groups to which the filter is assigned. For more information about assigning a filter to a user group, see Create a User Group.
CREATE A RESOURCE FILTER
CREATE FROM THE FILTER MANAGEMENT PAGE
1. In the Settings Pane, select > FILTERS AND TAGS > Filters. The FILTERS page displays with the NODE FILTERS tab selected.
2. At the top of the page, click the New Filter button. The PICK A FILTER TYPE selection displays.
3. Select Resource Filter. The NEW RESOURCE FILTER dialog displays.
4. Enter a Resource Filter Name. 5. Complete the fields for the filter criteria:
a. From the drop-down, select the Field to search. b. From the drop-down, select the Operator. c. Enter or select the Value to match. 6. To enter additional filter criteria: a. Click Add Criteria.
The Boolean operator displays with AND selected by default, and additional filter criteria display. b. Select the Boolean operator to apply to the filter criterion: l Select AND if the filter must match all values. l Select OR if one or the other of the values must match.
24.12.1
Managing Filters and Tags
234
Lighthouse User Guide
c. Enter or select the additional filter details in Field to search, Operator, and Value.
Note: Click the icon to remove additional search parameters as necessary.
7. Click Add Filter.
Note: When filters are assigned to a user group, then the RESOURCE FILTERS tab on the FILTERS page displays the number of user groups to which the filter is assigned. For more information about assigning a filter to a user group, see Create a User Group.
CREATE FROM THE RESOURCE FILTER CONTROL
1. In the Menu Pane, select Resources. The RESOURCES page displays.
2. Click the Filter Resources control. 3. Click the Select Resource Filter drop-down and select New Resource Filter.
The filter criteria section displays. 4. Complete the fields for the filter criteria:
a. From the drop-down, select the Field to search. b. From the drop-down, select the Operator. c. Enter or select the Value to match. 5. To enter additional filter criteria: a. Click Add Criteria.
The Boolean operator displays with AND selected by default, and additional filter criteria display. b. Select the Boolean operator to apply to the filter criterion: l Select AND if the filter must match all values. l Select OR if one or the other of the values must match.
24.12.1
Managing Filters and Tags
235
Lighthouse User Guide
c. Enter or select the additional filter details in Field to search, Operator, and Value.
Note: Click the icon to remove additional search parameters as necessary.
6. Complete one of the following actions: l Apply the filter without saving: Click Apply. The filter control updates to show Filter Resources: New Resource Filter * to indicate that a filter is applied but is not saved. l Save the filter: a. Click the Save resource filter icon. The SAVE RESOURCE FILTER dialog displays. b. Enter the Resource Filter Name. c. Review / update the filter criteria. d. Click Save and Apply. The filter control updates to show Filter Resources: <Name of Filter> to indicate that a filter is applied.
Note: When filters are assigned to a user group, then the RESOURCE FILTERS tab on the FILTERS page displays the number of user groups to which the filter is assigned. For more information about assigning a filter to a user group, see Create a User Group.
EDIT A FILTER
EDIT A FILTER FROM THE FILTER MANAGEMENT PAGE
1. In the Settings Pane, select > FILTERS AND TAGS > Filters. The FILTERS page displays with the NODE FILTERS tab selected.
2. Select the:
24.12.1
Managing Filters and Tags
236
Lighthouse User Guide
l NODE FILTERS tab to edit a node filter. l PORT FILTERS tab to edit a port filter. l RESOURCE FILTERS tab to edit a resource filter. 3. Click the Name of the filter you want to edit. The EDIT FILTER dialog displays for the type of filter. For example, if you clicked the Name of a node filter, the EDIT NODE FILTER dialog displays. 4. Update the name and/or the filter criteria.
Note: You can modify these fields the same way you would in Create a Node Filter, Create a Port Filter, or Create a Resource Filter.
5. Click Update Filter.
EDIT A FILTER FROM THE FILTER CONTROL
1. In the Menu Pane, select: l Nodes to edit a node filter. The NODES page displays with the ENROLLED tab selected. l Ports to edit a port filter. The PORTS page displays. l Resources to edit a resource filter. The RESOURCES page displays.
2. Click the Filter drop-down. Depending on the page, the drop-down is named Filter Nodes, Filter Ports, or Filter Resources.
3. Click the Select Filter drop-down and then select the filter you want to edit. Depending on the page, the drop-down is named Select Node Filter, Select Port Filter, or Select Resource Filter.
24.12.1
Managing Filters and Tags
237
Lighthouse User Guide
4. Click the Edit filter icon. The EDIT FILTER dialog displays for the type of filter you want to edit. For example, if you are editing a node filter, the EDIT NODE FILTER dialog displays.
5. Update the name and/or the filter criteria.
Note: You can modify these fields the same way you would in Create a Node Filter, Create a Port Filter, or Create a Resource Filter.
6. Click Save and Apply. The filter control updates to show Filter <Type>: <Name of Filter> to indicate that a filter is applied.
DELETE A FILTER
DELETE A FILTER FROM THE FILTER MANAGEMENT PAGE
1. In the Settings Pane, select > FILTERS AND TAGS > Filters. The FILTERS page displays with the NODE FILTERS tab selected.
2. Select the: l NODE FILTERS tab to delete a node filter. l PORT FILTERS tab to delete a port filter. l RESOURCE FILTERS tab to delete a resource filter.
3. Click the Name of the filter you want to delete. The EDIT FILTER dialog displays for the type of filter. For example, if you clicked the Name of a node filter, the EDIT NODE FILTER dialog displays.
4. Click Delete. The CONFIRM FILTER DELETION dialog displays for the type of filter you want to delete. For port and resources filters, this dialog includes the number of user groups to which the port or resource filter is assigned.
24.12.1
Managing Filters and Tags
238
Lighthouse User Guide
Note: Port and resource filters cannot be deleted while they are assigned to a user group; an error message is displayed. To remove a port or resource filter from a user group, see Edit a User Group.
5. Click Delete. The filter is deleted and a success notification displays.
DELETE A FILTER FROM THE FILTER CONTROL
1. In the Menu Pane, select: l Nodes to delete a node filter. The NODES page displays with the ENROLLED tab selected. l Ports to delete a port filter. The PORTS page displays. l Resources to delete a resource filter. The RESOURCES page displays.
2. Click the Filter drop-down. Depending on the page, the drop-down is named Filter Nodes, Filter Ports, or Filter Resources.
3. Click the Select Filter drop-down and then select the filter you want to delete. Depending on the page, the drop-down is named Select Node Filter, Select Port Filter, or Select Resource Filter.
4. Click the Edit filter icon. The EDIT FILTER dialog displays for the type of filter you want to delete. For example, if you are deleting a node filter, the EDIT NODE FILTER dialog displays.
5. Click Delete. The CONFIRM FILTER DELETION dialog displays. For port and resources filters, this dialog includes the number of user groups to which the port
24.12.1
Managing Filters and Tags
239
Lighthouse User Guide
or resource filter is assigned.
Note: Port and resource filters cannot be deleted while they are assigned to a user group; an error message is displayed. To remove a port or resource filter from a user group, see Edit a User Group.
6. Click Delete. The filter is deleted and a success notification displays.
MANAGE TAGS
Lighthouse has two types of tags l Node Tags: can be assigned to a node, and consist of a name and a value l Resource Tags: can be assigned to Ports and Resources, and consist of only a name. Both types of tags can be used in filters.
VIEW TAGS
The Tags page displays the status and number of all the resources on Lighthouse, which you have permissions to view/edit. To view a list of tags available: 1. In the Settings Pane, select > FILTERS AND TAGS > Tags.
The TAGS page displays with the NODE TAGS tab selected. 2. Select the:
l NODE TAGS tab to display a grid of available node tags. l RESOURCE TAGS tab to display a grid of available resource tags.
24.12.1
Managing Filters and Tags
240
Lighthouse User Guide
CREATE A NODE TAG
1. In the Settings Pane, select > FILTERS AND TAGS > Tags. The TAGS page displays with the NODE TAGS tab selected.
2. Click the New Tag button. The PICK A TAG TYPE selection displays.
3. Select Node Tag. The NEW NODE TAG dialog displays.
4. Enter a Name for the tag. 5. Enter a Value for the tag. 6. To add additional values, click the Add Value button and then enter the additional Value. 7. Click Add Tag.
CREATE A RESOURCE TAG
1. In the Settings Pane, select > FILTERS AND TAGS > Tags. The TAGS page displays with the NODE TAGS tab selected.
2. Select the RESOURCE TAGS tab. 3. Click the New Tag button.
The PICK A TAG TYPE selection displays. 4. Select Resource Tag.
The NEW RESOURCE TAG dialog displays. 5. Enter a Name for the tag.
Note: Add more than one name at a time by separating each name with a comma.
6. Click the Add Tag button.
24.12.1
Managing Filters and Tags
241
Lighthouse User Guide
EDIT A TAG
1. In the Settings Pane, select > FILTERS AND TAGS > Tags. The TAGS page displays with the NODE TAG tab selected.
2. Select the: l NODE TAGS tab to edit a node tag. l RESOURCE TAGS tab to edit a resource tab
3. Click the NAME of the tag you want to edit. The EDIT TAG dialog displays for the type of tag you want to edit. For example, if you clicked the NAME of a node tag, the EDIT NODE TAG dialog displays.
4. Complete the following actions as required: l For a node tag: l Update the Name. l Update the Value. l To add additional values, click the Add Valuebutton and then enter the additional Value. l To remove any values click the icon next to the Value you want to remove. l For a resource tag: Update the Name.
5. Click Update Tag.
DELETE A TAG
1. In the Settings Pane, select > FILTERS AND TAGS > Tags. The TAGS page displays with the NODE TAGS tab selected.
2. Select the: l NODE TAGS tab to delete a node tag. l RESOURCE TAGS tab to delete a resource tab
24.12.1
Managing Filters and Tags
242
Lighthouse User Guide
3. Click the NAME of the tag you want to delete. The EDIT TAG dialog displays for the type of tag you want to delete. For example, if you clicked the NAME of a node tag, the EDIT NODE TAG dialog displays.
4. Click Delete. A confirmation message displays.
5. Click Delete. The tag is deleted and a success notification displays.
24.12.1
Managing Filters and Tags
243
Lighthouse User Guide
MANAGING LIGHTHOUSE USERS
Lighthouse supports locally defined users, and remote users who are authenticated and authorized by Authentication Authorization Accounting (AAA) systems such as LDAP, Radius, and TACACs+. Group membership can either be defined locally for local users or defined on the AAA server. Groups that are assigned by the AAA servers must still exist locally.
ROLE DESCRIPTION
Users must be members of one or more groups. Each group has a role assigned to it which controls the level of access that group members have to the system.
The predefined system roles are:
Role
Description
LighthouseAdmin
The Lighthouse Administrator role is assigned to groups whose members are required to manage and maintain Lighthouse. Members have access to all data on the Lighthouse system and create and manage custom groups with custom permission sets.
NodeAdmin
The Node Administrator role is assigned to groups that are required to manage and maintain a set of Nodes. Each group with the Node Administrator role must have an associated Node Filters which is evaluated to define the set of nodes that the group members have access to.
NodeUser
The Node User role is assigned to groups that require access a set of nodes. Each group with the Node User role must have an associated Node Filters which is evaluated to define the set of nodes that the group members have access to. Optionally, access to the resources can be limited by associating the saved Resource Filter with the Node User role.
Reporter
The Reporter role is assigned to groups that require just read-only access across the system permission sets.
24.12.1
Managing Lighthouse Users
244
Lighthouse User Guide
MANAGE USER GROUPS
User groups are used to grant permissions to users that are assigned to them. To add permissions to a user group, you must create a role and then assign that role to the group. For certain actions, such as accessing a port or a resource, the access of users in the group can be limited by associating filters with the group. Users only have access to objects that are matched by their associated filters. l A user may be a member of multiple groups, the permissions from those groups add to get the
permissions of the user. l Group membership can either be defined locally for local users or defined on the AAA server.
Groups that are assigned by the AAA servers must still exist locally.
CREATE A USER GROUP
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Click Add User Group to the right of the page filter control. The NEW GROUP page displays.
3. Select Enabled to enable group. 4. Enter a group Name and Description.
Note: Group Name is case sensitive. It can contain numbers and some alphanumeric characters. When using remote authentication, characters from a user's remote groups that are not allowed on Lighthouse are converted to underscores during authentication. Local groups can be created that take that into account, allowing the authentication to continue.
5. Under ACCESS CONTROLS:
24.12.1
Managing Lighthouse Users
245
Lighthouse User Guide
a. Select a filter from the By Node Filter control to restrict access to nodes that match the selected filter. If you do not select a filter, users can access all nodes.
b. Select a filter from the By Port Filter control to restrict access to ports that match the selected filter. If you do not select a filter, users can access all ports.
c. Select a filter from the By Resource Filter control to restrict access to resources that match the selected filter. If you do not select a filter, users can access all resources.
Note: Any filters selected here when you create the user group, display under ACCESS CONTROL when you view the existing user group later.
6. Under ROLES, manage the roles assigned to the group: l To add a role: a. Click Add Role. The ADD ROLES dialog displays. b. Select the check boxes for the roles you want to add. Click the NAME of each role to view the details of the role and the OPERATION PERMISSIONS associated with the role. Click < Back to return to the ADD ROLES dialog. c. Click Add. l To remove a role, click the icon for the role. The role is removed. l Each role has specific operation permissions associated with it and CLI (Command Line Interface) access levels for Console Shell Access Level, Shell Access, and PM Shell Access. l Click View details to see the information for each group
1. Review the PERMISSIONS SUMMARY section. This section displays how CLI permissions are derived based on the selected roles.
2. Review the OPERATION PERMISSIONS section. This section displays how operation permissions are derived based on the selected roles.
24.12.1
Managing Lighthouse Users
246
3. Click Apply.
AVAILABLE ROLES
Role Lighthouse Administrator
Lighthouse User Guide
Description
Members of groups with this role have Full access to all nodes resources. The following applies to the group filters: l The filters are set to All Nodes and Port Filter set to All Ports. This cannot
be changed. l Conversely if a group's node filter is All Nodes and Port Filter is All Ports
you can not set the group's role Lighthouse Administrator.
Note: When a new group is given the Lighthouse Administrator role, members of the group have access to the sudo command. Groups or users with the Lighthouse Administrator role are added to the admin group, which is in the list of allowed sudoers. On first boot of a new Lighthouse instance, the root user is the only member of the admin group and the only user with sudo access.
NodeAdmin NodeUser Lighthouse Reporter
Has no shell access. Has Read Only access to Netops modules, all Nodes & Configuration Operations, Cell Health, Node Filters, Tags, and Jobs
Has PM Shell access. Has Read Only access to Nodes & Devices (Base) and Tags.
Has no shell access. Has Read Only access to all Operations.
24.12.1
Managing Lighthouse Users
247
Lighthouse User Guide
CREATE A USER GROUP FROM AN EXISTING GROUP
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Click the name of the group that you want to use as a template. The VIEW USER GROUP page displays.
3. On the top-right of the page, click Use as Template. The NEW GROUP page displays and populates the form with the same values as the selected group, except for the name.
4. Enter the new group Name. 5. Review and modify the remaining fields as required.
Note: You can modify these fields the same way you would in Create a User Group.
6. Click Apply.
EDIT A USER GROUP
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Click the NAME of the user group you want to edit. The VIEW USER GROUP page displays.
3. Click Edit. The EDITING GROUPS page displays.
4. Review and modify the details as required.
Note: You can modify these fields the same way you would in Create a User Group.
5. Click Apply.
24.12.1
Managing Lighthouse Users
248
Lighthouse User Guide
Note: The netgrp group is inherited as the primary group for all remote AAA users who are not defined locally on Lighthouse. By default, netgrp is disabled - it must be enabled to take effect for remote AAA users.
DELETE A USER GROUP
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Click the NAME of the group you want to delete. The VIEW USER GROUP page displays.
3. On the top-right of the page, click Delete Group. The CONFIRM GROUP DELETION dialog displays.
4. Click Delete.
MANAGE ROLES
A user is added to a user group for which one or many roles are assigned. Roles are used to configure the level of permissions to the CLI and the set of features to which a user has access.
24.12.1
Managing Lighthouse Users
249
Lighthouse User Guide
CLI PERMISSIONS REFERENCE
Permission Console Shell Access Level
Shell Access PM Shell Access
Options
Description
Admin | Standard | Disabled
Ability to connect to nodes' command lines via Lighthouse's SSH.
Standard allows access the node's console with the same username as the Lighthouse user, if the user has an existing user account of the same name on the node. The user will be asked for the password of their account on the node whilst connecting.
Admin will access the node's console as the node's root user. Lighthouse will authenticate the connection to the node using it's own ssh key, the user will not have to enter a password.
Enabled | Disabled
Ability to access the Lighthouse command line as an administrator.
Enabled | Disabled
Ability to connect to serial ports via SSH.
OPERATION PERMISSIONS REFERENCE
Feature Set Actions
Feature Events
Description
Ability to enable or disable if events are used to generate notifications.
Subscriptions
Ability to manage third-party access to events.
Logging
Port Logging
Currently allows access to delete port logs through the API. Other port logging functionality is currently available through the CLI on Lighthouse. Any additional API port logging functionality will be accessible via this permission.
24.12.1
Managing Lighthouse Users
250
Lighthouse User Guide
Feature Set
Netops Advanced Features
Nodes and Configuration
Feature
Description
Syslog
Allows managing the system syslog settings through the /system/logging endpoint, currently this functionality is not available via the UI. There is another permission (Services > Syslog) which allows the user to setup remote syslog servers for Lighthouse to send logs to.
Netops Modules
Allows configuring Netops modules, this includes the ability to use each module, set each module to always deploy, and redeploy modules. Installing and updating the modules is handled under the Services > NetOps permission.
Smart Management Fabric
Allows enabling Smart Management Fabric on Lighthouse and setting the internal area ID.
Enabling this permission requires "Multiple Instance".
Enabling Smart Management Fabric on the nodes requires the Nodes and Configuration > Template Push permission.
Configuring the Smart Management Fabric Network Range on the Lighthouse VPN, requires "Full Access" on Services > LHVPN.
Connected Resource Gateway
Allows managing resources through Connected Resource Gateway. To read or change tags on resources, you require the appropriate level on Tags. To read or change resource filters, you require the appropriate level on Filters.
Nodes and Devices (Base)
Access to dashboard, nodes, ports, node enrollment and node web UI.
Read Only will allow you to view nodes and ports, make searches for ports, and view node and port filters.
Full Access will allow you to do Lighthouse driven node enrollments, and approve nodes that are in a pending state. You can also unenroll nodes.
24.12.1
Managing Lighthouse Users
251
Lighthouse User Guide
Feature Set Service Settings
Feature
Description
Nodes and Devices (Advanced)
Extends Nodes and Devices (Base) permissions.
Read Only allows access to cell health information, and node connection information.
Full Access allows for changing the subscription associated with a node.
Nodes and Firmware Management
Ability to manage node firmware uploads and schedule node upgrades.
Template Push
Ability to push templates to nodes and manage templates.
LHVPN
Cell Health
Console Gateway
Custom Login Message
Access to set the custom login message:
l Read-Only allows the user to see the CUSTOM LOGIN MESSAGE tab, but they cannot add, update, delete, enable, or disable the custom login message.
l Full Access allows the user to add, update, delete, enable, or disable the custom login message.
By default, the Lighthouse Admin role receives Full Access and the Reporter role receives Read-Only access. When a custom login message is enabled, it is visible to all visitors to the Lighthouse login page prior to logging in.
Date & Time
24.12.1
Managing Lighthouse Users
252
Feature Set
Filters and Tags System
Feature HTTPS Netops Node Backup Session Settings
SNMP SSH Syslog Bundles Filters Tags Admin and Subscriptions
Description
Lighthouse User Guide
Ability to install Netops modules and modify local Netops repositories.
Access to set idle timeouts for the Web UI and CLI sessions and enable or disable the alternate API port status:
l Read-Only allows the user to see the relevant settings, but they cannot make changes to them.
l Full Access allows the user to update the relevant settings.
By default, the Lighthouse Admin role receives Full Access and the Reporter role receives Read-Only access.
Ability to manage bundles.
Allows for the management and use of filters.
Allows for the management and use of tags.
Ability to manage access settings for Lighthouse and manage subscription details.
24.12.1
Managing Lighthouse Users
253
Feature Set
User and Permissions
Feature Backup and Restore Jobs Multi-instance Network Settings
System Upgrade and Reset Authentication Group and Roles Users
Description
Lighthouse User Guide
Ability to manage multi-instance settings and control state of instances
Ability to manage the settings on the NETWORK SETTINGS page: l Read-Only allows the user to view the tabs for the
primary and secondary Lighthouses but they cannot edit the content. l Full Access allows the user to add, update, delete network connections and network interface settings, as well as edit the hostname, direct access port configuration and external network addresses. By default, the Lighthouse Admin role receives Full Access and the Reporter role receives Read-Only access.
Ability to manage authentication settings including methods of authentication, policy and restrictions.
Ability to create and edit roles and groups, but not the ability to assign them to users.
Ability to view and manage users, including creation and removal of users.
24.12.1
Managing Lighthouse Users
254
Lighthouse User Guide
CREATE A ROLE
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Select the ROLES tab. 3. To the right of the page filter control, click Add User Role .
The NEW ROLE page displays. 4. Enter a role Name. 5. Enter a role Description. 6. Under CLI PERMISSIONS, modify the permissions:
a. Set the Console Shell Access Level to Admin, Standard, or Disabled to determine the level of ability to connect to nodes' command lines via Lighthouse's SSH.
b. Select Enabled or Disabled for each of the following: l Shell Access: Ability to access the Lighthouse command line as administrator. l PM Shell Access: Ability to connect to serial ports via SSH.
Note: For more information about CLI permissions, see CLI Permissions Reference.
7. Under OPERATION PERMISSIONS, modify the permissions to specify the access level for each feature: a. Click to expand the FEATURE SET. b. For each FEATURE listed, select the access level to apply for the role: FULL ACCESS, READ ONLY, or DENY.
Note: The default access level is set to DENY.
24.12.1
Managing Lighthouse Users
255
Lighthouse User Guide
Note: For more information about operation permissions, see Operation Permissions Reference.
8. Click Apply.
CREATE A ROLE FROM AN EXISTING ROLE
A new role can also be based on an existing role with the Use as template link on the upper right of the detail page for a role. 1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles.
The GROUPS and ROLES dashboard displays with the USER GROUPS tab selected. 2. Select the ROLES tab. 3. Click the name of the role you want to use as a template. 4. On the top-right of the page, click Use as template.
The NEW ROLE page displays and populates the form with the same values as the selected role, except for the name. 5. Enter the new role Name. 6. Review and modify the remaining fields as required.
Note: You can modify these fields the same way you would in Create a Role.
7. Click Save Role to create the new role.
EDIT A ROLE
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Select the ROLES tab.
24.12.1
Managing Lighthouse Users
256
Lighthouse User Guide
3. Click the NAME of the role you want to edit. The VIEW ROLE page displays.
4. Click Edit. The EDITING ROLE page displays.
5. Review and modify the details as required.
Note: You can modify these fields the same way you would in Create a Role.
6. Click Apply.
DELETE A ROLE
1. In the Settings Pane, select > USERS & ACCOUNTS > Groups and Roles. The GROUPS AND ROLES page displays with the USER GROUPS tab selected.
2. Select the ROLES tab. 3. Click the NAME of the role you want to delete.
The VIEW ROLE page displays. 4. Click Delete Role.
The CONFIRM ROLE DELETION dialog displays. 5. Click Delete.
MANAGE USERS
You can create new users, edit existing users, delete users, and alter groups and permissions. Users can be either local users or remote users, in both instances you must understand how users must be authenticated.
24.12.1
Managing Lighthouse Users
257
Lighthouse User Guide
AUTHENTICATION MODES
Authentication Local
[AAA] - Radius - Tacacs+ - Ldap
Local[AAA] - LocalRadius - LocalTacacs+ - LocalLdap
Password And Group Source
Notes
Authentication: Local only; Groups: Local
All users must exist locally before they can log in.
Authentication: the username/password provided by the user is ONLY tested against the [AAA] server. Groups: Union of the user's local groups and their [AAA] groups.
If the user didn't exist locally and successfully authenticated via [AAA], the user is also added to the netgrp group.
If there is a local user with the same username as the [AAA] user and that user tries to login with the local password, login will be denied UNLESS the local password is the SAME as the remote password, that is, the remote password is used to login.
If the [AAA] server is unreachable, the only user that can authenticate locally is root.
Authentication: The username/password provided by the user is first tested locally and if local authentication fails then the [AAA] server is used. Groups: Union of the user's local groups and their [AAA] groups.
If the user didn't exist locally and successfully authenticated via [AAA], then the user is also added to the netgrp group.
Basically, the user can log in with either their local password (if the user exists locally) or their [AAA] password (if the user exists in the [AAA] server). The main point is that the username/password is tested locally first and if it fails, [AAA] auth is attempted with the same username and password.
24.12.1
Managing Lighthouse Users
258
Authentication [AAA]Local - RadiusLocal - Tacacs+Local - LdapLocal
[AAA]DownLocal - RadiusDownLocal - Tacacs+DownLocal - LdapDownLocal
Lighthouse User Guide
Password And Group Source
Notes
Authentication: The username/password provided by the user is first tested by the [AAA] server and if [AAA] authentication fails then the credentials are tested locally. Groups: Union of the user's local groups and their [AAA] groups.
If the user didn't exist locally and successfully authenticated via [AAA], then the user is also added to the netgrp group.
Basically, the user can log in with either their local password (if the user exists locally) or their [AAA] password (if the user exists in the [AAA] server). The main point is that the username/password is tested by [AAA] first and if it fails, local auth is attempted with the same username and password.
Authentication: Local authentication is ONLY used if the [AAA] server is unreachable. Otherwise [AAA] authentication is always used. Groups: Union of the user's local groups and their [AAA] groups. If the user didn't exist locally and successfully authenticated via [AAA], then the user is also added to the netgrp group.
This should behave exactly the same as the [AAA] mode until the [AAA] server is unreachable at which point, local authentication is attempted.
Note: The root user can be authenticated by AAA but it will always try local auth for the root user first.
CREATE A LOCAL USER
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Click Add User. The NEW USER page displays.
3. Select the User Status. 4. Enter a Username.
24.12.1
Managing Lighthouse Users
259
Lighthouse User Guide
Note: Username must only contain lowercase letters, numbers and _ . -
5. Enter a Description. 6. Enable or disable the Remote Password Only feature.
l Select Enabled for Remote Password Only to use external AAA server for password. l Select Disabled for Remote Password Only to create password for the user.
a. Enter the Password. b. Re-enter to Confirm Password. 7. To add a SSH Key: a. Click Add SSH Authentication Key. The ADD SSH AUTHENTICATION KEY dialog displays. b. Enter the SSH public key for the user. c. Click Add Key. 8. Under the GROUPS section, manage the user groups the user will be assigned. a. Click Add Group, The ADD GROUPS dialog displays. b. With the checkboxes, check groups to add the user to. c. Select the role name to view the details of the role and the operation permissions associated with the role. Click < Back to return to the ADD ROLES dialog. d. Click Add. 9. Review the PERMISSIONS SUMMARY section. This section displays how permissions are derived based on the selected roles for both CLI and OPERATION permissions. 10. Click Apply.
24.12.1
Managing Lighthouse Users
260
Lighthouse User Guide
CREATE USER EVENT LOGS
When a new user is created, an entry is added to the syslog that indicates the name of the new user, the user that performed the operation, database queries, and the time that it occurred:
2020-05-22T16:22:46.490627+01:00 localhost rest_api_log[62]: GET 200 (root | 192.168.1.230) - /api/v3.5/users?page=1&per_page=10 RESPONSE={'users': [{'username': 'root', 'description': 'System wide SuperUser account', 'enabled': True, 'id': 'users-1', 'no_password': False, 'expired': False, 'locked_out': False, 'rights': {'delete': True, 'modify': True}, 'groups': ['groups-2']}, {'username': 'fred', 'description': 'fred', 'enabled': True, 'id': 'users-2', 'no_ password': False, 'expired': False, 'locked_out': False, 'rights': {'delete': True, 'modify': True}, 'groups': ['groups-2']}], 'meta': {'total_pages': 1}}
If the created user is set to disabled, the configurator_users message does not appear as they have not been added to the passwords file. To access the syslog from Lighthouse, click > Generate Technical Support Report.
EDIT A USER
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Click the USERNAME of the user you want to edit. The EDIT USER page displays.
3. Review and modify the details as required.
Note: You can modify these fields the same way you would in Create a Local User.
4. Click Apply.
24.12.1
Managing Lighthouse Users
261
Lighthouse User Guide
Note: Disabled users cannot login to Lighthouse using either the Web-based interface or via shell-based logins (that is sshusername-disabled@lighthouse-name-or-ip). The user and the /home/username-disabled directory still exist in the Lighthouse VM file system.
DISABLE A USER
DISABLE A ROOT USER
Caution: Make sure that another user exists that is in a group that has the Lighthouse Administrator role.
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Click the Disable User icon on the right-hand side of the row for the root user. A confirmation dialog displays with the following message:
Warning This may prevent configuration of the system. Make sure another user exists that is in a group that has the "Lighthouse Administrator" role, before proceeding with this action.
3. Click Confirm. To re- enable the root user, login as another user with Lighthouse Administrator role and enable access for root user from Actions section on Users page. An Identity Provider (IdP) stores and manages users' digital identities An IdP may check user identities via username-password combinations and other factors, or it may simply provide a list of user identities that another service provider (like an SSO) checks. An IdP can authenticate any entity connected to a network or a system, including computers and other devices.
24.12.1
Managing Lighthouse Users
262
Lighthouse User Guide
DISABLE LOCAL USERS
1. In the Settings pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Disable the user(s): l For a single user, click the you want to disable.
Disable User icon on the right-hand side of the row for the user
l For multiple users, select the check box next to each user you want to disable and then click the Disable User icon above the user grid.
The DISABLE USER dialog displays.
3. Enter Your Password to proceed.
4. Click Confirm.
ENABLE A USER
ENABLE A ROOT USER
Note: To re-enable the root user, login as another user with Lighthouse Administrator role and enable access for root user from Actions section on Users page.
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Click the Enable User icon on the right-hand side of the row for the root user. The ENABLE USER dialog displays.
3. Click Confirm.
24.12.1
Managing Lighthouse Users
263
Lighthouse User Guide
ENABLE A SINGLE USER
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Click the Enable User icon on the right-hand side of the row for the user you want to enable. The ENABLE USER dialog displays.
3. Click Confirm.
DELETE A USER
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
2. Delete the user(s): l For a single user, click the Delete User icon on the right-hand side of the row for the user you want to delete. l For multiple users, select the check box next to each user you want to delete and then click the Delete User icon above the user grid. The CONFIRM USER DELETION dialog displays.
3. Enter Your Password to proceed. 4. Click Confirm.
The user(s) is permanently deleted.
UNLOCK A USER
For a user that fails the login restrictions policy and has become locked out, a notification displays with the following message:
24.12.1
Managing Lighthouse Users
264
Lighthouse User Guide
Error Your account has been locked out. Please try again later or contact your administrator.
An administrator can unlock the account with the following steps: 1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users.
The LOCAL USERS page displays. 2. Click the Unlock User icon on the right-hand side of the row for a locked user.
The UNLOCK USER confirmation dialog displays. 3. Click Confirm.
EXPIRE OR RESTORE A USER PASSWORD
EXPIRE A USER PASSWORD
You can set a user password to expire. The next time this user logs in, the user is required to change the password. 1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users.
The LOCAL USERS page displays. 2. Click the Expire Password icon on the right-hand side of the row for the user.
The EXPIRE PASSWORD dialog displays. 3. Enter Your Password to proceed. 4. Click Confirm.
RESTORE A USER PASSWORD
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Users. The LOCAL USERS page displays.
24.12.1
Managing Lighthouse Users
265
Lighthouse User Guide
2. Click the Restore Password icon on the right-hand side of the row for the user with a password set to expired. The RESTORE PASSWORD dialog displays.
3. Click Confirm.
MANAGE LOCAL AUTHENTICATION POLICY
An Identity Provider (IdP) stores and manages users' digital identities. An IdP may check user identities via username-password combinations and other factors, or it may simply provide a list of user identities that another service provider (like an SSO) checks. An IdP can authenticate any entity connected to a network or a system, including computers and other devices. Lighthouse Administrators can set Password Policies to ensure that users set secure passwords.
Note: All password fields in Lighthouse are write-only. They accept data from the clipboard or pasteboard but do not pass data out.
SET THE PASSWORD POLICY
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Authentication Policy. The LOCAL AUTHENTICATION POLICY page displays with the PASSWORD POLICY tab selected.
2. Select Enabled to enable the password policy. 3. Modify the PASSWORD REQUIREMENTS. select the check boxes to enable one or more of
the following options: l Minimum password length. Enter a value from 1 to 128. l Require at least one capital letter. l Require at least one number.
24.12.1
Managing Lighthouse Users
266
Lighthouse User Guide
l Require at least one symbol. l Disallow username in password. l Prevent password reuse. Select Always or Days and set the number of days between
reuse. l Set password expiry. Set the number of days until passwords expire. At next login, the user
must reset the password. 4. Click Apply.
SET THE LOGIN RESTRICTIONS
Login restrictions can be applied by administrator users to prevent unauthorized login attempts via the UI and REST API.
Caution: Enabling login restrictions can cause the system to be inaccessible in an emergency.
1. In the Settings Pane, select > USERS & ACCOUNTS > Local Authentication Policy. The LOCAL AUTHENTICATION POLICY page displays with the PASSWORD POLICY tab selected.
2. Select the LOGIN RESTRICTIONS tab. 3. Select Enabled to enable the login restriction policy. 4. Enter a value for Maximum attempts to set the number of attempts a user can enter an
incorrect password before being locked out. 5. Enter a value for Lockout period to set the number of minutes until a user can try to login again
after reaching maximum incorrect login attempts. 6. Click Apply.
CONFIGURE REMOTE AUTHENTICATION
Lighthouse supports three Authentication Authorization and Accounting (AAA) systems:
24.12.1
Managing Lighthouse Users
267
Lighthouse User Guide
l LDAP (Active Directory and OpenLDAP) l RADIUS l TACACS+ Authentication works much the same with each, but group membership retrieval varies. The following sections detail the configuration settings for each provider and explain how group membership retrieval works.
LDAP CONFIGURATION
1. In the Settings Pane, select > USERS & ACCOUNTS > Remote Authentication. The REMOTE AUTHENTICATION page displays.
2. From the Scheme options, select LDAP. 3. Select the required Mode:
l LDAPDownLocal l LDAP Mode l LocalLDAP l LDAPLocal 4. Enter the Address and optionally the Port of the remote authentication server to query. The port setting defaults to LDAP/LDAPS standard ports if not entered.
Note: Click Add Authentication Server to add multiple servers. The LDAP subsystem queries them in a round-robin fashion.
5. Enter the LDAP Base DN that corresponds to the LDAP system being queried. For example, if a user's distinguished name is cn=John Doe,dc=Users,dc=ACME,dc=com, the LDAP Base DN is dc=ACME,dc=com.
24.12.1
Managing Lighthouse Users
268
Lighthouse User Guide
6. Enter the LDAP Bind DN. This is the distinguished name of a user with privileges on the LDAP system to perform the lookups required for retrieving the username of the users, and a list of the groups they are members of.
7. Enter and confirm the Bind DN Password for the binding user. 8. Enter the LDAP Username attribute . This depends on the underlying LDAP system.
Use sAMAccountName for Active Directory systems, and uid for OpenLDAP based systems. 9. Enter the LDAP group membership attribute.
This is only required for Active Directory and is generally memberOf. 10. If required, check the Ignore referrals option.
When checked, LDAP will not follow referrals to other remote authentication servers when logging users in to Lighthouse. If multiple remote authentication servers exist on the network, checking this option may improve login times. 11. Select the required SSL protocol: l LDAP over SSL preferred: this attempts LDAPS before trying LDAP without SSL. l LDAP (no SSL) only: non-SSL LDAP is always used. l LDAP over SSL only: LDAP over SSL is always used. 12. Check Ignore SSL certificate errors to ignore any SSL certificate errors encountered when accessing LDAPS servers. If this option is checked, a certificate file uploaded will not be used. 13. To UPLOAD CERTIFICATE FILE to validate LDAPS servers, navigate to the directory that contains the appropriate upgrade image file and drag and drop the image onto the target page section or click select file to open a dialog.
Note: Supported files: .crt, .cer, .ca-bundle, .p7b, .p7c, .p7s, .pem, .txt
14. Click Apply.
24.12.1
Managing Lighthouse Users
269
Lighthouse User Guide
RADIUS CONFIGURATION
1. In the Settings Pane, select > USERS & ACCOUNTS > Remote Authentication. The REMOTE AUTHENTICATION page displays.
2. From the Scheme options, select Radius. 3. Select the required Mode:
l RADIUSDownLocal l RADIUS Mode l LocalRADIUS l RADIUSLocal 4. Enter the Address and optionally the Port of the Remote Authentication Server to query. The default port is 1812.
Note: Click Add Authentication Server to add multiple servers.
5. Enter the Address and optionally the Port of the Remote Accounting Server to send accounting information. The default port is 1813.
Note: Click Add Accounting Server to add multiple servers.
6. Enter and confirm the Server Password also known as the RADIUS Secret. 7. Click Apply. To provide group membership, RADIUS must be configured to provide a list of group names via the Framed-Filter-Id attribute. The following configuration snippet shows how this can be configured for FreeRADIUS: operator1 Auth-Type := System Framed-Filter-ID = ":group_name=west_ coast_admin,east_coast_user:"
24.12.1
Managing Lighthouse Users
270
Lighthouse User Guide
Note: The Framed-Filter-ID attribute must be delimited by the colon character.
TACACS+ CONFIGURATION
1. In the Settings Pane, select > USERS & ACCOUNTS > Remote Authentication. The REMOTE AUTHENTICATION page displays.
2. From the Scheme options, select TACACS+. 3. Select the required Mode:
l TACACS+DownLocal l TACACS+Mode l LocalTACACS+ l TACACS+Local 4. Enter the Address and optionally the Port of the Remote Authentication Server to query. The default port is 49.
Note: Click Add Authentication Server to add multiple servers. The TACACS+ subsystem queries them in a round-robin fashion.
5. Select the TACACS+ login methodto set the method used to authenticate to the server. The default selection is PAP. To use DES encrypted passwords, select Login.
6. Enter and confirm the Server Password, also known as the TACACS+ Secret. 7. Enter the TACACS+ service.
This determines which set of attributes are returned by the server. Defaults to "raccess". 8. Click Apply. To provide group membership, TACACS+ must be configured to provide a list of group names. The following configuration snippet shows how this can be configured for a tac_plus server:
24.12.1
Managing Lighthouse Users
271
Lighthouse User Guide
user = operator1 { service = raccess { groupname = west_coast_admin,east_cost_user }
}
To do this with Cisco ACS, see Setting up permissions with Cisco ACS 5 and TACACS+ on the Opengear Help Desk.
CONFIGURE SSH AUTHENTICATION
SSH authentication security settings for all users across all Lighthouses is managed under > USERS & ACCOUNTS > SSH Authentication. To configure SSH Authentication: 1. In the Settings Pane, select > USERS & ACCOUNTS > SSH Authentication.
The SSH AUTHENTICATION SETTINGS page displays. 2. Set the SSH Password Authentication to Enabled to allow using a password for
SSH connections for all users, including the root user.
Note: With Lighthouse version 24.06.0 and later, by default any AWS Lighthouse instance created will have this setting disabled. This setting affects every user account. l If disabled, Lighthouse users must use a SSH key to authenticate SSH connections to
Lighthouse. This can be set under > USERS & ACCOUNTS > Local Users and then configuring per user. l If enabled, then SSH Authentication will be authenticated via their password.
3. Set the SSH connection as Root User to Enabled to allow the root user to SSH into Lighthouse.
24.12.1
Managing Lighthouse Users
272
Lighthouse User Guide
Note: With Lighthouse version 24.06.0 and later, by default any AWS Lighthouse instance created will have this setting disabled. This setting only affects the root user. l If disabled the root user will not be able to use SSH to connect to a Lighthouse
Instance. l If enabled, the root user must still be enabled as well and is done by navigating to
> USERS & ACCOUNTS > Local Users and select Enabled for the root user.
4. Click Apply.
SAML CONFIGURATION FOR SSO
SAML is the framework used to integrate applications with identity providers for single sign-on (SSO). This is mostly (if not completely) reflected when a user logs in and authenticates with their IdP or is already logged in (if they have already authenticated with their identity provider prior to accessing Lighthouse). Lighthouse supports the independent, concurrent use of both SAML and AAA authentication. SAML authentication is independent of, and does not interact with, other authentication methods.
Note: For release 2025.12 SAML is only supported for authentication to the Lighthouse Web GUI.
When SAML is configured and enabled, users can authenticate to the Lighthouse Web GUI either through SAML or another configured authentication mechanism such as Local or AAA. Users can SSH only via the other configured authentication mechanism (Local or AAA) if Remote Authentication is configured. The default authentication is Local, with Lighthouse using locally defined users and groups. If AAA (TACACS, RADIUS or LDAP) Remote Authentication is configured, this will be used for Web GUI and SSH login authentication to Lighthouse (except for root which is always locally authenticated).
24.12.1
Managing Lighthouse Users
273
Lighthouse User Guide
Users are authenticated against AAA server(s) with group membership returned to Lighthouse, which is used to determine user roles and permissions. AAA Remote Authentication can support 2FA/MFA, depending on the AAA server capabilities. Lighthouse's SAML integrates with the following identity providers: l OKTA l Azure Active Directory (Azure AD) l One Login l Auth0
Note: In the following instructions, any text in braces {} for example, {main lighthouse address} must be substituted with the value for your environment.
Common values you will require are: {main lighthouse address} - The address (without the protocol or path) most users use to connect to your primary lighthouse's web interface. e.g. lighthouse.example.com or 192.168.1.10 {provider} - Each IdP implements the spec slightly differently. Lighthouse needs to know which style to expect to handle these differences. If your IdP is not one of our officially supported IdPs, try configuring Lighthouse using the generic provider option as the most widely applicable. (You could also try using our other explicit IdP options but these often expect provider specific intricacies).
GENERIC IDP SETUP
This section describes how to integrate Lighthouse with your generic Identity Provider (IdP) Application. In case Lighthouse's supported IdPs do not include your identity provider, use the Generic IdP setup. This has been made as general as possible to meet expectations of all IdPs in the market today.
24.12.1
Managing Lighthouse Users
274
Lighthouse User Guide
Notes: l You must have your user groups setup in Lighthouse prior creating & assigning them via
the IdP. See the example in step 6 of the Okta configuration later in this topic. l The {provider} in the steps must exactly match one of our provider strings that is, gen-
eric, okta, azure_ad, onelogin.
1. Create an application integration for "Lighthouse" in your IdP. 2. Set ACS or consumer URL as https://{main lighthouse
address}/api/v3.7/sessions/saml/sso/{provider}. 3. Set the Allowed SSO URLs or Allowed redirect URLs or ACS URL Validator to include or
match the /saml/sso/ URL for each address of each of your Lighthouses that you want users to be able to login from. Example:
https://{main lighthouse address}/api/v3.7/sessions/saml/sso/{provider} https://{main lighthouse ip address}/api/v3.7/sessions/saml/sso/{provider} https://{secondary lighthouse address}/api/v3.7/sessions/saml/sso/{provider}
Depending on your IdP you may need to include the /saml/sp_init/ URLs.
https://{main lighthouse address}/api/v3.7/sessions/saml/sso/{provider} https://{main lighthouse address}/api/v3.7/sessions/saml/sp_init/{provider} https://{main lighthouse ip address}/api/v3.7/sessions/saml/sso/{provider} https://{main lighthouse ip address}/api/v3.7/sessions/saml/sp_init/{provider} https://{secondary lighthouse address}/api/v3.7/sessions/saml/sso/{provider} https://{secondary lighthouse address}/api/v3.7/sessions/saml/sp_init/ {provider}
4. Set the Service Provider EntityID or Audience as lighthouse-{provider}.
24.12.1
Managing Lighthouse Users
275
Lighthouse User Guide
5. If your service provider requires you to configure the Recipient and only allows a single value and you run multiple Lighthouses or access Lighthouse via multiple addresses, then either: l Set the recipient as lighthouse-{provider} and use the onelogin option as your provider configuration, or l create a separate application integration per Lighthouse if you only access each via a single address .
6. If your IdP has the option, set the initiator to the Service Provider, set your IdP to sign the Assertion for SAML.
GENERIC IDP SAML ATTRIBUTE
You must also configure your IdP to send an additional attribute LH_Groups as part of the SAML response. In most IdPs this is done by adding an Attribute Statement or Parameter configuration in your application integration. This parameter should be set as a multi-value parameter, that is, multiple values should be provided by multiple duplicative either Attribute Value tags or Attribute tags in the SAML assertion. We recommend setting the value of this attribute to be populated with the names of the user's Roles (or Groups) in your IdP. This method allows you to create roles in your IdP with the same names as the user groups on your Lighthouse that can be assigned in your IdP to grant users that level of access to Lighthouse. Alternatively, you can populate the LH Groups attribute with the names of the Lighthouse user groups the user should be granted by any other mechanism that your IdP provides, that is, custom user properties.
Note: Your IdP can populate the LH_Groups attribute to place users in any Lighthouse user group except Lighthouse's default admin group. You can allow users to login with admin
24.12.1
Managing Lighthouse Users
276
Lighthouse User Guide
privileges by simply creating another user group in Lighthouse with the admin role and assigning the matching role/group in your IdP to the user (that is, populate LH_Groups to include its value).
LIGHTHOUSE IDP SETUP
You must export an IdP metadata xml file for your Lighthouse application integration from your IdP. If your IdP requires that requests be signed by the Service Provider, then you must also provide an x509 certificate & private key in .pem format (either exported from your IdP or created locally then configured in your IdP). 1. Upload your IdP metadata XML (and if required certificate & private key) to your primary
Lighthouse i.e. scp. 2. Use the saml-idp-metadata command to configure each Lighthouse individually. Each
Lighthouse is configured individually with the same or a different metadata xml (and certificate + key).
Note: The commands to configure each Lighthouse individually, all must be run from your primary Lighthouse.
# Example: Configuring a Multi-Instance Lighthouse for Okta IdP # List initial lighthouse configurations (i.e. none) saml-idp-metadata list # Configure Primary lighthouse saml-idp-metadata create \ --metadata metadata.xml \ --provider okta \ --lh-id 1 #Configure Secondary lighthouse saml-idp-metadata create \ --metadata metadata.xml \
24.12.1
Managing Lighthouse Users
277
Lighthouse User Guide
--provider okta \ --lh-id 2 # List lighthouse configurations (i.e. both lighthouses configured) saml-idp-metadata list
EXAMPLES OF SPECIFIC IDP SETUPS
The following are examples of how you could configure officially supported IdPs. They are based on the generic setup and the IdP's configuration options as of 10/2021. l Okta Example - Create an Application l Onelogin Example - Create an Application l Azure Example - Active Directory
OKTA EXAMPLE - CREATE AN APPLICATION
You are required to create an application that Okta will be doing authentication on behalf of.
Note: You must know the addresses of your Lighthouses before creating the application.
1. In the Okta web console go to Applications - > Applications. a. Click Create App Integration. b. Select SAML 2.0.
2. Give the application a name: for example, Lighthouse and click Next. 3. For the Single sign on URL enter: https://{main lighthouse
address}/api/v3.7/sessions/saml/sso/okta
24.12.1
Managing Lighthouse Users
278
Lighthouse User Guide
a. Select: Use this for Recipient URL and Destination URL b. Fill out the Other Requestable SSO URLs with the SSO URLs for every Lighthouse
address that you want to be able to sign in with, that is, IP addresses and DNS address for both your primary and secondary Lighthouses.
Example: https://{main lighthouse ip}/api/v3.7/sessions/saml/sso/okta https://{secondary lighthouse address}/api/v3.7/sessions/saml/sso/okta https://{secondary lighthouse ip}/api/v3.7/sessions/saml/sso/okta
4. For the Audience URI (SP Entity ID) enter lighthouse-okta. 5. Set Name ID format to email. 6. Set to email. 7. There are many ways you could configure Okta to populate the LH_Groups attribute, our
recommended way is to populate it from and manage it via the user's Okta groups: a. Add a Group Attribute Statement:
i. Name: LH_Groups. ii. Name Format: Basic. iii. Filter: Matches Regex .* 8. Click Next and finish.
IDP METADATA
1. Open your Okta application. 2. Go to More Actions > SAML Metadata. This is the metadata xml file that you require to
configure lighthouse.
24.12.1
Managing Lighthouse Users
279
Lighthouse User Guide
CONFIGURE LIGHTHOUSE
1. Copy the Identity Provider metadata XML to your primary Lighthouse. 2. Using saml-idp-metadata on your primary Lighthouse, configure each of your Lighthouses
to use your IdP. For example:
saml-idp-metadata -p {root password} creaUser groupste -m /path/to/okta_ metadata.xml -P okta -n "My Okta display name" -l {LH id number}
GROUPS SETUP
After this initial setup, you will be able to login as a SAML user. If you do not already have your own setup in Lighthouse: 1. Login to Lighthouse as a local user (or any non-SAML user) i.e. root. 2. Create the User groups with the Roles and permission that you require. 3. In Okta go to Directory > Groups. 4. Click Add Group. 5. Enter the Group name that matches a Group name on lighthouse. 6. Open your new group. 7. Go to Manage Apps. 8. Search for your lighthouse app and click Assign. 9. Click Done. 10. Go to Manage People. 11. Search for and click on the users you want to add to the group. The assigned users are now able to login to Lighthouse with the permission levels which that group grants them.
24.12.1
Managing Lighthouse Users
280
Lighthouse User Guide
ONELOGIN EXAMPLE - CREATE AN APPLICATION
You are required to create an application that Onelogin will be doing authentication on behalf of. 1. Go to Applications > Add App > Search for and choose SAML Custom Connector
(Advanced). 2. Name your connector, that is, Lighthouse. 3. In the Configuration tab for your new app:
a. Set Audience (EntityID) to lighthouse-onelogin. b. Set Recipient to lighthouse-onelogin. c. Set ACS (Consumer) URL to: https://{main lighthouse address}/ap-
i/v3.7/sessions/saml/sso/onelogin. d. Set ACS (Consumer) URL Validator to a regex expression that matches only all your
Lighthouses' SSO addresses (IP & DNS for Primary & Secondary Lighthouses). i. Ensure it begins with ^ and ends with $ to match the whole URL. ii. Recommended pattern:
^https:\/\/ {lighthouse addresses} \/api\/v3\.7\/sessions\/saml\/sso\/onelogin$. iii. For example to allow Onelogin login for Lighthouse addresses 192.168.1.10 and lighthouse.example.com , you could use the following: (note the additional () around your hostnames and the | separating them: ^https:\/\/ (192\.168\.1\.10|lighthouse\.example\.com)\/api\/v3\.7\/sessions\ /saml\/sso\/onelogin$. e. Set Login URL to https://{main lighthouse address}/api/v3.7/sessions/saml/sp_ init/onelogin.
24.12.1
Managing Lighthouse Users
281
Lighthouse User Guide
f. Set SAML initiator to Service Provider. g. Set SAML signature element to Assertion. 4. The recommended method to populate LH_Groups is with Onelogin Roles.
a. Go to Parameters then click Add. b. Set Field Name to LH_Groups. c. Check Include in SAML assertion. d. Check Multi-value parameter. e. Click Save. f. Set Default value to User Roles. g. If you intend on filtering the Roles that are sent to lighthouse (using a Rule) set no
transform otherwise set semicolon delimited. l An example Rule to filter roles:
o "Set LH_Groups in" for each role with a value that matches LH_.*. h. Save the parameter. 5. Save the connector.
IDP METADATA
1. Open your Onelogin application. 2. Go to More Actions > SAML Metadata. This is the metadata xml file that you require to
configure lighthouse.
CONFIGURE LIGHTHOUSE
1. Copy the metadata xml to your primary lighthouse. 2. Using saml-idp-metadata on your primary lighthouse, configure each of your lighthouses
to use your IdP., For example
24.12.1
Managing Lighthouse Users
282
Lighthouse User Guide
saml-idp-metadata -p {root password} create -m /path/to/metadata.xml -P onelogin -n "My Onelogin display name" -l {LH id number}.
ROLES SETUP
After this initial setup, you will be able to login as a SAML user. If you do not already have your own User Groups setup in Lighthouse: 1. Login to Lighthouse as a local user (or any non-SAML user) for example, root. 2. Create the User Groups with the Roles and Permissions that you require. 3. In Onelogin Go to Users > Roles. 4. Click New Role.
a. Set the Role's name to match the lighthouse group you want it to map to. b. Select your Lighthouse app to associate the role with. c. Click Save. 5. Open the newly created role. 6. Go to the Users tab on the left. 7. Search for and add your users or create a mapping to automatically add multiple users. 8. Click Save. a. If you used a mapping then go to Users > Mappings and run Reapply All Mappings. 9. Click Done The assigned users are now able to login to Lighthouse with the permission levels that the Onelogin Role/Lighthouse group grants them.
AZURE EXAMPLE - ACTIVE DIRECTORY
Lighthouse can be added as an Enterprise application to Azure Active Directory. This example uses "App roles" to grant users permissions.
24.12.1
Managing Lighthouse Users
283
Lighthouse User Guide
To create an Application (Enterprise applications) 1. Go to Azure Active Directory. 2. Go to Enterprise applications. 3. Click New Application. 4. Click Create your own application. 5. Select Integrate any other application you don't find in the gallery (Non-gallery). 6. Name your Application, for example, Lighthouse, then click Create. 7. Click Properties:
a. Set Assignment required to Yes. b. Set Enabled for users to sign-in to Yes. c. Click Save. 8. Go to Single sign-on: a. Select SAML. b. Edit Basic Configuration:
i. Add an Entity Id lighthouse-azure_ad and set it as default. ii. In Reply URL (Assertion Consumer Service URL) add the SSO URL for each address of
each Lighthouse that you want to be able to sign in on, i.e. IP addresses and DNS address for both your primary and secondary Lighthouses. https://{primary lighthouse address}/api/v3.7/sessions/saml/sso/azure_ad https://{primary lighthouse IP address}/api/v3.7/sessions/saml/sso/azure_ad https://{secondary lighthouse address}/api/v3.7/sessions/saml/sso/azure_ad https://{secondary lighthouse IP address}/api/v3.7/sessions/saml/sso/azure_ad.
24.12.1
Managing Lighthouse Users
284
Lighthouse User Guide
iii. Set Sign on URL to https://{main lighthouse address}/api/v3.7/sessions/saml/sp_init/azure_ad.
iv. Click Save. c. Edit Attributes & Claims:
i. Remove the default claims from Additional claims. ii. Click Add new claim and enter:
l Name: LH_Groups l Source Attributes: user.assignedroles
IDP METADATA
1. Go to the Azure Active Directory. 2. Go to Enterprise applications and open your application. 3. Go to Single sign-on. 4. Navigate to 3. SAML Signing Certificate and find and download Federation Metadata
XML.
CONFIGURE LIGHTHOUSE
1. Copy the Federation metadata XML to your primary Lighthouse. 2. Using saml-idp-metadata on your primary lighthouse, configure each of your lighthouses
to use your IdP as follows: For example, saml-idp-metadata -p {root password} create -m /path/to/metadata.xml -P azure_ad -n "My Azure display name" -l {LH id number}.
24.12.1
Managing Lighthouse Users
285
Lighthouse User Guide
APP ROLES SETUP
After this initial setup, you will be able to login as a SAML user. If you do not already have your own User groups setup in Lighthouse, you can set them up as follows: 1. Login to Lighthouse as a local user (or any non-SAML user) i.e. root. 2. Create the User groups with the Roles and permission required. See Add app roles and get them from a token - Microsoft identity platform for up to date documentation on how to create and assign App Roles. 1. Go to Azure Active Directory. 2. Go to App registrations. 3. Open your app (Use the All Applications tab to see Enterprise apps). 4. Go to App Roles. 5. Click Create App Role.
a. Set the value to match your usergroup on Lighthouse. b. Set Allowed member types to Both (Users/Groups + Applications). c. Set the other fields as required. 6. Go to Azure Active Directory. a. Go to Enterprise applications. b. Open your App, that is, Lighthouse. c. Go to Users and groups. d. Click Add user/group. e. Select a user and one of your App roles then click Assign. The assigned users are now able to login to Lighthouse with the permission levels which that App Role/Lighthouse group grants them.
24.12.1
Managing Lighthouse Users
286
Lighthouse User Guide
CONFIGURE AUTH0 FOR IDP
Lighthouse can be added as an Enterprise application to AUTH0. This example uses "App roles" to grant users permissions.
CREATE AN APPLICATION (ENTERPRISE APPLICATIONS)
1. Go to Auth0. 2. Go to Applications > Application. 3. Click Create application.
a. Select Regular Web Application. b. Name the application, for example, Lighthouse. 4. Go to Settings tab. a. Select SAML. b. Set Application Login URI to:
https://{main lighthouse address}/api/v3.7/sessions/saml/sp_init/auth0
c. In Allowed Callback URLs add each address for each Lighthouse that you want to allow users to sign-in via (that is, IP, hostname, dns for both primary and secondary).
https://{primary lighthouse address}/api/v3.7/sessions/saml/sso/auth0 https://{primary lighthouse IP address}/api/v3.7/sessions/saml/sso/auth0 https://{secondary lighthouse address}/api/v3.7/sessions/saml/sso/auth0 https://{secondary lighthouse IP address}/api/v3.7/sessions/saml/sso/auth0
d. Click Save. 5. Go to the Addons tab:
24.12.1
Managing Lighthouse Users
287
Lighthouse User Guide
a. Click SAML2. b. Go to the SAML settings tab. c. Set the Settings json to:
{ "audience": "lighthouse-auth0", "mappings": { "roles": "LH_Groups" }, "passthroughClaimsWithNoMapping": true, "mapUnknownClaimsAsIs": true, "nameIdentifierFormat": "urn:oasis:names:tc:SAML:1.1:nameidformat:emailAddress", "nameIdentifierProbes": [ "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" ] }
d. Click either Enable or Save. 6. Go to Actions > Triggers > post-login. 7. Click Add Action. 8. Select Build from Scratch. 9. Name the build, for example Lighthouse Roles to Groups SAML mapping.
Note: Leave the Trigger and Runtime unchanged.
10. Click Create. 11. Update the Handler to:
24.12.1
Managing Lighthouse Users
288
Lighthouse User Guide
exports.onExecutePostLogin = async (event, api) => { if (event.authorization && event.authorization.roles) { api.user.setAppMetadata("roles", event.authorization.roles);
} };
12. Click Save and Deploy.
CONFIGURE AUTH0 METADATA FOR IDP
To download IdP metadata: 1. Go to Auth0. 2. Go to Application > Applications. 3. Open your Lighthouse application. 4. Go to Addons. 5. Go to SAML. 6. Go to Usage. 7. Click the Identity Provider Metadata download.
A file named metadata.xml downloads to your preferred directory Configure each Lighthouse to use Auth0 IdP with the metadata file: 1. Copy the downloaded metadata.XML file to your primary Lighthouse. 2. Use the saml-idp-metadata file on your primary Lighthouse, configure each of your
Lighthouses to use your IdP with this command: saml-idp-metadata -p {root password} create -m /path/to/metadata.xml -P auth0 -n "My Auth0 display name" -l {LH id number}
24.12.1
Managing Lighthouse Users
289
Lighthouse User Guide
CONFIGURE AUTH0 ROLES FOR IDP
After you have added Lighthouse as an Enterprise application to AUTH0, you must use the App roles feature to grant users permissions to use IdP. After this initial setup, you will be able to login as a SAML user. 1. If you do not already have your own Usergroups setup in Lighthouse:
a. Login to Lighthouse as a local user (or any non-SAML user) for example, root. b. Create the User groups with the required Roles and permission. 2. Go to Auth0. 3. Go to User Management. 4. Go to Roles. 5. Click Create Role. 6. Enter the Role name that matches a Lighthouse group name. 7. Open your Role. 8. Go to the Users tab. 9. Click Add Users. a. Assign the role to the appropriate users. The assigned users are now able to login to Lighthouse with the permission levels granted by the Auth0 Role/Lighthouse group.
LIMITATIONS OF SAML CONFIGURATION
IDP METADATA CERTIFICATE EXPIRY
The Identity Provider (IdP) metadata XML file that you exported to configure Lighthouse contains a certificate that is used to authenticate that the SAML response came from your IdP.
24.12.1
Managing Lighthouse Users
290
Lighthouse User Guide
Different IdPs have different expiry periods for these certificates, consult your IdP's documentation to find their expiry period. When your IdP's certificate expires, you must regenerate it then reexport your IdP metadata and update your Lighthouse configurations. If your IdP supports sending expiry notifications to your admin, we recommend you enable these notifications.
MAKE CHANGES TO USER PERMISSIONS
When you change the permissions assigned to a Lighthouse user in your IdP (via LH_Groups SAML attribute), the changes will not take effect until the user logs out and back into Lighthouse. If you want to quickly restrict a user's access, consider altering the permissions of or deleting that user's user groups on Lighthouse. You can also set a low Web Session Timeout.
SAML SSO USER GROUPS
The LH_Groups attribute can be used to place SSO users in any Lighthouse user group except Lighthouse's default admin group. You can allow users to login with admin privileges by simply creating another user group in Lighthouse with the admin role and assigning the matching role/group in your IdP to the user (i.e. populate LH_Groups to include its value).
SAML SSO USERS
SAML Users can only be managed in your IdP and will not appear under Lighthouse User Management.
SAML SSO SUPPORT
Feature Web Terminal to access the serial port through Lighthouse.
Supported
24.12.1
Managing Lighthouse Users
291
Lighthouse User Guide
Feature Automation Gateway features through NetOps > Automation Gateway
Supported
Web Terminal to login to the Lighthouse CLI via the Lighthouse Web UI.
Connected Resource Gateway connect to a resource via SSH.
SSH link on a port accessed through Ports from the Lighthouse web interface. For SAML users, the SSH link will not be visible.
24.12.1
Managing Lighthouse Users
292
Lighthouse User Guide
ADVANCED FUNCTIONALITY
NetOps modules leverage Opengear's remote presence and proximity to infrastructure by allowing software applications to run directly on top of the out-of-band management fabric. The NetOps modules enable automation of the configuration and operation of network infrastructure in data center and remote edge locations.
WHAT IS A NETOPS MODULE
NetOps modules are software components that enable automation of specific operational scenarios (for example, network device provisioning), deployed as Docker containers. The modules become active on Lighthouse when a module license is installed and can then be manually or automatically activated on nodes.
Note: The availability of NetOps modules is dependent on your subscription type.
SUBSCRIPTIONS
NetOps modules require a Lighthouse with an appropriate subscription and modules to be uploaded and active. You will also require at least one node enrolled and able to use these modules.
Note: NetOps modules are not available with Lighthouse Core or Lighthouse Enhance subscriptions. For more information, see Subscription Types.
Subscription Type Enterprise Edition (EE)
Secure Provisioning*
IP Access*
Automation Gateway
24.12.1
Advanced Functionality
293
Subscription Type
Secure Provisioning*
Enterprise Automation Edition (AE)
IP Access*
Lighthouse User Guide
Automation Gateway
* The Smart Management Fabric feature can be used with these NetOps modules with some caveats.
MANAGE NETOPS MODULES
The management of NetOps modules is accessed from the NetOps menu. Note: The availability of these modules is dependent on your subscription type.
NETOPS PLATFORM SECURITY
The NetOps Automation platform uses a combination of advanced hardware and software security features to provide end-to-end security and resilience against network breach, fault or failure. All communications between Lighthouse and nodes are tunneled inside Lighthouse VPN, using strong ciphers and automated certificate authentication and revocation. Nodes such as the OM and CM8100 contain a TPM chip, which verifies the authenticity of the OM system software, its configuration, and NetOps module code and data any unauthorized tampering will render the appliance inoperable. These nodes are physically hardened to resist tampering attempts to physically to access storage media will render the appliance inoperable With a built-in cellular capability nodes with the TPM chip provide a secure WAN uplink in the event of network outage, DOS, or during initial network turn-up at a remote location.
24.12.1
Advanced Functionality
294
Lighthouse User Guide
CHANGE DOCKER IP RANGES
Docker powers the NetOps platform within Lighthouse. By default, Docker and NetOps utilize the 172.17.0.0/16 and 172.18.0.0/16 subnets. This has the potential to cause collisions inside of some networks. To avoid this, you can change these settings. To update Dockers subnet, you must alter two parameters, Docker's default subnet and the NetOps modules subnet. To do so: 1. Login to the Lighthouse shell CLI as a Lighthouse Administrator or the root user. 2. Ascertain the number of running containers to ensure you select an appropriate subnet size:
sudo docker ps -q | wc -l
3. Open a config CLI session on the Lighthouse Server and run the following to enter configuration management:
ogconfig-cli
4. Set the IP Range of the Docker subnet in CIDR format:
set services.nom.default_subnet "10.123.17.1/24"
5. Set the IP Range of the NetOps subnet in CIDR format:
set services.nom.netops_subnet "10.123.18.0/24"
6. Push the config to become the running config:
push
7. Exit the configuration management:
exit
24.12.1
Advanced Functionality
295
8. Restart Docker:
sudo /etc/init.d/docker.init restart
9. Restart the NetOps module(s):
sudo /etc/init.d/docker.init reset
Lighthouse User Guide
Note: The network mask selected for these subnets limits the maximum number of containers that can run on Lighthouse. NetOps currently runs up to approximately 10 containers.
INSTALL NETOPS MODULES
PERFORM NETOPS INSTALLATION FROM AN ONLINE REPOSITORY 1. In the Menu Pane, select NetOps > NetOps Installation.
The NETOPS INSTALLATION page displays with the ONLINE tab selected. 2. Enter the Repository address for the container registry that hosts NetOps modules. 3. Click Start Online Sync to start the process.
A progress message displays:
NetOps online sync in progress
The sync completes and the following message displays:
NetOps online sync completed
24.12.1
Advanced Functionality
296
Lighthouse User Guide
PERFORM NETOPS INSTALLATION FROM AN OFFLINE REPOSITORY
If Lighthouse is deployed on a network where outbound access to the Docker Hub repository is not permitted or not available, use the NetOps offline installer. The offline installer file can be downloaded from this link: offline installer file. 1. In the Menu Pane, select NetOps > NetOps Installation.
The NETOPS INSTALLATION page displays with the ONLINE tab selected. 2. Select the OFFLINE tab. 3. Drag and drop or select a file directly to upload.
Note: Supported files: .tar.gz
4. Click Upload to start the process.
PERFORM NETOPS INSTALLATION FROM AN OFFLINE REPOSITORY VIA CLI
1. Copy the offline installer to Lighthouse using scp, WinScp or similar, into the /mnt/nvram directory.
2. Log in to Lighthouse shell CLI as a Lighthouse Administrator and run:
gzip -d </mnt/nvram/netops_modules_*.tar.gz | nom update && rm /mnt/nvram/netops_modules_*.tar.gz
3. Deploy the upgrade to nodes: a. Log in to the Lighthouse web UI as a Lighthouse Administrator or the root user. b. In the Menu Pane, select NetOps > Manage NetOps Modules. The MANAGE NETOPS MODULES page displays. c. Confirm the module version. d. Click Redeploy. A progress message displays:
24.12.1
Advanced Functionality
297
Lighthouse User Guide
Module activation is in progress Module activation may take several minutes
The deployment completes and the following message displays:
Success Module synchronization complete
INSTALL MODULES FROM THE CLI
1. Log in to the Lighthouse CLI as root.
Note: Optionally, log in as a Lighthouse Administrator and become root with: sudo -i
2. Run the following procedure replacing root and default with a Lighthouse Administrator or root credentials:
USERNAME=root PASSWORD=default /etc/scripts/netops_sync_handler token=$(curl -k -L -d '{"username":"'$USERNAME'","password":"'$PASSWORD'"}' "https://127.0.0.1/api/v3.0/sessions/" | python -c 'import sys, json; print json.load(sys.stdin)["session"]') curl -k -L -H "Content-Type: application/json" -H "Authorization: Token $token" "https://127.0.0.1/api/v3.0/netops/modules/dop/redeploy"
ACTIVATE A NETOPS MODULE
The NetOps module license is installed on Lighthouse and contains a preset number of available node activations. Each supported node that is activated for the NetOps module provisioning, consumes an available activation. Lighthouse itself does not consume an activation.
24.12.1
Advanced Functionality
298
Lighthouse User Guide
Installing the NetOps module license automatically activates the module on Lighthouse, at which point the NetOps Automation platform deploys the central module software components, including the module's UI, to Lighthouse. The process of automatically or manually activating a NetOps module on a node deploys the remote module software components to that node, securely over Lighthouse VPN.
PREPARATION
1. Install the Lighthouse VM and ensure it is running. 2. Login to the Lighthouse web UI as root or a Lighthouse Administrator. 3. Install the Lighthouse node subscription (SKU OGLH) under > SYSTEM > Subscriptions.
PROCEDURE
1. Ensure you have a valid NetOps module subscription installed under > SYSTEM > Subscriptions.
Note: For more information, see Subscription Types.
2. It will take a few minutes for the module to activate on Lighthouse. View the progress under NetOps > Manage NetOps Modules.
Nodes may now be automatically activated for the module as they enroll, or manually activated after enrollment.
'ALWAYS ACTIVATE' MODE ON ALL NODES (AUTOMATIC)
In the Always Activate mode, NetOps automatically activates the NetOps module on all nodes, provided a license is present and activations are available. All nodes are activated for the module as they enroll.
24.12.1
Advanced Functionality
299
Lighthouse User Guide
PROCEDURE
1. In the Menu Pane, select NetOps > Manage NetOps Modules. The MANAGE NETOPS MODULES page displays.
2. Under Always Activate, select ENABLED as required for the module: l SECURE PROVISIONING l IP ACCESS l AUTOMATION GATEWAY
3. Click Apply. To activate a new node, enroll the node into Lighthouse.
ACTIVATE NETOPS ON SELECTED NODES (AUTOMATIC)
You may selectively activate the module on a subset of nodes using Enrollment Bundles. Only nodes enrolling using one of these bundles will be automatically activated.
PROCEDURE
4. In the Menu Pane, select NetOps > Manage NetOps Modules. The MANAGE NETOPS MODULES page displays.
5. Under Always Activate, select DISABLED as required for the module: l SECURE PROVISIONING l IP ACCESS l AUTOMATION GATEWAY
6. Click Apply. 7. In the Menu Pane, select Node Tools > Enrollment Bundles.
The ENROLLMENT BUNDLES page displays.
24.12.1
Advanced Functionality
300
Lighthouse User Guide
8. Click Add Enrollment Bundle to add a new bundle (you may also edit an existing bundle). The NEW ENROLLMENT BUNDLE page displays.
9. Enter the details and choose whether or not to Auto-Approve enrollment. 10. Under the NETOPS SECTION select Add Module.
The CHOOSE MODULE dialog is displayed. 11. Select the module from the drop-down. 12. Click Apply.
Note: Lighthouse-initiated manual enrollment (for example, clicking the Add Node button in the Lighthouse web UI) does not support bundles, you must use a node-initiated enrollment method.
ACTIVATE THE NETOPS MODULE ON NODES (MANUAL)
To activate nodes manually after enrollment, the process is performed across three phases: l Select Nodes l Pre-Flight Test l Push
SELECT NODES
1. Ensure the Always Activate option is DISABLED and applied for each module on the NetOps > Manage NetOps Modules dashboard.
2. In the Menu Pane, select Node Tools > Config Templates. The CONFIG TEMPLATES dashboard is displayed defaulted to the AUTHENTICATION tab.
3. Select the NETOPS MODULES tab. 4. Select the Push Template from the actions available on the module.
24.12.1
Advanced Functionality
301
Lighthouse User Guide
The PUSHING TEMPLATE page displays. 5. Check the NODE ID to push the template to.
PRE-FLIGHT TEST 6. Click Run Pre-Flight Test.
The page displays the current Pre-Flight Status per node. PUSH 7. On successful completion of the Pre-Flight Test, select Push Configuration.
The page displays the current Push Status per node.
Note: Under the NetOps licensing arrangement, when a node is activated for the NetOps module, the activation is consumed by and locked to that node. Unenrolling the node returns the activation to the available pool. Under NetOps subscription arrangements, it would be counted towards the node assignment of the subscription.
DEACTIVATE (REMOVE) A NETOPS MODULE
DEACTIVATE AND REMOVE A NETOPS MODULE VIA THE API
Use the following API call to Lighthouse:
DELETE /api/v3/netops/modules/module_id/nodes/node_id
where: l module_id is one of dop (Secure Provisioning), sdi (IP Access), or ag (Automation Gateway). l node_id is the internal node ID, for example, nodes-1.
24.12.1
Advanced Functionality
302
Lighthouse User Guide
DEACTIVATE AND REMOVE NETOPS MODULES VIA CLI
1. Log in to the Lighthouse CLI shell as root or a Lighthouse Administrator user. 2. Determine the node's node ID by running:
node-info --list
3. Update the highlighted fields with your username, password, the node ID and modules to deactivate, then run the following:
LH_USERNAME="root" LH_PASSWORD="default" NODE_ID="nodes-1" MODULES_TO_DEACTIVATE="dop ag sdi"
token=$(curl -k -L -d '{"username":"'$LH_USERNAME'","password":"'$LH_ PASSWORD'"}' https://127.0.0.1/api/v1/sessions/ | cut -f10 -d'"')
for module_id in $MODULES_TO_DEACTIVATE; do curl -k -L -X DELETE -H "Authorization: Token $token"
https://127.0.0.1/api/v3/netops/modules/${module_id}/nodes/$NODE_ID done
SECURE PROVISIONING
Note: The availability of this module is dependent on your subscription type.
Secure Provisioning for NetOps is a configuration storage, distribution and provisioning system. It does not generate, test or validate device configuration. Instead, it is focused on provisioning remote resources with user-supplied configuration and device OS images, automatically, remotely and securely, no matter where those devices are and no matter what the state of the network is.
24.12.1
Advanced Functionality
303
Lighthouse User Guide
The Secure Provisioning license is installed on Lighthouse and contains a preset number of available node activations. Each node activated for Secure Provisioning consumes an available activation; Lighthouse itself does not consume an activation. Using Secure Provisioning for NetOps, network turn up no longer requires network engineering staff to perform initial configuration tasks on site, even when there is no existing LAN or WAN in place. Remote hands rack, stack and cable the infrastructure, then Secure Provisioning for NetOps Automation automates the rest of the turn up process. The Secure Provisioning module leverages these technologies: l ZTP (Zero Touch Provisioning): The process by which resources in their unconfigured state
request and are delivered initial setup resources over the local management network. l Human-readable YAML language: Provides simplified configuration of resource ZTP
configuration parameters. l Git source control: resource resources such as initial configuration files and OS images are
automatically stored in a versioned, auditable repository. l Ansible automation framework: Automatically propagates device resources and configures on-
site ZTP services. The Secure Provisioning module combines a centrally orchestrated, vendor-neutral ZTP service with on-site node LAN and WAN connectivity, to automate the provisioning process end to end.
SECURE PROVISIONING CONFIGURATION MANAGEMENT
Secure Provisioning always applies device configuration in its entirety and does not support applying config patches or deltas to a provisioned device (for example, adding a few lines to running config, to enable a specific feature).
STATELESS FILE MANAGEMENT
Secure Provisioning supports a DevOps-style approach which collapses initial provisioning, disaster recovery and ongoing maintenance workflows into the one workflow:
24.12.1
Advanced Functionality
304
Lighthouse User Guide
Using this approach, the config patch is applied in Lighthouse to the central configuration template via git, which renders the configuration file in its entirety and pushes to the OM node. The device is factory reset and pulls the new configuration as if it were being provisioned for the first time.
Pros
Cons
Eliminates config drift.
Requires a longer maintenance window as the device is reset and reboots.
Enforces config reproducibility.
Patches cannot be applied to running configuration.
Central audit trail of all configuration changes.
Disaster recovery becomes as simple as resetting all devices to reprovision.
STATEFUL DEVICE MANAGEMENT GATEWAY
The NetOps Automation platform provides a management fabric from remote devices to your central management network via Lighthouse VPN and/or the cellular WWAN. There are many tools and protocols purpose-built for stateful configuration management, such as Cisco NSO and SolarWinds NCM, and NETCONF and gRPC (OpenConfig). NetOps can be leveraged by these tools as a secure, resilient management path, both extending their reach to the out-of-band management network, and ensuring reachability during outages.
HOW SECURE PROVISIONING WORKS
The Secure Provisioning feature centrally orchestrates the distribution of resource configuration files and firmware images, and the node provisioning (ZTP) services required to deliver the files to resources.
24.12.1
Advanced Functionality
305
Lighthouse User Guide
Secure Provisioning is configured by defining the resources to provision resources with, and defining how these resources should be distributed around your network. l Device Resource Bundles contain the files required to provision one or many resources:
l Configuration File, Script File and/or Image Files. l Each Resource Bundle has a defined Device Type. l When a Resource Bundle is distributed to a node, any ZTP request matching the Device
Type are provisioned with the bundled resources. l This may be restricted to specific devices by specifying one or more device MAC Addresses
(range and reverse match supported) or Serial Numbers (not supported by all vendors). l Resource Distribution policies are defined by Node Inventory Lists:
l Static Node Inventory List - a predefined, static list of nodes to distribute to. l Dynamic Node Inventory List - evaluates a Node Filters each time resources are distributed.
Tip: The Dynamic Node Inventory List allows you automatically tag certain nodes with Enrollment Bundles, for example, by region or site class, to help automate resource distribution to newly enrolled nodes in that region.
Device Resource Bundle and Resource Distribution configuration are supplied to Lighthouse using the web UI or CLI (git) method. The Web UI configuration method creates an underlying YAML configuration the same as created using the git method, it is effectively a front end to the git method. A git push to the Lighthouse repository, or clicking the UI Push Now/Push Resources button triggers a resource push: l A git post-commit hook triggers an Ansible playbook on Lighthouse. l The playbook copies resources down to nodes, securely over Lighthouse VPN. l The playbook start or restarts ZTP services on nodes.
24.12.1
Advanced Functionality
306
Lighthouse User Guide
SUPPORT FOR SECURE PROVISIONING
Opengear OM2200 and OM1200 nodes may be activated as Secure Provisioning nodes. Opengear ACM7000 or IM7200 nodes may also be activated as provisioning nodes, however not all features are available and there are some caveats to be aware of. Features that are not available of ACM7000/IM7200 nodes: l Secure boot and physical tamper resistance. l Encryption of device resource files at rest. l Centralized ZTP status logging. l Device configuration templating. l Ordered provisioning. l Post-provisioning scripts. Other ACM7000/IM7200 caveats: l Secure Provisioning takes control of node DHCP, NTP, DNS services and overwrites system
configuration. l Secure Provisioning overwrites node Management LAN configuration.
VENDOR RESOURCES SUPPORTED BY SECURE PROVISIONING
Secure Provisioning is vendor-neutral, with support for a broad range of network devices from multiple vendors. The ZTP process used to provision devices is not standardized, and each vendor OS implements ZTP differently for example, using differing DHCP options, or requiring an intermediary script to load files.
24.12.1
Advanced Functionality
307
Lighthouse User Guide
With Secure Provisioning, you upload configuration and/or firmware image files to create Resource Bundles, then select the vendor profile for that Resource Bundle. This automatically generates the vendor-appropriate ZTP configuration, simplifying the delivery of resources to target devices. Secure Provisioning currently has built-in support for provisioning devices from these vendors: l Cisco (IOS, IOS XR, IOS XE, NX-OS) l Juniper l Arista l HPE/Aruba l Huawei l Cumulus l Pica8 l Opengear Advanced users may add support for additional devices using custom DHCP configuration.
CONNECT TO A TARGET DEVICE
1. Connect a supported resource's management NIC directly to the node. 2. If the node has a built-in Ethernet switch, connect the device to any switch port. 3. Otherwise, connect the device directly to the node's NET2 Ethernet, or via an intermediary
management switch. 4. Power on the resource. 5. Ensure the resource is in ZTP mode, this typically requires the device to have its configuration
erased/reset to factory defaults.
24.12.1
Advanced Functionality
308
Lighthouse User Guide
LOCAL NETWORK SERVICES PROVIDED BY NODES
In addition to zero touch provisioning (ZTP) services, the local node runs local services required to act as a bootstrap management LAN and secure WAN for resources from day zero onwards. When responding to a BOOTP/DHCP provisioning request from a device, the Operations Manager node hands out its own local address as a: l Default Gateway l DNS Server l NTP Server l SYSLOG Server
DEFAULT GATEWAY
Devices trying to reach to destinations on the central LAN that Lighthouse resides on are securely routed over Lighthouse VPN. This allows devices to reach, for example, central NMS for monitoring, and central configuration systems for final service provisioning. Requests to other remote destinations are masqueraded behind and routed out the node's built-in cellular WWAN, allowing devices to reach cloud provisioning services. Note that device requests are masqueraded to Lighthouse's central IP and will appear to be originating from Lighthouse to hosts on the central LAN. All traffic between remote node network and the central Lighthouse network is securely tunneled inside Lighthouse VPN.
DNS SERVER
DNS lookups from devices are securely proxied through Lighthouse VPN to the central DNS server(s) used by Lighthouse, allowing devices to resolve central hosts from day one.
24.12.1
Advanced Functionality
309
Lighthouse User Guide
NTP SERVER
The NTP Server allows devices to set accurate time on first boot, for example, for certificate verification and generation. By default, the node's NTP service uses its local hardware clock as time source.
SYSLOG SERVER
The Syslog Server relays messages to a central LogZilla instance (this is an optional extra module). This allows log collection from day zero, and analysis of the device ZTP process itself.
SECURE PROVISIONING CONFIGURATION
All system configuration is performed via Lighthouse. The configuration necessary to provision a device consists two elements. The basic steps to configure Secure Provisioning are: l Create Device Resource Bundles and upload resource files (for example, configuration files or
scripts, firmware images) to Lighthouse. l Define Node Inventories to distribute the resources to specific nodes, where they will become
available for devices to request for provisioning.
DEVICE RESOURCE BUNDLE
A Device Resource Bundle contains the resource files, such as, a configuration file and OS upgrade image that are loaded via ZTP (DHCP + TFTP/HTTP) onto the resource. This may be a full, final configuration, or a baseline configuration to allow the resource to become managed by an upstream configuration service.
24.12.1
Advanced Functionality
310
Lighthouse User Guide
As each vendor's ZTP process is slightly different, Device Resource Bundles allow you to select the Device Type. This generates the appropriate ZTP server configuration (DHCP options), any necessary intermediary provisioning scripts and enables device-specific ZTP features, such as serial number matching. By default, Device Resource Bundles are targeted to all resources of the selected Device Type. Bundles may be targeted to specific resources by specifying one or more device MAC addresses (including range and reverse match), or in some case by specifying one or more device serial numbers.
NODE INVENTORY
A Node Inventory is a static or dynamic list of nodes and a corresponding list of Device Resource Bundles. This defines how Device Resource Bundles are distributed around your network. Resource Bundles may be distributed using one of two methods: l Push to a static list of nodes, selected individually by node ID l Push to a dynamic list of nodes, linked to a Lighthouse Node Filters of nodes
Note: You may combine distribution methods.
CREATE A DEVICE CONFIGURATION
To provision a resource, you must supply device resources. Device resources consist of an initial configuration file for the device to install, and optionally an operating system image for the device to upgrade itself with. Device resource file formats are specific to the target vendor. Secure Provisioning for NetOps Automation provisions these files, but does not generate them.
24.12.1
Advanced Functionality
311
EXAMPLE CONFIGURATION FILES l A trivial Arista initial configuration file may look like:
demo_arista.cfg
Lighthouse User Guide
l Example 2: trivial Cisco IOS XR initial configuration may look like:
24.12.1
Advanced Functionality
312
Cisco IOS XR initial configuration
Lighthouse User Guide
CLI BASED WORKFLOW
Advanced automation users may choose to manage device resources and resource distribution with direct access to the central file repository on Lighthouse. All necessary resource and configuration files are uploaded to Lighthouse using the Secure Copy protocol such as scp, WinScp or similar - or advanced users may prefer to use git directly.
24.12.1
Advanced Functionality
313
Lighthouse User Guide
If you have adopted DevOps-style configuration management using your own source repository (such as git, Mercurial or Subversion) and/or configuration deployment using continuous integration (such as Jenkins or GitLab), this interface also provides a convenient way to hook the Opengear system into these tools and workflows. For example, a configuration commit in the upstream system could automatically proliferate to the Lighthouse file repository, and then in turn to the downstream nodes. Note that changes pushed to nodes via the Lighthouse UI or API will override those made by direct repository access, therefore UI- based or CLI-based workflows should be considered mutually exclusive modes of operation.
CREATE CONFIGURATION YAML
The first step is to assign resource files to specific device types (collectively known as device resources), and to assign device resources to be deployed to specific nodes.
Tip: The web UI provides a convenient way to start provisioning resources without requiring to be fully familiar with YAML or git. The generated YAML files that controls resource bundling and distributions is located on Lighthouse, inside the central-dop container. You can view it by running the following command: sudo docker exec -it central-dop cat /srv/central-ui/root/config.yml | less
Use a YAML file to bundle device resources, and control the distribution of device resources from Lighthouse to the nodes. Procedure 1. Create a new directory or folder of your choosing, for example: nom-prov. 2. Inside the nom-prov directory, create a new directory or folder called: downloads. 3. In the nom-prov directory, create a file with the .yml or.yaml extension, using the following
format:
24.12.1
Advanced Functionality
314
Lighthouse User Guide
NOM-PROV.YML
device_resources: demo_arista: device_type: arista config_file: 'demo_arista.cfg' image_file: 'arista_eos.swi'
node_inventory: MyNodes: static: - nodes-1
deployment: MyNodes: - demo_arista
Note: Indentation is meaningful in YAML, and you must use space characters not tabs to indent.
The device_resources list groups and assigns resource files to particular device types (i.e. resource bundles). 4. Choose an identifier for each resource bundle item, for example demo_arista. 5. For each item, you must provide the device_type, as well as well as one or more resources, i.e.
config_file or image_file. l device_type matches this device resource item to all devices from the specified vendor it
may be one of the following: Cisco, Cisco_xe, Cisco_xr, Cisco_nx, Juniper, Arista, Aruba, Huawei, Cumulus, Pica, Opengear.
24.12.1
Advanced Functionality
315
Lighthouse User Guide
l config_file is the initial configuration file for the device to load via ZTP, as present in the downloads directory.
l image_file is the initial software image for the device to load via ZTP, as present in the downloads directory.
Note: HPE/Aruba devices do not support the image upgrade via ZTP. The Cisco Autoinstall process does not support image upgrade via ZTP, to automate image upgrade you must supply a TCL script file rather than a configuration file.
l mac_address optionally target this bundle at the listed MAC address(es), which may be specified in full, using a wildcard (for example, 00:10:FA:C2:BF:*), or negated to exclude from the match (for example, !01:23:45:67:89:AB).
l serial_number optionally target this bundle at the listed serial number(s). Device resource items are then assigned to nodes using the deployment and optionally the node_inventory lists. See Node Inventory for an overview of available distribution methods. The node_inventory list defines groups of nodes. Choose an identifier for each inventory, for example:. branchinventory_ or labinventory_ .
DEFINE A STATIC INVENTORY:
1. Create a list named static. 2. List nodes by node ID, for example, nodes-1. 3. You can view node IDs by running the following command on Lighthouse: node-info --all
DEFINE A DYNAMIC INVENTORY:
1. Create a Lighthouse Node Filters. 2. Create a key named smartgroup with a value of the Node Filters name, this Node Filters
search is dynamically evaluated to a list of nodes each time resources are pushed The deployment list assigns device resources to the node inventories defined above, or all nodes.
24.12.1
Advanced Functionality
316
Lighthouse User Guide
l Deployment identifiers correspond to node_inventory identifiers, for example, branchinventory_.
l Assign device resources by listing device resource items, for example, demo_arista. l You may have multiple device resources per deployment. A more comprehensive YAML file may look like: more-devices.yml
device_resources: access_switch: device_type: juniper config_file: 'jn-switch35.config' image_file: 'jinstall-ex-4200-13.2R1.1-domestic-signed.tgz' mac_address: - '00:00:0c:15:c0:*' - '!00:00:0c:15:c0:99' branch_router: serial_number: - 'SAD15300D4W' - 'FOC1749N1BD' - 'AVJ18163A52' config_file: 'branch_xr.cfg' device_type: cisco_xr demo_arista: device_type: arista config_file: 'demo_arista.cfg' image_file: 'arista_eos.swi'
node_inventory: branch_inventory: static:
24.12.1
Advanced Functionality
317
Lighthouse User Guide
- nodes-1 - nodes-2 - nodes-10 lab_inventory: smartgroup: LabNodes
deployment: lab_inventory: - demo_arista - access_switch branch_inventory: - branch_router - access_switch
HOW UI FIELDS CORRESPOND TO THE YAML FILE (EXAMPLE)
The following example YAML file contains line-by-line comments (blue text) denoting the UI page or field above each corresponding YAML element:
# CONFIGURE NODES > Secure Provisioning > Device Resources device_resources:
# Device Resource Details > Name access_switch:
# Device Resource Details > Device Type device_type: juniper # Device Resource Details > Configuration File config_file: 'jn-switch35.config' # Device Resource Details > Image File image_file: 'jinstall-ex-4200-13.2R1.1-domestic-signed.tgz' # Device Resource Details > MAC Addresses mac_address:
24.12.1
Advanced Functionality
318
Lighthouse User Guide
- '00:00:0c:15:c0:*' - '!00:00:0c:15:c0:99' # Device Resource Details > Provision After provision_after: - branch_router
# Device Resource Details > Name branch_router: # Device Resource Details > Device Type device_type: cisco_xr # Device Resource Details > Serial Numbers serial_number: - 'SAD15300D4W' - 'FOC1749N1BD' - 'AVJ18163A52' # Device Resource Details > Configuration File config_file: 'branch_xr.cfg'
# Device Resource Details > Name demo_arista: # Device Resource Details > Device Type device_type: arista # Device Resource Details > Configuration File config_file: 'demo_arista.cfg.j2' # Device Resource Details > Image File image_file: 'arista_eos.swi' # Device Resource Details > Post-Provisioning Script post_provision_script: arista_fixups_over_ssh.py post_provision_script_timeout: 900
# CONFIGURE NODES > Secure Provisioning > Resource Distribution node_inventory:
24.12.1
Advanced Functionality
319
Lighthouse User Guide
# Static Node Inventory List > Inventory Details > Name BranchInventory:
# Inventory Details > Select Nodes static: - nodes-1 - nodes-2 - nodes-10
# Dynamic Node Inventory List > Inventory Details > Name LabInventory:
# Inventory Details > Node Filters smartgroup: LabNodes
# CONFIGURE NODES > Secure Provisioning > Resource Distribution (mostly!) deployment:
# CONFIGURE NODES > Secure Provisioning > Resource Distribution
Inventory
Details > Resource Push
LabInventory:
- demo_arista
- branch_router
- access_switch
# CONFIGURE NODES > Secure Provisioning > Resource Distribution > Inventory
Details > Resource Distribution
BranchInventory:
- branch_router
- access_switch
24.12.1
Advanced Functionality
320
Lighthouse User Guide
UPLOAD CONFIGURATION AND RESOURCES
1. Assemble device resources on your PC or laptop in preparation for upload. 2. Locate the nom-prov directory created in the previous section. 3. Copy device resources into nom-prov/downloads. Your locally assembled files will now look similar to that below:
. nom-prov
nom-prov.yml downloads
arista_eos.swi demo_arista.cfg
You must now choose how you will upload files to the central Secure Provisioning repository, using Secure Copy (scp) or git.
OPTION A. SECURE COPY METHOD
Secure copy the entire nom-prov directory to Lighthouse port 2222, to the /srv/central-auto/ directory and authenticating as root, for example, using the scp command:
cd nom-prov scp -P 2222 -rp ./* root@192.168.0.1:/srv/central-auto/
.. where 192.168.0.1 is the IP address of Lighthouse. Secure Provisioning now automatically propagates the device resources to the nodes specified by the YAML, it automatically configures and starts or restarts ZTP services on the nodes. At this point, target device will begin the ZTP process and become provisioned.
24.12.1
Advanced Functionality
321
Lighthouse User Guide
OPTION B. GIT METHOD
Advanced users may choose to access the Secure Provisioning git repository on Lighthouse directly, rather than using scp. This has the advantage of supporting commit messages and integrate with upstream git or other continuous integration systems. Example commands to initialize the repository for the first time:
ssh-copy-id root@192.168.0.1 cd nom-prov git init git remote add origin ssh://root@192.168.0.1:2222/srv/central git add -A git commit -a -m "Initial commit of ZTP resources" git push origin master
where 192.168.0.1 is the IP address of Lighthouse. After the repository has been initialized, subsequent users can operate on it using the clone command:
ssh-copy-id root@192.168.0.1 git clone ssh://root@192.168.0.1:2222/srv/central nom-prov cd nom-prov echo >> nom-prov.yml git commit -a -m "Whitespace change for testing, please ignore" git push origin master
where 192.168.0.1 is the IP address of Lighthouse.
24.12.1
Advanced Functionality
322
Lighthouse User Guide
ADDITIONAL RESOURCE FILES AND DEVICE TYPE FILES
You may also provide additional resource files that are not explicitly part of Device Resource Bundles, for example, final configuration files that may be conditionally fetched and applied by the device's primary ZTP script. You may also extend Secure Provisioning to support additional device types by providing ISC DHCP configuration snippets, for example: new-vendor.conf
class "new-vendor-class" { match if (option vendor-class-identifier = "new-vendor"; option bootfile-name "new-vendor.cfg";
}
Additional files must be placed in the subdirectory named after the Node Inventory they will be deployed to. Within this subdirectory, files must be placed in the following: l Resource files such as device configuration or image files are placed in the downloads
directory. l Advanced: DHCP snippets may be placed in the dhcpd directory. Directly added files are pushed together with YAML-generated files to the nodes. An example local directory structure is shown below with a YAML config file from the earlier example, as well as manual new-vendor files added to the my_inventory directory:
. nom-prov nom-prov.yml downloads demo_arista.cfg cumulus_interfaces cumulus_setup.sh
24.12.1
Advanced Functionality
323
Lighthouse User Guide
arista_eos.swi my_inventory
downloads new-vendor.cfg dhcpd
new-vendor.conf
The files are uploaded to the central Secure Provisioning repository, using Secure Copy or git, in the same way as the earlier example.
CONFIGURE DEVICE RESOURCES VIA ZTP
There are two factors that determine which resources are delivered to which devices via ZTP: l Device resource bundle matching. l Resource distribution.
DEVICE RESOURCE BUNDLE MATCHING
As well as containing resource files themselves, each Resource Bundle itself has a few extra parameters: device vendor, device MAC address(es) and device serial number(s) (not supported by all vendors). Of these, only the device vendor is mandatory. When a resource broadcasts a BOOTP/DHCP request to initiate ZTP, it advertises its vendor ID string, MAC address, and in some cases serial number. These values are compared to the values in each Resource Bundle contained on the local node. If there's a match, the local node provisions the device with the resource files in the matching bundle.
24.12.1
Advanced Functionality
324
Lighthouse User Guide
RESOURCE DISTRIBUTION
Node Inventories are used to selectively control which Resource Bundles are pushed to which nodes. A node will only respond to a BOOTP/DHCP request on its local network if a matched Resource Bundle has been pushed to it. Note that resources are not distributed any nodes by default.
BASELINE VS FINAL DEVICE CONFIGURATION
Broadly speaking, there are two approaches to secure provisioning using ZTP. You may use strict matching and distribution settings to provision specific devices with unique, final configurations. Alternatively, you may use laxer matching and wider distribution settings to provision many devices with a baseline configuration, for example, "just enough configuration" to route to a central production configuration system for final configuration and service provisioning. You may also combine the two approaches, for example, use a reverse MAC address match to opt a specific device or devices out of an otherwise general, baseline configuration.
RUN A SCRIPT ON A NEWLY PROVISIONED DEVICE
Note: Post-provisioning scripting is an advanced feature only supported by Operations Manager nodes.
It is possible to upload a script and associated with a device Resource Bundle, to be run by remote Operations Manager node after a resource is considered provisioned. A device is considered to be in a provisioned state after it has downloaded all of the files in the Resource Bundle it is being provisioned with.
24.12.1
Advanced Functionality
325
Lighthouse User Guide
The script may be uploaded and associated via the UI during Resource Bundle creation using the Post-Provisioning Script option, or via git/scp and the CLI based workflow. Scripts may be implemented in bash, Python 2 or Python 3, and must start with a shebang i.e. the first line must be one of:
#!/bin/bash
#!/usr/bin/env python2
#!/usr/bin/env python3
l Scripts are run in a monitored background processes in the Secure Provisioning container (remote-dop) on the node.
l Scripts have a default 15 minute timeout, this can be manually configured in the YAML config (post_provision_script_timeout).
l Scripts may login to target device via the network using SSH key auth where nom_remote_ ssh_pub_key has been injected into the device config, or using username/password with the sshpass command.
MONITOR THE ZTP PROGRESS OF A RESOURCE
The current provisioning state of resources can be monitored via syslog on the Operations Manager (local devices only) or Lighthouse (all devices). Each Secure Provisioning syslog message contains a prefix identifying the MAC address of the device being provisioned, similar to:
[NetOps-DOP device="01:23:45:67:89:AB"]
For example, here are sample messages showing an Opengear ACM7004 device being provisioned:
24.12.1
Advanced Functionality
326
Lighthouse User Guide
[NetOps-DOP device="00:13:C6:EF:00:08"] Received DHCP request from device with vendor ID Opengear/ACM7004-5-LMR [NetOps-DOP device="00:13:C6:EF:00:08"] Assigned DHCP address of 10.0.0.2 to device [NetOps-DOP device="00:13:C6:EF:00:08"] Provisioning device with resource bundle my\_acm7004 [NetOps-DOP device="00:13:C6:EF:00:08"] Device retrieved resource file /files/acm7004-5-4.3.1.flash via HTTP/HTTPS
Syslog can be viewed from the CLI by running:
tail -F /var/log/messages | grep NetOps-DOP
WAN GATEWAY SERVICES
In addition to LAN provisioning, the node can utilize its built-in cellular connection to act as a WAN gateway and provide a proxy to essential services for devices on day one.
The node's DHCP server hands out the node's address as:
Server
Description
NTP server
This is a local service, synced to the node's system clock.
DNS server
DNS lookups by devices are relayed via Lighthouse VPN, to the DNS server that Lighthouse is configured to use.
Syslog server
Note that incoming syslog messages are dropped unless LogZilla for NetOps Automation has been activated.
Default gateway
When the node is configured in cellular router mode (i.e. with forwarding and masquerading enabled), devices can route to external services, for example, to enroll with third-party management systems for additional configuration.
24.12.1
Advanced Functionality
327
Lighthouse User Guide
ADVANCED OPTIONS
USE VARIABLES IN CONFIGURATION FILE TEMPLATES
In addition to static files, you may create templated ZTP configuration or script files. This is useful if your file is required to reference site-specific values such as an assigned IP addresses.
Any file uploaded via the web UI, or into the downloads directly with a file suffix of .j2 (Jinja2) will be automatically templated. The .j2 suffix is stripped when serving templated files to devices.
Advanced Variable
Description
Example
{{ nom_remote_server }}
Address of provisioning interface on the node.
10.0.0.1
{{ nom_remote_interface }}
Name of provisioning interface on
net2
the node .
{{ nom_remote_netmask }}
Netmask of provisioning interface on the node (and netmask assigned in DHCP offers).
255.255.255.0
{{ nomremotenetmaskcidr }}
CIDR format netmask (prefix
24
length) of provisioning interface
on the node
{{ nom_remote_ntp_server }}
Address of NTP server assigned in DHCP offers (same as nom_ remote_server)
10.0.0.1
{{ nom_remote_dns_server }}
Address of DNS server assigned in DHCP offers (same as nom_ remote_server)
10.0.0.1
24.12.1
Advanced Functionality
328
Lighthouse User Guide
Advanced Variable {{ nom_device_ipv4_address }} {{ nomremotesshpubkey }}
{ nom_device_hostname }} { nom_device_mac_address }}
Description
Example
This feature is only supported by Operations Manager nodes. DHCP address assigned to target device.
10.0.0.13
Public part of an auto-generated SSH keypair on the remote node, which may be injected into device config to pre- authenticate the node for any post-provisioning activities.
This feature is only supported by Operations Manager nodes.Hostname advertised by target device.
router
MAC Address of target device.This feature is only supported by Operations Manager nodes.]
00:12:34:56:78:9A
For example, a basic Cumulus templated provisioning script may look like: cumulus_setup.sh.j2
#!/bin/bash curl tftp://{{nom_remote_server}}/cumulus_interfaces > /etc/network/interfaces
POST-PROVISIONING SCRIPTS
Note: This feature is only supported by Operations Manager nodes.
24.12.1
Advanced Functionality
329
Lighthouse User Guide
It is possible to upload a script and associated with a device Resource Bundle, to be run by remote Operations Manager node when a resource is considered provisioned. A device is considered to be in a provisioned state after it has downloaded all of the files in the Resource Bundle it is being provisioned with. The script may be uploaded and associated via the UI during Resource Bundle creation using the Post-Provisioning Script option, or checked-in to the downloads directly via git/scp and specified in the YAML configuration for the device Resource Bundle:
demo_arista: device_type: arista config_file: 'demo_arista.cfg' image_file: 'arista_eos.swi' post_provision_script: arista_fixups_over_ssh.py post_provision_script_timeout: 900
Scripts may be implemented in bash, Python 2 or Python 3, and must start with a shebang i.e. the first line must be one of:
#!/bin/bash #!/usr/bin/env python2 #!/usr/bin/env python3
Notes: l Scripts are run in a monitored background processes in the Secure Provisioning container
(remote-dop) on the node. l Scripts have a default 15 minute timeout, this can be manually configured in the YAML config
(postprovisionscripttimeout_). l Scripts may login to target device via the network using SSH key auth where
nomremotesshpubkey has been injected into the device config (see Templated resource above), or using username/password with the sshpass command.
24.12.1
Advanced Functionality
330
ORDERED PROVISIONING
Lighthouse User Guide
Note: This feature is only supported by Operations Manager nodes.
The Provision After option allows you to create basic dependency chains, to enforce the order in which devices are provisioned. In certain scenarios it may be advantageous to control the order in which devices are provisioned, for example: l Ensure security infrastructure is provisioned ahead of systems that may other become
inadvertently exposed on the network. l Bring the production WAN up early to allow devices to provision services in-band, saving
cellular data. l Disallow local user access to the LAN until the network is fully up and running. When a secondary Resource Bundle has the Provision After option set, the node will not respond to ZTP requests for these resources until all required dependencies have been met. The Provision After property lists of one or more other, required Resource Bundles. Each required Resource Bundle creates a dependency that at least one device has been provisioned using the required bundle. If multiples of a particular required device must be provisioned before a secondary device, simply specify the dependency multiple times in the list. You may configure this via the UI during Resource Bundle creation using the Provision After option, or directly via git/scp in the YAML configuration for the device Resource Bundle:
access_switch: device_type: juniper config_file: 'jn-switch35.config' image_file: 'jinstall-ex-4200-13.2R1.1-domestic-signed.tgz' provision_after: - branch_router
24.12.1
Advanced Functionality
331
Lighthouse User Guide
TROUBLESHOOT SECURE PROVISIONING
SECURE PROVISIONING CONSISTS OF SEVERAL DOCKER CONTAINERS
Container central-dop dop-ui remote-dop
Description
The container runs on Lighthouse, hosting git repository.
The container runs on Lighthouse, serving the Secure Provisioning web UI.
The container runs on Operations Manager nodes, running DHCP and TFTP/HTTP ZTP services.
Additionally, the deployment container runs on Lighthouse, orchestrates new module installation on Lighthouse and nodes.
TROUBLESHOOTING COMMANDS FOR NETOPS MODULES
Command
Description
docker ps
View running Docker containers.
docker exec -ti container-name bash
Spawn a bash shell inside a container.
docker logs container-name
View logs of a container.
docker exec -ti deployment ansible-playbook -vvv /ansible/dop_2.0.0.yml
Manually run module deployment in verbose mode, on Lighthouse.
24.12.1
Advanced Functionality
332
Command etc/scripts/post-receive /etc/scripts/netops_ui_handler
Lighthouse User Guide
Description
Manually push ZTP resources from Lighthouse to Operations Manager nodes (inside central-dop container).
If the Lighthouse UI fails to display after an upgrade, it's possible a NetOps UI component is failing to load and may be able to recover by running this command.
IP ACCESS
Note: The availability of this module is dependent on your subscription type.
The Lighthouse IP Access feature allows an engineer to reach hosts on a remote site via an OpenVPN client through Lighthouse, over the Lighthouse VPN fabric, without physically traveling to the site. If IP Access is enabled for Lighthouse, it can be managed from using NetOps > IP Access on the Lighthouse web UI menu. IP Access adds client VPN capability to Lighthouse. Network engineers, firewall and server administrators can launch a VPN client connection to Lighthouse, be authenticated, and then automatically connected to the remote site management network. The client PC has a secure VPN tunnel to the remote equipment the user is required to work on, providing the same TCP/IP access they would get if they travelled to the site and plugged into the management LAN. The client can then access target devices on the remote network directly by their usual IP addresses and network ports. Requests from the client are masqueraded behind the node's IP address, so no additional routing configuration is required on the target devices.
Note: If you want to unenroll a node(s) that is running IP Access, it is recommended to push the Disable IP Access template to the node BEFORE you unenroll otherwise the VPN may still form a connection. See Disable NetOps Modules via Template.
24.12.1
Advanced Functionality
333
Lighthouse User Guide
CONNECTIVITY
By default, IP Access connects the client to the Management LAN of the Opengear appliance, or the interfaces in the LAN zone for the OM Series. A route for the directly attached subnet, plus any static routes configured on that interface (but never the default route) are also pushed automatically to the OpenVPN client.
In the diagram, the client PC has a virtual tunnel interface with a route to the yellow management network, and the user can access any target IP devices on the yellow network using their real IP addresses.
The basic configuration of this feature is:
l Activate the IP Access NetOps module this starts the OpenVPN service in a Docker container on Lighthouse.
l Activate the IP Access NetOps module on each node you want to use for IP Access this installs a remote connector service to allow the IP Access bridge to be created.
24.12.1
Advanced Functionality
334
Lighthouse User Guide
l Generate a certificate and export an associated OpenVPN client configuration file. l Import the configuration into your preferred OpenVPN client. The basic operation of this feature is: l Connect the tunnel this starts a connection to Lighthouse on UDP port 8194. l Authenticate when prompted using your Lighthouse credentials, appending the node name to
your Lighthouse username client certificate authentication is automatic, this is a second factor of authentication. l Wait a moment for the connection to complete this builds the GRE bridge between the client and pushes routes to the node's remote network(s). While connected, the client can access IP addresses on the node's remote network(s) LAN directly, for example, by using the ping command or by typing them into the browser address bar.
NODES SUPPORTED BY IP ACCESS
Opengear OM1200, OM2200, CM8100, ACM7000 and IM7200 nodes may be activated as IP Access nodes, to allow IP Access to their directly connected remote networks via Lighthouse.
Note: Other vendors/models are not currently supported.
To view the available nodes supported by IP Access: 1. In the Menu Pane, select NetOps > IP Access.
The IP ACCESS page displays. 2. Select the NODE ACCESS tab.
USE ADVANCED OPTIONS OF IP ACCESS
The Advanced options of the IP Access page enable you to set a number of features, including setting expiry of certificates lifetime, changing default connection routes and enabling policies.
24.12.1
Advanced Functionality
335
Lighthouse User Guide
IP Access connects the client to the Management LAN or LAN zone by default, which is intended for deployments where the target devices are connected to those interfaces. If the Opengear appliances are deployed into a different or more complex network environment, then there are some advanced options that the Lighthouse administrator can use to control the IP Access connectivity, and these are described below.
CONNECT TO WAN ZONE
By default, IP access connects the client to the management LAN zone. To enable IP Access for the WAN zone: 1. In the Menu Pane, select NetOps > IP Access.
The IP ACCESS page displays. 2. Select the ADVANCED OPTIONS tab. 3. Select the Push Wired WAN Routes checkbox to push routes for nodes' wired WAN interface
to clients. 4. Click Apply.
Note: This is a global configuration and will affect all node that are enabled for IP Access.
In this case, the customer must have deployed Opengear appliances with the Network Interface (NET1) connected to the management network or facing target devices, and it results in IP Access connecting the client to the WAN (NET1) interface.
NETWORK ACCESS POLICIES FOR OPERATIONS MANAGER
In a more complex deployment, Opengear appliances may be connected to multiple networks or virtual networks (VLANs), and in these cases it is often important to be able to control which of these networks each authenticated IP Access user is able to access.
24.12.1
Advanced Functionality
336
Lighthouse User Guide
This feature is only supported on Operations Manager or OM Series appliances, which support the zone-based firewall, designed to work with multiple VLANs and the optional built-in Ethernet switch with layer-3 capable ports. This flexibility and control is very useful, especially for customers who have a number of separate management networks (or VLANs) for different administrative teams. The Network Access Policy mechanism on Lighthouse provides a way to dynamically map IP Access users, based on their group membership, to the firewall zone(s) that they can access on the Nodes. Each firewall zone is a collection of network interfaces which is configured on each Opengear appliance or Node. Firewall zones are used to provide policy abstraction by logical zone names the physical or virtual interfaces on each Node may vary by site, but the zone names must stay consistent. It is recommended that zones and names are planned out in advance of implementation. A firewall zone is a collection of network interfaces which is configured on each Opengear appliance or Node in Lighthouse terminology. The Network Access Policy mechanism on Lighthouse provides a way to map users, based on their group membership, to the firewall zone(s) that they can access on the Nodes.
UNDERSTAND ACCESS POLICIES
Putting it all together, when a user authenticates to Lighthouse, they are mapped into one or more group(s), which map into firewall zone(s), which allow authenticated users to reach the appropriate network interfaces(s), including switch ports or VLANs, via IP Access. For example, users who belong to the security group may get mapped into the secops (security operations) zone. On each OM appliance, the appropriate switch port(s) and/or VLAN(s) for security operations should be configured to be in the secops zone. Similarly, users in the server group may get mapped into the serverops zone, and again on the OM appliances the appropriate interfaces can be configured to be part of the serverops zone.
24.12.1
Advanced Functionality
337
Lighthouse User Guide
The result is that members of the security group get IP Access to the networks in the secops zone, and members of the server group get IP Access to the networks in the serverops zone, for each node that they connect to.
SET UP NETWORK ACCESS POLICIES
To enable this feature: 1. In the Menu Pane, select NetOps > IP Access.
The IP ACCESS page displays. 2. Select the ADVANCED OPTIONS tab. 3. Check Network Access Policies for Operations Manager Enabled. 4. Click Apply.
SET ACCESS POLICIES
Note: A policy must be configured for each group whose members will use IP Access.
1. In the Menu Pane, select NetOps > IP Access. The IP ACCESS page displays.
2. Select the NETWORK ACCESS POLICIES tab.
Note: The group to zone mapping column ZONES is empty by default.
3. Select the GROUP to view details. The Group Details page is displayed.
4. Click on + Add Zone to add one or more firewall zones for this group. 5. Select the firewall zone and click Add.
The NETWORK ACCESS POLICIES tab now displays the group with the Firewall zone.
24.12.1
Advanced Functionality
338
Lighthouse User Guide
TROUBLESHOOT IP ACCESS
The most effective way to troubleshoot IP Access is to view the logs.
VIEW THE DOCKER LOGS
Run the following command on Lighthouse, either as root or with sudo (for non-root admins):
sudo docker logs -t central-sdi
The logs for the central-sdi Docker container, which controls client IP Access display.
2022-10-03T10:03:19.051579136Z INFO:root:[NetOps-SDI node="nodes-36" username="maverick"] VPN client authenticated 2022-10-03T10:03:19.094313762Z 2.29.37.12:65437 TLS: Username/Password authentication succeeded for username 'maverick123:OM1208-UK2' 2022-10-03T10:03:19.422971278Z 2.29.37.12:65437 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSASHA256 2022-10-03T10:03:19.422999989Z 2.29.37.12:65437 [LH5-UK3-22] Peer Connection Initiated with [AF_INET]2.29.37.12:65437 2022-10-03T10:03:22.000300953Z INFO:root:[NetOps-SDI node="nodes-36" username="maverick123"] VPN client connected with IP 172.31.0.8 netmask 255.255.0.0 2022-10-03T10:03:22.084275387Z LH5-UK3-22/2.29.37.12:65437 OPTIONS IMPORT: reading client specific options from: /tmp/openvpn_cc_3aa5d19c3ea09b3bbac56f6bacf7b6e.tmp 2022-10-03T10:03:22.084324213Z LH5-UK3-22/2.29.37.12:65437 Data Channel: using negotiated cipher 'AES-256-GCM' 2022-10-03T10:03:22.084332293Z LH5-UK3-22/2.29.37.12:65437 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2022-10-03T10:03:22.084337215Z LH5-UK3-22/2.29.37.12:65437 Incoming Data Channel:
24.12.1
Advanced Functionality
339
Lighthouse User Guide
Cipher 'AES-256-GCM' initialized with 256 bit key 2022-10-03T10:03:22.084342034Z LH5-UK3-22/2.29.37.12:65437 SENT CONTROL [LH5-UK322]: 'PUSH_REPLY,ping 10,ping-restart 120,route 192.168.2.0 255.255.255.0 172.31.0.1 1,ifconfig 172.31.0.8 255.255.0.0,peer-id 0,cipher AES-256-GCM' (status=1) 2022-10-03T10:03:22.084950386Z LH5-UK3-22/2.29.37.12:65437 PUSH: Received control message: 'PUSH_REQUEST' 2022-10-03T10:03:22.085204467Z LH5-UK3-22/2.29.37.12:65437 PUSH: Received control message: 'PUSH_REQUEST' 2022-10-03T10:03:22.085220316Z LH5-UK3-22/2.29.37.12:65437 PUSH: Received control message: 'PUSH_REQUEST' 2022-10-03T10:03:22.432350278Z LH5-UK3-22/2.29.37.12:65437 PUSH: Received control message: 'PUSH_REQUEST' 2022-10-03T10:03:23.120616769Z INFO:root:[NetOps-SDI node="nodes-36" username="maverick"] VPN client identified by MAC c6:87:ca:4a:3b:2c
Note the PUSH_REPLY line above shows that the IP Access client has been pushed the route to the network 192.168.2.0/24 which in this case is the interface on this Node in the firewall zone that the user was mapped into. (Unfortunately, the firewall zones are not listed in this log output). If there are errors with authentication, then they will show up here.
USE THE ROUTING TABLE
When troubleshooting IP Access it is useful to look at the routing table on the target Node to make sure that routes to the target networks are installed. If the interface is down, for example, then the route is not present and will not be pushed to the client. The following commands can be used to display the routing table on the target OM Series Node: l route l ip route Displaying the Routing table with the route command:
24.12.1
Advanced Functionality
340
Lighthouse User Guide
root@OM1208-UK2:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default _gateway 0.0.0.0 UG 110000001 0 0 net1 5.5.5.0 0.0.0.0 255.255.255.0 U 0 0 0 sw0p8 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.31.0.0 0.0.0.0 255.255.0.0 U 0 0 0 ipa-br0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 net2 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 net1 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 sw0p2 192.168.128.0 0.0.0.0 255.255.224.0 U 0 0 0 tun0 root@OM1208-UK2:~# root@OM1208-UK2:~# ip route default via 192.168.1.1 dev net1 proto static metric 110000001 5.5.5.0/24 dev sw0p8 proto kernel scope link src 5.5.5.5 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.31.0.0/16 dev ipa-br0 proto kernel scope link src 172.31.0.1 192.168.0.0/24 dev net2 proto kernel scope link src 192.168.0.48 192.168.1.0/24 dev net1 proto kernel scope link src 192.168.1.48 192.168.2.0/24 dev sw0p2 proto kernel scope link src 192.168.2.8 192.168.128.0/19 dev tun0 proto kernel scope link src 192.168.128.6 root@OM1208-UK2:~#
The ip command output is useful as it shows the interface IP address of the OM, which should be reachable via IP Access as long as that interface is up. Other standard network troubleshooting techniques can be used from the Node. For example testing the ability to ping a target device, or using curl if it has an http or https interface. Example:
ping 192.168.2.4 curl -k https://192.168.2.4/
24.12.1
Advanced Functionality
341
AUTOMATION GATEWAY
Lighthouse User Guide
Note: The availability of this module is dependent on your subscription type.
Opengear allows you to set up your network using automation tools.
Automation Gateway allows Lighthouse users and automation code to discover and manage IPbased management interfaces via the Opengear management system, with the same level of simplicity and efficiency as if they were serial consoles.
Resources like firewalls and servers may present an IP-based management interface in addition to (or sometimes instead of) the traditional serial or USB console port. This interface may serve a web-based GUI, VNC or RDP based KVM, SSH-based CLI and/or a programmable network API like RESTful HTTPS. The device itself may be physical or virtual.
By their nature, the IP-based management interfaces are more dynamic (for example, they may change IP address), varied (for example, protocols vary from device to device) and harder to reach (for example, on an un-routable private network).
The Automation Gateway module addresses the challenges of discovering, auditing and connecting to IP-based management services in a distributed, heterogeneous network. It is available on Operations Manager product lines, OM120x and OM22xx.
Notes: Opengear is transitioning from Automation Gateway (AG) to Connected Resource Gateway (CRG) for access, control, and management of connected resources: l CRG will be the primary solution moving forward, offering improved scalability, security,
and continued enhancements. l New users should begin with CRG as the recommended option, while existing AG users
are encouraged to migrate to CRG. l AG discovered resources are not automatically accessible on CRG. l To migrate to CRG, you must set up CRG as if you are setting up a new implementation,
see Set up Lighthouse as a Connected Resource Gateway (CRG).
24.12.1
Advanced Functionality
342
Lighthouse User Guide
DIFFERENCES BETWEEN IP ACCESS AND AUTOMATION GATEWAY
The IP Access module provides the IP Access feature and the Automation Gateway module provides the Automation Gateway feature. These two features are similar in that they both allow Lighthouse users to access network services on remote resources, however they accomplish this in different ways. One way to think about it is that IP Access transports the user to the remote network, whereas Automation Gateway transports a specific remote network service to user.
IP ACCESS
Using IP Access, the user must establish a VPN tunnel from their computer to Lighthouse, which then provides them with a routed connection to the entire network(s) connected to the remote node. When the tunnel is up, the user can access any network service on any network device by their standard management IP addresses.
AUTOMATION GATEWAY
Using the Automation Gateway feature, the user clicks through their existing Lighthouse browser session to access HTTP/HTTPS web GUI services of specific devices that have been discovered by the remote node. Access is limited to these services only, and the connections are proxied via Lighthouse's central address so no client or network reconfiguration is required.
CONNECT TO A REMOTE RESOURCE
Using Automation Gateway, Lighthouse users can connect to the web UI of a remote physical & virtual resource such as a firewall, lights-out server or SD-WAN appliance. Access is proxied via Lighthouse VPN via a remote node, allowing simply, point & click access to what may be an otherwise unreachable remote device.
24.12.1
Advanced Functionality
343
Lighthouse User Guide
TO ACTIVATE THE AUTOMATION GATEWAY ON AN ENROLLED NODE
Note: To perform these steps, a Lighthouse web UI as a user with at least NetOps Modules: Read Only permission, and at least Nodes & Devices (Base): Read Only permission for the activated node. 1. In the Menu Pane, select NetOps > Automation Gateway from the main menu. The AUTOMATION GATEWAY page displays. 2. In the FILTER BY menu, select HTTPS or HTTP from the Services drop-down. 3. Locate the remote device by hostname or IP address.
Tip: If many remote devices have been discovered, use the FILTER BY menu to search by full or partial device hostname or IP address.
4. To initiate an Automation Gateway session, click the device's web UI icon. You are now connected the web UI of the remote device.
Note: While an Automation Gateway session is active, all new browser tabs and windows that connect to Lighthouse are proxied through to the remote device web UI.
5. To close the Automation Gateway session, click the link at the bottom of the device web UI:
This system is being accessed via Lighthouse - click here to return to Lighthouse
CONNECT WITH REST/HTTP/HTTPS APIS
Automation Gateway allows central automation code to reach the HTTP/S API services running on devices on remote networks. For more details refer to the latest documentation: l https://ftp.opengear.com/download/documentation/api/lighthouse/
24.12.1
Advanced Functionality
344
Lighthouse User Guide
This is accomplished by modifying the request to add the X-Ip-Access-Auth HTTP header to your API request, and substituting the device's remote IP with Lighthouse's central IP. Requests containing the header are reverse proxied via Lighthouse then via an Operations Manager node that is local to the remote device. The example Python (3.5+) code below illustrates this. Note that this code is primarily for illustrative purposes with no error handling or modularity, for clarity & brevity. The device being accessed in this example is an HP ILO's Redfish REST API service.
#!/usr/bin/env python3 # Example code showing how to reach a remote device REST API via Opengear # Lighthouse Automation Gateway -> Operations Manager node -> device # # This code is primarily for illustrative purposes with no error handling # or modularity, for clarity & brevity
import requests import json import base64
# Authenticate to Lighthouse
lighthouse_address = '192.168.67.20' lighthouse_account = 'root' lighthouse_password = 'default'
data = { 'username': lighthouse_account, 'password': lighthouse_password } r = requests.post('https://%s/api/v3.7/sessions/' %
lighthouse_address, data=json.dumps(data), verify=False) lh_token = json.loads(r.text)['session']
print('Authenticated to Lighthouse, token %s' % lh_token)
24.12.1
Advanced Functionality
345
Lighthouse User Guide
lh_headers = { 'Authorization': 'Token ' + lh_token }
# Find the node that is local to the remote device's API service
device_address = '10.0.0.71' # Equivalent to the UI fields under CONFIGURE > device_service = 'https' # AUTOMATION GATEWAY > Devices > Filter By
r = requests.get('https://%s/api/v3.7/nom/ag/devices?ip=%s&service=%s' % (lighthouse_address, device_address, device_service), headers=lh_headers, verify=False)
j = json.loads(r.text)
print(json.dumps(j, indent=4))
for _device in j['devices']: for _host in _device['hosts']: for _service in _host['services']: if _service['nmap']['name'] != device_service: continue for _avail in _service['availability']: node_id = _avail['id'] print('Service available via %s' % node_id) break
# Generate Automation Gateway token
data = { 'session': lh_token, 'request_type': 'new', 'url': 'https://%s' % device_address, 'node': node_id }
r = requests.post('https://%s/api/v3.7/nom/ag/auth_tokens' % lighthouse_address, data=json.dumps(data), headers=lh_headers, verify=False)
24.12.1
Advanced Functionality
346
Lighthouse User Guide
j = json.loads(r.text) ag_token = j['token']
print('Automation Gateway token is %s' % ag_token)
ag_headers = { 'X-Ip-Access-Auth': ag_token }
# Now we can query the device API using the Lighthouse address, by including # the access token in the request headers
# The remaining code is specific to the device being accessed. this example # hits a Redfish-compliant REST API
device_username = 'baz' device_password = 'foobarfoobar' device_auth = base64.b64encode(('%s:%s' %
(device_username, device_password)).encode('utf-8')).decode('utf-8') device_headers = { 'Authorization': 'Basic %s' %
device_auth, 'Content-Type': 'application/json' }
# Add the access token to whatever headers you'd usually use to talk to the # device's native API -- this header will be stripped by Automation Gateway
_headers = { **ag_headers, **device_headers }
r = requests.get('https://%s/redfish/v1/systems/1/' % lighthouse_address, headers=_headers, verify=False)
j = json.loads(r.text) print(json.dumps(j, indent=4))
24.12.1
Advanced Functionality
347
Lighthouse User Guide
AUTOMATION GATEWAY SERVICE DISCOVERY
Automation Gateway discovery process can take a varied amount of time to complete, entirely based on the size of your scannable network. Services discovered by Automation Gateway are listed in the Lighthouse web UI, under NetOps > Automation Gateway. The discovery process can be restarted using the Rescan Devices button on the NetOps > Automation Gateway page. When an HTTP or HTTPS service has been discovered, it may also be accessed via this page. When a node has been activated for Automation Gateway, it begins to discover remote services. The discovery process is initiated by Lighthouse, and runs every 10 minutes. Each time the discovery process is initiated, the node runs an nmap script scan against all IPv4 connections belonging to the node's LAN firewall zone.
Note: Large logical networks with address space larger than 254 hosts (i.e. with a minimum netmask of /24 or 255.255.255.0) are excluded from the scan.
The nmap scan runs the default (non-intrusive) suite of nmap NSE scripts. These can be listed by running the following command on a node that has been activated for Automation Gateway:
sudo docker exec ag-remote cat /usr/share/nmap/scripts/script.db | awk -F\" '/"default"/ { print $2 }'
ACCESS MULTIPLE VLANS OR PORTS
There are several ways a user can access multiple target networks, virtual networks (VLANs) or physical ports.
24.12.1
Advanced Functionality
348
Lighthouse User Guide
GROUP MEMBERSHIPS
A user may belong to multiple groups, in which case they will have access to the sum of the zones mapped to those groups, in the same way port access works for Console Gateway and Node Filters matching. Note that this works regardless of Local or Remote user authentication on Lighthouse; user authorization (which determines access to Nodes and resources, and now firewall zones) is always derived from group membership.
FIREWALL ZONES
In the NetOps > IP Access dashboard under the NETWORK ACCESS POLICIES tab, each group can be configured to have access to one or more firewall zones. Some groups can be configured to have access to no zones, some to just one zone, and other groups to have access to multiple zones.
MULTIPLE LAYER 3 NETWORK CONNECTIONS
On each Node a layer 3 network connection or "conn" is required on the OM to communicate with other hosts on a network or VLAN. Multiple conns on each OM can be mapped into the same firewall zone. This may be used to provide access to multiple switch ports, though it is perhaps more likely that those switch ports would be configured in a bridge group if they are all part of the same LAN, and the bridge group only requires a single layer 3 conn. If multiple LANs or virtual LANs (VLANs) are managed by the same team, then it may make sense to combine them into the same firewall zone. Warning: The supported appliance's firewall will allow traffic to pass between interfaces in the same firewall zone, so to maintain security, multiple "separate" management VLANs should not be configured in the same zone, but should each have its own zone. If required, one of the mechanisms above can be used to allow user access to multiple zones and therefore to multiple "separate" VLANs.
24.12.1
Advanced Functionality
349
Lighthouse User Guide
COMMAND LINE TOOLS
Lighthouse includes a web-based terminal. To access this bash shell instance: 1. In the Menu Pane, select Terminal.
A login prompt displays 2. Enter an administrator username and press Enter.
A password: prompt displays. 3. Enter the administrator password and press Enter.
A bash shell prompt displays. This shell supports most standard bash commands and also supports copy-and-paste to and from the terminal.
24.12.1
Command Line Tools
350
Lighthouse User Guide
CERT_MANAGE
Caution: l Running cert_manage run may cause nodes to temporarily disconnect from Lighthouse,
and/or secondary Lighthouse instances to temporarily disconnect from the primary. l The certificate manager may take a while to complete. If running manually, do not interrupt
the process. l Renewing a CA certificate will result in each node being updated with the new CA details. A
status summary of these update jobs can be shown using cert_manage status. It is recommended that these be allowed to complete before using cert_manage run to make further changes. If renewing the CA and Lighthouse VPN certificates, the certificate processing will occur on separate scheduled runs to avoid a limitation where the Lighthouse VPN certificate is renewed before all nodes are informed of the CA renewal. If the Lighthouse VPN certificate renewal is forced too early, any nodes that did not receive the CA renewal notification will be disconnected and will require re-enrollment into Lighthouse.
Command
Description
cert_manage
l The cert_manage CLI tool can only be run on a primary lighthouse, by a root user. A lighthouse user may sudo to assume root permissions.
l This tool cannot be run on a secondary Lighthouse. l The cert_manage tool is not tied to a specific license or subscription. l Certificate renewal jobs are scheduled using cron to run at 1am (Lighthouse time),
every day. An administrator may choose to update the frequency of the cron job under /etc/cron.d/rotate_certificates.cron.
24.12.1
Command Line Tools
351
Lighthouse User Guide Syntax cert_manage [-h] [--config CONFIG_URI] {run,renew,show,status,validity,offset,logs}
Option -h | --help --config CONFIG_URI
Description Display usage information and exit. Config file for lipy.
Sub-Command run renew
show status validity offset
logs
Description
Process certificates due for renewal (current time > renewal time) and rotate them.
Schedule certificates for early renewal. Updates the renewal time of specified certificates to current time. The next certificate manager run will renew them. This will happen overnight or can be triggered using the run command
Show certificate or default value information. Display information for all specified certificates, or it can display the default values that are used for newly created certificates.
Show status summary including job status.
Set default validity period for new certificates.
Set renewal offset period in days to update the delta between expiry and renewal time for the specified certificates. The renewal period is calculated from the certificate expiry date using the offset.
Prints the last 20 logs from the log file /var/log/cert_manager.log.
24.12.1
Command Line Tools
352
SUB-COMMAND :: RUN
Syntax cert_manage run [-h] [--dry-run]
Lighthouse User Guide
Option -h | --help --dry-run
Description Display usage information and exit. Lists affected certificates.
SUB-COMMAND :: RENEW
Syntax
cert_manage renew [-h] (--cn COMMON_NAMES [COMMON_NAMES ...] | --ca | --nodes | -all-clients) [--dry-run]
Option
Description
-h | --help
Display usage information and exit.
--cn COMMON_NAMES [COMMON_ NAMES ...]
Specify certificates by Common Name.
--ca
Certificate Authority certificate.
--nodes
Certificates for all enrolled nodes.
24.12.1
Command Line Tools
353
Option --all-clients --dry-run
Lighthouse User Guide Description All existing client certificates. Lists affected certificates without executing the action.
SUB-COMMAND :: SHOW
Syntax
cert_manage show [-h] (--cn COMMON_NAMES [COMMON_NAMES ...] | --ca | --nodes | -all-clients | --defaults)
Option
Description
-h | --help
Display usage information and exit.
--cn COMMON_NAMES [COMMON_ NAMES ...]
Specify certificates by Common Name.
--ca
Certificate Authority certificate.
--nodes
Certificates for all enrolled nodes.
--all-clients
All existing client certificates.
--defaults
Show certificate defaults.
24.12.1
Command Line Tools
354
Lighthouse User Guide
SUB-COMMAND :: VALIDITY
Syntax cert_manage validity [-h] --days NUM_DAYS (--default-client | --default-ca) [--dryrun]
Option -h | --help --days NUM_DAYS --default-client --default-ca dry-run
Description Display usage information and exit. Number of days from current time. Specify the default value for new client certificates. Specify the default value for new CA certificates. Lists affected certificates without executing the action.
SUB-COMMAND :: OFFSET
Syntax
cert_manage offset [-h] --days NUM_DAYS (--cn COMMON_NAMES [COMMON_NAMES ...] | --ca | --nodes | --all-clients | --default-client | --default-ca) [--dry-run]
Option -h | --help
Description Display usage information and exit.
24.12.1
Command Line Tools
355
Lighthouse User Guide
Option
Description
--days NUM_DAYS
Number of days from expiry.
--cn COMMON_NAMES [COMMON_ NAMES ...]
Specify certificates by Common Name.
--ca
Certificate Authority certificate.
--nodes
Certificates for all enrolled nodes.
--all-clients
All existing client certificates.
--default-client
Specify the default value for new client certificates.
--default-ca
Specify the default value for new CA certificates.
dry-run
Lists affected certificates without executing the action.
SUB-COMMAND :: LOGS
Syntax cert_manage logs [-h]
Option -h | --help
Description Display usage information and exit.
24.12.1
Command Line Tools
356
CRON
Command crontab
Lighthouse User Guide
Description The cron service can be used to schedule file execution at specific times. The server daemon executes commands at specified dates and times based on the entries in the cron jobs table. The service can be managed via the /etc/init.d/crond interface, and the cron tables managed via crontab.
Syntax crontab [options] file crontab [options] crontab -n [hostname]
Option -u <user> -e
-l
Description
Define user.
Edit user's crontab. l Each line can contain one command to run. l The following format is used: minute hour day-of-month month day-of-
week command. l When finished, save and close the crontab file.
List user's crontab.
24.12.1
Command Line Tools
357
Option -r -i -n <host> -c -x <mask>
Description Delete user's crontab. Prompt before deleting. Set host in cluster to run users' crontabs. Get host in cluster to run users' crontabs. Enable debugging.
Lighthouse User Guide
Related Command /etc/init.d/crond start /etc/init.d/crond stop /etc/init.d/crond restart /etc/init.d/crond status
Description To start the crond service. To stop the crond service. To restart the crond service. To verify the current crond status.
24.12.1
Command Line Tools
358
MASS_ENROLL_NODES
Command mass_enroll_nodes
Description A tool to enroll nodes.
Lighthouse User Guide
Syntax
mass_enroll_nodes [-h] [--lh-address LH_ADDRESS] [--dry-run] [--insecure] [--autoapprove] [--preflight] --lh_username LH_USERNAME --lh_password LH_PASSWORD --node_ addresses NODE_ADDRESSES --node_username NODE_USERNAME --node_password NODE_PASSWORD
Required
Option -h
Alternate Syntax --help
-a <LH_ADDRESS>
--lh-address <LH_ ADDRESS>
-d
--dry-run
-i
--insecure
-x
--auto-approve
Description
Display usage information and exit.
The address of the Lighthouse to enroll nodes to (default=localhost).
Don't actually enroll anything - just list the nodes that would be enrolled.
Don't verify https certificates. This is only recommended for localhost.
Automatically approve nodes when they reply.
24.12.1
Command Line Tools
359
Required
Option y
Alternate Syntax --preflight
Y
-u <LH_USERNAME>
--lh_username <LH_
USERNAME>
Y
-p <LH_PASSWORD>
--lh_password <LH_
PASSWORD>
Y
-n <NODE_
ADDRESSES>
--node_addresses <NODE_ADDRESSES>
Y
-U <NODE_USERNAME> --node_username
<NODE_USERNAME>
Y
-P <NODE_PASSWORD> --node_password
<NODE_PASSWORD>
Lighthouse User Guide
Description
Run the preflight enrollment check.
The username of a Lighthouse root/admin user.
The password of a Lighthouse root/admin user.
A comma-separated list of opengear node addresses. They must all have the same username/password.
The username for all of the nodes to be enrolled.
The password for all of the nodes to be enrolled.
24.12.1
Command Line Tools
360
MASS_UNENROLL_NODES
Command mass_unenroll_nodes
Description A tool to unenroll nodes.
Lighthouse User Guide
Syntax
mass_unenroll_nodes [-h] [--lh-address LH_ADDRESS] [--dry-run] [--verbose] [--insecure] --lh-username LH_USERNAME --lh-password LH_PASSWORD (--all | --never-seen | -approved | --connected | --disconnected | --pending | --pending-connected | -pending-disconnected)
Required
Option -h
-a <LH_ADDRESS>
-d
-v -i
Alternate Syntax
Description
--help
Display usage information and exit.
--lh-address <LH_ADDRESS>
The address of the Lighthouse to unenroll nodes to (default=localhost).
--dry-run
Don't actually delete anything - just list the nodes that would be deleted.
--verbose
List the number of nodes in each state.
--insecure
Don't verify https certificates. This is only recommended for localhost.
24.12.1
Command Line Tools
361
Required Y
Option -u <LH_USERNAME>
Y
-p <LH_PASSWORD>
--all --never-seen
--approved
--connected
--disconnected
--pending
--pending-connected
--pending-disconnected
Lighthouse User Guide
Alternate Syntax
Description
--lh_username <LH_USERNAME>
The username of a Lighthouse root/admin user.
--lh_password <LH_PASSWORD>
The password of a Lighthouse root/admin user.
Unenroll all nodes.
Unenroll nodes that have never been seen.
Unenroll all approved nodes.
Unenroll all connected nodes.
Unenroll all disconnected nodes.
Unenroll all nodes that are pending.
Unenroll nodes that are pending, and connected.
Unenroll nodes that are pending, but disconnected.
24.12.1
Command Line Tools
362
Lighthouse User Guide
Note: The following options are related to the unenrollment strategy and only one option to be selected when entering the command:
(--all | --never-seen | --approved | --connected | --disconnected | --pending | -pending-connected | --pending-disconnected)
24.12.1
Command Line Tools
363
Lighthouse User Guide
NODE-COMMAND
Command node-command
Description A shell-based tool for pulling more detailed information from console servers.
Syntax node-command [options] command
Option -h -l
Alternate Syntax --help
--list-nodes
-i <ID> -n <name> -a <address>
-g <name> -A -C
--node-id=ID --node-name=name --node-addresss=address --smartgroup=name --all --connected>
Description Display usage information and exit. List all nodes matching query, or all nodes if none selected. Select node by config ID. Select node by name. Select node by VPN address.
Select nodes by the smart group they resolve to. Select all available nodes. Select all connected nodes.
24.12.1
Command Line Tools
364
Option -P -D -d -p -q -b -c -s
-e
--
Alternate Syntax --pending --disconnected --disable-fslog --par=num --quiet --batch --copy-file --source-file
--exact
Lighthouse User Guide
Description
Select all pending nodes.
Select all disconnected nodes.
Disable logging to file system.
Number of parallel processes to run at a time.
Suppress command output.
Suppress node-command output.
Copy a file to the node(s).
The file to copy to the node(s). Required if --copyfile is specified.
Run the command exactly as entered. Avoids quoting problems caused by shell interpretation.
Use this to stop argument parsing. This allows arguments that node-command understands to be passed to commands on the node. eg. node-command [options] -- command [args]
24.12.1
Command Line Tools
365
Lighthouse User Guide
NODE-INFO
Command node-info
Description A shell-based tool for pulling more detailed information from console servers.
Syntax node-info [options]
Option -h -l
Alternate Syntax --help
--list-nodes
-i <ID> -n <name> -a <address> -g <name> -A -C
--node-id=ID --node-name=name --node-address=address --smartgroup=name --all --connected>
Description Display usage information and exit. List all nodes matching query, or all nodes if none selected. Select node by config ID. Select node by name. Select node by VPN address. Select nodes by the smart group they resolve to. Select all available nodes. Select all connected nodes.
24.12.1
Command Line Tools
366
Option -P -D
Alternate Syntax --pending --disconnected
EXAMPLE
$ node-info -A BNE-R01-ACM7004-5
address: 192.168.128.2 id: nodes-1 ssh port: 22 description: Brisbane Rack 1 Enrollment status: Enrolled connection status: Connected BNE-R02-IM7216 address: 192.168.128.3 id: nodes-2 ssh port: 22 description: Brisbane Rack 2 Enrollment status: Enrolled connection status: Connected
Lighthouse User Guide Description Select all pending nodes. Select all disconnected nodes.
24.12.1
Command Line Tools
367
Lighthouse User Guide
NODE-UPGRADE
Command node-upgrade
Description
A tool for running firmware upgrades on multiple managed console servers with a single command and returns the results in tabular form to stdout.
Syntax
node-upgrade [-h] [-q | -b | -V | -D] [-l] [-I] [-n NODE_NAME] [-i NODE_ID] [-a NODE_ADDRESS] [-A] [-p {ACM500X,ACM550X,ACM700X,ACM70045,CM71XX,CM7196,IM42XX,IM72XX,OMXXXX,CM81XX}] [-g {Enrolled Nodes 2,Connected Nodes,Disconnected Nodes 2,Cell Health Sim Issues,Cell Health Connectivity Check Failed,retester,Good Health,SamTestFilter,JW Test}] (-f FIRMWARE_DIR | -F FIRMWARE_ FILE) [-v VERSION]
Option -h -q -b -V -D -l
Alternate Syntax --help --quiet --batch --verbose --debug --list-nodes
Description Display usage information and exit. Suppress log messages. DEPRECATED: use --quiet instead. Display logs generated while upgrading. Display detailed log messages, implies --verbose. Display nodes and their upgradeable paths without executing upgrade.
24.12.1
Command Line Tools
368
Lighthouse User Guide
Option
Alternate Syntax
Description
-I
--ignore-ver-
Ignore firmware version warnings for upgrade.
sion
-f <directory>
--firmware-dir <directory>
The directory of the firmware files(s). This is the directory node-upgrade looks to for the firmware image used as the source for all the firmware upgrade attempts.
-F <path>
--firmwarefile <path>
The path to the firmware image to use for upgrade.
-v <version>
--version <version>
The firmware version to upgrade to.
-n <name>
--node-namee=<name>
Select a specific node by its name, this option may be used multiple times.
-i <id>
--node-id <id>
Select a specific node by its ID, this option may be used multiple times.
-a <address>
--node-address <address>
Select a specific node by its Lighthouse VPN address, this option may be used multiple times.
-A
--all
Select all nodes. All other node selection options are ignored if
used at the same time.
-p <family>
--product <family>
Select node by product family where values available are: {ACM500X,ACM550X,ACM700X,ACM70045,CM71XX,CM7196,IM42XX,IM72XX,OMXXXX,CM81XX}
-g <name>
--smartgroup <name>
Select nodes by smartgroup. When using along side -product, 'product' and 'smartgroup' are used with an 'AND' operator.
24.12.1
Command Line Tools
369
EXIT STATUS
Exit Status
Description
0
Command exited normally
1
Invalid parameter
2
Unknown argument
Lighthouse User Guide
OUTPUT MESSAGES
Result SUCCESS FileNotFoundError UpgradeError
IncompatibleFirmwareError
Causes Node upgrade succeeded. No upgrade file found matching provided device family or version. Device already has same or higher firmware version or network connection lost. Firmware file provided does not match the product family.
EXAMPLE
# node-upgrade --all --firmware-dir /mnt/data/nvram/latest-firmware/ --version 4.11.0
NODE (UUID) MODEL FAMILY ADDRESS VERSION RESULT ----------------------------------------------------------------------------------
24.12.1
Command Line Tools
370
Lighthouse User Guide
-----cm7116-2 (nodes-4) CM7116-2 CM71XX 192.168.128.5 4.11.0 SUCCESS im7208-2 (nodes-6) IM7208-2 IM72XX 192.168.128.7 4.10.0 SUCCESS cm7196a-2 (nodes-5) CM7196A-2 CM7196 192.168.128.6 4.10.0 SUCCESS acm7004-2 (nodes-2) ACM7004-2 ACM700X 192.168.128.3 4.11.0 SUCCESS acm5508-2 (nodes-1) ACM5508-2 ACM550X 192.168.128.2 4.1.1u2 SUCCESS acm7004-5 (nodes-3) ACM7004-5 ACM7004-5 192.168.128.4 4.11.0 SUCCESS om2216-l (nodes-8) OM2216-L OMXXXX 192.168.128.9 21.Q2.1 FileNotFoundError om1208-8e (nodes-7) OM1208-8E OMXXXX 192.168.128.8 21.Q2.1 FileNotFoundError
Note: The information in the output shows the device version prior to upgrade.
24.12.1
Command Line Tools
371
Lighthouse User Guide
SUPPORT-REPORT
Command support-report
Description
Tool to generate a Lighthouse support report. This program should be run as super-user. All output is sent to stdout, and should be redirected to a file if required.
Syntax support-report [-h] [--zip] [--content-config CONTENT] [--config CONFIG_URI]
Option -h -z
-c CONTENT
Long Option
Description
--help
Display usage information and exit.
--zip
Create .zip archive, containing even more logs, config, and information.
--content-config CONTENT
Override default content (YAML) configuration file.
--config CONFIG_URI
Config file for lipy.
EXAMPLE
support-report -z > report.zip
24.12.1
Command Line Tools
372
SYSFLASH
Command sysflash
Lighthouse User Guide
Description Is a shell-based tool for upgrading a Lighthouse instance's system .Sysflash will warn you if you do not have enough available space to upgrade to, though this is unlikely as space is reserved specifically for the upgrade process.
Syntax sysflash [options] (filename|URL)
Option -V -I -m -v -o -r
Long Option
Description
--vendor <vendor>
Override vendor (currently opengear).
--no-version-check
Do not check software version for upgradability.
--no-migration
Do not migrate current config. Start fresh.
--verbose
Increase verbosity (may repeat).
--no-boot-once
Do not modify bootloader (implies --no-reboot).
--no-reboot
Do not reboot after upgrading.
24.12.1
Command Line Tools
373
Option
Long Option filename|URL
-h
--help
Lighthouse User Guide
Description
Location of the upgrade image: filename- path to system image .lg_upg. Filename cannot include spaces. URL- percent-encoded or quoted URL to firmware image .lg_upg
Display usage information and exit.
24.12.1
Command Line Tools
374
Lighthouse User Guide
TRAFFIC_MIRRORING
Command traffic_mirroring
Description
Is a tool that allows network administrators to set up an integration with their enterprise Intrusion Detection System (IDS). Network Traffic Mirroring can only be configured by a network administrator with sudo access and is available only through a command line interface.
Syntax
traffic_mirroring [-h] [--config CONFIG_URI] [--enable | --disable | --status | -test] [--instance-id INSTANCE_ID] [--destination-ip DESTINATION_IP] [--vlan-id VLAN_ ID] [--mirror-smf] [--ignore-multi-instance] [--external-interface INTERFACE]
Option -h | --help --config <CONFIG_URI> --enable --disable --status
--test
Description
Display usage information and exit.
Config file for lipy.
Enable traffic mirroring.
Disable network traffic mirroring.
Get the current status of the traffic mirroring config. Can be executed on a secondary Lighthouse.
Test the setup by sending a single ping on each VPN and attempt to confirm that the current setup is valid, and the correct rules and interfaces exist, and the destination IP is reachable. Execute on a secondary Lighthouse to check if the network traffic mirroring is in use.
24.12.1
Command Line Tools
375
Option --instance-id <INSTANCE_ ID> --destination-ip <DESTINATION_IP>
--vlan-id <VLAN_ID>
--mirror-smf
--ignore-multi-instance --external-interface <INTERFACE, e.g. net1>
Lighthouse User Guide
Description
The instance ID of the Lighthouse for which to manage traffic mirroring. If omitted, all Lighthouses will be affected.
The destination IP where mirrored traffic will be sent to (e.g: Intrusion Detection System). Because mirrored traffic preserves the original source/destination IP address, this IP should be on the same subnet as Lighthouse, or it may not be possible to get the MAC address to route the traffic to the destination.
The VLAN ID to use for traffic mirroring. This will result in a new vlantagged interface called 'mirror' being created, where ALL traffic to the destination IP will be routed through, even traffic that is not created by traffic mirroring (e.g. ping, ssh).
Mirror traffic for the Smart Management Fabric (SMF). SMF traffic is encapsulated in a Wireguard VPN tunnel within the OpenVPN tunnel that connects nodes together. Thus, to mirror the correct data for this tunnel, it must be handled twice. Reminder: The amount of traffic sent from Lighthouse is already doubled by enabling traffic mirroring. If this is enabled, then SMF traffic will be tripled (instead of doubled), and all other non-SMF traffic will still be doubled. This may result in huge amounts of traffic being sent by Lighthouse, as SMF can route traffic from many hosts, and the traffic might be bouncing multiple times (e.g. From a node, to LH, to a secondary LH, to another node). Be careful, and assess how you are planning to use SMF, and if you are capable of handling the network load.
Do not mirror traffic between multi-instance Lighthouses. Only mirror traffic between Lighthouse and nodes.
Specify the interface for traffic mirroring.
24.12.1
Command Line Tools
376
EXAMPLE :: ENABLE
Lighthouse User Guide
root@lighthouse:~# traffic_mirroring --enable --destination-ip 10.97.100.1 --vlanid 100 Configuring for Primary Lighthouse instance (Instance ID: 1). Confirming that Traffic Mirroring is set up... Traffic Mirroring successfully enabled.
EXAMPLE :: STATUS
root@lighthouse:~# traffic_mirroring --status Primary Lighthouse 1 has traffic mirroring enabled. Mirroring Node VPN (tun0) -> 10.97.100.1 (VLAN 100) Mirroring Multi Instance VPN (tun1) -> 10.97.100.1 (VLAN 100)
EXAMPLE :: TEST
root@lighthouse:~# traffic_mirroring --test Preparing to test Node VPN (tun0) interface. Pinging address '192.168.128.2' on interface 'tun0'. Preparing to test Multi Instance VPN (tun1) interface. Pinging address '172.16.1.2' on interface 'tun1'. Test complete. The pings sent across the VPN's should have been mirrored.
EXAMPLE :: DISABLE
root@lighthouse:~# traffic_mirroring --disable Traffic Mirroring disabled.
24.12.1
Command Line Tools
377
Lighthouse User Guide
GLOSSARY
Terms used in this guide to define Lighthouse elements and concepts are listed below.
Term
Definition
AUTHDOWNLOCAL (RADIUS/LDAP/TACAS)
When AUTHDOWNLOCAL authentication option is selected, if remote authentication fails because the user does not exist on the remote AAA server, the user is denied access.
AUTHLOCAL (RADIUS/LDAP/TACAS)
When AUTHLOCAL authentication option is selected, if remote authentication fails because the user does not exist on the remote AAA server, Lighthouse tries to authenticate the user using a local account.
CELLULAR HEALTH
Status of the cellular connection of a node.
CONNECTED RESOURCE GATEWAY
A catalog of resources that are within the Smart Management Fabric discovered networks with support for clientless network access to resources via either SSH, HTTP, or HTTPS proxy services.
DARK MODE
Changes the user interface to display mostly dark colors, reducing the light emitted by device screens.
DOCKER
An open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. Docker powers the NetOps platform within the Lighthouse product.
ENROLLMENT
Connecting a node to Lighthouse.
ENROLLMENT BUNDLE
Used to assign a number of tags to a set of nodes when they are enrolled. During Enrollment, the bundle is specified using its name, and a bundle-specific Enrollment token.
24.12.1
Glossary
378
Term ENROLLED NODE ENROLLMENT TOKEN INSTANCE INTRUSION DETECTION SYSTEM LIGHT MODE LIGHTHOUSE LIGHTHOUSE ENTERPRISE
LIGHTHOUSE VPN LOCALAUTH (RADIUS/LDAP/AAA) MANAGED DEVICE
Lighthouse User Guide
Definition
>A Node that has been connected to Lighthouse and is ready for use.
A password that authorizes the node with Lighthouse. Used when performing Node-based, or ZTP Enrollment.
A single running Lighthouse.
An Intrusion Detection System (IDS) is a network security technology built for detecting vulnerability exploits against a target application.
Changes the user interface to display mostly light colors. This is the default UI setting.
System for accessing, managing and monitoring Opengear console servers.
Offers an elevated centralized management solution with additional functionality. It supports growing trends such as edge computing and SD-WAN with High Availability and Remote IP Access.
The OpenVPN based connections that the Lighthouse instance has with the nodes it is managing.
When LOCALAUTH authentication option is selected, if local authentication fails, Lighthouse tries to authenticate the user using a remote AAA server.
A device that is managed via a node through a serial, USB, or network connection.
24.12.1
Glossary
379
Term MULTIPLE INSTANCE NODE OSPF
PASSWORD POLICY PENDING NODE
PRIMARY INSTANCE REMOTE LOGGING/REMOTE SYSLOG
Lighthouse User Guide
Definition
Access nodes through multiple Lighthouse instances at the same time.
A device that can be enrolled with Lighthouse, allowing it to be accessed, managed, and monitored. Currently, Opengear console servers are supported on a standard license, with support for other vendors Console Servers available as an add-on.
OSPF (Open Shortest Path First) is an interior gateway protocol used to distribute routing information within a single autonomous system. It is based on link-state technology. OSPF routers exchange link-state information with their neighbors to build a complete map of the network topology. This information is used to calculate the shortest path to each destination using Dijkstra's algorithm. OSPF supports multiple paths of equal cost and can load balance traffic across these paths.
Administrative users can define rules for Lighthouse user passwords including length, types of characters, reuse, and expiration period.
A node that has been connected to Lighthouse and has been configured with a VPN Tunnel, but which has not yet been approved for access, monitoring, or management. The approval operation can be automated by configuring Lighthouse to autoapprove nodes.
The main instance of Lighthouse used for updating configuration and node enrollment.
The ability to send logs to a remote server, for the offsite storage and review of logs.
24.12.1
Glossary
380
Lighthouse User Guide
Term REPLICATION ROLE SECONDARY/DEPENDENT INSTANCES SMART GROUP
SMART MANAGEMENT FABRIC
TAG THIRD-PARTY NODE
Definition
Automatic copying of the primary Lighthouse database to any connected dependent instances. Replication ensures that these instances mirror the same information and maintains connections to the same nodes.
A set of access rights for a particular group. Three roles are defined within Lighthouse: Lighthouse Administrator, Node Administrator, and Node User.
Redundant instances of Lighthouse that are used to access Lighthouse information and connected nodes.
Dynamic filter used to search for particular nodes, or for defining the access rights of a group of users. Smart Groups use node properties, as well as tags defined by users.
With Lighthouse 24.06 onwards, Smart Groups are now renamed to Node Filters within the Lighthouse UI. However, Smart Groups retain their naming within the CLI and API.
Smart Management Fabric (SMF) is a turnkey management network overlay that uses dynamic routing to allow IP connectivity to IT resources regardless of whether these are connected via USB, serial, SSH, HTTPS (GUI), SPs/BMCs (iLO, iDRAC, etc.), RDP, Ansible, Python, vCenter or other commonly used technologies.
User-defined attribute and value that is assigned to one or more nodes or ports. Tags are used when creating Smart Groups for filtering views or access to nodes and ports.
A third-party node is any device that is not an Opengear node; and is enrolled via the Lighthouse Web UI.
24.12.1
Glossary
381
madbuild