<?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: syslog.log fields? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176515#M162118</link>
    <description>It means due to a number of possible causes your ethernet card came down and up.&lt;BR /&gt;&lt;BR /&gt;This kind of messaging can be triggered by power cycling the switch, disconnecting the cable or other physical issues.&lt;BR /&gt;&lt;BR /&gt;It should not be triggered by cycling the card software with the ifconfig command.&lt;BR /&gt;&lt;BR /&gt;You might want to enable EMS monitoring(available from SAM) on the network card. This will get you an email or log with more data on the event, should it repeat itself.&lt;BR /&gt;&lt;BR /&gt;Last time I saw something similar it was on a D320 and was triggered by a cisco switch that power cycled.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Wed, 28 Jan 2004 11:37:09 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2004-01-28T11:37:09Z</dc:date>
    <item>
      <title>syslog.log fields?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176513#M162116</link>
      <description>Here is an exampe out of our syslog.log:&lt;BR /&gt;&lt;BR /&gt;Jan 26 17:21:30 5X:"NODE" 2287: Jan 26 17:24:13.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/21, changed state to up.&lt;BR /&gt;&lt;BR /&gt;After the date time and time there is a '5X'. Does any one know what this means and the configuration that controls this? This is causing some problems with templates and I am not sure how they started showing up. It seems to be some kind of priority and appears to match with the Cisco priority. Any ideas would be greatly appreaciated!</description>
      <pubDate>Wed, 28 Jan 2004 11:04:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176513#M162116</guid>
      <dc:creator>bdm900</dc:creator>
      <dc:date>2004-01-28T11:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log fields?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176514#M162117</link>
      <description>These are the facility and severity codes for the error message.&lt;BR /&gt;&lt;BR /&gt;These have been enabled by someone starting the syslogd process with the -v parameter set.&lt;BR /&gt;&lt;BR /&gt;5X translates as facility type "local7", severity "notice"&lt;BR /&gt;&lt;BR /&gt;The full details of facility and severity codes can be seen on the syslog man page&lt;BR /&gt;&lt;BR /&gt;man 3c syslog &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Jan 2004 11:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176514#M162117</guid>
      <dc:creator>Chris Wilshaw</dc:creator>
      <dc:date>2004-01-28T11:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log fields?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176515#M162118</link>
      <description>It means due to a number of possible causes your ethernet card came down and up.&lt;BR /&gt;&lt;BR /&gt;This kind of messaging can be triggered by power cycling the switch, disconnecting the cable or other physical issues.&lt;BR /&gt;&lt;BR /&gt;It should not be triggered by cycling the card software with the ifconfig command.&lt;BR /&gt;&lt;BR /&gt;You might want to enable EMS monitoring(available from SAM) on the network card. This will get you an email or log with more data on the event, should it repeat itself.&lt;BR /&gt;&lt;BR /&gt;Last time I saw something similar it was on a D320 and was triggered by a cisco switch that power cycled.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 28 Jan 2004 11:37:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176515#M162118</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-01-28T11:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: syslog.log fields?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176516#M162119</link>
      <description>That did it. I removed the -v and restarted the syslogd and it is logging now with out the priority. Thanks!</description>
      <pubDate>Wed, 28 Jan 2004 12:23:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/syslog-log-fields/m-p/3176516#M162119</guid>
      <dc:creator>bdm900</dc:creator>
      <dc:date>2004-01-28T12:23:32Z</dc:date>
    </item>
  </channel>
</rss>

