<?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: Auto Port Aggregation setup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139525#M540732</link>
    <description>I don't know how lan_monitor is monitoring the connection. I suspect that it just monitors the link state.&lt;BR /&gt;If you setup a balanced configuration it will also work if one link is down. It will not work if you accidentially change the VLAN configuration of one port etc.&lt;BR /&gt;&lt;BR /&gt;The only drawback in the manual mode is, that you have jumping MAC addresses on the switch. lan900 has 1 MAC address and for outging traffic this MAC address is used round robbin on every lan adapter. Some network guys don't like such behavior.&lt;BR /&gt;&lt;BR /&gt;I'd go for the load balancing setup because it includes the failover functionality and adds some kind of (outgoing) port aggregation.&lt;BR /&gt;&lt;BR /&gt;My 2 cents,&lt;BR /&gt;Armin&lt;BR /&gt;</description>
    <pubDate>Tue, 05 Feb 2008 08:42:08 GMT</pubDate>
    <dc:creator>Armin Kunaschik</dc:creator>
    <dc:date>2008-02-05T08:42:08Z</dc:date>
    <item>
      <title>Auto Port Aggregation setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139521#M540728</link>
      <description>I'm having difficulty understanding an internal document on setting up Auto Port Aggregation using 2 GB Lan cards. Here is the extract from the doco :-&lt;BR /&gt;&lt;BR /&gt;###############################################&lt;BR /&gt;3.1.5. Auto Port Aggregation Configuration&lt;BR /&gt;Next is to edit the Auto Port Agregation configuration file,&lt;BR /&gt; /etc/rc.config.d/hp_apaconf&lt;BR /&gt;Figure 4. /etc/rc.config.d/hp_apaconf&lt;BR /&gt;HP_APA_INTERFACE_NAME[0]=lan900 ## HP default 1st AggPort&lt;BR /&gt;HP_APA_LOAD_BALANCE_MODE[0]=LB_MAC ## Load balancing via MAC&lt;BR /&gt;HP_APA_HOT_STANDBY[0]=off&lt;BR /&gt;HP_APA_GROUP_CAPABILITY[0]=5&lt;BR /&gt;HP_APA_KEY[0]= HP_APA_MANUAL_LA[0]=0,1 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;3.1.6. Network IP Configuration&lt;BR /&gt;The final configuration step is to configure the IP connectivity to the Omnipresence network. This is done in similar fashion as you would for normal IP connectivity, except now you will configure a “virtual” interface”&lt;BR /&gt;Figure 5. /etc/rc.config.d/netconf&lt;BR /&gt;DEFAULT_INTERFACE_MODULES=""&lt;BR /&gt;INTERFACE_STATE[0]=up&lt;BR /&gt;INTERFACE_NAME[0]=lan900 # as configured in figure 4&lt;BR /&gt;IP_ADDRESS[0]=10.97.82.12   # Use YOUR assigned address&lt;BR /&gt;SUBNET_MASK[0]=255.255.255.224   # Use YOUR assigned netmask&lt;BR /&gt;Note: The number within the [ ] brackets will depend on your hardware configuration, for this example it is 0, as this is the first interface on the system.&lt;BR /&gt;3.2. Network Activation&lt;BR /&gt;To activate the network connectivity issue the following commands;&lt;BR /&gt;# /sbin/init.d/hpapa start&lt;BR /&gt;         /sbin/init.d/hpapa started&lt;BR /&gt;         Please be patient. This may take about 40 seconds.&lt;BR /&gt;   HP_APA_DEFAULT_PORT_MODE = MANUAL&lt;BR /&gt;lan900&lt;BR /&gt;   /usr/sbin/lanadmin  -X -l LB_MAC 900&lt;BR /&gt;   New Load Balancing = 2&lt;BR /&gt;    /usr/sbin/lanadmin  -X -y off 900&lt;BR /&gt;   New Hot Standby = OFF&lt;BR /&gt;    /usr/sbin/lanadmin -X -g 900 5 900&lt;BR /&gt;   New Group Capability = 5&lt;BR /&gt;   /usr/sbin/lanadmin  -X  -a 0 1 900&lt;BR /&gt;   Added ports:0 1 to lan900&lt;BR /&gt;   /sbin/init.d/hpapa Completed successfully.&lt;BR /&gt;##############################################&lt;BR /&gt;&lt;BR /&gt;Questions:-&lt;BR /&gt;&lt;BR /&gt;1. My understanding is this is set just for load balancing an d not failover - Is this true?&lt;BR /&gt;&lt;BR /&gt;2. I have one IP address set for lan 0. Should this same IP address be used for lan 1 i.e. have another entry in netconf&lt;BR /&gt;INTERFACE_NAME[1]=lan900&lt;BR /&gt;&lt;BR /&gt;3. Looking at doco there is mention of adding entries to the file 'hp_apaportconf' but in the extract from the doco there is none ?&lt;BR /&gt;&lt;BR /&gt;Basically I'm a little confused and would appreciate clarification. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 03 Feb 2008 23:12:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139521#M540728</guid>
      <dc:creator>Kenneth Woolard</dc:creator>
      <dc:date>2008-02-03T23:12:21Z</dc:date>
    </item>
    <item>
      <title>Re: Auto Port Aggregation setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139522#M540729</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Here are short answers:&lt;BR /&gt;&lt;BR /&gt;1. True. Your setup is designed for&lt;BR /&gt;load balancing. Failover is very different.&lt;BR /&gt;&lt;BR /&gt;Assign IP address to only the primary card&lt;BR /&gt;in the link aggregate for the failover scenario.&lt;BR /&gt;&lt;BR /&gt;2. No, you assign IP address to the relevant&lt;BR /&gt;link aggregate in /etc/rc.config.d/netconf&lt;BR /&gt;(lan900).&lt;BR /&gt;&lt;BR /&gt;3. Configure /etc/rc.config.d/hp_apaportconf:&lt;BR /&gt;(No entries for these interfaces in the netconf file). For manual change:&lt;BR /&gt;&lt;BR /&gt;HP_APAPORT_INTERFACE_NAME [0]=lan0&lt;BR /&gt;HP_APAPORT_GROUP_CAPABILITY [0]=5&lt;BR /&gt;HP_APAPORT_PRIORITY [0]=0&lt;BR /&gt;HP_APAPORT_CONFIG_MODE [0]=MANUAL&lt;BR /&gt;&lt;BR /&gt;HP_APAPORT_INTERFACE_NAME [1]=lan1&lt;BR /&gt;HP_APAPORT_GROUP_CAPABILITY [1]=5&lt;BR /&gt;HP_APAPORT_PRIORITY [1]=0&lt;BR /&gt;HP_APAPORT_CONFIG_MODE [1]=MANUAL&lt;BR /&gt;&lt;BR /&gt;Example how to put lan0 and lan1 into a&lt;BR /&gt;failover group:&lt;BR /&gt;&lt;BR /&gt;HP_APAPORT_INTERFACE_NAME[0]=lan0&lt;BR /&gt;HP_APAPORT_CONFIG_MODE[0]=LAN_MONITOR&lt;BR /&gt;&lt;BR /&gt;HP_APAPORT_INTERFACE_NAME[1]=lan1&lt;BR /&gt;HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR&lt;BR /&gt;&lt;BR /&gt;You can configure HP APA so that it will&lt;BR /&gt;aggregate ports in any of the following port&lt;BR /&gt;aggregation modes:&lt;BR /&gt;&lt;BR /&gt;FEC_AUTO or LACP_AUTO Port Aggregation Modes&lt;BR /&gt;&lt;BR /&gt;MANUAL Port Aggregation Mode&lt;BR /&gt;&lt;BR /&gt;Lot of good references are available at HP.&lt;BR /&gt;For example:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/J4240-90039/index.html" target="_blank"&gt;http://docs.hp.com/en/J4240-90039/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;VK2COT</description>
      <pubDate>Mon, 04 Feb 2008 00:50:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139522#M540729</guid>
      <dc:creator>VK2COT</dc:creator>
      <dc:date>2008-02-04T00:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: Auto Port Aggregation setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139523#M540730</link>
      <description>Thanks for the clarification but I'm still slightly confused on Point 3.&lt;BR /&gt;It seems that the way that NIC aggregation (load balancing) is configured means that if one of the NIC fails then all traffic will fall over to the remaining NIC.&lt;BR /&gt;To me this seems the same as NIC failover</description>
      <pubDate>Mon, 04 Feb 2008 01:38:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139523#M540730</guid>
      <dc:creator>Kenneth Woolard</dc:creator>
      <dc:date>2008-02-04T01:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: Auto Port Aggregation setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139524#M540731</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Data flows on a failing link are migrated to&lt;BR /&gt;the remaining "up" devices in the link&lt;BR /&gt;aggregate. When the link returns to the "up"&lt;BR /&gt;state, only new data flows will be sent on this &lt;BR /&gt;link that has rejoined the link aggregate.&lt;BR /&gt;&lt;BR /&gt;A data flow is defined by the load balancing&lt;BR /&gt;algorithm used. In the case of the LB_MAC&lt;BR /&gt;algorithm, the data flow is identified by the&lt;BR /&gt;low order byte of the destination MAC address.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;VK2COT&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Feb 2008 08:15:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139524#M540731</guid>
      <dc:creator>VK2COT</dc:creator>
      <dc:date>2008-02-04T08:15:47Z</dc:date>
    </item>
    <item>
      <title>Re: Auto Port Aggregation setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139525#M540732</link>
      <description>I don't know how lan_monitor is monitoring the connection. I suspect that it just monitors the link state.&lt;BR /&gt;If you setup a balanced configuration it will also work if one link is down. It will not work if you accidentially change the VLAN configuration of one port etc.&lt;BR /&gt;&lt;BR /&gt;The only drawback in the manual mode is, that you have jumping MAC addresses on the switch. lan900 has 1 MAC address and for outging traffic this MAC address is used round robbin on every lan adapter. Some network guys don't like such behavior.&lt;BR /&gt;&lt;BR /&gt;I'd go for the load balancing setup because it includes the failover functionality and adds some kind of (outgoing) port aggregation.&lt;BR /&gt;&lt;BR /&gt;My 2 cents,&lt;BR /&gt;Armin&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Feb 2008 08:42:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/auto-port-aggregation-setup/m-p/4139525#M540732</guid>
      <dc:creator>Armin Kunaschik</dc:creator>
      <dc:date>2008-02-05T08:42:08Z</dc:date>
    </item>
  </channel>
</rss>

