I am planning on upgrading from NMS 5.61 to 6.1 and UMP 2.62 to 6.0. Has anyone here already upgraded? I'm currently reading through the upgrade documentation but can anyone who has already upgraded provided any helpful tips?
Backup your DB and Nimsoft Folders just in case other than that it should be quite straight forward. If you run into any problems reach out to us here or log a case in the support portal.
Make sure you meet the hardware and OS specs too as the installer has a new ruby(?) script that checks for OS version and Memory (>=4GB)
when 6.0 was released I upgraded my lab to 6.0 and when 6.1 was released along with new UMP, I upgraded to those as well. I didn't come across any problems myself, but I did bump in to the script Carl mentioned, as it notified me about my UMP server's resources.
Didn't get automatic robot deploying up and running yet with new Unified Manager, though that has more to do with my Discovery setup. Also initially had some problems with ADE deploying robots to Win 2008R2 machines.
I'm planning to upgrade production environment from 5.12 -> 6.1 and UMP 2.5.2 -> 6.0 soon as well, hoping that will go smoothly as well!
I just upgraded recently. If you have any customizations to portal-ext.properties or if you've made changes to the default pages, then make sure you back those up.
UMP 6.0 changes the default user page layout, putting much more emphasis on the new Unified Service Manager (as it rightfully should). You may want to look into how you want to have your users' pages set up before upgrading.
What I have noticed is that now I want to update the origin of data captured in SLM database, a few seconds later it returns to the origin as before,
Has anyone happened that?, Could fix it?,
I glanced at the table S_QOS_DATA and the source for the VM's is the same that the robot who has vmware probe installed,
Before upgrading NMS I could change the source field to all virtual machines on S_QOS_DATA table, but it seems that the origin qos_processor back to the origin of the robot,
Do NOT change the source column in the S_QOS_DATA table. Origins are okay to change in the table but not source.
I am not sure if I misunderstood what you were thinking of doing, but I wanted to make sure to warn you about touching the source just to be sure.
Retrieving data ...