In AIX, you can configure multiple EtherChannels per system, but it is required that all the links in one EtherChannel are attached to a single switch. Because the EtherChannel cannot be spread across two switches, the entire EtherChannel is lost if the switch is unplugged or fails. To solve this problem, a new backup option available in AIX 5.2 and later keeps the service running when the main EtherChannel fails. The backup and EtherChannel adapters should be attached to different network switches, which must be inter-connected for this setup to work properly. In the event that all of the adapters in the EtherChannel fail, the backup adapter will be used to send and receive all traffic. When any link in the EtherChannel is restored, the service is moved back to the EtherChannel.
For example, ent0 and ent1 could be configured as the main EtherChannel adapters, and ent2 as the backup adapter, creating an EtherChannel called ent3. Ideally, ent0 and ent1 would be connected to the same EtherChannel-enabled switch, and ent2 would be connected to a different switch. In this example, all traffic sent over en3 (the EtherChannel's interface) would be sent over ent0 or ent1 by default (depending on the EtherChannel's packet distribution scheme), whereas ent2 will be idle. If at any time both ent0 and ent1 fail, all traffic would be sent over the backup adapter, ent2. When either ent0 or ent1 recover, they will once again be used for all traffic.
http://publib16.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/commadmn/tcp_etherchannel.htm
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.commadmn/doc/commadmndita/etherchannel_intro.htm
My blog has moved,please visit the new site
IBM AIX/UNIX system storage administration ksh/perl scripting
Monday, January 12, 2009
Etherchannel and switch requirement
Labels:
etherchannel,
network
Subscribe to:
Post Comments (Atom)
Labels
- ACL (1)
- admin (2)
- AIX 5.3 (1)
- AIX 6.1 (3)
- Atape (1)
- backup (5)
- backupios (1)
- Best Practices (1)
- bosboot (1)
- cdrom (1)
- cfgmgr (1)
- commands (4)
- compatibility (1)
- console (1)
- device (2)
- dhcp (1)
- disk (1)
- DNS (2)
- Downloads (1)
- dump (1)
- Dynamic (1)
- error (1)
- errpt (1)
- ESS (1)
- etherchannel (1)
- Filesystem (7)
- firmware (2)
- Freeware (1)
- ftp (2)
- getty (1)
- GNU (1)
- HACMP (2)
- HEA (1)
- HMC (2)
- hostname (1)
- I/O (1)
- Installation (2)
- installp (2)
- IP alias (1)
- iptrace (1)
- iso (2)
- IVM.CLI (1)
- jfs (1)
- JFS to JFS2 conversion (1)
- jfs2 (2)
- kdb (1)
- kernel (1)
- LED (2)
- lifecycle (2)
- Live Partition Mobility (1)
- lofiadm (1)
- login (1)
- LPAR (1)
- lppchk (1)
- lsof (1)
- LV (1)
- lvm (3)
- memory (1)
- migration (4)
- mksysb (2)
- mkvdev (1)
- mkvgdata (1)
- mount (1)
- multibos (1)
- ndd (2)
- netstat (1)
- network (7)
- NFS (2)
- NIC (4)
- NIM (2)
- NPIV (1)
- ODM (2)
- openssh (1)
- oslevel (1)
- patching (1)
- Performance (4)
- Perl (2)
- Perl Module (2)
- permission (1)
- port (1)
- Power VM (1)
- Power5 (1)
- Power6 (1)
- printer (1)
- problem (17)
- process (4)
- RAID5 (1)
- Recovery (2)
- respawn (1)
- restore (1)
- routing (4)
- RSC (1)
- runq (1)
- savevg (1)
- scripts (4)
- SEA (1)
- security (5)
- sendmail (1)
- solaris (7)
- SSA (1)
- SSH (2)
- ssh-agent (1)
- storage (3)
- subnet (1)
- Sun Remote System Control (1)
- support (2)
- synchronize (1)
- TCPIP (5)
- telnet (2)
- time zone (1)
- topas (1)
- Total Storage (1)
- trace (2)
- tuning (1)
- uninstall (1)
- update (1)
- update boot (4)
- upgrade (3)
- users (2)
- Veritas Volume Manager (1)
- VG (1)
- VIOS (4)
- VMM (1)
- VxVM (1)
- wtmp (1)
No comments:
Post a Comment