<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Setup Managed System? in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151440#M43</link>
    <description>In chapter 7 of the SIM Install &amp;amp; User guide, it says to Launch SSH and type command mxagentconfig -g.  Do I need to do that on the CMS as well?  All I have setup so far is the CMS.  When I try that command I get the GUI and I type in the Hostname, Username/Password and Connect CMS.  It says it is not able to connect.  Is the CMS a managed system as well?  Why the SSH stuff?  What does it mean by "Copy the SSH generated key from the CMS to the managed system"?  Do I need to update my Web Management agents on each of my Proliants first?</description>
    <pubDate>Tue, 23 Dec 2003 02:01:34 GMT</pubDate>
    <dc:creator>Jeff Tangen</dc:creator>
    <dc:date>2003-12-23T02:01:34Z</dc:date>
    <item>
      <title>Setup Managed System?</title>
      <link>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151440#M43</link>
      <description>In chapter 7 of the SIM Install &amp;amp; User guide, it says to Launch SSH and type command mxagentconfig -g.  Do I need to do that on the CMS as well?  All I have setup so far is the CMS.  When I try that command I get the GUI and I type in the Hostname, Username/Password and Connect CMS.  It says it is not able to connect.  Is the CMS a managed system as well?  Why the SSH stuff?  What does it mean by "Copy the SSH generated key from the CMS to the managed system"?  Do I need to update my Web Management agents on each of my Proliants first?</description>
      <pubDate>Tue, 23 Dec 2003 02:01:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151440#M43</guid>
      <dc:creator>Jeff Tangen</dc:creator>
      <dc:date>2003-12-23T02:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: Setup Managed System?</title>
      <link>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151441#M44</link>
      <description>Jeff -&lt;BR /&gt;&lt;BR /&gt;Let me start by saying that ssh is a secure shell utility. It provides a secure way to access the command prompt from a remote machine and it also comes with a bundle of useful tools that can also be used such as scp for secure copy and sftp for secure ftp etc. I would suggest that you brush up on openssh if you're going to use it. Although not needed for a seccessful implementation of SIM, It is useful for running command line tools.&lt;BR /&gt;&lt;BR /&gt;As stated in the user guide, You need to install openssh on the managed server in otherwords, the clien. Then run the mxagentconfig -g on the SIM server command prompt. You will only be able to connect after you installed and configured openssh on the client. The user guide as a pretty good section on how to setup the managed systems.</description>
      <pubDate>Tue, 23 Dec 2003 07:45:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151441#M44</guid>
      <dc:creator>Jadrice Toussaint</dc:creator>
      <dc:date>2003-12-23T07:45:25Z</dc:date>
    </item>
    <item>
      <title>Re: Setup Managed System?</title>
      <link>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151442#M45</link>
      <description>Jeff,&lt;BR /&gt;&lt;BR /&gt;No, you don't have to do that to the CMS - it should be setup properly during installation.&lt;BR /&gt;&lt;BR /&gt;SSH is only used for the command line tools that you want to run on the remote systems.  If you don't want to run those tools, then SSH isn't required.&lt;BR /&gt;&lt;BR /&gt;Please look at the readme PDF for instructions on getting SSH to work properly on Windows 2003 though - there is a big list of special steps to perform due to increased security in Windows 2003.</description>
      <pubDate>Sat, 03 Jan 2004 03:28:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/setup-managed-system/m-p/3151442#M45</guid>
      <dc:creator>Scott Shaffer</dc:creator>
      <dc:date>2004-01-03T03:28:52Z</dc:date>
    </item>
  </channel>
</rss>

