-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Notebooks Archive
- Problems with HP OMW 11.02 agent on AIX 5.3 server

Create an account on the HP Community to personalize your profile and ask a question

01-26-2012 12:58 PM
Hello all.
We are using HP Operations Manager for Windows 8.16 to monitor our AIX 5.3 servers.
I'm having issues getting the 11.02 agent to work on an AIX 5.3 node.
I get a "(ctrl-7) Error in the target component." message when I try starting the agent on the AIX server.
Many of the subagents aren't running.
Here's the subagent status.
# ovc -status
agtrep OV Discovery Agent AGENT,AgtRep Stopped
coda OV Performance Core COREXT (307218) Running
opcacta OVO Action Agent AGENT,EA Stopped
opccfgfile OVO configfile Agent AGENT,EA Stopped
opceca OVO Event Correlation AGENT,EA Stopped
opcecaas ECS Annotate Server AGENT,EA Stopped
opcle OVO Logfile Encapsulator AGENT,EA Stopped
opcmona OVO Monitor Agent AGENT,EA Stopped
opcmsga OVO Message Agent AGENT,EA Stopped
opcmsgi OVO Message Interceptor AGENT,EA Stopped
opctrapi OVO SNMP Trap Interceptor AGENT,EA Stopped
ovbbccb OV Communication Broker CORE (274528) Running
ovcd OV Control CORE (213004) Running
ovconfd OV Config and Deploy COREXT Aborted
rtmd HP Real Time Measurement AGENT (311528) Running
Here are entries being written to the /var/opt/OV/log/System.txt file on this AIX server.
0: ERR: Thu Jan 26 13:28:01 2012: ovcd (213004/4628): (ctrl-42) Initialization of component 'ovconfd' failed. Stopping component.
0: INF: Thu Jan 26 13:28:01 2012: ovconfd (311524/1): (conf-393) Configuration and Deploy process 'ovconfd' stopped.
0: INF: Thu Jan 26 13:28:02 2012: rtmd (311528/1): Initializing...
0: ERR: Thu Jan 26 13:28:04 2012: ovc (397522/1): (ctrl-7) Error in the target component.
0: INF: Thu Jan 26 13:28:30 2012: rtmd (311528/1): Waiting for requests...
0: INF: Thu Jan 26 13:33:05 2012: ovconfd (356590/1): (conf-390) Configuration and Deploy process 'ovconfd' started.
0: ERR: Thu Jan 26 13:33:10 2012: ovconfd (475374/1): (conf-376) Configuration and Deploy process 'ovconfd' cannot be started because Communication Broker service (CB) is not avail
able (status '4').
0: ERR: Thu Jan 26 13:33:10 2012: ovcd (213004/271): (ctrl-42) Initialization of component 'ovconfd' failed. Stopping component.
0: INF: Thu Jan 26 13:33:10 2012: ovconfd (356590/1): (conf-393) Configuration and Deploy process 'ovconfd' stopped.
0: INF: Thu Jan 26 13:33:10 2012: ovconfd (356592/1): (conf-390) Configuration and Deploy process 'ovconfd' started.
0: ERR: Thu Jan 26 13:33:15 2012: ovconfd (475376/1): (conf-376) Configuration and Deploy process 'ovconfd' cannot be started because Communication Broker service (CB) is not available (status '4').
0: ERR: Thu Jan 26 13:33:15 2012: ovcd (213004/271): (ctrl-42) Initialization of component 'ovconfd' failed. Stopping component.
0: INF: Thu Jan 26 13:33:15 2012: ovconfd (356592/1): (conf-393) Configuration and Deploy process 'ovconfd' stopped.
0: ERR: Thu Jan 26 13:33:16 2012: ovc (483574/1): (ctrl-7) Error in the target component.
Deployment of the policies to this AIX server failed on the OMW management server with the following error: "(PMD1231) Unable to deploy <policy name> to node <fully qualified node name>. The agent API returned the following error: (bbc-431) HttpOutputRequestImpl::ProcessRedirection()HttpStatus::NotFound:caught ServiceUnknownException. There is no server process registered for address: https://<fully qualified node name/com.hp.ov.conf.core/bbcrpcserver.
Does anyone have suggestions to fix this issue?
I've already tried a clean install of the agent but got the same results.
Anyhelp would be greatly appreciated.
Thanks in advance.
Tom Wolf
03-13-2012 11:04 AM
Hello Paulo.
Per HP, we had to manually add the AIX node's IP address to the agent's configuration with the following ovconfchg commands to fix issues with the communication broker. We then bounced the agent and everything was running and functional.
Hope this helps.
# ovconfchg -ns eaagt -set OPC_IP_ADDRESS <AIX node IP address>
# ovconfchg -ns bbc.cb -set SERVER_BIND_ADDR <AIX node IP address>
# ovconfchg -ns bbc.http -set SERVER_BIND_ADDR <AIX node IP address>
# ovconfchg -ns bbc.http -set CLIENT_BIND_ADDR <AIX node IP address>
# ovc -kill
Make sure no agent processes are running.
# ps -ef | grep -e /usr/lpp/OV | grep -v grep
Restart the agent.
#ovc -start
