<?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: Mismatch between VCA and SIM status in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183872#M32786</link>
    <description>That did not change the behavior I'm seeing. I installed the small hotfix from that page (SIM52_hotfix-win.exe) that said it addressed this issue, not the large upgrade. Was the one I applied the one you were referring to?</description>
    <pubDate>Wed, 23 Apr 2008 13:46:24 GMT</pubDate>
    <dc:creator>Matt Finnigan</dc:creator>
    <dc:date>2008-04-23T13:46:24Z</dc:date>
    <item>
      <title>Mismatch between VCA and SIM status</title>
      <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183868#M32782</link>
      <description>My frustration with this suite of tools is mounting :-&amp;gt;&lt;BR /&gt;&lt;BR /&gt;I have a DL360 that SIM Advise and Repair said had two VCA problems (and no other problems) :&lt;BR /&gt;The Version Control Agent (VCA) on the system(s) is not configured to use a Version Control Repository Manager (VCRM), and so cannot determine if there is software or firmware available to install.&lt;BR /&gt;  &lt;BR /&gt; There is no software or firmware data stored for the system(s), but it appears that the system(s) have the necessary agents to report this data.&lt;BR /&gt;&lt;BR /&gt;Upon inspection of the VCA settings on the managed server, it wasn't using the proper account to get to the VCRM. I fixed it and the local agent says it checks out good. On the SIM, I have since run Software Polling against this managed server, and from Quick Launch I did an Identify Systems, and then went into Manage Communications and did an Update, and then an Advise and Repair. &lt;BR /&gt;&lt;BR /&gt;It's still showing the same problems with the VCA. The actual VCA (from SMH) on the managed system is still telling me it's fine.&lt;BR /&gt;&lt;BR /&gt;What am I doing wrong?</description>
      <pubDate>Mon, 21 Apr 2008 15:08:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183868#M32782</guid>
      <dc:creator>Matt Finnigan</dc:creator>
      <dc:date>2008-04-21T15:08:27Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch between VCA and SIM status</title>
      <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183869#M32783</link>
      <description>Hi Matt,&lt;BR /&gt;&lt;BR /&gt;Can i know what version of HP SIM you are running, If it is only HP SIM 5.2 : they is an problem with that. The problem in resolved in HP SIM 5.2 update 1, you can the find more the information under &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18013.www1.hp.com/products/servers/management/hpsim/dl_windows.html#windows" target="_blank"&gt;http://h18013.www1.hp.com/products/servers/management/hpsim/dl_windows.html#windows&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Apr 2008 17:05:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183869#M32783</guid>
      <dc:creator>Rider</dc:creator>
      <dc:date>2008-04-22T17:05:26Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch between VCA and SIM status</title>
      <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183870#M32784</link>
      <description>Oh gosh. Yeah, I'km running 5.2, no update. Was not aware that there was an update already...</description>
      <pubDate>Tue, 22 Apr 2008 17:10:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183870#M32784</guid>
      <dc:creator>Matt Finnigan</dc:creator>
      <dc:date>2008-04-22T17:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch between VCA and SIM status</title>
      <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183871#M32785</link>
      <description>There is already an update is avaliable for this problem.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Don't forget to assign the points.....</description>
      <pubDate>Tue, 22 Apr 2008 17:16:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183871#M32785</guid>
      <dc:creator>Rider</dc:creator>
      <dc:date>2008-04-22T17:16:10Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch between VCA and SIM status</title>
      <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183872#M32786</link>
      <description>That did not change the behavior I'm seeing. I installed the small hotfix from that page (SIM52_hotfix-win.exe) that said it addressed this issue, not the large upgrade. Was the one I applied the one you were referring to?</description>
      <pubDate>Wed, 23 Apr 2008 13:46:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183872#M32786</guid>
      <dc:creator>Matt Finnigan</dc:creator>
      <dc:date>2008-04-23T13:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch between VCA and SIM status</title>
      <link>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183873#M32787</link>
      <description>I'm seeing the same issue with many servers. I'm running 5.02.02. Is this fixed or not?</description>
      <pubDate>Wed, 28 Jan 2009 19:23:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mismatch-between-vca-and-sim-status/m-p/4183873#M32787</guid>
      <dc:creator>JasonWoerner</dc:creator>
      <dc:date>2009-01-28T19:23:26Z</dc:date>
    </item>
  </channel>
</rss>

