HPOM Migration to OMi - Preparation

Just starting to take a look at OMi to plan migration from HPOM v9 - looks like a completely different and re-worked front-end.

First thing I need to do is work out all the main priorities before I can plan this in more detail - for example working out where the equivalent config items from HPOM v9 are in OMi - then I can check where functionality has been superseded in the new tool, or where any rework is required.

I have a rough plan jotted down already, so will share this with you in due course.

If you've migrated to OMi I'd appreciate your views on approach/problems etc., or if you are considering the migration yourself please sign-up and then I can keep you updated as to progress, and hopefully help you out also!

Have a great day,
Dave

Java GUI Issues in HPOM

I've seen issues in the past where Java GUI alerts in HP Operations Manager (HPOM) v9.x don't get owned or acknowledged when you trigger those actions.

If you reload the Java GUI console then the action you previously performed works, i.e. the alert is owned or acknowledged, but it's not being done automatically.

HP support came up with this fix - which seemed to work:

# /opt/OV/bin/ovc -stop SERVER
# rm -rf /var/opt/OV/share/tmp/OpC/mgmt_sv/WAP*
# rm -rf /var/opt/OV/share/tmp/OpC/mgmt_sv/WWW*
# rm -rf /var/opt/OV/share/tmp/OpC/ui/*
# /opt/OV/bin/ovc -start

I have also seen the Java GUI hang on the "Loading Messages" screen, and we think this was due to different versions of the Java GUI being used, so I strongly recommend if you see this issue keep an eye on the versions being used (use the listguis command) and try to align all users to the latest version.

Dave