[EMAIL PROTECTED] writes:
> ...but when you say "don't mix", does that imply they don't work
> together or that it just isn't optimal?
They cannot be used together. As the ifconfig(1M) man page says:
The use of the usesrc option is mutually exclusive of
the IP multipathing ifconfig options, group and standby.
That is, if an interface is already part of a IP mul-
tipathing group or specified as a standby interface,
then it cannot be specified with a usesrc option, and
vice-versa. For more details on IP multipathing, see
in.mpathd(1M) and the .
(No, I don't know what should be between "the" and "." in that last
sentence. It's a documentation mystery.)
> It would be nice if all of our networking technologies worked
> together...
Possibly, though I don't think all combinations are actually sensible
together. This is one of those cases where I don't think the
combination makes sense.
The whole point of IPMP is to move a set of IP addresses around so
that they get different MAC addresses at different times -- allowing
fail-over and inbound load spreading based on the IP-to-MAC mapping.
The whole point of 'vni' and 'usesrc' is to place an IP address on a
*VIRTUAL* interface -- one that like lo0 quite intentionally does
*not* have a MAC address -- and use routes instead to direct traffic.
Thus, the conflict is inherent. They do different things. Mashing
them together doesn't make operational sense to me.
I suppose someone could come up with a project to rationalize them
together. I have no idea what that project would look like, and I
don't know if it's worthwhile to attempt, but I guess anything is
possible.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
