Tape Drive Config Issue

[petemkuk]

I have a Solaris server running Solaris 10.
I have zoned 2 3592 tape drives to it via Brocade 48000 switch.
It has emulex cards: -

node instance wwpn type fware hardware path status use
======== ======== ================ =========== ======== =================================== ================== ========
bx953a emlxs 10000000c98214d3 LPe11000-M4 2.72a2 /dev/cfg/c3 online -
bx953a emlxs 10000000c98214b3 LPe11000-M4 2.72a2 /dev/cfg/c4 online -
bx953a qlc 2100001b328558bc 375-3355-02 4.04.01 /dev/cfg/c2 online -
bx953a qlc 2100001b32866719 375-3355-02 4.04.01 /dev/cfg/c1 online -

cfgadm -al>

Ap_Id Type Receptacle Occupant Condition
SB0 System_Brd connected configured ok
SB0::cpu0 cpu connected configured ok
SB0::cpu1 cpu connected configured ok
SB0::cpu2 cpu connected configured ok
SB0::cpu3 cpu connected configured ok
SB0::memory memory connected configured ok
SB0:ci0 io connected configured ok
SB0:ci1 io connected configured ok
SB0:ci2 io connected configured ok
SB0:ci3 io connected configured ok
SB0:ci8 io connected configured ok
SB1 disconnected unconfigured unknown
SB2 disconnected unconfigured unknown
SB3 disconnected unconfigured unknown
SB4 disconnected unconfigured unknown
SB5 disconnected unconfigured unknown
SB6 disconnected unconfigured unknown
SB7 disconnected unconfigured unknown
SB8 disconnected unconfigured unknown
SB9 disconnected unconfigured unknown
SB10 disconnected unconfigured unknown
SB11 disconnected unconfigured unknown
SB12 disconnected unconfigured unknown
SB13 disconnected unconfigured unknown
SB14 disconnected unconfigured unknown
SB15 disconnected unconfigured unknown
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 disk connected configured unknown
c0::dsk/c0t1d0 disk connected configured unknown
c1 fc-fabric connected configured unknown
c1::22540002ac000723 disk connected configured unknown
c1::22540002ac000726 disk connected configured unknown
c2 fc-fabric connected configured unknown
c2::23540002ac000723 disk connected configured unknown
c2::23540002ac000726 disk connected configured unknown
c3 fc-fabric connected unconfigured unknown
c4 fc-fabric connected unconfigured unknown
iou#1-pci#0 unknown empty unconfigured unknown
iou#1-pci#1 etherne/hp connected configured ok
iou#1-pci#2 fibre/hp connected configured ok
iou#1-pci#3 fibre/hp connected configured ok
iou#1-pci#4 pci-pci/hp connected configured ok
iou#1-pci#4:iobE04DP.pcie1 fibre/hp connected configured ok
iou#1-pci#4:iobE04DP.pcie2 etherne/hp connected configured ok
iou#1-pci#4:iobE04DP.pcie3 unknown empty unconfigured unknown
iou#1-pci#4:iobE04DP.pcie4 fibre/hp connected configured ok
iou#1-pci#4:iobE04DP.pcie5 unknown empty unconfigured unknown
iou#1-pci#4:iobE04DP.pcie6 unknown empty unconfigured unknown


System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M5000 Server
System clock frequency: 1012 MHz
Memory size: 32768 Megabytes

==================================== CPUs ====================================

CPU CPU Run L2$ CPU CPU
LSB Chip ID MHz MB Impl. Mask
--- ---- ---------------------------------------- ---- --- ----- ----
00 0 0, 1, 2, 3, 4, 5, 6, 7 2400 5.0 7 145
00 1 8, 9, 10, 11, 12, 13, 14, 15 2400 5.0 7 145
00 2 16, 17, 18, 19, 20, 21, 22, 23 2400 5.0 7 145
00 3 24, 25, 26, 27, 28, 29, 30, 31 2400 5.0 7 145

============================ Memory Configuration ============================

Memory Available Memory DIMM # of Mirror Interleave
LSB Group Size Status Size DIMMs Mode Factor
--- ------ ------------------ ------- ------ ----- ------- ----------
00 A 16384MB okay 2048MB 8 no 4-way
00 B 16384MB okay 2048MB 8 no 4-way

========================= IO Devices =========================

IO Lane/Frq

