cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to see Agent in SMD

rahul_yedapally
Active Participant
0 Kudos

Dear All,

We executed below script in ECC Box (/usr/sap/DIA/SMDA98/script)

smdsetup sldconf hostname:"/H/218.200.109.165/S/3299/H/Varslmandev.DOMAIN.com" port:"8101" user:"SLDDSUSER" pwd:"XXXXX”

command execution was successful

Our solution Manager and ECC box are in different location connecting with the help of SAP Router

please find below logs

mar 11, 2015 2:43:47 AM [Thread[Connector,5,main]                    

] Info       [p4:///H/varslmandev.DOMAIN.com/S/3299:50000] Checking server availability...

Mar 11, 2015 2:43:47 AM [Thread[Connector,5,main]                   

] Warning    Connecting to SMD server p4:///H/varslmandev.DOMAIN.com/S/3299:50000 failed - error counter: 968 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.net.MalformedURLException: p4:/H/varslmandev.DOMAIN.com/S/3299:50000 : no port is specified in the URL andthe service does not have a defalut port]

Thanks,

Rahul Yedapally

Accepted Solutions (0)

Answers (17)

Answers (17)

rahul_yedapally
Active Participant
0 Kudos

Ricardo,

Tried but no luck , same issue

I have installed agent many times to few customers , but i am not where did i went wrong

its pending from my end since last week

can some give me correct solution for your reference i have attached all logs

ricardocarrega_filho
Participant
0 Kudos

Hi Rahul,

Can you verify if SAP note 1711920 - Connection to ICM using P4 protocoll fails is applicable on your case?

Regards,

Ricardo

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi,

Please share the smd trace log file from SMD directory.

rahul_yedapally
Active Participant
0 Kudos

Facing below issue while doing DIA agent installation

1. Host entries added

2. 8101 Ports is opened

3. Username and password is correct

rahul_yedapally
Active Participant
0 Kudos

Srinivsan,

Tried with script also , same issue

Ricardo carrega,

SAP Router tab has full access and permit to all * * *

Thanks,

Rahul Yedapally

ricardocarrega_filho
Participant
0 Kudos

Hi Rahul Yedapally,

On this case try re-installing your SMD/DAA agent using the latest SWPM / Kernel available in the Service Marketplace if you still haven't done so.

Also make sure you're using the latest host agent patch available. Last time I checked 205 was it.

Regards,

Ricardo

ricardocarrega_filho
Participant
0 Kudos

Rahul, have you added both 8101 and 50004 ports to your saprouttab file and restarted your SAPRouter instance after doing so?

Please check the following thread for details:

Best regards,

Ricardo

rahul_yedapally
Active Participant
0 Kudos

Can some one guide me

Thanks,

Rahul Yedapally

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

Press ok to continue after installation completed run the smdsetup.exe script to update.

smdsetup managingconf hostname:"servername" port:"xxxxx" user:"SOLMAN_ADMIN" pwd:"xxxx"

Regards,

V Srinivasan

rahul_yedapally
Active Participant
0 Kudos

Hi srinivasan,

i think its not an issue with user, No user SMS_Admin  exists

Thanks,

Rahul Yedapally

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

You can use SMS_ADMIN user instead of SMD_AGT.

Regards,

V Srinivasan

rahul_yedapally
Active Participant
0 Kudos

Hi All,

Can some-one help me how do i connect SMD agent with help of SAP Router  (SAP Router format )

tried below steps

1. while doing DIA agent installation with Help of SWPM , Facing below issue

2. Port:8101 is opened even facing same issue and SMD_AGT password is correct

3. check below step , its basis authorization 

Thanks,

Rahul Yedapally 

rahul_yedapally
Active Participant
0 Kudos

HI Amar,

------- VM Properties ----------

OS                            : Windows NT (unknown)

OS Version                    : 6.3

OS Architecture               : amd64

OS data model                 : 64

Java Vendor                   : SAP AG

Java Home                     : C:\Program Files\sapinst_instdir\GENERIC\SMD\INST\sapjvm\sapjvm_6\jre

Java Version                  : 1.6.0_65

Java Classpath                : lib\sapxmltoolkit.jar;lib\smdagent.jar;lib\tc_sec_secstorefs.jar;lib\tc_sec_https.jar;lib\iaik_jce_export.jar;lib\logging.jar;lib\smdserver.jar;lib\exception.jar;lib\sapj2eeclient.jar;lib\com_sap_pj_jmx.jar;lib\httpclient.jar;lib\jARM.jar;lib\lcrclient.jar;lib\sldclient.jar;lib\sldserv.jar;lib\launcher\smdagentlauncher.jar;lib\sapni.jar;.\jstartup.jar;.\jstartupapi.jar;.\jstartupimpl.jar

Java Runtime version          : 6.1.059

Java Specfic. version         : 1.6

File Encoding                 : Cp1252

Console Encoding              : null

HTTP Proxy                    : null

HTTP Proxy port               : null

HTTP non Proxy hosts          : null

smd class version:            : 7.10.8.0.20131127231804

--------------------------------

Check Prerequisites:

OK.

------- Dump Input parameters ----------

port                          : 8101

connection                    : ms

pwd                           : *****************

javahome                      : C:\Program Files\sapinst_instdir\GENERIC\SMD\INST\sapjvm\sapjvm_6

hostname                      : 216.200.129.166

user                          : SMD_AGT

------------------------------------

Start the Check connection to Managing system prerequisite for Diagnostics agent installation...

- STEP  1 : checking Connection to SMD Server

SMD Server check completed successfully

- STEP 2: generating SecStore Environment

External Command Executed:

C:\Program Files\sapinst_instdir\GENERIC\SMD\INST\sapjvm\sapjvm_6\bin\java.exe -DP4ClassLoad=P4Connection -Dsap.p4.remote_classloading=false -cp "lib\sapxmltoolkit.jar;lib\smdagent.jar;lib\tc_sec_secstorefs.jar;lib\tc_sec_https.jar;lib\iaik_jce_export.jar;lib\logging.jar;lib\smdserver.jar;lib\exception.jar;lib\sapj2eeclient.jar;lib\com_sap_pj_jmx.jar;lib\httpclient.jar;lib\jARM.jar;lib\lcrclient.jar;lib\sldclient.jar;lib\sldserv.jar;lib\launcher\smdagentlauncher.jar;lib\sapni.jar;.\jstartup.jar;.\jstartupapi.jar;.\jstartupimpl.jar" com.sap.security.core.server.secstorefs.SecStoreFS create -f "C:\Program Files\sapinst_instdir\GENERIC\SMD\INST\SMDAgent\configuration\secstore.properties" -k "" -noenc

secstore.properties: has been created.

secstore.properties: update the property smd/agent/User but no previous value existing, so use insert method.

secstore.properties: property smd/agent/User updated.

secstore.properties: update the property smd/agent/Password but no previous value existing, so use insert method.

secstore.properties: property smd/agent/Password updated.

STEP  - Agent secstore file generated.

- STEP 3: checking P4 Connection

P4 Connection to SMD Server failed

Root exception is:

Exception:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:

varsolmandev.Domain.com:50004 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 216.201.124.166 and port: 50004]

  at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)

  at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

  at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)

  at javax.naming.InitialContext.init(InitialContext.java:223)

  at javax.naming.InitialContext.<init>(InitialContext.java:197)

  at com.sap.smd.setup.tasks.agent.configuration.check.CheckConfigurationMonitoringData.checkP4Connection(CheckConfigurationMonitoringData.java:287)

  at com.sap.smd.setup.tasks.agent.configuration.check.CheckConfigurationMonitoringData.executeTasks(CheckConfigurationMonitoringData.java:141)

  at com.sap.smd.setup.tasks.agent.configuration.check.CheckConfigurationMonitoringData.main(CheckConfigurationMonitoringData.java:71)

