<?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: Question on Syslog entry in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353603#M192902</link>
    <description>Thanks to all! Great info!&lt;BR /&gt;&lt;BR /&gt;Points awarded!&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bill&lt;BR /&gt;</description>
    <pubDate>Tue, 10 Aug 2004 13:54:24 GMT</pubDate>
    <dc:creator>Bill Anderson_2</dc:creator>
    <dc:date>2004-08-10T13:54:24Z</dc:date>
    <item>
      <title>Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353599#M192898</link>
      <description>Could anyone point me in the right direction or shed some light for this syslog entry?&lt;BR /&gt;&lt;BR /&gt;*************************************&lt;BR /&gt;&lt;BR /&gt;Aug  9 09:24:36 midas EMS [2194]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/0_7_0_0"     (Threshold:  &amp;gt;= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 143785989 -r /adapters/events/TL_adapter/0_7_0_0 -n 143785986 -a &lt;BR /&gt;&lt;BR /&gt;**************************************&lt;BR /&gt;TIA,&lt;BR /&gt;Bill&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Aug 2004 12:40:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353599#M192898</guid>
      <dc:creator>Bill Anderson_2</dc:creator>
      <dc:date>2004-08-10T12:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353600#M192899</link>
      <description>you have had diagnostic errors logged against what appears to be a Fibre Channel card&lt;BR /&gt;run the command it informs you to run and you will get more details&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Aug 2004 12:45:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353600#M192899</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2004-08-10T12:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353601#M192900</link>
      <description>This error message is from HP - EMS ( Hardware monitoring system )&lt;BR /&gt;--&lt;BR /&gt;$ swlist  -l "product" | grep -i ems&lt;BR /&gt;  EMS-Config            A.03.20        EMS Config&lt;BR /&gt;  EMS-Core              A.03.20        EMS Core Product&lt;BR /&gt;  EMS-KRMonitor         A.11.00.04     EMS Kernel Resource Monitor&lt;BR /&gt;--&lt;BR /&gt;&lt;BR /&gt;refer the below url for more details .&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/2512/B6191-90029.pdf" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/2512/B6191-90029.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/4316/ems_quick.pdf" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/4316/ems_quick.pdf&lt;/A&gt;</description>
      <pubDate>Tue, 10 Aug 2004 12:48:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353601#M192900</guid>
      <dc:creator>rvrameshbabu</dc:creator>
      <dc:date>2004-08-10T12:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353602#M192901</link>
      <description>Error message was generated by the EMS for the adapter installed at the hardware address 0/7/0/0.&lt;BR /&gt;&lt;BR /&gt;Severity is critical, so chances are that you have a serious hardware failure.&lt;BR /&gt;&lt;BR /&gt; # ioscan -fnH 0/7/0/0&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Aug 2004 12:54:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353602#M192901</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2004-08-10T12:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353603#M192902</link>
      <description>Thanks to all! Great info!&lt;BR /&gt;&lt;BR /&gt;Points awarded!&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bill&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Aug 2004 13:54:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353603#M192902</guid>
      <dc:creator>Bill Anderson_2</dc:creator>
      <dc:date>2004-08-10T13:54:24Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353604#M192903</link>
      <description>Bill,&lt;BR /&gt;&lt;BR /&gt;Is your environment by any chance a SAN that has an EVA on it? And running SecurePath software?&lt;BR /&gt;&lt;BR /&gt;If you do, then chances are the SecurePath instructions were not followed to the letter. You must disable EMS monitoring of your FC Paths in a SecurePath+EVA/StorageWorks  environment. Even with SecurePath 3.0D, this is still a requirement.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Aug 2004 13:57:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353604#M192903</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2004-08-10T13:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353605#M192904</link>
      <description>Nelson,&lt;BR /&gt;&lt;BR /&gt;After talking with the sysadmin, it appears that this was generated during configuration the new system which is mirroring the old system for conversion to the new system.&lt;BR /&gt;&lt;BR /&gt;Thanks for your info, I did pass it along.&lt;BR /&gt;&lt;BR /&gt;Bill&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Aug 2004 14:07:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353605#M192904</guid>
      <dc:creator>Bill Anderson_2</dc:creator>
      <dc:date>2004-08-10T14:07:58Z</dc:date>
    </item>
    <item>
      <title>Re: Question on Syslog entry</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353606#M192905</link>
      <description>I think you may very well have an EVA system and your SysAdmn is doing snapclones.. and I will advice him to make sure EMS is not active on the EVA FC. paths..</description>
      <pubDate>Tue, 10 Aug 2004 14:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/question-on-syslog-entry/m-p/3353606#M192905</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2004-08-10T14:10:53Z</dc:date>
    </item>
  </channel>
</rss>

