Shell script validate OM agent from OM to OBM
Anyone can help me out create shell script to validate OM agent migrated from OM to OBM
I'm not 100% sure what you require. Would you be able to explain in a little more detail? Do you just want to know the agent can connect to the OBM server?
Of course my collegues and i build many of such scripts, but we are not allowed to share code here.
tools needed are bbcutil -ping to check if the agent or OBM server is available and certificates are correct.
use ovconfget to check that all names/IP of the old OMU sever are gone on the agent.
also you can send a testmessage with opcmsg and check in the OBM database if it arrived
check with ovcert -list and -certinfo if certifcates are correct, check the issuer of the certificates. in case you like to remove the trusted certificates of OMu from new OBM server take care that all certificates are issued by OBM server else you risk a black out of the agent.
with ovdeploy you can do a lot from OBM server, too.
I am looking shell script, Currently we have migrate our OM to OBM need to check status of the agent. Any script we have validating this migration.
This has worked beautifully for me, before, during and after migrations of this kind, from OM to anything:
I think Michael's suggestion is great - there are a few other tools like:
https://marketplace.microfocus.com/itom/content/agent-heartbeat-polling-omi-92x (which is out of date, but would still work) or https://marketplace.microfocus.com/itom/content/operations-agent-health-analyzer-and-alerting-tool .
Don't forget about https://docs.microfocus.com/itom/Operations_Agent:12.15/HealthViewIntro.
Thanks. Yes, I did not mention the others, as they would be potentially not supported, although they may still work or WOULD still work. After all, the command opcagt still works and that's what they called OBM in 1994, Operations Center, and hence, the OpC messages we all still get, almost 30 years later.
OpC was created, just to consolidate NNM messages into a single-pane-of-glass (SPoG), the original manager-of-managers (MoM).
And, that's why OV (OpenView) is still mentioned in the Operations Agent (OA), just before the log directory for instance - /var/opt/OV, /etc/opt/OV and /opt/OV on Linux, for example.
PS: Health View - this should be removed from the OA media, unless the road map indicates it will be supported for anything other than HP Operations Manager (OM), which went EOL, but that can be confirmed by Micro Focus.
OpC was originally called CSM. CSM was created to help sell HP's 9000/3000 systems (and newly incorporated Apollo workstations) which were running HP-UX and MPE and we renamed to Operations Center just before it was released. Over the years it's changed it's name several times and merged with BSM into the incredible solution we know and love today (at least I do!)
Healthview is part of OA12. It is still released with 12.15 so it's still alive. But, I agree that the road map isn't that clear. I would also agree that it's not very OBM friendly in terms architecture (e.g. where to install it for HA nonfunctional) but it works and brings value which may be useful during a migration.
Tom, does this answer your question?