Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1117
Views
0
Helpful
9
Replies

SN5428 does not recognize Seagate ST39102FC JBOD

Alex1
Level 1
Level 1

‎09-03-2003 10:12 AM

When connected, displays (with logging on):

primaryPortLoginResp: PLOGI/PRLI failed status=0x6, loopId=0x81, portId=0x102e

1, plcPtr=0xd40aa88

Tried different FC port type settings (fl-port, gl-port, tl-port) with the same result.

What does the status=0x6 means? How to resolve the issue?

Thanks,

Alex

Labels:
0 Helpful
9 Replies 9

mrfrase
Level 1
Level 1

‎09-03-2003 06:59 PM

0x6 I believe is a Fibre Channel Timeout, disk is not responding

Have you tried placing the Drive in a diferent position in the JBOD?

Can you get a

Are there any other LUN's on the FC network?

0 Helpful

Alex1
Level 1
Level 1
In response to mrfrase

‎09-04-2003 11:23 AM

There are 4 drives. I tried to place one of the drives in all four available positions. Also tried with all 4 LUNs in place. The only difference was that sometimes I'd get status=0x4007 and other times status=0x6.

Invariably, displays zero luns (here is an output):

[cisco5428]# show debug rawlundatabase all

Raw Lun Data Base for Interface fci1

Entry Address = 0xca71cd4

fabricLoginFailureCode=0x0,fabricLoginExtendedCode=0x0,fabricLoginTimeoutCode=0x0

ReportLunsLLDStatus=0x0,ReportLunsLLDStatusModifier=0x0,ReportLunsSCSIStatus=0x0,ReportLunsASCASCQ=0x0,ReportLunsLu

nCount=0

InquiryLLDStatus=0x0,InquiryLLDStatusModifier=0x0,InquiryLastLunWithLLDError=0x0,

InquirySCSIStatus=0x0,InquiryASCASCQ=0x0,InquiryLastLunWithSCSIStatusError=0x0

boolLunsNotSupported=0x0,InquiryLastLunNotSupported=0x0

loopId=0x7e,masterState=0x6,slaveState=0x7,loggedIn=1,roles=0,valid=1,portId=0xfffffe,scanLuns=0x0

numberLuns=0x0,reportAsyncEvent=0x0,node_wwn=0x10000009 0x7c604b41, port_wwn=0x20000009 0x7c604b41

Raw Lun Data Base for Interface fci2

Entry Address = 0xcdddb1c

fabricLoginFailureCode=0x0,fabricLoginExtendedCode=0x0,fabricLoginTimeoutCode=0x0

ReportLunsLLDStatus=0x0,ReportLunsLLDStatusModifier=0x0,ReportLunsSCSIStatus=0x0,ReportLunsASCASCQ=0x0,ReportLunsLu

nCount=0

InquiryLLDStatus=0x0,InquiryLLDStatusModifier=0x0,InquiryLastLunWithLLDError=0x0,

InquirySCSIStatus=0x0,InquiryASCASCQ=0x0,InquiryLastLunWithSCSIStatusError=0x0

boolLunsNotSupported=0x0,InquiryLastLunNotSupported=0x0

loopId=0x7e,masterState=0x6,slaveState=0x7,loggedIn=1,roles=0,valid=1,portId=0xfffffe,scanLuns=0x0

numberLuns=0x0,reportAsyncEvent=0x0,node_wwn=0x10000009 0x7c604b41, port_wwn=0x200f0009 0x7c604b41

0 Helpful

mrfrase
Level 1
Level 1

‎09-04-2003 10:26 PM

Yes, this output shows the SN5428 internal initiators in the SN5428 doing a query to the name server data base at FE but there are no devices in the databases reported. Looks like the target devices(LUNS) are not doing a FLOGI to the fabric switch now. On the first message in this post shows we are trying to log into Domain 01, port 02, device e1, which is not now in the nameserver.

Little to go on right now, may need to open a TAC case to really dig into what's going on.

0 Helpful

dsicotte
Level 1
Level 1
In response to mrfrase

‎09-09-2003 02:06 PM

Right now Alex is using a "passive" SFP-to-Fibre-Channel cable specifically purchased to setup this test bed. We have also unsuccessfully tried to connect the following with the same results:

(1.) JMR Fibre-Channel-over-copper JBOD (4 disk)

This JBOD is an older unit from 1998 with 4 fibre channel disks inside. We connected to the SN5428 via a passive SFP-to-FC9-Fibre-Channel cable, using FC9 Fibre-Channel terminators to cap the open FC9 connectors. No luck with this configuration, no LUN's are visable.

