From: sunhux G (sunhux@gmail.com)
Date: Tue Apr 01 2008 - 02:11:29 EST
Hi,
I plan to "team" two interface ports (both ports on the same NIC)
on our T5120 (Solaris 10).
After reading Sun IPMP blueprint, I'm still confused :
a)to quote Buck : "I also prefer active/passive. It makes troubleshooting
& authentication much simpler (i.e. defining only one address to a
firewall rule instead of multiple addresses; one entry in /etc/hosts &
dfstab for NFS partners. True, it theoretically cuts down your bandwith,
but keep in mind that IPMP load balances OUTBOUND traffic only"
Question:
So in IPMP, do the client PCs access the Sun server using one
common IP address or there's a couple of IP address as what Buck
said above. I'm aiming for one IP address so as not to complicate
firewall rules. Is an active/active pair of ports still feasible?
b)is IPMP equivalent to Windows network teaming or Linux bonding?
I'm under the impression Windows teaming is active-active & only
one IP address is used by clients to access Windows server
c) Must the IP addresses of the interface be in the same subnet
as the floating/cluster/teaming address (this is the address
which client PCs use to access this Sun server)? I thought
of using "private" addresses (say 10.1.1.1/.2) on the interfaces
so that in case IP addresses are "leaked" into the network by
accident, it won't cause any IP address conflict
Thanks
U
Past summaries follows :
==================================================================
Blue print paper on IPMP :
http://www.sun.com/solutions/blueprints/1102/806-7230.pdf
=========
It doesn't matter. Think of it in a different way. You must have 2 fixed,
non-movable addresses, one per interface. These are used by in.mpathd for
pinging and determining availability. You must have at least one floating IP
address. This is the one that you use for your routing and that you give to
all client systems and that
you put in DNS. How you get to this state is irrelevent. You can use the
primary IP and make that into the movable, or you can assign a new IP and
make that the movable, as long as the floating one is the one you
give out, everything's fine.
Doug
================
Neither 'a' or 'b' are correct.
In IPMP, each physical interface needs its own test address. Then you have
one (active/passive) or two (active/active) 'data' IP addresses.
These data addresses float between the physical interfaces as necessary.
The big stylistic question comes in as to whether you want the 'test'
address as the 'base' address (i.e. hme0) or an 'additional' interface (i.e.
hme0:1). The debate rages on, For me, it makes sense to use the 'test'
address as the 'base' address- i.e. hme0 & hme1 will have their own
addresses <test> which never
change. Then, depending on the situation, either may have additional
addresses.
This is also the model from Sun Cluster & Veritas Cluster, as well as F15K
SCs).
I also prefer active/passive. It makes troubleshooting & authentication
much simpler (i.e. defining only one address to a firewall rule instead of
multiple addresses; one entry in /etc/hosts and dfstab for NFS partners,
True, it theoretically cuts down your bandwith, but keep in mind that IPMP
load balances OUTBOUND traffic only.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:42:53 EDT