Storage 6130 Post: 302392285

Sponsored Content

Operating Systems Solaris Storage 6130 Post 302392285 by incredible on Thursday 4th of February 2010 01:49:44 AM

02-04-2010

Registered User

As a precaution, what we do for expansion unit are as follows, not sure if its same for adding additional HDDs:-
All reconfigurations are performed while the system is offline from accepting I/O
from the host system (I/O has been quiesced).
System reconfiguration involves power cycling of storage arrays.
Data stored on the arrays will need to be evacuated before any reconfiguration
procedure starts. During the reconfiguration process, all existing volumes (storage
pools) will be deleted and recreated.

---------- Post updated at 02:15 PM ---------- Previous update was at 02:11 PM ----------

How to Add New Storage Disk Devices to Solaris[TM] Without Performing a Reconfiguration Boot

--------------------------------------------------------------------------------

Description

This document describes how to add storage devices without performing a reconfiguration boot(boot -r).

Steps to Follow

It is important to note that not all storage can be added hot, so use discretion when adding new hardware.

As a general rule, use the following guidelines:

Copper SCSI devices are not hot plug, with the exception of devices that use SCA-2 connectors to attach to the SCSI bus.

Fibre Channel devices are hot plug.

For Copper SCSI devices, there are quite a few more exceptions to the above rule. Consult the documentation for the device in question to answer this. Also, note the distinction between the hot-plug capability of devices in an enclosure and the hot-plug capability of the enclosure itself:

if the drives use SCA-2 connectors, they are hot-plug. The enclosure itself will likely use a VHCI, HD68 or HD50 SCSI cable, which is not designed with hot-plug in mind, so the enclosure itself is not hot-plug.

Choosing to hot-plug devices that are not capable can lead to a variety of errors: from a simple hung SCSI bus (cleared by a reboot) to electrically induced damage of host bus adaptors and/or devices. Especially newer, faster ultra3scsi host bus adapters and devices are a lot more sensitive to electrical damage. Additionally, your host may hang during attachment, requiring a boot cycle to initialize the bus.

This document describes general procedures for adding hardware while the system is up, but cannot take into account every possible hardware device or scenario. When in doubt, power down the host before adding your device!

General Procedure for Adding Storage in Solaris[TM]

1- Attach the disk or array to the host.

2- Power on the disk or array if applicable

3- Check, using the format command, to verify that the storage isn't already seen after a minute or two of being powered on. The devfsadmd daemon will be running in the background and constantly checking for the presence of new hardware, so often times the device will be found right away. This would be the expected behavior in a SAN environment for example.

If format does not see the device, and the device is directly attached Copper SCSI, run: devfsadm -c disk, and recheck format.
If format does not see the device, and the device is a directly attached Fibre Channel SCSI, run: luxadm insert_device and follow the prompts. Then re-check format.
If format does not see the device, and the device is a SAN attached Fibre Channel SCSI, Reference < Solution: 213181 > : Troubleshooting Fibre Channel Devices from the OS
If format does not see the device, and the device is a SAN attached iSCSI device, Reference < Solution: 205630 >: Host sees the iSCSI Target but fails to recognize the LUN
If format sees the device, you are complete.

---------- Post updated at 02:49 PM ---------- Previous update was at 02:15 PM ----------

And one more likelyhood is that your storage will go to Degraded state if your new disks firmware are not in sync with the existing. You will need to upgrade CAM , firmware too during your downtime

incredible

View Public Profile for incredible

Find all posts by incredible

LEARN ABOUT SUNOS

usoc

usoc(7D)							      Devices								  usoc(7D)

NAME

       usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver

DESCRIPTION

       The  Fibre  Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
       Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.

FILES

       /kernel/drv/usoc

	   32-bit ELF kernel module

       /kernel/drv/sparcv9/usoc

	   64-bit ELF kernel module

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Architecture		     |SPARC			   |
       +-----------------------------+-----------------------------+
       |Interface stability	     |Unknown			   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWusoc			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)

       Writing Device Drivers

       Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994

       Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996

	Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998

       Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998

DIAGNOSTICS

       The following messages are logged and may also appear on the system console. On the console these messages are preceded by:

       usoc%d:

       where

       usoc%d:
       is the per-port instance number of the usoc controller.

       Fibre Channel is ONLINE

       The Fibre Channel loop is now online.

       Fibre Channel Loop is ONLINE

       The Fibre Channel loop is now online.

       Fibre Channel Loop is OFFLINE

       The Fibre Channel loop is now offline.

       attach failed: device in slave-only slot.

       Move soc+ card to another slot.

       attach failed: alloc soft state.

       Driver did not attach, devices will be inaccessible.

       attach failed: bad soft state.

       Driver did not attach, devices will be inaccessible.

       attach failed: unable to map eeprom

       Driver was unable to map device memory; check for bad hardware.	Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to map XRAM

       Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to map registers

       Driver was unable to map device registers; check for bad hardware. Driver did not attach to device,   devices will be inaccessible.

       attach failed: unable to access status register

       Driver was unable to map device	registers; check for bad hardware.  Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to install interrupt handler

       Driver was not able to add the interrupt routine  to the kernel. Driver did not attach to device, devices will be inaccessible.

       attach failed: unable to access host adapter XRAM

       Driver was unable to access device RAM; check for  bad  hardware. Driver did not attach to device,  devices will be inaccessible.

       attach failed: unable to write host adapter XRAM

       Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

       attach failed: read/write mismatch in XRAM

       Driver was unable to verify device RAM; check for  bad hardware. Driver did not attach to device, devices will be inaccessible.

SunOS 5.10							    20 Jul 1999 							  usoc(7D)