AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070805183053.2e33d9fe@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<tim.gardner@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E04DF9F2A@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Sun, 5 Aug 2007 18:31:48 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>
Subject: Re: network issues
Message-ID: <20070805183148.40f76748@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E04DF9F2A@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E04DF9F2A@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=UTF-8
Content-Transfer-Encoding: quoted-printable

I take it that this is your normal filer.  Shouldn't the IP address be
10.3.something?  Anyway it is probably some bug in the driver or the
PCI setup.  I got a similar thing when trying to use the second port on
the broken filer I have.

a

On Sun, 5 Aug 2007 17:26:56 -0700 "Tim Gardner"
<tim.gardner@onstor.com> wrote:

> I need some help bringing up the second SSC network interface.
>=20
> When I configure the interface the following messages are repeatedly
> output: =EF=BB=BFeng70:/etc# ifconfig eth1 up
> eth1: reset did not complete in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: link up.
> eth1: Setting full-duplex based on negotiated link capability.
> eng70:/etc# eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
>=20
> The interesting thing is that even when the interface is down, I am
> able to access the filer via ping and ssh using the IP address
> configured on the second interface.
>=20
> =EF=BB=BFeng70:/etc# ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:07:34:02:25:00
>           inet addr:10.2.1.23  Bcast:10.2.255.255  Mask:255.255.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:33737712 errors:0 dropped:19286 overruns:0
> frame:0 TX packets:32841669 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:2924743710 (2.7 GiB)  TX bytes:2243923924 (2.0 GiB)
>           Interrupt:8
>=20
> eng70:/etc# ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:07:34:02:25:01
>           inet addr:10.2.1.25  Bcast:10.2.255.255  Mask:255.255.0.0
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:4294967277 overruns:0
> frame:4294967277 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:9 Base address:0x1000
>=20
> I am able to access the filer using both 10.2.1.23 and 10.2.1.25 even
> though eth1 is not up.=20
