Recently I fixed Partner Agent issue for one of my production Target Agent, which had a partner agent assigned  but was on development server. This ideally should not be the case as partner agent plays a very important role in monitoring. When primary agent is unavailable, it is very important to pick correct Partner agent to make sure monitoring is not affected.

Partner Agent is an agent which in addition to performing its regular functions, also remotely monitors the status of its assigned Management Agent and its host. OMS automatically assigns Partner Agent using built-in algorithm.

Partner Agent can be changed anytime, by using emcli verbmanage_agent_partnership“.

Few common alerts from Partner Agent.

 “Partner Agent could not connect to Host. Host might be down“.

Host=HANTESTAP5.dksharma.com 
Target type=Host
Target name=
HANTESTAP5.dksharma.com 
Categories=Availability
Message=
Partner Agent could not connect to Host. Host might be down. Refer to MOS Note (Doc ID 2101383.1) for additional information if you see the alert for more than few minutes. 
Severity=Fatal
Event reported time=Sep 4, 2017 1:02:25 AM CDT
Target Lifecycle Status=Production
Line of Business=BI
Department=DBA
Operating System=Linux
Platform=x86_64
Associated Incident Id=
99071
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Target Availability
Event name=Status
Availability status=Down
Root Cause Analysis Status=Neither Cause Nor Symptom
Causal analysis result=Neither a cause nor a symptom
Rule Name=RuleSet for all Production Targets,Incident creation Rule for target down.
Rule Owner=DKSHARMA
Update Details:
Partner Agent could not connect to Host. Host might be down. Refer to MOS Note (Doc ID 2101383.1) for additional information if you see the alert for more than few minutes.

Warning: – Host Up (Monitored) – Detected by Partner Agent

Host=hanpap1.dksharma.com 
Target type=Host
Target name=
hanpap1.dksharma.com 
Incident creation time=Apr 9, 2017 12:52:22 AM CDT
Last updated time=Apr 9, 2017 3:05:00 AM CDT
Message=Host Up (Unmonitored) – Detected by Partner Agent 
Severity=Warning
Incident ID=90359
Event count=1
Incident Status=New
Escalated=No
Priority=None
Incident owner=DKSHARMA
Incident Acknowledged By Owner=Yes
Categories=Availability
Rule Name=RuleSet for all Production Targets, Acknowledgement Rule
Rule Owner=DKSHARMA
Root Cause Analysis Status=Neither Cause Nor Symptom
This incident has an event that is neither a cause nor a symptom.
Update Details:
Acknowledged by DKSHARMA

You can check the associated partner agent by either using SQL statement or from the Console.

select target_agent.target_name "Target Agent", 
partner_agent.target_name "Partner Agent"
from 
EM_AGENT_BUDDY_MAP eabm, 
mgmt_targets target_agent, 
mgmt_targets partner_agent 
where 
eabm.buddy_target_guid = partner_agent.target_guid and
eabm.agent_target_guid = target_agent.target_guid and
target_agent.target_name = 'mention_agent_name';

 

Steps to change Partner Agent for any of the Target Agent.

Step 1:  Log into Enterprise Manager Command Line Interface “emcli”.

Step 2:  Run emcli sync.

Step 3: Crosscheck and Remove the old partnership.

$ ./emcli manage_agent_partnership –remove_agent_partnership -monitored_agent= hanproddb1.dksharma.com:3872 -partner_agent=hanprodap1.dksharma.com:3872
 $ Manage Agent Partnership operation completed successfully

 

Step 4: Add a new partner agent

$ ./emcli manage_agent_partnership -add_agent_partnership -monitored_agent= hanproddb1.dksharma.com:3872 -partner_agent=hanprodap1.dksharma.com:3872
$ Manage Agent Partnership operation completed successfully

For more information on “emcli” verbs check: http://docs.oracle.com/cd/E24628_01/em.121/e17786/cli_verb_ref.htm#EMCLI200

 

Thanks

ADDKS