AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080207140142.70ec5ec0@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<charissa.willard@onstor.com>,<tim.gardner@onstor.com>,<dl-designreview@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/design review	0	BB375AF679D4A34E9CA8DFA650E2B04E083508AF@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 7 Feb 2008 14:07:58 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Charissa Willard" <charissa.willard@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>, "dl-Design Review"
 <dl-designreview@onstor.com>
Subject: Re: sc interface state
Message-ID: <20080207140758.22067be3@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E083508AF@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0835086F@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E083508AF@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

An interface can be 'UP' or enabled w/o any cable plugged into the
socket (or AP associated for wireless interfaces), but no 'LINK' in
that case. On the other hand, an interface can be in the 'LINK' state
but not be 'UP' or have any IP address assigned.  As for the _interface
show interface_ command, I don't know what the spec says for the
Operation column. If there is a spec.

In the case of TED00018877, it appears the interface is neither 'UP' nor
'LINK', so that probably is a bug.

udev (hotplug) in Linux polls all the interfaces on a system and if the
LINK status changes from 0 to 1, it tries to bring that interface 'UP'
and get an address for it.  And the converse, with appropriate
de-bounce, when the LINK status goes from 1 to 0.  Unless you tell it
not to, of course.  So that may be something further that we want to
consider in regards to this question.


In the case of n Thu, 7 Feb 2008 13:00:41 -0800 "Charissa Willard"
<charissa.willard@onstor.com> wrote:

> Tim,
> 
> I believe the state should be persistent, too. One bug related to this
> issue is TED00018877 (The second SSC interface sc2 is showing
> Operation column "up" with out connecting cable.)
> 
> -Charissa
> 
> _____________________________________________
> From: Tim Gardner 
> Sent: Thursday, February 07, 2008 12:25 PM
> To: dl-Design Review
> Subject: sc interface state
> 
> The 'interface modify <name> -s enable' and 'interface modify <name>
> -s disable'
> commands are currently used to enable/disable sc and fp network
> interfaces.
> However, the state of the sc interfaces is not currently persistent.
> If you disable an sc interface and
> then reboot, the interface will be always be configured up if there is
> an IP address configured.
> 
> Is this the desired behavior or is this a defect?
> 
> I believe that the state should be persistent as it is for the fp
> interfaces.
> Unless I hear otherwise, I am going to change this as part of another
> sc interface defect I am working on.
> 
> Tim
> 
