On 25 Aug., 09:55, Michael Wolf <[email protected]> wrote:
> On 25 Aug., 02:14, Mike Christie <[email protected]> wrote:
>
>
>
>
>
> > On 08/24/2010 10:13 AM, Michael Wolf wrote:
>
> > > Hi ALL,
>
> > > I try to set up oracle cluster with four nodes (DELL R610) and
> > > EqualLogig PS6000.
> > > Servers has four Broadcom 5709C dual network cards, two intenal, two
> > > PCI cards.
> > > I`m trying to get the bnx2i driver to work using iSCSI offload for
> > > four channels.
> > > I can't get it to work, getting error
> > > iscsiadm: Could not login to [iface: bnx2i.00:22:19:68:3a:04, target:
> > > iqn.2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc63f-a1test,
> > > portal: 10.10.77.10,3260):
> > > iscsiadm: initiator reported error (4 - encountered connection
> > > failure)
>
> > > Showing nothing in /var/log/messages and no events on the EQ box.
>
> > So there is no iferror error in messages or nothing from iscsid?
>
> > > DELL suport team is not shure if bnx2i driver will work with RHEL 5.5,
> > > they ask me to reinstall RHEL 5.2, from my opinion is that not an
> > > option.
> > > I am using RHEL 5.5, oracle linux, kernel 2.6.18-194.11.1.0.1.el5 on
>
> > Is that a oracle linux kernel or the rhel 5.5 one? Are you running rhel
> > 5.5 in a oracle linux vm?
>
> > > x86_64
> > > iscsi-initiator-utils-6.2.0.871-0.16.el5
>
> > Also you need the updated iscsi
> > utils.http://people.redhat.com/mchristi/iscsi/rhel5.6/iscsi-initiator-utils/
>
> > > All firmware of the R610 is up to date
>
> > > All interfaces are shown as bnx2i
> > > [r...@ora-db-rac1-04 ~]# scsiadm -m iface
> > > -bash: scsiadm: command not found
> > > [r...@ora-db-rac1-04 ~]# iscsiadm -m iface
> > > default tcp,<empty>,<empty>,<empty>,<empty>
> > > iser iser,<empty>,<empty>,<empty>,<empty>
> > > bnx2i.00:22:19:68:3a:04 bnx2i,00:22:19:68:3a:
> > > 04,10.10.77.69,<empty>,<empty>
>
> > Are these IPs on the same subnet as the network port they are attached to?
>
> > > bnx2i.00:22:19:68:3a:0a bnx2i,00:22:19:68:3a:0a,
> > > 10.10.77.68,<empty>,<empty>
> > > bnx2i.00:00:00:00:00:00 bnx2i,
> > > 00:00:00:00:00:00,<empty>,<empty>,<empty>
> > > bnx2i.00:22:19:68:3a:06 bnx2i,00:22:19:68:3a:
> > > 06,10.10.77.67,<empty>,<empty>
> > > bnx2i.00:10:18:64:2e:5b bnx2i,00:10:18:64:2e:5b,
> > > 10.10.77.66,<empty>,<empty>
> > > bnx2i.00:10:18:64:98:bb bnx2i,00:10:18:64:98:bb,
> > > 10.10.77.65,<empty>,<empty>
> > > bnx2i.00:22:19:68:3a:08 bnx2i,00:22:19:68:3a:
> > > 08,10.10.77.64,<empty>,<empty>
> > > bnx2i.00:10:18:64:98:b9 bnx2i,
> > > 00:10:18:64:98:b9,10.10.77.63,<empty>,<empty>
>
> > > Only four of them are connected to the SAN. How to figure out which hw-
> > > adress belongs to which interface?
>
> > Start the iscsi service (or at least make sure bnx2i is loaded) then run:
>
> > [r...@meanminna kernel]# iscsiadm -m host -P 1
> > Host Number: 8
> > State: running
> > Transport: bnx2i
> > Initiatorname: <empty>
> > IPaddress: <empty>
> > HWaddress: 00:10:18:15:fd:f1
> > Netdev: eth1
>
> > You can see the network device the iscsi offload interface is attached
> > to (in this case eth1), and you can see the MAC/hwaddress for the iscsi
> > interface.
>
> > > Is bnx2i driver supported for RHEL5.5?
>
> > Yes.
>
> > > Is there a more detailed description for setting up such an
> > > environment as the RedHat manuals?
>
> > Section 5.1.2 Setting up a iface for a iSCSI offload card of the iscsi
> > readme in /usr/share/docs/iscsi-initiator-utils-$VERSION/README- Zitierten
> > Text ausblenden -
>
> > - Zitierten Text anzeigen -- Zitierten Text ausblenden -
>
> > - Zitierten Text anzeigen -
>
> Hi Mike,
>
> Trying to connect to the EQL box there are no messagese at all.
>
> On these oracle related boxes we use the oracle linux kernel. We do
> not use oracle linux vm.
> Are there any issues with this kernel and iscsi?
>
> I have downloaded the update and will install and test with this
> release, I will come back to you with the results.
>
> All storage IPs are on the same subnet 10.10.77.00. The EQL box
> listens to 10.10.77.10.
>
> Kind regards
> Michael- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -
With the new iscsi-initiator-utils set up, I now can connect to the
target.
I have set up two bnx2i ports with IP`s 63 and 64:
[r...@ora-db-rac1-04 ~]# iscsiadm -m iface
default tcp,<empty>,<empty>,<empty>,<empty>
iser iser,<empty>,<empty>,<empty>,<empty>
bnx2i.00:22:19:68:3a:04 bnx2i,00:22:19:68:3a:
04,<empty>,<empty>,<empty>
bnx2i.00:22:19:68:3a:0a bnx2i,00:22:19:68:3a:0a,
10.10.77.64,<empty>,<empty>
bnx2i.00:00:00:00:00:00 bnx2i,
00:00:00:00:00:00,<empty>,<empty>,<empty>
bnx2i.00:22:19:68:3a:06 bnx2i,00:22:19:68:3a:
06,<empty>,<empty>,<empty>
bnx2i.00:10:18:64:2e:5b bnx2i,00:10:18:64:2e:
5b,<empty>,<empty>,<empty>
bnx2i.00:10:18:64:98:bb bnx2i,
00:10:18:64:98:bb,<empty>,<empty>,<empty>
bnx2i.00:22:19:68:3a:08 bnx2i,00:22:19:68:3a:
08,10.10.77.63,<empty>,<empty>
bnx2i.00:10:18:64:98:b9 bnx2i,
00:10:18:64:98:b9,<empty>,<empty>,<empty>
I have done a discovery, finding two targets, my test target aitest
and the vss-Control target from the EQL box.
[r...@ora-db-rac1-04 ~]# iscsiadm -m discovery -t st -p
10.10.77.10:3260 -I bnx2i.00:22:19:68:3a:08 -P 1
Target: iqn.2001-05.com.equallogic:0-8a0906-68d84cc03-cbc00013c9149355-
vss-control
Portal: 10.10.77.10:3260,1
Iface Name: bnx2i.00:22:19:68:3a:08
Target: iqn.2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc4c63f-
a1test
Portal: 10.10.77.10:3260,1
Iface Name: bnx2i.00:22:19:68:3a:08
Now connecting to the test target:
[r...@ora-db-rac1-04 ~]# iscsiadm -m node -T iqn.
2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc4c63f-a1test -p
10.10.77.10:3260 -I bnx2i.00:22:19:68:3a:08 -l
Logging in to [iface: bnx2i.00:22:19:68:3a:08, target: iqn.
2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc4c63f-a1test,
portal: 10.10.77.10,3260]
Login to [iface: bnx2i.00:22:19:68:3a:08, target: iqn.
2001-05.com.equallogic:0-8a0906-76c630e04-e0492d35ddc4c63f-a1test,
portal: 10.10.77.10,3260]: successful
Everything is lookingfine, but there are a lot of failures in /var/log/
messages:
Aug 25 12:03:56 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:03:57 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:03:57 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:03:58 ora-db-rac1-04 kernel: connection4:0: bnx2i: conn
update - MBL 0x40000 FBL 0x10000MRDSL_I 0x40000 MRDSL_T 0x10000
Aug 25 12:03:58 ora-db-rac1-04 kernel: Vendor: EQLOGIC Model:
100E-00 Rev: 4.2
Aug 25 12:03:58 ora-db-rac1-04 kernel: Type: Direct-
Access ANSI SCSI revision: 05
Aug 25 12:03:58 ora-db-rac1-04 kernel: SCSI device sdb: 215040 512-
byte hdwr sectors (110 MB)
Aug 25 12:03:58 ora-db-rac1-04 kernel: sdb: Write Protect is off
Aug 25 12:03:58 ora-db-rac1-04 kernel: SCSI device sdb: drive cache:
write through
Aug 25 12:03:58 ora-db-rac1-04 kernel: SCSI device sdb: 215040 512-
byte hdwr sectors (110 MB)
Aug 25 12:03:58 ora-db-rac1-04 kernel: sdb: Write Protect is off
Aug 25 12:03:58 ora-db-rac1-04 kernel: SCSI device sdb: drive cache:
write through
Aug 25 12:03:58 ora-db-rac1-04 kernel: sdb: unknown partition table
Aug 25 12:03:58 ora-db-rac1-04 kernel: sd 8:0:0:0: Attached scsi disk
sdb
Aug 25 12:03:58 ora-db-rac1-04 multipathd: sdb: add path (uevent)
Aug 25 12:03:58 ora-db-rac1-04 kernel: sd 8:0:0:0: Attached scsi
generic sg3 type 0
Aug 25 12:03:58 ora-db-rac1-04 iscsid: connection4:0 is operational
now
Aug 25 12:03:58 ora-db-rac1-04 iscsid: Could not write to /sys/bus/
scsi/devices/8:0:0:0/queue_depth. Invalid permissions.
Aug 25 12:03:58 ora-db-rac1-04 iscsid: Could not queue depth for LUN 0
err 13.
Aug 25 12:04:58 ora-db-rac1-04 multipathd: sdb: failed to get path uid
Aug 25 12:04:58 ora-db-rac1-04 multipathd: uevent trigger error
Aug 25 12:05:11 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:05:11 ora-db-rac1-04 iscsid: Kernel reported iSCSI
connection 4:0 error (1011) state (3)
Aug 25 12:05:13 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:05:14 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:05:14 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:05:14 ora-db-rac1-04 iscsid: Kernel reported iSCSI
connection 4:0 error (1011) state (1)
Aug 25 12:05:14 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:05:15 ora-db-rac1-04 kernel: connection4:0: bnx2i: conn
update - MBL 0x40000 FBL 0x10000MRDSL_I 0x40000 MRDSL_T 0x10000
Aug 25 12:05:15 ora-db-rac1-04 kernel: session4: target reset
succeeded
Aug 25 12:05:15 ora-db-rac1-04 iscsid: connection4:0 is operational
after recovery (1 attempts)
Aug 25 12:06:26 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:06:27 ora-db-rac1-04 iscsid: Kernel reported iSCSI
connection 4:0 error (1011) state (3)
Aug 25 12:06:29 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:06:30 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:06:30 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:06:31 ora-db-rac1-04 kernel: connection4:0: bnx2i: conn
update - MBL 0x40000 FBL 0x10000MRDSL_I 0x40000 MRDSL_T 0x10000
Aug 25 12:06:31 ora-db-rac1-04 iscsid: connection4:0 is operational
after recovery (1 attempts)
Aug 25 12:06:51 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:06:51 ora-db-rac1-04 iscsid: Kernel reported iSCSI
connection 4:0 error (1011) state (3)
Aug 25 12:06:53 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:06:53 ora-db-rac1-04 kernel: connection4:0: detected conn
error (1011)
Aug 25 12:06:54 ora-db-rac1-04 kernel: bnx2i [02:00.00]: ISCSI_INIT
passed
Aug 25 12:06:54 ora-db-rac1-04 kernel: connection4:0: bnx2i: conn
update - MBL 0x40000 FBL 0x10000MRDSL_I 0x40000 MRDSL_T 0x10000
Aug 25 12:06:54 ora-db-rac1-04 kernel: session4: target reset
succeeded
Aug 25 12:06:55 ora-db-rac1-04 iscsid: connection4:0 is operational
after recovery (1 attempts)
Aug 25 12:07:49 ora-db-rac1-04 kernel: INFO: task vol_id:5911 blocked
for more than 120 seconds.
Aug 25 12:07:49 ora-db-rac1-04 kernel: "echo 0 > /proc/sys/kernel/
hung_task_timeout_secs" disables this message.
Aug 25 12:07:49 ora-db-rac1-04 kernel: vol_id D
ffffffff80150989 0 5911 1 5523 (NOTLB)
Aug 25 12:07:49 ora-db-rac1-04 kernel: ffff810614ef7c08
0000000000000082 ffff8106295c4e00 0000000000000018
Aug 25 12:07:49 ora-db-rac1-04 kernel: 0000000000000056
0000000000000006 ffff810619f5c820 ffffffff80309b60
Aug 25 12:07:49 ora-db-rac1-04 kernel: 0000033c75c6b1de
00000000000089a1 ffff810619f5ca08 0000000000000000
Aug 25 12:07:49 ora-db-rac1-04 kernel: Call Trace:
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8006e1f7>]
do_gettimeofday+0x40/0x90
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff800289e0>] sync_page
+0x0/0x43
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff800637ea>]
io_schedule+0x3f/0x67
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff80028a1e>] sync_page
+0x3e/0x43
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8006392e>]
__wait_on_bit_lock+0x36/0x66
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8003fbc5>]
__lock_page+0x5e/0x64
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff800a0a5d>]
wake_bit_function+0x0/0x23
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8000c2e4>]
do_generic_mapping_read+0x1df/0x359
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8000d0fd>]
file_read_actor+0x0/0x159
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8000c5aa>]
__generic_file_aio_read+0x14c/0x198
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff800c67cb>]
generic_file_read+0xac/0xc5
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff800a0a2f>]
autoremove_wake_function+0x0/0x2e
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff800b765c>]
audit_syscall_entry+0x180/0x1b3
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8000b69a>] vfs_read
+0xcb/0x171
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff80011bb3>] sys_read
+0x45/0x6e
Aug 25 12:07:49 ora-db-rac1-04 kernel: [<ffffffff8005d28d>] tracesys
+0xd5/0xe0
Aug 25 12:07:49 ora-db-rac1-04 kernel:
[r...@ora-db-rac1-04 ~]#
Any idea?
Regards Michael
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
