Lighthouse 2021.Q3.0 is Generally Available.
Fixes and Features:
21.Q3.0
- Node-upgrade CLI utility improvements and support for Operation Manager series devices
- Improved display of information and upgrade results
- CLI arguments and options preserved for backwards compatibility
- Additional arguments/options:
- firmware-file for selecting a specific firmware image instead of specifying a directory to search through
- product for selecting nodes by product family
- verbose for displaying log information (but not as much as with --debug)
- Added password verification when performing user changes for local Lighthouse users
- This is applicable for Lighthouses configured to only use local auth
- Usernames including "." characters can now be used in Lighthouse
- Content Security Policy header has been implemented
- Updated the WebUI display for third party/digi passport nodes to show the node address
- Added support for a configurable remote AAA timeout value via the ogconfig-cli tool
- Once your AAA auth has been set, use "ogconfig-cli auth.timeout #" to set the timeout in the CLI
- Fixed an issue in which the default static IPv4 address was left in External Network Address list when the associated network interface is disabled
- Improvements to Cell Health handling and display of the Failover status for nodes
- Added script to support for bulk-unenrolling of nodes - please contact support if you wish to utilize this script
- Added additional system status information to the Lighthouse support report
- Fixed issues with the smart group node-id search that had previously resulted in incorrect results when using the abbreviated id form (i.e. 1 instead of nodes-1) or viewing the results on the Console Gateway page
- Fixed an issue in which the "read_write" SNMP community field could not be cleared once set
- Fixed an issue with generic third party nodes which resulted in the port labels being assigned to the incorrect ports
- Enabled support for the Carrier Grade NAT IP range (RFC 6598, 100.64.0.0/10) for LHVPN tunnels to Nodes
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.