Task 03: OpenGear Lighthouse Portal Verification
DOCUMENT CATEGORY: Runbook
SCOPE: Console server verification
PURPOSE: Verify OpenGear is enrolled and accessible via Lighthouse
MASTER REFERENCE: OpenGear Lighthouse Documentation
Status: Active Estimated Time: 15 minutes
Overview
Verify that the OpenGear console server has been enrolled with the Lighthouse portal and provides remote access to infrastructure devices.
This verification requires access to the Lighthouse portal. Ensure you have the appropriate credentials before proceeding.
Prerequisites
| Requirement | Description |
|---|---|
| Lighthouse access | Azure Local Cloud Lighthouse portal credentials |
| OpenGear installed | Console server racked and powered |
| NET1 connectivity | Internet-routable network connected |
Values from infrastructure.yml
The script reads these keys from infrastructure.yml (schema 5). Each key, with its type, default and example, is in the variables reference.
network_devices[]: hostname, type, role, vendor, management.ip_address, management.protocol, credentials.username, credentials.password
Lighthouse Portal Verification
- Lighthouse Portal
- Orchestrated Script
Step 3.1: Login to Lighthouse Portal
- Navigate to {{lighthouse_url}}
- Login with Azure Local Cloud credentials
- Navigate to Nodes → All Nodes
Step 3.2: Locate Site Console Server
- Search for node:
OM-<SITE_CODE> - Verify node appears in the list
- Check status indicator
| Status | Indicator | Meaning |
|---|---|---|
| Online | 🟢 Green | Connected and operational |
| Offline | 🔴 Red | Not connected - investigate |
| Pending | 🟡 Yellow | Enrollment in progress |
Step 3.3: Verify Node Details
Click on the node to view details:
| Field | Expected Value | Status |
|---|---|---|
| Node Name | OM-<SITE_CODE> | ☐ |
| Status | Online | ☐ |
| Firmware | Current version | ☐ |
| IP Address | Visible | ☐ |
| Last Check-in | Recent (< 5 min) | ☐ |
PowerShell
When to use: Run the task from a management workstation or a pipeline. The script reads
infrastructure.ymland carries no values of its own.
Script
| Script | What it does |
|---|---|
scripts/deploy/03-onprem-readiness/phase-02-enterprise-readiness/task-03-opengear-verification/powershell/Test-OpengearVerification.ps1 | Checks that every console server of network_devices in infrastructure.yml can be reached and that its login can be read. Changes nothing. |
Requires: PowerShell 7.
Run
./Test-OpengearVerification.ps1 -InfrastructureFile ./infrastructure.yml
Console Port Verification
Step 3.4: Verify Serial Port Labels
- In Lighthouse, click on the node
- Navigate to Serial Ports
- Verify port labels match design:
| Port | Expected Label | Configured | Status |
|---|---|---|---|
| Console ports | Per infrastructure.yml network_devices[] | ☐ | ☐ |
| Network ports | Per infrastructure.yml network_devices[] | ☐ | ☐ |
| Switch ports | Per infrastructure.yml network_devices[] | ☐ | ☐ |
Step 3.5: Test Console Access
- Click on a serial port (e.g.,
Switch-TOR1) - Click Connect or Web Terminal
- Verify console session opens
- Test keyboard input (press Enter)
- Close session
Expected Result: Console session opens and accepts input.
OOB Network Verification
Step 3.6: Verify Bridge Configuration
- In Lighthouse, navigate to node Network settings
- Verify br0 bridge configuration:
| Setting | Expected Value | Status |
|---|---|---|
| Bridge Members | net2, sw0p1-sw0p8 | ☐ |
| IP Address | Per infrastructure.yml networking.oob.subnet | ☐ |
| Default Route | Disabled | ☐ |
Step 3.7: Test iDRAC Connectivity (via Lighthouse)
- In Lighthouse, use Network Tools or SSH to OpenGear
- Ping iDRAC addresses from OpenGear:
# SSH to OpenGear via Lighthouse, then ping each node iDRAC IP
# from infrastructure.yml: nodes[].bmc.ip_address
ping -c 2 <IDRAC_IP_NODE1>
ping -c 2 <IDRAC_IP_NODE2>
# Repeat for all nodes defined in infrastructure.yml
Expected Result: All iDRAC IPs respond to ping from OpenGear.
Firewall Zone Verification
Step 3.8: Verify Firewall Configuration
Via Lighthouse or SSH to OpenGear:
# Check firewall zones
ogcli get system.firewall.zones
# Expected output:
# WAN zone: net1 (reject default)
# LAN zone: br0 (accept default)
Troubleshooting
| Issue | Likely Cause | Resolution |
|---|---|---|
| Node offline | NET1 no internet | Verify NET1 connectivity |
| Enrollment pending | Firewall blocking | Open ports 443, 1194, 51820 outbound |
| Console won't connect | Serial cable issue | Check physical connection |
| iDRAC not pingable | OOB VLAN issue | Verify br0 bridge members |
Validation Checklist
| Check | Expected | Status |
|---|---|---|
| Node visible in Lighthouse | Yes | ☐ |
| Node status | Online (Green) | ☐ |
| Serial ports labeled | All ports configured | ☐ |
| Console access works | Session opens | ☐ |
| iDRAC pingable from OpenGear | All respond | ☐ |
| Firewall zones configured | WAN/LAN correct | ☐ |
Acceptance Criteria
- OpenGear node appears in Lighthouse portal with "Online" status
- All serial port labels match physical connections
- Console access test successful (session opens, accepts input)
- iDRAC devices pingable from OpenGear via OOB network
- Artifacts saved to deployment folder:
artifacts/phase-02-enterprise-readiness/
Next Steps
| Step Complete? | Next Action |
|---|---|
| ✅ Yes | Proceed to Task 4: Validation Sign-Off |
| ❌ No | Troubleshoot OpenGear connectivity issues |
Scripts for this task are located in the azurelocal-toolkit repository under scripts/deploy/ in the appropriate task folder.
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Navigation
| ← Task 02: Network Service Verification | ↑ Part 3: On-Premises Readiness | Task 04: Validation Sign-Off → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2025-06-04 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-03 | Azure Local Cloud | Standardized runbook format |
End of Task