The SMD Agent 'Hades' hasn't been found!

Question

Hello,
I started to install and configure Wily Introscope on one of my satellite
system.
I have one problem on some systems with the name of the server. The name of the satellite system is "hades" with lower letter. I installed the SMDagent on this hades system, this was installed successful (please see the [Agent Administration picture|http://img28.imageshack.us/img28/4707/agentadministration.jpg]). My problem is when I start to configure the agent for hades system on Managed Systems running Managed Systems, here I get "The SMD Agent 'Hades' hasn't
been found!".(please see the [picture|http://img831.imageshack.us/img831/1260/setupwizard.jpg]) I think the problem is because the difference of capital
letter for server name "hades". The server name is "hades" (with lower"h"), and this is the name in Agent Administration (please see the difference between ["Hades and hades|http://img15.imageshack.us/img15/4707/agentadministration.jpg]"), but in Setup Wizard the name of the server is "Hades"(upper "H"). Can you help me with this issue, because I am not able to
continue because Agent is not available.
I want to inform you that I ran SMSY_SETUP in to transfer all the SLD information to SMSY and this was successful transferred.
Can you please tell me from where can come this server name with upper "H(ades)" . Only some systems have this problem, I configured another systems and those worked fine (the name of server was correctly (with lower characters).
Best regards,
Florin Radulea

Answer 1

There are two possibities.
1) You specified the SLD option when you installed the agent (I think this requires NW 7 SMD agent > ~14).
- On SM system go to RCA work center, select Agent Administration, then Agent Candidates.  As long as you registered the agent in the same SLD as SM uses, it should be visible in the SLD view.  You need to associate the agent with this SM and supply connection information - there is a button for this, but you need to fill in a userid and password...
The agent retrieves connection information (eventually) from SLD.
2) You didn't register the agent in SLD or the agent needs special information to connect to managing SM.
On OS level User smdadm (or DAAadm) there is a scripts directory
/usr/sap/SMD/J##/script - SMD 7.0
/usr/sap/DAA/SMDA##/script -- Diagnostic agent 7.1 or 7.2
Run smdsetup.sh (.bat for windows) - no options gives all the possible sub commands.
You need to specify info for "managingconf" sub command.
If you provided wrong SLD connection information you can correct with this script too. (sldconf subcommand)
You can also specify saprouter info...
With supplied (correct) managing connection information, the agent should show up on the Agent Administration page.
Note hostname is managing hostname, servername should be managed hostname.
smdsetup managingconf      hostname:"sapms://<fqn>" port:"<MS httpPort>"
                              [optional user:"<...>" pwd:"<...>" servername:"<...>"]
smdsetup managingconf      hostname:"<fqn>" port:"<p4 port>"
                              [optional user:"<value>" pwd:"<value>" servername:"<value>"]
The first form uses load balancing the second doesn't.  The port in the second should be 5##04.
Ckeck logs in work directory for error information (in case of typos, etc).  I think there may be a log in SMDAgent directory too.
Ken