On Tue, 29 May 2007, Garrett D'Amore wrote:
> Al Hopper wrote:
... snip ....
>> a) you've got a white box with 2 ether interfaces marked "0" and "1" and
>> you need to identify which is which. Easy - unplug one briefly and look at
>> the console message.
.... snip ...
> In all of these cases, you _do not_ need to know the link speed/duplex, the
> "up" and "down" messages that I've proposed will address this need.
>
> To re-state:
>
> * the link state change will be logged (going from down to up, or vice
> versa), but the details of speed, duplex, channel, and other link tunables
> will _not_ be part of the message that I've proposed.
Every time I (personally) see the link up/down message, I *always* do
a mental "sanity check" to determine if the speed/duplicity settings
were "as expected". In our local environment that would almost always
be "1000Mbps full duplex" for an interface that is gigabit capable.
However, in a large client environment I am familiar with, it should
always be 100Mbps/full duplex, because they have "hard coded" every
bloody port in the entire datacenter[0]. Or at least, attempted
to[1]. So the speed/duplicity is always sanity checked - and I know
the sys admins I work closely with _always_ check it also.
> Hope that answers this concern.
I think the current info is very useful and should be retained, if
at all possible.
On a side note, as a developer, when I have my head in some code, I
generally look at what is logged at the "info" level and see if there
is some other data that is "close by" that might be useful and append
it to the message. In this case, when I say "close by", I mean in a
local data structure, or function arg, that is easy and inexpensively
(from a system resource perspective) added.
[0] your typical design by committee where the techies on the
committee are out-numbered 10 to 1 by 100% Buzzword Compliant
Management Types (BCMT).
[1] Until they swap out a switch supervisor board, or upgrade the
switch code - or some "new guy" comes along and "fixes" the current
switch configs. Or they move the wires over to a new switch (during a
maintenance window that we never received notification of).
Regards,
Al Hopper Logical Approach Inc, Plano, TX. al at logical-approach.com
Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT
OpenSolaris Governing Board (OGB) Member - Apr 2005 to Mar 2007
http://www.opensolaris.org/os/community/ogb/ogb_2005-2007/
