APA lan monitor mode hot standby failover mode

Here's what it looks like when a network link fails over to a secondary, standby lan (and then back again):

secondary port is down:

Link Aggregate PPA #             : 900
Link Aggregation Mode            : LAN_MONITOR
Load Balance Mode                : Hot Standby (LB_HOT_STANDBY)
Active Port PPA #                : 0
Port(s) ready                    : NONE
Port(s) not ready                : 1
Port(s) connected to active port : NONE

SYSLOG:
May 11 21:00:17 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan1 is down (lan0 is active)
May 11 21:00:52 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan0 isn't receiving poll packets (lan0 is active)


after plugged in:
Link Aggregate PPA #             : 900
Link Aggregation Mode            : LAN_MONITOR
Load Balance Mode                : Hot Standby (LB_HOT_STANDBY)
Active Port PPA #                : 0
Port(s) ready                    : 1
Port(s) not ready                : NONE
Port(s) connected to active port : NONE

SYSLOG:
May 11 21:01:32 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan0 is now receiving poll packets (lan0 is active)
May 11 21:01:52 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan1 is up (lan0 is active)

then:
Link Aggregate PPA #             : 900
Link Aggregation Mode            : LAN_MONITOR
Load Balance Mode                : Hot Standby (LB_HOT_STANDBY)
Active Port PPA #                : 0
Port(s) ready                    : 1
Port(s) not ready                : NONE
Port(s) connected to active port : 1




Primary port down:
Link Aggregate PPA #             : 900
Link Aggregation Mode            : LAN_MONITOR
Load Balance Mode                : Hot Standby (LB_HOT_STANDBY)
Active Port PPA #                : 1
Port(s) ready                    : NONE
Port(s) not ready                : 0
Port(s) connected to active port : NONE

SYSLOG:
May 11 21:03:05 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan0 is down (lan1 is active)
May 11 21:03:42 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan1 isn't receiving poll packets (lan1 is active)


Primary port back up:
Link Aggregate PPA #             : 900
Link Aggregation Mode            : LAN_MONITOR
Load Balance Mode                : Hot Standby (LB_HOT_STANDBY)
Active Port PPA #                : 1
Port(s) ready                    : 0
Port(s) not ready                : NONE
Port(s) connected to active port : NONE

SYSLOG:
May 11 21:05:12 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan1 is now receiving poll packets (lan1 is active)


May 11 21:05:32 sbhs3010 vmunix: APA/LM: FOG:lan900 - lan0 is up (lan1 is active)
same time:
Link Aggregate PPA #             : 900
Link Aggregation Mode            : LAN_MONITOR
Load Balance Mode                : Hot Standby (LB_HOT_STANDBY)
Active Port PPA #                : 1
Port(s) ready                    : 0
Port(s) not ready                : NONE
Port(s) connected to active port : 0


doesn't fail back to original active port because both ports have the same priority.

using Twitter with Google talk for your domain

http://www.kavinda.net/2007/07/31/HowToTwitterOnGTalkForYouDomain.aspx  explains how to add the necessary DNS SRV records to your zone in order to twit via Google chat.  This is necessary to get twitter to work with Google Talk when your using Google Apps for your domain.

Go to the Chat section under 'Service Settings' when in the administration 'manage this domain' page for your domain.  a link will be to: http://www.google.com/support/a/bin/answer.py?answer=60227&hl=en   But you'll need to follow the above instructions as well (maybe, haven't tried yet)

HP APA (auto port aggregation)

HP-UX has no built in lan aggregation or failover; I know - it's a damn shame.  (note: serviceguard does have a local lan failover mode)  HP APA (Auto Port Aggregation).

Be sure to do the configuration from a console connection or connect from a NIC that won't be involved in APA, otherwise you'll drop and may not be able reconnect over tha lan if you screw up the config.

commands to configure it:
lanqueryconf
lanapplyconf
lancheckconf
landeleteconf

Here's my quick and dirty version of creating a lan failover group:

--- APA configuration --
added the following line to /etc/rc.config.d/hp_apaconf
HP_APA_USE_SYSLOG=1

add the following to: /etc/rc.config.d/hp_apaportconf
HP_APAPORT_INTERFACE_NAME[0]=lan5
HP_APAPORT_CONFIG_MODE[0]=LAN_MONITOR

HP_APAPORT_INTERFACE_NAME[1]=lan6
HP_APAPORT_CONFIG_MODE[1]=LAN_MONITOR


 /sbin/init.d/hplm stop
 /sbin/init.d/hpapa stop
 /sbin/init.d/hpapa start
 /sbin/init.d/hplm start

create ascii file:
lanqueryconf -s

change priority of both primary and secondary to the same value, so that failback doesn't occur.
vi /etc/lanmon/lanconfig.ascii

check validity of ascii file:
lancheckconf

apply the changes to the binary file:
lanapplyconf

check config:
lanscan and lanscan -q and lanadmin -x -v PPA  and netstat -in



Once it's configured, here are some useful commands for looking at the status:
real status of ports:  lanadmin -x -i 900 
load balancing mode:   lanadmin -x -l 900
verbose config:        lanadmin -x -v 900

Where 900 is the PPA number for the apa/failover group