<?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 Alternate disk link failure in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487747#M1087</link>
    <description>We have a n-class box connected to a Emc array via fibre cards. I am getting alternate disk link failures on multiple disks. I am new to this particular environment so this question will probably be pretty simple. I need to know how I can check that my path from my server to my EMC box is good. I have heard of the 'inq' function  of EMC but need more info on it.</description>
    <pubDate>Mon, 29 Jan 2001 23:33:05 GMT</pubDate>
    <dc:creator>Carlos_8</dc:creator>
    <dc:date>2001-01-29T23:33:05Z</dc:date>
    <item>
      <title>Alternate disk link failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487747#M1087</link>
      <description>We have a n-class box connected to a Emc array via fibre cards. I am getting alternate disk link failures on multiple disks. I am new to this particular environment so this question will probably be pretty simple. I need to know how I can check that my path from my server to my EMC box is good. I have heard of the 'inq' function  of EMC but need more info on it.</description>
      <pubDate>Mon, 29 Jan 2001 23:33:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487747#M1087</guid>
      <dc:creator>Carlos_8</dc:creator>
      <dc:date>2001-01-29T23:33:05Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate disk link failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487748#M1088</link>
      <description>You can check if the link is up with the following command."fcmsutil "devicefile""The device file is normally "/dev/fcms "or "/dev/td "follow by a number with the option "stat" you can see the Register alos Error register of the interface.&lt;BR /&gt;The manpage of the command held some additonal infos.</description>
      <pubDate>Tue, 30 Jan 2001 06:28:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487748#M1088</guid>
      <dc:creator>Frank Skibbe</dc:creator>
      <dc:date>2001-01-30T06:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate disk link failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487749#M1089</link>
      <description>Thanks Frank,&lt;BR /&gt;&lt;BR /&gt;We actually found then problem to be a " sorry " by one of our other buildings. They made some config changes and forgot to disable the links. I will keep the info you gave me because it would help narrow the problem faster in the future. Thanks again!!!!</description>
      <pubDate>Tue, 30 Jan 2001 21:09:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/alternate-disk-link-failure/m-p/2487749#M1089</guid>
      <dc:creator>Carlos_8</dc:creator>
      <dc:date>2001-01-30T21:09:03Z</dc:date>
    </item>
  </channel>
</rss>

