E420 still seeing IBM Shark fibre LUNs after de-allocating

From: Robert Banniza (RPBanniz@ascensionhealth.org)
Date: Thu Jul 18 2002 - 11:33:07 EDT


I have a Sun E420R using a JNI1063 fibre card connected to an IBM ESS
Shark via switched fabric using Veritas Volume Manager for managing the
volumes. I recently de-allocated several drives (LUNS) from the E420 to
return them back to the Shark as unused disks. There were listed in
Veritas as unitialized disks. However, after doing this, I ran a
'devfsadm -C' to clean up any device entries and then rebooted the
machine with 'reboot  -r' for good measure. The problem I'm having now
is that I'm getting the following error messages upon bootup and Veritas
will not mount the other vxfs mountpoints upon boot:
 
######################################
Rebooting with command: boot -r
Boot device: /pci@1f,4000/scsi@3/disk@0,0 File and args: -r
SunOS Release 5.8 Version Generic_108528-14 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
/kernel/drv/sparcv9/fca-pci symbol ddi_model_convert_from multiply
defined
fca-pci0: JNI Fibre Channel Adapter model FCI-1063
fca-pci0: SCSI ID 125 / AL_PA 0x1
fca-pci0: Fibre Channel WWNN: 100000E069C01BBC WWPN: 200000E069C01BBC
fca-pci0: FCA SCSI/IP Driver Version 2.6.11, June 3, 2002 for Solaris
64-bit
fca-pci0: All Rights Reserved.
NOTICE: pci1242,46430 NPORT Initialization Complete, SID=C01BBC
fca-pci0: New Fabric Parameters Received. Resetting...
fca-pci0: LINK DOWN
NOTICE: pci1242,46430 NPORT Initialization Complete, SID=C01BBC
fca-pci0: LINK UP (180002FF)
fca-pci0: Host: Port 011C00 (100000E069C01BBC:200000E069C01BBC)
fca-pci0: Port 011000 (5005076300C08253:5005076300C38253) available.
fca-pci0: Port 011100 (5005076300C08253:5005076300C78253) available.
fca-pci0: Target 0: Port 011000 (5005076300C08253:5005076300C38253)
online.
fca-pci0: Target 0 Lun 0: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 1: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 2: Port 011000
(5005076300C08253:5005076300C38253) present.
fca-pci0: Target 0 Lun 3: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 4: Port 011000
(5005076300C08253:5005076300C38253) present.
fca-pci0: Target 0 Lun 5: Port 011000
(5005076300C08253:5005076300C38253) present.
WARNING: forceload of misc/md_trans failed
WARNING: forceload of misc/md_raid failed
WARNING: forceload of misc/md_hotspares failed
WARNING: forceload of misc/md_sp failed
Starting VxVM restore daemon...
VxVM starting in boot mode...
NOTICE: vxvm:vxdmp: added disk array 17595
 
configuring IPv4 interfaces: hme0.
Hostname: ebsun02
Configuring /dev and /devices
fca-pci0: Target 0 Lun 0: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 1: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 3: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 0: Port 011000
(5005076300C08253:5005076300C38253) not present.
fca-pci0: Target 0 Lun 0: Port 011000
(5005076300C08253:5005076300C38253) not present.
Configuring the /dev directory (compatibility devices)
VxVM general startup...
Initializing random number generator...
done.
syslog service starting.
volume management starting.
Jul 18 09:42:28 ebsun02 fca-pci: fca-pci0: Target 0 Lun 3: Port
011000 (5005076300C08253:5005076300C38253) not present.
Starting vradmind daemon
Starting RMI Registry
Starting VERITAS VM Storage Administrator Command Server
Starting VERITAS VM Storage Administrator Server
Starting VxRSync master daemon(s)
VRADMIND: started.
sshd: SSH Secure Shell 3.1.2 (non-commercial version) on
sparc-sun-solaris2.8
Jul 18 09:42:28 ebsun02 last message repeated 1 time
Jul 18 09:42:40 ebsun02 sshd[419]: Listener created on port 22.
Jul 18 09:42:40 ebsun02 sshd[424]: Daemon is running.
Oracle startup: cannot start
Change to state 3 has been completed.
######################################
 
As you can see, fca-pci0 is reporting LUNs as not being present. These
are the LUNs that I took away. Why didn't 'devfsadm -C' clean this up?
Do I need to modify /kernel/drv/sd.conf manually? Also, do I need to
modify /kernel/drv/fca-pci.conf manually as well? Any help appreciated.
 
Robert Banniza
Senior UNIX Administrator
Ascension Health ISD

NOTE: This e-mail message may contain information that may be privileged,
confidential, and exempt from disclosure. It is intended for use only by
the person to whom it is addressed. If you have received this message in
error, please do not forward or use this information in any way, delete it
immediately, and contact the sender as soon as possible by the reply option
or by telephone at the telephone number listed (if available). Thank you.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:37 EDT