<?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: TL_adapter question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070965#M140644</link>
    <description>No, its not normal. Ive never seen messages like this on rebooting all our HP servers with fibre/SAN disks. Contact your storage expert/storage supplier to investigate.&lt;BR /&gt;&lt;BR /&gt;Before you do that do ensure you have the latest Online Diagnostics installed as it may simply be a bug in the diags which is now fixed in a newer version.&lt;BR /&gt;</description>
    <pubDate>Mon, 15 Sep 2003 09:28:57 GMT</pubDate>
    <dc:creator>Stefan Farrelly</dc:creator>
    <dc:date>2003-09-15T09:28:57Z</dc:date>
    <item>
      <title>TL_adapter question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070964#M140643</link>
      <description>Hello,&lt;BR /&gt;after a reboot of the server I see this error in Syslog:&lt;BR /&gt;------ EMS Event Notification ------   Value: "SERIOUS (4)" for Resource:&lt;BR /&gt;"/adapters/events/TL_adapter/2_0_5_0_0"     (Threshold:  &amp;gt;= " 3")    Execute the following command to obtain ev&lt;BR /&gt;ent details:   /opt/resmon/bin/resdata -R 239534082 -r /adapters/events/TL_adapter/2_0_5_0_0 -n 239534081 -a&lt;BR /&gt;&lt;BR /&gt;I try to execute thi command, and i see:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; lbolt value: 1242 &lt;BR /&gt;&lt;BR /&gt;   The Fibre Channel Driver has gone into non-participating mode &lt;BR /&gt;   Frame Manager Status Register =  0xa0084480 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt;A cable or hardware problem exists. This can also be caused due &lt;BR /&gt;   to the Tachyon TL adapter changing its AL_PA across a LIP. &lt;BR /&gt;   Do the following: &lt;BR /&gt;   1. Verify that the fiber optic cable is functional and securely &lt;BR /&gt;      attached to the Fibre Channel Mass Storage Adapter. &lt;BR /&gt;   2. After checking the cabling, execute a loopback test using &lt;BR /&gt;      fcmsutil. &lt;BR /&gt;      Command syntax is as follows: &lt;BR /&gt;      /opt/fcms/bin/fcmsutil &lt;DEVICE_FILE&gt; lb plm &lt;BR /&gt;     If the problem persists after verifying fiber optic cabling, &lt;BR /&gt;     replace the adapter &lt;BR /&gt;&lt;BR /&gt;I verify the correct function of Fibre chanel, and now is all OK.&lt;BR /&gt;&lt;BR /&gt;Is normal that during reboot I see this error? &lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Filo&lt;/DEVICE_FILE&gt;</description>
      <pubDate>Mon, 15 Sep 2003 09:14:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070964#M140643</guid>
      <dc:creator>Filosofo</dc:creator>
      <dc:date>2003-09-15T09:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: TL_adapter question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070965#M140644</link>
      <description>No, its not normal. Ive never seen messages like this on rebooting all our HP servers with fibre/SAN disks. Contact your storage expert/storage supplier to investigate.&lt;BR /&gt;&lt;BR /&gt;Before you do that do ensure you have the latest Online Diagnostics installed as it may simply be a bug in the diags which is now fixed in a newer version.&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Sep 2003 09:28:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070965#M140644</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-09-15T09:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: TL_adapter question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070966#M140645</link>
      <description>No, You are not supposed to get this message.&lt;BR /&gt;&lt;BR /&gt;1. Install the latest version and patches of OnlineDiagnostics.&lt;BR /&gt;2. Try using monconfig, and set some requests for the device and check whether the device is fine or not. If monconfig reports some erroe, fix the same.&lt;BR /&gt;3. If monconfig, shows no error, reboot the same and check again whether you are getting the message. If u still get the message,  then contact fibre channel expert and check the device.</description>
      <pubDate>Mon, 15 Sep 2003 09:59:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070966#M140645</guid>
      <dc:creator>Bhuvaneswari Selvaraj</dc:creator>
      <dc:date>2003-09-15T09:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: TL_adapter question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070967#M140646</link>
      <description>Check with swlist -l product | grep -i fc that&lt;BR /&gt;you have all fc software/patches installed.&lt;BR /&gt;with fcmsutil /dev/tdX or /dev/fcmsX can get basic info on your card (patch,topology wwn etc),with fcmsutil "stat" option can get some more statistics.LIPs usualy happen when sone of the devices on arbitrated loop are reseting thus doing "logon" procedure to obtain port_id.&lt;BR /&gt;can be that on the other hand you have a device that doesn't have its AL-PA hard set?&lt;BR /&gt;Also check switchshow,porterrshow brocade switch commands to see a statistics for a specific port.&lt;BR /&gt;&lt;BR /&gt;Zeev</description>
      <pubDate>Mon, 15 Sep 2003 11:24:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tl-adapter-question/m-p/3070967#M140646</guid>
      <dc:creator>Zeev Schultz</dc:creator>
      <dc:date>2003-09-15T11:24:06Z</dc:date>
    </item>
  </channel>
</rss>

