0 Introscope Host Adapter Agent(s) from host name are connected to the EM

[Former Member]

Dear  Team,

I have installed diagnosis agent and host agent for R/3 Production server(which is in cluster environment).

I n which i have select Agent on fly for physical server of R/3 diagnosis agent it it showing following error below

Error log:

On instance : pcbe6ci
Created 0 action(s).
0 Introscope Host Adapter Agent(s) from host pcbe6ci are connected to the EM.
Introscope Host Adapter configuration finished without errors, but on Enterprise Manager (utclsm:6001) no Introscope Host Adapter was detected from host pcbe6ci. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
The Wily EM host name 'utclsm' can not be resolved by the agent running on pcbe6ci/pcbe6ci (pcbe6ci). Please provide a different host name, or adjust network connectivity.

Kindly advise,

Regards,

IMRAN.

[daniel_nicol]

Hi IMRAN,

This kind of issue occurs either because the agent cannot reach the EM host, therefore you have to try a telnet from the managed system to the EM host and port.

Besides that, if the EM is overloaded, the agent may not be able to connect, check the Enterprise Manager performance using the tool attached to KBA 2156320. It will provide recommendations in case any adjustment is necessary.

If the issue persists, attach file jvm_smdagent.out .

Kind regards,

Daniel.

[Former Member]

Dear Daniel,

Thanks for your reply,

Please  Suggest which port need to be open form  managed system?

Willy interscope Ip adress:10.1.66.189 port no:6001

Please find the attached snap shot OF WILLY INTERSCOPE PORT details , log of JVM_SMDAGENT.OUT  and EM_PERFLOG ANALYZER snap shot below

JVM_SMDAGENT.OUT:

AgentLauncherLogger [debug]: run
AgentLauncherLogger [debug]: ***********************************************************************
AgentLauncherLogger [debug]: * LoadBalanceRestricted=false
AgentLauncherLogger [debug]: * P4ClassLoad=P4Connection
AgentLauncherLogger [debug]: * SAPDBHOST=
AgentLauncherLogger [debug]: * SAPINFO=DA4_95_smdagent
AgentLauncherLogger [debug]: * SAPJStartVersion=721, patch 402, changelist 1562712, hpia64, optu (EXT) (Mar  9 2015, 04:39:10)
AgentLauncherLogger [debug]: *  SAPMYNAME=pcbe6ci_DA4_95
AgentLauncherLogger [debug]: * SAPSTARTUP=1
AgentLauncherLogger [debug]: * SAPSYSTEM=95
AgentLauncherLogger [debug]: * SAPSYSTEMNAME=DA4
AgentLauncherLogger [debug]: * application.home=/usr/sap/DA4/SMDA95/exe
AgentLauncherLogger [debug]: * com.sap.vm.codeline=61_REL
AgentLauncherLogger [debug]: * com.sap.vm.compressedoops=true
AgentLauncherLogger [debug]: * com.sap.vm.profilingserver=true
AgentLauncherLogger [debug]: * com.sap.vm.type=opt
AgentLauncherLogger [debug]: *  com.sap.vm.version=10
AgentLauncherLogger [debug]: * env.class.path=
AgentLauncherLogger [debug]: * file.encoding=ISO8859-1
AgentLauncherLogger [debug]: * file.encoding.pkg=sun.io
AgentLauncherLogger [debug]: * file.separator=/
AgentLauncherLogger [debug]: * j2ee.dbhost=
AgentLauncherLogger [debug]: * java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
AgentLauncherLogger [debug]: * java.awt.printerjob=sun.print.PSPrinterJob
AgentLauncherLogger [debug]: * java.class.path=/usr/sap/DA4/SMDA95/exe/jstart71.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx_tools.jar:/usr/sap/DA4/SMDA95/exe/jre/lib/iqlib.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/tools.jar:lib/iaik/iaik_jce.jar:lib/iaik/iaik_jsse.jar:lib/iaik/iaik_smime.jar:lib/iaik/iaik_ssl.jar:lib/iaik/w3c_http.jar:../exe/jstartupapi.jar:../exe/jstartupimpl.jar:lib/patch_7.10.13.0.20150224225905/launcher/smdagentlauncher.jar:../exe/jperflib.jar
AgentLauncherLogger [debug]: * java.class.version=50.0
AgentLauncherLogger [debug]: * java.endorsed.dirs=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/endorsed
AgentLauncherLogger [debug]: * java.ext.dirs=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ext-sap:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ext
AgentLauncherLogger [debug]: *  java.home=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre
AgentLauncherLogger [debug]: * java.io.tmpdir=/var/tmp/
AgentLauncherLogger [debug]: * java.library.path=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ia64/server:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ia64:/usr/sap/DA4/SMDA95/j2ee/os_libs:/usr/sap/DA4/SMDA95/exe
AgentLauncherLogger [debug]: * java.runtime.name=Java(TM) SE Runtime Environment
AgentLauncherLogger [debug]: * java.runtime.version=6.1.076
AgentLauncherLogger [debug]: * java.specification.name=Java Platform API Specification
AgentLauncherLogger [debug]: * java.specification.vendor=Sun Microsystems Inc.
AgentLauncherLogger [debug]: * java.specification.version=1.6
AgentLauncherLogger [debug]: * java.vendor=SAP AG
AgentLauncherLogger [debug]: *  java.vendor.url=http://www.sap.com/
AgentLauncherLogger [debug]: * java.vendor.url.bug=http://service.sap.com/support
AgentLauncherLogger [debug]: * java.version=1.6.0_95
AgentLauncherLogger [debug]: * java.vm.compressedOopsMode=32-bits Oops
AgentLauncherLogger [debug]: * java.vm.info=Apr 23 2015 13:48:20 - 61_REL - optU - hpux ia64 - 6 - bas2:239155 (mixed mode)
AgentLauncherLogger [debug]: * java.vm.name=SAP Java Server VM
AgentLauncherLogger [debug]: * java.vm.specification.name=Java Virtual Machine Specification
AgentLauncherLogger [debug]: * java.vm.specification.vendor=Sun Microsystems Inc.
AgentLauncherLogger [debug]: * java.vm.specification.version=1.0
AgentLauncherLogger [debug]: * java.vm.vendor=SAP AG
AgentLauncherLogger [debug]: * java.vm.version=6.1.076 25.45-b02
AgentLauncherLogger [debug]: * jstartup.debuggable=yes
AgentLauncherLogger [debug]: * jstartup.mode=JSTART
AgentLauncherLogger [debug]: * jstartup.ownHardwareId=F0831984652
AgentLauncherLogger [debug]: * jstartup.ownProcessId=17339
AgentLauncherLogger [debug]: * jstartup.whoami=java
AgentLauncherLogger [debug]: * line.separator=

