<?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: lan card failure in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955868#M577657</link>
    <description>Please check the NetTL log to see what the failure pertained to.  Networking related subsystems (drivers, transport, etc.) log to the NetTL log.&lt;BR /&gt;&lt;BR /&gt;Here's how you do it:&lt;BR /&gt;&lt;BR /&gt;1. cd /var/adm&lt;BR /&gt;2. Look for the files whose names start with nettl.LOG.&lt;BR /&gt;3. Pick the most recent one.&lt;BR /&gt;4. Run netfmt as follows:&lt;BR /&gt;&lt;BR /&gt;netfmt -t 20 -f nettl.LOGxx&lt;BR /&gt;&lt;BR /&gt;where nettl.LOGxx is the file you picked in step 3.&lt;BR /&gt;&lt;BR /&gt;-t 20 refers to the 20 most recent records logged.  You can change this number to get a varying number of log entries.&lt;BR /&gt;&lt;BR /&gt;Check the netfmt(1M) man page for more information.&lt;BR /&gt;&lt;BR /&gt;Let us know if you see anything unusual.  If you do, please attach the relevant NetTL log entries.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Ajit&lt;BR /&gt;HP Gigabit Ethernet&lt;BR /&gt;</description>
    <pubDate>Wed, 23 Apr 2003 05:04:11 GMT</pubDate>
    <dc:creator>Ajit Natarajan</dc:creator>
    <dc:date>2003-04-23T05:04:11Z</dc:date>
    <item>
      <title>lan card failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955864#M577653</link>
      <description>System running HPUX 10.20&lt;BR /&gt;Error with Lan card&lt;BR /&gt;&lt;BR /&gt;In syslog.log file found following error:&lt;BR /&gt;&lt;BR /&gt; btlan0 failed&lt;BR /&gt;&lt;BR /&gt;Ten seconds later received&lt;BR /&gt; btlan0 recovered&lt;BR /&gt;Is this a driver failure or card failure?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 21 Apr 2003 19:27:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955864#M577653</guid>
      <dc:creator>james gould</dc:creator>
      <dc:date>2003-04-21T19:27:54Z</dc:date>
    </item>
    <item>
      <title>Re: lan card failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955865#M577654</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Probably neither.  I usually see this when there is a cable problem or a problem at the switch.  You'll see those error messages when you lose connection for a bit and then it comes back.&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Mon, 21 Apr 2003 19:35:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955865#M577654</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-04-21T19:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: lan card failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955866#M577655</link>
      <description>In almost everycase, this is a cable problem, possibly a hub lost power briefly, or a switch port was reset.&lt;BR /&gt;&lt;BR /&gt;Failures like this are expected/anticiptaed in the TCP/IP protocol world and normally recovery is automatic. If these are rare events, it's safe to ignore them. &lt;BR /&gt;&lt;BR /&gt;One very common source of this kind of problem is cable length - you might be near (or above) the 100m mark.&lt;BR /&gt;</description>
      <pubDate>Mon, 21 Apr 2003 19:41:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955866#M577655</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-04-21T19:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: lan card failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955867#M577656</link>
      <description>It is probably a cable fault (don't forget the connector on the NIC - I've seen them get flaky too) but it wouldn't hurt to go into lanadmin (lanadmin, lan, display) and check for errors (mostly on the second page of the display).  Move a big file to another machine and then back again and recheck to see if the errors are climbing rapidly.  (You may also notice a major difference in the time it takes the file to go one way vs the other.  This is definitely a duplex mismatch issue if you notice a big time difference.)  Could be that you have a duplex mismatch and the switch is resetting the port because the error rate is too high.  While in lanadmin check to see if the duplex is set to full, half or auto. Then have your network guy check the switch.  Best is for both to be at 100 FULL if both ends support it.  Auto/Auto sometimes works but must people don't trust it.  FULL/Auto or Auto/FULL will definitely give you a mismatch since Auto will only negotiate if the other end is also set to Auto.  If not it goes on strike and set the link to Half.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Mon, 21 Apr 2003 20:53:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955867#M577656</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-04-21T20:53:36Z</dc:date>
    </item>
    <item>
      <title>Re: lan card failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955868#M577657</link>
      <description>Please check the NetTL log to see what the failure pertained to.  Networking related subsystems (drivers, transport, etc.) log to the NetTL log.&lt;BR /&gt;&lt;BR /&gt;Here's how you do it:&lt;BR /&gt;&lt;BR /&gt;1. cd /var/adm&lt;BR /&gt;2. Look for the files whose names start with nettl.LOG.&lt;BR /&gt;3. Pick the most recent one.&lt;BR /&gt;4. Run netfmt as follows:&lt;BR /&gt;&lt;BR /&gt;netfmt -t 20 -f nettl.LOGxx&lt;BR /&gt;&lt;BR /&gt;where nettl.LOGxx is the file you picked in step 3.&lt;BR /&gt;&lt;BR /&gt;-t 20 refers to the 20 most recent records logged.  You can change this number to get a varying number of log entries.&lt;BR /&gt;&lt;BR /&gt;Check the netfmt(1M) man page for more information.&lt;BR /&gt;&lt;BR /&gt;Let us know if you see anything unusual.  If you do, please attach the relevant NetTL log entries.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Ajit&lt;BR /&gt;HP Gigabit Ethernet&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Apr 2003 05:04:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-failure/m-p/2955868#M577657</guid>
      <dc:creator>Ajit Natarajan</dc:creator>
      <dc:date>2003-04-23T05:04:11Z</dc:date>
    </item>
  </channel>
</rss>

