In the 20.Q1 release, Lighthouse and NetOps Modules introduced several major architectural improvements.
This necessitated breaking changes and means there a few extra steps to get NetOps back up and running when upgrading from an earlier version.
1. All nodes that are enabled for IP Access in Lighthouse 19.Q3 must have IP Access disabled before the new module can start.
Note that the new IP Access network architecture is not backwards compatible, so any client configurations created in previous versions will no longer connect and must be recreated.
The simplest way is to do this is to disable IP Access on all nodes before upgrading to 20.Q1. (If you've already performed the upgrade to 20.Q1, skip to step 2.)
- Login to the Lighthouse 19.Q3 web UI as a Lighthouse Administrator or the root user
- From the menu, select CONFIGURE NODES > IP Access > Enable Nodes > Disable All
- Upgrade to Lighthouse 20.Q1 then proceed to step 2
2. After upgrading Lighthouse from 19.Q3 to 20.Q1, the IP Access and Device Provisioning page displays a message indicating that a module upgrade is required.
To upgrade NetOps Modules follow the steps detailed in this article, i.e.:
- Login to the Lighthouse 20.Q1 web UI as a Lighthouse Administrator or the root user
- From the menu, select SETTINGS > Services > NetOps Modules
- Click the Synchronize icon
- From the menu, select CONFIGURE NODES > NetOps Modules > Manage Modules
- Click the Redeploy icon
3. If you successfully disabled IP Access on all nodes before the upgrade as per step 1, migration is now complete.
If you upgraded before disabling IP Access on all nodes, follow these steps:
- Login to the Lighthouse 20.Q1 shell as the root user or a Lighthouse Administrator and become root with: sudo -i
- Run the following commands:
id=$(docker create opengear/central-sdi:1.1.2)
docker cp $id:/etc/scripts/$script /tmp/
docker rm -v $id
node-copy --all -s /tmp/$script /tmp/$script
node-command --all bash /tmp/$script '&&' rm /tmp/$script