<?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: Wrong behaviour of APA init script in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-behaviour-of-apa-init-script/m-p/2711119#M587846</link>
    <description>Hello,&lt;BR /&gt;&lt;BR /&gt;This problem description is probably an "FAQ" for APA.&lt;BR /&gt;Q. Some of my network interfaces no longer appear in the output from lanscan after I installed APA/LM.  What happened?&lt;BR /&gt;&lt;BR /&gt;A.  Try lanscan -q.  You will probably see the missing devices on the same line as one of the  APA link aggregates (device instances 100-104 for 11.0 and 900-904 from 11.11).  APA automatically attempts to form link aggregations for all devices that are APA compatible.  The missing devices have been aggregated into trunks.&lt;BR /&gt;There are two solutions for this:&lt;BR /&gt;1) Configure APA.  At a minimum, configure all devices that are not going to be used in a linkagg as MANUAL.  Do this in the /etc/rc.config.d/hp_apaportconf file. Example:&lt;BR /&gt;HP_APAPORT_INTERFACE_NAME[0]=lan0&lt;BR /&gt;HP_APAPORT_GROUP_CAPABILITY[0]=&lt;BR /&gt;HP_APAPORT_CONFIG_MODE[0]=MANUAL   &lt;BR /&gt;Reboot the system.&lt;BR /&gt;&lt;BR /&gt;2) Install the patch PHNE_24308 (11.0) or PHNE_24309 (11.11) or the APA product from Application Release Dec 2001(when available), then follow the instructions in the patch documentation and or product release note. &lt;BR /&gt;&lt;BR /&gt;If you install the patch, you need to copy in new hp_apaconf file AND hp_apaportconf file from /usr/newconfig/etc/rc.config.d into /etc/rc.config.d&lt;BR /&gt;&lt;BR /&gt;Be sure that the variable HP_APA_DEFAULT_PORT_MODE=MANUAL is included in the /etc/rc.config.d/hp_apaconf file.  Then configure APA.&lt;BR /&gt;&lt;BR /&gt;Hope this helps you resolve this once and for all,&lt;BR /&gt;&lt;BR /&gt;-&amp;gt; Brian Hackley</description>
    <pubDate>Mon, 29 Apr 2002 14:31:32 GMT</pubDate>
    <dc:creator>Brian Hackley</dc:creator>
    <dc:date>2002-04-29T14:31:32Z</dc:date>
    <item>
      <title>Wrong behaviour of APA init script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-behaviour-of-apa-init-script/m-p/2711118#M587844</link>
      <description>After installation of patches and system reboot, the APA startup script doesn't work properly.&lt;BR /&gt;&lt;BR /&gt;It create two new LinkAggregation interfaces (two virtual lan devices) called lan101 and lan102 for two real lan interfaces (lan2 and lan4). But they are not configured anywhere.&lt;BR /&gt;&lt;BR /&gt;APA config files /etc/rc.config.d/hp_apaconf and /etc/rc.config.d/hp_apaportconf refer to just ONE Link Agreggate (lan1 + lan3 -&amp;gt; lan100 ) that is properly configured. No mention to lan2 nor lan4.&lt;BR /&gt;&lt;BR /&gt;This a real problem because APA hides lan2 and lan4. Then they cannot be configured according to /etc/rc.config.d/netconf file.&lt;BR /&gt;&lt;BR /&gt;My workaround is assigning lan2 and lan4 IPs to lan101 and lan102.&lt;BR /&gt;&lt;BR /&gt;Some time ago, I had other problems after applying APA patches. So I'll install no APA patch anymore.&lt;BR /&gt;&lt;BR /&gt;P.D: APA commands have no manual pages.</description>
      <pubDate>Thu, 25 Apr 2002 13:52:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-behaviour-of-apa-init-script/m-p/2711118#M587844</guid>
      <dc:creator>Jdamian</dc:creator>
      <dc:date>2002-04-25T13:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong behaviour of APA init script</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/wrong-behaviour-of-apa-init-script/m-p/2711119#M587846</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;This problem description is probably an "FAQ" for APA.&lt;BR /&gt;Q. Some of my network interfaces no longer appear in the output from lanscan after I installed APA/LM.  What happened?&lt;BR /&gt;&lt;BR /&gt;A.  Try lanscan -q.  You will probably see the missing devices on the same line as one of the  APA link aggregates (device instances 100-104 for 11.0 and 900-904 from 11.11).  APA automatically attempts to form link aggregations for all devices that are APA compatible.  The missing devices have been aggregated into trunks.&lt;BR /&gt;There are two solutions for this:&lt;BR /&gt;1) Configure APA.  At a minimum, configure all devices that are not going to be used in a linkagg as MANUAL.  Do this in the /etc/rc.config.d/hp_apaportconf file. Example:&lt;BR /&gt;HP_APAPORT_INTERFACE_NAME[0]=lan0&lt;BR /&gt;HP_APAPORT_GROUP_CAPABILITY[0]=&lt;BR /&gt;HP_APAPORT_CONFIG_MODE[0]=MANUAL   &lt;BR /&gt;Reboot the system.&lt;BR /&gt;&lt;BR /&gt;2) Install the patch PHNE_24308 (11.0) or PHNE_24309 (11.11) or the APA product from Application Release Dec 2001(when available), then follow the instructions in the patch documentation and or product release note. &lt;BR /&gt;&lt;BR /&gt;If you install the patch, you need to copy in new hp_apaconf file AND hp_apaportconf file from /usr/newconfig/etc/rc.config.d into /etc/rc.config.d&lt;BR /&gt;&lt;BR /&gt;Be sure that the variable HP_APA_DEFAULT_PORT_MODE=MANUAL is included in the /etc/rc.config.d/hp_apaconf file.  Then configure APA.&lt;BR /&gt;&lt;BR /&gt;Hope this helps you resolve this once and for all,&lt;BR /&gt;&lt;BR /&gt;-&amp;gt; Brian Hackley</description>
      <pubDate>Mon, 29 Apr 2002 14:31:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/wrong-behaviour-of-apa-init-script/m-p/2711119#M587846</guid>
      <dc:creator>Brian Hackley</dc:creator>
      <dc:date>2002-04-29T14:31:32Z</dc:date>
    </item>
  </channel>
</rss>

