* RE: Possible bug in fusion mpt OR qlogic ip support
[not found] <53CF1076699CD711B7DD0002A51363F10190322B@exw-ks.ks.lsil.com>
@ 2003-12-17 17:58 ` Mario Giammarco
0 siblings, 0 replies; only message in thread
From: Mario Giammarco @ 2003-12-17 17:58 UTC (permalink / raw)
To: Stephens, Larry; +Cc: linux-scsi, Moore, Eric Dean, support
Il mer, 2003-12-17 alle 16:16, Stephens, Larry ha scritto:
> The suggestion is to utilize a board with the LSI 919 or 919X chip
> instead of the board with the 909 chip.
>
> I did send this message to the LSI Fibre Channel developers and here
> are their responses:
>
>
> ditto... support for the 40909 was discontinued about 3 months ago.
>
>
> We haven't supported the '909 in a LOOOONG time. I wouldn't know what
> to say even if I knew what rev. of firmware they were using.
>
> I would recommend they upgrade to at least 919, probably 919x if they
> want support of any kind.
>
>
Thank you for your precious suggestion but, after looking in your kernel
code, I have found a QLOGIC_NAA_WORKAROUND.
I have defined it and recompiled the kernel, now it works better, it
seems that at least arp goes well this time.
So the problem is not due to my "unsupported" 40909, but is common to
all lsi logic controllers and perhaps is connected to a bug in qlogic
code, so I forward this email also to qlogic support.
> -----Original Message-----
> From: Mario Giammarco [mailto:mgiammarco@virgilio.it]
> Sent: Wednesday, December 17, 2003 4:36 AM
> To: linux-scsi@vger.kernel.org; emoore@lsil.com; lstephen@lsil.com
> Subject: Possible bug in fusion mpt ip support
>
>
> Hello,
>
> I have two computers:
>
> cala IP 10.0.1.1 HW 00:E0:8B:02:96:DC HBA qlogic 2200
> server IP 10.0.1.10 HW 00:E0:3C:D0:12:89 HBA lsi logic 40909
>
> I cannot make them communicate.
>
> Route hardware etc. is all ok.
>
> I used tcpdump utility to debug.
>
> When I do ping from cala to server I obtain:
>
> on cala:
>
> 13:26:35.801540 arp who-has 10.0.1.10 tell 10.0.1.1
> 0001 0800 0604 0001 00e0 8b02 96dc 0a00
> 0101 0000 0000 0000 0a00 010a
> 13:26:36.800519 arp who-has 10.0.1.10 tell 10.0.1.1
> 0001 0800 0604 0001 00e0 8b02 96dc 0a00
> 0101 0000 0000 0000 0a00 010a
> 13:26:37.800288 arp who-has 10.0.1.10 tell 10.0.1.1
> 0001 0800 0604 0001 00e0 8b02 96dc 0a00
> 0101 0000 0000 0000 0a00 010a
> 13:26:38.903212 arp who-has 10.0.1.10 tell 10.0.1.1
> 0001 0800 0604 0001 00e0 8b02 96dc 0a00
> 0101 0000 0000 0000 0a00 010a
>
> on server:
>
> 13:20:02.037848 21:0:0:e0:8b:2 Broadcast 52:
> 96dc aaaa 0300 0000 0806 0001 0800 0604
> 0001 00e0 8b02 96dc 0a00 0101 0000 0000
> 0000 0a00 010a
> 13:20:02.037899 3c:d0:12:89:aa:aa 8b:2:96:dc:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0002 00e0
> 3cd0 1289 0a00 010a 00e0 8b02 96dc 0a00
> 0101
> 13:20:03.036611 21:0:0:e0:8b:2 Broadcast 52:
> 96dc aaaa 0300 0000 0806 0001 0800 0604
> 0001 00e0 8b02 96dc 0a00 0101 0000 0000
> 0000 0a00 010a
> 13:20:03.036656 3c:d0:12:89:aa:aa 8b:2:96:dc:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0002 00e0
> 3cd0 1289 0a00 010a 00e0 8b02 96dc 0a00
> 0101
> 13:20:04.036242 21:0:0:e0:8b:2 Broadcast 52:
> 96dc aaaa 0300 0000 0806 0001 0800 0604
> 0001 00e0 8b02 96dc 0a00 0101 0000 0000
> 0000 0a00 010a
> 13:20:04.036284 3c:d0:12:89:aa:aa 8b:2:96:dc:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0002 00e0
> 3cd0 1289 0a00 010a 00e0 8b02 96dc 0a00
> 0101
>
> This shows that cala do not start to send ping packets because it
> cannot
> resolve arp.
> On server it seems that hardware addresses are mangled.
>
> When I do ping from server to cala I obtain:
>
> on cala:
>
> NOTHING AT ALL
>
> on server:
>
> 13:22:39.355118 3c:d0:12:89:aa:aa ff:ff:ff:ff:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0001 00e0
> 3cd0 1289 0a00 010a 0000 0000 0000 0a00
> 0101
> 13:22:40.353542 3c:d0:12:89:aa:aa ff:ff:ff:ff:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0001 00e0
> 3cd0 1289 0a00 010a 0000 0000 0000 0a00
> 0101
> 13:22:41.353547 3c:d0:12:89:aa:aa ff:ff:ff:ff:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0001 00e0
> 3cd0 1289 0a00 010a 0000 0000 0000 0a00
> 0101
> 13:22:42.357615 3c:d0:12:89:aa:aa ff:ff:ff:ff:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0001 00e0
> 3cd0 1289 0a00 010a 0000 0000 0000 0a00
> 0101
> 13:22:43.356049 3c:d0:12:89:aa:aa ff:ff:ff:ff:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0001 00e0
> 3cd0 1289 0a00 010a 0000 0000 0000 0a00
> 0101
> 13:22:44.356044 3c:d0:12:89:aa:aa ff:ff:ff:ff:0:e0 48:
> 0300 0000 0806 0006 0800 0604 0001 00e0
> 3cd0 1289 0a00 010a 0000 0000 0000 0a00
> 0101
>
> So it seems that cala arp info is sent good.
> Because cala do not receive anything it seems that is fusion mpt that
> mangles hw addresses so the destination of packets is not cala
> anymore.
>
>
> Please help me!
>
> Thanks in advance for interest!
>
> --
> Mario Giammarco
--
Mario Giammarco
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-12-17 17:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <53CF1076699CD711B7DD0002A51363F10190322B@exw-ks.ks.lsil.com>
2003-12-17 17:58 ` Possible bug in fusion mpt OR qlogic ip support Mario Giammarco
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox