<?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: network card driver problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421377#M598293</link>
    <description>In /etc/rc.config/netconf where the interfaces are configured you should have the option of including the following parameter for each interface that is defined:&lt;BR /&gt;&lt;BR /&gt;INTERFACE_STATE: Desired interface state at boot time. Either up or down, default is up.&lt;BR /&gt;&lt;BR /&gt;This means that if the index number of 2 refers to a card that you wish to be configured but remain "down", then then entry in netconf should look like:&lt;BR /&gt;&lt;BR /&gt;INTERFACE_STATE[2]="down"&lt;BR /&gt;&lt;BR /&gt;If this parameter is omitted or set to "" then the default value of "up" is assigned.</description>
    <pubDate>Fri, 12 May 2000 13:47:11 GMT</pubDate>
    <dc:creator>Jason Luginbuhl</dc:creator>
    <dc:date>2000-05-12T13:47:11Z</dc:date>
    <item>
      <title>network card driver problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421375#M598291</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am running HP-UX 10.20 on two hosts that back up each other.&lt;BR /&gt;&lt;BR /&gt;When one has its lan interfaces up, the other one has its lan interfaces down, &lt;BR /&gt;and viceversa. Both with the same (set of) IP addresses.&lt;BR /&gt;&lt;BR /&gt;So far so good, there is no conflict because only one interface with the same &lt;BR /&gt;IP address is up at a given time, right? ... well, not quite.&lt;BR /&gt;&lt;BR /&gt;It occasionally happens that the driver btlan4 is monitoring the interface that &lt;BR /&gt;is down, and in a number of cases (i.e. the cable gets disconnected momentarily &lt;BR /&gt;or the device at the other end of the cable goes down) then btlan4 will &lt;BR /&gt;interpret that something may be wrong with the card itself, prints a message, &lt;BR /&gt;boots the card, and bingo, it comes UP instead of DOWN. Now we have two &lt;BR /&gt;interfaces (itself and the counterpart interface on the other host) both up and &lt;BR /&gt;both with the same IP address !!. &lt;BR /&gt;&lt;BR /&gt;That creates havok on the network.&lt;BR /&gt;&lt;BR /&gt;Does anyone out there know how to tell btlan4 NOT to be so intelligent and NOT &lt;BR /&gt;to boot/monitor the interface card ?&lt;BR /&gt;&lt;BR /&gt;Failing that, does anyone know how to tell it to bring the interfaces &lt;BR /&gt;ifconfig'ed down by default?&lt;BR /&gt;&lt;BR /&gt;Any other ideas?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Ricardo.&lt;BR /&gt;-------</description>
      <pubDate>Wed, 12 Apr 2000 08:59:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421375#M598291</guid>
      <dc:creator>Ricardo Correa</dc:creator>
      <dc:date>2000-04-12T08:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: network card driver problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421376#M598292</link>
      <description>in 10.20, i don't believe there is a way to tell a 100bt lan card to come up as s/w state DOWN by default.  in 11.0, there is a variable in the /etc/rc.config.d/netconf file.&lt;BR /&gt;&lt;BR /&gt;one alternative is to create a startup script that does ifconfig's it DOWN.&lt;BR /&gt;&lt;BR /&gt;one idea for two systems that use the same ip address is to cluster them together in MCServiceGuard.  however, that is something you will have to decide according to your particular scenario.&lt;BR /&gt;&lt;BR /&gt;Sincerely,&lt;BR /&gt;Rashmi Kadambi</description>
      <pubDate>Tue, 09 May 2000 21:32:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421376#M598292</guid>
      <dc:creator>alberto vasquez</dc:creator>
      <dc:date>2000-05-09T21:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: network card driver problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421377#M598293</link>
      <description>In /etc/rc.config/netconf where the interfaces are configured you should have the option of including the following parameter for each interface that is defined:&lt;BR /&gt;&lt;BR /&gt;INTERFACE_STATE: Desired interface state at boot time. Either up or down, default is up.&lt;BR /&gt;&lt;BR /&gt;This means that if the index number of 2 refers to a card that you wish to be configured but remain "down", then then entry in netconf should look like:&lt;BR /&gt;&lt;BR /&gt;INTERFACE_STATE[2]="down"&lt;BR /&gt;&lt;BR /&gt;If this parameter is omitted or set to "" then the default value of "up" is assigned.</description>
      <pubDate>Fri, 12 May 2000 13:47:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/network-card-driver-problem/m-p/2421377#M598293</guid>
      <dc:creator>Jason Luginbuhl</dc:creator>
      <dc:date>2000-05-12T13:47:11Z</dc:date>
    </item>
  </channel>
</rss>

