Last updated on JUNE 19, 2017
Applies to:Application Management Pack for Oracle Communications - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
This article clarify the below queries related to Application Management Pack for Oracle Communications(AMP), 188.8.131.52.0 version, BRM Discovery.
EM 12cR4 BRM discovery with oracle.cgbu.ocom plugin version 184.108.40.206.0
Here the user discovered Production environment using Communications discovery wizard, but some targets are left in pending, and others show down status when they are actually up. They also deleted and rediscovered targets, but the result is same. Why?
Error in gcagent_errors.log:
Here the user upgraded the plugin to v 220.127.116.11.0 in the pre-production environment, then removed all the targets from OEM and ran the discovery over again.
3.1) Why don't the custom BRM components show up as targets in OEM?
3.2) Why do some components which have been removed from the pin_ctl.conf file show up as targets in down state?
Please advise if there are any possible metric extensions that the user could deploy in the interim that would supplement the monitoring provided by 18.104.22.168 for this environment?
Does OEM metric extensions have any BRM specific monitoring suggestions that may help supplement the monitoring?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms