> A new draft "IPMP Administrative Procedures" has been posted as a first
> pass to document IPMP configuration procedures. These procedures will
> apply upon the completion and implementation of current IPMP
> rearchitecturing:
>
> http://www.opensolaris.org/os/project/clearview/docs/
>
> Of note are the new step to create IPMP interfaces and the introduction
> of "ipmpstat" to obtain different information about IPMP groups.
Raoul,
Before getting into the nitty-gritty, I have a high-level comment: can we
work ipmpstat into the core tasks themselves, rather than having it all at
the end as a separate task map? That is, by and large, administrators
should be encouraged to use ipmpstat rather than ifconfig to verify that
the changes they've made worked as expected. For instance, in example
8-3, the administrator should be using `ipmpstat -i' to see that hme2 is
now a standby interface, and `ipmpstat -tn' to see the test address
configuration. This may be a bit of a challenge since we will need to
reorder the material so that the reader knows the basics of ipmpstat
before getting to the examples, but it will ultimately lead to better
IPMP administration habits.
A few other general observations:
* The IPMP meta-interface is plumbed as part of the "ipmp"
subcommand itself. That is, there is no need to separately
"plumb" an IPMP interface, and it's an error to do so.
* Many of the examples still show group names that don't
match the IPMP meta-interface name. Given that we're not
recommending this practice anymore, we should mention that
it's supported, but eliminate unnecessary uses of it from
the documentation.
* Similarly, I'd recommend we be consistent with our "meta"
IPMP meta-interface name; I'd prefer we use ipmp0 to
myipmp0 (when there's no semantically better name).
* The documentation only covers explicit IPMP group creation.
It should mention how implicit group creation works, too
(though we don't want to encourage it).
--
meem