(2.) Second thing we tried was to connect a single Seagate ST39102FC Fibre-Channel hard disk directly to the SN5428. The connection was made via the same passive SFP-FC9-Fibre-Channel cable and a small Fibre-Channel Adapter that plugs directly on to the disk to accept FC9 connectors (one FC9 in and one FC9 out, we have the "out" side terminated with a standard FC9 terminator. No luck with this configuration either, no LUN's are visable.

- I'm starting to think this SN5428 wants to talk to some Arry logic, and not dumb JBOD's or disks directly. Where are we going wrong? Should we be able to talk directly to a Seagate ST39102FC disk directly?

Thanks,

Dan

0 Helpful

mrfrase
Level 1
Level 1
In response to dsicotte

‎09-10-2003 05:55 AM

We have labs full of the JMR Fortra copper enclosures with the Seagate FC drives. I have used the FC to DB9 Media converters on the JBOD's but they are very flaky at times. We also have used the copper SFP's that will take a direct H2FC to DBM cable that goes to the JBOD. The JBOD and drives will show up as a NL device. The Seagate FC imbedded controller on the drives will FLOGI into the Domain server in the SN5428. will show registered drives. If they do not FLOGI the SN5428 can not make them do it, no FC switch can make it FLOGI. Once the Nameserver is populated with the FCID's and pWWN of the Disk Drives the internal HBA's in the SN5428 will get database change notification and PLOGI to the Disks. At that point on the SN5428 will show the devices the internal HBA's tables have learned about on the Switch Fabric. will show any attempt from the Seagate FC drives to FLOGI into the network? If not it is a cable or drive issue.

0 Helpful

Alex1
Level 1
Level 1
In response to mrfrase

‎09-11-2003 11:17 AM

This time we used Seagate ST39103FC, which shows up in the SN5428 compatibility matrix. The good news is that now we can see our drive in the fcswitch nameserver database:

0101e8 NL 1 21000020378707e4 00000000

At port 1, we see the wwpn of the drive.

It means FLOGI happened, and was sucessful. At this point we know it is not a cable issue.

But PLOGI still fails:

Jan 31 01:54:48: %FC-fci2-7-QPRBIOCB: plogiRsp: giving up! portId=0x101e8, wwpn=0x21000020378707e4, loginRetryCount=0x5, lldStatus=0x6, plc=0xcdd14b8

Jan 31 01:54:48: %FC-fci2-7-QPPLRPF: primaryPortLoginResp: PLOGI/PRLI failed status=0x6, loopId=0x81, portId=0x101e8, plcPtr=0xcdd14b8

As you can see, it is the same wwpn, so SN5428 was really trying (and failing with timeout) to contact our disk.

0 Helpful

mrfrase
Level 1
Level 1
In response to Alex1

‎09-11-2003 01:01 PM

do a and then run

Mail the results to mfrase@cisco.com

Thanks.

0 Helpful

Alex1
Level 1
Level 1
In response to mrfrase

‎09-11-2003 01:45 PM

Michael,

We definitely have some kind of configuration issue. I did as you said. Here's the printout:

*[cisco5428]# sh devices rediscover

Fibre channel discovery kicked off!

*[cisco5428]# Jan 31 04:18:38: %FC-fci2-7-QPRBIOCB: plogiRsp: giving up! portId=0x101e8, wwpn=0x21000020378707e4

, loginRetryCount=0x5, lldStatus=0x6, plc=0xcdd1430

Jan 31 04:18:38: %FC-fci2-7-QPPLRPF: primaryPortLoginResp: PLOGI/PRLI failed status=0x6, loopId=0x81, portId=0x1

01e8, plcPtr=0xcdd1430

Jan 31 04:18:38: %FC-fci1-7-QPRBIOCB: plogiRsp: giving up! portId=0x101e8, wwpn=0x21000020378707e4, loginRetryCo

unt=0x5, lldStatus=0x6, plc=0xca57f78

Jan 31 04:18:38: %FC-fci1-7-QPPLRPF: primaryPortLoginResp: PLOGI/PRLI failed status=0x6, loopId=0x81, portId=0x1

01e8, plcPtr=0xca57f78

*[cisco5428]# sh debug scsirouter all scsitrace

top 0x22130f8, bottom 0x221dfc0, current 0x22130f8, count 0x320

710: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

711: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

712: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

713: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

714: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

715: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

716: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

717: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

718: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

719: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

720: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

721: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

722: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

723: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

724: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

725: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

726: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

727: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

728: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

729: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

730: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

731: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

732: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

733: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

734: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

735: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

736: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

737: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

738: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

739: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

740: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

741: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

742: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

743: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

744: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

745: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

746: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

747: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

748: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

749: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

750: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

751: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

752: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

753: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

754: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

755: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

756: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

757: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

758: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

759: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

760: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

761: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

762: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

763: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

764: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

765: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

766: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

767: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

768: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

769: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

770: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

771: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

772: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

773: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

774: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

775: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

776: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

777: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

778: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

779: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

780: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

781: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

782: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

783: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

784: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

785: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

786: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

787: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

788: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

789: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

790: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

791: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

792: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

793: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

794: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

795: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

796: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

797: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

798: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

799: InttrID 0, TgtID 0, IF 0 VP 0, LUN 0, TmStmp 0x00000000

*[cisco5428]#

0 Helpful

mrfrase
Level 1
Level 1
In response to Alex1

‎09-11-2003 01:57 PM

OK, I'll need to go over the complete That you will need to email.

0 Helpful
Customers Also Viewed These Support Documents

Review Cisco Networking for a $25 gift card