<?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: DL_ATTACH_REQ fails on a &amp;quot;virtual&amp;quot; PPA in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510614#M563052</link>
    <description>OK, I can see what you meand by being indecipherable.  Those numbers are no where near where one would expect them to be.&lt;BR /&gt;&lt;BR /&gt;It has been a long time since I've done DLPI stuff so be kind :) - you are certain of the structure definition, and that it is indeed a DL_ERROR_ACK that comes-back and not something else?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 29 Mar 2005 13:45:44 GMT</pubDate>
    <dc:creator>rick jones</dc:creator>
    <dc:date>2005-03-29T13:45:44Z</dc:date>
    <item>
      <title>DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510608#M563046</link>
      <description>Hello colleagues,&lt;BR /&gt;I've installed HP APA on a machine;&lt;BR /&gt;then I run a proprietary stack which issues a DL_ATTACH_REQ on the nmid related to the link aggregated generated by the HP APA; the command fails and the return message isn't understandable....&lt;BR /&gt;&lt;BR /&gt;Of course the stack properly runs on any other LAN card (btlan driver) since many many years!!&lt;BR /&gt;&lt;BR /&gt;What can I do?&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Enrico</description>
      <pubDate>Wed, 23 Mar 2005 12:39:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510608#M563046</guid>
      <dc:creator>Enrico Venturi</dc:creator>
      <dc:date>2005-03-23T12:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510609#M563047</link>
      <description>Hi, Enrico,&lt;BR /&gt;&lt;BR /&gt;What is the OS version and APA version?&lt;BR /&gt;(Run "what /usr/conf/lib/libhp_apa.a").&lt;BR /&gt;The DL_ATTACH_REQ should use PPA number instead of nmid. The PPA number of link aggregation should be 900-949 if your OS is 11i. (It is 100-149 for 11.0).&lt;BR /&gt;Can you please post the error messages and the code related to DL_ATTACH_REQ?&lt;BR /&gt;Can you use "ifconfig" to configure an IP address on the linkagg successfully? If IP is correctly configured, that means the link aggregation handles "DL_ATTACH_REQ" correctly, because "ifconfig" also uses "DL_ATTACH_REQ".&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Xianje</description>
      <pubDate>Thu, 24 Mar 2005 13:19:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510609#M563047</guid>
      <dc:creator>Xianjie Zhang</dc:creator>
      <dc:date>2005-03-24T13:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510610#M563048</link>
      <description>We successfully configured the IP address on that link aggregate, so I guess "our" DL_ATTACH_REQ doesn't work (even if we use PPA 900 as input) ...&lt;BR /&gt;I believe the DL_ATTACH_REQ usually works :-)...&lt;BR /&gt;maybe there's something not appropriate in our code.&lt;BR /&gt;&lt;BR /&gt;tlrhdq,sys,root # what libhp_apa.a &lt;BR /&gt;libhp_apa.a:&lt;BR /&gt;         HP Auto-Port Aggregation (APA): hp_apa.c: PHNE_28778 B.11.11.11 Apr  1 2003 16:04:53&lt;BR /&gt;&lt;BR /&gt;About the error code: we receive from the stream device a control buffer (buf_len &amp;gt; 0) while data buffer is empty, but I can't decode the buffer content....&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Mar 2005 03:16:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510610#M563048</guid>
      <dc:creator>Enrico Venturi</dc:creator>
      <dc:date>2005-03-25T03:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510611#M563049</link>
      <description>I beleive that something similar has come-up elsewhere in the forums, or perhaps in comp.sys.hp.hpux.  APA does not do _all_ the things a normal DLPI provider might, and some third-party code was doing stuff that it really didn't need to or should - something about trying to reset the interface.&lt;BR /&gt;&lt;BR /&gt;You might provide the entire contents of the return message so someone else might try to understand it.  errno, and dl_errno and the works.</description>
      <pubDate>Fri, 25 Mar 2005 12:44:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510611#M563049</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2005-03-25T12:44:27Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510612#M563050</link>
      <description>Hi, Enrico,&lt;BR /&gt;&lt;BR /&gt;The "ACK" for "DL_ATTACH_REQ" only contains control info, no data. You just need to cast the control data as "dl_ok_ack_t" and decode it. If "dl_ok_ack_t-&amp;gt;dl_primitive" is DL_OK_ACK, then the "DL_ATTACH_REQ" is successful.&lt;BR /&gt;&lt;BR /&gt;Please check the DLPI programmer guide for example programs. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-90139/index.html" target="_blank"&gt;http://docs.hp.com/en/B2355-90139/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;&lt;BR /&gt;Xianjie</description>
      <pubDate>Fri, 25 Mar 2005 14:06:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510612#M563050</guid>
      <dc:creator>Xianjie Zhang</dc:creator>
      <dc:date>2005-03-25T14:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510613#M563051</link>
      <description>see the reply mesage received after my DL_ATTACH_REQ:&lt;BR /&gt;(gdb) print *err_ack&lt;BR /&gt;$2 = {dl_primitive = 3197999093, dl_error_primitive = 3711907495, dl_errno = 2101030891, dl_unix_errno = 3121141789}&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;(gdb) ptype *err_ack&lt;BR /&gt;type = struct {&lt;BR /&gt;    uint32_t dl_primitive;&lt;BR /&gt;    uint32_t dl_error_primitive;&lt;BR /&gt;    uint32_t dl_errno;&lt;BR /&gt;    uint32_t dl_unix_errno;&lt;BR /&gt;}&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Mar 2005 03:40:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510613#M563051</guid>
      <dc:creator>Enrico Venturi</dc:creator>
      <dc:date>2005-03-29T03:40:16Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510614#M563052</link>
      <description>OK, I can see what you meand by being indecipherable.  Those numbers are no where near where one would expect them to be.&lt;BR /&gt;&lt;BR /&gt;It has been a long time since I've done DLPI stuff so be kind :) - you are certain of the structure definition, and that it is indeed a DL_ERROR_ACK that comes-back and not something else?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Mar 2005 13:45:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510614#M563052</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2005-03-29T13:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: DL_ATTACH_REQ fails on a "virtual" PPA</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510615#M563053</link>
      <description>Hi, Enrico,&lt;BR /&gt;&lt;BR /&gt;Did your program issue a DL_GET_PPA_REQ just before the DL_ATTACH_REQ?&lt;BR /&gt;You mentioned that the stack properly runs on any other LAN card (btlan driver) since many many years, but did you try the same program on a btlan interface AFTER APA is installed?&lt;BR /&gt;&lt;BR /&gt;I suspect that the data buffer of DL_GET_PPA_REQ is not big enough. (After APA installed, the returned data size of DL_GET_PPA_REQ inceased substantially.) If your data buffer is not big enough, there will still be control data left on the stream heard after the DL_GET_PPA_REQ is acked. When you try to read back the control data for DL_ATTACH_REQ, it actually reads the remaining data for DL_GET_PPA_REQ, which will NOT be understandable when you try to decode it as a DL_OK_ACK_T.&lt;BR /&gt;&lt;BR /&gt;The same problem happened for the older version of tcpdump. It works fine before APA installed. But after APA is installed, tcpdump failed due to failure of DL_ATTACH_REQ.&lt;BR /&gt;&lt;BR /&gt;I suspect you hit the same problem as the older tcpdump did.&lt;BR /&gt;&lt;BR /&gt;Xianjie</description>
      <pubDate>Fri, 01 Apr 2005 14:31:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dl-attach-req-fails-on-a-quot-virtual-quot-ppa/m-p/3510615#M563053</guid>
      <dc:creator>Xianjie Zhang</dc:creator>
      <dc:date>2005-04-01T14:31:14Z</dc:date>
    </item>
  </channel>
</rss>