LSB Type LPID RvID,DvID,VnID BDF State Act, Max Name Mode
l
--- ----- ---- ------------------ --------- ----- ----------- ------------------------------ ----
----------------
Logical Path
------------
00 PCIe 0 bc, 8532, 10b5 2, 0, 0 okay 8, 8 pci-pciex10b5,8532 N/A

/pci@0,600000/pci@0


00 PCIe 0 bc, 8532, 10b5 3, 8, 0 okay 8, 8 pci-pciex10b5,8532 N/A

/pci@0,600000/pci@0/pci@8


00 PCIe 0 bc, 8532, 10b5 3, 9, 0 okay 4, 8 pci-pciex10b5,8532 N/A

/pci@0,600000/pci@0/pci@9


00 PCIx 0 8, 125, 1033 4, 0, 0 okay 100, 133 pci-pciexclass,060400 N/A

/pci@0,600000/pci@0/pci@8/pci@0


00 PCIx 0 8, 125, 1033 4, 0, 1 okay --, 133 pci-pciexclass,060400 N/A

/pci@0,600000/pci@0/pci@8/pci@0,1


00 PCI 0 2, 50, 1000 5, 1, 0 okay --, 133 scsi-pci1000,50 LSI
,1064
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1


00 PCI 0 10, 1648, 14e4 5, 2, 0 okay --, 133 network-pci14e4,1648 N/A

/pci@0,600000/pci@0/pci@8/pci@0/network@2


00 PCI 0 10, 1648, 14e4 5, 2, 1 okay --, 133 network-pci14e4,1648 N/A

/pci@0,600000/pci@0/pci@8/pci@0/network@2,1


00 PCIe 0 6, 105e, 8086 119, 0, 0 okay 4, 4 network-pciex8086,105e SUN
W,pcie-northstar
/pci@0,600000/pci@0/pci@9/network@0


00 PCIe 0 6, 105e, 8086 119, 0, 1 okay 4, 4 network-pciex8086,105e SUN
W,pcie-northstar
/pci@0,600000/pci@0/pci@9/network@0,1


00 PCIe 1 2, fe00, 10df 2, 0, 0 okay 4, 4 lpfc-pciex10df,fe00 LPe
11000-M4
/pci@1,700000/lpfc@0


00 PCIe 2 3, 2432, 1077 2, 0, 0 okay 4, 4 SUNW,qlc-pciex1077,2432 QLE
2460
/pci@2,600000/SUNW,qlc@0


00 PCIe 3 bc, 9020, 108e 2, 0, 0 okay 8, 8 pci-pciex108e,9020 N/A

/pci@3,700000/pci@0


00 PCIe 3 bc, 8532, 10b5 3, 1, 0 okay 8, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@1


00 PCIe 3 bc, 8532, 10b5 3, 9, 0 okay 8, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@9


00 PCIe 3 bc, 8532, 10b5 4, 0, 0 okay 8, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@1/pci@0


00 PCIe 3 bc, 8532, 10b5 5, 0, 0 okay 4, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@1/pci@0/pci@0


00 PCIe 3 bc, 8532, 10b5 5, 1, 0 okay 4, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@1/pci@0/pci@1


00 PCIe 3 bc, 8532, 10b5 5, 9, 0 okay 1, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@1/pci@0/pci@9


00 PCIe 3 3, 2432, 1077 6, 0, 0 okay 4, 4 SUNW,qlc-pciex1077,2432 QLE
2460
/pci@3,700000/pci@0/pci@1/pci@0/pci@0/SUNW,qlc@0


00 PCIe 3 6, 105e, 8086 44, 0, 0 okay 4, 4 network-pciex8086,105e SUN
W,pcie-northstar
/pci@3,700000/pci@0/pci@1/pci@0/pci@1/network@0


00 PCIe 3 6, 105e, 8086 44, 0, 1 okay 4, 4 network-pciex8086,105e SUN
W,pcie-northstar
/pci@3,700000/pci@0/pci@1/pci@0/pci@1/network@0,1


00 PCIe 3 bc, 8532, 10b5 120, 0, 0 okay 8, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@9/pci@0


00 PCIe 3 bc, 8532, 10b5 121, 0, 0 okay 4, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@9/pci@0/pci@0


00 PCIe 3 bc, 8532, 10b5 121, 1, 0 okay 1, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@9/pci@0/pci@1


