San Tape Device not seen

[UVK_1]

Mark,

Once the SAN team says that they have did their mapping after you sending the WWN's from to them, I would only do what you have already tried like insf and ioscan.

If you are local to server check and see if you have activity on FC's, I would also check for activity on the SAN switch. If no activity you might want to suspect a bad fiber.

I had run into similar kind of problem with storage LUN where SAN team always kept on saying that they see the luns visisble but after 24 hrs when I pushed it hard they finally came back to saying there was bad gbit card on the storage box.

Try this I hope you might get lucky.

-uvk

[Mark Trux]

Here is what I see on the server.
I have re-enabled legacy file systems

disk 2 0/2/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072BB975
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s3
/dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0s1
disk 0 0/2/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072BB975
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 1 0/2/1/0.0.0.2.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 11 0/4/0/0/0/0.2.0.47.0.0.0 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 12 0/4/0/0/0/0.2.0.51.0.0.0 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 13 0/5/0/0/0/0.101.0.49.0.0.0 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 14 0/5/0/0/0/0.101.0.53.0.0.0 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
=================
Vendor ID is = 0x10df
Device ID is = 0xfe00
PCI Sub-system Vendor ID is = 0x103c
PCI Sub-system ID is = 0x1708
Chip version = 2
Firmware Version = 2.72A2 SLI-3 (Z3F2.72A2)
EFI Version = ZU6.00A5
EFI Boot = ENABLED
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0x200100
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x20000000c98030f2
N_Port Port World Wide Name = 0x10000000c98030f2
Switch Port World Wide Name = 0x2016000decad0080
Switch Node World Wide Name = 0x2066000dec2ca501
Driver state = ONLINE
Hardware Path is = 0/4/0/0/0/0
Maximum Frame Size = 2048
Driver Version = @(#) FCLP: PCIe Fibre Channel driver (FibrChanl-02), B.11.31.0809, Jun 27 2008, FCLP_IFC (3,2)



Vendor ID is = 0x10df
Device ID is = 0xfe00
PCI Sub-system Vendor ID is = 0x103c
PCI Sub-system ID is = 0x1708
Chip version = 2
Firmware Version = 2.72A2 SLI-3 (Z3F2.72A2)
EFI Version = ZU6.00A5
EFI Boot = ENABLED
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0xec0000
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x20000000c98030f3
N_Port Port World Wide Name = 0x10000000c98030f3
Switch Port World Wide Name = 0x2016000decacf480
Switch Node World Wide Name = 0x20a2000dec2cd1c1
Driver state = ONLINE
Hardware Path is = 0/4/0/0/0/1
Maximum Frame Size = 2048
Driver Version = @(#) FCLP: PCIe Fibre Channel driver (FibrChanl-02), B.11.31.0809, Jun 27 2008, FCLP_IFC (3,2)



Vendor ID is = 0x10df
Device ID is = 0xfe00
PCI Sub-system Vendor ID is = 0x103c
PCI Sub-system ID is = 0x1708
Chip version = 2
Firmware Version = 2.72A2 SLI-3 (Z3F2.72A2)
EFI Version = ZU6.00A5
EFI Boot = ENABLED
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0xb20100
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x20000000c9805906
N_Port Port World Wide Name = 0x10000000c9805906
Switch Port World Wide Name = 0x2015000decacef80
Switch Node World Wide Name = 0x2065000dec2cd541
Driver state = ONLINE
Hardware Path is = 0/5/0/0/0/0
Maximum Frame Size = 2048
Driver Version = @(#) FCLP: PCIe Fibre Channel driver (FibrChanl-02), B.11.31.0809, Jun 27 2008, FCLP_IFC (3,2)



Vendor ID is = 0x10df
Device ID is = 0xfe00
PCI Sub-system Vendor ID is = 0x103c
PCI Sub-system ID is = 0x1708
Chip version = 2
Firmware Version = 2.72A2 SLI-3 (Z3F2.72A2)
EFI Version = ZU6.00A5
EFI Boot = ENABLED
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0x340000
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x20000000c9805907
N_Port Port World Wide Name = 0x10000000c9805907
Switch Port World Wide Name = 0x2015000deca78940
Switch Node World Wide Name = 0x20a1000dec2cd541
Driver state = ONLINE
Hardware Path is = 0/5/0/0/0/1
Maximum Frame Size = 2048
Driver Version = @(#) FCLP: PCIe Fibre Channel driver (FibrChanl-02), B.11.31.0809, Jun 27 2008, FCLP_IFC (3,2)
=======================
LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk3

Total number of LUN paths = 1
World Wide Identifier(WWID) = 0x600508e0000000008b0ac3e4c3353c05

LUN path : lunpath0
Class = lunpath
Instance = 0
Hardware path = 0/2/1/0.0x53c35c3e4c30a8b.0x0
SCSI transport protocol = sas
State = UNOPEN
Last Open or Close state = ACTIVE


LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk4

Total number of LUN paths = 1
World Wide Identifier(WWID) = 0x5000c5000b9f24b3

LUN path : lunpath1
Class = lunpath
Instance = 1
Hardware path = 0/2/1/0.0x5000c5000b9f24b1.0x0
SCSI transport protocol = sas
State = UNOPEN
Last Open or Close state = ACTIVE


LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk5

Total number of LUN paths = 1
World Wide Identifier(WWID) = 0x5000c5000b9f570f

LUN path : lunpath2
Class = lunpath
Instance = 2
Hardware path = 0/2/1/0.0x5000c5000b9f570d.0x0
SCSI transport protocol = sas
State = ACTIVE
Last Open or Close state = ACTIVE


LUN PATH INFORMATION FOR LUN : /dev/pt/pt2

Total number of LUN paths = 4
World Wide Identifier(WWID) = 0x60060e800547f500000047f5000000df

LUN path : lunpath27
Class = lunpath
Instance = 27
Hardware path = 0/4/0/0/0/0.0x50060e800547f510.0x0
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath28
Class = lunpath
Instance = 28
Hardware path = 0/4/0/0/0/0.0x50060e800547f520.0x0
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath31
Class = lunpath
Instance = 31
Hardware path = 0/5/0/0/0/0.0x50060e800547f500.0x0
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE

LUN path : lunpath32
Class = lunpath
Instance = 32
Hardware path = 0/5/0/0/0/0.0x50060e800547f530.0x0
SCSI transport protocol = fibre_channel
State = UNOPEN
Last Open or Close state = ACTIVE


LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk10

Total number of LUN paths = 4
World Wide Identifier(WWID) = 0x60060e800547f500000047f5000000df

LUN path : lunpath29
Class = lunpath
Instance = 29
Hardware path = 0/4/0/0/0/0.0x50060e800547f510.0x400000000000000
0
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

LUN path : lunpath30
Class = lunpath
Instance = 30
Hardware path = 0/4/0/0/0/0.0x50060e800547f520.0x400000000000000
0
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

LUN path : lunpath33
Class = lunpath
Instance = 33
Hardware path = 0/5/0/0/0/0.0x50060e800547f500.0x400000000000000
0
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

LUN path : lunpath34
Class = lunpath
Instance = 34
Hardware path = 0/5/0/0/0/0.0x50060e800547f530.0x400000000000000
0
SCSI transport protocol = fibre_channel
State = ACTIVE
Last Open or Close state = ACTIVE

[Torsten.]

Telnet to the library and check

/show/interface>access all

or use commandview tl.


Why you post so many disk related info, e.g. from ioscan?

[Mark Trux]

I posted the disk to show that the FC cards were working.

[Torsten.]

Regarding the login see

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=115&prodSeriesId=438305&prodTypeId=18964&objectID=c00040002

[Mark Trux]

Great doc. I am awaiting them to send me the IP of the TL

[Mark Trux]

Well, the SAN people say it is my problem, the people who set up the Tape Library say it is my problem and they will not give me the telnet address to the TL.

Any other suggestions?

[Torsten. · Accepted solution]

The only point you are obviously responsible for is to make sure the driver is installed; all other things are related to SAN and library.

Let them check the switch if both is visible (server and library), if zoning is configured and activated (!!) and finally if the library really allows the server to connect.

There is nothing you can do on the server ...

[Mark Trux]

OK
I am just making sure all my bases are covered.
I will keep the thread open. If they find the fix I will post.

Thanks all....

[Torsten.]

For your reference:

http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=438305&targetPage=http%3A%2F%2Fbizsupport1.austin.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00849929%2Fc00849929.pdf

at bottom of this page

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=-1&contentType=SupportManual&docIndexId=64255&prodTypeId=18964&prodSeriesId=438305

see the chapter

Conï¬ guring host HBA access with Secure Manager

IMHO there are 2 possible reasons:

- zoning not activated (this sometimes happens, you create a new zone, but forget to make it active ... ;-))

- presentation settings on the library