<?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: OVSOM3.2 Off SMA, SMI-S, MPIO Basic, CVEVA4.1, W2k3 in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614955#M14258</link>
    <description>Try to connect "old way", hp OpenView Management proxy. &lt;BR /&gt;I got it work.&lt;BR /&gt;CIMOM won't work me either.&lt;BR /&gt;OVSAM3.2, Off SMA 3.3.3, SMI-S</description>
    <pubDate>Tue, 30 Aug 2005 14:23:21 GMT</pubDate>
    <dc:creator>name_27</dc:creator>
    <dc:date>2005-08-30T14:23:21Z</dc:date>
    <item>
      <title>OVSOM3.2 Off SMA, SMI-S, MPIO Basic, CVEVA4.1, W2k3</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614954#M14257</link>
      <description>I have the above configuration (1) and am having trouble getting CIMOM to work. OVSOM automatically discovered the above CIMOM agent. But does not discover the EVAs. I configured the passphases on the CIMOM as well. Did I leave out something or is something not supported here?&lt;BR /&gt;&lt;BR /&gt;I also have a 2nd SMA 2.1 (2) and installed hpSMISeva4_1 and EVA 4.1 on it as well, however OVSOM does not discover the SMA CIMOM.  I tried starting the CIMOM service and it stops with no information.&lt;BR /&gt;&lt;BR /&gt;I installed the Generic SMI-S DPI on (1)&lt;BR /&gt;hpSIMSeva4_1 on (1&amp;amp;2)&lt;BR /&gt;I did install the EVA DPI on (1) but took it off after reading it was not needed.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Aug 2005 12:21:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614954#M14257</guid>
      <dc:creator>Gary crews</dc:creator>
      <dc:date>2005-08-30T12:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: OVSOM3.2 Off SMA, SMI-S, MPIO Basic, CVEVA4.1, W2k3</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614955#M14258</link>
      <description>Try to connect "old way", hp OpenView Management proxy. &lt;BR /&gt;I got it work.&lt;BR /&gt;CIMOM won't work me either.&lt;BR /&gt;OVSAM3.2, Off SMA 3.3.3, SMI-S</description>
      <pubDate>Tue, 30 Aug 2005 14:23:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614955#M14258</guid>
      <dc:creator>name_27</dc:creator>
      <dc:date>2005-08-30T14:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: OVSOM3.2 Off SMA, SMI-S, MPIO Basic, CVEVA4.1, W2k3</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614956#M14259</link>
      <description>I read that the OffSMA config has to use &lt;BR /&gt;SMI-S - not true?</description>
      <pubDate>Tue, 30 Aug 2005 15:37:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614956#M14259</guid>
      <dc:creator>Gary crews</dc:creator>
      <dc:date>2005-08-30T15:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: OVSOM3.2 Off SMA, SMI-S, MPIO Basic, CVEVA4.1, W2k3</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614957#M14260</link>
      <description>think SMI-S is needed. I mean, don't use CIMOM as management proxy, use device type: Storage management appicance.</description>
      <pubDate>Tue, 30 Aug 2005 16:23:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/ovsom3-2-off-sma-smi-s-mpio-basic-cveva4-1-w2k3/m-p/3614957#M14260</guid>
      <dc:creator>name_27</dc:creator>
      <dc:date>2005-08-30T16:23:36Z</dc:date>
    </item>
  </channel>
</rss>