00 PCIe 3 bc, 8532, 10b5 121, 9, 0 okay 1, 8 pci-pciex10b5,8532 N/A

/pci@3,700000/pci@0/pci@9/pci@0/pci@9


00 PCIe 3 2, fe00, 10df 122, 0, 0 okay 4, 4 lpfc-pciex10df,fe00 LPe
11000-M4
/pci@3,700000/pci@0/pci@9/pci@0/pci@0/lpfc@0



==================== Hardware Revisions ====================

System PROM revisions:
----------------------

OBP 4.24.10 2008/08/12 19:52


=================== Environmental Status ===================

Mode switch is in LOCK mode

=================== System Processor Mode ===================

SPARC64-VII mode


The st.conf is as follows: -

#
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#

#
#pragma ident "@(#)st.conf 1.34 04/06/24 SMI"
#

#
# The officially supported devices do not require a entry under
# tape-config-list as their configuration is built in to the driver.
#
#
# A non configured drive will say Unconfigured Drive: and have single quoted
# Vendor and Product strings displayed when it's status is checked with mt.
#
# mt -f /dev/rmt/# status
# Unconfigured Drive: Vendor 'VENDOR ' Product 'A Product ID '
# sense key(0x0)= No Additional Sense residual= 0 retries= 0
# file no= 0 block no= 0
#
# If your drive is displayed like this first check to see if a newer version
# of the st driver has added support for your drive.
#
# If your drive is not supported by Sun, check the drive manufacturer's
# documentation or web site for their recommended configuration strings.
#
# To configure a drive not supported by the driver, use the single quoted
# Vendor and Product strings to create a entry under tape-config-list.
#
# A starting point for your st.conf entry can be obtained by reading the
# current DEFAULT configuration from the driver using mt.
#
# mt -f /dev/rmt/# config
# "SONY SDX-700C", "SONY SDX-700C", "SONYSDX700C";
# SONYSDX700C = \
# 2,0x12,0,0x1865B,4,0x00,0x00,0x00,0x00,0,120,120,3600,3600,3600,3600,3600;
#
#
# Notes:
# Any spaces in the Vendor field must be kept so that it is 8
# characters long. Trailing spaces in the Product field can be removed.
#
# To add this configuration information, first uncomment the
# "tape-config-list=" line, and add the first configuration line
# immediately afterward. If there is more than one entry in the
# tape-config-list, all entries but the last must end with a comma.
# The last entry ends with a semicolon.
#
# See the driver.conf(4) man page for general information on the conf
# file format, and the st(7d) man page for information specific to st.conf.
#
# Example:
tape-config-list=
"IBM 03592E05", "IBM 3592E", "CLASS_3592E";
CLASS_3592E = 2,0x24,0,0x45963d,3,0x00,0x51,0x52,2,30,0,480,840,720,660,9060;
# "VENDOR A Product ID", "A Prettier Name to Display", "A-Config-Name",
# "VENDORB Other Product ID", "An Other Pretty Name", "Other-Config-Name";
#
# Then for each config-Name there must be a setup string that looks like this.
#
# A-Config-Name = \
# 2,0x34,0,0x18659,4,0x47,0x47,0x47,0x47,1,120,120,3600,3600,3600,3600,3600;
# Other-Config-Name = 1,0x3B,0,0x18659,4,0x40,0x40,0x40,0x40,3;
#
# For specific details for of values to use see the st(7D) man pages and
# drive vendor manuals.
#

name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=1 lun=1;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=2 lun=1;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=3 lun=1;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=6 lun=1;

#
# In case there are wide tape drives, one can use these targets
#
#name="st" class="scsi" target=8 lun=0;
#name="st" class="scsi" target=9 lun=0;
#name="st" class="scsi" target=10 lun=0;
#name="st" class="scsi" target=11 lun=0;
#name="st" class="scsi" target=12 lun=0;
#name="st" class="scsi" target=13 lun=0;
#name="st" class="scsi" target=14 lun=0;
#name="st" class="scsi" target=15 lun=0;

# This line adds support for Fibre Channel Tapes
name="st" parent="fp" target=0;
name="st" parent="fp" target=1;
name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=1 lun=1;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=2 lun=1;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=3 lun=1;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=6 lun=1;
name="st" class="scsi" target=7 lun=0;
name="st" class="scsi" target=7 lun=1;
name="st" class="scsi" target=8 lun=0;
name="st" class="scsi" target=8 lun=1;

