<?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: CommandviewSDM in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732671#M36600</link>
    <description>&lt;!--!*#--&gt;I've doubled the thread size from it's default. I've deleted the config files (access and commIpAddr), and when reinstalled played with the default configuration, wildcard, and a localhost address. &lt;BR /&gt;&lt;BR /&gt;No luck yet. &lt;BR /&gt;&lt;BR /&gt;Thanks for the help.</description>
    <pubDate>Mon, 03 Jan 2011 21:52:48 GMT</pubDate>
    <dc:creator>Miles Denison</dc:creator>
    <dc:date>2011-01-03T21:52:48Z</dc:date>
    <item>
      <title>CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732662#M36591</link>
      <description>&lt;!--!*#--&gt;A bit of background first. I have a va7410, and a ds2405. After a long while of strenuous use my va7410 up and died, so I would like to throw the disks in the 2405. This would mean reformatting the block size from 520, to 512.&lt;BR /&gt;&lt;BR /&gt;After installing commandview in order to issue a JBODfmt, I'm getting errors when trying to use it: "launcher" yields "Error getting database reference from localhost", and "armdiscover" comes back with "Failed to obtain remote database interface to host: localhost"&lt;BR /&gt;&lt;BR /&gt;I have gone into the commIpAddr.txt, and access.dat and changed the IPs to match my current configuration (192.168.0.110). I've also uninstalled/reinstalled commandview a few times now to no avail.&lt;BR /&gt;&lt;BR /&gt;I can view the disks with an ioscan just fine.&lt;BR /&gt;&lt;BR /&gt;Is there some small step that I've missed during the install?&lt;BR /&gt;&lt;BR /&gt;Thanks for any help,&lt;BR /&gt;Miles.</description>
      <pubDate>Sun, 02 Jan 2011 20:42:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732662#M36591</guid>
      <dc:creator>Miles Denison</dc:creator>
      <dc:date>2011-01-02T20:42:51Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732663#M36592</link>
      <description>Please check this too:&lt;BR /&gt;&lt;BR /&gt;/opt/sanmgr/hostagent/config/access.dat</description>
      <pubDate>Mon, 03 Jan 2011 06:25:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732663#M36592</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2011-01-03T06:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732664#M36593</link>
      <description>as I mentioned above, I've checked access.dat and commIpAddr.txt already, and changed them both to 192.168.0.110.</description>
      <pubDate>Mon, 03 Jan 2011 07:10:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732664#M36593</guid>
      <dc:creator>Miles Denison</dc:creator>
      <dc:date>2011-01-03T07:10:34Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732665#M36594</link>
      <description>If you are planning to use the disks in DS2405 without the VA7410, then there is no need to use armdiscover / launcher. These commands will work only when you have access to Lun0 on VA7410 on the host. If VA7410 is dead, you can not use these commands.&lt;BR /&gt;&lt;BR /&gt;You can connect the DS2405 directly to the host and use them as normal disks and configure using LVM.&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jan 2011 08:45:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732665#M36594</guid>
      <dc:creator>hvhari</dc:creator>
      <dc:date>2011-01-03T08:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732666#M36595</link>
      <description>Ah. Well that would explain it.&lt;BR /&gt;&lt;BR /&gt;In that case how would I go about reformatting those disks back to 512 block size? mediainit only works with a 512 size I believe.</description>
      <pubDate>Mon, 03 Jan 2011 14:29:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732666#M36595</guid>
      <dc:creator>Miles Denison</dc:creator>
      <dc:date>2011-01-03T14:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732667#M36596</link>
      <description>I belive, it formatting to 512k block size will be automatically taken care via the usual process of adding the disks to LVM. I personally does not have any setup like this to test now.</description>
      <pubDate>Mon, 03 Jan 2011 14:42:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732667#M36596</guid>
      <dc:creator>hvhari</dc:creator>
      <dc:date>2011-01-03T14:42:19Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732668#M36597</link>
      <description>&amp;gt;&amp;gt; I belive, it formatting to 512k block size will be automatically taken care via the usual process of adding the disks to LVM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;No.&lt;BR /&gt;&lt;BR /&gt;You need command view SDM to do this.&lt;BR /&gt;&lt;BR /&gt;Remove the product, remove the files and directories that are left in /opt/sanmgr/ and install again:&lt;BR /&gt;&lt;BR /&gt;rm -fR /opt/sanmgr&lt;BR /&gt;&lt;BR /&gt;rm -fR /etc/opt/sanmgr&lt;BR /&gt;&lt;BR /&gt;rm -fR /var/opt/sanmgr&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jan 2011 15:31:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732668#M36597</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2011-01-03T15:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732669#M36598</link>
      <description>&lt;!--!*#--&gt;Done, but again no change.&lt;BR /&gt;&lt;BR /&gt;During the install procedure, when I am told to make sure that the correct services/daemons/scripts (technical term?) are running with ps "-ef |grep pfs" it only shows 4 of the 5 processes are running, "root  2592  2579  2 15:31:30 pts/tb    0:00 grep pfs" is not listed. &lt;BR /&gt;&lt;BR /&gt;Could this have anything to do with the problem? I'm fairly new to the os.</description>
      <pubDate>Mon, 03 Jan 2011 16:49:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732669#M36598</guid>
      <dc:creator>Miles Denison</dc:creator>
      <dc:date>2011-01-03T16:49:38Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732670#M36599</link>
      <description>Normally the problem is always the wrong IP in the config files, but if you delete them, it cannot be the problem any longer.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Do you still get the same error message?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;There is also a "wrong" kernel parameter possible, but the system will tell you during the installation (max_thread_proc I think).</description>
      <pubDate>Mon, 03 Jan 2011 17:53:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732670#M36599</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2011-01-03T17:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732671#M36600</link>
      <description>&lt;!--!*#--&gt;I've doubled the thread size from it's default. I've deleted the config files (access and commIpAddr), and when reinstalled played with the default configuration, wildcard, and a localhost address. &lt;BR /&gt;&lt;BR /&gt;No luck yet. &lt;BR /&gt;&lt;BR /&gt;Thanks for the help.</description>
      <pubDate>Mon, 03 Jan 2011 21:52:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732671#M36600</guid>
      <dc:creator>Miles Denison</dc:creator>
      <dc:date>2011-01-03T21:52:48Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732672#M36601</link>
      <description>I've successfully done this in the past.  Did you make sure that the drives are visible on the server?  I beleive that Commandview SDM connects directly to the individual drives in a JBOD config.&lt;BR /&gt;&lt;BR /&gt;If you are pretty sure the problem is Commandview SDM, you might try sg3utils, if you can build it on your system (or find binaries).  I beleive there is a format utility in there that will also get the job done.&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Jan 2011 17:16:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732672#M36601</guid>
      <dc:creator>Bill Rothanburg</dc:creator>
      <dc:date>2011-01-05T17:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732673#M36602</link>
      <description>No idea why it still not works, do you have another server by chance? Maybe a windows host? Commandview is available for windows too.</description>
      <pubDate>Wed, 05 Jan 2011 17:32:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732673#M36602</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2011-01-05T17:32:27Z</dc:date>
    </item>
    <item>
      <title>Re: CommandviewSDM</title>
      <link>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732674#M36603</link>
      <description>&lt;!--!*#--&gt;I can successfully see every disk when I issue an ioscan, yes. &lt;BR /&gt;&lt;BR /&gt;I'll check out sg3utils - and If needbe I can purchase a win 2k3 supported hba and toss it in one of my dl380s (maybe my next step). &lt;BR /&gt;&lt;BR /&gt;Just out of curiosity, if indeed I preform a fimware reflash, would that then make the disk appear as a 512 sector size instead of the (rather unnecessary in my opinon) 520? and at that point could I use the pvcreate and lvm successfully? Just a thought I had. &lt;BR /&gt;&lt;BR /&gt;Thanks for the help,&lt;BR /&gt;Miles.</description>
      <pubDate>Wed, 05 Jan 2011 20:36:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/commandviewsdm/m-p/4732674#M36603</guid>
      <dc:creator>Miles Denison</dc:creator>
      <dc:date>2011-01-05T20:36:39Z</dc:date>
    </item>
  </channel>
</rss>

