EM 13c: Deploying the JVMD Agent from Enterprise Manager 13c Cloud Control Fails with Error: Unable to connect to t3://<ip address>:<port>: Destination unreachable;
Last updated on MAY 31, 2017
Applies to:APM - Application Performance Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 13.2]
Information in this document applies to any platform.
In a multiple network card host, the agent installation is associated with one IP address, for instance 10.00.00.11.
Instead of listening on 10.00.00.11, each WebLogic domain's admin server is configured to listen on a different IP address than the agent's.
For example for a_domain and b_domain, a_domain's admin server is listening on 10.00.00.153 and b_domain's admin server is listening on 10.00.00.154.
Deploying the JVMD Agent from EM 13.2 for a_domain's admin server, which is listening on 10.44.20.153, fails with this characteristic error:
Unable to connect to 't3://10.00.00.11:39705': Destination unreachable;
Instead of using the domain target's actual admin URL, it uses the host agent's IP to attempt the connection.
Instead of the using domain target's actual admin URL, found it always use host agent's IP to make connection.
The host agent installed on target machine successfully without any problems.
In addition, all the WebLogic domains running on this physical machine can be added as middleware targets.
Since the Weblogic admin server's listen address is configured with an IP address which is different than the host agent's,
when deploying JVMD, it wrongly uses the agent's IP as the WebLogic admin URL to attempt the connection.
JVMD Agent deployment from Enterprise Manager (EM) 13.2 Cloud Control fails with the following error:
Job Steps Log for Job :Deploy JVMD Agent
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