On 05/12/10 06:25 PM, Edward Pilatowicz wrote:
also, i have the same question as tony. if nwam already supports
profiles why is this case even needed? why doesn't install just apply a
nwam profile to the system?
On 05/13/10 01:27 AM, Darren J Moffat wrote:
> There has been a very significant amount of engineering work put into
> NWAM profiles and the case of static configuration was an important part
> of it.
The reason NWAM can't be used is that NWAM has a different notion of
static addresses than what we provide for enterprise servers using
network/physical:default.
NWAM's notion of static is reactive in the sense that the static
configuration is not applied if the link isn't up (cable plugged in),
whereas the network/physical:default applies the configuration whether
or not the link is up.
Thus replacing network/physical:default with a static NWAM profile would
introduce a new failure mode; if the cable is unplugged the server can
no longer talk it itself, and server applications that bind to the local
IP addresses of the system would fail - since the addresses wouldn't be
configured when the link is down.
Hence we can't use NWAM for this right now.
One of the many projects underway in this area is to consolidate NWAM
and physical:default. The NWAM engineers are involved in this and other
network configuration projects.
Erik
_______________________________________________
opensolaris-arc mailing list
[email protected]
