2.54 to 3.0
While patching our servers, the nmsprime upgraded from 2.54 to 3.0. The website stopped working, however the backend services for provisioning are still function for provisioning. We were unaware you were moving to a new business model.
We read in your notes ... be aware that you can not upgrade to v3 without a valid SLA. If you are moving to a freemium business model, are you providing a migration path to a provisioning only VM from 2.54 or a fresh install of 3.x with database migration? Emails to your sales dept have not been returned about pricing and other 3.0 modules.
3 Comments
Ole Ernst
Hi Ken, unfortunately v3.0.0 was also pushed to the "legacy" rpm repo by our deployment team. The plan was to keep that repo at v2.5.4. I adjusted this just now. I would suggest disabling all the enterprise modules for now. This way the WebGUI should work again.
Disable all listed modules except for:
HfcReq
HfcSnmp
NmsMail
ProvBase
ProvVoip
Sorry for the inconvenience, the sales dept will get in contact with you.
BR,
Ole
Ken Miller
Hi,
I tried these steps but received the following errors:
[root@nmsprime nmsprime]# php artisan module:list
php artisan module:list
PHP Fatal error: Cannot make static method App\BaseModel::rules() non static in class Modules\ProvVoip\Entities\Mta in /var/www/nmsprime/modules/ProvVoip/Entities/Mta.php on line 341
In Mta.php line 341:
Cannot make static method App\BaseModel::rules() non static in class Modules\ProvVoip\Entities\Mta
[root@nmsprime nmsprime]# php artisan module:disable ProvMon
PHP Fatal error: Cannot make static method App\BaseModel::rules() non static in class Modules\ProvVoip\Entities\Mta in /var/www/nmsprime/modules/ProvVoip/Entities/Mta.php on line 341
In Mta.php line 341:
Cannot make static method App\BaseModel::rules() non static in class Modules\ProvVoip\Entities\Mta
Is there a way to roll back to the 2.5.4?
Sales has emailed me and we are going over options.
Thanks,
Ken
Ole Ernst
Hi Ken,
we are updating all customers with a subscription to 3.0.0 right now. Afterwards 2.5.4 will not be supported anymore. Unfortunately, we have not intended a rollback path and this is untested. Since you have a mix and match of new and old module versions right now, I would suggest setting up a new clean NMS Prime 3.0.0 community version and transfer your data over. As far as I understood you don't have much customers in NMS Prime at this point, so this might be a reasonable solution.
BR,
Ole