Alan, Thanks so much. This information is just what I was looking for. The more I read, the better I understand. The command-line functions are pretty straight-forward to me, but some of the background and "how it works" stuff I'm still struggling with.
I think once I have the latest bits installed on my laptop, and I can run some commands and do some testing, it will all make more sense. I've been struggling with a case of writer's block, but yesterday, I actually had a break-through. : ) Thanks again, Nita On 08/13/09 06:49, Alan Maguire wrote: > hi Nita > > I'll bite - comments inline below... > > Juanita Heieck wrote: >> Hi, >> >> I need to include a couple of sections in the overview chapter of the >> docs: >> >> 1. Benefits of using NWAM (why you want to use) >> 2. Why you might choose to disable NWAM >> >> - For the section about why you'd choose to use NWAM: >> >> Obviously NWAM is enabled by default, and out of the box, it's >> designed to >> configure your network automatically. Also, NWAM has >> dynamic capabilities that address changes in network conditions. >> I'd like to elaborate a bit about other benefits, such >> as the ability to create/use other profiles to >> meet different networking needs. >> >> Are there any other obvious benefits that I'm missing? >> > That's a good summary. Basically NWAM is valuable > for laptops and systems that find themselves in > different network environments regularly, but thanks > to the GUI, it's also useful for setting up static configurations > (i.e. static IP). It's also handy in general for using WiFi > since the GUI makes connecting and setting keys > etc easier. >> - I also need to add information about >> how to switch to manual network configuration mode >> (how to disable NWAM). In that section, I'd like to include "why" >> someone might opt to manually configure their network. >> > the how is simply: > > # svcadm disable nwam > # svcadm enable physical:default. >> The design doc has some information that I can use, >> but it would be really helpful if >> someone could just summarize in one or two paras >> these two pieces of information. >> > The "why" would be mainly configuration scenarios > that NWAM phase 1 does not support - if link aggregations, > IPMP, VNICs or VLANs are in use, there's > no way to configure these via NWAM presently. That's > all coming in the future hopefully, but for now the > options are limited. A bit brief, but I think that's > the main reason not to use phase 1 now (maybe > I'm biased though ;-) ). > > Hope this helps, > > Alan