Caused by: com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:

varsolmandev.Domain.com:50004 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 216.200.129.166 and port: 50004

  at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:57)

  at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:33)

  at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)

  ... 7 more

2015.03.10 07:01:22

Task completed with status ERROR (7)

Former Member
0 Kudos

hi Rahul,

For the error its pretty clear that the SMD setup is unable to connect to P4 port.


- STEP 3: checking P4 Connection

P4 Connection to SMD Server failed

Root exception is:

Exception:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:

varsolmandev.Domain.com:50004 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 216.201.124.166 and port: 50004]

and the 2ndly as your using a saprouter i will recommend to connect using Message server port for the Solution manager. AS most of the occasion P4 port is not allowed on saprouter.

So can you give try once with the sap ms port of Solman.

Let us know the update.

Regrds,

Ram

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

You try the saprouter

# Connection trought saprouter

smdsetup addsaprouter route:"/H/x.x.x.x/S/3299/H/solman.domain.com/S/3299"

# Update server name on smd

smdsetup changeservername servername:"servername"

# Connect to solution manager

smdsetup managingconf hostname:"servername" port:"5xxxx" user:"SMD_USER" pwd:"xxxxxxx"

# Connect to solution manager trough port or P4

smdsetup managingconf hostname:"servername" port:"xxxxx" user:"SOLMAN_ADMIN" pwd:"xxxx"

