Alan Maguire wrote:
> my understanding is that having NWAM enabled
> by default was to be deferred until phase 2 when
> support for link aggregations, IPMP, and Crossbow
> VNICs would be added - the idea being that since
> NWAM phase 1 is not slated to support all
> configurations, it accordingly can't upgrade legacy
> configurations completely (if i've got these details
> wrong, someone chime in). thanks!
I think the problem with the above technologies is
that NWAM phase 1 does not have the ability to
automatically detect them nor automagically set them
up. But it does not mean that NWAM cannot have a
static configuration for them. So for example, all
the SMF changes for NWAM can be applied to them, just
that they all have to be in "static" mode. When an
admin wants to use the above technologies, they need
to tell NWAM the configuration. Then NWAM will set
them up. There will be no automagic performed. The
key thing is that an admin needs to use the new NWAM
framework. And I believe this kind of static
configuration is needed anyway.
In phase 0, we can safely disabled NWAM because we
basically have not changed any of the existing setup
procedures, SMF services/dependency. There is little
confusion. In phase 1, there are so many changes and
the key point is that there is a framework. It is a
good idea to use the new NWAM framework to set things
up even though there is no automagic involved.
Otherwise, we are adding one more piece of puzzle for
admins to configure the system. Even with the simple
on/off in phase 0, we got questions about the set up.
I suspect that there will be more confusion in phase
1 given all those changes...
--
K. Poon.
kacheong.poon at sun.com
