<?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: EMS Event Notification  &amp;quot;CRITICAL (5)&amp;quot; in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544222#M652289</link>
    <description>Is there any disk with name c102t4d1 ??&lt;BR /&gt;If yes, whats is the status ?</description>
    <pubDate>Fri, 04 Dec 2009 06:14:49 GMT</pubDate>
    <dc:creator>R.K. #</dc:creator>
    <dc:date>2009-12-04T06:14:49Z</dc:date>
    <item>
      <title>EMS Event Notification  "CRITICAL (5)"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544220#M652287</link>
      <description>I am getting the EMS notification in the syslog.log as a crital .. pls find the attached txt of the logs and errors.&lt;BR /&gt;&lt;BR /&gt;I checked the hardware path and device status as per the EMS notification  the status of the device is &lt;BR /&gt;ext_bus 117  0/12/0/0.102.122.255.1      fcpdev   CLAIMED     INTERFACE    FCP Device Interface&lt;BR /&gt;target   67  0/12/0/0.102.122.255.1.3    tgt      CLAIMED     DEVICE&lt;BR /&gt;ctl      15  0/12/0/0.102.122.255.1.3.0  sctl     CLAIMED     DEVICE       IBM     2145&lt;BR /&gt;                            /dev/rscsi/c117t3d0&lt;BR /&gt;fcp       4  0/12/0/0.108    fcp      NO_HW       INTERFACE    FCP Domain&lt;BR /&gt;fcp       8  0/12/0/0.125    fcp      CLAIMED     INTERFACE    FCP Domain&lt;BR /&gt;&lt;BR /&gt;Pls help me out to fix this..</description>
      <pubDate>Fri, 04 Dec 2009 06:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544220#M652287</guid>
      <dc:creator>gany59</dc:creator>
      <dc:date>2009-12-04T06:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: EMS Event Notification  "CRITICAL (5)"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544221#M652288</link>
      <description>Hi..&lt;BR /&gt;&lt;BR /&gt;lbolt error signify hardware error.&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Dec 2009 06:13:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544221#M652288</guid>
      <dc:creator>R.K. #</dc:creator>
      <dc:date>2009-12-04T06:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: EMS Event Notification  "CRITICAL (5)"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544222#M652289</link>
      <description>Is there any disk with name c102t4d1 ??&lt;BR /&gt;If yes, whats is the status ?</description>
      <pubDate>Fri, 04 Dec 2009 06:14:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544222#M652289</guid>
      <dc:creator>R.K. #</dc:creator>
      <dc:date>2009-12-04T06:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: EMS Event Notification  "CRITICAL (5)"</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544223#M652290</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Summary:&lt;BR /&gt;     Adapter at hardware path 0/12/0/0 : Unable to open previously opened&lt;BR /&gt;     target&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; lbolt value: 2066411522&lt;BR /&gt;&lt;BR /&gt;   Unable to access previously accessed target&lt;BR /&gt;   nport ID  =  0x660b13&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt;An attempt to re-open a device which had been opened earlier&lt;BR /&gt;  has failed.&lt;BR /&gt;      There should be additional logging messages which will&lt;BR /&gt;      allow diagnosis of the problem.&lt;BR /&gt;&lt;BR /&gt;This is an HBA (* host bus adaptor *) at hardware address 0/12/0/0 and nport 0x660b13.&lt;BR /&gt;&lt;BR /&gt;Run&lt;BR /&gt;&lt;BR /&gt;ioscan -H 0/12/0/0 to get the device, ie, /dev/fc##.&lt;BR /&gt;&lt;BR /&gt;Run&lt;BR /&gt;&lt;BR /&gt;fcmsutil /dev/fc## to get the state.&lt;BR /&gt;&lt;BR /&gt;Run&lt;BR /&gt;&lt;BR /&gt;cstm&amp;lt;&amp;lt;-EOF&lt;BR /&gt;runutil logtool&lt;BR /&gt;rs&lt;BR /&gt;EOF&lt;BR /&gt;&lt;BR /&gt;To see how many errors are being recorded and paste in the report including the start end end times.&lt;BR /&gt;&lt;BR /&gt;LBOLTS can usually be ignored unless the number of errors is really high.  The logtool report will tell you this.&lt;BR /&gt;&lt;BR /&gt;See what is attached to this device, ie, tape drive or disk array.  IF tape drive then this is typical.</description>
      <pubDate>Fri, 04 Dec 2009 08:01:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ems-event-notification-quot-critical-5-quot/m-p/4544223#M652290</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2009-12-04T08:01:14Z</dc:date>
    </item>
  </channel>
</rss>