# Connection trought saprouter

smdsetup addsaprouter route:"/H/x.x.x.x/S/3299/H/solman.domain.com/S/3299"

# Registration of agent on sld

smdsetup sldconf hostname:"servername" port:"5xxxx" user:"j2ee_admin" pwd:"xxxx"

just done, restart DAA and check log

rahul_yedapally
Active Participant
0 Kudos

Hi Srinivasan,

Let me put my issue more clearly..

First i have tried with script execution  with help of message port , its was not working

Note: My solution Manger and ECC box are on different domain and different network

so i have re-installed and when i was trying to install agent with Help of SAP Router even installation was also not success..

I have installed with-out SLD and run the script manually

so tried with all alternatives bad luck ....... Not working

Manually edited the runtime properties /(F:\usr\sap\DAA\SMDA98\SMDAgent\configuration)

After edition of that now i can see the Agent in SLD ...but connection is getting failed

Please help me on that

Waiting for approvals , once Restart is done , i will update you

Thanks,

Rahul Yedapally

Former Member
0 Kudos

Dear Rahul,

Have you installed the SMD agent using SWPM software?

If yes, in the SWPM installer screen it will provide you the direct connection to Solman via Java SCS message server option along with the SAP Router checkbox in the next screen.

If you have done this and got any error in the SWPM GUI, please share the error.

Best regards,

Amarendra

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

After restart also not working, un-installa and re-install the DAA Instance, SAP also recommended the same.

rahul_yedapally
Active Participant
0 Kudos

HI Srinivasan

Thanks for the quick Response

Yes SMD agent directory has full permissions..8101 Ports are opened even i am facing port issue

Please find below logs for your reference

Mar 11, 2015 10:08:08 AM [Thread[Connector,5,main]                     ] Info       [p4://varsolmandev.DOMAIN.com:8101/P4] Checking server availability...

Mar 11, 2015 10:08:09 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://varsolmandev.DOMAIN.com:8101/P4 failed - error counter: 57 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:

varsolmandev.yash.com:8101 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 215.201.159.166 and port: 8101]

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59804'.

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Info       [p4://varsolmandev.DOMAIN.com:8101/P4] Checking server availability...

Mar 11, 2015 10:08:44 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://varsolmandev.DOMAIN.com:8101/P4 failed - error counter: 58 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:

varsolmandev.DOMAIN.com:8101 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 215.201.159.166 and port: 8101]

Thanks,

Rahul Yedapally 

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

Stop SAP and restart the OS.

Regards,

V Srinivasan

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

above screen in Details column please "show" and paste the log.

and give full permission for SMD agent directory.

Regards,

V Srinivasan

rahul_yedapally
Active Participant
0 Kudos

Dear All,

Facing an issue with Agent connectivity, can some one help me

Thanks,


Rahul Yedapally 

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Rahul,

Regards,

V Srinivasan

symon_braunbaer
Participant
0 Kudos

Content unavailable

rishav54
Active Contributor
0 Kudos

Hi,

Check this

http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

Please insure the P4 port is correctly maintained.

Regards

Rishav

rahul_yedapally
Active Participant
0 Kudos

Hi Rishav,

Yes as per above link , its looks every thing is correct