<?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: Automatic Port Aggregation in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694212#M555288</link>
    <description>You don't really "move" an ip - you setup the aggregate in one of the following ways:&lt;BR /&gt;&lt;BR /&gt;MANUAL   Use this mode to configure link aggregates if the server connects to a switch that supports only manual configuration. This mode requires the switch to support link aggregation. In the event of a link failure, APA automatically migrates the data flow from the failed link to another link in the aggregation.&lt;BR /&gt; &lt;BR /&gt;FEC_AUTO   Use this mode to configure link aggregates connected to a switch that supports the Cisco Fast EtherChannel protocol (PAgP). This mode requires the switch to support the PAgP (FEC) protocol. In the event of a link failure, PAgP automatically migrates the data flow from the failed link to another link in the aggregation.&lt;BR /&gt; &lt;BR /&gt;LACP_AUTO   Use this mode to automatically aggregate links connected to IEEE 802.3ad (LACP) supported switches. This mode requires the switch to support the LACP protocol. In the event of a link failure, LACP automatically migrates the data flow(s) from the failed link to another link in the aggregation.&lt;BR /&gt; &lt;BR /&gt;LAN_MONITOR   Use this mode to configure failover groups. In the event of a link failure, the LAN Monitor software automatically migrates the data flow from the primary link to one of the standby links in the failover group. Failover groups do not support HP Serviceguard. The mode does not strictly require the switch to support link aggregation, although some configurations might require the switch to support link aggregation.&lt;BR /&gt; &lt;BR /&gt;More info available here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/J4240-90031/index.html" target="_blank"&gt;http://docs.hp.com/en/J4240-90031/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
    <pubDate>Mon, 19 Dec 2005 11:48:45 GMT</pubDate>
    <dc:creator>Geoff Wild</dc:creator>
    <dc:date>2005-12-19T11:48:45Z</dc:date>
    <item>
      <title>Automatic Port Aggregation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694211#M555287</link>
      <description>Hello colleagues,&lt;BR /&gt;if I've already configured LAN #0 on my machine, can I set up a link aggregate using a not configured card, and "move" the LAN #0 IP to the new interface?&lt;BR /&gt;&lt;BR /&gt;ciao&lt;BR /&gt;Enrico</description>
      <pubDate>Mon, 19 Dec 2005 10:34:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694211#M555287</guid>
      <dc:creator>Enrico Venturi</dc:creator>
      <dc:date>2005-12-19T10:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic Port Aggregation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694212#M555288</link>
      <description>You don't really "move" an ip - you setup the aggregate in one of the following ways:&lt;BR /&gt;&lt;BR /&gt;MANUAL   Use this mode to configure link aggregates if the server connects to a switch that supports only manual configuration. This mode requires the switch to support link aggregation. In the event of a link failure, APA automatically migrates the data flow from the failed link to another link in the aggregation.&lt;BR /&gt; &lt;BR /&gt;FEC_AUTO   Use this mode to configure link aggregates connected to a switch that supports the Cisco Fast EtherChannel protocol (PAgP). This mode requires the switch to support the PAgP (FEC) protocol. In the event of a link failure, PAgP automatically migrates the data flow from the failed link to another link in the aggregation.&lt;BR /&gt; &lt;BR /&gt;LACP_AUTO   Use this mode to automatically aggregate links connected to IEEE 802.3ad (LACP) supported switches. This mode requires the switch to support the LACP protocol. In the event of a link failure, LACP automatically migrates the data flow(s) from the failed link to another link in the aggregation.&lt;BR /&gt; &lt;BR /&gt;LAN_MONITOR   Use this mode to configure failover groups. In the event of a link failure, the LAN Monitor software automatically migrates the data flow from the primary link to one of the standby links in the failover group. Failover groups do not support HP Serviceguard. The mode does not strictly require the switch to support link aggregation, although some configurations might require the switch to support link aggregation.&lt;BR /&gt; &lt;BR /&gt;More info available here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/J4240-90031/index.html" target="_blank"&gt;http://docs.hp.com/en/J4240-90031/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Mon, 19 Dec 2005 11:48:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694212#M555288</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-12-19T11:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic Port Aggregation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694213#M555289</link>
      <description>You could, but it wouldn't be lan0 any more.  APA link aggregates typically start at lan900.  And you'd get all sorts of errors moving forward if you have the original NIC off the aggregate on a permanent basis moving forward.&lt;BR /&gt;&lt;BR /&gt;If you're just trying to set up an existing IP on a different NIC, you're better off just doing it right.  If you get your command line parms figured out correctly, you can even execute the "ifconfig lan0 unplumb; ifconfig lan&lt;X&gt; &lt;IP&gt; netmask &lt;MASK&gt;" command so that there's &amp;lt;1 sec disruption to your IP's uptime. (Do this from the console, and not a remote telnet/ssh session!)&lt;/MASK&gt;&lt;/IP&gt;&lt;/X&gt;</description>
      <pubDate>Mon, 19 Dec 2005 12:02:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694213#M555289</guid>
      <dc:creator>Greg Vaidman</dc:creator>
      <dc:date>2005-12-19T12:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic Port Aggregation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694214#M555290</link>
      <description>Enrico,&lt;BR /&gt;&lt;BR /&gt;if you no longer wish to use lan0...then yes you can move the ip over to your new lan card (configured as an APA interface)...just make sure to modify the /etc/rc.config.d/netconf file.  Use lanscan -a to verify your APA lan id# (i.e. lan900)....also you can use lanadmin to configure your lancards (if you need to set them to auto-neg)&lt;BR /&gt;Something to keep in mind (which I'm sure the link mentioned in the previous post) when setting up channeling...your 2 lan interfaces need to be connected to the same switch.  If you wish to be fully redundant then set them up on separate switches (for MANUAL mode).&lt;BR /&gt;files to be configured for APA are gonna be the apaconf and apaportconf files in /etc/rc.config.d.&lt;BR /&gt;</description>
      <pubDate>Mon, 19 Dec 2005 12:03:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automatic-port-aggregation/m-p/3694214#M555290</guid>
      <dc:creator>Christine Hartman</dc:creator>
      <dc:date>2005-12-19T12:03:53Z</dc:date>
    </item>
  </channel>
</rss>