devlink.tab: -

#ident "@(#)devlink.tab.sh 1.72 00/07/17 SMI"
#
# Copyright (c) 1998 by Sun Microsystems, Inc.
#
#
# This is the table used by devlinks
#
# Each entry should have 2 fields; but may have 3. Fields are separated
# by single tab ('\t') characters.
#
# The fields are:
#
# devfs-spec: a keyword-value set of devfs specifications, describing the set
# of devfs node entries to be linked.
#
# The keywords are:
#
# type - The devinfo node type (see <sys/sunddi.h> for possible values)
#
# name - the devinfo node name (the part of a /devices entry that appears
# before the '@' or ':').
#
# addr - the devinfo node address part (the portion of the name between
# the '@' and the ':').
#
# minor - the minor-attributes (the portion of a /devices name after the
# ':').
#
# The keywords are separated from their valuse by an equals ('=') sign;
# keyword-value pairs are separated from each other by semicolons (';').
#
# dev name - the /dev name corresponding to the devfs node described by
# the devfs-spec field. This specification is assume to start rooted at
# /dev; THE INITIAL /dev/ SHOULD NOT BE SPECIFIED!
# The name can contain a number of escape-sequences to include parts of
# the devfs-name in the /dev/-name. These escape-sequences all start with
# a backslash ('\') character. The current sequences are:
#
# \D - the devfs 'name' field
#
# \An - the 'n'th component of the address field (n=0 means the whole
# address field)
#
# \Mn - the 'n'th component of the minor field (n=0 means the entire
# minor field).
#
# \Nn - a sequential counter, starting at n (a *single* digit, giving
# a starting range of 0 through 9).
#
# extra dev link - a few devices need a second link; that is, a second link
# pointing to the first link. This optional field specifies the /dev
# format of this second link. This entry can also use the above-described
# escape-sequences.
#
# Fields can be blank; seperated by single tab characters,
# Spaces are significant, and are considered part of a field. IN GENERAL THIS
# MEANS THERE SHOULD BE NO SPACE CHARACTERS IN THIS FILE!
# All fields must be present (even if blank)
#
#
# devfs-spec Dev-Namespec Extra-Link
#
type=pcmcia:event;name=pem pem
type=ddi_pseudo;name=SUNW,rtvc;minor=ctl rtvc\M0
type=ddi_pseudo;name=SUNW,rtvc \M0
type=ddi_pseudo;name=vxspec;minor=0,raw vx/config
type=ddi_pseudo;name=vxspec;minor=1,raw vx/trace
type=ddi_pseudo;name=vxspec;minor=2,raw vx/iod
type=ddi_pseudo;name=vxspec;minor=3,raw vx/info
type=ddi_pseudo;name=vxspec;minor=4,raw vx/task
type=ddi_pseudo;name=vxspec;minor=5,raw vx/taskmon
type=ddi_pseudo;name=vxspec;minor=6,raw vx/clust
type=ddi_pseudo;name=vxspec;minor=7,raw vx/netiod
type=ddi_pseudo;name=vxspec;minor=8,raw vx/vcevent
type=ddi_pseudo;name=vxdmp;minor=0,raw vx/dmpconfig
type=ddi_pseudo;name=fdd \D
type=ddi_pseudo;name=vxportal \D
type=ddi_pseudo;name=gab \M0
type=ddi_pseudo;name=vxfen \M0
type=ddi_pseudo;name=vxfen \M1
type=ddi_byte@tape;addr=w10000000c98214d3,0; rmt/20\M0
type=ddi_byte@tape;addr=w10000000c98214b3,0; rmt/30\M0


I have done a reconfig reboot, have tried devfsadm, have done a sfgadm configure, and still cannot see the drives.

Any ideas ?

Regards.

 

[domburns62]

Try getting a cfgadm -o show_SCSI_LUN -al to see if the paths are connecting to the tape drives. From the cfgadm above you are connected but unconfigured.

Also could try a luxadm -e dump_map /dev/cfg/c3 and c4.

In your devlink, you are listing the wwn of the hba, I think that should be the wwn of the tape drives themselves.

Also what is the zoning on the Brocade showing? Are the devices logged in on that? Use nsshow for the logged in devices, use cfgActvshow to see the active zones on the switch.

 

