Sebastien Roy writes: > James Carlson wrote: > > Sebastien Roy writes: > >> Peter Memishian wrote: > >>> > > > What is it PORTSTATE? > >>> > > > >>> > > Yes, it seems like PORTSTATE needs to be described. > >>> > > >>> > I meant to ask: What is PORTSTATE? Is there a way to describe this > >>> in a > >>> > way that makes sense to an administrator and in a way which is > >>> distinct > >>> > from STATE? > >>> > >>> The port state indicates whether the individual aggregation port is > >>> standby or attached, which is different than the link state. Or am I > >>> misunderstanding the question? > >> You didn't misunderstand the question, I'm the one who's a bit confused > >> regarding what this means. Are the definitions of "attached" and > >> "standby" defined in 802.3ad? If yes, then adding ", as defined by > >> 802.3ad" might be a good idea. > > > > If you're going to cite it, "802.3ad" is now dead. The relevant bits > > have been folded into IEEE 802.3 itself -- I think that happened with > > -2002. We're now up to 802.3-2005. > > Okay, then "as defined by IEEE 802.3". Honestly, I'm not quite > comfortable punting to the 802.3 spec for administrative things, since > the documents aren't meant to be read by administrators. I guess I'm not > making things worse, though, since there's 0 documentation on any of the > show-aggr output today in dladm(1M).
I agree ... a reference to 802.3 belongs in the "NOTES" section or something like that. If you need it because the values are incomprehensible without reading the IEEE tome, then we're short on user documentation. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
