<?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: Problem with WBEM subscription for EVA SMI-S Provider in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726228#M18216</link>
    <description>Hello Donald,&lt;BR /&gt;&lt;BR /&gt;thanks, but there is now firewall or other port blocking software involved in this communication.&lt;BR /&gt;&lt;BR /&gt;Any other idea?</description>
    <pubDate>Wed, 08 Feb 2006 08:19:15 GMT</pubDate>
    <dc:creator>Paul Kratz</dc:creator>
    <dc:date>2006-02-08T08:19:15Z</dc:date>
    <item>
      <title>Problem with WBEM subscription for EVA SMI-S Provider</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726226#M18214</link>
      <description>We installed the Command View for EVA (CV4EVA) and the SMI-S Provider on a ProLiant Server with W2k3 SP1. Then we went to Options -  Protocol settings – Global Protocol settings - Default WBEM settings and add the User “administrator” with the password “administrator”.&lt;BR /&gt;&lt;BR /&gt;CV4EVA works fine and SIM discovered the EVA6000 and shows there data and status.&lt;BR /&gt;&lt;BR /&gt;Then we went to Options – Events – Subscribe to WBEM  Events and run the task to the Server where the SMI-S Provider is installed. The subscription failed with the error message:&lt;BR /&gt;&lt;BR /&gt;Create Subscriptions for:&lt;BR /&gt;&lt;BR /&gt;dephbghhc1ms1ts&lt;BR /&gt;&lt;BR /&gt;FAILED to create indication subscription.&lt;BR /&gt;&lt;BR /&gt;No valid path to talk to CIMOM for &lt;SERVERNAME&gt;&lt;BR /&gt;&lt;BR /&gt;What’s wrong?&lt;BR /&gt;&lt;/SERVERNAME&gt;</description>
      <pubDate>Tue, 07 Feb 2006 12:04:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726226#M18214</guid>
      <dc:creator>Paul Kratz</dc:creator>
      <dc:date>2006-02-07T12:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with WBEM subscription for EVA SMI-S Provider</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726227#M18215</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I had this same issue on variosu Linux boxes and the fix was to open the TCP ports for WBEM.  The port numbers are &lt;BR /&gt;&lt;BR /&gt;5988    tcp     wbem-http               WBEM HTTP&lt;BR /&gt;5988    udp     wbem-http               WBEM HTTP&lt;BR /&gt;5989    tcp     wbem-https              WBEM HTTPS&lt;BR /&gt;5989    udp     wbem-https              WBEM HTTPS&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Feb 2006 07:49:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726227#M18215</guid>
      <dc:creator>Donald Rye</dc:creator>
      <dc:date>2006-02-08T07:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with WBEM subscription for EVA SMI-S Provider</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726228#M18216</link>
      <description>Hello Donald,&lt;BR /&gt;&lt;BR /&gt;thanks, but there is now firewall or other port blocking software involved in this communication.&lt;BR /&gt;&lt;BR /&gt;Any other idea?</description>
      <pubDate>Wed, 08 Feb 2006 08:19:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-with-wbem-subscription-for-eva-smi-s-provider/m-p/3726228#M18216</guid>
      <dc:creator>Paul Kratz</dc:creator>
      <dc:date>2006-02-08T08:19:15Z</dc:date>
    </item>
  </channel>
</rss>

