Veritas Volume Manager (VxVM) 5.0 MP3 triggers SCSI messages for EMC BCV luns that are in a Not-Ready (NR) / established state
Article ID: 100001913
Updated On:
Resolution
Prior to installing VxVM 5.0 MP3 RP4 HF1
In this instance, Veritas disk access name "emc0_00eb" happens to be an EMC BCV lun. The EMC BCV lun is in an established, Not-Ready device state, as indicated by the extended attributes field "bcv-nr".
# vxdisk -e list | grep emc0_00eb
emc0_00eb auto - - error c1t5006048C5368E580d20s2 bcv-nr
EMC SYMCLI command "syminq" also reports the EMC lun type.
# syminq | grep EB0
/dev/rdsk/c1t5006048C5368E5A0d199s2 BCV EMC SYMMETRIX 5773 22000EB000 2209920
/dev/rdsk/c1t5006048C5368E580d20s2 BCV EMC SYMMETRIX 5773 22000EB000 2209920
The paths to the BCV lun are disabled at this time.
# vxdisk list emc0_00eb
Device: emc0_00eb
devicetag: emc0_00eb
type: auto
flags: error private autoconfig
pubpaths: block=/dev/vx/dmp/emc0_00ebs2 char=/dev/vx/rdmp/emc0_00ebs2
guid: -
udid: EMC%5FSYMMETRIX%5F000290300822%5F60060480000290300822533030304542
site: -
Multipathing information:
numpaths: 2
c1t5006048C5368E5A0d199s2 state=disabled
c1t5006048C5368E580d20s2 state=disabled
When executing the VxVM CLI command "vxdctl enable", this triggers the SCSI event messages.
# vxdctl enable
/var/adm/messages
Jul 6 10:53:34 rdgv240sol14 Error for Command: read Error Level: Fatal
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 220EB000Q
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Sense Key: Not Ready
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.warning] Warning: /pci@1e,600000/SUNW,jfca@2/fp@0,0/ssd@w5006048c5368e580,14 (ssd21):
Jul 6 10:53:34 rdgv240sol14 Error for Command: read Error Level: Fatal
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 220EB000Q
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Sense Key: Not Ready
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.warning] Warning: /pci@1e,600000/SUNW,jfca@2/fp@0,0/ssd@w500601603021c60e,1 (ssd19):
Jul 6 10:53:34 rdgv240sol14 offline or reservation conflict
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.warning] Warning: /pci@1e,600000/SUNW,jfca@2/fp@0,0/ssd@w5006048c5368e580,14 (ssd21):
Jul 6 10:53:34 rdgv240sol14 Error for Command: read Error Level: Fatal
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 220EB000Q
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Sense Key: Not Ready
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.warning] Warning: /pci@1e,600000/SUNW,jfca@2/fp@0,0/ssd@w500601613021c60e,1 (ssd14):
Jul 6 10:53:34 rdgv240sol14 offline or reservation conflict
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.warning] Warning: /pci@1e,600000/SUNW,jfca@2/fp@0,0/ssd@w5006048c5368e580,14 (ssd21):
Jul 6 10:53:34 rdgv240sol14 Error for Command: read Error Level: Fatal
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 220EB000Q
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] Sense Key: Not Ready
Jul 6 10:53:34 rdgv240sol14 scsi: [ID 107833 kern.notice] ASC: 0x4 (LUN not ready intervention required), ASCQ: 0x3, FRU: 0x0
Summary
The function "devintf_check_label()" issues a USCSICMD to read the label sectors for a disk.
As a result of doing so, this triggers the SCSI messages for non-readable/Not-Ready (NR) related devices.
After applying VxVM 5.0 MP3 RP4 HF1, the above EMC DMX SCSI "Not Ready (NR)" messages are no longer reported.
Applies To
Solaris
Issue/Introduction
This document attempts to explain the benefits surrounding the installation of the Veritas Volume Manager (VxVM) hot-fix for 5.0 MP3 RP4 HF1.
Prior to applying the hot-fix, VxVM CLI command such as "vxdisk -o alldgs list", vxdisk scandisks etc, would trigger SCSI messages for EMC luns that are in a Not-Ready (NR).
Example:
An EMC BCV lun in an established state, would equate to a Not-Ready (NR) state.
As a result of applying the hot-fix, less SCSI events and related messages for such devices in a Not-Ready state will be recorded on the console and in the corresponding /var/adm/messages file.
Prior to applying the hot-fix, VxVM CLI command such as "vxdisk -o alldgs list", vxdisk scandisks etc, would trigger SCSI messages for EMC luns that are in a Not-Ready (NR).
Example:
An EMC BCV lun in an established state, would equate to a Not-Ready (NR) state.
As a result of applying the hot-fix, less SCSI events and related messages for such devices in a Not-Ready state will be recorded on the console and in the corresponding /var/adm/messages file.
Additional Information
ETrack: 2054201
Was this article helpful?
Yes
No
Powered by
