2016-08-04 01:05 PM
Two instances of UCUM 7.0RC1 are exhibiting the same behavior. When an alert is sent to an email, the event details link to https://localhost:443/um/.......(see attachment for screenshot). I assume "localhost" should have the name of the UCUM or OPM server. Prior to upgrading from 6.x, when an alert was sent to email, I was able to click on the event details link, which would then connect me to OCUM or OPM, and view the alert. Any ideas?
Solved! SEE THE SOLUTION
2016-08-05 01:04 AM
I also observed that OCUM registeres in WFA with the localhost address. I had to change the data source in WFA manually afterwards to reflect the right name/IP.
So this seems to be a general problem in 7.0RC1.
2016-08-05 10:48 AM
Is your setup running in Windows or Linux or vApp?
If it is running on Windows or Linux, can you paste the output of following commands:
* ping <hostname>
* pint -a <ip_address>
I do have a workaround for this issue, and the above output would help me to validate that.
2016-10-04 07:16 AM
we do have the same issue - even running OCUM 7.0 GA.
Risk - Aggregate Nearly Overcommitted
Impact Area - Protection
Severity - Warning
State - Obsolete
Source - XX
Trigger Condition - XX
Solution would be very much appreciated!
2016-10-27 05:28 AM
Sorry for the delay. Can you please reset the hostname using "um option" command.
Steps to fix this problem:
* Go to the console (root console)
* Login to "um cli"
* Set the custom.hostname option to the new value for whcih DNS works
* restart the ocie service
The commands for the above steps are shared below.
um cli login -u <user_name> -p <pwd>
um option set custom.hostname=oncommand-71rc1-168.gdl.englab.net
service ocie restart
Let me know if that doesnt work.
2016-10-27 07:29 AM - edited 2016-10-27 07:31 AM
Thanks - worked for me.
I changed the following options to reflect the actual FQDN rather than "localhost":
Unfortunately the manual restart of the ocie service did not succeed. I had to restart the vApp but all is fine now.