[petemkuk]

Sorry - that was an old devlink.tab, this is the current one: -

#ident "@(#)devlink.tab.sh 1.72 00/07/17 SMI"
#
# Copyright (c) 1998 by Sun Microsystems, Inc.
#
#
# This is the table used by devlinks
#
# Each entry should have 2 fields; but may have 3. Fields
# by single tab ('\t') characters.
#
# The fields are:
#
# devfs-spec: a keyword-value set of devfs specifications,
# of devfs node entries to be linked.
#
# The keywords are:
#
# type - The devinfo node type (see <sys/sunddi.h> fo
#
# name - the devinfo node name (the part of a /device
# before the '@' or ':').
#
# addr - the devinfo node address part (the portion o
# the '@' and the ':').
#
# minor - the minor-attributes (the portion of a /dev
# ':').
#
# The keywords are separated from their valuse by an
# keyword-value pairs are separated from each other b
#
# dev name - the /dev name corresponding to the devfs node
# the devfs-spec field. This specification is assume
# /dev; THE INITIAL /dev/ SHOULD NOT BE SPECIFIED!
# The name can contain a number of escape-sequences t
# the devfs-name in the /dev/-name. These escape-seq
# a backslash ('\') character. The current sequences
#
# \D - the devfs 'name' field
#
# \An - the 'n'th component of the address field (n=0
# address field)
#
# \Mn - the 'n'th component of the minor field (n=0 m
# minor field).
#
# \Nn - a sequential counter, starting at n (a *singl
# a starting range of 0 through 9).
#
# extra dev link - a few devices need a second link; that i
# pointing to the first link. This optional field sp
# format of this second link. This entry can also us
# escape-sequences.
#
# Fields can be blank; seperated by single tab characters,
# Spaces are significant, and are considered part of a fiel
# MEANS THERE SHOULD BE NO SPACE CHARACTERS IN THIS FILE!
# All fields must be present (even if blank)
#
#
# devfs-spec Dev-Namespec Extra-Link
#
type=pcmcia:event;name=pem pem
type=ddi_pseudo;name=SUNW,rtvc;minor=ctl rtvc\M0
type=ddi_pseudo;name=SUNW,rtvc \M0
type=ddi_pseudo;name=vxspec;minor=0,raw vx/config
type=ddi_pseudo;name=vxspec;minor=1,raw vx/trace
type=ddi_pseudo;name=vxspec;minor=2,raw vx/iod
type=ddi_pseudo;name=vxspec;minor=3,raw vx/info
type=ddi_pseudo;name=vxspec;minor=4,raw vx/task
type=ddi_pseudo;name=vxspec;minor=5,raw vx/taskmon
type=ddi_pseudo;name=vxspec;minor=6,raw vx/clust
type=ddi_pseudo;name=vxspec;minor=7,raw vx/netiod
type=ddi_pseudo;name=vxspec;minor=8,raw vx/vcevent
type=ddi_pseudo;name=vxdmp;minor=0,raw vx/dmpconfig
type=ddi_pseudo;name=fdd \D
type=ddi_pseudo;name=vxportal \D
type=ddi_pseudo;name=gab \M0
type=ddi_pseudo;name=vxfen \M0
type=ddi_pseudo;name=vxfen \M1
type=ddi_byte@tape;addr=w500507630f5ac30c,0; rmt/20\M0
type=ddi_byte@tape;addr=w500507630f5ac363,0; rmt/30\M0

The drives are showing as logged in on the fabric okay.

# cfgadm -o show_SCSI_LUN -al
Ap_Id Type Receptacle Occupant Condition
c1 fc-fabric connected configured unknown
c1::22540002ac000723,100 disk connected configured unknown
c1::22540002ac000723,101 disk connected configured unknown
c1::22540002ac000726,100 disk connected configured unknown
c1::22540002ac000726,101 disk connected configured unknown
c2 fc-fabric connected configured unknown
c2::23540002ac000723,100 disk connected configured unknown
c2::23540002ac000723,101 disk connected configured unknown
c2::23540002ac000726,100 disk connected configured unknown
c2::23540002ac000726,101 disk connected configured unknown
c3 fc-fabric connected unconfigured unknown
c4 fc-fabric connected unconfigured unknown


