<?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: Fiber channel problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fiber-channel-problem/m-p/4051490#M304557</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Sounds like one of the following issues.&lt;BR /&gt;&lt;BR /&gt;1) A lip storm or other major problem on the Fiber network. Run the diagnostics recommended in the message to learn more. Post back here the good stuff.&lt;BR /&gt;&lt;BR /&gt;2) LUN0 is not assigned to this fiber channel card and its detecting the disk array as a disk. Only its not a disk and causes errors. See if you can assign a LUN0 to the card and perhaps the message will magically go away.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Wed, 08 Aug 2007 00:36:23 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2007-08-08T00:36:23Z</dc:date>
    <item>
      <title>Fiber channel problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fiber-channel-problem/m-p/4051489#M304556</link>
      <description>Could someone plz make me understand the output:&lt;BR /&gt;Aug  6 01:53:20 billing EMS [5029]: ------ EMS Event Notification ------   Value: "MAJORWARNING (3)" for Resource: "/adapters/&lt;BR /&gt;&lt;BR /&gt;events/TL_adapter/0_0_12_0_0"     (Threshold:  &amp;gt;= " 3")    Execute the following command to obtain event details:   /opt/resmo&lt;BR /&gt;&lt;BR /&gt;n/bin/resdata -R 329580551 -r /adapters/events/TL_adapter/0_0_12_0_0 -n 329580545 -a&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;CURRENT MONITOR DATA:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Event Time..........: Mon Aug  6 01:53:19 2007&lt;BR /&gt;&lt;BR /&gt;Severity............: MAJORWARNING&lt;BR /&gt;&lt;BR /&gt;Monitor.............: dm_TL_adapter&lt;BR /&gt;&lt;BR /&gt;Event #.............: 3&lt;BR /&gt;&lt;BR /&gt;System..............: billing&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Summary:&lt;BR /&gt;&lt;BR /&gt;     Adapter at hardware path 0/0/12/0/0 : Received an interrupt indicating and&lt;BR /&gt;&lt;BR /&gt;     Elastic Store Error Storm&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; lbolt value: 86524156&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;   The Fibre Channel Driver received an interrupt from the&lt;BR /&gt;&lt;BR /&gt;   adapter indicating an Elastic Store Error Storm&lt;BR /&gt;&lt;BR /&gt;   Frame Manager Status Register =  0x82000400&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;The Tachyon TL chip controlling Fibre Channel operation has experienced&lt;BR /&gt;&lt;BR /&gt;  an overflow or underflow in its inbound data queue.&lt;BR /&gt;&lt;BR /&gt;      The following may cause this error :&lt;BR /&gt;&lt;BR /&gt;      1. Cable fault&lt;BR /&gt;&lt;BR /&gt;      2. Hardware fault&lt;BR /&gt;&lt;BR /&gt;      3. Optical Unit Fault&lt;BR /&gt;&lt;BR /&gt;   The Tachyon TL chip will recover without intervention&lt;BR /&gt;&lt;BR /&gt;   Preventive Information :&lt;BR /&gt;&lt;BR /&gt;   Verify the fiber optic cable integrity as follows:&lt;BR /&gt;&lt;BR /&gt;   1. Verify that the fiber optic cable is functional and securely&lt;BR /&gt;&lt;BR /&gt;      attached to the Fibre Channel Mass Storage Adapter.&lt;BR /&gt;&lt;BR /&gt;   2. After checking the cabling, execute a loopback test on the&lt;BR /&gt;&lt;BR /&gt;      FCMS Adapter using fcmsutil.  Command syntax is as follows:&lt;BR /&gt;&lt;BR /&gt;      /opt/fcms/bin/fcmsutil &lt;DEVICE_FILE&gt; lb plm&lt;BR /&gt;&lt;BR /&gt;   If the problem persists, replace the adapter.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Additional Event Data:&lt;BR /&gt;&lt;BR /&gt;     System IP Address...: 10.10.20.20&lt;BR /&gt;&lt;BR /&gt;     Event Id............: 0x46b62ab000000000&lt;BR /&gt;&lt;BR /&gt;     Monitor Version.....: B.01.00&lt;BR /&gt;&lt;BR /&gt;     Event Class.........: I/O&lt;BR /&gt;&lt;BR /&gt;     Client Configuration File...........:&lt;BR /&gt;&lt;BR /&gt;     /var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg&lt;BR /&gt;&lt;BR /&gt;     Client Configuration File Version...: A.01.00&lt;BR /&gt;&lt;BR /&gt;          Qualification criteria met.&lt;BR /&gt;&lt;BR /&gt;               Number of events..: 1&lt;BR /&gt;&lt;BR /&gt;     Associated OS error log entry id(s):&lt;BR /&gt;&lt;BR /&gt;          0x46b62aaf00000000&lt;BR /&gt;&lt;BR /&gt;     Additional System Data:&lt;BR /&gt;&lt;BR /&gt;          System Model Number.............: 9000/800/S16K-A&lt;BR /&gt;&lt;BR /&gt;          OS Version......................: B.11.11&lt;BR /&gt;&lt;BR /&gt;          EMS Version.....................: A.04.00&lt;BR /&gt;&lt;BR /&gt;          STM Version.....................: A.45.00&lt;BR /&gt;&lt;BR /&gt;     Latest information on this event:&lt;BR /&gt;&lt;BR /&gt;          &lt;A href="http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#3" target="_blank"&gt;http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#3&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;v-v-v-v-v-v-v-v-v-v-v-v-v    D  E  T  A  I  L  S    v-v-v-v-v-v-v-v-v-v-v-v-v&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Component Data:&lt;BR /&gt;&lt;BR /&gt;    Physical Device Path....: 0/0/12/0/0&lt;BR /&gt;&lt;BR /&gt;    Vendor Id...............: 0x0000103C&lt;BR /&gt;&lt;BR /&gt;    Serial Number(WWN)......: 50060B0000119050&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;I/O Log Event Data:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;     Driver Status Code..................: 0x00000003&lt;BR /&gt;&lt;BR /&gt;     Length of Logged Hardware Status....: 0 bytes.&lt;BR /&gt;&lt;BR /&gt;     Offset to Logged Manager Information: 0 bytes.&lt;BR /&gt;&lt;BR /&gt;     Length of Logged Manager Information: 61 bytes.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Manager-Specific Information:&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Raw data from FCMS Adapter driver:&lt;BR /&gt;&lt;BR /&gt;00000004 052840FC 00000001 00000001 82000400 2F75782F 6B65726E 2F6B6973&lt;BR /&gt;&lt;BR /&gt;752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E 63&lt;BR /&gt;&lt;/DEVICE_FILE&gt;</description>
      <pubDate>Wed, 08 Aug 2007 00:24:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fiber-channel-problem/m-p/4051489#M304556</guid>
      <dc:creator>Farhan Sabbir Siddique</dc:creator>
      <dc:date>2007-08-08T00:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: Fiber channel problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fiber-channel-problem/m-p/4051490#M304557</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Sounds like one of the following issues.&lt;BR /&gt;&lt;BR /&gt;1) A lip storm or other major problem on the Fiber network. Run the diagnostics recommended in the message to learn more. Post back here the good stuff.&lt;BR /&gt;&lt;BR /&gt;2) LUN0 is not assigned to this fiber channel card and its detecting the disk array as a disk. Only its not a disk and causes errors. See if you can assign a LUN0 to the card and perhaps the message will magically go away.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 08 Aug 2007 00:36:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fiber-channel-problem/m-p/4051490#M304557</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-08T00:36:23Z</dc:date>
    </item>
  </channel>
</rss>

