The configuration 2 is NOT supported. The standby link MUST have the same speed, i.e., 1 Gbps in your case. (There are other reasons why a gelan can not be mixed with 100bt, e.g., CKO, check-sum-offload is supported by gelan, but not 100bt.)
I think you need to reference to the users' guide.
Here is the general steps for configuration #1:
1. For the primary link aggregate, decide the aggregation/trunking mode you want to use, set the same mode for your server AND switch, the available modes are: MANUAL, FEC_AUTO, LACP_AUTO. You may want to consult with switch 's manual for corresponding configuration steps.
2. Configure the primary link aggregate. You can edit the configuration files, or you can use SAM.
3. Check the primary link aggregate is created correctly, e.g., use "lanscan -q".
4. Configure IP address on the primary link aggregate, say "ifconfig lan900 10.227.1.10 netmask 255.255.255.0". Modify /etc/netconf approapriately.
5. Make use "linkloop" between lan900 (the primary link aggregate) and gelan3 (say lan3) works fine.
6. Set the mode of lan3 to LAN_MONITOR, i.e., "lanadmin -X -p 3 LAN_MONITOR 900". Edit the /etc/rc.config.d/hp_apaportconf correspondingly if you want to preserve configuration across reboot.
7. Run "lanqueryconf"
8. Edit "/etc/lanmon/lanconfig.ascii": you should see something similar to:
=====
FAILOVER_GROUP lan901
STATIONARY_IP 10.227.1.10
STANDBY lan3 3
PRIMARY lan900 5
=====
If not, modify it.
9. Run "lanapplyconf".
10. If everything works fine, run "lanscan -q", you should see lan901. Run "netstat -in", you should see that IP is configured on lan901, NOT on lan900.
If you need a sample configuration file and could not find it in APA's doc, please let me know.
HTH,
Xianjie
