<?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 Server Architecture in Server Management (Insight Manager 7)</title>
    <link>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916462#M6392</link>
    <description>I buidlng out a cim server to manage 2700 servers.  any thoughts.. Dual 2.4 Ghz, 2GB RAM, Raid 1 + 0 drives for DB.  I've seen documentation that recommneds seprationg the DB from cim.?????  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How many people can web in simaltaneously&amp;gt;</description>
    <pubDate>Sun, 02 Mar 2003 05:33:53 GMT</pubDate>
    <dc:creator>Gordon_16</dc:creator>
    <dc:date>2003-03-02T05:33:53Z</dc:date>
    <item>
      <title>Server Architecture</title>
      <link>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916462#M6392</link>
      <description>I buidlng out a cim server to manage 2700 servers.  any thoughts.. Dual 2.4 Ghz, 2GB RAM, Raid 1 + 0 drives for DB.  I've seen documentation that recommneds seprationg the DB from cim.?????  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How many people can web in simaltaneously&amp;gt;</description>
      <pubDate>Sun, 02 Mar 2003 05:33:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916462#M6392</guid>
      <dc:creator>Gordon_16</dc:creator>
      <dc:date>2003-03-02T05:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Server Architecture</title>
      <link>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916463#M6393</link>
      <description>I don't manage anything close to 2700 servers, but I don't find CIM to be processor intensive.  I'm running mine on a compaq DL380 G3 with 4 Gig of memory, and dual 2.4 Ghz Xeon's.  Only managing about 200 servers mind you, but our server is basically idling.  As far as I know, your not limited to how many people can connect to the console.  We keep our database on a seperate SQL box which I would recommend.  You can also gather a lot of information about your servers by directly querying the database.  Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Jeff</description>
      <pubDate>Mon, 03 Mar 2003 20:30:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916463#M6393</guid>
      <dc:creator>Jeff Mathews</dc:creator>
      <dc:date>2003-03-03T20:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: Server Architecture</title>
      <link>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916464#M6394</link>
      <description>2700 servers is a lot of servers. With that many, I'd expect you have a few test servers.&lt;BR /&gt;&lt;BR /&gt;Build a CIM server for some of the test servers first. See exactly how it performs, and work out how heavy the maintenance and deployment is going to take. This is as much technical as it is project management.&lt;BR /&gt;&lt;BR /&gt;Also, what is CIM going to give you that your current monitoring tool does not? We have seperate asset management and alerting tools already, so CIM does not give us a huge benefit.</description>
      <pubDate>Mon, 03 Mar 2003 21:33:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-insight/server-architecture/m-p/2916464#M6394</guid>
      <dc:creator>Jez Thomas</dc:creator>
      <dc:date>2003-03-03T21:33:13Z</dc:date>
    </item>
  </channel>
</rss>

