Skip to main content
Version: Next

Task 03: OpenGear Lighthouse Portal Verification

Runbook Platform

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.

Run Location

This verification requires access to the Lighthouse portal. Ensure you have the appropriate credentials before proceeding.


Prerequisites

RequirementDescription
Lighthouse accessAzure Local Cloud Lighthouse portal credentials
OpenGear installedConsole server racked and powered
NET1 connectivityInternet-routable network connected

Variables from variables.yml

Variable PathTypeDescription
networking.network_devices.opengearObjectOpenGear hostname, IP, model, Lighthouse enrollment token
networking.network_devices.opengear.ports[]ArraySerial port-to-node mappings (port number, connected device, baud rate)
compute.nodes[]ArrayNode hostnames for console port label verification
networking.onprem.vlans.oobObjectOOB VLAN ID, CIDR, gateway for network connectivity tests
virtual_machines.lighthouseObjectLighthouse portal VM details

Lighthouse Portal Verification

Step 3.1: Login to Lighthouse Portal

  1. Navigate to {{lighthouse_url}}
  2. Login with Azure Local Cloud credentials
  3. Navigate to NodesAll Nodes

Step 3.2: Locate Site Console Server

  1. Search for node: OM-<SITE_CODE>
  2. Verify node appears in the list
  3. Check status indicator
StatusIndicatorMeaning
Online🟢 GreenConnected and operational
Offline🔴 RedNot connected - investigate
Pending🟡 YellowEnrollment in progress

Step 3.3: Verify Node Details

Click on the node to view details:

FieldExpected ValueStatus
Node NameOM-<SITE_CODE>
StatusOnline
FirmwareCurrent version
IP AddressVisible
Last Check-inRecent (< 5 min)

Console Port Verification

Step 3.4: Verify Serial Port Labels

  1. In Lighthouse, click on the node
  2. Navigate to Serial Ports
  3. Verify port labels match design:
PortExpected LabelConfiguredStatus
Console portsPer variables.yml network_devices.opengear.ports.console
Network portsPer variables.yml network_devices.opengear.ports.network
Switch portsPer variables.yml network_devices.opengear.ports.switch

Step 3.5: Test Console Access

  1. Click on a serial port (e.g., Switch-TOR1)
  2. Click Connect or Web Terminal
  3. Verify console session opens
  4. Test keyboard input (press Enter)
  5. Close session

Expected Result: Console session opens and accepts input.


OOB Network Verification

Step 3.6: Verify Bridge Configuration

  1. In Lighthouse, navigate to node Network settings
  2. Verify br0 bridge configuration:
SettingExpected ValueStatus
Bridge Membersnet2, sw0p1-sw0p8
IP AddressPer variables.yml vlans.oob
Default RouteDisabled

Step 3.7: Test iDRAC Connectivity (via Lighthouse)

  1. In Lighthouse, use Network Tools or SSH to OpenGear
  2. Ping iDRAC addresses from OpenGear:
# SSH to OpenGear via Lighthouse, then ping each node iDRAC IP
# from variables.yml: nodes.<node_name>.idrac_ip
ping -c 2 <IDRAC_IP_NODE1>
ping -c 2 <IDRAC_IP_NODE2>
# Repeat for all nodes defined in variables.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

IssueLikely CauseResolution
Node offlineNET1 no internetVerify NET1 connectivity
Enrollment pendingFirewall blockingOpen ports 443, 1194, 51820 outbound
Console won't connectSerial cable issueCheck physical connection
iDRAC not pingableOOB VLAN issueVerify br0 bridge members

Validation Checklist

CheckExpectedStatus
Node visible in LighthouseYes
Node statusOnline (Green)
Serial ports labeledAll ports configured
Console access worksSession opens
iDRAC pingable from OpenGearAll respond
Firewall zones configuredWAN/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
✅ YesProceed to Task 4: Validation Sign-Off
❌ NoTroubleshoot OpenGear connectivity issues

Task 02: Network Service Verification↑ Part 3: On-Premises ReadinessTask 04: Validation Sign-Off →

Version Control

VersionDateAuthorChanges
1.02025-06-04Azure Local Cloud Azure Local CloudnologyInitial document
1.12026-03-03Azure Local Cloud Azure Local CloudnologyStandardized runbook format

End of Task