Configuring network teaming/bonding on HP-UX, RHEL & older Solaris versions

Binding physical interfaces together to form a single IP link is called
very much differently, depending on the vendor you are talking to.
As far as I remember, it's usually called:
 - channel bonding (Linux, especially RH ES)
 - link aggregation (Solaris 10) ot trunking (Solaris 2.6 - 9, using
   Sun "trunking" software)
 - teaming (Cisco)

For Solaris 10 you found the solution alredy at
http://docs.sun.com/app/docs/doc/816-4554/gafxi?a=view


For Solaris prior to Solaris 10, you need "Sun Trunking" software
See at http://docs.sun.com/source/817-3374-11/overview.html



For Network Applicance filer, you simply create a virtual interface
(VIF) by assigning the desired physical interfaces (IF) to it and
giving the VIF the required IP settings (address, netmask etc.)


For RH EL:
Try loading the bonding module (while checking /var/log/messages)
  /sbin/insmod bond<x>  param=val ...
substituting <x> with some number. Once you did not get an error
in /var/log/messages, use this number (index) to put in
  /etc/modules.conf
alias bond0 bonding  
   options bonding miimon=100 mode=1
Now, create the corresponfign interface files
  /etc/sysconfig/network-scripts/ifcfg-eth<n>  (<n> is 0, 1, 2, etc.)
DEVICE=eth<n>
USERCTL=no
ONBOOT=yes
MASTER=bond0          { this is the bonding module from above }
SLAVE=yes  
BOOTPROTO=none
Finally, create a network script
  /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
USERCTL=no
ONBOOT=yes
BROADCAST=192.168.5.255
NETWORK=192.168.5.0
NETMASK=255.255.255.0
GATEWAY=192.168.5.1
IPADDR=192.168.5.202

You may reboot now or load the modules manually:
/sbin/insmod /lib/modules/`uname -r`/kernel/drivers/net/bonding/bonding.o miimon=100 mode=1
/sbin/service network restart