<?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: Mpc daemons? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162950#M893237</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I really never heard it.&lt;BR /&gt;The only one info about it that I found is on docs.hp.com about ATM Networks:&lt;BR /&gt;&lt;BR /&gt;MPOA has these logical components:&lt;BR /&gt;&lt;BR /&gt;MPOA Server (MPS)--Implements NHRP and resides on an MPOA router. The MPS includes a Next Hop Server (NHS), and it works with the NHS to resolve the Layer 3 target address of a shortcut route for MPCs. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;MPOA Client (MPC) --Implements the client side of the MPOA protocol. An MPC resides on a LAN Emulation Client (LEC) that is an edge device or an MPOA host. An MPC's main function is to be a point of entry and exit for data flows that use shortcut routes. Note that the ATM Forum specifies that an MPC can be used by more than one LEC. However, in HP's implementation of MPOA, an MPC can be used by only one LEC. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Anyway go ahead into docs.hp.com by keyword 'MPC'.&lt;BR /&gt;&lt;BR /&gt;I hope this helps you.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Ettore</description>
    <pubDate>Tue, 13 Jan 2004 09:29:08 GMT</pubDate>
    <dc:creator>Fabio Ettore</dc:creator>
    <dc:date>2004-01-13T09:29:08Z</dc:date>
    <item>
      <title>Mpc daemons?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162949#M893236</link>
      <description>I see the following daemons on an HP-UX v11 box.  What application or system service do they belong to? In general terms, what do they do?&lt;BR /&gt; &lt;BR /&gt;"MpcAsyncIoDaemon"&lt;BR /&gt; "MpcDispatchDaemon"&lt;BR /&gt; "MpcPeriodicCallbackDaemon"&lt;BR /&gt; "MpcResumeIoDaemon"&lt;BR /&gt; "MpcSpecialRequestDaemon"&lt;BR /&gt;&lt;BR /&gt;Mott Given</description>
      <pubDate>Tue, 13 Jan 2004 09:05:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162949#M893236</guid>
      <dc:creator>Mott Given</dc:creator>
      <dc:date>2004-01-13T09:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Mpc daemons?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162950#M893237</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I really never heard it.&lt;BR /&gt;The only one info about it that I found is on docs.hp.com about ATM Networks:&lt;BR /&gt;&lt;BR /&gt;MPOA has these logical components:&lt;BR /&gt;&lt;BR /&gt;MPOA Server (MPS)--Implements NHRP and resides on an MPOA router. The MPS includes a Next Hop Server (NHS), and it works with the NHS to resolve the Layer 3 target address of a shortcut route for MPCs. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;MPOA Client (MPC) --Implements the client side of the MPOA protocol. An MPC resides on a LAN Emulation Client (LEC) that is an edge device or an MPOA host. An MPC's main function is to be a point of entry and exit for data flows that use shortcut routes. Note that the ATM Forum specifies that an MPC can be used by more than one LEC. However, in HP's implementation of MPOA, an MPC can be used by only one LEC. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Anyway go ahead into docs.hp.com by keyword 'MPC'.&lt;BR /&gt;&lt;BR /&gt;I hope this helps you.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Ettore</description>
      <pubDate>Tue, 13 Jan 2004 09:29:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162950#M893237</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-01-13T09:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: Mpc daemons?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162951#M893238</link>
      <description>I'm not sure if the "MPC" that you found searching docs.hp.com is the same one that I was asking about.  I did not find any of the daemons that I mentioned listed in the manuals that your reply links to.&lt;BR /&gt;&lt;BR /&gt;Mott</description>
      <pubDate>Tue, 13 Jan 2004 14:35:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162951#M893238</guid>
      <dc:creator>Mott Given</dc:creator>
      <dc:date>2004-01-13T14:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Mpc daemons?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162952#M893239</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have the same daemons running on the only system that runs EMC PowerPath software...&lt;BR /&gt;If you look in the /opt/EMCpower/driver/mpc_hp_11_00_64.o file, you will find a lot of Mpc**** strings.&lt;BR /&gt;&lt;BR /&gt;By the way, i don't know what those daemons do...&lt;BR /&gt;&lt;BR /&gt;Hope this help...&lt;BR /&gt;Regards.&lt;BR /&gt;Fred</description>
      <pubDate>Fri, 19 Mar 2004 10:36:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162952#M893239</guid>
      <dc:creator>Frederic Sadoun</dc:creator>
      <dc:date>2004-03-19T10:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: Mpc daemons?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162953#M893240</link>
      <description>Thanks Frederic.  We do have the EMC devices and software so you explanation fits our system.&lt;BR /&gt;&lt;BR /&gt;Mott Given</description>
      <pubDate>Fri, 19 Mar 2004 11:20:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mpc-daemons/m-p/3162953#M893240</guid>
      <dc:creator>Mott Given</dc:creator>
      <dc:date>2004-03-19T11:20:53Z</dc:date>
    </item>
  </channel>
</rss>

