Perhaps not the right forum for this, but I would like to suggest an RFE for 
IPMP:  It would be very nice if probe targets could be explicitly specified 
somehow in the /etc/default/mpathd file.  Adding host routes to the route table 
to override selection of probe targets has always seemed like a kludge to me 
(no 
offense to however wrote it) and can be quite unwieldy to configure, maintain, 
and troubleshoot when you have servers with multiple IPMP groups on multiple 
physical NICs and/or VLAN tagged interfaces.

I am however quite happy to see the new features being added here.  Having just 
one "virtual" interface appear in 'ifconfig -a' for each group will make that 
output much easier to understand, particularly on servers with many groups 
and/or interfaces.  I think the new syntax for configuring groups in the 
/etc/hostname.* files will make configuration of IPMP simpler and more 
straightforward as well.


Thanks,
Chuck


Peter Memishian wrote:
> The Clearview IPMP component has now integrated into build 107 of Nevada;
> a huge thanks to everyone who assisted with this formidable task.
> 
> Now, on to Clearview IP Tunneling!
> 
> 
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Flag Day: Clearview IPMP Rearchitecture
> From:
> Peter Memishian <peter.memishian at sun.com>
> Date:
> Tue, 06 Jan 2009 20:40:31 -0500
> To:
> on-all at eng.sun.com, onnv-gate at onnv.eng.sun.com
> 
> To:
> on-all at eng.sun.com, onnv-gate at onnv.eng.sun.com
> 
> 
> This flag day affects those who use or test IP Multipathing (IPMP), those
> who use cap-eye Install, and those who do incremental builds.  Others can
> stop reading now.
> 
> My recent integration of:
> 
>   PSARC/2007/272 Project Clearview: IPMP Rearchitecture
> 
> ... introduces a new "ipmpstub" driver, which is needed early in boot to
> configure IPMP on the system.  Thus, systems configured for IPMP will need
> to use the version of bfu included with this integration.  If you neglect
> to do this, networking will fail to come up on next boot.  However, simply
> reboot again and all will be well.
> 
> Additionally:
> 
>   * Cap-eye Install will not get you across this flag day.  You must use
>     BFU or a package-based upgrade.
> 
>   * For incremental builds to create cpio archives successfully, the
>     following files must be removed from the proto area first:
> 
>         kernel/drv/vni    
>         kernel/drv/amd64/vni
>         kernel/drv/sparcv9/vni
>         kernel/drv/vni.conf
>         usr/lib/libipmp.so
>         usr/lib/libipmp.so.1
>         usr/lib/llib-lipmp
>         usr/lib/llib-lipmp.ln
> 
>   * Changes to Sun Cluster to support Clearview IPMP are under
>     development; see 6787361.  Since Sun Cluster typically trails Nevada
>     by a few builds, this shouldn't cause any problems.
> 
>   * The existing IPMP test suite will no longer report meaningful results.
>     A new comprehensive test suite for IPMP is currently in code review
>     and will integrate shortly; see 6789048.
> 
> *** The remainder of this message is a heads-up ***
> 
> As the project name suggests, IPMP's inner workings have been rewritten
> from the ground up to address numerous longstanding architectural flaws.
> The most visible change is that each IPMP group is now modeled as a single
> IP interface that hosts a set of IP addresses that are dynamically bound
> to a set of underlying IP interfaces.  The old semantics and features are
> still supported, along with many additional features such as DHCP, dynamic
> routing, and IP observability.  The "legacy" administrative model is still
> supported, but a new administrative model provides additional capabilities
> such as vanity naming of IPMP IP interfaces.  Further, the new
> ipmpstat(1M) utility provides visibility into the IPMP subsystem.  For
> more information, please see:
> 
>   http://www.opensolaris.org/os/project/clearview/docs/ipmpov.pdf
>   http://www.opensolaris.org/os/project/clearview/docs/ipmpconfig.pdf
>   http://sac.eng/PSARC/2007/272/final.materials/manpages
> 
> Please file CRs against network/ipmp or kernel/tcp-ip as appropriate.
> Please send feedback and questions to clearview-discuss at opensolaris.org.
> 
> Thanks and enjoy,
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 
> _________________________________
> clearview-discuss mailing list
> clearview-discuss at opensolaris.org


Reply via email to