I think that implementing EtheChannel will allow you to configure upto 3 ethernet cards with 1 IP address. It also gives you the additional bandwidth and the ability to suffer the failure of one card without losing the IP.
I don't think you can do this directly. However I have implemented some code that allows DNS to route traffic too two or more different IP addresses. So for example a user wishes to connect to server test. Load balanced DNS knows that test traffic can be routed to 2 or more real different IP addresses and will return a different IP address for each sequential request or will decide on which IP address to return for the DNS requst based on current loading. Have a look at
IBM have announced support for AIX 5 with PSSP 3.4 for the SP. as far as I know the only piece missing is P690 SP attach support which is not expected until second Qtr.
EtherChannel is what you want. It will take two or four ethernet adapters and build a new device (en?). You then define your single IP address on this new device. Etherchannel supports load balancing and failover. Etherchannel is also an industry standard. Etherchannel showed up somewhere around 4.3.3 ML7. Make sure you have the latest patches for etherchannel such as bos.net.tcp.client 4.3.3.77 and its coreqs.
Etherchannel is a CISCO invention but AIX has smit support for this and I have put this in where non-cisco switches are used. I tend to set up netif_backup on the adapters i.e. one active and one standby adapter combined into one logical interface. The point is AIX will support etherchannel on certain adapters.
Cheers
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
Standard AIX 4.3.3 has etherchannel and as PSD says it was a CISCO invention but it works for others
--------------------------
smitty etherchannel
How does etherchannel work? Etherchannel would operate at layer 2 below
the protocol stack. The EtherChannel would have one MAC address and for IP
it would have one IP address. For outgoing traffic, the packets are sent out
over one of the adapters of the channel. Which adapter to use is decided by
the lower bits of destination MAC address of the outgoing packet for non-IP
traffic. For IP traffic, the lower bits of destination IP address is used to decide
the adapter. When an adapter of an Etherchannel is down, traffic would be
re-routed through one of the other adapters and this would be transparent to
the upper layers. For incoming traffic, packet could be received over any of the
adapters.
The Etherchannel can be configured with up to 4 Ethernet adapters. It
provides a scaleble server to switch bandwidth. It allows the combination of
multiple ethernet adapters together to form a larger pipe. The etherchannel
allows a server to switch connection throughput between 40 and 800 Mbps.
The etherChannel can be configured with up to 4 ether adapters (ent0, ent2,
ent3, ent5 ) By default all the adapters of the etherchannel would be assigned
the MAC address of the first adapter that the user selects. The user will also
have the option to set a MAC address for all the adapters. This will be done
using the "use_alt__addr" and "alt_addr" attributes. You would configure an
etherchannel after the ethernet device drivers are configured. And before any
users of those devices are configured. Software comes as a part of AIX 4.3.3
and is devices.common.IBM.ethernet.rte. It is set up in smit under smitty
etherchannel. You will then need to select two to four adapters from the list to
form your channel.
NOTE:
One has to remember that trunking solutions such as EtherChannel need
routers or switches which are capable of talking the same language. It doesn't
matter if you have AIX 4.3.3 running EtherChannel or Solaris 2.7 running
Trunking 1.x or HPUX 11.x with Port Aggregation software. If you don't have
the correct model of Cisco router with the appropriate software on it, you can't
use the trunking software on your OS.
There is also a new option to set interface specific options for network
devices. It is the use_isno option in the no command. I.e.
no -o use_isno=1 (1=enabled 0=disable) The individual setting with the
ifconfig command are: tcp_recvspace, tcp_sendspace, tcp_mssdflt,
tcp_nodelay, and rfc1323.
------------------------
VIPA information is best found in the AIX 5L differences guide page 208
or at least chapter 5 of the book.... (it was on page 208)
SG24-5765-00
VIPA if used for 8+ interfaces uses up to a gig of memory.
The default for the no -a ifsize is 8 so if you wish to have more than 8 you must
up this parameter....
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.