iscsi Initiator failure

[i_saad]

Can anyone assist in interpreting the message below. Trying to connect a Windows 2003 Client to an IBM Shark system.

Initiator is always showing that a login has failed.

2006 Feb 5 05:25:21 s-do-ra-43-op-4 %IPS-5-ISCSI_SESSION_CREATE_FAILURE: port-

channel 6: iSCSI Session initiator

iqn.1987-05.com.cisco:02.eaa0467647a0.itdtest

win2003 target iqn.1992-08.com.ibm.ess1-da1c2lba1v5 create failed. All configure

d pwwn in use.

[tblancha]

What SANOS are you running? This might be a software defect

[i_saad]

s-do-ra-43-op-4# sh version

Cisco Storage Area Networking Operating System (SAN-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (c) 2002-2004, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 1.0.8

loader: version 1.2(2)

kickstart: version 1.3(6)

system: version 1.3(6)

BIOS compile time: 08/07/03

kickstart image file is: bootflash:/m9500-sf1ek9-kickstart-mz.1.3.6.bin

kickstart compile time: 10/27/2004 12:00:00

system image file is: bootflash:/m9500-sf1ek9-mz.1.3.6.bin

system compile time: 10/27/2004 12:00:00

Hardware

RAM 1024592 kB

bootflash: 500736 blocks (block size 512b)

slot0: 1001952 blocks (block size 512b)

s-do-ra-43-op-4 uptime is 79 days 15 hours 32 minute(s) 50 second(s)

Last reset

Reason: Unknown

System version: 1.3(6)

Service:

[inch]

Gday,

how many iscsi initiators have you got configured?

Cheers

Andrew

[i_saad]

I only have one iscsi initiator:

iscsi initiator ip-address 172.16.200.42

static nWWN 26:01:00:0d:ec:09:6c:02

static pWWN 26:05:00:0d:ec:09:6c:02

vsan 3

Establishing the TCP/IP session is successful via a Port Channel of two Gigabit ports, but acquiring the target is the problem.

Cheers...

[inch]

Howdy,

I had this happen a while ago. It was because I assigned the pwwn myself without using the auto-generated ones and then I had a another initiator pinch the pwwn that I manually assigned.

The fix was to remove the manual generated one. But seeing how you only have one configured is a bit odd!

Can you...

switch# sh iscsi session

switch# sh iscsi virtual-target configured

switch# sh iscsi initiator detail

Cheers

Andrew

[i_saad]

I've taken the decision to move to latest release 2.1.2d so as to clear any suspicion. I've done the upgrade yesterday. I'll test again tomorrow. The new interfaces of Dev & Fab managers are much much improved ones.

I should know the outcome within couple days and will post results...

cheers....

[inch]

Howdy,

It might be worth removing the current initiator config and adding it again. Make sure you static assign your nwwn/pwwn using the system's pool.

eg.

switch(config)# iscsi initiator ip-address [ip here]

switch(config)# static pwwn system-assign

Then all you need to do is zone in your shark's adaptor/port and lun mask your new iscsi initiator.

I have been using the IPS modules with the ESS's since the IPS-8 was released without any issues. You can setup the initiator on two vsan's and then use SDD to multipath your luns. It works a treat on Windows, Linux and Solaris.

Cheers

[jejoseph]

You might run into this issue, if you have

same initiator coming in twice thro' two different

iscsi portals.

gig 1/1 -- 172.16.34.100

gig 1/2 --- 172.16.34.101

if you define iscsi initiator with one pwwn and

one nwwn, and use both the portals, then

you might run into same issue.

so if you plan to use both the portals, then

use two pwwns instead of one pwwn when configuring

iscsi initiator.