AgentLauncherLogger [debug]: * os.arch=ia64
AgentLauncherLogger [debug]: * os.name=HP-UX
AgentLauncherLogger [debug]: * os.version=B.11.31
AgentLauncherLogger [debug]: * path.separator=:
AgentLauncherLogger [debug]: * sun.arch.data.model=64
AgentLauncherLogger [debug]: * sun.boot.class.path=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/sapjvm-alt-rt.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/resources.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/rt.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/sunrsasign.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/jsse.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/jce.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/charsets.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/jfr.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/classes
AgentLauncherLogger [debug]: * sun.boot.library.path=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ia64
AgentLauncherLogger [debug]: * sun.cds.enableSharedLookupCache=false
AgentLauncherLogger [debug]: * sun.cpu.endian=big
AgentLauncherLogger [debug]: * sun.cpu.isalist=
AgentLauncherLogger [debug]: * sun.io.unicode.encoding=UnicodeBig
AgentLauncherLogger [debug]: * sun.java.launcher=jstart
AgentLauncherLogger [debug]: * sun.jnu.encoding=ISO8859-1
AgentLauncherLogger [debug]: * sun.management.compiler=HotSpot 64-Bit Tiered Compilers
AgentLauncherLogger [debug]: * sun.os.patch.level=unknown
AgentLauncherLogger [debug]: * sys.global.dir=/usr/sap/DA4/SYS/global
AgentLauncherLogger [debug]: * user.country=US
AgentLauncherLogger [debug]: * user.dir=/usr/sap/DA4/SMDA95/SMDAgent
AgentLauncherLogger [debug]: * user.home=/home/da4adm
AgentLauncherLogger [debug]: * user.language=en
AgentLauncherLogger [debug]: * user.name=da4adm
AgentLauncherLogger [debug]: * user.timezone=
AgentLauncherLogger [debug]: ***********************************************************************
AgentLauncherLogger [info]: Running SMD Agent ...
adding Provider IAIK...

