Lighthouse 2021.Q2.1 is Generally Available.
Fixes and Features:
21.Q2.1
- Fixed issue where Lighthouse couldn't receive firewall zone data from OM series devices on 21.Q1
- Fixed issue where Lighthouse could use incompatible upgrade files
- Fixed issue where multiple instance enrollment via alternate port still sends traffic to port 443
21.Q2.0
- Upgraded Yocto version to Dunfell
- Deprecated Python 2 in favor of Python 3 on Lighthouse
- Improved monitoring and error notifications for Multiple Instance Lighthouses
- Improved upgrade process and flow for Multiple Instance Lighthouses
- Improved enrollment and unenrollment process of nodes on Lighthouse
- Improved performance of cellular health reporting on Lighthouse
- IMEI, IMSI and ICCID reported for cellular health on UI and through REST API
- Added node ID and port ID to Lighthouse system logs
- Added sorting support through REST API for smartgroups endpoint
- Added sorting support through REST API for jobs endpoint
- Added sorting support through REST API for nodes endpoint
- Fixed Lighthouse CVE issues
- Fixed issue with free text search not working for IP Addresses on node pages
- Fixed SSL problems with self-signed certs in web UI on Big Sur when using Google Chrome
- Fixed issue where in 20.Q4.0 third party (Avocent) nodes can't connect with pmshell
- Fixed issue with multiple instance Lighthouse enrollments when the replication_user already exists
- Fixed cross site scripting vulnerability for script templates
- Improved REST API backward compatibility
- Fixed issue where rest_api_log process was logging with incorrect hostname
- Fixed issue with Lighthouse memory usage info in SNMP (slab memory)
- Fixed issue with enrollment bundle template ordering not being saved
- Fixed issue with LDAP configuration changes not getting saved
- Fixed issue with ACM7008 configuration not getting updated on Lighthouse
- Fixed issue where LDAP does not fall back to local authentication on failure
- Fixed issue where node-related redis keys are not deleted when node is unenrolled
- Added MI diagnostics to support report
- Added versions support for Hyper-V powershell install script
- Fixed issue where Lighthouse console_gateway API doesn't always return address used for SSH links
- Fixed issue with RADIUS sending incorrect Service-Type
- Fixed issue where changing the node VPN on the Primary instance in a MI cluster does not check for vpn conflicts
- Fixed issue where Lighthouse generates invalid engine ID for SNMPv3
- Fixed issue with cell health when communicating with an OM device that has no modem
- Fixed issue where a user cannot deploy Azure Lighthouse without Public IP Address
- Fixed issue where hitting a node proxy URL when not logged in gives a 401 screen
- Fixed issue where Enrollment Token cannot contain special characters
- Fixed issue where port label with '%' breaks web terminal page
- Resolved Enrollment bundle UI issue for adding NetOps modules
- Fixed issue where lh-client-connect script is too slow
- Fixed issue where Lighthouse on AWS becomes unresponsive after upgrading and then factory resetting
Known Issues
Opengear are aware of the following product specific issues with this release:
- After promotion, the primary and secondary Lighthouses might not report the correct status. This can be fixed by running /etc/scripts/primary_Lighthouse_resync_replication.sh on the secondary Lighthouses
- External endpoint addresses (IPv6) are not automatically populated for Azure Lighthouses. Currently the user has to manually update this address on Lighthouse
- For Lighthouse deployments that don't use /dev/sda1 as the root volume, upgrading to versions from 20.Q4.2 must be done via the command line.
- For example, if the device is /dev/vda1, the following command will need to be run to specify the root volume:
- SYSFLASH_IB_DEV=/dev/vda1 sysflash -v ./og-image-lighthouse-lighthouse.lh_upg
- Note: This only works for standalone Lighthouse instances, or the primary Lighthouse in a Multiple Instance configuration. In a Multiple Instance configuration, the old secondary instances will need to be un-enrolled then re-enrolled into the primary Lighthouse.
- For example, if the device is /dev/vda1, the following command will need to be run to specify the root volume:
Please Note - It is highly recommended to upgrade NetOps modules to latest version. If the version of NetOps modules on Lighthouse does not match the required criteria, a banner is displayed on UI prompting the user to update the modules
----------------
Full release notes are available at:
Images and checksums are available under:
REST API documentation is available under:
User manual is available under:
Comments
0 comments
Article is closed for comments.