Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Upgrading from 2.8.8 to 3.3 - What will break, and what measures should be taken?
-
Are the Mango 3.0 Upgrade Notes written April 26, 2017 accurate for upgrading from Mango 2.8.8 to Mango 3.3? Are there any upgrade issues that will break features in 2.8.8? I'm especially concerned about not breaking the old Graphical Views, meta scripts, and global scripts, Modbus, and BACnet. If I backup the SQL database, /opt/mango, and TSDB, is it then safe to upgrade via the Mango Module page? What will break?
Thanks.
-
Hi Pedro,
The only part of those notes that is no long accurate is that the dashboards module is completely discontinued as of 3.3.0, so you must migrate any dashboards there into the UI module.
If you backup those databases, you could recreate your 2.8.8 Mango so yes attempting the upgrade is 'safe' after that. You will probably need to remove the dashboards module from your instance before the /modules.shtm page will allow you to upgrade to the latest.
Nothing in your Graphical Views, Meta scripts, Modbus or Global Scripts should break. You may have to play with your local device settings for BACnet, as there are differences in BACnet4J between 2.8 and 3.x
-
@phildunlap said:
remove the dashboards module from your instance
I have not implemented dashboards in 2.8.8 since I've been using DGLux. Are you stating that I should delete the dashboard from the modules directory before initiating the upgrade?
I am using an old BACnet datasource where all the different eGauge IP addresses are contained in a single datasource. At some later point in 2.x the BACnet module was changed so that each different IP address is listed as a separate datasource. Although I'd rather have separate data sources for each BACnet device, I'm still using the single datasource configuration because I did not want to risk breaking my BACnet sources. Will the upgrade break my BACnet worse than a simple 2.8.8 BACnet? What is your recommendation?
-
@pedro said in Upgrading from 2.8.8 to 3.3 - What will break, and what measures should be taken?:
I have not implemented dashboards in 2.8.8 since I've been using DGLux. Are you stating that I should delete the dashboard from the modules directory before initiating the upgrade?
Mark it for deletion from the modules page and restart. You will not be able to do the upgrade with the dashboards module installed.
-
DGLux is not compatible with Mango 3.3 so you will also need to remove the DGLux module as well.
BACnet is greatly improved in 3.3 but it does rely more on proper BACnet networking. As long as all your devices are discoverable with a WhoIs then there should be no difference and you should see a nice improvement especially if you want to run multiple BACnet Data Sources.
-
@joelhaggar Does the 3.3. BACnet still support polling multiple devices under the same data source? If not, then I expect that it will break when it tries to read my BACnet configuration. If all my BACnet devices will go offline during the upgrade, I need to be prepared and know how long it will take to move them into separate datasources without losing historical data.
-
It still supports all devices under one Data Source so there won't be any issue with leaving it the way it is. If you want to move them into separate data sources that should be fine to do in 3.3.
-
Thanks. I would like to move the devices to separate data sources, provided the point value history can be moved with it. I'm glad to hear that I can cross that bridge some time after the upgrade.
