<?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 Re: HP SIM 6.0 and multiple Command view managing differnt EVAÂ´s in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659135#M41587</link>
    <description>Have you logged a support case on this?  If so, what is the number?&lt;BR /&gt;&lt;BR /&gt;thanks.</description>
    <pubDate>Mon, 12 Jul 2010 20:00:12 GMT</pubDate>
    <dc:creator>Darrin Rawls</dc:creator>
    <dc:date>2010-07-12T20:00:12Z</dc:date>
    <item>
      <title>HP SIM 6.0 and multiple Command view managing differnt EVAÂ´s</title>
      <link>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659133#M41585</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;I have recently installed HP SIM 6.0. I am currently having some problems with previous discovery of EVA systems to stay configured in the HP SIM database. &lt;BR /&gt;&lt;BR /&gt;The problem is related to that we have 2 command view servers acting backup for one another. Both Command View servers can see 4 EVAÂ´s but each can only manage 2 EVAÂ´s in Command View EVA. When I had only discovered the first Command View EVA server everything works fine, but when discovering the other one all 4 EVAÂ´s hw status getÂ´s into a transitional state. &lt;BR /&gt;&lt;BR /&gt;Running HP SIM 6.0, Command View EVA 9.2, wccproxy 6.0&lt;BR /&gt;&lt;BR /&gt;SMI-S info: &lt;BR /&gt;&lt;BR /&gt;CXWSCimom = 2.2.0.0 &lt;BR /&gt;EVAProvider = 9.2.0.0&lt;BR /&gt;&lt;BR /&gt;I can still view EVA information in HP SIM as ports, storage etc but I am afraid that the state they are in we are unable to get any functional remote support reporting. &lt;BR /&gt;&lt;BR /&gt;Attaching a picture of the state they are in now. &lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Magnus</description>
      <pubDate>Fri, 09 Jul 2010 05:49:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659133#M41585</guid>
      <dc:creator>Magnus Angelow</dc:creator>
      <dc:date>2010-07-09T05:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: HP SIM 6.0 and multiple Command view managing differnt EVAÂ´s</title>
      <link>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659134#M41586</link>
      <description>Hi again&lt;BR /&gt;&lt;BR /&gt;Sure I know that one solution would be to only use one Command View Server managing all EVAs, but I am looking for another solution to solve the matter. &lt;BR /&gt;&lt;BR /&gt;Magnus</description>
      <pubDate>Fri, 09 Jul 2010 06:00:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659134#M41586</guid>
      <dc:creator>Magnus Angelow</dc:creator>
      <dc:date>2010-07-09T06:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: HP SIM 6.0 and multiple Command view managing differnt EVAÂ´s</title>
      <link>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659135#M41587</link>
      <description>Have you logged a support case on this?  If so, what is the number?&lt;BR /&gt;&lt;BR /&gt;thanks.</description>
      <pubDate>Mon, 12 Jul 2010 20:00:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hp-sim-6-0-and-multiple-command-view-managing-differnt-eva%C3%A2-s/m-p/4659135#M41587</guid>
      <dc:creator>Darrin Rawls</dc:creator>
      <dc:date>2010-07-12T20:00:12Z</dc:date>
    </item>
  </channel>
</rss>

