ys. i saw it b4 and it went away now. i try that wen coming back to office.tq
Main Topics
Browse All TopicsHI.
i am using solaris 8 . i cannot see my disk in Clariion SAN storage (FC-4700).
i have done below but still failed:
i) reboot server with boot -rv , run devfsadm
ii) run format , only see local disk
i have check HBA card in prtdiag file and the status is ok.
i can ping SAN SP ip address.meaning connectiviticy is ok.
any command or what should i try to solve the problem.
tq
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
i have try lputil and can see many opition there.
from my reading, maybe there is problem with persistent binding.
should i refresh the binding ?..
i did not remove any adapters to another slot.
some info of lputil.
..........................
1) link status
Link Status for Adapter 0:
Link Failure Count: 00000002
Loss Sync Count: 00000007
Loss Signal Count: 00000000
Prim Seq Err Count: 00000000
Invalid Xmit Word: 00000010
CRC Count: 00000000
Prim Seq Timeout: 00000002
Elastic Overrun: 00000000
ARB Timeout: 00000000
2) Status and Counters for Adapter 0:
Active RPI Count: 0000
Active XRI Count: 0000
Xmit Byte Count: 00000008
Rcv Byte Count: 00000007
Xmit Frame Count: 00000026
Rcv Frame Count: 00000037
Xmit Seq Count: 00000026
Rcv Seq Count: 00000037
Total Orig Xchgs: 0000001A
Total Resp Xchgs: 00000004
Rcv PBSY Count: 00000000
Rcv FBSY Count: 00000000
is there any other info needed to recover this prob.
i have increase points as this is critical , my systems has been down for a week.our support with vendor has expired .
When did the storage disappear? What has happened/changed?!!
A) Starting lputil, you should see some status info message like this one:
# /usr/sbin/lpfc/lputil
LightPulse Common Utility for Solaris/SPARC. Version 1.6a8 (03/03/2004).
Copyright (c) 2003, Emulex Network Systems, Inc.
Emulex Fibre Channel Host Adapters Detected: 2
Host Adapter 0 (lpfc0) is an LP9K (Ready Mode)
Host Adapter 1 (lpfc1) is an LP9K (Ready Mode)
B) Check entries in /kernel/drv/lpfc.conf (bindings are defined here)
Do you know the WWNs of your Clariion storage?
Do you have a switch between host and storage or is it direct attached?
C) Also, please check your messages file if the emulex LP card did recognize the connection:
grep lpfc /var/adm/messages
grep lpfc /var/adm/messages.? (to check older files)
Cheers,
JustUNIX
Also, please tell us how your FC4700 is connected. I have an FC4700 hooked to a 2-node Solaris 8 (E450's) cluster with Veritas VCS and VEA through EMC/Brocade switches. I also have ECC (EMC Control Center) to monitor the physical health of the cluster. What is your configuration?
I also had a fibre cable crimped (might as well have cut it!) by people doing work around the storage cabinet. Was any work being done around your gear?
JustUNIX - I agree about where the problem undoubtedly lies (and also that dmesg output can be found in /var/adm/messages, but I like dmesg for recently-booted-system information). I was giving my system's config as an example.
kintos: Your FC4700 should have an administrative workstation with Navisphere on it. Can you reach the FC4700 through that (to check its health). You can ping it, so the 4700 is alive and well, to some degree.
By asking you to run 'dmesg' I was hoping to see output such as LUN acquisition:
Nov 3 11:17:12 DPH-DB002 Emulex LightPulse FC SCSI/IP 5.02b
Nov 3 11:17:15 DPH-DB002 lpfc: [ID 104753 kern.info] NOTICE: lpfc2:031:Link Up Event received Data: 1 1 0 0
Nov 3 11:17:16 DPH-DB002 lpfc: [ID 129691 kern.notice] NOTICE: lpfc2: Firmware Rev 3.91A3 (D2D3.91A3)
Nov 3 11:17:16 DPH-DB002 lpfc: [ID 664688 kern.notice] NOTICE: lpfc2: WWPN:10:00:00:00:c9:24:f0:
24:f0:ec DID 0x610b13
Nov 3 11:17:16 DPH-DB002 lpfc: [ID 457646 kern.info] NOTICE: Device Path for interface lpfc2:
Nov 3 11:17:16 DPH-DB002 pcipsy: [ID 370704 kern.info] PCI-device: fibre-channel@2, lpfc2
Nov 3 11:17:16 DPH-DB002 genunix: [ID 936769 kern.info] lpfc2 is /pci@6,4000/fibre-channel@
Nov 3 11:17:19 DPH-DB002 lpfc: [ID 615023 kern.info] NOTICE: lpfc3:031:Link Up Event received Data: 1 1 0 0
Nov 3 11:17:21 DPH-DB002 lpfc: [ID 129691 kern.notice] NOTICE: lpfc3: Firmware Rev 3.91A3 (D2D3.91A3)
Nov 3 11:17:21 DPH-DB002 lpfc: [ID 664688 kern.notice] NOTICE: lpfc3: WWPN:10:00:00:00:c9:21:82:
21:82:b3 DID 0x610b13
Nov 3 11:17:21 DPH-DB002 lpfc: [ID 457646 kern.info] NOTICE: Device Path for interface lpfc3:
Nov 3 11:17:21 DPH-DB002 pcipsy: [ID 370704 kern.info] PCI-device: fibre-channel@1, lpfc3
Nov 3 11:17:21 DPH-DB002 genunix: [ID 936769 kern.info] lpfc3 is /pci@6,2000/fibre-channel@
Nov 3 11:17:21 DPH-DB002 lpfc: [ID 685918 kern.notice] NOTICE: lpfc2: Acquired FCP/SCSI Target 0 LUN 0
Nov 3 11:17:21 DPH-DB002 D_ID 0x610413 WWPN:50:06:01:60:40:04:e1:
Nov 3 11:17:21 DPH-DB002 lpfc: [ID 685918 kern.notice] NOTICE: lpfc2: Acquired FCP/SCSI Target 0 LUN 1
[other LUNs acquired by the HBA],
and later as LUNs are loaded into the kernel:
Nov 3 11:17:28 DPH-DB002 genunix: [ID 936769 kern.info] pci_pci0 is /pci@1f,2000/pci@1
Nov 3 11:17:28 DPH-DB002 pci_pci: [ID 370704 kern.info] PCI-device: SUNW,isptwo@4, isp0
Nov 3 11:17:28 DPH-DB002 genunix: [ID 936769 kern.info] isp0 is /pci@1f,2000/pci@1/SUNW,is
Nov 3 11:17:28 DPH-DB002 scsi: [ID 365881 kern.info] /pci@1f,2000/pci@1/SUNW,is
Nov 3 11:17:28 DPH-DB002 Firmware Version: v4.66, Customer: 0, Product: 4
Nov 3 11:17:28 DPH-DB002 scsi: [ID 193665 kern.info] sd191 at lpfc3: target 0 lun 0
Nov 3 11:17:28 DPH-DB002 genunix: [ID 936769 kern.info] sd191 is /pci@6,2000/fibre-channel@
and then up the boot process as the emcpower devices are loaded and acquired to the point where PowerPath loads:
Nov 3 11:19:49 DPH-DB002 PowerPath[83]: [ID 702911 daemon.notice] executing "powermt load"
Nov 3 11:19:49 DPH-DB002 PowerPath[85]: [ID 702911 daemon.notice] executing "powermt config"
Nov 3 11:19:52 DPH-DB002 PowerPath[91]: [ID 702911 daemon.notice] reading registration file
Nov 3 11:20:08 DPH-DB002 genunix: [ID 454863 kern.info] dump on /dev/dsk/c0t0d0s1 size 4000 MB
I'm hoping the absence of a set of messages such as these will help localize the problem.
kintos - thanks for checking in with us. In addition to letting us know the status of LUN acquisition and powerpath from the last boot, let's check the status of your FC4700. Assuming you have powerpath, would you run the following commands? You will have to run them as root, and either be in or have /opt/EMCpower/bin/ in your path. I've enclosed short information so you can see what a functioning system looks like.
# powermt display [gives device summary. For detail information see below]
Symmetrix logical device count=0
CLARiiON logical device count=27
==========================
----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==========================
0 pci@6,4000/fibre-channel@2
1 pci@6,2000/fibre-channel@1
# powermt display dev=all [gives detailed status for each individual device.]
Pseudo name=emcpower21a
CLARiiON ID=F20011400352
Logical device ID=6006016417600000568C21E
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
==========================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==========================
0 pci@6,4000/fibre-channel@2
1 pci@6,2000/fibre-channel@1
[rest of logical EMC power devices not listed]
# powermt display ports
Storage class = CLARiiON
==========================
----------- Storage System --------------- -- I/O Paths -- --- Stats ---
ID Interface Wt_Q Total Dead Q-IOs Errors
==========================
F20011400352 SP A0 256 27 0 0 0
F20011400352 SP B0 256 27 0 0 0
# powermt display paths
CLARiiON logical device count=27
==========================
----- Host Bus Adapters --------- ------ Storage System ----- - I/O Paths -
### HW Path ID Interface Total Dead
==========================
0 pci@6,4000/fibre-channel@2
1 pci@6,2000/fibre-channel@1
Thanks.
Business Accounts
Answer for Membership
by: durindilPosted on 2006-01-02 at 12:43:31ID: 15593459
Could you see the storage before, and it went away?
If not, and you are adding storage, you need to first enable persistent binding in your HBA conf file (i.e. /kernel/drv/lpfc.conf) and then add the necessary luns to the /kernel/drv/sd.conf file. Then, you would do a boot -- -r to discover the disks.