does the agent version show as 8.2.01.158 in the RSCD_VERSION property on the target server ?
what is the latest version of the vmware CO in the config object dictionary and is that what is in the dco job?
properties: RSCD_VERSION 18.104.22.168
config object dictionary view: VMware vCenter Server 82010000
In DCO job: Global Configuration Objects: VMware vCenter Server v82,010,000
i'm not sure if we incremented the co version in 8.2.01.256.
do you have the CONNECTION and VIRTUALIZATION psi's setup properly for this server ?
sorry wrong information app server version 8.2.01.273 and all instances of CONNECTION and VIRTUALIZATION have been configured well.
on the dco job can you set the 'DEBUG_MODE_ENABLED' property to true, run the job and post the debug log (will be in NSH/tmp/debug/<appserver name> on the appserver(s) involved w/ running the job)
After the changing the job property of Distribute Configuration Objects I have attached the debug file.
please find attachment.
I found the answer that if you are using 8.2.01.158 version of RSCD then you have to use 8.2.01.158 version of Application server. Till the patch level the version must match with its related components.
yes, that is expected...
Same thing happened to me with version 8.5SP1P5. Our agents are 8.5SP1P4 and our app server is 8.5SP1P5 (due to needing patch 5 for app server/console vulnerability, but not needing for agents.)
Where it says the agent has to be the same for Virtualization Objects is under 4.4 Agent compatibility which we didn't see as we just went to 6.3.3.
I think it would be helpful if it were also here:
6.3.3 Setting up a VMware vSphere environment - Installing the Windows agent on the vCenter server. Or at the very least, the error and solution should be in the TIP under 6.3.3. Adding the vCenter server to BMC Server Automation - Step 8, along with the other error/solution that is already there.
If you receive the following message when running the Distribute Configuration Objects
"Warning ignoring class BMC_VMware_VirtualInfrastructureManager version: xxxxx because it is not applicable on server <vCenterServerName>"
Ensure the agent on the vCenter server is the exact version (including patch level) of the application server. See Agent Compatibility Section 4.4.