Lighthouse 2020.Q4.2 is Generally Available.
Fixes and Features:
- Added storage of Azure configuration parameters to allow persistence after factory reset
- Fixed issue where Node Backup may be disabled after upgrading to 20.Q4.0, if it was configured on 20.Q3.0
- Fixed issue where replication on secondaries may be interrupted after promoting a secondary to primary
- Fixed issue where debugging log messages were being logged after enabling remote syslog
- Fixed issues with MI and node enrollment in various firewall configurations (combinations of NAT, external endpoints, alternate ports, etc.)
- Improved log handling of node config retrieval to not log spurious data
- Improved memory footprint by disabling some services if not enabled (eg. Zapier event notification)
- Improved memory usage by cleaning up database entries for old configuration updates
- Improved upgrade process in hosting configurations with non-standard device names (eg. /dev/vda, /dev/xvda)
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.