Java version number: 1.6.0_95
Java compiler: null
Java vendor-specific string: SAP AG
Java vendor URL: http://www.sap.com/
Java installation directory: /usr/sap/DA4/SMDA95/exe/sapjvm_6/jre
Java class format version number: 50.0
Java class path: /usr/sap/DA4/SMDA95/exe/jstart71.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx_tools.jar:/usr/sap/DA4/SMDA95/exe/jre/lib/iqlib.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/tools.jar:lib/iaik/iaik_jce.jar:lib/iaik/iaik_jsse.jar:lib/iaik/iaik_smime.jar:lib/iaik/iaik_ssl.jar:lib/iaik/w3c_http.jar:../exe/jstartupapi.jar:../exe/jstartupimpl.jar:lib/patch_7.10.13.0.20150224225905/launcher/smdagentlauncher.jar:../exe/jperflib.jar
Operating system name: HP-UX
Operating system architecture: ia64
Operating system version: B.11.31

Installed security providers providers:

Provider 1: IAIK  version: 3.1810000000000005
Provider 2: SUN  version: 1.6
Provider 3: SunRsaSign  version: 1.5
Provider 4: SunJSSE  version: 1.6
Provider 5: SunJCE  version: 1.6
Provider 6: SunJGSS  version: 1.0
Provider 7: SunSASL  version: 1.5
Provider 8: XMLDSig  version: 1.0
Provider 9: SunPCSC  version: 1.6
[ms://10.1.66.189:8102/P4] Agent ready.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.2.4.0 (Build 476771)
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.6.0_95" from SAP AG
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DA4/SMDA95/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DA4/SMDA95/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/DA4/SMDA95/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/ext was successfully located
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.                 
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA95" based on the value of the System Property "com.wily.introscope.agent.agentName".
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA95
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
12/15/15 11:56:00 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (1).
Initialization done.
12/15/15 11:56:10 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (2).
12/15/15 11:56:20 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (3).
12/15/15 11:56:30 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (4).
12/15/15 11:56:40 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (5).
12/15/15 11:56:50 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (6).
12/15/15 11:57:00 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (7).
12/15/15 11:57:10 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (8).
12/15/15 11:57:20 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (9).
12/15/15 11:57:30 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (10).
12/15/15 11:57:30 PM IST [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further failures will not be logged.

EM PERFLOG ANALYZER

Kindly advise,

Regards,

IMRAN.

[daniel_nicol]

Hi IMRAN,

Please increase the EM heap memory as recommended by the tool and restart the EM.

Please also try a telnet from your managed system host to host "utclsm"  port 6001. If it does not work, then the Introscope Host Adapter can't connect either due to a network issue, you have to make sure that name "utclsm" can be resolved correctly in your network.

Make sure you perform the test using the host name "utclsm" and not the direct IP, it has to be tested exactly as shown in the logs.

After you do this, restart the SMD Agent and check in the EM webview / workstation if the respective host is shown.

Kind regards,

Daniel.

[sachingupta28]

Hi Imran,

Are you looking forward to the managed system configuration or only host configuration.

If your aim is to managed system configuration,  save the host configuration at step-2 after applying the on the fly check and save it and leave host configuration tab.

Now start managed system configuration,  follow all the steps, In step 3 make sure that diagnostic agent assignment is correct, diagnostic agent is running and in step 5 you will enter details for Wily EM and managed system. Step 8 you will be running Introscope host adapter.

Let me know if this works.

Thanks and Regards

Sachin Gupta

[sachingupta28]

Hi Imran,

you also need to increase Wily EM heap, as already suggested by other members.

Check OSS note 1630229 for more details.

Thanks and Regards

Sachin Gupta

[Former Member]

Hi Team,

Issue is resolved and thanks for your suggestion.

I have fixed the  heap memory issue according to sap note:1630229 suggested and interscope host agent issue resolved as per suggested by Mr.Daniel nicol.

Regards,

Imran.

[Former Member]

Can you ping/resolve the host utclsm from your ERP system. Try to use the FQDN host name for utclsm. if not possible then you may have to amend the host file on both the clustered system for host utclsm.