<?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 XP512 Command Device in XP Storage</title>
    <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705675#M884</link>
    <description>Need W2K servers a command device to see other LUNs on a XP512?&lt;BR /&gt;We only see LUN's on W2k and W2003 servers when a XP512 Command Device is add to the LUN group.&lt;BR /&gt;Can anyone explane that.&lt;BR /&gt;&lt;BR /&gt;Regards, &lt;BR /&gt;Rene</description>
    <pubDate>Tue, 10 Jan 2006 04:28:50 GMT</pubDate>
    <dc:creator>Rene Sesink</dc:creator>
    <dc:date>2006-01-10T04:28:50Z</dc:date>
    <item>
      <title>XP512 Command Device</title>
      <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705675#M884</link>
      <description>Need W2K servers a command device to see other LUNs on a XP512?&lt;BR /&gt;We only see LUN's on W2k and W2003 servers when a XP512 Command Device is add to the LUN group.&lt;BR /&gt;Can anyone explane that.&lt;BR /&gt;&lt;BR /&gt;Regards, &lt;BR /&gt;Rene</description>
      <pubDate>Tue, 10 Jan 2006 04:28:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705675#M884</guid>
      <dc:creator>Rene Sesink</dc:creator>
      <dc:date>2006-01-10T04:28:50Z</dc:date>
    </item>
    <item>
      <title>Re: XP512 Command Device</title>
      <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705676#M885</link>
      <description>No, the commanddevice is only used for BC and CA purphoses.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Normaly when you map LUN's, you can group them as well as you can group WWN's. Finally you have to link them together (security).&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Jan 2006 05:14:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705676#M885</guid>
      <dc:creator>Fabian_Nowee</dc:creator>
      <dc:date>2006-01-10T05:14:52Z</dc:date>
    </item>
    <item>
      <title>Re: XP512 Command Device</title>
      <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705677#M886</link>
      <description>Fabian,&lt;BR /&gt;&lt;BR /&gt;Thanks for your fast responds.&lt;BR /&gt;When we add a LUN to a new W2k or W2k3 server,the new LUN is not seen after a rescan of new devices. We are using Emulex or Qlogic HBA together with SecurePath.&lt;BR /&gt;After adding the Command Device to the LUN group and do a rescan, all the LUN's are visible. This happend to all the windows servers. So all the W2k servers have a Command Device configured. Is this a normal behaviour? &lt;BR /&gt;&lt;BR /&gt;Rene</description>
      <pubDate>Tue, 10 Jan 2006 06:55:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705677#M886</guid>
      <dc:creator>Rene Sesink</dc:creator>
      <dc:date>2006-01-10T06:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: XP512 Command Device</title>
      <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705678#M887</link>
      <description>A Command LUN in XP / Hitachi Lingo (Yes XP Arrays are Hitachi Arrays) is carved, presented and allocated just like any other LUN. However - it does not have an emulation or since its purpose is for business copy or Hitachi tools. It is also most often used as a communications channel as an "in-band" thing for tools like Performance Advisor.&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Jan 2006 08:51:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705678#M887</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-01-10T08:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: XP512 Command Device</title>
      <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705679#M888</link>
      <description>Old driver? /firmware&lt;BR /&gt;&lt;BR /&gt;Lun 0 issue? nowaday's drivers create a pseudo lun to scan additional luns wich are not initialy starting at 0. Maybe the commanddevice (yes same as in HDS 9960) is providing the missing lun 0.</description>
      <pubDate>Tue, 10 Jan 2006 11:12:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705679#M888</guid>
      <dc:creator>Fabian_Nowee</dc:creator>
      <dc:date>2006-01-10T11:12:17Z</dc:date>
    </item>
    <item>
      <title>Re: XP512 Command Device</title>
      <link>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705680#M889</link>
      <description>Fabian,&lt;BR /&gt;&lt;BR /&gt;We running the latest drivers, so the LUN 0 issue must be more usefull.&lt;BR /&gt;The Command devices LUN number is 0, and that makes the whole story very clear to me.&lt;BR /&gt;Lun 0 makes other LUN's visible to the Wintel servers. It works as a pseudo LUN.&lt;BR /&gt;Thanks for your support.&lt;BR /&gt;&lt;BR /&gt;Rene</description>
      <pubDate>Wed, 11 Jan 2006 03:00:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/xp-storage/xp512-command-device/m-p/3705680#M889</guid>
      <dc:creator>Rene Sesink</dc:creator>
      <dc:date>2006-01-11T03:00:24Z</dc:date>
    </item>
  </channel>
</rss>

