<?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 fcmsutil question, CRC errors from switch in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/fcmsutil-question-crc-errors-from-switch/m-p/3604301#M13991</link>
    <description>Had an odd situation where a Tachyon XL2's fiber connects were loose, the system (rp8400) had it's SAN mounts no problem, but our SAN group eventually discovered excessive "CRC errors" coming from the box, and the errors were negatively impacting the fabric. Sure enough, when the fiber connections were pushed in tighter, the SAN errors disappeared. &lt;BR /&gt;&lt;BR /&gt;Question is, how can we see this from the OS side? Doing an fcmsutil /dev/td1 stat -s showed more than usual "Bad Char" but there was 0 for "Bad CRC." What in the output is worthy of paying attention to?&lt;BR /&gt;&lt;BR /&gt;fcmsutil /dev/td1 stat -s  &lt;BR /&gt;&lt;BR /&gt;Statistics From Link Status Registers ...&lt;BR /&gt;Bad Char                     3060&lt;BR /&gt;Bad CRC                            0     &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 15 Aug 2005 20:42:04 GMT</pubDate>
    <dc:creator>C W_1</dc:creator>
    <dc:date>2005-08-15T20:42:04Z</dc:date>
    <item>
      <title>fcmsutil question, CRC errors from switch</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/fcmsutil-question-crc-errors-from-switch/m-p/3604301#M13991</link>
      <description>Had an odd situation where a Tachyon XL2's fiber connects were loose, the system (rp8400) had it's SAN mounts no problem, but our SAN group eventually discovered excessive "CRC errors" coming from the box, and the errors were negatively impacting the fabric. Sure enough, when the fiber connections were pushed in tighter, the SAN errors disappeared. &lt;BR /&gt;&lt;BR /&gt;Question is, how can we see this from the OS side? Doing an fcmsutil /dev/td1 stat -s showed more than usual "Bad Char" but there was 0 for "Bad CRC." What in the output is worthy of paying attention to?&lt;BR /&gt;&lt;BR /&gt;fcmsutil /dev/td1 stat -s  &lt;BR /&gt;&lt;BR /&gt;Statistics From Link Status Registers ...&lt;BR /&gt;Bad Char                     3060&lt;BR /&gt;Bad CRC                            0     &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Aug 2005 20:42:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/fcmsutil-question-crc-errors-from-switch/m-p/3604301#M13991</guid>
      <dc:creator>C W_1</dc:creator>
      <dc:date>2005-08-15T20:42:04Z</dc:date>
    </item>
    <item>
      <title>Re: fcmsutil question, CRC errors from switch</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/fcmsutil-question-crc-errors-from-switch/m-p/3604302#M13992</link>
      <description>These values all only represent the receiver channel :)&lt;BR /&gt;&lt;BR /&gt;there's no way the box can see what arrives at the switch, but You might be able to find resulting re-logins and such errors in the lower part of the fcms stat output (when used without -s).&lt;BR /&gt;otherwise - gbic's can go bad, and sometimes someone steps on the cables, and sometimes they're just a bit loose :))</description>
      <pubDate>Tue, 16 Aug 2005 09:29:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/fcmsutil-question-crc-errors-from-switch/m-p/3604302#M13992</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-08-16T09:29:19Z</dc:date>
    </item>
  </channel>
</rss>

