<?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 problems in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161596#M569922</link>
    <description>1) run lanscan to find the nmid or ppa number of your lancard&lt;BR /&gt;2) run lanadmin to find the current settings of you lancard: lanadmin -x &lt;PPA&gt;&lt;BR /&gt;&lt;BR /&gt;Now, if your lancard is configured with autonegotiate, start by setting the lancard to a fixed speed, because there are lots of problems with autonegotiate.&lt;BR /&gt;&lt;BR /&gt;Also check the load on your network card. Use netstat -i to view number of packets (in/out) and especially errors. Those problems might be the result of the wrong settings (HD instead of FD, for instance).&lt;/PPA&gt;</description>
    <pubDate>Mon, 12 Jan 2004 05:59:11 GMT</pubDate>
    <dc:creator>Elmar P. Kolkman</dc:creator>
    <dc:date>2004-01-12T05:59:11Z</dc:date>
    <item>
      <title>Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161594#M569920</link>
      <description>Hello ITRC people,&lt;BR /&gt;I have a problem about a 10/100Baset-T lan card. On console get a lot of messages as&lt;BR /&gt;&lt;BR /&gt;"&amp;lt;6014&amp;gt; HPPB 10/100BASE-T adapter in slot 2 failed with Lo-Quix DMA Timeout"&lt;BR /&gt;&lt;BR /&gt;I already searched out ITRC forums but the only one result of my research doesn't give a solution and I would like to get more responses.&lt;BR /&gt;&lt;BR /&gt;Helps and suggestions would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Gianni</description>
      <pubDate>Mon, 12 Jan 2004 05:49:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161594#M569920</guid>
      <dc:creator>Pippo_9</dc:creator>
      <dc:date>2004-01-12T05:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161595#M569921</link>
      <description>Check with lanadmin the state of the interface.</description>
      <pubDate>Mon, 12 Jan 2004 05:52:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161595#M569921</guid>
      <dc:creator>Hoefnix</dc:creator>
      <dc:date>2004-01-12T05:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161596#M569922</link>
      <description>1) run lanscan to find the nmid or ppa number of your lancard&lt;BR /&gt;2) run lanadmin to find the current settings of you lancard: lanadmin -x &lt;PPA&gt;&lt;BR /&gt;&lt;BR /&gt;Now, if your lancard is configured with autonegotiate, start by setting the lancard to a fixed speed, because there are lots of problems with autonegotiate.&lt;BR /&gt;&lt;BR /&gt;Also check the load on your network card. Use netstat -i to view number of packets (in/out) and especially errors. Those problems might be the result of the wrong settings (HD instead of FD, for instance).&lt;/PPA&gt;</description>
      <pubDate>Mon, 12 Jan 2004 05:59:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161596#M569922</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-01-12T05:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161597#M569923</link>
      <description>You can check the i/f status using lanadmin.&lt;BR /&gt;&lt;BR /&gt;Check the logfile using the following command;&lt;BR /&gt;&lt;BR /&gt;#netfmt -Nvf /var/adm/nettl.LOG000&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Jan 2004 07:24:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161597#M569923</guid>
      <dc:creator>PVR</dc:creator>
      <dc:date>2004-01-12T07:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161598#M569924</link>
      <description>Would you be running 10.20 by any chance? &lt;BR /&gt;&lt;BR /&gt; PHNE_19216 s700_800 10.20 2.23 ACC Base Software (EISA) Patch corrects this problem:&lt;BR /&gt;&lt;BR /&gt;"DTS TPO0h02486&lt;BR /&gt; This problem was caused by an interrupt collision between&lt;BR /&gt; the NIO Lo-Quix chip on the ACC card and the HP-UX host.&lt;BR /&gt; That is, the card sent up an external interrupt at the exact&lt;BR /&gt; same time the host told the card to turn-off interrupts and&lt;BR /&gt; to start a DMA operation.  This resulted in the Lo-Quix chip&lt;BR /&gt; being unable to complete the DMA request which eventually&lt;BR /&gt; times out.  The nacc1 and nacc0 drivers was modified to&lt;BR /&gt; detect this condition and to sequence events to avoid the&lt;BR /&gt; problem.&lt;BR /&gt;"&lt;BR /&gt;Same fix seems to also be in PHNE_22519&lt;BR /&gt;Patch Description: s700_800 10.20 2.40.00-2.40.02 ACC Base Software Patch along with another DMA timeout.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If not 10.20 then go to:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/patch/search.do?BC=patch.breadcrumb.main" target="_blank"&gt;http://www2.itrc.hp.com/service/patch/search.do?BC=patch.breadcrumb.main&lt;/A&gt;|&amp;amp;pageContextName=hpux:::&lt;BR /&gt;&lt;BR /&gt;seach for Lo-Quix (you can download the patches from there too.)&lt;BR /&gt;&lt;BR /&gt;Ron&lt;BR /&gt;</description>
      <pubDate>Mon, 12 Jan 2004 07:58:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161598#M569924</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2004-01-12T07:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161599#M569925</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;It is detecting in ioscan out &lt;BR /&gt;&lt;BR /&gt;if it is not then pls check the hardware status of the lan card whether it is working or not&lt;BR /&gt;&lt;BR /&gt;it is showing in the ioscan check the driver status&lt;BR /&gt;&lt;BR /&gt;then try the lanscan, lanadmin command&lt;BR /&gt;&lt;BR /&gt;Thanx</description>
      <pubDate>Tue, 13 Jan 2004 02:15:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161599#M569925</guid>
      <dc:creator>Suresh Patoria</dc:creator>
      <dc:date>2004-01-13T02:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: Lan card problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161600#M569926</link>
      <description>HP-UX 11.00&lt;BR /&gt;Guys, I am working on a warning of patch PHNE_18546 (the 8.9.3 sendmail patch):&lt;BR /&gt;&lt;BR /&gt;2001/07/17 - This Critical Warning has been issued by HP.&lt;BR /&gt;- PHNE_18546 introduced a design change to identd(1M), an&lt;BR /&gt;  identification mechanism used by sendmail, that exposes&lt;BR /&gt;  behavior which can result in severe performance problems on&lt;BR /&gt;  any system or a TOC on an MC/ServiceGuard cluster node.  This&lt;BR /&gt;  behavior may be experienced on systems that have identd(1M)&lt;BR /&gt;  enabled and also have a large number of concurrent TCP&lt;BR /&gt;  connections.&lt;BR /&gt;- This behavior has been exhibited on systems that have more&lt;BR /&gt;  than than 3000 concurrent TCP connections.  To determine&lt;BR /&gt;  the number of TCP connections on a system, the following&lt;BR /&gt;  command string can be used:&lt;BR /&gt;    /usr/bin/netstat -a | grep -ic tcp&lt;BR /&gt;- The identd(1M) server implements an advisory identification&lt;BR /&gt;  mechanism that can be used by sendmail and is enabled by&lt;BR /&gt;  default.  The identd(1M) provided in PHNE_18546 makes use of&lt;BR /&gt;  the ndd(1M) command which results in the undesirable&lt;BR /&gt;  behavior.&lt;BR /&gt;- To avoid this behavior, HP recommends disabling identd(1M) on&lt;BR /&gt;  all systems that have PHNE_18546 installed.  Disabling&lt;BR /&gt;  identd(1M) will not negatively impact the delivery of mail.&lt;BR /&gt;  To disable identd(1M), perform the following steps as root:&lt;BR /&gt;    1. Edit the /etc/inetd.conf file and comment out the&lt;BR /&gt;       ident line by placing a '#' in the first column:&lt;BR /&gt;         #ident  stream tcp wait  bin  /usr/lbin/identd  identd&lt;BR /&gt;    2. Force inetd(1M) to re-read the inetd.conf file by&lt;BR /&gt;       executing:&lt;BR /&gt;  /usr/sbin/inetd -c&lt;BR /&gt;- In addition, to avoid this generating ident requests HP&lt;BR /&gt;  recommends disabling ident lookups in the sendmail&lt;BR /&gt;  configuration file on all systems that have PHNE_18546&lt;BR /&gt;  installed.  To disable this feature, perform the following&lt;BR /&gt;  steps as root:&lt;BR /&gt;    1. Edit the /etc/mail/sendmail.cf file as root and change&lt;BR /&gt;       the line:&lt;BR /&gt;         #O Timeout.ident=30s&lt;BR /&gt;       to:&lt;BR /&gt;         O Timeout.ident=0s&lt;BR /&gt;    2. Stop sendmail by executing:&lt;BR /&gt;  /usr/sbin/killsm&lt;BR /&gt;    3. Restart sendmail by executing:&lt;BR /&gt;         /sbin/init.d/sendmail start&lt;BR /&gt;  Please note that leaving the line commented out does not&lt;BR /&gt;  disable ident lookups.  The line must be uncommented and the&lt;BR /&gt;  timeout value explicitly set to "Os" in order to stop&lt;BR /&gt;  sendmail from making ident connections to the remote client.&lt;BR /&gt;- Since the undesirable behavior is easily avoided by disabling&lt;BR /&gt;  the identd(1M) functionality, HP recommends that the feature&lt;BR /&gt;  be disabled instead of removing PHNE_18546 from the systems&lt;BR /&gt;  on which it is installed.&lt;BR /&gt;- A new patch will be released as soon as possible to resolve&lt;BR /&gt;  this issue.&lt;BR /&gt;- PHNE_18546 was included in the following Support Plus Patch&lt;BR /&gt;  Bundles:&lt;BR /&gt; Sep 2000: XSWGR1100 B.11.00.50.5&lt;BR /&gt; Dec 2000: XSWGR1100 B.11.00.51.2&lt;BR /&gt; Mar 2001: XSWGR1100 B.11.00.52.2&lt;BR /&gt; Jun 2001: XSWGR1100 B.11.00.53.2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If I get more info (I hope the solution !!!) then I will post again on forum...meanwhile thanks for your hints!&lt;BR /&gt;&lt;BR /&gt;Gianni.</description>
      <pubDate>Tue, 13 Jan 2004 04:56:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-card-problems/m-p/3161600#M569926</guid>
      <dc:creator>Pippo_9</dc:creator>
      <dc:date>2004-01-13T04:56:36Z</dc:date>
    </item>
  </channel>
</rss>