# luxadm -e dump_map /dev/cfg/c3
No devices are found on /dev/cfg/c3.
# luxadm -e dump_map /dev/cfg/c4
No devices are found on /dev/cfg/c4.

# cfgadm -c configure c3
# cfgadm -c configure c4

# cfgadm -o show_SCSI_LUN -al
Ap_Id Type Receptacle Occupant Condition
c1 fc-fabric connected configured unknown
c1::22540002ac000723,100 disk connected configured unknown
c1::22540002ac000723,101 disk connected configured unknown
c1::22540002ac000726,100 disk connected configured unknown
c1::22540002ac000726,101 disk connected configured unknown
c2 fc-fabric connected configured unknown
c2::23540002ac000723,100 disk connected configured unknown
c2::23540002ac000723,101 disk connected configured unknown
c2::23540002ac000726,100 disk connected configured unknown
c2::23540002ac000726,101 disk connected configured unknown
c3 fc-fabric connected unconfigured unknown
c4 fc-fabric connected unconfigured unknown



We originally had the emulex drivers installed but could not see the drives, so we tried the leadville ones instead.
Still no joy.
Could it be an issue with the M5000 server not working with this version of the driver ? It is at 2.72a2.
I see the latest I can find is 2.82a3.

 

[petemkuk]

I have just checked in emlxadm, and see the following: -

EMLXADM Device Management Utility, Version 1.00r
COPYRIGHT ® 2004-2006 Emulex. All rights reserved.

Available HBA's:

1./devices/pci@1,700000/lpfc@0/fp@0,0:devctl (NOT CONNECTED)
2./devices/pci@3,700000/pci@0/pci@9/pci@0/pci@0/lpfc@0/fp@0,0:devctl (NOT CONNECTED)
3./devices/pci@2,600000/SUNW,qlc@0/fp@0,0:devctl (CONNECTED)
4./devices/pci@3,700000/pci@0/pci@1/pci@0/pci@0/SUNW,qlc@0/fp@0,0:devctl (CONNECTED)

 

[domburns62]

Your emulex cards are showing not connected in the emlxadm output, entries 1 & 2. Its the qlogic cards that are connected. I'd check zoning on the switch.

The luxadm -e dump_map should show what is out on the fabric even if cfgadm isn't up to date. Another sanity check is to use the apply show-children command from the OBP, that way you can be sure that the path is working without worrying about drivers.

Not sure on the current driver versions, but updating is normally a good idea.

 

[petemkuk]

fcinfo hba-port
HBA Port WWN: 10000000c98214d3
OS Device Name: /dev/cfg/c3
Manufacturer: Emulex
Model: LPe11000-M4
Firmware Version: 2.72a2 (Z3D2.72A2)
FCode/BIOS Version: 3.01a1
Serial Number: BT84228481
Driver Name: emlxs
Driver Version: 2.31h (2008.06.16.08.54)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c98214d3

HBA Port WWN: 10000000c98214b3
OS Device Name: /dev/cfg/c4
Manufacturer: Emulex
Model: LPe11000-M4
Firmware Version: 2.72a2 (Z3D2.72A2)
FCode/BIOS Version: 3.01a1
Serial Number: BT84228513
Driver Name: emlxs
Driver Version: 2.31h (2008.06.16.08.54)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 20000000c98214b3

Zoning is fine as another host that uses these 2 tape drives works fine. It is Solaris 9 though on a V490, whereas this is Solaris 10, and M5000.

 

[domburns62]

The fact that fcinfo shows it is online doesn't indicate that zoning in the switch is correct. Port status of online only indicates an fc link, the fact that it show's not connected in emlxadm implies that there are no devices in the zone other than the hba. The only way fcinfo would report offline would be if the port was disabled at the switch (or the cable/sfp was unplugged).
The fact that another host can see the same tape drives only means that the zoning for that host is correct.

If you do a luxadm -e dump_map /dev/cfg/c3 c4, you should see an entry for the hba in there (device type 0x1f unknown type, host bus adapter) with the port number it is attached to on the switch and any devices that are in the same zone. You can run that command on the "working" Solaris host (it runs on Solaris 9 as well), if both hbas are in the same zone you will see 2 entries with a device type of 0x1f, the local hosts hba will show host bus adapter.

And I would update the drivers on this host when you have a chance. I know there are newer emulex drivers than June 2008 out.